Dev Status * meaning* of variable passed with warmSpareFailoverDetected Trap

[DonL]

Hello, 

We are implementing trap support for a number of state changes on Meraki devices. 

One trap is -  warmSpareFailoverDetected  

devStatus OBJECT-TYPE
SYNTAX INTEGER { offline(0), online(1) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The status of the device's connection to the Meraki Cloud Controller"

I am wondering what device Status *Means* 
case 1 : 
DevStatus =  offline  ?  I have switched over to the Spare ( primary switch Offline ) ? 
DevStatus =  online  ?  I have switched Back from the Spare ( primary switch Online ) ? 
case 2:
DevStatus =  offline  ?  I am NO longer running on the Spare ? 
DevStatus =  online  ?  The Spare switch is Active ? 

I am leaning towards Case 1 - but looking for confirmation or corroboration 🙂 

Then I would use the status of Offline as the Set Alarm 
then the OnLine status would be the Clear Alarm !

Thanks, 
Don

[PhilipDAth]

I don't think you can use that as an indicator of failover.

All it is telling you is if it has a current connection to the Meraki cloud.

[DonL]

Hello Phil, 

I would expect a Trap called - warmSpareFailoverDetected - would be indicative that a Failover event had been observed? 
Unless the people in charge / responsible for the SNMP Agent development have an even more perverse sense of humor than I can imagine ? 

The 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)

Perhaps being a bit naïve I expected that the device and devstatus would be informing us that the primary is Offline and " We" have failed over to the Warm Spare.
the recovery state would be when the primary is Online 

That's my story and i'm sticking to it...

Don

[PhilipDAth]

When I read this bit:
DESCRIPTION "The status of the device's connection to the Meraki Cloud Controller"

I got the impression this was for monitoring connection to the Meraki cloud.

[DonL]

I guess *Everything* talks to the Meraki Controller and that's the perspective from which the determination is made as to whether the devices is Up or Not 🙂
( which might not be quite true - the devices might be Just Fine and functioning in the customers isolated environment... but the Controller can't reach then so there Down 😞 

???