Vous êtes sur la page 1sur 19

All TRX are in BL-RSL state

Solution:
Tested circuit with telco and found that the T1 has a loop left out.
Tech from telco normalized T1.
All TRX came to WO state one by one.
Conclusion:
This is is a working T1 circuit and was rewired on the demarc and probably the Tech called for testing and
the loop was left up. Before touching the circuit path let telco test their side first before isolating the T1
towards you. This will prevent tampering existing and working path.

I got an alarm on the BSC 2205 ET2 Failure
Problem:
** ALARM ET-228 1A005-07 PXRECE
(1870) 2205 ET2 FAILURE
01 FF
Solution:
Interpretation of alarm
Alarm 2205 is define as ET2 Failure (ET-228). Hardware or RAM failure on the plug-in unit.
Type of fault is 01 checksum error in load module of RAM. FF means on the BSC otherwise TCSM.
To solve problem you must replace the ET plug-in unit. Follow the procedure in replacing the the ET plug-
in unit.
Alarm 2992 BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON A INTERFACE
Definition:
Calls have been cleared repeatedly on the same A interface circuit due to BTS and transcoder
unsynchronisation and the number of successive releases has exceeded the limit defined in the PAFILE
alarm parameter (alarm limit for successive remote tc failures).
Example:
** ALARM .. SC7_BX
(7590) 2992 BTS AND TC UNSYNCHRONIZATION CLEAR CALLS ON A INTERFACE
1298d 3d 00F3 65535d 255d 34d 13d 4d 03 3d
END OF ALARMS CURRENTLY ON
Meaning:
1. number of PCM circuit
Indicates:
- number of external PCM circuit if GSW and unsubmultiplexed A interface are in use
- number of SMUX PCM circuit if GSW and submultiplexed A interface are in use
- PCMCON record index if GSWB is in use
2. time slot of the above-mentioned PCM circuit
3. circuit identification code
4. PCM circuit part of the circuit identification code
In T1 (ANSI 1.544 Mbit/s) environment the value is 0xFFFF.
5. time slot part of the circuit identification code
In T1 (ANSI 1.544 Mbit/s) environment the value is 0xFF.
6. number of external PCM circuit
7. time slot of external PCM circuit
8. sub-time-slot of external PCM circuit
9. number of transcoder PCM circuit
If GSW is used, this value is 0xFF.
10. time slot of transcoder PCM circuit
If GSW is used, this value is 0xFF.
Instruction:
Block the circuit in question with the MML command CEC.
< CEC:ETPCM=34,CRCT=3-3:
LOADING PROGRAM VERSION 10.40-0
SPECIFIED STATES BEFORE MODIFICATION
ETPCM CRCT DIR CGR NCGR STATE COND
34 3-3 IN 2 PHNM8AMR BL-US -
SYS-ST: 00000000000000000000000000000000
*****
/* GIVE STATE OF EXTERNAL CIRCUIT(S)
WO . WORKING
NU . NOT IN USE
*/
CEC:ETPCM=34,CRCT=3-3:WO;
EXTERNAL CIRCUIT(S) IN SPECIFIED STATES
ETPCM CRCT CGR NCGR OLDST NEWST CONN COND
34 3-3 2 PHNM8AMR BL-US WO-EX IDLE -
SYS-ST: 00000000000000000000000000000000
COMMAND EXECUTED
CIRCUIT STATE HANDLING COMMAND <CE_>
Check the transmission between (the BTS) the BSC and transcoder.
Check other active alarms concerning (the BTS) the BSC and transcoder transmission or transcoder plug-in
units.
Correct the faults causing the alarms. When the above-mentioned transmission alarms have been
cancelled or when transmission is working again, deblock the circuit in question with the MML command
CEC.
This alarm only informs the user that calls are cleared due to unsatisfactory transmission or equipment
failure but it does not directly indicate the faulty equipment, for example a plug-in unit.
Cancelling:
Do not cancel the alarm. The system cancels the alarm when the user blocks the circuit.
The system also cancels the alarm if a call is cleared in the circuit in question for some other reason than
BTS and transcoder unsynchronisation.
he command calendar is a program entity which is used to execute the MML
commands and command files at a given time or on the basis of alarms.
Set the backup procedure permanently into the command calendar. Activate the command calendar.
The command calendar can handle only one task at a time. If a task execution should start when the
previous one is still on, it is set to pending and the execution is delayed.
There are three modes for making a fallback:
1. FULL creates a new fallback build
2. DATA makes a safecopy of data files
3. ARCHIVE makes a safecopy of changed files
Steps
1. Define the command into the command calendar (ICI).
ZICI:<mml command code>,::<execution parameters>;
After the ICI command execution, the necessary parameters for the given
MML command are requested.
<mml command code>:MODE=<mode>,DIRE=<dire>,
NAME=<name>;
Example 1. Data type
ZICI:WKS,::TIME=01-00,PTYPE=DA,PNBR=1,NBR=255;
The parameters for the command WKS are requested:
MODE=DATA;
The command calendar makes a safecopy of the data files every night at 01:00 a.
m.
Example 2. Archive type
ZICI:WKS,::TIME=01-00,PTYPE=DA,PNBR=1,NBR=255;
The parameters for the command WKS are requested:
MODE=ARCHIVE;
The command calendar makes a safecopy of the changed files every night at 01:00 a.m.
Example 3. Full type
If the command calendar is used for making a fallback of the entire software build, do not define an
existing file or directory name for the FB build in the command. If you want to use an existing name,
delete it from the Winchester disk before executing the command.
In the following example, the delete command of the existing fallback is added to the calendar before the
actual fallback command and a sufficient amount of time is reserved for the deleting operation. The
command calendar deletes the existing
fallback build every night at 01:00 a.m. and makes a safecopy of the entire software build every night at
02:00 a.m.
Deleting the existing fallback:
ZICI:WQD,::TIME=01-00,PTYPE=DA,PNBR=1,NBR=255;
The parameters for the command WKS are requested:
DIRE=<fallback directory>:MAFILE,::;
Making a new fallback:
ZICI:WKS,::TIME=02-00,PTYPE=DA,PNBR=1,NBR=255;
The parameters for the command WKS are requested:
MODE=FULL,DIRE=<fallback directory>,NAME=<fallback
name>;
2. Test the task execution of the command calendar (ICT).
ZICT;
Further information:
With the ZICL command you can list the command calendar tasks.
3. Check that the fallback is successfully completed by displaying the log file of the fallback (WKP).
ZWKP:<fallback type>:<execution parameters>;
Expected outcome
The fallback is successfully completed when no errors occur during the procedure.
Unexpected outcome
If there are errors, you must do the fallback again.
Check the usability of the copy in the supplementary information field of the alarm.
For more information, see Expected/unexpected results.
4. Check the states of the databases (DBS).
The states of the databases BSDATA and OEDATA should be normal or dumping. The state of the database
EQUIPM in the spare unit should be abnormal.
Further information:
You can delete a command calendar task with the ICD command.
Below is a captured screen of a command calendar using the ZICL;
< ZICL;
LOADING PROGRAM VERSION 6.2-0
BSC3i XXXXBSC01 2009-02-17 11:53:51
ID CMND CFILE QUE USER DATE TIME NBR PNBR PTYPE ALARM
=================================================================
===========
1 WQD - TIM AWSRDC 2009-02-18 01:00 FOREV 1 DAY
2 WKS - TIM AWSRDC 2009-02-18 02:00 FOREV 1 DAY
COMMAND EXECUTED


Alarm 2205 ET2 Failure
Definition:
In the ET plug-in unit a fault has been detected in the RAM or in the hardware. If the fault is in the RAM,
the check sum of a load module in the RAM has changed, or the check sum of a program located in the
ROM has changed.
Example:
XXXXXXXXX BCSU-4 SWITCH 2008-08-13 11:44:35.78
** ALARM ET-228 1A005-07 PXRECE
(1870) 2205 ET2 FAILURE
01 FF
END OF ALARMS CURRENTLY ON
Meaning:
1. type of fault:
00 read/write memory error detected by RAM test
01 check sum error in load module of RAM
02 check sum error in ROM program memory
03 daughter board is missing (ET2E)
2. when the functional unit is TCSM, index of ET plug-in unit. Otherwise FF
Instructions:
If the fault is in the RAM, replace the faulty plug-in unit, see Instructions for Replacing Plug-in Units.
If the daughter board is missing, install it.
Cancelling:
Do not cancel the alarm. The system cancels the alarm automatically when the fault has been corrected.
The SIBs provide the switching function to the destination FPC (see Figure 1). The SIBs create the switch
fabric for the router, providing up to a total of 320 million packets per second (320 Mpps) of forwarding.
Three SIBs are installed in the router. The SIBs are located at the center rear of the chassis in the slots
labeled SIB0 through SIB2.
SIBs are hot-insertable and hot-removable.



The wrist strap is connected to ground through a coiled retractable cable and 1 megaohm resistor, which
allows high-voltage charges to leak through but prevents a shock hazard when working with low-voltage
parts. Where higher voltages are present, extra resistance (0.75 megaohm per 250 V) is added in the path
to ground to protect the wearer from excessive currents; this typically takes the form of a 4 megohm
resistor in the coiled cable (or, more usually, a 2 megohm resistor at each end). Very cheap wrist straps do
not have conductive fabric and instead use the fabric to hold the metal plate against the skin, which can
result in reduced ESD protection over time as the metal corrodes.
Wrist straps in industry usually connect to Earth Bonding Points (part of the grounding system) via either a
4 mm plug or 10 mm press stud, whereas personally owned straps are likely to be connected to ground
via a crocodile clip.
In addition to wrist straps, ankle and heel straps are used in industry to bleed away
accumulated charge from a body. These devices are usually not tethered to earth
ground, but instead incorporate high resistance in their construction, and work by
dissipating electrical charge to special floor tiles. Such straps are used when
workers need to be mobile in a work area and a grounding cable would get in the
way, such as in an operating theatre.
If working on pinball machines, these items are classed as useless due to the
current being unable to dissipate in time. The recommended product for this is "LHIP" (as it is known in
the industry) or Left Hand In Pocket.
Wireless or Dissipative wrist straps are available, but they are widely considered as pseudoscientifichoax
products. The claims of the operating principles vary from "Ion Neutralization, Skin Effect, Point Discharge
and Corona Discharge Effect" to "Selglard electric halo principles".
[1][2]



I was tasked to fabricate a RJ-45 TO RS-232 Female adapter to be used as console cable to the ALU 7670
and this is what I did.
First is identify the pin configuration of the adapter, most of them are configurable and I got this sitewhich
you can purchase at a cheaper cost. The table below is how I did the configuration.

RJ-45 PIN COLOR DB-9 PIN SIGNAL
1 BLUE 8 CTS
2 ORANGE 7 RTS
3 BLACK 2 RxD
4 RED 3 TxD
5 GREEN 5 SG
6 YELLOW 4 DTR
7 BROWN 6 DSR
8 WHITE N/C





Pin configuration
RJ45 pin Wire color
1 Blue
2 Orange
3 Black
4 Red
5 Green
6 Yellow
7 Brown
8 White

DB9 cable. This does NOT follow the EIA-561 standard.
RJ45 DB9 Abbreviatio
n
Description
1 8 CTS Clear To
Send
2 6 DSR Data Set
Ready
3 2 RD Received
Data
4 5 GND Ground
5 5 GND Ground
6 3 TD Transmit
Data
7 4 DTR Data
Terminal
Ready
8 7 RTS Request To
Send
Cisco RJ45 to DB9 Serial Console Cable

The above pin configuration is design specifically for Alcatel-Lucent (ALU) 7670 RSP box. Other
application may not apply.
Below are steps in troubleshooting the BCSU of a defective plug-in unit. Read notes below for ESD
requirements
Example. Replacing a plug-in unit in BCSU-0
1. Check the computer unit working state.
ZUSI:BCSU,0;
2. If a unit is in working state WO, change the working state to SP. After the calls handled by the unit have
ended, its state changes automatically to SP-EX. Change the working state first to TE and then to SE.
ZUSC:BCSU,0:SP;
ZUSC:BCSU,0:TE;
ZUSC:BCSU,0:SE;
3. Switch off the cartridge power supply.
4. Remove the plug-in unit from the cartridge.
5. Check the interchangeability of the new plug-in unit.
6. Check the strappings of the new plug-in unit.
7. Insert the new plug-in unit.
8. Switch on the cartridge power supply.
9. Change the computer unit working state to TE.
ZUSC:BCSU,0:TE;
10. Start the total diagnosis of the unit.
ZUDU:BCSU,0;
11. Check the diagnostics results.
ZUDH:BCSU,0;
12. Change the computer unit working state to SP (or WO).
ZUSC:BCSU,0:SP;
13. Check the alarms.
ZAHO;
See figure below in inserting a plug-in unit











FEATURES:
Shielded cable to reduce noise.
Bantam Plugs molded to the cable to provide optimum durability.
MATERIALS:
Plugs: Nickel Plated Brass.
Main Cable: 4 Conductor Shielded Twisted Pair.
Breakout Cables: 2 Conductor Shielded Twisted Pair.
Wire Jackets and Insulators: PVC
Breakout: Molded PVC
RATINGS:
Voltage: Hands free usage in controlled voltage environments: 300 Vrms Max. For CE
compliance: not
intended for hand-held use at voltages above 33 Vrms/70 Vdc.
Current: 0.5 Amperes per conductor @ 25C Max.
Operating Temperature: -4F to +176F (-20C to +80C)
ORDERING INFORMATION: Model 6320-96
Standard Length: 96 Inches (2,43M)

Retrieving Active Users from the 1631 and 1671 DACs
The syntax commands are different when you want to retrieve active users from both DACS but they will
give the same results. The syntax for 1631 is below:
RTRVCID:[TID]:[CPORT]:[CTAG];
Example:
RTRV-CID:::;
The syntax for 1671 is below:
RTRV-STATUS:[TID]::[CTAG]:::[ACT=];
Example:
RTRV-STATUS::::::;
verview of BSC3i commissioning
These instructions are intended to be used in the commissioning of the system in the final location of the
BSC3i. They can be used with the ANSI or ETSI environment BSC3i 1000/2000 variants. (For information on
the commissioning of BSC3i 660, see Commissioning BSC3i in Nokia BSC/TCSM S11.5 Product
Documentation.)
Prerequisites for the successful commissioning according to these instructions are that:
the BSC has passed the factory acceptance tests
the installation has to be accepted
at least the files associated with the configuration are ready on the
hard disks of the BSC
the site has been built and prepared according to Nokia BSC Base
Station Controller, Rel. S12, Site Documentation for BSC3i
in a two-cabinet configuration, the cabling has been done during the
installation phase
All the software that belongs to the BSC must be ready on the hard disks of the system before starting the
commissioning tests. If there is newer SW available than what is installed in the BSC disk, the BSC must be
commissioned with the same SW that is installed on the disks. The newer SW is installed before the
integration of the BSC.
In the final BSC site the tests which, according to the test logs delivered with the hardware, have already
been performed at the test field of Nokia Corporation, do not necessarily have to be performed.
The purpose of the commissioning tests is to ensure that the BSC will operate correctly in the GSM
network. When the commissioning tests have been performed in an acceptable manner, the BSC can be
taken into
traffic. Depending on the configuration, the commissioning of BSC3i 1000/2000 takes around 3-5
working days.

CMM replace procedure
a) Ensure all cables connected to the CMM are properly labeled before disconnecting.
b) Press and hold the reset button (Alarm Cutoff Pushbutton) on the standby CMM until blue hot swap
light comes on momentarily (see figure below), disconnect cables, unlatch the card and then extract the
card from the chassis.
c) Insert the replacement CMM in the chassis and re-connect the cables.
d) Wait for the CMM to boot up and be ready.

CMM front panel picture



















Nokia BSC3i Displaying Command History Logs
Command Syntax:
ZIGO;
Description:
Display command history logs
Results:
< ZIGO;
LOADING PROGRAM VERSION 5.2-0
/* TCSMBSC01 BSC3i ENGINE 2010-05-05 12:01:52 */
/* 1 TCSMBSC01 BSC3i VTP-29 SESSION=47503 USERID=ENGINE STARTED 2010-05-05 00:35:49 */
EAO:BTS=1&&248;
/* 3 SESSION=47503 USERID=ENGINE 2010-05-05 00:35:50 */
/* 4 EAO:BTS=1&&248; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47503 USERID=ENGINE 2010-05-05 00:37:10 */
/* 2 TCSMBSC01 BSC3i VTP-29 SESSION=47503 USERID=ENGINE ENDED 2010-05-05 00:37:56 */
/* 1 TCSMBSC01 BSC3i VTP-15 SESSION=47511 USERID=ENGINE STARTED 2010-05-05 01:19:42 */
DMI::::;
/* 3 SESSION=47511 USERID=ENGINE 2010-05-05 01:19:43 */
/* 4 DMI::::; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47511 USERID=ENGINE 2010-05-05 01:19:43 */
/* 2 TCSMBSC01 BSC3i VTP-15 SESSION=47511 USERID=ENGINE ENDED 2010-05-05 01:19:46 */
/* 1 TCSMBSC01 BSC3i VTP-28 SESSION=47513 USERID=ENGINE STARTED 2010-05-05 01:27:14 */
EEO:ALL;
/* 3 SESSION=47513 USERID=ENGINE 2010-05-05 01:27:15 */
/* 4 EEO:ALL; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47513 USERID=ENGINE 2010-05-05 01:27:15 */
/* 2 TCSMBSC01 BSC3i VTP-28 SESSION=47513 USERID=ENGINE ENDED 2010-05-05 01:27:17 */
/* 1 TCSMBSC01 BSC3i VTP-24 SESSION=47523 USERID=ENGINE STARTED 2010-05-05 02:17:33 */
DTI::::;
/* 3 SESSION=47523 USERID=ENGINE 2010-05-05 02:17:34 */
/* 4 DTI::::; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47523 USERID=ENGINE 2010-05-05 02:17:34 */
/* 2 TCSMBSC01 BSC3i VTP-24 SESSION=47523 USERID=ENGINE ENDED 2010-05-05 02:17:36 */
/* 1 TCSMBSC01 BSC3i VTP-26 SESSION=47530 USERID=ENGINE STARTED 2010-05-05 03:08:17 */
DSB;
/* 3 SESSION=47530 USERID=ENGINE 2010-05-05 03:08:19 */
/* 4 DSB; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47530 USERID=ENGINE 2010-05-05 03:08:19 */
/* 2 TCSMBSC01 BSC3i VTP-26 SESSION=47530 USERID=ENGINE ENDED 2010-05-05 03:08:21 */
/* 1 TCSMBSC01 BSC3i VTP-20 SESSION=47532 USERID=ENGINE STARTED 2010-05-05 03:11:40 */
EEI:;
/* 3 SESSION=47532 USERID=ENGINE 2010-05-05 03:11:41 */
/* 4 EEI:; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47532 USERID=ENGINE 2010-05-05 03:11:43 */
/* 2 TCSMBSC01 BSC3i VTP-20 SESSION=47532 USERID=ENGINE ENDED 2010-05-05 03:11:45 */
/* 1 TCSMBSC01 BSC3i VTP-29 SESSION=47533 USERID=ENGINE STARTED 2010-05-05 03:16:57 */
ESI;
/* 3 SESSION=47533 USERID=ENGINE 2010-05-05 03:16:58 */
/* 4 ESI; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47533 USERID=ENGINE 2010-05-05 03:16:58 */
/* 2 TCSMBSC01 BSC3i VTP-29 SESSION=47533 USERID=ENGINE ENDED 2010-05-05 03:16:59 */
/* 1 TCSMBSC01 BSC3i VTP-23 SESSION=47534 USERID=ENGINE STARTED 2010-05-05 03:17:55 */
EQO:BTS=1&&248:IDE;
/* 3 SESSION=47534 USERID=ENGINE 2010-05-05 03:17:57 */
/* 4 EQO:BTS=1&&248:IDE; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47534 USERID=ENGINE 2010-05-05 03:18:00 */
/* 2 TCSMBSC01 BSC3i VTP-23 SESSION=47534 USERID=ENGINE ENDED 2010-05-05 03:18:04 */
/* 1 TCSMBSC01 BSC3i VTP-21 SESSION=47539 USERID=ENGINE STARTED 2010-05-05 03:36:09 */
ERO:BTS=1&&310;
/* 3 SESSION=47539 USERID=ENGINE 2010-05-05 03:36:10 */
/* 4 ERO:BTS=1&&310; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47539 USERID=ENGINE 2010-05-05 03:36:25 */
/* 2 TCSMBSC01 BSC3i VTP-21 SESSION=47539 USERID=ENGINE ENDED 2010-05-05 03:36:31 */
/* 1 TCSMBSC01 BSC3i VTP-22 SESSION=47545 USERID=ENGINE STARTED 2010-05-05 04:17:01 */
OLT;
/* 3 SESSION=47545 USERID=ENGINE 2010-05-05 04:17:02 */
/* 4 OLT; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47545 USERID=ENGINE 2010-05-05 04:17:02 */
/* 2 TCSMBSC01 BSC3i VTP-22 SESSION=47545 USERID=ENGINE ENDED 2010-05-05 04:17:03 */
/* 1 TCSMBSC01 BSC3i VTP-15 SESSION=47555 USERID=ENGINE STARTED 2010-05-05 05:17:23 */
OLU::D:;
/* 3 SESSION=47555 USERID=ENGINE 2010-05-05 05:17:24 */
/* 4 OLU::D:; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47555 USERID=ENGINE 2010-05-05 05:17:24 */
/* 2 TCSMBSC01 BSC3i VTP-15 SESSION=47555 USERID=ENGINE ENDED 2010-05-05 05:17:25 */
/* 1 TCSMBSC01 BSC3i VTP-27 SESSION=47568 USERID=ENGINE STARTED 2010-05-05 06:17:48 */
USI:;
/* 3 SESSION=47568 USERID=ENGINE 2010-05-05 06:17:49 */
/* 4 USI:; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47568 USERID=ENGINE 2010-05-05 06:17:49 */
/* 2 TCSMBSC01 BSC3i VTP-27 SESSION=47568 USERID=ENGINE ENDED 2010-05-05 06:17:50 */
/* 1 TCSMBSC01 BSC3i VTP-16 SESSION=47605 USERID=ENGINE STARTED 2010-05-05 11:52:14 */
IGO;
/* 3 SESSION=47605 USERID=ENGINE 2010-05-05 11:52:29 */
/* 4 IGO; */
/* 4c COMMAND EXECUTED */
/* 4c SESSION=47605 USERID=ENGINE 2010-05-05 11:52:29 */
IGO;
/* 3 SESSION=47605 USERID=ENGINE 2010-05-05 12:01:52 */
COMMAND EXECUTED

Vous aimerez peut-être aussi