Activating a DCA Application

This procedure is used to activate a DCA application.

Log out of any active NOAM GUI sessions.
Use an SSH client to connect to the server as admusr.
# ssh <active NOAM XMI IP Address>
Change to the feature activation directory.
# cd /usr/TKLC/dsr/prod/maint/loaders/

Execute the feature activation script.

 #
				./featureActivateDeactivate

Choose Activate and DCA Application.
Enter a long name for the new application when prompted.

Note:
The DCA application long name consists of a combination of letters, numbers, and spaces. It can't begin with a space and has a maximum of 32 characters.
Enter a short name for the application when prompted.

Note:
The DCA application short name consists of a combination of letters and numbers. It has a maximum of 6 characters.

Verify that the screen output is similar to:

[admusr@HPC07-NO1 loaders]$ ./featureActivateDeactivate
Tue Feb  2 17:52:59 EST 2016::Starting featureActivateDeactivate main...
Start the Automation script , To run the Feature Activation/DeActivation on Active NO.

You want to Activate or Deactivate the Feature :
1.Activate
2.Deactivate

Enter your choice : 1

List of Feature you can Activate :
1.RBAR
2.FABR
3.Mediation
4.LoadGen
5.GLA
6.MAP Interworking
7.DTLS
8.Dca Framework
9.Dca Application

Enter the choice : 9

============= Start of Log Data in file /var/TKLC/log/DcaActivationTopLevel.log ===============


=====================================S-T-A-R-T===================================

Log file location: /var/TKLC/log/DcaActivationTopLevel.log

Note:-
In case of any failure please execute /usr/TKLC/dsr/prod/maint/loaders/deactivate/load.DcaDeactivationTopLevel script to revert the changes.

================================================================================
Execution of Activation Process Starts
================================================================================
Dca framework is activated on the setup..Continuing
Following Dca apps are activated on the system:
First Dca App
Enter the long name for the Dca application:Second DCA App
Entered dca name Second DCA App consist of valid characters
Entered Name is Second DCA App
next available dal id is 129
Enter the short name for the Dca application:sda
length of shortName is 3.continuing..
Entered dca name sda consist of valid characters
Entered Name is sda
==============================================
Verify that Dca Application is in the DalId table
==============================================
dalId=129
birthTime=02/02/2016 17:53:22.000
name=Second DCA App
shortName=sda
activated=No
=================================
==============================================
Verify that Dca Application is in the DcaDalId table
==============================================
dalId=129
name=Second DCA App
shortName=sda
=================================
Executing /usr/TKLC/dsr/prod/maint/loaders/activate/load.DcaActivateAscoped script on HPC07-NO1

============= Start of Log Data in file /var/TKLC/log/DcaActivateAscoped.log ===============

Server Name  : HPC07-NO1
Server Role  : NETWORK_OAMP
Node Id      : HPC07-NO1
HA State     : Active
Cluster Role : Primary
=========================================================
Add Dca application entry to the DsrApplication table.
=========================================================
==============================================
Verify that Dca Application is in the table
==============================================
id=129
name=sda
unavailableAction=ContinueRouting
avpInsertion=Yes
shutdownMode=Graceful
shutdownTimer=5
resultCode=3002
vendorId=0
errorString=Dca Application Unavailable Or Degraded
resExhResultCode=3004
resExhVendorId=0
resExhErrorString=Dca Resource Exhausted
routeListId=-1
realm=
fqdn=
mcl=0
=================================
================================
Add Dca Application KPI group
================================
=========================================
Add Dca Application Measurement groups
=========================================
===================================================
Add Permission Group headers for Dca Application
===================================================
===================================================
Add network configuration parameters for Dca
===================================================

======================================E-N-D======================================

Execution status of activation script on HPC07-NO1: PASSED
Please check /var/TKLC/log/DcaActivateAscoped.log for more details.

================================================================================
Starting Activation on StandBy NOAMP Server if it exists in the topology.

HPC07-NO1 is Active and Primary NOAMP Server. So, proceeding with next NOAMP Server.
======= Activation done on all Network OAMP Servers  =======

======= Starting Activation on System OAM servers =======

================================================================================
HPC07-SO1 is Active. So, proceeding with Activation.
FIPS integrity verification test failed.
Executing /usr/TKLC/dsr/prod/maint/loaders/activate/load.DcaActivateBscoped script on HPC07-SO1
FIPS integrity verification test failed.

============= Start of Log Data in file /var/TKLC/log/DcaActivateBscoped.log ===============

Server Name : HPC07-SO1
Server Role: SYSTEM_OAM
Node Id    : HPC07-SO1
HA State   : Active
=======================================================================
Add Dca application to DsrApplication. If already present then skip.
=======================================================================
==============================================
Verify that Dca application is in the table
==============================================
id=129
name=sda
unavailableAction=ContinueRouting
avpInsertion=Yes
shutdownMode=Graceful
shutdownTimer=5
resultCode=3002
vendorId=0
errorString=
resExhResultCode=3004
resExhVendorId=0
resExhErrorString=Dca Resource Exhausted
routeListId=-1
realm=
fqdn=
mcl=0
=================================
==========================================================
Add Permission Group headers for Dca app on SOAM server
==========================================================
===================================================
Add system configuration parameters for Dca
===================================================
===============================================END==============================

Execution status of activation script on HPC07-SO1: PASSED
Please check /var/TKLC/log/DcaActivateBscoped.log.HPC07-SO1 for more details.
FIPS integrity verification test failed.
FIPS integrity verification test failed.
================================================================================
  === changed 1 records ===
==============================================
Verify that activated field is udpated for Dca Application in the DalId table
==============================================
dalId=129
birthTime=02/02/2016 17:53:22.000
name=Second DCA App
shortName=sda
activated=Yes
=================================
================================================================================
Execution of Dca Applicaion Activation Script complete.
================================================================================
======================================E-N-D======================================

Restart the DSR MP from Main Menu > Status & Manage > Server.

Log into an Active NOAM and SOAM GUI.
Verify that DCA Application folder appears under the DCA Framework menu item on an NOAM and SOAM.
1. Verify that the folder for the new DCA application appears under DCA Framework on an NOAM. Under the application folder has General Options, Trial MP assignment, and Application Control sub-options.
2. Verify that the folder for the new DCA application appears under DCA Framework on an SOAM. Under the application folder has General Options, Trial MP assignment, and Application Controll, and System Options sub-options.
Log out of the NOAM login shells using the # exit command and close the SSH connections.