
CISCO-L4L7MODULE-REDUNDANCY-MIB
File:
CISCO-L4L7MODULE-REDUNDANCY-MIB.mib (39747 bytes)
Imported modules
Imported symbols
Defined Objects
| ciscoL4L7moduleRedundancyMIB |
1.3.6.1.4.1.9.9.650 |
| The L4-7 SLB devices are used for scaling websites, building web enabled applications, and migrating to web services. The following services ( but not limited to ) can be provided by L4-7 slb devices: SLB ( Server Load Balancing ) FW ( Firewall ) SSL ( Secure Socket Layer ) IDS ( Intrusion Detection System ) . This MIB provides the tables/objects that support redundancy configuration and redundancy statistics. The redundancy model supported by this MIB allows two or more SLB devices to be configured with one or more redundancy group. Each redundancy group is identified by a unique group ID. Two or more devices are redundant to each other if they use the same redundancy Group ID. Acronyms and terms: HB Heart Beat FT Fault Tolerant HA High Availability VLAN Virtual Local Area Network LB Load Balance |
| MODULE-IDENTITY |
|
|
|
| clrConfig |
1.3.6.1.4.1.9.9.650.1.1 |
| OBJECT IDENTIFIER |
|
|
|
| clrPeerConfigTable |
1.3.6.1.4.1.9.9.650.1.1.1 |
| This table is for configuring peer groups that are part of redundancy configuration. The peer configuration specifies the information used for exchanging High Availability information related to redundancy groups. |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
ClrPeerConfigEntry |
|
| clrPeerConfigEntry |
1.3.6.1.4.1.9.9.650.1.1.1.1 |
| An entry in clrPeerConfigTable. Each entry contains information about peer interface, query interface, heart beat count and heart beat time. |
| OBJECT-TYPE |
|
|
|
| |
ClrPeerConfigEntry |
|
|
| clrPeerId |
1.3.6.1.4.1.9.9.650.1.1.1.1.1 |
| This object identifies unique id for the peer. The peer is used in redundancy configuration. |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..65535 |
|
| clrPeerBackupInterface |
1.3.6.1.4.1.9.9.650.1.1.1.1.3 |
| This object specifies the backup interface used by the peer. The backup interface is used in case the heart beat message is not received. This interface is used to send the heart beat message. If the message sent is not successful, then it is assumed peer is down and switchover will be initiated. If the message sent is successful on this interface, the peer transitions to standbyCold and continue to monitor peer. |
| OBJECT-TYPE |
|
|
|
| |
InterfaceIndexOrZero |
|
|
| clrPeerHeartBeatCount |
1.3.6.1.4.1.9.9.650.1.1.1.1.5 |
| This object is used in conjunction with 'clrPeerHeartBeatTime' to switch over the active redundancy unit or not. Switch over occurs if heartbeats are not received from the peer during a specific time period, which is equal to ( clrPeerHeartBeatTime * clrPeerHeartBeatCount ) . |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| clrPeerRowStatus |
1.3.6.1.4.1.9.9.650.1.1.1.1.7 |
| This object is used for adding/deleting entries from the table. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value, as described in the description clause for each writable object. This object may be modified if the associated instance of this object is equal to active(1), notInService(2), or notReady(3). All other writable objects may be modified if the associated instance of this object is equal to notInService(2) or notReady(3). |
| OBJECT-TYPE |
|
|
|
| |
RowStatus |
|
|
| clrPeerInfoEntry |
1.3.6.1.4.1.9.9.650.1.1.2.1 |
| An entry in peer information table. An entry will get created whenever an entry is created in clrPeerConfigTable. Each entry contains information such as peer state, peer ip address, software and license compatibility. The entPhysicalIndex specifies an entry in entPhysicalTable with entPhysicalClass representing the value of 'module'. |
| OBJECT-TYPE |
|
|
|
| |
ClrPeerInfoEntry |
|
|
| clrPeerOperStatus |
1.3.6.1.4.1.9.9.650.1.1.2.1.1 |
| This object identifies the current status of the peer. The possible values are init(1) : The initial state of the peer. localIPaddr(2) : The local device IP address is missing. Waiting for the local IP address to be configured. peerIPAddr(3) : The peer IP address is missing. Waiting for the peer IP address to be configured. startHB(4) : The peer configuration is complete. Starting the heartbeat to see if there is a peer device. tcpSetUp(5) : The heartbeat has detected the presence of the peer device. Redundancy is in the process of establishing a TCP connection to the peer. srgCheck(6) : Checking for software version compatibility with the peer device. licCheck(7) : Checking for license compatibility with the peer device. compatible(8) : Version and license checks indicate that the peer is compatible for redundancy. peerInterfaceDown(9): The peer interface ( used for transmitting and receiving HB messages ) is down, but, through the query interface, the local device has determined that the peer is still alive. down(10) : The peer device is down. error(11) : Indicates that an error has occurred with the peer. Possible errors are: version mismatch, license mismatch, or failure to establish a TCP connection to the peer. A syslog message appears with more detailed information. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
init(1), localIPaddr(2), peerIPAddr(3), startHB(4), tcpSetup(5), srgCheck(6), licCheck(7), compatible(8), peerInterfaceDown(9), down(10), error(11) |
|
| clrPeerIpAddress |
1.3.6.1.4.1.9.9.650.1.1.2.1.3 |
| This Internet address for the redundant peer. The type of this address is determined by the value of the clrPeerIpAddressType object. |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| clrPeerSoftwareCompatibilty |
1.3.6.1.4.1.9.9.650.1.1.2.1.4 |
| Indicates whether the software version of the local device and the software version of the peer are compatible. The possible values are: init(1) : initialization state. compatible(2) : software version of the local and peer device are compatible. inCompatible(3) : software version of the local and peer device are not compatible. warmCompatible(4) : When the software version check of the local and the peer device returns 'supersedes' or 'superseded_by' then the clrPeerSoftwarecompatibility of the peer device is set to 'warmCompatible'. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
init(1), compatible(2), inCompatible(3), warmCompatible(4) |
|
| clrPeerLicenseCompatibility |
1.3.6.1.4.1.9.9.650.1.1.2.1.5 |
| Indicates whether the license of the local device and the license of the peer device are compatible. The possible values are: init(1) : initialization state. compatible(2) : license version of the local and peer device are compatible. inCompatible(3) : license version of the local and peer device are not compatible. |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
init(1), compatible(2), inCompatible(3) |
|
| clrRedundancyConfigEntry |
1.3.6.1.4.1.9.9.650.1.1.3.1 |
| An entry in redundancy table. Each entry contains information such as priority, preempt. Preemption ensures that the group member with high priority always becomes active. The entPhysicalIndex specifies the entry in entPhysicalTable with entPhysicalClass representing the value of 'module'. |
| OBJECT-TYPE |
|
|
|
| |
ClrRedundancyConfigEntry |
|
|
| clrRedGroupId |
1.3.6.1.4.1.9.9.650.1.1.3.1.1 |
| This object specifies the redundancy group identifier. This is the unique id of the redundancy group. |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..4096 |
|
| clrRedPeerId |
1.3.6.1.4.1.9.9.650.1.1.3.1.2 |
| The peer ID to which this group belongs. There must be an entry in clrPeerConfigTable with this value. This object cannot be modified if the associated clrRedRowStatus object is equal to 'active'. |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..65535 |
|
| clrRedPriority |
1.3.6.1.4.1.9.9.650.1.1.3.1.3 |
| The priority value of the redundancy group. This value is used in selecting the active and standby peer. The devices that belong to the same redundancy group must be configured with a different priority. The redundancy group with a highest priority will become active unit during negotiation phase of the redundancy. If two (or more) devices in a group have the same priority, the one with the highest IP address of the interface is the active device. If a redundancy group with high priority value is online after its peer has become active, then the group with high priority will become standby. This behavior can be changed by setting clrRedPreempt object to 'true'. |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..255 |
|
| clrRedPreempt |
1.3.6.1.4.1.9.9.650.1.1.3.1.4 |
| This specifies whether a high priority redundancy device can become active irrespective of the time at which it is online. The value 'true' specifies that the redundancy group with higher priority will always become active. The value 'false' specifies that the redundacy device which becomes active will remain active even if another redundancy device comes online with higher priority. |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| clrRedFailOverTime |
1.3.6.1.4.1.9.9.650.1.1.3.1.5 |
| The time to wait before standby redundancy group become active. This represents the amount of time a module need to wait after the last keep-alive message is received before assuming the peer is not operating. |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| clrRedContext |
1.3.6.1.4.1.9.9.650.1.1.3.1.8 |
| This object refers to the context name to which the redundant group is associated with. The context refers to the logical partitioning within a device. The context can be identified by a unique name in a device. |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
|
|
| clrRedRowStatus |
1.3.6.1.4.1.9.9.650.1.1.3.1.10 |
| This object is used for adding/deleting entries from the table. An entry MUST NOT exist in the active state unless all objects in the entry have an appropriate value, as described in the description clause for each writable object. This object may be modified if the associated instance of this object is equal to active(1), notInService(2), or notReady(3). All other writable objects may be modified if the associated instance of this object is equal to notInService(2) or notReady(3). |
| OBJECT-TYPE |
|
|
|
| |
RowStatus |
|
|
| clrRedundancyInfoEntry |
1.3.6.1.4.1.9.9.650.1.1.4.1 |
| An entry in redundancy information table. An entry will get created whenever an entry is created in clrRedundancyConfigTable. Each entry contains information such as priority, state and last time when the redundancy state got changed. The entPhysicalIndex specifies an entry in entPhysicalTable with entPhysicalClass representing the value of 'module'. |
| OBJECT-TYPE |
|
|
|
| |
ClrRedundancyInfoEntry |
|
|
| clrRedundancyPriority |
1.3.6.1.4.1.9.9.650.1.1.4.1.1 |
| The priority value of this redundancy entry. This value is same as the value configured in 'clrRedPriority' for a redundancy group. |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..255 |
|
| clrRedundancyIpAddress |
1.3.6.1.4.1.9.9.650.1.1.4.1.5 |
| This object identifies the Internet address by which this redundant device is reachable. The type of this address is determined by the value of the clrRedundancyIpAddressType object. |
| OBJECT-TYPE |
|
|
|
| |
InetAddress |
|
|
| clrStats |
1.3.6.1.4.1.9.9.650.1.2 |
| OBJECT IDENTIFIER |
|
|
|
| clrLBStatsEntry |
1.3.6.1.4.1.9.9.650.1.2.1.1 |
| Each entry represents the load balance statistics applicable for a redundancy group. The entPhysicalIndex specifies the entry in entPhysicalTable. The entries will get created in this table by way of adding entries in clrRedundancyConfigTable. The entries will be deleted from this table by way of removing entries in clrRedundancyConfigTable. |
| OBJECT-TYPE |
|
|
|
| |
ClrLBStatsEntry |
|
|
| clrLBStatsSharedStickyEntries |
1.3.6.1.4.1.9.9.650.1.2.1.1.1 |
| This object indicates the number of sticky entries that the local device sent to the peer. Sticky entries is a LB configuration which allows multiple connections from the same client to be sent to the same server. Stickiness can be configured based on source IP address, HTTP cookies, SSL session ID ( for SSL traffic only ) , etc. |
| OBJECT-TYPE |
|
|
|
| |
Counter64 |
|
|
| clrHAStatsEntry |
1.3.6.1.4.1.9.9.650.1.2.2.1 |
| Each entry represents the statistics applicable for a redundant peer. The entPhysicalIndex specifies the entry in entPhysicalTable . The entries will get created in this table by way of adding entries in clrPeerConfigTable. The entries will be deleted from this table by way of removing entries in clrPeerConfigTable. |
| OBJECT-TYPE |
|
|
|
| |
ClrHAStatsEntry |
|
|
| clrHAStatsHeartBeatTimeoutMismatches |
1.3.6.1.4.1.9.9.650.1.2.2.1.5 |
| Each HB packet contains the configured interval in the packet. When a peer receives a HB packet, it checks to see if the interval in the HB packet matches the interval configured locally. This object indicates the number of HB that the local device received from the remote peer with a mismatched HB interval. |
| OBJECT-TYPE |
|
|
|
| |
Counter64 |
|
|
| clrStateChangeNotifEnabled |
1.3.6.1.4.1.9.9.650.1.3.1 |
| This object controls the generation of clrRedundancyStateChange notification. 'true' : Indicates that clrRedundancyStateChange notification is to be generated when the state changes. That is, notification generation is enabled. 'false' : Indicates that clrRedundancyStateChange notification generation is disabled. |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
Defined Objects
| 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. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
other(1), nonRedundant(2), initializing(3), negotiation(4), active(5), standbyCold(6), standbyConfig(7), standbyBulk(8), standbyHot(9), standbyWarm(10) |
|
| ClrPeerConfigEntry |
|
| SEQUENCE |
|
|
|
| |
Unsigned32 as clrPeerId |
|
|
| |
InterfaceIndex as clrPeerInterface |
|
|
| |
InterfaceIndexOrZero as clrPeerBackupInterface |
|
|
| |
Unsigned32 as clrPeerHeartBeatTime |
|
|
| |
Unsigned32 as clrPeerHeartBeatCount |
|
|
| |
StorageType as clrPeerStorageType |
|
|
| |
RowStatus as clrPeerRowStatus |
|
|
| ClrPeerInfoEntry |
|
| SEQUENCE |
|
|
|
| |
INTEGER as clrPeerOperStatus |
|
|
| |
InetAddressType as clrPeerIpAddressType |
|
|
| |
InetAddress as clrPeerIpAddress |
|
|
| |
INTEGER as clrPeerSoftwareCompatibilty |
|
|
| |
INTEGER as clrPeerLicenseCompatibility |
|
|
| |
Unsigned32 as clrPeerRedGroups |
|
|
| ClrRedundancyConfigEntry |
|
| SEQUENCE |
|
|
|
| |
Unsigned32 as clrRedGroupId |
|
|
| |
Unsigned32 as clrRedPeerId |
|
|
| |
Unsigned32 as clrRedPriority |
|
|
| |
TruthValue as clrRedPreempt |
|
|
| |
Unsigned32 as clrRedFailOverTime |
|
|
| |
CiscoL4L7RedState as clrRedState |
|
|
| |
TimeStamp as clrRedStateChangeTime |
|
|
| |
OCTET STRING as clrRedContext |
|
|
| |
StorageType as clrRedStorageType |
|
|
| |
RowStatus as clrRedRowStatus |
|
|
| ClrRedundancyInfoEntry |
|
| SEQUENCE |
|
|
|
| |
Unsigned32 as clrRedundancyPriority |
|
|
| |
CiscoL4L7RedState as clrRedundancyState |
|
|
| |
TimeStamp as clrRedundancyStateChangeTime |
|
|
| |
InetAddressType as clrRedundancyIpAddressType |
|
|
| |
InetAddress as clrRedundancyIpAddress |
|
|
| ClrLBStatsEntry |
|
| SEQUENCE |
|
|
|
| |
Counter64 as clrLBStatsSharedStickyEntries |
|
|
| |
Counter64 as clrLBStatsSentPackets |
|
|
| |
Counter64 as clrLBStatsSendFailures |
|
|
| |
Counter64 as clrLBStatsDroppedEntries |
|
|
| |
Counter64 as clrLBStatsReceivedPackets |
|
|
| |
Counter64 as clrLBStatsReceiveFailures |
|
|
| ClrHAStatsEntry |
|
| SEQUENCE |
|
|
|
| |
Counter64 as clrHAStatsTxHeartBeatMsgs |
|
|
| |
Counter64 as clrHAStatsRxHeartBeatMsgs |
|
|
| |
Counter64 as clrHAStatsMissedHeartBeatMsgs |
|
|
| |
Counter64 as clrHAStatsRxUniDirectionalHeartBeatMsgs |
|
|
| |
Counter64 as clrHAStatsHeartBeatTimeoutMismatches |
|
|
| |
Counter64 as clrHAStatsPeerUpEvents |
|
|
| |
Counter64 as clrHAStatsPeerDownEvents |
|
|