3 Feature Deactivation Overview

3.1 Pre-Feature Deactivation Overview

The procedures shown in the following table are run inside a maintenance window. Deactivation procedure times are only estimates as the reason to run 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-1 Pre-Feature Deactivation Overview

Procedure Elapsed Time (Hours:Minutes) Elapsed Time (Hours:Minutes) Tasks Impact
  This Step Cumulative    
Perform Health Check (Pre-Feature Deactivation) 0:05 0:05
  • Verify DSR release.
  • Verify proper FABR feature state.
  • Verify server status.
  • Log current alarms.
None

3.2 Feature Deactivation Overview

The procedures shown in the following table are run inside a maintenance window. Deactivation procedure times are only estimates as the reason to run 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) Tasks Impact
  This Step Cumulative    
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
Feature Deactivation 0:20 0:50
  • Log out of active. NOAM/SOAM GUI.
  • SSH into active NOAM.
  • Log in as admusr.
  • Change directory to /usr/TKLC/dsr/prod/maint/loaders/
  • Run the feature deactivation script.
  • Log into NOAM or SOAM GUI.
  • Verify the FABR folder.
  • Log into NOAM GUI.
  • Verify Maintenance screen.
FABR is deactivated

3.3 Post-Feature Deactivation Overview

The procedures shown in the following table are run inside a maintenance window. Deactivation procedure times are only estimates as the reason to run 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-3 Post-Feature Deactivation Overview

Procedure Elapsed Time (Hours:Minutes) Tasks Impact
  This Step Cumulative    
Perform Health Check (Post-Feature Deactivation) 0:05 0:05
  • Verify server status.
  • Log all current alarms.
None