Configuring Interfaces on DCNM-LAN Client
Cisco NX-OS supports multiple configuration parameters for each of the interface types supported. Most of these parameters are covered in this guide but some are described in other documents.
Table 21-1 shows where to get further information on the parameters you can configure for an interface.
Table 21-1 Interface Parameters
|
|
|
Basic parameters |
description, duplex, error disable, flow control, MTU, beacon |
Configuring Basic Interface Parameters of this document |
Layer 2 |
Layer 2 access and trunk port settings |
Configuring Layer 2 Interfaces of this document |
Layer 2 MAC, VLANs, private VLANs, Rapid PVST+, Multiple Spanning Tree, Spanning Tree Extensions |
Layer 2 Switching Configuration Guide, Cisco DCNM for LAN, Release 6.xCisco Nexus 7000 Series NX-OS Layer 2 Switching Configuration Guide, Release 5.x |
Port security |
Security Configuration Guide, Cisco DCNM for LAN, Release 6.xCisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 5.x |
Layer 3 |
medium, IPv4 and IPv6 addresses |
Configuring Layer 3 Interfaces of this document |
bandwidth, delay, IP routing, VRFs |
Cisco Nexus 7000 Series NX-OS Unicast Routing Configuration Guide, Release 5.x Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide, Release 5.x |
Port Channels |
channel group, LACP |
Configuring Port Channels of this document |
vPCs |
Virtual port channels |
Configuring vPCs of this document |
Tunnels |
GRE Tunneling |
Configuring IP Tunnels of this document |
Security |
Dot1X, NAC, EOU, port security |
Security Configuration Guide, Cisco DCNM for LAN, Release 6.xCisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 5.x |
FCoE |
Beginning with Cisco NX-OS Release 5.2(1), you can run Fibre Channel over Ethernet (FCoE) on the Cisco Nexus 7000 Series Switch |
Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 |
Virtual Ethernet Interfaces |
Logical interfaces that correspond to a switch interface connected to a virtual port |
Configuring Virtual Ethernet Interfacesof this document |
Fabric Extenders |
High-density, low-cost connectivity for server aggregation |
Configuring Fabric Extenders of this document |
Port Profiles |
A mechanism for simplifying the configuration of interfaces. |
Configuring Port Profiles of this document |
This chapter includes the following topics:
For detailed information about the configuration of the interface on DCNM-LAN client, see the Interfaces Configuration Guide, Cisco DCNM for LAN, Release 7.x.
Configuring Layer 2 Interfaces
Note Beginning with Cisco Release 5.2, the Cisco Nexus 7000 Series devices support FabricPath Layer 2 interfaces. See the Cisco Nexus 7000 Series NX-OS FabricPath Command Reference for complete information about the FabricPath feature and interfaces.
This chapter in Interfaces Configuration Guide, Cisco DCNM for LAN, Release 7.x describes how to configure Layer 2 switching ports as access or trunk ports on Cisco NX-OS devices using Cisco Data Center Network Manager (DCNM).
Note The Cisco NX-OS release that is running on a managed device may not support all the features or settings described in this chapter. For the latest feature information and caveats, see the documentation and release notes for your platform and software release.
Layer 2 interfaces are used for switching packets. You can configure a Layer 2 port as an access port, which carries only one VLAN, or a trunk port, which carries many VLANs. By default, a trunk port carries all VLANs that are configured on the device, and you configure the trunk port to carry only those VLANs that you want on that port. The device uses IEEE 802.1Q to tag packets. All trunk ports must be in the same device, and trunk ports cannot carry VLANs from different devices.
You identify a native VLAN for each trunk port. The trunk port carries the traffic for that specific VLAN as untagged packets. If you do not configure a native VLAN, the device uses the default VLAN to carry untagged traffic for that trunk port. You can also configure the device to drop all untagged traffic on trunk ports and to retain the tag for the native VLAN.
Note Beginning with Cisco NX-OS Release 5.1, a Layer 2 port can function as either one of the following:
- A trunk port
- An access port
- A private VLAN port (see the Cisco DCNM Layer 2 Switching Configuration Guide, Release 5.x, for more information on private VLANs)
- A FabricPath port (see the Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide, Release 5.x, and the Cisco DCNM FabricPath Configuration Guide, Release 5.x, for information on FabricPath)
Beginning with Cisco NX-OS Release 5.2(1), a Layer 2 port can also function as a shared interface. You cannot configure an access interface as a shared interface. See the Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 for information on shared interfaces.
Note See the Cisco DCNM FabricPath Configuration Guide, Release 5.x, for more information on configuring the FabricPath feature.
Note A Layer 2 port can function as either a trunk port, an access port, or a private VLAN port.
Note See the Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Release 5.x, for information on configuring a SPAN destination interface.
Configuring Layer 3 Interfaces
This chapter in Interfaces Configuration Guide, Cisco DCNM for LAN, Release 7.x describes how to configure Layer 3 interfaces for Cisco NX-OS devices using Cisco Data Center Network Manager (DCNM).
Note The Cisco NX-OS release that is running on a managed device may not support all the features or settings described in this chapter. For the latest feature information and caveats, see the documentation and release notes for your platform and software release.
Layer 3 interfaces forward IPv4 and IPv6 packets to another device using static or dynamic routing protocols. You can use Layer 3 interfaces for IP routing and inter-VLAN routing of Layer 2 traffic. A layer 3 logical interface (VLAN network interface, loopback, tunnel) configured in one VDC is isolated from a layer 3 logical interface with the same number configured in another VDC. For example, loopback 0 in VDC 1 is independent of loopback 0 in VDC 2.
You cannot configure a shared interface as a Layer 3 interface. See the Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 for information on shared interfaces.
Beginning with Cisco Release 5.2(1), you can configure a Fabric Extender (FEX) port as a Layer 3 interface for host connectivity, but not for routing. See the Configuring the Cisco Nexus 2000 Series Fabric Extender for more information on fabric extenders.
Configuring Port Channels
This chapter in Interfaces Configuration Guide, Cisco DCNM for LAN, Release 7.x describes how to configure port channels and to apply and configure the Link Aggregation Control Protocol (LACP) for more efficient use of port channels using Cisco Data Center Network Manager (DCNM) in the Cisco NX-OS devices.
Beginning with Cisco Release NX-OS 5.1(1), you can use any of the F1 series modules or M1 series modules for the port channel, but you cannot combine member ports on an F1 module with ports on an M1 module in a single port channel. On a single switch, the port-channel compatibility parameters must be the same among all the port-channel members on the physical switch.
For more information about the Data Center Network Manager features and using the Topology tab with port channels, see the Fundamentals Configuration Guide, Cisco DCNM for LAN, Release 5.x.
Note The Cisco NX-OS release that is running on a managed device may not support all the features or settings described in this chapter. For the latest feature information and caveats, see the documentation and release notes for your platform and software release.
Note System-message logging levels for the port channels feature must meet or exceed Cisco DCNM requirements. During device discovery, Cisco DCNM detects inadequate logging levels and raises them the minimum requirements. Cisco Nexus 7000 Series Switches that run Cisco NX-OS Release 4.0 are an exception. For Cisco NX-OS Release 4.0, prior to device discovery, use the command-line interface to configure logging levels to meet or exceed Cisco DCNM requirements. For more information, see the Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Release 5.x.
Configuring vPCs
This chapter in Interfaces Configuration Guide, Cisco DCNM for LAN, Release 7.x describes how to configure virtual port channels (vPCs) using Cisco Data Center Network Manager (DCNM) on Cisco NX-OS devices.
Note Beginning with Cisco NX-OS Release 5.1(1), vPCs have been enhanced to interoperate with FabricPath. To configure vPCs with FabricPath networks, see the Cisco Nexus 7000 Series NX-OS FabricPath Configuration Guide, Release 5.x.
Note The Cisco NX-OS release that is running on a managed device may not support all the features or settings described in this chapter. For the latest feature information and caveats, see the documentation and release notes for your platform and software release.
Note System-message logging levels for the vPC feature must meet or exceed Cisco DCNM requirements. During device discovery, Cisco DCNM detects inadequate logging levels and raises them the minimum requirements. Cisco Nexus 7000 Series Switches that run Cisco NX-OS Release 4.0 are an exception. For Cisco NX-OS Release 4.0, prior to device discovery, use the command-line interface to configure logging levels to meet or exceed Cisco DCNM requirements. For more information, see the Cisco Nexus 7000 Series NX-OS System Management Configuration Guide, Release 5.x.
Beginning with Cisco NX-OS Release 5.1(1), you can use any of the 10-Gbps Ethernet (10GE) interfaces on the F series modules or the 10GE interfaces on the M series modules for the vPC peer link on an individual switch, but you cannot combine member ports on an F module with ports on an M module into a single port channel on a single switch. The port channel compatibility parameters must be the same for all the port channel members on the physical switch.
You cannot configure shared interfaces to be part of a vPC. See the Cisco NX-OS FCoE Configuration Guide for Cisco Nexus 7000 and Cisco MDS 9500 for more information on shared interfaces.
Note The port channel compatibility parameters must also be the same for all vPC member ports on both peers and therefore you must use the same type of module in each chassis.
Virtual port channels (vPCs) allow links that are physically connected to two different Cisco Nexus 7000 series devices to appear as a single port channel by a third device.
Configuring Virtual Ethernet Interfaces
This chapter in Interfaces Configuration Guide, Cisco DCNM for LAN, Release 7.x describes how to configure virtual Ethernet (vEthernet or vEth) interfaces using Cisco Data Center Network Manager (DCNM).
Virtual Ethernet (vEthernet or vEth) interfaces are logical interfaces. Each vEthernet interface corresponds to a switch interface that is connected to a virtual port. The interface types are as follows:
- Virtual Machine (VM) (interfaces connected to VM NICs)
- Service console
- VM-Fabric Extender (FEX)
- FEX-Adapter
- vmkernel
vEthernet interfaces are created on the Cisco MDS 9000 Series to represent virtual ports in use on the distributed virtual switch.
Note System-message logging levels for the Virtual Ethernet interfaces feature must meet or exceed Cisco DCNM requirements. During device discovery, Cisco DCNM detects inadequate logging levels and raises them to the minimum requirements. Cisco Nexus 7000 Series Switches that run Cisco NX-OS Release 4.0 are an exception. For Cisco NX-OS Release 4.0, prior to device discovery, use the command-line interface to configure logging levels to meet or exceed Cisco DCNM requirements. For more information, see the Fundamentals Configuration Guide, Cisco DCNM for LAN, Release 5.x .
Configuring Fabric Extenders
Note Beginning with Cisco DCNM for LAN, Release 5.2, you can configure a Fabric Extender host interface port as a routed or Layer 3 port. However, no routing protocols can be tied to this routed interface.
The Fabric Extender feature allows you to manage a Cisco Nexus 2000 Series Fabric Extender and its association with the Cisco NX-OS switch that it is attached to. A Fabric Extender is connected to the switch through physical Ethernet interfaces or a Port Channel. By default, the switch does not allow the attached Fabric Extender to connect until it has been assigned a chassis ID and is associated with the connected interface.
Note The Fabric Extender may connect to the switch through a number of separate physical Ethernet interfaces or at most one port channel interface.
This chapter in Interfaces Configuration Guide, Cisco DCNM for LAN, Release 7.x describes how to configure a Fabric Extender using Cisco Data Center Network Manager (DCNM) on a Cisco NX-OS device.
Configuring Port Profiles
This chapter in Interfaces Configuration Guide, Cisco DCNM for LAN, Release 7.x describes how to configure port profiles using Cisco Data Center Network Manager (DCNM).
A port profile is a mechanism for simplifying the configuration of interfaces. You can configure a port profile and then assign it to multiple interfaces to give them all the same configuration. Changes to the port profile are propagated to the configuration of any interface that is assigned to it.
You can configure Ethernet or vEthernet port profiles to which you can assign Ethernet or vEthernet interfaces, respectively.
Note We do not recommend that you override port profile configurations by making changes to the assigned interface configurations. Only make configuration changes to interfaces to quickly test a change or to disable a port.
Note System-message logging levels for the Port Profiles feature must meet or exceed Cisco DCNM requirements. During device discovery, Cisco DCNM detects inadequate logging levels and raises them to the minimum requirements. Cisco Nexus 7000 Series Switches that run Cisco NX-OS Release 4.0 are an exception. For Cisco NX-OS Release 4.0, prior to device discovery, use the command-line interface to configure logging levels to meet or exceed Cisco DCNM requirements. For more information, see the Fundamentals Configuration Guide, Cisco DCNM for LAN, Release 5.x .