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

Table Of Contents

Configuring 8-Port Multi-Service Muxponder Interfaces

About the 8-Port Multi-Service Muxponder

Configuring 8-Port Multi-Service Muxponder Interfaces

Displaying the 8-Port Multi-Service Muxponder Interface Configuration

Configuring IP on Sdcc Interfaces for In-Band Messages

Displaying the Sdcc Interface Configuration

Verifying Connectivity Over the Sdcc Interface

About Alarm Thresholds

Configuring Alarm Thresholds

Displaying the Alarm Threshold Configuration

Configuring Optical Power Thresholds

Configuring Laser Shutdown

Configuring Forward Laser Control

Configuring Laser Safety Control

About Patch Connections

Configuring Patch Connections

About Time Slot Interchange Mapping

Configuring Time Slot Interchange Mapping

Displaying the TSI Map

About Performance History Counters

Displaying Performance History Counters


Configuring 8-Port Multi-Service Muxponder Interfaces

This chapter describes how to configure 8-port multi-service muxponders on the Cisco ONS 15530. This chapter includes the following sections:

• About the 8-Port Multi-Service Muxponder

• Configuring 8-Port Multi-Service Muxponder Interfaces

• About Alarm Thresholds

• Configuring Alarm Thresholds

• Configuring Optical Power Thresholds

• Configuring Laser Shutdown

• About Patch Connections

• Configuring Patch Connections

• About Time Slot Interchange Mapping

• Configuring Time Slot Interchange Mapping

• About Performance History Counters

• Displaying Performance History Counters

About the 8-Port Multi-Service Muxponder

The 8-port multi-service muxponder provides up to eight configurable client interfaces that can transport a mix of protocols among sites in a metropolitan DWDM network. Each interface can be configured from the CLI (command-line interface) for T1, E1, Fast Ethernet, ESCON, SDI, DVB-ASI, Gigabit Ethernet, Fibre Channel, FICON, ITS, SONET OC-3, or SDH STM-1 traffic.

The 8-port multi-service muxponder assigns variable bandwidth using correctly sized STS-n streams for each client protocol and then aggregates the STS-n streams to form a 2.5-Gbps ITS signal. The aggregated signal is demultiplexing in the receive direction. This is achieved using a time slot interchange (TSI) mapping scheme.

Note Although the 8-port multi-service muxponder uses a SONET-like framing structure to aggregate multiple client data streams, it is not SONET compliant on the optical trunk output. The muxponder ITU compliant optical trunk output must be used in an end-to-end configuration and cannot be connected to a SONET/SDH OADM.

The 8-port multi-service muxponder accepts up to eight SFPs for client traffic and supports the following protocols:

•Gigabit Ethernet (1.25 Gbps), copper and optical

•Fiber Channel (1.062 Gbps), optical

•FICON (1.062 Gbps), optical

•DVB-ASI (Digital Video Broadcast-Asynchronous Serial Interface) (270 Mbps), copper

•SDI (Serial Digital Interface) (270 Mbps) and SDTI (350 Mbps), copper

•ESCON (200 MHz), optical

•SONET OC-3 (155 Mbps), optical

•SDH STM-1 (155 Mbps), optical

•Fast Ethernet (125 Mbps), copper and optical

•T1 (1.544 Mbps), copper

•E1 (2.048 Mbps), copper

•ITS (Integrated Trading System)

Each supported client protocol uses a fixed number of STS-1 streams. Table 7-1 shows the bandwidth allocation.

Table 7-1 Bandwidth Allocation for Supported Protocols 

Protocol
Bandwidth (in STS-1 streams)

Gigabit Ethernet (optical and copper)

21

Fibre Channel

18

FICON

18

Fast Ethernet (optical and copper)

3

ESCON

4

SONET OC-3

4

SDH STM-1

4

DVB-ASI

5

SDI

6

T1

1

E1

1

ITS

5


The trunk signal rate is 2.5-Gbps, which translates to 48 STS-1 streams. The STS-1 stream allocation algorithm is a simple top-down search using the first available required number of STS-1 streams.

Based on the order in which client protocols are configured and removed across the various client ports, the resulting TSI mapping in the client-to-trunk transmit direction can vary. The TSI protocol sends the transmit TSI mapping to the remote muxponder where it is used to program the trunk receive TSI maps.

Port-to-port mapping of the 8-port multi-service muxponder and the remote 8-port multi-service muxponder is fixed. For example, port 0 of the local 8-port multi-service muxponder maps to port 0 of remote 8-port multi-service muxponder, port 1 maps to port 1, and so forth.

To configure the 8-port multi-service muxponder on the Cisco ONS 15530, perform the following steps:

Step 1 Specify the protocol encapsulation of the multirate interfaces.

Step 2 Enable forward laser control (optional).

Step 3 Enable the sdcc and wavesonetphy interfaces by issuing the no shutdown command.

Step 4 Specify the laser frequency (optional).

Step 5 Enable the multirate interface by issuing the no shutdown command.

Step 6 Create alarm threshold lists and apply them to the interfaces (optional).

Step 7 Enable the sdcc interface by issuing the no shutdown sdcc interfaces command.

Note The Cisco IOS software only supports Cisco-certified SFP optics on the 8-port multi-service muxponder.

The 8-port multi-service muxponder adds latency to the transmission of traffic, depending upon the encapsulation of the interface. Table 7-2 shows the typical and maximum latency values for the various protocols that may be configured.

Table 7-2 Latency Values for the 8-Port Multi-Service Muxponder 

Protocol
Unidirectional End-to-End Latency with 0 km Fiber
Typical
Maximum

ESCON

10 µs

13 µs

Fibre Channel

4 µs

6 µs

GE1 optical

6 µs

8 µs

FE2 optical

14 µs

17 µs

SDI3

17 µs

20 µs

DVB-ASI4

9 µs

11 µs

1 GE = Gigabit Ethernet

2 FE = Fast Ethernet

3 SDI = Serial Digital Interface

4 DVB-ASI = Digital Video Broadcast Asynchronous Serial Interface


The 8-port FC/GE aggregation card does not supporting arbitrated loop for the following reasons:

•Typical arbitrated devices connect within a distance of 10 km and the 8-port FC/GE aggregation card latency can be as much as 15 km one way (30 km round trip), assuming jumbo GE frames are multiplexed with the FC traffic.

•The maximum timeout value on arbitrated loop devices is 10 ms.

•The primitive sequences generated by the 8-port FC/GE aggregation card, such as NOS (not_operational), OLS (offline), and LR (link reset), have no meaning with arbitrated loop.

Configuring 8-Port Multi-Service Muxponder Interfaces

The 8-port multi-service muxponder has four types of interfaces: multirate interfaces on the client side and wavesonetphy, sdcc, and wavepatch interfaces on the trunk side.

To configure the 8-port multi-service muxponder client side interfaces, perform the following tasks, starting in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface multirate slot/0/port

Switch(config-if)# shutdown

Specifies an interface to configure, enters interface configuration mode, and shuts down the interface.

Step 2 

Switch(config-if)# encapsulation {t1 | e1 | fastethernet {copper1 | optical} | escon | sdi | dvb | gigabitethernet {copper2 | optical} | its | fibrechannel | ficon | sonet oc33 | sdh stm-1}

Configures the interface protocol encapsulation.

Note When changing the interface encapsulation on the 8-port multi-service muxponder you must first shut down the port and remove the old encapsulation.

Step 3 

Switch(config-if)# laser control forward enable

Enables forward laser control on the interface. The default is disabled. (Optional)

Note FLC is enabled by default for ESCON, but not supported on the copper protocols.

Step 4 

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

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

Step 5 

Switch(config-if)# no shutdown

Enables the interface.

Step 6 

Switch(config-if)# exit

Switch(config)#

Returns to global configuration mode.

Repeat Step 1 through Step 6 for the other multirate interfaces on the 8-port multi-service muxponder.

1 Only 100 Mbps full duplex is supported on multirate interfaces encapsulated for copper Fast Ethernet.

2 Only 1000 Mbps full duplex is supported on multirate interfaces encapsulated for copper Gigabit Ethernet.

3 Although the 8-port multi-service muxponder uses a SONET-like framing structure to aggregate multiple client data streams, it is not SONET compliant on the optical trunk output. The muxponder ITU compliant optical trunk output must be used in an end-to-end configuration and cannot be connected to a SONET/SDH OADM.

Example

The following example shows how to configure 8-port multi-service muxponder client side interfaces:

Switch(config)# interface multirate 3/0/0
Switch(config-if)# shutdown
Switch(config-if)# encapsulation fibrechannel
Switch(config-if)# no shutdown
Switch(config-if)# exit

To configure the 8-port multi-service muxponder trunk side interfaces, perform the following tasks, starting in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface wavesonetphy slot/0

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# laser frequency number

Specifies the channel frequency in GHz.

Step 3 

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

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

Step 4 

Switch(config-if)# laser control safety enable

Enables laser safety control on the interface. The default is disabled. (Optional)

Step 5 

Switch(config-if)# no shutdown

Enables the interface.

Step 6 

Switch(config-if)# no laser shutdown

Enables the laser.

Step 7 

Switch(config-if)# no tsi-protocol enable

Disables the TSI protocol. TSI protocol is enabled by default and disabling it is not recommended

Step 8 

Switch(config-if)# exit

Switch(config)#

Returns to global configuration mode.

Step 9 

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

Specifies sdcc interface and enters interface configuration mode.

Step 10 

Switch(config-if)# no shutdown

Enables the sdcc interface so the TSI protocol can exchange STS maps with the remote 8-port multi-service muxponder.

Example

The following example shows how to configure 8-port multi-service muxponder trunk side interfaces:

Switch(config)# interface wavesonetphy 3/0
Switch(config-if)# laser frequency 195600
Switch(config-if)# laser control safety enable
Switch(config-if)# no shutdown
Switch(config-if)# no laser shutdown
Switch(config-if)# exit
Switch(config)# interface sdcc 4/0/0
Switch(config-if)# no shutdown

Displaying the 8-Port Multi-Service Muxponder Interface Configuration

To display the configuration of 8-port multi-service muxponder interfaces, use the following EXEC command:

Command
Purpose

show interfaces {multirate slot/0/port | wavesonetphy slot/0}

Displays the interface configuration.


Example

The following example shows how to display the configuration of a multirate interface configured as GE:

Switch# show interfaces multirate 3/0/0
Multirate3/0/0 is up, line protocol is up
Encapsulation: GigabitEthernet optical
Transceiver type: SFP Transceiver GE/FC
Forward laser control: Off
Signal quality: Good
Data receive error from Remote Client
Loopback not set
Code violation and running disparity error count( 8b10b cvrd): 17820857
Time of last "encapsulation" change 14:01:24
Last clearing of "show interface" counters 14:01:24
Hardware is multirate_client port

Note Code violation and running disparity error count (8b10b cvrd) are not applicable to for T1, E1, ITS, OC-3, STM1, copper Fast Ethernet, copper Gigabit Ethernet, and SDI.

Example

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

Switch# show interfaces wavesonetphy 8/0
waveSonetPhy8/0 is up, line protocol is up
Channel: 27 Frequency: 195.3 Thz Wavelength: 1535.04 nm
Active Wavepatch : Wavepatch3/0/0
Splitter Protected : No
Signal quality : Good
Receive power level : -15.69 dBm
Laser shut down : No
Laser safety control : Off
Wavelength capable for inband management: Yes
Loopback not set
Threshold monitored for: None
Section code violation error count(bip1): 5
Number of errored seconds(es): 1
Number of severely errored seconds(ses): 0
Number of severely errored framing seconds(sefs): 0
Last clearing of "show interface" counters never
Hardware is wave_sonet_phy port

Configuring IP on Sdcc Interfaces for In-Band Messages

Configuring IP on the sdcc interface allows you to use one Cisco ONS 15530 node in the network to monitor other Cisco ONS 15530 nodes in the network that support sdcc interfaces. The 8-port multi-service muxponder supports sdcc for in-band messaging.

IP addressing for the sdcc interfaces can be configured in two ways:

•An IP address for each sdcc interface with each address on a separate subnet.

•An unnumbered address for the Ethernet interfaces that reference another numbered interface.

The IP address of the reference interface is used as the IP packet source address. Use a loopback interface as the reference interface because it is always up. Configure an IP address for each node in a separate subnet. See the About Alarm Thresholds.

Note You can alternatively use the IP address of the NME (network management Ethernet) interface fastethernet (0) for the reference address instead of the loopback interface.

To configure IP on an sdcc interface, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface loopback 1

Switch(config-if)#

Selects the loopback interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# ip address ip-address subnet-mask

Configures IP address and subnet for the interface.

Step 3 

Switch(config-if)# exit

Switch(config)#

Exits interface configuration mode and returns to global configuration mode.

Step 4 

Switch(config)# interface fastethernet 0

Switch(config-if)#

Selects the NME interface to configuration and enters interface configuration mode.

Step 5 

Switch(config-if)# ip address ip-address subnet-mask

Configures IP address and subnet for the interface.

Step 6 

Switch(config-if)# exit

Switch(config)#

Exits interface configuration mode and returns to global configuration mode.

Step 7 

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

Switch(config-if)#

Selects the sdcc interface.

Step 8 

Switch(config-if)# ip unnumbered loopback 1

Configures an unnumbered interface referencing the loopback interface.

Step 9 

Switch(config-if)# exit

Switch(config)#

Exits interface configuration mode and returns to global configuration mode.

Step 10 

Switch(config)# ip route prefix prefix-mask interface

or

Switch(config)# router ospf process-id

Switch(config-router)# network network-address wildcard-mask area area-id

or

Switch(config)# router eigrp as-number

Switch(config-router)# network network-number [network-mask]

or

Switch(config)# router bgp as-number

Switch(config-router)# network network-number [mask network-mask]

Switch(config-router)# neighbor {ip-address | peer-group-name} remote-as number

Configures IP static routes for some or all destinations.

or

Configures OSPF as the routing protocol.


or

Configures EIGRP as the routing protocol.


or

Configures BGP as the routing protocol.

Note For detailed information about configuring routing protocols, refer to the Cisco IOS IP and IP Routing Configuration Guide.

Example

The following example shows how to configure IP on an sdcc interface for in-band messaging.

Node1# configure terminal
Node1(config)# interface loopback 1
Node1(config-if)# ip address 10.1.1.1 255.255.255.0
Node1(config-if)# exit
Node1(config)# interface fastethernet 0
Node1(config-if)# ip address 20.1.1.1 255.255.255.0
Node1(config-if)# exit
Node1(config)# interface sdcc 4/0/0
Node1(config-if)# ip unnumbered loopback 1
Node1(config-if)# exit

Displaying the Sdcc Interface Configuration

To display sdcc interface configuration, use the following EXEC command:

Command
Purpose

show interfaces sdcc slot/subcard/port

Displays the IP sdcc interface configuration.


Example

The following example shows how to display IP on an sdcc interface for in-band messaging:

Switch# show interfaces sdcc 4/0/0
SDCC4/0/0 is up, line protocol is up
This is the message channel interface on waveSonetPhy1/0
Hardware is sonet_dcc port
MTU 1492 bytes, BW 192000 Kbit, DLY 0 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation SNAP, loopback not set
Last input 00:00:02, output never, output hang never
Last clearing of "show interface" counters 19:45:56
Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
58074 packets input, 3389752 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
58076 packets output, 3389868 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out

Verifying Connectivity Over the Sdcc Interface

To verify connectivity over the sdcc interface, use the following EXEC command:

Command
Purpose

telnet ip-address

Connects to another node using the reference IP address for the other node.


Example

The following example shows how to use Telnet to connect from node 1 to node 2 in the ring to another node through the sdcc interface:

Node1# telnet 10.1.2.2
Trying 10.1.2.2 ... Open
Node2> enable
Node2#

About Alarm Thresholds

You can configure thresholds on the 8-port multi-service muxponder interfaces that issue alarm messages to the system if the thresholds are exceeded. On the trunk side interfaces, optical thresholds for receive power can be monitored. The trunk side interface also has the capability to monitor the section BIP (bit interleaved parity) errors (B1).

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 that is reserved for use by the system.

Configuring Alarm Thresholds

To configure alarm thresholds on the 8-port multi-service muxponder 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)# threshold name {cdl | crc | cvrd | sonet-sdh | tx-crc} {failure | degrade} [index value]

Switch(config-threshold)#

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

Step 3 

Switch(config-threshold)#value rate value

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

Step 4 

Switch(config-threshold)# description text

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

Step 5 

Switch(config-threshold)# exit

Switch(config-t-list)#

Returns to threshold list configuration mode.

Repeat Step 2 through Step 5 to configure more thresholds in the threshold list.

Step 6 

Switch(config-t-list)# exit

Switch(config)#

Returns to global configuration mode.

Step 7 

Switch(config)# interface wavesonetphy slot/0

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 8 

Switch(config-if)# threshold-group name

Configures the threshold list on the interface.

Table 7-3 lists the threshold error rates in errors per second for 8-port Multiservice Muxponder signals.

Table 7-3 Threshold Values for Monitored Rates for Muxponder Signals in Errors Per Second 

Rate
Muxponder Interface

3

32000

4

31987

5

17296

6

2394

7

248

8

25

9

2.5


Example

The following example shows how to create an alarm threshold list and configure that list for 8-port multi-service muxponder interfaces:

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

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 wave slot/subcard

Displays the interface configuration.


Examples

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

Switch# show threshold-list bip

Threshold List Name: bip
Notification throttle timer : 5 (in secs)
Threshold name : bip : Degrade
Value : 10e-9
APS Trigger : Not set
Threshold name : bip : 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 wavesonetphy 3/0
waveSonetPhy3/0 is up, line protocol is up
Channel:29 Frequency:195.6 Thz Wavelength:1532.68 nm
Active Wavepatch :Wavepatch1/0/0
Splitter Protected :No
Signal quality :Good
Receive power level :-16.49 dBm
Laser shut down :No
Laser safety control :On
Wavelength capable for inband management:Yes
Loopback not set

Configured threshold Group(s):bip
Threshold monitored for:bip
SF set value:10e-7 (248 in 1 secs)
SD set value:10e-9 (248 in 100 secs)
Section code violation error count(bip1):0
Number of errored seconds(es):0
Number of severely errored seconds(ses):0
Number of severely errored framing seconds(sefs):0
Number of times SF threshold exceeded:0
Number of times SD threshold exceeded:0
Last clearing of "show interface" counters 20:03:49
Hardware is wave_sonet_phy port

Configuring Optical Power Thresholds

You can configure thresholds on the wavepatch interfaces that issue alarm messages to the system if the thresholds are exceeded. On the trunk side interfaces, optical thresholds for receive power can be monitored.

Optical power thresholds provide a means of monitoring the receive signal power. Four types of thresholds are provided:

•Low alarm

•Low warning

•High warning

•High alarm

When a threshold is crossed, the system sends a message to the console.

Note The default values for the optical power receive thresholds are sufficient for most network configurations.

To configure optical receive power threshold for wavepatch interfaces on an 8-port multi-service muxponder, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface wavepatch slot/subcard/port

Switch(config-if)#

Selects the wavepatch interface to configure and enters interface configuration mode.

Step 2 

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

Specifies the optical power threshold value in units of 0.1 dBm.

Examples

The following example shows how to configure optical power thresholds for wavepatch interfaces on an 8-port multi-service muxponder:

Switch(config)# interface wavepatch 5/0/0
Switch(config-if)# optical threshold power receive high warning 7 severity major

Displaying Optical Power Threshold Configuration

To display the optical power thresholds for a wavepatch interface, use the following EXEC command:

Command
Purpose

show interfaces wavepatch slot/subcard/port

Displays interface information.


Example

The following example shows how to display the optical power threshold configuration for an interface:

Switch# show interfaces wavepatch 4/0/0
Wavepatch4/0/0 is up, line protocol is up
Receiver power level: -16.00 dBm

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

Configuring Laser Shutdown

The 8-port multi-service muxponder supports automatic laser shutdown (ALS) on the wavesonetphy interface and forward laser control (FLC) on the multirate interface. If ALS is enabled, a Loss of Signal detected on the wavesonetphy interface automatically shuts the trunk transmit laser off. When FLC is enabled on a multirate interface and the peer client interface detects a Loss of Light or Loss of Sync condition, the transmit laser on the local 8-port multi-service muxponder interface is shut down.

This sections describes how to configure forward laser control and laser safety control on the Cisco ONS 15530 8-port multi-service muxponder interfaces.

The trunk laser on the 8-port multi-service muxponder can be turned off by issuing the laser shutdown command on the wavesonetphy interface. Issuing the laser shutdown command stops all data and control traffic.

Note FLC is not supported on T1, E1, SDI, DVI-ASI, copper FE, or copper GE.

Note FLC is triggered on OFE, OC-3, STM1, and ITS by a Loss of Light condition. On OGE, FC, FICON, and ESCON it is triggered by a Loss of Light, Loss of Sync, or Loss of Lock condition.

Configuring Forward Laser Control

To configure forward laser control for the multirate interfaces on an 8-port multi-service muxponder, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface multirate slot/subcard/port

Switch(config-if)#

Selects the transparent interface to configure and enters interface configuration mode.

Step 2 

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

Configures forward laser control on the interface. The default state is disabled.

If FLC is enabled on a multirate interface the laser will be brought down when loss of light or loss of synchronization occur on the peer multirate interface even if FLC is not enabled there. This card uses end-to-end FLC (E2EFLC).

For more information, see the "About Laser Shutdown" section on page 8-13.

Step 3 

Switch(config-if)# exit

Returns to global configuration mode.

Note FLC is only applicable to optical protocols, copper protocols are not supported. FLC is disable by default for all protocols except ESCON, which is enabled by default.

Examples

The following example shows how to configure forward laser control for the multirate interfaces on an 8-port multi-service muxponder:

Switch(config)# interface multirate 5/0/0
Switch(config-if)# laser control forward enable
Switch(config-if)# exit

Displaying the Forward Laser Control Configuration

To display the forward laser control configuration of a transparent or wave interface, use the following EXEC command:

Command
Purpose

show interfaces multirate slot/subcard/port

Displays interface information.


Example

The following example shows how to display the forward laser control configuration for an interface:

Switch# show interfaces multirate 5/0/0
Multirate5/0/0 is up, line protocol is up
Encapsulation: GigabitEthernet optical
Transceiver type: SFP Transceiver GE/FC
Forward laser control: On
Signal quality: Good
Data receive error from Remote Client
Loopback not set
Code violation and running disparity error count( 8b10b cvrd): 17820857
Time of last "encapsulation" change 14:01:24
Last clearing of "show interface" counters 14:01:24
Hardware is multirate_client port

Configuring Laser Safety Control

To configure laser safety control (LSC) on a wavesonetphy interface, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Switch(config)# interface wavesonetphy slot/subcard}

Switch(config-if)#

Selects the wave interface to configure and enters interface configuration mode.

Step 2 

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

Enables or disables laser safety control.

Note LSC is disabled by default.

Example

The following example shows how to configure laser safety control on a wavesonetphy interface:

Switch(config)# interface wavesonetphy 8/0
Switch(config-if)# laser control safety enable

Displaying the Laser Safety Control Configuration

To display the laser safety control configuration of a wavesonetphy interface, use the following EXEC command:

Command
Purpose

show interfaces wavesonetphy slot/subcard

Displays interface information.


Example

The following example shows how to display the laser safety control configuration for an interface:

Switch# show interfaces wavesonetphy 10/0
waveSonetPhy10/0 is up, line protocol is up
Channel: 27 Frequency: 195.3 Thz Wavelength: 1535.04 nm
Active Wavepatch : Wavepatch3/0/0
Splitter Protected : No
Signal quality : Good
Receive power level : -15.69 dBm
Laser shut down : No
Laser safety control : On
Wavelength capable for inband management: Yes
Loopback not set
Threshold monitored for: None
Section code violation error count(bip1): 5
Number of errored seconds(es): 1
Number of severely errored seconds(ses): 0
Number of severely errored framing seconds(sefs): 0
Last clearing of "show interface" counters never
Hardware is wave_sonet_phy 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

Configures the patch connection between an 8-port multi-service muxponder and an OADM module.


Note If you correctly patch your cards, then the 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 the 8-port multi-service muxponder trunk side interface and the OADM module:

Switch# configure terminal
Switch(config)# patch wavepatch 3/0/0 filter 0/0/1

About Time Slot Interchange Mapping

The 8-port multi-service muxponder uses a time slot interchange (TSI) mapping scheme to aggregate STS-n data streams into one outgoing STS-48 stream. Sets of transmit and receive TSI tables are used to configure the various protocols into the STS-48 stream and to demultiplex the incoming STS-48 stream. This ongoing process requires constant updating of the transmit and receive TSI tables. This is accomplished by transmitting the local transmit TSI map over the sdcc interface to the peer 8-port multi-service muxponder where a receive TSI map is generated, allowing the incoming STS-48 stream to be demultiplexed.

Each supported client protocol uses a fixed number of STS-1 streams. Table 7-1 shows the bandwidth allocation.

The trunk signal rate is 2.5-Gbps, which translates to 48 STS-1 streams. The STS-1 stream allocation algorithm is a simple top-down search using the first available required number of STS-1 streams.

Based on the order in which client protocols are configured and removed across the various client ports, the resulting TSI mapping in the client-to-trunk transmit direction can vary. The TSI protocol sends the transmit TSI mapping to the remote muxponder where it is used to program the trunk receive TSI maps.

Note The port-to-port mapping on the 8-port multi-service muxponder is static. For example, port 0 on the local muxponder maps to port 0 on the remote muxponder, port 1 on the local muxponder maps to port 1 on the remote muxponder, and so on.

Configuring Time Slot Interchange Mapping

TSI mapping on the 8-port multi-service muxponder interfaces is enabled by default. To disable it, issue the no tsi-protocol command on the desired wavesonetphy interface.

Note If the TSI protocol is disabled, the user must manually ensure that the local and remote TSI maps are the same.

Displaying the TSI Map

To display the TSI map of a wavesonetphy interface, use the following EXEC command:

Command
Purpose

show tsi number

Displays interface information.


Example

The following example shows how to display TSI information. (See Table 7-4 for field descriptions.)

Switch# show tsi 1
Port Local Peer Error Trunk STS Map
Encap Encap Transmit Receive

Card: 1, TSI Ver: 1, DCC: SDCC1/0/0, TSI-Protocol: Enabled

0. CFE CFE - 00 00 00 00 00 07 00 00 00 00 00 07
1. CFE CFE - 00 00 00 00 00 38 00 00 00 00 00 38
2. CFE CFE - 00 00 00 00 01 C0 00 00 00 00 01 C0
3. None None -
4. None None -
5. None None -
6. None None -
7. None None -
Available STS= 39
------------------------------

Card: 9, TSI Ver: 1, DCC: SDCC9/0/0, TSI-Protocol: Enabled

  0. T1 T1 - 00 00 00 00 00 01 00 00 00 00 00 01
1. FC1 FC1 - 00 FF FE 00 00 0E 00 00 00 07 FF FE
2. T1 T1 - 00 00 00 00 00 01 00 00 00 00 00 01
3. CFE CFE - 07 00 00 00 00 00 00 00 00 38 00 00
4. E1 E1 - 00 00 00 00 00 01 00 00 00 00 00 01
5. CGE CGE - 00 00 01 FF FF F0 07 FF FF C0 00 00
6. T1 ESCON M 00 00 00 00 00 01 78 00 00 00 00 00
7. None None -
Available STS= 47
------------------------------

The following concepts are shown by the muxponder in slot 9:

•Fibre Channel is configured on port 1 (multirate 9/0/1 interface) on the local and remote muxponders. The Trunk STS Transmit field shows that 18 STS-1 (F+F+F+E+E = 4+4+4+3+3) streams are used for this interface. The exact STS-1 streams used are 2 through 5 and 25 through 40.

The Trunk STS Receive field shows that the STS-1 streams 2 to 19 on the incoming STS-48 signal carry client data from the remote node for this port. A similar explanation can be extended to port 3 (multirate 9/0/3) and port 5 (multirate 9/0/5).

•As shown by ports 0, 2, and 4, all the ports with T1 and E1 encapsulation use the same STS-1 stream. In this example, the first STS-1 stream on both the local and remote muxponders is used.

•If the configured local protocol encapsulation differs from the configured protocol on the remote port, the Error field indicates this as M, which indicates protocol mismatch.

Table 7-4 show tsi Field Descriptions 

Field
Description

Port

Shows the port number.

Local Encap

Shows the protocol encapsulation of the local port.

Remote Encap

Shows the protocol encapsulation of the remote port.

Error

Shows the error state. An M value indicates a protocol mismatch.

Trunk STS Map Transmit

Shows the hexadecimal bit map for the STS usage for the STS-48 signal transmitted to the trunk.

For each port this field shows the STS-1 streams used to transmit the client data from the port to the trunk. This field is displayed in hexadecimal format. The 48 bits represent the 48 STS-1 streams. A value one (1) for a particular STS-1 stream indicates that it is currently used by the corresponding port.

Trunk STS Map Receive

Shows the hexadecimal bit map for the STS usage for the STS-48 signal received from the trunk.

For each port this field shows the STS-1 streams used to transmit the client data from the trunk to the port. This field is displayed in hexadecimal format. The 48 bits represent the 48 STS-1 streams. A value one (1) for a particular STS-1 stream indicates that it is currently used by the corresponding port.

Card:

Shows the slot number in the shelf.

TSI Ver:

Shows the TSI version.

DCC:

Shows the DCC interface identifier.

Available STS=

Shows the number of STS-1 streams available.


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.


Performance history counters are supported only for the ESCON, 1-Gbps FC, optical, Gigabit Ethernet, 1-Gbps FICON, and DVB encapsulations on the multirate interface.

Examples

The following example shows how to display the current counter for a multirate interface:

Switch# show performance current multirate 3/0/5
Current 15 minute performance register
--------------------------------------
Interface : Multirate3/0/5
Interval Number : 45

Elapsed Time(seconds) : 849
Valid Time(seconds) : 849

Code violation and running disparity error count : 0

The following example shows how to display the 15-minute history counter for a multirate interface:

Switch# show performance history multirate 3/0/5 30
15 minute performance history register
--------------------------------------
Interface : Multirate3/0/5
Interval Number : 30

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

Code violation and running disparity error count : 0

The following example shows how to display the 24-hour counter for a multirate interface:

Switch# sh performance 24-hour multirate 3/0/5
24 hour performance register
----------------------------
Interface : Multirate3/0/5

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

Code violation and running disparity error count : 0

hometocprevnextglossaryfeedbacksearchhelp

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