Command Reference, Cisco IOS XE Gibraltar 16.10.x (Catalyst 9500 Switches)

main-cpu

To enter the redundancy main configuration submode and enable the standby switch, use the main-cpu command in redundancy configuration mode.

main-cpu

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

Redundancy configuration (config-red)

Command History


Release	Modification
Cisco IOS XE Everest 16.5.1a	This command was introduced.

Usage Guidelines

From the redundancy main configuration submode, use the standby console enable command to enable the standby switch.

Examples

This example shows how to enter the redundancy main configuration submode and enable the standby switch:

Device(config)# redundancy
Device(config-red)# main-cpu
Device(config-r-mc)# standby console enable
Device#

mode sso

To set the redundancy mode to stateful switchover (SSO), use the mode sso command in redundancy configuration mode.

mode sso

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

Redundancy configuration

Command History


Release	Modification
Cisco IOS XE Everest 16.5.1a	This command was introduced.

Usage Guidelines

The mode sso command can be entered only from within redundancy configuration mode.

Follow these guidelines when configuring your system to SSO mode:

You must use identical Cisco IOS images on the switches in the stack to support SSO mode. Redundancy may not work due to differences between the Cisco IOS releases.
If you perform an online insertion and removal (OIR) of the module, the switch resets during the stateful switchover and the port states are restarted only if the module is in a transient state (any state other than Ready).
The forwarding information base (FIB) tables are cleared on a switchover. Routed traffic is interrupted until route tables reconverge.

Examples

This example shows how to set the redundancy mode to SSO:

Device(config)# redundancy
Device(config-red)# mode sso
Device(config-red)#

policy config-sync prc reload

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

Syntax Description


bulk	Specifies bulk configuration mode.
lbl	Specifies line-by-line (lbl) configuration mode.

Command Default

The command is enabled by default.

Command Modes

Redundancy configuration (config-red)

Command History


Release	Modification
Cisco IOS XE Everest 16.5.1a	This command was introduced.

Examples

This example shows how to specify that the standby switch is not reloaded if a parser return code (PRC) failure occurs during configuration synchronization:

Device(config-red)# no policy config-sync bulk prc reload

redundancy

To enter redundancy configuration mode, use the redundancy command in global configuration mode.

redundancy

Syntax Description

This command has no arguments or keywords.

Command Default

None

Command Modes

Global configuration (config)

Command History


Release	Modification
Cisco IOS XE Everest 16.5.1a	This command was introduced.

Usage Guidelines

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 exit command to exit redundancy configuration mode.

Examples

This example shows how to enter redundancy configuration mode:

Device(config)# redundancy
Device(config-red)#

This example shows how to enter the main CPU submode:

Device(config)# redundancy
Device(config-red)# main-cpu
Device(config-r-mc)#

Related Commands


Command	Description
show redundancy	Displays redundancy facility information.

reload

To reload the stack member and to apply a configuration change, use the reload command in privileged EXEC mode.

Syntax Description


/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`	(Optional) Stack member number on which to save the changes. The range is 1 to 9.
standby-cpu	(Optional) Reloads the standby route processor (RP).

Command Default

Immediately reloads the stack member and puts a configuration change into effect.

Command Modes

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.5.1a	This command was introduced.

Usage Guidelines

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.

Examples

This example shows how to reload the switch stack:

Device# reload
System configuration has been modified. Save? [yes/no]: yes
Reload command is being issued on Active unit, this will reload the whole stack
Proceed with reload? [confirm] yes

This example shows how to reload a specific stack member:

Device# 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):

Device# reload slot 3
System configuration has been modified. Save? [yes/no]: y
Proceed to reload the whole Stack? [confirm] y

show redundancy

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]]

Syntax Description


clients	(Optional) Displays information about the redundancy facility client.
config-sync	(Optional) Displays a configuration synchronization failure or the ignored mismatched command list (MCL).
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.

Command Default

None

Command Modes

Privileged EXEC (#)

Command History


Release	Modification
Cisco IOS XE Everest 16.5.1a	This command was introduced.

Examples

This example shows how to display information about the redundancy facility:

Device# show redundancy

Redundant System Information :
------------------------------
       Available system uptime = 6 days, 5 hours, 28 minutes
Switchovers system experienced = 0
              Standby failures = 0
        Last switchover reason = none

                 Hardware Mode = Duplex
    Configured Redundancy Mode = sso
     Operating Redundancy Mode = sso
              Maintenance Mode = Disabled
                Communications = Up

Current Processor Information :
-------------------------------
               Active Location = slot 5
        Current Software state = ACTIVE
       Uptime in current state = 6 days, 5 hours, 28 minutes
                 Image Version = Cisco IOS Software, Catalyst L3 Switch Software
(CAT9K_IOSXE),Experimental Version 16.x.x [S2C-build-v16x_throttle-4064-/
nobackup/mcpre/BLD-BLD_V16x_THROTTLE_LATEST 102]
Copyright (c) 1986-201x by Cisco Systems, Inc.
Compiled Mon 07-Oct-xx 03:57 by mcpre
                          BOOT = bootflash:packages.conf;
        Configuration register = 0x102

Peer Processor Information :
----------------------------
              Standby Location = slot 6
        Current Software state = STANDBY HOT 
       Uptime in current state = 6 days, 5 hours, 25 minutes
                 Image Version = Cisco IOS Software, Catalyst L3 Switch Software
(CAT9K_IOSXE), Experimental Version 16.x.x [S2C-build-v16x_throttle-4064-/
nobackup/mcpre/BLD-BLD_V16x_THROTTLE_LATEST_20191007_000645 102]
Copyright (c) 1986-201x by Cisco Systems, Inc.
Compiled Mon 07-Oct-xx 03:57 by mcpre
                          BOOT = bootflash:packages.conf;
                   CONFIG_FILE = 
        Configuration register = 0x102
Device#

This example shows how to display redundancy facility client information:

Device# show redundancy clients

Group ID =     1
     clientID = 29       clientSeq = 60       Redundancy Mode RF
     clientID = 139      clientSeq = 62       IfIndex
     clientID = 25       clientSeq = 71       CHKPT RF
     clientID = 10001    clientSeq = 85       QEMU Platform RF
     clientID = 77       clientSeq = 87       Event Manager
     clientID = 1340     clientSeq = 104      RP Platform RF
     clientID = 1501     clientSeq = 105      CWAN HA
     clientID = 78       clientSeq = 109      TSPTUN HA
     clientID = 305      clientSeq = 110      Multicast ISSU Consolidation RF
     clientID = 304      clientSeq = 111      IP multicast RF Client
     clientID = 22       clientSeq = 112      Network RF Client
     clientID = 88       clientSeq = 113      HSRP
     clientID = 114      clientSeq = 114      GLBP
     clientID = 225      clientSeq = 115      VRRP
     clientID = 4700     clientSeq = 118      COND_DEBUG RF
     clientID = 1341     clientSeq = 119      IOSXE DPIDX
     clientID = 1505     clientSeq = 120      IOSXE SPA TSM
     clientID = 75       clientSeq = 130      Tableid HA
     clientID = 501      clientSeq = 137      LAN-Switch VTP VLAN

<output truncated>

The output displays the following information:

clientID displays the client’s ID number.
clientSeq displays the client’s notification sequence number.
Current redundancy facility state.

This example shows how to display the redundancy facility counter information:

Device# 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 = 135884 
     tx buffers unavailable = 0 
                 buffers rx = 135109 
      buffer release errors = 0 

 duplicate client registers = 0 
  failed to register client = 0 
       Invalid client syncs = 0 

Device#

This example shows how to display redundancy facility history information:

Device# show redundancy history

00:00:04 client added: Redundancy Mode RF(29) seq=60
00:00:04 client added: IfIndex(139) seq=62
00:00:04 client added: CHKPT RF(25) seq=71
00:00:04 client added: QEMU Platform RF(10001) seq=85
00:00:04 client added: Event Manager(77) seq=87
00:00:04 client added: RP Platform RF(1340) seq=104
00:00:04 client added: CWAN HA(1501) seq=105
00:00:04 client added: Network RF Client(22) seq=112
00:00:04 client added: IOSXE SPA TSM(1505) seq=120
00:00:04 client added: LAN-Switch VTP VLAN(501) seq=137
00:00:04 client added: XDR RRP RF Client(71) seq=139
00:00:04 client added: CEF RRP RF Client(24) seq=140
00:00:04 client added: MFIB RRP RF Client(306) seq=150
00:00:04 client added: RFS RF(520) seq=163
00:00:04 client added: klib(33014) seq=167
00:00:04 client added: Config Sync RF client(5) seq=168
00:00:04 client added: NGWC FEC Rf client(10007) seq=173
00:00:04 client added: LAN-Switch Port Manager(502) seq=190
00:00:04 client added: Access Tunnel(530) seq=192
00:00:04 client added: Mac address Table Manager(519) seq=193
00:00:04 client added: DHCPC(100) seq=238
00:00:04 client added: DHCPD(101) seq=239
00:00:04 client added: SNMP RF Client(34) seq=251
00:00:04 client added: CWAN APS HA RF Client(1502) seq=252
00:00:04 client added: History RF Client(35) seq=261

<output truncated>

This example shows how to display information about the redundancy facility slaves:

Device# 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]

Device#

This example shows how to display information about the redundancy facility state:

Device# show redundancy states

       my state = 13 -ACTIVE 
     peer state = 8  -STANDBY HOT 
           Mode = Duplex
           Unit = Primary
        Unit ID = 5

Redundancy Mode (Operational) = sso
Redundancy Mode (Configured)  = sso
Redundancy State              = sso
     Maintenance Mode = Disabled
    Manual Swact = enabled
 Communications = Up

   client count = 115
 client_notification_TMR = 30000 milliseconds
           RF debug mask = 0x0

Device#

show redundancy config-sync

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}

Syntax Description


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.

Command Default

None

Command Modes

User EXEC

Privileged EXEC

Command History


Release	Modification
Cisco IOS XE Everest 16.5.1a	This command was introduced.

Usage Guidelines

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:

Remove all mismatched commands from the active switch's running configuration.
Revalidate the MCL with a modified running configuration by using the redundancy config-sync validate mismatched-commands command.
Reload the standby switch.

Alternatively, you could ignore the MCL by following these steps:

Enter the redundancy config-sync ignore mismatched-commands command.

Reload the standby switch; the system transitions to SSO mode.

Note

If you ignore the mismatched commands, the out-of-synchronization configuration on the active switch and the standby switch still exists.

You can verify the ignored MCL with the show redundancy config-sync ignored mcl command.

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.

Examples

This example shows how to display the BEM failures:

Device> show redundancy config-sync failures bem
BEM Failed Command List
-----------------------

 The list is Empty

This example shows how to display the MCL failures:

Device> show redundancy config-sync failures mcl
Mismatched Command List
-----------------------

The list is Empty

This example shows how to display the PRC failures:

Device# show redundancy config-sync failures prc
PRC Failed Command List
-----------------------

 The list is Empty

show tech-support stack

To display all switch stack-related information for use by technical support, use the show tech-support stack command in privileged EXEC mode.

show tech-support stack

Command Modes

Privileged EXEC (#)

Command History


Release	Modification
Cisco IOS XE Gibraltar 16.10.1	This command was introduced.
Cisco IOS XE Gibraltar 16.12.1	The output for this command was enhanced to include more stack-related information.

Usage Guidelines

The show tech-support stack command captures the snapshot of stacking states and information for debug issues. Use this command, when stacking issues (such as stack cable issue, silent reload, switch not coming to ready state, stack crash, and so on) occur.

The output of the show tech-support stack command is very long. To better manage this output, you can redirect the output to a file (for example, show tech-support stack | redirect flash:filename ) in the local writable storage file system or remote file system.

The output of the show tech stack command displays the output of the following commands:

The following commands are only available on stacked switches in ready state

show platform software stack-mgr switch
show platform software sif switch
show platform hardware fed switch
dir crashinfo:
dir flash:/core

Cisco Catalyst 9500 Series Switches with Stackwise Virtual Link

show clock
show version
show running-config

The following commands are only available on non-stackable switches in ready state:

show redundancy switchover history
show platform software fed switch active
show platform software fed switch standby
show stackwise-virtual bandwidth
show stackwise-virtual dual-active-detection
show stackwise-virtual link
show stackwise-virtual neighbors
dir crashinfo:
dir flash:/core

Examples

The following is sample output from the show tech-support stack command:

Device# show tech-support stack  

.
.
.

------------------ show stackwise-virtual bandwidth ------------------

Switch  Bandwidth
------  ---------
1        400G
2        400G


------------------ show stackwise-virtual dual-active-detection ------------------

In dual-active recovery mode: No
Recovery Reload: Enabled

Dual-Active-Detection Configuration:
-------------------------------------
Switch  Dad port                        Status
------  ------------                    ---------


------------------ show stackwise-virtual dual-active-detection pagp ------------------

Pagp dual-active detection enabled: No
In dual-active recovery mode: No
Recovery Reload: Enabled


No PAgP channel groups configured

------------------ show stackwise-virtual link ------------------

Stackwise Virtual Link(SVL) Information:
----------------------------------------
Flags:
------
Link Status
-----------
U-Up D-Down
Protocol Status
---------------
S-Suspended P-Pending E-Error T-Timeout R-Ready
-----------------------------------------------
Switch  SVL     Ports                           Link-Status     Protocol-Status
------  ---     -----                           -----------     ---------------
1       1       HundredGigE1/0/45               D               R
                HundredGigE1/0/46               D               R
                HundredGigE1/0/47               D               R
                HundredGigE1/0/48               D               R
2       1       HundredGigE2/0/45               D               R
                HundredGigE2/0/46               D               R
                HundredGigE2/0/47               D               R
                HundredGigE2/0/48               D               R


------------------ show stackwise-virtual link detail ------------------



------------------ show stackwise-virtual neighbors ------------------

Stackwise Virtual Link(SVL) Neighbors Information:
--------------------------------------------------
Switch  SVL     Local Port                         Remote Port
------  ---     ----------                         -----------
1       1       HundredGigE1/0/45                  HundredGigE2/0/45
                HundredGigE1/0/46                  HundredGigE2/0/46
                HundredGigE1/0/47                  HundredGigE2/0/47
                HundredGigE1/0/48                  HundredGigE2/0/48
2       1       HundredGigE2/0/45                  HundredGigE1/0/45
                HundredGigE2/0/46                  HundredGigE1/0/46
                HundredGigE2/0/47                  HundredGigE1/0/47
                HundredGigE2/0/48                  HundredGigE1/0/48


------------------ dir crashinfo-1: ------------------



------------------ dir flash-1:/core ------------------



------------------ dir crashinfo: ------------------


Directory of crashinfo:/

15778  -rw-              337   Dec 9 2018 09:29:47 +00:00  shutdown_fp0.log
15779  -rw-              336   Dec 9 2018 09:29:48 +00:00  shutdown_cc1.log
15780  -rw-             3675   Dec 9 2018 09:29:50 +00:00  shutdown_rp0.log
15781  drwx           147456  Jun 27 2019 18:21:13 +00:00  tracelogs
15910  drwx             8192  Jun 24 2019 08:58:06 +00:00  license_evlog
15872  -rw-          6769749  Dec 10 2018 07:12:56 +00:00  PROM2_1_RP_0_trace_archive_0-20181210-071255.tar.gz
16367  -rw-          3312204  Dec 16 2018 13:34:55 +00:00  PROM2_1_RP_0_trace_archive_0-20181216-133455.tar.gz
16392  -rw-          9858028  Dec 17 2018 03:36:07 +00:00  PROM2_1_RP_0_trace_archive_0-20181217-033605.tar.gz
16506  -rw-         10925702  Dec 17 2018 03:55:51 +00:00  PROM2_1_RP_0_trace_archive_0-20181217-035549.tar.gz
15804  -rw-         36415970  Dec 17 2018 03:56:45 +00:00  system-report_RP_0_20181217-035641-UTC.tar.gz
15951  -rw-          9769982   Jan 2 2019 10:32:42 +00:00  PROM2_1_RP_0_trace_archive_0-20190102-103239.tar.gz
16266  -rw-          2789185  Jan 27 2019 09:16:00 +00:00  PROM2_trace_archive_0-20190127-091559.tar.gz
15913  -rw-          2817836  Jan 27 2019 09:16:01 +00:00  SV_PROM2_20190127-091600-20190127-091600.tar.gz
15892  -rw-          4226737  Jan 29 2019 09:21:35 +00:00  PROM2_trace_archive_0-20190129-092134.tar.gz
15908  -rw-          4278342  Jan 29 2019 09:21:36 +00:00  SV_PROM2_1_RP_0_20190129-092135-20190129-092135.tar.gz
16147  -rw-          2749781   Feb 9 2019 07:40:30 +00:00  PROM2_trace_archive_0-20190209-074029.tar.gz
16174  -rw-          2758048   Feb 9 2019 07:40:30 +00:00  SV_PROM2_1_RP_0_20190209-074030-20190209-074030.tar.gz
16255  -rw-          7587256   Feb 9 2019 07:54:30 +00:00  PROM2_trace_archive_0-20190209-075428.tar.gz
16111  -rw-          4138377  Feb 12 2019 14:49:27 +00:00  PROM2_trace_archive_0-20190212-144926.tar.gz
16289  -rw-          4163980  Feb 12 2019 14:49:28 +00:00  SV_PROM2_20190212-144927-20190212-144927.tar.gz
16408  -rw-         11192891  Feb 16 2019 03:46:34 +00:00  PROM2_trace_archive_0-20190216-034631.tar.gz
16532  -rw-         10775214  Feb 17 2019 08:26:00 +00:00  PROM2_trace_archive_0-20190217-082558.tar.gz
16724  -rw-          8511058  Feb 20 2019 07:16:24 +00:00  prom_trace_archive_0-20190220-071622.tar.gz
16142  -rw-          9272613  Feb 20 2019 07:59:18 +00:00  prom_trace_archive_0-20190220-075916.tar.gz
16487  -rw-          9489722  Feb 20 2019 08:17:15 +00:00  prom_1_RP_0_trace_archive_1-20190220-081712.tar.gz
15938  -rw-          8269605  Feb 21 2019 08:25:01 +00:00  prom_trace_archive_0-20190221-082459.tar.gz
16365  -rw-          8770811  Feb 23 2019 05:34:39 +00:00  prom_trace_archive_0-20190223-053437.tar.gz
16511  -rw-         11781087  Feb 23 2019 08:02:23 +00:00  prom_trace_archive_0-20190223-080219.tar.gz
16478  -rw-         12131870  Feb 23 2019 09:52:20 +00:00  prom_1_RP_0_trace_archive_1-20190223-095217.tar.gz
16518  -rw-          8884135  Feb 25 2019 04:54:49 +00:00  prom_trace_archive_0-20190225-045447.tar.gz
16015  -rw-          9323140  Feb 25 2019 05:20:51 +00:00  prom_trace_archive_0-20190225-052049.tar.gz
15827  -rw-         10669814  Feb 25 2019 06:19:23 +00:00  prom_1_RP_0_trace_archive_0-20190225-061920.tar.gz
16618  -rw-         11593370  Feb 26 2019 05:46:57 +00:00  prom_1_RP_0_trace_archive_0-20190226-054653.tar.gz
16566  -rw-          9183975  Feb 26 2019 09:06:15 +00:00  prom_trace_archive_0-20190226-090612.tar.gz
16101  -rw-         10331235  Feb 26 2019 09:33:31 +00:00  prom_trace_archive_0-20190226-093328.tar.gz
16583  -rw-         10877332  Feb 26 2019 15:06:11 +00:00  prom_trace_archive_0-20190226-150608.tar.gz
157761  -rw-         11572215  Feb 27 2019 04:25:32 +00:00  prom_trace_archive_0-20190227-042529.tar.gz
16597  -rw-         10179574   Mar 3 2019 09:53:09 +00:00  prom_trace_archive_0-20190303-095307.tar.gz
16411  -rw-         13563488   Mar 4 2019 09:25:11 +00:00  prom_trace_archive_0-20190304-092506.tar.gz
16206  -rw-         12814910   Mar 4 2019 10:35:28 +00:00  prom_trace_archive_0-20190304-103523.tar.gz
17008  -rw-         13367417   Mar 4 2019 14:48:42 +00:00  prom_1_RP_0_trace_archive_1-20190304-144838.tar.gz
16040  -rw-         13241640   Mar 4 2019 15:17:11 +00:00  prom_trace_archive_0-20190304-151706.tar.gz
157762  -rw-         13371247   Mar 4 2019 15:20:11 +00:00  SV_prom_1_RP_0_20190304-152007-20190304-152007.tar.gz
16450  -rw-         13382489   Mar 5 2019 05:57:08 +00:00  prom_trace_archive_0-20190305-055703.tar.gz
157763  -rw-         11658032   Mar 9 2019 11:03:00 +00:00  prom_trace_archive_0-20190309-110257.tar.gz
16679  -rw-         11492610  Mar 11 2019 08:53:16 +00:00  prom_trace_archive_0-20190311-085313.tar.gz
17015  -rw-         10077961  Mar 13 2019 05:17:33 +00:00  prom_trace_archive_0-20190313-051731.tar.gz
16004  -rw-          2408001  Mar 27 2019 11:50:31 +00:00  prom_1_RP_0_trace_archive_0-20190327-172031.tar.gz
16012  -rw-          2452283  Mar 27 2019 11:50:32 +00:00  SV_prom_20190327-172031-20190327-172031.tar.gz
16341  -rw-          2562092  Mar 27 2019 14:44:59 +00:00  prom_1_RP_0_trace_archive_1-20190327-201458.tar.gz
16332  -rw-          8298681  Mar 27 2019 17:16:51 +00:00  prom_1_RP_0_trace_archive_0-20190327-224649.tar.gz
16496  -rw-          9432359  Mar 27 2019 18:19:50 +00:00  prom_1_RP_0_trace_archive_0-20190327-234947.tar.gz
16664  -rw-          8910820  Mar 28 2019 15:58:12 +00:00  prom_1_RP_0_trace_archive_1-20190328-212810.tar.gz
16035  -rw-          8578186  Mar 29 2019 08:00:27 +00:00  prom_1_RP_0_trace_archive_0-20190329-133025.tar.gz
16312  -rw-          8735806  Mar 29 2019 08:30:39 +00:00  prom_1_RP_0_trace_archive_1-20190329-140037.tar.gz
15891  -rw-          9944637   Apr 4 2019 09:05:31 +00:00  prom_1_RP_0_trace_archive_0-20190404-143528.tar.gz
157764  -rw-          9969565   Apr 4 2019 09:05:36 +00:00  SV_prom_1_RP_0_20190404-143533-20190404-143533.tar.gz
15782  -rw-          9507820   Apr 4 2019 09:05:56 +00:00  system-report_RP_0_20190404-143553-IST.tar.gz
15790  -rw-           563542   Apr 4 2019 09:06:01 +00:00  SV_prom_1_RP_0_20190404-143600-20190404-143600.tar.gz
16131  -rw-         11331090  Apr 23 2019 14:43:24 +00:00  prom_trace_archive_0-20190423-201322.tar.gz
16524  -rw-         11230265  Apr 23 2019 14:49:24 +00:00  prom_1_RP_0_trace_archive_1-20190423-201921.tar.gz
16272  -rw-         11417387  Apr 23 2019 14:55:27 +00:00  SV_prom_1_RP_0_20190423-202524-20190423-202524.tar.gz
15901  -rw-         11435393  Apr 23 2019 14:56:03 +00:00  prom_1_RP_0_trace_archive_2-20190423-202600.tar.gz
16118  -rw-         11337603  Apr 23 2019 15:01:59 +00:00  SV_prom_1_RP_0_20190423-203157-20190423-203157.tar.gz

.
.
.

The output fields are self-explanatory.

standby console enable

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

Syntax Description

This command has no arguments or keywords.

Command Default

Access to the standby console switch is disabled.

Command Modes

Redundancy main configuration submode

Command History


Release	Modification
Cisco IOS XE Everest 16.5.1a	This command was introduced.

Usage Guidelines

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.

Examples

This example shows how to enter the redundancy main configuration submode and enable access to the standby console switch:

Device(config)# redundancy
Device(config-red)# main-cpu
Device(config-r-mc)# standby console enable
Device(config-r-mc)#

Bias-Free Language

Results

Chapter: High Availability Commands

High Availability Commands

main-cpu

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

mode sso

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

policy config-sync prc reload

Syntax Description

Command Default

Command Modes

Command History

Examples

redundancy

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

Related Commands

reload

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

show redundancy

Syntax Description

Command Default

Command Modes

Command History

Examples

show redundancy config-sync

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

show tech-support stack

Command Modes

Command History

Usage Guidelines

Examples

standby console enable

Syntax Description

Command Default

Command Modes

Command History

Usage Guidelines

Examples

Was this Document Helpful?

Contact Cisco