Cisco Nexus 5000 Series Nx-Os System Management Configuration Guide, Release 5.2(1)N1(1 - Cisco Nexus 5000 Series Configuration Manual
System management configuration guide
Hide thumbs
Also See for Nexus 5000 Series:
- Cli configuration manual (660 pages) ,
- Configuration manual (334 pages) ,
- Command reference manual (196 pages)
Table of Contents
Advertisement
Configuring Switch Profiles
• Supported command changes made from the configuration terminal mode are blocked when a switch
profile session is in progress. You should not make unsupported command changes from the configuration
terminal mode when a switch profile session is in progress.
• When you enter the commit command and a peer switch is reachable, the configuration is applied to
both peer switches or neither switch. If there is a commit failure, the commands remain in the switch
profile buffer. You can then make necessary corrections and try the commit again.
• Cisco recommends that you enable pre-provisioning for all Generic Expansion Modules (GEMs) and
Cisco Nexus Fabric Extender modules whose interface configurations are synchronized using the
configuration synchronization feature. Follow these guidelines in Cisco Nexus Fabric Extender
active/active topologies where the Fabric Extenders might not be online on one switch and its
configuration is changed and synchronized on the other switch. In this scenario, if you do not enable
pre-provisioning, a commit fails and the configuration is rolled back on both switches.
• Once a port channel is configured using switch profile mode, it cannot be configured using global
configuration (config terminal) mode.
Note
• Shutdown and no shutdown can be configured in either global configuration mode or switch profile
mode.
• If a port channel is created in global configuration mode, channel groups including member interfaces
must also be created using global configuration mode.
• Port channels that are configured within switch profile mode may have members both inside and outside
of a switch profile.
• If you want to import a member interface to a switch profile, the port channel including the member
interface must also be present within the switch profile.
Guidelines for Synchronizing After Reboot, Connectivity Loss, or Failure
• Synchronizing configurations after vPC peer link failure— If both switches are operational when a
peer-link fails, the secondary switch shuts down its vPC ports. In a fabric extender A/A topology, the
A/A fabric extender disconnects from the secondary switch. If the configuration is changed using a
switch profile on the primary switch, configurations are not accepted on the secondary switch unless
the A/A fabric extender is pre-provisioned. When using the configuration synchronization feature, we
recommend that you pre-provision all A/A fabric extenders.
• Synchronizing configurations after mgmt0 interface connectivity loss—When mgmt0 interface
connectivity is lost and configuration changes are required, apply the configuration changes on both
switches using the switch profile. When connectivity to the mgmt0 interface is restored, both switches
synchronize automatically.
Several port channel sub-commands are not configurable in switch profile mode. These
commands can be configured from global configuration mode even if the port channel
is created and configured in switch profile mode.
For example, the following command can only be configured in global configuration
mode:
switchport private-vlan association trunk primary-vlan secondary-vlan
Cisco Nexus 5000 Series NX-OS System Management Configuration Guide, Release 5.2(1)N1(1)
Guidelines and Limitations for Switch Profiles
11
Advertisement
Table of Contents
