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 S.
To enable a port profile, use the state enabled command. To disable a port profile, use the no form of this command.
Port profile configuration mode
|
|
---|---|
Use this command to enable a port profile to apply the port profile configurations to the interfaces. You can configure and inherit a port profile onto a range of interfaces before you enable that port profile. You must then enable that port profile for the configurations to take effect on the specified interfaces.
This example shows how to enable a port profile named ppEth that is configured for Ethernet interfaces:
This example shows how to disable a port profile named ppEth that is configured for Ethernet interfaces:
|
|
---|---|
Copies the running configuration to the startup configuration. |
|
To create or configure a switch profile, use the switch-profile command. To delete a switch profile, use the no form of this command.
switch-profile sw-profile-name
no switch-profile sw-profile-name { all-config | local-config }
Configuration synchronization mode
|
|
---|---|
Use this command to create a switch profile on each of the peer switches. You must use the same profile name on both the switches in the Cisco Fabric Services (CFS) peer configuration.
Note In this release of Cisco NX-OS, only a pair of switches can be configured as a peer.
You can configure only one active switch profile on each peer switch. If you create or configure a second switch profile, you see the following error message:
The configuration that is made locally on the switch is synchronized and made available on the peer switch only after the connectivity is established between the peer switches and the configuration is verified and committed on the local switch.
You can configure a switch profile to include the interface configuration, quality of service (QoS), and virtual port channel (vPC) commands. FCoE commands are not supported on a switch profile.
When you delete a switch profile, you can choose to delete the local switch profile with the local configurations on the switch, or delete the switch profile with the local configurations and configuration information in the peer. The peer becomes unreachable.
This example shows how to create a switch profile named s6000 on switch 1 of the peer:
This example shows how to create a switch profile named s6000 on switch 2 of the peer:
This example shows how to delete a switch profile named s6000 and its local configuration on switch 1 of the peer:
|
|
---|---|
Displays the switch profile created on the switch and its configuration revision. |
|
Configures the peer switch for configuration synchronization. |
To add a peer switch to a switch profile, use the sync-peers destination command. To remove a peer from the switch profile, use the no form of this command.
sync-peers destination ipv4-address
no sync-peers destination ipv4-address
Destination IPv4 address of the peer switch in the format A. B. C. D. |
Switch profile configuration mode
|
|
---|---|
Use this command to add the peer switch that will be included in the synchronization. You must have the IPv4 address of the peer switch. You can ensure that configuration synchronization is enabled on the peer switch by using the config sync command.
After you add a peer to a switch profile, you can add commands to the switch profile.
Peers maintain a configuration revision of their local configuration as well as the revision. After a network outage, when connectivity is established between the peer switches and the peers are reachable, each peer determines if any configuration in the switch needs to be synchronized with the other peer. Changed configurations will then be synchronized between the peers.
When you remove a peer from the switch profile, all configuration information about the peer is deleted from the local switch.
This example shows how to add a peer switch with IPv4 address 192.0.2.37 to a switch profile named s6000 on switch 1 of the peer:
This example shows how to add a peer switch with IPv4 address 192.0.2.3 to a switch profile named s6000 on switch 2 of the peer:
This example shows how to delete a peer with IPv4 address 192.0.2.37 from a switch profile named s6000 on switch 1 of the peer:
To manually configure the virtual port channel (vPC) domain MAC address, use the system-mac command. To restore the default vPC system MAC address, use the no form of this command.
MAC address that you want for the specified vPC domain in the following format aaaa.bbbb.cccc. |
|
|
---|---|
When you create a vPC domain, the Cisco NX-OS software automatically creates a vPC system MAC address, which is used for operations that are confined to the link-scope, such as the Link Aggregation Control Protocol (LACP). However, you may choose to configure the vPC domain MAC address manually.
This example shows how to configure the MAC address for the vPC domain:
|
|
---|---|
Copies the running configuration to the startup configuration. |
|
Displays information about the configuration for the keepalive messages. |
To manually configure a system priority for the virtual port channel (vPC) domain, use the system-priority command. To restore the default system priority, use the no form of this command.
system-priority priority_value
no system-priority priority_value
System priority that you want for the specified vPC domain. The range is from 1 to 65535, and the default value is 32667. |
|
|
---|---|
We recommend that you manually configure the vPC system priority when you are running Link Aggregation Control Protocol (LACP) to ensure that the vPC peer devices are the primary devices on LACP. When you manually configure the system priority, ensure that you configure the same priority value on both vPC peer devices. If these values do not match, vPC will not come up.
This example shows how to configure the system priority for the vPC domain:
|
|
---|---|
Copies the running configuration to the startup configuration. |
|