Table Of Contents
Configuring Interfaces
Configuring Fibre Channel Interfaces
About Interface Modes
E Port
F Port
FL Port
TL Port
TE Port
SD Port
Fx Port
B Port
Auto Mode
About Interface States
Administrative States
Operational States
Reason Codes
Configuring Fibre Channel Interfaces
Configuring a Range of Interfaces
Disabling Interfaces
Configuring Interface Modes
Configuring Administrative Speeds
Configuring Interface Descriptions
Configuring Buffer-to-Buffer Credits
Configuring Receive Data Field Size
Configuring the Beacon Mode
Identifying the Beacon LEDs
Configuring Switchport Defaults
Default Settings
Configuring the Management Interface
Configuring VSAN Interfaces
Displaying Interface Information
Displaying TL Port Information
TL Port Translation Guidelines
Configuring Interfaces
A switch's main function is to relay frames from one data link to another. To do that, the characteristics of the interfaces through which the frames are received and sent must be defined. The configured interfaces can be Fibre Channel interfaces, management interface (mgmt0), or VSAN interfaces.
This chapter describes the basic interface configuration to get your switch up and running. It includes the following sections:
•
Configuring Fibre Channel Interfaces
•
Default Settings
•
Configuring the Management Interface
•
Configuring VSAN Interfaces
•
Displaying Interface Information
Note
See "Initial Configuration" and "Configuring IP Services," for more information on configuring mgmt0 interfaces.
Before you begin configuring the switch, ensure that the modules in the chassis are functioning as designed. To verify the status of a module at any time, issue the show module command in EXEC mode (see the "Verifying the Module Status" section).
Configuring Fibre Channel Interfaces
This section describes Fibre Channel interface characteristics, including (but are not limited to) modes, states, and speeds. It includes the following sections:
•
About Interface Modes
•
About Interface States
•
Configuring Fibre Channel Interfaces
•
Configuring a Range of Interfaces
•
Disabling Interfaces
•
Configuring Interface Modes
•
Configuring Administrative Speeds
•
Configuring Interface Descriptions
•
Configuring Buffer-to-Buffer Credits
•
Configuring the Beacon Mode
About Interface Modes
Each physical Fibre Channel interface in a switch may operate in one of several modes: E port, F port, FL port, TL port, TE port, and SD port (see Figure 9-1). Besides these modes, each interface may be configured in auto or Fx port mode. These two modes determine the port type during interface initialization. A brief description of each interface mode follows.
Figure 9-1 Cisco MDS 9000 Family Switch Interface Modes
Note
Interfaces are created in VSAN 1 by default. See "Configuring and Managing VSANs."
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).
A brief description of each mode interface follows.
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 "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.
TL Port
In translative loop port (TL port) mode, an interface functions as a translative loop port. It may be connected to one or more private loop devices (NL ports). TL port mode is specific to Cisco MDS 9000 family switches and have similar properties as FL ports. TL ports enable communication between a private loop device and one of the following devices:
•
A device attached to any switch on the fabric
•
A device on a public loop anywhere in the fabric
•
A device on a different private loop anywhere in the fabric
•
A device on the same private loop
See the "Displaying TL Port Information" section. TL ports support class 2 and class 3 services.
Note
Devices attached to TL ports are recommended to be configured in zones which have up to 64 zone members.
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 (see "Configuring Trunking"). TE ports support class 2, class 3, and class F service.
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 merely 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 "Monitoring Network Traffic Using SPAN").
Fx Port
Interfaces configured as Fx ports are allowed to 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 Cisco's 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. Figure 17-11 depicts a typical SAN extension over an IP network
When an FCIP peer is a SAN extender device that only support 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 "Configuring IP Storage").
Auto Mode
Interfaces configured as auto are allowed to operate in one of the following modes: F port, FL port, E port, or TE 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 "Configuring Trunking"). TL ports and SD ports are not determined during initialization and are administratively configured.
About 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 9-1.
Table 9-1 Administrative States
Administrative State
|
Description
|
Up
|
Enables an interface.
|
Down
|
Disables an interface. When an interface is administratively disabled (shutdown command), 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 9-2.
Table 9-2 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 mode.
|
Reason Codes
Reason codes are dependent on the operational state of the interface as described in Table 9-3.
Table 9-3 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 9-4.
|
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 9-4.
Table 9-4 Reason Codes for Nonoperational States
Reason Code
|
Description
|
Applicable Modes
|
Link failure or not connected
|
Physical layer link is not operational.
|
All
|
Fcot not present
|
The Fibre Channel optical transmitter 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
|
Waiting 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 configure the interface as shutdown followed by no shutdown.
|
Isolation due to ELP failure
|
Port negotiation failed.
|
Only E ports and TE ports
|
Isolation due to ESC failure
|
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 other side 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.
|
Configuring 32-port Switching Modules
The 32-port 1/2-Gbps switching module contains 8 port groups of 4 ports each. When configuring these modules the following guidelines apply:
•
You can configure only the first port in each 4-port group (for example, the first port in ports 1-4, the fifth port in ports 5-8 and so on) as an E port. If the first port in the group is configured as an E port, the other three ports in each group (ports 2-4, 6-8 and so on) are not usable and remain in the shutdown state.
•
If any of the other three ports are configured in a no shutdown state, you cannot configure the first port as an E port. The other three ports continue to remain in a no shutdown state.
•
Generally, the default port mode is auto. The auto option is not allowed in a 32-port switching module.
•
The default port mode for 32-port switching modules is Fx (Fx negotiates to F or FL).
Configuring Fibre Channel Interfaces
To configure a Fibre Channel interface, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface fc1/1
|
Configures the specified interface.
|
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).
Configuring a Range of Interfaces
To configure a range of interfaces, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface fc1/1 - 4 , fc2/1 - 3
|
Configures the range of specified interfaces.
Note In this command, provide a space before and after the comma.
|
Disabling Interfaces
Interfaces on a port are shut down by default (unless you modified the initial configuration). To enable traffic flow, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface fc1/1
|
Configures the specified interface.
|
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).
|
switch(config-if)# shutdown
|
Shuts down the interface and disables traffic flow (default).
|
Configuring Interface Modes
To configure the interface mode, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface fc1/1
|
Configures the specified interface.
|
Step 3
|
switch(config-if)# switchport mode F
|
Configures the administrative mode of the port. You can set the operational state to auto, E, F, FL, Fx, TL, 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
|
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.
|
Configuring Administrative Speeds
By default, the administrative speed for an interface is automatically calculated by the switch. To configure the administrative speed of the interface, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config-if)# switchport speed 1000
|
Configures the administrative speed of the interface to 1000 Mbps.
The number indicates the speed in megabits per second (Mbps). You can set the speed to 1000 Mbps (for 1Gbps interfaces), 2000 Mbps (for 2 Gbps interfaces), or auto (default).
|
switch(config-if)# switchport speed auto
|
Reconfigures the factory default (auto) administrative speed of the interface.
|
Configuring Interface Descriptions
To configure a description for an interface, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface fc1/1
|
Configures the specified interface.
|
Step 3
|
switch(config-if)# switchport description cisco-HBA2
|
Configures the description of the interface.
The string may be up to 80 characters long.
|
switch(config-if)# no switchport description
|
Clears the description of the interface.
|
Configuring Buffer-to-Buffer Credits
Buffer-to-buffer credits (BB_credits) are a flow control mechanism to ensure that FC switches do not run out of buffers, since switches must not drop frames. Buffer Credits are negotiated on a per-hop basis.
The receive BB_credit value may be configured for each FC interface. In most cases, you don't need to modify the default configuration.
Note
The receive BB_credit values depend on the module type and the port mode:
16-port switching modules: The default value is 16 for the Fx mode and 255 for E or TE modes. The maximum value is 255 in all modes. This value can be changed as required.
32-port switching modules: The default value is 12 for the Fx, E, and TE modes. These values cannot be changed.
To configure buffer-to-buffer credits to a Fibre Channel interface, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface fc1/1
|
Configures the specified interface.
|
Step 3
|
switch(config-if)# switchport fcrxbbcredit default
|
Applies the default operational value to the selected interface.
The operational value depends on the port mode. The default values are assigned based on the port capabilities.
|
switch(config-if)# switchport fcrxbbcredit 5
|
Assigns a BB_credit of 5 to the selected interface. The range to assign BB_credits is between 1 and 255.
|
switch(config-if)# switchport fcrxbbcredit 5 mode E
|
Assigns this value if the port is operating in E or TE mode. The range to assign BB_credits is between 1 and 255.
|
switch(config-if)# switchport fcrxbbcredit 5 mode
Fx
|
Assigns this value if the port is operating in F or FL mode. The range to assign BB_credits is between 1 and 255.
|
Configuring Receive Data Field Size
You can also configure the receive data field size for Fibre Channel interfaces by issuing the switchport fcrxbufsize command. The default data field size is 2112 bytes, the frame length will be 2148 bytes.
To configure data field size for a Fibre Channel interface, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface fc1/1
|
Configures the specified interface.
|
Step 3
|
switch(config-if)# switchport fcrxbufsize 2000
|
Reduces the data field size for the selected interface to 2000 bytes. The default is 2112 bytes and the range is from 256 to 2112 bytes.
|
Configuring the 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. The beacon command has no effect on the operation of the interface.
To disable beacon mode for a specified interface or range of interfaces, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface fc1/1
|
Configures the specified interface.
|
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.
|
Identifying the Beacon LEDs
Figure 9-2 displays the status, link, and speed LEDs in a 16-port switching module.
Figure 9-2 Cisco MDS 9000 Family Switch Interface Modes
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—beacon mode is disabled
•
On (flashing green)—the beacon mode is enabled. The LED flashes at one-second intervals.
Configuring Switchport Defaults
You can configure default values for various switch port attributes. If you configure the following attributes, they will be applied globally to all future switch port configurations, even if you do not individually specify them at that time.
To configure switch port attributes, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# no system default
switchport shutdown
|
Configures the default setting for administrative state of an interface as Up. (The factory default setting is Down).
Tip ![](../../../../../../../../../../i/templates/blank.gif) This command is applicable only to interfaces for which no user configuration exists for the administrative state.
|
switch(config)# system default
switchport shutdown
|
Configures the default setting for administrative state of an interface as Down. This is the factory default setting.
Tip ![](../../../../../../../../../../i/templates/blank.gif) 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
|
Configures the default setting for administrative trunk mode state of an interface as Auto.
(The factory default setting is trunk mode On).
|
Default Settings
Table 9-5 lists the default settings for Fibre Channel interface parameters.
Table 9-5 Default Fibre Channel 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)
|
Trunk-allowed VSANs
|
1 to 4093
|
Interface VSAN
|
Default VSAN (1)
|
Beacon mode
|
Off
|
Configuring the Management Interface
You can remotely configure the switch through the management interface (mgmt0). To configure a connection remotely, you must configure the IP parameters (IP address, subnet mask, and default gateway) from the CLI so that the switch is reachable.
Note
Before you begin to configure the management interface manually, obtain the switch's IP address and IP subnet mask.
To configure the mgmt0 Ethernet interface, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface mgmt0
|
Configures the management Ethernet interface on the switch to configure the management interface.
|
Step 3
|
switch(config-if)# ip address 172.16.1.2 255
255.255.0
|
Enters the IP address and IP subnet mask for the interface specified in Step 2.
|
Step 4
|
switch(config-if)# no shutdown
|
Enables the interface.
|
Step 5
|
|
Returns to configuration mode.
|
Step 6
|
switch(config)# ip default-gateway 1.1.1.4
switch(config)#
|
Configures the default gateway IP address.
|
Step 7
|
|
Returns to EXEC mode.
|
Step 8
|
switch# copy running-config startup-config
|
Saves your configuration changes to the file system.
Note This step is optional. If you wish to save your configuration, you can issue this command at any time.
|
The management port (mgmt0) is autosensing and operates as full duplex mode and 100 Mbps speed. The speed and mode cannot be configured.
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.
Configuring 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.
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 using the interface VSAN command. This is not done automatically.
•
If you delete the VSAN, the attached interface is automatically deleted.
To create a VSAN interface, follow these steps:
|
Command
|
Purpose
|
Step 1
|
|
Enters configuration mode.
|
Step 2
|
switch(config)# interface vsan 5
|
Configures a VSAN with the ID 5.
|
You can configure each interface only in one VSAN.
After configuring the VSAN interface, you can configure an IP address or Virtual Router Redundancy Protocol (VRRP) features (see "Configuring IP Services").
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 9-1 to 9-9.
Example 9-1 Displays All Interfaces
Hardware is Fibre Channel
Port WWN is 20:81:00:05:30:00:12:5e
Peer port WWN is 22:01:00:05:30:00:12:9e
Admin port mode is E, trunk mode is auto
Receive B2B Credit is 255
Receive Buffer Size is 2112
Trunk vsans (admin allowed and active) (1-15)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
5 minutes input rate 40 bits/sec, 5 bytes/sec, 0 frames/sec
5 minutes output rate 24 bits/sec, 3 bytes/sec, 0 frames/sec
2161 frames input, 182556 bytes, 0 discards
2164 frames output, 139904 bytes, 0 discards
1 input OLS, 1 LRR, 1 NOS, 0 loop inits
2 output OLS, 1 LRR, 1 NOS, 0 loop inits
Hardware is Fibre Channel
Port WWN is 22:09:00:05:30:00:12:5e
Admin port mode is auto, trunk mode is auto
Port mode is FL, FCID is 0xef0100
Receive Buffer Size is 2112
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
5 frames input, 560 bytes, 0 discards
4 frames output, 524 bytes, 0 discards
0 input OLS, 0 LRR, 0 NOS, 2 loop inits
2 output OLS, 0 LRR, 1 NOS, 1 loop inits
Hardware is Fibre Channel
74994 packets input, 8076884 bytes
0 multicast frames, 0 compressed
0 input errors, 0 frame, 0 overrun 0 fifo
74991 packets output, 7689168 bytes, 0 underruns
0 output errors, 0 collisions, 0 fifo
Address is 0005.3000.2c5a
Internet address is 172.22.90.38/24
MTU 1500 bytes, Speed is 100 Mbps
9319 packets input, 738784 bytes
0 multicast frames, 0 compressed
0 input errors, 0 frame, 0 overrun 0 fifo
150 packets output, 34090 bytes, 0 underruns
0 output errors, 0 collisions, 0 fifo
vsan1 is up, line protocol is up
WWPN is 10:00:00:05:30:00:12:63, FCID is 0xef001e
Internet address is 10.10.11.10/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
port-channel 2 is trunking
Hardware is Fibre Channel
Port WWN is 24:02:00:05:30:00:26:1e
Admin port mode is E, trunk mode is on
Trunk vsans (admin allowed and active) (1-5)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
5 minutes input rate 8 bits/sec, 1 bytes/sec, 0 frames/sec
5 minutes output rate 8 bits/sec, 1 bytes/sec, 0 frames/sec
3534 frames input, 251672 bytes, 0 discards
3534 frames output, 176108 bytes, 0 discards
9 input OLS, 8 LRR, 0 NOS, 0 loop inits
13 output OLS, 11 LRR, 11 NOS, 0 loop inits
You can also specify arguments to display interface information.
Example 9-2 Displays a Range of Interfaces
switch# show interface fc2/5 , fc2/9
switch# show int fc2/5 - 10
Hardware is Fibre Channel
Port WWN is 20:45:00:05:30:00:26:1e
Peer port WWN is 21:85:00:05:30:00:25:9e
Admin port mode is E, trunk mode is on
Receive B2B Credit is 255
Receive Buffer Size is 2112
Belongs to port-channel 2
Trunk vsans (admin allowed and active) (1-5)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
5 minutes input rate 8 bits/sec, 1 bytes/sec, 0 frames/sec
5 minutes output rate 8 bits/sec, 1 bytes/sec, 0 frames/sec
1542 frames input, 105748 bytes, 0 discards
1542 frames output, 76656 bytes, 0 discards
5 input OLS, 5 LRR, 0 NOS, 0 loop inits
8 output OLS, 6 LRR, 6 NOS, 0 loop inits
Hardware is Fibre Channel
Port WWN is 20:49:00:05:30:00:26:1e
Peer port WWN is 21:89:00:05:30:00:25:9e
Admin port mode is E, trunk mode is off
Port mode is E, FCID is 0x7c0000
Receive B2B Credit is 255
Receive Buffer Size is 2112
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
624 frames input, 37736 bytes, 0 discards
625 frames output, 30248 bytes, 0 discards
3 input OLS, 3 LRR, 2 NOS, 0 loop inits
7 output OLS, 5 LRR, 5 NOS, 0 loop inits
Example 9-3 Displays a Specific Interface
switch# show interface fc2/9
Hardware is Fibre Channel
Port WWN is 20:49:00:05:30:00:26:1e
Peer port WWN is 21:89:00:05:30:00:25:9e
Admin port mode is E, trunk mode is off
Port mode is E, FCID is 0x7c0000
Receive B2B Credit is 255
Receive Buffer Size is 2112
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
624 frames input, 37736 bytes, 0 discards
625 frames output, 30248 bytes, 0 discards
3 input OLS, 3 LRR, 2 NOS, 0 loop inits
7 output OLS, 5 LRR, 5 NOS, 0 loop inits
Example 9-4 Displays a VSAN Interface
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
Example 9-5 Displays Port Description
switch# show interface description
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Example 9-6 Displays Interface Information in a Brief Format
switch# show interface brief
-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status Oper Oper Port-channel
-------------------------------------------------------------------------------
fc2/5 1 E on trunking TE 2 port-channel 2
fc2/6 1 E on trunking TE 2 port-channel 2
fc2/7 1 E on down -- -- --
fc2/8 1 auto on fcotAbsent -- -- --
fc2/9 3 E off up E 2 --
fc2/12 3 E on down -- -- port-channel 4
fc3/14 1 SD -- up SD 1 --
fc9/1 1 auto on fcotAbsent -- -- --
fc9/9 1 auto auto up FL 1 --
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Status IP Address Speed MTU
-------------------------------------------------------------------------------
mgmt0 up 172.22.90.38/24 100 Mbps 1500
-------------------------------------------------------------------------------
Interface Status IP Address Speed MTU
-------------------------------------------------------------------------------
vsan1 up 10.10.11.10/24 1 Gbps 1500
vsan2 up 10.10.12.10/24 1 Gbps 1500
-------------------------------------------------------------------------------
Interface Vsan Admin Status Oper Oper
-------------------------------------------------------------------------------
port-channel 1 1 off noOperMembers -- --
port-channel 2 1 on trunking TE 4
port-channel 3 3 off noOperMembers -- --
Example 9-7 Displays Interface Counters
switch# show interface counters
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
3505 frames output, 198888 bytes
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
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 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 class-2 frames, 0 bytes
0 class-3 frames, 0 bytes
0 class-f frames, 0 bytes
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
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
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 packets input, 0 bytes, 0 errors, 0 multicast
0 packets output, 0 bytes, 0 errors, 0 dropped
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 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 class-2 frames, 0 bytes
0 class-3 frames, 0 bytes
0 class-f frames, 0 bytes
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 9-8 Displays Interface Counters in Brief Format
switch# show interface counters brief
-------------------------------------------------------------------------------
Interface Input (rate is 5 min avg) Output (rate is 5 min avg)
----------------------------- -----------------------------
Mbits/s Frames Mbits/s Frames
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Interface Input (rate is 5 min avg) Output (rate is 5 min avg)
----------------------------- -----------------------------
Mbits/s Frames Mbits/s Frames
-------------------------------------------------------------------------------
port-channel 2 0 3946 0 3946
Example 9-9 Displays Transceiver Information
switch# show interface transceiver
part number is QFBR-5796L
serial number is A00156980
basic id fields (bytes 0-63)
0x03 0x04 0x07 0x00 0x00 0x00 0x00 0x20
0x40 0x0C 0x05 0x01 0x15 0x00 0x00 0x00
0x1E 0x0F 0x00 0x00 0x43 0x49 0x53 0x43
0x4F 0x2D 0x41 0x47 0x49 0x4C 0x45 0x4E
0x54 0x20 0x20 0x20 0x00 0x00 0x30 0xD3
0x51 0x46 0x42 0x52 0x2D 0x35 0x37 0x39
0x36 0x4C 0x20 0x20 0x20 0x20 0x20 0x20
0x20 0x20 0x20 0x20 0x00 0x00 0x00 0x86
extended id fields (bytes 64-95)
0x00 0x1A 0x00 0x00 0x41 0x30 0x30 0x31
0x35 0x36 0x39 0x38 0x30 0x20 0x20 0x20
0x20 0x20 0x20 0x20 0x30 0x32 0x30 0x38
0x32 0x30 0x20 0x20 0x00 0x00 0x00 0x44
vendor specific data (bytes 96-127)
0x00 0x00 0x06 0x36 0x31 0x8D 0x23 0xB5
0x8E 0xC2 0x13 0x9E 0xAC 0x57 0x47 0xB8
0xAB 0x37 0x19 0x00 0x00 0x00 0x00 0x00
0x00 0x00 0x00 0x00 0x01 0x7D 0x67 0x74
fc9/7 fcot is present but not supported
part number is IBM42P21SNY
serial number is 53P1487000WDN
basic id fields (bytes 0-63)
0x03 0x00 0x07 0x00 0x00 0x00 0x00 0x20
0x40 0x0C 0x05 0x01 0x15 0x00 0x00 0x00
0x1E 0x0F 0x00 0x00 0x49 0x42 0x4D 0x20
0x20 0x20 0x20 0x20 0x20 0x20 0x20 0x20
0x20 0x20 0x20 0x20 0x00 0x08 0x00 0x5A
0x49 0x42 0x4D 0x34 0x32 0x50 0x32 0x31
0x53 0x4E 0x59 0x20 0x20 0x20 0x20 0x20
0x41 0x41 0x32 0x30 0x00 0x00 0x00 0x07
extended id fields (bytes 64-95)
0x00 0x1A 0x05 0x05 0x35 0x33 0x50 0x31
0x34 0x38 0x37 0x30 0x30 0x30 0x57 0x44
0x4E 0x20 0x20 0x20 0x30 0x32 0x30 0x35
0x31 0x30 0x30 0x31 0x00 0x00 0x00 0x12
vendor specific data (bytes 96-127)
0x49 0x42 0x4D 0x20 0x53 0x46 0x50 0x53
0x20 0x41 0x52 0x45 0x20 0x43 0x4C 0x41
0x53 0x53 0x20 0x31 0x20 0x4C 0x41 0x53
0x45 0x52 0x20 0x53 0x41 0x46 0x45 0x20
Displaying TL Port Information
Private loop devices refer to legacy devices that reside on arbitrated loops. These devices are not aware of a switch fabric since they only communicate with devices on the same physical loop.
The legacy devices are used in Fibre Channel networks and devices outside the loop may need to communicate with them.The communication functionality is provided through TL ports.
Use the switchport mode command to configure a TL port (see the "Configuring Interface Modes" section).
The show tlport command displays the TL port interface configurations. This command provides a list of all TL ports configured on a box and shows the associated VSAN, the FC ID for the port (only domain and area are valid), and the current operational state of the TL port (up or initializing). See Examples 9-10 to 9-13.
Example 9-10 Displays the TL Ports in All VSANs
-------------------------------
Interface Vsan FC-ID State
------------------------- ------
TL ports allow a private device (devices that physically reside on the loop) to see a fabric device and vice-versa by proxying fabric devices on the loop. Fabric devices are proxied by allocating each fabric device an ALPA on this loop.
In addition to these proxied devices, other virtual devices (local or remote domain controller addresses) are also allocated ALPAs on the loop. A switch reserves the ALPA for its own communication with private devices, and the switch acts as a SCSI Initiator.
The first column in the output of the show tlport interface command is the ALPA identity of the device on the loop. The second lists the port WWNs, the third lists the node WWNs for each device, the fourth identifies the device as a SCSI initiator or target, and the last column is the real FC ID of the device.
Example 9-11 Displays the Detailed Information for a Specific TL Port
switch# show tlport interface fc1/16 all
fc1/16 is up, vsan 1, FCID 0x420000
--------------------------------------------------------------------------------
alpa pWWN nWWN SCSI Type Device FC-ID
--------------------------------------------------------------------------------
0x01 20:10:00:05:30:00:4a:de 20:00:00:05:30:00:4a:de Initiator Proxied 0xfffc42
0x73 22:00:00:20:37:39:ae:54 20:00:00:20:37:39:ae:54 Target Private 0x420073
0xef 20:10:00:05:30:00:4a:de 20:00:00:05:30:00:4a:de Initiator Switch 0x0000ef
Example 9-12 Displays TL Port Information for Private Devices
switch# show tlport int fc1/16 pri
fc1/16 is up, vsan 1, FCID 0x420000
------------------------------------------------------------------------
alpa pWWN nWWN SCSI Type FC-ID
------------------------------------------------------------------------
0x73 22:00:00:20:37:39:ae:54 20:00:00:20:37:39:ae:54 Target 0x420073
0x74 22:00:00:20:37:38:d3:de 20:00:00:20:37:38:d3:de Target 0x420074
Example 9-13 Displays TL Port Information for Proxied Devices
switch# show tlport int fc1/16 prox
fc1/16 is up, vsan 1, FCID 0x420000
------------------------------------------------------------------------
alpa pWWN nWWN SCSI Type FC-ID
------------------------------------------------------------------------
0x01 20:10:00:05:30:00:4a:de 20:00:00:05:30:00:4a:de Initiator 0xfffc42
0x02 21:00:00:e0:8b:01:95:e7 20:00:00:e0:8b:01:95:e7 Initiator 0x420100
TL Port Translation Guidelines
Table 9-6 lists the TL port translations supported in Cisco MDS 9000 Family switches:
Table 9-6 Supported TL Port Translation
Translation from
|
Translation to
|
|
Private initiator
|
Private target
|
From I1 to T1 or vice versa
|
Private initiator
|
Public target — N port
|
From I1 to T2 or vice versa
|
Private initiator
|
Public target — NL port
|
From I4 to T3 or vice versa
|
Public initiator — N port
|
Private target
|
From I2 to T1 or vice versa
|
Public initiator — NL port
|
Private target
|
From I3 to T1 or vice versa
|
Figure 9-3 TL Port Tranlsation Support Examples
Follow these guidelines when configuring private loops:
•
A maximum of 64 fabric devices can be proxied to a private loop.
•
To be proxied to the private loop, fabric devices must be in the same zone as private loop devices.
•
Each private device on a TL port may be included in a different zone.
•
All devices on the loop are treated as private loops. You cannot mix private and public devices on the loop if the configured port mode is TL.
•
The only FC4-type supported by TL ports is SCSI (FCP).
•
Communication between a private initiator to a private target on the same private loop does not invoke TL port services.