MIB Changes - Luke Warm Spare Fail Over vs. vpnFailOverDetected

DonL
Getting noticed

MIB Changes - Luke Warm Spare Fail Over vs. vpnFailOverDetected

Hi, 

In the MIB I got from the console a * while* ago  7.6.23 was a fail over trap 

# warmSpareFailoverDetected networkName
1.3.6.1.4.1.29671.1.1.7.6.23 0x06ba0016 1.3.6.1.4.1.29671.1.1.2.1.2(1,2)\
# organizationName
1.3.6.1.4.1.29671.1.1.1(3,0)\
# devMac
1.3.6.1.4.1.29671.1.1.4.1.1(4,0)\
# devStatus
1.3.6.1.4.1.29671.1.1.4.1.3(5,0)


Someone Compiles some Discount MIB while I'm *Away* 

# vpnFailoverDetected networkName
1.3.6.1.4.1.29671.1.1.7.6.23 0x06ba0016 1.3.6.1.4.1.29671.1.1.2.1.2(1,2)\
# organizationName
1.3.6.1.4.1.29671.1.1.1(3,0)


And Warm Fail over is not vpn fail over ???

Did the that trap Change from one version to the *Next* "

True or False "

Thanks, 

Don

2 Replies 2
alemabrahao
Kind of a big deal
Kind of a big deal

Warm Spare refers to the redundancy of the MXs, VPN fail over refers to the VPN, they are different things.
 
If there have been any changes, only Meraki will be able to inform you, so I suggest you open a support case.
I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.

Indeed they do refer to differing conditions - which make it more concerning that they should somehow Both be tied to the same trap ? 

Thanks, 

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.