Contents

1   System Administration Overview

The SAPC provides several interfaces and tools for system administrators, for the following purposes:

• Configuration and provisioning
• Performance Management
• Fault Management
• Logging Management

These different interfaces, tools, and procedures are described in the following sections.

2   Administration Interfaces and Tools

2.1   Interfaces

This section describes all the different operation and maintenance interfaces provided by the SAPC to the operator to access and configure the node. An overall view of these interfaces is shown in Figure 1 and they are depicted in the following chapters.

2.1.1   REST API

The SAPC provides a REST API for provisioning data, refer to Provisioning REST API.

Provisioning data persist in an internal database.

2.1.2   NETCONF

The Network Configuration Protocol (NETCONF), built on top of SSH, is a machine-machine interface that provides mechanisms to create, modify, and delete the SAPC configuration data.

The NETCONF interface is provided by Common Operation and Maintenance (COM).

For more information about NETCONF, refer to Ericsson NETCONF Interface.

2.1.3   SSH

Secure Shell (SSH) is a network protocol that allows data to be exchanged by using a secure channel between two network devices.

Note:  

Access by SSH to the SAPC is only recommended when it is indicated in this document or any other that this one is referring to.

2.1.4   SFTP

The Secure File Transfer Protocol, built on top of SSH, is supported to securely transfer or access files from the SAPC to external systems.

1. Connect to the SAPC by SFTP, to the <OAM VIP>, with user=sapcadmin and port=115.
2. To know the path to the needed file, follow the procedure explained in List File Groups and File Information in Logical File System

   For example, for Performance Management files: FileGroup=PerformanceManagementReportFiles.

3. Then, follow the procedure explained in Fetch File in Logical File System

Note:  

The SAPC also provides SFTP access in port 22. Then the remote working directory is /home/<user_sftp>.

2.1.5   SNMP

Simple Network Management Protocol (SNMP) is based on the agent and manager communication protocol over User Datagram Protocol (UDP). It is used a standard protocol to interchange administrative information between Network Elements.

2.2   Tools

This section describes the tools to be used through the different interfaces for operation and maintenance purposes.

2.2.1   COM CLI

COM CLI (also known as ECLI) is a terminal-based command line interface which allows the operator to monitor and manage (for example check active alarms, manage the SAPC configuration data) the Managed Element (ME). It enables interaction with the Management Information Base (MIB) through common, generic-purpose commands.

To access the COM CLI for administration node operations, the system administrator must use:

ssh sapcadmin@<OAM VIP> -p <COM_port> -t -s cli

where <OAM VIP> is the SAPC VIP OAM and <COM_port> is the COM port, normally 830.

ssh sapcadmin@10.42.118.235 -p 830 -t -s cli

As an example of use of this tool is:

>show ManagedElement=1
ManagedElement=1
SystemFunctions=1
Transport=1
JavaCaf=1
PolicyControlFunction=1

For further information about this interface, refer to Ericsson Command-Line Interface.

2.2.2   SSH

SSH access to the system must be used for operation and maintenance purposes specified along this document or in any other document that this refers to.

To access the system, execute the following command:

ssh sapcadmin@<OAM VIP>

3   Configuration and Provisioning Overview

The following sections introduce the main concepts related to configure and provision data in the SAPC.

Guidelines for configuring the SAPC in each specific scenario (function) can be found in the SAPC Configuration Guides documents.

Next figure, shows the main parts related to configuration and provisioning in the SAPC.

Configuration Management is the process where a configuration entity or in general a network management entity, issues orders to provide the parameters and information necessary for the correct operation of a network element, in terms of both software and hardware.

Provisioning function is the supplying of all the data necessary for the use of that a user or a set of users make of a service. It comprises both service and user-related data. For details of the SAPC provisioning related data, refer to Provisioning REST API.

3.1   Configuration through COM

The SAPC uses COM to configure some of the application data, offering a Managed Object Model (MOM).

There are two ways of accessing to the MOM (Managed Object Models):

1. NETCONF interface, refer to Ericsson NETCONF Interface.

   An example of NETCONF command (executed from an external machine) to configure an object included in the file "filename.xml" is the following:

   netconf-console -u sapcadmin -p <password> --proto=ssh --port=830 --host=<OAM VIP> -s raw --rpc=RPC filename.xml

   Note:  

   netconf-console is just an example of NETCONF client. The SAPC does not provide any NETCONF client. It is under the operator responsibility, to use any NETCONF client.

   
   
2. Or COM CLI, refer to Ericsson Command-Line Interface.

   To read the attribute values of an object in COM, refer to Display MO instances chapter in Ericsson Command-Line Interface.

For details of the SAPC data that can be configured using COM, refer to Managed Object Model (MOM).

4   Performance Measures Management

For information referring to the Performance Measurement Management, refer to Measurements.

5   Fault Management

Perform daily a verification of the active alarms and notifications. There are two ways to do so:

• Through any external system configured to collect SNMP traps.
• Through the COM CLI tool provided inside the SAPC.

To verify the alarms and notifications through the COM CLI tool, follow the steps:

1. Access to the COM CLI according to the Section 2.2.1
2. Execute the following command (more information in Ericsson Command-Line Interface):

   show-table ManagedElement=1,SystemFunctions=1,Fm=1 -m FmAlarm -p fmAlarmId, specificProblem

   ==================================================== 
   | fmAlarmId | specificProblem                      |
   ====================================================
   | 139       | Policy Control, Number of Gx Session | 
   |           | Rejections Reached                   |
   ====================================================

For information about procedures related to alarms and notifications, see the Fault Management folder in the library.

6   Logging Management

For information about the SAPC logging management, refer to Logging Events.

7   Security Management

The SAPC has the following Administrators, created at installation time:

• sapcadmin: Administrator to perform all operation and maintenance tasks, including create, read, and update the SAPC configuration data.
• sapcprov: administrator provided to perform REST provisioning operations.

8   Startup and Shutdown

This chapter describes the start and stop procedures. Before performing any of these actions, it is recommended to perform a backup.

8.1   SAPC Restart

To restart the SAPC, execute the following steps:

1. Access to the SAPC according to Section 2.2.2
2. sapcadmin@SC-X>sudo sapcApplication -a restart
3. Check the SAPC status:

   sapcadmin@SC-X>sudo sapcApplication -a status

8.2   SAPC Stop

To stop the SAPC, execute the following steps:

1. Access to the SAPC according to Section 2.2.2
2. sapcadmin@SC-X>sudo sapcApplication -a stop
3. Check the SAPC status:

   sapcadmin@SC-X>sudo sapcApplication -a status

8.3   SAPC Start

To start the SAPC, execute the following steps:

The SAPC can be started with the following steps.

1. Access to the SAPC according to Section 2.2.2
2. sapcadmin@SC-X>sudo sapcApplication -a start
3. Check the SAPC status:

   sapcadmin@SC-X>sudo sapcApplication -a status

8.4   Processor Restart

A processor on the SAPC can be individually restarted.

1. Access to the SAPC according to Section 2.2.2
2. Perform the restart of the processor in the SAPC.

   sapcadmin@SC-X>sudo cmw-node-reboot <processor>

3. Wait until the processor is back.
4. Check the SAPC status:

   sapcadmin@SC-X>sudo sapcApplication -a status

9   Directory Structure

The following table shows the directories containing configuration and storage files:

Table 1    Directory Structure

Directory Path	Comment
/cluster/storage/system/config/sapc	Directory containing the configuration files. It is in the SC-1 and SC-2.

Reference List

Ericsson Documents
[1] Logging Events.
[2] Measurements.