Status in source: current.
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"lsiSfoLastFoRsn",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"noFailover",
"(",
"1",
")",
",",
"heartbeatExpiration",
"(",
"3",
")",
",",
"partnerReset",
"(",
"4",
")",
",",
"initPartnerNotReady",
"(",
"5",
")",
",",
"initPartnerNotInit",
"(",
"6",
")",
",",
"initPartnerNoPhyEnable",
"(",
"7",
")",
",",
"initPartnerNoVerInfo",
"(",
"8",
")",
",",
"initPartnerVerMismatch",
"(",
"9",
")",
",",
"initPartnerExcluded",
"(",
"10",
")",
",",
"ielBroadcast",
"(",
"11",
")",
",",
"semaphoreFailed",
"(",
"12",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Reports the reason for the last expander failover operation. In many cases, the switch will recover from this failover and lsiSfoCurrentState will report operational(1). The following outlines the reasons for these failover operations: o noFailover(1) - There has not been a failover operation since the last reset. o heartbeatExpiration(3) - The switch has missed a series of heartbeats, and the heartbeat timer has expired. o partnerReset(4) - The partner expnader reset on its own. o initPartnerNotReady(5) - The partner expander did not reach the ready state during initialization. o initPartnerNotInit(6) - The partner expander did not reach the initializing state during initialization. o initPartnerNoPhyEnable(7) - During initialization, the partner failed to enable its phys. o initPartnerNoVerInfo(8) - The partner did not send its version information during initialization. o initPartnerVerMismatch(9) - The partner failed to synchronize its version information during initialization. o initPartnerExcluded(10) - The partner was held in failover because it is marked as permanently failed in the failover config page. o ielBroadcast(11) - A broadcast has been received on the IELs, which indicates that they have changed state. o semaphoreFailed(12) - The expander failed to secure the shared memory semaphore.\"",
"::=",
"{",
"lsiSwStatFailover",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"noFailover",
1
],
[
"heartbeatExpiration",
3
],
[
"partnerReset",
4
],
[
"initPartnerNotReady",
5
],
[
"initPartnerNotInit",
6
],
[
"initPartnerNoPhyEnable",
7
],
[
"initPartnerNoVerInfo",
8
],
[
"initPartnerVerMismatch",
9
],
[
"initPartnerExcluded",
10
],
[
"ielBroadcast",
11
],
[
"semaphoreFailed",
12
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Reports the reason for the last expander failover operation. In many cases, the switch will recover from this failover and lsiSfoCurrentState will report operational(1). The following outlines the reasons for these failover operations: o noFailover(1) - There has not been a failover operation since the last reset. o heartbeatExpiration(3) - The switch has missed a series of heartbeats, and the heartbeat timer has expired. o partnerReset(4) - The partner expnader reset on its own. o initPartnerNotReady(5) - The partner expander did not reach the ready state during initialization. o initPartnerNotInit(6) - The partner expander did not reach the initializing state during initialization. o initPartnerNoPhyEnable(7) - During initialization, the partner failed to enable its phys. o initPartnerNoVerInfo(8) - The partner did not send its version information during initialization. o initPartnerVerMismatch(9) - The partner failed to synchronize its version information during initialization. o initPartnerExcluded(10) - The partner was held in failover because it is marked as permanently failed in the failover config page. o ielBroadcast(11) - A broadcast has been received on the IELs, which indicates that they have changed state. o semaphoreFailed(12) - The expander failed to secure the shared memory semaphore."
],
null,
null,
null,
null
]
}