tmnxSrrpInstanceIdMismatch
TIMETRA-MC-REDUNDANCY-MIB ·
.1.3.6.1.4.1.6527.3.1.3.40.0.9
Object
notification
[CAUSE] The notification tmnxSrrpInstanceIdMismatch is generated when
an SRRP instance has detected that at least one SAP it is protecting
is associated with a different SRRP instance on the remote peer.
[EFFECT] One or more SAPs are not protected by SRRP.
[RECOVERY] Verify configuration on the local and remote end routers to
ensure that all SAPs are associated with the same SRRP instance on
both sides.
Context
- MIB
- TIMETRA-MC-REDUNDANCY-MIB
- OID
.1.3.6.1.4.1.6527.3.1.3.40.0.9- Type
- notification
- Status
- current
- Parent
- tmnxMcRedundancyNotifications
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workNotifications are emitted by an agent; they cannot be read with snmpget or walked.
Inspect the notification definition
/usr/bin/snmptranslate -Pud -Ir -Td -m 'TIMETRA-MC-REDUNDANCY-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-MC-REDUNDANCY-MIB::tmnxSrrpInstanceIdMismatch'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-MC-REDUNDANCY-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-MC-REDUNDANCY-MIB::tmnxSrrpInstanceIdMismatch'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of