Skip to main content

/centreon_cisco_standard_snmp.pl --plugin=network::cisco::standard::snmp::plugin --mode=stack
is doing fine for physical stack switches.
We have some stackwise virtual switches in fine condition, but this check is showing up as ‘notredundant’.

old classical stack:
OK: Stack status is 'redundant' - Number of members waiting: 0, progressing: 0, added: 0, ready: 2, SDM mismatch: 0, version mismatch: 0, feature mismatch: 0, new master init: 0, provisioned: 0, invalid: 0, removed: 0 - All stack members status are ok | 'waiting'=0;;;0; 'progressing'=0;;;0; 'added'=0;;;0; 'ready'=2;;;0; 'sdm_mismatch'=0;;;0; 'version_mismatch'=0;;;0; 'feature_mismatch'=0;;;0; 'new_master_init'=0;;;0; 'provisioned'=0;;;0; 'invalid'=0;;;0; 'removed'=0;;;0;
.1.3.6.1.4.1.9.9.500.1.1.3.0 = 1
.1.3.6.1.4.1.9.9.500.1.2.1.1.3.1000 = 1
.1.3.6.1.4.1.9.9.500.1.2.1.1.3.2000 = 4
.1.3.6.1.4.1.9.9.500.1.2.1.1.4.1000 = 15
.1.3.6.1.4.1.9.9.500.1.2.1.1.4.2000 = 14
.1.3.6.1.4.1.9.9.500.1.2.1.1.5.1000 = 0
.1.3.6.1.4.1.9.9.500.1.2.1.1.5.2000 = 0
.1.3.6.1.4.1.9.9.500.1.2.1.1.6.1000 = 4
.1.3.6.1.4.1.9.9.500.1.2.1.1.6.2000 = 4
.1.3.6.1.2.1.47.1.1.1.1.7.1000 = Switch 1
.1.3.6.1.2.1.47.1.1.1.1.7.2000 = Switch 2
Member 'Switch 1' state is 'ready', role is 'master'
Member 'Switch 2' state is 'ready', role is 'standby'

new virtual stack:
CRITICAL: Stack status is 'notredundant' | 'waiting'=0;;;0; 'progressing'=0;;;0; 'added'=0;;;0; 'ready'=2;;;0; 'sdm_mismatch'=0;;;0; 'version_mismatch'=0;;;0; 'feature_mismatch'=0;;;0; 'new_master_init'=0;;;0; 'provisioned'=0;;;0; 'invalid'=0;;;0; 'removed'=0;;;0;
.1.3.6.1.4.1.9.9.500.1.1.3.0 = 2
.1.3.6.1.4.1.9.9.500.1.2.1.1.3.2 = 1
.1.3.6.1.4.1.9.9.500.1.2.1.1.3.500 = 4
.1.3.6.1.4.1.9.9.500.1.2.1.1.4.2 = 1
.1.3.6.1.4.1.9.9.500.1.2.1.1.4.500 = 1
.1.3.6.1.4.1.9.9.500.1.2.1.1.5.2 = 0
.1.3.6.1.4.1.9.9.500.1.2.1.1.5.500 = 0
.1.3.6.1.4.1.9.9.500.1.2.1.1.6.2 = 4
.1.3.6.1.4.1.9.9.500.1.2.1.1.6.500 = 4
.1.3.6.1.2.1.47.1.1.1.1.7.2 = Switch 1 Chassis
.1.3.6.1.2.1.47.1.1.1.1.7.500 = Switch 2 Chassis
Member 'Switch 1 Chassis' state is 'ready', role is 'master'
Member 'Switch 2 Chassis' state is 'ready', role is 'standby'
 

Can I manipulate the OID .1.3.6.1.4.1.9.9.500.1.1.3.0 = 2 in a way, that cswRingRedundant = 2 is ‘ok’?

Hello,

Have you tried to change the critical-stack-status ?

Hi,
I have, but does it send notifications then, once something gets critical?
To ignore ANY status is not the goal for monitoring.

Wouldn’t it rather make sense to discover the cswStackType - oid .1.3.6.1.4.1.9.9.500.1.1.7 - and act as needed or to have a --mode=vstack ?
Something like this would make me feel more comfortable.

there are a few article also on other monitoring platform, one from librenms where someone has been in touch with the cisco support that explained that this status is to be ignored as it is pointless to check that status on a virtual stack

 

but you can post on the github a suggestion

Reply


Terms & ConditionsCookie settings