Troubleshooting the NNMi->BSM Topology integration

Hi,

In NNMi 10.10 on Linux we use a topology integration with BSM. When nodes are added in NNMi, they normally get the ODB_ID custom attribute that they should, due to this integration. A few nodes don't however. 

How do we troubleshoot the NNMi-BSM topology integration in the best manner when this happens? Which logs etc. should we look into, or are there any commands to find nodes that are "stuck" somewhere in the integration pipe?

BR,
Frank Mortensen
Managon AB

Parents
  • Hello Frank,

     

    you can enable tracing (/opt/OV/support/nnmsetlogging.ovpl) for the bsm integration and you can use the BSM integration methodes in the JMX console for some tests.

     

    I think, that you have checked the nodes in RTSM that they were modified by the NNMi integration.

     

    HTH and kind regards

     

    Allessandro

Reply
  • Hello Frank,

     

    you can enable tracing (/opt/OV/support/nnmsetlogging.ovpl) for the bsm integration and you can use the BSM integration methodes in the JMX console for some tests.

     

    I think, that you have checked the nodes in RTSM that they were modified by the NNMi integration.

     

    HTH and kind regards

     

    Allessandro

Children