seamewe-3 sc’s guide · web viewthis line is automatically shown if there are alarms on the adm....

SEAMEWE-3 SC’s GUIDE

(FINAL)

(Don’t leave office/station without it)

Updated by SEAMEWE-3 ORLO Dated May 2008

Content Page

Section Title Page Remarks1 Terms Of Reference for STEP

COORDINATOR(SC)2

2 STEP Coordinators (SC) appointed by SEAMEWE-3 RC

3-11

3 Non-Terminal Parties and Facility Providers(Involved RCOs)

12

4 SEAMEWE-3 Restoration Implementation Procedure

12-14

5 SEAMEWE-3 Restoration Forms 15-266 SEAMEWE-3 RET Form 27-287 SEAMEWE-3 SC’s Guide to troubleshooting

restoration paths29-30

8 PROCEDURE: “Manually Release SNCP switch”

31-33

9 History of main problems, solutions and feedback gathered

34-35

of 38document.doc

1. Terms Of Reference for STEP COORDINATOR(SC)

Upon receipt of the ‘Go-Ahead Order To Implement Restoration’ (i.e. Form 1) from the SMW-3 NOC to all affected SCs and facility providers, the SC shall assume responsibility of their nominated steps and log into Conference Bridge at Tel: (65) 6 668 7200, Code: 111489#.

The SC should remain on the Conference Bridge providing regular updates and co-ordinating the involved parties, until all their steps are restored. If necessary, the SC may contact external facility providers or other SCs outside of the Conference Bridge to further investigate any problem. A general guide to facilitate the investigation is provided as in Section 7.

SMW-3 NOC shall use the Conference Bridge to receive updates from the SC(s) and assume overall control as and when required. There is no concrete evidence correlating STEP and restore speed. A timeline of 10 mins is recommended to trouble-shoot a problematic STEP, before moving on to the next problematic STEP, and return to attend it later. This is to avoid staying too long in one problematic STEP, and not able to provide the needed assistance to the other STEPs.

SC shall follow the reporting procedure of STEPS restored using the Restoration Forms which are agreed by the RC as in Section 5.

Note: In RET case, SCs, of course, do not require SMW-3 NOC to inform them of SNCP switching. SC shall be responsible to collect the BER & RTD test results and ODF termination checks of involved stations. IF BER is bad, SC shall liaise with providers to troubleshoot. SC shall then complete the RET Form as in Section 6, and submit to ORLO office.

of 38document.doc

2. STEP Coordinators (SC) appointed by SEAMEWE-3 RC(Please refer to the latest URM Plans as in the website for the final appointment of SC, and subsequent updates)

SMW-3SEG.

(Path No.) Path SC ContactablePersonnel/RCO

ContactNo.(24Hrs)(O) – Office(F) – Fax

S1 P1P1,P15P3P6

OKIW-SHTOOKIW-TUASOKIW-SHGAHGKG-OKIW

KDDI RCO:Tokyo ITMCDuty Engr.

81-3-3347-5715(O)81-3-3347-5720(F)

P9P10

HGKG-KEOJKEOJ-SHTO

KT RCO:Seoul/K ITMC Duty Engr.

82-2-725-4221(O)82-2-725-4222(O)82-2-725-4224(F)

P11 SHGA-SHTO CT Chongming C/SDuty Staff

86-215-9470054(O)86-215-9471231(O)86-215-9470047(F)

P12P13P7

SHTO-TCHGFSHN-SHTOTCHG-SHGA

CHT Toucheng C/S Duty Staff

886-3-977-2252(O)886-3-977-2294(F)

P14 HGKG-SHTO SINGTEL ORCO: SMW-3 NOC Duty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P78 FSHN-HGKG CHT Fangshan C/S Duty Staff

886-8-876-1494(O)886-8-876-1386(F)

S2 P14P15,P37P15

HGKG-SHTOSATN-SHTOSHTO-TUAS

SINGTEL ORCO: SMW-3 NOC Duty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P1 ,P15 OKIW-TUAS KDDI RCO:Tokyo ITMCDuty Engr.

81-3-3347-5715(O)81-3-3347-5720(F)

P15,P36 PENG-SHTO SINGTEL ORCO: SMW-3 NOC Duty StaffPenang C/SDuty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)604-579-1104(O)604-579-1101(O)604-579-1533(F)

P16 DANG-SHTO VTI Danang ITMCDuty Staff

84-511-850006(O)84-511-895489(O)84-511-850048(F)

P17 SHTO-TAIP CT Shantou C/SDuty Staff

86-754-7870035(O)86-754-7870034(F)

P18P14,P18

BTGA-SHTOBTGA-HGKG

PLDT Batangas C/S Duty Staff

63-2-732-6704(O)63-2-732-6705(O)63-2-732-6706(O)63-2-732-6709(F)

P19 SHTO-TUGK JTB Tungku C/SDuty Staff

673-2-228-628(O)673-2-228-629(F)

P21 MERS-SHTO TM RCO:Int’l NETCAREDuty Staff

603-2020-5412(O)603-2020-5413(O)603-2020-5414(O)603-2020-5415(O)

of 38document.doc

603-2020-1024(F)P23P23, P33

HGKG-TUASHGKG-MBAI


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P24P25

DANG-TUASTAIP-TUAS


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P26 BTGA-TUAS PLDT Batangas C/S Duty Staff

63-2-732-6704(O)63-2-732-6705(O)63-2-732-6706(O)63-2-732-6709(F)

P27 TUGK-TUAS SINGTEL ORCO: SMW-3 NOC Duty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P29 MERS-TUAS TM RCO:Int’l NETCAREDuty Staff

603-2020-5412(O)603-2020-5413(O)603-2020-5414(O)603-2020-5415(O)603-2020-1024(F)

P79 DANG-HGKG VTI Danang ITMCDuty Staff

84-511-850006(O)84-511-895489(O)84-511-850048(F)

S3 P30 JKTA-TUAS INDOSAT Ancol C/SDuty Staff

62-21-692-3756(O)62-21-381-0872(O)62-21-692-8383(F)

P31 PERT-TUAS REACH (GNL)

RCO: Melbourne GOC

61-3-8549-0294(O)61-3-9543-9642(F)

P32 JKTA-PERT REACH (GNL)

RCO: Melbourne GOC

61-3-8549-0294(O)61-3-9543-9642(F)

S4 P84P84, P73

P86

PENM-TUASNDEN-TUAS

GOON-TUAS


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P33P33,47P33, 23

MBAI-TUASFUJA-TUASHGKG-MBAI


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P34 MTLA-TUAS SINGTEL ORCO: SMW-3 NOC Duty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

of 38document.doc

P35 COCH-TUAS VSNL Mumbai Cable Station

00-91-22-66592398(Tel)00-91-22-66592399(Fax)

Cochin Cable Station

00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P36P15,36

PENG-TUASPENG-SHTO

TM Penang C/SDuty Staff

604-579-1104(O)604-579-1101(O)604-579-1533(F)

P37P37,15

SATN-TUASSATN-SHTO


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P39 (indirect P33 +45)

MEDN-TUAS SINGTEL ORCO: SMW-3 NOC Duty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P40P40,46,58,64

MBAI-MTLAMTLA-MZRA

SLT Mt. Lavinia C/S Duty Staff

94-1-717674(O)94-1-717676(F)

P40, 88 MTLA-PENM FT RCO: Paris INOC Duty Staff

33-1-4993-8574(O)33-1-4993-7800(F)

P41 COCH-MBAICOCH- ALEX

VSNL Mumbai Cable Station

00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P41,P46,P58,P64

COCH-MZRA SINGTEL ORCO: SMW-3 NOC Duty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P41, 90 COCH-MZRA SINGTEL ORCO: SMW-3 NOC Duty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P42 MBAI-PENG VSNL Mumbai Cable Station

00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P43 MBAI-SATN VSNL Mumbai Cable Station

00-91-22-66592398(Tel)00-91-22-66592399(Fax)

Cochin Cable 00-91-484-

of 38document.doc

Station 659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P33,46,58,64

MZRA-TUAS SINGTEL ORCO: SMW-3 NOC Duty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P81 COCH-MTLA VSNL Mumbai Cable Station

00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

S5 P84P84, 73

P86

PENM-TUASNDEN-TUAS

GOON-TUAS


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P33,47P41,P90P41,46,58,64

FUJA-TUASCOCH-MZRACOCH-MZRA


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P40,46,58,64 MTLA-MZRA SLT Mt. Lavinia C/S Duty Staff

94-1-717674(O)94-1-717676(F)

P85 MBAI-SBRA VSNL Mumbai Cable Station

00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P88 MBAI-PENM VSNL Mumbai Cable Station

00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P89 MBAI-GOON VSNL Mumbai Cable Station

00-91-22-66592398(Tel)00-91-22-66592399(Fax)


of 38document.doc

Station 659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P90 MBAI-MZRA VSNL Mumbai Cable Station

00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P47 FUJA-MBAI ETISALAT RCO: Mumbai ITMC Duty Staff

91-22-2667998(O)91-22-2695537(O)91-22-2667999(F)91-22-2695532(F)

P53,58,60,71,72

GOON-KCHI BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)

P101 FUJA-GOON BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)

P40,88 MTLA-PENM FT RCO: Paris INOC Duty Staff

33-1-4993-8574(O)33-1-4993-7800(F)

P93 ALEX-FUJA ETISALAT Fujairah C/SDuty Staff

971-9-2222-995(O)971-9-2226-201(F)

P91 JEDD-MBAI STC Jeddah C/S Duty Staff

966-2-648-5248(O)966-2-649-3706(F)

P92P41 ,92

ALEX-MBAIALEX-COCH

T. EGYPT Alexandria C/S Duty Staff

20-34-910-605(O)20-34-947-2222(F)

P94 ALEX-KCHI PTCLP50 MBAI-MASQ VSNL Mumbai

Cable Station 00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P54 DJIB-MASQ ETISALAT RCO: Mumbai ITMC Duty Staff

91-22-2667998(O)91-22-2695537(O)91-22-2667999(F)91-22-2695532(F)

P51 FUJA-KCHI PTCLP49 KCHI-MBAI PTCLP46 DJIB-MBAI VSNL Mumbai

Cable Station 00-91-22-66592398(Tel)00-91-22-66592399(Fax)

of 38document.doc


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P48 DJIB-FUJA ETISALAT RCO: Mumbai ITMC Duty Staff

91-22-2667998(O)91-22-2695537(O)91-22-2667999(F)91-22-2695532(F)

P100 KCHI-JEDD PTCLP33,46,58,64P72,84P15,72,84

MZRA-TUAS

GOON-TUASGOON-SHTO


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P64, 93 FUJA-MZRA T.Italia(Sparkle TIS)

RCO:Palermo/L*IINOC Duty Staff

39-091-378-000(O)39-091-378-319(F)

S6 P84P84, 73

P86

PENM-TUASNDEN-TUAS

GOON-TUAS


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P41,46,58,64P41,90

COCH-MZRA

COCH-MZRA


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P56 DJIB-JEDD STC Jeddah C/S Duty Staff

966-2-648-5248(O)966-2-649-3706(F)

P40,46,58,64 MTLA-MZRA SLT Mt. Lavinia C/S Duty Staff

94-1-717674(O)94-1-717676(F)


00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)


00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)


00-91-22-66592398(Tel)00-91-22-66592399(Fax)


of 38document.doc

Station 659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)


00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P57 JEDD-SUEZ STC Jeddah C/S Duty Staff

966-2-648-5248(O)966-2-649-3706(F)

P53,58,60,71,72


44-1691 666777(O)44-1691-658452(F)

P101P102

FUJA-GOONGOOD-JEDD

BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)


33-1-4993-8574(O)33-1-4993-7800(F)

P93 ALEX-FUJA ETISALAT Fujairah C/SDuty Staff

971-9-2222-995(O)971-9-2226-201(F)

P91 JEDD-MBAI STC Jeddah C/S Duty Staff

966-2-648-5248(O)966-2-649-3706(F)

P92P41 ,92

ALEX-MBAIALEX-COCH

T. EGYPT Alexandria C/S Duty Staff

20-34-910-605(O)20-34-947-2222(F)

P94 ALEX-KCHI PTCLP58 ALEX-DJIB T. EGYPT Alexandria

C/S Duty Staff20-34-910-605(O)20-34-947-2222(F)

P59 ALEX-JEDD T. EGYPT Alexandria C/S Duty Staff

20-34-910-605(O)20-34-947-2222(F)

P100 KCHI-JEDD PTCLP33,46,58,64P72,84P15,72,84

MZRA-TUAS

GOON-TUASGOON-SHTO


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P64, 93 FUJA-MZRA T.Italia(Sparkle TIS)

RCO:Palermo/L*IINOC Duty Staff

39-091-378-000(O)39-091-378-319(F)

S8 P84P84, 73

P86

PENM-TUASNDEN-TUAS

GOON-TUAS


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P60 ALEX-SBRA PTC RCO: Linda a Velha Duty Staff

351-214-147280(O)351-214-147281(O)351-214-141355(F)

of 38document.doc

351-214-146535(F)P40,46,58,64 MTLA-MZRA SLT Mt. Lavinia

C/S Duty Staff94-1-717674(O)94-1-717676(F)


00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P41,46,58,64P41,90

COCH-MZRA

COCH-MZRA


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)


00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

of 38document.doc


00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)


00-91-22-66592398(Tel)00-91-22-66592399(Fax)


00-91-484-659010(Tel)00-91-484-2421164(Fax)

VSNL RCO Team

00-91-22-66592279 (Tel)

P98 GOON-MZRA BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)

P53,58,60,71,72


44-1691 666777(O)44-1691-658452(F)

P101P102

FUJA-GOONGOON-JEDD


44-1691 666777(O)44-1691-658452(F)


33-1-4993-8574(O)33-1-4993-7800(F)

P61 ALEX-MARM TURK T. RCO: Istanbul ITMC Duty Staff

90-212-5209898(O)90-212-5122850(F)

P95 ALEX-PENM FT RCO: Paris INOC Duty Staff

33-1-4993-8574(O)33-1-4993-7800(F)

P96 ALEX-GOON BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)

P62 ALEX-CHNA T. EGYPT Alexandria C/S Duty Staff

20-34-910-605(O)20-34-947-2222(F)

P63 ALEX-YRKP CYTA RCO: CYTA ITMC

357-22-702778(O)357-22-515355(F)

P64(inclusive P66)

ALEX-MZRA T. ITALIA RCO: Palermo/L*I INOC Duty Staff

39-091-378-000(O)39-091-378-319(F)

P65 CHNA-MZRA T. ITALIA RCO: 39-091-378-000(O)

of 38document.doc

P59, 64 JEDD-MZRA Sparkle (TIS)

Palermo/L*I INOC Duty Staff

39-091-378-319(F)

P68 MZRA-SBRA T. ITALIA RCO: Palermo/L*I INOC Duty Staff

39-091-378-000(O)39-091-378-319(F)

P69,P69,71,73

MARM-SBRAMARM-NDEN

PTC RCO: Linda a Velha Duty Staff

351-214-147280(O)351-214-147281(O)351-214-141355(F)351-214-146535(F)

P70 SBRA-TETU PTC RCO: Linda a Velha Duty Staff

351-214-147280(O)351-214-147281(O)351-214-141355(F)351-214-146535(F)

P83 CHNA-YRKP CYTA RCO: CYTA ITMC

357-22-702778(O)357-22-515355(F)

P33,46,58,64P72,84P15,72,84

MZRA-TUAS

GOON-TUASGOON-SHTO


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P66,68,71,73

NDEN-YRKP(See Note 1)

CYTA &T-systems

RCO: CYTA ITMC

357-22-702778(O)357-22-515355(F)

Norden C/SDuty Staff

49-4931-92700(O)49-4931-927015(F)

P97P64,93

MZRA-PENMFUJA-MZRA

T.Italia Sparkle(TIS)

RCO: Palermo/L*I INOC Duty Staff

39-091-378-000(O)39-091-378-319(F)

S9 P84P84, 73

P86

PENM-TUASNDEN-TUAS

GOON-TUAS


65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P71 PENM-SBRA FT RCO: Paris INOC Duty Staff

33-1-4993-8574(O)33-1-4993-7800(F)

of 38document.doc

P89 MBAI-GOON BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)

P71, 72 GOON-SBRA BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)


44-1691 666777(O)44-1691-658452(F)

P53,58,60,71,72


44-1691 666777(O)44-1691-658452(F)

P101P102

FUJA-GOONGOON-JEDD


44-1691 666777(O)44-1691-658452(F)


33-1-4993-8574(O)33-1-4993-7800(F)

P66,68,71,73

NDEN-YRKP T-systems Norden C/SDuty Staff

49-4931-92700(O)49-4931-927015(F)

P95 ALEX-PENM FT RCO: Paris INOC Duty Staff

33-1-4993-8574(O)33-1-4993-7800(F)


44-1691 666777(O)44-1691-658452(F)

P97 MZRA-PENM T.Italia Sparkle(TIS)

RCO: Palermo/L*I INOC Duty Staff

39-091-378-000(O)39-091-378-319(F)

S10 P72 GOON-PENM BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)

P86 GOON-TUAS SINGTEL ORCO: SMW-3 NOC Duty Staff

65-6836-3079(O)65-6836-3080(O)65-6734-6903(F)

P73P69,71,73

NDEN-PENMMARM-NDEN

DTAG Norden C/SDuty Staff

49-4931-92700(O)49-4931-927015(F)

P75 OSTD-PENM BICS RCO: Belgacom ITMC Duty Staff

32-25-405-200(O)32-25-406-885(F)

P89 MBAI-GOON BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)

of 38document.doc

P71, 72 GOON-SBRA BT RCO: Oswestry NMC(BT/RCO)

44-1691 666777(O)44-1691-658452(F)


44-1691 666777(O)44-1691-658452(F)

P53,58,60,71,72


44-1691 666777(O)44-1691-658452(F)

P101P102

FUJA-GOONGOON-JEDD


44-1691 666777(O)44-1691-658452(F)

P66,68,71,73

NDEN-YRKP(See Note 1)

CYTA &T-systems

RCO: CYTA ITMC

357-22-702778(O)357-22-515355(F)

Norden C/SDuty Staff

49-4931-92700(O)49-4931-927015(F)


44-1691 666777(O)44-1691-658452(F)

Notes:-1. 2 Admins. will assume the role of SCs for different routes. For details, see URM plan.

of 38document.doc

3. Non-Terminal Parties and Facility Providers (Involved RCOs)

Admin Station Telephone FacsimileAT&T (for China US CN & Columbus III)

Conyers 1 770 785 3600 1 770 785 3649

TELEFONICA Alcobendas ITMC 34 916 579 988 34 916 615 369Estepona c/s 34 952 800 250 34 952 793 269Santander 34 942 205734 34 942 344578

SAT-3/WASC/SAFE Melkbosstrand c/s (ORCO)

27 21 553 2236 27 21 553 2463

ALETAR Alexandria C/S Duty Staff 20-34-910-605(O)20-34-947-2222(F)

UGARIT RCO: CYTA ITMC 357-22-702778(O)357-22-515355(F)

of 38document.doc

4. SEAMEWE-3 Restoration Implementation Procedure

of 38document.doc

of 38document.doc

5. SEAMEWE-3 Restoration Forms Form 0

SEAMEWE-3CABLE FAILURE/DEGRADATION ADVICE

To: SEAMEWE-3 ORLO (SingTel) Fax. +65-6738-5549ORCO (SingTel) Fax. +65-6734-6903

From: _______________________ Fax: ______________(Relevant Terminal Parties of SEAMEWE-3) Tel: _______________

Date: _______________________ Time(UTC): _________

1. The following traffic paths have failed/degraded on ___________ at

___________UTC. The suspected cause of the fault is

____________________________________________________________________

____________________________________________________________________

_____________________________________________________

Affected traffic paths:

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

_____________________________________________________

________________________________________________________

of 38document.doc

Form 1(1/3)SEAMEWE-3

GO-AHEAD ORDER TO IMPLEMENT RESTORATIONTo: SEAMEWE-3 Terminal Parties, STEP Co-ordinators(SCs) & Facility ProvidersCopy: SEAMEWE-3 Owners (For Info.)From: SEAMEWE-3 ORLO (SingTel) Fax. +65-6738-5549

ORCO (SingTel) Fax. +65-6734-6903

Date: _______________________ Time(UTC): _________

1. A fault has developed in the SEAMEWE-3 Cable System Segment _____ between

_________________________ and _____________ on ___________ at

___________UTC. Suspected cause: _____________________________________

____________________________________________________________________.

2. The following traffic paths have been affected (Path ID may be stated here for the initial

quick reporting. The details will be reported in Form 2):

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________

________________________________________________________3. Please go ahead to implement Restoration Plan Reference: SMW-3 (S_______) Issue

_______________________ and log into SMW-3 Conference Bridge at Tel: +65 6668 7200 , Code: 111489#. For this most updated plan, you may visit the SMW-3 NA’s website at http://www.smw3.com (User ID: smw3na; Password: singtel).

4. Upon successful restoration of the above affected traffic paths, ORCO will issue another order (FORM 2) if necessary to transfer remaining unaffected traffic paths to respective restoration steps to facilitate cable repair.(IMPORTANT: Please see next page for the quick CHECKLIST for SC during restoration implementation)

of 38document.doc

http://www.smw3.com/

Form 1(2/3) Quick CHECKLIST for SC during restoration implementation.

Have you done the following?

a. During restoration implementation:

- Implement the Restoration Plan based on above reference, and log into SMW-3 Conference Bridge at Tel: +(65) 6668 7200 , Code: 111489#.

- A copy of the SEAMEWE-3 SC’s Guide is now with you.

- Report to ORCO using FORM 3 concerning the successful restoration time of the above steps.

b. When the failure occurs, SNCP switched by NOC but restoration not working:

- Identify a “tracer” reference circuit inside the STEP if necessary

The “Tracer” reference circuit is____________________________ - Contact the relevant stations one by one to see if the path is correctly

connected.

- Make sure SNCP is correctly switched out by looking at cable station’s SH. Contact relevant stations, where necessary.

- If all above fails, then request one by one the stations to loop back andat each step, check with the NMS centre managing the “tracer” circuit whether AIS alarm is cleared. It is not necessary to call NOC.

Remember that at any point of disconnect, receive port will have LOS alarm, and generate AIS backwards to all stations which will receive the AIS alarm.

Don’ts

- When asking for Loopback, don’t use the words like “give me” a loopback. On the phone, “me” is often misunderstood, always identify the station, e.g. “give a loopback towards Shantou cable station”.

- Don’t call the NOC to check whether Alarm is cleared or not during the troubleshooting process. Use a local “tracer circuit” or else contact the centre managing the NMS of the controlling station at the far end terminals. If everyone calls the NOC to check if alarm is cleared or not, then the purpose of decentralizing the restoration is defeated.

of 38document.doc

Form 1(3/3)

of 38document.doc

SMW-3 Connectivity Diagram (Updated as of 16 May 2008)Source: SMW-3 NA's Website.

Form 1 (Example) SEAMEWE-3

GO-AHEAD ORDER TO IMPLEMENT RESTORATION

To: SEAMEWE-3 Terminal Parties, STEP Co-ordinators(SCs) & Facility Providers

Copy: SEAMEWE-3 Owners (For Info.)

From: SEAMEWE-3 ORLO (SingTel) Fax. +65-6738-5549ORCO (SingTel) Fax. +65-6734-6903

Date: 2 Jan 2002 Time(UTC):1600UTC

1. A fault has developed in the SEAMEWE-3 Cable System Segment S2 between

Shantou and Tuas on 2 Jan 02 at 1545UTC. Suspected cause: Cable cut. Still

investigating.

2. The following traffic paths have been affected(Path ID may be stated here for the initial

quick reporting. The details will be reported in Form 2):

P15-Shantou-Tuas, P14-Shantou-DWB(S2), P23-Tuas-DWB,

P16-Shantou-Danang, P24-Tuas-Danang, P17-Shantou-Taipa,

P25-Tuas-Taipa, P79-Danang-DWB, P21-Shantou-Mersing,

P29-Tuas-Mersing, P18-Shantou-Batangas, P26-Tuas-Batangas,

P19-Shantou-Tungku, P27-Tuas-Tungku, P80-Batangas-Tungku

3. Please go ahead to implement Restoration Plan Reference: SMW-3 (S2) Issue 200X.X and log into SMW-3 Conference Bridge at Tel: +65 6668 7200 , Code: 111489#. For this most updated plan, you may visit the SMW-3 NA’s website at http://www.smw3.com (User ID: smw3na; Password: singtel).

4. Upon successful restoration of the above affected traffic paths, ORCO will issue another order (FORM 2) if necessary to transfer remaining unaffected traffic paths to respective restoration steps to facilitate cable repair.

of 38document.doc

http://www.smw3.com/

Form 2SEAMEWE-3

RESTORATION IMPLEMENTATION SCHEDULE/COMPLETION REPORTTo: SEAMEWE-3 Terminal Parties, STEP Co-ordinators(SCs) & Facility ProvidersCopy to: SEAMEWE-3 Owners (For Info.)From: SEAMEWE-3 ORLO/ORCO (SingTel) Fax.+65-6738-5549/+65-6734-6903Date:___________________ Time (UTC):________________

Please implement the restoration plan for the following bearers.

This is an update/Rest. Completion Report compiled from feedback received (Form 3)

Step Bearer

SNCP

Switching

Date/Time

Scheduled

Date/Time

For Rest’n

Actual

Restored

Date/Time

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

______ _______________________________ ___________ ____________ __________

of 38document.doc

Form 3

SEAMEWE-3RESTORATION COMPLETION ADVICE


From: ________________________________ Fax: ______________ Tel: _______________

STEP Co-ordinator(SC) of ___________________________________________________

(IMPORTANT: Please indicate clearly the STEP(s) involved)

Date: _______________________ Time (UTC): ___________

1. This is to confirm that the following bearers have been restored:

Step Bearer

Carrier RadiatedDate/Time

RestoredDate/Time

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

______ _______________________________________ ____________ ___________

Form 4a

of 38document.doc

SEAMEWE-3CABLE DEPOWERING/POWER RECONFIGURE REQUEST

To: MLO/OPCO of relevant Segment S____ Fax. __________________ Tel. ___________________

From: ORCO (SingTel) Fax. +65-6734-6903

Date: _______________________ Time (UTC): ___________

1. The SEAMEWE-3 System Restoration has been completed.

2. The SEAMEWE-3 Cable System is now handed over to MLO(Maintenance Liaison

Officer)/OPCO (Overall Power Control Officer). Please proceed to de-power the

cable and re-configure the power, in accordance with the power control safety

procedures and messages.

of 38document.doc

Form 4b

SEAMEWE-3POWER CONFIGURATION STATUS


From: ________________________________ Fax: ______________ MLO/OPCO of relevant Segment S____ Tel: _______________

Date: _______________________ Time(UTC):__________

1. Please be advised that the current status of power configuration is as follows:-

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

_______

of 38document.doc

Form 4c

SEAMEWE-3REPAIR COMPLETION ADVICE


From: ________________________________ Fax: ______________ MLO/OPCO of relevant Segment S____ Tel: _______________

Date: _______________________ Time(UTC):__________

1. Please be advised that the final splice operation on Segment S____________ and

power up tests have been successfully completed on __________________ at

______________UTC.

2. Please proceed to normalize traffic on______________________________________

3. Remarks, if any

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________

of 38document.doc

Form 5SEAMEWE-3

SEAMEWE-3 NORMALISATION SCHEDULE/NORMALISATION REPORT

To: SEAMEWE-3 Terminal Parties, STEP Co-ordinators(SCs) & Facility Providers

Date: _____________

Copy: SEAMEWE-3 Owners (For Info.)

From: SEAMEWE-3 ORLO/ORCO (SingTel) Fax. +65-6738-5549/65-6734-6903

SEAMEWE-3 Cable repair is expected to be completed on __________________ at ________UTC. Please Normalize according to the following schedule.This is a Normalization Report compiled from submissions received (Form 6).Power re-configuration is completed. We will normalize according to the following schedule.

Step Bearer

Scheduled

Date/Time For

Normalization

Actual

Normalized

Date/Time

______ _________________________________ ____________ __________

______ _________________________________ ____________ __________

______ _________________________________ ____________ __________

______ _________________________________ ____________ __________

______ _________________________________ ____________ __________

______ _________________________________ ____________ __________

______ _________________________________ ____________ __________

______ _________________________________ ____________ __________

______ _________________________________ ____________ __________

of 38document.doc

Form 6SEAMEWE-3

NORMALISATION ADVICE


From: ________________________________ Fax: ______________ Tel: _______________

STEP Co-ordinator(SC) of _____________________________________________

_____________________________________________________________________(IMPORTANT: Please indicate clearly the STEP(s) involved)

Date: _______________________ Time (UTC): ___________

1. We confirm that the following traffic paths have been normalized as indicated

Step Bearer

Normalized

Date/Time

Carrier Removed

Date/Time

______ _______________________________ ___________ ______________

______ _______________________________ ___________ ______________

______ _______________________________ ___________ ______________

______ _______________________________ ___________ ______________

______ _______________________________ ___________ ______________

______ _______________________________ ___________ ______________

______ _______________________________ ___________ ______________

______ _______________________________ ___________ ______________

______ _______________________________ ___________ ______________

of 38document.doc

6. SEAMEWE-3 RET Form


Copy: ____________________________ Fax:_______________(Please also copy to your counterpart)From: ____________________________ Fax: _______________ Tel:________________STEP Co-ordinator(SC) of ________________________(IMPORTANT: Please indicate clearly the STEP(s) involved)

Date: _________________ Time (UTC): _________

Note:- If test parties have other preference for the test date/time, please liaise and arrange among yourselves, and update ORLO accordingly. If restoration routes involve more than 3 test parties, please use the SMW-3 Conference Bridge (Tel: +65-6668-7200. Code: 111489#) with SMW-3 NOC to assist in coordinating the initial set-up.

In RET case, SCs, of course, do not require SMW-3 NOC to inform them of SNCP switching. SC shall be responsible to collect the BER test results and ODF termination checks of involved stations. IF BER is bad, SC shall liaise with providers to troubleshoot. SC shall then complete the RET Form, and submit to ORLO office.

Rest’nStep

Restored VC4 Bearer

*IMPORTANT:Does the physical ODF/DDF to SMW-3 TM/ADM connect’n at both ends conform to the latest issue of URM plan ?[Yes(Y) or No(N)]

(See Note)RET StartDate/Time(UTC)

(24Hr)End-to-End Continuity EstablishedDate/Time(UTC) Test

Result/ Remark

(Y / N) (Y / N)

(Y / N) (Y / N)

(Y / N) (Y / N)

(Y / N) (Y / N)*IMPORTANT: SC, please circle clearly the indication, after checking with your counterpart.

of 38document.doc

(Example of NEW Format for RET Form)


Copy: Mr. Lee Fax:86-754-7870034(Please also copy to your counterpart)From: Mr. Wannabe/Tokyo ITMC(KDDI) Fax: 81-3-3347-5720 Tel: 81-3-3347-5715STEP Co-ordinator(SC) of S1-STEPs 1.1, and 1.2(IMPORTANT: Please indicate clearly the STEP(s) involved)

Date: 11 Dec 01 Time (UTC): 0800

Note:- If test parties have other preference for the test date/time, please liaise and arrange among yourselves, and update ORLO accordingly. If restoration routes involve more than 3 test parties, please use the SMW-3 Conference Bridge (Tel: +65-6668-7200. Code: 111489#) with SMW-3 NOC to assist in coordinating the initial set-up.

In RET case, SCs, of course, do not require SMW-3 NOC to inform them of SNCP switching. SC shall be responsible to collect the BER test results and ODF termination checks of involved stations. IF BER is bad, SC shall liaise with providers to troubleshoot. SC shall then complete the RET Form, and submit to ORLO office.

Rest’nStep

Restored VC4 Bearer

*IMPORTANT:Does the physical ODF/DDF to SMW-3 TM/ADM connect’n at both ends conform to the latest issue of URM plan ?[Yes(Y) or No(N)]

(See Note)RET StartDate/Time(UTC)

(24Hr)End-to-End Continuity EstablishedDate/Time(UTC) Test

Result/ Remark

S1-STEP 1.1

OKIW-SHTO VC4S1

KDDI ( Y / N )

CT ( Y / N )

10 Dec 01/0200

10 Dec 01/0300

KDDI confirmed with CT that the test result isGOOD

S1-STEP 1.2

OKIW-SHTO VC4S2

KDDI ( Y / N )

CT ( Y / N )

10 Dec 01/0200

10 Dec 01/0330

KDDI confirmed with CT that the test result isGOOD

*IMPORTANT: SC, please circle clearly the indication, after checking with your counterpart.

of 38document.doc

7. SEAMEWE-3 SC’s guide to troubleshooting restoration paths

1. Step Co-ordinators can help speed up troubleshooting of restoration paths which doesn’t work. The most common reasons are due to Bad Loop (forgotten to normalize loopback somewhere in the restoration path), Open Circuit (wrong patch of ports not following URM), and Software Disconnect(wrong matrix connection in DXC, resulting in C2 Signal Label HO unequipped).

2. DO’s

a. Before the failure occurs (PLEASE REFER TO DIAGRAM next page):

- Identify (phone/names) all relevant 24x7 manned stations controlling the relevant SDH equipment.- If possible/practicable, do a sketch of the restoration path, with the aid of the sample attached. Label all ports.- Be familiar with URM Plan reference to the relevant ports for interconnecting points. (Don’t call NOC to check)- Identify a “tracer” reference circuit inside the STEP if necessary. For example if the restored bearer is Tuas Shantou VC4 and consists of mix of many E1s, VC3, from various WDMTS, etc., then the SC need to trace back a VC3 or E1 from the terminating Shantou data Centre or ITMC, and locate the NMS control centre for such circuit so that when doing loopbacks or circuit checking, it is sufficient to contact the end stations to find out status instead of flooding the SEAMEWE3 NOC/Singtel to find out if the TM port is clear of alarms.

b. When the failure occurs, SNCP switched by NOC but restoration not working:

- Contact the relevant stations one by one to see if the path is correctly connected.- Make sure SNCP is correctly switched out by looking at cable station’s SH. Contact relevant stations, where necessary.- If all above fails, then request one by one the stations to loop back and at each step check with the NMS centre managing the “tracer” circuit whether AIS alarm is cleared. It is not necessary to call NOC.

Remember that at any point of disconnect, receive port will have LOS alarm, and generate AIS backwards to all stations which will receive the AIS alarm.

DON’T’s

- When asking for Loopback, don’t use the words like “give me” a loopback. On the phone, “me” is often misunderstood, always identify the station, e.g. “give a loopback towards Shantou cable station”.- Don’t call the NOC to check whether Alarm is cleared or not during the troubleshooting process. Use a local “tracer circuit” or else contact the centre managing the NMS of the controlling station at the far end terminals. If everyone calls the NOC to check if alarm is cleared or not, then the purpose of decentralizing the restoration is defeated.

of 38document.doc

of 38document.doc

OTHER DXC

OTHER DXC

IN-SYSTEM SHANTOU-OKI

Restoration Troubleshooting for SHANTOU TUAS TRAFFIC(Example)

Force SNCP

Identify either Port A or B and observe clearing of AIS alarm of tracer traffic* through LOCAL NMS of local SDH.

Shantou DOMESTIC Network

1TM27/09-02 TM14/11-01 TM08/11-01 5-11-1 4-15-2 CR4A/F2/S1/F2 CR4A/F1/S1/P2 TM02/09-02

Cable CUT

TMADM

TM TM

ADM ADM

ADM

DOMESTIC JAPAN LINK

ADM

ADM

APCN

ADM

ADM

TMADM

TM

Force SNCP ADM

ADM

1641DXC

ADM

ADM

TM

ADM

OTHER DXC

ADM

ADM

Tuas DOMESTIC Network

See Notes for Shantou

2

12

3

3 4

4

Submarine link SMW3

5

5

6

6

78

7 8

A

B

b

a

Singapore Terrestrial

ITMC/ Data Centre

Singapore ITMC/ Data Centre

1. The important start/end Ports are No. 1 , No. 8. SMW3 NOC through RM can see alarm status of these Ports and able to systemetically diagnose restoration problem by requesting loopback at other Ports, moving upstream and monitoring the alarm condition of No. 1 / 8.

2. Step coordinators do not have visibility of No. 1 & 8, and they should not contact NOC for checking, otherwise it defeat the purpose of “decentralising” the restoration process to increase speed.

3. Instead Step Coodinators should trace back one step to the local traffic originating point (A) or (B). If the Step involved is a whole VC4 the Port A or B is monitored easily by contacting local NMS for domestic network. If the Step involved is a re-constituted traffic at 1641 DXC, then a pre-determined “tracer” traffic (VC3 or VC12 traffic inside the Step) originating further back from their ITMC or Data Centreshould be used as circuit status check in lieu of the No. 1 & No. 8 reference which are only visible from SMW3 NOC’s RM.

STEP 1-G Shantou Tuas VC4S14

OTHER DXC

1641DXC

1641DXC

1641DXC

OTHER DXC

OTHER DXC

IN-SYSTEM SHANTOU-OKI

Restoration Troubleshooting for SHANTOU TUAS TRAFFIC(Example)

Force SNCP

Identify either Port A or B and observe clearing of AIS alarm of tracer traffic* through LOCAL NMS of local SDH.

Shantou DOMESTIC Network

11TM27/09-02 TM14/11-01 TM08/11-01 5-11-1 4-15-2 CR4A/F2/S1/F2 CR4A/F1/S1/P2 TM02/09-02

Cable CUTCable CUT

TMADM

TM

TMADM

TM TM

ADM

TMTM

ADM ADM

ADM

ADM

ADM

DOMESTIC JAPAN LINK

ADM

ADM

ADM

ADM

APCN

ADM

ADM

ADM

ADM

TMADM

TM

TMADM

TM

Force SNCP ADM

ADM

ADM

ADM

1641DXC

ADM

ADM

ADM

ADM

TM

ADM

TM

ADM

OTHER DXC

ADM

ADM

ADM

ADM

Tuas DOMESTIC Network

See Notes for Shantou

22

1122

33

33 44

44

Submarine link SMW3

55

55

66

66

7788

77 88

AA

BB

bb

aa

Singapore Terrestrial

ITMC/ Data Centre

Singapore ITMC/ Data Centre

1. The important start/end Ports are No. 1 , No. 8. SMW3 NOC through RM can see alarm status of these Ports and able to systemetically diagnose restoration problem by requesting loopback at other Ports, moving upstream and monitoring the alarm condition of No. 1 / 8.

2. Step coordinators do not have visibility of No. 1 & 8, and they should not contact NOC for checking, otherwise it defeat the purpose of “decentralising” the restoration process to increase speed.

3. Instead Step Coodinators should trace back one step to the local traffic originating point (A) or (B). If the Step involved is a whole VC4 the Port A or B is monitored easily by contacting local NMS for domestic network. If the Step involved is a re-constituted traffic at 1641 DXC, then a pre-determined “tracer” traffic (VC3 or VC12 traffic inside the Step) originating further back from their ITMC or Data Centreshould be used as circuit status check in lieu of the No. 1 & No. 8 reference which are only visible from SMW3 NOC’s RM.

STEP 1-G Shantou Tuas VC4S14

OTHER DXC

1641DXC

1641DXC

1641DXC

8. PROCEDURE: “Manually Release SNCP switch” (Revised Version)

If a station is isolated from Tuas RM, you have to follow this scheduling to release theSNCP switch for each trail on the relevant ADM.

1°) On 1353SH, select the relevant ADM part of restoration scheme, then from the menu « Supervision », item « Access State », select « Local » to give the permission for management on the ADM by the Craft Terminal.

2°) Connect the Craft Terminal on the relevant ADM.

3°) Select icon « NECTAS » Enter login and password.

4°) On the Craft Terminal select the line « M:0-S:0 1664M21 ». This line is automatically shown if there are alarms on the ADM. If there are no alarm, to open this line select « View » and choice « All elements » one click.

5°) On the Craft Terminal, from the menu « Application_Choice », select the item « 5) Alarms, Status & Remote Control »

6°) From the window « AS&C - 1664SM - M:0-S:0 », select menu « Remote_Control », then select the item « All ».

7°) Opening Window Display Remote Control. Select your command. « Force West PPS Trib » to force in west and lock in west. « Force East PPS Trib » to force in east and lock in east. « Clear force PPS Trib » to release the locking state. This command doesn’t affect the switch.

8°) For each protected trail, select the relevant tributary and click on « ok ».

Case 1: Restoration activation : in case of cable fault and if 1353RM (in Tuas) can not activate restoration: « Clear force PPS Trib » on port A or B (in order to release the switch) Traffic is now switched on the restoration route!!(See Note for KDDI’s comment on Case 1)

Case 2: Restoration activation : in case of planned restoration before cable fault repair and if 1353RM (in Tuas) can not activate restoration: « Clear force PPS Trib » on port A or B (in order to release the switch) « Force East PPS Trib » on port A or B Traffic is now forced on the restoration route!!

Case 3: Normalization of traffic back in SMW3 : after cable fault repair and if 1353RM (in Tuas) can not normalize traffic: « Clear force PPS Trib » on port A or B (in order to release the switch) « Force West PPS Trib » on port A or B Traffic is now back to SMW3!!

9°) Back on 1353SH, you have to disable the management on this ADM by the CraftTerminal, using the menu « Supervision », item « Access State », select « OS ».

Here follows a correspondence table between the STM1 you have to switch on theRM, using the reporting of the trail and the table used by the Craft Terminal.

of 38document.doc

For example, if you want to release the SNCP switch for the ho-trail using theresource “djib-suez_S06F1L1_A01/sr1sl04/ElTribStm1#01”, you should select the“ Port A Tributary 3” on this ADM from the Craft Terminal.

On the RM On the Craft Terminal“ADM_name”/sr1sl02/ElTribStm1#01 Port A Tributary 1“ADM_name”/sr1sl02/ElTribStm1#02 Port B Tributary 1“ADM_name”/sr1sl03/ElTribStm1#01 Port A Tributary 2“ADM_name”/sr1sl03/ElTribStm1#02 Port B Tributary 2“ADM_name”/sr1sl04/ElTribStm1#01 Port A Tributary 3“ADM_name”/sr1sl04/ElTribStm1#02 Port B Tributary 3“ADM_name”/sr1sl05/ElTribStm1#01 Port A Tributary 4“ADM_name”/sr1sl05/ElTribStm1#02 Port B Tributary 4“ADM_name”/sr1sl08/ElTribStm1#01 Port A Tributary 5“ADM_name”/sr1sl08/ElTribStm1#02 Port B Tributary 5“ADM_name”/sr1sl09/ElTribStm1#01 Port A Tributary 6“ADM_name”/sr1sl09/ElTribStm1#02 Port B Tributary 6“ADM_name”/sr1sl10/ElTribStm1#01 Port A Tributary 7“ADM_name”/sr1sl10/ElTribStm1#02 Port B Tributary 7“ADM_name”/sr1sl11/ElTribStm1#01 Port A Tributary 8“ADM_name”/sr1sl11/ElTribStm1#02 Port B Tributary 8

of 38document.doc

Notes:

1. KDD’s comments on Case 1:

KDDI could confirm the above procedure with KDDI Okinawa staff during the SMW-3 Refresh Training in Okinawa cable station end 2002. However, KDDI had a comment on the Case 1 (Restoration activation: in case of cable fault and if 1354RM (vice 1353RM) (in Tuas) can not activate restoration.

According to the SC's Guide, traffic is switched on the restoration route just after invoking the "Clear Force" command. Yes, that is correct. KDDI could confirm the temporary facility configuration using the vacant SIE ports and SDH analyzers.

However, if restoration route is interrupted and there is no alarm on the original route, traffic is automatically switch back to the Original route even if SNCP is set up to the "Not revertive" mode since the SNCP status is just "No operator request".

Therefore, is it required to invoke the "Force East" command just after invoking the "Clear Force" command in order to keep the traffic on the restoration route.

of 38document.doc

9. History of main problems, solutions and feedback gathered

9.1. (From 1999- 2001)From time to time, the SMW3 NOC has been called upon by terminal parties to provide the following at their remote end:

a. Divergence of traffic from working card in the 1:8 system to the protection card

As the SDH equipment belongs to the terminal parties, they are rightfully responsible for their functionality and status. Thus, SMW3 NOC would like to seek the cooperation of the terminal parities to attend to these issues on their end. This issue has been agreed in previous O&M SC meeting.

b. Configuration of card from 140MB-to-STM1 (vice versa)Please refer to reason above.

c. Setting Performance Monitoring (PM)Setting up PM takes up considerable processing resource of the SMW3 RM (Regional Manager) as it needs to poll the monitored remote NEs every 15 minutes for results. With the increasing traffic capacity handled by SMW3 RM, PM would reduce the efficiency of the RM further. This would have a negative impact especially on the restoration activities that need to be carried out in the event of a cable failure.

SMW3 NOC wish to seek the understanding from the terminal parties to activate PM sparingly. If a request has to be made to set up PM on SMW3 system, terminal parties are requested to advise SMW3 NOC on the duration of monitoring so that NOC may remove the PM when it is no longer needed.

d. EML (Element Management Level) ProblemDuring the S10.1 failure (29 Jun – 15 Jul 01), SMW-3 NOC experienced EML problem in accessing to the ADMs in Goonhilly and Norden. As a result, LCT (Local Craft Terminal) had to be used, and delay was experienced. We have checked with Tuas cable station on this EML problem. This was mainly due to the 1353SH not responding to the RM. Subsequently, the following day, Tuas coordinated with Norden cable station to reboot the 1353SH to ensure that the ADM access state was in OS (Operation System) mode, after the manual SNCP switching. The EML was then aligned from Tuas’ RM.

Based on ASN's advice, the 1353SH was not responding probably due to insufficient memory. ASN has advised all the cable stations to clear their alarms in the 1353SH, and refrain from accumulating. If these are not cleared, then the memory resources could be drained off easily in the 1353SH, and caused this EML unreachable.

Learning from the above incident, we would like to urge all members to convey this message to your operation staff, and ensure that the above housekeeping is performed accordingly.

of 38document.doc

e. Procedure for Manually Release SNCP switchAt the same time, please also ensure that a copy of the Procedure for Manually Release SNCP switch is made available in the respective stations/RCOs, and staff are well versed with the steps involved. This will definitely expedite the whole restoration process in the event that RM is unable to access to the ADM, and manual SNCP switching via LCT has to be performed.

-End-

of 38document.doc

seamewe-3 sc’s guide · web viewthis line is automatically shown if there are alarms on the adm....

Documents