1678MCC R42 UK Training For Commiss

12
Do not delete this graphic elements in here:
1678 MCC R4.2 TAC Training

Christian Wittig US/S 22.09.2007
1678 MCC Operation and Maintenance

All Rights Reserved 2007, Alcatel-Lucent
AGENDA
Product Overview Function and Features 122
Mon
1.
Functional Overview, Redundancy mechanism and Hints
2.
3. 4.
New HW LAX + 1GBE HW + 1GBE Commissioning + 1GBE Commands on SC

HO-Matrix and Synchronization issue DCC / OSPF / OSI Ticket Overview 1678MCC TAC Germany Documentation in intranet Known Bugs in Transmission and LowOrderMatrix issues CT IP Tunnel / EP Dialog
Tue
1. 2. 3. 4.
Wed
1.
2. 3.
FLC Replacement
Usefull SC commands Health Check
All Rights Reserved Alcatel-Lucent 2007
Product Overview Function and Features
123
1 Functional Overview
1 Functional Overview
Product Overview Function and Features HK, RA, RL
124
Operation System
external LAN
Craft Terminal
DCC Subsystem
Control & Software Subsystem
9952 MBit/s 2488 MBit/s 622 MBit/s 155 MBit/s Gigabit Ethernet
STM-64
STM-16 STM-4 STM-1 o./el. GbEthernet 10GbEthernet I/O Subsystem Main Shelf
T1 T0
STM-4 STM-1 o./el. 140 MBit/s
622 MBit/s 155 MBit/s 140 MBit/s
2 MBit/s Cross Connection Subsystem

T0
2 MBit/s
10 Gigabit Ethernet
I/O Subsystem OED

T1/T2
T0
Synchronisation Subsystem
T3/T6 1678 MCC Operation and Maintenance
T4/T5
3 1678 MCC Main Shelf
3.7 Main Shelf Architecture

Operation System
Customer DCN
Rack Lamps Q3 F Craft Terminal F Q3 RL Remote and Housekeeping Alarms RA/HK
On Board LAN switch
1678 MCC Main Shelf
On Board LAN switch EM DCR

DCC Server
DCR
DCC Server
EM
FLCSERV Disc
Backpanel LAN (ISSB)
First Level Control
Disc
FLCCONGI
SC
Matrix LO Copy A
SC
Matrix HO Copy A
Management Bus (to/from I/O boards)
SC
Matrix HO Copy B
SC
Matrix LO Copy B
Second Level Control
3.10 Matrix Redundancy

I/O board
Assembler Assembler
HO Matrix active
LO Matrix active
copy A
copy A
I/O board
HO Matrix hot standby copy B
LO Matrix hot standby copy B
3.9 Low Order (LO) Matrix

Product Overview Function and Features RX direction STM-N 127
1678 MCC Main Shelf

copy B copy A HO Matrix board (1 pair)
TX direction STM-N STM-1 el. GbEthernet OED 1670 SM
STM-1 el.
GbEthernet OED 1670 SM STM-4 STM-1 op. STM-1 el. 140 Mbit/s VSR Link boards I/O boards
VSR Link boards
I/O boards
I/O boards
I/O boards copy B copy A Assembler LO Matrix (1 pair) Assembler
STM-4 STM-1 op. STM-1 el. 140 Mbit/s
OED 1662 SMC SYNTH16 board I/O boards
OED 1662 SMC SYNTH16 board I/O boards
2 Mbit/s
Switching on VC-12 / VC-3 level
2 Mbit/s
Assembler: Function to perform the high order path termination and adaptation
1678 DCN Architecture

OS
DCN
10/100BaseT (autosens, autoneg) 10/100BaseT (autosens,autoneg)
FLCSERVICE (active) on Board LAN SW (5x 10/100 Mbit/s)

IP Addrs: dcrServ activeDCR hostId gmreNode OSI Addr: NEs NSAP IP Addrs: emServ activeEM
FLCCONGI (standby) on Board LAN SW (5x 10/100 Mbit/s)

IP Addr: dcrCong IP Addr: emCong
OSPF
IS-IS
DCR
to OED
DCC
EM
DCR
EM
to OED
F-IF
IP Address Rules
The following addresses are in a common IP subnet (at least /28)

emServ emCong dcrServ
dcrCong
(always configured on the active FLC) activeDCR(always configured on the active FLC) localCT (reserved address for installation purposes) dcnGateway (if DCN connection is via LAN) The address DCRHostId/32 is needed if IP-over-DCC and/or OSPF is used Used as local address of all unnumbered IP-over-DCC links Used as OSPF router Id The address GmreNode/32 is needed if GMRE is used Used for GMRE neighbor-to-neighbor communication
activeEM
NE Management
Product Overview Function and Features 1 2 10
Management via Q3 or Q-RFC1006 IP mandatory for

Software
Installation and Update (ssh, ftp)

Provisioning (TCP based application) Backup/Restore (currently rsh-based, planned to move to
Equipment Time
Synchronization (NTP)
Configuration
ssh)
Management (IP and OSI) possible via LAN or DCC
Behavior on External LAN

Internal and external traffic separated via VLAN setup on on-board LAN SWs
Default: No No
no VLAN tagging on external LAN
internal IP addresses on external LAN

dedicated Router necessary per NE
Rapid Spanning Tree Protocol (RSTP) running on on-board LAN SWs

For
DCN redundancy reasons, external LAN ports to be interconnected via (RSTP
capable) LAN-Switching equipment

Bootp used during initial installation
OSI Address Rules

NSAP for Q3 communication always configured on active DCR Management may be via
Q3 NSAP address
RFC1006 activeDCR IP address
NE Address auto-detect for local CT connected via F-interface
Configuration Contents FLC

Backup / Restore functionality
FLC is installed with SW R4.2 and correct IP addresses
Platform Release (CORE-01J)

Application Release SKY42-05K
Persitency Cs Parameter Basic Framework
MIB, PmMgr, VHM Network configuration Hardware configuration (bfw db)
Stored in Backup
Configuration Contents FLC

VERIFY THAT BOTH FLCs ARE SYNCHRONIZED
Persistency Check
tools PersSync
CS Configuration
start
CSConfigCLI m n s
(all SCs, LAX, Synth16 listed)
appl@emCongA3(appl)$ 0 | no valid line in Offset-File 1 | no valid line in Offset-File 2 | no valid line in Offset-File 3 | no valid line in Offset-File 4 | no valid line in Offset-File 5 | no valid line in Offset-File 6 | no valid line in Offset-File 7 | VHM | 5043 | S | 8 | PmMgr | 66 | S | 9 | SSU | 123 | S | 10 | MIB | 2742 | S | 11 | MIB | 2742 | S | 12 | MIB | 2742 | S | 13 | no valid line in Offset-File 14 |CSServer | 1 | S | 15 |CSServer | 1 | S | 16 |GMRE_PM | 1 | S | 17 |GMRE_MA | 1 | S | NVRAM access successfully ended!
PersSync
with with with with with with with
1 2 14
this index this index this index this index this index this index this index 0 | T | F | F |0K 66 | T | F | F |0K 38 | T | F | F |0K 0 | T | F | F |0K 0 | T | F | F |0K 0 | T | F | F |0K with this index 0 | T | F | F |0K 0 | T | F | F |0K 0 | T | F | F |0K 0 | T | F | F |0K
Compare on both FLC

appl@emServ_A(STARTUP)$ start appl@emServ_A(STARTUP)$ CSConfigCLI -a -b -p -v -s n hoSlca_1_dcrs|100.1.10.1|100.1.203.4|00:00:00:00:00:0A|MX640GEA hoSlca_1_dcrc|100.1.10.20|100.1.203.5|00:00:00:00:00:0A|MX640GEA hoSlcb_1_dcrs|100.1.11.1|100.1.203.4|00:00:00:00:00:0B|MX640GEB hoSlcb_1_dcrc|100.1.11.20|100.1.203.5|00:00:00:00:00:0B|MX640GEB
Basic Framework
start ll bfw*
Execute to compare both FLC at once

appl@emServ(appl)$ start appl@emServ(STARTUP)$ ssh remoteau cat $STARTUPDIR/bfwdb_network.rdf | diff b B bfwdb_network.rdf 8c8 < <equip:EMType>S</equip:EMType> - - > <equip:EMType>C</equip:EMType>
CS parameters
Set CS configuration in Equipment Provisioning
Note: Avoid changing FLC IP address after first installation

CS Parameters
Check CS parameters on UNIX level

Get CS Parameters Login active EM as user appl bash tools getCSParams --file=/tmp/cs_params
<theNetworkPartIP type="string">10.227.225.96</theNetworkPartIP> <theNetworkPartNumBits type="string">28</theNetworkPartNumBits> <theDefaultGateway type="string">10.227.225.97</theDefaultGateway>
In case of EP not available: It is possible to change CS parameters Set CS Parameters
bash
tools setCSParams --file=/tmp/cs_params
CS parameters
What is the meaning of files PrelimCSSRepository.xml and Installconfig.xml ? Active FLC SW Installation Standby FLC
Installconfig.xml
CSServer CSServer
Use Equipment Provisioning : Change CS configuration
PrelimCSSRepository.xml Installconfig.xml.processed
Gigabit Ethernet
Logical Model for GBE EPL
Ethernet/GFP-F Mapping
Core header Payload header
Gigabit Ethernet
GFP Generic Frame Procedure
Commissioning of 1GBE
Follow commissioning docu for related release on NPI homepage or Customer docu homepage
Setup VCG using ISA port configuration menu Create unidirectional CrossConnection Loop from/to VC4vTTP of the 1GBE port on test Connect Ethernet Testset and check that L2 traffic is transported Test optical output power of GBE port and check that range is correct according to Commissioning protocol
Commissioning of 1GBE
Use ISA Port Configuration Menu to Setup Ethernet port
1 2 22
HO-ShelfController
Boot up HO-SC
Boot of Rawloader
gs go (to coninue bootup) Trace using Serial cable on debug interface (38400 baud)
Load of SC Image from FLC

Follow up on serial cable OR Open telnet Session and enable trace
telnet 100.1.10.1 chg + tr + red

chg tr rest
HO-ShelfController
Check image version on HO-SC
appl@mgb1em3(LogFiles)$ telnet 100.1.10.1

me 1 3 Make your choice:3
@(#)SEL Stuttgart SCM ID: SKY11-02L Released on Thu Jun 23 08:56:46 MEST 2005 Application software for SC1678mccX (SDH) R. 03.01.59 Based on generic SW R. 02.01.13 SC Protocol version: 11.6.1.0.0.0 SMX Protocol Version: 10.2.0.0.0.0
The image is located on DCR Board on each FLC: /dcrroot/tftpboot/NE_1678MCC/SC_SCM/ Image78MCC
HO-ShelfController
Check platform on HO-SC

Telnet+> plat
SC Application Platform Version: 'V8.1.0P110'

Date: Oct 11 2005 Board Configuration Pigato EPLD version not available on PQ2 SCM board V1.14 Micro Revision Number : 81 Cpu clock : 198MHz Cpm clock : 132MHz Instruction Cache : enabled Data Cache : enabled Copy Back : activated MMU : enabled Phisical Ram Size Equipped: 512Mbytes Ram Size Configured : 472Mbytes Application start address : 0x100000 Application end address : 0x1800000 SC Application Platform Libraries Version: LIB: ldr_lib_ec - REL: 'RWL-PQ2-EMC''V8.1.0P110'P9 (Oct 11 2005) llc2_lib - REL: 'CS-PQ1-GEN-LLC2''V8.1.0'P29 (Mar 30 2006) sec_lib - REL: 'KS-PQ2-SMC''V8.1.0P110'P18 (Jul 11 2006) ks_lib - REL: 'KS-PQ2-GMC''V8.1.0P110'P19 (Sep 8 2006) libbsp - REL: 'KS-PQ2-GMC''V8.1.0P110'P19 (Sep 8 2006)
LIB: LIB: LIB: LIB:
Synchronisation issues on MX640

Heated Quartz on MX640

Check Syncronisation on HO-MX
Check external references
me 4 5
Difference between Timing Source <-> headed 10 MHz quartz decValue in ppb (parts per billion) -> / 1000 -> in ppm Alarm: SSF (Server Signal Failure) on port, SF (Signal Failure) on Timing Source (Sync View) FO (Frequency Offset) Reason: TimeSource not working or Hardware (faulty quartz), doublecheck with bsw command Action: repair/remove Timing Source or replace MX board

Check T0 Output
me 4 14
Difference between Systemclock (T0) of active Matrix (used) <-> Output Frequency (T0) of passive Matrix (not used) decValue * 0.0226 -> in ppm Alarm: SSM (Synchronization Source Missmatch) if Difference decValue > 16 (0.3616 ppm)
Reason: Hardware (different from the problems above)

Action: It cant be determined which MX board cause the problem (sender -, receiver problem). The alarm is always reported from the passive matrix. Nevertheless the problem can be caused by the other one. Replace the passive matrix first. If this is nou successful replace the active matrix too (procedure required!). Note: A new plugged-in board reports this alarm until the CRUs are synchronized. This can take up to 45 min (normal case 10-15 min).

Check Register 84 bsw ispbRD 9 4 84 bsw ispbRD 10 4 84

Difference between Systemclock (T0) <-> headed 10 MHz quartz hexValue -> decValue * 0.0226 -> in ppm 0x7ff-hexValue -> decValue * 0.0226 -> in ppm Alarm: FO (Frequency Offset) (raised if > 10.0 ppm, cleared < 9.2 ppm) Reason: Hardware (faulty quartz) Action: replace MX board
DCC in 1678MCC
DCC Overhead Communication Channels

>DCC
8
Capabilities
x DCC-M + 2 x DCC-R per STM-N board
Configurable
on ports 18
42
x DCC-M + 16 x DCC-R per system
>DCC Application
Remote
2
management of NEs in STM-N rings
x DCC-M per STM-N ring (east west) STM-N rings per 1678
21
IF/IB
Signalling for GMPLS

NE management
Remote
DCC
Management over DCC
Ethernet
DCC
Management of NE2 is possible using NE1 as gateway NE for IP and OSI In EP dialog Gateway field is empty for NE2
DCC
Configuration of OSPF interface (OSPF Router ID) Example: NE1 ip address: 10.10.133.12 -> NE1 OSPF Router Id: 10.10.254.133
Menu Comm.Routing -> Interface Configuration -> OSPF
OSPF is needed for automatic IP routing through DCC

DCC
Configuration of LAPD interface
Configuration -> Comm.Routing -> LAPD -> Create X
X In case of Ethernet connected set to NO
DCC
Enable OSPF for LAPD port and Local Ethernet
Configuration -> Comm.Routing -> Interface Configuration -> OSPF
OSPF set on Local Eth.
Dont forget Admin State UP
OSPF set on LAPD
1678MCC Ticket overview DXC TAC Germany

Nr
Category
Mai
June
July
August
1 2 3 4 5
MX640/MX320/MX160 HW defect OED lost Question/Info Transmission Matrix issues, also Dafodil problem, OH-Link Others ICP/CSF/RTCSync/LanFailure Int.Comm
2 0 2 2 11
0 0 1 1 27
1 1 1 2 4
Alarms Loss of Timing Sources; 4 Frequency offset
Solution
10
GBE / Question
0 RUM Synth16 1 LossOfPointer/SS 3 F/RMAF/RMBF Solved by Reset MX640 8 Solved by SW Reset of Lan-Failure, ICP, DCR, LAX or Process 5 CSF, NoRTCSync Restart GBE Modul defect / wrong SSF,CPE, interpretation by Sequence operator/interworking 3 Mismatch problem
Exchange of MX640 Solved by EC Reset Synth16
Ticket overview TAC Germany

Ticket overview TAC Germany

Explanation for meaning of Others
- Trouble shooting transmission issues - I/O Card, FLC, FAN Defect
- Sync Problems solved without HW Change

- hanging processes - wrong configuration - Upgrade Request (ISU) - Request for Patch installation
Documentation
TAC Germanys home page
http://slsvho
Useful knowledge for CrossConnect systems
Documentation
NPI homepage (NewProduct Introduction)
http://aww3.stgl.sel.alcatel.de/pub/tsddev/npi_scm/indus/index.html
Find out correct SW media
Documentation
Customer Service Documentation

http://aww3.stgl.sel.alcatel.de/pub/tsddev/Customer_Service_Docu/
Documentation
CraftTerminal development homepage (Authorisation req.)

http://aww3.stgl.sel.alcatel.de:9000/SH5/start.html View Components of CT-SW
PSC link
http://aww3.stgl.sel.alcatel.de/pub/tsddev/PSC
IDEA Database
http://destgsweb59.ad1.ad.alcatel.com/idea/
Problems Transmission and misbehaviour

1) Wrong implementation of Workaround in SW3.2P3 Caused by short occurance of MS-SSF (MS-AIS). When the workaround interferees then the STM1 sending LOF (Alarmliste: RDI auf MSTTP) Action: Remove/restore Board me 0 3 RMV B04 (Slot 3) RST B04 Board will loose ist traffic on board level for 30sec Fix: 3.2 P5 / R4.2 <- Beispiel

2) RAVEL Register for unused ports wrong
Mismatch db-Info of both SCs. Will be found by HealthCheck. Consequence is that HiOrder-Matrix-Switch leads to traffic interuption of 20sec on all Boards.
Action: Reset cold passive SC EPS switch HiOrder-Matrix (leads to 20s interuption on all boards) Reset passive SC Fix: 3.2 P3

3) Dafodil-ASIC hanging pointer processor Alarm: LossOfPointer (LOP) on 2nd/3rd TUG3; Degraded Signal on MSTTP, Unequipped on TU12 Action
Reset Pointer Prozessor auf AU4 (100 ms interuption auf AU4)

OR Generation of Loss on port (plug out/in fibre) OR
Remove/restore Board (20-30s Ausfall auf Board-Ebene)

Fix: 3.2 P5 (will only avoid new problems)

4) Wrong values for register MOZART/WAGNER/CHOPIN Check registers on active HO-SC bsw bsw bsw bsw bsw bsw bsw bsw bsw bsw bsw bsw ispbRD ispbRD ispbRD ispbRD ispbRD ispbRD ispbRD ispbRD ispbRD ispbRD ispbRD ispbRD 9 2 140 10 2 140 9 3 140 10 3 140 9 5 283 9 6 283 9 7 283 9 8 283 10 5 283 10 6 283 10 7 283 10 8 283 If Overhead links are not correct the HiOrder-Matrix-Switch will lead to power reset on several or on all IO-Boards and to a traffic interuption on these boards
Result:
0xff ff ff fe (wrong) 0xff ff ff ff (correct)
Action:
Remove/restore passive HO-Matrix reset -p Fix: 3.2 P4
ICP/CSF on LAX, HO-MX troubleshooting

1)
All SC/LAX Interfaces pingable from both EM and DCR ? ping ping ping ping ping ping ping ping 100.1.10.1 (HO-MX left) 100.1.10.20 (HO-MX left) 100.1.11.1 (HO-MX right ) 100.1.11.20 (HO-MX right) 100.1.18.1 (left LAX) 100.1.18.20 (left LAX) 100.1.19.1(right LAX) 100.1.19.20 (right LAX)
2) Interfaces internally connected to process ICHdlr ? tools ./statICHdrl c hoSlca_1_dcrs hoSlcb_1_dcrs loSlca_1_dcrs loSlca_1_dcrs loSlca_1_dcrs
connected connected connected connected connected
hoSlca_1_dcrc hoSlcb_1_dcrc loSlca_1_dcrc loSlca_1_dcrc loSlca_1_dcrc
notConnected notConnected notConnected notConnected notConnected

3)
Alarm ICP not active for process ICHdlr ? log tail f scSwitch.log
24.09.2007 08:11:18 Alarm LSSC/CSF = 1 : HoMx (1, 4, 10, 0, 0) passive: HoMx (1, 4, 11, 0, 0) 24.09.2007 08:13:51 : HoMx (1, 4, 10, 0, 0) set EquState: e_EquState_Downloading=>e_EquState_Active 24.09.2007 08:13:51 Alarm LSSC/CSF = 0 : HoMx (1, 4, 10, 0, 0) passive: HoMx (1, 4, 11, 0, 0)
4) Each LAX is loaded correctly ? telnet 100.1.18.1 Telnet+> db role Local Role Equipment State Software State Database state
= = = =
ACTIVE FullyOp Configured DbRunning


5) All SCs are declared in CS configuration on both FLC
start CSConfigCLI m s n
hoSlca_1_dcrs|100.1.10.1|100.1.203.4|00:00:00:00:00:0A|MX640GEA|1_4_10 hoSlca_1_dcrc|100.1.10.20|100.1.120.2|00:00:00:00:00:0A|MX640GEA|1_4_10 hoSlcb_1_dcrs|100.1.11.1|100.1.203.4|00:00:00:00:00:0B|MX640GEB|1_4_11 hoSlcb_1_dcrc|100.1.11.20|100.1.120.2|00:00:00:00:00:0B|MX640GEB|1_4_11 loSlca_1_dcrs|100.1.12.1|100.1.203.4|00:00:00:00:00:0C|LAX40A|1_4_12 loSlca_1_dcrc|100.1.12.20|100.1.120.2|00:00:00:00:00:0C|LAX40A|1_4_12 loSlcb_1_dcrs|100.1.13.1|100.1.203.4|00:00:00:00:00:0D|LAX40B|1_4_13 loSlcb_1_dcrc|100.1.13.20|100.1.120.2|00:00:00:00:00:0D|LAX40B|1_4_13
6)
LAX is present in file /etc/hosts

#---BEGIN_SLC_HOSTS 100.1.10.1 hoSlca_1_dcrs 100.1.10.20 hoSlca_1_dcrc 100.1.11.1 hoSlcb_1_dcrs 100.1.11.20 hoSlcb_1_dcrc 100.1.12.1 loSlca_1_dcrs 100.1.12.20 loSlca_1_dcrc 100.1.13.1 loSlcb_1_dcrs 100.1.13.20 loSlcb_1_dcrc #---END_SLC_HOSTS--
view /etc/hosts
Craft Terminal
Usage of IP Tunnel function

FLC Service ACTIVE ??
F F
FLC Congi
Craft Terminal
-> F-Interface has to be connected to Active FLC
Internal LAN via ISSB-BUS

FLC Service
LAN
FLC Congi
Craft Terminal
-> Use Craft Terminal as PCCT via LAN is independent from state of FLC
CraftTerminal
Usage of IP Tunnel function (no F-Interface)
Start CT Appl.
-> Do not forget to declare the PCCT User in EP Dialog ! PCCT1 NSAP 540072872203010010088010 TSEL: 1102 SSEL: 00 PSEL: 1D
CraftTerminal
Equipment Provisioning without USM

It is possible to open Equipment Provisioning on the Service Laptop without Equipment View c:\alcatel\EP7.1.2\eqpprov\script\start_eqpprov.bat -> Enter IP of active EM -> Enter SW Release
Delete Persistency
Delete Persistency and CS Persistency (FLC default state)

SSUDiag -c shutAppl SSUDiag -c shutSSU tools PersCreate active su root bash start rm PrelimCSSRepository.xml (or move it) start mv Installconfig.xml.processed Installconfig.xml cp bfwdb_network.rdf.default bfwdb_network.rdf killall CSServer WAIT 2minutes tools ./updateCSconfig
FLC Replacement Procedure

FLC Replacement 1) 2) 3) Install new FLC with the same SW, IP and network parameters like on active FLC Start application on newly installed FLC Check processes on this FLC. The FLC should become passive [ Raise Equipment Provisioning, CS parameters and Click OK ] After Supervision comes back the Reinitialize of CS Server has written all necessary Persistency data onto passive FLC. Check this with command PersSync and check CS Persistency on passive FLC:
> start
> CSConfigCLI m n s > tools
> PersSync
Usefull SC commands
Request SC EPS status Check the EPS state of the SCs. In case SF for failure the EPS state release is not possible and the SCs remain with expression mark on GUI.
telnet <IP active SC> me 0 5 Matrix Pg.B10-AUTO_SWITCH pu.B09-SF pu.B10-SF-ACT EPS data: (bm_epsSW_status_t bm_privateEpsData[bSlot]=1=traffic on spare) 0 . 1 . 2 . 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
[EPS pg_status]
In case of EPS possible Pg.B10-NO_REQUEST
pu.B09-OK-ACT pu.B10-OK
Usefull SC commands
Show status of boards Product Overview Function and Features
1 2 57
Sometimes e.g. in ISU it is necessary to display the board status, in case a FPGA download will be performed than the status fpga dwnld will be displayed.
me 0 2 Slot Card Number Status 01->IN Slot number (0... (descrNum.) | S1..26 | A0..A3 B0..B21 | Ex-y | -1 all | Quit):-1 [00 BA01 CT01 B00] normal active [01 BA02 CT02 B01] undef idle 02->OUT [02 BA03 CT03 B02] undef idle 03->OUT [03 BA04 CT04 B03] undef idle 04->OUT [04 BA05 CT05 B04] undef idle 05->OUT [05 BA06 CT06 B05] normal active 06->IN [08 BA09 CT09 B08] normal active 09->IN [09 BA10 CT10 B09] normal active 10->IN [10 BA11 CT11 B10] normal active 10->IN [11 BA12 CT12 B11] normal InsSbyMain 11->IN [12 BA13 CT13 B12] normal InsActSpare 12->IN [13 BA14 CT14 B13] normal active 13->IN [14 BA15 CT15 B14] normal active 14->IN [15 BA16 CT16 B15] normal active 15->IN [16 BA17 CT17 B16] normal active 16->IN [17 BA18 CT18 B17] normal active 17->IN [18 BA19 CT19 B18] undef idle 18->OUT [19 BA20 CT20 B19] normal active 19->IN [20 BA21 CT21 B20] normal active 20->IN [21 BA22 CT22 B21] normal active 21->IN [22 BA23 CT23 A00] normal active 255->IN [23 BA24 CT24 A01] normal active 255->IN [24 BA25 CT25 A02] normal active 255->IN [25 BA26 CT26 A03] normal active 255->IN
Passive LAX card
Active LAX card
Usefull SC commands
Check CRU Status and Clock source The CRU mode must be SC_SYNC_LOCKED before SLC switchover and before testing. That means that a clock source is selected. In the example the CRU mode is not ok, probably no clock source is connected or configured me 4 2
[Get CRU Status]
refCh = SC_SYNC_T0 CRUMode = SC_SYNC_FREERUNNING source = 0 sqStatus = SC_SYNC_SQUELCH_ON syncAlrmSts
...
Usefull SC commands
Check SC traces The SC traces are usefull to find out if the SC behaves suspicious, board reset was performed or a SLC switchover was performed without an obvious reason. The latest traces are recorded. me 1 15
[SC traces]
SC AS 8 ../src/as_rav_blk.c:3204: REPEAT #2 failed to read RAVEL SW version on board with BA 0x2100 (at address 0x2100) SC AS 8 ../src/as_rav_blk.c:3204: REPEAT #3 failed to read RAVEL SW version on board with BA 0x2100 (at address 0x2100) SC AS 8 ../src/as_rav_blk.c:3204: REPEAT #4 failed to read RAVEL SW version
Usefull SC commands
Reset remote SC If the partner SLC should be resetted in case of being unavailable use following command. This can be done when e.g the active SLC is not pingable anymore (CSF alarm). Then perform Cold start. me 1 18
[Restart remote SC] Make your choice:18
### RESTART REMOTE SC ### 1) KS_POWER_ON_START 2) KS_COLD_START 3) KS_WARM_START 4) KS_NO_RESTART 0) Return to Menu
Usefull SC commands
Check ispbs error counters The ispbs is a bus for communication between the SCs and the intelligent boards in the shelf. In case of error counters are bigger than 000FF the bus is disturbed. This can be a result of a faulty board or a faulty Busterm board.
Telnet+> ispbs ----------------------------ISPB-BUS device-driver status ----------------------------- ISPB-read ABE DBE RDY ACK NDN NRS operation performed: = 0x090D7195 error error error error error error count count count count count count = = = = = = 0x00000000 0x00000000 0x00000000 0x000001C2 0x00000000 0x00000000
- ISPB-write - ABE - DBE - RDY - ACK - NDN - NRS
operation performed: = 0x001C7679 error count = 0x00000000 error count = 0x00000000 error count = 0x00000000 error count = 0x00000000 error count = 0x00000000 error count = 0x00000000
-> The error counters can be resetted by using command ispbs ?
Automatic Persistency Check Tool

Backup / Restore

Automatic Persistency Check performs Backup as crownjob

1. Copy script files to both FLCs maint@emServ(maint)$ tar -xvf cb.tar ./Alcatel/ION/DXC/Persistency/Domain.pm ./Alcatel/ION/DXC/Persistency/Slice.pm ./Alcatel/ION/DXC/Persistency.pm ./Alcatel/ION/DXC/CtrlSys.pm ./checkedPersBackup.pl 2. Create storage directories on FLCs
mkdir /packages/checkedBackup chown maint:maint /packages/checkedBackup

3. 3. Setup cronjob for scheduled backup crontab -e
# run checkedPersBackup tool every Mon and Thu at 00:35 UTC 35 0 * * 1,4 cd ~; /usr/bin/perl ./checkedPersBackup.pl >> ~/checkPersistency.log 2>&1
:wq

Backup data are stored in /packages/checkedBackup

1678MCC R42 UK Training For Commiss

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

1678MCC R42 UK Training For Commiss

Hochgeladen von

Copyright:

Verfügbare Formate

12

Do not delete this graphic elements in here:

1678 MCC R4.2 TAC Training

1678 MCC Operation and Maintenance

Functional Overview, Redundancy mechanism and Hints

New HW LAX + 1GBE HW + 1GBE Commissioning + 1GBE Commands on SC

1678 MCC Operation and Maintenance

All Rights Reserved Alcatel-Lucent 2007

Product Overview Function and Features

1678 MCC Operation and Maintenance

All Rights Reserved Alcatel-Lucent 2007

Product Overview Function and Features HK, RA, RL

Control & Software Subsystem

STM-4 STM-1 o./el. 140 MBit/s

622 MBit/s 155 MBit/s 140 MBit/s

2 MBit/s Cross Connection Subsystem

I/O Subsystem OED

3 1678 MCC Main Shelf

3.7 Main Shelf Architecture

On Board LAN switch

1678 MCC Main Shelf

On Board LAN switch EM DCR

First Level Control

Second Level Control

1678 MCC Operation and Maintenance

All Rights Reserved Alcatel-Lucent 2007

3 1678 MCC Main Shelf

3.10 Matrix Redundancy

HO Matrix hot standby copy B

LO Matrix hot standby copy B

1678 MCC Operation and Maintenance

All Rights Reserved Alcatel-Lucent 2007

3 1678 MCC Main Shelf

3.9 Low Order (LO) Matrix

1678 MCC Main Shelf

TX direction STM-N STM-1 el. GbEthernet OED 1670 SM

VSR Link boards

I/O boards copy B copy A Assembler LO Matrix (1 pair) Assembler

STM-4 STM-1 op. STM-1 el. 140 Mbit/s

OED 1662 SMC SYNTH16 board I/O boards

OED 1662 SMC SYNTH16 board I/O boards

Switching on VC-12 / VC-3 level

1678 DCN Architecture

FLCSERVICE (active) on Board LAN SW (5x 10/100 Mbit/s)

FLCCONGI (standby) on Board LAN SW (5x 10/100 Mbit/s)

1678 MCC Operation and Maintenance

All Rights Reserved Alcatel-Lucent 2007

The following addresses are in a common IP subnet (at least /28)

1678 MCC Operation and Maintenance

All Rights Reserved Alcatel-Lucent 2007

Management via Q3 or Q-RFC1006 IP mandatory for

Installation and Update (ssh, ftp)

1678 MCC Operation and Maintenance

All Rights Reserved Alcatel-Lucent 2007

Behavior on External LAN

no VLAN tagging on external LAN

internal IP addresses on external LAN

Rapid Spanning Tree Protocol (RSTP) running on on-board LAN SWs

DCN redundancy reasons, external LAN ports to be interconnected via (RSTP

capable) LAN-Switching equipment

1678 MCC Operation and Maintenance

All Rights Reserved Alcatel-Lucent 2007

OSI Address Rules