Hello!
Recently our juniper EX series switches have moved over to a different ISP provider requiring us to set up an "routing-instance" in our switches for the layer 3 traffic forwarding.
This means that the default root routing isnt at a play when speaking to our server LAN and therefore don't have access to our NeDi client.
On our loopback interface we have an MGMT-IP wich is connected to the routing-instance from wich nedi will pull SNMP from, the only change in NeDi is the added IP-Adresses in netfilter and the adding of the vlan in the community config, like before it was public, but now it is 100-Data@Public where 100-Data is the routing-instance.
I get the MiB information from the switches but in NeDi only the Vlans and Loopback interfaces shows up and i cant see LLDP neighbours.
This also leads to a rather unpleasant 100-Data@SYS-SW01 name.
Has anyone experienced this before and can tell me if the problem is in the NeDi config och the SNMP config on the equipment?
I would suspect that there is both work needing to be done to connect default/root routing to the routing-instance in regards of the LLDP function, but as for "system name" i dont know if it's possible to configure it to not display the name of the routing-instance from the equipment or if it can be "hacked" away from NeDi Conf.
And if you cant tell im quite new to NeDi, much applies!