Activación de Contadores - OSS-RC DITP for Adding New LTE PM Counters for CIS Step 2

Ericsson InternalLTE COUNTER ACTIVATION 1 (31)

Prepared (Subject resp) No.

NRJ/OR/SE/T Ashok Selvaraj 1/1546-FCP 130 5247 UenApproved (Document resp) Checked Date Rev Reference

NRJ/OA/RR [Karuvaul Joji Philip] 2012-10-17 A

OSS-RC DITP - OSS RC #6 CIS Step 2.1 Trial LTE counter activation

Date 2012/10/17 (Wed)

Customer SBM

Region Tokyo

Target OSS-RC

Tokyo OSS-RC LTEtssrns061 : 172.17.10.15 (Master)citrix_RAN06_tssrap061e : 172.17.10.179 (Citrix#1)citrix_RAN06_tssrap062e : 172.17.10.182 (Citrix#2)

NE Type on OSS-RC( e Node b)

E Node b

Target Node33097_L2G-MIMOMI (10.243.44.162)34823_L2G-NISHIOOTOMO (10.243.29.98)32945_L2G-MAKUHARI (10.243.25.2)

Project Manager Karuvaul Joji Philip (080-4122-8740)

OSS-RC Engineer

1st Warwick Ownhouse (080-4184-2584)

2nd

RAN Engineer S Ashok (080-4631-7779)

OSS-RC Work place Yokohama Office (Remote)

WOT 【11453770A】





Contents1 Revision Information............................................................................32 Introduction..........................................................................................33 Environment.........................................................................................34 Prerequisites........................................................................................35 Impact..................................................................................................46 Risk and Preventive Action..................................................................47 10 Basic Rules.....................................................................................48 Procedure............................................................................................59 DITP...................................................................................................2810 Check List..........................................................................................3011 References.........................................................................................31





1 Revision Information

Revision Date Author Description

PA1 2012/10/12 Ashok Selvaraj First Release Revision

2 Introduction

2.1 Scope

This document describes the activation of a trail period counter profile activation of 1 week for CIS Step 2.1 on 3 ENodeB using Tokyo OSS-RC LTE server.

2.2 Typographic Conventions

# is as root user.

$ is as nmsadm user.

> is as normal user.

3 Environment

3.1 Software

OSS-RC software level: OSS-RC O12.2

(If the software level is different with above stated sw level, then this document will be not applicable.)

4 Prerequisites

4.1 General

The followings are required before the integration.

OSS-RC is up and running. E Node b is connected and running successfully on network.





5 Impact

N/A

6 Risk and Preventive Action

No Risk Preventive Action

1 Ping to wrong IP address Confirm the target node IP address in CDR

2 Login to SBM network by mistake Confirm if VNC/CRASS VM IP address and port number are correct

3 Login to wrong SBM server Confirm the server name is Tokyo Citrix name in CDR

7 10 Basic Rules

No Slogan Details

1 TBM/KY Have an internal risk analysis and KY confirmation with customer

2 Confirmation Rounded Number Plate and Allocation Table Confirm the target nodes in CDR

3 Marking for Target Nodes Not applicable

4 Curing and Tape Separation Not applicable

5 Reference by pointing Perform it when processing the activity with target node

6 Double & Addressing Check Perform it when processing the activity with target node and command

7 Fail-stop If any unexpected behaviour occurred visually after fixing process, stop the activity

8 3 seconds rule Not applicable





9 Ring through & Recommendation for removing cables Not applicable

10 Pre & Post confirmation Pre-meeting and KY-meeting

8 Procedure

8.1 KY meetingCheck below items by Customer and Ericsson team

1. OSS-RC name to log in Tokyo OSS-RC RAN #6

tssrns061 : 172.17.10.15 (Master)citrix_RAN06_tssrap061e : 172.17.10.179 (Citrix#1)citrix_RAN06_tssrap062e : 172.17.10.182 (Citrix#2)

E/// : □ / SBM : □

2. VNC Address & Port that Ericsson engineer will useIP Address: E/// : □ / SBM: □PortNumber: E/// : □ / SBM : □





8.2 Open iWorks

1. Confirm iWorks Number. Then click link in the email. E/// : □ / SBM : □

2. Input username and password. Then click “OK” E/// : □ / SBM : □

Click here

Input hereInput here

Click here





3. Confirm that it is for today’s activity. Then click "開始". E/// : □ / SBM : □

4. Input your name in “作業実施者”. Then click “登録” E/// : □ / SBM : □

Click here

Input here

Click here





8.3 Pre Health check

8.3.1 Health Check on OSS

$ tcsh$ uname –a

Confirm that we logged in to the target node. E///: □ / SBM : □[RAN06_tssrap061e : 172.17.10.179 (Citrix#1)]

$ date$ ls –ltr /var/adm

Confirm that there are messages file. E/// : □ / SBM : □$ more /var/adm/messages* (check citrix side system logs) Confirm that hardware error has not been output. E/// : □ / SBM : □$ prstat -aL (repeat 2-3 times at least to see if Citrix’s performance changes) Confirm the load in the Citirix server. E/// : □ / SBM : □$ df –h | less Confirm the root is less than 80% and the percentage of segment1.E/// : □ / SBM : □$ rlogin mashost (login to masterserver)$ tcsh$ uname –a Confirm that we logged in to the target node.[RAN06_tssrns061 : 172.17.10.15 (Master)] E/// : □ / SBM : □

$ ls –ltr /var/adm Confirm that there are messages file. E/// : □ / SBM : □$ more /var/adm/messages* (check masterserver side system logs) Confirm that hardware error has not been output. E/// : □ / SBM : □$ prstat -aL Confirm the load in the master server. E/// : □ / SBM : □$ df –h | less Confirm the usages of each volume. E/// : □ / SBM : □$ smtool –l | grep –v started (to see process status) Confirm the failure is not output. E/// : □ / SBM : □$ su - (login as root)# ist_run Confirm OSS version. E/// : □ / SBM : □# hastatus –sum Confirm that master server is ONLINE. E/// : □ / SBM : □

(Sybase is ONLINE on mate server.)# exit $ rlogin tssrns042$ tcsh$ uname –a

Confirm that we logged in to the target node. E/// : □ / SBM : □[citrix_RAN06_tssrap062e : 172.17.10.182 (Citrix#2)]





$ ls –ltr /var/adm Confirm that there are messages file. E/// : □ / SBM : □$ more /var/adm/messages* (check materserver side system logs) Confirm that hardware error has not been output. E/// : □ / SBM : □$ prstat –aL Confirm the load in the mate server. E/// : □ / SBM : □$ df –h | less Confirm the usages of each volume. E/// : □ / SBM : □$ exit E/// : □ / SBM : □$ exit (return to masterserver) E/// : □ / SBM : □$ telnet eniqservice E/// : □ / SBM : □>uname –a Confirm that we logged in to the target node. E/// : □ / SBM : □>svcs –a | grep -i eniq (check the processes for the eniq) Confirm the necessary services are online. E/// : □ / SBM : □>engine status Confirm the engine running. E/// : □ / SBM : □>date>exit

1.1.1 Loading status check on ENIQ

Launch Web Brouser(right-click -> Sun Tools -> Web Browser)

E///: □ / SBM: □

Type URL[ 172.19.11.129:8080/adminui ]Username : eniqPassword : eniq E/// : □ / SBM : □

Click "System Status" and then, check the eniq statusIf there is at least one yellow and red circle, stop activity and follow escalation procedure

8.4 Pre activity health check of e Node b’s

l+ CIS21_EnodeB_Trial_Counter_Activation_yyyymmdd_hhmm.log

> cvls

> alt





> lgaevsmour 1

> lh ommp capi tot

Use TP server to login to e Node b’s involved in this activity and perform basic health check by running command file “e Node b’s basic health Check.mos”. Check for any abnormality in e Node b’s and take a decision to go ahead or suspend the activity. Observe MP load on O&M MPs.

8.5 Check existing PM counter profiles in e Node b’s

Run command pst to check all the PM counter user profile existing in the e Node b’s. This command is also included in health check command file.

>PST================================================================================ PROXY SCANNER-NAME STATE================================================================================ 4 PREDEF.PRIMARY.STATS ACTIVE 5 PREDEF.RBS.GPEH SUSPENDED 6 USERDEF.National_RBS_P7_CYCM19-25.Profile=SP_ID_129d0cdb9847051350867e73d70e3.Continuous=Y.STATS ACTIVE================================================================================>>> Total: 3 Scanners

8.6 New Counter profile creation and activation for e Node b’s in OSS RC

1. Log onto OSS. Right Click and select Performance à Initial Data Collection à WCDMA/LTE RAN measurements. This will open Data collection subscription profiles (PMR GUI) as shown in below picture.

2. In PMR GUI click on tab “user defined statistics profile” as shown in below picture





3. Step2 above will open tab shown in below picture n PMR GUI click on tab “user defined statistics profile” as shown in below picture

4. Right click on open area and select option “Add Profile” as shown in below picture





5. Select option “user defined statistical profile” and click next as shown in below picture

6. Input the name of new profile with the comments in the next window as per the example shown in below picture.

Enter user name for the profile: CIS Step 2.1 LTE Trial





Enter comment for the profile: Trial activation of LTE counters for a period of 1 week from 17/10/2012 until 24/10/2012.





7. Select profile type as “standard statistics” and click next as shown in below picture.

8. Select Network Element type as “e RBS Network elements…“and click next as shown in below picture.

9. Select e RBS’s to observe from available e RBS’s list and click next as shown in below picture. Please select the following e RBS’s list whereby new counters are to be activated.





33097_L2G-MIMOMI (10.243.44.162)34823_L2G-NISHIOOTOMO (10.243.29.98)32945_L2G-MAKUHARI (10.243.25.2)





10. Search for the counters to be added as shown in below picture.

11. Once desired counter has been found click right arrow button to include it for measurement as shown in below picture.





Counters to be added:MO CounterIPINTERFACE pmIfStatsIpOutDiscardsIPINTERFACE pmIfStatsIpOutRequestsIPINTERFACE pmIfStatsIpUnknownProtosIPINTERFACE pmIpIfStatsHCInOctetsIPINTERFACE pmIpIfStatsHCOutOctetsIPINTERFACE pmIpIfStatsHCInReceivesIPINTERFACE pmInDiscPolicyIPINTERFACE pmIpIfStatsHCOutTransmitsIPINTERFACE pmIfStatsIpAddrErrorsIPINTERFACE pmIfStatsIpInDiscardsIPINTERFACE pmIfStatsIpInHdrErrorsIPINTERFACE pmIfStatsIpInReceivesIPACCESSHOSTET pmIcmpInTimeExcdsIPACCESSHOSTET pmIpPortUnreachableIPACCESSHOSTET pmIpReasmFailsIPACCESSHOSTET pmIpInDiscardsIPACCESSHOSTET pmIpInHdrErrorsIPACCESSHOSTET pmIpInUnknownProtosIPACCESSHOSTET pmIpOutDiscardsIPACCESSHOSTET pmIpOutRequestsIPACCESSHOSTET pmUdpInErrorsIPACCESSHOSTET pmIpInAddrErrorsIPACCESSHOSTET pmIpInReceives





12. Perform above step for all the counters that are to be included in measurement and then click next as shown in below picture.

13. Select schedule type to “Continuous” and click finish as shown in below picture.





14. Check newly created profile exists in “inactive state”, right click and select “resume profile” option and confirm it when being asked, as shown in below picture.

15. Check newly created profile exists in “active state” now as shown in below picture. During this step OSS-RC will activate counters in e RBS’s.





8.7 Check existing PM counter profiles in e RBS’s

Run command pst to check all the PM counter user profile existing in the e Node b’s. Check newly created PM counter

8.8 Post activity health check of e Node b’s

Use TP server to login to e RBS’s involved in this activity and perform basic health check by running command file “e RBS’s basic health Check.mos”. Check for any abnormality in e RBS’s and take a decision to go ahead or suspend the activity. Observe MP load on O&M MPs to see if new counters have increased MP load.

8.9 e RBS’s Fallback

If fallback is required following steps will be followed

1. Follow steps 7.7 (1) to 7.7 (3)

2. In tab “user defined statistics profile” select the newly defined profile for e RBS’s and right click it and choose option “Suspend Profile” as shown in below picture





3. Now In tab “user defined statistics profile” select the newly defined profile for e RBS’s and right click it and choose option “Delete Profile” as shown in below picture





8.10

8.11 Confirmation new counter on OSS

8.11.1 Confirmation of e RBS’s counter

>cd .. E/// : □ / SBM : □

>ls

Confirm there is "MeContext=target node" E/// : □ / SBM : □

>cd MeContext="target node" E/// : □ / SBM : □

>ls –ltr | tail -5 E/// : □ / SBM : □

>grep [new counter name] [the newest file name]

Confirm there is "<mt>new counter name</mt>". E/// : □ / SBM : □

8.12 Confirmation new counter on ENIQ

8.12.1 Check e RBS’s counter

$telnet eniqservice E/// : □ / SBM : □

Log in as dcuser to ENIQ server

>isql -Udc -Pdc -Sdwhdb -w10000 E/// : □ / SBM : □

Check 1 RNC counter

1> select distinct datetime_id, pmRlAddAttemptsBestCellPacketLow,oss_id from DC_E_RAN_UCELL_RAW where datetime_id >= "2012-08-22 10:00 and pmRlAddAttemptsBestCellPacketLow != NULL

2> go E/// : □ / SBM : □





8.12.2 Loading status check on ENIQ

Launch Web Browser(right-click -> Sun Tools -> Web Browser)

E/// : □ / SBM : □

Type URL[ 172.19.11.129:8080/adminui ]Username : eniqPassword : eniq E/// : □ / SBM : □

Click "System Status" and then, check the eniq statusIf there is at least one yellow and red circle, stop activity, and call to RAN engineer.

E/// : □ / SBM : □

8.13 Post Health check

$ date$ uname –a Confirm that we logged in to the target node. E/// : □ / SBM : □

[RAN06_tssrns061 : 172.17.10.15 (Master)]$ ls –ltr /var/adm Confirm that there are messages file. E/// : □ / SBM : □$ more /var/adm/messages* (check masterserver side system logs) Confirm the hardware error has not been output. E/// : □ / SBM : □$ prstat -aL (repeat 2-3 times at least to see masterserver’s performance) Confirm the load in the master server. E/// : □ / SBM : □$ df –h | less Confirm the usages of each volume. E/// : □ / SBM : □$ smtool –l | grep –v started (to see process status) Confirm the failure is not output. E/// : □ / SBM : □$ su - (login as root)# ist_run Confirm OSS version. E/// : □ / SBM : □# hastatus –sum Confirm the master server is ONLINE. E/// : □ / SBM : □

(Sybase is ONLINE on mate server.)# exit





$ rlogin tssrns042$ tcsh$ uname –a Confirm that we logged in to the target node. E/// : □ / SBM : □

[RAN06_tssrap061e : 172.17.10.179 (Citrix#1)]$ ls –ltr /var/adm Confirm that there are messages file. E/// : □ / SBM : □$ more /var/adm/messages* (check materserver side system logs) Confirm the hardware error has not been output. E/// : □ / SBM : □$ prstat –aL Confirm the load in the mate server. E/// : □ / SBM : □$ df –h | less Confirm the usages of each volume. E/// : □ / SBM : □$ exit$ exit (return to masterserver)$telnet eniqservice E/// : □ / SBM : □>uname –a Confirm that we logged in to the target node. E/// : □ / SBM : □>svcs –a | grep -i eniq (check the processes for the eniq) Confirm the necessary services are online. E/// : □ / SBM : □>engine status Confirm the engine running. E/// : □ / SBM : □> exit (return to masterserver)$ exit$ exit (return to Citrix#1) E/// : □ / SBM : □$ uname –a

Confirm that we logged in to the target node. E/// : □ / SBM : □[citrix_RAN06_tssrap062e : 172.17.10.182 (Citrix#2)]

$ ls –ltr /var/admConfirm that there are messages file. E/// : □ / SBM : □

$ more /var/adm/messages* (check citrix side system logs) Confirm the hardware error has not been output. E/// : □ / SBM : □$ prstat -aL (repeat 2-3 times at least to see if Citrix’s performance) Confirm the load in the Citirix server. E/// : □ / SBM : □$ df –h | less Confirm the usages of each volume. E/// : □ / SBM : □$ date





Close iWork’s

1. Confirm iWork’s Number. Then click link in the email. E/// : □ / SBM : □

2. Input username and password. Then click “OK” E/// : □ / SBM: □

Click here

Click here

Input here





3. Confirm that it is for today’s activity. Then click "終了". E/// : □ / SBM : □

4. Input your name in “作業実施者”. Then click “登録” E/// : □ / SBM : □

8.14 KY meeting

Report the results of activity and log out from SBM network.

Click here

Click here





9 DITP

The yellow parts stand for "Risk and Preventive Action".

Start time: 14:00 a.m.

Item ContentPlanned Time Actual Time Procedure

No# Check

Start End Start End E/// SBM

1 Start of the Activity

1.1 Pre-meeting & KY-meeting 14:00 10:15 8.1

1.2 Open iWorks 10:15 14:17 8.2

1.3 Login to SBM network remotely and confirm the target server by customer

14:17 14:25

2 Preparation

2.1 Pre health check on OSS-RC 14:25 14:40 8.3.1

2.2 Loading status check on ENIQ 14:40 14:45 8.3.2

3 Confirmation new counters

3.1 Pre activity health check of e Node b’s

14:45 14:50 8.4.

3.2 Check existing PM counter profiles in of e Node b’s

14:50 14:55 8.5

3.3 New Counter profile creation and activation for of e Node b’s in OSS RC

14:55 15:05 8.6

3.4 Check existing PM counter profiles in of e Node b’s

15:05 15:15 8.7

3.5 Post activity health check of of e Node b’s

15:15 15:25 8.8





Item ContentPlanned Time Actual Time Procedure

No# Check

Start End Start End E/// SBM

4Confirm the counter on OSS and ENIQ

4.1 Confirm new counters on OSSCheck 1 e RBS counter 15:25 15:45

8.10.1

4.2 Confirm new counters on ENIQCheck1 e RBS counter 13:45 16:00

8.11.1

5 Post Health Check

5.1 Loading status check on ENIQ 16:00 16:15 8.11.2

5.2 Post health check on OSS-RC 16:15 16:25 8.12

6 Finish this activity

6.1 Close iWorks 16:25 16:30 8.13

6.2 Post-meeting & KY-meeting

Logout from SBM network Confirm target server by the customer

16:30 16:35 8.14

6.3 Send a report to PM as follows

[1] Activity result

[1] DITP

[2] Log

[3] Active counter lists

(The report will be sent to customer later by PM)

16:35 16:45 -





10 Check ListAuthor Name Ashok Selvaraj

Reviewer Name

Item No Category Check point Author

CheckReviewerCheck

1 Time Allocation

Activities which impact live traffic are clearly described. (If applicable)

2012/10/12OK

2012/10/12OK

2 Time Allocation Customer decision points for Rollback are clear 2012/10/12

OK2012/10/12

OK

3 Time Allocation Any impacts are described 2012/10/12

OK2012/10/12

OK

4 Time Allocation

If another node Engineers are involved in the activity, make sure contact point to them

2012/10/12OK

2012/10/12OK

5 Time Allocation

Implementation time is matched to related nodes activity's document.

2012/10/12OK

2012/10/12OK

6 Rollback Activities which impact live traffic are clearly described. (If applicable)

2012/10/12OK

2012/10/12OK

7 Call FlowInformation about names of person, department and telephone number for Customer and Ericsson are correctly filled in (Refer to CPM's information)

2012/10/12OK

2012/10/12OK

8 Call Flow Health-check item is included 2012/10/12OK

2012/10/12OK

9 Call Flow Activity Date is correctly filled in 2012/10/12OK

2012/10/12OK

10 Call Flow Sensitive activity is highlighted. (If applicable) 2012/10/12OK

2012/10/12OK

11 Other Activity risk is clearly described. (If applicable) 2012/10/12OK

2012/10/12OK

12 Other Expected result is clearly described 2012/10/12OK

2012/10/12OK





11 References1. OSS-RC Procedure - Login to Customer Network -.doc

(NRJ-12:004514 Uen)

Activación de Contadores - OSS-RC DITP for Adding New LTE PM Counters for CIS Step 2

Documents

Transcript of Activación de Contadores - OSS-RC DITP for Adding New LTE PM Counters for CIS Step 2