Вы находитесь на странице: 1из 21

OSS-RC APG43L Setup

USER GUIDE

3/1531-AOM 901 092 Uen F


Copyright

© LM Ericsson Limited (LMI) 2014. All rights reserved. No part of this document
may be reproduced in any form without the written permission of the copyright
owner.

Disclaimer

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

3/1531-AOM 901 092 Uen F | 2015-04-29


Contents

Contents

1 About This Document 1


1.1 Purpose 1
1.2 Target Groups 1
1.3 Prerequisites 1
1.4 Typographic Conventions 1

2 APG43L 3
2.1 APG43L User Management 3
2.2 APG43L Connection Modes 3
2.3 Destination and Destination Sets 5
2.4 Creating and Associating Transfer Queues to Destinations 7
2.5 Creating and listing the CP Volumes 8
2.6 Defining the CP Files 9
2.7 STS for APG43L 11
2.8 Configuring Alarm Routing in APG43L 12

Glossary 15

Reference List 17

3/1531-AOM 901 092 Uen F | 2015-04-29


OSS-RC APG43L Setup

3/1531-AOM 901 092 Uen F | 2015-04-29


About This Document

1 About This Document

This chapter contains the following elements:

• Purpose

• Target groups

• Prerequisites

• Typographic conventions

1.1 Purpose
This document describes the tasks involved in setting up the OSS dependent
configuration of the APG43L.

1.2 Target Groups


The intended target groups for this document are the following:

• System Administrator

• Installation Engineer

• Field Technician

1.3 Prerequisites
It is assumed that the reader of this document:

• Has general knowledge of the AXE System.

1.4 Typographic Conventions


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

3/1531-AOM 901 092 Uen F | 2015-04-29 1


OSS-RC APG43L Setup

2 3/1531-AOM 901 092 Uen F | 2015-04-29


APG43L

2 APG43L

Purpose:

This Instruction describes the procedure to set up a BSC/MSC/MSC-S DB


/MSC-S BC equipped with APG43L on OSS-RC.

Actions:

1. Setting up the users and accounts for accessing the APG43L - refer to
Section 2.1 on page 3.

2. Connecting to the Network Element - refer to Section 2.2 on page 3.

3. Creating destinations and destination sets - refer to Section 2.3 on page 5.

4. Creating and associating transfer queues - refer to Section 2.4 on page 7.

5. Creating CP Volumes - refer to Section 2.5 on page 8.

6. Defining CP Files - refer to Section 2.6 on page 9.

7. Setting up STS - refer to Section 2.7 on page 11.

8. Setting up Alarm routing - refer to Section 2.8 on page 12.

Note: Steps 2 to 8 mentioned above can also be performed by executing the


script OSS_APG43LNode_configuration_Setup.sh Reference [11]

Before running the OSS_APG43LNode_configuration_Setup.sh script,


user needs to edit few parameters in the script, which is explained
in the comment part of the script.

2.1 APG43L User Management


In BSC/MSC/MSC-S DB /MSC-S BC equipped with APG43L, users are
authenticated by matching their username and password to credentials stored
in OSS-RC LDAP.
For a detailed description on setting up roles, aliases, target and target groups
and LDAP administration see Reference [3] and Reference [6].

2.2 APG43L Connection Modes


This chapter gives an overview of how to connect to a BSC/MSC/MSC-S DB
/MSC-S BC equipped with APG43L.
It also describes how to browse the APG43L Model and how to make and
show configuration changes.

3/1531-AOM 901 092 Uen F | 2015-04-29 3


OSS-RC APG43L Setup

2.2.1 Prerequisite

The Network Element should be added on OSS-RC. For further information


see Reference [4].

2.2.2 Actions
Connect to the BSC/MSC/MSC-S DB /MSC-S BC equipped with APG43L using
Command Handling Application (CHA) or WinFIOL.

2.2.3 Description
According to the command types to be issued in APG43L, connection between
OSS and an AXE-based NE can be established in two ways:

1. AP session: In an AP session, the COM CLI is used for the purpose


of O&M configuration. This session allows the performing of model
configuration operations and the execution of AP commands. The prompt
for this session always ends with the symbol “>”.

2. MML session: This is used for the execution of MML commands: this
session allows a direct connection towards the CP part of the AXE node.
The prompt symbol for the MML Session is “<”.

To Switch between Modes:

1. AP to MML: Execute “mml” command to get MML Session. To revert back


to AP Mode again, use the “exit;” command.

2. MML to AP: Execute “APLOC;” command to get AP Session. To revert


back to MML Mode again, use the “exit” command.

In an AP session, the COM CLI is used for O & M configuration. This session
allows the user perform model configuration operations.
For a detailed description on how to use the COM CLI for model configuration
operations, see Reference [5].

Note: The <NodeName> field which is used in subsequent chapters is the


value readable from the object with DN ManagedElement.
For example:
>configure
(config)>show
ManagedElement=<NodeName>
(config)>

In this example, Node Name is the name of the Managed Element. The
value of the Managed Element defined in this MO should be the same
as that which is used in the Managed Element Id field while adding
the Network Element into OSS-RC by using Add Remove Network
Element (ARNE).

4 3/1531-AOM 901 092 Uen F | 2015-04-29


APG43L

2.3 Destination and Destination Sets


This chapter describes how destination and destination sets can be created,
listed and verified in APG43L.

2.3.1 Actions

1. Create the Responding destinations and destination sets.

• A. Enter Config Mode.


>configure
(config)>

• B. Navigate to the FileTransferManager MO.


(config)>ManagedElement=<NodeName>, SystemFunctions=1,AxeFu
nctions=1,DataOutputHandling=1,DataTransferM=1,FileTransferMan
ager=1

• C. Create the Responding destination Set.


(config-FileTransferManager=1)>RespondingDestinationSet=OSSCP
FILESSET

• D. Create the destination under it.


(config-RespondingDestinationSet=OSSCPFILESSET)>PrimaryRespo
ndingDestination=OSSCPFILES

• E. Set the OSS-RC Master Server IP Address


(config-PrimaryRespondingDestination=OSSCPFILES)>ipNotificationA
ddress=<OSS IP>

• F. Set the OSS port which will receive file notifications. While configuring
multiple Network elements, distribute the BSCs/MSC/MSC-S DB/
MSC-S BCs among the five ports from the below range with respect to
the Node that is being used. Values can be from the following range:

0 BSCs/MSC/MSC-S DB: [65506-65510]

0 MSC-S BC : [50185–50189]

Note: The same file notification port will be used by APG43


Windows and Linux for MSC-S BC.

(config-PrimaryRespondingDestination=OSSCPFILES)>portNotificat
ionNumber=<OSS Port>

• G. Move up to parent MO.


(config-PrimaryRespondingDestination=OSSCPFILES)>up
(config-RespondingDestinationSet=OSSCPFILESSET)>

• H. Set the AdvancedRespondingParameters MO.

3/1531-AOM 901 092 Uen F | 2015-04-29 5


OSS-RC APG43L Setup

(config-RespondingDestinationSet=OSSCPFILESSET)>AdvancedRes
pondingParameters=OSSCPFILESSET

• I. Set the inhibitTransferQueueNamePrefx attribute.


(config-AdvancedRespondingParameters=OSSCPFILESSET)>inhibit
TransferQueueNamePrefx=true

Note: This step should not be performed for OSSSTSSET destination


set.

• J. Commit and Return to top MO


(config-RespondingDestinationSet=OSSCPFILESSET)>commit

Note: For APG34L2.0 or later on successful execution of commit


command the CLI switches to exec mode with same MO
position.

(config-RespondingDestinationSet=OSSCPFILESSET)>top
(config)>

• K. Follow the same procedure from steps B to J and create


OSSSTSSET destination set and OSSSTS destination under it.
Step I should not be performed for OSSSTSSET.

• L. In order to list the destinations and destination sets created


as part of the earlier steps, issue the show all command in the
FileTransferManager MO. This is not a mandatory step.
(config)>ManagedElement=<NodeName>, SystemFunctions=1,AxeFu
nctions=1,DataOutputHandling=1,DataTransferM=1,FileTransferMan
ager=1
(config-FileTransferManager=1)>show all
(config-FileTransferManager=1)>top
(config)>

2. Verify the Connectivity:

• A. Navigate to FileTransferManager MO
(config)>ManagedElement=<NodeName>, SystemFunctions=1,AxeFu
nctions=1,DataOutputHandling=1,DataTransferM=1,FileTransferMan
ager=1

• B. Enter the OSSCPFILESSET Destination Set


(config-FileTransferManager=1)>RespondingDestinationSet=OSSCP
FILESSET

• C. Enter the OSSCPFILES Destination


(config-RespondingDestinationSet=OSSCPFILESSET)>PrimaryRespo
ndingDestination=OSSCPFILES

• D. Execute the action “connectionVerify”. A result showing “true”


implies a successful connectivity.

6 3/1531-AOM 901 092 Uen F | 2015-04-29


APG43L

(config-PrimaryRespondingDestination=OSSCPFILES)>connectionV
erify
true

• E. Return to top MO
(config-PrimaryRespondingDestination=OSSCPFILES)>top (config)>

• F. Follow the same steps from A to E and verify connectivity for the
OSSSTS destination under OSSSTSSET destination set.

• G. Exit Config Mode.


(config)>end
>

2.4 Creating and Associating Transfer Queues to


Destinations
This chapter describes the procedure involved in creating transfer queues and
associating them to destinations in APG43L.

2.4.1 Actions
1. Enter Config Mode.
>configure
(config)>

2. Navigate to FileTransferManager MO
(config)>ManagedElement=<NodeName>, SystemFunctions=1,AxeFunctio
ns=1,DataOutputHandling=1,DataTransferM=1,FileTransferManager=1
(config-FileTransferManager=1)>

3. Create the file transfer queue BARTRQ


(config-FileTransferManager=1)>FileTransferQueue=BARTRQ

4. Associate the transfer queue with the destination set and set the
AdvancedFileTransferQueueInfo MO
(config-FileTransferQueue=BARTRQ)>respondingDestinationSet=OSSC
PFILESSET
(config-FileTransferQueue=BARTRQ)>AdvancedFileTransferQueueInf
o=BARTRQ

5. Commit the changes and return back to FileTransferManager MO


(config-AdvancedFileTransferQueueInfo=BARTRQ)>commit

Note: For APG34L2.0 or later on successful execution of commit


command the CLI switches to exec mode with same MO position.

(config-AdvancedFileTransferQueueInfo=BARTRQ)>up
(config-FileTransferQueue=BARTRQ)>up

3/1531-AOM 901 092 Uen F | 2015-04-29 7


OSS-RC APG43L Setup

6. Follow the same Steps 3-5 and create transfer queues BCDCTRQ,
CDMTRQ, CERTRQ, CTRTRQ, MRRTRQ, MTRTRQ and RIRTRQ and
associate them to the OSSCPFILESSET destination set.

7. In order to list the transfer queues created as part of the steps above,
issue the show command in the FileTransferManager MO. This is not a
mandatory step.
(config-FileTransferManager=1)>show

8. Return to top MO and end the config session.


(config-FileTransferManager=1)>top
(config)>end
>

2.5 Creating and listing the CP Volumes


This chapter describes the procedures involved in listing and creating CP
volumes.

2.5.1 Actions
The CP volumes BTSVOLUMSW, EXCHVOLUME, TEMPVOLUME and
RELVOLUMSW are required for BSC.
EXCHVOLUME, TEMPVOLUME and RELVOLUMSW is created by default on
the APG; however BTSVOLUMSW have to be created manually by following
the procedure below. For more information on the CP File System management
see Reference [7].

1. Enter Config Mode.


>configure
(config)>

2. Navigate to the CpFileSystem MO


(config)>ManagedElement=<NodeName>, SystemFunctions=1,AxeFunct
ions=1, SystemHandling=1,CpFileSystemM=1
(config-CpFileSystemM=1)>

3. Create CP volumes and commit.


(config-CpFileSystemM=1)>CpVolume=BTSVOLUMSW
(config-CpVolume= BTSVOLUMSW)>up
(config-CpFileSystemM=1)>commit

Note: For APG34L2.0 or later on successful execution of commit


command the CLI switches to exec mode with same MO position.

4. In order to list the exchange volumes created as part of the earlier steps,
issue the show command in the CpFileSystemM MO. This is not a
mandatory step.
(config-CpFileSystemM=1)>show

5. Return to top MO

8 3/1531-AOM 901 092 Uen F | 2015-04-29


APG43L

(config-CpFileSystemM=1)>top
(config)>

6. Exit Config Mode.


(config)>end
>

2.6 Defining the CP Files


This chapter describes the general procedure to be followed for defining the CP
Files and associating them to transfer queues in APG43L.

2.6.1 Actions
Complete the actions below, by following the steps listed in the procedure
section of this chapter.

1. Define Mobile Traffic Recording (MTR) Files in BSC/MSC/MSC-S DB


/MSC-S BC for PMR.
Create 64 Files with names MTRFIL00, MTRFIL01, and so on until
MTRFIL63 is created.
Associate each file while creation to MTRTRQ transfer queue.

2. Define Cell Traffic Recording (CTR) Files in BSC for PMR.


Create File with name CTRFILE.
Associate the file while creation to CTRTRQ transfer queue.

3. Define Channel Event Recording (CER) Files in BSC for PMR.


Create 16 files with names CERFIL00, CERFIL01, and so on until
CERFIL15 is created.
Associate each file while creation to CERTRQ transfer queue.

4. Define Radio Interference Recording (RIR) Files in BSCfor RNO FAS


Measurements.
Create 10 files with names RIRFIL00, RIRFIL01 and so on until RIRFIL09
is created.
Associate each file while creation to RIRTRQ transfer queue.

5. Define BA-List Recording (BAR) Files in BSC for RNO NCS Measurements.
Create 10 files with names BARFIL00, BARFIL01 and so on until BARFIL09
is created.
Associate each file while creation to BARTRQ transfer queue.

6. Define Measurement Result Recording (MRR) Files in BSC for RNO.


Create 10 files with names MRRFIL00, MRRFIL01 and so on until
MRRFIL09 is created.
Associate each file while creation to MRRTRQ transfer queue.

7. Define BCDCFILE in the BSC for BSM.


Create file with the name BCDCFILE.
Associate the file while creation to BCDCTRQ transfer queue.

3/1531-AOM 901 092 Uen F | 2015-04-29 9


OSS-RC APG43L Setup

8. Define ROPCR Collection in BSC for CDM.


Create File with the name of ROPCRFILE.
Associate the file while creation to CDMTRQ transfer queue.

2.6.2 Procedure
1. Enter Config Mode.
>configure
(config)>

2. Navigate to the CpFileSystem MO


(config)>ManagedElement=<NodeName>,SystemFunctions=1,AxeFunc
tions=1,SystemHandling=1,CpFileSystemM=1
(config-CpFileSystemM=1)>

3. Go to the CP Volume EXCHVOLUME.


(config-CpFileSystemM=1)>CpVolume=EXCHVOLUME

4. Create the File.


(config-CpVolume=EXCHVOLUME)>InfiniteFile=<File Name>

5. Set overrideSubfileClosure parameter to true.


(config-InfiniteFile=<File Name>)>overrideSubfileClosure=true

6. Set the value of the recordLength to 512.


(config-InfiniteFile=<File Name>)>recordLength=512

7. Connect the file to the Transfer queue.


(config-InfiniteFile=<File Name>)>transferQueue=<Transfer Queue Name>

8. Go to the parent MO.


(config-InfiniteFile=<File Name>)>up
(config-CpVolume=EXCHVOLUME)>

9. Repeat Steps 4 to 8until all the files (mentioned in the preceding subsection)
have been created.

10. Commit the changes


(config-CpVolume=EXCHVOLUME)>commit

Note: For APG34L2.0 or later on successful execution of commit


command the CLI switches to exec mode with same MO position.

11. In order to list the files that were created as part of the earlier steps, issue
the show command. This is not a mandatory step.
(config-CpVolume=EXCHVOLUME)>show

12. Return to top MO


(config-CpVolume=EXCHVOLUME)>top
(config)>

13. Exit Config Mode.


(config)>end

10 3/1531-AOM 901 092 Uen F | 2015-04-29


APG43L

>

2.7 STS for APG43L


This chapter describes the procedure required to create, include and activate
Objects in the STS Database.

2.7.1 Actions
The recommended object types and recommendations relating to STS for BSC
are documented in Reference [8], Reference [9], Reference [10] and Reference
[12]
Use the general procedure below and include the object types in STS.

2.7.2 Procedure
1. Activate Object Types

• A. Enter Config Mode.


>configure
(config)>

• B. Navigate to ObjectTypes MO
(config)>ManagedElement=<Node Name>, SystemFunctions=1,Axe
Functions=1,DataOutputHandling=1,StatisticalCounterM=1,ObjectT
ypes=1

• C. Go to the object type


(config-ObjectTypes=1)>ObjectType=<ObjectType>
(config-ObjectType=<ObjectType>)>

• D. Set as included
(config-ObjectType=<ObjectType>)>isIncluded=true

• E. Return back to the ObjectTypes=1 MO


(config-ObjectType=<ObjectType>)>up

• F. Repeat steps C to E until all the object types that are desired are
included.

• F. Commit the changes


(config-ObjectTypes=1)>commit

Note: For APG34L2.0 or later on successful execution of commit


command the CLI switches to exec mode with same MO
position.

(config-ObjectTypes=1)>

• G.Return to top MO

3/1531-AOM 901 092 Uen F | 2015-04-29 11


OSS-RC APG43L Setup

(config-ObjectTypes=1)>top
(config)>

• Exit Config Mode.


(config)>end
>

2. Display the object types that were included in Step 1 and verify data
collection is enabled .

Execute the stmotls command.

2.8 Configuring Alarm Routing in APG43L


This chapter describes the procedure required to set-up alarm routing on the
APG43L.

2.8.1 Actions for BSC/MSC/MSC-S-DB/HLR


1. Enter Config Mode.
>configure
(config)>

2. Navigate to the PdsManager MO


(config)>ManagedElement=<NodeName>, SystemFunctions=1,AxeFunctio
ns=1,SystemHandling=1,AlphanumericDeviceM=1,PdsManager=1
(config-PdsManager=1)>
The AD devices in use can be printed by issuing show all on the
AlphanumericDeviceM MO.
For example:
(config-PdsManager=1)>up
(config-AlphanumericDeviceM=1)>show all
AlphanumericDeviceM=1
adhNextFreeAdDevice="AD-0"
MmlSessions=1
PdsManager=1
PdsIpClient=AD-120
prcaValues="30-40"
printoutFormat=TXT
queuedPrintouts=0
remoteIpAddress="10.45.18.194"
remotePort=65505
state=IDLE
moveQueuedPrintouts()
PdsIpClient=AD-122
prcaValues="30-40"
printoutFormat=TXT
queuedPrintouts=0
remoteIpAddress="10.45.18.194"
remotePort=65505
state=IDLE

12 3/1531-AOM 901 092 Uen F | 2015-04-29


APG43L

moveQueuedPrintouts()
moveQueuedPrintouts()
(config-AlphanumericDeviceM=1)>PdsManager=1
(config-PdsManager=1)>

In this example above AD-120 and AD-122 are occupied.

3. Specify the AD device which are not occupied.


(config-PdsManager=1)) >PdsIpClient=<AD device>

Note: This attribute defines the AD device associated with the Printout
Destination Service. Range is from AD-0.. to AD-1023.

4. Set the PRCA number which will be used.


(config-PdsIpClient=<ADDevice>)>prcaValues="32,35,37-46,48,49,51-5
6,57,58,69"

5. Set the printout format as TXT


(config-PdsIpClient=<ADDevice>)>printoutFormat=TXT

6. Specify the Port number at which OSS will receive the alarms.
(config-PdsIpClient=<ADDevice>)>remotePort=65505

7. Set the OSS Master Server IP address where the alarm printouts will be
received.
(config-PdsIpClient=<ADDevice>)>remoteIpAddress=<OSS IP>

8. Commit the changes


(config-PdsIpClient=<ADDevice>)>commit

Note: For APG34L2.0 or later on successful execution of commit


command the CLI switches to exec mode with same MO position.

9. Return to top MO
config-PdsIpClient=<ADDevice>)>top
(config)>

10. Exit Config Mode.


(config)>end
>

2.8.2 Actions for MSC-S BC/HLR BS


The actions for these nodes are as above in 2.8.1.
In step 6, the remotePort is 50184, i.e. remotePort=50184.

3/1531-AOM 901 092 Uen F | 2015-04-29 13


OSS-RC APG43L Setup

14 3/1531-AOM 901 092 Uen F | 2015-04-29


Glossary

Glossary

Glossary
The OSS Glossary is included in Operations
Support System (OSS) Glossary, Reference
[1].

3/1531-AOM 901 092 Uen F | 2015-04-29 15


OSS-RC APG43L Setup

16 3/1531-AOM 901 092 Uen F | 2015-04-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] Node Centralized User Management Integration Guide for OSS-RC,


1/1553-AOM 901 092

[4] OSS RC Network Element Commissioning, 1546-AOM 901 122

[5] COM Management Guide , 4/198 17-CXA 118 01, Available from the
COM support Library

[6] COMInf SUN Directory Server, System Administration Guide,


13/1543-APR 901 0124

[7] CP File System Management User Guide , 1/198 17-CNZ 217 3037,
available in the relevant AXE library.

[8] BSC Object Types and Counters , 3/198 17-APT 210 09, available in the
relevant AXE library.

[9] BSC STS Configuration , 2/198 17-APT 210 09, available in the relevant
AXE library.

[10] BSS KPI and PI Recommendations , 215/10056-HSC10312, available


in the relevant AXE library

[11] OSS_APG43L Node_configuration_Setup sh , 1/190 31-AOM 901 092,


Contact Local Ericsson Support.

[12] MSC GSM/WCDMA Performance Indicator, 1/1551-CSA 121 01/7,


available in the relevant AXE library.

3/1531-AOM 901 092 Uen F | 2015-04-29 17