API Guide

Field Description
PEER RPM
Status
Displays the state of the second RPM, if present
RPM Redundancy
Configuration
Displays the following information:
● which RPM is the preferred Primary on next boot (the redundancy primary
command)
● the data sync method configured (the redundancy synchronize
command)
● the failover type (you cannot change this type; it is software-dependent). Hot
Failover means that the running configuration and routing table are applied
on secondary RPM. Fast Failover means that the running configuration is not
applied on the secondary RPM until failover occurs, and the routing table on line
cards is cleared during failover.
● the status of auto booting the RPM (the redundancy disable-auto-
reboot command)
● the parameter for auto failover limit control (the redundancy auto-
failover-limit command)
●
RPM Failover
Record
Displays the following information:
● RPM failover counter (to reset the counter, use the redundancy reset-
counter command)
● the time and date of the last RPM failover
● the reason for the last RPM failover
Last Data Sync
Record
Displays the data sync information and the timestamp for the data sync:
● Start-up Config is the contents of the startup-config file.
● Line Card Config is the line card types configured and interfaces on those line
cards.
● Runtime Event Log is the contents of the Event log.
● Running Config is the current running-config.
This field only appears when you enter the command from the Primary RPM.
Example
DellEMC# show redundancy
-- RPM Status --
------------------------------------------------
RPM Slot ID: 1
RPM Redundancy Role: Primary
RPM State: Active
RPM SW Version: 7.5.1.0
Link to Peer: Up
-- PEER RPM Status --
------------------------------------------------
RPM State: Standby
RPM SW Version: 7.5.1.0
-- RPM Redundancy Configuration --
------------------------------------------------
Primary RPM: rpm0
Auto Data Sync: Full
Failover Type: Hot Failover
Auto reboot RPM: Enabled
Auto failover limit: 3 times in 60 minutes
-- RPM Failover Record --
------------------------------------------------
Failover Count: 1
Last failover timestamp: Jul 13 2007 21:25:32
Last failover Reason: User request
High Availability (HA)
577