Workflow to recover from ADP discovery failure
Process
If the NSP host server restarts or switches over to a redundant server during ADP, the ADP process will fail. In this scenario, NFM-P will show ADP Off. To recover from an ADP failure due to a restart or switchover, perform
Stage 1 through
Stage 3. For any other ADP failure, perform
Stage 4 through
Stage 6.
Scenario 1: ADP failure caused by an NSP host server restart or switchover
|
|
|
1 |
Perform the following in the NFM-P:
-
If an NGE domain is created in the cellular domain and the NGE domain is encrypted, create inbound and outbound ACL IP exception filters on the head-end nodes; see
To configure an ACL IP exception filter policy. Apply the new ACL IP exception filters to the gateway interfaces in the NGE domain.
-
For an inbound IP exception filter, the Source IP parameter must be set to the subnet IP address of the cellular domain. The Destination IP must be set to the IP address of the active NSP host server.
-
For an outbound IP exception filter, the Source IP parameter is set to the IP address of the active NSP host server. The Destination IP is set to the IP address of the 7705 SAR-Hm to be discovered.
Delete the failed sites from the cellular domain:
-
Choose Manage→Cellular Domains from the NFM-P main menu. The Cellular Domain Manager form opens.
-
Click Search and choose the cellular domain that initiated the failed ADP operation. The Cellular Domain [Edit] form opens.
-
Click on the Sites tab.
-
Choose a site from the list and click Delete.
-
Repeat for all sites in the domain for which ADP failed.
-
If the NE is already in a managed state, delete it from the NFM-P discovery manager; see
To delete a device from the managed network.
-
Delete the rule element corresponding to the NE from discovery rules created by ADP for the domain; see
To configure a discovery rule.
-
If the ADP System IP Address parameter is set to Verify, reload the XML file to the cellular domain.
|
2 |
Perform the following on the NE. See the NE documentation for more information.
-
Establish an SSHv2 session to the NE from either a terminal window or the NFM-P.
-
Restore the BOF file to factory default.
-
Delete the existing 7705 SAR-Hm config file.
-
Reboot the NE.
|
3 |
Perform the following in the NFM-P:
If ACL IP exception filters were created in
Stage 1
a
-
Remove the ACL IP exception filter from the gateway interfaces in the NGE domain.
-
Delete both inbound and outbound ACL IP exception filters; see
To configure an ACL IP exception filter policy.
-
Enable ADP; see
To enable and monitor the ADP discovery process.
|
Scenario 2: Other ADP failure
|
|
|
4 |
Perform the following in the NFM-P:
-
Disable ADP; see
To disable ADP.
-
If an NGE domain is created in the cellular domain and the NGE domain is encrypted, create inbound and outbound ACL IP exception filters on head-end nodes; see
To configure an ACL IP exception filter policy. Apply the new ACL IP exception filters to the gateway interfaces in the NGE domain.
-
For an inbound IP exception filter, the Source IP parameter must be set to the subnet IP address of the cellular domain. The Destination IP must be set to the IP address of the active NSP host server.
-
For an outbound IP exception filter, the Source IP parameter is set to the IP address of the active NSP host server. The Destination IP is set to the IP address of the 7705 SAR-Hm to be discovered.
Delete the failed sites from the cellular domain:
-
Choose Manage→Cellular Domains from the NFM-P main menu. The Cellular Domain Manager form opens.
-
Click Search and choose the cellular domain that initiated the failed ADP operation. The Cellular Domain [Edit] form opens.
-
Click on the Sites tab.
-
Choose a site from the list and click Delete.
-
Repeat for all sites in the domain for which ADP failed.
-
If the NE is already in a managed state, delete it from the NFM-P discovery manager; see
To delete a device from the managed network.
-
Delete the rule element corresponding to the NE from discovery rules created by ADP for the domain; see
To configure a discovery rule.
-
If the ADP System IP Address parameter is set to Verify, reload the XML file to the cellular domain.
|
5 |
Perform the following on the NE. See the NE documentation for more information.
-
Establish an SSHv2 session to the NE from either a terminal window or the NFM-P.
-
Restore the BOF file to factory default.
-
Delete the existing 7705 SAR-Hm config file.
-
Reboot the NE.
|
6 |
Perform the following in the NFM-P:
If ACL IP exception filters were created in
Stage 4
b:
-
Remove the ACL IP exception filter from the gateway interfaces in the NGE domain.
-
Delete both inbound and outbound ACL IP exception filters; see
To configure an ACL IP exception filter policy.
-
Enable ADP; see
To enable and monitor the ADP discovery process. |