CiscoL4L7RedState
The redundancy state of the device in redundancy configuration. 'other' : other than values defined below. 'nonRedundant' : redundancy has not been configured. 'initializing' : establish necessary system services 'negotiation' : peer unit discovery and negotiation 'active' : device is in active state. It is servicing the requests. 'standbyCold' : standby will take over if synchronization is failed using bulk synch mechanism. 'standbyConfig' : The active device receives a notification to send a snapshot of its running-config to the local standby device. 'standbyBulk' : The active device receives a notification to send a snapshot of the current state information for all applications to the standby device. 'standbyHot' : Incremental data synchronization continues. This unit is ready and is able to instantly take over activity. 'standbyWarm' : When the peer software compatibility is warmCompatible ( a state in clrPeerSoftwareCompatibility ) , the redundant groups on standby goes to standbyWarm instead of standbyHot. Whether the bulk config sync fails/passes the transition to standbyBulk is always made and eventually the standby device goes to standbyWarm. The standbyWarm state is similar to standbyHot state ( config mode will be locked, state replication/ config sync are continued ) , but when config-sync failed, there is no move to standbyCold state.
Possible values
10 objects| Number | Name |
|---|---|
| 1 | other |
| 2 | nonRedundant |
| 3 | initializing |
| 4 | negotiation |
| 5 | active |
| 6 | standbyCold |
| 7 | standbyConfig |
| 8 | standbyBulk |
| 9 | standbyHot |
| 10 | standbyWarm |