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

Table Of Contents

Configuring 4-Port 1-Gbps/2-Gbps FC Aggregation Card Interfaces

About the 4-Port 1-Gbps/2-Gbps FC Aggregation Card

Protocol Monitoring

Support for FC Port Types

Basic Configuration of the 4-port 1-Gbps/2-Gbps FC Aggregation Card Interfaces

Displaying the 4-port 1-Gbps/2-Gbps FC Aggregation Card Interface Configuration

About Forward Laser Control

Configuring Forward Laser Control

Displaying Forward Laser Control Configuration

About Latency and Transmit Buffers

Configuring Transmit Buffer Size for FC, FICON, and ISC

Displaying Transmit Buffer Configuration

About Cross-Connections

Configuring Cross-Connections

Displaying the Cross-Connection Configuration

About Alarm Thresholds

Configuring Alarm Thresholds

Displaying the Alarm Threshold Configuration

About Buffer Credit Flow Control

Configuring Buffer Credit Flow Control

Displaying the Buffer Credit Flow Control Configuration

About End-to-End Speed Negotiation

Configuring End-to-End Speed Negotiation

Displaying the End-to-End Speed Negotiation Configuration

About Oversubscription

Guidelines for Configuring Oversubscription

Configuring Oversubscription

Displaying Bandwidth Utilization of Oversubscribed Portgroup

About Superportgroup

Configuring Superportgroup

Displaying Bandwidth Utilization of Superportgroup

About Performance History Counters

Displaying Performance History Counters


Configuring 4-Port 1-Gbps/2-Gbps FC Aggregation Card Interfaces

This chapter describes how to configure 4-port 1-Gbps/2-Gbps FC (Fibre Channel) aggregation cards on the Cisco ONS 15530. This chapter includes the following sections:

• About the 4-Port 1-Gbps/2-Gbps FC Aggregation Card

• Basic Configuration of the 4-port 1-Gbps/2-Gbps FC Aggregation Card Interfaces

• About Forward Laser Control

• Configuring Forward Laser Control

• About Latency and Transmit Buffers

• Configuring Transmit Buffer Size for FC, FICON, and ISC

• About Cross-Connections

• Configuring Cross-Connections

• About Alarm Thresholds

• Configuring Alarm Thresholds

• About Buffer Credit Flow Control

• Configuring Buffer Credit Flow Control

• About End-to-End Speed Negotiation

• Configuring End-to-End Speed Negotiation

• About Oversubscription

• Configuring Oversubscription

• About Superportgroup

• Configuring Superportgroup

• About Performance History Counters

• Displaying Performance History Counters

About the 4-Port 1-Gbps/2-Gbps FC Aggregation Card

The 4-port 1-Gbps/2-Gbps FC aggregation card uses up to four small form-factor pluggable (SFP) optical transceivers to support client traffic. Each client interface can be configured using the command-line interface (CLI) for FC, fibre connection (FICON), or InterSystem Channel (ISC) links traffic at a 1-Gbps or 2-Gbps rate.

The 4-port 1-Gbps/2-Gbps FC aggregation card connects four 2.5-Gbps electric signals, or portgroup interfaces, to the switch module. The client port data streams must be mapped to one of these portgroup interfaces using the CLI. Only two 1-Gbps client interfaces or one 2-Gbps client interface can be mapped into a single portgroup interface.

The signal on the portgroup interfaces connects through the backplane and the CPU switch module to a 2.5-Gbps ITU trunk card, a 10-Gbps ITU trunk card, a 10-Gbps ITU tunable trunk card, or a 10-Gbps uplink card, where the signal is converted to/from an ITU channel. The cross-connections are configured using the CLI.

The following table summarizes the compatibility of the key features of 4-port 1-Gbps/2-Gbps FC aggregation cards.

Table 5-1 Compatibility of the Features of 4-Port 1-Gbps/2-Gbps Aggregation Cards 

Speed Negotiation

Speed Negotiation

           

Oversubscription

Yes

Oversubscription

         

Superportgroup

Yes

See footnote1

Superportgroup

 

OFC2

No

Yes

Yes

OFC

 

FLC3

See footnote4

Yes

Yes

No

FLC

 

Flow Control

Yes

Yes

Yes

Yes

Yes

Flow Control

 

Transmit buffer

Yes

No

No

Yes

Yes

See footnote5

Transmit Buffer

1 Both these features cannot be simultaneously enabled on the same card. However, when a portgroup is connected to a superportgroup, oversubscription is implicitly enabled on that portgroup.

2 OFC = Open Fibre Control.

3 FLC = Forward Laser Control.

4 Implicitly enabled.

5 The transmit buffer is used only during link initialization; thereafter, flow control is used.


The 1-Gbps client traffic from a 4-port 1-Gbps/2-Gbps FC aggregation card is interoperable with the 8-port FC/GE aggregation card at the other end of the network. Any 1-Gbps FC, FICON, or ISC client signal can be transmitted between a 4-port 1-Gbps/2-Gbps FC aggregation card and an 8-port FC/GE aggregation card.

The following table compares the key features of the FC aggregation cards supported on Cisco ONS 15530:

Table 5-2 Comparison of the Features of FC Aggregation Cards Supported on Cisco ONS 15530

Features
8-port FC/GE aggregation card
4-port 1-Gbps/2-Gbps FC Aggregation Card
   
With Functional versions prior to 1.20, and Cisco IOS versions prior to 12.2(29)SV
With Functional version 1.20 or later, and Cisco IOS version 12.2(29)SV or later

Speed Negotiation

No1

No1

Yes

Oversubscription

No

No

Yes

Superportgroup

No

No

Yes

Forward Laser Control

Yes

Yes

Yes

Open Fibre Control

Yes

Yes

Yes

Flow Control

Yes

Yes

Yes

1 End-to-end speed negotiation can be configured on the client devices connected to the aggregation card. However, the card will not participate in speed negotiation and will operate only at the configured speed.


Note Open Fibre Control, speed negotiation, oversubscription, and superportgroup features are not supported with ISC encapsulation. Forward Laser Control is implicitly enabled with ISC.

To configure the 4-port 1-Gbps/2-Gbps FC aggregation card on the Cisco ONS 15530, perform the following steps:

Step 1 Configure 4-port 1-Gbps/2-Gbps FC aggregation card interfaces.

Step 2 Configure 2.5-Gbps ITU trunk card interfaces, 10-Gbps ITU trunk card interfaces, 10-Gbps ITU tunable trunk card interfaces, or 10-Gbps uplink card interfaces as described in Chapter 9, "Configuring Trunk and Uplink Card Interfaces."

Step 3 Configure the transmission buffer size.

Step 4 Configure cross connections.

Step 5 Configure alarm thresholds (optional).

Step 6 Configure end-to-end speed negotiation (optional).

Step 7 Configure oversubscription (optional).

Step 8 Configure superportgroup (optional).

Note The Cisco IOS software only supports Cisco-certified SFP optics on the 4-port 1-Gbps/2-Gbps FC aggregation card.

Protocol Monitoring

For FC and FICON traffic, the node monitors the following conditions on the 4-port 1-Gbps/2-Gbps FC aggregation card:

•CVRD error counts

•Invalid transmission words

•Tx frame counts

•Rx frame counts

•Tx byte counts

•Rx byte counts

•Tx CRC errors

•Rx CRC errors

•Link failures

•Sequence protocol errors

•5 minute input/output rates

•Loss of Sync

•Loss of Light

For ISC traffic, the node monitors the following conditions on the 4-port 1-Gbps/2-Gbps FC aggregation card:

•CVRD error counts

•Loss of Light

•Tx frame counts

•Rx frame counts

•Frame rates (5 minute)

•Loss of Sync

Support for FC Port Types

The 4-port 1-Gbps/2-Gbps FC aggregation card supports the following FC port types:

•B_port—bridge port

•E_port—expansion port

•F_port—fabric port

•N_port—node port

•TE_port—trunking E_port (Cisco MDS 9000 Family systems only)

Examples of valid topologies supported by the 4-port 1-Gbps/2-Gbps FC aggregation card include the following:

•E_Port <--> E_Port

•F_Port <--> N_Port

•N_Port <--> N_Port

•B_Port <--> B_Port

•TE_Port <--> TE_Port

The 4-port 1-Gbps/2-Gbps FC aggregation card does not support arbitrated loop topology, including the following port types:

•NL_port—node loop port

•FL_port—fabric loop port

•EL_port—extension loop port

Any combination of these port types is not supported.

The 4-port 1-Gbps/2-Gbps FC aggregation card supports only the standard R_RDY based buffer-to-buffer flow control that is described in the FC-FS and FC-SW-2 specifications. For more information, refer to the "About Buffer Credit Flow Control" section.

Basic Configuration of the 4-port 1-Gbps/2-Gbps FC Aggregation Card Interfaces

The 4-port 1-Gbps/2-Gbps FC aggregation card has three types of interfaces: four twogigabitphy interfaces on the client side, four portgroup interfaces on the trunk side, and one superportgroup interface (virtual) on the trunk side.

To bring up the FC link, perform the following steps (starting in global configuration mode) on the twogigabitphy interfaces:

 
Command
Purpose

Step 1 

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

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# encapsulation {fibrechannel {1g | 2g| auto} [ofc {enable | disable}] | ficon {1g | 2g| auto} [ofc {enable | disable}] | sysplex isc {compatibility | peer {1g | 2g}}}

Configures the interface as either FC, FICON, or ISC. The default is fibrechannel 1g.

Note Auto encapsulation is not supported with OFC.

Step 3 

Switch(config-if)# cdl flow identifier number

Specifies the flow identifier for the signal. The range is 0 to 174.

Step 4 

Switch(config-if)# portgroup number

or

Switch(config-if)# superportgroup

Maps the interface to one of four portgroup interfaces.

Maps the interface to the superportgroup interface.

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 twogigabitphy interfaces on the 4-port 1-Gbps/2-Gbps FC aggregation card.

Note If oversubscription is not enabled, only two 1-Gbps client interfaces or one 2-Gbps client interface can be mapped into a single portgroup.

Note Each end of the link must be configured for the same rate (1g, 2g, or auto).

Note All configurations on the twogigabitphy interface must be similar to the peer twogigabitphy interface. The portgroup mappings can, however, be different.

Note If the superportgroup is configured on a twogigabitphy interface, it has to be configured on the peer twogigabitphy interface as well.

Example

The following example shows how to configure 4-port 1-Gbps/2-Gbps FC aggregation card interfaces:

Switch(config)# interface twogigabitphy 3/0/0
Switch(config-if)# encapsulation fibrechannel 1g
Switch(config-if)# cdl flow identifier 30
Switch(config-if)# portgroup 0
Switch(config-if)# no shutdown
Switch(config-if)# exit

Displaying the 4-port 1-Gbps/2-Gbps FC Aggregation Card Interface Configuration

To display the configuration of 4-port 1-Gbps/2-Gbps FC aggregation card interfaces, use the following EXEC command:

Command
Purpose

show interfaces {twogigabitphy | portgroup | superportgroup} slot/subcard/port

Displays the interface configuration.


Example

The following example shows how to display the configuration of a twogigabitphy interface configured as a 2-Gbps FC port:

Switch# show interfaces twogigabitphy 3/0/0
TwoGigabitPhy3/0/0 is up, line protocol is up
Optical Transceiver:Single Mode
Signal quality:Good
Encapsulation:Fibre channel Rate:1G Ofc:off
flow control:disabled
Time of last "encapsulation" change 08:03:20
Portgroup mapping:2
Forward laser control:Off
Flow-identifier:90
Loopback not set
Protection Mode:None Interface state:Active
Threshold monitored for:None
Received Frames:0
Received Bytes:0
Transmit Frames:0
Transmit Bytes:0
Code violation and running disparity error count( 8b10b cvrd):0
RX CRC errors:0
TX CRC errors:0
Link Failures:0
Loss of Sync:0
Loss of Light:0
Sequence Protocol Error count:0
Invalid Transmission Word count:88
5 minute input rate 0 bits/sec, 0 frames/sec
5 minute output rate 0 bits/sec, 0 frames/sec
Transmit Buffer size is 256 bytes

Last clearing of "show interface" counters 08:03:40
Hardware is 2gfc_phy_port

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

Switch# show interfaces portgroup 9/0/0
Portgroup9/0/0 is up, line protocol is up
Received Frames: 127294406966
Transmit Frames: 127183980670
Oversized Frames: 0
Undersized Frames: 0
CRC error count: 0
Code violation and running disparity error count(cvrd): 0
Number of times SF threshold exceeded: 0
Secondary fabric CVRD count: 0
CDL HEC error count: 0
SII Mismatch error count: 0
Oversubscription: Disabled
Hardware is 2gfc_portgroup

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

Switch# show interfaces superPortgroup 9/0/0
SuperPortgroup9/0/0 is up, line protocol is up

--------------------
PortGrp Intf FlowID
------------ ------
Portg9/0/0 100
Portg9/0/1 101
--------------------

---------------------------------------------------
Client Intf Max Subrate Cfgd Input Rate B/W
Rate Rx (MB/s) (MB/s) Share
------------ ---- ------------ ---------- -----
TwoGi9/0/0 212 150 90 yes
TwoGi9/0/1 106 106 60 yes
TwoGi9/0/2 212 200 15 yes
---------------------------------------------------

Total Bandwidth: 500 MB/s Free Bandwidth: 44 MB/s
Configured Bandwidth: 456 MB/s
Hardware is 2gfc_superportgroup

About Forward Laser Control

When loss of light occurs on a receive interface (client, trunk, or intermediate) in a DWDM network, the corresponding transmitting laser on the far end of the network continues to function and may send unreliable information to the client. Forward Laser Control (FLC) provides a means to quickly shut down a transmitting laser when a receive signal failure occurs and pass the fault to the client devices. Loss of light can result from a failure in upstream optics or in the client equipment, a laser shutdown on an upstream node in the network, or a receiver failure in the module. For more information on FLC, see the "About Forward Laser Control" section on page 8-13.

Configuring Forward Laser Control

To configure FLC on the twogigabitphy interfaces, perform the following steps, starting in global configuration mode:

 
Command
Purpose

Step 1 

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

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# laser control forward enable

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

You must enable FLC at both ends for FLC to take effect when loss of light occurs. This card uses end-to-end FLC (E2EFLC).

Step 3 

Switch(config-if)# exit

Switch(config)#

Returns to global configuration mode.

Displaying Forward Laser Control Configuration

To display the forward laser control configuration, use the following EXEC command:

Command
Purpose

show interfaces twogigabitphy slot/0/slot

Displays the interface configuration.


Example

The following example shows how to display the FLC configuration:

Switch# show interfaces twogigabitphy 9/0/0
TwoGigabitPhy9/0/0 is up, line protocol is up
Optical Transceiver: Single Mode
Signal quality: Good
Encapsulation: Fibre channel Rate: 2G Ofc: off
flow control: disabled
Time of last "encapsulation" change 1d02h
Portgroup mapping: 0
>> Forward laser control: On
Flow-identifier: 90
Loopback not set
Protection Mode: None Interface state: Active
Threshold monitored for: None
Received Frames: 0
Received Bytes: 0
Transmit Frames: 0
Transmit Bytes: 0
Code violation and running disparity error count( 8b10b cvrd): 0
RX CRC errors: 0
TX CRC errors: 0
Link Failures: 0
Loss of Sync: 1
Loss of Light: 1
Sequence Protocol Error count: 0
Invalid Transmission Word count: 0
5 minute input rate 0 bits/sec, 0 frames/sec
5 minute output rate 0 bits/sec, 0 frames/sec
Transmit Buffer size is 512 bytes

Last clearing of "show interface" counters 1d02h
Hardware is 2gfc_phy_port

About Latency and Transmit Buffers

The 4-port 1-Gbps/2-Gbps FC aggregation card adds latency to the transmission of FC, FICON, and ISC traffic depending on the services configured. Table 5-3 and Table 5-4 show the latency value for the various configurations on the transmitting node.

Table 5-3 1-Gbps FC, FICON, and ISC Latency Values for 4-Port 1-Gbps/2-Gbps Aggregation Cards 

Traffic Mix on Transmitting Node
Maximum Added End-to-End Latency
No GE
1518-Byte GE Packets
4470-Byte GE Packets
10,232-Byte GE Packets

FC/FICON/ISC only on the 2.5-Gbps aggregated signal carried over a 2.5-Gbps ITU trunk card

12.7 µs

     

FC/FICON/ISC only on a 2.5-Gbps aggregated signal carried over a 10-Gbps ITU trunk card or a 10-Gbps ITU tunable trunk card

12.1 µs

     

FC/FICON/ISC only on a 2.5-Gbps aggregated signal mixed with GE on the same 10-Gbps ITU trunk card or a 10-Gbps ITU tunable trunk card

 

13.5 µs

16.8 µs

26.2 µs


Note For FC and FICON the latency values shown in Table 5-3 and Table 5-4 are only valid when flow control is inactive and oversubscription is disabled.

Table 5-4 2-Gbps FC, FICON, and ISC Latency Values for 4-Port 1-Gbps/2-Gbps Aggregation Cards 

Traffic Mix on Transmitting Node
Maximum Added End-to-End Latency
No GE
1518-Byte GE Packets
4470-Byte GE Packets
10,232-Byte GE Packets

FC/FICON/ISC only on the 2.5-Gbps aggregated signal carried over a 2.5-Gbps ITU trunk card

10.6 µs

 

 

 

FC/FICON/ISC only on a 2.5-Gbps aggregated signal carried over a 10-Gbps ITU trunk card

9.9 µs

 

 

 

FC/FICON/ISC only on a 2.5-Gbps aggregated signal mixed with GE on the same 10-Gbps ITU trunk card

 

12.1 µs

15.4 µs

25.1 µs


The transmit buffer on the receiving node compensates for the packet jitter effects due to service multiplexing on the trunk. You must correctly configure the size of this transmit buffer to ensure that no buffer underflow or overflow occurs. Symptoms of an improperly configured transmit buffer on the FC or FICON port include CRC errors, frame drops, and transmission word errors detected by the receiving FC or FICON client node.

Configuring Transmit Buffer Size for FC, FICON, and ISC

To configure the transmit buffer on the receiving node, perform the following steps, starting in global configuration mode:

 
Command
Purpose

Step 1 

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

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# tx-buffer size bytes

Configures the transmit buffer size. The default value for 1-Gbps traffic is 256 bytes. The default value for 2-Gbps traffic is 512 bytes. The range is 256 to 13824.

Caution Issuing the tx-buffer size command might momentarily disrupt traffic through the interface.

Note The transmit buffer must be configured for all twogigabitphy interfaces encapsulated for FC, FICON, and ISC ports regardless of the flow-control mode configured on the FC and FICON ports. You need not configure the transmit buffer size for the twogigabitphy interfaces that are connected to an oversubscribed portgroup.

Table 5-5 and Table 5-6 provide transmit buffer settings for various configurations possible on the remote node.

Table 5-5 1-Gbps FC, FICON, and ISC Transmit Buffer Settings 

Traffic Mix on the Transmitting Node
Transmit Buffer Size (in Bytes) on the Receiving Node
No GE
1518-Byte GE Packets
4470-Byte GE Packets
10,232-Byte GE Packets

FC/FICON/ISC only on the 2.5-Gbps aggregated signal carried over a 2.5-Gbps ITU trunk card

256 (default)

 

 

 

FC/FICON/ISC only on a 2.5-Gbps aggregated signal carried over a 10-Gbps ITU trunk card

256 (default)

 

 

 

FC/FICON/ISC only on a 2.5-Gbps aggregated signal mixed with GE on the same 10-Gbps ITU trunk card

 

384

640

1280


Table 5-6 2-Gbps FC, FICON, and ISC Transmit Buffer Settings 

Traffic Mix on the Transmitting Node
Transmit Buffer Size (in Bytes) on the Receiving Node
No GE
1518-Byte GE Packets
4470-Byte GE Packets
10,232-Byte GE Packets

FC/FICON/ISC only on the 2.5-Gbps aggregated signal carried over a 2.5-Gbps ITU trunk card

512 (default)

 

 

 

FC/FICON/ISC only on a 2.5-Gbps aggregated signal carried over a 10-Gbps ITU trunk card

512 (default)

 

 

 

FC/FICON/ISC only on a 2.5-Gbps aggregated signal mixed with GE on the same 10-Gbps ITU trunk card

 

768

1280

2560


Example

The following example shows how to configure the transmit buffer size on the receiving node:

Switch(config)# interface twogigabitphy 3/0/0
Switch(config-if)# shutdown
Switch(config-if)# tx-buffer size 1280
Switch(config-if)# no shutdown

Displaying Transmit Buffer Configuration

To display the transmit buffer configuration, use the following EXEC command:

Command
Purpose

show interfaces twogigabitphy slot/0/slot

Displays the interface configuration.


Example

The following example shows how to display the transmit buffer configuration:

Switch# show interfaces twogigabitphy 3/0/0
TwoGigabitPhy3/0/0 is up, line protocol is up
Optical Transceiver:Single Mode
Signal quality:Good
Encapsulation:Fibre channel Rate:1G Ofc:off
flow control:disabled
Time of last "encapsulation" change 08:03:20
Portgroup mapping:2
Forward laser control:Off
Flow-identifier:90
Loopback not set
Protection Mode:None Interface state:Active
Threshold monitored for:None
Received Frames:0
Received Bytes:0
Transmit Frames:0
Transmit Bytes:0
Code violation and running disparity error count( 8b10b cvrd):0
RX CRC errors:0
TX CRC errors:0
Link Failures:0
Loss of Sync:0
Loss of Light:0
Sequence Protocol Error count:0
Invalid Transmission Word count:88
5 minute input rate 0 bits/sec, 0 frames/sec
5 minute output rate 0 bits/sec, 0 frames/sec
>>Transmit Buffer size is 256 bytes
Last clearing of "show interface" counters 08:03:40
Hardware is 2gfc_phy_port

About Cross-Connections

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

Figure 5-1 Cross-Connection Example for 4-Port 1-Gbps/2-Gbps FC Aggregation Card Interfaces

Configuring Cross-Connections

The aggregated signals from 4-port 1-Gbps/2-Gbps FC aggregation cards pass through the switch module 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 module, 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 module.


Note All portgroups that are part of a superportgroup must be cross-connected to the same trunk card.

Examples

The following example shows how to configure a cross-connection between a 4-port 1-Gbps/2-Gbps FC aggregation card and a 2.5-Gbps ITU trunk card:

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

The following example shows how to configure a cross-connection between a 4-port 1-Gbps/2-Gbps FC aggregation card and a 10-Gbps ITU trunk card:

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

The following example shows how to configure a cross-connection between a 4-port 1-Gbps/2-Gbps FC aggregation card and a 10-Gbps uplink card:

Switch(config)# connect portgroup 3/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:

Switch# show connect
Index Client Intf Trunk Intf Kind C2TStatus T2CliStatus
----- --------------- --------------- ----------- ---------- ---------
6 Portg3/0/1 WaveE9/0.1 Provisioned Up Up

The following example shows the intermediate cross-connections:

Switch# show connect intermediate
client/ wave wave wdm
wave client patch filter trk channel
------------ ------------ ------- ------ ----- -------
Gigab4/0/3 WaveE2/0 2/0/0* 0/0/0 0/0 25
2/0/1 0/1/0 0/1 25

TwoGi9/0/0 WaveE2/0 2/0/0* 0/0/0 0/0 25
2/0/1 0/1/0 0/1 25

TwoGi9/0/1 WaveE2/0 2/0/0* 0/0/0 0/0 25
2/0/1 0/1/0 0/1 25

TwoGi9/0/2 WaveE2/0 2/0/0* 0/0/0 0/0 25
2/0/1 0/1/0 0/1 25

TwoGi9/0/3 WaveE2/0 2/0/0* 0/0/0 0/0 25
2/0/1 0/1/0 0/1 25

About Alarm Thresholds

You can configure thresholds on the 4-port 1-Gbps/2-Gbps FC aggregation card 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 node issues alarms to the console. These alarms can help isolate failures in the node 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; only one counter can be set for the interface. Also, the threshold list name cannot begin with the text string "default" because that string is reserved for use by the node.

Configuring Alarm Thresholds

To configure alarm thresholds on the 4-port 1-Gbps/2-Gbps FC aggregation 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 5-7 lists the threshold error rates in errors per second for Fiber Channel 1G and 2G signals.

Table 5-7 Threshold Values for Monitored Rates for Fiber Channel 1G and 2G Signals in Errors Per Second 

Rate
FC/FICON 1G Tx-CRC
FC/FICON/ISC 1G CVRD
FC/FICON 2G Tx-CRC
FC/FICON/ISC 2G CVRD

3

83333

110000

166666

220000

4

58235

11000

116470

22000

5

9423

1100

18846

2200

6

994

110

1988

220

7

100

11

200

22

8

10

1.1

20

2.2

9

1

0.11

2

0.22


Example

The following example shows how to create an alarm threshold list and configure that list for 4-port 1-Gbps/2-Gbps FC aggregation card interfaces:

Switch# configure terminal
Switch(config)# threshold-list twogigabitphy-counters
Switch(config-t-list)# threshold name tx-crc degrade
Switch(config-threshold)# value rate 9
Switch(config-threshold)# exit
Switch(config-t-list)# threshold name tx-crc failure
Switch(config-threshold)# value rate 7
Switch(config-threshold)# exit
Switch(config-t-list)# exit
Switch(config)# interface twogigabitphy 3/0/0
Switch(config-if)# threshold-group twogigabitphy-counters

Displaying the Alarm Threshold Configuration

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

Command
Purpose

show threshold-list [name]

Displays the threshold group configuration.

show interfaces twogigabitphy slot/subcard/slot

Displays the interface configuration.


Examples

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

Switch# show threshold-list twogigabitphy-counters

Threshold List Name: twogigabitphy-counters
Notification throttle timer : 5 (in secs)
Threshold name : CRC Severity : Degrade
Value : 10e-9
APS Trigger : Not set
Threshold name : CRC 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 twogigabitphy 3/0/0
TwoGigabitPhy3/0/0 is up, line protocol is up
Optical Transceiver:Single Mode
Signal quality:Good
Encapsulation:Fibre channel Rate:1G Ofc:off
flow control:disabled
Time of last "encapsulation" change 08:14:03
Portgroup mapping:2
Forward laser control:Off
Flow-identifier:90
Loopback not set
Protection Mode:None Interface state:Active
>>Configured threshold Group(s):twogigabitphy-counters
Threshold monitored for:tx-crc
SF set value:10e-7 (100 in 1 secs)
SD set value:10e-9 (10 in 10 secs)
Received Frames:0
Received Bytes:0
Transmit Frames:0
Transmit Bytes:0
Code violation and running disparity error count( 8b10b cvrd):0
RX CRC errors:0
TX CRC errors:0
Link Failures:0
Loss of Sync:0
Loss of Light:0
Sequence Protocol Error count:0
Invalid Transmission Word count:88
5 minute input rate 0 bits/sec, 0 frames/sec
5 minute output rate 0 bits/sec, 0 frames/sec
Transmit Buffer size is 256 bytes

Last clearing of "show interface" counters 08:14:23
Hardware is 2gfc_phy_port

About Buffer Credit Flow Control

Buffer credit flow control increases the throughput of FC links over the DWDM network. Flow control requires that FC devices receive acknowledgement for transmitted frames before more frames can be transmitted. Although a certain number of outstanding transmitted frames is allowed (buffer credits), throughput can drop considerably as the distance grows. By configuring flow control on the twogigabitphy interfaces of the 4-port 1-Gbps/2-Gbps FC aggregation card, FC throughput can be maintained across much larger distances.

The 4-port 1-Gbps/2-Gbps FC aggregation card supports only the standard R_RDY based buffer-to-buffer flow control that is described in the FC-FS and FC-SW-2 specifications. Vendor specific flow control mechanisms are not supported. If client devices use vendor specific flow control, flow control on the 4-port 1-Gbps/2-Gbps FC aggregation card will become inactive. The traffic will, however, continue to flow without any errors. In such a case, you will not be able to utilize the 4-port 1-Gbps/2-Gbps FC aggregation card's FC distance extension capabilities. If flow control is disabled at the 4-port 1-Gbps/2-Gbps FC aggregation card, you can connect clients that use either standard or vendor specific flow control.

The 4-port 1-Gbps/2-Gbps FC aggregation card supports both symmetric and asymmetric modes of buffer credit flow control. In the symmetric mode, the FC client devices at both ends transmit frame bursts of sizes up to the lower value of the buffer credit capabilities advertised by them at FC login. In the asymmetric mode, the FC client at each end transmits frame bursts up to the full size of the peer FC client's credit buffers. Most FC devices operate in symmetric mode.

Asymmetric flow control mode is the default in 4-port 1-Gbps/2-Gbps FC aggregation cards with Functional version 1.20 or later and Cisco IOS version 12.2(29)SV or later. The 4-port 1-Gbps/2-Gbps FC aggregation card operates in the symmetric flow control mode only if any of the following conditions are met:

•Symmetric flow control is configured on the 4-port 1-Gbps/2-Gbps FC aggregation card at the local or remote end.

•The peer 4-port 1-Gbps/2-Gbps FC aggregation card is operating in the symmetric flow control mode.

•The 8-port Fibre Channel/Gigabit Ethernet aggregation card with Functional version up to 2.29 is used at the remote end.

Symmetric flow control is the default in 4-port 1-Gbps/2-Gbps FC aggregation cards with Functional versions prior to 1.20 and Cisco IOS versions prior to 12.2(29)SV. However, the asymmetric mode is selected if you enable asymmetric flow control at the local end while the remote node is operating in asymmetric mode. If the client at either end is operating in symmetric mode, flow control will operate in symmetric mode irrespective of the specified configuration.

If oversubscription is enabled, you must ensure that the buffer-to-buffer credit value configured on the client devices does not exceed the oversubscription memory credit size (211 for 1 Gbps and 939 for 2 Gbps).

Configuring Buffer Credit Flow Control

To configure buffer credit flow control on 4-port 1-Gbps/2-Gbps FC aggregation card twogigabitphy interfaces, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

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

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# flow control [asymmetric | symmetric]

Enables flow control on the interface and sets the flow control mode to asymmetric or symmetric.

Step 3 

Switch(config-if)# exit

Switch(config)#

Returns to global configuration mode.

Asymmetric flow control must be used only if the following conditions are met:

–4-port 1-Gbps/2-Gbps FC aggregation cards with Functional versions prior to 1.20 are present on at least one side.

–The number of credits supported by the FC clients are different.

–The FC clients support asymmetric flow control.

Example

The following example shows how to configure buffer credit flow control on a 4-port 1-Gbps/2-Gbps FC aggregation card twogigabitphy interface:

Switch# configure terminal
Switch(config)# interface twogigabitphy 3/0/0
Switch(config-if)# encapsulation fibrechannel 1g
Switch(config-if)# cdl flow identifier 30
Switch(config-if)# portgroup 0
Switch(config)# tx-buffer size 256
Switch(config-if)# flow control
Switch(config-if)# no shutdown
Switch(config-if)# exit

Displaying the Buffer Credit Flow Control Configuration

To display the buffer credit flow control configuration on 4-port 1-Gbps/2-Gbps FC aggregation card twogigabitphy interfaces, use the following EXEC command:

Command
Purpose

show interfaces twogigabitphy slot/subcard/port

Displays the interface configuration.


Examples

The following example shows how to display the configuration of a twogigabitphy interface configured with flow control:

Switch# show interfaces twogigabitphy 9/0/3
TwoGigabitPhy9/0/3 is up, line protocol is up
Optical Transceiver: Single Mode
Signal quality: Good
Encapsulation: Fibre channel Rate: 1G Ofc: off
>> flow control(symmetric): enabled, and active
Time of last "encapsulation" change 1d02h
Portgroup mapping: 3
>> Local Login Credits: 210 Remote Login Credits: 210
Forward laser control: Off
Flow-identifier: 93
Loopback not set
Protection Mode: None Interface state: Active
Threshold monitored for: None
Received Frames: 155803
Received Bytes: 334600660
Transmit Frames: 158006
Transmit Bytes: 339331172
Code violation and running disparity error count( 8b10b cvrd): 0
RX CRC errors: 0
TX CRC errors: 0
Link Failures: 0
Loss of Sync: 0
Loss of Light: 0
Sequence Protocol Error count: 0
Invalid Transmission Word count: 0
5 minute input rate 0 bits/sec, 0 frames/sec
5 minute output rate 0 bits/sec, 0 frames/sec
Transmit Buffer size is 256 bytes

Last clearing of "show interface" counters 00:00:17
Hardware is 2gfc_phy_port

About End-to-End Speed Negotiation

The 4-port 1-Gbps/2-Gbps FC aggregation card supports end-to-end speed negotiation. This allows client devices connected through the 4 port 1-Gbps/2-Gbps FC aggregation card to negotiate a common maximum transmission speed automatically.

When speed negotiation is enabled, the link will negotiate to a mutually supported maximum transmission speed on all interfaces (the twogigabitphy interface, the client interface connected directly to it, the peer twogigabitphy interface, and the peer client interface) in the link. For instance, if both the client interfaces are configured at 2 Gbps, the negotiated link speed will also be 2 Gbps. However, if one or both of these interfaces is configured at 1 Gbps, the link speed will be 1 Gbps. If any of the interfaces is configured at a fixed speed, all interfaces in the link will communicate at that speed. If different interfaces are configured at different fixed speeds, the link will not be able to negotiate a common speed.

Figure 5-2 End-to-End Speed Negotiation

To enable speed negotiation on a twogigabitphy interface, configure encapsulation on the interface and set the speed to auto.

Note For proper functioning of end-to-end speed negotiation, symmetrical speed configuration must be enabled on the twogigabitphy interfaces at both ends.

To enable end-to-end speed negotiation, the following requirements must be met:

•4-port 1-Gbps/2-Gbps FC aggregation cards with Functional version 1.20 or later must be used at both ends.

•The Cisco IOS version is 12.2(29)SV or later.

•10-Gbps ITU2 cards with Functional version 2.31 or later are installed.

Configuring End-to-End Speed Negotiation

To configure end-to-end speed negotiation, perform the following steps, starting in global configuration mode:

 
Command
Purpose

Step 1 

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

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# encapsulation {fibrechannel | ficon} auto

Configures the interface as FC or FICON with automatic speed negotiation.

Step 3 

Switch(config-if)# exit

Switch(config)#

Returns to global configuration mode.

Example

The following example shows how to configure end-to-end speed negotiation on a 4-port 1-Gbps/2-Gbps FC aggregation card twogigabitphy interface:

Switch# configure terminal
Switch(config)# interface twogigabitphy 7/0/0
Switch(config-if)# encapsulation fibrechannel auto
Switch(config-if)# exit

Note Speed negotiation is not supported for ISC.

Note OFC cannot be configured with auto encapsulation.

Displaying the End-to-End Speed Negotiation Configuration

To display the end-to-end speed negotiation configuration on 4-port 1-Gbps/2-Gbps FC aggregation card twogigabitphy interfaces, use the following EXEC command:

Command
Purpose

show interfaces twogigabitphy slot/subcard/port

Displays the interface configuration.


The following table describes the values of the Rate field in the output of the show interfaces command:

Value
Description

NEG

Speed negotiation is in progress.

N1G

Speed has been negotiated to 1 Gbps.

N2G

Speed has been negotiated to 2 Gbps.


Example

The following example shows how to display the configuration of a twogigabitphy interface configured with end-to-end speed negotiation:

Switch# show interfaces twogigabitphy 9/0/3
TwoGigabitPhy9/0/3 is up, line protocol is up
Optical Transceiver: Single Mode
Signal quality: Good
>> Encapsulation: Fibre channel Rate: N2G Ofc: off
flow control(symmetric): enabled, and active
Time of last "encapsulation" change 00:00:52
Portgroup mapping: 3
Local Login Credits: 16 Remote Login Credits: 16
Forward laser control: On
Flow-identifier: 93
Loopback not set
Protection Mode: None Interface state: Active
Threshold monitored for: None
Received Frames: 1796271
Received Bytes: 2127476584
Transmit Frames: 1799846
Transmit Bytes: 2030633756
Code violation and running disparity error count( 8b10b cvrd): 0
RX CRC errors: 0
TX CRC errors: 0
Link Failures: 0
Loss of Sync: 0
Loss of Light: 0
Sequence Protocol Error count: 0
Invalid Transmission Word count: 0
5 minute input rate 47222000 bits/sec, 5241 frames/sec
5 minute output rate 44776000 bits/sec, 4965 frames/sec
Transmit Buffer size is 2580 bytes

Last clearing of "show interface" counters 00:00:32
Hardware is 2gfc_phy_port

About Oversubscription

You can oversubscribe the 4-port 1-Gbps/2-Gbps FC aggregation card to efficiently utilize unused portgroup bandwidth. Oversubscription is supported only in the FC/FICON mode and not in the ISC mode.

Typically, to transfer 2-Gbps FC data at full rate over a 2.5-Gbps portgroup, only 84% of the portgroup bandwidth is utilized. Similarly, to transfer 1-Gbps FC data at full rate over a 2.5 Gbps portgroup, only 42% of the portgroup bandwidth is utilized. By oversubscribing the 4-port 1-Gbps/2-Gbps FC aggregation card, you can utilize the unused bandwidth to transfer FC data. Figure 5-3 shows an example of an oversubscribed portgroup.

Figure 5-3 Oversubscribed Portgroup Example

In most storage applications, the bandwidth used is much less than the configured 1 Gbps or 2 Gbps rate. This unused bandwidth can be used to transfer useful data. If you know the type of the application and its bandwidth utilization, you can minimize bandwidth wastage by allocating only the required bandwidth for each client. The remaining bandwidth can be allocated to other FC clients; thus, each 2.5-Gbps portgroup can be used to its fullest capacity by multiple clients.

To oversubscribe a 4-port 1-Gbps/2-Gbps FC aggregation card, you must configure subrates for every client interface. Subrate is specified in megabytes per second (MBps). For example, to permit full-rate 1-Gbps or 2-Gbps FC traffic over an oversubscribed portgroup, you must specify 106 MBps or 212 MBps as the subrate for that client interface. By default, for each client interface, subrate is set to 1 MBps.

Subrates can be configured only for those client interfaces that are already connected to an oversubscribed portgroup or superportgroup. A superportgroup is a set of oversubscribed portgroups. For more information on superportgroups, see "About Superportgroup" section.

By default, unused bandwidth in the portgroup will be used by other clients based on demand. For example, if two 2-Gbps FC ports are each configured at a 125 MBps subrate, and one of them is utilizing only 75 MBps of the available bandwidth, the other port can use 1 to 175 MBps of the portgroup bandwidth. If you do not want to permit the sharing of bandwidth, you can lock the bandwidth of a client interface. When the client bandwidth is locked, it will not share its configured bandwidth with other clients. However, if available, it will borrow bandwidth from other unlocked clients in the same portgroup or superportgroup.

Guidelines for Configuring Oversubscription

•Incorrect subrate configuration can lead to under utilization of the portgroup bandwidth. For example, if you configure three clients to share the bandwidth of a portgroup, and set the subrate for the first client as 25 MBps, the second as 50 MBps, and the third as 75 MBps, then only 150 MBps of the portgroup bandwidth will be used. The remaining 100 MBps of the portgroup bandwidth will not be shared by the client ports. In addition, the total subrates of all the clients in a portgroup must not exceed the portgroup bandwidth.

•To maximize throughput, Cisco recommends that you configure oversubscription along with flow control. Flow control is supported for Class-2, Class-3, and Class-F frames with standard R_RDY based flow control on the FC clients. If flow control is disabled, oversubscription will still be operational, but the optimal throughput may not be attainable.

•For oversubscription to function properly, you must ensure that the buffer-to-buffer credit values on the client devices do not exceed 211 for 1 Gbps and 939 for 2 Gbps.

•If a client has Class-4 traffic in addition to other clients carrying different classes of traffic over the same oversubscribed portgroup, Cisco recommends that you configure full subrate with locked bandwidth for the client carrying Class-4 traffic, and share the remaining bandwidth among other clients.

•You can oversubscribe a 4-port 1-Gbps/2-Gbps FC aggregation card only if the following conditions are met:

–The 4-port 1-Gbps/2-Gbps FC aggregation cards at both ends are configured to support oversubscription and the Functional version is 1.20 or later.

–The Cisco IOS version is 12.2(29)SV or later.

–10-Gbps ITU2 cards with Functional version 2.31 or later are installed.

–2.5-Gbps trunk cards with Functional version 1.70 or later are installed.

Configuring Oversubscription

To configure oversubscription, first perform the steps described in the "Basic Configuration of the 4-port 1-Gbps/2-Gbps FC Aggregation Card Interfaces" section, and then continue with the following steps (beginning in global configuration mode):

 
Command
Purpose

Step 1 

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

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# over-subscription

Configures oversubscription on the interface.

Step 3 

Switch(config-if)# exit

Exits interface configuration mode and returns to global configuration mode.

Step 4 

Switch(config-if)# interface twogigabitphy slot/0/port

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 5 

Switch(config-if)# portgroup number

Maps the interface to one of four portgroup interfaces.

Step 6 

Switch(config-if)# sub-rate rate {lock}

Configures the subrate for the interface. Specify lock if you want to lock the client bandwidth. To unlock it, execute the sub-rate command without the lock attribute.

Step 7 

Switch(config-if)# exit

Switch(config)#

Exits interface configuration mode and returns to global configuration mode.

To move a twogigabitphy client interface from an oversubscribed portgroup to a non-oversubscribed portgroup, perform the following steps:

Step 1 Shutdown the twogigabitphy interfaces at both ends.

Step 2 Disassociate the twogigabitphy interfaces from their respective portgroups at both ends.

Step 3 Associate the new portgroup at both ends.

Step 4 Execute the no shutdown command on the twogigabitphy interfaces at both ends.

To enable or disable oversubscription on a portgroup, perform the following steps:

Step 1 Shutdown the twogigabitphy interfaces at both ends.

Step 2 Enable or disable oversubscription.

Step 3 Execute the no shutdown command on the twogigabitphy interfaces at both ends.

Examples

The following example shows how to enable oversubscription on a 4-port 1-Gbps/2-Gbps FC aggregation card:

Switch# configure terminal
Switch(config)# interface portgroup 7/0/0
Switch(config-if)# over-subscription
Switch(config-if)# exit

The following example shows how to configure the subrate:

Switch(config)# interface twogigabitphy 7/0/0
Switch(config-if)# sub-rate 50
Switch(config-if)# exit

The following example shows how to disable bandwidth sharing:

Switch(config)# interface twogigabitphy 7/0/0
Switch(config-if)# sub-rate 50 lock

Switch(config-if)# exit

Displaying Bandwidth Utilization of Oversubscribed Portgroup

To display the bandwidth utilization of the oversubscribed portgroup, use the following EXEC command:

Command
Purpose

show interfaces portgroup slot/0/port

Displays the interface configuration.


Example

The following example shows how to display the oversubscription configuration and the portgroup bandwidth utilization:

Switch# show interfaces portgroup 9/0/3
Portgroup9/0/3 is up, line protocol is up
Received Frames: 457659558
Transmit Frames: 471666783
Oversized Frames: 0
Undersized Frames: 0
CRC error count: 0
Code violation and running disparity error count(cvrd): 0
Number of times SF threshold exceeded: 0
Secondary fabric CVRD count: 0
CDL HEC error count: 0
SII Mismatch error count: 0
>> Oversubscription: Enabled

-----------------------------------------------------------
Client Intf Max Subrate Cfgd Input Rate B/W FlowID
Rate Rx (MB/s) (MB/s) Share
------------ ---- ------------ ---------- ----- ------
TwoGi9/0/3 212 150 66 yes 93
TwoGi9/0/1 106 100 30 yes 91
-----------------------------------------------------------

Total Bandwidth: 250 MB/s Free Bandwidth: 0 MB/s
Configured Bandwidth: 250 MB/s
Hardware is 2gfc_portgroup

About Superportgroup

The 4-port 1-Gbps/2-Gbps FC aggregation card supports up to four 2.5-Gbps portgroups. You can group two or more of these portgroups to create a superportgroup. A superportgroup enables you to aggregate the unused bandwidth of all the portgroups to form a pool of unused bandwidth, which can be shared by the clients. For example, if you create a superportgroup with four client interfaces, each with a subrate of 187 MBps, then three portgroups (each 250 MBps) will be sufficient. The fourth 2.5 Gbps lane of the trunk card can be used to transport any other type of data such as GigE or ESCON. Figure 5-4 shows an example of a superportgroup.

Figure 5-4 Superportgroup Example

When a portgroup is associated to the superportgroup, oversubscription is automatically enabled on that portgroup. If you disassociate a portgroup from the superportgroup, oversubscription is automatically disabled on that portgroup. Moreover, while superportgroup is configured, oversubscription cannot be enabled on any other portgroup (in the same 4-port 1-Gbps/2-Gbps FC aggregation card) that is not part of the superportgroup. A portgroup that is associated to a superportgroup cannot be connected to any twogigabitphy interfaces.

The portgroups that are part of the superportgroup must be cross-connected to the same trunk card only. The trunk flow identifier will be configured on the look-up table of the ITU2 trunk card. If that flow ID causes a conflict with the other flow IDs programmed in the ITU2 trunk card, the superportgroup cross-connections or the portgroup associations with the superportgroup will be rejected.

Note In a superportgroup, client-to-client mappings are fixed. For instance, port-0 of the 4-port 1-Gbps/2-Gbps FC aggregation card at one end will communicate only with port-0 of the 4-port 1-Gbps/2-Gbps FC aggregation card at the other end.

To configure superportgroup, the following system requirements must be met:

•4-port 1-Gbps/2-Gbps FC aggregation cards with Functional version 1.20 or later are installed at both ends.

•The Cisco IOS version is 12.2(29)SV or later.

•10-Gbps trunk cards with Functional version 2.31 or later are installed.

•Superportgroup is configured at both ends.

Configuring Superportgroup

To configure superportgroup on the 4-port 1-Gbps/2-Gbps FC aggregation card, perform the following steps, beginning in global configuration mode:

 
Command
Purpose

Step 1 

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

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# portgroup portgroup-ID identifier trunk-flow-ID

Associates the portgroup to the superportgroup. The trunk flow identifiers of peer portgroups must match.

Note The cdl flow identifier is not applicable for the twogigabitphy interfaces that are mapped to the superportgroup.

Step 3 

Switch(config-if)# exit

Switch(config)#

Returns to global configuration mode.

Step 4 

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

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 5 

Switch(config-if)# superportgroup

Connects the twogigabitphy interface to the superportgroup.

Step 6 

Switch(config-if)# sub-rate rate

Selects the subrate for the interface.

Step 7 

Switch(config-if)# exit

Switch(config)#

Returns to global configuration mode.

To associate a twogigabitphy interface connected to the superportgroup to any other portgroup, perform the following steps in the given sequence:

Step 1 Shutdown the twogigabitphy interface at both ends.

Step 2 Remove the superportgroup association at both ends.

Step 3 Connect the twogigabitphy interface to any other portgroup at both ends.

Step 4 Execute the no shutdown command on the twogigabitphy interfaces at both ends.

Example

The following example shows how to configure superportgroup on a 4-port 1-Gbps/2-Gbps FC aggregation card:

Switch# configure terminal
Switch(config)# interface superportgroup 4/0/0
Switch(config-if)# portgroup 0 identifier 16
Switch(config-if)# portgroup 1 identifier 17
Switch(config-if)# portgroup 2 identifier 18
Switch(config-if)# exit
Switch(config)# interface twogigabitphy 4/0/0
Switch(config-if)# superportgroup
Switch(config-if)# sub-rate 212 lock
Switch(config-if)# exit
Switch(config)# interface twogigabitphy 4/0/1
Switch(config-if)# superportgroup
Switch(config-if)# sub-rate 212
Switch(config-if)# exit
Switch(config)# interface twogigabitphy 4/0/2
Switch(config-if)# superportgroup
Switch(config-if)# sub-rate 212
Switch(config-if)# exit
Switch(config)# interface twogigabitphy 4/0/3
Switch(config-if)# superportgroup
Switch(config-if)# sub-rate 114
Switch(config-if)# exit

Displaying Bandwidth Utilization of Superportgroup

To display the superportgroup configuration and to check the utilization of the portgroup bandwidth, use the following EXEC commands:

Command
Purpose

show interfaces superportgroup slot/0/0

Displays the interface configuration.


Example

The following example shows how to display the superportgroup configuration and the portgroup bandwidth utilization:

Switch# show interfaces superportgroup 7/0/0
SuperPortgroup4/0/0 is up, line protocol is up

--------------------
PortGrp Intf FlowID
------------ ------
Portg4/0/0 16
Portg4/0/1 17
Portg4/0/2 18
--------------------

---------------------------------------------------
Client Intf Max Subrate Cfgd Input Rate B/W
Rate Rx (MB/s) (MB/s) Share
------------ ---- ------------ ---------- -----
TwoGi4/0/0 212 212 181 no
TwoGi4/0/1 212 212 120 yes
TwoGi4/0/2 212 212 120 yes
TwoGi4/0/3 212 114 84 yes
---------------------------------------------------

Total Bandwidth: 750 MB/s Free Bandwidth: 0 MB/s
Configured Bandwidth: 750 MB/s
Hardware is 2gfc_superportgroup

Switch# show interfaces TwoGigabitPhy 4/0/0
TwoGigabitPhy4/0/0 is up, line protocol is up
Optical Transceiver: Single Mode
Signal quality: Good
Encapsulation: Fibre channel Rate: N2G Ofc: off
Configured Subrate: 212 MB/s Bandwidth Sharing: no
flow control(symmetric): enabled, and active
Time of last "encapsulation" change 00:04:13
>> Portgroup mapping: 0, 1, 2, (SuperPortgroup4/0/0)
Local Login Credits: 16 Remote Login Credits: 16
Forward laser control: On
Loopback not set
Protection Mode: None Interface state: Active

Configured threshold Group(s): bp2
Threshold monitored for: 8b10b cvrd
SF set value: 10e-5 (22149 in 1 secs)
SD set value: 10e-7 (221 in 1 secs)
Threshold monitored for: tx-crc
SF set value: 10e-5 (18846 in 1 secs)
SD set value: 10e-7 (200 in 1 secs)
Received Frames: 6696038
Received Bytes: 7544908504
Transmit Frames: 6696052
Transmit Bytes: 7542196596
Code violation and running disparity error count( 8b10b cvrd): 0
RX CRC errors: 0
TX CRC errors: 0
Link Failures: 0
Loss of Sync: 0
Loss of Light: 0
Sequence Protocol Error count: 0
Invalid Transmission Word count: 0
5 minute input rate 211931000 bits/sec, 23515 frames/sec
5 minute output rate 211854000 bits/sec, 23515 frames/sec
Transmit Buffer size is 512 bytes

Last clearing of "show interface" counters 00:00:59
Hardware is 2gfc_phy_port

Switch# show interfaces Portgroup 4/0/0
Portgroup4/0/0 is up, line protocol is up
Received Frames: 741369086
Transmit Frames: 741246018
Oversized Frames: 0
Undersized Frames: 0
CRC error count: 0
Code violation and running disparity error count(cvrd): 0
Number of times SF threshold exceeded: 0
Secondary fabric CVRD count: 0
CDL HEC error count: 0
SII Mismatch error count: 0
Oversubscription: Enabled, Trunk Flow-identifier: 16

-----------------------------------------------------------
Client Intf Max Subrate Cfgd Input Rate B/W FlowID
Rate Rx (MB/s) (MB/s) Share
------------ ---- ------------ ---------- ----- ------
-----------------------------------------------------------

Total Bandwidth: 250 MB/s Free Bandwidth: 250 MB/s
Configured Bandwidth: 0 MB/s
Hardware is 2gfc_portgroup

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 twogigabitphy interface:

Switch# show performance current twogigabitPhy 4/0/3
Current 15 minute performance register
--------------------------------------
Interface : TwoGigabitPhy4/0/3
Interval Number : 24

Elapsed Time(seconds) : 688
Valid Time(seconds) : 688

Received Frames : 326186915
Received Bytes : 41751926848
Transmit Frames : 326173811
Transmit Bytes : 41750247868
RX CRC : 0
Code violation and running disparity error count : 0
Link Failures : 0
Loss of Sync : 0
Loss of Light : 0
Sequence Protocol Error count : 0
Invalid Transmission Word count : 0

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

Switch# show performance history twoGigabitPhy 4/0/3 75
15 minute performance history register
--------------------------------------
Interface : TwoGigabitPhy4/0/3
Interval Number : 75

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

Received Frames : 424805068
Received Bytes : 54375048280
Transmit Frames : 424805064
Transmit Bytes : 54375048460
RX CRC : 0
Code violation and running disparity error count : 0
Link Failures : 0
Loss of Sync : 0
Loss of Light : 0
Sequence Protocol Error count : 0
Invalid Transmission Word count : 0

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

Switch# show performance 24-hour portgroup 4/0/3
24 hour performance register
----------------------------
Interface : Portgroup4/0/3

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

Transmit Frames : 57372289565
Received Frames : 57372177110
Oversized Frames : 0
Undersized Frames : 2
Code violation and running disparity error count : 4294967295
Secondary fabric CVRD count : 0
CRC error count : 0
CDL HEC error count : 1
SII Mismatch error count : 2

The SII mismatch error count is fetched by the SII mismatch idle frames MIB object, the CRC error count is fetched by the Tx CRC MIB object, the oversized frame count is fetched by the Tx oversize frames MIB object, and the undersized frame count is fetched by the Tx undersize frames MIB object for the portgroup interface of the 4-port 1-Gbps/2-Gbps FC aggregation card.

hometocprevnextglossaryfeedbacksearchhelp

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