Chapter 1. Overview

VEM Port Model

VEM Virtual Ports

VEM Physical Ports

Switching Traffic Between VEMs

Layer 2 Ethernet Switching

MAC Address Tables

VLANs

Private VLANs

IGMP Snooping

Chapter 2. Configuring MAC Address Tables

Information About MAC Address Tables

Guidelines and Limitations

Default Settings

Configuring a Static MAC Address

Configuring the Aging Time

Clearing Dynamic Addresses from the MAC Address Table

Verifying the MAC Address Table Configuration

Configuration Example for the MAC Address Table

Feature History for the MAC Address Table

Chapter 3. Configuring VLANs

Information About VLANs

Guidelines and Limitations

Default Settings

Creating a VLAN

Configuring VLAN Characteristics

Verifying the Configuration

Feature History for VLANs

Chapter 4. Configuring Private VLANs

Information About Private VLANs

Private VLAN Ports

Communication Between Private VLAN Ports

Guidelines and Limitations

Default Settings

Configuring a Private VLAN

Feature History for Private VLAN

Chapter 5. Configuring IGMP Snooping

Introduction

IGMPv1 and IGMPv2

IGMPv3

Prerequisites for IGMP Snooping

Default Settings

Enabling or Disabling IGMP Snooping Globally for the VSM

Configuring IGMP Snooping on a VLAN

Verifying the IGMP Snooping Configuration

Example Configuration IGMP Snooping

Feature History for IGMP Snooping

Chapter 6. Configuring Network Load Balancing for vEthernet

Information About Microsoft Network Load Balancing

Guidelines and Limitations

Configuring Microsoft Network Load Balancing Support in Interface Configuration Mode

Configuring Microsoft Network Load Balancing in Port Profile Configuration Mode

Enabling MAC Spoofing

Feature History for Microsoft Network Load Balancing for vEthernet

Chapter 7. Supporting Redundant Routing Protocols

Information About Redundant Routing Protocols

Guidelines and Limitations

Configuring a vEthernet Interface to Support Redundant Routing Protocols

Configuring a Port Profile to Support Redundant Routing Protocols

Feature History for Supporting Redundant Routing Protocol

Preface

Audience

Document Conventions

Related Documentation for Cisco Nexus 1000V for Microsoft Hyper-V Software

Documentation Feedback

Obtaining Documentation and Submitting a Service Request

Copyright Page

Chapter 1. Overview

This chapter contains the following sections:

- Layer 2 Ethernet Switching

- MAC Address Tables

- VLANs

- Private VLANs

- IGMP Snooping

VEM Port Model

The Cisco Nexus 1000V differentiates the following Virtual Ethernet Module (VEM) ports:

- VEM Virtual Ports

- VEM Physical Ports

The following figure shows the VEM view of the network.

VEM Port View

VEM Virtual Ports

The virtual side of the VEM maps together the following layers of ports:

Virtual NICs

There are two types of virtual NICs (vNICs). The vNIC is part of the Virtual Machine (VM), and represents the physical port of the host that is plugged into the switch. The internal NIC is used by the hypervisor for management,Live Migration, SMB iSCSI, and other network access. Each of these types maps to a Virtual Ethernet port within the Cisco Nexus 1000V.

Virtual Ethernet Ports

A virtual Ethernet port (vEth) represents a port on the Cisco Nexus 1000V Distributed Virtual Switch. The Cisco Nexus 1000V has a flat space of vEth ports, 1...n. These vEth ports are what the virtual cable plugs into and are moved to the host that the VM is running on. Virtual Ethernet ports are assigned to port groups.

VEM Physical Ports

The physical side of the VEM includes the following from top to bottom:

Physical Links

Each physical link on Hyper-V represents the actual physical NIC ports It on the host.

Uplink Ports

Each uplink port on the host represents a physical interface. There is a 1:1 mapping between uplink ports and physical links.

Ethernet Ports

Each physical port that is added to the Cisco Nexus 1000V appears as a physical Ethernet port, just as it would on a hardware-based switch.

Note

There is no fixed relationship between the uplink number and physical NIC number. These numbers can be different on different hosts and can change throughout the life of the host.

Switching Traffic Between VEMs

Each VEM that is attached to the VSM forwards traffic to and from the Hyper-V server as an independent and intelligent line card. Each VLAN uses its forwarding table to learn and store MAC addresses for ports that are connected to the VEM.

See the following figure to see how traffic flows between VEMs.

Traffic Flow Between VEMs

Layer 2 Ethernet Switching

The congestion related to high bandwidth and large numbers of users can be solved by assigning each device (for example, a server) to its own 10-, 100-, 1000-Mbps, or 10-Gigabit collision domain. Because each LAN port connects to a separate Ethernet collision domain, servers in a switched environment realize full bandwidth access.

Full duplex allows two stations to transmit and receive at the same time. 10/100-Mbps Ethernet usually operates in half-duplex mode, so that stations can either receive or transmit but not both. When packets can flow in both directions simultaneously, the effective Ethernet bandwidth doubles. 1/10-Gigabit Ethernet operates in full-duplex mode only.

Each LAN port can connect to a single workstation or server or to another device through which workstations or servers connect to the network.

To reduce signal degradation, each LAN port is considered to be an individual segment. When stations connected to different LAN ports need to communicate, frames are forwarded from one LAN port to the other at wire speed to ensure full bandwidth for each session.

MAC Address Tables

To switch frames between LAN ports efficiently, a MAC address table is maintained. The MAC address of the sending network is associated with the LAN port on which it was received.

VLANs

A VLAN is a switched network that is logically segmented by function, project team, or application, without regard to the physical locations of the users. VLANs have the same attributes of physical LANs, but you can group end stations even if they are not physically located on the same LAN segment.

Any switchport can belong to a VLAN, and unicast, broadcast, and multicast packets are forwarded and flooded only to end stations in that VLAN. Each VLAN is considered a logical network, and packets destined for stations that do not belong to the VLAN must be forwarded through a bridge or a router.

All ports, including the management port, are assigned to the default VLAN (VLAN1) when the device first comes up.

Up to 4094 VLANs are supported in accordance with the IEEE 802.1Q standard. These VLANs are organized into several ranges for different uses. Some of these VLANs are reserved for internal use by the device and are not available for configuration.

Note

You configure VLANs as VM subnets through OpenStack.

You must consistently use OpenStack for all VM network and subnet configuration. If you use both OpenStack and the VSM to configure VM networks and subnets, the OpenStack and the VSM configurations can become out-of-sync and result in faulty or inoperable network deployments.

Note

Inter-Switch Link (ISL) trunking is not supported on the Cisco Nexus 1000V.

Private VLANs

Private VLANs (PVLANs) are used to segregate Layer 2 ISP traffic and convey it to a single router interface. PVLANs achieve device isolation by applying Layer 2 forwarding constraints that allow end devices to share the same IP subnet while being Layer 2 isolated. The use of larger subnets reduces address management overhead.

IGMP Snooping

The Internet Group Management Protocol (IGMP) snooping software examines Layer 2 IP multicast traffic within a VLAN to discover the ports where interested receivers reside. Using the port information, IGMP snooping can reduce bandwidth consumption in a multi-access LAN environment to avoid flooding the entire VLAN. The IGMP snooping feature tracks which ports are attached to multicast-capable routers to help the routers forward IGMP membership reports. The IGMP snooping software responds to topology change notifications. By default, IGMP snooping is enabled on the device.

Chapter 2. Configuring MAC Address Tables

This chapter contains the following sections:

- Information About MAC Address Tables

- Guidelines and Limitations

- Default Settings

- Verifying the MAC Address Table Configuration

- Configuration Example for the MAC Address Table

- Feature History for the MAC Address Table

Information About MAC Address Tables

Layer 2 ports correlate the MAC address on a packet with the Layer 2 port information for that packet using the MAC address table. A MAC address table is built using the MAC source addresses of the frames received. When a frame is received for a MAC destination address not listed in the address table, the frame is flooded to all LAN ports of the same VLAN with the exception of the port that received the frame. When the destination station replies, the relevant MAC source addresses and port IDs are added to the address table. Subsequent frames are forwarded to a single LAN port without flooding all LAN ports.

You can configure MAC addresses, which are called static MAC addresses, to statically point to specified interfaces on the device. These static MAC addresses override any dynamically learned MAC addresses on those interfaces. You cannot configure broadcast or multicast addresses as static MAC addresses. The static MAC entries are retained across reboots if you copy the static MAC addresses configuration to the startup configuration by using the copy running-config startup-config command.

The address table per VEM can store up to 32,000 MAC entries. An aging timer triggers removal of addresses from the table when they remain inactive for the default time of 300 seconds. The aging timer can be configured on a global basis but not per VLAN.

You can configure the length of time an entry remains in the MAC address table, clear the table, and so forth.

Guidelines and Limitations

- The forwarding table for each VLAN in a VEM can store up to 4096 MAC addresses.

- You can configure only 32 static MAC addresses on a single interface and 1024 static MAC addresses on a DVS.

- The Cisco Nexus 1000V supports a maximum of 2000 private VLAN MAC addresses on a VSM.

Default Settings

Default MAC Address Aging Time

Parameters

Default

Aging time

300 seconds

Configuring a Static MAC Address

Use this procedure to configure a MAC address to statically point to a specific interface.

Before You Begin

- You are logged in to the CLI in EXEC mode.

- You cannot configure broadcast or multicast addresses as static MAC addresses.

- Static MAC addresses override dynamically-learned MAC addresses on an interface.

Note

Be aware that the Cisco NX-OS commands may differ from those used in Cisco IOS.

Procedure

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# mac address-table static mac_address vlan vlan-id {[ drop | interface { type if_id } port-channel number ]}

Adds a static MAC address in the Layer 2 MAC address table and saves it in the running configuration.

Interface can be specified as either of the following:

- ethernet slot/port

- veth number

Step 3

switch(config)# show mac address static interface [ type if_id ]

(Optional)
Displays static MAC addresses.

Step 4

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

(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

switch# configure terminal
switch(config)# mac address-table static 0002.3d11.5502 vlan 3967 interface ethernet 3/3
switch(config)# show mac address static
VLAN      MAC Address       Type    Age       Port                           Module
---------+-----------------+-------+---------+------------------------------+---------
1         0002.3d11.5502    static  0         N1KV Internal Port             3
1         0002.3d21.5500    static  0         N1KV Internal Port             3
1         0002.3d21.5502    static  0         N1KV Internal Port             3
1         0002.3d31.5502    static  0         N1KV Internal Port             3
1         0002.3d41.5502    static  0         N1KV Internal Port             3
1         0002.3d61.5500    static  0         N1KV Internal Port             3
1         0002.3d61.5502    static  0         N1KV Internal Port             3
1         0002.3d81.5502    static  0         N1KV Internal Port             3
3         12ab.47dd.ff89    static  0         Eth3/3                         3
342       0002.3d41.5502    static  0         N1KV Internal Port             3
343       0002.3d21.5502    static  0         N1KV Internal Port             3
Total MAC Addresses: 11
n1000v(config)# show mac address static interface Ethernet 3/3
VLAN      MAC Address       Type    Age       Port                           Module
---------+-----------------+-------+---------+------------------------------+---------
3         12ab.47dd.ff89    static  0         Eth3/3                         3
Total MAC Addresses: 1
switch(config)#

Configuring the Aging Time

Use this procedure to configure the amount of time that packet source MAC addresses, and the ports on which they are learned, remain in the MAC table containing the Layer 2 information.

Note

The aging time is a global setting that cannot be configured per VLAN. Although it is a global setting, you can also configure MAC aging time in interface configuration mode or VLAN configuration mode.

Before You Begin

You are logged in to the CLI in EXEC mode.

Note

Be aware that the Cisco NX-OS commands may differ from those used in Cisco IOS.

Procedure

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch# mac address-table aging-time seconds

Specifies and saves in the running configuration the amount of time that will elapse before an entry in the Layer 2 MAC address table is discarded.

Allowable entries include:

- 120 to 918000 seconds (default is 300)

- If you specify zero (0), MAC aging is disabled.

switch# configure terminal
switch(config)# mac address-table aging-time 600
switch(config)# show mac address-table aging-time
Vlan  Aging Time
----- ----------
101   300
100   300
1     300
switch#

Clearing Dynamic Addresses from the MAC Address Table

Before You Begin

You are logged in to the CLI in EXEC mode.

Note

Be aware that the Cisco NX-OS commands may differ from those used in Cisco IOS.

Procedure

Command or Action

Purpose

Step 1

switch# clear mac address-table dynamic [ vlan vlan_id ]

Clears the dynamic address entries from the Layer 2 MAC address table.

Step 2

switch# show mac address-table

(Optional)
Displays the MAC address table.

The following example clears the entire MAC address table of all dynamic entries:

switch# clear mac address-table dynamic
switch#

The following example clears the MAC address table of only those dynamic MAC addresses learned on VLAN 5:

switch# clear mac address-table dynamic vlan 5
switch#

Verifying the MAC Address Table Configuration

Use one of the following commands to verify the configuration:

Command

Purpose

show mac address-table

Displays the MAC address table.

show mac address-table static

Displays information about the MAC address table static entries.

show mac address-table static | inc veth

Displays the static MAC address of vEthernet interfaces in case a VEM physical port learns a dynamic MAC and the packet source is in another VEM on the same VSM.

show mac address static interface [ type if_id ]

Displays all static MAC addresses.

show mac address-table aging-time

Displays the aging time in the MAC address table.

show mac address-table count

Displays a count of MAC address entries.

show interface interface_id mac

Displays the MAC addresses and the burn-in MAC address for an interface.

Example for show mac address-table

switch# show mac address-table
VLAN      MAC Address       Type    Age       Port                           Module
---------+-----------------+-------+---------+------------------------------+---------
1         0002.3d11.5502    static  0         N1KV Internal Port             3
1         0002.3d21.5500    static  0         N1KV Internal Port             3
1         0002.3d21.5502    static  0         N1KV Internal Port             3
1         0002.3d31.5502    static  0         N1KV Internal Port             3
1         0002.3d41.5502    static  0         N1KV Internal Port             3
1         0002.3d61.5500    static  0         N1KV Internal Port             3
1         0002.3d61.5502    static  0         N1KV Internal Port             3
1         0002.3d81.5502    static  0         N1KV Internal Port             3
3         12ab.47dd.ff89    static  0         Eth3/3                         3
342       0002.3d41.5502    static  0         N1KV Internal Port             3
342       0050.568d.5a3f    dynamic 0         Eth3/3                         3
343       0002.3d21.5502    static  0         N1KV Internal Port             3
343       0050.568d.2aa0    dynamic 9         Eth3/3                         3
Total MAC Addresses: 13
switch#

Example for show mac address-table static | inc veth

switch# show mac address-table static | inc veth
460       0050.5678.ed16    static  0         Veth2                          3
460       0050.567b.1864    static  0         Veth1                          4
switch#

Example for show mac address static

switch# show mac address static
VLAN      MAC Address       Type    Age       Port                           Module
---------+-----------------+-------+---------+------------------------------+---------
1         0002.3d11.5502    static  0         N1KV Internal Port             3
1         0002.3d21.5500    static  0         N1KV Internal Port             3
1         0002.3d21.5502    static  0         N1KV Internal Port             3
1         0002.3d31.5502    static  0         N1KV Internal Port             3
1         0002.3d41.5502    static  0         N1KV Internal Port             3
1         0002.3d61.5500    static  0         N1KV Internal Port             3
1         0002.3d61.5502    static  0         N1KV Internal Port             3
1         0002.3d81.5502    static  0         N1KV Internal Port             3
3         12ab.47dd.ff89    static  0         Eth3/3                         3
342       0002.3d41.5502    static  0         N1KV Internal Port             3
343       0002.3d21.5502    static  0         N1KV Internal Port             3
Total MAC Addresses: 11
switch(config)# show mac address static interface Ethernet 3/3
VLAN      MAC Address       Type    Age       Port                           Module
---------+-----------------+-------+---------+------------------------------+---------
3         12ab.47dd.ff89    static  0         Eth3/3                         3
Total MAC Addresses: 1
switch#

Example for show mac address static interface

switch# show mac address static interface Ethernet 3/3
VLAN      MAC Address       Type    Age       Port                           Module
---------+-----------------+-------+---------+------------------------------+---------
3         12ab.47dd.ff89    static  0         Eth3/3                         3
Total MAC Addresses: 1
switch#

Example for show mac address-table aging-time

switch# show mac address-table aging-time
Vlan  Aging Time
----- ----------
101   300
100   300
1     300
switch#

Example for show mac address-table count

switch# show mac address-table count static
Total MAC Addresses: 12
switch#

Configuration Example for the MAC Address Table

The following example shows how to add a static MAC address and establish a global aging time:

switch# configure terminal
switch(config)# mac address-table static 0000.0000.1234 vlan 10 interface ethernet 2/15
switch(config)# mac address-table aging-time 120
switch(config)#

Feature History for the MAC Address Table

Feature Name

Releases

Feature Information

MAC Address Tables

5.2(1)SM1(5.1)

This feature was introduced

Chapter 3. Configuring VLANs

This chapter contains the following sections:

- Information About VLANs

- Guidelines and Limitations

- Default Settings

- Verifying the Configuration

- Feature History for VLANs

Information About VLANs

Physical NICs are always assigned as trunk ports that transmit either VLAN tagged or untagged packets. A vswitch can have the following VLAN configurations:

Configuration

Description

External Switch Tagging (EST)

Physical NICs are untagged and all vNICs are access ports. EST is enabled by default and is used when the VLAN for the vNIC is set to 0 or left blank.

Virtual Switch Tagging (VST)

All physical NIC ports are tagged and vNICs are access ports. VST is enabled whenever the vNIC’s VLAN is set to any value between 1 and 4094, inclusive.

Virtual Machine Guest Tagging (VGT)

All physical NIC ports are tagged. vNICs are trunk ports. To configure VGT, the VLAN is set to 4095 on the vNIC that is connected to the Virtual Machine (VM).

Physical ports are always trunk ports by default. The VM interfaces can be either access ports or trunk ports.

vEthernet interfaces that are assigned to specific VLANs are tagged with the VLAN when transmitted. A vEthernet interface that is not assigned to a specific VLAN, or assigned to VLAN 0, is transmitted as untagged on the physical NIC interfaces. When the VLAN is not specified, it is assumed to be 1.

The following table summarizes the actions taken on packets that are received by the Virtual Ethernet Module (VEM) based on VLAN tagging.

VEM Action on VLAN Tagging

Port Type

Packet received

Action

Access

Tagged

The packet is dropped.

Access

Untagged

The VEM adds an access VLAN to the packet.

Trunk

Tagged

No action is taken on the packet.

Trunk

Untagged

The VEM adds a native VLAN tag to the packet.

Guidelines and Limitations

In accordance with the IEEE 802.1Q standard, up to 4094 VLANs (from 1 to 4094) are supported in the Cisco Nexus 1000V, and are listed in the following table.

Note

For VLAN configuration limits, see Layer 2 Switching Configuration Limits.

Cisco Nexus 1000V VLAN Numbering

VLAN Numbers

Range

Usage

1

Normal

Cisco Nexus 1000V default. You can use this VLAN, but you cannot modify or delete it.

2 to1005

Normal

You can create, use, modify, or delete these VLANs.

1006 to 4094

Extended

You can create, name, or use these VLANs. You cannot change the following parameters:

- The state is always active.

- These VLANs are always enabled. You cannot shut down these VLANs.

The extended system ID is always automatically enabled.

3968 to 4047 and 4094

Internally allocated

You cannot use, create, delete, or modify these VLANs. You can display these VLANs.

The Cisco Nexus 1000V allocates these 80 VLANs, plus VLAN 4094, for features, like diagnostics, that use internal VLANs for their operation.

Default Settings

Default VLAN Settings

Parameters

Default

VLAN assignment for all interfaces and all ports configured as switchports

VLAN 1

VLAN name

VLANxxxx where xxxx represent four numeric digits (including leading zeroes) equal to the VLAN ID number

Shut state

No shutdown

Operational state

Active

External switch tagging (EST)

Enabled

Physical ports

Trunk ports

IGMP snooping

Enabled

Creating a VLAN

In Cisco Nexus 1000V for Microsoft Hyper-V, a VLAN is not created to define a bridge domain. Instead, a network segment is created on the virtual supervisor module (VSM). The network segment creation triggers the auto-creation of VLANs. Refer to the Cisco Nexus 1000V for Microsoft Hyper-V Network Segmentation Manager Configuration Guide for more about the VLAN configuration process.

Configuring VLAN Characteristics

Refer to the Cisco Nexus 1000V for Microsoft Hyper-V Network Segmentation Manager Configuration Guide for more information about the VLAN configuration process.

Verifying the Configuration

Use one of the following commands to verify the configuration:

Command

Purpose

show running-config vlan vlan-id

Displays VLAN information in the running configuration.

show vlan [ all-ports | brief | id vlan-id | name name | dot1q tag native ]

Displays the specified VLAN information.

show vlan summary

Displays a summary of VLAN information.

Example for show vlan summary

switch# show vlan summary

Number of existing VLANs           : 13
Number of existing user VLANs     : 12
Number of existing extended VLANs : 1

switch#

Example for show vlan brief

switch# show vlan brief
VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Eth2/1, Eth2/2, Eth2/3, Eth2/5
Eth2/7, Eth2/8, Eth2/9, Eth2/10
Eth2/15, Eth2/21, Eth2/22
Eth2/23, Eth2/24, Eth2/25
Eth2/46, Eth2/47, Eth2/48
5    accounting                       active
6    VLAN0006                         active
7    VLAN0007                         active
8    test                             active
9    VLAN0009                         active
10   VLAN0010                         active
50   VLAN0050                         active    Eth2/6
100  trunked                          active
200  VLAN0200                         active
201  VLAN0201                         active
202  VLAN0202                         active
3966 VLAN3966                         active
switch#

Feature History for VLANs

Feature Name

Releases

Feature Information

VLANs

5.2(1)SM1(5.1)

This feature was introduced

Chapter 4. Configuring Private VLANs

This chapter contains the following sections:

- Information About Private VLANs

- Private VLAN Ports

- Communication Between Private VLAN Ports

- Guidelines and Limitations

- Default Settings

- Configuring a Private VLAN

- Feature History for Private VLAN

Information About Private VLANs

PVLANs achieve Layer 2 isolation through the use of three separate port designations, each having its own unique set of rules that regulate each connected endpoint's ability to communicate with other connected endpoints within the same private VLAN domain.

Private VLAN Domains

A PVLAN domain consists of one or more pairs of VLANs. The primary VLAN makes up the domain; and each VLAN pair makes up a subdomain. The VLANs in a pair are called the primary VLAN and the secondary VLAN. All VLAN pairs within a private VLAN have the same primary VLAN. The secondary VLAN ID is what differentiates one subdomain from another. See the following figure.

Private VLAN Domain

Spanning Multiple Switches

PVLANs can span multiple switches, just like regular VLANs. Inter-switch link ports do not need to be aware of the special VLAN type and carry frames tagged with these VLANs just like they do any other frames. PVLANs ensure that traffic from an isolated port in one switch does not reach another isolated or community port in a different switch even after traversing an inter-switch link. By embedding the isolation information at the VLAN level and by transporting it with the packet, it is possible to maintain consistent behavior throughout the network. The mechanism that restricts Layer 2 communication between two isolated ports in the same switch also restricts Layer 2 communication between two isolated ports in two different switches.

Private VLAN Ports

Within a PVLAN domain, there are three separate port designations. Each port designation has its own unique set of rules that regulate the ability of one endpoint to communicate with other connected endpoints within the same private VLAN domain. The three port designations are as follows:

- promiscuous

- isolated

- community

Primary VLANs and Promiscuous Ports

The primary VLAN encompasses the entire PVLAN domain. It is a part of each subdomain and provides the Layer 3 gateway out of the VLAN. A PVLAN domain has only one primary VLAN. Every port in a PVLAN domain is a member of the primary VLAN.

A promiscuous port can talk to all other types of ports; it can talk to isolated ports as well as community ports and vice versa. Layer 3 gateways, DHCP servers, and other trusted devices that need to communicate with the customer endpoints are typically connected with a promiscuous port. A promiscuous port can be either an access port or a hybrid/trunk port according to the terminology presented in Annex D of the IEEE 802.1Q specification.

Secondary VLANs and Host Ports

Secondary VLANs provide Layer 2 isolation between ports in a PVLAN domain. A PVLAN domain can have one or more subdomains. A subdomain is made up of a VLAN pair that consists of the primary VLAN and a secondary VLAN. Because the primary VLAN is a part of every subdomain, secondary VLANs differentiate the VLAN subdomains.

To communicate to the Layer 3 interface, you must associate a secondary VLAN with at least one of the promiscuous ports in the primary VLAN. You can associate a secondary VLAN to more than one promiscuous port within the same PVLAN domain, for example, if needed for load balancing or redundancy. A secondary VLAN that is not associated with any promiscuous port cannot communicate with the Layer 3 interface.

A secondary VLAN can be one of the following types:

- Isolated VLANs—Isolated VLANs use isolated host ports. An isolated port cannot talk to any other port in that private VLAN domain except for promiscuous ports. If a device needs to have access only to a gateway router, it should be attached to an isolated port. An isolated port is typically an access port, but in certain applications, it can also be a hybrid or trunk port.

An isolated VLAN allows all its ports to have the same degree of segregation that could be obtained from using one separate dedicated VLAN per port. Only two VLAN identifiers are used to provide this port isolation.

Note

While multiple community VLANs can be in a private VLAN domain, one isolated VLAN can serve multiple customers. All endpoints that are connected to its ports are isolated at Layer 2. Service providers can assign multiple customers to the same isolated VLAN and be assured that their Layer 2 traffic cannot be sniffed by other customers that share the same isolated VLAN.

- Community VLANs—Community VLANs use community host ports. A community port is part of a group of ports. The ports within a community can communicate at Layer 2 with one another and can also talk to any promiscuous port. For example, if an ISP customer has four devices and wants them isolated from those devices of other customers but still be able to communicate among themselves, community ports should be used.

Note

Because trunks can support a VLAN that carries traffic between its ports, VLAN traffic can enter or leave the device through a trunk interface.

Communication Between Private VLAN Ports

The following table shows how access is permitted or denied between PVLAN port types.

Communication Between PVLAN Ports

Isolated

Promiscuous

Community 1

Community 2

Interswitch Link Port[1]

Isolated

Deny

Permit

Deny

Deny

Permit

Promiscuous

Permit

Permit

Permit

Permit

Permit

Community 1

Deny

Permit

Permit

Deny

Permit

Community 2

Deny

Permit

Deny

Permit

Permit

Interswitch Link Port

Deny[2]

Permit

Permit

Permit

Permit

[1] An interswitch link port is a regular port that connects two switches and that happens to carry two or more VLANs.

[2] This behavior applies to traffic that traverses inter-switch link ports over an isolated VLAN only. Traffic from an inter-switch link port to an isolated port will be denied if it is in the isolated VLAN. Traffic from an inter-switch link port to an isolated port will be permitted if it is in the primary VLAN.

Guidelines and Limitations

PVLANs have the following configuration guidelines and limitations:

Control VLANs, packet VLANs, and management VLANs must be configured as regular VLANs and not as private VLANs.

The following are configuration limits:

- Private VLANs per DVS: 512 maximum

- Primary VLANs per promiscuous trunk port: 64 maximum

- Private VLAN associations: 511 maximum

- Private VLAN ports per DVS : 4096 maximum

Default Settings

Default PVLAN Settings

Parameters

Default

PVLANs

Disabled

Configuring a Private VLAN

Refer to the Cisco Nexus 1000V for Microsoft Hyper-V Network Segmentation Manager Configuration Guide for more about the private VLAN configuration process.

Feature History for Private VLAN

Feature Name

Releases

Feature Information

Private VLAN

5.2(1)SM1(5.1)

This feature was introduced.

Chapter 5. Configuring IGMP Snooping

This chapter contains the following sections:

- Prerequisites for IGMP Snooping

- Default Settings

- Verifying the IGMP Snooping Configuration

- Example Configuration IGMP Snooping

- Feature History for IGMP Snooping

Introduction

The Internet Group Management Protocol (IGMP) snooping software examines Layer 2 IP multicast traffic within a VLAN to discover the ports where interested receivers reside. Using the port information, IGMP snooping can reduce bandwidth consumption in a multi-access LAN environment to avoid flooding the entire VLAN. The IGMP snooping feature tracks which ports are attached to multicast-capable routers to help the routers forward IGMP membership reports. The IGMP snooping software responds to topology change notifications. By default, IGMP snooping is enabled on the device.

The following figure shows an IGMP snooping switch that sits between the host and the IGMP router. The IGMP snooping switch snoops the IGMP membership reports and Leave messages and forwards them only when necessary to the connected IGMP routers.

IGMP Snooping Switch

The IGMP snooping software operates upon IGMPv1, IGMPv2, and IGMPv3 control plane packets where Layer 3 control plane packets are intercepted and influence the Layer 2 forwarding behavior.

The Cisco Nexus 1000V IGMP snooping implementation has the following proprietary features:

- Multicast forwarding based on an IP address rather than a MAC address.

- Optimized multicast flooding (OMF) that forwards unknown traffic to routers only and performs no data driven state creation.

For more information about IGMP snooping, see RFC 4541.

IGMPv1 and IGMPv2

If no more than one host is attached to each VLAN switch port, you can configure the fast leave feature in IGMPv2. The fast leave feature does not send last member query messages to hosts. As soon as the software receives an IGMP leave message, the software stops forwarding multicast data to that port.

IGMPv1 does not provide an explicit IGMP leave message, so the software must rely on the membership message timeout to indicate that no hosts remain that want to receive multicast data for a particular group.

Report suppression is not supported and is disabled by default.

Note

The software ignores the configuration of the last member query interval when you enable the fast leave feature because it does not check for remaining hosts.

IGMPv3

IGMPv3 snooping provides constrained flooding based on the group IP information in the IGMPv3 reports.

By default, the software tracks hosts on each VLAN port. The explicit tracking feature provides a fast leave mechanism. Because every IGMPv3 host sends membership reports, report suppression limits the amount of traffic that the switch sends to other multicast-capable routers.

Even though the IGMPv3 membership reports provide a full accounting of group members on a LAN segment, when the last host leaves, the querier sends a membership query. You can configure the parameter last member query interval. If no host responds before the timeout, the software removes the group state. If the querier specifies a mean-response-time (MRT) value in the query, it overrides the last member query interval configuration.

Prerequisites for IGMP Snooping

IGMP snooping has the following prerequisites:

- You are logged in to the switch.

- A querier must be running on the uplink switches on the VLANs that contain multicast sources and receivers.

When the multicast traffic does not need to be routed, you must configure an external switch to query membership. On the external switch, define the query feature in a VLAN that contains multicast sources and receivers but no other active query feature. In the Cisco Nexus 1000V, report suppression is not supported and is disabled by default.

When an IGMP snooping query feature is enabled , it sends out periodic IGMP queries that trigger IGMP report messages from hosts wanting to receive IP multicast traffic. IGMP snooping listens to these IGMP reports to identify accurate forwarding.

Default Settings

Default IGMP Snooping Settings

Parameters

Default

IGMP snooping

Enabled

IGMPv3 Explicit tracking

Enabled

IGMPv2 Fast leave

Disabled

Last member query interval

1 second

Link-local groups suppression

Enabled

Snooping querier

Disabled

IGMPv1/v2 Report suppression

Disabled

IGMPv3 Report suppression

Disabled

Enabling or Disabling IGMP Snooping Globally for the VSM

Use this procedure to enable or disable IGMP snooping globally for the VSM. IGMP snooping is enabled globally on the VSM (the default). If enabled globally, you can turn it on or off per VLAN.

Before You Begin

You are logged in to the CLI in EXEC mode.

Procedure

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# [ no ] ip igmp snooping

Enables or disables IGMP snooping in the running configuration for all VLANs. The default is enabled. If you have previously disabled the feature then you can enable it with this command.

Step 3

switch(config)# show ip igmp snooping [ vlan vlan-id ]

(Optional)
Displays the configuration for verification.

Note:
If disabled, then IGMP snooping on all VLANs is disabled.

Step 4

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

(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

switch# configure terminal
switch(config)# no ip igmp snooping
switch(config)# show ip igmp snooping
Global IGMP Snooping Information:
IGMP Snooping enabled
IGMPv1/v2 Report Suppression disabled
IGMPv3 Report Suppression disabled
Link Local Groups Suppression enabled

IGMP Snooping information for vlan 1
IGMP snooping enabled
IGMP querier none
Switch-querier disabled
IGMPv3 Explicit tracking enabled
IGMPv2 Fast leave disabled
IGMPv1/v2 Report suppression disabled
IGMPv3 Report suppression disabled
Link Local Groups suppression enabled
Router port detection using PIM Hellos, IGMP Queries
Number of router-ports: 0
Number of groups: 0
Active ports:

--More--
switch(config)#

Configuring IGMP Snooping on a VLAN

Use this procedure to configure IGMP snooping on a VLAN. IGMP snooping is enabled by default for all VLANs in the VSM.

Before You Begin

You are logged in to the CLI in EXEC mode.

Note

If IGMP snooping is disabled globally, it takes precedence over the VLAN state.

Procedure

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# vlan configuration vlan-id

Enters configuration mode for the specified VLAN.

Step 3

switch(config-vlan-config)# [ no ] ip igmp snooping

Enables or disables IGMP snooping in the running configuration for the specific VLAN. If IGMP snooping is enabled for the VSM, then IGMP snooping is enabled for the VLAN by default.

Note:
IGMP snooping must be enabled globally (the default) in order to toggle it on or off per VLAN. If IGMP snooping is disabled globally, then it cannot be enabled per VLAN.

Step 4

switch(config-vlan-config)# [ no ] ip igmp snooping explicit-tracking

(Optional)
Tracks IGMPv3 membership reports from individual hosts for each port on a per-VLAN basis in the running configuration.

The default is enabled.

Step 5

switch(config-vlan-config)# [ no ] ip igmp snooping fast-leave

(Optional)
Enables fast-leave for the specified VLAN in the running configuration.

Fast-leave supports IGMPv2 hosts that cannot be explicitly tracked because of the host report suppression mechanism of the IGMPv2 protocol.

Enables the software to remove the group state when it receives an IGMP Leave report without sending an IGMP query message. This parameter is used for IGMPv2 hosts when no more than one host is present on each VLAN port.

When you enable fast leave, the IGMP software assumes that no more than one host is present on each VLAN port.

The default is disabled.

Step 6

switch(config-vlan-config)# [ no ] ip igmp snooping last-member-query-interval seconds

(Optional)
Sets the interval the software waits after sending an IGMP query to verify that no hosts that want to receive a particular multicast group remain on a network segment. If no hosts respond before the last member query interval expires, the software removes the group from the associated VLAN port.

Values range from 1 to 25 seconds. The default is 1 second.

Step 7

switch(config-vlan-config)# [ no ] ip igmp snooping mrouter interface type if_id

(Optional)
Configures a static connection for the VLAN to a multicast router in the running configuration.

The interface to the router must be in the specified VLAN. You can specify the interface by the type and the number, such as ethernet slot/port.

vEths are not supported as router ports.

Step 8

switch(config-vlan-config)# [ no ] ip igmp snooping static-group group-ip-addr interface type if_id

(Optional)
Configures a VLAN Layer 2 port as a static member of a multicast group in the running configuration.

You can specify the interface by the type and the number, such as ethernet slot/port.

Step 9

switch(config-vlan-config)# [ no ] ip igmp snooping link-local-groups-suppression

(Optional)
Configures link-local groups suppression. The default is enabled.

Note:
You can apply link-local groups suppression to all interfaces in the VSM by entering this command in global configuration mode.

Step 10

switch(config-vlan-config)# show ip igmp snooping [ vlan vlan-id ]

(Optional)
Displays the configuration for verification.

Step 11

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

(Optional)
(Optional) Saves the running configuration persistently through reboots and restarts by copying it to the startup configuration.

switch# configure terminal
switch(config)# vlan configuration 2
switch(config-vlan-config)# ip igmp snooping
switch(config-vlan-config)# ip igmp snooping explicit-tracking
switch(config-vlan-config)# ip igmp snooping fast-leave
switch(config-vlan-config)# ip igmp snooping last-member-query-interval 3
switch(config-vlan-config)# ip igmp snooping mrouter interface ethernet 2/1
switch(config-vlan-config)# ip igmp snooping static-group 230.0.0.1 interface ethernet 2/1
switch(config-vlan-config)# ip igmp snooping link-local-groups-suppression
switch(config-vlan-config)# show ip igmp snooping vlan 2

IGMP Snooping information for vlan 2
IGMP snooping enabled
IGMP querier none
Switch-querier disabled
IGMPv3 Explicit tracking enabled
IGMPv2 Fast leave enabled
IGMPv1/v2 Report suppression disabled
IGMPv3 Report suppression disabled
Link Local Groups suppression enabled
Router port detection using PIM Hellos, IGMP Queries
Number of router-ports: 0
Number of groups: 0
Active ports:
switch(config-vlan)#

Verifying the IGMP Snooping Configuration

Use the following commands to verify the IGMP snooping configuration information.

Command

Purpose

show ip igmp snooping [ vlan vlan-id ]

Displays IGMP snooping configuration by VLAN.

show ip igmp snooping groups [ vlan vlan-id ] [ detail ]

Displays IGMP snooping information about groups by VLAN.

show ip igmp snooping querier [ vlan vlan-id ]

Displays IGMP snooping queriers by VLAN.

show ip igmp snooping mroute [ vlan vlan-id ]

Displays multicast router ports by VLAN.

show ip igmp snooping explicit-tracking [ vlan vlan-id ]

Displays IGMP snooping explicit tracking information by VLAN.

For detailed information about commands and their output, see the Cisco Nexus 1000V for Microsoft Hyper-V Command Reference.

Example Configuration IGMP Snooping

This example shows how to enable IP IGMP snooping for the VSM, and make the following optional configurations for VLAN 2:

- Tracking of IGMPv3 membership reports from individual hosts for each port.

- A static connection to a multicast router through Ethernet 2/1.

- Static membership in multicast group 230.0.0.1.

Feature History for IGMP Snooping

Feature Name

Releases

Feature Information

IGMP Snooping

5.2(1)SM1(5.1)

This feature was introduced.

Chapter 6. Configuring Network Load Balancing for vEthernet

This chapter contains the following sections:

- Information About Microsoft Network Load Balancing

- Guidelines and Limitations

- Configuring Microsoft Network Load Balancing Support in Interface Configuration Mode

- Configuring Microsoft Network Load Balancing in Port Profile Configuration Mode

- Enabling MAC Spoofing

- Feature History for Microsoft Network Load Balancing for vEthernet

Information About Microsoft Network Load Balancing

Microsoft Network Load Balancing (NLB) is a clustering technology offered by Microsoft as part of the Windows server operating systems. Clustering enables a group of independent servers to be managed as a single system for higher availability, easier manageability, and greater scalability.

For more information about Microsoft NLB, see Click Here

Note

Access to third-party websites identified in this document is provided solely as a courtesy to customers and others. Cisco Systems, Inc. and its affiliates are not in any way responsible or liable for the functioning of any third-party website, or the download, performance, quality, functioning or support of any software program or other item accessed through the website, or any damages, repairs, corrections or costs arising out of any use of the website or any software program or other item accessed through the website. Cisco's End User License Agreement does not apply to the terms and conditions of use of a third-party website or any software program or other item accessed through the website.

Guidelines and Limitations

NLB has the following configuration guidelines and limitations:

- The no mac auto-static-learn command is not supported on PVLAN ports.

- The no mac auto-static-learn command is not supported on the ports that are configured with switchport port-security mac-address sticky.

- Unknown unicast flood blocking (UUFB) does not block Microsoft-Network Load Balancing (MS-NLB) packets on MS-NLB vEthernet interfaces. UUFB can be used to limit flooding of MS-NLB packets to non-MS-NLB ports within a VLAN.

Configuring Microsoft Network Load Balancing Support in Interface Configuration Mode

Use this procedure to configure Microsoft Network Load Balancing in the interface configuration mode.

Before You Begin

Note

Make sure that the Cisco Nexus 1000V is configured before you configure Microsoft NLB on Windows virtual machines (VMs).

- You are logged in to the CLI in EXEC mode.

- Unicast is the default Microsoft Network Load Balancing mode of operation.

- Microsoft NLB replaces the MAC address of each server in the host group to a common Microsoft NLB MAC address.

- VM interfaces that are used for MS-NLB clusters should have "spoofing enabled" in the HyperV VM settings. For information about enabling MAC spoofing, see Enabling MAC Spoofing.

Procedure

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# show running-config interface veth number

Displays the vEthernet configuration to determine if no mac auto-static-learn is configured or not.

Step 3

switc(config)# interface veth

Sets interface configuration mode on vEthernet modules.

Step 4

switch(config-if)# [ no ] mac auto-static-learn

Toggles the auto-mac-learning on vEthernet modules.

Step 5

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

(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

The following example shows how to configure Microsoft Network Load Balancing directly on vEthernet:

switch# configure terminal
switch(config)# interface vethernet 1
switch(config-if)# no mac auto-static-learn
switch(config-if)# show running-config interface vethernet 1
!Command: show running-config interface Vethernet1
!Time: Wed Feb 20 16:12:14 2013

version 5.2(1)SM1(5.1)

interface Vethernet1
no mac auto-static-learn

switch(config-if)#

The following example shows how to unconfigure Microsoft Network Load Balancing directly from vEthernet:

switch# configure terminal
switch(config)# interface vethernet 1
switch(config-if)# mac auto-static-learn
switch(config-if)# show running-config interface vethernet 1
!Command: show running-config interface Vethernet1
!Time: Wed Feb 20 16:14:06 2013

version 5.2(1)SM1(5.1)

interface Vethernet1

switch(config-if)#

Configuring Microsoft Network Load Balancing in Port Profile Configuration Mode

Use this procedure to configure Microsoft Network Load Balancing in the port profile configuration mode.

Before You Begin

Note

Make sure that the Cisco Nexus 1000V is configured before you configure Microsoft NLB on Windows virtual machines (VMs).

- You are logged in to the CLI in EXEC mode.

- Unicast is the default Microsoft Network Load Balancing mode of operation.

- Microsoft NLB replaces the MAC address of each server in the host group to a common Microsoft NLB MAC address.

Procedure

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# show running config port-profile profile name

Displays the port profile configuration to determine if no mac auto-static-learn is configured or not.

Step 3

switch(config)# port profile type vethernet ms-nlb

Sets port profile configuration mode on vEthernet modules.

Step 4

switch(config-port-prof)# [ no ] mac auto-static-learn

Toggles the auto-mac-learning on vEthernet modules.

Step 5

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

(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

The following example shows how to configure Microsoft Network Load Balancing in port profile mode:

switch# configure terminal
switch(config)# port-profile type vethernet ms-nlb
switch(config-port-prof)# switchport mode access
switch(config-port-prof)# switchport access vlan 59
switch(config-port-prof)# no mac auto-static-learn
switch(config-port-prof)# no shutdown
switch(config-port-prof)# state enabled
switch(config-port-prof)# show run port-profile ms-nlb
!Command: show running-config port-profile ms-nlb
!Time: Wed Feb 20 16:18:46 2013

version 5.2(1)SM1(5.1)
port-profile type vethernet ms-nlb
switchport mode access
switchport access vlan 59
no mac auto-static-learn
no shutdown
guid 2402bb48-eb6d-4260-8891-8223fa000f5f
state enabled
switch(config-port-prof)#

The following example shows how to unconfigure Microsoft Network Load Balancing on vEthernet in port profile mode:

switch# configure terminal
switch(config)# port-profile type vethernet ms-nlb
switch(config-port-prof)# mac auto-static-learn
switch(config-port-prof)# show run port-profile ms-nlb
!Command: show running-config port-profile ms-nlb
!Time: Thu Feb 21 11:16:59 2013

version 5.2(1)SM1(5.1)
port-profile type vethernet ms-nlb
switchport mode access
switchport access vlan 59
no shutdown
guid 2402bb48-eb6d-4260-8891-8223fa000f5f
state enabled

switch(config-port-prof)#

Enabling MAC Spoofing

Use this procedure to enable MAC spoofing on a Hyper-V host using SCVMM.

Before You Begin

Note

Make sure that the Cisco Nexus 1000V is configured before you configure Microsoft NLB on Windows VMs.

- You are logged in to SCVMM.

- Unicast is the default Microsoft Network Load Balancing mode of operation.

- Microsoft NLB replaces the MAC address of each server in the host group to a common Microsoft NLB MAC address.

Procedure

Step 1

Create a Microsoft port profile.

1. In the Fabric pane, expand Networking, and then click Port Profiles.

2. On the Home tab, in the Create group, click Create, and then click Hyper-V Port Profile.

3. On the General page, enter a name and optional description for the port profile, click Virtual network adapter port profile, and then click Next.

4. On the Offload Settings page, select Enable virtual machine queue, and click Next.

5. On the Security Settings page, select Allow MAC spoofing and click Next.

6. Click Finish.

Step 2

Combine the Microsoft port profile created in the previous step with the Cisco Nexus 1000V port profile.

1. In the Fabric pane, expand Networking, and then click Logical Switch.

2. Select Nexus 1000V Logical Switch, click Virtual Ports, and then click Edit Port Classifications.

3. Select the Microsoft port profile and the Cisco Nexus 1000V port profile in the port classification.

Step 3

Attach the port classification created in the previous step to the VMs that have NLB configured.

Feature History for Microsoft Network Load Balancing for vEthernet

Feature Name

Releases

Feature Information

Network Load Balancing

5.2(1)SM1(5.1)

This feature was introduced

Chapter 7. Supporting Redundant Routing Protocols

This chapter contains the following sections:

- Information About Redundant Routing Protocols

- Guidelines and Limitations

- Feature History for Supporting Redundant Routing Protocol

Information About Redundant Routing Protocols

The Cisco Nexus 1000V implements a loop detection mechanism that is based on source and destination MAC addresses and drops packets that are coming in on uplink ports if the source MAC address is already present on a local vEthernet interface. As a result, such protocols as the Virtual Router Redundancy Protocol (VRRP), the Common Address Redundancy Protocol (CARP), the Hot Standby Router Protocol (HSRP), and other similar protocols fail on Virtual Machines (VMs) that are associated to the Cisco Nexus 1000V.

Disabling loop detection provides a flexible way of supporting these protocols on VMs that are associated to the Cisco Nexus 1000V. By disabling the loop detection mechanism, you can configure any combination of the above mentioned protocols on a port profile or a vEthernet interface. As a result, you can run multiple protocols on the same VM.

Guidelines and Limitations

Supporting the redundant routing protocols feature has the following configuration guidelines and limitations:

- A disabled loop detection configuration is not supported on PVLAN ports.

- A disabled loop detection configuration is not supported on the port security ports.

Configuring a vEthernet Interface to Support Redundant Routing Protocols

Use this procedure to configure a vEthernet interface to support redundant routing protocols.

Before You Begin

- You are logged in to the CLI in EXEC mode.

- You know which redundant routing protocol you want to disable.

- VM interfaces that carry such traffic should have "spoofing enabled" in the HyperV VM settings, if the VM sends traffic using multiple MAC addresses. For information about enabling MAC spoofing, see Enabling MAC Spoofing.

Procedure

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# interface vethernet interface-number

Enters the interface configuration mode for the specified vEthernet interface (from 1 to 1048575).

Step 3

switch(config-if)# disable-loop-detection { carp | hsrp | vrrp |custom-rp [src-mac-range s_mac end_mac] [dest-ip ip_address] [ip-proto no] [port port]}

Enables or disables the loop detection mechanism to support a redundant routing protocol on vEthernet interface.

- disable-loop-detection: Disables the loop detection mechanism.

- no disable-loop-detection: Enables the loop detection mechanism. This is the default configuration.

The protocols supported on a vEthernet interface include:

- carp - Common Address Redundancy Protocol

- custom-rp - User defined protocol

- hsrp - Hot Standby Router Protocol

- vrrp - Virtual Router Redundancy Protocol

The parameters for custom defined protocols include:

- src-mac-range - Source MAC address range for the user defined protocol.

- dest-ip - Destination IP address for the user defined protocol.

- ip-proto - IP protocol number for the user defined protocol.

- port - UDP or TCP destination port number for the user defined protocol.

Step 4

switch(config-if)# show running-config interface vethernet interface-number

(Optional)
Displays the interface status and information.

Step 5

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

(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

The following example shows how to configure a vEthernet interface to support VRRP, CERP, HSRP, and user defined protocols on a virtual machine:

switch# configure terminal
switch(config)# int veth5
switch(config-if)# disable-loop-detection carp
switch(config-if)# disable-loop-detection vrrp
switch(config-if)# disable-loop-detection hsrp
switch(config-if)# disable-loop-detection custom-rp dest-ip 224.0.0.12 port 2234
switch(config-if)# end
switch# show running-config interface vethernet 5
!Command: show running-config interface Vethernet5
!Time: Wed Feb 20 16:21:40 2013

version 5.2(1)SM1(5.1)

interface Vethernet5
no mac auto-static-learn

switch (config-if)#

Configuring a Port Profile to Support Redundant Routing Protocols

Use this procedure to configure a port profile to support redundant routing protocols. Use this procedure when the master in a master/slave relationship has lost connectivity, the slave has taken over the master role, and the original master is attempting to overtake the master role.

Note

If you configure a vEthernet Interface and a port profile to run multiple protocols on the same virtual machine, then the configuration on the vEthernet Interface overrides the configuration on the port profile.

Before You Begin

- You are logged in to the CLI in EXEC mode.

- You know which redundant routing protocol you want to disable.

Procedure

Command or Action

Purpose

Step 1

switch# configure terminal

Enters global configuration mode.

Step 2

switch(config)# port-profile name

Enters port profile configuration mode for the named port profile.

Step 3

switch(config-port-prof)# switchport mode {access | trunk}

Designates that the interface is to be used as a trunking port.

A trunk port transmits untagged packets for the native VLAN and transmits encapsulated, tagged packets for all other VLANs.

Step 4

switch(config-port-prof)# no shutdown

Administratively enables all ports in the profile.

Step 5

switch(config-port-prof)# disable-loop-detection { carp | hsrp | vrrp |custom-rp [ src-mac-range s_mac end_mac ] [ dest-ip ip_address ] [ ip-proto no ] [ port port ]}

Enables or disables the loop detection mechanism to support a redundant routing protocol on vEthernet interface.

- disable-loop-detection: Disables the loop detection mechanism.

- no disable-loop-detection: Enables the loop detection mechanism. This is the default configuration.

The protocols supported on a vEthernet interface include:

- carp - Common Address Redundancy Protocol

- custom-rp - User defined protocol

- hsrp - Hot Standby Router Protocol

- vrrp - Virtual Router Redundancy Protocol

The parameters for custom defined protocols include:

- src-mac-range - Source MAC address range for the user defined protocol.

- dest-ip - Destination IP address for the user defined protocol.

- ip-proto - IP protocol number for the user defined protocol.

- port - UDP or TCP destination port number for the user defined protocol.

Step 6

switch(config-port-prof)# show port-profile [ brief | expand-interface | usage ] [ name profile-name ]

(Optional)
Displays the configuration for verification.

Step 7

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

(Optional)
Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration.

This example shows how to disable loop detection for the Hot Standby Router Protocol:

switch# configure terminal
switch(config)# port-profile hsrp-1
switch(config-port-prof)# switchport mode trunk
switch(config-port-prof)# no shutdown
switch(config-port-prof)# disable-loop-detection hsrp
switch(config-port-prof)# state enabled
switch(config-port-prof)# show port-profile name hsrp-1
port-profile hsrp-1
type: Vethernet
description:
status: enabled
max-ports: 32
min-ports: 1
inherit:
config attributes:
switchport mode trunk
disable-loop-detection hsrp
no shutdown
evaluated config attributes:
switchport mode trunk
disable-loop-detection hsrp
no shutdown
assigned interfaces:
port-group:
system vlans: none
capability l3control: no
capability iscsi-multipath: no
capability vxlan: no
capability l3-vn-service: no
port-profile role: none
port-binding: static

switch(config-port-prof)#

This example shows how to disable loop detection for the Virtual Router Redundancy Protocol:

n1000v# configure terminal
switch(config)# port-profile vrrp-1
switch(config-port-prof)# switchport mode trunk
switch(config-port-prof)# no shutdown
switch(config-port-prof)# disable-loop-detection vrrp
switch(config-port-prof)# state enabled
switch(config-port-prof)# show port-profile name vrrp-1
port-profile vrrp-1
type: Vethernet
description:
status: enabled
max-ports: 32
min-ports: 1
inherit:
config attributes:
switchport mode trunk
disable-loop-detection vrrp
no shutdown
evaluated config attributes:
switchport mode trunk
disable-loop-detection vrrp
no shutdown
assigned interfaces:
port-group: vrrp-1
system vlans: none
capability l3control: no
capability iscsi-multipath: no
capability vxlan: no
capability l3-vservice: no
port-profile role: none
port-binding: static

Feature History for Supporting Redundant Routing Protocol

Feature Name

Releases

Feature Information

Supporting Redundant Routing Protocol

5.2(1)SM1(5.1)

This feature was introduced

Preface

The Preface contains the following sections:

- Audience

- Document Conventions

- Related Documentation for Cisco Nexus 1000V for Microsoft Hyper-V Software

- Documentation Feedback

- Obtaining Documentation and Submitting a Service Request

Audience

This publication is for network administrators who configure and maintain Cisco Nexus devices.

This guide is for network and server administrators with the following experience and knowledge:

- An understanding of virtualization

- An understanding of the corresponding hypervisor management software for your switch, such as VMware vSwitch, Microsoft System Center Virtual Machine Manager (SCVMM), or OpenStack.

Document Conventions

Command descriptions use the following conventions:

Convention

Description

bold

Bold text indicates the commands and keywords that you enter literally as shown.

Italic

Italic text indicates arguments for which the user supplies the values.

[x]

Square brackets enclose an optional element (keyword or argument).

[x | y]

Square brackets enclosing keywords or arguments separated by a vertical bar indicate an optional choice.

{x | y}

Braces enclosing keywords or arguments separated by a vertical bar indicate a required choice.

[x {y | z}]

Nested set of square brackets or braces indicate optional or required choices within optional or required elements. Braces and a vertical bar within square brackets indicate a required choice within an optional element.

variable

Indicates a variable for which you supply values, in context where italics cannot be used.

string

A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

Examples use the following conventions:

Convention

Description

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.

This document uses the following conventions:

Note

Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual.

Caution

Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Related Documentation for Cisco Nexus 1000V for Microsoft Hyper-V Software

This section lists the documents used with the Cisco Nexus 1000V for Microsoft Hyper-V software:

General Information

Cisco Nexus 1000V for Microsoft Hyper-V Release Notes

Install and Upgrade

Cisco Nexus 1000V for Microsoft Hyper-V Installation and Upgrade Guide

Configuration Guides

Cisco Nexus 1000V for Microsoft Hyper-V High Availability and Redundancy Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Interface Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Layer 2 Switching Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V License Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Network Segmentation Manager Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Port Profile Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Quality of Service Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Security Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V System Management Configuration Guide

Cisco Nexus 1000V for Microsoft Hyper-V Verified Scalability Guide

Reference Guides

Cisco Nexus 1000V for Microsoft Hyper-V Command Reference

Troubleshooting and Alerts

Cisco Nexus 1000V for Microsoft Hyper-V Troubleshooting Guide

Documentation Feedback

To provide technical feedback on this document, or to report an error or omission, please send your comments to: ciscodfa-docfeedback@cisco.com.

We appreciate your feedback.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation, at: Click Here .

Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.

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 UCB's 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 THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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 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: Click Here . 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. (1110R)