Contents

1   Description

This instruction describes how to change the administrative state of ECLI or NETCONF over SSH.

2   Procedure

2.1   Change Administrative State of ECLI over SSH

Prerequisites

• No documents are required.
• No tools are required.
• The following conditions must apply:
  • The user has the System Security Administrator role.
  • If locking ECLI over SSH, NETCONF over SSH must be unlocked, or the other way around.
  • An Ericsson Command-Line Interface (ECLI) in exec mode is in progress.

Before locking the administrative state of ECLI over SSH, make sure that the administrative state of NETCONF over SSH is UNLOCKED. Having both interfaces set to LOCKED disables O&M access to the ME. Refer to product-specific troubleshooting instructions to resolve such a scenario.

Steps

1. Navigate to the CliSsh Managed Object (MO), for example:

   >dn ManagedElement=1,SystemFunctions=1,SysM=1,CliSsh=1

2. Enter Config mode:

   (CliSsh=1)>configure

3. Set the administrativeState attribute, for example:

   (config-CliSsh=1)>administrativeState=UNLOCKED

   Note:  

   To lock the administrative state, set the attribute value to LOCKED.

   
   
4. Commit the settings:

   (config-CliSsh=1)>commit

5. Verify the settings:

   (CliSsh=1)>show

   The following is an example output:

   CliSsh=1 [...] administrativeState=UNLOCKED

2.2   Change Administrative State of NETCONF over SSH

Prerequisites

• No documents are required.
• No tools are required.
• The following conditions must apply:
  • The user has the System Security Administrator role.
  • If locking ECLI over SSH, NETCONF over SSH must be unlocked, or the other way around.
  • An Ericsson Command-Line Interface (ECLI) in exec mode is in progress.

Attention!

Risk of system malfunction or traffic disturbance.

Before locking the administrative state of NETCONF over SSH, make sure that the administrative state of ECLI over SSH is UNLOCKED. Having both interfaces set to LOCKED disables O&M access to the ME. Refer to product-specific troubleshooting instructions to resolve such a scenario.

Steps

1. Navigate to the NetconfSsh Managed Object (MO), for example:

   >dn ManagedElement=1,SystemFunctions=1,SysM=1,NetconfSsh=1

2. Enter Config mode:

   (NetconfSsh=1)>configure

3. Set the administrativeState attribute, for example:

   (config-NetconfSsh=1)>administrativeState=UNLOCKED

   Note:  

   To lock the administrative state, set the attribute value to LOCKED.

   
   
4. Commit the settings:

   (config-NetconfSsh=1)>commit

5. Verify the settings:

   (NetconfSsh=1)>show

   The following is an example output:

   NetconfSsh=1 [...] administrativeState=UNLOCKED