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

Table Of Contents

Configuring 8-Port FC/GE Aggregation Card Interfaces

About the 8-Port FC/GE Aggregation Card

Protocol Monitoring

Configuring 8-Port FC/GE Aggregation Card Interfaces

Displaying the 8-Port FC/GE Aggregation Card Interface 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


Configuring 8-Port FC/GE Aggregation Card Interfaces

This chapter describes how to configure 8-port Fibre Channel/Gigabit Ethernet aggregation cards on the Cisco ONS 15530. This chapter includes the following sections:

• About the 8-Port FC/GE Aggregation Card

• Configuring 8-Port FC/GE Aggregation Card Interfaces

• 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

Note To ensure the installed Cisco IOS software supports your hardware and provides the software features you wish to use, see the "New and Changed Information" section on page xiii. Also refer to the "Hardware Supported" section and "Feature Set" section of the latest release notes for the Cisco ONS 15530.

About the 8-Port FC/GE Aggregation Card

The 8-port FC/GE aggregation card uses SFP (small form-factor pluggable) optical transceivers to provide up to eight configurable client interfaces. Each interface can be configured in the CLI (command-line interface) for FC (Fibre Channel), FICON (fiber connection), GE (Gigabit Ethernet), or ISC-3 (InterSystem Channel) links compatibility mode traffic.

To configure the 8-port FC/GE aggregation card on the Cisco ONS 15530, perform the following steps:

Step 1 Configure 8-port FC/GE aggregation card interfaces.

Step 2 Configure 2.5-Gbps ITU trunk card interfaces, 10-Gbps ITU 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 (optional; FC and FICON traffic only).

Step 4 Configure cross connections.

Step 5 Configure alarm thresholds (optional).

Note The MTU size in the 8-port FC/GE aggregation card is 10232 bytes.

Note The Cisco IOS software only supports Cisco-certified SFP optics on the 8-port FC/GE aggregation card.

Protocol Monitoring

For GE traffic, the Cisco ONS 15530 monitors the following conditions on the 8-port FC/GE aggregation card:

•CVRD error counts

•Tx/Rx frame counts

•Tx/Rx byte counts

•Tx/Rx CRC errors

•Giant packet counts

•Runt packet counts

•5 minute input/output rates

For FC and FICON traffic, the system monitors the following conditions on the 8-port FC/GE aggregation card:

•CVRD error counts

•Tx/Rx frame counts

•Tx/Rx byte counts

•Rx CRC errors

•Link failures

•Sequence protocol errors

•Invalid transmission words

•5 minute input/output rates

•Loss of Sync

•Loss of Light

For ISC-3 compatibility mode traffic, the system monitors the following conditions on the 8-port FC/GE aggregation card:

•CVRD error counts

•Loss of Light

Support for FC Port Types

The 8-port FC/GE aggregation card supports the following FC port types, with or without the buffer credit distance extension feature enabled:

•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)

Note All of the above port topologies, except for TE_port, are point-to-point in Fibre Channel specifications.

Examples of valid topologies where you can put a Cisco ONS 15530 with an 8-port FC/GE aggregation card in the middle to extend distance include the following:

•E_Port <--> E_Port

•F_Port <--> N_Port

•N_Port <--> N_Port

•B_Port <--> B_Port

•TE_Port <--> TE_Port

Arbitrated loop topology is not supported by the 8-port FC/GE aggregation card. The arbitrated loop port types not supported include:

•NL_port—node loop port

•FL_port—fabric loop port

•EL_port—extension loop port

So any combination of above port types are not supported.

Configuring 8-Port FC/GE Aggregation Card Interfaces

The 8-port FC/GE aggregation card has two types of interfaces: eight gigabitphy interfaces on the client side and four portgroup interfaces on the trunk side.

To configure the 8-port FC/GE aggregation card interfaces, perform the following tasks, starting in global configuration mode:

 
Command
Purpose

Step 1 

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

Switch(config-if)#

Specifies an interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# encapsulation {fibrechannel [ofc {enable | disable}] | ficon [ofc {enable | disable} | gigabitethernet | sysplex isc compatibility}

Configures the interface as either FC, FICON, GE, or ISC-3 compatibility mode. The default mode for OSC is disabled.

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)# laser control forward enable

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

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). For more information on FLC, see the "About Laser Shutdown" section on page 6-14

Step 5 

Switch(config-if)# flow control

Enables buffer credits when the interface is encapsulated for Fibre Channel traffic. The default is disabled. (Optional)

Step 6 

Switch(config-if)# negotiation auto

Enables autonegotiation between the 8-port FC/GE aggregation card and the client equipment when the interface is encapsulated for Gigabit Ethernet traffic. The default is disabled. (Optional)

Note The 8-port FC/GE aggregation card supports end-to-end passthrough of the autonegotiation parameters.

Step 7 

Switch(config-if)# no shutdown

Enables the interface.

Step 8 

Switch(config-if)# exit

Switch(config)#

Returns to global configuration mode.

Repeat Step 1 through Step 8 for the other gigabitphy interfaces on the 8-port FC/GE aggregation card.

Caution If ESCON traffic mixes with GE traffic on a 10-Gbps ITU trunk card, assign flow identifiers to all esconphy interfaces, using either the cdl flow identifier command or the cdl flow identifier reserved command, and enable the interfaces with the no shutdown command.

Example

The following example shows how to configure 8-port FC/GE aggregation card interfaces:

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

Displaying the 8-Port FC/GE Aggregation Card Interface Configuration

To display the configuration of 8-port FC/GE aggregation card interfaces, use the following EXEC command:

Command
Purpose

show interfaces {gigabitphy | portgroup} slot/subcard/port

Displays the interface configuration.


Example

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

Switch# show interfaces gigabitphy 2/0/0
GigabitPhy2/0/0 is up, line protocol is up
Optical Transceiver:Single Mode
Signal quality:Good
Encapsulation:GigabitEthernet
Time of last "encapsulation" change 00:47:39
Forward laser control:Off
Flow-identifier:20
Loopback not set

Configured threshold Group(s):txcrc-sf6
Threshold monitored for:tx-crc
SF set value:10e-6 (994 in 1 secs)
Received Frames:39489
Received Bytes:59233500
Transmit Frames:39489
Transmit Bytes:59233500
Code violation and running disparity error count( 8b10b cvrd):0
RX CRC errors:39489
TX CRC errors:39489
Giant Packets:0
Runt Packets: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
Hardware is gige_fc_phy_port

The following example shows how to display the configuration of a gigabitphy interface configured as FC:

Switch# show interfaces gigabitphy 2/0/1
GigabitPhy2/0/1 is down, line protocol is down
Optical Transceiver:Single Mode
Signal quality:Loss of light
Encapsulation:Fibre channel Rate:1G Ofc:off
flow control:disabled
Time of last "encapsulation" change 00:47:46
Forward laser control:Off
Flow-identifier:21
Loopback not set

Configured threshold Group(s):txcrc-sf3
Threshold monitored for:tx-crc
SF set value:10e-3 (83333 in 1 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
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
Hardware is gige_fc_phy_port

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

Switch# show interfaces portgroup 2/0/0
Portgroup2/0/0 is up, line protocol is up
Received Frames:1472937898
Transmit Frames:1472937897
Giant/Runt Frame count:0
Code violation and running disparity error count(cvrd):30311179128
Number of times SF threshold exceeded:0
CDL HEC error count:0
SII Mismatch error count:0
Hardware is gefc_portgroup

About Latency and Transmit Buffers

The 8-port FC/GE aggregation card adds latency to the transmission of FC, FICON, and ISC traffic depending on the services configured. Table 5-1 shows the various configurations on the transmitting node and the FC, FICON, and ISC latency values, both the time in microseconds and the equivalent distance in kilometers (in parentheses).

Note The latency values shown in Table 5-1 are only valid if flow control is disabled and inactive.

Table 5-1 FC, FICON, and ISC Latency Values for 8-Port FC/GE Aggregation Cards 

Traffic Mix on Transmitting Node
Maximum Added End-to-End Latency1 (Time and Distance)
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

18.8 microseconds
(3.8 km)

 

 

 

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

19.9 microseconds
(4.0 km)

 

 

 

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

 

22.2 microseconds
(4.4 km)

24.8 microseconds
(5.0 km)

36.3 microseconds
(7.3 km)

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

 

27.9 microseconds
(5.6 km)

47.1 microseconds
(9.4 km)

83.6 microseconds
(16.7 km)

FC/FICON/ISC and GE on the same 2.5-Gbps aggregated signal carried over a 10-Gbps ITU trunk card

 

39.2 microseconds
(7.8 km)

77.1 microseconds
(15.4 km)

151.1 microseconds
(30.2 km)

1 The latency values are based on configuration of correct transmit buffer sizes as described in Table 5-2.


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 gigabitphy interface include CRC errors, frame drops, and transmission word errors detected by the receiving FC, FICON, or ISC client node.

Note We strongly recommend configuring port pairs as FC/FICON/ISC only or GE only. Mixing FC, FICON, or ISC and GE in a port pair increases the FC, FICON, or ISC signal latency between the nodes.

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 gigabitphy slot/0/port

Switch(config-if)#

Selects the interface to configure and enters interface configuration mode.

Step 2 

Switch(config-if)# shutdown

Disables the interface.

Step 3 

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

Configures the transmit buffer size. The default value is 256 bytes. The range is 256 to 13824.

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

Step 4 

Switch(config-if)# no shutdown

Enables the interface.

Table 5-2 provides transmit buffer settings for various configurations possible on the remote node.

Table 5-2 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

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

 

768

1792

3712

FC/FICON/ISC and GE on the same 2.50Gbps aggregated signal carried over a 10-Gbps ITU trunk card

 

1280

3584

7296


Note The transmit buffer must be configured correctly for all gigabitphy interfaces encapsulated for FC, FICON, or ISC traffic regardless of the flow controlmode configured on the interfaces.

Example

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

Switch(config)# interface gigabitphy 2/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 gigabitphy slot/0/slot

Displays the interface configuration.


Example

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

Switch# show interfaces gigabitphy 2/0/0
GigabitPhy2/0/0 is up, line protocol is up
Optical Transceiver: Multi-Mode
Signal quality: Good
Encapsulation: GigabitEthernet
Time of last "encapsulation" change 3d18h
Forward laser control: Off
Flow-identifier: 20
Loopback not set
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): 760759
RX CRC errors: 0
TX CRC errors: 0
Giant Packets: 0
Runt Packets: 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
MTU size is 10232 bytes
Hardware is gige_fc_phy_port

About Cross Connections

The client signal follows a path of interface optical 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 Optical Cross Connection Example

Configuring Cross Connections

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

Command
Purpose

Switch(config)# connect interface1 interface2

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


Examples

The following example shows how to configure a cross connection between an 8-port FC/GE aggregation card and a 2.5-Gbps ITU trunk card:

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

The following example shows how to configure a cross connection between an 8-port FC/GE aggregation card and a 10-Gbps ITU trunk card:

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

The following example shows how to configure a cross connection between an 8-port FC/GE aggregation card and a 10-Gbps uplink card:

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

Displaying the Cross Connection Configuration

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

Command
Purpose

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

Displays the signal cross connection configuration through the system.


Examples

The following example shows the cross connections:

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

The following example shows the intermediate cross connections:

Switch# show connect intermediate
client/ wave wave wdm
wave client patch filter trk channel
------------ ------------ ------- ------ ----- -------
Giga2/0/0 TenGE7/0 Giga2/0/1 TenGE7/0

About Alarm Thresholds

You can configure thresholds on the 8-port FC/GE 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 system issues alarms to the console. These alarms can help isolate failures in the system and in the network.

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

Configuring Alarm Thresholds

To configure alarm thresholds on the 8-port FC/GE 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-3 lists the threshold error rates in errors per second for 8-port FC/GE signals.

Table 5-3 Threshold Values for Monitored Rates for FC/FICON/GE Signals in Errors Per Second 

Rate
FC/FICON/GE CRC1
FC/FICON/GE CVRD2

3

83333

1244390

4

58235

124944

5

9423

12499

6

994

1250

7

100

125

8

100

12

9

10

1

1 CRC=cyclic redundancy check

2 CVRD= code violation and running disparity error


Note Portgroup interfaces have a default alarm threshold list that raises signal failure alarms for CVRD errors. The default rate value is 5.

Example

The following example shows how to create an alarm threshold list and configure that list for 8-port FC/GE aggregation card interfaces:

Switch# configure terminal
Switch(config)# threshold-list gigabitphy-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 gigabitphy 3/0/0
Switch(config-if)# threshold-group gigabitphy-counters

Displaying the Alarm Threshold Configuration

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

Command
Purpose

show threshold-list [name]

Displays the threshold group configuration.

show interfaces gigabitphy 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 gigabitphy-counters

Threshold List Name: gigabitphy-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 gigabitphy 3/0/0
GigabitPhy3/0/0 is up, line protocol is up
Signal quality: Good
Forward laser control: Off
Configured threshold Group: gigabitphy-counters
Threshold monitored for: CRC
SF set value: 10e-7 (20 in 1 secs)
SD set value: 10e-9 (1 in 5 secs)
Received Frames: 0
Transmit Frames: 0
Code violation and running disparity error count(cvrd): 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
CRC error count: 0
Number of times SF threshold exceeded: 0
Number of times SD threshold exceeded: 0
Egress Packet Sequence error count: 0
Egress Packet Indicated error count: 0
5 minute input rate 0 bits/sec, 0 frames/sec
5 minute output rate 0 bits/sec, 0 frames/sec
Hardware is escon_phy_port

hometocprevnextglossaryfeedbacksearchhelp

Posted: Tue May 17 23:47:44 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.