ENIQ Events Node Commissioning

PROCEDURE MANUAL

2/1546-AOM 901 079 Uen A

Copyright

© Ericsson LMI 2012. 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.

2/1546-AOM 901 079 Uen A | 2012-05-29

 Contents

Contents

1 About This Document 1

1.1 Scope 1
1.2 Purpose 1
1.3 Target Groups 1
1.4 Prerequisites 2
1.5 Typographic Conventions 2
1.6 Consistency Checking, Activating, and Checkpointing 2

2 Activation of Events on SGSN Node 3

2.1 SGSNR8 and Subsequent Versions 3
2.2 SGSN-MME 09B and Subsequent Versions 4

3 Activation of Cell Trace Events and CTUM 7

3.1 Cell Trace Events (Stream based) Initiation on eNodeB 7
3.2 Cell Trace Events (File-based) Initiation on eNodeB 8
3.3 Cell Trace UE Identification Mapping (CTUM) Initiation
on MME 9
3.4 LTE Event List 12

4 Activation of GPEH Events on RNC 15

4.1 GPEH Event List 15

5 Operands and Variables 17

5.1 Operands and Variables of EBS CLI Commands for
SGSN,SGSN MME Nodes 17
5.2 Operands and Variables of Cell Trace Mapping CLI
Commands for SGSN MME Nodes 20

Glossary 25

Reference List 27

2/1546-AOM 901 079 Uen A | 2012-05-29

ENIQ Events Node Commissioning

2/1546-AOM 901 079 Uen A | 2012-05-29

 About This Document

1 About This Document

This chapter contains the following parts:

• Scope

• Purpose

• Target groups

• Prerequisites

• Typographic conventions

1.1 Scope
The contents of this document are applicable where configuration changes are
required on a network element or OSS-RC to support ENIQ Events.

1.2 Purpose
This document should be used as a guideline on how to activate events on the
following nodes:

• SGSNR8 and subsequent versions

• SGSN-MME 09B and subsequent versions

• LTE RBS L11B and subsequent versions

• WCDMA RNC W11A and subsequent versions

A complete list of the node types and versions supported can be found in
Supported Network Elements, see Reference [3].

1.3 Target Groups

The intended target groups for this document are the following:

• Alarm Operator

• Radio Network Engineer

• System Administrator

• Installation Engineer

2/1546-AOM 901 079 Uen A | 2012-05-29 1

 ENIQ Events Node Commissioning

• Field Technician

1.4 Prerequisites
Readers of this document must have root authority to perform the tasks listed.
It is also assumed that the person performing the CLI command should have a
solid knowledge of and training in the following areas:

• ENIQ Events

• Unix

• Operation of the Serving GPRS Support Node and Mobility Management

Entity (SGSN-MME)

• Operation of the LTE Radio Base Stations (RBS)

• Operation of the WCDMA Radio Network Controller (RNC)

1.5 Typographic Conventions

The typographic conventions for all Customer Product Information (CPI) in
OSS-RC are found in OSS Library Typographic Conventions, Reference [2].

1.6 Consistency Checking, Activating, and Checkpointing

The following commands are common commands used to verify any
configuration changes on SGSN, SGSN-MME Nodes and should be run
wherever specified in the document:

1. To consistency check the pending and active configurations, use the

check_config CLI command.

2. To activate the currently modified attributes in the pending configuration,

use the activate_config_pending CLI command.

3. To persistently store the currently modified attributes in the SGSN,

checkpoint the software configuration by using the checkpoint CLI
command.

2 2/1546-AOM 901 079 Uen A | 2012-05-29

 Activation of Events on SGSN Node

2 Activation of Events on SGSN Node

The following section provides the procedure for Activating SGEH events for
ENIQ Events

In order to activate Events on specific nodes appropriate user permission is

required on the node.

Refer to specific Node CPI documentation for more information on user roles
and permissions.

2.1 SGSNR8 and Subsequent Versions

2.1.1 Activate Events

modify_ebs [-att Attach] [-actprim ActivatePrimaryPdp]

[-actsec ActivateSecondaryPdp] [-rau Rau] [-israu Israu]
[-deact Deactivate]

The modify_ebs CLI command configures the event types that must be logged
in the EBS-S log.

For a description of the operands and variables included, see Section 5 on

page 17.

2.1.1.1 Action Set

A user role with action set ebs_active is required to use this CLI command.

2.1.1.2 Output

This CLI command is accepted if no output response appears. Otherwise,

an error message appears.

2.1.1.3 Consistency Checking, Activating, and Checkpointing

Consistency checking, activating, and checkpointing are required, see Section

1.6 on page 2.

2.1.1.4 Example

The command turns on/off the logging of EBS-S event types.

2/1546-AOM 901 079 Uen A | 2012-05-29 3

 ENIQ Events Node Commissioning

Input

gsh modify_ebs -rau on -israu off

2.1.2 Set Report Period

modify_ebs_log [-rp ReportPeriod]

The modify_ebs_log CLI command configures the report period of the

Event-Based Statistics log.

For a description of the operands and variables included, see Section 5 on

page 17.

Note: For ENIQ Events the ReportPeriod must be set to 1.

2.1.2.1 Action Set

A user role with action set ebs_active is required to use this CLI command.

2.1.2.2 Output

This CLI command is accepted if no output response appears. Otherwise,

an error message appears.

2.1.2.3 Consistency Checking, Activating, and Checkpointing

Consistency checking, activating, and checkpointing are required, see Section

1.6 on page 2.

2.1.2.4 Example

This example modifies the EBS report interval to one minute.

Input

gsh modify_ebs_log -rp 1

2.2 SGSN-MME 09B and Subsequent Versions

2.2.1 Activate Events

modify_ebm_event -en EventName [-eo EventOutput]

The modify_ebm_event CLI command configures the output mechanism for a

specific Event-Based Monitoring event type. The output of the event type may

4 2/1546-AOM 901 079 Uen A | 2012-05-29

 Activation of Events on SGSN Node

be logged in the Event-Based Monitoring log file, streamed in real-time to an

external server or be both logged to file and streamed.

Note: It is recommended that all EventNames are activated for ENIQ Events.

EventOutput must be set to log, see Section 5 on page 17.

The CLI command will succeed only if a license for the optional feature
Event-Based Monitoring on the SGSN-MME node has been granted.

For a description of the operands and variables included, see Section 5 on

page 17.

2.2.1.1 Action Set

A user role with action set ebm_active is required to use this CLI command.

2.2.1.2 Output

This CLI command is accepted if no output response appears. Otherwise,

an error message appears.

2.2.1.3 Consistency Checking, Activating, and Checkpointing

Consistency checking, activating, and checkpointing are required, see Section

1.6 on page 2.

2.2.2 Set Report Period

modify_ebm_log [-rp ReportPeriod]

The modify_ebm_log CLI command configures the report period of the

Event-Based Monitoring log.

For a description of the operands and variables included, see Section 5 on

page 17.

Note: For ENIQ Events the ReportPeriod must be set to 1.

2.2.2.1 Action Set

A user role with action set ebm_active is required to use this CLI command.

2.2.2.2 Output

This CLI command is accepted if no output response appears. Otherwise,

an error message appears.

2/1546-AOM 901 079 Uen A | 2012-05-29 5

 ENIQ Events Node Commissioning

2.2.2.3 Consistency Checking, Activating, and Checkpointing

Consistency checking, activating, and checkpointing are required, see Section

1.6 on page 2.

2.2.2.4 Example

This example modifies the EBM report interval to one minute.

Input

gsh modify_ebm_log -rp 1

6 2/1546-AOM 901 079 Uen A | 2012-05-29

 Activation of Cell Trace Events and CTUM

3 Activation of Cell Trace Events and CTUM

The following section provides the procedure for Activating Cell Trace Events
and CTUM Trace of LTE Events for ENIQ Events.

3.1 Cell Trace Events (Stream based) Initiation on eNodeB

ENIQ Events relies on Subscription Profiles and the Performance Monitoring
(PMS) functionality of OSS for LTE Cell Trace Stream Initiation on eNodeBs.
PMS provides measurement management and result file collection support
for CellTrace functions of LTE RAN.

Create Cell Trace Subscription Profile using PMS with the following inputs:

Table 1 Parameters and Input

Parameter Required Input
Cell Trace : eNodeBs Select List of eNodeBs (of the same
MIM Version) on which Cell Trace is
to be initiated
Cell Trace Output Mode Select Output Mode as
"STREAMING"
IP Address Specify the IP Address of the stream
termination blade of the ENIQ Events
deployment.
The IP Address of the stream
Termination Blade can be found by
executing the following command on
the ENIQ Events Server :
# grep "ec_2" /etc/hosts |
awk '{print $1}'
Ports Enter the port number from the
pre-defined port ranges.
For the list of Pre-defined Ports, see
Destination Port Ranges for CTR
Streams and CTUM in Reference [4].

2/1546-AOM 901 079 Uen A | 2012-05-29 7

 ENIQ Events Node Commissioning

Cells Select "All Cells".

Events Choose the list of Events depending
on the Feature.
For the list of events, see Section 3.4
on page 12.
Warning: Ensure that only the
required Events are selected.
Selecting more events might lead to
unnecessary traffic over network.

After successful creation, activate the profile in PMS by Resuming Profile.

For more detailed information on the steps above, refer to the Subscription
Profiles and Performance Monitoring User Guide, see Reference [5].

3.2 Cell Trace Events (File-based) Initiation on eNodeB

ENIQ Events can consume input from cell trace files provided by OSS
Subscription Profiles and Performance Monitoring (PMS). PMS provides
measurement management and result file collection support for CellTrace
functions of LTE RAN.

To activate file-based Cell Trace Events for LTE Event, create Cell Trace
Subscription Profile in PMS with the following inputs:

Table 2 Parameters and Input

Parameter Required Input
Cell Trace : eNodeBs Select List of eNodeBs( of the same
MIM Version) on which Cell Trace is
to be initiated.
Cell Trace Output Mode Select Output Mode as "FILE"
Cells Select "All Cells".
Events Choose the list of Events depending
on the Feature .
For the list of Events, see Section 3.4
on page 12.
Warning: Ensure that only the
required Events are selected.
Selecting more events might lead to
unnecessary traffic over network.
Filter Select ASN1 (Applicable only from
12A Onwards)

After successful creation, activate the profile PMS by Resuming Profile.

8 2/1546-AOM 901 079 Uen A | 2012-05-29

 Activation of Cell Trace Events and CTUM

For more detailed information on the steps above, refer to the Subscription
Profiles and Performance Monitoring User Guide, see Reference [5].

Note: For ENIQ Events to consume the Cell Trace file provided by PMS,
ensure that createSymbolicLinksERbsCellTrace_ENIQEvents
is set to true in PMS. See PM, Performance Monitoring, Subscription
Profile and Performance Monitoring System Admin Guide in Reference
[5].

3.3 Cell Trace UE Identification Mapping (CTUM) Initiation

on MME
CTUM (Cell Trace UE Identification Mapping) streams have to be manually
initiated using CLI on the MME.
The IP Address Username, Password to connect to MME can be found from
OSS-RC.

In order to activate CTUM Streams on specific nodes, appropriate user

permission is required on the node. Refer to specific Node CPI documentation
for more information on user roles and permissions.

Activate the Cell Trace Mapping on MME with the following inputs via CLI
commands described below.

Note: While Activating CTUM streams on multiple MME Nodes, ensure that
the ENIQ Events ports are chosen in such a way that the streams
coming from MMEs are distributed across ports for load balancing.

For a description of the operands and variables included in CLI, see Section 5
on page 17.

3.3.1 Activate CTUM Streaming

modify_node_function -name FunctionName [-state

FunctionState]

The modify_node_function CLI command modifies the state of the specified

node function. Specify that Cell Trace Mapping log events are to be
streamed using the stream_cell_trace_ueid_mapping parameter as
FunctionName. For a description of the operands and variables included in
CLI , see Section 5 on page 17.

3.3.1.1 Action Set

A user role with action set feature_active is required to use this CLI
command.

2/1546-AOM 901 079 Uen A | 2012-05-29 9

 ENIQ Events Node Commissioning

3.3.1.2 Output

This CLI command is successfully executed if no output response appears.

Otherwise, an error message appears explaining the problem.

3.3.1.3 Consistency check, Activating and Check point

Consistency checking, activating, and checkpointing are required, see Section

1.6 on page 2.

3.3.1.4 Example

modify_node_function –name stream_cell_trace_ueid_mapping

3.3.2 Configure IP Address for Trace Collection Server

create_trace_collection_server -tcsn TraceCollectio

nServerName -ip TraceCollectionServerIpAddress -port
TraceCollectionServerPort

The create_trace_collection_server CLI command is used to configure the

IP address and TCP port of an external server which functions as a Trace
Collection server.

Select the Inputs for the Trace Collection Server IPAddress and Port as below:

Table 3 Parameters and Input

Parameter Required Input
TraceCollectionServerIpAdd Specify the IP Address of the stream
ress termination blade of the ENIQ Events
deployment.
The IP Address of the stream
Termination Blade can be found by
executing the following command on
the ENIQ Events Server:
# grep "ec_2" /etc/hosts
| awk '{print $1}'
TraceCollectionServerPort Specify the port number from the
pre-defined port ranges.
For the list of pre-defined ports, see
Destination Port Ranges for CTR
Streams and CTUM in Reference [4].

Refer to Configuring Cell Trace and UE Trace Operation Instructions for more
information, see Reference [6].

10 2/1546-AOM 901 079 Uen A | 2012-05-29

 Activation of Cell Trace Events and CTUM

3.3.2.1 Action Set

A user role with action set mme_active is required to use this CLI command.

3.3.2.2 Output

This CLI command is successfully executed if no output response appears.

Otherwise, an error message appears explaining the problem.

3.3.2.3 Consistency check, Activating and Check point

Consistency checking, activating, and checkpointing are required, see Section

1.6 on page 2.

3.3.2.4 Example

create_trace_collection_server -tcsn ENIQStreamTermination

-ip 10.158.26.75 -port 4010

3.3.3 create_ip_service

create_ip_service -sn IpServiceName -nw IpNetworkName

The create_ip_service

CLI command configures an IP service on the specified network.

3.3.3.1 Action Set

A user role with action set ip_active is required to use this CLI command.

3.3.3.2 Output

This CLI command is successfully executed if no output response appears.

Otherwise, an error message appears explaining the problem.

3.3.3.3 Consistency check, Activating and Checkpointing

Consistency checking, activating, and checkpointing are required, see Section

1.6 on page 2.

3.3.3.4 Example

create_ip_service -sn CTUM -nw Gom

3.3.4 Configure IPv4 Address

create_ip_service_address -sn IpServiceName -ip
ServiceIpAddress

2/1546-AOM 901 079 Uen A | 2012-05-29 11

 ENIQ Events Node Commissioning

The create_ip_service_address CLI command configures an IPv4

address for the specified IP service.

3.3.4.1 Action Set

A user role with action set ip_active is required to use this CLI command.

3.3.4.2 Output

This CLI command is successfully executed if no output response appears.

Otherwise, an error message appears explaining the problem.

3.3.4.3 Consistency check, Activating and Checkpointing

Consistency checking, activating, and checkpointing are required, see Section

1.6 on page 2.

3.3.4.4 Example

create_ip_service_address -sn CTUM -ip 10.43.223.2

3.4 LTE Event List

Below is the list of pm Events that are required to be initiated in Cell Trace
on eNodeB.

Table 4 PM Events
Event Name LTE Event Statistics LTE Call Failure LTE Handover
Analysis Failure Analysis

Version L11B L12A L12B L11B L12A, L11B L12A, L12B

L12B
INTERNAL_PROC_RR Y Y Y Y Y
C_CONN_SETUP
INTERNAL_PER_PROC Y Y Y
ESSOR_LOAD
INTERNAL_PROC_S1_ Y Y Y
SETUP
INTERNAL_PROC_HO_ Y Y Y Y Y
EXEC_S1_OUT
INTERNAL_PROC_HO_ Y Y Y Y Y
EXEC_X2_OUT
INTERNAL_PROC_UE_ Y Y
CTXT_RELEASE_ENB
INTERNAL_PROC_X2_ Y Y Y
SETUP
INTERNAL_PROC_INIT Y Y Y Y Y
IAL_CTXT_SETUP

12 2/1546-AOM 901 079 Uen A | 2012-05-29

 Activation of Cell Trace Events and CTUM

Event Name LTE Event Statistics LTE Call Failure LTE Handover
Analysis Failure Analysis
Version L11B L12A L12B L11B L12A, L11B L12A, L12B
L12B
INTERNAL_PROC_ERA Y Y Y Y Y
B_SETUP
S1_DOWNLINK_NAS_T Y Y Y
RANSPORT
S1_UPLINK_NAS_TRA Y Y Y
NSPORT
INTERNAL_PROC_UE_ Y Y Y
CTXT_RELEASE
INTERNAL_PROC_ERA Y Y
B_RELEASE
INTERNAL_EVENT_S1 Y Y
_NAS_NON_DELIVERY
_INDICATION
INTERNAL_EVENT_S1 Y Y
_ERROR_INDICATION
INTERNAL_PROC_X2_ Y Y
RESET
INTERNAL_EVENT_X2 Y Y
_ERROR_INDICATION
INTERNAL_PROC_SCT Y Y
P_SHUTDOWN
INTERNAL_PROC_S1_ Y Y
SIG_CONN_SETUP
INTERNAL_PROC_HO_ Y Y Y
EXEC_S1_IN
INTERNAL_PROC_HO_ Y Y Y
EXEC_X2_IN
INTERNAL_PROC_HO_ Y Y Y
PREP_S1_IN
INTERNAL_PROC_HO_ Y Y Y
PREP_S1_OUT
INTERNAL_PROC_HO_ Y Y Y
PREP_X2_IN
INTERNAL_PROC_HO_ Y Y Y
PREP_X2_OUT
INTERNAL_EVENT_AN Y
R_PCI_REPORT_WAN
TED
INTERNAL_EVENT_CM Y
AS_REQ
INTERNAL_EVENT_CM Y
AS_RESP
INTERNAL_EVENT_ET Y
WS_REQ
INTERNAL_EVENT_ET Y
WS_RESP
INTERNAL_EVENT_NE Y
IGHBREL_ADD

2/1546-AOM 901 079 Uen A | 2012-05-29 13

 ENIQ Events Node Commissioning

Event Name LTE Event Statistics LTE Call Failure LTE Handover
Analysis Failure Analysis

Version L11B L12A L12B L11B L12A, L11B L12A, L12B

L12B
INTERNAL_EVENT_UN Y
KNOWN_UE_AT_RE_E
STABLISHMENT
INTERNAL_PER_EVEN Y
T_CMAS_REPET_COM
PL
INTERNAL_PROC_ANR Y
_CGI_REPORT
INTERNAL_PROC_ERA Y
B_MODIFY
INTERNAL_PROC_RR Y
C_CONN_RECONF_NO
_MOB
INTERNAL_PROC_RR Y
C_CONNECTION_RE_
ESTABLISHMENT
INTERNAL_PROC_UE_ Y
CTXT_MODIFY

14 2/1546-AOM 901 079 Uen A | 2012-05-29

 Activation of GPEH Events on RNC

4 Activation of GPEH Events on RNC

ENIQ Events relies on Subscription Profiles and Performance Monitoring

(PMS) functionality of OSS for GPEH Event Initiation on RNC. PMS provides
measurement management and result file collection support GPEH Events
of WCDAM RAN.

Create GPEH Subscription Profile using PMS with the following inputs:

Table 5 Parameters and Input

Parameter Required Input
GPEH: Select NE Type Select the Network element type to
observe as RNC Network Element
to be Observed.
GPEH: Select RNC(s) Select List of RNCs (of same MIM
version) on which GPEH Events to
be initiated
GPEH: Select Cells Select All Cells.
GPEH: Select GPEH Events Choose the list of events depending
on the Feature. For list of Events,
see Section 4.1 on page 15.
Note Ensure that only the required
events are selected. Selecting more
events might lead to unnecessary
traffic over network.
GPEH : Select Filters Set the UE fraction as 1000.
Note The default is 1000.
GPEH: Select Schedule Select Schedule Type As
Scheduled and choose the
duration.

After successful creation activate the profile in PMS by Resuming Profile.

For detailed information on the steps above, refer to Subscription Profiles
and Performance Monitoring User Guide, available in Reference [5] for more
information.

4.1 GPEH Event List

Below is the list of GPEH Events that are required to be initiated on RNC

2/1546-AOM 901 079 Uen A | 2012-05-29 15

 ENIQ Events Node Commissioning

Table 6 List of GPEH Events

GPEH Event Name WCDMA WCDMA
Call Failure Handover
Analysis Failure
Analysis
INTERNAL_SYSTEM_RELEASE Y
INTERNAL_IMSI Y Y
INTERNAL_CALL_SETUP_FAIL Y
INTERNAL_SOFT_HANDOVER_EXECUTI Y
ON
INTERNAL_HSDSCH_CELL_SELECTION_ Y
NO_CELL_SELECTED
INTERNAL_FAILED_HSDSCH_CELL_CHA Y
NGE
INTERNAL_IFHO_EXECUTION_ACTIVE Y
INTERNAL_OUT_HARD_HANDOVER_FA Y
ILURE
RRC_UPLINK_DIRECT_TRANSFER Y Y

16 2/1546-AOM 901 079 Uen A | 2012-05-29

 Operands and Variables

5 Operands and Variables

5.1 Operands and Variables of EBS CLI Commands for

SGSN,SGSN MME Nodes
This section describes all operands and parameters included in the syntax of
the event-based Statistics CLI commands.
The following operands and variables are described.

actprim ActivatePrimaryPdp actsec ActivateSecond att Attach

aryPdp
deact Deactivate israu Israu rau Rau
en EventName rp ReportPeriod eo EventOutput

5.1.1 -actprim ActivatePrimaryPdp

The event type 'Activation of Primary PDP context' is being logged.

Type: Enumeration

Values: off,on

Default value: off

Unit: No unit

Activation: Not applicable

5.1.2 -actsec ActivateSecondaryPdp

The event type 'Activation of Secondary PDP context' is being logged.

Type: Enumeration

Values: off,on

Default value: off

Unit: No unit

Activation: Not applicable

5.1.3 -att Attach

The event type 'Attach' is being logged.

2/1546-AOM 901 079 Uen A | 2012-05-29 17

 ENIQ Events Node Commissioning

Type: Enumeration

Values: off,on

Default value: off

Unit: No unit

Activation: Not applicable

5.1.4 -deact Deactivate

The event type 'Deactivate' is being logged.

Type: Enumeration

Values: off,on

Default value: off

Unit: No unit

Activation: Not applicable

5.1.5 -israu Israu

The event type 'ISRAU' is being logged.

Type: Enumeration

Values: off,on

Default value: off

Unit: No unit

Activation: Not applicable

5.1.6 -rau Rau

The event type 'RAU' is being logged.

Type: Enumeration

Values: off,on

Default value: off

Unit: No unit

Activation: Not applicable

18 2/1546-AOM 901 079 Uen A | 2012-05-29

 Operands and Variables

5.1.7 -en EventName

The EventName variable specifies the name of an event-based Monitoring
event type.

Type: String

Syntax: Up to 60 characters

Values: No value range

Note: For ENIQ Events it is recommended to activate all Event Names.

Default value: No default

Unit: No unit

Activation: Run-time. After activation of the planned area.

5.1.8 -rp ReportPeriod

The ReportPeriod variable of the event-based Monitoring log specifies the time
interval after which a log file is stored on the network element.

Type: Enumeration

Values: 1,5,15,30,60

Note: For ENIQ Events, ReportPeriod must be set to 1.

Default value: 1

Unit: min

Activation: Run-time. After activation of the planned area.

5.1.9 -eo EventOutput

The EventOutput variable specifies the output mechanism for a specific
event-based Monitoring event type. The output may be logged in the
event-based Monitoring log file, streamed in real-time to an external server,
or both.

Type: Enumeration

Values: off,log,stream,log_stream

Note: For ENIQ Events, EventOutput must be set to log.

Default value: log

Unit: No unit

2/1546-AOM 901 079 Uen A | 2012-05-29 19

 ENIQ Events Node Commissioning

Activation: Run-time. After activation of the planned area.

5.2 Operands and Variables of Cell Trace Mapping CLI

Commands for SGSN MME Nodes
This section describes all operands and parameters included in the syntax of
the event-based Statistics CLI commands.
The following operands and variables are described.

-name FunctionName -state FunctionState -ip TraceCollectio

nServerIPAddress
-port TraceCollectionServerPort -tcsn TraceCollectionS -nw IpNetworkN
erverName ame
-sn IpServiceName -ip ServiceIpAddress

5.2.1 -name FunctionName

The FunctionName parameter specifies the name of a node function.

Type: String

Syntax: Up to 40 characters

Values: No defined value range

Default value: No default

Activation: Not applicable, read only.

5.2.2 -state FunctionState

The FunctionState parameter specifies the state of a node function.

Type: Enumeration

Values: off, on

Default value: No default value

Activation: Run-time. After activation of the planned area.

5.2.3 -ip TraceCollectionServerIpAddress

The TraceCollectionServerIpAddress parameter specifies the IP
address of an external server capable of receiving real-time Cell Trace Mapping
events streamed over TCP/IP.

Type: String

20 2/1546-AOM 901 079 Uen A | 2012-05-29

 Operands and Variables

Syntax: IP address notation: [1-126,128-223].[0-255].[0-255].[0-

255], 7-15 characters

Values: No defined value range

Default value: No default

Activation: Run-time. After activation of the planned area.

5.2.4 -port TraceCollectionServerPort

The TraceCollectionServerPort parameter specifies the TCP port of
an external server capable of receiving real-time Cell Trace Mapping events
streamed over TCP/IP.

Type: Integer

Values: 1024-65535

Default value: No default

Activation: Run-time. After activation of the planned area.

5.2.5 -tcsn TraceCollectionServerName

The TraceCollectionServerPort parameter specifies the TCP port of
an external server capable of receiving real-time Cell Trace Mapping events
streamed over TCP/IP.

Type: String

Syntax: Up to 255 characters

Values: No defined value range

Default value: No default

Activation: Run-time. After activation of the planned area.

5.2.6 -nw IpNetworkName

The IpNetworkName parameter specifies the name of a network.

Type: String

Syntax: IpNetworkName: a-z, A-Z, 0-9, ., _, - .

Values: 1-95 characters

Default value: No default

Activation: Run-time. After activation of the planned area.

2/1546-AOM 901 079 Uen A | 2012-05-29 21

 ENIQ Events Node Commissioning

5.2.7 -sn IpServiceName

The IpServiceName parameter identifies an IP service, for example Gb over

IP, in the SGSN-MME.

Type: Enumeration

Values: • sgsnlwg: CDR-FTP,CDR-GTP-P,CN-SS7-1,CN-S

S7-2,CTUM,DNS,EBM,Filterlog,GbIP,GbIP-C,Gn-G
TP-C,Gn-GTP-U,Iu-GTP-U,Iu-SS7-1,Iu-SS7-2,LI-C
,LI-U,NTP,OAM,S1-MME-1,S1-MME-2,S6a-1,S6a-
2,S13-1,S13-2,S3-GTP-C,S10-GTP-C,S11-GTP-C
,SGs-1,SGs-2,SLg-1,SLg-2,SLs-1,SLs-2

• sgsnwg: CDR-FTP,CDR-GTP-P,CN-SS7-1,CN-S
S7-2,DNS,EBM,Filterlog,GbIP,GbIP-C,Gn-GTP-C
,Gn-GTP-U,Iu-GTP-U,Iu-SS7-1,Iu-SS7-2,LI-C,LI-U
,NTP,OAM

• sgsnlg: CDR-FTP,CDR-GTP-P,CN-SS7-1,CN-SS7
-2,CTUM,DNS,EBM,Filterlog,GbIP,GbIP-C,Gn-GT
P-C,Gn-GTP-U,LI-C,LI-U,NTP,OAM,S1-MME-1,S1-
MME-2,S6a-1,S6a-2,S13-1,S13-2,S3-GTP-C,S10
-GTP-C,S11-GTP-C,SGs-1,SGs-2,SLg-1,SLg-2,S
Ls-1,SLs-2

• sgsng: CDR-FTP,CDR-GTP-P,CN-SS7-1,CN-SS7
-2,DNS,EBM,Filterlog,GbIP,GbIP-C,Gn-GTP-C,Gn-
GTP-U,LI-C,LI-U,NTP,OAM

• sgsnlw: CDR-FTP,CDR-GTP-P,CN-SS7-1,CN-SS
7-2,DNS,CTUM,EBM,Filterlog,Gn-GTP-C,Gn-GTP-
U,Iu-GTP-U,Iu-SS7-1,Iu-SS7-2,LI-C,LI-U,NTP,OA
M,S1-MME-1,S1-MME-2,S6a-1,S6a-2,S13-1,S13-2
,S3-GTP-C,S10-GTP-C,S11-GTP-C,SGs-1,SGs-2
,SLg-1,SLg-2,SLs-1,SLs-2

• sgsnw: CDR-FTP,CDR-GTP-P,CN-SS7-1,CN-SS7
-2,DNS,EBM,Filterlog,Gn-GTP-C,Gn-GTP-U,Iu-GT
P-U,Iu-SS7-1,Iu-SS7-2,LI-C,LI-U,NTP,OAM

• sgsnl: CDR-FTP,CDR-GTP-P,CTUM,DNS,EBM,F
ilterlog,Gn-GTP-C,LI-C,NTP,OAM,S1-MME-1,S1-
MME-2,S6a-1,S6a-2,S13-1,S13-2,S3-GTP-C,S10
-GTP-C,S11-GTP-C,SGs-1,SGs-2,SLg-1,SLg-2,S
Ls-1,SLs-2

Default value: • sgsnlwg : No default

• sgsnwg : No default

• sgsnlg : No default

22 2/1546-AOM 901 079 Uen A | 2012-05-29

 Operands and Variables

• sgsng : No default

• sgsnlw : No default

• sgsnw : No default

• sgsnl : No default

Activation: Run-time. After activation of the planned area.

5.2.8 -ip ServiceIpAddress

The ServiceIpAddress parameter specifies the IP address to which an IP
service is connected.

Type: String

Syntax: IP address notation: [1-223].[0-255].[0-255].[0-255]

Values: 7-15 characters

Default value: No default

Activation: Run-time. After activation of the planned area.

2/1546-AOM 901 079 Uen A | 2012-05-29 23

 ENIQ Events Node Commissioning

24 2/1546-AOM 901 079 Uen A | 2012-05-29

 Glossary

Glossary

Glossary
The OSS Glossary is available in Reference
[1].

2/1546-AOM 901 079 Uen A | 2012-05-29 25

 ENIQ Events Node Commissioning

26 2/1546-AOM 901 079 Uen A | 2012-05-29

 Reference List

Reference List

[1] Operations Support System (OSS) Glossary, 0033-AOM 901 017/2

[2] OSS Library Typographic Conventions, 1/154 43-AOM 901 017/4

[3] ENIQ Events Supported Network Elements, 2/1029-AOM 901 079

[4] Ericsson Network IQ Events, System Administration Guide, 2/1543-AOM

901 079

[5] Operations Support System, Radio and Core (OSS-RC) CPI , EN/LZN
703 0129

[6] SGSN-MME 2011B CPI, EN/LZN 704 0106

2/1546-AOM 901 079 Uen A | 2012-05-29 27