Cannot manage new devices

New devices cannot be managed

The possible causes are:

  • The number of managed devices or MDAs exceeds the licensed quantity.

  • Large packet sizes from the managed devices are being dropped by intermediate routers because the packets exceed the device MTU, causing resynchronizations to fail.

Additional devices cannot be managed, but can be discovered, when the licensed MDA limit is exceeded.

Steps
CAUTION 

CAUTION

Service Disruption

Do not modify other nms-server.xml parameters. Modifying the file can seriously affect network management and performance of the NFM-P.

Consult technical support before you attempt to modify parameters.

 
1 

Check the license key status.

  1. The NFM-P generates an alarm when a license limit is exceeded or nearly exceeded. View the NFM-P alarm list in the client GUI, or use an OSS client to monitor the JMS alarm event stream for license alarms.

  2. Choose Help→NFM-P License Information from the NFM-P main menu. The NFM-P License (Edit) form opens.

  3. Click on the Devices and Quantities Licensed tab.

  4. View the information to ensure that the required Remaining quantity is not equal to zero.

    Note:

    If you have a new license that supports a greater number of managed objects, you can dynamically update the license without restarting the main server. See the NSP NFM-P Classic Management User Guide for information about updating an NFM-P license.

  5. Close the NFM-P License (Edit) form.

2 

Ensure that the new devices are configured to send SNMP packets of up to 9216 bytes. Check the MTU size, as described in Problem: Packet size and fragmentation issues.

End of steps