Morgan,
I had not noticed this behavior before, but I get the same results on a
3400 cluster. I think what is throwing you off is that the
jnxRedundancyTable was designed to apply to Routing Engines, such as on
the MX platform. Since you can have multiple Redundancy Groups, etc. on
the SRX, the redundancy feature on the SRX doesn't line up well with what
this MIB was designed to do.
Let's compare your output from the SRX with an MX router with dual REs:
Your SRX cluster:
JUNIPER-MIB::jnxRedundancyContentsIndex.9.1.0.0 = INTEGER: 9
JUNIPER-MIB::jnxRedundancyContentsIndex.9.3.0.0 = INTEGER: 9
JUNIPER-MIB::jnxRedundancyL1Index.9.1.0.0 = INTEGER: 1
JUNIPER-MIB::jnxRedundancyL1Index.9.3.0.0 = INTEGER: 3
JUNIPER-MIB::jnxRedundancyL2Index.9.1.0.0 = INTEGER: 0
JUNIPER-MIB::jnxRedundancyL2Index.9.3.0.0 = INTEGER: 0
JUNIPER-MIB::jnxRedundancyL3Index.9.1.0.0 = INTEGER: 0
JUNIPER-MIB::jnxRedundancyL3Index.9.3.0.0 = INTEGER: 0
JUNIPER-MIB::jnxRedundancyDescr.9.1.0.0 = STRING: node0 Routing Engine 0
JUNIPER-MIB::jnxRedundancyDescr.9.3.0.0 = STRING: node1 Routing Engine 0
JUNIPER-MIB::jnxRedundancyConfig.9.1.0.0 = INTEGER: master(2)
JUNIPER-MIB::jnxRedundancyConfig.9.3.0.0 = INTEGER: master(2)
JUNIPER-MIB::jnxRedundancyState.9.1.0.0 = INTEGER: master(2)
JUNIPER-MIB::jnxRedundancyState.9.3.0.0 = INTEGER: master(2)
JUNIPER-MIB::jnxRedundancySwitchoverCount.9.1.0.0 = Counter32: 0
JUNIPER-MIB::jnxRedundancySwitchoverCount.9.3.0.0 = Counter32: 0
JUNIPER-MIB::jnxRedundancySwitchoverTime.9.1.0.0 = Timeticks: (0) 0:00:00.00
JUNIPER-MIB::jnxRedundancySwitchoverTime.9.3.0.0 = Timeticks: (739204)
2:03:12.04
JUNIPER-MIB::jnxRedundancySwitchoverReason.9.1.0.0 = INTEGER:
neverSwitched(2)
JUNIPER-MIB::jnxRedundancySwitchoverReason.9.3.0.0 = INTEGER:
neverSwitched(2)
An MX with 2 REs:
JUNIPER-MIB::jnxRedundancyContentsIndex.9.1.0.0 = INTEGER: 9
JUNIPER-MIB::jnxRedundancyContentsIndex.9.2.0.0 = INTEGER: 9
JUNIPER-MIB::jnxRedundancyL1Index.9.1.0.0 = INTEGER: 1
JUNIPER-MIB::jnxRedundancyL1Index.9.2.0.0 = INTEGER: 2
JUNIPER-MIB::jnxRedundancyL2Index.9.1.0.0 = INTEGER: 0
JUNIPER-MIB::jnxRedundancyL2Index.9.2.0.0 = INTEGER: 0
JUNIPER-MIB::jnxRedundancyL3Index.9.1.0.0 = INTEGER: 0
JUNIPER-MIB::jnxRedundancyL3Index.9.2.0.0 = INTEGER: 0
JUNIPER-MIB::jnxRedundancyDescr.9.1.0.0 = STRING: Routing Engine 0
JUNIPER-MIB::jnxRedundancyDescr.9.2.0.0 = STRING: Routing Engine 1
JUNIPER-MIB::jnxRedundancyConfig.9.1.0.0 = INTEGER: master(2)
JUNIPER-MIB::jnxRedundancyConfig.9.2.0.0 = INTEGER: backup(3)
JUNIPER-MIB::jnxRedundancyState.9.1.0.0 = INTEGER: master(2)
JUNIPER-MIB::jnxRedundancyState.9.2.0.0 = INTEGER: backup(3)
JUNIPER-MIB::jnxRedundancySwitchoverCount.9.1.0.0 = Counter32: 1
JUNIPER-MIB::jnxRedundancySwitchoverCount.9.2.0.0 = Counter32: 0
JUNIPER-MIB::jnxRedundancySwitchoverTime.9.1.0.0 = Timeticks: (655)
0:00:06.55
JUNIPER-MIB::jnxRedundancySwitchoverTime.9.2.0.0 = Timeticks: (0)
0:00:00.00
JUNIPER-MIB::jnxRedundancySwitchoverReason.9.1.0.0 = INTEGER:
userSwitched(3)
JUNIPER-MIB::jnxRedundancySwitchoverReason.9.2.0.0 = INTEGER: other(1)
The differences are apparent here, as the SRX just shows a single "Routing
Engine 0". That being said, it might be really helpful for Juniper to
expand/modify this mib to support SRX clusters, or put in a new mib. But
I am not aware that they have done this --- at least on the flavor of 10.4
that I am running or later.
Clarke Morledge
College of William and Mary
Information Technology - Network Engineering
Jones Hall (Room 18)
Williamsburg VA 23187
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
