Question about the topology

[vclaudiatja]

Hello,

I have a question regarding the topology.
I am an intern in a lab company (the switch they use is juniper) and my mentor assigned me to manage the switch by using the NAV software.
As you can see from the photo, it doesn't show any port connected to any devices but it shows potential neighbours but unrecognisable.
I tried to find the solution in NAV documentation but still not working 🥲.

Hopefully you can help us
Thank you very much

[vclaudiatja]

Extra information

My tutor tried to send you email in details what protocol that we used but the email couldn’t go thorugh.
I will paste the message here

Hello,

We have deployed nav to manage juniper switchs (ex3300, ex2200, ex2300,
ex3400, ex4550, ex4650). We have created NAPALM profile and it works for
view and manage the ports.

But we can not see the topology in netmap.

Our switchs are interconnected with LACP agregate trunk links.

We have set ssh port to 830, set system services netconf ssh port 830

and activated LLDP protocols with:
set protocols lldp interface all
set protocols lldp-med interface all

Can you please help us to resolve this problem.

Thank you very much.

Bests Regards.

Responsable informatique de l'IPCMS
Institut de Physique et de Chimie des Matériaux de Strasbourg

[lunkwill42]

Are all the switches added to NAV? Are all background processes in NAV running without error (are all the ipdevpoll collection jobs for the switches shown as green in the ipdevinfo web tool?), especially the topology cron job?

You pasted bits of "direct neighborship candidate" reports, but are all the link ports actually represented in these ports with realistic candidates?

Usually, LLDP information is pretty reliable to build topology from, but it all depends on all the devices being recorded in SeedDB and NAV being able to identify them from the reported LLDP records.

There is sometimes also some issues with timestamps on the LLDP data tables themselves that causes NAV to use invalid cached data, but we can get into that if nothing else helps...

[fabien3103]

Hello,

I am the mentor of Claudia.
We have still the same problem.

Here are some other informations

Switch one (ipcms-ex3300-bat74) is connected with to agregate 10 Gb interface to switch 2 (ipcms-ex3300-datacenter)

ipcms-ex3300-bat74> show lldp

LLDP : Enabled
Advertisement interval : 30 seconds
Transmit delay : 2 seconds
Hold timer : 4 seconds
Notification interval : 0 Second(s)
Config Trap Interval : 0 seconds
Connection Hold timer : 300 seconds
Port ID TLV subtype : interface-name
Port Description TLV type : interface-alias (ifAlias)

LLDP MED : Enabled
MED fast start count : 3 Packets

Interface Parent Interface LLDP LLDP-MED Power Negotiation
all - Enabled Enabled Enabled

ipcms-ex3300-bat74> show lldp neighbors

xe-0/1/1.0 ae0.0 5c:45:27:ad:7f:40 xe-0/1/1.0 ipcms-ex3300-datacenter
xe-1/1/1.0 ae0.0 5c:45:27:ad:7f:40 xe-3/1/1.0 ipcms-ex3300-datacenter

ipcms-ex3300-datacenter> show lldp

LLDP : Enabled
Advertisement interval : 30 seconds
Transmit delay : 2 seconds
Hold timer : 4 seconds
Notification interval : 0 Second(s)
Config Trap Interval : 0 seconds
Connection Hold timer : 300 seconds
Port ID TLV subtype : interface-name
Port Description TLV type : interface-alias (ifAlias)

LLDP MED : Enabled
MED fast start count : 3 Packets

Interface Parent Interface LLDP LLDP-MED Power Negotiation
all - Enabled Enabled Enabled

ipcms-ex3300-datacenter> show lldp neighbors

xe-0/1/1.0 ae1.0 7c:e2:ca:6f:ea:80 xe-0/1/1.0 ipcms-ex3300-bat74
xe-3/1/1.0 ae1.0 7c:e2:ca:6f:ea:80 xe-1/1/1.0 ipcms-ex3300-bat74

Hopefully you can help us
Thank you very much

[lunkwill42]

Sorry, you got me in the middle of my summer vacation, @fabien3103, so I didn't see this when I got back - I only noticed it now.

What I get from your screenshots and info is that ipcms-ex3300-bat74 has these aggregate uplinks to ipcms-ex3300-bat74:

xe-0/1/1.0 ae1.0 7c:e2:ca:6f:ea:80 xe-0/1/1.0 ipcms-ex3300-bat74
xe-3/1/1.0 ae1.0 7c:e2:ca:6f:ea:80 xe-1/1/1.0 ipcms-ex3300-bat74

However, I don't see the relation to the original post from @vclaudiatja, which seems to list details from other switches.

What do the neighbor candidate lists look like for these six interfaces on ipcms-ex3300-bat74:

• xe-0/1/1
• xe-0/1/1.0
• xe-3/1/1
• xe-3/1/1.0
• ae1
• ae1.0

The neighbor candidate report for each individual interface can be found by clicking on the arrow-out-of-the-box symbol behind "To IP device" in the port details view:

This report should show which potential neighbor candidates NAV has collected information about from this port. Usually, there will be a lot of CAM-based source data, but if there is LLDP-based source data as well, NAV will give that more importance.

The big question is whether there is collected data, and then whether that data makes sense.

Sometimes the LLDP data is just on the physical ports, sometimes just from the aggregate/virtual ports, sometimes from both. This tends to vary between vendors, and I cannot recall how Juniper does it it, which is why I'm asking for data for all 6 involved interfaces.

[lunkwill42]

Oh, and I also noticed that your IP Device details views have no reachability statistics at all, which makes it look like pping is not running. Are all your background processes actually running? What's the output of the nav status shell command?