8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
1/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000
800 553-NETS (6387)Fax: 408 527-0883
Cisco MDS 9000 Family NX-OS Interfaces
Configuration GuideCisco MDS NX-OS Release 4.2(1) Through 4.2(7)
July 2010
Text Part Number: OL-19445-02
http://www.cisco.com/http://www.cisco.com/8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
2/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public
domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF TH E USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks . Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display
output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in
illustrative content is unintentional and coincidental.
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
2009 Cisco Systems, Inc. All rights reserved.
http://www.cisco.com/go/trademarkshttp://www.cisco.com/go/trademarks8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
3/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
iii
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
C O N T E N T S
New and Changed Information xi
Preface xiii
Audience xiii
Organization xiii
Document Conventions xiv
Related Documentation xv
Release Notes xv
Regulatory Compliance and Safety Information xvCompatibility Information xv
Hardware Installation xv
Software Installation and Upgrade xv
Cisco NX-OS xvi
Cisco Fabric Manager xvi
Command-Line Interface xvi
Intelligent Storage Networking Services Configuration Guides xvi
Troubleshooting and Reference xvii
Obtaining Documentation and Submitting a Service Request xvii xvii
C HA P T E R 1 Interfaces Overview 1-1
Trunks and PortChannels 1-1
Fibre Channel Port Rate Limiting 1-2
Extended Credits 1-2
N Port Virtualization 1-2
FlexAttach 1-2
C HA P T E R 2 Configuring Interfaces 2-1
Fibre Channel Interfaces 2-1
Generation 1 Interfaces Configuration Guidelines 2-2
About Interface Modes 2-3
E Port 2-4
F Port 2-4
FL Port 2-4
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
4/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
Contents
iv
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
NP Ports 2-4
TL Port 2-5
TE Port 2-5
TF Port 2-5
TNP Port 2-6
SD Port 2-6
ST Port 2-6
Fx Port 2-6
B Port 2-6
Auto Mode 2-7
About Interface States 2-7
Administrative States 2-7
Operational States 2-7
Reason Codes 2-7
Configuring Fibre Channel Interfaces 2-11
Graceful Shutdown 2-12
Setting the Interface Administrative State 2-12
Configuring Interface Modes 2-13
Configuring System Default Port Mode F 2-13
Configuring Port Speeds 2-14
Autosensing 2-15
About Interface Descriptions 2-15
Configuring the Interface Description 2-15
Specifying a Port Owner 2-15
About Frame Encapsulation 2-16
Identifying the Beacon LEDs 2-16
About Speed LEDs 2-17
About Beacon Mode 2-17
Configuring Beacon Mode 2-17
About Bit Error Thresholds 2-18
Switch Port Attribute Default Values 2-18
About SFP Transmitter Types 2-19Displaying Interface Information 2-20
TL Ports for Private Loops 2-28
About TL Ports 2-28
About TL Port ALPA Caches 2-30
Displaying TL Port Information 2-30
Manually Inserting Entries into ALPA Cache 2-32
Displaying the ALPA Cache Contents 2-32
Clearing the ALPA Cache 2-32
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
5/204
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
6/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
Contents
vi
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Dynamic Bandwidth Management 3-7
Out-of-Service Interfaces 3-8
Combining Generation 1, Generation 2, and Generation 3 Modules 3-8
Port Indexes 3-9PortChannels 3-11
Configuring Module Interface Shared Resources 3-14
Displaying Interface Capabilities 3-14
Configuration Guidelines for 48-Port, 24-Port, and 4/44-Port 8-Gbps Fibre Channel Switching
Modules 3-15
Migrating from Shared Mode to Dedicated Mode 3-16
Migrating from Dedicated Mode to Shared Mode 3-16
Configuration Guidelines for 48-Port and 24-Port 4-Gbps Fibre Channel Switching Modules 3-17
Migrating from Shared Mode to Dedicated Mode 3-17
Migrating from Dedicated Mode to Shared Mode 3-17
Configuration Guidelines for 12-Port 4-Gbps Switching Module Interfaces 3-18
Configuration Guidelines for 4-Port 10-Gbps Switching Module Interfaces 3-18
Configuring Port Speed 3-19
Configuring Rate Mode 3-21
Configuring Oversubscription Ratio Restrictions 3-26
Disabling Restrictions on Oversubscription Ratios 3-28
Oversubscription Ratio Restrictions Example 3-29
Enabling Restrictions on Oversubscription Ratios 3-31
Configuring Bandwidth Fairness 3-31
Enabling Bandwidth Fairness 3-32
Disabling Bandwidth Fairness 3-32
Upgrade or Downgrade Scenario 3-33
Taking Interfaces Out of Service 3-33
Releasing Shared Resources in a Port Group 3-34
Disabling ACL Adjacency Sharing for System Image Downgrade 3-35
Displaying SFP Diagnostic Information 3-35
Example Configurations 3-36
Configuring a 48-Port 8-Gbps Fibre Channel Switching Module Example 3-36
Configuring a 24-Port 8-Gbps Fibre Channel Switching Module Example 3-37
Configuring a 4/44-Port 8-Gbps Fibre Channel Switching Module Example 3-37
Configuring a 24-Port 4-Gbps Fibre Channel Switching Module Example 3-38
Configuring a 48-Port 4-Gbps Fibre Channel Switching Module Example 3-39
Default Settings 3-40
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
7/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
Contents
vii
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
C HA P T E R 4 Configuring Interface Buffers 4-1
About Buffer-to-Buffer Credits 4-1
Configuring Buffer-to-Buffer Credits 4-2
About Performance Buffers 4-2
Configuring Performance Buffers 4-3
Buffer Pools 4-3
BB_Credit Buffers for Switching Modules 4-6
Configuring Buffer Credits on a Generation 2 or Generation 3 Module 4-6
48-Port 8-Gbps Fibre Channel Module BB_Credit Buffers 4-7
24-Port 8-Gbps Fibre Channel Module BB_Credit Buffers 4-8
4/44-Port 8-Gbps Host-Optimized Fibre Channel Module BB_Credit Buffers 4-9
48-Port 4-Gbps Fibre Channel Module BB_Credit Buffers 4-10
24-Port 4-Gbps Fibre Channel Module BB_Credit Buffers 4-1218-Port Fibre Channel/4-Port Gigabit Ethernet Multiservice Module BB_Credit Buffers 4-13
12-Port 4-Gbps Switching Module BB_Credit Buffers 4-13
4-Port 10-Gbps Switching Module BB_Credit Buffers 4-15
BB_Credit Buffers for Fabric Switches 4-16
Cisco MDS 9134 Fabric Switch BB_Credit Buffers 4-16
Cisco MDS 9124 Fabric Switch BB_Credit Buffers 4-16
Cisco MDS 9222i Multiservice Modular Switch BB_Credit Buffers 4-16
About Extended BB_Credits 4-17
Extended BB_credits on Generation 1 Switching Modules 4-17Extended BB_credits on Generation 2 and Generation 3 Switching Modules 4-18
Configuring Extended BB_credits 4-19
Enabling Buffer-to-Buffer State Change Number 4-19
To use the BB_SC_N field during PLOGI or FLOGI, follow these steps: 4-20
.About Receive Data Field Size 4-20
Configuring Receive Data Field Size 4-20
Displaying BB_Credit Information 4-21
C HA P T E R 5 Configuring Trunking 5-1About Trunking 5-1
Trunking E Ports 5-2
Trunking F Ports 5-2
Key Concepts 5-3
Trunking Guidelines and Restrictions 5-3
Trunking Misconfiguration Examples 5-4
Upgrade and Downgrade Restrictions 5-5
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
8/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
Contents
viii
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Difference Between TE Ports and TF-TNP Ports 5-5
Enabling the Trunking Protocols 5-7
About Trunking Protocols 5-7
Enabling the Cisco Trunking and Channeling Protocols 5-8Enabling the F Port Trunking and Channeling Protocol 5-8
Configuring Trunk Mode and VSAN List 5-8
About Trunk Modes 5-8
Configuring Trunk Mode 5-9
About Trunk-Allowed VSAN Lists and VF_IDs 5-9
Configuring an Allowed-Active List of VSANs 5-12
Example F Port Trunking Configuration 5-12
Displaying Trunking Information 5-13
Default Settings 5-14
C HA P T E R 6 Configuring PortChannels 6-1
About PortChannels 6-1
About E PortChannels 6-2
About F and TF PortChannels 6-3
About PortChanneling and Trunking 6-3
About Load Balancing 6-4
About PortChannel Modes 6-6
Configuration Guidelines and Restrictions 6-7Generation 1 PortChannel Limitations 6-7
F and TF PortChannel Restrictions 6-8
PortChannel Configuration 6-9
About PortChannel Configuration 6-10
Creating a PortChannel 6-11
Configuring the PortChannel Mode 6-11
About PortChannel Deletion 6-12
Deleting PortChannels 6-12
Interfaces in a PortChannel 6-12About Interface Addition to a PortChannel 6-13
Compatibility Check 6-13
Suspended and Isolated States 6-13
Adding an Interface to a PortChannel 6-14
Forcing an Interface Addition 6-14
About Interface Deletion from a PortChannel 6-15
Deleting an Interface from a PortChannel 6-15
PortChannel Protocols 6-15
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
9/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
Contents
ix
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
About Channel Group Creation 6-16
About Autocreation 6-18
Enabling and Configuring Autocreation 6-18
About Manually Configured Channel Groups 6-19
Converting to Manually Configured Channel Groups 6-19
Example F and TF PortChannel Configurations 6-19
Verifying the PortChannel Configuration 6-21
Default Settings 6-25
C HA P T E R 7 Configuring N Port Virtualization 7-1
About N Port Identifier Virtualization 7-1
Enabling N Port Identifier Virtualization 7-2
About N Port Virtualization 7-2
NPV Mode 7-4
NP Ports 7-5
NP Links 7-5
Internal FLOGI Parameters 7-5
Default Port Numbers 7-6
NPV CFS Distribution over IP 7-7
NPV Traffic Management 7-7
Auto 7-7
Traffic Map 7-7Disruptive 7-8
Multiple VSAN Support 7-8
NPV Guidelines and Requirements 7-8
NPV Traffic Management Guidelines 7-9
Configuring NPV 7-9
Configuring NPV Traffic Management 7-11
Configuring List of External Interfaces per Server Interface 7-11
Enabling or Disabling the Global Policy for Disruptive Load Balancing 7-11
DPVM Configuration 7-12NPV and Port Security 7-12
Verifying NPV 7-12
Verifying NPV Traffic Management 7-14
C HA P T E R 8 Configuring FlexAttach Virtual pWWN 8-1
About FlexAttach Virtual pWWN 8-1
FlexAttach Virtual pWWN Guidelines and Requirements 8-2
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
10/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
Contents
x
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Configuring FlexAttach Virtual pWWN 8-2
Enabling FlexAttach Virtual pWWN 8-2
Automatically Enabling FlexAttach Virtual pWWN 8-2
Manually Enabling FlexAttach Virtual pWWN 8-3
Mapping pWWN to Virtual pWWN 8-3
Verifying FlexAttach Virtual pWWN 8-4
Verifying the End Device 8-4
Debugging FlexAttach Virtual pWWN 8-5
Security Settings for FlexAttach Virtual pWWN 8-5
FlexAttach Virtual pWWN CFS Distribution 8-6
Difference Between San Device Virtualization and FlexAttach Port Virtualization 8-6
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
11/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
xi
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
New and Changed Information
As of Cisco MDS NX-OS Release 4.2(1), software configuration information is available in new
feature-specific configuration guides for the following information:
System management
Interfaces
Fabric
Quality of service
Security
IP services
High availability and redundancy
The information in these new guides previously existed in the Cisco MDS 9000 Family CLI
Configuration Guideand in theCisco MDS 9000 Family Fabric Manager Configuration Guide. Those
configuration guides remain available on Cisco.com and should be used for all software releases prior
to MDS NX-OS Release 4.2(1). Each guide addresses the features introduced in or available in a
particular release. Select and view the configuration guide that pertains to the software installed in yourswitch.
For a complete list of document titles, see the list of Related Documentation in the Preface.
To find additional information about Cisco MDS NX-OS Release 4.2(x), see the Cisco MDS 9000 Family
Release Notes available at the following Cisco Systems website:
http://www.cisco.com/en/US/products/ps5989/prod_release_notes_list.htm
About this Guide
The information in the new Cisco MDS 9000 NX-OS Interfaces Configuration Guidepreviously existed
in Part 3: Switch Configuration of the Cisco MDS 9000 Family CLI Configuration Guide.
Table 1lists the New and Changed features for this guide, starting with MDS NX-OS Release 4.2(1).
http://www.cisco.com/en/US/products/ps5989/prod_release_notes_list.htmlhttp://-/?-http://-/?-http://www.cisco.com/en/US/products/ps5989/prod_release_notes_list.html8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
12/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
xii
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
New and Changed Information
Table 1-1 New and Changed Features for Cisco MDS NX-OS Release 4.2(x)
Feature New and Change Topics
ChangedinRelease Where Documented
Slow Drain Device
Detection and Congestion
Avoidance
Added information about configuring stuck frame
timeout value, no-credit timeout value, credit loss
recovery threshold and action, and average credit
non-available duration threshold and action.
4.2(7) Chapter 2, Configuring
Interfaces
Port Group Monitor Added information about configuring policies
and monitoring port groups.
4.2(1) Chapter 2, Configuring
Interfaces
Port Guard Added port guard configuration guidelines for
multiple types of port failure causes.
4.2(1) Chapter 2, Configuring
Interfaces
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
13/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
xiii
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Preface
This preface describes the audience, organization, and conventions of the Cisco MDS 9000 Family
NX-OS Interfaces Configuration Guide . It also provides information on how to obtain related
documentation.
AudienceThis guide is for experienced network administrators who are responsible for configuring and
maintaining the Cisco MDS 9000 Family of multilayer directors and fabric switches.
OrganizationThe Cisco MDS 9000 Family NX-OS Interfaces Configuration Guideis organized as follows:
Chapter Title DescriptionChapter 1 Interfaces Overview Provides an overview of all the features in this
guide.
Chapter 2 Configuring Interfaces Explains Generation 1 and Generation 2
module port and operational state concepts in
Cisco MDS 9000 Family switches and provides
details on configuring ports and interfaces.
Chapter 3 Configuring Fibre Channel Interfaces Explains configuration concepts for Fibre
Channel module ports and interfaces.
Chapter 4 Configuring Interface Buffers Explains configuration concepts for Interface
Buffers.
Chapter 5 Configuring Trunking Explains TE ports and trunking concepts.
Chapter 6 Configuring Por tChannels Explains PortChannels and load balancing
concepts and provides details on configuring
PortChannels, adding ports to PortChannels,
and deleting ports from PortChannels.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
14/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
xiv
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Preface
Document ConventionsCommand descriptions use these conventions:
Screen examples use these conventions:
This document uses the following conventions:
Note Means readertake note. Notes contain helpful suggestions or references to material not covered in the
manual.
Caution Means reader be careful. In this si tuation, you might do something that could result in equipment
damage or loss of data.
Chapter 7 Configuring N Port Virtual ization Provides an overview of N Port Virtualization
and includes quidelines and requirements for
configuring and verifying NPV.
Chapter 8 Configuring FlexAttach VirtualpWWN
FlexAttach virtual pWWN feature facilitatesserver and configuration management. In a
SAN environment, the server installation or
replacement, requires interaction and
coordination among the SAN and server
administrators.
Chapter Title Description
boldface font Commands and keywords are in boldface.
italic font Arguments for which you supply values are in italics.
[ ] Elements in square brackets are optional.
[ x | y | z ] Optional alternative keywords are grouped in brackets and separated by
vertical bars.
screen font Terminal sessions and information the switch displays are in screen font.
boldface screen font Information you must enter is in boldface screen font.
italic screen font Arguments for which you supply values are in italic screen font.
< > Nonprinting characters, such as passwords, are in angle brackets.
[ ] Default responses to system prompts are in square brackets.
!, # An exclamation point (!) or a pound sign (#) at the beginning of a line of code
indicates a comment line.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
15/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
xv
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Preface
Related DocumentationThe documentation set for the Cisco MDS 9000 Family includes the following documents. To find a
document online, use the Cisco MDS NX-OS Documentation Locator at:
http://www.cisco.com/en/US/docs/storage/san_switches/mds9000/roadmaps/doclocater.htm
Release Notes
Cisco MDS 9000 Family Release Notes for Cisco MDS NX-OS Releases
Cisco MDS 9000 Family Release Notes for MDS SAN-OS Releases
Cisco MDS 9000 Family Release Notes for Storage Services Interface Images
Cisco MDS 9000 Family Release Notes for Cisco MDS 9000 EPLD Images
Release Notes for Cisco MDS 9000 Family Fabric Manager
Regulatory Compliance and Safety Information
Regulatory Compliance and Safety Information for the Cisco MDS 9000 Family
Compatibility Information
Cisco Data Center Interoperability Support Matrix
Cisco MDS 9000 NX-OS Hardware and Software Compatibility Information and Feature Lists
Cisco MDS NX-OS Release Compatibility Matrix for Storage Service Interface Images
Cisco MDS 9000Family Switch-to-Switch Interoperability Configuration Guide
Cisco MDS NX-OS Release Compatibility Matrix for IBM SAN Volume Controller Software for
Cisco MDS 9000
Cisco MDS SAN-OS Release Compatibility Matrix for VERITAS Storage Foundation for Networks
Software
Hardware Installation
Cisco MDS 9500 Series Hardware Installation Guide
Cisco MDS 9200 Series Hardware Installation Guide
Cisco MDS 9100 Series Hardware Installation Guide
Cisco MDS 9124 and Cisco MDS 9134 Multilayer Fabric Switch Quick Start Guide
Software Installation and Upgrade
Cisco MDS 9000 NX-OS Release 4.1(x) and SAN-OS 3(x) Software Upgrade and Downgrade Guide
Cisco MDS 9000 Family Storage Services Interface Image Install and Upgrade Guide
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
16/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
xvi
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Preface
Cisco MDS 9000 Family Storage Services Module Software Installation and Upgrade Guide
Cisco NX-OS
Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide
Cisco MDS 9000 Family NX-OS Licensing Guide
Cisco MDS 9000 Family NX-OS System Management Configuration Guide
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
Cisco MDS 9000 Family NX-OS Fabric Configuration Guide
Cisco MDS 9000 Family NX-OS Quality of Service Configuration Guide
Cisco MDS 9000 Family NX-OS Security Configuration Guide
Cisco MDS 9000 Family NX-OS IP Services Configuration Guide
Cisco MDS 9000 Family NX-OS Intelligent Storage Services Configuration Guide
Cisco MDS 9000 Family NX-OS High Availability and Redundancy Configuration Guide
Cisco MDS 9000 Family NX-OS Inter-VSAN Routing Configuration Guide
Cisco Fabric Manager
Cisco Fabric Manager Fundamentals Configuration Guide
Cisco Fabric Manager System Management Configuration Guide
Cisco Fabric Manager Interfaces Configuration Guide
Cisco Fabric Manager Fabric Configuration Guide
Cisco Fabric Manager Quality of Service Configuration Guide
Cisco Fabric Manager Security Configuration Guide
Cisco Fabric Manager IP Services Configuration Guide
Cisco Fabric Manager Intelligent Storage Services Configuration Guide
Cisco Fabric Manager High Availability and Redundancy Configuration Guide
Cisco Fabric Manager Inter-VSAN Routing Configuration Guide
Cisco Fabric Manager Online Help
Cisco Fabric Manager Web Services Online Help
Command-Line Interface
Cisco MDS 9000 FamilyCommand Reference
Intelligent Storage Networking Services Configuration Guides
Cisco MDS 9000 Family I/O Accelerator Configuration Guide
Cisco MDS 9000 Family SANTap Deployment Guide
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
17/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
xvii
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Preface
Cisco MDS 9000 Family Data Mobility Manager Configuration Guide
Cisco MDS 9000 Family Storage Media Encryption Configuration Guide
Cisco MDS 9000 Family Secure Erase Configuration Guide
Cisco MDS 9000 Family Cookbook for Cisco MDS SAN-OS
Troubleshooting and Reference
Cisco NX-OS System Messages Reference
Cisco MDS 9000 Family NX-OS Troubleshooting Guide
Cisco MDS 9000 Family NX-OS MIB Quick Reference
Cisco MDS 9000 Family NX-OS SMI-S Programming Reference
Cisco MDS 9000 Family Fabric Manager Server Database Schema
Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly Whats New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the Whats New in Cisco Product Documentation as an RSS feed and set content to be
delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently
supports RSS Version 2.0.
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.htmlhttp://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
18/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
xviii
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Preface
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
19/204
C H A P T E R
Send documentat ion comments to mdsfeedback -doc@c isco .com
1-1
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
1Interfaces Overview
This chapter describes the basic interfaces that are used with Fabric Manager. These interfaces include
Gigabit Ethernet interfaces, Fiber Channel interfaces, virtual interfaces on Nexus hardware, buffer
credits, management interfaces, VSAN interfaces, shared interface resources, trunking, PortChanneling,
N port virtualization (NPV), and FlexAttach virtual pWWN.
This chapter includes the following topics:
Trunks and PortChannels, page 1-1
Fibre Channel Port Rate Limiting, page 1-2
Extended Credits, page 1-2
N Port Virtualization, page 1-2
FlexAttach, page 1-2
Trunks and PortChannelsTrunking, also known as VSAN t runking, is a feature specific to switches in the Cisco MDS 9000
Family. Trunking enables interconnect ports to transmit and receive frames in more than one VSAN, over
the same physical link. Trunking is supported on E ports and F ports.
PortChannels aggregate multiple physical ISLs into one logical link with higher bandwidth and port
resiliency for both Fibre Channel and FICON traffic. With this feature, up to 16 expansion ports
(E-ports) or trunking E-ports (TE-ports) can be bundled into a PortChannel. ISL ports can reside on any
switching module, and they do not need a designated master port. If a port or a switching module fails,
the PortChannel continues to function properly wi thout requiring fabric reconfiguration.
Cisco NX-OS software uses a protocol to exchange PortChannel configuration information between
adjacent switches to simplify PortChannel management, including misconfiguration detection and
autocreation of PortChannels among compatible ISLs. In the autoconfigure mode, ISLs with compatible
parameters automatically form channel groups; no manual intervention is required.
PortChannels load balance Fibre Channel traffic using a hash of source FC-ID and destination FC-ID,
and optionally the exchange ID. Load balancing using PortChannels is performed over both Fibre
Channel and FCIP links. Cisco NX-OS software also can be configured to load balance across multiple
same-cost FSPF routes.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
20/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
1-2
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 1 Interfaces Overview
Fibre Channel Port Rate Limiting
Fibre Channel Port Rate LimitingThe Fibre Channel port rate-limiting feature for the Cisco MDS 9100 Series controls the amount of
bandwidth available to individual Fibre Channel ports within groups of four host-optimized ports.
Limiting bandwidth on one or more Fibre Channel ports allows the other ports in the group to receive a
greater share of the available bandwidth under high-utilization conditions. Port rate limiting is also
beneficial for throttling WAN traffic at the source to help eliminate excessive buffering in Fibre Channel
and IP data network devices.
Extended CreditsFull line-rate Fibre Channel ports provide at least 255 buffer credits standard. Adding credits lengthens
distances for Fibre Channel SAN extension. Using extended credits, up to 4095 buffer credits from a
pool of more than 6000 buffer credits for a module can be allocated to ports as needed to greatly extend
the distance for Fibre Channel SANs.
N Port VirtualizationCisco NX-OS software supports industry-standard N port identifier virtualization (NPIV), which allows
multiple N port fabric logins concurrently on a single physical Fibre Channel link. HBAs that support
NPIV can help improve SAN security by enabling zoning and port security to be configured
independently for each virtual machine (OS partition) on a host. In addition to being useful for server
connections, NPIV is beneficial for connectivity between core and edge SAN switches.
N port virtualizer (NPV) is a complementary feature that reduces the number of Fibre Channel domain
IDs in core-edge SANs. Cisco MDS 9000 family fabric switches operating in the NPV mode do not join
a fabric; they only pass traffic between core switch links and end devices, which eliminates the domain
IDs for these switches. NPIV is used by edge switches in the NPV mode to log in to multiple end devices
that share a link to the core switch. This feature is available only for Cisco MDS Blade Switch Series,
the Cisco MDS 9124 Multilayer Fabric Switch, and the Cisco MDS 9134 Multilayer Fabric Switch.
FlexAttachCisco NX-OS supports the FlexAttach feature. One of the main problems in a SAN environment is the
time and effort required to install and replace servers. The process involves both SAN and server
administrators, and the interaction and coordination between them can make the process time
consuming. To alleviate the need for interaction between SAN and server administrators, the SAN
configuration should not be changed when a new server is installed or an existing server is replaced.
FlexAttach addresses these problems, reducing configuration changes and the time and coordination
required by SAN and server administrators when installing and replacing servers. This feature is
available only for Cisco MDS 9000 Blade Switch Series, the Cisco MDS 9124, and the Cisco MDS 9134
when NPV mode is enabled.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
21/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
1-3
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 1 Interfaces Overview
FlexAttach
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
22/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
1-4
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 1 Interfaces Overview
FlexAttach
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
23/204
C H A P T E R
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-1
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
2Configuring 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 chapter describes the basic interface configuration to get your switch up and running. It includes
the following sections:
Fibre Channel Interfaces, page 2-1
TL Ports for Private Loops, page 2-28
Configuring Port Guard, page 2-32
Configuring Port Monitor, page 2-34
Configuring Port Group Monitor, page 2-40
Configuring Slow Drain Device Detection and Congestion Avoidance, page 2-44
Management Interfaces, page 2-47
VSAN Interfaces, page 2-49
Default Settings, page 2-50
For more information on configuring mgmt0 interfaces, refer to the Cisco MDS 9000 Family NX-OS
Fundamentals Configuration Guideand Cisco MDS 9000 Family NX-OS IP Services Configuration
Guide.
See the Cisco MDS 9000 Family NX-OS IP Services Configuration Guidefor more information on
configuring Gigabit Ethernet interfaces.
Tip 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, enter the show modulecommand in EXEC mode
(for information about verifying the module status, refer to the Cisco NX-OS Fundamentals
Configuration Guide).
Fibre Channel InterfacesThis section describes Fibre Channel interface characteristics, including (but not limited to) modes,
frame encapsulation, states, SFPs, and speeds.
This section includes the following topics:
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
24/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-2
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
Generation 1 Interfaces Configuration Guidelines, page 2-2
About Interface Modes, page 2-3
About Interface States, page 2-7
Configuring Fibre Channel Interfaces, page 2-11
Graceful Shutdown, page 2-12
Configuring Interface Modes, page 2-13
Configuring Port Speeds, page 2-14
About Interface Descriptions, page 2-15
Configuring the Interface Description, page 2-15
Specifying a Port Owner, page 2-15
About Frame Encapsulation, page 2-16
Identifying the Beacon LEDs, page 2-16
About Beacon Mode, page 2-17
About Bit Error Thresholds, page 2-18
Switch Port Attribute Default Values, page 2-18
About SFP Transmitter Types, page 2-19
Displaying Interface Information, page 2-20
Generation 1 Interfaces Configuration Guidelines
The Generation 1 interfaces configuration guidelines apply to the following hardware:
The 32-port, 2-Gbps or 1-Gbps switching module interfaces.
The Cisco MDS 9140 and 9120 switch interfaces.
Note Due to the hardware design of the MDS 9134 switch, we do not support interface
out-of-service action on either of its two 10-Gigabit ports. This is because no internal port
hardware resource is released when an out-of-service action is performed on these
10-Gigabit ports.
When configuring these host-optimized ports, the following port mode 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 remainshutdown.
If you execute the write erasecommand on a 32-port switching module, and then copy a saved
configuration to the switch from a text file that contains the no system default switchport
shutdowncommand, you need to copy the text file to the switch again for the E ports to come up
without manual configuration.
If any of the other three ports are enabled, you cannot configure the first port as an E port. The other
three ports continue to remain enabled.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
25/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-3
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
The auto mode is not a llowed in a 32-port switching module or the host-optimized ports in the Cisco
9100 Series (16 host-optimized ports in the Cisco MDS 9120 switch and 32 host-optimized ports in
the Cisco MDS 9140 switch).
The default port mode is Fx (Fx negotiates to F or FL) for 32-port switching modules.
The 32-port switching module does not support FICON.
Note We recommend that you configure your E ports on a 16-port switching module. If you must configure
an E port on a 32-port host-optimized switching module, the other three ports in that 4-port group cannot
be used.
Note In the Cisco MDS 9100 Series, the groups of ports that are located on the left and outlined in white are
full line rate. The other ports are host-optimized. Each group of 4 host-optimized ports have the same
features as for the 32-port switching module.
About 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, S T p o r t , a n d 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:
N port
F port
Publicloop
loop
E port E portFL port
NL port NL port
NL port NL port
p
TL port
ISL link
79528
Private
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
26/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-4
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
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).
Note We recommend that you configure E ports on 16-port modules. If you must configure an E port on a
32-port oversubscribed module, then you can only use the first port in a group of four ports (for example,
ports 1 through 4, 5 through 8, and so forth). The other three ports cannot be used.
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.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
27/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-5
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
For more details about NP ports and NPV, see Chapter 7, Configuring N Port Virtualization.
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 pr ivate loop devices (NL ports). TL ports are 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
TL ports support class 2 and class 3 services.
Private loop devices refer to legacy devices that reside on arbitrated loops. These devices are not aware
of a switch fabric because they only communicate with devices on the same physical loop (see the
About TL Port ALPA Caches section on page 2-30).
Tip We recommend configuring devices attached to TL ports in zones that have up to 64 zone members.
Note TL port mode is not supported on Generation 2 switching module interfaces.
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 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 t runking 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.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
28/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-6
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
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 modefor 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).
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
29/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-7
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
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. Ifthe 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.
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 2-1.
Operational States
The operational state indicates the current operational state of the interface as described in Table 2-2.
Reason Codes
Reason codes are dependent on the operational state of the interface as described in Table 2-3.
Table 2-1 Administrative States
Administrative State Description
Up Interface is enabled.
Down Interface is disabled. If you adminis tratively disable an interface by shuttingdown that interface, the physical link layer state change is ignored.
Table 2-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, andthe interface initialization must be completed.
Down Interface cannot transmit or receive (data) traffic.
Trunking Interface is operational in TE or TF mode.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
30/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-8
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
Note Only some of the reason codes are listed in Table 2-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 2-4.
Table 2-3 Reason Codes for Interface States
AdministrativeConfiguration
OperationalStatus Reason Code
Up Up None.Down Down Administratively downIf you administratively configure an interface
as down, you disable the interface. No traffic is received or transmitted.
Up Down See Table 2-4.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
31/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-9
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
Table 2-4 Reason Codes for Nonoperational States
Reason Code (long version) DescriptionApplicableModes
Link failure or not connected The physical layer link is not operational. AllSFP 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.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
32/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-10
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
Isolation due to ELP failure The port negotiation failed. Only E ports
and TE portsIsolation 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
interfacesSuspended 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.
Table 2-4 Reason Codes for Nonoperational States (continued)
Reason Code (long version) DescriptionApplicableModes
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
33/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-11
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
Configuring Fibre Channel Interfaces
To configure a Fibre Channel interface, follow these steps:
To configure a range of interfaces, follow these steps:
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.
Command Purpose
Step 1 switch# config t Enters configuration mode.
Step 2 switch(config)# interface fc1/1switch(config-if)#
Selects a Fibre Channel interface and enters interface
configuration submode.
Note When a Fibre Channel interface is configured, it is
automatically assigned a unique world wide name
(WWN). If the interfaces operational state is up, it is
also assigned a Fibre Channel ID (FC ID).
Command Purpose
Step 1 switch# config t Enters configuration mode.
Step 2 switch(config)# interface fc1/1 - 4 , fc2/1 - 3switch(config-if)#
Selects the range of Fibre Channel interfaces
and enters interface configuration submode3.
Note In this command, provide a space
before and after the comma.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
34/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-12
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
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.
Setting the Interface Administrative State
To gracefully shut down an interface, follow these steps:
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)# shutdown Gracefully shuts down the interface and administratively
disables traffic flow (default).
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 noprefix is used (provided the operational state is up).
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
35/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-13
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
Configuring Interface Modes
To configure the interface mode, follow these steps:
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 eraseorreload. 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.
Example 2-1shows the command in the setup utility, and Example 2-2shows the command from the
command line.
Example 2-1 Setup Utility
Configure default switchport mode F (yes/no) [n]:y
Example 2-2 Command Line
switch(config)# system default switchport mode F
Command Purpose
Step 1 switch# config t Enters configuration mode.
Step 2 switch(config)# interfacefc1/1switch(config-if)#
Selects a Fibre Channel interface and enters interface
configuration submode.
Step 3 switch(config-if)# switchport mode Fswitch(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 autoswitch(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.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
36/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-14
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
Note 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.
Note When the command is executed from the command line, switch operation remains graceful. No ports are
flapped.
To set the administrative mode of Fibre Channel ports to mode F in the CLI, follow these steps:
Note For detailed information about the switch setup utility see the Cisco MDS 9000 Family NX-OS
Fundamentals Configuration Guide.
Configuring Port Speeds
By default, the port administrative speed for an interface is automatically calculated by the switch.
Caution Changing the port administrative speed is a disruptive operation.
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)# system defaultswitchport mode F
Sets the administrative mode of Fibre Channel ports to
mode F (if applicable).
switch(config)# no system default
switchport mode FSets the administrative mode of Fibre Channel ports to
the default (unless user configured).
Command Purpose
Step 1 switch# config t Enters configuration mode.
Step 2 switch(config)# interface fc 1/1 Selects the mgmt0 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). You can set the speed to 1000(for
1-Gbps interfaces), 2000(for 2-Gbps interfaces),
4000(for 4-Gbps interfaces), 8000(for 8-Gbps
interfaces), or auto(default).
switch(config-if)# no switchport speed Reverts the factory default (auto) administrative
speed of the interface.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
37/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-15
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
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.
About Interface Descriptions
Interface descriptions enable you to identify the traffic or the use for that interface. The interface
description can be any alphanumeric string.
Configuring the Interface Description
To configure a description for an interface, follow these steps:
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.
Command Purpose
Step 1 switch# config t Enters configuration mode.
Step 2 switch(config)# interfacefc1/1switch(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 80characters long.
switch(config-if)# no switchport description Clears the description of the interface.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
38/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-16
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
To specify or remove the port owner, follow these steps:
Note The port guard and port owner features are available for all ports regardless of the operational mode.
To display the owner description specified for a port, use the following commands:
switch# show running interface fcmodule-number/interface-number
switch# show port internal info interface fcmodule-number/interface-number
About Frame Encapsulation
The switchport encap eislcommand 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 eislcommand 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_interfacecommand output (see the Cisco MDS 9000 Family NX-OS System Management
Configuration Guide).
Identifying the Beacon LEDs
Figure 2-2displays the status, link, and speed LEDs in a 16-port switching module.
Figure 2-2 Cisco MDS 9000 Family Switch Interface Modes
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 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.
1 Status LED1
1. Se e th e Cisco MDS 9000 Family NX-OS Fundamentals Configuration Guide.
3 Link LEDs1and speed LEDs2
2 1/2-Gbps Fibre Channel port group3 4 Asset tag4
77686
2
1 43
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
39/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-17
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
About Speed LEDsEach 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:
OffThe 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 greenBeacon mode is disabled.
Flashing greenThe beacon mode is enabled. The LED flashes at one-second intervals.
Note Generation 2 and Generation 3 modules and fabric switches do not have speed LEDs.
About 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.
Configuring Beacon ModeTo enable beacon mode for a specified interface or range of interfaces, follow these steps:
Note 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.
2. See the About Speed LEDs section on page 2-17.
3. See the Generation 1 Interfaces Configuration Guidelines section on page 2-2.
4. Refer to the Cisco MDS 9000 Family hardware installation guide for your platform.
Command Purpose
Step 1 switch# config tswitch(config)#
Enters configuration mode.
Step 2 switch(config)# interfacefc1/1switch(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)# noswitchport beacon Disables the beacon mode for the interface.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
40/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-18
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
About 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, theswitch disables the interface when the threshold is reached. You can enter a shutdown andno shutdown
command sequence to reenable the interface.
You can configure the switch to not disable an interface when the threshold is crossed. By default, the
threshold disables the interface.
To disable the bit error threshold for an interface, follow these steps:
Note Regardless of the setting of the switchport ignore bit-errorscommand, the switch generates a syslog
message when bit-error threshold events are detected.
Switch Port Attribute Default ValuesYou 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.
Command Purpose
Step 1 switch# config t Enters configuration mode.
Step 2 switch(config)# interfacefc1/1switch(config-if)#
Selects a Fibre Channel interface and enters
interface configuration submode.
Step 3 switch(config-if)# switchport ignorebit-errors
Prevents the detection of bit error threshold
events from disabling the interface.
switch(config-if)# no switchport ignorebit-errors
Prevents the detection of bit error threshold
events from enabling the interface.
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
41/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-19
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
To configure switch port attributes, follow these steps:
About SFP Transmitter Types
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 interfaceand show interface briefcommands display the ID instead of the transmitter
type. The show interface transceivercommand and the show interface fcs lot/porttransceiver
command display both values for Cisco-supported SFPs. Table 2-5defines the acronyms used in the
command output (see the Displaying Interface Information section on page 2-20).
Command Purpose
Step 1 switch# config t Enters configuration mode.
Step 2 switch(config)# no system default
switchport shutdownswitch(config)#
Configures the default setting for administrative state of an
interface as Up. (The factory default setting is Down).
Tip This command is applicable only to interfaces for
which no user configuration exists for the
administrative state.
switch(config)# system default
switchport shutdownswitch(config)#
Configures the default setting for administrative state of an
interface as Down. This is the factory default setting.
Tip This command is applicable only to interfaces for
which no user configuration exists for the
administrative state.
switch(config)# system defaultswitchport trunk mode auto
switch(config)#
Configures the default setting for administrative trunk mode
state of an interface as Auto.
Note The default setting is trunk mode on.
Table 2-5 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
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
42/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-20
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
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 al l the configured
interfaces in the switch. See Examples 2-3to 2-10.
Example 2-3 Displays All Interfaces
switch# show interfacefc1/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.
. . .
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
43/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-21
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
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:
interfacefc1/1-5,fc2/5-7
Note The spaces are required before and after the dash ( -) and before and after the comma (,).
Example 2-4 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
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
44/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-22
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
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-5 Displays a Specific Interface
switch# show interface fc2/2fc2/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
8/11/2019 Cisco MDS 9000 NX-OS Interface Config Guide
45/204
Send documentat ion comments to mdsfeedback -doc@c isco .com
2-23
Cisco MDS 9000 Family NX-OS Interfaces Configuration Guide
OL-19445-02, Cisco MDS NX-OS Release 4.2(x)
Chapter 2 Configuring Interfaces
Fibre Channel Interfaces
3 transmit B2B credit remaining.
Example 2-6 Displays Port Description
switch# show interface description-------------------------------------------------------------------------------
Interface Description-------------------------------------------------------------------------------
fc3/1 test intestfc3/2 --fc3/3 --fc3/4 TE portfc3/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-7 Displays Interface Information in a Brief Format
switch# show interface b