CUBE HA state SNMP monitoring

cukouncukoun · ‎12-15-2015

Hi all,

we have 2 ISR4451 (IOS-XE) gateways configured as one CUBE HA pair. I would like to know how is it possible to monitor state of each gateway through SNMP - if its on ACTIVE,STANDBY or PROTECTED mode as you can see through CLI below.

This is very important because CUBE node which is on the PROTECTED state needs to be reloaded to start to work again as pair with the second node.

#show voice high-availability rf-client
IDLE RF DOMAIN: 0x2

-----
RF Domain: 0x0
Voice HA Client Name: VOIP RF CLIENT
Voice HA RF Client ID: 1345
Voice HA RF Client SEQ: 129
My current RF state ACTIVE (13)
Peer current RF state DISABLED (1)

Current VOIP HA state [LOCAL / PEER] :
        [PROTECTED (13) / UNKNOWN (0)]

VOIP HA RF CB Data:
        ENABLED:1
        flags: 0x6 [PEER_COMM_DOWN/PEER_PRESENCE_DOWN/IN-BOX HA]
        red_mode: 0

-----
RF Domain: 0x2 [RG: 1]
Voice HA Client Name: VOIP RG CLIENT
Voice HA RF Client ID: 4054
Voice HA RF Client SEQ: 461
My current RF state STANDBY HOT (8)
Peer current RF state ACTIVE (13)

Current VOIP HA state [LOCAL / PEER] :
        [PROTECTED (8) / ACTIVE (13)]

VOIP HA RF CB Data:
        ENABLED:0
        flags: 0x0 [PEER_COMM_UP/PEER_PRESENCE_UP/IN-BOX HA]
        red_mode: 0
        rg_flags: 0x0
                ctrl [UP/NO SHUT]
                data [UP/NO SHUT]
                traffic (TOT:2; SH:0, DN:0) [UP/NO SHUT]

-----
Voice HA Standby is not available.
System has not experienced switchover.

Thanks

Tomas

jsteinberg · ‎04-26-2016

Did you have any luck with this task ?

cukouncukoun · ‎04-26-2016

No I didn't :-(. I also openned TAC case and they confirmed to me that these parametres are not possible to be monitored over SNMP - there is NO MIB for this, really very unbelievable from Cisco that this is not there.

If you look to the available SNMP MIBs you will find that there is really huge number of unnecessary parametres that you can monitor over SNMP and on the other side there is also lot of parametres which are really important but are not available over SNMP :-).

There is just one option how to monitor this - EEM+TCL or scheduled TCL script from which you can send SNMP traps to the monitoring system.

Tom