ConnectNow Feature @ Atlas, Links between Juniper Devices not getting discovered.

Hello everyone,

Recentley i been working a lot with Juniper devices and it looks like there is an issue with the Topology data polling from Juniper Devices.

I've got few Juniper EX series discovered with the Network Discovery tool within NPM, i did a little research and i found out that somtimes Topology data shown for those devices, but even then, it showing incorrect data, i ran a simulation of the production environment at my lab :

Took the same model devices running on the production and tried to discover their Topology data with few different OS versions, the result always been the same, somtimes Topology data shown but incorrect and somtimes not shown at all.

I was trying to run SNMP walk to see if the required OIDs from the bellow kb is shown ( Object IDs and information Orion Platform poll for NTM - SolarWinds Worldwide, LLC. Help and Support )

However, there is many OIDs missing when i did the walk.

As well, i was trying to see if anyone else had similar issue here at TWHACK but i couldn't find any.

Did anyone ever had such issue or if there is any work around to get those devices to work with Connectnow ?

Thank you guys

Find more posts tagged with

connectnow

npm

atlas maps

npm 12.1

Accepted answers

All comments

melmstedt

I am aware that NTA and Atlas utilize multiple fields to build out the topology. I am very familiar with Atlas and the topology issue and have finally figured it out to be an issue of the way NPM views the logical interface and not having capability to join that data with the layer 2 and layer 3 data properly. This is at least why, when I only monitor logical pretty I had more success but that does not accurately represent the circuit or trunk.

In sorry, the new version of NPM with "live mapping" ability does do a slightly better joi but it stops at the router. Should you desire a "real topology" of all nodes and trunks it requires NTA which is better but still has issues.

Final note, we are currently up a creek without a paddle sure to the upgrade and while there are great new features, being the one to identify a bug is not my idea of a great time.

Good luck,

Matthew

sja

Me 2 not a good friend with Solarwinds disco engine.

I think it's works just fine if you have pure Cisco with CDP.

But when it's LLDP and multi vendors and LAG interface.. you getting problems.

1.control that LLDP is enable on the EX.

2.control that interfaces and L2/L3 are enable in "list resurces"

3. update disco

Still not working ?

Support@solarwinds

Please vote so they will take a good look on that...

mesverrum

Since he looked at the OIDs topology uses and said his device doesn't support them then you are really not even going to get anywhere with support. Your device is not compatible with the model they used to determine the relationships so the feature will not work as is. Your best bet is to set up a feature request and try to get some votes to get some attention on your specific hardware. Ultimately they built their tool under the assumption of the OIDs you find on Cisco gear, so the topology mapping is pretty hit or miss with anything else. Juniper has not really been a top priority up to this point from what I've seen.

lesojiri

Hello,

I had a same issue with Juniper switches too. There is a problem that these switches shows OID tree not from the beginning but somewhere in the middle.

You can force it to read SNMP OID tree using these commands :

snmp {

engine-id {

use-mac-address; - this command is to force switch to use its MAC as a key for SNMPv3 (otherwise auth key is changed during any config change in SNMP)

}

view view-all {

oid 1 include; - this command forces switch to read from SNMP OID .1

}

Without oid 1 include switch do not replays anything for Topology related OIDs requests.

(Juniper is a nightmare - worst switches have ever seen - so so many bugs in it)