APG43L 3.

2 Network Impact Report

NETWORK IMPACT REPORT

3/10948-APZ 212 33/62 Uen E

Copyright

© Ericsson AB 2016. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of
this document.

3/10948-APZ 212 33/62 Uen E | 2017-02-03

 Contents

Contents

1 Introduction 1
1.1 Purpose 1
1.2 General information 1
1.3 Node Configurations 2
1.4 Revision Information 3

2 General Impact 3
2.1 Capacity and Performance of APG43L 3.2 3
2.2 Hardware 8
2.3 File System 8
2.4 Implementation 8
2.5 Interface 9
2.6 Operation 11
2.7 Functional Changes 11

3 Upgrade 14

4 Additional Information 15
4.1 Operation 15
4.2 Documentation 17

Glossary 25

Reference List 27

3/10948-APZ 212 33/62 Uen E | 2017-02-03

APG43L 3.2 Network Impact Report

3/10948-APZ 212 33/62 Uen E | 2017-02-03

 Introduction

1 Introduction

The Network Impact Report describes how the current release of APG43L 3.2
with new and changed features affects the previous release of APG43L and the
operator's overall network, including all affected products and functions.

1.1 Purpose
The purpose of this document is to provide sufficient information at an early stage
to Ericsson system operators in order to help them to plan the introduction in their
networks of new APG43L 3.2 Software (SW) package.

1.2 General information

This Network Impact Report describes the software changes introduced in
APG43L 3.2 release with respect to APG43L 3.0. As no network level impacts
have been released in APG43L 3.1, no Network Impact Report document has
been created for that release.

For information about the software changes introduced in APG43L 3.0, refer to
APG43L 3.0 Network Impact Report, Reference [1].

APG43L 3.2 supports one or two APGs in Single-CP and Multi-CP System.

APG43L SW is supported by Operation Support System (OSS-RC) 15B and

subsequent releases.

APG43L 3.2 supports interworking with LI-IMS 14B and subsequent releases.

Refer to specific application (BSC/HLR/MSC/Wireline) Network Impact Report

documents to check actual compatibility between APG43L 3.2 and supported
OSS-RC versions.

APG43L 3.2 is deployed through:

— New installation of BSC/HLR/MSC nodes;

— Software Upgrade of BSC/HLR/MSC/Wireline nodes based on APG43L 2.2,

3.0 or 3.1;

For supporting customers deploying APG43L 3.2 in the network, User Instructions
Network Introduction of APG43L 3.2, Reference [5] should be used.

With reference to HW configurations, in the following sections APG43 will be used

as common term for APG43 based on APUB (AP processor board based on single
core processor), APG43/2 will be used for APG43 based on APUB2 (AP processor

3/10948-APZ 212 33/62 Uen E | 2017-02-03 1

 APG43L 3.2 Network Impact Report

board based on quad-core processor), while APG43/3 will identify APG43 based
on GEP5 (AP processor board based on 10-core processor).

1.2.1 Software Baseline

APG43L 2.2, 3.0 and 3.1 are the software baselines to upgrade towards APG43L
3.2 release.

Note: Customers having APG43L 2.1, or lower releases, must first upgrade to
either APG43L 2.2, 3.0 or 3.1 before upgrading to 3.2. Customers having APG43
Windows must first upgrade to APG43L 3.0, before upgrading to APG43L 3.2.

1.3 Node Configurations

APG43L 3.2 can be deployed in the following configurations, according to the
installation type.

APG Hardware Swap:

— BSC node based on APZ 212 60F with APG43 (EGEM) upgraded to APZ 212
60F with APG43/3 (EGEM);

— BSC node based on APZ 212 60F with APG43/2 (EGEM) upgraded to APZ
212 60F with APG43/3 (EGEM);

— MSC-S and HLR-FE nodes based on APZ 212 60 with APG43 (EGEM)
upgraded to APZ 212 60 with APG43/3 (EGEM);

— MSC-S and HLR-FE nodes based on APZ 212 60 with APG43/2 (EGEM)
upgraded to APZ 212 60 with APG43/3 (EGEM);

— HLR-FE Blade node based on APZ 214 03 with APG43/2 (EGEM2 IS)
upgraded to APZ 214 03 with APG43/3 (EGEM2 IS).

New installation:

— BSC on APZ 212 60F with APG43/3 (EGEM2);

— MSC-S on APZ 212 60F with APG43/3 (EGEM2 BSP);

— MSC-S BC on APZ 214 10 with APG43/3 (EGEM2 BSP);

— HLR-FE Blade on APZ 214 10 with APG43/3 (EGEM2 BSP).

2 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 General Impact

1.4 Revision Information

Table 1 Revision Information
Rev Date Description
A 2016-09-16 New version of document for APG43L 3.2 final release.
B 2016-09-30 Minor updates.
C 2016-10-12 Doc. numbers updated in Documentation section.
D 2016-11-03 Additional performance data plus minor updates.
E 2017-02-03 Removed not relevant information.

2 General Impact

2.1 Capacity and Performance of APG43L 3.2

Figures reported in this chapter are sourced from lab tests. Site conditions, for
example the processor load, memory usage, network load, concurrent tasks, AXE
node application and version can make figures different from what is stated below.

2.1.1 Statistics and Traffic Measurements Capability

Statistics and Traffic Measurement (STS) counters in different configurations are
reported in the tables below.

The first table below reports the counter measurements in APG43L 3.2 for
APG43/3 and APG43/2 Single CP System. A configuration similar to BSC
application is reported:

Table 2 STS Counters in APG43/3 and APG43/2 Single CP System

Input parameters APG43L Measured Data
BRP period (min) Accumulation STS counters STS counters
time (sec) APG43/3 with APG43/2 with
APZ 212 60F APZ 212 60
(M=10^6) (M=10^6)
15 100 10M 10M

The table below reports the counter measurements in APG43L 3.2 for APG43/3
and APG43/2 Multi-CP System. A configuration similar to MSC application is
reported:

3/10948-APZ 212 33/62 Uen E | 2017-02-03 3

 APG43L 3.2 Network Impact Report

Table 3 STS Counters in APG43/3 and APG43/2 Multi-CP System

Input parameters APG43L Measured Data
BRP period Accumulation STS counters STS counters
(min) Time (sec) APG43/3 with APZ APG43/2 with APZ
214 10 (M=10^6) 214 03 (M=10^6)
15 100 4M 4M

2.1.2 MML Command Throughput

The maximum numbers of MML commands/second that can be sent in Single-CP
System (for APG43/3 and APG43/2) in an MML session opened towards the
TCP port number 5000 or 52000 are shown in table below. The table shows the
sustainable throughput when commands are simultaneously sent using 1, 4 and
40 opened MML sessions:

Table 4 MML Throughput in APG43/3 and APG43/2 Single CP System

APG43L Measured Data
Number of APG43/3 with APZ 212 APG43/2 with APZ 212
sessions 60F (cmd/s) 60 (cmd/s)
1 230 240
4 800 800
40 5500 1900

The maximum numbers of MML commands/second that can be sent in Multi-CP

System for APG43/3 and APG43/2 in an MML session opened towards the TCP
port number 5000 or 52000 are shown in the table below. The table shows the
sustainable throughput when commands are simultaneously sent using 1, 4 and
40 opened MML sessions:

Table 5 MML Throughput in APG43/3 and APG43/2 Multi-CP System

APG43L Measured Data
Number of APG43/3 with APZ214 APG43/2 with APZ214
sessions 10 (cmd/s) 03 (cmd/s)
1 220 160
4 850 510
40 4300 1450

Note: For all tables above the data depends heavily on the measurement
environment. The reported measurements indicate the possible maximum
obtainable from the APG. Elements in the total environment outside the IO system,
like Telnet clients, AXE application nodes and connected network elements may

4 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 General Impact

create bottle-necks that result in lower values; similarly lower values may be
expected depending on specific MML commands.

2.1.3 Backup and Restore Time

The table below reports the APG43L 3.2 backup and restore times in APG43/3:

Table 6 AP Backup and Restore Time in APG43/3

Input parame APG43L Measured Data
ters
Restore size (MB) AP Backup time APG43/3 AP Restore time APG43/3
(min) (min)
~350 ~1 ~5

The table below reports the APG43L 3.2 backup and restore times in APG43/2:

Table 7 AP Backup and Restore Time in APG43/2

Input parame APG43L Measured Data
ters
Restore size (MB) AP Backup time APG43/2 AP Restore time APG43/2
(min) (min)
~350 ~2 ~5-6

Note: AP restore time takes longer than backup as it requires the re-installation of
applications and a node reboot.

2.1.4 AP SW Upgrade Time

The Software Upgrade total time depends on the number of corrections, functional
content and operating system fixes and changes. The worst use case is when a
major release of operating system is released together with AP fixes. Upgrade
time is reported in the tables below according to the content type.

The table below shows the APG43L 3.2 SW upgrade time in APG43/3:

Table 8 AP SW Upgrade Time in APG43/3 System

Input parameters APG43L Measured Data
Content Type Update time APG43/3 (min)
Only Application Corrections 20-30
Application + Operating System 35-45
Corrections

The table below shows the APG43L 3.2 SW upgrade time in APG43/2 system:

3/10948-APZ 212 33/62 Uen E | 2017-02-03 5

 APG43L 3.2 Network Impact Report

Table 9 AP SW Upgrade Time in APG43/2

Input parameters APG43L Measured Data
Content Type Update time APG43/2 (min)
Only Application Corrections 20-30
Application + Operating System 40-50
Corrections

2.1.5 Throughput of Data Records Transfer

Sustained throughput for data records transfer (e.g. charging data) offered by
using three different protocols (FTP, SFTP and BGWrpc) are shown in this chapter.

Typical settings for CP-AP buffer size and size of sent file have been used for the
three mentioned protocol types.

The table below reports the data records transfer throughput in APG43L 3.2 for
APG43/3 and APG43/2 Single-CP System:

Table 10 Data records transfer throughput in APG43/3 and APG43/2 Single-CP

System
Input parameters APG43L Measured Data
Data Recor CP-AP Size of file APG43/3 with APG43/2 with
ds Transfer buffer size sent (kB) APZ 212 60F APZ 212 60
Throughput (kB)
(KB/s)
4 4096 3000-10000* 800-1200
FTP 8 8192 5000-15000* 1800-2200
16 16384 10000-30000* Not available
4 4096 8000-10000 800-1200
SFTP 8 8192 15000-20000 1800-2200
16 16384 18000-20000 Not available
2 2 200 200
BGWrpc
4 32 2500-3000 900-1000

The table below reports the data records transfer throughput in APG43L 3.2 for
APG43/3 and APG43/2 Multi-CP System:

6 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 General Impact

Table 11 Data records transfer throughput in APG43/3 and APG43/2 Multi-CP

System
Input parameters APG43L Measured Data
Data Recor CP-AP Size of file APG43/3 with APG43/2 with
ds Transfer buffer size sent (kB) APZ 214 10 APZ214 03
Throughput (kB)
(KB/s)
4 4096 2800-18000* 2500-4000*
FTP 8 8192 5000-20000* 5000-6000*
16 16384 Not available* Not available*
4 4096 8000-10000 2500-4000
SFTP 8 8192 13000-15000 5000-6000
16 16384 Not available Not available
2 2 200 200
BGWrpc
4 32 2500-3500 900-1400

* Note: The lower value refers to destinations with Windows FTP server based on
Microsoft IIS and Windows registry key TcpTimedWaitDelay set to default value
(240s). The higher one refers to destinations either with Windows FTP server
based on Microsoft IIS and Windows registry key TcpTimedWaitDelay set to 30s,
or to destinations based on Linux FTP servers.

2.1.6 Throughput of Direct Data Transfer

Sustained throughput for direct data transfer offered by using three different
protocols (FTP, SFTP and BGWrpc) are shown in this chapter.

Typical settings for CP-AP buffer size and size of sent file have been used for the
three mentioned protocol types.

The table below reports the direct data transfer throughput in APG43L 3.2 for
APG43/3 and APG43/2 Single-CP System:

Table 12 Direct data transfer throughput in APG43/3 and APG43/2 Single-CP

System
Input parameters APG43L Measured Data
Direct Data CP-AP Size of file APG43/3 with APG43/2 with
Transfer buffer size sent (kB) APZ 212 60F APZ 212 60
Throughput (kB)
(KB/s)
2 2048 2000-2500* 1500-1800
FTP
4 4096 3000-4000* 2000-2500

3/10948-APZ 212 33/62 Uen E | 2017-02-03 7

 APG43L 3.2 Network Impact Report

2 2048 2000-2500 1500-1800

SFTP
4 4096 3000-4000 2000-2500
2 2 700-800 800-1000
BGWrpc
4 16 1500-2000 1500-2000

The table below reports the direct data transfer throughput in APG43L 3.2 for
APG43/3 and APG43/2 Multi-CP System:

Table 13 Direct data transfer throughput in APG43/3 and APG43/2 Multi-CP

System
Input parameters APG43L Measured Data
Direct Data CP-AP Size of file APG43/3 with APG43/2 with
Transfer buffer size sent (kB) APZ 214 10 APZ214 03
Throughput (kB)
(KB/s)
2 2048 6000-8000* 2000-3000*
FTP
4 4096 10000-12000* Not available*
2 2048 6000-8000 1500-1800
SFTP
4 4096 8000-10000 1500-1800
2 2 2000-2500 Not available
BGWrpc
4 16 6000-8000 Not available

* Note: The results refer to destinations either with Windows FTP server based
on Microsoft IIS and Windows registry key TcpTimedWaitDelay set to 30s, or to
destinations based on Linux FTP servers.

2.2 Hardware
For APG43/3 a new family of GEP5 boards is supported, based on 64 GB RAM.

2.3 File System

No differences compared to APG43L 3.0.

2.4 Implementation
The preparation of customer network is a critical part, especially the first time an
APG43L is introduced in the network. In particular, the setup of OSS-RC with
Lightweight Directory Access Protocol (LDAP) server and public key infrastructure
is required for the centralized user management.

8 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 General Impact

The preparation of customer network is a critical part, especially the first time an
APG43L is introduced in the network. In particular Local Authentication (LA)
provides a management interface to manage a standalone authentication service
for Operation and Maintenance (OaM) access in the Managed Element (ME) that
does not rely on a data store external to the ME.

Refer to User Instructions Network Introduction of APG43L 3.2, Reference [5], for
how to introduce for the first time APG43L 3.2 in the network, for the use cases of
the APG node installed from scratch and as HW swap.

When not using OSS-RC, the recommended connection tool for direct connections
to APG is WinFIOL.

2.5 Interface
The following table reports the supported standard protocols:

Table 14 Supported Standard Protocols

Application Layer
Telnet • FTP • SSH • SFTP • LDAPS • RPC • HTTP • NETCONF
Transport Layer
TCP
Network/Internet Layer
IP • IPSec
Data link/Physical Layer
Ethernet

2.5.1 Inter-Node Interface

The table below provides the full set of listening ports and supported protocols
provided by APG43L 3.2. For each port and based on user type, it shows the
allowed access session type for each specific protocol.

User profiles:

— OaM = Operation and Maintenance;

— TS = Troubleshooting.

Table 15 Session Types for OaM and TS Users

Session Types Protocols
User Profile TCP Port SFTP SSH FTP (Note 4) Telnet (Note 4)
Number

3/10948-APZ 212 33/62 Uen E | 2017-02-03 9

 APG43L 3.2 Network Impact Report

Table 15 Session Types for OaM and TS Users

21 File Transfer session
22 File Transfer AP session
session MML session
(Note 1)(Note 5)
23 AP session
MML session
(Note 1)(Note 5)
52000 MML session
52001 AP session
52010 (Note 2)(Note 5)
52011
52100
52101
52110
52111
OaM and TS User
52002 MML session
(Note 3)(Note 5)
AP session
(Note 2)
5000 MML session
5001 AP session
5010 (Note 2)(Note 5)
5011
5100
5101
5110
5111
5002 MML session
(Note 3)(Note 5)
AP session
(Note 2)
830 NETCONF session
4422 TS session
MML session
(Note 1)(Note 5)
TS User
4423 TS session
MML session
(Note 1)(Note 5)

— Note 1: Via AP command mml into opened session;

— Note 2: Via MML command APLOC into opened MML session;

— Note 3: Via Ericsson client WinFIOL;

— Note 4: Insecure client types File Transfer Protocol (FTP) and Telnet are
not recommended;

— Note 5: In a Dual-APG configuration MML session is allowed only from AP1.

For APG43L 3.2, the table below reports the maximum number of supported
connections for Telnet and SSH, for the different TCP ports and for the different
GEP types.

10 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 General Impact

Table 16 Maximum Number of Supported TCP Connections

TCP Port Maximum Number of Connections
Telnet SSH GEP1 GEP2 GEP5
23 22 128 128 128
4423 4422 128 128 128
5000 52000 150 255 768
5001 52001 150 255 512
5002 52002 150 255 512
5010 52010 150 255 512
5011 52011 150 255 512
5100 52100 150 255 512
5101 52101 150 255 512
5110 52110 150 255 512
5111 52111 150 255 512

For more information refer to User Guide How to Access an AXE, Reference [4].

2.6 Operation
APG43L 3.2 introduces, compared with APG43L 3.0, some changes in terms of:

— New, changed or dismissed functions;

— Deprecated AP commands;

— Model item changes;

— New and modified Operational CPI documents (Printout Descriptions,

Operational Instructions, User Guides).

The details about above changes are described in Section 4 on page 15.

Note: For a description of changes in STS Object Types and/or Counters, refer to
specific AXE Application documentation.

2.7 Functional Changes

APG43L 3.2 introduces some functional changes compared with APG43L 3.0. The
changes details are explained in the following sections.

3/10948-APZ 212 33/62 Uen E | 2017-02-03 11

 APG43L 3.2 Network Impact Report

2.7.1 User Management

2.7.1.1 Local Users

Local user management requires an administrator account on the each of

connected APG(s) . It is identified as laadmin user and it’s a system created
instance of AdministratorAccount Managed Object Class (MOC) that is
instantiated at installation time and locked. It is requested the unlock operation to
enable it. Unlocking of Administrator account is allowed only to TS administrator
user issuing pwdresetlaadmin command.

The procedure for creation of local user is changed with respect to APG43L 3.0
and a specific procedure has created to administration of local users. Refer to User
Guide User Management, Reference [6], for more information.

In APG43L 3.2 it is not allowed to define more than 299 local users.

2.7.1.2 Troubleshooting Users

In APG43L 3.2 it is not allowed to define more than 200 Troubleshooting (TS)
users.

The maximum account age is increased from 14 days to 30 days. So, the attribute
maximumAccountAge can be set in the range 1..30.

The printout which is produced to a TS user at first time login is changed with
respect to APG43L 3.0.

Old printout:

login as: ts_test

Using keyboard-interactive authentication.
******************************************************************
**************
IF YOU ARE NOT AN AUTHORIZED USER, PLEASE EXIT IMMEDIATELY.
******************************************************************
**************
Password:
Using keyboard-interactive authentication.
Password change requested. Choose a new password.
Old Password:
Using keyboard-interactive authentication.
New password:
Using keyboard-interactive authentication.
Retype new password:
Password changed.

New printout:

login as: ts_test

Using keyboard-interactive authentication.

12 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 General Impact

******************************************************************
**************
IF YOU ARE NOT AN AUTHORIZED USER, PLEASE EXIT IMMEDIATELY.
******************************************************************
**************
Password:
Using keyboard-interactive authentication.
You are required to change your password immediately (root
enforced)
Old Password:
Using keyboard-interactive authentication.
New password:
Using keyboard-interactive authentication.
Retype new password:
Password changed.

2.7.2 Direct Data Transfer

APG43L 3.2 introduces a new function called Direct Data Transfer Management
allowing to configure transfer of data without using any permanent or external
storage for such data in transit. Supported external protocols for direct data
transfer are RPC, SFTP, FTP.

In order to use this function a minimum SW level of MSC 17A or HLR 17A is
needed.

Refer to User Guide Direct Data Transfer Management, Reference [3], for specific
information about how to employ the function.

2.7.3 LDAP Server

In case a new LDAP server is configured on APG via installation of new certificates,
it is recommended to migrate existing users keeping the same identities (UID)
used in old LDAP server. If this is not followed, an authentication attempt will
fail for 60 seconds.

2.7.4 CP Configuration Management via Model Interaction

APG43L 3.2 provides support for configuration management of CP through model
interaction in an AP session, in addition to configuration through MML commands
in an MML session. This is useful in case a Management System (MS) does not
support MML session handling.

As prerequisite, a configuration mediation module should be installed on APG43L

3.2, and onwards, within the CP SW upgrade of the related AXE application,
BSC, MSC, HLR. Two new MML commands have been introduced to install the
configuration mediation module, FCCML, and to print related information, FCCMP.

3/10948-APZ 212 33/62 Uen E | 2017-02-03 13

 APG43L 3.2 Network Impact Report

2.7.5 Support for Static Route

APG43L 3.2 allows to configure a static route between the OaM untagged APG
network and an external destination reachable via a supplementary gateway
server.

In particular, the existing netdef AP command is extended so as to offer a static

route not only for an already defined tagged (via VLAN) network, but also for an
untagged network. The netls AP command is modified as well, in order to list
also all defined static routes not belonging to tagged networks.

2.7.6 Software-Based MAU

The primary objective of the Maintenance Unit (MAU) is to control the CP
states, take the faulty CP unit out of service and preserve fault information for
post-mortem analysis.

APG43L 3.2 supports the software-based Maintenance Unit (MAU) functionality,

thus removing the need for the physical MAU Board (MAUB).

SW-based MAU is implemented as a purely software function, running on APG.

SW-based MAU is applicable from APZ 212 60F onwards.

2.7.7 Recovery Procedure

For recovery use cases of APG43L 3.2 where an LCT is needed, the LCT SW
needs to be updated.

Ericsson Support can be contacted for further information.

2.7.8 Support for IP-STP

A new value for the enumeration AxeApplication has been added for representing
an IP-STP AXE node. The read-only attribute axeApplication will acquire the new
enumeration value IPSTP only for newly installed IP-STP nodes (in case of SW
upgrade the attribute will keep the existing value MSC).

3 Upgrade

SW upgrade from APG43L 2.2, 3.0 and 3.1 to APG43L 3.2 is supported.

14 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 Additional Information

The old APG releases provided the support for local authentication and during SW
upgrade the local users which were available will be migrated using the new local
authentication mechanism. If the baseline contains a local user with upper case
characters then the SW Upgrade will fail.

Note: Before beginning the upgrade procedure towards APG43L 3.2, it is

necessary to install on APG an AXE Application (either BSC or MSC or HLR) SW
package which must be specific for APG43L 3.2. In case this step is not carried
out, the upgrade procedure will fail and an APG Restore will be needed.
Refer to specific AXE Application SW upgrade procedures for more details.

4 Additional Information

4.1 Operation

4.1.1 New AP Commands in APG43L 3.2

The table below lists new AP commands in APG43L 3.2 when compared to
APG43L 3.0.

Table 17 New AP commands

Command Comment
back New command for navigating back.
The CLI session will keep the last
cursor locations, and this command
will change cursor location to the
previous one.
pwdresetlaadmin New command for reset of
administrator account laadmin
password. Unlocking of Administrator
account is allowed only to TS
administrator user by issuing
pwdresetlaadmin command. If
option -h is specified, the new
hashed password is directly set to the
administrator account.

4.1.2 Deprecated AP Commands in APG43L 3.2

N/A

3/10948-APZ 212 33/62 Uen E | 2017-02-03 15

 APG43L 3.2 Network Impact Report

The table below lists all AP commands that are deprecated in APG43L 3.2 when
compared to APG43L 3.0.

Table 18 Removed AP commands are:

localuseradd
localuserdel
localuserlist
localusermod

4.1.3 Changed AP Commands in APG43L 3.2

The table below lists all AP commands that have changed their behavior on
APG43L 3.2 when compared to APG43L 3.0.

Table 19 Changed AP commands

Command Comment
dn Introduction of a new command usage
making MOM navigation faster.
netdef Support for static route definition in
APG43L.
netls Support for static route listing in
APG43L.
show Introduction of a new option for
recursive execution.
show-table Introduction of a new option for
recursive execution.

4.1.4 New MML Commands

The table below lists new MML commands introduced in APG43L 3.2.

Table 20 New MML commands in APG43L 3.2

Command Comment
FCCML Installing the configuration mediation
module on APG.
FCCMP Printing information about
configuration mediation module.

16 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 Additional Information

4.1.5 New Alarms

The table below lists new alarms introduced in APG43L 3.2.

Table 21 New Alarms in APG43L 3.2

Printout Comment
AP, CONFIGURATION MEDIATION This alarm is raised in case an
MANAGEMENT, FAULT operation with the configuration
mediation module has failed.
AP DATA SOURCE WARNING This alarm is raised when the total
memory allocated for the defined Data
Source for the Direct Data Transfer
function has reached its predefined
warning size limit.
DIRECT DATA TRANSFER FAULT This alarm is raised when there is a
connection lost to the remote system
for both block and file transfer in DDT
service
AP, LOCAL USER AUTHENTICATION, The alarm is raised with a specific
FAULT reason, when the authentication
failure limit is reached for the local
administrator user account.

4.1.6 Removed Alarms

N/A

4.1.7 Changed Alarms

N/A

4.2 Documentation

4.2.1 New APG documents

The tables of next subsections report new documents introduced in APG43L 3.2
compared with APG43L 3.0.

4.2.1.1 New Manual pages

N/A

3/10948-APZ 212 33/62 Uen E | 2017-02-03 17

 APG43L 3.2 Network Impact Report

4.2.1.2 New Command Descriptions

The table below reports new Command Descriptions introduced in APG43L 3.2.

Table 22 New Command Descriptions in APG43L 3.2

Document Document Number
FCCML: Function Change, 4/19082-CNZ 218 1161/4
Configuration Mediation Module,
Load
FCCMP: Function Change, 5/19082-CNZ 218 1161/4
Configuration Mediation Module,
Print

4.2.1.3 New Printout Descriptions

The table below reports new Printout Descriptions introduced in APG43L 3.2.

Table 23 New Printout Descriptions in APG43L 3.2

Document Document Number
Configuration Mediation Module Data 5/19083-CNZ 218 1161/4
Configuration Mediation Module 6/19083-CNZ 218 1161/4
Loading Result
AP, LOCAL USER AUTHENTICATION, 3/190 83-CNZ 222 270/5
FAULT

4.2.1.4 New Operational Instructions

The table below reports new Operational Instructions introduced in APG43L 3.2
compared with APG43L 3.0.

Table 24 New Operational Instruction documents

Title Comment Document number
AP, CONFIGURATION This document describes 1/154 31-CNZ 218
MEDIATION the actions to be taken 1166/4
MANAGEMENT, FAULT in case an operation
with the Configuration
Mediation Module has
failed.
AP DATA SOURCE This document describes 1/154 31-CNZ 220
WARNING the actions to be taken 1052/5
when an AP DATA
SOURCE WARNING
alarm is received.

18 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 Additional Information

DIRECT DATA This document describes 2/154 31-CNZ 220

TRANSFER FAULT the actions to be taken 1052/5
when a DIRECT DATA
TRANSFER FAULT
alarm is received.
Function Change, This document 15/15431-CNZ 218
Configuration Mediation describes the actions 1161/5
Module, Initiate to install/upgrade the
Configuration Mediation
Module on APG.

4.2.1.5 New User Guides

The table below reports new User Guides introduced in APG43L 3.2 compared
with APG43L 3.0.

Table 25 New User Guides

Document Comment Document number
Direct Data Transfer New User Guide 1553-CXA 117 0053/5
Management describing how to
operate with the
Direct Data Transfer
Management function.
Time Management New User Guide 2/1553-CXA 117
describing how to 0043/5
operate with the Time
Management function.
User Management New User Guide, 604/1553-CXA 118
Describes the user 03/2
management function
in terms of local user
management and
Troubleshooting (TS)
user management of
users accessing to an
AXE node

4.2.2 Changed APG documents

4.2.2.1 Changed User Guides

The table below reports User Guides changed in APG43L 3.2 compared to APG43L
3.0.

3/10948-APZ 212 33/62 Uen E | 2017-02-03 19

 APG43L 3.2 Network Impact Report

Table 26 User Guides changed in APG43L 3.2

Document Reason for Change Document Number
AXE Equipment New doc. number. 1/1553-CXA 117
Management 0046/5-V3
Data Transfer Range for attribute 1553-CXA 117 0052/5
Management removeDelay has been
changed from -1..10080
to -1..20160.
File Management New quotas defined for 5/1553-CXA 118
AXE node IP-STP. 03/2-V3
License Management New doc. number. 1553-CXA 117
0050/5-V3
OaM Command Line User Guide has a 8/1553-CXA 118 03/2
Interface new title: "ECLI:
Ericsson Command-Line
Interface". New
AP command back
introduced, plus minor
improvements.
Time Reference New classes 1553-CXA 117 0003/5
Configuration SwitchTimeService and
Management SwitchTimeReference
replacing ScxTimeServic
e and ScxTimeReference.
Transport Management Static route support in 12/1553-CXA 118
APG43L. 03/2-V3

4.2.2.2 Changed Manual Pages

The table below reports Manual Pages changed in APG43L 3.2 compared to
APG43L 3.0.

Table 27 Manual Pages changed in APG43L 3.2

Document Reason for Change Document Number
alogfind: Audit Log, New option to list only 3/190 80-CNZ 222 239
Search the MML commands
send by configuration
mediation module.
hcstart: AP, Health New doc. number. 8/190 80-CNZ 222
Check, Start 272/5-V3

20 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 Additional Information

mktr: Make Trouble Added extra logs for 1/190 80-CNZ 222
Report configuration mediation 285/5-V3
module. New doc.
number.
netdef: AP, Network, Static route support in 4/190 80-CNZ 226
Define APG43L. 28/5-V3
netls: AP, Network, List Static route support in 24/190 80-CNZ 226
APG43L. 28/5-V3
snrinit: AP, Single New doc. number. 22/190 80-CNZ 226
Node Recovery, Init 28/5-V3

4.2.2.3 Changed Printout Descriptions

The table below reports Printout Descriptions changed in APG43L 3.2 compared
to APG43L 3.0.

Table 28 Printout Descriptions changed in APG43L 3.2

Printout Reason for Change Document Number
AP FAULT New doc. number. 1/190 83-CNZ 222
270/5-V3
AUDIT LOG FORMAT Added new tag 1/190 83-CNZ 222 239
specifying configuration
mediation module
commands.

4.2.2.4 Changed Operational Instructions

The table below lists all Operational Instruction that have been changed in
APG43L 3.2 compared with APG43L 3.0.

Table 29 Changed Operational Instructions in APG43L 3.2

Title Reason for Change Document Number
AP FAULT New doc. number. 1/154 31-CNZ 222
270/5-V3
AP, Data Disk, Recovery Support of 64 GB GEP5. 24/154 31-CNZ 226
28/5-V3
AP, IP Address Change, Static route support in 1/154 31-CNZ 226 28/5
Initiate APG43L.
AP, System, Repair Support of 64 GB GEP5. 29/154 31-CNZ 226
28/5-V3
APG43L, AP board, Support of 64 GB GEP5. 28/154 31-CNZ 226
Repair 28/5

3/10948-APZ 212 33/62 Uen E | 2017-02-03 21

 APG43L 3.2 Network Impact Report

APG43L, System Double Support of 64 GB GEP5. 2/15431-CNZ 226

Node Disaster, Recovery 28/5-V3
BIOS Upgrade and Support of 64 GB GEP5. 1/154 31-ANZ 212 44/5
Recovery Procedure
Intelligent Platform Support of 64 GB GEP5. 3/154 31-ANZ 212 44/5
Management Interface
Firmware, Upgrade

4.2.3 Modified MOM items

The following tables list the modified MOM items in APG43L 3.2 compared with
APG43L 3.0.

Table 30 Added classes

Class Name Comment
AccountPolicy It represents properties of account
policy that can be referenced by users.
AdministratorAccount It used for initial and recovery
scenarios when authentication to
regular OaM accounts is inaccessible.
BlockPeer Part of Direct Data Transfer
Management function.
DataSink Part of Direct Data Transfer
Management function.
DataSource Part of Direct Data Transfer
Management function.
DirectDataTransferM Part of Direct Data Transfer
Management function.
FileFormat Part of Direct Data Transfer
Management function.
FilePeer Part of Direct Data Transfer
Management function.
LocalAuthenticationMethod It is the root MO and represents
Local Authentication (LA) related
information.
OutputFormat Part of Direct Data Transfer
Management function.
PasswordPolicy It represents properties of the
password policy and the configuration
can be changed by using MOC
PasswordQuality.

22 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 Additional Information

PasswordQuality It represents properties the password

quality.
SwitchTimeReference Part of Time Reference Management
function.
SwitchTimeService Part of Time Reference Management
function.
SwMau Part of AXE Equipment Management
function.
TransferProgress Part of Direct Data Transfer
Management function.
UserAccount It represents a user account and
these includes password policies and
account lockout policies.
UserAccountM It represents the management of OaM
user accounts.

Table 31 Removed Classes

Class Name
InfiniteSubFile

Table 32 Changed Classes

Class Name Items changed
DualSidedCp New attribute:
mauType
FileGroup New attribute:
files
LocalAuthorizationMethod New attribute:
administrativeState

4.2.4 Removed APG documents

4.2.4.1 Removed Manual Pages

N/A

4.2.4.2 Removed Printout Descriptions

N/A

3/10948-APZ 212 33/62 Uen E | 2017-02-03 23

 APG43L 3.2 Network Impact Report

4.2.4.3 Removed Operational Instructions

N/A

4.2.4.4 Removed User Guides

N/A

24 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 Glossary

Glossary

AP GEP
Adjunct Processor Generic Ericsson Processor

APG HLR
Adjunct Processor Group Home Location Register

APUB HW
Adjunct Processor Unit Board Hardware

BC IPSec
Blade Cluster Internet Protocol Security

BGW IP-STP
Billing Gateway IP Signalling Transfer Point

BGWrpc LCT
Billing Gateway Remote Procedure Call Local Craft Terminal

BRP LDAP
Basic Recording Period Lightweight Directory Access Protocol

BSC LKF
Base Station Controller License Key File

BSP LA
Blade Server Platform Local Authorization

CP MAU
Central Processor Maintenance Unit

DDT MAUB
Direct Data Transfer Maintenance Unit Board

DRBD MML
Distributed Replicated Block Device Man Machine Language

EGEM MO
Enhanced Generic Ericsson Magazine Managed Object

EGEM2 MOM
Enhanced Generic Ericsson Magazine version 2 Managed Object Model

FE MSC
Front End Mobile Switch Centre Server

FTP NETCONF
File Transfer Protocol Network Configuration

3/10948-APZ 212 33/62 Uen E | 2017-02-03 25

 APG43L 3.2 Network Impact Report

NTP
Network Time Protocol

OaM
Operation and Maintenance

OSS
Operations Support System

RP
Regional Processor

RPC
Billing Gateway Remote Procedure Call

SFTP
Secure FTP

STS
Statistics and Traffic Measurement Subsystem

SW
Software

TS
Troubleshooting

UID
User Identity

UUID
Universal Unique Identifier

VLAN
Virtual Local Access Network

VM
Virtual Machine

VNF
Virtualized Network Function

26 3/10948-APZ 212 33/62 Uen E | 2017-02-03

 Reference List

Reference List

[1] APG43L 3.0 Network Impact Report

NETWORK IMPACT REPORT

[2] AXE Equipment Management

USER GUIDE

[3] Direct Data Transfer Management

USER GUIDE

[4] How to Access an AXE

USER GUIDE

[5] Network Introduction of APG43L 3.2

USER INSTRUCTIONS

[6] User Management

USER GUIDE

3/10948-APZ 212 33/62 Uen E | 2017-02-03 27