Cisco systems atm switch installation guide (10 pages)
Summary of Contents for Cisco Nexus 1000V
Page 1
Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x First Published: August 22, 2014 Last Modified: November 05, 2015 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)
Page 2
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/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.
Specifying an Interface to Configure Configuring a Description Configuring the Interface Speed and Duplex Modes Configuring the MTU Size for an Ethernet Interface Shutting Down and Activating an Interface Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 4
Configuring a vEthernet Access Interface Configuring a Private VLAN on a vEthernet Interface Enabling or Disabling a vEthernet Interface Verifying the vEthernet Interface Configuration Monitoring the vEthernet Interface Configuration Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 5
Pinning a Control or Packet VLAN to a Subgroup Migrating a Channel Group to a Port Profile Migrating Port Profile Types in a Port Profile Configuring Network State Tracking for vPC-HM Configuring Static Pinning for an Interface Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 6
Feature History for Port Channels Supported RFCs A P P E N D I X A Supported RFCs Interface Configuration Limits A P P E N D I X B Interface Configuration Limits Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
New and Changed Information This section lists new and changed content in this document by software release. To find additional information about new features or command changes, see the Cisco Nexus 1000V Release Notes and Cisco Nexus 1000V Command Reference.
Page 8
New and Changed Information New and Changed Information Table 1: New and Changed Features for the Cisco Nexus 1000V Interface Configuration Guide Feature Description Changed in Release Where Documented Port channel vPC-HM The interface 4.2(1)SV2(1.1) Configuring Port Channels, level on page 45...
Page 9
Mapping vEthernet interfaces vEthernet 4.2(1)SV1(4) Configuring Virtual Ethernet to connected ports interfaces are Interfaces, on page 35 now mapped to connected ports by addresses as well as the DVPort number. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 10
Configuration limits Configuration 4.0(4)SV1(2) Interface Configuration limits for Limits, on page 89 vEthernet interfaces, vEthernet trunks, and port profiles were added. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 11
45 creation of subgroups. Static Pinning Support for 4.0(4)SV1(2) Configuring Port Channels, attaching (or on page 45 pinning) a vEthernet interface to a specific port channel subgroup. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 12
New and Changed Information New and Changed Information Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
High Availability for Interfaces, page 9 Information About Interfaces Ethernet Interfaces All interfaces on the Cisco Nexus 1000V are Layer 2 Ethernet interfaces, which include access ports, trunk ports, private VLAN ports, and promiscuous ports. Access Ports An access port carries traffic for one VLAN. This type of port is a Layer 2 interface only.
• VM (interfaces connected to VM NICs) • Service console • vmkernel vEthernet interfaces are created on the Cisco Nexus 1000V to represent virtual ports in use on the distributed virtual switch. Management Interface You can use the management Ethernet interface to connect the device to a network for remote management using a Telnet client, the Simple Network Management Protocol (SNMP), or other management agents.
High Availability for Interfaces Interfaces support stateful and stateless restarts. A stateful restart occurs during a supervisor switchover. After the switchover, the Cisco Nexus 1000V applies the run-time configuration. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 16
Overview High Availability for Interfaces Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
If you change the settings, be sure to use the same speed and duplex mode settings on both interfaces or use autonegotiation for at least one of the interfaces. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Cisco Discovery Protocol The Cisco Discovery Protocol (CDP) is a Layer 2 protocol that enables two devices that run CDP to learn about each other. You can use CDP to troubleshoot the network by displaying information about the neighboring devices that are linked through each interface.
Adds a description of up to 80 alphanumeric characters for the interface and saves it in the running configuration. Step 4 switch(config-if)# show interface (Optional) interface Displays the interface status, which includes the description. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
• Know that Jumbo frames are supported only on the vmxnet3 driver. Attempts to change the MTU appear to succeed but the adapter always drops frames larger than 1500 bytes. For more information, see the VMware KB article http://kb.vmware.com/selfservice/microsites/search.do?language=en_ US&cmd=displayKC&externalId=1015556 Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Enabling or Disabling CDP You can enable or disable the Cisco Discovery Protocol (CDP) for Ethernet and management interfaces. Before You Begin • Log in to the CLI in EXEC mode. • Make sure that CDP is enabled at both ends of the link.
Clearing the Interface Counters You can clear the Ethernet, vEthernet, and management interface counters. Before You Begin Log in to the CLI in EXEC mode, configuration mode, or interface configuration mode. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Displays the status of Layer 2 ports. Feature History for Basic Interface Parameters Feature Name Releases Feature Information System jumbo MTU 4.2(1)SV1(4) The system jumbo MTU is fixed at 9000 and cannot be changed. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 27
Feature Name Releases Feature Information Interface MTU 4.2(1)SV1(4) The interface MTU can be configured as a value between 1500 and 9000. Basic interface parameters 4.0(4)SV1(1) This feature was introduced. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 28
Configuring Interface Parameters Feature History for Basic Interface Parameters Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
For information about configuring a Switched Port Analyzer (SPAN) destination interface, see the Cisco Note Nexus 1000V System Management Configuration Guide. For information about VLANs, MAC address tables, and private VLANs, see the Cisco Nexus 1000V Note Layer 2 Switching Configuration Guide.
• A trunk port can have two or more VLANs configured on that port; it can carry traffic for several VLANs simultaneously. By default, all ports on the Cisco Nexus 1000V are Layer 2 ports. You can change the default port mode (access or trunk). See the Cisco Nexus 1000V Installation and Upgrade Guide for information about setting the default port mode.
• Do not connect devices with access links because access links may partition a VLAN. • When connecting Cisco switches through an 802.1Q trunk, make sure that the native VLAN for an 802.1Q trunk is the same on both ends of the trunk link. If the native VLAN on one end of the trunk is different from the native VLAN on the other end, spanning tree loops might result.
VLAN that does not exist. • Know that the Cisco Nexus 1000V commands may differ from the Cisco IOS commands. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Before You Begin • Before you configure a trunk port, ensure that you are configuring a Layer 2 interface. • Know that the interface can be either Ethernet or vEthernet. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
VLANs. See IEEE 802.1Q Encapsulation, on page 24 for more information. • The device supports 802.1Q encapsulation only. • Know that the Cisco Nexus 1000V commands may differ from the Cisco IOS commands. Procedure Command or Action Purpose...
Configuring Layer 2 Interfaces Configuring the Allowed VLANs for Trunking Ports Before You Begin Be aware that the Cisco Nexus 1000V commands may differ from the Cisco IOS commands. Procedure Command or Action Purpose Step 1 switch# configure terminal Enters global configuration mode.
When working with 802.1Q trunked interfaces, you can maintain the tagging for all packets that enter with a tag that matches the native VLAN ID. Untagged traffic is dropped (you will still carry control traffic on that interface). Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
• Know that this feature applies to the entire device; you cannot apply it to selected VLANs on a device. • Know that the Cisco Nexus 1000V commands may differ from the Cisco IOS commands. If you enable 802.1Q tagging on one device and disable it on another device, all traffic is dropped on the Note device with this feature disabled.
This example shows how to configure a Layer 2 access interface and assign the access VLAN for that interface: switch# configure terminal switch(config)# interface ethernet 2/30 switch(config-if)# switchport switch(config-if)# switchport mode access Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Feature History for Layer 2 Interface Parameters Feature Name Releases Feature Information Layer 2 interface parameters 4.0(4)SV1(1) This feature was introduced. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 40
Configuring Layer 2 Interfaces Feature History for Layer 2 Interface Parameters Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
• Service console • vmkernel vEthernet interfaces are created on the Cisco Nexus 1000V to represent virtual ports in use on the distributed virtual switch. vEthernet interfaces are mapped to connected ports by MAC address as well as DVPort number. When a server administrator changes the port profile assignment on a vNIC or hypervisor port, the same vEthernet interface is reused.
You can enable or disable the following automatic controls for vEthernet interfaces: • Deleting unused vEthernet interfaces • Purging of manual vEthernet configurations • Creating vEthernet interfaces Before You Begin Log in to the CLI in EXEC mode. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Displays the specified interface for verification. Step 7 switch(config-if)# copy (Optional) running-config startup-config Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Displays the interface status and information. Step 8 switch(config-if)# copy (Optional) running-config startup-config Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Enables or disables the vEthernet interface in the running configuration: • shutdown: Disables the vEthernet interface. • no shutdown: Enables the vEthernet interface. Step 4 switch(config-if)# show interface (Optional) Displays the interface status and information. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 48
Example: show interface virtual port-mapping This example shows how to display the virtual port mapping for all vEthernet interfaces: switch# show interface virtual port-mapping ------------------------------------------------------------------------------- Port Hypervisor Port Binding Type Status Reason Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
You can enable or disable the following automatic vEthernet interface controls: • Deleting unused vEthernet interfaces • Purging of manual vEthernet configurations • Creating vEthernet interfaces vEthernet interface parameters 4.0(4)SV1(1) This feature was introduced Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Verifying the Port Channel Configuration, page 82 • Monitoring Port Channels, page 83 • Configuration Examples for Port Channels, page 84 • Feature History for Port Channels, page 84 Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Layer 2 configuration of the first interface. You can also create the port channel first. In this instance, the Cisco Nexus 1000V creates an empty channel group with the same channel number as the port channel and takes the default Layer 2 configuration, as well as the compatibility configuration.
Page 53
• MTU size • SPAN—Cannot be a SPAN source or a destination port To view the full list of compatibility checks performed by the Cisco Nexus 1000V, use the show port-channel compatibility-parameters. You can only add interfaces configured with the channel mode set to on to static port channels. You can configure these attributes on an individual member port.
Load Balancing Using Port Channels The Cisco Nexus 1000V load balances traffic across all operational interfaces in a port channel by hashing the addresses in the frame to a numerical value that selects one of the links in the channel. Port channels provide load balancing by default.
A maximum of eight interfaces can be active, and a maximum of eight interfaces can be placed in a standby state. The following figure shows how individual links can be combined into LACP port channels and channel groups as well as function as individual links. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
• When you delete the port channel, the associated channel group is automatically deleted. All member Note interfaces revert to their original configuration. • LACP port channels on Cisco virtual interface cards do not support more than two vNICs. Figure 4: Individual Links Combined into a Port Channel VEM Management of LACP...
• A port in on mode is not running LACP and cannot form a port channel with another port that is in active or passive mode. LACP ID Parameters This section describes the LACP parameters. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
The software supports only Marker Responders. LACP-Enabled and Static Port Channels Differences The following table summarizes the major differences between port channels with LACP enabled and static port channels. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
You use vPC-HM mode to create a port channel when the switch is connected to multiple upstream switches that are not clustered. In the Cisco Nexus 1000V, the port channel is divided into subgroups or logical smaller port channels, each representing one or more uplinks to one upstream physical switch.
Figure 5: Using vPC-HM to Connect a Port Channel to Multiple Upstream Switches Subgroup Creation If Cisco Discovery Protocol (CDP) is enabled on the upstream switches, subgroups are automatically created using information gathered from the CDP packets. If not, you must manually create subgroups.
In the case of a failure, the Cisco Nexus 1000V first sends a gratuitous ARP packet to the upstream switch indicating that the VEM MAC address will now be learned on a different link. It also allows for subsecond failover time.
In split mode, the interfaces are marked as inactive, and traffic is pinned to active interfaces. System messages indicate when a port channel enters or recovers from split mode; and interfaces are marked active or inactive. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Guidelines and Limitations Port channeling has the following guidelines and restrictions: • All ports in the port channel must be in the same Cisco Nexus 1000V module; you cannot configure port channels across Cisco Nexus 1000V modules. • Port channels can be formed with multiple upstream links only when they satisfy the compatibility requirements and under the following conditions: ◦...
1000V when vPC is also configured on the ports of upstream switches that connect to its VEMs. • You must have already configured the Cisco Nexus 1000Vsoftware using the setup routine. For information, see the Cisco Nexus 1000V Installation and Upgrade Guide.
Creating a Port Profile for a Port Channel You can define a port channel in a port profile and, if needed, to configure and pin interface or VLAN subgroups. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Server, the corresponding port group can be selected and assigned to physical ports (PNICs). Note If a port profile is configured as an Ethernet type, it cannot be used to configure VMware virtual ports. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Connecting to Multiple Upstream Switches You can create a port channel that connects to multiple upstream switches. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 68
Connectivity may be disrupted for up to 60 seconds if the CDP timer is set to 60 seconds (the default). Caution The VMs behind the Cisco Nexus 1000V receive duplicate packets from the network for unknown unicasts, Caution multicast floods, and broadcasts if vPC-HM is not configured when port channels connect to two different upstream switches.
Page 69
This example shows how to create a port channel that connects to multiple upstream switches that support CDP: switch# configure terminal switch(config)# port-profile UpLinkProfile2 switch(config-port-prof)# channel-group auto mode on sub-group cdp switch(config-port-prof)# show port-profile name UpLinkProfile2 Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 70
32 inherit: config attributes: channel-group auto mode on mac-pinning evaluated config attributes: channel-group auto mode on mac-pinning assigned interfaces: switch(config-port-prof)# copy running-config startup-config Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
• If you are pinning a control or packet VLAN, know that it must already be in the port profile. • If you are pinning a control VLAN, know that the control VLAN must already be one of the system VLANs in the port profile. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 74
SystemProfile1 switch(config-port-prof)# pinning packet-vlan 0 switch(config-port-prof)# show port-profile name SystemProfile1 port-profile SystemProfile1 description: type: ethernet status: disabled capability l3control: no pinning control-vlan: - pinning packet-vlan: 0 system vlans: 1 Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
The new port channel has a new port channel Step 5 When all the port(s) are moved from the old port profile, use the following command from the Cisco Nexus 1000V CLI to delete the port channels with zero members:no interface port-channel id Step 6 Bring the host out of maintenance mode.
• Otherwise, manually migrate the virtual machines. Step 3 When all the virtual machines are successfully migrated, from the Cisco Nexus 1000V CLI, create a new Ethernet type port profile for the uplink ports on this host. • Enter one of the following commands: ◦...
Specifies the maximum number of broadcasts that can be missed successively (from 3 to 7) before a split network is declared. The default is 5 missed broadcasts. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
(from 1 to 1048575). Step 3 switch(config-if)# pinning id subgroup_id Assigns (or pins) a vEthernet interface to a specific [backup subgroup_id1...subgroup_id7 ] port channel subgroup (from 0 to 31). Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Removing a Port Channel Group from a Port Profile You can remove a port channel group from a port profile. Before You Begin Log in to the CLI in EXEC mode. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Step 3 switch(config-if)# shutdown | no The shutdown keyword shuts down the interface. No shutdown traffic passes and the interface displays as administratively down. The default is no shutdown. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Adds a description to the port channel interface. string For the string, the description can be up to 80 alphanumeric characters. You do not need to use quotations around Note descriptions that include spaces. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Displays interface information for the specified port channel. Step 6 switch(config-if)# copy running-config (Optional) startup-config Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
• Configure a system uplink port profile for LACP. Before You Begin • Log in to the CLI in EXEC mode. • Know that the default port channel mode is on. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 85
Designates how the interfaces are to be used. Allowable port modes: switchport mode {access | • access private-vlan {host | promiscuous} | trunk} • private-vlan ◦ host ◦ promiscuous Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Configuring VEM Management of LACP You can offload management of LACP from the VSM to the VEMs. Before You Begin • Log in to the CLI in EXEC mode. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 87
Reboots both the primary and secondary VSM. Step 6 switch(config)# show lacp (Optional) Displays the LACP offload status for verification. offload status Note The current status does not change to enabled until after a reload. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Displays the Network State Tracking status for a interface channelID} module or interface. show port-channel compatibility-parameters Displays the parameters that must be the same among the member ports in order to join a port channel. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
[module module] Displays information about the number of error packets. show lacp counters [interface port-channel Displays information about LACP statistics. channel-number] Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
You can assign up to seven backup subgroups when pinning the primary subgroup. Port channel relative numbering 4.2(1)SV1(4a) The subgroup numbering begins at zero and is not tied to the vmnic number. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 91
Support for manual creation of subgroups. Static Pinning 4.0(4)SV1(2) Support for attaching (or pinning) a vEthernet interface to a specific port channel subgroup. Port Channels 4.0(4)SV1(1) This feature was introduced. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Page 92
Configuring Port Channels Feature History for Port Channels Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...
Interface Configuration Limits This chapter contains the following sections: • Interface Configuration Limits, page 89 Interface Configuration Limits The configuration limits are documented in the Cisco Nexus 1000V Resource Availability Reference. Cisco Nexus 1000V for VMware vSphere Interface Configuration Guide, Release 5.x...