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.
To enable debugging of the stack manager software, use the debug platform stack-manager command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug platform stack-manager { all | rpc | sdp | sim | ssm | trace }
no debug platform stack-manager { all | rpc | sdp | sim | ssm | trace }
all |
Displays all stack manager debug messages. |
rpc |
Displays stack manager remote procedure call (RPC) usage debug messages. |
sdp |
Displays the Stack Discovery Protocol (SDP) debug messages. |
sim |
Displays the stack information module debug messages. |
ssm |
Displays the stack state-machine debug messages. |
trace |
Traces the stack manager entry and exit debug messages. |
Debugging is disabled.
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This command is supported only on stacking-capable switches.
The undebug platform stack-manager command is the same as the no debug platform stack-manager command.
When you enable debugging on a switch stack, it is enabled only on the stack master. To enable debugging on a stack member, you can start a session from the stack master by using the session switch-number EXEC command. Enter the debug command at the command-line prompt of the stack member. You also can use the remote command stack-member-number LINE EXEC command on the stack master switch to enable debugging on a member switch without first starting a session.
To enter the redundancy main configuration submode and enable the standby switch, use the main-cpu command in redundancy configuration mode.
main-cpu
This command has no arguments or keywords.
None
Redundancy configuration
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
From the redundancy main configuration submode, use the standby console enable command to enable the standby switch.
This example shows how to enter the redundancy main configuration submode and enable the standby switch:
Controller(config)# redundancy Controller(config-red)# main-cpu Controller(config-r-mc)# standby console enable Controller#
Command |
Description |
Enables access to the standby console switch. |
To set the redundancy mode to stateful switchover (SSO), use the mode sso command in redundancy configuration mode.
mode sso
This command has no arguments or keywords.
None
Redundancy configuration
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
The mode sso command can be entered only from within redundancy configuration mode.
Follow these guidelines when configuring your system to SSO mode:
This example shows how to set the redundancy mode to SSO:
Controller(config)# redundancy Controller(config-red)# mode sso Controller(config-red)#
To reload the standby switch if a parser return code (PRC) failure occurs during configuration synchronization, use the policy config-sync reload command in redundancy configuration mode. To specify that the standby switch is not reloaded if a parser return code (PRC) failure occurs, use the no form of this command.
policy config-sync { bulk | lbl } prc reload
no policy config-sync { bulk | lbl } prc reload
bulk | Specifies bulk configuration mode. |
lbl | Specifies line-by-line (lbl) configuration mode. |
The command is enabled by default.
Redundancy configuration
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This example shows how to specify that the standby switch is not reloaded if a parser return code (PRC) failure occurs during configuration synchronization:
Controller(config-red)# no policy config-sync bulk prc reload
To enter redundancy configuration mode, use the redundancy command in global configuration mode.
redundancy
This command has no arguments or keywords.
None
Global configuration
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
The redundancy configuration mode is used to enter the main CPU submode, which is used to enable the standby switch.
To enter the main CPU submode, use the main-cpu command while in redundancy configuration mode.
From the main CPU submode, use the standby console enable command to enable the standby switch.
Use the no command to disable redundancy. If you disable redundancy and then reenable it, the switch returns to default redundancy settings.
Use the exit command to exit redundancy configuration mode.
This example shows how to enter redundancy configuration mode:
Controller(config)# redundancy Controller(config-red)#
This example shows how to enter the main CPU submode:
Controller(config)# redundancy Controller(config-red)# main-cpu Controller(config-r-mc)#
To allow the standby switch to join the stack if a configuration mismatch occurs between the active and standby switches, use the redundancy config-sync mismatched-commands command in privileged EXEC mode.
redundancy config-sync { ignore | validate } mismatched-commands
ignore | Ignores the mismatched command list. |
validate | Revalidates the mismatched command list with the modified running-configuration. |
None
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
If the command syntax check in the running configuration of the active switch fails while the standby switch is booting, use the redundancy config-sync mismatched-commands command to display the Mismatched Command List (MCL) on the active switch and to reboot the standby switch.
The following is a log entry example for mismatched commands:
00:06:31: Config Sync: Bulk-sync failure due to Servicing Incompatibility. Please check full list of mismatched commands via: show redundancy config-sync failures mcl 00:06:31: Config Sync: Starting lines from MCL file: interface GigabitEthernet7/7 ! <submode> "interface" - ip address 192.0.2.0 255.255.255.0 ! </submode> "interface"
To display all mismatched commands, use the show redundancy config-sync failures mcl command.
To clean the MCL, follow these steps:
You can ignore the MCL by doing the following:
Note |
If you ignore the mismatched commands, the out-of-sync configuration at the active switch and the standby switch still exists. |
If SSO mode cannot be established between the active and standby switches because of an incompatibility in the configuration file, a mismatched command list (MCL) is generated at the active switch and a reload into route processor redundancy (RPR) mode is forced for the standby switch.
Note |
RPR mode is supported on Catalyst 3850 switches as a fallback in case of errors. It is not configurable. |
If you attempt to establish an SSO after removing the offending configuration and rebooting the standby switch with the same image, the C3K_REDUNDANCY-2-IOS_VERSION_CHECK_FAIL and ISSU-3-PEER_IMAGE_INCOMPATIBLE messages appear because the peer image is listed as incompatible. You can clear the peer image from the incompatible list with the redundancy config-sync ignore mismatched-commands EXEC command while the peer is in a standby cold (RPR) state. This action allows the standby switch to boot in a standby hot (SSO) state when it reloads.
This example shows how to revalidate the mismatched command list with the modified configuration:
Controller# redundancy config-sync validate mismatched-commands Controller#
To force a switchover from the active switch to the standby switch, use the redundancy force-switchover command in privileged EXEC mode on a switch stack.
redundancy force-switchover
This command has no arguments or keywords.
None
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
Use the redundancy force-switchover command to manually switch over to the redundant switch. The redundant switch becomes the new active switch that runs the Cisco IOS image, and the modules are reset to their default settings.
The old active switch reboots with the new image and joins the stack.
If you use the redundancy force-switchover command on the active switch, the switchports on the active switch to go down.
If you use this command on a switch that is in a partial ring stack, the following warning message appears:
Controller# redundancy force-switchover
Stack is in Half ring setup; Reloading a switch might cause stack split
This will reload the active unit and force switchover to standby[confirm]
This example shows how to manually switch over from the active to the standby supervisor engine:
Controller# redundancy force-switchover Controller#
To force a reload of one or all of the switches in the stack, use the redundancy reload command in privileged EXEC mode.
redundancy reload { peer | shelf }
peer | Reloads the peer unit. |
shelf | Reboots all switches in the stack. |
None
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
Before using this command, see the “Performing a Software Upgrade” section of the Stack Manager Configuration Guide (Platform—Cisco WLC 5700 Series) for additional information.
Use the redundancy reload shelf command to reboot all the switches in the stack.
This example shows how to manually reload all switches in the stack:
Controller# redundancy reload shelf Controller#
To reload the stack member and to apply a configuration change, use the reload command in privileged EXEC mode.
reload [ /noverify | /verify ] [ LINE | at | cancel | in | slot stack-member-number | standby-cpu ]
/noverify |
(Optional) Specifies to not verify the file signature before the reload. |
/verify |
(Optional) Verifies the file signature before the reload. |
LINE |
(Optional) Reason for the reload. |
at |
(Optional) Specifies the time in hh:mm for the reload to occur. |
cancel |
(Optional) Cancels the pending reload. |
in |
(Optional) Specifies a time interval for reloads to occur. |
slot |
(Optional) Saves the changes on the specified stack member and then restarts it. |
stack-member-number |
|
standby-cpu |
(Optional) Reloads the standby route processor (RP). |
Immediately reloads the stack member and puts a configuration change into effect.
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
If there is more than one switch in the switch stack, and you enter the reload slot stack-member-number command, you are not prompted to save the configuration.
This example shows how to reload the switch stack:
Controller# reload
System configuration has been modified. Save? [yes/no]: y
Proceed to reload the whole Stack? [confirm] y
This example shows how to reload a specific stack member:
Controller# reload slot 6
Proceed with reload? [confirm] y
This example shows how to reload a single-switch switch stack (there is only one member switch):
Controller# reload slot 3
System configuration has been modified. Save? [yes/no]: y
Proceed to reload the whole Stack? [confirm] y
Command |
Description |
Displays information related to the stack member or the switch stack. |
|
Changes the stack member priority value. |
|
Changes the stack member number. |
To access a specific stack member use the session command in privileged EXEC mode on the stack master.
session stack-member-number
stack-member-number |
Stack member number to access from the . |
None
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
When you access the member, its member number is appended to the system prompt.
Use the session command from the master to access a member Controller
Use the session command with processor 1 from the master or a standalone switch to access the internal controller. A standalone Controller is always member 1.
This example shows how to access stack member 3:
Controller# session 3 Controller-3#
Command |
Description |
Reloads the stack member and applies a configuration change. |
|
Displays information related to the stack member or the switch stack. |
|
Changes the stack member priority value. |
|
Changes the stack member number. |
To trace the control and provisioning of wireless access point high availability, use the set trace capwap ap ha command.
set trace capwap ap ha [ detail | event | dump | | { filter [ none [ switch switch ] | filter_name [ filter_value [ switch switch ] ] ] | filtered switch level { default | trace_level } [ switch switch ] } ]
detail | (Optional) Specifies the wireless CAPWAP HA details. |
event | (Optional) Specifies the wireless CAPWAP HA events. |
dump | (Optional) Specifies the wireless CAPWAP HA output. |
filter mac | Specifies the MAC address. |
switch switch number | Specifies the switch number. |
none | (Optional) Specifies the no filter option. |
switch switch | (Optional) Specifies the controller number. |
filter name | Trace adapted flag filter name. |
filter_value | (Optional) Value of the filter. |
switch switch | (Optional) Specifies the controller number. |
filtered | Specifies the filtered traces messages. |
switch | Specifies the switch number. |
level | Specifies the trace level. |
default | Specifies the unset trace level value. |
trace_level | Specifies the trace level. |
switch switch | (Optional) Specifies the controller number. |
None
Any command mode
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This example shows how to display the wireless CAPWAP HA:
Controller# set trace capwap ap ha detail filter mac WORD switch number
To debug the wireless mobility high availability in the controller, use the set trace mobility ha command.
set trace mobility ha [ event | detail | dump ] { filter [ mac WORD switch switch number ] [ none [ switch switch ] | filter_name [ filter_value [ switch switch ] ] ] | level { default | trace_level } [ switch switch ] { filtered | switch } }
event | (Optional) Specifies the wireless mobility high availability events. |
detail | (Optional) Specifies the wireless mobility high availability details. |
dump | (Optional) Specifies the wireless mobility high availability output. |
filter | Specifies to trace adapted flag filter. |
mac | Specifies the MAC address. |
WORD switch | Specifies the switch. |
switch number | Specifies the switch number. The value ranges from one to four. |
none | Specifies no trace adapted flag filter. |
switch switch | (Optional) Specifies the controller number. |
filter_name | Trace adapted flag filter name. |
filter_value | Trace adapted flag filter value. |
switch switch | Specifies the controller number. |
level | Specifies the trace level value. |
default | Specifies the un-set trace level value. |
trace_level | Specifies the trace level value. |
switch switch | Specifies the controller number. |
filtered | Specifies the filtered trace messages. |
switch | Specifies the switch. |
None
Any command mode
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This example shows how to display wireless mobility high availability details:
Controller# set trace mobility ha detail filter mac WORD
[08/27/13 10:38:35.349 UTC 1 8135] Invalid src ip: 169.254.1.1
[08/27/13 10:38:35.349 UTC 2 8135] Invalid sysIp: Skip plumbing MC-MA tunnels.
[08/27/13 10:38:54.393 UTC 3 8135] Mobility version mismatch, v10 received, or m
sglen mismatch msglen=74 recvBytes=0, dropping
To trace wireless Quality of Service (QoS) high availability, use the set trace qos ap ha command.
set trace QOS ap ha [ event | error ] { filter [ MACnone [ switch switch ] | filter_name [ filter_value [ switch switch ] ] ] | level { default | trace_level } [ switch switch ] }
event | (Optional) Specifies trace QoS wireless AP event. |
event mac | Specifies the MAC address of the AP. |
event none | Specifies no MAC address value. |
error | (Optional) Specifies trace QoS wireless AP errors. |
error mac | Specifies the MAC address of the AP. |
error none | Specifies no value. |
filter | Specifies the trace adapted flag filter. |
filter mac | Specifies the MAC address of the AP. |
filter none | Specifies no value. |
switch switch | Specifies the switch number. |
filter_name | (Optional) Specifies the switch filter name. |
filter_value | (Optional) Specifies the switch filter value. Value is one. |
switch switch | (Optional) Specifies the switch number. Value is one. |
level | Specifies the trace level. |
default | Specifies the trace QoS wireless AP default. |
trace_level | Trace level. |
switch switch | (Optional) Specifies the switch number. Value is one. |
None
Any command mode
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This example shows how to trace wireless QoS high availability:
Controller# set trace QOS ap ha
To display platform-dependent switch-stack information, use the show platform stack-manager command in privileged EXEC mode.
show platform stack-manager { oir-states | sdp-counters | sif-counters } switch stack-member-number
oir-states |
Displays Online Insertion and Removal (OIR) state information |
sdp-counters |
Displays Stack Discovery Protocol (SDP) counter information. |
sif-counters |
Displays Stack Interface (SIF) counter information. |
switch stack-member-number |
Specifies the stack member for which to display stack-manager information. |
None
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
Use the show platform stack-manager command to collect data and statistics for the switch stack.
Use this command only when you are working directly with your technical support representative while troubleshooting a problem. Do not use this command unless your technical support representative asks you to do so.
To display redundancy facility information, use the show redundancy command in privileged EXEC mode
show redundancy [ clients | config-sync | counters | history [ reload | reverse ] | slaves [ slave-name ] { clients | counters } | states | switchover history [ domain default ] ]
clients |
(Optional) Displays information about the redundancy facility client. |
config-sync |
(Optional) Displays a configuration synchronization failure or the ignored mismatched command list (MCL). For more information, see show redundancy config-sync. |
counters |
(Optional) Displays information about the redundancy facility counter. |
history |
(Optional) Displays a log of past status and related information for the redundancy facility. |
history reload |
(Optional) Displays a log of past reload information for the redundancy facility. |
history reverse |
(Optional) Displays a reverse log of past status and related information for the redundancy facility. |
slaves |
(Optional) Displays all slaves in the redundancy facility. |
slave-name |
(Optional) The name of the redundancy facility slave to display specific information for. Enter additional keywords to display all clients or counters in the specified slave. |
clients |
Displays all redundancy facility clients in the specified slave. |
counters |
Displays all counters in the specified slave. |
states |
(Optional) Displays information about the redundancy facility state, such as disabled, initialization, standby or active. |
switchover history |
(Optional) Displays information about the redundancy facility switchover history. |
domain default |
(Optional) Displays the default domain as the domain to display switchover history for. |
None
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This example shows how to display information about the redundancy facility:
Controller# show redundancy Redundant System Information : ------------------------------ Available system uptime = 6 days, 9 hours, 23 minutes Switchovers system experienced = 0 Standby failures = 0 Last switchover reason = not known Hardware Mode = Simplex Configured Redundancy Mode = SSO Operating Redundancy Mode = SSO Maintenance Mode = Disabled Communications = Down Reason: Simplex mode Current Processor Information : ------------------------------ Active Location = slot 1 Current Software state = ACTIVE Uptime in current state = 6 days, 9 hours, 23 minutes Image Version = Cisco IOS Software, IOS-XE Software, Catalyst 3 850 L3 Switch Software (CAT3850-UNIVERSALK9-M), Version 03.08.59.EMD EARLY DEPLO YMENT ENGINEERING NOVA_WEEKLY BUILD, synced to DSGS_PI2_POSTPC_FLO_DSBU7_NG3K_11 05 Copyright (c) 1986-2012 by Cisco Systems, Inc. Compiled Sun 16-S Configuration register = 0x102 Peer (slot: 0) information is not available because it is in 'DISABLED' state Controller#
This example shows how to display redundancy facility client information:
Controller# show redundancy clients
Group ID = 1
clientID = 20002 clientSeq = 4 EICORE HA Client
clientID = 24100 clientSeq = 5 WCM_CAPWAP
clientID = 24101 clientSeq = 6 WCM RRM HA
clientID = 24103 clientSeq = 8 WCM QOS HA
clientID = 24105 clientSeq = 10 WCM_MOBILITY
clientID = 24106 clientSeq = 11 WCM_DOT1X
clientID = 24107 clientSeq = 12 WCM_APFROGUE
clientID = 24110 clientSeq = 15 WCM_CIDS
clientID = 24111 clientSeq = 16 WCM_NETFLOW
clientID = 24112 clientSeq = 17 WCM_MCAST
clientID = 24120 clientSeq = 18 wcm_comet
clientID = 24001 clientSeq = 21 Table Manager Client
clientID = 20010 clientSeq = 24 SNMP SA HA Client
clientID = 20007 clientSeq = 27 Installer HA Client
clientID = 29 clientSeq = 60 Redundancy Mode RF
clientID = 139 clientSeq = 61 IfIndex
clientID = 3300 clientSeq = 62 Persistent Variable
clientID = 25 clientSeq = 68 CHKPT RF
clientID = 20005 clientSeq = 74 IIF-shim
clientID = 10001 clientSeq = 82 QEMU Platform RF
<output truncated>
The output displays the following information:
This example shows how to display the redundancy facility counter information:
Controller# show redundancy counters Redundancy Facility OMs comm link up = 0 comm link down = 0 invalid client tx = 0 null tx by client = 0 tx failures = 0 tx msg length invalid = 0 client not rxing msgs = 0 rx peer msg routing errors = 0 null peer msg rx = 0 errored peer msg rx = 0 buffers tx = 0 tx buffers unavailable = 0 buffers rx = 0 buffer release errors = 0 duplicate client registers = 0 failed to register client = 0 Invalid client syncs = 0 Controller#
This example shows how to display redundancy facility history information:
Controller# show redundancy history
00:00:00 *my state = INITIALIZATION(2) peer state = DISABLED(1)
00:00:00 RF_EVENT_INITIALIZATION(524) op=0 rc=0
00:00:00 *my state = NEGOTIATION(3) peer state = DISABLED(1)
00:00:01 client added: Table Manager Client(24001) seq=21
00:00:01 client added: SNMP SA HA Client(20010) seq=24
00:00:06 client added: WCM_CAPWAP(24100) seq=5
00:00:06 client added: WCM QOS HA(24103) seq=8
00:00:07 client added: WCM_DOT1X(24106) seq=11
00:00:07 client added: EICORE HA Client(20002) seq=4
00:00:09 client added: WCM_MOBILITY(24105) seq=10
00:00:09 client added: WCM_NETFLOW(24111) seq=16
00:00:09 client added: WCM_APFROGUE(24107) seq=12
00:00:09 client added: WCM RRM HA(24101) seq=6
00:00:09 client added: WCM_MCAST(24112) seq=17
00:00:09 client added: WCM_CIDS(24110) seq=15
00:00:09 client added: wcm_comet(24120) seq=18
00:00:22 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) First Slave(0) op=0 rc=0
00:00:22 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Slave(6107) op=0 rc=0
00:00:22 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Slave(6109) op=0 rc=0
00:00:22 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Slave(6128) op=0 rc=0
00:00:22 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Slave(8897) op=0 rc=0
00:00:22 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Slave(8898) op=0 rc=0
00:00:22 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Slave(8901) op=0 rc=0
00:00:22 RF_EVENT_SLAVE_STATUS_DONE(523) First Slave(0) op=405 rc=0
00:00:22 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) Redundancy Mode RF(29) op=0 rc=0
00:00:22 RF_STATUS_REDUNDANCY_MODE_CHANGE(405) IfIndex(139) op=0 rc=0
<output truncated>
This example shows how to display information about the redundancy facility slaves:
Controller# show redundancy slaves Group ID = 1 Slave/Process ID = 6107 Slave Name = [installer] Slave/Process ID = 6109 Slave Name = [eicored] Slave/Process ID = 6128 Slave Name = [snmp_subagent] Slave/Process ID = 8897 Slave Name = [wcm] Slave/Process ID = 8898 Slave Name = [table_mgr] Slave/Process ID = 8901 Slave Name = [iosd] Controller#
This example shows how to display information about the redundancy facility state:
Controller# show redundancy states my state = 13 -ACTIVE peer state = 1 -DISABLED Mode = Simplex Unit ID = 1 Redundancy Mode (Operational) = SSO Redundancy Mode (Configured) = SSO Redundancy State = Non Redundant Manual Swact = disabled (system is simplex (no peer unit)) Communications = Down Reason: Simplex mode client count = 75 client_notification_TMR = 360000 milliseconds keep_alive TMR = 9000 milliseconds keep_alive count = 0 keep_alive threshold = 18 RF debug mask = 0 Controller#
To display a configuration synchronization failure or the ignored mismatched command list (MCL), if any, use the show redundancy config-sync command in EXEC mode.
show redundancy config-sync { failures { bem | mcl | prc } | ignored failures mcl }
failures | Displays MCL entries or best effort method (BEM)/Parser Return Code (PRC) failures. |
bem | Displays a BEM failed command list, and forces the standby switch to reboot. |
mcl | Displays commands that exist in the switch’s running configuration but are not supported by the image on the standby switch, and forces the standby switch to reboot. |
prc | Displays a PRC failed command list and forces the standby switch to reboot. |
ignored failures mcl | Displays the ignored MCL failures. |
None
User EXEC
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
When two versions of Cisco IOS images are involved, the command sets supported by two images might differ. If any of those mismatched commands are executed on the active switch, the standby switch might not recognize those commands, which causes a configuration mismatch condition. If the syntax check for the command fails on the standby switch during a bulk synchronization, the command is moved into the MCL and the standby switch is reset. To display all the mismatched commands, use the show redundancy config-sync failures mcl command.
To clean the MCL, follow these steps:
Alternatively, you could ignore the MCL by following these steps:
Note |
If you ignore the mismatched commands, the out-of-synchronization configuration on the active switch and the standby switch still exists. |
Each command sets a return code in the action function that implements the command. This return code indicates whether or not the command successfully executes. The active switch maintains the PRC after executing a command. The standby switch executes the command and sends the PRC back to the active switch. A PRC failure occurs if these two PRCs do not match. If a PRC error occurs at the standby switch either during bulk synchronization or line-by-line (LBL) synchronization, the standby switch is reset. To display all PRC failures, use the show redundancy config-sync failures prc command.
To display best effort method (BEM) errors, use the show redundancy config-sync failures bem command.
This example shows how to display the BEM failures:
Controller> show redundancy config-sync failures bem
BEM Failed Command List
-----------------------
The list is Empty
This example shows how to display the MCL failures:
Controller> show redundancy config-sync failures mcl
Mismatched Command List
-----------------------
The list is Empty
This example shows how to display the PRC failures:
Controller# show redundancy config-sync failures prc
PRC Failed Command List
-----------------------
The list is Empty
To display information that is related to the stack member or the switch stack, use the show switch command in EXEC mode.
None
User EXEC
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This example shows how to display summary stack information:
This example shows how to display detailed stack information:
This example shows how to display the member 6 summary information:
Controller# show switch 6
Switch# Role Mac Address Priority State
--------------------------------------------------------
6 Member 0003.e31a.1e00 1 Ready
This example shows how to display the neighbor information for a stack:
Controller# show switch neighbors
Switch # Port A Port B
-------- ------ ------
6 None 8
8 6 None
This example shows how to display stack-port information:
Controller# show switch stack-ports
Switch # Port A Port B
-------- ------ ------
6 Down Ok
8 Ok Down
Command |
Description |
Reloads the stack member and applies a configuration change. |
|
Updates the stack MAC address to the MAC address of the active switch. |
|
Changes the stack member priority value. |
|
Supplies a configuration to a new switch before it joins the switch stack. |
|
Changes the stack member number. |
To display wireless control and provisioning of wireless access points (CAPWAP) high availability, use the show trace messages capwap ap ha command.
show trace messages capwap ap ha [ detail | event | dump ] [ switch switch ]
detail | (Optional) Displays wireless CAPWAP high availability details. |
detailswitch number | Specifies the controller number. Value is one. |
event | (Optional) Displays wireless CAPWAP high availability events. |
eventswitch number | Specifies the controller number. Value is one. |
dump | (Optional) Displays wireless CAPWAP high availability output. |
dump switch number | Specifies the controller number. Value is one. |
switch | (Optional) Displays the controller number. The value is one. |
switch switch number | Specifies the controller number. Value is one. |
None
Any command mode
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This example shows how to display CAPWAP high availability output:
Controller# show trace messages mobility ha dump switch 1
| Output modifiers
<cr>
To display wireless mobility high availability, use the show trace messages mobility ha command.
show trace messages mobility ha [ event | detail | dump ] [ switch switch ]
event | (Optional) Displays wireless mobility HA events. |
event switch | Specifies the controller number. Value is one. |
detail | (Optional) Displays wireless mobility HA details. |
detail switch | Specifies the controller number. Value is one. |
dump | (Optional) Displays the wireless mobility HA output debugging. |
dump switch | Specifies the controller number. Value is one. |
switch switch | (Optional) Displays the controller number. |
switch switch | Specifies the controller number. Value is one. |
None
Any command mode
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This example shows how to display wireless mobility high availability:
Controller# show trace messages mobility ha
To enable the persistent MAC address feature, use the stack-mac persistent timer command in global configuration mode on the switch stack or on a standalone switch. To disable the persistent MAC address feature, use the no form of this command.
stack-mac persistent timer [ 0 | time-value ]
no stack-mac persistent timer
0 |
|
time-value |
(Optional) Time period in minutes before the stack MAC address changes to that of the new . The range is 1 to 60 minutes. |
Persistent MAC address is disabled. The MAC address of the stack is always that of the first .
Global configuration
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
Command |
Description |
Updates the stack MAC address to the MAC address of the active switch. |
To update the stack MAC address to the MAC address of the active switch, use the stack-mac update force command in EXEC mode on the active switch.
stack-mac update force
This command has no arguments or keywords.
None
User EXEC
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
By default, the stack MAC address is not changed to the MAC address of the new active switch during a high availability (HA) failover. Use the stack-mac update force command to force the stack MAC address to change to the MAC address of the new active switch.
If the switch with the same MAC address as the stack MAC address is currently a member of the stack, the stack-mac update force command has no effect. (It does not change the stack MAC address to the MAC address of the active switch.)
Note |
If you do not change the stack MAC address, Layer 3 interface flapping does not occur. It also means that a foreign MAC address (a MAC address that does not belong to any of the switches in the stack) could be the stack MAC address. If the switch with this foreign MAC address joins another stack as the active switch, two stacks will have the same stack MAC address. You must use the stack-mac update force command to resolve the conflict. |
This example shows how to update the stack MAC address to the MAC address of the active switch:
Controller> stack-mac update force Controller>
You can verify your settings by entering the show switch privileged EXEC command. The stack MAC address includes whether the MAC address is local or foreign.
Command |
Description |
Displays information related to the stack member or the switch stack. |
|
Enables the persistent MAC address feature. |
To enable access to the standby console switch, use the standby console enable command in redundancy main configuration submode. To disable access to the standby console switch, use the no form of this command.
standby console enable
no standby console enable
This command has no arguments or keywords.
Access to the standby console switch is disabled.
Redundancy main configuration submode
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
This command is used to collect and review specific data about the standby console. The command is useful primarily for Cisco technical support representatives troubleshooting the switch.
This example shows how to enter the redundancy main configuration submode and enable access to the standby console switch:
Controller(config)# redundancy Controller(config-red)# main-cpu Controller(config-r-mc)# standby console enable Controller(config-r-mc)#
Command |
Description |
Enters the redundancy main configuration submode and enables the standby switch. |
To disable or enable the specified stack port on the member, use the switch command in privileged EXEC mode on a stack member.
switch stack-member-number stack port port-number { disable | enable }
stack-member-number |
|
stack port port-number |
Specifies the stack port on the member. The range is 1 to 2. |
disable |
Disables the specified port. |
enable |
Enables the specified port. |
The stack port is enabled.
Privileged EXEC
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
A stack is in the full-ring state when all members are connected through the stack ports and are in the ready state.
The stack is in the partial-ring state when the following occurs:
Note |
Be careful when using the switch stack-member-number stack port port-number disable command. When you disable the stack port, the stack operates at half bandwidth. |
If you enter the switch stack-member-number stack port port-number disable privileged EXEC command and the stack is in the full-ring state, you can disable only one stack port. This message appears:
Enabling/disabling a stack port may cause undesired stack changes. Continue?[confirm]
If you enter the switch stack-member-number stack port port-number disable privileged EXEC command and the stack is in the partial-ring state, you cannot disable the port. This message appears:
Disabling stack port not allowed with current stack configuration.
This example shows how to disable stack port 2 on member 4:
Controller# switch 4 stack port 2 disable
Command |
Description |
Displays information related to the stack member or the switch stack. |
To change the stack member priority value, use the switch priority command in mode on the .
switch stack-member-number priority new-priority-value
stack-member-number |
|
new-priority-value |
New stack member priority value. The range is 1 to 15. |
The default priority value is 1.
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
The new priority value is a factor when a new is elected. When you change the priority value the is not changed immediately.
This example shows how to change the priority value of stack member 6 to 8:
Controller switch 6 priority 8
Changing the Switch Priority of Switch Number 6 to 8
Do you want to continue?[confirm]
Command |
Description |
Reloads the stack member and applies a configuration change. |
|
Displays information related to the stack member or the switch stack. |
|
Changes the stack member number. |
To supply a configuration to a new switch before it joins the switch stack, use the switch provision command in global configuration mode on the . To delete all configuration information that is associated with the removed switch (a stack member that has left the stack), use the no form of this command.
switch stack-member-number provision type
no switch stack-member-number provision
stack-member-number |
Stack member number. The range is 1 to 2. |
type |
Switch type of the new switch before it joins the stack. |
The switch is not provisioned.
Global configuration
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
For type, enter the model number of a supported switch that is listed in the command-line help strings.
To avoid receiving an error message, you must remove the specified switch from the switch stack before using the no form of this command to delete a provisioned configuration.
To change the switch type, you must also remove the specified switch from the switch stack. You can change the stack member number of a provisioned switch that is physically present in the switch stack if you do not also change the switch type.
If the switch type of the provisioned switch does not match the switch type in the provisioned configuration on the stack, the switch stack applies the default configuration to the provisioned switch and adds it to the stack. The switch stack displays a message when it applies the default configuration.
Provisioned information appears in the running configuration of the switch stack. When you enter the copy running-config startup-config privileged EXEC command, the provisioned configuration is saved in the startup configuration file of the switch stack.
Caution |
When you use the switch provision command, memory is allocated for the provisioned configuration. When a new switch type is configured, the previously allocated memory is not fully released. Therefore, do not use this command more than approximately 200 times, or the switch will run out of memory and unexpected behavior will result. |
This example shows how to provision a switch with a stack member number of 2 for the switch stack. The show running-config command output shows the interfaces associated with the provisioned switch.
Controller(config)# switch 2 provision WS-xxxx Controller(config)# end Controller# show running-config | include switch 2 ! interface GigabitEthernet2/0/1 ! interface GigabitEthernet2/0/2 ! interface GigabitEthernet2/0/3 <output truncated>
You also can enter the show switch user EXEC command to display the provisioning status of the switch stack.
This example shows how to delete all configuration information about stack member 5 when the switch is removed from the stack:
Controller(config)# no switch 5 provision
You can verify that the provisioned switch is added to or removed from the running configuration by entering the show running-config privileged EXEC command.
Command |
Description |
Displays information related to the stack member or the switch stack. |
To change the stack member number, use the switch renumber command in mode on the .
switch current-stack-member-number renumber new-stack-member-number
current-stack-member-number |
|
new-stack-member-number |
The default stack member number is 1.
Release | Modification |
---|---|
Cisco IOS XE 3.2SE |
This command was introduced. |
If another stack member is already using the member number that you just specified, the assigns the lowest available number when you reload the stack member.
Note |
If you change the number of a stack member, and no configuration is associated with the new stack member number, that stack member loses its current configuration and resets to its default configuration. |
Do not use the switch current-stack-member-number renumber new-stack-member-number command on a provisioned switch. If you do, the command is rejected.
Use the reload slot current stack member number privileged EXEC command to reload the stack member and to apply this configuration change.
This example shows how to change the member number of stack member 6 to 7:
Command |
Description |
Reloads the stack member and applies a configuration change. |
|
Displays information related to the stack member or the switch stack. |
|
Changes the stack member priority value. |