Cisco Catalyst 9800 Series Wireless Controller Software Configuration Guide, Cisco IOS XE 17.14.x - High Availability [Cisco Catalyst 9800 Series Wireless Controllers] (2024)

This table provides release and related information for the features explained in this module.

These features are available in all the releases subsequent to the one they were introduced in, unless noted otherwise.

External Interfaces and IPs

Because all the interfaces are configured only on the Active box, but are synchronized with the Standby box, the same set of interfaces are configured on both controllers. From external nodes, the interfaces connect to the same IP addresses, irrespective of the controllers they are connected to.

For this purpose, the APs, clients, DHCP, Cisco Prime Infrastructure, Cisco Catalyst Centre, and Cisco Identity Services Engine (ISE) servers, and other controller members in the mobility group always connect to the same IP address. The SSO switchover is transparent to them. But if there are TCP connections from external nodes to the controller, the TCP connections need to be reset and reestablished.

HA Interfaces

The HA interface serves the following purposes:

• Provides connectivity between the controller pair before an IOSd comes up.

• Provides IPC transport across the controller pair.

• Enables redundancy across control messages exchanged between the controller pair. The control messages can be HA role resolution, keepalives, notifications, HA statistics, and so on.

You can select either SFP or RJ-45 connection for HA port. Supported Cisco SFPs are:

• GLC-SX-MMD

• GLC-LH-SMD

When either SFP or RJ-45 connection is present, HA works between the two controllers. The SFP HA connectivity takes priority over RJ-45 HA connectivity. If SFP is connected when RJ-45 HA is up and running, the HA pair reloads. The reload occurs even if the link between the SFPs isn’t connected.

Note	It is recommended to have a dedicated physical NIC and Switch for RP when the HA pair is deployed across two host machines. This avoids any keep-alive loses and false HA switchovers or alarms. Disable security scans on VMware virtual instances.

Procedure

Use the following procedure to copy a WebAuth tar bundle to the standby controller, in a high-availability configuration.

Procedure

If the standby controller crashes, it reboots and comes up as the standby controller. Bulk sync follows causing the standby to become hot. If the active controller crashes, the standby becomes active. The new active controller assumes the role of primary and tries to detect a dual active.

The following matrices provide a clear picture of the conditions the controller switchover would trigger:

Active to Active Recovery

• When RP is down and RMI is up at boot up, the Active Recovery occurs.

• When HA is stable (active - standby), if RMI is down first and then RP goes down next, and later if RMI comes up before RP comes up, the Active to Active Recovery occurs. Once the RP is up, the Active Recovery reloads and HA is formed.

Standby to Standby Recovery

• When Standby goes to Standby Recovery for Gateway alone, once the Gateway is up, the HA comes up without any reboot.

• When Standby goes to Standby Recovery for RP down, once the RP is up, the standby recovery reboots automatically and HA is formed.

To view the HA configuration details, use the following command:

Device# show romvarROMMON variables: LICENSE_BOOT_LEVEL = MCP_STARTUP_TRACEFLAGS = 00000000:00000000 BOOTLDR = CRASHINFO = bootflash:crashinfo_RP_00_00_20180202-034353-UTC STACK_1_1 = 0_0 CONFIG_FILE = BOOT = bootflash:boot_image_test,1;bootflash:boot_image_good,1;bootflash:rp_super_universalk9.vwlc.bin,1; RET_2_RTS = SWITCH_NUMBER = 1 CHASSIS_HA_REMOTE_IP = 10.0.1.9 CHASSIS_HA_LOCAL_IP = 10.0.1.10 CHASSIS_HA_LOCAL_MASK = 255.255.255.0 CHASSIS_HA_IFNAME = GigabitEthernet2 CHASSIS_HA_IFMAC = 00:0C:29:C9:12:0B RET_2_RCALTS = BSI = 0 RANDOM_NUM = 647419395

To view the AP SSO statistics, use the following command:

Device# show wireless stat redundancy statistics ap-recovery wnc allAP SSO Statistics Inst Timestamp Dura(ms) #APs #Succ #Fail Avg(ms) Min(ms) Max(ms)------------------------------------------------------------------------------ 0 00:06:29.042 98 34 34 0 2 1 35 1 00:06:29.057 56 33 30 3 1 1 15 2 00:06:29.070 82 33 33 0 2 1 13Statistics:WNCD Instance : 0No. of AP radio recovery failures : 0No. of AP BSSID recovery failures : 0No. of CAPWAP recovery failures : 0No. of DTLS recovery failures : 0No. of reconcile message send failed : 0No. of reconcile message successfully sent : 34No. of Mesh BSSID recovery failures: 0No. of Partial delete cleanup done : 0...

To view the Client SSO statistics, use the following command:

Device# show wireless stat redundancy client-recovery wncd allClient SSO statistics ---------------------- WNCD instance : 1Reconcile messages received from AP : 1Reconcile clients received from AP : 1Recreate attempted post switchover : 1Recreate attempted by SANET Lib : 0Recreate attempted by DOT1x Lib : 0Recreate attempted by SISF Lib : 0Recreate attempted by SVC CO Lib : 1Recreate attempted by Unknown Lib : 0Recreate succeeded post switchover : 1Recreate Failed post switchover : 0Stale client entries purged post switchover : 0Partial delete during heap recreate : 0Partial delete during force purge : 0Partial delete post restart : 0Partial delete due to AP recovery failure : 0Partial delete during reconcilation : 0Client entries in shadow list during SSO : 0Client entries in shadow default state during SSO : 0Client entries in poison list during SSO : 0Invalid bssid during heap recreate : 0Invalid bssid during force purge : 0BSSID mismatch with shadow rec during reconcilation : 0BSSID mismatch with shadow rec reconcilation(WGB client): 0BSSID mismatch with dot11 rec during heap recreate : 0AID mismatch with dot11 rec during force purge : 0AP slotid mismatch during reconcilation : 0Zero aid during heap recreate : 0AID mismatch with shadow rec during reconcilation : 0AP slotid mismatch shadow rec during reconcilation : 0Client shadow record not present : 0

To view the mobility details, use the following command:

Device# show wireless stat redundancy client-recovery mobilitydMobility Client Deletion Reason Statistics-------------------------------------------Mobility Incomplete State : 0Inconsistency in WNCD & Mobility : 0Partial Delete : 0General statistics--------------------Cleanup sent to WNCD, Missing Delete case : 0

To view the Client SSO statistics for SISF, use the following command:

Device# show wireless stat redundancy client-recovery sisfClient SSO statistics for SISF--------------------------------Number of recreate attempted post switchover : 1Number of recreate succeeded post switchover : 1Number of recreate failed because of no mac : 0Number of recreate failed because of no ip : 0Number of ipv4 entry recreate success : 1Number of ipv4 entry recreate failed : 0Number of ipv6 entry recreate success : 0Number of ipv6 entry recreate failed : 0Number of partial delete received : 0Number of client purge attempted : 0Number of heap and db entry purge success : 0Number of purge success for db entry only : 0Number of client purge failed : 0Number of garp sent : 1Number of garp failed : 0Number of IP entries validated in cleanup : 0Number of IP entry address errors in cleanup : 0Number of IP entry deleted in cleanup : 0Number of IP entry delete failed in cleanup : 0Number of IP table create callbacks on standby : 0Number of IP table modify callbacks on standby : 0Number of IP table delete callbacks on standby : 0Number of MAC table create callbacks on standby : 1Number of MAC table modify callbacks on standby : 0Number of MAC table delete callbacks on standby : 0

To view the HA redundancy summary, use the following command:

Device# show wireless stat redundancy summaryHA redundancy summary---------------------AP recovery duration (ms) : 264SSO HA sync timer expired : No

To start the packet capture in the redundancy HA port (RP), use the following commands:

• test wireless redundancy packet dump start

• test wireless redundancy packet dump stop

• test wireless redundancy packet dump start filter port 2300

Device# test wireless redundancy packetdump startRedundancy Port PacketDump StartPacket capture started on RP port.Device# test wireless redundancy packetdump stopRedundancy Port PacketDump StartPacket capture started on RP port.Redundancy Port PacketDump StopPacket capture stopped on RP port.Device# dir bootflash: Directory of bootflash:/1062881 drwx 151552 Oct 20 2020 23:15:25 +00:00 tracelogs47 -rw- 20480 Oct 20 2020 23:15:24 +00:00 haIntCaptureLo.pcap1177345 drwx 4096 Oct 20 2020 19:56:14 +00:00 certs294337 drwx 8192 Oct 20 2020 19:56:05 +00:00 license_evlog15 -rw- 676 Oct 20 2020 19:56:01 +00:00 vlan.dat14 -rw- 30 Oct 20 2020 19:55:16 +00:00 throughput_monitor_params13 -rw- 134808 Oct 20 2020 19:54:57 +00:00 memleak.tcl1586145 drwx 4096 Oct 20 2020 19:54:45 +00:00 .inv1103761 drwx 4096 Oct 20 2020 19:54:39 +00:00 dc_profile_dir17 -r-- 114 Oct 20 2020 19:54:17 +00:00 debug.conf1389921 drwx 4096 Oct 20 2020 19:54:17 +00:00 .installer46 -rw- 1104760207 Oct 20 2020 19:26:41 +00:00 leela_katar_rping_test.SSA.bin49057 drwx 4096 Oct 20 2020 16:11:21 +00:00 .prst_sync45 -rw- 1104803200 Oct 20 2020 15:39:19 +00:00 C9800-L-universalk9_wlc.2020-10-20_14.57_yavadhan.SSA.bin269809 drwx 4096 Oct 19 2020 23:41:49 +00:00 core44 -rw- 1104751981 Oct 19 2020 17:42:12 +00:00 C9800-L-universalk9_wlc.BLD_POLARIS_DEV_LATEST_20201018_053825_2.SSA.bin43 -rw- 1104286975 Oct 16 2020 12:05:47 +00:00 C9800-L-universalk9_wlc.BLD_POLARIS_DEV_LATEST_20201010_001654_2.SSA.binDevice# test wireless redundancy packetdump start filter port 2300Redundancy Port PacketDump StartPacket capture started on RP port with port filter 2300.

To check connection between the two HA Ports (RP) and check if there are any drops, delays, or jitter in the connection, use the following command:

Device# test wireless redundancy rpingRedundancy Port pingPING 169.254.64.60 (169.254.64.60) 56(84) bytes of data.64 bytes from 169.254.64.60: icmp_seq=1 ttl=64 time=0.083 ms64 bytes from 169.254.64.60: icmp_seq=2 ttl=64 time=0.091 ms64 bytes from 169.254.64.60: icmp_seq=3 ttl=64 time=0.074 ms--- 169.254.64.60 ping statistics ---3 packets transmitted, 3 received, 0% packet loss, time 2041msrtt min/avg/max/mdev = 0.074/0.082/0.091/0.007 mstest wireless redundancy

To see the HA port interface setting status, use the show platform hardware slot R0 ha_port interface stats command.

Device# show platform hardware slot R0 ha_port interface statsHA Portha_port Link encap:Ethernet HWaddr 70:18:a7:c8:80:70 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) Memory:e0900000-e0920000Settings for ha_port: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: noNIC statistics: rx_packets: 0 tx_packets: 0 rx_bytes: 0 tx_bytes: 0 rx_broadcast: 0 tx_broadcast: 0 rx_multicast: 0 tx_multicast: 0 multicast: 0 collisions: 0 rx_crc_errors: 0 rx_no_buffer_count: 0 rx_missed_errors: 0 tx_aborted_errors: 0 tx_carrier_errors: 0 tx_window_errors: 0 tx_abort_late_coll: 0 tx_deferred_ok: 0 tx_single_coll_ok: 0 tx_multi_coll_ok: 0 tx_timeout_count: 0 rx_long_length_errors: 0 rx_short_length_errors: 0 rx_align_errors: 0 tx_tcp_seg_good: 0 tx_tcp_seg_failed: 0 rx_flow_control_xon: 0 rx_flow_control_xoff: 0 tx_flow_control_xon: 0 tx_flow_control_xoff: 0 rx_long_byte_count: 0 tx_dma_out_of_sync: 0 tx_smbus: 0 rx_smbus: 0 dropped_smbus: 0 os2bmc_rx_by_bmc: 0 os2bmc_tx_by_bmc: 0 os2bmc_tx_by_host: 0 os2bmc_rx_by_host: 0 tx_hwtstamp_timeouts: 0 rx_hwtstamp_cleared: 0 rx_errors: 0 tx_errors: 0 tx_dropped: 0 rx_length_errors: 0 rx_over_errors: 0 rx_frame_errors: 0 rx_fifo_errors: 0 tx_fifo_errors: 0 tx_heartbeat_errors: 0 tx_queue_0_packets: 0 tx_queue_0_bytes: 0 tx_queue_0_restart: 0 tx_queue_1_packets: 0 tx_queue_1_bytes: 0 tx_queue_1_restart: 0 rx_queue_0_packets: 0 rx_queue_0_bytes: 0 rx_queue_0_drops: 0 rx_queue_0_csum_err: 0 rx_queue_0_alloc_failed:0 rx_queue_1_packets: 0 rx_queue_1_bytes: 0 rx_queue_1_drops: 0 rx_queue_1_csum_err: 0 rx_queue_1_alloc_failed:0

Bringing Down Wireless Management Interface Faster

In case of a switchover in ACI deployments, APs and clients are dropped because of interleaving traffic between the old and the new active controller. To resolve this issue, bring down the traffic from the old active controller faster. You can do this by bringing down the wireless management interface as soon as a failure is detected. When the wireless management interface shuts down, the traffic that is sourced from the old active wireless management interface stops. This avoids conflicts in the management IP address. The standby controller transitions to the role of the active controller with a new IP-MAC binding.

Note	The IP Data-Plane Learning feature in an ACI deployment tracks the following: A duplicate MAC address for the same IP. Alarm that blocks the IP address for a configured duration.

During failure detection, the controller sets up the chassis property non-participant . In IP Data-Plane Learning feature, listen to the property for bringing down the wireless management interface and shutting down traffic in the old active controller faster, thereby avoiding any kind of interleaving traffic between the old and new active controllers.

Disabling Fast Switchover Notification

This mechanism provides more control to avoid interleaving traffic.

During failure handling, the active controller sends an explicit notification to the standby controller, stating that it is going down. This triggers the standby node to take over as the active node. In the event of failure, you can use the disable fast switchover notification option to control the explicit notification from active to standby. In the absence of explicit notification, the standby controller takes over as the active controller on the basis of keepalive timeout.

Note	You can configure the keepalive timeout so that you have control over when the traffic from the new active controller begins if a failure occurs. In such a failure scenario, the switchover also gets delayed.

When you enable this option, the active controller cannot send an explicit failure notification message to the standby controller. The standby controller relies solely on the keepalive timeout failures to detect when the active controller went down.

This delays the keepalive timeout in the commencing traffic in the new active controller, thus avoiding the overlapping traffic from the old active controller. Therefore, disabling fast switchover notification increases the switchover duration by the additional keepalive timeout duration.

GARP Burst

During a controller switchover event, the GARP traffic is generated in burst that overwhelms the ARP learning of ACI. This feature devises a way to retransmit the GARP packet at a much lower rate after a switchover from a new active controller.

Procedure

Procedure

Procedure

Active Controller

The primary address on the active controller is the management IP address. The secondary IPv4 address on the management VLAN is the RMI IP address for the active controller. Do not configure the secondary IPv4 addresses explicitly because a single secondary IPv4 address is configured automatically by RMI under the RMI.

Standby Controller

The standby controller does not have the wireless management IP configured; it has the RMI IP address configured as the primary IP address. When the standby controller becomes active, the management IP address becomes the primary IP address and the RMI IP address becomes the secondary IP address. If the interface on the active controller is administratively down, the same state is reflected on the standby controller.

Dual Stack Support on Management VLAN with RMI

Dual stack refers to the fact that the wireless management interface can be configured with IPv4 and IPv6 addresses. If an RMI IPv4 address is configured along with an IPv4 management IP address, you can additionally configure an IPv6 management address on the wireless management interface. This IPv6 management IP address will not be visible on the standby controller.

If an RMI IPv6 address is configured along with an IPv6 management IP address, you can additionally configure an IPv4 management address on the wireless management interface. This IPv4 management IP address will not be visible on the standby controller.

Therefore, you can monitor only the IPv6 gateway when the RMI IPv6 address is configured, or only the IPv4 gateway when the RMI IPv4 address is configured.

Note	The RMI feature supports the RMI IPv4 or IPv6 addresses.

RMI-Based High-Availability Pairing

You should consider the following scenarios for HA pairing:

• Fresh Installation

• Already Paired Controllers

• Upgrade Scenario

• Downgrade Scenario

Dynamic HA pairing requires both the active controller and the standby controller to reload. However, dynamic HA pairing occurs on the Cisco Catalyst 9800-L Wireless Controller, Cisco Catalyst 9800-40 Wireless Controller, and the Cisco Catalyst 9800-80 Wireless Controller when one of them reloads and becomes the standby controller.

Note	Chassis numbers identify individual controllers. Unique chassis numbers must be configured before forming an HA pair.

HA Pairing Without Previous Configuration

When HA pairing is done for the first time, no ROMMON variables are found for the RP IP addresses. You can choose from the existing privileged EXEC mode RP-based commands or the RMI IP-based mechanisms. However, the privileged EXEC mode RP-based commands will be deprecated soon. If you use Cisco Catalyst Center, you can choose the privileged EXEC mode RP-based CLI mechanism till the Cisco Catalyst Center migrates to support the RMI.

The RP IPs are derived from the RMI IPs after an HA pair is formed. Also, the privileged EXEC mode RP-based CLI method of clearing and forming an HA pair is not allowed after the RMI IP-based HA mechanism is chosen.

Note	Although you can choose RP or RMI for a fresh installation, we recommend that you use RMI install method. To view the ROMMON variables, use the show romvars command.

If you choose the privileged EXEC RP-based CLI mechanism, the RP IPs are configured the same way as in the 16.12 release.

The following occurs when the RMI-based HA pairing is done on a brand-new system:

• RP IPs are derived from RMI IPs and used in HA pairing.

• Privileged EXEC mode RP-based CLIs are blocked.

Note

The RMI migration is supported from Cisco Catalyst Center, 2.3.3.x release version. The following are the limitations observed during RMI migration: The negative cases fail due to the following reasons: When devices are not reachable. When non-Cisco Catalyst 9800 Series Wireless Controllers are in use. When an earlier controller version (Cisco IOS XE 17.3) is in use. When High Availability is not configured. When High Availability RMI is already configured. When High Availability is upgraded to RMI-based High Availability for Cisco IOS XE release version greater than or equal to 17.3. When upgrading to an already failed High Availability paired controller. The controller GUI prohibits applying RMI migration configuration to High Availability failed devices.

Paired Controllers

If the controllers are already in an HA pair, the existing EXEC mode RP-based commands will continue to be used. You can enable RMI to migrate to the RMI-based HA pairing.

If the controllers are already paired and RMI is configured, it will overwrite the RP IPs with the RMI-derived IPs. The HA pair will not be disturbed immediately, but the controllers will pick up the new IP when the next reload happens. The RMI feature mandates a reload for the feature to be effective. When both the controllers are reloaded, they come up as a pair with the new RMI-derived RP IPs.

The following occurs when the RMI configuration is done:

• The RP IPs derived from the RMI IPs are overwritten, and used for HA pairing.

• If the active and standby controller already exist prior to HA pairing through the EXEC mode RP-based command mechanism, the pair is not interrupted.

• When the pair reloads later, the new RP IPs are used.

• EXEC mode RP-based commands are blocked.

Upgrading from Cisco IOS XE 16.1.x to a Later Release

A system that is being upgraded can choose to:

• Migrate with the existing RP IP configuration intact—In this case, the existing RP IP configuration will continue to be used. The EXEC mode RP-based commands are used for future modifications.

• Migrate after clearing the HA configuration—In this case, you can choose between the old (EXEC mode RP-based commands) and new RMI-based RP configuration methods.

Note	In case the older configuration is retained, the RMI configuration updates the RP IPs with the IPs derived from the RMI IPs.

Downgrade Scenario

Note	The downgrade scenario given below is not applicable for Cisco IOS XE Amsterdam 17.1.x.

The downgrade scenario will have only the EXEC mode RP-based commands. The following are the two possibilities:

• If the upgraded system used the RMI-based RP configuration.

• If the upgraded system continued to use the EXEC mode RP-based commands.

Note	In the above cases, the downgraded system uses the EXEC mode RP-based commands to modify the configuration. However, the downgraded system will continue to use the new derived RP IPs.

Note

When you downgrade the Cisco Catalyst 9800 Series Wireless Controller to any version below 17.1 and if the mDNS gateway is enabled on the WLAN/RLAN/GLAN interfaces, the mdns-sd-interface gateway goes down after the downgrade. To enable the mDNS gateway on the WLAN/RLAN/GLAN interfaces in 16.12 and earlier versions, use the following commands: wlan test 1 test mdns-sd gateway To enable the mDNS gateway on the WLAN/RLAN/GLAN interfaces from version 17.1 onwards, use the following command: mdns-sd-interface gateway

Gateway Monitoring

From Cisco IOS XE Amsterdam 17.2.1 onwards, the method to configure the gateway IP has been modified. The ip default-gateway gateway-ip command is not used. Instead, the gateway IP is selected based on the static routes configured. From among the static routes configured, the gateway IP that falls in the same subnet as the RMI subnet (the broadest mask and least gateway IP) is chosen. If no matching static route is found, gateway failover will not work (even if management gateway-failover is enabled).

Before configuring RMI + RP using GUI, ensure that WMI is available.

Procedure

Procedure

Procedure

Procedure

From RMI IPv4

1. Unconfigure the RMI IPv4 using the following CLIs:

   Device# conf tDevice(config)# no redun-management interface <vlan_name> chassis 1 address <ip_address1> chassis 2 address <ip_address2>

   Note	This CLI unconfigures RMI on both the controllers.

2. Note	Take a backup of the running config on active before you reload the controller.

   Reload the controller.

3. Copy the backed up config to the running config on the box which would have lost all the config.

4. Configure the RMI IPv6 on both the controllers. For information on the CLI, see .

5. Reload the controller.

From HA Pairing (Without RMI)

For information on HA pairing, see Configuring Redundancy Management Interface (GUI).

Feature Scenarios

• To monitor the health of the standby directly from the standby controller using Standby RMI IP.

• To get syslogs from the standby controller using the Standby RMI IP.

Use Cases

• Enabling SNMP agent and programmatic interfaces on the standby controller: You can directly perform an SNMP query or programmatic interface query to the standby’s RMI IP and active controller.

• Enabling syslogs on the standby controller: You can directly get the standby syslogs from the standby controller.

RADIUS Accounting Support

Whenever you log in to a standby device, the RADIUS start record must be sent to the external RADIUS server. Similarly, when you log out of a device, the RADIUS stop record must be sent to the external RADIUS server.

TACACS+ Authentication Support

Users are authenticated through the RMI using the external TACACS+ server. The username and password are evaluated in the TACACS+ server. Depending on the response received from the server, a user will be able to log in to the standby device.

TACACS+ Accounting Support

Whenever you log in to the standby device, the TACACS+ accounting start record must be sent to the external TACACS+ server. Similarly, when you log out of a device, the TACACS+ accounting stop record must be sent to the external TACACS+ server.

Note	The following configuration must be in place to configure AAA to send the accounting packets: aaa accounting exec {default | named-list} start-stop group {RAD | tac-group-name}

Note	The TACACS+ login to the standby device is not supported when TACACS+ server is configured with hostname.

CISCO-LWAPP-HA-MIB

The CISCO-LWAPP-HA-MIB monitors the health parameters of the standby controller, that is, memory, CPU, port status, power statistics, peer gateway latencies, and so on.

You can query the following MIB objects of CISCO-LWAPP-HA-MIB.

CISCO-PROCESS-MIB

The CISCO-PROCESS-MIB monitors CPU and process statistics. Use it to monitor CPU-related or memory-related BINOS processes. The standby CISCO-PROCESS-MIB can be monitored using the active controller.

ENTITY-MIB

The ENTITY-MIB is used to monitor hardware details of the active and standby controllers using the active controller.

Note	The standby Route Processor (RP) sensors are appended in the active RP sensors.

You can monitor parameters such as CPU, memory, sensors, and interface status on a standby controller using programmatic interfaces such as NETCONF and RESTCONF. The RMI IP of the standby controller can be used for access to the following operational models:

The models can be accessed through .

• Cisco-IOS-XE-device-hardware-oper.yang

• Cisco-IOS-XE-process-cpu-oper.yang

• Cisco-IOS-XE-platform-software-oper.yang

• Cisco-IOS-XE-process-memory-oper.yang

• Cisco-IOS-XE-interfaces-oper.yang

For more information on the YANG models, see the Programmability Configuration Guide, Cisco IOS XE Amsterdam 17.3.x.

This section describes the different commands that can be used to monitor the standby device.

You can connect to the standby controller through SSH using the RMI IP of the standby controller. The user credentials must have been configured already. Both local authentication and RADIUS authentication are supported.

Note	The redun-management command needs to be configured on both the controllers, primary and standby, prior to high availability (HA) pairing.

Monitoring Port State

The following is a sample output of the show interfaces interface-name command:

Device-standby# show interfaces GigabitEthernet1  GigabitEthernet1 is down, line protocol is down Shadow state is up, true line protocol is up Hardware is CSR vNIC, address is 000c.2909.33c2 (bia 000c.2909.33c2) MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full Duplex, 1000Mbps, link type is force-up, media type is Virtual output flow-control is unsupported, input flow-control is unsupported ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:06, output 00:00:24, output hang never Last clearing of "show interface" counters never Input queue: 30/375/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/40 (size/max) 5 minute input rate 389000 bits/sec, 410 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 3696382 packets input, 392617128 bytes, 0 no buffer Received 0 broadcasts (0 multicasts) 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 watchdog, 0 multicast, 0 pause input 18832 packets output, 1218862 bytes, 0 underruns Output 0 broadcasts (0 multicasts) 0 output errors, 0 collisions, 2 interface resets 3 unknown protocol drops 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier, 0 pause output 0 output buffer failures, 0 output buffers swapped out

The following is a sample output of the show ip interface brief command:

Device# show ip interface briefInterface IP-Address OK? Method Status ProtocolGigabitEthernet1 unassigned YES unset down down GigabitEthernet0 unassigned YES NVRAM administratively down down Capwap1 unassigned YES unset up up Capwap2 unassigned YES unset up up Capwap3 unassigned YES unset up up Capwap10 unassigned YES unset up up Vlan1 unassigned YES NVRAM down down Vlan56 unassigned YES unset down down Vlan111 111.1.1.85 YES NVRAM up up 

Monitoring CPU or Memory

The following is a sample output of the show process cpu sorted 5sec command:

Device-standby# show process cpu sorted 5secCPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 0% PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process 10 1576556 281188 5606 0.15% 0.05% 0.05% 0 Check heaps 232 845057 54261160 15 0.07% 0.05% 0.06% 0 IPAM Manager 595 177 300 590 0.07% 0.02% 0.01% 2 Virtual Exec 138 1685973 108085955 15 0.07% 0.08% 0.08% 0 L2 LISP Punt Pro 193 19644 348767 56 0.07% 0.00% 0.00% 0 DTP Protocol 5 0 1 0 0.00% 0.00% 0.00% 0 CTS SGACL db cor 4 24 15 1600 0.00% 0.00% 0.00% 0 RF Slave Main Th 6 0 1 0 0.00% 0.00% 0.00% 0 Retransmission o 7 0 1 0 0.00% 0.00% 0.00% 0 IPC ISSU Dispatc 2 117631 348801 337 0.00% 0.00% 0.00% 0 Load Meter 8 0 1 0 0.00% 0.00% 0.00% 0 EDDRI_MAIN 

To check CPU and memory utilization of binOS processes, run the following command:

Device-standby# show platform software process slot chassis standby R0 monitor top - 23:24:14 up 8 days, 3:38, 0 users, load average: 0.69, 0.79, 0.81 Tasks: 433 total, 1 running, 431 sleeping, 1 stopped, 0 zombie %Cpu(s): 1.7 us, 2.8 sy, 0.0 ni, 95.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 stMiB Mem : 32059.2 total, 21953.7 free, 4896.8 used, 5208.6 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 26304.6 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND23565 root 20 0 2347004 229116 130052 S 41.2 0.7 5681:44 ucode_pkt+2306 root 20 0 666908 106760 46228 S 5.9 0.3 15:06.14 smand 22807 root 20 0 3473004 230020 152120 S 5.9 0.7 510:56.90 fman_fp_i+1 root 20 0 14600 11324 7424 S 0.0 0.0 0:31.07 systemd 2 root 20 0 0 0 0 S 0.0 0.0 0:00.28 kthreadd 3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp 4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0+7 root 20 0 0 0 0 I 0.0 0.0 0:00.49 kworker/u+8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu+9 root 20 0 0 0 0 S 0.0 0.0 0:03.26 ksoftirqd+...32258 root 20 0 57116 3432 2848 S 0.0 0.0 0:00.00 rotee32318 root 20 0 139560 9500 7748 S 0.0 0.0 0:55.67 pttcd32348 root 20 0 31.6g 3.1g 607364 S 0.0 9.8 499:12.04 linux_ios+32503 root 20 0 3996 3136 2852 S 0.0 0.0 0:00.00 stack_snt+32507 root 20 0 3700 1936 1820 S 0.0 0.0 0:00.00 sntp

Monitoring Hardware

The following is a sample output of the show environment summary command:

Device# show environment summaryNumber of Critical alarms: 0Number of Major alarms: 0Number of Minor alarms: 0 Slot Sensor Current State Reading Threshold(Minor,Major,Critical,Shutdown) ---------- -------------- --------------- ------------ --------------------------------------- P0 Vin Normal 231 V AC na P0 Iin Normal 2 A na P0 Vout Normal 12 V DC na P0 Iout Normal 30 A na P0 Temp1 Normal 25 Celsius(na ,na ,na ,na )(Celsius) P0 Temp2 Normal 31 Celsius(na ,na ,na ,na )(Celsius) P0 Temp3 Normal 37 Celsius(na ,na ,na ,na )(Celsius) R0 VDMB1: VX1 Normal 1226 mV na R0 VDMB1: VX2 Normal 6944 mV na R0 Temp: DMB IN Normal 26 Celsius(45 ,55 ,65 ,70 )(Celsius) R0 Temp: DMB OUT Normal 40 Celsius(70 ,75 ,80 ,85 )(Celsius) R0 Temp: Yoda 0 Normal 54 Celsius(95 ,105,110,115)(Celsius) R0 Temp: Yoda 1 Normal 62 Celsius(95 ,105,110,115)(Celsius) R0 Temp: CPU Die Normal 43 Celsius(100,110,120,125)(Celsius) R0 Temp: FC FANS Fan Speed 70% 26 Celsius(29 ,39 ,0 )(Celsius) R0 VDDC1: VX1 Normal 1005 mV na R0 VDDC1: VX2 Normal 7084 mV na R0 VDDC2: VH Normal 12003mV na R0 Temp: DDC IN Normal 25 Celsius(55 ,65 ,75 ,80 )(Celsius) R0 Temp: DDC OUT Normal 35 Celsius(75 ,85 ,95 ,100)(Celsius) P0 Stby Vin Normal 230 V AC na P0 Stby Iin Normal 2 A na P0 Stby Vout Normal 12 V DC na P0 Stby Iout Normal 32 A na P0 Stby Temp1 Normal 24 Celsius(na ,na ,na ,na )(Celsius) P0 Stby Temp2 Normal 29 Celsius(na ,na ,na ,na )(Celsius) P0 Stby Temp3 Normal 35 Celsius(na ,na ,na ,na )(Celsius) R0 Stby VDMB1: VX1 Normal 1225 mV na R0 Stby VDMB1: VX2 Normal 6979 mV na R0 Stby VDMB2: VX2 Normal 5005 mV na R0 Stby VDMB2: VX3 Normal 854 mV na R0 Stby VDMB3: VX1 Normal 972 mV na R0 Stby Temp: DMB INormal 22 Celsius(45 ,55 ,65 ,70 )(Celsius) R0 Stby Temp: DMB ONormal 32 Celsius(70 ,75 ,80 ,85 )(Celsius) R0 Stby Temp: Yoda Normal 43 Celsius(95 ,105,110,115)(Celsius) R0 Stby Temp: Yoda Normal 45 Celsius(95 ,105,110,115)(Celsius) R0 Stby Temp: CPU DNormal 33 Celsius(100,110,120,125)(Celsius) R0 Stby Temp: FC FAFan Speed 70% 22 Celsius(29 ,39 ,0 )(Celsius) R0 Stby VDDC1: VX1 Normal 1005 mV na R0 Stby VDDC1: VX2 Normal 7070 mV na R0 Stby VDDC2: VX2 Normal 752 mV na R0 Stby VDDC2: VX3 Normal 750 mV na R0 Stby Temp: DDC INormal 22 Celsius(55 ,65 ,75 ,80 )(Celsius) R0 Stby Temp: DDC ONormal 28 Celsius(75 ,85 ,95 ,100)(Celsius)

Note	The command displays both active and standby hardware details.

Note

The show environment summary command displays data only for physical appliances such as Cisco Catalyst 9800-80 Wireless Controller, Cisco Catalyst 9800-40 Wireless Controller, Cisco Catalyst 9800-L Wireless Controller, and Cisco Catalyst 9800 Embedded Wireless Controller for Switch. The command does not display data for Cisco Catalyst 9800 Wireless Controller for Cloud.

To verify the status of the gateway-monitoring configuration on an active controller, run the following command:

Device# show redundancy statesmy state = 13 -ACTIVEpeer state = 8 -STANDBY HOTMode = DuplexUnit = PrimaryUnit ID = 1Redundancy Mode (Operational) = ssoRedundancy Mode (Configured) = ssoRedundancy State = ssoMaintenance Mode = DisabledManual Swact = enabledCommunications = Upclient count = 129client_notification_TMR = 30000 millisecondsRF debug mask = 0x0Gateway Monitoring = DisabledGateway monitoring interval = 8 secs

To verify the status of the gateway-monitoring configuration on a standby controller, run the following command:

Device-stby# show redundancy statesmy state = 8 -STANDBY HOTpeer state = 13 -ACTIVEMode = DuplexUnit = PrimaryUnit ID = 2Redundancy Mode (Operational) = ssoRedundancy Mode (Configured) = ssoRedundancy State = ssoMaintenance Mode = DisabledManual Swact = cannot be initiated from this the standby unitCommunications = Upclient count = 129client_notification_TMR = 30000 millisecondsRF debug mask = 0x0Gateway Monitoring = DisabledGateway monitoring interval = 8 secs

Verify the RMI IPv4 configuration.

Device# show running-config interface vlan management-vlanBuilding configuration...Current configuration : 109 bytes!interface Vlan90ip address 9.10.90.147 255.255.255.0 secondaryip address 9.10.90.41 255.255.255.0end 

To verify the interface configuration for a standby controller, use the following command:

Device-stby# show running-config interface vlan 90Building configuration... Current configuration : 62 bytes!interface Vlan90ip address 9.10.90.149 255.255.255.0end

To verify the chassis redundancy management interface configuration for an active controller, use the following command:

Device# show chassis rmiChassis/Stack Mac Address : 000c.2964.1eb6 - Local Mac AddressMac persistency wait time: IndefiniteH/W CurrentChassis# Role Mac Address Priority Version State IP RMI-IP--------------------------------------------------------------------------------------------------------*1 Active 000c.2964.1eb6 1 V02 Ready 169.254.90.147 9.10.90.1472 Standby 000c.2975.3aa6 1 V02 Ready 169.254.90.149 9.10.90.149

To verify the chassis redundancy management interface configuration for a standby controller, use the following command:

Device-stby# show chassis rmiChassis/Stack Mac Address : 000c.2964.1eb6 - Local Mac AddressMac persistency wait time: Indefinite H/W CurrentChassis# Role Mac Address Priority Version State IP RMI-IP------------------------------------------------------------------------------------------------1 Active 000c.2964.1eb6 1 V02 Ready 169.254.90.147 9.10.90.147*2 Standby 000c.2975.3aa6 1 V02 Ready 169.254.90.149 9.10.90.149

To verify the ROMMON variables on an active controller, use the following command:

Device# show romvar | include RMIRMI_INTERFACE_NAME = Vlan90RMI_CHASSIS_LOCAL_IP = 9.10.90.147RMI_CHASSIS_REMOTE_IP = 9.10.90.149

To verify the ROMMON variables on a standby controller, use the following command:

Device-stby# show romvar | include RMIRMI_INTERFACE_NAME = Vlan90RMI_CHASSIS_LOCAL_IP = 9.10.90.149RMI_CHASSIS_REMOTE_IP = 9.10.90.147

To verify the switchover reason, use the following command:

Device# show redundancy switchover historyIndex Previous Current Switchover Switchover active active reason time----- -------- ------- ---------- ---------- 1 2 1 Active lost GW 17:02:29 UTC Mon Feb 3 2020 

To verify the chassis redundancy management interface configuration for both active and standby controllers, run the following command:

Device# show chassis rmiChassis/Stack Mac Address : 00a3.8e23.a540 - Local Mac AddressMac persistency wait time: IndefiniteLocal Redundancy Port Type: Twisted Pair H/W CurrentChassis# Role Mac Address Priority Version State IP RMI-IP--------------------------------------------------------------------------------------------- 1 Standby 706d.1536.23c0 1 V02 Ready 169.254.254.17 2020:0:0:1::211 *2 Active 00a3.8e23.a540 1 V02 Ready 169.254.254.18 2020:0:0:1::212

To verify the RMI related ROMMON variables for both active and standby controllers, run the following command

Device# show romvar | i RMIRMI_INTERFACE_NAME = Vlan52RMI_CHASSIS_LOCAL_IPV6 = 2020:0:0:1::212RMI_CHASSIS_REMOTE_IPV6 = 2020:0:0:1::211

To verify the Redundancy Port Interface (RIF) resource status in an active instance, run the following command:

Device# show platform software rif-mgr chassis active R0 resource-statusRIF Resource Status RP Status : Up RMI Status : Up Current Chassis State : Active Peer Chassis State : Standby

To verify the RIF resource status in a standby instance, run the following command:

Device# show platform software rif-mgr chassis standby R0 resource-statusRIF Resource Status RP Status : Up RMI Status : Up Current Chassis State : Standby Peer Chassis State : Active

To verify the RMI link re-establishment count and the time since the RMI link is Up in the active instance, run the following command:

Device# show platform software rif-mgr chassis active R0 rmi-connection-detailsRMI Connection Details RMI Link re-establish count : 2 RMI Link Uptime : 21 hours 8 minutes 43 seconds RMI Link Upsince : 08/05/2021 13:46:01

To verify the RMI link re-establishment count and the time since the RMI link is Down in the active instance, run the following command:

Device# show platform software rif-mgr chassis active R0 rmi-connection-detailsRMI Connection Details RMI Link re-establish count : 1 RMI Link Downtime : 28 seconds RMI Link Downsince : 07/16/2021 03:19:11

To verify the RMI link re-establishment count and the time since the RMI link is Up in the standby instance, run the following command:

Device# show platform software rif-mgr chassis standby R0 rmi-connection-detailsRMI Connection Details RMI Link re-establish count : 1 RMI Link Uptime : 1 hour 39 minute 9 seconds RMI Link Upsince : 07/16/2021 01:31:41

To verify the RMI link re-establishment count and the time since the RMI link is Down in the standby instance, run the following command:

Device# show platform software rif-mgr chassis standby R0 rmi-connection-detailsRMI Connection Details RMI Link re-establish count : 1 RMI Link Downtime : 22 seconds RMI Link Downsince : 07/16/2021 03:19:17

To verify the RP link re-establishment count and the time since the RP link is UP for days in the active instance, run the following command:

Device# show platform software rif-mgr chassis active R0 rp-connection-detailsRP Connection Details RP Connection Uptime : 12 days 17 hours 1 minute 39 seconds RP Connection Upsince : 07/03/2021 07:06:20

To verify the RP link re-establishment count and the time since the RP link is Down in the active instance, run the following command:

Device# show platform software rif-mgr chassis active R0 rp-connection-detailsRP Connection Details RP Connection Downtime : 4 seconds RP Connection Downsince : 07/16/2021 03:33:04

To verify the RP link re-establishment count and the time since the RP link is UP in the standby instance, run the following command:

Device# show platform software rif-mgr chassis standby R0 rp-connection-detailsRP Connection Details RP Connection Uptime : 12 days 17 hours 2 minutes 1 second RP Connection Upsince : 07/03/2021 07:05:58

To verify the RP link re-establishment count and the time since the RP link is Down in the standby instance, run the following command:

Device# show platform software rif-mgr chassis standby R0 rp-connection-detailsRP Connection Details RP Connection Downtime : 22 seconds RP Connection Downsince : 07/16/2021 03:19:17

To verify the RIF and stack manager internal statistics in the active instance, run the following command:

Device# show platform software rif-mgr chassis active R0 rif-stk-internal-statsRIF Stack Manager internal stats Stack-mgr reported RP down : False DAD link status reported to Stack-Mgr : True

To verify the RIF and stack manager internal statistics in the standby instance, run the following command:

Device# show platform software rif-mgr chassis standby R0 rif-stk-internal-statsRIF Stack Manager internal stats Stack-mgr reported RP down : False DAD link status reported to Stack-Mgr : True

To verify the number of packets sent or received for each type in the active instance, run the following command:

Device# show platform software rif-mgr chassis active R0 lmp-statisticsLMP StatisticsInfo Type Sent : 6Solicit Info Type Sent : 0Unsolicit Info Type Sent : 6Reload Type Sent : 0Recovery Type Sent : 1 Gateway Info Type Sent : 0Enquiry Type Sent : 0Solicit Enquiry Type Sent : 0Unsolicit Enquiry Type Sent : 0 Info Type Received : 5Solicit Info Type Received : 2Unsolicit Info Type Received : 3Reload Type Received : 0Recovery Type Received : 0Gateway Info Type Received : 4Enquiry Type Received : 0Solicit Enquiry Type Received : 0Unsolicit Enquiry Type Received : 0

To verify the number of packets sent or received for each type in the standby instance, run the following command:

Device# show platform software rif-mgr chassis standby R0 lmp-statisticsLMP StatisticsInfo Type Sent : 6Solicit Info Type Sent : 0Unsolicit Info Type Sent : 6Reload Type Sent : 0Recovery Type Sent : 0Gateway Info Type Sent : 4Enquiry Type Sent : 0Solicit Enquiry Type Sent : 0Unsolicit Enquiry Type Sent : 0Info Type Received : 5Solicit Info Type Received : 3Unsolicit Info Type Received : 2Reload Type Received : 0Recovery Type Received : 1Gateway Info Type Received : 0Enquiry Type Received : 0Solicit Enquiry Type Received : 0Unsolicit Enquiry Type Received : 0

Procedure

Procedure

Procedure

Procedure

Use the following show commands to view the LLDP details independently in the active and standby controller.

To verify the timer and status in the active and standby controller, use the following command:

Device# show lldpGlobal LLDP Information: Status: ACTIVE LLDP advertisem*nts are sent every 30 seconds LLDP hold time advertised is 120 seconds LLDP interface reinitialisation delay is 2 seconds

To verify the neighbor details in the active controller, use the following command:

Device# show lldp neighborsCapability codes: (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device (W) WLAN Access Point, (P) Repeater, (S) Station, (O) OtherDevice ID Local Intf Hold-time Capability Port ID9500-SW Tw0/0/0 120 B,R Twe1/0/14

To verify the neighbor details in the standby controller, use the following command:

Device# show lldp neighborsCapability codes:(R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device(W) WLAN Access Point, (P) Repeater, (S) Station, (O) OtherDevice ID Local Intf Hold-time Capability Port ID9500-SW Tw0/0/0 120 B,R Twe1/0/13Total entries displayed: 1

To verify the LLDP neighbor (TLV) detail, use the following command:

Device# show lldp neighbors detail------------------------------------------------Local Intf: Te0/0/0Chassis id: 2cd0.2d62.be80Port id: Te1/1Port Description: TenGigabitEthernet1/1System Name: HSRP-ROUTER-1-15.cisco.com System Description:Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500e-UNIVERSAL-M), Version 03.09.00.E RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2016 by Cisco Systems, Inc.Compiled Tue 19-Jul Time remaining: 99 secondsSystem Capabilities: B,REnabled Capabilities: B,RManagement Addresses: IP: 8.109.0.1 IPV6: 2001:12:1::2Auto Negotiation - not supportedPhysical media capabilities: Other/unknownMedia Attachment Unit type - not advertisedVlan ID: 109Peer Source MAC: 2cd0.2d62.be80

To verify the LLDP details in the uplink switch, use the following command:

Device# show lldp neighbors detail------------------------------------------------Local Intf: Te1/1Chassis id: d4e8.80b3.0420Port id: Te0/0/0Port Description: TenGigabitEthernet0/0/0System Name: WLC-BGL15.cisco.com System Description:Cisco IOS Software [Bangalore], C9800 Software (C9800_IOSXE-K9), Experimental Version 17.9.20220630:200739Copyright (c) 1986-2022 by Cisco Systems, Inc.Compiled Thu 30-Jun-22 13:19 Time remaining: 107 secondsSystem Capabilities: B,REnabled Capabilities: RManagement Addresses: IP: 8.109.0.47 IPV6: FD09:8:109::45Auto Negotiation - not supportedPhysical media capabilities - not advertisedMedia Attachment Unit type - not advertisedVlan ID: 109

To verify LLDP packet errors, use the following command:

Device# show lldp errorsLLDP errors/overflows:Total memory allocation failures: 0Total encapsulation failures: 0Total input queue overflows: 0Total table overflows: 0

To verify LLDP traffic statistics, use the following command:

Device# show lldp trafficLLDP traffic statistics:Total frames out: 18470Total entries aged: 0Total frames in: 6156Total frames received in error: 0Total frames discarded: 0Total TLVs discarded: 0Total TLVs unrecognized: 0

This table provides release and related information about the feature explained in this section.

This feature is also available in all the releases subsequent to the one in which they are introduced in, unless noted otherwise.

To view the reload history details, use the following command:

Device# show reload-historyReload History:Reload Index: 1Reload Code: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 01:33:44 UTC Wed Nov 30 2022Reload Index: 2Reload Code: Critical Process FaultReload Description: Critical process stack_mgr fault on rp_0_0 (rc=137), system report at bootflash:core/Yang_Test-system-report_20221130-012929-UTC.tar.gzReload Severity: Abnormal RebootReload Time: 01:31:11 UTC Wed Nov 30 2022Reload Index: 3Reload Code: Image InstallReload Description: Image Install Reload Severity: Normal RebootReload Time: 01:25:03 UTC Wed Nov 30 2022Reload Index: 4Reload Code: Critical Process FaultReload Description: Critical process rif_mgr fault on rp_0_0 (rc=137), system report at bootflash:core/Yang_Test-system-report_20221130-011127-UTC.tar.gzReload Severity: Abnormal RebootReload Time: 01:13:08 UTC Wed Nov 30 2022Reload Index: 5Reload Code: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 01:08:26 UTC Wed Nov 30 2022Reload Index: 6Reload Code: Critical Process FaultReload Description: Critical process wncmgrd fault on rp_0_0 (rc=137), system report at bootflash:core/Yang_Test-system-report_20221130-010338-UTC.tar.gzReload Severity: Abnormal RebootReload Time: 01:05:23 UTC Wed Nov 30 2022Reload Index: 7Reload Code: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 01:01:09 UTC Wed Nov 30 2022Reload Index: 8Reload Code: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 00:57:27 UTC Wed Nov 30 2022Reload Index: 9Reload Code: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 00:22:34 UTC Wed Nov 30 2022Reload Index: 10Reload Code: Fast SwitchoverReload Description: redundancy force-switchoverReload Severity: Normal RebootReload Time: 23:40:01 UTC Tue Nov 29 2022

To view reason for the last reload, use the following command:

Device# show platform software tdl-database content ios device dataDevice Current time: 04:06:04Device boot time: 01:33:37Software version: Cisco IOS Software [Dublin], C9800-CL Software (C9800-CL-K9_IOSXE), Experimental Version 17.11.20221012:120806 [BLD_POLARIS_DEV_S2C_20221010_023625-1-g5ebdd5c35512:/nobackup/saikarth/polaris_relhis 103]Copyright (c) 1986-2022 by Cisco Systems, Inc.Compiled Wed 12-Oct-22 05:08 by saikarthRommon version: IOS-XE ROMMONLast Reboot reason: Reload CommandReboot reason severity: Normal RebootUnsaved configuration: * Unknown boolean * Reload History:Reload Category: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 11/30/2022 01:33:44 UTCReload Category: Critical Process FaultReload Description: Critical process stack_mgr fault on rp_0_0 (rc=137), system report at bootflash:core/Yang_Test-system-report_20221130-012929-UTC.tar.gzReload Severity: Abnormal RebootReload Time: 11/30/2022 01:31:11 UTCReload Category: Image InstallReload Description: Image Install Reload Severity: Normal RebootReload Time: 11/30/2022 01:25:03 UTCReload Category: Critical Process FaultReload Description: Critical process rif_mgr fault on rp_0_0 (rc=137), system report at bootflash:core/Yang_Test-system-report_20221130-011127-UTC.tar.gzReload Severity: Abnormal RebootReload Time: 11/30/2022 01:13:08 UTCReload Category: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 11/30/2022 01:08:26 UTCReload Category: Critical Process FaultReload Description: Critical process wncmgrd fault on rp_0_0 (rc=137), system report at bootflash:core/Yang_Test-system-report_20221130-010338-UTC.tar.gzReload Severity: Abnormal RebootReload Time: 11/30/2022 01:05:23 UTCReload Category: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 11/30/2022 01:01:09 UTC Reload Category: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 11/30/2022 00:57:27 UTC Reload Category: ReloadReload Description: Reload CommandReload Severity: Normal RebootReload Time: 11/30/2022 00:22:34 UTC Reload Category: Fast SwitchoverReload Description: redundancy force-switchoverReload Severity: Normal RebootReload Time: 11/29/2022 23:40:01 UTC