MIBs Depot

CISCO-L4L7MODULE-REDUNDANCY-MIB

Registered at
1.3.6.1.4.1.9.9.650
Last updated
2008-04-04 00:00
Organization
Cisco Systems, Inc.
Revisions
2008-04-04 00:00, 2008-03-13 00:00
Namespace
cisco
Source file
CISCO-L4L7MODULE-REDUNDANCY-MIB
Digest
sha256:43b21bfb9b2716d80b2d3a3feea1a930ff0b0d118a83099e7cb274edce71fc09

Description

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

Contact

Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: cs-l4l7security@cisco.com

Imports

FromSymbols
CISCO-SMIciscoMgmt
ENTITY-MIBentPhysicalIndex
IF-MIBInterfaceIndex, InterfaceIndexOrZero
INET-ADDRESS-MIBInetAddress, InetAddressType
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-SMICounter64, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, Unsigned32, iso
SNMPv2-TCDisplayString, RowStatus, StorageType, TEXTUAL-CONVENTION, TimeStamp, TruthValue

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

CISCO-L4L7MODULE-REDUNDANCY-MIB
CISCO-SMI
ENTITY-MIB
IANA-ENTITY-MIB
IANAifType-MIB
IF-MIB
INET-ADDRESS-MIB
SNMP-FRAMEWORK-MIB
SNMPv2-CONF
SNMPv2-MIB
SNMPv2-SMI
SNMPv2-TC
UUID-TC-MIB

Textual conventions

NameOIDSyntaxAccessStatus
CiscoL4L7RedState
TEXTUAL-CONVENTION
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.
current

Objects

NameOIDSyntaxAccessStatus
ciscoLmRedundancyMIBNotifs
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.650.0
ciscoLmRedundancyMIBObjects
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.650.1
clrConfig
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.650.1.1
clrPeerConfigTable
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.1.1not-accessiblecurrent
clrPeerConfigEntry
OBJECT-TYPE
An entry in clrPeerConfigTable. Each entry contains information about peer interface, query interface, heart beat count and heart beat time.
1.3.6.1.4.1.9.9.650.1.1.1.1not-accessiblecurrent
clrPeerId
OBJECT-TYPE
This object identifies unique id for the peer. The peer is used in redundancy configuration.
1.3.6.1.4.1.9.9.650.1.1.1.1.1Unsigned32 (1..65535)not-accessiblecurrent
clrPeerInterface
OBJECT-TYPE
This object specifies the interface used by the peers to exchange High Availability ( HA ) protocol information.
1.3.6.1.4.1.9.9.650.1.1.1.1.2InterfaceIndexread-createcurrent
clrPeerBackupInterface
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.1.1.1.3InterfaceIndexOrZeroread-createcurrent
clrPeerHeartBeatTime
OBJECT-TYPE
The time interval between heartbeat/keep-alive messages exchanged between the peers.
1.3.6.1.4.1.9.9.650.1.1.1.1.4Unsigned32read-createcurrent
clrPeerHeartBeatCount
OBJECT-TYPE
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 ) .
1.3.6.1.4.1.9.9.650.1.1.1.1.5Unsigned32read-createcurrent
clrPeerStorageType
OBJECT-TYPE
The storage type for this conceptual row.
1.3.6.1.4.1.9.9.650.1.1.1.1.6StorageTyperead-createcurrent
clrPeerRowStatus
OBJECT-TYPE
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).
1.3.6.1.4.1.9.9.650.1.1.1.1.7RowStatusread-createcurrent
clrPeerInfoTable
OBJECT-TYPE
This table contains information of the redundancy peer.
1.3.6.1.4.1.9.9.650.1.1.2not-accessiblecurrent
clrPeerInfoEntry
OBJECT-TYPE
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'.
1.3.6.1.4.1.9.9.650.1.1.2.1not-accessiblecurrent
clrPeerOperStatus
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.1.2.1.1INTEGER {init(1), localIPaddr(2), peerIPAddr(3), startHB(4), tcpSetup(5), srgCheck(6), licCheck(7), compatible(8), peerInterfaceDown(9), down(10), error(11)}read-onlycurrent
clrPeerIpAddressType
OBJECT-TYPE
The type of internet address by which the peer is reachable.
1.3.6.1.4.1.9.9.650.1.1.2.1.2InetAddressTyperead-onlycurrent
clrPeerIpAddress
OBJECT-TYPE
This Internet address for the redundant peer. The type of this address is determined by the value of the clrPeerIpAddressType object.
1.3.6.1.4.1.9.9.650.1.1.2.1.3InetAddressread-onlycurrent
clrPeerSoftwareCompatibilty
OBJECT-TYPE
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'.
1.3.6.1.4.1.9.9.650.1.1.2.1.4INTEGER {init(1), compatible(2), inCompatible(3), warmCompatible(4)}read-onlycurrent
clrPeerLicenseCompatibility
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.1.2.1.5INTEGER {init(1), compatible(2), inCompatible(3)}read-onlycurrent
clrPeerRedGroups
OBJECT-TYPE
This object refers to the number of redundancy groups the peer is associated with.
1.3.6.1.4.1.9.9.650.1.1.2.1.6Unsigned32read-onlycurrent
clrRedundancyConfigTable
OBJECT-TYPE
This table is used for configuring redundancy groups. The redundancy group is configured by specifying the same value of 'clrRedGroupId' in multiple devices.
1.3.6.1.4.1.9.9.650.1.1.3not-accessiblecurrent
clrRedundancyConfigEntry
OBJECT-TYPE
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'.
1.3.6.1.4.1.9.9.650.1.1.3.1not-accessiblecurrent
clrRedGroupId
OBJECT-TYPE
This object specifies the redundancy group identifier. This is the unique id of the redundancy group.
1.3.6.1.4.1.9.9.650.1.1.3.1.1Unsigned32 (1..4096)not-accessiblecurrent
clrRedPeerId
OBJECT-TYPE
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'.
1.3.6.1.4.1.9.9.650.1.1.3.1.2Unsigned32 (1..65535)read-createcurrent
clrRedPriority
OBJECT-TYPE
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'.
1.3.6.1.4.1.9.9.650.1.1.3.1.3Unsigned32 (1..255)read-createcurrent
clrRedPreempt
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.1.3.1.4TruthValueread-createcurrent
clrRedFailOverTime
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.1.3.1.5Unsigned32read-createcurrent
clrRedState
OBJECT-TYPE
The current redundancy state.
1.3.6.1.4.1.9.9.650.1.1.3.1.6CiscoL4L7RedStateread-onlycurrent
clrRedStateChangeTime
OBJECT-TYPE
The time of the last change in the current redundancy state.
1.3.6.1.4.1.9.9.650.1.1.3.1.7TimeStampread-onlycurrent
clrRedContext
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.1.3.1.8OCTET STRINGread-createcurrent
clrRedStorageType
OBJECT-TYPE
The storage type for this conceptual row.
1.3.6.1.4.1.9.9.650.1.1.3.1.9StorageTyperead-createcurrent
clrRedRowStatus
OBJECT-TYPE
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).
1.3.6.1.4.1.9.9.650.1.1.3.1.10RowStatusread-createcurrent
clrRedundancyInfoTable
OBJECT-TYPE
This table contains information on the devices that are part of redundancy group.
1.3.6.1.4.1.9.9.650.1.1.4not-accessiblecurrent
clrRedundancyInfoEntry
OBJECT-TYPE
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'.
1.3.6.1.4.1.9.9.650.1.1.4.1not-accessiblecurrent
clrRedundancyPriority
OBJECT-TYPE
The priority value of this redundancy entry. This value is same as the value configured in 'clrRedPriority' for a redundancy group.
1.3.6.1.4.1.9.9.650.1.1.4.1.1Unsigned32 (1..255)read-onlycurrent
clrRedundancyState
OBJECT-TYPE
The current redundancy state.
1.3.6.1.4.1.9.9.650.1.1.4.1.2CiscoL4L7RedStateread-onlycurrent
clrRedundancyStateChangeTime
OBJECT-TYPE
The time of the last change in the current redundancy state.
1.3.6.1.4.1.9.9.650.1.1.4.1.3TimeStampread-onlycurrent
clrRedundancyIpAddressType
OBJECT-TYPE
The type of internet address by which this redundant device reachable.
1.3.6.1.4.1.9.9.650.1.1.4.1.4InetAddressTyperead-onlycurrent
clrRedundancyIpAddress
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.1.4.1.5InetAddressread-onlycurrent
clrStats
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.650.1.2
clrLBStatsTable
OBJECT-TYPE
This table contains the load balance statistics related to a redundancy group.
1.3.6.1.4.1.9.9.650.1.2.1not-accessiblecurrent
clrLBStatsEntry
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.2.1.1not-accessiblecurrent
clrLBStatsSharedStickyEntries
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.2.1.1.1Counter64read-onlycurrent
clrLBStatsSentPackets
OBJECT-TYPE
This object contains the number of valid packets that the local device sent to the peer.
1.3.6.1.4.1.9.9.650.1.2.1.1.2Counter64read-onlycurrent
clrLBStatsSendFailures
OBJECT-TYPE
This object contains the number of packets that the local device attempted to send to the peer, but failed.
1.3.6.1.4.1.9.9.650.1.2.1.1.3Counter64read-onlycurrent
clrLBStatsDroppedEntries
OBJECT-TYPE
This object contains the number of sticky entries that the peer sent to the local device, but the local device discarded them.
1.3.6.1.4.1.9.9.650.1.2.1.1.4Counter64read-onlycurrent
clrLBStatsReceivedPackets
OBJECT-TYPE
This object contains the number of valid packets that the local device received from the peer.
1.3.6.1.4.1.9.9.650.1.2.1.1.5Counter64read-onlycurrent
clrLBStatsReceiveFailures
OBJECT-TYPE
This object contains the number of packets that the peer sent to the local device, but the local device failed to receive them.
1.3.6.1.4.1.9.9.650.1.2.1.1.6Counter64read-onlycurrent
clrHAStatsTable
OBJECT-TYPE
This table contains the statistics related to a redundant peer.
1.3.6.1.4.1.9.9.650.1.2.2not-accessiblecurrent
clrHAStatsEntry
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.2.2.1not-accessiblecurrent
clrHAStatsTxHeartBeatMsgs
OBJECT-TYPE
This object refers to the number of heart beat messages sent to the peer.
1.3.6.1.4.1.9.9.650.1.2.2.1.1Counter64read-onlycurrent
clrHAStatsRxHeartBeatMsgs
OBJECT-TYPE
This object refers to the number of heart beat messages received from the peer.
1.3.6.1.4.1.9.9.650.1.2.2.1.2Counter64read-onlycurrent
clrHAStatsMissedHeartBeatMsgs
OBJECT-TYPE
This object refers to the number of missed heart beat messages.
1.3.6.1.4.1.9.9.650.1.2.2.1.3Counter64read-onlycurrent
clrHAStatsRxUniDirectionalHeartBeatMsgs
OBJECT-TYPE
This object indicates that the heartbeat messages from a peer is unidirectional. That is, the peer cannot receive ( only send ) heartbeats.
1.3.6.1.4.1.9.9.650.1.2.2.1.4Counter64read-onlycurrent
clrHAStatsHeartBeatTimeoutMismatches
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.2.2.1.5Counter64read-onlycurrent
clrHAStatsPeerUpEvents
OBJECT-TYPE
This object contains the number of peer up messages that the local device sent to the remote peer.
1.3.6.1.4.1.9.9.650.1.2.2.1.6Counter64read-onlycurrent
clrHAStatsPeerDownEvents
OBJECT-TYPE
This object contains the number of peer down messages that the local device sent to the remote peer.
1.3.6.1.4.1.9.9.650.1.2.2.1.7Counter64read-onlycurrent
clrNotifObjects
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.650.1.3
clrStateChangeNotifEnabled
OBJECT-TYPE
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.
1.3.6.1.4.1.9.9.650.1.3.1TruthValueread-writecurrent
ciscoLmRedundancyMIBConformance
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.650.2
ciscoLmRedundancyMIBCompliances
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.650.2.1
ciscoLmRedundancyMIBGroups
OBJECT-IDENTITY
1.3.6.1.4.1.9.9.650.2.2

Notifications

NameOIDStatus
clrRedundancyStateChange
NOTIFICATION-TYPE
The notification generated when the redundancy state is changed.
1.3.6.1.4.1.9.9.650.0.1current

Conformance

NameOIDStatus
ciscoLmRedundancyMIBCompliance
MODULE-COMPLIANCE
The compliance statement for entities which implement the L4L7 Switch Redundancy.
1.3.6.1.4.1.9.9.650.2.1.1current
clrPeerConfigGroup
OBJECT-GROUP
This group contains the peer configuration objects.
1.3.6.1.4.1.9.9.650.2.2.1current
clrRedConfigGroup
OBJECT-GROUP
This group contains the redundancy configuration objects.
1.3.6.1.4.1.9.9.650.2.2.2current
clrRedInfoGroup
OBJECT-GROUP
This group contains the redundancy information objects.
1.3.6.1.4.1.9.9.650.2.2.3current
cslbxNotifControlGroup
OBJECT-GROUP
The collection of objects to control the notifications for state changed in a L4 redundancy configuration.
1.3.6.1.4.1.9.9.650.2.2.4current
cslbxNotifGroup
NOTIFICATION-GROUP
This group contains the notifications related to redundancy.
1.3.6.1.4.1.9.9.650.2.2.5current
clrRedundancyStatsGroup
OBJECT-GROUP
This group contains objects related to redundant peer and load balacing statistics.
1.3.6.1.4.1.9.9.650.2.2.6current