Suppressed Device are incorrectly put in UnManaged State with NSM/Spectrum Integration (Legacy KB ID CNC TS34177 )

Document ID : KB000051534
Last Modified Date : 14/02/2018
Show Technical Document Details

To fix this do the following:

    • Change the Model _Name attribute of the model in Spectrum, replace the while space and "," into "_"; we should also change the sysname of the device if it is possible.

    • Change the NSM device name in the NSM MCC.
      a) In MCC, select the device object in left panel in Topology view;
      b) Select "Properties" view in the right panel, and modify the name of the device object, make it as the same the Model_Name you have specified in the step 1.
      c) Confirm your NSM name change in the 2D map, and confirm you could find the device object via the "obrowser" command.

    • Execute the "restartSpect.bat" from the NSM, which is in the integration module installation directory.
      The final result should fix the problem and modified the name of the "CallManager_Host,2" to "CallManager_Host_2".

    • [optional] If you like, you could :
      a) delete the obsolete Spectrum MO:  run command "nodeview ?target <spectrumserver>", delete the child node, which is representing the obsolete Spectrum MO;
      b) rename the object name in MCC


    Related Issues/Questions:
    Suppressed Device are incorrectly put in UnManaged State with NSM/Spectrum Integration

    Problem Environment:
    Spectrum 9.1
    NSM Integration

    Causes of this problem:

    When using Spectrum-NSM integration module 5.0, this suppressed devices may still show up as in a Managed State in NSM. 

    This problem might be caused by the device?s invalid name, which will cause the NSM DSM to not managed the device. To confirm the device is not managed by DSM, you can do following:

    run "obrowser" command

    In the show up window, check "MO Name", do not input anything, click "search" button;

    In the search result, if the device is not show up in the result list, then the device is not managed by the DSM.

    This problem may very likely caused by a character like ',' and white space in a NSM device name, which is from the device?s sysname.


    (Legacy KB ID CNC TS34177 )