03 02 rn33153en10gla0 rncoam service terminal excercise

8/18/2019 03 02 RN33153EN10GLA0 RNCOAM Service Terminal Excercise

http://slidepdf.com/reader/full/03-02-rn33153en10gla0-rncoam-service-terminal-excercise 1/16

© Nokia Siemens Networks 1 (16)

RNC Service Terminal

Exercises




2 (16) © Nokia Siemens Networks

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Siemens Networks trainingdocumentation, product documentation and slide presentation material, all of which are

forthwith known as Nokia Siemens Networks training material, are the exclusive property ofNokia Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification,translation, adaptation or derivatives including any improvements or developments. NokiaSiemens Networks has the sole right to copy, distribute, amend, modify, develop, license,sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individualscan use the Nokia Siemens Networks training material for their own personal self-development only, those same individuals cannot subsequently pass on that same IntellectualProperty to others without the prior written agreement of Nokia Siemens Networks. The NokiaSiemens Networks training material cannot be used outside of an agreed Nokia SiemensNetworks training session for development of groups without the prior written agreement ofNokia Siemens Networks.

Indemnity

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement underwhich the document is submitted, and no part of it may be used, reproduced, modified ortransmitted in any form or means without the prior written permission of Nokia SiemensNetworks. The document has been prepared to be used by professional and properly trainedpersonnel, and the customer assumes full responsibility when using it. Nokia SiemensNetworks welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively ina separate agreement between Nokia Siemens Networks and the customer. However, NokiaSiemens Networks has made all reasonable efforts to ensure that the instructions contained inthe document are adequate and free of material errors and omissions. Nokia SiemensNetworks will, if deemed necessary by Nokia Siemens Networks, explain issues which may

not be covered by the document.Nokia Siemens Networks will correct errors in the document as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY MONETARYLOSSES,SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESSINTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THEUSE OF THIS DOCUMENT OR THE INFORMATION IN IT

This document and the product it describes are considered protected by copyrights and otherintellectual property rights according to the applicable laws.

Wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective

owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2007. All rights reserved.





Contents

1. Objectives....................................................................................4

2. Starting Service Terminal Session............................................5

2.1 Local Service Terminal Session ...................................................5

2.2 Load Service Terminal from MMI session ....................................6

2.3 Load Service Terminal from Other Service TerminalSession.........................................................................................7

3. Service Terminal Extension Handling ......................................9

3.1 Service Terminal Extension in DMX Unit......................................9

3.2 Service Terminal Extension in Chorus Unit ..................................9

4. Adding/Updating RNC Delivery Number ................................10

5. HMS Extension and Interface ..................................................12

5.1 HMS Extension General Usage..................................................12

5.2 Updating HMS SW......................................................................13

6. RNC Problem Reporting...........................................................15

6.1 Displaying Computer and System Log .......................................15

6.2 Displaying Unit Blackbox ............................................................15

6.3 Unit Start-up Log.........................................................................16





1. Objectives

After completing this learning element exercise, participant should beable to:

• Start service terminal session in RNC locally and remotely.

• Handle service terminal extension on DMX and Chorus units

• Use service terminal extensions for operation and maintenancetasks, e.g.

o Add/Update RNC Delivery Number

o Update HMS node SW

o RNC Problem Reporting





2. Starting Service Terminal Session

2.1 Local Service Terminal Session

Before you start, load an MMI session on a workstation (PC) andprepare a serial connection on separate workstation with the followingproperties,

• Bit rate 9600 bit/s

• 7 data bits

• Even parity

• 2 stop bits

The service terminal interface on a computer unit is implemented byusing RJ45 connector. The cabling configuration is shown on thefollowing figure

Figure 1. Service Terminal Interface Cabling

Number of service terminal interface on a computer unit depends oncomputer unit type. The interface is normally labelled SER

1. Interrogate the physical address of the following computer unitsusing MMI.

Computer unit Command Physical address

ICSU 0

ICSU 1

DMPG 0

DMPG 1





2. Load service terminal session by connecting the workstation withserial connection to the computer units, give username andpassword if required (default is SYSTEM/SYSTEM). Copy theservice terminal prompt to the following table.

Computer unit Prompt

ICSU 0

ICSU 1

DMPG 0

DMPG 1

3. Compare the physical address on MMI (number 1) to computerunit address on service terminal prompt (number 2) and state thedifference (if any).

Note: Disconnect the cable from computer unit will close the session

2.2 Load Service Terminal from MMI session

Service terminal session is handled on DD_ (Remote Debugger SessionCommand) command group. There are two options to execute a serviceterminal command,

S: ..... START REMOTE SESSIONE: ..... EXECUTE DEBUGGER COMMAND

1. Start a remote service terminal session to the computer units byexecuting "S" command.

Computer unit Command Prompt

ICSU 0

ICSU 1

2. State the difference in service terminal prompt (if any) compare tolocal session (section 2.1 no. 2)

3. Display the main level menu of service terminal session

Command: ________________________________________

4. Exit from the service terminal session back to MMI session

Command: ________________________________________





5. Display the main level menu of computer unit above withoutleaving the MMI session. Use "E" command

Command: ________________________________________

6. Start a remote service terminal session to the computer units byexecuting "S" command.

Computer unit Command Prompt

DMPG 0

DMPG 1

7. State the difference in service terminal prompt (if any) compare tolocal session (section 2.1 no. 2)

8. Display the main level menu of service terminal session

Command: ________________________________________

9. Exit from the service terminal session back to MMI session

Command: ____________________________ (3 possibilities)

2.3 Load Service Terminal from Other ServiceTerminal Session

It is also possible to load service terminal session to other computer unitwhile you are on service terminal session on a computer unit.

Note: the following exercise requires you to use local service session.

1. Load local service terminal session on a DMX computer unit.

2. Display the Remote Debugger Handling menu and read the HelpText

Command: ________________________________________

3. Start a remote session to another DMX computer.

Command: ________________________________________

Prompt : ________________________________________

4. Stop your remote session with command CTRL-@. What is yourprompt now?

Prompt : ________________________________________

5. Start another remote session to a different DMX computer. Exitthis session from the main level.

Command: ________________________________________





6. Show active sessions of the computer.

Command: ________________________________________

Session : ________________________________________

7. Disconnect existing sessions.

Command: ________________________________________

8. Start a remote service terminal session to a Chorus unit (useDMPG)

Command: ________________________________________

Prompt : ________________________________________

9. Display the available chorus unit commands with "help"

Command: ________________________________________





3. Service Terminal Extension Handling

3.1 Service Terminal Extension in DMX Unit

Extensions are a range of specific programs. The availability of modulesdepends on the type of the unit through which the session is established.To load an extension so it is "linked" to the main level menu, we need toinstall it first.

1. Display the syntax of the Extension Handling in DMX unit

Command: ________________________________________

2. Search all the available extensions from the chain.

Command: ________________________________________

3. Install VIM (Virtual MML Terminal) extension.

This extension is needed, when RNC access via a telnet(Ethernet) session is not available for any reason.

Command: ________________________________________

4. Display the port status and connect a disconnected port number

Command: ________________________________________

5. Disconnect from the port and remove the extension.

Command: ________________________________________

3.2 Service Terminal Extension in Chorus Unit

1. Start a service terminal session in Chorus computer unit (e.g.DMPG). List the service terminal extensions in Chorus unit

Command: ________________________________________

2. Service terminal extension in chorus unit is handled by usingcommand loadext. Display the command syntax of thiscommand.

Command: ________________________________________

3. Install extension called "connect"

Command: ________________________________________

4. Use "connect" command to load remote service terminal sessionon other computer (DMX or Chorus)

Command: ________________________________________





4. Adding/Updating RNC DeliveryNumber

The RNC delivery number must be added/updated correctly before theimplementation of RN2.2 SW release onward, in order to ensure thecapability of activating of new optional features controlled by licensekeys.

The complete instruction on adding/updating RNC delivery number isdescribed on "Software Implementation Q4 1.11-0" document.

1. Start service terminal session on active OMU.

Command: ________________________________________

2. Install MRS (Mixed Commands Handling) extension.Command: ________________________________________

3. Display the delivery number (known as C_NUMBER). of currentRNC

Note: the command information is simplified to "Where I am"

Command: ________________________________________

4. Install MAS (Mass Memory Handling) extension.

5. Patch APPARAGX.IMG and APPARAG2.IMG files on both disks

000X-MAS>VL:W0-/<current_SW_directory>/BLCODE/APPARAGX.IMG,4,100

000X-MAS>VL:W0-/<current_SW_directory>/BLCODE/APPARAG2.IMG,4,100

Notes:

• Be careful with number to be modified

• Exit editing mode by using CTRL+C and answer "Y" to write thechanging to disk.

Example:

The RNC delivery number is 052271





Figure 2. Example of adding/updating RNC delivery number





5. HMS Extension and Interface

5.1 HMS Extension General Usage

1. Start service terminal session on active OMU

2. Install HME (HMS extension)

Command: ________________________________________

3. Get the active line

Command: ________________________________________

Active line: ________________________________________

4. Get the temperature of OMU-1

Command: ________________________________________

5. Interrogate the status of OMU-0

Command: ________________________________________

6. Display the active HMS master address and interrogate the status,write down the HMMN SW version. Do the same for the bridgenode and a slave node

Command: ________________________________________

Master Node________ Bridge Node _______ Slave Node_______

7. Interrogate the equipment data of OMU-0

Command: ________________________________________

8. Compare this information with the concerning MMI command

Command: ________________________________________

9. Send a delay test to ICSU 3 node. Note delay

Command: ________________________________________

10. Now do the same to ICSU 3 SW. Compare the delay difference

Command: ________________________________________

11. Get the physical address of MXU 3 with MML and use HME to lookup HMS address

Command: ________________________________________





5.2 Updating HMS SW

On this exercise, we are going to use the spare ICSU to be updated.

Complete instruction on updating HMS SW is described on "HMSSoftware Update Procedure" document.

1. Start service terminal session on active OMU.

2. Install RCJ (Recovery Userpart) extension.

Command: ________________________________________

3. Change spare OMU state to SE-NH.

Command: ________________________________________

4. Change spare RSMU state to SE-NH.

Command: ________________________________________

5. Set FBAN flags on all units.

Command: ________________________________________

6. Interrogate the physical address of spare ICSU.

Command: ________________________________________

7. Use HME extension to lookup HMS address of spare ICSU from itsphysical address.

Command: ________________________________________

8. Get the current status of spare ICSU HMS node.

Command: ________________________________________

9. Get the current active line.

Command: ________________________________________

10. Prevent independent switchover of HMS.

Wait until the following text is displayed

HMS INDEPENDENT SWITCHOVER DISABLED SUCCESSFULLY.

Command: ________________________________________

11. Update the spare ICSU HMS node.

Note: Use the suitable file according to node version. 1st versionnode uses HMX1SNGX.IMG while A-version node usesHMXASNGX.IMG

Command: ________________________________________

12. Get the status of spare ICSU now, verify that the HMS SW versionhas been updated.

Command: ________________________________________





13. Enable independent switchover of HMS

Wait until the following text is displayed

HMS INDEPENDENT SWITCHOVER ENABLED SUCCESSFULLY.

Command: ________________________________________

14. Clear FBAN flags on all units.

Command: ________________________________________

15. Change spare RSMU state back to SP-EX.

Command: ________________________________________

16. Change spare OMU state back to SP-EX.

Command: ________________________________________





6. RNC Problem Reporting

During field operation, there may be unsolved problems that must beescalated to RNC technical support or Production line. To makeinvestigation process easier, maintenance engineer needs to provide aset of log or configuration files. The complete instruction to create aproblem reporting is described on "TS-RNC-SW-038 RNC ProblemReport Instructions" document

6.1 Displaying Computer and System Log

1. Start service terminal session on a chorus computer unit. Use"clog" to show details of computer log

Command: ________________________________________

2. Use "olog" to show operating system log

Command: ________________________________________

3. Start service terminal session on a DMX computer unit. Usecomputer log handler to show computer log in long format

Command: ________________________________________

4. Display operating system log

Command: ________________________________________

6.2 Displaying Unit Blackbox

1. Start service terminal session on a chorus computer unit. LoadChorusOS system dump tool extension.

Command: ________________________________________

2. Prints all system dump information from all available resets.

Command: ________________________________________

3. Load Chorus blackbox log extension.Command: ________________________________________

4. Shows details of computer log.

Command: ________________________________________

5. Start service terminal session on DMX computer unit. Load BOX(Blackbox analyser) extension.

Command: ________________________________________





6. Display the whole blackbox contents.

Command: ________________________________________

6.3 Unit Start-up Log

1. Start a service terminal session on a DMX computer unit. LoadSQQ (starter extension)

Command: ________________________________________

2. Output the unit start-up log

Command: ________________________________________

3. Start a service terminal session on a Chorus computer unit.Command: ________________________________________

4. Use system tool dump to display console printout.

Command: ________________________________________

03 02 rn33153en10gla0 rncoam service terminal excercise

Documents