Contents

1   Introduction

This document describes how to connect to the Arwa solution through one of the available communications channels, that is, through Remote Support Gateway (RSG) or HTTPS (over Internet).

Note:  

Select either one of the two communication channels, depending on the need and requirements which are outside the scope of this document.

The Arwa connection requires a secure tunnel (such as RSG). Changing the Arwa server address, as described in this procedure, requires a change to the secure tunnel configuration. Updating the tunnel configuration is outside the scope of this document.

1.1   Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.1.1   Documents

Before starting any of the procedures, ensure that the following document is available:

• Data Collection Guideline for MTAS
• Create Backup

1.1.2   Tools

No tools are required.

1.1.3   Conditions

Before starting any of the procedures, ensure that the following conditions are met:

• It is known whether to update the Arwa server address.
• If applicable, the new Arwa server address is known.
• If applicable, the new Arwa Domain Name System (DNS) hostname is known.
• A secure tunnel to Arwa is established.
• The user has root access to the System Controllers (SCs).
• An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.
• The user has proper authority to handle configuration management of the network elements.
• The communication from MTAS virtualized to the Arwa severs are on port 443 and to the YPS and SCC servers. Hence, it is important to ensure that no firewalls are blocking the traffic at network, to either the YPS or SCC servers of the Arwa solution (on port 443).

2   Procedure

Based on the selected communication channel, see Section 2.1 or Section 2.2, then to connect manually to the Arwa server, see Section 2.3.

2.1   Configure RSG Connectivity

To configure the RSG connectivity:

1. Is a secure tunnel to the Arwa server established?

   Yes: Proceed with Step 3.

   No: Proceed with Step 14.

2. Before any Update Arwa Connection activities are performed, create a backup. Refer to Create Backup.
3. Log on to the Managed Element (ME) to access a Linux® shell:

   ssh <user>@<hostname> -p 22

4. Check connectivity with the persistent storage path, for example:

   ls -l `cmwea software-location-get`/lm-apr9010503/SentinelCloudRuntime.properties

5. Is the file SentinelCloudRuntime.properties accessible?

   Yes: Continue with Step 6.

   No: Proceed with Step 14.

6. Verify that the file SentinelCloudRuntime.properties points to the correct Arwa server address:

   grep YPSAddress `cmwea software-location-get`/lm-apr9010503/SentinelCloudRuntime.properties

   The following is an expected output:

   <add key="YPSAddress" value="https://yps.internal.ericsson.com:443/YPServer">

7. Is the address matched?

   Yes: Proceed with Step 9.

   No: Continue with Step 8.

8. Update the Arwa server address:

   sed 's,https://<current_address>/YPServer,https://yps.internal.ericsson.com:443/YPServer,g' -i `cmwea software-location-get`/lm-apr9010503/SentinelCloudRuntime.properties

9. Verify that the file cluster.conf points to the correct Arwa SCC DNS hostname:

   grep "host control" /cluster/etc/cluster.conf | grep scc

   The following is an expected output:

   host control 153.88.11.78 scc.internal.ericsson.com

10. Is the output matched?

    Yes: Continue with Step 11.

    No: Update the cluster.conf with the expected output in Step 9 and continue with Step 11.

11. Check that the Arwa YPC server Fully Qualified Domain Name (FQDN ), yps.internal.ericsson.com, is reachable from the SC. If it is not reachable, update the following line to cluster.conf:

    host control 153.88.11.77 ypc.internal.ericsson.com

12. If any update is done on cluster.conf during Step 9 or Step 11, reboot the cluster:

    cluster reboot –a

13. Is the cluster reboot performed successfully?

    Yes: Proceed with Step 16.

    No: Proceed with Step 15.

14. Perform data collection, refer to Data Collection Guideline for MTAS.
15. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
16. Job is completed.

2.2   Configure HTTPS Connectivity

To configure the HTTPS connectivity:

1. Log on to the ME to access a Linux shell:

   ssh <user>@<hostname> -p 22

2. Before any Update Arwa Connection activities are performed, create a backup. Refer to Create Backup.
3. Check the connectivity with the persistent storage path, for example:

   ls -l `cmwea software-location-get`/lm-apr9010503/SentinelCloudRuntime.properties

4. Is the file SentinelCloudRuntime.properties accessible?

   Yes: Continue with Step 5.

   No: Proceed with Step 13.

5. Verify that the file SentinelCloudRuntime.properties points to the correct Arwa server address:

   grep YPSAddress `cmwea software-location-get`/lm-apr9010503/SentinelCloudRuntime.properties

   The following is an expected output:

   <add key="YPSAddress" value="https://yps.ericsson.net:443/YPServer">

6. Is the output is matched?

   Yes: Proceed with Step 8.

   No: Continue with Step 7.

7. Update the Arwa server address:

   sed 's,https://<current_address>/YPServer,https://yps.ericsson.net:443/YPServer,g' -i `cmwea software-location-get`/lm-apr9010503/SentinelCloudRuntime.properties

8. Verify that file cluster.conf points to the correct Arwa SCC DNS hostname:

   grep "host control" /cluster/etc/cluster.conf | grep scc

   The following is an expected output:

   host control 193.180.14.226 scc.ericsson.net

9. Is the output matched?

   Yes: Continue with Step 10.

   No: Update the cluster.conf with the expected output in Step 8 and continue with Step 10.

10. Check that the Arwa YPC server FQDN, yps.ericsson.net, is reachable from the SC. If the server is not reachable, update the following line to cluster.conf:

    host control 193.180.14.225 yps.ericsson.net

11. If any update is done on cluster.conf during Step 8 or Step 10, reboot the cluster:

    cluster reboot –a

12. Is the cluster reboot performed successfully?

    Yes: Proceed with Step 15.

    No: Proceed with Step 14.

13. Perform data collection, refer to Data Collection Guideline for MTAS.
14. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
15. Job is completed.

2.3   Connect to Arwa Server

To connect to the Arwa server:

1. Log on to the ME to access a Linux shell:

   ssh <user>@<hostname> -p 22

2. Verity that the Arwa server is reachable:

   telnet <arwa_address> 443 [ arwa_address is Arwa YPC server FQDN]

3. Is Arwa reachable?

   Yes: The telnet output is similar to the following:

   Trying <ip_address>...
   Connected to <arwa_address>.
   Escape character is '^]'.

   Continue with Step 4.

   No: The telnet output is the following:

   Trying <ip_address>...
   telnet: connect to address <ip_address>: Connection refused

   Proceed with Step 9.

4. Use the ECLI and navigate to the ArwaConfiguration Managed Object (MO), for example:

   > dn ManagedElement=NODE06ST,SystemFunctions=1,Lm=1,ArwaConfiguration=1

5. Start a manual connection to the Arwa server:

   (ArwaConfiguration=1) > connectToArwa

   The system returns true if the action was successful.

6. Check the result of the manual connection:

   (ArwaConfiguration=1) > show -r reportProgress

   Note:  

   Since this is a long-running operation, it can be necessary to enter the command several times until the final operation result is shown in the progress report.

   
   

   The following is an example output:

   ArwaConfiguration=1 reportProgress actionId=0 actionName="connectToArwa" additionalInfo="" progressInfo="" progressPercentage=100 result=SUCCESS resultInfo="connectToArwa has succeeded." state=FINISHED timeActionCompleted="2015-05-13T14:12:34" timeActionStarted="2015-05-13T14:12:34" timeOfLastStatusUpdate="2015-05-13T14:12:34"

7. Is the result successful?

   Yes: Proceed with Step 10.

   No: Continue with Step 8.

8. Perform data collection, refer to Data Collection Guideline for MTAS.
9. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
10. Job is completed.

Reference List

[1] Fully Qualified Domain Name for HTTPS, yps.ericsson.net
[2] Fully Qualified Domain Name for RSG, yps.internal.ericsson.com