Community in read only mode June 18 & 19
This community will be set in READ ONLY mode for a while on Tuesday June 18 into Wednesday June 19 while we import content and users from our Micro Focus Forums community site. MORE INFORMATION
Highlighted
Established Member.. Amrita_priya
Established Member..
165 views

NNM has not detected the L2\L3 connectivity in topology maps

Hi Community,

We are running NNM 9.23 on Linux red-hat 5.5.

We have added one router and one switch, they are connected via an interface but NNM has not detected the connectivity in topology maps.

Both devices are responding to SNMP and current status is Normal.

Please assist.

Regards,

Amrita

0 Likes
1 Reply
Micro Focus Expert
Micro Focus Expert

Re: NNM has not detected the L2\L3 connectivity in topology maps

Hi Amrita,

You could perform some basic checks that may hint the cause of the missing L2/L3 connection.

  1. Are both these devices discovered/managed by the NNMi Station locally, or are these remote nodes (i.e managed by an NNMi RNM) ?

  2 Verify that the participating nodes/interfaces are present in the NNMi inventory and being managed.

  3. Execute a configuration poll on both these devices (#nnmconfigpoll.ovpl) and study the command results to capture if these devices deliver on xDP (CDP/LLDP) or FDB data.

  4. Dump the WorkingSet to confirm if the two devices belong to the same working set. And the state of the WorkingSet is 'Clean' -

      #nnmtwiddle.ovpl invoke com.hp.ov.nms.disco:name=WorkingSet dumpWorkingSet "" "" "" true "" >> D:\workingSet.txt

      Sample results -

                ------------------------------------------------
                WorkingSet 8623517284 has nodes 63, analyzed 1, state Clean
                ------------------------------------------------
                Access Switch 01/67454     false      true            null
                End Node 01/2196685895     false     false      2195585900
                ------------------------------------------------
                Node  isRouter  isSwitch     L3Iface


  5. Dump the L2 connection info for a node -

      #nnmtwiddle.ovpl invoke com.hp.ov.nms.disco:name=TroubleShooter dumpL2ConnectionInfo <Node_IP>

      Sample results-

       L2Connection Name: CISCO-DC-6509-CDR.mtsindia.in[Gi1/4/13],ABC NIPS[eth1]
       L2Connection Status: NORMAL
       L2Connection Source: FDB

       L2Connection Name: CISCO-DC-6509-CDR.mtsindia.in[Gi1/4/26],INDIA_DR_R3[Gi0/1]
       L2Connection Status: NORMAL
       L2Connection Source: FDB

  6. Check if the following .ovpl is present on your NNMi v9.2x box (NNMi_Support directory). If yes, then collect the results of the command and send it to HPE Support for further investigation.

     #nnmCheckConnections.ovpl -walk “IP_of_Router, IP_of_Switch”

Regards,

Ashish Rai

HPE Support

The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HPE

If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.