Base Processor Terminal Commands

C-DOT DSS MAX

APPLICATION NOTE ON BASE PROCESSOR

TERMINAL COMMANDS

System Practices

Section No. 400-658-0920

Draft 03, June 2005

C-DOT DSS MAX

APPLICATION NOTE ON BASE PROCESSOR

TERMINAL COMMANDS

© 2005, C-DOT Printed in India

C-DOT DSS MAX

APPLICATION NOTE ON BASE PROCESSOR TERMINAL COMMANDS

DRAFT 03

JUNE 2005

ASADHA 2062

SERIES 600 : SOFTWARE

CSP SECTION NO. 400-658-0920

THIS C–DOT SYSTEM PRACTICE REFERS TO THE C–DOT DIGITAL SWITCHING SYSTEM

MAIN AUTOMATIC EXCHANGE (ABBREVIATED AS C–DOT DSS MAX IN THE REST OF THIS

PUBLICATION).

THE INFORMATION IN THIS SYSTEM PRACTICE IS FOR INFORMATION PURPOSES AND IS

SUBJECT TO CHANGE WITHOUT NOTICE.

A COMMENT FORM HAS BEEN INCLUDED AT THE END OF THIS PUBLICATION FOR

READER'S COMMENTS. IF THE FORM HAS BEEN USED, COMMENTS MAY BE

ADDRESSED TO THE DIRECTOR (C&S), CENTRE FOR DEVELOPMENT OF TELEMATICS,

C-DOT CAMPUS, MEHRAULI, NEW DELHI - 110 030

© 2005 BY C–DOT, NEW DELHI.

Table of Contents

Chapter 1. Introduction ..............................................................................................................................5 Chapter 2. BP Cable Details.......................................................................................................................9 Chapter 3. Base Module............................................................................................................................14 Chapter 4. Remote Base Module Monitoring Through BP Terminal ....................................................29 Chapter 5. Central Module & Administrative Module ...........................................................................34 Chapter 6. Signaling Unit Module (CCS7 Module).................................................................................45 Chapter 7. V5.X Unit.................................................................................................................................51 Chapter 8. Input Output Module (IOP) ...................................................................................................56 Chapter 9. Health Log & Field Debugging Tool......................................................................................60 Annexure I Symbols and Addresses for Various Function ......................................................................66

H:\HOME\MAX\WORD\MXAPBPTCM.DOC June 21, 2005

APPLICATION NOTE ON BASE PROCESSOR TERMINAL COMMANDS 5

Chapter 1.

Introduction

1.1. GENERAL

During Installation and maintenance of C-DOT SBM/MAX-L/MAX-XL, some times, it is necessary to use a VT100 terminal connected directly to the processor in the module to give commands directly to processor in the module. Terminal can be connected to processor in BM/RBM/SUM/CM/AM using a RS232 cable. From this terminal, commands can be issued to perform following tasks. • To view the switch unit status in the module • To modify the switch unit status in the module • To initialize the module, when module does not respond to commands from

crp terminal connected to IOP. • To increase SRF counter value.

1.2. SRF COUNTER OVERFLOW PROBLEM

Due to problem in Hardware, data inconsistency, call failures in trunk groups etc., system generates recoveries and this can be seen on BP terminal connected to the respective module. Whenever recoveries exceed default value of 0064 (Hex), system initializes on its own, going for stable clear. Before problem is identified and recoveries are stopped, counter value can be increased to FFFF (Hex) to avoid frequent initialisation of system to stable clear level.

1.3. For Accessing Processor in any module the following things have to be done.

• RS232 cable should be prepared as given in the Chapter 2 of this document for BM-L/BM-XL/SUM.

• RS232 cable meant for BM-L (with CPUS04/S05 processor card can be used in BM-L, CM-L, AM in MAX-L.

• RS232 cable meant for BM-XL (with BPC processor card) can be used in BM-XL, CM-XL & AM in MAX-XL.

• Connect the VT100 terminal (VDU) to required module (BM/RBM/SUM/CM/AM) using RS232 cable. Details of connectors used for

Chapter 1.

6 C-DOT DSS MAX

terminating RS232 cable in each module is given in respective chapters of this document.

• Set the baud rate of terminal to 4800/9600 bps depending on processor in the module as given below :

CPU S04 - 4800 bps

CPU S05 - 4800 bps

BPC/HPC - 9600 bps • Switch unit identity in HEX for all units is given in Table 1.1 • Follow the commands and examples as given for each module in different

chapters.

INTRODUCTION


1.4. SWITCH UNIT ID’S 0 1 2 3 4 5 6 7 8 9 A B C D E F

0 BP1-0 BP1-1 BP2-0 BP2-1 BP3-0 BP3-1 BP4-0 BP4-1 BP5-0 BP5-1 BP6-0 BP6-1 BP7-0 BP7-1 BP8-0 BP8-1 1 BP9-0 BP9-1 BP10-0 BP10-1 BP11-0 BP11-1 BP12-0 BP12-1 BP13-0 BP13-1 BP14-0 BP14-1 BP15-0 BP15-1 BP16-0 BP16-1 2 BP17-0 BP17-1 BP18-0 BP18-1 BP19-0 BP19-1 BP20-0 BP20-1 BP21-0 BP21-1 BP22-0 BP22-1 BP23-0 BP23-1 BP24-0 BP24-1 3 BP25-0 BP25-1 BP26-0 BP26-1 BP27-0 BP27-1 BP28-0 BP28-1 BP29-0 BP29-1 BP30-0 BP30-1 BP31-0 BP31-1 BP32-0 BP32-1 4 SWC1-0 SWC1-1 SWC2-0 SWC2-1 SWC3-0 SWC3-1 SWC4-0 SWC4-1 SWC5-0 SWC5-1 SWC6-0 SWC6-1 SWC7-0 SWC7-1 SWC8-0 SWC8-1 5 AP-0 AP-1 ADC IOP-0 IOP-1 SU7-0 SU7-1 6 SS-0 SS-1 SSC-0 SSC-1 CMS1 CMS2 CMS3 CMS4 IFC1 IFC2 IFC3 IFC4 IFC5 IFC6 7 IFC7 IFC8 IFC9 IFC10 IFC11 IFC12 IFC13 IFC14 IFC15 IFC16 IFC17 IFC18 IFC19 IFC20 IFC21 IFC22 8 IFC23 IFC24 IFC25 IFC26 IFC27 IFC28 IFC29 IFC30 IFC31 IFC32 CLK-0 CLK-1 SSBID-0 SSBID-I 9 MU-0 MU-1 BMS-0 BMS-1 SCIC-0 SCIC-1 TSC-0 TSC-1 A T101-0 T101-1 T102-0 T102-1 T103-0 T103-1 T104-0 T104-1 T105-0 T105-1 T106-0 T106-1 T107-0 T107-1 T108-0 T108-1 B T109-0 T109-1 T110-0 T110-1 T111-0 T111-1 T112-0 T112-1 T113-0 T113-1 T114-0 T114-1 T115-0 T115-1 T116-0 T116-1 C ICCI-0 ICC1-1 ICC2-0 ICC2-1 ICC3-0 ICC3-1 ICC4-0 ICC4-1 VP-0 VP-1 VMU-0 VMU-1 D TTC ANNC E SWC9-0 SWC9-1 SWC10-

0 SWC10-1

SWC11-0

SWC11-1

SWC12-0

SWC12-1

SWC13-0

SWC13-1

SWC14-0

SWC14-1

SWC15-0

SWC15-1

SWC16-0

SWC16-1

F MFC1 MFC2 MFC3 MFC4 TOGC-0 TOGC-1

Table 1.1 Note: 1. All CRP Ids used 2. Usage unit id (UID) = Row No. followed by Column No. 3. Example: Say for IFC17 Row No = 7, Column ‘A’ Hence UID for IFC17 is 7A. 4. BP1-0, BP1-1 represent BP-0, BP-1 for BM1, BP2-0, BP2-1 represent BP-0,BP1 for BM-2.. So on. Ex : Unit ids for BP_0 & BP_1 of BM 32 are 3E, 3F respectively. Unit ids for BP_0 & BP1 of BM 10 are 12,13

Chapter 1.

8 C-DOT DSS MAX

STATUS OF UNITS

Numbers in HEX representing the status of switch units are given below with status of switch units.

HEX ID

STATUS HEX ID

STATUS

02 INS-ACT (Inservice Active) 04 INS-SBY (Inservice Standby) 08 INS-FRC (Inservice forced) 90 OOS-INI (Out of service

Initialization) 91 OOS-EXT (Out of service

external) 93 OOS-EXT (Out of service

external) 94 OOS-TST (Out of service test) 96 OOS-SUS (Out of service

suspect) 98 OOS-SYS (Out of service

system) 9A OOS-OPR (Out of service

operator)

! CAUTION Working on 'BP' Terminal should be done very carefully particularly in a working exchange. A careless handling may cause the module to go for initialization. Some times corruption of data may also occur. While handling BP terminal one should be utmost sure about the commands to be given.


Chapter 2.

BP Cable Details

This chapter gives the details of a pictorial view of various BP cables and its drawing reference ie., C-DOT Assy. No. with the help of which all these cable can be prepared easily at the site.

These cables are generally supplied with the equipments with the following description.

Part Code

For MAX-XL

AP/BP Terminal Cable Assy. (8 pair telephone cable 0.4 mm, 25 Mtrs length)

ACB-MAXXBPTX-000

For SUM

BP Terminal Cable Assy. for SUM (8 pair telephone cable 0.4 mm, 25 Mtrs length)

ACB-MAXXSUTX-000

For MAX-L

AP/BP Terminal Cable Assy. for (8 pair telephone cable 0.4 mm, 25 Mtrs length)

ACB-RSUVTEZX-00

Chapter 2.

10 C-DOT DSS MAX

25 P

IN D

-TYP

E

WIR

EWR

AP

(FEM

ALE)

25 M

Ts (M

AX)

8 P

AIR

TEL

EPH

ON

E

CA

BLE

(0.4

mm

)

DES

TIN

ATI

ON

BPØ

/BP1

SO

UR

CE

VDU

MC

C-B

PC

SZ0

12-4

01

MC

C-B

PC

SZ0

11-4

01

MC

C-B

PC

SZ0

22-4

01

MC

C-D

CFM

Z002

-301

TE

Z1

XZ

ET

BP T

ERM

INAL

CAB

LE F

OR

BM

-L/C

M-L

FIG

. 2.1

2Z

ET

CO

NN

EC

TOR

B

CO

NN

EC

TOR

A

(((

(C)

SIN

GLE

MO

DU

LE C

OVE

R

(b)

CO

NTA

CT

BLO

CK

7x2

PIER

CIN

G B

LOC

K(a

)

7x2

IDC

CR

IMP

CO

NN

EC

TOR

CO

NSI

STI

NG

OF

1M

L1

L21M

S. N

o.C

DO

T AS

SY N

o.FR

OM

TOC

ABLE

MAR

KER

1A

CB

-RSU

VTEZ

X-00

VT-

220

TER

MIN

ALBP

TEZ1

VT-

220

TER

MIN

ALBP

TEZ2

ASS

EM

BLY

INST

RU

CTI

ON

S

25 P

IN D

TY

PEC

ON

NE

CTO

R

A B

PIN

S

IGN

ALC

ABLE

PAI

R7x

2C

ON

NE

CTO

R P

AIR

2Tx

(VD

U)

WH

OF

BL-

WH

1c 1aB

L O

F BL

-WH

Rx

(VD

U)

3 7G

ND

(VD

U)

OR

, WH

OF

OR

-WH

2a, 2

c

6a, 6

cB

N, W

H O

F BN

-WH

GN

OF

GN

-WH

5a5cW

H O

F G

N-W

H

CO

NN

EC

TOR

72 3G

ND

(VD

U)

Rx

(VD

U)

Tx (V

DU

)

NO

TE: U

SE S

ILIC

ON

RU

BBE

R S

LEE

V O

NLE

NG

THS

L1,

L2

\DE

SIG

N\D

SS

MA

X\M

AX-X

L\B

PTR

MN

L\BP

-BTC

BP CABLE DETAILS


\DE

SIG

N\D

SS

MA

X\M

AX-X

L\B

PTR

MN

L\R

SXLI

MAS

OV

ER

LEN

GTH

L1,

L2

AN

DP

UT

6.0m

m B

LAC

K S

ILIC

ON

RU

BBER

SLE

EVE

(A)

ASS

EM

BLY

INST

RU

CTI

ON

MC

C-D

CFM

Z002

-301

WIR

EWR

AP

(FEM

ALE)

25 P

IN D

-TYP

E

CO

NN

EC

TOR

CO

NN

EC

TOR

SO

UR

CE A

VDU

B

25M

(MAX

)

PB

1T

1M

BP

T2

CAB

LE (0

.4m

m)

8 P

AIR

TE

LEPH

ON

E

VT-

220

TER

MIN

AL

VT-

220

TER

MIN

ALA

CB-

MAX

XBP

TX-0

00

CD

OT

ASSY

No.

S. N

o.

1

FRO

MTO B

PØ

BP1

CAB

LEM

ARKE

R

BPT

1

BPT

2

CO

NN

EC

TOR

D T

YPE

(B)

A

PIN

No.

3 2

B

7 3 72

(C)

BPØ

DES

TIN

ATI

ON

1P

BT

2P

BT

0.25

M

3

CO

NN

EC

TOR

1 2 4

A

31 2

CO

NN

EC

TOR

4

B

PIN

20

TO P

IN 6

AN

D P

IN 8

PIN

4 T

O P

IN 5

ON

EA

CH

D T

YPE

CO

NN

EC

TOR

SH

OR

T AS

FO

LLO

WS.

CO

NSI

STI

NG

OF

7x2

IDC

CR

IMP

CO

NN

EC

TOR

SIN

GLE

MO

DU

LE C

OVE

R

7x2

PIER

CIN

G B

LOC

K

CO

NTA

CT

BLO

CK

(a)

(C)

(b)

DES

TIN

ATI

ON

BP1

DTR

TO

DR

S D

CD

RTS

TO

CTS

(1)

(2) R X

D (V

DU

)T

X D

(VD

U)

SIG

NAL

SO

UR

CE

BL

WH

PAI

R

BL-

WH

BL-

WH

MC

C-B

PC

SZ0

22-4

01)

MC

C-B

PC

SZ0

11-4

01)

MC

C-B

PC

SZ0

12-4

01)

( ((

PIN

No.

(7x2

MO

DU

LE)

DES

TIN

ATI

ON

A4c 5a

T X

D (V

DU

)R

X D

(VD

U)

DIG

ITA

L G

ND

DIG

ITA

L G

ND

WH

OR

,WH

GR

BL-

RD

GR

-WH

OR

-WH

GR

-WH

BL-

RD

TIE

WIT

H C

ABLE

B

5c 4c 5c5aFI

G. 2

.2BP

TER

MIN

AL C

ABLE

FO

R B

M-X

L/C

M-X

L

Chapter 2.

12 C-DOT DSS MAX

25 P

IN D

-TYP

E

WIR

EWR

AP

(FEM

ALE)

25 M

Ts (M

AX)

8 P

AIR

TEL

EPH

ON

E

CA

BLE

(0.4

mm

)

SO

UR

CE

SU

7-0/

SU7-

1

DE

STIN

ATIIO

NVD

U

MC

C-B

PC

SZ0

12-4

01

MC

C-B

PC

SZ0

11-4

01

MC

C-B

PC

SZ0

22-4

01

MC

C-D

HX

XXT2

5-10

0

SU

M1

XT

US

BP T

ERM

INAL

CAB

LE F

OR

SU

MFI

G. 2

.3

2M

US

CO

NN

EC

TOR

B

CO

NN

EC

TOR

A

(((

(C)

SIN

GLE

MO

DU

LE C

OVE

R

(b)

CO

NTA

CT

BLO

CK

7x2

PIER

CIN

G B

LOC

K(a

)

7x2

IDC

CR

IMP

CO

NN

EC

TOR

CO

NSI

STI

NG

OF

1M

L1

L21M

S. N

o.C

DO

T AS

SY N

o.FR

OM

TOC

ABLE

MAR

KER

1A

CB

-MAX

XSU

TX-0

00V

T-22

0 TE

RM

INAL

SU

7-0

SU

M1

VT-

220

TER

MIN

ALS

U7-

1S

UM

2

ASS

EM

BLY

INST

RU

CTI

ON

(A)

ON

EA

CH

D T

YPE

CO

NN

EC

TOR

SH

OR

T AS

FO

LLO

WS.

(1)

RTS

TO

CTS

PIN

4 T

O P

IN 5

(2)

DTR

TO

DR

S D

CD

PIN

20

TO P

IN 6

AN

D P

IN 8

D T

YPE

CO

NN

E-

A B

PIN

No.

SIG

NAL

DES

TIN

ATI

ON

PAI

RS

OU

RC

E(7

x2 M

OD

ULE

)

3T

X D

(VD

U)

WH

BL-

WH

1a

(B)

1CB

L-W

HB

LR

X D

(VD

U)

2 7D

IGIT

AL

GN

DO

R,W

HO

R-W

H2a

, 2c

4a, 4

cB

L-R

DB

L-R

DD

IGIT

AL

GN

D72

R X

D (V

DU

)G

RG

R-W

H3c3a

GR

-WH

WH

T X

D (V

DU

)3

(C)

PU

T 6.

0mm

BLA

CK

SIL

ICO

N R

UBB

ER S

LEE

VEO

VE

R L

ENG

TH L

1, L

2 A

ND

TIE

WIT

H C

ABLE

MC

C-D

CFM

Z002

-301

CTO

R

\DE

SIG

N\D

SS

MA

X\M

AX-X

L\BP

TRM

NL\

MXI

-AS

BP CABLE DETAILS


In all the configurations the source is the Base Processor frame with different connector location. Following table gives details of the exact points of connection.

For BM-L/CM-L/AM-L Rack BM (BP) CM (SSC) CM (AP)

Frame 5 3 4

Slot 2 2 2

Connector B A A

Tab No. 1 1 1

For BM-XL/CM-XL/AM-XL Rack BM (BP) CM (SSC) CM (AP)

Copy 0 Copy 1 Copy 0 Copy 1 Copy 0 Copy 1

Frame 5 5 5 5 6 6

Connector J7 J24 J25 J52 J20 J36

Tab No. 4 4 1 1 1 1

For SUM/VU

Connection Position : Slot 5 / connector A / Tab 2

14 C-DOT DSS MAX

Chapter 3.

Base Module

3.1. BASE MODULE

3.1.1. Accessing BP in Base Module

BP of BM can be accessed to view/modify switch unit status, modifying SRF counter values whenever BM generates recovery messages due to fault in hardware/software/data problems. BP of BM can be accessed by directly connected terminal to BPU. However, it is also possible to access BP of BM from CRP terminal connected to IOP provided module is active and this procedure also has been described. Connect the BP cable form terminal to BPU frame as given below to access BP of Base Module.

For BM-L (CPUS04/S05)

Source : RS232 port of VDU

Destination : Frame 5 / slot 1 / B connector / Tab 1

Note : Set baud rate of terminal to 4800 bps for CPU S04 and CPU S05

For BM-XL (BPC)

Source : RS232 port of VDU

Destination : Frame 5 / Slot 11 / B connector / Tab 4 ➜ for Copy 0

Frame 5 / Slot 20 / B connector / Tab 4 ➜ for Copy 1

Note : Set baud rate of terminal to 9600 bps for BPC/HPC cards in BPU.

3.1.2. Procedure to View Switch Status on BP Terminal

Switch unit status in BM can be seen from BP terminal, connected directly to BPU respective of BM or from any IOP terminal.

In the procedure given below, we have used symbol mbc_bm_unit to view switch unit status map. Alternatively, we can use address also to define and view the unit status map. Address for required symbol can be derived from

BASE MODULE


BP terminal or IOP terminal. However, note that symbols remain same across different software releases, whereas addresses may be different in different software releases. While using address, derive address from BP or IOP terminal as described below.

Deriving address for required symbol from BP terminal (BM/RBM/AM/CM/SUM/VU)

MDEBXX> sy mbc_bm_unit ↵ (XX is bp id of copy 0 processor of that module) mbc_bm_unit : 0 x cc3202 (Address for symbol mbc_bm_unit is cc3202) mdebxx> ex ↵ cdos> ex ↵

Note : Procedure to derive address for symbol from IOP terminal is described in chapter 8 (Input Output module).

For eg: For symbol mbc_bm_unit address is cc3202 in S/W release 2_2_1_6 for MBM.

PROCEDURE TO VIEW UNIT STATUS Define the address of unit status map (mbc_bm_unit as us) as follows : Press ctrl-D, you should get CDOS prompt. If terminal continuously prints 62, then change 25 pin connector in terminal end of BP cable for other copy of CPU. After changing connector, press control D again to get CDOS prompt. CDOS XX>m ↵ Note : Here XX indicates BP id in Hex corresponding to that BM. BP ids are given in Table 1.1. ### WELCOME TO DD, MBEBUG & RETEST ### Type HE for MDEB & HELP for DD help MDEBXX> def us md @mbc_bm_unit l+100 ↵ Logical symbol US defined

Alternatively use address to view unit status as given below : MDEBXX> def us md cc3202 l + 100 ↵ Logical symbol US defined.

MDEBXX>prn e ↵

Chapter 3.

16 C-DOT DSS MAX

Note :

Now type US ↵ on MDEB prompt to see unit status and type def ↵ on MDEB prompt to see the defined symbols. XX is BP identity in BM in Hexadecimal. In this example unit status map is shown for BM-10.

TO SEE THE DEFINED SYMBOLS GIVE THE FOLLOWING COMMAND : MDEB12 > def ↵

To view the unit status map in that BM.

MDEB12> us ↵

00CC3202 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@

00CC3212 C0 C0 04 02 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@..@@@@@@

00CC3222 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@@@

00CC3232 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@@

00CC3242 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@

00CC3252 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@@

00CC3262 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@.@@@

00CC3272 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@

00CC3282 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@

00CC3292 C0 C0 C0 C0 C0 C0 02 02 04 02 C0 C0 02 04 02 98 @@@@@@…

00CC32A2 02 91 02 91 02 91 02 91 02 91 02 91 02 91 02 91 ………

00CC32B2 02 91 02 91 02 91 02 91 02 91 02 91 02 91 02 91 ………

00CC32C2 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@

00CC32D2 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 02 02 C0 @@@@@@@@

00CC32E2 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@

00CC32F2 02 02 02 02 C0 C0 C0 C0 02 04 C0 C0 C0 C0 C0 C0 ….@@@@.

Table 3.1

MDEB12>ex ↵

CDOS12>ex ↵

Note :

Unit-id can be derived from table 1.1 and status of units as displayed in unit status map shown in table 3.1 are given in Table 3.2.

BASE MODULE


Unit_id Unit Status Unit_id Unit Status 12 BP-0 (BM-10) Ins-sby 13 BP-1 (BM-10) Ins-act

A0,A2,A4,A6 TI01-0 to TI04-0 Ins-act

96 MU-0 Ins-act 97 MU-1 Ins-act

A1,A3,A5,A7 TI01-1 to TI04-1 Oos-ext

98 BMS-0 Ins-sby 99 BMS-1 Ins-act

A8,AA,AC,AE TI05-0 to TI08-0 Ins_act

9c SCIC-0 Ins-act 9d SCIC-1 Ins-sby

A9,AB,AD,AF TI05-1 to TI08-1 Ins-act

9e TSC-0 Ins-act 9f TSC-1 Oos-sys

B0,B2,B4,B6 TI09-0 to TI12-0 Ins-act

dd TTC Ins-act de ANNC Ins-act

B1,B3,B5,B7 TI09-1 to TI12-1 Oos-ext

fo MFC1 Ins-act f1 MFC2 Ins-act

B8,BA,BC,BE TI13-0 to TI16-0 Ins-act

f2 MFC3 Ins-act f3 MFC4 Ins-act

B9,BB,BD,BF TI13-1 to TI16-1 OoS-ext

f8 TOGC-0 Ins-act f9 TOGC-1 Ins-sby

Table 3.2 Here we have used symbol US (any other characters can also be used) see the unit status map stored in memory. On typing us and then return, unit status map is displayed as given above. First column of the unit status map contains the address of the locations. The remaining columns contains the unit status. This map contains status of unit represented by numbers (i.e. 02 ➜ Ins-act, 04 ➜ Ins-sby etc.) and numbers representing status units is given in Table 1.1. We can see from the table that, in 2nd row after address, 04, 02 exists in 3rd, 4th locations. This is status of unit ids BP10-0, BP10-1 and thus this US map indicates status of units of BM10.

Example : a) To check the status of both copies of BP in unit status map shown in

Table 3.1 In table 3.1, the first column is address and other columns contain status of switch units. In US map in Table 2.1 we can see that 04,02 exist in 2nd row in locations i.e. unit id row x column works out to 12,

Chapter 3.

18 C-DOT DSS MAX

13 for BP-0 & BP-1 respectively. Thus we can see that BP-0 is in ins-standby status and BP-1 is in ins-act status. Note : To calculate BP id use the procedure given below or refer table 1.1 BP-0 UID = [(BM-NO * 2) – 2] } Result of the expression in decimal may be converted to BP-1 UID = [(BM-NO * 2) – 1] } hexadecimal to get Bp id. Ex : BP-0 ID of BM-6 is 6*2-2=10 =0A (in HEX)

b) To check the status of TSC-1 in unit status map shown in table 2.1 From Table 1.1, we can derive switch unit identity in the Hex for TSC-1 and it is 9f. From Table 3.1 we can see that location 9f (start counting rows from 0 and go to 9th row, start counting columns from 0 and go to 15th column. (i.e. first column is address and should not be included while counting row/column). We can see that location 9f has value 98, which indicates that TSC-1 is in oos-sys status. Thus TSC-1 is in oos-sys status. Similarly, other unit status also can be checked. Note that both memories (unit identifies 96,97) are active as it should be.

The table below shows the UNIT and its UID in HEX SWITCH UNIT UID in HEX BP-0 (BM-NO * 2) – 2 (in HEX) BP-1 (BM-NO * 2) – 1 (in HEX) MU-0 96 MU-1 97 BMS-0 98 BMS-1 99 SCIC-0 9C SCIC-1 9D TSC-0 9E TSC-1 9F TIC1-0 to TIC8-1 A0 to AF TIC9-0 to TIC16-1 B0 to BF MFC1 to MFC4 F0 to F3 TTC DD ANNC DE TOGC-0 F8 TOGC-1 F9

Table 3.2

Note : Except BP-0 and BP-1 all other Unit ID’s are common for all BM’s

BASE MODULE


Status of Units :

02 ➙ INS-ACT

04 ➙ INS-SBY

9A ➙ 00S-OPR

91 ➙ 00S-EXT

98 ➙ 00S-SYS

96 ➙ 00S-SUS

C0 ➙ UNEQUIPPED

08 ➙ INS-FRC

Note : BP cables are same for BM-CPU, AM-CPU and CM-CPU, but it is different for MAX-L and MAX-XL, Chapter 2, gives details of BP cables.

3.1.3. Procedure to Modify Switch Unit Status in BM

From BP terminal we can modify status of switch units. Switch unit status can be modified from ins_sby to oos-opr, oos-sys to oos-opr, oos-opr to ins-sby etc. Interchange of active and standby units is also possible.

CDOSXX> m ↵ MDEBXX> def m ml ~mcm ↵ (Instead of mcm, pmsp can be used. Then action code 0 or 1 can be used in put or force options) MDEBXX> m ↵

Buffer size : ↵ Opcode : mswins OR mstreq OR mswich ↵ Subfield : 1 ↵

All other parameters except the two given below take default value.

Action code :1 ↵ (when pmsp is used only in place of mcm, 0 or 1 i.e put or force both options can be used.)

* unit ID : UID ↵ → [Here type unit id in hex.]

MDEBXX> ex ↵ CDOSXX> ex ↵

Chapter 3.

20 C-DOT DSS MAX

Note : Depending on action to be taken i.e. to make a switch unit, inservice, out of service or interchange of active/or standby, use required op code as given below :

Opcode = mswins → for changing unit status to ins-act/ins-sby = mstreq → for changing unit status to oos-opr = mswich → for interchanging active and standby units

Note : Do Not modify status of MU-0 and MU-1.

Ex : To modify the TI01-1 Switch unit status to OOS-OPR in BM-1 from BP terminal. From table 1.1 id for T101-1 is derived as A1.

Press control D. CDOS>m ↵

### WELCOME TO DD, MDEBUG & RETEST ### ….Type HE for MDEB & HE_P for DD help

MDEB 0 > def m ml ~mcm ↵ Logical symbol M redifined/defined.

MDEB 0 > m ↵ Buffer size = ? (24[1], 256 [2], 512[3], 1024[4]) (def = 128) ↵ Struct { Opcode = mstreq ↵ Char subfield = 1 ↵ Char dummy = ↵ Sender_pid = ↵ Mnt_com_hd { Unsigned short user_id = ↵ Unsigned char session_id ↵ Unsigned char job_id = ↵

} mci_hdr; unsigned char action_cod = 1 ↵ → 1 represent type of action i.e. force unsigned char unit_id = a1 ↵ → Here a1 is switch unit id for TI01-1

} MSTREQ;

% MDEB-I-INFO, Send ret. Val = 0 MDEB 0 > ex ↵

CDOS_0 > ex ↵ STACK DUMP

Note : Now view the switch unit status map by typing US ↵ on MDEB prompt. In US map TI01-1 should be in oos-opr status.

BASE MODULE


3.2. PROCEDURE TO MODIFY SRF COUNTER VALUE

When BM goes for STB-CLR due to SRF COUNTER OVER-FLOW, modify the SRF counter size to FFFF, then isolate the problem. This will avoid BM’s going for frequent STB-CLR due to SRF OVER-FLOW. This can be done from the IOP terminal or through BP terminal.

a) PROCEDURE TO INCREASE SRF COUNTER VALUE FROM IOP TERMINAL

I0P5C > conp ↵ Conp > m xx (xx is the BM BP ID for which SRF to be modified.)

MDEBxx>sy mrp_m_ro ↵ (To get the SRF address say XXXX)

Note: For S/W release 2_2_1_6 add 600 in Hex to address XXXX.

b) PROCEDURE TO INCREASE SRF COUNTER VALUE FROM BP TERMINAL Press control D Note : CDOSxx> m ↵ (xx is the BM BP ID for which SRF to be modified. MDEBxx> prn e ↵ Prn e stands for print enable. This is to be done to see recovery or general MDEBxx> ex ↵ messages on BP terminal. CDOS-XX> ex ↵

Example : To modify SRF counter value

For BM-1 Iop5C > conp ↵ CONP > m 0 ↵

### WELCOME TO DD, MDEBUG & RETEST ### … Type HE for MDEB & HELP for DD help

MDEB 0>sy mrp_m_ro ↵ mrp_m_ro : 0 x 5b1542 ← add 600 in Hex to get SRF counter address i.e. 5b1542+600 → 5b1b42 .

MDEB 0> exm.w 5b1b42 ↵ … Type CR to skip, space to modify, minus to go back (max = 9), … Plus to come back (max = 9), dot to exit 005B1B42 0064? …ffff ↵ 005B1B44 0030 ? . ↵ (press dot and return) MDEB 0> ex ↵ CONP > ex ↵

Chapter 3.

22 C-DOT DSS MAX

3.3. PROCEDURE FOR MODIFYING UNIT STATUS BY EDITING UNIT STATUS MAP

Unit status can also be modified by directly editing the unit status in the unit_status address, instead of mailing through ml~mcm. After modifying unit status give SOFT-START to the BM, BM comes up with modified to us provided modified unit cards are in good condition, else it goes back to its original status.

Note : This procedure involves down time and should be used with BP-CABLE connected to any of the BM-CPU.

Press Control D CDOSxx>m xx ↵ (Where xx is the BP-0 id of the required BM). MDEBxx> hlt sys ↵ (HALT-SYS to prevent BM’s updating its original status) MDEBxx>exm.w yyyy ↵ (YYYY is unit address)

After updating the unit status type. In the next address so that it comes back to MDEB>XX>> prompt.

MDEBxx> init s ↵ (To give SOFT START).

Example given below shows how to change TIC1-0 to TIC4-0 of BM-27 oos-opr

The address of the unit status to be changed from unit status map. First locate the line in which the UNIT is available, note down address of that line for example

TI01-0 is in 11th line its address is cc32a2.

Press Control D CDOS 34_0 >m ↵

### WELCOME TO DD, MDEBUG & RETEST ### ….Type HE for MDEB & HELP for DD help

MDEB34 > US ↵ 00CC3202 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@@@@@@@@

00CC3212 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@@@@@@@@


00CC3232 C0 C0 C0 C0 04 02 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@..@@@@@@@@@@



00CC3262 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@.@@@@@@@@@@



00CC3292 C0 C0 C0 C0 C0 C0 02 02 02 04 C0 C0 02 04 02 04 @@@@@@….@@….

BASE MODULE


00CC32A2 02 04 02 04 02 04 02 04 04 02 04 02 04 02 04 02 …………….

00CC32B2 04 02 04 02 04 02 04 02 02 04 02 04 02 04 C0 C0 …………..@@

00CC32C2 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@@@@@@@@

00CC32D2 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 02 02 C0 @@@@@@@@@@@@@..@

00CC32E2 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 @@@@@@@@@@@@@@@@

00CC32F2 02 02 02 02 C0 C0 C0 C0 02 04 C0 C0 C0 C0 C0 C0 ….@@@@..@@@@@.

Table 2.5

MDEB34> hlt sys ↵ MDEB34> exm.w cc32A2 ↵ … Type CR to skip, space to modify, minus to go back (max = 9), … plus to come back (max = 9), dot to exit

00CC32A2 0204? …9A02 ↵ 00CC32A4 0204? …9A02 ↵ 00CC32A6 0204? …9A02 ↵ 00CC32A8 0204? …9A02 ↵ 00CC32AA 0204? . ↵ (enter dot and press return)

MDEB34> init s ↵

Note : When BM comes up after soft start, view the unit status in US map.

3.4. PROCEDURE TO ENABLE DGN PRINT ON BP TERMINAL

This is required to be done when we want to get DGN failure report on BP terminal while conducting DGN for Switch-Units.

This can be seen only from BP, Terminal connected to the BM whose switch-unit is being diagnosed.

Connect BP terminal to BM. Press Control D CDOSxx>m ↵ MDEBxx>sy mda_print_flag ↵ (To get mda_print address) mda_print_flag : 0xcc6fa4 MDEBxx>exm.w cc6fa4 ↵

Exact procedure is given in example below :

Note : Whenever dgn fails, address value will be restored to 0000. To get reports again, repeat above procedure.

Chapter 3.

24 C-DOT DSS MAX

Ex :

Press control D CDOS34 > m ↵ MDEB 34>exm.w cc6fa4 ↵

…Type CR to skip, space to modify, minus to go back (max = 9), …plus to come back (max=9), dot to exit

00CC6FA4 0000? …0101 ↵ 00CC6FA6 020C? . ↵ (enter dot and press return) MDEB 34> prn e ↵ MDEB 34>ex ↵ CDOS 34_0>ex Unit tested – A1 Here A1 is unit id i.e. TI01-1 Failed to contact TIC Failed to contact TIC via alternate path.

3.5. PROCEDURE TO CHECK WHICH SWITCH UNIT IS BEING DIAGNOSED

3.5.1. Procedure to Know Whether Switch Unit is being Diagnosed

This can be seen from IOP terminal OR BP terminal. IOP5X > conp CONP> m xx ↵ (xx is BP) id for required BM) MDEBxx>msg ~DAP ↵ (DAP = Diagnostic Aid Process) When switch unit is not being diagnosed you will get message as below

OWNER ADDRESS OPCD SENDER MLEN

6C0 NONE

When SWU-UNIT is being diagnosed you will get message as :

OWNER ADDRESS OPCD SENDER MLEN

6C0 62A400 A7 18A10080 E

3.5.2. PROCEDURE TO FIND OUT THE IDENTITY OF SWITCH UNIT BEING DIAGNOSED

Press control D in BP terminal.

CDOSXX > m ↵ MDEBXX> def dgn exs mda_working _unit ↵ Logical symbol dgn defined

BASE MODULE


MDEBXX>dgn ↵ 00B4CB38 B0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Note : The line above is in response to typing dgn ↵ on MDEB prompt. First byte contains unit id in Hex which is being diagnosed. In this example, B0 is first byte and B0 is unit id for T109-0.

3.6. UNIT STATUS OF CONTROLLERS IN ISTU

ITC-0, ITC-1 are functioning as TIC as ISDN frame and have unit ids similar to TIC ids. ICC-0 and ICC)1 UID depends on which frame ISDN is equipped.

ICC1-0 ICC1-1 ISDN Equipped in I frame of BM ICC2-0 ICC2-1 ISDN Equipped in II frame of BM ICC3-0 ICC3-1 ISDN Equipped in III frame of BM ICC4-0 ICC4-1 ISDN Equipped in IV frame of BM

UNIT NAME UID (Unit identify) in BP ICC1-0 & ICC1-1 C0 & C1 ICC2-0 & ICC2-1 C2 & C3 ICC3-0 & ICC3-1 C4 & C5 ICC4-0 & ICC4-1 C6 & C7

Table 2.6

Note : Unit status for ISTU can be modified as described previously for other BM units. For ITC to come in service corresponding ICC should be brought inservice first.

3.7. INITIALISATION FROM BP TERMINAL CONNECTED TO MODULE

Command may be issued for initialising the module to which BP terminal is connected. AM/CM/BM/SUM may be initialised from terminal connected to respective module.

PROCEDURE TO INITIALISE FROM TERMINAL CONNECTED TO MODULE

Connect BP terminal to module and set the communication speed to 4800/9600 bps as required. Suppose we want to module to soft start level.

Press control D

CDOS XX > m ↵ MDEB XX > init ↵

Chapter 3.

26 C-DOT DSS MAX

Init options :

Q : Quit S : Softstart P : Part init I : Patch init C : Code load

Default - stable clear.

Init option > S ↵

Note : Module will go for soft start & come up.

3.8. TYPICAL MESSAGES COMING ON BP TERMINAL

3.8.1. Normal Messages (Do not require any action)

i) Following are the normal messages appearing on a BP terminal :

OSPM>> CPU IDLE_TIME = 284144ms DURING THE PAST 300340 ms [“=94%]

TIME IS 30-MAY-2001 22:46:09

ii) Heal !! WOKEUP AT BOUNDAY HOUR

iii) Whenever a MODULE recovers after initialisation, all its switch units get initialise and if the initialisation is successful, all the working `TIC’s’ get unblocked at the end with following messages :

% OCP>> INIT – CONTROL LEVEL : 5

% OCP>> TIC – UNBLOCKED = A03580 % OCP>> INIT – CONTROL LEVEL : 5 % OCP>> INIT – CONTROL LEVEL : 5 % OCP>> INIT – CONTROL LEVEL : 4 % OCP>> INIT – CONTROL LEVEL : 3 % OCP>> INIT – CONTROL LEVEL : 2 % OCP>> INIT – CONTROL LEVEL : 1 % OCP>> INIT – CONTROL LEVEL : 0

Note : Above message shown is for TIC `A0’ i.e. TIC 01-0. Similar messages will be repeated for all the TICs.

BASE MODULE


3.8.2. Critical Messages – Require Appropriate Action

i) In case following messages (Called Recoveries) are coming frequently on BP Terminal the same should be reported to `CDOT’ for further debugging:

Process 180C3783h (code 207) Cmf_Rec_Routine with parameters

1. 39h

2. 0h

3. 1h

EQN : 7044200h

Above recovery indicates that this is related to `DATA’ and more specifically due to wrong routing & Trunking data creation on one or more routes.

Note 1: There can be many such recoveries with different process, code, rec_routine and parameters Each one of these indicate different nature of fault. Frequent recoveries may cause the `BM’ to go for initialisation with reason “SRF counter overflow”.

Note 2: However if such recoveries are not frequent then the same can be ignored.

ii) Whenever some switch unit becomes OOS-SUS, message is flashed on `BP’ terminal with it’s Unit-ID with message MCM_SUS.

These messages are very helpful in debugging switch unit faults.

3.8.3. Message on BP Terminal During Initialization

a) Message : P0-1E

Remarks : Port 0 & port 1 enabled. i.e. both mu-0 & mu-1 are enabled

b) Message : Status 2 Off board out switch over

Remarks : Whichever BP connected to terminal is active and offboard memory i.e. mu-0/mu-1 not accessible.

c) Message : Change TS 98, 9c, 9e

Remarks : Change Time Switch, path selected is 98,9c,9e i.e., BMS-0, SCIC-0, TSC-0. Similarly change SCI means SCIC changed, change MS means BMS changed.

Chapter 3.

28 C-DOT DSS MAX

d) Message : Path 98, 9c, 9e, 66 Path 98, 9c, 9f, 66 Path 98, 9c, 9e, 67 Path 98, 9c, 9f, 67

Remarks : All above are unit ids in Hex. These units are tested for selecting download path. When any combination of selected path is ok, down loading starts with message DNLD, ok22K ok

e) Message : LF 98 to 9e

Remarks : LE refers to Link fault. Here it is indicated that, there is link fault between BMS-0 & TSC-0. Change cards & observe message again. Similarly link faults will be indicated between any units with unit ids in Hex.


Chapter 4.

Remote Base Module Monitoring Through BP Terminal

4.1. REMOTE BASE MODULE

Remote Base Module hardware is same as that of a colocated BM except for TSS card. In RBM TSS card will be replaced by ETS/RTS card. BPU mother jumpers should be set depending on BM number. ACIO and clock cables, digital trunk cables should be connected properly as per RSU Installation manual. When RBM is switched on BP terminal will display messages as follows (No commands need be given, only communication speed should be 4800/9600 bps depending on type of processor.)

BP terminal messages given below will be observed with healthy TSC/ETS cards and if messages are different, change controller cards and observe messages.

Note : For BP cable details refer Fig. 1

Messages on RBM BP Terminal a) Message : Health log for TSC_0 is 0

Remarks : Health log is 0, TSC card is OK

Message : Health log for TSC_1 is 0

Remarks : Health log is 0, TSC-1 card is OK

b) Message : Health log of RTS_0 is 400

Remarks : Health log is 400. ETS on copy 0 of TSC is OK.

Message : Health log of RTS_1 is 400

Remarks : Health log is 400, ETS copy_1 of TSC is OK.

Chapter 4.

30 C-DOT DSS MAX

c) Message : DTK health log for TSC_0 is 0011111111111111

Remarks : Status of PCMs connected to ETS card in TSU is represented by 16 bits. It is possible to use only maximum of 8 pcms connected to ETS card in each copy. In the above, 16 bits indicate status of PCMs. 0 ➝ PCM is OK through to main Exchange 1 ➝ PCM is down and not through to main Exchange In the above case 1st & 2nd PCMs are OK. Remaining 6 are down or not equipped; last 8 bits can be ignored. RBM digital trunks counted from 1 to 8 on bus-0 and 17 to 24 on Bus-1 side.

Message : DTK health log for TSC-1 is 1011111111111111

Remarks : In this case RBM dtk 17 is down and dtk18 is OK. Remaining dtks 19 to 24 are down or not equipped. Ignore last 8 bits.

d) For other messages refer para 3.8.3.

4.2. PROCEDURE TO SEE RBM-DTK (PCM) STATUS

We can see the status of digital trunks (i.e. Dtk or PCM) connected to RBM on BP terminal. To see the dtk status on BP terminal do the following :

Press Control D CDOS_02>m ### WELCOME TO DD, MDEBUG & RETEST ### …Type HE for MDEB & HELP for DD help

MDEB 2> def dtk md @mbc_dtk_link_sta l +20 Logical symbol dtk defined. MDEB 2>dtk ↵

00CC3086 02 02 02 02 02 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 …..@@@@@

00CC3096 02 02 02 02 02 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 C0 …..@@@@

Table 4.1

Note :

First line shows status of DTK 01 to DTK 08 (BUS-0). (dtks 9 to 16 not used) Second line shows status of DTK 17 to DTK 24 (BUS-1). (dtks 25 to 32 not used)

In the above example 5 dtks are equipped on Bus0 and 5 dtks are equipped on Bus-1.

Status of digital trunks of RBM are represented in HEX as given below :

02-> INS-ACT 98-> 00S-SYS C0-> UNEQUIPPED

mailto:md@mbc_dtk_link_st

REMOTE BASE MODULE MONITORING THROUGH BP TERMINAL


4.3. PROCEDURE TO SEE RBM-MODE (RBM OR RBMSA)

When all PCMs connected to RBM are down, RBM goes to stand alone mode. On BP temrinal connected to RBM we can see whether RBM is in RBM mode or RBM stand alone mode by doing the following :

Press Control D ↵ CDOS 12>m ### WELCOME TO DD, MDEBUG & RETEST ### Type HE for MDEB & HELP for DD help

MDEB 2> def mode md @mpi_bm_mode 1+10 ↵ Logical symbol MODE defined.

MDEB 2>mode ↵ 00CBC6CE 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ………

Table 4.2

Note :

1. First byte shows the status of RBM 05—RBM mode 06—RBMSA mode

2. RBM goes to RBMSA (RBM stand alone) mode when all the dtks (PCMs) connected to main exchange are down.

4.4. PROCEDURE TO TEST PCM (DTKS) OF RBM USING BP TERMINAL

RBM PCMs (digital trunks) are identified as follows on each copy of TSC.

TSC-COPY dtk id dtk id dtk id dtk id dtk id dtk id dtk id dtk id

TSC-0 (BUS-0)

1 2 3 4 5 6 7 8 9 to 16 not used

TSC-1 (BUS-1)

17 18 19 20 21 22 23 24 25 to 32 not used

Table 4.3

TO TEST PCMS DURING INITIAL POWER ON AND BM HAS NOT COME UP: When RBM is down, BP terminal connected to RBM displays messages as given in Section 4.1, C. Each PCM can be tested by looping transmit and receive pairs at different points i.e. RBM site, transmission room DDF, Main Exchange transmission room DDF, digital trunk cable connector on back plane of CM. Details of cable termination on connector / DDF are given in RSU installation manual. Each PCM TX & RX can be looped one by one and fault can be isolated as indicated in the following section.

Chapter 4.

32 C-DOT DSS MAX

4.5. PROCEDURE TO IDENTIFY PCM FAULTS USING BP TERMINAL BY LOOPING TX/RX PAIRS AT DIFFERENT POINTS

PCM (dtk) faults connected to RBM may be located by looping TX-a to Rx-a and TX-b to Rx-b towards RBM from different points in transmission path. This loop should always be extended towards Remote Base Module and not towards CM. Status of PCM streams (dtks) may be observed on BP terminal as explained in section 4.1 or 4.2. Section 4.1 is to be used when RBM is down. Section 4.2 may be used when RBM is up and few of equipped PCMs (dtks) are down. STatus of PCMs may be observed by giving loop/break on individual PCMs from different points. By following steps given below, PCM faults may be localized.

Step TX-RX Loop Point PCM status after loop on BP terminal connected to

RBM Remarks

1 RBM site transmission room DDF

PCM has come in service Wiring OK upto transmission room (TX & RX reversal may be there) GO TO STEP 3

2 RBM site transmission room DDF

PCM has not come in service Cable Termination fault in connector, DDF or ulinks in transmission equipment. Rectify fault & repeat above step.

3 Main Exchange Transmission room DDF

PCM has come in service Wiring OK at RBM site & no interchange of TX-RX at RBM (Tx & Rx reversal may be there at Main exchange transmission room DDF. Go to step 5.

4. Main Exchange Transmission room DDF

PCM has not come in service Wiring not ok at RBM site interchange TX & RX at RBM site DDF only. Interchange TX RX jumpers at RBM PDF and repeat the above step.

5. 7 x 3 connector of DTK cable on back plane of CM

PCM has come in service Everything OK from transmission room equipment to RBM site (Interchange of TX-RX may be there at Main Exchange Transmission Room DDF.

Note :

After testing following above steps if PCM is not coming in service after putting through connector to CM, and comes in service only for Loop from 7 X 3 connector of DTK cable on backplane of CM, there is interchange of TX-RX pairs at Main Exchange transmission room DDF. Interchange TX/RX pairs of that particular PCM and put through the connector to CM. Now verify PCM status on BP terminal and it should be OK.

REMOTE BASE MODULE MONITORING THROUGH BP TERMINAL


4.6. PROCEDURE TO IDENTIFY PCM FAULTS WHEN RBM IS ACTIVE

Define the dtk symbol on BP terminal as given in section 3.2 and identify the faulty PCM id. View the status of the PCM by typing dtk ↵ on MDEBxx > prompt. Loop Tx/Rx of that particular PCM at different points as described in section 4.5 and view the status of PCM on BP terminal by typing dtk ↵ on MDEB xx > prompt, This process can be repeated until fault is PCM isolated.

34 C-DOT DSS MAX

Chapter 5.

Central Module & Administrative Module

5.1. CENTRAL MODULE

5.1.1. CM (SSC) Terminal

1. Unit status of CM can be seen from terminal connected to CM CPU. (i.e. SSC)

2. For BP cable refer Chapter 2

3. (a) For MAX-L connect BP cable to Frame_no:3, slot no: 2A, TAB:1 of CM

(b) For MAX-XL connect BP cable to J25 & J52 (marked as RS-232), TAB-1 of frame-5 copy-0 and copy-1 of CM.

4. (a) Set baud rate of terminal to 9600 for BPC/HPC

(b) Set baud rate of terminal to 4800 for CPU-S04/CPU-S05.

Numbers in hex representing unit status are given below :

02 – INST-ACT 04 – INS-SBY 9A-00S-OPR 98-00S-SYS

96 – 00S-SUS 08 – INS-FRC

5.1.2. Procedure to View A Switch Unit Status on SSC Terminal

By defining a symbol on SSC terminal we can see the switch unit status of CM on SSC terminal. Procedure viewing switch unit status is given below:

Press Control D CDOS 64_0 >m ↵ ### WELCOME TO DD, MDEBUG & RETEST ### ….Type HE for MDEB & HELP for DD help MDEB 64> def us ca mtdusmap ( ) ↵ Logical symbol us defined / redefined .

CENTRAL MODULE & ADMINISTRATIVE MODULE


MDEB 64> prn e ↵ MDEB 64> us ↵ Hit Ctrl-C to cancel

CLK/NSC : C0=4 C1=2 SWC_0 : C0 = 2 C1 = 2 SWC_1 : C0 = 2 C1 = 2 SWC_2 : C0 = 2 C1 = 2 SWC_3 : C0 = 2 C1 = 2 SWC_4 : C0 = 2 C1 = 2 SWC_5 : C0 = 2 C1 = 2 SWC_6 : C0 = 2 C1 = 2 SWC_7 : C0 = 2 C1 = 2 SWC_8 : C0 = 2 C1 = 2 SWC_9 : C0 = 2 C1 = 2 SWC_10 : C0 = 2 C1 = 2 SWC_11 : C0 = 2 C1 = 2 SWC_12 : C0 = 2 C1 = 2 SWC_13 : C0 = 2 C1 = 2 SWC_14 : C0 = 2 C1 = 2 SWC_15 : C0 = 2 C1 = 2 SSB/CBX : C0 = 4 C1=2 IFC/CSM_0 : 2 IFC/CSM_1 : 2 IFC/CSM_2 : 2 IFC/CSM_3 : 2 IFC/CSM_4 : 2 IFC/CSM_5 : 2 IFC/CSM_6 : 2 IFC/CSM_7 : 2 IFC/CSM_8 : 2

Chapter 5.

36 C-DOT DSS MAX

IFC/CSM_9 : 2 IFC/CSM_10 : 2 IFC/CSM_11 : 2 IFC/CSM_12 : 2 IFC/CSM_13 : 2 IFC/CSM_14 : 2 IFC/CSM_15 : 2 IFC/CSM_16 : 98 IFC/CSM_17 : 2 IFC/CSM_18 : 2 IFC/CSM_19 : 2 IFC/CSM_20 : 2 IFC/CSM_21 : 2 IFC/CSM_22 : 2 IFC/CSM_23 : 2 IFC/CSM_24 : 2 IFC/CSM_25 : 2 IFC/CSM_26 : 2 IFC/CSM_27 : 2 IFC/CSM_28 : 2 IFC/CSM_29 : 2 IFC/CSM_30 : 2 IFC/CSM_31 : 2 CMS_0 : 2 CMS_1 : 2 CMS_2 : 2 CMS_3 : 2

SSC : C0 = 2 C1 = 4

MEM : C0 = 2 C1 = 2

SWP : C0 = 4 C1 = 2



FUNCTION RETURNS ff IN D0

FUNCTION RETURNS 356436 IN A0

Table 5.1 Function call over MDEB 64 > ex CDOS 64_0 > ex Note : Unit Ids i.e. SWC, IFC, CMS start from zero. Ifc0 in CM terminal is IFC 1 in Crp terminal. CMS0 in CM terminal is CMS1 in Crp terminal. In the unit status map CM in Table 4.1, we can see that clk0 is ins-sby, clk1 ins-act, All switch cards are ins-act. Copy-0 of the SSBID (CBX) is ins-sby, copy-1 of SSBID (CBX) is ins-active. If C17 (i.e. Ifc 16 in map is Ifc17 in crp) is oos-sys other Ifcs are ins-act. CMs 1,2,3,4 are active. SSC-0 is ins-act, ssc-1, ins-sby, switch plane (SWP) i.e SS-0 is ins-sby and SS-1 is ins-act. SWP gives the consolidated status of switch plane. For example if any unit in SS_0 (SWCX-0, CBX-0, CLK-0) is 00S-SUS, then SWP-0 will also be 00S-SUS.

5.1.3. Procedure to Modify Switch Unit Status in CM

Press Control D CDOS 64> m ↵ MDEB 64_1>ca mcm_pus (%UID, %STATUS) ↵ UNIT UID Number in Hex representing Switch unit

Status SS-0 62 02 → INS-ACT 04 → INS-SBY SS-1 63 9A→ 00S-OPR 98 → 00S-SYS SSC-0 64 91 → 00S-EXT 96 → 00S-SUS SSC-1 65 CMS-1 to CMS-4 66 to 69 IFC1 to IFC16 6A to 79 IFC17 to IFC32 7A to 89 CLK-0 8A CLK-1 8B SSBID-0 8C SSBID-1 8D SWC1-0 → SWC16-0 SWC1-1 → SWC16-1 Refer to Table 1.1 for Switch Unit ids

Chapter 5.

38 C-DOT DSS MAX

Table 5.2

EX : TO MODIFY IFC-1 STATUS TO 00S-0PR Derive unit id from table 1.1 for Ifc1. Press Control D CDOS 64 > m ↵ MDED 64>ca mcm_pus (%6A, %9A) ↵ MDEB 64>ex ↵ CODS 64> ex ↵

5.1.4. To Modify SRF Counter of CM-CPU

Press control D CDOS 64> m ↵

MDEB 64> sy mrp_m_ro ↵ (To get SRF address) mrp_m_ro : 0 x 307a78 (SRF address) → to this add 600 (in Hex) 307a78 + 600 = 308078 for 2_2_1_6 software.

MDEB 64 > ex ↵ CDOS 64_0 > ex ↵ Press control D CDOS 64_0 > m ↵

### WELCOME TO DD, MDEBUG & RETEST ### … Type HE for MDEB & HELP for DD help

MDEB 64 > exm.w 308078 ↵↵↵↵

…Type CR to skip, space to modify, minus to go back (max = 9) …plus to come back (max = 9), dot to exit

00308078 0064? …ffff ↵ 0030807A 0030? . ↵ (press dot and enter) MDEB 64>ex ↵ CDOS 64> ex ↵



5.1.5. Procedure to See Switch Unit Status in CM By Accessing Processor (SSC) in CM From IOP Terminal

IOPX > conp ↵ CONP > m 64 ↵

### WELCOME TO DD, MDEBUG & RETEST ### …. Type HE for MDEB & HELP for DD help

MDEB 64 > def us md @mcm_usmap l + 50 ↵

MDEB 64>def ↵

TAG LOGICAL EQUIVALENCE STRING

0 US md 46a980 l + 50

MDEB 64>us ↵ 0044EE0C 04 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 ………..

0044EE1C 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 ………..

0044EE2C 02 02 04 02 02 02 02 02 02 02 02 02 02 02 02 02 ……..

0044EE3C 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 02 ………..

0044EE4C 02 02 02 02 02 02 02 02 02 04 02 02 04 02 00 00 ………..

Table 5.3

MDEB 64 > ex ↵ CPM[ > ex ↵

Note : First column of table 5.3 has address. Switch Unit identities to corresponding position in Table 5.3 from 2nd column are given below in Table 5.4.

Clk-0

Clk-1

Swc 1-0

Swc1-1 Swc 2-0

Swc 2-1

Swc 3-0

Swc 3-1

Swc4-0

Swc4-1

Swc 5-0

Swc 5-1

Swc6-0

Swc 6-1

Swc 7-0

Swc 7-1

Swc8-0

Swc 8-1

Swc 9-0

Swc 9-1

Swc 10-0

Swc 10-1

Swc 11-0

Swc 11-1

Swc 12-0

Swc 12-1

Swc 13-0

Swc 13-1

Swc 14-0

Swc 14-1

Swc 15-0

Swc 15-1

Swc16-0

Swc 16-1

SSBID (CBX) -0

SSBID (CBX) -1

Ifc 1

Ifc 2

Ifc 3

Ifc 4

Ifc 5

Ifc 6

Ifc 7

Ifc 8

Ifc 9

Ifc 10

Ifc 11

Ifc 12

Ifc 13

Ifc 14

Ifc 15

Ifc 16

Ifc 17

Ifc 18

Ifc 19

Ifc 20

Ifc 21

Ifc 22

Ifc 23

Ifc 24

Ifc 25

Ifc 26

Ifc 27

Ifc 28

Ifc 29

Ifc 30

Ifc 31

Ifc 32

CMS 1

CMS 2

CMS 3

CMS 4

SSC-0

SSC-1

Mu -0

Mu -1

SS -0

SS -1

-- --

Table 5.3

EX : TO SEE THE SWITCH UNIT STATUS OF SS FROM TABLE 5.3

Referring to Table 5.3 & Table 5.4, we can see that SS-0 is in ins-sby status and SS-1 is ins-act status.

Chapter 5.

40 C-DOT DSS MAX

5.1.6. To Modify CM Unit Status From IOP Terminal

IOP5X > conp ↵ Conp> m 64 ↵

### WELCOME TO DD, MDEBUG & RETEST ### …Type HE for MDEB & HELP for DD help

MDEB 64 > m ↵ Buffer size = ? (24 [1], 256[2], 512[3], 1024[4]) (def = 128)

Struct { where Opcode = mstreq ↵ mstreq → OOS – OPR Char subfield =1 ↵ mswins → INS-ACT Char dummy = ↵ mswich → INTCHG Sender_pid = ↵ Mnt_com_hd { Unsigned short user_id = ↵

Unsigned char session_id = ↵ Unsigned char job_id = ↵ } mci_hdr ; unsigned char action_cod = 1 ↵ unsigned char unit_id = UNIT ID of CM * ↵ } MSTREQ ; %MDEB-I INFO Send ret. Val=0 MDEB 4>ex → Conp > ex ↵ IOP 5x >

* Ref table 5.2 for CM UNIT ID

** DO NOT MODIFY MU-0, MU-1, SS-0, SS-1

5.1.7. To Check Status of External Clock In CM

After connecting BP Terminal at 'SSC', status of external clocks (RClk0, Rclk1, Rclk2) can be seen in S/W Release 2_2_1_6.

MDEB_64> md @mcm_clk_status ↵

Alternatively use address to view the status of External Clock in CM

MDEB_64> md 46970a ↵ Byte 0 1 2 3 4 5 6 7 8 9 a b c d e f

Address DUP CLK0 RCLK2

RCLK1

RCLK0 USRN - DUP

CLK1 RCLK2

RCLK1

RCLK0 USRN - - - - -

NSC0 NSC1



5.2. ADMINISTRATIVE MODULE

5.2.1. AP Terminal

Switch unit status of AM can be seen from BP terminal connected to CPU of AM.

For BP cable details, refer fig. No :

a) For MAX-L connect BP cable to Frame No. 4 slot No. 2A, TAB : 1 of CM CABINET

b) For MAX-XL connect BP cable to BPC-AUX TAB – 1 frame –6 of CM of copy-0 and copy-1. (Refer Chapter 3)

a) Set baud rate of terminal to 9600 for BPC/HPC

b) Set baud rate of terminal to 4800 for CPU-S04/CPU-S05

5.2.2. To View Switch Unit Status in AM

Press Control D CDOS 56_1 > m ↵ ### WELCOME TO DD, MDEBUG & RETEST ### …. Type HE for MDEB & HELP for DD help MDEB 56>prn e ↵ MDEB 56 > def us ca mtdsmap ()↵ Logical symbol US redefined MDEB 56> us ↵ Hit Ctrl-C to cancel

AP : C0 = 4 C1 = 2

MEM : C0 = 2 C1 = 2

IOP : C0 = 2 C1 = 4

ADC : 2

CM : 2

Numbers in Hex representing unit status are given below :

02 – INS-ACT 04 – INS-SBY 9A-00S-OPR 98-00S-SYS

96 – 00S-SUS 91-00S-EXT

FUNCTION RETURNS ff IN D0

FUNCTION RETURNS 200148 IN A0

Chapter 5.

42 C-DOT DSS MAX

Function Call over MDEB 56> ex ↵ CDOS 56> ex ↵

Note : CM : 2 Gives the status of central module.

Status of CM as module → 02 → Module active 90→ Module 00S-INI (out of service under initialisation)

5.2.3. Procedure to Modify Switch Unit Status in AM

Press control D CDOS 56 > m ↵ MDEB 56_1>ca mac_pus (% UID % STATUS)

UNIT UID STATUS

AP-0 56 02 →INS-ACT

AP-1 57 04 →INS-SBY

IOP-0 5C 9A →00S-OPR

IOP-1 5D 91 →00S-EXT

ADC 5A 96 →00S-SUS

98 →00S-SYS

Table 5.1

Ex : To modify status of IOP-0 to 00S-OPR

Press control D CDOS 56> m ↵ MDEB 56>ca mac_pus (%5C, %9A) ↵ MDEB 56>ex ↵ CDOS 56>ex ↵

Note : DO NOT MODIFY STATUS OF MU-0 & MU-1

5.2.4. Procedure to Modify SRF Counter of AM

Press Control D CDOS 56> MDEB 56>sy mrp_m_ro ↵ (To get SRF address) Mrp_m_ro : 0 x 368694 (SRF Address) → To this add 600 (in Hex) If software is 2_2_1_6 368694 + 600 = 368c94 MDEB 56 > exm.w 368c94 ↵



Ex : To modify SRF counter value in AM.

Press Control D CDOS 56_1 > m ↵ ### WELCOME TO DD, MDEBUG & RETEST ### …Type HE for MDEB & HELP for DD help

MDEB 56> sy mrp_m_ro ↵ Mrp_m_ro : 0 x 368694 → Note : To get SRF address add 600 in Hex to this value ie. 368694 + 600 = 368c94

MDEB 56>exm.w 368c94↵ TIME IS 31 JAN 2001 12 : 30 : 33 ….Type CR to skip, space to modify, minus to go back (max = 9) ….plus to come back (max = 9), dot to exit. 00368C94 0064? …ffff ↵ 00368C96 0030? . ↵ (Press dot and return) MDEB 56>ex ↵ CDOS 56 > ex ↵ . ↵

5.2.5. Procedure to see the ETE of BM with SUM at AP Terminal

With this procedure we can check the ETE of BM with SUM and other details like BM status, ETE on or off etc from the AP terminal.

Press Control D CDOS 56_1>m↵ ###WELCOME TO DD, MDEBUG $RETEST### ... Type HE for MDEB &HELP for DD help MDEB56> def et md @nbm7_data l+c0↵ Logical symbol et defined

This will give us the map of ETE and other details for all the BMs.

Chapter 5.

44

MDEB56>et ↵

0066E24E 01 00 0066E25E 00 01 0066E26E 00 00 0066E27E 00 00 0066E28E 00 00 0066E29E 00 00 0066E2AE 00 00 0066E2BE 00 00 0066E2CE 00 00 0066E2DE 00 00 0066E2EE 00 00 0066E2FE 00 00

On this MAPpossible valuPos. Value

00

01

With the aboActive or in Owith CCS#7 check the ET♦ In case♦ For loc

5.2.6. Address for

Please refer A

B 1 B 2 B 3

B 0

M-0
01 01 01 01 01 0101 00 01 01 01 0101 01 00 00 00 0000 00 00 00 00 0000 00 00 00 00 0000 00 00 00 00 0000 00 00 00 00 0000 00 00 00 00 0000 00 00 00 00 0000 00 00 00 00 0000 00 00 00 00 0000 00 00 00 00 00
six bytes represent ones. Byte 1 Byte 2 Byte

BM Down

Non-Home BM

CCSTrksAbse

BM UP Home BM CCSTrksPres

ve MAP we can able to OS-INI, whether the T

trunks available or not. E {End-to-End link) of B of BM is not equipped aal and remote line BM b

SRF Counters in Var

nnexure I for the detail

B 1

M-0
01 01 01 01 00 0 00 00 00 00 00 0 00 00 00 00 00 0 00 00 00 00 00 0 00 00 00 00 00 0 00 00 00 00 00 0 00 00 00 00 00 0 00 00 00 00 00 0 00 00 00 00 00 0 00 00 00 00 00 0 00 00 00 00 00 0 00 00 00 00 00 0
e BM, which are expla

3 Byte 4 Byt

#7 nt

ETE off BM

#7 ent

ETE On BM

see the details of every runk BM is Home BM orFinally the fourth bite isM with SUM is ON or Oll the bytes will be showytes 2, 3 and 4 will have

ious Configurations

s of symbols and address

B

M-0
0 01 00 0 01 00 0 00 00 0 00 00 0 00 00 0 00 00 0 00 00 0 00 00 0 00 00 0 00 00 0 00 00 0 00 00
2
M-3 M-3 M-3
C-DOT DSS MAX

ined below with

e 5 & Byte6

Unequipped

equipped

BMs like BM is Non Home BM more helpful to FF. n as 00. a value 00.

es.


Chapter 6.

Signaling Unit Module (CCS7 Module)

6.1. INTRODUCTION

The SUM BP cable details are given in Figure 2.3. Set the baud rate for 9600 and connect bp cable to SLOT No. 5 connector A tab 2 position of SUM frame.

6.1.1. PROCEDURE TO SEE THAT ETE WITH SUM TO OTHER BM’S HAVING #7 TRUNKS.

Sum communicates with other BMs & Home BM (BM in which SUM is Equipped) on c.85 links. These C.85 links are nailed up through PHC timeslots (channel). By defining a symbol et, we can find out which PHC time slot is used by SUM to nail up C.85 links towards BPs of BMs having No. 7 trunks.

Press control D (Note : Each time when not required exit from MDEB5e> & CHAOS 5e> Prompt by giving ex ↵ CHAOS : 5E_0>m ↵ ### WELCOME TO DD, MDEBUG & RETEST ### …. Type HE for MDEB & HELP for DD help. MDEB 5e > def et md @nrwdatabase +1d00 l +80 ↵ Logical symbol ET defined. MDEB 5e>et ↵

BM-1 BM-2 BM-3 BM-4 005EE2DA 00 00 FF 00 00 01 FF 00 00 02 49 00 00 03 FF 00 ………

005EE2EA 00 04 FF 00 00 05 FF 00 00 06 6A 00 00 07 FF 00 →For BM5 to BM8

005EE2FA 00 08 2A 00 00 09 FF 00 00 0A 5A 00 00 0B FF 00 →For BM9 to BM12

005EE30A 00 0C 0D 00 00 0D FF 00 00 0E FF 00 00 0F FF 00 →For BM13 to BM16

005EE31A 00 10 0A 00 00 11 FF 00 00 12 FF 00 00 13 FF 00 →For BM17 to BM20

005EE32A 00 14 4D 00 00 15 FF 00 00 16 FF 00 00 17 FF 00 →For BM21 to BM24

005EE33A 00 18 2E 00 00 19 FF 00 00 1A FF 00 00 1B 6E 00 →For BM25 to BM28

005EE34A 00 1C FF 00 00 ID 3A 00 00 1E 09 00 00 1F 5E 00 →For BM29 to BM32

Table 6.1

Chapter 6.

46 C-DOT DSS MAX

MDEB 5e > ex ↵ Chaos 5E > ex ↵

Note : In the above example 11 BM’s are having ETE with SUM all BM No’s are logical numbers. BM’s having ETE is allotted with phc channel number otherwise it is marked as FF.

Leaving the first column which has address, other columns can be counted from 1 to 16. Columns 2,6,10,14 have the BM Nos and columns 3,7,11,15 have PHC channel nos. allocated for that corresponding BM No.

PHC card slot and corresponding channel numbers in hex are indicated in table 6.2 below. PHC-CARD (Slot No.) Channel No. 7 08 to 0f 8 18 to 1f 9 28 to 2f 10 38 to 3f 17 48 to 4f 18 58 to 5f 19 68 to 6f 20 78 to 7f

Table 6.2

Ex : In the above table 6.1 BM-03 is having ETE with SUM through 49, BM-9 (Logical No. 08) is having ete with sum through PHC channel 2A… so on.

6.1.2. Alternative Procedure to see the ETE of BM with SUM at AP Terminal

With this procedure we can check the ETE of BM with SUM and other details like BM status, ETE on or off etc from the AP terminal.

Press Control D CDOS 56_1>m↵ ###WELCOME TO DD, MDEBUG $RETEST### ... Type HE for MDEB &HELP for DD help MDEB56> def et md @nbm7_data l+c0↵ Logical symbol et defined

This will give us the map of ETE and other details for all the BMs.

SIGNALING UNIT MODULE (CCS7 MODULE)

APPLICATION NOTE ON BAS

MDEB56>et !

0066E24E 01 00

0066E25E 00 01

0066E26E 00 00

0066E27E 00 00

0066E28E 00 00

0066E29E 00 00

0066E2AE 00 00

0066E2BE 00 00

0066E2CE 00 00

0066E2DE 00 00

0066E2EE 00 00

0066E2FE 00 00

On this MAPpossible valuPos. Value

00

01

With the aboActive or in Owith CCS#7 check the ET♦ In case♦ For loc

6.2. PROCEDURE TO

Press control D CHA0S : 5E>m

B 1 B 2 B 3

B 0

M-0

E PROCESSOR TERMINAL

01 01 01 01 01 01

01 00 01 01 01 01

01 01 00 00 00 00

00 00 00 00 00 00

00 00 00 00 00 00

00 00 00 00 00 00

00 00 00 00 00 00

00 00 00 00 00 00

00 00 00 00 00 00

00 00 00 00 00 00

00 00 00 00 00 00

00 00 00 00 00 00

six bytes represent ones. Byte 1 Byte 2 Byte

BM Down

Non-Home BM

CCSTrksAbse

BM UP Home BM CCSTrksPres

ve MAP we can able toOS-INI, whether the T

trunks available or not. E {End-to-End link) of B of BM is not equipped aal and remote line BM b

SEE THE TERMINAL

B 1

M-0

COMMANDS

01 01 01 01 00 0

00 00 00 00 00 0

00 00 00 00 00 0

00 00 00 00 00 0

00 00 00 00 00 0

00 00 00 00 00 0

00 00 00 00 00 0

00 00 00 00 00 0

00 00 00 00 00 0

00 00 00 00 00 0

00 00 00 00 00 0

00 00 00 00 00 0

e BMs, which are expla

3 Byte 4 Byt

#7 nt

ETE off BM

#7 ent

ETE On BM

see the details of everyrunk BM is Home BM orFinally the fourth bite isM with SUM is ON or Oll the bytes will be showytes 2, 3 and 4 will have

TABLE OF SUM

B

M-0

0 01 00

0 01 00

0 00 00

0 00 00

0 00 00

0 00 00

0 00 00

0 00 00

0 00 00

0 00 00

0 00 00

0 00 00 2
M-3 M-3 M-3
47

ined below with

e 5 & Byte6

unequipped

equipped

BM like BM is Non Home BM more helpful to FF. n as 00. a value 00.

Chapter 6.

48 C-DOT DSS MAX

### WELCOME TO DD, MDEBUG & RETEST ### Type HE for MDEB & HELP for DD help

MDEB 5e> def tt md @terminal_table l + 80 ↵ Logical symbol TT redefined.

MDEB 5e>TT 005F500E 09 FC 08 FC 0A FC 0B FC 0C FC 0D FC 0E FC 0F FC

005F501E 28 FC 29 FC 2A FC 2B FC 2C FC 2D FD 2E FC 2F FC

005F502E 38 FC 39 FC 3A FC 3B FC 3C FC 3D FC 3E FC 3F FD

005F503E 48 FC 49 FC 4A FD 4B FD 4C FC 4D FC 4E FC 4F FC

005F504E 58 FC 59 FD 5A FC 5B FC 5C FC 5D FC 5E FC 5F FC

005F505E 68 FC 69 FC 6A FC 6B FD 6C FC 6D FC 6E FC 6F FC

005F506E 78 FC 79 FC 7A FC 7B FD 7C FC 7D FC 7E FC 7F FD

005F507E FF FE FF FE FF FE FF FE FF FF FF FF FF FE FF FE

Table 6.3

The above Table shows allocation of phc channels. From this table 6.3 we can determine how many phc channels are being used. Status is represented as follows :

FC → USED FD → FREE

Ex : To know status of PHC channel in PHC slot 7 in sum channel numbers for slot 7 is 08 to Of (table 6.2). From table 6.3 we can locate 08 to Of are in first line and are allocated. Channel 09 has fc against it and hence it is allocated.

6.3. PROCEDURE TO SEE NUMBER OF FREE PHC CHANNEL AVAILABLE FOR C.85

CHAOS:5E>m ↵

### WELCOME TO DD, MDEBUG & RETEST ### Type HE for MDEB & HELP for DD help.

MDEB 5e>def free md @ int_free_trm l + 10 ↵ Logical symbol FREE defined. MDEB 5e> free ↵

005EEA30 02 00 00 00 00 00 09 00 00 14 00 00 00 00 00 81 ………..

MDEB5e > ex ↵ CHAOS5e> ex ↵

Table 6.4

SIGNALING UNIT MODULE (CCS7 MODULE)


Note: After typing free ↵ on MDEB prompt, response will be as given in table 6.4. First column has address 2nd column has value 02 which indicates that no. of free PHC channels available for C.85 link is 2.

6.4. PROCEDURE TO SEE NUMBER OF FREE PHC CHANNEL AVAILABLE FOR #7 IN FREE POOL

(not allocated at present) CHAOS:5E>m ↵ ### WELCOME TO DD, MDEBUG & RETEST ### Type HE for MDEB & HELP for DD help MDEB 5e> def n7 md @no7_free_trm l+10 ↵ Logical symbol N7 redefined. MDEB 5e>n7 ↵

005EF6EE 06 00 B0 00 40 00 00 00 00 00 00 00 00 00 00 00 ..0.@…


Table 6.5

Note :

On typing n7↵ on MDEB prompt, response will be as given in table 6.5. First column has address. 2nd column has value 06, which indicates that no. of free phc channels for no.7 links is 6.

6.5. PROCEDURE TO SEE HOME ACTIVE CHANNEL (C.85) FOR HOME BM

Press Control D CHAOS : 5e>m ↵ ### WELCOME TO DD, MDEBUG & RETEST ### Type HE for MDEB & HELP for DD help

MDEB 5e> def hc md @ home_i_channel l + 10 ↵ Logical symbol HC defined. MDEB5e> hc ↵

005F09F2 09 00 08 00 00 00 00 00 00 00 00 00 00 00 00 00 ……….


Table 6.6

Note : In this channel 09 is used for SUM to Home BM ETE.

Chapter 6.

50 C-DOT DSS MAX

6.6. PROCEDURE TO SEE STANDBY CHANNEL (C.85) FOR HOME BM

Press control D CHAOS : 5E>m ↵

### WELCOME TO DD, MDEBUG & RETEST ### Type HE for MDEB & HELP for DD help MDEB 5e> def sb md @sby_i_channel l+10 Logical symbol SB defined. MDEB 5e>sb ↵

005FBACF 7D 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 }……..


Table 6.7

Note :

Standby phc channel for communication on C.85 link with home BM is 7d as in 2nd column of table above (6.7).

51 C-DOT DSS MAX

Chapter 7.

V5.X Unit

7.1. INTRODUCTION

The VU BP cable details are given in Figure 2.3. Set the baud rate for 9600 and connect BP cable to SLOT No.5 connector A tab 2 position of VU frame (same as in case of SUM).

7.1.1. Procedure to See the ETE of VU with Home BM

Press control D PERIOS 91_CC_0 > ↵ PERIOS 91_CC_0 > m ↵ ### WELCOME TO DD, MDEBUG & RETSET ### ….Type HE for MDEB & HELP for DD help. MDVU 91 > def et ete 166 s ↵ Logical symbol ET defined MDVU 91 >et ↵

ENDNO STATUS EDTMR RCR TMR TOC REJ INI ETR EOF

166 1 28 N N N N N N Y

Table 7.1

Note: If there is ETE between BP and VU then all fields will be N except EOF as shown above in table 7.1 .

Chapter 7.

52 C-DOT DSS MAX

PHC card slot and corresponding channel numbers in hex are indicated in table 7.2 below

PHC-CARD (Slot No.) Channel No.

7 08 to 0f

8 18 to 1f

9 28 to 2f

10 38 to 3f

11 48 to 4f

12 58 to 5f

13 68 to 6f

14 78 to 7f

Table 7.2

7.2. PROCEDURE TO SEE THE TERMINAL TABLE OF VU

Press control D PERIOS 91_CC_0 > m ↵ ### WELCOME TO DD, MDEBUG & RETSET ### ….Type HE for MDEB & HELP for DD help MDVU 91 > def tt md @ terminal_table l+80 ↵ Logical symbol TT defined

MDVU 91 >TT ↵ 0061620E 09 FC 08 FD 0A FD 0B FD 0C FC 0D FC 0E FD 0F FD 0061621E FF FE FF FE FF FE FF FE FF FE FF FE FF FE FF FE 0061622E FF FE FF FE FF FE FF FE FF FE FF FE FF FE FF FE 0061623E FF FE FF FE FF FE FF FE FF FE FF FE FF FE FF FE 0061624E FF FE FF FE FF FE FF FE FF FE FF FE FF FE FF FE 0061625E FF FE FF FE FF FE FF FE FF FE FF FE FF FE FF FE 0061626E FF FE FF FE FF FE FF FE FF FE FF FE FF FE FF FE 0061627E FF FE FF FE FF FE FF FE FF FE FF FE FF FE FF FE

Table 7.3

The above table shows allocation of PHC channels. From this table 7.3 we can determine how many PHC channels are being used.

V5.X UNIT


MDVU 91 > ex ↵

PERIOS 91_CC_0 > ex ↵

Status is represented as follows

FC USED

FD FREE

Ex. To know status of PHC channel in PHC slot 7 in VU channel numbers for slot 7 is 08 to 0F (table 7.2). From table 7.3 we can locate 08 to 0F are in first line and are allocated.

Channel 09 has FC against it and hence it is allocated.

7.3. PROCEDURE TO SEE NUMBER OF FREE PHC CHANNEL AVAILABLE FOR C.85

Press control D PERIOS 91_CC_0 > m ### WELCOME TO DD, MDEBUG & RETSET ### ….Type HE for MDEB & HELP for DD help MDVU 91 > def free md @int_free_trm l+1 ↵ Logical symbol FREE defined. MDVU 91 > free ↵

00615ADE 02

MDVU 91 > ex ↵


Note :

After typing free on MDVU prompt, response will show the decimal value, i.e., 02 which indicates that no. of free PHC available for C.85 link is 2

7.4. PROCEDURE TO SEE NUMBER OF FREE PHC CHANNELS AVAILABLE FOR V5.2 IN FREE POOL

Press control D PERIOS 91_CC_0 > m ↵ ### WELCOME TO DD, MDEBUG & RETSET ### ….Type HE for MDEB & HELP for DD help MDVU 91 > def v5 md @v5_free_trm l+1 ↵ Logical symbol V5 defined. MDVU 91 >v5 ↵

0061A924 03

Chapter 7.

54 C-DOT DSS MAX

MDVU 91 > ex ↵


Note :

On typing V5 on MDVU prompt, response will show the decimal value, i.e., 03 which indicates that no. of free PHC channels available for V5.2 in free pool is 3.

7.5. PROCEDURE TO SEE HOME ACTIVE CHANNELS (C.85) FOR HOME BM

Press control D PERIOS 91_CC_0 > m ↵ ### WELCOME TO DD, MDEBUG & RETSET ### ….Type HE for MDEB & HELP for DD help MDVU 91 > def hc md @home_i_channel l+1 ↵ Logical symbol HC defined. MDVU 91 >hc ↵

006161F3 09

MDVU 91 > ex ↵


Note :

In this, channel 09 is used as active C.85 channel.

7.6. PROCEDURE TO SEE STANDBY CHANNEL (C.85) FOR HOME BM

Press control D PERIOS 91_CC_0 > m ↵ ### WELCOME TO DD, MDEBUG & RETSET ### ….Type HE for MDEB & HELP for DD help MDVU 91 > def sb md @sby_i_channel l+1 ↵ Logical symbol SB defined. MDVU 91 >sb ↵

0061A937 0D

MDVU 91 > ex ↵


Note :

In this, channel 0D is used as standby C.85 channel.

V5.X UNIT


7.7. PROCEDURE TO SEE STATUS OF VU ON BP-TERMINAL

After connecting BP-cable to the proper position on BM, on MDEB, we define the following string

MDEBXX > def stat md @mbc_bm_unit+CC l+4 ↵

00CC32C2 02 04 02 02

The first 02 stands for VU-0 copy and 04 stands for VU-1 copy.

Similarly the next two 02s stand for VMU-0 and VMU-1 respectively.

MDEBXX> ex ↵

MDEBXX> ex ↵


Chapter 8.

Input Output Module (IOP)

8.1. INTRODUCTION

In this chapter, following are discussed. • Procedure to use sbyupd utility to change switch unit status in IOP • Procedure to derive address for required symbols from IOP for BP terminal

operations

8.2. SBYUPD UTILITY

Some time module under initialisation (say BM) may not come up because down loading path is not available through healthy switch units. For example, when BM is down, BM may not come up because TSC-0 is in oos-opr status and TSC-1 path may not be ok. In such situations, it is required to correct the status of TSC. We may correct status of switch units as TSC-0 as ins-act and TSC-1 as ins-sby. After correcting the status of switch units, AM and concerned module is to be initialised to part-init or above.

PROCEDURE TO USE SBYUPD UTILITY

Utility is menu driven and all switch unit identities are to be entered in Hexadecimal. Switch unit ids in Hex may be derived from table 1.1. Before invoking utility note down total no. of switch units and their ids in HEX whose status is to be corrected. Unit status available in file apunit.bin is to be edited by choosing respective module.

Ex : BM-01 is under initialisation and not recovering. On seeing displ-sys-all in growth mode in active IOP, TSC-0 is in oos-opr and TSC-1 is ins-act. Now, there may be problem in TSC-1 and system is not able to select TSC-0 path because TSC-0 is oos-opr. Now it is desirable to correct TSC-0, TSC-1 status as ins-act, ins-sby respectively, so that system can recover from alternate path. Now switch off both BPU power supplies of BM-01. If IOPs are in duplex bring stand by IOP to warm start and then active IOP to warm start. Edit the switch unit status of TSC-0, TSC-1 in last active IOP (now in warm start) using sby upd utility as follows :

Iop 5x > cd $ PRCDATAP ↵ Iop 5x > pwd ↵

INPUT OUTPUT MODULE (IOP)


/data / exdata / prcdata iop5x > sbyupd ↵

Welcome to RETROFIT UNIT STATUS MANAGEMENT SYSTEM

Input file name of unit status : apunit.bin ↵ What LINK – SBM/MBM (S/M) : m ↵ Module to be updated / viewed (CAM/IOM/BM-01 to BM-32/CM/SUM/ALL) : BM-01 ↵

MAIN MENU

Select your option

1. View default units

2. Update default units

3. View certain unit status data

4. Update certain unit status data

5. Do updations for some other module

6. Quit (without write)

7. exit

Option : 4 ↵

How many units to be updated : 2 ↵

INPUT UNIT TO BE UPDATED : value in hex eg. 96,9e,9f etc. : 9e ↵ INPUT STATUS TO BE UPDATED : (eg. 2, 9a) : 02 ↵ INPUT UNIT TO BE UPDATED : 9f ↵ INPUT STATUS TO BE UPDATED (eg. 2, 9a) : 04 ↵

Note :

Now main menu appears and choose exit option from main menu.

Option : 7 ↵ Iop5x> crp ↵

Now change iop mode from online to growth mode. With displ-sys-all command for BM-01 we can see that TSC-0 is ins-act and TSC-1 as ins-sby. Now IOP has proper status and go back to on line mode. Now AM is to be initialized to part init from AP terminal connected to APU. If AP terminal is not available give reset to both copies of AP. Now system will be down & MLF appears on ADP. Last active IOP where unit status is corrected can be brought ins-act by command init-iop : 5,1; ↵

Chapter 8.

58 C-DOT DSS MAX

Now IOP will become active, AM goes for part init or code load (if reset given to both APs), all BMs go for stable clear & system recovers. Switch on the BM-01 and BM-01, should come up after code load.

Note :

This procedure involves down time and may be carried out during slack hours.

8.3. PROCEDURE TO DERIVE ADDRESS FOR REQUIRED SYMBOL FROM IOP TERMINAL FOR USE WITH BP TERMINAL

Procedure to derive address for required symbol for MBM 2_2_1_6 link is given below.

Address can be obtained from different files in directory / code / abpexe for different module as given below. Response for grep command will give the address. Please note that address can be different with different software releases whereas symbols remain same. It is advisable to derive address from IOP and use it.

For AP/SSC Iop5x > grep mrp_m_ro / code / abpexe / napxxxsys.map ↵ mrp_m_ro 0 x 368694 - For AP Note : Address for symbol mrp_m_ro is 368694 for AP IOP5x> grep mrp_m_ro / code / abpexe / sscxxxsys.map ↵ mrp_m_ro 0 x 307a78 - For SSC Note : Address for symbol mrp_m_ro is 307a78 for SSC. iop5x > grep mcm_usmap / code / abpexe / sscxxxsys.map ↵ mcm_usmap 0 x 46a980 – For im iop5x >grep mcm_clk_status /code/apexe/sscxxxsys.map ↵ mcm_clk_status ox46970a

For BM (colocated/RBM) Iop5x > grep mbc_bm_unit /code/abpexe/nbpxxxsys.map mbc_bm_unit oxcc3202 iop5X> grep mrp_m_ro / code / abpexe / nbpxxxsys.map mrp_m_ro o x 5b1542 iop5x> grep mda_print_flag / code / abpexe/nbpxxxsys.map mda_print_flag 0 x cc6fa4

For RBM

iop5x> grep mbc_dtk_link_sta / code / abpexe / nbpxxxsys.map mbc_dtk_link_sta 0 x cc3086

INPUT OUTPUT MODULE (IOP)


iop5x> grep mpi_bm_mode / code / abpexe/nbpxxxsys.map mpi_bm_mode 0 xcbc6ce

For SUM Iop5x> grep nrwdatabase / code / abpexe / nnpxxxsys.map nrwdatabase 0 x 5ec5da Iop5x> grep terminal _ table / code / abpexe / nnpxxxsys.map Terminal_table 0 x 5f500e Iop5x > grep int_free_trm / code /abpexe/nnpxxxsys.map Int_free_trm 0 x 5eea30 Iop5x>grep no7_free_trm /code/abpexe/nnpxxxsys.map No7_free_trm 0 x 5ef6ee Iop5x> grep home_i_channel /code/abpexe/nnpxxxsys.map Home_i_channel 0 x 5f09f2

Iop5x> grep sby_i_channel / code / abpexe/nnpxxxsys.map Sby_i_channel 0 x 5fbacf

For VU

IOP5x>grep terminal_table /code/abpexe/nvpxxxsys.map terminal_table 0x61620e

IOP5x>grep int_free_trm /code/abpexe/nvpxxxsys.map int_free_terminal 0x615ade

IOP5x>grep v5_free_trm /code/abpexe/nvpxxxsys.map v5_free_trm 0x61a924

IOP5x>grep home_i_channel /code/abpexe/nvpxxxsys.map home_i_channel 0x6161f3

IOP5x>grep sys_i_channel /code/abpexe/nvpxxxsys.map sys_i_channel 0x61a937


Chapter 9.

Health Log & Field Debugging Tool

9.1. PROCESSING HEAL LOG FILES

Note :

Processing of Health log is not required during normal maintenance schedule. It can be done only in consultation with C-DOT.

Heal log’s are health log reports of BM, this can be enabled by modifying system-parameter “HEAL-LOG-ENBL” to 255 by CRP command. This parameter can be disabled by modifying HEAL-LOG-ENBL to “0”, it is common for all BMs. SUM heal logs are always enabled.

System generates heal log’s for all BM’s in separate file. These files are available in IOP in $FDTDIR directory in healXXmmdd.format Where XX = BM_ID For SUM it is 2f mm = current month dd = current date

Procedure to see recoveries through crp using heal log • System parameter 'Heal-log-enable' should be modified to .255 • IOP5X> cd $FDTDIR

IOP5X>ls - ls heal*

Module File Name

AM heal2bddmm

SUM heal2fddmm

BM healXXddmm (where XX is logical BM No.)

CM heal32ddmm • IOP 5X> cd $FDTDIR

IOP5X> hlpp -P <heal file Name>

eg. hlpp .P heal2f2110 (for heal log of SUM of 21-10-02)

HEALTH LOG & FIELD DEBUGGING TOOL


Choose option for 'Process Recovery' using J&K keys and press '+' to highlight and 'X' to exit. To select all press 'a' and 'x'.

• An o/p file healxxddmm.rep will be generated. This file can be paged to check for recoveries type.

• To enable heal log for CM, do following:

MDEB64>exm.b 2e2a56

Modify from 00 to ff.

Note : Address of heal_log_enable can be taken using "sy heal_log_enable" on mdeb_64> prompt.

9.2. PROCEDURE TO START AND PROCESS FDT

FDT is FIELD DEBUGGING TOOL this is used to find out the reasons for recoveries and other failures.

Note : FDT is used for specific problems only and is not required during normal maintenance.

1. Copy of the required FDT file in $FDTDIR directory

2. Compile the file “fdtl file_name” this generates object file filename.O

3. If there is no compilation error proceed further

4. From IOP terminal go to CONP

Ex : iop5C > fdtl filename ↵ Iop5c > filename.O ↵

9.3. PROCEDURE TO START FDT & VIEW FDT STATUS

IOP5X> cd $FDTDIR IOP5X> pwd /u/fdt/test Copy fdt script file (say abc.fdt) in this directory. Compile fdt script file 'abc.fdt' by giving IOP5X>fdtl abc IOP5X. conp CONP> fdt xx (when xx is BP ID of module) FDT XX> start abc Give 'user name'. Password is default. Now 'fdt' will be started on the module xx. FDT xx> exit (To come out of FDT prompt to IOP5X>). Once observation is taken for required period, one has to stop the fdt session. Go to FDT xx> prompt again

Chapter 9.

62 C-DOT DSS MAX

FDT xx> quit (To quit FDT session) Output of 'FDT' will be available in abc.log file, same has to be post processed by giving IOP5X>pp -P abc

Output of this post processing will be stored in abc.pri, which can be paged using 'pg' or 'cat'.

In between, if one wants to check whether 'FDT' session is running or not, give following command

IOP5X> conp CONP> fdt xx FDT xx> ses This will show the name of the 'FDT' script file running at that time.

9.4. PROCEDURE TO COPY FILES FROM BMDC/ED/BD

Many a times fresh files are required to be copied from BMDC or old files to be restored from ED/BD

Suppose apgpa.dat, apgpa.idx, apgpa.lok files are to be copied from BMDC to Disk in $GLBDATAP.

IOP5X>cd $GLBDATAP IOP5X>cp apgpa* /u/admn IOP5X>rm apgpa* IOP5X> cd / Now Insert 'BMDC' cartridge IOP5X>cpio -icvdu *apgpa* <$TAPE

It must show 3 files (apgpa.dat, apgpa.idx and apgpa.lok) and then total Block size of BMDC

IOP5X>cd $GLBDATAP IOP5X>ls -ls apgpa* (To verify the files)

9.5. PROCEDURE TO INSTALL & CHECK PPL

9.5.1. Procedure to Install PPL

Copy PPL files in $HPCHP directory

IOP5X>cd $HPCHP IOP5X>pwd /to verify/ It shows /code/wpch Insert 'PPL' cartridge in IOP. IOP5X>cpio -icv <$TAPE IOP5X>ls -ls



It shows files 'say' hmplatf, pmplatf & its log file (say mbm_altf.log) Now go to crp & give following command <instl-ppl [PCH-LNK] = < > [PM-NO] = < > [BM-NO] = < >

and execute to remove all the previous existing PPL (if installed) Again give the command [PCH-LNK] = altf [PM-NO] = < > [BM-NO] = < > and execute

Keep giving return to come out to crp prompt,

Caution : In case any BM is down (OOS-INI), then in parameter [BM-NO], write exact BM Nos e.g. 1&2&3.... etc skipping the 'OOS-INI' BM No.

9.5.2. Procedure to Check Proper Installation of the Patch

Procedure - 1

IOP5X>cd $PRCDATAP IOP5X>od -cx pplf or IOP5X>od -bc pplf

This will show PPL name (e.g. altf in above case) in the first line. This will confirm that ppl altf has been installed.

Procedure - 2

For this procedure, 'ppl' log files must be available in the 'ppl' cartridge

i) IOP5X>cd $HPCHP IOP5X>vi mbm_altf.log Following are the contents: Patch : mst : file=vpc1pcs_sto7_chk_pndng_msg.c Maptable=cpmap *********MESSAGE********

Function : clp_sto7ckk_pndng_msg Process : vp Old address : 0x48ad50 New address: 0x7a1802 Map_table_index:164 Map_table_address:4638bc

Note down value of index, New address & Maptable (say cpmap).

Chapter 9.

64 C-DOT DSS MAX

ii) On 'BP' terminal, give following:

MDEB>md @cpmap+4*(Index Value) eg. in above case, give: MDEB> md @cpmap+4*164

In the memory dump, compare 1st sixe bytes, which should match with the value of new address. Otherwise the 'ppl' has not been installed properly.

9.6. PROCEDURE FOR TRANSFERING FILES FROM IOP TO PC AND VICE-VERSA

Introduction: There are two utilities namely 'rz' and 'sz' present in directory $TOOLP which are used to transfer the files from IOP to PC/LAPTOP and vice-versa.

1. 'rz' is the utility to transfer the file from PC/Laptop to IOP

2. 'sz' is the utility to transfer the file from IOP to PC/Laptop.

PROCEDURE : For using the 'rz' and 'sz' utilities follow the procedure given below. • Copy the 'rz' and 'sz' utilities in $TOOLP directory in IOP. • Connect the com port (say com2) of PC/Laptop to ASIO port of IOP using RS-

232 cable having female connector on both side. • Go to Hyperterminal option on the PC/Laptop available in Accessories. • In the top menu of Hyperterminal, click on 'file' and select the 'properties' to

change the setting of Hyperterminal. Select Port as 'COM2' and click on 'configure'. In the port setting of 'COM2' give the following values for the given parameters

(a) Bits per second = 9600

(b) Data bits = 8

(c) Parity = None

(d) Flow control = None

Click 'OK' after setting all these parameter. Now click 'Setting' and select 'Emulation' as 'VT100' and click 'OK'.

• After connecting the cable and changing the setting the above setting login prompt will be obtained on the Hyperterminal.

• Login as 'admn' and password as 'CDOTadmn' • The file from IOP to PC/LAPTOP can be transferred by using the 'sz' utility.

For this run the following command at IOP prompt:



IOP5x> sz filename

This will transfer the file from IOP to Hyperterminal(PC/Laptop). • The file from PC/LAPTOP to IOP can be transferred by using the 'rz' utility.

For this run the following command at IOP prompt:

IOP5x> rz

In the top menu of Hyperterminal, click on 'transfer' and select the 'send file'. A browser window will get opened. Select the Protocol as 'Z modem' and the file name to be transferred to IOP.

Cable Preparation

1. RS-232 cable having female connectors on both sides should be used.

2. Pin connection for cable should be 2-3, 3-2, 5-5.

3. Pin no 1-4-6 should be shorted both sides.


Annexure I

Symbols and Addresses for Various Function

Module Function Symbol 2_1_1_1 2_2_1_3 2_2_1_4 2_2_1_6

AP SRF Counter mrp_m_ro+600 348bb2 368c94 398c94 368c94

SRF Counter mrp_m_ro+600 2e8040 308078 308078 308078

Status Map mcm_usmap 44ee0c 46f5b4 46a980 46a980

CM

External Clk Sts. mcm_clk_status 44dcb8 46e33e 46970a 46970a

Status Map mbc_bm_unit 9ec332 ca2948 ca2d58 cc3202

SRF Counter mrp_m_ro+600 4ad260 591928 591928 5b1b42

DGN Print mda_print_flag 9ed228 ca66de ca6aee cc6fa4

DTK Status mbc_dtk_link-st 9ec192 ca27cc ca2bdc cc3086

BM/RBM

RBMSA Mode mpi_bm_mode 9e0422 c9be14 c9c224 cbc6ce

BM ETE Status nrwdatabase 5c64b0 5cc51a 5ec5da 5ec5da

PHC Trml Alloc. terminal_table 5cf840 5d4f4e 5f500e 5f500e

Free C.85 Trml int_free_trm 5c882e 5ce970 5eea30 5eea30

Free Trml no7_free_trm 5c8ef8 5cf62e 5ef6ee 5ef6ee

Home Act C.85 home_i_channel 5c9410 5d0932 5f09f2 5f09f2

Home Sby C.85 sby_i_channel 5d40f4 5dba0f 5fbacf 5fbacf

SUM

Status Map mpi_unit_stat_m 0204a4 023cee 023cee 023cee

PHC Trml Alloc. terminal_table - 5f84ba 5f851e 61620e

Free C.85 Trml int_free_trm - 5f7d8a 5f7dee 615ade

Free Trml v5_free_trm - 5f842e 5fcc34 61a924

Home Act C.85 home_i_channel - 5f849f 5f8503 6161f3

VU

Home Sby C.85 sby_i_channel - 5fcbe3 5fcc47 61a937

Note: The addresses for the various mrp_m_ro (SRF Addresses) here given after adding 600 (in HEX) to the addressed value.

Base Processor Terminal Commands

Documents

Transcript of Base Processor Terminal Commands