Ms Procomm Software Commnds

Software and commands:-

As we know we use Software to control and maintain any problem through it but it also need some configuration so that it will be able to work in proper way.

The name of software is PROCOMM PLUS and it has two versions but also with same configuration which will be shown in the following Figures.

After this configuration you will see the prompt on this way

MMI-RAM 1015 -> or

[24/08/06 12:35:22] MMI-RAM 1015 ->

Which means that you can write commands and software can accept it

5.29 COMMANDS:-

Before we start any command we must know what we need from it and the kind of information and the meaning of it.

But the most important thing is that to observe carefully the result because it will guide you to the right way and where is the problem.

NOTE:- All commands in small mode not in capital mode.

1- disp_site (space)

This command will show you the Site ID like in the example

[24/08/06 12:35:22] MMI-RAM 1015 -> disp_site

Current site number is 17

2- disp_act_al (space) (S.N)

This command will give you all active alarm on the site like in the example

[24/08/06 12:35:26] MMI-RAM 1015 -> disp_act_al 17

ACTIVE ALARM INFORMATION FOR LOCATION 17:

Device Alarm Clear

(Subtype) Code Type Tag(hex) Date/Time Description

-------------------- ---- ---- -------- ---------- ---------------------------

EAS 0 0 0 20 FMIC Untagged 08-24-2006 INTRUDER. (5)

12:27:53

IAS 1 0 0 93 FMIC Untagged 08-24-2006 Door Open

12:33:41

IAS 0 0 0 93 FMIC Untagged 08-24-2006 Door Open

12:33:49

END OF REPORT

As you can see we have two kind of alarms.

EAS: EXTERNAL ALARMS (Outside BTS cabinet)

IAS: INTERNAL ALARMS (Inside BTS cabinet)

Also check what is followed by EAS or IAS because it shows you the place of alarm like in example we have.

IAS 0 0 0 --------> in the first cabinet according to the first digit

IAS 1 0 0 ---------> in the second cabinet according to the first digit

EAS 0 0 0 ---------> all External Alarms

Also we can know if this old alarm or new alarm from the time and date and comparing it with time and date in [24/08/06 12:35:22] MMI-RAM 1015 ->

So we need to know the following:

1- Alarm type

2- Internal or External

3- Date and Time of the Alarm

3- alarm_mode (SPACE) (S.N) (ON)

This alarm to activate monitoring mode which will help you because if there is any alarm or fluctuation happened it will automatically appear on the screen with all its information.

[24/08/06 12:36:34] MMI-RAM 1015 -> alarm_mode 17 on

SITE MODE

---- ---------------------------------------

17 Alarm reporting enabled

4- State (SPACE) (S.N)

This is the most important command because it will give you the status of all data of site like the following:

[24/08/06 12:46:36] MMI-RAM 1015 -> state 17

DEVICE STATUS INFORMATION FOR LOCATION 17:

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

------------- ----- ------------------------- --------------- ------------- ---------------------

CSFP 0 0 0 D-U NO CODE 24/08 11:47:06 None

BTP 0 0 0 B-U NO REASON 24/08 11:47:03 None

BTP 1 0 0 E-U NO REASON 24/08 11:47:15 None

DRI 0 0 0 B-U NO REASON 24/08 11:51:00 RTF 0 1 0















MSI 0 0 0 B-U NO REASON 24/08 11:47:09 None

MMS 0 0 0 B-U MMS Providing Clock 24/08 11:47:10 None

MMS 0 1 0 D-U Synch Loss OOS Timer 24/08 11:47:10 None


RSL 0 0 0 E- U 64Kbps Link 24/08 12:45:19 None

GCLK 0 0 0 B-U GCLK Phase Locked 24/08 11:50:47 None

GCLK 1 0 0 E-U Phase Locked to Master 24/08 11:48:45 None

EAS 0 0 0 B-U NO REASON 24/08 11:47:03 None

CAB 0 0 0 B-U NO REASON 24/08 11:46:57 None


SITE 0 0 0 B-U NO REASON 24/08 11:53:38 None

PATH 0 0 0 D-U NO REASON 24/08 12:45:18 None

FUNCTION STATUS INFORMATION FOR LOCATION 17:

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


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

------------- ----- ------------------------- --------------- ------------- --------------------

RTF 0 0 0 B-E NO REASON 24/08 11:52:16 DRI 0 2 0















END OF STATUS REPORT

First we need to know the operation status and administration Status.

OPER STATES: D:Disabled E:Enabled B:Busy

ADMIN STATES: L:Locked U:Unlocked E:Equipped S:Shutdown

5.30 The operational state:-

Represents the state of a device from the viewpoint of the system. It can have one of three values:

Enabled.

Disabled.

Busy.

A disabled state indicates that the system has determined it cannot use the device. The system might put a device into the disabled state due to a problem detected by the system.

An enabled state indicates that the device is available for use and is not supporting user traffic. This device may be used to receive checkpoint info, that is, as a hot standby.

The busy state indicates that the device is currently in use and is supporting user traffic.

5.31 The administrative state:-

Represents the state of a device according to the view point of the operator. It can have one of four values:

Locked.

A locked state indicates that the device should not be used by the system.

Shutting Down.

The shutting down state is a transitory state between the unlocked and locked states. The system waits until all users of the device have finished with the device before moving the device to the locked state.

Unlocked.

An unlocked state indicates that the device may be used by the system.

NOTE:- You can change only the status of Administration but you can not change the status of operation even after changing the security level and to change the security level you need to use the following command.

chg_l (SPACE) (ENTER)

Enter security level password : *********

Then after this we need what are the items which appear on screen.

CSFP : Code Storage Facility Processor

BTP : Base Transceiver Processor

DRI : Digital Radio Interface

MSI : Multiple Serial Interface board

MMS : Multiple Serial Interface link

RSL : Radio Signaling Level

EAS : External Alarm Board

CAB : Cabinet

SITE : Site

PATH : Path between BTS and BSC

RTF : Radio Transmit Function

From the last abbreviation we should know that CSFP is available only at BSC so we will find it always D-U.BTP you will find one is B-U and the other is redundant E-U and every one is associated with MCUF or HIISC.

DRI : related to our transceiver cards

MSI: related to the card in the BSC

MMS : Related to the E1 channels

CAB: related to the cabinets as all

PATH: related to the complete link from the BTS till BSC

RSL : related to Link between the processor of MCUF or HIISC to the MSI

RTF : related to the software which is downloaded on the DRI

GCLK : The generic clock

And if you need to know al equipment connected to your cabinet you can write the following command.

5- disp_equip (SPACE) (S.N)

But the command of state it will give a lot of information so we need to check for specific thing & we will check for the following items.

(MMS & RSL & PATH & DRI)

6- state (SPACE) (S.N) mms (SPACE) * (SPACE) *

Like the following example

[24/08/06 12:48:16] MMI-RAM 1015 -> state 17 mms * *





Device State Reason dd/mm hh:mm





As any one see the important information that the operating MMS is MMS 0 0 0 and it is Busy from 24/8/2006 at 11:47:10 am and it is operation reason is MMS providing clock which can be also no reason.

Status of MMS are :

1- BUSY 2- SYNC LOSS OOS TIMER 3- REMOTE ALARM OOS TIMER EXPIRED

7- state (SPACE) (S.N) rsl (SPACE)* (SPACE) *


[24/08/06 12:48:22] MMI-RAM 1015 -> state 17 rsl * *






------------- ----- ------------------------- --------------- ------------- --------------

RSL 0 0 0 E-U 64Kbps Link 24/08 12:45:19 None


8- state (SPACE) (S.N) (SPACE) path (SPACE) * (SPACE) *


[24/08/06 12:48:32] MMI-RAM 1015 -> state 17 path * *






------------- ----- ------------------------- --------------- ------------- ----------------



But if any one have some confusion and want to know the place of any DRI he must write the following command.

9- disp_eq (SPACE) (S.N) (SPACE) dri ( number or id like 0 0 or 1 2)

Like this example for CTU I

[05/02/03 14:42:37] MMI–RAM 0115 –> disp_eq 81 dri 0 0

DRI identifier: 0 0

DRI Density[dri_density]: SINGLE

Cabinet identifier: 0

Type of connection to the BTP: MASTER

Port to which the TCU is connected[tcu_port]: 0

RTF identifier[pref_rtf_id]:

GSM cell ID where the DRI appears: 001 01 1 91

Antenna select number for this cell[antenna_select]: 1

Tuneable combining used: No

The diversity flag for this DRI is[diversity_flag]: 0

The fm cell type is[fm_cell_type]: 0

This example for CTU II

[05/02/03 14:47:55] MMI–RAM 0115 –> disp_eq 81 dri 0 1

DRI identifier: 0 1

DRI Density[dri_density]: DOUBLE

Associated DRI identifier: 0 2



Port to which the TCU is connected[tcu_port]: 1

RTF identifier[pref_rtf_id]:


Antenna select number for this cell[antenna_select]: 1


The diversity flag for this DRI is[diversity_flag]: 0

The fm cell type is[fm_cell_type]: 0

And as you can see the difference in the Density of the CTU I and CTU II where CTU II work as two of CTU I in software but only one in hardware.

And if any one need to know the configuration of any site he will write the following command .

10- state (SPACE) (S.N) (SPACE) dri (SPACE) * (SPACE) *


20/10/06 21:16:07] MMI-RAM 1015 -> state 14 dri * *






------------- ----- ------------------------- --------------- ------------- -------------------


DRI 0 1 0 E-U NO REASON 20/10 21:15:32 RTF 0 0 0












From which we will know that

FIRST SECTOR

DRI 0 0 0

DRI 0 1 0

DRI 0 2 0

DRI 0 3 0

SECOND SECTOR

DRI 1 0 0

DRI 1 1 0

DRI 1 2 0

DRI 1 3 0

SECTOR THREE

DRI 2 0 0

DRI 2 1 0

DRI 2 2 0

DRI 2 3 0

AND SO FOR ANY SITE

But after all of this we need to know how we can know the alarms of our BSC which the BTS is connected to it.

It is very simple because all BSC take the ID ZERO

So all commands on BTS can be applied on BSC but site number will equal to zero like the following example if we need to know the alarms on it.

[20/10/06 21:14:37] MMI-RAM 1015 -> disp_act_al 0

ACTIVE ALARM INFORMATION FOR LOCATION 0:

Device Alarm Clear

(Subtype) Code Type Tag(hex) Date/Time Description

-------------------- ---- ---- -------- ---------- ---------------------------

MMS 36 1 0 16 FMIC 00000001 09-01-2006 Synchronization Loss OOS

02:44:32 Timer Expired

MMS 31 0 0 16 FMIC 00000001 09-01-2006 Synchronization Loss OOS

02:44:27 Timer Expired

EAS 1 0 0 23 FMIC Untagged 09-01-2006 BSC Rectifier Minor (16)

02:45:09

END OF REPORT

Or to get all information about it to know the status of the following

MMS MSI GPROC MTL RSL PATH XBL……….AND OTHER PARAMETERS FOR ANY SITE ON THIS BSC

[20/10/06 21:14:41] MMI-RAM 1015 -> state 0






------------- ----- ------------------------- --------------- -------------

GPROC 1 0 0 B-U NO REASON 01/09 02:48:55 LCF 12 0 0

GPROC 2 0 0 B-U NO REASON 01/09 02:44:53 OMF 0 0 0













BSP 0 0 0 E-U NO REASON 01/09 02:43:10 None

BSP 1 0 0 B-U NO REASON 01/09 02:43:09 None























MMS 6 0 0 B-U NO REASON 17/10 02:02:53 None


























MMS 28 0 0 D-U Remote Alarm OOS Timer 01/09 18:44:38 None


















MTL 0 0 0 B-U NO REASON 17/10 02:02:04 None








RSL 1 0 0 B-U 64Kbps Link 19/10 13:14:09 None









RSL 8 1 0 D-U MMS Not In Service 19/10 23:31:14 None










RSL 86 0 0 D-U MMS Not In Service 20/10 21:14:43 None

OML 0 0 0 B-U NO REASON 17/10 00:00:19 None

GCLK 0 0 0 B-U GCLK Phase Locked 17/10 00:06:06 None

GCLK 1 0 0 E-U GCLK Phase Locked 17/10 00:06:06 None

KSW 0 0 0 E-U NO REASON 01/09 02:44:56 None

KSW 0 1 0 B-U NO REASON 01/09 02:44:56 None

KSW 1 0 0 E-U NO REASON 01/09 02:44:56 None

KSW 1 1 0 B-U NO REASON 01/09 02:44:56 None

TDM 0 0 0 E-U NO REASON 01/09 02:44:56 None

TDM 1 0 0 B-U NO REASON 01/09 02:44:56 None

LAN 0 0 0 B-U NO REASON 01/09 02:40:47 None

LAN 1 0 0 E-U NO REASON 01/09 02:44:54 None

EAS 1 0 0 B-U NO REASON 01/09 02:44:57 None

PBUS 0 0 0 B-U NO REASON 01/09 02:42:16 None

PBUS 0 1 0 E-U NO REASON 01/09 02:42:16 None

PBUS 1 0 0 B-U NO REASON 01/09 02:42:21 None

PBUS 1 1 0 E-U NO REASON 01/09 02:42:21 None

CBUS 0 0 0 B-U NO REASON 01/09 02:44:51 None

CBUS 0 1 0 E-U NO REASON 01/09 02:42:16 None

CBUS 1 0 0 B-U NO REASON 01/09 02:44:51 None

CBUS 1 1 0 E-U NO REASON 01/09 02:42:21 None

SBUS 0 0 0 B-U NO REASON 01/09 02:42:16 None

SBUS 0 1 0 E-U NO REASON 01/09 02:42:16 None

SBUS 1 0 0 B-U NO REASON 01/09 02:42:21 None

SBUS 1 1 0 E-U NO REASON 01/09 02:42:21 None

TBUS 0 0 0 E-U NO REASON 01/09 02:44:56 None

TBUS 0 1 0 B-U NO REASON 01/09 02:44:56 None

TBUS 1 0 0 E-U NO REASON 01/09 02:44:56 None

TBUS 1 1 0 B-U NO REASON 01/09 02:44:56 None

CAGE 0 0 0 B-U NO REASON 01/09 02:43:14 None

CAGE 1 0 0 B-U NO REASON 01/09 02:43:57 None













SITE 11 0 0 D-U Loading 20/10 20:49:58 None






SITE 86 0 0 D-U NO REASON 01/09 02:40:45 None

XBL 155 0 0 B-U 64Kbps Link 17/10 00:00:19 None








PATH 1 0 0 B-U NO REASON 19/10 13:14:22 None




















OPL 0 0 0 B-U NO REASON 17/10 00:00:19 None

PCU 0 0 0 B-U NO REASON 20/10 15:33:57 None

GSL 0 0 0 B-U NO REASON 20/10 15:32:30 None






AXCDR 155 0 0 B-U NO REASON 13/10 17:07:43 None

AXCDR 175 0 0 D-U No Link 01/09 02:40:45 None






FUNCTION STATUS INFORMATION FOR LOCATION 0:

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


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

------------- ----- ------------------------- --------------- -------------

LCF 0 0 0 B-E NO REASON 01/09 02:44:52 GPROC 3 0 0













OMF 0 0 0 B-E NO REASON 01/09 02:44:53 GPROC 2 0 0


And believe me when i am saying it is very huge information and we can also select what we need by command ………state


[20/10/06 21:15:09] MMI-RAM 1015 -> state 0 site * *






------------- ----- ------------------------- --------------- -------------












SITE 11 0 0 D-U Loading 20/10 20:49:58 None






SITE 86 0 0 D-U NO REASON 01/09 02:40:45 None


Which give us all details about sites and that all sites were down at the same time and return back due to some data base upgrade.

But we can also be more accurate if we are searching for specific MMS like the following example.

20/10/06 21:15:15] MMI-RAM 1015 -> state 0 mms 26 0

STATUS INFORMATION:

Device: MMS 26 0 0

Administration state: UNLOCKED

Operational state: DISABLED

Reason code: Synch Loss OOS Timer

Time of last transition: Fri Oct 20 14:16:47 2006

Related Device/Function: None


5.32 Servicing Section:-

In this section we will use some commands like the following so that we will be able to change, maintain and calibrate any card so.

First we need to prevent the DRI 0 0 form working and carrying any calls but first change your security level to second level through this command.

20/10/06 21:15:15] MMI-RAM 1015 ->chg_l

Enter security level password : **************

Then

20/10/06 21:15:15] MMI-RAM 1015 ->l # dri 0 0 0

Where # is the site number and

After this if we need to switch it on again we can do it by two commands with the same function

20/10/06 21:15:15] MMI-RAM 1015 ->unl # dri 0 0 0

Or

20/10/06 21:15:15] MMI-RAM 1015 ->ins # dri 0 0 0

And we explain more about more commands in private section for

MOTOROLA HORIZON – II

Comparing the functionality of the main components of the Horizon II macro with equivalent components of the previous generation Horizonmacro I.

Horizon II macro vs. Horizonmacro I

Function Horizon II macro component

Horizonmacro I equivalent

Input power conversion units (max fitted)

PSU

(4)

PSM

(3)

Power to transceivers and signal routeing

Backplane BPSM and backplane

Transceivers

(max fitted)

CTU2

(6)

CTU

(6)

Main processor module

(Max fitted)

HIISC

(2)

MCUF

(2)

Processor module connection to transceivers in another cabinet

Internal XMUX in HIISC (1) and separate site expansion boards

(1 or 2)

Internal FMUX in

MCUF (2) or

external FMUX (2)

Slave cabinet multiplexer XMUX FMUX

Rx components

(Max fitted)

SURF2

(2)

SURF

(1)

Transceiver to Rx components SURF2 harness SURF harness

TX blocks

(Max fitted internally)

DUP, HCU and DHU

(6)

DCF, TDF, DDF and HCU

(3)

DC power supply for digital modules

(Max fitted)

Integrated in HIISC supplied via backplane

BPSM

(2)

Equipment protection/isolation CBC CBM

Links to terrestrial network

(Max fitted)

Internal NIU in HIISC NIU

(4)

Alarm Handling Alarm Module *** Alarm Module

E1/T1 links CIM/T43 or BIM/BIB CIM/T43 or BIM/BIB

NOTE :- *** Alarm boards are not interchangeable.

CTU is not forward compatible with the HMII cabinet and is not supported.

6.1 CTU2 :-

The new CTU2 provides the following functionality:

Double density carrier support

Backwards compatibility with current Horizonmacro platform (with some restrictions)

Support of 900Mhz CTU2

Support of 1800Mhz CTU2

The Double Density Capable CTU2 Hardware is capable of operating in Dual Carrier Mode or Single Carrier Mode under software control. There is a difference between the transmit power capabilities of a XCVR in SDM or DDM.

6.2 CTU2 RF Power Output:-

CTU 2 RF power output (installed in Horizon II macro cabinet)

Output power (+/- 2dB)

CTU2 configuration Combining EGSM 900 DCS1800

Single density No external combining 63 W 50 W

Double density No external combining 20 W 16 W

2 x double density 1 internal + 1 external stage hybrid combining

9 W 7 W

CTU 2 RF power output (installed in Horizonmacro cabinet)

Output power (+/- 2dB)

CTU2 configuration Combining EGSM 900 DCS1800

Single density No external combining 40 W 32 W

Single density 1 external stage hybrid 20 W 16 W

Double density No external combining 10 W 10 W

2 x double density 1 internal + 1 external stage hybrid combining

5 W 5 W

The CTU2 transceiver has the ability to support two logical carriers within a single transceiver unit.

The number of carriers to be supported by a CTU2 is determined from the database.

The CTU2 operates in single or dual carrier mode within a Horizonmacro or Horizon II macro cabinet. Therefore, it is possible that a single Horizonmacro or Horizon II macro cabinet can now support a maximum of 12 carriers, if all of the transceivers within the Horizonmacro/Horizon II macro cabinet are CTU2 operating in dual carrier mode.

However, when operating in dual carrier mode there are some restrictions on the operation in the Horizonmacro and Horizon II macro cabinet types.

The BSS in which the Horizonmacro cabinet resides must be running the current software release for Horizon II macro (1670.xx). If the BSS is running software release prior to the addition of support for the CTU2, the CTU2 will not be able to be brought into service. If this fault were to occur, the H2SC/CTU2 would have to be returned for repair.

To prevent this unrecoverable fault occurring in the field, the H2SC and CTU2 contains self-preservation code, which will prevent a software release prior to 1670.xx being downloaded.

6.3 Single Carrier Mode:-

In Single Carrier mode, the CTU2 is similar to those of a CTU. The CTU2 can be used as a replacement (FRU) for the CTU within a Horizonmacro cabinet.

MMI-RAM 0115 -> disp_eq 60 dri 1 0

DRI identifier: 1 0

DRI Density [dri_density]: SINGLE



Port to which the TCU is connected [tcu_port]: 1

RTF identifier [pref_rtf_id]:


Antenna select number for this cell [antenna_select]: 2


The diversity flag for this DRI is [diversity_flag]: 0

The fm cell type is [fm_cell_type]: 0

MMI-RAM 0115 -> disp_eq 63 dri 2 0

DRI identifier: 2 0

DRI Density [dri_density]: DOUBLE

Associated DRI identifier: 2 1



Port to which the TCU is connected [tcu_port]: 4

RTF identifier [pref_rtf_id]:


Antenna select number for this cell [antenna_select]: 3


The diversity flag for this DRI is [diversity_flag]: 1

The fm cell type is [fm_cell_type]: 4

6.4 Dual Carrier Mode:-

CTU2 supports two carriers when operating in dual carrier mode. When the CTU2 is operating in dual carrier mode within a Horizonmacro cabinet the following restrictions apply;

Baseband Hopping – Baseband hopping is not allowed in some scenarios. The baseband hopping restrictions on the CTU2 apply when the controlling cabinet within the BTS is a Horizonmacro or M-Cell cabinet. The table below shows Baseband Hopping support for CTU2.

Controlling cabinet

M-Cell or Horizonmacro Horizon II macro

Extension cabinet

None

M-Cell

Horizon

macro

Horizon

macro2

None

M-Cell

Horizon

macro

Horizon

macro2

XCVR Type

CTU2 - SD

Yes Yes Yes Yes Yes Yes Yes Yes

CTU2 - DD

No No No No Yes Yes Yes Yes

Output Power - Maximum output power capabilities (at the cabinet antenna connector) are reduced when operating in Dual Carrier Mode. This is due to internal combining within the CTU2.

Remote Tune Combining – The use of an RTC device with a Double Density XCVR in Dual Carrier Mode is not possible as the XCVR contains two carriers multiplexed onto a single RF output.

Cell Restrictions – In Dual Carrier Mode, both of the carriers supported on the CTU2 must reside in the same cell because there is only a single RF output on the CTU2. In addition, as the CTU2 can only support a single frequency band, the carriers must also reside in the same zone in a Dual Band Cell.

6.5 Power Supply Unit (PSU):-

The power consumption of a CTU2 is greater than that of a CTU. When using CTU2’s in a Horizonmacro cabinet it is recommended to use 3 PSU’s. The following rule of thumb applies:

The cabinet power requirements come in 3 variants:

Horizon II macro cabinet power supply requirements

Nominal Voltage Voltage supply range Current supply maximum

+27 V dc (negative earth) +19.5 to +30 V dc 64 A (at nominal voltage)

-48 V dc (positive earth) -39 to –72 V dc 36 A (at nominal voltage)

120/240 V ac (50 to 60 Hz) 88 to 270 V 7.5 A (at nominal voltage)

There are five alarm conditions for each PSU:

Output Overvoltage.

Output undervoltage.

Input undervoltage.

Overtemperature.

Fan failure.

PSU Operation configuration

Number of PSUs Maximum load capability

2 Upto 3 CTUs

3 Upto 6 CTUs

4 Redundancy and power load sharing

Ms Procomm Software Commnds

Documents

Transcript of Ms Procomm Software Commnds