cancel
Showing results for 
Search instead for 
Did you mean: 

VOSS (Fabric Engine) VRRP Status SNMP

VOSS (Fabric Engine) VRRP Status SNMP

jeronimo
Contributor III

Neither Rapidcity MIB

.1.3.6.1.4.1.2272.1.73

Nor VRRP MIB

.1.3.6.1.2.1.68

seem to provide any info.

I have specified the proper snmp context (vrf).
It shows more stuff than GlobalRouter (notably routing table etc. so we know it's the correct vrf) but where is the vrrp info?

.1.3.6.1.4.1.2272.1.73.1.1.2 (rcVrrpOperTable)
or
.1.3.6.1.2.1.68.1.3 (vrrpOperTable)
would be useful.
Notably the Master/Backup state.

Thx

(FE 9.0.4)

1 ACCEPTED SOLUTION

TokenRingJoe
New Contributor

I am going to assume that you are using VRRP v3 as 1.3.6.1.4.1.2272.1.73 does work for v2.   For v3 use rcVrrpv3 (1.3.6.1.4.1.2272.1.206)

My trick to finding mibs is to take a wireshark trace of an EDM session and then look through the payload.  You will find clues like this:

command=getTableVariables&userId=admin&vrfId=0&varNames=indexNA%2CrcVrrpTmpOperationsPrimaryIpAddr

View solution in original post

5 REPLIES 5

LoefAlex
New Contributor

Hi Jeronimo and TokenRingJoe.

I see the same issue, but the OID for "VRRP Operations State" remain empty.

FE: 9.0.4.0
VRF 100
VRRP-Version: 3
SNMP-View: "vrf"

# SNMP V3 MIB VIEW CONFIGURATION
snmp-server view "ALL" 1
snmp-server view "vrf" 1.3.6.1.4.1.2272.1.206

OBJECT: rcVrrpTmpOperationsState=1.3.6.1.4.1.2272.1.206.1.1.7.1.5
This object should return  { initialize(1), backup(2), master(3) } but it is empty.

Does your query reply any value? 

Do you have any idea whats wrong here?

Thanks in advance
Alex

I got it by myself. You need to add the context string into your query.

1. Login to the switch
2. show snmp-server context ("" = no context, vrf100, vrf200, etc)
3. Check your snmp tool where to add the context string

Now it works
regards
Alex

TokenRingJoe
New Contributor

I am going to assume that you are using VRRP v3 as 1.3.6.1.4.1.2272.1.73 does work for v2.   For v3 use rcVrrpv3 (1.3.6.1.4.1.2272.1.206)

My trick to finding mibs is to take a wireshark trace of an EDM session and then look through the payload.  You will find clues like this:

command=getTableVariables&userId=admin&vrfId=0&varNames=indexNA%2CrcVrrpTmpOperationsPrimaryIpAddr

Very nice, thanks.

I've never used EDM ... I thought it was used to manage a single switch. Can you connect to remote ones?
Anyway, I could've sniffed XIQ-SE's session or so, but I'd have had to revert back to unencrypted snmp etc. first...

Well, thanks.

GTM-P2G8KFN