1000p20b

Technical ManualiDEN Alarm and State Change Event Reference Manual

6871000P20-B

30-Oct-08

SR17.0

SYSTEM LEVEL INFORMATION

Notice to Users

No part of this publication, or any software included with it, may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, including but not limited to, photocopying, electronic, mechanical, recording or otherwise, without the express prior written permission of the copyright holder. Motorola, Inc. provides this document AS IS without warranty of any kind, either expressed or implied, including but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Motorola reserves the rights to make changes or improvements in the equipment, software, or specifications described in this document at any time without notice. These changes will be incorporated in new releases of this document.

Computer Software CopyrightsThe Motorola and 3rd Party supplied Software (SW) products described in this instruction manual may include copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola and other 3rd Party supplied SW certain exclusive rights for copyrighted computer programs, including the exclusive right to copy or reproduce in any form of the copyrighted computer program. Accordingly, any copyrighted Motorola or other 3rd Party supplied SW computer programs contained in the Motorola products described in this instruction manual may not be copied, reverse engineered, or reproduced in any manner without the express prior written permission of Motorola or the 3rd Party SW supplier. Furthermore, the purchase of Motorola products shall not be deemed to grant, either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied SW, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product.

Use and Disclosure Restrictions

The software described in this document is the property of Motorola, Inc. It is furnished under a duly executed license agreement and may be used and/or disclosed only in accordance with the terms of the said agreement.

The software and documentation contained in this publication are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without the express prior written permission of Motorola, Inc.

Trademarks

MOTOROLA, the Stylized M Logo, iDEN, and Message Mail are trademarks or registered trademarks of Motorola, Inc. in the United States and other countries.

All other product or services mentioned in this document are identified by the trademarks or service marks of their respective companies or organizations, and Motorola, Inc. disclaims any responsibility for specifying their ownership. Any such marks are used in an editorial manner, to the benefit of the owner, with no intention of infringement.

2008 - Motorola, Inc. All Rights Reserved REV 12/15/06

Contact Information

Motorola, Inc.Networks business1501 Shure Dr.Arlington Heights, IL 60004U.S.A

SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE.

While reasonable efforts have been made to assure the accuracy of this document, this document may contain technical or typographical errors or omissions. Motorola, Inc. and its subsidiaries and affiliates disclaim responsibility for any labor, materials, or costs incurred by any person or party as a result of using this document. Motorola, Inc., any of its subsidiaries or affiliates shall not be liable for any damages (including, but not limited to, consequential, indirect, incidental, or special damages or loss of profits or data) even if they were foreseeable and Motorola has been informed of their potential occurrence, arising out of or in connection with this document or its use. Motorola, Inc. reserves the right to make changes without notice to any products or services described herein and reserves the right to make changes from time to time in content of this document and substitute the new document therefor, with no obligation to notify any person or party of such changes or substitutions.

SR17. m and State Change Event Reference Manual30-Oc iii

IntrodOvHoIntInt

ACGAlaStaEv

APDAlaStaEv

BRCAlaStaEv

BSCAlaStaEv

CCPDAlaStaEv

. . . . . . . . . . . . . . . . . . . . CCPHA DAP-1

. . . . . . . . . . . . . . . . . . . CCPHA DAP-25

. . . . . . . . . . . . . . . . . . . CCPHA DAP-38

. . . . . . . . . . . . . . . . . . . . . . CCPiHLR-1

. . . . . . . . . . . . . . . . . . . . . CCPiHLR-19

. . . . . . . . . . . . . . . . . . . . . CCPiHLR-25

. . . . . . . . . . . . . . . . . . . . . . . . . . . iCP-1

. . . . . . . . . . . . . . . . . . . . . . . . . . . iCP12

. . . . . . . . . . . . . . . . . . . . . . . . . . iCP-23

. . . . . . . . . . . . . . . . . . . . . . . . . . iDAC-1

. . . . . . . . . . . . . . . . . . . . . . . . . . iDAC-5

. . . . . . . . . . . . . . . . . . . . . . . . . iDAC-12

. . . . . . . . . . . . . . . . . . . . . . . . . . . iSG-1

. . . . . . . . . . . . . . . . . . . . . . . . . . . iSG-9

. . . . . . . . . . . . . . . . . . . . . . . . . . iSG-17

. . . . . . . . . . . . . . . . . . . . . . . . . . iVPU-1

. . . . . . . . . . . . . . . . . . . . . . . . . iVPU-77

. . . . . . . . . . . . . . . . . . . . . . . . . iVPU-98

of Contents0 iDEN Alart-08 6871000P20-B

uctionerview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1w to Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1erpreting Alarm Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2erpreting Event Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

rms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACG-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACG-55

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACG-72

rms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APD-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APD-5

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APD-9

rms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BRC-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BRC-23

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BRC-26

rms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC-53

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC-72APrms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPDAP-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPDAP-23

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPDAP-37

CCPHA DAPAlarms . . . . . . . . . . . . . . . State Changes . . . . . . . . Events . . . . . . . . . . . . . . .

CCPiHLRAlarms . . . . . . . . . . . . . . . State Changes . . . . . . . . Events . . . . . . . . . . . . . . .

iCPAlarms . . . . . . . . . . . . . . . State Changes . . . . . . . . Events . . . . . . . . . . . . . . .

iDACAlarms . . . . . . . . . . . . . . . State Changes . . . . . . . . Events . . . . . . . . . . . . . . .

iSGAlarms . . . . . . . . . . . . . . . State Changes . . . . . . . . Events . . . . . . . . . . . . . . .

iVPUAlarms . . . . . . . . . . . . . . . State Changes . . . . . . . . Events . . . . . . . . . . . . . . .

X X X X Table

Tab

iDEN SR17.0iv 30-Oct-08

MDGAlaStaEv

MDGAlaStaEv

OMCAlaStaMis

SSCAlaStaEv

VSGWAlaStaEv

3gXCAlaStaEvle of Contents

Alarm and State Change Event Reference Manual6871000P20-B

2rms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG2-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG2-77

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG2-844rms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG4-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG4-76

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG4-86-Rrms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R-26cellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R-36

rms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSC-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSC-11

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSC-18

rms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSGW-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSGW-41

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSGW-73DRrms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XCDR-1te Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XCDR-31

ents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XCDR-53

SR17. m and State Change Event Reference Manual30-Oc 1

ntroductionOve

Many istorical reference. These status messages may be use jor categories: Ala played for the attention of the operator. Alarms

are OMC-R Event Alarm Management manual (68

Sta Eve

How

This m arm, state change, or event. Each section contain he OMC-R: AC AP BR BS CC CC CC iCP0 iDEN Alart-08 6871000P20-B

X X X X Irview

iDEN Network Elements (NEs) report status messages to the OMC-R where they are received and stored for hd to aid in system troubleshooting and diagnostics. Each status message falls into one of the following three marms An occurrence or change in the operating state of the network or NEs that is significant enough to be dis both system defaults and defined by the operator(s) and are classified by severity. For more details, refer to the71000P16).te Changes Changes in the operation condition of the network or NE. (e.g., from active to standby).nts Events that occur that are not Alarms nor state changes that provide information to the operator.

to Use this Manual

anual is System Release specific. The sections of the manual are organized by the major NEs that report the als tables that summarize the OMC-R reporting activities for that NE. The following NEs report their status to tGDCCPDAPPHADAPPiHLR

iDAC iSG iVPU MDG2 MDG4 OMCR SSC VSGW 3gXCDR

Important This version of this manual supersedes all versions prior to 30-Oct-08.

iDEN SR17.02 30-Oct-08

Inte

Each c

TableColum

Alarm

OMC

MOI In (e.g., cabinet, cage, slot position).

MOI In

Inst

Alarm

Sever

me alarms cannot be cleared.

void service-affecting conditions.

ld be taken to prevent an interruption of service.

action is required. For example, part of an NE has

s level usually indicates that facilities connections,

Relate

Relate

Reme Alarm and State Change Event Reference Manual6871000P20-B

rpreting Alarm Tables

olumn of the Alarm tables contains the following information:

1: Alarm Table Column Heading Descriptionsn Description

Code The identifier that uniquely identifies this alarm.

Text The text the alarm uses to report to the OMC-R.

fo (ID) The Managed Object Instance (MOI) identifier used by the particular portion of the NE to identify itself

fo (Label) The label (name) assigned to the alarm-reporting device.

Additional MOI information, e.g., the device Instance that further identifies the source of the alarm.

Code Text Additional information about the alarm.

ity

One of the following 6 severity levels:

1. Clear One or more previous alarms have been resolved (alarm condition no longer exists). So

2. Indeterminate The severity level of the alarm cannot be accurately reported.

3. Warning A condition exists that may affect service. Warnings should be investigated to help a

4. Minor A fault condition that does not affect service has been detected. Corrective action shou

5. Major A service-affecting condition exists. Service is impaired or reduced. Immediate correctivestopped working properly but the rest of the NE is still functioning.

6. Critical A significant service-affecting fault condition exists that requires immediate action. Thior all or a large portion of an NE is not in service.

d Alarms The Alarm codes that, when combined, may result in this alarm.

d State Changes The reason code(s) that could occur at the NE that may result in this Alarm.

dy Possible corrective action(s) for the alarm.

SR17. m and State Change Event Reference Manual30-Oc 3

Repor

Outag

Chang oved in the next release.

Comm ual events and operating conditions of the network.

TableColum0 iDEN Alart-08 6871000P20-B

t & Clear

Alarms may only announce themselves. This column indicates one of the following: R (Report) Removes previous alarms C (Clear) Alarm has been cleared RC (Report and Clear)

eWhether the alarm is service-affecting: Yes An outage may occur. No An outage will not occur.

e Status Whether the alarm has changed from the previous software release. If D, then this alarm will be rem

ents & Notes Additional comments/information that may be useful in understanding and connecting the alarm to act

1: Alarm Table Column Heading Descriptions (continued)n Description

iDEN SR17.04 30-Oct-08

Inte

Each c

TableColum

Reaso

OMC

MOI In elf (e.g., cabinet, cage, slot position).

MOI In

Inst

From

To Sta

Relate

Relate

Event

Outag

Chang moved in the next release.

Comm tual events and operating conditions of the network. Alarm and State Change Event Reference Manual6871000P20-B

rpreting Event Tables

olumn of the Event tables contains the following information

2: Event Table Column Heading Descriptionsn Description

n Code An identifier that uniquely identifies the State Change and/or Event.

Text The text the alarm uses to report to the OMC-R.

fo (ID) The Managed Object Instance (MOI) identifier used by the particular portion of the NE to identify its

fo (Label) The label (name) assigned to the alarm-reporting device.

Additional MOI information: the device instance that further identifies the source of the alarm.

State The nature of the change: From State The initial operating state. To State The state produced by the change.te

d State Changes The reason code(s) that could occur at the NE that may result in this Event.

d Alarms The Event codes that, when combined, may result in this Event.

Description A general description of the change in operating conditions.

eWhether the event is service-affecting: Yes An outage may occur. No An outage will not occur.

e Status Whether the event has changed from the previous software release. If D, then this event will be re

ents & Notes Additional comments/information that may be useful in understanding and connecting the event to ac

Release SR17.0 iDEN Alarm and State Change Event Reference Manual

October 30, 2008 ACG-1

________________________________ ACG Alarms

Alarm Type

Alarm Code

OMC Text MOI Info (Id)

MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

communicationFailureEvent

903 ACG T1 or E1 Physical Link Failure

1.3.6.1.4.1.161.3.3.2.2.14.1.4.54.1.n.m

T1/E1 n=[1/2], m=[1/2]

The physical T1 or E1 line is down.

Warning

EMPTY

EMPTY Possible Causes:1. Physical T1 or E1 cable is connected improperly or defective 2. BSC or DACS is powered off 3. ACG or BSC or DACS is rebooted 4. T1 or E1 line problem occurred somewhere along the path from EBTS to BSC (e.g., central office or T1 or E1 provider line outage) 5. All DAP links down and any of the following conditions: RAI (remote alarm indication) or LFA (loss of frame alignment) Actions:1. Properly connect or replace T1 or E1 cable 2. Power on BSC or DACS 3. Wait for ACG or BSC or DACS to establish T1 or E1 connection 4. Check with the T1 or E1 provider or check any other hubs that are along the path from EBTS to BSC 5. Check DAP links and check with T1/E1 provider.

R N U note:m[1-2] indicates the T1/E1 link ID


903 ACG T1 or E1 Physical Link Failure

1.3.6.1.4.1.161.3.3.2.2.14.1.4.54.1.n.m

T1/E1 n=[1/2], m=[1/2]

The physical T1 or E1 line is up.

Clear

EMPTY

EMPTY No action required C N U note:m[1-2] indicates the T1/E1 link ID.

communicationFailureE

920 ACG_BMR or iMU Link Failure

1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.

BMR n = [1/2] EMPTY Mi

EM

EMPTY Possible Causes (for VME or ISC2 only):1. BMR (for VME)

R N U EMPTY

iDEN Alarm and State Change Event Reference Manual Release SR17.0

ACG-2 October 30, 2008

Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

vent 1.n nor

PTY

or iMU (for iSC2) powered off 2. Communication cable (RS232 serial for VME or IEEE 1284 parallel for iSC2) connected improperly or defective 3. Power cable connected improperly or defective 4. Circuit breaker blown or defective. 5. BMR (for VME) or iMU (for iSC2) defective Actions: 1. Power on BMR (for VME) or iMU (for iSC2) 2. Properly connect or replace appropriate communication cable 3. Properly connect or replace power cable 4. Repair/replace circuit breaker 5. Repair/replace BMR (for VME) or iMU (for iSC2)


921 ACG_EAS or ACG_iMU Link Failure

1.3.6.1.4.1.161.3.3.2.2.14.1.4.7.1.1.n

EAS n = [1/2] EMPTY Major

EMPTY

EMPTY Possible Causes:1. EAS (for VME) or iMU (for iSC) powered off 2. Communication cable (RS232 serial for VME or IEEE 1284 parallel for iSC) connected improperly or defective 3. Power cable connected improperly or defective 4. Circuit breaker blown or defective 5. EAS (for VME) or iMU (for iSC) defective Actions:1. Power on EAS (for VME) or iMU (for iSC) 2. Properly connect or replace appropriate communication cable 3. Properly connect or replace power cable 4. Repair/replace circuit breaker 5. Repair/replace EAS (for VME) or iMU (for iSC)

RC

N U EMPTY

communicationFailureE

922 GPSR Communications

1.3.6.1.4.1.161.3.3.2.2.14.1.4.2.2.

TFR/SRI n = [1/2] EMPTY Cr

EM

EMPTY Possible Causes:1. TFR (for VME) or SRI (for iSC2)

RC

N U EMPTY



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

vent Fault 2.n itical

PTY

powered off 2. Communication cable (RS232 serial for VME only) connected improperly or defective 3. Power cable connected improperly or defective (VME only) 4. Circuit breaker blown or defective (VME only) 5. TFR (for VME) or SRI (for iSC2) or iSC3 (for iSC3) defective Actions:1. Power on TFR (for VME) or SRI (for iSC2) 2. Properly connect or replace communication cable 3. Properly connect or replace power cable(VME only) 4. Repair circuit breaker(VME only) 5.Power cycle the iSC3 (for iSC3). 6. Repair/replace TFR (for VME) or SRI (for iSC2) or iSC3 (for iSC3).


931 BSC_ACG MOBIS LAPD Link Failure

1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.n

GenACG n = [1/2] EMPTY Indeterminate

EMPTY

REPORT: ACG_STM: UEA-UEIDL, UEA-UEIMP, UEIMP-UEIDL EBTS_STM: UEA-UEIDL, UEA-UEIMP, UEIMP-UEIDL CLEAR: ACG_STM: LEIDL-UEIDL, UEIMP-

Possible Causes:1. T1 physical or logical link is down 2. BSC powered off.3. BSC defective Actions:1. Establish T1 physical and logical link connection to BSC. Also, need more info from system engineers 2. Power on BSC 3. Repair/replace BSC

RC

N U EMPTY



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

UEA EBTS_STM: UEA-UEIDL, UEIMP-UEIDL, UDIDL-UEIDL, UEIMP-UEA


940 ACG_BRC LAPD Link Failure

1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.n.m.o

GenACG n = [1-8], m = [1-6], o = [1/2]

ACG-BRC LAPD link failure for BRC

Critical

EMPTY

REPORT: CELL_STM: LEIDL-LDIDL, UEIDL-UDIDL, UEA-UDIDL, UEIMP-UDIDL, UEA-UEIMP, UEIDL-LEIDL ACG_STM: UEIDL-UDIDL, UEA-UEIDL, UEA-UEIMP, UEIDL-LEIDL, UDIDL-LDIDL, UEIDL-UEIMP, UEA-UEIMP, UEA-UDIDL, UEA-

Possible Causes:1. Ethernet LAN physical or logical link is down 2. BRC powered off 3. BRC self reset 4. BRC defective Actions:1. Establish Ethernet LAN physical and logical link connection to the BRC 2. Power on BRC 3. Wait for BRC to transition to UEIMP or UEA state 4. Repair/replace BRC

R N U note:[1-8] indicates the BRC's cabinet ID [1-6] indicates the BRC's position ID. where: = BRC's combined cabinet and position ID, 11 - 86 = Type of the BR: 1 = Legacy BR, 3 = Quad BR



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

UEIMP, UEIMP-UDIDL, UEIMP-UEIDL, UEIDL-LEIDL, UDIDL-LDIDL, LEIDL-UEIDL, UDIDL-UEIDL EBTS_STM: UEA-UEIDL, UEIMP-UEIDL, UDIDL-UEIDL, UEIDL-UEIMP, UEA-UEIMP, UEIDL-UDIDL, UEA-UDIDL, UEIMP-UDIDL


940 ACG_BRC LAPD Link Failure

1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.n.m.o

GenACG n = [1-8], m = [1-6], o = [1/2]

ACG-BRC LAPD link established for BRC

Clear

EMPTY

EMPTY No action required. C N U where: = BRC's combined cabinet and position ID, 11 - 86


1000 No DAP Link Version Response

1.3.6.1.4.1.161.3.3.2.2.14.1.4.101.1.n.m

ACG-genDAP

n=[1-15], m=[1/2]

Major

EMPTY

CLEAR: DL_STM: UEIDL-UEA, UEIDL-UEIMP DCC_STM: UEIDL-UEA,

Possible Causes:1. T1 or E1 physical or logical link is down 2. DAP powered off 3. DAP rebooted 4. DAP defective Actions:1. Establish T1 or E1 physical and logical link connection to DAP 2. Power on DAP 3. Wait for DAP to come up 4. Repair/replace/reboot DAP

RC

N U note:[1-15] indicates the DAP ID, where: = DAP ID of the DAP that did not respond to the Link Version Request sent by ACG, 1 - 15



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

UEIDL-UEIMP, UEIMP-UEA, UEA-UEIMP ACG_STM: LEIDL-UEIDL, UEA-UEIMP, UEIMP-UEA EBTS_STM: UEA-UEIDL, UEIMP-UEIDL, UDIDL-UEIDL


2000 No MDG Link Version Response

1.3.6.1.4.1.161.3.3.2.2.14.1.4.103.1.n.m

ACG-genMDG

n=[1-34], m=[1/2]

Minor

EMPTY

CLEAR: ML_STM: UEIDL-UEA MCC_STM: UEIDL-UEA, UEIDL-UEIMP, UEIMP-UEA ACG_STM: UEIMP-UEA, UEA-UEIMP EBTS_STM: UEIMP-UEA, UEIDL-UEIMP,

Possible Causes:1. T1 or E1 physical or logical link is down 2. MDG powered off 3. MDG rebooted 4. MDG defective Actions:1. Establish T1 or E1 physical and logical link connection to MDG 2. Power on MDG 3. Wait for MDG to come up 4. Repair/replace/reboot MDG

RC

N U note:[1-34] indicates the MDG ID, where: = MDG ID that did not respond to the Link Version Request sent by ACG, 1 - 34



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

UEA-UEIMP


3000 No iVPU Link Version Response

1.3.6.1.4.1.161.3.3.2.2.14.1.4.104.1..

ACG_genIVPU

=[1-252],

=[1/2]

Major

3001

EMPTY Possible Causes:1. T1 physical or logical link is down 2. iVPU powered off 3. iVPU rebooted 4. iVPU defective Actions:1. Establish T1 physical and logical link connection to iVPU 2. Power on iVPU 3. Wait for iVPU to come up 4. Repair/replace/reboot iVPU

RC

N U note: and indicates iVPU ID, "1" - "252" that did not respond to the Link Version Request sent by ACG. indicates redundant status, Active ACG = "1", Standby ACG ="2".

qualityOfServiceFailureEvent

201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR not ready for testing: BMRT Task not initialized

Major

EMPTY

EMPTY Possible Causes:1. ACG has startup problem Actions: Wait for ACG to complete startup (when ACG is in UEIMP or UEA state)

R N U EMPTY


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR cannot test: Bad configuration or not all PCCH BR(s) are up

Major

EMPTY

EMPTY Possible Causes:1. BR cabinet and position in EBTS configuration is wrong 2. MOBIS and/or DAP links are down 3. Ethernet LAN physical or logical link is down 4. BRC powered off 5. BRC has self reset 6. PCCH or traffic BR recovery in progress 7. BRC defective Actions: 1. Reconfigure EBTS with correct BR cabinet and position 2. Notify a system engineer that the links are down 3. Establish Ethernet LAN physical and logical link connection to BRC 4. Power on BRC 5. Wait for BRC to transition to UEIMP or UEA state 6. Wait for CELL containing the BRC at cab and pos to transition to UEIMP or UEA state 7. Repair/replace BRC

R N U EMPTY


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BRC at cab and pos

Majo

EMPT

EMPTY Possible Causes:1. MOBIS and/or DAP links are down 2. Ethernet LAN physical or logical link is down 3. BRC

R N U where: = BRCs cabinet ID, 1- 8 = BRCs position ID, 1 - 6



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

failed to register or is locked.

r Y powered off 4. BRC has self reset 5. PCCH or traffic BR recovery in progress 6. BRC defective Actions:1. Notify a system engineer that the links are down 2. Establish Ethernet LAN physical and logical link connection to BRC 3. Power on BRC 4. Wait for BRC to transition to UEIMP or UEA state 5. Wait for CELL containing the BRC at cab and pos to transition to UEIMP or UEA state 6. Repair/replace BRC


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR received invalid PC request from BR

Major

EMPTY

EMPTY Possible Causes:1. PC service not active when user attempted to stop it 2. PC service active when they attempted to start it 3. Radio out of service and cannot perform request Actions:1. Check if someone using BMR mobile at the site 2. Need info from MS engineers

R N U where: = BRCs cabinet ID, 1- 8 = BRCs position ID, 1 - 6


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR received bad PC stop response from BR

Major

EMPTY

EMPTY Possible Causes:1. Private Call Stop Cause is user canceled 2. Private Call Stop Cause is radio time-out due to one or more of the following: DAP link down, BR receiver bad, BR transmitter bad, BR antenna bad, BMR antenna bad 3. Private Call Stop Cause is radio denies request 4. Private Call Stop Cause is target not responding indicates a DAP problem Actions:1. Make sure nobody is using the BMR mobile at the site 2. Check the DAP link, forward power on the indicated BR

R N U where: = BRC's cabinet ID, 1- 8 = BRCs position ID, 1 - 6



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

and the BMR antenna. If any of these are down or are not functioning properly, bring up, repair or replace as necessary 3. Check that BMR is properly provisioned in DAP, repair as necessary 4. Reconfigure DAP database such that the Target Fleet ID 65535 is reserved for BMR


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR not ready for test: waiting to get into single cell mode

Major

EMPTY

EMPTY Possible Causes:1. BR not transmitting 2. BMR antenna set-up improperly 3. BMR receiver defective Actions:1. Check forward power on BR. If problem persists, replace BR 2. Properly set-up and configure BMR antenna 3. Replace BMR (for VME) or iMU (for iSC)



201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR failed cell selection for BR

Major

EMPTY

EMPTY Possible Causes:1. BR not transmitting 2. BMR antenna set-up improperly Actions:1. Check forward power on BR. If problem persists, replace BR 2. Properly set-up and configure BMR antenna



201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR RNC does not match any cells RNCs

Major

EMPTY

EMPTY Possible Causes:1. Wrong BMR or cell RNC configured Action:1. Reconfigure EBTS with the correct BMR or cell RNC

R N U where: n = BMR Regional Network Code


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] GNP Reset: Auto Switch : acg_id

Major

EMPTY

EMPTY Configuration File too large. R Y U where ACG ID is the acgId configuration value, INDEX 1-6


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] GNP Reset: Manual Switch : acg_id

Major

EMPTY

EMPTY Tells why the ACG is about to do a redundancy action reset.

R Y U where ACG ID is the acgId configuration value, INDEX 1-2


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] GNP Reset: Bgdl Switch :

Maj

EMP





Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

acg_id

or

TY


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] GNP RESET: New active is old active : acg_id

Major

EMPTY




201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] GNP Reset: Invalid Ncarrier Carriers Site : acg_id

Major

EMPTY




201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] GNP Reset: Invalid Ncarrier Carriers Cell : acg_id

Major

EMPTY




201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] GNP Reset: DLX Config Fail : acg_id

Major

EMPTY




201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] Carrier Mean Ini , cell id , carrier id , cab , pos .

Major

EMPTY

EMPTY No action required. R N U where CMI = Carrier Mean Ini > 140, CELL is the cell instance 1-3, CARRIER is carrier id 1-36, CAB is the cabinet 1-8, and POS is the position 1-6.


201 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] ACG entered Level CPU access control mode

Major

EMPTY

EMPTY ACG entered CPU access control mode

R N U This new alarm text is an interim solution to provide a means of indicating that the ACG is performing CPU Access Control activities, without impacting the interface of OMC-R.


210 SCCH Failure 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY Number of SCCH Reduced Cell Current Num Scch

Major

EMPTY

EMPTY Possible Causes: hardware problem or misconfiguration

R N U =[1-3] =Current number of SCCH after reduction



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes


210 SCCH Failure 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY Number of SCCH Restored Cell

Clear

EMPTY

EMPTY No action required C N U =[1-3]


900 ISO Mode 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.n

BMR n = [1/2] ISO Mode Major

EMPTY

EMPTY OMC Automatically takes the necessary action for this alarm

RC

N U EMPTY


905 ACG LAPD Msg Dropped

1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.

BMR =[1/2]

Discarding LAPD msg for DAP

Warning

EMPTY

EMPTY Alarm Code Text will specify to what box the message was sent to. Possible Causes: ACG discarding a LAPD message due to LAPD Queue is overloaded. 1. Temporary link failure causes too many re-transmissions 2. Too many control messages from Sat-COW site

R N U note: indicates redundant status, Active ACG = '1", Standby ACG ="2". = "1" - "15".



1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.

BMR =[1/2]

Discarding LAPD msg for MDG

Warning

EMPTY


R N U note: indicates redundant status, Active ACG = '1", Standby ACG ="2". = "1" - "34".



1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.

BMR =[1/2]

Discarding LAPD msg for BSC

Warning

EMPTY

EMPTY Alarm Code Text will specify to what box the message was sent to. Possible Causes: ACG discarding a LAPD message due to LAPD Queue is overloaded. 1. Temporary link failure causes too many re-transmissions 2. Too many control messages from Sat-COW

R N U note: indicates redundant status, Active ACG = '1", Standby ACG ="2".



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

site qualityOfServiceFailureEvent


1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.

BMR =[1/2]

Discarding LAPD msg for OMC

Warning

EMPTY


R N U note: indicates redundant status, Active ACG = '1", Standby ACG ="2".

processingFailureEvent

2 GPS Version Mismatch

1.3.6.1.4.1.161.3.3.2.2.14.1.4.2.2.2.n

TFR/SRI n = [1/2] GPS Receiver SW ver is incompatible. Please update to ver or better.

Indeterminate

EMPTY

EMPTY Possible Causes:1. GPS Receiver does not have latest software version (should be at least 3.3 for VME or at least 8.3 for iSC) Actions:1. Update GPS Receiver to the appropriate latest software version (at least 3.3 for VME or 8.3 for iSC)

R N U EMPTY


1000 MS Message Routing DAP ID Range Conflict

1.3.6.1.4.1.161.3.3.2.2.14.1.4.101.1.1.n

ACG-genDAP

n = [1/2] : [ ...]

Critical

EMPTY

EMPTY Possible Causes:1. DAPs have conflicting MS message routing ranges Actions: 1. Reconfigure the ranges for those DAPs with conflicting ranges

RC

N U where: = DAP ID of DAP requesting the , 1-15 = the requested range, xx-xx (xx = 0x00-0x3F) = DAP ID(s) of DAP(s) that have previously requested at least one entry in this range, 1-15


1001 MS Defined In More Than One DAP HLR

1.3.6.1.4.1.161.3.3.2.2.14.1.4.101.1.1.n

ACG-genDAP

n = [1/2] ID TYPE= MS_ID=0x DAP_ID= [DAP_ID= ... DAP_ID=]

Minor

EMPTY

EMPTY Possible Causes:1. MS are defined in more than one DAP HLR Actions:1. Reconfigure the HLRs of those DAPs with same MS defined

R N U where: = IMEI or IMSI = IMEI or IMSI of the MS = DAP ID(s) of DAP(s) with MS defined in their HLR, 1-15

processingF 1002 ACG_DAP Link 1.3.6.1.4.1.161.3 ACG- n=[1-15], : M E REPORT Possible Causes:1. DAP has R N U note:n=[1-15] indicates the DAP



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

ailureEvent Version Check Fail .3.2.2.14.1.4.101.1.n.m

genDAP m=[1/2]

ajor

MPTY

: DL_STM: UEIDL-UEA, UEIDL-UEIMP DCC_STM: UEIDL-UEA, UEIMP-UEA, UEIDL-UEIMP, UEA-UEIMP ACG_STM: LEIDL-UEIDL, UEA-UEIMP, UEIMP-UEA EBTS_STM: UEA-UEIDL, UEIMP-UEIDL, UDIDL-UEIDL, UEIDL-UEIMP, UEA-UEIMP, UEIMP-UEA

version that is not supported by ACG Actions:1. Replace DAP and/or ACG software with versions that are compatible

ID. Alarm code text: = 1-15 DAP ID using unknown version, = Rxx.xx.xx (xx = 00-99)


1003 ACG_DAP Link Version Check Fail

1.3.6.1.4.1.161.3.3.2.2.14.1.4.101.1.n.m

ACG-genDAP

n=[1-15], m=[1/2]

:

Critical

EMPTY

REPORT: DL_STM: UEIDL-UEA, UEIDL-UEIMP DCC_ST

Possible Causes:1. Status field of the DAP version response message is FAIL Actions:1. Reconfigure DAP ID in DAP (or DAP DLCIs in ACG config) so that DAP IDs match 2. Replace DAP and/or ACG software with

R N U note:[1-15] indicates the DAP ID. Alarm Code Text: = DAP ID sending fail message, 1-15 = Rxx.xx.xx (xx = 00-99)



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

M: UEIDL-UEA, UEIMP-UEA, UEIDL-UEIMP, UEA-UEIMP ACG_STM: LEIDL-UEIDL, UEA-UEIMP, UEIMP-UEA EBTS_STM: UEA-UEIDL, UEIMP-UEIDL, UDIDL-UEIDL, UEIDL-UEIMP, UEA-UEIMP, UEIMP-UEA

versions that are compatible 3. Reconfigure ACG ID in ACG (or ACG DLCI in DAP config) so that ACG IDs match


1004 ACG_DAP Link Version Check Fail

1.3.6.1.4.1.161.3.3.2.2.14.1.4.101.1.n.m

ACG-genDAP

n=[1-15], m=[1/2]

Critical

EMPTY

REPORT: DL_STM: UEIDL-UEA, UEIDL-UEIMP DCC_STM: UEIDL-UEA, UEIMP-UEA, UEIDL-UEIMP,

Possible Causes:1. ACG ID in link version response message does not match the ID of this ACG due to invalid ACG to DAP DLCI mapping in the MPS (ITC header error) Actions:1. Reconfigure the MPS with the correct ACG to DAP DLCI mapping

RC

N U note:[1-15] indicates the DAP ID, where: = DAP ID sending invalid ITC header, 1 - 15



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

UEA-UEIMP ACG_STM: LEIDL-UEIDL, UEA-UEIMP, UEIMP-UEA EBTS_STM: UEA-UEIDL, UEIMP-UEIDL, UDIDL-UEIDL, UEIDL-UEIMP, UEA-UEIMP, UEIMP-UEA


1100 Incompatible subrate configuration between ACG and BSC

1.3.6.1.4.1.161.3.3.2.2.14.1.4.102.1.1.n

ACG-BSC

n = [1/2] CM: DS0 not configured as subrated voice

Indeterminate

EMPTY

EMPTY Possible Causes:1. Subrate configured in BSC, but not in ACG Actions:1. Download site with correct configuration

R N U where: = DS0 number


2002 ACG_MDG Link Version Check Fail

1.3.6.1.4.1.161.3.3.2.2.14.1.4.103.1.n.m

ACG-genMDG

n=[1-34], m=[1/2]

:

Minor

EMPTY

REPORT: ML_STM: UEIDL-UEA MCC_STM: UEIDL-UEA,

Possible Causes:1. MDG has version that is not supported by ACG Actions:1. Replace MDG and/or ACG software with versions that are compatible

R N U note:[1-34] indicates the MDG ID. where: = Rxx.xx.xx (xx = 00-99) = MDG ID using unknown version, 1-34



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

UEIDL-UEIMP, UEIMP-UEA ACG_STM: UEA-UEIMP, UEIMP-UEA EBTS_STM: UEIDL-UEIMP, UEA-UEIMP, UEIMP-UEA



1.3.6.1.4.1.161.3.3.2.2.14.1.4.103.1.n.m

ACG-genMDG

n=[1-34], m=[1/2]

:

Major

EMPTY

REPORT: ML_STM: UEIDL-UEA MCC_STM: UEIDL-UEA, UEIDL-UEIMP, UEIMP-UEA ACG_STM: UEA-UEIMP, UEIMP-UEA EBTS_STM: UEIDL-UEIMP, UEA-UEIMP, UEIMP-UEA

Possible Causes:1. Status field of the MDG version response message is FAIL Actions:1. Reconfigure MDG ID in MDG (or MDG DLCIs in ACG config) so that MDG IDs match 2. Replace MDG and/or ACG software with versions that are compatible 3. Reconfigure ACG ID in ACG (or ACG DLCI in MDG config) so that ACG IDs match

R N U note:[1-34] indicates the MDG ID. where: = Rxx.xx.xx (xx = 00-99) = MDG ID using unknown version, 1-34



1.3.6.1.4.1.161.3.3.2.2.14.1.4.103.1.n.m

ACG-genMDG

n=[1-34], m=[1/2]

Cri

EMP

REPORT: ML_STM

Possible Causes:1. ACG ID in link version response message does not match the

R N U note:[1-34] indicates the MDG ID. where: = MDG ID sending invalid ITC



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

tical

TY

: UEIDL-UEA MCC_STM: UEIDL-UEA, UEIDL-UEIMP, UEIMP-UEA ACG_STM: UEA-UEIMP, UEIMP-UEA EBTS_STM: UEIDL-UEIMP, UEA-UEIMP, UEIMP-UEA

ID of this ACG due to invalid ACG to MDG DLCI mapping in the MPS Actions:1. Reconfigure the MPS with the correct ACG to MDG DLCI mapping

header, 1 - 34


2012 Invalid Packet Data Configuration

1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.n.1.m

GenACG n=[1-3], m=[1/2]

Major

EMPTY

EMPTY Possible Causes:1. MDG DLCIs in ACG configuration are wrong. No MDG is configured for the site, but PCHs are configured for a particular cell Actions:1. The site will not provide Packet Data service. No PCHs will be assigned in the site. Reconfigure EBTS with the correct MDG DLCIs and number of PCHs

R N U note:[1-3] indicates the Cell ID. where: = Cell ID with non-zero number of PCHs configured, 1 - 3


2013 Total Min PCH Size Scaled

1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.n.1.1

GenACG n=[1-3] ,

, , , ,



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

carriers in service>

te

NOT occur or remain uncleared when the cell is in the active state Actions:1. No action required 2. Check the EBTS configuration and/or correct PCH minimums

Carriers> = Carriers configured for the cell, 1 - 20 = Number of Carriers that were in service in the cell when this condition was detected.


2014 Invalid WiDEN BR Configuration

1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.n.1.1

GenACG n=[1-3] Major

EMPTY

EMPTY Possible Causes: 1) More than one WiDEN BR per cell. 2) PCCH assigned to WiDEN BR and the number of WiDEN carriers is the same as the configured number of carriers in the WiDEN Quad BRC. 3) Single carrier BR is configured with non-zero widenCarriers. 4) WiDEN Shared BR band is not primaryBand Actions: 1) Modify config such that there is only one WiDEN BR per cell. 2) Modify config such that single carrier BR has zero widenCarriers. 3) Modify config such that WiDEN Shared BR is primaryBand.

RC

N U note:n=[1-3], (cabinet in Alarm) indicates the Cell ID.


2020 RAG Update Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.103.1.n.m

GenACG n=[1-34], m=[1/2]

, 0x, , , , 0x,

Critical

EMPTY

EMPTY Possible Causes:1. MDG is out of synch with the OMC 2. Invalid RAG to MDG mapping configured in the OMC Actions:1. Reset MDG 2. Reconfigure the MDG( s) with the correct RAG( s)

RC

N U note:n=[1-34] indicates MDG ID. Alarm Code Text:: = Requesting MDG ID, 1 - 34, = MDG ID1s timestamp, = RAG ID which is claimed by more than one MDG, 0-31, = the operation MDG ID1 attempted, where: 1 = unclaim, 2 = inactivate, 3 = activate, = RAG owners MDG ID, 1 - 34, otherwise 0, = MDG ID2s timestamp, if the RAG was owned, otherwise, timestamp of the last successful unclaim command on the RAG, = RAG state, where: 1 = inactive, 2 =



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

active, 3 = unclaimed processingFailureEvent

2021 RAG Update Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.103.1.n.m

GenACG n=[1-34], m=[1/2]

, 0x,

Critical

EMPTY

EMPTY Possible Causes:1. MDG is defective Actions:1. Reset/repair/replace MDG

R N U note:[1-34] indicates the MDG ID. where: = MDG ID sending invalid number of timestamps, 1 - 34


3001 iVPU Link Hardening Failure

1.3.6.1.4.1.161.3.3.2.2.14.1.4.104.1..

ACG_genIVPU

=[1-252],

=[1/2]

Major

3000, 3002, 3003, 3004

EMPTY Possible Causes: T1 is in loopback mode. Actions: Check condition of physical T1 link

R N U note: and indicates the iVPU ID, "1"-"252", = "no response". indicates redundant status, Active ACG = "1", Standby ACG = "2".



1.3.6.1.4.1.161.3.3.2.2.14.1.4.104.1..

ACG_genIVPU

=[1-252],

=[1/2]

Major

3000, 3002, 3003, 300

EMPTY Possible Causes: Misconfiguration of iVPU ID Actions: Reconfigure iVPU ID.

R N U note: and indicates the iVPU ID, "1"-"252". indicates the wrong iVPU ID, "1" - "252". indicates redundant status, Active ACG = "1", Standby ACG = "2".



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

4 processingFailureEvent


1.3.6.1.4.1.161.3.3.2.2.14.1.4.104.1..

ACG_genIVPU

=[1-252],

=[1/2]

Clear

3000, 3002, 3003, 3004

EMPTY iVPU ID configuration synchronized.

C N N note: and indicates the iVPU ID, "1"-"252". indicates the wrong iVPU ID, "1" - "252". indicates redundant status, Active ACG = "1", Standby ACG = "2".



1.3.6.1.4.1.161.3.3.2.2.14.1.4.104.1..

ACG_genIVPU

=[1-252],

=[1/2]

Major

3000, 3002, 3003, 3004

EMPTY Possible Cause: New ACG site was added or site ID was changed.

R N N note: indicates the iVPU ID, "1"-"252". indicates the wrong ACG ID, "1" - "10000". indicates redundant status, Active ACG = "1", Standby ACG = "2".



1.3.6.1.4.1.161.3.3.2.2.14.1.4.104.1..

ACG_genIVPU

=[1-252],

=[1/2]

Clear

3000, 30

EMPTY Site ID configuration synchronized.

C N N note: indicates the iVPU ID, "1"-"252". indicates the wrong ACG ID, "1" - "10000". indicates redundant status, Active ACG = "1", Standby ACG = "2".



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

02, 3003, 3004


3002 ACG_iVPU Link Version Check Fail

1.3.6.1.4.1.161.3.3.2.2.14.1.4.104.1..

ACG_genIVPU

=[1-252],

=[1/2]

Major

3001

EMPTY Possible Causes:1. iVPU has version that is not supported by ACG Actions:1. Replace iVPU and/or ACG software with versions that are compatible

R N U note: and indicates the iVPU ID, "1"-"252". = Rxx.xx.xx (xx = 00-99) . indicates redundant status, Active ACG = "1", Standby ACG = "2".



1.3.6.1.4.1.161.3.3.2.2.14.1.4.104.1..

ACG_genIVPU

=[1-252],

=[1/2]

Critical

3001

EMPTY Possible Causes:1. Status field of the iVPU version response message is FAIL Actions:1. Replace iVPU and/or ACG software with versions that are compatible 2. Reconfigure ACG ID or iVPU ID

R N U note: and indicates the iVPU ID, "1"-"252". = Rxx.xx.xx (xx = 00-99). indicates redundant status, Active ACG = "1", Standby ACG ="2".



1.3.6.1.4.1.161.3.3.2.2.14.1.4.104.1..

ACG_genIVPU

=[1-252],

=[1/2]

Critical

3001

EMPTY Possible Causes:1. ACG ID in link version response message does not match the ID of this ACG.

R N U note: and indicates the iVPU ID sending invalid ITC header, "1"-"252". indicates redundant status, Active ACG = "1", Standby ACG ="2".

equipmentFailureEvent

201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.n

GenACG n = [1/2] FIRST TIME BOOTED - NO PREVIOUS RESET ERROR ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset

C Y U note: 1= iSC2, 2= iSC3



GenACG n = [1/2] ACG RESET: CORRUPTED DATA IN

Cri

EMP


C Y U note: 1= iSC2, 2= iSC3 This alarm code text does not



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

RESET INFO ?

tical

TY

indicate why the ACG reset. Rather, it indicates that the stored reset reason is corrupt.



GenACG n = [1/2] INDETERMINATE RESET ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset. ACG lost power before it was able to record a reset reason. In most cases, this is due to either power or temperature issues at the site. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details.




GenACG n = [1/2] WDOG RESET ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset ACG was about to hang due to an overload on the processor. On an iSC2 with a high number of carriers, this may be because there is simply too much traffic for the hardware to handle. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details.

C Y U note: 1= iSC2, 2= iSC3, Reset Info - internal info about the watchdog reset.



GenACG n = [1/2] ? ERR EX= TSK= MSR= CR= PC= R3/4=/



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

4> (for iSC) equipmentFailureEvent


GenACG n = [1/2] ACG SM Initiated ACG Reset: Unable to start CRM ?

Critical

EMPTY





GenACG n = [1/2] ACG SM Initiated ACG Reset: T1/E1 config block read failed ?

Critical

EMPTY





GenACG n = [1/2] ACG SM Initiated ACG Reset: DLCI retrieval failed ?

Critical

EMPTY





GenACG n = [1/2] ACG SM Initiated ACG Reset: DLX configuration failed. ?

Critical

EMPTY





GenACG n = [1/2] ACG SM Initiated ACG Reset: CM failure while loading IC ?

Critical

EMPTY





GenACG n = [1/2] ACG SM Initiated ACG Reset: Engine failure while allocating

Criti

EMPTY





Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

memory ?

cal



GenACG n = [1/2] ACG CM Initiated Reset: Maximum Number of T1/ E1 lines should be 1 on iSC2 ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration. Possible Causes:1. The number of T1/E1 links is NOT set to 1 (or is greater than 2) in the EBTS configuration for this iSC2 (or iSC III) site. Actions:1. Change the number of T1/E1 links to 1 (or to 2 or less) in the EBTS worksheet configuration for this iSC2 (or iSC III) site. The parameter name is numberOfT1. Redownload the new configuration to this iSC2 (or iSC III) site




GenACG n = [1/2] ACG CM Initiated Reset: Maximum Number of T1/E1 lines should be 2 on iSC III ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration. Possible Causes:1. The number of T1/E1 links is NOT set to 1 (or is greater than 2) in the EBTS configuration for this iSC2 (or iSC III) site. Actions:1. Change the number of T1/E1 links to 1 (or to 2 or less) in the EBTS worksheet configuration for this iSC2 (or iSC III) site. The parameter name is numberOfT1. Redownload the new configuration to this iSC2 (or iSC III) site




GenACG n = [1/2] ACG CM Initiated Reset: Interconnect Subrate pools

Criti

EMPTY

EMPTY Download site with correct configuration




Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

overlap ?

cal



GenACG n = [1/2] ACG CM Initiated Reset: Interconnect Subrate pools past end of T1/E1 ?

Critical

EMPTY





GenACG n = [1/2] ACG CM Initiated Reset: Interconnect Subrate pools use DS0 1 or 17 on E1 ?

Critical

EMPTY





GenACG n = [1/2] ACG CM Initiated Reset: More than 2 interconnect Subrate pools on a span ?

Critical

EMPTY





GenACG n = [1/2] ACG CM Initiated Reset: Line number for a link should be 1 on iSC2 ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration. Possible Causes:1. The T1/E1 card number carrying the channel (ds0) for a channel type (Interconnect, OMC-R or Dispatch) is NOT set to 1 in the EBTS configuration for this iSC2 site. Actions:1. Change the T1/E1 card number for a channel type (Interconnect, OMC-R or Dispatch) to 1 in the EBTS worksheet




Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

configuration for this iSC2 site. The parameter name is chanCard. Redownload the new configuration to this iSC2 site



GenACG n = [1/2] ACG CM Initiated Reset: 'INFO' Region depleted, config too large. ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration. Possible Causes:1. The T1/E1 card number for a carriers subrates is NOT set to 1 in the EBTS configuration for this iSC2 site. Actions:1. Change the T1/E1 card number for a carriers subrates to 1 in the EBTS worksheet configuration for this iSC2 site. The parameter name is t1Number. Redownload the new configuration to this iSC2 site




GenACG n = [1/2] ACG CM Initiated Reset: Tuple limit exceeded, config too large. ?

Critical

EMPTY

EMPTY Too many configuration parameters.




GenACG n = [1/2] ACG CM Initiated Reset: Line number for subrate should be 1 on iSC2 ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration. Possible Causes:1. The T1/E1 card number for a carriers subrates is NOT set to 1 in the EBTS configuration for this iSC2 site. Actions:1.




GenACG n = [1/2] ACG CM Initiated Reset: Frame Relay must

Crit

EMPT

EMPTY No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration.




Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

begin on 1st DS0 of 2nd T1/E1 ?

ical

Y Possible Causes:1. The Frame Relay channel may not be configured at beginning DS0 on 2nd T1/E1 for an iSC III site. Actions:1. Change the Frame Relay channel to be configured at beginning DS0 on 2nd T1/E1 for iSC III EBTS site. Redownload the new configuration to this site



GenACG n = [1/2] ACG SM Initiated Reset: Max number of carriers should be 24 on iSC2 ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration. Possible Causes:1. The total number of carriers exceeds the maximum in the EBTS configuration for this site. The maximum number of carriers for a site is 24 for an iSC2 site and 36 for an iSC III site. Actions:1. Change the total number of carriers to 24 for iSC2 or 36 for iSC III for this EBTS site. Redownload the new configuration to this site




GenACG n = [1/2] ACG SM Initiated Reset: Max number of carriers should be 36 on iSC III ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration. Possible Causes:1. The total number of carriers exceeds the maximum in the EBTS configuration for this site. The maximum number of carriers for a site is 24 for an iSC2 site and 36 for an iSC III site. Actions:1. Change the total number of carriers to 24 for iSC2 or 36 for iSC III for this EBTS site. Redownload the new configuration to this site


equipmentF 201 ACG Reset Reason 1.3.6.1.4.1.161.3 GenACG n = [1/2] ACG SM C E EMPTY No action required. FYI only C Y U note: 1= iSC2,



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

ailureEvent .3.2.2.14.1.4.100.1.1.n

Initiated Reset: Max carriers per cell should be 20 (omni) on iSC2 ?

ritical

MPTY

- This alarm indicates that an EBTS reset occurred due to invalid ACG configuration. Possible Causes:1. The total number of carriers exceeds the maximum in the EBTS configuration for a cell in this site. The maximum number of carriers for a cell is 12 for an iSC2 site and 18 for an iSC III site. The maximum number of carriers for an omni site is 20. Actions:1. Change the total number of carriers in a cell to 12 (or 20 for omni) for iSC2 or 18 (or 20 for omni) for iSC III for this EBTS site. Redownload the new configuration to this site

2= iSC3



GenACG n = [1/2] ACG SM Initiated Reset: Max carriers per cell should be 20 (for omni) on iSC III ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration. Possible Causes:1. The total number of carriers exceeds the maximum in the EBTS configuration for a cell in this site. The maximum number of carriers for a cell is 12 for an iSC2 site and 18 for an iSC III site. The maximum number of carriers for an omni site is 20. Actions:1. Change the total number of carriers in a cell to 12 (or 20 for omni) for iSC2 or 18 (or 20 for omni) for iSC III for this EBTS site. Redownload the new configuration to this site




GenACG n = [1/2] GNP software reset requested with indeterminate reason.

Criti

EMPTY





Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

?

cal



GenACG n = [1/2] GNP RAM Reset requested with indeterminate reason. ?

Critical

EMPTY




201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY Stby ACG Initiated Switch: Active ACG Communication Down ?

Critical

EMPTY

EMPTY Possible Causes:1. ACG hardware failure Actions:1. Repair/replace old Active ACG



201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY OMC Initiated Switch: old Stby is new Active ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset. OMC requested site to switch standby to run as active.

C Y U where: = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16), = Reason for recovery: 21 - 29, 1= iSC2, 2= iSC3


201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY OMC Initiated Switch: old Active is new Active ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset. OMC requested site to switch standby to run as active, however, the action was unsuccessful.



201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY ACG Initiated Switch: old Stby is new Active ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset. Depending on the value of , one of two reset scenarios is possible: =25, 32, 42, or 44 - EBTS reset due to GPS failure. This may include loss of satellite visibility or bad GPS hardware.

C Y U where: = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16) = Reason for recovery: 00 - 99, 1= iSC2, 2= iSC3



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

=41 or 43 - EBTS reset due to loss of T1/E1 for 60 consecutive minutes. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details.


201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY ACG Initiated Switch: old Active is new Active ?, 1= iSC2, 2= iSC3

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset. Depending on the value of , one of two reset scenarios is possible: =25, 32, 42, or 44 - EBTS reset due to GPS failure. This may include loss of satellite visibility or bad GPS hardware. =41 or 43 - EBTS reset due to loss of T1/E1 for 60 consecutive minutes. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details.

C Y U where: = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16) = Reason for recovery: 00 - 99, 1= iSC2, 2= iSC3


201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY ACG Initiated Recovery: old Standby is new Active ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset. Active ACG failed during boot/download, and standby ACG recovered as active.



201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY ACG Initiated Recovery: old Active is new Active ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset Both ACGs at the site attempted to run as active at the same time.

C Y U where: = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16), 1= iSC2, 2= iSC3


201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY OMC Requested EBTS Reset ?

Criti

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset. Possible Causes:1) OMC initiated reset of EBTS




Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

cal


201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY ACG Initiated Switch: Software Memory Corruption, old Stby is new Active ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset. Possible Causes:1) File Corruption



201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY ACG CM Initiated Reset: Insufficient memory ?

Critical

EMPTY

EMPTY No action required FYI only - This alarm indicates why EBTS reset. Possible Cause: 1) ACG cannot allocate memory for T1 initialization.



201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY ACG CM Initiated Reset: Begin channel number shouldn't be 0 ?

Critical

EMPTY

EMPTY No action required FYI only - This alarm indicates why EBTS reset. Cause: 1) The beginning channel number for a T1 config cannot be zero



201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.

GenACG =[1/2]

ACG SM Initiated Reset: Mismatched Backhaul Mode - ?

Critical

EMPTY

EMPTY No action required. FYI only - This alarm indicates why EBTS reset. Backhaul method negotiated upon initialization does not match that negotiated before download.

C Y U note: and indicates the backhaul configuration type, Split Backhaul Mode = "SPLIT", All Frame Relay ="AFR". indicates redundant status, Active ACG = "1", Standby ACG ="2", 1= iSC2, 2= iSC3


201 ACG Reset Reason 1.3.6.1.4.1.161.3.3.2.2.14.1.4.100.1.1.1

GenACG EMPTY ACG SM Initiated Reset: RFDS value should be 1 for iSC2 ?

Critical

EMPTY

EMPTY No action required FYI only - (for iSC2)This alarm indicates why EBTS reset. Cause: 1) rfdstype should be 1 for iSC2 platform




Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes


202 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR Failed to respond to a cell selection on BR

Major

EMPTY

EMPTY Possible Causes (for VME or iSC2 only):1. BMR cannot register 2. BMR (for VME) or iMU (for iSC2) defective. Actions:1. Check if BMR is in the DAP database. If this alarm occurs repeatedly, Power Cycle the BMR (for VME) or iMU (for iSC2). If the alarm still occurs, Master Reset the BMR (for VME) or iMU (for iSC2) 2. Replace BMR (for VME) or iMU (for iSC2)

C N U EMPTY


202 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR failed to send PC Start response on BR

Major

EMPTY

EMPTY Possible Causes (for VME or iSC2 only):1. BMR cannot register 2. BMR (for VME) or iMU (for iSC2) defective. Actions:1. Check if BMR is in the DAP database. If this alarm occurs repeatedly, Power Cycle the BMR (for VME) or iMU (for iSC2). If the alarm still occurs, Master Reset the BMR (for VME) or iMU (for iSC2). 2. Replace BMR (for VME) or iMU (for iSC2)



202 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR failed to send PC Stop response on BR

Major

EMPTY

EMPTY Possible Causes (for VME or iSC2 only):1. BMR cannot register. 2. BMR (for VME) or iMU (for iSC2) defective. Actions:1. Check if BMR is in the DAP database. If this alarm occurs repeatedly, Power Cycle the BMR (for VME) or iMU (for iSC2). If the alarm still occurs, Master Reset the BMR (for VME) or iMU (for iSC2) 2. Replace BMR (for VME) or iMU (for iSC2)



202 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR reset unexpectedly

Majo

EMPT

EMPTY Possible Causes (for VME or iSC2 only):1. BMR reset while processing a RAP IO test request.2. BMR (for

R N U EMPTY



Alarm Type

Alarm Code


MOI Info

(Label) Inst Alarm

Code Text

Severity

Related Alarms

Related State

ChangesRemedy Re

port & Clear

Outage Y/N

Change Status

Comments & Notes

r Y VME) or iMU (for iSC2) defective. Actions:1. If this alarm occurs repeatedly, Power Cycle the BMR (for VME) or iMU (for iSC2). If alarm still occurs, Master Reset the BMR (for VME) or iMU (for iSC2). 2. Replace BMR (for VME) or iMU (for iSC2)


202 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR not ready for test: waiting for initial comm enable response

Major

EMPTY

EMPTY Possible Causes (for VME or iSC2 only):1. ACG waiting for response from a communication enable request from BMR. 2. BMR (for VME) or iMU (for iSC2) defective. Actions: 1. If this alarm occurs repeatedly, Power Cycle the BMR (for VME) or iMU (for iSC2). If alarm still occurs, Master Reset the BMR (for VME) or iMU (for iSC2). 2. Replace BMR (for VME) or iMU (for iSC2).

R N U EMPTY


202 ACG BMR Error 1.3.6.1.4.1.161.3.3.2.2.14.1.4.8.1.1.n

BMR n = [1/2] BMR not ready for test: waiting for BMR to reset

Major

EMPTY

EMPTY Possible Causes (for VME or iSC2 only):1. BMR waiting for response before proceeding (occurs after a successful reset). 2. BMR (for VME) or iMU (for iSC2) defective. Actions:1. If alarm occurs repeatedly, Power Cycle the BMR (for VME) or iMU (for iSC2). If alarm still occurs, Master Reset the BMR (for VME) or iMU (for iSC2). 2. Replace BMR (

1000p20b

Documents

copyrighted motorola

property of motorola

purchase of motorola

software sw products

sw computer programs

copyrighted computer

party sw supplier

computer language