Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
Configuring Interfaces
Downloads: This chapterpdf (PDF - 1.04 MB) | Feedback

Table of Contents

Configuring Interfaces

Feature Information

Information About Interfaces

Interface Description

Interface Modes

E Port

F Port

FL Port

NP Ports

TE Port

TF Port

TNP Port

SD Port

ST Port

Fx Port

B Port

Auto Mode

Interface States

Administrative States

Operational States

Reason Codes

Graceful Shutdown

Port Administrative Speeds

Auto sensing

Frame Encapsulation

Beacon LEDs

Speed LEDs

Bit Error Thresholds

SFP Transmitter Types

Port Guard

Port Monitor

Port Monitor Port Guard

Port Monitor Check Interval

Guidelines and Restrictions

Configuring Check Interval

Port Group Monitor

Local Switching

Slow Drain Device Detection and Congestion Avoidance

Management Interfaces

VSAN Interfaces

Internal CRC Detection and Isolation

Stages of Internal CRC Detection and Isolation

Prerequisites for Interfaces

Guidelines and Limitations

VSAN Interface Configuration Guidelines

Default Settings

Configuring Interfaces

Configuring Fibre Channel Interfaces

Setting the Interface Administrative State

Configuring Interface Modes

Configuring MAX NPIV Limit

Configuring System Default Port Mode F

Configuring ISL Between Two Switches

Configuring 10-Gbps Fibre Channel Mode

Configuring Port Administrative Speeds

Configuring Port Speed Group

Enabling 10-Gbps Speed Mode

Configuring the Interface Description

Specifying a Port Owner

Configuring Beacon Mode

Disabling Bit Error Threshold

Configuring Switch Port Attribute Default Values

Configuring Port Guard

Configuring Port Monitor

Enabling Port Monitor

Configuring a Port Monitor Policy

Configuring a Port Monitor Port Guard

Configuring Port Group Monitor

Enabling Port Group Monitor

Configuring a Port Group Monitor Policy

Reverting to the Default Policy for a Specific Counter

Turning Off the Monitoring of Specific Counter

Activating a Port Group Monitor Policy

Configuring Management Interfaces

Creating VSAN Interfaces

Configuring Slow Drain Device Detection and Congestion Avoidance

Configuring Congestion Frame Timeout Value for FCoE

Configuring Pause Frame Timeout for FCoE

Configuring Congestion Drop Timeout Value for FC

Configuring No Credit Frame Timeout Value for FC

Configuring Slow Port Monitor Timeout Value for FC

Displaying Credit Loss Recovery Actions

Configuring Average Credit Nonavailable Duration Threshold and Action

Configuring Internal CRC Detection and Isolation

Verifying Interfaces Configuration

Displaying Interface Information

Displaying Port Monitor Status and Policies

Displaying Port Group Monitor Status and Policies

Displaying Management Interface Configuration

Displaying VSAN Interface Information

Displaying Congestion Frame Timeout Value for FCoE

Displaying Pause Frame Timeout for FCoE

Displaying Congestion drop Timeout Value for FC

Displaying No Credit Frame Timeout Value for FC

Displaying Slow Port Monitor Events

TXWAIT History Graph

Feature Information

Table 2-1 lists the New and Changed features for Cisco MDS NX-OS Release 6.2(13).

Table 2-1 New and Changed features for Cisco MDS NX-OS Release 6.2(13).

Feature
Releases
Feature Information

Slow drain detection and mitigation enhancements.

Cisco MDS NX-OS Release 6.2.13

The slow drain device detection feature allows to detect slow drain devices that cause congestion in a network and also provides a congestion mitigation function.

  • Slowport monitoring is supported on 8-Gbps and advanced 8-Gbps modules.

The following command was introduced or modified by this feature:

—show process creditmon slowport-monitor-events

—system timeout slowport-monitor

  • Txwait: The advanced 8-Gpbs and 16-Gbps modules support slow port monitoring using the Txwait feature. The tx credit unavailable history is graphically represented using txwait-history graph.

The following commands were introduced or modified by this feature:

—show interface fcx/y counters

—show process creditmon txwait-history

  • On Board Failure Logging: The slowport-monitor events and the txwait delta values are logged into OBFL periodically.

The following commands were introduced or modified by this feature:

—show logging onboard slowport-monitor-events

—show logging onboard txwait

  • Port-monitor alerting: Three new counters— tx-slowport-count, tx-slowport-oper-delay, and txwait are added to the port monitor policy.

The following commands were introduced or modified by this feature:

—counter tx-slowport-count,

—counter tx-slowport-oper-delay

—counter txwait

  • Display of various debug logs related to slow drain.

The following command was introduced by this feature:

show tech-support slowdrain

Information About Interfaces

The main function of a switch is to relay frames from one data link to another. To relay the frames, the characteristics of the interfaces through which the frames are received and sent must be defined. The configured interfaces can be Fibre Channel interfaces, Gigabit Ethernet interfaces, the management interface (mgmt0), or VSAN interfaces.

This section includes the following topics:

Interface Description

For the Fibre Channel interfaces, you can configure the description parameter to provide a recognizable name for the interface. Using a unique name for each interface allows you to quickly identify the interface when you are looking at a listing of multiple interfaces. You can also use the description to identify the traffic or the use for that interface.

Interface Modes

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, ST port, and B port (see Figure 2-1). Besides these modes, each interface may be configured in auto or Fx port modes. These two modes determine the port type during interface initialization.

Figure 2-1 Cisco MDS 9000 Family Switch Port Modes

 


Note Interfaces are created in VSAN 1 by default. See the Cisco MDS 9000 Family NX-OS Fabric Configuration Guide.


Each interface has an associated administrative configuration and an operational status:

  • The administrative configuration does not change unless you modify it. This configuration has various attributes that you can configure in administrative mode.
  • The operational status represents the current status of a specified attribute like the interface speed. This status cannot be changed and is read-only. Some values may not be valid when the interface is down (for example, the operational speed).

Note When a module is removed and replaced with the same type of module, the configuration is retained. If a different type of module is inserted, then the original configuration is no longer retained.


Each interface is briefly described in the sections that follow.

E Port

In expansion port (E port) mode, an interface functions as a fabric expansion port. This port may be connected to another E port to create an Inter-Switch Link (ISL) between two switches. E ports carry frames between switches for configuration and fabric management. They serve as a conduit between switches for frames destined to remote N ports and NL ports. E ports support class 2, class 3, and class F service.

An E port connected to another switch may also be configured to form a PortChannel (see Chapter 6, “Configuring PortChannels”).

F Port

In fabric port (F port) mode, an interface functions as a fabric port. This port may be connected to a peripheral device (host or disk) operating as an N port. An F port can be attached to only one N port. F ports support class 2 and class 3 service.

FL Port

In fabric loop port (FL port) mode, an interface functions as a fabric loop port. This port may be connected to one or more NL ports (including FL ports in other switches) to form a public arbitrated loop. If more than one FL port is detected on the arbitrated loop during initialization, only one FL port becomes operational and the other FL ports enter nonparticipating mode. FL ports support class 2 and class 3 service.


Note FL port mode is not supported on 4-port 10-Gbps switching module interfaces.


NP Ports

An NP port is a port on a device that is in NPV mode and connected to the core switch via an F port. NP ports function like N ports except that in addition to providing N port operations, they also function as proxies for multiple, physical N ports.

For more details about NP ports and NPV, see Chapter7, “Configuring N Port Virtualization”

TE Port

In trunking E port (TE port) mode, an interface functions as a trunking expansion port. It may be connected to another TE port to create an extended ISL (EISL) between two switches. TE ports are specific to Cisco MDS 9000 Family switches. They expand the functionality of E ports to support the following:

  • VSAN trunking
  • Transport quality of service (QoS) parameters
  • Fibre Channel trace (fctrace) feature

In TE port mode, all frames are transmitted in EISL frame format, which contains VSAN information. Interconnected switches use the VSAN ID to multiplex traffic from one or more VSANs across the same physical link. This feature is referred to as trunking in the Cisco MDS 9000 Family switches (see Chapter 5, “Configuring Trunking”). TE ports support class 2, class 3, and class F service.

TF Port

In trunking F port (TF port) mode, an interface functions as a trunking expansion port. It may be connected to another trunked N port (TN port) or trunked NP port (TNP port) to create a link between a core switch and an NPV switch or an HBA to carry tagged frames. TF ports are specific to Cisco MDS 9000 Family switches. They expand the functionality of F ports to support VSAN trunking.

In TF port mode, all frames are transmitted in EISL frame format, which contains VSAN information. Interconnected switches use the VSAN ID to multiplex traffic from one or more VSANs across the same physical link. This feature is referred to as trunking in the Cisco MDS 9000 Family (see Chapter 5, “Configuring Trunking”). TF ports support class 2, class 3, and class F service.

TNP Port

In trunking NP port (TNP port) mode, an interface functions as a trunking expansion port. It may be connected to a trunked F port (TF port) to create a link to a core NPIV switch from an NPV switch to carry tagged frames.

SD Port

In SPAN destination port (SD port) mode, an interface functions as a switched port analyzer (SPAN). The SPAN feature is specific to switches in the Cisco MDS 9000 Family. It monitors network traffic that passes though a Fibre Channel interface. This monitoring is done using a standard Fibre Channel analyzer (or a similar switch probe) that is attached to an SD port. SD ports do not receive frames, they only transmit a copy of the source traffic. The SPAN feature is nonintrusive and does not affect switching of network traffic for any SPAN source ports (see the Cisco MDS 9000 Family NX-OS System Management Configuration Guide).

ST Port

In the SPAN tunnel port (ST port) mode, an interface functions as an entry point port in the source switch for the RSPAN Fibre Channel tunnel. The ST port mode and the remote SPAN (RSPAN) feature are specific to switches in the Cisco MDS 9000 Family. When configured in ST port mode, the interface cannot be attached to any device, and thus cannot be used for normal Fibre Channel traffic (see the Cisco MDS 9000 Family NX-OS System Management Configuration Guide).


Note ST port mode is not supported on the Cisco MDS 9124 Fabric Switch, the Cisco Fabric Switch for HP c-Class BladeSystem, and the Cisco Fabric Switch for IBM BladeCenter.


Fx Port

Interfaces configured as Fx ports can operate in either F port or FL port mode. The Fx port mode is determined during interface initialization depending on the attached N port or NL port. This administrative configuration disallows interfaces to operate in any other mode—for example, preventing an interface to connect to another switch.

B Port

While E ports typically interconnect Fibre Channel switches, some SAN extender devices, such as the Cisco PA-FC-1G Fibre Channel port adapter, implement a bridge port (B port) model to connect geographically dispersed fabrics. This model uses B ports as described in the T11 Standard FC-BB-2.

If an FCIP peer is a SAN extender device that only supports Fibre Channel B ports, you need to enable the B port mode for the FCIP link. When a B port is enabled, the E port functionality is also enabled and they coexist. If the B port is disabled, the E port functionality remains enabled (see the Cisco MDS 9000 Family NX-OS IP Services Configuration Guide).

Auto Mode

Interfaces configured in auto mode can operate in one of the following modes: F port, FL port, E port, TE port, or TF port. The port mode is determined during interface initialization. For example, if the interface is connected to a node (host or disk), it operates in F port or FL port mode depending on the N port or NL port mode. If the interface is attached to a third-party switch, it operates in E port mode. If the interface is attached to another switch in the Cisco MDS 9000 Family, it may become operational in TE port mode (see Chapter 5, “Configuring Trunking”).

TL ports and SD ports are not determined during initialization and are administratively configured.


Note Fibre Channel interfaces on Storage Services Modules (SSMs) cannot be configured in auto mode.


Interface States

The interface state depends on the administrative configuration of the interface and the dynamic state of the physical link.

Administrative States

The administrative state refers to the administrative configuration of the interface as described in Table 2-2 .

 

Table 2-2 Administrative States

Administrative State
Description

Up

Interface is enabled.

Down

Interface is disabled. If you administratively disable an interface by shutting down that interface, the physical link layer state change is ignored.

Operational States

The operational state indicates the current operational state of the interface as described in Table 2-3 .

 

Table 2-3 Operational States

Operational State
Description

Up

Interface is transmitting or receiving traffic as desired. To be in this state, an interface must be administratively up, the interface link layer state must be up, and the interface initialization must be completed.

Down

Interface cannot transmit or receive (data) traffic.

Trunking

Interface is operational in TE or TF mode.

Reason Codes

Reason codes are dependent on the operational state of the interface as described in Table 2-4 .

 

Table 2-4 Reason Codes for Interface States

Administrative Configuration
Operational Status
Reason Code

Up

Up

None.

Down

Down

Administratively down—If you administratively configure an interface as down, you disable the interface. No traffic is received or transmitted.

Up

Down

See Table 2-5 .


Note Only some of the reason codes are listed in Table 2-5.


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

 

Table 2-5 Reason Codes for Nonoperational States

Reason Code (long version)
Description
Applicable Modes

Link failure or not connected

The physical layer link is not operational.

All

SFP not present

The small form-factor pluggable (SFP) hardware is not plugged in.

Initializing

The physical layer link is operational and the protocol initialization is in progress.

Reconfigure fabric in progress

The fabric is currently being reconfigured.

Offline

The Cisco NX-OS software waits for the specified R_A_TOV time before retrying initialization.

Inactive

The interface VSAN is deleted or is in a suspended state.

To make the interface operational, assign that port to a configured and active VSAN.

Hardware failure

A hardware failure is detected.

Error disabled

Error conditions require administrative attention. Interfaces may be error-disabled for various reasons. For example:

  • Configuration failure.
  • Incompatible buffer-to-buffer credit configuration.

To make the interface operational, you must first fix the error conditions causing this state; and next, administratively shut down or enable the interface.

FC redirect failure

A port is isolated because a Fibre Channel redirect is unable to program routes.

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.

Isolation due to ELP failure

The port negotiation failed.

Only E ports and TE ports

Isolation due to ESC failure

The port negotiation failed.

Isolation due to domain overlap

The Fibre Channel domains (fcdomain) overlap.

Isolation due to domain ID assignment failure

The assigned domain ID is not valid.

Isolation due to the other side of the link E port isolated

The E port at the other end of the link is isolated.

Isolation due to invalid fabric reconfiguration

The port is isolated due to fabric reconfiguration.

Isolation due to domain manager disabled

The fcdomain feature is disabled.

Isolation due to zone merge failure

The zone merge operation failed.

Isolation due to VSAN mismatch

The VSANs at both ends of an ISL are different.

Nonparticipating

FL ports cannot participate in loop operations. It may happen if more than one FL port exists in the same loop, in which case all but one FL port in that loop automatically enters nonparticipating mode.

Only FL ports and TL ports

PortChannel administratively down

The interfaces belonging to the PortChannel are down.

Only PortChannel interfaces

Suspended due to incompatible speed

The interfaces belonging to the PortChannel have incompatible speeds.

Suspended due to incompatible mode

The interfaces belonging to the PortChannel have incompatible modes.

Suspended due to incompatible remote switch WWN

An improper connection is detected. All interfaces in a PortChannel must be connected to the same pair of switches.

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:

  • If you shut down an interface.
  • If a Cisco NX-OS software application executes a port shutdown as part of its function.

A graceful shutdown ensures that no frames are lost when the interface is shutting down. When a shutdown is triggered either by you or the Cisco NX-OS software, the switches connected to the shutdown link coordinate with each other to ensure that all frames in the ports are safely sent through the link before shutting down. This enhancement reduces the chance of frame loss.

A graceful shutdown is not possible in the following situations:

  • If you physically remove the port from the switch.
  • If in-order delivery (IOD) is enabled (for information about IOD, refer to the Cisco MDS 9000 Family NX-OS Fabric Configuration Guide).
  • If the Min_LS_interval interval is higher than 10 seconds. For information about FSPF global configuration, refer to the Cisco MDS 9000 Family NX-OS Fabric Configuration Guide.

Note This feature is only triggered if both switches at either end of this E port interface are MDS switches and are running Cisco SAN-OS Release 2.0(1b) or later, or MDS NX-OS Release 4.1(1a) or later.


Port Administrative Speeds

By default, the port administrative speed for an interface is automatically calculated by the switch.

For internal ports on the Cisco Fabric Switch for HP c_Class BladeSystem and Cisco Fabric Switch for IBM BladeCenter, a port speed of 1 Gbps is not supported. Auto-negotiation is supported between 2 Gbps and 4 Gbps only. Also, if the BladeCenter is a T chassis, then port speeds are fixed at 2 Gbps and auto-negotiation is not enabled.

Autosensing

Autosensing speed is enabled on all 4-Gbps and 8-Gbps switching module interfaces by default. This configuration enables the interfaces to operate at speeds of 1 Gbps, 2 Gbps, or 4 Gbps on the 4-Gbps switching modules, and 8 Gbps on the 8-Gbps switching modules. When autosensing is enabled for an interface operating in dedicated rate mode, 4 Gbps of bandwidth is reserved, even if the port negotiates at an operating speed of 1 Gbps or 2 Gbps.

To avoid wasting unused bandwidth on 48-port and 24-port 4-Gbps and 8-Gbps Fibre Channel switching modules, you can specify that only 2 Gbps of required bandwidth be reserved, not the default of 4 Gbps or 8 Gbps. This feature shares the unused bandwidth within the port group provided that it does not exceed the rate limit configuration for the port. You can also use this feature for shared rate ports that are configured for autosensing.


Tip When migrating a host that supports up to 2-Gbps traffic (that is, not 4 Gbps with autosensing capabilities) to the 4-Gbps switching modules, use autosensing with a maximum bandwidth of 2 Gbps. When migrating a host that supports up to 4-Gbps traffic (that is, not 8 Gbps with autosensing capabilities) to the 8-Gbps switching modules, use autosensing with a maximum bandwidth of 4 Gbps.


Frame Encapsulation

The switchport encap eisl command only applies to SD port interfaces. This command determines the frame format for all frames transmitted by the interface in SD port mode. If the encapsulation is set to EISL, all outgoing frames are transmitted in the EISL frame format, regardless of the SPAN sources.

The switchport encap eisl command is disabled by default. If you enable encapsulation, all outgoing frames are encapsulated, and you will see a new line (Encapsulation is eisl) in the show interface SD_port_interface command output. See the Cisco MDS 9000 Family NX-OS System Management Configuration Guide.

You can set the frame format to EISL for all frames transmitted by the interface in SD port mode. If you sent the frame encapsulation to EISL, all outgoing frames are transmitted in the EISL frame format, regardless of the SPAN sources. See the Cisco MDS 9000 Family NX-OS System Management Configuration Guide.

Beacon LEDs

Figure 2-2 displays the status, link, and speed LEDs in a 16-port switching module.

Figure 2-2 Cisco MDS 9000 Family Switch Interface Modes

1

Status LED1

3

Link LEDs 1 and speed LEDs2

2

1/2-Gbps Fibre Channel port group3

4

Asset tag4

1.See the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.

4.Refer to the Cisco MDS 9000 Family hardware installation guide for your platform.

Speed LEDs

Each port has one link LED on the left and one speed LED on the right.

The speed LED displays the speed of the port interface:

  • Off—The interface attached to that port is functioning at 1000 Mbps.
  • On (solid green)—The interface attached to that port is functioning at 2000 Mbps (for 2 Gbps interfaces).

The speed LED also displays if the beacon mode is enabled or disabled:

  • Off or solid green—Beacon mode is disabled.
  • Flashing green—The beacon mode is enabled. The LED flashes at one-second intervals.

Note Only 2-Gbps modules have speed LEDs.


Bit Error Thresholds

The bit error rate threshold is used by the switch to detect an increased error rate before performance degradation seriously affects traffic.

The bit errors can occur for the following reasons:

  • Faulty or bad cable.
  • Faulty or bad GBIC or SFP.
  • GBIC or SFP is specified to operate at 1 Gbps but is used at 2 Gbps.
  • GBIC or SFP is specified to operate at 2 Gbps but is used at 4 Gbps.
  • Short haul cable is used for long haul or long haul cable is used for short haul.
  • Momentary sync loss.
  • Loose cable connection at one or both ends.
  • Improper GBIC or SFP connection at one or both ends.

A bit error rate threshold is detected when 15 error bursts occur in a 5-minute period. By default, the switch disables the interface when the threshold is reached. You can enter a shutdown and no shutdown command sequence to re-enable the interface.

You can configure the switch to not disable an interface when the threshold is crossed. By default, the threshold disables the interface.

SFP Transmitter Types

The small form-factor pluggable (SFP) hardware transmitters are identified by their acronyms when displayed. Table 2-6 defines the acronyms used for SFPs.

The small form-factor pluggable (SFP) hardware transmitters are identified by their acronyms when displayed in the show interface brief command. If the related SFP has a Cisco-assigned extended ID, then the show interface and show interface brief commands display the ID instead of the transmitter type. The show interface transceiver command and the show interface fc slot / port transceiver command display both values for Cisco-supported SFPs. Table 2-6 defines the acronyms used in the command output (see the “Displaying Interface Information” section).

 

Table 2-6 SFP Transmitter Acronym Definitions

Definition
Acronym
Standard transmitters defined in the GBIC specifications

short wave laser

swl

long wave laser

lwl

long wave laser cost reduced

lwcr

electrical

elec

Extended transmitters assigned to Cisco-supported SFPs

CWDM-1470

c1470

CWDM-1490

c1490

CWDM-1510

c1510

CWDM-1530

c1530

CWDM-1550

c1550

CWDM-1570

c1570

CWDM-1590

c1590

CWDM-1610

c1610

Port Guard

The port guard feature is intended for use in environments where the system and application environment does not adapt quickly and efficiently to a port going down and back up, or to a port rapidly cycling up and down, which can happen in some failure modes. For example, if a system takes five seconds to stabilize after a port goes down, but the port is going up and down once a second, a more severe failure in the fabric might occur.

The port guard feature gives the SAN administrator the ability to prevent this issue from occurring in environments that are vulnerable to these problems. The port can be configured to stay down after the first failure or after a specified number of failures in a specified time period. This allows the SAN administrator to intervene and control the recovery, avoiding any problems caused by the cycling.

Using the port guard feature, you can restrict the number of error reports and bring a malfunctioning port to down state dynamically. A port can be configured to go into error-disabled state for specific types of failures.

A general link failure caused by link-down is the superset of all other causes. The sum of the number of all other causes equals to the number of link-down link failures. This means a port is brought to down state when it reaches the maximum number of allowed link failures or the number of specific causes.

The causes of link failure can be any of the following:

  • ESP trustsec-violation
  • Bit-errors
  • Signal loss
  • Sync loss
  • Link reset
  • Credit loss
  • Additional causes might be the following:

Not operational (NOS).

Too many interrupts.

Cable is disconnected.

Hardware recoverable errors.

The connected device rebooted (F ports only).

The connected linecard rebooted (ISL only).

Port Monitor

Port monitor helps to monitor the performance and status of ports and generate alerts when problems occur. You can configure thresholds for various counters and trigger an event when the values cross the threshold settings.

For rising and falling thresholds a syslog is generated only when the error count crosses the threshold values.

Beginning from the Cisco MDS NX-OS Release 6.2.15, along with the rising and falling threshold, the user can configure a new threshold called warning threshold to generate syslogs.


Note ISSD (In-service Software Downgrade) is blocked when warning threshold is configured.


Use Case—Warning Threshold

Let us consider 2 scenarios with the following configurations:

  • Rising threshold is 30
  • Warning threshold is 20
  • Falling threshold is 0

Example 2-1 When the error count is lesser than the rising threshold value

This example displays the syslog generated when the error count is lesser than the rising threshold value but has reached the warning threshold value:

switch(config)# 2016 Jan 6 06:08:37 switch %PMON-SLOT2-4-WARNING_THRESHOLD_REACHED_UPWARD: Invalid Words has reached warning threshold in the upward direction (port fc2/18 [0x1091000], value = 20).
 
switch(config)# 2016 Jan 6 06:09:27 switch %PMON-SLOT2-5-WARNING_THRESHOLD_REACHED_DOWNWARD: Invalid Words has reached warning threshold in the downward direction (port fc2/18 [0x1091000], value = 0).

 

In the first polling interval, the errors triggered for the counter (Invalid words) are 20, which has reached the warning threshold value. A syslog is generated indicating the error count is increasing (moves in the upward direction) and no further errors are triggered.

In the next polling interval, the error count decreases (moves in the downward direction) and a syslog is generated indicating the error count has decreased (moves in the downward direction).

Example 2-2 When the error count crosses the rising threshold value

This example displays the syslog generated when the error count crosses the rising threshold value:

switch(config)# 2016 Jan 6 06:51:35 sw-apex-40 %PMON-SLOT2-4-WARNING_THRESHOLD_REACHED_UPWARD: Invalid Words has reached warning threshold in the upward direction (port fc2/18 [0x1091000], value = 30).
2016 Jan 6 06:51:35 sw-apex-40 %PMON-SLOT2-3-RISING_THRESHOLD_REACHED: Invalid Words has reached the rising threshold (port=fc2/18 [0x1091000], value=30).
2016 Jan 6 06:51:36 sw-apex-40 %SNMPD-3-ERROR: PMON: Rising Alarm Req for Invalid Words counter for port fc2/18(1091000), value is 30 [event id 1 threshold 30 sample 2 object 4 fcIfInvalidTxWords]
2016 Jan 6 06:52:21 sw-apex-40 %PMON-SLOT2-5-WARNING_THRESHOLD_REACHED_DOWNWARD: Invalid Words has reached warning threshold in the downward direction (port fc2/18 [0x1091000], value = 0).
2016 Jan 6 06:52:21 sw-apex-40 %PMON-SLOT2-5-FALLING_THRESHOLD_REACHED: Invalid Words has reached the falling threshold (port=fc2/18 [0x1091000], value=0).
2016 Jan 6 06:52:21 sw-apex-40 %SNMPD-3-ERROR: PMON: Falling Alarm Req for Invalid Words counter for port fc2/18(1091000), value is 0 [event id 2 threshold 0 sample 2 object 4 fcIfInvalidTxWords]

 

The errors generated for the counter (Invalid Words) are 30 where it has crossed both the warning and rising threshold values. A syslog is generated when no further errors are triggered.

As there are no further errors in this poll interval, the consecutive polling interval will have no errors, and so the error count decreases (moves in downward direction) and reaches the falling threshold value which is zero. A syslog is generated for falling threshold.

The default port monitor policy has the following threshold values:

 

Counter
Threshold Type
Interval (Seconds)
Rising Threshold
Event
Falling Threshold
Event
Warning Threshold
PMON Port Guard

Link Loss

Delta

60

5

4

1

4

Not enabled

Not enabled

Sync Loss

Delta

60

5

4

1

4

Not enabled

Not enabled

Signal Loss

Delta

60

5

4

1

4

Not enabled

Not enabled

Invalid Words

Delta

60

1

4

0

4

Not enabled

Not enabled

Invalid CRCs

Delta

60

5

4

1

4

Not enabled

Not enabled

TX Discards

Delta

60

200

4

10

4

Not enabled

Not enabled

LR RX

Delta

60

5

4

1

4

Not enabled

Not enabled

LR TX

Delta

60

5

4

1

4

Not enabled

Not enabled

Timeout Discards

Delta

60

200

4

10

4

Not enabled

Not enabled

Credit Loss Reco

Delta

1

1

4

0

4

Not enabled

Not enabled

TX Credit Not Available

Delta

1

10%

4

0%

4

Not enabled

Not enabled

RX Datarate

Delta

60

80%

4

20%

4

Not enabled

Not enabled

TX Datarate

Delta

60

80%

4

20%

4

Not enabled

Not enabled

TX-Slowport-Count5

Delta

1

5

4

0

4

Not enabled

Not enabled

TX-Slowport-Oper-Delay6

Absolute

1

50 ms

80 ms (Advanced 8-Gbps modules)

4

0 ms

4

Not enabled

TXWait7

Delta

1

40%

4

0%

4

Not enabled

Not enabled

5.For all platforms if the default value for tx-slowport-count is modified then ISSD will be restricted. To proceed with ISSD, use the no form of the command to roll back to the default value.

6.For all platforms if the default value for tx-slowport-oper-delay is modified then ISSD will be restricted. To proceed with ISSD, use the no form of the command to roll back to the default value.

7.For all platforms if the default value for txwait is modified then ISSD will be restricted. To proceed with ISSD, use the no form of the command to roll back to the default value.


The unit for threshold values (Rising and Falling) differs across different counters.



Note TX-Slowport-Count is applicable only for 8-Gbps modules (DS-X9224-96K9, DS-X9248-96K9, and DS-X9248-48K9) in Cisco MDS 9500 series switches. In the default configuration, port-monitor sends alert when slowport condition is detected 5 times in 1 second for the configured slowport monitor timeout. (See system timeout slowport-monitor command).

  • TX-Slowport-Oper-Delay is applicable only for Advanced 8-Gbps and 16-Gbps modules. There are two defaults based on the module type:

For advanced 8-Gbps modules, the default rising-threshold is 80ms in a 1-second polling interval.

For 16-Gbps modules and switches, the default rising-threshold is 50ms in a 1-second polling interval.

  • Slowport monitor must be configured (system timeout slowport-monitor) in order to get alerts for “TX-Slowport-Count” and “TX-Slowport-Oper-Delay” for a particular port type. (See system timeout slowport-monitor command).
  • Portguard action for TX-Slowport-Oper-Delay (for Absolute type counter) is not supported.
  • TXWait is applicable only for advanced 8-Gbps and 16-Gbps modules. In the default configuration, port-monitor sends alert if the TX credit is not available for 400 milliseconds (40%) in 1 second.
  • TXWait can send alerts when there are multiple slowport events which have not hit the slowport-monitor threshold but together they hit the TXWait threshold configured. For example, if there are 40 discrete 10 ms intervals of 0 tx credits in 1 second, TX-Slowport-Oper-Delay does not find this but TXWait finds it and sends alert.

Three additional counters were added in Cisco NX-OS 5.2(2a) Release that are not included in the default policy:

  • err-pkt-from-port_ASIC Error Pkt from Port
  • err-pkt-to-xbar_ ASIC Error Pkt to xbar
  • err-pkt-from-xbar_ ASIC Error Pkt from xbar

The slowdrain port monitor policy has the following threshold values:

 

Counter
Threshold Type
Interval (Seconds)
Rising Threshold
Event
Falling Threshold
Event
PMON Port Guard

Credit Loss Reco

Delta

1

1

4

0

4

Not enabled

TX Credit Not Available

Delta

1

10%

4

0%

4

Not enabled


Note If no other port monitor policy is explicitly activated then the slowdrain policy is activated. The default policy only shows the default counter monitor values.


Port Monitor Port Guard

The port monitor port guard feature disables or shuts down a port when an event occurs. Depending on the configuration, when an event occurs the port is either error-disabled or flapped.

Port monitor port guard is a different or separate feature that functions based on the configuration of the errordisable command.


Note Port guard is not available on absolute counters.


Port Monitor Check Interval

Beginning from the Cisco MDS NX-OS Release 6.2.15 a new functionality called check interval is introduced to check errors at a lesser time interval compared to a poll interval.

Check interval polls for values frequently within a poll interval so that the errors are detected much early and appropriate action is taken.

With the existing poll interval, it is not possible to detect errors at an early stage. The user has to wait till the completion of the poll interval to detect the errors.

By default, the Check Interval functionality is not enabled.


Note It is recommended to configure the poll interval as a multiple of check interval.


Guidelines and Restrictions

  • Check interval should be configured before activating any port monitor policies.

Note The value of the Check interval is common across counters and policies.


  • Check interval is applicable to all the active port monitor policies configured.
  • User has to deactivate all active port monitor policies before enabling, modifying, or disabling the check interval functionality.
  • Check interval cannot be enabled when an active policy is configured.
  • Software downgrade to a version which does not support check interval functionality is restricted when the check interval functionality is enabled.

Example 2-3 Check Interval

Let us consider a scenario where the poll interval, rising threshold and check interval are configured with the following values:

  • Poll interval is 100 seconds
  • Rising threshold is 30
  • Check interval is 20 seconds

The check interval starts its interval, C1 along with poll-interval at P1. If an error occurs in between the check interval C2 and C3, which is greater than the configured rising-threshold value 30, an alert (syslog or trap or both) is generated at C3 alerting the user that the error has occurred at that particular port.

Configuring Check Interval

To configure check interval follow these steps:


Step 1 Enter the configuration mode:

switch# configure terminal
 

Step 2 Configure the check interval time to 30 seconds

switch(config)# port-monitor check-interval 30
 

To disable check interval use the following command:

switch(config)# no port-monitor check-interval

Port Group Monitor

Each line card or module has a predefined set of ports that share the same backplane bandwidth called port groups. While oversubscription is a feature, the port group monitor feature helps to monitor the spine bandwidth utilization. An alarm syslog is generated so that you can provision the ports across port groups evenly to manage the oversubscription better.

When the port group monitor feature is enabled and a policy consisting of polling interval in seconds, and the raising and falling thresholds in percentage are specified, port group monitor generates a syslog if a port group traffic goes above the specified percentage of the maximum supported bandwidth for that port group (for rx and for tx) and another syslog if the value falls below the specified threshold.

The default port group policy has the following threshold values:

Counter
Threshold Type
Interval (Seconds)
% Rising Threshold
% Falling Threshold

RX Performance

Delta

60

80

20

TX Performance

Delta

60

80

20


Note For all one rack unit boxes, when port group monitor is enabled, and if any of the threshold is met for the rx-performance and tx-performance counters, port group monitor is not supported.


Local Switching

Local switching can be enabled in Advanced 8-Gbps modules, which allows traffic to be switched directly with a local crossbar when the traffic is directed from one port to another on the same line card. By using local switching, an extra switching step is avoided, which decreases the latency.

When using local switching, note the following guidelines:

  • All ports need to be in shared mode, which usually is the default state. To place a port in shared mode, enter the switchport ratemode shared command.
  • E ports are not allowed in the module because they must be in dedicated mode.

Note Local switching is not supported on the Cisco MDS 9710 switch.


Slow Drain Device Detection and Congestion Avoidance

Most SAN edge devices use class 2 or class 3 Fibre Channel services that has the link-level flow control feature. The flow control feature allows a receiving port to back pressure the upstream sending port when the receiving port reaches its capacity to accept frames. When an edge device does not accept frames from the fabric for an extended period of time, it creates a condition in the fabric known as slow drain. If the upstream source of a slow edge device is an ISL, it results in credit starvation on that ISL. This credit starvation on the ISL can then affect the unrelated flows that use the same ISL link, making these flows to be affected by slow drain device's behavior.

Congestion avoidance focuses on minimizing or completely avoiding the held frames from consuming all the egress buffers of an edge port attached to a slow drain device. To achieve congestion avoidance, configure a no credit frame timeout value lower than the default 500 ms frame timeout which reduces the effects of the slow drain device on the fabric. Thus, the slow moving frames get dropped faster than the general frame timeout freeing buffers in the upstream ISL and allowing the unrelated flows to move continuously.


Note The early no-credit timeout functionality is mainly used for edge ports as they are directly connected to slow drain devices. Even though the early no-credit timeout functionality can be applied to core ports, we recommend that you do not use it. The early no-credit timeout functionality is not supported on Generation 1 modules.


Management Interfaces

You can remotely configure the switch through the management interface (mgmt0). To configure a connection on the mgmt0 interface, you must configure either the IP version 4 (IPv4) parameters (IP address, subnet mask, and default gateway) or the IP version 6 (IPv6) parameters so that the switch is reachable.

Before you begin to configure the management interface manually, obtain the switch’s IPv4 address and subnet mask, or the IPv6 address.

The management port (mgmt0) is autosensing and operates in full-duplex mode at a speed of 10, 100, or 1000 Mbps. Autosensing supports both the speed and the duplex mode. On a Supervisor-1 module, the default speed is 100 Mbps and the default duplex mode is auto. On a Supervisor-2 module, the default speed is auto and the default duplex mode is auto.


Note You need to explicitly configure a default gateway to connect to the switch and send IP packets or add a route for each subnet.


VSAN Interfaces

VSANs apply to Fibre Channel fabrics and enable you to configure multiple isolated SAN topologies within the same physical infrastructure. You can create an IP interface on top of a VSAN and then use this interface to send frames to this VSAN. To use this feature, you must configure the IP address for this VSAN. VSAN interfaces cannot be created for nonexisting VSANs.

Internal CRC Detection and Isolation

The internal Cyclic Redundancy Check (CRC) detection and isolation functionality enables the Cisco MDS switches to detect CRC errors and isolate the source of these errors that originate within a switch. This functionality is supported only in the Cisco MDS 9700 Series Multilayer Directors. It is disabled by default.

The modules that support this functionality are:

  • Cisco MDS 9700 48-Port 16-Gbps Fibre Channel Switching Module
  • Cisco MDS 9700 48-Port 10-Gbps Fibre Channel over Ethernet Switching Module
  • Cisco MDS 9700 Fabric Module 1

These errors are a separate class of CRC errors when compared to frames that arrive from outside the switch, with CRC errors. In the store mode and forward mode, frames with CRC errors are dropped at the ingress port and do not propagate through the system.

Internal CRC errors are usually caused by a fault in the system. Such faults may be transient, such as an ungracefully removed module, or permanent, such as a badly seated module, or, in rare cases, a failing or failed hardware component. The rate of errors depends on many factors and may range from very high to very low.

The error-rate threshold is configurable as a system-wide value, but separate error counts are maintained for each module to identify an error source.

Stages of Internal CRC Detection and Isolation

The five possible stages (5.) at which internal CRC errors may occur in a switch:

1. Ingress buffer of a module

2. Ingress crossbar of a module

3. Crossbar of a fabric module

4. Egress crossbar of a module

5. Egress buffer of a module

Figure 2-3 Stages of Internal CRC Detection and Isolation

Ingress Buffer of a Module

There are multiple ingress buffers on each module. When the CRC error rate of an ingress buffer reaches the threshold, the entire module is shut down.

Ingress Crossbar of a Module

Ingress crossbar is an ASIC complex on an ingress module that switches traffic from ingress buffers to fabric modules. When the CRC error rate of ingress module crossbar reaches the threshold, the entire module is shut down.

Crossbar of a Fabric Module

Crossbar is an ASIC complex on a fabric module that switches traffic from an ingress module to an egress module.

When the CRC error rate of a crossbar reaches the threshold, if there is more than one fabric module in the corresponding switch, the host fabric module is shut down. If the switch has only one fabric module, the module connected to the fabric module link on which the errors occurred is shut down.

Egress Crossbar of a Module

Egress crossbar is an ASIC complex on an egress module that switches traffic from fabric modules to egress buffers. When the CRC error-rate of an egress module crossbar reaches the threshold, the entire module is shut down.

Egress Buffer of a Module

There are multiple egress buffers on each module. When the CRC error rate of an egress buffer reaches the threshold, the entire module is shut down.

Prerequisites for Interfaces

Before you begin configuring the interfaces, ensure that the modules in the chassis are functioning as designed. 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 NX-OS Fundamentals Configuration Guide.

Guidelines and Limitations

This section includes the following topics:

VSAN Interface Configuration Guidelines

Follow these guidelines when creating or deleting VSAN interfaces:

  • Create a VSAN before creating the interface for that VSAN. If a VSAN does not exist, the interface cannot be created.
  • Create the interface VSAN; it is not created automatically.
  • If you delete the VSAN, the attached interface is automatically deleted.
  • Configure each interface only in one VSAN.

Tip After configuring the VSAN interface, you can configure an IP address or Virtual Router Redundancy Protocol (VRRP) feature. See the Cisco MDS 9000 Family NX-OS IP Services Configuration Guide.


Default Settings

 

Table 2-7 lists the default settings for interface parameters.

 

Table 2-7 Default Interface Parameters

Parameters
Default

Interface mode

Auto

Interface speed

Auto

Administrative state

Shutdown (unless changed during initial setup)

Trunk mode

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

Internal CRC Error Handling

Disabled

Configuring Interfaces

This section includes the following topics:

For more information on configuring mgmt0 interfaces, refer to the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide and Cisco MDS 9000 Family NX-OS IP Services Configuration Guide.

For more information on configuring Gigabit Ethernet interfaces, see the Cisco MDS 9000 Family NX-OS IP Services Configuration Guide.

Configuring Fibre Channel Interfaces

Detailed Steps

To configure a Fibre Channel interface, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1

switch(config-if)#

Selects a Fibre Channel interface and enters interface configuration submode.

When a Fibre Channel interface is configured, it is automatically assigned a unique world wide name (WWN). If the interface’s operational state is up, it is also assigned a Fibre Channel ID (FC ID).

To configure a range of interfaces, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1 - 4, fc2/1 - 3

switch(config-if)#

Selects the range of Fibre Channel interfaces and enters interface configuration submode3.

In this command, provide a space before and after the comma.

For the Cisco Fabric Switch for HP c-Class BladeSystem and the Cisco Fabric Switch for IBM BladeCenter, you can configure a range of interfaces among internal ports or external ports, but you cannot mix both interface types within the same range. For example, “bay 1-10, bay 12” or “ext 0, ext 15-18” are valid ranges, but “bay 1-5, ext 15-17” is not.

Setting the Interface Administrative State

Detailed Steps

To gracefully shut down an interface, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1

Selects a Fibre Channel interface and enters interface configuration submode.

Step 3

switch(config-if)# shutdown

Gracefully shuts down the interface and administratively disables traffic flow (default).

To enable traffic flow, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1

Selects a Fibre Channel interface and enters interface configuration submode.

Step 3

switch(config-if)# no shutdown

Enables traffic flow to administratively allow traffic when the no prefix is used (provided the operational state is up).

Configuring Interface Modes

Detailed Steps

To configure the interface mode, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1

switch(config-if)#

Selects a Fibre Channel interface and enters interface configuration submode.

Step 3

switch(config-if)# switchport mode F

switch(config-if)#

Configures the administrative mode of the port. You can set the operational state to auto, E, F, FL, Fx, TL, NP, or SD port mode.

Note Fx ports refers to an F port or an FL port (host connection only), but not E ports.

switch(config-if)# switchport mode auto

switch(config-if)#

Configures the interface mode to auto-negotiate an E, F, FL, or TE port mode (not TL or SD port modes) of operation.

Note TL ports and SD ports cannot be configured automatically. They must be administratively configured.

Note You cannot configure Fibre Channel interfaces on SSMs in auto mode.

Configuring MAX NPIV Limit

Restrictions

  • Both max-npiv-limit and trunk-max-npiv-limit can be configured on a port or port channel. If the port or port channel becomes a trunking port then trunk-max-npiv-limit is used for limit checks.

Detailed Steps

To configure the maximum NPIV limit, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc 3/29

switch(config-if)#

Selects a Fibre Channel interface and enters interface configuration submode.

Step 3

switch(config-if)# switchport mode F

switch(config-if)#

Configures the switch port mode F on the Fibre Channel interface.

switch(config-if)# switchport max-npiv-limit 100

switch(config-if)#

Specifies the maximum login value for this port. The range is from 1 to 256.

Configuring System Default Port Mode F

The system default switchport mode F command sets the administrative mode of all Fibre Channel ports to mode F, while avoiding traffic disruption caused by the formation of unwanted Inter-Switch Links (ISLs). This command is part of the setup utility that runs during bootup after a write erase or reload. It can also be executed from the command line in configuration mode. This command changes the configuration of the following ports to administrative mode F:

  • All ports that are down and that are not out-of-service.
  • All F ports that are up, whose operational mode is F, and whose administrative mode is not F.

This command does not affect the configuration of the following ports:

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

Restrictions

  • To ensure that ports that are part of ISLs do not get changed to port mode F, configure the ports in port mode E, rather than in auto mode.
  • When the command is executed from the command line, switch operation remains graceful. No ports are flapped.

Detailed Steps

To set the administrative mode of Fibre Channel ports to mode F in the CLI, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# system default switchport mode F

Sets the administrative mode of Fibre Channel ports to mode F (if applicable).

 

switch(config)# no system default switchport mode F

Sets the administrative mode of Fibre Channel ports to the default (unless user configured).


Note For detailed information about the switch setup utility, see the Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.


Example 2-4 shows the command in the setup utility, and Example 2-5 shows the command from the command line.

Example 2-4 Setup Utility

Configure default switchport mode F (yes/no) [n]: y

Example 2-5 Command Line

switch(config)# system default switchport mode F
 

Configuring ISL Between Two Switches


Note Ensure that Fibre Channel cable is connected between the ports and do a no-shut operation on each port.


E-port mode is used when the port functions as one end of an Inter-Switch Link (ISL) setting. When you set the port mode to E, you restrict the port coming up as an E port (trunking or non-trunking, depending on the trunking port mode).

switch# conf t --------> Enter configuration commands, one per line. End with CNTL/Z.
switch(config)# interface fc <Slot No/Port No>
switch(config-if)# switchport mode E
switch(config-if)# end
 

Be sure that you follow this action on both the switches between which you are attempting to bring up the ISL link.

Configuring 10-Gbps Fibre Channel Mode

The 48-port 8-Gbps Advanced Fibre Channel module (DS-X9248-256K9) and the 32-port 8-Gbps Advanced Fibre Channel module (DS-X9232-256K9) can switch between two speed modes—the 1, 2, 4, 8, or 10 Gbps. By default, the modules are online in the 1, 2, 4, or 8 Gbps modes when they are loaded for the first time.

Similarly, the 16-Gbps Fibre Channel module (DS-X9448-768K9) can switch between 2, 4, 8, 16, or 10 Gbps. By default, the modules are online in the 2, 4, 8, or 16 Gbps modes when they are loaded for the first time.

8-Gbps linecards are applicable to Cisco MDS 9513 Multilayer Directors and 16-Gbps linecards are applicable to Cisco MDS 9710 Multilayer Directors.

There are two ways to change the ports to the 10-Gbps speed mode:

  • Using the 10G-speed mode command, which is the recommended method.

Note When 10G-speed mode is configured for a port group in 16-Gbps modules, all ports in the port group will be in 10-Gbps mode, where as in 8-Gbps modules, only certain ports in a port group will be in 10-Gbps mode and the rest will be in out-of-service state.


  • Using the generic speed configuration switchport speed command which has certain constraints.

The following conditions apply when the ports in the module can be configured to 10-Gbps speed mode:

  • The ports in the module can be configured to 10-Gbps speed only when the DS-13SLT-FAB3 module bandwidth is 256 G. Any other combination of fabric modules will not let the ports come up in 10 Gbps.
  • When in 10-Gbps mode, the ports in the module that are not 10-Gbps capable are disabled and will be in out-of-service state.
  • The ports function only in full rate mode. They cannot be moved to shared rate mode.
  • The ports cannot be configured in any other speed.
  • Ports that are capable of 10 Gbps that are disabled or out-of-service cannot be put back in service using the no out-of-service command. To put these ports back in service, all ports in the module first have to be moved to the out-of-service state. Then they can be brought back to the in-service state.
  • Local switching must be disabled, otherwise, ports cannot be configured in dedicated mode.

Only certain ports on the 48-port and 32-port 8-Gbps Advanced Fibre Channel modules are 10-Gbps capable. When running in 10-Gbps mode, the non-10-Gbps ports cannot be operational. They have to be either in shut state or out-of-service state.

Detailed Steps

To configure the interface mode, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1-12

switch(config-if)#

Selects a Fibre Channel interface and enters interface configuration submode.

Ensure that one full ASIC range of ports are selected before executing this command. For example, /1-12 for a 48-port module or fcY/1-8 for a 32-port module.

The first ASIC on the 48-port module has ports fc1/1-12.

For DS-X9448-768K9, each ASIC supports 8 front panel ports.

For example, fc1/1-8.

Step 3

switch(config-if)# 10G-speed-mode

Configures all the ports (fc1 to 12) to out-of-service state.

Moves the ports that are capable of a 10-Gbps configuration (fc1/4-8 and fc1/10) to in-service state.

Sets the speed on ports fc1/4-8 and fc1/10 to 10Gbps.

Sets port modes on these ports to dedicated.

Performs a no shut on these ports.

For DS-X9248-256K9 module, the 10G-speed-mode command will not work for interface ranges other than 1–12, 13–24, 25–36 or 37–48 only.

For DS-X9232-256K9 module, the 10G-speed-mode command will not work for interface ranges other than 1–8, 9–16, 17–24 or 25–32 only.

For DS-X9448-768K9 module, the 10G-speed-mode command will not work for interface ranges other than 1–8, 9–16, 17–24, 25–32, 33–40 or 41–48.

switch(config-if)# no 10G-speed-mode

Reverts the settings and puts all the ports (fc1 to 12) in out-of-service state and moves them to in-service state.

Configuring Port Administrative Speeds

Restrictions

  • Changing the port administrative speed is a disruptive operation.

Detailed Steps

To configure the port speed of the interface, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc 1/1

Selects the fc interface and enters interface configuration mode.

Step 3

switch(config-if)# switchport speed 1000

Configures the port speed of the interface to 1000 Mbps.

The number indicates the speed in megabits per second (Mbps).

switch(config-if)# switchport speed 10000

Configures the port speed of the interface to 10000 Mbps (for 10Gbps).

All the 10-Gbps capable interfaces, except the interface that is being configured, must be in the out-of-service state. At least one other 10-Gbps capable interface must be in the in-service state.

switch(config-if)# no switchport speed

Reverts the factory default (auto) administrative speed of the interface.

Configuring Port Speed Group

Detailed Steps

To configure the port speed group of the interface, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc 1/1

Selects the fc interface and enters interface configuration mode.

Step 3

switch(config-if)# speed group 10g

Configures the port speed group to 10 Gbps.

The preferred way of changing the speed group is the 10g-speed-mode command.

switch(config-if)# no speed group 10g

Unsets the port speed group and reverts to the factory default (auto) administrative speed group of the interface.

Enabling 10-Gbps Speed Mode

Cisco MDS 9000 Family Advanced 8-Gbps modules support 10-Gbps ports. However, a group of ports must be put into 10-Gbps mode in order to use the port speed group feature. Individual ports cannot be put into 10-Gbps mode.

  • For the 48-port Advanced 8-Gbps module the group size is 12 ports (1-12, 13-24, and so on). When the group is put into 10-Gbps mode, the ports 1-3, 9, and 11-12 in that group are unavailable for use and shows outOfServc or Out of Service.
  • For the 32-port Advanced 8-Gbps module the group size is 8 ports(1-8, 9-16, and so on). When the group is put into 10-Gbps mode, the ports 1 and 7 in that group are unavailable for use and shows outOfServc or Out of Service.
  • For the 48-port 16-Gbps module in the Cisco MDS 9700 switch and the Cisco MDS 9396S switch the group size is 8 ports. When the group is put into 10-Gbps mode, all the 8 ports are available for use.

To enable the 10-Gbps speed mode on a group of ports, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1-12

Selects the fc interface and enters interface configuration mode.

Step 3

switch(config-if)# 10g-speed-mode

Changes the speed group to 10-Gbps.

switch(config-if)# no 10g-speed-mode

Reverts to defaults speed group setting.


Note In Cisco NX-OS Release 5.2(8c) the default speed group for the supported switching modules are 1-, 2-, 4-, and 8-Gbps.


Configuring the Interface Description

The interface description can be any alphanumeric string.

Detailed Steps

To configure a description for an interface, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1

switch(config-if)#

Selects a Fibre Channel interface and enters interface configuration submode.

Step 3

switch(config-if)# switchport description cisco-HBA2

Configures the description of the interface. The string can be up to 80 characters long.

switch(config-if)# no switchport description

Clears the description of the interface.

Specifying a Port Owner

Using the port owner feature, you can specify the owner of a port and the purpose for which a port is used so that the other administrators are informed.


Note The port guard and port owner features are available for all ports regardless of the operational mode.


Detailed Steps

To specify or remove the port owner, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1

Selects the port interface.

Step 3

switch(config)# switchport owner description

Specifies the owner of the switch port. The description can include name of the owner and the purpose for which the port is used. The description can be up to 80 characters long.

switch(config)# no switchport owner

Removes (default) the port owner description.

To display the owner description specified for a port, use the following commands:

switch# show running interface fc module-number/interface-number
switch# show port internal info interface fc module-number/interface-number
 

Configuring Beacon Mode

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. Configuring the beacon mode has no effect on the operation of the interface.

Detailed Steps

To enable beacon mode for a specified interface or range of interfaces, follow these steps:

Command
Purpose

Step 1

switch# config t

switch(config)#

Enters configuration mode.

Step 2

switch(config)# interface fc1/1

switch(config-if)#

Selects a Fibre Channel interface and enters interface configuration submode.

Step 3

switch(config-if)# switchport beacon

Enables the beacon mode for the interface.

switch(config-if)# no switchport beacon

Disables the beacon mode for the interface.

Troubleshooting Tips

  • The flashing green light turns on automatically when an external loopback is detected that causes the interfaces to be isolated. The flashing green light overrides the beacon mode configuration. The state of the LED is restored to reflect the beacon mode configuration after the external loopback is removed.

Disabling Bit Error Threshold

Detailed Steps

To disable the bit error threshold for an interface, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1

switch(config-if)#

Selects a Fibre Channel interface and enters interface configuration submode.

Step 3

switch(config-if)# switchport ignore bit-errors

Prevents the detection of bit error threshold events from disabling the interface.

switch(config-if)# no switchport ignore bit-errors

Prevents the detection of bit error threshold events from enabling the interface.

Troubleshooting Tips

  • Regardless of the setting of the switchport ignore bit-errors command, the switch generates a syslog message when bit-error threshold events are detected.

Configuring Switch Port Attribute Default Values

You can configure attribute default values for various switch port attributes. These attributes will be applied globally to all future switch port configurations, even if you do not individually specify them at that time.

Detailed Steps

To configure switch port attributes, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# no system default switchport shutdown

switch(config)#

Configures the default setting for administrative state of an interface as Up. (The factory default setting is Down).

This command is applicable only to interfaces for which no user configuration exists for the administrative state.

switch(config)# system default switchport shutdown

switch(config)#

Configures the default setting for administrative state of an interface as Down. This is the factory default setting.

This command is applicable only to interfaces for which no user configuration exists for the administrative state.

switch(config)# system default switchport trunk mode auto

switch(config)#

Configures the default setting for administrative trunk mode state of an interface as Auto.

The default setting is trunk mode on.

Configuring Port Guard

Detailed Steps

To enable or disable the port guard for a port, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface fc1/1

Selects the port interface.

Step 3

switch(config-if)# errdisable detect cause link-down

Brings the port to down state if the link flaps once.

switch(config-if)# errdisable detect cause link-down [ num-times number duration seconds ]

Enables the port guard configuration for the interface. Brings the port to down state if the link flaps for the number of instances within the specified seconds.

switch(config-if)# no errdisable detect cause link-down

Removes (default) the port guard configuration for the interface. The link resumes flapping and sending error reports normally.

Step 4

switch(config-if)# errdisable detect cause { trustsec-violation | bit-errors | credit-loss | link-reset | signal-loss | sync-loss }

Brings the port to down state if the specified error occurs even once.

switch(config-if)# errdisable detect cause { trustsec-violation | bit-errors | credit-loss | link-reset | signal-loss | sync-loss } [ num-times number duration seconds ]

Brings the port to down state if the specified error occurs for the number of instances within the specified seconds.

switch(config-if)# no errdisable detect cause { trustsec-violation | bit-errors | credit-loss | link-reset | signal-loss | sync-loss }

Removes (default) the port guard configuration for the interface. The link resumes flapping and sending error reports normally.

Examples

This example shows how to configure port guard to bring a port to down state if the link flaps 5 times within 120 seconds based on multiple causes:

Switch# config t
Switch (config)# interface fc1/1
Switch (config-if)# errdisable detect cause link-down num-times 5 duration 120
Switch (config-if)# errdisable detect cause bit-errors num-times 5 duration 120
Switch (config-if)# errdisable detect cause credit-loss num-times 5 duration 120
 

The above example sets the configuration to the following status:

  • The port will be error-disabled due to bit errors if the port suffers link failure due to bit errors 5 times in 120 seconds.
  • The port will be error-disabled due to credit loss if the port suffers link failure due to credit loss 5 times in 120 seconds.
  • The port will be error-disabled due to link down if the port suffers link failure due to bit errors 2 times and link-failure due to credit loss 3 times in 120 seconds.

This example shows the internal information about a port in down state because of TrustSec violation:

Switch# show interface fc8/3
fc8/3 is down (Error disabled - port down due to trustsec violation)
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 21:c3:00:0d:ec:10:57:80
Admin port mode is E, trunk mode is on
snmp link state traps are enabled
Port vsan is 1
Receive data field Size is 2112
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
11274 frames input, 1050732 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
11242 frames output, 971900 bytes
0 discards, 0 errors
11 input OLS, 34 LRR, 10 NOS, 0 loop inits
72 output OLS, 37 LRR, 2 NOS, 0 loop inits
Interface last changed at Sun Nov 27 07:34:05 1988

Troubleshooting Tips

  • Link down is the superset of all other causes. A port is brought to down state if the total number of other causes equals to the number of allowed link-down failures.
  • Even if the link does not flap due to failure of the link, and port guard is not enabled, the port goes into a down state if too many invalid FLOGI requests are received from the same host. Use the shut and the no shut commands consecutively to bring up the link.

Enabling Port Monitor

Detailed Steps

To enable port monitor, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# port-monitor enable

Enables (default) port monitoring.

switch(config)# no port-monitor enable

Disables port monitoring.

Configuring a Port Monitor Policy

Detailed Steps

To configure a port monitor policy, follow these steps:Activating a Port Monitor Policy

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# port-monitor name policyname

Specifies the policy name and enters the port monitoring policy configuration mode.

switch(config)# no port-monitor name policyname

Removes the policy.

switch# config t

Enters configuration mode.

Step 3

switch(config-port-monitor)# port-type access-port

Applies the policy to the access ports.

switch(config-port-monitor)# port-type trunks

Applies the policy to the trunk ports.

switch(config-port-monitor)# port-type all

Applies the policy to all ports.

Step 4

switch(config-port-monitor)# counter credit-loss-reco poll-interval seconds delta rising-threshold count1 event event-id falling threshold count2 event event-id

Specifies the delta credit loss recovery counter, poll interval in seconds, the threshold limits, and the event IDs of events.

Step 5

switch(config-port-monitor)# monitor counter err-pkt-from-port8

switch(config-port-monitor)# counter err-pkt-from-port 1 poll-interval seconds delta rising-threshold eventcount1 event event-id falling-threshold eventcount2 event event-id

Activates the err-pkt-from-port counter.

Specifies the delta err-pkt-from-port counter, poll interval in seconds, the threshold limits, and the event IDs of events.

Step 6

switch(config-port-monitor)# monitor counter err-pkt-from-xbar 1

switch(config-port-monitor)# counter err-pkt-from-xbar 1 poll-interval seconds delta rising-threshold eventcount1 event event-id

Activates the err-pkt-from-xbar counter.

Specifies the delta err-pkt-from-xbar counter, poll interval in seconds, the thresholds in the count of error frame events, and the event IDs of events.

Step 7

switch(config-port-monitor)# monitor counter err-pkt-to-xbar 1

switch(config-port-monitor)# counter err-pkt-to-xbar 1 poll-interval seconds delta rising-threshold eventcount1 event event-id falling-threshold eventcount2 event event-id

Activates the err-pkt-to-xbar counter.

Specifies the delta err-pkt-to-xbar counter, poll interval in seconds, the thresholds in the count of error frame events, and the event IDs of events.

Step 8

switch(config-port-monitor)# counter invalid-crc poll-interval seconds delta rising-threshold count1 event event-id falling-threshold count2 event event-id

Specifies the delta invalid CRC, poll interval in seconds, the threshold limits, and the event IDs of events to be triggered.

Step 9

switch(config-port-monitor)# counter invalid-words poll-interval seconds delta rising-threshold count1 event event-id falling-threshold count2 event event-id

Specifies the delta invalid words, poll interval in seconds, the threshold limits, and the event IDs of events to be triggered.

Step 10

switch(config-port-monitor)# counter link-loss poll-interval seconds delta rising-threshold count1 event event-id falling-threshold count2 event event-id

Specifies the delta link failure counter, poll interval in seconds, the thresholds limits, and the event IDs of events to be triggered.

Step 11

switch(config-port-monitor)# counter rx-datarate poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id

Specifies the delta for the counter Rx (receive) datarate poll interval in seconds and thresholds in percentage.

Step 12

switch(config-port-monitor)# counter signal-loss poll-interval seconds delta rising-threshold count1 event event-id falling-threshold count2 event event-id

Specifies the delta signal loss poll interval in seconds, the thresholds limits, and the event IDs of events to be triggered.

Step 13

switch(config-port-monitor)# counter sync-loss poll-interval seconds delta rising-threshold count1 event event-id falling-threshold count2 event event-id

Specifies the delta sync loss poll interval in seconds, the threshold limits, and the event IDs of events to be triggered.

Step 14

switch(config-port-monitor)# counter tx-datarate poll-interval seconds delta rising-threshold percentage1 event event-id falling-threshold percentage2 event event-id

Specifies the delta for the counter Tx (transmit) datarate poll interval in seconds and thresholds in percentage.

Step 15

switch(config-port-monitor)# counter tx-slowport-count poll-interval seconds {absolute | delta} {rising-threshold count1 event event-id [falling-threshold count2 event event-id ]}

Specifies the poll interval in seconds and absolute or delta threshold limits for the counter tx-slowport-count.

Step 16

switch(config-port-monitor)# counter tx-slowport-oper-delay poll-interval seconds absolute rising-threshold value event event-id [falling-threshold value event event id ]

Specifies the poll interval in seconds and absolute threshold limit for the tx- slowport-oper-delay counter.

Step 17

switch(config-port-monitor) # counter txwait poll-interval seconds {absolute | delta} {rising-threshold percentage1 event event-id [falling-threshold percentage2 event event-id ]}

Specifies the poll interval in seconds and absolute or delta thresholds in percentage for the counter txwait.

Step 18

switch(config-port-monitor)# no counter sync-loss

Reverts to the default policy for sync loss performance counter values.

Step 19

switch(config-port-monitor)# no counter tx-performance

Reverts to the default policy for Tx performance counter values.

Step 20

switch(config-port-monitor)# no counter tx-slowport-count poll-interval seconds {absolute | delta} {rising-threshold count1 event event-id [falling-threshold count2 event event-id ]}

Reverts to the default value for tx-slowport-count.

Step 21

switch(config-port-monitor)# no counter tx-slowport-oper-delay poll-interval seconds absolute rising-threshold value event event-id [falling-threshold value event event id ]

Reverts to the default value for tx-slowport-oper delay.

Step 22

switch(config-port-monitor)# no counter txwait poll-interval seconds {absolute | delta} {rising-threshold percentage1 event event-id [falling-threshold percentage event event-id ]}

Reverts to the default value for txwait.

Step 23

switch(config-port-monitor)# monitor counter rx-datarate

Turns on rx-performance counter.

switch(config-port-monitor)# monitor counter tx-datarate

Turns on tx performance counter.

switch(config-port-monitor)# no monitor counter tx-datarate

Turns off tx performance counter.

switch(config-port-monitor)# no monitor counter sync-loss

Turns off monitoring sync loss.

switch(config-port-monitor)# no monitor counter state-change

Turns off monitoring state change.

Step 24

switch(config-port-monitor)# monitor counter tx-slowport-count

switch(config-port-monitor)# no monitor counter tx-slowport-count

Turns on monitoring for tx-slowport-count.

Turns off monitoring for tx-slowport- count.

Step 25

switch(config-port-monitor)# monitor counter tx-slowport-oper-delay

switch(config-port-monitor)# no monitor counter tx-slowport-oper-delay

Turns on monitoring for tx-slowport-oper-delay.

Turns off monitoring for tx-slowport-oper-delay.

Step 26

switch(config-port-monitor)# monitor counter txwait

switch(config-port-monitor)# no monitor counter txwait

Turns on monitoring for txwait.

(Optional) Turns off monitoring for txwait.

8.The error-pkt-port counter, the err-pkt-from xbar counter, and the err-pkt-to-xbar counter are all ASIC counters. All ASIC counters are turned off by default. The Asic counters are queried every 10 seconds. If the ASIC corresponding to a specific ASIC counter sends or receives any error packets during a 10-second interval, an error frame event occurs during the interval for that counter.

 

Port monitor currently recognizes two kinds of ports:

  • Port-type access ports are normally F ports with a single end device logged in. However, port monitor considers TF ports and F ports carrying multiple logins to be port-type access as well.
  • Port-type trunk are ports that are E ports (ISLs) regardless if they are actually carrying multiple VSANs (TE, trunking) or not. Some of the access port counter thresholds and port guard actions might not be appropriate on the TF ports in port monitor configuration. Specifically, port guard disable or flap actions can affect multiple end devices on these F ports carrying multiple logins. So taking these actions should be avoided on an NPIV system.

Detailed Steps

To activate a port monitor policy, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# port-monitor activate policyname

Activates the specified port monitor policy.

switch(config)# port-monitor activate

Activates the default port monitor policy.

switch(config)# no port-monitor activate policyname

Deactivates the specified port monitoring policy.

Configuring a Port Monitor Port Guard

The port guard action is optional for each counter and is disabled unless specified.

Detailed Steps

To configure a port monitor policy, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# port-monitor name policyname

Specifies the policy name and enters the port monitoring policy configuration mode.

switch(config)# no port-monitor name policyname

Removes the policy.

Step 3

switch(config-port-monitor)# counter link-loss poll-interval seconds delta rising-threshold count1 event event-id falling-threshold count2 event event-id

portguard flap

Specifies the delta link loss poll interval in seconds, threshold limits, and event IDs of the events to be triggered. It also specifies that the port is flapped (port goes down and up) when the event occurs. It also specifies the portguard action to flap the port when the rising-threshold is reached.

Step 4

switch(config-port-monitor)# counter link-loss poll-interval seconds delta rising-threshold count1 event event-id falling-threshold count2 event event-id

portguard errordisable

Specifies the delta link loss poll interval in seconds, threshold limits, and event IDs of the events to be triggered. It also specifies that the interface is down (error disabled) when the event occurs. It also specifies the portguard action to error disable the port when the rising-threshold is reached.


Note Port guard action is not supported for absolute type counters.

Enabling Port Group Monitor

Detailed Steps

To enable port group monitor, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# port-group-monitor enable

Enables (default) port group monitoring.

switch(config)# no port-group-monitor enable

Disables port group monitoring.

Configuring a Port Group Monitor Policy

Detailed Steps

To configure port group monitor policy, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# port-group-monitor name policyname

Specifies the policy name and enters the port group monitoring policy configuration mode.

switch(config)# no port-group-monitor name policyname

Removes the policy.

Step 3

switch(config-port-group-monitor)# counter rx-performance poll-interval seconds delta rising-threshold percentage1 falling-threshold percentage2

Specifies the delta Rx counter poll interval in seconds and thresholds in percentage.

switch(config-port-group-monitor)# counter tx-performance poll-interval seconds delta rising-threshold percentage1 falling-threshold percentage2

Specifies the delta Tx counter poll interval in seconds and thresholds in percentage.

switch(config-port-group-monitor)# no counter tx-performance

9Reverts to the 10default policy.

Step 4

switch(config-port-group-monitor)# monitor counter rx-performance

Turns on Rx performance monitoring.

switch(config-port-group-monitor)# monitor counter tx-performance

Turns on Tx performance monitoring.

switch(config-port-group-monitor)# no monitor counter tx-performance

11Turns off Tx performance monitoring.

11.See Turning Off the Monitoring of Specific Counter.


On 8-Gbps and higher speed modules, ports errors are monitored using the counters, invalid-crc and invalid-words. The counter err-pkt-from-port is supported only on 4-Gbps modules.


Reverting to the Default Policy for a Specific Counter

When the no counter command is used in the config-port-group-monitor mode, the specified counter polling values will revert to the default values as seen in the following example:

switch(config)# port-group-monitor name PGMON_policy
switch(config-port-group-monitor)# counter tx-performance poll-interval 100 delta rising-threshold 65 falling-threshold 25
switch(config)# show port-group-monitor PGMON_policy
 
Policy Name : PGMON_policy
Admin status : Not Active
Oper status : Not Active
Port type : All Port Groups
------------------------------------------------------------------------------------------
Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold
------- --------- -------- -------------------- ---------------------
RX Performance Delta 60 80 10
TX Performance Delta 100 65 25
 
switch(config)# port-group-monitor name PGMON_policy
switch(config-port-group-monitor)# no counter tx-performance
switch(config)# show port-group-monitor PGMON_policy
 
 
Policy Name : PGMON_policy
Admin status : Not Active
Oper status : Not Active
Port type : All Port Groups
------------------------------------------------------------------------------------------
Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold
------- --------- -------- -------------------- ----------------------
RX Performance Delta 60 80 10
TX Performance Delta 60 80 10
------------------------------------------------------------------------------------------

Turning Off the Monitoring of Specific Counter

When the no monitor counter command is used in the config-port-group-monitor mode, it turns off the monitoring of the specified counter in the given policy as seen in the following example:

switch(config)# port-group-monitor name PGMON_policy
switch(config-port-group-monitor)# no monitor counter rx-performance
 
switch(config)# show port-group-monitor PGMON_policy
 
Policy Name : PGMON_policy
Admin status : Not Active
Oper status : Not Active
Port type : All Port Groups
------------------------------------------------------------------------------------------
Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold
------- --------- -------- -------------------- ----------------------
RX Performance Delta 26 450 250
TX Performance Delta 60 100 80
------------------------------------------------------------------------------------------
 

Activating a Port Group Monitor Policy

To activate a port group monitor policy, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# port-group-monitor activate policyname

Activates the specified port group monitor policy.

switch(config)# port-group-monitor activate

Activates the default port group monitor policy.

switch(config)# no port-group-monitor activate policyname

Deactivates the specified port group monitor policy.

Configuring Management Interfaces

Detailed Steps

To configure the mgmt0 Ethernet interface to connect over IPv4, follow these steps:

Command
Purpose

Step 1

switch# config terminal

switch(config)#

Enters configuration mode.

Step 2

switch(config)# interface mgmt0

switch(config-if)#

Selects the management Ethernet interface on the switch and enters interface configuration submode.

Step 3

switch(config-if)# ip address 10.16.1.2 255.255.255.0

Configures the IPv4 address and IPv4 subnet mask.

Step 4

switch(config-if)# no shutdown

Enables the interface.

Step 5

switch(config-if)# exit

switch(config)#

Returns to configuration mode.

Step 6

switch(config)# ip default-gateway 1.1.1.4

Configures the default gateway IPv4 address.

Step 7

switch(config)# exit

switch#

Returns to EXEC mode.

Step 8

switch# copy running-config startup-config

(Optional) Saves your configuration changes to the file system.

If you want to save your configuration, you can enter this command at any time.

To configure the mgmt0 Ethernet interface to connect over IPv6, follow these steps:

Command
Purpose

Step 1

switch# config terminal

switch(config)#

Enters configuration mode.

Step 2

switch(config)# interface mgmt0

switch(config-if)#

Selects the management Ethernet interface on the switch and enters interface configuration submode.

Step 3

switch(config-if)# ipv6 enable

Enables IPv6 and assigns a link-local address on the interface.

Step 4

switch(config-if)# ipv6 address ipv6 address 2001:0db8:800:200c::417a/64

Specifies an IPv6 unicast address and prefix length on the interface.

Step 5

switch(config-if)# no shutdown

Enables the interface.

Step 6

switch(config-if)# end

switch#

Returns to EXEC mode.

Step 7

switch# copy running-config startup-config

(Optional) Saves your configuration changes to the file system.

If you want to save your configuration, you can enter this command at any time.

Creating VSAN Interfaces

Detailed Steps

To create a VSAN interface, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# interface vsan 2

switch(config-if)#

Configures a VSAN with the ID 2.

Step 3

switch(config-if)# no shutdown

Enables the VSAN interface.

Configuring Slow Drain Device Detection and Congestion Avoidance

Slow drain devices are devices that do not accept frames at the configured rate. The presence of these slow drain devices leads to traffic congestion in the FC/FCoE fabric. This traffic congestion can affect the unrelated flows in the fabric that use the same inter-switch links (ISLs) for its traffic as the slow drain device. This is true even though the destination devices are not, themselves, slow drain devices.

Beginning with the Cisco MDS NX-OS Release 4.2(1), slow drain device detection and congestion avoidance is supported on all FC switching modules.

Beginning with the Cisco MDS NX-OS Release 5.2(1), slow drain device detection and congestion avoidance is supported on all FCoE switch modules.

Beginning in Cisco MDS NX-OS Release 5.2(1), slow drain detection and congestion avoidance functionality for edge ports was enhanced.

There are multiple features available on the Cisco MDS 9000 Series platforms to detect slow drain and avoid the resulting effects of slow drain.

Table 2-8 describes the features to detect slow drain:

Table 2-8 Features to detect slow drain

Feature Name
Description

TX credit not available counter

FC port monitor: Transmit credit not available is the continuous no transmit credit condition. When the configured period expires, trap/flap/error disable the port.

Congestion drop

FC system: Congestion drop timeout is the maximum lifetime of a frame in the switch. When the configured period expires, the frames are dropped.

FCoE system: Congestion drop timeout is the maximum lifetime of a frame in the switch. When the configured period expires, the frames are dropped.

Slow port monitor

FC system: Slow port monitor credits returns to the switch slowly; log events only.

No credit drop

FC system: No credit drop is the continuous no transmit credit condition; all the queued and incoming frames for the port are dropped immediately.

Pause timeout

FCoE system: Pause timeout is the continuous pause condition. When the configured period expires, all the queued and incoming frames for the port are dropped.

Credit loss recovery

FC system: Credit loss recovery is the continuous no transmit credit condition; resets the port.

This section includes the following topics:

Configuring Congestion Frame Timeout Value for FCoE

When an FCoE frame takes longer than the congestion timeout period to be transmitted by the egress port, the frame is dropped. This dropping of the frames is useful in controlling the effect of slow egress ports, which are paused almost continuously (long enough to cause congestion) but not long enough to trigger the pause timeout drop. The dropping of frames is counted as egress discard on the egress port. The egress discard releases buffers in the upstream ingress ports of the switch allowing the unrelated flows to move continuously through them.

The congestion timeout value is 500 milliseconds by default for all port types. It is recommended to retain the default timeout for core ports and consider configuring a lower value for edge ports. This value should be equal to or greater than the pause frame timeout value for that port type.

To configure the congestion frame timeout value for FCoE, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config) # system default interface congestion timeout milliseconds mode {core | edge}

Configures the system-wide FCoE congestion timeout in milliseconds for either core or edge ports.

The FCoE congestion timeout range is 100-1000 milliseconds.

Configuring Pause Frame Timeout for FCoE

When an FCoE port is in a state of continuous pause for the pause frame timeout period, all the frames that are queued to that port are dropped immediately. As long as the port continues to remain in the pause state, the newly arriving frames destined to the port are dropped immediately. These drops are counted as egress discards on the egress port which creates buffers in the upstream ingress ports of the switch allowing unrelated flows to continue moving through them.

To reduce the effect of a slow drain device on unrelated traffic flows configure a lower pause frame timeout value for edge ports than the congestion frame timeout. This causes frames destined for a slow port to be dropped immediately once the pause timeout period has occurred rather than waiting for the congestion timeout period to drop them.

Pause timeout dropping can be enabled and disabled. By default, frame dropping is enabled. The pause timeout value is 500 milliseconds by default for all ports. It is recommended to retain the default time out core ports and consider configuring a lower value for edge ports.

To configure the pause frame timeout value for FCoE, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config) # system default interface pause timeout milliseconds mode {core | edge}

Configures the system-wide FCoE pause timeout in milliseconds for either core or edge ports.

The range is 100–500 milliseconds.

Step 3

switch(config) # no system default interface pause timeout milliseconds mode {core | edge}

Reverts to the default pause timeout in milliseconds.

Step 4

switch(config)# system default interface pause mode {core | edge}

Enables the pause timeout drops for edge and core ports. This is the default.

Step 5

switch(config)# no system default interface pause mode {core | edge}

Disables the pause timeout drops for edge or core ports.

Configuring Congestion Drop Timeout Value for FC

When an FC frame takes longer than the congestion timeout period to be transmitted by the egress port, the frame is dropped. This option of the frames being dropped is useful for controlling the effect of slow egress ports which lack transmit credits almost continuously; long enough to cause congestion, but not long enough to trigger the no credit timeout drop. These drops are counted as egress discards on the egress port, which releases buffers in the upstream ingress ports of the switch, allowing unrelated flows to continue moving through them.

By default, the congestion timeout value is 500 milliseconds for all port types. It is recommended to retain the default timeout for core ports and configure a lower value (not less than 200 milliseconds) for edge ports. The congestion timeout value should be equal to or greater than the no credit frame timeout value for that port type.

To configure the congestion frame timeout value for FC, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config) # system timeout congestion-drop milliseconds mode E | F

Configures the FC congestion drop timeout value in milliseconds for the specified port type.

The range is 100-500 milliseconds in multiples of 10.

Step 3

switch(config) # system timeout congestion-drop default mode E | F

Configures the default value for the congestion timeout for the specified port type.

Configuring No Credit Frame Timeout Value for FC

When an FC egress port has no transmit credits continuously for the no-credit timeout period, all the frames already queued to that port are dropped immediately. As long as the port remains in this condition, any newly arriving frame destined to that port is dropped immediately. These drops are counted as egress discards on the egress port. This releases buffers in the upstream ingress ports of the switch allowing unrelated flows to continue moving through them.

No credit dropping can either be enabled or disabled. By default, frame dropping is disabled and the frame timeout value is 500 milliseconds for all port types. It is recommended to retain the default frame timeout for core ports and configure a lower value (300 milliseconds) for edge ports. If the slow drain events continue to affect unrelated traffic flows then the frame timeout value for the edge ports can be lowered to drop the previous slow drain frames. This frees the ingress buffers for frames of unrelated flows, thus reducing the latency of the frames through the switch.


Note The no-credit frame timeout value should always be less than the congestion frame timeout for the same port type, and the edge port frame timeout values should always lower than core port frame timeout values.



Note The slow port monitor delay value should always be less than no-credit frame timeout value for the same port type.


For pre-16 Gbps capable modules and systems, the no credit timeout value is allowed to be 100-500 milliseconds in multiples of 100 milliseconds. On these systems, the no credit condition is checked only at 100 millisecond intervals and at this point if the no credit condition exists then dropping starts. Depending on the timing of the actual onset of the no credit condition, the checking of the port dropping could be delayed by up to 100 milliseconds longer than the configured value. On 16 Gbps and later modules and systems, the no credit timeout value is allowed to be 1-500 milliseconds in multiples of 1 millisecond. Dropping starts immediately after the no credit condition exists for the configured timeout value.

To configure the no credit timeout value, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# system timeout no-credit-drop milli seconds mode F

Specifies the no credit timeout value for F ports for the switch.

switch(config)# system timeout no-credit-drop default mode F

Configures the default no credit timeout value (500 ms) for edge ports. The no credit drop action is not changed.

 

switch(config)# no system timeout no-credit-drop mode F

Disables no credit dropping for edge ports.

Configuring Slow Port Monitor Timeout Value for FC

The slow port monitor functionality is like the no credit frame timeout and drop functionality except that it does not drop frames, it only logs qualifying events. When an FC egress port has no transmit credits continuously for the slow port monitor timeout period, the event is logged. No frames are dropped unless the no credit frame timeout period is reached and no credit frame timeout drop is enabled. If the no credit frame timeout drop is not enabled then no frames are dropped until the congestion frame timeout period is reached.

Slow port monitoring is implemented in the hardware, and the slow port monitor functionality implemented is slightly different on each generation of hardware. The 8-Gbps modules report a single slow port monitor event for each 100 millisecond window in which the slow port monitor threshold has crossed one or more times. They do not have the ability to report the exact number of slow port events. The Advanced 8-Gbps and 16-Gbps modules and switches are not restricted and can detect each time the slow port monitor threshold has crossed. The slow port monitor log is updated at 100 millisecond intervals. A log entry for a slow port on an 8-Gbps could increment by a maximum of one. A log for a slow port event on an Advanced 8-Gbps or 16-Gbps module or system would increment the exact number of times the threshold was reached.

Earlier module and switches do not support slow port monitor functionality. Modules and switches currently supporting slow port monitor are:

  • 8-Gbps modules:

Cisco MDS 9500 1, 2, 4, or 8-Gbps FC Module DS-X9248-48K9

Cisco MDS 9500 1, 2, 4, or 8-Gbps FC Module DS-X9224-96K9

Cisco MDS 9500 1, 2, 4, or 8-Gbps FC Module DS-X9248-96K9

  • Advanced 8-Gbps modules:

Cisco MDS 9500 1, 2, 4, 8, or 10-Gbps Advanced FC Module DS-X9232-256K9

Cisco MDS 9500 1, 2, 4, 8, or 10-Gbps Advanced FC Module DS-X9248-256K9

  • 16-Gbps modules or switches:

Cisco MDS 9700 2, 4, 8, 10, or 16-Gbps Advanced FC Module DS-X9448-768K9

Cisco MDS 9250i Fabric Switch

Cisco MDS 9148S Fabric Switch

Cisco MDS 9396S Fabric Switch

Table 2-9 displays the slowport features supported on different FC switching modules for the Cisco MDS NX-OS Release 6.2(13).

Table 2-9 Slow Port Support on FC Switching Modules

Function
Hardware Support
8-Gbps modules
Advanced 8-Gbps modules
16-Gbps modules and switches

Slowport monitor12

Yes

Yes

Yes

Transmit wait history graph

No

Yes

Yes

Transmit wait OBFL logging

Yes

Yes

Yes

Port monitor slow port counter

No

Yes

Yes

Port monitor transmit wait counter

Yes

Yes

Yes

Transmit wait interface counter

No

Yes

Yes

12.Beginning with the Cisco MDS NX-OS Release 6.2(9), slowport monitoring is supported on 16-Gbps modules and switches. Beginning with the Cisco MDS NX-OS Release 6.2(13), slowport monitoring is supported on 8-Gbps modules.

To configure the slow port monitor timeout value, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch(config)# system timeout slowport-monitor milliseconds mode E | F

Specifies the slow port monitor timeout value for E or F port mode for the switch.

The allowed values for the slow port monitor timeout are as follows:

  • 16-Gbps modules or switches: 1-500 ms in 1 ms increments.
  • 8-Gbps and Advanced 8-Gbps modules: 1-100 ms in 1 ms increments.

switch(config)# system timeout slowport-monitor default mode E | F

Configures the default slow port monitor timeout value (500 milliseconds) for the specified port type.

Displaying Credit Loss Recovery Actions

When a port is at zero Tx credits for 1 full second (F ports) and 1.5 seconds (E ports), it is called a Credit Loss condition. The Cisco MDS initiates Credit Loss Recovery by transmitting a Link Credit Reset (LR). If the end device responds with a Link Credit Reset Response (LRR), the port is back at its fully agreed number of B2B credits in both directions. If an LRR is not received, the port is shutdown.

When the port detects the credit loss condition and recovers, some of the following actions can occur:

1. An SNMP trap with interface details can be sent indicating the credit loss event.

2. The port can be error-disabled.

3. The port can be flapped.

When the configured threshold is exceeded, one or more of these actions can be combined together. These actions can be turned on or off depending on the situation. The port monitor feature provides the command line interface to configure the thresholds and action.

The 1 second (F ports) and 1.5 second (E ports) that the switch initiates Credit Loss Recovery are fixed and cannot be changed.

To configure a port-monitor to generate SNMP alerts and take other actions in a wide range of quantity and timing of these events, follow these steps:

Command
Purpose

Step 1

switch# show process creditmon credit-loss-events [module x]

Displays the last 10 credit loss events per interface per module.

Step 2

switch# show process creditmon credit-loss-event-history [module x]

Displays a chronological log of credit loss events per module.

When the port sees the credit loss condition and fails to recover, the port flaps. This function is already a part of the port guard, and you can configure the supported actions using the port guard feature.

Configuring Average Credit Nonavailable Duration Threshold and Action

The Cisco MDS monitors its ports that are at zero Tx credits for 100ms or more. This is called Tx average credit nonavailable duration. Port-monitor can monitor this using the “TX Credit Not Available” counter. When the Tx average credit nonavailable duration exceeds the threshold set in the port-monitor, some of the following actions can occur:

1. An SNMP trap with interface details can be sent indicating the Tx average credit nonavailable duration event.

2. The port can be error-disabled.

3. The port can be flapped.

When the configured threshold is exceeded, one or more of these actions can be combined together. These actions can be turned on or off depending on the situation. The port monitor feature provides the command line interface to configure the thresholds and action. The threshold configuration is configured as a percentage of the interval. The thresholds can be 0 percent to 100 percent in multiples of 10, and the interval can be 1 second to 1 hour. The default is 10 percent of a 1 second interval and generates a trap when Tx average credit nonavailable duration hits 100ms.

To configure average credit nonavailable duration threshold and action, refer to the “Port Monitor” section.

To configure credit loss recovery and average credit nonavailable duration threshold and action, refer to the following example:

switch# show port-monitor
Policy Name : Cisco
Admin status : Not Active
Oper status : Not Active
Port type : All Ports
------------------------------------------------------------------------------------------
Counter Threshold Interval Rising Threshold event Falling Threshold event PMON Portguard
------------------------------------------------------------------------------------------
Link Loss Delta 60 5 4 1 4
Not enabled
Sync Loss Delta 60 5 4 1 4
Not enabled
Signal Loss Delta 60 5 4 1 4
Not enabled
Invalid Words Delta 60 1 4 0 4
Not enabled
Invalid CRC's Delta 60 5 4 1 4
Not enabled
TX Discards Delta 60 200 4 10 4
Not enabled
LR RX Delta 60 5 4 1 4
Not enabled
LR TX Delta 60 5 4 1 4
Not enabled
Timeout Discards Delta 60 200 4 10 4
Not enabled
Credit Loss Reco Delta 1 1 4 0 4
Not enabled
TX Credit Not
Available Delta 1 10% 4 0% 4
Not enabled
RX Datarate Delta 60 80% 4 20% 4
Not enabled
TX Datarate Delta 60 80% 4 20% 4
Not enabled
TX-Slowport-Count Delta 1 5 4 0 4
Not enabled
TX-Slowport-Oper-
Delay Absolute 1 50ms 4 0ms 4
Not enabled
TXWait Delta 1 40% 4 0% 4
Not enabled
------------------------------------------------------------------------------------------
 

The following edge port monitor policy is active by default. There is no port monitor policy enabled for core ports by default.

switch# show port-monitor slowdrain
 
Policy Name : slowdrain
Admin status : Not Active
Oper status : Not Active
Port type : All Access Ports
------------------------------------------------------------------------------------------
Counter Threshold Interval Rising Threshold event Falling Threshold event
PMON Portguard
------------------------------------------------------------------------------------------
Credit Loss Reco Delta 1 1 4 0 4
Not enabled
TX Credit Not
Available Delta 1 10% 4 0% 4
Not enabled
------------------------------------------------------------------------------------------
 

Configuring Internal CRC Detection and Isolation

Detailed Steps

This functionality is disabled by default. To configure internal CRC detection and isolation, follow these steps:

Command
Purpose

Step 1

switch# config t

Enters configuration mode.

Step 2

switch (config)# hardware fabric crc [threshold threshold-count]

Enables internal CRC detection and isolation.

The error rate is measured over sequential 24-hour windows. The range of threshold is 1 to 100. If the threshold is not specified, the default value of 3 is used.

Step 3

switch (config)# no hardware fabric crc

Disables internal CRC detection and isolation.

Step 4

switch (config)# copy running-config startup-config

(Optional) Saves the configuration change.

Verifying Interfaces Configuration

This section includes the following topics:

Displaying Interface Information

The show interface command is invoked from the EXEC mode and displays the interface configurations. Without any arguments, this command displays the information for all the configured interfaces in the switch. See Examples 2-6 to 2-13 .

Example 2-6 Displays All Interfaces

switch# show interface
fc1/1 is up
Hardware is Fibre Channel, SFP is short wave laser
Port WWN is 20:0b:00:05:30:00:8d:de
Admin port mode is F
Port mode is F, FCID is 0x610000
Port vsan is 2
Speed is 2 Gbps
Transmit B2B Credit is 3
Receive B2B Credit is 16
Receive data field Size is 2112
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
134 frames input, 8468 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
154 frames output, 46072 bytes
0 discards, 0 errors
1 input OLS, 1 LRR, 0 NOS, 0 loop inits
1 output OLS, 0 LRR, 1 NOS, 0 loop inits
16 receive B2B credit remaining
3 transmit B2B credit remaining.
...
fc1/9 is trunking
Hardware is Fibre Channel, SFP is long wave laser cost reduced
Port WWN is 20:09:00:05:30:00:97:9e
Peer port WWN is 20:0b:00:0b:5f:a3:cc:00
Admin port mode is E, trunk mode is on
Port mode is TE
Port vsan is 100
Speed is 2 Gbps
Transmit B2B Credit is 255
Receive B2B Credit is 255
Receive data field Size is 2112
Beacon is turned off
Trunk vsans (admin allowed and active) (1,100,3000)
Trunk vsans (up) (1,100,3000)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
5 minutes input rate 280 bits/sec, 35 bytes/sec, 0 frames/sec
5 minutes output rate 176 bits/sec, 22 bytes/sec, 0 frames/sec
4609939 frames input, 8149405708 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
4638491 frames output, 7264731728 bytes
0 discards, 0 errors
3 input OLS, 9 LRR, 1 NOS, 0 loop inits
9 output OLS, 7 LRR, 1 NOS, 0 loop inits
16 receive B2B credit remaining
3 transmit B2B credit remaining.
...
fc1/13 is up
Hardware is Fibre Channel, SFP is short wave laser
Port WWN is 20:0d:00:05:30:00:97:9e
Admin port mode is auto, trunk mode is on
Port mode is F, FCID is 0x650100
Port vsan is 100
Speed is 2 Gbps
Transmit B2B Credit is 3
Receive B2B Credit is 16
Receive data field Size is 2112
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
8696 frames input, 3227212 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
16799 frames output, 6782444 bytes
0 discards, 0 errors
0 input OLS, 0 LRR, 0 NOS, 0 loop inits
1 output OLS, 1 LRR, 0 NOS, 1 loop inits
16 receive B2B credit remaining
3 transmit B2B credit remaining.
...
sup-fc0 is up
Hardware is Fibre Channel
Speed is 1 Gbps
139597 packets input, 13852970 bytes
0 multicast frames, 0 compressed
0 input errors, 0 frame, 0 overrun 0 fifo
139516 packets output, 16759004 bytes, 0 underruns
0 output errors, 0 collisions, 0 fifo
0 carrier errors
 

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 with the following example format:

interface fc1/1 - 5 , fc2/5 - 7

Note The spaces are required before and after the dash ( -) and before and after the comma (,).


Example 2-7 Displays Multiple, Specified Interfaces

switch# show interface fc3/13, fc3/16
fc3/13 is up
Hardware is Fibre Channel, SFP is short wave laser
Port WWN is 20:8d:00:05:30:00:97:9e
Admin port mode is FX
Port mode is F, FCID is 0x7b0300
Port vsan is 1
Speed is 2 Gbps
Transmit B2B Credit is 3
Receive B2B Credit is 12
Receive data field Size is 2112
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
1856 frames input, 116632 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
1886 frames output, 887712 bytes
0 discards, 0 errors
0 input OLS, 0 LRR, 0 NOS, 1 loop inits
1 output OLS, 1 LRR, 0 NOS, 1 loop inits
16 receive B2B credit remaining
3 transmit B2B credit remaining.
 
fc3/16 is up
Hardware is Fibre Channel, SFP is short wave laser
Port WWN is 20:90:00:05:30:00:97:9e
Admin port mode is FX
Port mode is F, FCID is 0x7d0100
Port vsan is 3000
Speed is 2 Gbps
Transmit B2B Credit is 3
Receive B2B Credit is 12
Receive data field Size is 2112
Beacon is turned off
5 minutes input rate 504 bits/sec, 63 bytes/sec, 0 frames/sec
5 minutes output rate 520 bits/sec, 65 bytes/sec, 0 frames/sec
47050 frames input, 10311824 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
62659 frames output, 10676988 bytes
0 discards, 0 errors
0 input OLS, 0 LRR, 0 NOS, 0 loop inits
1 output OLS, 1 LRR, 0 NOS, 1 loop inits
16 receive B2B credit remaining
3 transmit B2B credit remaining.

Example 2-8 Displays a Specific Interface

switch# show interface fc2/2
fc2/2 is trunking
Port description is Trunk to Core-4
Hardware is Fibre Channel, SFP is short wave laser
Port WWN is 20:42:00:05:30:00:97:9e
Peer port WWN is 20:cc:00:05:30:00:50:9e
Admin port mode is E, trunk mode is on
Port mode is TE
Port vsan is 1
Speed is 2 Gbps
Transmit B2B Credit is 255
Receive B2B Credit is 255
Receive data field Size is 2112
Beacon is turned off
Belongs to port-channel 2
Trunk vsans (admin allowed and active) (1,100,3000)
Trunk vsans (up) (1)
Trunk vsans (isolated) (100,3000)
Trunk vsans (initializing) ()
5 minutes input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
5 minutes output rate 32 bits/sec, 4 bytes/sec, 0 frames/sec
2214834 frames input, 98673588 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
2262415 frames output, 343158368 bytes
0 discards, 0 errors
1 input OLS, 1 LRR, 1 NOS, 0 loop inits
2 output OLS, 1 LRR, 0 NOS, 0 loop inits
16 receive B2B credit remaining
3 transmit B2B credit remaining.

Example 2-9 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 --
-------------------------------------------------------------------------------
Interface Description
-------------------------------------------------------------------------------
port-channel 1 --
port-channel 5 --
port-channel 6 --

Example 2-10 Displays Interface Information in a Brief Format

switch# show interface brief
 
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 1 E on trunking swl TE 2 1
fc1/2 1 E on trunking swl TE 2 1
fc1/3 1 auto on SFPAbsent -- -- --
fc1/4 1 auto on SFPAbsent -- -- --
fc1/5 3000 auto on up swl F 2 --
...
fc2/2 1 E on trunking swl TE 2 2
fc2/3 1 auto on down c1610 -- --
fc2/4 1 auto on down c1590 -- --
fc2/5 3000 auto on notConnected lwcr -- --
fc2/6 1 auto on SFPAbsent -- -- --
...
fc3/16 3000 FX -- up swl F 2 --
fc3/17 1 FX -- SFPAbsent -- -- --
...
-------------------------------------------------------------------------------
Interface Status IP Address Speed MTU
-------------------------------------------------------------------------------
GigabitEthernet4/1 SFPAbsent -- auto 1500
...
GigabitEthernet4/6 down 10.1.1.2/8 auto 3000
GigabitEthernet4/7 down 10.1.1.27/24 auto 1500
GigabitEthernet4/8 down -- auto 1500
 
-------------------------------------------------------------------------------
Interface Status Oper Mode Oper Speed
(Gbps)
-------------------------------------------------------------------------------
iscsi4/1 down --
...
-------------------------------------------------------------------------------
Interface Status Speed
(Gbps)
-------------------------------------------------------------------------------
sup-fc0 up 1
 
-------------------------------------------------------------------------------
Interface Status IP Address Speed MTU
-------------------------------------------------------------------------------
mgmt0 up 172.19.48.96/25 100 Mbps 1500
 
-------------------------------------------------------------------------------
Interface Vsan Admin Status Oper Oper
Trunk Mode Speed
Mode (Gbps)
-------------------------------------------------------------------------------
port-channel 1 1 on trunking TE 4
port-channel 2 1 on trunking TE 4
 
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status Oper Profile Port-channel
Mode Trunk Mode
Mode
-------------------------------------------------------------------------------
fcip10 1 auto on notConnected -- 10 --

Example 2-11 Displays Interface Counters

switch# show interface counters
fc3/1
5 minutes input rate 24 bits/sec, 3 bytes/sec, 0 frames/sec
5 minutes output rate 16 bits/sec, 2 bytes/sec, 0 frames/sec
3502 frames input, 268400 bytes
0 discards, 0 CRC, 0 unknown class
0 too long, 0 too short
3505 frames output, 198888 bytes
0 discards
1 input OLS, 1 LRR, 1 NOS, 0 loop inits
2 output OLS, 1 LRR, 1 NOS, 0 loop inits
1 link failures, 1 sync losses, 1 signal losses
.
.
.
fc9/8
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
0 frames input, 0 bytes
0 class-2 frames, 0 bytes
0 class-3 frames, 0 bytes
0 class-f frames, 0 bytes
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
0 discards
0 input OLS, 0 LRR, 0 NOS, 0 loop inits
0 output OLS, 0 LRR, 0 NOS, 0 loop inits
0 link failures, 0 sync losses, 0 signal losses
16 receive B2B credit remaining
3 transmit B2B credit remaining.
...
sup-fc0
114000 packets input, 11585632 bytes
0 multicast frames, 0 compressed
0 input errors, 0 frame, 0 overrun 0 fifo
113997 packets output, 10969672 bytes, 0 underruns
0 output errors, 0 collisions, 0 fifo
0 carrier errors
 
mgmt0
31557 packets input, 2230860 bytes
0 multicast frames, 0 compressed
0 input errors, 0 frame, 0 overrun 0 fifo
26618 packets output, 16824342 bytes, 0 underruns
0 output errors, 0 collisions, 7 fifo
0 carrier errors
 
vsan1
0 packets input, 0 bytes, 0 errors, 0 multicast
0 packets output, 0 bytes, 0 errors, 0 dropped
.
.
.
port-channel 1
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
0 frames input, 0 bytes
0 class-2 frames, 0 bytes
0 class-3 frames, 0 bytes
0 class-f frames, 0 bytes
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
0 discards
0 input OLS, 0 LRR, 0 NOS, 0 loop inits
0 output OLS, 0 LRR, 0 NOS, 0 loop inits
0 link failures, 0 sync losses, 0 signal losses
 

Note Interfaces 9/8 and 9/9 are not trunking ports and display class 2, 3, and F information as well.


Example 2-12 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
-------------------------------------------------------------------------------
fc3/1 0 3871 0 3874
fc3/2 0 3902 0 4232
fc3/3 0 3901 0 4138
fc3/4 0 3895 0 3894
fc3/5 0 3890 0 3897
fc9/8 0 0 0 0
fc9/9 0 5 0 4
fc9/10 0 4186 0 4182
fc9/11 0 4331 0 4315
 
-------------------------------------------------------------------------------
Interface Input (rate is 5 min avg) Output (rate is 5 min avg)
----------------------------- -----------------------------
Rate Total Rate Total
Mbits/s Frames Mbits/s Frames
-------------------------------------------------------------------------------
port-channel 1 0 0 0 0
port-channel 2 0 3946 0 3946
 

Note The show interface transceiver command can only be issued on a switch in the Cisco MDS 9100 Series if the SFP is present (see Example 2-13).


Example 2-13 Displays Transceiver Information

switch# show interface transceiver
fc1/1 SFP is present
name is CISCO-AGILENT
part number is QFBR-5796L
revision is
serial number is A00162193
fc-transmitter type is short wave laser
cisco extended id is unknown (0x0)
...
fc1/9 SFP is present
name is FINISAR CORP.
part number is FTRJ-1319-7D-CSC
revision is
serial number is H11A6ER
fc-transmitter type is long wave laser cost reduced
cisco extended id is unknown (0x0)
...
 

Example 2-14 displays the entire running configuration with information for all interfaces. The interfaces have multiple entries in the configuration files to ensure that the interface configuration commands execute in the correct order when the switch reloads.

Example 2-14 Displays the Running Configuration for All Interfaces

switch# show running-config
...
interface fc9/1
switchport speed 2000
...
interface fc9/1
switchport mode E
...
interface fc9/1
channel-group 11 force
no shutdown
 

Example 2-15 displays the running configuration information for a specified interface. The interface configuration commands are grouped together.

Example 2-15 Displays the Running Configuration for a Specified Interface

switch# show running-config interface fc1/1
interface fc9/1
switchport speed 2000
switchport mode E
channel-group 11 force
no shutdown
 

Example 2-16 displays the running configuration after the system default switchport mode F command is executed.

Example 2-16 Displays the Running Configuration after the System Default Switchport Mode F Command is Executed

switch# show running-config
version 3.1(3)
system default switchport mode F
interface fc4/1
interface fc4/2
interface fc4/3
interface fc4/4
interface fc4/5
interface fc4/6
interface fc4/7
interface fc4/8
interface fc4/9
interface fc4/10
 

Example 2-17 displays the running configuration after two interfaces are individually configured for mode FL.

Example 2-17 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
interface fc4/8
interface fc4/9
interface fc4/1
 

Example 2-18 displays interface information in a brief format after the system default switchport mode F command is executed. Example 2-19 displays interface information in a brief format after two interfaces are individually configured for mode FL.

Example 2-18 Displays Interface Information in a Brief Format after the System Default Switchport Mode F Command is Executed

switch# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc4/1 1 F -- notConnected swl -- --
fc4/2 1 F -- notConnected swl -- --
fc4/3 1 F -- notConnected swl -- --
fc4/4 1 F -- notConnected swl -- --
fc4/5 1 F -- sfpAbsent -- -- --
fc4/6 1 F -- sfpAbsent -- -- --
fc4/7 1 F -- sfpAbsent -- -- --
fc4/8 1 F -- sfpAbsent -- -- --
fc4/9 1 F -- sfpAbsent -- -- --

Example 2-19 Displays Interface Information in a Brief Format after Two Interfaces Are Individually Configured for Mode FL

switch# show interface brief
 
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc4/1 1 FL -- notConnected swl -- --
fc4/2 1 F -- notConnected swl -- --
fc4/3 1 FL -- notConnected swl -- --
fc4/4 1 F -- notConnected swl -- --
fc4/5 1 F -- sfpAbsent -- -- --
fc4/6 1 F -- sfpAbsent -- -- --
fc4/7 1 F -- sfpAbsent -- -- --
fc4/8 1 F -- sfpAbsent -- -- --
fc4/9 1 F -- sfpAbsent -- -- --
fc4/10 1 F -- sfpAbsent -- -- --

 

Displaying Port Monitor Status and Policies

The following commands display information regarding port monitor:

switch# show port-monitor status
Port Monitor : Enabled
Active Policies : sample
Last 100 logs :
 
switch# show port-monitor
------------------------------------------------------------------------------------------
Port Monitor : enabled
------------------------------------------------------------------------------------------
Policy Name : Sample
Admin status : Not Active
Oper status : Not Active
Port type : All Ports
------------------------------------------------------------------------------------------
Counter Threshold Interval Rising Threshold event Falling Threshold event PMON Portguard
------------------------------------------------------------------------------------------ Link Loss Delta 60 5 4 1 4
Not enabled
Sync Loss Delta 60 5 4 1 4
Not enabled
Signal Loss Delta 60 5 4 1 4
Not enabled
Invalid Words Delta 60 1 4 0 4
Not enabled
Invalid CRC's Delta 60 5 4 1 4
Not enabled
TX Discards Delta 60 200 4 10 4
Not enabled
LR RX Delta 60 5 4 1 4
Not enabled
LR TX Delta 60 5 4 1 4
Not enabled
Timeout
Discards Delta 60 200 4 10 4 Not enabled
Credit Loss
Reco Delta 1 1 4 0 4 Not enabled
TX Credit Not
Available Delta 1 10% 4 0% 4 Not enabled
RX Datarate Delta 60 80% 4 20% 4 Not enabled
TX Datarate Delta 60 80% 4 20% 4 Not enabled
TX-Slowport
-Count Delta 1 5 4 0 4 Not enabled
TX-Slowport
-Oper-Delay Absolute 1 50ms 4 0ms 4 Not enabled
TXWait Delta 1 40% 4 0% 4 Not enabled
------------------------------------------------------------------------------------------
 
Policy Name : default
Admin status : Not Active
Oper status : Not Active
Port type : All Ports
------------------------------------------------------------------------------------------
Counter Threshold Interval Rising Threshold event Falling Threshold event PMON Portguard
--------------------------------------------------------------------------------------------------------------
Link Loss Delta 60 5 4 1 4
Not enabled
Sync Loss Delta 60 5 4 1 4
Not enabled
Signal Loss Delta 60 5 4 1 4
Not enabled
Invalid Words Delta 60 1 4 0 4
Not enabled
Invalid CRC's Delta 60 5 4 1 4
Not enabled
TX Discards Delta 60 200 4 10 4
Not enabled
LR RX Delta 60 5 4 1 4
Not enabled
LR TX Delta 60 5 4 1 4
Not enabled
Timeout
Discards Delta 60 200 4 10 4
Not enabled
Credit Loss
Reco Delta 1 1 4 0 4
Not enabled
TX Credit Not
Available Delta 1 10% 4 0% 4
Not enabled
RX Datarate Delta 60 80% 4 20% 4
Not enabled
TX Datarate Delta 60 80% 4 20% 4
Not enabled
TX-Slowport-
Count Delta 1 5 4 0 4
Not enabled
TX-Slowport-
Oper-Delay Absolute 1 50ms 4 0ms 4
Not enabled
TXWait Delta 1 40% 4 0% 4
Not enabled
------------------------------------------------------------------------------------------
 
switch# show port-monitor active
Policy Name : sample
Admin status : Active
Oper status : Active
Port type : All Access Ports
------------------------------------------------------------------------------------------
Counter Threshold Interval Rising Threshold event Falling Threshold event portguard
------------------------------------------------------------------------------------------
Link Loss Delta 60 5 4 1 4
Not enabled
Sync Loss Delta 60 5 4 1 4 Not enabled
Signal Loss Delta 60 5 4 1 4 Not enabled
Invalid Words Delta 60 1 4 0 4 Not enabled
Invalid CRC's Delta 60 5 4 1 4 Not enabled
TX Discards Delta 60 200 4 10 4 Not enabled
LR RX Delta 60 5 4 1 4 Not enabled
LR TX Delta 60 5 4 1 4 Not enabled
Timeout
Discards Delta 60 200 4 10 4 Not enabled
Credit Loss
Reco Delta 1 1 4 0 4 Not enabled
TX Credit Not
Available Delta 1 10% 4 0% 4 Not enabled
RX Datarate Delta 60 80% 4 20% 4 Not enabled
TX Datarate Delta 60 80% 4 20% 4 Not enabled
TX-Slowport
-Count Delta 1 5 4 0 4 Not enabled
TX-Slowport-
Oper-Delay Absolute 1 50ms 4 0ms 4 Not enabled
TXWait Delta 1 40% 4 0% 4 Not enabled
------------------------------------------------------------------------------------------
 
switch# show port-monitor sample
Policy Name : sample
Admin status : Active
Oper status : Active
Port type : All Access Ports
------------------------------------------------------------------------------------------
Counter Threshold Interval Rising Threshold event Falling Threshold event portgurard
------------------------------------------------------------------------------------------
Link Loss Delta 60 5 4 1 4
Not enabled
Sync Loss Delta 60 5 4 1 4 Not enabled
Signal Loss Delta 60 5 4 1 4 Not enabled
Invalid Words Delta 60 1 4 0 4 Not enabled
Invalid CRC's Delta 60 5 4 1 4 Not enabled
TX Discards Delta 60 200 4 10 4 Not enabled
LR RX Delta 60 5 4 1 4 Not enabled
LR TX Delta 60 5 4 1 4 Not enabled
Timeout Discards Delta 60 200 4 10 4 Not enabled
Credit Loss Reco Delta 1 1 4 0 4 Not enabled
TX Credit Not
Available Delta 1 10% 4 0% 4 Not enabled
RX Datarate Delta 60 80% 4 20% 4 Not enabled
TX Datarate Delta 60 80% 4 20% 4 Not enabled
TX-Slowport-Count Delta 1 5 4 0 4 Not enabled
TX-Slowport-Oper
-Delay Absolute 1 50ms 4 0ms 4 Not enabled
TXWait Delta 1 40% 4 0% 4 Not enabled
------------------------------------------------------------------------------------------
 
switch# show port-monitor default
 
Policy Name : default
Admin status : Not Active
Oper status : Not Active
Port type : All Ports
------------------------------------------------------ ------------------------------------
Counter Threshold Interval Rising Threshold event Falling Threshold event PMON Portguard
------------------------------------------------------------------------------------------
Link Loss Delta 60 5 4 1 4 Not enabled
Sync Loss Delta 60 5 4 1 4 Not enabled
Signal Loss Delta 60 5 4 1 4 Not enabled
Invalid Words Delta 60 1 4 0 4 Not enabled
Invalid CRC's Delta 60 5 4 1 4 Not enabled
TX Discards Delta 60 200 4 10 4 Not enabled
LR RX Delta 60 5 4 1 4 Not enabled
LR TX Delta 60 5 4 1 4 Not enabled
Timeout Discards Delta 60 200 4 10 4 Not enabled
Credit Loss Reco Delta 1 1 4 0 4 Not enabled
TX Credit Not
Available Delta 1 10% 4 0% 4 Not enabled
RX Datarate Delta 60 80% 4 20% 4 Not enabled
TX Datarate Delta 60 80% 4 20% 4 Not enabled
TX-Slowport-Count Delta 1 5 4 0 4 Not enabled
TX-Slowport-Oper
-Delay Absolute 1 50ms 4 0ms 4 Not enabled
TXWait Delta 1 40% 4 0% 4 Not enabled
------------------------------------------------------------------------------------------
switch#
 
 
switch# show port-monitor slowdrain
 
Policy Name : slowdrain
Admin status : Not Active
Oper status : Not Active
Port type : All Access Ports
------------------------------------------------------------------------------------------
Counter Threshold Interval Rising Threshold event Falling Threshold event PMON Portguard
------------------------------------------------------------------------------------------
Credit Loss Reco Delta 1 1 4 0 4 Not enabled
TX Credit Not
Available Delta 1 10% 4 0% 4 Not enabled
------------------------------------------------------------------------------------------
switch#
------------------------------------------------------------------------------------------
 

Displaying Port Group Monitor Status and Policies

The following commands display information about port group monitor:

switch# show port-group-monitor status
Port Group Monitor : Enabled
Active Policies : pgm2
Last 100 logs :
switch#
 
 
switch# show port-group-monitor
------------------------------------------------------------------------------------------
Port Group Monitor : enabled
------------------------------------------------------------------------------------------
Policy Name : pgm1
Admin status : Not Active
Oper status : Not Active
Port type : All Port Groups
------------------------------------------------------------------------------------------
Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold
------- --------- -------- -------------------- ----------------------
RX Performance Delta 60 50 10
TX Performance Delta 60 50 10
------------------------------------------------------------------------------------------
Policy Name : pgm2
Admin status : Active
Oper status : Active
Port type : All Port Groups
------------------------------------------------------------------------------------------
Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold
------- --------- -------- -------------------- ----------------------
RX Performance Delta 60 80 10
TX Performance Delta 60 80 10
------------------------------------------------------------------------------------------
Policy Name : default
Admin status : Not Active
Oper status : Not Active
Port type : All Port Groups
------------------------------------------------------------------------------------------
Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold
------- --------- -------- -------------------- ----------------------
RX Performance Delta 60 80 20
TX Performance Delta 60 80 20
------------------------------------------------------------------------------------------
 
switch# show port-group-monitor active
Policy Name : pgm2
Admin status : Active
Oper status : Active
Port type : All Port Groups
------------------------------------------------------------------------------------------
Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold
------- --------- -------- -------------------- ----------------------
RX Performance Delta 60 80 10
TX Performance Delta 60 80 10
------------------------------------------------------------------------------------------
 
switch# show port-group-monitor PGMON_policy
PPolicy Name : PGMON_policy
Admin status : Not Active
Oper status : Not Active
Port type : All Port Groups
------------------------------------------------------------------------------------------
Counter Threshold Interval %ge Rising Threshold %ge Falling Threshold
------- --------- -------- -------------------- ----------------------
RX Performance Delta 26 450 250
TX Performance Delta 60 100 80
------------------------------------------------------------------------------------------

Displaying Management Interface Configuration

To display the management interface configuration, use the show interface mgmt 0 command.

switch# show interface mgmt 0
mgmt0 is up
Hardware is FastEthernet
Address is 000c.30d9.fdbc
Internet address is 10.16.1.2/24
MTU 1500 bytes, BW 100 Mbps full Duplex
26388 packets input, 6101647 bytes
0 multicast frames, 0 compressed
0 input errors, 0 frame, 0 overrun 0 fifo
10247 packets output, 2389196 bytes, 0 underruns
0 output errors, 0 collisions, 0 fifo
0 carrier errors
 

Displaying VSAN Interface Information

To display VSAN interface information, use the show interface vsan command.

switch# show interface vsan 2
vsan2 is up, line protocol is up
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
 

Displaying Congestion Frame Timeout Value for FCoE

To display the congestion frame timeout value for FCoE use the following commands:

Step 1

switch# show logging onboard flow-control pause-count

(Optional) Displays the pause counter log with timestamp information.

Step 2

switch# show logging onboard flow-control pause-events

(Optional) Displays the pause event log with timestamp information.

Displaying Pause Frame Timeout for FCoE

To display the pause frame timeout value for FCoE use the following commands:

Step 1

switch# show logging onboard flow-control pause-count

Displays the pause counter log with timestamp information.

Step 2

switch# show logging onboard flow-control pause-events

(Optional) Displays the pause counters per module per interface with the timestamp information.

Step 3

switch# show logging onboard flow-control timeout-drops [module x] [last mm minutes] [last hh hours] [last dd days]

(Optional) Displays the timeout drops per module per interface with the time-stamp information.

Displaying Congestion drop Timeout Value for FC

To display the congestion drop timeout value for FC use the following command:

Step 1

switch# show logging onboard flow-control timeout-drops [module x] [last mm minutes] [last hh hours] [last dd days]

(Optional) Displays the timeout drops per module per interface with the time-stamp information.

Displaying No Credit Frame Timeout Value for FC

To display the no credit frame timeout value for FC use the following command:

Step 1

switch# s how logging onboard [module x] [starttime mm/dd/yy-hh:mm:ss] error-stats

Displays various error statistics per module per interface with the time-stamp information.

The following counters indicate that the no-credit-drop threshold has been reached:

FCP_CNTR_FORCE_TIMEOUT_ON

AK_FCP_CNTR_FORCE_TIMEOUT_ON

FCP_SW_CNTR_FORCE_TIMEOUT_ON

The following counters indicate that a credit has been received on the interface and the port no longer drops packets due to the no-credit-drop condition:

FCP_CNTR_FORCE_TIMEOUT_OFF

AK_FCP_CNTR_FORCE_TIMEOUT_OFF

FCP_SW_CNTR_FORCE_TIMEOUT_OFF

Displaying Slow Port Monitor Events

To display slow port monitor events, use the show process creditmon slowport-monitor-events command.

This command is applicable for both supervisor and module prompts.

Step 1

switch# show process creditmon slowport-monitor-events [module x [port y]]

Displays any slowport-monitor events per module.

Step 2

switch# show logging onboard slowport-monitor-events

Displays the slowport-monitor events on the OBFL (On-Board Fault Log). The slowport-monitor events are logged periodically into the OBFL.

The following examples displays the creditmon slow port monitor statistics information for the 16-Gbps modules.

switch# show process creditmon slowport-monitor-events
 
Module: 06 Slowport Detected: YES
=========================================================================
Interface = fc6/3
----------------------------------------------------------------
| admin | slowport | oper | Timestamp |
| delay | detection | delay | |
| (ms) | count | (ms) | |
----------------------------------------------------------------
| 1 | 46195 | 1 | 1. 10/14/12 21:46:51.615 |
| 1 | 46193 | 50 | 2. 10/14/12 21:46:51.515 |
| 1 | 46191 | 50 | 3. 10/14/12 21:46:51.415 |
| 1 | 46189 | 50 | 4. 10/14/12 21:46:51.315 |
| 1 | 46187 | 50 | 5. 10/14/12 21:46:51.215 |
| 1 | 46185 | 50 | 6. 10/14/12 21:46:51.115 |
| 1 | 46183 | 50 | 7. 10/14/12 21:46:51.015 |
| 1 | 46181 | 50 | 8. 10/14/12 21:46:50.915 |
| 1 | 46179 | 50 | 9. 10/14/12 21:46:50.815 |
| 1 | 46178 | 50 |10. 10/14/12 21:46:50.715 |
----------------------------------------------------------------
 
switch#
 

Note For 16-Gbps modules and switches (Cisco MDS 9700, 9148S, 9250i, and 9396S switches only), if no-credit-drop timeout is configured, the maximum value of oper delay as shown in slowport-monitor-events is limited by the no-credit-drop timeout. So the maximum value for oper delay can reach up to no-credit-drop timeout, (even if the actual slowport delay from the device is higher) because the frames are forcefully dropped by the hardware when oper delay reaches no-credit-drop timeout. It applies to only 9700, 9148S, 9250i and 9396S only (16Gbps modules and switches).


The following example displays the creditmon slow port monitor statistics for the platform Cisco MDS 9500 switches (8-Gbps modules):

 
switch# show process creditmon slowport-monitor-events
Module: 04 Slowport Detected: YES
========================================================================
Interface = fc4/13
--------------------------------------------------------
| admin | slowport | Timestamp |
| delay | detection | |
| (ms) | count | |
--------------------------------------------------------
| 1 | 194 | 1. 04/29/15 17:19:13.345 |
| 1 | 193 | 2. 04/29/15 17:19:13.245 |
| 1 | 192 | 3. 04/29/15 17:19:13.145 |
| 1 | 191 | 4. 04/29/15 17:19:13.045 |
| 1 | 190 | 5. 04/29/15 17:19:12.945 |
| 1 | 189 | 6. 04/29/15 17:19:12.845 |
| 1 | 188 | 7. 04/29/15 17:19:12.745 |
| 1 | 187 | 8. 04/29/15 17:19:12.645 |
| 1 | 186 | 9. 04/29/15 17:19:12.545 |
| 1 | 185 |10. 04/29/15 17:19:12.445 |
--------------------------------------------------------
========================================================================
switch#
 

Note The MDS 9500 series 8-Gbps modules can only detect if the slow-port monitor has reached the threshold (admin delay) or not for every 100ms-polling interval. The modules cannot determine the actual length of time higher than the threshold that the port was in 0 Tx B2B credits remaining. Additionally, the modules cannot determine if the slowport-monitor has reached the threshold (admin delay) multiple times. The modules can record only 1 event per 100ms polling interval.


 

The following example displays the creditmon slow port monitor statistics for the platform Cisco MDS 9500 switches (Advanced 8-Gbps modules):


Note The MDS 9500 series Advanced 8-Gbps modules utilize the txwait functionality to implement slowport-monitoring. Hence, the txwait oper delay is the total amount of time the port was in 0 Tx B2B credits remaining condition during the 100ms-polling interval. No specific duration of time is indicated.


 
switch# show process creditmon slowport-monitor-events module 1
        Module: 01      Slowport Detected: YES
===================================================================
 Interface = fc1/5
----------------------------------------------------------------
| admin  | slowport  | txwait|            Timestamp            |
| delay  | detection |  oper |                                 |
| (ms)   | count     | delay |                                 |
|        |           |  (ms) |                                 |
----------------------------------------------------------------
|  10    |       888 |   93  | 1. 04/30/15 21:33:42.561        |
|  10    |       887 |  81  | 2. 04/30/15 21:33:42.461        |
|  10    |       886 |  76  | 3. 04/30/15 21:33:42.361        |
|  10    |       885 |   99  | 4. 04/30/15 21:33:42.261        |
|  10    |       884 |   99  | 5. 04/30/15 21:33:42.161        |
--------------------------------------------------------
========================================================================

Note For Advanced 8-Gbps modules, the txwait value does not increment once the no-credit-drop threshold has been reached as the frames are forcefully dropped by the hardware and there are no frames remaining queued for transmit. Consequently, when slowport-monitor is used in conjunction with no-credit-drop the txwait oper delay value as shown in slowport-monitor-events may be lower than expected.


The following example displays the txwait statistics for a particular interface for the platform Cisco MDS 9500 switches (Advanced 8-Gbps modules and 16-Gbps modules)

switch# show interface fc1/1 counters
or
switch# show interface fc1/1 counters details
 
switch(config)# show int fc1/81 counters
fc1/81
5 minutes input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
5 minutes output rate 280288 bits/sec, 35036 bytes/sec, 15 frames/sec
5206879 frames input, 11142684612 bytes
0 class-2 frames, 0 bytes
5206879 class-3 frames, 11142684612 bytes
0 class-f frames, 0 bytes
171 discards, 175 errors, 0 CRC/FCS
0 unknown class, 0 too long, 4 too short
2498081 frames output, 5345868788 bytes
0 class-2 frames, 0 bytes
2498081 class-3 frames, 5345868788 bytes
0 class-f frames, 0 bytes
7260927715 discards, 0 errors
7260927715 timeout discards, 0 credit loss
2 input OLS, 272 LRR, 0 NOS, 0 loop inits
3 output OLS, 3 LRR, 2 NOS, 0 loop inits
2 link failures, 0 sync losses, 0 signal losses
2498321 Transmit B2B credit transitions to zero
275 Receive B2B credit transitions to zero
54867361792 2.5us TxWait due to lack of transmit credits
Percentage Tx credits not available for last 1s/1m/1h/72h: 50%/50%/92%/52%
32 receive B2B credit remaining
0 transmit B2B credit remaining
0 low priority transmit B2B credit remaining
Last clearing of "show interface" counters :never
switch(config)#
=================================================================================
switch(config)# show int fc1/81 counters details
fc1/81
5206879 frames, 11142684612 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
5206879 class-3 frames, 11142684612 bytes received
0 class-f frames, 0 bytes received
171 discards, 175 errors received
7273423181 discards, 0 errors transmitted
2499069 frames, 5347983108 bytes transmitted
0 class-2 frames, 0 bytes transmitted
2499069 class-3 frames, 5347983108 bytes transmitted
171 class-3 frames discarded
0 class-f frames, 0 bytes transmitted
0 class-f frames discarded
0 multicast packets received, 0 transmitted
0 broadcast packets received, 0 transmitted
5206879 unicast packets received, 2499069 transmitted
7273423181 timeout discards, 0 credit loss
2 link failures, 0 sync losses, 0 signal losses
0 primitive sequence protocol errors
31822 invalid transmission words
0 invalid CRCs, 0 Delimiter Errors
0 address identifier errors
0 link reset received while link is active
272 link reset transmitted while link is active
2 Offline Sequence errors received
3 Offline Sequence errors transmitted
0 frames received that are shorter than
the minimum allowable frame length
regardless of the CRC/FCS error
0 frames received that are longer than
the maximum frame length and also have a
CRC/FCS error
54879203328 2.5us TxWait due to lack of transmit credits
0 frames received with length greater
than what was agreed to in FLOGI/PLOGI
4 frames received with length less than
the minimum indicated by the frame header
272 link reset responses received
3 link reset responses transmitted
0 non-operational sequences received
2 non-operational sequences transmitted
0 fragmented frames received
171 frames received with EOF aborts
0 unknown class frames received
0 8b10b disparity errors
0 frames discarded
0 Exchange Link Parameters switch fabric
internal link service request failures
2499309 Transmit B2B credit transitions to zero
275 Receive B2B credit transitions to zero
0 Enhanced Inter Switch Link (EISL) frames
discarded
0 framing errors
0 F8 type LIP sequence errors received
0 F8 type LIP sequence errors issued
0 Non F8 type LIP sequence errors received
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: 50%/50%/92%/52%
switch(config)#
 

TXWAIT History Graph

The transmit wait history for slow ports on Advanced 8-Gbps and 16-Gbps modules and switches can be displayed in the form of a graph over a period of time. The total transmit wait time for each time period is displayed as a column of '#'s. The actual value appears above each column as a vertically printed number. The following graphs can be displayed:

  • Seconds scale—The transmit wait history for the port over the last 60 seconds. The Y-axis value is the total transmit wait time for each second in milliseconds.
  • Minutes scale—The transmit wait history for the port over the last 60 seconds. The Y-axis value is the total transmit wait time for each minute in seconds to one decimal place.
  • Hours scale—The transmit wait history for the port over the last 60 seconds. The Y-axis value is the total transmit wait time for each hour in minutes.

To display the txwait history for a given interval of time, follow these steps:

Command
Purpose

Step 1

switch# show process creditmon txwait-history [module x [port y]]

Displays the txwait history graph for the period when the tx credit is not available for a given interval of time (seconds, minutes, or hours).

Step 2

switch# show logging onboard txwait

Displays the txwait time in 2.5 microsecond units as well as in seconds. The txwait delta values are logged periodically (every 20 seconds) into the OBFL when txwait increases by at least 100ms in the 20-seconds interval.

Step 3

switch# show interface fc x/y counters

Displays the total txwait value for a particular interface in 2.5 microsecond units.

The following example displays the txwait history graph in seconds for Advanced 8-Gbps modules and 16-Gbps modules:
 
switch(config)# show process creditmon txwait-history module 1 port 81
show process creditmon txwait-history port 81`
 
TxWait history for port fc1/81:
==============================
 
455555555455554555554555599999999999999999999999999999999999
900000000800009000008100011111231922322211321121112112113111
433799991899990359909838608935137962088988254848894870461938
1000 #
900 ###################################
800 ###################################
700 ###################################
600 ###################################
500 ############################################################
400 ############################################################
300 ############################################################
200 ############################################################
100 ############################################################
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
 
Tx Credit Not Available per second (last 60 seconds)
# = TxWait (ms)
 
The following example displays the txwait history graph in minutes for Advanced 8-Gbps modules and 16-Gbps modules:
 
555555555555555555555555555555555555555555555555555555555555
055555555555555555555555555555555555555555555555555555555555
............................................................
035444445444445445454444444445635363534375434453343554545344
60
54 ###########################################################
48 ############################################################
42 ############################################################
36 ############################################################
30 ############################################################
24 ############################################################
18 ############################################################
12 ############################################################
6 ############################################################
0....5....1....1....2....2....3....3....4....4....5....5....6
0 5 0 5 0 5 0 5 0 5 0
 
Tx Credit Not Available per minute (last 60 minutes)
# = TxWait (secs)
 
The following example displays the txwait history graph in hours for 8-Gbps modules and 16-Gbps modules:
 
33333333333333333333333333333333333333333
33333333333333333333333333333333333333332
22222222222222222222222222222222222222229
777788777777877877778777877677777777876790000000000000000000000000000000
3600
3240 #########################################
2880 #########################################
2520 #########################################
2160 #########################################
1800 #########################################
1440 #########################################
1080 #########################################
720 #########################################
360 #########################################
0....5....1....1....2....2....3....3....4....4....5....5....6....6....7.7
0 5 0 5 0 5 0 5 0 5 0 5 0 2
 
Tx Credit Not Available per hour (last 72 hours)
# = TxWait (secs)
 
 
The following example displays the txwait OBFL logging for Advanced 8-Gbps modules and 16-Gbps modules:
 
switch# show logging onboard txwait
Notes:
    - sampling period is 20 seconds
    - only txwait delta value >= 100 ms are logged
---------------------------------
 Module: 1 txwait count
---------------------------------
 
-----------------------------------------------------------------------------
| Interface | Delta TxWait Time | Congestion | Timestamp                |
|           | 2.5us ticks | seconds |            |                          |
-----------------------------------------------------------------------------
|   fc1/11  |  3435973 | 08   |      42%   | Sun Sep 30 05:23:05 2001 |
|   fc1/11  |  6871947 | 17   |      85%   | Sun Sep 30 05:22:25 2001 |