Page 1 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883...
Page 2 Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com...
Page 3: Table Of Contents
Maximum NPIV Limit Extended Credits N Port Virtualization FlexAttach C H A P T E R 3 Configuring Interfaces Finding Feature Information Feature History for Interfaces Information About Interfaces Interface Description Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 4 Disabling the Bit Error Rate Threshold SFP Transmitter Types Portguard Port Level Portguard Port Monitor Portguard Port Monitor Warning Threshold Port Monitor Check Interval Port Group Monitor Interface Types Management Interfaces VSAN Interfaces Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 5 Configuring the Check Interval Configuring a Port Monitor Policy Activating a Port Monitor Policy Configuring Port Monitor Portguard Configuring Port Group Monitor Enabling a Port Group Monitor Configuring a Port Group Monitor Policy Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 6 Task Flow for Migrating Interfaces from Shared Mode to Dedicated Mode Task Flow for Migrating Interfaces from Dedicated Mode to Shared Mode Configuring Port Speed Configuring FEC Configuring Rate Mode Disabling Restrictions on Oversubscription Ratios Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 7 48-Port 16-Gbps Fibre Channel Module Buffer-to-Buffer Credit Buffers Buffer-to-Buffer Credit Buffers for Fabric Switches Cisco MDS 9396S Fabric Switch Buffer-to-Buffer Credit Buffers Cisco MDS 9250i and Cisco MDS 9148S Fabric Switch Buffer-to-Buffer Credit Buffers Extended Buffer-to-Buffer Credits Buffer-to-Buffer Credit Recovery...
Page 8 Configuring the Congestion Drop Timeout Value for FCoE Configuring Pause Drop Timeout for FCoE Configuring the Congestion Drop Timeout Value for Fibre Channel Configuring the No-Credit Frame Timeout Value for Fibre Channel Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x viii...
Page 9 Trunking Misconfiguration Examples Default Settings Configuring Trunking Enabling the Cisco Trunking and Channeling Protocols Enabling the F Port Trunking and Channeling Protocol Configuring Trunk Mode Configuring an Allowed-Active List of VSANs Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 10 Valid and Invalid PortChannel Examples Configuring PortChannels Configuring PortChannels Using the Wizard Creating a PortChannel Configuring the PortChannel Mode Deleting PortChannels Adding an Interface to a PortChannel Adding a Range of Ports to a PortChannel Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 11 NPV Traffic Management Guidelines DPVM Configuration Guidelines NPV and Port Security Configuration Guidelines Connecting an NPIV-Enabled Cisco MDS Fabric Switch Configuring N Port Virtualization Enabling N Port Identifier Virtualization Configuring NPV Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 12 Information About Port Tracking Guidelines and Limitations Default Settings Configuring Port Tracking Enabling Port Tracking Information About Configuring Linked Ports Binding a Tracked Port Operationally Information About Tracking Multiple Ports Tracking Multiple Ports Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 13 Contents Information About Monitoring Ports in a VSAN Monitoring Ports in a VSAN Information AboutForceful Shutdown Forcefully Shutting Down a Tracked Port Verifying Port Tracking Configuration Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x xiii...
Page 14 Contents Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 15: P R E F A C E Preface
Communications, Services, and Additional Information, on page xvi Preface This preface describes the audience, organization of, and conventions used in the Cisco MDS 9000 Series Configuration Guides. It also provides information on how to obtain related documentation, and contains the...
Page 16: Related Documentation
Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071. Related Documentation The documentation set for the Cisco MDS 9000 Series Switches includes the following documents. Release Notes http://www.cisco.com/c/en/us/support/storage-networking/mds-9000-nx-os-san-os-software/ products-release-notes-list.html...
Page 17 Cisco Bug Search Tool Cisco Bug Search Tool (BST) is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. BST provides you with detailed defect information about your products and software.
Page 18 Preface Preface Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x xviii...
Page 19: New And Changed Information
New and Changed Information • Change Summary, on page 2 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 20: Change Summary
Fibre Channel. Avoidance, Isolation, on page 129 Port Monitor The link connecting a core switch to a Cisco NPV switch 8.1(1) Configuring should be treated as an Inter-Switch Link (ISL) (core port) in Interfaces, the port monitor. Previously, core ports were included as...
Page 21 Isolation—Port monitor has a new portguard option to allow the categorization of a device as slow, so that it can have all the traffic flowing to the device routed to the slow virtual link. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 22 New and Changed Information Change Summary Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 23 Fibre Channel Port Rate Limiting, on page 8 • Maximum NPIV Limit, on page 9 • Extended Credits, on page 10 • N Port Virtualization, on page 11 • FlexAttach, on page 12 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 24: Interface Overview
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 25: Trunks And Portchannels
Trunks and PortChannels Trunks and PortChannels Trunking, also known as VSAN trunking, is a feature specific to switches in the Cisco MDS 9000 Series. Trunking enables interconnect ports to transmit and receive frames in more than one VSAN, over the same physical link.
Page 26: Fibre Channel Port Rate Limiting
Fibre Channel Port Rate Limiting Fibre Channel Port Rate Limiting The Fibre Channel port rate-limiting feature for the Cisco MDS 9100 Series controls the amount of bandwidth available to individual Fibre Channel ports within groups of four host-optimized ports. Limiting bandwidth on one or more Fibre Channel ports allows the other ports in the group to receive a greater share of the available bandwidth under high-utilization conditions.
Page 27: Maximum Npiv Limit
The maximum number of NPIV logins is not configurable at the port level on edge switches operating in NPV mode. Starting with Cisco MDS 9000 Release 6.2(7), the maximum NPIV limit feature is supported on core NPIV switches, which include Cisco MDS 9513, MDS 9710, and MDS 9250i switches. The maximum NPIV limit per-port feature allows you to configure a per-port limit.
Page 28: Extended Credits
6000 buffer credits for a module can be allocated to ports as needed to greatly extend the distance for Fibre Channel SANs. Note This feature is supported on all Cisco MDS Director Class Fabric Switches and it is not supported on any Cisco MDS Fabric switches. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 29: N Port Virtualization
NPIV is used by edge switches in the NPV mode to log in to multiple end devices that share a link to the core switch. This feature is available only for Cisco MDS Blade Switch Series, the Cisco MDS 9124 Multilayer Fabric Switch, Cisco MDS 9134 Multilayer Fabric Switch, Cisco MDS 9148 Multilayer Fabric Switch, Cisco MDS 9148S Multilayer Fabric Switch, and Cisco MDS 9396S Multilayer Fabric Switch.
Page 30: Flexattach
SAN and server administrators when installing and replacing servers. This feature is available only for Cisco MDS 9000 Blade Switch Series, the Cisco MDS 9124, Cisco MDS 9134, Cisco MDS 9148 Multilayer Fabric Switch, Cisco MDS 9148S Multilayer Fabric Switch, and Cisco MDS 9396S switches when NPV mode is enabled.
Page 31: Configuring Interfaces
Guidelines and Limitations, on page 38 • Default Settings, on page 41 • Configuring Interfaces, on page 42 • Verifying Interfaces Configuration, on page 61 • Transmit-Wait History Graph, on page 77 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 32: Finding Feature Information
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 33: Feature History For Interfaces
{core | edge | all} command, where port-type was replaced with logical-type, access-port was replaced with edge, and trunks was replaced with core. The following command was modified: logical-type {core | edge | all} Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 34 (cong-isolate) was introduced for the credit-loss-reco, tx-credit-not-available, tx-slowport-oper-delay, and txwait counters. The cong-isolate portguard action was added to the following commands: • counter credit-loss-reco • counter tx-credit-not-available • counter tx-slowport-oper-delay • counter tx-wait Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 35: Information About Interfaces
Each physical Fibre Channel interface in a switch may operate in one of several port modes: E port, F port, FL port, TL port, TE port, SD port, and ST port (see Figure 1: Cisco MDS 9000 Series Switch Port Modes, on page 17).
Page 36: E Port
In trunking E port (TE port) mode, an interface functions as a trunking expansion port. It can be connected to another TE port to create an extended ISL (EISL) between two switches. TE ports are specific to Cisco MDS 9000 Series Multilayer Switches. These switches expand the functionality of E ports to support the following: •...
Page 37: Tf Port
N port (TN port) or trunked NP port (TNP port) to create a link between a core switch and an NPV switch or an host bus adapter (HBA) in order to carry tagged frames. TF ports are specific to Cisco MDS 9000 Series Multilayer Switches.
Page 38: Auto Mode
E port mode. If the interface is attached to another switch in the Cisco MDS 9000 Series Multilayer Switches, it may become operational in TE port mode. For more details about trunking, see Configuring Trunking, on page 197.
Page 39 If the administrative state is up and the operational state is down, the reason code differs based on the nonoperational reason code, as described in Table 6: Reason Codes for Nonoperational States , on page Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 40 No port activation license available A port is not active because it does not have a port license. SDM failure A port is isolated because SDM is unable to program routes. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 41: Graceful Shutdown
Interfaces on a port are shut down by default (unless you modified the initial configuration). The Cisco NX-OS software implicitly performs a graceful shutdown in response to either of the following actions for interfaces operating in the E port mode: •...
Page 42: Port Administrative Speeds
Cisco MDS 9000 Series NX-OS Fabric Configuration Guide Note This feature is triggered only if both the switches at either end of the E port interface are Cisco MDS switches and are running Cisco SAN-OS Release 2.0(1b) or later, or Cisco MDS NX-OS Release 4.1(1a) or later.
Page 43: Port Beaconing
By default, the threshold disables the interface. However, you can configure the switch to not disable an interface when the threshold is crossed. To disable the BER threshold for an interface, perform these steps: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 44: Sfp Transmitter Types
The SFP hardware transmitters are identified by their acronyms when displayed using the show interface brief command. If the related SFP has a Cisco-assigned extended ID, the show interface and show interface brief commands display the ID instead of the transmitter type. The show interface transceiver and show interface fc slot/port transceiver commands display both values (ID and transmitter type) for Cisco-supported SFPs.
Page 45: Portguard
This means that a port is brought to down state when it reaches the maximum number of allowed link failures or the maximum number of specified causes. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 46: Port Monitor Portguard
The following is the list of events that can be used to trigger the Port Monitor portguard actions: • err-pkt-from-xbar • err-pkt-to-xbar • credit-loss-reco • link-loss • signal-loss • sync-loss • rx-datarate • invalid-crc • invalid-words • link-loss • tx-credit-not-available • tx-datarate • tx-discards • tx-slowport-oper-delay • txwait Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 47: Port Monitor
The unit for threshold values (rising and falling) differs across different counters. Note The link connecting a core switch to a Cisco NPV switch should be treated as an Inter-Switch Link (ISL) (core port) in the port monitor. Previously, core ports were included as access ports and were subject to any portguard actions configured.
Page 48 • This counter was introduced in Cisco NX-OS Release 6.2(13). • For all platforms, if the default value for txwait is modified, ISSD to a version lower than Cisco MDS NX-OS Release 6.2(13) will be restricted. To proceed with ISSD, use the no form of the counter txwait command to roll back to the default value.
Page 49 Configuring Interfaces Port Monitor • This counter was introduced in Cisco NX-OS Release 6.2(13). Table 9: Recommended Units for Port Monitor Policy Counter Threshold Interval Rising Event Falling Event Warning Type (Seconds) Threshold Threshold Threshold link-loss Delta Seconds Number Event...
Page 50 For more information, see Configuring a Port Monitor Policy, on page The following counters were added from Cisco MDS NX-OS Release 5.2(2a) that are not included in the default policy: Note •...
Page 51: Warning Threshold
Syslog Generated When the Error Count is Less Than the Rising Threshold Value %PMON-SLOT2-4-WARNING_THRESHOLD_REACHED_UPWARD: Invalid Words has reached warning threshold in the upward direction (port fc2/18 [0x1091000], value = 10). Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 52 As there are no further errors in this poll interval, the consecutive polling interval will have no errors, and the error count decreases (moves in downward direction) and reaches the falling threshold value, which is zero. A syslog is generated for the falling threshold. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 53: Port Monitor Check Interval
By default, the check interval functionality is not enabled. Note • The port monitor check interval feature is supported only on the Cisco MDS 9710 Multilayer Director, Cisco MDS 9718 Multilayer Directors, and Cisco MDS 9706 Multilayer Directors. • Check interval is supported on both counters, absolute and delta.
Page 54: Interface Types
You can create an IP interface on top of a VSAN, and then use this interface to send frames to the corresponding VSAN. To use this feature, configure the IP address for this VSAN. Note VSAN interfaces cannot be created for non existing VSANs. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 55: Prerequisites For Interfaces
To verify the status of a module at any time, enter the show module command in EXEC mode. For information about verifying the module status, refer to the Cisco MDS 9000 Series NX-OS Fundamentals Configuration Guide. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 56: Guidelines And Limitations
If the link between a core switch and a Cisco NPV switch is treated as an edge port, portguard action is taken on such ports which will result in the loss of connectivity to all the devices connected to the Cisco NPV switch.
Page 57 You can configure longer poll intervals to capture events across poll intervals. For example, configure a poll interval of 24 hours with a check interval of 30 seconds, with the rising threshold value being checked cumulatively every 30 seconds. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 58: Guidelines For Vsan Interface Configuration
• If you send a port beaconing request with the duration set to 0 from Switch A that is running Cisco MDS NX-OS Release 8.3(1) or later releases to Switch B and then downgrade Switch A to Cisco MDS NX-OS Release 8.2(2) or earlier releases, the port LED on Switch B to which the port beaconing request was...
Page 59: Default Settings
On (unless changed during initial setup) on non-NPV and NPIV core switches. Off on NPV switches. Trunk-allowed VSANs or VF-IDs 1 to 4093 Interface VSAN Default VSAN (1) Beacon mode Off (disabled) EISL encapsulation Disabled Data field size 2112 bytes Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 60: Configuring Interfaces
To set the interface administrative state, you must first gracefully shut down the interface and enable traffic flow. Shutting Down an Interface To gracefully shut down an interface, perform these steps: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 61: Enabling Traffic Flow
Fx ports refer to an F port or an FL port (host connection only), but not E ports. Note Step 4 Configure interface mode to auto negotiate an E, F, FL, or TE port mode (not TL or SD port modes) of operation: switch(config-if)# switchport mode auto Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 62: Configuring The Max Npiv Limit
• All user-configured ports, even if they are down. • All non-F ports that are up. However, if non-F ports are down, this command changes the administrative mode of those ports. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 63: Configuring Isl Between Two Switches
E port (trunking or nontrunking, depending on the trunking port mode). To configure the port mode to E: Step 1 Enter configuration mode: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 64: Configuring The Port Administrative Speeds
To configure the port speed group of the interface, perform these steps: Step 1 Enter configuration mode: switch# configure terminal Step 2 Select the Fibre Channel interface and enter interface configuration mode: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 65: Configuring The Interface Description
Configuring a Port Logical Type The logical port type can be used to override the default type assigned by the Cisco NX-OS to a port. Previously, point to point F and TF ports were used by a single edge device with a single login to the switch. With the adoption of the Cisco NPV technology, these types of switch ports can now have multiple logins from multiple edge devices on a single port.
Page 66: Specifying A Port Owner
By default, the beacon mode is disabled on all switches. The beacon mode is indicated by a flashing green light that helps you identify the physical location of the specified interface. Note that configuring the beacon mode has no effect on the operation of the interface. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 67: Configuring The Port Beacon Led
(Optional) Configure the default setting for the administrative state of an interface as down: switch(config)# system default switchport shutdown Note This command is applicable only to interfaces for which no user configuration exists for the administrative state. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 68: Configuring The Port-Level Portguard
{trustsec-violation | bit-errors | credit-loss | link-reset | signal-loss | sync-loss} The link resumes flapping and sending error reports normally. The portguard credit loss event is triggered only on loop interfaces; it is not triggered on point-to-point interfaces. Note Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 69 Admin Speed is auto max 16 Gbps Operating Speed is 4 Gbps Rate mode is dedicated Port flow-control is R_RDY Transmit B2B Credit is 500 Receive B2B Credit is 500 B2B State Change Number is 14 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 70: Configuring A Port Monitor
To enable or disable a port monitor, perform these steps: Step 1 Enter configuration mode: switch# configure terminal Step 2 Enable port monitoring: switch(config)# port-monitor enable (Optional) Disable port monitoring: switch(config)# no port-monitor enable Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 71: Configuring The Check Interval
| tx-credit-not-available | tx-datarate | tx-discards | tx-slowport-oper-delay | txwait} poll-interval seconds {absolute | delta} rising-threshold count1 event RMON-ID warning-threshold count2 falling-threshold count3 event RMON-ID portguard {errordisable | flap | cong-isolate} Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 72: Activating A Port Monitor Policy
• Logical-type edge ports are normally F ports that are connected to end devices. • Logical-type core ports are E ports (ISLs) or (T)F ports connected to Cisco NPV switches. Some of the edge port counter thresholds and port-guard actions might not be appropriate on the TF ports in the port-monitor configurations.
Page 73: Configuring Port Monitor Portguard
| tx-credit-not-available | tx-datarate | tx-discards | tx-slowport-oper-delay | txwait} poll-interval seconds {absolute | delta} rising-threshold count1 event RMON-ID warning-threshold count2 falling-threshold count3 event RMON-ID portguard {errordisable | flap | cong-isolate} Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 74: Configuring Port Group Monitor
To configure a port group monitor policy, perform these steps: Step 1 Enter configuration mode: switch# configure terminal Step 2 Specify the policy name and enter port group monitoring policy configuration mode: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 75: Reverting To The Default Policy For A Specific Counter
Admin status : Not Active Oper status : Not Active Port type : All Port Groups ------------------------------------------------------------------------------------------ Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold ------- --------- -------- -------------------- ---------------------- RX Datarate Delta Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 76: Turning Off Specific Counter Monitoring
To configure the mgmt0 Ethernet interface to connect over IPv4, perform these steps: Step 1 Enter configuration mode: switch# configure terminal Step 2 Select the management Ethernet interface on the switch and enter interface configuration submode: switch(config)# interface mgmt0 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 77: Configuring The Management Interface Over Ipv6
2001:0db8:800:200c::417a/64 Step 5 Enable the interface: switch(config-if)# no shutdown Step 6 Return to user EXEC mode: switch(config)# exit (Optional) Save your configuration changes to the file system: switch# copy running-config startup-config Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 78: Creating Vsan Interfaces
To create a VSAN interface, perform these steps: Step 1 Enter configuration mode: switch# configure terminal Step 2 Configure a VSAN with the ID 2: switch(config)# interface vsan 2 Step 3 Enable the VSAN interface: switch(config-if)# no shutdown Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 79: Verifying Interfaces Configuration
Port vsan is 1 Admin Speed is auto max 32 Gbps Operating Speed is 16 Gbps Rate mode is dedicated Port flow-control is R_RDY Transmit B2B Credit is 64 Receive B2B Credit is 32 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 80 You can also specify arguments (a range of interfaces or multiple specified interfaces) to display interface information. You can specify a range of interfaces by issuing a command in the following format: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 81 500 transmit B2B credit remaining 485 low priority transmit B2B credit remaining Interface last changed at Mon Apr 24 23:11:49 2017 Last clearing of "show interface" counters : never fc3/12 is trunking Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 82 Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN) Port WWN is 20:89:54:7f:ee:de:c5:00 Peer port WWN is 20:09:00:2a:6a:a4:0b:00 Admin port mode is E, trunk mode is on snmp link state traps are enabled Port mode is TE Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 83 The following example displays the description of interfaces: Displays Port Description switch# show interface description ------------------------------------------------------------------------------- Interface Description ------------------------------------------------------------------------------- fc3/1 test intest fc3/2 fc3/3 fc3/4 TE port fc3/5 fc3/6 fc3/10 Next hop switch 5 fc3/11 fc3/12 fc3/16 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 84 0 discards, 0 CRC, 0 unknown class 0 too long, 0 too short 0 frames output, 0 bytes 0 class-2 frames, 0 bytes 0 class-3 frames, 0 bytes 0 class-f frames, 0 bytes Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 85 Displays Interface Counters in Brief Format switch# show interface counters brief ------------------------------------------------------------------------------- Interface Input (rate is 5 min avg) Output (rate is 5 min avg) ----------------------------- ----------------------------- Rate Total Rate Total Mbits/s Frames Mbits/s Frames ------------------------------------------------------------------------------- Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 86 2 3946 3946 You can run the show interface transceiver command only on a switch in the Cisco MDS 9100 Series if the SFP is present, as show in the following example: Displays Transceiver Information switch# show interface transceiver...
Page 87 Displays the Running Configuration after Two Interfaces are Individually Configured for Mode FL switch# show running-config version 3.1(3) system default switchport mode F interface fc4/1 switchport mode FL interface fc4/2 interface fc4/3 switchport mode FL interface fc4/4 interface fc4/5 interface fc4/6 interface fc4/7 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 88: Displaying The Port-Level Portguard
Displaying the Port-Level Portguard The following command displays information about an interface that is set to error-disabled state by the portguard because of a TrustSec violation: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 89: Displaying Port Monitor Status And Policies
Signal Loss Delta Not enabled Not enabled Invalid Words Delta Not enabled Not enabled Invalid CRC's Delta Not enabled Not enabled State Change Delta Not enabled Not enabled TX Discards Delta Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 90 TX Credit Not Available Delta Not enabled Cong-isolate RX Datarate Delta Not enabled Not enabled TX Datarate Delta Not enabled Not enabled ASIC Error Pkt from Port Delta Not enabled Not enabled Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 91 Not enabled TX-Slowport-Oper -Delay Absolute 50ms Not enabled TXWait Delta Not enabled ----------------------------------------------------------------------------------------------------------- switch# show port-monitor default Policy Name : default Admin status : Not Active Oper status : Not Active Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 92 Rising Threshold event Falling Threshold event PMON Portguard ------------------------------------------------------------------------------------------------------------------------------- Credit Loss Reco Delta Not enabled TX Credit Not Available Delta Not enabled -------------------------------------------------------------------------------------------------------------------------------- switch# show port-monitor slowportdetect Policy Name : slowportdetect Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 93: Displaying Port Group Monitor Status And Policies
Admin status : Not Active Oper status : Not Active Port type : All Port Groups ------------------------------------------------------------------------------------------ Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold ------- --------- -------- -------------------- ---------------------- RX Datarate Delta Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 94: Displaying The Management Interface Configuration
WWPN is 10:00:00:05:30:00:59:1f, FCID is 0xb90100 Internet address is 10.1.1.1/24 MTU 1500 bytes, BW 1000000 Kbit 0 packets input, 0 bytes, 0 errors, 0 multicast 0 packets output, 0 bytes, 0 errors, 0 dropped Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 95: Transmit-Wait History Graph
1 port 81 TxWait history for port fc1/81: ============================== 455555555455554555554555599999999999999999999999999999999999 900000000800009000008100011111231922322211321121112112113111 433799991899990359909838608935137962088988254848894870461938 1000 ################################### ################################### ################################### ################################### 500 ############################################################ 400 ############################################################ 300 ############################################################ 200 ############################################################ 100 ############################################################ 0..5..1..1..2..2..3..3..4..4..5..5..6 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 96 - only txwait delta value >= 100 ms are logged --------------------------------- Module: 1 txwait count --------------------------------- ----------------------------------------------------------------------------- | Interface | Delta TxWait Time | Congestion | Timestamp | 2.5us ticks | seconds | ----------------------------------------------------------------------------- Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 97 Configuring Interfaces Transmit-Wait History Graph fc1/11 3435973 | 08 | Sun Sep 30 05:23:05 2001 | fc1/11 6871947 | 17 | Sun Sep 30 05:22:25 2001 | Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 98 Configuring Interfaces Transmit-Wait History Graph Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 99: Configuring Fibre Channel Interfaces
Guidelines and Limitations, on page 85 • Configuring Fibre Channel Interfaces, on page 91 • Verifying Fibre Channel Interfaces Configuration, on page 104 • Configuration Examples for Fibre Channel Interfaces, on page 106 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 100: Finding Feature Information
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 101: Information About Fibre Channel Interfaces
Corresponding resources must be made available in order for the port to be successfully returned to service. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 102: Bandwidth Fairness
Module 2 bandwidth-fairness is enabled Upgrade or Downgrade Scenario When you are upgrading from a release earlier than Cisco SAN-OS Release 3.1(2), all modules operate with bandwidth fairness disabled until the next module reload. After the upgrade, any new module that is inserted has bandwidth fairness enabled.
Page 103: Guidelines And Limitations
Generation 1 and Generation 2 modules are not supported in Cisco MDS NX-OS Release 8.1(x). Cisco MDS 9000 switches allocate index identifiers for the ports on the modules. These port indexes cannot be configured. You can combine Generation 1, Generation 2, Generation 3, and Generation 4 switching modules, with either Supervisor-1 modules or Supervisor-2 modules.
Page 104 (PSS) and displaying an allowed range for startup indices is meaningless. If a module fails to power up, you can use the show module slot recovery-steps command to display the reason. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 105: Portchannel Limitations
PortChannel Limitations Note Generation 1 and Generation 2 modules are not supported in Cisco MDS NX-OS Release 8.1(x). PortChannels have the following restrictions: • The maximum number of PortChannels allowed is 256 if all switching modules are Generation 2 or Generation 3, or both.
Page 106 Auto Auto max 2000 Auto Generation 2 or Normal Fail Generation 3 Force Pass or fail Generation 1 or Auto max 4000 Auto Generation 2 Auto max 4000 Auto Generation 3 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 107 Auto max 2000 Auto Generation 3 or Normal Fail Generation 4 Force Pass Auto Auto max 2000 Generation 3 or Normal Fail Generation 4 Force Pass If resources are not available. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 108 Configuring Fibre Channel Interfaces PortChannel Limitations If resources are not available. Use the show port-channel compatibility parameters command to obtain information about PortChannel addition errors. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 109: Configuring Fibre Channel Interfaces
Configuring an Interface Mode , on page Note ISL ports cannot operate in shared rate mode. Step 4 Configure the rate mode (dedicated or shared) to use. See the Configuring FEC, on page Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 110: Configuring Port Speed
Beacon is turned off 5 minutes input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec 5 minutes output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec 226 frames input, 18276 bytes 0 discards, 0 errors Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 111: Configuring Fec
FEC has the following restrictions: • FEC is supported on the DS-X9334-K9, DS-X9648-1536K9, and DS-X9448-768K9 modules in the Cisco MDS 9700 Series switch. FEC is also supported on the Cisco MDS 9132T Fibre Channel Switch and Cisco MDS 9396S Multilayer Fabric Switch.
Page 112 0 input OLS,0 LRR,0 NOS,0 loop inits 306 output OLS,304 LRR, 1 NOS, 4 loop inits 32 receive B2B credit remaining 128 transmit B2B credit remaining 128 low priority transmit B2B credit remaining Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 113: Configuring Rate Mode
Before disabling restrictions on oversubscription ratios, ensure that you have explicitly shut down shared ports. To disable restrictions on oversubscription ratios on a Fibre Channel switching module, perform these steps: Step 1 switch# configure terminal Enters configuration mode. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 114: Examples
-------------------------------------------------------------------- Interfaces in the Port-Group B2B Credit Bandwidth Rate Mode Buffers (Gbps) -------------------------------------------------------------------- fc2/1 shared fc2/2 shared fc2/3 dedicated fc2/4 shared fc2/5 shared fc2/6 dedicated fc2/7 dedicated fc2/8 shared fc2/9 shared Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 115 Step 4 Disable restrictions on oversubscription ratios for the ports. Example: switch# config t Enter configuration commands, one per line. End with CNTL/Z. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 116: Enabling Restrictions On Oversubscription Ratios
• Before enabling restrictions on oversubscription ratios, ensure that you have explicitly configured shared ports to out-of-service mode. To enable restrictions on oversubscription ratios on a Fibre Channel switching module, perform these steps: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 117: Enabling Bandwidth Fairness
Saves the new oversubscription ratio configuration to the startup configuration, and then the new configuration is enforced upon subsequent reboots of the module. Enabling Bandwidth Fairness To enable bandwidth fairness on a switching module, perform these steps: Step 1 switch# configure terminal Enters configuration mode. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 118: Disabling Bandwidth Fairness
You can take interfaces out of service on Generation 2 and Generation 3 switching modules. When an interface is out of service, all the shared resources for the interface are released as well as the configuration associated with those resources. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 119 Total shared bandwidth is 12.8 Gbps Allocated dedicated bandwidth is 0.0 Gbps -------------------------------------------------------------------- Interfaces in the Port-Group B2B Credit Bandwidth Rate Mode Buffers (Gbps) -------------------------------------------------------------------- fc9/1 shared fc9/2 (out-of-service) fc9/3 shared fc9/4 shared fc9/5 shared Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 120: Releasing Shared Resources In A Port Group
Fibre Channel ACL adjacency sharing is enabled by default on the switches with an active Generation 2 switching module as of Cisco MDS SAN-OS Release 3.0(3), and with an active Generation 3 module as of MDS NX-OS Release 4.1(1). Fibre Channel ACL adjacency sharing improves the performance for zoning and inter-VSAN routing (IVR) network address translation (NAT).
Page 121 Configuring Fibre Channel Interfaces Disabling ACL Adjacency Sharing for System Image Downgrade the system image on your switch to a release prior to Cisco SAN-OS Release 3.0(3), enter the following command in EXEC mode: switch# system no acl-adjacency-sharing To reenable Fibre Channel ACL adjacency sharing on your switch, enter the following command in EXEC...
Page 122: Verifying Fibre Channel Interfaces Configuration
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN) Port WWN is 22:55:54:7f:ee:ea:1f:00 Peer port WWN is 22:24:54:7f:ee:ea:1d:00 Admin port mode is auto, trunk mode is on snmp link state traps are enabled Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 123: Displaying Sfp Diagnostic Information
SFP Diagnostics Information: Temperature 30.61 C Voltage 3.35 V Current 4.10 mA Optical Tx Power -2.44 dBm Optical Rx Power Tx Fault count Note: ++ high-alarm; + high-warning; -- low-alarm; -low-warning Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 124: Configuration Examples For Fibre Channel Interfaces
4/3 - 4 Step 5 Configure the port speed, rate mode, and port mode on the interfaces. Example: switch(config-if)# switchport speed 16000 switch(config-if)# switchport fec Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 125: Configuring Interface Buffers
Configuring Interface Buffers, on page 117 • Configuration Examples for Interface Buffers, on page 122 • Verifying Interface Buffer Configuration, on page 124 • Troubleshooting Interface Buffer Credits, on page 126 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 126: Finding Feature Information
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 127: Information About Interface Buffers
(for example, forwarding frames over FCIP interfaces). For each physical Fibre Channel interface in any switch in the Cisco MDS 9000 Series, you can specify the amount of performance buffers allocated in addition to the configured receive buffer-to-buffer credit value.
Page 128: 48-Port 32-Gbps Fibre Channel Module Buffer-To-Buffer Credit Buffers
500 buffers. • If you have installed an enterprise license, per port credits in a port group can be increased up to 800 using extended buffer to buffer credits. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 129: 48-Port 16-Gbps Fibre Channel Module Buffer-To-Buffer Credit Buffers
8191 Note In Cisco MDS 9700 Series Switches module, each port group comprises of 16 ports, and there are 3 port groups per ASIC. Port group buffers can be allocated to any combination of ports in that port group using extended buffer configuration.
Page 130: Buffer-To-Buffer Credit Buffers For Fabric Switches
Note In Cisco MDS 9700 Series Switches module, each port group comprises of 4 ports, and there are 12 port groups per ASIC. Port group buffers can be allocated to any combination of ports in that port group using extended buffer configuration.
Page 131: Cisco Mds 9250I And Cisco Mds 9148S Fabric Switch Buffer-To-Buffer Credit Buffers
Cisco MDS 9250i and Cisco MDS 9148S Fabric Switch Buffer-to-Buffer Credit Buffers Table 17: 40/48-Port 16-Gbps Switch Buffer-to-Buffer Credit Buffer Allocation, on page 113 lists the buffer-to-buffer credit buffer allocation for 40/48-port 16-Gbps Cisco MDS 9250i and 9148S Fabric switches. Table 17: 40/48-Port 16-Gbps Switch Buffer-to-Buffer Credit Buffer Allocation Buffer-to-Buffer...
Page 132: Extended Buffer-To-Buffer Credits
Note Cisco MDS 9148S and Cisco MDS 9250i are 16 Gbps line-rate switches. The following guidelines apply to buffer-to-buffer credit buffers on the 40/48-port 9250i/9148S Fabric switches: • Buffer-to-buffer credit buffers can be configured from a minimum of 1 buffer to a maximum of 64 buffers per port when the ports are in F or FL mode.
Page 133: Buffer-To-Buffer Credit Recovery
R_RDY primitives sent. This enables an attached port to determine if any R_RDY primitives are lost. If R_RDY primitive loss is detected, the receiver of the BB_SCr increments the number of transmit credits by the appropriate number to compensate for the lost R_RDYs. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 134: Receive Data Field Size
• F ports • This feature is enabled by default on F ports. • This feature works on an F port between a Cisco switch and a peer device from any vendor, provided this feature is supported on the peer device.
Page 135: Configuring Interface Buffers
ISL in ER_RDY flow-control mode. Before you begin Enable the Extended Receiver Ready (ER_RDY) mode on ISLs before configuring the virtual-link credits. For more information, see Enabling Extended Receiver Ready, on page 177. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 136: Configuring Performance Buffers
The interface must be in R_RDY flow-control mode. Before you begin Enable the Receiver Ready (R_RDY) mode on ISLs before configuring the shared buffer-to-buffer credit pool. For more information, see Disabling Extended Receiver Ready, on page 178. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 137: Configuring Extended Buffer-To-Buffer Credits For Virtual Links
Set the extended buffer-to-buffer credits per virtual link on an ISL: switch(config-if)# switchport vl-credit extended vl0 credits vl1 credits vl2 credits vl3 credits Step 5 (Optional) Reset the extended buffer-to-buffer credits on the ISL to the default value: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 138: Configuring Buffer-To-Buffer Credit Recovery
Configuring Receive Data Field Size Note From Cisco MDS NX-OS 8.2(1), the switchport fcrxbufsize command is obsolete on the Cisco MDS 9700 48-port 16-Gbps Fibre Channel Switching Module and the Cisco MDS 9700 48-port 32-Gbps Fibre Channel Switching Module. The receive data field size is permanently set to 2112 bytes. Any receive data field size configuration from earlier Cisco MDS NX-OS versions is ignored.
Page 139 Configuring Interface Buffers Configuring Receive Data Field Size switch(config-if)# no switchport fcrxbufsize Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 140: Configuration Examples For Interface Buffers
12 vl1 10 vl2 29 vl3 349 This example shows how to assign extended buffer-to-buffer credits per virtual link on an ISL: switch# configure terminal switch(config)# fcrxbbcredit extended enable switch(config)# interface fc 1/1 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 141 Configuring Interface Buffers Configuration Examples for Interface Buffers switch(config-if)# switchport vl-credit extended vl0 20 vl1 25 vl2 40 vl3 349 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 142: Verifying Interface Buffer Configuration
Classes of Service supported are Class 2, Class 3, Class F Class 2 sequential delivery supported Class 3 sequential delivery supported Hold time (max/min) (100000/1) micro sec BB state change notification supported Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 143 Transmit B2B Credit for vl3 is 430 Receive B2B Credit for vl0 is 15 Receive B2B Credit for vl1 is 15 Receive B2B Credit for vl2 is 40 Receive B2B Credit for vl3 is 430 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 144: Troubleshooting Interface Buffer Credits
0 discards, 0 errors received 0 discards, 0 errors transmitted 4 frames, 304 bytes transmitted 0 class-2 frames, 0 bytes transmitted 4 class-3 frames, 304 bytes transmitted 0 class-3 frames discarded Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 145 0 Non F8 type LIP sequence errors issued 0 fec corrected blocks 0 fec uncorrected blocks 0 BB_SCs credit recoveries, 0 BB_SCr credit recoveries Percentage Tx credits not available for last 1s/1m/1h/72h: 0%/0%/0%/0% Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 146 Configuring Interface Buffers Troubleshooting Interface Buffer Credits Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 147: Congestion Detection, Avoidance, And Isolation
Verifying Slow-Drain Device Detection and Congestion Isolation, on page 182 • Configuration Examples for Congestion Detection, Avoidance, and Isolation, on page 183 • Verifying Congestion Detection, Avoidance, and Isolation, on page 190 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 148: Finding Feature Information
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 149: Feature History For Congestion Detection, Avoidance, And Isolation
The following commands were introduced: • show hardware internal txwait-history [module number | port number] • show hardware internal rxwait-history [module number | port number] Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 150 | global-list | ifindex-list | include-list | pmon-list | remote–list | status} The cong-isolate portguard action was added to the following commands: • counter credit-loss-reco • counter tx-credit-not-available • counter tx-slowport-oper-delay • counter tx-wait Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 151 • system timeout congestion-drop milliseconds logical-type {core | edge} • system timeout no-credit-drop milliseconds logical-type edge • system timeout slowport-monitor milliseconds logical-type {core | edge} • switchport logical-type {auto | core | edge} Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 152: Information About San Congestion
1 second and for an E port it is 1.5 seconds. When this type of congestion occurs, a Fibre Channel primitive Link Credit Reset (LR) is sent to restore the BB_credits on the link in Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 153 Counts of frames and credits that are returned are periodically exchanged and if there is any discrepancy in the count then credits can be recovered. BB_SCN is available on all ISLs and is extended to F ports from Cisco MDS NX-OS Release 8.2(1).
Page 154 (Fibre Channel only). • Transitions to zero: A Virtual Link based Buffer-to-Buffer credit. From Cisco MDS NX-OS 8.1(1), we introduced the Congestion-Isolation feature. This feature allows slow-drain devices to be isolated to a slow traffic virtual link (VL2) on an ISL (E port). The ISL must be in the Extended Receiver Ready (ER_RDY) mode for this feature to function.
Page 155: Information About San Congestion Caused By Over Utilization
Information About Congestion Detection, Avoidance, and Isolation Information About Congestion Detection The following features are used to detect congestion on all slow-drain levels on Cisco MDS switches: • All Slow-Drain Levels Display of credits agreed to along with the remaining credits on a port (Fibre Channel only)—The credits that are agreed to in both directions in FLOGI (F ports) and Exchange Link Parameters (ELP) for ISLs are displayed via the show interface command.
Page 156 27651428465 frames, 59174056872960 bytes received 0 class-2 frames, 0 bytes received 0 class-2 discards 0 F_BSY frames, 0 F_RJT frames generated against class-2 frames 0 port reject frames 27651428465 class-3 frames, 59174056872960 bytes received Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 157 0 Non F8 type LIP sequence errors issued 0 fec corrected blocks 0 fec uncorrected blocks Percentage Tx credits not available for last 1s/1m/1h/72h: 0%/64%/0%/0% switch# show process creditmon credit-loss-events Module: 01 Credit Loss Events: YES Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 158 ERROR STATISTICS INFORMATION FOR DEVICE DEVICE: FCMAC --------------------------------------------------------------------------------------------------------- Interface Time Stamp Range Error Stat Counter Name Count |MM/DD/YY HH:MM:SS --------------------------------------------------------------------------------------------------------- fc1/1 |F16_TMM_TOLB_TIMEOUT_DROP_CNT |14713116 |08/22/18 10:25:15 fc1/1 |FCP_SW_CNTR_TX_WT_AVG_B2B_ZERO |1781669 |08/22/18 10:25:15 fc1/1 |FCP_SW_CNTR_CREDIT_LOSS |08/22/18 10:25:15 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 159 These dropped frames cause SCSI exchanges to fail at the end hosts. Timeout discards are mostly accompanied by level 1 or level 1.5 congestion. Timeout-drops are displayed in the following ways: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 160 |08/22/18 10:25:15 fc1/1 |F16_TMM_TOLB_TIMEOUT_DROP_CNT |13338566 |08/22/18 10:24:55 fc1/1 |FCP_SW_CNTR_TX_WT_AVG_B2B_ZERO |1781544 |08/22/18 10:24:55 fc1/1 |FCP_SW_CNTR_CREDIT_LOSS |08/22/18 10:24:55 • Instances of timeout-drops in OBFL flow-control timeout-drops switch# show logging onboard flow-control timeout-drops --------------------------------- Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 161 Therefore, these counters are not a preferred indication of congestion on a port. See the TxWait counter for a better indication of Tx congestion on a port. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 162 0 output OLS, 0 LRR, 0 NOS, 0 loop inits 0 link failures, 0 sync losses, 0 signal losses 903218 Transmit B2B credit transitions to zero 743093 Receive B2B credit transitions to zero Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 163 TxWait history for port fc1/1: ============================== 8999994 299999999999999999999997 5888883 188879888888888889999998 000000076362570000000000000066468354635464357888708700000000 1000 ##### ###################### ###### ###################### ###### ####################### ###### ####################### ###### ####################### ###### ####################### ####### ####################### ####### ####################### ####### ######################## ####### ######################## Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 164 PFC pause; therefore, preventing the adjacent device from transmitting. switch# attach module 2 module-2# show hardware internal rxwait-history port 1 RxWait history for port Eth2/1: ============================== 000000000000000000000000000000000000000000000000000000000000 1000 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 165 100 ms or more of TxWait or RxWait in a 20-second interval. If a port accumulates less than 100 ms of TxWait or RxWait, nothing is logged for that 20-second interval. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 166 | Thu Aug 2 11:47:58 2018 | • Display of average Tx credit not available in 100-ms intervals—Cisco MDS switches have a software process that runs every 100 ms to check for ports that are in continuous state of 0 Tx credits remaining.
Page 167 20 seconds. Information about other counters is also included in the command output. switch# show logging onboard error-stats ---------------------------- Module: ---------------------------- ---------------------------- Show Clock ---------------------------- 2018-08-28 12:28:15 --------------------------------- Module: 1 error-stats --------------------------------- Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 168 (port=fc12/11 [0x158a000], value=878848923) . 2018 Aug 24 13:10:45 %PMON-SLOT12-5-FALLING_THRESHOLD_REACHED: TX Datarate has reached the falling threshold (port=fc12/11 [0x158a000], value=387111312) . switch# show logging onboard datarate ---------------------------- Module: ---------------------------- --------------------------------- Module: 1 datarate --------------------------------- ---------------------------- Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 169 The following example displays the transition to zero status of the transmit and receive credits: switch# show interface eth3/1 Ethernet3/1 is up admin state is up, Dedicated Interface Belongs to Epo540 ...snip 555195 unicast packets 105457 multicast packets 0 broadcast packets ...snip 230870335 Rx pause Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 170 Port monitor can also generate a slowport-monitor alert. By default, slowport-monitor alert is set to off. Slowport-monitor must be configured to get the port-monitor slowport-monitor alerts. The show process creditmon slowport-monitor-events [module number] [port number] command shows the last ten events per port. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 171 • RxWait (FCoE only)—It is a measure of time that a port is in a transmit PFC pause state that is preventing the adjacent device from transmitting to the port. RxWait increments by 1 every 2.5 microseconds that a port is unable to receive. RxWait is shown in the following ways: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 172 The show logging onboard error-stats command records various counters when the counters change value. When the value of a counter changes, the current value is recorded along with the date and time. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 173 The time that the port was highly utilized is the time between the rising threshold and falling threshold alerts. These alerts are recorded in the RMON log in all Cisco MDS NX-OS releases. From Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 174 Congestion Detection, Avoidance, and Isolation Information About Congestion Detection Cisco MDS NX-OS 8.2(1) and later releases, the alerts are logged in OBFL and are displayed in the show logging onboard datarate command. • Port monitor (Fibre Channel only)—Port monitor can generate alerts for various congestion-related counters.
Page 175: Information About Congestion Avoidance
Congestion avoidance focuses on minimizing or completely avoiding the congestion that results from frames being queued to congested ports. Cisco MDS switches have multiple features designed to void congestion in SAN: • Congestion-drop timeout threshold (Fibre Channel and FCoE): The congestion-drop timeout threshold determines the amount of time a queued Fibre Channel or FCoE frame will stay in the switch awaiting transmission.
Page 176: Information About Congestion Isolation
(or defaulted) FCoE congestion-drop timeout. It is configured via the system timeout fcoe pause-drop commands (available from Cisco MDS NX-OS Release 8.2(1) onwards). The FCoE pause-drop timeout functionality is only used for edge ports, because these ports are directly connected to the slow-drain devices.
Page 177 You must ensure that the following requirements are met before enabling the Congestion Isolation feature: • Flows must traverse ISLs because Congestion Isolation functions only across Fibre Channel ISLs. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 178 Congestion Isolation portguard action (cong-isolate). The following is the list of counters that you can use to trigger the Congestion Isolation port-monitor portguard action (cong-isolate): • credit-loss-reco • tx-credit-not-available • tx-slowport-oper-delay • txwait Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 179: Guidelinesandlimitationsforcongestiondetection,Avoidance, And Isolation
743 – 626 = 117 frames. There were 117 frames discarded at timeout-drops during that interval. switch# show logging onboard error-stats ---------------------------- Show Clock ---------------------------- 2018-01-24 15:01:35 --------------------------------- Module: 1 error-stats --------------------------------- Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 180: Guidelines And Limitations For Congestion Avoidance
Since no-credit-drop will drops any frames queued for transmit, if no-credit-drop is configured for Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 181: Guidelines And Limitations For Congestion Isolation
15:15:40:430 (VL0:VL1:VL2:VL3). • If you are upgrading or if you are in the Cisco MDS NX-OS Release 8.1(1), if ER_RDY was enabled, and if the buffer-to-buffer credits value that is configured is less than 34, the VLs are stuck in the...
Page 182 30:30:100:3935 (VL0:VL1:VL2:VL3). • If you are upgrading to or if you are in the Cisco MDS NX-OS Release 8.1(1), ER_RDY is enabled, and the buffer-to-buffer credits value configured is less than 34, the VLs are stuck in the initialization state because the control lane (VL0) is allocated 0 credits.
Page 183: Congestion Isolation
If the Congestion Isolation feature is configured on all the intended switches, these messages do not have any negative effect and can be ignored. For example, if a Cisco MDS switch is connected via FCoE ISLs then the Congestion Isolation feature does not apply to this switch and these messages can be ignored.
Page 184 VL (VL2). To avoid this situation, set the zone QoS priority to low or high. • When a link to a Cisco NPV switch carrying multiple fabric logins (FLOGIs) is detected as a slow device, all the devices connected to the Cisco NPV switch are marked as slow devices.
Page 185 Virtual Link (VL2). The switch does not automatically remove any devices from congestion isolation. This must be done manually once the problem with the slow device is identified and resolved. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 186: Configuring Congestion Avoidance
• Cisco MDS 9700 48-Port 10-Gbps Fibre Channel over Ethernet (DS-X9848-480K9) • 40-Gbps FCoE module: • Cisco MDS 9700 40-Gbps 24-Port Fibre Channel over Ethernet Module (DS-X9824-960K9) Table 20: Slow Port Monitor Support on Fibre Channel and FCoE Switching Modules, on page 169...
Page 187: Configuring The Slow-Port Monitor Timeout Value For Fibre Channel
If the no-credit frame timeout drop is not enabled, no frames are dropped until the congestion frame timeout period is reached. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 188: Configuring Slow Port Monitor For Port Monitor
Configuring the Transmit Average Credit-Not-Available Duration Threshold and Action in Port Monitor Cisco MDS monitors its ports that are at zero transmit credits for 100 ms or more. This is called transmit average credit-not-available duration. The Port Monitor feature can monitor this using the TX Credit Not Available counter.
Page 189 Counter Threshold Interval Rising event Falling event Warning PMON Threshold Threshold Threshold Portguard ------------------------------------------------------------------------------------------------------------ Credit Loss Reco Delta Not enabled Not enabled TX Credit Not Available Delta Not enabled Not enabled Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 190: Configuring Other Congestion Related Port Monitor Counters
This is applicable only for generation 3 modules. tx-slowport-oper-delay Captures average credit delay (or R_RDY delay) experienced by a port. The value is in milliseconds. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 191: Configuring Congestion Avoidance
Step 2 Depending on the Cisco MDS NX-OS release version you are using, use one of the following commands to configure the system-wide FCoE congestion drop timeout, in milliseconds, for core or edge ports: • Cisco MDS NX-OS Release 8.1(1) and earlier releases switch(config)# system default interface congestion timeout milliseconds mode {core | edge} The FCoE congestion drop timeout range is from 100 to 1000 ms.
Page 192: Configuring Pause Drop Timeout For Fcoe
Step 2 Depending on the Cisco MDS NX-OS release version that you are using, use one of the following commands to configure the system-wide FCoE pause drop timeout value, in milliseconds, for edge or core ports: • Cisco MDS NX-OS Release 8.1(1) and earlier releases switch(config)# system default interface pause timeout milliseconds mode {core | edge} •...
Page 193: Configuring The Congestion Drop Timeout Value For Fibre Channel
Configuring the Congestion Drop Timeout Value for Fibre Channel (Optional) Depending on the Cisco MDS NX-OS release version that you are using, use one of the following commands to disable the FCoE pause drop timeout for edge or core ports: •...
Page 194: Displaying Credit Loss Recovery Actions
When a port is at zero transmit credits for 1 full second (F ports) and 1.5 seconds (E ports), it is called a credit loss condition. Cisco MDS initiates credit loss recovery by transmitting a Link Credit Reset (LCR). If the end device responds with a Link Credit Reset Response (LCRR), the port is back at its fully agreed number of B2B credits in both directions.
Page 195: Configuring Congestion Isolation
Configuring the Port-Monitor Portguard Action for Congestion Isolation, on page 180. Configuring Extended Receiver Ready Enabling Extended Receiver Ready To enable Extended Receiver Ready (ER_RDY) on a switch, perform these steps: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 196 180. 2. Disable the Congestion Isolation feature. For more information, see Enabling Congestion Isolation, on page 179. Step 1 Enter configuration mode: switch# configure terminal Step 2 Disable ER_RDY flow-control mode: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 197: Configuring Congestion Isolation
To disable Congestion Isolation, perform these steps: Before you begin Remove the congestion-isolation portguard action for links in the port-monitor policy. For more information, Configuring the Port-Monitor Portguard Action for Congestion Isolation, on page 180. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 198: Configuring The Port-Monitor Portguard Action For Congestion Isolation
Specify the policy name and enter port monitoring policy configuration mode: switch(config)# port-monitor name policyname Step 3 Specify the counter parameters for the portguard to take congestion isolation action on a port: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 199 Step 4 Return to configuration mode: switch(config-port-monitor)# exit Step 5 Activate the specified port-monitor policy: switch(config)# port-monitor activate policyname (Optional) Deactivate the specified port-monitoring policy: switch(config)# no port-monitor activate policyname Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 200: Verifyingslow-Draindevicedetectionandcongestionisolation
If the module number is not specified, the Note command will display the output for all the modules. Displays Fibre Channel flow-control mode of a switch. show system fc flow-control Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 201: Configuration Examples For Congestion Detection, Avoidance, And Isolation
Configuration Examples for Congestion Detection This example shows how to configure the FCoE congestion drop timeout to the default value of 500 milliseconds for a core port type in Cisco MDS NX-OS Release 8.1(1) and earlier releases: switch# configure terminal...
Page 202 200 mode edge This example shows how to configure the FCoE congestion drop timeout to the value of 200 milliseconds for an edge port type in Cisco MDS NX-OS Release 8.2(1) and later releases: switch# configure terminal...
Page 203: Configuration Examples For Congestion Avoidance
Cisco MDS NX-OS Release 8.2(1) and later releases: switch# configure terminal switch(config)# system timeout fcoe pause-drop default mode edge This example shows how to disable the FCoE pause drop timeout for a core port type in Cisco MDS NX-OS Release 8.1(1) and earlier releases: switch# configure terminal...
Page 204 This example shows how to configure the Fibre Channel no-credit drop timeout to the default value of 500 milliseconds for logical type edge: Note The no-credit drop timeout value is disabled by default. switch# configure terminal switch(config)# system timeout no-credit-drop default logical-type edge Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 205: Configuration Examples For Congestion Isolation
You need to disable the Congestion Isolation feature before disabling the ER_RDY flow-control mode. switch# configure terminal switch(config)# no feature congestion-isolation switch(config)# no system fc flow-control This example shows how to enable Congestion Isolation: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 206 2. Identifying the host that is using the interface. switch# show congestion-isolation pmon-list PMON detected list for vsan 1 : PWWN(FCID) =============================================== PMON detected list for vsan 2 : PWWN(FCID) =============================================== Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 207 PMON detected list for vsan 3 : PWWN(FCID) =============================================== <<<<<<<<<<<<<<< host behind interface fc2/9 removed from isolation PMON detected list for vsan 4 : PWWN(FCID) =============================================== PMON detected list for vsan 5 : PWWN(FCID) =============================================== Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 208: Verifying Congestion Detection, Avoidance, And Isolation
| 5. 10/14/12 21:46:51.215 46185 | | 6. 10/14/12 21:46:51.115 46183 | | 7. 10/14/12 21:46:51.015 46181 | | 8. 10/14/12 21:46:50.915 46179 | | 9. 10/14/12 21:46:50.815 46178 | |10. 10/14/12 21:46:50.715 ---------------------------------------------------------------- Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 209: Verifying Congestion Isolation
Verifying Congestion Isolation Note For 16-Gbps modules, 32-Gbps modules, and Cisco MDS 9700, 9148S, 9250i, and 9396S switches, if no-credit-drop timeout is configured, the maximum value of tx-slowport-oper-delay as shown in slow-port monitor events is limited by the no-credit-drop timeout. So, the maximum value for tx-slowport-oper-delay...
Page 210 36 ########### 30 ########### 24 ########### 18 ########### 12 ########### 6 ############ 0..5..1..1..2..2..3..3..4..4..5..5..6 TxWait per minute (last 60 minutes) # = TxWait (secs) 000000000000000000000000000000000000000000000000000000000000000000000000 3600 3240 2880 2520 2160 1800 1440 1080 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 211 36 ########### 30 ########### 24 ########### 18 ########### 12 ########### 6 ############ 0..5..1..1..2..2..3..3..4..4..5..5..6 RxWait per minute (last 60 minutes) # = RxWait (secs) 000000000000000000000000000000000000000000000000000000000000000000000000 3600 3240 2880 2520 2160 1800 1440 1080 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 212 | Thu Sep 14 14:45:56 2017 | Eth14/30(VL3) 47839 | Thu Sep 14 14:45:56 2017 | This example displays the error statistics onboard failure log (OBFL) for a switch: switch# show logging onboard error-stats Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 213 This example shows how to verify the list of devices that were detected as slow on a local switch: switch# show congestion-isolation pmon-list vsan 4 PMON detected list for vsan 4 : PWWN(FCID) =============================================== 10:00:00:00:c9:f9:16:8d(0xbe0000) Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 214 This example shows the list of devices that were manually configured using Congestion Isolation exclude list command on a local switch: switch# show congestion-isolation exclude-list vsan 4 Exclude list for vsan 4 : PWWN(FCID) (online/offline) ========================================================= 10:00:00:00:c9:f9:16:8d(0xbe0000) - (Online) Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 215: Configuring Trunking
Guidelines and Limitations, on page 205 • Default Settings, on page 209 • Configuring Trunking, on page 210 • Verifying Trunking Configuration, on page 212 • Configuration Example for F Port Trunking, on page 214 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 216: Finding Feature Information
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 217: Information About Trunking
Information About Trunking Information About Trunking Trunking, also known as VSAN trunking, is a feature specific to switches in the Cisco MDS 9000 Series Multilayer Switches. Trunking enables interconnect ports to transmit and receive frames in more than one VSAN, over the same physical link. Trunking is supported on E ports and F ports (see...
Page 218: Key Concepts
200) and that PortChannel becomes operational as a trunking F PortChannel, it is referred to as TF PortChannel. Cisco Port Trunking Protocol (PTP) is used to carry tagged frames. • TF-TN port link—A single link can be established to connect an F port to an HBA to carry tagged frames...
Page 219: Trunking Protocols
PTP also supports trunking PortChannels. Note The TF-TNP port link between a third-party NPV core and a Cisco NPV switch is established using the EVFP protocol. • A Fibre Channel VSAN is called Virtual Fabric and uses a VF_ID in place of the VSAN ID. By default, the VF_ID is 1 for all ports.
Page 220: Trunk Modes
Auto, on, or off No trunking F-NP link The preferred configuration on the Cisco MDS 9000 Series Multilayer Switches is one side of the trunk set to auto and the other side set to on. Note When connected to a third-party switch, the trunk mode configuration on E ports has no effect. The ISL is always in a trunking disabled state.
Page 221 Used for vendor-specific VSANs. FFFh Cannot be used as virtual fabric identifier. Note If the VF_ID of the F port and the N port do not match, then no tagged frames can be exchanged. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 222 • The ISL between switch 3 and switch 1 includes VSAN 1, 2, and 5. Consequently, VSAN 2 can only be routed from switch 1 through switch 3 to switch 2. Figure 7: Operational and Allowed VSAN Configuration Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 223: Guidelines And Limitations
General Guidelines and Limitations The trunking feature has the following general configuration guidelines and limitations: • You will see the switchport trunk mode off command added to F ports after upgrading from Cisco MDS NX-OS Release 8.1(1) to Cisco MDS NX-OS Release 8.2(1).
Page 224: Difference Between Te Ports And Tf-Tnp Ports
Configuring Trunking Difference Between TE Ports and TF-TNP Ports • When F port trunking or channeling is configured on a link, the switch cannot be downgraded to Cisco MDS SAN-OS Release 3.x and NX-OS Release 4.1(1b), or earlier. • If you are upgrading from a SAN-OS Release 3.x to NX-OS Release 5.0(1), and you have not created VSAN 4079, the NX-OS software will automatically create VSAN 4079 and reserve it for EVFP use.
Page 225: Trunking Misconfiguration Examples
VSANs, both VSANs will be mismatched. The trunking protocol validates the VSAN interfaces at both ends of a link to avoid merging VSANs (see Figure 8: VSAN Mismatch, on page 208). Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 226 Figure 9: Third-Party Switch VSAN Mismatch VSAN 2 and VSAN 3 are effectively merged with overlapping entries in the name server and the zone applications. Cisco DCNM-SAN helps detect such topologies. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 227: Default Settings
OFF on NPV switches. Allowed VSAN list 1 to 4093 user-defined VSAN IDs. Allowed VF-ID list 1 to 4093 user-defined VF-IDs. Trunking protocol on E ports Enabled. Trunking protocol on F ports Disabled. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 228: Configuring Trunking
Configuring Trunking Enabling the Cisco Trunking and Channeling Protocols To enable or disable the Cisco trunking and channeling protocol, perform these steps: Before you begin To avoid inconsistent configurations, disable all ports with a shutdown command before enabling or disabling the trunking protocols.
Page 229: Configuring An Allowed-Active List Of Vsans
Expands the specified VSAN (5) to the new allowed list. switch(config-if)# no switchport trunk allowed vsan 2-4 (Optional) Deletes VSANs 2, 3, and 4. switch(config-if)# no switchport trunk allowed vsan add 5 (Optional) Deletes the expanded allowed list. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 230: Verifying Trunking Configuration
11 input OLS, 12 LRR, 10 NOS, 28 loop inits 34 output OLS, 19 LRR, 17 NOS, 12 loop inits Displays the Trunking Protocol switch# show trunk protocol Trunk protocol is enabled Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 231 Vsan 1 is up, FCID is 0xef0000 Vsan 2 is up, FCID is 0xef0000 port-channel 6 is trunking Vsan 1 is up, FCID is 0xef0000 Vsan 2 is up, FCID is 0xef0000 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 232: Configuration Example For F Port Trunking
Configure the trunk mode to ON on the NPV switch: Example: switch(config-if)# switchport trunk mode on Step 7 Set the port administrative state on NPIV and NPV switches to ON: Example: switch(config)# interface fc1/2 switch(config-if)# shut Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 233 Configuring Trunking Configuration Example for F Port Trunking switch(config-if)# no shut Step 8 Save the configuration. Example: switch(config)# copy running-config startup-config Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 234 Configuring Trunking Configuration Example for F Port Trunking Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 235: Configuring Portchannels
• Verifying PortChannel Configuration, on page 239 • Configuration Examples for F and TF PortChannels, on page 244 • Configuration Examples for F and TF PortChannels (Dedicated Mode), on page 246 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 236: Finding Feature Information
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 237: Information About Portchannels
PortChannel link. Figure 10: PortChannel Flexibility PortChannels on Cisco MDS 9000 Series Multilayer Switches allow flexibility in configuration. This illustrates three possible PortChannel configurations: • PortChannel A aggregates two links on two interfaces on the same switching module at each end of a connection.
Page 238: F And Tf Portchannels
Cisco PTP and PCP protocols over Cisco EPP (ELS). Note If a Cisco MDS 9124 or 9134 switch is used as a core switch, only a nontrunking F PortChannel is supported. Trunking is not supported on this platform when NPIV enabled.
Page 239: Load Balancing
ID1 (DID1) based load balancing works. When the first frame in a flow is received on an interface for forwarding, link 1 is selected. Each subsequent frame in that flow is sent over the same link. No frame in SID1 and DID1 utilizes link 2. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 240 All remaining frames in that particular exchange are sent on the same link. For exchange 1, no frame uses link 2. For the next exchange, link 2 is chosen by the hash algorithm. Now all frames in exchange 2 use link 2. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 241: Portchannel Modes
PortChannels in releases prior to Release 2.0(1b), where the channel group mode is implicitly assumed to be ON. In Cisco MDS SAN-OS Releases 1.3 and earlier, the only available PortChannel mode was the ON mode. PortChannels configured in the ON mode require you to explicitly enable and disable the PortChannel member ports at either end if you add or remove ports from the PortChannel configuration.
Page 242: Portchannel Deletion
PortChannel. Adding an interface to a PortChannel increases the channel size and bandwidth of the PortChannel. Removing an interface from a PortChannel decreases the channel size and bandwidth of the PortChannel. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 243: Interface Addition To A Portchannel
If the operational parameters are incompatible, the compatibility check fails and the interface is placed in a suspended or isolated state based on the configured mode: • An interface enters the suspended state if the interface is configured in the ON mode. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 244: Forcing An Interface Addition
Any change in configuration applied to the associated PortChannel interface is propagated to all members of the channel group. A protocol to exchange PortChannel configurations is available in all Cisco MDS switches. This addition simplifies PortChannel management with incompatible ISLs. An additional autocreation mode enables ISLs with compatible parameters to automatically form channel groups without manual intervention.
Page 245: Channel Group Creation
• Autocreation protocol—Automatically aggregates compatible ports into a PortChannel. Channel Group Creation Note Channel groups are not supported on internal ports in the Cisco Fabric Switch for HP c-Class BladeSystem and the Cisco Fabric Switch for IBM BladeSystem. Assuming link A1-B1 comes up first (see...
Page 246: Autocreation
• You can enable or disable the autocreation feature on a per-port basis or for all ports in the switch. When this configuration is enabled, the channel group mode is assumed to be active. The default for this task is disabled. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 247: Manually Configured Channel Groups
When enabling autocreation in any switch in the Cisco MDS 9000 Series Multilayer Switches, we recommend that you retain at least one interconnected port between the switches without any autocreation configuration.
Page 248: Prerequisites For Portchannels
If all three conditions are not met, the faulty link is disabled. Enter the show interface command for that interface to verify that the PortChannel is functioning as required. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 249: Default Settings
Table 29: Default PortChannel Parameters Parameters Default PortChannels FSPF is enabled by default. Create PortChannel Administratively up. Default PortChannel mode ON mode on non-NPV and NPIV core switches. ACTIVE mode on NPV switches. Autocreation Disabled. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 250: Guidelines And Limitations
E ports to come up without manual configuration. • Any (or all) full line rate port(s) in the Cisco MDS 9100 Series can be included in a PortChannel. • The host-optimized ports in the Cisco MDS 9100 Series are subject to the same PortChannel rules as 32-port switching modules;...
Page 251: Valid And Invalid Portchannel Examples
• Since the FLOGI payload carries only the VF bits to trigger the use of a protocol after the FLOGI exchange, those bits will be overridden. In the case of the NPV switches, the core has a Cisco WWN and will try to initiate the PCP protocol.
Page 252 Configuring PortChannels Valid and Invalid PortChannel Examples Figure 17: Misconfigured Configurations Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 253: Configuring Portchannels
Step 3 switch(config-if)# channel mode active Configures the ACTIVE mode. switch(config-if)# no channel mode active (Optional) Reverts to the default ON mode. Deleting PortChannels To delete a PortChannel, perform these steps: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 254: Adding An Interface To A Portchannel
Adds physical interfaces 1/1, 1/2, 1/3, 1/4, and 1/5 to channel group 2. If channel group 2 does not exist, it is created. If the compatibility check is successful, the interfaces are operational and the corresponding states apply to these interfaces. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 255: Forcing An Interface Addition
Enters the selected range of physical interfaces. Step 4 switch(config-if)# no channel-group 2 Deletes the physical Fibre Channel interfaces in channel group 2. Enabling and Configuring Autocreation To configure automatic channel groups, perform these steps: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 256: Converting To Manually Configured Channel Groups
Converting to Manually Configured Channel Groups You can convert autocreated channel group to a user-configured channel group using the port-channel channel-group-number persistent EXEC command. If the PortChannel does not exist, this command is not executed. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 257: Verifying Portchannel Configuration
Displays the PortChannel Summary, on page 239. Displays the PortChannel Summary switch# show port-channel summary ------------------------------------------------------------------------------ Interface Total Ports Oper Ports First Oper Port ------------------------------------------------------------------------------ port-channel 77 port-channel 78 port-channel 79 fcip200 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 258 First operational port is fcip200 2 ports in total, 2 ports up Ports: fcip101 [up] fcip200 [up] * The show port-channel consistency command has two options: without details and with details. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 259 2 ports, first operational port is none fcip1 [down] fcip2 [down] port-channel 78: 2 ports, first operational port is none fc2/1 [down] fc2/5 [down] port-channel 79: 2 ports, first operational port is fcip200 fcip101 [up] fcip200 [up] Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 260 Administrative channel mode is active Operational channel mode is active Last membership update succeeded Channel is auto created First operational port is fc1/1 1 ports in total, 1 ports up Ports: fc1/1 [up] * Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 261 Displays the PortChannel Summary switch# show port-channel summary ------------------------------------------------------------------------------ Interface Total Ports Oper Ports First Oper Port ------------------------------------------------------------------------------ port-channel 1 port-channel 2 fc8/13 port-channel 3 port-channel 4 port-channel 5 fc8/3 port-channel 6 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 262: Configuration Examples For F And Tf Portchannels
1 switch(config-if)# no shut switch(config-if)# exit Step 5 Create the PortChannel on the NPV switch: Example: switch(config)# interface port-channel 1 switch(config-if)# switchport mode NP switch(config-if)# switchport rate-mode shared switch(config-if)# exit Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 263 Set the administrative state of all the PortChannel member interfaces in both NPIV core switch and the NPV switch to Example: switch(config)# interface fc1/1-3 switch(config-if)# shut switch(config-if)# >no shut switch(config)# interface fc2/1-3 switch(config-if)# shut switch(config-if)# >no shut Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 264: Configuration Examples For F And Tf Portchannels (Dedicated Mode)
4000 switch(config-if)# switchport rate-mode dedicated switch(config-if)# switchport trunk mode on switch(config-if)# channel-group 2 switch(config-if)# no shut switch(config-if)# exit Step 5 Create the PortChannel in dedicated mode on the NPV switch: Example: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 265 Set the administrative state of all the PortChannel member interfaces in both NPIV core switch and the NPV switch to Example: switch(config)# interface fc1/4-6 switch(config-if)# shut switch(config-if)# no shut switch(config)# interface fc3/1-3 switch(config-if)# shut switch(config-if)# no shut Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 266 Configuring PortChannels Configuration Examples for F and TF PortChannels (Dedicated Mode) Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 267: Configuring N Port Virtualization
• Information About N Port Virtualization, on page 251 • Guidelines and Limitations, on page 259 • Configuring N Port Virtualization, on page 262 • Verifying NPV Configuration, on page 266 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 268: Finding Feature Information
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 269: Information About N Port Virtualization
NPV mode do not join a fabric. They pass traffic between NPIV core switch links and end devices, which eliminates the domain IDs for these edge switches. NPV is supported by the following Cisco MDS 9000 switches only: • Cisco MDS 9132T 32-Gbps 32-Port Fibre Channel Switch •...
Page 270: N Port Virtualization
NPV makes use of NPIV to get multiple FCIDs allocated from the core switch on the NP port. Figure 20: Cisco NPV Configuration-Interface View, on page 253 shows a more granular view of an NPV configuration at the interface level. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 271: Npv Mode
CFS configuration commands. Configure CLI commands. clock Configure time-of-day clock. crypto Set crypto settings. event Event Manager commands. fcanalyzer Configure cisco fabric analyzer. feature Command to enable/disable features. fips Enable/Disable FIPS mode. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 272 Configure rate mode oversubscription limit. rmon Remote Monitoring. role Configure roles. snmp Configure snmp. snmp-server Configure snmp server. span Enter SPAN configuration mode. SSH to another system. switchname Configure system's network name. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 273: Np Ports
• The IP address of the NPV device is registered as the IP address in the name server registration of the NPV device. Note The BB_SCN of internal FLOGIs on NP ports is always set to zero. The BB_SCN is supported at the F-port of the NPV device. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 274: Default Port Numbers
Default Port Numbers Port numbers on NPV-enabled switches will vary depending on the switch model. For details about port numbers for NPV-eligible switches, see the Cisco NX-OS Series Licensing Guide. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 275: Npv Cfs Distribution Over Ip
NPV Traffic Management Auto Before Cisco MDS SAN-OS Release 3.3(1a), NPV supported automatic selection of external links. When a server interface is brought up, an external interface with the minimum load is selected from the available links. There is no manual selection on the server interfaces using the external links. Also, when a new external interface was brought up, the existing load was not distributed automatically to the newly available external interface.
Page 276: Multiple Vsan Support
By grouping devices into different NPV sessions based on VSANs, it is possible to support multiple VSANs on the NPV-enabled switch. The correct uplink must be selected based on the VSAN that the uplink is carrying. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 277: Guidelines And Limitations
NPV core switches. • NPV supports NPIV-capable servers. This capability is called nested NPIV. • Connecting two Cisco NPV switches together is not supported. • Only F, NP, and SD ports are supported in NPV mode. • In the case of servers that are booted over the SAN with NPV, if an NPV link failover occurs, servers will lose access to their boot LUN temporarily.
Page 278: Dpvm Configuration Guidelines
Guide. Connecting an NPIV-Enabled Cisco MDS Fabric Switch This topic provides information about connecting an NPIV-enabled Cisco MDS 9396S Multilayer Fabric Switch to an NPV switch running Cisco MDS NX-OS Release 6.2(13) and earlier. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 279 Connecting an NPIV-Enabled Cisco MDS Fabric Switch When trunking is enabled on the NPV ports of any MDS switch (released before the Cisco MDS 9396S Multilayer Fabric Switch) that runs on an Cisco MDS NX-OS Release 6.2(13) and earlier, and you connect an NPIV enabled Cisco MDS 9396S Multilayer Fabric Switch, use ports fc1/1 through fc1/63.
Page 280: Configuring N Port Virtualization
NPV cannot be enabled or disabled from the ASCII configuration file. You can enable or disable only from the command line. To configure NPV using the CLI, perform the following steps: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 281 Configures the port VSANs for the F ports on the NPV device. Step 11 switch(config-npv)# no npv enable Terminates session and disables NPV mode, which results in a reload of the NPV device. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 282: Configuring Npv Traffic Management
Enters configuration mode on the NPV. Step 2 switch(config)# npv auto-load-balance disruptive Enables disruptive load balancing on the NPV core switch. Step 3 switch (config)# no npv auto-load-balance disruptive Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 283 Configuring N Port Virtualization Enabling the Global Policy for Disruptive Load Balancing Disables disruptive load balancing on the NPV core switch. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 284: Verifying Npv Configuration
------------------------ VSAN:1 FCID:0x010000 ------------------------ port-wwn (vendor) :20:01:00:0d:ec:2f:c1:40 (Cisco) node-wwn :20:00:00:0d:ec:2f:c1:40 class :2,3 node-ip-addr :172.20.150.38 ipa :ff ff ff ff ff ff ff ff Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 285 Interface: fc1/1, VSAN: 2, FCID: 0x1c0000, State: Up Interface: fc1/2, VSAN: 3, FCID: 0x040000, State: Up Number of External Interfaces: 2 Server Interfaces: ================== Interface: fc1/7, VSAN: 2, NPIV: No, State: Up Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 286: Verifying Npv Traffic Management
To display the NPV internal traffic details, enter the show npv internal info traffic-map command. switch# show npv internal info traffic-map NPV Traffic Map Information: ------------------------------------------------------------ Server-If Last Change Time External-If(s) ------------------------------------------------------------ fc1/1 2015-01-15 03:24:16.247856 fc1/5 ------------------------------------------------------------ Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 287: Configuring Flexattach Virtual Pwwn
Guidelines and Limitations, on page 273 • Configuring FlexAttach Virtual pWWN, on page 274 • Verifying FlexAttach Virtual pWWN Configuration, on page 277 • Monitoring FlexAttach Virtual pWWN, on page 278 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 288: Finding Feature Information
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 289: Information About Flexattach Virtual Pwwn
WWN NAT and Fibre Channel ID (FC-ID) are WWN and Network Address Transport (NAT) is allocated on the virtual device, both primary and allocated to host bus adapter (HBA). secondary. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 290: Flexattach Virtual Pwwn Cfs Distribution
Security settings for the FlexAttach virtual pWWN feature are done by port security at the NPV core. Node WWN of the end device is used to provide physical security. For more details on enabling port security, refer to the Cisco MDS 9000 Series NX-OS Security Configuration Guide. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 291: Guidelines And Limitations
Following are recommended guidelines and requirements when deploying FlexAttach virtual pWWN: • FlexAttach configuration is supported only on NPV switches. • Cisco Fabric Services (CFS) IP version 4 (IPv4) distribution should be enabled. • Virtual WWNs should be unique across the fabric.
Page 292: Configuring Flexattach Virtual Pwwn
The interface mentioned in the interface value must be in a shut state. To assign virtual pWWN manually, perform this task: Before you begin • Some ports may be in automode, some in manual mode, and the virtual pWWNs need not be assigned. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 293: Mapping Pwwn To Virtual Pwwn
• To map pWWN to virtual pWWN, perform this task: Before you begin The interface must be in a shut state and the specified virtual pWWN should not be logged in. Step 1 Enter configuration mode: Example: Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 294 Mapping pWWN to Virtual pWWN switch# configure terminal Step 2 Map the pWWN to the virtual pWWN: Example: switch(config)# flex-attach virtual-pwwn vpwwn pwwn pwwn Step 3 Commit the configuration: switch(config)# flex-attach commit Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 295: Verifying Flexattach Virtual Pwwn Configuration
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE -------------------------------------------------------------------------- 0x010000 N 20:01:00:0d:ec:2f:c1:40 (Cisco) npv 0x010001 N 20:02:00:0d:ec:2f:c1:40 (Cisco) npv 0x010200 N 21:00:00:e0:8b:83:01:a1 (Qlogic) scsi-fcp:init 0x010300 N 21:01:00:e0:8b:32:1a:8b (Qlogic) scsi-fcp:init Total number of entries = 4 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 296: Monitoring Flexattach Virtual Pwwn
Virtual port WWN already This occurs when you try to Use an undefined virtual pWWN for a new exists configure an already defined interface. pWWN to a different interface. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 297: Configuring Port Tracking
Information About Port Tracking, on page 281 • Guidelines and Limitations, on page 282 • Default Settings, on page 283 • Configuring Port Tracking, on page 284 • Verifying Port Tracking Configuration, on page 288 Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 298: Finding Feature Information
To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the New and Changed chapter or the Feature History table below. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 299: Information About Port Tracking
When you enable this feature and explicitly configure the linked and tracked ports, the Cisco NX-OS software monitors the tracked ports and alters the operational state of the linked ports on detecting a link state change.
Page 300: Guidelines And Limitations
Before configuring port tracking, consider the following guidelines: • Verify that the tracked ports and the linked ports are on the same Cisco MDS switch. • Do not track a linked port back to itself (for example, Port fc1/2 to Port fc2/5 and back to Port fc1/2) to avoid recursive dependency.
Page 301: Default Settings
Table 33: Default Port Tracking Parameters , on page 283 lists the default settings for port tracking parameters. Table 33: Default Port Tracking Parameters Parameters Default Port tracking Disabled. Operational binding Enabled along with port tracking. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 302: Configuring Port Tracking
In this case, you must explicitly bring the port up when required. Enabling Port Tracking The port tracking feature is disabled by default in all switches in the Cisco MDS 9000 Series Multilayer Switches. When you enable this feature, port tracking is globally enabled for the entire switch.
Page 303: Information About Tracking Multiple Ports
1 be brought down. Direct link 1 will not be brought down if either 2 or 3 are still functioning as desired. Figure 23: Traffic Recovery Using Port Tracking Tracking Multiple Ports To track multiple ports, perform these steps: Step 1 switch# configure terminal Enters configuration mode. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 304: Information About Monitoring Ports In A Vsan
Enables tracking of the PortChannel in VSAN 2. switch(config-if)# no port-track interface port-channel 1 vsan 2 (Optional) Removes the VSAN association for the linked port. The PortChannel link remains in effect. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 305: Information Aboutforceful Shutdown
Configures the specified interface and enters the interface configuration submode. You can now configure tracked ports. Step 3 switch(config-if)# port-track force-shut Forcefully shuts down the tracked port. switch(config-if)# no port-track force-shut (Optional) Removes the port shutdown configuration for the tracked port. Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 306: Verifying Port Tracking Configuration
Configuring Port Tracking Verifying Port Tracking Configuration Verifying Port Tracking Configuration The show commands display the current port tracking settings for the Cisco MDS switch (see Examples Displays the Linked and Tracked Port Configuration, on page 288 Displays a Forced Shutdown Configuration , on page 289).
Page 307 Receive B2B Credit is 16 Receive data field Size is 2112 Beacon is turned off Port track mode is force_shut <--this port remains shut even if the tracked port is back up Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...
Page 308 Configuring Port Tracking Verifying Port Tracking Configuration Cisco MDS 9000 Series Interfaces Configuration Guide, Release 8.x...

Cisco MDS 9000 Series Configuration Manual

P R E F a C E Preface

CHAPTER 1 New and Changed Information

CHAPTER 2 Interface Overview

CHAPTER 3 Configuring Interfaces

CHAPTER 4 Configuring Fibre Channel Interfaces

CHAPTER 5 Configuring Interface Buffers

CHAPTER 6 Congestion Detection, Avoidance, and Isolation

CHAPTER 7 Configuring Trunking

CHAPTER 8 Configuring Portchannels

CHAPTER 9 Configuring N Port Virtualization

CHAPTER 10 Configuring Flexattach Virtual Pwwn

Quick Links

Need help?

Questions and answers

Related Manuals for Cisco MDS 9000 Series

Summary of Contents for Cisco MDS 9000 Series