The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco NX-OS virtual port channel (vPC) commands that begin with I.
To import an interface configuration to a switch profile, use the import interface command.
import interface { ethernet s lot /[ QSFP-module /] port | port-channel channel-no }
Switch profile configuration mode
|
|
---|---|
When no option is specified with the import command, an empty switch profile is created. You can then selectively add the configuration that is needed to be synchronized with the peer switch.
You can import a switch profile based on the set of commands that you want to import. The following three ways can be used to import commands that were added using the configuration terminal mode:
1. Add selected commands to the switch profile.
2. Add supported commands that were specified for an interface.
3. Add supported system-level commands.
When you import commands to a switch profile, the switch profile buffer must be empty.
Use the commit command to complete the import process and move the configuration into the switch profile. Because configuration changes are not supported during the import process, if new commands are added before entering the commit command, the switch profile remains unsaved and the switch remains in the switch profile import mode (config-sync-sp-import). You can remove the added commands or use the abort command to stop the import. Unsaved configurations are lost if the process is aborted. New commands can be added to the switch profile after the import is complete.
This example shows how to import the Ethernet interface configuration to a switch profile named s5010 on switch 1 of the peer:
This example shows how to create an empty switch profile named sp100 on switch 1 of the peer and then add the configuration commands:
This example shows how to import an interface in a switch profile:
|
|
---|---|
Copies the running configuration to the startup configuration. |
|
To import the running configuration to a switch profile, use the import running-config command.
import running-config [ exclude interface ethernet ]
Switch profile configuration mode
|
|
---|---|
The import running-config exclude interface ethernet command discards all physical interface commands in the running configuration during the import operation.
When no option is specified with the import command, an empty switch profile is created. You can then selectively add the configuration that is needed to be synchronized with the peer switch.
You can import a switch profile based on the set of commands that you want to import. The following three ways can be used to import commands that were added using the configuration terminal mode:
1. Add selected commands to the switch profile.
2. Add supported commands that were specified for an interface.
3. Add supported system-level commands.
When you import commands to a switch profile, the switch profile buffer must be empty.
Use the commit command to complete the import process and move the configuration into the switch profile. Because configuration changes are not supported during the import process, if new commands are added before entering the commit command, the switch profile remains unsaved and the switch remains in the switch profile import mode (config-sync-sp-import). You can remove the added commands or use the abort command to stop the import. Unsaved configurations are lost if the process is aborted. New commands can be added to the switch profile after the import is complete.
This example shows how to import the running configuration to a switch profile named s5010 on switch 1 of the peer:
|
|
---|---|
Copies the running configuration to the startup configuration. |
|
To inherit a port profile into an existing profile or to apply a port profile configuration to an interface, use the inherit port-profile command. To remove the inheritance, use the no form of this command.
inherit port-profile port-profile-name
no inherit port-profile port-profile-name
Name of the port profile. The name is case sensitive, can be a maximum of 80 alphanumeric characters and can include an underscore and hyphen. The name cannot contain spaces or special characters. |
Port profile configuration mode
Interface configuration mode
Virtual Ethernet interface configuration mode
|
|
---|---|
You inherit the port profile when you attach the port profile to an interface or range of interfaces. When you attach, or inherit, a port profile to an interface or range of interfaces, the switch applies all the commands in that port profile to the interfaces. A port profile configured for an interface type can be applied only to that type of interface. For example, a port profile created for VLAN interfaces must be attached onto a VLAN interface. If you delete a port profile after you attach the port profile to an interface, the port profile configuration is removed from the interface.
To apply the port profile configurations to the interfaces, you must enable the specific port profile.
This example shows how to inherit a port profile named ppEth that is configured for Ethernet interfaces into an existing port profile named test:
This example shows how to assign a port profile named ppEth that is configured for Ethernet interfaces to a range of Ethernet interfaces:
This example shows how to assign a port profile named ppVEth that is configured for virtual Ethernet interfaces to a virtual Ethernet interface:
This example shows how to remove an inherited port profile named ppEth from an existing port profile named test:
|
|
---|---|
Copies the running configuration to the startup configuration. |
|
To enable Address Resolution Protocol (ARP) synchronization between the virtual port channel (vPC) peers, use the ip arp synchronize comand. To disable ARP synchronization, use the no form of this command.
|
|
---|---|
The ARP table sync feature overcomes the delay involved in ARP table restoration that can be triggered when one of the switches in the vPC domain goes offline and comes back online and also when there are peer-link port channel flaps. Enabling ARP on a vPC domain improves convergence times for unicast traffic.
This example shows how to enable ARP synchronization on a vPC domain:
This example shows how to disable ARP synchronization on a vPC domain:
|
|
---|---|
To configure a static connection to a virtual port channel (vPC) peer link, use the ip igmp snooping mrouter vpc-peer-link command. To remove the static connection, use the no form of this command.
ip igmp snooping mrouter vpc-peer-link
no ip igmp snooping mrouter vpc-peer-link
|
|
By default, a vPC Peer-link is considered an IGMP snooping mrouter port. The multicast traffic is sent over to a peer-link for the source VLAN and for each receiving VLAN. If you use the no ip igmp snooping mrouter vpc-peer-link command, the multicast traffic is not sent over to a peer-link for the source VLAN and receiver VLAN unless there are orphan ports in the VLAN.
Note In Cisco NX-OS Release 5.0(3)N1(1), the no ip igmp snooping mrouter vpc-peer-link command is not supported in topologies where there is a dual-homed Cisco Nexus 2000 Series Fabric Extender attached to a Cisco Nexus 5000 Series switch.
This example shows how to configure a static connection to a vPC peer link:
switch(
config)#
ip igmp snooping mrouter vpc-peer-link
switch(
config)#
This example shows how to remove a static connection to a vPC peer link:
switch(
config)#
no ip igmp snooping mrouter vpc-peer-link
Warning: IGMP Snooping mrouter vpc-peer-link should be globally disabled on peer
VPC switch as well.
switch(
config)#
|
|
---|---|