3.2 Feature Deactivation Execution Overview

The procedures shown in the following table are executed inside a maintenance window. Deactivation procedure times are only estimates as the reason to execute a deactivation has a direct impact on any additional deactivation preparation that must be done. Times may vary due to differences in database size, network configuration and loading, user experience, and user preparation.

Table 3-2 Feature Deactivation Overview

Procedure Elapsed Time (Hours:Minutes) Activity Deactivation Procedures Impact
  This Step Cum.    
Deactivation Setup 0:30 0:30
  • The reason to deactivate has a direct impact on any additional back-out preparation that must be done. Since not all possible reasons can be predicted ahead of time, only estimates are given here. Execution time will vary.
None
Pre-Feature Deactivation Health Check 0:20 0:50
  • Log out of active NOAM/SOAM GUI.
  • SSH into active NOAM.
  • Login as admusr
  • Change directory to /usr/TKLC/dsr/prod/maint/loaders/
  • Execute the feature deactivation script.
  • Log into NOAM or SOAM GUI.
  • Verify the FABR folder.
  • Restart each active DA-MP server.
  • Log into NOAM GUI
  • Verify Maintenance screen.
RBAR is deactivated