Usage Guidelines

Typically, you configure 802.1Q trunks with a native VLAN ID, which strips tagging from all packets on that VLAN and allows all untagged traffic and control traffic to transit the switch. Packets that enter the switch with 802.1Q tags that match the native VLAN ID value are similarly stripped of tagging. If you choose to maintain the tagging on the native VLAN and drop untagged traffic, enter the vlan dot1q tag native command.

Use the vlan dot1q tag native command to configure the switch to tag the traffic received on the native VLAN and to admit only the 802.1Q-tagged frame, dropping any untagged traffic, including untagged traffic in the native VLAN. Control traffic continues to be accepted untagged on the native VLAN on a trunked port, when the vlan dot1q tag native command is enabled.

Note	If you enable 802.1Q tagging on one switch and disable it on another switch, all traffic is dropped; you must identically configure 802.1Q tagging on each switch.

To exclude untagged control traffic but include tagged data traffic, use the vlan dot1q tag native exclude control command .

The no vlan dot1q tag native exclude control command specifies that both control and data traffic will egress the trunk port as untagged.

Note	The vlan dot1q tag native command applies only to trunk ports.

This command does not require a license.

Usage Guidelines

You must enable the vPC feature before you can create a vPC.

Once you have created the vPC domain ID and the vPC peer link, you create port channels to attach the downstream device to each vPC peer device. That is, you create one port channel from the downstream device to the primary vPC peer device and you create another port channel from the downstream device to the secondary peer device. Finally, working on each vPC peer device, you assign a vPC number to the port channel that connects to the downstream device. You will experience minimal traffic disruption when you are creating vPCs.

Note	The vPC number that you assign to the port channel connecting to the downstream device from the vPC peer device must be identical on both vPC peer devices.

This command does not require a license.

Usage Guidelines

Use the vpc config-sync re-merge command if the current state of the configuration is not synchronized. The options are as follows:

• Use the vpc config-sync re-merge sync {export | import } command to synchronize the configuration with the peer switch.

• Use the vpc config-sync re-merge sync interface ethernet slot/port {export | import } command to synchronize the physical port configuration.

• Use the vpc config-sync re-merge sync port-channel channel-number {export | import } command to synchronize the port channel configuration.

This command does not require a license.

Usage Guidelines

You must enable the vPC feature before you can create a vPC domain.

You put all vPC interfaces, including the vPC peer link, on both of the vPC peer devices into the identical vPC domain. You must have unique vPC domain numbers within each VDC. In Cisco NX-OS Release 4.1(3), you can have only one vPC per VDC. Once you create a vPC domain, the system automatically creates a vPC system MAC address that is unique to that vPC.

You also use this command to enter the vpc-domain command mode in order to configure vPC parameters.

This command does not require a license.

Usage Guidelines

You can use the vpc orphan-ports suspend command only on physical ports.

Note	You can configure vPC orphan port suspension only on physical ports, not on port channel member ports.

The term “orphaned ports” refers to switch ports connected to single-attached hosts, or vPC ports whose members are all connected to a single vPC peer in a vPC VLAN. End-host can either be attached to a single vPC switch or connected to a vPC pair of switches in an active-standby mode with orphan ports. When a vPC peer-link goes down, while the peer-keepalive link is up, vPC secondary switch suspends all its vPC ports. All the interface VLANs for the vPC VLAN are also brought down during this process. However, orphan ports attached to the vPC secondary switch are not suspended. This may cause traffic disruption for the hosts connected to orphan ports as there is no Layer 3 connectivity for end host through the secondary switch. To suspend the vPC orphan ports along with the vPC ports, use the vpc orphan-ports suspend command in interface-configuration mode. The vpc orphan-ports suspend command can be configured on an orphan port that needs to be disconnected from the secondary-operational switch when the vPC peer-link fails.

This command does not require a license.

Usage Guidelines

You must enable the vPC feature before you can create a vPC peer link.

You configure a port channel using 10-Gigabit Ethernet ports on the N7K-M132XP-12 module. We recommend that you use the 10-Gigabit Ethernet ports for the channel in dedicated mode and configure at least two of these ports on two different modules into the port channel for redundancy.

Use the vpc peer-link command to make that port channel a vPC peer link. The system returns an error message if you attempt to configure a 1-Gigabit Ethernet interface as a vPC peer link.

After you configure the vPC peer device and the vPC peer link is established, the system creates a new MAC address for the vPC and decides which vPC device is the primary device and which is the secondary device.

This command does not require a license.

Usage Guidelines

The vpc sync command triggers a configuration merge between the primary and secondary switches if the current merge state is failed (for example, there is an interface configuration conflict between the port channels).

This command does not require a license.