P Commands
This chapter describes the Cisco NX-OS virtual port channel (vPC) commands that begin with P.
peer-config-check-bypass
To ignore type checks on the primary vPC device when the multichassis EtherChannel trunk (MCT) is down, use the peer-config-check-bypass command. To stop ignoring type checks, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The peer link, also known as the multichassis EtherChannel trunk (MCT), connects the vPC peer switches. The peer link is always forwarding. The bridge protocol data units (BPDUs) or Link Aggregation Control Protocol (LACP) packets that are received by the secondary vPC peer on a vPC port are forwarded to the primary vPC peer through the peer link for processing.
The peer link is used to synchronize the MAC addresses of the vPC peer switches to provide the necessary transport for multicast traffic. It is also used for forwarding traffic that originates at, or is destined for, orphan ports (that is, a non-vPC port).
Examples
This example shows how to configure the primary vPC device to ignore type checks when the MCT is down:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
Displays information about the configuration for the keepalive messages. |
peer-gateway
To enable Layer 3 forwarding for packets destined to the gateway MAC address of the virtual Port Channel (vPC), use the peer-gateway command. To disable Layer 3 forwarding packets, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The vPC peer-gateway functionality allows a vPC switch to act as the active gateway for packets that are addressed to the router MAC address of the vPC peer. This feature enables local forwarding of such packets without the need to cross the vPC peer-link. In this scenario, the feature optimizes use of the peer-link and avoids potential traffic loss.
You must configure the peer-gateway functionality on both vPC peer switches.
Note
This command is applicable to a Cisco Nexus 5548 switch and Cisco Nexus 5596 switch.
Examples
This example shows how to enable the vPC peer gateway:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
peer-keepalive
To configure the IPv4 address for the remote end of the vPC peer keepalive link that carries the keepalive messages, use the peer-keepalive command. To disassociate the peer keepalive link, use the no form of this command.
peer-keepalive destination ipv4_address [ hold-timeout holdtime_seconds | interval mseconds { timeout seconds } | { precedence { prec_value | critical | flash | flash-override | immediate | internet | network | priority | routine }} | source ipv4_address | tos { tos_value | max-reliability | max-throughput | min-delay | min-monetary-cost | normal } | tos-byte tos_byte_value | udp-port udp_port | vrf { vrf_name | management }]
no peer-keepalive destination ipv4_address [ hold-timeout holdtime_seconds | interval mseconds { timeout seconds } | { precedence { prec_value | critical | flash | flash-override | immediate | internet | network | priority | routine }} | source ipv4_address | tos { tos_value | max-reliability | max-throughput | min-delay | min-monetary-cost | normal } | tos-byte tos_byte_value | udp-port udp_port | vrf { vrf_name | management }]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
You must configure the vPC peer-keepalive link before the system can form the vPC peer link. Ensure that both the source and destination IP addresses used for the peer-keepalive message are unique in your network and these IP addresses are reachable from the Virtual Routing and Forwarding (VRF) associated with the vPC peer-keepalive link.
The Cisco NX-OS software uses the peer-keepalive link between the vPC peers to transmit periodic, configurable keepalive messages. You must have Layer 3 connectivity between the peer devices to transmit these messages. The system cannot bring up the vPC peer link unless the peer-keepalive link is already up and running.
Note We recommend that you configure a separate VRF instance and put a Layer 3 port from each vPC peer device into that VRF for the vPC peer-keepalive link. Do not use the peer link itself to send vPC peer-keepalive messages.
Examples
This example shows how to set up the peer keepalive link connection between the primary and secondary vPC device:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
Displays information about the configuration for the keepalive messages. |
port-profile
To create or configure a port profile, use the port-profile command. To delete a port profile, use the no form of this command.
port-profile { port-profile-name | type { ethernet | interface-vlan | port-channel | vethernet } port-profile-name }
no port-profile { port-profile-name | type { ethernet | interface-vlan | port-channel | vethernet } port-profile-name }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Note ● You must enable virtual interfaces on the switch by using the feature-set virtualization command to see the vethernet keyword.
- You must enable interface VLANs by using the feature interface-vlan command to see the interface-vlan keyword.
You can create a port profile that contains a batch of repetitive interface commands and apply that port profile to a range of interfaces on the switch. You can configure and apply port profiles to the following interface types:
The port profile is configured for an interface so that the commands that are applicable to one interface do not show up when you configure a port profile for another interface. For example, the commands that are applicable to port channel interfaces do not show up when you configure a port profile that is attached to an Ethernet interface.
Each port profile must have a unique name across the interface types.
When you delete a port profile, the commands that are configured within the port profile are removed from the interfaces that have inherited the port profile. If you want to delete a port profile that has been inherited by other port profiles, you must remove the inheritance before you can delete the port profile.
Examples
This example shows how to create a port profile named ppEth for Ethernet interfaces:
This example shows how to create a port profile named ppVEth for virtual Ethernet interfaces:
This example shows how to delete an Ethernet type port profile named ppEth:
Related Commands
|
|
|
|---|---|
Copies the running configuration to the startup configuration. |
|
Displays the running configuration information for a port profile. |
Feedback