MIB Browser

Juniper-REDUNDANCY-MIB

Juniper Networks/Unisphere
The redundancy configuration MIB for Juniper Networks enterprise.
Organization
Juniper Networks, Inc.
Root OID
1.3.6.1.4.1.4874.2.2.74
Last updated
Objects
56
Source
Show full MIB
snmptranslate -m Juniper-REDUNDANCY-MIB -Tp
snmpwalk -v2c -c <community> -m Juniper-REDUNDANCY-MIB <host> 1.3.6.1.4.1.4874.2.2.74

Imports

Juniper-MIBsjuniMibs
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP
SNMPv2-MIBsysUpTime
SNMPv2-SMIBits, Integer32, IpAddress, MODULE-IDENTITY, MibIdentifier, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, TimeTicks, Unsigned32, iso
SNMPv2-TCDateAndTime, DisplayString, PhysAddress, RowStatus, TEXTUAL-CONVENTION, TruthValue

OID tree

NameOIDTypeAccessStatus
IjuniRedundancyMIB1.3.6.1.4.1.4874.2.2.74
NjuniRedundancyNotifications1.3.6.1.4.1.4874.2.2.74.0
!juniRedundancyColdSwitchoverNotification1.3.6.1.4.1.4874.2.2.74.0.1
!juniRedundancyWarmSwitchoverNotification1.3.6.1.4.1.4874.2.2.74.0.2
!juniRedundancyStateEnabledNotification1.3.6.1.4.1.4874.2.2.74.0.3
!juniRedundancyStateDisabledNotification1.3.6.1.4.1.4874.2.2.74.0.4
!juniRedundancyStatePendingNotification1.3.6.1.4.1.4874.2.2.74.0.5
!juniRedundancyModeNotification1.3.6.1.4.1.4874.2.2.74.0.6
!juniLcRedundancySwitchoverNotification1.3.6.1.4.1.4874.2.2.74.0.7
!juniLcRedundancyStateEnabledNotification1.3.6.1.4.1.4874.2.2.74.0.8
!juniLcRedundancyStateDisabledNotification1.3.6.1.4.1.4874.2.2.74.0.9
NjuniRedundancyObjects1.3.6.1.4.1.4874.2.2.74.1
NjuniRedundancyStatus1.3.6.1.4.1.4874.2.2.74.1.1
SjuniRedundancyActiveSlot1.3.6.1.4.1.4874.2.2.74.1.1.1Integer32 (0..255)RO
SjuniRedundancyActiveSlotState1.3.6.1.4.1.4874.2.2.74.1.1.2JuniRedundancyStateRO
SjuniRedundancyStandbySlot1.3.6.1.4.1.4874.2.2.74.1.1.3Integer32 (0..255)RO
SjuniRedundancyStandbySlotState1.3.6.1.4.1.4874.2.2.74.1.1.4JuniRedundancyStateRO
SjuniRedundancyLastResetReason1.3.6.1.4.1.4874.2.2.74.1.1.5JuniRedundancyResetReasonRO
SjuniRedundancyLastSystemActivationTime1.3.6.1.4.1.4874.2.2.74.1.1.6TimeTicksRO
SjuniRedundancyLastSystemActivationType1.3.6.1.4.1.4874.2.2.74.1.1.7JuniRedundancySystemActivationTypeRO
SjuniRedundancyHaActiveTime1.3.6.1.4.1.4874.2.2.74.1.1.8TimeTicksRO
NjuniRedundancyCfg1.3.6.1.4.1.4874.2.2.74.1.2
SjuniRedundancyNotifsEnabled1.3.6.1.4.1.4874.2.2.74.1.2.1TruthValueRW
SjuniRedundancyCfgRedundancyMode1.3.6.1.4.1.4874.2.2.74.1.2.2JuniRedundancyModeRW
NjuniRedundancyHistory1.3.6.1.4.1.4874.2.2.74.1.3
SjuniRedundancySystemActivationHistoryTableMaxLength1.3.6.1.4.1.4874.2.2.74.1.3.1Integer32 (0..50)RW
SjuniRedundancySystemActivationHistoryCommand1.3.6.1.4.1.4874.2.2.74.1.3.2JuniRedundancyHistoryCommandRW
TjuniRedundancySystemActivationHistoryTable1.3.6.1.4.1.4874.2.2.74.1.3.3NA
RjuniRedundancySystemActivationHistoryEntry1.3.6.1.4.1.4874.2.2.74.1.3.3.1NA
CjuniRedundancySystemActivationHistoryIndex1.3.6.1.4.1.4874.2.2.74.1.3.3.1.1Integer32NA
CjuniRedundancyHistoryResetType1.3.6.1.4.1.4874.2.2.74.1.3.3.1.2JuniRedundancyResetTypeRO
CjuniRedundancyHistoryActivationType1.3.6.1.4.1.4874.2.2.74.1.3.3.1.3JuniRedundancySystemActivationTypeRO
CjuniRedundancyHistoryPrevActiveSlot1.3.6.1.4.1.4874.2.2.74.1.3.3.1.4Integer32 (0..255)RO
CjuniRedundancyHistoryPrevActiveRelease1.3.6.1.4.1.4874.2.2.74.1.3.3.1.5DisplayStringRO
CjuniRedundancyHistoryCurrActiveSlot1.3.6.1.4.1.4874.2.2.74.1.3.3.1.6Integer32 (0..255)RO
CjuniRedundancyHistoryCurrActiveRelease1.3.6.1.4.1.4874.2.2.74.1.3.3.1.7DisplayStringRO
CjuniRedundancyHistoryResetReason1.3.6.1.4.1.4874.2.2.74.1.3.3.1.8JuniRedundancyResetReasonRO
CjuniRedundancyHistoryActivationTime1.3.6.1.4.1.4874.2.2.74.1.3.3.1.9DateAndTimeRO
SjuniRedundancyHistoryReloads1.3.6.1.4.1.4874.2.2.74.1.3.4Integer32RO
SjuniRedundancyHistoryColdSwitchovers1.3.6.1.4.1.4874.2.2.74.1.3.5Integer32RO
SjuniRedundancyHistoryWarmSwitchovers1.3.6.1.4.1.4874.2.2.74.1.3.6Integer32RO
NjuniLcRedundancyStatus1.3.6.1.4.1.4874.2.2.74.1.4
SjuniLcRedundancyActiveSlot1.3.6.1.4.1.4874.2.2.74.1.4.1Integer32 (0..255)AN
SjuniLcRedundancyStandbySlot1.3.6.1.4.1.4874.2.2.74.1.4.2Integer32 (0..255)AN
SjuniLcRedundancyLastResetReason1.3.6.1.4.1.4874.2.2.74.1.4.3JuniLcRedundancyResetReasonAN
SjuniLcRedundancyActivationType1.3.6.1.4.1.4874.2.2.74.1.4.4JuniLcRedundancySystemActivationTypeAN
SjuniLcRedundancyHaActiveTime1.3.6.1.4.1.4874.2.2.74.1.4.5TimeTicksAN
SjuniLcRedundancySwitchoverTime1.3.6.1.4.1.4874.2.2.74.1.4.6TimeTicksAN
NjuniRedundancyMIBConformance1.3.6.1.4.1.4874.2.2.74.2
NjuniRedundancyMIBCompliances1.3.6.1.4.1.4874.2.2.74.2.1
MjuniRedundancyMIBCompliance1.3.6.1.4.1.4874.2.2.74.2.1.1
NjuniRedundancyMIBGroups1.3.6.1.4.1.4874.2.2.74.2.2
GjuniRedundancyStatusGroup1.3.6.1.4.1.4874.2.2.74.2.2.1
GjuniRedundancyCfgGroup1.3.6.1.4.1.4874.2.2.74.2.2.2
GjuniRedundancyHistoryGroup1.3.6.1.4.1.4874.2.2.74.2.2.3
GjuniRedundancyNotificationGroup1.3.6.1.4.1.4874.2.2.74.2.2.4

Textual conventions

JuniLcRedundancyResetReason INTEGER

hardware(4) notKnown(2) poweron(1) software(5) userInitiated(3)

Reason codes for the reset of active line card that might result
in switch of control to standby line card.
      poweron       - indicates 'power-on' situation.
      notKnown      - Reason is unknown.
      userInitiated - A safe, manual reset was initiated by the user.
      hardware - reset was initiated due to hardware issue.
      software - reset was initiated due to software issue.
JuniLcRedundancySystemActivationType INTEGER

coldSwitch(2) reload(1) warmSwitch(3)

Various kinds of system activation:
reload      - line card has reloaded, i.e., no switchover has occurred.
coldSwitch  - line card switched over from active to standby linecard and no subscriber state is
                    maintained
warmSwitch  - line card switched over from active to standby linecards; line cards were
                     not reloaded during switchover.
JuniRedundancyHistoryCommand INTEGER

clear(2) keep(1)

Identifies the command to be performed on the system activation
history table.
    keep   - Retain history in persistent storage.
    clear  - Erase the current entries of juniRedundancySystemActivationHistoryTable.
JuniRedundancyMode INTEGER

fileSystemSynchronization(1) highAvailability(2)

The mode of the redundancy subsystem:
fileSystemSynchronization  - SRP synchronization is based on file synchronization.
highAvailability           - SRP synchronization is based on high availability
                             model that allows non-stop forwarding.
JuniRedundancyResetReason INTEGER

none(1) notKnown(2) userInitiated(3)

Reason codes for the reset of active SRP or a line card that might result
in switch of control to standby SRP or spare line card.
    none          - No reset or switchover has occurred and indicates 'power-on'
                    situation.
    notKnown      - Reason is unknown.
    userInitiated - A safe, manual reset was initiated by the user.
JuniRedundancyResetType INTEGER

linecardReload(4) linecardSwitchover(5) notKnown(1) srpReload(2) srpSwitchover(3)

Identifies the nature of the reset and slot types involved since the
system is powered on.
    notKnown            - Reset type is unknown.
    srpReload           - The reset involved reloading SRP slot(s).
    srpSwitchover       - The reset involved switchover of SRP slot(s).
    linecardReload      - The reset involved reloading the line card slot(s).
    linecardSwitchover  - The reset involved line card redundancy.
JuniRedundancyState INTEGER

active(6) disabled(3) fileSystemSyncing(2) initializing(4) notKnown(1) pending(5)

The current state of redundancy subsystem:
notKnown          - Redundancy state is unknown.
fileSystemSyncing - Redundancy operation is based on file system
                    synchronization.  SRP switchover stops forwarding.
disabled          - Redundancy operation is based on high availability
                    model but high availability is not yet operational.
                    SRP switchover stops forwarding.
initializing      - Redundancy operation is based on high availability
                    model and standby SRP is being bulk synchronized from
                    active SRP.  SRP switchover stops forwarding.
pending           - Redundancy operation is based on high availability
                    model and bulk synchronization of standby SRP completed.
                    SRP switchover stops forwarding.
active            - Redundancy operation is based on high availability model
                    and high availability is fully operational.  SRP
                    switchover does not stop forwarding.
JuniRedundancySystemActivationType INTEGER

coldSwitch(2) reload(1) warmSwitch(3)

Various kinds of system activation:
reload      - System has reloaded, i.e., no switchover has occurred.
coldSwitch  - System switched over from active to standby SRP and the
              switchover involved reloading of line cards interrupting
              forwarding.
warmSwitch  - System switched over from active to standby SRP; line cards were
              not reloaded during switchover and forwarding was uninterrupted.