Configuration Validation - Cisco Nexus 5000 Series Configuration Manual

System management configuration guide
Hide thumbs Also See for Nexus 5000 Series:
Table of Contents

Advertisement

Configuring Switch Profiles
Because different topologies require different commands that are included in a switch profile, the import
command mode allows you to modify the imported set of commands to suit a specific topology. For example,
a dual homed Fabric Extender (FEX) topology requires that most of the configuration is synchronized. In
other vPC topologies, the configuration that needs to be synchronized might be a much smaller set of commands.
You need to enter 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 you added new
commands before entering the commit command, the switch profile remains unsaved and the switch remains
in the switch profile import mode. You can remove the added commands or abort the import. Unsaved
configurations are lost if the process is aborted. You can add new commands to the switch profile after the
import is complete.

Configuration Validation

Two types of configuration validation checks can identify two types of switch profile failures:
• Mutual Exclusion Checks
• Merge Checks
Mutual Exclusion Checks
To reduce the possibility of overriding configuration settings that are included in a switch profile, mutual
exclusion (mutex) checks the switch profile commands against the commands that exist on the local switch
and the commands on the peer switch. A command that is included in a switch profile cannot be configured
outside of the switch profile or on a peer switch. This requirement reduces the possibility that an existing
command is unintentionally overwritten.
As a part of the commit process, the mutex-check occurs on both switches if the peer switch is reachable;
otherwise, the mutex-check is performed locally. Configuration changes made from the configuration terminal
occur only on the local switch.
If a mutex-check identifies errors, they are reported as mutex failures and they must be manually corrected.
The following exceptions apply to the mutual exclusion policy:
• Interface configuration—Prior to release 5.1(3), an interface configuration could be partially present in
• Shutdown/no shutdown
• System QoS
a switch profile and partially present in the running configuration as long as there were no conflicts.
Starting in release 5.1(3), port channel interfaces must be configured fully in either switch profile mode
or global configuration mode.
Several port channel sub-commands are not configurable in switch profile mode. These
Note
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)
Configuration Validation
9

Advertisement

Table of Contents
loading

Table of Contents