ENTERASYS-RIPv2-EXT-MIB
The ENTERASYS-RIPv2-EXT-MIB enables SNMP-based configuration and monitoring of Routing Information Protocol version 2 (RIPv2) parameters on Enterasys Networks hardware, specifically managing protocol timers, authentication settings, and interface-specific routing attributes.
Imported Objects
Objects
17 total| Object Name |
|---|
etsysRip2ExtMIBThis MIB module defines a portion of the SNMP MIB under the Enterasys Networks enterprise OID pertaining to the RIPv2 configuration This MIB was designed to be used for configuring the RIP-2 protocol parameters. MODULE-IDENTITY .1.3.6.1.4.1.5624.1.2.66 |
etsysRip2ExtObjects OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.66.1 |
etsysRip2ExtGlobals OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.66.1.1 |
etsysRip2ExtAdminStatusThe current administrative state of the RIP protocol. Setting this object to adminStatusUp turns on the RIP protocol, while setting it to adminStatusDown turns off the RIP protocol. When the object is set to adminStatusUp, it triggers the RIP process to begin normal operation by populating its routing table and sending/receiving routing updates. Setting this object to adminStatusDown turns off the RIP protocol. This causes the etsysRip2ExtOperStatus object to change its state to operStatusGoingDown. This has the effect of removing all of the RIP routes from the RIB.rw Enumeration .1.3.6.1.4.1.5624.1.2.66.1.1.1 |
etsysRip2ExtOperStatusThe current operational state of the RIP Protocol. Changing the state of the etsysRip2ExtAdminStatus object may effect the state of this object. If etsysRip2ExtAdminStatus is set to adminStatusDown, this object's status is changed to operStatusGoingDown. Once the RIP process has finished cleaning up its routing table and freeing its resources, the status is changed to operStatusDown. If etsysRip2ExtAdminStatus is set to adminStatusUp, this object's status is changed to operStatusGoingUp. After RIP allocates its resources and begins operation, the status of this object changes to operStatusUp. If there are problems acquiring the resources needed to operate the RIP protocol, the status changes to operStatusActFailed.ro Enumeration .1.3.6.1.4.1.5624.1.2.66.1.1.2 |
etsysRip2ExtMaxEcmpHopsThe maximum number of equal-cost next hops that RIP can program in the Routing Table Manager. Changing this value causes RIP to refresh all of its routes in the Routing Table Manager with the new maximum number of equal-cost next hops.rw Unsigned32 .1.3.6.1.4.1.5624.1.2.66.1.1.3 |
etsysRip2ExtRefreshIntervalThe frequency at which RIP sends periodic updates to all of its peers. A change to this value takes effect after the next periodic update is sent.rw Unsigned32 .1.3.6.1.4.1.5624.1.2.66.1.1.4 |
etsysRip2ExtTriggeredDelayMinThe lower bound of the random time period that RIP waits between sending Triggered Updates. A change to this value takes effect after the next Triggered Update is sent. This value MUST be less than etsysRip2ExtTriggeredDelayMax.rw Unsigned32 UNITS "seconds" .1.3.6.1.4.1.5624.1.2.66.1.1.5 |
etsysRip2ExtTriggeredDelayMaxThe upper bound of the random time period that RIP waits between sending Triggered Updates. A change to this value takes effect after the next Triggered Update is sent. This value MUST be greater than etsysRip2ExtTriggeredDelayMin.rw Unsigned32 UNITS "seconds" .1.3.6.1.4.1.5624.1.2.66.1.1.6 |
etsysRip2ExtRouteCheckIntervalThe frequency with which RIP checks the routing table for expired routes. A change to this value takes effect after the next scheduled route check.rw Unsigned32 .1.3.6.1.4.1.5624.1.2.66.1.1.7 |
etsysRip2ExtRouteExpiryIntervalThe period from the point of the last refresh after which a route received from a peer times out and is marked as expired. This period is expressed as a multiple of the etsysRip2ExtRouteCheckInterval. A change to this value takes effect at the next scheduled route check.rw Unsigned32 .1.3.6.1.4.1.5624.1.2.66.1.1.8 |
etsysRip2ExtRouteFlushIntervalThe period from the point of route expiry that a route is finally removed from the routing table, also known as the 'garbage collection time'. This period is expressed as a multiple of the etsysRip2ExtRouteCheckInterval. A change to this value takes effect at the next scheduled route check.rw Unsigned32 .1.3.6.1.4.1.5624.1.2.66.1.1.9 |
etsysRip2ExtConformance OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.66.2 |
etsysRip2ExtGroups OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.66.2.1 |
etsysRip2ExtGlobalGroupThis group defines global controls for Enterasys RIPv2 systems. Unknown .1.3.6.1.4.1.5624.1.2.66.2.1.1 |
etsysRip2ExtCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.5624.1.2.66.2.2 |
etsysRip2ExtComplianceThe compliance statement for devices that support etsysRip2Ext. Unknown .1.3.6.1.4.1.5624.1.2.66.2.2.1 |
More MIBs from Enterasys
Browse all EnterasysMIBs →The ENTERASYS-OIDS-MIB module provides the foundational Object Identifier (OID) definitions required for SNMP-based monitoring of Enterasys Networks hardware system attributes, including device identity, software versions, and hardware inventory. It serves as the structural registry enabling network management systems to map and retrieve specific system-level metrics from Enterasys switches, routers, and wireless controllers.
The ENTERASYS-CLASS-OF-SERVICE-MIB manages transmission and reception attributes for Quality of Service (QoS) classification on Extreme Networks (formerly Enterasys) edge and access devices. It enables SNMP-based configuration and monitoring of traffic prioritization policies, including queue mapping, scheduling, and bandwidth allocation parameters.
The ENTERASYS-FIREWALL-MIB enables SNMP-based configuration, policy management, and real-time monitoring of Enterasys firewall appliances, specifically exposing metrics for access control rules, session states, and interface traffic statistics.
The ENTERASYS-LSNAT-MIB provides management access to Layer 4 Session NAT (LSNAT) entities on Enterasys Networks hardware, enabling the monitoring of active session states, translation table entries, and packet/byte counters for protocol-specific NAT mappings.
The ENTERASYS-POLICY-PROFILE-MIB enables SNMP-based monitoring and configuration of per-user policy profiles on Enterasys network edge and access devices. It facilitates the retrieval and management of specific user authentication and authorization parameters, including assigned access control lists and traffic shaping rules, to enforce granular network access policies.
The ENTERASYS-TWCB-MIB-2 module enables monitoring and management of Time-Weighted Cost-Based (TWCB) routing metrics and interface attributes on Enterasys Networks switches. It provides specific counters and gauges for tracking path costs and link states to support advanced traffic engineering and load balancing decisions.