cc/td/doc/product/mels/15530/12_2_sv
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Configuring Trunk and Uplink Card Interfaces

Configuring 2.5-Gbps ITU Trunk Card Interfaces

Displaying the 2.5-Gbps ITU Trunk Card Interface Configuration

Configuring 10-Gbps ITU Trunk Card Interfaces

Displaying the 10-Gbps ITU Trunk Card Interface Configuration

Configuring 10-Gbps ITU Tunable Trunk Card Interfaces

Displaying the 10-Gbps ITU Tunable Trunk Card Interface Configuration

Configuring 10-Gbps Uplink Card Interfaces

Displaying the 10-Gbps Uplink Card Interface Configuration

About Cross Connections

Configuring Cross Connections

Displaying the Cross Connection Configuration

About Alarm Thresholds

Configuring Alarm Thresholds

Displaying the Alarm Threshold Configuration

About Patch Connections

Configuring Patch Connections

About Performance History Counters

Displaying Performance History Counters


Configuring Trunk and Uplink Card Interfaces

This chapter describes how to configure 2.5-Gbps ITU trunk cards, 10-Gbps ITU tunable and non tunable trunk cards, and 10-Gbps uplink cards on the Cisco ONS 15530. This chapter includes the following sections:

• Configuring 2.5-Gbps ITU Trunk Card Interfaces

• Configuring 10-Gbps ITU Trunk Card Interfaces

• Configuring 10-Gbps ITU Tunable Trunk Card Interfaces

• Configuring 10-Gbps Uplink Card Interfaces

• About Cross Connections

• Configuring Cross Connections

• About Alarm Thresholds

• Configuring Alarm Thresholds

• About Patch Connections

• Configuring Patch Connections

• About Performance History Counters

• Displaying Performance History Counters

Configuring 2.5-Gbps ITU Trunk Card Interfaces

To configure the 2.5-Gbps ITU trunk card interface, perform the following tasks, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface waveethernetphy slot/0

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# laser frequency number

Selects one of the two frequencies in GHz supported by the laser. The default is the lower frequency for the 2.5-Gbps ITU trunk card. (Optional)

Step 3 

Switch(config-if)# [no] loopback [facility | terminal]

Enables or disables internal loopback for testing and defect isolation. (Optional)

Step 4 

Switch(config-if)# [no] laser control safety enable

Enables or disables laser safety control.

Step 5 

Switch(config-if)# [no] laser shutdown

Turns the laser on and off. (Optional)

Note The laser must warm up for 2 minutes before carrying traffic.

Step 6 

Switch(config-if)# [no] cdl defect-indication force hop-endpoint

Enables or disables hop endpoint for in-band message channel defect indications when APS is not configured (Optional).

Step 7 

Switch(config-if)# no shutdown

Enables the interface.

Step 8 

Switch(config-if)# exit

Switch(config)

Returns to global configuration mode.

Step 9 

Switch(config)# interface wavepatch slot/0/0

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 10 

Switch(config-if)# optical threshold power receive {low | high} {alarm | warning} value [severity {critical | major | minor | not alarmed | not reported}]

Specifies the optical power receive threshold value in units of 0.1 dBm. The default values are as follows:

Low alarm: -28 dBm

Low warning: -26 dBm

High warning: -10 dBm

High alarm: -8 dBm

Alarm severity: major

Warning severity: not alarmed

Step 11 

Switch(config-if)# [no] shutdown

Enables or disables the interface.

Repeat Step 9 and Step 11 on wavepatch slot/0/1 for splitter 2.5-Gbps ITU trunk cards.

Caution Loopbacks on waveethernetphy interfaces disrupt service. Use this feature with care.

Note For configuration information for the ethernetdcc interface, see the "Configuring IP on Ethernetdcc Interfaces for the In-Band Message Channel" section on page 14-15.

Example

The following example shows how to configure 2.5-Gbps ITU trunk card waveethernetphy interfaces:

Switch(config)# interface waveethernetphy 10/0
Switch(config-if)# cdl defect-indication force hop-endpoint
Switch(config-if)# no shutdown

Displaying the 2.5-Gbps ITU Trunk Card Interface Configuration

To display the configuration of 2.5-Gbps ITU trunk card interfaces, use the following EXEC command:

Command
Purpose

show interfaces {waveethernetphy slot/0 | wavepatch slot/0/port}

Displays the interface configuration.


Examples

The following example shows how to display the configuration of a waveethernetphy interface:

Switch# show interfaces waveethernetphy 1/0
WaveEthernetPhy1/0 is up, line protocol is up
Channel: 1 Frequency: 192.1 Thz Wavelength: 1560.61 nm
Active Wavepatch : Wavepatch1/0/0
Splitter Protected : No
Signal quality : Good
Receive power level : -6.45 dBm
Laser shut down : No
Osc physical port : No
Wavelength used for inband management: No
Loopback not set

Configured threshold Group: None
CDL HEC error count: 0
CRC error count: 0
Code violation and running disparity error count( 64b66b cvrd): 0

Defect Indication Status : up
Configured Node Behavior : Hop Terminating
Current Node Behavior : Hop Terminating
Defect Indication Receive : FDI-H FDI-E
Defect Indication Transmit : BDI-H

Tx Frames sent to N/W : 218707020912

Tx Frames rcvd from Client : 0
Tx CRC Errors : 0
Tx HEC Errors : 0
Tx QuadPHY sybl Errs : 4257380395
Tx Dropped Frames : 0
Tx Oversize Frames : 0
Tx Undersize Frames : 0
Tx Idle Frames from Fabric : 0
Tx Generated CDL Idle Frames : 218720041509
(having an SII of 255)

Rx Frames rcvd from N/W : 218719304600

Rx Frames sent to Client : 647
Rx CRC Errors : 0
Rx HEC Errors : 0
Rx MII (Decoder) Errors : 0
Rx Dropped Frames : 0
Rx Oversize Frames : 0
Rx Undersize Frames : 0
Rx Total Drpd Idle Frames : 218719303953
Rx Dropped CDL Idle Frames : 218719301229
(having an SII of 255)

Last clearing of "show interface" counters never
Hardware is data_enabled_port
Switch#sh int wavepatch 1/0/0
Wavepatch1/0/0 is up, line protocol is up
Receiver power level: -6.46 dBm

Optical threshold monitored for : Receive Power (in dBm)
Threshold exceeded for : High Warning and High Alarm
Low alarm value = -28.0 (default)
Low Alarm Severity = major
Low warning value = -26.0 (default)
Low Warning Severity = not alarmed
High alarm value = -8.0 (default)
High Alarm Severity = major
High warning value = -10.0 (default)
High Warning Severity = not alarmed
Hardware is passive_port

The following example shows how to display the configuration of a wavepatch interface:

Switch# show interfaces wavepatch 1/0/0
Wavepatch1/0/0 is up, line protocol is up
Receiver power level: -6.46 dBm

Optical threshold monitored for : Receive Power (in dBm)
Threshold exceeded for : High Warning and High Alarm
Low alarm value = -28.0 (default)
Low Alarm Severity = major
Low warning value = -26.0 (default)
Low Warning Severity = not alarmed
High alarm value = -8.0 (default)
High Alarm Severity = major
High warning value = -10.0 (default)
High Warning Severity = not alarmed
Hardware is passive_port

Configuring 10-Gbps ITU Trunk Card Interfaces

To configure the 10-Gbps ITU trunk card interface, perform the following tasks, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface waveethernetphy slot/0

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# [no] loopback [facility | terminal]

Enables or disables internal loopback for testing and defect isolation. (Optional)

Step 3 

Switch(config-if)# [no] laser control safety enable

Enables or disables laser safety control.

Step 4 

Switch(config-if)# [no] laser shutdown

Turns the laser on and off. (Optional)

Note The laser must warm up for 2 minutes before carrying traffic.

Step 5 

Switch(config-if)# [no] cdl defect-indication force hop-endpoint

Enables or disables hop endpoint for in-band message channel defect indications when APS is not configured. (Optional)

Step 6 

Switch(config-if)# no shutdown

Enables the interface.

Step 7 

Switch(config-if)# exit

Switch(config)

Returns to global configuration mode.

Step 8 

Switch(config)# interface wavepatch slot/0/0

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 9 

Switch(config-if)# optical threshold power receive {low | high} {alarm | warning} value [severity {critical | major | minor | not alarmed | not reported}]

Specifies the optical power receive threshold value in units of 0.1 dBm. The default values are as follows:

Low alarm: -22 dBm

Low warning: -20 dBm

High warning: -10 dBm

High alarm: -8 dBm

Alarm severity: major

Warning severity: not alarmed

Step 10 

Switch(config-if)# [no] shutdown

Enables or disables the interface.

Repeat Step 8 and Step 10 on wavepatch slot/0/1 for splitter 10-Gbps ITU trunk cards.

Caution Loopbacks on waveethernetphy interfaces disrupt service. Use this feature with care.

Note For configuration information for the ethernetdcc interface, see the "Configuring IP on Ethernetdcc Interfaces for the In-Band Message Channel" section on page 14-15.

Example

The following example shows how to configure 10-Gbps ITU trunk card waveethernetphy interfaces:

Switch(config)# interface waveethernetphy 10/0
Switch(config-if)# cdl defect-indication force hop-endpoint
Switch(config-if)# no shutdown

Displaying the 10-Gbps ITU Trunk Card Interface Configuration

To display the configuration of 10-Gbps ITU trunk card interfaces, use the following EXEC command:

Command
Purpose

show interfaces {waveethernetphy slot/0[.subinterface] | wavepatch slot/0/port}

Displays the interface configuration.


Examples

The following example shows how to display the configuration of a waveethernetphy interface:

Switch# show interfaces waveethernetphy 1/0
WaveEthernetPhy1/0 is down, line protocol is down
Channel: 21 Frequency: 194.6 Thz Wavelength: 1540.56 nm
Active Wavepatch : Wavepatch1/0/0
Splitter Protected : Yes
Signal quality : Loss of lock
Receive power level : < -23.00 dBm
Laser shut down : No
Osc physical port : No
Wavelength capable for inband management: Yes
Loopback not set
Threshold monitored for: None
CDL HEC error count: 0
CRC error count: 0
Code violation and running disparity error count( 64b66b cvrd): 0

Defect Indication Status : up
Configured Node Behavior : None
Current Node Behavior : Path Terminating
Defect Indication Receive : None
Defect Indication Transmit : BDI-H

MTU Size: 10232 bytes

Total Tx Frames Sent to N/W: 0
Tx Gen CDL Idle Frame: 5162988928209

Rx Frames rcvd from N/W: 0
Rx IPG drpd pkts: 0
Rx Idle Packets : 0
Rx Oversize Frames : 0
Rx Undersize Frames : 0

Rx SII mismatch drpd data Frames : 0
Rx SII mismatch drpd idle Frames : 0

Last clearing of "show interface" counters never
Hardware is data_enabled_port

The following example shows how to display the configuration of a waveethernetphy subinterface:

Switch# show interfaces waveethernetphy 1/0.1
WaveEthernetPhy1/0.1 is down, line protocol is down

MTU Size: 10232 bytes

Tx Frames Sent to N/W: 0
Tx HEC Errors: 0
Tx CRC Errors: 0
Tx QuadPHY sybl Errs: 78206331656577
Tx Dropped Frames: 0
Tx Oversize Frames: 0
Tx Undersize Frames: 0
Tx Rcvd Idle Packets: 0

Rx Frames Sent to Clnt: 0
Rx FIFO full drpd pkts: 0
Rx Gen Idle pkt cnt: 0

Last clearing of "show interface" counters never
Hardware is data_enabled_port

The following example shows how to display the configuration of a wavepatch interface:

Switch# show interfaces wavepatch 1/0/0
Wavepatch1/0/0 is down, line protocol is down
Receiver power level: < -23.00 dBm

Optical threshold monitored for : Receive Power (in dBm)
Threshold exceeded for : Low Warning and Low Alarm
Low alarm value = -22.0 dBm (default)
Low Alarm Severity = major
Low warning value = -20.0 dBm (default)
Low Warning Severity = not alarmed
High alarm value = -6.0 dBm (default)
High Alarm Severity = major
High warning value = -8.0 dBm (default)
High Warning Severity = not alarmed
Hardware is passive_port

Configuring 10-Gbps ITU Tunable Trunk Card Interfaces

To configure the 10-Gbps ITU tunable trunk card interface, perform the following tasks, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface waveethernetphy slot/0

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# laser frequency number

Selects one of the four frequencies, in GHz, supported by the laser. The default is the lowest frequency supported by10-Gbps tunable ITU trunk card. (Optional)

Step 3 

Switch(config-if)# [no] loopback [facility | terminal]

Enables or disables internal loopback for testing and defect isolation. (Optional)

Step 4 

Switch(config-if)# [no] laser control safety enable

Enables or disables laser safety control.

Step 5 

Switch(config-if)# [no] laser shutdown

Turns the laser on and off. (Optional)

Note The laser must warm up for 2 minutes before carrying traffic.

Step 6 

Switch(config-if)# [no] cdl defect-indication force hop-endpoint

Enables or disables hop endpoint for in-band message channel defect indications when APS is not configured. (Optional)

Step 7 

Switch(config-if)# no shutdown

Enables the interface.

Step 8 

Switch(config-if)# exit

Switch(config)

Returns to global configuration mode.

Step 9 

Switch(config)# interface wavepatch slot/0/0

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 10 

Switch(config-if)# optical threshold power receive {low | high} {alarm | warning} value [severity {critical | major | minor | not alarmed | not reported}]

Specifies the optical power receive threshold value in units of 0.1 dBm. The default values are as follows:

Low alarm: -22 dBm

Low warning: -20 dBm

High warning: -10 dBm

High alarm: -8 dBm

Alarm severity: major

Warning severity: not alarmed

Step 11 

Switch(config-if)# [no] shutdown

Enables or disables the interface.

Repeat Step 8 and Step 10 on wavepatch slot/0/1 for splitter 10-Gbps ITU tunable trunk cards.

Caution Loopbacks on waveethernetphy interfaces disrupt service. Use this feature with care.

Note For configuration information for the ethernetdcc interface, see the "Configuring IP on Ethernetdcc Interfaces for the In-Band Message Channel" section on page 14-15.

Example

The following example shows how to configure 10-Gbps ITU tunable trunk card waveethernetphy interfaces:

Switch(config)# interface waveethernetphy 10/0
Switch(config-if)# laser frequency 193600
Switch(config-if)# cdl defect-indication force hop-endpoint
Switch(config-if)# no shutdown

Displaying the 10-Gbps ITU Tunable Trunk Card Interface Configuration

To display the configuration of 10-Gbps ITU tunable trunk card interfaces, use the following EXEC command:

Command
Purpose

show interfaces {waveethernetphy slot/0[.subinterface] | wavepatch slot/0/port}

Displays the interface configuration.


Examples

The following example shows how to display the configuration of a waveethernetphy interface:

Switch# show interfaces waveethernetphy 1/0
WaveEthernetPhy1/0 is down, line protocol is down
Channel: 21 Frequency: 194.6 Thz Wavelength: 1540.56 nm
Active Wavepatch : Wavepatch1/0/0
Splitter Protected : Yes
Signal quality : Loss of lock
Receive power level : < -23.00 dBm
Laser shut down : No
Osc physical port : No
Wavelength capable for inband management: Yes
Loopback not set
Threshold monitored for: None
CDL HEC error count: 0
CRC error count: 0
Code violation and running disparity error count( 64b66b cvrd): 0

Defect Indication Status : up
Configured Node Behavior : None
Current Node Behavior : Path Terminating
Defect Indication Receive : None
Defect Indication Transmit : BDI-H

MTU Size: 10232 bytes

Total Tx Frames Sent to N/W: 0
Tx Gen CDL Idle Frame: 5162988928209

Rx Frames rcvd from N/W: 0
Rx IPG drpd pkts: 0
Rx Idle Packets : 0
Rx Oversize Frames : 0
Rx Undersize Frames : 0

Rx SII mismatch drpd data Frames : 0
Rx SII mismatch drpd idle Frames : 0

Last clearing of "show interface" counters never
Hardware is data_enabled_port

The following example shows how to display the configuration of a waveethernetphy subinterface:

Switch# show interfaces waveethernetphy 1/0.1
WaveEthernetPhy1/0.1 is down, line protocol is down

MTU Size: 10232 bytes

Tx Frames Sent to N/W: 0
Tx HEC Errors: 0
Tx CRC Errors: 0
Tx QuadPHY sybl Errs: 78206331656577
Tx Dropped Frames: 0
Tx Oversize Frames: 0
Tx Undersize Frames: 0
Tx Rcvd Idle Packets: 0

Rx Frames Sent to Clnt: 0
Rx FIFO full drpd pkts: 0
Rx Gen Idle pkt cnt: 0

Last clearing of "show interface" counters never
Hardware is data_enabled_port

The following example shows how to display the configuration of a wavepatch interface:

Switch# show interfaces wavepatch 1/0/0
Wavepatch1/0/0 is down, line protocol is down
Receiver power level: < -23.00 dBm

Optical threshold monitored for : Receive Power (in dBm)
Threshold exceeded for : Low Warning and Low Alarm
Low alarm value = -22.0 dBm (default)
Low Alarm Severity = major
Low warning value = -20.0 dBm (default)
Low Warning Severity = not alarmed
High alarm value = -6.0 dBm (default)
High Alarm Severity = major
High warning value = -8.0 dBm (default)
High Warning Severity = not alarmed
Hardware is passive_port

Configuring 10-Gbps Uplink Card Interfaces

To configure the 10-Gbps uplink card interface, perform the following tasks, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface tengigethernetphy slot/0

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# [no] loopback [facility | terminal]

Enables or disables internal loopback for testing and defect isolation. (Optional)

Step 3 

Switch(config-if)# [no] laser shutdown

Turns the laser on and off. (Optional)

Step 4 

Switch(config-if)# [no] cdl defect-indication force hop-endpoint

Enables or disables hop endpoint for in-band message channel defect indications when APS is not configured. (Optional)

Step 5 

Switch(config-if)# [no] shutdown

Enables or disables the interface.

Caution Loopbacks on tengigethernetphy interfaces disrupt service. Use this feature with care.

Note For configuration information for the ethernetdcc interface, see the "Configuring IP on Ethernetdcc Interfaces for the In-Band Message Channel" section on page 14-15.

Example

The following example shows how to configure 10-Gbps uplink card interfaces:

Switch(config)# interface tengigethernetphy 10/0
Switch(config-if)# cdl defect-indication force hop-endpoint
Switch(config-if)# no shutdown

Displaying the 10-Gbps Uplink Card Interface Configuration

To display the configuration of 10-Gbps uplink card interfaces, use the following EXEC command:

Command
Purpose

show interfaces {tengigethernetphy slot/0[.subinterface] | wavepatch slot/0/port}

Displays the interface configuration.


Example

The following example shows how to display the configuration of a tengigethernetphy interface:

Switch# show interfaces tengigethernetphy 3/0
TenGigEthernetPhy3/0 is up, line protocol is up
Signal quality :Good
laser shut down :Off
Osc physical port :No
Loopback not set
Wavelength used for inband management:No

Configured threshold Group:None
CDL HEC error count:0
Number of times SF threshold exceeded:0
Number of times SD threshold exceeded:0
CRC error count:0
Number of times SF threshold exceeded:0
Number of times SD threshold exceeded:0
Code violation and running disparity error count( 64b66b cvrd):0
Number of times SF threshold exceeded:0
Number of times SD threshold exceeded:0

Defect Indication Status :up
Configured Node Behavior :None
Current Node Behavior :Path Terminating
Defect Indication Receive : None
Defect Indication Transmit : None

Total Tx Frames Sent to N/W: 48297
Tx Gen CDL Idle Frame: 2173636535

Rx Frames rcvd from N/W: 0
Rx CRC Errors: 0
Rx HEC Errors: 0
Rx XGMII Errors: 0
Rx IPG drpd pkts: 0
Rx Idle Packets : 1836560218
Rx Oversize Frames : 0
Rx Undersize Frames : 0

Rx SII mismatch drpd data Frames : 0
Rx SII mismatch drpd idle Frames : 1842816773

Last clearing of "show interface" counters never
Hardware is data_enabled_port

The following example shows how to display the configuration of a tengigethernetphy subinterface:

Switch# show interfaces tengigethernetphy 3/0.4
TenGigEthernetPhy3/0.4 is up, line protocol is up

Tx Frames Sent to N/W: 0
Tx HEC Errors: 0
Tx CRC Errors: 0
Tx QuadPHY sybl Errs: 37831687439
Tx Dropped Frames: 0
Tx Oversize Frames: 0
Tx Undersize Frames: 0
Tx Rcvd Idle Packets: 0

Rx Frames Sent to Clnt: 0
Rx FIFO full drpd pkts: 0
Rx Gen Idle pkt cnt: 0

Last clearing of "show interface" counters never
Hardware is data_enabled_port

About Cross Connections

The client signal follows a path of interface optical cross connections through the Cisco ONS 15530. Figure 9-1 shows an example of cross connections. Knowing the path of a signal through the shelf helps with system management and troubleshooting.

Figure 9-1 Optical Cross Connection Example for Trunk and Uplink Card Interfaces

Configuring Cross Connections

The aggregated signal from the ESCON aggregation cards, 4-port 1-Gbps/2-Gbps FC aggregation cards, and 8-port FC/GE aggregation cards passes through the switch fabric to the 2.5-Gbps ITU trunk card, 10-Gbps ITU trunk card, 10-Gbps ITU tunable trunk card, or the 10-Gbps uplink card. To establish a cross connection through the switch fabric, perform the following steps, beginning in global configuration mode:

Command
Purpose

Switch(config)# connect interface1 interface2

Creates a cross connection between two interfaces through the switch fabric.


Example

The following example shows how to configure a cross connection between an ESCON aggregation card and a 2.5-Gbps ITU trunk card:

Switch(config)# connect portgroup 2/0/0 waveethernetphy 3/0

The following example shows how to configure a cross connection between an ESCON aggregation card and a 10-Gbps ITU trunk card:

Switch(config)# connect portgroup 2/0/0 waveethernetphy 3/0.1

The following example shows how to configure a cross connection between an ESCON aggregation card and a 10-Gbps uplink card:

Switch(config)# connect portgroup 2/0/0 tengigethernetphy 3/0.1

Displaying the Cross Connection Configuration

To display the cross connection configuration, use the following privileged EXEC command:

Command
Purpose

show connect [edge | intermediate [sort-channel | interface interface]]

Displays the signal cross connection configuration through the system.


Examples

The following example shows the cross connections within a system for an ESCON signal:

Switch# show connect
Index Client Intf Trunk Intf Kind C2TStatus T2CliStatus
----- --------------- --------------- ----------- ---------- ---------
15 Port3/0/0 WaveE8/0.1 Provisioned Up Up

The following example shows the cross connections within a system for a transponder signal:

Switch# show connect intermediate
client/ wave wave wdm
wave client patch filter trk channel
------------ ------------ ------- ------ ----- -------
Trans7/0/0 Wave7/0 7/0/0* 0/0/0 0/0 25
7/0/1

About Alarm Thresholds

You can configure thresholds on the 2.5-Gbps ITU trunk card, 10-Gbps ITU trunk card, 10-Gbps ITU tunable trunk card, and 10-Gbps uplink interfaces that issue alarm messages to the system if the thresholds are exceeded.

Every second the monitoring facility updates the counters that correspond to the alarm thresholds. When the signal degrades, or fails entirely, the system issues alarms to the console. These alarms can help isolate failures in the system and in the network. Signal degrade and signal failure are indicators of signal quality based on the signal data stream. Signal degrade is reported when the number of errors reported per second is more than the signal degrade threshold. Signal failure is reported when the number of errors per second is more than the signal failure threshold.

You can configure more than one threshold list on an interface. The threshold lists cannot have overlapping counters so that only one counter is set for the interface. Also, the threshold list name cannot begin with the text string "default" because it is reserved for use by the system.

Configuring Alarm Thresholds

To configure alarm thresholds on the 2.5-Gbps ITU trunk card, 10-Gbps ITU trunk card, 10-Gbps ITU tunable trunk card, and 10-Gbps uplink card interfaces, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# threshold-list name

Switch(config-t-list)#

Creates or selects the threshold list to configure and enters threshold list configuration mode.

Note You cannot modify an existing threshold list if it is associated with an interface.

Step 2 

Switch(config-t-list)# notification-throttle timer seconds

Configures the SNMP notification timer. The default value is 5 seconds. (Optional)

Step 3 

Switch(config-t-list)# threshold name {cvrd | cdl hec | crc | sonet-sdh section cv | tx-crc} {failure | degrade} [index value]

Switch(config-threshold)#

Specifies a threshold type to modify and enters threshold configuration mode.

Step 4 

Switch(config-threshold)# value rate value

Specifies the threshold rate value. This value is the negative power of 10 (10-n).

Step 5 

Switch(config-threshold)# description text

Specifies a description of the threshold. The default value is the null string. (Optional)

Step 6 

Switch(config-threshold)# exit

Switch(config-t-list)#

Returns to threshold list configuration mode.

Repeat Step 3 through Step 6 to configure more thresholds in the threshold list.

Step 7 

Switch(config-t-list)# exit

Switch(config)#

Returns to global configuration mode.

Step 8 

Switch(config)# interface interface

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 9 

Switch(config-if)# threshold-group name

Configures the threshold list on the interface.

Table 9-1 lists the threshold error rates in errors per second.

Table 9-1 Threshold Values for Monitored Rates in Errors Per Second 

Rate
10-Gbps CRC
10-Gbps CVRD
10-Gbps CDL HEC
2.5-Gbps CRC
2.5-Gbps CVRD
2.5-Gbps CDL HEC

3

66980248

12,443,900

457901

312396

19,968,416

1628

4

9580636

1,249,438

46765

172090

2,055,776

166

5

995697

124,944

4686

24026

206,176

17

6

99957

10,312

468

2490

20,624

1.7

7

10000

1031

47

250

2,064

0.17

8

1000

103

4.7

25

208

0.017

9

100

10

0.47

2.5

24

0.0017


Example

The following example shows how to create an alarm threshold list and configure that list for 10-Gbps ITU trunk card interfaces:

Switch# configure terminal
Switch(config)# threshold-list cvrd-counters
Switch(config-t-list)# threshold name cvrd degrade
Switch(config-threshold)# value rate 9
Switch(config-threshold)# exit
Switch(config-t-list)# threshold name cvrd failure
Switch(config-threshold)# value rate 7
Switch(config-threshold)# exit
Switch(config-t-list)# exit
Switch(config)# interface waveethernetphy 10/0
Switch(config-if)# threshold-group cvrd-counters

Displaying the Alarm Threshold Configuration

To display the configuration of a threshold list and the threshold group for an interface, use the following EXEC commands:

Command
Purpose

show threshold-list [name]

Displays the threshold group configuration.

show interfaces {waveethernetphy slot/subcard | tengigethernetphy slot/subcard}

Displays the interface configuration.


Examples

The following example shows how to display the configuration of a threshold group:

Switch# show threshold-list cvrd-counters

Threshold List Name: cvrd-counters
Notification throttle timer : 5 (in secs)
Threshold name : CVRD Severity : Degrade
Value : 10e-9
APS Trigger : Not set
Threshold name : CVRD Severity : Failure
Value : 10e-7
APS Trigger : Not set

The following example shows how to display the threshold group information for an interface:

Switch# show interfaces waveethernetphy 10/0
WaveEthernetPhy10/0 is administratively down, line protocol is down
Channel: 3 Frequency: 192.3 Thz Wavelength: 1558.98 nm
Active Wavepatch : Wavepatch10/0/0
Splitter Protected : No
Receive power level : -8.38 dBm
Laser shut down : No
Osc physical port : No
Wavelength used for inband management: No
Loopback not set

Configured threshold Group(s): cvrd-counters
Threshold monitored for: 64b66b cvrd
SF set value: 10e-7 (1031 in 1 secs)
SD set value: 10e-9 (10 in 1 secs)
CDL HEC error count: 0
CRC error count: 0
Code violation and running disparity error count( 64b66b cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0

Defect Indication Status : down
Configured Node Behavior : None
Current Node Behavior : Path Terminating
Defect Indication Receive : FDI-H FDI-E
Defect Indication Transmit : FDI-H FDI-E

MTU Size: 10232 bytes

Total Tx Frames Sent to N/W: 0
Tx Gen CDL Idle Frame: 540367537118

Rx Frames rcvd from N/W: 0
Rx IPG drpd pkts: 0
Rx Idle Packets : 0
Rx Oversize Frames : 0
Rx Undersize Frames : 0

Rx SII mismatch drpd data Frames : 0
Rx SII mismatch drpd idle Frames : 0

Last clearing of "show interface" counters never
Hardware is data_enabled_port

About Patch Connections

Because the mux/demux modules are passive devices, the Cisco ONS 15530 does not detect its optical patch connection configuration. For system management purposes, you must also configure the patch connection configuration using the CLI.

Configuring Patch Connections

To configure patch connections between link cards within the same shelf, use the following global configuration commands:

Command
Purpose

patch wavepatch slot1/subcard1/port1 filter slot2/subcard2/port2

or

patch filter slot1/subcard1/port1 wavepatch slot2/subcard2/port2

Configures the patch connection between a 2.5-Gbps ITU trunk card, 10-Gbps ITU trunk card or 10-Gbps ITU tunable trunk card, and an OADM module.

patch thru slot/subcard1 thru slot/subcard2

Configures the patch connection between two OADM modules.

patch wave slot/subcard oscfilter slot/subcard

or

patch oscfilter slot/subcard wave slot/subcard

Configures the patch connection between the wave interface on the OSC module and the oscfilter interface on the OADM module. This is only required if an OSC module is present.


Note If you correctly patch your cards, patch command configuration is not necessary for the signal to pass from the client to the trunk fiber.

Example

The following example shows how to configure the patch connections between line cards in a shelf with two OSC cards in slot  4, two OADM modules with OSC in slot  0, and a splitter 2.5-Gbps ITU trunk card or 10-Gbps ITU trunk card in slot 3:

Switch# configure terminal
Switch(config)# patch thru 0/0 thru 0/1
Switch(config)# patch wave 4/0 oscfilter 0/0
Switch(config)# patch wave 4/1 oscfilter 0/1
Switch(config)# patch wavepatch 3/0/0 filter 0/0/1
Switch(config)# patch wavepatch 3/0/1 filter 0/1/1

About Performance History Counters

Cisco ONS 15530 supports 15 minute based performance history counters. You can use the performance history counters to track the performance of the Cisco ONS 15530 interfaces.

There are three types of performance history counters: current, 15-minute history, and 24-hour. Cisco ONS 15530 uses these counters to store the performance data for the following time periods:

•The current 15 minutes (using the current counter).

•The last 24 hours (using ninety six 15-minute history counters).

•The previous 1 day (using the 24-hour counter).

When the Cisco ONS 15530 system boots up, a continuously incrementing current counter is started. At the end of 15 minutes, this current counter is converted to a static 15-minute history counter with an interval number 1, and a new current counter is started with an interval number 2.

This process continues for 24 hours, by the end of which, ninety six 15-minute history counters are created. After the creation of the ninety sixth 15-minute history counter, a new 24-hour counter is created along with a current counter that has an interval number 1. The 24-hour counter has the aggregated data of all the ninety six 15-minute history counters.

The 15-minute history counters that are created thereafter overwrite the existing set of ninety six 15-minute history counters, in the order they were created. Again, after the creation of the ninety sixth 15-minute history counter, the contents of the existing 24-hour counter are overwritten with new values. This entire process continues in a cyclic fashion.

Note The performance history counters are reset if you reboot the Cisco ONS 15530 system, insert or remove the line card or SFP online, or change the encapsulation.

The performance history counters synchronize periodically from the primary CPU switch module to the standby CPU switch module enabling the system to preserve the performance data across a CPU switch module switchover.

Note To enable or disable the syncing of the performance history counters to the standby CPU switch module, execute the auto-sync counter interfaces command.

Displaying Performance History Counters

To display the performance history counters, use the following EXEC commands:

Command
Purpose

show performance current [interface]

Displays the current counter for the specified interface1 .

show performance history [interface] [interval number]

Displays the 15-minute history counter for the specified interface and interval number1.

show performance 24-hour [interface]

Displays the 24-hour counter for the specified interface1.

1 If you do not specify the interface or interval number, the performance history counters for all interfaces or interval numbers are displayed.


To clear and reset all performance history counters, use the following EXEC command:

Command
Purpose

clear performance history [interface]

Clears the performance history counters for the specified interface.


Examples

The following example shows how to display the current counter for a waveethernetphy interface of a 2.5-Gbps ITU trunk card:

Switch# show performance current waveethernetphy 8/0
Current 15 minute performance register
--------------------------------------
Interface : WaveEthernetPhy8/0
Interval Number : 26

Elapsed Time(seconds) : 424
Valid Time(seconds) : 424

CDL HEC error count : 0
CRC error count : 0
Code violation and running disparity error count : 0

Tx Frames sent to N/W : 1086166500
Tx Frames rcvd from Client : 16357979
Tx CRC Errors : 0
Tx HEC Errors : 0
Tx QuadPHY sybl Errs : 0
Tx Dropped Frames : 0
Tx Oversize Frames : 0
Tx Undersize Frames : 0
Tx Idle Frames from Fabric : 0
Tx Generated CDL Idle Frames : 1069808521

Rx Frames rcvd from N/W : 1086166510
Rx Dropped Frames : 0
Rx Oversize Frames : 0
Rx Undersize Frames : 0
Rx Total Idle Frames : 1069808517
Rx Dropped CDL Idle Frames : 1069808532

The following example shows how to display the 15-minute history counter for a waveethernetphy interface of a 10-Gbps ITU2 trunk card:

Switch# show performance history waveethernetphy 10/0 70
15 minute performance history register
--------------------------------------
Interface : WaveEthernetPhy10/0
Interval Number : 70

Total Time(seconds) : 900
Valid Time(seconds) : 900

CDL HEC error count : 0
CRC error count : 0
Code violation and running disparity error count : 0

Total Tx Frames Sent to N/W : 3380096397
Tx Gen CDL Idle Frame : 2212796342

Rx Frames rcvd from N/W : 3380096277
Rx IPG drpd pkts : 0
Rx Idle Packets : 2212796286
Rx Oversize Frames : 0
Rx Undersize Frames : 0

Rx SII mismatch drpd data Frames : 0
Rx SII mismatch drpd idle Frames : 2212796336

The following example shows how to display the 24-hour counter for a tengigethernetphy sub interface of a 10-Gbps uplink card:

Switch# show performance 24-hour tengigethernetphy 3/0.4
24 hour performance register
----------------------------
Interface : TenGigEthernetPhy3/0.4

Total Time(seconds) : 86400
Valid Time(seconds) : 86400

Tx Frames Sent to N/W : 57372294124
Tx HEC Errors : 612484
Tx CRC Errors : 183951
Tx QuadPHY sybl Errs : 2602312210
Tx Dropped Frames : 183951
Tx Oversize Frames : 19412
Tx Undersize Frames : 12136
Tx Rcvd Idle Packets : 427671

Rx Frames Sent to Clnt : 57370443917
Rx FIFO full drpd pkts : 0
Rx Gen Idle pkt cnt : 0

hometocprevnextglossaryfeedbacksearchhelp

Posted: Wed Apr 26 03:07:07 PDT 2006
All contents are Copyright © 1992--2006 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.