02-20-2014 04:26 AM
We are having HP NNMi 9.20 with latest patch 04 installed on Windows server 2008 R2.
We are facing issue in the Layer 2 connection.
When check the connectivity between the devices it shows that it is connected using the FDB topology source.
And We confirm with the network team, they mentioning that FDB was disabled before discovering the devices.
But still NNMi discover connectivity as FDB.
How we can correct this connectivity ?
Please suggest, if any have face this issue.
02-20-2014 05:04 AM
FDB isnt something one would enable or disable on a network device as normal operation. The FDB fowarding database table is used by a Layer 2 device (switch/bridge) to store the MAC addresses that have been learned and which ports that MAC address was learned on.
NNMi uses these tables to build the layer two connectivity between devices by cross referencing the tables at a per-device and per instance (for virtualized switching contexts).
If FDB were disabled on a switch , it would stop working.
Andy Kemp, CISSP
02-24-2014 11:06 PM
No, there is a proper channel while creating L-2 views.
First, it uses FDB to create the L-2 Path views ( we can also disable it node group wise ). And then if not available, then uses other protocols such as XDP, CDP etc to create these views.
If there are no such protocols which is not the case anywhere, because NNMi just takes the Mac table from switches and uses that information.
There may be some case, where one interface of a switch uses XDP, and other interface for another connecting switch uses FDB, then you may say the wrong topoloy L-2 View on NNMi.
Please appreciate by hitting kudos.
02-24-2014 11:08 PM
And yes, if no such protocols are running, then you can't see the L-2 Information on NNMi. You may see the neighbourship devices only in NNMi.
Please appreciate by hitting kudos
02-26-2014 09:22 AM
Thanks for information.
We just want confirm.
If Network team disabled these FDB/LLDP/CDP protocol, NNMi will not able to fetch Layer-2 connectivity details ?