slbSaspRedundancy
The Load Balancer's state in a redundant setup. The Load Balancer may still contact the SASP Agents, which are defined in the slbSaspAgentTable, regardless of the state. This is possible because every Load Balancer contacting a SASP Agent is required to have it's own unique identifier. Therefore, the master and backup Load Balancer MUST have different unique identifiers.
Details
Possible values
| 1 | other |
| 2 | master |
| 3 | backup |
Table columns
6 objects| Oid | Name | Access | Type |
|---|---|---|---|
| 1.3.6.1.4.1.9.9.161.1.12.1.1.1 | slbSaspIdentifier | readwrite | SnmpAdminString |
| 1.3.6.1.4.1.9.9.161.1.12.1.1.2 | slbSaspEnabled | readwrite | TruthValue |
| 1.3.6.1.4.1.9.9.161.1.12.1.1.3 | slbSaspHealth | readonly | SlbSaspLBHealth |
| 1.3.6.1.4.1.9.9.161.1.12.1.1.4 | slbSaspRedundancy | readonly | SlbSaspRedundancy |
| 1.3.6.1.4.1.9.9.161.1.12.1.1.5 | slbSaspMaxAgents | readonly | Unsigned32 |
| 1.3.6.1.4.1.9.9.161.1.12.1.1.6 | slbSaspMaxLbWeight | readonly | Unsigned32 |
Used by conformance groups
1 objects- 1.3.6.1.4.1.9.9.161.3.2.14 ciscoSlbSaspGroup