Do you how to do discovery for a Juniper stacked swtiches since the member switches have dynamic IPs?

[jomonmathew]

Do you how to do discovery for a Juniper stacked switches since the member switches have dynamic IPs?

[Dubz]

I've not tested but i think discovery identifies unique CI's based on MAC address by default. It shouldn't matter if their IP changes.

[jomonmathew]

Hi David,

But if the member switches IPs are configured as loop back IPs or virtual IPs will the discovery able to identify them since those IPs are not in the IP range we are given for scanning.

[Alexey7]

Discovery utilizes logic from the last step of Network Switch pattern called "Stacked Switches". Basically, discovery uses SNMP to look for all siblings of a stack (entPhysicalContainedIn) and identifies master/slave relationships (entPhysicalParentRelPos) from there.

Hope it helps.

[Severin Launiau]

Actually we just came across that issue: the OIDs used in that Staked Switches step are part of the RFC 4133, Entity MIB:

Name: entPhysicalIndex

OID: 1.3.6.1.2.1.47.1.1.1.1.1

And unfortunately these OIDs are not supported by some of the devices we have (https://www.juniper.net/documentation/en_US/junos/topics/concept/standard-mib-overview.html):

RFC 4133, Entity MIB

Unsupported tables and objects: entityLogicalGroup table entPhysicalMfgDate and entPhysicalUris objects in entityPhysical2Group table entLPMappingTable and entPhysicalContainsTable in entityMappingGroup table entityNotoficationsGroup table

Only MX240, MX480, and MX960 routers, and EX2200 and EX3300 switches

If that limitation is confirmed, we will likely use .1.3.6.1.4.1.2636.3.1.8.1.6 instead.

Séverin