Вы находитесь на странице: 1из 90

BSC & RXCDR Installation

and Configuration

1
Chapter 1
Site Preparation
Tool kits for installing GSM cellular equipment …………………………………………..4
Site requirements and consideration ………………………………………………………7
Power requirement s ……………………………………………………………………….. 9
Handling optical fibers ………………………………………………………………………10

Chapter 2
Installing the equipment

Overview …………………………………………………………………………………….13
Unpacking the equipment ………………………………………………………………….16
Anchoring the cabinet ………………………………………………………………………18
Preparing to connect DC power and earth cables ………………………………………19
BSCC2 interconnect panel …………………………………………………………………20
Power cable for +ve earth cabinet ……………………………………………………….. 21
Installing power supply modules …………………………………………………………. 23
Installing digital modules ………………………………………………………………….. 24
Installing BBBX modules ………………………………………………………………….. 24

Chapter 3
BSC & RXCDR configuration

Overview …………………………………………………………………………………….. 27
BSCC2 cabinet configuration ……………………………………………………………… 28
Cabinet description …………………………………………………………………………. 29

Chapter 4
BSC and RXCDR commissioning and Integration procedure
BSC commissioning and Integration example …………………………………………… 42
RXCDR commissioning …………………………………………………………………….. 71
RXCDR Integration …………………………………………………………………………. 84

2
Chapter 1

Site preparation

3
Tool kits for installing GSM cellular equipment
Introduction
Two tool kits are recommended for use when installing GSM cellular sites. Cellular tool kit
number one is for installation, and number two is for commissioning.

Tool kit one


The table lists the contents of cellular tool kit number one:

4
5
6
Tool kit two
The table lists the contents of cellular tool kit number two:

7
Site requirements and considerations

Introduction
The base site must meet the following criteria.

Structural requirements
There must be:
Clearance of at least 775 mm (30.5 in) in front of the equipment for operation and
maintenance purposes.
An overhead cable trough, mounted at least 150 mm (6 in) above the top of the tallest
cabinet.

Cabinet dimensions
BSSC cabinets both have the following dimensions:
Height 2096 mm
Width 712 mm
Depth (with door) 415 mm
Depth (without door) 400 mm

Operating environment
Temperature 0 _C to +50 _C (+32 _F to +122 _F).
Humidity 20 % to 80 % non-condensing relative humidity
(maximum 0.024 gram of water per gram of dry air).
Airborne particulate matter < 5 milligrams/1000 cubic feet of air.

The BSSC cabinet dissipates a maximum of 3100 watts when fully equipped.

Storage environment

Temperature –40 _C to +70 _C (–40_F to +158_F).


Humidity 10 % to 90 % non-condensing relative humidity

8
Diagram
The diagram shows the cabinet dimensions and mounting foot details:

9
Power requirements
Introduction
BSSC cabinets can operate from either positive or negative earth supplies (requested by
the customer and configured at initial installation|) at various voltages.

Positive earth BSSC cabinets


Positive earth BSSC cabinets operate from a –48 V or –60 V dc supply. The maximum
power requirements are:

GSM900 and EGSM900


• (–48 V) = 50 A.
• (–60 V) = 40 A.

DCS1800 and PCS1900


• (–48 V) = 50 A.
• (–60 V) = 40 A.

Backup power
BSSC cabinets can be connected to an external battery to provide a dc input power
backup for dynamic random access memory (DRAM) devices.

The DRAM backup maximum power requirement for each cabinet is:
• 4 A (maximum) at +27 V dc.

10
Handling optical fibres
Introduction
This section details the precautions necessary when handling optical fibers such as those
fitted in BSS equipment cabinets.

Protection
The ends of the optical fiber, whether or not terminated by a connector, must be kept
clean at all times. No dust or dirt must be allowed to contaminate the ends of the fiber or
the female connectors on the modules.
When a fiber is not connected, the protective caps must be fitted at all times to the ends
of the fiber and to all unused connectors on the modules.

Cleaning
To clean optical components, wipe them gently with a lint-free cloth soaked in a suitable
cleaning solution. Do not scratch the ends of the fibers.

Bending

All optical fibers have a minimum bend radius. This indicates the smallest circle that can
be formed from a loop of fibre that is how tight it can be coiled, looped or bent.
The minimum bend radii for the optical fibers used in Motorola BSS equipment cabinets
are as follows. Refer to the diagram on the next page.

• Polymer fibers (black outer sheath): 20 mm.


• Glass fibers (orange or green outer sheath): 30 mm.

If a fiber is bent tighter than the minimum bend radius, two effects are possible:

• Excessive light loss from the outside of the bend.


• Fiber fracture due to microscopic imperfections caused by bending. Light is
scattered and reflected by the fracture. The damage is permanent and is not
repaired by straightening the fiber.

11
Diagram

12
Chapter 2

Installing the equipment

13
Overview
Introduction
Follow the procedures and guidelines to install BSS equipment cabinets and their internal
and external interfaces.

In this section
Installation consists of the following steps, all of which are described in this section:

• Unpacking the equipment and inspecting for visible damage.


• Positioning and securing the cabinets as shown on the floor plan.
• Earthing the cabinets.
• Connecting dc power to the cabinets.
• Inserting modules into the cabinets.
• Connecting external equipment cabling such as transmits and receives antenna
cables and E1/T1 lines.
• Connecting the inter-cabinet fibre optic cables.

Cabinet types
This chapter describes the installation procedure for BSSC cabinets. The procedure is
the same for all cabinets except where otherwise indicated.

Delivery
Before the BSSC equipment is delivered, designate an area of the site where the heavy
freight and/or moving company can unload the equipment. The equipment must be
carefully delivered to the site with the dollies and padding required to move it from the
unloading area to the installation point.

14
Packaging
The cabinets are shipped in wooden crates.
Cabinets are shipped with the following items already installed:

• Cabinet interconnect panel.


• DC power distribution and alarm interface equipment.
• Module mounting shelves.
• Cooling fan assemblies.
• All intra-cabinet cabling.
• Digital modules.

The following items are shipped in separate cartons:

• Power supply modules (PSMs).

Lifting cabinets

BSSC cabinets are fitted with four lifting points, designed to accommodate M12 eyebolts,
built in to the top panels. These lifting points are fitted with plastic inserts to protect the
threads. Motorola kit number SWLN4648A contains four M12 eyebolts manufactured to
C.E. conformity, each with a safe weight loads of 400 kg and individually numbered. Only
eyebolts supplied in this kit must be used.

Before attempting to insert the eyebolts, visually check each one for any damage that
may have occurred in transit. If any damage is apparent, DO NOT USE; contact Motorola
for replacement.

1. Carefully remove the plastic insert from the M12 threaded lifting point.
2. Insert the eyebolt into the thread, ensuring that no cross-threading

3. Repeat the procedure until all four eyebolts have been correctly fitted.
4. When the lifting operation is complete, remove the eyebolts and refit the plastic inserts.

For continued use of eyebolts, there may be local regulations that govern the use of lifting
equipment and stipulate a test and/or examination regime. If the eyebolts are to be used,
ensure that all such regulations are met.

15
Site earthing
The cell site equipment must be earthed at the same common earth point as its power
source. Provision must be made for routing earthing lines into the site and to the cabinet
before installing the system cabinets. An earthing terminal (stud) is located on the
interconnect panel on top of each cabinet. Each cabinet must be earthed separately (not
daisy chained). For detailed site earthing information, refer to the site specific
documentation.

Transient/ lightning protection


E1/T1 lines connected to Motorola equipment have secondary transient protection as part
of the balanced-line interconnects board (BIB) or T43 board. The receive and transmit
antenna connections to the building must be fed through coaxial electromagnetic
protection (EMP) devices.

Torque values
Use the torque values listed below when tightening bolts:

Optical fibres
Refer to Handling optical fibres before installing fibre optic cables.

16
Unpacking the equipment
Introduction
Carry out the following procedure with reference to the diagram on the next page.

Procedure
To unpack a cabinet from its shipping crate:

1. Cut the recyclable plastic banding used to secure the wooden crate. Put the banding in
a place where it will not be lost.

2. Remove the eight metal clips that secure the lid of the crate using a claw hammer or a
similar levering device. Put the clips in a place where they will not be lost or
damaged.

3. Lift the lid free of the crate. Place the lid where it will not be damaged.

4. Remove the 12 metal clips that secure the sides of the crate using a claw hammer.
Put the clips in a place where they will not be lost or damaged.

5. Lift the sides free of the crate. Place the sides where they will not be damaged.

6. Carefully cut open the sealed barrier bag containing the cabinet.

7. Lift or slide the cabinet off the base of the crate.

8. Remove the desiccant bag from the cabinet.

9. Put all the clips in a bag and tie them together with the banding, desiccant bag, barrier
bag and the lid, sides and base of the cabinet.

10. Return the dismantled crate as advised by the in-country project manager.

11. Immediately after unpacking the equipment, inspect it for damage and report the
extent of any damage to the transport company.

17
Shipping crate
The diagram shows the cabinet shipping crate:

18
Anchoring the cabinet
Introduction
Mounting procedures must conform to local building codes and regulations. Consult the
site authorities before beginning an installation.

Procedure
To secure a cabinet to the floor:

1. Open the cabinet door.


2. For access to the bottom of the cabinet, remove the lower fan housing/air baffle
assembly (below the BSU shelf) by removing the four screws that secure it to the
cabinet frame; retain the screws for reassembly.
3. Carefully place the cabinet at its anchoring point as shown in the site plan.

4. Use the mounting foot of the cabinet as a template to mark the location of the four
mounting holes. All four anchoring positions must be used.

5. Move the cabinet away from the installation point. Drill holes for concrete mounting
anchors and fit them (Motorola suggests the RAWLNUT 1275).
6. Move the cabinet back to the installation point. Place an insulating shoulder washer
and then a flat washer onto each bolt. Loosely secure each cabinet to the anchors
using the bolts with washers (Motorola suggests M12 x 100 bolts for use with the
RAWLNUT 1275 anchors).
7. Tighten the bolts, ensuring that the cabinet remains vertical and level.
8. Replace the lower fan housing/air baffle assembly removed in step 2.

19
Preparing to connect dc power and earth cables
Introduction

The dc power distribution system within each cabinet, including all internal power cabling
and fuses, is factory assembled and tested.

The power requirements for the cabinets are listed before.

The power input and earth connectors are secured with M10 nuts.

Adequate means, for example a cable trough, must be provided for routing cables from
the main power source to the cabinet.

20
BSSC2 interconnect panel

The diagram shows the BSSC2 interconnect panel:

21
Power cables for +ve earth cabinets
Use the correct cable specified in the tables for the dc input power cable from the main
dc power source.

To connect dc power cables to a positive earth cabinet:

1. Ensure that the main power source output is switched off.

2. Connect the earth ground from the master ground bar to the earth stud on top of the
cabinet.

3. Connect the blue negative (–) dc power cable from the main dc power source to the
cabinet dc power connector assembly terminal marked VIN.

4. Connect the black positive (+) dc power cable from the main dc power source to the
cabinet dc power connector assembly terminal marked 0V.

5. Tighten the dc power and earth terminal set screws (M10).

22
Connecting dc input power and earth cables to the main
power source
Safety

Procedure
To connect the dc power cables to the main power source:

1. Ensure that all main dc power source output switches are switched off.

2. Ensure that all circuit breakers in the cabinet are switched off.

3. Use a digital voltmeter to ensure that power is not present.

4. Connect the positive lead of the input dc power cable to the positive terminal of the
main dc power supply.

5. Connect the negative lead of the input dc power cable to the negative terminal of the
main dc power supply.

6. Do not apply power to the cabinet at this point in the procedure.

23
Installing power supply modules
Introduction
The following types of power supply modules (PSMs) are fitted:

• +ve earth BSSC2: Integrated power supply module (IPSM).

Before installing power supply modules, refer to the site specific documentation to
determine the following:

• The number of power supply modules to be installed.


• The positions in which the power supplies modules are to be installed.

Procedure
To install the power supply modules:

1. Locate and unpack the power supply modules.

2. If the cabinet is delivered with the digital modules already installed, two transportation
panel fillers are fitted to the digital shelf to prevent the modules from falling out of the
shelf in transit. Remove these by releasing the clips at the top and bottom, and
replace them with blanking plates, before proceeding.

3. Mount each power supply module (and power converter if fitted) in the BSU/RXU shelf
assembly according to the configuration information in the site specific
documentation.

4. Pull each PSM forward by about 25 mm (1 in) to unseat it.

24
Installing digital modules
Introduction

Before installing digital modules, refer to the site specific documentation to determine the
following:
• The number of digital modules to be installed.
• The positions in which the digital modules are to be installed.

Factory installation
Some cabinets are delivered with all digital modules already installed. If this is the case,
perform only those steps in the procedure that relate to cabling.
If a digital module is found to be unserviceable, return it to Motorola in the container
provided in the PCB transportation boxes kit (SWBN4831A).

Installing BBBX modules

The battery backup board (BBBX) module has no backplane connections, and can
therefore be installed in any available slot, provided that the associated cables can reach
it.
The cables are factory installed in the cabinet, but must be connected to the BBBX
module on site.

Cabling is as follows:

25
Procedure

To install the digital modules:

1. Locate and unpack the full- and half-size digital modules. Place the modules on an
antistatic bench mat. If an antistatic bench mat is not available place each module on
the antistatic bag from which it was removed.

2. Locate a PIX module. If no PIX module is present go to step 6.

3. Locate the PIX interconnect cables that are tie-wrapped to the BSU/RXU shelf. If one
PIX module is present, cut the tie-wrap for the cable labeled PIX0. If two PIX modules
are present, cut the tie-wraps for both cables (labeled PIX0 and PIX1).

4. Insert the first PIX module into slot 16, ensuring that the module is firmly seated in the
backplane connector. Insert the second PIX module (if present) into slot 15, making
sure that the module is firmly seated in the backplane connector.

5. Connect the cable PIX0 to the PIX module in slot number 16 and tighten the two
captive screws to secure the cable to the PIX module. Connect the cable PIX1 to the
PIX module in slot 15 (if present) and tighten the two captive screws to secure the
cable to the PIX module.

6. Mount the remaining modules in the BSU/RXU shelf assembly according to the
configuration information in the site specific documentation and the diagrams on the
BSCC2 configuration chapter 3.
7. Make sure that the switch on the front of each digital module is set to the down
(disabled) position.

8. using a non-permanent marker, note the module arrangement used for this BSU shelf
on the label affixed to the inside of the cabinet door.

26
Chapter 3

BSC & RXCDR Configuration

27
Overview
Introduction
This chapter is a mechanical and electrical description of the base station system control
(BSSC) cabinet.
A BSSC cabinet can be configured as:

• Base station controller (BSC) containing digital hardware modules configured to


control the radio subsystem.

• Remote transcoder (RXCDR) containing digital hardware modules configured to


provide an interface between the BSC and mobile switching centre (MSC).

• A combination of the BSC and RXCDR functions.

The difference between the BSC and RXCDR configurations is in the complement of
digital modules on the backplane.

The information in this section applies to all three of the above configurations and, unless
otherwise indicated, to GSM, extended GSM (EGSM), DCS1800 and PCS1900 systems.

Cabinet types
The earlier BSSC cabinet is the same as the BSSC2 except in its handling of power
distribution and alarms..

The BSSC and BSSC2 cabinets can be powered by a positive earth (–48 V or –60 V) or
negative earth (+27 V) supply (this is requested by the customer and configured during
initial installation). The only difference in the cabinets is the inclusion of fan power
converters in the –48/–60 V versions of the BSSC to derive +27 V power for the cooling
fans.

28
BSSC2 cabinet configuration
Configuration options

BSC configuration
The BSSC2 cabinet configured as a BSC contains at least one base station unit (BSU)
shelf assembly. This assembly is in the lower portion of the cabinet; the upper portion of
the cabinet can contain a second BSU configured either as a separate BSC or as an
expansion of the BSU on the lower shelf.
Transcoding can be performed at the BSC. In this case, the upper portion of the cabinet
contains a separate transcoder unit (RXU) shelf assembly instead of a second BSU.
The top shelf contains the power distribution unit (PDU) which consists of a distribution
alarm board and a dc circuit breaker panel.

RXCDR configuration

The BSSC2 cabinet configured as an RXCDR contains at least one RXU shelf assembly,
located in the lower portion of the cabinet. A second RXU can be located in the upper
portion of the cabinet. The top shelf contains the PDU, which consists of a distribution
alarm board and a dc circuit breaker panel.

BSU and RXU shelves

Each shelf in a cabinet can be configured as a separate network element.


The BSU and RXU shelf assemblies consist of:
• A backplane.
• Two vertical slot module shelves.
• A three compartment shelf.
The lower portion of the two vertical slot shelves holds 26 full size digital modules in slots
numbered L0 to L28. The upper portion of the shelf holds 28 half size digital modules in
slots numbered U0 to U28.
There are three compartments at the bottom of the BSU/RXU shelf assembly, with slide-
in mountings for power supply modules. The left compartment is for an optional
redundant power supply module.

Location
The BSC can be located at the same site as the radio (collocated). They can also share
the same cabinet. Alternatively, the BSC at one site can control several radio subsystems
at remote sites.
The transcoding function of the BSS can be located either:
• With the BSC.
• Remotely between the BSC and the MSC.
Locating the transcoding function between the BSC and the MSC is the most common
option and is referred to as the RXCDR.

Equipment
The exact digital hardware module equipment in the cabinet depends on the BSS
application. Chapter 2 of this manual contains descriptions of the digital hardware
modules used in the BSSC2 cabinet.

29
Cabinet description: external
Introduction
This section describes the external appearance of the BSSC2 cabinet.

External view
The diagram shows an external view of the BSSC2 cabinet:

External features
The cabinet door is hinged on the left side of the cabinet, and has four air vents with
grilles:

• Intake vents have air filters.

• Exhaust vents have exhaust fans fitted behind the vents.

All connections to the cabinet are at the interconnect panel, which is on top of the
cabinet. This panel also has feed-through tubes for routeing fibre optic inter-cabinet
cables in and out of the cabinet. All cabinets are RF/EMI shielded.

30
Cabinet description: internal
Introduction
This section describes the internal appearance of the BSSC2 cabinet.

Internal view
The diagram shows an internal view of the BSSC2 cabinet:

Internal units
As shown in the internal view on the previous page, the BSSC2 can contain two card
cages, each with one full-size and one half-size digital board shelf. A card cage can
contain either a BSU or an RXU. All cabinets contain a power distribution unit PDU and a
fan cooling system.
Card cages are equipped according to the required function of the cabinet, as shown in
the table:

31
Base station unit shelf assembly
Overview
A base station unit (BSU) shelf assembly consists of:
• A backplane.

• Two vertical-slot module shelves containing the required digital modules.

• The upper shelf holds half size digital modules


.
• The lower shelf holds full size digital modules.

• A three-compartment shelf for the power supply modules.

Every cabinet must be fitted with the following digital cards:


• Two bus termination cards (BTC).

• One local area network extender (LANX) module.

All other digital modules are optional, and their inclusion depends upon the cabinet
configuration.

BSC numbering

In a BSC, BSUs are numbered from 0 forward using the sixteen positions (0 to F hex)
rotary switch on the LANX module. This rotary switch sets the BSU LAN address.

32
BSU shelf
The diagram shows a base station unit shelf:

33
Shelf module fit

34
Ventilation

Blanking plates are inserted in all unused full size and power supply module slots to
assist with the correct airflow and ventilation.

Backplane connectors

35
Remote transcoder unit shelf assembly
Overview
A remote transcoder unit (RXU) shelf assembly consists of:
• A backplane.
• Two vertical-slot module shelves containing the required digital modules:
• The upper shelf holds half size digital modules.
• The lower shelf holds full size digital modules.
• A three-compartment shelf for the power supply modules.

Every cabinet must be fitted with:


• Two bus termination cards (BTC).
• One local area network extender (LANX) module.
All other digital modules are optional, and their inclusion depends upon the cabinet
configuration.

BSC numbering
In a BSC, RXUs are numbered from 0 forward using the sixteen position (0 to F hex)
rotary switch on the LANX module. This rotary switch sets the RXU’s LAN address.

RXU shelf

36
Remote transcoder unit shelf assembly

37
Ventilation
Blanking plates are inserted in all unused full size and power supply module slots to
assist with the correct airflow and ventilation.

Backplane connectors

Power distribution unit components


Introduction
This section describes the cabinet dc power distribution arrangements.

Overview
The power distribution unit (PDU) is located on the top shelf of the cabinet and:
• Distributes dc power throughout the cabinet.
• Provides an alarm interface.

It consists of:
• A distribution alarm board (DAB).
• A circuit breaker panel containing seven dc circuit breakers.

38
Input power
DC input power is applied at the interconnection panel on top of the cabinet and is routed
to:
• The VIN bus bar.
• The earth (GND) bus bar in the PDU.

A second bus bar obtains +27 V power from:


• The integrated power supply modules (IPSMs) in the lower BSU in positive earth
(–48/–60 V) cabinets.
• The VIN and GND bus bars, via bus bar links, in negative earth (+27 V) cabinets.

Circuit breakers
The seven circuit breakers distribute power to units within the cabinet.

• CB1 (30 A) provides +27 V to the DAB.


• CB5 to CB10 (60 A) provide:
• –48/–60 V to the IPSMs in a positive earth cabinet.
• +27 V to the EPSMs in a negative earth cabinet.

Fan cooling system


Overview

Each fan tray assembly contains three exhaust fans. Cabinet baffling divides the cabinet
cooling system into upper and lower cabinet cooling sub-systems.
The cooling system, in conjunction with the correct use of shelf airflow deflectors,
provides adequate cooling for all cabinet equipment.
Each fan has a fan stall sensor which is connected to alarm circuits in the DAB through
connector PC5.

Location
The fan cooling system is mounted directly below each BSU/RXU shelf assembly.

Requirements
Power for the fans is derived from the +27 V bus bar and is routed to the +27 V terminals
on the DAB, then from connector PC9 on the DAB to the fans.

39
Interconnect panel
Overview
The interconnect panel is mounted on the top of the cabinet and provides connections
for:
• DC input power.
• E1/T1 line interconnects modules.
• Customer defined alarm equipment input/output.
• +27 V battery back-up input for DRAM.

The Interconnect panel has feed-through tubes for routeing fibre optic inter-cabinet
cables into and out of the cabinet.

The E1/T1 line interconnection modules are:

• Type 43 (T43) interconnect boards.


• Balanced line interconnects boards (BIB).

Panel layout

40
Connectors

41
Chapter 4

BSC & RXCDR Commissioning and Integration


Example

42
BSC Commissioning and Integration example

BSC Commissioning and Integration procedure

• power on the main DC C.B from rectifier belongs to that BSC


• Make sure that the switch on the front of each digital module is set to the down (disabled)
position.
• power on all DC C.B in BSC after that be sure all power supply modules working and
not have any alarm and all fans work
• Rest all BSC cards (full and half modules)
• connect your PC to master GPROC (GPROC # 20)
• change to emon prompt by (1- chg_l , 2- 3stooges, 3- 4beatles) three password to be at
level 3 then Ctrl+N to go to emon prompt
• Send DTE address for that BSC (you must know the DTE address from database in
OMC). After that make check if DTE address you sent it is accepted or nor by using
command disp_dte
• If the DTE you sent it is the same as in OMCR and OML between BSC and OMCR not
have any problem (B.U at OMCR), BSC must start download object code, if not check the
link between BSC and OMCR or RXCDR.
• If download in progress it will be as below

MMI-RAM 0115 -> disp_dte

BSC DTE addresses:


Address #0: 602010215
Address #1: 602010215
Address #2: 602010215
Address #3: 602010215

OMCR DTE addresses:


Address #0: 60201003000141
Address #1: 60201003001142
Address #2: 60201003000061
Address #3: 60201003001062
Address #4: 60201003009999
Address #5: 60201003000100
Address #6: Zero length address
Address #7: Zero length address

CBC DTE address:


Address #0: Zero length address

BSC CBC DTE address:


Address #0: Zero length address

43
GPROC2_RAM:emon_0115 % obj
GPROC2_RAM:emon_0115 % obj

1-THIS COMMAND TO WATCH THE DOWNLOADING FOR OBJECT CODES AFTER THE
ESTALBISHING FOR THE CONNECTION BETWEEN THE BSC&OMC
Object Dv
Object
Name Version Date Time Checksum Size S Ty
Specific
======== =========== ========= ===== ========== ======== = ==
============
000 ex_ram 05.01.05.01 10-Oct-98 14:48 0x02236a25 00443830 1 01
f8
002 dbase 00.00.03.fd 01-Aug-99 22:33 0x06460bfa 01743916 1 03
ab09 0000
003 ex_nul 05.01.01.00 04-May-98 16:58 0x00007b06 00000426 2 01
f8
004 libboot 05.01.01.00 04-May-98 16:55 0x001421d2 00015092 1 01
f8
005 libcomn 05.01.00.05 31-Jul-97 14:44 0x000046d2 00000200 1 06
f8
006 ex_com 05.01.01.00 04-May-98 16:56 0x0010f6eb 00012339 2 01
f8
008 mcuboot 05.01.05.01 10-Oct-98 14:55 0x01da14c4 00262802 1 09
a7
012 rssboot 05.01.06.00 10-Dec-98 13:38 0x01a42ee7 00232867 1 12
a0
013 options 06.00.00.00 16-Mar-99 14:18 0x000211e2 00001144 1 04
016 cp_mtp3 05.01.05.00 25-Sep-98 15:16 0x0093c6fd 00114795 1 01
bf
017 ex_mtp 05.01.01.00 04-May-98 16:58 0x00376a78 00042406 1 01
bf
018 ex_dlsp 05.01.05.00 25-Sep-98 15:24 0x003cff50 00045111 2 01
f8
019 ex_lap 05.01.01.00 04-May-98 16:57 0x0025307c 00028502 2 01
ff
020 ex_tty 05.01.01.00 04-May-98 17:04 0x000ab6c6 00007456 2 01
f8
022 ex_ftr 05.01.01.00 04-May-98 16:56 0x0009b602 00007662 2 01
f8
023 ex_mtr 05.01.03.00 16-Jul-98 18:11 0x00535227 00060351 2 01
f8
024 fm_sdls 05.01.05.01 09-Oct-98 15:37 0x0025e089 00029279 2 01
f8
032 cp_rrsm 05.01.05.01 09-Oct-98 12:47 0x01487e91 00256428 1 05
b8
033 cp_ssm 05.01.05.04 28-Oct-98 15:20 0x014b7aa0 00263227 1 01
bf
034 cp_crm 05.01.05.01 09-Oct-98 12:27 0x01e74ac9 00381731 1 05
b8
035 cp_clm 05.01.05.00 25-Sep-98 15:10 0x0048f51d 00055721 2 01
bf
036 cp_cbs 05.01.01.00 04-May-98 16:48 0x0067149b 00081201 1 05
b8
048 rs_cfm 05.01.05.01 09-Oct-98 18:39 0x00468f44 00053660 1 07
b8

44
049 rs_ho 05.01.05.00 26-Sep-98 00:52 0x008d1066 00108489 1 07
b8
050 rs_lyr1 05.01.06.00 10-Dec-98 16:16 0x00c8d336 00149685 1 07
b8
051 rs_abis 05.01.05.00 26-Sep-98 00:47 0x007f4525 00096179 1 07
b8
052 rs_lyr2 05.01.01.00 04-May-98 23:27 0x00288a65 00033189 1 07
b8
063 fm_msm 05.01.01.00 04-May-98 17:57 0x003ad70d 00032629 1 09
b7
064 fm_sm 05.01.05.00 25-Sep-98 17:52 0x01223b5c 00215224 2 01
f8
065 mca_dsp 05.01.05.00 25-Sep-98 17:24 0x003aa9d8 00055935 2 01
f8
066 fm_ca 05.01.05.01 10-Oct-98 15:35 0x049cf763 00865670 2 01
f8
067 fm_rtrp 05.01.01.00 04-May-98 17:57 0x000b54c3 00008996 2 06
f8
068 fm_crtr 05.01.01.00 04-May-98 17:38 0x0009494a 00011557 2 06
f8
069 fm_gvp 05.01.01.00 04-May-98 18:08 0x0025b813 00028387 2 01
f8
070 fm_mvp 05.01.01.00 04-May-98 18:08 0x00102025 00008992 1 09
b7
071 fm_mca 05.01.05.01 10-Oct-98 15:07 0x01c626d0 00249575 1 09
b7
072 fm_sync 05.01.01.00 04-May-98 18:08 0x0025ac79 00020751 1 09
b7
074 fm_fcp 05.01.06.00 10-Dec-98 13:19 0x007768e7 00092605 2 01
f8
075 fm_ftp 05.01.06.00 10-Dec-98 16:32 0x0189650c 00311081 2 05
f8
076 fm_mmf 05.01.01.00 04-May-98 17:54 0x00301655 00036177 1 05
b8
077 fm_sap 05.01.03.00 17-Jul-98 20:36 0x00575e19 00066827 2 05
f8
078 fm_xbl 05.01.01.00 04-May-98 18:09 0x00214b99 00025145 2 01
ff
079 fm_mfcp 05.01.06.00 10-Dec-98 14:10 0x0049d4d8 00040865 1 17
b7
080 ip_ram 05.01.05.00 25-Sep-98 18:01 0x00879e82 00108700 2 01
f8
096 st_csp 05.01.05.01 09-Oct-98 18:41 0x001b8d9c 00020414 2 01
ff
097 st_ssp 05.01.05.00 26-Sep-98 01:07 0x000b23bf 00007980 2 05
b8
112 om_mmi 05.01.06.00 10-Dec-98 14:46 0x032d4940 00624049 2 05
f8
113 om_cm 05.01.06.00 10-Dec-98 16:15 0x035746e9 00642536 2 05
f8
114 om_agnt 05.01.05.01 09-Oct-98 16:07 0x006403ff 00077037 2 01
ff
116 om_coup 05.01.01.00 04-May-98 19:49 0x00132f6d 00014258 2 01
ff
117 ex_lmp 05.01.01.00 04-May-98 16:57 0x001953ae 00018849 2 01
f8

45
118 om_nmas 05.01.06.00 10-Dec-98 15:13 0x0259bbc8 00446027 2 01
ff
119 om_cba 05.01.01.00 04-May-98 18:31 0x00845fe5 00097137 1 01
bf
128 om_plp 05.01.01.00 04-May-98 22:12 0x00651901 00076009 2 01
ff
162 ccdsp 05.01.05.00 22-Sep-98 17:28 0x0062ec4a 00054052 1 13 b0
0003 0f00
163 orac_os 05.01.06.01 16-Dec-98 16:59 0x016070f6 00187167 1 15 b7
0405 0600
164 orac_eq 05.01.03.00 15-Jul-98 12:29 0x003491f9 00028628 1 15 b7
0003 0900
165 TSM_FEP 05.01.05.00 22-Sep-98 10:26 0x00224b2a 00018747 1 16 b0
0401 0f00
166 TSM_CC 05.01.05.01 08-Oct-98 10:27 0x004184dd 00036100 1 16 b0
0401 e500
170 a52 05.01.03.00 18-Jun-98 15:52 0x00017d34 00000914 1 19 b0
0000 0000
177 niu 05.01.05.00 22-Sep-98 13:16 0x00f619da 00156188 1 10 b7
0009 0100
178 ceb_020 05.01.00.07 08-Sep-97 15:37 0x00bdebab 00175754 1 02 fe
0002 0200
179 eq_0100 05.01.00.00 11-Apr-97 09:49 0x0019d72c 00024194 1 02 fe
0002 0100
180 pa4_009 05.01.00.00 11-Apr-97 14:35 0x00053a50 00003407 1 02 ba
0004 0090
181 ksw_021 05.01.00.00 11-Apr-97 14:16 0x003f44f0 00059939 1 02 f8
0002 0100
182 000202 05.01.00.05 25-Jul-97 13:12 0x0035c14b 00051546 1 02 f8
0002 0200
183 xc2_040 05.01.00.00 11-Apr-97 14:16 0x00426161 00043038 1 02 ff
0002 0400
184 cs1_ccc 05.01.06.00 10-Dec-98 10:34 0x00b1f3a9 00095884 1 18 b0
0503 0e20
185 cs1_eqc 05.01.06.00 10-Dec-98 10:34 0x0122d62e 00155351 1 18 b0
0503 0f20
186 dcb_010 05.01.00.00 11-Apr-97 11:23 0x00c994f2 00180951 1 02 fe
0101 0100
187 deq_010 05.01.00.00 11-Apr-97 11:06 0x00221686 00031421 1 02 fe
0102 0100
189 scb_020 05.01.00.08 19-Sep-97 16:58 0x00c7ddd6 00182027 1 02 fa
0201 0200
190 req_050 05.01.04.00 05-Aug-98 17:18 0x00247e3d 00034236 1 02 fa
0201 0500
191 000803 05.01.00.05 28-Jul-97 09:00 0x002a1597 00041292 1 02 b8
0008 0300
192 00080f 05.01.04.01 13-Aug-98 13:30 0x00408f73 00063404 1 02 b8
0008 0f00
194 a52 05.01.00.00 07-Aug-95 12:50 0x0001cdf8 00001607 1 08 b8
0e02 0000
200 sync_fw 05.01.00.fa 09-Apr-98 13:47 0x006465e8 00058258 1 10 b7
0005 0200
201 SCP 05.01.03.01 30-Jul-98 12:55 0x00a662c0 00157240 1 08 b8
0305 0500
202 eq_scu 05.01.05.01 08-Oct-98 11:06 0x0018d3da 00024686 1 08 b8
0303 0900

46
203 v14107 05.01.00.00 19-Sep-96 13:20 0x007efafe 00088363 1 02 f8
0002 0016
204 mcuop 05.01.05.01 06-Oct-98 13:48 0x00f838ee 00205300 1 02 ff
0005 0005
205 dspbt 05.01.00.0a 03-Nov-97 17:02 0x00172e4c 00023178 1 02 ff
0001 0005
206 dspop 05.01.06.00 04-Dec-98 14:09 0x008640d5 00122641 1 02 ff
0010 0015

Load version 05.01.06.01 Created 16-Mar-99 14:19

GPROC2_RAM:emon_0115 %
CA->KSW | --> TRANSITION COMPLETED FOR FOLLOWING KSW(s) <--

DEVICE_ID CAGE # SLOT # STATUS CAGES FED


--------- ------ ------ ------ ---------
KSW 1 1 0 1 1 Passed 1
KSW 1 0 0 1 27 Passed 1

MMI-RAM 0115 -> Waiting for System Initialization to complete.....

MMI-RAM 0115 -> Database display commands accepted.

MMI-RAM 0115 -> Initialization complete. All commands accepted.

After download completed start Commissioning and integration for the


BSC

Check database using

MMI-RAM 0115 -> disp_equip 0

GPROC 0 0 0
GPROC 1 0 0
GPROC 2 0 0
GPROC 3 0 0
GPROC 4 0 0
GPROC 5 0 0
GPROC 6 0 0
GPROC 7 0 0
BSP 0 0 0
BSP 1 0 0
MSI 0 0 0
MSI 1 0 0
MSI 2 0 0
MSI 3 0 0
MSI 4 0 0
MSI 5 0 0
MSI 6 0 0
MSI 7 0 0
MSI 8 0 0
MSI 9 0 0
MSI 10 0 0
MSI 11 0 0
MSI 12 0 0

47
MSI 13 0 0
MSI 14 0 0
MSI 15 0 0
MSI 16 0 0
MSI 17 0 0
MSI 18 0 0
MSI 19 0 0
MSI 20 0 0
MSI 21 0 0
MSI 22 0 0
MSI 23 0 0
MMS 0 0 0
MMS 0 1 0
MMS 1 0 0
MMS 1 1 0
MMS 2 0 0
MMS 2 1 0
MMS 3 0 0
MMS 3 1 0
MMS 4 0 0
MMS 4 1 0
MMS 5 0 0
MMS 5 1 0
MMS 6 0 0
MMS 6 1 0
MMS 7 0 0
MMS 7 1 0
MMS 8 0 0
MMS 8 1 0
MMS 9 0 0
MMS 9 1 0
MMS 10 0 0
MMS 10 1 0
MMS 11 0 0
MMS 11 1 0
MMS 12 0 0
MMS 12 1 0
MMS 13 0 0
MMS 13 1 0
MMS 14 0 0
MMS 14 1 0
MMS 15 0 0
MMS 15 1 0
MMS 16 0 0
MMS 16 1 0
MMS 17 0 0
MMS 17 1 0
MMS 18 0 0
MMS 18 1 0
MMS 19 0 0
MMS 19 1 0
MMS 20 0 0
MMS 20 1 0
MMS 21 0 0
MMS 21 1 0
MMS 22 0 0
MMS 22 1 0

48
MMS 23 0 0
MMS 23 1 0
MTL 1 0 0
MTL 2 0 0
MTL 3 0 0
MTL 4 0 0
RSL 10 0 0
RSL 11 0 0
RSL 12 0 0
RSL 13 0 0
RSL 14 0 0
RSL 15 0 0
RSL 26 0 0
RSL 27 0 0
RSL 29 0 0
OML 0 0 0
OML 1 0 0
GCLK 1 0 0
GCLK 0 0 0
KSW 0 0 0
KSW 1 0 0
KSW 0 1 0
KSW 1 1 0
EAS 0 0 0
CAGE 0 0 0
CAGE 1 0 0
CAB 0 0 0
SITE 0 0 0
SITE 10 0 0
SITE 11 0 0
SITE 12 0 0
SITE 13 0 0
SITE 14 0 0
SITE 15 0 0
SITE 26 0 0
SITE 27 0 0
SITE 29 0 0
XBL 0 0 0
XBL 1 0 0
XBL 2 0 0
PATH 10 0 0
PATH 11 0 0
PATH 12 0 0
PATH 13 0 0
PATH 14 0 0
PATH 15 0 0
PATH 26 0 0
PATH 27 0 0
PATH 29 0 0
LCF 0 0 0
LCF 1 0 0
LCF 2 0 0
LCF 3 0 0
LCF 4 0 0
LCF 5 0 0
LCF 6 0 0
LCF 7 0 0

49
Check all digital cards using command

MMI-RAM 0115 -> state 0

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
GPROC 0 0 0 B-U NO REASON 02/08 06:02:36 LCF 0 0 0
GPROC 1 0 0 B-U NO REASON 02/08 06:02:37 LCF 1 0 0
GPROC 2 0 0 B-U NO REASON 02/08 06:02:39 LCF 2 0 0
GPROC 3 0 0 B-U NO REASON 02/08 06:02:40 LCF 3 0 0
GPROC 4 0 0 B-U NO REASON 02/08 06:02:41 LCF 4 0 0
GPROC 5 0 0 B-U NO REASON 02/08 06:02:42 LCF 5 0 0
GPROC 6 0 0 B-U NO REASON 02/08 06:02:38 LCF 6 0 0
GPROC 7 0 0 D-U GPROC Not On LAN 02/08 06:02:45 None
BSP 0 0 0 B-U NO REASON 02/08 06:01:02 None
BSP 1 0 0 E-U NO REASON 02/08 06:01:11 None
MSI 0 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 1 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 2 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 3 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 4 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 5 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 6 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 7 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 8 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 9 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 10 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 11 0 0 B-U NO REASON 02/08 06:01:33 None
MSI 12 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 13 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 14 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 15 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 16 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 17 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 18 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 19 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 20 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 21 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 22 0 0 B-U NO REASON 02/08 06:02:23 None
MSI 23 0 0 B-U NO REASON 02/08 06:02:23 None
MMS 0 0 0 D-U Synch Loss OOS Timer 02/08 06:01:40 None
MMS 0 1 0 B-U NO REASON 02/08 06:01:40 None
MMS 1 0 0 B-U MMS Providing Clock 02/08 06:02:45 None
MMS 1 1 0 D-U Synch Loss OOS Timer 02/08 06:01:40 None
MMS 2 0 0 D-U Synch Loss OOS Timer 02/08 06:01:39 None
MMS 2 1 0 D-U Synch Loss OOS Timer 02/08 06:01:39 None
MMS 3 0 0 B-U NO REASON 02/08 06:01:38 None
MMS 3 1 0 D-U Synch Loss OOS Timer 02/08 06:01:38 None
MMS 4 0 0 D-U Synch Loss OOS Timer 02/08 06:01:37 None
MMS 4 1 0 D-U Synch Loss OOS Timer 02/08 06:01:38 None

50
MMS 5 0 0 D-U Synch Loss OOS Timer 02/08 06:01:37 None
MMS 5 1 0 D-U Synch Loss OOS Timer 02/08 06:01:37 None
MMS 6 0 0 D-U Synch Loss OOS Timer 02/08 06:01:36 None
MMS 6 1 0 D-U Synch Loss OOS Timer 02/08 06:01:37 None
MMS 7 0 0 D-U Synch Loss OOS Timer 02/08 06:01:36 None
MMS 7 1 0 D-U Synch Loss OOS Timer 02/08 06:01:36 None
MMS 8 0 0 D-U Synch Loss OOS Timer 02/08 06:01:35 None
MMS 8 1 0 D-U Synch Loss OOS Timer 02/08 06:01:35 None
MMS 9 0 0 D-U Synch Loss OOS Timer 02/08 06:01:34 None
MMS 9 1 0 D-U Synch Loss OOS Timer 02/08 06:01:35 None
MMS 10 0 0 D-U Synch Loss OOS Timer 02/08 06:01:34 None
MMS 10 1 0 D-U Synch Loss OOS Timer 02/08 06:01:34 None
MMS 11 0 0 D-U Synch Loss OOS Timer 02/08 06:01:33 None
MMS 11 1 0 D-U Synch Loss OOS Timer 02/08 06:01:34 None
MMS 12 0 0 D-U Synch Loss OOS Timer 02/08 06:02:30 None
MMS 12 1 0 D-U Synch Loss OOS Timer 02/08 06:02:31 None
MMS 13 0 0 D-U Synch Loss OOS Timer 02/08 06:02:30 None
MMS 13 1 0 D-U Synch Loss OOS Timer 02/08 06:02:30 None
MMS 14 0 0 D-U Synch Loss OOS Timer 02/08 06:02:29 None
MMS 14 1 0 D-U Synch Loss OOS Timer 02/08 06:02:29 None
MMS 15 0 0 D-U Synch Loss OOS Timer 02/08 06:02:28 None
MMS 15 1 0 D-U Synch Loss OOS Timer 02/08 06:02:29 None
MMS 16 0 0 D-U Synch Loss OOS Timer 02/08 06:02:28 None
MMS 16 1 0 D-U Synch Loss OOS Timer 02/08 06:02:28 None
MMS 17 0 0 D-U Synch Loss OOS Timer 02/08 06:02:27 None
MMS 17 1 0 D-U Synch Loss OOS Timer 02/08 06:02:27 None
MMS 18 0 0 D-U Synch Loss OOS Timer 02/08 06:02:27 None
MMS 18 1 0 D-U Synch Loss OOS Timer 02/08 06:02:27 None
MMS 19 0 0 D-U Synch Loss OOS Timer 02/08 06:02:26 None
MMS 19 1 0 D-U Synch Loss OOS Timer 02/08 06:02:26 None
MMS 20 0 0 D-U Synch Loss OOS Timer 02/08 06:02:25 None
MMS 20 1 0 D-U Synch Loss OOS Timer 02/08 06:02:26 None
MMS 21 0 0 D-U Synch Loss OOS Timer 02/08 06:02:25 None
MMS 21 1 0 D-U Synch Loss OOS Timer 02/08 06:02:25 None
MMS 22 0 0 D-U Synch Loss OOS Timer 02/08 06:02:24 None
MMS 22 1 0 D-U Synch Loss OOS Timer 02/08 06:02:24 None
MMS 23 0 0 D-U Synch Loss OOS Timer 02/08 06:02:23 None
MMS 23 1 0 D-U Synch Loss OOS Timer 02/08 06:02:24 None
MTL 1 0 0 E-U WAIT 02/08 06:02:45 None
MTL 2 0 0 D-U MMS Not In Service 02/08 06:02:45 None
MTL 3 0 0 D-U MMS Not In Service 02/08 06:02:45 None
MTL 4 0 0 D-U MMS Not In Service 02/08 06:02:45 None
RSL 10 0 0 D-U NO REASON 02/08 06:00:01 None
RSL 11 0 0 D-U MMS Not In Service 02/08 06:02:45 None
RSL 12 0 0 D-U MMS Not In Service 02/08 06:02:45 None
RSL 13 0 0 D-U MMS Not In Service 02/08 06:02:45 None
RSL 14 0 0 D-U MMS Not In Service 02/08 06:02:55 None
RSL 15 0 0 D-U MMS Not In Service 02/08 06:02:55 None
RSL 26 0 0 D-U MMS Not In Service 02/08 06:02:55 None
RSL 27 0 0 D-U NO REASON 02/08 06:00:01 None
RSL 29 0 0 D-U MMS Not In Service 02/08 06:02:55 None
OML 0 0 0 B-U NO REASON 02/08 06:02:45 None
OML 1 0 0 D-U MMS Not In Service 02/08 06:02:45 None
GCLK 0 0 0 B-U GCLK Phase Locking 02/08 06:02:45 None
GCLK 1 0 0 D-U NO REASON 02/08 06:00:01 None
KSW 0 0 0 B-U NO REASON 02/08 06:02:44 None
KSW 0 1 0 E-U NO REASON 02/08 06:00:53 None

51
KSW 1 0 0 B-U NO REASON 02/08 06:02:44 None
KSW 1 1 0 E-U NO REASON 02/08 06:01:45 None
TDM 0 0 0 B-U NO REASON 02/08 06:00:00 None
TDM 1 0 0 E-U NO REASON 02/08 06:00:00 None
LAN 0 0 0 B-U NO REASON 02/08 06:00:02 None
LAN 1 0 0 E-U NO REASON 02/08 06:02:43 None
EAS 0 0 0 B-U NO REASON 02/08 06:02:45 None
PBUS 0 0 0 B-U NO REASON 02/08 06:00:35 None
PBUS 0 1 0 E-U NO REASON 02/08 06:00:35 None
PBUS 1 0 0 B-U NO REASON 02/08 06:01:42 None
PBUS 1 1 0 E-U NO REASON 02/08 06:01:42 None
CBUS 0 0 0 B-U NO REASON 02/08 06:02:45 None
CBUS 0 1 0 E-U NO REASON 02/08 06:00:35 None
CBUS 1 0 0 B-U NO REASON 02/08 06:01:42 None
CBUS 1 1 0 E-U NO REASON 02/08 06:01:42 None
SBUS 0 0 0 B-U NO REASON 02/08 06:00:35 None
SBUS 0 1 0 E-U NO REASON 02/08 06:00:35 None
SBUS 1 0 0 B-U NO REASON 02/08 06:01:42 None
SBUS 1 1 0 E-U NO REASON 02/08 06:01:42 None
TBUS 0 0 0 B-U NO REASON 02/08 06:01:01 None
TBUS 0 1 0 E-U NO REASON 02/08 06:01:01 None
TBUS 1 0 0 B-U NO REASON 02/08 06:01:49 None
TBUS 1 1 0 E-U NO REASON 02/08 06:01:49 None
CAGE 0 0 0 B-U NO REASON 02/08 06:01:40 None
CAGE 1 0 0 B-U NO REASON 02/08 06:02:31 None
CAB 0 0 0 B-U NO REASON 02/08 06:00:00 None
SITE 0 0 0 B-U NO REASON 02/08 06:02:45 None
SITE 10 0 0 D-U NO REASON 02/08 06:00:00 None
SITE 11 0 0 D-U NO REASON 02/08 06:00:00 None
SITE 12 0 0 D-U NO REASON 02/08 06:00:00 None
SITE 13 0 0 D-U NO REASON 02/08 06:00:00 None
SITE 14 0 0 D-U NO REASON 02/08 06:00:00 None
SITE 15 0 0 D-U NO REASON 02/08 06:00:00 None
SITE 26 0 0 D-U NO REASON 02/08 06:00:00 None
SITE 27 0 0 D-U NO REASON 02/08 06:00:00 None
SITE 29 0 0 D-U NO REASON 02/08 06:00:00 None
XBL 0 0 0 B-U 64Kbps Link 02/08 06:02:45 None
XBL 1 0 0 D-U MMS Not In Service 02/08 06:02:45 None
XBL 2 0 0 D-U MMS Not In Service 02/08 06:02:45 None
PATH 10 0 0 D-U NO REASON 02/08 06:00:01 None
PATH 11 0 0 D-U NO REASON 02/08 06:00:01 None
PATH 12 0 0 D-U NO REASON 02/08 06:00:01 None
PATH 13 0 0 D-U NO REASON 02/08 06:00:01 None
PATH 14 0 0 D-U NO REASON 02/08 06:00:01 None
PATH 15 0 0 D-U NO REASON 02/08 06:00:01 None
PATH 26 0 0 D-U NO REASON 02/08 06:00:01 None
PATH 27 0 0 D-U NO REASON 02/08 06:00:01 None
PATH 29 0 0 D-U NO REASON 02/08 06:00:01 None

FUNCTION STATUS INFORMATION FOR LOCATION 0:


OPER STATES: E:Enabled B:Busy ADMIN STATES: E:Equipped

Last Transition Related


Function State Reason dd/mm hh:mm:ss Device
------------- ----- ------------------------- --------------- ---------
----

52
LCF 0 0 0 B-E NO REASON 02/08 06:02:36 GPROC 0 0
0
LCF 1 0 0 B-E NO REASON 02/08 06:02:37 GPROC 1 0
0
LCF 2 0 0 B-E NO REASON 02/08 06:02:39 GPROC 2 0
0
LCF 3 0 0 B-E NO REASON 02/08 06:02:40 GPROC 3 0
0
LCF 4 0 0 B-E NO REASON 02/08 06:02:41 GPROC 4 0
0
LCF 5 0 0 B-E NO REASON 02/08 06:02:42 GPROC 5 0
0
LCF 6 0 0 B-E NO REASON 02/08 06:02:38 GPROC 6 0
0
LCF 7 0 0 E-E NO REASON 02/08 06:00:01 None

END OF STATUS REPORT

Check OML links using command

MMI-RAM 0115 -> state 0 oml * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
OML 0 0 0 B-U NO REASON 02/08 06:02:45 None
OML 1 0 0 D-U MMS Not In Service 02/08 06:02:45 None

END OF STATUS REPORT

Check MTL links using command

MMI-RAM 0115 -> state 0 mtl * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
MTL 1 0 0 E-U WAIT 02/08 06:02:45 None
MTL 2 0 0 D-U MMS Not In Service 02/08 06:02:45 None
MTL 3 0 0 D-U MMS Not In Service 02/08 06:02:45 None
MTL 4 0 0 D-U MMS Not In Service 02/08 06:02:45 None

END OF STATUS REPORT

53
We notes that there is a problem in MTL 1 0 0 so we will check it again

MMI-RAM 0115 -> !!


state 0 mtl * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
MTL 1 0 0 E-U WAIT 02/08 06:02:45 None
MTL 2 0 0 D-U MMS Not In Service 02/08 06:02:45 None
MTL 3 0 0 D-U MMS Not In Service 02/08 06:02:45 None
MTL 4 0 0 D-U MMS Not In Service 02/08 06:02:45 None

END OF STATUS REPORT

We found that it’s the same state then we will check MMS dedicated for that MTL

MMI-RAM 0115 -> disp_equip 0 mtl 1 0

Device identification for this MTL: 1


First MMS identifier for this device: 1
Second MMS identifier for this device: 0
Timeslot on MMS where this device appears: 16

MMI-RAM 0115 -> state 0 mms 1 0

STATUS INFORMATION:
Device: MMS 1 0 0
Administration state: UNLOCKED
Operational state: BUSY
Reason code: MMS Providing Clock
Time of last transition: Mon Aug 2 06:02:45 1999
Related Device/Function: None
END OF STATUS REPORT

MMI-RAM 0115 -> disp_mms 0 1 0

Check MTL 1 0 equiped and defined in database or not

Start of Report:

Site: 0 MMS: 1 0
General Timeslot Usage:
TS Usage Device ID Type Site CIC Group CIC State
TS

0 UNAVAILABLE
1 OML 0 0 0 0
2 XBL 0 0 0 64K 0
3 CIC 9 0 IDLE
CIC 10 1 IDLE

54
CIC 11 2 IDLE
CIC 12 3 IDLE
4 CIC 13 0 IDLE
CIC 14 1 IDLE
CIC 15 2 IDLE
CIC 17 3 IDLE
5 CIC 18 0 IDLE
CIC 19 1 IDLE
CIC 20 2 IDLE
CIC 21 3 IDLE
6 CIC 22 0 IDLE
CIC 23 1 IDLE
CIC 24 2 IDLE
CIC 25 3 IDLE
7 CIC 26 0 IDLE
CIC 27 1 IDLE
CIC 28 2 IDLE
CIC 29 3 IDLE
8 CIC 30 0 IDLE
CIC 31 1 IDLE
CIC 33 2 IDLE
CIC 34 3 IDLE
9 CIC 35 0 IDLE
CIC 36 1 IDLE
CIC 37 2 IDLE
CIC 38 3 IDLE
10 CIC 39 0 IDLE
CIC 40 1 IDLE
CIC 41 2 IDLE
CIC 42 3 IDLE
11 CIC 43 0 IDLE
CIC 44 1 IDLE
CIC 45 2 IDLE
CIC 46 3 IDLE
12 CIC 47 0 IDLE
CIC 49 1 IDLE
CIC 50 2 IDLE
CIC 51 3 IDLE
13 CIC 52 0 IDLE
CIC 53 1 IDLE
CIC 54 2 IDLE
CIC 55 3 IDLE
14 CIC 56 0 IDLE
CIC 57 1 IDLE
CIC 58 2 IDLE
CIC 59 3 IDLE
15 CIC 60 0 IDLE
CIC 61 1 IDLE
CIC 62 2 IDLE
CIC 63 3 IDLE
16 MTL 1 0 0 0
17 CIC 65 0 IDLE
CIC 66 1 IDLE
CIC 67 2 IDLE
CIC 68 3 IDLE
18 CIC 69 0 IDLE
CIC 70 1 IDLE

55
CIC 71 2 IDLE
CIC 72 3 IDLE
19 CIC 73 0 IDLE
CIC 74 1 IDLE
CIC 75 2 IDLE
CIC 76 3 IDLE
20 CIC 77 0 IDLE
CIC 78 1 IDLE
CIC 79 2 IDLE
CIC 81 3 IDLE
21 CIC 82 0 IDLE
CIC 83 1 IDLE
CIC 84 2 IDLE
CIC 85 3 IDLE
22 CIC 86 0 IDLE
CIC 87 1 IDLE
CIC 88 2 IDLE
CIC 89 3 IDLE
23 CIC 90 0 IDLE
CIC 91 1 IDLE
CIC 92 2 IDLE
CIC 93 3 IDLE
24 CIC 94 0 IDLE
CIC 95 1 IDLE
CIC 97 2 IDLE
CIC 98 3 IDLE
25 CIC 99 0 IDLE
CIC 100 1 IDLE
CIC 101 2 IDLE
CIC 102 3 IDLE
26 CIC 103 0 IDLE
CIC 104 1 IDLE
CIC 105 2 IDLE
CIC 106 3 IDLE
27 CIC 107 0 IDLE
CIC 108 1 IDLE
CIC 109 2 IDLE
CIC 110 3 IDLE
28 CIC 111 0 IDLE
CIC 113 1 IDLE
CIC 114 2 IDLE
CIC 115 3 IDLE
29 CIC 116 0 IDLE
CIC 117 1 IDLE
CIC 118 2 IDLE
CIC 119 3 IDLE
30 CIC 120 0 IDLE
CIC 121 1 IDLE
CIC 122 2 IDLE
CIC 123 3 IDLE
31 CIC 124 0 IDLE
CIC 125 1 IDLE
CIC 126 2 IDLE
CIC 127 3 IDLE
End of Report.

56
Try to make INS for the MMS carry MTL 1 0

MMI-RAM 0115 -> chg_lev

Enter password for security level you wish to access:


Enter password for security level you wish to access:
Current security level is 3

MMI-RAM 0115 -> ins 0 mms 1 0


WARNING: This MMS is providing clock to the GCLK.
Continuing will result in the GCLK going to Set Frequency mode.
This command affects the OML and may impact the OMC-BSS session.
Are you sure (y=yes,n=no)? y

COMMAND ACCEPTED

MMI-RAM 0115 -> state 0 mms 1 0

STATUS INFORMATION:
Device: MMS 1 0 0
Administration state: UNLOCKED
Operational state: BUSY
Reason code: NO REASON
Time of last transition: Mon Aug 2 06:08:44 1999
Related Device/Function: None
END OF STATUS REPORT

MMI-RAM 0115 -> state 0 mtl 1 0

STATUS INFORMATION:
Device: MTL 1 0 0
Administration state: UNLOCKED
Operational state: ENABLED
Reason code: WAIT
Time of last transition: Mon Aug 2 06:08:44 1999
Related Device/Function: None
END OF STATUS REPORT

The problem still existing, must be from MSC

Check LANX cards and redundant

MMI-RAM 0115 -> state 0 lan * *


DEVICE STATUS INFORMATION FOR LOCATION 0:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
LAN 0 0 0 B-U NO REASON 15/09 12:45:58 None

57
LAN 1 0 0 E-U NO REASON 15/09 12:48:39 None

END OF STATUS REPORT

Remove the fiber from the first LAN card (0 0 0) then check the
redundant card

MMI-RAM 0115 -> state 0 lan * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
LAN 0 0 0 D-U NO REASON 15/09 17:12:57 None
LAN 1 0 0 B-U NO REASON 15/09 17:12:57 None

END OF STATUS REPORT

MMI-RAM 0115 -> !!


state 0 lan * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
LAN 0 0 0 E-U NO REASON 15/09 17:13:38 None
LAN 1 0 0 B-U NO REASON 15/09 17:12:57 None

END OF STATUS REPORT

MMI-RAM 0115 -> !!


state 0 lan * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
LAN 0 0 0 B-U NO REASON 15/09 17:13:54 None
LAN 1 0 0 D-U NO REASON 15/09 17:13:55 None

END OF STATUS REPORT

58
MMI-RAM 0115 -> state 0 lan * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
LAN 0 0 0 B-U NO REASON 02/08 06:00:02 None
LAN 1 0 0 E-U NO REASON 02/08 06:02:43 None

END OF STATUS REPORT

Notes if you didn’t give time after installing 1st fiber before remove 2nd one
BSC will make reset

Check all GPROC cards using command

MMI-RAM 0115 -> state 0 gproc * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
GPROC 0 0 0 B-U NO REASON 02/08 06:29:36 LCF 0 0 0
GPROC 1 0 0 D-U GPROC Not On LAN 02/08 06:29:41 None
GPROC 2 0 0 B-U NO REASON 02/08 06:29:36 LCF 1 0 0
GPROC 3 0 0 B-U NO REASON 02/08 06:29:37 LCF 2 0 0
GPROC 4 0 0 B-U NO REASON 02/08 06:29:37 LCF 3 0 0
GPROC 5 0 0 B-U NO REASON 02/08 06:29:38 LCF 4 0 0
GPROC 6 0 0 B-U NO REASON 02/08 06:29:38 LCF 5 0 0
GPROC 7 0 0 D-U GPROC Not On LAN 02/08 06:29:41 None

END OF STATUS REPORT

Check the process for each GPROC

MMI-RAM 0115 -> disp_proc 0


PROCESSOR STATUS INFORMATION FOR LOCATION 0:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped NE:Not Equipped

Related
Related
CPU# Processor Name State Reason Device
Function

59
---- --------------------- ----- ------------------------- ---------- -
---------

0113 GPROC 0 0 (LCF 0) B-U NO REASON MTL 1 0


N/A
0114 GPROC 1 0 (Off LAN) D-U GPROC Not On LAN N/A
N/A
0115 BSP 0 0 B-U NO REASON OML 0 0
N/A
XBL 0 0
N/A
0116 GPROC 2 0 (LCF 1) B-U NO REASON N/A
N/A
0117 GPROC 3 0 (LCF 2) B-U NO REASON SITE 13 0
N/A
SITE 26 0
N/A
0118 GPROC 4 0 (LCF 3) B-U NO REASON SITE 14 0
N/A
SITE 27 0
N/A
0119 BSP 1 0 E-U NO REASON N/A
N/A
011a GPROC 5 0 (LCF 4) B-U NO REASON SITE 10 0
N/A
0213 GPROC 6 0 (LCF 5) B-U NO REASON SITE 11 0
N/A
SITE 12 0
N/A
SITE 29 0
N/A
0214 GPROC 7 0 (Off LAN) D-U GPROC Not On LAN N/A
N/A

END OF STATUS REPORT

Check KSW cards and redundant

MMI-RAM 0115 -> state 0 ksw * *


DEVICE STATUS INFORMATION FOR LOCATION 0:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
KSW 0 0 0 B-U NO REASON 02/08 06:29:40 None
KSW 0 1 0 E-U NO REASON 02/08 06:31:23 None
KSW 1 0 0 B-U NO REASON 02/08 06:29:40 None
KSW 1 1 0 E-U NO REASON 02/08 06:31:05 None

END OF STATUS REPORT


MMI-RAM 0115 -> lock 0 ksw 0 0

60
COMMAND ACCEPTED

MMI-RAM 0115 -> state 0 ksw * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
KSW 0 0 0 E-L NO REASON 02/08 06:49:11 None
KSW 0 1 0 B-U NO REASON 02/08 06:49:11 None
KSW 1 0 0 E-U NO REASON 02/08 06:49:11 None
KSW 1 1 0 B-U NO REASON 02/08 06:49:11 None

END OF STATUS REPORT

MMI-RAM 0115 -> unlock 0 ksw 0 0

COMMAND ACCEPTED

0 MMI-RAM 0115 -> state 0 ksw 0

STATUS INFORMATION:
Device: KSW 0 0 0
Administration state: UNLOCKED
Operational state: ENABLED
Reason code: NO REASON
Time of last transition: Mon Aug 2 06:49:53 1999
Related Device/Function: None
END OF STATUS REPORT

MMI-RAM 0115 -> lock 0 ksw 0 1

COMMAND ACCEPTED

MMI-RAM 0115 -> !s


state 0 ksw 0 0

STATUS INFORMATION:
Device: KSW 0 0 0
Administration state: UNLOCKED
Operational state: BUSY
Reason code: NO REASON
Time of last transition: Mon Aug 2 06:50:31 1999
Related Device/Function: None
END OF STATUS REPORT

MMI-RAM 0115 -> unlock 0 ksw 0 1

COMMAND ACCEPTED

61
Check GCLK card and Redundant

MMI-RAM 0115 -> state 0 gclk * *


DEVICE STATUS INFORMATION FOR LOCATION 0:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
GCLK 0 0 0 B-U GCLK Phase Locked 02/08 06:33:04 None
GCLK 1 0 0 D-U NO REASON 02/08 06:26:53 None

END OF STATUS REPORT

Check redundant GCLCK

MMI-RAM 0115 -> lock 0 gclk 0 0


MMI-RAM 0115 -> lock 0 gclk 0 0 0
DUE TO FAULTY GCLK CARD ANOTHER REBOOT HABBNED

MMI-RAM 0115 -> Initialization complete. All commands accepted.

MMI-RAM 0115 -> state 0 gclk * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
GCLK 0 0 0 D-U GCLK is warming up 02/08 06:42:20 None
GCLK 1 0 0 D-U NO REASON 02/08 06:41:16 None

END OF STATUS REPORT

MMI-RAM 0115 -> disp_eq 0 gclk 0 0

Device identifier for the GCLK: 0


Cage number: 0
Slot number: 5
CLKX 0 (slot U7) present: YES
CLKX 1 (slot U6) present: NO
CLKX 2 (slot U5) present: NO

MMI-RAM 0115 -> state 0 site 11

STATUS INFORMATION:
Device: SITE 11 0 0
Administration state: UNLOCKED

62
Operational state: DISABLED
Reason code: NO REASON
Time of last transition: Mon Aug 2 06:41:16 1999
Related Device/Function: None
END OF STATUS REPORT

Check Alarms
MMI-RAM 0115 -> disp_act_alarm 0
Device Alarm Clear
(Subtype) Code Type Tag(hex) Date/Time Description
-------------------- ---- ---- -------- ---------- --------------------
-------
IAS 0 0 0 75 FMIC Untagged 08-02-1999 IAS +27V DAB Power
Fuse
06:42:21 Failure
CBUS 0 1 0 3 FMIC Untagged 08-02-1999 Local KSWX Clock
Fiber
06:42:31 Failure
CBUS 1 1 0 3 FMIC Untagged 08-02-1999 Local KSWX Clock
Fiber
06:43:06 Failure
EAS 0 0 0 16 FMIC Untagged 08-02-1999 AC POWER FAIL (0)
06:43:50
EAS 0 0 0 17 FMIC Untagged 08-02-1999 LORAIN RECT. MINOR
ALARM (1)
06:43:50
EAS 0 0 0 18 FMIC Untagged 08-02-1999 LORAIN RECT. MAJOR
ALARM (2)
06:43:50
EAS 0 0 0 19 FMIC Untagged 08-02-1999 BATTERY LOW
VOLTAGE(48v) (3)
06:43:50
EAS 0 0 0 20 FMIC Untagged 08-02-1999 HIGH TEMPERATURE (5)
06:43:50
EAS 0 0 0 21 FMIC Untagged 08-02-1999 FIRE ALARM (6)
06:43:50
EAS 0 0 0 22 FMIC Untagged 08-02-1999 DOOR OPEN (4)
06:43:50
MMS 3 1 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:46 Timer Expired
Estimated restoral-
10.0 secs
MMS 5 0 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:44 Timer Expired
Estimated restoral-
10.0 secs
MMS 5 1 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:44 Timer Expired
Estimated restoral-
10.0 secs

63
MMS 7 0 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:43 Timer Expired
Estimated restoral-
10.0 secs
MMS 7 1 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:43 Timer Expired
Estimated restoral-
10.0 secs
MMS 8 0 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:42 Timer Expired
Estimated restoral-
10.0 secs
MMS 8 1 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:43 Timer Expired
Estimated restoral-
10.0 secs
MMS 9 0 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:42 Timer Expired
Estimated restoral-
10.0 secs
MMS 9 1 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:42 Timer Expired
Estimated restoral-
10.0 secs
MMS 10 0 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:42:41 Timer Expired
Estimated restoral-
10.0 secs
MMS 15 1 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:43:36 Timer Expired
Estimated restoral-
10.0 secs
MMS 17 0 0 16 FMIC 00000001 08-02-1999 Synchronization Loss
OOS
06:43:35 Timer Expired
Estimated restoral-
10.0 secs
BSS 0 0 0 22 FMIC 00000001 08-02-1999 Trunk Critical
Threshold
06:43:48 Exceeded
MTL 1 0 0 0 FMIC Untagged 08-02-1999 Signalling Link
Failure
06:45:06
MTL 2 0 0 0 FMIC 00000001 08-02-1999 Signalling Link
Failure
06:43:48
MTL 3 0 0 0 FMIC 00000001 08-02-1999 Signalling Link
Failure
06:43:48

64
MTL 4 0 0 0 FMIC 00000001 08-02-1999 Signalling Link
Failure
06:43:48

Check all MSI cards using command

MMI-RAM 0115 -> state 0 msi * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
MSI 0 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 1 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 2 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 3 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 4 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 5 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 6 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 7 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 8 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 9 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 10 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 11 0 0 B-U NO REASON 02/08 06:42:40 None
MSI 12 0 0 B-U NO REASON 02/08 06:43:31 None
MSI 13 0 0 B-U NO REASON 02/08 06:43:31 None
MSI 14 0 0 B-U NO REASON 02/08 06:43:31 None
MSI 15 0 0 B-U NO REASON 02/08 06:43:31 None
MSI 16 0 0 B-U NO REASON 02/08 06:43:31 None
MSI 17 0 0 B-U NO REASON 02/08 06:43:31 None
MSI 18 0 0 B-U NO REASON 02/08 06:43:31 None
MSI 19 0 0 B-U NO REASON 02/08 06:43:30 None
MSI 20 0 0 B-U NO REASON 02/08 06:43:30 None
MSI 21 0 0 B-U NO REASON 02/08 06:43:30 None
MSI 22 0 0 B-U NO REASON 02/08 06:43:30 None
MSI 23 0 0 B-U NO REASON 02/08 06:43:30 None

END OF STATUS REPORT

65
Check MTL again after MSC finished the problem

MMI-RAM 0115 -> state 0 mtl * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
MTL 1 0 0 B-U NO REASON 15/09 15:11:15 None
MTL 2 0 0 E-U WAIT 15/09 13:55:54 None
MTL 3 0 0 E-U WAIT 15/09 12:48:42 None
MTL 4 0 0 E-U WAIT 15/09 12:48:42 None
MTL 5 0 0 E-U WAIT 15/09 12:48:42 None
MTL 6 0 0 E-U WAIT 15/09 13:58:13 None
MTL 7 0 0 E-U WAIT 15/09 12:48:42 None
MTL 8 0 0 E-U WAIT 15/09 13:55:54 None

END OF STATUS REPORT

Check TDM and redundant

MMI-RAM 0115 -> state 0 tdm * *


DEVICE STATUS INFORMATION FOR LOCATION 0:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
TDM 0 0 0 B-U NO REASON 15/09 12:45:56 None
TDM 1 0 0 E-U NO REASON 15/09 12:45:56 None

END OF STATUS REPORT

END OF STATUS REPORT

MMI-RAM 0115 -> !!


state 0 tdm * *

66
DEVICE STATUS INFORMATION FOR LOCATION 0:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
TDM 0 0 0 B-U NO REASON 15/09 12:45:56 None
TDM 1 0 0 E-U NO REASON 15/09 12:45:56 None

END OF STATUS REPORT

MMI-RAM 0115 -> !!


state 0 tdm * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
TDM 0 0 0 B-U NO REASON 15/09 12:45:56 None
TDM 1 0 0 E-U NO REASON 15/09 12:45:56 None

END OF STATUS REPORT

MMI-RAM 0115 -> state 0 ksw * *


DEVICE STATUS INFORMATION FOR LOCATION 0:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
KSW 0 0 0 B-U NO REASON 15/09 12:48:41 None
KSW 0 1 0 E-U NO REASON 15/09 12:46:31 None
KSW 1 0 0 B-U NO REASON 15/09 12:48:41 None
KSW 1 1 0 E-U NO REASON 15/09 12:47:39 None

END OF STATUS REPORT

MMI-RAM 0115 -> lock 0 ksw 0 0


COMMAND ACCEPTED

MMI-RAM 0115 -> lock 0 ksw 1 0

67
COMMAND ACCEPTED

MMI-RAM 0115 -> state 0 ksw * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
KSW 0 0 0 E-L NO REASON 15/09 17:17:17 None
KSW 0 1 0 B-U NO REASON 15/09 17:17:17 None
KSW 1 0 0 E-L NO REASON 15/09 17:17:24 None
KSW 1 1 0 B-U NO REASON 15/09 17:17:17 None

END OF STATUS REPORT

MMI-RAM 0115 -> state 0 tdm * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
TDM 0 0 0 D-U NO REASON 15/09 17:17:24 None
TDM 1 0 0 B-U NO REASON 15/09 17:17:17 None

END OF STATUS REPORT

MMI-RAM 0115 -> unlock 0 ksw 0 0


unlock 0 ks
COMMAND ACCEPTED

MMI-RAM 0115 -> w 1 0

COMMAND ACCEPTED

MMI-RAM 0115 -> state 0 ksw * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
KSW 0 0 0 E-U NO REASON 15/09 17:18:05 None
KSW 0 1 0 B-U NO REASON 15/09 17:17:17 None
KSW 1 0 0 E-U NO REASON 15/09 17:18:17 None

68
KSW 1 1 0 B-U NO REASON 15/09 17:17:17 None

END OF STATUS REPORT

MMI-RAM 0115 -> lock 0 ksw 0 1

COMMAND ACCEPTED

MMI-RAM 0115 -> lock 0 ksw 1 1

COMMAND ACCEPTED

MMI-RAM 0115 -> state 0 ksw * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
KSW 0 0 0 B-U NO REASON 15/09 17:18:51 None
KSW 0 1 0 E-L NO REASON 15/09 17:18:51 None
KSW 1 0 0 B-U NO REASON 15/09 17:18:51 None
KSW 1 1 0 E-L NO REASON 15/09 17:18:56 None

END OF STATUS REPORT

MMI-RAM 0115 -> unlock 0 ksw 0 1


unlock 0 ksw 1 1
stat
COMMAND ACCEPTED

MMI-RAM 0115 -> e 0 ksw * *

COMMAND ACCEPTED

MMI-RAM 0115 ->


DEVICE STATUS INFORMATION FOR LOCATION 0:
OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- ---------
----
KSW 0 0 0 B-U NO REASON 15/09 17:18:51 None
KSW 0 1 0 E-U NO REASON 15/09 17:19:16 None
KSW 1 0 0 B-U NO REASON 15/09 17:18:51 None
KSW 1 1 0 E-U NO REASON 15/09 17:19:27 None

END OF STATUS REPORT

MMI-RAM 0115 -> chg_cell_id 6 0 2 0 1 7777 7183 6 0 2 0 1 13106 7183

69
WARNING: This change is NOT propagated throughout the CMDB neighbor
list(s).

COMMAND ACCEPTED

70
RXCDR Commissioning and Integration Example

71
RXCDR Commissioning

It’s the same procedure like BSC as before

GPROC2_ROM:emon_0115 % disp_dte
BSS DTE addresses:
Address #0: 602100120
Address #1: 602100120
Address #2: 602100120
Address #3: 602100120

OMCR DTE addresses:


Address #0: 60201003000141
Address #1: 60201003001142
Address #2: 60201003000061
Address #3: 60201003001062
Address #4: 60201003009999
Address #5: 60201003000100
Address #6: Zero or incorrect length address
Address #7: Zero or incorrect length address
GPROC2_ROM:emon_0115 % reset

Process 0x17 (monitor) requested a generic hard reset

Send DTE address for RXCDR as exist in OMCR

PROC2_ROM:emon_0115 % chg_dte bsc 0 9 6 0 2 0 1 0 0 2 2 8


COMMAND ACCEPTED

BSS DTE addresses:


Address #0: 602010022
Address #1: 602100120
Address #2: 602100120
Address #3: 602100120

OMCR DTE addresses:


Address #0: 60201003000141
Address #1: 60201003001142
Address #2: 60201003000061
Address #3: 60201003001062
Address #4: 60201003009999
Address #5: 60201003000100
Address #6: Zero or incorrect length address
Address #7: Zero or incorrect length address
GPROC2_ROM:emon_0115 % chg_dte bsc 0 9 6 0 2 0 1 0 2 2 8
COMMAND ACCEPTED

BSS DTE addresses:


Address #0: 602010228
Address #1: 602100120
Address #2: 602100120
Address #3: 602100120

72
OMCR DTE addresses:
Address #0: 60201003000141
Address #1: 60201003001142
Address #2: 60201003000061
Address #3: 60201003001062
Address #4: 60201003009999
Address #5: 60201003000100
Address #6: Zero or incorrect length address
Address #7: Zero or incorrect length address
GPROC2_ROM:emon_0115 % chg_dte bsc 1 9 6 0 2 0 1 0 2 2 8
COMMAND ACCEPTED

BSS DTE addresses:


Address #0: 602010228
Address #1: 602010228
Address #2: 602100120
Address #3: 602100120

OMCR DTE addresses:


Address #0: 60201003000141
Address #1: 60201003001142
Address #2: 60201003000061
Address #3: 60201003001062
Address #4: 60201003009999
Address #5: 60201003000100
Address #6: Zero or incorrect length address
Address #7: Zero or incorrect length address
GPROC2_ROM:emon_0115 % chg_dte bsc 2 6 0 2 0 1 0 2 2 8
COMMAND ACCEPTED

BSS DTE addresses:


Address #0: 602010228
Address #1: 602010228
Address #2: 020102
Address #3: 602100120

OMCR DTE addresses:


Address #0: 60201003000141
Address #1: 60201003001142
Address #2: 60201003000061
Address #3: 60201003001062
Address #4: 60201003009999
Address #5: 60201003000100
Address #6: Zero or incorrect length address
Address #7: Zero or incorrect length address
).
GPROC2_ROM:emon_0115 % chg_dte bsc 2 9 6 0 2 0 1 0 2 2 8
COMMAND ACCEPTED

BSS DTE addresses:


Address #0: 602010228
Address #1: 602010228
Address #2: 602010228
Address #3: 602100120

73
OMCR DTE addresses:
Address #0: 60201003000141
Address #1: 60201003001142
Address #2: 60201003000061
Address #3: 60201003001062
Address #4: 60201003009999
Address #5: 60201003000100
Address #6: Zero or incorrect length address
Address #7: Zero or incorrect length address

MMI-ROM 0115 -> chg_lev

Enter password for security level you wish to access:


Enter password for security level you wish to access:
Current security level is 3

Object Dv Object
Name Version Date Time Checksum Size S Ty Specific
======== =========== ========= ===== ========== ======== = == ============
015 bootrom 05.01.07.04 04-Jun-99 10:30 0x04093476 00870716 1 01 f8

Load version 05.01.07.04 Created 23-Aug-99 14:45

GPROC2_ROM:emon_0115 % GPROC-KSW Loopback, GPROC 113; TDM A = 1,1,1,1; TDM B


=1
,1,1,1
GPROC-KSW Loopback, GPROC 114; TDM A = 1,1,1,1; TDM B = 1,1,1,1
GPROC-MSI Loopback, GPROC 113; MSI cage 0, slot 16; TDM A = 1,1,1,1
GPROC-MSI Loopback, GPROC 114; MSI cage 0, slot 16; TDM A = 1,1,1,1
GPROC-MSI Loopback, GPROC 113; MSI cage 0, slot 16; TDM B = 1,1,1,1
GPROC-MSI Loopback, GPROC 114; MSI cage 0, slot 16; TDM B = 1,1,1,1
IP: TDM bus 0 selected

IP: BSC waiting for connection to the OMCR


IP: Successful connection established with the OMCR
IP: OMC indicates different database level.

IP: Requesting OMCR object # 0 via requestor # 0


IP: Requesting OMCR object # 2 via requestor # 0
IP: Setting dbase level to # 32857
IP: Requesting OMCR object # 3 via requestor # 0
IP: Requesting OMCR object # 4 via requestor # 0
IP: Requesting OMCR object # 5 via requestor # 0
IP: Requesting OMCR object # 6 via requestor # 0
IP: Requesting OMCR object # 8 via requestor # 0
IP: Requesting OMCR object # 12 via requestor # 0
IP: Requesting OMCR object # 13 via requestor # 0
IP: Requesting OMCR object # 16 via requestor # 0
IP: Requesting OMCR object # 17 via requestor # 0
IP: Requesting OMCR object # 18 via requestor # 0
IP: Requesting OMCR object # 19 via requestor # 0
IP: Requesting OMCR object # 20 via requestor # 0
IP: Requesting OMCR object # 22 via requestor # 0
IP: Requesting OMCR object # 23 via requestor # 0
IP: Requesting OMCR object # 24 via requestor # 0

74
IP: Requesting OMCR object # 32 via requestor # 0
IP: Requesting OMCR object # 33 via requestor # 0
IP: Requesting OMCR object # 34 via requestor # 0
IP: Requesting OMCR object # 35 via requestor # 0
IP: Requesting OMCR object # 36 via requestor # 0
IP: Requesting OMCR object # 48 via requestor # 0
IP: Requesting OMCR object # 49 via requestor # 0
IP: Requesting OMCR object # 50 via requestor # 0
IP: Requesting OMCR object # 51 via requestor # 0
Failed to cancel IP tid 0x8fa4: state machine 1, CPU type 3, cpu state 17, CPU s
eq 2
IP timeout: state machine 1, CPU type 3, cpu state 17, CPU seq 2, IP tid 0x8fbc,
Rcv tid 0x8fa4
IP: Requesting OMCR object # 52 via requestor # 0
IP: Requesting OMCR object # 63 via requestor # 0
IP: Requesting OMCR object # 64 via requestor # 0
IP: Requesting OMCR object # 65 via requestor # 0
IP: Requesting OMCR object # 66 via requestor # 0
IP: Requesting OMCR object # 67 via requestor # 0
IP: Requesting OMCR object # 68 via requestor # 0
IP: Requesting OMCR object # 69 via requestor # 0
IP: Requesting OMCR object # 70 via requestor # 0
IP: Requesting OMCR object # 71 via requestor # 0

GPROC2_ROM:emon_011a % disp_dte
BSS DTE addresses:
Address #0: 602010121
Address #1: 602010121
Address #2: 602010121
Address #3: 602010121

OMCR DTE addresses:


Address #0: 60201003000141
Address #1: 60201003001142
Address #2: 60201003000061
Address #3: 60201003001062
Address #4: 60201003009999
Address #5: 60201003000100
Address #6: Zero or incorrect length address
Address #7: Zero or incorrect length address
GPROC2_ROM:emon_011a % disp_dte

BSS DTE addresses:


Address #0: 602010121
Address #1: 602010121
Address #2: 602010121
Address #3: 602010121

OMCR DTE addresses:


Address #0: 60201003000141
Address #1: 60201003001142
Address #2: 60201003000061
Address #3: 60201003001062
Address #4: 60201003009999
Address #5: 60201003000100

75
Address #6: Zero or incorrect length address
Address #7: Zero or incorrect length address
GPROC2_ROM:emon_011a % 0

GPROC2_ROM:emon_011a % object
Object Dv Object
Name Version Date Time Checksum Size S Ty Specific
======== =========== ========= ===== ========== ======== = == ============
000 ex_ram 05.01.07.04 04-Jun-99 10:20 0x023022e8 00452868 1 01 f8
002 dbase 00.00.03.fd 27-Mar-00 12:16 0x060427e1 01743916 1 03 8db1 0000
003 ex_nul 05.01.07.00 18-Feb-99 18:30 0x00007bc4 00000427 1 01 f8
004 libboot 05.01.07.00 18-Feb-99 18:16 0x00142817 00015117 1 01 f8
005 libcomn 05.01.00.05 31-Jul-97 14:44 0x000046d2 00000200 1 06 f8
006 ex_com 05.01.07.00 18-Feb-99 18:19 0x0010f7bb 00012340 1 01 f8
013 options 06.01.00.00 23-Aug-99 14:45 0x000215fd 00001144 1 04
015 bootrom 05.01.07.04 04-Jun-99 10:30 0x04093476 00870716 0 01 f8
IP: Requesting OMCR object # 18 via requestor # 0

Load version 05.01.07.04 Created 23-Aug-99 14:45

GPROC2_ROM:emon_011a % IP: Requesting OMCR object # 19 via requestor # 0


IP: Requesting OMCR object # 20 via requestor # 0
IP: Requesting OMCR object # 22 via requestor # 0
IP: Requesting OMCR object # 23 via requestor # 0
IP: Requesting OMCR object # 24 via requestor # 0
IP: Requesting OMCR object # 64 via requestor # 0

GPROC2_ROM:emon_011a % IP: Requesting OMCR object # 65 via requestor # 0


IP: Requesting OMCR object # 66 via requestor # 0
IP: Requesting OMCR object # 67 via requestor # 0
IP: Requesting OMCR object # 68 via requestor # 0
IP: Requesting OMCR object # 69 via requestor # 0
IP: Requesting OMCR object # 74 via requestor # 0
IP: Requesting OMCR object # 75 via requestor # 0
IP: Requesting OMCR object # 77 via requestor # 0
IP: Requesting OMCR object # 78 via requestor # 0
IP: Requesting OMCR object # 80 via requestor # 0
IP: Requesting OMCR object # 96 via requestor # 0
IP: Requesting OMCR object # 112 via requestor # 0
IP: Requesting OMCR object # 113 via requestor # 0
IP: Requesting OMCR object # 114 via requestor # 0
IP: Requesting OMCR object # 116 via requestor # 0
IP: Requesting OMCR object # 117 via requestor # 0
IP: Requesting OMCR object # 118 via requestor # 0
IP: Requesting OMCR object # 128 via requestor # 0
IP: Requesting OMCR object # 178 via requestor # 0
IP: Requesting OMCR object # 179 via requestor # 0
IP: Requesting OMCR object # 181 via requestor # 0
IP: Requesting OMCR object # 182 via requestor # 0
IP: Requesting OMCR object # 183 via requestor # 0
IP: Requesting OMCR object # 186 via requestor # 0
IP: Requesting OMCR object # 187 via requestor # 0
IP: Requesting OMCR object # 189 via requestor # 0
IP: Requesting OMCR object # 190 via requestor # 0
IP: Requesting OMCR object # 203 via requestor # 0

76
IP: Requesting OMCR object # 204 via requestor # 0
IP: Requesting OMCR object # 205 via requestor # 0
IP: Requesting OMCR object # 206 via requestor # 0
IP: All is well, jump to ram
IP: Setting code verision to # 83953412

Copyright 1999, Motorola Incorporated

Motorola GPROC RAM Software Version 1.5.1.7.4 23-Aug-99


Motorola GPROC RAM Executive Version 1.5.1.7.4 4-Jun-99

GPROC2_RAM:emon_011a %
IP: Board is a GPROC II.
BOOT PROGRAMMING IN PROGRESS. DO NOT PULL GPROC
FROM BACKPLANE WHILE LEDs ARE FLASHING!!!

GPROC2 BOOT PROGRAMMING SUCCESSFUL, 870716 BYTES

MMI-RAM 011a ->

MMI-RAM 011a -> Waiting for System Initialization to complete.....


MMI-RAM 011a -> Database display commands accepted.
MMI-RAM 011a ->

MMI-RAM 011b -> disp_mms 0 16 0

Start of Report:

Site: 0 MMS: 16 0
General Timeslot Usage:
TS Usage Device ID Type Site CIC Group CIC State TS

0 UNAVAILABLE
16 UNUSED

Remote Transcoder Timeslot Usage:


TS Group Usage MMS TS Group
1 ADD CHANNEL 2 1 8 2
2 ADD CHANNEL 2 1 8 3
3 ADD CHANNEL 2 1 9 0
4 ADD CHANNEL 2 1 9 1
5 ADD CHANNEL 2 1 9 2
6 ADD CHANNEL 2 1 9 3
7 ADD CHANNEL 2 1 10 0
8 ADD CHANNEL 2 1 10 1
9 ADD CHANNEL 2 1 10 2
10 ADD CHANNEL 2 1 10 3
11 ADD CHANNEL 2 1 11 0
12 ADD CHANNEL 2 1 11 1
13 ADD CHANNEL 2 1 11 2

77
14 ADD CHANNEL 2 1 11 3
15 ADD CHANNEL 2 1 12 0
17 ADD CHANNEL 2 1 12 1
18 ADD CHANNEL 2 1 12 2
19 ADD CHANNEL 2 1 12 3
20 ADD CHANNEL 2 1 13 0
21 ADD CHANNEL 2 1 13 1
22 ADD CHANNEL 2 1 13 2
23 ADD CHANNEL 2 1 13 3
24 ADD CHANNEL 2 1 14 0
25 ADD CHANNEL 2 1 14 1
26 ADD CHANNEL 2 1 14 2
27 ADD CHANNEL 2 1 14 3
28 ADD CHANNEL 2 1 15 0
29 ADD CHANNEL 2 1 15 1
30 ADD CHANNEL 2 1 15 2
31 ADD CHANNEL 2 1 15 3

MMI-RAM 011a -> disp_act 0

Device Alarm Clear


(Subtype) Code Type Tag(hex) Date/Time Description
-------------------- ---- ---- -------- ---------- ---------------------------
GCLK 0 0 0 230 FMIC 00000001 03-29-2000 GCLK Calibration Request
(GCLK) 22:26:18
GCLK 0 0 0 2 FMIC 0080001B 03-30-2000 Clock Reference Failure
(GCLK) 13:25:29
GCLK 0 0 0 4 FMIC 0080001B 03-30-2000 Phase Lock Lost
(GCLK) 13:25:29
GCLK 0 0 0 13 FMIC 0080001B 03-30-2000 No Clock References
(GCLK) 13:29:30 Available
MMS 1 0 0 14 FMIC 0080001F 03-30-2000 Bit Error OOS Threshold
(MSI) 13:28:38 Exceeded
Estimated restoral-600.0 secs

MMS 1 1 0 16 FMIC 00800022 03-30-2000 Synchronization Loss OOS


(MSI) 13:29:10 Timer Expired
Estimated restoral-3.0 secs
MMS 2 0 0 16 FMIC 00800020 03-30-2000 Synchronization Loss OOS
(MSI) 13:28:55 Timer Expired
Estimated restoral-3.0 secs
MMS 2 1 0 14 FMIC 00800021 03-30-2000 Bit Error OOS Threshold
(MSI) 13:29:00 Exceeded
Estimated restoral-600.0 secs

MMS 3 0 0 18 FMIC 00800023 03-30-2000 Remote Alarm OOS Timer


(GDP) 13:31:53 Expired
Estimated restoral-50.0 secs
MMS 3 0 0 242 FMIC 00800023 03-30-2000 Device(s) OOS due to action
(GDP) 13:32:03 on this device
MMS 4 0 0 16 FMIC 0080000F 03-30-2000 Synchronization Loss OOS
(GDP) 13:22:16 Timer Expired
Estimated restoral-3.0 secs
MMS 5 0 0 14 FMIC 00800010 03-30-2000 Bit Error OOS Threshold

78
(GDP) 13:22:22 Exceeded
Estimated restoral-600.0 secs

MMS 6 0 0 16 FMIC 00000001 03-29-2000 Synchronization Loss OOS


22:19:38 Timer Expired
Estimated restoral-3.0 secs
MMS 7 0 0 16 FMIC 00800011 03-30-2000 Synchronization Loss OOS
(GDP) 13:22:47 Timer Expired
Estimated restoral-3.0 secs
MMS 8 0 0 16 FMIC 00800013 03-30-2000 Synchronization Loss OOS
(GDP) 13:22:54 Timer Expired
Estimated restoral-3.0 secs
MMS 9 0 0 18 FMIC 00800001 03-29-2000 Remote Alarm OOS Timer
(GDP) 22:24:06 Expired
Estimated restoral-50.0 secs
MMS 10 0 0 14 FMIC 00800012 03-30-2000 Bit Error OOS Threshold
(GDP) 13:22:52 Exceeded
Estimated restoral-600.0 secs

MMS 11 0 0 16 FMIC 00800014 03-30-2000 Synchronization Loss OOS


(GDP) 13:23:23 Timer Expired
Estimated restoral-3.0 secs
MMS 12 0 0 16 FMIC 00800015 03-30-2000 Synchronization Loss OOS
(GDP) 13:23:24 Timer Expired
Estimated restoral-3.0 secs
MMS 13 0 0 14 FMIC 00800017 03-30-2000 Bit Error OOS Threshold
(GDP) 13:24:51 Exceeded
Estimated restoral-600.0 secs

MMS 14 0 0 14 FMIC 00800016 03-30-2000 Bit Error OOS Threshold


(GDP) 13:23:25 Exceeded
Estimated restoral-600.0 secs

MMS 15 0 0 16 FMIC 00800018 03-30-2000 Synchronization Loss OOS


(GDP) 13:25:11 Timer Expired
Estimated restoral-3.0 secs
MMS 16 0 0 16 FMIC 00800019 03-30-2000 Synchronization Loss OOS
(GDP) 13:25:15 Timer Expired
Estimated restoral-3.0 secs
MMS 17 0 0 14 FMIC 0080001C 03-30-2000 Bit Error OOS Threshold
(GDP) 13:25:34 Exceeded
Estimated restoral-600.0 secs

MMS 18 0 0 14 FMIC 0080001A 03-30-2000 Bit Error OOS Threshold


(GDP) 13:25:29 Exceeded
Estimated restoral-600.0 secs

BSS 0 0 0 22 FMIC 00800020 03-30-2000 Trunk Critical Threshold


13:28:55 Exceeded
SITE 0 0 0 242 FMIC 00000001 03-29-2000 Device(s) OOS due to action
22:26:18 on this device

MMI-RAM 011a -> state 0 mms 7 0

STATUS INFORMATION:
Device: MMS 7 0 0

79
Administration state: UNLOCKED
Operational state: DISABLED
Reason code: Synch Loss OOS Timer
Time of last transition: Thu Mar 30 13:22:47 2000
Related Device/Function: None
END OF STATUS REPORT

MMI-RAM 011a -> state 0 xbl * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- -------------
XBL 0 0 0 D-U MMS Not In Service 30/03 13:28:39 None
XBL 1 0 0 D-U MMS Not In Service 30/03 13:28:55 None
XBL 2 0 0 D-U MMS Not In Service 30/03 13:29:10 None
XBL 3 0 0 D-U MMS Not In Service 30/03 13:29:00 None

END OF STATUS REPORT

MMI-RAM 011a -> state 0 oml * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- -------------
OML 0 0 0 B-U NO REASON 30/03 13:28:19 None

END OF STATUS REPORT

MMI-RAM 011a -> state 0 busy mms * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- -------------
MMS 0 0 0 B-U NO REASON 30/03 07:35:19 None
MMS 1 0 0 B-U NO REASON 31/03 04:56:30 None
MMS 1 1 0 B-U NO REASON 01/04 02:18:31 None
MMS 2 0 0 B-U NO REASON 31/03 04:57:15 None
MMS 2 1 0 B-U NO REASON 01/04 02:19:42 None
MMS 3 0 0 B-U NO REASON 30/03 17:42:05 None
MMS 4 0 0 B-U NO REASON 30/03 17:51:51 None
MMS 5 0 0 B-U NO REASON 01/04 01:41:54 None
MMS 6 0 0 B-U NO REASON 01/04 01:42:44 None
MMS 7 0 0 B-U NO REASON 01/04 02:13:03 None
MMS 8 0 0 B-U NO REASON 01/04 02:13:37 None

80
MMS 9 0 0 B-U NO REASON 01/04 02:14:02 None
MMS 10 0 0 B-U NO REASON 01/04 02:14:29 None
MMS 11 0 0 B-U NO REASON 30/03 17:42:45 None
MMS 12 0 0 B-U NO REASON 01/04 02:26:52 None
MMS 13 0 0 B-U NO REASON 30/03 17:43:06 None
MMS 14 0 0 B-U NO REASON 30/03 17:42:59 None
MMS 15 0 0 B-U NO REASON 01/04 02:14:52 None
MMS 16 0 0 B-U NO REASON 01/04 02:15:32 None
MMS 17 0 0 B-U NO REASON 01/04 02:16:31 None
MMS 18 0 0 B-U NO REASON 01/04 02:17:18 None

END OF STATUS REPORT

MMI-RAM 011a -> disp_act 0

Device Alarm Clear


(Subtype) Code Type Tag(hex) Date/Time Description
-------------------- ---- ---- -------- ---------- ---------------------------
IAS 0 0 0 1 FMIC Untagged 03-29-2000 Serial Bus Connection
21:57:43 Failure
GCLK 0 0 0 230 FMIC 0000000A 03-29-2000 GCLK Calibration Request
(GCLK) 23:30:02
GCLK 0 0 0 14 FMIC 00800192 03-30-2000 Phase Lock Failure
(GCLK) 13:31:27
GCLK 0 0 0 4 FMIC 0080001D 03-30-2000 Phase Lock Lost
(GCLK) 03:19:45
SITE 0 0 0 242 FMIC 00000001 03-29-2000 Device(s) OOS due to action
22:01:55 on this device

MMI-RAM 0114 ->


MMI-RAM 011a -> state 0 mms * *

DEVICE STATUS INFORMATION FOR LOCATION 0:


OPER STATES: D:Disabled E:Enabled B:Busy
ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

Last Transition Related


Device State Reason dd/mm hh:mm:ss Function
------------- ----- ------------------------- --------------- -------------
MMS 0 0 0 B-U NO REASON 30/03 13:28:18 None
MMS 0 1 0 B-U NO REASON 30/03 05:09:42 None
MMS 1 0 0 D-U Bit Error OOS Threshold 30/03 13:28:38 None
MMS 1 1 0 D-U Synch Loss OOS Timer 30/03 13:29:10 None
MMS 2 0 0 D-U Synch Loss OOS Timer 30/03 13:28:55 None
MMS 2 1 0 D-U Bit Error OOS Threshold 30/03 13:29:00 None
MMS 3 0 0 D-U Remote Alarm OOS Timer 30/03 13:31:53 None
MMS 4 0 0 D-U Synch Loss OOS Timer 30/03 13:22:16 None
MMS 5 0 0 D-U Bit Error OOS Threshold 30/03 13:22:22 None
MMS 6 0 0 D-U Synch Loss OOS Timer 29/03 22:19:38 None
MMS 7 0 0 D-U Synch Loss OOS Timer 30/03 13:22:47 None
MMS 8 0 0 D-U Synch Loss OOS Timer 30/03 13:22:54 None
MMS 9 0 0 D-U Remote Alarm OOS Timer 29/03 22:24:06 None
MMS 10 0 0 D-U Bit Error OOS Threshold 30/03 13:22:52 None
MMS 11 0 0 D-U Synch Loss OOS Timer 30/03 13:23:23 None
MMS 12 0 0 D-U Synch Loss OOS Timer 30/03 13:23:24 None
MMS 13 0 0 D-U Bit Error OOS Threshold 30/03 13:24:51 None

81
MMS 14 0 0 D-U Bit Error OOS Threshold 30/03 13:23:25 None
MMS 15 0 0 D-U Synch Loss OOS Timer 30/03 13:25:11 None
MMS 16 0 0 D-U Synch Loss OOS Timer 30/03 13:25:15 None
MMS 17 0 0 D-U Synch Loss OOS Timer 01/04 14:05:34 None
MMS 18 0 0 D-U NO REASON 30/03 13:25:29 None

END OF STATUS REPORT

MMI-RAM 011a -> ins 0 mms 10 0

COMMAND REJECTED: Insufficient security level, level = 1.

END OF STATUS REPORT

MMI-RAM 011a -> disp_mms 0 1 0

Start of Report:

Site: 0 MMS: 1 0
General Timeslot Usage:
TS Usage Device ID Type Site CIC Group CIC State TS

0 UNAVAILABLE
2 XBL 0 0 0 64K 0

Remote Transcoder Timeslot Usage:


TS Group Usage MMS TS Group
1 RXCDR LINK 0 0 2
3 0 ADD CHANNEL 3 0 9
1 3 0 10
2 3 0 11
3 3 0 12
4 0 ADD CHANNEL 3 0 13
1 3 0 14
2 3 0 15
3 3 0 17
5 0 ADD CHANNEL 3 0 18
1 3 0 19
2 3 0 20
3 3 0 21
6 0 ADD CHANNEL 3 0 22
1 3 0 23
2 3 0 24
3 3 0 25
7 0 ADD CHANNEL 3 0 26
1 3 0 27
2 3 0 28
3 3 0 29
8 0 ADD CHANNEL 3 0 30
1 3 0 31
2 4 0 1
3 4 0 2
9 0 ADD CHANNEL 4 0 3
1 4 0 4
2 4 0 5

82
3 4 0 6
10 0 ADD CHANNEL 4 0 7
1 4 0 8
2 4 0 9
3 4 0 10
11 0 ADD CHANNEL 4 0 11
1 4 0 12
2 4 0 13
3 4 0 14
12 0 ADD CHANNEL 4 0 15
1 4 0 17
2 4 0 18
3 4 0 19
13 0 ADD CHANNEL 4 0 20
1 4 0 21
2 4 0 22
3 4 0 23
14 0 ADD CHANNEL 4 0 24
1 4 0 25
2 4 0 26
3 4 0 27
15 0 ADD CHANNEL 4 0 28
1 4 0 29
2 4 0 30
3 4 0 31
16 RXCDR LINK 5 0 16
17 0 ADD CHANNEL 5 0 1
1 5 0 2
2 5 0 3
3 5 0 4
18 0 ADD CHANNEL 5 0 5
1 5 0 6
2 5 0 7
3 5 0 8
19 0 ADD CHANNEL 5 0 9
1 5 0 10
2 5 0 11
3 5 0 12
20 0 ADD CHANNEL 5 0 13
1 5 0 14
2 5 0 15
3 5 0 17
21 0 ADD CHANNEL 5 0 18
1 5 0 19
2 5 0 20
3 5 0 21
22 0 ADD CHANNEL 5 0 22
1 5 0 23
2 5 0 24
3 5 0 25
23 0 ADD CHANNEL 5 0 26
1 5 0 27
2 5 0 28
3 5 0 29
24 0 ADD CHANNEL 5 0 30
1 5 0 31

83
2 6 0 1
3 6 0 2
25 0 ADD CHANNEL 6 0 3
1 6 0 4
2 6 0 5
3 6 0 6
26 0 ADD CHANNEL 6 0 7
1 6 0 8
2 6 0 9

84
RXCDR Integrating

Introduction
Follow this procedure to ensure that all allocated Circuit Identification Codes (CICs) are
carrying good quality voice traffic.

Test equipment

The following test equipment is required:

• An IBM-compatible personal computer (PC).


• Terminal emulator software.
• A 9-way to- 25-way cable.
• A GSM mobile with a registered SIM card.

Commands
The following commands are required to carry out this procedure:

Procedure
Before starting the transcoder integration procedure, consult the site specific
documentation to determine the BSC/RXCDR configuration and cage slot allocation
(conventionally, timeslots 00 and 16 on XCDR boards are not allocated to voice/traffic
channels).

85
Proceed as follows:

Displaying MMS timeslot usage

1. At the operations and maintenance centre (OMC-R) man-machine interface (MMI), log
in to the required base site controller (BSC).
2. To display the circuit mapping, type:

disp_mms_ts_usage X Y Z

Under each heading, information relevent to the site and MMS port will be displayed.

3. Repeat step 2 for all MMSs.

4. Log out from the BSC.

86
Displaying BSC-MSC connectivity

1. Log on to the required RXCDR.

2. To display all CEPT nailed connections, type:

3. The information in the messages displayed in steps 2 and 2, together with


BSC/RXCDR site documentation, contain the CIC mapping.
Two examples are:

87
CIC test
1. Log on to the required BSC.

2. At the RAM EMON prompt type:

fil list

If any filters are shown delete them using the fil delete command.

3. Remotely log in to the GPROC running the LCF that supports the site under test using
the rlogin command. Determine this using the disp_p <site number> command at the
BSP.

4. At the RAM EMON prompt type:

fil create tag 10501h

Filter 10501h is created.


A response will be returned with a filter id.

5. at the prompt type:

fil start *
Filter * is started.

Where: * is: filter id

6. Set up a mobile to land or land to mobile call and monitor the filter output.
The following message is displayed:

The last two bytes of the data displayed (in hexadecimal) indicate the CIC in use.
Check the quality of the call and, if good, check off the CIC number on the checklist on
the next page. If the quality is bad, note the CIC number and retest.
The last two bytes in the example show a call on CIC 05 (hexadecimal).

Repeat this step until all CICs have been tested.

7. At the RAM EMON prompt type:

fil stop *

Filter * is stopped.

Where: * is: filter id

88
8. At the RAM EMON prompt type:

fil delete *

Filter * is deleted.

Where: * is: filter id

9. At the RAM EMON prompt type:

fil list

If any filters are shown delete them using the fil delete command.

10. Log out of the BSC.

11. Report the result of the integration and any anomalies to the OMC-R operator.

89
90

Вам также может понравиться