EZ5 MIB Catalog

ARISTA-REDUNDANCY-MIB

2014-08-15

This MIB module provides configuration and status information pertaining to high availability or redundancy infrastructure on Arista devices. As such, this MIB module is aimed at providing relevant information on 'Modular Systems' which support dual supervisors for control plane redundancy. Each of the dual supervisors are referred to as 'unit' in the module.

Download ARISTA-REDUNDANCY-MIB.txt Open ARISTA-REDUNDANCY-MIB.txt in a new tab

SCALARS (3) · TABLES (1) · TRAPS (1)

Scalars (3)

NameOID
aristaRedundancyProtocolConfig1.3.6.1.4.1.30065.3.8.0.0.1
aristaRedundancyProtocolOper1.3.6.1.4.1.30065.3.8.0.0.2
aristaRedundancyLastSwOverReason1.3.6.1.4.1.30065.3.8.0.0.4

Tables (1)

NameOID
aristaRedundancyUnitStateTable1.3.6.1.4.1.30065.3.8.0.0.3

Traps (1)

NameOID
aristaRedundancySwitchOverNotif1.3.6.1.4.1.30065.3.8.1.0.1

END OF TOC

Scalar details

aristaRedundancyProtocolConfig

1.3.6.1.4.1.30065.3.8.0.0.1

AristaRedundancyProtocol0 = unknown1 = simplex2 = rpr3 = ssoThe redundancy protocol. unknown - The protocol is unknown. simplex - The peer unit will remain disabled with this protocol. rpr - Route Processor Redundancy. This protocol allows the startup configuration files to be synchronized between the units but not the active operational state. sso - Stateful Switchover. This protocol allows the peer units to synchronize not only configuration but also operational state so when the active unit fails, the peer can take over control plane responsibilities. · Integer32

Indicates the configured redundancy protocol in the system.

aristaRedundancyProtocolOper

1.3.6.1.4.1.30065.3.8.0.0.2

AristaRedundancyProtocol0 = unknown1 = simplex2 = rpr3 = ssoThe redundancy protocol. unknown - The protocol is unknown. simplex - The peer unit will remain disabled with this protocol. rpr - Route Processor Redundancy. This protocol allows the startup configuration files to be synchronized between the units but not the active operational state. sso - Stateful Switchover. This protocol allows the peer units to synchronize not only configuration but also operational state so when the active unit fails, the peer can take over control plane responsibilities. · Integer32

Indicates the operational redundancy protocol in the system.

aristaRedundancyLastSwOverReason

1.3.6.1.4.1.30065.3.8.0.0.4

OCTET STRING SIZE (0..255)

The reason for the last switchover in the system.

Table details

aristaRedundancyUnitStateTable

1.3.6.1.4.1.30065.3.8.0.0.3

Index: aristaRedundancyUnitId

This table contains the current redundancy state information for the units in the system.

aristaRedundancyUnitId

1.3.6.1.4.1.30065.3.8.0.0.3.1.1

Unsigned32

A unique identifier representing a unit. Usually it is the slot number of the inserted unit on the given modular system.

aristaRedundancyUnitState

1.3.6.1.4.1.30065.3.8.0.0.3.1.2

AristaRedundancyState0 = unknown1 = standby2 = active3 = disabledThe status of the unit. unknown - The redundancy status is unknown. standby - The unit is initialized, and is in the standby state. active - The unit is currently in active mode. The SNMP agent runs only on the active unit. disabled - The unit is currently disabled. · Integer32

The current state of the given unit.

aristaRedundancyUnitStateEntryTime

1.3.6.1.4.1.30065.3.8.0.0.3.1.3

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The value of sysUpTime when the unit entered the given state.

Trap details

aristaRedundancySwitchOverNotif

1.3.6.1.4.1.30065.3.8.1.0.1

A switchover notification is generated whenever a unit becomes active and it has taken over the control plane duties.

aristaRedundancyUnitStateEntryTime

1.3.6.1.4.1.30065.3.8.0.0.3.1.3

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The value of sysUpTime when the unit entered the given state.

aristaRedundancyLastSwOverReason

1.3.6.1.4.1.30065.3.8.0.0.4

OCTET STRING SIZE (0..255)

The reason for the last switchover in the system.

↑ To TOC