CISCO-HSRP-MIB: View SNMP OID List / Download MIB
VENDOR: CISCO
Home | MIB: CISCO-HSRP-MIB | |||
---|---|---|---|---|
Download as: |
Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
|
|||
Object Name | OID | Type | Access | Info |
ciscoHsrpMIB | 1.3.6.1.4.1.9.9.106 |
The MIB module provides a means to monitor and configure the Cisco IOS proprietary Hot Standby Router Protocol (HSRP). Cisco HSRP protocol is defined in RFC2281. Terminology: HSRP is a protocol used amoung a group of routers for the purpose of selecting an 'active router' and a 'standby router'. An 'active router' is the router of choice for routing packets. A 'standby router' is a router that takes over the routing duties when an active router fails, or when preset conditions have been met. An 'HSRP group' or a 'standby group' is a set of routers which communicate using HSRP. An HSRP group has a group MAC address and a group Virtual IP address. These are the designated addresses. The active router assumes (i.e. inherits) these group addresses. 'Hello' messages are sent to indicate that a router is running and is capable of becoming the active or standby router. 'Hellotime' is the interval between successive HSRP Hello messages from a given router. 'Holdtime' is the interval between the receipt of a Hello message and the presumption that the sending router has failed. |
||
ciscoHsrpMIBObjects | 1.3.6.1.4.1.9.9.106.1 | |||
cHsrpGlobalConfig | 1.3.6.1.4.1.9.9.106.1.1 | |||
cHsrpConfigTimeout | 1.3.6.1.4.1.9.9.106.1.1.1 | unsigned32 | read-write |
The amount of time in minutes a row in cHsrpGrpTable can remain in a state other than active before being timed out. |
cHsrpGroup | 1.3.6.1.4.1.9.9.106.1.2 | |||
cHsrpGrpTable | 1.3.6.1.4.1.9.9.106.1.2.1 | no-access |
A table containing information on each HSRP group for each interface. |
|
1.3.6.1.4.1.9.9.106.1.2.1.1 | no-access |
Information about an HSRP group. Management applications use cHsrpGrpRowStatus to control entry modification, creation and deletion. Setting cHsrpGrpRowStatus to 'active' causes the router to communicate using HSRP. The value of cHsrpGrpRowStatus may be set to 'destroy' at any time. Entries may not be created via SNMP without explicitly setting cHsrpGrpRowStatus to either 'createAndGo' or 'createAndWait'. Entries can be created and modified via the management protocol or by the device's local management interface. A management application wishing to create an entry should choose the ifIndex of the interface which is to be added as part of an HSRP group. Also, a cHsrpGrpNumber should be chosen. A group number is unique only amongst the groups on a particular interface. The value of the group number appears in packets which are transmitted and received on a LAN segment to which the router is connected. The application must select the group number as explained in the description for cHsrpGrpNumber. If the row is not active, and a local management interface command modifies that row, the row may transition to active state. A row which is not in active state will timeout after a configurable period (five minutes by default). This timeout period can be changed by setting cHsrpConfigTimeout. |
||
cHsrpGrpNumber | 1.3.6.1.4.1.9.9.106.1.2.1.1.1 | unsigned32 | no-access |
This object along with the ifIndex of a particular interface uniquely identifies an HSRP group. Group numbers 0,1 and 2 are the only valid group numbers for TokenRing interfaces. For other media types, numbers range from 0 to 255. Each interface has its own set of group numbers. There's no relationship between the groups configured on different interfaces. Using a group number on one interface doesn't preclude using the same group number on a different interface. For example, there can be a group 1 on an Ethernet and a group 1 on Token Ring. More details can be found from RFC 2281. |
cHsrpGrpAuth | 1.3.6.1.4.1.9.9.106.1.2.1.1.2 | displaystring | read-only |
This is an unencrypted authentication string which is carried in all HSRP messages. An authentication string mismatch prevents a router interface from learning the designated IP address or HSRP timer values from other HSRP-enabled routers with the same group number. The function of this object is not to supply any sort of security-like authentication but rather to confirm that what's happening is what's intended. In other words, this is meant for sanity checking only. |
cHsrpGrpPriority | 1.3.6.1.4.1.9.9.106.1.2.1.1.3 | unsigned32 | read-only |
The cHsrpGrpPriority helps to select the active and the standby routers. The router with the highest priority is selected as the active router. In the priority range of 0 to 255, 0 is the lowest priority and 255 is the highest priority. If two (or more) routers in a group have the same priority, the one with the highest ip address of the interface is the active router. When the active router fails to send a Hello message within a configurable period of time, the standby router with the highest priority becomes the active router. A router with highest priority will only attempt to overthrow a lower priority active router if it is configured to preempt. But, if there is more than one router which is not active, the highest priority non-active router becomes the standby router. |
cHsrpGrpPreempt | 1.3.6.1.4.1.9.9.106.1.2.1.1.4 | truthvalue | read-only |
This object, if TRUE, indicates that the current router should attempt to overthrow a lower priority active router and attempt to become the active router. If this object is FALSE, the router will become the active router only if there is no such router (or if an active router fails). |
cHsrpGrpPreemptDelay | 1.3.6.1.4.1.9.9.106.1.2.1.1.5 | unsigned32 | read-only |
This delay is the time difference between a router power up and the time it can actually start preempting the currently active router. When a router first comes up, it doesn't have a complete routing table. If it's configured to preempt, then it will become the Active router, but it will not be able to provide adequate routing services. The solution to this is to allow for a configurable delay before the router actually preempts the currently active router. |
cHsrpGrpUseConfiguredTimers | 1.3.6.1.4.1.9.9.106.1.2.1.1.6 | truthvalue | read-only |
HSRP routers learn a group's Hellotime or Holdtime from hello messages. The Hellotime is used to determine the frequency of generating hello messages when this router becomes the active or standby router. The Holdtime is the interval between the receipt of a Hello message and the presumption that the sending router has failed. If this object is TRUE, the cHsrpGrpConfiguredHelloTime and cHsrpGrpConfiguredHoldTime will be used. If it is FALSE, the Hellotime and Holdtime values are learned. |
cHsrpGrpConfiguredHelloTime | 1.3.6.1.4.1.9.9.106.1.2.1.1.7 | unsigned32 | read-only |
If cHsrpGrpUseConfiguredTimers is true, cHsrpGrpConfiguredHelloTime is used when this router is an active router. Otherwise, the Hellotime learned from the current active router is used. All routers on a particular LAN segment must use the same Hellotime. |
cHsrpGrpConfiguredHoldTime | 1.3.6.1.4.1.9.9.106.1.2.1.1.8 | unsigned32 | read-only |
If cHsrpGrpUseConfiguredTimers is true, cHsrpGrpConfiguredHoldTime is used when this router is an active router. Otherwise, the Holdtime learned from the current active router is used. All routers on a particular LAN segment should use the same Holdtime. Also, the Holdtime should be at least three times the value of the Hellotime and must be greater than the Hellotime. |
cHsrpGrpLearnedHelloTime | 1.3.6.1.4.1.9.9.106.1.2.1.1.9 | unsigned32 | read-only |
If the Hellotime is not configured on a router, it can be learned from the Hello messages from active router, provided the Hello message is authenticated. If the Hellotime is not learned from a Hello message from the active router and it is not manually configured, a default value of 3 seconds is recommended. |
cHsrpGrpLearnedHoldTime | 1.3.6.1.4.1.9.9.106.1.2.1.1.10 | unsigned32 | read-only |
If the Holdtime is not configured on a router, it can be learned from the Hello message from the active router. Holdtime should be learned only if the Hello message is authenticated. If the Holdtime is not learned and it is not manually configured, a default value of 10 seconds is recommended. |
cHsrpGrpVirtualIpAddr | 1.3.6.1.4.1.9.9.106.1.2.1.1.11 | ipaddress | read-only |
This is the primary virtual IP address used by this group. If this address is configured (i.e a non zero ip address), this value is used. Otherwise, the agent will attempt to discover the virtual address through a discovery process (which scans the hello messages). |
cHsrpGrpUseConfigVirtualIpAddr | 1.3.6.1.4.1.9.9.106.1.2.1.1.12 | truthvalue | read-only |
If this object is TRUE, cHsrpGrpVirtualIpAddr was a configured one. Otherwise, it indicates that cHsrpGrpVirtualIpAddr was a learned one. |
cHsrpGrpActiveRouter | 1.3.6.1.4.1.9.9.106.1.2.1.1.13 | ipaddress | read-only |
Ip Address of the currently active router for this group. |
cHsrpGrpStandbyRouter | 1.3.6.1.4.1.9.9.106.1.2.1.1.14 | ipaddress | read-only |
Ip Address of the currently standby router for this group. |
cHsrpGrpStandbyState | 1.3.6.1.4.1.9.9.106.1.2.1.1.15 | hsrpstate | read-only |
The current HSRP state of this group on this interface. |
cHsrpGrpVirtualMacAddr | 1.3.6.1.4.1.9.9.106.1.2.1.1.16 | macaddress | read-only |
Mac Addresses used are as specified in RFC 2281. For ethernet and fddi interfaces, a MAC address will be in the range 00:00:0c:07:ac:00 through 00:00:0c:07:ac:ff. The last octet is the hexadecimal equivalent of cHsrpGrpNumber (0-255). Some Ethernet and FDDI interfaces allow a unicast MAC address for each HSRP group. Certain Ethernet chipsets(LANCE Ethernet, VGANYLAN and QUICC Ethernet) only support a single Unicast Mac Address. In this case, only one HSRP group is allowed. For TokenRing interfaces, the following three MAC addresses are permitted (functional addresses): C0:00:00:01:00:00 C0:00:00:02:00:00 C0:00:00:04:00:00. |
cHsrpGrpEntryRowStatus | 1.3.6.1.4.1.9.9.106.1.2.1.1.17 | rowstatus | read-only |
The control that allows modification, creation, and deletion of entries. For detailed rules see the DESCRIPTION for cHsrpGrpEntry. |
cHsrpGrpIpNone | 1.3.6.1.4.1.9.9.106.1.2.1.1.18 | truthvalue | read-only |
This object specifies the disable HSRP IPv4 virtual IP address. |
cHsrpMIBNotificationPrefix | 1.3.6.1.4.1.9.9.106.2 | |||
cHsrpMIBNotifications | 1.3.6.1.4.1.9.9.106.2.0 | |||
cHsrpStateChange | 1.3.6.1.4.1.9.9.106.2.0.1 |
A cHsrpStateChange notification is sent when a cHsrpGrpStandbyState transitions to either active or standby state, or leaves active or standby state. There will be only one notification issued when the state change is from standby to active and vice versa. |
||
cHsrpConformance | 1.3.6.1.4.1.9.9.106.3 | |||
cHsrpCompliances | 1.3.6.1.4.1.9.9.106.3.1 | |||
cHsrpCompliance | 1.3.6.1.4.1.9.9.106.3.1.1 |
The compliance statement for all hosts implementing the CISCO-HSRP-MIB. |
||
cHsrpComplianceRev1 | 1.3.6.1.4.1.9.9.106.3.1.2 |
The object group is deprecated by the cHsrpComplianceRev2 |
||
cHsrpComplianceRev2 | 1.3.6.1.4.1.9.9.106.3.1.3 |
The compliance statement for all hosts implementing the CISCO-HSRP-MIB. |
||
cHsrpComplianceGroups | 1.3.6.1.4.1.9.9.106.3.2 | |||
cHsrpConfigGroup | 1.3.6.1.4.1.9.9.106.3.2.1 |
The collection of objects used to set global configuration objects for the HSRP MIB. |
||
cHsrpGrpGroup | 1.3.6.1.4.1.9.9.106.3.2.2 |
The collection of objects used to add, delete and retrieve information about HSRP groups. |
||
cHsrpNotificationsGroup | 1.3.6.1.4.1.9.9.106.3.2.3 |
The collection of notifications used to indicate HSRP state information. |
||
cHsrpGrpGroupSup | 1.3.6.1.4.1.9.9.106.3.2.4 |
The collection of objects used to add, delete and retrieve information about HSRP groups. |