LBHUB-MSH-MIB :: resPairState

MIB Reference — IPNetwork Monitor

All MIBsLBHUB-MSH-MIBresPairState

resPairState

Module: LBHUB-MSH-MIB

OID (symbolic): LBHUB-MSH-MIB::resPairState

OID (numeric): 1.3.6.1.4.1.43.10.15.1.1.8

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description:

Each row in the table is in one of two states, 'invalid' or 'operational'. If the state is 'invalid', the resilient pair represented by this row is not active. There are several reasons why this may be the case. Firstly during the row creation process, not all information necessary may have been provided. Secondly an operational pair may become invalid because the resilient pair rules are no longer met because of a change in the MSH configuration. The rules are that both main and standby ports be on the same repeater and that the standby port be 'disable on boot'. Changing the standby card, moving one of the cards to a different repeater are two possible changes that can invalidate a pair configration.

If the parameters in the row are all valid then the pair becomes 'operational'.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.43.10.15.1.1.8
snmpwalk -v2c -c public <target> LBHUB-MSH-MIB::resPairState

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.43.10.15.1.1.8.1
snmpget -v2c -c public <target> LBHUB-MSH-MIB::resPairState.1

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.4privateBIANCA-BRICK-PPP-MIB
1.3.6.1.4.1enterprisesANIROOT-MIB
1.3.6.1.4.1.43a3ComA3COM-HUAWEI-OID-MIB
1.3.6.1.4.1.43.10genericA3Com-products-MIB
1.3.6.1.4.1.43.10.15mrmResilienceA3COM0004-GENERIC
1.3.6.1.4.1.43.10.15.1resTableA3COM0304-RESILIENTLINKS
1.3.6.1.4.1.43.10.15.1.1resTableEntryA3COM0304-RESILIENTLINKS
1.3.6.1.4.1.43.10.15.1.1.8resPairStateLBHUB-MSH-MIB