CISCO-L4L7MODULE-REDUNDANCY-MIB

File: CISCO-L4L7MODULE-REDUNDANCY-MIB.mib (39747 bytes)

Imported modules

SNMPv2-SMI SNMPv2-CONF INET-ADDRESS-MIB
SNMPv2-TC IF-MIB ENTITY-MIB
CISCO-SMI

Imported symbols

MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-TYPE
Unsigned32 Counter64 MODULE-COMPLIANCE
OBJECT-GROUP NOTIFICATION-GROUP InetAddressType
InetAddress TEXTUAL-CONVENTION TimeStamp
TruthValue RowStatus StorageType
InterfaceIndex InterfaceIndexOrZero entPhysicalIndex
ciscoMgmt

Defined Types

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    
  clrPeerId Unsigned32
  clrPeerInterface InterfaceIndex
  clrPeerBackupInterface InterfaceIndexOrZero
  clrPeerHeartBeatTime Unsigned32
  clrPeerHeartBeatCount Unsigned32
  clrPeerStorageType StorageType
  clrPeerRowStatus RowStatus

ClrPeerInfoEntry  
SEQUENCE    
  clrPeerOperStatus INTEGER
  clrPeerIpAddressType InetAddressType
  clrPeerIpAddress InetAddress
  clrPeerSoftwareCompatibilty INTEGER
  clrPeerLicenseCompatibility INTEGER
  clrPeerRedGroups Unsigned32

ClrRedundancyConfigEntry  
SEQUENCE    
  clrRedGroupId Unsigned32
  clrRedPeerId Unsigned32
  clrRedPriority Unsigned32
  clrRedPreempt TruthValue
  clrRedFailOverTime Unsigned32
  clrRedState CiscoL4L7RedState
  clrRedStateChangeTime TimeStamp
  clrRedContext OCTET STRING
  clrRedStorageType StorageType
  clrRedRowStatus RowStatus

ClrRedundancyInfoEntry  
SEQUENCE    
  clrRedundancyPriority Unsigned32
  clrRedundancyState CiscoL4L7RedState
  clrRedundancyStateChangeTime TimeStamp
  clrRedundancyIpAddressType InetAddressType
  clrRedundancyIpAddress InetAddress

ClrLBStatsEntry  
SEQUENCE    
  clrLBStatsSharedStickyEntries Counter64
  clrLBStatsSentPackets Counter64
  clrLBStatsSendFailures Counter64
  clrLBStatsDroppedEntries Counter64
  clrLBStatsReceivedPackets Counter64
  clrLBStatsReceiveFailures Counter64

ClrHAStatsEntry  
SEQUENCE    
  clrHAStatsTxHeartBeatMsgs Counter64
  clrHAStatsRxHeartBeatMsgs Counter64
  clrHAStatsMissedHeartBeatMsgs Counter64
  clrHAStatsRxUniDirectionalHeartBeatMsgs Counter64
  clrHAStatsHeartBeatTimeoutMismatches Counter64
  clrHAStatsPeerUpEvents Counter64
  clrHAStatsPeerDownEvents Counter64

Defined Values

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    

ciscoLmRedundancyMIBNotifs 1.3.6.1.4.1.9.9.650.0
OBJECT IDENTIFIER    

ciscoLmRedundancyMIBObjects 1.3.6.1.4.1.9.9.650.1
OBJECT IDENTIFIER    

ciscoLmRedundancyMIBConformance 1.3.6.1.4.1.9.9.650.2
OBJECT IDENTIFIER    

clrConfig 1.3.6.1.4.1.9.9.650.1.1
OBJECT IDENTIFIER    

clrStats 1.3.6.1.4.1.9.9.650.1.2
OBJECT IDENTIFIER    

clrNotifObjects 1.3.6.1.4.1.9.9.650.1.3
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.
Status: current Access: not-accessible
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.
Status: current Access: not-accessible
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.
Status: current Access: not-accessible
OBJECT-TYPE    
  Unsigned32 1..65535  

clrPeerInterface 1.3.6.1.4.1.9.9.650.1.1.1.1.2
This object specifies the interface used by the peers to exchange High Availability ( HA ) protocol information.
Status: current Access: read-create
OBJECT-TYPE    
  InterfaceIndex  

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.
Status: current Access: read-create
OBJECT-TYPE    
  InterfaceIndexOrZero  

clrPeerHeartBeatTime 1.3.6.1.4.1.9.9.650.1.1.1.1.4
The time interval between heartbeat/keep-alive messages exchanged between the peers.
Status: current Access: read-create
OBJECT-TYPE    
  Unsigned32  

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 ) .
Status: current Access: read-create
OBJECT-TYPE    
  Unsigned32  

clrPeerStorageType 1.3.6.1.4.1.9.9.650.1.1.1.1.6
The storage type for this conceptual row.
Status: current Access: read-create
OBJECT-TYPE    
  StorageType  

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).
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

clrPeerInfoTable 1.3.6.1.4.1.9.9.650.1.1.2
This table contains information of the redundancy peer.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    ClrPeerInfoEntry

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'.
Status: current Access: not-accessible
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.
Status: current Access: read-only
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)  

clrPeerIpAddressType 1.3.6.1.4.1.9.9.650.1.1.2.1.2
The type of internet address by which the peer is reachable.
Status: current Access: read-only
OBJECT-TYPE    
  InetAddressType  

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.
Status: current Access: read-only
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'.
Status: current Access: read-only
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.
Status: current Access: read-only
OBJECT-TYPE    
  INTEGER init(1), compatible(2), inCompatible(3)  

clrPeerRedGroups 1.3.6.1.4.1.9.9.650.1.1.2.1.6
This object refers to the number of redundancy groups the peer is associated with.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32  

clrRedundancyConfigTable 1.3.6.1.4.1.9.9.650.1.1.3
This table is used for configuring redundancy groups. The redundancy group is configured by specifying the same value of 'clrRedGroupId' in multiple devices.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    ClrRedundancyConfigEntry

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'.
Status: current Access: not-accessible
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.
Status: current Access: not-accessible
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'.
Status: current Access: read-create
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'.
Status: current Access: read-create
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.
Status: current Access: read-create
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.
Status: current Access: read-create
OBJECT-TYPE    
  Unsigned32  

clrRedState 1.3.6.1.4.1.9.9.650.1.1.3.1.6
The current redundancy state.
Status: current Access: read-only
OBJECT-TYPE    
  CiscoL4L7RedState  

clrRedStateChangeTime 1.3.6.1.4.1.9.9.650.1.1.3.1.7
The time of the last change in the current redundancy state.
Status: current Access: read-only
OBJECT-TYPE    
  TimeStamp  

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.
Status: current Access: read-create
OBJECT-TYPE    
  OCTET STRING  

clrRedStorageType 1.3.6.1.4.1.9.9.650.1.1.3.1.9
The storage type for this conceptual row.
Status: current Access: read-create
OBJECT-TYPE    
  StorageType  

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).
Status: current Access: read-create
OBJECT-TYPE    
  RowStatus  

clrRedundancyInfoTable 1.3.6.1.4.1.9.9.650.1.1.4
This table contains information on the devices that are part of redundancy group.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    ClrRedundancyInfoEntry

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'.
Status: current Access: not-accessible
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.
Status: current Access: read-only
OBJECT-TYPE    
  Unsigned32 1..255  

clrRedundancyState 1.3.6.1.4.1.9.9.650.1.1.4.1.2
The current redundancy state.
Status: current Access: read-only
OBJECT-TYPE    
  CiscoL4L7RedState  

clrRedundancyStateChangeTime 1.3.6.1.4.1.9.9.650.1.1.4.1.3
The time of the last change in the current redundancy state.
Status: current Access: read-only
OBJECT-TYPE    
  TimeStamp  

clrRedundancyIpAddressType 1.3.6.1.4.1.9.9.650.1.1.4.1.4
The type of internet address by which this redundant device reachable.
Status: current Access: read-only
OBJECT-TYPE    
  InetAddressType  

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.
Status: current Access: read-only
OBJECT-TYPE    
  InetAddress  

clrLBStatsTable 1.3.6.1.4.1.9.9.650.1.2.1
This table contains the load balance statistics related to a redundancy group.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    ClrLBStatsEntry

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.
Status: current Access: not-accessible
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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrLBStatsSentPackets 1.3.6.1.4.1.9.9.650.1.2.1.1.2
This object contains the number of valid packets that the local device sent to the peer.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrLBStatsSendFailures 1.3.6.1.4.1.9.9.650.1.2.1.1.3
This object contains the number of packets that the local device attempted to send to the peer, but failed.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrLBStatsDroppedEntries 1.3.6.1.4.1.9.9.650.1.2.1.1.4
This object contains the number of sticky entries that the peer sent to the local device, but the local device discarded them.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrLBStatsReceivedPackets 1.3.6.1.4.1.9.9.650.1.2.1.1.5
This object contains the number of valid packets that the local device received from the peer.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrLBStatsReceiveFailures 1.3.6.1.4.1.9.9.650.1.2.1.1.6
This object contains the number of packets that the peer sent to the local device, but the local device failed to receive them.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrHAStatsTable 1.3.6.1.4.1.9.9.650.1.2.2
This table contains the statistics related to a redundant peer.
Status: current Access: not-accessible
OBJECT-TYPE    
  SEQUENCE OF  
    ClrHAStatsEntry

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.
Status: current Access: not-accessible
OBJECT-TYPE    
  ClrHAStatsEntry  

clrHAStatsTxHeartBeatMsgs 1.3.6.1.4.1.9.9.650.1.2.2.1.1
This object refers to the number of heart beat messages sent to the peer.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrHAStatsRxHeartBeatMsgs 1.3.6.1.4.1.9.9.650.1.2.2.1.2
This object refers to the number of heart beat messages received from the peer.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrHAStatsMissedHeartBeatMsgs 1.3.6.1.4.1.9.9.650.1.2.2.1.3
This object refers to the number of missed heart beat messages.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrHAStatsRxUniDirectionalHeartBeatMsgs 1.3.6.1.4.1.9.9.650.1.2.2.1.4
This object indicates that the heartbeat messages from a peer is unidirectional. That is, the peer cannot receive ( only send ) heartbeats.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

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.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrHAStatsPeerUpEvents 1.3.6.1.4.1.9.9.650.1.2.2.1.6
This object contains the number of peer up messages that the local device sent to the remote peer.
Status: current Access: read-only
OBJECT-TYPE    
  Counter64  

clrHAStatsPeerDownEvents 1.3.6.1.4.1.9.9.650.1.2.2.1.7
This object contains the number of peer down messages that the local device sent to the remote peer.
Status: current Access: read-only
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.
Status: current Access: read-write
OBJECT-TYPE    
  TruthValue  

clrRedundancyStateChange 1.3.6.1.4.1.9.9.650.0.1
The notification generated when the redundancy state is changed.
Status: current Access: read-write
NOTIFICATION-TYPE    

ciscoLmRedundancyMIBCompliances 1.3.6.1.4.1.9.9.650.2.1
OBJECT IDENTIFIER    

ciscoLmRedundancyMIBGroups 1.3.6.1.4.1.9.9.650.2.2
OBJECT IDENTIFIER    

ciscoLmRedundancyMIBCompliance 1.3.6.1.4.1.9.9.650.2.1.1
The compliance statement for entities which implement the L4L7 Switch Redundancy.
Status: current Access: read-write
MODULE-COMPLIANCE    

clrPeerConfigGroup 1.3.6.1.4.1.9.9.650.2.2.1
This group contains the peer configuration objects.
Status: current Access: read-write
OBJECT-GROUP    

clrRedConfigGroup 1.3.6.1.4.1.9.9.650.2.2.2
This group contains the redundancy configuration objects.
Status: current Access: read-write
OBJECT-GROUP    

clrRedInfoGroup 1.3.6.1.4.1.9.9.650.2.2.3
This group contains the redundancy information objects.
Status: current Access: read-write
OBJECT-GROUP    

cslbxNotifControlGroup 1.3.6.1.4.1.9.9.650.2.2.4
The collection of objects to control the notifications for state changed in a L4 redundancy configuration.
Status: current Access: read-write
OBJECT-GROUP    

cslbxNotifGroup 1.3.6.1.4.1.9.9.650.2.2.5
This group contains the notifications related to redundancy.
Status: current Access: read-write
NOTIFICATION-GROUP    

clrRedundancyStatsGroup 1.3.6.1.4.1.9.9.650.2.2.6
This group contains objects related to redundant peer and load balacing statistics.
Status: current Access: read-write
OBJECT-GROUP