05_01_RN33155EN10GLA0_RNC and Unit Startup Supervision

8/18/2019 05_01_RN33155EN10GLA0_RNC and Unit Startup Supervision

http://slidepdf.com/reader/full/0501rn33155en10gla0rnc-and-unit-startup-supervision 1/18

1 © Nokia S iemens Networks RN33154EN10GLA0

For public use –IPR applies

RNC and Unit Startup Supervision



2 © Nokia Siemens Networks RN33154EN10GLA0


Nokia Siemens Networks Academy

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Siemens Networks training documentation,product documentation and slide presentation material, all of which are forthwith known as NokiaSiemens Networks training material, are the exclusive property of Nokia Siemens Networks. NokiaSiemens Networks owns the rights to copying, modification, translation, adaptation or derivativesincluding any improvements or developments. Nokia Siemens Networks has the sole right to copy,distribute, amend, modify, develop, license, sublicense, sell, transfer and assign the Nokia SiemensNetworks training material. Individuals can use the Nokia Siemens Networks training material for theirown personal self-development only, those same individuals cannot subsequently pass on that sameIntellectual Property to others without the prior written agreement of Nokia Siemens Networks. TheNokia Siemens Networks training material cannot be used outside of an agreed Nokia SiemensNetworks training session for development of groups without the prior written agreement of NokiaSiemens Networks.





Content

• System start-up

• Monitoring system start-up

• DMX unit start-up phases

• Chorus unit start-up phases

• Collecting log for system start-up

• Collecting log for DMX unit start-up

• Collecting log for Chorus unit start-up





System Start-up Overview

DMX M essagingHMS M essaging

Initialize HW port

for FU

Initialize ATM

Interface for FU

Create ATM virtual

connections

Load code Restart any FU

RESTART





System Start-up Order

CACU /RSMU

SFU

MX U

MX U

CM

OM U

PSTN / A / IWU

MX U

SPMU

NIP1

A2 SU

ICSU /ISU

NIWU

Iu

VANU

IP Core IP NIU

Iu / ATM Core NISx

Ethernet

disks

3. Start the rest of theactive MXUs, and SYM-MXU’stributary units2. Start active SYM-MXU and SFU.

•To al low ATM connection setup for OMUand other SYM -MXU tr ibutary units•SFU is started only at flash boot level(Note: includes only switch portinitialization, but not message connectivityto the SFU unit compu ter)

5. Start the interface units.

• Starting in the last phaseensures that the networkelement is ready to

respond immediately whennetwork interfaces areopened.

1. Start the active SYM-unit (OMU).

•To start the System M aintenance•Only OMU has a direct connectionto disks.

DM CU/ TCU

4. Start the tributary unitsof the other MX Us

CACU /RSMU

SFU

MX U

MX U

CM

OM U

PSTN / A / IWU

MX U

SPMU

NIP1

A2 SU

ICSU /ISU

NIWU

Iu

VANU

IP Core IP NIU

Iu / ATM Core NISx

Ethernet

disks

3. Start the rest of theactive MXUs, and SYM-MXU’stributary units2. Start active SYM-MXU and SFU.

•To al low ATM connection setup for OMUand other SYM -MXU tr ibutary units•SFU is started only at flash boot level(Note: includes only switch portinitialization, but not message connectivityto the SFU unit compu ter)

5. Start the interface units.

• Starting in the last phaseensures that the networkelement is ready to

respond immediately whennetwork interfaces areopened.

1. Start the active SYM-unit (OMU).

•To start the System M aintenance•Only OMU has a direct connectionto disks.

DM CU/ TCU

4. Start the tributary unitsof the other MX Us





System Start-up Principles

The starting order at high level is:

1. active units up and running first (for user traffic)2. redundant units next

3. rest of the units.

The IPA2800 is a multiprocessor and multi-unit platform, which starts in a paralleland concurrent way:

• Parallel - units genuinely execute independently; high level control from centralizedunits

• Concurrent - units perform internally concurrent operations during unit start-up

For units with multiple processors (A2SU, DMCU, TCU, NIWU, IW1S1)

• the master processor will be started first,

• and then the rest of the processors will be started independently, and in parallel.

For those units with DSP resources (DMCU, TCU),• DSP-0 in each DMPG/TPG will be started first,

• and then the rest of the DSPs under DMPG/TPG will be started in parallel





Parallel Start-up

• When the active OMU is started, ATM connections are not requiredsince the programs are loaded directly from the disk.

• After reaching restart phase 3, the active OMU (SYM unit) can startacting as a central controller for the start-up of the other functionalunits.

Color codes: = RP 0 (Flash boot)= RP1

= RP2

= RP3

= Normal working s ta te (WO/SP-EX)

Act ive SYM

Act ive MXUs

2N, N+1, SN+1 units

Interface units

Color codes: = RP 0 (Flash boot)= RP1

= RP2

= RP3

= Normal working s ta te (WO/SP-EX)

Act ive SYM

Act ive MXUs

2N, N+1, SN+1 units

Interface units





Monitoring System Start-up

1. Open local service terminal connection to working OMU computerunit, make sure the connection is made to SER1 port.

2. Load RCJUUS extension

ZLP: J , RCJ ;

3. Use the following command to interrogate the system start-upprocess

ZJ I : ALL; or you may use ZJ I : ALL, FULL;





DMX Unit Start-up Phases

Phases on DMX unit start-up

• Boot• Initial loading

• Starting phase 1



• Warming (for SP units)

Boot

• BOLERO perform HW tests.

• BOLERO initialises main memory andperipheral buses, includes forming blackbox if needed.

• BOLERO loads modules in non-volatilememory (FLASH)

• DMXRTE and STQPRO are started

• Initial loading can be started





DMX Unit Start-up Phases (cont’)

Initial loading

• EPISOD is started.• EPISOD contacts load manager.

• EPISOD loads BOOLIS (load list) and loadthe rest modules accordingly.

• DMXRTE and STQPRO are started again

• STQPRO starts some special processfamilies

Starting phase 1

• Initialisation of work files

• File loading is started

– Loading group loadings

– Loading performed by applicationprograms (mainly database managers)

Starting phase 2

• Unit can function as a file loading sourcefor other units.

• Databases and other files started andloaded

• Process families started (mainly databasemanagers)

Starting phase 3

• Starting the rest process families

• No more file loading

• Unit expected to be WO-EX

Warming• No new process families, only essential data of

processes with corresponding processes inactive unit





Chorus Unit Start-up Phases

Phases on Chorus unit start-up

• Boot• Loading boot archives and microcode

image

• Starting of boot archives

• File loading

• Starting of actors

Boot

• Processor and memory banks areinitialised

• Second phase boot loader is started• Second phase boot loader located innon-volatile memory (FLASH)

Boot

Loading boot archives andmicrocode images

Starting of boot archives

File loading

Starting of actors





Chorus Unit Start-up Phases (cont’)

Loading boot archives and microcode

image• Second phase boot actor LEADER is

started

• LEADER loads actual boot archivefrom memory of active SYM unit orfrom system disk

Starting of boot archives

• After boot archive is loaded, LEADERexecute warm reset so boot phasestart again.

• Boot archives is started on secondphase boot

• Chorus OS and some special actorsstarted

File loading

• The rest actors is loaded• As well as service terminal programs

and parameters

Starting of actors

• All loaded actors are started

• Actor starting can is further dividedinto:

– System starting phase

– Application starting phase





Collecting Log for System Start-up

• These instruction are applied to RSMU and OMU units

1. Open service terminal connection

ZDDS: <uni t t ype>, <uni t i ndex>;

2. Load the Blackbox Analyser extension

ZLP: 1, BOX;

3. Display the blackbox log

Z1U;

4. Save the blackbox log.

Include the name and index of the unit in the file name

• In the event of multiple restart, use FTP to collect the blackbox files of the unitsfrom / var / crash/ folder.

• Blackbox files are saved with the following format

00xx_00.bbox – 00xx_11.bbox (12 files)

xx indicates physical address of corresponding computer units; i.e. 00 for OMU-0, 0F for RSMU-0.





Collecting Log for System Start-up (cont’)

Blackbox files for 00 unit (OMU-0), 12 files

Full path on ftp browser ftp://<OMU IP address>/shadows/var/crash





Collecting Log for DMX Unit Restart

• These instruction are applied to RSMU, OMU, ICSU and GTPUunits

1.Open service terminal connection


2.Load the Blackbox Analyser extension

ZLP: 1, BOX;

3.Display the blackbox log

Z1U;

4.Save the blackbox log.

Include the name and index of the unit in the file name

5.Print out the log data stored on disk

ZDVL: : CONT: : : : : <uni t t ype>, <uni t i ndex>;





Disk Log Information

Family process name, id and hand’s life

focus that wrote the log

Address of process’s storage where the log

was written

Time stamp

Compt address

Sequence number

CRI = critical error logERR = error logINF = info logTES = test log

APP = application layer CPL = computing platform layer KER = operating system kernelREC = recovery software layer SPL = switching platform software layer UND = undefined

Writing class of the log





Collecting Log for Chorus Unit Restart

• These instruction are applied to MXU, A2SU, NIP1, NIS1, DMCUand SFU units

1.Open service terminal connection


2.Load “sysdump” extension

l oadext sysdump

3.Printout the start-up log

sysdump - p - r 2

4.Printout the actors

sysdump - a - r 2

5.Printout the threads

sysdump - t - r2

6.Printout the log entries

sysdump - l - r2





Collecting Log for Chorus Unit Restart (cont’)

7. Printout the failed system calls information

sysdump - s - n 300 - r 2

8. Printout the context switching information

sysdump - c -r 2

9. Printout the log data stored on disk

ZDVL: : CONT: : : : : <uni t t ype>, <uni t i ndex>;

05_01_RN33155EN10GLA0_RNC and Unit Startup Supervision

Documents

Transcript of 05_01_RN33155EN10GLA0_RNC and Unit Startup Supervision