AXE Equipment Management: User Guide

AXE Equipment Management
USER GUIDE
1/1553-CXA 117 0046/5-V3 Uen C

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.
Abstract
This document describes the AXE Equipment Management function for

APG43L, acting as Adjunct Processor Group (APG).
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

Contents
Contents
1 General 1
1.1 Revision Information 1
1.2 Concepts 1
1.3 Scope 3
1.4 Introduction 4
2 How to Use 9
2.1 Define a Shelf 9
2.2 Define an AP Blade 9
2.3 Define a CP Blade 13
2.4 Define Other Blade 18
2.5 Remove a Blade 27
2.6 Reset a Blade 28
2.7 Block a Blade 32
2.8 Deblock a Blade 33
2.9 List Hardware Configuration 34
2.10 List SCB Info 35
2.11 List SCX Info 35
2.12 Change Cluster Operation Mode 36
2.13 Change OaM Profile 38
2.14 Remove OaM Profiles 38
2.15 Export CCF 39
2.16 Import CCF 40
2.17 Activate CCF 40
2.18 Rollback CCF 41
2.19 Enable LAG Function 42
2.20 Disable LAG Function 42
2.21 Change APZ System 43
2.22 Change CP Type 45
2.23 Administration of MAUS 47
2.24 Actions on Alarms 48
3 Configuration 53
3.1 First Installation of CCF 53
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

Glossary 55
Reference List 57
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

General
1 General
1.1 Revision Information

Table 1 Revision Information
Revision Date Comment
A 2016-07-28 Updated document based on 1/1553-CXA 117
0025 Uen Rev. E. New option to handle the
Maintenance Unit (MAU) as SW emulation
added.
Updated Section 1.2 on page 1 and Section 1.4
on page 4. Added Section 2.23 on page 47.
B 2016-09-26 Minor changes added.
1.2 Concepts
AP blade An Adjunct Processor (AP) blade is any equipment
related to an Adjunct Processor Group (APG); in
particular two AP nodes, node A and node B, two
data disk nodes, a Digital Versatile Disk (DVD), and a
Generic Ericsson Alarm (GEA).
Blade Server Platform

An infrastructure management product that provides the
backbone for an Ericsson multi-application site solution.
It offers services and resources in order to streamline
user interface and implementation for common
infrastructure tasks for different Ericsson applications.
Applications that are running on Blade Server Platform
(BSP) are implemented as BSP tenants.
Classic CP A Central Processor (CP) blade that belongs to

APZ21233 and APZ21233C CP Hardware (HW)
versions.
Cluster CP A CP that is a member of a CP Cluster.
Command Classification File

A file consisting of all Man-Machine Language (MML)
commands and the dispatching rules applicable for
them. The file is stored on AP. There is one Command
Classification File (CCF) for each application type, for
example MSC or HLR.
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 1

CP blade A CP blade is any board, such as Central Processor

Unit Board (CPUB), Maintenance Unit Board (MAUB)
and Regional Processor Bus Interface, Serial (RPBI-S),
related to a CP. CPUB and MAUB are clustered
together forming a dual-sided CP.
CP Cluster A set of cluster CPs that provides CP functionality. It is

implemented using a variable number of cluster CPs
(3-64).
Cluster Operation Mode

Determines the level of Operation and Maintenance
(OaM) activities allowed in a CP Cluster. There are 2
cluster operation modes, Normal and Expert.
• Normal Mode is intended for regular OaM activities

in the CP cluster. In Normal Mode, the CP cluster
system protects itself to a great extent against
data inconsistencies among cluster CPs that
can be introduced through incorrect handling. If
inconsistencies cannot be avoided, the system can
still detect and report inconsistencies when they are
created.
• The Expert Mode is reserved for advanced cluster

level operation and maintenance activities (for
example, software updates or upgrades). This
mode is intended for expert users only. It is the
responsibility of the expert user to maintain data
consistency among cluster CPs when expert mode
is used.
Dual-Sided CP A 1+1 redundant CP (A+B side). Such CP consists also

of a Maintenance Unit (MAU).
Multi-CP System
A system that includes several types of CPs regardless
if the CPs are single-sided CPs or dual-sided CPs.
OaM Profile A Network Element property defining the functional level

that is in effect on the AP and the CP cluster.
Non-Classic CP CpBlade that belongs to APZ21255 and later HW

versions.
2 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

General
Other Blade Other blade can refer to any board other than an AP
or CP blade, such as System Control Switch Board
(SCXB), System Control Board - Regional Processor
(SCB-RP), Evo Processing Board 1 (EPB1), Component
Main Switch Board (CMXB), Evo Exchange Terminal
(EvoET), Integrated Protocol Tracer Board (IPTB),
Integrated Protocol Load Balancer (IPLB), or Gigabit
Ethernet Switch Board (GESB).
Shelf A shelf represents a specific magazine or subrack in

which different types of boards can be inserted. It can
be an Enhanced Generic Ericsson Magazine (EGEM)
with SCB as shelf manager or Enhanced Generic
Ericsson Magazine, type 2 (EGEM2) with SCX as shelf
manager and AXE managed Infrastructure or in EGEM2
with BSP managed infrastructure. This is used to
specify the shelf address where the board is placed.
The address is made up from the address plugs in the
magazine expressed as a.b.c.d where
a - Address plug 0 (Integer 0-15)
b - Address plug 1 (Integer 0-15)
c - Address plug 2. Is always zero (Integer 0-15)
d - Address plug 3 (Integer 0-15)
Single-CP System
A system that includes the Dual-Sided CP type only.
Single-Sided CP A Cluster CP without redundancy on a CP board level.
SW MAU The SW emulation of CP MAU is responsible for

controlling the CP states, monitoring the CP-A and CP-B
side for faults, and provides expert commands (CPT)
that allow the operator to recover the CP in case of fault.
SW MAU is referred to as MAUS.
1.3 Scope
This User Guide is written as an aid for the configuration and management of
equipment blades belonging to an AXE node.
The knowledge of the following User Guides is a prerequisite for this document.
• AXE Functions Management, Reference [3]
• Ericsson Command-Line Interface, Reference [5]
• How to Access an AXE, Reference [6]
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 3

• Managed Element Management, Reference [8]
• Managed Object Model, Reference [9]
• User Management, Reference [10]
1.4 Introduction
The AXE Equipment Management function allows the hardware configuration,
the management and the supervision of AP blades, CP blades, and other
blades, as well as the management of OaM Profile and CCF.
The function allows:
• Defining a blade
• Removing a blade
• Resetting a blade
• Blocking a blade
• Deblocking a blade
• Listing the status and properties of a blade
• Changing the Cluster Operation Mode
• Changing OaM profile
• Removing OaM profiles
• Exporting a CCF
• Importing a CCF
• Activating a CCF
• Rolling back a CCF
• Enabling LAG Function
• Disabling LAG Function
• Changing the APZ system, that is the type of control system the CP
belongs to.
• Changing the CP type.
• Changing the state of SW MAU.
As soon as a blade is defined and powered on an IP address is automatically

assigned to it.
4 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

General
The AXE Equipment Management function is provided through a Managed

Object Model (MOM) and AP commands hwcls, hwmscbls, and hwmxls.
Figure 1 shows the AXE Equipment Management function MOM.
Figure 1 AXE Equipment Management Function MOM
Note: CpCluster Managed Object Class (MOC) and related children MOCs
are applicable for a Multi-CP system only (see the bottom right part
of Figure 1).
SystemComponentHandling is the root MOC for the System Component

Handling function; it is a container MOC without any attribute. Refer to User
Guide AXE Functions Management, Reference [3] for more information.
EquipmentM is the root MOC for the AXE Equipment Management function.
MOC HardwareMgmt represents the HW view of the configured boards. Only

one instance of this class is needed. HardwareMgmt is the root MOC for Shelf,
ApBlade, OtherBlade, CpBlade, and ApBladeInfo objects.
MOC Shelf represents a magazine containing several blades.
MOC ApBlade represents a hardware blade that is part of an AP node and

contains configuration data for the blade. For the node to operate properly, all
hardware blades must have a corresponding blade Managed Object (MO) with
configuration data. The number of AP blades do not change under normal
operation. There is no need to recreate the corresponding ApBlade MO if a
hardware blade needs to be replaced.
MOC OtherBlade represents a blade which is not a CP/AP blade.
Lag represents the root MOC for SCXB front port(s) for Link Aggregation Group
(LAG). It is a group of Ethernet links bundled together to act as a single link to
provide increased bandwidth. It consists of SCXB front ports Gigabit Ethernet
(GE1) and GE2.
Note: Lag MOC is applicable only for shelf architecture based on SCX.
MOC CpBlade represents a hardware blade that is part of a CP and contains

configuration data for the blade. For the node to operate properly, all hardware
blades must have a corresponding blade MO with configuration data. The
number of CP blades do not change under normal operation. There is no need
to recreate the corresponding CpBlade MO if a hardware blade needs to be
replaced.
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 5

MOC ApBladeInfo specifies the information of an ApBlade. All attributes of this

class are automatically updated whenever they change.
LogicalMgmt is the root MOC for the logical management view of all configured
blades. It is a container MOC, system instantiated, without any attribute.
MOC Apg represents an APG consisting of two AP nodes and two data disk
nodes, and, if present, of a DVD and a GEA. It is system instantiated. One or
two instances can be present depending on number of connected APGs.
MOC DualSidedCp represents a Dual-Sided CP consisting of two CP blades

and a CP MAU working as one unit. It is system instantiated. One or two
instances can be present depending on number of connected Dual-Sided CPs.
MOC SwMau represents the SW emulation of CP MAU. It is system instantiated

according to the value of attribute mauType in MOC DualSidedCp.
CpCluster represents a cluster system that provides CP functionality. It is

implemented using a variable number of Cluster CPs/CP blades.
MOC ClusterCp represents a Single-Sided CP (Cluster CP) regardless the

state.
MOC OmProfileManager represents a placeholder for OaM Profile handling.
MOC OmProfile represents the OaM Profile MOC and contains the related
information about the OaM Profile and its state (SUPPORTED or ACTIVE).
MOC CcFile represents the CCF MOC and contains the rules for MML
commands and its state (NOT_ACTIVE, ACTIVE or BACKUP).
MOC CcFileManager represents a placeholder of CCF stored in the APG file

system.
MOC CandidateCcFile represents a CCF stored in the APG file system and
ready to be imported.
There is a relationship between the MOM logical view of APG/CP related

equipments, represented by MOCs Apg, DualSidedCp, and ClusterCp, and the
MOM HW view, represented by MOCs ApBlade and CpBlade.
In particular an instance of MOC Apg is associated to up 6 instances of MOC
ApBlade, via the multi-value attribute apBladesDn; this is because an APG can
consists of up 6 AP blades.
And an instance of MOC DualSidedCp is associated to up 3 instances of MOC
CpBlade, via the multi-value attribute cpBladesDn; this is because a Dual-Sided
CP can consist of up 3 CP blades.
And an instance of MOC ClusterCp is associated to 1 instance of MOC
CpBlade, via the attribute cpBladesDn; this is because a Cluster CP, or
Single-Sided CP, consists of 1 CP blade.
All such associations are visible in Figure 1 as unidirectional solid lines between
MOCs Apg, DualSidedCp, ClusterCP and MOCs ApBlade and CpBlade.
6 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

General
1.4.1 Commands and HW Supervision

The AXE Equipment Management function is provided through AP commands
hwcls, hwmscbls, and hwmxls.
• hwcls: it is used to list the content of the equipment connected into an

AXE node.
• hwmscbls: it is used for SCB-RP boards, to list the slot position, the
primary and secondary IP address, the status (master or passive), and
whether the neighbour SCB-RP is present or not.
• hwmxls: it is used for SCX boards, to list the master status of switches in
the node. It also reports the functional board name, the magazine and slot
position, the primary and secondary IP Address and whether the Switch
can communicate with the neighbour.
HW supervision is meant to identify the disk replication, disk cable connection,

board fault, missing board, mirror disk redundancy, NIC connection, and so
forth. APG allows the monitoring and supervision of the boards, except the
other boards which are monitored by CP.
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 7

8 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
2 How to Use
2.1 Define a Shelf

Only after new shelf is defined, the individual blades belonging to that shelf
can be defined and configured. A shelf definition is achieved by creating an
instance of MOC Shelf.
2.1.1 Example
This example shows how to add a shelf with address 1.2.0.4.
>dn -m HardwareMgmt
ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1,SystemCompo
(HardwareMgmt=1)>configure
(config-HardwareMgmt=1)>show
HardwareMgmt=1
(config-HardwareMgmt=1)>
(config-HardwareMgmt=1)>Shelf=1.2.0.4
(config-Shelf=1.2.0.4)>commit
(Shelf=1.2.0.4)
(Shelf=1.2.0.4)up
(HardwareMgmt=1)>show
HardwareMgmt=1
Shelf=1.2.0.4
(HardwareMgmt=1)>
2.2 Define an AP Blade

To make an ApBlade up and working, creation of an MO is needed. The MO is
created by specifying the slot number into the shelf where the blade is placed.
The ApBlade supported are APUB, DISK, DVD, GEA.
The following information is required to define an ApBlade:
• Functional board name, by setting the attribute functionalBoardName.
• Side, by setting the attribute side.
• System number, by setting the attribute systemNumber.
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 9

Note: System number is used to define the number of the system which
identifies a group of AP blades that form a working unit. Only
systemNumber=1 and systemNumber=2 are used respectively
for AP1 and AP2.
2.2.1 Example 1, GEA Board

This example shows how to define a GEA board in AP1 on shelf 1.2.0.4
in slot 2.
>dn -m HardwareMgmt
ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1,SystemCompone
(HardwareMgmt=1)>Shelf=1.2.0.4
(Shelf=1.2.0.4)>configure
(config-Shelf=1.2.0.4)>ApBlade=2
(config-ApBlade=2)>functionalBoardName=GEA
(config-ApBlade=2)>systemNumber=1
(config-ApBlade=2)>commit
(ApBlade=2)>
(ApBlade=2)>show
ApBlade=2
functionalBoardName=GEA
systemNumber=1
ApBladeInfo=2
(ApBlade=2)>
Once the MO has been created in the hardware view, the logical view is
automatically created.
(ApBlade=2)>dn ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=
(LogicalMgmt=1)>show
LogicalMgmt=1
Apg=AP1
(LogicalMgmt=1)>show Apg=AP1
Apg=AP1
apBladeDn
"ManagedElement=CEMSS07,SystemFunctions=1,
AxeFunctions=1,SystemComponentHandling=1,EquipmentM=1,
HardwareMgmt=1,Shelf=1.2.0.4,ApBlade=2"
(LogicalMgmt=1)>
2.2.2 Example 2, Data Disk
This example shows how to define a Data Disk, in AP1 on shelf 1.2.0.4 in
slot 12 and assign side A to it.
>dn -m HardwareMgmt
10 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
(config-ApBlade=12)>functionalBoardName=DISK
(config-ApBlade=12)>side=A
(ApBlade=12)>
(ApBlade=12)>show
ApBlade=12
functionalBoardName=DISK
side=A
systemNumber=1
ApBladeInfo=12
(ApBlade=12)>
(ApBlade=12)>dn ManagedElement=CEMSS07,SystemFunctions=1,
AxeFunctions=1,SystemComponentHandling=1,EquipmentM=1,LogicalMgmt=1
LogicalMgmt=1
Apg=AP1
Apg=AP1
apBladeDn
"ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1,
SystemComponentHandling=1,EquipmentM=1,HardwareMgmt=1,
Shelf=1.2.0.4,ApBlade=2"
Shelf=1.2.0.4,ApBlade=12"
(LogicalMgmt=1)>
2.2.3 Example 3, DVD

This example shows how to define a DVD board in AP1 on shelf 1.2.0.4 in
slot 16.
>dn -m HardwareMgmt
(config-ApBlade=16)>functionalBoardName=DVD
(ApBlade=16)>
(ApBlade=16)>show
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 11

ApBlade=16
functionalBoardName=DVD
systemNumber=1
ApBladeInfo=16
(ApBlade=16)>
(ApBlade=16)>dn ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions
LogicalMgmt=1
Apg=AP1
Apg=AP1
apBladeDn
"ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1,SystemCo
(LogicalMgmt=1)>
2.2.4 Example 4, AP Blade

This example shows how to define an AP blade, in AP1 shelf 1.2.0.4 slot 20
and assign side A to it.
>dn -m HardwareMgmt
(config-ApBlade=20)>functionalBoardName=APUB
(config-ApBlade=20)>side=A
(ApBlade=20)>
(ApBlade=20)>show
ApBlade=20
functionalBoardName=APUB
side=A
systemNumber=1
ApBladeInfo=20
(ApBlade=20)>
(ApBlade=20)>dn ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions
12 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
LogicalMgmt=1
Apg=AP1
Apg=AP1
apBladeDn
"ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1,System
(LogicalMgmt=1)>
2.3 Define a CP Blade

This chapter describes how to configure different types of CpBlade such as
CPUB, MAUB, and RPBI-S.
RPBI-S boards are for RP-serial bus connection. This board replaces the APZ
unique functionality Regional Processor Handler (RPH) which consists of
boards Regional Processor Input/Output - 2 (RPIO2) and Regional Processor
Interface, Receiver, and Sender (RPIRS). Depending on the number of RPB-S,
there can be up to six RPBI boards where each pair serves ten RBP-S
branches.
To define a CP blade, an instance of MOC CpBlade should be created.
The attributes for defining a CpBlade board are:
• Sequence number, by setting the attribute sequenceNumber.
Note: System number is used to define the number of the system that
together with cpArchitecture identifies a group of blades that form
a working unit. Only systemNumber=1 and systemNumber=2 are
allowed.
• CP architecture, by setting the attribute cpArchitecture.
Note: Set the value of cpArchitecture=DUAL_SIDED_CP in case of MAUB

and RPBI-S boards, and cpArchitecture=SINGLE_SIDED_CP or
cpArchitecture=DUAL_SIDED_CP in case of CPUB.
The logical view is automatically created once the CpBlade is defined in the
hardware view.
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 13

In logical view DualSidedCp MO is created in case cpArchitecture is

DUAL_SIDED_CP and ClusterCp MO is created in case cpArchitecture is
SINGLE_SIDED_CP.
The attributes to define in the logical view for a DualSidedCp MO and for
a ClusterCp MO are:
• The APZ system, by setting the attribute apzSystem.
• The type of the CP board, by setting the attribute cpType.
• The alias name for the CpBlade board, by setting the attribute cpAlias.
Note: The cpAlias attribute is optional and it is applicable for a Multi-CP

system only. It can be used to specify a custom name for a CP
blade.
• The attribute mauType, which is automatically updated according to the

node configuration.
• The SwMau=1 MO is automatically created.
Note: The SwMau=1 MO is not created if the MAU is available as a

physical board.
2.3.1 Example 1, Dual-Sided CP
To define a dual-sided CP blade to the configuration, an instance of

MOC CpBlade should be created with attribute cpArchitecture set as
DUAL_SIDED_CP and functionalBoardName set as CPUB.
This example shows how to define a Dual-Sided CP having system number

equal to 1 and side to A into the shelf position 1.2.0.4 slot 3. An instance of
MOC CpBlade is to be created by setting the following attributes:
• functionalBoardName = CPUB
• side = A
• systemNumber = 1
• cpArchitecture = DUAL_SIDED_CP
>dn -m HardwareMgmt
(config-Shelf=1.2.0.4)>CpBlade=3
(config-CpBlade=3)>functionalBoardName=CPUB
(config-CpBlade=3)>side=A
(config-CpBlade=3)>systemNumber=1
(config-CpBlade=3)>cpArchitecture=DUAL_SIDED_CP
(config-CpBlade=3)>commit
14 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
(CpBlade=3)>
(CpBlade=3)>show
CpBlade=3
functionalBoardName=CPUB
ipAddressEthA="192.168.169.58"
ipAddressEthB="192.168.170.58"
side=A
systemNumber=1
cpArchitecture=DUAL_SIDED_CP
(CpBlade=3)>
(CpBlade=3)>dn ManagedElement=CEMSS07,SystemFunctions=1,AxeFunction
LogicalMgmt=1
DualSidedCp=CP1
(LogicalMgmt=1)>DualSidedCp=CP1
(DualSidedCp=CP1)>show
cpBladeDn
(DualSidedCp=CP1)>
2.3.2 Example 2, MAU Board

To define a MAUB board, an instance of MOC CpBlade should be created with
attribute cpArchitecture set as DUAL_SIDED_CP and functionalBoardName
set as MAUB.
This example shows how to define a MAUB board having sequenceNumber

1 into shelf position 1.2.0.4 slot 7. An instance of MOC CpBlade is to be
created by setting the following attributes:
• functionalBoardName = MAUB
• systemNumber = 1
>show
ManagedElement=CEMSS07
>dn ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1,
SystemComponentHandling=1,EquipmentM=1,HardwareMgmt=1,Shelf=1.2.0.4
(config-CpBlade=7)>functionalBoardName=MAUB
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 15

(CpBlade=7)>show
CpBlade=7
functionalBoardName=MAUB
systemNumber=1
(CpBlade=7)>
(CpBlade=7)>dn ManagedElement=CEMSS07,SystemFunctions=1,
AxeFunctions=1,SystemComponentHandling=1,EquipmentM=1,LogicalMgmt=1
LogicalMgmt=1
DualSidedCp=CP1
DualSidedCp=CP1
apzSystem="APZ21260"
cpBladeDn
Shelf=1.2.0.4,CpBlade=3"
Shelf=1.2.0.4,CpBlade=7"
cpType=21260
(DualSidedCp=CP1)>
2.3.3 Example 3, Single-Sided CP

To define a single sided CP, an instance of MOC CpBlade should be
created with attribute cpArchitecture set as SINGLE_SIDED_CP and
functionalBoardName set as CPUB.
This example shows how to define a single-sided CP having sequenceNumber

1 into the shelf position 1.2.0.4 slot 5. An instance of MOC CpBlade is to be
created by setting the following attributes:
• functionalBoardName = CPUB
• sequenceNumber = 1
• cpArchitecture = SINGLE_SIDED_CP
>dn -m HardwareMgmt
16 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
(config-CpBlade=5)>functionalBoardName=CPUB
(config-CpBlade=5)>sequenceNumber=1
(config-CpBlade=5)>cpArchitecture=SINGLE_SIDED_CP
(CpBlade=5)>
(CpBlade=5)>show
CpBlade=5
functionalBoardName=CPUB
systemNumber=1
sequenceNumber=1
cpArchitecture=SINGLE_SIDED_CP
(CpBlade=5)>
(CpBlade=5)>dn ManagedElement=CEMSS07,SystemFunctions=1,AxeFunction
LogicalMgmt=1
CpCluster=1
(LogicalMgmt=1)>CpCluster=1
(CpCluster=1)>show
CpCluster=1
alarmMaster=1001
allBcGroup
"BC0"
clockMaster=1001
clusterOpMode=NORMAL
ClusterCp=BC0
OmProfileManager=1
(CpCluster=1)>ClusterCp=BC0
(ClusterCp=BC0)>show
ClusterCp=BC0
cpBladesDn="ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1
(ClusterCp=BC0)>
2.3.4 Example 4, RPBI

To define an RPBI-S board, an instance of MOC CpBlade should be created
with attribute functionalBoardName set as RPBI_S.
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 17

This example shows how to define a RPBI_S board into the shelf position
1.2.0.4 slot 10 with sequenceNumber 0. An instance of MOC CpBlade is to
be created by setting the following attributes:
• functionalBoardName = RPBI_S
• systemNumber= 1
• sequenceNumber = (0 for RPBI-S-0 or 1 for RPBI-S-1 and 2 for RPBI-S-2 )
>dn -m HardwareMgmt
(config-CpBlade=10)>functionalBoardName=RPBI_S
(config-CpBlade=10)>sequenceNumber=0
(CpBlade=10)>
(CpBlade=10)>show
CpBlade=10
functionalBoardName=RPBI_S
sequenceNumber=0
(CpBlade=10)>
2.4 Define Other Blade

This chapter describes how to configure different types of Other Blades such as
SCB-RP, SCX, EPB1, CMX, EvoET, IPLB, IPT, and GESB boards.
SCB-RP boards can be defined only in EGEM magazines.
SCX, CMX, EPB1, and EvoET boards can be defined only in EGEM2
magazines with AXE managed infrastructure.
IPT boards can be defined in EGEM magazines or EGEM2 magazines with

AXE managed infrastructure.
IPLB boards can be defined only in EGEM2 magazines with BSP managed
infrastructure.
To define an Other Blade board, an instance of the MOC OtherBlade should

be created.
18 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
The Lag MOC is automatically instantiated after configuring OtherBlade MO

for SCXB residing on APZ magazine.
The attributes for defining SCB-RP, GESB, CMX, EvoET, EPB1, and IPT
boards are:
The attributes for defining an SCX board are:
• The blade product number, by setting the attribute bladeProductNumber.
The attributes for defining an IPLB board are:
Note: System number is used to define the number of the system

that identifies a group of blades that form a working unit. It is
recommended to use first unused system number.
2.4.1 Example 1, Define SCB

This example shows how to define an SCB-RP board on shelf position 1.2.0.4
slot 0. An instance of MOC OtherBlade is created by setting the attribute
functionalBoardName.
>dn -m HardwareMgmt
(Shelf=1.2.0.4)>show
Shelf=1.2.0.4
ApBlade=22
ApBlade=20
ApBlade=16
ApBlade=14
ApBlade=12
CpBlade=8
CpBlade=7
CpBlade=3
(config-Shelf=1.2.0.4)>OtherBlade=0
(config-OtherBlade=0)>functionalBoardName=SCB_RP
(config-OtherBlade=0)>commit
(OtherBlade=0)>
(OtherBlade=0)>show
OtherBlade=0
functionalBoardName=SCB_RP
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 19

sequenceNumber=1
side=A
(OtherBlade=0)>up
(Shelf=1.2.0.4)>show -s
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
(Shelf=1.2.0.4)>
2.4.2 Example 2, Define SCXB

This example shows how to define an SCXB blade into shelf position 1.2.0.4
slot 0. An instance of MOC OtherBlade is created by setting the attributes
functionalBoardName and bladeProductNumber.
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=25
(config-OtherBlade=0)>functionalBoardName=SCXB
(config-OtherBlade=0)>bladeProductNumber=ROJ208395/1
(OtherBlade=0)>
(OtherBlade=0)>show
OtherBlade=0
currentLoadModuleVersion="ManagedElement=CEMSS07,SystemFunctions=1,
bladeProductNumber="ROJ208395/1"
functionalBoardName=SCXB
20 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
side=A
Lag=1
(OtherBlade=0)>up
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
(Shelf=1.2.0.4)>
Note: Lag MO is created only for the SCXB residing in APZ magazine.
2.4.3 Example 3, Define EPB1

This example shows how to define an EPB1 blade into shelf position 1.2.0.4
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
(Shelf=1.2.0.4)>
(config-OtherBlade=18)>functionalBoardName=EPB1
(OtherBlade=18)>
(OtherBlade=18)>show
OtherBlade=18
currentLoadModuleVersion="ManagedElement=CEMSS07,SystemFunctions
functionalBoardName=EPB1
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 21

(OtherBlade=18)>up
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=18
OtherBlade=25
(Shelf=1.2.0.4)>
2.4.4 Example 4, Define CMXB

This example shows how to define a CMXB blade into shelf position 1.2.0.4
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=18
OtherBlade=25
(config-OtherBlade=26)>functionalBoardName=CMXB
OtherBlade=26
currentLoadModuleVersion="ManagedElement=CEMSS07,SystemFunctions=1
functionalBoardName=CMXB
(OtherBlade=26)>up
Shelf=1.2.0.4
22 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=18
OtherBlade=25
OtherBlade=26
(Shelf=1.2.0.4)>
2.4.5 Example 5, Define EvoET

This example shows how to define an EvoET blade on shelf 1.2.0.4 and
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=18
OtherBlade=25
OtherBlade=26
(Shelf=1.2.0.4)>
(config-OtherBlade=11)>functionalBoardName=EvoET
(OtherBlade=11)>
OtherBlade=11
currentLoadModuleVersion="ManagedElement=CEMSS07,SystemFunctions
functionalBoardName=EVOET
(OtherBlade=11)up
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 23

Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=11
OtherBlade=18
OtherBlade=25
OtherBlade=26
2.4.6 Example 6, Define GESB

This example shows how to define a GESB blade into shelf position 1.2.0.4
and slot 9. An instance of MOC OtherBlade is created by setting the attribute
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=11
OtherBlade=18
OtherBlade=25
OtherBlade=26
(config-OtherBlade=9)>functionalBoardName=GESB
(OtherBlade=9)>
(OtherBlade=9)>show
OtherBlade=9
functionalBoardName=GESB
(OtherBlade=9)>
(OtherBlade=9)>up
24 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
Shelf=15.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=9
OtherBlade=11
OtherBlade=18
OtherBlade=25
OtherBlade=26
(Shelf=15.2.0.4)>
2.4.7 Example 7, Define IPTB

This example shows how to define an IPTB blade into shelf position 1.2.0.4
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
(config-OtherBlade=5)>functionalBoardName=IPTB
(OtherBlade=5)>
(OtherBlade=5)>show
OtherBlade=5
currentLoadModuleVersion="ManagedElement=CEMSS07,
SystemFunctions=1,AxeFunctions=1,SystemComponentHandling=1,
BladeSwM=1,ApManagedSwPackage=CXP113195_6_P4J93"
functionalBoardName=IPTB
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 25

(OtherBlade=5)>up
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=5
OtherBlade=25
(Shelf=1.2.0.4)>
2.4.8 Example 8, Define IPLB

This example shows how to define side A of an IPLB blade, having system
number equal to 1, into shelf position 1.2.0.4 and slot 16. An instance of
MOC OtherBlade is created by setting the attributes functionalBoardName,
side, systemNumber.
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
(config-OtherBlade=16)>functionalBoardName=IPLB
(config-OtherBlade=16)>side=A
(config-OtherBlade=16)>systemNumber=1
OtherBlade=16
currentLoadModuleVersion="ManagedElement=CEMSS07,
SystemFunctions=1,AxeFunctions=1,SystemComponentHandling=1,
BladeSwM=1,ApManagedSwPackage=CXP1003195_6_P4J95"
functionalBoardName=IPLB
26 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
side=A
systemNumber=1
(OtherBlade=16)>up
Shelf=1.2.0.4
ApBlade=12
ApBlade=14
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=16
(Shelf=1.2.0.4)>
2.5 Remove a Blade

This chapter describes how to remove a blade from the HW configuration. The
removal procedure is common for ApBlade, CpBlade, and OtherBlade.
2.5.1 Example 1, Remove CP Blade

This example shows how to remove a CP blade represented by MO CpBlade=8.
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=10
OtherBlade=25
OtherBlade=26
OtherBlade=28
(config-Shelf=1.2.0.4)>no CpBlade=8
(config-Shelf=1.2.0.4)>commit
(Shelf=1.2.0.4)>
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 27

Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
OtherBlade=0
OtherBlade=10
OtherBlade=25
OtherBlade=26
OtherBlade=28
(Shelf=1.2.0.4)>
It is possible to list all the remaining available blades in the logical view after
the removal of the CP blade.
(Shelf=1.2.0.4)>dn ManagedElement=CEMSS07,SystemFunctions=1,AxeFuncti
cpBladeDn
"ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1,SystemComp
"ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1,SystemComp
(DualSidedCp=CP1)>
2.6 Reset a Blade

Blade reset aims for reboot and refresh of the board. This is applicable for AP
blades DVD, DISK, APUB, GEA and OtherBlade such as SCXB, CMXB, IPLB
and IPTB. For OtherBlade like SCX and CMX, a normal reset or a reset to
factory default configuration can be performed. For IPT and IPLB, it is possible
to execute a normal reset or a reset that reboots the blade from network. In
case of IPLB, it is possible to forcefully reset the board when the other IPLB in
same cluster is not active, which means that the supervision of IPLB cluster
status is skipped.
To reset a board, the action request reset can be executed on the relevant
MO of ApBlade or OtherBlade.
2.6.1 Example 1, Reset AP Blade

This example shows how to reset the APUB on shelf 1.2.0.4 and slot 20.
>dn -m HardwareMgmt
28 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
OtherBlade=26
OtherBlade=28
(Shelf=1.2.0.4)>ApBlade=20
(ApBlade=20)>show
ApBlade=20
functionalBoardName=APUB
side=B
systemNumber=1
ApBladeInfo=20
(ApBlade=20)>reset
(ApBlade=20)>
2.6.2 Example 2, Reset DVD

This example shows how to reset the DVD board on shelf 1.2.0.4 and slot 16.
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
OtherBlade=26
OtherBlade=28
(ApBlade=16)>show
ApBlade=16
functionalBoardName=DVD
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 29

systemNumber=1
ApBladeInfo=16
(ApBlade=16)>reset
(ApBlade=16)>
2.6.3 Example 3, Reset Disk

This example shows how to reset the DISK on shelf 1.2.0.4 and slot 12.
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
OtherBlade=26
OtherBlade=28
(ApBlade=12)>show
ApBlade=12
functionalBoardName=DISK
side=A
systemNumber=1
ApBladeInfo=12
(ApBlade=12)>reset
(ApBlade=12)>
2.6.4 Example 4, Reset SCX

This example shows how to reset the SCX board on shelf 1.2.0.4 and slot 0.
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
30 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
OtherBlade=26
OtherBlade=28
(Shelf=1.2.0.4)>OtherBlade=0
(OtherBlade=0)>reset --type NORMAL
(OtherBlade=0)>
2.6.5 Example 5, Reset CMX
This example shows how to reset to factory default the CMX board on shelf
1.2.0.4 and slot 26.
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
OtherBlade=26
OtherBlade=28
(OtherBlade=26)>reset --type FACTORY_DEFAULT
(OtherBlade=26)>
2.6.6 Example 6, Reset IPT

This example shows how to reset the IPT board with network boot option on
shelf 1.2.0.4 and slot 5.
>dn -m HardwareMgmt
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 31

Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=5
OtherBlade=25
(OtherBlade=5)>show functionalBoardName
functionalBoardName=IPTB
(OtherBlade=5)>reset --type NETWORK_BOOT
(OtherBlade=5)>
2.6.7 Example 7, Reset IPLB
This example shows how to reset the IPLB board with network boot option on
shelf 1.2.0.4 and slot 16.
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=16
(OtherBlade=16)>show functionalBoardName
functionalBoardName=IPLB
(OtherBlade=16)>reset --type NETWORK_BOOT
(OtherBlade=16)>
2.7 Block a Blade

This chapter describes how to block a blade. It is applicable for ApBlade like
APUB, DVD, GEA, and DISK and OtherBlade such as IPT and IPLB.
32 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
As a consequence of the block action, the board is powered OFF and the MIA
LED of the board is turned ON.
To block a board, the action block should be executed on the relevant MO.
2.7.1 Example 1, Block AP Blade
This example shows how to block the AP blade on shelf 1.2.0.4 and slot 2.
>dn -m HardwareMgmt
Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
OtherBlade=26
OtherBlade=28
(ApBlade=2)>block
(ApBlade=2)>
2.8 Deblock a Blade

This chapter describes how to deblock a blade. It is applicable for ApBlade like
APUB, DVD, GEA, and DISK and OtherBlade such as IPT and IPLB.
As a consequence of the deblock action, the board is powered ON and the

MIA LED of the board is turned OFF.
To deblock a (blocked) board, the action deblock should be executed on the

relevant MO.
2.8.1 Example 1, Deblock AP Blade

This example shows how to deblock the AP blade on shelf 1.2.0.4 and slot 2.
>dn -m HardwareMgmt
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 33

Shelf=1.2.0.4
ApBlade=2
ApBlade=12
ApBlade=14
ApBlade=16
ApBlade=20
ApBlade=22
CpBlade=3
CpBlade=7
CpBlade=8
OtherBlade=0
OtherBlade=25
OtherBlade=26
OtherBlade=28
(ApBlade=2)>deblock
(ApBlade=2)>
2.9 List Hardware Configuration

The AP command hwcls provides the list of the Hardware Configuration
(HWC) table.
2.9.1 Example
This example lists the information of HWC table.
>hwcls
HARDWARE CONFIGURATION TABLE
MAG SLOT SYSTYPE SYSNUM FBN IPA IPB

1.2.0.4 0 - - SCXB 192.168.169.56 192.168.170.56
1.2.0.4 2 AP 1 GEA - -
1.2.0.4 3 CP 1 CPUB 192.168.169.58 192.168.170.58
1.2.0.4 7 CP 1 MAUB 192.168.169.59 192.168.170.59
1.2.0.4 8 CP 1 CPUB 192.168.169.60 192.168.170.60
1.2.0.4 10 - - IPTB 192.168.169.68 192.168.170.68
1.2.0.4 12 AP 1 Disk - -
1.2.0.4 14 AP 1 APUB 192.168.169.1 192.168.170.1
1.2.0.4 16 AP 1 DVD - -
1.2.0.4 20 AP 1 APUB 192.168.169.2 192.168.170.2
1.2.0.4 22 AP 1 Disk - -
1.2.0.4 25 - - SCXB 192.168.169.57 192.168.170.57
1.2.0.4 26 - - CMXB 192.168.169.62 192.168.170.62
1.2.0.4 28 - - CMXB 192.168.169.61 192.168.170.61
2.0.0.0 0 - - SCXB 192.168.169.63 192.168.170.63
34 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
2.0.0.0 8 - - GESB 192.168.169.67 192.168.170.67

2.0.0.0 25 - - SCXB 192.168.169.64 192.168.170.64
2.0.0.0 26 - - CMXB 192.168.169.66 192.168.170.66
2.0.0.0 28 - - CMXB 192.168.169.65 192.168.170.65
2.10 List SCB Info

The AP command hwmscbls is used for SCB-RP boards, to list the slot
position, the primary and secondary Internet Protocol (IP) address, the status
(master or passive), and whether the neighbour SCB-RP is present or not.
2.10.1 Example
This example lists SCB-RP boards information.
> hwmscbls
SCB-RP/4s TABLE
SLOT IP ADDRESS IP ADDRESS SEC STATUS NEIGHBOUR

0 192.168.169.56 192.168.170.56 passive present
25 192.168.169.60 192.168.170.60 master present
>
2.11 List SCX Info

The AP command hwmxls lists the master status of switches in the node. It
also reports the functional board name, the shelf and slot position, the primary
and secondary IP address and whether the switch can communicate with its
neighbor. Using option -m, the command displays switches in the specified
shelf.
2.11.1 Example 1, List All Info

This example lists information of SCX switches.
> hwmxls
SWITCH TABLE
MAG SLOT FBN IP ADDRESS IP ADDRESS SEC STATUS NEIGHBOUR
1.2.0.4 0 SCXB 192.168.169.56 192.168.170.56 passive present
1.2.0.4 25 SCXB 192.168.169.57 192.168.170.57 master present
>
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 35

2.11.2 Example 2, List Specific Info
This example lists information of switches in the specific shelf.
> hwmxls -m 1.2.0.4
SWITCH TABLE
MAG SLOT FBN IP ADDRESS IP ADDRESS SEC STATUS NEIGHBOUR
>
2.12 Change Cluster Operation Mode

It is valid for a Multi-CP System only.
The cluster operation mode can be changed from EXPERT mode to

NORMAL mode or the opposite way. The action changeClusterOpMode under
the MO CpCluster=1 allows performing the change of cluster operation mode
specifying the requested cluster operation mode as input parameter as shown
in Page 36.
Table 2 Allowed Cluster Operation Mode Values

Input parameter value Cluster Operation Mode
NORMAL Normal Mode
EXPERT Expert Mode
The Operational Instruction AP, Configuration Data in AP, Change, Reference

[1], describes the actions to be taken to change the cluster operation mode.
2.12.1 Example 1, Change to Normal

This example shows how to change the cluster operation mode to NORMAL:
>dn -m CpCluster
(CpCluster=1)>changeClusterOpMode --clusterOpModeRequested NORMAL
(CpCluster=1)>show
CpCluster=1
alarmMaster=1001
allBcGroup
"BC0"
"BC1"
"BC10"
"BC11"
"BC12"
clockMaster=1001
36 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
operativeGroup
"BC0"
"BC10"
"BC12"
reportProgress
actionId=CHANGE_OP_MODE
result=SUCCESS
state=FINISHED
timeOfLastAction="2013-06-28 11:34:24"
ClusterCp=BC0
ClusterCp=BC1
ClusterCp=BC10
ClusterCp=BC11
ClusterCp=BC12
OmProfileManager=1
(CpCluster=1)>
2.12.2 Example 2, Change to Expert

This example shows how to change the cluster operation mode to EXPERT:
>dn -m CpCluster
(CpCluster=1)>changeClusterOpMode --clusterOpModeRequested EXPERT
(CpCluster=1)>show
CpCluster=1
alarmMaster=1001
allBcGroup
"BC0"
"BC1"
"BC10"
"BC11"
"BC12"
clockMaster=1001
clusterOpMode=EXPERT
operativeGroup
"BC0"
"BC10"
"BC12"
reportProgress
actionId=CHANGE_OP_MODE
result=SUCCESS
state=FINISHED
changeClusterOpMode()
ClusterCp=BC0
ClusterCp=BC1
ClusterCp=BC10
ClusterCp=BC11
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 37

ClusterCp=BC12
OmProfileManager=1
(CpCluster=1)>
2.13 Change OaM Profile

The OaM profile of the network element can be changed to a new profile value.
The action changeOmProfile under the MO OmProfileManager =1 allows
performing the change of OaM profile specifying the requested profile value as
input parameter. The default value of OaM profile is 100.
The CCF related to the requested OaM profile must be already imported as
described in Section 2.16 on page 39.
The Operational Instruction AP, Configuration Data in AP, Change, Reference

[1], describes the actions to be taken to change the OaM profile.
2.13.1 Example
This example shows how to change the OaM profile 100 to new profile 200:
>dn -m CpCluster
(CpCluster=1)>OmProfileManager=1
(OmProfileManager=1)>changeOmProfile --omProfileRequested 200
(OmProfileManager=1)>show
OmProfileManager=1
omProfile="PROFILE 200"
reportProgress
actionId=CHANGE_OM_PROFILE
result=SUCCESS
state=FINISHED
CcFileManager=1
OmProfile=100
(OmProfileManager=1)>
2.14 Remove OaM Profiles

All supported OaM profiles of the network element can be removed from CP
cluster. The action removeOmProfiles under the MO OmProfileManager =1
allows performing the removal of all supported OaM profiles.
38 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
2.14.1 Example
This example shows how to remove all supported OaM profiles:
>dn -m CpCluster
OmProfileManager=1
reportProgress
actionId=REMOVE_OM_PROFILES
result=SUCCESS
state=FINISHED
CcFileManager=1
OmProfile=100
2.15 Export CCF

The active CCF can be exported to APG file system into folder
/sw_package/CP/CCF. The action exportCcFile under the MO
OmProfileManager =1 allows performing the export of CCF.
2.15.1 Example
This example shows how to export the active CCF CXC1372200_PA100:
>dn -m CpCluster
(OmProfileManager=1)>exportCcFile
OmProfileManager=1
activeCcFile="CXC1372200_PA100"
reportProgress
actionId=EXPORT_CCF
result=SUCCESS
state=FINISHED
CcFileManager=1
OmProfile=100
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 39

2.16 Import CCF

Not active CCF can be imported from APG file system into folder
/sw_package/CP/CCF. The action importCcFile under the MO
CandidateCcFile =<candidateCcFileId> allows performing the import of CCF for
the OaM profile that can be activated.
After CCF imported, an active OmProfile MO with required profile and a not
active CcFile MO are created.
2.16.1 Example
This example shows how to import the CCF named MmlCommandRules_100.
xml for the OaM profile 100:
>dn -m CpCluster
(OmProfileManager=1)>importCcFile
(OmProfileManager=1)>CandidateCcFile=MmlCommandRules_100.xml
(CandidateCcFile=MmlCommandRules_100.xml)>show
CandidateCcFile=MmlCommandRules_100.xml
reportProgress
actionId=IMPORT_CCF
result=SUCCESS
state=FINISHED
CcFileManager=1
OmProfile=100
2.17 Activate CCF

Already imported CCF into the active OaM profile can be activated in the CP
cluster. The action activateCcFile under the MO OmProfileManager =1 allows
performing the activation of CCF previously imported (see Section 2.16 on
page 39).
2.17.1 Example
This example shows how to activate the CCF CXC1372200_PA100:
>dn -m CpCluster
40 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
(OmProfileManager=1)>activateCcFile
OmProfileManager=1
reportProgress
actionId=ACTIVATE_CCF
result=SUCCESS
state=FINISHED
CcFileManager=1
OmProfile=100
2.18 Rollback CCF

The backup CCF for the active OaM profile can be rolled back in the CP
cluster. The action rollbackCcFile under the MO OmProfileManager =1 allows
performing the rolling back of backup CCF.
Backup CCF must be already present into APG file system into folder
/sw_package/CP/CCF.
2.18.1 Example 39
This example shows how to roll back the backup CCF CXC1372200_PA100.
>dn -m CpCluster
(OmProfileManager=1)>rollbackCcFile
OmProfileManager=1
reportProgress
actionId=ROLLBACK_CCF
result=SUCCESS
state=FINISHED
CcFileManager=1
OmProfile=100
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 41

2.19 Enable LAG Function

LAG can be configured on the SCXB residing on the APZ magazine. LAG
consist of SCXB front ports GE1 and GE2. Enabling of front port LAG
functionality in SCX is provided by unlocking the administrativeState in Lag=1
MO.
2.19.1 Example
This example shows how to enable LAG on SCXB.
>dn -m HardwareMgmt
(HardwareMgmt=1)>Shelf=1.2.0.4,OtherBlade=0,Lag=1
(Lag=1)>configure
(config-Lag=1)>administrativeState=UNLOCKED
(config-Lag=1)>commit
(Lag=1)>
(Lag=1)>show
Lag=1
administrativeState=UNLOCKED
operationalState=ENABLED
(Lag=1)>
2.20 Disable LAG Function

LAG configuration can be brought down on the SCXB residing on the APZ
magazine. The SCX front port links GE1 and GE2 will work as two separate
links after disabling the LAG. Disabling of front port LAG functionality in SCX is
provided by locking the administrativeState in Lag=1 MO.
2.20.1 Example
This example shows how to disable LAG on SCXB.
>dn -m HardwareMgmt
(HardwareMgmt=1)>Shelf=1.2.0.4,OtherBlade=0,Lag=1
(Lag=1)>configure
(config-Lag=1)>administrativeState=LOCKED
(config-Lag=1)>commit
(Lag=1)>
(Lag=1)>show
Lag=1
operationalState=DISABLED
(Lag=1)>
42 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
2.21 Change APZ System

The APZ system type can be changed for all configured Dual-Sided CPs and
Single-Sided CPs.
For a Dual-Sided CP, the APZ system can be changed by setting the attribute
apzSystem in MOC DualSidedCp.
For a Single-Sided CP, the APZ system can be changed by setting the attribute
apzSystem in MOC ClusterCp.

This example shows how to change the APZ system of the Dual-Sided CP
CP1 to the value APZ21260.
>dn -m LogicalMgmt
LogicalMgmt=1
Apg=AP1
DualSidedCp=CP1
DualSidedCp=CP1
cpBladesDn
"ManagedElement=ITSAAP136,SystemFunctions=1,AxeFunctions=1,Sy
cpType=0
mauType=MAUB
(DualSidedCp=CP1)>configure
(config-DualSidedCp=CP1)>apzSystem=APZ21260
(config-DualSidedCp=CP1)>commit
DualSidedCp=CP1
cpBladesDn
cpType=0
mauType=MAUB
(DualSidedCp=CP1)>dn -m LogicalMgmt
LogicalMgmt=1
DualSidedCp=CP1
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 43

(config-DualSidedCp=CP1)>apzSystem=APZ21270
DualSidedCp=CP1
(DualSidedCp=CP1)>

This example shows how to change the APZ system of the Single-Sided CP
BC0 to the value APZ21403.
>dn -m LogicalMgmt
LogicalMgmt=1
Apg=AP1
CpCluster=1
(LogicalMgmt=1)> CpCluster=1
LogicalMgmt=1
Apg=AP1
CpCluster=1
DualSidedCp=CP1
(LogicalMgmt=1)> CpCluster=1
(CpCluster=1)>show
CpCluster=1
alarmMaster=1001
allBcGroup
"BC0"
"BC1"
"BC2"
"BC3"
"BC4"
"BC5"
clockMaster=1001
operativeGroup
"BC0"
"BC1"
"BC3"
"BC4"
reportProgress
ClusterCp=BC0
ClusterCp=BC1
ClusterCp=BC2
ClusterCp=BC3
ClusterCp=BC4
ClusterCp=BC5
44 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
OmProfileManager=1
(CpCluster=1)> ClusterCp=BC0
ClusterCp=BC0
cpBladesDn="ManagedElement=ITSAAP015,SystemFunctions=1,AxeFuncti
(ClusterCp=BC0)>configure
(config-ClusterCp=BC0)>apzSystem="APZ21403"
(config-ClusterCp=BC0)>commit
ClusterCp=BC0
cpBladesDn="ManagedElement=ITSAAP015,SystemFunctions=1,AxeFuncti
(ClusterCp=BC0)>
2.22 Change CP Type

The CP type can be changed for all configured Dual-Sided CPs and
Single-Sided CPs.
For a Dual-Sided CP, the CP type can be changed by setting the attribute
cpType in MOC DualSidedCp.
For a Single-Sided CP, the CP type can be changed by setting the attribute
cpType in MOC ClusterCp.
This example shows how to change the CP type of the Dual-Sided CP CP1 to
the value 21260.
>dn -m LogicalMgmt
LogicalMgmt=1
Apg=AP1
DualSidedCp=CP1
DualSidedCp=CP1
cpBladesDn
"ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=1,Syst
cpType=0
mauType=MAUB
(config-DualSidedCp=CP1)>cpType=21260
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 45

DualSidedCp=CP1
cpBladesDn
cpType=21260
mauType=MAUB
(DualSidedCp=CP1)>

This example shows how to change the CP type of the Single-Sided CP BC0 to
the value 21260.
>dn -m CpCluster
(CpCluster=1)>show
CpCluster=1
alarmMaster=1001
allBcGroup
"BC0"
"BC1"
"BC2"
"BC3"
"BC4"
"BC5"
clockMaster=1001
operativeGroup
"BC0"
"BC1"
"BC3"
"BC4"
reportProgress
ClusterCp=BC0
ClusterCp=BC1
ClusterCp=BC2
ClusterCp=BC3
ClusterCp=BC4
ClusterCp=BC5
OmProfileManager=1
(CpCluster=1)>ClusterCp=BC0
ClusterCp=BC0
cpBladesDn="ManagedElement=CEMSS07,SystemFunctions=1,AxeFunctions=
46 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
(ClusterCp=BC0)>configure
(config-ClusterCp=BC0)>cpType="21260"
(config-ClusterCp=BC0)>commit
ClusterCp=BC0
cpBladesDn="ManagedElement=CEMSS07,SystemFunctions=1,AxeFunction
cpType=21260
(ClusterCp=BC0)>
2.23 Administration of MAUS

MAUS function on APG can be started or stopped. This can be used to repair
MAUS when CP fault occurs.
To start or stop MAUS, the attribute administrativeState in MO SwMau=1 should

be set to UNLOCKED or LOCKED; respectively.
2.23.1 Example
This example shows how to stop and start MAUS function on APG.
MAUS function can be stopped by setting administrativeState to LOCKED.
>dn -m LogicalMgmt
(DualSidedCp=CP1)SwMau=1
(SwMau=1)>configure
(config-SwMau=1)>administrativeState=LOCKED
(config-SwMau=1)>commit
(SwMau=1)>
(SwMau=1)>show
SwMau=1
administrativeState=LOCKED
operationalState=DISABLED
(SwMau=1)>
MAUS function can be started by setting administrativeState to UNLOCKED.
(SwMau=1)>configure
(config-SwMau=1)>administrativeState=UNLOCKED
(config-SwMau=1)>commit
(SwMau=1)>
(SwMau=1)>show
SwMau=1
administrativeState=UNLOCKED
operationalState=ENABLED
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 47

(SwMau=1)>
2.24 Actions on Alarms
2.24.1 AP-DMXC LINK

Alarm Class = A1.
The alarm AP FAULT with problem text AP-DMXC LINK is raised when the
communication between the AP and the Blade System Platform (BSP) Switch
is not working.
The Operational Instruction AP FAULT, Reference [2], describes the actions to

be taken when the alarm is received.
2.24.2 AP-SWITCH SNMP LINK

The Simple Network Management Protocol (SNMP) communication between
the AP and the SCB-RP or SCX boards in slot 0/25 is not working.
In case of SNMP communication issues:
Alarm Class = A2.
The alarm AP FAULT with problem text AP-SWITCH SNMP LINK is raised
when the SNMP communication between the AP and at least one switch (SCX
or SCB-RP) board in a magazine is not working.
Alarm Class = A1.
The alarm AP FAULT with problem text AP-SWITCH SNMP LINK is raised
when the SNMP communication between the AP and both switch (SCX or
SCB-RP) boards in at least one magazine is not working.

2.24.3 BACKPLANE MALFUNCTION

Alarm Class = A1.
The alarm AP FAULT with problem text BACKPLANE MALFUNCTION is raised

when the communication on faster internal backplane is not working in a BSP
configuration.

48 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use
2.24.4 BOARD FAULTY

Alarm Class = A2.
The alarm AP FAULT with problem text BOARD FAULTY is raised when one of
the AP boards configured in the HWC table is faulty. The AP board is reported
faulty by other function.

2.24.5 BOARD MISSING

Alarm Class = A2.
The alarm AP FAULT with problem text BOARD MISSING is raised when one of
the AP boards configured in the HWC table is missing. The AP board is missing.

2.24.6 DISK FAULTY

Alarm Class = A2.
The alarm AP FAULT with problem text DISK FAULTY is raised when one of
the data disks is faulty. It is applicable only for APG having data disks onto
the same processor board.

2.24.7 DISK REPLICATION

Alarm Class = A2.
The alarm AP FAULT with problem text DISK REPLICATION is raised when
the control node pair has been operating in a non-redundant mode for more
than 20 minutes. Control nodes have lost connection to each other or the data
is not consistent.

2.24.8 DISK CABLES MAY BE NOT CONNECTED PROPERLY
Alarm Class = A2.
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 49

The alarm AP FAULT with problem text DISK CABLES MAY BE NOT
CONNECTED PROPERLY is raised when one of the APG data disks may be
not connected properly.

2.24.9 INFRASTRUCTURE LINK AGGREGATION FAULT

Alarm Class = A2.
The alarm INFRASTRUCTURE LINK AGGREGATION FAULT is raised when

SCXB front port(s) is either not connected properly to External Switch or the
cable/ports are not functioning properly.
The Operational Instruction INFRASTRUCTURE LINK AGGREGATION

FAULT, Reference [7], describes the actions to be taken when the alarm is
received.
2.24.10 MIRRORED DISKS NOT REDUNDANT

Alarm Class = A2.
The alarm AP FAULT with problem text MIRRORED DISKS NOT REDUNDANT
is raised when one of the mirrored disks on the AP is not mirrored properly.
The disk mirroring is not working properly.

2.24.11 NIC NOT CONNECTED

Alarm Class = A3.
The alarm AP FAULT with problem text NIC NOT CONNECTED is raised when
one of the NIC is not connected properly.

2.24.12 THUMBDRIVE MALFUNCTION
Alarm Class = A2.
The alarm AP FAULT with problem text THUMBDRIVE MALFUNCTION is raised

when thumb drive is either not connected to AP board or the device is not
functioning properly.
50 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

How to Use

1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 51

52 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

Configuration
3 Configuration
3.1 First Installation of CCF

It is valid for a Multi-CP system only.
Intention of this chapter is to show how to install CCF at the first time.
Prerequisite is to have a CCF with profile equal to 100 in APG file
system into folder /sw_package/CP/CCF and with the filename equal to
MmlCommandRules_100.xml.
Note: At first installation the attribute omProfile is equal to PROFILE 100.
The first installation consists of following actions:
• Import the above-mentioned CCF as described in Section 2.16 on page 39
• Set the attribute scope in MO OmProfileManager=1 equal to ONLY_APG
• Activate the imported CCF as described in Section 2.17 on page 40.
Note: At the end of first installation, an active CCF is created in the active
OaM profile with profile 100.
3.1.1 Example 47
Once CCF is imported this is how the MO OmProfile=100 is displayed:
>dn -m CpCluster
(CpCluster=1)>OmProfileManager=1,OmProfile=100
(OmProfile=100)>show
OmProfile=100
aptProfile="100"
apzProfile="100"
state=ACTIVE
CcFile=CXC1372200_PA100
(OmProfile=100)>
This is how the MO CcfFile=CXC1372200_PA100 is displayed:
(OmProfile=100)>CcFile=CXC1372200_PA100
(CcFile=CXC1372200_PA100)>show
rulesVersion="APZP19.0_LSV14_MSCR141_CM202_2011-11-17_092011"
state=NOT_ACTIVE
(CcFile=CXC1372200_PA100)>
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 53

Note: CCF identity consists of a document number and a revision as specified

in the XML file.
Once the CCF is activated this is how the MO OmProfileManager=1 is

displayed:
>dn -m CpCluster
OmProfileManager=1
reportProgress
actionId=ACTIVATE_CCF
result=SUCCESS
state=FINISHED
CcFileManager=1
OmProfile=100
This is how the MO OmProfile=100 is displayed:
(OmProfileManager=1)>OmProfile=100
(OmProfile=100)>show
OmProfile=100
aptProfile="100"
apzProfile="100"
state=ACTIVE
(OmProfile=100)>
This is how the MO CcfFile=CXC1372200_PA100 is displayed:
(OmProfile=100)>CcFile=CXC1372200_PA100
(CcFile=CXC1372200_PA100)>show
rulesVersion="APZP19.0_LSV14_MSCR141_CM202_2011-11-17_092011"
state=ACTIVE
(CcFile=CXC1372200_PA100)>
54 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

Glossary
Glossary
AP GESB
Adjunct Processor Gigabit Ethernet Switch Board
APG HW
Adjunct Processor Group Hardware
APUB HWC
Adjunct Processor Unit Board Hardware Configuration
BSP IP
Blade Server Platform Internet Protocol
CCF IPLB
Command Classification File Integrated Protocol Load Balancer
CMXB IPTB
Component Main Switch Board Integrated Protocol Tracer Board
CP LAG
Central Processor Link Aggregation Group
CPUB LED
Central Processor Unit Board Light Emitting Diode
DMXC MAU
Distributed Main Switch Controller Maintenance Unit
DVD MAUB
Digital Versatile Disk Maintenance Unit Board
EGEM MAUS
Enhanced Generic Ericsson Magazine MAU Software
EGEM2 MIA
Enhanced Generic Ericsson Magazine, type 2 Manual Intervention Allowed
EPB1 MML
Evo Processing Board 1 Man-Machine Language
EvoET MO
Evo Exchange Terminal Managed Object
GE MOC
Gigabit Ethernet Managed Object Class
GEA MOM
Generic Ericsson Alarm board Managed Object Model
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 55

NIC
Network Interface Card
OaM
Operation and Maintenance
RPBI-S
Regional Processor Bus Interface, Serial
RPH
Regional Processor Handler
RPIO2
Regional Processor Input/Output - 2
RPIRS
Regional Processor Interface, Receiver, and
Sender
SCB-RP
System Control Board - Regional Processor
SCXB
System Control Switch Board
SNMP
Simple Network Management Protocol
SW
Software
VLAN
Virtual Local Area Network
XML
Extensible Markup Language
56 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

Reference List
Reference List
[1] AP, Configuration Data in AP, Change

OPERATIONAL INSTRUCTION
[2] AP FAULT
[3] AXE Functions Management

USER GUIDE
[4] CP FAULT
[5] Ericsson Command-Line Interface

USER GUIDE
[6] How to Access an AXE

USER GUIDE
[7] INFRASTRUCTURE LINK AGGREGATION FAULT

[8] Managed Element Management

USER GUIDE
[9] Managed Object Model

USER GUIDE
[10] User Management

USER GUIDE
1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 57

AXE Equipment Management: User Guide

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

AXE Equipment Management: User Guide

Transféré par

Droits d'auteur :

Formats disponibles

AXE Equipment Management

1/1553-CXA 117 0046/5-V3 Uen C

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

This document describes the AXE Equipment Management function for

1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

1.1 Revision Information

Blade Server Platform

Classic CP A Central Processor (CP) blade that belongs to

Cluster CP A CP that is a member of a CP Cluster.

Command Classification File

1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 1

CP blade A CP blade is any board, such as Central Processor

CP Cluster A set of cluster CPs that provides CP functionality. It is

Cluster Operation Mode

• Normal Mode is intended for regular OaM activities

• The Expert Mode is reserved for advanced cluster

Dual-Sided CP A 1+1 redundant CP (A+B side). Such CP consists also

OaM Profile A Network Element property defining the functional level

Non-Classic CP CpBlade that belongs to APZ21255 and later HW

2 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

Shelf A shelf represents a specific magazine or subrack in

a - Address plug 0 (Integer 0-15)

b - Address plug 1 (Integer 0-15)

c - Address plug 2. Is always zero (Integer 0-15)

d - Address plug 3 (Integer 0-15)

Single-Sided CP A Cluster CP without redundancy on a CP board level.

SW MAU The SW emulation of CP MAU is responsible for

SW MAU is referred to as MAUS.

• AXE Functions Management, Reference [3]

• Ericsson Command-Line Interface, Reference [5]

• How to Access an AXE, Reference [6]

1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 3

• Managed Element Management, Reference [8]

• Managed Object Model, Reference [9]

• User Management, Reference [10]

The function allows:

• Listing the status and properties of a blade

• Changing the Cluster Operation Mode

• Changing OaM profile

• Removing OaM profiles

• Rolling back a CCF

• Enabling LAG Function

• Disabling LAG Function

• Changing the CP type.

• Changing the state of SW MAU.

As soon as a blade is defined and powered on an IP address is automatically

4 1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05

The AXE Equipment Management function is provided through a Managed

Figure 1 AXE Equipment Management Function MOM

SystemComponentHandling is the root MOC for the System Component

MOC HardwareMgmt represents the HW view of the configured boards. Only

MOC Shelf represents a magazine containing several blades.

MOC ApBlade represents a hardware blade that is part of an AP node and

MOC OtherBlade represents a blade which is not a CP/AP blade.

MOC CpBlade represents a hardware blade that is part of a CP and contains

1/1553-CXA 117 0046/5-V3 Uen C | 2016-10-05 5

MOC ApBladeInfo specifies the information of an ApBlade. All attributes of this

MOC DualSidedCp represents a Dual-Sided CP consisting of two CP blades

MOC SwMau represents the SW emulation of CP MAU. It is system instantiated

CpCluster represents a cluster system that provides CP functionality. It is

MOC ClusterCp represents a Single-Sided CP (Cluster CP) regardless the