Migration of CLI managed NGE to NFM-P managed NGE
Migration overview
If you have been using CLI for NGE management before setting up the NFM-P, you can migrate the NGE to the NFM-P after the NFM-P is installed and operational.
When the NFM-P is performing NGE migration from CLI to NFM-P managed NGE, the NFM-P tracks the key groups and encryption keys from the CLI NGE configurations and auto downloads key groups and encryption keys as necessary for all the services requiring encryption. In the end, the cleanup scheduled task removes un-used key groups and keys from CLI.
After the migration, do not make any NGE changes via CLI, including for troubleshooting purposes. If this occurs, the NFM-P generates a mismatch alarm and, if there is service impact, the NFM-P reverts the changes from CLI.
Migration scenarios
Migration from CLI NGE to NFM-P NGE is available in several scenarios. The process the user must perform in the NFM-P after node discovery differs slightly depending on the scenario.
See Workflow for migration of NGE management from CLI to NFM-P for details and prerequisites.
The following table shows the available scenarios and how the process differs in each.
|
Scenario |
Configuration process in NFM-P after the node is discovered |
|---|---|
|
Key group is the same on CLI and NFM-P VPRN and PW Template are configured on CLI but not in the NFM-P |
Add the VPRN and the PW Template in the NFM-P, and encrypt |
|
Key group and services are configured in CLI but not in the NFM-P |
Create the key group, add the services, and encrypt |
|
Key group and services are configured the same in both CLI and NFM-P |
No further action is needed: the node will be discovered directly into the key group and services. |
|
Key group and services are configured in CLI and NFM-P CLI key group is different from the key group in NFM-P, for example, the CLI key group is number 77 and the NFM-P key group is 60. |
No further action is needed: the NFM-P will create key group 60 on the CLI and move the services to key group 60 on the NFM-P. If the migration leaves key group 77 unused on the CLI, the NGE cleanup task will remove it. |
NSP alarms
If there is a difference between CLI and NFM-P NGE configuration, alarms will be generated as follows:
-
The NSP raises a ConfigurationUnknown alarm if configuration is present on the CLI that is not present on the NFM-P
ConfigurationUnknown alarms for global encryption label, key group, VPRN, and PW templates will be suppressed for first time node discovery. However, these alarms will be raised when there is subsequent addition of the key group or service association from CLI after the node has been discovered. Or if node resync is done after the node is already discovered by NFM-P and before the migration from CLI to NGE is completed.
ConfigurationUnknown alarms for SDP, WLAN GW, L2 and L3 interfaces configured via CLI will still be present upon node discovery.
-
The NSP raises a ConfigurationMismatch alarm if the NGE configuration on an NE is modified using CLI.
During migration from CLI, the alarms are suppressed.