Configuration Management; Fault Management - Ericsson MINI-LINK 6351 Technical Description

7.3

Configuration Management

Configuration management operations are performed using CLI or an
XML-based protocol towards a ServiceOn Element Manager (SOEM).
7.3.1 Configuration File
The configuration file is stored both in the RMM and in a flash memory on
the packet radio.
If a packet radio needs to be replaced, the RMM from the faulty packet radio
can be inserted in the new packet radio.
If a packet radio or an RMM is replaced, the configuration file identity of the
RMM and flash memory are compared on power up. If the configuration file
identity differs, the configuration file on the RMM is used.
7.3.2 Automatic Rollback
An automatic rollback function for the configuration is available. When this
function is enabled, most changes to the configuration are temporary (to avoid
malfunction, changes that has to do with the internal configuration database,
licenses, software, and users are always saved).
Unless a command to save the changes is entered within 15 minutes, the
configuration automatically reverts to the state it was in before the changes
were made,
7.3.3 Scripts on RMM
CLI scripts that are located on the RMM are executed automatically when the
packet radio is powered up.
MINI-LINK RMM Writer is needed to write scripts to the RMM. MINI-LINK RMM
Writer is part of MINI-LINK Configuration Generator.
7.4

Fault Management

All software and hardware in operation is monitored by the control system. The
control system locates and maps faults to replaceable HW parts.
The practical fault management is based around alarm and event notifications.
Reporting of some alarms is turned off by default. Furthermore, alarm filter
persistency is set for some types of alarms by default. This may prevent
reporting of some types of alarms by default.
1/22102-HRA 901 17/9 Uen PU1 | 2016-07-04
Management
41