For classic devices, selecting Manage, Unmanage or Manage, Delete from an NE Table row actions menu () performs the selected function in the underlying classic management system.

The unmanage function may be used for unusual conditions such as when the NSP requires a complete refresh of device data because of data corruption. If the discovery rule runs while the NE is in Not Managed status, the discovery operation skips the NE. When the NE is re-managed, the NE is resynchronized with the NSP.

For model-driven devices, the Unmanage action is not supported in the current release.

When a device is deleted, regardless of whether it is managed through classic or MD mediation, the NE will be re-discovered in the next scanning interval unless the IP address of the NE is removed from the associated unified discovery rule.

The following table summarizes the differences between unmanaging and deleting an NE.

Action	Data changes	Backup behavior 1	Discovery behavior
Unmanage (classic devices only)	All management data is removed, for example: alarms physical links object names and descriptions	If NFM-P is used to back up your classic devices, backup files are deleted when the NE is unmanaged. Retention cannot be configured. Nokia recommends using backup operations within NSP to create NE backups. If NSP is used to perform backups, backup files remain in the NSP File Server after an NE is unmanaged. After the NE has been re-discovered and managed, you can restore the backup; see How do I restore an NE from a backup?. You can still perform backup operations in NSP: the operation will skip the unmanaged device the next time it runs.	The discovery operation skips the NE while NE is in Not Managed state. When the NE is managed again, the NE is resynchronized with the NSP. After the NE has been re-discovered and managed, you can restore a backup taken using NSP; see How do I restore an NE from a backup?.
Delete (classic or MD devices)	All management data is removed.	If NFM-P is used to back up your classic devices, you can configure retention of backups after NE deletion; see “How do I configure backup-file retention for deleted NEs?” in the NSP System Administrator Guide. You can use retained backups to assist in recovering a device that was deleted in error. If you are using NSP to perform backups, backup files remain in the NSP File Server.	The next discovery operation discovers the NE again unless the NE IP address is removed from the unified discovery rule. After the NE has been re-discovered and managed, you can restore a backup taken using NSP; see How do I restore an NE from a backup?.

Notes:

1. Backup files taken by NFM-P are stored on the NFM-P server. Backup files taken by NSP are stored in the NSP File Server.