04 OS90524EN15GLA0 Connecting The Core Network

Connecting the Core Network
Contents
1 NE3S/WS SBM 3
1.1 NE3S/WS Mediation 4
1.2 Supported Network Elements 6
1.3 NE3S / WS Implementation 9
1.4 Managing the NE3S/WS Connectivity 16
1.5 Log files and trace 18
2 SNMP and NE3S/SNMP SBM 21
2.1 SNMP Overview 22
2.3 SNMP and NE3S/SNMP Southbound Mediations 28
3 XML over HTTP (XoM) SBM 33
3.1 XoH Overview 34
3.3 XoH Data Flow 39
3.4 Managing XoH SBM 47
3.5 Logging and Tracing 48
4 NX2S SBM 49
4.1 NX2S (NE3S/FTP) Mediation 50
4.2 XoH Data Flow 52
4.3 Troubleshooting NX2S SBI 56
4.4 Log Files and Tracing 58
5 Exercises 61
OS90524EN15GLA0
© Nokia Solutions and Networks 2015.
.
zzz 1
OS90524EN15GLA0
2 © Nokia Solutions and Networks 2015.

1 NE3S/WS SBM
OS90524EN15GLA0
.
zzz 3
1.1 NE3S/WS Mediation

NE3S/WS South Mediation mediates management operations and notifications between
Network Management / Element management applications and Network Elements. The O&M
Agent implements the NE3S/WS protocol on the Network element and exposes standard
management interfaces for Network Management /Element Management systems.
NE3S/WS South Mediation is integrated with the O&M agent through NE3S/WS protocol and
enables integration for higher management systems in managing different network elements.
TIP
NE3S/WS is an interface suite based on Web Service technologies, most
importantly based in the SOAP messaging.
SOAP, originally defined as Simple Object Access Protocol, is a protocol specification for
exchanging structured information in the implementation of Web Services in computer
networks. It relies on XML (Extensible Markup Language) for its message format, and usually
relies on other Application Layer protocols, most notably HTTP or SMTP, for message
negotiation and transmission
NE3S/WS is Nokia Solutions and Networks' proprietary interface for several management
fragments:
 FM - Fault Management
 CM - Configuration Management
 PM - Performance Management (Administration of Measurements)
 ATL - Audit Trail
 SLT - System Level Trace / Subscriber and Equipment Trace
OS90524EN15GLA0

NE3S/WS SBM
NetAct Network Element
Mediation Fragment
Application 1
Fragment
Application 2
NE3S/WS Agent
NE3S/WS Manager TCP/IP COMA
Fragment
Application 3
Fragment
Application n
1 © Nokia Solutions and Networks 2015
Fig. 1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
OS90524EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. Solutions
© Nokia . . and. Networks
. . .2015.. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zzz. . . . . . . . 5
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Supported Network Elements

Supported Network elements and versions in NetAct 15 are listed below.
NE Type Versions Function Support
CAM 15.0 FM, PM Support
MGW U5.0 EP2 U6.0 Support
Open MGW Ui5.0 , Ui5.0 EP1 , Ui5.0 EP2 , Ui5.0 EP3 Support
Flexi NS – SGSN SG8.0 ATCA , SG8.0 ATCA CD2, SG8.0

Support
ATCA ATCA CD3 , SG8.0 ATCA CD4
SG8.0 DX CD2 , SG8.0 DX CD3 ,SG8.0

Flexi NS – SGSN DX Support
DX CD3.1
Flexi NS (Combined
NS3.0 ,NS4.0 Support
SGSN/MME)
Flexi NG Flexi NG2.0 , Flexi NG2.1 , Flexi NG3.1, Support

Flexi NG3.2
One-NDS One-NDS 8 MP8 , One-NDS 9 Base, One- Support
NDS 9 SP1 , One-NDS 9 SP2
NT HLR FE 5.0 SP2 , NT HLR FE 5.0 SP3,
NT HLR FE 5.0 SP4, NT HLR FE 6.0 SP1,
NT HLR FE NT HLR FE 6.0 SP2, NT HLR FE 6.0 SP3, Support
NT HLR FE 6.0 SP4, NT HLR FE 7.0 ,
NT HLR FE 7.0 SP1
One-MNP One-MNP8.0 SP6 ,One-MNP9.0 FM, PM Support
One-EIR One-EIR 4.0 SP1 , One-EIR 5.0 , One-EIR FM, PM Support

5.0 SP1 , One-EIR 5.2
MGW U5.0 EP2 U6.0 Support
Open MGW Ui5.0 , Ui5.0 EP1 , Ui5.0 EP2 , Ui5.0 EP3 Support
Flexi NS – SGSN SG8.0 ATCA , SG8.0 ATCA CD2, SG8.0

Support
ATCA ATCA CD3 , SG8.0 ATCA CD4
SG8.0 DX CD2 , SG8.0 DX CD3 ,SG8.0

Flexi NS – SGSN DX Support
DX CD3.1
Flexi NS (Combined
NS3.0 ,NS4.0 Support
SGSN/MME)
Flexi NG Flexi NG2.0 , Flexi NG2.1 , Flexi NG3.1, Support

Flexi NG3.2
OS90524EN15GLA0

One-NDS One-NDS 8 MP8 , One-NDS 9 Base, One- Support

NDS 9 SP1 , One-NDS 9 SP2
NT HLR FE 5.0 SP2 , NT HLR FE 5.0 SP3,
NT HLR FE 5.0 SP4, NT HLR FE 6.0 SP1,
NT HLR FE NT HLR FE 6.0 SP2, NT HLR FE 6.0 SP3, Support
NT HLR FE 6.0 SP4, NT HLR FE 7.0 ,
NT HLR FE 7.0 SP1
One-MNP One-MNP8.0 SP6 ,One-MNP9.0 FM, PM Support
One-EIR One-EIR 4.0 SP1 , One-EIR 5.0 , One-EIR FM, PM Support

5.0 SP1 , One-EIR 5.2
One AAA One-AAA 6.0 SP1, One-AAA 7 FM, PM Support
CMD 4.0 FM, PM Support
Flexi CMD5.0 , Flexi CMD5.1 , Flexi Support

Flexi CMD
CMD5.2
DXA 3.2 FM, PM Support
SBC SD 6.2 4250/4500/3820 FM, PM support
SBC SD SBC SD 6.3 4500/3820
SBC SD 6.4 4500/3820
SBC BG 6.2 4500 FM, PM support
BG 4500 SBC BG 6.3 4500
SBC BG 6.4 4500
BGF BGF 6.5 4250/4500 FM, PM support
EMC R14, R19 FM Support
iNUM 9.0 , iNUM 10.0 , iNUM 11.0 , iNUM FM, PM Support

iNUM 6.1
11.0 VI
IPSW (Cisco) IOS12.x , IOS15.x FM, PM Support
RTR (Cisco) IOS12.x , IOS15.x FM, PM Support
SAM Server 4.20. FM, PM Support
nSignia nSignia 2.8.4 FM, PM Support
Movius Mereon 4.1 Support
OS90524EN15GLA0
.
zzz 7

IMS CMS-8200 (HSS- 8.2 EP2, 8.2EP3, 8.2EP4, 9.1, 9.2, 10, Support
FE) 10.1, 11.0, 11.0 VI
IMS CFX-5000 (CSCF) 8.2EP2, 9.1, 9.2, 10, 10.1, 11.0, 11.0 VI Support
IMS CMS-8200 (HSS- Support

8.2
FE, SLF, DRA)
IMS CMS-8200 (HSS- Support
8.2EP4, 10.0, 10.1, 11.0, 11.0 VI
FE, DRA)
PCS-5000 v6.2 (ATCA only) FM, PM Support
PCS-5000
PCS-5000 v6.3
iNMC / iSMC V14 Support
Convedia CMS-3000 v3.16 FM, PM Support
Convedia CMS-9000 v3.16 FM, PM Support
hiG1800 V7.2, V8.1 FM, PM Support
Load Balancer F5 BIG- FM, PM Support

-
IP 6400, 6900
For detailed information, please check the latest Compatibility Matrix file
OS90524EN15GLA0

1.3 NE3S / WS Implementation
1.3.1 FM Data Flow

The FM notification flow starts when the registered agents send a SOAP message to NetAct.
After load balancing provided by the lb-unify service, the relevant NSN-common_mediation
ServiceMix instance has the service available in the Protocol Manager component.
The SOAP message is forwarded to the Notification Manager. The Notification Manager
identifies the notification type and decides the needed actions. The Enhancer gets the
credentials using NCA (Network Credential Access).
The Data Transformation Component transforms the alarm data to SQL insert XML format
and forwards the data to the DB via the interface.
The Alarm operation flow follows same structure, where Application is sending basic
operation request as a file to the Service Mix instance component. Request goes to the
network element after credential retrieve. The Operation response from network element is
collected by the service mix instance and then forwarded to the application using File SMI.
OS90524EN15GLA0
.
zzz 9
NE3S/WS SBM
Implementation: Data Flow - FM
DB SMI FM DB
ServiceMix
Interface to GEP
notification-manager
other components (fm processing
subsystem)
Protocol manager credentials

Data transformations
File SMI
NE / Agent
SMI: South Mediation Interface
Fig. 2
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OS90524EN15GLA0
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia
. .Solutions
. .and .Networks
. .2015.
10
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2 PM Data Flow

The Measurement schedule defines the time frames during which measurement data is
collected by the agent. It also defines the measurement type and objects for the
measurement. The Measurement type is a group of performance indicators and object
classes which define target for measurement.
TIP
The Administration of measurements (AoM) application is used to activate the
measurements in the Network Elements.
The following list contains the basic scenarios in performance management:

1. New measurement job is activated by the manager.
2. The agent starts to collect measurement data according to the measurement schedule
plan.
3. Measurement results are sent to the manager in OMeS files by the agent.
The Measurement data is received as notifications to the mediation. The Notification is sent
to file writing. Transformation is not needed. Measurement Data is written to SMI as OMeS
files. Files are then ready for PM component in PM Platform to read them.
TIP
The PM data is transferred to
/var/opt/nokia/oss/global/mediation/south/pm/import
OS90524EN15GLA0
.
zzz 11
NE3S/WS SBM
Implementation: Data Flow - PM Scenario
AoM
1) Create and activate

measurement job
2) Agent starts
Manager Agent
to collect
measurement
data
3) Measurement data
In OMeS file
Fig. 3
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OS90524EN15GLA0
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia
. Solutions
. . .and .Networks
. .2015.
12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
NE3S/WS SBM
Implementation: Data Flow - PM
Common mediations
ServiceMix
Notification manager
Interface to Other
Protocol Manager Components PM File SMI
NE / Agent
The PM data is transferred to

/var/opt/nokia/oss/global/mediation/south/pm/import
Fig. 4
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90524EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
zzz
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.3 CM Data Flow

CM upload request can be initiated from Monitor application by requesting topology upload
from elements.
This request is sent to the mediation. The service mix instance receives the request message
and sends request to enhancer to get credentials from NCA. The Request is sent to Protocol
Manager which forms the SOAP request and sends it to NE/agent.
The upload type is bulk, meaning that all objects from network element are retrieved. The
response(s) are received by Service mix and forwarded to the interface to external
components. Finally the Monitor application gets the response and constructs the object tree
in the application. The topology is updated.
OS90524EN15GLA0

NE3S/WS SBM
Implementation: Data Flow - CM
Common mediation
ServiceMix
cm upload request
Notifications manager Interface to other
Components Monitor
Protocol Manager async upload response

Credential
Bulk cm upload
cm upload response
NE / Agent
Fig. 5
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90524EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
zzz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Managing the NE3S/WS Connectivity

1.4.1 Managing the ServiceMix process
Using smanager:
[root]# /opt/cpf/bin/smanager.pl stop service
common_mediations-<vm node name>
OS90524EN15GLA0

NE3S/WS SBM
Managing the connectivity: smanager.pl – example for Mainstream deployment
n83-vm16
netfs-n83-vm16 started standAlone
cpfnx2s-n83-vm16 started standAlone Common mediations
OMAgentAF-n83-vm16 started standAlone service also handles
ssh-n83-vm16 started (u) standAlone the 3gppp SBI
ntp-n83-vm16 started (u) standAlone connectivity
common_mediations-n83-vm16 started standAlone
httpd-n83-vm16 started standAlone
pingServer-n83-vm16 started standAlone
PasswordChangeWS-n83-vm16 started standAlone
tnameserver-n83-vm16 started standAlone
DNS-Slave started (u) standAlone
n83-vm17
cpfnx2s-n83-vm17 started standAlone
OMAgentAF-n83-vm17 started standAlone
ssh-n83-vm17 started (u) standAlone
ntp-n83-vm17 started (u) standAlone
common_mediations-n83-vm17 started standAlone
httpd-n83-vm17 started standAlone
Fig. 6
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
OS90524EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Solutions
. . .2015.. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
zzz
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Log files and trace

1.5.1 Logging configuration
/opt/oss/NSN-common_mediations/smx/conf/log4j.xml
1.5.2 /var/opt/oss/log/common_mediations
oss_activity0_0.log Common activity log
oss_error0_0.log Common error log
oss_trace0_0.log Trace log
persistence.log Data Cache debug
In the following, there are Operation examples extracted from the log files located in
var/opt/oss/log/common_mediations/oss_activity0_*.log/
1. Executing the operation upload for agent 10.8.83.152 operation id

:: A.cmb.gxiol4a1-2l session id :: 1326790132104
Upload operation request being processed
2. Triggered the operation upload successfully for agent 10.8.83.152

user ::wsuser password :: ***** ne3sws endpoint
::http://10.8.83.152:8080/NE3S/1.0/NE3SBulkOperationsService
operation id :: G.cmb.gxc9og67-4s time taken (in ms) :: 166.
waiting for response from Agent
Upload operation request sent to network element successful
3. Response received from agent 12345000000043231 mainhost ::

10.8.83.152 for operation A.cmb.gxiol4a1-2l page no 1 content
type ocos completed false attachment cid
reportOperationStatusContent1326790176780@nokiasiemens.com
attachment javax.activation.DataHandler@6c4d0e2e
Upload response with OCoS attachment received. Upload Completion
status is false.
4. Response received from agent 12345000000043231 mainhost ::

10.8.83.152 for operation A.cmb.gxiol4a1-2l page no 2 content
type feedback completed true attachment cid
reportOperationStatusContent1326790177485@nokiasiemens.com
attachment javax.activation.DataHandler@737bac2
Upload response with feedback attachment received. Upload
Completion status is true
OS90524EN15GLA0

5. Completed the operation successfully for agent id

12345000000043231 mainhost :: 10.8.83.152for operation id ::
A.cmb.gxiol4a1-2l
Upload operation completed successfully
6. Notification processed successfully for agent ::

12345000000645520 mainhost :: scv51lab20rep.netact.noklab.net for
queueId common_changeNotificationQueue sequenceNumber 38073
content type ocos notificationType ne3s_common_changeNotification
attachment cid
transferNotificationContent1327966613234@nokiasiemens.com
CM notification received from agent
OS90524EN15GLA0
.
zzz 19
OS90524EN15GLA0

2 SNMP and NE3S/SNMP SBM
OS90524EN15GLA0
.
zzz 21
2.1 SNMP Overview

The Simple Network Management Protocol (SNMP) is a well-supported standard that can be
used to monitor and control devices. Many SNMP devices provide both general network
management and device management through a serial cable, modem, or over the network
from a remote computer. It involves a primary management station communicating with
different management processes.
The figure in next page shows an outline of an SNMP-based system. An SNMP agent runs
the SNMP management software. An SNMP server sends commands to the agent which
responses back with the results.
The SNMP protocol is initially based on the RFC1157 document. It defines a simple protocol
that gives a management information base (MIB) to the network element.
SNMP is a very simple protocol, but suffers from the fact that it is based on connectionless,
unreliable UDP. Therefore, NSN has developed on top of the basic SNMP a NE3S interface
that brings reliability to the SNMP managed objects. The two main versions of SNMP are
SNMP Ver1 and SNMP Ver2. SNMP has added security to stop intruders determining
network loading or the state of the network.
OS90524EN15GLA0

SNMP SBM
SNMP Overview
• SNMP stands for Simple Network Management Protocol.

• SNMP requires only a couple of basic components to work: a
management station and an agent
SNMP Agents
on Port 161/162
Agents
Fig. 7
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
OS90524EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Solutions
. . .2015.. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
zzz
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 MIB Structure

To be able to receive information from a managed system, the information has to be defined
in a well-known structure. The structure of the management information as used by SNMP is
specified in RFC 1155 (Structure and Identification of Management Information for TCP/IP-
based Internets). The document describes a general framework for definition of Management
Information Bases (MIB).
The MIB defines the information SNMP can attain from a network element in a tree-like
structure. Top of the tree is the most general information available about a network. Every
branch of the tree becomes more detailed focusing on a specific network area, with the
leaves of the tree holding the most specific information. Each resource to be managed is
represented by an object. This is not a NSN NetAct managed object; it is rather a variable
that is read of set.
A fully qualified MIB object ID is given in 'dot notation':
.1.3.6.1.2.1.1.1 or .iso.org.dod.internet.mgmt.mib-2.system.sysDescr
Both notations describe the same object ('sysDescr') of the MIB.
In addition to the Internet-standard MIB-II objects (RFC 1213), many hardware vendors have
developed MIB extensions. These MIB extensions are part of the enterprise branch of the
MIB tree. For example, the path to the Nokia specified MIB is: .1.3.6.1.4.1.94
On the Internet several sources for vendor-specific MIBs exist. A good starting point for
searching MIBs is www.simpleweb.org.
OS90524EN15GLA0

SNMP SBM
SNMP Overview: MIB Structure
root (.)
ccitt (0) iso (1) joint (2)
standard (0) reg-authority (1)member-bocy (2) indent-org (3)
dod (6)
interner (1)
directory (1) mgmt (2) experimental (3) private (4)
mib (1) enterprises (1)
system (1) interfaces (2) at (3) ip (4) icmp (5) snmp (11)
hp (11) nokia (94)
sysDescr (1)
Fig. 8
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90524EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
© Nokia
. Solutions
. . and. Networks
. . .2015.. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
zzz
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

NE Domain NE Name NE version FM PM EM Launch
DCN backbone BIG-IP BIG-IP 6400, 6900 NE3S/SNMP SNMP v2 HTTPS, SSH
Cisco Router (any

DCN backbone Cisco Router version) SNMP v2c SNMP v2c Telnet
Cisco Switch (any

DCN backbone Cisco Switch version) SNMP v2c SNMP v2c Telnet
DCN backbone Juniper EX Juniper EX 3200 SNMP, SSH SNMP v2c J-web
Fixed-Mobile Movius Mereon 6000

Convergence Media Server M6MS 4.1 SNMP SNMP SSH
Fixed-Mobile Session Border SBC SD 6.2, BG 6.2

Convergence Controller and BGF 6.5 SNMP v2c SNMP v2c HTTP, SSH
Charge AtOnce
Mobile Voice Mediate CMD 4.0 SNMP SNMP, FTP SSH
intelligent Gateway
Mobile Location NE3S/SNMP,
Positioning Center iGMLC 6.0 NE3S/SNMP FTP HTTPS
Subscriber Data
Management EMC CX4-120 EMC CX4-120 SNMP v1) No HTTP
Subscriber Data IBM BladeCenter IBM BladeCenter

Management LS42 blades LS42 blades SNMP v1) No HTTP, SSH
Subscriber Data IBM BladeCenter IBM BladeCenter

Management HS22 blades HS22 blades SNMP v1) No HTTP, SSH
Subscriber Data IBM BladeCenter HT IBM BladeCenter

Management Chassis HT Chassis SNMP v1) No HTTP, SSH
Subscriber Data IBM BladeCenter H IBM BladeCenter H

Management Chassis Chassis SNMP v1) No HTTP, SSH
Subscriber Data One-EIR 4.0, 5.0,

Management One-EIR 5.0 EP1 NE3S/SNMP NE3S/SNMP SSH
OS90524EN15GLA0

NE Domain NE Name NE version FM PM EM Launch
Subscriber Data One-MNP 8.0 SP6,

Management One-MNP 9.0 NE3S/SNMP NE3S/SNMP SSH
RadiSys
Voice over IP CMS3000/9000 CMS3000/9000
(under FMC) MediaServer v3.16 SNMP SNMP HTTP, SSH
Voice over IP SNMP, Telnet,

(under FMC) hiG1800 hiG1800 V8.2/V7.2 SSH SFTP SSH, Telnet
Voice over IP hiQ8000/4200

(under FMC) hiQ8000/4200 R14.1 SNMP SNMP, FTP HTTP)
Voice over IP
(under FMC) hiQ4300 hiQ4300 R14.1 SNMP N/A HTTPS, SSH
Voice over IP intelligent Number NE3S/SNMP,

(under FMC) Mapping iNUM v9.0, 10 NE3S/SNMP FTP HTTP, SSH
NE3S/SNMP,
SADM SADM 9.0 NE3S/SNMP HTTP, SSH
FTP
RACS RACS/COD LA15 SNMP SNMP SSH
RACS RACS-C 1.0, 2.0 SNMP SNMP SSH
RACS RACS-T LA15 SNMP SNMP SSH
TRAFFICA Nelmon NM3.0 SNMP -- SSH
For detailed information, please check the latest Compatibility Matrix file
OS90524EN15GLA0
.
zzz 27
2.3 SNMP and NE3S/SNMP Southbound Mediations

2.3.1 SNMP Mediation
The SNMP southbound interface is used for integrating Nokia Solutions and Networks
network elements, element management systems or multivendor tools to NetAct using the
SNMP mediation. The SNMP SBI supports:
 basic configuration management (topology)
 fault management
 performance management
2.3.2 NE3S/SNMP Mediation

The NE3S/SNMP southbound interface is a proprietary interface used for integrating
networks elements and element managers to NetAct using the NE3S/SNMP mediation. It
supports:
 Administration of Measurements
In NE3S SNMP FM, alarms are transmitted as SNMP traps. In addition to traps that follow
NE3S MIB conventions, the NE3S compliant agent can also send the following MIB-II traps:
 EGB neighbor loss
 authentication failure
 link up
 link down
 cold start
 warm start.
OS90524EN15GLA0

2.3.3 Load Balancing

NetAct receives notification from Elements through load balancing. Load balancer is
configured to forward ports to specific receivers at mediation layer. Different ports are used to
the specific mediations SNMP and NE3S/SNMP.
NE3S/SNMP and plain SNMP mediations are built as EJB application and run in WAS:
OS90524EN15GLA0
.
zzz 29
SNMP and NE3S/SNMP SBM

Implementation: Load balancing
WAS
VM11/
VM06
Load Balancers
Load Balancers
NE3S/SNMP SNMP
Fig. 9
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OS90524EN15GLA0
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia
. .Solutions
. .and .Networks
. .2015.
30
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.4 Managing SNMP and NE3S/SNMP Mediations

SNMP and NE3S/SNMP interfaces are deployed in the WebSphere Application Server virtual
machines as applications:
In the case of SNMP, the WAS related applications are:
 FM_SNMP_Deployment_Controller
 FM_SNMP_Mediation
 PM_SNMP_Deployment_Controller
 PM_SNMP_Mediation
In the case of NE3S/SNMP, the WAS related applications are:

 FM_NE3S_Mediation application
 PM_NE3S_Mediation application
 NE3SWS_Deployment_Controller
OS90524EN15GLA0
.
zzz 31
SNMP SBM
SNMP and NE3S/SNMP Mediations in WAS
To manage SNMP and

NE3S/SNMP mediations use
the WebSphere Application
Server Console or the WAS
scripts
Fig. 10
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OS90524EN15GLA0
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia
. Solutions
. . .and .Networks
. .2015.
32
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3 XML over HTTP (XoM) SBM
OS90524EN15GLA0
.
zzz 33
3.1 XoH Overview

XoH (XML over HTTP) is a Standard open interface that uses XML as data encoding and
HTTP/HTTPs as the transfer protocol. XoH uses Simple Object Access Protocol (SOAP) in
operations requested by NMSs from network element or element management subsystem. It
supports the following functions:
 system level trace management
 License Management
 Software Management
 NEAC
 Network Element Backup and Restore
 Audit Trail
OS90524EN15GLA0

XoH SBM
Overview
XoH (XML over HTTP) is a Standard open

interface that uses XML as data encoding
and HTTP/HTTPs as the transfer protocol.
XoH uses Simple Object Access Protocol
(SOAP) in operations requested by NMSs
from network element or element Web Services Client Web Client
management subsystem. It supports the
following functions in NetAct:
SOAP, WDSL, XML/HTTP
XML/HTTP
● fault management
● performance management Web Services
● system level trace management
● License Management
● Software Management
● NEAC
● Network Element Backup and Restore
Service Service Service Web Server
● Audit Trail
Fig. 11
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90524EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
zzz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

The NSS network subsystem is managed from NetAct via the XoH mediation. The Network
Subsystem (NSS) consists of the following network elements: Mobile Switching Center
(MSCi) with the DX 200 Home Location Register (HLRi) and Circuit Switched Data Server
(CDS).
The DX 200 Mobile Switching Center (DX MSCi) is a digital switching product for both GSM
(2G) and UMTS (3G) networks. In the DX 200-based network, the NSS switching functions
are distributed between the DX MSCi and DX HLRi, with the DX MSCi performing the
functions of the MSC, the Visitor Location Register (VLR) and Service Switching Point (SSP).
The DX 200 Home Location Register (DX HLRi) functions as an integrated DX HLR (HLR),
Authentication Center (AUC) and Equipment Identity Register (EIR).
The Circuit Switched Data Server (CDS) is a data server providing the circuit switched data
call interworking between PLMN and the fixed networks. The CDS converts the protocols
used in the PLMN to those used in the fixed network.
OS90524EN15GLA0

XoH SBM
Supported Network Elements
The NSS network subsystem is managed

from NetAct via the XoH mediation. The
Network Subsystem (NSS) consists of the
following network elements: Mobile
Switching Center (MSCi) with the DX 200
Home Location Register (HLRi) and Circuit
Switched Data Server (CDS).
Fig. 12
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90524EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
zzz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
XoH SBM
Supported Network Elements
Open TAS Tv16.2
Open TAS Open TAS 15 (Tv17.0) Support
Open TAS 15 Cloud (Tv17.0)
M15.0
M15.1
Md16.1 (DX)
Md16.1 EP1 (DX)
MSC/HLR/
Md16.2 (DX) Support
CDS/MSS
M16.0
M16.0 EP1
Ma16.1 (ATCA)
Ma16.2 (ATCA)
For
1 detailed information,
© Nokia Solutions and Networks please
2014 check the latest Compatibility Matrix file
Fig. 13
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OS90524EN15GLA0
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia
. Solutions
. . .and .Networks
. .2015.
38
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3 XoH Data Flow

3.3.1 FM Data Flow
3.3.1.1 Alarm Event
1. Network element sends alarm event notification to XoH mediation through
HTTP/HTTPS.
2. XoH mediation parses the notification.
3. XoH mediation changes the notification format to OFaS.
4. XoH mediation sends the OFaS message to SMIRP (inter sub-systems communication).
5. SMIRP dispatches the message to FM application.
OS90524EN15GLA0
.
zzz 39
XoH SBM
Fault Management Data Flow: Alarm Event
Fig. 14
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OS90524EN15GLA0
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia
. Solutions
. . .and .Networks
. .2015.
40
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1.2 Alarm Upload Data flow

1. The user triggers an alarm upload from alarm monitor application.
2. SMIRP sends the alarm upload request to XoH mediation.
3. XoH mediation parses the alarm upload request.
4. XoH mediation sends SOAP request to the network element to perform alarm uploading.
5. After the network element completes preparing uploading file, it sends an alarm file
ready notification to XoH mediation.
6. XoH mediation parses the notification.
7. XoH mediation retrieves IP address, file transfer protocol and user/password from
credential service.
8. XoH mediation uses FTP/SFTP to get the alarm file from the network element.
9. XoH gets the alarm file from the network element.
10. XoH mediation changes the file format to OFaS.
11. XoH mediation sends the OFaS message to SMIRP (inter sub-systems communication).
12. SMIRP sends the OFaS message to FM application.
OS90524EN15GLA0
.
zzz 41
XoH SBM
Fault Management Data Flow: Alarm Upload
Fig. 15
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OS90524EN15GLA0
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia
. Solutions
. . .and .Networks
. .2015.
42
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 PM Data Flow

1. Network element sends performance management file ready notification to XoH
mediation through HTTP/HTTPS.
2. XoH mediation parses the notification to get the performance management data file
paths.
3. XoH mediation retrieves network element information from NASDA (topology service)
and credential service, such as network element DN, IP address, file transfer protocol,
user and password.
4. XoH mediation uses FTP/SFTP to get performance management data files from network
element.
5. XoH mediation gets file from network element and sends SOAP message to network
element for successfully transferred files.
6. XoH mediation converts performance management data file format from OMeS1 to
OMeS2.
7. XoH mediation puts OMeS2 files into performance management pipe.
8. PM application handles the files in performance management pipe.
.
Note
In NetAct 15 EP1 there is no common topology for all components. Instead, each component
(for example fault management) has its own topology for application or component specific
data. In NetAct 15 EP1, there is NetAct System Data Access service (NASDA) which
contains and only handles data relevant for the whole NetAct:
 Managed objects registry
 Relationships between managed objects
 Network element connectivity and interface information
 Maintenance regions
 Working sets
 Sites
OS90524EN15GLA0
.
zzz 43
XoH SBM
PM Data Flow
Fig. 16
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OS90524EN15GLA0
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia
. Solutions
. . .and .Networks
. .2015.
44
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.3 Subscriber Level Trace (SLT) Data flow

1. Network element sends trace file ready notification to XoH mediation through
HTTP/HTTPS.
2. XoH mediation parses the notification to get the network element name and trace file
paths.
3. XoH mediation retrieves network element information from NASDA and credential
service, such as network element DN, IP address, file transfer protocol, user and
password.
4. XoH mediation gets information from NASDA.
5. XoH mediation uses FTP/SFTP to get trace files from network element.
6. XoH mediation gets file from network element and sends SOAP message to network
element for successfully transferred files.
7. XoH mediation converts OObS trace file format.
8. XoH mediation sends the OObS data to SMIRP.
9. SMIRP dispatches the OObS data to TraceViewer application.
OS90524EN15GLA0
.
zzz 45
XoH SBM
Subscriber Level Trace Data Flow
Fig. 17
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OS90524EN15GLA0
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .© Nokia
. Solutions
. . .and .Networks
. .2015.
46
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4 Managing XoH SBM

3.4.1 Managing the ServiceMix process
Using smanager: [root]# /opt/cpf/bin/smanager.pl stop service xoh
XoH SBM
Troubleshooting: Managing the XoH SMI
n83-vm12
ftp-n83-vm12 started standAlone
nx2s started standAlone
xoh started standAlone
ne3sws_dynamicadaptation started standAlone
generic_mediations started standAlone
Fig. 18
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90524EN15GLA0
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
© Nokia
. Solutions
. . and. Networks
. . .2015.. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
zzz
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5 Logging and Tracing

3.5.1 Logging
All the mediation log files of XoH SBI are under /var/opt/oss/log/xoh.
The log file for information level is oss_activity0_0.log, and the log file for debug level is
oss_trace0_0.log. The log file for error level is oss_error0_0.log.
3.5.2 Trace
More debug details in logs of Mediation Framework can be obtained modifying some parts of
the log4j.xml file.
Please follow these steps:
1. To change the mediation log level, enter command:
/opt/oss/NSN-jbi_swp/bin/set_logger_level.sh -instance xoh -
logger com.nsn.oss.xoh -level <The level you want to change>
The possible values are INFO (default), TRACE, DEBUG, WARN, ERROR and FATAL
OS90524EN15GLA0

4 NX2S SBM
OS90524EN15GLA0
.
zzz 49
4.1 NX2S (NE3S/FTP) Mediation

Nokia XML Solution Suite Southbound Interface (NX2S SBI) provides a well-defined interface
based on the extensible markup language (XML) which supports FTP file-based processes.
NX2S SBI offers basic configuration management function including Integration Data Upload
(old Topology Upload) and Integration Data Notification.
NX2S system component provides southbound mediation interfaces to an NX2S based
Agent. This mediation is built on JBI technology based on the Mediation Framework and is
designed to be adaptable to multiple OSS Systems.
4.1.1 Basic Configuration Management (BCM) -Upload

Basic CM comprises the essential functionality needed in a management system to "detect"
and manage a NE.
It provides functions like
 real-time forwarding of notifications
 upload of the basic configuration parameter from the agent (i.e. the configuration of the
Network Element)
Regarding the network parameters, for Basic CM essentially the hierarchy of managed
objects and the parameter common to all classes like user label, vendor or version are of
relevance.
Configuration upload provides means to align the NE image in the Network Manager (e.g.
NetAct) with the actual (or real) configuration of the agent (e.g. Element Manager or NE).
Such function is needed since changes in the Network might not be notified to the manager
in any case (failure situation, notification not supported) or initial upload after installation.
When processing the uploaded configuration, the manager compares its own image in the
database with the data received from the agent and processes it according to the assumption
that the network is the master image:
 Found new managed objects (e.g. NE's) are inserted into the NM database
 Removed managed object (i.e. objects are found in manager but not in the NE) are
deleted from manager database.
Typically the deletion process will include also the removal of all child instances of the node
object implicitly.
 Managed objects, which are modified compared to manager’s image, are updated in the
manager database.
 Inconsistent data is discarded (e.g. invalid relations like MO's without valid parent)
OS90524EN15GLA0

NX2S SBM
Overview
NE3S/FTP XML Solution Suite SBI (NX2S SBI) provides a well-defined interface based
on XML which supports FTP file-based processes. NX2S SBI offers basic configuration
management function including Integration Data Upload and Integration Data Notification
Fig. 19
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OS90524EN15GLA0
. . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zzz. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2 XoH Data Flow

4.2.1 Integration Data Upload
This section describes the data flow in NX2S SBI file-based Integration Data Upload.
1. The user requests an Integration Data Upload from the NetAct Monitor application.
NetAct Monitor application forwards the request to Mediation Dispatcher.
2. Mediation Dispatcher forwards the request to NX2S SBI.
3. NX2S SBI writes a request file into the export directory /home/nx2suser/export.
4. Network element or external system reads the request file from the export directory by
using FTP and remove the request after reading.
5. Network element or external system creates a configuration file and stores it to the
import directory by using FTP.
6. NX2S SBI reads the configuration file from the import directory /home/nx2suser/import.
7. NX2S SBI stores the uploaded objects in configuration file to NASDA.
8. NX2S SBI forwards the upload completion feedback to Notification Handler.
9. Notification Handler forwards the upload completion feedback to NetAct Monitor
application.
OS90524EN15GLA0

NX2S SBM
Data Flow Integration Data Upload (BCM)
Export Dir:
home/nx2suser/export
Import Dir:
/home/nx2suser /import
Fig. 20
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
OS90524EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Solutions
. . .2015.. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zzz. . . . . . . . 53
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2 Data Notification Handler

1. Network element or external system creates a notification file and stores it to the import
directory by using FTP.
2. NX2S SBI reads the notification file from the import directory /home/nx2suser/import.
3. NX2S SBI creates or deletes the objects in notification file from NASDA.
4.2.3 Users
During installation, nx2suser account is added to LDAP.
4.2.4 Interfaces
During startup time, NX2S registers it service to the ICF (Interface Communications
Framework). After this, the mediation is available for OSS Applications.
WARNING
NX2S has no connection to any NE. Its main purpose is to poll import and
export folders where elements are updating responses and reading requests.
4.2.5 Deployment
The computer platform for NX2S Mediation is deployed on all VM Nodes. The mediation
itself is deployed as xoh service.
OS90524EN15GLA0

NX2S SBM
Integration Data Notification
Fig. 21
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
OS90524EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Solutions
. . .2015.. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zzz 55
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3 Troubleshooting NX2S SBI

4.3.1 Checking NX2S SBI status
Log in to any VM as the root user.
Check NX2S SBI status by entering:
# smanager.pl status
If the state of service:nx2s is “started”, NX2S SBI is running. If the state of service:nx2s is
disabled, NX2S SBI is stopped.
OS90524EN15GLA0

NX2S SBM
Troubleshooting: Checking NX2S SMI status
n83-vm12
ftp-n83-vm12 started standAlone
nx2s started standAlone
xoh started standAlone
ne3sws_dynamicadaptation started standAlone
generic_mediations started standAlone
Fig. 22
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . .
OS90524EN15GLA0 . . . . . . . . . . . . . . . . . . . . . . . . . . .
. Solutions
. . .2015.. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
zzz. . . . . . . . 57
. . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.4 Log Files and Tracing

4.4.1 Log levels for NX2S
4.4.2 Log Location

- NX2S log is under /var/opt/oss/log/nx2s
* oss_activity0_0.log (for verbose log like DEBUG/INFO)
* oss_error0_0.log (for WARN/ERROR logs)
* oss_trace0_0.log (for event tracing logs)
4.4.3 Mediation log

All mediation log files of NX2S SBI are under /var/opt/oss/log/nx2s.
The log file for information level is oss_activity0_0.log, and the log file for debug level is
oss_trace0_0.log. Errors are logged to oss_error0_0.log.
To change mediation log levels and the file location, modify file /var/opt/oss/log/NSN-
nx2s/log4j.xml accordingly.
4.4.4 Audit Trail log

The output file of audit trail log is /var/opt/oss/log/audit/oss_change-
common_mediations0_0.log.
To change audit trail log levels and the file location, modify file
/var/opt/oss/log/smx/conf/logging.properties accordingly.
OS90524EN15GLA0

4.4.5 Trace
/opt/oss/NSN-jbi_swp/bin/set_logger_level.sh
The purpose for this script is to change the level of the logs dumped to NX2S log file. Behind
the scene, this script will modify the logging configuration file:
/opt/oss/NSN-nx2s/smx/conf/log4j.xml
No restart is needed – Log level change takes effect immediately. Any error during the
execution of this script will be dumped to
/var/opt/oss/log/NSN-nx2s/set_logger_level.log
Before changing the logging level, the log4j.xml entries are:

<logger name=" com.nsn.oss.nx2s ">
<level value="INFO"/>
</logger>
To change the Log level, execute:

#set_logger_level.sh –instance NSN-nx2s –logger com.nsn.oss.nx2s –
level ERROR
Then, the log4j.xml will be updated with new log level

<logger name=" com.nsn.oss.nx2s ">
<level value=“ERROR"/>
</logger>
OS90524EN15GLA0
.
zzz 59
OS90524EN15GLA0

5 Exercises
OS90524EN15GLA0
.
zzz 61
Exercise 1
Title: NE3S/WS SBI
Objectives: Explain the functionality of NE3S/WS SBM

Describe the FM support provided by NE3S/WS SBM
Explain the Data Flow between NetAct and NE3S/WS managed
Network elements
Manage the NE3S/WS SBM
List the log files and manage traces for NE3S/WS SBM.
Pre-requisite: none
Task
Please execute the exercises and answer the corresponding questions. Use the credentials
provided by the trainer to connect to NetAct system.
Query
1. What is the carrier protocol in NE3S/WS?
______________________________________________________________________
______________________________________________________________________
2. List the main management fragments carried by NE3S/WS.

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
3. NE3S/WS is based on which known widely technology?

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90524EN15GLA0

4. List 2 Network Elements supported by NE3S/WS

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
5. What transfer method is in use of CM?

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90524EN15GLA0
.
zzz 63
Exercise 2
Title: SNMP and NE3S/SNMP SBI
Objectives: Explain the SNMP most important functionalities.

List the SNMP and NE3S/SNMP managed network elements..
Manage the SNMP and NE3S/SNMP SBM
Pre-requisite: none
Task
Query
1. Explain the concept of SNMP Trap.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
2. How does an Agent know where to send a Trap?

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
3. List three SNMP trap sending elements supported in NetAct 15. List three NEs managed
via NE3S/SNMP. Please use as reference the latest NE Compatibility Matrix.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90524EN15GLA0

4. List all active applications for SNMP and NE3S/SNMP in WAS. Can you see this
information from command line? Please execute the commands if available and
compare with the information found in the WAS Console.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90524EN15GLA0
.
zzz 65
Exercise 3
Title: XoH and NX2S SBI
Objectives: List the network elements supported by XoH SBI

Explain the functionality provided by NX2S SBM for Basic
Configuration Management.
Describe the XoH and NX2S Mediations functionality.
Manage the XoH NX2S in NetAct.
List the log files and manage traces for XoH and NX2S SBM
Pre-requisite: None
Task
Query
1. What network subsystem is supported by XoH mediation? List the supported network
elements.
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
2. What is the purpose of NX2S Mediation?

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
3. List the operations that are supported in NX2S mediation.

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90524EN15GLA0

4. List three network elements that are using NX2S BCM.

______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
OS90524EN15GLA0
.
zzz 67
OS90524EN15GLA0

04 OS90524EN15GLA0 Connecting The Core Network

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

04 OS90524EN15GLA0 Connecting The Core Network

Hochgeladen von

Copyright:

Verfügbare Formate

Connecting the Core Network

Connecting the Core Network

2 © Nokia Solutions and Networks 2015.

1.1 NE3S/WS Mediation

 PM - Performance Management (Administration of Measurements)

 ATL - Audit Trail

 SLT - System Level Trace / Subscriber and Equipment Trace

4 © Nokia Solutions and Networks 2015.

NetAct Network Element

1 © Nokia Solutions and Networks 2015

1.2 Supported Network Elements

NE Type Versions Function Support

CAM 15.0 FM, PM Support

MGW U5.0 EP2 U6.0 Support

Flexi NS – SGSN SG8.0 ATCA , SG8.0 ATCA CD2, SG8.0

SG8.0 DX CD2 , SG8.0 DX CD3 ,SG8.0

Flexi NG Flexi NG2.0 , Flexi NG2.1 , Flexi NG3.1, Support

One-EIR One-EIR 4.0 SP1 , One-EIR 5.0 , One-EIR FM, PM Support

MGW U5.0 EP2 U6.0 Support

Flexi NS – SGSN SG8.0 ATCA , SG8.0 ATCA CD2, SG8.0

SG8.0 DX CD2 , SG8.0 DX CD3 ,SG8.0

Flexi NG Flexi NG2.0 , Flexi NG2.1 , Flexi NG3.1, Support

6 © Nokia Solutions and Networks 2015.

NE Type Versions Function Support

One-NDS One-NDS 8 MP8 , One-NDS 9 Base, One- Support

One-EIR One-EIR 4.0 SP1 , One-EIR 5.0 , One-EIR FM, PM Support

CMD 4.0 FM, PM Support

Flexi CMD5.0 , Flexi CMD5.1 , Flexi Support

DXA 3.2 FM, PM Support

SBC SD 6.2 4250/4500/3820 FM, PM support

SBC SD SBC SD 6.3 4500/3820

SBC SD 6.4 4500/3820

SBC BG 6.2 4500 FM, PM support

BG 4500 SBC BG 6.3 4500

SBC BG 6.4 4500

BGF BGF 6.5 4250/4500 FM, PM support

EMC R14, R19 FM Support

iNUM 9.0 , iNUM 10.0 , iNUM 11.0 , iNUM FM, PM Support

IPSW (Cisco) IOS12.x , IOS15.x FM, PM Support

RTR (Cisco) IOS12.x , IOS15.x FM, PM Support

SAM Server 4.20. FM, PM Support

nSignia nSignia 2.8.4 FM, PM Support

Movius Mereon 4.1 Support

CAM 15.0 FM, PM Support

NE Type Versions Function Support

IMS CMS-8200 (HSS- Support

Convedia CMS-3000 v3.16 FM, PM Support

Convedia CMS-9000 v3.16 FM, PM Support

hiG1800 V7.2, V8.1 FM, PM Support

Load Balancer F5 BIG- FM, PM Support

8 © Nokia Solutions and Networks 2015.

1.3 NE3S / WS Implementation

1.3.1 FM Data Flow

Protocol manager credentials

SMI: South Mediation Interface

1 © Nokia Solutions and Networks 2015

1.3.2 PM Data Flow

The following list contains the basic scenarios in performance management:

1) Create and activate

1 © Nokia Solutions and Networks 2015

The PM data is transferred to

1.3.3 CM Data Flow

14 © Nokia Solutions and Networks 2015.