Contents

1   Description

This instruction describes how to configure the connection to Network License Server (NeLS).

Note:  

The NeLS connection requires a secure tunnel (such as SSL). Changing the NeLS 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.

2   Procedure

2.1   Configure Connection to NeLS

Prerequisites

• No documents are required.
• No tools are required.
• The following conditions must apply:
  • It is known whether to update the NeLS server address.
  • If applicable, the new NeLS server address and port is known.
  • An Ericsson Command-Line Interface (ECLI) session in Exec mode is in progress.

Steps

1. Verify that the connection parameters to NeLS point to the correct host address and port:

   >show verbose ManagedElement=NODE06ST,SystemFunctions=1,Lm=1,NeLSConfiguration=1,host

   host=<IP_Address_or_FQDN>

   >show verbose ManagedElement=NODE06ST,SystemFunctions=1,Lm=1,NeLSConfiguration=1,port

   port=<Port_Number>

2. If necessary, update the connection parameters to NeLS:

   >configure

   (config)>ManagedElement=NODE06ST,SystemFunctions=1,Lm=1,NeLSConfiguration=1

   (config)>host=<IP_Address_or_FQDN>

   (config)>port=<Port_Number>

   (config)>commit

   After committing the configuration changes, LM drops the current connection to NeLS, if one is established, and attempts to reconnect using the updated configuration settings.

3. Check connectivity by printing the status of the connection to NeLS:

   show ManagedElement=NODE06ST,SystemFunctions=1,Lm=1,NeLSConfiguration=1,connectionStatus

   The following is an example output:

   connectionStatus=CONNECTED

   connectionStatus=CONNECTED indicates that a connection to NeLS is established.

   It is also possible that NeLS is deployed with Geographical Redundancy. In this case there are two NeLS instances deployed with redundancy, one acting as primary and the other as secondary. To configure NeLS connection, the IP addresses of primary and secondary NeLS instances have to configured in the same order as A or AAAA records in a DNS server that is reachable from LM. The corresponding domain name then has to be configured as NeLS host within LM configuration. LM shall attempt first connecting to primary NeLS and if the connection fails, it then attempts connection to the secondary NeLS. SRV type records are not supported for LM to NELS connection.

   Note:  

   If the output shows connectionStatus=NOT_CONNECTED, wait a few minutes and try again.

   
   
4. If the connection is still not established, use ping and traceroute from a Linux® shell to attempt to reach the NeLS host address. Contact the network administrator to investigate any network problems.