As the application user, shut down Cisco InTracer.

Verify that the JAVA_HOME environment variable points to Java 1.7, which the DMIntegrator.sh script requires.

Verify that the /usr/bin/scp secure copy tool is present on the Cisco InTracer server.

Under the Cisco InTracer home folder, create a prime_integrator folder (if it does not already exist) and copy the following files to it:

Verify that permissions are correct.

Run the DMIntegrator.sh script. (For usage details, see DMIntegrator.sh Script Usage.)

As the primeusr user, log in to the Prime Central integration layer and restart it:

1. Enter the following command, which lists all integration layer instances (and their profiles) that are running:

   itgctl list

2. Note down the ID of the integration layer instance with the "PC-IL-CORE" profile.

3. Stop the PC-IL-CORE profile instance:

   itgctl stop ID

4. Restart the integration layer:

   itgctl start ID

Start Cisco InTracer.

After Cisco InTracer is integrated with Prime Central, use the Prime Central portal to create new users, even if they already existed in standalone mode.

As the application user, shut down Prime Network:

Enter:

Verify that the JAVA_HOME environment variable points to Java 1.7 , or 1.8 from Prime Network 4.3 onwards which the DMIntegrator.sh script requires:

Verify that the correct value is configured for the HOSTNAME object in the DMIntegrator.prop file.

1. Enter the following command:

   hostname – –fqdn

2. On the primary Prime Network server, navigate to the $PRIME_NETWORK_HOME/prime_integrator directory.

3. Open the DMIntegrator.prop file and confirm that the value configured for the HOSTNAME object is the same as the gateway listed after running the hostname –fqdn command.

Run the DMIntegrator.sh script.

Start Prime Network:

Restart the Prime Central integration layer so that it recognizes the recently added Prime Network server:

Now that Prime Network is integrated with Prime Central, you must also integrate the Prime Network integration layer. Continue to Integrating the Prime Network Integration Layer with Prime Central.

After Prime Network is integrated with Prime Central, use the Prime Central portal to create new users, even if they already existed in standalone mode (or provide PN scope to the users).

As the Prime Network user, log in to the Prime Network gateway:

Disable the Prime Network integration layer health checker by entering the following command on the Prime Network gateway server:

Stop the Prime Network integration layer:

Change directories to the $PRIMEHOME/integration directory:

Verify that the correct value is configured for the HOSTNAME object in the ILIntegrator.prop file.

1. Enter the following command:

   hostname ––fqdn

2. On the primary Prime Network server, navigate to the $PRIMEHOME/pnil directory.

3. Open the ILIntegrator.prop file and confirm that the value configured for the HOSTNAME object is the same as the gateway listed after running the hostname ––fqdn command.

Run the DMIntegrator script.

Reload the user profile:

Enable the Prime Network integration layer health checker by entering the following command on the Prime Network gateway server:

Start the Prime Network integration layer:

Restart Prime Central integration layer in order for the new Prime Network server to be recognized by the application:

As the application user, shut down Prime Network.

Verify that the JAVA_HOME environment variable points to Java 1.7 , or 1.8 from Prime Network 4.3 onwards, which the DMIntegrator.sh script requires.

Verify that the /usr/bin/scp secure copy tool is present on the Prime Network server.

Under the Prime Network home folder, create a prime_integrator folder (if it does not already exist) and copy the following files to it:

Verify that permissions are correct.

In the DMIntegrator.prop file, change the HOSTNAME value to ana-cluster-ana.

Add the hostname ana-cluster-ana to the /etc/hosts file on the Prime Central machine.

On the client workstation, repeat the preceding step. If you are using a Windows workstation, use the C:\Windows\system32\drivers\etc\hosts file.

Run the DMIntegrator.sh script.

As the Prime Network user, run the jars script:

1. Enter:

   cd ~/prime_integrator/PN_PC_Integration/

   perl runPrimeCentralUpgrade.pl

2. When prompted, enter the Prime Central IP address, Prime Central root username and password, and the system's Prime Central username (usually primeusr).

If you are reintegrating the same Prime Network instance with a different COM-URI, you must restart the Prime Central portal. (The COM-URI is the Prime Network identifier and can be found in the Prime Central portal > Suite Monitoring portlet.) To do so, log in to the Prime Central portal as the primeusr user and enter:

Start Prime Network.

After Prime Network is integrated with Prime Central, use the Prime Central portal to create new users, even if they already existed in standalone mode.

As the application user, shut down Prime Optical:

Under the application home folder, change directories to the /bin directory:

Run the CPOIntegrator.sh script:

Start Prime Optical:

As the root user, log in to the Prime Performance Manager gateway server and navigate to the Prime-Performance-Manager-gateway-installation-directory /bin directory.

Enter:

Enter the appropriate responses at the prompts:

Restart Prime Performance Manager for the changes to take effect.

As the primeusr user, log in to the Prime Central integration layer and restart it:

If you are reintegrating Prime Performance Manager after a previous integration, you must unregister it from Prime Central before you reintegrate it. See Unregistering Prime Performance Manager.

If remote units are connected to the gateway, complete the below steps to enable SSL on remote units:

1. Log into the remote unit.

2. Enable SSL on the unit:

   /opt/CSCOppm-unit/bin/ppm ssl enable

   Prime Performance Manager:

   • Stops the unit.

   • Generates RSA private key.

3. When prompted, enter the SSL distinguishing information for the unit:

   Country Name (2 letter code) []:
   State or Province Name (full name) []:
   Locality Name (eg, city) []:
   Organization Name (eg, company) []:
   Organizational Unit Name (eg, section) []:
   Common Name (your hostname) []:
   Email Address []:
   Certificate Validity (number of days)? [min: 30, default: 365]

   Prime Performance Manager generates the server.key, server.crt, and server.csr on the unit /opt/CSCOppm-unit/etc/ssl directory :

4. Import the unit certificate to the gateway:

   1. Copy the/opt/CSCOppm-unit/etc/ssl/server.crt to a temporary location on the gateway, for example,/tmp/server.crt .

   2. Enter the following command to import the unit certificate:

   /opt/CSCOppm-gw/bin/ppm certtool import myhostname-unit -file filename

   Where alias is a string that is an alias for the certificate file and filename is the full path name for the certificate file, for example,/tmp/server.crt. Each imported certificate must have a unique alias when imported.

5. Import the gateway certificate to the unit:

   1. Copy the/opt/CSCOppm-gw/etc/ssl/server.crt to a temporary location on the unit machine, for example,/tmp/server.crt .

   2. Import the gateway certificate:

   /opt/CSCOppm-unit/bin/ppm certtool import myhostname-gateway -file filename

   Where alias is a string that is an alias for the certificate file and filename is the full path name for the certificate file, for example,/tmp/server.crt .

   Note	The gateway imports the certificate file for each unit that connects to it. Each unit then imports the gateway certificate file for the gateway that it connects to.

6. Restart the gateway:

   /opt/CSCOppm-gw/bin/ppm restart

7. Restart the remote unit:

   /opt/CSCOppm-unit/bin/ppm restart unit

After Prime Performance Manager is integrated with Prime Central, use the Prime Central portal to create new users. (Any users that existed before the integration are removed during the integration.)

If you install a Prime Network instance after Prime Performance Manager is integrated with Prime Central, enter the following commands to integrate Prime Performance Manager with Prime Network:

If Prime Performance Manager is configured to send alarms directly to the Prime Central Fault Management server, verify that an upstream OSS host is configured correctly in the System Event Editor of Prime Performance Manager.

If you install the Fault Management component after Prime Performance Manager is integrated with Prime Central, enter the following command and select Fault Management as the trap destination to integrate it with Prime Performance Manager:

# ./ppm setpctrapdestination

Trap destinations registered with Prime Central:

1. Prime Central Fault Management (hostname)
2. Prime Network (hostname-1) 
3. Prime Network (hostname-2) 
4. Prime Network (hostname-3)

Enter trap destination: [1, 2, 3, 4] 1, 2, 3

As the application user, shut down Prime Provisioning.

Set the Prime Provisioning environment:

Run the DMIntegrator.sh script. (For usage details, see DMIntegrator.sh Script Usage.)

As the primeusr user, log in to the Prime Central integration layer and restart it:

1. Enter the following command, which lists all integration layer instances (and their profiles) that are running:

   itgctl list

2. Note down the ID of the integration layer instance with the "PC-IL-CORE" profile.

3. Stop the PC-IL-CORE profile instance:

   itgctl stop ID

4. Restart the integration layer:

   itgctl start ID

If you are reintegrating Prime Provisioning with a different COM-URI, you must restart the Prime Central portal. (The COM-URI is the Prime Provisioning identifier and can be found in the Prime Central portal > Suite Monitoring portlet.) To do so, log in to the Prime Central portal as the primeusr user and enter:

Start Prime Provisioning.

After Prime Provisioning is integrated with Prime Central, use the Prime Central portal to create new users, even if they already existed in standalone mode.

Log in to the Agora-NG server as the user agorang.

Enter the following commands:

From the Fault Source Management portlet, click Add to add the Fault Source details.

Enter the Fault Source Type from the drop-down as CAR and specify the Fault Source details in the appropriate fields.

Click OK.

From the Fault Source Management portlet, click Add to add the Fault Source details.

Enter the Fault Source Type from the drop-down as CNR and specify the Fault Source details in the appropriate fields.

Click OK.

From the Fault Source Management portlet, click Add to add the Fault Source details.

Enter the Fault Source Type from the drop-down as SpiderCloud and specify the Fault Source details in the appropriate fields.

Click OK.