NNMi Support Tip: Best practice for Phantom/Orphaned Connections (FDB)
NNMi 9.1. Patch 1 / NNMi 9.2x includes some changes that prevent the creation of phantom connections with connection source FDB. However, those connections that already exist in the database will remain. The following steps clean out and re-calculate all FDB connections in an effort to remove phantom connections.
In order to remove these phantom connections, do the following steps using the new script nnml2maint.ovpl (found in /opt/OV/support on Unix, and %NnmInstallDir%\support on Windows):
# nnml2maint.ovpl deleteAllFDBConnections
# nnml2maint.ovpl reAnalyzeAllWorkingSets
The first script example removes all existing FDB connections in the NNMi database. The second script example schedules the FDB connections to be recalculated. This recalculation may take from 15 minutes up to a few hours to complete, depending on the size of the NNMi database.
[nnmsupport]$ ./nnml2maint.ovpl deleteAllFDBConnections
WARNING: Running this tool removes all L2 connections derived from
switch FDB tables so that they can be recalculated.
1Is it OK to remove these connections? [n] y
Deleting 94 connections from the database.
Total connections deleted: 94
[nmsupport]$ ./nnml2maint.ovpl reAnalyzeAllWorkingSets
SwitchFdb2Conns should be kicked off in 5 minutes
The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP.
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution, If you are satisfied with anyone’s response please remember to give them a KUDOS and show your appreciation.