Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"apexChassisRedundancyState",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"unknown",
"(",
"0",
")",
",",
"available",
"(",
"1",
")",
",",
"protected",
"(",
"2",
")",
",",
"unavailable",
"(",
"3",
")",
",",
"synchronizing",
"(",
"4",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"This parameter is applicable for an APEX where chassis redundancy is enabled. This parameter will report the chassis redundancy availability status. These are based on its knowledge about the secondary APEX from heartbeat messages. The APEX configured as primary will report the following values: unknown(0): State of redundancy is not known (heartbeat not received). available(1): Primary is active and secondary is in standby, configurations are synchronized and no critical faults on either of the APEX. protected(2): Primary is fault and secondary is in active. unavailable(3): Configuration not synchronized or primary has not received heartbeat message from secondary. synchronizing(4): Synchronizing configuration between active and standby APEX's. The APEX configured as secondary will report the following values: unknown(0): State of redundancy is not known (heartbeat not received). available(1): Secondary is active and primary is in standby, configurations are synchronized and no critical faults on either of the APEX. protected(2): Secondary is in active and primary is fault state. unavailable(3): Configuration not synchronized or secondary is in fault state or secondary has not received heartbeat message from primary. synchronizing(4): Synchronizing configuration between active and standby APEX's. \"",
"::=",
"{",
"apexChassisRedundancyStatusGeneral",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"unknown",
0
],
[
"available",
1
],
[
"protected",
2
],
[
"unavailable",
3
],
[
"synchronizing",
4
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This parameter is applicable for an APEX where chassis redundancy is enabled. This parameter will report the chassis redundancy availability status. These are based on its knowledge about the secondary APEX from heartbeat messages. The APEX configured as primary will report the following values: unknown(0): State of redundancy is not known (heartbeat not received). available(1): Primary is active and secondary is in standby, configurations are synchronized and no critical faults on either of the APEX. protected(2): Primary is fault and secondary is in active. unavailable(3): Configuration not synchronized or primary has not received heartbeat message from secondary. synchronizing(4): Synchronizing configuration between active and standby APEX's. The APEX configured as secondary will report the following values: unknown(0): State of redundancy is not known (heartbeat not received). available(1): Secondary is active and primary is in standby, configurations are synchronized and no critical faults on either of the APEX. protected(2): Secondary is in active and primary is fault state. unavailable(3): Configuration not synchronized or secondary is in fault state or secondary has not received heartbeat message from primary. synchronizing(4): Synchronizing configuration between active and standby APEX's."
],
null,
null,
null,
null
]
}