Cisco_redundancy check -

Hello,

I am doing hard to understand the meaning of this cisco_redundancy check:

WARN - Switchover - 
Old status: Unit ID: 1 (active), Peer ID: 2 (standby hot), Duplex mode: True (SUB-Peer detected), 
New status: Unit ID: 2 (active), Peer ID: 1 (standby hot), Duplex mode: True (SUB-Peer detected)

Due to power supply problems, the stack changed its master. Both members are up and healthy, Duplex is still active and both peers see each other.

Why does this check report this as a WARNING?

Thanks,
Simon

take a look for the Unit ID`s they have switched …

It is only that the master switch is recognized from the monitoring guys :slight_smile:
Now normally a “tabula rasa” on booth device will set the current status as ok.
Only if there is again a master switch it will be shown as warning.

The check cisco_redundancy resolves to WARN if the parameter init_states is found in the SNMP data. (line 92)

image

From what I can see, on the check side there is no evaluation of the unit ID assignment to determine a state.
To find out how to set this parameter, I have grepped the whole OMD site for init_states - without any further result.

Shouldn’t be there a WATO definition to set init_states ?
What is the corresponding rule name then? :thinking:

Thanks & regards,
Simon

The inventory functions is remembering the init_states if i see it correctly

def inventory_cisco_redundancy(info):
    try:
        swact_reason = info[0][5]
    except IndexError:
        pass
    else:
        if swact_reason != "1":
            return [(None, {"init_states": info[0][:5]})]
    return []

The check only then compares this to the current state. If it is identical → Ok

Hi Andreas,

honestly, I missed the inventory part completely.
You’re absolutely right, the service gets configured with the stack state found at this time.
And any stack switchover must be followed then by a “tabula rasa” inventory scan.

Thanks a lot.

BR
Simon

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed. Contact @fayepal if you think this should be re-opened.