1000 P 20 B

Technical Manual
iDEN 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 Copyrights The 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. 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.
2008 - Motorola, Inc. All Rights Reserved
REV 12/15/06
Contact Information Motorola, Inc. Networks business 1501 Shure Dr. Arlington Heights, IL 60004 U.S.A
SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE.
Table of Contents
Introduction
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 How to Use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Interpreting Alarm Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Interpreting Event Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
CCPHA DAP
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPHA DAP-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPHA DAP-25 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPHA DAP-38
CCPiHLR
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPiHLR-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPiHLR-19 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPiHLR-25
ACG
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACG-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACG-55 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACG-72
iCP
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iCP-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iCP12 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iCP-23
APD
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APD-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APD-5 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . APD-9
iDAC
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iDAC-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iDAC-5 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iDAC-12
BRC
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BRC-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BRC-23 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BRC-26
iSG
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iSG-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iSG-9 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iSG-17
BSC
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC-53 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC-72
iVPU
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iVPU-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iVPU-77 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iVPU-98
CCPDAP
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPDAP-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPDAP-23 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CCPDAP-37
SR17.0 30-Oct-08
6871000P20-B
iDEN Alarm and State Change Event Reference Manual iii
Table of Contents
MDG2
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG2-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG2-77 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG2-84
MDG4
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG4-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG4-76 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MDG4-86
OMC-R
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R-26 Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . OMC-R-36
SSC
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSC-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSC-11 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSC-18
VSGW
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSGW-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSGW-41 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . VSGW-73
3gXCDR
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XCDR-1 State Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XCDR-31 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XCDR-53
iDEN Alarm and State Change Event Reference Manual iv
6871000P20-B
SR17.0 30-Oct-08
Introduction
Overview
Many iDEN Network Elements (NEs) report status messages to the OMC-R where they are received and stored for historical reference. These status messages may be used to aid in system troubleshooting and diagnostics. Each status message falls into one of the following three major categories: Alarms An occurrence or change in the operating state of the network or NEs that is significant enough to be displayed for the attention of the operator. Alarms are both system defaults and defined by the operator(s) and are classified by severity. For more details, refer to the OMC-R Event Alarm Management manual (6871000P16). State Changes Changes in the operation condition of the network or NE. (e.g., from active to standby). Events Events that occur that are not Alarms nor state changes that provide information to the operator.
How to Use this Manual

This manual is System Release specific. The sections of the manual are organized by the major NEs that report the alarm, state change, or event. Each section contains tables that summarize the OMC-R reporting activities for that NE. The following NEs report their status to the OMC-R: ACG iDAC APD iSG BRC iVPU BSC MDG2 CCPDAP MDG4 CCPHADAP OMCR CCPiHLR SSC iCP VSGW 3gXCDR Important This version of this manual supersedes all versions prior to 30-Oct-08.
SR17.0 30-Oct-08
6871000P20-B
iDEN Alarm and State Change Event Reference Manual 1
Interpreting Alarm Tables

Each column of the Alarm tables contains the following information: Table 1:
Column Alarm Code OMC Text MOI Info (ID) MOI Info (Label) Inst Alarm Code Text The identifier that uniquely identifies this alarm. The text the alarm uses to report to the OMC-R. The Managed Object Instance (MOI) identifier used by the particular portion of the NE to identify itself (e.g., cabinet, cage, slot position). 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. Additional information about the alarm. One of the following 6 severity levels:
Alarm Table Column Heading Descriptions

Description
1. Clear One or more previous alarms have been resolved (alarm condition no longer exists). Some alarms cannot be cleared. 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 avoid service-affecting conditions.
Severity
4. Minor A fault condition that does not affect service has been detected. Corrective action should be taken to prevent an interruption of service. 5. Major A service-affecting condition exists. Service is impaired or reduced. Immediate corrective action is required. For example, part of an NE has
stopped working properly but the rest of the NE is still functioning.
6. Critical A significant service-affecting fault condition exists that requires immediate action. This level usually indicates that facilities connections,
or all or a large portion of an NE is not in service. Related Alarms Related State Changes Remedy The Alarm codes that, when combined, may result in this alarm. The reason code(s) that could occur at the NE that may result in this Alarm. Possible corrective action(s) for the alarm.
6871000P20-B
SR17.0 30-Oct-08
Table 1:
Column
Alarm Table Column Heading Descriptions (continued)

Description Alarms may only announce themselves. This column indicates one of the following:
Report & Clear
R (Report) Removes previous alarms C (Clear) Alarm has been cleared RC (Report and Clear)
Whether the alarm is service-affecting: Outage

Yes An outage may occur. No An outage will not occur.
Change Status Comments & Notes
Whether the alarm has changed from the previous software release. If D, then this alarm will be removed in the next release. Additional comments/information that may be useful in understanding and connecting the alarm to actual events and operating conditions of the network.
SR17.0 30-Oct-08
6871000P20-B
Interpreting Event Tables

Each column of the Event tables contains the following information Table 2:
Column Reason Code OMC Text MOI Info (ID) MOI Info (Label) Inst From State To State Related State Changes Related Alarms Event Description An identifier that uniquely identifies the State Change and/or Event. The text the alarm uses to report to the OMC-R. The Managed Object Instance (MOI) identifier used by the particular portion of the NE to identify itself (e.g., cabinet, cage, slot position). The label (name) assigned to the alarm-reporting device. Additional MOI information: the device instance that further identifies the source of the alarm. The nature of the change:

Event Table Column Heading Descriptions

Description
From State The initial operating state. To State The state produced by the change.
The reason code(s) that could occur at the NE that may result in this Event. The Event codes that, when combined, may result in this Event. A general description of the change in operating conditions. Whether the event is service-affecting:
Outage
Yes An outage may occur. No An outage will not occur.
Change Status Comments & Notes
Whether the event has changed from the previous software release. If D, then this event will be removed in the next release. Additional comments/information that may be useful in understanding and connecting the event to actual events and operating conditions of the network.
6871000P20-B
SR17.0 30-Oct-08
Release SR17.0
________________________________ Alarms
Alarm Type
Alarm Code
ACG
Remedy
R e p o r t O u t a g e C h a n g e S t a t u s U note:m[1-2] indicates the T1/E1 link ID
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
S e v e r i t y
R e l a t e d
Related State Changes
Comments & Notes
communicat ionFailureE vent
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 <number> is down.
A l a r m s W E a M r P n T i Y n g
EMPTY
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 <number> is up. EMPTY
communicat ionFailureE
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]
C l e a r M i
E M P T Y E M
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. No action required
& Y / C N l e a r R N
C N U
note:m[1-2] indicates the T1/E1 link ID.
EMPTY
Possible Causes (for VME or ISC2 only):1. BMR (for VME)
R N U
EMPTY
October 30, 2008
ACG-1

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
C h a n g e S t a t u s
Comments & Notes
vent
1.n
A l a r m s n P o T r Y
& Y / C N l e a r 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) 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) Possible Causes:1. TFR (for VME) or SRI (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
M a j o r
E M P T Y
EMPTY
R N U C
EMPTY
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
C E r M
EMPTY
R N U C
EMPTY
ACG-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

OMC Text MOI Info (Id)
MOI Info (Label) Inst
Alarm Code Text
S e v e r i t y
R e l a t e d A l a r m s P T Y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r 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). 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
vent
Fault
2.n
i t i c a l
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
I n d e t e r m i n a t e
E M P T Y
REPORT : ACG_ST M: UEAUEIDL, UEAUEIMP, UEIMPUEIDL EBTS_S TM: UEAUEIDL, UEAUEIMP, UEIMPUEIDL CLEAR: ACG_ST M: LEIDLUEIDL, UEIMP-
R N U C
EMPTY
October 30, 2008
ACG-3

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s UEA EBTS_S TM: UEAUEIDL, UEIMPUEIDL, UDIDLUEIDL, UEIMPUEA REPORT : CELL_S TM: LEIDLLDIDL, UEIDLUDIDL, UEAUDIDL, UEIMPUDIDL, UEAUEIMP, UEIDLLEIDL ACG_ST M: UEIDLUDIDL, UEAUEIDL, UEAUEIMP, UEIDLLEIDL, UDIDLLDIDL, UEIDLUEIMP, UEAUEIMP, UEAUDIDL, UEARelated State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
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 <BRC Physical ID>
C r i t i c a l
E M P T Y
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 Physical ID> = BRC's combined cabinet and position ID, 11 86 = Type of the BR: 1 = Legacy BR, 3 = Quad BR
ACG-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
R e l a t e d A l a r m s
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r UEIMP, UEIMPUDIDL, UEIMPUEIDL, UEIDLLEIDL, UDIDLLDIDL, LEIDLUEIDL, UDIDLUEIDL EBTS_S TM: UEAUEIDL, UEIMPUEIDL, UDIDLUEIDL, UEIDLUEIMP, UEAUEIMP, UEIDLUDIDL, UEAUDIDL, UEIMPUDIDL EMPTY
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]
1000
No DAP Link Version Response
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.101 .1.n.m
ACGgenDAP
n=[1-15], m=[1/2]
ACG-BRC LAPD link established for BRC <BRC Physical ID> <DAP ID>
C l e a r M a j o r
E M P T Y E M P T Y
No action required.
C N U
where: <BRC Physical ID> = BRC's combined cabinet and position ID, 11 - 86
CLEAR: DL_STM: UEIDLUEA, UEIDLUEIMP DCC_ST M: UEIDLUEA,
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
R N U C
note:[1-15] indicates the DAP ID, where:<DAP ID> = DAP ID of the DAP that did not respond to the Link Version Request sent by ACG, 1 - 15
October 30, 2008
ACG-5

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s UEIDLUEIMP, UEIMPUEA, UEAUEIMP ACG_ST M: LEIDLUEIDL, UEAUEIMP, UEIMPUEA EBTS_S TM: UEAUEIDL, UEIMPUEIDL, UDIDLUEIDL CLEAR: ML_STM : UEIDLUEA MCC_ST M: UEIDLUEA, UEIDLUEIMP, UEIMPUEA ACG_ST M: UEIMPUEA, UEAUEIMP EBTS_S TM: UEIMPUEA, UEIDLUEIMP, Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
2000
No MDG Link Version Response
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.103 .1.n.m
ACGgenMDG
n=[1-34], m=[1/2]
<MDG ID>
M i n o r
E M P T Y
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
R N U C
note:[1-34] indicates the MDG ID, where:<MDG ID> = MDG ID that did not respond to the Link Version Request sent by ACG, 1 - 34
ACG-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r UEAUEIMP EMPTY
3000
No iVPU Link Version Response
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.104 .1.<POS>.<RED S>
ACG_ge nIVPU
<POS>=[ 1-252], <REDS> =[1/2]
<iVPU ID>
M a j o r
3 0 0 1
qualityOfSer viceFailureE vent
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]
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 BMR cannot test: Bad configuration or not all PCCH BR(s) are up
M a j o r M a j o r
E M P T Y E M P T Y
EMPTY
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 <Cabinet> and pos <Position>
M a j o
E M P T
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 Possible Causes:1. ACG has startup problem Actions: Wait for ACG to complete startup (when ACG is in UEIMP or UEA state) 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 <Cabinet> and pos <Position> to transition to UEIMP or UEA state 7. Repair/replace BRC Possible Causes:1. MOBIS and/or DAP links are down 2. Ethernet LAN physical or logical link is down 3. BRC
R N U C
note: <POS> and <iVPU ID> indicates iVPU ID, "1" - "252" that did not respond to the Link Version Request sent by ACG. <REDS> indicates redundant status, Active ACG = "1", Standby ACG ="2".
R N U
EMPTY
R N U
EMPTY
R N U
where:<Cabinet> = BRCs cabinet ID, 1- 8<Position> = BRCs position ID, 1 - 6
October 30, 2008
ACG-7

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r 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 <Cabinet> and pos <Position> to transition to UEIMP or UEA state 6. Repair/replace BRC 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 Possible Causes:1. Private Call Stop Cause <06> is user canceled 2. Private Call Stop Cause <07> 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 <08> is radio denies request 4. Private Call Stop Cause <13> 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
failed to register or is locked.
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 <Cabinet> <Position>
M a j o r
E M P T Y
EMPTY
R N U
where:<Cabinet> = BRCs cabinet ID, 1- 8<Position> = 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 <Private Call Stop Cause> from BR <Cabinet> <Position>
M a j o r
E M P T Y
EMPTY
R N U
where:<Cabinet> = BRC's cabinet ID, 1- 8<Position> = BRCs position ID, 1 - 6
ACG-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r 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 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) 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 Possible Causes:1. Wrong BMR or cell RNC configured Action:1. Reconfigure EBTS with the correct BMR or cell RNC Configuration File too large.
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
M a j o r
E M P T Y
EMPTY
R N U
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 <Cabinet> <Position>
M a j o r
E M P T Y
EMPTY
R N U
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 <n> does not match any cells RNCs GNP Reset: Auto Switch <INDEX>: acg_id <ACG ID> GNP Reset: Manual Switch <Index>: acg_id <ACG ID> GNP Reset: Bgdl Switch <INDEX>:
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]
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]
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]
M a j o r M a j o r M a j o r M a j
E M P T Y E M P T Y E M P T Y E M P
EMPTY
R N U
where: n = BMR Regional Network Code
EMPTY
R Y U
where ACG ID is the acgId configuration value, INDEX 1-6
EMPTY
Tells why the ACG is about to do a redundancy action reset.
R Y U
EMPTY
R Y U
October 30, 2008
ACG-9

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s T Y E M P T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
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]
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]
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]
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]
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]
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_id <ACG ID> GNP RESET: New active is old active <INDEX>: acg_id <ACG ID> GNP Reset: Invalid Ncarrier Carriers Site <INDEX>: acg_id <ACG ID> GNP Reset: Invalid Ncarrier Carriers Cell <INDEX>: acg_id <ACG ID> GNP Reset: DLX Config Fail <INDEX>: acg_id <ACG ID> Carrier Mean Ini <CMI>, cell id <CELL>, carrier id <CARRIER>, cab <CAB>, pos <POS>. ACG entered Level <CPU Util.Level> CPU access control mode Number of SCCH Reduced Cell <CELL_ID> Current Num Scch
o r M a j o r M a j o r
EMPTY
R Y U
EMPTY
R Y U
M a j o r
E M P T Y
EMPTY
R Y U
M a j o r M a j o r
E M P T Y E M P T Y
EMPTY
R Y U
EMPTY
No action required.
R N U
where CMI = Carrier Mean Ini > 140, CELL is the cell instance 13, CARRIER is carrier id 1-36, CAB is the cabinet 1-8, and POS is the position 1-6.
M a j o r M a j o r
E M P T Y E M P T Y
EMPTY
ACG entered CPU access control mode
R N U
210
SCCH Failure
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.1
GenACG
EMPTY
EMPTY
Possible Causes: hardware problem or misconfiguration
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. <CELL_ID>=[1-3] <NUMSCCH>=Current number of SCCH after reduction
ACG-10
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r EMPTY No action required
210
SCCH Failure
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.1
GenACG
EMPTY
<NUMSCCH> Number of SCCH Restored Cell <CELL_ID> ISO Mode
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]
905
ACG LAPD Msg Dropped
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.8.1. 1.<REDS>
BMR
<REDS> =[1/2]
Discarding LAPD msg for DAP <DAP ID>
C l e a r M a j o r W a r n i n g
E M P T Y E M P T Y E M P T Y
C N U
<CELL_ID>=[1-3]
EMPTY
OMC Automatically takes the necessary action for this alarm
R N U C
EMPTY
EMPTY
905
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.8.1. 1.<REDS>
BMR
<REDS> =[1/2]
Discarding LAPD msg for MDG <MDG ID>
W a r n i n g
E M P T Y
EMPTY
905
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.8.1. 1.<REDS>
BMR
<REDS> =[1/2]
Discarding LAPD msg for BSC
W a r n i n g
E M P T Y
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 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 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: <REDS> indicates redundant status, Active ACG = '1", Standby ACG ="2". <DAP ID> = "1" - "15".
R N U
note: <REDS> indicates redundant status, Active ACG = '1", Standby ACG ="2". <MDG ID> = "1" - "34".
R N U
note: <REDS> indicates redundant status, Active ACG = '1", Standby ACG ="2".
October 30, 2008
ACG-11

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r EMPTY site 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 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)
905
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.8.1. 1.<REDS>
BMR
<REDS> =[1/2]
Discarding LAPD msg for OMC
W a r n i n g
E M P T Y
R N U
note: <REDS> indicates redundant status, Active ACG = '1", Standby ACG ="2".
processingF ailureEvent
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.
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
ACGgenDAP
n = [1/2]
<n> <range>: <DAP ID a> [<DAP ID b> ...]
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
ACGgenDAP
n = [1/2]
processingF
1002
ACG_DAP Link
1.3.6.1.4.1.161.3
ACG-
n=[1-15],
ID TYPE=<IMEI/I MSI> MS_ID=0x<M SID> DAP_ID=<DA P ID a> [DAP_ID=<DA P ID b> ... DAP_ID=<DA P ID n>] <DAP ID>:
I n d e t e r m i n a t e C r i t i c a l M i n o r
E M P T Y
EMPTY
R N U
EMPTY
E M P T Y
EMPTY
Possible Causes:1. DAPs have conflicting MS message routing ranges Actions: 1. Reconfigure the ranges for those DAPs with conflicting ranges
R N U C
E M P T Y
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: <n> = DAP ID of DAP requesting the <range>, 115<range> = the requested range, xx-xx (xx = 0x000x3F)<DAP IDx> = DAP ID(s) of DAP(s) that have previously requested at least one entry in this range, 1-15 where:<IMEI/IMSI> = IMEI or IMSI<MSID> = IMEI or IMSI of the MS<DAP ID x> = DAP ID(s) of DAP(s) with MS defined in their HLR, 1-15
M E
REPORT
Possible Causes:1. DAP has
R N U
note:n=[1-15] indicates the DAP
ACG-12
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
R e l a t e d
Remedy
R e p o r t
O u t a g e
Comments & Notes
ailureEvent
Version Check Fail
.3.2.2.14.1.4.101 .1.n.m
genDAP
m=[1/2]
<unknown version>
A l a r m s a M j P o T r Y
& Y / C N l e a r : DL_STM: UEIDLUEA, UEIDLUEIMP DCC_ST M: UEIDLUEA, UEIMPUEA, UEIDLUEIMP, UEAUEIMP ACG_ST M: LEIDLUEIDL, UEAUEIMP, UEIMPUEA EBTS_S TM: UEAUEIDL, UEIMPUEIDL, UDIDLUEIDL, UEIDLUEIMP, UEAUEIMP, UEIMPUEA REPORT : DL_STM: UEIDLUEA, UEIDLUEIMP DCC_ST version that is not supported by ACG Actions:1. Replace DAP and/or ACG software with versions that are compatible
ID. Alarm code text:<DAP ID> = 1-15 DAP ID using unknown version, <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
ACGgenDAP
n=[1-15], m=[1/2]
<DAP ID>: <unknown version>
C r i t i c a l
E M P T Y
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> = DAP ID sending fail message, 1-15<unknown version> = Rxx.xx.xx (xx = 00-99)
October 30, 2008
ACG-13

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s M: UEIDLUEA, UEIMPUEA, UEIDLUEIMP, UEAUEIMP ACG_ST M: LEIDLUEIDL, UEAUEIMP, UEIMPUEA EBTS_S TM: UEAUEIDL, UEIMPUEIDL, UDIDLUEIDL, UEIDLUEIMP, UEAUEIMP, UEIMPUEA REPORT : DL_STM: UEIDLUEA, UEIDLUEIMP DCC_ST M: UEIDLUEA, UEIMPUEA, UEIDLUEIMP, versions that are compatible 3. Reconfigure ACG ID in ACG (or ACG DLCI in DAP config) so that ACG IDs match Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
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
ACGgenDAP
n=[1-15], m=[1/2]
<DAP ID>
C r i t i c a l
E M P T Y
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
R N U C
note:[1-15] indicates the DAP ID, where:<DAP ID> = DAP ID sending invalid ITC header, 1 - 15
ACG-14
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r UEAUEIMP ACG_ST M: LEIDLUEIDL, UEAUEIMP, UEIMPUEA EBTS_S TM: UEAUEIDL, UEIMPUEIDL, UDIDLUEIDL, UEIDLUEIMP, UEAUEIMP, UEIMPUEA EMPTY
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
ACGBSC
n = [1/2]
CM: DS0 <a> not configured as subrated voice
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
ACGgenMDG
n=[1-34], m=[1/2]
<MDG ID> : <unknown version>
I n d e t e r m i n a t e M i n o r
E M P T Y
Possible Causes:1. Subrate configured in BSC, but not in ACG Actions:1. Download site with correct configuration
R N U
where:<a> = DS0 number
E M P T Y
REPORT : ML_STM : UEIDLUEA MCC_ST M: UEIDLUEA,
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:<unknown version> = Rxx.xx.xx (xx = 00-99) <MDG ID> = MDG ID using unknown version, 1-34
October 30, 2008
ACG-15

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s UEIDLUEIMP, UEIMPUEA ACG_ST M: UEAUEIMP, UEIMPUEA EBTS_S TM: UEIDLUEIMP, UEAUEIMP, UEIMPUEA REPORT : ML_STM : UEIDLUEA MCC_ST M: UEIDLUEA, UEIDLUEIMP, UEIMPUEA ACG_ST M: UEAUEIMP, UEIMPUEA EBTS_S TM: UEIDLUEIMP, UEAUEIMP, UEIMPUEA REPORT : ML_STM Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
2003
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.103 .1.n.m
ACGgenMDG
n=[1-34], m=[1/2]
<MDG ID> : <unknown version>
M a j o r
E M P T Y
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:<unknown version> = Rxx.xx.xx (xx = 00-99) <MDG ID> = MDG ID using unknown version, 1-34
2004
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.103 .1.n.m
ACGgenMDG
n=[1-34], m=[1/2]
<MDG ID>
C E r M i P
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> = MDG ID sending invalid ITC
ACG-16
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
R e l a t e d A l a r m s T Y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r : UEIDLUEA MCC_ST M: UEIDLUEA, UEIDLUEIMP, UEIMPUEA ACG_ST M: UEAUEIMP, UEIMPUEA EBTS_S TM: UEIDLUEIMP, UEAUEIMP, UEIMPUEA EMPTY 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
t i c a l
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]
<Cell ID>
M a j o r
E M P T Y
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]
<Cell ID>, <Auto Management> , <Configured min PCH>, <Scaled min PCH>, <Configured Number Of Carriers>, <Number of
I n d e t e r m i n a
E M P T Y
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 Possible Causes:1. If this alarm occurred when the cell is in impaired state and was cleared when that cell goes active, then, the minimum size of PCH channels for that cell was reduced temporarily due to the temporarily limited number of BRs that were in service in that cell.2. This alarm should
R N U
note:[1-3] indicates the Cell ID. where:<Cell ID> = Cell ID with non-zero number of PCHs configured, 1 - 3
R N U C
note:[1-3] indicates the Cell ID. where:<Cell ID> = Cell ID with minimum PCH scaled, 1 3<Auto Management> = 1 YES or 0 - NO<Configured total min PCH> = Total PCH min size in terms of number of I12s.<Scaled min PCH> = Scaled total PCH Min Size in terms of number of I12s.<Configured Number Of
October 30, 2008
ACG-17

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s carriers in service> t e 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 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. 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) Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
Carriers> = Carriers configured for the cell, 1 - 20<Number of Carriers in service> = Number of Carriers that were in service in the cell when this condition was detected. R N U C note:n=[1-3], (cabinet in Alarm) indicates the Cell ID.
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]
<Cell ID>
M a j o r
E M P T Y
EMPTY
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]
<MDG ID1>, 0x<Timestam p1>, <RAG ID>, <Command>, <MDG ID2>, 0x<Timestam p2>, <RAG State>
C r i t i c a l
E M P T Y
EMPTY
R N U C
note:n=[1-34] indicates MDG ID. Alarm Code Text:: <MDG ID1> = Requesting MDG ID, 1 34, <Timestamp1> = MDG ID1s timestamp, <RAG ID> = RAG ID which is claimed by more than one MDG, 0-31, <Command> = the operation MDG ID1 attempted, where: 1 = unclaim, 2 = inactivate, 3 = activate, <MDG ID2> = RAG owners MDG ID, 1 - 34, otherwise 0, <Timestamp2> = MDG ID2s timestamp, if the RAG was owned, otherwise, timestamp of the last successful unclaim command on the RAG, <RAG State> = RAG state, where: 1 = inactive, 2 =
ACG-18
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r EMPTY Possible Causes:1. MDG is defective Actions:1. Reset/repair/replace MDG
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]
<Number of timestamps>, 0x<RAG Update Map>, <MDG ID>
3001
iVPU Link Hardening Failure
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.104 .1.<POS>.<RED S>
ACG_ge nIVPU
<POS>=[ 1-252], <REDS> =[1/2]
<iVPU ID><no response>
C r i t i c a l M a j o r
E M P T Y
R N U
active, 3 = unclaimed note:[1-34] indicates the MDG ID. where:<MDG ID> = MDG ID sending invalid number of timestamps, 1 - 34
3001
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.104 .1.<POS>.<RED S>
ACG_ge nIVPU
<POS>=[ 1-252], <REDS> =[1/2]
<iVPU ID><wrong iVPU ID>
3 0 0 0 , 3 0 0 2 , 3 0 0 3 , 3 0 0 4 M 3 a 0 j 0 o 0 r , 3 0 0 2 , 3 0 0 3 , 3 0 0
EMPTY
Possible Causes: T1 is in loopback mode. Actions: Check condition of physical T1 link
R N U
note: <POS> and <iVPU ID> indicates the iVPU ID, "1"-"252", <no response> = "no response". <REDS> indicates redundant status, Active ACG = "1", Standby ACG = "2".
EMPTY
Possible Causes: Misconfiguration of iVPU ID Actions: Reconfigure iVPU ID.
R N U
note: <POS> and <iVPU ID> indicates the iVPU ID, "1"-"252". <wrong iVPU ID> indicates the wrong iVPU ID, "1" - "252". <REDS> indicates redundant status, Active ACG = "1", Standby ACG = "2".
October 30, 2008
ACG-19

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s 4 3 0 0 0 , 3 0 0 2 , 3 0 0 3 , 3 0 0 4 3 0 0 0 , 3 0 0 2 , 3 0 0 3 , 3 0 0 4 3 0 0 0 , 3 0 Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r EMPTY iVPU ID configuration synchronized.
3001
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.104 .1.<POS>.<RED S>
ACG_ge nIVPU
<POS>=[ 1-252], <REDS> =[1/2]
<iVPU ID><wrong iVPU ID>
C l e a r
C N N
note: <POS> and <iVPU ID> indicates the iVPU ID, "1"-"252". <wrong iVPU ID> indicates the wrong iVPU ID, "1" - "252". <REDS> indicates redundant status, Active ACG = "1", Standby ACG = "2".
3001
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.104 .1.<POS>.<RED S>
ACG_ge nIVPU
<POS>=[ 1-252], <REDS> =[1/2]
<ACG ID><wrong ACG ID>
M a j o r
EMPTY
Possible Cause: New ACG site was added or site ID was changed.
R N N
note: <POS> indicates the iVPU ID, "1"-"252". <wrong ACG ID> indicates the wrong ACG ID, "1" - "10000". <REDS> indicates redundant status, Active ACG = "1", Standby ACG = "2".
3001
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.104 .1.<POS>.<RED S>
ACG_ge nIVPU
<POS>=[ 1-252], <REDS> =[1/2]
<ACG ID><wrong ACG ID>
C l e a r
EMPTY
Site ID configuration synchronized.
C N N
note: <POS> indicates the iVPU ID, "1"-"252". <wrong ACG ID> indicates the wrong ACG ID, "1" - "10000". <REDS> indicates redundant status, Active ACG = "1", Standby ACG = "2".
ACG-20
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
R e l a t e d
Remedy
R e p o r t
O u t a g e
Comments & Notes
3002
ACG_iVPU Link Version Check Fail
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.104 .1.<POS>.<RED S>
ACG_ge nIVPU
<POS>=[ 1-252], <REDS> =[1/2]
<iVPU ID><unknown version>
A l a r m s 0 2 , 3 0 0 3 , 3 0 0 4 M 3 a 0 j 0 o 1 r
& Y / C N l e a r
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 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 Possible Causes:1. ACG ID in link version response message does not match the ID of this ACG.
R N U
3003
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.104 .1.<POS>.<RED S>
ACG_ge nIVPU
<POS>=[ 1-252], <REDS> =[1/2]
<iVPU ID><unknown version>
3004
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.104 .1.<POS>.<RED S>
ACG_ge nIVPU
<POS>=[ 1-252], <REDS> =[1/2]
<iVPU ID>
equipmentF ailureEvent
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]
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 ?<Platform Type> ACG RESET: CORRUPTED DATA IN
C r i t i c a l C r i t i c a l C r i t i c a l C r i
3 0 0 1
EMPTY
R N U
note: <POS> and <iVPU ID> indicates the iVPU ID, "1"-"252". <unknown version> = Rxx.xx.xx (xx = 00-99) . <REDS> indicates redundant status, Active ACG = "1", Standby ACG = "2". note: <POS> and <iVPU ID> indicates the iVPU ID, "1"-"252". <unknown version> = Rxx.xx.xx (xx = 00-99). <REDS> indicates redundant status, Active ACG = "1", Standby ACG ="2". note: <POS> and <iVPU ID> indicates the iVPU ID sending invalid ITC header, "1"-"252". <REDS> indicates redundant status, Active ACG = "1", Standby ACG ="2".
3 0 0 1
EMPTY
R N U
E M P T Y
EMPTY
No action required. FYI only - This alarm indicates why EBTS reset
C Y U
note: <Platform Type> 1= iSC2, 2= iSC3
E M P
EMPTY
C Y U
note: <Platform Type> 1= iSC2, 2= iSC3 This alarm code text does not
October 30, 2008
ACG-21

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
RESET INFO ?<Platform Type>
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] INDETERMIN ATE RESET ?<Platform Type>
t i c a l C r i t i c a l
indicate why the ACG reset. Rather, it indicates that the stored reset reason is corrupt.
E M P T Y
EMPTY
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]
WDOG RESET ?<Platform Type> <Reset Info>
C r i t i c a l
E M P T Y
EMPTY
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]
?<Platform Type> ERR <Error Type> EX=<Exceptio n Level> TSK=<Task> MSR=<Machi ne state register> CR=<Conditio n Register> PC=<Program counter> R3/4=<Regist er 3>/<Register
C r i t i c a l
E M P T Y
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. 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. No action required. FYI only - This alarm indicates why EBTS reset EBTS reset due to ACG software fault (pROBE). However, repeated pROBEs on a site generally indicate one of the following fault conditions: (a) bad ACG - must be replaced, or (b) T1/E1 bouncing. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details.
C Y U
C Y U
note: <Platform Type> 1= iSC2, 2= iSC3, Reset Info - internal info about the watchdog reset.
C Y U
for iSC platform, <Platform Type> 1= iSC2, 2= iSC3
ACG-22
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r EMPTY No action required. FYI only - This alarm indicates why EBTS reset
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]
4> (for iSC) ACG SM Initiated ACG Reset: Unable to start CRM ?<Platform Type>
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]
ACG SM Initiated ACG Reset: T1/E1 config block read failed ?<Platform Type> ACG SM Initiated ACG Reset: DLCI retrieval failed ?<Platform Type>
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]
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]
ACG SM Initiated ACG Reset: DLX configuration failed. ?<Platform Type> ACG SM Initiated ACG Reset: CM failure while loading IC ?<Platform Type> ACG SM Initiated ACG Reset: Engine failure while allocating
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]
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]
C r i t i c a l C r i t i c a l C r i t i c a l C r i t i c a l C r i t i c a l C r i t i
E M P T Y
C Y U
E M P T Y
EMPTY
C Y U
E M P T Y
EMPTY
C Y U
E M P T Y
EMPTY
C Y U
E M P T Y
EMPTY
C Y U
E M P T Y
EMPTY
C Y U
October 30, 2008
ACG-23

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s memory ?<Platform Type> ACG CM Initiated Reset: Maximum Number of T1/ E1 lines should be 1 on iSC2 ?<Platform Type> c a l C r i t i c a l Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
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]
E M P T Y
EMPTY
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]
ACG CM Initiated Reset: Maximum Number of T1/E1 lines should be 2 on iSC III ?<Platform Type>
C r i t i c a l
E M P T Y
EMPTY
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]
ACG CM Initiated Reset: Interconnect Subrate pools
C r i t i
E M P T Y
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 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 Download site with correct configuration
C Y U
C Y U
C Y U
ACG-24
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
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]
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]
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]
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]
overlap ?<Platform Type> ACG CM Initiated Reset: Interconnect Subrate pools past end of T1/E1 ?<Platform Type> ACG CM Initiated Reset: Interconnect Subrate pools use DS0 1 or 17 on E1 ?<Platform Type> ACG CM Initiated Reset: More than 2 interconnect Subrate pools on a span ?<Platform Type> ACG CM Initiated Reset: Line number for a link should be 1 on iSC2 ?<Platform Type>
c a l C r i t i c a l C r i t i c a l C r i t i c a l C r i t i c a l
E M P T Y
EMPTY
Download site with correct configuration
C Y U
E M P T Y
EMPTY
C Y U
E M P T Y
EMPTY
C Y U
E M P T Y
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
C Y U
October 30, 2008
ACG-25

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s configuration for this iSC2 site. The parameter name is chanCard. Redownload the new configuration to this iSC2 site 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 Too many configuration parameters. Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
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]
ACG CM Initiated Reset: 'INFO' Region depleted, config too large. ?<Platform Type>
C r i t i c a l
E M P T Y
EMPTY
C Y U
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]
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]
ACG CM Initiated Reset: Tuple limit exceeded, config too large. ?<Platform Type> ACG CM Initiated Reset: Line number for subrate should be 1 on iSC2 ?<Platform Type> ACG CM Initiated Reset: Frame Relay must
C r i t i c a l C r i t i c a l
E M P T Y
EMPTY
C Y U
E M P T Y
EMPTY
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]
C r i t
E M P T
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. No action required. FYI only - This alarm indicates that an EBTS reset occurred due to invalid ACG configuration.
C Y U
C Y U
ACG-26
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
R e l a t e d A l a r m s Y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r 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 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 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 No action required. FYI only
begin on 1st DS0 of 2nd T1/E1 ?<Platform Type>
i c a l
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]
ACG SM Initiated Reset: Max number of carriers should be 24 on iSC2 ?<Platform Type>
C r i t i c a l
E M P T Y
EMPTY
C Y U
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]
ACG SM Initiated Reset: Max number of carriers should be 36 on iSC III ?<Platform Type>
C r i t i c a l
E M P T Y
EMPTY
C Y U
equipmentF
201
ACG Reset Reason
1.3.6.1.4.1.161.3
GenACG
n = [1/2]
ACG SM
C E
EMPTY
C Y U
note: <Platform Type> 1= iSC2,
October 30, 2008
ACG-27

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r - 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 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 No action required. FYI only - This alarm indicates why EBTS reset
ailureEvent
.3.2.2.14.1.4.100 .1.1.n
Initiated Reset: Max carriers per cell should be 20 (omni) on iSC2 ?<Platform Type>
r i t i c a l
2= iSC3
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]
ACG SM Initiated Reset: Max carriers per cell should be 20 (for omni) on iSC III ?<Platform Type>
C r i t i c a l
E M P T Y
EMPTY
C Y U
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]
GNP software reset requested with indeterminate reason.
C r i t i
E M P T Y
EMPTY
C Y U
ACG-28
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
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]
201
ACG Reset Reason
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.1
GenACG
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
<reason> ?<Platform Type> GNP RAM Reset requested with indeterminate reason. <reason> ?<Platform Type> Stby ACG Initiated Switch: Active ACG Communicatio n Down ?<Platform Type> OMC Initiated Switch: old Stby is new Active <ESN> <reason> ?<Platform Type> OMC Initiated Switch: old Active is new Active <ESN> <reason> ?<Platform Type> ACG Initiated Switch: old Stby is new Active <ESN> <reason> ?<Platform Type>
201
ACG Reset Reason
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.1
GenACG
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
c a l C r i t i c a l C r i t i c a l C r i t i c a l C r i t i c a l C r i t i c a l
E M P T Y
EMPTY
C Y U
E M P T Y
EMPTY
Possible Causes:1. ACG hardware failure Actions:1. Repair/replace old Active ACG
C Y U
E M P T Y
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
E M P T Y
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.
C Y U
E M P T Y
EMPTY
No action required. FYI only - This alarm indicates why EBTS reset. Depending on the value of <reason>, one of two reset scenarios is possible: <reason>=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:<ESN> = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16), <reason> = Reason for recovery: 21 - 29, <Platform Type> 1= iSC2, 2= iSC3 where:<ESN> = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16), <reason> = Reason for recovery: 21 - 29, <Platform Type> 1= iSC2, 2= iSC3 where:<ESN> = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16)<reason> = Reason for recovery: 00 - 99, <Platform Type> 1= iSC2, 2= iSC3
October 30, 2008
ACG-29

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s <reason>=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. No action required. FYI only - This alarm indicates why EBTS reset. Depending on the value of <reason>, one of two reset scenarios is possible: <reason>=25, 32, 42, or 44 EBTS reset due to GPS failure. This may include loss of satellite visibility or bad GPS hardware. <reason>=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. No action required. FYI only - This alarm indicates why EBTS reset. Active ACG failed during boot/download, and standby ACG recovered as active. Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
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 <ESN> <reason> ?<Platform Type>, <Platform Type> 1= iSC2, 2= iSC3
C r i t i c a l
E M P T Y
EMPTY
C Y U
where:<ESN> = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16)<reason> = Reason for recovery: 00 - 99, <Platform Type> 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
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 <ESN> <reason> ?<Platform Type> ACG Initiated Recovery: old Active is new Active <ESN> ?<Platform Type>
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 ?<Platform Type>
C r i t i c a l C r i t i c a l C r i t i
E M P T Y
EMPTY
C Y U
E M P T Y
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:<ESN> = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16), <reason> = Reason for recovery: 21 - 29, <Platform Type> 1= iSC2, 2= iSC3 where:<ESN> = Electronic Serial Number of current Active ACG: 0 - 9999999999999999 (variable number of digits up to a maximum of 16), <Platform Type> 1= iSC2, 2= iSC3
E M P T Y
EMPTY
No action required. FYI only - This alarm indicates why EBTS reset. Possible Causes:1) OMC initiated reset of EBTS
C Y U
ACG-30
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
201
ACG Reset Reason
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.1
GenACG
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
ACG Initiated Switch: Software Memory Corruption, old Stby is new Active ?<Platform Type> ACG CM Initiated Reset: Insufficient memory ?<Platform Type> ACG CM Initiated Reset: Begin channel number shouldn't be 0 ?<Platform Type> ACG SM Initiated Reset: Mismatched Backhaul Mode <old mode>-<new mode> ?<Platform Type> ACG SM Initiated Reset: RFDS value should be 1 for iSC2 ?<Platform Type>
c a l C r i t i c a l C r i t i c a l C r i t i c a l C r i t i c a l
E M P T Y
EMPTY
No action required. FYI only - This alarm indicates why EBTS reset. Possible Causes:1) File Corruption
C Y U
E M P T Y
EMPTY
No action required FYI only This alarm indicates why EBTS reset. Possible Cause: 1) ACG cannot allocate memory for T1 initialization.
C Y U
201
ACG Reset Reason
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.1
GenACG
EMPTY
E M P T Y
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
C Y U
201
ACG Reset Reason
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.<REDS>
GenACG
<REDS> =[1/2]
E M P T Y
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: <old mode> and <new mode> indicates the backhaul configuration type, Split Backhaul Mode = "SPLIT", All Frame Relay ="AFR". <REDS> indicates redundant status, Active ACG = "1", Standby ACG ="2",<Platform Type> 1= iSC2, 2= iSC3 note: <Platform Type> 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
C r i t i c a l
E M P T Y
EMPTY
No action required FYI only (for iSC2)This alarm indicates why EBTS reset. Cause: 1) rfdstype should be 1 for iSC2 platform
C Y U
October 30, 2008
ACG-31

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
C h a n g e S t a t u s U
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 <Cabinet> <Position>
A l a r m s M E a M j P o T r Y
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 <Cabinet> <Position>
M a j o r
E M P T Y
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 Stop response on BR <Cabinet> <Position>
M a j o r
E M P T Y
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 reset unexpectedly
M a j o
E M P T
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) 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) 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) Possible Causes (for VME or iSC2 only):1. BMR reset while processing a RAP IO test request.2. BMR (for
& Y / C N l e a r C N
EMPTY
R N U
R N U
R N U
EMPTY
ACG-32
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r 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) 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). 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 (for VME) or iMU (for iSC2) 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
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
M a j o r
E M P T Y
EMPTY
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
M a j o r
E M P T Y
EMPTY
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 comm enable response
M a j o r
E M P T Y
EMPTY
R N U
EMPTY
October 30, 2008
ACG-33

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s 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) Possible Causes (for VME or iSC2 only):1. BMR (for VME) or iMU (for iSC2) powered off. 2. Communication cable (RS232 serial for VME and 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 communication cable. 3. Properly connect or replace power cable. 4. Repair circuit breaker. 5. Repair/replace BMR (for VME) or iMU (for iSC2) Possible Causes (for VME or iSC2 only):1. BMR cannot register. 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 (for VME) or iMU (for iSC2) No action required. Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
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 to bring link up
M a j o r
E M P T Y
EMPTY
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 dropped out of single cell mode while testing
M a j o r
E M P T Y
EMPTY
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]
Resetting BR. carrier id <CARRIER>, cab <CAB>, pos <POS>.
M a j o r
E M P T Y
EMPTY
R N U
When a bad carrier mean ini value is calculated for a BR, the iSC resets the BR to clear the issue. Where CARRIER is the carrier id of the bad ini value 1-
ACG-34
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
High Carrier Mean INI <CMI>. equipmentF ailureEvent 304 Active TFR/SRI Off Line 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.1 TFR/SRI EMPTY EMPTY M i n o r E M P T Y EMPTY Possible Causes (for VME or iSC2):1. TFR/SRI is off-line, (For iSC3) TFR/SRI output failure. Actions:1. No action required. The TFR/SRI should automatically go online within 5 seconds. 2. If alarm has not cleared within 15 seconds, manually reset the EBTS site (for VME, iSC2, iSC3). 3) If alarm repeats, replace unit. Possible Causes: 1. SRI (for iSC2) or iSC3 (for iSC3) time/frequency output bit #1 fault: either (1) loss of the time/frequency signal or (2) line driver or relay failure. Actions:1. Power cycle iSC. 2. Replace SRI (for iSC2) or iSC3 (for iSC3) See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. Possible Causes:1. SRI (for iSC2) or iSC3 (for iSC3) time/frequency output bit #1 fault: either (1) loss of the time/frequency signal or (2) line driver or relay failure. Actions:1. Replace SRI (for iSC2) or iSC3 (for iSC3) See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. Possible Causes (for iSC3 only):1. iSC3 time/frequency output bit #2 fault: (1) loss of the time/frequency signal or (2) line driver or relay failure. 2. Cabling problem or short R N U
36, CAB is the cabinate of the BR 1-8, POS is the position of the BR 1-6, and CMI is the bad carrier EMPTY
305
TFR/SRI Generated Alarm
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
0 (iSC only)
M i n o r
E M P T Y
EMPTY
R N U
for iSC platform
305
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
1 (iSC only)
M i n o r
E M P T Y
EMPTY
R N U
for iSC platform
305
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
2 (iSC3 only)
M i n o r
E M P T Y
EMPTY
R N U
for iSC3 platform
October 30, 2008
ACG-35

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s circuit on the time/ frequency distribution. Actions: 1. Replace iSC3. 2. Fix or replace cabling. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. Possible Causes:1. TFR (for VME) power loss (-48 Volts removed). Actions:1. Reconnect -48 Volts, reset the EBTS, and wait for BRC to key. (for VME only) Possible Causes:1. GPS antenna not connected.2. GPS receiver defective. 3. Bad almanac. Actions:1. If alarm is reported greater than 5minutes without an alarm clear, check GPS antenna. 2. Check if standby ACG is able to track satellites to determine GPS reliability. 3. It may take up to one hour for GPS to track satellite if its first time power up. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. Possible Causes:1. TFR (for VME), SRI (for iSC2) or iSC3 (for iSC3) defective. Actions:1. Power cycle TFR (for VME), SRI (for iSC2) or iSC3 (for iSC3) 2. Replace TFR (for VME), SRI (for iSC2) or iSC3 (for iSC3) Possible Causes:1. Communication cable (RS232 serial for VME only) connected improperly or defective. 2. TFR (for VME), SRI (for iSC2) or iSC3 (for iSC3) defective. 3. TFR (for VME) power loss (-48 Volts Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
305
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
M i n o r M a j o r
E M P T Y E M P T Y
EMPTY
R N U
VME only
306
GPS Problem / 0 Tracked Satellites
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
EMPTY
R N U C
EMPTY
307
GPSR Self Test Failure
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
M a j o r
E M P T Y
EMPTY
R N U C
EMPTY
308
GPSR 1PPS Missing
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
M a j o r
E M P T Y
EMPTY
R N U C
EMPTY
ACG-36
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r removed). Actions:1. If serial watchdog console messages are present, properly connect or replace communication cable. Else if data expiration messages are not gone, look for Alarm 310 and follow its cause/action. 2. If BRCs also report 1PPS alarm, look for Alarm 310 and follow its cause/action. Else if BRCs do not report 1PPS alarm and only ACG is reporting this alarm, then the problem is a communication cable problem (see cause/action 1) or a defective GPSR (replace TFR for VME, SRI for iSC2 or iSC3 for iSC3). 3. Reconnect -48 Volts and reset the EBTS Possible Causes (for VME or iSC2 only):1. This is part of normal start-up procedure, but TFR (for VME) or SRI (for iSC2) may be defective. Actions: 1. No action required, but if alarm is reported greater than 10 seconds without an alarm clear, replace TFR (for VME) or SRI (for iSC2) Possible Causes:1. SRI (for iSC2) or iSC3 (for iSC3) HSO has drifted near the end of its adjustable frequency range. This alarm indicates that the HSO will probably fail in the near future and should be replaced. Upon total HSO failure, the HSO Failed Equipment alarm code 319 will be reported. Actions:1. Replace SRI (for iSC2) or
310
TFR/SRI Detected in Idle Mode
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
M a j o r
E M P T Y
EMPTY
R N U C
EMPTY
312
HSO Aging
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
E M P T Y
EMPTY
R N U C
EMPTY
October 30, 2008
ACG-37

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r REPORT : GPS_ST M: UEIDLUDIDL, UEIMPUDIDL, UEAUDIDL SBYGPS _STM: UEIDLUDIDL, UEIMPUDIDL, UEAUDIDL ACG_ST M: UEIDLUDIDL, UEAUDIDL, UEIMPUDIDL SBYACG _STM: LEIDLUDIDL, UEIDLUDIDL, UEIMPUDIDL, UEIMPLEIDL, UEAUDIDL EBTS_S TM: UEIDLUDIDL, UEAUDIDL, UEIMPiSC3 (for iSC3) Possible Causes:1. ACG Free Run Timeout because GPS has not received a good signal for over 4 hours. Actions:1. Check GPS antenna and cabling. If GPS antenna is not defective, replace SRI/iSC3/TFR See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details.
313
ACG Free Run Timeout
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
Site Reset <STATUS>
M 3 a 0 j 6 o r
R Y U
If GPS Disruption Tolerance parameters are enabled, the site reset will be suppressed. (Refer to "iDEN System Response to GPS Denial and GPS Spoofing Small Feature/Enhancement Implementation Document (SFEID)" PRO-ID-022.) <STATUS>= "Occurring" or "GPS Tolerance Mode Postponed"
ACG-38
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r UDIDL, UEAU_E_IM P EMPTY
314
HSO 1PPS Missing
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
M i n o r
E M P T Y
315
High Internal iSC SRI Temperature
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
M i n o r
E M P T Y
EMPTY
316
HSO Phase Not Locked
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
M i n o r
E M P T Y
EMPTY
Possible Causes:1. SRI (for iSC2) or iSC3 (for iSC3) defective. Actions:1. Reset both iSC2s or iSC3s; replace SRI (for iSC2); replace iSC2 (for iSC2) or iSC3 (for iSC3) See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. Possible Causes (for iSC2 or iSC3 only):SRI (for iSC2) or iSC3 (for iSC3) detected the ACG s ambient temperature as > 71 degrees due to (fault is cleared after SRI detects the ACGs ambient temperature < 69 degrees): 1. No or defective air conditioning. 2. iSC2 or iSC3 fan failure 3. SRI or iSC3 defective. Actions (for iSC2 or iSC3 only): 1. Add or repair air conditioning. 2. Replace iSC or iSC3 fan. 3. Powercycle iSC or iSC3. 4. Replace SRI (for iSC2); replace iSC2 or iSC3 Possible cause: Failure of an aging HSO (may be intermittent). Poor (intermittent) satellite tracking for an extended time. Other SRI hardware problems (damage to site) is also a possible cause but less likely, as are extreme temperature variations. Actions: Confirm that satellite tracking statistics for the site are good and
R N U
EMPTY
R N U
EMPTY
R N U C
EMPTY
October 30, 2008
ACG-39

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s monitor the specific FRU which generated the alarm. A site which appears to resume healthy operation after a reset should not necessarily be assumed to have cleared this alarm. Problems related to an aging HSO may recur with a period of days to weeks. The SRI should be replaced on any Site which repeats this alarm, otherwise occasional failures could persist (typically this will only recur on the Standby side, since the first failure will normally have triggered a redundancy switch). For iSC2 the SRI card should be replaced. For iSC3, the iSC3 unit should be replaced. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. No actions required. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
317
Bad Original Site Position in GPSR
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
<Bad Latitude>,<Ba d Longitude>, <Bad Height>:<Corr ected Latitude>, <Corrected Longitude>,< Corrected Height>
C r i t i c a l
E M P T Y
EMPTY
R Y U
If GPS Disruption Tolerance parameters are enabled, the site reset will be suppressed. (Refer to "iDEN System Response to GPS Denial and GPS Spoofing Small Feature/Enhancement Implementation Document (SFEID)" PRO-ID-022.) <Bad Latitude> = Bad original coordinates for latitude,<Bad Longitude>=Bad original coordinates for longitude, <Bad Height>=Bad original coordinates for height, <Corrected Latitude> = , <Corrected Longitude>,<Corrected Height> EMPTY
318
HSO Frequency Not Locked
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
M E i M n P
EMPTY
Possible cause: Failure of an aging HSO (may be intermittent). Poor
R N U C
ACG-40
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
R e l a t e d
Remedy
R e p o r t
O u t a g e
Comments & Notes
A l a r m s o T r Y
& Y / C N l e a r (intermittent) satellite tracking for an extended time. Other SRI hardware problems (damage to site) is also a possible cause but less likely, as are extreme temperature variations. Actions: Confirm that satellite tracking statistics for the site are good and monitor the specific FRU which generated the alarm. A site which appears to resume healthy operation after a reset should not necessarily be assumed to have cleared this alarm. Problems related to an aging HSO may recur with a period of days to weeks. The SRI should be replaced on any Site which repeats this alarm, otherwise occasional failures could persist (typically this will only recur on the Standby side, since the first failure will normally have triggered a redundancy switch). For iSC2 the SRI card should be replaced. For iSC3, the iSC3 unit should be replaced. See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. Possible Causes:1. SRI (for iSC2) or iSC3 (for iSC3) HSO has drifted to the end of its adjustable frequency range (for iSC2 or iSC3 only). This alarm indicates that the HSO has failed. 2. If the ACG is moved to a location > 1,000 kilo- meters away from the position
319
HSO Failed
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
<Latitude> <Longitude> <Altitude>
M i n o r
E M P T Y
EMPTY
R N U
where:<Latitude> = The latitude position of the EBTS GPS Receiver antenna (milliseconds), -324,000,000 324,000,000;<Longitude> = The longitude position of the EBTS GPS Receiver antenna (milliseconds), -648,000,000 648,000,000;<Altitude> = The altitude position of the EBTS
October 30, 2008
ACG-41

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s stored in the ACG and the position is not cleared using the iSC Install Code process, then this alarm indicates a manual failure to clear the position fault. Actions:1. Replace SRI (for iSC2 only) or iSC3 (for iSC3). 2. Check if location in this alarm is correct (using OMC-R to get current location of neighboring EBTS sites and comparing locations). If location is wrong, execute iSC Install Code process and reset the EBTS position to 0, 0, 0. After tracking 4 or more satellites, the EBTS site should initialize correctly (without replacing SRI) See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. Possible Causes:1. TFR (for VME), SRI (for iSC2) or iSC3 (for iSC3) defective. 2. GPS antenna or cabling defective. Actions:1. Replace TFR (for VME), SRI (for iSC2) or iSC3 (for iSC3).2. Repair/replace GPS antenna or cabling See EBTS Subsystem Troubleshooting Guide (6881012Y79-O) for more details. This emergency operation is intentional, and controlled by the operator via the 'GPS Disruption Tolerance' and 'GPS Key-up Override' parameters. Investigate whether GPS Spoofing could be occurring. Are many sites affected? Are there news bulletins? If Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
GPS Receiver antenna (meters), - 1,000 10,000;Note: Position data is stored in ACGs NVRAM after the GPS Receiver has tracked four satellites and has acquired position. 1 millisecond is equal to 0.03092 meters [6,378,140 meters (radius of Earth) * 2p / (360 degrees * 60 minutes * 60 seconds * 1000)]
320
ACG Failed to Achieve GPS Synchronization
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
EMPTY
M i n o r
E M P T Y
EMPTY
R N U
EMPTY
321
GPS Key up Override Alarm
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
322
GPS Spoofing Warning
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
Site has keyed with GPS Keyup Override parameter enabled GPS Spoofed <TYPE>,vel <VEL>, delta pos <POS>,
M a j o r W a r n
E M P T Y E M P T
EMPTY
R N U
EMPTY
R N U C
Refer to "iDEN System Response to GPS Denial and GPS Spoofing Small Feature/Enhancement Implementation Document (SFEID)" PRO-ID-022 Refer to "iDEN System Response to GPS Denial and GPS Spoofing Small Feature/Enhancement
ACG-42
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r not, check condition of the site's GPS system. If so, consider enabling 'GPS Disruption Tolerance' and 'GPS Key-up Override' parameters during the emergency situation.
dop <DOP>
i n g
Implementation Document (SFEID)" PRO-ID-022 <TYPE>= Type of Spoofing Detected, 0=No Spoof, 1 =Position, 2=Velocity, 3=Velocity and Position, <VEL>=Velocity m/s, <POS> delta position meters; -1 = Not Avail <DOP> = Dilution of Precision Refer to "iDEN System Response to GPS Denial and GPS Spoofing Small Feature/Enhancement Implementation Document (SFEID)" PRO-ID-022 <Fault Type>=Fault that triggered reset note:Cabinet and Position identify the BR, where: = Type of BR configured by operator: 1 = Single BR, 3 = Quad BR, "5" = Quad2 BR. = Band of the BR:2 = 800 MHz, 4=900 MHz, 5=1.5GHz Note:BR Type and Band are based on operator configuration via OMC-R for the Report alarm and for Clear alarm these are based on BR's registration, and will include the following values in addition to the above: "6"=800_DB, "7"=900_DB, "8"=DB. note1: If more than one BR is unequipped, EBTS would report about first unequipped BR only. note2:Cabinet and Position identify the first unequipped BR, where: = Type of the BR:1 = Legacy BR, 3 = Quad BR, "4" = Gen2 BR, "5" = Quad2 BR, "6" = GEN3 BR.
323
GPS Tolerance Event
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.2.2. 2.n
TFR/SRI
n = [1/2]
General GPS emergency operation notices, cause <Fault Type>
M a j o r
E M P T Y
EMPTY
In SR16.0, this indicates a failsafe mechanism triggering a site reset, which the operator should have already performed when the 'GPS Disruption Tolerance' or 'GPS Key-up Override' parameters were cleared. Possible Causes:1. Equipped BR is down (or powered off). 2. The BR cabinet and position in EBTS configuration is wrong. Actions:1. Verify that BR with cabinet <Cabinet> position <Position> is powered on and registering onto the LAN. Replace BR if necessary.2. Reconfigure EBTS with correct BR cabinet and position.
R Y U
900
Equipped BR did not Register
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]
 , 
M a j o r
E M P T Y
EMPTY
R N U C
901
Unequipped BR Registered
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]
 , 
C r i t i c a l
E M P T Y
EMPTY
Possible Causes:1. BR not configured by operator is up (or powered on) 2. The BR cabinet and position in EBTS configuration is wrong.3. The BRs cabinet and position is wrong. Actions:1. If all equipped BRs have registered, power off BR with
R N U
October 30, 2008
ACG-43

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s cabinet <Cabinet> position <Position>. Else if an equipped BR has not registered yet, modify cabinet and position of this BR to an equipped BR cabinet and position. 2. Reconfigure EBTS with correct BR cabinet and position. Possible Causes:1. Multiple BRCs have been configured with the same Cabinet and Position IDs. Actions:1. Check cabinet and position of all BRCs and then power off or reconfigure the Duplicate Cabinet/ Position BRC(s) Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
 = Band of the BR:2 = 800 MHz, 4= 900 MHz, "5" = 1.5 GHz, "6"=800_DB, "7"=900_DB, "8"=DB. NOTE:BR Platform and BR Band are based on BRs Registration message (for Legacy BR BR Band is Primary Band) R N U C note:Cabinet and Position identify the Duplicate Cabinet/ Position BRCs, where:<MAC-1> = Ethernet MAC address of BR accepted by ACG: 000000000001 FFFFFFFFFFFE,<MAC-2> = Ethernet MAC address of Duplicate BR rejected by ACG: 000000000001 FFFFFFFFFFFE, = Platform type of the BR: 1 = Legacy BR, 3 = Quad BR, , "4" = Gen2 BR, "5" = Quad2 BR, "6" = GEN3 BR. = Band of the BR:2 = 800 MHz, 4= 900 MHz, "5" = 1.5 GHz, "6"=800_DB, "7"=900_DB, "8"=DB. Note:BR Platform and BR Band are based on BRs Registration message (for Legacy BR BR Band is Primary Band) note:Cabinet and Position identify the Registering Duplicate MAC BRC, where:<MAC> = Ethernet MAC address of Duplicate MAC BRCs: 000000000001 FFFFFFFFFFFE,<Cabinet> = Cabinet ID of the BRC accepted by ACG: 1-8,<Position> = Position ID of the BRC accepted by ACG: 1-6, = Platform type of the BR: 1 =
902
Duplicate Cabinet/Position BRCs Registered
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]
0x<MAC-1>, 0x<MAC-2>, , 
C r i t i c a l
E M P T Y
EMPTY
904
Duplicate MAC BRCs Registered
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]
0x<MAC>, <Cabinet><Po sition>, ,
I n d e t e r m i n a t
E M P T Y
EMPTY
Possible Causes:1. Multiple BRCs have been configured with the same Ethernet MAC address. Actions:1. Check Ethernet MAC address of all BRCs and then power off or reconfigure the Duplicate MAC BRC(s)
R N U
ACG-44
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
905
Invalid MAC BRC Registered
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]
0x<MAC>, ,
E M P T Y
EMPTY
Possible Causes:1. BRCs has been configured with the same Ethernet MAC address as the ACGs Ethernet MAC address.2. BRC has been configured with an Ethernet MAC address of 0x000000000000 or 0xFFFFFFFFFFFF. Actions:1. Power off BRC or reconfigure the invalid MAC address. 2. Same as 1
R N U
906
Replacement BRC Registered
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]
0x<MAC>, ,
M i n o r
E M P T Y
CLEAR: CELL_S TM: LEIDLLDIDL, UEIDLUDIDL, UEAUDIDL, UEIMPUDIDL, UEAUEIMP ACG_ST M: UEIDL-
No action required. FYI only - This alarm notifies the OMC-R operator when a Replacement BRC has been accepted by the ACG.
C N U
Legacy BR, 3 = Quad BR, "4" = Gen2 BR, "5" = Quad2 BR, "6" = GEN3 BR. = Band of the BR:2 = 800 MHz, 4= 900 MHz, "5" = 1.5 GHz, "6"=800_DB, "7"=900_DB, "8"=DB. Note:BR Platform and BR Band are based on BRs Registration message (for Legacy BR BR Band is Primary Band) note:Cabinet and Position identify the Invalid MAC BRC, where:<MAC> = Ethernet MAC address of BRC: 000000000000 FFFFFFFFFFFF, = Platform type of the BR: 1 = Legacy BR, 3 = Quad BR, "4" = Gen2 BR, "5" = Quad2 BR, "6" = GEN3 BR. = Band of the BR:2 = 800 MHz, 4= 900 MHz, "5" = 1.5 GHz, "6"=800_DB, "7"=900_DB, "8"=DB. Note:BR Platform and BR Band are based on BRs Registration message (for Legacy BR BR Band is Primary Band) note:Cabinet and Position identify the BRC, where:<MAC> = Ethernet MAC address of Replacement BRC accepted by ACG: 000000000001 FFFFFFFFFFFE, = Platform type of the BR: 1 = Legacy BR, 3 = Quad BR, "4" = Gen2 BR, "5" = Quad2 BR, "6" = GEN3 BR. = Band of the BR:2 = 800 MHz, 4= 900 MHz, "5" = 1.5 GHz, "6"=800_DB, "7"=900_DB, "8"=DB. Note:BR Platform and BR Band are based on BRs
October 30, 2008
ACG-45

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s UDIDL, UEAUEIDL, UEAUEIMP, UEIDLLEIDL, UDIDLLDIDL, UEIDLUEIMP, UEAUDIDL, UEIMPUEIDL, UEIMPUDIDL EBTS_S TM: UEAUEIDL, UEIMPUEIDL, UDIDLUEIDL, UEIDLUEIMP, UEAUEIMP EMPTY Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
Registration message (for Legacy BR BR Band is Primary Band)
908
Invalid Platform Type BRC Registered
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]
0x<MAC>, , , 
M i n o r
E M P T Y
Possible Causes:1. Wrong type of BR was installed at the EBTS site.2. Network operator misconfigured the BRs Type.3. Network operator misconfigured the BRs Band. Actions:1. Replace BR with correct Type of BR.2. Reconfigure BRs BR Type. 3. Reconfigure BRs band
R N U
note:Cabinet and Position identify the BRC, where:<MAC> = Ethernet MAC address of registering BRC rejected by ACG: 000000000001 FFFFFFFFFFFE, = Platform type of the BR that registered: 0 = unknown, 1 = Legacy BR, 3 = Quad BR, "4" = Gen2 BR, "5" = Quad2 BR. = Type of BR configured by the operator: 1 = Single, 3 = Quad, "5" = Quad2 BR, "6" = GEN3 BR. = Band of the Registering BR:2 = 800 MHz, 4= 900 MHz, "5" = 1.5
ACG-46
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
911
Cooling Fan Failed
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.n
GenACG
n = [1/2]
EMPTY
912
Possible Failure on Local Ethernet Loop
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.n.m
GenACG
n=[1-4], m = [1/2]
<number>
M a j o r M i n o r
E M P T Y E M P T Y
EMPTY
Possible Causes (for iSC3 only):1. iSC III defective. Actions:1. Replace iSC III
R N U
GHz, "6"=800_DB, "7"=900_DB, "8"=DB. = Band of the Configured BR:2 = 800 MHz, 4= 900 MHz, "5" = 1.5 GHz. Note: is based on BRs Registration message (for Legacy BR BR Band is Primary Band)BR Platform is based on BRs hardware and BR Type is based on operator configuration via OMC-R EMPTY
EMPTY
912
Possible Failure on Local Ethernet Loop
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.n.m
GenACG
n=[1-4], m = [1/2]
Loss of Signal on loop <number>
M i n o r
E M P T Y
EMPTY
913
More Than 24 Carriers on an Ethernet Loop
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.n.m
GenACG
n = [1-3], m = [1/2]
More than 24 carriers on the local Ethernet loop <number>, BR <Cabinet><Po sition>
M i n o r
E M P T Y
EMPTY
Possible Causes (for iSC2 or iSC3):1. iSC2 Ethernet card or iSC III defective.2. Ethernet cable is not connected properly. Actions:1. Replace iSC2 Ethernet card or iSC III.2. Check Ethernet cable connection Possible Causes (for iSC2 or iSC3):1. iSC2 Ethernet card or iSC III defective.2. Ethernet cable is not connected properly. Actions:1. Replace iSC2 Ethernet card or iSC III.2. Check Ethernet cable connection Possible Causes (for iSC3 only):1. The total number of carriers physically connected to the 10 Mbps local Ethernet loop exceeds the maximum allowance (24 carriers). Actions:1. Reduce the number of BR(s) connected to the indicated local Ethernet loop by physically re-connecting the
R N U C
note:n=[1-4] indicates the Ethernet loop ID, where:<number> = Ethernet loop ID: 1 - 4
R N U C
note:n=[1-4] indicates the Ethernet loop ID, where:<number> = Ethernet loop ID: 1 - 4
R N U C
note:n=[1-3] indicates the Ethernet loop ID, where:<number> = Ethernet loop ID: 1 - 3,<Cabinet> = Cabinet ID of the BRC rejected by ACG: 1-8,<Position> = Position ID of the BRC rejected by ACG: 1-6
October 30, 2008
ACG-47

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s BR(s) to another loop.2. Reduce the number of carriers connected to the indicated local Ethernet loop by reducing the number of carriers configured on that BR (on quad BR only) ACG memory should be added or removed to make the amount of memory identical on both ACGs. Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
914
ACG Memory Mismatch
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.1
GenACG
EMPTY
915
Not enough ACG memory
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.1
GenACG
EMPTY
Standby ACG memory (< X MB>) does not match Active ACG memory (<Y MB>) ACG memory size is too small (X MB < 32 MB) EMPTY
M i n o r
E M P T Y
EMPTY
R N U
EMPTY
environment FailureEven t
201
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
202
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
203
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
204
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
205
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
environment FailureEven
206
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1.
EAS
n = [1/2]
EMPTY
M a j o r M i n o r M i n o r M i n o r M i n o r M i n o r M i
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M
EMPTY
ACG memory should be added to bring total memory to at least 32MB
R N U
EMPTY
Possible Causes:1. User defined. Actions:1. User defined.
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
Possible Causes:1. User defined. Actions:1. User
R N U C
EMPTY
ACG-48
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
R e l a t e d A l a r m s P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r defined.
1.n
207
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
208
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
209
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
210
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
211
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
212
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
213
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
214
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
215
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
October 30, 2008
ACG-49

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
216
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
217
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
218
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
219
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
220
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
221
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
222
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
223
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
224
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
ACG-50
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
R e l a t e d A l a r m s Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r EMPTY Possible Causes:1. User defined. Actions:1. User defined.
225
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
226
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
227
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
228
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
229
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
230
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
231
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
232
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
233
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
October 30, 2008
ACG-51

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
234
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
235
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
236
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
237
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
238
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
239
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
240
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
241
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
242
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
environment
243
User Defined
1.3.6.1.4.1.161.3
EAS
n = [1/2]
EMPTY
M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M
EMPTY
& Y / C N l e a r R N C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
Possible Causes:1. User
R N U
EMPTY
ACG-52
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
S e v e r i t y
R e l a t e d A l a r m s M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M
Remedy
R e p o r t
O u t a g e
Comments & Notes
FailureEven t
.3.2.2.14.1.4.7.1. 1.n
244
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
245
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
246
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
247
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
248
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
249
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
250
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
251
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1. 1.n
EAS
n = [1/2]
EMPTY
environment FailureEven
252
User Defined
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.7.1.
EAS
n = [1/2]
EMPTY
i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i n o r M i
defined. Actions:1. User defined.
& Y / C N l e a r C
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
R N U C
EMPTY
EMPTY
Possible Causes:1. User defined. Actions:1. User
R N U C
EMPTY
October 30, 2008
ACG-53

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
1.n
A l a r m s n P o T r Y
& Y / C N l e a r defined.
ACG-54
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
esmrStateCh angeEvent
1 0 0 1 0 1 1 0 2 1 0 3 1 0 4
PCCH BR ENABLED
CELL GOING UNLOCKE D PCCH BR ACTIVE
ALL BRS ACTIVE IN CELL CELL BEING LOCKED BY ACG CELL BEING LOCKED BY ACG CELL BEING LOCKED BY ACG CELL LOCK SUCCESS FUL BR DISABLED
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200
CELL
[1-3]
L-D-Idl
L-E-Idl
Empty
Empty
During Initialization: Cell begins in L-D-Idl state. Cell becomes enabled when PCCH BR is enabled (loaded and configured). Cell has unlocked PCCH BR and other BRs that are enabled. Cell is waiting for PCCH BR to key up (report U-E-A or U-E-Imp). The cell is now functional. The PCCH BR is keyed with full functionality.
S t a t u s U Empty
CELL
[1-3]
L-E-Idl
U-E-Idl
Empty
Empty
U Empty
CELL
[1-3]
U-E-Idl
U-EImp
Empty
Empty
U Empty
CELL
[1-3]
U-EImp
U-E-A
Empty
Empty
The cell is now fully functional. All BRs in cell are keyed with full functionality.
U Empty
CELL
[1-3]
U-E-A
U-E-Idl
Empty
Empty
1 0 4
CELL
[1-3]
U-EImp
U-E-Idl
Empty
Empty
1 0 4
CELL
[1-3]
U-DIdl
L-D-Idl
Empty
Empty
1 0 6 1 0
CELL
[1-3]
U-E-Idl
L-E-Idl
Empty
Empty
The cell is being taken out of service by the ACG. This may be because of an EBTS-wide problem (i.e. DAP or Mobis failure). The exact cause is given in the ACG State Change Trap that is also sent at this time. The cell is being taken out of service by the ACG. This may be because of an EBTS-wide problem (i.e. DAP or Mobis failure). The exact cause is given in the ACG State Change Trap that is also sent at this time. The cell is being taken out of service by the ACG. This may be because of an EBTS-wide problem (i.e. DAP or Mobis failure). The exact cause is given in the ACG State Change Trap that is also sent at this time. The cell has successfully been taken out of service. The cell is ready and waiting to be unlocked. The cell is partially functional. One of its BRs is disabled.
U Empty
U Empty
U Empty
U Reason Code # 105 not used
CELL
[1-3]
U-E-A
U-EImp
Empty
Empty
U Empty
October 30, 2008
ACG-55

State Changes
R e a s o n C o d e
Release SR17.0
Related State Changes Related Alarms Event Description
O u t a g e ( Y / N ) C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
7 esmrStateCh angeEvent 1 0 8 1 0 9 1 1 0 1 1 1 BR IMPAIRED
BR LOCKED
BR RESET
1 1 1
1 1 2 1 1 3 1 1 4 1 1 4 1 1 4 1 1 4
CELL RECOVER Y SUCCESS FUL CELL RECOVER Y SUCCESS FUL CRM CELL LOCK ERROR CRM CELL UNLOCK ERROR PCCH BR DISABLED
1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535.
CELL
[1-3]
U-E-A
U-EImp
Empty
Empty
The cell is partially functional. One of its BRs is impaired.
U Empty
CELL
[1-3]
U-E-A
U-EImp
Empty
Empty
The cell is partially functional. One of its BRs is temporarily locked.
U Empty
CELL
[1-3]
U-E-A
U-EImp
Empty
Empty
The cell is partially functional. One of its BR has reset.
U Empty
CELL
[1-3]
U-DIdl
U-E-Idl
Empty
Empty
Cell has become enabled after recovering from a PCCH failure.
U Empty
CELL
[1-3]
L-D-Idl
L-E-Idl
Empty
Empty
Cell has become enabled after recovering from a PCCH failure.
U Empty
CELL
[1-3]
U-E-Idl
U-DIdl
Empty
Empty
Cell is disabled and attempting recovery. Cell Resource Manager has encountered an error while locking the cell. Cell is disabled and attempting recovery. Cell Resource Manager has encountered an error while unlocking the cell. Cell is disabled and attempting recovery. PCCH BR is disabled.
U Empty
CELL
[1-3]
U-E-Idl
U-DIdl
Empty
Empty
U Empty
CELL
[1-3]
U-E-A
U-DIdl
Empty
Empty
U Empty
PCCH BR DISABLED
CELL
[1-3]
U-EImp
U-DIdl
Empty
Empty
Cell is disabled and attempting recovery. PCCH BR is disabled.
U Empty
PCCH BR DISABLED
CELL
[1-3]
U-E-Idl
U-DIdl
Empty
Empty
U Empty
PCCH BR DISABLED
CELL
[1-3]
L-E-Idl
L-D-Idl
Empty
Empty
U Empty
ACG-56
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
MOI Info (Label) Inst From State To State
OMC Text
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 1 5 1 1 5 1 1 6 1 1 6 1 1 6 1 1 7 1 1 7 1 1 7 1 1 7 1 1 8 1 1 9 1 2
PCCH BR IMPAIRED
PCCH BR IMPAIRED
PCCH BR LOCKED
PCCH BR LOCKED
PCCH BR LOCKED
PCCH BR RESET
PCCH BR RESET
PCCH BR RESET
PCCH BR RESET
PCCH BR FAILED TO UNLOCK PCCH BR FAILED TO KEYUP PCCH BR FAILED
1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200
CELL
[1-3]
U-E-Idl
U-EImp
Empty
Empty
Cell is partially functional. PCCH BR is up with partial functionality.
U Currently BRCs do not report transition to Impaired state. U Empty
CELL
[1-3]
U-E-A
U-EImp
Empty
Empty
Cell is partially functional. PCCH BR is downgraded to partial functionality.
CELL
[1-3]
U-E-A
U-DIdl
Empty
Empty
Cell is disabled and attempting recovery. PCCH BR is locked.
U Empty
CELL
[1-3]
U-EImp
U-DIdl
Empty
Empty
U Empty
CELL
[1-3]
U-E-Idl
U-DIdl
Empty
Empty
U Empty
CELL
[1-3]
U-E-A
U-DIdl
Empty
Empty
Cell is disabled and attempting recovery. PCCH BR has reset.
U Empty
CELL
[1-3]
U-EImp
U-DIdl
Empty
Empty
U Empty
CELL
[1-3]
U-E-Idl
U-DIdl
Empty
Empty
U Empty
CELL
[1-3]
L-E-Idl
L-D-Idl
Empty
Empty
Cell is locked and disabled. PCCH BR has reset.
U Empty
CELL
[1-3]
U-E-Idl
U-DIdl
Empty
Empty
Cell is disabled and attempting recovery. PCCH BR failed to unlock.
U Empty
CELL
[1-3]
U-E-Idl
U-DIdl
Empty
Empty
Cell is disabled and attempting recovery. PCCH BR failed to key-up.
U Empty
CELL
[1-3]
U-E-Idl
U-DIdl
Empty
Empty
Cell is disabled and attempting recovery. PCCH BR failed to lock.
U Empty
October 30, 2008
ACG-57

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
0 esmrStateCh angeEvent 1 2 1 1 2 2
TO LOCK PCCH CARRIER NOT FOUND CELL READY FOR CAVITY SWITCH BACK TO ORIGINAL PCCH BR CELL READY FOR CAVITY SWITCH BACK TO ORIGINAL PCCH BR ATTEMPTI NG OMC INITIATED CAVITY SWITCH BACK ATTEMPTI NG OMC INITIATED CAVITY SWITCH BACK SCCH BR FAILED
1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1
CELL
[1-3]
L-D-Idl
L-D-Idl
Empty
Empty
Cell is disabled. Configuration error: No PCCH carrier identified for this cell.
U Empty
CELL
[1-3]
U-EImp
U-EImp
Empty
Empty
Cell is ready for OMC to initiate Cavity Switch Back to Original PCCH BR from Redundant PCCH BR. Note: Cavity Switch Back will temporarily disable the cell.
U Empty
1 2 2
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1
CELL
[1-3]
L-E-Idl
L-E-Idl
Empty
Empty
Cell is ready for OMC to initiate Cavity Switch Back to Original PCCH BR from Redundant PCCH BR. Note: Cavity Switch Back will temporarily disable the cell.
U Empty
1 2 3
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1
CELL
[1-3]
U-EImp
U-DIdl
Empty
Empty
OMC has initiated Cavity Switch Back for this cell. Cell is attempting to switch back to Original PCCH BR from Redundant PCCH BR.
U Empty
1 2 3
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1
CELL
[1-3]
L-E-Idl
L-D-Idl
Empty
Empty
OMC has initiated Cavity Switch Back for this cell. Cell is attempting to switch back to Original PCCH BR from Redundant PCCH BR.
U Empty
1 2 4 1 2 4 4 0 0 4
SCCH BR FAILED
DAP LINK ACTIVE
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 1.CellInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 2.1.65535.1 1.3.6.1.4.1.161.3
CELL
[1-3]
U-E-A
U-DIdl
Empty
Empty
Cell is disabled. SCCH BR dekeyed or disabled.
U Empty
CELL
[1-3]
U-EImp
U-DIdl
Empty
Empty
Cell is disabled. SCCH BR dekeyed or disabled.
U Empty
DCC
U-E-Idl
U-EImp
Empty
Empty
esmrStateCh
ALL DAP
DCC
U-E-Idl
U-E-A
Empty
Empty
An ACG-DAP Link is Active. Communications to at least one DAP is established. Redundant DAP links for this DAP are UP. The site is not in ISO mode. All ACG-DAP Links are Active. Communications
U Empty
U Empty
ACG-58
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
0 1 4 0 1 4 0 2 4 0 2 4 0 3 4 0 4 4 0 4 4 0 4 3 0 2
LINKS ACTIVE ALL DAP LINKS ACTIVE DAP LINK IMPAIRED
.3.2.2.14.1.4.200 2.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 2.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 2.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 2.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 2.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 2.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 2.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 2.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1
DCC
U-EImp U-E-Idl
U-E-A
Empty
Empty
DCC
U-EImp
Empty
Empty
DAP LINK IMPAIRED
DCC
U-E-A
U-EImp
Empty
Empty
DAP LINK IDLE
DCC
U-E-A
U-EImp
Empty
Empty
ALL DAP LINKS IDLE ALL DAP LINKS IDLE ALL DAP LINKS IDLE DAP VERSION RECEIVE D BOTH REDUNDA NT LAPD LINKS UP DAP VERSION RECEIVE D PRIMARY LAPD LINK UP DAP VERSION RECEIVE D
DCC
U-EImp
U-E-Idl
Empty
Empty
DCC
U-E-A
U-EImp
Empty
Empty
DCC
U-E-A
U-E-Idl
Empty
Empty
ACG-DL
[1-15]
U-E-Idl
U-E-A
Empty
Empty
to all DAPs is established. All redundant DAP links are UP. The site is not in ISO mode. All ACG-DAP Links are Active. Communications to all DAPs is established. All redundant DAP links are UP. The site is not in ISO mode. An ACG-DAP Link is Impaired. Communications to at least one DAP is established, however, one or more redundant DAP links is DOWN. The site is not in ISO mode. An ACG-DAP Link is Impaired. Communications to at least one DAP is established, however, one or more redundant DAP links is DOWN. The site is not in ISO mode. An ACG-DAP Link is Idle. Communications to one DAP has failed, how ever, communications to at least one other DAP remains. The site will not enter ISO mode yet. All ACG-DAP Links are Idle. Communications to all DAPs has failed. If the site is ISO capable and no ACG-DAP links return, it will become barred then enter ISO mode. All ACG-DAP Links are Idle. Communications to all DAPs has failed. If the site is ISO capable and no ACG-DAP links return, it will become barred then enter ISO mode. All ACG-DAP Links are Idle. Communications to all DAPs has failed. If the site is ISO capable and no ACG-DAP links return, it will become barred then enter ISO mode. ACG-DAP Link is now functional. Both Primary and Secondary redundant LAPD links are UP.
U Empty
U Empty
U Empty
U Empty
U Empty
U Empty
U Empty
U Reason Code # 300, 301 not used
3 0 3
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1
ACG-DL
[1-15]
U-E-Idl
U-EImp
Empty
Empty
ACG-DAP Link is now functional. Only the Primary redundant LAPD link is UP.
U Empty
3 0 4
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1
ACG-DL
[1-15]
U-E-Idl
U-EImp
Empty
Empty
ACG-DAP Link is now functional. Only the Secondary redundant LAPD link is UP.
U Empty
October 30, 2008
ACG-59

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
3 0 5 3 0 6 3 0 7 3 0 7 3 0 7 3 0 8 3 0 8 3 0 8 3 1 0
SECONDA RY LAPD LINK UP PRIMARY LAPD LINK UP SECONDA RY LAPD LINK UP PRIMARY LAPD LINK DOWN PRIMARY LAPD LINK DOWN PRIMARY LAPD LINK DOWN SECONDA RY LAPD LINK DOWN SECONDA RY LAPD LINK DOWN SECONDA RY LAPD LINK DOWN DAPLINK VERSION DOWN NOTIFICA TION RECEIVE D DAPLINK VERSION DOWN NOTIFICA TION
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1
ACG-DL
[1-15]
U-EImp
U-E-A
Empty
Empty
ACG-DAP Primary LAPD link is UP. Both redundant LAPD links are now UP.
U Empty
ACG-DL
[1-15]
U-EImp
U-E-A
Empty
Empty
ACG-DAP Secondary LAPD link is UP. Both redundant LAPD links are now UP.
U Empty
ACG-DL
[1-15]
U-E-A
U-EImp
Empty
Empty
ACG-DAP Primary LAPD link is DOWN. Remaining redundant LAPD link is still functional. ACG-DAP Primary LAPD link is DOWN. Both redundant LAPD links are now DOWN.
U Empty
ACG-DL
[1-15]
U-EImp
U-E-Idl
Empty
Empty
U Empty
ACG-DL
[1-15]
U-E-A
U-E-Idl
Empty
Empty
ACG-DAP Primary LAPD link is DOWN. Both redundant LAPD links are now DOWN.
U Empty
ACG-DL
[1-15]
U-E-A
U-EImp
Empty
Empty
ACG-DAP Secondary LAPD link is DOWN. Remaining redundant LAPD link is still functional. ACG-DAP Secondary LAPD link is DOWN. Both redundant LAPD links are now DOWN.
U Empty
ACG-DL
[1-15]
U-EImp
U-E-Idl
Empty
Empty
U Empty
ACG-DL
[1-15]
U-E-A
U-E-Idl
Empty
Empty
ACG-DAP Secondary LAPD link is DOWN. Both redundant LAPD links are now DOWN.
U Empty
ACG-DL
[1-15]
U-E-A
U-E-Idl
Empty
Empty
DAP has detected a LAPD link drop but didnt get a link Version Request from the ACG after the LAPD link came up because the ACG didnt detect the LAPD link drop. ACG-DAP Link Version request procedure will begin.
U Reason Code # 309not used.
3 1 0
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 3.DapInst.65535. 1
ACG-DL
[1-15]
U-EImp
U-E-Idl
Empty
Empty
DAP has detected a LAPD link drop but didnt get a link Version Request from the ACG after the LAPD link came up because the ACG didnt detect the LAPD link drop. ACG-DAP Link Version request procedure will begin.
U Empty
ACG-60
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
6 0 0 6 0 0 6 0 1 6 0 1 6 0 2 6 0 3 5 0 0 5 0 1 5 0 2
RECEIVE D ALL MDG LINKS IDLE ALL MDG LINKS IDLE ALL MDG LINKS ACTIVE ALL MDG LINKS ACTIVE MDG LINK IDLE MDG LINK ACTIVE MDG LINK VERSION VERIFIED MDG LINK DOWN
9 0 1
MDG LINK VERSION DOWN NOTIFICA TION ACTIVE GPS CRITICAL FAULT ACTIVE GPS CRITICAL FAULT ACTIVE GPS CRITICAL FAULT
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 4.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 4.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 4.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 4.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 4.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 4.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 5.MdgInst.65535 .1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 5.MdgInst.65535 .1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 5.MdgInst.65535 .1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.1
MCC
U-EImp U-E-A
U-E-Idl
Empty
Empty
All ACG-MDG links to this ACG site are idle.
U Empty
MCC
U-E-Idl
Empty
Empty
All ACG-MDG links to this ACG site are idle.
U Empty
MCC
U-E-Idl
U-E-A
Empty
Empty
All ACG-MDG links to this ACG site are active.
U Empty
MCC
U-EImp U-E-A
U-E-A
Empty
Empty
All ACG-MDG links to this ACG site are active.
U Empty
MCC
U-EImp U-EImp U-E-A
Empty
Empty
At least one ACG-MDG link is idle, but not all MDG links are idle. At least one ACG-MDG link is active, but not all MDG links are active. ACG-MDG link has been established. A valid link version message from the MDG was received. ACG-MDG link has dropped.
U Empty
MCC
U-E-Idl
Empty
Empty
U Empty
ACG-ML
[1-40]
U-E-Idl
Empty
Empty
U Empty
ACG-ML
[1-40]
U-E-A
U-E-Idl
Empty
Empty
U Empty
ACG-ML
[1-40]
U-E-A
U-E-Idl
Empty
Empty
ACTIVE_ SRI/TFR
U-E-Idl
U-DIdl
Empty
Empty
MDG has detected a link failure but didnt get a Link Version Request from the ACG after the link came up because the ACG didnt detect the link failure. ACG-MDG Link Version Request procedure will begin. Active SRI/TFR is disabled due to critical fault.
U Empty
9 0 1
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.1
ACTIVE_ SRI/TFR
U-EImp
U-DIdl
Empty
Empty
Active SRI/TFR is disabled due to critical fault.
9 0 1
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.1
ACTIVE_ SRI/TFR
U-E-A
U-DIdl
Empty
Empty
Active SRI/TFR is disabled due to critical fault.
See EBTS Subsystem Troubleshooting Guide (6881012Y79O) for more details. U See EBTS Subsystem Troubleshooting Guide (6881012Y79O) for more details. U See EBTS Subsystem Troubleshooting Guide (6881012Y79-
October 30, 2008
ACG-61

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s O) for more details. See EBTS Subsystem Troubleshooting Guide (6881012Y79O) for more details. U Empty U
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
9 0 2
ACTIVE GPS FREERUN STARTED ACTIVE GPS FREERUN ENDED ACTIVE GPS SYNCHRO NIZED STANDBY GPS CRITICAL FAULT STANDBY GPS CRITICAL FAULT STANDBY GPS CRITICAL FAULT STANDBY GPS FREERUN STARTED STANDBY GPS FREERUN ENDED STANDBY GPS SYNCHRO NIZED STANDBY GPS SENT TO IDLE STANDBY GPS SENT TO IDLE STANDBY
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.1
ACTIVE_ SRI/TFR
U-E-A
U-EImp
Empty
Empty
Active SRI/TFR is impaired due to the free run started.
9 0 3 9 0 4 9 5 1 9 5 1 9 5 1 9 5 2 9 5 3 9 5 4 9 5 5 9 5 5 9
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 7.1.65535.2 1.3.6.1.4.1.161.3
ACTIVE_ SRI/TFR
U-EImp
U-E-A
Empty
Empty
Active SRI/TFR is Active due to the free run ended.
ACTIVE_ SRI/TFR
U-E-Idl
U-E-A
Empty
Empty
Active SRI/TFR is Active due to the arrival of time synchronization.
U Empty
STANDB Y_SRI/T FR STANDB Y_SRI/T FR STANDB Y_SRI/T FR STANDB Y_SRI/T FR STANDB Y_SRI/T FR STANDB Y_SRI/T FR STANDB Y_SRI/T FR STANDB Y_SRI/T FR STANDB
U-E-Idl
U-DIdl
Empty
Empty
Standby SRI/TFR is disabled due to critical fault.
U Empty
U-EImp
U-DIdl
Empty
Empty
U Empty
U-E-A
U-DIdl
Empty
Empty
U Empty
U-E-A
U-EImp
Empty
Empty
Standby SRI/TFR is impaired due to the free run started.
U Empty
U-EImp
U-E-A
Empty
Empty
Standby SRI/TFR is Active due to the free run ended.
U Empty
U-E-Idl
U-E-A
Empty
Empty
Standby SRI/TFR is Active due to the arrival of time synchronization.
U Empty
U-E-A
U-E-Idl
Empty
Empty
The Standby SRI/TFR has been sent to idle during the standby initialization or in preparation for a BGDL/Redundancy switch. The Standby SRI/TFR has been sent to idle during the standby initialization or in preparation for a BGDL/Redundancy switch. The Standby SRI/TFR has been sent to idle
U Empty
U-EImp
U-E-Idl
Empty
Empty
U Empty
esmrStateCh
U-D-
U-E-Idl
Empty
Empty
U Empty
ACG-62
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
5 5 2 0 0 2 0 0 2 0 0 2 0 1 2 0 2 2 0 2 2 0 3 2 0 3 2 0 3
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
GPS SENT TO IDLE ALL CELLS DISABLED ALL CELLS DISABLED ALL CELLS DISABLED DAP COMMUNI CATIONS UP MOBIS LINK UP MOBIS LINK UP DAP COMMUNI CATIONS DOWN DAP COMMUNI CATIONS DOWN DAP COMMUNI CATIONS DOWN
.3.2.2.14.1.4.200 7.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
Y_SRI/T FR ACG 1
Idl
during the standby initialization or in preparation for a BGDL/Redundancy switch. U-DIdl U-DIdl U-DIdl U-E-Idl Empty Empty All cells are Disabled. This is the result of a BR problem in the cell(s). All cells are Disabled. This is the result of a BR problem in the cell(s). All cells are Disabled. This is the result of a BR problem in the cell(s). ACG-DAP Communications are UP. The ACG is communicating with at least one DAP. ACG will now unlock the cells which are ready. ACG-BSC Mobis Link is UP. ACG will now unlock the cells which are ready. ACG-BSC Mobis Link is UP and all equipped cells are active. Site is providing full service(Site was ISO/SIO-DAP enabled). All ACG-DAP Links are down and the ACG is preparing to Lock all cells(Site is disabled for ISO/SIO-MOBIS). All ACG-DAP Links are down and the ACG is preparing to Lock all cells(Site is disabled for ISO/SIO-MOBIS). All ACG-DAP Links are DOWN in a(n) ISO/SIOMOBIS enabled site. ISO enabled site will be BARRED until the barred timer expires, then will enter ISO mode. An alarm will be sent when entering ISO mode, see ACG Quality of Service Failures(30). ACG-BSC Mobis link is DOWN and the ACG is preparing to Lock all cells(Site is disabled for ISO/SIO-DAP). ACG-BSC Mobis link is DOWN and the ACG is preparing to Lock all cells(Site is disabled for ISO/SIO-DAP). ACG-BSC Mobis link is down. Site lost Interconnect service support but providing other services(Site is ISO/SIO-DAP enabled). ACG-DAP Communications are Impaired. The DAP Communications Composite is Impaired-Y U Empty
U-E-Idl
ACG
U-E-A
Empty
Empty
U Empty
ACG
U-EImp L-E-Idl
Empty
Empty
U Empty
ACG
Empty
Empty
U Empty
ACG
L-E-Idl
U-E-Idl
Empty
Empty
U Empty
ACG
U-EImp U-E-A
U-E-A
Empty
Empty
U Empty
ACG
U-E-Idl
Empty
Empty
U Empty
ACG
U-EImp
U-E-Idl
Empty
Empty
U Empty
ACG
U-E-A
U-EImp
Empty
Empty
U Empty
2 0 4 2 0 4 2 0 4 2 0
MOBIS LINK DOWN MOBIS LINK DOWN MOBIS LINK DOWN DAP COMMUNI
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200
ACG
U-E-A
U-E-Idl
Empty
Empty
U Empty
ACG
U-EImp U-E-A
U-E-Idl
Empty
Empty
U Empty
ACG
U-EImp U-EImp
Empty
Empty
U Empty
ACG
U-E-A
Empty
Empty
U Reason Code # 205 not used.
October 30, 2008
ACG-63

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
CATIONS IMPAIRED CELL DISABLED
0.1.65535.1
2 0 8 2 0 9 2 0 9 2 1 0
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-E-A
U-EImp
Empty
Empty
one or more redundant DAP links are DOWN. The ACG may still be communicating with all DAPs, or as few as one. A cell is Disabled. This is the result of a BR problem in the cell.
U Reason Code # 207 not used.
CELL ENABLED CELL ENABLED CELL IMPAIRED
ACG
L-E-Idl
U-E-Idl
Empty
Empty
ACG
U-DIdl U-E-Idl
U-E-Idl
Empty
Empty
ACG
U-EImp
Empty
Empty
2 1 0
CELL IMPAIRED
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-E-A
U-EImp
Empty
Empty
2 1 1
POWER UP OR RESET
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
L-D-Idl
L-E-Idl
Empty
Empty
2 1 2 2 1 3 2 1 5 2 1 6 2 1 7
esmrStateCh angeEvent esmrStateCh angeEvent
DAP COMMUNI CATIONS ACTIVE ACG LEIDL TIMER EXPIRED ALL CELLS IDLE ALL CELLS ACTIVE MDG COMMUNI CATIONS IDLE
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-EImp
U-E-A
Empty
Empty
ACG
L-E-Idl
U-E-Idl
Empty
Empty
ACG
U-EImp U-EImp
U-E-Idl
Empty
Empty
A cell is Enabled. This trap indicates that the cell is in the process of coming up. Its final state is not known. A cell is Enabled. This trap indicates that the cell is in the process of coming up. Its final state is not known. A cell is Impaired. This cell now has a PCCH BR and less than all of its radios are available to process calls, which could be an improvement or degradation depending on the previous state. A cell is Impaired. This cell now has a PCCH BR and less than all of its radios are available to process calls, which could be an improvement or degradation depending on the previous state. Always sent on power up, or after a reset of the ACG. This State Change will not appear at the OMC because the ACG-OMC link will normally not have been established when this transition occurs. ACG-DAP Communications are Active. The DAP Communications Composite is Active-- all redundant DAP links are UP. Also, all the cells are fully functional, and the Mobis Link is UP. ACG timer for all cells to report L-E-Idl has expired. The ACG was waiting for all the cells to be ready to be unlocked, but will now unlock any cell which is ready. All cells are Idle.
U Empty
U Empty
U Empty
U Empty
U Empty
U Empty
U Empty
U Reason Code # 214 not used. U Empty
ACG
U-E-A
Empty
Empty
ACG
U-E-A
U-EImp
Empty
Empty
All cells are fully functional, ACG-DAP Communications are fully functional, ACG-MDG Communications are fully functional if the site is PD capable, and the Mobis Link is UP. ACG-MDG Communications are IDLE. The ACG is not communicating with any MDG. Only a site with one configured MDG will see this state change. Site must be Packet Data
U Empty
ACG-64
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
2 1 8
MDG COMMUNI CATIONS IMPAIRED
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-E-A
U-EImp
Empty
Empty
2 1 9 2 2 0
2 2 1 2 2 1 2 2 1 2 2 2 2 2 2 2 2 3 2 2 4 2 2 5
2 2 5
MDG COMMUNI CATIONS ACTIVE GPS TRACKIN G COMPLET ED ACTIVE GPS DISABLED ACTIVE GPS DISABLED ACTIVE GPS DISABLED ACTIVE GPS ACTIVE ACTIVE GPS ACTIVE ACTIVE GPS IMPAIRED ACTIVE IS LOCKED FOR SWITCH ACTIVE RESET EBTS TIMER EXPIRED ACTIVE RESET EBTS
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-EImp
U-E-A
Empty
Empty
ACG
L-E-Idl
U-E-Idl
Empty
Empty
Capable for this state change to be seen. ACG-MDG Communications are IMPAIRED. The ACG is not communicating with all MDGs. This state change will be seen upon the first MDG Link failure, and other MDG failures will be reported via the MCC and ML state change traps. Site must be Packet Data Capable for this state change to be seen. ACG-MDG Communications are ACTIVE. The ACG is communicating with all MDGs. Site must be Packet Data Capable for this state change to be seen. GPS tracking completed. ACG will now unlock the cells which are ready.
U Empty
U Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-E-A
U-DIdl U-DIdl U-DIdl U-E-Idl
Empty
Empty
Active ACG has received a critical fault due to the active GPS going disabled. Active ACG has received a critical fault due to the active GPS going disabled. Active ACG has received a critical fault due to the active GPS going disabled. Active ACG is active due to the active GPS going active. Active ACG is active due to the active GPS going active. Active ACG is impaired due to the active GPS going impaired. Active ACG has received a lock for switch message. Active ACG then prepares for the switch procedure by locking all the cells. Active ACG has timed out due to DAP and MOBIS links were down.
U Empty
ACG
U-EImp U-E-Idl
Empty
Empty
U Empty
ACG
Empty
Empty
U Empty
ACG
L-E-Idl
Empty
Empty
U Empty
ACG
U-EImp U-E-A
U-E-A
Empty
Empty
U Empty
ACG
U-EImp U-E-Idl
Empty
Empty
U Empty
ACG
U-EImp
Empty
Empty
U Empty
ACG
U-E-A
U-DIdl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-E-Idl
U-DIdl
Empty
Empty
Active ACG has timed out due to DAP and MOBIS links were down.
U Empty
October 30, 2008
ACG-65

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
2 2 5
2 2 6
2 2 6
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
2 2 7 2 2 8 8 0 0 8 0 1 8 0 1 8 0 1 8 0 1 8 0 2 8 0
TIMER EXPIRED ACTIVE RESET EBTS TIMER EXPIRED ALL CELLS IN ACTIVE ACG ARE LOCKED OR DISABLED ALL CELLS IN ACTIVE ACG ARE LOCKED OR DISABLED C1 LINK DOWN C1 LINK UP STANDBY GPS IMPAIRED STANDBY GPS DISABLED STANDBY GPS DISABLED STANDBY GPS DISABLED STANDBY GPS DISABLED STANDBY GPS ACTIVE STANDBY GPS
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-EImp
U-DIdl
Empty
Empty
Active ACG has timed out due to DAP and MOBIS links were down.
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-DIdl
L-D-Idl
Empty
Empty
This implies that all the cells in the active ACG are locked or disabled.
U This implies that all the cells in the active ACG are locked or disabled.
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1
ACG
U-E-Idl
L-E-Idl
Empty
Empty
This implies that all the cells in the active ACG are locked or disabled.
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200
ACG
U-E-A
U-EImp U-E-A
701
3000
This implies that the ACG-IVPU link is DOWN.
U Empty
ACG
U-EImp U-E-A
703
3000
This implies that the ACG-IVPU link is UP and all cells are active. Standby ACG is partially providing service due to the standby GPS going impaired. Standby ACG is disabled due to the standby GPS going disabled Standby ACG is disabled due to the standby GPS going disabled Standby ACG is disabled due to the standby GPS going disabled Standby ACG is disabled due to the standby GPS going disabled Standby ACG is becoming active due to standby GPS becoming active Standby ACG is becoming active due to standby GPS becoming active
U Empty
STANDB Y_ACG STANDB Y_ACG STANDB Y_ACG STANDB Y_ACG STANDB Y_ACG STANDB Y_ACG STANDB Y_ACG
U-EImp U-DIdl U-DIdl U-DIdl U-DIdl U-E-A
Empty
Empty
U Empty
L-E-Idl
Empty
Empty
U Empty
U-E-Idl
Empty
Empty
U Empty
U-EImp U-E-A
Empty
Empty
U Empty
Empty
Empty
U Empty
U-E-Idl
Empty
Empty
U Empty
U-EImp
U-E-A
Empty
Empty
U Empty
ACG-66
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
2 8 0 3
8 0 3
8 0 3
8 0 4
8 0 4
8 0 4
8 0 5
8 0 6 8 0 7
esmrStateCh
ACTIVE STANDBY acg LOCKED FOR SWITCH STANDBY acg LOCKED FOR SWITCH STANDBY acg LOCKED FOR SWITCH BACKGRO UND DOWNLO AD STARTED BACKGRO UND DOWNLO AD STARTED BACKGRO UND DOWNLO AD STARTED STANDBY ACG OPERATI NG MODE DETERMI NED STANDBY ACG HAS INVALID LOAD STANDBY ACG COMMUNI CATION DOWN STANDBY
0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-E-Idl
L-E-Idl
Empty
Empty
Standby ACG has received a lock message and is preparing to switch
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-EImp
L-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-E-A
L-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-E-Idl
L-E-Idl
Empty
Empty
Standby ACG is locked due to the operator initiating aBackground Download.
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-EImp
L-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-E-A
L-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
L-E-Idl
U-E-Idl
Empty
Empty
The standby ACG has come up after a reset and will be in the Redundant Mode.
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-E-Idl
L-E-Idl
Empty
Empty
Standby ACG has come up with an invalid load after a reset and will be reset again.
U Empty
STANDB Y_ACG
L-E-Idl
U-DIdl
Empty
Empty
Communication with the standby ACG is lost.
U Empty
1.3.6.1.4.1.161.3
STANDB
U-E-Idl
U-D-
Empty
Empty
U Empty
October 30, 2008
ACG-67

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
angeEvent
0 7
8 0 7
8 0 7
8 0 7
8 0 8
8 0 8
8 0 8
8 0 8
8 0 9 8 0 9
ACG COMMUNI CATION DOWN STANDBY ACG COMMUNI CATION DOWN STANDBY ACG COMMUNI CATION DOWN STANDBY ACG COMMUNI CATION DOWN STANDBY ACG COMMUNI CATION UP STANDBY ACG COMMUNI CATION UP STANDBY ACG COMMUNI CATION UP STANDBY ACG COMMUNI CATION UP STANDBY ACG REQUEST ING LOAD STANDBY ACG REQUEST ING LOAD
.3.2.2.14.1.4.200 0.1.65535.2
Y_ACG
Idl
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-EImp
U-DIdl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-E-A
U-DIdl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-DIdl
U-DIdl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-DIdl
L-E-Idl
Empty
Empty
Communication with the standby ACG is reestablished.
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
L-E-Idl
U-E-A
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
L-E-Idl
U-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
L-E-Idl
U-EImp
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-DIdl
L-E-Idl
Empty
Empty
Standby ACG is requesting a crossload after an unexpected reset.
U Empty
STANDB Y_ACG
U-EImp
L-E-Idl
Empty
Empty
U Empty
ACG-68
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
8 0 9 8 0 9 8 1 0
8 1 0
8 1 0
8 1 1
8 1 1
8 1 1
7 0 0 7 0
STANDBY ACG REQUEST ING LOAD STANDBY ACG REQUEST ING LOAD STANDBY ACG LOST REDUNDA NCY STANDBY ACG LOST REDUNDA NCY STANDBY ACG LOST REDUNDA NCY STANDBY ACG REESTAB LISHED REDUNDA NCY STANDBY ACG REESTAB LISHED REDUNDA NCY STANDBY ACG REESTAB LISHED REDUNDA NCY ACTIVE ACG IDLE
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-E-A
L-E-Idl
Empty
Empty
S t a t u s U Empty
STANDB Y_ACG
U-DIdl
L-E-Idl
Empty
Empty
U Empty
STANDB Y_ACG
U-E-Idl
L-E-Idl
Empty
Empty
Standby ACG lost redundancy due to Active ACG OLCC Switch has been completed, but Standby ACG OLCC Switch hasnt completed yet. Standby ACG lost redundancy due to Active ACG OLCC Switch has been completed, but Standby ACG OLCC Switch hasnt completed yet. Standby ACG lost redundancy due to Active ACG OLCC Switch has been completed, but Standby ACG OLCC Switch hasnt completed yet. Standby ACG reestablished redundancy after Standby ACG OLCC Switch has been completed.
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-EImp
L-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-E-A
L-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-EImp
U-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-EImp
U-EImp
Empty
Empty
Standby ACG reestablished redundancy after Standby ACG OLCC Switch has been completed.
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 0.1.65535.2
STANDB Y_ACG
U-EImp
U-E-A
Empty
Empty
Standby ACG reestablished redundancy after Standby ACG OLCC Switch has been completed.
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200
EBTS
U-E-A
U-E-Idl
Empty
Empty
ACTIVE ACG IDLE
EBTS
U-EImp
U-E-Idl
Empty
Empty
EBTS is idle. It is either due to the active ACG initializing, or due to active ACG shutting down call processing, or due to active ACG losing some critical resources EBTS is idle. It is either due to the active ACG initializing, or due to active ACG shutting down
U Empty
U Empty
October 30, 2008
ACG-69

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
0 esmrStateCh angeEvent 7 0 0 7 0 1 7 0 1 7 0 2 7 0 2 7 0 2 7 0 3 7 0 4 7 0 5 7 0 6 7 0 7 7 0 8 7 1 0 7 1 ACTIVE ACG IDLE
6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 EBTS 1 U-DIdl U-E-Idl Empty Empty
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
ACTIVE ACG IMPAIRED ACTIVE ACG IMPAIRED ACTIVE ACG DISABLED ACTIVE ACG DISABLED ACTIVE ACG DISABLED ACTIVE ACG ACTIVE STANDBY ACG LOCKED STANDBY ACG IMPAIRED STANDBY ACG ACTIVE STANDBY ACG DISABLED ACTIVE ACG CRITICAL FAULT EBTS STARTIN G AUTO SWITCH EBTS STARTIN
EBTS
U-E-Idl
U-EImp U-EImp U-DIdl U-DIdl U-DIdl U-E-A
Empty
Empty
EBTS
U-E-A
Empty
Empty
EBTS
U-E-Idl
Empty
Empty
call processing, or due to active ACG losing some critical resources EBTS is idle. It is either due to the active ACG initializing, or due to active ACG shutting down call processing, or due to active ACG losing some critical resources EBTS is semi-operational. Either the active ACG is coming up or it has lost some critical resources. EBTS is semi-operational. Either the active ACG is coming up or it has lost some critical resources. EBTS is Disabled due to the active ACG being disabled. EBTS is Disabled due to the active ACG being disabled. EBTS is Disabled due to the active ACG being disabled. EBTS is Active due to active ACG starting to provide Full service. EBTS is impaired due to standby ACG locked
U Empty
U Empty
U Empty
U Empty
EBTS
U-E-A
Empty
Empty
U Empty
EBTS
U-EImp U-EImp U-E-A
Empty
Empty
U Empty
EBTS
Empty
Empty
U Empty
EBTS
U-EImp U-EImp U-E-A
Empty
Empty
U Empty
EBTS
U-E-A
Empty
Empty
EBTS is impaired since the standby ACG is impaired. EBTS is Active due to the standby ACG and active ACG providing full service EBTS is impaired since the standby ACG is disabled EBTS is trying to recover from the critical fault in the active ACG
U Empty
EBTS
U-EImp U-E-A
Empty
Empty
U Empty
EBTS
U-EImp U-E-Idl
Empty
Empty
U Empty
EBTS
U-DIdl
Empty
Empty
U Empty
EBTS
U-DIdl
U-E-Idl
Empty
Empty
EBTS in initiating an automatic (without operator intervention) switch to bring up the standby ACG as active EBTS in initiating an automatic (without operator intervention) switch to bring up the standby
U Reason Code 709 not used
EBTS
U-DIdl
U-E-Idl
Empty
Empty
U Empty
ACG-70
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
0 esmrStateCh angeEvent 7 1 1
7 1 1
7 1 1
7 1 2
7 1 2
7 1 2
7 1 4 7 1 4 7 1 4
G AUTO SWITCH EBTS STARTIN G MANUAL SWITCH EBTS STARTIN G MANUAL SWITCH EBTS STARTIN G MANUAL SWITCH EBTS STARTIN G BGDL MANUAL SWITCH EBTS STARTIN G BGDL MANUAL SWITCH EBTS STARTIN G BGDL MANUAL SWITCH CRITICAL FAULTS NOT CLEARED CRITICAL FAULTS NOT CLEARED CRITICAL FAULTS NOT CLEARED
6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 EBTS 1 U-E-A U-E-Idl Empty Empty
ACG as active EBTS is performing an operator requested redundancy switch Y U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1
EBTS
U-EImp
U-E-Idl
Empty
Empty
EBTS is performing an operator requested redundancy switch
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1
EBTS
U-DIdl
U-E-Idl
Empty
Empty
EBTS is performing an operator requested redundancy switch
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1
EBTS
U-E-A
U-E-Idl
Empty
Empty
EBTS is performing an operator requested BGDL switch after it has received the background download load from the OMC
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1
EBTS
U-EImp
U-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1
EBTS
U-DIdl
U-E-Idl
Empty
Empty
U Empty
1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1 1.3.6.1.4.1.161.3 .3.2.2.14.1.4.200 6.1.65535.1
EBTS
U-E-A
U-E-Idl
Empty
Empty
EBTS had critical faults even after initialization and is trying to recover from it.
U Reason Code 713 not used
EBTS
U-EImp
U-E-Idl
Empty
Empty
U Empty
EBTS
U-DIdl
U-E-Idl
Empty
Empty
U Empty
October 30, 2008
ACG-71
Release SR17.0
__________________________________ Events
Event Type
R e a s o n C o d e
OMC Text
MOI Info (Id)
M I O n I s t I n f o ( L a b e l ) E B T S E B T S
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Background Download
1 EMPTY 0
started 1, 0,1, 0
Background Download
1 EMPTY 0
failedAborted 3 , 0,1,[1-6]
E EMPTY M P T Y E EMPTY M P T Y
EMPTY
EMPTY
EMPTY
EMPTY
N U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Background Download
1 EMPTY 0
completedSu ccessfully 4, 0, 1, 0
E B T S E B T S E B T S
Background Download Switch
1 EMPTY 1
started 1, 0,1, 0
Background Download Switch
1 EMPTY 1
failedAborted 3, 0,1,0
E EMPTY M P T Y E EMPTY M P T Y E EMPTY M P T Y
EMPTY
EMPTY
EMPTY
EMPTY
N U 1. Standby ACG failed during Background Download2. BRC failed during Background Download3. BRC download in progress4. Active ACG failed during Background Download5. Download session failed during Background Download6. Miscellaneous failure during Background Download N U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Background
1 EMPTY
completed
E E EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U Background Download is not received successfully or the EBTS is already in the process of doing a switch or standby failed during switch. N U EMPTY
ACG-72
October 30, 2008
Release SR17.0
Event Type
R e a s o n C o d e

M I O n I s t I n f o ( L a b e l ) B M T P S T Y
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Download Switch
Background Download Abort
1 EMPTY 2
Redundancy Switch
2 EMPTY 0
Successfully 4, 1, 1, <LV> where: <LV> = aabbccdd (where: aa = 0x00 - 0xFF bb = 0x00 0xFF cc = 0x00 - 0xFF dd = 0x00 0xFF) completedSu ccessfully 4, 1, 1, <LV> where: <LV> = aabbccdd (where:aa = 0x00 0xFFbb = 0x00 0xFFcc = 0x00 0xFFdd = 0x00 - 0xFF) started 1, 0,1, 0
E B T S
E EMPTY M P T Y
EMPTY
EMPTY
EMPTY
EMPTY
N U EMPTY
E B T S E B T S E B T S E B T S
Redundancy Switch
2 EMPTY 0
failedAborted 3, 0,1,[1-2]
Redundancy Switch
2 EMPTY 0
completedSu ccessfully 4, 0, 1,0
OLCC Background Download
3 EMPTY 0
E M P T Y E M P T Y E M P T Y E M P T Y
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U 1. Standby ACG is Locked 2. Standby ACG is Disabled
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U EMPTY
October 30, 2008
ACG-73

Event Type
R e a s o n C o d e
Release SR17.0
To State Related State Changes Related Alarms Event Description
OMC Text
MOI Info (Id)
M I O n I s t I n f o ( L a b e l ) E B T S
From State
Comments & Notes
OLCC Background Download
3 EMPTY 0
failed Aborted 3, 0, 1,[ 0x20 - 0x27 ]
E EMPTY M P T Y
EMPTY
EMPTY
EMPTY
EMPTY
OLCC Switch
3 EMPTY 2
E B T S E B T S
OLCC Switch
3 EMPTY 2
failed Aborted 3, 0, 1,[ 0x20 - 0x22 ,0x30]
EMPTY
EMPTY
EMPTY
EMPTY
N U 0x20 - OLCC file format is incorrect (i.e. format is not 0x00000001) 0x21 - OLCC delta base version does not match ACG current version 0x22 - OLCC file is corrupt (i.e. invalid delta markers, etc.) 0x23 - PFTP session aborted due to BR download in progress0x24 PFTP session aborted due to BR download required0x25 - Invalid file received 0x26 - OLCC Background Download in progress0x27 OLCC next data base version is 0 N U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
OLCC Background Download Abort
3 EMPTY 1
E B T S E B T S E B T
OLCC Background Download Abort
3 EMPTY 1
failedAborted 3, 0,1,0
ACG Hardware Configuration Trap
E EMPTY M P
EMPTY
E EMPTY M P T Y E EMPTY M P T Y E EMPTY M P
EMPTY
EMPTY
EMPTY
EMPTY
N U 0x20 - OLCC file format is incorrect (i.e. format is not 0x00000001) 0x21 - OLCC delta base version does not match ACG current version 0x22 - OLCC file is corrupt (i.e. invalid delta markers, etc.) 0x30 - OLCC Switch Failure N U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U OLCC Switch is in progress andOLCC Abort is impossible.
EMPTY
EMPTY
EMPTY
<REDUNDANT STATUS>, <ETHERNET MAC ADDRESS>, <GPS SOFT-
N U This info will be sent to the OMC only after the ACG has gotten the GPS
ACG-74
October 30, 2008
Release SR17.0
Event Type
R e a s o n C o d e

M I O n I s t I n f o ( L a b e l ) S T Y
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
T Y
Availability Trap
E M P T
<universal time>_<sequence number>_<secondary id>_<new
EMPTY
E B T S
E EMPTY M P T
EMPTY
EMPTY
EMPTY
WARE VERSION>, <ACG CPU ESN>, <ACG ROM VERSION> where: <REDUNDANT STATUS> = Active ACG- 1, Standby ACG - 2, <ETHERNET MAC ADDRESS> = ASCII<GPS SOFTWARE VERSION> = ASCII (decimal), Range: 3.3 999999.999 (variable number of characters up to a maximum of 10), (hexadecimal), Range: 000000000001 FFFFFFFFFFFE (12 digits), <GPS SOFTWARE VERSION> = ASCII (decimal), Range: 3.3 999999.999 (variable number of characters up to a maximum of 10), <ACG CPU ESN> = ASCII (decimal), Range: 0000000000000000 9999999999999999 (variable number of digits up to a maximum of 16), <ACG ROM VERSION> = ASCII (numbers are hexadecimal), Range: LAA.BB.CC (9 characters) where: L:D = Development versionB = Beta versionR = Release versionAA:01 = VME 02 = iSC2 03 = iSC3BB:00-FF = Major revision numberCC:00-FF = Minor revision number Event is generated when the ACG mode changes from in service to out of service and from out of
Software Version from its hardware.
N U This message is sent until acknowledged by the OMC.
October 30, 2008
ACG-75

Event Type
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
M I O n I s t I n f o ( L a b e l ) Y
From State
Comments & Notes
Y mode>_<time of switch>_<reason code>_<old mode>_<additional text>_<reason text>
service to inservice. <universal time> = time in GMT when event was generated yymmddhhmmssz, <sequence number> = integer incremented for each new availability trap, Range: "0" - "FFFF", <secondary id> = 0, <new mode> and <old mode> = Maintenance "1", Standby "2", Active "3", <time of switch> = time in GMT format, <reason code> = reason why ACG entered this mode, Range "1" "18", <additional text> and <reason text> are character strings
ACG-76
October 30, 2008
Release SR17.0
_________________________________ Alarms
Alarm Type Alarm Code OMC Text MOI Info (Id) MOI Info (Label)
I n s t
APD
Remedy
R e p o r t O u t a g e C h a n g e S t a t u s U EMPTY
Alarm Code Text
S e v e r i t y
R e l a t e d
Comments & Notes
1056
Link Version Check procedure failed
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.2.1.0
APD_DAP_ LINK
No response from DAP
1056
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.2.1.0
APD_DAP_ LINK
Version Mismatch
1056
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.2.1.0
APD_DAP_ LINK
Status field indicates failure.
1056
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.2.1.0
APD_DAP_ LINK
ITC header source or destination does not match apdDapId or nodeId.
1056
1.3.6.1.4.1.1 61.3.3.10.5.6
APD_DAP_ LINK
Clear link version check procedure
A l a r m s C E 110, 112, 302 r M i P t T i Y c a l C E 110, 112, 302 r M i P t T i Y c a l C E 110, 112, 302 r M i P t T i Y c a l C E 110, 112, 302 r M i P t T i Y c a l C E EMPTY l M
No remedy. APD will start Link Version Check Procedure till it receives a success indication. APD will start Link Version Check Procedure till it receives a success indication. APD will start Link Version Check Procedure till it receives a success indication. APD will start Link Version Check Procedure till it receives a success indication. No remedy. APD cleared
& Y / C N l e a r R N
R N U
EMPTY
R N U
EMPTY
R N U
EMPTY
C N U
EMPTY
October 30, 2008
APD-1

I n s t
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d
Remedy
R e p o r t
O u t a g e
Comments & Notes
.1.1.2.2.1.0
alarm
A l a r m s e P a T r Y W a r n i n g C r i t i c a l M a j o r E EMPTY M P T Y
& Y / C N l e a r link version procedure failed alarm 1056. No remedy. APD will recover by itself.
1071
Internal software error
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.1.0
APD_GEN
File name:<file_name>, Line num:<line_num>, Reason: <reason_string> APD will reset. File name:<file_name>, Line num:<line_num>, Reason: <reason_string>
R N U
EMPTY
1071
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.1.0
APD_GEN
E EMPTY M P T Y
APD will reset.
R Y U
EMPTY
1074
Invalid logical FRVD from the DAP
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.9.1.3.x .y
APD_FR_A CG
x : 1 0 2 4 y : 1 3 7 0 0
Device type: <Device Type>, Device ID: <FRVD_ID>
E EMPTY M P T Y
1074
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.9.1.3.x .y
APD_FR_I SG
x : 4 0 9 6
M a j o r
E EMPTY M P T Y
APD will discard the request as it receives a FRVD target whose RowStatus is not Active in the apdFrTable. The operator should verify that the OMC has provided the target information to the DAP correctly that is the same as the one in the apdFrTable. APD will discard the request as it receives a FRVD target whose
R N U
EMPTY
R N U
EMPTY
APD-2
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s y : 1 3 7 0 0 RowStatus is not Active in the apdFrTable. The operator should verify that the OMC has provided the target information to the DAP correctly that is the same as the one in the apdFrTable. APD will discard the request as it receives a FRVD target whose RowStatus is not Active in the apdFrTable. The operator should verify that the OMC has provided the target information to the DAP correctly that is the same as the one in the apdFrTable. If the OMC was the source of this error, then should be corrected at OMC.
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
1074
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.9.1.3.x .y
APD_FR_I DAC
x : 5 1 2 0 y : 1 3 7 0 0
M a j o r
E EMPTY M P T Y
R N U
EMPTY
1076
Error in configuration data file(s)
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.1.0
APD_GEN
<field> was out of range and is changed to <new_value>
I n d e t e r m i n
E EMPTY M P T Y
R N U
EMPTY
October 30, 2008
APD-3

I n s t
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s a t e C r i t i c a l M i n o r
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
1076
Error in configuration data file(s)
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.1.0
APD_GEN
<field> was out of range. APD will reset.
E EMPTY M P T Y
1084
Impaired status: No response
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.2.1.0
APD_DAP_ LINK
Not receiving an Impaired Status Response.
E EMPTY M P T Y
1084
Impaired status: No response
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.2.1.0
APD_DAP_ LINK
Clear impaired status no response alarm
1046
FRU failure
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.7.2.n
APD_FRU_ IO
1 4
Source of error within <slot_num> is uncertain.
1046
FRU failure
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.7.2.n
APD_FRU_ IO
1 4
Clear FRU status alarm
1094
Hardware configuration error
1.3.6.1.4.1.1 61.3.3.10.5.6 .1.1.2.7.2.n
APD_FRU_ IO
1 4
Unrecognized version <version_num> in <slot_num>.
C l e a r M a j o r C l e a r M a j o r
EMPTY
EMPTY
APD will reset. If the OMC was the source of this error, then should be corrected at OMC. No remedy. APD will keep sending Impaired Status indication until DAP acknowledges it. No remedy. APD cleared Impaired status alarm 1084. Replace that particular unit.
R Y U
EMPTY
R N U
EMPTY
C N U
EMPTY
R N U
EMPTY
EMPTY
No remedy. APD cleared FRU failure alarm 1046. If necessary replace the respective Hardware unit.
C N U
EMPTY
EMPTY
R N U
EMPTY
APD-4
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label )
I n s t
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 0 1
ALL SPANS/LINK S FUNCTIONA L CALL CAPACITY EXCEEDED NO LONGER EXCEEDING CALL CAPACITY AT LEAST ONE OF IMPAIRED CONDITIONS ARE TRUE
1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0
APD_N ODE
0 U-D-Idl
U-E-A
301
EMPTY
EMPTY
S t a t u s N U
1 0 2 1 0 3
1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0
APD_N ODE
0 U-E-A
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
Link Version Check procedure has completed successfully. None of the impaired conditions are true. This reverses the effects of state change 110 or 112. APD has exceeded its call capacity threshold.
APD_N ODE
0 U-E-Imp
U-E-A
EMPTY
EMPTY
EMPTY
N U
1 0 4
APD_N ODE
0 U-D-Idl
U-E-Imp
301
EMPTY
EMPTY
N U
1 0 5
SPAN DISABLED
1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161
APD_N ODE
0 U-E-A
U-E-Imp
202
EMPTY
EMPTY
N U
1 0 6 1 0 7 1 0
PORT OVERLOADE D ENTERED CPU LOAD SHEDDING EXITED PORT
APD_N ODE
0 U-E-A
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
APD is no longer exceeding its call capacity threshold. None of the impaired conditions are true. This reverses the effects of state change 102 or 115. Link (APD-DAP) is operational and Link Version Check procedure has completed successfully, but the APD is in one of the impaired conditions. This reverses the effects of state change 110 or 112. At least one but not all spans (APD-SM) are operational, and link (APD-DAP) is operational and Version Check procedure has completed successfully. Any one of the ports are overloaded.
APD_N ODE
0 U-E-A
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
APD has entered load shedding mode 1 or higher.
APD_N ODE
0 U-E-Imp
U-E-A
EMPTY
EMPTY
EMPTY
N U
None of the ports are overloaded. None of the
October 30, 2008
APD-5

State Changes
R e a s o n C o d e
Release SR17.0
Related Alarms Event Description
O u t a g e ( Y / N ) C h a n g e S t a t u s impaired conditions are true. This reverses the effects of state change 106 or 117. APD in not in load shedding mode 1 or higher. None of the impaired conditions are true. This reverses the effects of state change 107 or 113. APD-DAP logical link (LAPD) is disabled.
OMC Text
MOI Info (Id)
MOI Info (Label )
I n s t
From State
To State
Comments & Notes
1 0 9
OVERLOADE D CONDITION EXITED CPU LOAD SHEDDING
.3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. APD_N ODE 0 U-E-Imp U-E-A EMPTY EMPTY EMPTY N U
1 1 0 1 1 1
LINK DISABLED
APD_N ODE
0 U-E-A
U-D-Idl
302
1056
EMPTY
N U
ALL SPANS OPERATION AL
APD_N ODE
0 U-E-Imp
U-E-A
201
EMPTY
EMPTY
N U
1 1 2 1 1 3 1 1 4 1 1 5 1 1 6
LINK DISABLED
APD_N ODE
0 U-E-Imp
U-D-Idl
302
1056
EMPTY
N U
All Spans (APD-SM) are operational. None of the impaired conditions are true. This reverses the effects of state change 105 or 120. APD-DAP logical link (LAPD) is disabled.
ENTERED CPU LOAD SHEDDING EXITED CPU LOAD SHEDDING MODE EXCEEDED THE CALL CAPACITY THRESHOLD NO LONGER EXCEEDING THE CALL CAPACITY THRESHOLD PORT OVERLOADE D PORT NO LONGER OVERLOADE D SPAN
APD_N ODE
0 U-E-Imp
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
APD is in impaired state for other reason.
APD_N ODE
0 U-E-Imp
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
APD_N ODE
0 U-E-Imp
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
This reverses the effects of state change 107 or 113. APD is still in impaired state for other reason. APD is in impaired state for other reason.
APD_N ODE
0 U-E-Imp
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
This reverses the effects of state change 102 or 115. APD is still in impaired state for other reason. APD is in impaired state for other reason.
1 1 7 1 1 8 1
APD_N ODE
0 U-E-Imp
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
APD_N ODE
0 U-E-Imp
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
esmrStateCh
APD_N
0 U-E-Imp
U-E-Imp
201
EMPTY
EMPTY
N U
This reverses the effects of state change 106 or 117. APD is still in impaired state for other reason. This reverses the effects of
APD-6
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Label ) I n s t
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
1 9 1 2 0 1 2 1 1 2 2 1 2 3
FUNCTIONA L SPAN DOWN
ENTERED MMI IMPAIRED ENTERED MMI IMPAIRED EXITED MMI IMPAIRED
4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0
ODE
APD_N ODE
0 U-E-Imp
U-E-Imp
202
EMPTY
EMPTY
N U
state change 105 or 120. APD is still in impaired state for other reason. APD is in impaired state for other reason.
APD_N ODE
0 U-E-A
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
APD has been forced to go to impaired state by MMI command. APD has been forced to go to impaired state by MMI command. APD has been exited from impaired state by MMI command. None of the impaired conditions are true. This reverses the effects of state change 121 or 122. This reverses the effects of state change 121 or 122. APD is still in impaired state for other reason. Span is operational.
APD_N ODE
0 U-E-Imp
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
APD_N ODE
0 U-E-Imp
U-E-A
EMPTY
EMPTY
EMPTY
N U
1 2 4 2 0 1
EXITED MMI IMPAIRED
SPAN FUNCTIONA L
2 0 2
SPAN DOWN
3 0 1
LOGICAL LINK FUNCTIONA L LOGICAL LINK DOWN
3 0 2
1.3.6.1. 4.1.161 .3.3.10. 2.3.1.0 1.3.6.1. 4.1.161 .3.3.10. 5.6.1.1. 2.4.1.1. n 1.3.6.1. 4.1.161 .3.3.10. 5.6.1.1. 2.4.1.1. n 1.3.6.1. 4.1.161 .3.3.10. 5.6.1.1. 2.2.1.0 1.3.6.1. 4.1.161 .3.3.10. 5.6.1.1. 2.2.1.0
APD_N ODE
0 U-E-Imp
U-E-Imp
EMPTY
EMPTY
EMPTY
N U
APD_S PAN
1 U-D-A 4
U-E-A
EMPTY
EMPTY
EMPTY
N U
APD_S PAN
1 U-E-A 4
U-D-A
EMPTY
EMPTY
EMPTY
N U
Span is not operational.
APD_D AP_LIN K
0 U-D-A
U-E-A
EMPTY
EMPTY
EMPTY
N U
Logical link is operational and Link Version Check Procedure has completed successfully.
APD_D AP_LIN K
0 U-E-A
U-D-A
202
1056
EMPTY
N U
Either LAPD down or Link Version Check Procedure failed. Related state change 202 can only cause this if it is the control span that goes down. Note this
October 30, 2008
APD-7

State Changes
R e a s o n C o d e
Release SR17.0
Related Alarms Event Description
O u t a g e ( Y / N ) C h a n g e S t a t u s event may occur even if the control span is still enabled (e.g.- LAPD failure).
OMC Text
MOI Info (Id)
MOI Info (Label )
I n s t
From State
To State
Comments & Notes
APD-8
October 30, 2008
Release SR17.0
__________________________________ Events
Event Type OMC Text MOI Info (Id)
MOI Info (Labe l) I n s t
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N ) N
Restart Trap
Action Status
New Operate State: <operational state> New Usage State: <usage state> New Admin State: <administrative state> System ROM Version: <boot ROM version> System Load Version: <software Load version> System DB Version: <database version> System Code Version: <code version> Description: <system description> System Reset Reason: <latest reset reason> System Outage Time: <outage time since latest reset> System Reboot Time: <reboot time> System Boot Diagnostics: <boot diagnostics> Background Download completed successfully
1.3.6.1 .4.1.16 1.3.3.1 0.2.3.1 .0
APD_ NODE
0 EMPTY
EMPTY
EMPTY
EMPTY
This event is used to inform the OMC whenever APD switches its application code load or when it reboots. It also tells the OMC that SNMP agent is operational and is ready to handle request.
C Comments h a n g e S t a t u s U EMPTY
& Notes
Action Status
Background Download failed
Action Status
Background Download
1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.1.0 1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.1.0 1.3.6.1
Backgr ound Downl oad(bg dlStart) Backgr ound Downl oad(bg dlStart) Backgr
E EMPTY M P T Y E EMPTY M P T Y E EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has completed successfully.
N U EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has failed.
N U EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC
N U EMPTY
October 30, 2008
APD-9

MOI Info (Labe l) I n s t
Release SR17.0
From State
To State
Comments & Notes
aborted
Action Status
Background Download aborted successfully
.4.1.16 1.3.3.1 0.2.10. 1.1.0 1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.2.0
Action Status
Background Download incorrect action status
1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.2.0
Action Status
Background Download Switch completed successfully
Action Status
Background Download Switch aborted
1.3.6.1 .4.1.16 1.3.3.1 0.2.11. 1.1.0 1.3.6.1 .4.1.16 1.3.3.1 0.2.11. 1.1.0
ound Downl oad(bg dlStart) Backgr ound Downl oad Abort( bgdlAb ort) Backgr ound Downl oad Abort( bgdlAb ort) OnLine Switch (olcSwi tch) OnLine Switch (olcSwi tch)
M P T Y E EMPTY M P T Y
background download has been aborted.
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has been aborted successfully.
N U EMPTY
E EMPTY M P T Y
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download could not be aborted due to an OLCC switch still in progress.
N U EMPTY
EMPTY
EMPTY
EMPTY
Event is generated when OLCC switch has completed successfully.
N U EMPTY
EMPTY
EMPTY
EMPTY
Event is generated when OLCC switch has been aborted.
N U EMPTY
APD-10
October 30, 2008
Release SR17.0
_________________________________ Alarms
Alarm Type
Alarm Code
BRC
Related Alarms
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Severity
Remedy
R e p o r t
O u t a g e
Comments & Notes
32001
BR Reset requested by the ACG or OMC
1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>. <cabinet>.<positi on>
CntrlBrd
32001
BR Reset requested by the ACG or OMC
CntrlBrd
32001
LAPD Link
CntrlBrd
32001
LAPD Link
CntrlBrd
32002
BR Reset Error
CntrlBrd
<instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[1-
BRC Reset requested by ACG
Clear
EMPTY
EMPTY
None
& Y / C N l e a r C Y
EMPTY
BRC Reset requested by OMC
Clear
EMPTY
EMPTY
None
C Y
EMPTY
LAPD is down
Critical
EMPTY
EMPTY
None
R Y
R = LDI (Legacy) or BR Reset (Quad/EBRC)
LAPD is up
Clear
EMPTY
EMPTY
None
C N
C = Enable Condition (Legacy) or Report Only (Quad/EBRC)
BR Reset Error; <Task: X; File_ID: X; Line: X>.
Clear
EMPTY
EMPTY
None
C Y
EMPTY
October 30, 2008
BRC-1

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
Severity Related Alarms
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r processingF ailureEvent 32002 BR Reset Error 1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>. <cabinet>.<positi on> CntrlBrd 8],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 61BR Reset Error. Data1: <X>; Data2: <X>. X Clear EMPTY EMPTY None C Y
EMPTY
32003
BR Processing Warning
CntrlBrd
Warning
EMPTY
EMPTY
None
R N
EMPTY
32004
BR Diagnostics
CntrlBrd
Warning
EMPTY
EMPTY
None
C N
EMPTY
32005
BR MMI Operator Reset
CntrlBrd
MMI Operator Reset
Clear
EMPTY
EMPTY
None
C Y
EMPTY
32006
BR Download Timeout
CntrlBrd
Download Time-out
Critical
EMPTY
EMPTY
None
C Y
BR Resets
32007
BR DSP Alarm
CntrlBrd
DSP Alarm X
Critical
EMPTY
EMPTY
None
C Y
BR Resets
32008
BR MMI Operator Dekey
1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>.
CntrlBrd
BR Intrusive Disable by
Critical
EMPTY
EMPTY
None
R Y C
R = LDI; C = Enable Condition
BRC-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r <cabinet>.<positi on> 66, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [1MMI Command
32009
BR Intrusive Test
CntrlBrd
DSP EMU Download in Progress
Critical
EMPTY
EMPTY
None
R Y C
35000
No Reset Alarm was pending
CntrlBrd
No Reset Alarm was pending
Clear
EMPTY
EMPTY
None
C N
EMPTY
35001
External Reference Failure
CntrlBrd
External Reference Failure
Critical
EMPTY
EMPTY
Site Service Call, if persiste nt
R Y C
35002
Station Reference Failure
CntrlBrd
16 MHz Station Reference Failure.
Critical
EMPTY
EMPTY
R Y C
35003
Pendulum Lock Failure
CntrlBrd
Pendulum Lock Failure.
Critical
EMPTY
EMPTY
R Y C
R = LDI (Legacy); C = Enable Condition (Legacy)
35004
Pendulum Failure
CntrlBrd
Pendulum Failure
Critical
EMPTY
EMPTY
R Y C
LDI (Legacy)
October 30, 2008
BRC-3

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r 8],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[1-
35005
SPI Bus Failure
CntrlBrd
SPI Bus Failure.
Critical
EMPTY
EMPTY
R Y
Not implemented
35006
RF Hardware Initialization Failure
CntrlBrd
RF Hardware Initializatio n Failure.
Critical
EMPTY
EMPTY
R Y
LDI
35007
Control Board EEPROM failure
CntrlBrd
Control Board EEPROM Failure
Critical
EMPTY
EMPTY
R Y
Not implemented
35008
GPS Failure
CntrlBrd
1PPS Signal Missing.
Major
EMPTY
EMPTY
R N
EMPTY
35008
GPS Failure
CntrlBrd
1PPS Signal Recovered .
Clear
EMPTY
EMPTY
C N
EMPTY
35009
Unable to key
CntrlBrd
Unable to key.
Critical
EMPTY
EMPTY
R Y C
R = Lock Condition; C = Report Only
BRC-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r equipmentF ailureEvent 35010 Frequencies do not match Band 1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>. <cabinet>.<positi on> CntrlBrd 8],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, Frequenci es do not match Band. Critical EMPTY EMPTY Site Service Call, if persiste nt R Y
R = LDI (Quad/EBRC) or Reset (Legacy)
35011
FRU configuration error
CntrlBrd
FRU configurati on error.
Critical
EMPTY
EMPTY
R Y
Lock Condition
35012
Tx DSP sanity check Failure
CntrlBrd
Tx DSP sanity check Failure.
Critical
EMPTY
EMPTY
R Y C
35013
Rx DSP sanity check Failure
CntrlBrd
Rx DSP sanity check Failure
Critical
EMPTY
EMPTY
R Y C
35014
DSP SSI Failure
CntrlBrd
SSI Failure
Critical
EMPTY
EMPTY
C Y
BR Resets
35015
BR Unlocked, Not Keyed
CntrlBrd
WARNING : BR Unlocked, Not Keyed: Data = X
Indeterminat e
EMPTY
EMPTY
None
R Y
Lock Condition (Legacy)
35016
Invalid BRC FRU revision number
1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in
CntrlBrd
WARNING : Invalid
Critical
EMPTY
EMPTY
Site Service
R Y
LDI
October 30, 2008
BRC-5

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r stance>.<type>. <cabinet>.<positi on> 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = BRC revision number Call, if persiste nt
35017
BR Front Panel Reset
CntrlBrd
BR Reset due to Front Panel Reset
Clear
EMPTY
EMPTY
None
C Y
EMPTY
35018
No Reset Alarm was pending on Enhanced BR
CntrlBrd
No Reset Alarm was pending on Enhanced BR
Clear
EMPTY
EMPTY
None
C N
(Legacy)
35019
BR loss of External Reference Reset
CntrlBrd
BR Reset due to loss of External Reference
Clear
EMPTY
EMPTY
C Y
EMPTY
35020
BR Cold Boot
CntrlBrd
BR Cold Boot: No Previous Reset Error
Clear
EMPTY
EMPTY
None
C N
EMPTY
35021
TFR Timing Error
CntrlBrd
TFR TIMING error received from DSP <X>. ROM rev. does not support setting of RX_FRU_
Indeterminat e
EMPTY
EMPTY
R N
EMPTY
35022
ROM revision incompatible with 3 RX FRU
CntrlBrd
Warning
EMPTY
EMPTY
R N
Possible Degraded Operation (Legacy)
BRC-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r [8],<cabinet> = [18],<position> = [16] equipmentF ailureEvent 35023 RX diversity parameter out of range 1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>. <cabinet>.<positi on> CntrlBrd <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, CONFIG, possible degraded operation. RX_FRU_ CONFIG diversity value <XX> invalid, possible degraded operation RX Mode RX Diversity Mismatch Alarm
Warning
EMPTY
EMPTY
R N
Possible Degraded Operation (Legacy)
35024
RX mode mismatch
CntrlBrd
Major
EMPTY
EMPTY
R N C
(Legacy)
35025
Frequency offset error
CntrlBrd
Frequency Offset Error.
Major
EMPTY
EMPTY
R Y
R = LDI (Quad/EBRC) or Reset (Legacy)
35026
_48 MHz Station Reference Failure
CntrlBrd
48 MHz Station Reference Failure
Major
EMPTY
EMPTY
R Y C
R = LDI (Quad); C = Enable Condition (Quad)
35027
_48 MHz Steering Line Failure
exBrc
48 MHz Steering Line Failure
Major
EMPTY
EMPTY
R Y C
R = LDI (EBRC/Quad); C = Enable Condition (EBRC/Quad)
35028
_16 MHz Steering Line Failure
1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in
exBrc
16 MHz Steering
Major
EMPTY
EMPTY
Site Service
R Y C
R = LDI (EBRC/Quad); C =
October 30, 2008
BRC-7

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r stance>.<type>. <cabinet>.<positi on> 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] Line Failure Call, if persiste nt
Enable Condition (EBRC/Quad)
35029
Invalid Critical Data
exBrc
Invalid Critical Data.
Critical
EMPTY
EMPTY
R Y C
R = LDI (EBRC/Quad); C = Enable Condition (EBRC/Quad)
35030
BR Watchdog Timer Expiration Reset
exBrc
BR Reset due to Watchdog Timer Expiration
Critical
EMPTY
EMPTY
None
C Y
(Quad/EBRC)
35031
Platform Internal Communcation Failure
exBrc
Platform Internal Communc ation Failure
Critical
EMPTY
EMPTY
R Y C
Not implemented
35032
Platform 3 Volt Failure
exBrc
Platform 3 Volt Failure
Critical
EMPTY
EMPTY
R Y C
R = LDI (EBRC); C = Enable Condition (EBRC)
35033
Overload condition on 5MHz/1PPS line
CntrlBrd
5 MHz/1PP S Overload Condition. Check 5MHz/1PP S terminatio n connection .
Major
EMPTY
EMPTY
R Y
EMPTY
BRC-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
35033
Overload condition on 5MHz/1PPS line
CntrlBrd
40000
Exciter Synthesizer Lock Failure
Excitr1
40001
Clip Detect Alarm
Excitr1
40001
Clip Detect Alarm
Excitr1
40002
Exciter EEPROM Checksum Failure
Excitr1
40003
Exciter 5 Volt Analog Alarm
Excitr1
<instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type>=[8,10],<cab inet>=[18],<position>=[1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [8,10],<cabinet> = [1-8],<position> = [1-6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5],<cabinet> = [18],<position> = [1-
5MHz/1PP S overload condition is recovered.
Clear
EMPTY
EMPTY
& Y / C N l e a r C N
EMPTY
Exciter Synthesiz er Lock Failure
Critical
EMPTY
EMPTY
R Y C
Clip Detect Alarm
Major
EMPTY
EMPTY
R N C
R = Roll Back Power (Legacy); C = Enable Condition
Clip Detect Alarm
Critical
EMPTY
EMPTY
R Y C
R = LDI (Quad/EBRC); C = Enable Condition
Exciter EEPROM Checksum Failure
Critical
EMPTY
EMPTY
R Y C
Not implemented
Exciter 5 Volt Analog Alarm
Critical
EMPTY
EMPTY
R Y C
R = LDI (Legacy/EBRC); C = Enable Condtidion (Legacy/EBRC)
October 30, 2008
BRC-9

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r equipmentF ailureEvent 40004 Exciter 5 Volt Digital Alarm 1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>. <cabinet>.<positi on> Excitr1 6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5, 10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5, Exciter 5 Volt Digital Alarm Critical EMPTY EMPTY Site Service Call, if persiste nt R Y C
R = LDI (EBRC); C = Enable Condtidion (EBRC)
40005
Exciter 10 Volt Alarm
Excitr1
Exciter 10 Volt Alarm
Critical
EMPTY
EMPTY
R Y C
40006
Exciter A Plus Voltage Alarm
Excitr1
Exciter A Plus Voltage Alarm
Critical
EMPTY
EMPTY
R Y C
R = LDI (Legacy); C = Enable Condtidion (Legacy)
40007
Exciter TXLIN Synthesizer Lock Alarm
Excitr1
Exciter TXLIN Synthesiz er Lock Alarm
Critical
EMPTY
EMPTY
R Y C
40008
Ext Wattmeter VSWR Failure Alarm
Excitr1
Ext Wattmeter VSWR Failure Alarm
Minor
EMPTY
EMPTY
R N C
EMPTY
40009
Invalid Exciter FRU revision number
Excitr1
WARNING : Invalid Exciter revision number
Critical
EMPTY
EMPTY
R Y
LDI
BRC-10
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r 10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5, 10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5, 10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5, 10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5, 10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5, 10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 61-
40010
Exciter local oscillator steering line failure
Excitr1
Exciter local oscillator steering line failure
Major
EMPTY
EMPTY
R Y C
R = LDI (Quad/EBRC); C = Enable Condition (Quad/EBRC)
40011
Exciter local offset oscillator lock failure
exBrc
Exciter local offset oscillator lock failure
Major
EMPTY
EMPTY
R Y C
40012
Exciter local offset oscillator steering line failure
exBrc
Exciter local offset oscillator steering line failure
Major
EMPTY
EMPTY
R Y C
40013
Exciter buffer amplifier failure
exBrc
Exciter buffer amplifier failure
Major
EMPTY
EMPTY
R Y C
40014
Exciter output amplifier failure
exBrc
Exciter output amplifier failure
Major
EMPTY
EMPTY
R Y C
40015
Exciter injection amplifier failure
1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>.
exBrc
Exciter injection amplifier
Major
EMPTY
EMPTY
Site Service Call, if
R Y C
October 30, 2008
BRC-11

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r <cabinet>.<positi on> 66, 71-76, 81-86], <type> = [5, 10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [5, 10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [10],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [11failure persiste nt
(Quad/EBRC)
40016
Exciter Injection Level Alarm
exBrc
Exciter Injection Level Alarm
Major
EMPTY
EMPTY
R Y C
40017
Exciter LO Feedthrough alarm
exBrc
Exciter LO Feedthrou gh alarm
Warning
EMPTY
EMPTY
None
R N C
(Quad)
45000
Power Supply 28 Volt Failure
exBrc
Major
EMPTY
EMPTY
R N C
45000
PwrSupp ly
Critical
EMPTY
EMPTY
R N C
45001
PwrSupp ly
Critical
EMPTY
EMPTY
R Y C
equipmentF
45002
Power Supply 5
1.3.6.1.4.1.161.3
PwrSupp
Power
Critical
EMPTY
EMPTY
Site
R Y
R = LDI
BRC-12
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
ailureEvent
Volt Failure
.3.2.4.2.8.1.5.<in stance>.<type>. <cabinet>.<positi on>
ly
45003
Power Supply DC Failure
PwrSupp ly
45003
PwrSupp ly
45005
Power Supply Fan Failure
PwrSupp ly
45006
Power Supply Heat Sink Failure
PwrSupp ly
45006
PwrSupp ly
16, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [1-
Supply 5 Volt Failure
Service Call, if persiste nt
& Y / C N l e a r C
(Legacy/EBRC); C = Enable Condition (Legacy/EBRC)
Major
EMPTY
EMPTY
R N C
Critical
EMPTY
EMPTY
R Y C
Power Supply Fan Failure
Warning
EMPTY
EMPTY
R N C
EMPTY
Major
EMPTY
EMPTY
R N C
Critical
EMPTY
EMPTY
R Y C
October 30, 2008
BRC-13

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r equipmentF ailureEvent 45007 Power Supply Battery Temperature Alarm 1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>. <cabinet>.<positi on> PwrSupp ly 6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [6],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = Power Supply Battery Temperatu re Alarm Warning EMPTY EMPTY Site Service Call, if persiste nt R N C
Not Implemented
45008
Power Supply Input Voltage Alarm
PwrSupp ly
Power Supply Input Voltage Alarm
Major
EMPTY
EMPTY
R Y C
R = Lock Condition (Legacy) or LDI (Quad/EBRC); C = Report Only (Legacy) or Enable Condition (Quad/EBRC)
45009
Power Supply Battery Voltage Failure
PwrSupp ly
Power Supply Battery Voltage Failure
Critical
EMPTY
EMPTY
R Y C
45010
Power Supply Battery Voltage Warning
PwrSupp ly
Power Supply Battery Voltage Warning
Warning
EMPTY
EMPTY
R N C
R = Roll Back Power (Legacy); C = Report Only (Legacy)
45011
PwrSupp ly
Major
EMPTY
EMPTY
R Y C
50000
PA Power Control Loop Error
PwrAmp
PA Power Control Loop Error
Critical
EMPTY
EMPTY
R Y C
R = LDI (Legacy); C = Enable Condition
BRC-14
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 61-
50001
PA Power Output Warning
PwrAmp
PA Power Output Warning
Warning
EMPTY
EMPTY
R N C
Not Implemented
50002
PA Power Output Alarm
PwrAmp
PA Power Output Alarm
Critical
EMPTY
EMPTY
R Y C
R = LDI
50003
PA High Temperature Warning
PwrAmp
PA High Temperatu re Warning
Warning
EMPTY
EMPTY
R N C
R = Roll back Power (Legacy) or Report Only; C = Report Only
50004
PA High Temperature Alarm
PwrAmp
PA High Temperatu re Alarm
Critical
EMPTY
EMPTY
R Y C
50005
PA High Reverse Power Warning
PwrAmp
PA High Reverse Power Warning
Warning
EMPTY
EMPTY
R N C
R = Roll back Power (Legacy) or Report Only; C = Report Only
50006
PA High Reverse Power Alarm
1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>.
PwrAmp
PA High Reverse Power
Critical
EMPTY
EMPTY
R Y C
LDI
October 30, 2008
BRC-15

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r <cabinet>.<positi on> 66, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [11Alarm persiste nt
50007
PA Fan Failure
PwrAmp
PA Fan Failure
Warning
EMPTY
EMPTY
R N C
EMPTY
50008
PA Power Rollback Alarm
PwrAmp
PA Power Rollback Alarm
Warning
EMPTY
EMPTY
R N C
(Legacy)
50009
PA EEPROM Checksum Failure
PwrAmp
PA EEPROM Checksum Failure
Warning
EMPTY
EMPTY
R N
Not Implemented
50010
PA Training Failure
PwrAmp
Training Failure
Warning
EMPTY
EMPTY
R N C
Not Implemented
50011
Invalid PA FRU revision number
PwrAmp
WARNING : Invalid Power Amplifier revision number
Critical
EMPTY
EMPTY
R Y
LDI
equipmentF
50012
PA Current
1.3.6.1.4.1.161.3
PwrAmp
PA
Critical
EMPTY
EMPTY
Site
R Y
R = LDI (Quad); C =
BRC-16
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
ailureEvent
Balance
.3.2.4.2.8.1.5.<in stance>.<type>. <cabinet>.<positi on>
50013
PA Communication Failure
PwrAmp
50014
PA High External Reverse Power Alarm
PwrAmp
50015
PA 28 Volt Low Alarm
PwrAmp
55000
Preamp Bias Alarm
Rcvr1
55001
Local Osc. #1 is not locked to 2.1 MHz ref
Rcvr1
16, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [7],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [24],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [1-
Current Balance
Service Call, if persiste nt
& Y / C N l e a r C
Enable Condition (Quad)
PA Communic ation Failure
Critical
EMPTY
EMPTY
R Y C
PA High External Reverse Power Alarm
Critical
EMPTY
EMPTY
R Y C
PA 28 Volt Low Alarm
Critical
EMPTY
EMPTY
R Y C
Preamp Bias Alarm
Major
EMPTY
EMPTY
R N C
R = Failed branch of RX FRU removed from service (Legacy); C = Branch returned to service (Legacy)
Local Oscillator #1 is not locked
Major
EMPTY
EMPTY
R N C
R = All branches of failed RX FRU removed from service; C = All branches returned to service
October 30, 2008
BRC-17

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r equipmentF ailureEvent 55002 _5 Volt Analog Alarm 1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>. <cabinet>.<positi on> Rcvr2 6] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [24],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [25 Volt Analog Alarm Major EMPTY EMPTY Site Service Call, if persiste nt R N C
R = Failed RX FRU removed from service; <cabinet> = FRU returned to service
55003
_5 Volt Digital Alarm
Rcvr3
5 Volt Digital Alarm
Major
EMPTY
EMPTY
R N C
R = Failed RX FRU removed from service; <cabinet> = FRU returned to service
55004
_10 Volt Analog Alarm
Rcvr1
10 Volt Analog Alarm
Major
EMPTY
EMPTY
R N C
R = Failed branch of RX FRU removed from service (Legacy/EBRC); C = Branch returned to service (Legacy/EBRC) R = All branches of failed RX FRU removed from service (Quad/EBRC); C = All branches returned to service (Quad/EBRC)
55005
Local Osc. #1 Steering Voltage Alarm
Rcvr2
Local Oscillator #1 Steering Line Voltage Alarm Local Oscillator #2 Steering Line Voltage Alarm Reference Level Alarm
Major
EMPTY
EMPTY
R N C
55006
Local Osc. #2 Steering Line Voltage alarm
Rcvr2
Major
EMPTY
EMPTY
R N C
R = All branches of failed RX FRU removed from service (Quad/EBRC); C = All branches returned to service (Quad/EBRC)
55007
Reference Level Alarm
Rcvr1
Critical
EMPTY
EMPTY
R Y C
BRC-18
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r 4],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [24],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [24],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [24],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [24],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [24],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 61-
55008
Receiver #1 EEPROM Checksum Failure
Rcvr2
Warning
EMPTY
EMPTY
R N
Not Implemented
55009
Rcvr3
Warning
EMPTY
EMPTY
R N
Not Implemented
55010
Rcvr1
Warning
EMPTY
EMPTY
R N
Not Implemented
55011
Injection Level Alarm
Rcvr2
Injection Level Alarm
Major
EMPTY
EMPTY
R N C
R = Failed branch of RX FRU removed from service (Legacy); C = Branch returned to service (Legacy)
55012
RX Delta value out of range
Rcvr3
WARNING : RX Delta Value out of range
Major
EMPTY
EMPTY
R N
(Legacy)
55013
Invalid RX FRU revision number
1.3.6.1.4.1.161.3 .3.2.4.2.8.1.5.<in stance>.<type>.
Rcvr1
WARNING : Invalid Receiver
Warning
EMPTY
EMPTY
R N
EMPTY
October 30, 2008
BRC-19

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r <cabinet>.<positi on> 66, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [9],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] revision number persiste nt
55014
RX FRU revision number conflict
Rcvr2
55015
Receiver Antenna Branch Imbalance
Rcvr1
RX rev number conflict: <RXX.XX> <RXX.XX> <RXX.XX> , possible degraded operation WARNING : Receiver Antenna Branch Imbalance Detected
Major
EMPTY
EMPTY
R N
Possible degraded operation (Legacy)
Major
EMPTY
EMPTY
TBD
R N
EMPTY
55016
Injection Level Alarm Path1
general
Receiver <X> Path 1 Injection Level Alarm
Major
EMPTY
EMPTY
R N
R = Failed branch of RX FRU removed from service (Quad/EBRC); C = Branch returned to service (Quad/EBRC)
55017
Rcvr2
Major
EMPTY
EMPTY
R N
55018
Rcvr2
Major
EMPTY
EMPTY
R N
BRC-20
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t
O u t a g e
Comments & Notes
55019
Preamp Bias Alarm Path1
Rcvr2
55020
Rcvr1
55021
Rcvr2
55022
Multicoupler Alarm Path 1
Rcvr2
55023
Rcvr1
55024
Rcvr3
<instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11], <cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [18],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [2-4, 11],<cabinet> = [1-
Receiver <X> Path 1 Preamp Bias Alarm
Major
EMPTY
EMPTY
Major
EMPTY
EMPTY
R N C
Major
EMPTY
EMPTY
R N C
Receiver <X> Path 1 Multicoupl er Alarm
Major
EMPTY
EMPTY
R N C
R = Coupled branches from each RX FRU removed from service (Quad); C = Branches returned to service (Quad) R = Coupled branches from each RX FRU removed from service (Quad); C = Branches returned to service (Quad) R = Coupled branches from each RX FRU removed from service (Quad); C = Branches returned to service
Major
EMPTY
EMPTY
R N C
Major
EMPTY
EMPTY
R N C
October 30, 2008
BRC-21

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r 8],<position> = [16] <instance> = [1116, 21-26, 31-36, 41-46, 51-56, 6166, 71-76, 81-86], <type> = [24],<cabinet> = [18],<position> = [16]
(Quad) Receiver Synthesiz er/Inj. Amp 10V Alarm Critical EMPTY EMPTY Site Service Call, if persiste nt R Y C U R = Disable Condition (EBRC); C = Enable Condition (EBRC)
55025
Synthesizer/Inj. Amp 10V Alarm
Rcvr1
BRC-22
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Labe l)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
BR State Change BR State Change BR State Change BR State Change BR State Change BR State Change BR State Change
1 BR INITIALIZED 2 BR ENABLED 3 BR UNLOCKED 4 BR KEYED
5 BR LOCKED BY ACG 5 BR LOCKED BY ACG 6 BR CHANNELS NOT RECEIVED 7 BR LOCK CONDITION 7 BR LOCK CONDITION 8 BR ACG LAPD LINK RELEASED 8 BR ACG LAPD LINK RELEASED 8 BR ACG
1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3.
BR
BR
BR
BR
BR
BR
BR
<instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] 11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86
I-I-I
L-D-Idl
EMPTY
EMPTY
EMPTY
S t a t u s N U
BR reset, is initialized, and is ready for Critical Data Download Critical Data received, LAPD up, all Disable Conditions Clear Unlock received from ACG
L-D-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
L-E-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
U-E-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
BR is keyed and ready to process calls Lock received from ACG
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
Lock received from ACG
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
Channel setups were not received from the ACG
BR State Change BR State Change BR State Change
BR
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
BR failure condition resulting in Lock action occurred BR failure condition resulting in Lock action occurred BR failure condition resulting in reset action occurred
BR
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
BR
U-E-A
I-I-I
EMPTY
32001
BR State Change
BR
11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86
U-E-Idl
I-I-I
EMPTY
32001
BR State
BR
11-16, 21-26, 31-36, 41-46,
L-E-Idl
I-I-I
EMPTY
32001
BR detected LAPD link loss between BR and ACG BR detected LAPD link loss between BR and ACG BR detected
Y U
Y U
BR failure condition resulting in reset action occurred
Y U
BR failure condition resulting in
October 30, 2008
BRC-23

State Changes
R e a s o n C o d e
Release SR17.0
From State To State Related State Changes
Related Alarms Event Description O u t a g e ( Y / N ) C h a n g e S t a t u s reset action occurred
OMC Text
MOI Info (Id)
MOI Info (Labe l)
Inst
Comments & Notes
Change
LAPD LINK RELEASED 8 BR ACG LAPD LINK RELEASED 9 BR DISABLE CONDITION
2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 BR
51-56, 61-66, 71-76, 81-86
BR State Change
11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86
L-D-Idl
I-I-I
EMPTY
32001
BR State Change
BR
<instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86]
U-E-A
U-D-Idl
EMPTY
EMPTY
LAPD link loss between BR and ACG BR detected LAPD link loss between BR and ACG EMPTY
Y U
BR failure condition resulting in reset action occurred
Y U
BR State Change
9 BR DISABLE CONDITION
1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535
BR
<instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86]
U-E-Idl
U-D-Idl
EMPTY
EMPTY
EMPTY
Y U
BR State Change BR State Change BR State Change BR State Change BR State Change BR State Change BR State Change BR State Change
9 BR DISABLE CONDITION 9 BR DISABLE CONDITION 9 BR DISABLE CONDITION 9 BR DISABLE CONDITION 9 BR DISABLE CONDITION 1 BR BAD 1 CHANNEL SPLIT 1 BR BAD 2 CHANNEL JOIN 1 BR FREE 3 RUN TIMER EXPIRED NO SATELLITES 3 BR PCCH 1 REJECT PCCH EXISTS 3 BR PCCH
1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3.
BR
BR
BR
BR
BR
BR
BR
BR
<instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26,
L-E-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
Y U
U-D-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
Y U
U-E-A
L-D-Idl
EMPTY
EMPTY
EMPTY
Y U
U-E-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
Y U
L-E-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
Y U
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
BR failure condition resulting in Disable action occurred (Immediately followed by an UD-Idle -> L-D-Idle State Change Trap) (Legacy) BR failure condition resulting in Disable action occurred (Immediately followed by an UD-Idle -> L-D-Idle State Change Trap) (Legacy) BR failure condition resulting in Disable action occurred (Legacy) BR failure condition resulting in Disable action occurred (Legacy) BR failure condition resulting in Disable action occurred (Quad/EBRC) BR failure condition resulting in Disable action occurred (Quad/EBRC) BR failure condition resulting in Disable action occurred (Quad/EBRC) ACG attempted to split a BR channel that is not UNASSIGNED ACG attempted to join a BR channel that is not UNASSIGNED BR free-run timer has expired. TFR needs to be recalibrated
BR State Change
BR
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
The host received a PCCH setup when a PCCH exists
BR State
BR
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
The host received a PCCH
BRC-24
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
MOI Info (Labe l) Inst
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Change
BR State Change
BR State Change
BR State Change
BR State Change
BR State Change
BR State Change
BR State Change BR State Change BR State Change
2 REJECT SCCH EXISTS 3 BR SCCH 3 REJECT PCCH EXISTS 3 BR SCCH 4 REJECT SCCH EXISTS 3 BR BAD 5 CHAN SETUP PCH CANNOT BE REASSIGNE D 3 BR FIRST 6 TIME SLOT NOT SERVICED 3 BR 7 CRITICAL DATA IN UNLOCKED STATE 3 BR 7 CRITICAL DATA IN UNLOCKED STATE 4 BR BAD 4 PSCCH SETUP 4 BR BAD 4 PSCCH SETUP 4 BR 5 UNKNOWN BACKHAUL MODE
2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 BR
31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] U-E-A L-E-Idl EMPTY EMPTY EMPTY Y U
setup when a SCCH exists
The host received a SCCH setup when a PCCH exists
BR
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
The host received a SCCH setup when a SCCH exists
BR
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
The host received a channel setup request which attempted to illegally change an existing PCH to a non-UCH type
1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535
BR
<instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86]
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
The host timed out for an indication signifying the start of the first time slot The host received critical data while it is in unlocked state
BR
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535
BR
<instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86]
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
The host received critical data while it is in unlocked state
1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535 1.3.6.1.4.1.161.3.3. 2.4.2.8.1.5.<instanc e>.1000.1.65535
BR
BR
BR
<instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86] <instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86]
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
Y U
The host received an invalid PCCH or SCCH setup request message from ACG The host received an invalid PCCH or SCCH setup request message from ACG The host did not receive a valid ACG Backhaul Indication message from ACG
October 30, 2008
BRC-25
Release SR17.0
__________________________________ Events
MOI Info (Labe l) Inst From State To State Related State Changes
Event Description
O u t a g e ( Y / N )
Comments & Notes
Hardware Config Trap
EMPT Y
1.3.6.1.4.1. 161.3.3.2.4. 2.8.1.5.<ins tance>.<typ e>.<cabinet >.<position >
Gen
<instance> = [11-16, 21-26, 31-36, 41-46, 51-56, 61-66, 71-76, 81-86], <type>=[9],<c abinet>=[18],<position>= [1-6]
U-E-Idl
U-E-A
EMPTY
<BR_TYPE>, <BR_REVISION>, <EX_REVISION>, <PA_REVISION>, <RX1_REVISION>, <RX2_REVISION>, <RX3_REVISION>, <RX4_REVISION>, <BR_BAND> where: <BR_TYPE> = Legacy BR(1), Quad-BR(3), Gen2 BR (4), Quad2-BR(5); <BR_REVISION> = The format is ASCII (numbers and hexadecimal) and the range of legal values is: LAA.BB.CC (9 characters); <EX_REVISION> = The format is ASCII (numbers and hexadecimal) and the range of legal values is: LAA.BB.CC (9 characters); <PA_REVISION> = The format is ASCII (numbers and hexadecimal) and the range of legal values is: LAA.BB.CC (9 characters); <RX1_REVISION> = The format is ASCII (numbers and hexadecimal) and the range of legal values is: LAA.BB.CC.DD (12 characters); <RX2_REVISION> = The format is ASCII (numbers and hexadecimal) and the range of legal values is: LAA.BB.CC.DD (12 characters); <RX3_REVISION> = The format is ASCII (numbers and hexadecimal) and the range of legal values is: LAA.BB.CC.DD (12 characters); <RX4_REVISION> = The format is ASCII (numbers and hexadecimal) and the range of legal values is: LAA.BB.CC.DD (12 characters) ; <BR_BAND> = 800 Single Band(2), 900 Single Band(4), 1.5G Single Band (5), 800 Dual Band(6), 900 Dual Band(7), Dual Band RFDS(8); WHERE: L : D = Development : B = Beta version : R = Release version AA : 00 - FF = Major version number BB : 00 - FF = Minor version number CC : 00 - FF = Maintenance version number " DD : 00 - FF = ( 01 - Legacy BR with 3 carrier paths, 02 - Legacy BR with 1 carrier path, 03 - Quad/Quad2-BR with 4 carriers, 04 - Quad/Quad2-BR with 2 carriers, 05 - Quad/Quad2-BR with 1 carrier)
BRC-26
October 30, 2008
Release SR17.0
_________________________________ Alarms
Alarm Type
A l a r m C o d e
BSC
Remedy
R e p o r t & O u t a g e Y C / l N e a r R N C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Severity
Related Alarms
Comments & Notes
qualityOfSer viceFailureE vent communicat ionFailureE vent communicat ionFailureE vent processingF ailureEvent
Threshold Exceeded: Paging Request From MSC Protocol Error Threshold Exceeded: Routing Failure, Syntax Error Detected Threshold Exceeded: Routing Failure, Reason Unknown Excessive GPROC CPU utilization
Device ID: 0
BSC
EMPTY
Warning
EMPTY
EMPTY
No action required
Device ID: 0
BSC
EMPTY
Warning
EMPTY
EMPTY
No action required
R N
Device ID: 0
BSC
EMPTY
Warning
EMPTY
EMPTY
No action required
R N
2 7
Cage: 0; Slot: 20
BSP
2 7
Excessive GPROC CPU utilization
Cage: 0; Slot: 20
BSP
GPROCid= N1, CPUid=N2, BSP, #XBLs=N5, util=N7%, threshold= N8%, margin=N9 % Scheduled TDM_conn _test skipped, high CPU% (A%), thresh=B%
Warning
MTL: 3; RslSap: 13; SITE: 0, 1, 4; XBL: 0, 1, 2, 3, 5, 6, 7, 10
XBL: BU/D-U(31, 32, 37), BU/E-U(36), B-U/E-L(0)
Overloaded system, please review configuration.
R N C
U PMALARM. Collect the BSP MMI TTY outputs and send to BSC group for further analysis. U PMALARM. This statistic is pegged when a syntax error is detected in the routing message. U PMALARM. This statistic is pegged whenever there is a routing failure from the MSC. U N1 = 0, 1, 2, ... N2 = 0113, 0115, 0215, ... N3 = 0, 1, 2, ... N4 = 0, 1, 2, ... N5 = 0, 1, 2, ... N6 = 0, 1, 2, ... N7 = 0, 10, 11, 23, ... N8 = 0, 10, 11, 23, ... N9 = 0, 10, 11, 23, ... N10 = 0, 1, 2,
Warning
EMPTY
EMPTY
This message indicates that this audit was skipped due to excessive CPU utilization (due to call traffic) in the system. If this message is received during system initialization, there is no cause for concern. If however this message is received during regular operation or everyday, the scheduled time of the specified reportedly skipped audit (e.g. TDM conn_test) should be reviewed and altered to a low
R N
U 0 <= A <= 100 0 <= B <= 100
October 30, 2008
BSC-1

Alarm Type
A l a r m C o d e
Release SR17.0
Severity Related Alarms Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r usage time as appropriate. Note that as of SR9.0, the BSC time changed to Greenwich Mean Time (GMT), so a low usage time of 3am Central US Time may be a GMT of 9am, so the BSC audit time must be specified as 9am to run at a local time of 3am (if the time difference is -6 hours). This message indicates that this audit was skipped due to excessive CPU utilization (due to call traffic) in the system. This is Device-Triggered, meaning that a cage was just brought in service. If the system is call processing, then there is no cause for concern. If however the system not call processing, the configuration should be reviewed to determine why the CPU utilization is excessive, causing the TDM conn_test to be skipped. Check the Local KSWX on the A side
Comments & Notes
2 7
Cage: 0; Slot: 20
BSP
DeviceTriggered TDM_conn _test skipped, high CPU% (A%), thresh=B%
Warning
EMPTY
EMPTY
R N
U 0 <= A <= 100 0 <= B <= 100
2 8
TDM Clock A Failure
Cage: 0; Slot: 20
BSP
EMPTY
Major
CBUS: 0, 1, 2, 3
GCLK: BU/D-U(25)
R N
2 9
TDM Clock B Failure
Cage: 0; Slot: 20
BSP
EMPTY
Major
CBUS: 0, 1, 2, 3
GCLK: BU/D-U(25)
Check the Local KSWX on the B side
R N
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
processingF
General Alarm
Cage: 0;
BSP
LAN: Dropping frame, code xfer in progress LAN: dropping frame, max length exceeded LAN: dropping frame, no Q blocks available LAN FLOW
Critical
GPROC/EG PROC: 23, 231, 254
GPROC/EG PROC: BU/D-U(23, 24) EMPTY
Critical
EMPTY
Check the state of GPROCs/EGPs, find the GPROC/EGP that has gone down, and make sure the GPROC/EGP is stable. No action required
R N
U If many boards report the same alarm, reseat or replace the Local KSWX cards. U If many boards report the same alarm, reseat or replace the Local KSWX cards. U The related alarms and state changes are from non-master GPROCs
R N
U Indication that a frame that was too big was received on the LAN.
Critical
GPROC/EG PROC: 23, 231, 254
GPROC/EG PROC: BU/D-U(23, 24) GPROC/EG
If this problem persists, check LAN connectivity.
R N
U Indication that no buffers are available to send data over the LAN, possible LAN issue. U Indication that no buffers
Critical
GPROC/EG
If this problem persists, check
R N
BSC-2
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

MOI Info (Label) I n s t
Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Slot: 20 CONTROL: locking all LAN Links LAN FLOW CONTROL: Unlocking all LAN Links BAD FRAME RECEIVED exceeding Q_BLOCK_ SIZE KSW Cage X, Slot Y, msg Z times, for MM:SS XCDR Cage X, Slot Y, msg Z times, for MM:SS GCLK Cage X, Slot Y, msg Z times, for MM:SS MSI Cage X, Slot Y, msg Z times, for MM:SS SM Error: Missing RCI Xh Yh Zh Zh Unknown Intrpt 0x%x rcvd, channel %d, sap %d, restart T7115/T713 0 PROC: 23, 231, 254 Critical EMPTY PROC: BU/D-U(23, 24) EMPTY LAN connectivity.
Comments & Notes
ailureEvent
3 2 2 3 2 General Alarm
Cage: 0; Slot: 20
BSP
R N
are available to send data over the LAN, possible LAN issue. U Indication that buffers are now available to send data over the LAN, possible LAN issue. U Indication that a frame that was too big was received on the LAN.
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
Critical
EMPTY
EMPTY
No action required
R N
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
Critical
KSW:224
EMPTY
If this problem persists, then replace the card.
R N
U X=0, 1, 2, 5; Y=1/27; Z=10, 1000; MM=00, 01, , 1000; SS=00, 01, , 59 U X=0, 1, 2, 5; Y=6, 7, , 24; Z=10, 1000; MM=00, 01, , 1000; SS=00, 01, , 59 U X=0, 1, 2, 5; Y=3/5; Z=10, 1000; MM=00, 01, ,1000; SS=00, 01, , 59 U X=0, 1, 2, 5; Y=6, 7, , 17; Z=10, 1000; MM=00, 01, , 1000; SS=00, 01, , 59 U X=0, 1, EF; Y=0, 1, 0ff; Z=0, 1, FF
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
Critical
XCDR:19
EMPTY
R N
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
Critical
GCLK: 2,3,4,5,6,7, 8,9
EMPTY
R N
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
Critical
MSI: 0, 1, 2, 4, 5, 6, 8, 10, 12, 13, 14, 16 EMPTY
EMPTY
R N
2 3 2 2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
Critical
EMPTY
EMPTY
R N
General Alarm
Cage: 0; Slot: 20
BSP
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 11
RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: B-
Possible T1 / DACS problems. Check BSC to EBTS or BSC to XCDR (for XBL) physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this link
R N
U In the case where an Unknown Interrupt has been received and the HDLC Chip will be reset, this alarm will be displayed
October 30, 2008
BSC-3

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r U/D-U(31, 32, 37) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) EMPTY
Comments & Notes
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
Unknown Intrpt 0x%x rcvd, channel %d, sap %d
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 13
R N
U In the case where an Unknown Interrupt has been received and the "lap_isr_fix_flag" is set to "off", the HDLC Chip reset has been turned off, this alarm will be displayed
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
T7130 LAPD controller FATAL ERROR error Code=%d. Restart T7115/T713 0 T7130 Halted, must reset T7115/T713 0 to recover, channel%d
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 14
R N
U In the case where a Fatal error occurred and the HDLC Chip will be reset this alarm will be displayed
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 16
R N
U In the case where T7130 is halted, condition detected by one way XBL, this alarm will be displayed
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
T7130 Halted, must reset GPROC to recover, channel %d
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 17
Possible GPROC issues or possible T1 / DACS problems. Check BSC to EBTS or BSC to XCDR (for XBL) physical connection as well as devices (GPROC/EGP, MSI, etc) controlling this link. If the condition persists, replace the GPROC.
R N
U In the case where the "lap_isr_fix_flag" is set to "off" or if the condition happened too many times, this alarm will be displayed
processingF
General Alarm
Cage: 0;
BSP
Possible
Warning
EMPTY
If the alarm does not clear, run
R N
U Indicates that a register on
BSC-4
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Slot: 20 register corruption on BSP the health check
Comments & Notes
ailureEvent
3 2
2 3 2 2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
General Alarm
Cage: 0; Slot: 20
BSP
2 3 2
General Alarm
Cage: 0; Slot: 20
BSP
2 5 4 0
Device Failed
Cage: 0; Slot: 20
BSP
Register corruption cleared on BSP Blk cage recovery proc restarts T7115/T713 0 on MCAP GPROC id1 id2 id3 Too many blocked cage conditions detected. Please check hardware EMPTY
Clear
EMPTY
EMPTY
No action required
C N
the BSP may have a corrupt value. We do not expect this to affect call processing, but it is a good idea to run the health check test to verify that everything works fine. U The problem is self correcting. If it corrects, the clear will be raised U This warning will be displayed when the blocked cage recovery procedure performs HDLC reset of MCAP GPROC in cage that is going to be blocked U This alarm will be displayed when the blocked cage recovery procedure starts more times than allowed within the specified time period
Warning
EMPTY
EMPTY
No action required
R N
Major
CAGE: 18
EMPTY
Check KSW, KSWX boards for malfunctions. Check KSWX fiber connections for breakages. Perform BLOCKED CAGE troubleshooting.
R N
Critical
EMPTY
EMPTY
No action required
R Y
Expansion KSWX Communication Failure Expansion KSWX Communication Failure Expansion KSWX Communication Failure Expansion KSWX Communication Failure
Device ID: 0-5
CAGE
14
Device ID: 0-5
CAGE
14
Device ID: 0-5
CAGE
14
Device ID: 0-5
CAGE
14
Check KSWX in Cage xx, Slot 7 Check KSWX in Cage xx, Slot 8 Check KSWX in Cage xx, Slot 9 Check KSWX in Cage xx, Slot 21
Major
EMPTY
EMPTY
Reinsert or replace KSWX.
R N C
U This alarm might be seen if the BSP is reset. If the alarm occurs continuously, replace the BSP. U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
October 30, 2008
BSC-5

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Expansion KSWX Communication Failure Expansion KSWX Communication Failure Local KSWX Communication Failure Local KSWX Communication Failure Remote KSWX Communication Failure Remote KSWX Communication Failure Remote KSWX Communication Failure Remote KSWX Communication Failure Remote KSWX Communication Failure Remote KSWX Communication Failure Remote KSWX Communication Failure Remote KSWX Communication Failure
Device ID: 0-5
CAGE
14
Device ID: 0-5
CAGE
14
Device ID: 0-5
CAGE
16
Device ID: 0-5
CAGE
16
Device ID: 0-5
CAGE
12
Device ID: 0-5
CAGE
12
1 0
Device ID: 0-5
CAGE
12
1 1
Device ID: 0-5
CAGE
12
1 2
Device ID: 0-5
CAGE
12
1 3
Device ID: 0-5
CAGE
12
1 4
Device ID: 0-5
CAGE
12
1 5
Device ID: 0-5
CAGE
12
Check KSWX in Cage xx, Slot 22 Check KSWX in Cage xx, Slot 23 Check KSWX in Cage xx, Slot 0 Check KSWX in Cage xx, Slot 1 Check KSWX in Cage xx, Slot 2 Check KSWX in Cage xx, Slot 3 Check KSWX in Cage xx, Slot 4 Check KSWX in Cage xx, Slot 5 Check KSWX in Cage xx, Slot 6 Check KSWX in Cage xx, Slot 24 Check KSWX in Cage xx, Slot 25 Check KSWX in Cage xx,
Major
EMPTY
EMPTY
Y C / l N e a r R N C
Comments & Notes
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
Major
EMPTY
EMPTY
R N C
U EMPTY
BSC-6
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Remote KSWX Communication Failure Remote KSWX Communication Failure Cage Blocked Device ID: 0-5 CAGE 12 Slot 26 Check KSWX in Cage xx, Slot 27 Check KSWX in Cage xx, Slot 28 No Active TBUS in the cage Major EMPTY EMPTY Reinsert or replace KSWX. R N C
Comments & Notes
1 6
U EMPTY
1 7
Device ID: 0-5
CAGE
12
Major
EMPTY
EMPTY
R N C
U EMPTY
1 8
Device ID: 0-5
CAGE
16
Major
CAGE: 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17; KSW: 8, 230, 231, 254; TBUS: 0, 1, 226, 254;
Over 50% of boards Detected Clock Failure
Cage: 0-5; Side: 0/1
CBUS
11 2
Local KSWX Clock Fiber Failure
CBUS
11 2
Local KSWX Communication Failure
CBUS
11 2
Check KSWX Cage xx, Slot yy and fiber connection Check fiber connection of KSWX Cage xx, Slot yy from CLKX Cage 0, slot zz Bad/Missin g KSWX card, Cage
Critical
EMPTY
KSW: BU/D-U(22, 24, 25), BU/E-L(0), BU/E-U(28), E-U/B-U(0), E-L/B-U(0), E-U/DU(22, 24, 25), E-U/EL(0); TBUS: D-U/B-U(0), E-U/B-U(0), B-U/DU(22, 24, 29), E-U/DU(22, 24, 29), B-U/EL(0), E-L/EU(0), E-L/BU(0), BU/E-U(28) EMPTY
Do disp_tdm_op to find out the impaired TDM highway and TBUS and take proper action to correct the problem(s).
R N C
U EMPTY
Replace local KSWX.
R N C
U EMPTY
Minor
EMPTY
EMPTY
Check fiber connection
R N C
U EMPTY
Minor
EMPTY
EMPTY
Check KSWX card
R N C
U EMPTY
October 30, 2008
BSC-7

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r CLKX Communication Failure Cage: 0-5; Side: 0/1 CBUS 11 2 11 2 11 2 xx, Slot yy Bad/Missin g CLKX card, Cage xx Slot yy Neither CBUS is busy unlocked Probable GCLK Failure (slot x) detected by Clock Bus Critical EMPTY EMPTY Check CLKX card R N C
Comments & Notes
U EMPTY
No master CBUS in Cage 0
CBUS
Warning
CBUS: 0,1,2,3
CBUS: BU/D-U(61)
Check local KSWX connection in master cage.
R N C
U The last in service CBUS in master cage is disabled
Probable GCLK Failure
CBUS
Minor
GCLK: 4,5,6,7,26
GCLK: BU/D-U(25), E-U/DU(25)
Clock Bus State Mismatch
CBUS
11 2
This BUSY CBUS not associated with BUSY GCLK
Warning
CBUS: 0,1,2,3,224; GCLK: 5,6,7,11,12, 14,26,224
2 2 4
Safe Test Fail
CBUS
11 2
2 2 4 2 2 4
Safe Test Fail
CBUS
11 2 11 2
Safe Test Fail
CBUS
2 2 4 6
Safe Test Fail
CBUS
11 2 12 4
Threshold Exceeded: Cipher Mode Cmd from MSC Failed
Device ID: 1-240
CELL
KSWX Cage xx Slot yy reports clock alarm Bad/Missin g KSWX card, Cage xx, Slot yy 50% of the full size boards report clock failure Bad/Missin g CLKX card, Cage xx Slot yy EMPTY
Minor
CBUS: 1
CBUS: BU/D-U(61), E-U/DU(61); GCLK: BU/D-U(25), B-U/EU(48) CBUS: BU/D-U(61), E-U/DU(61) CBUS: BU/D-U(61), E-U/DU(61) CBUS: BU/D-U(61), E-U/DU(61) CBUS: BU/D-U(61), E-U/DU(61) EMPTY
On a Basic BSC system, there is unfortunately no remedy; a system reset may be imminent. Immediately upon reset (if so), replace the GCLK card. On an enhanced system with only one GCLK card equipped, the situation is unfortunately the same, system reset Check the fiber connections between the KSWX cards and the CLKX cards. The A-side and the B-side KSWX cards should be fed from their respective CLKX cards corresponding to their respective GCLK cards. Check local KSWX clock fiber connection.
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
Minor
CBUS: 2
Bad or Missing local KSWX
R N
U EMPTY
Minor
CBUS: 0
Check local KSWX connection.
R N
U EMPTY
Minor
CBUS: 3
Check CLKX card
R N
U EMPTY
Minor
EMPTY
No action required
R N
U PMALARM. The actual format for MOI Info (label) will be 000 00 0000 0XXX
BSC-8
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r 0
Comments & Notes
Threshold Exceeded: Intra Cell Handover Failed & Recovered to Org Channel Threshold Exceeded: Intra Cell Handover Failed & Mobile Lost
Device ID: 1-240
CELL
12 4 0 12 4 0 12 4 0 12 4 0 12 4 0 12 4 0 12 4 0 11 8
EMPTY
Warning
EMPTY
EMPTY
No action required
R N
1 0
Device ID: 1-240
CELL
EMPTY
Minor
EMPTY
EMPTY
No action required
R N
1 1
Threshold Exceeded: Intra BSS HO Primary Target Cell Blocked
Device ID: 1-240
CELL
EMPTY
Minor
EMPTY
EMPTY
No action required
R N
1 3
Threshold Exceeded: Intra BSS HO Failed and Recovered to Org Channel Threshold Exceeded: Intra BSS HO Failed and Mobile Lost
Device ID: 1-240
CELL
EMPTY
Warning
EMPTY
EMPTY
No action required
R N
1 4
Device ID: 1-240
CELL
EMPTY
Minor
EMPTY
EMPTY
No action required
R N
1 5
Threshold Exceeded: Inter BSS HO, MS HO Failed Message Received Threshold Exceeded: HO Failure to the MSC due to all Possible Errors Except No Channels Bad ID
Device ID: 1-240
CELL
EMPTY
Warning
EMPTY
EMPTY
No action required
R N
1 8
Device ID: 1-240
CELL
EMPTY
Warning
EMPTY
EMPTY
No action required
R N
Cage 0-5; Device ID: 0-5
DPSM
Cage: ìd', `dpsm location'
Warning
EMPTY
EMPTY
Check if compatible DPSM is installed in BSC card cage.
R N C
No Board
Cage 0-5; Device ID: 0-5
DPSM
11 8
Cage: ìd', `dpsm location'
Critical
EMPTY
EMPTY
No DPSM in slot. Insert DPSM if needed.
R N C
where "XXX" represents the significant digits. PMALARM. The actual format for MOI Info (label) will be 000 00 0000 0XXX where "XXX" represents the significant digits. PMALARM. The actual format for MOI Info (label) will be 000 00 0000 0XXX where "XXX" represents the significant digits. PMALARM. The actual format for MOI Info (label) will be 000 00 0000 0XXX where "XXX" represents the significant digits. PMALARM. The actual format for MOI Info (label) will be 000 00 0000 0XXX where "XXX" represents the significant digits. PMALARM. The actual format for MOI Info (label) will be 000 00 0000 0XXX where "XXX" represents the significant digits. PMALARM. The actual format for MOI Info (label) will be 000 00 0000 0XXX where "XXX" represents the significant digits. PMALARM. The actual format for MOI Info (label) will be 000 00 0000 0XXX where "XXX" represents the significant digits. Note: 'dpsm location' can be any one of the following: Right Power Supply, Center Power Supply, Left Power Supply. DPSM ID maps to its cage number The last DPSM in nonmaster cage goes out of service. DPSM ID maps to
October 30, 2008
BSC-9

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Bad Status Cage 0-5; Device ID: 0-5 Cage 0-5; Device ID: 0-5 DPSM 11 8 11 8 Cage: ìd', `dpsm location' Cage: ìd', `dpsm location' Warning EMPTY EMPTY Bad data returned from DPSM. Replace DPSM. Check if Input Failure also occurs. If so, see Remedy for Input Failure. If not, possible causes are: improperly inserted DPSM, DPSM failure, over-temperature condition reached. Check corresponding BSC cabinet circuit breaker, check input DC power to BSC cabinet, if previous are met, replace DPSM. Check for possible BSC card failures. Switch to the standby GCLK and replace this GCLK. A circuitry failure has been detected. R N C R N C
Comments & Notes
equipmentF ailureEvent equipmentF ailureEvent
its cage number U DPSM ID maps to its cage number U DPSM ID maps to its cage number
DPSM Output Failure
DPSM
Critical
DPSM: 4
EMPTY
DPSM Input Failure
Cage 0-5; Device ID: 0-5 Cage 0-5; Device ID: 0-5 Cage: 0; Slot: 3/5
DPSM
11 8 11 8 12
Cage: ìd', `dpsm location' Cage: ìd', `dpsm location' GCLK IRR Value is 0xXX, ISR Value is 0xYY, SHR Value is 0xZZ (r#) GCLK IRR Value is 0xXX, ISR Value is 0xYY, SHR Value is 0xZZ (r#) GCLK IRR Value is 0xXX, ISR Value is 0xYY, SHR Value is 0xZZ (r#) GCLK IRR Value is 0xXX, ISR Value is 0xYY, SHR Value is 0xZZ (r#) GCLK IRR Value is
Critical
EMPTY
EMPTY
R N C
U DPSM ID maps to its cage number
DPSM Over Temperature Warning Reference Distribution Module Failure
DPSM
Critical
PAB: 3
EMPTY
R N C R N C
U DPSM ID maps to its cage number U Note: # can be 0-50
GCLK
Critical
GCLK: 5, 6, 7
EMPTY
Mate GCLK Failure
Cage: 0; Slot: 3/5
GCLK
12
Critical
EMPTY
EMPTY
A mate GCLK failure has been detected. Ensure that mate GCLK is standby or DISABLED and replace it.
R N C
U Note: # can be 0-50
GCLK 2.048 MHz Reference B Fail
Cage: 0; Slot: 3/5
GCLK
12
Major
MSI: 2, 6, 8, 10, 14, 16, 26, 28, 32, 34, 231, 254
MSI: BU/E-L(0); T1/E1: BU/D-U(24, 30), B-U/EL(0) MSI: BU/E-L(0); T1/E1: BU/D-U(24, 30), B-U/EL(0) MSI: BU/E-L(0);
Check GCLK card and Reference Span.
R N
GCLK 2.048 MHz Reference A Fail
Cage: 0; Slot: 3/5
GCLK
12
Major
MSI: 2, 6, 8, 10, 14, 16, 26, 28, 32, 34, 231, 254
R N
Phase Lock Loss
Cage: 0; Slot: 3/5
GCLK
12
Major
GCLK: 2, 3; MSI: 2, 6, 8,
R N C
U Immediately after site initialization and recovery
BSC-10
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r 0xXX, ISR Value is 0xYY, SHR Value is 0xZZ ( r#) 10, 14, 16, 26, 28, 32, 34, 231, 254 T1/E1: BU/D-U(24, 30), B-U/EL(0)
Comments & Notes
GCLK 125 kHz Reference Overflow
Cage: 0; Slot: 3/5
GCLK
12
GCLK 60kHz Reference Overflow
Cage: 0; Slot: 3/5
GCLK
12
GCLK 6.12 MHz Reference Overflow
Cage: 0; Slot: 3/5
GCLK
12
GCLK Frequency Difference
Cage: 0; Slot: 3/5
GCLK
12
GCLK Reset
Cage: 0; Slot: 3/5
GCLK
12
GCLK IRR Value is 0xXX, ISR Value is 0xYY, SHR Value is 0xZZ (r#) GCLK IRR Value is 0xXX, ISR Value is 0xYY, SHR Value is 0xZZ (r#) GCLK IRR Value is 0xXX, ISR Value is 0xYY, SHR Value is 0xZZ (r#) GCLK IRR Value is 0xXX, ISR Value is 0xYY, SHR Value is 0xZZ (r#) GCLK IRR Value is 0xXX, ISR Value is 0xYY, SHR Value is
Major
GCLK: 2, 3, 26; MSI: 2, 6, 8, 10, 14, 16, 26, 28, 32, 34, 231, 254 GCLK: 2, 3, 26; MSI: 2, 6, 8, 10, 14, 16, 26, 28, 32, 34, 231, 254 GCLK: 2, 3, 26; MSI: 2, 6, 8, 10, 14, 16, 26, 28, 32, 34, 231, 254 GCLK: 2, 3, 4, 26
MSI: BU/E-L(0); T1/E1: BU/D-U(24, 30), B-U/EL(0) MSI: BU/E-L(0); T1/E1: BU/D-U(24, 30), B-U/EL(0) MSI: BU/E-L(0); T1/E1: BU/D-U(24, 30), B-U/EL(0) MSI: BU/E-L(0); T1/E1: BU/D-U(24, 30), B-U/EL(0) EMPTY
R N
of the X.25 link (OML), a "Clear" indication of this alarm may appear. This is a normal part of initialization resulting from the introduction of GCLK Redundancy in SR9.8. If the "Clear" is seen during normal operation without the associated "Major", then there might be an alarm-reporting problem. Note: # can be 0-50 U Note: # can be 0-50
Major
R N
Major
R N
Major
Choose another reference span for the phase locking. If it doesn't help, replace the standby GCLK. Then try to calibrate both GCLKs.
R N C
Major
EMPTY
If this happens excessively (multiple times in a day), replace the GCLK.
R N
October 30, 2008
BSC-11

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r GCLK Long Term Average Alarm Cage: 0; Slot: 3/5 GCLK 12 0xZZ (r#) 25% or more of the GCLK frequency values are out of range. (r#) Minor GCLK: 4, 26 EMPTY Calibrate the GCLK by following the GCLK calibration procedure in the BSC Troubleshooting Guide. If this does not clear the alarm, then either add GCLK-R or if GCLK-R is already installed, Switch the system to the other GCLK and replace this alarming GCLK. R N C
Comments & Notes
1 1
1 2
GCLK Revision Level
Cage: 0; Slot: 3/5
GCLK
12
1 4
GCLK Unlock CLock Reference
Cage: 0; Slot: 3/5
GCLK
12
The hardware version of the GCLK is not supported. (r#) The GCLK was unable to lock to the reference SPAN. (r#)
Minor
EMPTY
EMPTY
Switch to the standby GCLk and replace this card.
C N
U This alarm happens in a couple days or a week after SPAN goes down. This is a long term effect. Immediately after site initialization and recovery of the X.25 link (OML), a "Clear" indication of this alarm may appear. This is a normal part of initialization resulting from the introduction of GCLK Redundancy in SR9.8. If the "Clear" is seen during normal operation without the associated "Major", then there might be an alarm-reporting problem. Note: # can be 0-50 U The supported versions are: 0-10 Note: # can be 0-50
Minor
MSI: 29, 33, 35
MSI: D-U/BU(0), E-L/BU(0); T1/E1: DU/B-U(0), E-L/B-U(0)
Check GCLK card and Reference Span. Calibrate the GCLK by following the GCLK calibration procedure in the BSC Troubleshooting Guide. If this does not clear the alarm, then switch to the standby and replace the GCLK card.
C N
2 6
GCLK Calibration
Cage: 0; Slot: 3/5
GCLK
12
Current GCLK LTA is out of the
Minor
EMPTY
EMPTY
Calibrate the GCLK by following the GCLK calibration procedure in the BSC Troubleshooting Guide.
R N C
U MSI 254 clear alarm is one of the trigger for this alarm. Immediately after site initialization and recovery of the X.25 link (OML), a "Clear" indication of this alarm may appear. This is a normal part of initialization resulting from the introduction of GCLK Redundancy in SR9.8. If the "Clear" is seen during normal operation without the associated "Major", then there might be an alarm-reporting problem. Note: # can be 0-50 U This alarm can be triggered by the insertion of an uncalibrated GCLK
BSC-12
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r acceptable range. (r#) If this does not clear the alarm, then switch the system to the other GCLK and replace this alarming GCLK.
Comments & Notes
2 2 4
Safe Test Fail
Cage: 0; Slot: 3/5
GCLK
12
125 uS, 60 mS, 6.12 S, RDM Failure. (r#) MCAP Timeout, Phase Lock Lost, Oscillator Cold, Reference Span Failure, Needs Calibration. (r#) EMPTY
Critical
GCLK: 5, 6, 7
EMPTY
Switch to the standby GCLK and replace this GCLK. A circuitry failure has been detected.
R N
2 2 4
Safe Test Fail
Cage: 0; Slot: 3/5
GCLK
12
Critical
GCLK: 2, 3, 4, 26
MSI: B-U/DU( 22, 24, 25 ), B-U/EL( 0 ); T1/E1: BU/D-U(24, 30 ), B-U/EL( 0)
GCLK will have phase locking problems. Allow the GCLK to warm, check reference span is INS, and calibrate the GCLK. This will resolve Phase Lock Lost problems.
R N
or by a GCLK losing phase lock (a long term affect). Immediately after site initialization and recovery of the X.25 link (OML), a "Clear" indication of this alarm may appear. This is a normal part of initialization resulting from the introduction of GCLK Redundancy in SR9.8. If the "Clear" is seen during normal operation without the associated "Major", then there might be an alarm-reporting problem. Note: # can be 0-50 U Note: Any combination of the alarm code text can appear when this alarm gets generated. # can be 0-50 U Note: Any combination of the alarm code text can appear when this alarm gets generated. # can be 0-50
equipmentF ailureEvent equipmentF ailureEvent communicat ionFailureE vent
2 3 0 2 3 1 2 3
Board Inserted
Cage: 0; Slot: 3/5 Cage: 0; Slot: 3/5 Cage: 0-5; Slot: 18-25
GCLK
12 12 13 2
Clear
EMPTY
EMPTY
No action required
R N
Board Removed
GCLK
EMPTY
Critical
EMPTY
EMPTY
Check front panel switch and indicator lights If this alarm occurs continuously, replace this GPROC/EGP board. Otherwise, this alarm is self correcting
R N
GPROC Lost Indication
GPROC / EGPRO C
EMPTY
Critical
GPROC/EG PROC: 254
GPROC/EG PROC: BU/D-U(23, 24), E-U/DU(23, 24), E-L/D-L(23, 24)
R N
U Informational alarm, a GCLK has just been inserted. U An operator might have removed the GCLK or it might have gone bad. U If the BOARD OUT alarm occurs at the same time as this alarm, replace/reinsert the board.
October 30, 2008
BSC-13

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
2 7
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
LCF=N1, #MTL=N2, #SITE=N3, util=N4%, onset=N5, abatement= N6, Throttling LUs, Calls, IMSI Detaches, Page Reqs, HOs LCF=N1, #MTL=N2, #SITE=N3, util=N4%, onset=N5, abatement= N6, Throttling LUs, Calls, IMSI Detaches, HOs
Warning
GPROC/EG PROC: 23, 254; MTL: 0, 1, 2, 3; RslSap: 13; SITE: 0, 1, 4; XBL: 0, 1, 2, 3, 5, 6, 7, 10
2 7
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Warning
2 7
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Warning GPROCid= N1, CPUid=N2, OMF, #OMLs=N1 0, #XBLs=N5, util=N7%, threshold= N8%, margin=N9 % GPROCid= N1, CPUid=N2, STANDBY, util=N7%, Warning
2 7
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
GPROC/EG PROC: 23, 254; MTL: 0, 1, 2, 3; RslSap: 13;
GPROC/EG PROC: BU/D-U(23, 24), B-U/EL(0); MTL: B-U/DU(31, 32, 39, 44), BU/E-L(0); XBL: BU/D-U(31, 32, 37), BU/E-U(36), B-U/E-L(0) GPROC/EG PROC: BU/D-U(23, 24), B-U/EL(0); MTL: B-U/DU(31, 32, 39, 44), BU/E-L(0); XBL: BU/D-U(31, 32, 37), BU/E-U(36), B-U/E-L(0) GPROC/EG PROC: BU/D-U(23, 24), B-U/EL(0); MTL: B-U/DU(31, 32, 39, 44), BU/E-L(0); XBL: BU/D-U(31, 32, 37), BU/E-U(36), B-U/E-L(0) GPROC/EG PROC: BU/D-U(23, 24), B-U/EL(0); MTL:
Comments & Notes
U N1 = 0, 1, 2, ... N2 = 0, 1, 2, ... N3 = 0, 1, 2, ... N4 = 0, 10, 11, 23, ... N5 = 0, 10, 11, 23, ... N6=0, 10, 11, 23,
R N C
U N1 = 0, 1, 2, ... N2 = 0, 1, 2, ... N3 = 0, 1, 2, ... N4 = 0, 10, 11, 23, ... N5 = 0, 10, 11, 23, ... N6=0, 10, 11, 23, ...
R N C
U N1 = 0, 1, 2, ... N2 = 0113, 0115, 0215, ... N3 = 0, 1, 2, ... N4 = 0, 1, 2, ... N5 = 0, 1, 2, ... N6 = 0, 1, 2, ... N7 = 0, 10, 11, 23, ... N8 = 0, 10, 11, 23, ... N9 = 0, 10, 11, 23, ... N10 = 0, 1, 2,
R N C
U N1 = 0, 1, 2, ... N2 = 0113, 0115, 0215, ... N3 = 0, 1, 2, ... N4 = 0, 1, 2, ... N5 = 0, 1, 2, ... N6 = 0, 1, 2, ... N7 = 0, 10, 11, 23, ...
BSC-14
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r threshold= N8%, margin=N9 % SITE: 0, 1, 4; XBL: 0, 1, 2, 3, 5, 6, 7, 10 B-U/DU(31, 32, 39, 44), BU/E-L(0); XBL: BU/D-U(31, 32, 37), BU/E-U(36), B-U/E-L(0) GCLK: BU/D-U(25)
Comments & Notes
N8 = 0, 10, 11, 23, ... N9 = 0, 10, 11, 23, ... N10 = 0, 1, 2,
2 8
TDM Clock A Failure
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C GPROC / EGPRO C GPROC / EGPRO C GPROC / EGPRO C GPROC / EGPRO C GPROC / EGPRO C GPROC / EGPRO C
13 2 13 2 13 2 13 2 13 2 13 2 13 2
EMPTY
Major
CBUS: 0, 1, 2, 3
Check the Local KSWX on the A side
R N
2 9
TDM Clock B Failure
Cage: 0-5; Slot: 18-25
EMPTY
Major
CBUS: 0, 1, 2, 3
GCLK: BU/D-U(25)
R N
communicat ionFailureE vent equipmentF ailureEvent equipmentF ailureEvent equipmentF ailureEvent
2 2 4 2 2 8 2 3 0 2 3 1 2 3 2
Safe Test Fail
Cage: 0-5; Slot: 18-25
soft audit timeout for PID: xx, yy EMPTY
Critical
EMPTY
EMPTY
Reset this GPROC/EGP.
R N
Status Fail
Cage: 0-5; Slot: 18-25 Cage: 0-5; Slot: 18-25 Cage: 0-5; Slot: 18-25
Critical
EMPTY
EMPTY
No action required
R N
U If many boards report the same alarm, reseat or replace the Local KSWX cards. U If many boards report the same alarm, reseat or replace the Local KSWX cards. U Reset this GPROC/EGP from the EMON prompt or through the front panel switch. U EMPTY
Board Inserted
EMPTY
Clear
GPROC/EG PROC: 232 GPROC/EG PROC: 232
Board Removed
EMPTY
Critical
General Alarm
Cage: 0-5; Slot: 18-25
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
processingF
General Alarm
Cage: 0-5;
GPROC /
1-
TDM Parity errors reported on X of Y timeslots LAN: Dropping frame, code xfer in progress LAN: dropping frame, max length exceeded LAN:
Critical
GPROC/EG PROC: 231, 254
GPROC/EG PROC: DU/E-U(28) GPROC/EG PROC: BU/D-U(23, 24) EMPTY
No action required
R N
No action required
R N
U When MCAP GPROC comes back or card is inserted. U When MCAP GPROC switches over or card is pulled out. U EMPTY
Check the fiber connections between the KSWX cards
R N
Critical
EMPTY
EMPTY
Critical
EMPTY
EMPTY
Check the state of GPROCs/EGPs, find the GPROC/EGP that has gone down, make sure the GPROC/EGP is stable. No action required
R N
U EMPTY
R N
U Indication that a frame that was too big was received on the LAN.
Critical
GPROC/EG
GPROC/EG
If this problem persists, check
R N
U Indication that no buffers
October 30, 2008
BSC-15

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Slot: 18-25 EGPRO C 3 2 dropping frame, no Q blocks available LAN FLOW CONTROL: locking all LAN Links LAN FLOW CONTROL: Unlocking all LAN Links BAD FRAME RECEIVED exceeding Q_BLOCK_ SIZE Cannot recover MCAP: MCAP fail GPROC ##: Disable CAGE ## Cannot recover MCAP: CSAP fail GPROC ##: Disable CAGE ## MCAP recovered: GPROC ## / CAGE ## / SLOT ## MCAP disabled: GPROC ## / CAGE ## / SLOT ## PROC: 23, 231, 254 PROC: BU/D-U(23, 24) GPROC/EG PROC: BU/D-U(23, 24) EMPTY LAN connectivity.
Comments & Notes
ailureEvent
3 2
are available to send data over the LAN, possible LAN issue. R N U Indication that no buffers are available to send data over the LAN, possible LAN issue. U Indication that buffers are now available to send data over the LAN, possible LAN issue. U Indication that a frame that was too big was received on the LAN.
2 3 2 2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C GPROC / EGPRO C
13 2 13 2
Critical
GPROC/EG PROC: 23, 231, 254 EMPTY
General Alarm
Cage: 0-5; Slot: 18-25
Critical
R N
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Critical
EMPTY
EMPTY
No action required
R N
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Critical
EMPTY
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Critical
EMPTY
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Critical
EMPTY
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Critical
2 3
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO
13
Cannot recover
Critical
EMPTY
GPROC/EG PROC: BU/D-U(23, 24), E-U/DU(23, 24), E-L/D-L (23, 24) GPROC/EG PROC: BU/D-U(23, 24), E-U/DU(23, 24), E-L/D-L (23, 24) GPROC/EG PROC: DU/B-U(0), D-U/EU(28) GPROC/EG PROC: BU/D-U(23, 24), E-U/DU(23, 24), E-L/D-L(23, 24) GPROC/EG PROC: B-
Replace card reporting alarm
R N
U EMPTY
Replace card reporting alarm
R N
U EMPTY
No action required
R N
U Information alarm reporting MCAP recovery
No action required
R N
U The MCAP should recover on an available GPROC/EGP in the same cage
Replace the card reporting alarm
R N
U If this alarm occurs continuously, replace the
BSC-16
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r C 2 MCAP: No available GPROC: Disable CAGE ## %s ##, ##, Timeslot Condition Occurred: MCAP: Wait ## minutes for available GPROC CAGE ## Cannot recover MCAP: ## minute Time-out exceeded: Disable CAGE ## Unknown Intrpt 0x%x rcvd, channel %d, sap %d, restart T7115/T713 0 U/D-U(23, 24), E-U/DU(23, 24), E-L/D-L(23, 24) EMPTY
Comments & Notes
board
2 3 2 2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C GPROC / EGPRO C
13 2 13 2
Critical
EMPTY
No action required
R N
U EMPTY
General Alarm
Cage: 0-5; Slot: 18-25
Critical
EMPTY
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Critical
EMPTY
GPROC/EG PROC: BU/D-U(23, 24), E-U/DU(23, 24), E-L/D-L(23, 24) GPROC/EG PROC: BU/D-U(23, 24), E-U/DU(23, 24), E-L/D-L(23, 24) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) RslSap: B-
No action required
R N
U Information alarm reporting attempted MCAP recovery
If this alarm occurs continuously, replace this GPROC/EGP board. Otherwise, this alarm is self correcting
R N
U EMPTY
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 11
Possible T1 / DACS problems . Check BSC to EBTS or BSC to XCDR (for XBL) physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this link
R N
U In the case where an Unknown Interrupt has been received and the HDLC Chip will be reset, this alarm will be displayed
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Unknown Intrpt 0x%x rcvd, channel %d, sap %d, must reset GPROC
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 12
Possible GPROC issues or possible T1 / DACS problems . Check BSC to EBTS or BSC to XCDR (for XBL) physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this link. If the condition persists, replace the GPROC.
R N
U In the case where too many unknown interrupts have been received, the GPROC needs to be reset, this alarm will be displayed
processingF
General Alarm
Cage: 0-5;
GPROC /
1-
Unknown
Critical
RslSap: 9,
Possible T1 / DACS problems .
R N
U In the case where an
October 30, 2008
BSC-17

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Slot: 18-25 EGPRO C 3 2 Intrpt 0x%x rcvd, channel %d, sap %d 10, 11; OML: 0; XBL: 9, 10, 13 U/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) RslSap: BU/D-U(31, 32, 35, 37, 39, 40, 46, Check BSC to EBTS or BSC to XCDR (for XBL) physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this link
Comments & Notes
ailureEvent
3 2
Unknown Interrupt has been received and the "lap_isr_fix_flag" is set to "off", the HDLC Chip reset has been turned off, this alarm will be displayed
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
T7130 LAPD controller FATAL ERROR error Code=%d. Restart T7115/T713 0 T7130 LAPD controller FATAL ERROR error Code=%d, must reset GPROC
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 14
R N
U In the case where a Fatal error occurred and the HDLC Chip will be reset this alarm will be displayed
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 15
Possible GPROC issues or possible T1 / DACS problems . Check BSC to EBTS or BSC to XCDR (for XBL) physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this link. If the condition persists, replace the GPROC.
R N
U In the case where too many Fatal error occurred on T7130 Chipset or the "lap_isr_fix_flag" is set to "off", this alarm will be displayed
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
T7130 Halted, must reset T7115/T713 0 to recover, channel%d
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10, 16
R N
U In the case where T7130 is halted, condition detected by one way XBL, this alarm will be displayed
2 3 2
General Alarm
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
T7130 Halted, must reset GPROC to
Critical
RslSap: 9, 10, 11; OML: 0; XBL: 9, 10,
Possible GPROC issues or possible T1 / DACS problems . Check BSC to EBTS or BSC to XCDR (for XBL) physical
R N
U In the case where the "lap_isr_fix_flag" is set to "off" or if the condition happened too many times,
BSC-18
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r recover, channel %d 17 47), OML: B-U/DU(31, 32, 39, 43); XBL: BU/D-U(31, 32, 37) GPROC/EG PROC: BU/D-U(23, 24), E-U/DU(23, 24), E-L/D-L (23, 24) CBUS: BU/D-U(61), B-U/E-U(0); TBUS: BU/D-U(22, 24, 29), BU/E-U(28) CBUS: EU/D-U(61), B-U/DU(61); GCLK: EU/D-U(25), B-U/DU(25), BU/E-U(48) CBUS: EU/D-U(61), B-U/DU(61); GCLK: EU/D-U(25), B-U/DU(25), BU/E-U(48) GCLK: EU/D-U(25), B-U/DU(25), BU/E-U(48) EMPTY connection as well as devices(GPROC/EGP, MSI, etc) controlling this link. If the condition persists, replace the GPROC.
Comments & Notes
this alarm will be displayed
2 5 4
Device Failed
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
EMPTY
Critical
Verify that the front panel switch is the enabled position.
R N
U Check the board, reseat or replace the card.
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 18-25
GPROC / EGPRO C
13 2
Wrong bus(es): MCAP TDM Clock
Critical
EMPTY
Board maybe on a wrong bus. Lock/Unlock the board to initialize the board to the proper active buses. If problem persists, replace the board.
R N
Note: Any combination of the alarm code text can appear when this alarm gets generated.
Clock A Loss
Cage: 0-5; Slot: 1/27
KSW
18
EMPTY
Critical
CBUS:0, 1, 2, 3, 5; GCLK: 5, 6, 7, 9
R N
U If many boards report the same alarm, reseat or replace the Local KSWX cards.
Clock B Loss
Cage: 0-5; Slot: 1/27
KSW
18
EMPTY
Critical
CBUS:0, 1, 2, 3, 5; GCLK: 5, 6, 7, 9
R N
U If many boards report the same alarm, reseat or replace the Local KSWX cards.
_6.12 Second Reference Loss
Cage: 0-5; Slot: 1/27
KSW
18
EMPTY
Major
GCLK: 224
No action required
R N C
U If the alarm reoccurs, check the calibration of the GCLK.
KSW Re Initialized Unexpectedly
Cage: 0-5; Slot: 1/27
KSW
18
EMPTY
Critical
EMPTY
This alarm is self correcting
R N
U If this alarm occurs continuously, replace the board
October 30, 2008
BSC-19

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
KSW Reset
Cage: 0-5; Slot: 1/27
KSW
18
Watchdog Timer Expired
Cage: 0-5; Slot: 1/27
KSW
18
KSW IRR Value is ##, ISR Value is ## KSW IRR Value is ##, ISR Value is ##
Critical
EMPTY
EMPTY
Y C / l N e a r R N
Comments & Notes
U If this alarm occurs continuously, replace the board U If this alarm occurs continuously, replace the board. If the board does not recover, this problem could be because of a bad GCLK.
Critical
CBUS: 0, 1, 2, 3; KSW: 8; GCLK: 5,6
1 0
Expansion KSWX TDM Failure
Cage: 0-5; Slot: 1
KSW
14
1 1
Cage: 0-5; Slot: 1
KSW
14
1 2
Cage: 0-5; Slot: 1
KSW
14
1 3
Cage: 0-5; Slot: 27
KSW
14
1 4
Cage: 0-5; Slot: 27
KSW
14
Check connections to KSWX RX port in Cage xx, Slot 7 Check connections to KSWX RX port in Cage xx, Slot 8 Check connections to KSWX RX port in Cage xx, Slot 9 Check connections to KSWX RX port in Cage xx, Slot 21 Check connections to KSWX RX port in Cage xx,
Major
KSW: 8( c ), 230
CBUS: EU/D-U(61), B-U/DU(61); GCLK: EU/D-U(25), B-U/DU(25), BU/E-U(48); KSW: EU/D-U(22, 24, 25), BU/D-U(22, 24, 25) EMPTY
R N
Check fiber cable connections at both ends. Check both KSWX cards. Reconnect/replace if necessary.
R N C
U The related alarms are for the clear alarm
Major
KSW: 8( c ), 230
EMPTY
R N C
Major
KSW: 8( c ), 230
EMPTY
R N C
Major
KSW: 8( c ), 230
EMPTY
R N C
Major
KSW: 8( c ), 230
EMPTY
R N C
BSC-20
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Expansion KSWX TDM Failure Cage: 0-5; Slot: 27 KSW 14 Slot 22 Check connections to KSWX RX port in Cage xx, Slot 23 Clock A Loss, Clock B Loss, 6.12 Second Reference Loss Major KSW: 8( c ), 230 EMPTY Check fiber cable connections at both ends. Check both KSWX cards. Reconnect/replace if necessary. R N C
Comments & Notes
1 5
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 1/27
KSW
18
Major
KSW: 4, 7
EMPTY
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 1/27
KSW
18
Wrong bus(es): MCAP TDM Clock
Major
CBUS: 0, 1, 2, 3, 5; KSW: 4, 5; GCLK: 5,6, 7, 9
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 1/27
KSW
18
MCAP timeout
Major
LAN: 1; KSW: 228
CBUS:EU/D-U(61), B-U/DU(61); GCLK: BU/D-U(25), E-U/DU(25), BU/E-U(48) LAN: EU/D-U(131), B-U/DU(132)
For Clock A and B Loss, check for clock signal from CLKX to local KSWXs. If necessary, reseat local KSWX. If this doesn't work, replace KSW. For 6.12 Second Reference Loss, execute GCLK status audit. If GCLK audit fails, replace GCLK Else, replace KSW. Lock/Unlock the KSW to reinitialize the board to the proper active buses. If problem persists, replace the board.
R N
Note: Any combination of the alarm code text can appear when this alarm gets generated.
R N
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 1/27
KSW
18
EMPTY
Critical
KSW: 4, 7; CBUS: 0, 1, 2, 3, 5; KSW: 4, 5; GCLK: 5,6, 7, 9; LAN: 1; KSW: 228
CBUS:EU/D-U(61), B-U/DU(61); GCLK: BU/D-U(25), E-U/DU(25), BU/E-U(48); LAN: EU/D-U(131),
Run the safe test on the MCAP GPROC. If it passes, then check the sanity of the cage and lock/unlock KSW. If it fails, run the safe test for MCAP GPROC again. If MCAP timeout continues, reset MCAP GPROC for the cage that is reporting the timeout. (CAUTION: Resetting master cage MCAP will reset the entire BSC). Execute the remedy for the previously reported Safe Test Fail alarms for the same device.
R N
U When GCLK reset, if KSW does not switch to the right CBUS within 10 minutes, safe test will be failed for KSW. Note: Any combination of the alarm code text can appear when this alarm gets generated. U EMPTY
R N
U When Safe Test Fail alarm for this device is reported consecutively for 5 times, there will be a "Major" alarm raised along with the 5th alarm for the same device.
October 30, 2008
BSC-21

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r B-U/DU(132) EMPTY
Comments & Notes
2 2 8
Status Fail
Cage: 0-5; Slot: 1/27
KSW
18
2 3 0 2 3 1
Board Inserted
Cage: 0-5; Slot: 1/27 Cage: 0-5; Slot: 1/27
KSW
18 18
TXQ_JAM MED condition is hit. RXQ_RUN AWAY condition is hit. Mailbox is locked EMPTY
Major
EMPTY
Front-panel reset the KSW
R N
U This does not affect call processing.
Clear
GPROC/EG PROC: 232 LAN: 1; GPROC/EG PROC: 232
Board Removed
KSW
EMPTY
Critical
2 5 4
Device Failed
Cage: 0-5; Slot: 1/27
KSW
18
EMPTY
Critical
LAN Failure
Side: 0/1
LAN
12
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent
Remote Alarm Daily Threshold Exceeded Remote Alarm Hourly Threshold Exceeded Remote Alarm OOS Threshold Exceeded Frame Slip Daily Threshold Exceeded Frame Slip Hourly Threshold Exceeded
Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17
MSI
MSI
MSI
MSI
MSI
17 2 17 2 17 2 17 2 17 2
Check fiber connections and LANX insertion stream group: ## stream group: ## stream group: ## stream group: ## stream group: ##
Critical
KSW: 7, 9, 224; GPROC/EG PROC: 232; MSI: 25; XCDR: 19 EMPTY
GPROC/EG PROC: DU/E-U(28) LAN: EU/D-U(131), B-U/DU(132); GPROC/EG PROC: BU/D-U(23, 24) EMPTY
No action required
R N
Check front panel switch and indicator lights
R N
U When MCAP GPROC comes back or card is inserted. U When MCAP GPROC switches over or card is pulled out.
Verify that the front panel switch is the enabled position.
R N
U Check the board, reseat or replace the card.
EMPTY
Minor
MSI: 8
EMPTY
Investigate cause of LAN failure. Alarm will be cleared once the back up ring test indicates the LAN is operational. Minor recurring T1 physical line error. Check TX line from BSC. Major recurring T1 physical line error. Check TX line from the BSC. Critical recurring T1 physical line error. Check TX line from the BSC Minor T1 clocking problem on physical line. Check clock reference sources. Major T1 clocking problem on physical line. Check clock reference sources.
R N C
U EMPTY
R N
U EMPTY
Major
MSI: 8
EMPTY
R N
U EMPTY
Critical
MSI: 8
EMPTY
R N C R N
U EMPTY
Minor
EMPTY
EMPTY
U EMPTY
Major
EMPTY
EMPTY
R N
U EMPTY
BSC-22
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent equipmentF ailureEvent equipmentF ailureEvent
Frame Slip OOS Threshold Exceeded Remote Alarm OOS Timer Expired Framed AIS OOS Timer Expired Red Alarm Daily Threshold Exceeded Red Alarm Hourly Threshold Exceeded Red Alarm OOS Threshold Exceeded Red Alarm OOS Timer Expired MSI Initialized
Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17
MSI
MSI
1 0 1 2 1 3 1 4 1 6 1 8 1 9
MSI
MSI
MSI
MSI
MSI
MSI
MSI Reset
MSI
17 2 17 2 17 2 17 2 17 2 17 2 17 2 17 2 17 2 17 2
stream group: ## stream group: ## stream group: ## stream group: ## stream group: ## stream group: ## stream group: ## EMPTY
Critical
EMPTY
EMPTY
Critical
EMPTY
EMPTY
Critical T1 clocking problem on physical line. Check clock reference sources. Far end doesn't see BSC TX signal. Far end is sending a `keep alive' signal to BSC. Minor recurring T1 line problem. Lock/Unlock on MSI resets alarm counters. Major recurring T1 line problem. Lock/Unlock on MSI resets alarm counters. Critical recurring T1 line problem. Lock/Unlock on MSI resets alarm counters. BSC does not see a good incoming line. Check physical connections. No action required
Y C / l N e a r R N C R N C R N C R N
Comments & Notes
U EMPTY
U EMPTY
Critical
EMPTY
EMPTY
U EMPTY
Minor
MSI: 16
EMPTY
U EMPTY
Major
MSI: 16
EMPTY
R N
U EMPTY
Critical
MSI: 16
EMPTY
R N C R N C R N
U EMPTY
Critical
EMPTY
EMPTY
U EMPTY
Critical
EMPTY
EMPTY
U Informational alarm, a MSI has just been inserted. U If this alarm occurs continuously, replace the board U If this alarm occurs continuously, replace the board. If the board does not recover, this problem could be because of a bad GCLK. U If many boards report the same alarm, reseat or replace the Local KSWX cards. U If many boards report the same alarm, reseat or replace the Local KSWX cards. U Alarm is self correcting, if there are no parity errors, the device will be disabled. A reset or replacement might be required to bring
2 0
Cage: 0-5; Slot: 6-17
MSI
MSI IRR Value is ##, ISR Value is ## MSI IRR Value is ##, ISR Value is ##
Critical
EMPTY
EMPTY
R N
Critical
EMPTY
EMPTY
R N
2 1
TDM Clock B Failure
Cage: 0-5; Slot: 6-17
MSI
17 2 17 2 17 2
2 2
TDM Clock A Failure
Cage: 0-5; Slot: 6-17
MSI
2 3
Assigned Timeslot Counter Underflow
Cage: 0-5; Slot: 6-17
MSI
MSI IRR Value is ##, ISR Value is ## MSI IRR Value is ##, ISR Value is ## MSI IRR Value is ##, ISR Value is ##
Major
CBUS: 0, 1, 2, 3
GCLK: BU/D-U(25)
R N C
Major
CBUS: 0, 1, 2, 3
GCLK: BU/D-U(25)
R N C
Critical
CBUS: 1 , 3
EMPTY
No action required
R N C
October 30, 2008
BSC-23

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Assigned Timeslot Counter Overflow Cage: 0-5; Slot: 6-17 MSI 17 2 MSI IRR Value is ##, ISR Value is ## Critical CBUS: 1 , 3 EMPTY No action required R N C
Comments & Notes
2 4
communicat ionFailureE vent communicat ionFailureE vent
2 5
TDM Parity Error
Cage: 0-5; Slot: 6-17
MSI
17 2 17 2
2 5
TDM Parity Error
Cage: 0-5; Slot: 6-17
MSI
2 5
TDM Parity Error
Cage: 0-5; Slot: 6-17
MSI
17 2
2 6
Synchronization Loss Daily Threshold Exceeded
Cage: 0-5; Slot: 6-17
MSI
17 2
MSI IRR Value is ##, ISR Value is ## TDM Parity errors reported on X of Y timeslots TDM Parity errors reported on all Y timeslots stream group: ##
Major
CBUS: 0, 1, 2, 3; MSI: 231 CBUS: 0, 1, 2, 3; MSI: 231
EMPTY
Execute the tdm_conn_test command to isolate the cause of the alarm Execute the tdm_conn_test command to isolate the cause of the alarm
R N C
the card back into service. U Alarm is self correcting, if there are no parity errors, the device will be disabled. A reset or replacement might be required to bring the card back into service. U EMPTY
Major
EMPTY
R N C
U EMPTY
Major
CBUS: 0, 1, 2, 3; MSI: 231
EMPTY
Execute the tdm_conn_test command to isolate the cause of the alarm
R N C
U EMPTY
Minor
MSI: 34
EMPTY
2 7
Synchronization Loss Hourly Threshold Exceeded
Cage: 0-5; Slot: 6-17
MSI
17 2
stream group: ##
Major
MSI: 34
EMPTY
2 8
Synchronization Loss OOS Threshold Exceeded
Cage: 0-5; Slot: 6-17
MSI
17 2
stream group: ##
Critical
MSI: 34
EMPTY
2 9 3 0
Synchronization Loss Restoral Threshold Exceeded Bit Error Rate Daily Threshold Exceeded
Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17
MSI
MSI
17 2 17 2
stream group: ## stream group: ##
Critical
EMPTY
EMPTY
Indication of a minor recurring E1 physical line problem. Check physical connections or stability of far end equipment. Lock/Unlock of MSI will reset alarm counters. Indication of a major recurring E1 physical line problem. Check physical connections or stability of far end equipment. Lock/Unlock of MSI will reset alarm counters. Indication of a critical recurring E1 physical line problem. Check physical connections or stability of far end equipment. Lock/Unlock of MSI will reset alarm counters. Indication that the alarm has cleared. Indication of a minor recurring E1 physical line problem. Check physical connections or stability of far end equipment. Lock/Unlock of MSI will reset alarm counters. Indication of a major recurring E1 physical line problem. Check physical connections or stability of
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
3 1
Bit Error Rate Hourly Threshold Exceeded
Cage: 0-5; Slot: 6-17
MSI
17 2
stream group: ##
Major
EMPTY
EMPTY
R N
U EMPTY
BSC-24
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r far end equipment. Lock/Unlock of MSI will reset alarm counters. Indication of a critical recurring E1 physical line problem. Check physical connections or stability of far end equipment. Lock/Unlock of MSI will reset alarm counters. Indication that alarm has cleared.
Comments & Notes
3 2
Bit Error Rate OOS Threshold Exceeded
Cage: 0-5; Slot: 6-17
MSI
17 2
stream group: ##
Critical
EMPTY
EMPTY
R N
U EMPTY
communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent
3 3 3 4 3 5 2 2 4 2 2 4
Bit Error Rate Restoral Threshold Exceeded Synchronization Loss OOS timer expired Synchronization Loss Restoral Timer Expired Safe Test Fail
Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17 Cage: 0-5; Slot: 6-17
MSI
MSI
MSI
MSI
17 2 17 2 17 2 17 2 17 2
stream group: ## stream group: ## stream group: ## span: xx (yy), span: xx (yy) Wrong bus(es): MCAP TDM Clock MCAP timeout
Critical
EMPTY
EMPTY
R N
U EMPTY
Critical
EMPTY
EMPTY
Loss of signal. Check line or far end equipment. Signal restored.
R N
U EMPTY
Critical
EMPTY
EMPTY
R N
U EMPTY
Warning
EMPTY
EMPTY
Safe Test Fail
Cage: 0-5; Slot: 6-17
MSI
Warning
EMPTY
EMPTY
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 6-17
MSI
17 2
Warning
GPROC/EG PROC: 232; MSI: 228
EMPTY
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 6-17
MSI
17 2
EMPTY
Major
GPROC/EG PROC: 232; MSI: 228
EMPTY
Span reporting alarms. Check status of span(s). Lock/Unlock MSI. Replace MSI card if problem persists. Board maybe on a wrong bus. Lock/Unlock the board to initialize the board to the proper active buses. If problem persists, replace the board. Run the safe test on the MCAP GPROC. If it passes, then check the sanity of the cage. If it fails, run the safe test for MCAP GPROC again. If MCAP timeout continues, reset MCAP GPROC for the cage that is reporting the timeout. (CAUTION: Resetting master cage MCAP will reset the entire BSC). Execute the remedy for the previously reported Safe Test Fail alarms for the same device.
R N
U EMPTY
R N
U Note: Any combination of the alarm code text can appear when this alarm gets generated. U EMPTY
R N
R N
2 2 8
Hardware Status Fail
Cage: 0-5; Slot: 6-17
MSI
17 2
TXQ_JAM MED condition is hit. RXQ_RUN
Major
EMPTY
EMPTY
Front-panel reset the MSI
R N
U When Safe Test Fail alarm for this device is reported consecutively for 5 times, there will be a "Major" alarm raised along with the 5th alarm for the same device. U This does not affect call processing.
October 30, 2008
BSC-25

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r AWAY condition is hit. Mailbox is locked EMPTY
Comments & Notes
2 3 0 2 3 1 2 5 4 0
Board Inserted
MSI
Board Removed
MSI
17 2 17 2 17 2 11 6
Clear
EMPTY
Critical
Device Failed
Cage: 0-5; Slot: 6-17
MSI
EMPTY
Critical
MSI: 18, 21, 25
No action required
R N
R N
U When MCAP GPROC comes back or card is inserted. U When MCAP GPROC switches over
No action required
R N
Signaling Link OOS
Device ID: 0-15
MTL
signal link: ##, event data: ##
Critical
EMPTY
EMPTY
communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent
Remote Processor Out Remote User Part Unavailable Link Traffic Too High
Device ID: 0-15 Device ID: 0-15 Device ID: 0-15
MTL
MTL
MTL
11 6 11 6 11 6
signal link: ##, event data: ## signal link: ##, event data: ## signal link: ##, event data: ##
Major
EMPTY
EMPTY
Major
EMPTY
EMPTY
Indication that the MTL has gone down. Check the connectivity between the MSC and BSC as well as devices controlling this MTL Indication that the remote side, the MSC, is having processor outages. Check the MSC. Indication of a remote user part unavailable, check the MSC. Indication that the transmit buffers on the BSC are getting full. Find the source of messages and examine if an extra link needs to be added or it is a misconfiguration issue. Indication that there are a high number of messages being sent to the BSC by the MSC. Find the source of messages and examine if an extra link needs to be added or it is a misconfiguration issue Indication that there are a high number of messages being sent by the BSC to the MSC and buffers are getting full. SS7 congestion control will start controlling the traffic. Find the source of messages and examine if an extra link needs to be added or it is a misconfiguration issue
R N
U This alarm might be seen if the BSP is reset. If the alarm occurs continuously, replace the BSP. U EMPTY
R N
U EMPTY
R N
U EMPTY
Major
MTL: 0 , 1
MTL: BU/D-U(31, 32, 39, 44)
R N C
U EMPTY
Link Traffic Too High
Device ID: 0-15
MTL
11 6
signal link: %d, RX Buffer Full
Major
MTL: 0 , 1
MTL: BU/D-U(31, 32, 39, 44)
R N C
U EMPTY
Device ID: 0-15
MTL
11 6
signal link:%d, TX Buffer Full. Throttling LUs, Calls, IMSI Detaches, HOs
Major
MTL: 0 , 1
MTL: BU/D-U(31, 32, 39, 44)
R N C
U EMPTY
BSC-26
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Device ID: 0-15
MTL
11 6
Last Link Failed
Device ID: 0-15
MTL
11 6
signal link:%d, MSC Congestion Indication Received. Throttling LUs, Calls, IMSI Detaches, HOs EMPTY
Major
MTL: 0 , 1
MTL: BU/D-U(31, 32, 39, 44)
Indication sent to the BSC that the MSC is congested. Find the source of congestion and examine if it is a misconfiguration issue
Comments & Notes
U EMPTY
Critical
MTL: 0
MTL: BU/D-U(31, 32, 39, 44)
Threshold Exceeded: SL Alignment Failure
Device ID: 0-15
MTL
11 6
EMPTY
Minor
EMPTY
EMPTY
BSC - MSC communication lost, last MTL failed. Check the connectivity between the MSC and BSC as well as devices controlling this MTL Check the connection between BSC and EBTS and MSC.
R N
U EMPTY
R N
Threshold Exceeded: Number of Signal Units in error
Device ID: 0-15
MTL
11 6
EMPTY
Warning
EMPTY
EMPTY
Check the connection between BSC and EBTS and MSC.
R N
Threshold Exceeded: SL Number of Negative Acks Received
Device ID: 0-15
MTL
11 6
EMPTY
Warning
EMPTY
EMPTY
R N
Threshold Exceeded: Start of Remote Processor Outage
Device ID: 0-15
MTL
11 6
EMPTY
Warning
EMPTY
EMPTY
R N
Threshold Exceeded: Number of Octets Retransmitted
Device ID: 0-15
MTL
11 6
EMPTY
Warning
EMPTY
EMPTY
R N
communicat
Threshold Exceeded:
Device ID:
MTL
1-
EMPTY
Warning
EMPTY
EMPTY
If these alarms keep appearing it
R N
U PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) U PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) U PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) U PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) U PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) U PMALARM. These are
October 30, 2008
BSC-27

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r MSUs Discarded due to SL Congestion 0-15 1 6 is an indication that the system can not handle the offered traffic. The remedy will be to add more resources (MTLs) to the system. EMPTY Warning EMPTY EMPTY Check the connection between BSC and EBTS and MSC. R N
Comments & Notes
ionFailureE vent
1 1
Threshold Exceeded: SL Congestion Events Resulting in Loss of MSUs
Device ID: 0-15
MTL
11 6
1 2
Threshold Exceeded: SL Congestion Indications
Device ID: 0-15
MTL
11 6
EMPTY
Warning
EMPTY
EMPTY
R N
1 3
Threshold Exceeded: SL Failure, All Reasons
Device ID: 0-15
MTL
11 6
EMPTY
Major
EMPTY
EMPTY
R N
1 4
Threshold Exceeded: SL Failure, Abnormal FIBR/BSNR
Device ID: 0-15
MTL
11 6
EMPTY
Major
EMPTY
EMPTY
R N
1 5
Threshold Exceeded: SL Failure, Excessive Delay of ACK
Device ID: 0-15
MTL
11 6
EMPTY
Major
EMPTY
EMPTY
R N
1 6
Threshold Exceeded: SL Failure, Excessive Error Rate
Device ID: 0-15
MTL
11 6
EMPTY
Major
EMPTY
EMPTY
R N
1 7
Threshold Exceeded: SL Failure, Excessive Duration of Congestion Link Disconnected
Device ID: 0-15
MTL
11 6
EMPTY
Major
EMPTY
EMPTY
communicat
Device ID:
OML
1-
EMPTY
Critical
EMPTY
EMPTY
If these alarms keep appearing it is an indication that the system can not handle the offered traffic. The remedy will be to add more resources (MTLs) to the system. Indication that the OML links as
R N
indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) PMALARM. These are indications of problems with the link outside of the BSC (either the physical link or the remote side of the link, i.e.; the MSC) PMALARM
R N
U EMPTY
BSC-28
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r 0/1 2 been disconnected, check BSC to OMC connectivity as well as devices(GPROC/EGP, MSI, etc)controlling this OML If this happens, the operator will have to either move the OMF functionality to an EGP and reinitiate the BGDL, or keep the OMF as GPROC1 and initiate a FGDL. Check X.25 link
Comments & Notes
ionFailureE vent
Link Alarm
Device ID: 0/1
OML
12
Threshold Exceeded: Expiration of N2
Device ID: 0/1
OML
12
Insufficient memory for BGDL, assign OMF to EGP or perform FGDL EMPTY
Major
EMPTY
EMPTY
R N
U EMPTY
Warning
EMPTY
EMPTY
R N
Threshold Exceeded: Invalid Received Frames
Device ID: 0/1
OML
12
EMPTY
Warning
EMPTY
EMPTY
Check X.25 link
R N
Threshold Exceeded: FRMR Frames
Device ID: 0/1
OML
12
EMPTY
Warning
EMPTY
EMPTY
Check X.25 link
R N
Bad Configuration
Device ID: 0-19
OPL
12 0
Span and ts can't be chosen for OPL link
Warning
EMPTY
EMPTY
Bad ID
Device ID: 0-2
PAB
11 8
Cabinet: ìd', `pab location'
Warning
EMPTY
EMPTY
OPL link can be equipped either on span (with at least one RSL link) and unequipped ts or on span (with no sysgen configured link) and unequipped ts. For correct OPL equipping the proper action is SYSGEN. Check if compatible PAB is installed in BSC cabinet.
R N C
U PMALARM. Those three are related to the statistics of OML framing types. Basically, we can not do anything to make it better U PMALARM. Those three are related to the statistics of OML framing types. Basically, we can not do anything to make it better U PMALARM. Those three are related to the statistics of OML framing types. Basically, we can not do anything to make it better U EMPTY
R N C
No Board
Device ID: 0-2
PAB
11 8
Cabinet: ìd', `pab location'
Critical
EMPTY
EMPTY
Bad response returned from PAB due to time out while polling PAB. Ignore the alarm if a clear alarm comes after that. If problem persists, check the cable
R N C
U Note: 'pab location' can be any one of following: Lower Cage Right Fan, Lower Cage Center Fan, Lower Cage Left Fan, Upper Cage Right Fan, Upper Cage Center Fan, Upper Cage Left Fan. PAB ID maps to its cabinet num U PAB ID maps to its cabinet num
October 30, 2008
BSC-29

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r connecting the PAB board to the cage. Bad data returned from PAB. Replace PAB. Replace specified FAN.
Comments & Notes
equipmentF ailureEvent equipmentF ailureEvent equipmentF ailureEvent communicat ionFailureE vent
Bad Status
Device ID: 0-2 Device ID: 0-2 Device ID: 0-2 Device ID [0]: 1-80; Device ID [1]: 0/1 Device ID [0]: 1-80; Device ID [1]: 0/1 Device ID [0]: 1-80; Device ID [1]: 0/1 Device ID [0]: 1-80; Device ID [1]: 0/1 Device ID [0]: 1-80; Device ID [1]: 0/1 Device ID [0]: 1-80; Device ID [1]: 0/1 Device ID [0]: 1-80; Device ID [1]: 0/1 Device ID [0]: 1-80; Device ID
PAB
Fan Failure
PAB
Fan Fuse Failure
PAB
Link Timeout
RslSap
11 8 11 8 11 8 11 6 0 11 6 0 11 6 0 11 6 0 11 6 0 11 6 0 11 6 0 11 6
Cabinet: ìd', `pab location' Cabinet: ìd', `pab location' Cabinet: ìd', `pab location' EMPTY
Warning
EMPTY
EMPTY
R N C R N C R N C R N
U PAB ID maps to its cabinet num U PAB ID maps to its cabinet num U PAB ID maps to its cabinet num U EMPTY
Critical
EMPTY
EMPTY
Critical
EMPTY
EMPTY
Replace specified FUSE
Critical
EMPTY
EMPTY
Sequence Error
RslSap
EMPTY
Minor
EMPTY
EMPTY
Frame Rejected
RslSap
EMPTY
Minor
EMPTY
EMPTY
Unexpected Response Frame
RslSap
EMPTY
Minor
EMPTY
EMPTY
Bad Configuration
RslSap
EMPTY
Indetermina te
EMPTY
EMPTY
Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this RSL. Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this RSL. Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this RSL. Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this RSL. Check BSC to EBTS physical connection, possible SPAN in loopback. Check the BSC to EBTS physical connection. Possible one way communication. Check T1 / DACS as well as devices(GPROC/EGP, MSI, etc) controlling this RSL. Check BSC to EBTS physical connection.
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
Unexpected SABME Received
RslSap
EMPTY
Critical
EMPTY
EMPTY
R N
U EMPTY
Bad Frame
RslSap
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Link SABME Failed
RslSap
EMPTY
Critical
EMPTY
EMPTY
Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as
R N
U EMPTY
BSC-30
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r [1]: 0/1 0 RslSap 11 6 0 EMPTY Critical EMPTY MSI: B-U/DU(22, 24, 25), B-U/EL(0); T1/E1: B-U/DU(24, 30), B-U/E-L(0) EMPTY devices(GPROC/EGP, MSI, etc) controlling this RSL. Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this RSL.
Comments & Notes
Link Disconnect Failed
Device ID [0]: 1-80; Device ID [1]: 0/1
R N
U EMPTY
Link Statistics Failed
RslSap
11 6 0
Bouncing RSL #, chn # mb #, on GPROC slot # cage # Possible T1 problems
Critical
EMPTY
Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this RSL.
R N
RslSap
11 6 0
Bouncing RSL # chn # mb # on GPROC slot # cage # MDL error timeout
Critical
EMPTY
EMPTY
R N
RslSap
11 6 0
RslSap
11 6 0
Bouncing RSL # chn # mb # on GPROC slot #, cage #. Two MDL errors occurred within tmo Unknown reason # to bounce link on channel #, sap
Critical
EMPTY
EMPTY
R N
U In the case where we get the channel being restarted due to lockup of the mailbox the following will be displayed. This is the case where BSC has data to send out but, possibly because of T1 errors, BSC runs out of buffers since there are no responses from the remote side. U In the case where an MDL error timeout occurs, the following will be displayed. MDL error timeout occurs when an MDL error is detected but within a specified timeout, the link didn't recover and it didn't go down either. Unlikely scenario but it is there as backup. U In the case where an MDL errors is received before recovering from the first MDL error this alarm will be displayed
Critical
EMPTY
EMPTY
R N
U In the case where it is an unknown cause for the channel reset, it will display this alarm. This will be for any other case that is not specified above.
October 30, 2008
BSC-31

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
RslSap
11 6 0
RslSap
11 6 0
RslSap
11 6 0
RslSap
11 6 0
1 0
Link Disconnected
1 1
Link Connected
Device ID [0]: 1-80; Device ID [1]: 0/1 Device ID [0]: 1-80; Device ID [1]: 0/1
RslSap
RslSap
11 6 0 11 6 0
Resetting HDLC for GPROC slot #, cage # RSL #. Possible T1/chnl problems Too many T7130/T711 5 fatal conditions for RSL #, resetting GPROC Temporarily disabling RSL #, bouncing HDLC. Possible T1/chnl problems Bouncing RSL on chn # mb #, possible T1/chn problems, not resetting HDLC EMPTY
Critical
EMPTY
EMPTY
Y C / l N e a r R N
Comments & Notes
U In the case where the HDLC Chip will be reset, this alarm will be seen
Critical
EMPTY
EMPTY
Critical
EMPTY
EMPTY
Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this RSL. If the condition persists, replace the GPROC. Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this RSL.
R N
U In the case where too may requests to reset the HDLC Chip have been received, this alarm will be printed and the GPROC will be reset U In the case where too many HDLC Chip resets have take place and a link needs to be temporarily disabled, this alarm will be displayed
R N
Critical
EMPTY
EMPTY
Possible T1 / DACS problems . Check BSC to EBTS physical connection as well as devices(GPROC/EGP, MSI, etc) controlling this RSL. The GPROC may need to be reset to recover the site.
R N
U In the case where the HDLC Chip is requested to be reset but the "lap_isr_fix_flag" is set to "off", in other words the chip reset is disabled, this alarm will be seen
Critical
OML: 0
OML:BU/D-U (31, 32, 39, 43) GPROC/EG PROC: DU/B-U(0), E-U/B-U(0); T1/E1: DU/B-U(0), E-L/B-U(0); MSI: D-U/BU(0); E-L/BU(0) EMPTY
Check the BSC to EBTS physical connection.
R N
U OML would affect SNMP
EMPTY
Minor
GPROC/EG PROC: 230; MSI: 230; T1/E1: 254
Indication that the link connected, investigate the cause of link bounce.
R N
U ( c ) stands for clear alarm
communicat
Device ID
RslSap
1-
site: %d,
Major
EMPTY
Indication that there are a high
R N
U EMPTY
BSC-32
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
ionFailureE vent
[0]: 1-80; Device ID [1]: 0/1 Link Traffic Too High Device ID [0]: 1-80; Device ID [1]: 0/1 RslSap
1 6 0 11 6 0
MOBIS alarm, RX Buffer Full site: %d, MOBIS alarm, TX Buffer Full . Throttling Page Reqs Major EMPTY EMPTY
1 3
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent communicat ionFailureE vent
Unexpected Msg
EMPTY
SITE
Unexpected Msg: %s EMPTY
Warning
EMPTY
EMPTY
number of messages being sent to the BSC by the EBTS. Find the source of messages and examine if it is a misconfiguration issue Indication that there are a high number of messages being sent by the BSC to the EBTS and buffers are getting full. SS7 congestion control will start controlling the traffic. Find the source of messages and examine if it is a misconfiguration issue EMPTY
Y C / l N e a r C
Comments & Notes
R N C
U EMPTY
R N
U EMPTY
OMC BSC Time Sync lost Alarm MSC Overload Alarm
EMPTY
SITE
Minor
OML: 0, 1
EMPTY
SITE
OLCC RC Was Used
EMPTY
SITE
Throttling LUs, Calls, IMSI Detaches, HOs EMPTY
Major
EMPTY
OML: BU/D-U(31, 32, 39, 43) EMPTY
Check BOML link. Lock/unlock BOML link to bring it back. Indication sent to the BSC that the MSC is overloaded. Find the source of the MSC overload and examine if it is a misconfiguration issue Investigate why a command or commands have been used in Recent Change mode after the last OLCC switcher BSC configuration creation from object #4, and do SYSGEN if necessary. Investigate why a command or commands failed during the previous OLCC switch or BSC configuration creation from object #4, and do SYSGEN if necessary. Investigate why a command or commands were rejected during the OLCC. It can be either wrong command syntax or resource conflict caused by a command in Recent Change mode or a command failed during the previous OLCC or BSC configuration creation from object None. System will disallow anymore automatic switchovers, unless an on-demand test is
R N C R N C
U EMPTY
U EMPTY
Warning
EMPTY
EMPTY
R N
OLCC Commands Failed
EMPTY
SITE
OLCC Commands Failed
EMPTY
SITE
Commands failed during previous OLCC or re-init Commands failed during OLCC
Warning
EMPTY
EMPTY
R N
U BSC database has been changed by MMI command in Recent Change mode. Alarm is reported at the beginning of OLCC switch. U The OMC's database might be different from the BSC's one. Alarm is reported at the beginning of OLCC switch. U The OMC's database might be different from the BSC's one. Alarm is reported at the end of OLCC switch.
Warning
EMPTY
EMPTY
R N
Max TDM Changeovers Reached
EMPTY
SITE
X(Y) TDM Changeove rs have
Major
TDM: 24, 25
EMPTY
R N C
U Note: X = the number of changeover have occurs so far, Y = the max
October 30, 2008
BSC-33

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r occurred initiated. Warning EMPTY EMPTY If XCDR card is configured for some slots but physically not present, inserting XCDR into those slots will provide more transcoding resources and may clear the alarm R N
Comments & Notes
VPs Usage Alarm
EMPTY
SITE
VPs Usage Alarm
EMPTY
SITE
EGP required
EMPTY
SITE
EGP required
EMPTY
SITE
EGP required
EMPTY
SITE
EGP required
EMPTY
SITE
VP utilization level for all VP types meets or exceeds the high watermark level of X% VP utilization level for all VP types meets or drops below the low watermark level of X% EGP Preferred MTL LCF # will be unassigned No EGP board available as a standby GPROC EGP Preferred LCF # is assigned to GPROC1 Board EGP Preferred OMF Requires an EGP Board EMPTY
number of changeover allowed U Alarm is set when the level of VP utilization exceeds the high watermark threshold configuration parameter. Indicates that additional VP resources should be added.
Clear
EMPTY
EMPTY
This CLEAR indication occurs when the usage drops the threshold
C N
U Alarm is cleared when the level of VP utilization falls below low watermark threshold configuration parameter.
Major
EMPTY
EMPTY
Major
EMPTY
EMPTY
Alarm code text will give the reason for raising the alarm. Insert an EGP board. The MTL LCF function should automatically be assigned to this board. Alarm code text will give the reason for raising the alarm. Insert an EGP board
R N C
U MTL LCF was not assigned to a GPROC due to unavailability of correct board type U There is no EGP as a standby GPROC in a BSC- Call Processor
R N C
Major
EMPTY
EMPTY
Alarm code text will give the reason for raising the alarm. Insert an EGP board and reassign the function to this EGP
R N C
"EGP preferred" LCF has been assigned to a GPROC1 board
Major
EMPTY
EMPTY
Alarm code text will give the reason for raising the alarm. Insert an EGP board and reassign the function to this EGP
R N C
2 5 4
Device Failed (T1/E1)
Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device
T1/E1
11 4 4
Critical
MSI: 231
EMPTY
Check the MSI card handling this T1/E1 device.
R N C
"EGP preferred" OMF on a BSC-Call Processor is assigned to a GPROC1. This alarm will only be seen on BSC-CP not on BSC-XCDR. U The MSI handling this T1/E1 might have been locked or reset.
BSC-34
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Remote KSWX TDM Error ID[1]: 0/1 Side: 0/1 TBUS 14 Check connections to KSWX RX port in Cage xx, slot yy Check connections to KSWX RX port in Cage xx, slot yy EMPTY Major EMPTY EMPTY Check fiber cable connections at both ends. Check both KSWX cards. Reconnect/replace if necessary. R N C
Comments & Notes
U EMPTY
Local KSWX TDM Error
Side: 0/1
TBUS
14
Major
EMPTY
EMPTY
R N C
U EMPTY
2 2 6
External Loopback Fail
Side: 0/1
TBUS
11 2
Critical
EMPTY
EMPTY
equipmentF ailureEvent communicat ionFailureE vent
2 5 4 0
Device Failed
Side: 0/1
TBUS
TDM Test Failed Path KSW 0 to KSW 1
Side: 0/1
TDM
11 2 12
EMPTY
Critical
EMPTY
EMPTY
If the alarm is for a TBUS in a cage without KSWs, check KSWX fiber cable connections at both ends. Reconnect/replace fibers or reseat/replace KSWXs if necessary. If the alarm is for a TBUS in a cage with KSWs, run the TDM connectivity test for that TDM side. If the TBUS remains disabled, check MCAP GPROC of the cage and KSW in the cage for that TDM side (perform safe tests). Replace if necessary. The troubleshooting guide has a strategy to identify MCAP GPROC problems (if one or more TDM problems are seen in a cage on both TDM sides, the MCAP GPROC is probably bad.) Check KSWX card and fiber.
R N
U EMPTY
R N
U EMPTY
Side: 0/1
TDM
12
KSWX connectivity fault[1], Cage 0 Slot y, Cage 1 Slot yy KSWX connectivity fault[5], Cage 0 Slot y,
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
Check connections of KSWX in cage 1 slot yy
R N C
U TDM Conn Test needed to be run to see this alarm
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
Replace KSWX in cage 1 slot yy
R N C
October 30, 2008
BSC-35

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Cage 1 Slot yy TDM connectivity fault[z], Cage 0 Slot y, Cage 1 Slot yy KSW not active[3], Cage 0 Slot y, Cage 1 Slot yy One active KSW[4], Cage 0 Slot y, Cage 1 Slot yy KSWX connectivity fault[1], Cage 1 Slot y, Cage 0 Slot yy KSWX connectivity fault[5], Cage 1 Slot y, Cage 0 Slot yy TDM connectivity fault[z], Cage 1 Slot y, Cage 0 Slot yy KSW not active[3], Cage 1 Slot y, Cage 0
Comments & Notes
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
Check active KSW in cage 0 and 1 status. Audit KSWs.
R N C
U The clear alarm for the listed related alarms on Active side will trigger TDM Conn Test to run. Then this alarm will be set or cleared depends if there is a fault. U EMPTY
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
U EMPTY
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
BSC-36
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r TDM Test Failed Path KSW 1 to KSW 0 Side: 0/1 TDM 12 Slot yy One active KSW[4], Cage 1 Slot y, Cage 0 Slot yy KSWX connectivity fault[1], Cage 0 Slot y, Cage 2 Slot yy KSWX connectivity fault[5], Cage 0 Slot y, Cage 2 Slot yy TDM connectivity fault[z], Cage 0 Slot y, Cage 2 Slot yy KSW not active[3], Cage 0 Slot y, Cage 2 Slot yy One active KSW[4], Cage 0 Slot y, Cage 2 Slot yy KSWX connectivity fault[1], Cage 2 Slot y, Cage 0 Slot yy Critical EMPTY EMPTY Check active KSW in cage 0 and 1 status. Audit KSWs. R N C
Comments & Notes
U EMPTY
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
U EMPTY
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
October 30, 2008
BSC-37

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
KSWX connectivity fault[5], Cage 2 Slot y, Cage 0 Slot yy TDM connectivity fault[z], Cage 2 Slot y, Cage 0 Slot yy KSW not active[3], Cage 2 Slot y, Cage 0 Slot yy One active KSW[4], Cage 2 Slot y, Cage 0 Slot yy KSWX connectivity fault[1], Cage 0 Slot y, Cage 3 Slot yy KSWX connectivity fault[5], Cage 0 Slot y, Cage 3 Slot yy TDM connectivity fault[z], Cage 0 Slot y, Cage 3 Slot yy
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
Comments & Notes
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Critical
EMPTY
EMPTY
R N C
Critical
EMPTY
EMPTY
R N C
U EMPTY
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
U The clear alarm for the listed related alarms on Active side will trigger TDM Conn Test to run. Then this alarm will be set or cleared depends if there is a fault.
BSC-38
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
Side: 0/1
TDM
12
KSW not active[3], Cage 0 Slot y, Cage 3 Slot yy One active KSW[4], Cage 0 Slot y, Cage 3 Slot yy KSWX connectivity fault[1], Cage 3 Slot y, Cage 0 Slot yy KSWX connectivity fault[5], Cage 3 Slot y, Cage 0 Slot yy TDM connectivity fault[z], Cage 3 Slot y, Cage 0 Slot yy KSW not active[3], Cage 3 Slot y, Cage 0 Slot yy One active KSW[4], Cage 3 Slot y, Cage 0 Slot yy KSWX connectivity
Critical
EMPTY
EMPTY
Comments & Notes
U EMPTY
Critical
EMPTY
EMPTY
R N C
U EMPTY
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Critical
EMPTY
EMPTY
R N C
Critical
EMPTY
EMPTY
R N C
U EMPTY
Critical
CAGE: 0, 1, 2, 3, 4, 5;
EMPTY
R N C
October 30, 2008
BSC-39

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r fault[1], Cage 1 Slot y, Cage 2 Slot yy KSWX connectivity fault[5], Cage 1 Slot y, Cage 2 Slot yy TDM connectivity fault[z], Cage 1 Slot y, Cage 2 Slot yy KSW not active[3], Cage 1 Slot y, Cage 2 Slot yy One active KSW[4], Cage 1 Slot y, Cage 2 Slot yy KSWX connectivity fault[1], Cage 2 Slot y, Cage 1 Slot yy KSWX connectivity fault[5], Cage 2 Slot y, Cage 1 Slot yy TDM connectivity KSW: 10, 11, 12, 13, 14, 15
Comments & Notes
vent
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
U EMPTY
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5;
EMPTY
R N C
U The clear alarm for the listed related alarms on
BSC-40
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r fault[z], Cage 2 Slot y, Cage 1 Slot yy KSW not active[3], Cage 2 Slot y, Cage 1 Slot yy One active KSW[4], Cage 2 Slot y, Cage 1 Slot yy KSWX connectivity fault[1], Cage 1 Slot y, Cage 3 Slot yy KSWX connectivity fault[5], Cage 1 Slot y, Cage 3 Slot yy TDM connectivity fault[z], Cage 1 Slot y, Cage 3 Slot yy KSW not active[3], Cage 1 Slot y, Cage 3 Slot yy One active KSW[4], Cage 1 KSW: 10, 11, 12, 13, 14, 15
Comments & Notes
vent
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
Active side will trigger TDM Conn Test to run. Then this alarm will be set or cleared depends if there is a fault. U EMPTY
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
U EMPTY
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
U EMPTY
October 30, 2008
BSC-41

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Slot y, Cage 3 Slot yy KSWX connectivity fault[1], Cage 3 Slot y, Cage 1 Slot yy KSWX connectivity fault[5], Cage 3 Slot y, Cage 1 Slot yy TDM connectivity fault[z], Cage 3 Slot y, Cage 1 Slot yy KSW not active[3], Cage 3 Slot y, Cage 1 Slot yy One active KSW[4], Cage 3 Slot y, Cage 1 Slot yy KSWX connectivity fault[1], Cage 2 Slot y, Cage 3 Slot yy KSWX connectivity fault[5], Cage 2
Comments & Notes
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
U EMPTY
1 0
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
1 0
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13,
EMPTY
Replace KSWX in cage 3 slot yy.
R N C
BSC-42
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Slot y, Cage 3 Slot yy TDM connectivity fault[z], Cage 2 Slot y, Cage 3 Slot yy KSW not active[3], Cage 2 Slot y, Cage 3 Slot yy One active KSW[4], Cage 2 Slot y, Cage 3 Slot yy KSWX connectivity fault[1], Cage 3 Slot y, Cage 2 Slot yy KSWX connectivity fault[5], Cage 3 Slot y, Cage 2 Slot yy TDM connectivity fault[z], Cage 3 Slot y, Cage 2 Slot yy KSW not active[3], Cage 3 Slot y, 14, 15
Comments & Notes
1 0
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
R N C
1 0
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
1 0
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
U EMPTY
1 1
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
Check connections of KSWX in cage 2 slot yy.
R N C
1 1
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
Replace KSWX in cage 2 slot yy.
R N C
1 1
Side: 0/1
TDM
12
Critical
CAGE: 0, 1, 2, 3, 4, 5; KSW: 10, 11, 12, 13, 14, 15
EMPTY
Check connections of KSWX in cage 2 slot yy.
R N C
1 1
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
October 30, 2008
BSC-43

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Cage 2 Slot yy One active KSW[4], Cage 3 Slot y, Cage 2 Slot yy Test Aborted [z], Cage 0 Slot y, Cage 1 Slot yy Test Aborted [z], Cage 1 Slot y, Cage 0 Slot yy Test Aborted [z], Cage 0 Slot y, Cage 2 Slot yy Test Aborted [z], Cage 2 Slot y, Cage 0 Slot yy Test Aborted [z], Cage 0 Slot y, Cage 3 Slot yy Test Aborted [z], Cage 3 Slot y, Cage 0 Slot yy Test Aborted [z], Cage 1
Comments & Notes
1 1
Side: 0/1
TDM
12
Critical
EMPTY
EMPTY
R N C
U EMPTY
1 2
TDM Test Aborted Path KSW 0 to KSW 1
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
Test aborted. TDM path from cage 0 to 1 is still in service.
R N C
1 3
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
1 4
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
1 5
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
1 6
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
1 7
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
1 8
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
BSC-44
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Slot y, Cage 2 Slot yy Test Aborted [z], Cage 2 Slot y, Cage 1 Slot yy Test Aborted [z], Cage 1 Slot y, Cage 3 Slot yy Test Aborted[z], Cage 3 Slot y, Cage 1 Slot yy Test Aborted [z], Cage 2 Slot y, Cage 3 Slot yy Test Aborted[z], Cage 3 Slot y, Cage 2 Slot yy TDM Highway is xx% operable
Comments & Notes
1 9
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
2 0
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
2 1
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
2 2
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
2 3
Side: 0/1
TDM
12
Warning
EMPTY
EMPTY
R N C
2 4
A Side TDM Highway Impaired
Side: 0
TDM
Warning
CAGE: 3, 4, 5, 7, 13, 14, 15, 16, 17; KSW: 8, 13, 14, 15, 230, 231, 254; TBUS: 0, 1; TDM:0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11;
KSW: BU/D-U(22, 24, 25), BU/E-L(0), BU/E-U(28), E-U/B-U(0), E-L/B-U(0), E-U/DU(22, 24, 25), E-U/EL(0); TBUS: D-U/B-U(0), E-U/B-U(0), B-U/D-
Maintenance required on A-Side TDM Highway when less than 100% operable
R N C
U EMPTY
October 30, 2008
BSC-45

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r U(22, 24, 29), E-U/DU(22, 24, 29), B-U/EL(0), E-L/EU(0), E-L/BU(0), BU/E-U(28) KSW: BU/D-U(22, 24, 25), BU/E-L(0), BU/E-U(28), E-U/B-U(0), E-L/B-U(0), E-U/DU(22, 24, 25), E-U/EL(0); TBUS: D-U/B-U(0), E-U/B-U(0), B-U/DU(22, 24, 29), E-U/DU(22, 24, 29), B-U/EL(0), E-L/EU(0), E-L/BU(0), BU/E-U(28) EMPTY
Comments & Notes
2 5
B Side TDM Highway Impaired
Side: 1
TDM
TDM Highway is xx% operable
Warning
CAGE: 0, 1, 2, 6, 8, 9, 10, 11, 12; KSW:8, 10, 11, 12, 230, 231, 254; TBUS: 0, 1; TDM:0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11;
Maintenance required on B-Side TDM Highway when less than 100% operable
R N C
U EMPTY
Link Timeout
Device ID: 0-31
XBL
13 2
EMPTY
Critical
EMPTY
Sequence Error
Device ID: 0-31
XBL
13 2
EMPTY
Minor
EMPTY
EMPTY
Frame Rejected
Device ID: 0-31
XBL
13 2
EMPTY
Minor
EMPTY
EMPTY
Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc)
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
BSC-46
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Unexpected Response Frame Device ID: 0-31 XBL 13 2 EMPTY Minor EMPTY EMPTY controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and R N
Comments & Notes
U EMPTY
Bad Configuration
Device ID: 0-31
XBL
13 2
EMPTY
Indetermina te
EMPTY
EMPTY
R N
U EMPTY
Unexpected SABME Received
Device ID: 0-31
XBL
13 2
EMPTY
Critical
EMPTY
EMPTY
R N
U EMPTY
Bad Frame
Device ID: 0-31
XBL
13 2
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Link SABME Failed
Device ID: 0-31
XBL
13 2
EMPTY
Critical
EMPTY
EMPTY
R N
U EMPTY
Link Disconnect Failed
Device ID: 0-31
XBL
13 2
EMPTY
Critical
EMPTY
Device ID: 0-31
XBL
13 2
XBL Keep Alive Failed
Critical
EMPTY
MSI: B-U/DU(22, 24, 25), B-U/EL(0); T1/E1: B-U/DU(24, 30), B-U/E-L(0) EMPTY
R N
U EMPTY
R N
U EMPTY
Device ID: 0-31
XBL
13 2
Link Disconnect ed, T7130
Critical
EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
BSC-47

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Device Halted RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL. Possible T1 / DACS problems. Check BSC to RXCDR physical connection. Check BSC and RXCDR status as well as devices (GPROC/EGP, MSI, etc) controlling this XBL.
Comments & Notes
Device ID: 0-31
XBL
13 2
Possible one way XBL, bouncing link Restarted XBL due to failure to recover this HDLC channel EMPTY
Critical
EMPTY
EMPTY
R N
U EMPTY
Device ID: 0-31
XBL
13 2
Critical
EMPTY
EMPTY
R N
U EMPTY
1 0
Link Disconnected
Device ID: 0-31
XBL
13 2
Critical
EMPTY
EMPTY
R N
U EMPTY
1 1
Link Connected
Device ID: 0-31
XBL
13 2
EMPTY
Minor
GPROC/EG PROC: 230; MSI: 230; T1/E1: 254 (C)
1 2 1 3
XCDR Initialized
XCDR
XCDR Reset
XCDR
15 5 15 5 15 5
EMPTY
Critical
XCDR: 13
1 4
Cage: 0-5; Slot: 6-24
XCDR
XCDR IRR Value is ##, ISR Value is ## XCDR IRR Value is ##, ISR Value is ##
Critical
EMPTY
GPROC/EG PROC: DU/B-U(0), E-U/B-U(0); T1/E1: DU/B-U(0), E-L/B-U(0); MSI: D-U/BU(0), E-L/BU(0) XCDR: DU/B-U(0), D-L/B-U(0) XCDR: BU/D-U(22, 24, 25) XCDR: BU/D-U(22, 24, 25)
R N
U ( c ) stands for clear alarm
No action required
R N
R N
U Informational alarm, a XCDR has just been inserted. U If this alarm occurs continuously, replace the board U If this alarm occurs continuously, replace the board. If the board does not recover, this problem could be because of a bad GCLK. U If many boards report the same alarm, reseat or replace the Local KSWX
Critical
XCDR: 13
R N
1 5
TDM Clock B Failure
Cage: 0-5; Slot: 6-24
XCDR
15 5
XCDR IRR Value is ##, ISR Value
Major
CBUS: 0, 1, 2, 3
GCLK: BU/D-U(25)
R N
BSC-48
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r TDM Clock A Failure Cage: 0-5; Slot: 6-24 XCDR 15 5 15 5 is ## XCDR IRR Value is ##, ISR Value is ## XCDR IRR Value is ##, ISR Value is ## Major CBUS: 0, 1, 2, 3 GCLK: BU/D-U(25) Check the Local KSWX on the B side R N
Comments & Notes
1 6
1 7
Assigned Timeslot Counter Underflow
Cage: 0-5; Slot: 6-24
XCDR
Critical
CBUS: 1, 3
EMPTY
No action required
R N C
1 8
Assigned Timeslot Counter Overflow
Cage: 0-5; Slot: 6-24
XCDR
15 5
XCDR IRR Value is ##, ISR Value is ##
Critical
CBUS: 1, 3
EMPTY
No action required
R N C
1 9
TDM Parity Error
Cage: 0-5; Slot: 6-24
XCDR
15 5 15 5
1 9
TDM Parity Error
Cage: 0-5; Slot: 6-24
XCDR
1 9
TDM Parity Error
Cage: 0-5; Slot: 6-24
XCDR
15 5
2 2
XCDR Wrong Board Type
Cage: 0-5; Slot: 6-24
XCDR
15 5
2 2
Cage: 0-5; Slot: 6-24
XCDR
15 5
2 2
Cage: 0-5; Slot: 6-24
XCDR
15 5
XCDR IRR Value is ##, ISR Value is ## TDM Parity errors reported on X of Y timeslots TDM Parity errors reported on all Y timseslots HXCDR board type inserted in 48 channel configured slot HXCDR board type inserted in 72 channel configured slot HXCDR board type inserted in 96 channel
Major
CBUS: 0, 1, 2, 3; XCDR: 231 CBUS: 0, 1, 2, 3; XCDR: 231
EMPTY
Execute the tdm_conn_test command to isolate the cause of the alarm Execute the tdm_conn_test command to isolate the cause of the alarm
R N C
cards. U If many boards report the same alarm, reseat or replace the Local KSWX cards. U Alarm is self correcting, if there are no parity errors, the device will be disabled. A reset or replacement might be required to bring the card back into service. U Alarm is self correcting, if there are no parity errors, the device will be disabled. A reset or replacement might be required to bring the card back into service. U EMPTY
Major
EMPTY
R N C
U EMPTY
Major
CBUS: 0, 1, 2, 3; XCDR: 231
EMPTY
Execute the tdm_conn_test command to isolate the cause of the alarm
R N C
U EMPTY
Major
EMPTY
EMPTY
Replaced board with iXCDR or GXCDR. If slot is configured for 48 channel AMBE+ 2, replace board with GXCDR.
R N
U EMPTY
Major
EMPTY
EMPTY
Replaced board with GXCDR.
R N
U EMPTY
Major
EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
BSC-49

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r configured slot iXCDR board type inserted in 48 channel AMBE+2 configured slot iXCDR board type inserted in 72 channel configured slot iXCDR board type inserted in 96 channel configured slot GXCDR board type inserted in 24 channel configured slot DSP 'id' ('vp type') (XCDR 'xcdr id' ('xcdr type') /CAGE 'cage id' /SLOT 'slot id'): Failed DSP Swap Wrong bus(es): MCAP TDM Clock MCAP timeout
Comments & Notes
2 2
Cage: 0-5; Slot: 6-24
XCDR
15 5
Major
EMPTY
EMPTY
R N
U EMPTY
2 2
Cage: 0-5; Slot: 6-24
XCDR
15 5
Major
EMPTY
EMPTY
R N
U EMPTY
2 2
Cage: 0-5; Slot: 6-24
XCDR
15 5
Major
EMPTY
EMPTY
R N
U EMPTY
2 2
Cage: 0-5; Slot: 6-24
XCDR
15 5
Major
EMPTY
EMPTY
Replaced board with HXCDR or iXCDR.
R N
U EMPTY
2 3
DSP Swap Fail
Cage: 0-5; Slot: 6-24
XCDR
15 5
Warning
EMPTY
EMPTY
No action required
R N
U Note: vp_ type: VSELP_ 3TO1, VSELP_ 6TO1, or AMBE_ 6TO1. xcdr type: 24_ CHAN and 48_ CHAN. If this alarm occurs several times for the same card, reset or replace the board.
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 6-24
XCDR
15 5
Warning
EMPTY
EMPTY
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 6-24
XCDR
15 5
Warning
GPROC/EG PROC: 232; XCDR: 228
EMPTY
Board maybe on a wrong bus. Lock/Unlock the board to initialize the board to the proper active buses. If problem persists, replace the board. MCAP Timeout could mean that either XCDR or the MCAP GPROC for the cage is faulty. Run safe test on the MCAP GPROC. If it fails then, run the
R N
U EMPTY
R N
U EMPTY
BSC-50
October 30, 2008
Release SR17.0
Alarm Type
A l a r m C o d e

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r safe test on the MCAP GPROC again and check the sanity of the cage. If it passes, run safe test 3 times on the XCDR. If all these 3 safe test fails, software will automatically reset the XCDR during the maintenance window and it will correct itself. Execute the remedy for the previously reported Safe Test Fail alarms for the same device.
Comments & Notes
2 2 4
Safe Test Fail
Cage: 0-5; Slot: 6-24
XCDR
15 5
EMPTY
Major
GPROC/EG PROC: 232; XCDR: 228
EMPTY
R N
2 2 8
Status Fail
Cage: 0-5; Slot: 6-24
XCDR
15 5
2 3 0 2 3 1 2 5 4 2 0
Board Inserted
XCDR
Board Removed
XCDR
15 5 15 5 15 5 15 5
TXQ_JAM MED condition is hit. RXQ_RUN AWAY condition is hit. Mailbox is locked EMPTY
Major
EMPTY
EMPTY
Front-panel reset the XCDR
R N
U When Safe Test Fail alarm for this device is reported consecutively for 5 times, there will be a "Major" alarm raised along with the 5th alarm for the same device. U EMPTY
Clear
EMPTY
Critical
Device Failed
XCDR
EMPTY
Critical
Voice Trunk Test Fail
XCDR, VP
VP 'id' ('vp type') (XCDR 'xcdr id' ('xcdr type') /CAGE 'cage id' /SLOT 'slot id'): Failed Audit (energy = <number>, <number>)
Major
XCDR: 10, 12, 14, 17, 18, 19, 224 EMPTY
No action required
R N
R N
U When MCAP GPROC comes back or card is inserted. U When MCAP GPROC switches over or card is pulled out. U When MCAP GPROC switches over or card is pulled out. U Note: vp_ type: VSELP_ 3TO1, VSELP_ 6TO1, or AMBE_ 6TO1. xcdr type: 24_ CHAN , 48_ CHAN, 72_CHAN, 96_CHAN number: a number in range from 2147483648 to 2147483647.
No action required
R N
EMPTY
If there is only 1 VP fails on VTT, block it out and monitor that card for any further issues with any other VPs. If there are multiple VPs on the same card failing constantly, then replace it.
R N C
October 30, 2008
BSC-51

Alarm Type
A l a r m C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
2 1
VTT Audit Fails for All VPs
Cage: 0-5; Slot: 6-24
XCDR, VP
15 5
ALL VPs on (XCDR 'xcdr id' ('xcdr type') /CAGE 'cage id' /SLOT 'slot id'): Failed Audit
Major
EMPTY
EMPTY
Possibly bad XCDR board. Lock/Unlock XCDR card.
Comments & Notes
U Note: vp_ type: VSELP_ 3TO1, VSELP_ 6TO1, or AMBE_ 6TO1. xcdr type: 24_ CHAN and 48_ CHAN. If this alarm occurs several times for the same card, reset or replace the board.
BSC-52
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
BSC State Change
No reason
Cage 0-5
CAGE
1-6
D-U
B-U
GPROC/EGPROC: D-U/BU ( 0 ), D-L/E-L ( 23, 24 ), D-U/E-U ( 28 ) GPROC/EGPROC: E-U/DU ( 23, 24 ), E-L/D-L ( 0 ), B-U/D-U ( 23, 24 ) EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY
GPROC/EGPRO C: 230
No Reason
S t a t u s N U
BSC State Change
1 6
MCAP RECOVERY FAILURE MCAP FAIL INITIALIZATI ON ERROR NO ACTIVE KSW NO ACTIVE CBUS NO ACTIVE PBUS NO ACTIVE SBUS NO ACTIVE POWER SUPPLIES No reason
Cage 0-5
CAGE
1-6
B-U
D-U
GPROC/EGPRO C: 231, 232, 254
Cannot recover MCAP (no available GPROC) MCAP DLSP GPROC failure Initialization Error No active KSW found No active CLOCK BUS found No active MCAP BUS found No active SERIAL BUS found No power supplies (BCUP) found No Reason
N U
BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
1 8 1 7 1 9 5 5 5 6 5 7 5 8 0
Cage 0-5 Cage 0-5 Cage 0-5 Cage 0-5 Cage 0-5 Cage 0-5 Cage 0-5
CAGE CAGE CAGE CAGE CAGE CAGE CAGE
1-6 1-6 1-6 1-6 1-6 1-6 1-6
D-U D-U D-U D-U D-U D-U D-U
D-U D-U D-U D-U D-U D-U D-U
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY
N U N U N U N U N U N U N U
MCAP GPROC is transitioning in the Related State Changes and Alarms columns. MCAP GPROC is transitioning in the Related State Changes and Alarms columns. EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY
Cage 0-5; Slot 18-25
GPROC / EGPROC
1-32
D-U
B-U
GPROC/EGPROC: D-U/BU ( 0 ), D-L/E-L ( 23, 24 ), D-U/E-U ( 28 ) EMPTY EMPTY EMPTY EMPTY EMPTY
GPROC/EGPRO C: 230
N U
BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
2 3 2 3 2 3 2 4 2 4
GPROC LAN ERROR GPROC LAN ERROR GPROC LAN ERROR ALARM ALARM
Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25
GPROC / EGPROC GPROC / EGPROC GPROC / EGPROC GPROC / EGPROC GPROC / EGPROC
1-32 1-32 1-32 1-32 1-32
B-U E-U E-L B-U E-U
D-U D-U D-L D-U D-U
EMPTY EMPTY EMPTY EMPTY EMPTY
GPROC LAN Alarms Reported GPROC LAN Alarms Reported No Reason Alarm detected on device Alarm detected on device
N U N U N U N U N U
MCAP GPROC is transitioning in the Related State Changes and Alarms columns. EMPTY EMPTY A locked card was disabled with it's front panel switch EMPTY EMPTY
October 30, 2008
BSC-53

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
BSC State Change BSC State Change
2 4 1 7
ALARM INITIALIZATI ON ERROR
Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25
GPROC / EGPROC GPROC / EGPROC
1-32 1-32
E-L D-U
D-L D-U
EMPTY EMPTY
EMPTY GPROC/EGPRO C: 232
No Reason Initialization Error
S t a t u s N U
N U
BSC State Change BSC State Change BSC State Change BSC State Change
1 9 2 0 2 1 2 2
NO ACTIVE KSW NO KSW ERROR GPROC NOT FOUND PARENT CAGE OOS
Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25
GPROC / EGPROC GPROC / EGPROC GPROC / EGPROC GPROC / EGPROC
1-32 1-32
D-U D-U
D-U D-U
EMPTY EMPTY
EMPTY EMPTY
No active KSW found Failed configure timeslots due to no active KSW Cannot find GPROC (check if card is in slot) Parent Cage is Out of Service
N U N U
A locked card was disabled with it's front panel switch An Initialization error can occur when a GPROC/EGPROC that is coming up cannot register with the CA process to update CA's router tables. Either the BSP (or the CA process) is not up or the GPROC/EGPROC cannot communicate on the MCAP bus. EMPTY EMPTY
1-32
D-U
D-U
EMPTY
EMPTY
N U
EMPTY
1-32
D-U
D-U
2 7 2 8
WRONG CARD TYPE ERROR STANDBY DEVICE
GPROC / EGPROC GPROC / EGPROC
1-32
D-U
D-U
GPROC/EGPROC: E-U/DU ( 23, 24 ), E-L/D-L ( 0 ), B-U/D-U ( 23, 24 ); CBUS: B-U/D-U ( 61 ) EMPTY
GPROC/EGPRO C:231, 232, 254; CBUS: 1, 2, 3, 4, 224 EMPTY
N U
Wrong Card Type Found in Slot Device is a Standby Device
N U
MCAP GPROC is transitioning in the Related State Changes and Alarms columns. EMPTY
1-32
D-U
E-U
GPROC/EGPROC: D-U/BU ( 0 ), D-U/E-U ( 28 )
GPROC/EGPRO C: 230
N U
BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
0 0 0 0 0 0
No reason No reason No reason No reason No reason No reason
Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25 Cage 0-5; Slot 18-25
GPROC / EGPROC GPROC / EGPROC GPROC / EGPROC GPROC / EGPROC GPROC / EGPROC GPROC / EGPROC
1-32 1-32 1-32 1-32 1-32 1-32
D-U D-L B-U E-L E-U E-U
D-L D-U E-L E-U E-L B-U
EMPTY EMPTY EMPTY EMPTY EMPTY GPROC/EGPROC: B-U/DU ( 23, 24 )
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY
No Reason No Reason No Reason No Reason No Reason No Reason
N U N U N U N U N U N U
MCAP GPROC is transitioning in the Related State Changes and Alarms columns. Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Operator LOCKED device LCF/OMF GPROC was disabled, the LCF/OMF process moves to this (standby) GPROC
BSC-54
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
BSC State Change
No reason
GPROC / EGPROC
1-32
D-L
E-L
GPROC/EGPROC: D-U/BU ( 0 ), D-U/E-U ( 28 ); CBUS: D-U/B-U ( 0 )
GPROC/EGPRO C: 230
No Reason
S t a t u s N U
0 0
No reason No reason
GPROC / EGPROC KSW
1-32 1-8
E-L D-U
D-L B-U
EMPTY GPROC/EGPROC: D-U/BU ( 0 ), D-U/E-U ( 28 ); CBUS: D-U/B-U ( 0 ) KSW: B-U/D-U ( 22, 25 ), B-U/E-L ( 0 )
EMPTY KSW: 230
No Reason No Reason
N U N U
BSC State Change
No reason
KSW
1-8
E-U
B-U
KSW: 231, 232, 254
No Reason
N U
BSC State Change
1 7
INITIALIZATI ON ERROR
Cage 0-5; Slot 1/27
KSW
1-8
D-U
D-U
EMPTY
MCAP GPROC/EGPRO C: 232; CBUS Alarms: 0, 1, 2, 3, 5
Initialization Error
N U
2 7 2 2
WRONG CARD TYPE ERROR PARENT CAGE OOS
Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27
KSW
1-8
D-U
D-U
EMPTY
EMPTY
Wrong card type found in a slot Parent Cage is Out of Service
N U
Device is ENABLED, possibly because CAGE comes up. MCAP GPROC is transitioning in the Related State Changes and Alarms column. A locked card was disabled with it's front panel switch System moved device to BUSY. MCAP GPROC is transitioning in the Related State Changes Column. System moved device to BUSY. Active side KSW is transitioning or producing alarms. If KSW could not register with MCAP DLSP or both the ACTIVE and STANDBY CBUS are down, the KSW will report an initialization error. MCAP GPROC is transitioning in the Related Alarms column. EMPTY
KSW
1-8
E-L
D-L
GPROC/EGPROC: E-U/DU ( 23, 24 ), E-L/D-L ( 0 ), B-U/D-U ( 23, 24 ); CBUS: B-U/D-U ( 61 ) EMPTY GPROC/EGPROC: E-U/DU ( 23, 24 ), E-L/D-L ( 0 ), B-U/D-U ( 23, 24 ); CBUS: B-U/D-U ( 61 )
GPROC/EGPRO C:231, 232; CBUS: 1, 2, 3, 4, 224 EMPTY GPROC/EGPRO C:231, 232; CBUS: 1, 2, 3, 4, 224
N U
2 2 2 2
PARENT CAGE OOS PARENT CAGE OOS
Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27
KSW KSW
1-8 1-8
D-U B-U
D-U D-U
Parent Cage is Out of Service Parent Cage is Out of Service
N U N U
A Parent cage will go down if there is no MCAP bus. MCAP GPROC is transitioning in the Related State and Alarms column. EMPTY A Parent cage will go down if there is no MCAP bus. MCAP GPROC is transitioning in the Related State Changes and Alarms columns. A Parent cage will go down if there is no MCAP bus. MCAP GPROC is transitioning in the Related State and Alarms column. EMPTY
BSC State Change
2 2
PARENT CAGE OOS
Cage 0-5; Slot 1/27
KSW
1-8
E-U
D-U
GPROC/EGPRO C:231, 232; CBUS: 1, 2, 3, 4, 224 EMPTY
Parent Cage is Out of Service
N U
BSC State
BOARD OUT
Cage 0-5; Slot
KSW
1-8
E-L
D-L
Board
N U
October 30, 2008
BSC-55

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
5 2 5 2 5 2 5 2 4 2 4 2 4 2 8 2 8
OF CAGE BOARD OUT OF CAGE BOARD OUT OF CAGE BOARD OUT OF CAGE ALARM ALARM ALARM STANDBY DEVICE STANDBY DEVICE
1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 KSW 1-8 D-U D-U EMPTY EMPTY
KSW
1-8
B-U
D-U
EMPTY
EMPTY
KSW
1-8
E-U
D-U
EMPTY
EMPTY
KSW KSW KSW KSW
1-8 1-8 1-8 1-8
E-L B-U E-U D-U
D-L D-U D-U E-U
EMPTY EMPTY EMPTY GPROC/EGPROC: D-U/BU ( 0 ), D-U/E-U ( 28 ); CBUS: D-U/B-U ( 0 ) KSW: B-U/D-U ( 22, 25 ), B-U/E-L ( 0 )
EMPTY EMPTY EMPTY KSW: 230
removed/missing from cage Board removed/missing from cage Board removed/missing from cage Board removed/missing from cage Alarm detected on device Alarm detected on device Alarm detected on device Device is a Standby Device Device is a Standby Device
N U
EMPTY
N U
EMPTY
N U
EMPTY
N U N U N U N U
EMPTY EMPTY EMPTY MCAP GPROC is transitioning in the Related State Changes column. KSW in Related State Change column is on the same side, but in a different cage. Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Device is ENABLED This TBUS is now the active TBUS. Parent KSW or Active TBUS is transitioning in Related State Changes column. This TBUS is now the
KSW
1-8
B-U
E-U
KSW: 231, 232, 254
N U
BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
2 8 0 0 0 0 0 0 0 0
STANDBY DEVICE No reason No reason No reason No reason No reason No reason No reason No reason
Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5; Slot 1/27 Cage 0-5
KSW KSW KSW KSW KSW KSW KSW KSW TBUS
1-8 1-8 1-8 1-8 1-8 1-8 1-8 1-8 1-12
E-L D-U D-L B-U E-L E-U E-L D-L D-U
E-U D-L D-U E-L E-U E-L B-U E-L B-U
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY CAGE: D-U/B-U ( 0 ) KSW: D-U/B-U ( 0 ); TBUS B-U/E-L ( 0 )
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY KSW: 230 EMPTY
Device is a Standby Device No Reason No Reason No Reason No Reason No Reason No Reason No Reason No Reason
N U N U N U N U N U N U N U N U N U
BSC State
No reason
Cage 0-5
TBUS
1-12
E-U
B-U
TBUS B-U/E-L ( 0 ); KSW:
EMPTY
No Reason
N U
BSC-56
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Change
B-U/E-L ( 0 ), B-U/D-U ( 22, 25 )
2 9 2 9 2 9 2 2
PARENT KSW OOS PARENT KSW OOS PARENT KSW OOS PARENT CAGE OOS
Cage 0-5
TBUS
1-12
B-U
D-U
KSW: B-U/E-L ( 0 ), B-U/DU ( 22, 25 ) KSW: E-U/D-U, E-U/E-L
KSW: 231, 254
Parent KSW is Out of Service Parent KSW is Out of Service Parent KSW is Out of Service Parent Cage is Out of Service
N U
Cage 0-5
TBUS
1-12
E-U
D-U
KSW: 231, 254
N U
Cage 0-5
TBUS
1-12
D-U
D-U
Cage 0-5
TBUS
1-12
B-U
D-U
BSC State Change
2 2
PARENT CAGE OOS
Cage 0-5
TBUS
1-12
E-U
D-U
BSC State Change
2 2
PARENT CAGE OOS
Cage 0-5
TBUS
1-12
D-U
D-U
2 8 2 8
STANDBY DEVICE STANDBY DEVICE
Cage 0-5 Cage 0-5
TBUS TBUS
1-12 1-12
D-U B-U
E-U E-U
KSW: B-U/E-L ( 0 ), B-U/DU ( 22, 24, 25 ), E-U/D-U (22, 24, 25 ) GPROC/EGPROC: E-U/DU ( 23, 24 ), E-L/D-L ( 0 ), B-U/D-U ( 23, 24 ); CBUS: B-U/D-U ( 61 ); CAGE: BU/D-U ( 16 ) GPROC/EGPROC: E-U/DU ( 23, 24 ), E-L/D-L ( 0 ), B-U/D-U ( 23, 24 ); CBUS: B-U/D-U ( 61 ); CAGE: BU/D-U ( 16 ) GPROC/EGPROC: E-U/DU ( 23, 24 ), E-L/D-L ( 0 ), B-U/D-U ( 23, 24 ); CBUS: B-U/D-U ( 61 ); CAGE: BU/D-U ( 16 ) KSW: D-U/E-U ( 28 ), EL/E-U ( 0 ) TBUS: B-U/E-U ( 28 ), BU/D-U ( 22, 24, 29 ); KSW: B-U/E-L (0 ), B-U/D-U ( 22, 24, 25 )
KSW: 231, 254
N U
active TBUS. Active KSW or Active TBUS is transitioning in Related State Changes column. Active KSW is transitioning in Related State Changes column Standby KSW is transitioning in the Related State Changes column EMPTY
GPROC/EGPRO C:231, 232; CBUS: 1, 2, 3, 4, 224 GPROC/EGPRO C:231, 232; CBUS: 1, 2, 3, 4, 224 GPROC/EGPRO C:231, 232; CBUS: 1, 2, 3, 4, 224 EMPTY TDM: 24, 25; CAGE: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17; KSW: 10, 11,12, 13, 14, 15, 231, 232, 254; TBUS: 0, 1 EMPTY EMPTY EMPTY EMPTY
N U
MCAP GPROC is transitioning in the Related State Changes and Alarms columns. MCAP GPROC is transitioning in the Related State Changes and Alarms columns. MCAP GPROC is transitioning in the Related State Changes and Alarms columns. EMPTY EMPTY
N U
N U
Device is a Standby Device Device is a Standby Device
N U N U
0 0 0 0
No reason No reason No reason No reason
Cage 0-5 Cage 0-5 Cage 0-5 Cage 0-5
TBUS TBUS TBUS TBUS
1-12 1-12 1-12 1-12
D-U D-L B-U E-L
D-L D-U E-L E-U
EMPTY EMPTY EMPTY EMPTY
No Reason No Reason No Reason No Reason
N U N U N U N U
Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device
October 30, 2008
BSC-57

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
0 0 0 0 6 2 6 2 6 2 6 3
No reason No reason No reason No reason REMOTE KSWX TDM ALARM REMOTE KSWX TDM ALARM REMOTE KSWX TDM ALARM REMOTE KSWX COMMUNIC ATION FAILURE REMOTE KSWX COMMUNIC ATION FAILURE REMOTE KSWX COMMUNIC ATION FAILURE LOCAL KSWX TDM ALARM LOCAL KSWX TDM ALARM LOCAL KSWX TDM ALARM LOCAL KSWX COMMUNIC ATION FAILURE
Cage 0-5 Cage 0-5 Cage 0-5 Cage 0-5 Cage 0-5
TBUS TBUS TBUS TBUS TBUS
1-12 1-12 1-12 1-12 1-12
E-U E-L E-L D-L B-U
E-L B-U D-L E-L D-U
EMPTY EMPTY EMPTY EMPTY TBUS: 0
No Reason No Reason No Reason No Reason Remote KSWX RX fiber port is showing problems Remote KSWX RX fiber port is showing problems Remote KSWX RX fiber port is showing problems Remote KSWX card is either failed or missing from cage
S t a t u s N U N U N U N U N U
Operator LOCKED device Operator UNLOCKED device Device is DISABLED Device is ENABLED Check Remote KSWX TDM RX port fiber connections Check Remote KSWX TDM RX port fiber connections Check Remote KSWX TDM RX port fiber connections Cannot poll status Remote KSWX, Board is missing or faulty.
Cage 0-5
TBUS
1-12
E-U
D-U
EMPTY
TBUS: 0
N U
Cage 0-5
TBUS
1-12
D-U
D-U
EMPTY
TBUS: 0
N U
Cage 0-5
TBUS
1-12
B-U
D-U
EMPTY
CAGE: 8, 9, 10, 11, 12, 13, 14, 15, 16, 17; TBUS: 1 CAGE: 8, 9, 10, 11, 12, 13, 14, 15, 16, 17; TBUS: 1 CAGE: 8, 9, 10, 11, 12, 13, 14, 15, 16, 17; TBUS: 1 TBUS: 1
N U
BSC State Change
6 3
Cage 0-5
TBUS
1-12
E-U
D-U
EMPTY
Remote KSWX card is either failed or missing from cage
N U
Cannot poll status Remote KSWX, Board is missing or faulty.
BSC State Change
6 3
Cage 0-5
TBUS
1-12
D-U
D-U
EMPTY
Remote KSWX card is either failed or missing from cage
N U
6 4 6 4 6 4 6 5
Cage 0-5
TBUS
1-12
B-U
D-U
EMPTY
Cage 0-5
TBUS
1-12
E-U
D-U
EMPTY
TBUS: 1
Cage 0-5
TBUS
1-12
D-U
D-U
EMPTY
TBUS: 1
Cage 0-5
TBUS
1-12
B-U
D-U
EMPTY
CAGE: 6, 7; CBUS: 1; TBUS: 0
Local KSWX RX fiber port is showing problems Local KSWX RX fiber port is showing problems Local KSWX RX fiber port is showing problems Local KSWX card is either failed or missing from cage
N U
Check Local KSWX TDM RX port fiber connections Check Local KSWX TDM RX port fiber connections Check Local KSWX TDM RX port fiber connections Cannot poll status Remote KSWX, Board is missing or faulty.
N U
N U
N U
BSC-58
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
BSC State Change
6 5
BSC State Change
6 5
6 6 6 6 6 6 0
LOCAL KSWX COMMUNIC ATION FAILURE LOCAL KSWX COMMUNIC ATION FAILURE FAILED LOOPBACK TEST FAILED LOOPBACK TEST FAILED LOOPBACK TEST No reason
Cage 0-5
TBUS
1-12
E-U
D-U
EMPTY
Local KSWX card is either failed or missing from cage
S t a t u s N U
Cage 0-5
TBUS
1-12
D-U
D-U
EMPTY
Local KSWX card is either failed or missing from cage
N U
Cage 0-5
TBUS
1-12
B-U
D-U
EMPTY
EMPTY
Cage 0-5
TBUS
1-12
E-U
D-U
EMPTY
EMPTY
Cage 0-5
TBUS
1-12
D-U
D-U
EMPTY
EMPTY
Cage 0-5; Slot 6-24
XCDR
0-55
D-U
B-U
BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
1 7 2 2 2 5 2 7 4 5 2 2
INITIALIZATI ON ERROR PARENT CAGE OOS BOARD OUT OF CAGE WRONG CARD TYPE ERROR WRONG XCDR TYPE ERROR PARENT CAGE OOS
Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24
XCDR XCDR
0-55 0-55
D-U D-U
D-U D-U
GPROC/EGPROC: D-U/BU ( 0 ), D-U/E-L ( 0 ), DU/E-U ( 28 ); CBUS: DU/B-U ( 0 ) EMPTY EMPTY
XCDR:230
External loopback failed, check KSWX cards and fibers External loopback failed, check KSWX cards and fibers External loopback failed, check KSWX cards and fibers No Reason
N U
TBUS External Loopback test failed. TBUS External Loopback test failed. TBUS External Loopback test failed. MCAP GPROC is transitioning in Related State Changes column. EMPTY MCAP GPROC is transitioning in the Related Alarms column. EMPTY
N U
N U
N U
EMPTY GPROC/EGPRO C:231, 232, 254 EMPTY
Initialization Error Parent Cage is Out of Service Board removed/missing from cage Wrong card type found in a slot Wrong XCDR card type found in XCDR slot Parent Cage is Out of Service
N U N U
XCDR
0-55
D-U
D-U
EMPTY
N U
XCDR
0-55
D-U
D-U
EMPTY
EMPTY
N U
EMPTY
XCDR
0-55
D-U
D-U
EMPTY
XCDR: 22
N U
EMPTY
XCDR
0-55
B-U
D-U
2 5 2 4
BOARD OUT OF CAGE ALARM
XCDR
0-55
B-U
D-U
GPROC/EGPRO C:231, 232; CBUS: 1, 2, 3, 4, 224 XCDR: 230
N U
XCDR
0-55
B-U
D-U
EMPTY
EMPTY
Board removed/missing from cage Alarm detected on device
N U
N U
EMPTY
October 30, 2008
BSC-59

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
0 0 0 0 0
No reason No reason No reason No reason No reason
Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24
XCDR XCDR XCDR XCDR XCDR
0-55 0-55 0-55 0-55 0-55
D-U D-L B-U D-L D-L
D-L D-U E-L B-U E-L
EMPTY EMPTY EMPTY EMPTY GPROC/EGPROC: D-U/BU ( 0 ), D-L/E-L ( 23, 24 ), D-U/E-U ( 28 ); CBUS: DU/B-U ( 0 ) EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY EMPTY XCDR:230
No Reason No Reason No Reason No Reason No Reason
S t a t u s N U
Operator LOCKED device Operator UNLOCKED device Operator LOCKED device System moved device to BUSY MCAP GPROC is transitioning in the Related State Changes column. Operator UNLOCKED device Device went disabled with no specific reason given. Device encountered an error while in the B-U state and was subsequently disabled. System moved device to BUSY EMPTY EMPTY
N U N U N U N U
BSC State Change BSC State Change BSC State Change
0 0 1 7
No reason No reason INITIALIZATI ON ERROR
Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24 Cage 0-5; Slot 6-24
XCDR XCDR XCDR
0-55 0-55 0-55
E-L E-L B-U
B-U D-L D-U
EMPTY EMPTY EMPTY
No Reason No Reason No Reason
N U N U N U
0 1 7 2 7 2 2
No reason INITIALIZATI ON ERROR WRONG CARD TYPE ERROR PARENT CAGE OOS
Cage 0-5; Slot 6-17 Cage 0-5; Slot 6-17 Cage 0-5; Slot 6-17 Cage 0-5; Slot 6-17
MSI MSI MSI
1-72 1-72 1-72
D-U D-U D-U
B-U D-U D-U
CAGE: D-U/B-U ( 0 ) EMPTY EMPTY
MSI: 230 EMPTY EMPTY
No Reason Initialization Error Wrong card type found in a slot Parent Cage is Out of Service
N U N U N U
MSI
1-72
D-U
D-U
2 5 2 2
BOARD OUT OF CAGE PARENT CAGE OOS
MSI
1-72
D-U
D-U
N U
MSI
1-72
B-U
D-U
BSC State Change BSC State Change BSC State Change BSC State
2 5 2 4 0 0
BOARD OUT OF CAGE ALARM No reason No reason
Cage 0-5; Slot 6-17 Cage 0-5; Slot 6-17 Cage 0-5; Slot 6-17 Cage 0-5; Slot
MSI
1-72
B-U
D-U
Board removed/missing from cage Parent Cage is Out of Service
N U
MCAP GPROC is transitioning in Related State Changes/Alarms Column. EMPTY
N U
MSI MSI MSI
1-72 1-72 1-72
B-U D-U D-L
D-U D-L D-U
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
Board removed/missing from cage Alarm detected on device No Reason No Reason
N U
N U N U N U
EMPTY Operator LOCKED device Operator UNLOCKED
BSC-60
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
0 0 0 0 0
No reason No reason No reason No reason No reason
6-17 Cage 0-5; Slot 6-17 Cage 0-5; Slot 6-17 Cage 0-5; Slot 6-17 Cage 0-5; Slot 6-17 Cage 0-5; Slot 6-17
MSI MSI MSI MSI MSI
1-72 1-72 1-72 1-72 1-72
B-U E-L E-U E-L D-L
E-L E-U E-L B-U E-L
EMPTY EMPTY EMPTY EMPTY GPROC/EGPROC: D-U/BU ( 0 ), D-L/E-L ( 23, 24 ), D-U/E-U ( 28 ); CBUS: DU/B-U ( 0 ) EMPTY
EMPTY EMPTY EMPTY EMPTY MSI: 230
No Reason No Reason No Reason No Reason No Reason
N U N U N U N U N U
device Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device MCAP GPROC is transitioning in the Related State Changes column. System moved device to BUSY
BSC State Change
No reason
BSC State Change
1 7
INITIALIZATI ON ERROR
BSC State Change
2 4
ALARM
BSC State Change
3 0
PARENT MSI OOS
BSC State Change
3 0
PARENT MSI OOS
BSC State Change
2 4
ALARM
BSC State Change
No reason
Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device
T1/E1
1-144
D-U
B-U
EMPTY
No Reason
N U
T1/E1
1-144
D-U
D-U
EMPTY
EMPTY
N U
Operator UNLOCKED device
T1/E1
1-144
D-U
D-U
EMPTY
EMPTY
Alarm detected on device
N U
EMPTY
T1/E1
1-144
D-U
D-U
EMPTY
EMPTY
Parent MSI is Out of Service
N U
EMPTY
T1/E1
1-144
B-U
D-U
MSI: B-U/E-L ( 0 ), B-U/DU ( 22, 24, 25 )
MSI: 231, 254
Parent MSI is Out of Service
N U
EMPTY
T1/E1
1-144
B-U
D-U
EMPTY
EMPTY
N U
EMPTY
T1/E1
1-144
D-U
D-L
EMPTY
EMPTY
No Reason
N U
Operator LOCKED device
October 30, 2008
BSC-61

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s Operator UNLOCKED device
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
BSC State Change
No reason
BSC State Change
No reason
BSC State Change
No reason
BSC State Change
No reason
BSC State Change
No reason
BSC State Change
No reason
BSC State Change
2 4
ALARM
0 3 2 3 1
No reason NO GPROC AVAILABLE PARENT SPAN LOCKED OR DISABLED
ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Cage: 0-5; Slot: 6-17; Device ID[0]: 0-71; Device ID[1]: 0/1 Device ID: 031 Device ID: 031 Device ID: 031
T1/E1
1-144
D-L
D-U
EMPTY
EMPTY
No Reason
N U
T1/E1
1-144
B-U
E-L
EMPTY
EMPTY
No Reason
N U
T1/E1
1-144
E-L
E-U
EMPTY
EMPTY
No Reason
N U
T1/E1
1-144
E-U
E-L
EMPTY
EMPTY
No Reason
N U
T1/E1
1-144
E-L
B-U
EMPTY
EMPTY
No Reason
N U
T1/E1
1-144
D-L
E-L
MSI: D-U/B-U ( 0 ), E-L/BU(0)
EMPTY
No Reason
N U
Device is ENABLED
T1/E1
1-144
E-L
D-L
EMPTY
EMPTY
N U
EMPTY
XBL XBL XBL
1-32 1-32 1-32
E-U D-U D-U
B-U D-U D-U
EMPTY EMPTY GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) EMPTY
EMPTY EMPTY GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
No Reason No GPROC available for the link SPAN on which the link resides has been Locked or Disabled
N U N U N U
System moved device to BUSY EMPTY EMPTY
BSC State
INITIALIZATI
Device ID: 0-
XBL
1-32
D-U
D-U
EMPTY
N U
EMPTY
BSC-62
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Change BSC State Change BSC State Change BSC State Change
7 3 7 3 4 3 1
ON ERROR INTERNAL ERROR WAITING FOR SABME PARENT SPAN LOCKED OR DISABLED
31 Device ID: 031 Device ID: 031 Device ID: 031
XBL XBL
1-32 1-32
D-U D-U
D-U E-U
EMPTY MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) GPROC/EGPROC: B-U/EL ( 0 ), B-U/D-U ( 23, 24 ) EMPTY EMPTY
EMPTY MSI: 230; GPROC/EGPRO C: 230 GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
Internal Error Waiting for SABME/UA from remote site SPAN on which the link resides has been Locked or Disabled
N U N U
EMPTY EMPTY
XBL
1-32
B-U
D-U
N U
EMPTY
3 2 3 7 3 6
3 2 3 1
NO GPROC AVAILABLE INTERNAL ERROR LINK DISCONNEC T INDICATION WAITING NO GPROC AVAILABLE PARENT SPAN LOCKED OR DISABLED
Device ID: 031 Device ID: 031 Device ID: 031
XBL XBL XBL
1-32 1-32 1-32
B-U B-U B-U
D-U D-U E-U
GPROC/EGPRO C: 231, 232, 254 XBL: 1, 8, 9, 10 XBL:10
No GPROC available for the link Internal Error Received remote disconnect, back to waiting for event
N U N U N U
EMPTY EMPTY EMPTY
Device ID: 031 Device ID: 031
XBL XBL
1-32 1-32
E-U E-U
D-U D-U
0 0 0 0 0 0 0
No reason No reason No reason No reason No reason No reason No reason
Device ID: 031 Device ID: 031 Device ID: 031 Device ID: 031 Device ID: 031 Device ID: 031 Device ID: 031 Device ID: 180; side: 0/1
XBL XBL XBL XBL XBL XBL XBL
1-32 1-32 1-32 1-32 1-32 1-32 1-32
D-U D-L B-U E-L E-U E-L D-L
D-L D-U E-L E-U E-L B-U E-L
GPROC/EGPROC: B-U/EL ( 0 ), B-U/D-U ( 23, 24 ) GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) EMPTY
GPROC/EGPRO C: 231, 232, 254 GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
No GPROC available for the link SPAN on which the link resides has been Locked or Disabled
N U N U
EMPTY EMPTY
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY MSI: 230; GPROC/EGPRO C: 230 EMPTY
No Reason No Reason No Reason No Reason No Reason No Reason No Reason
N U N U N U N U N U N U N U
Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Operator LOCKED device
No reason
RslSap
1-160
E-U
B-U
No Reason
N U
System moved device to BUSY
October 30, 2008
BSC-63

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
3 2 3 1
NO GPROC AVAILABLE PARENT SPAN LOCKED OR DISABLED
Device ID: 180; side: 0/1 Device ID: 180; side: 0/1
RslSap RslSap
1-160 1-160
D-U D-U
D-U D-U
EMPTY GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) EMPTY EMPTY
EMPTY GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
No GPROC available for the link SPAN on which the link resides has been Locked or Disabled
S t a t u s N U N U
EMPTY EMPTY
1 7 3 7 3 4 3 2 3 1
INITIALIZATI ON ERROR INTERNAL ERROR WAITING FOR SABME NO GPROC AVAILABLE PARENT SPAN LOCKED OR DISABLED
Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1
RslSap RslSap
1-160 1-160
D-U D-U
D-U D-U
EMPTY EMPTY
Initialization Error Disable request initiated due to BSC internal error Waiting for SABME/UA from remote site No GPROC available for the link SPAN on which the link resides has been Locked or Disabled
N U N U
EMPTY EMPTY
RslSap
1-160
D-U
E-U
RslSap RslSap
1-160 1-160
E-U E-U
D-U D-U
3 7 3 5 3 1
INTERNAL ERROR DISCONNEC T IND RECEIVED PARENT SPAN LOCKED OR DISABLED
Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1
RslSap
1-160
E-U
D-U
MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) GPROC/EGPROC: B-U/EL ( 0 ), B-U/D-U ( 23, 24 ) GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) EMPTY
MSI: 230; GPROC/EGPRO C: 230 GPROC/EGPRO C: 231, 232, 254 GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
N U
EMPTY
N U N U
EMPTY EMPTY
EMPTY
RslSap
1-160
E-U
D-U
EMPTY
EMPTY
Disable request initiated due to BSC internal error Disconnect Indication Received SPAN on which the link resides has been Locked or Disabled
N U
EMPTY
N U
EMPTY
RslSap
1-160
B-U
D-U
GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0)
GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
N U
EMPTY
3 9 3 2 3 7 3 5
LINK ALARM RECEIVED NO GPROC AVAILABLE INTERNAL ERROR DISCONNEC T IND RECEIVED
Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1
RslSap RslSap RslSap
1-160 1-160 1-160
B-U B-U B-U
D-U D-U D-U GPROC/EGPROC: B-U/EL ( 0 ), B-U/D-U ( 23, 24 ) EMPTY GPROC/EGPRO C: 231, 232, 254 EMPTY
RslSap
1-160
B-U
D-U
EMPTY
EMPTY
Alarm received on the link No GPROC available for the link Disable request initiated due to BSC internal error Disconnect Indication Received
N U N U N U
EMPTY EMPTY EMPTY
N U
EMPTY
BSC-64
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
BSC State Change
4 6
OML DISABLES SNMP RSL LINK SABME FAIL ALARM AGENT DISABLE REQUEST INTERNAL ERROR E OML LINK NOT BUSY No reason No reason No reason No reason No reason No reason No reason
Device ID: 180; side: 0/1
RslSap
1-160
B-U
D-U
BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
4 0 4 7 3 7 4 1 0 0 0 0 0 0 0
Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 180; side: 0/1
RslSap RslSap
1-160 1-160
B-U B-U
D-U D-U
OML: B-U/E-L ( 0 ), B-U/DU ( 31, 32, 39, 43 ); GPROC/EGPROC: B-U/EL ( 0 ), B-U/D-U ( 23, 24 ) EMPTY EMPTY
OML: 0
E-OML is taking down SNMP RSL
S t a t u s N U
EMPTY EMPTY
Ten SABMEs were rejected OMC Agent taking down SNMP RSL Disable request initiated due to BSC internal error E-OML Link is not in the BUSY State No Reason No Reason No Reason No Reason No Reason No Reason No Reason
N U N U
OMF GPROC and E_OML are transitioning in the Related State Changes column. EMPTY EMPTY
RslSap
1-160
E-U
E-U
EMPTY
EMPTY
N U
EMPTY
RslSap RslSap RslSap RslSap RslSap RslSap RslSap RslSap
1-160 1-160 1-160 1-160 1-160 1-160 1-160 1-160
E-U D-U D-L B-U E-L E-U E-L D-L
E-U D-L D-U E-L E-U E-L B-U E-L
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) EMPTY EMPTY
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY MSI: 230; GPROC/EGPRO C: 230 EMPTY EMPTY
N U N U N U N U N U N U N U N U
EMPTY Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Device is ENABLED
0 2
No reason Device is disabled due to parent device being out of service WAITING FOR SABME INTERNAL ERROR No reason NO GPROC AVAILABLE
RslSap RslSap
1-160 1-160
E-L B-U
D-L D-U
No Reason No Reason
N U N U
Device went disabled with no specific reason given. Device went disabled with no specific reason given.
3 4 3 7 0 3 2
Device ID: 180; side: 0/1 Device ID: 180; side: 0/1 Device ID: 0/1 Device ID: 0/1
RslSap
1-160
E-L
E-U
RslSap
1-160
B-U
B-U
MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) EMPTY
MSI: 230; GPROC/EGPRO C: 230 EMPTY
OML OML
1-2 1-2
E-U D-U
B-U D-U
EMPTY EMPTY
EMPTY EMPTY
Waiting for SABME/UA from remote site Error encountered while updating RSL's internal router tables. No Reason No GPROC available for the link
N U
EMPTY
N U
EMPTY
N U N U
System moved device to BUSY EMPTY
October 30, 2008
BSC-65

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
BSC State Change
3 1
PARENT SPAN LOCKED OR DISABLED
Device ID: 0/1
OML
1-2
D-U
D-U
1 7 3 4 3 9 3 1
INITIALIZATI ON ERROR WAITING FOR SABME LINK ALARM RECEIVED PARENT SPAN LOCKED OR DISABLED
Device ID: 0/1 Device ID: 0/1
OML OML
1-2 1-2
D-U D-U
D-U E-U
GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) EMPTY MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) EMPTY GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) GPROC/EGPROC: B-U/EL ( 0 ), B-U/D-U ( 23, 24 ) GPROC/EGPROC: B-U/EL ( 0 ), B-U/D-U ( 23, 24 ) EMPTY EMPTY
GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
SPAN on which the link resides has been Locked or Disabled
S t a t u s N U
EMPTY
EMPTY MSI: 230; GPROC/EGPRO C: 230, OML: 1 GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
Initialization Error Waiting for SABME/UA from remote site Alarm received on the link SPAN on which the link resides has been Locked or Disabled
N U N U
EMPTY EMPTY
Device ID: 0/1 Device ID: 0/1
OML OML
1-2 1-2
B-U B-U
D-U D-U
N U N U
EMPTY EMPTY
BSC State Change
3 1
PARENT SPAN LOCKED OR DISABLED
Device ID: 0/1
OML
1-2
E-U
D-U
GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
SPAN on which the link resides has been Locked or Disabled
N U
EMPTY
3 2 3 2 4 3 4 2
BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State
0 0 0 0 0 0
NO GPROC AVAILABLE NO GPROC AVAILABLE LINK OML OOS IND LINK ACTIVATE AGENT REJ TAG No reason No reason No reason No reason No reason No reason
Device ID: 0/1 Device ID: 0/1 Device ID: 0/1 Device ID: 0/1
OML OML OML OML
1-2 1-2 1-2 1-2
B-U E-U B-U E-U
D-U D-U D-U E-U
GPROC/EGPRO C: 231, 232, 254 GPROC/EGPRO C: 231, 232, 254 OML: 0 OML: 1
No GPROC available for the link No GPROC available for the link Received indication to take OML down OML failed to go busy: link activate agent msg rejected No Reason No Reason No Reason No Reason No Reason No Reason
N U N U N U N U
Device ID: 0/1 Device ID: 0/1 Device ID: 0/1 Device ID: 0/1 Device ID: 0/1 Device ID: 0/1
OML OML OML OML OML OML
1-2 1-2 1-2 1-2 1-2 1-2
D-U D-L B-U E-L E-U E-L
D-L D-U E-L E-U E-L B-U
N U N U N U N U N U N U
Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED
BSC-66
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Change BSC State Change BSC State Change BSC State Change BSC State Change
No reason
Device ID: 0/1
OML
1-2
D-L
E-L
0 3 2 3 1
No reason NO GPROC AVAILABLE PARENT SPAN LOCKED OR DISABLED
MTL MTL MTL
1-16 1-16 1-16
E-U D-U D-U
B-U D-U D-U
MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) EMPTY EMPTY GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) EMPTY MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) EMPTY GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) GPROC/EGPROC: B-U/EL ( 0 ), B-U/D-U ( 23, 24 ) EMPTY GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ); MSI: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); E1/T1: BU/D-U ( 24, 30 ) , B-U/E-L ( 0) GPROC/EGPROC: B-U/EL ( 0 ), B-U/D-U ( 23, 24 ) EMPTY EMPTY EMPTY EMPTY
MSI: 230; GPROC/EGPRO C: 230 EMPTY EMPTY GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
No Reason
N U
device Device is ENABLED
No Reason No GPROC available for the link SPAN on which the link resides has been Locked or Disabled
N U N U N U
System moved device to BUSY EMPTY EMPTY
1 7 3 4 3 9 3 1
INITIALIZATI ON ERROR WAITING FOR SABME LINK ALARM RECEIVED PARENT SPAN LOCKED OR DISABLED
Device ID: 015 Device ID: 015 Device ID: 015 Device ID: 015
MTL MTL
1-16 1-16
D-U D-U
D-U E-U
EMPTY MSI: 230; GPROC/EGPRO C: 230 MTL: 0, 1 , 2 GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
Initialization Error Waiting for SABME/UA from remote site Alarm received on the link SPAN on which the link resides has been Locked or Disabled
N U N U
EMPTY EMPTY
MTL MTL
1-16 1-16
B-U B-U
D-U D-U
N U N U
EMPTY EMPTY
3 2 4 4 3 1
NO GPROC AVAILABLE LINK INHIBITED PARENT SPAN LOCKED OR DISABLED
MTL MTL MTL
1-16 1-16 1-16
B-U B-U E-U
D-U D-U D-U
GPROC/EGPRO C: 231, 232, 254 EMPTY GPROC/EGPRO C: 231, 232, 254; MSI: 231, 254
No GPROC available for the link MSC Inhibit Requested SPAN on which the link resides has been Locked or Disabled
N U N U N U
EMPTY EMPTY EMPTY
BSC State Change BSC State Change BSC State Change BSC State Change BSC State
3 2 0 0 0 0
NO GPROC AVAILABLE No reason No reason No reason No reason
Device ID: 015 Device ID: 015 Device ID: 015 Device ID: 015 Device ID: 0-
MTL MTL MTL MTL MTL
1-16 1-16 1-16 1-16 1-16
E-U D-U D-L B-U E-L
D-U D-L D-U E-L E-U
GPROC/EGPRO C: 231, 232, 254 EMPTY EMPTY EMPTY EMPTY
No GPROC available for the link No Reason No Reason No Reason No Reason
N U N U N U N U N U
EMPTY Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED
October 30, 2008
BSC-67

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s device Operator LOCKED device Operator UNLOCKED device Device is ENABLED
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
0 0 0
No reason No reason No reason
15 Device ID: 015 Device ID: 015 Device ID: 015 Device ID: 015 Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1
MTL MTL MTL
1-16 1-16 1-16
E-U E-L D-L
E-L B-U E-L
EMPTY EMPTY MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) MSI: E-L/B-U ( 0 ), D-U/BU ( 0 ); T1/E1: D-U/B-U ( 0 ) GCLK: E-L/E-U ( 0 ), DU/E-U ( 28 ) GCLK: E-L/B-U ( 0 ), DU/B-U ( 0 ) GCLK: E-U/B-U ( 0 ) GCLK: B-U /E-L ( 0 ), BU/D-U ( 25 )
EMPTY EMPTY MSI: 230; GPROC/EGPRO C: 230 MSI: 230; GPROC/EGPRO C: 230 GCLK: 1 ( C ), 2 ( C ), 3 ( C ) GCLK: 1 ( C ), 2 ( C ), 3 ( C ) EMPTY EMPTY
No Reason No Reason No Reason
N U N U N U
3 4 2 8 0 0 6 1
WAITING FOR SABME STANDBY DEVICE No reason No reason CBUS CONFIGURA TION ERROR CBUS CONFIGURA TION ERROR No reason No reason No reason No reason No reason No reason No reason No reason STANDBY DEVICE
MTL
1-16
B-U
E-U
CBUS CBUS CBUS CBUS
1-2 1-2 1-2 1-2
D-U D-U E-U E-U
E-U B-U B-U D-U
Waiting for SABME/UA from remote site Device is a Standby Device No Reason No Reason CBUS had a configuration error
N U
EMPTY
N U N U N U N U
EMPTY EMPTY BSC swapped Active/Stand-by CBUS EMPTY
BSC State Change
6 1
Cage 0-5; Side: 0/1
CBUS
1-2
B-U
D-U
GCLK: B-U /E-L ( 0 ), BU/D-U ( 25 )
EMPTY
CBUS had a configuration error
N U
EMPTY
0 0 0 0 0 0 0 0 2 8
Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1 Cage 0-5; Side: 0/1 Side: 0/1
CBUS CBUS CBUS CBUS CBUS CBUS CBUS CBUS LAN
1-2 1-2 1-2 1-2 1-2 1-2 1-2 1-2 1-2
B-U D-U D-L B-U E-L E-U E-L D-L D-U
E-U D-L D-U E-L E-U E-L B-U E-L E-U
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY GCLK: E-L/E-U ( 0 ), DU/E-U ( 28 ) EMPTY
GCLK: 4, 14 EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY
No Reason No Reason No Reason No Reason No Reason No Reason No Reason No Reason Back-up ring(BUR) test passed and the device is in the standby mode, ready to take over if the
N U N U N U N U N U N U N U N U N U
Device is ENABLED Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Operator LOCKED device Operator UNLOCKED device Device is ENABLED EMPTY
BSC-68
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 3 1 1 3 2 0
BUR TEST FAILED RING FAILURE No reason
Side: 0/1
LAN
1-2
E-U
D-U
EMPTY
EMPTY
active LAN fails. Back-up ring (BUR) test failed. Active LAN failed.
N U
Side: 0/1
LAN
1-2
B-U
D-U
EMPTY
LAN: 1
N U
Stand-by LAN is broken: system moves device to DU EMPTY
Side: 0/1
LAN
1-2
E-U
B-U
LAN: B-U/D-L ( 0 ), BU/D/U ( 132 )
EMPTY
No Reason
N U
BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change BSC State Change
0 0 0 0 2 8 0
No reason No reason No reason No reason STANDBY DEVICE No reason
Side: 0/1 Side: 0/1 Side: 0/1 Side: 0/1 Side: 0/1
LAN LAN LAN LAN LAN
1-2 1-2 1-2 1-2 1-2
B-U E-U D-U D-L D-L
D-L D-L D-L D-U E-U
No Reason No Reason No Reason No Reason Device is a Standby Device Function assigned to GPROC Function not assigned to GPROC Function assigned to GPROC Function not assigned to GPROC Device is a Standby Device No Reason No Reason
N U N U N U N U N U
Stand-by became Active. Active LAN is transitioning in the Related State Changes column. Operator LOCKED Active LAN, if equipped Operator LOCKED standby LAN Operator LOCKED device Operator UNLOCKED device. Operator UNLOCKED device, LAN became standby. Locking is not allowed on this function Locking is not allowed on this function Locking is not allowed on this function Locking is not allowed on this function System is initializing or GCLK has just warmed up. System is initializing or GCLK has just warmed up. Active GCLK is transitioning in Related State Changes and Alarms column. EMPTY EMPTY
No reason
No reason
No reason
2 8 0 0
STANDBY DEVICE No reason No reason
LCF ID:0-19, GPROC/EGP ROC:0-31 LCF ID:0-19, GPROC/EGP ROC:0-31 OMF ID:0, GPROC/EGP ROC:0-31 OMF ID:0, GPROC/EGP ROC:0-31 Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5
LCF
1-20
E-Eq
B-Eq
GPROC/EGPROC: D-U/BU ( 0 ), E-U/B-U ( 0 ) GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ) GPROC/EGPROC: D-U/BU ( 0 ), E-U/B-U ( 0 ) GPROC/EGPROC: B-U/DU ( 23, 24 ), B-U/E-L ( 0 ) CAGE: D-U/B-U ( 0 ) CAGE: D-U/B-U ( 0 ) GCLK: B-U/D-U ( 25 ), BU/E-L ( 0 ); CBUS: B-U/DU ( 61 ), B-U/E-L ( 0 ) EMPTY EMPTY
GPROC/EGPRO C: 230 GPROC/EGPRO C: 231, 232, 254 GPROC/EGPRO C: 230 GPROC/EGPRO C: 231, 232, 254 GCLK: 230 GCLK: 230 GCLK: 224
N U
LCF
1-20
B-Eq
E-Eq
N U
OMF
E-Eq
B-Eq
N U
OMF
B-Eq
E-Eq
N U
GCLK GCLK GCLK
1-2 1-2 1-2
D-U D-U E-U
E-U B-U B-U
N U N U N U
2 5 2 5
BOARD OUT OF CAGE BOARD OUT OF CAGE
Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5
GCLK GCLK
1-2 1-2
E-U B-U
D-U D-U
EMPTY EMPTY
GCLK card was removed GCLK card was removed
N U N U
October 30, 2008
BSC-69

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Comments & Notes
4 8 0 0 0 0 0 0 0 0
Safe Test Failed No reason No reason No reason No reason No reason No reason No reason No reason
Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5 Cage: 0-5; Slot: 3/5 Side: 0/1
GCLK GCLK GCLK GCLK GCLK GCLK GCLK GCLK TDM
1-2 1-2 1-2 1-2 1-2 1-2 1-2 1-2 0-1
B-U D-U D-L B-U E-L E-L E-U D-L E-U
E-U D-L D-U E-L E-U B-U E-L E-L B-U
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY KSW: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); TBUS: BU/D-U ( 22, 29, 62, 63, 64, 65, 66 ), B-U/E-L ( 0 )
EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY GCLK: 230 TDM: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 24, 25; CAGE: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17; KSW: 231, 254 TDM: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 24, 25; CAGE: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17; KSW: 231, 254 TDM: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 24, 25; CAGE: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17; KSW: 231, 254 TDM: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 24, 25; CAGE: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17;
GCLK Safe Test Failed No Reason No Reason No Reason No Reason No Reason No Reason No Reason Device is Active TDM highway
S t a t u s N U N U N U N U N U N U N U N U N U
EMPTY Operator locked device Operator unlocked device Operator locked device Operator unlocked device Operator unlocked device Operator locked device EMPTY Active side KSW and TBUS are showing problems. The stand-by side TDM is now coming into service.
BSC State Change
No reason
Side: 0/1
TDM
0-1
B-U
E-U
KSW: B-U/D-U ( 22, 24, 25 ), B-U/E-L ( 0 ); TBUS: BU/D-U ( 22, 29, 62, 63, 64, 65, 66 ), B-U/E-L ( 0 )
TDM Highway is less or equally operable than ACTIVE Highway
N U
Active side KSW and TBUS are showing problems. Therefore, the Active side is moving out of service.
BSC State Change
3 7
INTERNAL ERROR
Side: 0/1
TDM
0-1
B-U
D-U
TDM Highway is having problems that have resulted in DISABLING the device
N U
Active side KSW and TBUS are showing problems. Therefore, the Active side is to DISABLED
BSC State Change
No reason
Side: 0/1
TDM
0-1
B-U
D-U
N U
Active side KSW and TBUS are showing problems. Therefore, the Active side is moving out of service.
BSC-70
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
BSC State Change
3 7
INTERNAL ERROR
Side: 0/1
TDM
0-1
E-U
D-U
BSC State Change
No reason
Device ID: 0239
CA_CELL
1-240
D-U
B-U
EMPTY
KSW: 231, 254 TDM: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 24, 25; CAGE: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17; KSW: 231, 254 EMPY
N U
Stand-by side KSW and TBUS are showing problems. Therefore, the Stand-by side is to DISABLED
No Reason
N U
BSC State Change
No reason
Device ID: 0239
CA_CELL
1-240
B-U
D-U
EMPTY
EMPY
No Reason
N U
BSC State Change
3 4 1 3
Device is disabled due to parent device being out of service WAITING FOR SABME BSC Database Generation Successful BSC Database Generation Failed
Device ID: 0239
CA_CELL
1-240
B-U
D-U
EMPTY
EMPY
No Reason
N U
The representation of a cell in the CA process has moved to B-U because the cell has become busy The representation of a cell in the CA process has moved to D-U because the cell has become disabled The representation of a cell in the CA process has moved to D-U because the cell has become disabled EMPTY OMF GPROC comes back to service.
Device ID: 0239 Device ID: 1
CA_CELL BSCDB
1-240 1
B-U D-Neq
D-U B-U
EMPTY GPROC/EGPROC: D-U/BU(0)
EMPY EMPTY
No Reason Acknowledges that a database build on the BSC has been completed and was successful Acknowledges that a database build on the BSC has been attempted and was not successful
N U N U
BSC State Change
1 4
Device ID: 1
BSCDB
D-Neq
B-U
GPROC/EGPROC: D-U/BU(0)
EMPTY
N U
OMF GPROC comes back to service.
October 30, 2008
BSC-71
Release SR17.0
__________________________________ Events
Event Type
Reason Code
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
bgdownloadStarted Event
EMPTY
<load> <release>.<version >.<subversion>. <load> <release>.<version >.<subversion>. - <object number> - <object name> - <object size> <load> <release>.<version >.<subversion>. Background Download Successful Abort - Aborting
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
bgobjectDownloadE vent
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has completed successfully or has failed. In case of failure, Action Status Info details reason for failure. An object is being downloaded to the BSC.
S t a t u s U EMPTY
U EMPTY
bgdownloadComple tedEvent
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated when a download is completed.
U EMPTY
bgdownloadFinishe dEvent bgdlAbortEvent
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event reports the status of a completed background download. Event is generated if OLCC background download abort has been requested. Event is generated if OLCC background download has been successfully aborted. Event is generated when OLCC switch is scheduled. Event is generated when OLCC switch has completed successfully. Operator has acknowledged download in the "Background Download SW Loads" widow. Event is generated when a file (typically a statistics file) is uploaded to the OMC. This event is used to inform the OMC, a download request has been
U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
U EMPTY
bgdlAbortEvent
EMPTY
Abort - Success
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
U EMPTY
onlineSwitchSched uledEvent onlineSwitchSucce ededEvent ackSucceededEven t fileNEavailableEven t downloadStartedEv ent
EMPTY EMPTY EMPTY
Online Switch Scheduled Online Switch Successful Ack Successful
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
N N N
U EMPTY U EMPTY U EMPTY
EMPTY
File Type = <file type> <load> <release>.<version
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
U EMPTY
BSC-72
October 30, 2008
Release SR17.0
Event Type
Reason Code

MOI Info (Label) Inst From State To State Related State Changes Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
downloadComplete dEvent
EMPTY
filexferCompletedE vent
EMPTY
filexferAbortedEven t
EMPTY
objectDownloadEve nt
EMPTY
>.<subversion>. <load> <release>.<version >.<subversion>. File Type = <file type> - File Name = <dest file name> where file type can be Unknown or Statistics Abort Reason = <abort reason code> - File Type = <file type> - File Name = <dest file name> <load> <release>.<version >.<subversion>. - <object number> - <object name> - <object size>
sent. EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY This event is used to inform the OMC the download has completed. N U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Upload of a statistics file.
U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Upload of a statistics file was interrupted.
U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated when a object file is downloaded to the BSC
U EMPTY
October 30, 2008
BSC-73
Release SR17.0
BSC-74
October 30, 2008
Release SR17.0
__________________________ Alarms
Alarm Type
Alarm Code
CCPDAP
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t & C l e a r R C
O u t a g e Y / N
Comments & Notes
1296
DAP Peer to Peer Connection Terminated
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
DAP'S UANC = <UANC> DAP ID = <DAP_ID>
Major
EMPTY
DAP_DAP_ LINK: 9, 12 DAP_DAP_ HN_LINK: 9, 12
1) Restart DAP.2) Replace failed Ethernet card or system unit. 3) Troubleshoot Network and Repair.
32800
Physical Link: V.35 Loss
DAP_FR _ALM
4.[12].[16].[314318].1
<FR board number>
Critical
EMPTY
DAP_ACG_ LINK: 7,9 DAP_MDG _LINK: 7,9 DAP_APD_ LINK: 7,9
32806
iSG_DAP, DAP_DAP, or iDAC_DAP TCP Link Down
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Critical
EMPTY
communicat
32807
Ethernet Link
1.3.6.1.4.1.
DAP_NI
10.1.3.[3
E-Net Link
Critical
EMPTY
DAP_DAP_ LINK: 9,12 DAP_DAP_ HN_LINK: 9,12 DAP_ISG_ LINK: 9,12 DAP_IDAC _LINK: 9, 12 DAP_DAP_
1) Replace paddle card, ribbon cable, V.35 connector board. 2) Trouble-shoot MPS. 3) FR board may restart automatically. If not, attempt to restart FR board manually. If FR board fails multiple attempts to restart, replace FR board card. Reestablish TCP connection
R C
1) DAP was shutdown. 2) Ethernet Card Failure. Double Point of Failure. 3) General Network Failure. Note: Only the DAP that initiated the termination of the connection reports this alarm. Where: <UANC> = {1-16777215} <DAP_ID> = {1-300} 1) Paddle card, ribbon cable, or V.35 connector board related problem. 2) MPS related problem. 3) FR board card problem. WHERE <FR board number> = {0x01 - 0x1f}
R C
1) iSG, iDAC or remote DAP terminated TCP connection 2) Local DAP terminated TCP connection
Contact the iDEN
Ethernet Link is down.
October 30, 2008
CCPDAP-1

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t & C l e a r C
O u t a g e Y / N
Comments & Notes
ionFailureE vent
Down
161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
OC_ALM
13,319,3 18,324].1
<Link ID> is down
32807
Ethernet Link Down
DAP_NI OC_ALM
10.1.3.[3 13,319,3 18,324].1
Sub Agent Task <Task Name> SMUX link down
Critical
EMPTY
45058
Power Disabled
45059
Fan Disabled
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
DAP_PO WER_AL M
3.[12].6.[101, 103].1
EMPTY
Critical
EMPTY
LINK: 9,12 DAP_DAP_ HN_LINK: 9,12 DAP_HLR_ LINK: 9,12 DAP_HLR_ HN_LINK: 9,12 DAP_IDAC _LINK: 9,12 DAP_ISGLINK: 9,12 DAP_DAP_ LINK: 9,12 DAP_DAP_ HN_LINK: 9,12 DAP_HLR_ LINK: 9,12 DAP_HLR_ HN_LINK: 9,12 DAP_IDAC _LINK: 9,12 DAP_ISGLINK: 9,12 DAP_HW_ CONTAINE R: 601-606
Customer Situation Center for assistance.
<Link ID>= {1-2}
Contact the iDEN Customer Situation Center for assistance.
R C
Sub Agent Task <Task Name> lost the SMUX link connection with CA
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit.
R C
A hardware failure has occurred
DAP_FA N_ALM
2.[12].5.[401402].1
EMPTY
Critical
EMPTY
DAP_HW_ CONTAINE R: 601-606
R C
This alarm is reported as a cooling fan has been disabled. The DAP has 2 fans, and 1 out of service is not service impacting but should be investigated for corrective action. Should one fan fail, open a minor ticket with Motorola CNRC. If both fans are disabled, the
CCPDAP-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t & C l e a r
O u t a g e Y / N
Comments & Notes
45060
CPU Set Disabled
45061
FR Board Disabled
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Critical
EMPTY
DAP_CPU: 608 DAP_HW_ CONTAINE R: 601-606
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit.
R C
DAP will shutdown when it reaches its thermal limit to avoid heat damage. Should both fans fail, open a Critical ticket with Motorola CNRC for resolution and contact the market A hardware failure has occurred
DAP_FR _ALM
4.[12].[16].[314318].1
<FR board number>
Critical
EMPTY
45062
SCSI Device Disabled
45063
Synchronous Device Disabled
45064
Asynchronous Device Disabled
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT
DAP_SC SI_ALM
7.1.3.[31 3,319].1
EMPTY
Critical
EMPTY
DAP_FR: 608 DAP_ACG_ LINK: 7,9 DAP_MDG _LINK: 7,9 DAP_APD_ LINK: 7,9 DAP_HW_ CONTAINE R: 601-606 DAP_SCSI: 607,608 DAP_HW_ CONTAINE R: 601-606
R C
A hardware failure has occurred. Where: <FR board number> = {0x01 - 0x1f} or <FR board number> <recovery> Where <recovery>={01=auto, 02=manual}
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts
R C
DAP_SY NC_ALM
8.1.3.[31 4-318].1
EMPTY
Critical
EMPTY
R C
DAP_AS YNC_AL M
9.[12].[16].[314318].1
EMPTY
Critical
EMPTY
R C
October 30, 2008
CCPDAP-3

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
45065
NIOC Disabled
45066
Router Controller Disabled
45069
Frame Relay Board Failure
ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
to re-integrate, replace the hardware or system unit. DAP_NI OC_ALM 10.1.3.[3 13,319,3 18,324].1 EMPTY Critical EMPTY DAP_HW_ CONTAINE R: 601-606 DAP_NIOC: 608 Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. R C N U A hardware failure has occurred
DAP_RO C_ALM
6.1.2.[20 1,206,20 7,212].1
EMPTY
Critical
45060
R C
DAP_FR _ALM
4.[12].[16].[314318].1
45069
Frame Relay Board Failure
DAP_FR _ALM
4.[12].[16].[314318].1
HFR Board <FR board number> :HFR to Host Communica tion Down, Heartbeat Failed HFR Board <FR board number> : High CPU usage <cpu usage>
Critical
EMPTY
DAP_FR: 608 DAP_ACG_ LINK: 7,9 DAP_MDG _LINK: 7,9 DAP_APD_ LINK: 7,9 DAP_FR: 608 DAP_ACG_ LINK: 7,9 DAP_MDG _LINK: 7,9 DAP_APD_ LINK: 7,9 EMPTY
R C
A hardware failure has occurred. Where: <FR board number> = {0x01 - 0xC80} . Board recovery can be Automatic in case of heartbeat failure
Critical
EMPTY
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Verify that the DAP Configuration file has the proper ACG and Cell IDs.
R C
A hardware failure has occurred. Where: <FR board number> = {0x01 - 0xC80} . Board recovery can be Manual in case of 100% CPU
5377
Missing Cell IDs in the DAP Configuration File
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
ACG ID = <ACG_ID> Sector ID = <Sector_ID >
Major
EMPTY
During registration or registration renewal, the MS fails to retrieve the sector info, MDG region Id and primary location ID from the VLR database. This is likely to be due to a DAP configuration mismatch. Where: <ACG_ID> = {1-
CCPDAP-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
5419
Authentication failure due to SRES mismatch
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<IMSI> <Correct HLR SRES> <Incorrect MS SRES> <ACG ID> <Sector ID>
Minor
EMPTY
EMPTY
1) Contact Subscriber who owns the MS with that IMSI to verify if his MS is working well. If so, the alarm can be attributed to a rogue. 2) If MS is not working well, check for Ki if it has been changed in the MS or in the iDEN HLR.
5444
The DAP was unable to find an MDG to handle the Packet Data Registration
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<IMSI> <Number of failures> <Last MDG ID>
Major
EMPTY
EMPTY
1) Examine DAPMDG state links to verify if there are up. Concentrate on the MDG which is listed on the alarm (only the last failed is listed). 2) Monitor the MDG for other suspicious alarms.
5462
DAP cannot map to an iDEN HLR address for this IMSI
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<IMSI> <ACG ID> <Sector ID> <Transactio n type (Motorola internal use)>
Minor
EMPTY
EMPTY
1) Check the GTT tables to determine whether the specified IMSI is included in the IMSI ranges. 2) Verify the iDEN HLR configuration in the GTT tables. 3) A `rogue' or `foreign' MS is attempting to access the system.
3204} <Sector_ID> = {13} Authentication failure due to SRES mismatch. 1) A `rogue' MS has attempted to register on the system, but failed authentication.2) A legitimate MS's Ki has been changed, and it is out of sync with iDEN HLR. Where: <IMSI>= {0x00000000000000000x9999999999999999} <Correct HLR SRES> = {0x000000000x99999999} <Incorrect MS SRES> = {0x000000000x99999999} <ACG ID> = {1-3204} <Sector ID> = {1-3} DAP attempted to forward a PD registration to several MDGs, but all have failed: Time-outs or invalid responses. 1) DAP-MDG link problem. 2) MDG problem. Where: <IMSI>= {0x00000000000000000x9999999999999999} <Number of failures>= {1-10} <Last MDG ID> = {1-36} MS has attempted to register, but global title translation failed. As a result the D-VLR was not able to determine a path to the iDEN HLR for the MS. 1) GTT IMSI ranges do not include MS. 2) GTT does not properly configure the iDEN HLR. 3) A 'rogue'
October 30, 2008
CCPDAP-5

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
5465
The iDEN HLR claimed that an IMSI is unknown
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<IMSI> <ACG ID> <Sector ID> <Transactio n type (Motorola internal use)>
Minor
EMPTY
EMPTY
1) Pull up the listed IMSI at the iDEN HLR ADC. If the IDEN HLR ADC is missing, it should be added. If the record exists, verify that the IMSI is active. 2) Contact the iDEN Customer Situation Center for assistance.
5485
UF GTT lookup failed during registration
6162
Incompatible ACG_DAP interface versions
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<A CG_ID>
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
urban_id=< urban id> fleet_id=<fl eet id>
Major
EMPTY
EMPTY
The urban_id/fleet_id needs to be added to GTT
MS has attempted to register with an invalid IMSI. Where: <IMSI>= {0x00000000000000000x9999999999999999} <ACG ID> = {1-3204} <Sector ID> = {1-3} <Transaction type (Motorola internal use)> = {0x0000-0xffff} MS attempted to register, but the iDEN HLR indicates that the MS is unknown. 1) MS missing from iDEN HLR. 2) Unknown. Where: <IMSI>= {0x00000000000000000x9999999999999999} <ACG ID> = {1-3204} <Sector ID> = {1-3} <Transaction type (Motorola internal use)> = {0x0000-0xffff} 1) The UF lookup failed during registration. MM will log/report up to 10 alarms in a 5 minute interval.
DAP_CP U_ALM
1.1.2.[20 2205,207210].[13204]
processingF
6166
Incompatible
1.3.6.1.4.1.
DAP_CP
1.1.2.[20
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_ACG_ VERSION_ NEW = <VER> ACG ID = <ACG_ID> ACG'S DAP
Critical
6172
DAP_ACG_ LINK: 13
Verify that the ACG identified has the proper software load version to interface with the software version of the DAP reporting the alarm.
The ACG has requested link version checking and neither the old nor the new link version numbers match the DAP-ACG Link Version. Where: <VER> = Rxx.xx.xx <ACG_ID> = {1-3204}
Critical
6172
EMPTY
Trouble shoot
The ACG sent a link
CCPDAP-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
ailureEvent
DAP ID and/or ACG ID
161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<A CG_ID>
U_ALM
2205,207210].[13204]
ID = <DAP_ID> ACG'S ACG ID = <ACG_ID> DAP'S DAP ID = <DAP_ID>
DAP/EBTS configuration.
6170
Incompatible MDG_DAP interface versions
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.< MDG_ID>
DAP_CP U_ALM
1.1.2.[20 2205,207210].[136]
6171
Incompatible DAP ID and/or MDG ID
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.< MDG_ID>
DAP_CP U_ALM
1.1.2.[20 2205,207210].[136]
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_MDG _VERSION _NEW = <VER> MDG ID = <MDG_ID> MDG'S DAP ID = <DAP_ID> MDG'S MDG ID = <MDG_ID> DAP'S DAP ID = <DAP_ID>
Critical
6173
DAP_MDG _LINK: 13
Verify that the MDG identified has the proper software load version to interface with the software version of the DAP reporting the alarm.
version request message to the DAP but the DAP ID identified in the ITC header identified does not match the DAP ID of the DAP that received the request or the ACG ID(in the ITC header), that sent the link version message, is not present in the DAP config file. Where: <DAP_ID> = {1-15} <ACG_ID> = {1-3204} The MDG has requested link version checking and neither the old nor the new link version numbers match the DAP-MDG Link Version. Where: <VER> = Rxx.xx.xx <MDG_ID> = {1-36}
Critical
6173
EMPTY
Trouble shoot MDG configuration.
6172
ACG has not sent a link version request message to the
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1-
ACG ID = <ACG_ID>
Critical
EMPTY
EMPTY
R C
The MDG sent a link version request message to the DAP but the DAP ID identified in the ITC header identified does not match the DAP ID of the DAP that received the request or the MDG ID(in the ITC header), that sent the link version message, is not present in the DAP config file. Where: <DAP_ID> = {1-15} <MDG_ID> = {1-36} The ACG identified in the extra text has not requested a version check even though a
October 30, 2008
CCPDAP-7

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
DAP
6173
MDG has not sent a link version request message to the DAP
6174
GTT On_Line Change
ype>.<Cabi net>.<Cage >.<Slot>.<A CG_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.< MDG_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
3204]
connection has been established. Where: <ACG_ID> = {1-3204} MDG ID = <MDG_ID> Critical EMPTY EMPTY Contact the iDEN Customer Situation Center for assistance. R C N U The MDG identified in the extra text has not requested a version check even though a connection has been established. Where: <MDG_ID> = {1-36} DAP is unable to perform an OLCC of GTT data. 1) Unable to re-establish lost Sub agent-Master agent communication. 2) Unable to update memory.
DAP_CP U_ALM
1.1.2.[20 2205,207210].[136]
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
STARTING GTT OLCC
Critical
EMPTY
EMPTY
6185
GTT Initialization
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Critical
EMPTY
EMPTY
1) Check DAP alarm log for the following GTT memory alarms: ALMACP_GTT_UPD_ START ALMACP_GTT_UPD_ END ALMACP_GTT_UPD_ ISDN_TBL ALMACP_GTT_UPD_ IMSI_TBL ALMACP_GTT_UPD_ UFMI_TBL 2) Check if Sub agent-Master agent connection is up. 1) Check DAP alarm log for the following GTT memory alarms: ALMACP_GTT_INIT, ALMACP_GTT_REST ORE, ALMACP_GTT_MMA P_CORRUPTED, ALMACP_GTT_UPD_ START, ALMACP_GTT_UPD_ END, ALMACP_GTT_UPD_ ISDN_TBL, ALMACP_GTT_UPD_ IMSI_TBL, ALMACP_GTT_UPD_ UFMI_TBL or verify the subagent
R C
R C
DAP experienced problem during initialization of global titling translation table information. 1) Memory problem. 2) Unable to register to Common agent to retrieve GTT data 3) Incorrect GTT Data. 4) Can't get DAP's ISDN and IP address corresponding to the Logical Id and Uanc of current DAP.
CCPDAP-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
6186
Global Title Failure: Own Route
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<Old ISDN Address> <New ISDN Address> < UANC> <Logical Id> <IP Address>
Critical
EMPTY
EMPTY
registration failure, ALMACC_CA_REGIS TER_FAIL. 2) ALMACP_GTT_DAP_ OWN_ADDR and ALMACP_GDM_VLR _NOT_IN_VLR verify the GTT Data dump on the DAP if it contains the current DAP Id and UANC information. 1) DAP will not be able to communicate to the iDEN-HLRs and collocated iDEN-HLR will not be able to communicate to DAPs until a global title translation file containing the DAP's new routing information is downloaded. 2) DAP will not be able to communicate to the iDEN-HLRs. 3) Reconfigure the DAP's own logical Id and Uanc in the configuration file.
R C
6191
Location Area's MDG Region Id does not match ACG's MDG Region Id
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<A CG_ID>
DAP_CP U_ALM
1.1.2.[20 2205,207210].[13204]
ACG ID = <ACG_ID> MDG_REGI ON_ ID = <MDG_RE GION_ID> LA_ID = <LA_ID>
Critical
EMPTY
EMPTY
Trouble shoot the System Boundary configuration at the OMC, paying close attention to the Dispatch Location Area Identifier shown in the additional text. Insure that this Dispatch Location
DAP's own Global Title Translation Table routing is not correct. 1) If additional text indicates an ISDN address, then newly loaded Global Title Translation Table does not contain the DAP's own routing information. 2) Improperly configured DAP Logical Id and Uanc address. Where: <Old ISDN Address> <New ISDN Address> < UANC> <Logical Id> <IP Address> WHERE: <Old ISDN Address>= {000000000000001 999999999999999} <New ISDN Address>= {000000000000001 999999999999999} <Uanc> = {1-16777215} <Logical Id>= {1-15} This ACG has been assigned to a Dispatch Location Area (LA_ID) that is associated with a MDG Region id that is different than the MDG Region id identified in the extra text. Where: <MDG_REGION_ID> = {1-4} <ACG_ID> = {1-
October 30, 2008
CCPDAP-9

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
6194
Incompatible APD_DAP interface versions
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<A PD_ID>
DAP_CP U_ALM
1.1.2.[20 2205,207210].[164]
6195
Incompatible DAP ID and/or APD ID
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<A PD_ID>
DAP_CP U_ALM
1.1.2.[20 2205,207210].[164]
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_APD_ VERSION_ NEW = <VER> APD ID = <APD_ID> APD'S DAP ID = <DAP_ID> APD'S APD ID = <APD_ID> DAP'S DAP ID = <DAP_ID>
Critical
6196
DAP_APD_ LINK: 13
Area is not associated with more than one MDG Region. Verify that the APD identified has the proper software load version to interface with the software version of the DAP reporting the alarm.
3204} <LA_ID> = {19999} R N U The APD has requested link version checking and neither the old nor the new link version numbers match the DAP-APD Link Version. Where: <VER> = Rxx.xx.xx <APD_ID> = {1-64}
Critical
6196
EMPTY
Trouble shoot APD configuration.
6196
APD has not sent a link version request message to the DAP
6201
Link Version Request Timeout
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<A PD_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<D
DAP_CP U_ALM
1.1.2.[20 2205,207210].[164]
APD ID = <APD_ID>
Critical
EMPTY
EMPTY
R C
The APD sent a link version request message to the DAP but the DAP ID identified in the ITC header identified does not match the DAP ID of the DAP that received the request or the APD ID(in the ITC header), that sent the link version message, is not present in the DAP config file. Where: <DAP_ID> = {1-15} <APD_ID> = {1-64}. The APD identified in the extra text has not requested a version check even though a connection has been established. Where: <APD_ID> = {1-64} 1) The DAP that is the target of the link version request is not responding. 2) Network Congestion. 3) Network Latency. Where: <UANC> = {1-
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1300]
DAP'S UANC = <UANC> DAP ID = <DAP_ID>
Critical
EMPTY
EMPTY
1) Troubleshoot the target DAP and repair. 2) Troubleshoot the Network and repair.
R C
CCPDAP-10
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
AP_ID> processingF ailureEvent 6204 Incompatible DAP ID on DAP_DAP Interface 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<D AP_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<D AP_ID> DAP_CP U_ALM 1.1.2.[20 2205,207210].[1300] DAP'S UANC = <UANC> DAP ID = <DAP_ID> Critical EMPTY EMPTY Verify that the DAP ID and peer DAP ID configuration for each DAP match. R N U
16777215} <DAP_ID> = {1-300} Originating Peer DAP is misconfigured. Where: <UANC> = {116777215} <DAP_ID> = {1-300}
6205
Invalid Link Version
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1300]
6206
Link Version Failure
6216
Own DAP UANC not OLCCable
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<D AP_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<D AP_ID>
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1300]
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_DAP_ VERSION_ OLD = <VER> DAP_DAP_ VERSION_ NEW = <VER> UANC = <UANC> DAP ID = <DAP_ID> DAP'S UANC = <UANC> DAP ID = <DAP_ID>
Critical
EMPTY
DAP_DAP_ LINK: 13 DAP_DAP_ HN_LINK: 13
Contact the iDEN Customer Situation Center for Assistance.
Invalid Version Mismatch. Where: <UANC> = {116777215} <DAP_ID> = {1-300}
Critical
EMPTY
EMPTY
Troubleshoot DAPs and reconfigure.
Originating or peer DAP is misconfigured. Where: <UANC> = {116777215} <DAP_ID> = {1-300}
DAP_CP U_ALM
1.1.2.[20 2205,207210].[115]
Current DAP Info: <DAP_ID> <Current Uanc> OLCC DAP Info:<DAP_ ID> <New Uanc>
Critical
EMPTY
EMPTY
The DAP should be restarted for the UANC Change by OLCC to take effect.
If the DAP OLCC of UANC was not intended, this can be corrected by EGT4 correcting the configuration information and pushing the correct GTT data which will be accepted by the DAP and OLCC successful
October 30, 2008
CCPDAP-11

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
7436
DAP Rag Update Failure
7438
APD availability out of range
9488
Incompatible DAP_iDEN HLR interface versions
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<A PD_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
Requesting MDG <MDG ID>, Affected RAG <RAG ID>
Critical
EMPTY
EMPTY
Resetting of the active MDG for the RAG may be required to resync MDG ownership information in the DAP
and no alarm will be generated in that case. Where: <Current UANC> = {1-16777215} <New UANC> = {116777215} <DAP_ID> = {1-300} Indication of the Rag Management Issues. Where: <MDG ID>={136} <RAG ID>={0-31}
DAP_CP U_ALM
1.1.2.[20 2205,207210].[164]
<APD_ID>
Critical
EMPTY
EMPTY
An APD has reported an availability that is not within the range expected. Where: <APD_ID> = {1-64}
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<DAP ISDN ADDRESS > <DAP iDEN MAP APPLICATI ON CONTEXT VERSION> <iDEN HLR ISDN ADDRESS >
Critical
EMPTY
EMPTY
R C
9985
Maximum number of retries reached for an MS download request
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<RAG ID> <MDG ID>
Warning
EMPTY
EMPTY
DAP has attempted to communicate with the iDEN HLR, but the iDEN MAP APPLICATION CONTEXT VERSIONS are incompatible. Where: <DAP ISDN ADDRESS>={00000000 0000000999999999999999} <DAP iDEN MAP APPLICATION CONTEXT VERSION>= {2- 255} <iDEN HLR ISDN ADDRESS>={00000000 0000000999999999999999} MDG has not responded to MS download request and the maximum number of download retries has been reached. Where: <RAG
CCPDAP-12
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
9986
Start RAG download request failed
9991
MDG responded to an MS download request with a temporary failure
9992
MDG responded to an MS download request with an unrecoverable failure
9993
Maximum number of retries reached for a RAG download complete request
9994
MDG responded to an RAG download complete request with a temporary failure
9995
MDG responded to a RAG download complete request with an
>.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<RAG ID> <MDG ID>
Warning
EMPTY
EMPTY
ID> = {0x00-0x1f} <MDG ID> = {0x01-0x24} The RAG is already being downloaded, or the MDG requesting the RAG info does not own that RAG. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x01-0x24} The ms_download_request message failed with a temporary failure. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x01-0x24} The ms_download_request message failed with a permanent failure. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x01-0x24} An MDG RAG download request failed the maximum number of times. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x01-0x24}
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<RAG ID> <MDG ID>
Warning
EMPTY
EMPTY
No action is required at this point because the procedure will be retried.
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<RAG ID> <MDG ID>
Warning
EMPTY
EMPTY
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<RAG ID> <MDG ID>
Warning
EMPTY
EMPTY
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<RAG ID> <MDG ID>
Warning
EMPTY
EMPTY
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<RAG ID> <MDG ID>
Warning
EMPTY
EMPTY
In handling a RAG download complete request indicating a download temporary failure occurred. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x010x24} In handling a RAG download complete response indicating download unrecoverable failure occurred. Where:
October 30, 2008
CCPDAP-13

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
unrecoverable failure processingF ailureEvent 10752 Invalid iSG Connection Attempt
10753
Incompatible iSG_DAP interface versions
net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
iSG connection rejected due to no CALEA feature
Critical
EMPTY
EMPTY
<RAG ID> = {0x00-0x1f} <MDG ID> = {0x010x24} CALEA feature disabled in DAP.
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1-4]
10754
Incompatible DAP ID and/ or iSG ID
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1-4]
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_ISG_ VERSION_ NEW = <VER> ISG ID = <iSG_ ID> ISG'S DAP ID = <DAP_ID> ISG'S ISG ID = <iSG_ ID> DAP'S DAP ID = <DAP_ID>
Critical
10755
DAP_ISG_ LINK: 13
Verify that the iSG identified has the proper software load version to interface with the soft-ware version of the DAP reporting the alarm.
The ISG has requested link version checking and neither the old nor the new link version numbers match the DAP- ISG Link Version. Where: <VER> = Rxx. xx. Xx <iSG_ ID> = {14}
Critical
10755
EMPTY
Troubleshoot iSG configuration.
10755
iSG has not sent a link version request message to the DAP
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
Critical
EMPTY
EMPTY
R C
The ISG sent a link version request message to the DAP but the DAP ID identified in the ITC header identified does not match the DAP ID of the DAP that received the request or the ISG ID(in the ITC header), that sent the link version message, is not present in the DAP config file. Where: <DAP_ID> = {1- 15} <iSG_ ID> = {1- 4} The iSG identified in the extra text has not requested a version check even though a connection has been established. Where: <iSG_ ID> = {1- 4}
CCPDAP-14
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
10768
Incompatible iDAC_DAP interface versions
SG_ ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
DAP_CP U_ALM
1.1.2.[20 2205,207210].[110]
10769
Incompatible DAP ID and/or iDAC ID
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
DAP_CP U_ALM
1.1.2.[20 2205,207210].[110]
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_IDAC _VERSION _NEW = <VER> IDAC ID = <iDAC_ ID> IDAC'S DAP ID = <DAP_ID> IDAC'S IDAC ID = <iDAC_ ID> DAP'S DAP ID = <DAP_ID>
Critical
10770
DAP_IDAC _LINK: 13
Verify that the iDAC identified has the proper software load version to interface with the soft-ware version of the DAP reporting the alarm.
The IDAC has requested link version checking and neither the old nor the new link version numbers match the DAP- IDAC Link Version. Where: <VER> = Rxx.xx.xx <iDAC_ ID> = {1- 10}
Critical
10770
EMPTY
Troubleshoot iDAC configuration.
10770
iDAC has not sent a link version request message to the DAP
10774
DAP to iSG Connection Terminated
processingF
10775
DAP to iDAC
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1.
DAP_CP U_ALM
1.1.2.[20 2205,207210].[110]
IDAC ID = <iDAC_ ID>
Critical
EMPTY
EMPTY
The IDAC sent a link version request message to the DAP but the DAP ID identified in the ITC header identified does not match the DAP ID of the DAP that received the request or the IDAC ID(in the ITC header), that sent the link version message, is not present in the DAP config file. Where: <DAP_ID> = {1- 15} <iDAC_ ID> = {1- 10} The IDAC identified in the extra text has not requested a version check even though a connection has been established. Where: <iDAC_ ID> = {1- 10} 1)ISG was shutdown. 2) Ethernet Card Failure. Double Point of Failure. Where: <iSG_ ID>={1-4}
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1-4]
ISG'S ISG ID = <iSG_ ID>
Major
EMPTY
DAP_ISG_ LINK: 9, 12
1) Replace failed Ethernet card or system unit. 2) Troubleshoot Network and Repair.
R C
DAP_CP
1.1.2.[20
IDAC'S
Major
EMPTY
DAP_IDAC
1) Replace failed
1)IDAC was shutdown.
October 30, 2008
CCPDAP-15

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
ailureEvent
Connection Terminated
10786
Invalid SDG parameter
161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<D AP_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<D AP_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
_LINK: 9, 12
Ethernet card or system unit. 2) Troubleshoot Network and Repair.
2) Ethernet Card Failure. Double Point of Failure. Where: <iDAC_ ID>={110}
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1300]
Parameter = <parameter >, Value = <value>
Minor
EMPTY
EMPTY
12042
CA Poll timer creation failed
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
Creation of CA poll timer during runtime failed
Major
EMPTY
EMPTY
The SDG parameter in the DAP-DAP LVCP was invalid where : <parameter> = {SDG, iDEN SDG} <value> = {0-50} This new alarm was added to the LVCP for the iGW SDGC feature The CA poll timer could not be created by the task and therefore OLCC for this task will not be performed successfully.
13058
Current billing collection interval has been disabled
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1300]
DAP ID = <DAP_ID>
Critical
EMPTY
EMPTY
R C
An error has occurred for which the billing file could not be written. At the next billing cycle, another attempt will be made to re-enable billing. CCP failed to locate the CPU ID for the task
13837
CPU bind fail
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
cpu bind for mailbox id = <mailbox ID>, rt_val = < return value>
Major
EMPTY
EMPTY
41042
Task not running
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<Task name>(<tas k ID>) <Additional Info>
Critical
EMPTY
EMPTY
R C
A DAP task has not responded to a poll. Where: <Task name> = four letter abbreviation of task name <task ID>={0-65535}
CCPDAP-16
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
41052
SCSI Disk Problem
nstance> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<item type> <item name><err or code> <additional info>
Critical
EMPTY
EMPTY
R C
41075
Invalid IP address
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<IP address>
Critical
EMPTY
EMPTY
100000
Bad Value in the Configuration File Buffer Pool Utilization: Medium
1.3.6.1.4.1. 161.3.3.10. 2.14.1.1.0 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
CA_BAD VAL_AL M DAP_CP U_ALM
EMPTY
201
1.1.2.[20 2205,207210].1
Bad Value for OID:<object _id> <Additional Information >
Major
EMPTY
EMPTY
1)Check for proper configuration of iSG, iDAC, or remote DAP 2)Change the iSG, iDAC or remote DAP IP address via OLCC. 3) Make the iSG, iDAC, or remote DAP IP address change to the DAP configuration at OMC-R. 4) Download the latest configuration load to DAP (and/or iSG, iDAC, or remote DAP) Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance.
A disk failure has occurred. Where: <item type>={Volume, Plex, Disk group, Physical device}, <item name> = name of item text <error code>=status of item text <additional info>=additional info text 1)Misconfiguration of iSG, iDAC or remote DAP IP address 2)DAP (and/or iSG, iDAC or remote DAP) not downloaded with latest configuration data 3)Illegal device attempting connection to the DAP.
Major
EMPTY
EMPTY
R C
202
Buffer Pool Utilization: Critical
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<Additional Information >
Critical
EMPTY
EMPTY
R C
Bad Value returned in the Configuration File. Where: <object_id> = {x.x.x...} Buffers are running low. Additional text in alarm consists of Resource Usage { 1-100% }, Resource Type { MM Buffer pool , System Buffer Pool, CP Buffer Pool } MM => Mobility Management, CP=> Call Processing Buffers are running critically low. Additional text in alarm consists of Resource Usage { 1100% }, Resource Type { MM Buffer pool , System Buffer Pool, CP Buffer Pool } MM =>
October 30, 2008
CCPDAP-17

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
215
GCI Load Shedding: Call Processing
216
GCI Load Shedding: Mobility Management
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<D AP_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Major
EMPTY
EMPTY
R C
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Major
EMPTY
EMPTY
R C
218
DAP Shutting Down
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
Critical
EMPTY
DAP_NOD E: 503
No action necessary.
R C
Mobility Management, CP=> Call Processing High number of global call identifiers utilized is causing calls to be rejected. Additional text in alarm consists of Resource Type {PC/CA/MSS GCI pool, SDGC pool} High number of global call identifiers utilized is causing mobility procedures to be rejected. Additional text in alarm consists of Resource Type {PC/CA/MSS GCI pool, SDGC pool} The DAP is being shut down for maintenance or software upgrade.
219
DAP CP Shutting Down
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Critical
EMPTY
EMPTY
R C
The DAP is no longer processing calls as a result of a request to shut down the DAP.
227
DAP Restart Initiated
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1300]
Critical
228
DAP_APP: 202 DAP_CP_A PP: 202 DAP_NOD E: 503
R C
DAP will be restarted immediately
228
DAP Restart Scheduled
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1-
<Additional Information > Restart time:
Critical
227
DAP_APP: 202 DAP_CP_A PP: 202
1)The operator can perform a manual restart. 2) Disable the restart from iDEN
R C
1) When a scheduled restart is re-scheduled, the old alarm is cleared and a new DAP Restart
CCPDAP-18
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
ype>.<Cabi net>.<Cage >.<Slot>.<D AP_ID>
300]
<HH:MM:S S>
DAP_NOD E: 503
menu.
229
DAP Max Restarts Reached
231
Call Processing CPU Load Shedding: Medium
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.<D AP_ID> 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
DAP_CP U_ALM
1.1.2.[20 2205,207210].[1300]
EMPTY
Critical
227
DAP_APP: 202 DAP_CP_A PP: 202 DAP_NOD E: 503
R C
Scheduled alarm with the new time of restart is issued.2) When a scheduled restart is disabled, later when the alarm is enabled it may detect the same error which originally caused the scheduled restart.3)Unlike the set alarm, the clear alarm will not have state the time of planned restart. Restart time does not need to include the MM/DD/YYYY and hence removed. This alarm will be generated on the next attempt to restart the DAP after the maximum number of restarts limit is reached
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Major
EMPTY
DAP_LOAD _SHEDDIN G: 101,102 DAP_APP: 203,204 DAP_CP_A PP: 203, 204 DAP_NOD E: 502, 504 DAP_LOAD _SHEDDIN G: 101,102 DAP_APP: 203,204 DAP_CP_A PP: 203, 204 DAP_NOD E: 502, 504
232
Call Processing CPU Load Shedding: Critical
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Critical
EMPTY
1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Situation Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Situation Center for assistance.
R C
High CPU utilization is causing Intra-urban probing (target DAP location) to be dropped.
R C
High CPU utilization is causing Dispatch call originations (for SDGC, both initial and callback) and PD page requests to be dropped.
October 30, 2008
CCPDAP-19

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
233
DVLR Audit CPU Load Shedding: Low
234
DVLR Audit CPU Load Shedding: Medium
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Minor
EMPTY
EMPTY
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Major
EMPTY
EMPTY
237
RAG Download CPU Load Shedding: Medium
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Major
EMPTY
EMPTY
238
RAG Download CPU Load Shedding: Critical
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Critical
EMPTY
EMPTY
240
Mobility Management CPU Load Shedding: Medium
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Major
EMPTY
EMPTY
1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Contact the iDEN Customer Situation Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Situation Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Situation Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Situation Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to
High CPU utilization is causing Fleet Lifetime, MDG, and Consistency Audits to be reduced.
R C
High CPU utilization is causing all Audits (Sub/Fleet Capacity, Sub Lifetime) and Removals (fleets/modes) to be reduced.
R C
High CPU utilization is causing RAG downloads rates to be reduced
R C
High CPU utilization is causing RAG downloads to be stopped or postponed.
R C
High CPU utilization is causing background fault recovery procedures to be dropped.
CCPDAP-20
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
>.<Slot>.
242
Registration Renewal Required CPU Load Shedding: Low
100001
Time Synchronization Cannot Be Done
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1. 161.3.3.10. 2.6.1.0
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
EMPTY
Minor
EMPTY
EMPTY
CA_SNT P_ALM
EMPTY
28675
MAP Dialog Threshold Limit
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
Time Difference between NMS and NE exceeds maximum difference for synchroniza tion MAP Dialog <Additional Text>
Major
EMPTY
EMPTY
distribute load to other DAPs. 3) Contact the iDEN Customer Situation Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance.
R C
High CPU utilization is causing Registration Renewal Required procedures to be dropped.
The time difference between the NMS and the NE was larger than the maximum value for automatic synchronization to be completed.
Critical
EMPTY
EMPTY
Monitor the DAP/iHLR and/or the network traffic.
R C
36864
File System Excessive
qualityOfSer
36867
ACG in
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>. 1.3.6.1.4.1.
DAP_CP U_ALM
1.1.2.[20 2205,207210].1
<file system name >, <% utilization>
Critical
EMPTY
EMPTY
R C
DAP_FR
4.[1-
<FR board
Critical
EMPTY
EMPTY
Identify and remove
A high number of DAPiHLR procedures (likely due to registrationrelated traffic) may cause the DAP to run out of MAP Dialogs. Once that maximum limit is reached, no more DAP-iHLR procedures will be initiated until existing Dialogs complete.. <Additional Text>= "Threshold Limit Reached" or "Usage Normal" The reported file system is almost full. WHERE: <file system name> ={ a string containing the file system name (mount point with path)}, <% utilization> = {current utilization % 0 - 100%} The T1 to an ACG is
October 30, 2008
CCPDAP-21

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
viceFailureE vent
LoopBack
161.3.3.10. 5.7.1.1.2.3. 1.6.<FRUT ype>.<Cabi net>.<Cage >.<Slot>.
_ALM
2].[16].[314318].1
number>
T1 loop.
"loopback" to the DAP. The EBTS is off the air. WHERE <FR board number> = {0x01 - 0x1f}
CCPDAP-22
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
CONFIGUR ED PHYSICAL LINK UP PHYSICAL LINK DOWN PHYSICAL LINK DOWN PHYSICAL LINK DOWN PHYSICAL LINK DOWN
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE>
DAP_AC G_LINK DAP_AC G_LINK DAP_AC G_LINK
1-3204
U-D-Idl
U-D-Idl
EMPTY
EMPTY
EMPTY
1-3204
U-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
The DAP has read in the link's configuration information. MOC=1 The link's physical connection came up. MOC=1 The link's logical connection was down when its physical connection went down. MOC=1 The link was fully operational when one of its redundant link's physical connection went down. MOC=1 The link's logical connection was down when its physical connection went down. MOC=1 The (logically fault-tolerant) link had one of its logical links up and was available when its remaining physical link went down. MOC=1 The link's both physical connection and logical connection came up. MOC=1 The (logically fault-tolerant) link had one of its logical links up and was available when its remaining logical link came up. MOC=1 The (logical non-fault-tolerant) link was available and had a physical connection when its logical connection went down. MOC=1 The (logically fault-tolerant)
1-3204
U-E-A
U-D-Idl
EMPTY
32800, 45061, 45069
EMPTY
DAP_AC G_LINK
1-3204
U-E-A
U-E-Imp
EMPTY
32800, 45061, 45069
EMPTY
DAP_AC G_LINK
1-3204
U-E-Idl
U-D-Idl
EMPTY
32800, 45061, 45069
EMPTY
DAP_AC G_LINK
1-3204
U-E-Imp
U-D-Idl
EMPTY
32800, 45061, 45069
EMPTY
LOGICAL LINK UP LOGICAL LINK UP
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE>
DAP_AC G_LINK DAP_AC G_LINK
1-3204
U-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
1-3204
U-E-Imp
U-E-A
EMPTY
EMPTY
EMPTY
LOGICAL LINK DOWN
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE>
DAP_AC G_LINK
1-3204
U-E-A
U-E-Idl
EMPTY
32800, 45061, 45069
Logical Link is no longer connected to NE
esmrStateCh
LOGICAL
1.3.6.1.4.1.161.3.3.10.
DAP_AC
1-3204
U-E-A
U-E-Imp
EMPTY
32800, 45061,
Logical Link is no
October 30, 2008
CCPDAP-23

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s link had both its logical links up and was available when one of its logical links went down. MOC=1 The (logically fault-tolerant) link had one of its logical links up and was available when its remaining logical link went down. MOC=1 The link's logical connection was totally up when link version checking succeeded. MOC=1 The link's logical connection was partially up when link version checking succeeded. MOC=1 The link was deleted from OLCC operation. MOC=1 The link was deleted from OLCC operation. MOC=1 The link was deleted from OLCC operation. MOC=1 The link was deleted from OLCC operation. MOC=1 The link was fully operational when link version check was conducted but failed. MOC=1 The (logically fault-tolerant) link had one of its logical links up and was available when link version check was conducted but failed. MOC=1 Application has been started/automatically restarted. MOC=10; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing Application has failed. MOC=10; Instances: 1 = Mobility Management, 2 =
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
angeEvent
LINK DOWN
5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE>
G_LINK
45069
longer connected to NE
LOGICAL LINK DOWN
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE>
DAP_AC G_LINK
1-3204
U-E-Imp
U-E-Idl
EMPTY
32800, 45061, 45069
1 0
1 0
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
1 1 1 1 1 1 1 1 1 3 1 3
VERSION CHECK SUCCEEDE D VERSION CHECK SUCCEEDE D TERMINAT ED BY DAP TERMINAT ED BY DAP TERMINAT ED BY DAP TERMINAT ED BY DAP VERSION CHECK FAILED VERSION CHECK FAILED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.1.<UAN C>.<INSTANCE>
DAP_AC G_LINK
1-3204
U-E-Idl
U-E-A
EMPTY
EMPTY
Version check succeeded
DAP_AC G_LINK
1-3204
U-E-Idl
U-E-Imp
EMPTY
EMPTY
DAP_AC G_LINK DAP_AC G_LINK DAP_AC G_LINK DAP_AC G_LINK DAP_AC G_LINK DAP_AC G_LINK
1-3204
U-E-A
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-3204
U-E-Imp
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-3204
U-E-Idl
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-3204
U-D-Idl
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-3204
U-E-A
U-E-Idl
EMPTY
6162
Version check failed Version check failed
1-3204
U-E-Imp
U-E-Idl
EMPTY
6162
2 0 1
APPLICATI ON STARTED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.10.<UA NC>.<INSTANCE>
DAP_AP P
1-4
U-D-Idl
U-E-A
EMPTY
EMPTY
DAP is starting up
2 0 2
APPLICATI ON FAILED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.10.<UA NC>.<INSTANCE>
DAP_AP P
1-4
U-E-A
U-D-Idl
EMPTY
227, 228, 229
EMPTY
CCPDAP-24
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
2 0 2
APPLICATI ON FAILED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.10.<UA NC>.<INSTANCE>
DAP_AP P
1-4
U-E-Imp
U-D-Idl
EMPTY
227, 228, 229
EMPTY
2 0 3
LOAD SHEDDING ACTIVE
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.10.<UA NC>.<INSTANCE>
DAP_AP P
1-4
U-D-Idl
U-E-Imp
EMPTY
231, 232
Application started while processing load is too high
2 0 3
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.10.<UA NC>.<INSTANCE>
DAP_AP P
1-4
U-E-A
U-E-Imp
EMPTY
231, 232
EMPTY
2 0 4
LOAD SHEDDING INACTIVE
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.10.<UA NC>.<INSTANCE>
DAP_AP P
1-4
U-E-Imp
U-E-A
EMPTY
231, 232
Load Shedding is cleared
2 0 1
APPLICATI ON STARTED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.22.<UA NC>.<INSTANCE>
DAP_CP _APP
1-4
U-D-Idl
U-E-A
EMPTY
EMPTY
DAP is starting up
2 0 2
APPLICATI ON FAILED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.22.<UA NC>.<INSTANCE>
DAP_CP _APP
1-4
U-E-A
U-D-Idl
EMPTY
227, 228, 229
EMPTY
2 0 2
APPLICATI ON FAILED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.22.<UA NC>.<INSTANCE>
DAP_CP _APP
1-4
U-E-Imp
U-D-Idl
EMPTY
227, 228, 229
EMPTY
2 0 3
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.22.<UA NC>.<INSTANCE>
DAP_CP _APP
1-4
U-D-Idl
U-E-Imp
EMPTY
231, 232
EMPTY
Call Processing, 3 = Billing, 4 = I/O Routing Application has failed. MOC=10; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing Application is being impacted by load shedding procedures. MOC=10; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing Application is being impacted by load shedding procedures. MOC=10; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing Application is no longer being impacted by load shedding procedures. MOC=10; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing Application has been started/automatically restarted. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Application has failed. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Application has failed. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Application is loadshedding. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 =
October 30, 2008
CCPDAP-25

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s U Selective Dynamic Group Call Application is loadshedding. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Application is not loadshedding. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Critical application functionality has been lost. MOC=11 Critical application functionality has been lost. MOC=11 All applications are fully operational. MOC=11
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
2 0 3
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.22.<UA NC>.<INSTANCE>
DAP_CP _APP
1-4
U-E-A
U-E-Imp
EMPTY
231, 232
EMPTY
2 0 4
LOAD SHEDDING INACTIVE
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.22.<UA NC>.<INSTANCE>
DAP_CP _APP
1-4
U-E-Imp
U-E-A
EMPTY
231, 232
EMPTY
3 0 1 3 0 1 3 0 2
3 0 2
3 0 3
3 0 3
6 0 7
CRITICAL FUNCTION ALITY LOST CRITICAL FUNCTION ALITY LOST ALL APPLICATI ONS FUNCTION AL ALL APPLICATI ONS FUNCTION AL ONE OR MORE APPLICATI ONS NOT FUNCTION AL ONE OR MORE APPLICATI ONS NOT FUNCTION AL FRU RESTORED FULL FUNCTION ALITY
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.11.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.11.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.11.<UA NC>.<INSTANCE>
DAP_AP P_ROLL UP DAP_AP P_ROLL UP DAP_AP P_ROLL UP
U-E-A
U-D-Idl
202
EMPTY
The application has shutdown
U-E-Imp
U-D-Idl
202
EMPTY
U-D-Idl
U-E-A
201
EMPTY
DAP is starting up
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.11.<UA NC>.<INSTANCE>
DAP_AP P_ROLL UP
U-E-Imp
U-E-A
201
EMPTY
Tasks no longer load shedding
All applications are fully operational. MOC=11
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.11.<UA NC>.<INSTANCE>
DAP_AP P_ROLL UP
U-D-Idl
U-E-Imp
202
EMPTY
Task not responding to poll
One or more applications are not fully operational. MOC=11
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.11.<UA NC>.<INSTANCE>
DAP_AP P_ROLL UP
U-E-A
U-E-Imp
202
EMPTY
Task is impaired due to load shedding
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.102..<INSTANCE>
DAP_CP U
1-2
U-D-Idl
U-E-A
EMPTY
EMPTY
EMPTY
FRUs have become operational. CPU: MOC=102 Instance=1-2
CCPDAP-26
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
6 0 8 9
FRU LOST FUNCTION ALITY LOGICAL LINK DOWN VERSION CHECK SUCCEEDE D TERMINAT ED BY DAP TERMINAT ED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED LOGICAL LINK DOWN VERSION CHECK SUCCEEDE D TERMINAT ED BY DAP TERMINAT ED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED PARTIAL LINK CONNECTI VITY
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.102..<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.20.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.20.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.20.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.20.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.20.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.20.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.8.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.8.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.8.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.8.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.8.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.8.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.12.<UA NC>.<INSTANCE>
DAP_CP U
1-2
U-E-A
U-D-Idl
603
45060
EMPTY
1 0
DAP_DA P_HN_LI NK DAP_DA P_HN_LI NK DAP_DA P_HN_LI NK DAP_DA P_HN_LI NK DAP_DA P_HN_LI NK DAP_DA P_HN_LI NK DAP_DA P_LINK DAP_DA P_LINK
1-300
U-E-A
U-D-Idl
EMPTY
1296, 32806. 32807 EMPTY
1-300
U-D-Idl
U-E-A
EMPTY
Logical Link is no longer connected to NE Version check succeeded
1 1 1 1 1 2 1 3
1-300
U-E-A
U-D-Idl
EMPTY
EMPTY
Deleted Link
FRUs have become nonoperational or have been removed. CPU: MOC=102 Instance=1-2 TCP/IP connectivity lost; inter urban link. OMC display UANC. MOC=20 Link Version Check procedure passed; inter urban link. OMC display UANC. MOC=20 The link was deleted from OLCC operation. MOC=20 The link was deleted from OLCC operation. MOC=20 Link Status Check has failed; inter urban link. OMC display UANC. MOC=20 Link Version Check procedure failed; inter urban link. OMC display UANC. MOC=20 TCP/IP connectivity lost; intra urban link. MOC=8 Link Version Check Procedure passed; intra urban link. MOC=8 The link was deleted from OLCC operation. MOC=8 The link was deleted from OLCC operation. MOC=8 Link Status Check has failed; intra urban link. MOC=8 Link Version Check procedure failed; intra urban link. MOC=8 One or more DAP links to the peer DAP are not fully operational. This rollup only applies to local DAP-DAP
1-300
U-D-Idl
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-300
U-E-A
U-D-Idl
EMPTY
1296, 32806. 32807 6205
Heartbeat check failure Version check failed
1-300
U-E-A
U-D-Idl
EMPTY
1-15
U-E-A
U-D-Idl
EMPTY
1296, 32806. 32807 EMPTY
1 0
1-15
U-D-Idl
U-E-A
EMPTY
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
1 1 1 1 1 2 1 3 4 0 1
DAP_DA P_LINK DAP_DA P_LINK DAP_DA P_LINK DAP_DA P_LINK DAP_DA P_LINK_ ROLLUP
1-15
U-E-A
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-15
U-D-Idl
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-15
U-E-A
U-D-Idl
EMPTY
1296, 32806. 32807 6205
Heartbeat check failure Version check failed Partial Link connectivity
1-15
U-E-A
U-D-Idl
EMPTY
U-D-Idl
U-E-Imp
10
EMPTY
October 30, 2008
CCPDAP-27

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s U links. MOC=12 One or more DAP links to the peer DAP are not fully operational. This rollup only applies to local DAP-DAP links. MOC=12 All DAP links to the peer DAP are failed. This rollup only applies to local DAP-DAP links. MOC=12 All DAP links to the peer DAP are failed. This rollup only applies to local DAP-DAP links. MOC=12 All DAP links to the peer DAP are fully operational. This rollup only applies to local DAP-DAP links. MOC=12 All DAP links to the peer DAP are fully operational. This rollup only applies to local DAP-DAP links. MOC=12 FRUs has become operational. FR: MOC=103 Instance=1-32
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
4 0 1
PARTIAL LINK CONNECTI VITY ALL LINKS FAILED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.12.<UA NC>.<INSTANCE>
DAP_DA P_LINK_ ROLLUP
U-E-A
U-E-Imp
9, 12, 13
EMPTY
Partial Link connectivity
4 0 2 4 0 2 4 0 3 4 0 3 6 0 7
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.12.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.12.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.12.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.12.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.103..<INSTANCE>
DAP_DA P_LINK_ ROLLUP DAP_DA P_LINK_ ROLLUP DAP_DA P_LINK_ ROLLUP DAP_DA P_LINK_ ROLLUP DAP_FR
U-E-Imp
U-D-Idl
9, 12, 13
EMPTY
All links failed
ALL LINKS FAILED
U-E-A
U-D-Idl
9, 12, 13
EMPTY
All links failed
ALL LINKS OPERATIO NAL ALL LINKS OPERATIO NAL FRU RESTORED FULL FUNCTION ALITY FRU LOST FUNCTION ALITY LOGICAL LINK DOWN VERSION CHECK SUCCEEDE D TERMINAT ED BY DAP TERMINAT ED BY DAP STATUS CHECK FAILED
U-E-Imp
U-E-A
10, 11
EMPTY
All links operational
U-D-Idl
U-E-A
10, 11
EMPTY
1-32
U-D-Idl
U-E-A
EMPTY
EMPTY
EMPTY
6 0 8 9
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.103..<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.21.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.21.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.21.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.21.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.21.<UA NC>.<INSTANCE>
DAP_FR
1-32
U-E-A
U-D-Idl
603
45061, 45069
EMPTY
1 0
DAP_HL R_HN_LI NK DAP_HL R_HN_LI NK DAP_HL R_HN_LI NK DAP_HL R_HN_LI NK DAP_HL R_HN_LI NK
1-300
U-E-A
U-D-Idl
EMPTY
32807
1-300
U-D-Idl
U-E-A
EMPTY
EMPTY
1 1 1 1 1 2
1-300
U-E-A
U-D-Idl
EMPTY
EMPTY
Deleted Link
FRUs has become nonoperational or have been removed. FR: MOC=103 Instance=1-32 TCP/IP connectivity lost; inter urban link. OMC display UANC. MOC=21 Link Version Check procedure passed; inter urban link. OMC display UANC. MOC=21 The link was deleted from OLCC operation. MOC=21 The link was deleted from OLCC operation. MOC=21 Link Status Check has failed; inter urban link. OMC display UANC. MOC=21
1-300
U-D-Idl
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-300
U-E-A
U-D-Idl
EMPTY
32807
Heartbeat check failure
CCPDAP-28
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 3
VERSION CHECK FAILED OPERATOR TERMINAT ED CONNECTI ON LOGICAL LINK DOWN VERSION CHECK SUCCEEDE D TERMINAT ED BY DAP TERMINAT ED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED OPERATOR TERMINAT ED CONNECTI ON PARTIAL LINK CONNECTI VITY PARTIAL LINK CONNECTI VITY ALL LINKS FAILED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.21.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.21.<UA NC>.<INSTANCE>
DAP_HL R_HN_LI NK DAP_HL R_HN_LI NK
1-300
U-E-A
U-D-Idl
EMPTY
EMPTY
Version check failed
1 4
1-300
U-E-A
U-D-Idl
EMPTY
EMPTY
Operator Terminated connection
Link Version Check procedure failed; inter urban link. OMC display UANC. MOC=21 Operator terminated this link; inter urban link. OMC display UANC. MOC=21
1 0
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.3.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.3.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.3.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.3.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.3.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.3.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.3.<UAN C>.<INSTANCE>
DAP_HL R_LINK DAP_HL R_LINK
1-8
U-E-A
U-D-Idl
EMPTY
32807
1-8
U-D-Idl
U-E-A
EMPTY
EMPTY
TCP/IP connectivity lost; intra urban link. MOC=3 Link Version Check procedure passed; intra urban link. MOC=3 The link was deleted from OLCC operation. MOC=3 The link was deleted from OLCC operation. MOC=3 Link Status Check has failed; intra urban link. MOC=3 Link Version Check procedure failed; intra urban link. MOC=3 Operator terminated this link; inter urban link. MOC=3
1 1 1 1 1 2 1 3 1 4
DAP_HL R_LINK DAP_HL R_LINK DAP_HL R_LINK DAP_HL R_LINK DAP_HL R_LINK
1-8
U-E-A
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-8
U-D-Idl
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-8
U-E-A
U-D-Idl
EMPTY
32807
Heartbeat check failure Version check failed Operator Terminated connection
1-8
U-E-A
U-D-Idl
EMPTY
EMPTY
1-8
U-E-A
U-D-Idl
EMPTY
EMPTY
4 0 1
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.13.<UA NC>.<INSTANCE>
DAP_HL R_LINK_ ROLLUP
U-D-Idl
U-E-Imp
10
EMPTY
4 0 1
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.13.<UA NC>.<INSTANCE>
U-E-A
U-E-Imp
9, 12, 13, 14
EMPTY
4 0 2
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.13.<UA NC>.<INSTANCE>
U-E-Imp
U-D-Idl
9, 12, 13, 14
EMPTY
All links failed
One or more DAP links to the iHLR are not fully operational. This rollup only applies to local DAP-HLR links. MOC=13 One or more DAP links to the iHLR are not fully operational. This rollup only applies to local DAP-HLR links. MOC=13 All DAP links to the iHLR are failed. This rollup only applies to local DAP-HLR links. MOC=13
October 30, 2008
CCPDAP-29

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s U
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
4 0 2 4 0 3
ALL LINKS FAILED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.13.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.13.<UA NC>.<INSTANCE>
DAP_HL R_LINK_ ROLLUP DAP_HL R_LINK_ ROLLUP
U-E-A
U-D-Idl
9, 12, 13, 14
EMPTY
All links failed
ALL LINKS OPERATIO NAL
U-E-Imp
U-E-A
10, 11
EMPTY
4 0 3
ALL LINKS OPERATIO NAL
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.13.<UA NC>.<INSTANCE>
U-D-Idl
U-E-A
10, 11
EMPTY
6 0 1
6 0 2
6 0 3
6 0 4
6 0 5
esmrStateCh
HW CONTAINE R RESTORED FULL FUNCTION ALITY HW CONTAINE R LOST FULL FUNCTION ALITY HW CONTAINE R LOST PARTIAL FUNCTION ALITY HW CONTAINE R LOST FULL FUNCTION ALITY HW CONTAINE R RESTORED PARTIAL FUNCTION ALITY HW
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.101..<INSTANCE>
DAP_H W_CON TAINER
U-D-Idl
U-E-A
607
45058-45066
EMPTY
All DAP links to the iHLR are failed. This rollup only applies to local DAP-HLR links. MOC=13 All DAP links to the network element are fully operational. This rollup only applies to local DAP-HLR links. MOC=13 All DAP links to the network element are fully operational. This rollup only applies to local DAP-HLR links. MOC=13 HW Container has become operational. MOC=101
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.101..<INSTANCE>
DAP_H W_CON TAINER
U-E-A
U-D-Idl
EMPTY
45058-45066
EMPTY
Certain HW Container functionality has been lost. For example, Ethernet cards are failed. MOC=101
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.101..<INSTANCE>
DAP_H W_CON TAINER
U-E-A
U-E-Imp
EMPTY
45058-45066
EMPTY
HW Container has partially failed - one or more FRUs are not operational. MOC=101
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.101..<INSTANCE>
DAP_H W_CON TAINER
U-E-Imp
U-D-Idl
EMPTY
45058-45066
EMPTY
Certain HW Container functionality has been lost. For example, Ethernet cards are failed. MOC=101
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.101..<INSTANCE>
DAP_H W_CON TAINER
U-D-Idl
U-E-Imp
EMPTY
45058-45066
EMPTY
Operation of HW Container is partially restored. Still one or more FRUs, but not all of FRUs of the same fru type, are failed. MOC=101
1.3.6.1.4.1.161.3.3.10.
DAP_H
U-E-Imp
U-E-A
EMPTY
45058-45066
EMPTY
All HW Container's FRUs are
CCPDAP-30
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 6
1 0
1 1 1 1 1 2 1 3 4 0 1 4 0 1 4 0 2 4 0 2 4 0 3 4 0
CONTAINE R RESTORED FULL FUNCTION ALITY LOGICAL LINK DOWN VERSION CHECK SUCCEEDE D TERMINAT ED BY DAP TERMINAT ED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED PARTIAL LINK CONNECTI VITY PARTIAL LINK CONNECTI VITY ALL LINKS FAILED
5.7.1.1.2.5.1.4.101..<INSTANCE>
W_CON TAINER
fully operational. MOC=101
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.18.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.18.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.18.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.18.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.18.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.18.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.19.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.19.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.19.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.19.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.19.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.19.<UA
DAP_ID AC_LINK DAP_ID AC_LINK
1-10
U-E-A
U-D-Idl
EMPTY
10775, 32806, 32807 EMPTY
1-10
U-D-Idl
U-E-A
EMPTY
TCP/IP connectivity lost. MOC=18 Link Version Check procedure passed. MOC=18
DAP_ID AC_LINK DAP_ID AC_LINK DAP_ID AC_LINK DAP_ID AC_LINK DAP_ID AC_LINK _ROLLU P DAP_ID AC_LINK _ROLLU P DAP_ID AC_LINK _ROLLU P DAP_ID AC_LINK _ROLLU P DAP_ID AC_LINK _ROLLU P DAP_ID AC_LINK
1-10
U-E-A
U-D-Idl
EMPTY
EMPTY
Deleted Link
The link was deleted from OLCC operation. MOC=18 The link was deleted from OLCC operation. MOC=18 Link Status Check has failed. MOC=18 Link Version Check procedure failed. MOC=18 One or more DAP links to the iDAC are not fully operational. MOC=19 One or more DAP links to the iDAC are not fully operational. MOC=19 All DAP links to the iDAC are failed. MOC=19
1-10
U-D-Idl
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-10
U-E-A
U-D-Idl
EMPTY
10775, 32806, 32807 10768
1-10
U-E-A
U-D-Idl
EMPTY
U-D-Idl
U-E-Imp
10
EMPTY
U-E-A
U-E-Imp
9, 12, 13
EMPTY
U-E-Imp
U-D-Idl
9, 12, 13
EMPTY
All links failed
ALL LINKS FAILED
U-E-A
U-D-Idl
9, 12, 13
EMPTY
All links failed
All DAP links to the iDAC are failed. MOC=19
ALL LINKS OPERATIO NAL ALL LINKS OPERATIO
U-E-Imp
U-E-A
10, 11
EMPTY
All DAP links to the iDAC are fully operational. MOC=19
U-D-Idl
U-E-A
10, 11
EMPTY
All DAP links to the iDAC are fully operational. MOC=19
October 30, 2008
CCPDAP-31

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
3 esmrStateCh angeEvent esmrStateCh angeEvent 9
NAL LOGICAL LINK DOWN VERSION CHECK SUCCEEDE D TERMINAT ED BY DAP TERMINAT ED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED PARTIAL LINK CONNECTI VITY PARTIAL LINK CONNECTI VITY ALL LINKS FAILED ALL LINKS FAILED ALL LINKS OPERATIO NAL ALL LINKS OPERATIO NAL PROCESSI NG LOAD TOO HIGH PROCESSI
NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.7.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.7.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.7.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.7.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.7.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.7.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.16.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.16.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.16.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.16.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.16.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.16.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.9.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10.
_ROLLU P DAP_IS G_LINK DAP_IS G_LINK
1-4
U-E-A
U-D-Idl
EMPTY
10774, 32806, 32807 EMPTY
1 0
1-4
U-D-Idl
U-E-A
EMPTY
TCP/IP connectivity broken. MOC=7 Link Version Check Procedure passed. MOC=7
1 1 1 1 1 2 1 3 4 0 1 4 0 1 4 0 2 4 0 2 4 0 3 4 0 3 1 0 1 1
DAP_IS G_LINK DAP_IS G_LINK DAP_IS G_LINK DAP_IS G_LINK DAP_IS G_LINK_ ROLLUP DAP_IS G_LINK_ ROLLUP DAP_IS G_LINK_ ROLLUP DAP_IS G_LINK_ ROLLUP DAP_IS G_LINK_ ROLLUP DAP_IS G_LINK_ ROLLUP DAP_LO AD_SHE DDING DAP_LO
1-4
U-E-A
U-D-Idl
EMPTY
EMPTY
Deleted Link
The link was deleted from OLCC operation. MOC=7 The link was deleted from OLCC operation. MOC=7 iSG is not sending a heartbeat message. MOC=7 Link Version Check procedure failed. MOC=7 One or more DAP links to the iSG are not fully operational. MOC=16 One or more DAP links to the iSG are not fully operational. MOC=16 All DAP links to the iSG are failed. MOC=16 All DAP links to the iSG are failed. MOC=16 All DAP links to the iSG are fully operational. MOC=16 All DAP links to the iSG are fully operational. MOC=16 The DAP processing load has exceeded its `normal' level and load shedding has been initiated. MOC=9 The DAP processing load has
1-4
U-D-Idl
U-D-Idl
EMPTY
EMPTY
Deleted Link
1-4
U-E-A
U-D-Idl
EMPTY
10774, 32806, 32807 10753
1-4
U-E-A
U-D-Idl
EMPTY
U-D-Idl
U-E-Imp
10
EMPTY
U-E-A
U-E-Imp
9, 12, 13
EMPTY
U-E-Imp
U-D-Idl
9, 12, 13
EMPTY
All links failed
U-E-A
U-D-Idl
9, 12, 13
EMPTY
All links failed
U-E-Imp
U-E-A
10, 11
EMPTY
U-D-Idl
U-E-A
10, 11
EMPTY
U-E-Idl
U-E-A
203
231, 232
Call Processing is loadshedding
esmrStateCh
U-E-A
U-E-Idl
204
231, 232
Call Processing is
CCPDAP-32
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 2 1
NG LOAD NORMAL CONFIGUR ED PHYSICAL LINK UP PHYSICAL LINK DOWN PHYSICAL LINK DOWN
5.7.1.1.2.5.1.4.9.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE>
AD_SHE DDING DAP_MD G_LINK DAP_MD G_LINK DAP_MD G_LINK 1-36 U-D-Idl U-D-Idl EMPTY EMPTY
not loadshedding
EMPTY
1-36
U-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
returned to its `normal' level and any load shedding has been terminated. MOC=9 The DAP has read in the link's configuration information. MOC=4 The link's physical connection came up. MOC=4 The link was fully operational when both of its physical connection went down. MOC=4 The (logically fault-tolerant) link had both its logical links up and was available when one of its physical links went down. MOC=4 The link's logical connection was down when its physical connection went down. MOC=4 The link's logical connection was down when its physical connection went down. MOC=4 The link's both physical connection and logical connection came up. MOC=4 The (logically fault-tolerant) link had one of its logical links up and was available when its remaining logical link came up. MOC=4 The (logical non-fault-tolerant) link was available and had both physical connections when both of its logical connections went down. MOC=4 The (logically fault-tolerant) link had both its logical links up and was available when one of its logical links went down. MOC=4 The (logically fault-tolerant) link had one of its logical links
1-36
U-E-A
U-D-Idl
EMPTY
32800, 45061, 45069
EMPTY
DAP_MD G_LINK
1-36
U-E-A
U-E-Imp
EMPTY
32800, 45061, 45069
EMPTY
PHYSICAL LINK DOWN PHYSICAL LINK DOWN LOGICAL LINK UP LOGICAL LINK UP
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE>
DAP_MD G_LINK
1-36
U-E-Idl
U-D-Idl
EMPTY
32800, 45061, 45069
EMPTY
DAP_MD G_LINK
1-36
U-E-Imp
U-D-Idl
EMPTY
32800, 45061, 45069
EMPTY
DAP_MD G_LINK DAP_MD G_LINK
1-36
U-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
1-36
U-E-Imp
U-E-A
EMPTY
EMPTY
EMPTY
LOGICAL LINK DOWN
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE>
DAP_MD G_LINK
1-36
U-E-A
U-E-Idl
EMPTY
32800, 45061, 45069
LOGICAL LINK DOWN
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE>
DAP_MD G_LINK
1-36
U-E-A
U-E-Imp
EMPTY
32800, 45061, 45069
LOGICAL LINK
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN
DAP_MD G_LINK
1-36
U-E-Imp
U-E-Idl
EMPTY
32800, 45061, 45069
Logical Link is no longer connected
October 30, 2008
CCPDAP-33

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s up and was available when its remaining logical link went down. MOC=4 The link's logical connection was totally up when link version checking succeeded. MOC=4 The link's logical connection was partially up when link version checking succeeded. MOC=4 The link was fully operational when link version check was conducted but failed. MOC=4 The (logically fault-tolerant) link had one of its logical links up and was available when link version check was conducted but failed. MOC=4 One or more (but not all) DAP links to the MDG have failed (in state UDI). MOC=15 One or more (but not all) DAP links to the MDG have failed (in state UDI). MOC=15 All DAP links to the MDG are failed (in state UDI). MOC=15 All DAP links to the MDG are failed (in state UDI). MOC=15 All DAP links to the MDG are fully operational (in state UEA). MOC=15 All DAP links to the MDG are fully operational (in state UEA). MOC=15 FRUs has become operational. NIOC: MOC=105 Instance=1-2
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
DOWN
C>.<INSTANCE>
to NE
1 0
1 0
1 3 1 3
VERSION CHECK SUCCEEDE D VERSION CHECK SUCCEEDE D VERSION CHECK FAILED VERSION CHECK FAILED
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.4.<UAN C>.<INSTANCE>
DAP_MD G_LINK
1-36
U-E-Idl
U-E-A
EMPTY
EMPTY
DAP_MD G_LINK
1-36
U-E-Idl
U-E-Imp
EMPTY
EMPTY
DAP_MD G_LINK DAP_MD G_LINK
1-36
U-E-A
U-E-Idl
EMPTY
6170
Version check failed Version check failed
1-36
U-E-Imp
U-E-Idl
EMPTY
6170
4 0 1 4 0 1 4 0 2 4 0 2 4 0 3 4 0 3 6 0 7
PARTIAL LINK CONNECTI VITY PARTIAL LINK CONNECTI VITY ALL LINKS FAILED ALL LINKS FAILED ALL LINKS OPERATIO NAL ALL LINKS OPERATIO NAL FRU RESTORED FULL FUNCTION ALITY FRU LOST FUNCTION ALITY
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.15.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.15.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.15.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.15.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.15.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.15.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.105..<INSTANCE>
DAP_MD G_LINK_ ROLLUP DAP_MD G_LINK_ ROLLUP DAP_MD G_LINK_ ROLLUP DAP_MD G_LINK_ ROLLUP DAP_MD G_LINK_ ROLLUP DAP_MD G_LINK_ ROLLUP DAP_NI OC
U-D-Idl
U-E-Imp
10
EMPTY
U-E-A
U-E-Imp
7, 9
EMPTY
U-E-Imp
U-D-Idl
7, 9
EMPTY
All links failed
U-E-A
U-D-Idl
7, 9
EMPTY
All links failed
U-E-Imp
U-E-A
10
EMPTY
U-D-Idl
U-E-A
10
EMPTY
1-2
U-D-Idl
U-E-A
EMPTY
EMPTY
EMPTY
6 0 8
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.105..<INSTANCE>
DAP_NI OC
1-2
U-E-A
U-D-Idl
603
45065
EMPTY
FRUs has become nonoperational or have been removed. NIOC: MOC=105
CCPDAP-34
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
5 0 1
5 0 1
5 0 2
5 0 3 5 0 3 5 0 3 5 0 4
NODE RESTORED FULL FUNCTION ALITY NODE RESTORED FULL FUNCTION ALITY NODE LOST PARTIAL FUNCTION ALITY NODE LOST FULL FUNCTION ALITY NODE LOST FULL FUNCTION ALITY NODE LOST FULL FUNCTION ALITY NODE RESTORED PARTIAL FUNCTION ALITY CONFIGUR ED PHYSICAL LINK UP PHYSICAL LINK DOWN PHYSICAL LINK DOWN LOGICAL
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.17.<UA NC>.<INSTANCE>
DAP_NO DE
U-D-Idl
U-E-A
302, 601
EMPTY
EMPTY
Instance=1-2 The DAP has restored full functionality. MOC=17
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.17.<UA NC>.<INSTANCE>
DAP_NO DE
U-E-Imp
U-E-A
302, 601
EMPTY
EMPTY
The DAP has restored full functionality. MOC=17
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.17.<UA NC>.<INSTANCE>
DAP_NO DE
U-E-A
U-E-Imp
303, 603
231, 232
EMPTY
The DAP has lost partial functionality. MOC=17
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.17.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.17.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.17.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.17.<UA NC>.<INSTANCE>
DAP_NO DE
U-D-Idl
U-D-Idl
301, 602
218, 227, 228, 229
EMPTY
The DAP has lost full functionality. MOC=17
DAP_NO DE
U-E-A
U-D-Idl
301, 602
218, 227, 228, 229
EMPTY
DAP_NO DE
U-E-Imp
U-D-Idl
301, 602
218, 227, 228, 229
EMPTY
DAP_NO DE
U-D-Idl
U-E-Imp
303, 605
231, 232
EMPTY
The DAP has restored partial functionality. MOC=17
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.6.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.6.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.6.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.6.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10.
DAP_AP D_LINK DAP_AP D_LINK DAP_AP D_LINK DAP_AP D_LINK
1-64
U-D-Idl
U-D-Idl
EMPTY
EMPTY
EMPTY
1-64
U-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
The DAP has read in the link's configuration information. MOC=6 The link's physical connection came up. MOC=6 The link was fully operational when its physical connection went down. MOC=6 The link's logical connection was down when its physical connection went down. MOC=6 The link's both physical
1-64
U-E-A
U-D-Idl
EMPTY
32800, 45061, 45069 32800, 45061, 45069
EMPTY
1-64
U-E-Idl
U-D-Idl
EMPTY
EMPTY
esmrStateCh
DAP_AP
1-64
U-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
October 30, 2008
CCPDAP-35

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s connection and logical connection came up. MOC=6 The link was fully operational when its logical connection went down. MOC=6 The Link's Logical Connection was totally up when link version checking succeeded. MOC=6 The link was fully operational when link version check was conducted but failed. MOC=6 One or more (but not all) DAP links to the APD have failed (in state UDI). MOC=14 One or more (but not all) DAP links to the APD have failed (in state UDI). MOC=14 All DAP links to the APD are failed (in state UDI). MOC=14 All DAP links to the APD are failed (in state UDI). MOC=14 All DAP links to the APD are fully operational (in state UEA). MOC=14 All DAP links to the APD are fully operational (in state UEA). MOC=14 FRUs has become operational. SCSI: MOC=104 Instance=1-12
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent 9
LINK UP LOGICAL LINK DOWN VERSION CHECK SUCCEEDE D VERSION CHECK FAILED PARTIAL LINK CONNECTI VITY PARTIAL LINK CONNECTI VITY ALL LINKS FAILED ALL LINKS FAILED ALL LINKS OPERATIO NAL ALL LINKS OPERATIO NAL FRU RESTORED FULL FUNCTION ALITY FRU LOST FUNCTION ALITY
1 0
5.7.1.1.2.5.1.4.6.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.6.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.6.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.6.<UAN C>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.14.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.14.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.14.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.14.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.14.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.14.<UA NC>.<INSTANCE> 1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.104..<INSTANCE>
D_LINK DAP_AP D_LINK DAP_AP D_LINK 1-64 U-E-A U-E-Idl EMPTY 32800, 45061, 45069 EMPTY Logical Link is no longer connected to NE Version check succeeded N U
1-64
U-E-Idl
U-E-A
EMPTY
1 3 4 0 1 4 0 1 4 0 2 4 0 2 4 0 3 4 0 3 6 0 7
DAP_AP D_LINK DAP_AP D_LINK_ ROLLUP DAP_AP D_LINK_ ROLLUP DAP_AP D_LINK_ ROLLUP DAP_AP D_LINK_ ROLLUP DAP_AP D_LINK_ ROLLUP DAP_AP D_LINK_ ROLLUP DAP_SC SI
1-64
U-E-A
U-D-Idl
EMPTY
6194
Version check failed Partial Link connectivity
U-D-Idl
U-E-Imp
10
EMPTY
U-E-A
U-E-Imp
7, 9
EMPTY
U-E-Imp
U-D-Idl
7, 9
EMPTY
All links failed
U-E-A
U-D-Idl
7, 9
EMPTY
All links failed
U-E-Imp
U-E-A
10
EMPTY
U-D-Idl
U-E-A
10
EMPTY
1-12
U-D-Idl
U-E-A
EMPTY
45062
EMPTY
6 0 8
1.3.6.1.4.1.161.3.3.10. 5.7.1.1.2.5.1.4.104..<INSTANCE>
DAP_SC SI
1-12
U-E-A
U-D-Idl
603
45062
EMPTY
FRUs has become nonoperational or have been removed. SCSI: MOC=104 Instance=1-12
CCPDAP-36
October 30, 2008
Release SR17.0
__________________________________ Events
Event Type
R e a s o n C o d e reStartEvent E M P T Y <universal time>-<managed object instance>-<usage state><operational state>-<administrative state>-<boot ROM version><software Load version>-<database version>-<code version>-<system description>-<latest reset reason><outage time since latest reset><reboot time>-<boot diagnostics> 1.3.6.1 .4.1.16 1.3.3.1 0.2.3.1 .0 DAP_ STAT E 0 EMPTY EMPTY DAP_NO DE EMPTY This event is used to inform the OMC whenever DAP starts. It also tells the OMC that SNMP agent is operational and is ready to handle request. Reset reason 0x05 means the DAP application got automatically restarted because of a reboot. Event is generated if OLCC background download has completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated if OLCC background download has completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated if OLCC background download has completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated if OLCC background download has completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure
OMC Text
MOI Info (Id)
MOI Info (Labe l)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N ) N
Action Status
1 Background Download started
1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.1.0 1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.1.0 1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.1.0 1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.1.0 1.3.6.1 .4.1.16 1.3.3.1 0.2.11. 1.1.0
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
2 Background Download aborted
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
3 Background Download failed
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
4 Background Download completed successfully
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
1 Background Download Switch started
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
C Comments & h Notes a n g e S t a t u s U The DAP has been started. Please involve CNRC if the latest reset reason code is 0x05. The state change was updated to keep it consistent with the code and other documentation and avoid confusion. U The state change was updated to keep it consistent with the code and other documentation and avoid confusion. U The state change was updated to keep it consistent with the code and other documentation and avoid confusion. U The state change was updated to keep it consistent with the code and other documentation and avoid confusion. U The state change was updated to keep it consistent with the code and other documentation and avoid confusion. U The state change was updated to keep it consistent with the code and other documentation and
October 30, 2008
CCPDAP-37

Event Type
R e a s o n C o d e (reason and line number in configuration file). Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure (reason and line number in configuration file). Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure (reason and line number in configuration file). Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure (reason and line number in configuration file). Event is generated if OLCC background download has been aborted.
Release SR17.0
From State To State Related State Changes Related Alarms
OMC Text
MOI Info (Id)
MOI Info (Labe l)
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
avoid confusion. N U The state change was updated to keep it consistent with the code and other documentation and avoid confusion. The state change was updated to keep it consistent with the code and other documentation and avoid confusion. The state change was updated to keep it consistent with the code and other documentation and avoid confusion. The state change was updated to keep it consistent with the code and other documentation and avoid confusion.
Action Status
2 Background Download Switch aborted
1.3.6.1 .4.1.16 1.3.3.1 0.2.11. 1.1.0
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
3 Background Download Switch failed
1.3.6.1 .4.1.16 1.3.3.1 0.2.11. 1.1.0
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
4 Background Download Switch completed successfully
1.3.6.1 .4.1.16 1.3.3.1 0.2.11. 1.1.0
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
1 Background Download aborted , Incorrect action status 2 o r 3 4 Background Download aborted successfully
1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.2.0
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
1.3.6.1 .4.1.16 1.3.3.1 0.2.10. 1.2.0
DAP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has been aborted.
The state change was updated to keep it consistent with the code and other documentation and avoid confusion.
CCPDAP-38
October 30, 2008
Release SR17.0
_____________________ Alarms
Alarm Type
Alarm Code
CCPHADAP
Alarm Code Text Severity R e l a t e d A l a r m s E M P T Y
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
101300
iSG_DAP, DAP_DAP, MDG_DAP or iVPU_DAP TCP Link Down
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Link Down DevType <value> DevNum <value> Uanc <value> IpAddr <value> sd<value> E-Net <Link ID> Is Down
Critical
101301
Ethernet Link Down
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 10.1.1.1. <Instanc e>
HADAP_NI OC_ALM
1-4
Critical
E M P T Y
101301
Ethernet Link Down
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 10.1.1.1. <Instanc e>
HADAP_NI OC_ALM
1-4
E-Net id=<value>, name=<text_d esc> is <Enabled or Impaired or Disabled>
Critical
E M P T Y
HADAP_LINK: 9,10,12,13 HADAP_HN_LINK: 9,10,12,13 HADAP_ISG_LINK: 9,10,12,13 HADAP_MDG_LINK: 9,10,12,13 HADAP_iVPU_LINK: 9,10,12,13 HADAP_LINK: 9,10,12,13 HADAP_HN_LINK: 9,10,12,13 HADAP_HLR_LINK: 9 HADAP_HLR_HN_LI NK:9 HADAP_ISG_LINK: 9,10,12,13 HADAP_LINK: 9,10,12,13 HADAP_HN_LINK: 9,10,12,13 HADAP_HLR_LINK: 9 HADAP_HLR_HN_LI NK:9 HADAP_ISG_LINK: 9,10,12,13
Reestablish TCP connection
C h a n g e S Y t C / a l N t e u a s r R N U C
R e p o r t &
O u t a g e
Comments & Notes
iSG, MDG, iVPU or remote DAP terminated TCP connection 2) Local DAP terminated TCP connection. Device Type=DAP, iSG, MDG, iVPU. Updates are made to alarm code text to make it simpler
Contact the iDEN Customer Network Resolution Center for assistance.
R N M Ethernet Link is down. <Link C ID>= {1-4}. This alarm is used to detect the Ethernet link connection failure. Applies to SCP-DAP only
Check for the following in the chassis: Both switch blades (SSC) should be installed in the chassis. If the blade is configured as per the configuration given above and if this alarm is still seen, contact the iDEN Customer Network Resolution Center for assistance.
R N M Ethernet Link is enabled or C impaired or disabled. This alarm is used to detect the Ethernet link connection failure. Applies to ATCA-DAP only
October 30, 2008
CCPHADAP-1

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s E M P T Y
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
101335
Unsupported Hardware
103300
DAP Peer to Peer Connection Terminated
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 20.1.1.1. <Instanc e> 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_LM _ALM
Missing Object Files for Hardware Type <HWtype>
Critical
EMPTY
C h a n g e S Y t C / a l N t e u a s r R N N
R e p o r t &
O u t a g e
Comments & Notes
Update Loads on OMC to versions that not support the hardware version installed. Applies to ATCA-DAP only.
HADAP_CP U_ALM
PEER DAP'S UANC = <UANC> DAP ID = <DAP ID>
Major
E M P T Y
HADAP_HN_LINK: 9,10,12 HADAP_LINK: 9,10,12 HADAP_LINK_ROLL UP: 401,402,403
1) Restart DAP.2) Replace failed Ethernet card or system unit. 3) Troubleshoot Network and Repair.
R N U C
101340
Software Upgrade Failure
101310
DEV_TEMP device disabled
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 20.1.1.1. <Instanc e> 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 14.1.1.1. <Instanc e>
HADAP_LM _ALM
<reason>
Critical
E M P T Y
EMPTY
R Y N C
1) DAP was shutdown. 2) Ethernet Card Failure. Double Point of Failure. 3) General Network Failure. Note: Only the DAP that initiated the termination of the connection reports this alarm. Where: <UANC> = {1-16777215} <DAP_ID> = {1-300} Software Upgrade Failure. Where: <reason> displays different reasons for different failure scenarios. Applies to ATCA-DAP only.
HADAP_DE V_TEMP
1-7
DEV_TEMP DeviceType <DeviceTypeI d> DeviceId <DeviceID> <Enabled or Disabled>
Critical
E M P T Y
HADAP_MISC: 615, 617, 619, 621
101302
Power Disabled
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 3.1.1.1.
HADAP_P OWER_AL M
1-3
Power DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Impaired or Enabled>
Critical
E M P T Y
HADAP_HW_CONTA INER: 601-605,622 HADAP_MISC: 606,613,615,617,619, 621 HADAP_NODE: 901-902
101303
Fan Disabled
1.3.6.1.4. 1.161.3.3 .10.5.7.1.
HADAP_FA N_ALM
1-20
Fan DeviceType <DeviceTypeI
Critical
E M P
HADAP_HW_CONTA INER: 601-605,622 HADAP_MISC:
Try to maintain the temperature in the operating range. If the problem persists even after the temperature is brought to a safe range, contact Customer Situation Center for assistance. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if
R N N C
Temperature outside the operating range. SCP-DAP instance is 1, ATCA-DAP instance is 1-7
R N M A hardware failure has occurred. C Instance 3 will be in impaired condition if there is a fault with one of the power supplies or if sufficient power is not fed to one of the power supplies. Applies to SCP-DAP only
R N M This alarm is reported as a C cooling fan has been disabled. The DAP has 2 fans, and 1 out
CCPHADAP-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

OMC Text MOI Info (Id) MOI Info (Label)
Inst Alarm Code Text Severity R e l a t e d A l a r m s T Y
Remedy
R e p o r t &
C h a n g e S Y t C / a l N t e u a s r
O u t a g e
Comments & Notes
1.2.3.1.6. 2.1.1.1.
d> Device Id <DeviceID> <Disabled or Impaired or Enabled>
606,613,615,617,619, 621 HADAP_NODE: 901-902
possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit.
101305
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 7.1.1.1.
HADAP_SC SI_ALM
1-4
SCSI DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled>
Critical
E M P T Y
HADAP_HW_CONTA INER: 601 - 605,622 HADAP_NODE: 901902 HADAP_SCSI: 607-608
101305
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 7.1.1.1.
HADAP_SC SI_ALM
1-4
101306
NIOC Disabled
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 10.1.1.1. <Instanc e>
HADAP_NI OC_ALM
1-2
HARD_DISK DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Impaired or Enabled> NIOC DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled>
Critical
E M P T Y
HADAP_HW_CONTA INER: 601 - 605,622 HADAP_NODE: 901902 HADAP_SCSI: 607-612
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Contact Customer Network Resolution Center if needed. Contact the iDEN Customer Network Resolution Center for assistance
of service is not service impacting but should be investigated for corrective action. Should one fan fail, open a minor ticket with Motorola CNRC. If both fans are disabled, the DAP will shutdown when it reaches its thermal limit to avoid heat damage. Should both fans fail, open a Critical ticket with Motorola CNRC for resolution and contact the market. Applies to SCP-DAP only R N M A hardware failure has occurred. C Applies to SCP-DAP, where the instance range is 1-2.
R N M A hardware failure has occurred. C Applies to ATCA-DAP, where the instance is 1
Critical
E M P T Y
HADAP_HW_CONTA INER: 601-605,622 HADAP_NIOC: 607612 HADAP_NODE: 901-902
101309
TOY_CLOCK device
1.3.6.1.4. 1.161.3.3
HADAP_TO Y_CLOCK_
TOY_CLOCK DeviceType
Critical
E M
HADAP_HW_CONTA INER: 601-605,622
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed
R N M A hardware failure has occurred. C This alarm is used to detect the Ethernet card failure. Applies to SCP-DAP only
R N M A hardware failure has occurred. C The Alarm Code Text was
October 30, 2008
CCPHADAP-3

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s P T Y
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Comments & Notes
disabled
.10.5.7.1. 1.2.3.1.6. 15.1.1.1. <Instanc e>
ALM
<DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled>
HADAP_MISC: 606,613,615,617,619, 621
101323
Disk Volume Disabled
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
1-99
101324
Memory Disabled
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
DISK VOLUME DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled> MEMORY DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Impaired or Enabled>
Critical
E M P T Y
EMPTY
hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Contact the iDEN Customer Network Resolution Center for assistance
updated for providing more information to the customer regarding Device Failure. Applies to SCP-DAP only
R N M A hardware failure has occurred. C 99 is the maximum instance of instance. The real instance of VOLUME is decided during runtime, which is around 20.
Critical
E M P T Y
HADAP_HW_CONTA INER: 601-605,622 HADAP_MISC: 606,613,615,617,619, 621
Contact the iDEN Customer Network Resolution Center for assistance
101325
MP Processor Disabled
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
1-2
MP PROCESSOR DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or
Critical
E M P T Y
HADAP_HW_CONTA INER: 601-605,622 HADAP_MISC: 606,613,615,617,619, 621
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate,
R N M A hardware failure has occurred. C An alarm indicating enabled state of HW Device Memory is sent when memory is available, which is CLEAR alarm for HW DEVICE MEMORY. An alarm indicating impaired state of HW Device Memory is sent when total Memory decreased from last reboot or % mem used over alarm threshold (default = 85%), which is SET alarm for HW DEVICE MEMORY. An alarm indicating disabled state of HW Device Memory is sent when % mem used over recovery threshold (default = 90%) or total memory less than minimum required by config, which is SET alarm for HW DEVICE MEMORY also. In some scenarios, there can be one CLEAR alarm for more than one corresponding SET alarms. R N M A hardware failure has occurred. C Applies to SCP-DAP only
CCPHADAP-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Inst Alarm Code Text Severity R e l a t e d A l a r m s
Remedy
R e p o r t &
O u t a g e
Comments & Notes
Impaired or Enabled>
101326
SYSTEM BUS Disabled
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
1-2
SYSTEM_BU S DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled>
Critical
E M P T Y
EMPTY
101326
SYSTEM BUS Disabled
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
1-2
101331
Voltage Outside Operating Threshold
101332
IPMI Controller Disabled
101333
Latch Open
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
1-17
SYSTEM_BU S DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Impaired or Enabled> Voltage Device <id> Outside Operating Range IPMI Controller <id> <Disabled or Enabled> Latch Open <id>
Critical
E M P T Y
EMPTY
replace the hardware or system unit. Contact Customer Network Resolution Center if needed. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Contact Customer Network Resolution Center if needed. Contact the iDEN Customer Network Resolution Center for assistance
R N M A hardware failure has occurred. C Applies SCP-DAP instance range is 1-2
R N M A hardware failure has occurred. C Applies ATCA-DAP instance is 1
Critical
EMPTY
Contact Customer Network Resolution Center for assistance.
R N N C
Voltage Level Outside of given threshold range. Applies to ATCA-DAP only
HADAP_CP U_ALM
1-2
Critical
EMPTY
R N N C
IPMI controller is not operational. Applies to ATCADAP only
HADAP_CP U_ALM
1-2
Major
EMPTY
Check if latch is closed for the front blade and the rear transition blade. If problem persists contact iDEN
R N N C
Close the latch to clear the condition. Applies to ATCA-DAP only
October 30, 2008
CCPHADAP-5

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Comments & Notes
100004
Bad Value in config file
1.3.6.1.4. 1.161.3.3 .10.2.14. 1.1.0 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
CA_BADVA L_ALM
EMPT Y
Bad Value for OID:<object_i d>
Major
101311
Invalid IP address
HADAP_CP U_ALM
invalid ip address, dev_type=<de vicetypeID>, ip_addr=<Ipad dress>, close sd <sdno>
Critical
E M P T Y E M P T Y
EMPTY
Customer Network Resolution Center for assistance Contact the iDEN Customer Network Resolution Center for assistance. 1)Check for proper configuration of iSG, MDG, or remote DAP 2)Change the iSG, MDG or remote DAP IP address via OLCC. 3) Make the iSG, MDG, or remote DAP IP address change to the DAP configuration at OMC-R. 4) Download the latest configuration load to DAP (and/or iSG, MDG, or remote DAP) Contact Customer Network Resolution Center for assistance.
R N U
Bad Value returned in the Configuration File. Where <object_id> = {x.x.x...}
EMPTY
R N U
1)Misconfiguration of iSG, MDG or remote DAP IP address 2)DAP (and/or iSG, MDG or remote DAP) not downloaded with latest configuration data 3)Illegal device attempting connection to the DAP.
101330
Timezone Failure
101334
Firmware Upgrade Status
101337
Blade Initialization Failure
101500
Current billing collection
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3
HADAP_CP U_ALM
Timezone setup failure
Major
E M P T Y E M P T Y E M P T Y E M
EMPTY
R N N C
Timezone is set based on configuration downloaded from OMC-R. Applies to ATCA-DAP only
HADAP_CP U_ALM
<Additional Information>
Critical
EMPTY
R N N C
This alarm is not supported and will be removed from this document in a future release.
HADAP_CP U_ALM
Failure <type> at initialization
Critical
EMPTY
R Y N C
HADAP_CP U_ALM
1-300
DAP ID = <DAP_ ID>
Critical
EMPTY
Contact the iDEN Customer Network
R N U C
An error has occurred for which the billing file could not be
CCPHADAP-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Inst Alarm Code Text Severity R e l a t e d A l a r m s P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Comments & Notes
interval has been disabled
101600
GTT On_Line Change
.10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID> 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID>
Resolution Center for assistance.
written. At the next billing cycle, another attempt will be made to re-enable billing. R N U C DAP is unable to perform an OLCC of GTT data. 1) Unable to re-establish lost Sub agentMaster agent communication. 2) Unable to update memory.
HADAP_CP U_ALM
1-300
GTT OLCC
Critical
EMPTY
101601
GTT Initialization
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID>
HADAP_CP U_ALM
1-300
EMPTY
Critical
E M P T Y
EMPTY
1) Check DAP alarm log for the following GTT memory alarms: ALMACP_GTT_U PD_START ALMACP_GTT_U PD_END ALMACP_GTT_U PD_ISDN_TBL ALMACP_GTT_U PD_IMSI_TBL ALMACP_GTT_U PD_UFMI_TBL 2) Check if Sub agent-Master agent connection is up. 1) Check DAP alarm log for the following GTT memory alarms: ALMACP_GTT_IN IT, ALMACP_GTT_R ESTORE, ALMACP_GTT_M MAP_CORRUPTE D, ALMACP_GTT_U PD_START, ALMACP_GTT_U PD_END, ALMACP_GTT_U PD_ISDN_TBL, ALMACP_GTT_U PD_IMSI_TBL, ALMACP_GTT_U PD_UFMI_TBL or verify the subagent registration failure, ALMACC_CA_RE
R N U C
DAP experienced problem during initialization of global titling translation table information. 1) Memory problem. 2) Unable to register to Common agent to retrieve GTT data 3) Incorrect GTT Data. 4) Can't get DAP's ISDN and IP address corresponding to the Logical Id and Uanc of current DAP.
October 30, 2008
CCPHADAP-7

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Comments & Notes
101602
Global Title Failure: Own Route
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<Old ISDN Address> <New ISDN Address> < UANC> <Logical Id>
Critical
E M P T Y
EMPTY
101603
Location Area's MDG Region Id does not match ACG's MDG Region Id
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< ACG_ID >
HADAP_CP U_ALM
110000
ACG ID = <ACG_ID> MDG_REGIO N_ ID = <MDG_REGI ON_ID> LA_ID = <LA_ID>
Critical
E M P T Y
EMPTY
GISTER_FAIL. 2) ALMACP_GTT_D AP_OWN_ADDR and ALMACP_GDM_V LR_NOT_IN_VLR verify the GTT Data dump on the DAP if it contains the current DAP Id and UANC information. 1) DAP will not be able to communicate to the iDEN-HLRs and iDEN-HLR will not be able to communicate to DAPs until a global title translation file containing the DAP's new routing information is downloaded. 2) DAP will not be able to communicate to the iDEN-HLRs. 3) Reconfigure the DAP's own logical Id and Uanc in the configuration file. Trouble shoot the System Boundary configuration at the OMC, paying close attention to the Dispatch Location Area Identifier shown in the additional text. Ensure that this Dispatch Location Area is not associated with
R N U C
DAP's own Global Title Translation Table routing is not correct. 1) If additional text indicates an ISDN address, then newly loaded Global Title Translation Table does not contain the DAP's own routing information. 2) Improperly configured DAP Logical Id and Uanc address. WHERE: <Old ISDN Address>= {000000000000001 999999999999999} <New ISDN Address>= {000000000000001 999999999999999} <Uanc> = {1-16777215} <Logical Id>= {115}
R N U
This ACG has been assigned to a Dispatch Location Area (LA_ID) that is associated with a MDG Region id that is different than the MDG Region id identified in the extra text. Where: <MDG_REGION_ID> = {1-4} <ACG_ID> = {1-10000} <LA_ID> = {1-9999}
CCPHADAP-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Remedy
R e p o r t &
O u t a g e
Comments & Notes
101604
Own DAP UANC not OLCCable
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID>
HADAP_CP U_ALM
1-15
Current DAP Info: <DAP_ID> <Current Uanc> OLCC DAP Info:<DAP_ID > <New Uanc>
Critical
E M P T Y
EMPTY
more than one MDG Region. The DAP should be restarted for the UANC Change by OLCC to take effect.
R N U
101605
CPU bind fail
101650
DAP to ACG Connection Terminated
101651
ACG has not sent a link version request message to the DAP Incompatible ACG_DAP interface versions
101652
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< ACG_ID > 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< ACG_ID > 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< ACG_ID >
HADAP_CP U_ALM
cpu bind for mailbox id = <mailbox ID>, rt_val = < return value> DAP'S ACG ID = <ACG_ID>
Major
E M P T Y E M P T Y
EMPTY
R N U
If the DAP OLCC of UANC was not intended, this can be corrected by EGT4 correcting the configuration information and pushing the correct GTT data which will be accepted by the DAP and OLCC successful and no alarm will be generated in that case. Where: <Current UANC> = {1-16777215} <New UANC> = {1-16777215} <DAP_ID> = {1-300} CCP failed to locate the CPU ID for the task
HADAP_CP U_ALM
110000
Major
HADAP_ACG_LINK: 9,10
1) Replace failed Ethernet card or system unit. 2) Troubleshoot Network and Repair. Contact the iDEN Customer Network Resolution Center for assistance.
R N U C
1) ACG was shutdown. 2) Ethernet Card Failure. Double Point of Failure. Where: <ACG_ID> = {1-10000}
HADAP_CP U_ALM
110000
ACG ID = <ACG_ID>
Critical
E M P T Y
EMPTY
R N U C
The ACG identified in the extra text has not requested a version check even though a connection has been established. Where: <ACG_ID> = {1-10000}
HADAP_CP U_ALM
110000
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_ACG_V ERSION_NE W = <VER> ACG ID = <ACG_ID>
Critical
E M P T Y
HADAP_ACG_LINK:1 3
Verify that the ACG identified has the proper software load version to interface with the software version of the DAP reporting the alarm.
R N U
The ACG has requested link version checking and neither the old nor the new link version numbers match the DAP-ACG Link Version. Where: <VER> = Rxx.xx.xx <ACG_ID> = {110000}
October 30, 2008
CCPHADAP-9

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
101653
Incompatible DAP ID and/or ACG ID
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< ACG_ID >
HADAP_CP U_ALM
110000
101654
DAP to MDG Connection Terminated
101655
MDG has not sent a link version request message to the DAP Incompatible MDG_DAP interface versions
101656
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< MDG_ID > 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< MDG_ID > 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< MDG_ID >
HADAP_CP U_ALM
1-36
ACG'S DAP ID = <DAP_ID> ACG'S ACG ID = <ACG_ID> DAP'S DAP ID = <DAP_ID> DAP'S MDG ID = <MDG ID>
Critical
EMPTY
Trouble shoot DAP/EBTS configuration.
C h a n g e S Y t C / a l N t e u a s r R N U
R e p o r t &
O u t a g e
Comments & Notes
The ACG has requested link version checking and the DAP identified does not match the ID of the DAP that received the request. Where: <DAP_ID> = {1-15} <ACG_ID> = {1-10000}
Major
E M P T Y
HADAP_MDG_LINK: 9, 10, 12 HADAP_MDG_LINK_ ROLLUP: 401,402,403
R N U C
1) MDG was shutdown. 2) Ethernet Card Failure. Double Point of Failure. Where: <MDG_ID> = {1-36}
HADAP_CP U_ALM
1-36
MDG ID = <MDG_ID> Ip Address = <ip_address>
Critical
E M P T Y
EMPTY
R N U C
HADAP_CP U_ALM
1-36
101657
Incompatible DAP ID and/or MDG ID
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< MDG_ID >
HADAP_CP U_ALM
1-36
101659
DAP_DAP Link Version
1.3.6.1.4. 1.161.3.3
HADAP_CP U_ALM
1-300
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_MDG_V ERSION_NE W = <VER> MDG ID = <MDG_ID> MDG'S DAP ID = <DAP_ID> MDG'S MDG ID = <MDG_ID> DAP'S DAP ID = <DAP_ID> PEER DAP'S UANC =
Critical
E M P T Y
HADAP_MDG_LINK: 13 HADAP_MDG_LINK_ ROLLUP: 401,402,403
Verify that the MDG identified has the proper software load version to interface with the software version of the DAP reporting the alarm.
R N U
The MDG identified in the extra text has not requested a version check even though a connection has been established. Where: <MDG_ID> = {UNKNOWN, 136} <ip_address> = xxx.xxx.xxx.xxx The MDG has requested link version checking and neither the old nor the new link version numbers match the DAP-MDG Link Version. Where: <VER> = Rxx.xx.xx <MDG_ID> = {1-36}
Critical
E M P T Y
EMPTY
Trouble shoot MDG configuration.
R N U
The MDG has requested link version checking and the DAP identified does not match the ID of the DAP that received the request. Where: <DAP_ID> = {1-15} <MDG_ID> = {1-36}
Critical
E M
EMPTY
1) Troubleshoot the target DAP
R N U C
1) The DAP that is the target of the link version request is not
CCPHADAP-10
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Inst Alarm Code Text Severity R e l a t e d A l a r m s P T Y
Remedy
R e p o r t &
O u t a g e
Comments & Notes
Request Timeout
.10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID>
<UANC> DAP ID = <DAP_ID>
101660
Incompatible DAP ID on DAP_DAP Interface
101661
Incompatible DAP_DAP interface versions
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID> 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID>
HADAP_CP U_ALM
1-300
PEER DAP'S UANC = <UANC> DAP ID = <DAP_ID> RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_DAP_V ERSION_OLD = <VER> DAP_DAP_V ERSION_NE W = <VER> UANC = <UANC> DAP ID = <DAP_ID> PEER DAP'S UANC = <UANC> DAP ID = <DAP_ID> DAP'S ISG ID = <iSG_ID>
Critical
E M P T Y E M P T Y
EMPTY
and repair. 2) Troubleshoot the Network and repair. 3) Troubleshoot the Network and repair. Verify that the DAP ID and peer DAP ID configuration for each DAP match. Contact the iDEN Customer Network Resolution Center for Assistance.
responding. 2) Network Congestion. 3) Network Latency. Where: <UANC> = {116777215} <DAP_ID> = {1-300}
R N U
Originating Peer DAP is misconfigured. Where: <UANC> = {1-16777215} <DAP_ID> = {1300}
HADAP_CP U_ALM
1-300
Critical
HADAP_HN_LINK: 13 HADAP_LINK: 13 HADAP_LINK_ROLL UP:401,402,403
R N U
Invalid Version Mismatch. Where: <VER>= Rxx.xx.xx <UANC> = {1-16777215} <DAP_ID> = {1-300}
101662
DAP_DAP Link Version Failure
101663
DAP to iSG Connection Terminated
101664
Invalid iSG Connection Attempt
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID> 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6.
HADAP_CP U_ALM
1-300
Critical
E M P T Y E M P T Y E M P T
EMPTY
Troubleshoot DAPs and reconfigure.
R N U
Originating or peer DAP is misconfigured. Where: <UANC> = {1-16777215} <DAP_ID> = {1300}
HADAP_CP U_ALM
1-4
Major
HADAP_ISG_LINK: 9, 10, 12 HADAP_ISG_LINK_R OLLUP: 401, 402, 403 EMPTY
HADAP_CP U_ALM
iSG connection rejected due to no CALEA
Critical
R N U C
1) iSG was shutdown. 2) Ethernet Card Failure. Double Point of Failure. Where: <iSG_ID> = {1-4}
R N U
CALEA feature disabled in DAP.
October 30, 2008
CCPHADAP-11

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s Y E M P T Y E M P T Y
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Comments & Notes
101665
101666
iSG has not sent a link version request message to the DAP Incompatible iSG_DAP interface versions
1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
feature HADAP_CP U_ALM 1-4 ISG ID = <iSG_ID> Critical
EMPTY
R N U C
The iSG identified in the extra text has not requested a version check even though a connection has been established. Where: <iSG_ID> = {1- 4} The iSG has requested link version checking and neither the old nor the new link version numbers match the DAP- iSG Link Version. Where: <VER> = Rxx. xx. xx <iSG_ID> = {1- 4}
HADAP_CP U_ALM
1-4
101667
Incompatible DAP ID and/or iSG ID
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
1-4
101668
DAP to iVPU Connection Terminated
HADAP_CP U_ALM
1-252
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER NUM = <VER> DAP_ ISG_ VERSION_ NEW = <VER> ISG ID = <iSG_ID> ISG'S DAP ID = <DAP_ID> ISG'S ISG ID = <iSG_ID> DAP'S DAP ID = < DAP_ID> DAP'S IVPU ID = <iVPU_ID>
Critical
HADAP_ISG_LINK: 13 HADAP_ISG_LINK_R OLLUP:401,402
Verify that the iSG identified has the proper software load version to interface with the soft-ware version of the DAP reporting the alarm.
R N U
Critical
E M P T Y
EMPTY
Troubleshoot iSG configuration.
R N U
The iSG has requested link version checking and the DAP identified does not match the ID of the DAP that received the request. Where: <DAP_ID> = {1- 15} <iSG_ID> = {1- 4} 1) iVPU was shutdown. 2) Ethernet Card Failure. Double Point of Failure. Where: <iVPU_ID> = {1-252}
Major
E M P T Y E M P T Y
HADAP_IVPU_LINK: 9,10,12 HADAP_IVPU_LINK_ ROLLUP: 401,402,403 EMPTY
101669
iVPU has not sent a link version request message to the DAP Incompatible iVPU_DAP interface versions
HADAP_CP U_ALM
1-252
IVPU ID = <iVPU_ID> Ip Address = <ip_address>
Critical
R N U C
R N U C
101670
HADAP_CP U_ALM
1-252
RECEIVED OLD VER NUM = <VER> RECEIVED NEW VER
Critical
E M P T Y
HADAP_IVPU_LINK: 13 HADAP_IVPU_LINK_ ROLLUP: 401,402,403
Verify that the iVPU identified has the proper software load version to interface with the
R N U
The iVPU identified in the extra text has not requested a version check even though a connection has been established. Where: <iVPU_ID> = {UNKNOWN, 1252} <ip_address> = xxx.xxx.xxx.xxx The iVPU has requested link version checking and neither the old nor the new link version numbers match the DAP- iVPU Link Version. Where: <VER> = Rxx.xx.xx <iVPU_ID> = {1- 252}
CCPHADAP-12
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Remedy
R e p o r t &
O u t a g e
Comments & Notes
101671
Incompatible DAP ID and/or iVPU ID
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
1-252
101672
DAP to iHLR Connection Terminated
101673
iVPU Ip Address Mapping Failure
101674
Invalid SDG parameter
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID> 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
NUM = <VER> DAP_ IVPU_ VERSION_ NEW = <VER> IVPU ID = <iVPU_ ID> IVPU'S DAP ID = <DAP_ID> IVPU'S IVPU ID = <iVPU_ID> DAP'S DAP ID = <DAP_ID> PEER IHLR'S UANC = <UANC> IHLR ID = <iHLR_ID> IVPU ID = <iVPU_ID> Ip Address = <ip_address>
soft-ware version of the DAP reporting the alarm.
Critical
E M P T Y
EMPTY
Troubleshoot iVPU configuration.
R N U
The iVPU has requested link version checking and the DAP identified does not match the ID of the DAP that received the request. Where: <DAP_ID> = {1- 15} <iVPU_ID> = {1- 252}
Major
HADAP_CP U_ALM
1-252
Critical
HADAP_HLR_HN_LI NK: 9,10,13,14 HADAP_HLR_LINK: 9,10,13,14 HADAP_HLR_LINK_ ROLLUP:401,402,403 EMPTY
1) Replace failed Ethernet card or system unit. 2) Troubleshoot Network and Repair. Verify that the iVPU identified has the proper ip address configured. Contact the iDEN Customer Network Resolution Center for assistance.
R N U C
1) iHLR was shutdown. 2) Ethernet Card Failure. Double Point of Failure. Where: <UANC> = {1-16777215} <iHLR_ID> = {1-300} The iVPU identified the ip address are duplicate. Where: <iVPU_ID> = {1- 252} <ip_address> = xxx.xxx.xxx.xxx
R N U
HADAP_CP U_ALM
1-300
Parameter=, Value=<SDG_ value>
Minor
EMPTY
R N U
102100
Missing Cell IDs in the DAP Configuration File
HADAP_CP U_ALM
ACG ID = <ACG_ID> Sector ID = <Sector_ID>
Major
E M P T Y
EMPTY
Verify that the DAP Configuration file has the proper ACG and Cell IDs.
R N U
102101
Authentication failure due to
1.3.6.1.4. 1.161.3.3
HADAP_CP U_ALM
<IMSI> <Correct HLR
Minor
E M
EMPTY
1) Contact Subscriber who
R N U
The SDG parameter in the DAPDAP LVCP was invalid. Where: <parameter> = {SDG, iDEN SDG}, <SGG_value> = {0-50} This new alarm was added to the LVCP for the iGW SDGC feature During registration or registration renewal, the MS fails to retrieve the sector info, MDG region Id and primary location ID from the VLR database. This is likely to be due to a DAP configuration mismatch. Where: <ACG_ID> = {1-10000} <Sector ID> = {1-3} Authentication failure due to SRES mismatch. 1) A `rogue'
October 30, 2008
CCPHADAP-13

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s P T Y
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Comments & Notes
SRES mismatch
.10.5.7.1. 1.2.3.1.6. 1.1.1.1.
SRES> <Incorrect MS SRES> <ACG ID> <Sector ID>
owns the MS with that IMSI to verify if his MS is working well. If so, the alarm can be attributed to a rogue. 2) If MS is not working well, check for it, if it has been changed in the MS or in the iDEN HLR. EMPTY 1) Examine DAPMDG state links to verify if there are up. Concentrate on the MDG which is listed on the alarm (only the last failed is listed). 2) Monitor the MDG for other suspicious alarms. 1) Check the GTT tables to determine whether the specified IMSI is included in the IMSI ranges. 2) Verify the iDEN HLR configuration in the GTT tables. 3) A `rogue' or `foreign' MS is attempting to access the system. R N U
102102
The DAP was unable to find an MDG to handle the Packet Data Registration
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<IMSI> <Number of failures> <Last MDG ID>
Major
E M P T Y
MS has attempted to register on the system, but failed authentication.2) A legitimate MS's Ki has been changed, and it is out of sync with iDEN HLR. Where: <IMSI>= {0x00000000000000000x9999999999999999} <Correct HLR SRES> = {0x000000000x99999999} <Incorrect MS SRES> = {0x000000000x99999999} <ACG ID> = {110000} <Sector ID> = {1-3} DAP attempted to forward a PD registration to several MDGs, but all have failed: Time-outs or invalid responses. 1) DAP-MDG link problem. 2) MDG problem. Where: <IMSI>= {0x00000000000000000x9999999999999999} <Number of failures>= {1-10} <Last MDG ID> = {1-36} MS has attempted to register, but global title translation failed. As a result the D-VLR was not able to determine a path to the iDEN HLR for the MS. 1) GTT IMSI ranges do not include MS. 2) GTT does not properly configure the iDEN HLR. 3) A 'rogue' MS has attempted to register with an invalid IMSI. Where: <IMSI>= {0x00000000000000000x9999999999999999} <ACG ID> = {1-10000} <Sector ID> = {1-3} <Transaction type (Motorola internal use)> = {0x0000-0xffff} MS attempted to register, but the iDEN HLR indicates that the MS is unknown. 1) MS missing from iDEN HLR. 2) Unknown. Where: <IMSI>= {0x0000000000000000-
102103
DAP cannot map to an iDEN HLR address for this IMSI
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<IMSI> <ACG ID> <Sector ID> <Transaction type (Motorola internal use)>
Minor
E M P T Y
EMPTY
R N U
102104
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<IMSI> <ACG ID> <Sector ID> <Transaction type (Motorola internal use)>
Minor
E M P T Y
EMPTY
1) Pull up the listed IMSI at the iDEN HLR ADC. If the IDEN HLR ADC is missing, it should be added.
R N U
CCPHADAP-14
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Remedy
R e p o r t &
O u t a g e
Comments & Notes
102105
UF GTT lookup failed during registration
102400
DAP Rag Update Failure
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
urban_id=<urb an id> fleet_id=<fleet id>
Major
E M P T Y E M P T Y
EMPTY
If the record exists, verify that the IMSI is active. 2) Contact the iDEN Customer Network Resolution Center for assistance. The urban_id/fleet_id needs to be added to GTT
0x9999999999999999} <ACG ID> = {1-10000} <Sector ID> = {1-3} <Transaction type (Motorola internal use)> = {0x0000-0xffff}
R N U
1) The UF lookup failed during registration. MM will log/report up to 10 alarms in a 5 minute interval.
HADAP_CP U_ALM
Requesting MDG <MDG ID>, Affected RAG <RAG ID>
Critical
EMPTY
102650
102651
Maximum number of retries reached for an MS download request Start RAG download request failed
HADAP_CP U_ALM
<RAG ID> <MDG ID>
Warning
EMPTY
Resetting of the active MDG for the RAG may be required to resync MDG ownership information in the DAP Contact the iDEN Customer Network Resolution Center for assistance.
R N U
Indication of the Rag Management Issues. Where: <MDG ID>={1-36} <RAG ID>={0-31}
R N U
HADAP_CP U_ALM
<RAG ID> <MDG ID>
Warning
EMPTY
R N U
102652
102653
MDG responded to an MS download request with a temporary failure MDG responded to an MS download request with an unrecoverable
HADAP_CP U_ALM
<RAG ID> <MDG ID>
Warning
EMPTY
No action is required at this point because the procedure will be retried.
R N U
MDG has not responded to MS download request and the maximum number of download retries has been reached. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x01-0x24} The RAG is already being downloaded, or the MDG requesting the RAG info does not own that RAG. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x01-0x24} The ms_download_request message failed with a temporary failure. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x010x24}
HADAP_CP U_ALM
<RAG ID> <MDG ID>
Warning
E M P T Y
EMPTY
R N U
The ms_download_request message failed with a permanent failure. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x01-0x24}
October 30, 2008
CCPHADAP-15

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
C h a n g e S Y t C / a l N t e u a s r R N U
O u t a g e
Comments & Notes
102654
102655
102656
102800
failure Maximum number of retries reached for a RAG download complete request MDG responded to an RAG download complete request with a temporary failure MDG responded to a RAG download complete request with an unrecoverable failure DAP Replication Failure
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<RAG ID> <MDG ID>
Warning
EMPTY
An MDG RAG download request failed the maximum number of times. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x010x24}
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<RAG ID> <MDG ID>
Warning
E M P T Y
EMPTY
R N U
During the handling of a RAG download complete request, a download temporary failure condition occurred for this RAG and MDG. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x010x24} During the handling of a RAG download complete response, a download unrecoverable failure condition occurred for this RAG and MDG. Where: <RAG ID> = {0x00-0x1f} <MDG ID> = {0x010x24}
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<RAG ID> <MDG ID>
Warning
E M P T Y
EMPTY
R N U
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<Node><Reas on>
Major
E M P T Y
HADAP_REPLICATI ON: 702, 703
R N U C
102801
DAP Replication Communicatio n Failure
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<Node><Com munication Failure><Interf ace>
Major
E M P T Y
Contact the iDEN Customer Network Resolution Center for assistance, if condition does not clear
DAP Replication services have transitioned to an inactive state and is no longer tracking information for replication to the other node. Until this information is refreshed from the iHLR and the subscriber re-registers, the subscriber might experience unexpected behaviors when a switchover occurs before the condition clears. One potential unexpected behavior is shadow subscribers caused by MSID/DGID assignments not being replicated. R N M DAP Replication services C encountered an issue with its communication path to the other node and is attempting to recover communications with the other node. When the
CCPHADAP-16
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Remedy
R e p o r t &
O u t a g e
Comments & Notes
102802
DAP Replication Suspended
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<Node Suspended On> <User Who Suspended>
Warning
E M P T Y
102803
DAP Replication Log 25% Full
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<Node> <Send Backlog> <Apply Backlog>
Warning
E M P T Y
EMPTY
When DAP Replication suspension was not planned, customer can utilize the LMT Replication Activation option to restart DAP Replication. Contact the iDEN Customer Network Resolution Center for assistance, if condition does not clear or a large number of events detected.
R N U C
condition does not clear, the HA-DAP nodes and the Ethernet cables should be examined for issues. DAP Replication services were suspended by a LMT User on the DAP. Communications with the other node have terminated until the DAP Replication services are activated again.
R N U C
102804
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Minor
1 0 2 8 0 3
EMPTY
R N U C
102805
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Major
1 0 2 8 0 4
EMPTY
R N U C
DAP Replication services is experiencing a backlog of replication events, but is performing all operations normally. Because the synchronization activity is a likely source of this backlog, the throttling of the synchronization will commence if the backlog continues to grow. When this event does not clear within a reasonable period of time, additional investigation should be started. DAP Replication services is experiencing a serious backlog of replication events, where the synchronization activity is being throttled. If the backlog continues to grow, the synchronization activities will be halted. Customer should verify that DAP Replication has not been suspended and DAP Replication Communications are functioning normally. DAP Replication services is experiencing a major backlog of replication events, and synchronization activities are being blocked. If the backlog continues to grow, DAP Replication services will
October 30, 2008
CCPHADAP-17

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Comments & Notes
102806
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Critical
1 0 2 8 0 5
R N U C
102807
DAP Replication Synchronized
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<Node> <Type> <Scope>
Warning
E M P T Y
Contact the iDEN Customer Network Resolution Center for assistance, if the node remains in a synchronization state.
R N U C
102808
DAP Replication No Region
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<Node> <Region>
Warning
E M P T Y
EMPTY
Contact the iDEN Customer Network Resolution Center for assistance in determining the impacted region. Contact the iDEN Customer Network Resolution Center for assistance.
R N U C
103200
Incompatible DAP_iDEN HLR interface versions
HADAP_CP U_ALM
<DAP ISDN ADDRESS> <DAP iDEN MAP APPLICATIO N CONTEXT VERSION> <iDEN HLR ISDN ADDRESS>
Critical
E M P T Y
EMPTY
R N U C
103201
CA Poll timer creation failed
1.3.6.1.4. 1.161.3.3
HADAP_CP U_ALM
Creation of CA poll timer
Major
E M
EMPTY
Contact the iDEN Customer Network
R N U
automatically transition into an inactive state. Customer should verify that DAP Replication has not been suspended and DAP Replication Communications are functioning normally. DAP Replication services is experiencing a critical backlog of replication events and is transitioning replication to an inactive state. Customer should verify that DAP Replication has not been suspended and DAP Replication Communications are functioning normally. DAP Replication services has been requested to perform a synchronization activity on one or more connected regions. The request could have been generated by a LMT user or internally. Customer should wait until the synchronization activity completes before performing maintenance on the node. DAP Replication services received a replication event for a region that was not connected. The replication event was dropped and the region flagged for a synchronization activity once the region reconnected. DAP has attempted to communicate with the iDEN HLR, but the iDEN MAP APPLICATION CONTEXT VERSIONS are incompatible. Where: <DAP ISDN ADDRESS>={00000000000000 0-999999999999999} <DAP iDEN MAP APPLICATION CONTEXT VERSION>= {2255} <iDEN HLR ISDN ADDRESS>={00000000000000 0-999999999999999} The CA poll timer could not be created by the task and
CCPHADAP-18
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Inst Alarm Code Text Severity R e l a t e d A l a r m s P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Comments & Notes
103202
HA Recovery Initiated
.10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
during runtime failed
therefore OLCC for this task will not be performed successfully.
HADAP_CP U_ALM
Critical
HADAP_APP_ROLLU P : 301
R Y U
100005
Time Synchronizati on Cannot Be Done
1.3.6.1.4. 1.161.3.3 .10.2.6.1. 0
CA_SNTP_ ALM
EMPT Y
101100
MAP Dialog Threshold Limit
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Time Difference between NMS and NE exceeds maximum difference for synchronizatio n MAP Dialog <Additional Text>
Major
E M P T Y
EMPTY
R N U
DAP application has detected a failure of a critical task that has triggered HA recovery action. The HA recovery action would involve any of the following actions. Restart of the DAP, Switchover to Standby side in Bi-nodal DAP, Shutdown of the DAP, or Reboot of the DAP node. The time difference between the NMS and the NE was larger than the maximum value for automatic synchronization to be completed.
Critical
E M P T Y
EMPTY
Monitor the DAP/iHLR and/or the network traffic.
R N U C
101312
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
<File system name> File System Set Excessive at <%> utilization
Critical
E M P T Y
EMPTY
101312
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. File System <Set or Clear> Excessive at
Critical
E M P T Y
EMPTY
A high number of DAP-iHLR procedures (likely due to registration-related traffic) may cause the DAP to run out of MAP Dialogs. Once that maximum limit is reached, no more DAP-iHLR procedures will be initiated until existing Dialogs complete.. <Additional Text>= "Threshold Limit Reached" or "Usage Normal" R N M The reported file system is C almost full. WHERE: <file system name> ={ a string containing the file system name (mount point with path)}, <% utilization> = {current utilization % 0 - 100%}. Applies to SCPDAP only R N M The reported file system is C almost full. WHERE: <file system name> ={ a string containing the file system name (mount point with path)}, <%
October 30, 2008
CCPHADAP-19

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Comments & Notes
nstance>
<%> utilization
101312
101313
ACG in LoopBack
101314
DAP LAPD msg to ACG dropped
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 4.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 4.1.1.1.
HADAP_CP U_ALM
<File system name> File System Clear Excessive
Critical
EMPTY
HADAP_FR _ALM
110000
Acg number <ACG_ID> is in loopback
Critical
EMPTY
Identify and remove T1 loop.
utilization> = {current utilization % 0 - 100%}. Applies to ATCADAP only R N M The reported file system is C unmounting. WHERE: <file system name> = {a string containing the file system name (mount point with path)}. Applies to ATCA-DAP only R N U The T1 to an ACG is "loopback" C to the DAP. The EBTS is off the air. WHERE <ACG Id> = {110000}
HADAP_FR _ALM
110000
Discarding LAPD msg for ACG <ACG Id>
Warning
EMPTY
103400
Buffer Pool Utilization: Medium
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Major
E M P T Y
EMPTY
Discarding a LAPD message due to LAPD Queue is overloaded: temporary link failure causes many retransmissions; too many control messages to SatCOW site Contact the iDEN Customer Network Resolution Center for assistance.
R N U C
<ACG ID> = {1-10000}
R N U C
103401
Buffer Pool Utilization: Critical
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Critical
E M P T Y
EMPTY
R N U C
103402
GCI Load Shedding: Call Processing
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6.
HADAP_CP U_ALM
HADAP_APP :203
Major
E M P T
EMPTY
R N U C
Buffers are running low. Additional text in alarm consists of Resource Usage { 1-100% }, Resource Type { MM Buffer pool , System Buffer Pool, CP Buffer Pool } MM => Mobility Management, CP=> Call Processing Buffers are running critically low. Additional text in alarm consists of Resource Usage { 1-100% }, Resource Type { MM Buffer pool , System Buffer Pool, CP Buffer Pool } MM => Mobility Management, CP=> Call Processing High number of global call identifiers utilized is causing calls to be rejected. Additional text in alarm consists of
CCPHADAP-20
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Inst Alarm Code Text Severity R e l a t e d A l a r m s Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Comments & Notes
103403
GCI Load Shedding: Mobility Management
1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1. 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
EMPTY
Major
EMPTY
R N U C
103404
DAP Shutting Down
HADAP_CP U_ALM
Critical
E M P T Y
103405
DAP Delayed Restart Scheduled
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID>
HADAP_CP U_ALM
1-15
<Additional Information>R estart time: <HH:MM:SS>
Critical
1 0 3 2 0 1
HADAP_MODE: 801,804 HADAP_NODE:901,9 03 HADAP_APP_ROLLU P: 301-303 HADAP_APP:201, 202, 205 HADAP_CP_APP: 201,202 HADAP_APP: 202 HADAP_CP_APP: 202 HADAP_NODE: 903
R Y U C
Resource Type {PC/CA/MSS GCI pool, SDGC pool} High number of global call identifiers utilized is causing mobility procedures to be rejected. Additional text in alarm consists of Resource Type {PC/CA/MSS GCI pool, SDGC pool} The DAP is being shut down for maintenance or software upgrade.
1)The operator can perform a manual restart.
R N U C
103406
DAP Delayed Restart Initiated
103407
Call Processing CPU Load Shedding: Medium
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID> 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
1-15
Critical
HADAP_CP U_ALM
Major
1 0 3 4 0 5 E M P T Y
HADAP_APP:202 HADAP_CP_APP: 202
R Y U
1) DAP has detected a noncritical failure that requires a DAP restart to recover. 2) Since the failure is non-critical a delayed restart is scheduled to restart and switchover the DAP during the maintenance window.3)Unlike the set alarm, the clear alarm will not state the time of planned restart DAP is restarted and switchover to the standby node is initiated to recover a non-critical failure.
HADAP_LOAD_SHE DDING: 101,102 HADAP_APP: 203,204 HADAP_CP_APP 203, 204
1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Network
R N U C
High CPU utilization is causing Intra-urban probing (target DAP location) to be dropped.
October 30, 2008
CCPHADAP-21

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Comments & Notes
103408
Call Processing CPU Load Shedding: Critical
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Critical
E M P T Y
HADAP_LOAD_SHE DDING: 101,102 HADAP_APP: 203,204 HADAP_APP_ROLLU P: 302, 303 HADAP_NODE: 901904 HADAP_CP_APP 203, 204
103409
DVLR Audit CPU Load Shedding: Low
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Minor
E M P T Y
EMPTY
103410
DVLR Audit CPU Load Shedding: Medium
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Major
E M P T Y
EMPTY
103411
RAG Download CPU Load Shedding: Medium
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Major
E M P T Y
EMPTY
Resolution Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Network Resolution Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Contact the iDEN Customer Network Resolution Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Network Resolution Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform
R N U C
High CPU utilization is causing Dispatch call originations (for SDGC, both initial and callback) and PD page requests to be dropped.
R N U C
High CPU utilization is causing Fleet Lifetime, MDG, and Consistency Audits to be reduced.
R N U C
High CPU utilization is causing all Audits (Sub/Fleet Capacity, Sub Lifetime) and Removals (fleets/modes) to be reduced.
R N U C
High CPU utilization is causing RAG downloads rates to be reduced
CCPHADAP-22
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Remedy
R e p o r t &
O u t a g e
Comments & Notes
103412
RAG Download CPU Load Shedding: Critical
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Critical
E M P T Y
EMPTY
103413
Mobility Management CPU Load Shedding: Medium
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Major
E M P T Y
EMPTY
103414
Registration Renewal Required CPU Load Shedding: Low
1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.
HADAP_CP U_ALM
Minor
E M P T Y
EMPTY
qualityOfSer viceFailureE
103415
Max Restarts Reached
1.3.6.1.4. 1.161.3.3
HADAP_CP U_ALM
1-300
Critical
1 0
HADAP_NODE: 903
migration to distribute load to other DAPs. 3) Contact the iDEN Customer Network Resolution Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Network Resolution Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Possibly perform migration to distribute load to other DAPs. 3) Contact the iDEN Customer Network Resolution Center for assistance. 1) Analyze trends of DAP CPU utilization statistics to determine whether new DAP is needed. 2) Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network
R N U C
High CPU utilization is causing RAG downloads to be stopped or postponed.
R N U C
High CPU utilization is causing background fault recovery procedures to be dropped.
R N U C
High CPU utilization is causing Registration Renewal Required procedures to be dropped.
R Y D
This alarm will be generated when the configured number of
October 30, 2008
CCPHADAP-23

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s 3 4 0 4 E M P T Y
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Comments & Notes
vent
103416
DVLR's Current LDRI
.10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID> 1.3.6.1.4. 1.161.3.3 .10.5.7.1. 1.2.3.1.6. 1.1.1.1.< DAP_ID>
restarts limit is reached
HADAP_CP U_ALM
1-300
D-VLR <initialized/reinitialized> with <New LDRI>
Major
EMPTY
Reregister subscribers.
R N U
1) Logged when D-VLR is recovered, created or reinitialized. 2) If D-VLR is created or reinitialized, existing subscribers in the D-VLR were discarded and D-VLR is using new LDRI set. 3) During initialization of the DAP, the need for a new LDRI would be an unrecoverable DVLR. After initialization is complete, the need for a new LDRI would be another DAP claiming the current LDRI set used by the current DAP.
CCPHADAP-24
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
LOGICAL LINK DOWN VERSION CHECK SUCCEED ED TERMINA TED BY DAP TERMINA TED BY DAP VERSION CHECK FAILED APPLICAT ION STARTED
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.1.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.1.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.1.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.1.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.1.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.202.<UANC>.<INST ANCE>
HADAP_AC G_LINK
1-10000
U-E-A
U-DIdl
EMPTY
101650
1 0
HADAP_AC G_LINK
1-10000
U-DIdl
U-E-A
EMPTY
101650
The (logical non-fault-tolerant) link was available and had a physical connection when its logical connection went down. MOC=1 The link's logical connection was totally up when link version checking succeeded. MOC=1 The link was deleted from OLCC operation. MOC=1 The link was deleted from OLCC operation. MOC=1 The link was fully operational when link version check was conducted but failed. MOC=1 Application has been started/automatically restarted. MOC=202; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing Application has failed. MOC=202; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing Application has failed. MOC=202; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing Application has been started/automatically restarted. After restart, the DAP has been impaired by load shedding hence directly gone to Impaired before becoming Active. MOC=202; Instances: 1 = Mobility Management, 2 = Call
1 1 1 1 1 3 2 0 1
HADAP_AC G_LINK HADAP_AC G_LINK HADAP_AC G_LINK HADAP_AP P
1-10000
U-E-A
U-DIdl U-DIdl U-DIdl U-E-A
EMPTY
EMPTY
Deleted Link
1-10000
U-DIdl U-E-A
EMPTY
EMPTY
Deleted Link
1-10000
EMPTY
101652
Version check failed DAP is starting up
1-4
U-DIdl
EMPTY
103404
2 0 2 2 0 2 2 0 3
APPLICAT ION FAILED APPLICAT ION FAILED LOAD SHEDDIN G ACTIVE
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.202.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.202.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.202.<UANC>.<INST ANCE>
HADAP_AP P
1-4
U-E-A
U-DIdl
EMPTY
103404, 103405, 103406, 103404, 103405, 103406 103407, 103408
EMPTY
HADAP_AP P
1-4
U-EImp
U-DIdl
EMPTY
EMPTY
HADAP_AP P
1-4
U-DIdl
U-EImp
EMPTY
Application started while processing load is too high
October 30, 2008
CCPHADAP-25

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
2 0 3
LOAD SHEDDIN G ACTIVE
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.202.<UANC>.<INST ANCE>
HADAP_AP P
1-4
U-E-A
U-EImp
EMPTY
103402, 103407, 103408
EMPTY
2 0 4
LOAD SHEDDIN G INACTIVE
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.202.<UANC>.<INST ANCE>
HADAP_AP P
1-4
U-EImp
U-E-A
EMPTY
103407, 103408
Load Shedding is cleared
2 0 5 2 0 5 3 0 1 3 0 1 3 0 2
3 0 2
3 0 3
3 0
APPLICAT ION SHUTDO WN APPLICAT ION SHUTDO WN CRITICAL FUNCTIO NALITY LOST CRITICAL FUNCTIO NALITY LOST ALL APPLICAT IONS FUNCTIO NAL ALL APPLICAT IONS FUNCTIO NAL ONE OR MORE APPLICAT IONS NOT FUNCTIO NAL ONE OR MORE
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.202.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.202.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.203.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.203.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.203.<UANC>.<INST ANCE>
HADAP_AP P
1-4
U-EImp
U-DIdl
EMPTY
103404
HADAP_AP P
1-4
U-E-A
U-DIdl
EMPTY
103404
HADAP_AP P_ROLLUP
U-E-A
U-DIdl
HADAP_A PP: 202
103404, 103202
Processing, 3 = Billing, 4 = I/O Routing Application is being impacted by load shedding procedures. MOC=202; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing Application is no longer being impacted by load shedding procedures. MOC=202; Instances: 1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing <UANC>={UANC for this DAP}, <Inst> ={1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing}. MOC=202 <UANC>={UANC for this DAP}, <Inst> ={1 = Mobility Management, 2 = Call Processing, 3 = Billing, 4 = I/O Routing}. MOC=202 Critical application functionality has been lost. MOC=203
HADAP_AP P_ROLLUP
U-EImp
U-DIdl
HADAP_A PP: 202
103404, 103202
Critical application functionality has been lost. MOC=203
HADAP_AP P_ROLLUP
U-DIdl
U-E-A
HADAP_A PP: 201
103404
DAP is starting up
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.203.<UANC>.<INST ANCE>
HADAP_AP P_ROLLUP
U-EImp
U-E-A
HADAP_A PP: 201
103408
Task no longer load shedding
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.203.<UANC>.<INST ANCE>
HADAP_AP P_ROLLUP
U-DIdl
U-EImp
HADAP_A PP: 202
103404
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.203.<UANC>.<INST
HADAP_AP P_ROLLUP
U-E-A
U-EImp
HADAP_A PP: 202
103408
Task is impaired due to load
CCPHADAP-26
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Event Description
O u t a g e ( Y / N )
Comments & Notes
2 0 1
APPLICAT IONS NOT FUNCTIO NAL APPLICAT ION STARTED
ANCE>
shedding
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.22.<UANC>.<INSTA NCE>
HADAP_CP _APP
1-4
U-DIdl
U-E-A
EMPTY
103404
DAP is starting up
2 0 2 2 0 2 2 0 3
APPLICAT ION FAILED APPLICAT ION FAILED LOAD SHEDDIN G ACTIVE
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.22.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.22.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.22.<UANC>.<INSTA NCE>
HADAP_CP _APP
1-4
U-E-A
U-DIdl
EMPTY
103404
EMPTY
HADAP_CP _APP
1-4
U-EImp
U-DIdl
EMPTY
103404
EMPTY
HADAP_CP _APP
1-4
U-DIdl
U-EImp
EMPTY
103407, 103408
EMPTY
2 0 3
LOAD SHEDDIN G ACTIVE
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.22.<UANC>.<INSTA NCE>
HADAP_CP _APP
1-4
U-E-A
U-EImp
EMPTY
103407, 103408
EMPTY
2 0 4
LOAD SHEDDIN G INACTIVE LOGICAL LINK DOWN VERSION CHECK SUCCEED ED TERMINA TED BY DAP TERMINA TED BY DAP VERSION
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.22.<UANC>.<INSTA NCE>
HADAP_CP _APP
1-4
U-EImp
U-E-A
EMPTY
103407, 103408
EMPTY
1 0
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.21.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.21.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.21.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.21.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1
HADAP_HL R_HN_LIN K HADAP_HL R_HN_LIN K HADAP_HL R_HN_LIN K HADAP_HL R_HN_LIN K HADAP_HL
1-300
U-E-A
U-DIdl U-E-A
EMPTY
101301, 101672 101672
1-300
U-DIdl
EMPTY
Application has been started/automatically restarted. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Application has failed. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Application has failed. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Application is loadshedding. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Application is loadshedding. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call Application is not loadshedding. MOC=22; Instances: 1 = Private Call, 2 = Group Call, 3 = Call Alert/MS Status, 4 = Selective Dynamic Group Call TCP/IP connectivity lost; inter urban link; OMC display UANC. MOC=21 Link Version Check procedure passed; inter urban link; OMC display UANC. MOC=21 The link was deleted from OLCC operation. MOC=21 The link was deleted from OLCC operation. MOC=21 Link Version Check procedure failed;
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
1 1 1 1 1
1-300
U-E-A
U-DIdl U-DIdl U-D-
EMPTY
EMPTY
Deleted Link
1-300
U-DIdl U-E-A
EMPTY
EMPTY
Deleted Link
1-300
EMPTY
101672
Version check
October 30, 2008
CCPHADAP-27

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent esmrStateCh angeEvent
3 1 4
1 0
1 1 1 1 1 3 1 4
4 0 1 4 0 1 4 0 2 4 0 2 4 0 3
CHECK FAILED OPERATO R TERMINA TED CONNECT ION LOGICAL LINK DOWN VERSION CHECK SUCCEED ED TERMINA TED BY DAP TERMINA TED BY DAP VERSION CHECK FAILED OPERATO R TERMINA TED CONNECT ION PARTIAL LINK CONNECT IVITY PARTIAL LINK CONNECT IVITY ALL LINKS FAILED ALL LINKS FAILED ALL LINKS OPERATI ONAL
.2.5.1.4.21.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.21.<UANC>.<INSTA NCE>
R_HN_LIN K HADAP_HL R_HN_LIN K
Idl 1-300 U-E-A U-DIdl EMPTY 101672
failed Operator Terminated connection N U
inter urban link; OMC display UANC. MOC=21 Operator terminated this link; inter urban link; OMC display UANC. MOC=21
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.3.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.3.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.3.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.3.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.3.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.3.<UANC>.<INSTAN CE>
HADAP_HL R_LINK HADAP_HL R_LINK
1-8
U-E-A
U-DIdl U-E-A
EMPTY
101301, 101672 101672
1-8
U-DIdl
EMPTY
TCP/IP connectivity lost; intra urban link. MOC=3 Link Version Check procedure passed; intra urban link. MOC=3
HADAP_HL R_LINK HADAP_HL R_LINK HADAP_HL R_LINK HADAP_HL R_LINK
1-8
U-E-A
U-DIdl U-DIdl U-DIdl U-DIdl
EMPTY
EMPTY
Deleted Link
The link was deleted from OLCC operation. MOC=3 The link was deleted from OLCC operation. MOC=3 Link Version Check procedure failed; intra urban link. MOC=3 Operator terminated this link; inter urban link. MOC=3
1-8
U-DIdl U-E-A
EMPTY
EMPTY
Deleted Link
1-8
EMPTY
101672
Version check failed Operator Terminated connection
1-8
U-E-A
EMPTY
101672
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.13.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.13.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.13.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.13.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.13.<UANC>.<INSTA NCE>
HADAP_HL R_LINK_R OLLUP HADAP_HL R_LINK_R OLLUP HADAP_HL R_LINK_R OLLUP HADAP_HL R_LINK_R OLLUP HADAP_HL R_LINK_R OLLUP
U-DIdl
U-EImp
HADAP_H LR_LINK: 10 HADAP_H LR_LINK: 9, 13, 14 HADAP_H LR_LINK: 9, 13, 14 HADAP_H LR_LINK: 9, 13, 14 HADAP_H LR_LINK: 10, 11
101672
U-E-A
U-EImp
101672
U-EImp U-E-A
U-DIdl U-DIdl U-E-A
101672
All links failed
101672
All links failed
U-EImp
101672
One or more DAP links to the iHLR are not fully operational. This rollup only applies to local DAP-HLR links. MOC=13 One or more DAP links to the iHLR are not fully operational. This rollup only applies to local DAP-HLR links. MOC=13 All DAP links to the iHLR are failed. This rollup only applies to local DAPHLR links. MOC=13 All DAP links to the iHLR are failed. This rollup only applies to local DAPHLR links. MOC=13 All DAP links to the network element are fully operational. This rollup only applies to local DAP-HLR links.
CCPHADAP-28
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Event Description
O u t a g e ( Y / N )
Comments & Notes
4 0 3 9
ALL LINKS OPERATI ONAL LOGICAL LINK DOWN VERSION CHECK SUCCEED ED TERMINA TED BY DAP TERMINA TED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED HW CONTAIN ER RESTORE D FULL FUNCTIO NALITY HW CONTAIN ER LOST FULL FUNCTIO NALITY HW CONTAIN ER LOST PARTIAL FUNCTIO NALITY HW CONTAIN ER LOST FULL
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.13.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.20.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.20.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.20.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.20.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.20.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.20.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
HADAP_HL R_LINK_R OLLUP HADAP_H N_LINK HADAP_H N_LINK
U-DIdl
U-E-A
HADAP_H LR_LINK: 10, 11 EMPTY
101672
1-300
U-E-A
U-DIdl U-E-A
1 0
1-300
U-DIdl
EMPTY
101300, 101301, 103300 101300, 101301, 103300 EMPTY
MOC=13 All DAP links to the network element are fully operational. This rollup only applies to local DAP-HLR links. MOC=13 TCP/IP connectivity lost; inter urban link. OMC display UANC. MOC=20 Link Version Check procedure passed; inter urban link. OMC display UANC. MOC=20 The link was deleted from OLCC operation. MOC=20 The link was deleted from OLCC operation. MOC=20 Link Status Check has failed; inter urban link. OMC display UANC. MOC=20 Link Version Check procedure failed; inter urban link. OMC display UANC. MOC=20 HW Container has become operational. MOC=101
1 1 1 1 1 2 1 3 6 0 1
HADAP_H N_LINK HADAP_H N_LINK HADAP_H N_LINK HADAP_H N_LINK HADAP_H W_CONTAI NER
1-300
U-E-A
U-DIdl U-DIdl U-DIdl U-DIdl U-E-A
EMPTY
Deleted Link
1-300
U-DIdl U-E-A
EMPTY
EMPTY
Deleted Link
1-300
EMPTY
1-300
U-E-A
EMPTY
U-DIdl
EMPTY
101300, 101301, 103300 101300, 101301, 101661 101302,1 01303,10 1305,101 306,1013 09,10132 4,101325 101302,1 01303,10 1305,101 306,1013 09,10132 4,101325 101302,1 01303,10 1305,101 306,1013 09,10132 4,101325 101302,1 01303,10 1305,101 306,1013
Heartbeat check failure Version check failed EMPTY
6 0 2
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
HADAP_H W_CONTAI NER
U-E-A
U-DIdl
EMPTY
EMPTY
HW Container functionality has been lost.MOC=101
6 0 3
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
U-E-A
U-EImp
EMPTY
EMPTY
HW Container has partially failed one or more FRUs are not operational. MOC=101
6 0 4
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
U-EImp
U-DIdl
EMPTY
EMPTY
October 30, 2008
CCPHADAP-29

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
6 0 5
6 2 2
1 0
1 1 1 1 1 2 1 3 4 0 1 4 0 1 4 0 2
FUNCTIO NALITY HW CONTAIN ER RESTORE D PARTIAL FUNCTIO NALITY HW CONTAIN ER RESTORE D FULL FUNCTIO NALITY LOGICAL LINK DOWN VERSION CHECK SUCCEED ED TERMINA TED BY DAP TERMINA TED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED PARTIAL LINK CONNECT IVITY PARTIAL LINK CONNECT IVITY ALL LINKS FAILED
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
U-DIdl
U-EImp
EMPTY
09,10132 4,101325 101302,1 01303,10 1305,101 306,1013 09,10132 4,101325
EMPTY
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
U-EImp
U-E-A
EMPTY
101302,1 01303,10 1305,101 306,1013 09,10132 4,101325 101300, 101301, 101663 101300, 101301, 101663 EMPTY
All HW Container's FRUs are fully operational
All HW Container's FRUs are fully operational. MOC=101
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.7.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.7.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.7.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.7.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.7.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.7.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.16.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.16.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.16.<UANC>.<INSTA NCE>
HADAP_IS G_LINK HADAP_IS G_LINK
1-4
U-E-A
U-DIdl U-E-A
EMPTY
1-4
U-DIdl
EMPTY
TCP/IP connectivity broken. MOC=7
Link Version Check Procedure passed. MOC=7
HADAP_IS G_LINK HADAP_IS G_LINK HADAP_IS G_LINK HADAP_IS G_LINK HADAP_IS G_LINK_R OLLUP HADAP_IS G_LINK_R OLLUP HADAP_IS G_LINK_R OLLUP
1-4
U-E-A
U-DIdl U-DIdl U-DIdl U-DIdl U-EImp
EMPTY
Deleted Link
The link was deleted from OLCC operation. MOC=7 The link was deleted from OLCC operation. MOC=7 iSG is not sending a heartbeat message. MOC=7 Link Version Check procedure failed. MOC=7 One or more DAP links to the iSG are not fully operational. MOC=16
1-4
U-DIdl U-E-A
EMPTY
EMPTY
Deleted Link
1-4
EMPTY
1-4
U-E-A
EMPTY
U-DIdl
HADAP_IS G_LINK: 10 HADAP_IS G_LINK: 9, 12, 13 HADAP_IS G_LINK: 9, 12, 13
101300, 101301, 101663 101300, 101301, 101666 101663
U-E-A
U-EImp
101663, 101666
One or more DAP links to the iSG are not fully operational. MOC=16
U-EImp
U-DIdl
101663, 101666
All links failed
All DAP links to the iSG are failed. MOC=16
CCPHADAP-30
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Event Description
O u t a g e ( Y / N )
Comments & Notes
4 0 2 4 0 3 4 0 3 9
ALL LINKS FAILED ALL LINKS OPERATI ONAL ALL LINKS OPERATI ONAL LOGICAL LINK DOWN VERSION CHECK SUCCEED ED TERMINA TED BY DAP TERMINA TED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED PARTIAL LINK CONNECT IVITY PARTIAL LINK CONNECT IVITY ALL LINKS FAILED ALL LINKS FAILED ALL LINKS OPERATI ONAL ALL LINKS
1 0
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.16.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.16.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.16.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.23.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.23.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.23.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.23.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.23.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.23.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.24.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.24.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.24.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.24.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.24.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1
HADAP_IS G_LINK_R OLLUP HADAP_IS G_LINK_R OLLUP HADAP_IS G_LINK_R OLLUP HADAP_IV PU_LINK HADAP_IV PU_LINK
U-E-A
U-DIdl U-E-A
U-EImp U-DIdl U-E-A
U-E-A
1-252
U-DIdl U-E-A
HADAP_IS G_LINK: 9, 12, 13 HADAP_IS G_LINK: 10, 11 HADAP_IS G_LINK: 10, 11 EMPTY
101663, 101666 101663
All links failed
All DAP links to the iSG are failed. MOC=16 All DAP links to the iSG are fully operational. MOC=16 All DAP links to the iSG are fully operational. MOC=16 TCP/IP connectivity lost. MOC=23
101663
101300, 101668 101300, 101668
1-252
U-DIdl
EMPTY
Link Version Check procedure passed. MOC=23
1 1 1 1 1 2 1 3 4 0 1 4 0 1 4 0 2 4 0 2 4 0 3 4
HADAP_IV PU_LINK HADAP_IV PU_LINK HADAP_IV PU_LINK HADAP_IV PU_LINK HADAP_IV PU_LINK_ ROLLUP HADAP_IV PU_LINK_ ROLLUP HADAP_IV PU_LINK_ ROLLUP HADAP_IV PU_LINK_ ROLLUP HADAP_IV PU_LINK_ ROLLUP HADAP_IV
1-252
U-E-A
EMPTY
EMPTY
Deleted Link
The link was deleted from OLCC operation. MOC=23 The link was deleted from OLCC operation. MOC=23 Link Status Check has failed. MOC=23 Link Version Check procedure failed. MOC=23 One or more DAP links to the iVPU are not fully operational. MOC=24
1-252
U-DIdl U-E-A
EMPTY
EMPTY
Deleted Link
1-252
EMPTY
101300, 101668 101300, 101670 101668
1-252
U-E-A
EMPTY
U-DIdl
HADAP_IV PU_LINK: 10 HADAP_IV PU_LINK: 9, 12, 13 HADAP_IV PU_LINK: 9, 12, 13 HADAP_IV PU_LINK: 9, 12, 13 HADAP_IV PU_LINK: 10, 11 HADAP_IV
U-E-A
U-EImp
101668, 101670
One or more DAP links to the iVPU are not fully operational. MOC=24
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
U-EImp U-E-A
U-DIdl U-DIdl U-E-A
101668, 101670 101668, 101670 101668, 101670 101668,
All links failed
All DAP links to the iVPU are failed. MOC=24 All DAP links to the iVPU are failed. MOC=24 All DAP links to the iVPU are fully operational. MOC=24 All DAP links to the iVPU are fully
All links failed
U-EImp U-D-
U-E-A
October 30, 2008
CCPHADAP-31

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
0 3 9
1 0
1 1 1 1 1 2 1 3 4 0 1 4 0 1 4 0 2 4 0 2 4 0 3 4 0 3 1 0 1
OPERATI ONAL LOGICAL LINK DOWN VERSION CHECK SUCCEED ED TERMINA TED BY DAP TERMINA TED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED PARTIAL LINK CONNECT IVITY PARTIAL LINK CONNECT IVITY ALL LINKS FAILED ALL LINKS FAILED ALL LINKS OPERATI ONAL ALL LINKS OPERATI ONAL LOAD SHEDDIN G OCCURRI
.2.5.1.4.24.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.8.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.8.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.8.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.8.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.8.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.8.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.12.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.12.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.12.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.12.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.12.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.12.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.201.<UANC>.<INST ANCE>
PU_LINK_ ROLLUP HADAP_LI NK HADAP_LI NK
Idl 1-15 U-E-A U-DIdl U-E-A
PU_LINK: 10, 11 EMPTY
101670 101300, 101301, 103300 101300, 101301, 103300 EMPTY Logical Link is no longer connected to NE Version check succeeded N U
operational. MOC=24 TCP/IP connectivity lost; intra urban link. MOC=8 Link Version Check Procedure passed; intra urban link. MOC=8
1-15
U-DIdl
EMPTY
HADAP_LI NK HADAP_LI NK HADAP_LI NK HADAP_LI NK HADAP_LI NK_ROLLU P HADAP_LI NK_ROLLU P HADAP_LI NK_ROLLU P HADAP_LI NK_ROLLU P HADAP_LI NK_ROLLU P HADAP_LI NK_ROLLU P HADAP_LO AD_SHED DING
1-15
U-E-A
EMPTY
Deleted Link
The link was deleted from OLCC operation. MOC=8 The link was deleted from OLCC operation. MOC=8 Link Status Check has failed; intra urban link. MOC=8 Link Version Check procedure failed; intra urban link. MOC=8 One or more DAP links to the peer DAP are not fully operational. This rollup only applies to local DAP-DAP links. MOC=12 One or more DAP links to the peer DAP are not fully operational. This rollup only applies to local DAP-DAP links. MOC=12 All DAP links to the peer DAP are failed. This rollup only applies to local DAP-DAP links. MOC=12 All DAP links to the peer DAP are failed. This rollup only applies to local DAP-DAP links. MOC=12 All DAP links to the peer DAP are fully operational. This rollup only applies to local DAP-DAP links. MOC=12 All DAP links to the peer DAP are fully operational. This rollup only applies to local DAP-DAP links. MOC=12 The DAP processing load has exceeded its `normal' level and load shedding has been initiated. MOC=201
1-15
U-DIdl U-E-A
EMPTY
EMPTY
Deleted Link
1-15
EMPTY
1-15
U-E-A
EMPTY
U-DIdl
HADAP_LI NK: 10
101300, 101301, 103300 101300, 101301, 101661 103300
U-E-A
U-EImp
HADAP_LI NK: 9,12,13 HADAP_LI NK: 9,12,13 HADAP_LI NK: 9,12,13 HADAP_LI NK: 10, 11
103300, 101661
U-EImp U-E-A
U-DIdl U-DIdl U-E-A
103300, 101661 103300, 101661 103300, 101661
All links failed
All links failed
U-EImp
U-DIdl
U-E-A
HADAP_LI NK: 10, 11
103300, 101661
U-E-A
U-EImp
HADAP_A PP: 203
103407, 103408
CCPHADAP-32
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 0 2
1 0
1 1 1 1 1 2 1 3 4 0 1 4 0 1 4 0 2 4 0 2 4 0 3 4 0 3 6
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
NG LOAD SHEDDIN G NOT OCCURRI NG LOGICAL LINK DOWN VERSION CHECK SUCCEED ED TERMINA TED BY DAP TERMINA TED BY DAP STATUS CHECK FAILED VERSION CHECK FAILED PARTIAL LINK CONNECT IVITY PARTIAL LINK CONNECT IVITY ALL LINKS FAILED ALL LINKS FAILED ALL LINKS OPERATI ONAL ALL LINKS OPERATI ONAL MISCELLA
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.201.<UANC>.<INST ANCE>
HADAP_LO AD_SHED DING
U-EImp
U-E-A
HADAP_A PP: 204
103407, 103408
Call Processing is not loadshedding
The DAP processing load has returned to its `normal' level and any load shedding has been terminated. MOC=201 TCP/IP connectivity lost. MOC=4
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.4.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.4.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.4.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.4.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.4.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.4.<UANC>.<INSTAN CE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.15.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.15.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.15.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.15.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.15.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.15.<UANC>.<INSTA NCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1
HADAP_M DG_LINK HADAP_M DG_LINK
1-36
U-E-A
U-DIdl U-E-A
EMPTY
101300, 101654 101300, 101654
1-36
U-DIdl
EMPTY
Link Version Check procedure passed. MOC=4
HADAP_M DG_LINK HADAP_M DG_LINK HADAP_M DG_LINK HADAP_M DG_LINK HADAP_M DG_LINK_ ROLLUP HADAP_M DG_LINK_ ROLLUP HADAP_M DG_LINK_ ROLLUP HADAP_M DG_LINK_ ROLLUP HADAP_M DG_LINK_ ROLLUP HADAP_M DG_LINK_ ROLLUP HADAP_MI
1-36
U-E-A
EMPTY
EMPTY
Deleted Link
The link was deleted from OLCC operation. MOC=4 The link was deleted from OLCC operation. MOC=4 Link Status Check has failed. MOC=4 Link Version Check procedure failed. MOC=4 One or more DAP links to the MDG are not fully operational. MOC=15
1-36
U-DIdl U-E-A
EMPTY
EMPTY
Deleted Link
1-36
EMPTY
101300, 101654 101300, 101656 101654
1-36
U-E-A
EMPTY
U-DIdl
HADAP_M DG_LINK: 10 HADAP_M DG_LINK: 9, 12, 13 HADAP_M DG_LINK: 9, 12, 13 HADAP_M DG_LINK: 9, 12, 13 HADAP_M DG_LINK: 10, 11 HADAP_M DG_LINK: 10, 11 EMPTY
U-E-A
U-EImp
101654, 101656
One or more DAP links to the MDG are not fully operational. MOC=15
U-EImp U-E-A
U-DIdl U-DIdl U-E-A
101654, 101656 101654, 101656 101654
All links failed
All DAP links to the MDG are failed. MOC=15 All DAP links to the MDG are failed. MOC=15 All DAP links to the MDG are fully operational. MOC=15 All DAP links to the MDG are fully operational. MOC=15 Miscellaneous Container's
All links failed
U-EImp U-DIdl U-E-
U-E-A
101654, 101656 101302,1
U-E-A
Miscellaneous
October 30, 2008
CCPHADAP-33

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 6
6 1 3
6 1 5
NEOUS CONTAIN ER FULLY OPERATI ONAL MISCELLA NEOUS CONTAIN ER FULLY OPERATI ONAL MISCELLA NEOUS CONTAIN ER FAILURE MISCELLA NEOUS CONTAIN ER PARTLY OPERATI ONAL MISCELLA NEOUS CONTAIN ER FAILURE MISCELLA NEOUS CONTAIN ER PARTLY OPERATI ONAL NODE IN MAINTEN ANCE MODE NODE IN STANDBY MODE
.2.5.1.4.107.<UANC>.<INST ANCE>
SC
Imp
01303,10 1309,101 324,1013 25 U-E-A EMPTY 101302,1 01303,10 1309,101 324,1013 25 101302,1 01303,10 1309,101 310,1013 24,10132 5 101302,1 01303,10 1309,101 310,1013 24,10132 5 101302,1 01303,10 1309,101 310,1013 24,10132 5 101302,1 01303,10 1309,101 310,1013 24,10132 5 103404
components are fully operational
FRUs(power, fan, cpu) are fully operational. MOC=107
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
HADAP_MI SC
U-DIdl
Miscellaneous components (Fans, Power Supplies) are fully operational
Miscellaneous Container's FRUs(power, fan,cpu) has become operational. MOC=107
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
HADAP_MI SC
U-E-A
U-DIdl
EMPTY
All miscellaneous components are no longer operational
Miscellaneous Container(power, fan, cpu) functionality has been lost. MOC=107
6 1 7
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
HADAP_MI SC
U-E-A
U-EImp
EMPTY
All miscellaneous components are partially operational
Miscellaneous Container(power, fan, cpu) has partially failed - one or more FRUs are not operational. MOC=107
6 1 9
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
HADAP_MI SC
U-EImp
U-DIdl
EMPTY
All Miscellaneous Container's FRUs(power, fan, cpu) has become non-operational. MOC=107
6 2 1
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
HADAP_MI SC
U-DIdl
U-EImp
EMPTY
Operation of Miscellaneous Container(power, fan, cpu) is partially restored.Still one or more FRUs but not all of FRUs of the same fru type, are failed. MOC=107
8 0 1
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.208.<UANC>.<INST ANCE>
HADAP_M ODE
U-E-A
U-DIdl
8 0 2
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.208.<UANC>.<INST ANCE>
HADAP_M ODE
U-E-A
U-E-Idl
HADAP_A PP: 202 HADAP_C P_APP: 202 HADAP_A PP: 202 HADAP_C P_APP: 202
Node moves from Active mode to Maintenance mode
<UANC>={UANC for this DAP}
EMPTY
Node moves from Active mode to Standby mode
CCPHADAP-34
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Event Description
O u t a g e ( Y / N )
Comments & Notes
8 0 3
NODE IN ACTIVE MODE
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.208.<UANC>.<INST ANCE>
HADAP_M ODE
U-E-Idl
U-E-A
8 0 4
NODE IN MAINTEN ANCE MODE NODE IN STANDBY MODE
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.208.<UANC>.<INST ANCE>
HADAP_M ODE
U-E-Idl
U-DIdl
8 0 5
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.208.<UANC>.<INST ANCE>
HADAP_M ODE
U-DIdl
U-E-Idl
6 0 7
6 0 8 6 0 9
6 1 0
6 1 1 6 1 2 9 0 1
FRU RESTORE D FULL FUNCTIO NALITY FRU LOST FUNCTIO NALITY FRU RESTORE D PARTIAL FUNCTIO NALITY FRU RESTORE D FUNCTIO NALITY FRU LOST PARTIAL FUNCTIO NALITY FRU LOST FUNCTIO NALITY NODE RESTORE D FULL FUNCTIO NALITY
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE>
HADAP_NI OC
1-2
U-DIdl
U-E-A
HADAP_A PP: 201 HADAP_C P_APP: 201 HADAP_A PP: 202 HADAP_C P_APP: 202 HADAP_A PP: 202 HADAP_C P_APP: 202 EMPTY
EMPTY
Node moves from Standby mode to Active mode
103404
Node moves from Standby mode to Maintenance mode
EMPTY
Node moves from Maintenance mode to Standby mode
101306
FRU has become operational
FRUs has become fully operational. NIOC: MOC=105 Instance=1-2
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE>
HADAP_NI OC HADAP_NI OC
1-2
U-E-A
U-DIdl U-EImp
EMPTY
101306
FRU has become non-operational FRU has become partial operational
1-2
U-DIdl
EMPTY
101306
FRUs has become non-operational or have been removed. NIOC: MOC=105 Instance=1-2 FRUs has become partial operational. NIOC: MOC=105 Instance=1-2
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE>
HADAP_NI OC
1-2
U-EImp
U-E-A
EMPTY
101306
FRUs has become operational. NIOC: MOC=105 Instance=1-2
HADAP_NI OC
1-2
U-E-A
U-EImp
EMPTY
101306
FRU has become partial operational
FRUs has become partial operational. NIOC: MOC=105 Instance=1-2 FRUs has become non-operational or have been removed. NIOC: MOC=105 Instance=1-2 The DAP has restored full functionality. MOC=17
HADAP_NI OC HADAP_N ODE
1-2
U-EImp U-DIdl
U-DIdl U-E-A
EMPTY
101306
FRU has become non-operational DAP is starting up
HADAP_A PP_ROLL UP: 302 HADAP_H W_CONTA INER: 601
103404, 103408
October 30, 2008
CCPHADAP-35

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
9 0 1
NODE RESTORE D FULL FUNCTIO NALITY NODE LOST PARTIAL FUNCTIO NALITY NODE LOST FULL FUNCTIO NALITY NODE LOST FULL FUNCTIO NALITY NODE RESTORE D PARTIAL FUNCTIO NALITY REPLICAT ION IS ACTIVE REPLICAT ION IS ACTIVE REPLICAT ION FAILED
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.204.<UANC>.<INST ANCE>
HADAP_N ODE
U-EImp
U-E-A
9 0 2
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.204.<UANC>.<INST ANCE>
HADAP_N ODE
U-E-A
U-EImp
9 0 3
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.204.<UANC>.<INST ANCE>
HADAP_N ODE
U-E-A
U-DIdl
9 0 3
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.204.<UANC>.<INST ANCE>
HADAP_N ODE
U-EImp
U-DIdl
9 0 4
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.204.<UANC>.<INST ANCE>
HADAP_N ODE
U-DIdl
U-EImp
7 0 1 7 0 1 7 0 2
HADAP_RE PLICATION HADAP_RE PLICATION HADAP_RE PLICATION
U-DIdl U-EImp U-E-A
U-E-A
HADAP_A PP_ROLL UP: 302 HADAP_H W_CONTA INER: 601 HADAP_A PP_ROLL UP: 303 HADAP_H W_CONTA INER: 603 HADAP_A PP_ROLL UP: 301 HADAP_H W_CONTA INER: 602 HADAP_A PP_ROLL UP: 301 HADAP_H W_CONTA INER: 602 HADAP_A PP_ROLL UP: 301 HADAP_H W_CONTA INER: 605 EMPTY
101302, 101303, 101305, 101306
Application task and hardware are restored
The DAP has restored full functionality. MOC=204
103408, 101302, 101303, 101305, 101306 103404, 103405, 103408
Application task is loadshedding or hardware failed
The DAP has lost partial functionality. MOC=204
Application task not responding to poll
103404, 103405, 103408
Application task not responding to poll
103408
The DAP has restored partial functionality. MOC=204
EMPTY
Replication is active Replication is active Replication has failed; Manual recovery is required Replication has failed; Manual recovery is required Replication has
U-E-A
EMPTY
EMPTY
U-DIdl
EMPTY
7 0 2
REPLICAT ION FAILED
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.207.<UANC>.<INST ANCE>
HADAP_RE PLICATION
U-EImp
U-DIdl
EMPTY
esmrStateCh
REPLICAT
1.3.6.1.4.1.161.3.3.10.5.7.1.1
HADAP_RE
U-E-A
U-E-
EMPTY
102800, 102801, 102802, 102806, 102807 102800, 102801, 102802, 102806, 102807 102800,
CCPHADAP-36
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 3
ION DEFFERE D REPLICAT ION DEFFERE D FRU RESTORE D FULL FUNCTIO NALITY FRU LOST FUNCTIO NALITY FRU RESTORE D PARTIAL FUNCTIO NALITY FRU RESTORE D FUNCTIO NALITY FRU LOST PARTIAL FUNCTIO NALITY FRU LOST FUNCTIO NALITY
.2.5.1.4.207.<UANC>.<INST ANCE>
PLICATION
Imp
7 0 3
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.207.<UANC>.<INST ANCE>
HADAP_RE PLICATION
U-DIdl
U-EImp
EMPTY
6 0 7
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.104.<UANC>.<INST ANCE>
HADAP_SC SI
1-4
U-DIdl
U-E-A
EMPTY
102801, 102802, 102806, 102807 102800, 102801, 102802, 102806, 102807 101305
been deferred
Replication has been deferred
EMPTY
FRUs has become operational. SCSI: MOC=104 Instance=1-4
6 0 8 6 0 9
HADAP_SC SI HADAP_SC SI
1-4
U-E-A
U-DIdl U-EImp
EMPTY
101305
EMPTY
1-4
U-DIdl
EMPTY
101305
EMPTY
FRUs has become non-operational or have been removed. SCSI: MOC=104 Instance=1-4 FRUs has become partial operational SCSI: MOC=104 Instance=1-4. Applies to ATCA-DAP only
6 1 0
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.104.<UANC>.<INST ANCE>
HADAP_SC SI
1-4
U-EImp
U-E-A
EMPTY
101305
EMPTY
FRUs has become operational. SCSI: MOC=104 Instance=1-4. Applies to ATCA-DAP only
6 1 1 6 1 2
HADAP_SC SI
1-4
U-E-A
U-EImp
EMPTY
101305
EMPTY
HADAP_SC SI
1-4
U-EImp
U-DIdl
EMPTY
101305
EMPTY
FRU has become partially operational. SCSI: MOC=104 Instance=1-4. Applies to ATCA-DAP only FRUs has become non-operational or have been removed. SCSI: MOC=104 Instance=1-4. Applies to ATCA-DAP only
October 30, 2008
CCPHADAP-37
Release SR17.0
__________________________________ Events
Event Type
Reason Code
OMC Text
MOI Info (Id)
M O I I n f o ( L a b e l ) H A D A P _ S T A T E H A D A P
I n s t
F r o m S t a t e
T o S t a t e
Event Description
O u t a g e ( Y / N )
Comments & Notes
reStartEven t
2, 5
availabilityE vent
0, 1, 3, 5, 9, 10, 13
<universal time> <managed object instance> <usage state> <operational state> <administrative state> <boot ROM version> <software Load version> <database version> <code version> <system description> <latest reset reason> <outage time since latest reset> <reboot time> <boot diagnostics> <universal time> <sequence number> <secondary id> <new mode> <time of switch> <reason code> <old mode> <additional text> <reason text>
1.3.6.1.4.1. 161.3.3.10. 2.3.1.0
E M P T Y
E M P T Y
HADAP_NOD E
E M P T Y
This event is used to inform the OMC whenever DAP starts. The reason code are Operator Requested (2), Software Initiated (5). It also tells the OMC that SNMP agent is operational and is ready to handle request.
N U
Changed the Event Type to reStartEvent to match OMC event window. Added reason code to provide enhanced description for restart trap
EMPTY
E M P T Y
E M P T Y
E M P T Y
EMPTY
E M P T Y
Event is generated when the HADAP mode changes to Maintenance (1), Standby (2), Active (3) . Universal time Time (in GMT) when the trap was generated. Sequence number Integer incremented for each new Availability trap; the valid range is 24 bits (0..16777215) and it wraps back to 1 when incremented past 24 bits. The value of 0 is only used to restart the sequence when no previous information is available. Secondary id HA DAP Node ID. New mode HA DAP nodes new mode. Maintenance (1), Standby (2), Active (3) Time of switch Time (in GMT format) when the HA DAP node entered this mode. Reason Code -- Reason why the HA DAP node entered this mode. Old mode Mode the HA DAP node switched from. Unknown is represented as (0). Maintenance (1), Standby (2), Active (3). Reason text -- Optional text supplied by the operator explaining the reason for requesting a change in mode from Active to Maintenance, Standby to Maintenance, or Active to Standby.
N M
Changed the Event Type to availabilityEvent to match OMC event window.
CCPHADAP-38
October 30, 2008
Release SR17.0
Event Type
Reason Code

OMC Text
MOI Info (Id) M O I I n f o ( L a b e l ) I n s t F r o m S t a t e T o S t a t e Related State Changes R e l a t e d A l a r m s
Event Description
O u t a g e ( Y / N )
Comments & Notes
Reason text is only sent with the Reason Codes: 10 and 13. Additional text Additional information provided by the HA DAP if available to facilitate root cause analysis. Application software version number is appended at the end of this additional text in this format SV=NN.NN.NN.NN {REASON CODE, ACTION, REASON TEXT, ADDITIONAL TEXT } {No Reason Code (0), Used for Standby to Active transitions, N/A, SV=NN.NN.NN.NN} {Platform Hardware Fault (1), None, N/A, SV=NN.NN.NN.NN} {Platform HA Software Fault (3), None, N/A, SV=NN.NN.NN.NN} {Application Software Fault (5), None, N/A, SV=NN.NN.NN.NN} {Operator Initiated Platform (9), Operator initiates the IDEN_APP_SHUTDOWN_NODE command via the ELMT, N/A, SV=NN.NN.NN.NN} {Operator Initiated Platform (9), Operator initiates the IDEN_APP_RESTART_NODE command via the ELMT, N/A, SV=NN.NN.NN.NN} {Operator Initiated Application (10), Application started, N/A, SV=NN.NN.NN.NN} {Operator Initiated Application (10), Reinit configuration downloaded from OMC, New configuration file downloaded, SV=NN.NN.NN.NN} {Operator Initiated Application (10), Stop the application, LMT User-entered reason text, SV=NN.NN.NN.NN} {Provider Active to Standby (13), Force to Standby, LMT User-entered reason text, SV=NN.NN.NN.NN} This event is sent when there is a super user login/logout.
Action Status
0x90,0x9 1,0x92,0 x94
Root or Super User
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
H A D A P
E M P T Y
E M P T Y
E M P T Y
EMPTY
E M P T Y
N D
action status information includes the following information: reason code <user login name> <access level> login/logout. Reason code 0x90=Logged in successfully,0x91=logged out successfully,
October 30, 2008
CCPHADAP-39

Event Type
Reason Code
Release SR17.0
Related State Changes R e l a t e d A l a r m s
OMC Text
MOI Info (Id)
M O I I n f o ( L a b e l )
I n s t
F r o m S t a t e
T o S t a t e
Event Description
O u t a g e ( Y / N )
Comments & Notes
Action Status
0x90
Logged in successfully
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
Action Status
0x91
Logged out successfully
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
Action Status
0x92
Session timed-out
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
H A D A P H A D A P H A D A P H A D A P H A D A P H A D A P H A D A P H A
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M
EMPTY
EMPTY
EMPTY
A LMT or UNIX user has logged in. See the Action Status Information for details
N N
A LMT or UNIX user has logged out. See the Action Status Information for details
N N
A LMT user has been logged out due to session timedout. See the Action Status Information for details
N N
Action Status
0x94
Session Manually Terminated
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
EMPTY
A LMT user login session has been manually terminated. See the Action Status Information for details
N N
Action Status
Background Download started
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
EMPTY
Event is generated if OLCC background download has completed successfully or has failed. In case of failure, Action Status Info details reason for failure.
N D
Action Status
Background Download aborted
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
EMPTY
Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details.
N M
Action Status
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
EMPTY
Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details.
N M
Action Status
Background Download completed successfully
1.3.6.1.4.1. 161.3.3.10.
EMPTY
Event is generated if background download has aborted, completed successfully or has failed. Action
N M
0x92=session timed-out, 0x94=session manually terminated. action status information includes the following information: reason code <user login name> <access level> login. action status information includes the following information: reason code <user login name> <access level> logout. action status information includes the following information: reason code <user login name> <access level> login session timedout. action status information includes the following information: reason code <user login name> <access level> login session manually terminated. The state change was updated to keep it consistent with the code and other documentation and avoid confusion. The state change was updated to keep it consistent with the code and other documentation and avoid confusion. Reason Code 2=Aborted The state change was updated to keep it consistent with the code and other documentation and avoid confusion. Reason Code 3=Failed The state change was updated to keep it
CCPHADAP-40
October 30, 2008
Release SR17.0
Event Type
Reason Code

OMC Text
MOI Info (Id) M O I I n f o ( L a b e l ) D A P H A D A P H A D A P H A D A P H A D A P H A D A P H A D A P H A D A P H A I n s t F r o m S t a t e T o S t a t e Related State Changes R e l a t e d A l a r m s
Event Description
O u t a g e ( Y / N )
Comments & Notes
2.10.1.1.0
P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M
P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M EMPTY
Status Error Code may contain addition details.
Action Status
Background Download Switch started
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure (reason and line number in configuration file). Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details.
N D
Action Status
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
EMPTY
N M
Action Status
Background Download Switch failed
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
EMPTY
Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details.
N M
Action Status
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
EMPTY
Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details.
N M
Action Status
Upgrade Aborted
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0
EMPTY
Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if OLCC background download has been aborted.
N N
consistent with the code and other documentation and avoid confusion. Reason Code 4=Successful The state change was updated to keep it consistent with the code and other documentation and avoid confusion. The state change was updated to keep it consistent with the code and other documentation and avoid confusion. Reason Code 2=Aborted The state change was updated to keep it consistent with the code and other documentation and avoid confusion. Reason Code 3=Failed The state change was updated to keep it consistent with the code and other documentation and avoid confusion. Reason Code 4=Successful Reason Code 2=Aborted. Applies to ATCA-DAP only
Action Status
Upgrade Failed
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0
EMPTY
N N
Reason Code 3=Failed. Applies to ATCA-DAP only
Action Status
Upgrade Completed Successfully
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0
EMPTY
N N
Reason Code 4=Successful. Applies to ATCA-DAP only
Action Status
1,2 or 3
Background Download aborted Incorrect action
1.3.6.1.4.1. 161.3.3.10.
EMPTY
N D
The state change was updated to keep it
October 30, 2008
CCPHADAP-41

Event Type
Reason Code
Release SR17.0
Related State Changes R e l a t e d A l a r m s
OMC Text
MOI Info (Id)
M O I I n f o ( L a b e l ) D A P H A D A P
I n s t
F r o m S t a t e
T o S t a t e
Event Description
O u t a g e ( Y / N )
Comments & Notes
status
2.10.1.2.0
Action Status
1.3.6.1.4.1. 161.3.3.10. 2.10.1.2.0
P T Y E M P T Y
P T Y E M P T Y
P T Y E M P T Y
EMPTY
P T Y E M P T Y
Event is generated if background download abort (bgdlAbort) is successful.
N M
consistent with the code and other documentation and avoid confusion. The state change was updated to keep it consistent with the code and other documentation and avoid confusion. Reason Code 4=Successful
CCPHADAP-42
October 30, 2008
Release SR17.0
_________________________ Alarms
I n s t
CCPiHLR
Alarm Code Text
Remedy
R e p o r t
O u t a g e
Comments & Notes
17668
iHLR Common Agent Registration Failure
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<SERVICE NAME>
A l a r m s C E EMPTY r M i P t T i Y c a l C r i t i c a l C r i t i c a l E 402, 502 M P T Y
No remedy. Wait for situation to clear.
32807
Ethernet Link Down
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
1 4
E-Net Link <Link ID> is down, or Sub Agent Task <Task Name> SMUX link down
Contact the Customer Network Resolution Center for assistance.
Sub Agent unable to register with the Master Agent. <SERVICE NAME>={"MM", "PROVISIONING", "LOAD MANAGEMENT", "NODE STATE MANAGEMENT", "LINK STATE MANAGEMENT", "PROVISIONING MANAGEMENT", "CP"} R N M Ethernet Link is down. <Link C ID>= {1-4}, or Sub Agent Task <Task Name> lost the SMUX link connection with CA. Applies to Alpha iHLR where the instance is 1.
32807
Ethernet Link Down
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
1 4
E-Net id=<value>, name=<text_desc> is <Enabled or Impaired or Disabled>
E 402, 502 M P T Y
Check for the following in the chassis: Both switch blades (SSC) should be installed in the chassis. If the blade is configured as per the configuration given above and if this alarm is still seen, contact the Customer Network
R N M Ethernet Link is enabled or C impaired or disabled. This alarm is used to detect the Ethernet link connection failure. Applies to ATCA-iHLR only.
October 30, 2008
CCPiHLR-1

I n s t
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s Resolution Center for assistance. No action necessary.
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
16384
iHLR Node Shutting Down
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
16388
GTT Update In Progress
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<TEXT STRING>
16390
Provisioning Consistency Check Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
28675
MAP Dialogs Limit Exceeded
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
MAP Dialog <Additional Text>
M a j o r M a j o r W a r n i n g C r i t i c a l
E 205 M P T Y E EMPTY M P T Y E EMPTY M P T Y
R Y U C
iHLR is being shut down for maintenance or software upgrade.
No remedy. Wait for situation to clear. EMPTY
R N U C
GTT file was downloaded. <TEXT STRING>=supporting information text regarding GTT update EMPTY
R N U C
E EMPTY M P T Y
Monitor the DAP, iHLR and/or the network traffic.
R N U C
36864
File Sys Excessive
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
Filesystem is Almost Full: <Partition Id>
36864
File Sys Excessive
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<File system name> File System <Set or Clear> Excessive at <%> utilization
C r i t i c a l C r i t i c a
E EMPTY M P T Y
A high number of DAP-iHLR procedures (likely due to registrationrelated traffic) may cause the iHLR to run out of MAP Dialogs. Once that maximum limit is reached, no more DAP-iHLR procedures will be initiated until existing Dialogs complete. <Additional Text>={"Threshold Limit Reached", "Usage Normal"} R N M The reported file system has a utilization of at least 90%. <Partition Id> = {1-10}. Applies to Alpha iHLR only
E EMPTY M P T Y
R N M The reported file system is almost full. WHERE: <file system name> = {a string containing the file system name (mount point with path)}, <% utilization> = {current utilization % 0 - 100%}. Applies to ATCA-
CCPiHLR-2
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r No action necessary.
36864
File Sys Excessive
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
36865
Buffer Pool Depleted
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<Node> <Pool>
l C r i t i c a l M a j o r M a j o r M a j o r
E EMPTY M P T Y
iHLR only R N M The reported file system is unmounting. WHERE: <file system name> = {a string containing the file system name (mount point with path)}. Applies to ATCA-iHLR only
36866
Buffer Pool Critical
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<Node> <Pool>
100009
1.3.6.1.4.1.1 61.3.3.10.2.6 .1.0
CA_SNTP_ ALM
Time Difference between NMS and NE exceeds maximum difference for synchronization
Contact the Customer Network Resolution Center for assistance. Contact the Customer Network Resolution Center for assistance. Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance. Correct the configuration parameter value.
R N U
Buffers are running low. <Node>= {1=UNIX} <Pool>= {0=32 byte, 1=64 byte, 2=128 byte, 3=256 byte, 4=512 byte, 5=1024 byte} Buffers are running critically low. <Node>= {1=UNIX} <Pool>= {0=32 byte, 1=64 byte, 2=128 byte, 3=256 byte, 4=512 byte, 5=1024 byte}
R N U
100008
Bad Value in the Configuration File
1.3.6.1.4.1.1 61.3.3.10.2.1 4.1.1.0
CA_BADVA L_ALM
Bad Value for OID:<object_id>
M a j o r C r i t i c a l
R N M The time difference between the NMS and the NE was larger than the maximum value for automatic synchronization to be completed. Reason For Change: Added to provide notification of NE losing time synchronization. R N M Bad Value returned in the Configuration File, object_id is the OID that has the bad value
16398
iHLR Configuration Value Invalid
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<SERVICE NAME> <CONFIG FILE TYPE> <PARAMETER NAME>
R N U
iHLR has encountered an invalid configuration parameter. The invalid configuration parameter will be replaced by the default value for the configuration. <SERVICE NAME>={"MM", "PROVISIONING", "LOAD MANAGEMENT", "LINK MANAGEMENT", "NODE STATE MANAGEMENT", "PROVISIONING MANAGEMENT", "CP", "DB"}
October 30, 2008
CCPiHLR-3

I n s t
Release SR17.0
Alarm Code Text
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
16399
iHLR Database Version Incompatibility
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
Expected DB Version: <VERSION NUMBER> Actual DB Version: <VERSION NUMBER>
16400
Incompatible Interface Version
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<iHLR ISDN ADDRESS> <MAP APPLICATION CONTEXT VERSION> <DAP ISDN ADDRESS>
E EMPTY M P T Y
Contact the Customer Network Resource Center.
R N U
<CONFIG FILE TYPE>={INITIAL, OLCC} <PARAMETER NAME>={text string containing the name of parameter} Wrong version database for the iHLR. <VERSION NUMBER>= {S00.00.00-S99.99.99, U00.00.00-U99.99.99}
E EMPTY M P T Y
R N U C
16408
Application Service Cannot Connect To Database
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<SERVICE NAME> SQLCODE:<NUM>, ISAM:<NUM>
16464
iHLR Critical Failure
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<TEXT STRING>
16465
No Gtt Data Found
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
C r i t i c a l C r i t i c a l C r i t i
E EMPTY M P T Y
R N U
E EMPTY M P T Y
R N U C
iHLR has attempted to communicate with DAP, but the MAP Application Context Versions are incompatible. <iHLR ISDN ADDRESS>={00000000000000 0-999999999999999} <MAP APPLICATION CONTEXT VERSION>= {2- 255} <DAP ISDN ADDRESS>={00000000000000 0-999999999999999} Problem with the application establishing a new connection to the database. <SERVICE NAME>={"MM", "Link Management", "Provisioning", "PROVISIONING MANAGEMENT", "CP"} <NUM>={000000-999999} A critical failure has occurred within the software. <TEXT STRING> = {text description of failure}
E EMPTY M P T Y
EMPTY
R N U C
GTT information could not be found.
CCPiHLR-4
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s c a l C r i t i c a l M i n o r M i n o r W a r n i n g W a r n i n g C r i t i c a l
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
16472
GTT Update Rejected
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
VERSION: <GTT VERSION>, <REASON FOR FAILURE>
E EMPTY M P T Y
EMPTY
R N U
The GTT download was rejected by the iHLR. <GTT VERSION>={GTT version downloaded} <REASON FOR FAILURE>={text string describing the cause of the rejection} Large amount of provisioning transactions
16640
Provisioning Transaction Log Full
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
16641
Service Cant Access Log
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<SERVICE NAME>
No Action necessary.
R N U
16642
Cannot Retrieve Database Objects Report
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
Contact the Customer Network Resolution Center for assistance. Contact the Customer Network Resolution Center for assistance. Use the LMT to reverse the permission granted to the Network Management Station. Use the Provisioning interface to check D-VLR address in the subscriber record. Next, check that the Global Title Translation
R N U
Incorrect file permissions. <SERVICE NAME>={LMT, PROVISIONING}
R N U
Insufficient disk space.
16643
Operator Grants Permission for Download
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
E EMPTY M P T Y
R N U C
LMT operator grants permission for the Network Management Station to download a configuration file that breaks GTT data requirements.
17177
Global Title Failure
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
[<imsi>] <isdn>
E EMPTY M P T Y
R N U C
Unable to route to subscriber's D-VLR. [<imsi>={0x0000000000000000 - 0x0999999999999999}] <isdn>={0x0000000000000000 - 0x0999999999999999}
October 30, 2008
CCPiHLR-5

I n s t
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s routing information exists for the given D-VLR. If both are valid, contact Customer Network Resource Center. Check service provider provisioning system for validity of subscriber. If valid, then add subscriber into the iHLR.
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
17260
Subscriber Not In iDEN HLR
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<RC> <IDENTIFIER>
M i n o r
E EMPTY M P T Y
R N U
17263
Invalid SCCH Service and Seed Combination
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<INVALID INSTANCE>
M i n o r
E EMPTY M P T Y
R N U
17408
Database Logs Full
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
M a j o r
E EMPTY M P T Y
17410
Serious Database Problem
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
Dbspace is offline: <DB SPACE NAME> or Index failure:<DBSPACE NAME>:<OWNER>.
C r i t i c
E 702 M P T Y
Backup the iHLR database. Contact the Customer Network Resolution Center for assistance. Contact the Customer Network Resolution Center for assistance.
R N U
The subscriber is not within the iHLR. <RC>={"RC=<RCVAL>"}; <IDENTIFIER>={"<IMSI>", "<UFMI>"}; <RCVAL>={18(CancLoc), 77(GSD), 140(Auth), 160(UL)}; <IMSI> = {0x00000000000000010x0999999999999999}; <UFMI>= {"VAL, VAL, VAL"}; VAL = {0x0001-0xFFFFF} SCCH service is Active and the SCCH seed is not between 1 and 60. <INVALID INSTANCE>={"<IMSI>","<URB AN ID>, <FLEET ID>"} <IMSI>={0x0000000000000000 - 0x0999999999999999} <URBAN ID>={urban id number} <FLEET ID>={fleet id number} iHLR Database logical logs are filled or long transactions caused the logs to fill up. For example, issuing a provisioning delete fleet for a large fleet.
R N U C
iHLR system failure. <DB SPACE NAME>={text string} <OWNER>={text string} <TABLE NAME>={text string} <INDEX NAME>={text string} <CHUNK PATHNAME>={text
CCPiHLR-6
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s <TABLE NAME><INDEX NAME> or Cannot open chunk: <CHUNK PATHNAME> or Cannot open dbspace:<DB SPACE NAME> or SQLCODE:<NUM>, ISAM:<NUM> EMPTY a l
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
string} <NUM>={000000999999}
17411
Database System Not Online
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
17419
DBM Internal System Failure
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<TEXT STRING>
C r i t i c a l M a j o r
E 702 M P T Y
R N U
DB server failure or DB server placed in an off-line state.
E EMPTY M P T Y
17433
Replication reached Threshold One
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
W a r n i n g
1 EMPTY 7 4 3 4 , 1 7 4 3 5 , 1 7 4 3 6 ,
When the switchover has completed, run DB synchronizatio n procedure on the standby node. If outage cannot be fixed, stop ER service using LMT interface.
R N U
Internal DBMS subsystem failure. <TEXT STRING>={description of failure}
R N U
Attempted to delete large fleet or ER long time under outages.
October 30, 2008
CCPiHLR-7

I n s t
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s 1 7 4 3 7 1 EMPTY 7 4 3 3 , 1 7 4 3 5 , 1 7 4 3 6 , 1 7 4 3 7 1 EMPTY 7 4 3 3 , 1 7 4 3 4 ,
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
17434
Replication reached Threshold Two
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
W a r n i n g
If outage cannot be fixed, stop ER service using LMT interface.
R N U
17435
Replication reached Threshold Three
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
W a r n i n g
R N U
CCPiHLR-8
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s 1 7 4 3 6 , 1 7 4 3 7 1 EMPTY 7 4 3 3 , 1 7 4 3 4 , 1 7 4 3 5 , 1 7 4 3 7 M 1 EMPTY a 7 j 4 o 3 r 3 , 1
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
17436
Replication reached Threshold Four
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
W a r n i n g
R N U
17437
Replication reached Critical Threshold
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
EMPTY
System should automatically stop ER service. If automatic stop failed, stop ER service using LMT interface.
R N U
October 30, 2008
CCPiHLR-9

I n s t
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s 7 4 3 4 , 1 7 4 3 5 , 1 7 4 3 6 M E 702 a M j P o T r Y M i n o r M a j o r E 703 M P T Y E 701 M P T Y
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
17440
iHLR Node Loss Replication Synchronization
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
iHLR NODE Loss Replication Synchronization
17441
Replication Transitions from Active state to Deferred State
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
Replication Transitions From Active to Deferred State
17442
Replication Transitions from Deferred State to Active State
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
Replication Transitions From Enabled to Active State
17443
Replication Transitions from Deferred state to Incompatible State
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<PROBLEM DESCRIPTION>
M a j o r
E 702 M P T Y
After both Nodes are repaired, run manual synchronizatio n process. If it was an automatic suspension and repaired, no action necessary. If it was an automatic suspension and repaired, no action necessary. If it was user suspension, user activate. Clean ER resources in both Nodes. Run ER database restoration process.
R N U
ER was dropped by iHLR monitoring task due to loss of resources or ER crashed.
R N U
Any ER outages, including dualnode outages or ER suspended by LMT user.
R N U
Any ER outages, including dualnode outages, ER suspended by LMT user, or ER resources out of limits with DB Monitor dropping ER.
R N U
ER was dropped ungracefully for any reason or ER version between Dispatch Center's HLR Nodes incompatible. <PROBLEM DESCRIPTION>={"Cannot setup ER", "ER version
CCPiHLR-10
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r If network or hardware problem, fix it and using LMT interface reconnect to other Node. Reconfigure Standby Node. Contact the Customer Network Resolution Center for assistance.
17444
iHLR Node Failed to establish ER connection with other iHLR Node
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<PROBLEM TYPE> Problem
M a j o r
E EMPTY M P T Y
R N U
incompatible"} Private network connection failed, Ethernet card in one Node failed or Standby Node configurations incorrect. <PROBLEM TYPE>={"Network", "Configuration"}
18801
Max reboot reached no more reboot allowed
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<TEXT STRING>
18802
Application Service Is Not Aware Of Current Mode State
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<SERVICE NAME>:<TEXT STRING>
18841
Provisioning Critically Impaired
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<TEXT STRING>
C r i t i c a l M i n o r W a r n i n g M a j o r C r i t i c a l
E EMPTY M P T Y
R N U
<TEXT STRING>=supporting information text
R N U C
<SERVICE NAME> = {PROVISIONING} <TEXT STRING>=support information text Critical failure has occurred within Provisioning Application. <TEXT STRING> = {"Provisioning failed to get platform information and cannot be initialized." or a text description of provisioning situation encountered} Indication of the iHLR Load Level. <DIRECTION>={"increased", "decreased"} <VALUE>={0-5} <TYPE>={NO LOAD, CPU, QUEUE, ENET, OVERRIDE} <PROBLEM> = {"e_init_task FAILURE", "UNKNOWN TASK NAME", "ITCU INITIALIZATION FAILURE", "UNIX DOMAIN SOC CREATION FAILURE", "ICP INITIALIZATION FAILURE", "SM INITIALIZATION FAILURE", "TCAP INITIALIZATION
Contact the Customer Network Resolution Center for Assistance.
R N U
18982
iHLR Current Load Shedding Level
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
Load Level <DIRECTION> to level <VALUE> Due to <TYPE>
R N U
28674
MAHT Software Failure
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
SW FAILURE EVENT IN MAHT DUE TO [<PROBLEM>][<LV U RETRY>]
Node switch will fix the problem.
R N U
October 30, 2008
CCPiHLR-11

I n s t
Release SR17.0
Alarm Code Text
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
41042
Task Not Running
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.1.2.0
IHLR_ALA RM_APP
<Task name>(<Task id>) <type> failure
C r i t i c a l
E 202 M P T Y
45058
Power Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 13.[12].6.[101,103 ].<Instance>
IHLR_POW ER_ALM
EMPTY
C r i t i c a l
E IHLR_HW_CONTAI M NER: 601-605, 622 P T Y
equipmentF
45059
Fan Disabled
1.3.6.1.4.1.1
IHLR_FAN_
EMPTY
C E IHLR_HW_CONTAI
If task is critical, then the iHLR node will automatically recover. If task is not critical and it is the standby iHLR node, then restart the iHLR application. If it is the active iHLR node, then restart the iHLR application during the next maintenance window. Try to reintegrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate, replace the hardware or system unit. Try to re-
R N U C
FAILURE", "MAP INITIALIZATION FAILURE", "MAPU INITIALIZATION FAILURE", "LIBGTT ATTACH FAILURE", "MAP SAP CONFIGURATION FAILURE", "SIGSEGV/SIGBUS/SIGFPE/SI GPWR"}; <LVU RETRY> = {LVU RETRY COUNT EXCEEDS MAX VALUE <NUMBER> FOR MAILBOXID <ID>} An iHLR task has not responded to a poll. <Task name>= four letter abbreviation of task name <Task id>= {0-65535} <type>={critical, non-critical}
R Y M A hardware failure has occurred. C Instance 3 will be in impaired condition if there is a fault with one of the power supplies or if sufficient power is not fed to one of the power supplies. Applies to Alpha HA-iHLR only
R N M This alarm is reported as a
CCPiHLR-12
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
Remedy
R e p o r t
O u t a g e
Comments & Notes
ailureEvent
61.3.3.10.5.7 .1.1.2.3.1.6.1 12.[12].5.[401402].<Instan ce>
ALM
r i t i c a l
A l a r m s M NER: 601-605, 622 P T Y
45060
CPU Set Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 11.1.2.[202205,207210].<Instan ce>
IHLR_CPU _ALM
EMPTY
C r i t i c a l
45062
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 17.1.3.[313,3 19].<Instanc e>
IHLR_SCSI _ALM
EMPTY
C r i t i c a l
E M P T Y
IHLR_HW_CONTAI NER: 601-605, IHLR_SCSI: 607608
45063
Synchronous Device Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 18.1.3.[314318].<Instan
IHLR_SYN C_ALM
EMPTY
C r i t i
integrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate, replace the hardware or system unit. Try to reintegrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate, replace the hardware or system unit. Try to reintegrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate, replace the hardware or system unit. Contact Customer Network Resolution Center if needed. Try to reintegrate the failed hardware. If hardware fails
& Y / C N l e a r C
cooling fan has been disabled. Applies to Alpha HA-iHLR only
R Y M A hardware failure has occurred. C Applies to Alpha HA-iHLR only
R N M A hardware failure has occurred. C Applies to Alpha HA-iHLR only
October 30, 2008
CCPiHLR-13

I n s t
Release SR17.0
Alarm Code Text
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r multiple attempts to reintegrate, replace the hardware. Try to reintegrate the failed hardware. If hardware fails multiple attempts to reintegrate, replace the hardware. Try to reintegrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate, replace the hardware or system unit. Try to reintegrate the failed hardware. If hardware fails multiple attempts to reintegrate, replace the hardware. Try to reintegrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate,
ce>
c a l
45064
Asynchronous Device Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 19.[1-2].[16].[314318].<Instan ce>
IHLR_ASY NC_ALM
EMPTY
C r i t i c a l
45065
NIOC Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 20.1.3.[313,3 19,318,324]. <Instance>
IHLR_NIOC _ALM
EMPTY
C r i t i c a l
E M P T Y
IHLR_HW_CONTAI NER: 601-605, 622, IHLR_NIOC: 607612
R N M A hardware failure has occurred. C This alarm is used to detect the Ethernet card failure. Applies to Alpha iHLR only
45066
Router Controller Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 16.1.2.[201,2 06,207,212]. <Instance>
IHLR_ROC _ALM
EMPTY
C r i t i c a l
45070
PLEX Device Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 27.1.1.1.<Ins tance>
IHLR_PLEX _ALM
1 9 9
PLEX Device Disabled, DeviceNumber: <dev_num>
C r i t i c a l
R N M A hardware failure has occurred C where <dev_num> = {1..n}. Applies to Alpha iHLR only
CCPiHLR-14
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s replace the hardware or system unit. Try to reintegrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate, replace the hardware or system unit. Try to reintegrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate, replace the hardware or system unit. Try to reintegrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate, replace the hardware or system unit. Try to reintegrate the failed hardware, if possible. If hardware fails multiple
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
45071
SUBDISK Device Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 26.1.1.1.<Ins tance>
IHLR_SUB DISK_ALM
1 9 9
SUBDISK Device <Disabled or Enabled>
C r i t i c a l
R N M A hardware failure has occurred. C Applies to Alpha iHLR only
45071
SUBDISK Device Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 26.1.1.1.<Ins tance>
IHLR_SUB DISK_ALM
1 8
HARD_DISK DeviceType <DeviceTypeId> Device Id <DeviceID> <Disabled or Impaired or Enabled>
C r i t i c a l
E M P T Y
IHLR_HW_CONTAI NER: 601-605, 622, IHLR_SCSI: 607612
R N M A hardware failure has occurred. C This alarm is used to report SCSI (hard disk) failures. Applies to ATCA-iHLR, where the <DeviceID> = {1..8}
45072
TOY_CLOCK Device Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 25.1.1.1.<Ins tance>
IHLR_TOY _CLOCK_A LM
TOY_CLOCK Device Disabled, DeviceNumber: <dev_num>
C r i t i c a l
R N N C
A hardware failure has occurred where <dev_num> = {1}. Applies to Alpha HA-iHLR only
45073
DEV_TEMP Device Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 24.1.1.1.<Ins tance>
IHLR_DEV _TEMP_AL M
1 7
DEV_TEMP Device Disabled, DeviceNumber: <dev_num>
C r i t i c a
R N N C
A hardware failure has occurred. Applies to SCP HA-iHLR.
October 30, 2008
CCPiHLR-15

I n s t
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s l attempts to reintegrate, replace the hardware or system unit. Try to reintegrate the failed hardware, if possible. If hardware fails multiple attempts to reintegrate, replace the hardware or system unit. Contact the iDEN Customer Network Resolution Center for assistance Check if latch is closed for the front blade and the rear transition blade. If problem persists contact iDEN Customer Network Resolution Center for assistance Contact Customer Network Resolution Center for assistance. Contact
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
45073
DEV_TEMP Device Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 24.1.1.1.<Ins tance>
IHLR_DEV _TEMP_AL M
1 7
DEV_TEMP DeviceType <DeviceTypeId> DeviceId <DeviceID> <Enabled or Disabled>
C r i t i c a l
R N N C
A hardware failure has occurred. <DeviceID> = {1 -7}. Applies to ATCA-IHLR
45326
SYSTEM BUS Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 10.1.1.1.<Ins tance>
IHLR_APP_ ALM
45333
Latch Open
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 10.1.1.1.<Ins tance>
IHLR_APP_ ALM
1 2
SYSTEM_BUS DeviceType <DeviceTypeId> Device Id <DeviceID> <Disabled or Impaired or Enabled> Latch Open <id>
E EMPTY M P T Y
R N N C
A hardware failure has occurred. Applies to ATCA-IHLR only
E EMPTY M P T Y
R N N C
Close the latch to clear the condition. Applies to ATCA-iHLR only.
45330
Timezone Failure
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 10.1.1.1.<Ins tance> 1.3.6.1.4.1.1
IHLR_APP_ ALM
M a j o r
E EMPTY M P T Y
R N N C
Timezone is set based on configuration downloaded from OMC-R. Applies to ATCA-iHLR only.
equipmentF
45331
Voltage Outside
IHLR_APP_
Voltage Device <id>
C E EMPTY
R N N
Voltage Level Outside of given
CCPiHLR-16
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s M P T Y
Remedy
R e p o r t
O u t a g e
Comments & Notes
ailureEvent
Operating Threshold
61.3.3.10.5.7 .1.1.2.3.1.6.1 10.1.1.1.<Ins tance>
ALM
1 7
Outside Operating Range
45332
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 10.1.1.1.<Ins tance>
IHLR_APP_ ALM
1 2
IPMI Controller <id> <Disabled or Enabled>
45334
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 10.1.1.1.<Ins tance>
IHLR_APP_ ALM
45335
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 30.1.1.1.<Ins tance>
IHLR_LM_ ALM
45337
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 10.1.1.1.<Ins tance>
IHLR_APP_ ALM
45324
Memory Disabled
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 10.1.1.1.<Ins tance>
IHLR_APP_ ALM
MEMORY DeviceType <DeviceTypeId> Device Id <DeviceID> <Disabled or Impaired or
r i t i c a l C r i t i c a l C r i t i c a l C r i t i c a l C r i t i c a l C r i t i c a
Customer Network Resolution Center for assistance.
& Y / C N l e a r C
threshold range. Applies to ATCA-iHLR only.
E EMPTY M P T Y
R N N C
IPMI controller is not operational. Applies to ATCAiHLR only.
E EMPTY M P T Y
R N N C
E EMPTY M P T Y
R N N
Update Loads on OMC to versions that not support the hardware version installed. Applies to ATCA-iHLR only.
E EMPTY M P T Y
R Y N C
E EMPTY M P T Y
R N N C
A hardware failure has occurred. An alarm indicating enabled state of HW Device Memory is sent when memory is available, which is CLEAR alarm for HW DEVICE MEMORY. An alarm indicating impaired state of HW
October 30, 2008
CCPiHLR-17

I n s t
Release SR17.0
Alarm Code Text
S e v e r i t y R e l a t e d A l a r m s Enabled> l
Remedy
R e p o r t
O u t a g e
Comments & Notes
& Y / C N l e a r
45340
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 30.1.1.1.<Ins tance>
IHLR_LM_ ALM
<reason>
45323
1.3.6.1.4.1.1 61.3.3.10.5.7 .1.1.2.3.1.6.1 10.1.1.1.<Ins tance>
IHLR_APP_ ALM
1 9 9
DISK VOLUME DeviceType <DeviceTypeId> Device Id <DeviceID> <Disabled or Enabled>
E EMPTY M P T Y
R Y N C
Device Memory is sent when total Memory decreased from last reboot or % mem used over alarm threshold (default = 85%), which is SET alarm for HW DEVICE MEMORY. An alarm indicating disabled state of HW Device Memory is sent when % mem used over recovery threshold (default = 90%) or total memory less than minimum required by config, which is SET alarm for HW DEVICE MEMORY also. In some scenarios, there can be one CLEAR alarm for more than one corresponding SET alarms. Applies to ATCA-iHLR Only Software Upgrade Failure. Where: <reason> displays different reasons for different failure scenarios. Applies to ATCA-iHLR Only
E EMPTY M P T Y
R N N C
A hardware failure has occurred. 99 is the maximum instance of instance. The real instance of VOLUME is decided during runtime, which is around 20. Applies to ATCA-iHLR Only.
CCPiHLR-18
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 0 1 1 0 2 2 0 1
PROCESSING LOAD TOO HIGH
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.201.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.201.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.202.<UANC>.
IHLR_LOA D_SHEDDI NG IHLR_LOA D_SHEDDI NG IHLR_APP
U-E-Idl
U-E-A
203
EMPTY
PROCESSING LOAD NORMAL
U-E-A
U-E-Idl
204
EMPTY
APPLICATION STARTED
1-4, 6
U-DIdl
U-E-A
EMPTY
EMPTY
The iHLR processing load has exceeded normal level and load shedding has been initiated The iHLR processing load has returned to its normal level and load shedding has been terminated. Application has been started or has been recovered.
S t a t u s N U
<UANC>={UANC for this iHLR}
N U
N U
2 0 3
APPLICATION IS LOADSHEDDING
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.202.<UANC>.
IHLR_APP
1-4
U-DIdl
U-EImp
EMPTY
EMPTY
Application is being impacted by load shedding procedures.
N U
2 0 2
APPLICATION FAILED
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.202.<UANC>.
IHLR_APP
1-4, 6
U-E-A
U-DIdl
EMPTY
41042
Application has failed.
N U
2 0 5
APPLICATION SHUTDOWN
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.202.<UANC>.
IHLR_APP
1-4, 6
U-E-A
U-DIdl
EMPTY
16384
The application has shutdown.
N U
2 0
APPLICATION IS LOADSHEDDING
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.202.<UANC>.={UANC for this iHLR}, <Inst>={1 = Mobility Management, 2 = Call Processing, 3 = Provisioning, 4 = Transaction Logging, 6 = Database} <UANC>={UANC for this iHLR}, <Inst>={1 = Mobility Management, 2 = Call Processing, 3 = Provisioning, 4 = Transaction Logging} <UANC>={UANC for this iHLR}, <Inst>={1 = Mobility Management, 2 = Call Processing, 3 = Provisioning, 4 = Transaction Logging, 6 = Database} <UANC>={UANC for this iHLR}, <Inst>={1 = Mobility Management, 2 = Call Processing, 3 = Provisioning, 4 = Transaction Logging, 6 = Database} <UANC>={UANC for this iHLR}, <Inst>={1 = Mobility
October 30, 2008
CCPiHLR-19

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
nst>
procedures.
2 0 4
APPLICATION NOT LOADSHEDDING
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.202.<UANC>.
IHLR_APP
1-4
U-EImp
U-E-A
102
EMPTY
Application is no longer being impacted by load shedding procedures.
N U
2 0 5
APPLICATION SHUTDOWN
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.202.<UANC>.
IHLR_APP
1-4, 6
U-EImp
U-DIdl
EMPTY
16384
The application has shutdown.
N U
2 0 2
APPLICATION FAILED
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.202.<UANC>.
IHLR_APP
1-4, 6
U-EImp
U-DIdl
EMPTY
41042
Application has failed.
N U
3 0 1 3 0 3 3 0 3 3 0 1 3 0 2 9 0 4
CRITICAL APPLICATION FUNCTIONALITY LOST ONE OR MORE APPLICATIONS FUNCTIONALITY LOST ONE OR MORE APPLICATIONS FUNCTIONALITY LOST CRITICAL APPLICATION FUNCTIONALITY LOST ALL APPLICATIONS FUNCTIONAL NODE RESTORED PARTIAL FUNCTIONALITY
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.203.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.203.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.203.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.203.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.203.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.204.<UANC>.
IHLR_APP_ ROLLUP
U-E-A
U-DIdl
EMPTY
EMPTY
One or more critical applications functionality has been lost One or more applications are not fully operational
N U
Management, 2 = Call Processing, 3 = Provisioning, 4 = Transaction Logging} <UANC>={UANC for this iHLR}, <Inst>={1 = Mobility Management, 2 = Call Processing, 3 = Provisioning, 4 = Transaction Logging} <UANC>={UANC for this iHLR}, <Inst>={1 = Mobility Management, 2 = Call Processing, 3 = Provisioning, 4 = Transaction Logging, 6 = Database} <UANC>={UANC for this iHLR}, <Inst>={1 = Mobility Management, 2 = Call Processing, 3 = Provisioning, 4 = Transaction Logging, 6 = Database} <UANC>={UANC for this iHLR}
IHLR_APP_ ROLLUP
U-E-A
U-EImp
EMPTY
EMPTY
N U
IHLR_APP_ ROLLUP
U-DIdl
U-EImp
EMPTY
EMPTY
One or more applications are not fully operational
N U
IHLR_APP_ ROLLUP
U-EImp
U-DIdl
EMPTY
EMPTY
Critical application functionality has been lost.
N U
IHLR_APP_ ROLLUP IHLR_NOD E
U-EImp U-DIdl
U-E-A
EMPTY
EMPTY
All applications are fully operational. The iHLR has restored partial functionality.
N U
<UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR}
U-EImp
EMPTY
EMPTY
N U
CCPiHLR-20
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
9 0 2 9 0 3 9 0 1 9 0 3 4 0 1 4 0 7 4 0 2 4 0 9 4 1 0
NODE LOST PARTIAL FUNCTIONALITY NODE LOST FULL FUNCTIONALITY NODE RESTORED FULL FUNCTIONALITY NODE LOST FULL FUNCTIONALITY LVC SUCCEEDED NODE IN STANDBY MODE LOGICAL LINK DOWN NODE IN STANDBY MODE
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.204.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.204.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.204.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.204.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.205.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.205.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.205.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.205.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.205.<UANC>.
IHLR_NOD E IHLR_NOD E IHLR_NOD E IHLR_NOD E IHLR_DAP _LINK IHLR_DAP _LINK IHLR_DAP _LINK IHLR_DAP _LINK
U-E-A
U-EImp U-DIdl U-E-A
EMPTY
EMPTY
The iHLR has lost partial functionality. The iHLR has lost full functionality. The iHLR has restored full functionality. The iHLR has lost full functionality. Link Version Check procedure passed Link dropped cause the node move to Standby Mode TCP/IP connectivity lost
S t a t u s N U
<UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id} <UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id} <UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id} <UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id} <UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id}
U-E-A
EMPTY
EMPTY
N U
U-EImp U-EImp U-DIdl U-E-A
EMPTY
EMPTY
N U
U-DIdl U-E-A
EMPTY
EMPTY
N U
1 - 300
EMPTY
EMPTY
N U
1 - 300
U-E-Idl
EMPTY
EMPTY
N U
1 - 300
U-E-A
U-DIdl U-E-Idl
EMPTY
EMPTY
N U
1 - 300
U-DIdl
EMPTY
EMPTY
LINK NOT ESTABLISHED
IHLR_DAP _LINK
1 - 300
U-E-Idl
U-DIdl
EMPTY
EMPTY
4 1 2 4 0 1 4 0 7 4 0 2 4 0 9
OPERATOR LINK RESET LVC SUCCEEDED NODE IN STANDBY MODE LOGICAL LINK DOWN NODE IN STANDBY MODE
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.205.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.209.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.209.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.209.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.209.<UANC>.
IHLR_DAP _LINK IHLR_DAP _HN_LINK IHLR_DAP _HN_LINK IHLR_DAP _HN_LINK IHLR_DAP _HN_LINK
1 - 300
U-E-A
U-DIdl U-E-A
EMPTY
EMPTY
Failed connection to DAP has been inactivated. iHLR Node has become the Standby iHLR Node. iHLR Node has transitioned from the Standby Mode to the Active Mode or Maintenance Mode and the DAP has not yet established a connection or the connection failed. EMPTY
N U
N U
N U
1 - 300
U-DIdl U-E-A
EMPTY
EMPTY
Link Version Check procedure passed Link dropped cause the node move to Standby Mode TCP/IP connectivity lost
N U
1 - 300
U-E-Idl
EMPTY
EMPTY
N U
1 - 300
U-E-A
U-DIdl U-E-Idl
EMPTY
32807
N U
1 - 300
U-DIdl
EMPTY
EMPTY
Failed connection to DAP has been inactivated. iHLR Node has become the
N U
<UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id} <UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id} <UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id} <UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id} <UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id}
October 30, 2008
CCPiHLR-21

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
4 1 0
LINK NOT ESTABLISHED
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.209.<UANC>.
IHLR_DAP _HN_LINK
1 - 300
U-E-Idl
U-DIdl
EMPTY
EMPTY
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
4 1 2 5 0 1 5 0 2 5 0 2 5 0 3 5 0 4 5 0 3 5 0 5 5 0 7 5 0 8 5 0 9 5 1 0
OPERATOR LINK RESET ONE OR MORE LINKS LOST ALL LINKS FAILED ALL LINKS FAILED ALL LINKS OPERATIONAL ONE OR MORE LINKS RESTORED ALL LINKS OPERATIONAL ALL LINKS DROPPED ALL LINKS INACTIVE ALL LINKS FAILED
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.209.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.206.<UANC>.
IHLR_DAP _HN_LINK IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP IHLR_DAP _LINK_ROL LUP
1 - 300
U-E-A
U-DIdl U-EImp U-DIdl U-DIdl U-E-A
EMPTY
EMPTY
Standby iHLR Node. iHLR Node has transitioned from the Standby Mode to the Active Mode or Maintenance Mode and the DAP has not yet established a connection or the connection failed. EMPTY
N U
<UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id}
N U
U-E-A
EMPTY
EMPTY
U-E-A
EMPTY
32807
One or more iHLR links to the DAP are not fully operational All iHLR links to the DAP has failed. All iHLR links to the DAP has failed. All iHLR links to the DAP are fully operational One or more iHLR links to the DAP are not fully operational. All iHLR links to the DAP are fully operational All iHLR links to the DAP has been dropped as the node now is Standby All iHLR links to DAPs are inactive for this iHLR Node. All iHLR links to DAPs are failed for this iHLR Node. iHLR Node has become the Active iHLR Node. All iHLR links to DAPs are inactive for this iHLR Node. One or more iHLR links to DAPs are failed or inactive for this iHLR Node. iHLR Node has become the Active iHLR Node.
N U
<UANC>={UANC for the DAP}, <Inst>={DAP's Logical Id} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR}
N U
U-EImp U-EImp U-DIdl U-DIdl U-E-A
EMPTY
32807
N U
EMPTY
EMPTY
N U
U-EImp U-E-A
EMPTY
EMPTY
N U
EMPTY
EMPTY
N U
U-E-Idl
EMPTY
EMPTY
N U
U-DIdl U-E-Idl
U-E-Idl
EMPTY
EMPTY
N U
U-DIdl
EMPTY
EMPTY
N U
ALL LINKS INACTIVE ONE OR MORE LINKS INACTIVE
U-EImp U-E-Idl
U-E-Idl
EMPTY
EMPTY
N U
<UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR}
U-EImp
EMPTY
EMPTY
N U
CCPiHLR-22
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
7 0 1 7 0 2 7 0 3 7 0 1 7 0 3 7 0 2 8 0 1 8 0 2 8 0 3 8 0 4 8 0 5 6 0 1 6 0 2 6 0 3 6 0 4
REPLICATION IS ACTIVE REPLICATION FAILED REPLICATION DEFERRED REPLICATION IS ACTIVE REPLICATION DEFERRED REPLICATION FAILED
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.207.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.207.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.207.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.207.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.207.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.207.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.208.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.208.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.208.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.208.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.208.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.101.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.101.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.101.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.101.<UANC>.
IHLR_REP LICATION IHLR_REP LICATION IHLR_REP LICATION IHLR_REP LICATION IHLR_REP LICATION IHLR_REP LICATION
U-DIdl U-E-A
U-E-A
EMPTY
EMPTY
Replication is active
S t a t u s N U
<UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR}
U-DIdl U-EImp U-E-A
EMPTY
U-E-A
EMPTY
17410, 17411, 17440 17441
Replication has failed; Manual recovery is required. Replication has been deferred. Replication is active
N U
N U
U-EImp U-DIdl U-EImp
EMPTY
17442
N U
U-EImp U-DIdl
EMPTY
EMPTY
Replication has been deferred. Replication has failed; Manual recovery is required.
N U
EMPTY
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes
NODE IN MAINTAINANCE MODE NODE IN STANDBY MODE NODE IN ACTIVE MODE NODE IN MAINTAINANCE MODE NODE IN STANDBY MODE HW CONTAINER RESTORED FULL FUNCTIONALITY HW CONTAINER LOST FULL FUNCTIONALITY HW CONTAINER LOST PARTIAL FUNCTIONALITY HW CONTAINER LOST FULL FUNCTIONALITY
IHLR_MOD E IHLR_MOD E IHLR_MOD E IHLR_MOD E IHLR_MOD E IHLR_HW_ CONTAINE R IHLR_HW_ CONTAINE R IHLR_HW_ CONTAINE R IHLR_HW_ CONTAINE R
U-E-A
U-DIdl U-EImp U-E-A
EMPTY
17410, 17411, 17440, 17443 EMPTY
N U
Node moves from Active mode to Maintenance mode Node moves from Active mode to Standby mode Node moves from Standby mode to Active mode Node moves from Standby mode to Maintenance mode Node moves from Maintenance mode to Standby mode. HW Container has become operational. Critical HW Container functionality has been lost. HW Container has partially failed. Critical HW Container functionality has been lost.
N U
<UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} <UANC>={UANC for this iHLR} RFC(SR16.0 release): Added related alarms RFC(SR16.0 release): Added related alarms RFC(SR16.0 release): Added related alarms RFC(SR16.0 release): Added related alarms
U-E-A
EMPTY
EMPTY
N U
U-EImp U-EImp U-DIdl U-DIdl U-E-A
EMPTY
EMPTY
N U
U-DIdl U-EImp U-E-A
EMPTY
EMPTY
N U
EMPTY
EMPTY
N U
EMPTY
EMPTY
N M
U-DIdl U-EImp U-DIdl
EMPTY
EMPTY
N M
U-E-A
EMPTY
EMPTY
N M
U-EImp
EMPTY
EMPTY
N M
October 30, 2008
CCPiHLR-23

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes CCPiHLR State Changes
6 0 5 6 2 2 6 0 7 6 0 7 6 0 8 6 0 8 6 0 9 6 0 9 6 1 0 6 1 0 6 1 1 6 1 1 6 1 2 6 1 2
HW CONTAINER RESTORED PARTIAL FUNCTIONALITY HW CONTAINER RESTORED FULL FUNCTIONALITY FRU RESTORED FUNCTIONALITY FRU RESTORED FUNCTIONALITY FRU LOST FUNCTIONALITY FRU LOST FUNCTIONALITY FRU RESTORED PARTIAL FUNCTIONALITY FRU RESTORED PARTIAL FUNCTIONALITY FRU RESTORED FUNCTIONALITY FRU RESTORED FUNCTIONALITY FRU LOST PARTIAL FUNCTIONALITY FRU LOST PARTIAL FUNCTIONALITY FRU LOST FUNCTIONALITY FRU LOST FUNCTIONALITY
1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.101.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.101.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.104.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.105.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.104.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.105.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.104.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.105.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.104.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.105.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.104.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.105.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.104.<UANC>. 1.3.6.1.4.1.161.3.3.10.5.7. 1.1.2.5.1.4.105.<UANC>.
IHLR_HW_ CONTAINE R IHLR_HW_ CONTAINE R IHLR_SCSI
U-DIdl
U-EImp
EMPTY
EMPTY
Operation of HW Container is partially restored.
S t a t u s N M
RFC(SR16.0 release): Added related alarms
U-EImp U-DIdl U-DIdl U-E-A
U-E-A
EMPTY
EMPTY
All HW Container's FRUs are fully operational. FRU has become operational. FRU has become operational. FRU has become nonoperational. FRU has become nonoperational. FRU has become partial operational. FRU has become partial operational. FRU has become operational. FRU has become operational. FRU has become partial operational. FRU has become partial operational. FRU has become nonoperational. FRU has become nonoperational.
N U
EMPTY
1-8
U-E-A
EMPTY
EMPTY
N M
EMPTY
IHLR_NIOC
1-2
U-E-A
EMPTY
EMPTY
N U
EMPTY
IHLR_SCSI
1-8
U-DIdl U-DIdl U-EImp U-EImp U-E-A
EMPTY
EMPTY
N M
EMPTY
IHLR_NIOC
1-2
U-E-A
EMPTY
EMPTY
N U
EMPTY
IHLR_SCSI
1-8
U-DIdl U-DIdl U-EImp U-EImp U-E-A
EMPTY
EMPTY
N N
Applies to ATCA-iHLR Only
IHLR_NIOC
1-2
EMPTY
EMPTY
N U
EMPTY
IHLR_SCSI
1-8
EMPTY
EMPTY
N N
IHLR_NIOC
1-2
U-E-A
EMPTY
EMPTY
N U
EMPTY
IHLR_SCSI
1-8
U-EImp U-EImp U-DIdl U-DIdl
EMPTY
EMPTY
N N
IHLR_NIOC
1-2
U-E-A
EMPTY
EMPTY
N U
EMPTY
IHLR_SCSI
1-8
U-EImp U-EImp
EMPTY
EMPTY
N N
IHLR_NIOC
1-2
EMPTY
EMPTY
N U
EMPTY
CCPiHLR-24
October 30, 2008
Release SR17.0
__________________________________ Events
Event Type
Reason Code
OMC Text
MOI Info (Id)
MOI Info (Label )
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N ) N
availabilityEven t
0, 1, 3, 5, 6, 7, 9, 10, 11 or 13
<universal time><sequence number><secondary id><new mode>-<time of switch>-<reason code>-<old mode><additional text><reason text> <universal time><managed object instance>-<usage state>-<operational state><administrative state>-<boot ROM version>-<software Load version><database version><code version><system description>-<latest reset reason><outage time since latest reset>-<reboot time>-<boot diagnostics> Background Download started
EMPTY
IHLR
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated when the iHLR mode changes.
reStartEvent
EMPTY
1.3.6.1.4.1 .161.3.3.1 0.2.3.1.0
IHLR_ST ATE
EMPTY
EMPTY
EMPTY
EMPTY
This event is used to inform the OMC whenever iHLR switches its application code load or when it reboots. It also tells the OMC that SNMP agent is operational and is ready to handle request.
C Comments & h Notes a n g e S t a t u s U Reason For Change : Added reason code to provide enhanced description for availability trap. Changed the Event Type to availabilityEvent to match OMC event window. U Reason For Change : Changed the Event Type to reStartEvent to match OMC event window.
Action Status
1.3.6.1.4.1 .161.3.3.1 0.2.10.1.1. 0
IHLR
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEv ent
Background Download Aborted
1.3.6.1.4.1 .161.3.3.1 0.2.10.1.1. 0
IHLR
Empty
Empty
Empty
Empty
Event is generated if OLCC background download has completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may
The state change was updated to keep it consistent with the code and other documentation and avoid confusion. M Empty
October 30, 2008
CCPiHLR-25

Event Type
Reason Code
Release SR17.0
Related Alarms
OMC Text
MOI Info (Id)
MOI Info (Label )
Inst
Event Description
O u t a g e ( Y / N )
Comments & Notes
actionStatusEv ent
Background Download Failed
1.3.6.1.4.1 .161.3.3.1 0.2.10.1.1. 0
IHLR
Empty
Empty
Empty
Empty
actionStatusEv ent
Background Download Completed Successfully
1.3.6.1.4.1 .161.3.3.1 0.2.10.1.1. 0
IHLR
Empty
Empty
Empty
Empty
actionStatusEv ent
Background Download Aborted Successfully Background Download Switch started
Action Status
1.3.6.1.4.1 .161.3.3.1 0.2.10.1.2. 0 1.3.6.1.4.1 .161.3.3.1 0.2.11.1.1. 0
IHLR
Empty
Empty
Empty
Empty
contain addition details. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download abort (bgdlAbort) is successful. Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure (reason and line number in configuration file). Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download
M Empty
M Empty
M Empty
IHLR
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEv ent
Background Download Switch Aborted
1.3.6.1.4.1 .161.3.3.1 0.2.11.1.1. 0 1.3.6.1.4.1 .161.3.3.1 0.2.11.1.1. 0 1.3.6.1.4.1 .161.3.3.1 0.2.11.1.1. 0 1.3.6.1.4.1 .161.3.3.1 0.2.12.2.1. 0
IHLR
Empty
Empty
Empty
Empty
M Empty
actionStatusEv ent
Background Download Switch Failed
IHLR
Empty
Empty
Empty
Empty
M Empty
actionStatusEv ent
Background Download Switch Completed Successfully Upgrade Aborted
IHLR
Empty
Empty
Empty
Empty
M Empty
actionStatusEv ent
iHLR
Empty
Empty
Empty
Empty
N Applies to ATCAiHLR Only
actionStatusEv ent
Upgrade Failed
1.3.6.1.4.1 .161.3.3.1
iHLR
Empty
Empty
Empty
Empty
CCPiHLR-26
October 30, 2008
Release SR17.0
Event Type
Reason Code

MOI Info (Label ) Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
0.2.12.2.1. 0
actionStatusEv ent
1.3.6.1.4.1 .161.3.3.1 0.2.12.2.1. 0
iHLR
Empty
Empty
Empty
Empty
Action Status
1,2 or 3
Background Download aborted Incorrect action status
1.3.6.1.4.1 .161.3.3.1 0.2.10.1.2. 0
iHLR
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if OLCC background download has been aborted.
actionStatusEv ent
0x90
1.3.6.1.4.1 .161.3.3.1 0.2.13.1.1. 0
IHLR
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
A LMT or UNIX user has logged in. See the Action Status Information for details
actionStatusEv ent
0x91
1.3.6.1.4.1 .161.3.3.1 0.2.13.1.1. 0
IHLR
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEv ent
0x92
Session timed-out
1.3.6.1.4.1 .161.3.3.1 0.2.13.1.1. 0
IHLR
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEv ent
0x94
1.3.6.1.4.1 .161.3.3.1 0.2.13.1.1. 0
IHLR
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
The state change was updated to keep it consistent with the code and other documentation and avoid confusion. action status information includes the following information: reason code <user login name> <access level> login. action status information includes the following information: reason code <user login name> <access level> logout. action status information includes the following information: reason code <user login name> <access level> login session timedout. action status information includes the following information: reason code <user login name> <access level> login session manually terminated.
October 30, 2008
CCPiHLR-27
Release SR17.0
CCPiHLR-28
October 30, 2008
Release SR17.0
__________________________________ Alarms
Alarm Type
Alarm Code
iCP
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t & C l e a r R C R
O u t a g e Y / N
Comments & Notes
equipmentF ailureEvent processingF ailureEvent processingF ailureEvent
201
Version Mismatch Unknown EBTS Reported by iVPU Critical Application Failed
202
204
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM ICP_APP _ALM ICP_APP _ALM
communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent
214
Last Link Failed
214
Last Link Failed
214
Last Link Failed
217
Link Disconnected
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM ICP_APP _ALM ICP_APP _ALM ICP_APP _ALM
XBL Id ## Version Incompatible Unknown AFR Mobis RSL ## from iVPU ## Critical Application Functionality Lost: <Func Area> MTL : ##
Critical
EMPTY
EMPTY
Check iCP to iVPU connection Check Configuration Self Correcting.
N U
iCP and iVPU have differing software versions iCP and iVPU have differing databases Software Failure which is self-correcting after the iCP node (automatically) takes a reset. Sent when the last inservice MTL has been rendered out-of-service. Sent when the last inservice XBL has been rendered out-of-service. Sent when the last inservice RSL has been rendered out-of-service. Sent when a MOBIS or SNMP RSL link is rendered in-service or outof-service.
Critical
EMPTY
EMPTY
N U
Critical
225
202, 301
N U
Critical
217
502
Check Connected Network Elements Check Connected Network Elements Check Connected Network Elements Check Connected Network Elements
R C R C R C R C
N U
XBL : ##
Critical
217
502
N U
communicat ionFailureE vent communicat ionFailureE vent communicat
217
Link Disconnected
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3.
ICP_APP _ALM
< MOBIS / SNMP > RSL : ## < MOBIS / SNMP / AFRMOBIS > RSL ## < Disconnected / Connected > MTL ## < Disconnected / Connected > XBL ## < Disconnected / Connected > Unequipped CIC
Critical
217
502
N U
Critical
214
EMPTY
N U
Critical
214
EMPTY
Check Connected Network Elements
R C
N U
217
Link Disconnected
ICP_APP _ALM
Critical
214
EMPTY
R C
N U
217
Link
ICP_APP
Critical
EMPTY
EMPTY
Verify CICs
N U
Sent when a MOBIS or SNMP RSL link is rendered in-service or outof-service. Sent when a MOBIS or SNMP RSL link is rendered in-service or outof-service. iCP received unequipped
October 30, 2008
iCP-1

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent
Disconnected 217 Link Disconnected
10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
_ALM ICP_APP _ALM 1
217
Link Disconnected
ICP_APP _ALM
from MSC, #, #, #, Exceed the Max downloads allowed for RSL <id> Exceed the Max uploads allowed for RSL <id> < SNMP / DOWNLOAD / UPLOAD > Communication Lost for RSL # MTL ##, Signaling Link Out of Serv ice MTL ##, Remote Processor Outage MTL ##, Remote User Part Unavailable RSL ##, Link Timeout (Info ##)
Critical
EMPTY
EMPTY
Critical
EMPTY
EMPTY
217
Link Disconnected
ICP_APP _ALM
Critical
EMPTY
EMPTY
equipped on iBSC and MSC match Don't run more then 45 EBTS downloads simultaneously. Don't run too many EBTS uploads simultaneously. Check OMC to iCP connection
circuit message from MSC. R N U Too many simultaneous EBTS downloads were requested Too many simultaneous EBTS uploads were requested iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network
N U
N U
communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent
217
Link Disconnected
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
Critical
EMPTY
EMPTY
N U
217
Link Disconnected
ICP_APP _ALM
Critical
EMPTY
EMPTY
N U
217
Link Disconnected
ICP_APP _ALM
Critical
EMPTY
EMPTY
N U
217
Link Disconnected
ICP_APP _ALM
Critical
EMPTY
EMPTY
N U
217
Link Disconnected
ICP_APP _ALM
RSL ##, Sequence Error (Info ##) RSL ##, Frame Reject (Info ##)
Critical
EMPTY
EMPTY
N U
217
Link Disconnected
ICP_APP _ALM
Critical
EMPTY
EMPTY
N U
217
Link Disconnected
ICP_APP _ALM
217
Link Disconnected
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
RSL ##, Unexpected Response (S / DM / UA) (Info ##) RSL ##, Bad Configuration (Info ##)
Critical
EMPTY
EMPTY
N U
Critical
EMPTY
EMPTY
N U
iCP-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent qualityOfSer viceFailureE vent
217
Link Disconnected
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
RSL ##, Unexpected SABME (Info ##) RSL ##, Bad Frame (I field / wrong size) (Info ##) RSL ##, Link Disconnected Failed (Info ##) Throttling traffic: < "MTL" > #, #, #, #,
Critical
EMPTY
EMPTY
N U
217
Link Disconnected
ICP_APP _ALM
Critical
EMPTY
EMPTY
N U
217
Link Disconnected
ICP_APP _ALM
Critical
EMPTY
EMPTY
N U
223
ICP_APP _ALM
Critical
231
101
223
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
< Local / Remote > Congestion, MTL ##
Critical
231
101
231
Processing Load Notification
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
Processing Load < High / Normal / Warning > Current CPU utilization = ## Processing Load < High / Normal >, RSL #, #, #
Critical
223
101, 102
231
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
Critical
223
101, 102
231
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
Processing Load < High / Normal >, MTL #, #, #
Critical
223
101, 102
238
MSC Overload Alarm
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
Throttling LUs, Calls, IMSI Detaches, Hos
Critical
231, 223
EMPTY
May need to reengineer for proper capacity increase (see Planning guidelines) May need to reengineer for proper capacity increase (see Planning guidelines) May need to reengineer for proper capacity increase (see Planning guidelines) May need to reengineer for proper capacity increase (see Planning guidelines) May need to reengineer for proper capacity increase (see Planning guidelines) May need to reengineer for proper capacity increase (see
R C
N U
R C
N U
R C
N U
R C
N U
issues iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network issues iCP may not be able to communicate with the OMC due to network issues Each MTL Link that traffic is being throttled on, is listed. Additional such alarms are sent if not all affected links fit within one "Alarm Code Text" string. Each MTL Link that traffic is being throttled on, is listed. Additional such alarms are sent if not all affected links fit within one "Alarm Code Text" string. Triggered when CPU utilization on the iCP node is running high. RFC(SR16.0 release): Added warning in the alarm code text CPU utilization on the RSL I/O Blades running high, causing RSL links to be congested
R C
N U
CPU utilization on the MTL I/O Blades running high, causing MTL links to be congested
R C
N U
MSC Overload detected by BSC Call Processing Application
October 30, 2008
iCP-3

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
301
Ethernet Link Down
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
16
E-Net <Link ID> Is Down
Critical
214
EMPTY
Planning guidelines) Check Connected Network Elements
R C
N M
301
Ethernet Link Down
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
16
E-Net id=<value>, name=<text_des c> is <Enabled or Impaired or Disabled>
Critical
214
EMPTY
302
Power Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 13.1.1.1.<INSTAN CE>
ICP_PO WER_AL M
12
Power DeviceType <DeviceTypeID> Device Id <DeviceID> <Disabled or Enabled>
Critical
EMPTY
1004
Check for the following in the chassis: 1) Both switch blades (SSC) should be installed in the chassis 2) Two Ethernet ports on the RTM should be connected to I/O chassis. If the chassis and the blade are configured as per the configuration given above and if this alarm is still seen, contact iDEN Customer Network Resolution Center for assistance. Contact CNRC
R C
N M
Ethernet Link is down. <Link ID>= {1-6}. This alarm is used to detect the Ethernet link connection failure. RFC(SR15.0 release): Changed for Greater Than 192 Sites(SR1256). RFC(SR16.0 release): reformatted the alarm code text; changed instance. Applies to SCP-iCP only Ethernet Link is enabled or impaired or disabled. This alarm is used to detect the Ethernet link connection failure. Applies to ATCAiCP only.
R C
N M
303
Fan Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2
ICP_FAN _ALM
15
Fan DeviceType <DeviceTypeId>
Critical
EMPTY
1004
Replace the fan.
R C
N M
The iCP has lost one of its power supplies. For power disable alarm on I/O chassis, check the slot id, slot id={32-36}. RFC(SR16.0 release): change to provide correct information. Applies to SCP-iCP only A hardware failure has occurred. RFC(SR15.0
iCP-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
12.1.1.1.<INSTAN CE>
Device Id <DeviceID> <Disabled or Enabled>
305
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 17.1.1.1.<INSTAN CE>
ICP_SC SI_ALM
12
SCSI DeviceType <DeviceTypeId> Device Id <DeviceID> <Disabled or Enabled>
Critical
EMPTY
607-608
Contact CNRC
R C
N M
305
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 17.1.1.1.<INSTAN CE>
ICP_SC SI_ALM
12
306
NIOC Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 20.1.1.1.<INSTAN CE>
ICP_NIO C_ALM
12
HARD_DISK DeviceType <DeviceTypeId> Device Id <DeviceID> <Disabled or Impaired or Enabled> NIOC DeviceType <DeviceTypeId> Device Id <DeviceID> <Disabled or Enabled>
Critical
EMPTY
607-612
Contact CNRC
R C
N M
release): Changed for Greater Than 192 Sites(SR1256). RFC(SR16.0 release): reformatted the alarm code text; changed instance; modified comments. Applies to SCP-iCP only A hardware failure has occurred. RFC(SR15.0 release): Changed for Greater Than 192 Sites (SR1256). RFC(SR16.0 release): reformatted the alarm code text; Added related state change. SCP-iCP instance range is 1..2 A hardware failure has occurred. Applies to ATCAiCP, where the instance is 1
Critical
EMPTY
608,607,6 12,609
Contact CNRC
R C
N M
309
TOY_CLOCK device disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 25.1.1.1.<Instance >
ICP_TO Y_CLOC K_ALM
TOY_CLOCK DeviceType<ID> DeviceId<Num> <Disabled or Enabled>
Critical
EMPTY
EMPTY
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or
R C
N M
A hardware failure has occurred. This alarm is used to detect the Ethernet card failure. RFC(SR15.0 release): Changed for Greater Than 192 Sites(SR1256). RFC(SR16.0 release): Change instance (SR1262); Added related state change. Applies to SCP-iCP only A hardware failure has occurred. RFC(SR15.0 release): Changed for Greater Than 192 Sites (SR1256). RFC(SR16.0 release): reformatted the alarm code text. Applies to SCP-iCP only
October 30, 2008
iCP-5

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
310
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 24.1.1.1.<Instance >
ICP_DE V_TEMP _ALM
17
DEV_TEMP DeviceType <ID> DeviceId <Num> <Disabled or Enabled>
Critical
EMPTY
EMPTY
312
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
312
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
qualityOfSer viceFailureE vent equipmentF ailureEvent
312
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 14.1.1.<SLOT>.<IN STANCE>
ICP_APP _ALM
316
IO Port Down
ICP_IOB LADE_A LM
18
<File system name> File System Set Excessive at <%> utilization <File system name> File System <Set or Clear> Excessive at <%> utilization <File system name> File System Clear Excessive Set/Clear <Blue /Red/Yellow> Alarm IO_SPAN<num> on Board <id> or Set/Clear IO_SPAN <num> on Board <id> Down Alarm or IO_SPAN <num> Down/Up due to Locking/Unlockin g the Board <id> or IO_SPAN <num> Down/Up due to Locking/Unlockin
Critical
305
EMPTY
system unit. Try to maintain the temperature in the operating range. If the problem persists even after the temperature is brought to a safe range, contact the iDEN Customer Center for assistance. Contact CNRC
R C
N M
A hardware failure has occurred. RFC(SR15.0 release): Changed for Greater Than 192 Sites(SR1256). RFC(SR16.0 release): reformatted the alarm code text. SCP-iCP instance range is 1..1. ATCA-iCP instance range is 1..7
R C
N M
The reported file system is almost full. Applies to SCPiCP only
Critical
305
EMPTY
Contact CNRC
R C
N M
The reported file system is almost full. Applies to ATCA-iCP only
Critical
305
EMPTY
R C
N M
The reported file system is almost full. Applies to ATCA-iCP only A hardware failure has occurred.
Critical
214
EMPTY
Lock/unlock SPAN. If recurring, check span cable and connectivity. If recurring, then lock/unlock IO_BLADE. If recurring then replace IO_BLADE
R C
N U
iCP-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
317
IO Board Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
g the Span on Board <id> IO board ## failed.
Critical
EMPTY
EMPTY
318
AMC Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 29.1.1.1.<Instance >*
ICP_AM C_ALM
12
AMC DeviceType <DeviceTypeId> DeviceId <DeviceId> at Slot <Slot ID> <Disabled or Enabled>
Critical
EMPTY
EMPTY
319
IP Switch Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 30.1.1.1.<Instance >*
ICP_IP_ SWITCH _ALM
12
IP Switch DeviceType <DeviceTypeId> DeviceId <DeviceId> at Slot <Slot ID> <Disabled or Enabled>
Critical
EMPTY
EMPTY
320
IO_FAN Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 31.1.1.1.<Instance >*
ICP_IO_ FAN_AL M
13
IO_FAN DeviceType <DeviceTypeId> DeviceId <DeviceId> at Slot <SlotID> <Disabled or Enabled>
Critical
EMPTY
EMPTY
321
IO_POWER disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2
ICP_IO_ POWER
15
IO_POWER DeviceType
Critical
EMPTY
EMPTY
For Pay load cards, Lock/unlock IO_BLADE. If recurring, replace IO_BLADE. For switch cards Replace Switch cards. Contact CNRC if any IO miscellaneous device hardware failure. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed
R C
N D
An I/O Blade was brought down. This can occur during normal locks/unlocks when it is no cause for concern
R C
N M
A hardware failure has occurred. RFC(SR15.0 release): Changed for Greater Than 192 Sites (SR1256). RFC(SR16.0 release)SR16.0 change: reformatted the alarm code text
R C
N M
A hardware failure has occurred. RFC(SR15.0 release): Changed for Greater Than 192 Sites (SR1256). RFC(SR16.0 release): reformatted the alarm code text
R C
N M
A hardware failure has occurred. RFC(SR15.0 release): Changed for Greater Than 192 Sites (SR1256). RFC(SR16.0 release): reformatted the alarm code text
R C
N M
A hardware failure has occurred. RFC(SR15.0
October 30, 2008
iCP-7

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
32.1.1.1.<Instance >*
_ALM
<DeviceTypeId> DeviceId <DeviceId> at Slot <SlotID> <Disabled or Enabled>
322
IO_PAYLOAD disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 33.1.1.1.<Instance >*
ICP_IO_ PAYLOA D_ALM
16
IO_PAYLOAD DeviceType <DeviceTypeId> DeviceId <DeviceId> at Slot <SlotID> <Disabled or Impaired or Enabled> DISK VOLUME DeviceType<Dev iceTypeId> Device Id <DeviceID> <Disabled or Enabled>
Critical
EMPTY
608,607,6 12,609
323
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 11.1.1.1.<Instance >
ICP_CP U_ALM
19 9
Critical
EMPTY
EMPTY
hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Contact the iDEN Customer Network Resolution Center for assistance
release): Changed for Greater Than 192 Sites (SR1256)
R C
N M
A hardware failure has occurred. RFC(SR15.0 release): Changed for Greater Than 192 Sites (SR1256). RFC(SR16.0 release): added related state change
R C
N M
324
Memory Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 11.1.1.1.<Instance >
ICP_CP U_ALM
MEMORY DeviceType<Dev iceTypeId> Device Id <DeviceID> <Enabled or Impaired or Disabled>
Critical
EMPTY
EMPTY
R C
N M
A hardware failure has occurred. 99 is the maximum value of instance. The real instance of VOLUME is decided during run-time, which is around 20. RFC(SR16.0 release): new alarm derived from ICP_SCSI_ALM (alarm code 305) for a specific situation(BCCB 2089) A hardware failure has occurred. An alarm indicating enabled state of HW Device Memory is sent when memory is available, which is CLEAR alarm for HW DEVICE MEMORY. An alarm indicating impaired state of HW Device Memory is sent when total Memory decreased from last reboot or % mem used over alarm threshold (default = 85%), which is SET alarm for HW DEVICE MEMORY. An alarm indicating disabled
iCP-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
326
SYSTEM BUS Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 11.1.1.1.<Instance >
ICP_CP U_ALM
12
SYSTEM_BUS DeviceType<Dev iceTypeId> Device Id <DeviceID> <Disabled or Enabled>
Critical
EMPTY
EMPTY
326
SYSTEM BUS Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 11.1.1.1.<Instance >
ICP_CP U_ALM
12
327
IPMI BUS Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 11.1.1.1.<Instance >
ICP_CP U_ALM
SYSTEM_BUS DeviceType<Dev iceTypeId> Device Id <DeviceID> <Disabled or Impaired or Enabled> IPMI Bus on I/O Chassis All devices on IPMI Bus operational OR IPMI Bus on I/O Chassis One or More devices on IPMI Bus Not
Critical
EMPTY
EMPTY
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Contact Customer Network Resolution Center if needed. Contact the iDEN Customer Network Resolution Center for assistance
R C
N M
state of HW Device Memory is sent when % mem used over recovery threshold (default = 90%) or total memory less than minimum required by config, which is SET alarm for HW DEVICE MEMORY also. In some scenarios, there can be one CLEAR alarm for more than one corresponding SET alarms. RFC(SR16.0 release): new alarm derived from ICP_SCSI_ALM (alarm code 305) for a specific situation(BCCB 2089). A hardware failure has occurred. RFC(SR16.0 release): new alarm is added because a failure can be detected now due to HP vendor software enhancement. SCP-iCP instance range is 1..2
R C
N M
Critical
EMPTY
EMPTY
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the
R C
N U
A hardware failure has occurred. RFC(SR16.0 release): new alarm is added because a failure can be detected now due to HP vendor software enhancement. ATCA-iCP instance range is 1 A hardware failure has occurred. RFC(SR16.0 release): new alarm derived from ICP_IO_PAYLOAD_ALM (alarm code 322) for a specific situation(BCCB 2089).
October 30, 2008
iCP-9

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
328
BITS CLOCK Disabled
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 11.1.1.1.<Instance >
ICP_CP U_ALM
operational OR IPMI Bus on I/O Chassis All devices on IPMI Bus Not operational. Primary BITS clocking for the IO Chassis | Secondary BITS clocking for the IO Chassis | Internal BITS clocking for the IO Chassis
Critical
EMPTY
EMPTY
330
Timezone Failure
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
Major
EMPTY
EMPTY
hardware or system unit. Contact Customer Network Resolution Center if needed. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Contact Customer Network Resolution Center if needed. Contact Customer Network Resolution Center for assistance. Contact Customer Network Resolution Center for assistance. Contact Customer Network Resolution Center for assistance. Check if latch is closed for the front blade and the rear transition blade. If problem persists contact iDEN Customer Network Resolution Center for assistance Contact Customer Network Resolution Center
R C
N U
A hardware failure has occurred. RFC(SR16.0 release): new alarm derived from ICP_TOY_CLOCK_ALM (alarm code 309) for a specific situation(BCCB 2089).
R C
N N
331
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 11.1.1.1.<Instance > 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 11.1.1.1.<Instance > 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.2.3.1.6.2 11.1.1.1.<Instance >
ICP_CP U_ALM
11 7
Voltage Device <id> Outside Operating Range
Critical
EMPTY
EMPTY
R C
N N
332
ICP_CP U_ALM
12
IPMI Controller <id> <Disabled or Enabled> Latch Open <id>
Critical
EMPTY
EMPTY
R C
N N
333
Latch Open
ICP_CP U_ALM
12
Critical
EMPTY
EMPTY
R C
N N
Timezone is set based on configuration downloaded from OMC-R. RFC(SR17.0 Melody): newly added. Applies to ATCA-iCP only Voltage Level Outside of given threshold range. RFC(SR17.0 Melody): newly added. Applies to ATCA-iCP only IPMI controller is not operational. RFC(SR17.0 Melody): newly added. Applies to ATCA-iCP only Close the latch to clear the condition. RFC(SR17.0 Melody): newly added. Applies to ATCA-iCP only
334
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
Critical
EMPTY
EMPTY
R C
N N
This alarm is not supported and will be removed from this document in a future
iCP-10
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
335
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
Critical
EMPTY
EMPTY
for assistance. Contact the iDEN Customer Situation Center for assistance.
N N
release. Update Loads on OMC to versions that not support the hardware version installed. RFC(SR17.0 Melody): newly added. Applies to ATCA-iCP only RFC(BCCB 1690): newly added.
100024
Bad Value in Configuration File Time Synchronization Cannot Be Done
1.3.6.1.4.1.161.3.3. 10.2.14.1.1.0
CA_BAD VAL_AL M CA_SNT P_ALM
Bad Value for OID:<object_id>
Major
EMPTY
EMPTY
100025
1.3.6.1.4.1.161.3.3. 10.2.6.1.0
Time Difference between NMS and NE exceeds maximum difference for synchronization
Major
EMPTY
EMPTY
Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance
N N
N U
337
Blade Initialization Failure Software Upgrade Failure
1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE> 1.3.6.1.4.1.161.3.3. 10.5.7.1.1.1.2.<INS TANCE>
ICP_APP _ALM
Critical
EMPTY
EMPTY
340
ICP_APP _ALM
<reason>
Critical
EMPTY
EMPTY
Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance.
R C
Y N
R C
Y N
The time difference between the NMS and the NE was larger than the maximum value for automatic synchronization to be completed. RFC(SR16.0 release): Changed alarm code for SR1381,1383 This alarm is not supported and will be removed from this document in a future release. Software Upgrade Failure. Where: <reason> displays different reasons for different failure scenarios. Applies to ATCA-iCP Only.
October 30, 2008
iCP-11
Release SR17.0
__________________________________ State Changes

State Changes
Reas on Code (Label)
OMC Text
MOI Info (Id)
MOI Info
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C Comments h & Notes a n g e S t a t u s U EMPTY
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
101
101
102
PROCESSING LOAD TOO HIGH PROCESSING LOAD TOO HIGH PROCESSING LOAD NORMAL PROCESSING LOAD NORMAL APPLICATION STARTED APPLICATION STARTED APPLICATION STARTED APPLICATION STARTED APPLICATION STARTED APPLICATION STARTED APPLICATION STARTED APPLICATION STARTED APPLICATION
102
201
201
201
201
201
201
201
201
201
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.408.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.407.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.408.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.407.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.401.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.401.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.401.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.402.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.402.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.402.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.403.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.403.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1
iCP_LOAD_SHE DDING iVPU_LOAD_SH EDDING iCP_LOAD_SHE DDING iVPU_LOAD_SH EDDING iCP_APP_AGT
U-E-A
U-D-Idl
EMPTY
223, 231
The iCP processing load has exceeded normal level . The iVPU processing load has exceeded normal level . The iCP processing load has returned to its normal level. The iVPU processing load has returned to its normal level. All functional area processes are operational. All functional area processes are coming up. All functional area processes are coming up. All functional area processes are operational. All functional area processes are coming up. All functional area processes are coming up. All functional area processes are operational. All functional area processes are coming up. All functional area processes
U-E-A
U-D-Idl
EMPTY
EMPTY
U EMPTY
U-DIdl U-DIdl U-DIdl U-DIdl U-EImp U-DIdl U-DIdl U-EImp U-DIdl U-DIdl U-E-
U-E-A
EMPTY
231
U EMPTY
U-E-A
EMPTY
EMPTY
U EMPTY
U-E-A
EMPTY
EMPTY
U EMPTY
iCP_APP_AGT
U-E-Imp
EMPTY
EMPTY
U EMPTY
iCP_APP_AGT
U-E-A
EMPTY
EMPTY
U EMPTY
iCP_APP_CP
U-E-A
EMPTY
EMPTY
U EMPTY
iCP_APP_CP
U-E-Imp
EMPTY
EMPTY
U EMPTY
iCP_APP_CP
U-E-A
EMPTY
EMPTY
U EMPTY
iCP_APP_FM
U-E-A
EMPTY
EMPTY
U EMPTY
iCP_APP_FM
U-E-Imp
EMPTY
EMPTY
U EMPTY
iCP_APP_FM
U-E-A
EMPTY
EMPTY
U EMPTY
iCP-12
October 30, 2008
Release SR17.0
State Changes

MOI Info Inst From State To State Related State Changes Related Alarms
Event Description
O u t a g e ( Y / N )
C Comments h & Notes a n g e S t a t u s
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent 201
STARTED APPLICATION STARTED APPLICATION STARTED APPLICATION STARTED APPLICATION STARTED CRITICAL APPLICATION FUNCTIONALIT Y LOST CRITICAL APPLICATION FUNCTIONALIT Y LOST CRITICAL APPLICATION FUNCTIONALIT Y LOST CRITICAL APPLICATION FUNCTIONALIT Y LOST CRITICAL APPLICATION FUNCTIONALIT Y LOST CRITICAL APPLICATION FUNCTIONALIT Y LOST CRITICAL APPLICATION FUNCTIONALIT Y LOST CRITICAL APPLICATION FUNCTIONALIT Y LOST ALL
201
201
201
301
.2.5.1.4.403.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.404.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.404.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.404.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.405.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.401.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.401.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.402.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.403.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.404.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.405.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.405.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.405.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1
Imp iCP_APP_OAM 1 U-DIdl U-DIdl U-EImp U-DIdl U-E-A U-E-A EMPTY EMPTY
are coming up. All functional area processes are operational. All functional area processes are coming up. All functional area processes are coming up. Some functional areas are operational. One or more critical functional area process is down. One or more critical functional area process is down. One or more critical functional area process is down. One or more critical functional area process is down. One or more critical functional area process is down. One or more functional areas have been disabled N U EMPTY
iCP_APP_OAM
U-E-Imp
EMPTY
EMPTY
U EMPTY
iCP_APP_OAM
U-E-A
EMPTY
EMPTY
U EMPTY
iCP_APP_ROLL UP iCP_APP_AGT
U-E-Imp
201, 1001 EMPTY
EMPTY
U EMPTY
U-D-Idl
EMPTY
U EMPTY
301
iCP_APP_AGT
U-E-A
U-E-Imp
EMPTY
EMPTY
U EMPTY
301
iCP_APP_CP
U-E-A
U-D-Idl
EMPTY
EMPTY
U EMPTY
301
iCP_APP_FM
U-E-A
U-D-Idl
EMPTY
EMPTY
U EMPTY
301
iCP_APP_OAM
U-E-A
U-D-Idl
EMPTY
EMPTY
U EMPTY
301
iCP_APP_ROLL UP
U-E-A
U-D-Idl
202
204
U EMPTY
301
iCP_APP_ROLL UP
U-E-A
U-E-Imp
202
204
One or more functional areas have been impaired
U EMPTY
301
iCP_APP_ROLL UP
U-EImp
U-D-Idl
202
204
One or more functional areas have been disabled
U EMPTY
esmrStateCh
302
iCP_APP_ROLL
U-D-
U-E-A
201,
EMPTY
All functional areas are fully
U EMPTY
October 30, 2008
iCP-13

State Changes
Release SR17.0
Inst From State To State Related State Changes Related Alarms
OMC Text
MOI Info (Id)
MOI Info
Event Description
O u t a g e ( Y / N )
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent 302
401
APPLICATIONS FUNCTIONAL ALL APPLICATIONS FUNCTIONAL LOGICAL LINK UP LOGICAL LINK UP LOGICAL LINK UP LOGICAL LINK UP LOGICAL LINK DOWN LOGICAL LINK DOWN LOGICAL LINK DOWN LOGICAL LINK DOWN LOGICAL LINK DOWN LOGICAL LINK DOWN LOGICAL LINK DOWN ONE OR MORE LINKS LOST ONE OR MORE LINKS LOST ONE OR MORE LINKS LOST
401
401
401
402
402
402
402
402
402
402
501
501
501
.2.5.1.4.405.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.405.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.410.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.414.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.415.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.418.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.410.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.410.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.414.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.414.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.415.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.415.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.418.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.420.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.411.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.421.<UANC>.<INST
UP iCP_APP_ROLL UP iCP_MTL 1
Idl U-EImp U-DIdl U-DIdl U-DIdl U-DIdl U-E-A U-E-A
1001 201, 1001 EMPTY EMPTY
operational. All functional areas are fully operational. SS7 Link connectivity established. LAPD link established N U EMPTY
1-16
U-E-A
EMPTY
U EMPTY
iCP_RSL_MOBI S iCP_RSL_SNMP
110000 110000 1 - 336
U-E-A
EMPTY
EMPTY
U EMPTY
U-E-A
EMPTY
EMPTY
LAPD link established
U EMPTY
iCP_XBL
U-E-A
503 504
EMPTY
XBL connectivity established.
U EMPTY
iCP_MTL
1-16
U-D-Idl
EMPTY
217
SS7 link lost connectivity.
U EMPTY
iCP_MTL
1-16
I-I-I
U-D-Idl
EMPTY
217
SS7 link lost connectivity.
U EMPTY
iCP_RSL_MOBI S iCP_RSL_MOBI S iCP_RSL_SNMP
110000 110000 110000 110000 1 - 336
U-E-A
U-D-Idl
EMPTY
217
LAPD link is disconnected or OOS LAPD link is disconnected or OOS LAPD link is disconnected or OOS LAPD link is disconnected or OOS XBL lost connectivity.
U EMPTY
I-I-I
U-D-Idl
EMPTY
217
U EMPTY
U-E-A
U-D-Idl
EMPTY
217
U EMPTY
iCP_RSL_SNMP
I-I-I
U-D-Idl
EMPTY
217
U EMPTY
iCP_XBL
U-E-A
U-D-Idl
EMPTY
217
U EMPTY
iCP_LINK_ROLL UP iCP_MTL_ROLL UP iCP_RSL_ROLL UP
U-E-A
U-E-Imp
402, 1002 402, 1002 402, 1002
EMPTY
One or more Links are not fully operational One or more MTLs are not fully operational One or more RSLs are not fully operational
U EMPTY
U-E-A
U-E-Imp
EMPTY
U EMPTY
U-E-A
U-E-Imp
EMPTY
U EMPTY
iCP-14
October 30, 2008
Release SR17.0
State Changes

Event Description
O u t a g e ( Y / N )
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
501
ONE OR MORE LINKS LOST ALL LINKS FAILED ALL LINKS FAILED ALL LINKS FAILED ALL LINKS FAILED ALL LINKS FAILED ALL LINKS FAILED ALL LINKS FAILED ALL LINKS FAILED ALL LINKS OPERATIONAL ALL LINKS OPERATIONAL ALL LINKS OPERATIONAL ALL LINKS OPERATIONAL ALL LINKS OPERATIONAL ALL LINKS OPERATIONAL
502
502
502
502
502
502
502
502
503
503
503
503
503
503
ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.419.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.420.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.420.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.411.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.411.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.421.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.421.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.419.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.419.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.420.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.420.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.411.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.411.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.421.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.421.<UANC>.<INST ANCE>
iCP_XBL_ROLL UP iCP_LINK_ROLL UP iCP_LINK_ROLL UP iCP_MTL_ROLL UP iCP_MTL_ROLL UP iCP_RSL_ROLL UP iCP_RSL_ROLL UP iCP_XBL_ROLL UP iCP_XBL_ROLL UP iCP_LINK_ROLL UP iCP_LINK_ROLL UP iCP_MTL_ROLL UP iCP_MTL_ROLL UP iCP_RSL_ROLL UP iCP_RSL_ROLL UP
U-E-A
U-E-Imp
402, 1002 402, 1002 402, 1002 402, 1002 402, 1002 402, 1002 402, 1002 402, 1002 402, 1002 401
EMPTY
One or more XBLs are not fully operational All Links have failed.
U-E-A
U-D-Idl
214
U EMPTY
U-EImp U-E-A
U-D-Idl
214
All Links have failed.
U EMPTY
U-D-Idl
214
All MTLs have failed.
U EMPTY
U-EImp U-E-A
U-D-Idl
214
All MTLs have failed.
U EMPTY
U-D-Idl
214
All RSLs have failed.
U EMPTY
U-EImp U-E-A
U-D-Idl
214
All RSLs have failed.
U EMPTY
U-D-Idl
214
All XBLs have failed.
U EMPTY
U-EImp U-EImp U-DIdl U-EImp U-DIdl U-EImp U-DIdl
U-D-Idl
214
All XBLs have failed.
U EMPTY
U-E-A
EMPTY
All Links are fully operational
U EMPTY
U-E-A
401
EMPTY
All Links are fully operational
U EMPTY
U-E-A
401
EMPTY
All MTLs are fully operational
U EMPTY
U-E-A
401
EMPTY
All MTLs are fully operational
U EMPTY
U-E-A
401
EMPTY
All RSLs are fully operational
U EMPTY
U-E-A
401
EMPTY
All RSLs are fully operational
U EMPTY
October 30, 2008
iCP-15

State Changes
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info
Event Description
O u t a g e ( Y / N )
503
ALL LINKS OPERATIONAL ALL LINKS OPERATIONAL ONE OR MORE LINKS RESTORED ONE OR MORE LINKS RESTORED ONE OR MORE LINKS RESTORED ONE OR MORE LINKS RESTORED HW CONTAINER RESTORED FULL FUNCTIONALIT Y HW CONTAINER RESTORED FULL FUNCTIONALIT Y HW CONTAINER LOST FULL FUNCTIONALIT Y HW CONTAINER LOST FULL FUNCTIONALIT Y HW CONTAINER LOST FULL FUNCTIONALIT Y HW
503
504
504
504
504
601
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.419.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.419.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.420.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.411.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.421.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.419.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_XBL_ROLL UP iCP_XBL_ROLL UP iCP_LINK_ROLL UP iCP_MTL_ROLL UP iCP_RSL_ROLL UP iCP_XBL_ROLL UP iCP_HW_CONT AINER
U-EImp U-DIdl U-DIdl U-DIdl U-DIdl U-DIdl U-DIdl
U-E-A
401
EMPTY
All XBLs are fully operational
U-E-A
401
EMPTY
All XBLs are fully operational
U EMPTY
U-E-Imp
401
EMPTY
One or more Links are not fully operational. One or more MTLs are not fully operational. One or more RSLs are not fully operational. One or more XBLs are not fully operational. HW Container has become operational.
U EMPTY
U-E-Imp
401
EMPTY
U EMPTY
U-E-Imp
401
EMPTY
U EMPTY
U-E-Imp
401
EMPTY
U EMPTY
U-E-A
EMPTY
302306,309,31 0,318322,324,32 7 EMPTY
601
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_HW_CONT AINER
I-I-I
U-E-A
EMPTY
HW Container has become operational.
U RFC(SR1 6.0 release): Added related alarms M Currently this trap is not supported
602
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_HW_CONT AINER
U-E-A
U-D-Idl
EMPTY
302306,309,31 0,318322,324,32 7 EMPTY
Critical HW Container functionality has been lost.
602
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_HW_CONT AINER
U-DIdl
I-I-I
EMPTY
U RFC(SR1 6.0 release): Added related alarms M Currently this trap is not supported M Currently this trap is not supported U RFC(SR1
602
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_HW_CONT AINER
I-I-I
U-D-Idl
EMPTY
EMPTY
esmrStateCh
603
1.3.6.1.4.1.161.3.3.10.5.7.1.1
iCP_HW_CONT
U-E-A
U-E-Imp
EMPTY
302-
HW Container has partially
iCP-16
October 30, 2008
Release SR17.0
State Changes

Event Description
O u t a g e ( Y / N )
C Comments h & Notes a n g e S t a t u s 6.0 release): Added related alarms U RFC(SR1 6.0 release): Added related alarms M Currently this trap is not supported
angeEvent
CONTAINER LOST PARTIAL FUNCTIONALIT Y 604 HW CONTAINER LOST FULL FUNCTIONALIT Y HW CONTAINER RESTORED PARTIAL FUNCTIONALIT Y HW CONTAINER RESTORED PARTIAL FUNCTIONALIT Y HW CONTAINER RESTORED PARTIAL FUNCTIONALIT Y MISCELLANEO US CONTAINER FULLY OPERATIONAL
.2.5.1.4.101.<UANC>.<INST ANCE>
AINER
306,309,31 0,318322,324,32 7 1 U-EImp U-D-Idl EMPTY 302306,309,31 0,318322,324,32 7 EMPTY
failed.
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_HW_CONT AINER
605
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_HW_CONT AINER
I-I-I
U-D-Idl
EMPTY
605
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_HW_CONT AINER
U-DIdl
U-E-Imp
EMPTY
302306,309,31 0,318322,324,32 7 EMPTY
605
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_HW_CONT AINER
I-I-I
U-E-Imp
EMPTY
U RFC(SR1 6.0 release): Added related alarms M Currently this trap is not supported
613
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
iCP_MISC
U-DIdl
U-E-A
EMPTY
302306,309,31 0,318,320,3 21,324,327
Miscellaneous components (Fans, Power Supplies) are fully operational.
606
MISCELLANEO US CONTAINER FULLY OPERATIONAL
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
iCP_MISC
U-EImp
U-E-A
EMPTY
302306,309,31 0,318,320,3 21,324,327
Miscellaneous components are fully operational.
607
FRU RESTORED FUNCTIONALIT Y
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST ANCE>
iCP_IOBLADE
1 - 6, 26-27
U-DIdl
U-E-A
EMPTY
EMPTY
FRU has become operational.
M RFC(SR1 6.0 release): Added related alarms, BCCB 2582 U RFC(SR1 6.0 release): Added related alarms U EMPTY
October 30, 2008
iCP-17

State Changes
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info
Event Description
O u t a g e ( Y / N )
607
607
607
608
608
608
608
608
608
609
609
609
610
FRU RESTORED FUNCTIONALIT Y FRU RESTORED FUNCTIONALIT Y FRU RESTORED FUNCTIONALIT Y FRU LOST FUNCTIONALIT Y FRU LOST FUNCTIONALIT Y FRU LOST FUNCTIONALIT Y FRU LOST FUNCTIONALIT Y FRU LOST FUNCTIONALIT Y FRU LOST FUNCTIONALIT Y FRU RESTORED PARTIAL FUNCTIONALIT Y FRU RESTORED PARTIAL FUNCTIONALIT Y FRU RESTORED PARTIAL FUNCTIONALIT Y FRU RESTORED
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.104.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.104.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST ANCE>
iCP_IOBLADE
1-6
L-D-Idl
U-D-Idl
EMPTY
EMPTY
FRU has become unlocked.
iCP_NIOC
1-2
U-DIdl
U-E-A
EMPTY
EMPTY
U EMPTY
iCP_SCSI
1-2
U-DIdl
U-E-A
EMPTY
305
M EMPTY
iCP_IOBLADE
1-6
U-EImp U-DIdl U-E-A
L-D-Idl
EMPTY
EMPTY
I/O Blade has been locked by the operator. I/O Blade has been locked by the operator. FRU has become nonoperational. FRU has become locked.
U EMPTY
iCP_IOBLADE
1-6
L-D-Idl
EMPTY
EMPTY
U EMPTY
iCP_IOBLADE
1 - 6, 26-27 1 - 6, 26-27 1-2
U-D-Idl
EMPTY
EMPTY
U EMPTY
iCP_IOBLADE
U-E-A
L-D-Idl
EMPTY
EMPTY
U EMPTY
iCP_NIOC
U-E-A
U-D-Idl
EMPTY
EMPTY
FRU has become nonoperational. FRU has become nonoperational. FRU has become partial operational.
U EMPTY
iCP_SCSI
1-2
U-E-A
U-D-Idl
EMPTY
305
M EMPTY
iCP_IOBLADE
1-6
U-DIdl
U-E-Imp
EMPTY
EMPTY
U EMPTY
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE>
iCP_NIOC
1-2
U-DIdl
U-E-Imp
EMPTY
EMPTY
FRU has become partial operational.
U EMPTY
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.104.<UANC>.<INST ANCE>
iCP_SCSI
1-2
U-DIdl
U-E-Imp
EMPTY
305
N Applies to ATCA-iCP Only
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST
iCP_IOBLADE
1-6
U-EImp
U-E-A
EMPTY
EMPTY
U EMPTY
iCP-18
October 30, 2008
Release SR17.0
State Changes

Event Description
O u t a g e ( Y / N )
610
610
611
611
611
612
612
612
614
614
615
FUNCTIONALIT Y FRU RESTORED FUNCTIONALIT Y FRU RESTORED FUNCTIONALIT Y FRU LOST PARTIAL FUNCTIONALIT Y FRU LOST PARTIAL FUNCTIONALIT Y FRU LOST PARTIAL FUNCTIONALIT Y FRU LOST FUNCTIONALIT Y FRU LOST FUNCTIONALIT Y FRU LOST FUNCTIONALIT Y NODE RESTORED FULL FUNCTIONALIT Y NODE RESTORED FULL FUNCTIONALIT Y MISCELLANEO US CONTAINER FAILURE
ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.104.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.104.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.106.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.105.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.104.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.413.<UANC>.<INST ANCE> iCP_NIOC 1-2 U-EImp U-E-A EMPTY EMPTY FRU has become operational. N U EMPTY
iCP_SCSI
1-2
U-EImp
U-E-A
EMPTY
305
N Applies to ATCA-iCP Only U EMPTY
iCP_IOBLADE
1 - 6, 26-27
U-E-A
U-E-Imp
EMPTY
EMPTY
iCP_NIOC
1-2
U-E-A
U-E-Imp
EMPTY
EMPTY
U EMPTY
iCP_SCSI
1-2
U-E-A
U-E-Imp
EMPTY
305
N Applies to ATCA-iCP Only U EMPTY
iCP_IOBLADE
1-6
U-EImp U-EImp U-EImp U-DIdl
U-D-Idl
EMPTY
EMPTY
FRU has become nonoperational. FRU has become nonoperational. FRU has become nonoperational The iCP NODE has restored full functionality.
iCP_NIOC
1-2
U-D-Idl
EMPTY
EMPTY
U EMPTY
iCP_SCSI
1-2
U-D-Idl
EMPTY
305
iCP_NODE
1-2
U-E-A
613, 503
EMPTY
N Applies to ATCA-iCP Only M EMPTY
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.413.<UANC>.<INST ANCE>
iCP_NODE
1-2
U-EImp
U-E-A
606, 503
EMPTY
The iCP NODEhas restored full functionality.
U EMPTY
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
iCP_MISC
U-E-A
U-D-Idl
EMPTY
302306,309,31 0,318,320,3 21,324,327
All miscellaneous components are no longer operational.
U RFC(SR1 6.0 release): Added related alarms
October 30, 2008
iCP-19

State Changes
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info
Event Description
O u t a g e ( Y / N )
616
617
NODE LOST PARTIAL FUNCTIONALIT Y MISCELLANEO US CONTAINER PARTLY OPERATIONAL
iCP_NODE
1-2
U-E-A
U-E-Imp
603, 501
EMPTY
The iCP NODE has lost partial functionality.
iCP_MISC
U-E-A
U-E-Imp
EMPTY
302306,309,31 0,318,320,3 21,324,327
Miscellaneous components are partially operational.
618
618
618
619
NODE LOST FULL FUNCTIONALIT Y NODE LOST FULL FUNCTIONALIT Y NODE LOST FULL FUNCTIONALIT Y MISCELLANEO US CONTAINER FAILURE
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.413.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.413.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.413.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
iCP_NODE
1-2
I-I-I
U-D-Idl
602, 502
EMPTY
The iCP NODE has lost full functionality.
U RFC(SR1 6.0 release): Added related alarms U EMPTY
iCP_NODE
1-2
U-E-A
U-D-Idl
602, 502
EMPTY
U EMPTY
iCP_NODE
1-2
U-EImp
U-D-Idl
602, 502
EMPTY
U EMPTY
iCP_MISC
U-EImp
U-D-Idl
EMPTY
302306,309,31 0,318,320,3 21,324,327
All miscellaneous components are no longer operational.
620
621
NODE RESTORED PARTIAL FUNCTIONALIT Y MISCELLANEO US CONTAINER PARTLY OPERATIONAL
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.413.<UANC>.<INST ANCE>
iCP_NODE
1-2
U-DIdl
U-E-Imp
605, 504
EMPTY
The iCP NODE has restored partial functionality.
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.107.<UANC>.<INST ANCE>
iCP_MISC
U-DIdl
U-E-Imp
EMPTY
302306,309,31 0,318,320,3 21,324,327
Miscellaneous components are partially operational.
622
1002
HW CONTAINER RESTORED FULL FUNCTIONALIT Y LOGICAL LINK LOCKED
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.101.<UANC>.<INST ANCE>
iCP_HW_CONT AINER
U-EImp
U-E-A
EMPTY
302306,309,31 0,318322,324,32 7 217
All HW Container's FRUs are fully operational.
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.410.<UANC>.<INST
iCP_MTL
1-16
U-E-A
L-D-Idl
EMPTY
Link has been locked.
U EMPTY
iCP-20
October 30, 2008
Release SR17.0
State Changes

Event Description
O u t a g e ( Y / N )
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
1002
LOGICAL LINK LOCKED LOGICAL LINK LOCKED LOGICAL LINK LOCKED LOGICAL LINK LOCKED LOGICAL LINK LOCKED LOGICAL LINK LOCKED LOGICAL LINK LOCKED LOGICAL LINK UNLOCKED LOGICAL LINK UNLOCKED LOGICAL LINK UNLOCKED LOGICAL LINK UNLOCKED NODE IS NO LONGER SUPERVISOR NODE IS NO LONGER SUPERVISOR NODE IS NO LONGER SUPERVISOR NODE IS SUPERVISOR
1002
1002
1002
1002
1002
1002
1003
1003
1003
1003
1007
1007
1007
1008
ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.410.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.414.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.414.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.415.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.415.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.418.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.418.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.410.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.414.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.415.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.418.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.417.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.417.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.417.<UANC>.<INST ANCE> 1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.417.<UANC>.<INST ANCE>
iCP_MTL
1-16
U-DIdl U-E-A
L-D-Idl
EMPTY
217
Disabled Link has been locked. Link is locked and unable to provide service. Link is locked and unable to provide service. Link is locked and unable to provide service. Link is locked and unable to provide service. Disabled Link has been locked. Link has been locked.
iCP_RSL_MOBI S iCP_RSL_MOBI S iCP_RSL_SNMP
110000 110000 110000 110000 1 - 336
L-D-Idl
EMPTY
217
U EMPTY
U-DIdl U-E-A
L-D-Idl
EMPTY
217
U EMPTY
L-D-Idl
EMPTY
217
U EMPTY
iCP_RSL_SNMP
U-DIdl U-DIdl U-E-A
L-D-Idl
EMPTY
217
U EMPTY
iCP_XBL
L-D-Idl
501 502
217
U EMPTY
iCP_XBL
1 - 336
L-D-Idl
EMPTY
217
U EMPTY
iCP_MTL
1-16
L-D-Idl
U-D-Idl
EMPTY
EMPTY
Link has been unlocked.
U EMPTY
iCP_RSL_MOBI S iCP_RSL_SNMP
110000 110000 1 - 336
L-D-Idl
U-D-Idl
EMPTY
EMPTY
LAPD link has been unlocked. LAPD link has been unlocked. Link has been unlocked.
U EMPTY
L-D-Idl
U-D-Idl
EMPTY
EMPTY
U EMPTY
iCP_XBL
L-D-Idl
U-D-Idl
504 503
EMPTY
U EMPTY
iCP_SUPERVIS OR iCP_SUPERVIS OR iCP_SUPERVIS OR iCP_SUPERVIS OR
U-E-A
U-D-Idl
604
EMPTY
The iCP Node is in Maintenance The iCP NODE is ActiveNonsupervisor The iCP Node is in Maintenance The iCP NODE is the Supervisor. (Pair Role)
U EMPTY
U-E-A
U-E-Imp
603
EMPTY
U EMPTY
U-EImp U-DIdl
U-D-Idl
604
EMPTY
U EMPTY
U-E-Imp
603
EMPTY
U EMPTY
October 30, 2008
iCP-21

State Changes
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info
Event Description
O u t a g e ( Y / N )
1008
NODE IS SUPERVISOR
1.3.6.1.4.1.161.3.3.10.5.7.1.1 .2.5.1.4.417.<UANC>.<INST ANCE>
iCP_SUPERVIS OR
U-EImp
U-E-A
604
EMPTY
The iCP NODE is the Supervisor. (Pair Role)
iCP-22
October 30, 2008
Release SR17.0
__________________________________ Events
Event Type
Reason Code
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N ) N
actionStatusEve nt
Background Download started
1.3.6.1.4.1.16 1.3.3.10.2.10. 1.1.0
iCP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
1.3.6.1.4.1.16 1.3.3.10.2.11. 1.1.0
iCP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
1,2 or 3
Background Download aborted Incorrect action status Background Download Aborted
1.3.6.1.4.1.16 1.3.3.10.2.10. 1.2.0
iCP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure (reason and line number in configuration file). Event is generated if OLCC background download has been aborted.
C h a n g e S t a t u s D
Comments & Notes
The state change was updated to keep it consistent with the code and other documentation and avoid confusion. RFC(SR17.0 Melody): deleted
N D
The state change was updated to keep it consistent with the code and other documentation and avoid confusion. RFC(SR17.0 Melody): deleted
N D
actionStatusEve nt
2= Aborted
1.3.6.1.4.1.16 1.3.3.10.2.10. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
2= Aborted
1.3.6.1.4.1.16 1.3.3.10.2.11. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has
The state change was updated to keep it consistent with the code and other documentation and avoid confusion. RFC(SR17.0 Melody): deleted N M RFC(SR17.0 Melody): modified for the feature
N M RFC(SR17.0 Melody): modified for the feature
October 30, 2008
iCP-23

Event Type
Reason Code
Release SR17.0
From State To State Related State Changes Related Alarms Event Description
O u t a g e ( Y / N ) failed. Action Status Error Code may contain addition details. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download abort (bgdlAbort) is successful. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Comments & Notes
actionStatusEve nt
3= Failed
1.3.6.1.4.1.16 1.3.3.10.2.10. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
3= Failed
1.3.6.1.4.1.16 1.3.3.10.2.11. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
4= Successf ul
Background Download Completed Successfull y
1.3.6.1.4.1.16 1.3.3.10.2.10. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
4= Successf ul
actionStatusEve nt
4= Successf ul
Background Download Aborted Successfull y Background Download Switch Completed Successfull y
1.3.6.1.4.1.16 1.3.3.10.2.10. 1.2.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
1.3.6.1.4.1.16 1.3.3.10.2.11. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
2= Aborted
Upgrade Aborted
1.3.6.1.4.1.16 1.3.3.10.2.12. 2.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
N N RFC(SR17.0 Melody): Added for the feature Applies to ATCA-iCP Only
iCP-24
October 30, 2008
Release SR17.0
Event Type
Reason Code

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
actionStatusEve nt
3= Failed
Upgrade Failed
1.3.6.1.4.1.16 1.3.3.10.2.12. 2.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
4= Successf ul
Upgrade Completed Successfull y
1.3.6.1.4.1.16 1.3.3.10.2.12. 2.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
0x90
1.3.6.1.4.1.16 1.3.3.10.2.13. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. A LMT or UNIX user has logged in. See the Action Status Information for details
actionStatusEve nt
0x91
1.3.6.1.4.1.16 1.3.3.10.2.13. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatusEve nt
0x92
Session timed-out
1.3.6.1.4.1.16 1.3.3.10.2.13. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N N action status information includes the following information: reason code <user login name> <access level> login. RFC(SR17.0 Melody): Added for the feature Applies to ATCA-iCP Only N N action status information includes the following information: reason code <user login name> <access level> logout. RFC(SR17.0 Melody): Added for the feature Applies to ATCA-iCP Only N N action status information includes the following information: reason code <user login name> <access level> login session timedout. RFC(SR17.0 Melody): Added for the
October 30, 2008
iCP-25

Event Type
Reason Code
Release SR17.0
From State To State Related State Changes Related Alarms Event Description
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Comments & Notes
actionStatusEve nt
0x94
1.3.6.1.4.1.16 1.3.3.10.2.13. 1.1.0
ICP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
availabilityEvent
EMPTY
reStartEvent
EMPTY
<universal time> <sequence number> <secondary id> <new mode> <time of switch> <reason code> <old mode> <additional text> <reason text> <universal time> <managed object instance> <usage state> <operationa l state> <administra tive state> <boot ROM version> <software Load version> <database version> <code version> <system
EMPTY
ICP
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated when the iCP mode changes. (Supervisor state changes, loss of 50% of RSLs, loss of 50% MTLs, loss of XBLs)
feature Applies to ATCA-iCP Only N N action status information includes the following information: reason code <user login name> <access level> login session manually terminated. RFC(SR17.0 Melody): Added for the feature Applies to ATCA-iCP Only N M Supervisor State Changes are detected through changes in Mode State. RFC(SR17.0 release): Changed MOI Label to be capital letter
1.3.6.1.4.1.16 1.3.3.10.2.3.1. 0,
ICP_NO DE
EMPTY
EMPTY
EMPTY
EMPTY
This event is used to inform the OMC whenever iCP switches its application code load or when it reboots. It also tells the OMC that SNMP agent is operational and is ready to handle request.
N M RFC(SR17.0 release): Changed MOI Label to be capital letter
iCP-26
October 30, 2008
Release SR17.0
Event Type
Reason Code

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
actionStatusEve nt
EMPTY
description > <latest reset reason> <outage time since latest reset> <reboot time> <boot diagnostics > <universal time> <managed object instance> <request id> <action status> <action status info>
EMPTY
On-Line Switch(ol cSwitch)
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure (reason and line number in configuration file).
N M RFC(SR17.0 release): Changed MOI Label to be capital letter
October 30, 2008
iCP-27
Release SR17.0
iCP-28
October 30, 2008
Release SR17.0
________________________________ Alarms
Alarm Type
Alarm Code
iDAC
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t & C l e a r R
O u t a g e Y / N
Comments & Notes
29500
DAP Connection Failure
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.5.1.2.n
IDAC_DAP _LINK
1-15
Cannot establish TCP/IP connection with DAP. DAP IP Address: <DAP IP address>
Critical
EMPTY
EMPTY
29501
SM Connection Failure
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
Cannot establish physical connection with SM.
Critical
EMPTY
EMPTY
29501
SM Connection Failure WAN Connection Failure
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0 1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.3.2.0
IDAC_GEN
29502
IDAC_WAN _LINK
Established Physical Connection with SM Cannot establish physical connection with WAN.
Clear
EMPTY
EMPTY
iDAC will persistently retry the connection. Verify that DAP is operational. Verify IP configuration and iDEN LAN network connectivity. iDAC will persistently retry the connection. Verify PVC connections and Frame Relay network connectivity. EMPTY
iDAC cannot communicate with this DAP.
iDAC cannot communicate with APDs.
iDAC can communicate with APDs. iDAC cannot distribute intra-urban voice packets.
Critical
EMPTY
EMPTY
29502
WAN Connection Failure
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.3.2.0
IDAC_WAN _LINK
Established Physical Connection with WAN
Clear
EMPTY
EMPTY
iDAC will persistently retry the connection. Verify network connectivity from iDAC to switch/router. EMPTY
iDAC can distribute intra-urban voice packets.
October 30, 2008
iDAC-1

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
31500
DAP Link Version Check Procedure Failed
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.5.1.2.n
IDAC_DAP _LINK
1-15
No response from DAP.
Critical
EMPTY
EMPTY
31500
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.5.1.2.n
IDAC_DAP _LINK
1-15
Status field indicates failure.
Critical
EMPTY
EMPTY
31500
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.5.1.2.n
IDAC_DAP _LINK
1-15
Version mismatch.
Critical
EMPTY
EMPTY
31500
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.5.1.2.n
IDAC_DAP _LINK
1-15
Source and destination mismatch in message header from DAP. Logical Link Up
Critical
EMPTY
EMPTY
31500
31503
DAP Link Version Check Procedure Failed iDAC Link Version Negotiation Failed
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.5.1.2.n 1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.11.2.1.9. m.n
IDAC_DAP _LINK
1-15
Clear
EMPTY
EMPTY
iDAC will persist with Link Version Check Procedure until receives a success indication from the DAP. Verify configuration between iDAC and DAP in OMC. Either the iDAC or the DAP must be upgraded to a software load that supports a compatible link protocol version. Status field indicates success, but DAP sends a version to iDAC that iDAC doesn't support. Contact CNRC. Check DAP ID of the iDAC configuration and the iDAC ID of the DAP configuration in the OMC configuration. EMPTY
This is an expected alarm when a new DAP is added and has not been fully initialized. iDAC cannot communicate with this DAP.
iDAC can communicate with this DAP. iDAC cannot distribute voice to and from this inter-urban iDAC.
IDAC_IDAC _LINK
m=116777 215 and n=1800
Version mismatch. UANC: <interurban iDAC's UANC>, ID: <inter-urban iDAC's ID>. Logical Link Up
Critical
EMPTY
EMPTY
31503
iDAC Link Version Negotiation Failed
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.2.11.2.1.9. m.n
IDAC_IDAC _LINK
m=116777 215 and n=1800
Clear
EMPTY
EMPTY
Either the originating iDAC or the interurban iDAC must be upgraded to a software load that supports a compatible link protocol version. EMPTY
iDAC can distribute voice to and from this inter-urban iDAC.
iDAC-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Inst
Alarm Code Text
Severity
Related Alarms
Remedy
O u t a g e Y / N
Comments & Notes
31504
Internal Software Error; iDAC will reset Error in configuration data; Default value available
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
31505
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
File name: <file name>, Process name: <process name>, Reason: <reason string> <field> was out of range and it is changed to <new value>.
Critical
EMPTY
EMPTY
iDAC will recover via self-reset.
iDAC processing functionality is interrupted until recovery. Configured value from OMC was out of range. A default value is being used.
Major
EMPTY
EMPTY
31506
Error in configuration data; Default value unavailable
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
<field> was out of range.
Critical
EMPTY
EMPTY
31507
Call Capacity Exceeded
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
iDAC Call or Target Capacity has exceeded the threshold. iDAC Call or Target Capacity No Longer Exceeded iDAC is experiencing CPU overload.
Major
EMPTY
EMPTY
iDAC continues execution with the default. Analyze and change OMC configuration as needed for this iDAC. Analyze and change OMC configuration as needed for this iDAC. If iDAC can continue execution, it will ignore the bad value; otherwise it will recover via selfreset. If this alarm occurs frequently, additional iDACs may need to be added. EMPTY
Configured value from OMC was out of range. No default value is available to be used.
iDAC will discard new call setup messages until call or target capacity is no longer exceeded. iDAC call processing functionality is restored. iDAC processing functionality is limited based on the severity of overload.
31507
Call Capacity Exceeded
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0 1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
Clear
EMPTY
EMPTY
31508
CPU Overload
IDAC_GEN
Major
EMPTY
EMPTY
31508
CPU Overload
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
iDAC is no longer experiencing CPU overload
Clear
EMPTY
EMPTY
Check statistics to determine if the iDAC is running at or above the rated call profile. If this alarm occurs frequently, additional iDACs may need to be added. EMPTY
iDAC processing functionality is restored.
October 30, 2008
iDAC-3

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
31509
HSSI Port Overload
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
iDAC is experiencing port overload on HSSI. iDAC is no longer experiencing port overload on HSSI. iDAC is experiencing port overload on WAN.
Major
EMPTY
EMPTY
31509
HSSI Port Overload
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
Clear
EMPTY
EMPTY
Determine the source of HSSI port overload. For example, check APD statistics. EMPTY
iDAC voice distribution functionality is limited.
iDAC voice distribution functionality is restored. iDAC voice distribution functionality is limited.
31510
WAN Port Overload
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
Major
EMPTY
EMPTY
31510
WAN Port Overload
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
31511
LMT Halt Command Issued
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
iDAC is no longer experiencing port overload on WAN. The iDAC LMT halt command has been issued. The iDAC is in the process of halting.
Clear
EMPTY
EMPTY
Determine the source of WAN port overload. For example, check WAN router statistics. EMPTY
iDAC voice distribution functionality is restored. Halt command was issued at the LMT. iDAC will continue to process active calls for a maximum of ten minutes.
Critical
EMPTY
EMPTY
32500
FRU Failure
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
<FRU> failed.
Critical
EMPTY
EMPTY
Wait for the LMT indication that the halt is complete and perform maintenance as necessary. Bring the iDAC back online by power cycling the box. Replace the FRU that failed.
32501
Hardware Configuration Error
1.3.6.1.4.1.16 1.3.3.10.5.13. 1.1.1.1.0
IDAC_GEN
Unrecognized <hardware name> version <version number>.
Major
EMPTY
EMPTY
If necessary, replace the respective hardware unit.
Either iDAC motherboard FRU or HSSI FRU has failed. iDAC cannot communicate to DAPs, OMC, and remote iDACs if motherboard FRU fails. iDAC cannot communicate to APDs if HSSI FRU fails. Take the installed HSSI card out and put in one with the correct HSSI version.
iDAC-4
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label )
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 0 8
DAP LINK UP
1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX
U-DIdl
U-EImp
201, 801, 806
31500C
1 0 9
APD LINK UP
1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX
U-DIdl
U-EImp
401, 901, 902, 906
EMPTY
1 1 0
iDAC LINK UP
1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX
U-DIdl
U-EImp
301, 701, 702, 706
31503C
1 0 7
DAP LINK UP
1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX
U-DIdl
U-E-A
201, 802
31500C
1 8 0
APD LINK UP
1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX
U-DIdl
U-E-A
401, 901, 902
EMPTY
1 7 9
iDAC LINK UP
1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX
U-DIdl
U-E-A
301, 701, 702
31503C
1 1
RESET FROM OMC
1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX
U-DIdl
L-E-Idl
EMPTY
EMPTY
iDAC establishes the first DAP link connection. At least one APD and one iDAC logical link are already connected for this transition to occur. iDAC establishes the first APD link connection. At least one DAP and one iDAC logical link are already connected for this transition to occur. iDAC establishes the first iDAC link connection. At least one DAP and one APD logical link are already connected for this transition to occur. iDAC establishes the only DAP link connection. At least one APD and one iDAC logical link are already connected for this transition to occur (bypassing the UEImp state transition). iDAC establishes the first APD link connection. All DAP logical links and at least one iDAC logical link are already connected for this transition to occur (bypassing the UEImp state transition). iDAC establishes the first iDAC link connection. All DAP logical links and at least one APD logical link are already connected for this transition to occur (bypassing the UEImp state transition). Reset command from OMC-R. iDAC will start load shedding.
S t a t u s N U
N U
iDAC can perform limited voice distribution functionality. All the existing calls for this DAP will be deleted if this DAP was previously up & went down. iDAC can perform limited voice distribution functionality.
N U
iDAC can perform limited voice distribution functionality.
N U
N U
iDAC can perform voice distribution functionality for enabled links. All the existing calls for this DAP will be deleted if this DAP was previously up and went down. iDAC can perform voice distribution functionality for enabled links.
N U
iDAC can perform voice distribution functionality for enabled links.
Y U
iDAC will service active calls for up to 10 minutes.
October 30, 2008
iDAC-5

State Changes
R e a s o n C o d e
Release SR17.0
To State Related State Changes Related Alarms
OMC Text
MOI Info (Id)
MOI Info (Label )
Inst
From State
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 1 1 2 1 1 4 1 0 1 1 1 7
INTERNAL RESET LOCK FROM OMC HALT FROM LMT DAP LINK DOWN
1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX IDAC_B OX IDAC_B OX IDAC_B OX
U-DIdl U-DIdl U-DIdl U-E-A
L-E-Idl
EMPTY
31504R, 31506R EMPTY
L-E-Idl
EMPTY
iDAC has reset itself due to internal failure. iDAC will start load shedding. Lock command from OMC-R. iDAC will start load shedding. Halt command from LMT. iDAC will start load shedding. iDAC loses connectivity to a single DAP. At least one of each logical link (DAP, APD, and iDAC) is connected. Otherwise, the state changes to UDIdl. A DAP is added during OLCC. (If an APD or iDAC is added, box stays UEA.) iDAC has exceeded call or target capacity, or entered CPU overload, HSSI port overload, or WAN port overload.
Y U
iDAC will service active calls for up to 10 minutes. iDAC will service active calls for up to 10 minutes. iDAC will service active calls for up to 10 minutes. iDAC cannot service new calls assigned to this DAP.
Y U
L-E-Idl
EMPTY
31511R
Y U
U-EImp
202, 808
EMPTY
N U
1 7 3 1 2 0
OLCC DEVICE ADD ENTER OVERLOADI NG CONDITION
1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX IDAC_B OX
U-E-A
U-EImp U-EImp
811
EMPTY
N U
EMPTY
U-E-A
1001
31507R, 31508R, 31509R, 31510R
N U
1 2 5 1 2 6 1 2 7 1 7 4 1 2 8 1 2 9
ALL DAP LINKS DOWN ALL APD LINKS DOWN ALL iDAC LINKS DOWN OLCC DEVICE DELETE RESET FROM OMC INTERNAL RESET
1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX IDAC_B OX IDAC_B OX IDAC_B OX IDAC_B OX IDAC_B OX
U-E-A
U-DIdl U-DIdl U-DIdl U-DIdl L-E-Idl
202, 803, 807 402, 903, 907 302, 703, 707 810, 812, 910, 912, 710, 712 EMPTY
EMPTY
iDAC loses connectivity to all DAPs. iDAC loses connectivity to all APDs. iDAC loses connectivity to all iDACs. Delete the only DAP, the last APD, or the last iDAC during OLCC. Reset command from OMC-R. iDAC will start load shedding. iDAC has reset itself due to internal failure. iDAC will start load shedding.
N U
iDAC will discard new call setup messages for call or target capacity exceeded situation. iDAC processing functionality is limited based on the severity of overload in CPU overload situation. iDAC voice distribution functionality is limited for HSSI port overload and WAN port overload situations. iDAC cannot service any new calls for all DAPs. iDAC cannot perform voice distribution functionality. iDAC cannot perform voice distribution functionality. EMPTY
U-E-A
EMPTY
N U
U-E-A
EMPTY
N U
U-E-A
31500C, 31503C EMPTY
N U
U-E-A
Y U
iDAC will service active calls for up to 10 minutes. iDAC will service active calls for up to 10 minutes.
U-E-A
L-E-Idl
EMPTY
31504R, 31506R
Y U
iDAC-6
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Label ) Inst From State To State Related State Changes Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 3 1 1 0 2 1 3 3
LOCK FROM OMC HALT FROM LMT ALL DAP LINKS UP
1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX IDAC_B OX IDAC_B OX
U-E-A
L-E-Idl
EMPTY
EMPTY
Lock command from OMC-R. iDAC will start load shedding. Halt command from LMT. iDAC will start load shedding. Connectivity to all DAPs, at least one APD and at least one iDAC is now established. No other impaired conditions exist.
S t a t u s Y U
iDAC will service active calls for up to 10 minutes. iDAC will service active calls for up to 10 minutes. iDAC can perform voice distribution functionality for enabled links. All the existing calls for this DAP will be deleted if this DAP was previously up and went down. iDAC processing functionality is restored for call or target capacity exceeded and CPU overload situations. iDAC voice distribution functionality is restored for HSSI port overload and WAN port overload situations. EMPTY
U-E-A
L-E-Idl
EMPTY
31511R
Y U
U-EImp
U-E-A
201, 802, 806
31500C
N U
1 6 6
EXIT OVERLOADI NG CONDITION
1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX
U-EImp
U-E-A
1002
31507C, 31508C, 31509C, 31510C
1 7 5
OLCC DEVICE DELETE
1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX
U-EImp
U-E-A
809
31500C
1 4 8 1 4 9 1 5 0 1 7 8 1 5 2 1 5 3 1 5 5
ALL DAP LINKS DOWN ALL APD LINKS DOWN ALL iDAC LINKS DOWN OLCC DEVICE DELETE RESET FROM OMC INTERNAL RESET LOCK FROM OMC
1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX IDAC_B OX IDAC_B OX IDAC_B OX IDAC_B OX IDAC_B OX IDAC_B OX
U-EImp U-EImp U-EImp U-EImp U-EImp U-EImp U-EImp
U-DIdl U-DIdl U-DIdl U-DIdl L-E-Idl
202, 803, 807 402, 903, 907 302, 703, 707 810, 812, 910, 912, 710, 712 EMPTY
31500R
Connectivity to all DAPs, at least one APD and at least one iDAC is already established. iDAC is no longer impaired due to exceeding call or target capacity, CPU overload, HSSI port overload, or WAN port overload. Delete a DAP whose logical link is down during OLCC. This link down was the only impaired condition. At least one of each logical link (DAP, APD, and iDAC) is still connected. iDAC loses connectivity to all DAPs. iDAC loses connectivity to all APDs. iDAC loses connectivity to all iDACs. Delete the last DAP, APD, or iDAC during OLCC. Reset command from OMC-R. iDAC will start load shedding. iDAC has reset itself due to internal failure. iDAC will start load shedding. Lock command from OMC-R. iDAC will start load shedding.
N U
N U
N U
iDAC cannot service any new calls for all DAPs. iDAC cannot perform voice distribution functionality. iDAC cannot perform voice distribution functionality. EMPTY
EMPTY
N U
EMPTY
N U
31500C, 31503C EMPTY
N U
Y U
iDAC will service active calls for up to 10 minutes. iDAC will service active calls for up to 10 minutes. iDAC will service active calls for up to 10 minutes.
L-E-Idl
EMPTY
31504R, 31506R EMPTY
Y U
L-E-Idl
EMPTY
Y U
October 30, 2008
iDAC-7

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label )
Inst
From State
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 0 3 1 5 7
HALT FROM LMT LOAD SHEDDING COMPLETE
1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0
IDAC_B OX IDAC_B OX
U-EImp L-E-Idl
L-E-Idl
EMPTY
31511R
Halt command from LMT. iDAC will start load shedding. iDAC has triggered a reset or lock. Load shedding complete will occur when all active calls have been processed, when the reset guard timer expires, or when fatal internal errors occur within iDAC rendering it unable to complete load shedding. iDAC receives unlock command from OMC-R. Reset command from OMC-R while the box is locked. iDAC has reset itself due to internal failure while the box is locked. iDAC establishes the first DAP logical link connection. Other DAP logical link connections are still down. iDAC establishes the only DAP logical link connection.
S t a t u s Y U
iDAC will service active calls for up to 10 minutes. iDAC will remain idle if the triggering condition was OMC lock. iDAC will reset if the triggering condition was OMC reset or internal reset. iDAC will Halt if the triggering condition is a LMT Halt. iDAC will reset.
L-D-Idl
EMPTY
EMPTY
Y U
1 5 8 1 5 9 1 7 2 8 0 1 8 0 2 8 0 3 8 1 2 8 0 6
UNLOCK FROM OMC RESET FROM OMC INTERNAL RESET LOGICAL LINK UP
1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.2.3.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.8.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.8.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.8.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.8.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.8.1.0
IDAC_B OX IDAC_B OX IDAC_B OX IDAC_D AP_CO NTAINE R IDAC_D AP_CO NTAINE R IDAC_D AP_CO NTAINE R IDAC_D AP_CO NTAINE R IDAC_D AP_CO NTAINE R IDAC_D AP_CO NTAINE R IDAC_D AP_CO
L-D-Idl
U-DIdl U-DIdl U-DIdl U-EImp
EMPTY
EMPTY
Y U
L-D-Idl
EMPTY
EMPTY
Y U
iDAC will reset.
L-D-Idl
EMPTY
EMPTY
Y U
iDAC will reset.
U-DIdl
201
31500C
N U
ALL DAP LOGICAL LINKS UP ALL DAP LOGICAL LINKS DOWN OLCC DEVICE DELETE ALL DAP LOGICAL LINKS UP
U-DIdl
U-E-A
201
31500C
N U
U-EImp
U-DIdl
202
EMPTY
iDAC loses the last DAP logical connection.
N U
iDAC can service calls for this DAP. All the existing calls for this DAP will be deleted if this DAP was previously down. iDAC can service calls for this DAP. All the existing calls for this DAP will be deleted if this DAP was previously down. iDAC cannot service any new calls for this DAP.
U-EImp
U-DIdl
EMPTY
31500C
Delete the only DAP whose logical link is up during OLCC.
N U
EMPTY
U-EImp
U-E-A
201
31500C
iDAC establishes the last DAP logical link connection. All DAP logical link connections are up.
N U
8 0 9 8 0
OLCC DEVICE DELETE ALL DAP LOGICAL
1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.8.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1.
U-EImp
U-E-A
EMPTY
31500C
U-E-A
U-DIdl
202
EMPTY
Delete a DAP whose logical link is down during OLCC. All other DAP logical link connections are up. iDAC loses the only DAP logical connection.
N U
iDAC can service calls for this DAP. All the existing calls for this DAP will be deleted if this DAP was previously up and went down. EMPTY
N U
iDAC cannot service calls for this DAP.
iDAC-8
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Event Description
O u t a g e ( Y / N )
Comments & Notes
7 esmrStateCh angeEvent 8 1 0 8 0 8 8 1 1 2 0 1
LINKS DOWN OLCC DEVICE DELETE LOGICAL LINK DOWN
2.8.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.8.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.8.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.8.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.5.1.2.n
OLCC DEVICE ADD
LOGICAL LINK UP
NTAINE R IDAC_D AP_CO NTAINE R IDAC_D AP_CO NTAINE R IDAC_D AP_CO NTAINE R IDAC_D AP_LIN K
U-E-A
U-DIdl
EMPTY
31500C
iDAC loses the only DAP logical connection during OLCC.
N U
EMPTY
U-E-A
U-EImp
202
EMPTY
iDAC loses a DAP logical connection. Other DAP logical link connections are still up. A DAP is added during OLCC.
N U
iDAC cannot service calls for this DAP.
U-E-A
U-EImp
EMPTY
EMPTY
N U
EMPTY
1-15
U-DIdl
U-E-A
EMPTY
31500C
TCP/IP connectivity established and Link Version Check Procedure passed.
N U
2 0 2 9 0 1 9 0 2 9 0 3 9 1 2 9 0 6 9 0 9
LOGICAL LINK DOWN
1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.5.1.2.n 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0
IDAC_D AP_LIN K IDAC_A PD_CO NTAINE R IDAC_A PD_CO NTAINE R IDAC_A PD_CO NTAINE R IDAC_A PD_CO NTAINE R IDAC_A PD_CO NTAINE R IDAC_A PD_CO NTAINE R
1-15
U-E-A
U-DIdl
EMPTY
EMPTY
LOGICAL LINK UP
U-DIdl
U-EImp
401
EMPTY
ALL APD LOGICAL LINKS UP ALL APD LOGICAL LINKS DOWN OLCC DEVICE DELETE ALL APD LOGICAL LINKS UP OLCC DEVICE DELETE
U-DIdl
U-E-A
401
EMPTY
TCP/IP connectivity lost, or Link Version Check Procedure has failed, or Link Continuity Check failed. iDAC establishes the first APD logical link connection. Other APD logical link connections are still down. iDAC establishes the only APD logical link connection.
N U
iDAC can communicate with this DAP. All the existing calls for this DAP will be deleted if this DAP was previously up and went down. iDAC cannot communicate with this DAP.
N U
iDAC can perform voice distribution functionality for this APD. iDAC can perform voice distribution functionality for this APD. iDAC cannot perform voice distribution functionality for this APD. EMPTY
N U
U-EImp
U-DIdl
402
EMPTY
iDAC loses the last APD logical connection.
N U
U-EImp
U-DIdl
EMPTY
EMPTY
Delete the only APD whose logical link is up during OLCC.
N U
U-EImp
U-E-A
401
EMPTY
iDAC establishes the last APD logical link connection.
N U
iDAC can perform voice distribution functionality for this APD. EMPTY
U-EImp
U-E-A
EMPTY
EMPTY
Delete an APD whose logical link is down during OLCC. All other APD logical link connections are up.
N U
October 30, 2008
iDAC-9

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label )
Inst
From State
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
9 0 7 9 1 0 9 0 8 9 1 1 4 0 1 4 0 2 7 0 1 7 0 2 7 0 3 7 1 2 7 0 6 7 0 9 7
ALL APD LOGICAL LINKS DOWN OLCC DEVICE DELETE LOGICAL LINK DOWN
1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.9.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.4.1.8.m.n 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.4.1.8.m.n 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161.
OLCC DEVICE ADD
LOGICAL LINK UP LOGICAL LINK DOWN LOGICAL LINK UP
ALL IDAC LOGICAL LINKS UP ALL IDAC LOGICAL LINKS DOWN OLCC DEVICE DELETE ALL IDAC LOGICAL LINKS UP OLCC DEVICE DELETE ALL IDAC
esmrStateCh
IDAC_A PD_CO NTAINE R IDAC_A PD_CO NTAINE R IDAC_A PD_CO NTAINE R IDAC_A PD_CO NTAINE R IDAC_A PD_LIN K IDAC_A PD_LIN K IDAC_ID AC_CO NTAINE R IDAC_ID AC_CO NTAINE R IDAC_ID AC_CO NTAINE R IDAC_ID AC_CO NTAINE R IDAC_ID AC_CO NTAINE R IDAC_ID AC_CO NTAINE R IDAC_ID
U-E-A
U-DIdl
402
EMPTY
iDAC loses the only APD logical connection.
S t a t u s N U
iDAC cannot perform voice distribution functionality.
U-E-A
U-DIdl
EMPTY
EMPTY
iDAC loses the only APD logical connection during OLCC.
N U
EMPTY
U-E-A
U-EImp
402
EMPTY
iDAC loses an APD logical connection. Other APD logical link connections are still up. An APD is added during OLCC.
N U
iDAC cannot perform voice distribution functionality for this APD. EMPTY
U-E-A
U-EImp
EMPTY
EMPTY
N U
m=0x0600 and n=1-45 m=0x0600 and n=1-45 1
U-DIdl U-E-A
U-E-A
EMPTY
EMPTY
iDAC-APD session is established. iDAC-APD session is terminated. iDAC establishes the first iDAC logical link connection. Other iDAC logical link connections are still down. iDAC establishes the only iDAC logical link connection.
N U
U-DIdl U-EImp
EMPTY
EMPTY
N U
U-DIdl
301
31503C
N U
iDAC can perform voice distribution functionality for this APD. iDAC cannot perform voice distribution functionality for this APD. iDAC can perform voice distribution functionality for this inter-urban iDAC. iDAC can perform voice distribution functionality for this inter-urban iDAC. iDAC cannot perform voice distribution functionality for this inter-urban iDAC. EMPTY
U-DIdl
U-E-A
301
31503C
N U
U-EImp
U-DIdl
302
EMPTY
iDAC loses the last iDAC logical connection.
N U
U-EImp
U-DIdl
EMPTY
31503C
Delete the only iDAC whose logical link is up during OLCC.
N U
U-EImp
U-E-A
301
31503C
iDAC establishes the last iDAC logical link connection.
N U
iDAC can perform voice distribution functionality for this inter-urban iDAC. EMPTY
U-EImp
U-E-A
EMPTY
31503C
U-E-A
U-D-
302
EMPTY
Delete an iDAC whose logical link is down during OLCC. All other iDAC logical link connections are up. iDAC loses the only iDAC
N U
N U
iDAC cannot perform voice
iDAC-10
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 7 7 1 0 7 0 8 7 1 1 3 0 1 3 0 2 1 0 0 1
LOGICAL LINKS DOWN OLCC DEVICE DELETE LOGICAL LINK DOWN
3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.10.1.0 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.11.2.1.9.m.n 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.11.2.1.9.m.n 1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.6.1.0
OLCC DEVICE ADD
LOGICAL LINK UP LOGICAL LINK DOWN ENTER OVERLOADI NG
AC_CO NTAINE R IDAC_ID AC_CO NTAINE R IDAC_ID AC_CO NTAINE R IDAC_ID AC_CO NTAINE R IDAC_ID AC_LIN K IDAC_ID AC_LIN K IDAC_L OADING _CONT AINER
Idl
logical connection.
distribution functionality for this inter-urban iDAC. N U EMPTY
U-E-A
U-DIdl
EMPTY
31503C
iDAC loses the only iDAC logical connection during OLCC. iDAC loses an iDAC logical connection. Other iDAC logical link connections are still up. An iDAC is added during OLCC.
U-E-A
U-EImp
302
EMPTY
N U
iDAC cannot perform voice distribution functionality for this inter-urban iDAC. EMPTY
U-E-A
U-EImp
EMPTY
EMPTY
N U
m=1-16777215 and n=1-800 m=1-16777215 and n=1-800 1
U-DIdl U-E-A
U-E-A
EMPTY
31503C
iDAC-iDAC session is established. iDAC-iDAC session is terminated. iDAC has exceeded call or target capacity, or entered CPU overload, HSSI port overload, or WAN port overload.
N U
U-DIdl U-E-A
EMPTY
EMPTY
N U
U-DIdl
EMPTY
31507R, 31508R, 31509R, 31510R
N U
1 0 0 2
EXIT OVERLOADI NG
1.3.6.1.4.1.161. 3.3.10.5.13.1.1. 2.6.1.0
IDAC_L OADING _CONT AINER
U-E-A
U-DIdl
EMPTY
31507C, 31508C, 31509C, 31510C
iDAC is no longer impaired due to call or target capacity, CPU overload, HSSI port overload, or WAN port overload.
N U
iDAC can perform voice distribution functionality for this inter-urban iDAC. iDAC cannot perform voice distribution functionality for this inter-urban iDAC. iDAC will discard new call setup messages for call or target capacity exceeded situation. iDAC processing functionality is limited based on the severity of overload in CPU overload situation. iDAC voice distribution functionality is limited for HSSI port overload and WAN port overload situations. iDAC processing functionality is restored for call or target capacity exceeded and CPU overload situations. iDAC voice distribution functionality is restored for HSSI port overload and WAN port overload situations.
October 30, 2008
iDAC-11
Release SR17.0
__________________________________ Events
Event Description
O u t a g e ( Y / N )
C h a n g e
Comment s & Notes
Restart Trap
Action Status
New Operate State: <operational state> New Usage State: <usage state> New Admin State: <administrative state> System ROM Version: <boot ROM version> System Load Version: <software Load version> System DB Version: <database version> System Code Version: <code version> Description: <system description> System Reset Reason: <latest reset reason> System Outage Time: <outage time since latest reset> System Reboot Time: <reboot time> System Boot Diagnostics: <boot diagnostics> <universal time>-<action status><action status info>
1.3.6.1.4. 1.161.3.3 .10.2.3.1. 0
IDAC_BOX
EMPTY
EMPTY
EMPTY
EMPTY
This event is used to inform the OMC whenever iDAC switches its application code load or when it reboots. It also tells the OMC that SNMP agent is operational and is ready to handle request.
S t a t u s N U
EMPTY
1.3.6.1.4. 1.161.3.3 .10.2.10. 1.1.0
Background Download(b gdlStart)
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
<universal time>-<action status><action status info>
Action Status
<universal time>-<action status><action status info>
1.3.6.1.4. 1.161.3.3 .10.2.10. 1.2.0 1.3.6.1.4. 1.161.3.3 .10.2.11. 1.1.0
Background Download Abort(bgdlA bort) On-Line Switch(olcS witch)
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has completed successfully or has failed. In case of failure, Action Status Info includes reason code for failure. Event is generated if OLCC background download has been aborted. Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure.
N U
EMPTY
N U
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
iDAC-12
October 30, 2008
Release SR17.0
__________________________________ Alarms
Alarm Type
Alarm Code
iSG
Remedy
R e p o r t & O u t a g e Y C / l N e a r R N C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Severity
Related Alarms
Comments & Notes
2901
SPA Connection Failure
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.4 .1.0
ISG_SP A_LINK
iSG cannot connect to SPA.
Major
EMPTY
EMPTY
iSG will persistently retry connection. Verify that SPA is operational. Verify IP configuration and connectivity.
2901
SPA Connection Failure
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.4 .1.0
ISG_SP A_LINK
Active iSG initiated connection to SPA failed.
Major
EMPTY
EMPTY
iSG will persistently retry connection. Verify that SPA is operational. Verify network connectivity.
R N
2902
SPA IP Address Mismatch
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.4 .1.0
ISG_SP A_LINK
3101
DAP Link Version Check procedure failed
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.3 .1.2.n
ISG_DA P_LINK
1-15
Connection request from unrecognized address <ip addr> received. No response from DAP.
Major
EMPTY
EMPTY
Verify that the IP address of the SPA matches the OMC-R configuration for this iSG. iSG will persist with Link Version Check Procedure until it receives a success indication. Verify that installed DAP SW contains support for surveillance feature. Verify configuration between iSG and DAP in OMC. Upgrade the iSG and/or DAP software to versions that support compatible link
R N
U iSG cannot be provisioned with surveillance information. Box state changes 109, 116, and 122 indicate that iSG can communicate with SPA. U iSG cannot be provisioned with surveillance information. Box state changes 109, 116, and 122 indicate that iSG can communicate with SPA. U Monitor for non-SPA devices attempting to communicate with iSG within the iDEN network.
Critical
EMPTY
EMPTY
R N
U iSG cannot perform surveillance for subjects assigned to this DAP.
3101
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.3 .1.2.n
ISG_DA P_LINK
1-15
Version mismatch.
Critical
EMPTY
EMPTY
R N
October 30, 2008
iSG-1

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 3101 DAP Link Version Check procedure failed 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.3 .1.2.n ISG_DA P_LINK 1-15 Status field indicates failure. Critical EMPTY EMPTY protocols. iSG will persist with Link Version Check Procedure until it receives a success indication. Investigate DAP alarms. iSG will drop the message. iSG will persist with Link Version Check Procedure. Verify DAP SW for incorrect values in ITC header. R N
Comments & Notes
3101
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.3 .1.2.n
ISG_DA P_LINK
1-15
3101
DAP Link Version Check procedure failed SPA Link version failure
3102
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.3 .1.2.n 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.4 .1.0 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.4 .1.0
ISG_DA P_LINK
1-15
ISG_SP A_LINK
Invalid <Destination FunctionId/ Destination MailBoxId/Sou rce InstanceId/De stination InstanceId> in ITC Header Link Version Check passed after previous failure. Incompatible version on iSG initiated connection. Link Version Check passed on iSG initiated connection after previous failure. Location: <sdlref>, Reason: <textmsg> iSG will reset. Location: <sdlref>, Reason: <textmsg> <field> was out of range and is changed to <new_value>
Critical
EMPTY
EMPTY
R N
Clear
EMPTY
EMPTY
EMPTY
C N
U iSG can perform surveillance for subjects assigned to this DAP. U Ability to provision iSG with surveillance information impaired.
Critical
EMPTY
EMPTY
3102
SPA Link version failure
ISG_SP A_LINK
Clear
EMPTY
EMPTY
Upgrade the iSG and/or SPA software to versions that support compatible link protocols. EMPTY
R N
C N
U Ability to provision iSG with surveillance information restored.
3103
3103
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.1.1 .0 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.1.1 .0 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.1.1 .0
ISG_GE N
Warning
EMPTY
EMPTY
iSG will recover by itself. Contact Motorola personnel. iSG will recover via selfreset.
R N
U iSG processing functionality is not impacted. U iSG processing functionality is interrupted until recovery. U Configured value from OMC was out of range. A default value is being used.
ISG_GE N
Critical
EMPTY
EMPTY
R Y
3104
Error in configuration data
ISG_GE N
Warning
EMPTY
EMPTY
Analyze and change OMC Configuration as needed for this iSG.
R N
iSG-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
3104
Error in configuration data Error in configuration data
3104
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.1.1 .0 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.1.1 .0 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.1.1 .0
ISG_GE N
No DAPs Configured
Warning
EMPTY
EMPTY
OMC needs to configure this iSG with at least one DAP. Analyze and change OMC Configuration as needed for this iSG. iSG will recover via selfreset. Analyze and change OMC Configuration for this parameter to value "0", so iSG can support both voice over HSSI and UDP.
Y C / l N e a r R N
Comments & Notes
U Configured number of DAPs in iSG = 0. iSG will remain in UEI state. U Configured value from OMC was out of range. No default value is available to be used. U Configured value from OMC is incorrect. No default value is available. iSG will not handle HSSI voice until the value is changed.
ISG_GE N
iSG will reset. <field> was out of range.
Critical
EMPTY
EMPTY
R Y
3104
Error in configuration data
ISG_GE N
3105
MIB values modified
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.1.1 .0
ISG_GE N
3109
iSG surveillance start rejected by DAP due to too many active IMSIs
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.3 .1.2.n
ISG_DA P_LINK
1-15
iSG VoiceReceptio nmethod parameter is configured All IP with legacy DAPs still in the urban. MIB Variable <variablenam e> modified through LMT Session to <newvalue> EMPTY
Critical
EMPTY
EMPTY
R N
Warning
EMPTY
EMPTY
Logout from LMT to revert back to old configuration values.
R N
U EMPTY
Major
EMPTY
EMPTY
3110
iSG surveillance start rejected by DAP due to surveillance by more than two iSGs
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.3 .1.2.n
ISG_DA P_LINK
1-15
EMPTY
Major
EMPTY
EMPTY
The SPA will initiate a surveillance audit automatically. If the problem occurs again, analyze DAP configuration from OMC. The SPA will initiate a surveillance audit automatically. If the problem occurs again, analyze DAP configuration from OMC.
R N
R N
3111
iSG surveillance start rejected due to other reason
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.3 .1.2.n
ISG_DA P_LINK
1-15
Reject code: <number>
Major
EMPTY
EMPTY
EMPTY
R N
U The system will not be able to provide surveillance for an IMSI for which it received the error. Surveillance capacity in DAP may have been exceeded. U The system will not be able to provide surveillance for an IMSI for which it received the error. DAP has recognized a possible error in configuring surveillance provisioning system. U The system will not be able to provide surveillance for an IMSI for which it received the error. DAP has recognized a possible error in surveillance provisioning within the
October 30, 2008
iSG-3

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 3112 SPA Link version failure 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.4 .1.0 ISG_SP A_LINK 1 Timeout waiting for Link Version Request on SPA-initiated connection Incompatible version on SPA initiated connection. Link Version Check passed on SPA initiated connection after previous failure. Bad Value for OID:<object_i d> Time Difference between NMS and NE exceeds maximum difference for synchronizatio n <FRU> failed. Major EMPTY EMPTY Verify that SPA is operational. R N
Comments & Notes
system. U Ability to provision iSG with surveillance information impaired.
3112
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.4 .1.0 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.2.4 .1.0
ISG_SP A_LINK
Major
EMPTY
EMPTY
3112
ISG_SP A_LINK
Clear
EMPTY
EMPTY
Upgrade the iSG and/or SPA software to versions that support compatible link protocols. EMPTY
R N
U Ability to provision iSG with surveillance information impaired.
C N
U Ability to provision iSG with surveillance information restored.
100012
100013
Bad Value returned in the Configuration File Time Synchronization Cannot Be Done
1.3.6.1.4.1. 161.3.3.10. 2.14.1.1.0 1.3.6.1.4.1. 161.3.3.10. 2.6.1.0
CA_BAD VAL_AL M CA_SNT P_ALM
Major
EMPTY
EMPTY
Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance.
R N
Major
EMPTY
EMPTY
R N
M Bad Value returned in the Configuration File. Applies to ATCA-ISG only. M The time difference between the NMS and the NE was larger than the maximum value for automatic synchronization to be completed. Applies to ATCA-ISG only. U iSG LEM FRU has failed. iSG cannot communicate to LEMs. U Take the installed HSSI card out and put in one with the correct HSSI version. iSG can still perform surveillance in situations where voice surveillance is not provisioned. This alarm will not be reported in final NGD. N A hardware failure has
3201
FRU failure
3202
Hardware Configuration Error
1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.1.2 .0 1.3.6.1.4.1. 161.3.3.10. 5.10.1.1.1.2 .0
ISG_FR U_IO
Major
EMPTY
EMPTY
Replace the FRU that failed.
R N
ISG_FR U_IO
HSSI Hardware Configuration Error
Major
EMPTY
EMPTY
If necessary, replace the respective hardware unit
R N
equipmentF
33305
SCSI Device
1.3.6.1.4.1.
ISG_SC
HARD_DISK
Critical
EMPTY
607-612
Contact Customer
R N
iSG-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
ailureEvent
Disabled
161.3.3.10. 5.7.1.1.2.3. 1.6.317.1.1. 1.<Instance >
SI_ALM
33309
TOY_CLOCK device disabled
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.325.1.1. 1.<Instance > 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.324.1.1. 1.<Instance >
ISG_TO Y_CLOC K_ALM
33310
ISG_DE V_TEMP
1-7
33326
SYSTEM BUS Disabled
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.311.1.1. 1.<Instance >
ISG_CP U_ALM
33333
Latch Open
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.311.1.1. 1.<Instance >
ISG_CP U_ALM
1-2
DeviceType <DeviceTypeI d> Device Id <DeviceID> <Enabled or Disabled or Impaired> TOY_CLOCK DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled> DEV_TEMP DeviceType <DeviceTypeI d> Device Id <DeviceID> <Enabled or Disabled or Impaired> SYSTEM_BU S DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Impaired or Enabled> Latch Open <id>
Network Resolution Center for assistance.
Y C / l N e a r C
Comments & Notes
occurred. Applies to ATCA-ISG only.
Critical
EMPTY
EMPTY
Critical
EMPTY
EMPTY
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Contact the iDEN Customer Network Resolution Center for assistance
R N C
N This alarm is not supported and will be removed from this document in a future release. Applies to ATCA-ISG only. N A hardware failure has occurred. Applies to ATCA-ISG only.
R N C
Critical
EMPTY
EMPTY
R N C
N A hardware failure has occurred. ATCA iSG instance is 1. Applies to ATCA-ISG only.
Critical
EMPTY
EMPTY
33330
Timezone Failure
33331
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.310.1.1. 1.<Instance > 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3.
ISG_AP P_ALM
Major
EMPTY
EMPTY
Check if latch is closed for the front blade and the rear transition blade. If problem persists contact iDEN Customer Network Resolution Center for assistance Contact Customer Network Resolution Center for assistance.
R N C
N Close the latch to clear the condition. Applies to ATCA-ISG only.
R N C
N Timezone is set based on configuration downloaded from OMCR. Applies to ATCA-ISG only. N Voltage Level Outside of given threshold range. Applies to ATCA-ISG
ISG_CP U_ALM
1-17
Voltage Device <id> Outside
Critical
EMPTY
EMPTY
R N C
October 30, 2008
iSG-5

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r 1.6.311.1.1. 1.<Instance > 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.311.1.1. 1.<Instance > 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.320.1.1. 1.<Instance > Operating Range ISG_CP U_ALM 1-2 IPMI Controller <id> <Disabled or Enabled> E-Net id=<value>, name=<text_d esc> is <Enabled or Impaired or Disabled> Critical EMPTY EMPTY Contact the iDEN Customer Situation Center for assistance. R N C
Comments & Notes
only.
33332
N IPMI controller is not operational. Applies to ATCA-ISG only.
33301
Ethernet Link Down
ISG_NIO C_ALM
1-5
Critical
EMPTY
iSG_HW_C ONTAINER : 601605,622 iSG_NIOC: 607-612
33334
33335
33337
33324
Memory Disabled
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.310.1.1. 1.<Instance > 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.330.1.1. 1.<Instance > 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.310.1.1. 1.<Instance > 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3.
ISG_AP P_ALM
Critical
EMPTY
EMPTY
Check for the following in the chassis: 1) Both switch blades (SSC) should be installed in the chassis 2) One Ethernet port on the RTM should be connected to LEM network. If the chassis and the blade are configured as per the configuration given above and if this alarm is still seen, contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Situation Center for assistance.
R N C
N Ethernet Link is enabled or impaired or disabled. This alarm is used to detect the Ethernet link connection failure. Applies to ATCA-ISG only.
R N C
ISG_LM_ ALM
Missing Object Files for Hardware Type <HWtype> Failure <type> at initialization
Critical
EMPTY
EMPTY
R N
N This alarm is not supported and will be removed from this document in a future release. Applies to ATCA-ISG only. N Update Loads on OMC to versions that not support the hardware version installed. Applies to ATCA-ISG only. N This alarm is not supported and will be removed from this document in a future release. Applies to ATCA-ISG only. N A hardware failure has occurred. An alarm indicating enabled state
ISG_AP P_ALM
Critical
EMPTY
EMPTY
R Y C
ISG_CP U_ALM
MEMORY DeviceType <DeviceTypeI
Critical
EMPTY
EMPTY
Contact the iDEN Customer Network Resolution Center for
R N C
iSG-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r 1.6.311.1.1. 1.<Instance > d> Device Id <DeviceID> <Disabled or Impaired or Enabled> assistance
Comments & Notes
33340
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.330.1.1. 1.<Instance > 1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.311.1.1. 1.<Instance >
ISG_LM_ ALM
<reason>
Critical
EMPTY
EMPTY
R Y C
33323
ISG_CP U_ALM
1-99
DISK VOLUME DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled>
Critical
EMPTY
EMPTY
R N C
of HW Device Memory is sent when memory is available, which is CLEAR alarm for HW DEVICE MEMORY. An alarm indicating impaired state of HW Device Memory is sent when total Memory decreased from last reboot or % mem used over alarm threshold (default = 85%), which is SET alarm for HW DEVICE MEMORY. An alarm indicating disabled state of HW Device Memory is sent when % mem used over recovery threshold (default = 90%) or total memory less than minimum required by config, which is SET alarm for HW DEVICE MEMORY also. In some scenarios, there can be one CLEAR alarm for more than one corresponding SET alarms. Applies to ATCA-ISG only. N Software Upgrade Failure. Where: <reason> displays different reasons for different failure scenarios. Applies to ATCA-ISG only. N A hardware failure has occurred. 99 is the maximum instance of instance. The real instance of VOLUME is decided during run-time, which is around 20. Applies to ATCA-ISG only.
October 30, 2008
iSG-7

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
33312
1.3.6.1.4.1. 161.3.3.10. 5.7.1.1.2.3. 1.6.310.1.1. 1.<Instance >
ISG_AP P_ALM
<File system name> File System Set Excessive at <%> utilization
Critical
EMPTY
EMPTY
Comments & Notes
N The reported file system is almost full. WHERE: <file system name> ={ a string containing the file system name (mount point with path)}, <% utilization> = {current utilization % 0 - 100%}. Applies to ATCA-ISG only.
iSG-8
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 0 1 1 0 2 1 0 3 1 0 5 1 3 7 1 3 8 1 0 7 1 0 8 1 4 6 1 3 2 1 4 2
DAP LINK DOWN SM LINK DOWN
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-A
U-EImp U-EImp
207
3101R
iSG loses connectivity on first iSG-DAP link. iSG loses connectivity on iSGSM link (Only in Mixed Mode).
S t a t u s N U
ISG_STATE
U-E-A
303, 304, 305
EMPTY
N U
SPA CONNECT FAILED ALL DAP LINKS DOWN LEM CARRIER FAILURE LEM FRU FAILURE RESET FROM OMC
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-A
U-EImp U-E-Idl
EMPTY
2901R, 3102R 3101R
N U
iSG cannot perform surveillance for subjects assigned to this DAP. iSG cannot perform voice surveillance for subjects. Final NGD will not have SM link rolled up to node state. iSG cannot be provisioned with surveillance information. iSG cannot perform surveillance for any subjects. iSG cannot distribute surveillance information to LEM. iSG cannot distribute surveillance information to LEM. iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. Not implemented.
ISG_STATE
U-E-A
207
iSG loses connectivity on all iSG-DAP links. LEM physical connection is lost.
N U
ISG_STATE
U-E-A
U-E-Idl
EMPTY
EMPTY
N U
ISG_STATE
U-E-A
U-DIdl L-E-Idl
EMPTY
3201R
LEM Ethernet card failure.
N U
ISG_STATE
U-E-A
EMPTY
EMPTY
Reset command from OMC-R. iSG will start load shedding.
Y U
INTERNAL RESET
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-A
L-E-Idl
EMPTY
RESET FROM LMT
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-A
L-E-Idl
EMPTY
3103R (Critical), 3104R (Critical) EMPTY
iSG has reset itself due to internal failure. iSG will start load shedding. Reset command from LMT.
Y U
Y U
LOCK FROM OMC LOCK FROM LMT
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-A
L-E-Idl
EMPTY
EMPTY
Lock command from OMC-R. iSG will start load shedding. Lock command from LMT.
Y U
ISG_STATE
U-E-A
L-E-Idl
EMPTY
EMPTY
Y U
iSG can continue to provide surveillance information for active calls for maximum of 10
October 30, 2008
iSG-9

State Changes
R e a s o n C o d e
Release SR17.0
To State
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 0 9
ISG FULLY FUNCTION AL
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-EImp
U-E-A
206, 302
3101C, 3102C
1 1 0 1 1 1 1 1 2 1 1 4 1 1 5 1 1 6 1 1 8 1 3 9 1 4 0 1 2 0 1 2
DAP LINK DOWN SM LINK DOWN
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-EImp U-EImp
U-EImp U-EImp
207
3101R
All configured iSG-DAP and all iSG-SM (Only in Mixed Mode) links fully functional. iSG is fully functional. iSG initiated SPA connection is fully functional. The LEM Carrier Link is established. This also means that the Hardware Container is active. iSG loses connectivity on an iSG-DAP link. iSG loses connectivity on iSGSM link (Only in Mixed Mode).
N U
minutes. iSG capable of performing all types of surveillance.
N U
ISG_STATE
303, 304, 305
EMPTY
N U
SPA CONNECT FAILED DAP LINK UP SM LINK UP
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-EImp
U-EImp
EMPTY
2901R, 3102R
N U
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-EImp U-EImp
U-EImp U-EImp
206
3101C
ISG_STATE
302
EMPTY
SPA CONNECT SUCCEEDE D ALL DAP LINKS DOWN LEM CARRIER FAILURE LEM FRU FAILURE RESET FROM OMC
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-EImp
U-EImp
EMPTY
3102C
iSG establishes connectivity on an iSG-DAP link. Other failure conditions exist. iSG establishes connectivity on iSG-SM link (Only in Mixed Mode). Other failure conditions exist. iSG initiated SPA connection is fully functional. Other failure conditions exist. iSG loses connectivity on all iSG-DAP links. LEM physical connection is lost.
N U
iSG cannot perform surveillance for subjects assigned to this DAP. iSG cannot perform voice surveillance for subjects. Final NGD will not have SM link rolled up to node state. This state change will not be reported if the SPA connection is previously unavailable. iSG can perform surveillance for subjects assigned to this DAP. iSG can perform voice surveillance for subjects. Final NGD will not have SM link rolled up to node state. iSG can be provisioned with surveillance information.
N U
N U
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-EImp U-EImp U-EImp U-EImp
U-E-Idl
207
3101R
N U
iSG cannot perform surveillance for any subjects. iSG cannot distribute surveillance information to LEM. iSG cannot distribute surveillance information to LEM. iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. iSG can continue to provide surveillance information for
ISG_STATE
U-E-Idl
EMPTY
EMPTY
N U
ISG_STATE
U-DIdl L-E-Idl
EMPTY
3201R
LEM Ethernet card failure.
N U
ISG_STATE
EMPTY
EMPTY
Y U
INTERNAL RESET
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-EImp
L-E-Idl
EMPTY
3103R (Critical),
iSG has reset itself due to internal failure. iSG will start
Y U
iSG-10
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 esmrStateCh angeEvent 1 4 7 1 3 3 1 4 3 1 2 2 RESET FROM LMT 1.3.6.1.4.1.161.3. 3.10.2.3.1.0 ISG_STATE 1 U-EImp L-E-Idl EMPTY
3104R (Critical) EMPTY
load shedding. Reset command from LMT. Y U
LOCK FROM OMC LOCK FROM LMT
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-EImp U-EImp
L-E-Idl
EMPTY
EMPTY
Lock command from OMC-R. iSG will start load shedding. Lock command from LMT.
Y U
active calls for maximum of 10 minutes. iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. Not implemented.
ISG_STATE
L-E-Idl
EMPTY
EMPTY
Y U
ISG FULLY FUNCTION AL
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-Idl
U-E-A
206, 302
3101C, 3102C
1 2 3 1 5 0 1 4 1 1 2 5 1 2 6 1 4 8 1 3 4
DAP LINK UP LEM CARRIER SUCCESS LEM FRU FAILURE RESET FROM OMC
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-Idl
U-EImp U-EImp
206
3101C
ISG_STATE
U-E-Idl
EMPTY
EMPTY
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-Idl
U-DIdl L-E-Idl
EMPTY
3201R
All configured iSG-DAP and all iSG-SM (Only in Mixed Mode) links fully functional. iSG is fully functional. iSG initiated SPA connection is fully functional. The LEM Carrier Link is established. This also means that the Hardware Container is active. iSG establishes first iSG-DAP link connection and the LEM Carrier Link is established. iSG establishes the LEM Carrier Link and at least one but not all iSG-DAP links are connected. LEM Ethernet card failure.
N U
iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. iSG capable of performing all types of surveillance.
N U
iSG can perform surveillance for subjects assigned to this DAP. iSG can distribute surveillance information to LEM.
N U
N U
iSG cannot distribute surveillance information to LEM. iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. Not implemented.
ISG_STATE
U-E-Idl
EMPTY
EMPTY
Y U
INTERNAL RESET
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-Idl
L-E-Idl
EMPTY
RESET FROM LMT
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-Idl
L-E-Idl
EMPTY
iSG has reset itself due to internal failure. iSG will start load shedding. Reset command from LMT.
Y U
Y U
LOCK FROM OMC
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-Idl
L-E-Idl
EMPTY
EMPTY
Lock command from OMC-R. iSG will start load shedding.
Y U
October 30, 2008
iSG-11

State Changes
R e a s o n C o d e
Release SR17.0
To State
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 4 4 1 2 7 1 2 8 1 2 9 1 4 9 1 3 5 1 4 5 1 3 0 2 0 6 2 0 7 3 0 1 3 0 2
LOCK FROM LMT
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-Idl
L-E-Idl
EMPTY
EMPTY
Lock command from LMT.
S t a t u s Y U
ISG ENABLED RESET FROM OMC
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-DIdl U-DIdl
U-E-Idl
EMPTY
EMPTY
The LEM FRU is fully functional. Reset command from OMC-R. The iSG will reset immediately as there are no active calls to service. iSG has reset itself due to internal failure. The iSG will reset immediately as there are no active calls to service. Reset command from LMT.
N U
iSG can continue to provide surveillance information for active calls for maximum of 10 minutes. iSG cannot distribute surveillance information to LEM. iSG processing functionality is interrupted until recovery.
ISG_STATE
L-D-Idl
EMPTY
EMPTY
Y U
INTERNAL RESET
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-DIdl
L-D-Idl
EMPTY
RESET FROM LMT LOCK FROM OMC LOCK FROM LMT LOAD SHEDDING COMPLETE LOGICAL LINK UP LOGICAL LINK DOWN PHYSICAL LINK ENABLED PHYSICAL LINK UP
1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.2.3.1.0 1.3.6.1.4.1.161.3. 3.10.5.10.1.1.2.3. 1.2.n 1.3.6.1.4.1.161.3. 3.10.5.10.1.1.2.3. 1.2.n 1.3.6.1.4.1.161.3. 3.10.5.10.1.1.2.9. 1.0 1.3.6.1.4.1.161.3. 3.10.5.10.1.1.2.9. 1.0
ISG_STATE
U-DIdl U-DIdl U-DIdl L-E-Idl
L-D-Idl
EMPTY
Y U
iSG processing functionality is interrupted until recovery.
Y U
iSG processing functionality is interrupted until recovery. Not implemented.
ISG_STATE
L-D-Idl
EMPTY
EMPTY
Lock command from OMC-R. (iSG will not load shed.) Lock command from LMT.
Y U
ISG_STATE
L-D-Idl
EMPTY
EMPTY
Y U
iSG processing functionality is interrupted until recovery. iSG processing functionality is interrupted until recovery. iSG can perform surveillance for subjects assigned to this DAP. iSG cannot perform surveillance for subjects assigned to this DAP. iSG can establish a physical link to SM (only in Mixed Mode). Final NGD will not have this state change. iSG can provide voice surveillance. This state change is only possible in Mixed Mode. Final NGD will not have this state change. iSG cannot perform voice surveillance for subjects. Final NGD will not have this state change. iSG cannot perform voice
ISG_STATE
L-D-Idl
EMPTY
EMPTY
ISG_DAP_LIN K ISG_DAP_LIN K ISG_SM_LIN K
1-15
U-DIdl U-E-A
U-E-A
EMPTY
3101C
1-15
U-DIdl U-E-Idl
EMPTY
EMPTY
Load shedding complete due to all active calls processed or reset guard timer expired. TCP/IP connectivity established and Link Version Check Procedure passed. TCP/IP connectivity lost or Link Continuity Check failed. I/O FRU is operational but no physical connectivity.
Y U
N U
N U
U-DIdl
EMPTY
EMPTY
N U
ISG_SM_LIN K
U-E-Idl
U-E-A
EMPTY
EMPTY
Physical connectivity established.
N U
3 0 3 3
PHYSICAL LINK DISABLED PHYSICAL
1.3.6.1.4.1.161.3. 3.10.5.10.1.1.2.9. 1.0 1.3.6.1.4.1.161.3.
ISG_SM_LIN K
U-E-Idl
U-DIdl
EMPTY
EMPTY
Internal FRU failure.
N U
esmrStateCh
ISG_SM_LIN
U-E-A
U-D-
EMPTY
EMPTY
Internal FRU failure.
N U
iSG-12
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 4 3 0 5 6 0 1
LINK DISABLED PHYSICAL LINK DOWN HW CONTAINE R RESTORED FULL FUNCTION ALITY HW CONTAINE R LOST FULL FUNCTION ALITY
3.10.5.10.1.1.2.9. 1.0 1.3.6.1.4.1.161.3. 3.10.5.10.1.1.2.9. 1.0 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.101.<UANC>.
Idl
ISG_SM_LIN K
U-E-A
U-E-Idl
EMPTY
EMPTY
Physical connectivity lost.
N U
ISG_HW_CO NTAINER
U-DIdl
U-E-A
EMPTY
6 0 2
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.101.<UANC>.
ISG_HW_CO NTAINER
U-E-A
U-DIdl
EMPTY
6 0 3
HW CONTAINE R LOST PARTIAL FUNCTION ALITY
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.101.<UANC>.
ISG_HW_CO NTAINER
U-E-A
U-EImp
EMPTY
6 0 4
HW CONTAINE R LOST FULL FUNCTION ALITY
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.101.<UANC>.
ISG_HW_CO NTAINER
U-EImp
U-DIdl
EMPTY
6 0 5
HW CONTAINE R RESTORED PARTIAL FUNCTION ALITY
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.101.<UANC>.
ISG_HW_CO NTAINER
U-DIdl
U-EImp
EMPTY
33301, 33305, 33309, 33310, 33326, 33331, 33332, 33333 33301, 33305, 33309, 33310, 33326, 33331, 33332, 33333 33301, 33305, 33309, 33310, 33326, 33331, 33332, 33333 33301, 33305, 33309, 33310, 33326, 33331, 33332, 33333 33301, 33305, 33309, 33310, 33326, 33331, 33332, 33333
HW Container has become operational.
N N
surveillance for subjects. Final NGD will not have this state change. iSG can establish a physical link to SM (only in Mixed Mode). Final NGD will not have this state change. HW Container has become operational. MOC=101. Applies to ATCA-ISG only.
N N
HW Container functionality has been lost.MOC=101. Applies to ATCA-ISG only.
HW Container has partially failed.
N N
HW Container has partially failed - one or more FRUs are not operational. MOC=101. Applies to ATCA-ISG only.
N N
HW Container functionality has been lost.MOC=101. Applies to ATCA-ISG only.
N N
Operation of HW Container is partially restored. Still one or more FRUs, but not all of FRUs of the same fru type, are failed. MOC=101. Applies to ATCAISG only.
October 30, 2008
iSG-13

State Changes
R e a s o n C o d e
Release SR17.0
To State
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
6 2 2
HW CONTAINE R RESTORED FULL FUNCTION ALITY MISCELLA NEOUS CONTAINE R FULLY OPERATIO NAL MISCELLA NEOUS CONTAINE R FULLY OPERATIO NAL MISCELLA NEOUS CONTAINE R FAILURE
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.101.<UANC>.
ISG_HW_CO NTAINER
U-EImp
U-E-A
EMPTY
6 0 6
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.107.<UANC>.
ISG_MISC
U-EImp
U-E-A
EMPTY
6 1 3
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.107.<UANC>.
ISG_MISC
U-DIdl
U-E-A
EMPTY
6 1 5
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.107.<UANC>.
ISG_MISC
U-E-A
U-DIdl
EMPTY
6 1 7
6 1 9
MISCELLA NEOUS CONTAINE R PARTLY OPERATIO NAL MISCELLA NEOUS CONTAINE R FAILURE
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.107.<UANC>.
ISG_MISC
U-E-A
U-EImp
EMPTY
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.107.<UANC>.
ISG_MISC
U-EImp
U-DIdl
EMPTY
6 2 1
MISCELLA NEOUS CONTAINE R PARTLY OPERATIO NAL FRU RESTORED
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.107.<UANC>.
ISG_MISC
U-DIdl
U-EImp
EMPTY
33301, 33305, 33309, 33310, 33326, 33331, 33332, 33333 33309, 33310, 33326, 33331, 33332, 33333 33309, 33310, 33326, 33331, 33332, 33333 33309, 33310, 33326, 33331, 33332, 33333 33309, 33310, 33326, 33331, 33332, 33333 33309, 33310, 33326, 33331, 33332, 33333 33309, 33310, 33326, 33331, 33332, 33333 33301
All HW Container's FRUs are fully operational
S t a t u s N N
All HW Container's FRUs are fully operational. MOC=101. Applies to ATCA-ISG only.
Miscellaneous components are fully operational
N N
Miscellaneous Container's FRUs(power, fan, cpu) are fully operational. MOC=107. Applies to ATCA-ISG only.
Miscellaneous components (Temperature, Hardware Clock Battery, Memory, System Bus, Voltage Levels, Latch, IPMI controller) are fully operational All miscellaneous components are no longer operational
N N
Miscellaneous Container's FRUs(power, fan,cpu) has become operational. MOC=107. Applies to ATCA-ISG only.
N N
Miscellaneous Container(power, fan, cpu) functionality has been lost. MOC=107. Applies to ATCA-ISG only.
N N
Miscellaneous Container(power, fan, cpu) has partially failed one or more FRUs are not operational. MOC=107. Applies to ATCA-ISG only. All Miscellaneous Container's FRUs(power, fan, cpu) has become non-operational. MOC=107. Applies to ATCAISG only. Operation of Miscellaneous Container(power, fan, cpu) is partially restored. Still one or more FRUs but not all of FRUs of the same fru type, are failed. MOC=107. Applies to ATCAISG only. FRUs has become fully operational. NIOC: MOC=105
N N
N N
6 0
1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1.
ISG_NIOC
U-DIdl
U-E-A
EMPTY
N N
iSG-14
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
6 0 8
FULL FUNCTION ALITY FRU LOST FUNCTION ALITY
4.105.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.105.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.105.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.105.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.105.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.105.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.104.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.104.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.104.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.104.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. ISG_NIOC 1 U-E-A U-DIdl EMPTY 33301 FRU has become nonoperational N N
Instance=1-3. Applies to ATCAISG only. FRUs has become nonoperational or have been removed. NIOC: MOC=105 Instance=1-3. Applies to ATCAISG only. FRUs has become partial operational. NIOC: MOC=105 Instance=1-3. Applies to ATCAISG only. FRUs has become operational. NIOC: MOC=105 Instance=1-3. Applies to ATCA-ISG only. FRUs has become partial operational. NIOC: MOC=105 Instance=1-3.Applies to ATCAISG only. FRUs has become nonoperational or have been removed. NIOC: MOC=105 Instance=1-3. Applies to ATCAISG only. FRUs has become operational. SCSI: MOC=104 Instance=1. Applies to ATCA-ISG only.
6 0 9
6 1 0 6 1 1 6 1 2
FRU RESTORED PARTIAL FUNCTION ALITY FRU RESTORED FUNCTION ALITY FRU LOST PARTIAL FUNCTION ALITY FRU LOST FUNCTION ALITY
ISG_NIOC
U-DIdl
U-EImp
EMPTY
33301
N N
ISG_NIOC
U-EImp
U-E-A
EMPTY
33301
N N
ISG_NIOC
U-E-A
U-EImp
EMPTY
33301
N N
ISG_NIOC
U-EImp
U-DIdl
EMPTY
33301
FRU has become nonoperational
N N
6 0 7
6 0 8
FRU RESTORED FULL FUNCTION ALITY FRU LOST FUNCTION ALITY
ISG_SCSI
U-DIdl
U-E-A
EMPTY
33305
N N
ISG_SCSI
U-E-A
U-DIdl
EMPTY
33305
FRU has become nonoperational
N N
6 0 9
6 1 0 6 1
FRU RESTORED PARTIAL FUNCTION ALITY FRU RESTORED FUNCTION ALITY FRU LOST PARTIAL
ISG_SCSI
U-DIdl
U-EImp
EMPTY
33305
N N
FRUs has become nonoperational or have been removed. SCSI: MOC=104 Instance=1. Applies to ATCAISG only. FRUs has become partial operational SCSI: MOC=104 Instance=1. Applies to ATCAISG only. FRUs has become operational. SCSI: MOC=104 Instance=1. Applies to ATCA-ISG only. FRUs has become partial operational. SCSI: MOC=104
ISG_SCSI
U-EImp
U-E-A
EMPTY
33305
N N
ISG_SCSI
U-E-A
U-EImp
EMPTY
33305
N N
October 30, 2008
iSG-15

State Changes
R e a s o n C o d e
Release SR17.0
To State
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 esmrStateCh angeEvent 6 1 2
FUNCTION ALITY FRU LOST FUNCTION ALITY
4.104.<UANC>. 1.3.6.1.4.1.161.3. 3.10.5.7.1.1.2.5.1. 4.104.<UANC>. 1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_SCSI
U-EImp
U-DIdl
EMPTY
33305
FRU has become nonoperational.
N N
1 6 0
1 6 1
1 6 2
ISG LOST PARTIAL HW CONTAINE R FUNCTION ALITY ISG LOST FULL HW CONTAINE R FUNCTION ALITY ISG NOT FULLY FUNCTION AL
ISG_STATE
U-E-A
U-EImp
EMPTY
EMPTY
HW Container has partially failed while iSG is in active state.
N N
Instance=1. Applies to ATCAISG only. FRUs has become nonoperational or have been removed. SCSI: MOC=104 Instance=1. Applies to ATCAISG only. HW Container has partially failed - one or more FRUs are not operational. Applies to ATCA-ISG only.
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-E-A
U-EImp
EMPTY
EMPTY
Critical HW Container functionality has been lost while iSG is active.
N N
HW Container functionality has been lost. Applies to ATCA-ISG only.
1.3.6.1.4.1.161.3. 3.10.2.3.1.0
ISG_STATE
U-EImp
U-EImp
EMPTY
EMPTY
HW Container state change while iSG is in impaired state (not all iSG-DAP links are connected or SPA is not connected)
N N
HW container gained or lost functionality when the iSG is not fully operational. Applies to ATCA-ISG only.
iSG-16
October 30, 2008
Release SR17.0
__________________________________ Events
Event Type
Reason Code
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N ) N
Availability Trap
EMPTY
Restart Trap
EMPTY
actionStat usEvent
<universal time>-<sequence number>-<secondary id>-<new mode>-<time of switch>-<reason code>-<old mode>-<additional text>-<reason text> New Operate State: <operational state> New Usage State: <usage state> New Admin State: <administrative state> System ROM Version: <boot ROM version> System Load Version: <software Load version> System DB Version: <database version> System Code Version: <code version> Description: <system description> System Reset Reason: <latest reset reason> System Outage Time: <outage time since latest reset> System Reboot Time: <reboot time> System Boot Diagnostics: <boot diagnostics> Background Download Aborted
EMPTY
ISG
EMPT Y
EMPT Y
EMPTY
EMPTY
Event is generated when the iSG's availability mode state changes.
Comments & Notes
EMPTY
1.3.6.1.4.1. 161.3.3.10. 2.3.1.0
ISG_STA TE
EMPT Y
EMPT Y
EMPTY
EMPTY
This event is used to inform the OMC whenever iSG switches its application code load or when it reboots. It also tells the OMC that SNMP agent is operational and is ready to handle request.
N U
EMPTY
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
ISG
Empty
Empty
Empty
Empty
actionStat usEvent
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
ISG
Empty
Empty
Empty
Empty
Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details.
N N
Applies to ATCA-ISG only.
N N
October 30, 2008
iSG-17

Event Type
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Event Description
O u t a g e ( Y / N ) N
actionStat usEvent
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
ISG
Empty
Empty
Empty
Empty
actionStat usEvent actionStat usEvent
Background Download Aborted Successfully Background Download Switch Aborted
1.3.6.1.4.1. 161.3.3.10. 2.10.1.2.0 1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
ISG
Empty
Empty
Empty
Empty
ISG
Empty
Empty
Empty
Empty
actionStat usEvent
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
ISG
Empty
Empty
Empty
Empty
actionStat usEvent
Background Download Switch Completed Successfully
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
ISG
Empty
Empty
Empty
Empty
actionStat usEvent
Upgrade Aborted
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0
ISG
Empty
Empty
Empty
Empty
actionStat usEvent
Upgrade Failed
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0
ISG
Empty
Empty
Empty
Empty
actionStat usEvent
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0
ISG
Empty
Empty
Empty
Empty
Action Status
0x90
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
ISG
EMPT Y
EMPT Y
EMPT Y
EMPTY
EMPTY
Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download abort (bgdlAbort) is successful. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. A LMT or UNIX user has logged in. See the Action Status Information for details
C h a n g e S t a t u s N
Comments & Notes
N N
Applies to ATCA-ISG only. Applies to ATCA-ISG only.
N N
N N
N N
N N
N N
N N
N N
action status information includes the following
iSG-18
October 30, 2008
Release SR17.0
Event Type
Reason Code

Event Description
O u t a g e ( Y / N )
Comments & Notes
Action Status
0x91
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
ISG
EMPT Y
EMPT Y
EMPT Y
EMPTY
EMPTY
N N
Action Status
0x92
Session timed-out
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
ISG
EMPT Y
EMPT Y
EMPT Y
EMPTY
EMPTY
N N
Action Status
0x94
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
ISG
EMPT Y
EMPT Y
EMPT Y
EMPTY
EMPTY
N N
information: reason code <user login name> <access level> login. Applies to ATCA-ISG only. action status information includes the following information: reason code <user login name> <access level> logout. Applies to ATCA-ISG only. action status information includes the following information: reason code <user login name> <access level> login session timedout. Applies to ATCA-ISG only. action status information includes the following information: reason code <user login name> <access level> login session manually terminated. Applies to ATCA-ISG only.
October 30, 2008
iSG-19
Release SR17.0
iSG-20
October 30, 2008
Release SR17.0
________________________________ Alarms
Alarm Type
Alarm Code
iVPU
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
C h a n g e S Y t / a N t u s N U
Comments & Notes
236057 6
Equipment Fault, Device Removal Detected Communication Fault, Clock Timing Input Failure Device Out of Service : Device Locked Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization,
communicat ionFailureE vent equipmentF ailureEvent
216345 6
65537
210252 9
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.1.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.5.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT
IVPU_AI O
<CORR_TAG> <EID>
Critical
2301952
IVPU_BI TS
IVPU_BP P2
3-17
<CORR_TAG> <EID> Clock Reference Source Failed <CORR_TAG> <EID> Operator Locked Device <CORR_TAG> <EID> Connection to ISB: Frame Pulse Lost Clock A <CORR_TAG> <EID> Connection to ISB: Frame Pulse Lost Clock B <CORR_TAG> <EID> Connection to ISB: Clock A Error <CORR_TAG> <EID> Connection to ISB: Clock A Lost <CORR_TAG> <EID> Connection to ISB: Clock B
Critical
EMPTY
Critical
EMPTY
IVPU_BP P2
3-17
Minor
65537, 2169624
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF
Replace or reseat Hardware.
EMPTY
Check configuration. If recurring, contact CNRC.
R C
N U
EMPTY
Unlock hardware. If recurring, reset hardware. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset
R C
N U
EMPTY
R C
N U
EMPTY
210252 9
IVPU_BP P2
3-17
Minor
65537, 2169624
R C
N U
EMPTY
210252 9
IVPU_BP P2
3-17
Minor
65537, 2169624
R C
N U
EMPTY
210252 9
IVPU_BP P2
3-17
Minor
65537, 2169624
R C
N U
EMPTY
210252 9
IVPU_BP P2
3-17
Minor
65537, 2169624
R C
N U
EMPTY
October 30, 2008
iVPU-1

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
Sever ity Related Alarms Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
C h a n g e S Y t / a N t u s
Comments & Notes
210252 9
210253 0
210253 0
210253 0
210253 0
210253 0
210253 0
210278 4
229888 0
Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Both Connections Lost Processing Fault, Synchronization Processing Fault
_ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> IVPU_BP P2 3-17
Error <CORR_TAG> <EID> Connection to ISB: Clock B Lost <CORR_TAG> <EID> Connection to ISB: Frame Pulse Lost Clock A <CORR_TAG> <EID> Connection to ISB: Frame Pulse Lost Clock B <CORR_TAG> <EID> Connection to ISB: Clock A Error <CORR_TAG> <EID> Connection to ISB: Clock A Lost <CORR_TAG> <EID> Connection to ISB: Clock B Error <CORR_TAG> <EID> Connection to ISB: Clock B Lost <CORR_TAG> <EID> Connection to ISB: No Clock Available <CORR_TAG> <EID> Frame Counter Reprogrammed Minor 65537, 2169624
FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
IVPU_BP P2
3-17
Minor
65537, 2169624
IVPU_BP P2
3-17
Minor
65537, 2169624
IVPU_BP P2
3-17
Minor
65537, 2169624
IVPU_BP P2
3-17
Minor
65537, 2169624
IVPU_BP P2
3-17
Minor
65537, 2169624
IVPU_BP P2
3-17
Minor
65537, 2169624
IVPU_BP P2
3-17
Critical
65537, 2169624
IVPU_BP P2
3-17
Minor
65537
the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the ISB. If recurring under normal conditions, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Self correcting. If recurring, contact CNRC.
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
This alarm will be reported when the BPP2 board received an incorrect
iVPU-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
229888 0
Processing Fault, Synchronization Processing Fault Processing Fault, First System Time Message Not Received Equipment Fault, Hardware Produced Error Equipment Fault, Hardware Produced Error Device Out of Service : Contact Lost Device Out of Service : Contact Lost
230144 0
236083 2
236083 2
communicat ionFailureE vent equipmentF ailureEvent
419430 5
419430 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2.
IVPU_BP P2
3-17
IVPU_BP P2
3-17
IVPU_BP P2
3-17
<CORR_TAG> <EID> System Time Message Missing <CORR_TAG> <EID> System Time Message Not Initialized <CORR_TAG> <EID> PLL Unlocked <CORR_TAG> <EID> Synchronization Loss <CORR_TAG> <EID> Payload Alive Timeout After Initialization <CORR_TAG> <EID> Resource Does Not Register
Minor
65537
Critical
EMPTY
Critical
EMPTY
IVPU_BP P2
3-17
Critical
EMPTY
IVPU_BP P2
3-17
Critical
5243280
IVPU_BP P2
3-17
Critical
5308496, 5243280
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 -
Check ISBs' state. If recurring, contact CNRC.
R C
N U
Contact CNRC.
R C
N U
frame counter in the clock sync message from the ISB. This alarm is reported on CP2 clock to ISB failure. EMPTY
R C
N U
R C
N U
ISB clock failures can trigger this alarm. CP2 clock to ISB failure.
Self correcting. If recurring, contact CNRC.
R C
N U
EMPTY
Self correcting. Check device state.
R C
N U
530841 6
Application Failure
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Critical
EMPTY
N U
This alarm is reported by the SPROC when a device goes out of service. EMPTY
530841 6
Application Failure
IVPU_BP P2
3-17
530841 7
Application Error
IVPU_BP P2
3-17
<CORR_TAG> <EID> Could not initiate codeload for personality change <CORR_TAG> <EID>
Critical
EMPTY
N U
EMPTY
Minor
EMPTY
N U
EMPTY
530841 7
Application Error
IVPU_BP P2
3-17
530843 2
Call Processing Failure
IVPU_BP P2
3-17
<CORR_TAG> <EID> Processor Statistics Collection Impacted <CORR_TAG> <EID>
Minor
EMPTY
N U
EMPTY
Critical
EMPTY
R C
N U
EMPTY
October 30, 2008
iVPU-3

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
530843 3
Call Processing Error
530844 8
General Software Failure
530846 4
Configuration Failure
530848 0
Hardware Component Error
530849 6
Hardware Component Failure
1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID>
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Minor
EMPTY
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Critical
EMPTY
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Critical
EMPTY
IVPU_BP P2
3-17
<CORR_TAG> <EID> HCI Link Loss <CORR_TAG> <EID> Loss of contact - HCI failure on all active links <CORR_TAG> <EID>
Minor
5308496
IVPU_BP P2
3-17
Critical
5308480
0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF EMPTY
In the maintenance window, lock/unlock BPP2. If recurring, reset board. If recurring, contact CNRC. Self correcting. If recurring, contact CNRC.
N U
EMPTY
R C
N U
EMPTY
Verify BPP2 configuration parameters. If recurring, contact CNRC. Check device state. If recurring, reseat DOC3 board. Reseat hardware.
R C
N U
EMPTY
N U
EMPTY
R C
N U
EMPTY
530851 2
Partial Call Processing Capacity Loss Partial Call Processing Capacity Loss Partial Call Processing Capacity Loss Partial Call Processing Capacity Loss Full Call Processing Capacity Loss Switch Processing Error
IVPU_BP P2
3-17
Major
EMPTY
530851 2
IVPU_BP P2
3-17
<CORR_TAG> <EID> Q Overflow, Lvl: <Level>. <CORR_TAG> <EID> Q Overflow.
Clear
EMPTY
In the maintenance window, lock/unlock BPP2. If recurring, reset board. If recurring, contact CNRC. EMPTY
R C
N U
EMPTY
N U
EMPTY
530851 2
IVPU_BP P2
3-17
Minor
EMPTY
EMPTY
N U
EMPTY
530851 2
IVPU_BP P2
3-17
<CORR_TAG> <EID> Q Overflow.
Clear
EMPTY
EMPTY
EMPTY
N U
EMPTY
530852 8
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Critical
EMPTY
530854 4
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Minor
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
R C
N U
EMPTY
In the maintenance window, lock/unlock BPP2. If recurring, reset board. If recurring, contact CNRC.
N U
EMPTY
iVPU-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
530856 0
ISB Link Loss
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID>
IVPU_BP P2
3-17
<CORR_TAG> <EID> ISB slot n, where n=2 or 18
Minor
65537
0x0000 0000 0xFFFF FFFF
This alarm is reported when the CP2 link to theISB is lost. Check the staus of the ISB. If recurring, reseat the BPP2 board. If recurring, contact CNRC.
environment FailureEven t environment FailureEven t processingF ailureEvent
530859 2
High Temperature
530859 3
Very High Temperature
530864 0
Software Initialization Error
530864 0
530864 0
530865 6
Software Initialization Failure
838873 0
BCP CPU Overload Level 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID>
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Minor
EMPTY
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Major
2361088
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Minor
EMPTY
IVPU_BP P2
3-17
IVPU_BP P2
3-17
<CORR_TAG> <EID> Processor Statistics Collection Impacted <CORR_TAG> <EID> Waiting for Personality <CORR_TAG> <EID>
Minor
EMPTY
Minor
EMPTY
IVPU_BP P2
3-17
Critical
EMPTY
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Major
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
Check Fan Trays. Check the ambient air temperature at the site. If recurring, contact CNRC. Check Fan Tray. Check the ambient air temperature at the site. If recurring, contact CNRC. Lock/unlock BPP2 in the maintenance window. If recurring reset board. If recurring, contact CNRC. Lock/unlock BPP2 in the maintenance window. If recurring reset board. If recurring, contact CNRC. Lock/unlock BPP2 in the maintenance window. If recurring reset board. If recurring, contact CNRC. Self correcting. If recurring, contact CNRC.
R C
N U
This alarm is reported when the CP2 link to theISB is lost. Check the staus of the ISB. If recurring, reseat the BPP2 board. If recurring, contact CNRC. EMPTY
R C
N U
EMPTY
N U
EMPTY
N U
EMPTY
N U
EMPTY
R C
N U
EMPTY
R C
N U
qualityOfSer viceFailureE
838873 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2.
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Major
EMPTY
0x0000 0000 -
R C
N U
To self correct, the iVPU will reject new requests for services. If condition persists, operator needs to reduce traffic from sites. (SR872) To self correct, the iVPU shall
October 30, 2008
iVPU-5

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
vent
1.1.1.1.7.<SLOT _ID>
0xFFFF FFFF
838873 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.7.<SLOT _ID>
IVPU_BP P2
3-17
<CORR_TAG> <EID>
Major
EMPTY
R C
N U
229708 8
Invalid Configuration Data Loaded Device Out of Service : Device Locked Communication Fault, Electronic ID 1 wire Bus Connection no. 1..20
65537
209920 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 2.1.1.1.<DEV_ID > 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C ABINET_ SENSOR IVPU_C CA
1-5
<CORR_TAG> <EID> <obj class attribute> <CORR_TAG> <EID> Operator Locked Device <CORR_TAG> <EID> <Device Name> <#>
Major
EMPTY
1,19
Critical
EMPTY
IVPU_C CA
1,19
Minor
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
Check config.
R C
N U
request to stop new services. If condition persists, operator needs to reduce traffic from sites. (SR872) To self correct, the iVPU shall request to stop new services. If condition persists, operator needs to reduce traffic from sites. (SR872) EMPTY
Unlock hardware.
R C
N U
EMPTY
209920 2
Communication Fault, Electronic ID 1 wire Bus Connection no. 1..20
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
<CORR_TAG> <EID> <Device Name> <#>
Minor
EMPTY
communicat
209920
Communication
1.3.6.1.4.1.161.3
IVPU_C
1,19
<CORR_TAG>
Minor
EMPTY
0x0000
The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a
R C
N M
R C
N M
N M
This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will
iVPU-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
ionFailureE vent
Fault, Electronic ID 1 wire Bus Connection no. 1..20
.3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
CA
<EID> <Device Name> <#>
0000 0xFFFF FFFF
209920 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209920 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209920 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209920 7
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If
R C
N M
R C
N M
R C
N M
R C
N M
be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for
October 30, 2008
iVPU-7

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
209920 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209920 9
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209921 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209921 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209921 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without
R C
N M
R C
N M
R C
N M
R C
N M
R C
N M
disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of
iVPU-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
209921 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209921 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209921 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209921 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209921 7
Communication Fault, Electronic ID
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2.
IVPU_C CA
1,19
<CORR_TAG> <EID> <Device
Minor
EMPTY
0x0000 0000 -
any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID
R C
N M
R C
N M
R C
N M
R C
N M
R C
N M
the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the
October 30, 2008
iVPU-9

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
vent
1 wire Bus Connection no. 1..20
1.1.1.1.1.<SLOT _ID>
Name> <#>
0xFFFF FFFF
209921 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209921 9
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209922 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
Minor
EMPTY
209922 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1, 19
Minor
EMPTY
information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to
R C
N M
R C
N M
R C
N M
R C
N M
EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of
iVPU-10
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
209922 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1, 19
Minor
EMPTY
209922 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1, 19
Minor
EMPTY
210150 5
Communication Fault, Packet Bus Connection no. 1..2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
<CORR_TAG> <EID> Connection to ISB: CP2_A Packet Connection
Major
EMPTY
210150 6
Communication Fault, Packet Bus Connection no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection
210253 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID>
IVPU_C CA
1,19
<CORR_TAG> <EID> Connection to ISB lost <CORR_TAG> <EID> Connection to ISB: Frame Pulse Lost Clock A <CORR_TAG> <EID> Connection to ISB: Frame Pulse Lost Clock B <CORR_TAG> <EID> Connection to ISB: Clock A Error
Major
65537
IVPU_C CA
1,19
Minor
65537, 2169624
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
210253 0
IVPU_C CA
1,19
Minor
65537, 2169624
210253 0
IVPU_C CA
1,19
Minor
65537, 2169624
replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. The alarm is a result of a failure to read the EID information for the related device. If the device is working properly without any other issues, lock/unlock CCA card in the maintenance window. If recurring, contact CNRC to replace the CCA card. This alarm indicates the CP2 link to the ISB is instable. Check the ISB state. If recurring, try reseating the CCA. If recurring, check config. If recurring, reseat hardware. Check ISB's state. If recurring, check config. If recurring, reseat hardware. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring,
R C
N M
R C
N M
R C
N U
communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported if the EID could not be read during initialization of the device or a hot swap. There is a potential for disruption of communication. This alarm will be reported when the CCA loses the CP2 A link to ISB-2.
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
October 30, 2008
iVPU-11

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
210253 0
210253 0
210253 0
229632 0
230195 2
Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Processing Fault, Illegal Configuration Change Configuration Or Customization Error Equipment Fault, Subcomponent Fault Device Out of Service : Contact Lost
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.1.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 2.1.1.3.<DEV_ID > 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 2.1.1.2.<DEV_ID > 1.3.6.1.4.1.161.3
IVPU_C CA
1,19
<CORR_TAG> <EID> Connection to ISB: Clock A Lost <CORR_TAG> <EID> Connection to ISB: Clock B Error <CORR_TAG> <EID> Connection to ISB: Clock B Lost <CORR_TAG> <EID> <obj class attribute> <CORR_TAG> <EID> Invalid Configuration Data Loaded <CORR_TAG> <EID> EID 1-Wire Init Failed <CORR_TAG> <EID> Payload Alive Timeout After Initialization <CORR_TAG> <EID> Resource Does Not Register
Minor
65537, 2169624
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000
IVPU_C CA
1,19
Minor
65537, 2169624
IVPU_C CA
1,19
Minor
65537, 2169624
IVPU_C CA
1,19
Critical
EMPTY
contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the ISB. If recurring under normal conditions, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check configuration. If recurring, contact CNRC.
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
IVPU_C CA
1, 19
Minor
65537
Self correcting. If recurring, check DGBE.
R C
N U
EMPTY
236288 0
IVPU_C CA
1,19
Minor
EMPTY
Contact CNRC.
R C
N U
EMPTY
419430 5
IVPU_C CA
1,19
Critical
5308496, 5243280
R C
N U
419430 5
Device Out of Service : Contact Lost
IVPU_C CA
1,19
Critical
5308496, 5243280
R C
N U
229708 8
Invalid Configuration Data Loaded Invalid Configuration Data Loaded Environmental
IVPU_C ONTROL _RELAY IVPU_C USTOM ER_SEN SOR IVPU_C
1-8
<CORR_TAG> <EID> <obj class attribute> <CORR_TAG> <EID> <obj class attribute> <CORR_TAG>
Major
EMPTY
Reset the device in the maintenance window. If recurring, contact CNRC. Check configuration. If recurring, contact CNRC.
R C
N U
This alarm is reported by the SPROC when a device goes out of service. This alarm is reported by the SPROC when a device goes out of service. EMPTY
229708 8
1-5
Major
EMPTY
R C
N U
EMPTY
environment
242636
1-5
Major
EMPTY
Self correcting. If recurring,
N U
EMPTY
iVPU-12
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
FailureEven t qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent equipmentF ailureEvent
838872 8
Fault, External Sensor Threshold Exceeded Logical Link Down
.3.10.5.19.1.1.2. 2.1.1.2.<DEV_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 4.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 4.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 4.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 4.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
USTOM ER_SEN SOR IVPU_D AP_CON TAINER IVPU_D AP_CON TAINER IVPU_D AP_CON TAINER IVPU_D AP_CON TAINER IVPU_D AP_LINK
<EID>
838872 8
Logical Link Down
838873 7
All DAP Logical Links Down
838873 7
All DAP Logical Links Down
65537
Device Out of Service : Device Locked
1-15
<CORR_TAG> Container State Changed to Impaired <CORR_TAG> Container State Changed to Impaired <CORR_TAG> Container State Changed to Disabled <CORR_TAG> Container State Changed to Disabled <CORR_TAG> Operator Locked Device
Major
65537, 8388637
Clear
65537, 8388637
Critical
65537, 8388637
Clear
65537, 8388637
Critical
EMPTY
0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0000 0000 FFFF FFFF
check hardware. Monitor. If recurring, contact CNRC. Check the link status, try to bring the OOS link back into service. If recurring, contact CNRC. EMPTY
N U
EMPTY
N U
EMPTY
Check the link status, try to bring the OOS link back into service. If recurring, contact CNRC. EMPTY
N U
EMPTY
N U
EMPTY
Unlock DAP link.
N U
65537
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
<CORR_TAG> Operator Locked Device
Clear
EMPTY
0000 0000 FFFF FFFF
EMPTY
N U
838862 5
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
<CORR_TAG> Cannot establish TCP/IP connection.IP Addr: <DAP IP address>
Critical
EMPTY
EMPTY
iVPU will persistently retry the connection. Verify that DAP is operational. Verify IP configuration and iDEN LAN network connectivity.
N U
838862 5
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
<CORR_TAG> Cannot establish TCP/IP connection.IP Addr:
Clear
EMPTY
EMPTY
EMPTY
N U
Operator issued DAP link lock command. iVPU cannot communicate with this DAP. Operator issued DAP link unlock command and iVPU can establish communication with this DAP or this DAP is deleted in OLCC. iVPU cannot communicate with this DAP. This alarm can happen only during first time iVPU-DAP link initialization. This DAP is deleted in OLCC.
October 30, 2008
iVPU-13

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
838862 5
838862 5
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
IVPU_D AP_LINK
1-15
<DAP IP address> <CORR_TAG> Clear DAP Connection Failure alarm. <CORR_TAG> Lost connection with DAP.
Clear
EMPTY
EMPTY
EMPTY
N U
Critical
EMPTY
EMPTY
iVPU will persistently reestablish the connection with this DAP.
N U
communicat ionFailureE vent processingF ailureEvent
838862 5
838862 7
DAP Link Version Check Procedure Failure
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
<CORR_TAG> Lost connection with DAP. <CORR_TAG> Clear DAP Link Version Check Procedure Failure alarm. <CORR_TAG> No response from DAP.
Clear
EMPTY
EMPTY
EMPTY
N U
iVPU can establish TCP/IP connection with this DAP. iVPU lost the communication with this DAP. This alarm can happen only when the iVPUDAP link was previously up. This DAP is deleted in OLCC. iVPU receives the LVCP response from this DAP. This is an expected alarm when a new DAP is added and has not been fully initialized. iVPU cannot communicate with this DAP. This DAP is deleted in OLCC. Configured value from OMC was out of range. No default value is available to be used. Configured value from OMC cannot be used in iVPU. No default value is
IVPU_D AP_LINK
1-15
Clear
EMPTY
EMPTY
EMPTY
N U
838862 7
IVPU_D AP_LINK
1-15
Critical
EMPTY
EMPTY
iVPU will persist with Link Version Check Procedure until it receives a success indication from the DAP. Verify configuration between iVPU and DAP in OMC.
N U
838862 7
DAP Link Version Check Procedure Failure Error in configuration data: Default value unavailable
838863 4
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
<CORR_TAG> No response from DAP. <CORR_TAG> <field> was out of range.
Clear
EMPTY
EMPTY
EMPTY
N U
IVPU_D AP_LINK
1-15
Critical
EMPTY
EMPTY
Analyze and change OMC configuration as needed for this iVPU. iVPU can continue execution and will ignore this DAP. Analyze and change OMC configuration as needed for this iVPU. iVPU can continue execution and will ignore this DAP.
N U
838863 4
Error in configuration data: Default value unavailable
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
<CORR_TAG> <reason string>
Major
EMPTY
EMPTY
N U
iVPU-14
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent
838863 7
DAP link Disabled
838863 7
DAP link Disabled
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
<CORR_TAG> Clear DAP Link Disabled alarm. <CORR_TAG> Logical Link Down.
Clear
EMPTY
EMPTY
EMPTY
N U
IVPU_D AP_LINK
1-15
Critical
EMPTY
EMPTY
Check DAP configuration and state of DAP (e.g. down, up) in OMC.
N U
available to be used. iVPU clears the DAP link disabled alarm for this DAP. iVPU cannot communicate with this DAP. It may be due to OLCC or IP Footprint changes. RFC: There is a minor change in SR15.0 comments & notes to add IP Footprint impact on this alarm. This DAP is deleted in OLCC. iVPU clears the LVCP status field failure alarm for this DAP. iVPU cannot communicate with this DAP.
qualityOfSer viceFailureE vent processingF ailureEvent
838863 7
DAP link Disabled
838864 7
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID
IVPU_D AP_LINK
1-15
<CORR_TAG> Logical Link Down.
Clear
EMPTY
EMPTY
EMPTY
N U
IVPU_D AP_LINK
1-15
838864 7
IVPU_D AP_LINK
1-15
<CORR_TAG> Clear DAP Link Version Check Procedure Failure alarm. <CORR_TAG> Status field indicates failure.
Clear
EMPTY
EMPTY
EMPTY
N U
Critical
EMPTY
EMPTY
838864 7
DAP Link Version Check Procedure Failure DAP Link Version Check Procedure Failure
IVPU_D AP_LINK
1-15
<CORR_TAG> Status field indicates failure. <CORR_TAG> Clear DAP Link Version Check Procedure Failure alarm. <CORR_TAG> Version mismatch.
Clear
EMPTY
EMPTY
Either the iVPU or the DAP must be upgraded to a software load that supports a compatible link protocol version. EMPTY
N U
N U
This DAP is deleted in OLCC. iVPU clears the LVCP version mismatch alarm for this DAP. iVPU cannot communicate with this DAP.
838864 8
IVPU_D AP_LINK
1-15
Clear
EMPTY
EMPTY
EMPTY
N U
838864 8
IVPU_D AP_LINK
1-15
Critical
EMPTY
EMPTY
Status field indicates success, but DAP sends a version to iVPU that iVPU
N U
October 30, 2008
iVPU-15

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
> processingF ailureEvent 838864 8 DAP Link Version Check Procedure Failure DAP Link Version Check Procedure Failure 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID > IVPU_D AP_LINK 1-15 <CORR_TAG> Version mismatch. Clear EMPTY EMPTY
doesn't support. Contact CNRC. EMPTY
N U
This DAP is deleted in OLCC. iVPU clears the LVCP source and destination mismatch in message header alarm for this DAP. iVPU cannot communicate with this DAP.
838864 9
IVPU_D AP_LINK
1-15
<CORR_TAG> Clear DAP Link Version Check Procedure Failure alarm.
Clear
EMPTY
EMPTY
EMPTY
N U
838864 9
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
838864 9
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 4.6.1.1.<DAP_ID >
IVPU_D AP_LINK
1-15
236057 6
Equipment Fault, Device Removal Detected Equipment Fault, Hardware Fault Detected Equipment Fault, Span Port Loopback Failure no. 1
236108 8
236262 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> Source and destination mismatch in message header from DAP. <CORR_TAG> Source and destination mismatch in message header from DAP. <CORR_TAG> <EID>
Critical
EMPTY
EMPTY
Check DAP ID of the iVPU configuration and the iVPU ID of the DAP configuration in the OMC configuration.
N U
Clear
EMPTY
EMPTY
EMPTY
N U
This DAP is deleted in OLCC.
Critical
EMPTY
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Critical
5308592
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
Replace Hardware.
R C
N U
EMPTY
Replace Hardware.
R C
N U
EMPTY
EMPTY
R C
N U
This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity
iVPU-16
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
236262 5
Equipment Fault, Span Port Loopback Failure no. 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236262 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236262 7
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
equipmentF
236262
Equipment Fault,
1.3.6.1.4.1.161.3
IVPU_D
1-2
<CORR_TAG>
Minor
EMPTY
0x0000
EMPTY
N U
will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm
October 30, 2008
iVPU-17

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
ailureEvent
Span Port Loopback Failure no. 5
.3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
GBE
<EID>
0000 0xFFFF FFFF
236262 9
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236263 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236263 1
Equipment Fault, Span Port Loopback Failure
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
0x0000 0000 0xFFFF
EMPTY
R C
N U
indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback
iVPU-18
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
no. 8
D>
FFFF
236263 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236263 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236263 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device
October 30, 2008
iVPU-19

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
236263 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236263 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236263 7
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment
iVPU-20
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
236263 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236263 9
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D>
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Minor
EMPTY
EMPTY
R C
N U
236313 6
Equipment Fault, Span Power Supply Fault Device Out of Service : Device Locked Communication
65537
communicat
210150
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.2.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3
IVPU_D GBE
1-2
<CORR_TAG> <EID>
Major
EMPTY
IVPU_D OC3
33, 38
<CORR_TAG> <EID> Operator Locked Device <CORR_TAG>
Critical
EMPTY
IVPU_D
33, 38
Major
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000
Reseat hardware. Monitor. If recurring, replace hardware Unlock hardware.
R C
N U
malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. This alarm indicates a span port loopback failure fault due to a I/O Device error, or a equipment malfunction. The last two digits of the alarm ID indicates the connection number. The Device capacity will be impacted. EMPTY
R C
N U
EMPTY
Reset the DOC3 board. If
N U
This alarm will
October 30, 2008
iVPU-21

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
ionFailureE vent
Fault, Packet Bus Connection no. 1..2
.3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT
OC3
<EID> Connection to ISB: CP2_A Packet connection 33, 38 <CORR_TAG> <EID> Connection to ISB: CP2_B Packet Connection <CORR_TAG> <EID> Connection to ISB: Frame Pulse Lost Clock A <CORR_TAG> <EID> Connection to ISB: Frame Pulse Lost Clock B <CORR_TAG> <EID> Connection to ISB: Clock A Error <CORR_TAG> <EID> Connection to ISB: Clock A Lost <CORR_TAG> <EID> Connection to ISB: Clock B Error <CORR_TAG> <EID> Connection to ISB: Clock B Lost <CORR_TAG> <EID> Connection to ISB: Frame Pulse Lost Clock A <CORR_TAG> <EID> Connection to ISB: Frame Major 2298880
0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF
recurring, reseat the board. If recurring, contact CNRC.
210150 6
Communication Fault, Packet Bus Connection no. 1..2
IVPU_D OC3
Reset the DOC3 board. If recurring, reseat the board. If recurring, contact CNRC.
R C
N U
210252 9
210252 9
210252 9
210252 9
210252 9
210252 9
210253 0
210253 0
Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization,
IVPU_D OC3
33, 38
Minor
EMPTY
IVPU_D OC3
33, 38
Minor
EMPTY
IVPU_D OC3
33, 38
Minor
EMPTY
IVPU_D OC3
33, 38
Minor
EMPTY
IVPU_D OC3
33, 38
Minor
EMPTY
IVPU_D OC3
33, 38
Minor
EMPTY
IVPU_D OC3
33, 38
Minor
65537
IVPU_D OC3
33, 38
Minor
65537
Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset
R C
N U
be reported when the DOC3 loses the CP2 A link to the ISB. This alarm will be reported when the DOC3 loses the CP2 B link to the ISB. EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
iVPU-22
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
210253 0
210253 0
210253 0
210253 0
210278 4
229888 0
Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Single Connection Lost no. 1..2 Communication Fault, TDM Synchronization, Both Connections Lost Processing Fault, Synchronization Processing Fault
_ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> IVPU_D OC3 33, 38
Pulse Lost Clock B <CORR_TAG> <EID> Connection to ISB: Clock A Error <CORR_TAG> <EID> Connection to ISB: Clock A Lost <CORR_TAG> <EID> Connection to ISB: Clock B Error <CORR_TAG> <EID> Connection to ISB: Clock B Lost <CORR_TAG> <EID> Connection to ISB: No Clock Available <CORR_TAG> <EID> Frame Counter Reprogrammed Minor 65537
FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
IVPU_D OC3
33, 38
Minor
65537
IVPU_D OC3
33, 38
Minor
65537
IVPU_D OC3
33, 38
Minor
65537
IVPU_D OC3
33, 38
Critical
EMPTY
IVPU_D OC3
33, 38
Minor
EMPTY
the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Check the indicated connection to the parent device. If recurrint, reset the FRU. If recurring, contact CNRC. Self correcting. If persists, contact CNRC.
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
229888 0
Processing Fault, Synchronization Processing Fault Processing Fault, First System Time Message Not Received Equipment Fault, Hardware Produced Error
230144 0
236083 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT
IVPU_D OC3
33, 38
IVPU_D OC3
33, 38
IVPU_D OC3
33, 38
<CORR_TAG> <EID> System Time Message Missing <CORR_TAG> <EID> System Time Message Not Initialized <CORR_TAG> <EID> PLL Unlocked
Minor
EMPTY
Critical
EMPTY
Critical
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF
Self correcting. If persists, contact CNRC.
R C
N U
This alarm will be reported when the DOC3 board received an incorrect frame counter in the clock sync message from the ISB. EMPTY
Contact CNRC.
R C
N U
EMPTY
Check clocking source
R C
N U
EMPTY
October 30, 2008
iVPU-23

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
236083 2
Equipment Fault, Hardware Produced Error Equipment Fault, Synchronization Fault
236339 2
_ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID>
IVPU_D OC3
33, 38
IVPU_D OC3
33,38
419430 5
IVPU_D OC3
33, 38
<CORR_TAG> <EID> Synchronization Loss <CORR_TAG> <EID> Synchronization Loss During a Source Swap <CORR_TAG> <EID> Payload Alive Timeout After Initialization <CORR_TAG> <EID> Resource Does Not Register
Critical
EMPTY
Critical
EMPTY
FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
R C
N U
EMPTY
R C
N U
EMPTY
Critical
5243280
R C
N U
419430 5
IVPU_D OC3
33, 38
Critical
530841 7
Application Error
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2.
IVPU_D OC3
33, 38
<CORR_TAG> <EID>
Minor
2163456, 8388613, 2101505, 5243280, 5308560, 216924, 2294016, 2102530 EMPTY
R C
N U
This alarm is reported by the SPROC when a device goes out of service. This alarm is reported by the SPROC when a device goes out of service.
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 -
530841 7
Application Error
IVPU_D OC3
33, 38
<CORR_TAG> <EID> Processor Statistics Collection Impacted <CORR_TAG> <EID>
Minor
EMPTY
530844 8
General Software Failure
IVPU_D OC3
33, 38
Critical
EMPTY
Lock/reset DOC3 in the maintenance window. If recurring, check hardware. Monitor. If recurring, contact CNRC. Lock/reset DOC3 in the maintenance window. If recurring, check hardware. Monitor. If recurring, contact CNRC. Self Correcting. If recurring, contact CNRC.
N U
EMPTY
N U
EMPTY
R C
N U
EMPTY
530846 4
IVPU_D OC3
33, 38
<CORR_TAG> <EID>
Critical
EMPTY
530846 4
IVPU_D OC3
33, 38
<CORR_TAG> <EID> APS Parameter <CORR_TAG> <EID> Call
Critical
EMPTY
530846 4
IVPU_D OC3
33, 38
Critical
EMPTY
Check DOC3 configuration parameters and correct as necessary. If recurring, contact CNRC. Check DOC3 configuration parameters and correct as necessary. If recurring, contact CNRC. Check DOC3 configuration parameters and correct as
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
iVPU-24
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
530846 5
Configuration Error
530846 5
Configuration Error
530846 5
Configuration Error
530848 0
Hardware Component Error
530849 6
Hardware Component Failure
1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.4.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D>
IVPU_D OC3
33, 38
Processing Parameter <CORR_TAG> <EID>
Major
EMPTY
IVPU_D OC3
33, 38
<CORR_TAG> <EID> APS Parameter <CORR_TAG> <EID> Call Processing Parameter <CORR_TAG> <EID> Noise on HCI Links <CORR_TAG> <EID> Loss of contact - HCI failure on all active links <CORR_TAG> <EID>
Major
EMPTY
IVPU_D OC3
33, 38
Major
EMPTY
IVPU_D OC3
33, 38
Major
EMPTY
IVPU_D OC3
33, 38
Critical
5308480
0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
necessary. If recurring, contact CNRC. Check DOC3 configuration parameters and correct as necessary. If recurring, contact CNRC. Check DOC3 configuration parameters and correct as necessary. If recurring, contact CNRC. Check DOC3 configuration parameters and correct as necessary. If recurring, contact CNRC. Check BPP2 cards.
N U
EMPTY
N U
EMPTY
N U
EMPTY
N U
EMPTY
Reseat Board
R C
N U
EMPTY
530857 6
File System Error
IVPU_D OC3
33, 38
Minor
EMPTY
Lock/reset DOC3 in the maintenance window. If recurring, contact CNRC. Lock/reset DOC3 in the maintenance window. If recurring, contact CNRC. Lock/reset DOC3 in the maintenance window. If recurring, contact CNRC. Lock/reset DOC3 in the maintenance window. If recurring, contact CNRC. Self Correcting. If recurring, contact CNRC.
N U
EMPTY
530864 0
IVPU_D OC3
33, 38
<CORR_TAG> <EID>
Minor
EMPTY
N U
EMPTY
530864 0
IVPU_D OC3
33, 38
530864 0
IVPU_D OC3
33, 38
<CORR_TAG> <EID> Processor Statistics Collection Impacted <CORR_TAG> <EID> Waiting for Personality <CORR_TAG> <EID>
Minor
EMPTY
N U
EMPTY
Minor
EMPTY
N U
EMPTY
530865 6
Software Initialization Failure
IVPU_D OC3
33, 38
Critical
EMPTY
R C
N U
EMPTY
65537
IVPU_EB TS_CON TROL_LI NK
110000
Critical
EMPTY
Unlock the EBTS link
R C
N U
EMPTY
October 30, 2008
iVPU-25

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
838865 2
ACG Link Hardening Procedure Failure ACG Link Hardening Procedure Failure BCP CPU Overload Level 1
838865 2
838873 0
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D>
IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK
110000
ACG Device ID Mismatch <acg_id>
Critical
EMPTY
110000
iVPU Device ID Mismatch <ivpu_id> <CORR_TAG>
Critical
EMPTY
110000
Major
EMPTY
Possible Cause: New ACG site was added or site ID was changed Possible Cause: Misconfiguration of iVPU ID Self correcting. If recurring, contact CNRC.
N U
R C
N U
838873 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D>
110000
<CORR_TAG>
Major
EMPTY
R C
N U
838873 2
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D>
110000
<CORR_TAG>
Major
EMPTY
R C
N U
838873 3
FRIP CPU Overload Level 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I
IVPU_EB TS_CON TROL_LI
110000
<CORR_TAG>
Major
EMPTY
0x0000 0000 0xFFFF
R C
N U
RFC: (SR17.0 BCCB 2107) Added new alarm. RFC: (SR17.0 BCCB 2107) Added new alarm. To self correct, the iVPU shall request to stop new inter connect services for this AFR site. If condition persists, operator needs to reduce traffic from this AFR site. To self correct, the iVPU shall request to stop new inter connect services for this AFR site. If condition persists, operator needs to reduce traffic from this AFR site. To self correct, the iVPU shall request to stop new inter connect services for this AFR site. If condition persists, operator needs to reduce traffic from this AFR site. To self correct, the iVPU shall request to stop
iVPU-26
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
D>
NK
FFFF
838873 4
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D>
110000
<CORR_TAG>
Major
EMPTY
R C
N U
838873 5
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D>
110000
<CORR_TAG>
Major
EMPTY
R C
N U
838874 1
LAPD Communication Failure Backhual Negotiation Failure
838874 2
838874 3
Link Version Mismatch
838874 4
Link Version Down
838874 5
Link Hardening Failure
838874 6
Backhaul Test Procedure Failure
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I
IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI
110000
110000
110000
<CORR_TAG> C1 Link Down: LAPD Communication Failure <CORR_TAG> C1 Link Down: Backhual Negotiation Failure <CORR_TAG> C1 Link Down: Link Version Mismatch <CORR_TAG> C1 Link Down: Link Version Down <CORR_TAG> C1 Link Down: Link Hardening Failure <CORR_TAG> C1 Link Down: Backhual Test
Critical
EMPTY
Critical
EMPTY
Critical
EMPTY
110000
Critical
EMPTY
110000
Critical
EMPTY
110000
Critical
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF
Check the DACS and EBTS configuration. If recurring, contact CRNC Check the DACS and EBTS configuration. If recurring, contact CRNC Check the DACS and EBTS configuration. If recurring, contact CRNC Check the DACS and EBTS configuration. If recurring, contact CRNC Check the DACS and EBTS configuration. If recurring, contact CRNC Check the DACS and EBTS configuration. If recurring, contact CRNC
R C
N U
new services. If condition persists, operator needs to reduce traffic from this site. To self correct, the iVPU shall request to stop new services. If condition persists, operator needs to reduce traffic from this site. To self correct, the iVPU shall request to stop new services. If condition persists, operator needs to reduce traffic from this site. EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
October 30, 2008
iVPU-27

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
838876 8
Site Resource Reconfiguration
838876 8
D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D>
NK IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK
110000
Procedure Failure <CORR_TAG>
Major
EMPTY
110000
<CORR_TAG> Ds0 change Rejected by Site
Major
EMPTY
FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
Self correcting when resources are available. If recurring, contact CNRC. Needs the operator to change the configuration on the ACG or the VPU to rectify it
R C
N U
EMPTY
R C
N U
838876 8
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D>
110000
<CORR_TAG> Link Not Available
Major
EMPTY
Self correcting or it needs the operator to change the configuration on the ACG or the VPU to rectify it
R C
N U
838876 8
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 2.6.1.1.<EBTS_I D>
110000
<CORR_TAG> Timed out propagating change
Major
EMPTY
Self correcting or it needs the operator to change the configuration on the ACG or the VPU to rectify it
R C
N U
838872 6
All EBTS Logical Links Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 2.0
IVPU_EB TS_LINK _CONTA INER
<CORR_TAG> Container State Changed to Disabled
Clear
838872 6
All EBTS Logical Links Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 2.0
<CORR_TAG> Container State Changed to Disabled
Critical
838872 8
Logical Link Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 2.0
<CORR_TAG> Container State Changed to Impaired
Major
65537, 8388739, 8388741, 8388742, 8388743, 8388744, 8388745, 8388746 65537, 8388739, 8388741, 8388742, 8388743, 8388744, 8388745, 8388746 65537, 8388739, 8388741, 8388742, 8388743, 8388744, 8388745, 8388746
EMPTY
N U
RFC: The alarm text is introduced as a part of SR15 feature for SITE aggregation RFC: The alarm text is introduced as a part of SR15 feature for SITE aggregation RFC: The alarm text is introduced as a part of SR15 feature for SITE aggregation The related alarms are the corresponding clear alarms
Check the link status, try to bring the OOS link back into service. If recurring, contact CNRC.
N U
EMPTY
Check the link status, try to bring the OOS link back into service. If recurring, contact CNRC.
N U
EMPTY
iVPU-28
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838872 8
Logical Link Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 2.0
<CORR_TAG> Container State Changed to Impaired
Clear
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent equipmentF ailureEvent
838872 8
Logical Link Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 3.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 3.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 3.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 3.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 3.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 3.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 3.6.1.1.<EBTS_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.3.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.3.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.3.<DEV_I
838872 8
Logical Link Down
838872 9
All EBTS SNMP Logical Links Down
838872 9
All EBTS SNMP Logical Links Down
65537
Device Out of Service : Device Locked LAPD Communication Failure EBTS Proxy OMC Connection Failure
IVPU_EB TS_SNM P_CONT AINER IVPU_EB TS_SNM P_CONT AINER IVPU_EB TS_SNM P_CONT AINER IVPU_EB TS_SNM P_CONT AINER IVPU_EB TS_SNM P_LINK IVPU_EB TS_SNM P_LINK IVPU_EB TS_SNM P_LINK IVPU_FA N_TRAY
110000
<CORR_TAG> Container State Changed to Impaired <CORR_TAG> Container State Changed to Impaired <CORR_TAG> Container State Changed to Disabled <CORR_TAG> Container State Changed to Disabled <CORR_TAG> Operator Locked Device <CORR_TAG> SNMP LINK LAPD Communication Failure <CORR_TAG>
Major
Clear
Critical
Clear
Critical
65537, 8388739, 8388741, 8388742, 8388743, 8388744, 8388745, 8388746 65537, 8388739, 8388741, 8388749 65537, 8388739, 8388741, 8388749 65537, 8388739, 8388741, 8388749 65537, 8388739, 8388741, 8388749 EMPTY
EMPTY
The related alarms are the corresponding clear alarms
communicat ionFailureE vent communicat ionFailureE vent processingF ailureEvent
838874 1
110000
Critical
EMPTY
838874 9
110000
Critical
EMPTY
229632 0
236057 6
Processing Fault, Illegal Configuration Change Equipment Fault, Device Removal Detected Equipment Fault, Hardware Fault Detected
1-3
<CORR_TAG> <EID> <obj class attribute> <CORR_TAG> <EID>
Critical
EMPTY
IVPU_FA N_TRAY
1-3
Critical
2301952
236108 8
IVPU_FA N_TRAY
1-3
<CORR_TAG> <EID>
Critical
5308592
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF
N U
EMPTY
N U
N U
The related alarms are the corresponding clear alarms EMPTY
N U
Unlock the SNMP link
R C
N U
Check the DACS and EBTS configuration. If recurring, contact CRNC Check the IP connectivity with OMC from the iVPU.
R C
N U
EMPTY
R C
N U
EMPTY
Contact CNRC.
R C
N U
EMPTY
Replace Hardware.
R C
N U
EMPTY
Reseat hardware. If recurring, contact CNRC.
R C
N U
EMPTY
October 30, 2008
iVPU-29

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
838875 0
Partial Sites Lost
D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.1.2. 7.1.1.<FRIP_ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_FR IP
1-100
<CORR_TAG>
Major
EMPTY
838863 2
Internal Software Error
IVPU_G EN
Critical
EMPTY
FFFF 0x0000 0000 0xFFFF FFFF EMPTY
N/A. Impacted sites will be automatically reconfigured
R C
N U
EMPTY
iVPU will recover itself.
N U
838863 3
Error in configuration data: Default value available
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> <field> was out of range and it is changed to <new value>.
Major
EMPTY
EMPTY
iVPU continues execution with the default. Analyze and change OMC configuration as needed for this iVPU.
N U
838863 4
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> <field> was out of range.
Critical
EMPTY
EMPTY
Analyze and change OMC configuration as needed for this iVPU. iVPU will continue to self-reset until the incorrect value is corrected in the OMC configuration.
Y U
838863 4
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
Major
EMPTY
EMPTY
Analyze and change OMC configuration as needed for this iVPU. iVPU can continue execution and will ignore the incorrect value.
N U
iVPU processing functionality may be affected until recovery. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. Configured value from OMC was out of range. A default value is being used. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. Configured value from OMC was out of range. No default value is available to be used. SR1443:The MOI Info Id was changed to use the correct OID in SR16.0. Configured value from OMC cannot be used in iVPU. No default value is available to be used. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0.
iVPU-30
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838863 5
Inter Urban Component CPU Overload Level 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> iVPU inter-urban component is experiencing CPU overload level 1.
Major
EMPTY
EMPTY
Check statistics to determine if the iVPU is running at or above the rated call profile. If this alarm occurs frequently, additional iVPUs may need to be added.
838863 5
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> iVPU inter-urban component is no longer CPU overload level 1.
Clear
EMPTY
EMPTY
EMPTY
N U
838863 6
Inter Urban Call Capacity Exceeded Level 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> iVPU inter-urban call capacity has exceeded the level 1 threshold.
Major
EMPTY
EMPTY
If this alarm occurs frequently, additional iVPUd or iVPUdi may need to be added.
N U
838863 6
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> iVPU inter-urban call capacity is no longer exceeding level 1.
Clear
EMPTY
EMPTY
EMPTY
N U
838864 0
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> iVPU inter-urban component is
Major
EMPTY
EMPTY
Check statistics to determine if the iVPU is running at or above the
N U
iVPU inter-urban processing functionality is limited based on the severity of overload. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban processing functionality is partially restored. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU will discard all HN targets in inter-urban call setup messages until inter-urban call capacity is no longer exceeded. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban call processing functionality is partially restored. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban processing functionality is
October 30, 2008
iVPU-31

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
experiencing CPU overload level 2.
rated call profile. If this alarm occurs frequently, additional iVPUs may need to be added.
838864 0
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
Clear
EMPTY
EMPTY
EMPTY
N U
838864 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> iVPU inter-urban component is experiencing CPU overload level 3.
Major
EMPTY
EMPTY
Check statistics to determine if the iVPU is running at or above the rated call profile. If this alarm occurs frequently, additional iVPUs may need to be added.
N U
838864 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
Clear
EMPTY
EMPTY
EMPTY
N U
838864 2
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
Major
EMPTY
EMPTY
N U
limited based on the severity of overload. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban processing functionality is partially restored. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban processing functionality is limited based on the severity of overload. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban processing functionality is fully restored if no other overload conditions exist. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban call processing functionality is limited based on the severity of overload.
iVPU-32
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838864 2
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
Clear
EMPTY
EMPTY
EMPTY
N U
838864 3
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
Major
EMPTY
EMPTY
N U
838864 3
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
Clear
EMPTY
EMPTY
EMPTY
N U
838864 4
Inter Urban Target Capacity Exceeded Level 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> iVPU inter-urban target capacity has exceeded the level 1 threshold.
Major
EMPTY
EMPTY
N U
SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban call processing functionality is partially restored. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban call processing functionality is limited based on the severity of overload. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban processing functionality is fully restored if no other overload conditions exist. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU will discard new inter-urban call setup messages until inter-urban call capacity is no longer exceeded. SR1443: The
October 30, 2008
iVPU-33

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
838864 4
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> iVPU inter-urban target capacity is no longer exceeding level 1.
Clear
EMPTY
EMPTY
EMPTY
N U
838864 5
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
Major
EMPTY
EMPTY
N U
838864 5
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG> iVPU inter-urban target capacity is no longer exceeding level 2.
Clear
EMPTY
EMPTY
EMPTY
N U
838864 6
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
Major
EMPTY
EMPTY
N U
qualityOfSer
838864
Inter Urban Target
1.3.6.1.4.1.161.3
IVPU_G
<CORR_TAG>
Clear
EMPTY
EMPTY
EMPTY
N U
MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban call processing functionality is partially restored. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban call processing functionality is limited based on the severity of overload. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban call processing functionality is partially restored. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban call processing functionality is limited based on the severity of overload. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. iVPU inter-urban
iVPU-34
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
viceFailureE vent
Capacity Exceeded Level 3
.3.10.5.18.1.4.1. 5.0
EN
iVPU inter-urban target capacity is no longer exceeding level 3.
838873 6
Not Enough IOPs Available
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG>
Major
EMPTY
migrate sites so that a unassigned frip will be available to be reconfiged to sip Reconfig a sip into frip through olcc. If there is no sip, reconfig the site to a different VPU.
R C
N U
838874 7
FRIP Limit Reached
1.3.6.1.4.1.161.3 .3.10.2.11.1.1.0
IVPU_G EN
110000
<CORR_TAG>
Major
EMPTY
R C
N U
838875 1
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG>
Major
EMPTY
EMPTY
R C
N U
838875 2
Database Mismatch
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
<CORR_TAG>
Major
EMPTY
EMPTY
R C
N U
838875 5
Inter Urban Dispatch Functionality Out of Service
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 5.0
IVPU_G EN
838872 8
Logical Link Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 7.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 7.0
IVPU_H N_CONT AINER IVPU_H N_CONT AINER
838872 8
Logical Link Down
<CORR_TAG> Inter Urban Dispatch Functionality Partially Out of Service <CORR_TAG> Container State Changed to Impaired <CORR_TAG> Container State Changed to Impaired
Major
EMPTY
N/A. a replacing ward will be automatically reconfigured
R C
N U
processing functionality is fully restored if no other overload conditions exist. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. RFC(SR15.0 release) changed MOI to be IVPU_GEN from IVPU_EBTS_CO NTROL_LINK SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. SR1443: The MOI Info Id was changed to use the correct OID in SR16.0. EMPTY
Major
65537, 8388638
Clear
65537, 8388638
N U
N U
October 30, 2008
iVPU-35

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent processingF ailureEvent
838875 7
All Inter Urban HN Device Logical Links Down All Inter Urban HN Device Logical Links Down Inter Urban HN Device Link Version Negotiation Failure
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 7.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 7.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 7.6.1.1.<UANC>. <HN_ID>
IVPU_H N_CONT AINER IVPU_H N_CONT AINER IVPU_H N_LINK
838875 7
838862 9
838862 9
Inter Urban HN Device Link Version Negotiation Failure
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 7.6.1.1.<UANC>. <HN_ID>
IVPU_H N_LINK
838862 9
Inter Urban HN Device Link Version Negotiation Failure
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 7.6.1.1.<UANC>. <HN_ID>
IVPU_H N_LINK
838863 4
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 7.6.1.1.<UANC>. <HN_ID>
IVPU_H N_LINK
838863 4
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 7.6.1.1.<UANC>. <HN_ID>
IVPU_H N_LINK
838863 8
HN link Disabled
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 7.6.1.1.<UANC>. <HN_ID>
IVPU_H N_LINK
UANC =116777 215 and HN_ID =1-800 UANC =116777 215 and HN_ID =1-800 UANC =116777 215 and HN_ID =1-800 UANC =116777 215 and HN_ID =1-800 UANC =116777 215 and HN_ID =1-800 UANC =116777 215
<CORR_TAG> Container State Changed to Disabled <CORR_TAG> Container State Changed to Disabled <CORR_TAG> Clear HN Link Version Negotiation Procedure Failure alarm.
Critical
65537, 8388638
Clear
65537, 8388638
Clear
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF EMPTY
EMPTY
N U
EMPTY
N U
The related alarms are the corresponding clear alarms iVPU can distribute voice to and from this inter-urban iDAC or iVPU.
<CORR_TAG> Version mismatch.
Critical
EMPTY
EMPTY
Clear
EMPTY
EMPTY
Either the originating iVPU or the inter-urban HN device (iDAC or iVPU) must be upgraded to a software load that supports a compatible link protocol version. EMPTY
N U
iVPU cannot distribute voice to and from this inter-urban iDAC or iVPU.
N U
<CORR_TAG> <field> was out of range.
Critical
EMPTY
EMPTY
Analyze and change OMC configuration as needed for this iVPU. iVPU can continue execution and will ignore this HN device.
N U
This inter-urban iDAC or iVPU is deleted in OLCC or the BPP2 card with this HN allocated to goes down. Configured value from OMC was out of range. No default value is available to be used. Configured value from OMC cannot be used in iVPU. No default value is available to be used. iVPU clears the HN link disabled alarm for this inter-urban iDAC
Major
EMPTY
EMPTY
Analyze and change OMC configuration as needed for this iVPU. iVPU can continue execution and will ignore this HN device.
N U
<CORR_TAG> Clear HN Link Disabled alarm.
Clear
EMPTY
EMPTY
EMPTY
N U
iVPU-36
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838863 8
HN link Disabled
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 7.6.1.1.<UANC>. <HN_ID>
IVPU_H N_LINK
838863 8
HN link Disabled
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 7.6.1.1.<UANC>. <HN_ID>
IVPU_H N_LINK
838875 8
IOP Out of Service
1.3.6.1.4.1.161.3 .3.10.5.18.1.1.2. 8.1.1.<IOP_ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2.
IVPU_IO P
and HN_ID =1-800 UANC =116777 215 and HN_ID =1-800 UANC =116777 215 and HN_ID =1-800 1-100
or iVPU.
Critical
EMPTY
EMPTY
Check inter-urban iDAC or iVPU configuration and state of inter-urban iDAC or iVPU (e.g. down, up) in OMC.
N U
Clear
EMPTY
EMPTY
EMPTY
N U
iVPU cannot distribute voice to and from this inter-urban iDAC or iVPU. It may be due to OLCC changes. This inter-urban iDAC or iVPU is deleted in OLCC.
<CORR_TAG>
Major
EMPTY
65537
Device Out of Service : Device Locked Communication Fault, External Clock Reference Error Communication Fault, Physical Link Connection Error no. 1 Communication Fault, Physical Link Connection Error no. 2 Communication Fault, Physical Link Connection Error no. 3 Communication Fault, Physical Link
IVPU_IS B
2, 18
<CORR_TAG> <EID> Operator Locked Device <CORR_TAG> <EID> Active ISB Free Running, Secondary Available <CORR_TAG> <EID> Switch Router - Slot <#> (Port 0) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 1) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 2) - Physical Link Failure <CORR_TAG> <EID> Switch
Critical
EMPTY
216371 2
IVPU_IS B
2, 18
Critical
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 -
N/A. a replacing dsp will be automatically reconfigured
R C
N U
EMPTY
Unlock hardware. If recurring, reset hardware. If recurring, contact CNRC. Lock/unlock hardware. Monitor. If recurring, replace hardware.
R C
N U
EMPTY
R C
N U
EMPTY
216960 1
IVPU_IS B
2, 18
Major
EMPTY
Check board in <slot ID>. If recurring, contact CNRC.
R C
N U
216960 2
IVPU_IS B
2, 18
Major
65537
R C
N U
216960 3
IVPU_IS B
2, 18
Major
65537
R C
N U
216960 4
IVPU_IS B
2, 18
Major
65537
R C
N U
RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 This alarm is reported when a
October 30, 2008
iVPU-37

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
vent
Connection Error no. 4
1.1.1.1.3.<SLOT _ID>
Router - Slot <#> (Port 3) - Physical Link Failure
0xFFFF FFFF
216960 5
Communication Fault, Physical Link Connection Error no. 5 Communication Fault, Physical Link Connection Error no. 6 Communication Fault, Physical Link Connection Error no. 7 Communication Fault, Physical Link Connection Error no. 8 Communication Fault, Physical Link Connection Error no. 9 Communication Fault, Physical Link Connection Error no. 10 Communication Fault, Physical Link Connection Error no. 11 Communication Fault, Physical Link Connection Error no. 12
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
2, 18
216960 6
IVPU_IS B
2, 18
216960 7
IVPU_IS B
2, 18
216960 8
IVPU_IS B
2, 18
216960 9
IVPU_IS B
2, 18
216961 0
IVPU_IS B
2, 18
216961 1
IVPU_IS B
2, 18
216961 2
IVPU_IS B
2, 18
<CORR_TAG> <EID> Switch Router - Slot <#> (Port 4) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 5) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 6) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 7) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 8) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 9) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 10) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 11) - Physical
Major
65537
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
payload board goes disabled or resets. RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in
iVPU-38
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
216961 3
Communication Fault, Physical Link Connection Error no. 13 Communication Fault, Physical Link Connection Error no. 14 Communication Fault, Physical Link Connection Error no. 15 Communication Fault, Physical Link Connection Error no. 16 Communication Fault, Physical Link Connection Error no. 17 Communication Fault, Physical Link Connection Error no. 18 Communication Fault, Physical Link Connection Error no. 19 Communication Fault, Physical Link Connection Error no. 20 Communication Fault, Physical Link Connection Error no. 21 Communication
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3
IVPU_IS B
2, 18
216961 4
IVPU_IS B
2, 18
216961 5
IVPU_IS B
2, 18
216961 6
IVPU_IS B
2, 18
216961 7
IVPU_IS B
2, 18
216961 8
IVPU_IS B
2, 18
216961 9
IVPU_IS B
2, 18
216962 0
IVPU_IS B
2, 18
216962 1
IVPU_IS B
2, 18
communicat
216962
IVPU_IS
2, 18
Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 12) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 13) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 14) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 15) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 16) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 17) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 18) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 19) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 20) - Physical Link Failure <CORR_TAG>
Major
65537
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
R C
N U
Major
65537
N U
SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified
October 30, 2008
iVPU-39

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
ionFailureE vent
Fault, Physical Link Connection Error no. 22 Communication Fault, Physical Link Connection Error no. 23 Communication Fault, Physical Link Connection Error no. 24 Quality of Serv Fault, Packet Routing Capacity Exceeded Quality of Serv Fault, Packet Routing Capacity Severely Exceeded
.3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
216962 3
IVPU_IS B
2, 18
216962 4
IVPU_IS B
2, 18
222899 2
IVPU_IS B
2, 18
222924 8
IVPU_IS B
2, 18
229401 6
Processing Fault, All Ext Timing Reference Correlated Fault
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
2, 18
<EID> Switch Router - Slot <#> (Port 21) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 22) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 23) - Physical Link Failure <CORR_TAG> <EID> Switch Router Port <number> - Queue <queue id> Full <CORR_TAG> <EID> Switch Router Port <number> - Packet Queue <queue id> Overflow <CORR_TAG> <EID> No Reference Source Clock Available
0000 0xFFFF FFFF Major 65537 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
contact CNRC.
R C
N U
Major
65537, 229880
R C
N U
Minor
EMPTY
May need to re-engineer for proper capacity increase (see Planning guide) May need to re-engineer for proper capacity increase (see Planning guide)
R C
N U
OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 RFC: Modified OMC text to specify the Error number in SR15.0 EMPTY
Major
EMPTY
R C
N U
EMPTY
Major
65537
229657 6
Processing Fault, Initialization Failure
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
2, 18
229657 6
229734 4
OSPF Inactivity Timer Expired
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
2, 18
<CORR_TAG> <EID> Switch Router Ethernet Initialization Failed, return code <code>, port mask <mask> <CORR_TAG> <EID> Multicast reconfig failed <CORR_TAG> <EID> Neighbor Router <#.#.#.#>
Critical
EMPTY
Check the external and internal timing reference. Replace this device and other source devices as necessary. If recurring, contact CNRC. Reseat hardware. Monitor. If recurring, replace hardware
R C
N U
EMPTY
R C
N U
EMPTY
Critical
EMPTY
IVPU_IS B
2, 18
Minor
EMPTY
Reseat hardware. Monitor. If recurring, replace hardware ISB detected connectivity loss with a neighbouring router. Check physical link, hardware configuration. If recurring, contact CNRC.
R C
N U
EMPTY
R C
M U
EMPTY
iVPU-40
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
229760 0
Processing Fault, Primary Resource Fault Processing Fault, OSPF Aggregation Change Error Processing Fault, OSPF Aggregation Change Error
229811 2
229811 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
2, 18
IVPU_IS B
2, 18
<CORR_TAG> <EID> No Primary Reference Available <CORR_TAG> <EID> OSPF Add Route Failure <CORR_TAG> <EID> Configuration Database Update Failure <CORR_TAG> <EID> OSPF Delete Route Failure <CORR_TAG> <EID> Secondary ISB Cannot Track to Mate <CORR_TAG> <EID>
Major
EMPTY
Minor
EMPTY
IVPU_IS B
2, 18
Minor
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
Contact CNRC.
EMPTY
Reseat hardware. Monitor. If recurring, replace hardware Reseat hardware. Monitor. If recurring, replace hardware
R C
N U
EMPTY
R C
N U
EMPTY
229811 2
Processing Fault, OSPF Aggregation Change Error Processing Fault, Secondary Resource Fault Processing Fault, Invalid Configuration For Device Type Equipment Fault, Clock Output Fault
IVPU_IS B
2, 18
Minor
EMPTY
Reseat hardware. Monitor. If recurring, replace hardware Contact CNRC.
R C
N U
EMPTY
229836 8
IVPU_IS B
2, 18
Major
EMPTY
R C
N U
EMPTY
229990 4
IVPU_IS B
2, 18
Critical
EMPTY
Contact CNRC.
R C
N U
EMPTY
236032 0
IVPU_IS B
2, 18
236108 8
Equipment Fault, Hardware Fault Detected Equipment Fault, Hardware Fault Detected
IVPU_IS B
2, 18
236108 8
IVPU_IS B
2, 18
<CORR_TAG> <EID> Main Oscillator Output Failure <CORR_TAG> <EID> Switch Router Port PCI Fatal Error <CORR_TAG> <EID> Checksum Error - packet loss / corruption
Critical
EMPTY
Contact CNRC.
R C
N U
EMPTY
Critical
5308592
Replace Hardware.
R C
N U
EMPTY
Majjor
5308592
Reseat Hardware.
R C
N U
419430 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
2, 18
<CORR_TAG> <EID> Payload Alive Timeout After Initialization
Critical
5243280, 5308496
R C
N U
RFC: This new instance of alarm code text was added in SR14.0 for IDNsa21658 but the ASCE update is in SR15.0 due to schedule issue. This alarm is reported by the SPROC when a device goes out of service.
October 30, 2008
iVPU-41

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
419430 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
2, 18
<CORR_TAG> <EID> Resource Does Not Register
Critical
838877 0
VRRP Mode Transition
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
2,18
<CORR_TAG> <EID> iVPU Switched from VRRP to OSPF
Clear
2163456, 8388613, 2101505, 5243280, 5308560, 216924, 2294016, 2102530 EMPTY
This alarm is reported by the SPROC when a device goes out of service.
EMPTY
EMPTY
N U
838877 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
18
<CORR_TAG> <EID> Transition from BACKUP to INITIALIZE
Minor
838877 0
838877 0
838877 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
18
IVPU_IS B
2, 18
IVPU_IS B
2, 18
<CORR_TAG> <EID> Transition from INITIALIZE to BACKUP <CORR_TAG> <EID> Transition from INITIALIZE to MASTER <CORR_TAG> <EID> Transition from MASTER to INITIALIZE
Clear
2164224, 65537, 2163712, 2296576, 2299904, 2360320, 2361088, 4194305 EMPTY
EMPTY
Self correcting. If recurring, check the Gigabit links and ISB state. If recurring, contact CNRC
R C
N U
It is to clear the outstanding alarm with this type RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm is added in SR15.0 for VRRP feature
EMPTY
EMPTY
R C
N U
Clear
EMPTY
EMPTY
EMPTY
R C
N U
Minor
838877 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID>
IVPU_IS B
18
<CORR_TAG> <EID>Transition from BACKUP to MASTER
Minor
2164224, 65537, 2163712, 2296576, 2299904, 2360320, 2361088, 4194305 2164224, 65537, 2163712, 2296576, 2299904, 2360320, 2361088,
EMPTY
R C
N U
RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm is added in SR15.0 for VRRP feature
EMPTY
Self correcting. If recurring, check the Gigabit links and ISB-2 state. If recurring, contact CNRC
R C
N U
RFC: This alarm is added in SR15.0 for VRRP feature
iVPU-42
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838877 0
838877 0
838861 7
Wrong ISB Hardware Type Detected
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.3.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B
18
IVPU_IS B
2,18
<CORR_TAG> <EID>Transition from MASTER to BACKUP <CORR_TAG> <EID>VRRP Internal Error <CORR_TAG> <EID> ISB1 board type detected in IPFR enabled mode <CORR_TAG> <EID> Operator Locked Device <CORR_TAG> <EID> Active ISB Free Running, Secondary Available <CORR_TAG> <EID> Switch Router - Slot <#> (Port 0) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 1) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 2) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 3) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 4) - Physical
Clear
4194305 EMPTY
EMPTY
EMPTY
R C
N U
Critical
EMPTY
EMPTY
R C
N U
IVPU_IS B
2,18
Critical
EMPTY
EMPTY
Replace ISB1 with ISB2
R C
Y U
RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm is added in SR15.0 for IPFR feature EMPTY
65537
Device Out of Service : Device Locked Communication Fault, External Clock Reference Error Communication Fault, Physical Link Connection Error no. 1 Communication Fault, Physical Link Connection Error no. 2 Communication Fault, Physical Link Connection Error no. 3 Communication Fault, Physical Link Connection Error no. 4 Communication Fault, Physical Link Connection Error no. 5
IVPU_IS B2
2, 18
Critical
EMPTY
216371 2
IVPU_IS B2
2, 18
Critical
EMPTY
Unlock hardware. If recurring, reset hardware. If recurring, contact CNRC. Lock/unlock hardware. Monitor. If recurring, replace hardware.
R C
N U
R C
N U
EMPTY
216960 1
IVPU_IS B2
2, 18
Major
EMPTY
Check board in <slot ID>. If recurring, contact CNRC.
R C
N U
EMPTY
216960 2
IVPU_IS B2
2, 18
Major
65537
R C
N U
EMPTY
216960 3
IVPU_IS B2
2, 18
Major
65537
R C
N U
EMPTY
216960 4
IVPU_IS B2
2, 18
Major
65537
R C
N U
EMPTY
216960 5
IVPU_IS B2
2, 18
Major
65537
R C
N U
EMPTY
October 30, 2008
iVPU-43

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
216960 6
Communication Fault, Physical Link Connection Error no. 6 Communication Fault, Physical Link Connection Error no. 7 Communication Fault, Physical Link Connection Error no. 8 Communication Fault, Physical Link Connection Error no. 9 Communication Fault, Physical Link Connection Error no. 10 Communication Fault, Physical Link Connection Error no. 11 Communication Fault, Physical Link Connection Error no. 12 Communication Fault, Physical Link Connection Error no. 13 Communication Fault, Physical Link Connection Error no. 14 Communication
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3
IVPU_IS B2
2, 18
216960 7
IVPU_IS B2
2, 18
216960 8
IVPU_IS B2
2, 18
216960 9
IVPU_IS B2
2, 18
216961 0
IVPU_IS B2
2, 18
216961 1
IVPU_IS B2
2, 18
216961 2
IVPU_IS B2
2, 18
216961 3
IVPU_IS B2
2, 18
216961 4
IVPU_IS B2
2, 18
communicat
216961
IVPU_IS
2, 18
Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 5) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 6) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 7) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 8) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 9) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 10) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 11) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 12) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 13) - Physical Link Failure <CORR_TAG>
Major
65537
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
N U
EMPTY
iVPU-44
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
ionFailureE vent
Fault, Physical Link Connection Error no. 15 Communication Fault, Physical Link Connection Error no. 16 Communication Fault, Physical Link Connection Error no. 17 Communication Fault, Physical Link Connection Error no. 18 Communication Fault, Physical Link Connection Error no. 19 Communication Fault, Physical Link Connection Error no. 20 Communication Fault, Physical Link Connection Error no. 21 Communication Fault, Physical Link Connection Error no. 22 Communication Fault, Physical Link Connection Error no. 23 Communication Fault, Physical Link Connection Error
.3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT
B2
216961 6
IVPU_IS B2
2, 18
216961 7
IVPU_IS B2
2, 18
216961 8
IVPU_IS B2
2, 18
216961 9
IVPU_IS B2
2, 18
216962 0
IVPU_IS B2
2, 18
216962 1
IVPU_IS B2
2, 18
216962 2
IVPU_IS B2
2, 18
216962 3
IVPU_IS B2
2, 18
216962 4
IVPU_IS B2
2, 18
<EID> Switch Router - Slot <#> (Port 14) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 15) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 16) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 17) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 18) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 19) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 20) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 21) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#> (Port 22) - Physical Link Failure <CORR_TAG> <EID> Switch Router - Slot <#>
0000 0xFFFF FFFF Major 65537 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF
contact CNRC.
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537
R C
N U
EMPTY
Major
65537, 229880
R C
N U
EMPTY
October 30, 2008
iVPU-45

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
no. 24 qualityOfSer viceFailureE vent 222899 2 Quality of Serv Fault, Packet Routing Capacity Exceeded Quality of Serv Fault, Packet Routing Capacity Severely Exceeded
_ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> IVPU_IS B2 2, 18
222924 8
IVPU_IS B2
2, 18
229401 6
Processing Fault, All Ext Timing Reference Correlated Fault
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
(Port 23) - Physical Link Failure <CORR_TAG> <EID> Switch Router Port <number> - Queue <queue id> Full <CORR_TAG> <EID> Switch Router Port <number> - Packet Queue <queue id> Overflow <CORR_TAG> <EID> No Reference Source Clock Available
FFFF Minor EMPTY 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF May need to re-engineer for proper capacity increase (see Planning guide) May need to re-engineer for proper capacity increase (see Planning guide) R C N U EMPTY
Major
EMPTY
R C
N U
EMPTY
Major
65537
229657 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
229657 6
229734 4
OSPF Inactivity Timer Expired
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
<CORR_TAG> <EID> Switch Router Ethernet Initialization Failed, return code <code>, port mask <mask> <CORR_TAG> <EID> Multicast reconfig failed <CORR_TAG> <EID> Neighbor Router <#.#.#.#>
Critical
EMPTY
Check the external and internal timing reference. Replace this device and other source devices as necessary. If recurring, contact CNRC. Reseat hardware. Monitor. If recurring, replace hardware
R C
N U
EMPTY
R C
N U
EMPTY
Critical
EMPTY
IVPU_IS B2
2, 18
Minor
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
Reseat hardware. Monitor. If recurring, replace hardware ISB detected connectivity loss with a neighbouring router. Check physical link, hardware configuration. If recurring, contact CNRC. Contact CNRC.
R C
N U
EMPTY
R C
N U
EMPTY
229760 0
Processing Fault, Primary Resource Fault Processing Fault, OSPF Aggregation Change Error Processing Fault, OSPF Aggregation Change Error
IVPU_IS B2
2, 18
229811 2
IVPU_IS B2
2, 18
<CORR_TAG> <EID> No Primary Reference Available <CORR_TAG> <EID> OSPF Add Route Failure <CORR_TAG> <EID> Configuration Database Update
Major
EMPTY
R C
N U
EMPTY
Minor
EMPTY
Reseat hardware. Monitor. If recurring, replace hardware Reseat hardware. Monitor. If recurring, replace hardware
R C
N U
EMPTY
229811 2
IVPU_IS B2
2, 18
Minor
EMPTY
R C
N U
EMPTY
iVPU-46
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
229811 2
Processing Fault, OSPF Aggregation Change Error Processing Fault, Secondary Resource Fault Processing Fault, Invalid Configuration For Device Type Equipment Fault, Clock Output Fault
229836 8
229990 4
236032 0
236108 8
Equipment Fault, Hardware Fault Detected Device Out of Service : Contact Lost
419430 5
IVPU_IS B2
2, 18
IVPU_IS B2
2, 18
IVPU_IS B2
2, 18
Failure <CORR_TAG> <EID> OSPF Delete Route Failure <CORR_TAG> <EID> Secondary ISB Cannot Track to Mate <CORR_TAG> <EID>
Minor
EMPTY
Major
EMPTY
Critical
EMPTY
IVPU_IS B2
2, 18
IVPU_IS B2
2, 18
IVPU_IS B2
2, 18
<CORR_TAG> <EID> Main Oscillator Output Failure <CORR_TAG> <EID> Switch Router Port PCI Fatal Error <CORR_TAG> <EID> Payload Alive Timeout After Initialization <CORR_TAG> <EID> Resource Does Not Register
Critical
EMPTY
Critical
5308592
Critical
5243280, 5308496
Reseat hardware. Monitor. If recurring, replace hardware Contact CNRC.
R C
N U
EMPTY
R C
N U
EMPTY
Contact CNRC.
R C
N U
EMPTY
Contact CNRC.
R C
N U
EMPTY
Replace Hardware.
R C
N U
EMPTY
R C
N U
419430 5
IVPU_IS B2
2, 18
Critical
543955 2
Switch Router Internal Port Physical Link Failure
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
<CORR_TAG> <EID> Port Number X Physical Failure
Minor
2163456, 8388613, 2101505, 5243280, 5308560, 216924, 2294016, 2102530 EMPTY
R C
N U
This alarm is reported by the SPROC when a device goes out of service. This alarm is reported by the SPROC when a device goes out of service.
543955 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will
R C
N U
This alarm indicates that an internal ethernet connection has lost physical connectivity.
R C
N U
This alarm indicates that an internal ethernet connection has
October 30, 2008
iVPU-47

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
543955 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543955 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543955 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543955 7
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543955 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and
lost physical connectivity.
R C
N U
R C
N U
R C
N U
R C
N U
R C
N U
iVPU-48
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
543955 9
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543956 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543956 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543956 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543956 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is
R C
N U
R C
N U
R C
N U
R C
N U
R C
N U
October 30, 2008
iVPU-49

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
543956 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543956 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543956 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543956 7
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543956 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
communicat
543956
Switch Router
1.3.6.1.4.1.161.3
IVPU_IS
2, 18
<CORR_TAG>
Minor
EMPTY
0x0000
necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call
R C
N U
R C
N U
R C
N U
R C
N U
R C
N U
N U
This alarm
iVPU-50
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
ionFailureE vent
Internal Port Physical Link Failure
.3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
B2
<EID> Port Number X Physical Failure
0000 0xFFFF FFFF
543957 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543957 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543957 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543957 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543957 4
Switch Router Internal Port Physical Link
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT
IVPU_IS B2
2, 18
<CORR_TAG> <EID> Port Number X Physical
Minor
EMPTY
0x0000 0000 0xFFFF
processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload
indicates that an internal ethernet connection has lost physical connectivity.
R C
N U
R C
N U
R C
N U
R C
N U
R C
N U
This alarm indicates that an internal ethernet
October 30, 2008
iVPU-51

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
Failure
_ID>
Failure
FFFF
543957 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543957 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543957 7
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543957 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543957 9
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system
connection has lost physical connectivity.
R C
N U
R C
N U
R C
N U
R C
N U
R C
N U
This alarm indicates that an internal ethernet connection has lost physical
iVPU-52
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
543958 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543958 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543958 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543958 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543958 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt
connectivity.
R C
N U
R C
N U
R C
N U
R C
N U
R C
N U
October 30, 2008
iVPU-53

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
543958 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543958 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543958 7
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543958 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543958 9
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary.
R C
N U
R C
N U
R C
N U
R C
N U
R C
N U
iVPU-54
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
543959 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543959 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543959 2
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543959 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543959 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543959 5
Switch Router Internal Port
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2.
IVPU_IS B2
2, 18
<CORR_TAG> <EID> Port
Minor
EMPTY
0x0000 0000 -
No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet
R C
N U
R C
N U
R C
N U
R C
N U
R C
N U
This alarm indicates that an
October 30, 2008
iVPU-55

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
vent
Physical Link Failure
1.1.1.1.8.<SLOT _ID>
Number X Physical Failure
0xFFFF FFFF
543959 6
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543959 7
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543959 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543959 9
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
543960 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will
internal ethernet connection has lost physical connectivity.
R C
N U
R C
N U
R C
N U
R C
N U
R C
N U
This alarm indicates that an internal ethernet connection has
iVPU-56
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
543960 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2, 18
Minor
EMPTY
838877 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
2,18
<CORR_TAG> <EID> iVPU Switched from VRRP to OSPF
Clear
EMPTY
EMPTY
be affected. The system will continuously and automatically attempt recovery. No action is necessary. No impact to call processing. Ethernet redundancy to a payload card, ISB2, or SPROC will be affected. The system will continuously and automatically attempt recovery. No action is necessary. EMPTY
lost physical connectivity.
R C
N U
N U
838877 0
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
IVPU_IS B2
18
<CORR_TAG> <EID> Transition from BACKUP to INITIALIZE
Minor
838877 0
838877 0
838877 0
IVPU_IS B2
18
IVPU_IS B2
2, 18
IVPU_IS B2
2, 18
<CORR_TAG> <EID> Transition from INITIALIZE to BACKUP <CORR_TAG> <EID> Transition from INITIALIZE to MASTER <CORR_TAG> <EID> Transition from MASTER to INITIALIZE
Clear
2164224, 65537, 2163712, 2296576, 2299904, 2360320, 2361088, 4194305 EMPTY
EMPTY
R C
N U
It is to clear the outstanding alarm with this type RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm is added in SR15.0 for VRRP feature
EMPTY
EMPTY
R C
N U
Clear
EMPTY
EMPTY
EMPTY
R C
N U
Minor
processingF
838877
VRRP Mode
1.3.6.1.4.1.161.3
IVPU_IS
18
<CORR_TAG>
Minor
2164224, 65537, 2163712, 2296576, 2299904, 2360320, 2361088, 4194305 2164224,
R C
N U
RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm is added in SR15.0 for VRRP feature
EMPTY
N U
RFC: This alarm
October 30, 2008
iVPU-57

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
ailureEvent
Transition
.3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID>
B2
<EID>Transition from BACKUP to MASTER
838877 0
838877 0
838863 0
Intra Urban Audio Route Link Failure
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.8.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.12.1.1.<iSG_I D>
IVPU_IS B2
18
IVPU_IS B2
2,18
<CORR_TAG> <EID>Transition from MASTER to BACKUP <CORR_TAG> <EID>VRRP Internal Error <CORR_TAG> Max retries, <source device type>,<source device ID>,<source IP address>,<source port>,<destination IP address>,<destinati on port>. <CORR_TAG> No CntChkRsp, <source device type>,<source device ID>,<source IP address>,<source port>,<destination IP address>,<destinati on port>. <CORR_TAG> No InfoRsp, <source device type>,<source device ID>,<source IP address>,<source port>,<destination IP address>,<destinati
Clear
65537, 2163712, 2296576, 2299904, 2360320, 2361088, 4194305 EMPTY
check the Gigabit links and ISB state. If recurring, contact CNRC
is added in SR15.0 for VRRP feature
EMPTY
EMPTY
R C
N U
Critical
EMPTY
EMPTY
R C
N U
IVPU_iS G_LINK
1-4
Clear
EMPTY
EMPTY
EMPTY
N U
RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm is added in SR15.0 for VRRP feature Check for possible network problem.
838863 0
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.12.1.1.<iSG_I D>
IVPU_iS G_LINK
1-4
Critical
EMPTY
EMPTY
EMPTY
N U
iVPU does not receive the intraurban audio route continuity check response and cannot set up the audio route with this iSG.
838863 0
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.12.1.1.<iSG_I D>
IVPU_iS G_LINK
1-4
Critical
EMPTY
EMPTY
EMPTY
N U
iVPU does not receive the intraurban audio route information response and cannot set up the audio route with this iSG.
iVPU-58
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838863 0
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.12.1.1.<iSG_I D>
IVPU_iS G_LINK
1-4
838863 0
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.12.1.1.<iSG_I D>
IVPU_iS G_LINK
1-4
216422 4
Communication Fault, Gigabit Link Connection Error
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.6.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 8.0
IVPU_LA NCIRCUI T
1-4
838875 9
Enter Overloading
IVPU_LO AD_CON TAINER
on port>. <CORR_TAG> Rcvd CntChkRsp, <source device type>,<source device ID>,<source IP address>,<source port>,<destination IP address>,<destinati on port>. <CORR_TAG> Rcvd InfoRsp, <source device type>,<source device ID>,<source IP address>,<source port>,<destination IP address>,<destinati on port>. <CORR_TAG> <EID> Switch Router Port <port number> Physical Link Failure <CORR_TAG> Container State Changed to Impaired
Clear
EMPTY
EMPTY
EMPTY
N U
iVPU receives the intra-urban audio route continuity check response and can set up the audio route with this iSG,
Clear
EMPTY
EMPTY
EMPTY
N U
iVPU receives the intra-urban audio route information response and can set up the audio route with this iSG.
Critical
EMPTY
Major
838872 8
Logical Link Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 5.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 5.0
838872 8
Logical Link Down
IVPU_M DG_CO NTAINE R IVPU_M DG_CO NTAINE
<CORR_TAG> Container State Changed to Impaired <CORR_TAG> Container State Changed to
Major
8388635, 8388640, 8388641, 8388730, 8388731, 8388732, 8388733, 8388734, 8388735, 8388763, 8388764, 8388765 65537, 8388639
Check physical link with remote entity. Check the speed for this interface on the router. If recurring, contact CNRC. EMPTY
R C
N U
RFC: (SR15.0 release) Modified remedy. EMPTY
R C
N U
Clear
65537, 8388639
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF
N U
EMPTY
N U
The related alarms are the corresponding
October 30, 2008
iVPU-59

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent equipmentF ailureEvent
838876 0
All MDG Logical Links Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 5.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 5.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D>
838876 0
All MDG Logical Links Down
65537
R IVPU_M DG_CO NTAINE R IVPU_M DG_CO NTAINE R IVPU_M DG_LIN K
1-36
Impaired <CORR_TAG> Container State Changed to Disabled <CORR_TAG> Container State Changed to Disabled <CORR_TAG> Operator Locked Device
Critical
65537, 8388639
Clear
65537, 8388639
Critical
EMPTY
FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0000 0000 FFFF FFFF
N U
clear alarms EMPTY
N U
Unlock MDG link.
N U
65537
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D>
IVPU_M DG_LIN K
1-36
Clear
EMPTY
0000 0000 FFFF FFFF
EMPTY
N U
838862 6
MDG Connection Failure
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D>
IVPU_M DG_LIN K
1-36
<CORR_TAG> Cannot establish TCP/IP connection.IP Addr: <MDG IP address>
Critical
EMPTY
EMPTY
iVPU will persistently retry the connection. Verify that MDG is operational. Verify IP configuration and iDEN LAN network connectivity.
N U
838862 6
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D>
IVPU_M DG_LIN K
1-36
838862 6
IVPU_M DG_LIN K IVPU_M DG_LIN K
1-36
838862 6
1-36
<CORR_TAG> Cannot establish TCP/IP connection.IP Addr: <MDG IP address> <CORR_TAG> Clear MDG Connection Failure alarm. <CORR_TAG> Lost connection with MDG
Clear
EMPTY
EMPTY
EMPTY
N U
The related alarms are the corresponding clear alarms Operator issued MDG link lock command. iVPU cannot communicate with this MDG. Operator issued MDG link unlock command and iVPU can establish communication with this MDG or this MDG is deleted in OLCC. iVPU cannot communicate with this MDG. This alarm can happen only during first time iVPU-MDG link initialization. This MDG is deleted in OLCC.
Clear
EMPTY
EMPTY
EMPTY
N U
Critical
EMPTY
EMPTY
iVPU will persistently reestablish the connection with this MDG.
N U
iVPU can establish TCP/IP connection with this MDG. iVPU lost the communication with this MDG. This alarm can happen only
iVPU-60
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838862 6
838862 8
MDG Link Version Check Procedure Failure
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D>
1-36
<CORR_TAG> Lost connection with MDG <CORR_TAG> Clear MDG Link Version Check Procedure Failure alarm. <CORR_TAG> No response from MDG.
Clear
EMPTY
EMPTY
EMPTY
N U
when the iVPUMDG link was previously up. This MDG is deleted in OLCC. iVPU receives the LVCP response from this MDG. This is an expected alarm when a new MDG is added and has not been fully initialized. iVPU cannot communicate with this MDG. This MDG is deleted in OLCC. Configured value from OMC was out of range. No default value is available to be used. Configured value from OMC cannot be used in iVPU. No default value is available to be used. iVPU clears the MDG link disabled alarm for this MDG. iVPU cannot communicate with this MDG. It may be due to
1-36
Clear
EMPTY
EMPTY
EMPTY
N U
838862 8
IVPU_M DG_LIN K
1-36
Critical
EMPTY
EMPTY
iVPU will persist with Link Version Check Procedure until it receives a success indication from the MDG. Verify configuration between iVPU and MDG in OMC.
N U
838862 8
MDG Link Version Check Procedure Failure Error in configuration data: Default value unavailable
838863 4
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D>
1-36
<CORR_TAG> No response from MDG. <CORR_TAG> <field> was out of range.
Clear
EMPTY
EMPTY
EMPTY
N U
1-36
Critical
EMPTY
EMPTY
Analyze and change OMC configuration as needed for this iVPU. iVPU can continue execution and will ignore this MDG. Analyze and change OMC configuration as needed for this iVPU. iVPU can continue execution and will ignore this MDG.
N U
838863 4
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D>
IVPU_M DG_LIN K
1-36
Major
EMPTY
EMPTY
N U
838863 9
MDG link Disabled
838863 9
MDG link Disabled
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D>
1-36
<CORR_TAG> Clear MDG Link Disabled alarm. <CORR_TAG> Logical Link Down.
Clear
EMPTY
EMPTY
EMPTY
N U
1-36
Critical
EMPTY
EMPTY
Check MDG configuration and state of MDG (e.g. down, up) in OMC.
N U
October 30, 2008
iVPU-61

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
OLCC or IP Footprint changes. RFC: There is a minor change in SR15.0 comments & notes to add IP Footprint impact on this alarm. This MDG is deleted in OLCC. iVPU clears the LVCP status field failure alarm for this MDG. iVPU cannot communicate with this MDG.
838863 9
MDG link Disabled
838865 0
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 5.6.1.1.<MDG_I D> 1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 5.0
1-36
Clear
EMPTY
EMPTY
EMPTY
N U
1-36
838865 0
IVPU_M DG_LIN K
1-36
<CORR_TAG> Clear MDG Link Version Check Procedure Failure alarm. <CORR_TAG> Status field indicates failure.
Clear
EMPTY
EMPTY
EMPTY
N U
Critical
EMPTY
EMPTY
838865 0
MDG Link Version Check Procedure Failure MDG Link Version Check Procedure Failure
1-36
<CORR_TAG> Status field indicates failure. <CORR_TAG> Clear MDG Link Version Check Procedure Failure alarm. <CORR_TAG> Version mismatch.
Clear
EMPTY
EMPTY
Either the iVPU or the MDG must be upgraded to a software load that supports a compatible link protocol version. EMPTY
N U
N U
This MDG is deleted in OLCC. iVPU clears the LVCP version mismatch alarm for this MDG. iVPU cannot communicate with this MDG.
838865 1
1-36
Clear
EMPTY
EMPTY
EMPTY
N U
838865 1
IVPU_M DG_LIN K
1-36
Critical
EMPTY
EMPTY
838865 1
MDG Link Version Check Procedure Failure Misc Rollup container
IVPU_M DG_LIN K IVPU_MI SC_CON TAINER
1-36
Clear
EMPTY
EMPTY
Status field indicates success, but MDG sends a version to iVPU that iVPU doesn't support. Contact CNRC. EMPTY
N U
N U
This MDG is deleted in OLCC. Miscellaneous container represents the following
838861 3
<CORR_TAG> <EID> Caused By: <BITS | FANTRAY | PSM>
Critical
2163456, 65537
Lock/Unlock hardware causing the state change. If recurring, contact CNRC.
R C
N U
iVPU-62
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838861 3
Misc Rollup container
1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 5.0
IVPU_MI SC_CON TAINER
<CORR_TAG> <EID> Caused By: <BITS | FANTRAY | PSM>
Major
2163456, 65537
Lock/Unlock hardware causing the state change. If recurring, contact CNRC.
R C
N U
838876 1
All Channels Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 6.0
838876 2
Channel Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.1. 6.0
838861 1
Node container state transition
1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 2.0
IVPU_M PS_FR_ CHAN_C ONTAIN ER IVPU_M PS_FR_ CHAN_C ONTAIN ER IVPU_N ODE
<CORR_TAG> Container State Changed to Disabled <CORR_TAG> Container State Changed to Impaired <CORR_TAG> Caused By: <CCA | SPROC | AIO | BPP2 | DOC3 | OCPORT | ISB | DGBE | MISC>
Critical
8388766
Major
8388766
Major
5308480, 5308560, 4194305, 2362880
Check the MPS FR channels status, try to bring the OOS channels back into service. If recurring, contact CNRC. Check the MPS FR channels status, try to bring the OOS channels back into service. If recurring, contact CNRC. Check composite hardware devices. If recurring, contact CNRC.
R C
N U
devices: BITS, Power Supply, Fan Tray. All instances of at least one of these device types have failed. This alarm will be preceded by the individual device's alarm. Miscellaneous container represents the following devices: BITS, Power Supply, Fan Tray. At least one instance of these device types has failed. EMPTY
R C
N U
EMPTY
R C
N U
Node container represents the following devices: CCA, SPROC, AIO, BPP2, DOC3, OCPORT, ISB, DGBE, MISC_CONTAIN ER . At least one instance of these device types has failed. Depending on what device is
October 30, 2008
iVPU-63

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
838861 1
Node container state transition
1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 2.0
IVPU_N ODE
<CORR_TAG> Caused By: <CCA | SPROC | BPP2 | DOC3 | OCPORT | ISB | DGBE>
Critical
5308480, 5308560, 4194305, 2362880
Check the alarms log to see which device caused this alarm.
R C
N U
838877 1
VRRP Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 2.0
IVPU_N ODE
838877 2
Incompatible Gigabit interface type
1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 2.0
IVPU_N ODE
<CORR_TAG> <EID> VRRP requires iVPU IP addresses to be on the same subnet <CORR_TAG> <EID> ISBs are running incompatible protocols
Minor
EMPTY
EMPTY
Change the IP addresses to be on the same subnet
R C
N U
non-functional, there may be a capacity impairment. Locking or resetting of the devices listed above can raise this alarm. Node container represents the following devices: CCA, SPROC, BPP2, DOC3, OCPORT, ISB, DGBE. All instances of one of the device type mentioned above has failed. Depending on what device is non-functional, there may be a capacity impairment. MISC_CONTAIN ER and AIO will not cause Node State to be disabled. RFC: This alarm is added in SR15.0 for VRRP feature One ISB is configured as OSPF, the other is configured as VRRP RFC: This alarm is added in SR15.0 for VRRP feature RFC: This alarm
Minor
EMPTY
EMPTY
switch the mode to make sure both ISBs are running the same protocol
R C
N U
communicat
851969
iVPU Logical IP
1.3.6.1.4.1.161.3
IVPU_N
<CORR_TAG>
Warni
EMPTY
0x0000
EMPTY
N U
iVPU-64
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
ionFailureE vent
Address /Subnet Changed
.3.10.5.18.1.1.1. 2.0
ODE
524339 2
Active Role Required
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 2.1.1.<OCBANK _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID>
IVPU_O CBANK
1,2
<EID> iVPU Logical IP address is changed from <old IP> to <new IP> <CORR_TAG> <EID>
ng
0000 0xFFFF FFFF
is added in SR15.0 for IPFR feature
Critical
65537, 2164224
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
537420 8
Signal Failure on the OC3 Link
IVPU_O CPORT
537420 8
IVPU_O CPORT
537420 8
IVPU_O CPORT
537420 8
IVPU_O CPORT
537420 8
IVPU_O CPORT
331332, 381382 331332, 381382 331332, 381382 331332, 381382 331332, 381382
<CORR_TAG> LOF
Critical
EMPTY
<CORR_TAG> SF
Critical
EMPTY
Ensure at least one DOC3 is active and both its ocports are active. If recurring, check the state of ISB. Ensure DACS configuration is correct. Refer to trouble shootingn guide Ensure the oc3 fibers are connected
R C
N U
R C
N U
Locking or resetting of the devices listed above can raise this alarm. EMPTY
R C
N U
EMPTY
<CORR_TAG> AIS
Critical
EMPTY
Ensure the oc3 fibers are connected
R C
N U
EMPTY
<CORR_TAG> APS Protection Switching Byte Failure <CORR_TAG> FEPL
Critical
EMPTY
R C
N U
EMPTY
Critical
EMPTY
Ensure that the OC3 fibers are connected. Ensure that the configuration of the remote entity matches the iVPU. If recurring, contact CNRC.
R C
N U
537420 8
537422 4
Signal Degradation on the OC3 Link
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID>
IVPU_O CPORT
IVPU_O CPORT
331332, 381382 331332, 381382
<CORR_TAG> LOS
Critical
65537, 2164224
<CORR_TAG> AIS
Major
65537
R C
N U
This is a signal failure alarm. Detected under bidirectional mode, and protecting TX cable is pulled out. EMPTY
537422 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT
IVPU_O CPORT
331332, 381-
<CORR_TAG> APS Channel Mismatch
Major
65537
0x0000 0000 0xFFFF
Ensure that the OC3 fibers are connected. Ensure that the configuration of the remote entity matches the iVPU. If recurring, contact CNRC. Ensure that the OC3 fibers are connected. Ensure that the configuration of the
R C
N U
EMPTY
R C
N U
EMPTY
October 30, 2008
iVPU-65

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
_ID>
382
FFFF
537422 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID>
IVPU_O CPORT
331332, 381382
<CORR_TAG> APS Mode Mismatch
Major
65537
537422 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID>
IVPU_O CPORT
331332, 381382
<CORR_TAG> LOP
Major
65537
537422 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID>
IVPU_O CPORT
331332, 381382
<CORR_TAG> PLM
Major
65537
537422 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID>
IVPU_O CPORT
331332, 381382
<CORR_TAG> RFI
Major
65537, 2164224
537422 4
537422 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID>
IVPU_O CPORT
IVPU_O CPORT
331332, 381382 331332, 381382
<CORR_TAG> SD
Major
EMPTY
<CORR_TAG> UNEQ
Major
65537
remote entity matches the iVPU. If recurring, contact CNRC. Ensure that the OC3 fibers are connected. Ensure that the configuration of the remote entity matches the iVPU. If recurring, contact CNRC. Ensure that the OC3 fibers are connected. Ensure that the configuration of the remote entity matches the iVPU. If recurring, contact CNRC. Ensure that the OC3 fibers are connected. Ensure that the configuration of the remote entity matches the iVPU. If recurring, contact CNRC. Ensure that the OC3 fibers are connected. Ensure that the configuration of the remote entity matches the iVPU. If recurring, contact CNRC. Ensure the oc3 fibers are connected
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
537424 0
Automatic Protection Switch Failure OLCC Command Failed
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.5.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.2.11.1.1.0
IVPU_O CPORT
IVPU_OL CC
331332, 381382 1
<CORR_TAG> APS Switching Failure Commands Failed during OLCC
Critical
EMPTY
Warni ng
EMPTY
0x0000 0000 0xFFFF FFFF EMPTY
Ensure that the OC3 fibers are connected. Ensure that the configuration of the remote entity matches the iVPU. If recurring, contact CNRC. Ensure that at least one DOC3 is active and both ocports on them are active Investigate why a command or commands were rejected during OLCC
R C
N U
EMPTY
R C
N U
EMPTY
N U
There may be mismatch between OMC and BSC database. SR1443: The
iVPU-66
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838863 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.11.1.1.<PEER _IVPU_ID>
IVPU_PE ERIVPU _LINK
1-252
838863 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.11.1.1.<PEER _IVPU_ID>
1-252
838863 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.11.1.1.<PEER _IVPU_ID>
1-252
838863 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.11.1.1.<PEER _IVPU_ID>
1-252
<CORR_TAG> Max retries, <source device type>,<source device ID>,<source IP address>,<source port>,<destination IP address>,<destinati on port>. <CORR_TAG> No CntChkRsp, <source device type>,<source device ID>,<source IP address>,<source port>,<destination IP address>,<destinati on port>. <CORR_TAG> No InfoRsp, <source device type>,<source device ID>,<source IP address>,<source port>,<destination IP address>,<destinati on port>. <CORR_TAG> Rcvd CntChkRsp, <source device type>,<source device ID>,<source IP address>,<source port>,<destination
Clear
EMPTY
EMPTY
EMPTY
N U
MOI Info Label was changed to differentiate from other IVPU_GEN alarms in SR16.0. Check for possible network problem.
Critical
EMPTY
EMPTY
EMPTY
N U
iVPU does not receive the intraurban audio route continuity check response and cannot set up the audio route with this intra-urban iVPU. iVPU does not receive the intraurban audio route information response and cannot set up the audio route with this intraurban iVPU.
Critical
EMPTY
EMPTY
EMPTY
N U
Clear
EMPTY
EMPTY
EMPTY
N U
iVPU receives the intra-urban audio route continuity check response and can set up the audio route with this intra-urban
October 30, 2008
iVPU-67

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
838863 1
1.3.6.1.4.1.161.3 .3.10.5.18.1.5.2. 1.11.1.1.<PEER _IVPU_ID>
1-252
229632 0
236057 6
Processing Fault, Illegal Configuration Change Equipment Fault, Device Removal Detected Equipment Fault, Hardware Fault Detected Equipment Fault, Subcomponent Fault Equipment Fault, Power Supply Input Circuit Fault Environmental Fault, Bus Under Voltage Threshold Exceeded Environmental Fault, Temperature High Threshold Exceeded Environmental Fault, Temperature Very High Threshold Exceeded
236108 8
236288 0
236416 0
environment FailureEven t environment FailureEven t environment FailureEven t
242585 6
242713 6
242764 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.4.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.4.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.4.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.4.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.4.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.4.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.4.<DEV_I D> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.2.1.1.4.<DEV_I D>
IVPU_P OWER_ SUPPLY IVPU_P OWER_ SUPPLY IVPU_P OWER_ SUPPLY IVPU_P OWER_ SUPPLY IVPU_P OWER_ SUPPLY IVPU_P OWER_ SUPPLY IVPU_P OWER_ SUPPLY IVPU_P OWER_ SUPPLY
1-2
IP address>,<destinati on port>. <CORR_TAG> Rcvd InfoRsp, <source device type>,<source device ID>,<source IP address>,<source port>,<destination IP address>,<destinati on port>. <CORR_TAG> <EID> <obj class attribute> <CORR_TAG> <EID>
iSG.
Clear
EMPTY
EMPTY
EMPTY
N U
iVPU receives the intra-urban audio route information response and can set up the audio route with this intra-urban iVPU.
Critical
EMPTY
1-2
Critical
EMPTY
1-2
<CORR_TAG> <EID> Power supply -48V <CORR_TAG> <EID> Power supply -48V. Fan Failure <CORR_TAG> <EID> Power supply -48V <CORR_TAG> <EID> Battery
Critical
5308592
1-2
Minor
EMPTY
1-2
Critical
65537
1-2
Minor
EMPTY
1-2
<CORR_TAG> <EID> Power supply -48V <CORR_TAG> <EID> Power supply -48V
Minor
EMPTY
1-2
Critical
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
Check configuration
R C
N U
EMPTY
Reseat hardware. Monitor. If recurring, replace hardware Reseat hardware. Monitor. If recurring, replace hardware Reseat hardware. Monitor. If recurring, replace hardware Self correcting. If recurring, reseat hardware. Monitor. If recurring, replace hardware. Reset hardware. If recurring, replace hardware. Reset hardware. If recurring, reseat hardware. If recurring, replace hardware. Reset hardware. If recurring, replace hardware.
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
iVPU-68
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
65537
Device Out of Service : Device Locked Device Out of Service : Device Locked Device Out of Service : Contact Lost
65537
419430 5
IVPU_SP ROC
2, 18
<CORR_TAG> Operator Locked Device <CORR_TAG> Operator Locked Device <CORR_TAG> Payload Alive Timeout After Initialization
Critical
EMPTY
IVPU_SP ROC
2, 18
Critical
EMPTY
IVPU_SP ROC
2, 18
Critical
5243280
Unlock hardware. If recurring, reset hardware. If recurring, contact CNRC. Unlock device
EMPTY
R C
N U
EMPTY
R C
N U
419430 5
Device Out of Service : Contact Lost Device Out of Service : Software Failure Low Memory : Operator Warning
419430 6
419430 7
432538 0
Low Memory : Critical Reset
524296 0
Application Heartbeat Failure
524297 6
Application Messaging Failure
524297 6
Application Messaging Failure
IVPU_SP ROC
2, 18
<CORR_TAG> Resource Does Not Register <CORR_TAG> Application HeartBeat Failed <CORR_TAG> Low Memory <5MB warning threshold exceeded <CORR_TAG> Low Memory <1MB reset threshold exceeded <CORR_TAG> <EID>
Critical
2169601, 5243280
IVPU_SP ROC
2, 18
Critical
5308496, 5243280
IVPU_SP ROC
2, 18
Major
EMPTY
IVPU_SP ROC
2, 18
Critical
EMPTY
IVPU_SP ROC
2,18
Critical
EMPTY
IVPU_SP ROC
2, 18
<CORR_TAG>
Critical
EMPTY
IVPU_SP ROC
2, 18
<CORR_TAG> RM Message Queue Full
Critical
EMPTY
Check the presence of hardware. If recurring, check config. If recurring, contact CNRC. The device will self recover after a reset. If recurring, contact CNRC> Self correcting/May need to re-engineer for proper capacity increase. If recurring, may need to re-engineer for proper capacity increase. Self correcting. If recurring, check configuration. If recurring, contact CNRC. Self correcting. If recurring, contact CNRC.
R C
N U
The device may be reset or locked. If there was a redundant SPROC, it will not cause any system impact. EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
524308 8
Application Initialization Failure
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2.
IVPU_SP ROC
2, 18
<CORR_TAG>
Critical
EMPTY
0x0000 0000 -
R C
N U
If there is a redundant SPROC, the redundant device will take over If there is a redundant
October 30, 2008
iVPU-69

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
1.1.1.1.2.<SLOT _ID>
0xFFFF FFFF
524308 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
<CORR_TAG> RM HeartBeat Failure
Critical
EMPTY
R C
N U
524308 8
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
<CORR_TAG> RM Initialization Failure
Critical
EMPTY
R C
N U
524313 6
Multicast Failure
524328 0
Application Platform Failure
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
<CORR_TAG>
Critical
EMPTY
IVPU_SP ROC
2, 18
<CORR_TAG>
Critical
EMPTY
Self correcting. If recurring, check configuration. If recurring, contact CNRC. Self correcting. If recurring, contact CNRC.
R C
N U
SPROC, the redundant device will take over. If there is a redundant SPROC, the redundant device will take over. If there is a redundant SPROC, the redundant device will take over. EMPTY
R C
N U
524332 8
Incomplete Dataload
524334 4
All Active Calls Released
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
IVPU_SP ROC
2, 18
<CORR_TAG> Partial Data Download. Regenerate Files. <CORR_TAG>
Critical
EMPTY
Warni ng
EMPTY
Regenerate download files and retry.
N U
This alarm will be reported when an application component fails its heartbeat. The device will recover by a reset. If there was a redundant SPROC, it will lead to a SPROC failover. EMPTY
838876 3
SPROC CPU Overload Level 1
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
<CORR_TAG> iVPUd mode, no site affected
Major
EMPTY
Self correcting. If recurring, check configuration. If recurring, may need to reengineer for proper capacity increase (see planning guide). Contact CNRC.
N U
EMPTY
R C
N U
Unexpected condition.
iVPU-70
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
838876 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
<CORR_TAG> iVPUdi mode, new interconnect calls are prevented
Major
EMPTY
838876 3
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
<CORR_TAG> iVPUi mode, new interconnect calls are prevented
Major
EMPTY
R C
N U
838876 4
838876 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
<CORR_TAG> iVPUd mode, no site affected <CORR_TAG> iVPUdi mode, new interconnect calls are prevented
Major
EMPTY
IVPU_SP ROC
2, 18
Major
EMPTY
Contact CNRC.
R C
N U
To self correct, the iVPU shall request to stop new inter connect services. If condition persists, operator needs to reduce traffic from sites to iVPU. To self correct, the iVPU shall request to stop new inter connect services. If condition persists, operator needs to reduce traffic from sites to iVPU. Unexpected condition.
R C
N U
838876 4
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
Major
EMPTY
R C
N U
To self correct, the iVPU shall request to stop new inter connect services. If condition persists, operator needs to reduce traffic from sites to iVPU. To self correct, the iVPU shall request to stop new inter connect services. If condition
October 30, 2008
iVPU-71

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
838876 5
838876 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
<CORR_TAG> iVPUd mode, no site affected <CORR_TAG> iVPUdi mode, new interconnect calls are prevented
Major
EMPTY
IVPU_SP ROC
2, 18
Major
EMPTY
Contact CNRC.
R C
N U
persists, operator needs to reduce traffic from sites to iVPU. Unexpected condition.
R C
N U
838876 5
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
Major
EMPTY
R C
N U
845414 5
High Voice Processing Usage
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID>
IVPU_SP ROC
2, 18
<CORR_TAG> SAR CPU Utilization (##%)
Warni ng
EMPTY
Warning only. Self correcting. If recurring, check configuration.
R C
N U
845414 5
High Voice Processing Usage
229964 8
Processing Fault, Warmup in Progress
1.3.6.1.4.1.161.3 .3.10.5.19.1.1.2. 1.1.1.1.2.<SLOT _ID> 1.3.6.1.4.1.161.3 .3.10.5.19.1.2.1. 2.0
IVPU_SP ROC
2, 18
<CORR_TAG> Reached full capacity <CORR_TAG> <EID>
Minor
EMPTY
IVPU_SY NCHRO NIZATIO N
Critical
EMPTY
Warning only. Self correcting. If recurring, check configuration. Self correcting. If recurring, check hardware. If recurring, contact CNRC
R C
N U
To self correct, the iVPU shall request to stop new inter connect services. If condition persists, operator needs to reduce traffic from sites to iVPU. To self correct, the iVPU shall request to stop new inter connect services. If condition persists, operator needs to reduce traffic from sites to iVPU. RFC:(SR16.0 release): Modified alarm code text for correct information. EMPTY
R C
N U
EMPTY
iVPU-72
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
229964 8
Processing Fault, Warmup in Progress
1.3.6.1.4.1.161.3 .3.10.5.19.1.2.1. 2.0
IVPU_SY NCHRO NIZATIO N IVPU_TE RCKT_R G IVPU_TE RCKT_R G IVPU_TE RCKT_R G IVPU_VP F
524336 0
Loss Of Function
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.1. 4.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.1. 4.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.1. 4.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.4.2. 1.1.1.<BPP2_ID > 1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 3.0
<CORR_TAG> <EID> OCXO in Progress of Initialization and Warmup <CORR_TAG> <EID>
Critical
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
Self correcting. If recurring, check hardware. If recurring, contact CNRC.
EMPTY
Critical
EMPTY
Check the state of DOC3 boards. If persists, contact CNRC. Activate both ocPorts on active doc3
R C
N U
EMPTY
524336 1
Loss of Capacity
<CORR_TAG> <EID>
Major
EMPTY
N U
EMPTY
524336 2
Loss of Redundancy
<CORR_TAG> <EID>
Minor
65537, 2164224
524329 6
Application Platform Failure
3-17
<CORR_TAG> <EID>
Critical
EMPTY
Self correcting. If recurring, activate the disabled standby doc3. If recurring, check the state of ISB. Reset the SPROC in the maintenance windows. If recourring, contact CNRC. EMPTY
N U
EMPTY
N U
EMPTY
524315 2
Capacity Greatly Reduced
IVPU_VP F_RG
524316 8
Capacity Reduced
1.3.6.1.4.1.161.3 .3.10.5.18.1.4.1. 3.0
IVPU_VP F_RG
838861 2
VTLink Rollup container
1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 4.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1.
IVPU_VT _LINK
<CORR_TAG> <EID> Capacity loss reached X%; current capacity allow for N voice calls. Where X is the amount of capacity lost (i.e. 100 - current capacity) <CORR_TAG> <EID> Capacity loss reached X%; current capacity allow for N voice calls. Where X is the amount of capacity lost (i.e. 100 - current capacity) <CORR_TAG> <EID> Caused By: VTLINK <CORR_TAG> <EID> Caused By:
Critical
EMPTY
R C
N U
EMPTY
Major
EMPTY
EMPTY
R C
N U
EMPTY
Critical
2361088
838861 2
VTLink Rollup container
IVPU_VT _LINK
Major
2361088
0x0000 0000 0xFFFF FFFF 0x0000 0000 -
Activate the vtSpans that are out of service. If recurring, contact CNRC. Activate the vtSpans that are out of service
R C
N U
EMPTY
R C
N U
EMPTY
October 30, 2008
iVPU-73

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
4.0 qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent 537425 6 Remote Alarm 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID> IVPU_VT _SPAN 11-184 | 21284 11-184 | 21284
VTLINK <CORR_TAG> Critical EMPTY
537425 6
Remote Alarm
IVPU_VT _SPAN
<CORR_TAG> RACRC
Critical
EMPTY
0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
Check the alarm at the far end to trouble shoot the alarm. If recurring, contact CNRC. Verify T1/E1 configuration. Check the span source to correct the problem. Check clock sources. Check the alarm at the far end to trouble shoot the alarm. If recurring, contact CNRC.
R C
N U
EMPTY
R C
N U
537425 6
Remote Alarm
537425 6
Remote Alarm
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID>
IVPU_VT _SPAN
11-184 | 21284 11-184 | 21284
<CORR_TAG> RAI
Critical
EMPTY
IVPU_VT _SPAN
<CORR_TAG> RAIC
Critical
EMPTY
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent
537425 6
Remote Alarm
537425 6
Remote Alarm
537427 2
RED Alarm
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID>
IVPU_VT _SPAN
11-184 | 21284 11-184 | 21284 11-184 | 21284
<CORR_TAG> RFI
Critical
EMPTY
IVPU_VT _SPAN
<CORR_TAG> YELLOW
Critical
EMPTY
IVPU_VT _SPAN
<CORR_TAG>
Critical
EMPTY
537427 2
RED Alarm
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID>
IVPU_VT _SPAN
11-184 | 21284
<CORR_TAG> CFA
Critical
EMPTY
Check the alarm at the far end to trouble shoot the alarm. If recurring, contact CNRC. Make sure that the VT Mapping of the VPU matches with the Far End. The default value in VPU is Byte Synchronous mapping. Most DACS support only Asynchronous Mapping. If recurring, contact CNRC. Check the alarm at the far end to trouble shoot the alarm. If recurring, contact CNRC. Check the alarm at the far end to trouble shoot the alarm. If recurring, contact CNRC. 1) DOC3 T1 framing format should match with the far end framing format. 2) Ensure that the T1 cable is connected and the cable is in good condition. 1) DOC3 T1 framing format should match with the far end framing format. 2) Ensure that the T1 cable is connected and the cable
R C
N U
RACRC Remote Alarm Cyclic Redundancy Check - Remote End has detected excess of E1 CRC Errors. EMPTY
R C
N U
RAICI - Remote Alarm Indication Customer Interface.
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
iVPU-74
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Sever ity
Related Alarms
Remedy
O u t a g e
Comments & Notes
537427 2
RED Alarm
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID>
IVPU_VT _SPAN
11-184 | 21284
<CORR_TAG> LOP
Critical
EMPTY
537427 2
RED Alarm
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID>
IVPU_VT _SPAN
11-184 | 21284
<CORR_TAG> PLM
Critical
EMPTY
537427 2
RED Alarm
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID>
IVPU_VT _SPAN
11-184 | 21284
<CORR_TAG> RED
Critical
EMPTY
537427 2
RED Alarm
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID>
IVPU_VT _SPAN
11-184 | 21284
<CORR_TAG> UNEQ
Critical
EMPTY
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent equipmentF ailureEvent
537428 8
AIS Alarm
537428 8
AIS Alarm
838876 6
MPS Physical Connection Failure
1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.2.2. 4.1.1.<VTSPAN_ ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.1.2. 3.1.1.<ICP_NOD E_ID>
IVPU_VT _SPAN
11-184 | 21284 11-184 | 21284 11-184 | 21284
<CORR_TAG> AIS
Critical
EMPTY
IVPU_VT _SPAN
<CORR_TAG> AISC
Critical
EMPTY
IVPU_VT _SPAN
<CORR_TAG> Mps Physical Connection Failure: Dsp Out of Service <CORR_TAG> Mps Physical Connection Failure: VtSpan Out of Service <CORR_TAG> <EID> Operator Locked Device
Major
EMPTY
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
838876 6
MPS Physical Connection Failure
IVPU_VT _SPAN
11-184 | 21284
Major
EMPTY
65537
IVPU_XB L
1-336
Critical
EMPTY
is in good condition. 1) DOC3 T1 framing format should match with the far end framing format. 2) Ensure that the T1 cable is connected and the cable is in good condition. 1) DOC3 T1 framing format should match with the far end framing format. 2) Ensure that the T1 cable is connected and the cable is in good condition. 1) DOC3 T1 framing format should match with the far end framing format. 2) Ensure that the T1 cable is connected and the cable is in good condition. 1) DOC3 T1 framing format should match with the far end framing format. 2) Ensure that the T1 cable is connected and the cable is in good condition. Provision/loopback T1/E1 source for the VT at the FAR end . If recurring, contact CNRC. Provision/loopback T1/E1 source for the VT at the FAR end . If recurring, contact CNRC. if it's due to vtspan oos, lock and unlock the vtspan to bring it back ins. If it's due to dsp oos, no action is needed. if it's due to vtspan oos, lock and unlock the vtspan to bring it back ins. If it's due to dsp oos, no action is needed. Unlock XBL. If recurring, reset hardware. If recurring, contact CNRC.
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
R C
N U
EMPTY
October 30, 2008
iVPU-75

Alarm Type
Alarm Code
Release SR17.0
Alarm Code Text
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Remedy
O u t a g e
Comments & Notes
845414 8
Communication Failure with iCP
845415 1
Version Mismatch Alarm
1.3.6.1.4.1.161.3 .3.10.5.18.1.1.2. 3.1.1.<ICP_NOD E_ID> 1.3.6.1.4.1.161.3 .3.10.5.18.1.1.2. 3.1.1.<ICP_NOD E_ID>
IVPU_XB L
1-336
<CORR_TAG> <EID> Link Lost
Critical
EMPTY
IVPU_XB L
1-336
<CORR_TAG> <EID> XBL Version mismatch for XBL <XBL_ID>. Alarm Set/Cleared
Major
EMPTY
Check the connectivity with iCP node
EMPTY
The software version running on iVPU does not match the version running on iCP. Upgrade iCP or iVPU to compatible software versions.
R C
N U
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent
838874 8
XBL Link Down
1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 6.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 6.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 6.0 1.3.6.1.4.1.161.3 .3.10.5.18.1.1.1. 6.0
IVPU_XB L_CONT AINER IVPU_XB L_CONT AINER IVPU_XB L_CONT AINER IVPU_XB L_CONT AINER
838874 8
XBL Link Down
838876 7
All XBL Links Down
838876 7
All XBL Links Down
<CORR_TAG> Container State Changed to Impaired <CORR_TAG> Container State Changed to Impaired <CORR_TAG> Container State Changed to Disabled <CORR_TAG> Container State Changed to Disabled
Major
65537, 5243408, 8454148 65537, 5243408, 8454148 65537, 5243408, 8454148 65537, 5243408, 8454148
Clear
Critical
Clear
0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF 0x0000 0000 0xFFFF FFFF
N U
This alarm is raised when the XBL versions on the iVPU and iCP do not match. The iVPU and iCP must be upgraded to compatible versions. RFC: SR1075: Modified Remedy for the correct information, also changed the alarm type. EMPTY
N U
N U
N U
iVPU-76
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
Reason Code
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF
Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx>
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.1.<DEV_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.1.<DEV_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.5.<DEV_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.5.<DEV_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.5.<DEV_ID>
IVPU_AI O IVPU_AI O IVPU_BI TS IVPU_BI TS IVPU_BI TS
U-DIdl U-E-A
U-E-A
EMPTY
EMPTY
Device has been enabled Device was disabled Device has been enabled Device has been enabled Device was disabled
S t a t u s N U
Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Changes will have the same CORR_TAG. iVPU will switch to a redundant clock source, either a vtSpan ir one is configured and enabled or to an internal ISB clock source. Related Alarms & State Change will have the same CORR_TAG
U-DIdl U-E-A
EMPTY
EMPTY
N U
U-DIdl U-DIdl U-E-A
EMPTY
EMPTY
N U
U-E-Idl
EMPTY
EMPTY
N U
U-DIdl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
Correlation Tag <xxxxxxxx>
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.5.<DEV_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.7.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.7.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.7.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.7.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1.
IVPU_BI TS
U-E-Idl
U-E-A
EMPTY
EMPTY
IVPU_BP P2 IVPU_BP P2 IVPU_BP P2 IVPU_BP P2 IVPU_BP P2
3-17
L-D-Idl
U-DIdl L-D-Idl
EMPTY
EMPTY
Device has been enabled and providing service Unlock disabled device Disabled device has been locked Device has been enabled Active device has been admin locked Active device has been
N U
N U
Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG.
3-17
U-DIdl U-DIdl U-E-A
EMPTY
65537
N U
3-17
U-E-Idl
EMPTY
EMPTY
N U
3-17
L-D-Idl
EMPTY
65537
N U
3-17
U-E-A
U-DIdl
EMPTY
EMPTY
N U
October 30, 2008
iVPU-77

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1.7.<SLOT_ID> esmrStateCh angeEvent esmrStateCh angeEvent 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.7.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.7.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.7.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.1.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.1.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.1.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.1.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.1.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.1.<SLOT_ID> IVPU_BP P2 IVPU_BP P2 3-17 U-E-Idl L-D-Idl EMPTY 65537
disabled/failed Device has been admin locked Device failed to initialize N U
Call processing Capacity will be impacted Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. Call processing Capacity will be impacted Related Alarms & State Change will have the same CORR_TAG
3-17
U-E-Idl
U-DIdl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
IVPU_BP P2
3-17
U-E-Idl
U-E-A
EMPTY
EMPTY
0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF
Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx>
IVPU_C CA IVPU_C CA IVPU_C CA IVPU_C CA IVPU_C CA IVPU_C CA
1,19
L-D-Idl
U-DIdl U-E-Idl
EMPTY
EMPTY
Device has been enabled and providing service Unlocked a disabled device Admin unlock, device is ready for use Disabled device has been admin locked Device has been enabled Active device has been admin locked Active device failed or reset
N U
N U
Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. If there is a standby device then it will take over the active role. For a successful failover, one should see a U-E-Idl to U-E-A transition on the other CCA. Does not affect call processing Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG.
1,19
L-D-Idl
EMPTY
EMPTY
N U
1,19
U-DIdl U-DIdl U-E-A
L-D-Idl
EMPTY
65537
N U
1,19
U-E-Idl
EMPTY
EMPTY
N U
1,19
L-D-Idl
EMPTY
65537
N U
1,19
U-E-A
U-DIdl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF
Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx>
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.1.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.1.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.1.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.4.0
IVPU_C CA IVPU_C CA IVPU_C CA IVPU_D AP_CON
1,19
U-E-Idl
L-D-Idl
EMPTY
65537
1,19
U-E-Idl
U-DIdl U-E-A
EMPTY
EMPTY
Device has been admin locked Standby device failed or reset Standby device has become active The only one link in this
N U
N U
1,19
U-E-Idl
EMPTY
EMPTY
N U
U-DIdl
U-E-A
EMPTY
8388737
N U
iVPU-78
October 30, 2008
Release SR17.0
State Changes
Reason Code

MOI Info (Label) Inst From State To State Related State Changes
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
TAINER
container is back in service 1 U-DIdl U-EImp EMPTY 8388728 At least one HADAP link represented by this container has become enabled The only one link in this container is disabled One or more HADAP links represented by this container is disabled All HADAP links represented by this container are disabled All the HADAP links represented by this container are fully functional again iVPU-DAP link is unlocked and the logical link is down. EMPTY N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.4.0
IVPU_D AP_CON TAINER
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.4.0
IVPU_D AP_CON TAINER IVPU_D AP_CON TAINER
U-E-A
U-DIdl
EMPTY
8388737
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.4.0
U-E-A
U-EImp
EMPTY
8388728
N U
This container has only one link equipped. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. At least one of the DAP link in this container is still not functioning. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. Related Alarms & State Change will have the same CORR_TAG. At least one of the DAP link in this container is not functioning. Related Alarms & State Change will have the same CORR_TAG. All the DAP link in this containes are disabled Related Alarms & State Change will have the same CORR_TAG. All the DAP link in this container are active and in a service providing role. The alarms in Related Alarms column are clear ones. Note: The alarm in Related Alarms column is clear one.
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.4.0
IVPU_D AP_CON TAINER IVPU_D AP_CON TAINER
U-EImp
U-DIdl
EMPTY
8388737
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.4.0
U-EImp
U-E-A
EMPTY
8388728
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.4.6.1. 1.<DAP_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.4.6.1. 1.<DAP_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.4.6.1. 1.<DAP_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.4.6.1. 1.<DAP_ID>
IVPU_D AP_LINK
1-15
L-D-Idl
U-DIdl
EMPTY
65537
N U
0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF
Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx>
IVPU_D AP_LINK IVPU_D AP_LINK IVPU_D AP_LINK
1-15
L-D-Idl
U-E-Idl
EMPTY
EMPTY
N U
1-15
U-DIdl U-DIdl
L-D-Idl
EMPTY
65537
iVPU-DAP link is locked. TCP/IP connectivity established and Link Version Check Procedure passed.
N U
U-E-Idl is a transitional state. This transition should not happen. Note: The alarm in Related Alarms column is report one. U-E-Idl is a transitional state while the DAP link goes enabled. It is expected to go to U-E-A state immediately. iVPU can communicate with this DAP. Note: The alarms in Related Alarms column are clear ones.
1-15
U-E-Idl
EMPTY
8,388,625, 8,388,627, 8,388,637, 8,388,647, 8,388,648, 8,388,649
N U
October 30, 2008
iVPU-79

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
0000 0000 FFFF FFFF 0000 0000 FFFF FFFF
Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx>
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.4.6.1. 1.<DAP_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.4.6.1. 1.<DAP_ID>
IVPU_D AP_LINK IVPU_D AP_LINK
1-15
U-E-A
L-D-Idl
EMPTY
65537
iVPU-DAP link is locked. TCP/IP connectivity lost or Link Continuity Check failed or Link Version Down received from DAP or OLCC changed or IP Footprint changed. EMPTY
S t a t u s N U
Note: The alarm in Related Alarms column is report one. iVPU cannot communicate with this DAP. All the existing calls for this DAP will be deleted if this DAP was previously up and went down. Note: The alarms in Related Alarms column are report ones. RFC: There is a minor change in SR15.0 event description to add IP Footprint impact on this state change. U-E-Idl is a transitional state. This transition should not happen. U-E-Idl is a transitional state. This transition should not happen. U-E-Idl is a transitional state while the DAP link goes enabled. iVPU can communicate with this DAP.
1-15
U-E-A
U-DIdl
EMPTY
8,388,625, 8,388,637
N U
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.4.6.1. 1.<DAP_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.4.6.1. 1.<DAP_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.4.6.1. 1.<DAP_ID>
IVPU_D AP_LINK IVPU_D AP_LINK IVPU_D AP_LINK
1-15
U-E-Idl
L-D-Idl
EMPTY
EMPTY
N U
1-15
U-E-Idl
U-DIdl U-E-A
EMPTY
EMPTY
EMPTY
N U
1-15
U-E-Idl
EMPTY
EMPTY
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.2.<DEV_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.2.<DEV_ID>
IVPU_D GBE IVPU_D GBE
1-2
U-DIdl U-E-A
U-E-A
EMPTY
EMPTY
1-2
U-DIdl
EMPTY
EMPTY
TCP/IP connectivity established and Link Version Check Procedure passed. Admin unlock, device is ready for use Device was disabled
N U
N U
Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. Lancircuit and DGBE redundacy is lost. If there was a redundant DGBE and Lancircuit available then the OMC connectivity will be maintained. As a result of this transition iVPU_NODE state will change to U-E-Imp with DGBEredundancy and U-D-Idl without DGBE redundancy Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG
N U
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.4.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1.
IVPU_D OC3 IVPU_D OC3
33, 38
L-D-Idl
U-DIdl L-D-Idl
EMPTY
EMPTY
Unlocked the standby device Disabled device has been
N U
33, 38
U-DIdl
EMPTY
65537
N U
iVPU-80
October 30, 2008
Release SR17.0
State Changes
Reason Code

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1.4.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.4.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.4.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.4.<SLOT_ID>
IVPU_D OC3 IVPU_D OC3 IVPU_D OC3
33, 38
U-DIdl U-E-A
U-E-Idl
EMPTY
EMPTY
locked Device has been enabled Active device has been admin locked Active device has been disabled/failed
N U
Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. DOC3 and ocPort redundacy is lost. If there was a redundant DOC3 and ocPorts available then there will be no impacts to call processing . As a result of this transition iVPU_NODE state will change to U-E-Imp with DOC3 redundancy and U-D-Idl without DOC3 redundancy Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG EMPTY
33, 38
L-D-Idl
EMPTY
65537
N U
33, 38
U-E-A
U-DIdl
EMPTY
EMPTY
N U
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.4.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.4.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.4.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.2.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.2.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.2.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.2.6.1. 1.<EBTS_ID>
IVPU_D OC3 IVPU_D OC3 IVPU_D OC3 IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK
33, 38
U-E-Idl
L-D-Idl
EMPTY
65537
33, 38
U-E-Idl
U-DIdl U-E-A
EMPTY
EMPTY
Device has been admin locked Device failed or reset Device has become active EBTS Link was admin unlocked
N U
N U
33, 38
U-E-Idl
EMPTY
EMPTY
N U
110000
L-D-Idl
U-DIdl
EMPTY
65537
N U
0000 0000 FFFF FFFF
110000
L-D-Idl
U-E-Idl
EMPTY
65537
EBTS Link was enabled and is in service EBTS Link was admin locked
N U
EMPTY
0000 0000 FFFF FFFF
110000
U-DIdl
L-D-Idl
EMPTY
65537
N U
EMPTY
0000 0000 FFFF FFFF
110000
U-DIdl
U-E-Idl
EMPTY
esmrStateCh
0000 0000 -
Correlation Tag
1.3.6.1.4.1.161.3.3.
IVPU_EB
1-
U-E-A
L-D-Idl
EMPTY
8388739, 8388741, 8388742, 8388743, 8388744, 8388745, 8388746 65537
EBTS Link was enabled and is in service
N U
U-E-Idl is a transitional state while link goes enabled
EBTS Link was
N U
EMPTY
October 30, 2008
iVPU-81

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
FFFF FFFF
<xxxxxxxx>
10.5.18.1.5.2.2.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.2.6.1. 1.<EBTS_ID>
0000 0000 FFFF FFFF
TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK
10000
admin locked
110000
U-E-A
U-DIdl
EMPTY
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.2.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.2.6.1. 1.<EBTS_ID>
0000 0000 FFFF FFFF
IVPU_EB TS_CON TROL_LI NK IVPU_EB TS_CON TROL_LI NK
110000
U-E-Idl
L-D-Idl
EMPTY
8388739, 8388741, 8388742, 8388743, 8388744, 8388745, 8388746 65537
EBTS Link connectivity lost
N U
EMPTY
EBTS Link was admin locked
N U
While in U-E-Idl transitional state, the link gets locked. We shall not see this transition. While in U-E-Idl transitional state, the link gets disabled. We shall not see this transition.
110000
U-E-Idl
U-DIdl
EMPTY
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.2.6.1. 1.<EBTS_ID>
110000
U-E-Idl
U-E-A
EMPTY
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.2.0
IVPU_EB TS_LINK _CONTA INER IVPU_EB TS_LINK _CONTA INER
U-DIdl
U-E-A
EMPTY
8388739, 8388741, 8388742, 8388743, 8388744, 8388745, 8388746 8388739, 8388741, 8388742, 8388743, 8388744, 8388745, 8388746 8388726
EBTS Link was disabled
N U
EBTS Link was enabled and is in service.
N U
The only one link in this container is back in service At least one EBTS link represented by this container has become enabled. The only one link in this container is out of service One or more EBTS links represented by
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.2.0
U-DIdl
U-EImp
EMPTY
8388726
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.2.0
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.2.0
IVPU_EB TS_LINK _CONTA INER IVPU_EB TS_LINK _CONTA
U-E-A
U-DIdl
EMPTY
8388726
N U
U-E-A
U-EImp
EMPTY
8388728
N U
Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. At least one of the EBTS link in this container is still not functioning. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. Related Alarms & State Change will have the same CORR_TAG. At least one of the EBTS link in
iVPU-82
October 30, 2008
Release SR17.0
State Changes
Reason Code

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
INER esmrStateCh angeEvent 0000 0000 FFFF FFFF Correlation Tag <xxxxxxxx> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.2.0 IVPU_EB TS_LINK _CONTA INER IVPU_EB TS_LINK _CONTA INER 1 U-EImp U-DIdl EMPTY 8388726
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.2.0
U-EImp
U-E-A
EMPTY
8388728
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.3.0
IVPU_EB TS_SNM P_CONT AINER IVPU_EB TS_SNM P_CONT AINER
U-DIdl
U-E-A
EMPTY
8388728
this container is disabled All EBTS links represented by this container are disabled. All the EBTS links represented by this container are fully functional again The only link in this container is back in service
this container is not functioning. N U Related Alarms & State Change will have the same CORR_TAG. All the EBTS link in this container are disabled Related Alarms & State Change will have the same CORR_TAG. All the EBTS link in this container are active and in a service providing role. Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. At least one of the EBTS SNMP link in this container is still not functioning. Related Alarms & State Change will have the same CORR_TAG. The only SNMP link in this container is not functioning. Related Alarms & State Change will have the same CORR_TAG. At least one of the EBTS SNMP link in this container is not functioning. Related Alarms & State Change will have the same CORR_TAG. All the EBTS SNMP link in this container are disabled Related Alarms & State Change will have the same CORR_TAG. All the EBTS SNMP links in this container are active and in a service providing role. The alarms in Related Alarms column are clear ones. EMPTY
N U
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.3.0
U-DIdl
U-EImp
EMPTY
8388728
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.3.0
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.3.0
IVPU_EB TS_SNM P_CONT AINER IVPU_EB TS_SNM P_CONT AINER IVPU_EB TS_SNM P_CONT AINER IVPU_EB TS_SNM P_CONT AINER
U-E-A
U-DIdl
EMPTY
8388729
At least one SNMP link represented by this container has become enabled. The only SNMP link is disabled
N U
N U
U-E-A
U-EImp
EMPTY
8388728
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.3.0
U-EImp
U-DIdl
EMPTY
8388729
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.3.0
U-EImp
U-E-A
EMPTY
8388728
One or more SNMP links represented by this container is disabled All SNMP links represented by this container are disabled. All the SNMP links represented by this container are fully functional again EBTS SNMP Link was admin unlocked EBTS SNMP
N U
N U
N U
esmrStateCh angeEvent esmrStateCh
0000 0000 FFFF FFFF 0000 0000 -
Correlation Tag <xxxxxxxx> Correlation Tag
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.3.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3.
IVPU_EB TS_SNM P_LINK IVPU_EB
110000 1-
L-D-Idl
U-DIdl U-E-Idl
EMPTY
65537
N U
L-D-Idl
EMPTY
65537
N U
EMPTY
October 30, 2008
iVPU-83

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
FFFF FFFF
<xxxxxxxx>
10.5.18.1.5.2.3.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.3.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.3.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.3.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.3.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.3.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.3.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.3.6.1. 1.<EBTS_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.3.<DEV_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.3.<DEV_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.7.0
TS_SNM P_LINK IVPU_EB TS_SNM P_LINK IVPU_EB TS_SNM P_LINK IVPU_EB TS_SNM P_LINK IVPU_EB TS_SNM P_LINK IVPU_EB TS_SNM P_LINK IVPU_EB TS_SNM P_LINK IVPU_EB TS_SNM P_LINK IVPU_FA N_TRAY IVPU_FA N_TRAY IVPU_H N_CONT AINER
10000
110000 110000
U-DIdl U-DIdl
L-D-Idl
EMPTY
65537
U-E-Idl
EMPTY
EMPTY
110000 110000 110000 110000 110000
U-E-A
L-D-Idl
EMPTY
65537
U-E-A
U-DIdl L-D-Idl
EMPTY
EMPTY
U-E-Idl
EMPTY
65537
U-E-Idl
U-DIdl U-E-A
EMPTY
EMPTY
U-E-Idl
EMPTY
EMPTY
1-4
U-DIdl U-E-A
U-E-A
EMPTY
EMPTY
1-4
U-DIdl U-E-A
EMPTY
EMPTY
Link was enabled and is in service EBTS SNMP Link was admin locked EBTS SNMP Link was enabled and is in service EBTS SNMP Link was admin locked EBTS SNMP Link connectivity lost EBTS SNMP Link was admin locked EBTS SNMP Link was disabled EBTS SNMP Link was enabled and is in service Device is enabled and active Device is disabled. The only one link in this container is back in service At least one HN link represented by this container has become enabled. The only one link in this container is disabled
N U
EMPTY
N U
N U
EMPTY
N U
EMPTY
N U
N U
N U
While in U-E-Idl transitional state, the link gets locked. We shall not see this transition. While in U-E-Idl transitional state, the link gets disabled. We shall not see this transition. U-E-Idl is a transitional state while link goes enabled
N U
Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. At least one of the HN link in this container is still not functioning.
N U
U-DIdl
EMPTY
8388757
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.7.0
IVPU_H N_CONT AINER
U-DIdl
U-EImp
EMPTY
8388728
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.7.0
IVPU_H N_CONT AINER
U-E-A
U-DIdl
EMPTY
8388757
N U
Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped.
iVPU-84
October 30, 2008
Release SR17.0
State Changes
Reason Code

Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.7.0
IVPU_H N_CONT AINER
U-E-A
U-EImp
EMPTY
8388728
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.7.0
IVPU_H N_CONT AINER IVPU_H N_CONT AINER
U-EImp
U-DIdl
EMPTY
8388757
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.7.0
U-EImp
U-E-A
EMPTY
8388728
One or more HN links represented by this container is disabled All HN links represented by this container are disabled. All the HN links represented by this container are fully functional again
S t a t u s N U
Related Alarms & State Change will have the same CORR_TAG. At least one of the HN link in this container is not functioning. Related Alarms & State Change will have the same CORR_TAG. All the HN link in this container are disabled Related Alarms & State Change will have the same CORR_TAG. All the HN link in this container are active and in a service providing role. The alarms in Related Alarms column are clear ones. U-E-Idl is a transitional state while the HN link goes enabled. It is expected to go to U-E-A state immediately. iVPU can perform voice distribution functionality for this inter-urban HN device. Note: The alarms in Related Alarms column are clear ones. iVPU cannot perform voice distribution functionality for this inter-urban HN device. Note: The alarm in Related Alarms column is report one.
N U
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.7.6.1. 1.<UANC>.<HN_ID >
IVPU_H N_LINK
UANC =116777 215 and HN_ID =1-800
U-DIdl
U-E-Idl
EMPTY
8388629, 8388638
iVPU-Interurban HN device session is established.
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.7.6.1. 1.<UANC>.<HN_ID >
IVPU_H N_LINK
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.7.6.1. 1.<UANC>.<HN_ID >
IVPU_H N_LINK
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.3.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.3.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1.
IVPU_IS B IVPU_IS B IVPU_IS B
UANC =116777 215 and HN_ID =1-800 UANC =116777 215 and HN_ID =1-800 2, 18
U-E-A
U-DIdl
EMPTY
8388638
iVPU-Interurban HN device session is terminated.
N U
U-E-Idl
U-E-A
EMPTY
EMPTY
iVPU-Interurban HN device session is established.
N U
U-E-Idl is a transitional state while the HN link goes enabled. iVPU can perform voice distribution functionality for this inter-urban HN device.
L-D-Idl
U-DIdl U-E-Idl
EMPTY
EMPTY
Device unlocked Admin unlock, device is ready for use Disabled device has been
N U
Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG
2, 18
L-D-Idl
EMPTY
EMPTY
N U
2, 18
U-DIdl
L-D-Idl
EMPTY
65537
N U
October 30, 2008
iVPU-85

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1.3.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.3.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.3.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.3.<SLOT_ID>
IVPU_IS B IVPU_IS B
2,18
U-DIdl U-E-A
U-E-Idl
EMPTY
EMPTY
locked Device has been enabled Active device has been admin locked Active device has been disabled/failed
N U
Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. If there is redundancy then the service will not be impacted. Related Alarms & State Change will have the same CORR_TAG. If there is redundancy then there will be failover and the service will not be impacted.For a successful failover, one should see a U-E-Idl to U-E-A transition on the other ISB Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. Possibly active device has failed and standby is taking over. Related Alarms & State Change will have the same CORR_TAG RFC: This state change is added in SR15.0 for IPFR feature Related Alarms & State Change will have the same CORR_TAG RFC: This state change is added in SR15.0 for IPFR feature Related Alarms & State Change will have the same CORR_TAG RFC: This state change is added in SR15.0 for IPFR feature Related Alarms & State Change will have the same CORR_TAG RFC: This state change is added in SR15.0 for IPFR feature Related Alarms & State Change
2, 18
L-D-Idl
EMPTY
65537
N U
0000 0000 FFFF FFFF
IVPU_IS B
2,18
U-E-A
U-DIdl
EMPTY
EMPTY
N U
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.3.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.3.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.3.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.8.<SLOT_ID>
IVPU_IS B IVPU_IS B IVPU_IS B
2,18
U-E-Idl
L-D-Idl
EMPTY
65537
2,18
U-E-Idl
U-DIdl U-E-A
EMPTY
EMPTY
Device has been admin locked Device failed or reset Device has become active
N U
N U
2,18
U-E-Idl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
IVPU_IS B2
2,18
L-D-Idl
U-DIdl
EMPTY
EMPTY
Device unlocked
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.8.<SLOT_ID>
IVPU_IS B2
2,18
L-D-Idl
U-E-Idl
EMPTY
EMPTY
Admin unlock, device is ready for use
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.8.<SLOT_ID>
IVPU_IS B2
2,18
U-DIdl
L-D-Idl
EMPTY
65537
Disabled device has been locked
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.8.<SLOT_ID>
IVPU_IS B2
2,18
U-DIdl
U-E-Idl
EMPTY
EMPTY
Device has been enabled
N U
esmrStateCh
0000 0000 -
Correlation Tag
1.3.6.1.4.1.161.3.3.
IVPU_IS
2,18
U-E-A
L-D-Idl
EMPTY
65537
Active device
N U
iVPU-86
October 30, 2008
Release SR17.0
State Changes
Reason Code

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
FFFF FFFF
<xxxxxxxx>
10.5.19.1.1.2.1.1.1. 1.8.<SLOT_ID>
B2
has been admin locked
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.8.<SLOT_ID>
IVPU_IS B2
2,18
U-E-A
U-DIdl
EMPTY
EMPTY
Active device has been disabled/failed
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.8.<SLOT_ID>
IVPU_IS B2
2,18
U-E-Idl
L-D-Idl
EMPTY
65537
Device has been admin locked
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.8.<SLOT_ID>
IVPU_IS B2
2,18
U-E-Idl
U-DIdl
EMPTY
EMPTY
Device failed or reset
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.8.<SLOT_ID>
IVPU_IS B2
2,18
U-E-Idl
U-E-A
EMPTY
EMPTY
Device has become active
N U
0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 -
Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.6.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.6.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.6.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.6.<SLOT_ID> 1.3.6.1.4.1.161.3.3.
IVPU_LA NCIRCUI T IVPU_LA NCIRCUI T IVPU_LA NCIRCUI T IVPU_LA NCIRCUI T IVPU_LA
1-4
L-D-Idl
U-DIdl L-D-Idl
EMPTY
EMPTY
Device unlocked Active device has been admin locked Device has been enabled Active device has been admin locked Active device
N U
will have the same CORR_TAG. If there is redundancy then the service will not be impacted. RFC: This state change is added in SR15.0 for IPFR feature Related Alarms & State Change will have the same CORR_TAG. If there is redundancy then there will be failover and the service will not be impacted.For a successful failover, one should see a U-E-Idl to U-E-A transition on the other ISB RFC: This state change is added in SR15.0 for IPFR feature Related Alarms & State Change will have the same CORR_TAG RFC: This state change is added in SR15.0 for IPFR feature Related Alarms & State Change will have the same CORR_TAG RFC: This state change is added in SR15.0 for IPFR feature Related Alarms & State Change will have the same CORR_TAG. Possibly active device has failed and standby is taking over. RFC: This state change is added in SR15.0 for IPFR feature Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change
1-4
U-DIdl U-DIdl U-E-A
EMPTY
65537
N U
1-4
U-E-Idl
EMPTY
EMPTY
N U
1-4
L-D-Idl
EMPTY
65537
N U
1-4
U-E-A
U-D-
EMPTY
EMPTY
N U
October 30, 2008
iVPU-87

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
FFFF FFFF
<xxxxxxxx>
10.5.19.1.1.2.1.1.1. 1.6.<SLOT_ID>
NCIRCUI T
Idl
has been disabled/failed
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.6.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.6.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.6.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.8.0
IVPU_LA NCIRCUI T IVPU_LA NCIRCUI T IVPU_LA NCIRCUI T IVPU_LO AD_CON TAINER IVPU_LO AD_CON TAINER IVPU_M DG_CO NTAINE R IVPU_M DG_CO NTAINE R
1-4
U-E-Idl
L-D-Idl
EMPTY
65537
1-4
U-E-Idl
U-DIdl U-E-A
EMPTY
EMPTY
Device has been admin locked Device failed or reset Device has been enabled iVPU exited a load shedding condition iVPU entered a load shedding condition The only one link in this container is back in service At least one MDG link represented by this container has become enabled. The only one link in this container is disabled One or more MDG links represented by this container is disabled All MDG links represented by this container
N U
will have the same CORR_TAG. If there was a redundant lancircuit available then there will be no loss of OMC connectivity. As a result of this transition iVPU_NODE state will change to U-E-Imp Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. At least one of the MDG link in this container is still not functioning. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. Related Alarms & State Change will have the same CORR_TAG. At least one of the MDG link in this container is not functioning. Related Alarms & State Change will have the same CORR_TAG. All the MDG link in this
N U
1-4
U-E-Idl
EMPTY
EMPTY
N U
U-EImp
U-E-A
EMPTY
8388759
N U
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.8.0 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.5.0
U-E-A
U-EImp U-E-A
EMPTY
8388759
N U
U-DIdl
EMPTY
8388760
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.5.0
U-DIdl
U-EImp
EMPTY
8388728
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.5.0
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.5.0
IVPU_M DG_CO NTAINE R IVPU_M DG_CO NTAINE R IVPU_M DG_CO NTAINE
U-E-A
U-DIdl
EMPTY
8388760
N U
U-E-A
U-EImp
EMPTY
8388728
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.5.0
U-EImp
U-DIdl
EMPTY
8388760
N U
iVPU-88
October 30, 2008
Release SR17.0
State Changes
Reason Code

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.5.0
R IVPU_M DG_CO NTAINE R
U-EImp
U-E-A
EMPTY
8388728
are disabled. All the MDG links represented by this container are fully functional again iVPU-MDG link is unlocked and the logical link is down. EMPTY
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.5.6.1. 1.<MDG_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.5.6.1. 1.<MDG_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.5.6.1. 1.<MDG_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.5.6.1. 1.<MDG_ID>
IVPU_M DG_LIN K IVPU_M DG_LIN K IVPU_M DG_LIN K IVPU_M DG_LIN K
1-36
L-D-Idl
U-DIdl
EMPTY
65537
N U
container are disabled Related Alarms & State Change will have the same CORR_TAG. All the MDG link in this container are active and in a service providing role. The alarms in Related Alarms column are clear ones. Note: The alarm in Related Alarms column is clear one.
1-36
L-D-Idl
U-E-Idl
EMPTY
EMPTY
N U
1-36
U-DIdl U-DIdl
L-D-Idl
EMPTY
65.537
iVPU-MDG link is locked. TCP/IP connectivity established and Link Version Check Procedure passed. iVPU-MDG link is locked. TCP/IP connectivity lost or Link Continuity Check failed or Link Version Down received from MDG or OLCC changed or IP Footprint changed. EMPTY
N U
U-E-Idl is a transitional state. This transition should not happen. Note: The alarm in Related Alarms column is report one. U-E-Idl is a transitional state while the MDG link goes enabled. It is expected to go to U-E-A state immediately. iVPU can communicate with this MDG. Note: The alarms in Related Alarms column are clear ones. Note: The alarm in Related Alarms column is report one. iVPU cannot communicate with this MDG. Note: The alarms in Related Alarms column are report ones. RFC: There is a minor change in SR15.0 event description to add IP Footprint impact on this state change.
1-36
U-E-Idl
EMPTY
8,388,626, 8,388,628, 8,388,639, 8,388,650, 8,388,651
N U
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.5.6.1. 1.<MDG_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.5.6.1. 1.<MDG_ID>
1-36
U-E-A
L-D-Idl
EMPTY
65537
N U
1-36
U-E-A
U-DIdl
EMPTY
8,388,626, 8,388,639
N U
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 -
Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.5.6.1. 1.<MDG_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.5.2.5.6.1. 1.<MDG_ID> 1.3.6.1.4.1.161.3.3.
IVPU_M DG_LIN K IVPU_M DG_LIN K IVPU_M
1-36
U-E-Idl
L-D-Idl
EMPTY
EMPTY
N U
1-36
U-E-Idl
U-DIdl U-E-A
EMPTY
EMPTY
EMPTY
N U
1-36
U-E-Idl
EMPTY
EMPTY
TCP/IP
N U
U-E-Idl is a transitional state. This transition should not happen. U-E-Idl is a transitional state. This transition should not happen. U-E-Idl is a transitional state
October 30, 2008
iVPU-89

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
FFFF FFFF
<xxxxxxxx>
10.5.18.1.5.2.5.6.1. 1.<MDG_ID>
DG_LIN K
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.5.0
U-DIdl
U-EImp
EMPTY
8388613
connectivity established and Link Version Check Procedure passed. At least one device represented by this container has become enabled. One or more devices represented by this container is disabled All hardware represented by this container are disabled.
while the MDG link goes enabled. iVPU can communicate with this MDG.
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.5.0
U-E-A
U-EImp
EMPTY
8388613
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.5.0
U-EImp
U-DIdl
EMPTY
8388613
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.5.0
U-EImp
U-E-A
EMPTY
EMPTY
All the devices represented by this container are fully functional again
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.6.0
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.6.0
IVPU_M PS_FR_ CHAN_C ONTAIN ER IVPU_M PS_FR_ CHAN_C ONTAIN ER
U-DIdl
U-E-A
EMPTY
8388761
The only one link in this container is back in service At least one MPS FR channel represented by this container has become enabled. The only one link in this container is
N U
U-DIdl
U-EImp
EMPTY
8388762
N U
Related Alarms & State Change will have the same CORR_TAG. At least one of the entities that this containes (power supply modules, fan trays or BITS, if provisioned) is still not functioning. Related Alarms & State Change will have the same CORR_TAG. At least one of the entities that this containes (power supply modules, fan trays or BITS, if provisioned) is not functioning. Related Alarms & State Change will have the same CORR_TAG. All the entities that this contains (power supply modules, fan trays and the BITS, if provisioned) are disabled Related Alarms & State Change will have the same CORR_TAG. All the entities that this contains (power supply modules, fan trays and the BITS, if provisioned) are active and in a service providing role. Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. At least one of the MPS channel in this container is still not functioning.
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.6.0
IVPU_M PS_FR_ CHAN_C
U-E-A
U-DIdl
EMPTY
8388761
N U
Related Alarms & State Change will have the same CORR_TAG. This container has only one link
iVPU-90
October 30, 2008
Release SR17.0
State Changes
Reason Code

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.6.0
ONTAIN ER IVPU_M PS_FR_ CHAN_C ONTAIN ER IVPU_M PS_FR_ CHAN_C ONTAIN ER IVPU_M PS_FR_ CHAN_C ONTAIN ER
disabled 1 U-E-A U-EImp EMPTY 8388762 One or more MPS FR channels represented by this container is disabled All MPS FR channels represented by this container are disabled. All the MPS FR channels represented by this container are fully functional again Node's availability maybe impaired. N U
equipped. Related Alarms & State Change will have the same CORR_TAG. At least one of the MPS channel in this container is not functioning. Related Alarms & State Change will have the same CORR_TAG. All the MPS channels in this containes are disabled Related Alarms & State Change will have the same CORR_TAG. All the MPS channels in this container are active and in a service providing role. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. Node container represents the following devices: CCA, SPROC, AIO, BPP2, DOC3, OCPORT, ISB, DGBE, XBL, MISC_CONTAINER . At least one instance of a device type, has come into service. Depending on what device is not functional, there may be a capacity impairment. Related Alarms & State Change will have the same CORR_TAG. Node container represents the following devices: CCA, SPROC, AIO, BPP2, DOC3, OCPORT, ISB, DGBE, XBL, MISC_CONTAINER . At least one instance of these devices, is disabled. Depending on what device is not functional, there may be a capacity impairment. Related Alarms & State Change will have the same CORR_TAG. Node container represents the following devices:CCA, SPROC,
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.6.0
U-EImp
U-DIdl
EMPTY
8388761
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.5.1.6.0
U-EImp
U-E-A
EMPTY
8388762
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.2.0
IVPU_N ODE
U-DIdl
U-EImp
EMPTY
8388610
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.2.0
IVPU_N ODE
U-E-A
U-EImp
EMPTY
8388610
Node's availability maybe impaired.
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.2.0
IVPU_N ODE
U-EImp
U-DIdl
EMPTY
8388611
Node not functional.
N U
October 30, 2008
iVPU-91

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.2.0
IVPU_N ODE
U-EImp
U-E-A
EMPTY
EMPTY
Node is fully functional
N U
1.3.6.1.4.1.161.3.3. 10.5.18.1.2.2.2.1.1. <OCBANK_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.2.2.2.1.1. <OCBANK_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.2.2.2.1.1. <OCBANK_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.2.2.2.1.1. <OCBANK_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.5.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.5.<SLOT_ID>
IVPU_O CBANK IVPU_O CBANK
1-2
U-DIdl U-E-A
U-E-Idl
EMPTY
EMPTY
Device has been enabled Active device has been disabled/failed Device failed to initialize Device has become available Device has been enabled
N U
AIO, BPP2, DOC3, OCPORT, ISB, DGBE, XBL, MISC_CONTAINER . All instances of a device type is disabled. Related Alarms & State Change will have the same CORR_TAG. Node container represents the following devices: CCA, SPROC, AIO, BPP2, DOC3, OCPORT, ISB, DGBE, XBL, MISC_CONTAINER The only disabled device ( representing the node) has come into service. Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. Call processing impaired. Lost resources on one OC3 link. Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG
1-2
U-DIdl
EMPTY
65537
N U
IVPU_O CBANK IVPU_O CBANK IVPU_O CPORT
1-2
U-E-Idl
U-DIdl U-E-A
EMPTY
EMPTY
N U
1-2
U-E-Idl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
IVPU_O CPORT
331332, 381382 331332, 381382
U-DIdl
U-E-Idl
EMPTY
EMPTY
N U
U-E-A
U-DIdl
EMPTY
65537
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.5.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.5.<SLOT_ID> 1.3.6.1.4.1.161.3.3.
IVPU_O CPORT
0000 0000 FFFF FFFF
IVPU_O CPORT
esmrStateCh
0000 0000 -
Correlation Tag
IVPU_P
331332, 381382 331332, 381382 1-2
U-E-Idl
U-DIdl
EMPTY
EMPTY
Device failed to initialize
N U
Related Alarms & State Change will have the same CORR_TAG. If both ocports on the standby DOC3 are active then it will take over and there will be no call processing/capacity loss. Related Alarms & State Change will have the same CORR_TAG
U-E-Idl
U-E-A
EMPTY
EMPTY
Device has become available Disabled device
N U
Related Alarms & State Change will have the same CORR_TAG
U-D-
U-E-A
EMPTY
EMPTY
N U
Related Alarms & State Change
iVPU-92
October 30, 2008
Release SR17.0
State Changes
Reason Code

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
FFFF FFFF 0000 0000 FFFF FFFF
<xxxxxxxx> Correlation Tag <xxxxxxxx>
10.5.19.1.1.2.1.2.1. 1.4.<DEV_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.2.1. 1.4.<DEV_ID>
OWER_ SUPPLY IVPU_P OWER_ SUPPLY
Idl 1-2 U-E-A U-DIdl EMPTY EMPTY
has been enabled Active device has been disabled/failed
will have the same CORR_TAG N U Related Alarms & State Change will have the same CORR_TAG. Maintanence required. A failure of the redundant power supply will result in outage. Related Alarms & State Change will have the same CORR_TAG. This state change will be preceded by the DOC3's state change events. Related Alarms & State Change will have the same CORR_TAG. This state change will be preceded by the DOC3's state change events. Related Alarms & State Change will have the same CORR_TAG. This state change will be preceded by the DOC3's state change events. Related Alarms & State Change will have the same CORR_TAG. This state change will be preceded by the DOC3's state change events. Related Alarms & State Change will have the same CORR_TAG. This state change will be preceded by the DOC3's state change events. Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. For a successful failover, one should see a U-E-Idl to U-E-A
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.4.1.1. <DOC3_ID>
IVPU_SP F
33, 38
U-DIdl
U-E-A
EMPTY
EMPTY
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.4.1.1. <DOC3_ID>
IVPU_SP F
33, 38
U-DIdl
U-E-Idl
EMPTY
EMPTY
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.4.1.1. <DOC3_ID>
IVPU_SP F
33, 38
U-E-A
U-E-Idl
EMPTY
EMPTY
The DOC3 board has transitioned from Disabled to Enabled state The DOC3 board has transitioned from Disabled to Enabled state The DOC3 board has been disabled
N U
N U
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.4.1.1. <DOC3_ID>
IVPU_SP F
33, 38
U-E-Idl
U-DIdl
EMPTY
EMPTY
The DOC3 board has been disabled
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.4.1.1. <DOC3_ID>
IVPU_SP F
33, 38
U-E-Idl
U-E-A
EMPTY
EMPTY
The DOC3 board has been enabled to provide service Device unlocked Disabled device has been locked Disabled device has been enabled Active device has been admin locked
N U
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.2.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.2.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.2.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.2.<SLOT_ID>
IVPU_SP ROC IVPU_SP ROC IVPU_SP ROC IVPU_SP ROC
2, 18
L-D-Idl
U-DIdl L-D-Idl
EMPTY
EMPTY
N U
2, 18
U-DIdl U-DIdl U-E-A
EMPTY
65537
N U
2,18
U-E-Idl
EMPTY
EMPTY
N U
2, 18
L-D-Idl
EMPTY
65537
N U
October 30, 2008
iVPU-93

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.2.<SLOT_ID>
IVPU_SP ROC
2,18
U-E-A
U-DIdl
EMPTY
65537
N U
1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.2.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.2.<SLOT_ID> 1.3.6.1.4.1.161.3.3. 10.5.19.1.1.2.1.1.1. 1.2.<SLOT_ID>
IVPU_SP ROC IVPU_SP ROC IVPU_SP ROC
2,18
U-E-Idl
L-D-Idl
EMPTY
65537
2,18
U-E-Idl
U-DIdl U-E-A
EMPTY
65537
Device has been admin locked Standby device failed or reset Standby device has become the functioning active device
N U
transition on the other SPROC with 30 seconds of this event. Related Alarms & State Change will have the same CORR_TAG. For a successful failover, one should see a U-E-Idl to U-E-A transition on the other SPROC with 30 seconds of this event. Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. If this event is preceded by a UE-A to U-D-Idl or L-D-Idl on the other SPROC in the same iVPU cage within a 30 second period, this means that this SPROC has transitioned from a redundant role to an active role. Related Alarms & State Change will have the same CORR_TAG.
N U
2,18
U-E-Idl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.2.1.2.0
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.2.1.2.0
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.2.1.2.0
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.19.1.2.1.2.0
1.3.6.1.4.1.161.3.3. 10.5.18.1.2.1.4.0 1.3.6.1.4.1.161.3.3. 10.5.18.1.2.1.4.0 1.3.6.1.4.1.161.3.3. 10.5.18.1.2.1.4.0
IVPU_SY NCHRO NIZATIO N IVPU_SY NCHRO NIZATIO N IVPU_SY NCHRO NIZATIO N IVPU_SY NCHRO NIZATIO N IVPU_TE RCKT_R G IVPU_TE RCKT_R G IVPU_TE RCKT_R
U-DIdl
U-E-Idl
EMPTY
EMPTY
U-E-A
U-DIdl
EMPTY
EMPTY
U-E-A
U-E-Idl
EMPTY
EMPTY
U-E-Idl
U-E-A
EMPTY
EMPTY
U-DIdl U-E-A
U-E-Idl
EMPTY
EMPTY
U-DIdl U-E-Idl
EMPTY
EMPTY
U-E-A
EMPTY
EMPTY
The Synchronization component was enabled. The Synchronization component was disabled. The Synchronization component went idle. The Synchronization component went active. The tercktRG component was enabled. The tercktRG component went disabled. The tercktRG component
N U
N U
Related Alarms & State Change will have the same CORR_TAG.
N U
N U
N U
Related Alarms & State Change will have the same CORR_TAG. Related Alarms & State Change will have the same CORR_TAG. Related Alarms & State Change will have the same CORR_TAG.
N U
N U
iVPU-94
October 30, 2008
Release SR17.0
State Changes
Reason Code

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1.3.6.1.4.1.161.3.3. 10.5.18.1.2.1.4.0 1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.1.1.1. <BPP2_ID>
G IVPU_TE RCKT_R G IVPU_VP F
U-E-Idl
U-E-A
EMPTY
EMPTY
317
U-DIdl
U-E-Idl
EMPTY
EMPTY
went idle. The tercktRG component went active A BPP2 card is coming into service
N U
Related Alarms & State Change will have the same CORR_TAG. Related Alarms & State Change will have the same CORR_TAG. The associated disabled BPP2 card has been enabled, but not yet ready to provide service. Related Alarms & State Change will have the same CORR_TAG. The associated BPP2 card has failed / reset or has been locked. Related Alarms & State Change will have the same CORR_TAG. The associated BPP2 card was disabled. Related Alarms & State Change will have the same CORR_TAG. The associated BPP2 card has failed / reset or has been locked. Related Alarms & State Change will have the same CORR_TAG. The associated BPP2 card is ready to provide service. Related Alarms & State Change will have the same CORR_TAG. Immediate maintenance action required. Call processing impacted Related Alarms & State Change will have the same CORR_TAG. Immediate maintenance action required. No Call processing Impacted Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.1.1.1. <BPP2_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.1.1.1. <BPP2_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.1.1.1. <BPP2_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.4.2.1.1.1. <BPP2_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.4.1.3.0
IVPU_VP F
317
U-E-A
U-DIdl
EMPTY
EMPTY
A BPP2 card has been disabled A BPP2 card has been disabled A BPP2 card has been disabled A BPP2 card had come into service All BPP2 cards are out of service
N U
0000 0000 FFFF FFFF
IVPU_VP F
317
U-E-A
U-E-Idl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
IVPU_VP F
317
U-E-Idl
U-DIdl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
IVPU_VP F
317
U-E-Idl
U-E-A
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
IVPU_VP F_RG
U-E-A
U-E-Idl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.4.1.3.0
IVPU_VP F_RG
U-E-Idl
U-E-A
EMPTY
EMPTY
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.4.0 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.4.0
IVPU_VT _LINK IVPU_VT _LINK
U-DIdl U-DIdl
U-E-A
EMPTY
EMPTY
U-EImp
EMPTY
8388612
esmrStateCh
0000 0000 -
Correlation Tag
1.3.6.1.4.1.161.3.3.
IVPU_VT
U-E-A
U-D-
EMPTY
8388612
At least one device represented by this container has become enabled. All virtual tributaties are fully operational One or more virtual tributaries are not fully operational (at least one is enabled) All virtual
N U
N U
N U
N U
Related Alarms & State Change
October 30, 2008
iVPU-95

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
FFFF FFFF 0000 0000 FFFF FFFF
<xxxxxxxx> Correlation Tag <xxxxxxxx>
10.5.18.1.1.1.4.0 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.4.0
_LINK IVPU_VT _LINK 1 U-E-A
Idl U-EImp EMPTY 8388612
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.4.0 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.4.0 1.3.6.1.4.1.161.3.3. 10.5.18.1.2.2.4.1.1. <VTSPAN_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.2.2.4.1.1. <VTSPAN_ID>
IVPU_VT _LINK IVPU_VT _LINK IVPU_VT _SPAN IVPU_VT _SPAN
U-DIdl U-E-A
EMPTY
8388612
EMPTY
EMPTY
11184| 21-284 11184| 21-284
U-E-Idl
EMPTY
EMPTY
tributaries have failed One or more virtual tributaries are not fully operational (at least one is enabled) All virtual tributaries have failed All virtual tributaties are fully operational Device has been enabled Device has become idle
will have the same CORR_TAG N U Related Alarms & State Change will have the same CORR_TAG
N U
Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. Call processing will be impacted. All resources on that vtspan will not be usable. Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG
N U
N U
U-E-Idl
EMPTY
EMPTY
N U
1.3.6.1.4.1.161.3.3. 10.5.18.1.2.2.4.1.1. <VTSPAN_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.2.2.4.1.1. <VTSPAN_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.2.3.1.1. <ICP_NODE_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.2.3.1.1. <ICP_NODE_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.2.3.1.1. <ICP_NODE_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.2.3.1.1. <ICP_NODE_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.2.3.1.1. <ICP_NODE_ID> 1.3.6.1.4.1.161.3.3.
IVPU_VT _SPAN IVPU_VT _SPAN
11184| 21-284 11184| 21-284 1-336
U-E-Idl
U-DIdl U-E-A
EMPTY
EMPTY
Device has been disabled Device has been enabled and providing service XBL Link was admin unlocked
N U
U-E-Idl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF
IVPU_XB L
L-D-Idl
U-DIdl
EMPTY
EMPTY
N U
0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 FFFF FFFF 0000 0000 -
Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag <xxxxxxxx> Correlation Tag
IVPU_XB L IVPU_XB L IVPU_XB L IVPU_XB L IVPU_XB
1-336
L-D-Idl
U-E-Idl
EMPTY
EMPTY
1-336
U-DIdl U-DIdl U-E-A
L-D-Idl
EMPTY
65537
XBL Link was enabled and is in service XBL Link was admin locked XBL Link was enabled and is in service XBL Link was admin locked XBL Link
N U
Related Alarms & State Change will have the same CORR_TAG. The iCP side of the XBL may be locked. Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change
N U
1-336
U-E-Idl
EMPTY
EMPTY
N U
1-336
L-D-Idl
EMPTY
65537
N U
1-336
U-E-A
U-D-
EMPTY
8454146,
N U
iVPU-96
October 30, 2008
Release SR17.0
State Changes
Reason Code

Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
FFFF FFFF
<xxxxxxxx>
10.5.18.1.1.2.3.1.1. <ICP_NODE_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.2.3.1.1. <ICP_NODE_ID> 1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.6.0
Idl
8454147
connectivity lost
IVPU_XB L IVPU_XB L_CONT AINER
1-336
U-E-Idl
U-E-A
EMPTY
EMPTY
U-DIdl
U-E-A
EMPTY
8388767
XBL Link was enabled and is in service The only one link in this container is back in service At least one XBL link represented by this container has become enabled. The only one link in this container is disabled One or more XBL links represented by this container is disabled All XBL links represented by this container are disabled. All the XBL links represented by this container are fully functional again
N U
will have the same CORR_TAG. Call processing capacity will be reduced. Related Alarms & State Change will have the same CORR_TAG Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. At least one of the XBL link in this container is still not functioning. The alarms in Related Alarms column are clear ones. Related Alarms & State Change will have the same CORR_TAG. This container has only one link equipped. Related Alarms & State Change will have the same CORR_TAG. At least one of the XBL link in this container is not functioning. Related Alarms & State Change will have the same CORR_TAG. All the XBL links in this container are disabled Related Alarms & State Change will have the same CORR_TAG. All the XBL links in this container are active and in a service providing role. The alarms in Related Alarms column are clear ones.
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.6.0
IVPU_XB L_CONT AINER
U-DIdl
U-EImp
EMPTY
8388748
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.6.0
IVPU_XB L_CONT AINER IVPU_XB L_CONT AINER
U-E-A
U-DIdl
EMPTY
8388767
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.6.0
U-E-A
U-EImp
EMPTY
8388748
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.6.0
IVPU_XB L_CONT AINER IVPU_XB L_CONT AINER
U-EImp
U-DIdl
EMPTY
8388767
N U
0000 0000 FFFF FFFF
1.3.6.1.4.1.161.3.3. 10.5.18.1.1.1.6.0
U-EImp
U-E-A
EMPTY
8388748
N U
October 30, 2008
iVPU-97
Release SR17.0
__________________________________ Events
Event Type
Reason Code
OMC Text
MOI Info (Id)
MOI Info (Labe l)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
actionStatus Event
2= Aborted
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatus Event
2= Aborted
Background Download Switch Aborted Background Download Failed
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatus Event
3= Failed
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatus Event
3= Failed
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatus Event actionStatus Event
3= Failed 6=Login
Upgrade failed User Login
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0 1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has aborted, completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated if OLCC switch has aborted, completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated if OLCC background download has aborted, completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated if OLCC switch has aborted, completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Indicate upgrade failed.
S t a t u s N U
EMPTY
N U
EMPTY
N U
EMPTY
N U
EMPTY
N U
EMPTY
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
This event is sent when there is a user login
N U
actionStatus Event
7=Logout
User Logout
1.3.6.1.4.1. 161.3.3.10. 2.13.1.1.0
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
This event is sent when there is a user logout
N U
SR15.0 release NGDE feature change: Started from SR15.0, this trap will include user login name, user access level, and reason code. 0x90 = Logged in successfully SR15.0 release NGDE feature change: Started from SR15.0, this trap will include user login name, user access level, and reason code. 0x91 = Logged out successfully, 0x92 = Session
iVPU-98
October 30, 2008
Release SR17.0
Event Type
Reason Code

MOI Info (Labe l) Inst From State To State Related State Changes Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
actionStatus Event
4= Successf ul
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
actionStatus Event
4= Successf ul 4= Successf ul
actionStatus Event
actionStatus Event actionStatus Event actionStatus Event actionStatus Event availabilityEv ent
4= Successf ul 5= inProgre ss 1= Started 3= Failed 8= Applicati on Schedule d 9= Operator Initiated Platform 11 = Indetermi nate
Background Download Aborted Successfully Background Download Switch Completed Successfully Upgrade completed successfully Upgrade in progress Upgrade started Upgrade failed System Sequence Number: <Sys Seq No> System Secondary ID: <Sys Secondary Id> System New Mode: <Active or Standby> System Switch Time: <Switch Time>
1.3.6.1.4.1. 161.3.3.10. 2.10.1.2.0 1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has aborted, completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated if background download abort (bgdlAbort) is successful. Event is generated if OLCC switch has aborted, completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Indicate RUP ended successfully. Report estimated RUP remaining time to OMC. Indicate RUP started
N U
timed-out, 0x94 = Session manually terminated EMPTY
N U
EMPTY
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0 1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0 1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0 1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0 EMPTY
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Indicate upgrade failed.
N U
EMPTY
IVPU
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
This event is sent to indicate any state transition of all iVPU components -- each SPROC, ISB, DGBE, DOC3 and BPP2.
N U
Availability Trap Fields: Universal time the time (in GMT) when the trap was generated. Sequence number integer incremented for each new Availability trap; the valid range is 24 bits (0..16777215) and it wraps back to 1 when incremented past 24 bits. The value of 0 is only used to restart the sequence when no previous information is available. Secondary id Specifies the Logical iCP Id of the associated iCP. The value (-1) is used for an
October 30, 2008
iVPU-99

Event Type
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Labe l)
Inst
From State
Event Description
O u t a g e ( Y / N )
Comments & Notes
System Reason Code: <Reason Code> System Old Mode: <Active or Standby> System Additional Text: <Availability Trap> System Reason Text: <Current Availability>
iVPU that does not have an associated iCP at the time the Availability Trap is generated. New mode Indicates the mode state of the iVPU. Maintenance (1) Active (3) Time of switch Time (in GMT format) when the iVPU network element or the identified internal iVPU component transitioned mode state. Reason Code Cause captured by the iVPU that triggered the availability trap. The value (0) is used for transitions to Active. No Reason Code (0) Platform Hardware Fault (1) Application Software Fault (5) Operator Initiated Platform (9) Indeterminate (11) Old mode Indicates the mode state of the iVPU. Unknown is represented as (0). Uses the same range of values as is specified in New mode. Reason text Text that conveys information about the iVPU FRU that has transitioned in-service or out-of-service and whether the FRU has become active or standby. These FRUs include SPROC, ISB, DGBE, BPP2, and DOC3. The general format of the Reason Text is as follows: "'X' in slot 'Y' transitioned out of service or "'X' in slot 'Y' transitioned in service
iVPU-100
October 30, 2008
Release SR17.0
Event Type
Reason Code

Event Description
O u t a g e ( Y / N )
Comments & Notes
where 'X' is one of the following component types Active SPROC2, Standby SPROC2, Active ISB2, Standby ISB2, DOC3, DGBE, BPP2 and 'Y' is the slot/board number
Additional text The text provides the number of affected FRU of a particular type that can generate the availability trap. The FRUs that can trigger an availability trap are the SPROC, ISB, DGBE, BPP2, and DOC3. The general format of the Additional Text is as follows: SPROC:numActive/numStandby /numConfigured; ISB:numActive/numStandby/num Configured; DOC3:numActive/numConfigured ; DGBE:numActive/numConfigured ; BPP2:numActive/numConfigured where numActive represents the number active components of a particular type, numStandby represents the number of standby components of a particular type, and numConfigured represents the number of components configured at the time of issuance of the availability trap.
October 30, 2008
iVPU-101

Event Type
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Labe l)
Inst
From State
Event Description
O u t a g e ( Y / N )
Comments & Notes
reStartEvent
EMPTY
New Operate State: <New Operate State> New Usage State: <New Usage State> New Admin State: <New Admin State> System ROM Version: <Sys ROM Version> System Load Version: <Sys Software Load Version> System DB Version: <Sys Database Version> System Code Version: <Sys Code Version> Description: <Sys Description> System Reset Reason: <Sys Reset Reason> System Outage Time: <Sys outage Time> System Reboot Time:
1.3.6.1.4.1. 161.3.3.10. 5.18.1.1.1.2 .0
IVPU_ NODE
EMPTY
EMPTY
EMPTY
EMPTY
Event is sent out to indicate the reboot time and outage time.
N U
New Operate State: Current node operational state New Usage State: Current node usage state New Admin State: Current node admin state System ROM Version:N/A System Load Version: Version of the current software System DB Version: Version of the current database System Code Version: Same as load version Description: N/A System Reset Reason: Reason for the last system reset. System Outage Time: Time in seconds for the latest outage. System Reboot Time: Time of the last reboot System Boot Diagnostics: Diagnostics reported during boot.
iVPU-102
October 30, 2008
Release SR17.0
Event Type
Reason Code

Event Description
O u t a g e ( Y / N )
Comments & Notes
<Sys Reboot Time> System Boot Diagnostics: <Sys Boot Diagnostics>
October 30, 2008
iVPU-103
Release SR17.0
iVPU-104
October 30, 2008
Release SR17.0
______________________________ Alarms
Alarm Type
Alarm Code
MDG2
R e l a t e d A l a r m s E M P T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Severity
Remedy
R e p o r t &
O u t a g e
201
202
Mobile IP: Received improperly formatted protocol element Mobile IP: Response not received from DAP within allotted time
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: DAP Update Response: Invalid response, DAP ID = <DAP ID>/ <Unknown DAP ID>. 1 Mobile IP: DAP Backup Info: Timeouts=<count>,IMSI=<IM SI>,DAP=<DAP ID>,Tx=<Total number of MIP Registration Update Requests sent to DAP>,Rx=<Total number of MIP Registration Update Responses received from DAP>
Warning
EMPTY
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
Warning
EMPTY
203
SLM: Invalid ACG ID
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
203
SLM: Invalid ACG ID
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
204
SLM: Invalid rag_service_flag value
1.3.6.1.4. 1.161.3.3 .5.1.13.2.
mdgSLM
1 Unconfigured acg_id <ACG ID> in RR msg from DAP <DAP ID> TEI= <TEI number>IMSI= <IMSI number> FILE <file name>, LINE <line number> 1 Invalid acg_id <ACG ID> in RR msg from DAP <DAP ID> TEI= <TEI number> IMSI= <IMSI number> FILE <file name>, LINE<line number> 1 invalid rag_service_flag <RAG service flag value> in RR msg from DAP <DAP
Major
E M P T Y E M P T Y E M P
EMPTY
Cause: The Mobile IP foreign agent has received a Mobile IP Registration Update Reply from the DAP that has an improper length, or is otherwise improperly formatted. Cause: The Mobile IP foreign agent (MDG) failed to receive Mobile IP Registration Update Response from DAP. The alarms are generated depending on the alarm mode. There are two possible alarm modes: Default Mode: Alarm is reported every 5 minutes with a count of number of occurrences since the last alarm. Debugging Mode: Alarm is reported for every occurrence. The alarm mode can be set on/off using MMI command "set comm alarm <on|off>". The alarm mode is defaulted to off (default mode) upon MDG initialization. Cause: The MDG received PCH ACCESS or PACKET DATA RECONNECT UPDATE message from the DAP containing acg id which is not configured. Cause: The MDG received PCH ACCESS or PACKET DATA RECONNECT UPDATE message from the DAP containing invalid acg id.
Y C / l N e a r R N
Comments & Notes
U EMPTY
R N
U EMPTY
R N
U EMPTY
Major
EMPTY
R N
U EMPTY
Minor
EMPTY
Cause: SLM receives Radio Resource message from the DAP with invalid rag_service_flag value. The message
R N
U EMPTY
October 30, 2008
MDG2-1

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r is discarded.
Comments & Notes
2.1.0
205
SLM: Invalid sector_id value
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
206
SLM: Invalid tei
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
ID>, TEI = <TEI number>, IMSI = <IMSI number> FILE <file name> LINE <line number> 1 Invalid sector id <Sector ID> in RR msg from DAP <DAP ID>, TEI = TEI number>, IMSI = <IMSI number> FILE <file name> LINE <line number> 1 Invalid tei <tei> and imsi <imsi> in SRP msg FILE <filename>, LINE <line number>!
Major
E M P T Y E M P T Y
EMPTY
Cause: SLM receives Radio Resource message from the DAP with invalid (out of range) sector_id value. The message is discarded.
R N
U EMPTY
Warning
EMPTY
207
SLM: Invalid dispatch_active_fla g_value
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
208
SLM: Invalid pd_ms_dormant_rs p status
mdgSLM
209
SLM: Invalid session_state value
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
210
SLM: Invalid message type in ICS_PPR_SLM_R R queue msg SLM: Invalid interface type in ICS_PPR_SLM_R R queue msg SLM: RR message is received when DAP is OOS
mdgSLM
211
mdgSLM
212
mdgSLM
1 Invalid dispatch_active_flag <dispatch active flag value> in RR msg from DAP <DAP ID> FILE <file name>, LINE <line number>! 1 Invalid pd_ms_dormant_rsp <PD MS dormant response status> status in RR msg from DAP <DAP ID> FILE <file name>, LINE <line number>! 1 Invalid session_state <session state value> in RR msg from DAP <DAP ID> FILE <filename>, LINE <line number>! 1 Invalid msg type <message type code> in RR msg from DAP <DAP ID> FILE <filename>, LINE <line number>! 1 Invalid interface type <interface type> in RR msg from DAP <DAP ID> FILE <filename>, LINE <line number>! 1 pch_access is rx when DAP is OOS FILE <filename> LINE <line number>.
Minor
Minor
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T
EMPTY
Cause: SLM has received Interboard Communication Service (ICS) messages from SRP protocol with invalid or unregistered TEI. Occasional occurrence of this alarm could be an indication of internal inconsistency or race condition. Cause: SLM receives Radio Resource message from the DAP with invalid dispatch_active_flag_value field. The message is discarded. Cause: SLM receives Radio Resource message from the DAP with invalid pd_ms_dormant_rsp field. The message is discarded.
R N
U EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
Cause: SLM receives Radio Resource message from the DAP with invalid session_state field. The message is discarded. Cause: SLM receives Radio Resource message from the DAP with undefined message type. The message is discarded. Cause: SLM receives Radio Resource message from the DAP with undefined interface type. The message is discarded. Cause: SLM receives an RR message when SLM state indicates that the DAP is out of service. The message is discarded.
R N
U EMPTY
Minor
EMPTY
R N
U EMPTY
Minor
EMPTY
R N
U EMPTY
Warning
EMPTY
R N
U EMPTY
MDG2-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
212
SLM: RR message is received when DAP is OOS
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
1 ms_dispatch_active is rx when DAP is OOS FILE <filename>LINE <line number>. 1 pd_ms_dormant_response is rx when DAP is OOS FILE <filename> LINE <line number>. 1 pd_reconnect_update is rx when DAP is OOS FILE<filename> LINE <line number>. 1 pdl_unreliabledata_ind is rx when DAP <DAP ID> is OOS FILE <filename> LINE <line number>. 1 pdm_resettimer_ind is rx when DAP <DAP ID>is OOS FILE <filename>LINE <line number>. 1 Lost communication with the DAP <DAP ID> FILE <filename>, LINE<line number>.
Warning
212
mdgSLM
Warning
212
mdgSLM
Warning
213
SLM: RF message is received when DAP is OOS
mdgSLM
Warning
213
SLM: RF message is received when DAP is OOS
mdgSLM
Warning
216
SLM: generate alarm LOST_COMM_W_ DAP and send alarm SLM: response message from DAP is received indicating DAP OOS
mdgSLM
Minor
R e l a t e d A l a r m s Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: SLM receives an RR message when SLM state indicates that the DAP is out of service. The message is discarded. Cause: SLM receives an RR message when SLM state indicates that the DAP is out of service. The message is discarded. Cause: SLM receives an RR message when SLM state indicates that the DAP is out of service. The message is discarded. Cause: SLM receives an RF message when SLM state indicates that the DAP is out of service. The message is discarded. Cause: SLM receives an RF message when SLM state indicates that the DAP is out of service. The message is discarded. Cause: This alarm is generated by SLM after MAX_RADIO_FREE_RETRY number of unsuccessful retries of pd_ms_dormant_req messages. The retry is stopped. Cause: SLM receives a Radio Resources message (pd_ms_dormant_rsp message) from the DAP with status field indicating temporary error in the DAP. The retry for the corresponding request message is stopped. Cause: SLM receives a Radio Resource message (pd_ms_dormant_rsp_message) from the DAP with status field indicating unrecoverable error in the DAP. The retry for the corresponding request message is stopped. Cause: A Download Start Request R N
Comments & Notes
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
D EMPTY
EMPTY
R N
U EMPTY
217
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
1 Temporary DAP out of service, DAP ID = <DAP ID>, RAG ID = <RAG ID>, FILE <file name> LINE <line number>!
Minor
EMPTY
R N
U EMPTY
218
SLM: response message from DAP is received indicating unrecoverable DAP OOS RAG: Timer
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
1 unrecoverable DAP out of service, DAP ID = <DAP ID>, RAG ID = <RAG ID>, FILE <file name> LINE <line number>!
Major
E M P T Y
EMPTY
R N
U EMPTY
communicat
219
1.3.6.1.4.
mdgRAG
1 DLstart timer expiration:
Major
EMPTY
R N
U EMPTY
October 30, 2008
MDG2-3

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r message is sent to a DAP during RAG Download. This alarm indicates that the timer timed out waiting for a response message from the DAP corresponding to a Download Start Request message. Cause: A Download Abort Request message is sent to a DAP when a download session is aborted by an MDG. This alarm indicates that the timer timed out waiting for a response message from the DAP corresponding to a Download Abort Request. Cause: This alarm serves as a sanity check timer and occurs during RAG download. The alarm occurs when a record that is expected to be downloaded is not due to session expiration of the waiting period between each record during a download. This alarm prevents a RAG download from hanging. Cause: A RAG Update Request message is sent to a DAP and/or ACG. This alarm indicates that the timer timed out waiting for a response message from the DAP or ACG corresponding to a Rag Update Request message. Note: ACG/DAP id(-1) means, during the initial RAG updates, if id(-1) appears, it means RAG update response has not been received for one or more. Cause: A RAG Verification Request message is sent to a DAP. This alarm indicates that the timer timed out waiting for a response message from the DAP corresponding to a Rag Verification Request message. Cause: There was an incompatibility detected between the interface version of the MDG and that of the communicating network element.
Comments & Notes
ionFailureE vent
Exp/No rsp on a Download Start Request to a DAP
1.161.3.3 .5.1.14.1. 0
DAP <DAP ID> RAG <RAG ID>
220
RAG: Timer Exp/No rsp on a Download Abort Request to a DAP
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0
mdgRAG
1 DLabort timer expiration: DAP <DAP ID> RAG <RAG ID>
Major
E M P T Y
EMPTY
R N
U EMPTY
221
RAG: Download session expired
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0
mdgRAG
1 DLsanity timer expiration: DAP <DAP ID> RAG <RAG ID>
Major
E M P T Y
EMPTY
R N
U EMPTY
222
Board Manager: Timer Exp/No rsp on a RAG Update Request
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0
mdgRAG
1 RAG Update Req timeout: ACG/DAP <id>
Minor
E M P T Y
EMPTY
R N
U EMPTY
223
Board Manager: Timer Exp/No rsp on a RAG Verification Request Link: Link Version Check Failure
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0
mdgRAG
1 RAG Verif Req timeout DAP <DAP ID>
Minor
E M P T Y E M P T Y E M
EMPTY
R N
U EMPTY
224
1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMAL
224
Link: Link Version Check Failure
1.3.6.1.4. 1.161.3.3
mdgMDL
1 3 2 0 0 1 -
ACG Link Version check Failed for ACG <ACG ID> DLCI <DLCI> PORT <PORT id>
Major
EMPTY
R N
U EMPTY
DAP Link Version check Failed for DAP <DAP ID>
Major
EMPTY
Cause: There was an incompatibility detected between the interface version
R N
U EMPTY
MDG2-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
vent
.5.1.8.2.6 .2.1.1 225 Link: Unnumbered LAPD msg 1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1 mdgMAL
1 DLCI <DLCI> PORT <PORT 5 id> Version <version> 1 3 2 0 0 1 1 5 1 3 2 0 0 1 1 5 1 3 2 0 0 1 1 5 Received Unnumbered data confirmation from ACG <ID> DLCI <DLCI> PORT <PORT id> Major
R e l a t e d A l a r m s P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r of the MDG and that of the communicating network element. EMPTY Cause: The MDG has received an unnumbered LAPD message. The MDG should not receive any unnumbered LAPD data. R N
Comments & Notes
U EMPTY
225
Link: Unnumbered LAPD msg
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMDL
Received Unnumbered data confirmation from DAP <ID> DLCI <DLCI> PORT <PORT id> Received Unnumbered data indication from ACG <ID> DLCI <DLCI> PORT <PORT id>
Major
EMPTY
Cause: The MDG has received an unnumbered LAPD message. The MDG should not receive any unnumbered LAPD data. Cause: The MDG has received an unnumbered LAPD message. The MDG should not receive any unnumbered LAPD data.
R N
U EMPTY
225
mdgMAL
Major
EMPTY
R N
U EMPTY
225
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMDL
Received Unnumbered data indication from DAP <ID> DLCI <DLCI> PORT <PORT id> Discarding ACG LAPD message for undefined channel for ACG < ACG ID> DLCI <DLCI>PORT <PORT id>
Major
EMPTY
Cause: The MDG has received an unnumbered LAPD message. The MDG should not receive any unnumbered LAPD data. Cause: The MDG has received inbound data for a LAPD link which has not been initialized.
R N
U EMPTY
226
Link: LAPD msg for undef channel
mdgMAL
Major
EMPTY
R N
U EMPTY
226
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgMDL
226
mdgMDL
Discarding DAP LAPD message for undefined channel for DAP <DAP ID> DLCI <DLCI> PORT <PORT id> 1 Discarding DAP LAPD - message for undefined 1 channel 5 1 Discarding invalid encapsulation message from ACG/DAP <ID> DLCI <DLCI> PORT <PORT id> 1 Discarding FR message for
Major
EMPTY
Cause: The MDG has received inbound data for a LAPD link which has not been initialized.
R N
U EMPTY
Major
EMPTY
Cause: The MDG has received inbound data for a LAPD link which has not been initialized.
R N
U EMPTY
227
Link: Invalid Frame Relay msg
mdgLink
Major
EMPTY
Cause: The MDG has received a frame relay message whose encapsulation header could not be identified.
R N
U EMPTY
communicat
228
Link: Frame Relay
1.3.6.1.4.
mdgLink
Major
EMPTY
Cause: The MDG has received a frame
R N
U EMPTY
October 30, 2008
MDG2-5

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r relay message whose DLCI header could not be identified.
Comments & Notes
ionFailureE vent
msg from undef DLCI
1.161.3.3 .5.1.8.1.0
unassigned PORT/DLCI <PORT/DLCI id>
230
Link: Unrecognized ITC msg
1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMAL
230
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMDL
1 3 2 0 0 1 1 5 1 3 2 0 0 1 1 5 1 3 2 0 0 1 1 5 1 3 2 0 0 1 1 5
Unrecognized ITC message from ACG/DAP <ID> DLCI <DLCI> PORT <PORT id>
Major
EMPTY
Cause: The MDG has received an ITC message whose ITC header contains an unrecognized destination function ID.
R N
U EMPTY
Unrecognized ITC message from DAP <ID> DLCI <DLCI> PORT <PORT id>
Major
EMPTY
Cause: The MDG has received an ITC message whose ITC header contains an unrecognized destination function ID. Cause: The MDG has received an ITC message whose ITC header contains some errors
R N
U EMPTY
230
mdgMAL
Unrecognized ITC message from <dev_type> <dev_id>
Major
EMPTY
R N
N EMPTY
230
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMDL
Unrecognized ITC message from <dev_type> <dev_id>
Major
EMPTY
Cause: The MDG has received an ITC message whose ITC header contains some errors
R N
N EMPTY
231
Link: LM ITC msg w/ invalid msg type
mdgMAL
Unrecognized ITC message from ACG <ACG ID> DLCI <DLCI> PORT <PORT id>
Major
EMPTY
Cause: The MDG has received a Link Version ITC message containing an invalid message type in its header.
R N
U EMPTY
231
Link: LM ITC msg w/ invalid msg type
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMDL
Unrecognized ITC message received from DAP <DAP ID> DLCI <DLCI> PORT <PORT id> Timedout waiting for VCheck request from ACG <ACG ID> DLCI <DLCI> PORT <PORT id>
Major
EMPTY
Cause: The MDG has received a Link Version ITC message containing an invalid message type in its header.
R N
U EMPTY
232
Link: Timed out waiting for VCheck request
mdgMAL
Warning
EMPTY
Cause: The MDG has timed out waiting for a Link Version request from an ACG.
R N
U EMPTY
233
Link: Timed out waiting for VCheck response
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1
mdgMDL
Timedout waiting for VCheck response from DAP <DAP ID> DLCI <DLCI> PORT <PORT id>
Major
EMPTY
Cause: The MDG has timed out waiting for a Link Version response from a DAP.
R N
U EMPTY
MDG2-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
234
Billing: TCP Connection with BA cannot be established
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: MDG-BA[<BA Number>] TCP connection attempt failed in proc_conn_wait_timeout()
Major
R e l a t e d A l a r m s Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: Each MDG-node tries to establish a TCP connection with a Billing Accumulator. If it fails to do that because of any of the following reasons, then it sends an alarm: - The server (BA) refuses to make a connection. - There is no physical connection between the BA and the MDG-node. - The specified TCPaddress of the BA is not available. Cause: Each MDG-node tries to establish a TCP connection with a Billing Accumulator. If it fails to do that because of any of the following reasons, then it sends an alarm: - The server (BA) refuses to make a connection. - There is no physical connection between the BA and the MDG-node. - The specified TCPaddress of the BA is not available. Cause: Each MDG-node tries to establish a TCP connection with a Billing Accumulator. If it fails to do that because of any of the following reasons, then it sends an alarm: - The server (BA) refuses to make a connection. - There is no physical connection between the BA and the MDG-node. - The specified TCPaddress of the BA is not available. Cause: Each MDG-node tries to establish a TCP connection with a Billing Accumulator. If it fails to do that because of any of the following reasons, then it sends an alarm: - The server (BA) refuses to make a connection. - There is no physical connection between the BA and the MDG-node. - The specified TCPaddress of the BA is not available. Cause: Each MDG-node tries to establish a TCP connection with a Billing Accumulator. If it fails to do that because of any of the following reasons, then it sends an alarm: - The server (BA) refuses to make a R N
Comments & Notes
U EMPTY
234
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Specified address <address> not available in connect() call in proc_conn_wait_timeout()
Major
E M P T Y
EMPTY
R N
U EMPTY
234
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Attempt to connect was refused in connect() call in proc_conn_wait_timeout()
Major
E M P T Y
EMPTY
R N
U EMPTY
234
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: proc_conn_wait_timeout(): Invalid Socket argument in connect() call or BA not listening on port<port number>
Major
E M P T Y
EMPTY
R N
U EMPTY
234
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BIll Task: Specified address <address> not available in connect() call in exe_BSP_session()
Major
E M P T Y
EMPTY
R N
U EMPTY
October 30, 2008
MDG2-7

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r connection. - There is no physical connection between the BA and the MDG-node. - The specified TCPaddress of the BA is not available. Cause: Each MDG-node tries to establish a TCP connection with a Billing Accumulator. If it fails to do that because of any of the following reasons, then it sends an alarm: - The server (BA) refuses to make a connection. - There is no physical connection between the BA and the MDG-node. - The specified TCPaddress of the BA is not available. Cause: Each MDG-node tries to establish a TCP connection with a Billing Accumulator. If it fails to do that because of any of the following reasons, then it sends an alarm: - The server (BA) refuses to make a connection. - There is no physical connection between the BA and the MDG-node. - The specified TCPaddress of the BA is not available. Cause: An error has occurred during the header decompression - packet is silently discarded.
Comments & Notes
234
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Attempt to connect was refused in connect() call in exe_BSP_session()
Major
E M P T Y
EMPTY
R N
U EMPTY
234
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: exe_BSP_session: Invalid Socket Argument in connect() call or BA not listening on port <port number>
Major
E M P T Y
EMPTY
R N
U EMPTY
235
RFCL: header decompression violation
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1.
mdgRFC L
1 Header decompression violation: Packet discarded IMSI = <IMSI>.
Warning
236
Board Manager: RAG Timestamp failed
mdgRAG
1 RAG Verif Resp timestamp failure NOT OWNED / OWNED DAP <DAP ID> RAG <RAG ID> 1 Download Start Req failure: RAG <RAG ID> DAP <DAP ID> Unreachable
Major
237
General: Network Element Unreachable
mdgRAG
Major
237
mdgRAG
1 Download Abort Req failure: RAG <RAG ID> DAP <DAP ID> Unreachable
Major
237
mdgRAG
1 MS Download Resp failure: RAG <RAG ID> DAP <DAP ID> Unreachable
Major
E M P T Y E M P T Y E M P T Y E M P T Y E M P
EMPTY
R N
U EMPTY
EMPTY
Cause: Timestamp in the MDG and DAP RAG Tables are out of synch.
R N
U EMPTY
EMPTY
Cause: Could not communicate with some network element
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
MDG2-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
0 communicat ionFailureE vent 237 General: Network Element Unreachable 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.9.1.0 mdgRAG 1 RAG Download Resp failure: RAG <RAG ID> DAP <DAP ID> Unreachable Major
237
mdgRAG
1 Rag Update Req failure ACG/DAP <ID> Unreachable
Major
237
mdgRAG
1 RAG Verif Req failure DAP <DAP ID> Unreachable
Major
238
Board Manager: RAG Download Session control timer expiration Mobile IP: Response not received from HA within allotted retries or registration request/reply validation fails Mobile IP: Response not received from HA within allotted retries or registration request/reply validation fails SRPC objects failed Sanity timer
mdgRAG
DAP Download Session control timeout: Delay request from DAP <DAP ID>
Minor
239
mdgMIP
1 Mobile IP: PendRegTimeout: Missed MIP response(s) from HA, count=<count>
Major
R e l a t e d A l a r m s T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
Cause: Session control expires without response from DAP.
R N
U EMPTY
EMPTY
Cause: MDG did not receive MIP Registration Response(s) from HA for <count > number of times
R N
U EMPTY
239
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: RegReplyRcvd: No Matching pending records, count=<count>
Major
E M P T Y
EMPTY
Cause: MDG could not the corresponding visitor for the HA response for <count> number of times.
R N
U EMPTY
240
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0
mdgSRP
1 Channel Grant Sanity Timer expired: ACG <acg_id> SECTOR <sector_id> RAG <rag_id> WIDEN_FLAG <on/off>
Major
E M P T Y
EMPTY
Cause: This alarm occurs when there is srpc obj (acg_id/sector_id/rag_id) queue that have been waiting for SRPC Channel Grant Messages for more than the sanity timer interval (2 min). In the alarm text there could be one suspected object. 1. sector flagged when in probable trouble. 2. assumed in trouble when channel request
R N
U EMPTY
October 30, 2008
MDG2-9

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY pending > 2 minutes Cause: The CLEAR alarm will be sent as soon as a Channel Grant is received (provided a SET was sent for this srpc object). Cause: The MDG was unable to start one of its communication ports. 1. Check the cable connection on both sides. 2. Check the transition module (model#SMM726), if you still have a problem change the I/O board. Cause: The MDG successfully started the port <port id>. As a result, all links in this port will start to establish themselves. Cause: An error occurred when making a call to a pna system function. R N
Comments & Notes
240
SRPC objects failed Sanity timer
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgSRP
1 Channel Grant Received: ACG <acg_id> SECTOR <sector_id> RAG <rag_id> WIDEN_FLAG <on/off> 1 Port<port id> is Down indication
Clear
U EMPTY
253
FRPortIndication
mdgLink
Major
EMPTY
R N
U EMPTY
253
FRPortIndication
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Port <port id> is Up indication
Major
EMPTY
R N
U EMPTY
311
pNA system call failed
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgMLI NK
1 MLNK: mlnk_add_framing: pNA send failed. pNA send error <error> on sockd = <socket>. 1 MLNK: mlnk_add_framing: pNA send failed all attempts. error <error> on sockd=<error>. 1 RAG Update Resp Failure. Fail Retry/Fail No Retry/Fail Illegal Trans ACG/DAP <ID> RAG <RAG ID> 1 Primary LAN port disconnected
Major
EMPTY
R N
U EMPTY
311
pNA system call failed
mdgMLI NK
Major
EMPTY
Cause: An error occurred when making a call to a pna system function.
R N
U EMPTY
324
Board Manager: Bad Message RAG Update Request
mdgRAG
Major
EMPTY
Cause: The ACG/DAP sends a RAG Update message to MDG indicating that the RAG Update request was not processed. Cause: The primary LAN port has been disconnected. Check the Ethernet cable running from the MDG to the Ethernet Switch. Reattach, repair or replace the cable as necessary. Cause: The primary LAN port has been reconnected. Check the ethernet cable running from the MDG to the Ethernet Switch. Reattach, repair or replace the cable as necessary. Cause: Timeout on waiting RAG Mirroring Verification Response
R N
U EMPTY
326
Board Manager: LAN Port Notification
mdgRIP
Major
EMPTY
R N
U EMPTY
326
Board Manager: LAN Port Notification
mdgRIP
1 Primary LAN port connected
Clear
EMPTY
C N
U EMPTY
384
VDRC_SERVER_ RSP_TO
mdgVDR C
1 RAG Verification Time Out with Backup MDG <backup MDG id>
Warning
EMPTY
R N
U EMPTY
MDG2-10
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
416
VDRS: Server Request Failed
1.3.6.1.4. 1.161.3.3 .5.1.19.6. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.6. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.6. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.6. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.6. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.6. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0
mdgVDR S
1 Client - <mdg_id>
Major
417
VDRS: Server Retirement Failed
mdgVDR S
1 Client - <mdg_id>
Warning
418
VDRS: Illegal RAG Operation
mdgVDR S
1 Client - <mdg_id> RAG <rag id>
Major
419
VDRS: Illegal Backup Request
mdgVDR S
1 Client - <mdg_id>
Major
420
VDRS: Illegal Resync Type
mdgVDR S
1 Client - <mdg_id>
Major
421
VDRS: RAG In Sync
mdgVDR S
1 Client - <mdg_id> RAG <rag id>
Warning
433
TCP connection not established
mdgMLI NK
1 MLNK: MDG[<MDGid>]MDG[<MDGid>]TCP connection not established: (optional: Error<error code>)
Major
R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
EMPTY
Cause:The server advertisement request is timeout, or a negative response is received.
Y C / l N e a r R N
Comments & Notes
U EMPTY
EMPTY
Cause:The server retirement request is timeout, or a negative response is received.
R N
U EMPTY
EMPTY
Cause:The client requests an operation on the RAG which it does not own.
R N
U EMPTY
EMPTY
Cause:The client requests an operation to a MDG which is not a backup.
R N
U EMPTY
EMPTY
Cause:The resync type that the client MDG wants to use can not be accepted by the backup server.
R N
U EMPTY
EMPTY
Cause: The RAG is in sync with the client.
R N
U EMPTY
EMPTY
434
Lower layer down
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3
mdgMLI NK
1 MLNK: Ethernet layer is down.
Major
450
EBTS Proxy Advertisement
mdgiVPU
1 <dev_type><dev_id> link is not configured/ <dev_type>
Warning
E M P T Y E M
EMPTY
Cause: If an MDG-node fails while trying to establish a TCP connection with another MDG because of any of the following reasons, it sends this alarm: - The peer MDG node refuses to make a connection. - There is no physical connection between the MDGs. - The specified TCP-address of the peer MDG is invalid. - Any other internal error occurs. Cause: Ethernet cable may be disconnected
R N
U EMPTY
R N
U EMPTY
EMPTY
Cause: Either iVPU is not configured with the particular ACG or no IVPU
R N
N EMPTY
October 30, 2008
MDG2-11

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r assigned for the particular ACG
Comments & Notes
vent
Configuration Mismatch 451 Error in EBTS Proxy Advertisement Message Error in EBTS Proxy Advertisement Procedure Error in iVPU Load Indication Message
.5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.9.1.0 mdgiVPU
is not assigned to <dev_type> 1 <reason> in the PA message Major
EMPTY
Cause: Parsing error of EBTS Advertisement message
R N
N EMPTY
452
mdgiVPU
1 Unable to <action> to iVPU <dev_id>
Major
EMPTY
Cause: General error in EBTS proxy advertisement procedure
R N
N EMPTY
453
mdgiVPU
1 Invalid shedding level <level> iVPU <dev_id>
Major
EMPTY
Cause: Parsing error of the Load Indication message
R N
N EMPTY
454
Error in iVPU Load Indication Procedure
mdgiVPU
1 Load indication procedure error
Major
EMPTY
Cause: Parsing error of the Load Indication message
R N
N EMPTY
100000
Bad Value returned in the Configuration File
mdgNod e
1 Empty
Major
EMPTY
R N
N Bad Value returned in the Configuration File U EMPTY
201
ev_receive() failed
mdgNod e
1 Call to ev_receive failed in BM
Major
EMPTY
Cause: The pSOS system call ev_receive() returned an error. ev_receive() is responsible for receiving an MDG event. Cause: The pSOS system call ev_receive() returned an error. ev_receive() is responsible for receiving an MDG event. Cause: The pSOS system call ev_receive() returned an error. ev_receive() is responsible for receiving an MDG event. Cause: The pSOS system call ev_receive() returned an error. ev_receive() is responsible for receiving an MDG event.
R N
201
ev_receive() failed
mdgRAG
1 ev_receive failure in RDL
Major
EMPTY
R N
U EMPTY
201
ev_receive() failed
mdgMIP
1 FIBS: ev_receive failed
Major
EMPTY
R N
U EMPTY
201
ev_receive() failed
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0
mdgMLI NK
1 MLNK: ev_recv failed in mlnk_main(): Error <error code>
Critical
EMPTY
R Y
U EMPTY
MDG2-12
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
201
ev_receive() failed
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0
mdgVDR C
1 VCRT: vcrt_main. ev_receive failed
Critical
201
ev_receive() failed
mdgNod e
1 IPSERV :ipserv_main. ev_receive failed
Critical
202
mgmt_poll() failed
mdgNod e
1 mgmt_poll failure in BM
Major
R e l a t e d A l a r m s Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: The pSOS system call ev_receive() returned an error. ev_receive() is responsible for receiving an MDG event. Cause: The pSOS system call ev_receive() returned an error. ev_receive() is responsible for receiving an MDG event. Cause: An error occurred while polling for SNMP event(s). When a set command is received from the SNMP agent, a call to mgmt_poll() is made. This alarm is generated in the event that such a call was unsuccessful. Cause: An error occurred while polling for SNMP event(s). When a set command is received from the SNMP agent, a call to mgmt_poll() is made. This alarm is generated in the event that such a call was unsuccessful. Cause: An error occurred when a task (subagent) initialized his SNMP session. R Y
Comments & Notes
U EMPTY
EMPTY
R Y
N EMPTY
EMPTY
R N
U EMPTY
202
mgmt_poll() failed
1.3.6.1.4. 1.161.3.3 .5.1.13.1. 0
mdgPPR
1 Call to mgmt_poll from PPR failed!
Critical
EMPTY
R Y
U EMPTY
203
mgmt_init_env() failed
1.3.6.1.4. 1.161.3.3 .5.1.13.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0
mdgPPR
1 Could not initialize SNMP session for PPR!
Critical
EMPTY
R Y
U EMPTY
204
mgmt_new_instanc e() failed
mdgRAG
1 RAG table instance registration failure
Critical
EMPTY
Cause: An error occurred while registering a MIB managed object.
R Y
U EMPTY
204
mdgRAG
1 RAG basic instance registration failure
Critical
EMPTY
R Y
U EMPTY
204
mdgRAG
1 Rdl instance registration failure
Critical
EMPTY
R Y
U EMPTY
204
mdgNod e
1 Node instance registration failure
Critical
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-13

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: An error occurred while registering a MIB managed object. R Y
Comments & Notes
204
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 Bill instance registration failure
Critical
U EMPTY
204
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgRIP
1 RIP instance registration failure
Critical
EMPTY
R Y
U EMPTY
205
mgmt_wait_initializ e() failed
mdgLink
1 Error during configuration initialization
Critical
EMPTY
Cause: An error occurred during MIB initialization.
R Y
U EMPTY
206
pm_register() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error registering ACG LINK OUTAGE statistic
Critical
EMPTY
Cause: An error occurred while registering a statistic upon MDG start up.
R Y
U EMPTY
206
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error registering DAP LINK OUTAGE statistic
Critical
EMPTY
R Y
U EMPTY
206
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4.
mdgNod e
1 Error registering MDG SCHEDULED OUTAGE stats: Node
Critical
EMPTY
R Y
U EMPTY
206
mdgRFC L
1 Could not register PM_IDX_ECP_IBD_PKTS_ COMPRESSED statistic in PPR! 1 Could not register PM_IDX_ECP_IBD_PKTS_ REQ_COMPRESSED statistic in PPR! 1 Could not register PM_IDX_ECP_IBD_PKT_R EQ_ECYPT statistic in PPR!
Critical
EMPTY
R Y
U EMPTY
206
mdgRFC L
Critical
EMPTY
R Y
U EMPTY
206
mdgRFC L
Critical
EMPTY
R Y
U EMPTY
processingF
206
mdgRFC
1 Could not register
Critical
EMPTY
Cause: An error occurred while
R Y
U EMPTY
MDG2-14
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
ailureEvent
1.161.3.3 .5.1.13.2. 5.1.0 206 pm_register() failed 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2.
PM_IDX_ECP_OBD_PKTS_ COMPRESSED statistic in PPR! 1 Could not register PM_IDX_ECP_OBD_PKTS_ REQ_COMP statistic in PPR! 1 Could not register PM_IDX_ECP_OBD_PKTS_ REQ_ECYPT statistic in PPR! 1 Could not register PM_IDX_ECP_TOTAL_PKT S statistic in PPR! Critical
mdgRFC L
206
mdgRFC L
Critical
206
mdgRFC L
Critical
206
mdgRFC L
1 Could not register PM_IDX_IB_ACTUAL_LOA D statistic in PPR!
Critical
206
mdgSLM
1 Could not register206 PM_IDX_OB_MDG_DATAG RAM_DISCARD stat in PPR!
Critical
206
mdgSLM
1 Could not register PM_IDX_PD_SESSION stat in PPR!
Critical
206
mdgSLM
1 Could not register PM_IDX_LENGTH_PD_SSN stat in PPR!
Critical
206
mdgSLM
1 Could not register PM_IDX_OB_SLM_QUEUE _TM_BIN stat in PPR!
Critical
206
mdgSLM
1 Could not register PM_IDX_OB_L3_OFFERED _LOAD stat in PPR!
Critical
R e l a t e d A l a r m s M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r registering a statistic upon MDG start up.
Comments & Notes
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-15

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
2.1.0 processingF ailureEvent 206 pm_register() failed 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.4.1.0 mdgSLM 1 Could not register PM_IDX_OB_MDG_CELL_ DATAGRAM_DSCRD Critical
EMPTY
R Y
U EMPTY
206
mdgMM
1 MM: MMInit: Error registering MS_RECORD_MODIFIED statistic; result=<result> 1 MM: MMInit: Error registering WIDEN_NUM_PD_REG_MS statistic; result=<result> 1 MM: Error registering WIDEN_OB_DATAGRAM_A RRIVAL_RATE statistic; result=<result> 1 BILL Task: Timer DB init failure in bill_task_init()
Major
EMPTY
R N
U EMPTY
206
mdgMM
Major
EMPTY
R N
U EMPTY
206
mdgMM
Major
EMPTY
R N
U EMPTY
207
timer_db_init() fail
mdgBill
Critical
EMPTY
Cause: An error occurred when initializing a timer database.
R Y
U EMPTY
207
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgRAG
1 Timer DB Init Failure: RDL
Critical
EMPTY
R Y
U EMPTY
207
mdgRAG
1 Timer DB Init Failure: BM
Critical
EMPTY
R Y
U EMPTY
207
mdgPPR
1 Could not initialize timer database for PPR!
Critical
EMPTY
R Y
U EMPTY
207
mdgLink
1 Timer database could not be initialized
Critical
EMPTY
R Y
U EMPTY
MDG2-16
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
207
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3
mdgSRP
1 SFU_T: sfu_main() timer_db_init Failure
Critical
207
mdgMLI NK
1 MLNK:Timer database init failed: Error <error code>
Critical
207
mdgVDR C
1 VCRT: vcrt_initialize. Failed to initialize vcrt timer db.
Major
208
timer_db_add() failed
mdgSRP
1 SFU_T: sfu_main() timer_db_add Failure
Critical
208
mdgNod e
1 Timer DB Add Failure : synch_to_omc
Critical
208
mdgRAG
208
mdgRAG
1 Timer DB Add Failure : RAG Download / RAG Update / RAG Update Request / RAG Update Request Timeout / RAG Verification 1 Timer DB Failure: RDL
Critical
Critical
208
mdgSRP
1 SFU_T: inbound SRP timer_db_add Failure
Critical
208
mdgRFC L
1 RFCL: Call to timer_db_add failed!
Critical
208
mdgSLM
1 SLM: Call to timer_db_add failed!
Critical
R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M
Remedy
R e p o r t &
O u t a g e
EMPTY
Y C / l N e a r R Y
Comments & Notes
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
Cause: An error occurred when initializing the timer database.
R Y
U EMPTY
EMPTY
Cause: An error occurred when adding a timer to the timer database.
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-17

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
.5.1.13.2. 2.1.0 processingF ailureEvent 208 timer_db_add() failed 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.4.2.1 8.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 mdgMM 1 MM: begin_timer: MM Add Timer Failed Critical
EMPTY
R Y
U EMPTY
208
mdgMM
1 MM: startCheckLifetimeTimer: MM Add Timer Failed; timer_db_add=<timer code> 1 MLNK: Failed to add <timer_name>[<MDG id>] timer in File <file name> Line <line number> 1 VCRT: timer_control_timer_start. Could not add control timer = <id> 1 VCRT: timer_rag_mirroring_req_sta rt. Could not add mirror timer = <id> 1 Failed to add <timer_name> timer for <dev_type><dev_id>
Critical
EMPTY
R Y
U EMPTY
208
mdgMLI NK
Critical
EMPTY
R Y
U EMPTY
208
mdgVDR C
Major
EMPTY
R N
U EMPTY
208
mdgVDR C
Major
EMPTY
R N
U EMPTY
208
mdgNod e
Major
EMPTY
R N
N EMPTY
209
ics_send() failed
mdgBillG en
1 ppr-BillGen: ics-send failed in bill_rec_ready_req()
Major
EMPTY
Cause: An error occurred when sending an ICS message to a specified queue.
R N
U EMPTY
209
ics_send() failed
mdgMM
1 MM: mmRagDeleteReq: ICS_BM_RM_MM invalid queue id
Major
EMPTY
R N
U EMPTY
209
ics_send() failed
mdgMM
1 MM: mmRagDeleteReq: ICS_BM_RM_MM invalid message
Major
EMPTY
R N
U EMPTY
MDG2-18
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
209
ics_send() failed
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMM
1 MM: mmRagRecoveryReq: ICS_BM_RM_MM invalid queue id
Major
209
ics_send() failed
mdgMM
1 MM: mmRagRecoveryReq: ICS_BM_RM_MM invalid message
Major
209
ics_send() failed
mdgMM
1 MM: mmRdlStartReq: ICS_BM_RM_MM invalid queue id
Major
209
ics_send() failed
mdgMM
1 MM: mmRdlStartReq: ICS_BM_RM_MM invalid message
Major
209
ics_send() failed
mdgNod e
1 ICS Send Failure : Node
Critical
209
ics_send() failed
mdgRAG
1 ICS Send Failure : DDSM
Critical
209
ics_send() failed
mdgMIP
1 Mobile IP: DapSendBackupFIB : ICS send failure
Critical
209
ics_send() failed
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 (ECP)FNE2MS_ICS_SEND_ FAILURE
Critical
209
ics_send() failed
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 (ECP)MS2FNE_ICS_SEND_ FAILURE
Critical
processingF
209
ics_send() failed
1.3.6.1.4.
mdgECP
1 (ECP)ICS failed reporting
Critical
R e l a t e d A l a r m s Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: An error occurred when sending an ICS message to a specified queue. R N
Comments & Notes
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
Cause: An error occurred when
R Y
U EMPTY
October 30, 2008
MDG2-19

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r sending an ICS message to a specified queue.
Comments & Notes
ailureEvent
1.161.3.3 .5.1.5.1.0
Encryption Stats
209
ics_send() failed
209
ics_send() failed
1.3.6.1.4. 1.161.3.3 . 5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgSRP
1 SFU_T:inbound SRP-ics _send Failure
Critical
EMPTY
M Y
U EMPTY
mdgRFC L
1 RFCL: ICS fails when sending to ECP!
Critical
EMPTY
R Y
U EMPTY
209
ics_send() failed
mdgVDR C
1 VCRT: send_data_msg. Could not send to ICS_MLNK_DATA
Major
EMPTY
Cause: An error occurred when sending an ICS message to a specified queue. Can't send the ICS message.
R N
U EMPTY
209
ics_send() failed
mdgVDR C
1 VCRT: send_link_down_mlnk. ICS send failed. error = <error>
Major
EMPTY
R N
U EMPTY
209
ics_send() failed
mdgVDR C
1 VCRT: send_rep_start_req. ICS send failed. error = <error>
Major
EMPTY
R N
U EMPTY
209
ics_send() failed
mdgVDR C
1 VCRT: send_rep_complete_req. ICS send failed. error = <error> 1 VCRT: send_rep_abort_to_bm. ICS send failed. error = <error>
Major
EMPTY
R N
U EMPTY
209
ics_send() failed
mdgVDR C
Major
EMPTY
R N
U EMPTY
210
ics_receive() failed
mdgECP
1 (ECP)FNE2MS_ICS_RECEI VE_FAILURE
Critical
EMPTY
210
1.3.6.1.4. 1.161.3.3
mdgECP
1 (ECP)MS2FNE_ICS_RECEI VE_FAILURE
Critical
EMPTY
Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This
R Y
U EMPTY
R Y
U EMPTY
MDG2-20
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
.5.1.5.1.0
R e l a t e d A l a r m s P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading
Comments & Notes
210
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0
mdgRFC L
1 ICS fails when receiving from ECP, ERR_CODE: <error code>!
Critical
EMPTY
R Y
U EMPTY
210
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
1 ICS fails when receiving RR msg, ERR_CODE: <error code>!
Critical
EMPTY
R Y
U EMPTY
210
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0
mdgRFC L
1 ICS fails when receiving control message from ECP, ERR_CODE: <error code>!
Critical
EMPTY
R Y
U EMPTY
210
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
1 ICS fails when receiving SRP msg, ERR_CODE: <error code>!
Critical
EMPTY
R Y
U EMPTY
210
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 FIBS: ics_receive failed
Major
EMPTY
R N
U EMPTY
210
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0
mdgMM
1 MM: ICS receive message failed.
Major
EMPTY
R N
U EMPTY
210
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0
mdgMLI NK
MLNK: ics_receive failed in process_event() Line <line number>
Major
EMPTY
R N
U EMPTY
processingF
210
1.3.6.1.4.
mdgVDR
1 VCRT: handle_ctrl:
Major
EMPTY
R N
U EMPTY
October 30, 2008
MDG2-21

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: A fatal error has occurred during the initialization on the Mobile IP foreign agent. Currently this occurs if the Timer subsystem cannot be initialized, or the required UDP sockets cannot be opened and initialized. Cause: This indicates that a pSOS error has occurred for the select() system call. This is a critical error indicating pSOS and/or pNA is malfunctioning. Cause: This indicates that a pSOS error has occurred for the recvfrom() system call. This is a critical error indicating pSOS and/or pNA is malfunctioning. Cause: This indicates that a pSOS error has occurred for the recvfrom() system call. This is a critical error indicating pSOS and/or pNA is malfunctioning. Cause: Mobile IP task was unable to create the required UDP sockets for Mobile IP. This is a critical error and will also cause the MDG Processing Alarm #211 to be generated as the Mobile IP task shuts down. Cause: Mobile IP task was unable to create the required UDP sockets for Mobile IP. This is a critical error and will also cause the MDG Processing Alarm #211 to be generated as the Mobile IP task shuts down. Cause: This indicates that a pSOS error has occurred for the sendto() system call when attempting to forward
Comments & Notes
ailureEvent
1.161.3.3 .5.1.19.5. 0
ics_receive failed. Queue not emptied.
210
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgVDR C
1 VCRT: handle_data: ics_receive failed. Queue not emptied.
Major
EMPTY
R N
U EMPTY
211
Mobile IP: Registration task is deleting itself now
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: MIP FA task is deleting itself now
Critical
EMPTY
R Y
U EMPTY
212
Mobile IP: select error
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: Select failure
Major
EMPTY
R N
U EMPTY
213
Mobile IP: recvfrom error
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: MIP UDP socket recvfrom failure
Major
EMPTY
R N
U EMPTY
213
Mobile IP: recvfrom error
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: MIP FIBS socket recvfrom failure
Major
EMPTY
R N
U EMPTY
214
Mobile IP: Unable to create MIP UDP socket
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: Unable to create MIP UDP socket
Critical
EMPTY
R Y
U EMPTY
214
Mobile IP: Unable to create MIP UDP socket
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: Unable to create MIP FIBS socket
Critical
EMPTY
R Y
U EMPTY
215
Mobile IP: sendto error : Registration Request not
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: sendto failed (RegRequestRcvd) errno: <error number> MS <ms_ip
Warning
EMPTY
R N
U EMPTY
MDG2-22
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
forwarded
address> : HA <ha_ip address>
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r a Mobile IP Registration Request. This is a critical error indicating pSOS and/or pNA is malfunctioning (Note: Refer to MDG pNA+ Error Codes document in the iDEN Technical Publications White Paper at https://gtssonline.motorola.com). Cause: This indicates that a pSOS error has occurred for the sendto() system call when attempting to forward a Mobile IP Registration Reply. This is a critical error indicating pSOS and/or pNA is malfunctioning (Note: Refer to MDG pNA+ Error Codes document in the iDEN Technical Publications White Paper at https://gtssonline.motorola.com). Cause: A timer could not be started in the Mobile IP foreign agent. This is an internal error indicating possible memory corruption, or a software error. Cause: The Mobile IP foreign agent attempted to add a visitor to the visitor list and failed due to a visitor with the same IP address already existing in the table. This is an indication of possible IP address misconfiguration on mobile nodes. Cause: The Mobile IP foreign agent attempted to set a pointer to the COA interface specified in the Mobile Subscriber record of a mobile attempting to Mobile IP register. The Care Of Address (COA) assigned to the mobile is not valid. This is an internal error indicating possible memory corruption, or a software error. Cause: The node was not found when attempting to remove a visitor from the visitor list AVL tree. This is an internal error indicating possible memory corruption, or a software error. Cause: The Mobile IP foreign agent's Mobility Management (MM) driver attempted to use an invalid interface number (if_num) during initialization of
Comments & Notes
216
Mobile IP: sendto error : Registration Reply not forwarded
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: sendto failed (RegReplySend) errno: <error number>
Warning
E M P T Y
EMPTY
R N
U EMPTY
217
Mobile IP: TimerStart failure
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: TimerStart failure
Major
218
Mobile IP: VisitorAdd : IP address already in use
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: VisitorAdd: IP address already in use: IP=<IP address>, IMSI=<IMSI>
Major
E M P T Y E M P T Y
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
219
Mobile IP: VisitorAdd : Could not set COA route pointer
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: VisitorAdd : Could not set COA route pointer: COA=< COA> IMSI=<IMSI>
Major
E M P T Y
EMPTY
R N
U EMPTY
220
Mobile IP: VisitorRemove : Node not in AVL tree Mobile IP: MM Driver : invalid if_num on NI_INIT
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: VisitorRemove : Node not in AVL tree, IMSI = <IMSI number>.
Major
221
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: MM Driver : NI_INIT: invalid interface number <interface number>
Critical
E M P T Y E M P T
EMPTY
R N
U EMPTY
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-23

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r the driver module. This is an internal error indicating possible memory corruption, or a software error. Cause: The FIBS task was unable to initialize properly. Currently this occurs when it cannot open necessary UDP sockets. Cause: This indicates that a pSOS error has occurred for the sendto() system call when attempting to forward a FIBS message. This error indicates pSOS and/or pNA malfunctions (Note: Refer to MDG pNA+ Error Codes document in the iDEN Technical Publications White Paper at https://gtssonline.motorola.com). Cause: Attempted to add a mobile to a RAG within the DAP/RAG table but no RAGs were available.
Comments & Notes
222
FIBS Task: failed to initialize
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 FIBS: Task failed to initialize
Critical
223
FIBS Task: sento() error
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 FIBS: sendto failed dest port: <port #> error<error code>
Major
E M P T Y E M P T Y
EMPTY
R Y
U EMPTY
EMPTY
R N
U EMPTY
224
Mobility Management Task: No active RAGs
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0
mdgMM
1 MM: mmPdRegNew: no active RAGs
Warning
225
Mobility Management Task: VLR add failure
mdgMM
1 MM: mmPdRegNew: VLR add failure
Major
225
mdgMM
1 MM: mmRagRecoveryReq: Dap/Rag Vlr Add Failed for tei <downloaded TEI>
Major
225
mdgMM
1 MM: mmRdlCreateRec: Dap/Rag Vlr Add Failed for tei <downloaded TEI>
Major
226
226
Mobility Management Task: Maximum number of mobiles exceeded Mobility Management Task: Maximum number of mobiles exceeded
mdgMM
1 MM: mmPdRegNew: Max number of records reached: <Max Allowed Mobiles>
Warning
mdgMM
1 MM: mmRagRecoveryReq: max number of records reached: <Max Allowed Mobiles>
Warning
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
EMPTY
R N
U EMPTY
EMPTY
Cause: Unable to add an MS_Record to the binary tree.
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
Cause: Self explanatory
R N
U EMPTY
EMPTY
R N
U EMPTY
MDG2-24
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
226
227
Mobility Management Task: Maximum number of mobiles exceeded Mobility Management Task: TEI not found
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0
mdgMM
1 MM: mmRdlCreateRec: max number of records reached: <Max Allowed Mobiles>
Warning
mdgMM
1 MM: TEI <TEI number >not found for SLM processing <code>. MSID = <msid>
Warning
227
Mobility Management Task: TEI not found
mdgMM
228
Mobility Management Task: Duplicate TEI
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0
mdgMM
229
SLM: Invalid state
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgSLM
229
SLM: Invalid state
mdgSLM
1 MM: freeTEI: teiTable.entry[<entry>] = NULL, IMSI = <IMSI>, TEI = <TEI Number>, DAP ID = <DAP ID>, RAG ID = <RAG ID> 1 MM: Duplicate TEI on RAG download: existing IMSI = <IMSI>, downloaded IMSI = <IMSI>, TEI = <TEI Number>, DAP ID = <DAP ID>,RAG ID = <RAG ID> 1 add_oq is rx in invalid state = <state>, nbragcell = <outstanding load in mobile's RAG/cell>, acg = <ACG ID>, sector = <Sector ID> 1 delete_oq is rx in invalid state = <state>
Warning
R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
EMPTY
Y C / l N e a r R N
Comments & Notes
U EMPTY
EMPTY
Cause: The TEI was not found in the tei_table . A NULL was returned to the calling function instead of the correct tei. Cause: The TEI was not found in the tei_table . A NULL was returned to the calling function instead of the correct tei.
R N
U EMPTY
EMPTY
R N
U EMPTY
Warning
EMPTY
Cause: This error found that more than 1 ms_rec had the same extension, the same count, the same DAP, and the same RAG. This error should never occur. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset.
R N
U EMPTY
Critical
EMPTY
R Y
U EMPTY
Critical
EMPTY
R Y
U EMPTY
229
SLM: Invalid state
mdgSLM
1 increment_nbcell is rx in invalid state = <state>
Critical
EMPTY
R Y
U EMPTY
229
SLM: Invalid state
mdgSLM
1 decrement_nbcell is rx in invalid state = <state>
Critical
EMPTY
R Y
U EMPTY
229
SLM: Invalid state
mdgSLM
1 pdl_establish_cfrm is invalid when slm_mng_state = <SLM manager state>.
Critical
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-25

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
229
SLM: Invalid state
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3
mdgSLM
1 pdl_establish_ind is invalid when slm_mng_state = <SLM manager state>.
Critical
EMPTY
Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by SLM state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by RFCL state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by RFCL state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by RFCL state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received
Y C / l N e a r R Y
Comments & Notes
U EMPTY
229
SLM: Invalid state
mdgSLM
1 slm_adduser_req is invalid when slm_mng_state = <SLM Manager state>
Critical
EMPTY
R Y
U EMPTY
229
SLM: Invalid state
mdgSLM
1 pdl_release_cfrm is invalid when slm_mng_state = <SLM Manager state>.
Critical
EMPTY
R Y
U EMPTY
229
SLM: Invalid state
mdgSLM
1 ERR: pdl_release_ind is invalid when slm_mng_state = <SLM Manager state>
Critical
EMPTY
R Y
U EMPTY
229
SLM: Invalid state
mdgSLM
1 pdl_userdata_cfrm is invalid when slm_mng_state = <SLM Manager state>
Critical
EMPTY
R Y
U EMPTY
229
SLM: Invalid state
mdgSLM
1 pdl_notify_ind is invalid when slm_mng_state = <SLM Manager state>
Critical
EMPTY
R Y
U EMPTY
230
RFCL: Invalid state
mdgRFC L
1 ecp_obddata_cfrm is invalid when rfcl_state = <RFCL state>
Critical
EMPTY
R Y
U EMPTY
230
RFCL: Invalid state
mdgRFC L
1 rfcl_adduser_req is invalid when rfcl_state = <RFCL state>.
Critical
EMPTY
R Y
U EMPTY
230
RFCL: Invalid state
mdgRFC L
1 rfcl_deleteuser_req is invalid when rfcl_state = <RFCL state>.
Critical
EMPTY
R Y
U EMPTY
230
RFCL: Invalid state
mdgRFC L
1 ecp_ibddata_cfrm is invalid when rfcl_state = <RFCL
Critical
EMPTY
R Y
U EMPTY
MDG2-26
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
.5.1.13.2. 5.1.0 processingF ailureEvent 230 RFCL: Invalid state 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 mdgRFC L
state>
1 ecp_dcompdel_ack is invalid when rfcl_state = <RFCL state>
Critical
230
RFCL: Invalid state
mdgRFC L
1 ecp_dcompcreate_ack is invalid when rfcl_state = <RFCL state>
Critical
230
RFCL: Invalid state
mdgRFC L
1 pdl_userdata_ind is invalid when rfcl_state = <RFCL state
Critical
231
Unauthorized WiDEN service usage
mdgSLM
231
Unauthorized WiDEN service usage
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2.
mdgSRP
1 SLM pch_access: unauthorized WiDEN service usage, TEI=<tei>, IMSI=<imsi>, FILE <filename>, LINE <line number>! 1 SFU_T: inbound SRP Unauthorized WiDEN service usage
Major
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r by RFCL state machine in invalid state. This alarm causes MDG to reset. EMPTY Cause: This mdg_fatal alarm is generated when an event is received by RFCL state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by RFCL state machine in invalid state. This alarm causes MDG to reset. Cause: This mdg_fatal alarm is generated when an event is received by RFCL state machine in invalid state. This alarm causes MDG to reset. Cause: This alarm is generated if a WiDEN MS tries to use WiDEN service when it's not allowed. R Y
Comments & Notes
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R N
U EMPTY
Warning
EMPTY
Cause: MS sends WiDEN inbound SFU when it is not WiDEN allowed.
R N
U EMPTY
232
Maximum number of RAGs reached
mdgRAG
1 OMC attempting to unlock greater than 16 RAGs: RAG rag_id=<RAG id>
Major
EMPTY
Cause: MDG gets more than 16 RAGs assigned by the OMC when MDG connects to more than 1600 ACGs.
R N
U EMPTY
234
SLM: Corrupted ACG ID
mdgSLM
1 Invalid acg_id <ACG ID> used to access the acg_structure
Critical
EMPTY
Cause: This alarm is generated when SLM is called by an entity or protocol "inside" MDG with corrupted ACG ID field. This alarm causes MDG to reset. Cause: This alarm is generated when SLM is called by an entity or protocol "inside" MDG with corrupted ACG ID field. This alarm causes MDG to reset. Cause: Internal error in SLM flow control entity. This alarm is generated when SLM detects that the outbound
R Y
U EMPTY
234
SLM: Corrupted ACG ID
mdgSLM
1 Unconfigured acg_id <ACG ID> used to access the acg_structure
Critical
EMPTY
R Y
U EMPTY
235
SLM: Error in Tcleanup
mdgSLM
1 Error in Tcleanup
Critical
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-27

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r datagram double link list is corrupted. This alarm causes MDG to reset. Cause: Internal error in SLM flow control entity. This alarm is generated when a request to delete an element from a (outbound queue) heap structure is received when the heap structure is empty. The heap structure is corrupted. This alarm causes MDG to reset. Cause: Internal error in SLM flow control entity. This alarm is generated when SLM detects that the outbound datagram queue is corrupted. This alarm causes MDG to reset. Cause: This alarm is generated when ECP does not respond to RFCL request within a predefined duration of time. Cause: This alarm is generated when ECP does not respond to RFCL request within a predefined duration of time.
Comments & Notes
2.1.0 processingF ailureEvent 236 SLM: Heap is empty, or node not in heap, slm_heap_node_d elete 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 mdgSLM 1 ERR: Heap is empty slm_heap__node_delete Critical
EMPTY
R Y
U EMPTY
237
SLM: Error finding last node in slm_oq_push
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0
mdgSLM
1 Error finding last node in slm_oq_push
Critical
238
RFCL: rfcl_tecpalive_to
mdgRFC L
1 ERR: RFCL tecpalive timeout!
Major
238
RFCL: rfcl_tecpalive_to
mdgRFC L
240
LLC: Failure when queueing events: not enough slots in queue
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 3.1.0
mdgLLC
1 ECP alive timeout: ECP load = <ECP 1 data load>, <ECP 2 data load>, <ECP 3 data load>; MN load (I/O) = <number of outstanding inbound in ECP>, <number of outstanding outbound in ECP>; tid = <expiring timer id>. 1 LAPi: failed to queue event.
Major
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
Major
E M P T Y E M P T Y E M P T Y E M
EMPTY
241
LLC: Wrong primitive from SLM
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 3.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 3.1.0 1.3.6.1.4. 1.161.3.3
mdgLLC
1 LAPi: received invalid SLM primitive: <event_state>
Major
EMPTY
Cause: There exists an event queue in LAPi, in which all events are placed. The size of this event queue is limited. This alarm is generated when the queue is full and a new event is generated to be placed in the queue. Cause: This alarm is generated when a combination of the LAPi state and the primitive received by LAPi from SLM are different than expected. Cause: This alarm is generated when any LAPi timer has expired in a state other than Connection Establish, Awaiting Establishment, or Reestablish. Cause: Each MDG-node has to register it self with each BA in order to
R Y
U EMPTY
R Y
U EMPTY
242
LLC: Timer expired in a state when it was not supposed to be set Billing: No Match BA Password
mdgLLC
1 LAPi: invalid timer expiry: <event_state>
Major
EMPTY
R Y
U EMPTY
246
mdgBill
1 BILL Task: MDG-BA[<BA number>] password failed in
Major
EMPTY
R N
U EMPTY
MDG2-28
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
.5.1.4.1.0
proc_BA_msg()
R e l a t e d A l a r m s P T Y
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r send Billing Records. In the registration request message, one of the elements, the current "Password", is also sent. If the password does not match with the one stored in the BA's database, the BA sends "password verification failure". In response to this message, the MDG-node sends an alarm. Cause: An error occurred when synchronizing time.
Comments & Notes
247
Time Synchronization failure
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgNod e
1 Waiting For Time Synch, synch_to_omc
Warning
247
Time Synchronization failure
mdgNod e
1 MDG-OMC time synch failure of <seconds> seconds
Warning
248
RIP: Initialization Failure
mdgRIP
1 <File name> <Line number>Bad index from pm_register
Warning
249
RIP: Processing Failure
mdgRIP
1 <File name> <Line #> Problem with pm_incr <statistic index>
Warning
250
Billing: MDG and Billing Accumulator's protocol versions do not match
mdgBill
1 BILL Task: MDG-BA[<BA number>] protocol version failed in proc_BA_msg(). MDG version number is <MDG version number>.
Major
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
EMPTY
R N
U EMPTY
EMPTY
Cause: MDG and OMC have more than 100 seconds difference in the time synchronization.
R N
U EMPTY
EMPTY
Cause: An error occurred while registering IP link outage statistic.
R N
U EMPTY
EMPTY
Cause: An error occurred while incrementing IP link outage statistic.
R N
U EMPTY
EMPTY
252
Board manager: Unlock received without time synch
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1.
mdgNod e
1 OMC attempting to lock node in state: <IO_INIT>/<RECOVERY>/< ECP_INIT_AC> 1 OMC attempting to unlock node in state: <DISABLED>
Warning
252
mdgNod e
Warning
E M P T Y E M P
EMPTY
Cause: Each MDG-node has to register it self with each BA in order to send Billing Records. In the registration request message, one of the elements, the current "Protocol Version Number", used by the MDG-node is sent. If this version number does match with the one used by the BA, the BA responds back with "protocol version failure". In response to this MDG-node sends an alarm. Cause: OMC attempting to lock MDG Node in an invalid state. The MDG will reject this SNMP lock command from the OMC. Cause: OMC attempting to unlock MDG Node in an invalid state when the MDG is still not time synched with the
R N
U EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
MDG2-29

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r OMC. The MDG will reject this SNMP unlock command from the OMC. Cause: OMC attempting to assign MDG Node the Backup role in an invalid state. The MDG will reject this SNMP mirroring role change command from the OMC. Cause: OMC attempting to assign MDG Node the Active role in an invalid state. The MDG will reject this SNMP mirroring role change command from the OMC. Cause: OMC attempting to unlock RAG when the MDG is still not time synched with the OMC. The MDG will reject this SNMP unlock command from the OMC. Cause: OMC attempting to lock RAG when the MDG Node in an invalid state. The MDG will reject this SNMP lock command from the OMC. Cause: OMC attempting to unlock RAG when the node is in an invalid state. The MDG will reject this SNMP unlock command from the OMC. Cause: The MDG was unable to start one of its communication ports. 1. Check the cable connection in both sides. 2. Check the transition module (model#SMM726), if you still have a problem change the I/O board. Cause: An error occurred allocating a memory buffer.
Comments & Notes
0 processingF ailureEvent 252 Board manager: Unlock received without time synch 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0 mdgNod e 1 OMC attempting to assign Node backup role in state: <DISABLED>/<IO_INIT>/<R ECOVERY>/<ECP_INIT_AC >/<ACTIVE>/<CLEANUP> 1 OMC attempting to assign Node active role in state: <ECP_INIT_BU>/<BACKUP > 1 OMC attempting to unlock without time synch: RAG <id> Warning
EMPTY
R N
U EMPTY
252
mdgNod e
Warning
EMPTY
R N
U EMPTY
252
mdgRAG
Warning
EMPTY
R N
U EMPTY
252
mdgRAG
1 OMC attempting to lock in invalid node state: RAG <id>
Warning
EMPTY
R N
U EMPTY
252
mdgRAG
1 OMC attempting to unlock in invalid node state: RAG <id>
Warning
EMPTY
R N
U EMPTY
253
FRPortIndication
mdgLink
1 Start Port Failed for PORT <PORT id>
Major
EMPTY
R N
U EMPTY
254
bm_alloc() failed
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 Mobile IP: DapSendBackupFIB : Out of memory
Critical
EMPTY
R Y
U EMPTY
254
bm_alloc() failed
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: bm_malloc() failed in bill_X731_state()
Critical
EMPTY
Cause: An error occurred allocating a memory buffer.
R Y
U EMPTY
254
bm_alloc() failed
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: bm_malloc failed in bill_task_init()
Critical
EMPTY
R Y
U EMPTY
MDG2-30
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
254
bm_alloc() failed
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: bm_malloc failed in update _store_ready_Q()
Critical
254
bm_alloc() failed
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgNod e
1 Buffer Allocation Failure: Bm_Arg_Push / SET_bgdlStart / Node / Node Object / BM Proxy 1 Buffer Allocation Failure: ddsm_row_init / ddsc_entry_init / DDSM / RAG Object / RAG Update / RAG Verification / RDL 1 Mobile IP: PendRegAdd : Out of memory
Critical
254
bm_alloc() failed
mdgRAG
Critical
254
bm_alloc() failed
mdgMIP
Critical
254
bm_alloc() failed
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4.
mdgSRP
1 SFU_T: outbound SRP bm_alloc Failure
Critical
254
bm_alloc() failed
mdgSRP
1 SFU_T: inbound SRP bm_alloc Failure
Critical
254
bm_alloc() failed
mdgSLM
1 bm_malloc fails!
Critical
254
bm_alloc() failed
mdgRFC L
1 bm_malloc fails!
Critical
254
bm_alloc() failed
mdgMM
1 MM: mmPdRegNew: bm alloc stream failure
Critical
processingF
254
bm_alloc() failed
mdgMM
1 MM: mmRagRecoveryReq:
Critical
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: An error occurred allocating a memory buffer. R Y
Comments & Notes
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
Cause: An error occurred allocating a
R Y
U EMPTY
October 30, 2008
MDG2-31

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r memory buffer.
Comments & Notes
ailureEvent
1.161.3.3 .5.1.13.2. 1.1.0 254 bm_alloc() failed 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. mdgMM
bm alloc failure
1 MM: mmRdlCreateRec: bm alloc failure
Critical
EMPTY
R Y
U EMPTY
254
bm_alloc() failed
mdgMM
1 MM: mmRagDeleteReq: bm alloc failure
Critical
EMPTY
R Y
U EMPTY
254
bm_alloc() failed
mdgSRP
1 SRPC bm_malloc fail at mkcnclgrnt
Major
EMPTY
R N
U EMPTY
254
bm_alloc() failed
mdgMLI NK
1 MLNK: send_data_to_queue : bm_malloc failed while allocate ICS message.
Major
EMPTY
Cause: An error occurred allocating a message buffer to send an ICS message.
R N
U EMPTY
254
bm_alloc() failed
mdgMLI NK
1 MLNK: convert_stream_to_linear: bm_malloc failed.
Major
EMPTY
R N
U EMPTY
254
bm_alloc() failed
mdgVDR C
1 VCRT: AU_update. Could not allocate memory for resync msg
Major
EMPTY
R N
U EMPTY
254
bm_alloc() failed
mdgVDR C
1 VCRT: send_resync_burst. Could not allocate memory for rsyn
Major
EMPTY
R N
U EMPTY
254
bm_alloc() failed
mdgVDR C
1 VCRT: send_rep_complete_req. Memory allocate failure.
Major
EMPTY
R N
U EMPTY
254
bm_alloc() failed
mdgVDR C
1 VCRT: send_rep_abort_to_bm. Memory allocate failure.
Major
EMPTY
R N
U EMPTY
MDG2-32
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
0 processingF ailureEvent 254 bm_alloc() failed 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0 mdgVDR C 1 VCRT: send_rep_start_req. Memory allocation failure. Major
254
bm_alloc() failed
mdgVDR C
1 VCRT: send_link_down_mlnk. Memory allocation failure.
Major
254
bm_alloc() failed
mdgVDR C
1 VCRT: msg_create_ics_data_buffer. Memory allocate failure.
Major
254
bm_alloc() failed
mdgVDR C
1 VCRT: msg_create_ics_ctrl_buffer. Memory allocate failure.
Major
254
bm_alloc() failed
mdgVDR C
1 VCRT: lists_init. Could not allocate memory on initialization.
Critical
255
bm_alloc_stream() failed
mdgRAG
1 Buffer Stream Allocation Failure:RAG Update/RAG Verification
Critical
255
mdgLink
1 LapdTxI: bm_alloc_stream failed
Critical
255
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0
mdgRFC L
bm_alloc_stream fails!
Critical
255
mdgSLM
1 bm_alloc_stream fails!
Critical
R e l a t e d A l a r m s T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
Cause: An error occurred allocating a streams memory buffer.
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-33

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
255
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgMM
MM: mmPdRegNew: bm alloc stream failure
Critical
EMPTY
Y C / l N e a r R Y
Comments & Notes
U EMPTY
255
mdgSRP
1 SRPC bm_alloc_stream fail at mkreqmsg
Major
EMPTY
R N
U EMPTY
255
mdgMLI NK
1 MLNK: mlnk_add_itc: bm_alloc_stream failed while trying to add itc header.
Major
EMPTY
Cause: An error occurred allocating a streams memory buffer for ITC header.
R N
U EMPTY
255
mdgMLI NK
1 MLNK: mlnk_add_framing: bm_alloc_stream failed while trying to add framing header.
Major
EMPTY
Cause: An error occurred allocating a streams memory buffer for framing header.
R N
U EMPTY
255
mdgMLI NK
1 MLNK: mlnk_add_framing: bm_alloc_stream failed while trying to add framing suffix.
Major
EMPTY
Cause: An error occurred allocating a streams memory buffer for framing suffix.
R N
U EMPTY
255
mdgMLI NK
1 MLNK: verify_suffix: bm_alloc_stream failed while trying to add framing suffix.
Major
EMPTY
Cause: An error occurred allocating a streams memory buffer for framing suffix.
R N
U EMPTY
255
mdgMLI NK
1 MLNK: convert_linear_to_stream: bm_alloc_stream failed.
Major
EMPTY
R N
U EMPTY
255
mdgMLI NK
1 MLNK: bm_alloc_stream failed in File <file name> Line <line number>
Major
EMPTY
R N
U EMPTY
256
Link: LapdInitPort() failed
mdgLink
1 Error calling LapdInitPort for Port <Port id >
Critical
EMPTY
processingF
257
Link:
1.3.6.1.4.
mdgLink
1 Error calling LapdInitChan
Critical
EMPTY
Cause: Port number is not in range. Switch type is not in range. Physical port with same port ID was found. Could not allocate a physical port Control Block. Initializing of port driver failed. Cause: Channel with same channel ID
R Y
U EMPTY
R Y
U EMPTY
MDG2-34
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
ailureEvent
LapdInitChan() failed
1.161.3.3 .5.1.8.1.0
258
Link: LapdSuAdd() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error calling LapdSuAdd for ACG <ACG ID> status <status id>
Critical
R e l a t e d A l a r m s M P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r found. Could not allocate control block. Initializing of channel driver failed.
Comments & Notes
EMPTY
258
Link: LapdSuAdd() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error calling LapdSuAdd for primary/secondary link of DAP <DAP ID> status <status id> ,
Critical
E M P T Y
EMPTY
259
Link: LapdEstReq() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
Error calling LapdEstReq for ACG <ACG ID> status <status id>
Critical
E M P T Y
EMPTY
Cause: Error in PORT ID, CHAN ID, TEI, SAPI, CEI, CES, DLCI, Window. Port or Channel not found. Duplicate CEI or DLCI. These are the values that LapdSuAdd could return which is printed out as status. LAPD_OK --> 0, LAPD_ERR_PORT_ID --> 1, LAPD_ERR_CHAN_ID --> 2, LAPD_ERR_SAPI --> 3, LAPD_ERR_TEI --> 4, LAPD_ERR_CES --> 5, LAPD_ERR_DLCI --> 6, LAPD_ERR_CEI --> 7, LAPD_ERR_WINDOW --> 8, LAPD_ERR_PORT_NOT_FOUND --> 9, LAPD_ERR_CHAN_NOT_FOUND -> 10, LAPD_ERR_DUP_DLCI --> 14, LAPD_ERR_DUP_CEI --> 15, LAPD_ERR_USER_ALLOC --> 16. Cause: Error in PORT ID, CHAN ID, TEI, SAPI, CEI, CES, DLCI, Window. Port or Channel not found. Duplicate CEI or DLCI. These are the values that LapdSuAdd could return which is printed out as status. LAPD_OK --> 0, LAPD_ERR_PORT_ID --> 1, LAPD_ERR_CHAN_ID --> 2, LAPD_ERR_SAPI --> 3, LAPD_ERR_TEI --> 4, LAPD_ERR_CES --> 5, LAPD_ERR_DLCI --> 6, LAPD_ERR_CEI --> 7, LAPD_ERR_WINDOW --> 8, LAPD_ERR_PORT_NOT_FOUND --> 9, LAPD_ERR_CHAN_NOT_FOUND -> 10, LAPD_ERR_DUP_DLCI --> 14, LAPD_ERR_DUP_CEI --> 15, LAPD_ERR_USER_ALLOC --> 16. Cause: The MDG was unable to successfully initiate a LAPD link with its peer.
R Y
U EMPTY
R Y
U EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-35

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
259
Link: LapdEstReq() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
Error calling LapdEstReq for primary/secondary link of DAP <DAP ID> status <status id>
Critical
EMPTY
Cause: The MDG was unable to successfully initiate a LAPD link with its peer.
Y C / l N e a r R Y
Comments & Notes
U EMPTY
260
Link: LapdSuRem() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error removing service user for ACG <acg id> DLCI <dlci> Port <port_id>
Critical
EMPTY
Cause: The MDG was unable to deallocate its LAPD link control block.
R Y
U EMPTY
260
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Unable to remove service user for secondary of DAP <dap id> DLCI <dlci> Port <port_id> 1 Unable to remove service user for primary of DAP <dap id> DLCI <dlci> Port <port_id> 1 Error calling LapdSuRem for DAP <dap id> DLCI <dlci> Port <port_id>
Critical
EMPTY
R Y
U EMPTY
260
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
Critical
EMPTY
R Y
U EMPTY
260
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
Critical
EMPTY
R Y
U EMPTY
260
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error calling LapdSuRem for ACG <acg id> DLCI <dlci> Port <port_id>
Critical
EMPTY
R Y
U EMPTY
261
Link: LapdEstRsp() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error calling LapdEstRsp for ACG <acg id> DLCI <dlci> Port <port_id>
Critical
EMPTY
Cause: The MDG failed in responding to a connection request from a peer network element.
R Y
U EMPTY
261
Link: LapdEstRsp() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error calling LapdEstRsp for DAP <dap id> DLCI <dlci> Port <port_id>
Critical
EMPTY
Cause: The MDG failed in responding to a connection request from a peer network element.
R Y
U EMPTY
262
Link: LapdRelReq() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
Error calling LapdRelReq for ACG <ACG ID>
Critical
EMPTY
Cause: The MDG was unable to successfully disconnect a LAPD link.
R Y
U EMPTY
262
Link: LapdRelReq() failed
1.3.6.1.4. 1.161.3.3
mdgLink
1 Error calling LapdRelReq for primary/secondary link of
Critical
EMPTY
Cause: The MDG was unable to successfully disconnect a LAPD link.
R Y
U EMPTY
MDG2-36
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
.5.1.8.1.0
DAP <DAP ID>
263
Link: LapdDatReq() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error calling LapdDatReq for ACG <ID> DLCI <DLCI> PORT <PORT id>
Critical
263
Link: LapdDatReq() failed
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Error calling LapdDatReq for primary/secondary link of DAP <ID> DLCI <DLCI> PORT <PORT id> 1 ICS_LINK_PORTSTAT queue is not empty
Critical
264
Link: ICS queue not empty
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
Critical
264
Link: ICS queue not empty
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 ICS_LINK_OBLAPD queue is not empty
Critical
265
Link: Link Version Check proc error
1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMAL
265
Link: Link Version Check proc error
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgMDL
1 3 2 0 0 1 1 5
Unrecognized ACG event in LM_ACGVCheck for ACG <ACG ID>
Critical
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
EMPTY
Cause: The MDG was unable to transmit data to its peer along a LAPD link.
R Y
U EMPTY
EMPTY
Cause: The MDG was unable to transmit data to its peer along a LAPD link.
R Y
U EMPTY
EMPTY
Cause: On initialization, an ICS queue (which should be empty) contained one or more messages.
R Y
U EMPTY
EMPTY
Cause: On initialization, an ICS queue (which should be empty) contained one or more messages.
R Y
U EMPTY
EMPTY
Cause: An internal processing error occurred while carrying out Link Version protocol.
R Y
U EMPTY
Unrecognized DAP event in LM_DAPVCheck for DAP <DAP ID>
Critical
EMPTY
Cause: An internal processing error occurred while carrying out Link Version protocol.
R Y
U EMPTY
266
Link: Network Routing proc error
mdgLink
1 Discarding message due to unrecognized destination function id : <func_id>
Critical
EMPTY
Cause: An error occurred during transmission of an ITC message.
R Y
U EMPTY
266
Link: Network Routing proc error
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Unrecognized network element type in SuLapdRelCnf
Critical
EMPTY
Cause: An error occurred during transmission of an ITC message.
R Y
U EMPTY
267
Link: Driver_Link interface error
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Received a PORT_UP message from undefined PORT <PORT id>
Critical
EMPTY
Cause: A status message was received from the communication driver for an undefined port.
R Y
U EMPTY
October 30, 2008
MDG2-37

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
267
Link: Driver_Link interface error
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Received a PORT_DOWN message from undefined PORT <PORT id>
Critical
EMPTY
Cause: A status message was received from the communication driver for an undefined port.
R Y
U EMPTY
268
Link: LMI processing failure
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Unrecognized function id in LM_KeepAlive
Critical
EMPTY
Cause: An internal processing error has occurred during frame relay Local Management Interface processing.
R Y
U EMPTY
269
Link: Invalid X731 State
1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMAL
269
Link: Invalid X731 State
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMDL
1 3 2 0 0 1 1 5 1 3 2 0 0 1 1 5 1 3 2 0 0 1 1 5
Error in ACG state for ACG <ACG ID>
Major
EMPTY
Cause: An invalid processing state has been detected for a MDG-ACG or MDG-DAP communication link object.
R N
U EMPTY
Error in DAP state for DAP <DAP ID>
Major
EMPTY
Cause: An invalid processing state has been detected for a MDG-ACG or MDG-DAP communication link object.
R N
U EMPTY
270
Link: Invalid LAPD State
mdgMAL
Discarding ACG message for ACG <acg id> due to invalid LAPD state
Major
EMPTY
Cause: An invalid processing state has been detected on LAPD link.
R N
U EMPTY
270
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgMDL
Discarding DAP message for DAP <dap id> due to invalid LAPD state
Major
EMPTY
R N
U EMPTY
270
mdgMAL
Error in LAPD state for ACG <acg id> DLCI <dlci> Port <port_id>
Major
EMPTY
R N
U EMPTY
270
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3
mdgMDL
Error in LAPD state for DAP <dap id> DLCI <dlci> Port <port_id>
Major
EMPTY
R N
U EMPTY
271
Link: Invalid VCHECK State
mdgMAL
1 invalid ACG Version Check - transition for ACG <ACG ID>
Major
EMPTY
Cause: An invalid processing state has been detected during Link Version
R N
U EMPTY
MDG2-38
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
.5.1.8.2.5 .2.1.1
271
Link: Invalid VCHECK State
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgMDL
3 2 0 0 1 Invalid DAP Version Check - transition for DAP <DAP ID> 1 5 1 VANCOUVER_INIT_FAILUR E
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r protocol.
Comments & Notes
Major
EMPTY
Cause: An invalid processing state has been detected during Link Version protocol.
R N
U EMPTY
272
ECP: Vancouver Initialization Failure
mdgECP
Critical
EMPTY
Cause: Data encryption algorithm (Vancouver) failed test vector initialization.
R Y
U EMPTY
273
ECP: shipping room backup up; packet lost
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 SHIPPING_ROOM_BACKE D_UP
Critical
EMPTY
274
ECP: Packet length not positive
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_PACKET_LENGT H_NOT_POSITIVE
Critical
EMPTY
Cause: Shipping room backed up: packet lost. This is fatal for the packet but not the ECP. This is the case where data cannot be retrieved by the MDGp from the ECP. Cause: The packet length is not positive. This is fatal for the ECP.
R Y
U EMPTY
R Y
U EMPTY
275
ECP: read pointer invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_MDGP_READ_PT R_INVALID
Critical
EMPTY
276
ECP: write pointer invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_MDGP_WRITE_P TR_INVALID
Critical
EMPTY
277
ECP: encryption type invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_ENCRYPTION_T YPE_INVALID
Critical
EMPTY
Cause: Possible buffer corruption of the data. The read pointer is pointing to local memory or NULL. This is fatal for the packet but not for the ECP. The read pointer is invalid. Cause: Possible buffer corruption of the data. The write pointer is pointing to local memory or NULL. This is fatal for the packet but not for the ECP. The write pointer is invalid. Cause: This is fatal for the packet but not for the ECP. The encryption type is not valid.
R Y
U EMPTY
R Y
U EMPTY
R Y
U EMPTY
278
ECP: key size invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_KEY_SIZE_INVAL ID
Critical
EMPTY
Cause: The encryption key size is invalid. This is fatal for the packet but not for the ECP.
R Y
U EMPTY
279
ECP: bad MS2FNE packet
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 BAD_MS2FNE_PACKET
Critical
EMPTY
Cause: Corrupted or invalid data. The Packet is bad so the ECP throws it away. This is fatal for the MDGp but
R Y
U EMPTY
October 30, 2008
MDG2-39

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r not for the ECP. A bad work order from the MDGp was received and the ECP must be informed. This may be fatal for MDGp if it expects the packet to be processed. Cause: Corrupted or invalid data. The read from MS2FNE_Q queue failed. This is fatal for the packet but not for the ECP. The ECP was not able to get a queued work order for inbound data from the MDGp. This is fatal for the MDGp. Cause: Corrupted or invalid data. The read from FNE2MS_Q queue failed. This is fatal for the packet but not for the ECP. The ECP was not able to get a queued work order for outbound data from the MDGp. This is fatal for the MDGp. Cause: Corrupted or invalid data. An MS2FNE read from the MDGp failed. This is fatal for the packet but not for the ECP. The ECP was not able to get a work order for inbound data from the MDGp. This is fatal for the MDGp. Cause: Corrupted or invalid data. A MS2FNE bad data read. This is Fatal for the packet but not for the ECP. The ECP was not able to get a work order for outbound data from the MDGp. This is fatal for the MDGp. Cause: Possible buffer corruption of the outbound data. The message dma_read_outbound_streams: nonmatching data lengths. This is a forewarning with probably no affect, but MDG or OMC should be aware of the situation. Cause: Possible buffer corruption of the outbound data. The streams buffer pointers are not correct since the data block size is illegal. Cause: Possible buffer corruption of the inbound data. The dma_write_inbound_streams: next DCB pointer not NULL. There is a
Comments & Notes
280
ECP: MS2FNE queued DCB bad data read
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_QUEUED_DCB_E RROR
Critical
E M P T Y
EMPTY
R Y
U EMPTY
281
ECP: FNE2MS queued DCB bad data read
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_QUEUED_DCB_E RROR
Critical
E M P T Y
EMPTY
R Y
U EMPTY
282
ECP: MS2FNE bad data read
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_DATA_READ_ER ROR
Critical
EMPTY
R Y
U EMPTY
283
ECP: FNE2MS bad data read
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_DATA_READ_ER ROR
Critical
EMPTY
R Y
U EMPTY
284
ECP: data length not same on FNE2MS read
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_DATA_LENGTH_ MISMATCH
Critical
EMPTY
R Y
U EMPTY
285
ECP: FNE2MS block size invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_BLOCK_SIZE_IN VALID
Critical
286
ECP: last streams mblock pointer not NULL
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 DCB_LST_STRMS_MBLK_ PTR_NOT_NULL
Warning
E M P T Y E M P T
EMPTY
R Y
U EMPTY
EMPTY
R N
U EMPTY
MDG2-40
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r forewarning with probably no affect, but the MDG or OMC should be aware of the situation. The streams buffer seems to not be set up correctly as all data has been written yet there seems to be more to the streams structure. Cause: Possible buffer corruption of the inbound data. The streams buffer pointers are not correct since the data block size is illegal. Cause: Internal error on data transfer between the ECP and the MDGp. The dma_read_inbound_contiguous: DMA_READ_FAILURE. This is fatal for the packet but not an ECP Failure during DMA read of contiguous inbound data. The MDGp must be informed of such. This is fatal for the MDGp. Cause: Internal error on data transfer between the ECP and the MDGp. The dma_read_inbound_contiguous: DMA_READ_FAILURE. This is fatal for the packet but not an ECP Failure during DMA read of contiguous inbound data. The MDGp must be informed of such. This is fatal for the MDGp. Cause: Internal error on data transfer between the ECP and the MDGp. The dma_write_inbound_streams: DMA_WRITE_FAILURE. This is fatal for the packet but not for the ECP. There is Failure during DMA write of streams of inbound data. The MDGp must be informed. This is fatal for the MDGp. Cause: Internal error on data transfer between the ECP and the MDGp. The dma_write_outbound_contiguous: DMA_WRITE_FAILURE. This is fatal for the packet but not for the ECP. There is failure during DMA write of contiguous outbound data. The MDGp must be informed. This is fatal for the MDGp.
Comments & Notes
287
ECP: MS2FNE block size invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_BLOCK_SIZE_IN VALID
Critical
288
ECP: MS2FNE DMA read failure
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_DMA_READ_FAIL URE
Critical
E M P T Y E M P T Y
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
289
ECP: FNE2MS DMA read failure
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_DMA_READ_FAIL URE
Critical
E M P T Y
EMPTY
R Y
U EMPTY
290
ECP: MS2FNE DMA write failure
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_DMA_WRITE_FAI LURE
Critical
E M P T Y
EMPTY
R Y
U EMPTY
291
ECP: FNE2MS DMA write failure
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_DMA_WRITE_FAI LURE
Critical
E M P T Y
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-41

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
292
ECP: Encryption work room not free
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 WORK_ROOM_BUFFER_N OT_FREE
Critical
EMPTY
293
ECP: waiting room free
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 WAIT_ROOM_BUFFER_FR EE
Critical
E M P T Y
EMPTY
294
ECP: Encryption type no good
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 ENCRYPTION_TYPE_NO_ GOOD
Critical
E M P T Y
EMPTY
295
ECP: FNE2MS packet length not positive
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_PACKET_LENGT H_NOT_POSITIVE
Critical
296
ECP: FNE2MS MDGp read pointer invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_MDGP_READ_PT R_INVALID
Critical
297
ECP: FNE2MS MDGp write pointer invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_MDGP_WRITE_P TR_INVALID
Critical
298
ECP: FNE2MS encryption type invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_ENCRYPTION_T YPE_INVALID
Critical
299
ECP: FNE2MS key size invalid
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_KEY_SIZE_INVAL ID
Critical
processingF
300
ECP: Bad FNE2MS
1.3.6.1.4.
mdgECP
1 BAD_FNE2MS_PACKET
Critical
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E
EMPTY
Cause: Internal error in data encryption task. An Encryption task error has occurred: work room not free. This is fatal for the packet but not for the ECP. The work room is not free for the encryption task. The MDGp must be informed. This is fatal for the MDGp. Cause: Internal error in data encryption task. An Encryption task error: wait room free. This is fatal for the packet but not for the ECP. The wait room is free for the encryption task. The MDGp must be informed. This is fatal for the MDGp. Cause: Internal error in data encryption task. An Encryption task error has occurred: work room not free. This is fatal for the packet but not for the ECP. The work room is not free for the encryption task. The MDGp must be informed. This is fatal for the MDGp. Cause: FNE2MS packet length is not positive. This is fatal for the ECP.
Y C / l N e a r R Y
Comments & Notes
U EMPTY
R Y
U EMPTY
R Y
U EMPTY
R Y
U EMPTY
EMPTY
Cause: Possible buffer corruption on the outbound data. The FNE2MS read pointer is either NULL or local. This is illegal and the packet is discarded. Cause: Possible buffer corruption on the outbound data. The FNE2MS write pointer is either NULL or local. This is not legal therefore the packet is discarded. Cause: The FNE2MS encryption type is invalid. Packet is discarded.
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
Cause: The FNE2MS key size is less than 32 or greater than 64 bits. The packet is discarded.
R Y
U EMPTY
EMPTY
Cause: An internal ECP outbound
R Y
U EMPTY
MDG2-42
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
ailureEvent
packet
1.161.3.3 .5.1.5.1.0
301
TRAP: Trap Daemon self shutdown notification Mobility Management Task: Timeout for audit timer net_send_reliable() failed
1.3.6.1.4. 1.161.3.3 .5.1.18.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0
mdgTrap
1 Trap Daemon self shutdown notification
Critical
303
mdgMM
1 MM: mmCheckLifetime: MM Audit Response Timeout from dap <dap ID>
Major
304
mdgMM
1 MM: send_reg: MM Audit Req Net Send Fail; Dap=<dap ID> Status=<status code> 1 MM: mmPDReg: net_send_reliable failure Dap=<dap ID> Status=<status code>IMSI=<imsi> 1 SRPC NetSndReliable failed acg <acg ID> rag < rag ID> sector <sector ID> code < code ID> 1 MM Audit Rsp: DAP could not process request status = <status>
Major
304
net_send_reliable() failed
mdgMM
Major
304
net_send_reliable() failed
mdgSRP
Critical
306
Mobility Management Task: bad status code for audit response Mobility Management Task: invalid message type for audit response invalid message type
mdgMM
Major
307
mdgMM
1 MM Audit Rsp: bad msg type=<msg type>
Major
308
mdgRAG
1 Download Complete Req failure : Undefined RAG status DAP <DAP ID> RAG <RAG ID>
Major
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r packet processing error has occurred the packet is discarded.
Comments & Notes
EMPTY
Cause: If all configuration parameters for the trap daemon are invalid, 0's for ex., Trap Daemon will disable itself and send out this trap as a warning. Cause: This particular Audit timer has timed out. The audit response was expected.
R Y
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
Cause: An error occurred sending an ITC message to another network element (ACG or DAP)
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
Cause: The Status code of 0 was not stored in the audit response message.
R N
U EMPTY
EMPTY
Cause: The MDG/DAP message type of PD_MS_AUDIT_RSP was not stored in the audit response message.
R N
U EMPTY
EMPTY
308
invalid message type
1.3.6.1.4. 1.161.3.3
mdgBill
1 BILL Task: Invalid Registration Response Type
Major
EMPTY
Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or
R N
U EMPTY
R N
U EMPTY
October 30, 2008
MDG2-43

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG
Comments & Notes
.5.1.4.1.0
<invalid message> received in proc_BA_msg()
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid Billing Block Response Type <invalid message> received in proc_BA_msg()
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid Message Type <invalid message> received in proc_BA_msg()
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid Port Number <invalid message> received in proc_bill_BM_msg()
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid Bill-Link State <invalid message> received in proc_bill_BM_msg()
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid MDG Node State <invalid message> received in proc_bill_BM_msg()
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid Message Type <invalid message> received in proc_bill_BM_msg()
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid Port Number <invalid message> received in proc_billgen_msg()
Major
EMPTY
R N
U EMPTY
processingF
308
invalid message
1.3.6.1.4.
mdgBill
1 BILL Task: Invalid Message
Major
EMPTY
R N
U EMPTY
MDG2-44
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
ailureEvent
type
1.161.3.3 .5.1.4.1.0
Type <invalid message> received in proc_billgen_msg()
R e l a t e d A l a r m s M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field.
Comments & Notes
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid Port Number <invalid message> received in proc_bill_IP_msg()
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid MDG-IR Link State <invalid message> received in proc_bill_IP_msg()
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Invalid Message Type <invalid message> received in proc_bill_IP_msg()
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0
mdgRAG
1 Undefined message type to RDL: DAP <DAP ID>
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0
mdgMM
1 MM: mmCheckLifetime arg mismatch <p1, p2, p3>
Major
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0
mdgNod e
1 Invalid ICS message from ECP during board synch
Warning
EMPTY
R N
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0
mdgRAG
1 Unexpected RAG Complete Req: DAP<DAP ID>RAG <RAG >
Warning
EMPTY
R N
U EMPTY
October 30, 2008
MDG2-45

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
308
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0
mdgNod e
1 Undefined ICS msg from RDL
Warning
EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0
mdgNod e
1 Undefined ICS msg from MM
Warning
EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0
mdgNod e
1 Undefined msg from NET
Warning
EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0
mdgNod e
1 BM Trap Proxy failure: Undefined trap for relay
Warning
EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0
mdgMLI NK
1 MLNK: Invalid message type <message type> received in File <file name> Line <line number>
Major
EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgVDR C
1 VCRT: handle_data. Invalid message type on data queue. Type = <type>
Major
EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgVDR C
1 VCRT: handle_crtl. Invalid msg type on ctrl queue. Type = <type>
Major
EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgVDR C
1 VCRT: process_resync_start_respo nse. Invalid msg status = <status>
Major
EMPTY
Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type
Y C / l N e a r R N
Comments & Notes
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
MDG2-46
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: A message within the MDG sent from either one task to another or received from another iDEN network entity contains as part of the message, an invalid value in the message type field. Cause: An error occurred when making a call to a psos system function. R N
Comments & Notes
308
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgVDR C
1 VCRT: process_resync_done_respo nse. Invalid msg status = <status>. Received stop upon completion. 1 VCRT: process_rep_response. Replication response error. Invalid msg status = <status> 1 <File name> <Line number> Failed t_ident. <return val> <error code>
Major
U EMPTY
308
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgVDR C
Major
EMPTY
R N
U EMPTY
310
psos system call failed
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgRIP
Critical
EMPTY
R Y
U EMPTY
310
mdgRIP
1 <File name> <Line number> Failed setting priority. <return val>
Critical
EMPTY
Cause: An error occurred when making a call to a psos system function.
R Y
U EMPTY
310
mdgRIP
1 <File name> <Line number> Failed RIP socket. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
310
mdgRIP
1 <File name> <Line number> Cant Bind RIP socket. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
310
mdgMLI NK
1 MLNK: ev_send failed in Sig_Hnd_func: Error <error code>
Major
EMPTY
Cause:An error occurred when making a call to a psos system function.
R N
U EMPTY
311
pna system call failed
mdgBill
1 BILL Task: Socket creation failed in bill_task_init()
Critical
EMPTY
R Y
U EMPTY
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Socket bind() call failed in bill_task_init()
Critical
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-47

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: An error occurred when making a call to a pna system function. R Y
Comments & Notes
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: select() call failed in select_and_timer()
Critical
U EMPTY
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Socket close() call failed in close_BSP_session()
Major
EMPTY
R Y
U EMPTY
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: ioctl() call failed in create_BA_soc()
Major
EMPTY
R Y
U EMPTY
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Bad socket descriptor in connect() call in exe_BSP_session()
Critical
EMPTY
R Y
U EMPTY
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: No internal buffs available for connect() in File <file name> Line <line number> 1 BILL Task: recv() call failure in proc_bill_BM_msg()
Major
EMPTY
R Y
U EMPTY
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
Major
EMPTY
R Y
U EMPTY
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Soc.buff size cannot be changed to 8K
Major
EMPTY
R Y
U EMPTY
311
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0
mdgRIP
1 <File name> <Line number> Failed select. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
311
mdgRIP
1 <File name> <Line number> Input on IOCTL socket. <error code>
Critical
EMPTY
R Y
U EMPTY
processingF
311
pna system call
mdgRIP
1 <File name> <Line number>
Critical
EMPTY
Cause: An error occurred when making
R Y
U EMPTY
MDG2-48
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
ailureEvent
failed
311
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1.
Cant IP_ADD_MEMBERSHIP. <return val> <error code> mdgRIP 1 <File name> <Line number> Failed IOCTL, FIONBIO. <return val> <error code> Critical
311
mdgRIP
1 <File name> <Line number> Failed Setsockopt, SO_BROADCAST. <return val> <error code> 1 <File name> <Line number> Failed Setsockopt, SO_RCVBUF. <return val> <error code> 1 <File name> <Line number> rbuf too small. <rbuf> <error code>
Critical
311
mdgRIP
Critical
311
mdgRIP
Critical
311
mdgRIP
1 <File name> <Line number> COA failed add_ni. <address of COA var> <error code>
Critical
311
mdgRIP
1 <File name> <Line #> Error on rtcoa_add.
Critical
311
mdgRIP
1 <File name> <Line #> init_eth failed configure_eth. <return val>
Critical
311
mdgRIP
1 <File name> <Line #> Failed ev_sock. <return val> < error code>
Critical
311
mdgRIP
1 <File name> <Line number> Failed ev_sock bind. <return val> <error code>
Critical
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r a call to a pna system function.
Comments & Notes
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-49

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
0 processingF ailureEvent 311 pna system call failed 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 mdgRIP 1 <File name> <Line #> Failed setsockopt. <return val> <error code> Critical
EMPTY
R Y
U EMPTY
311
mdgRIP
1 <File name> <Line #> Failed socket rt_sock. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
311
mdgRIP
1 <File name> <Line #> Failed IOCTL rt_sock. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
311
mdgRIP
1 <File name> <Line #> Failed IOCTL SOICFIFCONF. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
311
mdgRIP
1 <File name> <Line #> Failed IOCTL SIOCGIFFLAGS. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
311
mdgRIP
1 <File name> <Line #> Failed IOCTL SIOCMODRT. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
311
mdgRIP
1 <File name> <Line #> Failed IOCTL GETIF_FLAGS. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
311
mdgRIP
1 <File name> <Line #> Failed IOCTL SETIF_FLAGS. <return val> <error code>
Critical
EMPTY
R Y
U EMPTY
311
mdgRIP
1 <File name> <Line #> init_eth failed add_ni. <address of ethernet var> <error code>
Critical
EMPTY
R Y
U EMPTY
MDG2-50
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
311
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgRIP
1 <File name> <Line #> Failed setsockopt <error code>
Critical
311
mdgRIP
1 <File name> <Line #> Failed IOCTL. <error code>
Critical
311
mdgRIP
1 <File name> <Line #> Negative recvfrom. <return val> <error code>
Major
311
mdgRIP
1 <File name> <Line #> Nothing to read. <return val>
Major
311
mdgRIP
1 <File name> <Line #> Negative fromlen. <from length> <error code>
Major
311
mdgBill
1 BILL Task: Socket creation failed in create_BA_soc()
Major
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL-task: Connect() failed after <#> attempts in File <file name>.Resetting MDG.
Critical
311
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: Socket creation failed after <#> attempts.Resetting MDG
Critical
311
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3
mdgMLI NK
311
mdgMLI NK
1 MLNK: ioctl call failed FIONBIO for MDG[<MDGid>]MDG[<MDGid>] socket: Error <error code> 1 MLNK: ioctl call failed FIOASYNC for
Major
Major
Remedy
R e p o r t &
O u t a g e
EMPTY
Y C / l N e a r R Y
Comments & Notes
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
MDG2-51

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
.5.1.19.4. 0 processingF ailureEvent 311 pna system call failed 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 mdgMLI NK
MDG[<MDGid>]MDG[<MDGid>] socket: Error <error code> 1 MLNK: ioctl call failed FIOSETOWN for MDG[<MDGidMDG[<MDGid >] socket: Error <error code> 1 MLNK: Socket creation failed for MDG[<MDGid>MDG[<MDGid>] link: Error <error code> 1 MLNK: Socket listen failed for MDG[<MDGid>] server listening socket. Error <error code> 1 MLNK: Socket creation failed for MDG[<MDGid>] server listening socket. Error <error code> 1 MLNK: ioctl call failed FIOSETOWN for MDG[<MDGid>] server listening socket. Error <error code> 1 MLNK: ioctl call failed FIOASYNC for MDG[<MDGid>] server listening socket. Error <error code> 1 MLNK: ioctl call failed FIONBIO for MDG[<MDGid>] server listening socket. Error <error code> 1 MLNK: Socket bind failed for MDG[<MDGid>] server listening socket. Error <error code> 1 MLNK:MDG[<mdgid>] Socket accept call failed:Error<error code>
Major
EMPTY
Cause:An error occurred when making a call to a pna system function.
R N
U EMPTY
311
mdgMLI NK
Major
EMPTY
Cause:An error occurred when making a call to a pna system function.
R N
U EMPTY
311
mdgMLI NK
Critical
EMPTY
R Y
U EMPTY
311
mdgMLI NK
Critical
EMPTY
R Y
U EMPTY
311
mdgMLI NK
Critical
EMPTY
R Y
U EMPTY
311
mdgMLI NK
Critical
EMPTY
R Y
U EMPTY
311
mdgMLI NK
Critical
EMPTY
R Y
U EMPTY
311
mdgMLI NK
Critical
EMPTY
R Y
U EMPTY
311
mdgMLI NK
Major
EMPTY
R N
U EMPTY
MDG2-52
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
311
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0
mdgMLI NK
311
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgMLI NK
1 MLNK:Could not bring up mdg link on address = <address> subnet = <subnet mask> gateway = <gateway> in process_event() Line <Line number> 1 MLNK:Connect() failed with ENOBUFS error for MDG[<mdgid>]MDG[<mdgid>] link. 1 BILL Task: getutctime() failed in update_ready_to_send_Q()
Critical
R e l a t e d A l a r m s Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: An error occurred when making a call to a pna system function. MDG may be configured with an invalid IP address or default gateway. R Y
Comments & Notes
U EMPTY
Major
312
get UTC time failed
mdgBill
Major
312
get UTC time failed
1.3.6.1.4. 1.161.3.3 .5.1.4.2.1 8.0 1.3.6.1.4. 1.161.3.3 .5.1.4.2.1 8.0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgBillG en
1 ppr-BillGen: getutctime() failed in set_first_buffer()
Major
312
get UTC time failed
mdgBillG en
1 ppr-BillGen: getutctime() failed in bill_rec_ready_req()
Major
312
get UTC time failed
mdgNod e
1 Get UTC time failure: get_timestamp
Critical
312
get UTC time failed
mdgRAG
1 Get UTC time failure: rag_get_utc_time
Critical
312
get UTC time failed
mdgMM
1 MM: get_ntp_time: Bad UTC time
Critical
313
ECP: MS2FNE Queue Overflow
mdgECP
1 MS2FNE_QUEUE_OVERFL OW
Critical
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T
EMPTY
R N
U EMPTY
EMPTY
Cause: An error occurred when trying to retrieve the UTC time.
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
Cause: An inbound queue overflow has occurred in the ECP.
R Y
U EMPTY
October 30, 2008
MDG2-53

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: An outbound queue overflow has occurred in the ECP. R Y
Comments & Notes
314
ECP: FNE2MS Queue Overflow
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_QUEUE_OVERFL OW
Critical
U EMPTY
315
ECP: Cipher Counter Direction Wrong
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 CIPHER_CNTR_DIRECTIO N_WRONG
Critical
EMPTY
Cause: Internal encryption processing failure. ECP encryption cipher counter direction is wrong.
R Y
U EMPTY
316
ECP: Cipher Counter Direction Mismatch
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 CIPHER_CNTR_DIRECTIO N_MISMATCH
Critical
EMPTY
Cause: Internal encryption processing failure. ECP encryption cipher counter direction mismatch.
R Y
U EMPTY
317
Link: LAPD general failure
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 LapdTxI: LapdPhDatReq failed
Critical
EMPTY
Cause: An internal LAPD error has occurred while attempting packet transmission.
R Y
U EMPTY
317
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 LapdTxRr: LapdPhDatReq failed
Critical
EMPTY
R Y
U EMPTY
317
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 LapdTxRnr: LapdPhDatReq failed
Critical
EMPTY
R Y
U EMPTY
317
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 MDG-OPERATOR <reset cold> command detected
Critical
EMPTY
R Y
U EMPTY
317
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 MDG-OPERATOR <reset warm> command detected
Critical
EMPTY
R Y
U EMPTY
318
Billing: MDG is not in the BA database
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: proc_BA_msg(): MDG <MDG number> is not registered in the BA database
Major
EMPTY
Cause: Each Billing Accumulator maintains a database of all MDGnodes (by their MDG-IDs), which may send billing records. If it receives a registration request from an MDG-node which is not in its database, it will send
R N
U EMPTY
MDG2-54
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r "Non-registered MDG NACK". In response to this message, the MDGnode will send an alarm. Cause: This registration-NACK is for future use. If an MDG-node can not be registered because of none of the above mentioned reasons, a BA will send "General-NACK" to an MDGnode and response to that the MDGnode will send an alarm. Cause: DAP_ID is out of range.
Comments & Notes
319
Billing: registration general NACK
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: General NACK on registration request in proc_BA_msg()
Major
E M P T Y
EMPTY
R N
U EMPTY
320
Invalid DAP ID
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3
mdgRAG
1 RAG Verify Resp failure: Invalid DAP <DAP ID>
Major
320
Invalid DAP ID
mdgMM
1 MM: mmRagAddReq: Invalid Dap ID = <DAP ID>
Major
320
Invalid DAP ID
mdgMM
1 MM: mmRagDeleteReq: Invalid Dap ID = <DAP ID>
Major
321
Invalid RAG ID
mdgMM
1 MM: mmRagAddReq: Invalid Rag ID = <RAG ID>
Major
321
Invalid RAG ID
mdgMM
1 MM: mmRagDeleteReq: Invalid Rag ID = <RAG ID>
Major
321
Invalid RAG ID
mdgVDR C
1 VCRT: process_bm_start. Invalid rag id = <rag>
Major
321
Invalid RAG ID
mdgVDR C
1 VCRT: process_bm_stop. Invalid rag id = <rag>
Major
321
Invalid RAG ID
mdgVDR C
1 VCRT: process_resync_start_respo
Major
EMPTY
R N
U EMPTY
EMPTY
Cause: DAP_ID is out of range.
R N
U EMPTY
EMPTY
Cause: DAP_ID is out of range.
R N
U EMPTY
EMPTY
Cause: RAG_ID is out of range.
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
MDG2-55

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
.5.1.19.5. 0 processingF ailureEvent 321 Invalid RAG ID 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.4.1.0 mdgVDR C
nse. Invalid rag id in msg. rag = <rag> 1 VCRT: process_resync_done_respo nse. Invalid rag id in msg. rag = <rag> 1 VCRT: process_rep_response. Replication response error. Invalid msg status = <status> 1 RAG Verify Resp failure: Badly Formatted Message / Mismatch Sequence Number / Unexpected message DAP <id>. 1 Badly Formatted Message: <ACG/DAP> <id> Major
EMPTY
R N
U EMPTY
321
Invalid RAG ID
mdgVDR C
Major
EMPTY
R N
U EMPTY
323
Board Manager: Bad Message RAG Verification Request Board Manager: Bad Message RAG Update Request
mdgRAG
Major
EMPTY
Cause: A Badly formatted RAG Verification Request message has been received.
R N
U EMPTY
324
mdgRAG
Major
EMPTY
Cause: A badly formatted RAG Update Request message has been received.
R N
U EMPTY
325
Board Manager: Board Synchronization Timeout Board Manager: SNMP Error
mdgNod e
1 Board Synch Failed
Critical
EMPTY
Cause: The timer timed out waiting for all MDG boards (processor, IO, ECP), to be synchronized.
R N
U EMPTY
326
mdgBill
1 Attempt at locking already locked Billing X731 admin state
Warning
EMPTY
Cause: An Illegal SNMP command, either set or get, has been issued.
R Y
U EMPTY
326
Board Manager: SNMP Error
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgRIP
1 Attempt at locking already locked IR X731 admin state
Warning
EMPTY
R Y
U EMPTY
326
mdgBill
1 Attempt at unlocking already unlocked Billing X731 admin state
Warning
EMPTY
R Y
U EMPTY
326
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0
mdgRIP
1 Attempt at unlocking already unlocked IR X731 admin state
Warning
EMPTY
R Y
U EMPTY
MDG2-56
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
326
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0
mdgRAG
1 Full DAP download completed:New PD registrations allowed for RAG<id> 1 <File name> <Line number>Modify_intnet. No modifications to intnet list.
Warning
327
RIP: Out of range config value
mdgRIP
Warning
R e l a t e d A l a r m s Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: New PD registration allowed after full download complete. R N
Comments & Notes
U EMPTY
EMPTY
327
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0
mdgRIP
1 <File name> <Line #> Warning, No change in interface. <interface flag>
Warning
EMPTY
327
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0
mdgRIP
1 <File name> <Line number>IP Netmask is discontiguous! 0X<netmask>
Critical
EMPTY
327
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0
mdgRIP
1 <File name> <Line number>COA not A, B or C. 0x<COA IP address>
Critical
EMPTY
327
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0
mdgRIP
1 <File name> <Line number>init_eth, myaddr not A, B or C. 0x<MDG IP address>
Critical
EMPTY
327
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0
mdgRIP
1 <File name> <Line number>Too many network bits in IP netmask! 0X<netmask>
Critical
EMPTY
327
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0
mdgRIP
1 <File name> <Line #> modify_intnet bad metric. <metric>
Critical
EMPTY
Cause: This occurs when a critical value appears out-of-range. If the data item were used for processing, the result would be unpredictable. Typically this pertains to bad COA/IP addresses or, metric values. Cause: This occurs when a critical value appears out-of-range. If the data item were used for processing, the result would be unpredictable. Typically this pertains to bad COA/IP addresses or, metric values. Cause: This occurs when a critical value appears out-of-range. If the data item were used for processing, the result would be unpredictable. Typically this pertains to bad COA/IP addresses or, metric values. Cause: This occurs when a critical value appears out-of-range. If the data item were used for processing, the result would be unpredictable. Typically this pertains to bad COA/IP addresses or, metric values. Cause: This occurs when a critical value appears out-of-range. If the data item were used for processing, the result would be unpredictable. Typically this pertains to bad COA/IP addresses or, metric values. Cause: This occurs when a critical value appears out-of-range. If the data item were used for processing, the result would be unpredictable. Typically this pertains to bad COA/IP addresses or, metric values. Cause: This occurs when a critical value appears out-of-range. If the data item were used for processing, the result would be unpredictable. Typically this pertains to bad COA/IP
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R Y
U EMPTY
R Y
U EMPTY
R Y
U EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-57

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY addresses or, metric values. Cause: This is generated when a communications socket detects input when the X731 state of the machine is locked. Cause: The box manager sent a message (via FIBS) to RIP and RIP does not understand the message type. Cause: The box manager sent a message (via FIBS) to RIP and RIP does not understand the message type. Cause: FIBS has forwarded a message to RIP and RIP does not understand the message type. R N
Comments & Notes
328
RIP: Ethernet traffic detected when interface is off
1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgRIP
1 <File name> <Line number>Sockets Active with eth off
Major
U EMPTY
329
RIP: Bad message from BM
mdgRIP
1 <File name> <Line number>Unrecognized BM_IR_LINK type from BM. 0x<type> 1 <File name> <Line number>Unrecognized COA_ADVERT type from BM. 0x<state> 1 <File name> <Line number>Unrecognized FIBS type. 0x<type>
Major
EMPTY
R N
U EMPTY
329
RIP: Bad message from BM
mdgRIP
Major
EMPTY
R N
U EMPTY
330
RIP: Bad message from FIBS
mdgRIP
Major
EMPTY
R N
U EMPTY
331
ECP General Critical Message
mdgECP
1 MS2FNE: next mblk is current mblk (inbound)
Critical
EMPTY
Cause: Internal ECP buffering failure next mblk pointer is the current mblk pointer.
R N
U EMPTY
331
ECP General Critical Message
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS: next mblk is current mblk (outbound)
Critical
EMPTY
Cause: Internal ECP buffering failure next mblk pointer is the current mblk pointer.
R Y
U EMPTY
333
bm_free() failed
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: bm_free() failed in free_bill_rec_mem()
Critical
EMPTY
Cause: An error occurred freeing a memory buffer.
R Y
U EMPTY
333
bm_free() failed
1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgBill
1 BILL Task: bm_free() failed in update_retrieve_ready_Q()
Critical
EMPTY
R Y
U EMPTY
333
bm_free() failed
1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgMIP
1 FIBS: bm_free failed
Major
EMPTY
R Y
U EMPTY
processingF
333
bm_free() failed
1.3.6.1.4.
mdgMIP
Mobile IP: PendRegFree:
Critical
EMPTY
Cause: An error occurred freeing a
R N
U EMPTY
MDG2-58
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
ailureEvent
1.161.3.3 .5.1.9.1.0
free failure <return val>
333
bm_free() failed
1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2.
mdgRAG
1 bm_free_error: <bm_code_bm_free> <file_name> <line_number>
Critical
333
bm_free() failed
mdgSRP
1 SFU_T: sfu_main() bm_free Failure
Critical
333
bm_free() failed
mdgSRP
1 SFU_T: inbound SRP bm_free Failure
Critical
333
bm_free() failed
mdgSRP
1 SFU_T: outbound SRP bm_free Failure
Critical
333
bm_free() failed
mdgRFC L
1 bm_free fails, ERR_CODE: <Error code>!
Critical
333
bm_free() failed
mdgSLM
Critical
334
bm_free_stream() failed
mdgRAG
1 bm_free_stream_error: <bm_code_bm_free> <file_name> <line_number>.
Critical
334
mdgSLM
1 bm_free_stream fails, ERR_CODE: <Error code>!
Critical
334
mdgRFC L
1 bm_free_stream fails, ERR_CODE: <Error code>!
Critical
Remedy
R e p o r t &
O u t a g e
Comments & Notes
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
Cause: An error occurred freeing a streams memory buffer.
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-59

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
5.1.0 processingF ailureEvent 336 bm_prev_watchdog _timeout() 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0 mdgLink 1 Previous reset caused by watchdog timeout Warning
EMPTY
Cause: The previous MDG system reset was caused by a watchdog timeout.
R Y
U EMPTY
337
Performance Management Registration Callback Failed Performance Management Registration Callback Failed timer_db_del() failed
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgMM
337
mdgMM
338
mdgSRP
1 MM: MMInit: OB_DATAGM_ARRIVAL_R ATE pm_register_callback failure; result=<result number> 1 MM: MMInit: WIDEN_OB_DATAGM_ARR IVAL_RATE pm_register_callback failure; result=<result number> 1 SFU_T: sfu_main() timer_db_del Failure
Major
EMPTY
Cause: Registration of a callback function with performance management has occurred. Statistics will not be properly collected. Cause: Registration of a callback function with performance management has occurred. Statistics will not be properly collected. Cause: An error occurred when deleting a timer from the timer database.
R N
U EMPTY
Major
EMPTY
R N
U EMPTY
Critical
EMPTY
R N
U EMPTY
338
timer_db_del() failed
mdgSRP
1 SFU_T: inbound SRP timer_db_del Failure
Critical
EMPTY
Cause: An error occurred when deleting a timer from the timer database.
R Y
U EMPTY
338
mdgMLI NK
1 MLNK: Failed to delete <timer name>[<MDGid>] timer in File <file name> Line <line number> 1 MLNK: Timer delete failed for MDG[<mdgid>]
Critical
EMPTY
R Y
U EMPTY
338
mdgMLI NK
Critical
EMPTY
R Y
U EMPTY
338
mdgVDR C
1 VCRT: handle_timeouts. Timer delete failed.
Major
EMPTY
R N
U EMPTY
338
mdgVDR C
1 VCRT: timer_delete. Could not delete timer = <id>
Major
EMPTY
R N
U EMPTY
MDG2-60
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
339
SRP: Bad event
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3
mdgSRP
1 SFU_T: inbound SRP invalid event encountered
Warning
339
SRP: Bad event
mdgSRP
1 SRPC_MS invalid event: TEI <number>, current state <number>, Event <number>
Major
339
SRP: Bad event
mdgSRP
339
SRP: Bad event
mdgSRP
339
SRP: Bad event
mdgSRP
1 SRPC_OBJ invalid event: SEC <number>, RAG <number>, ACG <number>, State <number>, Event <number> 1 SRPC_OBJ invalid state: SEC <number>, RAG <number>, ACG <number>, State <number>, Event <number> 1 SRPC_MS invalid state: TEI <number>, State <number>, Event <number>
Major
Major
Major
339
SRP: Bad event
mdgSRP
1 SRPC invalid channel grant msg acg <acg_id>, sec <sector_id>, rag <rag_id>, bndl_id <srp bundle id> 1 SFU_T: invalid event <event_id> TEI <tei> bid <bundle_id> sfu seq <sequence num> 1 SRPC_MS invalid acg_id <id number> at chnnd_s1 TEI <TEI number>
Major
339
SRP: Bad event
mdgSRP
Warning
340
Invalid ACG ID
mdgSRP
Major
340
Invalid ACG ID
mdgSRP
1 SRPC_MS invalid acg_id <id number> at datareq_s4 TEI <TEI number>
Major
340
Invalid ACG ID
mdgSRP
1 SRPC_MS invalid acg_id <id number> at timeout_s3 TEI
Major
Remedy
R e p o r t &
O u t a g e
EMPTY
Cause: SRP receives an invalid event for a given state.
Y C / l N e a r R Y
Comments & Notes
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R Y
N EMPTY
EMPTY
Cause: An error occurred when referencing an ACG ID of an ACG that is non-existent
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
Cause: An error occurred when referencing an ACG ID of an ACG that
R N
U EMPTY
October 30, 2008
MDG2-61

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r is non-existent
Comments & Notes
.5.1.13.2. 4.1.0 processingF ailureEvent 340 Invalid ACG ID 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.5.1.0 mdgSRP
<TEI number>
1 SRPC_MS invalid acg_id <id number> at cncltimr_s3 TEI <TEI number>
Major
EMPTY
R N
U EMPTY
340
Invalid ACG ID
mdgSRP
1 SFU_T: inbound SRP invalid ACG_ID from ACG_LOOKUP < DLCI number><Port number> 1 SFU_T: SFU came from invalid ACG <acg_id>
Warning
EMPTY
R N
U EMPTY
340
Invalid ACG ID
mdgSRP
Warning
EMPTY
R N
N EMPTY
341
ECP: FNE2MS packet length excessive
mdgECP
1 FNE2MS_PACKET_LENGT H_EXCESSIVE
Warning
EMPTY
Cause: The data length is out of range. This is fatal for the packet but not for the ECP.
R N
U EMPTY
342
ECP: MS2FNE packet length excessive
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_PACKET_LENGT H_EXCESSIVE
Warning
EMPTY
Cause: The data length is out of range. This is fatal for the packet but not for the ECP.
R N
U EMPTY
343
ECP: FNE2MS compression type no good
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_COMPRESSION_ TYPE_NO_GOOD
Critical
EMPTY
344
ECP: MS2FNE compression type no good
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_COMPRESSION_ TYPE_NO_GOOD
Critical
E M P T Y
EMPTY
345
ECP: MS2FNE insufficient streams buffer
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_INSUFFICIENT_S TREAMS_BUFFER
Critical
E M P T Y
EMPTY
Cause: An Unrecognized compression type has occurred. This will not change to fatal for the packet, but the ECP will perform no compression, since the compression type is not valid. The MDGp must be informed. This is fatal for the MDGp. Cause: An Unrecognized compression type has occurred. This will not change to fatal for the packet, but the ECP will perform no compression, since the compression type is not valid. The MDGp must be informed. This is fatal for the MDGp. Cause: Internal error during data transfer between the ECP and MDGp. The dma_write_inbound_streams function fails to advance to next streams block to write to. This is fatal
R N
U EMPTY
R N
U EMPTY
R Y
U EMPTY
MDG2-62
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r for the packet but not for the ECP. There is Failure during DMA write of streams of inbound data. The MDGp must be informed. This is fatal for the MDGp. Cause: Internal error in intertask communications between the ECP and MDGp. An error occurred while reading from the ICS queue designated for dictionary control messages. Cause: An error occurred while deleting the outbound compression dictionary.
Comments & Notes
346
ECP: dictionary ICS receive failure
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 DICTIONARY_ICS_RECEIV E_FAILURE
Critical
347
ECP: FNE2MS dictionary deletion failure
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_DICTIONARY_DE LETION_FAILURE
Critical
348
ECP: MS2FNE dictionary deletion failure
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_DICTIONARY_DE LETION_FAILURE
Critical
349
ECP: cannot delete null FNE2MS dictionary
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 CANNOT_DELETE_NULL_ FNE2MS_DICTIONARY
Critical
350
ECP: cannot delete null MS2FNE dictionary
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 CANNOT_DELETE_NULL_ MS2FNE_DICTIONARY
Critical
351
ECP: FNE2MS free MS2FNE dictionary fail
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_FREE_MS2FNE_ DICT_FAIL
Critical
352
ECP: MS2FNE dictionary creation failure
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_DICTIONARY_CR EATION_FAILURE
Critical
353
ECP: FNE2MS dictionary creation failure
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_DICTIONARY_CR EATION_FAILURE
Critical
354
ECP: MS2FNE dictionary already
1.3.6.1.4. 1.161.3.3
mdgECP
1 MS2FNE_DICTIONARY_AL READY_EXISTS
Critical
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M
EMPTY
R Y
U EMPTY
EMPTY
R Y
U EMPTY
EMPTY
Cause: An error occurred while deleting the inbound compression dictionary.
R Y
U EMPTY
EMPTY
Cause: Dictionary pointer for the outbound compression dictionary to be deleted is already NULL (deleted).
R Y
U EMPTY
EMPTY
Cause: Dictionary pointer for the inbound compression dictionary to be deleted is already NULL (deleted).
R Y
U EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Cause: Internal error in buffer allocation/deallocation. Freeing inbound dictionary fails when deleting inbound dictionary due to outbound dictionary creation failure. Cause: Internal error in buffer allocation/deallocation. Failure to create inbound compression dictionary. Dictionary pointer is NULL after bm_malloc. Cause: Internal error in buffer allocation/deallocation. Failure to create outbound compression dictionary. Dictionary pointer is NULL after bm_malloc. Cause: An inbound compression dictionary has already been allocated
R Y
U EMPTY
R Y
U EMPTY
R Y
U EMPTY
R Y
U EMPTY
October 30, 2008
MDG2-63

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r for a user and a dictionary creation request has arrived EMPTY Cause: An outbound compression dictionary has already been allocated for a user and a dictionary creation request has arrived Cause: An outbound compression dictionary pointer was NULL when a work order arrived to process an outbound datagram. Cause: An inbound compression dictionary pointer was NULL when a work order arrived to process an inbound datagram. Cause: Decompressing an inbound datagram yielded a packet smaller that to be decompressed. R Y
Comments & Notes
exists
.5.1.5.1.0
355
ECP: FNE2MS dictionary already exists
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_DICTIONARY_AL READY_EXISTS
Critical
U EMPTY
356
ECP: FNE2MS compression dictionary NULL
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 FNE2MS_COMPRESSION_ DICTIONARY_NULL
Critical
EMPTY
R Y
U EMPTY
357
ECP: MS2FNE compression dictionary NULL
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_COMPRESSION_ DICTIONARY_NULL
Critical
EMPTY
R Y
U EMPTY
358
ECP: MS2FNE shrank during decompression
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_SHRANK_DURIN G_DECOMPRESSION
Warning
EMPTY
R Y
U EMPTY
359
ECP: MS2FNE decompressed beyond max
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 MS2FNE_DECOMPRESSE D_BEYOND_MAX
Warning
EMPTY
360
LINK_DUP_DLCI_ PORT
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 [Link] - Duplicate DLCI and PORT for ACG <ACG id>
Critical
EMPTY
Cause: Decompressing an inbound datagram yielded a packet that is larger than the maximum allowable size for a datagram. This is fatal for the datagram but not for the MDG. Cause: This is caused when two different links have the same DLCI and PORT combination.
R Y
U EMPTY
R N
U EMPTY
360
LINK_DUP_DLCI_ PORT
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 [Link] - Duplicate DLCI and PORT for DAP <DAP id> Primary/Secondary
Critical
EMPTY
Cause: This is caused when two different links have the same DLCI and PORT combination.
R N
U EMPTY
362
LINK_OUT_OF_R ANGE
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 [Link] - Instance/DLCI/PORT out of range for ACG/DAP <id>
Warning
EMPTY
Cause: This is caused when OMC sends an out of range value for either the Instance, DLCI or PORT.
R N
U EMPTY
362
LINK_OUT_OF_R ANGE
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
Instance out of range for ACG/DAP/iVPU <id>
Warning
EMPTY
Cause: This is caused when OMC sends an out of range value for Instance
R N
N EMPTY
MDG2-64
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
362
LINK_OUT_OF_R ANGE
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Got transaction number <tr_m>, but expected <tr_n>
Warning
364
MGMT_OLC_FAIL
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.20.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4.
mdgNod e
1 Call to mgmt_olc_precommited() failed BM
Major
364
MGMT_OLC_FAIL
mdgNod e
1 Call to mgmt_olc_precommit_failed( ) failed BM
Major
364
MGMT_OLC_FAIL
mdgNod e
1 Call to mgmt_olc_commited() failed BM
Major
364
MGMT_OLC_FAIL
mdgNod e
1 IP Configuration error for MDG_ID <mdg_id> and <mdg_id>
Major
365
MGMT_CONFIGFI LE_READY_FAIL
mdgNod e
1 Call to mgmt_olc_configfile_ready() failed BM
Major
366
MGMT_OLC_ROL LBACK
mdgNod e
1 Received MGMT_OLC_ROLLBACK in caBgdlState SWITCHING
Critical
367
CORE_FILE_FOU ND
mdgUtil
1 Corefile found for board <board>, Serial#: <serial number>
Minor
384
vdrc server rsp timeout
mdgVDR C
1 VCRT: timeout_control_timer. Invalid state when control timer timed out = <state> 1 VCRT:
Major
processingF
384
vdrc server rsp
mdgVDR
Major
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: Got incorrect transaction number R N
Comments & Notes
N EMPTY
EMPTY
Cause: one of the following failed 1. duplicate dlci/port reported by link 2. can't send precommit 3. can't send commit Cause: one of the following failed 1. duplicate dlci/port reported by link 2. can't send precommit 3. can't send commit Cause: one of the following failed 1. duplicate dlci/port reported by link 2. can't send precommit 3. can't send commit Cause: one of the following failed 1. duplicate dlci/port reported by link 2. can't send precommit 3. can't send commit Cause: Sent out a config file ready message to Common Agent but the Common Agent returned a failure
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
Cause: Something wrong with the config file (version number same)
R Y
U EMPTY
EMPTY
Cause: Corefile was found.
R N
U EMPTY
EMPTY
Cause: The server did not respond to a message within the alloted time.
R N
U EMPTY
EMPTY
Cause: The server did not respond to a
R N
U EMPTY
October 30, 2008
MDG2-65

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s M P T Y E M P T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r message within the alloted time.
Comments & Notes
ailureEvent
timeout
1.161.3.3 .5.1.19.5. 0
385
VDRC_RAG_REP_ ABORT
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgVDR C
timeout_rag_mirror_req. Mirror timeout with mobiles in pending-old list. Mobile count = <count> Rag = <rag> 1 Invalid RAG Verification Request for RAG <rag_id>
Warning
EMPTY
Cause: RAG Mirroring Verification Response: Invalid Transaction
R N
U EMPTY
385
VDRC_RAG_REP_ ABORT
mdgVDR C
1 VCRT Backup MDG abort PD VLR Rep. req <message type> rag <rag_id> backup <backup MDG ID> err_code <error code number>
Major
EMPTY
385
VDRC_RAG_REP_ ABORT
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0
mdgVDR C
1 VCRT: process_resync_start_respo nse. Received abort from server on start 1 VCRT: process_rep_response. Received abort from server on rep response 1 Invalid Server Advertisement Request from Backup MDG <backup MDG id>
Major
385
VDRC_RAG_REP_ ABORT
mdgVDR C
Major
386
VDRC_INV_SER_ ADV
mdgVDR C
Major
387
vcrt invalid state
mdgVDR C
1 VCRT: process_bm_start. Invalid state change from <old> to VCRT_START for rag <rag> 1 VCRT: process_resync_start_respo nse. Invalid state change from <old> to VCRT_RESYNC. 1 VCRT: process_resync_done_respo nse. Invalid state change from <old> to VCRT_SYNCHED.
Major
387
vcrt invalid state
mdgVDR C
Major
387
vcrt invalid state
mdgVDR C
Major
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
EMPTY
Cause: The error occurs when PD VLR Replication Response, Resynchronization Start Response, or Resynchronization Complete Response message indicates abort. Any replication procedure for the specified RAG will be stopped. Cause: VCRT is aborting the rag replication.
R N
U EMPTY
R N
U EMPTY
EMPTY
Cause: VCRT is aborting the rag replication.
R N
U EMPTY
EMPTY
Cause: MDG received invalid server advertisement request.
R N
U EMPTY
EMPTY
Cause: VCRT attempted an invalid state change or attempted to perform an operation in a state that should not perform such an operation Cause: VCRT attempted an invalid state change or attempted to perform an operation in a state that should not perform such an operation Cause: VCRT attempted an invalid state change or attempted to perform an operation in a state that should not perform such an operation
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
MDG2-66
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
388
vcrt invalid message
1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.5. 0 1.3.6.1.4. 1.161.3.3 .5.1.4.1.0
mdgVDR C
1 VCRT: process_rep_response. Total Num To ack was less than zero (count) 1 VCRT: process_rep_response. Cant find msrec* for index = <index> 1 VCRT: process_rep_response. Num To ack was less than zero (count) 1 EMPTY
Major
388
mdgVDR C
Major
388
mdgVDR C
Major
411
General_MDG information
mdgBill
Warning
411
1.3.6.1.4. 1.161.3.3 .5.1.5.1.0
mdgECP
1 EMPTY
Warning
411
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgSRP
1 EMPTY
Warning
411
mdgLink
1 EMPTY
Warning
411
1.3.6.1.4. 1.161.3.3 .5.1.13.2. 5.1.0 1.3.6.1.4. 1.161.3.3 .5.1.9.1.0
mdgRFC L
1 EMPTY
Warning
411
mdgMIP
1 EMPTY
Warning
411
1.3.6.1.4. 1.161.3.3
mdgMM
1 EMPTY
Warning
Remedy
R e p o r t &
O u t a g e
EMPTY
Cause: VCRT processed a message that was invalid in some way.
Y C / l N e a r R N
Comments & Notes
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
Cause: The text in this alarm will vary depending on which MDG protocol has sent the alarm.
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
R N
U EMPTY
EMPTY
Cause: The text in this alarm will vary depending on which MDG protocol has
R N
U EMPTY
October 30, 2008
MDG2-67

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r sent the alarm.
Comments & Notes
.5.1.13.2. 1.1.0 processingF ailureEvent 411 General_MDG information 1.3.6.1.4. 1.161.3.3 .5.1.14.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.15.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 3.1.0 1.3.6.1.4. 1.161.3.3 .5.1.18.1. 0 1.3.6.1.4. 1.161.3.3 . 5.1.13.2. 4.1.0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0 mdgRAG 1 EMPTY Warning
EMPTY
R N
U EMPTY
411
mdgNod e
1 EMPTY
Warning
EMPTY
R N
U EMPTY
411
mdgRIP
1 EMPTY
Warning
EMPTY
R N
U EMPTY
411
mdgPPR
1 EMPTY
Warning
EMPTY
R N
U EMPTY
411
mdgLLC
1 EMPTY
Warning
EMPTY
R N
U EMPTY
411
mdgTrap
1 EMPTY
Warning
EMPTY
R N
U EMPTY
411
mdgSRP
1 SFU_T:inbound SRP-ics _send Failure
Warning
EMPTY
M Y
N EMPTY
411
mdgLink
1 ICS send failure
Major
EMPTY
R N
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0
mdgiVPU
1 ICS send failure
Major
EMPTY
R N
N EMPTY
MDG2-68
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
411
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 ICS_receive failed in <file> <line>.
Major
R e l a t e d A l a r m s Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred while reading from a specified ICS queue. "This alarm indicates an error condition internal to MDG. Depends on the protocol, it could lead to MDG resetting, or just an alarm to OMC." Cause: An error occurred allocating a memory buffer. R N
Comments & Notes
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0
mdgiVPU
1 ICS_receive failed in <file> <line>.
Major
EMPTY
R N
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Out of memory . Access failed for ACG/DAP/iVPD <id> /EBTS mode
Major
EMPTY
R N
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Buffer size fails to allocate: <num_bytes> bytes
Major
EMPTY
R N
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgiVPU
1 Buffer size fails to allocate: <num_bytes> bytes
Major
EMPTY
R N
N EMPTY
411
mdgLink
ev_send failed in Sig_Hnd_func: Error <error code>
Major
EMPTY
R N
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0
mdgiVPU
1 ev_send failed in Sig_Hnd_func: Error <error code>
Major
EMPTY
R N
N EMPTY
411
mdgiVPU
1 Socket creation failed for device <dev_type>
Critical
EMPTY
R N
N EMPTY
411
mdgiVPU
1 Socket initialization failed for device <dev_type>
Critical
EMPTY
R N
N EMPTY
October 30, 2008
MDG2-69

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r EMPTY Cause: An error occurred when making a call to a pna system function. R N
Comments & Notes
411
1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgiVPU
1 Socket connect call failed failed for device <dev_type>
Critical
N EMPTY
411
mdgiVPU
1 ioctl call failed <option> for IVPU <dev_id>: Error <error_code>
Critical
EMPTY
R N
N EMPTY
411
mdgiVPU
1 Socket bind failed for <dev_type>: Error <error_code
Critical
EMPTY
R N
N EMPTY
411
mdgiVPU
1 Socket listen failed for <dev_type> server listening socket: Error <error_code
Critical
EMPTY
R N
N EMPTY
411
mdgLink
1 Failed to send packets to socket <socket_num>
Critical
EMPTY
R N
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Socket creation failed for device <dev_type>
Critical
EMPTY
R N
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 ioctl call failed <option> : Error <error_code>
Critical
EMPTY
R N
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 UDP Socket bind failed for <dev_type>: Error <error_code
Critical
EMPTY
R N
N EMPTY
411
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
Critical
EMPTY
R Y
N EMPTY
processingF
411
General_MDG
1.3.6.1.4.
mdgiVPU
1 bm_free fails, ERR_CODE:
Critical
EMPTY
Cause: An error occurred freeing a
R Y
N EMPTY
MDG2-70
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
ailureEvent
information
1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.8.1.0 mdgLink
<Error code>!
411
1 bm_free_stream fails
Critical
411
1.3.6.1.4. 1.161.3.3 .5.1.8.1.0
mdgLink
1 Failed to delete <timer name> <dev_type> <dev_id>
Major
411
1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0 1.3.6.1.4. 1.161.3.3 .5.1.8.2.5 .2.1.1
mdgiVPU
1 Failed to delete <timer name> <dev_type> <dev_id>
Major
411
mdgiVPU
411
mdgMAL
411
1.3.6.1.4. 1.161.3.3 .5.1.8.2.6 .2.1.1 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3
mdgMDL
1 2 5 2 1 3 2 0 0 1 1 5
IVPU <dev_id> link is not configured
Warning
ACG <dev_id> link is not configured
Warning
Remedy
R e p o r t &
O u t a g e
Comments & Notes
EMPTY
R Y
N EMPTY
EMPTY
R N
N EMPTY
EMPTY
R N
N EMPTY
EMPTY
Cause: Link is not configured for particular device
R N
N EMPTY
EMPTY
R N
N EMPTY
DAP <dev_id> link is not configured
Warning
EMPTY
R N
N EMPTY
421
Invalid MS record received
mdgMM
422
Total number of MS records recovered
mdgMM
1 MM: mmAddUserReq: Invalid record in MS download. TEI <tei>. DAP ID is <DAP id>. RAG ID is <RAG id>. IMSI is <imsi> 1 MM: mmRagRecoveryRequest: Total no. of subscribers recovered from mirror = %d 1 PD-Reg-update request recvd when DAP-link is
Warning
EMPTY
Cause: MDG received an invalid MS record from the DAP.
R N
U EMPTY
Warning
EMPTY
Cause: This is generated just to give information about the number of subscribers recovered from PD VLR Mirroring. Cause: MDG failed in processing a received message when DAP link is
R N
U EMPTY
423
Message received when DAP link is
mdgMM
Warning
EMPTY
R N
U EMPTY
October 30, 2008
MDG2-71

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s P T Y E M P T Y E M P T Y E M P T Y E M P T Y Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r down.
Comments & Notes
down
.5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.13.2. 1.1.0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 mdgMM
down!
423
Message received when DAP link is down
1 New PD-reg-request recvd when DAP-link is down!
Warning
EMPTY
Cause: MDG failed in processing a received message when DAP link is down.
R N
U EMPTY
423
Message received when DAP link is down
mdgMM
1 mmAddUserReq called in RAG-download when DAP link is down!
Warning
EMPTY
Cause: MDG failed in processing a received message when DAP link is down.
R N
U EMPTY
432
Link version check procedure failed
mdgMLI NK
432
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0
mdgMLI NK
432
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0
mdgMLI NK
1 MLNK: Link Version Check failed for MDG[<MDGid>]MDG[<MDG id>] link:<client old LVC number> <client new LVC number>, <server Link Version Number> 1 MLNK: Link Version Check failed for MDG[<MDGid>]MDG[<MDG id>] link:<client old LVC number> <client new LVC number> <server old LVC number> <server new LVC number> 1 MLNK: MDG[<MDGid>]: Did not receive LVC response from MDG[<MDG id>]
Major
EMPTY
Cause: The link versions of the two MDGs do not match. Check versions for both MDGs.
R N
U EMPTY
Major
EMPTY
Cause: The link versions of the two MDGs do not match. Check versions for both MDGs.
R N
U EMPTY
Major
432
mdgMLI NK
1 MLNK: MDG[<MDGid>] sent Link Version Down message to MDG[<MDG id>]
Major
E M P T Y E M P T Y
EMPTY
Cause: MDG did not receive LVC response from peer because: 1. peer MDG is down OR 2. LVC request failed Cause: MDG did not receive link version request from peer MDG because: 1. Link Version Down timer value is less than the Link Version Request timer value (OMC configurable timers) OR 2. Peer MDG may be down. Cause: MDG did not receive link version request from peer device because: 1. Link Version Down timer value is less than the Link Version Request timer value (OMC configurable timers) OR 2. Peer device may be down. Cause: Invalid message.
R N
U EMPTY
EMPTY
R N
U EMPTY
432
1.3.6.1.4. 1.161.3.3 .5.1.21.1. 2.1.0
mdgiVPU
MDG[<MDGid>] sent Link Version Down message to <device_type>[<dev_id>]
Major
E M P T Y
EMPTY
R N
N EMPTY
435
MLNK message processing failure
1.3.6.1.4. 1.161.3.3
mdgMLI NK
1 MLNK: Invalid message MDG <mdgid> address <IP
Major
E M
EMPTY
R N
U EMPTY
MDG2-72
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
.5.1.19.4. 0
435
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0
mdgMLI NK
address> row status <row_status> received in process_event() Line <line number> 1 MLNK: mlnk_remove_itc: Message length less than header size. Length = <len>. 1 MLNK: mlnk_remove_itc: Invalid instance in ITC msg. src_instance = <mdgid> dest_instance = <mdgid>. 1 MLNK: mlnk_remove_itc: Length mismatch in ITC msg. itc_length(<len>) != msg_length(<len>) 1 MLNK: mlnk_remove_itc: Unknown destination mailbox id <id> from mdg <mdgid>. 1 MLNK: mlnk_add_framing: unknown buffer type <type> (not stream or linear)
R e l a t e d A l a r m s P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
Major
EMPTY
Cause: Invalid message length.
R N
U EMPTY
435
mdgMLI NK
Major
EMPTY
Cause: Invalid message header.
R N
U EMPTY
435
mdgMLI NK
Major
EMPTY
Cause: Invalid message length in header.
R N
U EMPTY
435
mdgMLI NK
Major
EMPTY
Cause: Unknown mailbox in message header.
R N
U EMPTY
435
mdgMLI NK
Major
EMPTY
Cause: Did not recognize message buffer type.
R N
U EMPTY
435
mdgMLI NK
1 MLNK: mlnk_add_framing: msg_top is NULL. Could not convert to mblk.
Major
EMPTY
Cause:Error converting message from one type to another.
R N
U EMPTY
435
mdgMLI NK
MLNK: Invalid <timer name> timer received. Using default.
Major
EMPTY
Cause: An invalid timer value was received.
R N
U EMPTY
435
mdgMLI NK
435
1.3.6.1.4. 1.161.3.3
mdgMLI NK
1 MLNK: mlnk_process_framing: Received invalid framing header msg from mdg <mdgid>. Reserved = <reserved>. 1 MLNK: mlnk_process_framing:
Major
EMPTY
Cause: Received an invalid message.
R N
U EMPTY
Major
EMPTY
Cause: Invalid message length in header.
R N
U EMPTY
October 30, 2008
MDG2-73

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y E M P Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
.5.1.19.4. 0 processingF ailureEvent 435 MLNK message processing failure 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 mdgMLI NK
Suffix not found at end of msg. Msg from mdg <mdg>. Length = <len> 1 MLNK: mlnk_process_framing: Could not sync with mdg <mdg>. 1 MLNK: Invalid node id <mdgid> received in process_event() Line <Line number> 1 MLNK: Duplicate data MDG <mdgid> address <IP address> MDG<mdgid> address <IP address> received. Rejecting MDG <mdgid> 1 MLNK: Invalid message length <length> received in File <file name> Line <line number> 1 MLNK: Did not receive valid config data MDG <mdgid> address <address> num_mdg_nodes <# of mdg nodes> 1 MLNK:Timer configuration data not received. Using default
Major
EMPTY
Cause: Could not receive valid message from an MDG.
R N
U EMPTY
435
mdgMLI NK
Critical
EMPTY
Cause: An invalid MDG-id was received.
R Y
U EMPTY
435
mdgMLI NK
Major
EMPTY
Cause: Duplicate data was received.
R N
U EMPTY
435
1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.19.4. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1.
mdgMLI NK
Major
EMPTY
Cause: Invalid message length.
R N
U EMPTY
435
mdgMLI NK
Critical
EMPTY
Cause: Did not receive valid configuration data.
R Y
U EMPTY
435
mdgMLI NK
Major
EMPTY
Cause:Did not receive valid timer values from configuration data.
R N
U EMPTY
435
mdgMLI NK
1 MLNK:Received connection request from unconfigured MDG with address <address> 1 LDSHD: CPU Threshold exceeded, CPU = <percentage>
Major
EMPTY
Cause: The MDG sending the connection request is not configured.
R N
U EMPTY
436
MDG CPU loadshedding threshold reached
mdgNod e
Major
EMPTY
Cause: CPU has exceeded loadshedding threshold.
R N C
U EMPTY
437
MDG Memory loadshedding threshold reached
mdgNod e
1 LDSHD: Memory Threshold exceeded, 128-byte: <percentage>, 256-byte:
Major
EMPTY
Cause: Memory has exceeded loadshedding threshold.
R N C
U EMPTY
MDG2-74
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
448
Billing Record storage status
1.3.6.1.4. 1.161.3.3 .5.1.4.2.1 8.0
mdgBillG en
<percentage>, 512-byte: <percentage>, 1024-byte: <percentage>, 2048-byte: <percentage>, 4096-byte: <percentage> 1 BillGen: Max BB-Msg-list number <max number> reached. Dropping billing records.
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
Major
E M P T Y
EMPTY
448
Billing Record storage status
1.3.6.1.4. 1.161.3.3 .5.1.4.2.1 8.0
mdgBillG en
1 BillGen: Resuming to store billing records.
Clear
E M P T Y
EMPTY
201
MDG iVPU triggered loadshedding: Critical MDG iVPU triggered loadshedding: Medium MDG iVPU triggered loadshedding: Low
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0 1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0
mdgNod e
1 iVPU <dev_id> loadshedding level set to 1
Critical
202
mdgNod e
Major
203
mdgNod e
Warning
100001
mdgNod e
1 Time Difference between NMS and NE exceeds maximum difference for synchronization
Major
EMPTY
Cause: When MDG is not able to send billing records to BAs due to TCP connections to supported BAs going down, it continues to store all records in its local buffer until it reaches its maximum limit of storage. When this limit is reached it starts to drop any new record that arrives and sends this alarm to OMC. Remedy: TCP connections to BAs need to be established. There could be various reasons for why the links are down: ethernet cable may be disconnected or BAs may be down. Cause: This alarm clears the above alarm. When this alarm is sent, MDG resumes to store the records again in its local buffer and send them to the BAs periodically .i.e., the TCP links have been established and billing records are not lost anymore. Contact the iDEN Customer Situation Center for assistance.
R N C
U EMPTY
C N
U EMPTY
R N
N EMPTY
EMPTY
R N
N EMPTY
EMPTY
R N
N EMPTY
EMPTY
R N
N The time difference between the NMS and the NE was larger than the
October 30, 2008
MDG2-75

Alarm Type
Alarm Code
Release SR17.0
Severity R e l a t e d A l a r m s Related State Changes
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
maximum value for automatic synchronizatio n to be completed.
MDG2-76
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 1
LOWER LAYER ESTABLISHED LOWER LAYER ESTABLISHED
1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1 1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1
mdgMAL mdgMAL
1-3200 1-3200
L-D-Idl U-D-Idl
L-E-Idl U-E-Idl
EMPTY EMPTY
EMPTY EMPTY
EMPTY EMPTY
S t a t u s N U N U
LOWER LAYER ESTABLISHED
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
L-D-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1
mdgMAL
1-3200
L-E-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1
mdgMAL
1-3200
U-E-Idl
U-DIdl
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1
mdgMAL
1-3200
U-E-A
U-DIdl
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
L-E-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
N U
The physical port has been enabled. The physical port has been enabled. The MDG will attempt to establish the LAPD connection. A physical port has been enabled. If primary and secondary utilize different ports, enabling either port will invoke this state change. A physical port has been enabled. If primary and secondary utilize different ports, enabling either port will invoke this state change. The MDG will attempt to establish the LAPD connection(s). The physical port has become disabled. All communication ceases with ACG until port becomes operational. The physical port has become disabled. All communication ceases with ACG until port becomes operational. The physical port has become disabled. All communication ceases with ACG until port becomes operational. Physical port has become disabled. If primary and secondary utilize different ports, failure of both ports will result in this state change. All communication ceases with DAP until either port becomes
October 30, 2008
MDG2-77

State Changes
R e a s o n C o d e
Release SR17.0
From State To State Related State Changes Related Alarms Event Description O u t a g e ( Y / N ) C h a n g e S t a t u s operational. Physical port has become disabled. If primary and secondary utilize different ports, failure of both ports will result in this state change. All communication ceases with DAP until either port becomes operational. Physical port has become disabled. If primary and secondary utilize different ports, failure of both ports will result in this state change. All communication ceases with DAP until either port becomes operational. Physical port has become disabled. If primary and secondary utilize different ports, failure of both ports will result in this state change. All communication ceases with DAP until either port becomes operational. The MDG-ACG link has been unlocked by the OMC. The MDG will attempt to establish the LAPD connection. The MDG-ACG link has been unlocked by the OMC The MDG-DAP link has been unlocked by the OMC.The MDG will attempt to establish the LAPD connection. The MDG-DAP link has been unlocked by the OMC. The MDG-ACG link has been locked by the OMC. The MDG-ACG link has been locked by the OMC. The LAPD connection will be released. The MDG-ACG link has been locked by the OMC. The MDG-DAP link has been locked by the OMC. The MDG-DAP link has been
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Comments & Notes
LOWER LAYER FAILURE
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-E-Idl
U-DIdl
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-E-A
U-DIdl
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-E-Imp
U-DIdl
EMPTY
EMPTY
EMPTY
N U
LINK UNLOCKED
1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1
mdgMAL
1-3200
L-E-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
3 3
LINK UNLOCKED LINK UNLOCKED
1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1 1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMAL mdgMDL
1-3200 1-15
L-D-Idl L-E-Idl
U-DIdl U-E-Idl
EMPTY EMPTY
EMPTY EMPTY
EMPTY EMPTY
N U N U
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
3 4 4
LINK UNLOCKED LINK LOCKED LINK LOCKED
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1 1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1 1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1 1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1 1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1 1.3.6.1.4.1.161.3
mdgMDL mdgMAL mdgMAL
1-15 1-3200 1-3200
L-D-Idl U-E-Idl U-E-A
U-DIdl L-E-Idl L-E-Idl
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
N U N U N U
4 4 4
LINK LOCKED LINK LOCKED LINK LOCKED
mdgMAL mdgMDL mdgMDL
1-3200 1-15 1-15
U-D-Idl U-E-Idl U-E-A
L-D-Idl L-E-Idl L-E-Idl
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
N U N U N U
MDG2-78
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Label) Inst From State To State Related State Changes Related Alarms Event Description O u t a g e ( Y / N ) .3.5.1.8.2.6.2.1.1 C h a n g e S t a t u s locked by the OMC. All LAPD connections will be released. The MDG-DAP link has been locked by the OMC. The MDG-DAP link has been locked by the OMC. All LAPD connections will be released. The previously active MDGACG LAPD link has been terminated by the peer (ACG) or other external cause. A restart will be attempted. A previously active MDG-DAP LAPD link has been terminated by the peer (DAP) or other external cause. A restart will be attempted. A previously active MDG-DAP LAPD link has been terminated by the peer (DAP) or other external cause. A restart will be attempted. A previously active MDG-DAP LAPD link has been terminated by the peer (DAP) or other external cause. A restart will be attempted. The previously active MDGACG LAPD link has been suspended due to reception of a version check request from the ACG containing an incompatible version. Resumption of service will take place only after successful version check is received. The MDG has received a version check request from the ACG containing a compatible version. A version check response is returned to the ACG and the link is now fully operational. Using either the primary or secondary link, the MDG has received a version check response from the DAP
Comments & Notes
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent 4 4 LINK LOCKED LINK LOCKED
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1 1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1 1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1
mdgMDL mdgMDL
1-15 1-15
U-D-Idl U-E-Imp
L-D-Idl L-E-Idl
EMPTY EMPTY
EMPTY EMPTY
EMPTY EMPTY
N U N U
LAPD CONNECTION RELEASED
mdgMAL
1-3200
U-E-A
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-E-A
U-EImp
EMPTY
EMPTY
EMPTY
N U
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-E-Imp
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-E-A
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
VERSION CHECK FAILURE
1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1
mdgMAL
1-3200
U-E-A
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
VERSION CHECK SUCCESSFUL
1.3.6.1.4.1.161.3 .3.5.1.8.2.5.2.1.1
mdgMAL
1-3200
U-E-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-E-Idl
U-EImp
EMPTY
EMPTY
EMPTY
N U
October 30, 2008
MDG2-79

State Changes
R e a s o n C o d e
Release SR17.0
From State To State Related State Changes Related Alarms Event Description O u t a g e ( Y / N ) C h a n g e S t a t u s indicating a compatible version Using either the primary or secondary link, the MDG has received a version check response from the DAP indicating a compatible version The second of the dual LAPD links has been established between the MDG and DAP. A second version check is unnecessary. The communication link is now fully operational. The RAG instance has been locked by the OMC. The RAG instance has been locked by the OMC. The RAG instance has been unlocked by the OMC. The RAG instance goes inactive as a result of a locked node. The RAG instance goes active as a result of a fully completed download. Node Object locked by OMC.
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Comments & Notes
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-E-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
LAPD CONNECTION ESTABLISHED
1.3.6.1.4.1.161.3 .3.5.1.8.2.6.2.1.1
mdgMDL
1-15
U-E-Imp
U-E-A
EMPTY
EMPTY
EMPTY
N U
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
1 0 0 1 0 0 1 0 1 1 0 2 1 0 3 1 5 0 1 5 0 1 5 1 1 5 2 1 5 3 1 5 4
RAG LOCKED
1.3.6.1.4.1.161.3 .3.5.1.14.1.0 1.3.6.1.4.1.161.3 .3.5.1.14.1.0 1.3.6.1.4.1.161.3 .3.5.1.14.1.0 1.3.6.1.4.1.161.3 .3.5.1.14.1.0 1.3.6.1.4.1.161.3 .3.5.1.14.1.0 1.3.6.1.4.1.161.3 .3.5.1.10.1.0 1.3.6.1.4.1.161.3 .3.5.1.10.1.0 1.3.6.1.4.1.161.3 .3.5.1.10.1.0 1.3.6.1.4.1.161.3 .3.5.1.10.1.0 1.3.6.1.4.1.161.3 .3.5.1.10.1.0 1.3.6.1.4.1.161.3 .3.5.1.10.1.0
mdgRAG
0-31
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
RAG LOCKED
mdgRAG
0-31
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
RAG UNLOCKED
mdgRAG
0-31
L-E-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
NODE LOCKED
mdgRAG
0-31
U-E-A
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
RAG ACTIVATION
mdgRAG
0-31
U-E-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
NODE LOCKED
mdgNode
EMPTY
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
NODE LOCKED
mdgNode
EMPTY
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
Node Object locked by OMC.
NODE UNLOCKED
mdgNode
EMPTY
L-E-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
Node Object unlocked by OMC.
NODE ACTIVE
mdgNode
EMPTY
U-E-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
Node Object goes into Active state. Node failure.
SYNC FAIL
mdgNode
EMPTY
L-E-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
N U
NODE SYNCHED
mdgNode
EMPTY
L-D-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
Node synched to the OMC.
MDG2-80
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Label) Inst From State To State Related State Changes Related Alarms Event Description O u t a g e ( Y / N ) C h a n g e
Comments & Notes
1 5 5 2 0 0 2 0 0
NODE IDLE
1.3.6.1.4.1.161.3 .3.5.1.10.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0
mdgNode
EMPTY
U-E-A
U-E-Idl
EMPTY
EMPTY
EMPTY
S t a t u s N U
Node is enabled.
LOWER LAYER ESTABLISHED LOWER LAYER ESTABLISHED
mdgBill
EMPTY
L-D-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
The MDG-IR Link is UP. This means that RIP is stable. The MDG-IR Link is UP.This means that RIP is stable. MDG will now attempt to establish connections with the supported BAs. The MDG-IR link is down. Could be because of RIP failure. The MDG-IR link is down. Could be because of RIP failure. The MDG-IR link is down. Could be because of RIP failure.Connections to supported BAs go down. The MDG-IR link is down. Could be because of RIP failure. The only active connection to a BA goes down. The MDG-BA link is unlocked by the OMC.MDG will now attempt to connect to the supported BAs. The MDG-BA link is unlocked by the OMC.MDG now waits for the lower layer to be established. The MDG-BA link is locked by the OMC The MDG-BA link is locked by the OMC.The connections to the supported BAs go down. The MDG-BA link is locked by the OMC The MDG-BA link is locked by the OMC TCP connection with one BA is established. (Two BAs are supported)
mdgBill
EMPTY
U-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
2 0 1 2 0 1 2 0 1 2 0 1 2 0 2 2 0 2 2 0 3 2 0 3 2 0 3 2 0 3 2 0 4
LOWER LAYER FAILURE
1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0
mdgBill
EMPTY
L-E-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
mdgBill
EMPTY
U-E-Idl
U-DIdl U-DIdl
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
mdgBill
EMPTY
U-E-A
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
1.3.6.1.4.1.161.3 .3.5.1.4.1.0
mdgBill
EMPTY
U-E-Imp
U-DIdl
EMPTY
EMPTY
EMPTY
N U
LINK UNLOCKED
1.3.6.1.4.1.161.3 .3.5.1.4.1.0
mdgBill
EMPTY
L-E-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
LINK UNLOCKED
1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0
mdgBill
EMPTY
L-D-Idl
U-DIdl L-E-Idl
EMPTY
EMPTY
EMPTY
N U
LINK LOCKED
mdgBill
EMPTY
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
LINK LOCKED
mdgBill
EMPTY
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
LINK LOCKED
mdgBill
EMPTY
U-D-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
N U
LINK LOCKED
mdgBill
EMPTY
U-E-Imp
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
TCP CONNECTION WITH ONE BA ESTABLISHED
mdgBill
EMPTY
U-E-Idl
U-EImp
EMPTY
EMPTY
EMPTY
N U
October 30, 2008
MDG2-81

State Changes
R e a s o n C o d e
Release SR17.0
From State To State Related State Changes Related Alarms Event Description O u t a g e ( Y / N ) C h a n g e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Comments & Notes
2 0 5 2 0 6 2 0 6 2 0 7 3 0 0 3 0 0 3 0 1
TCP CONNECTION WITH BOTH BAs ESTABLISHED TCP CONNECTION FAILURE WITH ONE BA TCP CONNECTION FAILURE WITH ONE BA TCP CONNECTION FAILURE WITH BOTH Bas LINK UNLOCKED
1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.4.1.0 1.3.6.1.4.1.161.3 .3.5.1.15.1.0 1.3.6.1.4.1.161.3 .3.5.1.15.1.0 1.3.6.1.4.1.161.3 .3.5.1.15.1.0
mdgBill
EMPTY
U-E-Imp
U-E-A
EMPTY
EMPTY
EMPTY
S t a t u s N U
mdgBill
EMPTY
U-E-A
U-EImp U-E-Idl
EMPTY
EMPTY
EMPTY
N U
mdgBill
EMPTY
U-E-A
EMPTY
EMPTY
EMPTY
N U
mdgBill
EMPTY
U-E-Imp
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
mdgRIP
EMPTY
L-E-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
TCP connection with one BA is established. (Two BAs are supported) TCP connection with one of the BAs is lost. (Two BAs are supported) TCP connection with the only BA is lost. (Only one BA is supported) TCP connection with second BA is also lost. (Two BAs are supported) OMC unlocks MDG-IR link for service. MDG is trying to establish contact with a default router. MDG fails to establish contact with a default router within the appropriate time frame. Note: The MDG will continue to route packets to its last known default router (if there was one) until the OMC takes the MDG node out of service. MDG lost communication with its current default router. Note: The MDG will continue to route packets to its last known default router until the OMC takes the MDG node out of service. Transitory state to U-E-A (needed for X.731 convention compliance). MDG (re)gained contact with a default router. MDG-IR link is (re)established. MDG (re)gained contact with a default router. MDG-IR link is (re)established. Transitory state to L-E-Id (needed for X.731 convention compliance). MDG could not find a default router and OMC takes this non functional MDG-IR link out
LINK UNLOCKED
mdgRIP
EMPTY
U-E-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
LOWER LAYER FAILURE
mdgRIP
EMPTY
U-E-Idl
U-DIdl
EMPTY
EMPTY
EMPTY
N U
3 0 2
IR CONNECTION RELEASED
1.3.6.1.4.1.161.3 .3.5.1.15.1.0
mdgRIP
EMPTY
U-E-A
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
3 0 3 3 0 4 3 0 4 3 0 5 3 0 6
LOWER LAYER ESTABLISHED IR CONNECTION ESTAB
1.3.6.1.4.1.161.3 .3.5.1.15.1.0 1.3.6.1.4.1.161.3 .3.5.1.15.1.0 1.3.6.1.4.1.161.3 .3.5.1.15.1.0 1.3.6.1.4.1.161.3 .3.5.1.15.1.0 1.3.6.1.4.1.161.3 .3.5.1.15.1.0
mdgRIP
EMPTY
U-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
mdgRIP
EMPTY
U-E-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
IR CONNECTION ESTAB
mdgRIP
EMPTY
U-D-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
LINK LOCKED
mdgRIP
EMPTY
U-D-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
N U
mdgRIP
EMPTY
L-D-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
MDG2-82
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Label) Inst From State To State Related State Changes Related Alarms Event Description O u t a g e ( Y / N ) C h a n g e
Comments & Notes
3 0 7 3 0 8 4 0 0 4 0 1 5 0 1 5 0 2
LINK LOCKED
1.3.6.1.4.1.161.3 .3.5.1.15.1.0
mdgRIP
EMPTY
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
S t a t u s N U
LINK LOCKED
1.3.6.1.4.1.161.3 .3.5.1.15.1.0 1.3.6.1.4.1.161.3 .3.5.1.19.4.0 1.3.6.1.4.1.161.3 .3.5.1.19.4.0 1.3.6.1.4.1.161.3 .3.5.1.21.1.2.1.0 1.3.6.1.4.1.161.3 .3.5.1.21.1.2.1.0
mdgRIP
EMPTY
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
OMC takes a functional MDG-IR link out of service when MDG is performing default router discovery procedure. OMC takes a functional MDG-IR link out of service. TCP connection with MDG has been established. TCP connection with MDG is down. EMPTY
MLNK TCP CONNECTION ESTABLISHED MLNK TCP CONNECTION DOWN iVPU LINK ENABLED
mdgMLINK
EMPTY
U-D-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
mdgMLINK
EMPTY
U-E-A
U-DIdl U-E-A
EMPTY
EMPTY
EMPTY
N U
mdgiVPU
1-252
U-D-Idl
EMPTY
EMPTY
EMPTY
N N
iVPU LOWER LAYER FAILURE
mdgiVPU
1-252
U-E-A
U-DIdl
EMPTY
EMPTY
EMPTY
N N
EMPTY
October 30, 2008
MDG2-83
Release SR17.0
__________________________________ Events
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
downloadStart edEvent downloadCom pletedEvent reStartEvent
<load> <release>.<version>.<subver sion>.<patchlevel> <load> <release>.<version>.<subver sion>.<patchlevel> New Operate State: <New Operate State> New Usage State: <New Usage State> New Admin State: <New Admin State> System ROM Version: <System ROM Version> System Load Version: <System Software Load Version> System DB Version: <System Database Version> System Code Version: <System Code Version> Description: <System Description> System Reset Reason: <System Reset Reason> System Outage Time: <System outage Time> System Reboot Time: <System Reboot Time> System Boot Diagnostics: <System Boot Diagnostics> Abort Reason = <abort reason code> - File Type = <file type> - File Name = <dest file name> Background Download completed successfully
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
This event is used to inform the OMC, a download request has been sent. This event is used to inform the OMC the download has completed. This event is used to inform the OMC whenever MDG switches its application code load or when it reboots. It also tells the OMC that SNMP agent is operational and is ready to handle request. NOTE: The following are the error codes presented in the reStart trap displayed on the OMC for <MDG Reset Reason> as of SR9.5 : UNKNOWN --> 1, OPERATOR --> 2, POWER --> 3, HARDWARE --> 4, SOFTWARE --> 5, UNDEFINED --> Any other value, including 0. 'UNDEFINED' This reason code is possible if the MDG return a value other than the ones listed above. This happens if new hardware is initially installed. Since the RAM image reads the memory of NVRAM, it is possible that it can be other than values listed above. MCG doesn't program this memory region for us. Once the download has completed, the default value of '3' --> power is stored to memory. EMPTY
S t a t u s U EMPTY
U EMPTY
1.3.6.1.4. 1.161.3.3 .5.1.10.1. 0
mdgNod e
EMPTY
EMPTY
EMPTY
EMPTY
U EMPTY
filexferAborted Event
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
U EMPTY
actionStatusE vent
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated if OLCC background download has
U EMPTY
MDG2-84
October 30, 2008
Release SR17.0

Related State Changes Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
actionStatusE vent actionStatusE vent
Background Download aborted successfully Background Download Switch completed successfully
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
availabilityEve nt
<universal time>-<sequence number>-<secondary id><new mode>-<time of switch>-<reason code>-<old mode>-<reason text><additional text>
1.3.6.1.4. 1.161.3.3 .5.1.3.1.9 .0
MDG2
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
completed successfully or has failed. In case of failure, Action Status Info details reason for failure. Event is generated if OLCC background download has been aborted. Event is generated when OLCC switch has completed successfully or has failed. In case of failure, Action Status info details reason for failure (reason and line number in configuration file). Event is generated when the MDG2 mode changes from in service to out of service and from out of service to inservice
U EMPTY
U EMPTY
N Universal time the time (in GMT) when the trap was generated. Sequence number integer incremented for each new Availability trap; the valid range is 24 bits (0..16777215) and it wraps back to 1 when incremented past 24 bits. The value of 0 is only used to restart the sequence when no previous information is available. Secondary id This is not used in MDG2. MDG2 will use 0. New mode Applicable state values for MDG2:
October 30, 2008
MDG2-85

Release SR17.0
Event Description
O u t a g e ( Y / N ) C h a n g e S t a t u s Maintenance (1) Standby (2) Active (3) Time of switch Time (in GMT format) when the MDG2 entered this mode. Reason code Applicable reason codes for MDG2: Platform Hardware Fault (1) Application Software Fault (5) Operator Initiated Platform (9) Operator Initiated Application (10) Indeterminate (11) Old mode Applicable state values for MDG2: Unknown (0) Maintenance (1) Standby (2) Active (3) Reason text MDG2 only provides reason text when the reason code is equal to Operator Initiated Application (10)
Comments & Notes
MDG2-86
October 30, 2008
Release SR17.0

Related State Changes Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
and operator supplied reason text is available. The operator is required to enter a reason text via LMT when requesting a change in mode from Active to Maintenance and Standby to Maintenance. Active to Standby is not a valid state transition for MDG2. Additional text In most cases MDG does not provide additional text. In the case of platform hardware fault, the identification of the faulty component will be provided.
October 30, 2008
MDG2-87
Release SR17.0
MDG2-88
October 30, 2008
Release SR17.0
_________________________ Alarms
Alarm Type
Alarm Code
MDG4
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
100000
100101
Bad Value returned in the Configuration File Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Empty
Major
Empty
Empty
MDG4_AP P
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100101
Message Timed Out
MDG4_AP P
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CM: Failed to receive MCMAnswer message from MDG <mdg_id>. CM: Failed to receive MCMCoordinate message. CM: Failed to receive MCMGrantAckn owledge message from MDG <mdg_id>. CM: Failed to receive MCMHealthIndic ationAcknowledg e message from MDG <mdg_id>. CM: Failed to receive MCMRecoverAc knowledge message from MDG <mdg_id>. CM: Failed to receive MCMReleaseRe questAcknowled
Major
Empty
Empty
Contact the iDEN Customer Network Resolution Center for assistance. No action necessary.
Y C / l N e a r R N
Comments & Notes
U Bad Value returned in the Configuration File
R N
U MDG-MDG connection will be brought down and reestablished.
Major
Empty
Empty
R N
U Cluster Coordinator Election procedure will be restarted.
Major
Empty
Empty
R N
Major
Empty
Empty
R N
Major
Empty
Empty
R N
U The participant is taking longer than the timeout of 25 seconds to recover.
Major
Empty
Empty
R N
October 30, 2008
MDG4-1

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ge message from MDG <mdg_id>. CM: Failed to receive MCMReport message from MDG <mdg_id>. MIPR : AlarmTimeout : Timeouts on PendRegNewRe q from HA <#> times in last <#> minutes
Comments & Notes
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Warni ng
Empty
Empty
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : AlarmTimeout : Timeouts on PendRegNewRe q from VLRM <#> times in last <#> minutes
Warni ng
Empty
Empty
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2
MDG4_AP P
SRPC: Channel Grant Received: ACG <acg_id> SECTOR <sector_idx+1> RAG <rag_id> WIDEN_FLAG off SRPC: Channel Grant Received: ACG <acg_id> SECTOR <sector_idx+1> RAG <rag_id> WIDEN_FLAG on SRPC: Channel Grant Sanity
Clear
Empty
Empty
MDG does not receive MIP registration response from home agent within predefined time frame. No action is necessary if this is intermittent; otherwise check the network connection with home agent. MDG does not receive MIP update response from VLRM on V_card within predefined time frame. No action is necessary if this is intermittent; otherwise contact the iDEN Customer Network Resolution Center for assistance. No action necessary.
R N
U Failed to received MIP registration reply from HA
R N
U Failed to received MIP registration reply from VLRM process on V board
C N
U When the MDG received an SRP Channel Grant (WiDEN on) from the ACG that has expired previously, the alarm is cleared.
Clear
Empty
Empty
C N
U When the MDG received an SRP Channel Grant (WiDEN off) from the ACG that has expired previously, the alarm is cleared.
Major
Empty
Empty
R N
U The MDG did not receive an SRP Channel Grant (WiDEN
MDG4-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r vent .1.0 Timer expired: ACG <acg_id> SECTOR <sector_idx+1> RAG <rag_idx> WIDEN_FLAG off SRPC: Channel Grant Sanity Timer expired: ACG <acg_id> SECTOR <sector_idx+1> RAG <rag_idx> WIDEN_FLAG on VLRM: MIP CHANGE: HandleTimeOut_ MipUpdateResp onse: Retry exceeded <MAX> for Index <INDEX>, Tei <TEI> Bill: Cannot send Billing Block <curr_seq_num> to BA. Discarding after <MAX_ATTEMP TS> attempts Bill: All configuration information not recvd
Comments & Notes
on) from the ACG. The MDG will retransmit the SRP Channel Request to the ACG.
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
U The MDG did not receive an SRP Channel Grant (WiDEN off) from the ACG. The MDG will retransmit the SRP Channel Request to the ACG.
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Warni ng
Empty
Empty
R N
U MDG has not received a MIP update response from DAP
100101
Message Timed Out
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
Check health of BA.
R N
U MDG is unable to send Billing records to the BA
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
1) Check Configuration file for missing row status , IP address, port number and/or password information for atleast one BA. 2) Verify that the above configuration information is provided for the number of Billing accumulators specified in the file. 3) Else verify that the BA ids specified in the configuration file are 1 based (ids are 1
R N
U MDG did not receive configuration information for all BAs that are configured in the network. The TCP connections to the BA(s) can therefore not be established.
October 30, 2008
MDG4-3

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r and 2, if two BAs are configured) and not 0 based. Verify that the IP addresses of both BAs in the configuration file are not the same. The board will reset and the backup V board will become active. No action necessary. Verify that the BA port number is configured correctly in the Configuration file.
Comments & Notes
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Bill: Duplicate IP address recvd for BAs: <ip_addr> Bill: Invalid Board State msg recvd Bill: Invalid port number recvd: <port>. Setting to default: 5566
Critical
Empty
Empty
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100102
Invalid Value
MDG4_AP P
Minor
Empty
Empty
R N
processingF ailureEvent processingF ailureEvent
100102
Invalid Value
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P MDG4_AP P
Bill: Invalid uanc recvd in OLCC: <uanc> Bill: Invalid uanc recvd: <uanc>
Minor
Empty
Empty
Critical
Empty
Empty
100102
Invalid Value
MDG4_AP P
Bill: Invalid value recvd for billNumBA: <billNumBA> Bill: IP address zero recvd for BA[]
Critical
Empty
Empty
Verify that the UANC value sent to the MDG during OLCC is in range Verify that the UANC value in the configuration file is in the correct range. Verify that the number of BAs specified in the Configuration file is 1 or 2 Verify that the IP address information for the BA is configured correctly in the Configuration file.
R N
R N
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
processingF
100102
Invalid Value
1.3.6.1.4.1.161.3
MDG4_AP
CM: Answer message received from MDG <instance> is invalid. CM: Link Down
Major
Empty
Empty
MDG-MDG connection will be brought down and reestablished.
R N
U MDG has received the same IP address for both Bas in the network. The TCP connections to the BAs can therefore not be established. U Bill process has not received a valid board state from the Node Manager. Possible Software failure U MDG did not receive a valid port number for the BA and therefore cannot establish TCP connection with the BA. If the port number is configured correctly, look for alarms/information referring to problems during configuration download. U The user entered an invalid UANC value while doing OLCC. U MDG records UANC in Billing records. The UANC value received is out of range. U Number of BAs specified in Configuration file is out of range.MDG cannot establish TCP connections with the BAs U The process received an IP address value zero for a BA configured in the network. If the address is configured correctly, look for alarms/information referring to problems during configuration download. U Answer message received from peer MDG when the local MDG did not send Elect message. U Link down message received
Minor
Empty
Empty
This alarm indicates that
R N
MDG4-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent .3.10.5.27.1.11.2 .1.0 P from MDG ID <instance> is invalid. a Link Down message was received by the Cluster Management protocol from MLNK which is a lower layer protocol when the link was already marked as down by the Cluster Management protocol. No action necessary. No action necessary.
Comments & Notes
from an MDG when the link is already down.
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100102
Invalid Value
MDG4_AP P
100102
Invalid Value
MDG4_AP P
CM: Link Up from MDG ID <instance> is invalid. CM: MDG ID <instance> does not match the Coordinator ID. CM: MDG ID <instance> is invalid. CM: RAG Group ID <instance> is invalid. CM: Timestamp for RAG <instance> is stale. app_name:MLN K: Invalid MDG id in ITC msg from MDG<mdg_id>. Src id = <source_id> Dest id = <destination_id> my id = <my_id>. Closing TCP connection. app_name:MLN K: Invalid local mdgid received: <mdg_id>
Minor
Empty
Empty
R N
U Link up message received from an MDG when the link is already up. U Coordinate message received from an MDG whose ID is less than the local MDG ID. U MDG ID configuration is invalid. The MDG ID is less than 0 or greater than 36. U RAG group configuration received from participant does not match that of the coordinator U RAG has been claimed by another MDG with a newer timestamp. U MDG is configured with incorrect id/IP address information of the peer MDG. The TCP connection is therefore being closed.
Major
Empty
Empty
MDG-MDG connection will be brought down and reestablished. Contact the iDEN Customer Network Resolution Center for assistance. MDG-MDG connection will be brought down and reestablished. MDG with stale timestamp will release the RAG Verify that the MDGs are configured with the correct id and IP address information for peer MDGs.
R N
Major
Empty
Empty
R N
100102
Invalid Value
MDG4_AP P
Minor
Empty
Empty
R N
100102
Invalid Value
MDG4_AP P
Major
Empty
Empty
R N
100102
Invalid Value
MDG4_AP P
Major
Empty
Empty
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
Verify that the MDG's id is configured correctly in the Configuration file.
R N
U The process did not receive a valid id for the MDG. If the MDG id is configured correctly, look for alarms/information referring
October 30, 2008
MDG4-5

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
iLNK:Invalid local mdgid received: <My_id>
Critical
Empty
Empty
Verify that the MDG's id is configured correctly in the Configuration file.
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
app_name:MLN K: MDG[<mdg_id>]: Did not recv a valid local IP address app_name:MLN K: MDG[<mdg_id>]: Duplicate IP address: MDG[] IP_address <ip_addr> MDG[<j>] IP address <ip_addr> app_name:MLN K: MDG[<mdg_id>]: Invalid Row status <status> recvd for MDG[] iLNK: Invalid Row status <status> recvd for iVPU[]
Critical
Empty
Empty
Verify that the MDG's IP address is configured correctly in the Configuration file.
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
Verify that the iDEN IP addresses of the two MDGs are not the same in the Configuration file
R N
to problems during configuration download. U The process did not receive a valid id for the MDG. If the MDG id is configured correctly, look for alarms/information referring to problems during configuration download. U The process did not receive a valid IP address for the local MDG. If the IP address is configured correctly, look for alarms/information referring to problems during configuration download. U MDG cannot establish TCP connections to the two remote MDGs since their IP addresses are configured to be the same.
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
Verify that the row status information for the MDG is configured correctly in the Configuration file.
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
Verify that the row status information for the MDG is configured correctly in the Configuration file.
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
app_name:MLN K: MDG[<mdg_id>]: Received IP
Critical
Empty
Empty
Verify that the IP address information for the MDG is configured correctly in the
R N
U The process did not receive a valid row status for an MDG configured in the network. If the row status is configured correctly, look for alarms/information referring to problems during configuration download. U The process did not receive a valid row status for an iVPU configured in the network. If the row status is configured correctly, look for alarms/information referring to problems during configuration download. U The process did not receive a valid IP address for an MDG configured in the network. If the address is
MDG4-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r address zero for MDG[] Configuration file.
Comments & Notes
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: SLM invalid acg_id <acg_id> or rag_idx <rag_idx> or sec_idx <sector_idx>.
Major
Empty
Empty
1) This alarm indicates corruption for a single subscriber. 2) While packet_data for this single subscriber may be affected, no other subscriber should be affected.
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: SLM invalid pch_type <pch_type>.
Major
Empty
Empty
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: slm_ragcell_addr _req: ACG_Control_T able is NULL for acg_id <acg_id>.
Major
Empty
Empty
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: srp_ragcell_addr _req: ACG_Control_T able is NULL for acg_id <acg_id>.
Major
Empty
Empty
1) This alarm indicates corruption for a single subscriber. 2) While packet_data for this single subscriber may be affected, no other subscriber should be affected. 1) This alarm indicates corruption for a single subscriber. 2) While packet_data for this single subscriber may be affected, no other subscriber should be affected.
R N
configured correctly, look for alarms/information referring to problems during configuration download. U 1) To correctly process channel_request and data_request (both to ACG), and channel_grant (from ACG), the d-board queries the subscriber's database. 2) Invalid values indicate subscriber database is corrupted. 3) PPR task in dboard will be unable to process these messages properly. U 1) To correctly process channel_request and data_request (both to ACG), and channel_grant (from ACG), the d-board queries the subscriber's database. 2) Invalid channel type (iDEN or WiDEN is valid) indicate subscriber database is corrupted. 3) PPR task in dboard will be unable to process these messages properly. U Possible corruption of acg_id as this id comes from higher protocols and it is less likely that invalid acg_id is being passed all along
R N
U 1) To correctly process channel_request and data_request (both to ACG), and channel_grant (from ACG), the d-board queries the subscriber's database. 2) Invalid values indicate subscriber database is corrupted. 3) PPR task in dboard will be unable to
October 30, 2008
MDG4-7

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: SRPC invalid acg_id <acg_id> or rag_idx <rag_idx> or sec_idx <sector_idx>.
Major
Empty
Empty
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: SRPC invalid pch_type <pch_type>.
Major
Empty
Empty
R N
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : RegRequestRcv d : Error code <code> mn {0.0.0.0}
Warni ng
Empty
Empty
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPI: Invalid ACG-ID <acg_id>.
Warni ng
Empty
Empty
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRS: ILLEGAL RAG operation client <mdg_id> rag <rag_id>
Major
Empty
Empty
The MIPR process on the D-Board received an invalid MIP Registration from the MS and will send back a reject message back to the MS. No action necessary. The SFUT process on the C-Board received SFUs from Frame Relay that contain an invalid ACG_ID that is zero. The SFUs are discarded. No action necessary. A remote MDG has sent a message that is invalid. The connection to that MDG will be closed and the RAGs
R N
process these messages properly. U 1) To correctly process channel_request and data_request (both to ACG), and channel_grant (from ACG), the d-board queries the subscriber's database. 2) Invalid values indicate subscriber database is corrupted. 3) PPR task in dboard will be unable to process these messages properly. U 1) To correctly process channel_request and data_request (both to ACG), and channel_grant (from ACG), the d-board queries the subscriber's database. 2) Invalid values indicate subscriber database is corrupted. 3) PPR task in dboard will be unable to process these messages properly. U Incorrect Mobile IP registration request received
R N
U SRP received an invalid ACG ID of 0.
R N
U Remote MDG failure. The MDG will recover from this failure re-establishing the connection with the client.
MDG4-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r will be re-negotiated to recover from this situation. A remote MDG has sent a message that is invalid. The connection to that MDG will be closed and the RAGs will be re-negotiated to recover from this situation. A remote MDG has not responded to the server advertisement response. This is indicates that the remote MDG has failed. To recover from this situation we will close the connection to the remote MDG and wait for it to reconnect. Verify that the MDGs are configured with the correct id and IP address information for peer MDGs.
Comments & Notes
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRS: ILLEGAL RAG. client <mdg_id> rag <rag_id>
Major
Empty
Empty
R N
U Remote MDG failure. The MDG will recover from this failure re-establishing the connection with the client.
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRS: No server advertisement response. client <CLIENT>
Major
Empty
Empty
R N
U This error occurs normally during an MDG reset (the MDG will fail to respond to the backup). Otherwise the MDG will close the connection to recover. No user intervention is necessary.
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100102
Invalid Value
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CMNM:MLNK: Invalid MDG id in ITC msg from MDG<mdg_id>. Src id = <source_id> Dest id = <destination_id> my id = <my_id>. Closing TCP connection. VDRR:MLNK: Invalid MDG id in ITC msg from MDG<mdg_id>. Src id = <source_id> Dest id = <destination_id> my id = <my_id>. Closing TCP connection. iLNK: Received LVC req msg from unconfigured
Major
Empty
Empty
R N
U MDG is configured with incorrect id/IP address information of the peer MDG. The TCP connection is therefore being closed.
Major
Empty
Empty
Verify that the MDGs are configured with the correct id and IP address information for peer MDGs.
R N
U MDG is configured with incorrect id/IP address information of the peer MDG. The TCP connection is therefore being closed.
Major
Empty
Empty
Verify that the MDGs are configured with the correct id information for iVPUs.
R N
U The iVPU id in the LVC request message sent by an iVPU to the MDG is not configured in the MDG. The
October 30, 2008
MDG4-9

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r iVPU with id <ID> CM: Unexpected Grant Acknowledge message received from MDG <instance>. CM: Unexpected Grant message received from MDG <instance>. CM: Unexpected Health Indication Acknowledge message received from MDG <instance>.
Comments & Notes
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Minor
Empty
Empty
MDG-MDG connection will be brought down and reestablished.
R N
TCP connection is therefore closed. U Grant Acknowledge message received from participant MDG when the local MDG did not send Grant message.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Minor
Empty
Empty
R N
U Participant was assigned a RAG group when it is shutting down.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Minor
Empty
Empty
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CM: Unexpected Report message received from MDG <instance>. MIPR : MIPD_ind : MIP_Driver invalid msg
Minor
Empty
Empty
This alarm indicates that the participant received more than one Health Indication Acknowledgement message from the Coordinator. Before the participant could process the first message it got the next message right away. No action necessary. MDG-MDG connection will be brought down and reestablished.
R N
U Participant received Health Indication Acknowledgement in an invalid state.
R N
U Report message received from participant MDG when the local MDG did not send Coordinate message. U MIPR received invalid message from MIP_Driver on PPRT
Major
Empty
Empty
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : VLRM Update Response : Invalid response
Warni ng
Empty
Empty
MIPR process received invalid formatted message from PPRT on the same D-Card. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. MIPR process received invalid message from VRLM of V_Card. No action is necessary if this is intermittent, otherwise contact the
R N
R N
U MIPR received invalid message from VLRM on V board
MDG4-10
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r iDEN Customer Network Resolution Center for assistance. During RAG Verification, the MDG detected that the DAP timestamps for the RAGs are newer than the MDG. The MDG will reject the RAG Verification. No action necessary. During a RAG Download session, an internal event in the RAGT process was generated for an invalid DAP_ID of 0 or greater than 15. This is 1-based value from 1 to 15 for valid DAP_ID. The event will be ignored. No action necessary. During a RAG Download session, an internal event in the RAGT process was generated for an invalid RAG_ID greater than 31. This is 0-based value from 0 to 31 for valid RAG_ID. The event will be ignored. No action necessary. During a RAG Download procedure, an internal event in the RAGT process was generated for an invalid DAP_ID of 0 or greater than 15. This is 1-based value from 1 to 15 for valid DAP_ID. The event will be ignored. No action necessary. During a RAG Download procedure, an internal event in the RAGT
Comments & Notes
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: DAP has a Greater Timestap than MDG for RAG 
Minor
Empty
Empty
R N
U DAP has a greater Timestamp than the MDG.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: DDSM SM Event for Invalid DAP ID <dap_id>
Minor
Empty
Empty
R N
U DDSM State Machine received an event for an Invalid DAP ID.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: DDSM SM Event for Invalid RAG ID <rag_id>
Minor
Empty
Empty
R N
U DDSM State Machine received an event for an Invalid RAG ID.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: DDSP SM Event for Invalid DAP ID <dap_id>
Minor
Empty
Empty
R N
U DDSP State Machine received an event for an Invalid DAP ID.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: DDSP SM Event for Invalid RAG ID
Minor
Empty
Empty
R N
U DDSP State Machine received an event for an Invalid RAG ID.
October 30, 2008
MDG4-11

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r <rag_id> process was generated for an invalid RAG_ID greater than 31. This is 0-based value from 0 to 31 for valid RAG_ID. The event will be ignored. No action necessary. During a RAG Download session, an unexpected internal event was generated in the RAGT process. The event will be handled gracefully by the RAGT process. No action necessary. During a RAG Download procedure, an unexpected internal event was generated in the RAGT process. The event will be handled gracefully by the RAGT process. No action necessary. During a RAG Verification, an unexpected internal event was generated in the RAGT process. The event will be handled gracefully by the RAGT process. No action necessary. During a RAG Download procedure, the MDG received a RAG_Download_Compl ete_Request message from the DAP with an invalid 'Status' value. The DAP message will be discarded. No action necessary. During a RAG Download procedure, the MDG received an invalid
Comments & Notes
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Invalid DDSM SM Event for DAP <dap_id> RAG <rag_id>
Minor
Empty
Empty
R N
U Invalid DDSM State Machine Event.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Invalid DDSP SM Event for DAP <dap_id> RAG <rag_id>
Minor
Empty
Empty
R N
U Invalid DDSP State MAchine Event.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Invalid RV SM Event for DAP ID <device_id>
Minor
Empty
Empty
R N
U Invalid RAG Verification State Machine Event.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Invalid Status in RAG Download Complete Request for DAP <dap_id> RAG <rag_id>
Minor
Empty
Empty
R N
U Invalid Status Field in RAG Download Complete Request Message sent from the DAP.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Message Type <msg_type> Not
Minor
Empty
Empty
R N
U Unrecognized Message to the DDSP Module from the DAP.
MDG4-12
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Recognized by DDSP SM [DAP <dap_id>] processingF ailureEvent 100103 Invalid Message 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 RAG: PD Reg State Received for RAG <rag_id> Not Assigned, state <state> Minor Empty Empty message from the DAP. The DAP message will be discarded. No action necessary. RAGT process received a PD_Reg_State indication primitive from VLRM on the V-Board for a RAG that is not "assigned". The primitive will be discarded by RAGT. No action necessary. During a RAG Update procedure, the MDG received a RAG_Update_Response message from an invalid ACG_ID of 0 or greater than 3204. This is 1based value from 1 to 3204 for valid ACG_ID. The message will be ignored. No action necessary. During a RAG Update procedure, the MDG received a RAG_Update_Response message from an invalid DAP_ID of 0 or greater than 15. This is 1-based value from 1 to 15 for valid DAP_ID. The message will be ignored. No action necessary. During a RAG Update procedure, the MDG received a RAG_Update_Response message from the ACG with the wrong sequence number. The message will be discarded. No action necessary. During a RAG Update
Comments & Notes
R N
U RAG Object State Machine received an Invalid PD Reg State from VLRM.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: RAG Update Response for Invalid ACG ID <device_id>
Minor
Empty
Empty
R N
U RAG Update Response from an Invalid ACG ID.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: RAG Update Response for Invalid DAP ID <device_id>
Minor
Empty
Empty
R N
U RAG Update Response from an Invalid DAP ID.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: RAG Update Response Sequence Number Mismatch for ACG <device_id>
Minor
Empty
Empty
R N
U RAG Update Response with mismatched Sequence Number from the ACG.
processingF
100103
Invalid Message
1.3.6.1.4.1.161.3
MDG4_AP
RAG: RAG
Major
Empty
Empty
R N
U RAG Update Response with
October 30, 2008
MDG4-13

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent .3.10.5.27.1.11.2 .1.0 P Update Response Sequence Number Mismatch for DAP <device_id> procedure, the MDG received a RAG_Update_Response message from the DAP with the wrong sequence number. The message will be discarded. No action necessary. During a RAG Verification procedure, the MDG received a RAG_Verification_Resp onse message from an invalid DAP_ID of 0 or greater than 15. This is 1-based value from 1 to 15 for valid DAP_ID. The message will be ignored. No action necessary. During a RAG Verification procedure, the MDG received a RAG_Verification_Resp onse message from the DAP with the wrong sequence number. The message will be discarded. No action necessary. During a RAG Download procedure, the MDG received a RAG_Download_Abort_ Request message from the DAP with an invalid 'failure' value. The MDG will discard the message and stop the RAG Download procedure. No action necessary. During a RAG Update procedure, an internal event in the RAGT process was generated for an invalid ACG_ID of
Comments & Notes
mismatched Sequence Number from the DAP.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: RAG Verification Response for Invalid DAP ID <dap_id>
Minor
Empty
Empty
R N
U RAG Update Response from an Invalid DAP ID.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: RAG Verification Response Sequence Number Mismatch for DAP <dap_id>
Minor
Empty
Empty
R N
U RAG Verification Response with mismatched Sequence Number from the DAP.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: RAG_DOWNLO AD_ABORT_RS P failed - Invalid Response for DAP <dap_id>, RAG <rag_id>
Minor
Empty
Empty
R N
U Invalid Response from the DAP for a RAG_DOWNLOAD_ABORT _REQUEST from the MDG.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: RU SM Event for Invalid ACG ID <device_id>
Minor
Empty
Empty
R N
U RAG Update State Machine received an Event from an Invalid ACG ID.
MDG4-14
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r 0 or greater than 3204. This is 1-based value from 1 to 3204 for valid ACG_ID. The event will be ignored. No action necessary. During a RAG Update procedure, an internal event in the RAGT process was generated for an invalid DAP_ID of 0 or greater than 15. This is 1-based value from 1 to 15 for valid DAP_ID. The event will be ignored. No action necessary. At least one RAG has an invalid subgroup in the config file. Modify the config file or contact iDEN support
Comments & Notes
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: RU SM Event for Invalid DAP ID <device_id>
Minor
Empty
Empty
R N
U RAG Update State Machine received an Event from an Invalid DAP ID.
100103
Invalid Message
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: RAG ASSIGN: Invalid board ID <dboard_id> during RAG assignment Bill: BA link(s) up but have zero availability factor Bill: BA links are up but both have zero availability Bill: Bill-NM connection failed
Critical
Empty
Empty
R N
communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent
100104
Communication Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
Check health of BA(s).
R N
100104
MDG4_AP P
Major
Empty
Empty
Check health of both BAs.
R N
100104
MDG4_AP P
Critical
Empty
Empty
100104
MDG4_AP P
Bill: MDGBA[<NEid>] TCP connection not established
Major
Empty
Empty
The board will reset and the backup V board will become active. No action necessary. This could be caused by various factors. Some remedy methods are listed below. 1)Check network connectivity between the MDG and BA. 2)Check health of BA(s) 3)Verify that MDG received correct configuration information (IP address, port
R N
R N
U Invalid config file information. Modify the configuration file to contain valid RAG subgroup IDs. The MDG will be reset to handle this error. A new config file should be downloaded. U The TCP connection(s) to both or the only BA(s) is(are) up but BA(s) is(are) reporting zero availability U The TCP connections to both BAs are up but both BAs are reporting zero availability. U Bill process is not able to communicate with CMNM process. CMNM process probably died. U The TCP connection is not establiched with the Billing Accumulator.
October 30, 2008
MDG4-15

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r number etc) of the BA and that it is configured correctly in the BA. 3)Using mmi command "mdisplay billstats" find the "Last connection close reason", if available, and take remedy actions accordingly. For example if the "Last connection close reason is REG_FAIL, verify that password information is correct and is the same on MDG and BA. OR Contact the iDEN Customer Network Resolution Center for assistance. Check health of BA
Comments & Notes
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Bill: Registration failed for MDGBA[<NEid>] TCP connection
Major
Empty
Empty
R N
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Bill: Registration failed for MDGBA[<NEid>] TCP connection. Reg resp is <type>
Major
Empty
Empty
communicat
100104
Communication
1.3.6.1.4.1.161.3
MDG4_AP
app_name:MLN
Major
Empty
Empty
If Reg resp type is 0x02: Verify that the BA password in the MDG configuration file is same as the password listed in the BA. 0x03: MDG is not registered with BA. Add MDG id entry in BA. 0xF000: General NACK by BA.Check health of BA. 0x01: Protocol version sent by MDG is not supported by BA. Possible Software failure. Contact the iDEN Customer Situation Center for assistance. This could be caused by
R N
U MDG could not register successfully with the BA since the BA did not send a valid Registration Response message (bad message size). U MDG could not register successfully with the BA
R N
U The TCP connection to the
MDG4-16
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ionFailureE vent Failure .3.10.5.27.1.11.2 .1.0 P K: MDG<NEid> TCP connection failed to establish various factors. Some remedy methods are listed below. 1)Check network connectivity between the two MDGs. 2) Check health of remote MDG. 3)Verify that both MDGs received correct configuration information (IP address, port number etc) of the other MDG and self. 4) Look for alarms related to VLR mirroring or cluster management procedure. OR Contact the iDEN Customer Situation Center for assistance Check health of iVPU. Verify network connectivity between MDG and iVPU.
Comments & Notes
MDG failed to be established.
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
iLNK:Closing MDGiVPU[<NEid>] TCP connection, LC Request timed out. MIPR : MIPD_ind : MIP_Driver connection closed MIPR : RegReplySend : send fail mn = <ip_addr>
Major
Empty
Empty
R N
Major
Empty
Empty
Major
Empty
Empty
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : RegRequestRcv d : HA connection closed MIPR : RegRequestRcv d : HA send fail
Major
Empty
Empty
Connection between MIPR and PPRT lost. No action necessary since MIPR will try to reconnect automatically. MIPR process failed to forward MIP registration reply to PPRT. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. MIPR process failed to forward MIP registration request to home agent.
R N
U MDG failed to receive a periodic hearbeat message from iVPU. The TCP connection is brought down and will be reestablished by the iVPU. U MIPR lost connection to MIP_Driver on PPRT
R N
U MIPR failed to send Mobile IP registration reply to MIP_Driver on PPRT
R N
U MIPR connection to HA failed.
Major
Empty
Empty
R N
U MIPR failed to send Mobile IP registration request to home agent
October 30, 2008
MDG4-17

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r errno <error number> No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. VCRT could not register an MLNK callback function. This indicates that MLNK has failed. To recover from this situation the VDRR process is terminated and the V board is failed over. The standby V board will then recover. VDRC could not register an MLNK callback function. This indicates that MLNK has failed. To recover from this situation the VDRR process is terminated and the V board is failed over. The standby V board will then recover. VDRC could not register an MLNK callback function. This indicates that MLNK has failed. To recover from this situation the VDRR process is terminated and the V board is failed over. The standby V board will then recover. VDRC received an invalid server advertisement from the backup MDG. This indicates that the request came with an invalid server timestamp. The link will be closed to the remote MDG and CMNM will reassign a correct role to
Comments & Notes
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VCRT: Couldn't register MLNK data callback
Critical
Empty
Empty
R N
U The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged.
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRC: Couldn't register MLNK control callback
Critical
Empty
Empty
R N
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRC: Couldn't register MLNK link status callback
Critical
Empty
Empty
R N
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRC: Invalid server advertisement from backup MDG <mdg_id>
Major
Empty
Empty
R N
U Remote MDG failure. The MDG will recover from this failure re-establishing the connection with the client. No user intervention is required.
MDG4-18
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r the MDG to recover. The link will then be restored. VDRR Failed to open a connection to CMNM because the port was already in use. The V board will failover and the standby V board will recover. VDRR Failed to open a connection to RAG because the port was already in use. The V board will failover and the standby V board will recover. VDRR Failed to open a connection to VDRR because the port was already in use. The V board will failover and the standby V board will recover. VDRS could not register an MLNK callback function. This indicates that MLNK has failed. To recover from this situation the VDRR process is terminated and the V board is failed over. The standby V board will then recover. VDRS could not register an MLNK callback function. This indicates that MLNK has failed. To recover from this situation the VDRR process is terminated and the V board is failed over. The standby V board will then recover. VDRS could not register an MLNK callback function. This indicates
Comments & Notes
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRR: Can not open CMNM connection on port <port>
Critical
Empty
Empty
R N
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRR: Can not open RAG connection on port <port>
Critical
Empty
Empty
R N
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRR: Can not open VDRR connection on port <port>
Critical
Empty
Empty
R N
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRS: Couldn't register MLNK control callback
Critical
Empty
Empty
R N
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRS: Couldn't register MLNK data callback
Critical
Empty
Empty
R N
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRS: Couldn't register MLNK link status
Critical
Empty
Empty
R N
U The board has reached a critical software failure. The board will be reset and
October 30, 2008
MDG4-19

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r that MLNK has failed. To recover from this situation the VDRR process is terminated and the V board is failed over. The standby V board will then recover. VDRS received a server advertisement failure response from VDRC. This indicates that the client is not expecting this server to be the backup. The connection will be closed and CMNM will reassign a new role to the MDG. No action necessary.
Comments & Notes
failover mechanisms will be engaged.
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRS: SERVER ADV FAILED client <mdg_id> event <event>
Major
Empty
Empty
R N
U Remote MDG failure. The MDG will recover from this failure re-establishing the connection with the client. No user intervention is required.
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100104
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CM: Failed to receive MCMElect message from all lower id cluster participants. CM: Failure to bring up link with any higher id cluster participant. RAGT: LAPD Sublink is down for greater than <x> msec.
Major
Empty
Empty
R N
U The CMNM process on the V-Board did not receive the MCMElect message from all the Cluster Participants.
Major
Empty
Empty
R N
Critical
Empty
Empty
R N
100105
Link Version Check Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
iLNK:Link Version Check Request failed for MDG[<mdg_id>] -iVPU[<NEid>] link:Version Supported: <version> Req_OLD: <LV_number>, Req_NEW: <LV_number>
Major
Empty
Empty
Verify that software versions of MDG and iVPU are compatible.
R N
U The CMNM process on the V-Board could not establish a TCP connection with the Cluster Participant. The CMNM process will retry. U The RAGT process on the VBoard communication link to the LAPD process on the CBoard is down beyond the accepted time. The V-Board will be reset. N Link Version Check protocol between MDG and iVPU failed.
MDG4-20
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
100105
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100105
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100105
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100105
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
app_name:MLN K:Link Version Check Request failed for MDG[<mdg_id>] -MDG[<NEid>] link:OLD: <version> NEW: <version> Req_OLD: <LV_number>,R eq_NEW: <LV_number> app_name:MLN K:Link Version Check Response failed for MDG[<mdg_id>] -MDG[<NEid>] link:OLD:<versio n> New:<version>, Response:<LV_ num> app_name:MLN K:MDG[<mdg_id >]: LVC Response received from MDG[<NEid>] app_name:MLN K: MDG[<mdg_id>]: LVC Response not received from MDG[<NEid>] [CreateDictionar y] Inbound memory allocation failure, index=<vlr_index > [CreateDictionar y] Outbound memory allocation failure,
Major
Empty
Empty
Check software versions of both MDGs.
Y C / l N e a r R N
Comments & Notes
U Link Version Check protocol between the two MDGs failed.
Major
Empty
Empty
Check software versions of both MDGs.
R N
U Link Version Check protocol between the two MDGs failed.
Clear
Empty
Empty
C N
U This alarm clears the above alarm.
Major
Empty
Empty
Check health of peer MDG and network connectivity.
R N
U MDG did not receive Link Version Response from peer MDG.
Minor
Empty
Empty
Minor
Empty
Empty
MDG failed to create data compression dictionary for the subscriber, resulting in data compression service failure. MDG failed to create data compression dictionary for the subscriber, resulting in
R N
U Failure to allocate memory for EDCL Dictionary. If error occurs Data Compression will not function.
R N
U Failure to allocate memory for EDCL Dictionary. If error occurs Data Compression will not function.
October 30, 2008
MDG4-21

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r index=<vlr_index > [DeleteDictionary ] Inbound memory allocation failure, index=<vlr_index > [DeleteDictionary ] Outbound memory allocation failure, index=<vlr_index > app_name: Can not get IP address of MA using hostname <hostname> MIP_DB : cannot create MIP_DB file, exit MIP_DB::MIP_D B : ftruncate() returns errno = <errno>, exit MIPD_IBdataFw d : write to Sock #<sock_num> fail data compression service failure. MDG failed to deallocate data compression dictionary for the subscriber, resulting in data compression service failure. MDG failed to deallocate data compression dictionary for the subscriber, resulting in data compression service failure. The board will reset and the backup V board will become active. No action necessary. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Failed to write inbound data to socket. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. Failed to write inbound data to TUN device. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for
Comments & Notes
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
U Failure to de-allocate memory for EDCL Dictionary. If error occurs Data Compression will not function. U Failure to de-allocate memory for EDCL Dictionary. If error occurs Data Compression will not function. U Bill process could not get IP address of Master agent. IP Configuration error.
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
U MIPR failed to create DB object
100106
System Call Failure
MDG4_AP P
Critical
Empty
Empty
R N
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
U The database to hold Mobile IP information could not be created/updated on the DBoard. The D-Board will be reset. U An error writing inbound data to the PDIP network.
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPD_IBdataFw d : write to TUN #<tun_num> fail
Major
Empty
Empty
R N
U TUN writing failure.
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : mip_init : conn_ha init fail
Major
Empty
Empty
R N
U MIPR failed to init home agent connection object
MDG4-22
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100106 System Call Failure 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 MIPR : mip_init : conn_mipd init fail MIPR : mip_init : conn_vlrm init fail MIPR : mip_init : MIPD_Connectio n init fail MIPR : mip_init : mipr_visitor init fail MIPR : mip_init : VLRM_Connecti on init fail RAG: Can not get IP address of MA using hostname <hostname> Major Empty Empty assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. When the V-board comes up from reset, the RAGT process on the V-Board was not able to get the IP address of the Master Agent on the "active" VBoard. No action necessary. The MDG does not have the address for the active V board. The V board will fail over to the standby V board to recover from this situation. VDRS is unable to create shared memory. No memory is available on the board. The V board will failover to the standby V board to recover. No action necessary. R N
Comments & Notes
U MIPR failed to init MIP_Driver connection object U MIPR failed to init VLRM connection object
100106
System Call Failure
MDG4_AP P
Major
Empty
Empty
R N
100106
System Call Failure
MDG4_AP P
Major
Empty
Empty
R N
U MIPR failed to create connection object
100106
System Call Failure
MDG4_AP P
Major
Empty
Empty
R N
U MIPR failed to create visitor object
100106
System Call Failure
MDG4_AP P
Major
Empty
Empty
R N
U MIPR failed to create connection object
100106
System Call Failure
MDG4_AP P
Critical
Empty
Empty
R N
U The RAG Module cannot get the IP Address of the MA using Hostname.
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRR: Can not get IP address of MA using hostname <hostname>
Critical
Empty
Empty
R N
U Board Failure. The board can not perform its normal operation. It will be reset to recover.
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRS: Can not create shared memory
Critical
Empty
Empty
R N
U Critical board failure. The board will be reset to recover. No user intervention is required.
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLR_: Can not create shared memory
Critical
Empty
Empty
R N
U The database to hold subscriber information could not be created/updated on
October 30, 2008
MDG4-23

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r database processingF ailureEvent 100106 System Call Failure 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 VLRM: Can not allocate memory during recovery rag file <filename> Major Empty Empty VLRM can not allocate memory to recover the RAG from the cache. The subscribers on the RAG will not be recovered and RAG download will be started to recover them from the DAP. VLRM can not allocate memory to recover the RAG from the cache. The subscribers on the RAG will not be recovered and RAG download will be started to recover them from the DAP. The MDG does not have the address for the active V board. The V board will fail over to the standby V board to recover from this situation. The MDG does not have the address for the active V board. The V board will fail over to the standby V board to recover from this situation. VLRM can not locate the RAG ID that is requested. VLRM will note the error and require RAG download to start for all RAGs to recover from the error. No action necessary. R N
Comments & Notes
the V-Board. The V-Board will be reset. U Board Failure. The board can not perform its normal operation. It will be reset to recover.
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Can not create shared memory during recovery rag file <filename>
Major
Empty
Empty
R N
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Can not get IP address of Active V Board using hostname <hostname>
Critical
Empty
Empty
R N
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Can not get IP address of MA using hostname <hostname>
Critical
Empty
Empty
R N
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Invalid RAG ID during recovery of rag <rag_id>
Major
Empty
Empty
R N
U Software failure. The software will handle this error internally without failover.
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
processingF
100106
System Call
1.3.6.1.4.1.161.3
MDG4_AP
MIPD_Visitor::MI PD_Visitor : Can not create shared memory database MIPR_Visitor::MI
Critical
Empty
Empty
R N
Critical
Empty
Empty
R N
U The database to hold Mobile IP information could not be created/updated on the DBoard. The D-Board will be reset. U The database to hold Mobile
MDG4-24
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent Failure .3.10.5.27.1.11.2 .1.0 P PR_Visitor : Can not create shared memory database MIPD_Visitor::MI PD_Visitor : cannot open MIP_DB file, exit MIPD_Visitor::MI PD_Visitor : cannot obtain MIP_DB file information, exit MIPR_Visitor::MI PR_Visitor : cannot open MIP_DB file, exit MIPR_Visitor::MI PR_Visitor : cannot obtain MIP_DB file information, exit bill main: mgmt_init_env() failed bill main: mgmt_poll() failed bill main: mgmt_select_fd( ) failed bill main: mgmt_wait_initia lize() failed bill main: open() failed for Master Agent Connection bill_main: Registering SMI_GROUP_m dg4BillBasicObje cts failed.
Comments & Notes
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100106
System Call Failure
MDG4_AP P
Critical
Empty
Empty
R N
IP information could not be created/updated on the DBoard. The D-Board will be reset. U The database to hold Mobile IP information could not be opened on the D-Board. The D-Board will be reset. U The database to hold Mobile IP information could not be accessed on the D-Board. The D-Board will be reset. U The database to hold Mobile IP information could not be opened on the D-Board. The D-Board will be reset. U The database to hold Mobile IP information could not be accessed on the D-Board. The D-Board will be reset. U Common Agent API failure
100106
System Call Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100106
System Call Failure
MDG4_AP P
Critical
Empty
Empty
R N
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
100108
CA API Failure
MDG4_AP P
Warni ng
Empty
Empty
100108
CA API Failure
MDG4_AP P
Critical
Empty
Empty
100108
CA API Failure
MDG4_AP P
Warni ng
Empty
Empty
100108
CA API Failure
MDG4_AP P
Critical
Empty
Empty
100108
CA API Failure
MDG4_AP P
Warni ng
Empty
Empty
The board will reset and the backup V board will become active. No action necessary. The process will reattempt the function call. No action necessary. The board will reset and the backup V board will become active. No action necessary. The process will reattempt the function call. No action necessary. The board will reset and the backup V board will become active. No action necessary. The process will reattempt registration. No action necessary.
R N
R N
U Common Agent API failure
R N
R N
R N
R N
October 30, 2008
MDG4-25

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
MDG4_AP P
100108
CA API Failure
MDG4_AP P
100108
CA API Failure
MDG4_AP P
100108
CA API Failure
MDG4_AP P
bill_main: Registering SMI_GROUP_m dg4BillLinkEntry failed. bill_main: Registering SMI_GROUP_m dg4NodeId failed. Could not register stat_id <stat_id> in PPR. Could not register stat_id <stat_id> in SFU. Could not register stat_id <stat_id> in MMI_MON. iLNK:MDG[<My_ id>] Failed to register stat <stat name> mdg4AppObject s registration failed.
Warni ng
Empty
Empty
The process will reattempt registration. No action necessary.
Y C / l N e a r R N
Comments & Notes
Warni ng
Empty
Empty
The process will reattempt registration. No action necessary.
R N
Major
Empty
Empty
Major
Empty
Empty
Major
Empty
Empty
Critical
Empty
Empty
Warni ng
Empty
Empty
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
mdg4RagBasicO bjects registration failed.
Warni ng
Empty
Empty
Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. During the V-Board initialization, the RAGT process will attempt to connect to the Master Agent (also on the same V-Board) and register for 'mdg4AppObjects' MIBs information. If the registration failed, then the connection to the Master Agent could not be established. The RAGT process would use default value for its MIBs. No action is needed. During the V-Board initialization, the RAGT process will attempt to connect to the Master Agent (also on the same
R N
U pm_register failed for a PPR stat
R N
U pm_register failed for a SFU stat
R N
U pm_register failed for a MMI stat
R N
U The process failed to register for a stat.Common Agent API failure. U This alarm would apply during V-Board initialization.
R N
R N
U This alarm would apply during V-Board initialization.
MDG4-26
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r V-Board) and register for 'mdg4RagBasicObjects' MIBs information. If the registration failed, then the connection to the Master Agent could not be established. The RAGT process would use default value for its MIBs. No action is needed. During the V-Board initialization, the RAGT process will attempt to connect to the Master Agent (also on the same V-Board) and register for 'mdg4RagDownloadObj ects' MIBs information. If the registration failed, then the connection to the Master Agent could not be established. The RAGT process would use default value for its MIBs. No action is needed. If the RAGT process on the V-Board could not connect to the Master Agent (also on the same V-Board), then a critical alarm would cause the current V-Board to reset and the Hot-Standby VBoard to become active. No action is needed. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN
Comments & Notes
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
mdg4RagDownl oadObjects registration failed.
Warni ng
Empty
Empty
R N
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
mgmt_select_fd( ) failed.
Critical
Empty
Empty
R N
U This alarm would apply during active V-Board operation.
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
MDG4_AP P
processingF
100108
CA API Failure
1.3.6.1.4.1.161.3
MDG4_AP
MIPD_Visitor::MI PD_Visitor : cannot open MIP_DB file, exit MIPD_Visitor::MI PD_Visitor : cannot obtain MIP_DB file information, exit MIPR_Visitor::MI
Critical
Empty
Empty
R N
U MIPD failed to open DB object
Critical
Empty
Empty
R N
U MIPD failed to open DB object information
Critical
Empty
Empty
R N
U MIPR failed to open DB
October 30, 2008
MDG4-27

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent .3.10.5.27.1.11.2 .1.0 100108 CA API Failure 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 P PR_Visitor : cannot open MIP_DB file, exit MIPR_Visitor::MI PR_Visitor : cannot obtain MIP_DB file information, exit MIPR: mipr_hca_conne ctToMasterAgent : mgmt_poll() failed. Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. The D-Board will retry to connect to the V-Board. Execute the Packet Data Health Check Script. If the alarm persists, report this issue to the Motorola CNRC and NTS. The D-Board will retry to connect to the V-Board. Execute the Packet Data Health Check Script. If the alarm persists, report this issue to the Motorola CNRC and NTS. The D-Board will retry to connect to the V-Board. Execute the Packet Data Health Check Script. If the alarm persists, report this issue to the Motorola CNRC and NTS. The D-Board will retry to connect to the V-Board. Execute the Packet Data Health Check Script. If the alarm persists, report this issue to the Motorola CNRC and NTS. The D-Board will retry to connect to the V-Board. Execute the Packet Data Health Check Script. If the alarm persists, report this issue to the Motorola CNRC and
Comments & Notes
object
MDG4_AP P
Critical
Empty
Empty
R N
U MIPR failed to open DB object information
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Warni ng
Empty
Empty
R N
U D-Board connectivity to VBoard is temporarily lost.
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR: mipr_hca_conne ctToMasterAgent : mgmt_select_fd( ) failed.
Critical
Empty
Empty
R N
U D-Board connectivity to VBoard is temporarily lost. When the D-Board comes up from reset, it will attempt to connect to the Master Agent on the V-Board to get its MIB configurations. U D-Board connectivity to VBoard is temporarily lost.
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR: mipr_hca_conne ctToMasterAgent : mgmt_wait_initia lize() failed, code <code>. MIPR: mipr_hca_conne ctToMasterAgent : Registering SMI_GROUP_m dg4MobileIpSyst em failed. MIPR: mipr_hca_MA_e vt__ipc_rx_data: mgmt_poll() failed.
Warni ng
Empty
Empty
R N
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Warni ng
Empty
Empty
R N
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Warni ng
Empty
Empty
R N
MDG4-28
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100108 CA API Failure 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 MIPR: ppr_hca_connec tToMasterAgent: mgmt_init_env() failed, MA_addr <MA_addr>. Warni ng Empty Empty NTS. The D-Board will retry to connect to the V-Board. Execute the Packet Data Health Check Script. If the alarm persists, report this issue to the Motorola CNRC and NTS. Contact the iDEN Customer Network Resolution Center for assistance. When the D-Board comes up from reset, it will attempt to connected to the Master Agent on the V-Board to get its MIB configurations. If the connection failed, it will back-off and reattempt after a few seconds. No action required. No action required. The D-Board will retry to connect to the V-Board. R N
Comments & Notes
U D-Board connectivity to VBoard is temporarily lost. When the D-Board comes up from reset, it will attempt to connect to the Master Agent on the V-Board to get its MIB configurations. U pm_register failed for mdg4_load_shedding_durati on_stat
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PLS: Could not register MDG4_LOAD_S HEDDING_DUR ATION PM stat! PLS: pls_hca_connect ToMasterAgent: mgmt_init_env() failed,
Critical
Empty
Empty
R N
Warni ng
Empty
Empty
R N
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PLS: pls_hca_connect ToMasterAgent: mgmt_poll() failed. PLS: pls_hca_connect ToMasterAgent: mgmt_select_fd( ) failed.
Warni ng
Empty
Empty
R N
Critical
Empty
Empty
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PLS: pls_hca_connect ToMasterAgent: mgmt_wait_initia lize() failed, code <code>.
Warni ng
Empty
Empty
When the D-Board comes up from reset, it will attempt to connected to the Master Agent on the V-Board to get its MIB configurations. If the connection failed, it will back-off and reattempt after a few seconds. No action required. No action required. The D-Board will retry to connect to the V-Board.
R N
R N
October 30, 2008
MDG4-29

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PLS: pls_hca_connect ToMasterAgent: Registering SMI_GROUP_m dg4AppObjects failed. PLS: pls_hca_connect ToMasterAgent: Registering SMI_GROUP_m dg4LoadSheddin g failed. PPRT: ppr_hca_connec tToMasterAgent: mgmt_init_env() failed.
Warni ng
Empty
Empty
No action required. The D-Board will retry to connect to the V-Board.
Y C / l N e a r R N
Comments & Notes
Warni ng
Empty
Empty
R N
Warni ng
Empty
Empty
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT: ppr_hca_connec tToMasterAgent: mgmt_poll() failed. PPRT: ppr_hca_connec tToMasterAgent: mgmt_select_fd( ) failed.
Warni ng
Empty
Empty
R N
U D-Board connectivity to VBoard is temporary lost.
R N
Critical
Empty
Empty
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT: ppr_hca_connec tToMasterAgent: mgmt_wait_initia lize() failed, code <code>.
Warni ng
Empty
Empty
R N
R N
MDG4-30
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT: ppr_hca_connec tToMasterAgent: Registering SMI_GROUP_m dg4AppObjects failed. PPRT: ppr_hca_connec tToMasterAgent: Registering SMI_GROUP_m dg4BillGenObjec ts failed. PPRT: ppr_hca_connec tToMasterAgent: Registering SMI_GROUP_m dg4EncryptCom pBasic failed. PPRT: ppr_hca_connec tToMasterAgent: Registering SMI_GROUP_m dg4LlcObjects failed. PPRT: ppr_hca_connec tToMasterAgent: Registering SMI_GROUP_m dg4MobileIpSyst em failed. PPRT: ppr_hca_connec tToMasterAgent: Registering SMI_GROUP_m dg4SlmObjects failed. PPRT: ppr_hca_MA_evt __ipc_rx_data: mgmt_poll() failed.
Warni ng
Empty
Empty
Y C / l N e a r R N
Comments & Notes
Warni ng
Empty
Empty
R N
Warni ng
Empty
Empty
R N
Warni ng
Empty
Empty
R N
Warni ng
Empty
Empty
R N
Warni ng
Empty
Empty
R N
Warni ng
Empty
Empty
R N
October 30, 2008
MDG4-31

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
app_name:MLN K:MDG[<My_id> ] Failed to register stat <stat_id> RAG: mdg4AppObject s registration failed. RAG: mdg4RagBasicO bjects registration failed. RAG: mdg4RagDownl oadObjects registration failed. RAG: mdg4RagEntry registration failed. RAG: mgmt_select_fd( ) failed.
Critical
Empty
Empty
Contact the iDEN Customer Network Resolution Center for assistance. No action necessary.
Y C / l N e a r R N
Comments & Notes
U The process failed to register a stat. Common Agent API failure.
Warni ng
Empty
Empty
R N
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Warni ng
Empty
Empty
R N
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Warni ng
Empty
Empty
R N
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Warni ng
Empty
Empty
R N
100108
CA API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Bill: Failed to add timer
Critical
Empty
Empty
The board will reset and the backup V board will become active. No action necessary. The board will reset and the backup V board will become active. No action necessary. Reset the D-board to get rid of the potential memory issue. Note: Doing this will effect PD service.
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
app_name:NELi nk: Failed to add timer with arg
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: timer_db_add failed.
Critical
Empty
Empty
R N
U The RAGT process was not able to register with the Master Agent on the VBoard. RAGT will back-off and retry again. U The RAGT process was not able to register with the Master Agent on the VBoard. RAGT will back-off and retry again. U The RAGT process was not able to register with the Master Agent on the VBoard. RAGT will back-off and retry again. U The RAGT process was not able to register with the Master Agent on the VBoard. RAGT will back-off and retry again. U The RAGT process was not able to retrieve the file descriptor from the Common Agent. The V-Board will be reset. U The process failed to add a timer into the timer database. Process might have run out of memory or other software failure. U The process failed to add a timer into the timer database. Process might have run out of memory or other software failure U Timer Database was not able to add timer successfully. Check for memory consumption on board, as this may be at critical levels hence causing timer db add failures
MDG4-32
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : PendRegNewRe g : timer DB fail <srcaddr>
Major
Empty
Empty
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT: Couldn't add iDEN PPR Rag Active Indication timer for ACG_ID: <acg_id>.
Critical
Empty
Empty
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT: Failed to add pm_report_timer for PPR Task.
Critical
Empty
Empty
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SFUT: Failed to add pm_report_timer for SFU Task.
Critical
Empty
Empty
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MMI_MON: Failed to add pm_report_timer for MMI_MON Task.
Critical
Empty
Empty
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: Call to timer_db_add failed for t3153!
Critical
Empty
Empty
MIPR failed to create timer. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should
Y C / l N e a r R N
Comments & Notes
U MIPR failed to create timer db
R N
U 1) Timer database was not able to add timer successfully. 2) D-board could possibly be having higher memory consumption and at critical levels.
R N
R N
U 1) Timer database was not able to add timer successfully. 2) C-board could possibly be having higher memory consumption and at critical levels.
R N
U 1) Timer database was not able to add timer successfully. 2) C-board could possibly be having higher memory consumption and at critical levels.
R N
October 30, 2008
MDG4-33

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100109 Timer DB Failure 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 SLM: Call to timer_db_add failed for tcleanup! Critical Empty Empty recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed R N
Comments & Notes
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: Call to timer_db_add failed for tirperr!
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: Call to timer_db_add failed for tretr!
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: Call to timer_db_add failed for tsess!
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: Call to timer_db_add failed for tsusp!
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: failed_srpc_obj_ add: SRPC timer_db_add_ti ck alarm_timer failed.
Critical
Empty
Empty
R N
MDG4-34
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) Retry of Channel_Requests may not happen. 3) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself 1) The various tasks within the MDG box should be able to control this excessive memory consumption. 2) No action will be needed and the system should recover itself The SFUT process on the C-Board could not allocate memory for starting a timer for inbound packet data. The critical alarm would cause the C-Board to reset. No action is needed. The SFUT process on the C-Board could not allocate memory for starting a timer for inbound packet data. The critical alarm would cause the C-Board to reset. No action is needed. The SFUT process on
Comments & Notes
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: process_rag_acti vated: SRPC timer_db_add_ti ck sanity_timer failed.
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: srpc_sanity_time _out: SRPC timer_db_add_ti ck sanity_timer failed.
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: start_srpc_hold_ timer: SRPC timer_db_add_ti ck failed.
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPI: Failed to add bundle_reorder_t imer for SRP_IN.
Critical
Empty
Empty
R N
U This alarm would apply during C-Board operation.
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPI: Failed to add bundle_send_tim er for SRP_IN.
Critical
Empty
Empty
R N
processingF
100109
Timer DB Failure
1.3.6.1.4.1.161.3
MDG4_AP
SRPI: Failed to
Critical
Empty
Empty
R N
U This alarm would apply
October 30, 2008
MDG4-35

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent .3.10.5.27.1.11.2 .1.0 P add bundle_timer for SRP_IN. the C-Board could not allocate memory for starting a timer for inbound packet data. The critical alarm would cause the C-Board to reset. No action is needed. The SFUT process on the C-Board could not delete a timer for inbound packet data. The critical alarm would cause the C-Board to reset. No action is needed. The SFUT process on the C-Board could not delete a timer for inbound packet data. The critical alarm would cause the C-Board to reset. No action is needed. The SFUT process on the C-Board could not delete a timer for inbound packet data. The critical alarm would cause the C-Board to reset. No action is needed. No user action required. The C-Board will reset.
Comments & Notes
during C-Board operation.
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPI: Failed to delete bundle_reorder_t imer for SRP_IN.
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPI: Failed to delete bundle_send_tim er for SRP_IN.
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPI: Failed to delete bundle_timer for SRP_IN.
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPO: Couldn't add iDEN timer SFU_OB_CACH E_TMR.
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPO: Couldn't add iDEN timer SFU_OB_SEND _TMR.
Critical
Empty
Empty
No user action required. The C-Board will reset.
R N
U Timer Database was not able to add timer successfully due to C-Board run out of memory. SFUT task on C-Board detected that there was no more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board. U Timer Database was not able to add timer successfully due to C-Board run out of memory. SFUT task on C-Board detected
MDG4-36
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100109
Timer DB Failure
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P MDG4_AP P
100109
Timer DB Failure
MDG4_AP P
100109
Timer DB Failure
MDG4_AP P
PPR: Failed to add Ppr_acc_ib_bun dle timer for PPR. PPR: Failed to add ppr_chann_grant _accumulation_ti mer for PPR. PPR: Failed to restart Ppr_acc_ib_bun dle timer for PPR. RAGT: Couldn't add Checkpoint timer. RAGT: Couldn't add PD Allowed Health Check timer. SFU: Failed to add Sfu_acc_conn timer for SFU. UTL: Timer pool memory is corrupted.
Critical
Empty
Empty
R N
that there was no more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board. U The PPRT process on the DBoard could not start a timer. The D-Board will be reset.
Critical
Empty
Empty
R N
U The PPRT process on the DBoard could not start a timer. The D-Board will be reset.
Critical
Empty
Empty
R N
U The PPRT process on the DBoard could not start a timer. The D-Board will be reset.
Critical
Empty
Empty
R N
Critical
Empty
Empty
R N
U The PPRT process on the DBoard could not start a timer. The D-Board will be reset. U The PPRT process on the DBoard could not start a timer. The D-Board will be reset. U The PPRT process on the DBoard could not start a timer. The D-Board will be reset. U The timer mechanism in the MDG detected a memory corruption and could not continue. The board (V, D, or C) that encountered this condition will be reset. U The timer mechanism in the MDG detected a failure and could not continue. The Board (V, D, or C) that encountered this condition will be reset. U AUDIT failed to open VLRM connection to the port ICS_AUDIT_VLRM. The board has reached a critical
Critical
Empty
Empty
R N
Critical
Empty
Empty
R N
100109
Timer DB Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
UTL: Timer pool tick could not be started.
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
AUDIT: Can not open connection (listen) to port <port>
Critical
Empty
Empty
R N
October 30, 2008
MDG4-37

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
AUDIT: Can't open Sublink Manager. errno <errno>
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
AUDIT: Can't subscriber to LinkObserver DAP Links. errno <errno>
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
AUDIT: Failed to establish connection to sublink manager. errno <errno>
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
AUDIT: Failed to register routing information with sublink manager. errno <errno>
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
AUDIT: Failed to register with sublink. errno <errno> id <registration_id> status <status>
Critical
Empty
Empty
R N
processingF
100110
iRP API Failure
1.3.6.1.4.1.161.3
MDG4_AP
AUDIT:
Critical
Empty
Empty
R N
software failure. The board will be reset and failover mechanisms will be engaged. AUDIT failed to open Sublink Manager and reported the error code. The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged. AUDIT failed to subscribe to Link Observer DAP Links and reported the error code. The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged. AUDIT failed to establish connection to Sublink Manager and reported the error code. The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged. AUDIT failed to register routing information with Sublink Manager and reported the error code. The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged. AUDIT failed to register with Sublink Manager and reported the error code. The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged. AUDIT failed to initialize
MDG4-38
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent .3.10.5.27.1.11.2 .1.0 P IRP_Link_Obser ver.initialize() error, errno <errno>.
Comments & Notes
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Bill: Failed to bind to local ESAN address.
Critical
Empty
Empty
Verify that ESAN IP address of the V board is configured correctly.
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Bill: get_local_ip Failed to return ESAN IP address Bill: get_local_ip Failed to return iDEN IP address app_name:MLN K:MDG <mdg_id> failed connection open(). Ret = <ret> err = <errno> iLNK: get_local_ip Failed to return iDEN IP address
Critical
Empty
Empty
Verify that ESAN IP address of the V board is configured correctly.
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
Verify that iDEN IP address of the V board is configured correctly. Verify that the iDEN IP address is configured correctly.
R N
100110
iRP API Failure
MDG4_AP P
Critical
Empty
Empty
R N
Link Observer and reported the error code. The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged. The process could not bind to local ESAN IP address and hence cannot communicate with the D board. The process could not get the ESAN IP address of the V board and hence cannot communicate with the D board. The process could not get the iDEN IP address and hence cannot communicate with the BA. The process could not bind to the iDEN IP address and hence cannot communicate with remote MDGs.
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
Verify that iDEN IP address of the V board is configured correctly.
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100110
iRP API Failure
MDG4_AP P
iLNK:MDG[<mdg _id>] failed to open server listening socket. Ret = <ret> err = <errno> MIPD : mipd_rag_info : COA coa_ip installation fail MIPD : mipd_rag_info : Install FA
Critical
Empty
Empty
Verify that iDEN IP address of the V board is configured correctly.
R N
Major
Empty
Empty
Major
Empty
Empty
Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for
R N
U The process could not get the iDEN IP address and hence cannot communicate with the iVPU. V board will failover and standby V board will become active. U The process could not get the iDEN IP address and hence cannot communicate with the iVPU. V board will failover and standby V board will become active. U MIP_Driver failed to install COA interface
R N
U MIP_Driver failed to install FA interface
October 30, 2008
MDG4-39

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r fa_ip/fa_subnet fail MIPD : mipd_rag_info : Start RIPv2 for <coa_ip> fail MIPD : mipd_rag_info : stop COA <coa_ip> advertisement fail MIPD : mipd_rag_info : alarm for COA <IP Address> advertisement fail cleared MIPD: COA <coa_ip> uninstallation fail MIPR: mipr_hca_conne ctToMasterAgent : ACE_IPC_Event s.open() failed. MIPR: mipr_hca_conne ctToMasterAgent : new ACE_IPC_Event s() failed. PLS: pls_hca_connect ToMasterAgent: ACE_IPC_Event s.open() failed. PLS: pls_hca_connect ToMasterAgent: new ACE_IPC_Event s() failed. PPRT: ppr_hca_connec assistance. Major Empty Empty Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. R N
Comments & Notes
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
U MIP_Driver failed to set advertised IP address
100110
iRP API Failure
MDG4_AP P
Major
Empty
Empty
R N
U MIP_Driver failed to deadvertise COA interface
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Clear
Empty
Empty
No action required.
C N
U MIP_Driver COA advertisement failure condition has been cleared.
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
100110
iRP API Failure
MDG4_AP P
Critical
Empty
Empty
Contact the iDEN Customer Network Resolution Center for assistance. No action required. The D-Board will retry to connect to the V-Board.
R N
U MIP_Driver failed to delete COA interface
R N
U MIPR failed to create object
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
U MIPR failed to open connection to Master Agent
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2
MDG4_AP P
Critical
Empty
Empty
No action required. The D-Board will retry to
R N
MDG4-40
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r .1.0 tToMasterAgent: ACE_IPC_Event s.open() failed. PPRT: ppr_hca_connec tToMasterAgent: new ACE_IPC_Event s() failed. RAG: Can not open RAGC connection errno <errno> connect to the V-Board.
Comments & Notes
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Can not open RAGS connection errno <errno>
Major
Empty
Empty
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Connection error <errno>
Critical
Empty
Empty
The RAGT process on the Hot-Standby VBoard could not open a connection with the RAGT process on the Active V-Board. This would prevent the RAG data from being 'checkpointed' with the Hot-Standby V-Board. The remedy is to make sure the Active V-Board is operational. If the Active V-Board is operational, then the Hot-Standby V-Board will need to be resetted. The RAGT process on the Active V-Board could not open a connection with the RAGT process on the Hot-Standby VBoard. This would prevent the RAG data from being 'checkpointed' with the Hot-Standby V-Board. The remedy is to make sure the Hot-Standby VBoard is operational. If the Hot-Standby VBoard is operational, then the Active V-Board will need to be resetted. The RAGT process on the V-Board could not send RAG information to the VLRM process on
R N
U This alarm would apply to a two V-Boards configuration.
R N
U This alarm would apply to a two V-Boards configuration.
R N
October 30, 2008
MDG4-41

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100110 iRP API Failure 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 RAG_Mgmt_Evt>open() failed. Critical Empty Empty the same V-Board. K37. If the RAGT process on the V-Board could not connect to the Master Agent (also on the same V-Board), then a critical alarm would cause the current V-Board to reset and the Hot-Standby VBoard to become active. No action is needed. The PPRT process on the D-Board could not send a 'PD MS Active' LAPD message to the DAP. The critical alarm would cause the current D-Board to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not send a 'PD MS Dormant Request' LAPD message to the DAP. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. VDRR was unable to get the board status indications from CWNS. The board will fail over and the standby V board will recover. VDRR could not register for application probing. This indicates an iRP service failure. The board will be reset and the standby V board will take over. No action necessary. R N
Comments & Notes
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: in process_dll(activ e): ppr_frlk_lapd_se nd failed, errno <errno>, idx <vlr_index>
Critical
Empty
Empty
R N
U This alarm would apply during active D-Board operation.
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: in process_dll(dor mant_req): ppr_frlk_lapd_se nd failed, errno <errno>, idx <vlr_index>
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VDRR: Failed to register for CWNS callback. ID <id> Status <status> VDRR: Failed to register for probing.
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Minor
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2
MDG4_AP P
VDRR: mgmt_init_env()
Minor
Empty
Empty
R N
U Software warning. The software will continually
MDG4-42
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r .1.0 failed
Comments & Notes
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
app_name: mgmt_select_fd failed VLRC:Can not open VLRM connection to port <ICS_VLRC_VL RM>
Critical
Empty
Empty
R N
100110
iRP API Failure
MDG4_AP P
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRC:Can not open VLRM RESYNCH connection to port <ICS_VLRC_VL RM_RESYNCH>
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Can not open CMNM connection to port <ICS_CMNM_V LRM> errno <errno> VLRM: Can not open connection (listen) to port <port_id> errno <errno>
Critical
Empty
Empty
Critical
Empty
Empty
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
processingF
100110
iRP API Failure
1.3.6.1.4.1.161.3
MDG4_AP
VLRM: CONTROLLER: Can not open connection (listen) to port <port_id> errno <errno> VLRM: Can't
Critical
Empty
Empty
Critical
Empty
Empty
VLRM Failed to open a connection to CMNM because the port was already in use. The V board will failover and the standby V board will recover. VLRM Failed to open a listening connection because the port was already in use. The V board will failover and the standby V board will recover. VLRM Failed to open a listening connection because the port was already in use. The V board will failover and the standby V board will recover. VLRM attempted to
R N
attempt to recover until successful or board reset. No user intervention is required. Board Failure. The board can not perform its normal operation. It will be reset to recover. VLRC failed to open VLRM connection to the port ICS_VLRC_VLRM. The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged. VLRC failed to open VLRM RESYNCH connection to the port ICS_VLRC_VLRM_RESYN CH. The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged. Board Failure. The board can not perform its normal operation. It will be reset to recover.
R N
R N
R N
U Board Failure. The board
October 30, 2008
MDG4-43

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent .3.10.5.27.1.11.2 .1.0 P open Sublink Manager. errno <errno> open the Sublink Manager connection but failed because the iRP service could not start. The V board will failover and the standby V board will take over. VLRM could not get link status from the Link Observer. This indicates iRP service failure. The V board will failover and the standby V board will recover. Contact the iDEN Customer Network Resolution Center for assistance.
Comments & Notes
can not perform its normal operation. It will be reset to recover.
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Can't subscriber to LinkObserver DAP Links. errno <errno>
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Error registering MDG4_MS_PDR EG_UPDATE statistic; result=<Mdg4Ms PdReg> VLRM: Error registering MS_RECORD_ MODIFIED statistic; result=<count> VLRM: Failed to establish connection to sublink manager. errno <errno>
Major
Empty
Empty
R N
Major
Empty
Empty
R N
Critical
Empty
Empty
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
app_name: Failed to register for CWNS callback. ID <id> Status <status> VLRM: Failed to register routing information with sublink manager. errno <errno>
Major
Empty
Empty
VLRM attempted to open the Sublink Manager connection but failed because the iRP service could not start. The V board will failover and the standby V board will take over. No action necessary.
R N
R N
U Board Failure. The board can not perform its normal operation. It will be reset to recover. U Board Failure. The board can not perform its normal operation. It will be reset to recover.
Critical
Empty
Empty
VLRM attempted to register for related messages with the Sublink Manager but failed because the iRP service could not start. The V board will failover
R N
MDG4-44
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r and the standby V board will take over. VLRM attempted to register for related messages with the Sublink Manager but failed because the iRP service could not start. The V board will failover and the standby V board will take over. VLRM could not set the configuration so the board will be failed over and the standby V board will recover. VLRM could not register for application probing. This indicates an iRP service failure. The board will be reset and the standby V board will take over. No action necessary.
Comments & Notes
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Failed to register with sublink. errno <errno> id <registration_id> status <status>
Critical
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Failed to set configuration. Status <status>
Critical
Empty
Empty
R N
U Board Failure. The board can not perform its normal operation. It will be reset to recover. U Board Failure. The board can not perform its normal operation. It will be reset to recover.
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: Failed to register for probing.
Minor
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: mgmt_init_env() failed
Minor
Empty
Empty
R N
100110
iRP API Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VLRM: mgmt_select_fd failed
Critical
Empty
Empty
100110
iRP API Failure
100112
Process Initialization Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P MDG4_AP P
VLRM: STATS: Couldn't start the stats timer. MIPD : mipd_rag_info : FA subnet router setup fail
Major
Empty
Empty
VLRM could not receive data from the specified file descriptor. To recover the board will be failed over and the standby V board will recover. No action necessary.
R N
U Software warning. The software will continually attempt to recover until successful or board reset. No user intervention is required. U Board Failure. The board can not perform its normal operation. It will be reset to recover.
R N
Major
Empty
Empty
Contact the iDEN Customer Network Resolution Center for assistance. Reset the D card manually. If this does not help lock and reset the MDG node from the OMC.
R N
U The VLRM process on the VBoard could start a timer to peg the PM stats. U MIP_Driver failed to setup FA subnet router IP address (default gateway)
October 30, 2008
MDG4-45

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
100112
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100112
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPD : mip_rag_info : pdip event connection failure for coa_ip MIPD: mipd_init : pdip connection failure
Major
Empty
Empty
Reset D-board or MDG node
Y C / l N e a r R N
Comments & Notes
U Cannot open raw socket connection for outbound data on a specific RAG
Major
Empty
Empty
100112
Process Initialization Failure Process Initialization Failure Process Initialization Failure Process Initialization Failure
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100112
MDG4_AP P
MIPR : MIPD_ind:HA connection failure MIPR : PPR connection failure MIPR : VLRM connection failure PLS: Unable to get shared memory.
Major
Empty
Empty
Major
Empty
Empty
100112
MDG4_AP P
Major
Empty
Empty
100112
MDG4_AP P
Critical
Empty
Empty
100113
RAG Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Invalid Checkpointing Message Type Received
Minor
Empty
Empty
100113
RAG Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Invalid RAG OBJ SM Event <event>
Minor
Empty
Empty
Contact the iDEN Customer Network Resolution Center for assistance. MIPD will retry to establish the connection. If connection retries continue unsuccessfully, lock and reset the MDG node from the OMC. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. PLS is unable to create shared memory. No memory is available on the board. The D board will failover to the standby D board. The RAGT process on the Standby-V Board received an invalid message from the RAGT process on the Active-V Board. The message is discarded. No action required. The RAGT process detected an invalid internal event for its internal RAG Object database. The event is discarded. No action
R N
U MIP_Driver failed to open raw socket
R N
U MIPR failed to create home agent connection
R N
U MIPR failed to create PPRT connection
R N
U MIPR failed to create VLRM connection
R N
U Board Failure. The board will be reset to recover from this error.
R N
U The RAG Module on the BAckup V Board received an Invalid Checkpoint Message Type.
R N
U RAG Object State Machine received an Invalid Event.
MDG4-46
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100113 RAG Error 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 RAG: RAG OBJ SM Event for Invalid RAG Id <rag_id> Minor Empty Empty required. The RAGT process detected an internal event being generated for a RAG Object database for an invalid RAG_ID greater than 31. This is 0-based value from 0 to 31 for valid RAG_ID. The event is discarded. No action required. The PPRT process on the D-Board has received an invalid index associated with a subscriber. The critical alarm would cause the current D-Board to reset and the Hot-Standby DBoard to become active. No action is needed. The D-board will be reset and failover. The bundle timer should not be running in this LAPi state. R N
Comments & Notes
U RAG Object State Machine received an Event for an Invalid RAG ID.
100114
VLR Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: In slm_acg_del_ind : invalid vlr_index rx. idx = <vlr_index>
Critical
Empty
Empty
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: invalid bundle timer expiry for s2
Major
Empty
Empty
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: invalid bundle timer expiry for s3
Major
Empty
Empty
The D-board will be reset and failover. The bundle timer should not be running in this LAPi state.
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: invalid isrr timer expiry for s2
Major
Empty
Empty
The D-board will be reset and failover. The receiver ready timer should not be running in LAPi states other than S6_2 (connection established, busy).
R N
U Bundle Timer expiry is invalid in state S2. This could mean: (1) The timer was not deleted from the database when LAPi link went down. (2) The timer was started in the wrong state (3) LAPi is not really in S2 U Bundle Timer expiry is invalid in state S3. This could mean: (1) The timer was not deleted from the database when LAPi link went down. (2) The timer was started in the wrong state (3) LAPi is not really in S3 U ISRR Timer expiry is invalid in state S2. This could mean: (1) The timer was not deleted from the database when LAPi link went down. (2) The timer was started in the wrong state (3) LAPi is
October 30, 2008
MDG4-47

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100115 Invalid State 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 LAPi: invalid isrr timer expiry for s3 Major Empty Empty The D-board will be reset and failover. The receiver ready timer should not be running in LAPi states other than S6_2 (connection established, busy). The D-board will be reset and failover. The receiver ready timer should not be running in LAPi states other than S6_2 (connection established, busy). The D-board will be reset and failover. The receiver ready timer should not be running in LAPi states other than S6_2 (connection established, busy). The D-board will be reset and failover. The receiver ready timer should not be running in LAPi states other than S6_2 (connection established, busy). The D board will reset and failover. The SLM and LAPi protocol layers are out of synchronization. The D board will reset and failover. The SLM and LAPi protocol layers are out of synchronization. R N
Comments & Notes
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: invalid isrr timer expiry for s6_1
Major
Empty
Empty
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: received invalid SLM enable primitive for s2 LAPi: received invalid SLM userdata primitive for s2
Major
Empty
Empty
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2
MDG4_AP P
LAPi: received invalid SLM
Major
Empty
Empty
The D board will reset and failover. The SLM
R N
not really in S3 U ISRR Timer expiry is invalid in state S3. This could mean: (1) The timer was not deleted from the database when LAPi link went down. (2) The timer was started in the wrong state (3) LAPi is not really in S3 U ISRR Timer expiry is invalid in state S4. This could mean: (1) The timer was not deleted from the database when LAPi link went down. (2) The timer was started in the wrong state (3) LAPi is not really in S4 U ISRR Timer expiry is invalid in state S5. This could mean: (1) The timer was not deleted from the database when LAPi link went down. (2) The timer was started in the wrong state (3) LAPi is not really in S5 U ISRR Timer expiry is invalid in state S6_1. This could mean: (1) The timer was not deleted from the database when LAPi link went down. (2) The timer was started in the wrong state (3) LAPi is not really in S6_1 U SLM thinks LAPi is disabled and tries to enable it when in fact it already is enabled. This can only be caused by LAPi-SLM being out of sync. U SLM is initiating outbound data transmission thinking LAPi is connection established when in fact LAPi is S2 state. This can only be caused by LAPi-SLM being out of sync. U SLM is initiating outbound data transmission thinking
MDG4-48
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r .1.0 userdata primitive for s3 and LAPi protocol layers are out of synchronization.
Comments & Notes
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: received invalid SLM userdata primitive for s4
Major
Empty
Empty
The D board will reset and failover. The SLM and LAPi protocol layers are out of synchronization.
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: received invalid SLM userdata primitive for s5
Major
Empty
Empty
The D board will reset and failover. The SLM and LAPi protocol layers are out of synchronization.
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAG: Invalid PD Reg State <state> Received for RAG <rag_id>
Minor
Empty
Empty
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
<AppName>: CWNS: Transition from ACTIVE>STANDBY handled with failover. PPR: Invalid DBoard CWNS transition out of CWNS_ACTIVE during run-time, slot <physical_slot>. PPR: Invalid DBoard CWNS transition out of
Critical
Empty
Empty
The RAGT process received a PD_Reg_State primitive from the VLRM process on the V-Board for an invalid RAG_ID greater than 31. This is 0-based value from 0 to 31 for valid RAG_ID. The primitive will be ignored. No action required. No action necessary.
R N
LAPi is connection established when in fact LAPi is S3 state. This can only be caused by LAPi-SLM being out of sync. U SLM is initiating outbound data transmission thinking LAPi is connection established when in fact LAPi is S4 state. This can only be caused by LAPi-SLM being out of sync. U SLM is initiating outbound data transmission thinking LAPi is connection established when in fact LAPi is S5 state. This can only be caused by LAPi-SLM being out of sync. U RAG Module received an Invalid PD Reg State.
R N
U The Board (V, D, or C) detected an invalid transition from "active" to "non active". The Board that detected this condition will reset.
Critical
Empty
Empty
R N
U The D-Board detected an invalid transition from "active" to "non active". The D-Board will be resetted.
Critical
Empty
Empty
R N
U The D-Board detected an invalid transition from "active" to "non active". The
October 30, 2008
MDG4-49

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r CWNS_ACTIVE with RAG, slot <physical_slot>. SFU: Invalid CBoard CWNS transition out of CWNS_ACTIVE during run-time, slot <physical_slot>. SRPC: MS record is linked to SRPC object 0x0 in ms_canceltimer_ s3. SRPC: MS record is linked to SRPC object 0x0 in ms_chan_need_ s1. SRPC: MS record is linked to SRPC object 0x0 in ms_timerout_s3. Bill: Buffer alloc failed when trying to build msg for BA[<NEid>] Bill: Buffer alloc failed when trying to recv data from BA[<NEid>] Bill: Buffer alloc failed when trying to recv data from Billgen Bill: Buffer alloc failed when trying to recv data from NM Billgen: Buffer alloc failed when
Comments & Notes
D-Board will be resetted.
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
U The C-Board detected an invalid transition from "active" to "non active". The C-Board will be resetted.
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
U The PPRT process detected that a subscriber has no associated SRPC object. PPRT cleans up and continue. U The PPRT process detected that a subscriber has no associated SRPC object. PPRT cleans up and continue. U The PPRT process detected that a subscriber has no associated SRPC object. PPRT cleans up and continue. U The process could not allocate a buffer.Memory not available.
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100115
Invalid State
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
The board will reset and the backup V board will become active. No action necessary. The board will reset and the backup V board will become active. No action necessary. The board will reset and the backup V board will become active. No action necessary. The board will reset and the backup V board will become active. No action necessary. The board will reset and the backup V board will
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
U The process could not allocate a buffer.Memory not available.
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2
MDG4_AP P
Critical
Empty
Empty
R N
U The process could not allocate a buffer.Memory not available. U The process could not allocate a buffer.Memory not available. U The process could not allocate a buffer.Memory not
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
R N
MDG4-50
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r .1.0 trying to create billing record..cannot generate record CRM: Couldn't allocate ACG_CONTROL _STR for adding ACG <acgid>. become active. No action necessary.
Comments & Notes
available.
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: Couldn't allocate iDEN SLM_RAG_CEL L_CONTROL_S TR for adding ACG <acgid>.
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: Couldn't allocate iDEN SLM_RAG_CEL L_CONTROL_S TR for rag_idx <ragidx>, state <state>. CRM: Couldn't allocate iDEN SRP_REQ_MSG _QUEUE for adding ACG <acgid>.
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: Couldn't allocate iDEN SRP_REQ_MSG _QUEUE for rag_idx <ragidx>, state <state>. CRM: Couldn't allocate WiDEN SLM_RAG_CEL
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a
R N
U 1) Certain tasks on the dboard are consuming excessive memory, leaving no memory for others. 2) DBoard will inform HA about its ability to allocate memory
R N
R N
R N
R N
R N
U 1) Certain tasks on the dboard are consuming excessive memory, leaving
October 30, 2008
MDG4-51

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r L_CONTROL_S TR for adding ACG <acgid>. core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed Memory is depleted, the D board will be reset and failover.
Comments & Notes
no memory for others. 2) DBoard will inform HA about its ability to allocate memory
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: Couldn't allocate WiDEN SLM_RAG_CEL L_CONTROL_S TR for rag_idx <ragidx>, state <state>. CRM: Couldn't allocate WiDEN SRP_REQ_MSG _QUEUE for adding ACG <acgid>.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CRM: Couldn't allocate WiDEN SRP_REQ_MSG _QUEUE for rag_idx <ragidx>, state <state>. LAPi: Couldn't allocate LAPI_DB.msrec _tab for <num_ms_max> MSs. LAPi: lapi_malloc_bcb out(<size>) failure.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
U Lapi IB Receiver can't allocate more memory. This could either point to excessive pd traffic on MDG or a memory leak. U This alarm would apply during active D-Board operation.
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2
MDG4_AP P
LAPi: lapi_malloc_dcb
Critical
Empty
Empty
The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not
R N
R N
U This alarm would apply during active D-Board
MDG4-52
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r .1.0 out(<size>) failure. allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No
Comments & Notes
operation.
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: lapi_malloc_pcb out(<size>) failure.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: lapi_malloc_pcto ut(<size>) failure.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: lapi_malloc_ppd out(<size>) failure.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: lapi_malloc_wind ow(<size>) failure.
Critical
Empty
Empty
R N
October 30, 2008
MDG4-53

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100116 Buffer Error 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 LAPi: LLC_IB_RX: Failed to allocate the buffer for BUNDLE_CB. LAPi: LLC_IB_RX: Failed to allocate the buffer for I_DCB_T. LAPi: LLC_IB_RX: Failed to allocate the buffer for PACKET_CB. LAPi: mma_ppr_mallo c(<size>) failure. Critical Empty Empty action is needed. Memory is depleted, the D board will be reset and failover. R N
Comments & Notes
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
Memory is depleted, the D board will be reset and failover.
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPD : OBdataRcvd : buffer allocation fail
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : mip_alloc : Memory exhausted
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : mip_free : Memory was never allocated
Minor
Empty
Empty
The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. MIPR failed to allocate memory. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. MIPR failed to free memory. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance.
R N
U Lapi IB Receiver can't allocate more memory. This could either point to excessive pd traffic on MDG or a memory leak. U Lapi IB Receiver can't allocate more memory. This could either point to excessive pd traffic on MDG or a memory leak. U Lapi IB Receiver can't allocate more memory. This could either point to excessive pd traffic on MDG or a memory leak. U LAPi is unable to get memory. D-Board is out of memory. This could either point to excessive pd traffic on MDG or a memory leak. U This alarm would apply during active D-Board operation.
R N
U Memory allocation failure.
R N
U Illegal memory operation
MDG4-54
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : PendRegNewRe q : IRP failed to allocate buffer for pending reg. structure
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT : ipip_input : IRP failed to allocate buffer for ICMP message
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT : ipip_input : IRP failed to allocate the buffer to outbound data block
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT : ipip_input : IRP failed to allocate the buffer to outbound data control block
Critical
Empty
Empty
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT : mipd_init : IRP failed to allocate buffer for ICMP list structure
Critical
Empty
Empty
MIPR failed to allocate memory. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No
Y C / l N e a r R N
Comments & Notes
U Memory allocation failure.
R N
R N
R N
R N
October 30, 2008
MDG4-55

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100116 Buffer Error 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 PPRT : MIPD_RegReply Rcvd : IRP failed to allocate buffer for receiving reg. reply from MIPR Critical Empty Empty action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DR N
Comments & Notes
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT : MIPD_RegReply Rcvd : IRP failed to allocate buffer for reg. reply control block
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT : MIPD_RegReqF wd : IRP failed to allocate buffer for MIPD->MIPR ics message
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT : rfcl_userdata_in d : IRP failed to allocate buffer for icmp message
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT : rfcl_userdata_in d : IRP failed to allocate buffer for icmp message control
Critical
Empty
Empty
R N
MDG4-56
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r block Board to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The PPRT process on the D-Board could not allocate memory for processing packet data. The critical alarm would cause the current DBoard to reset and the Hot-Standby D-Board to become active. No action is needed. The D-Board will reset. The staand-by D board will become active. No action required.
Comments & Notes
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT: lap_ib_recv_mall oc: IRP Failed to allocate the buffer.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT: ppr_ics_add_usr data_node:
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
PPRT: ppr_ics_send_cb oard_sfu_mib: Couldn't allocate memory to send MIB to SFU Task. PPRT: ppr_srpin_llc_ma lloc: IRP Failed to allocate the buffer for the receiving message. RAGT: Can not allocate memory
Critical
Empty
Empty
R N
U No memory is available on the D-Board.
Critical
Empty
Empty
The D-Board will reset. The staand-by D board will become active. No action required.
R N
U No memory is available on the D-Board.
Critical
Empty
Empty
The RAGT process on the V-Board could not allocate any memory from the Operating System for normal operation. The critical alarm would cause the current V-Board to be resetted and the Hot-
R N
October 30, 2008
MDG4-57

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Standby V-Board to become active. No action is needed. The RAGT process on the V-Board could not allocate any memory from the Operating System for sending messages to the PPRT process on the D-Board. The critical alarm would cause the current VBoard to be resetted and the Hot-Standby VBoard to become active. No action is needed. The C-Board will reset and then become active . No action required
Comments & Notes
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
RAGT: rag_ics_send_ra g_active_msg_to _ppr:
Critical
Empty
Empty
R N
U This alarm would apply during RAG Update with the ACGs.
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100116
Buffer Error
MDG4_AP P
100116
Buffer Error
MDG4_AP P
SFUT: Failed to allocate the buffer for receiving message. SFUT: Failed to allocate the buffer for SFU_MR. SFUT: Failed to allocate the buffer for TEI_TABLE. SLM: In process_dll(dor mant): mmamalloc fails!
Critical
Empty
Empty
R N
U No memory is available on the C-Board for the SFU Task.
Critical
Empty
Empty
The C-Board will reset and then become active . No action required. The C-Board will reset and then become active. No action required The PPRT process on the D-Board cannot allocate memory to send out the MS_Dormant_Request message to the DAP. The 'critical' alarm will cause the D-Board to reset. No action necessary. The PPRT process on the D-Board cannot allocate memory to send out the MS_Active message to the DAP. The 'critical' alarm will cause the D-Board to reset. No action
R N
U No memory is available on the C-Board for the SFU Task. U No memory is available on the C-Board for the SFU Task. U mmamalloc failed for dormant_req msg
Critical
Empty
Empty
R N
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: In process_dll(ms_ active): mmamalloc fails!
Critical
Empty
Empty
R N
U mmamalloc failed for ms_active msg
MDG4-58
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100116 Buffer Error 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 SLM: In slm_ragcell_init_ req: malloc fails! Critical Empty Empty necessary. When the RAG gets assigned, the PPRT process on the D-Board cannot allocate memory for its internal database. The 'critical' alarm will cause the D-Board to reset. No action necessary. The PPRT process on the D-Board cannot allocate memory for its internal MS database. The 'critical' alarm will cause the D-Board to reset. No action necessary. 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be R N
Comments & Notes
U crm failed malloc for slm ragcell structure
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SLM: slm_heap__swa p: malloc fails!
Critical
Empty
Empty
R N
U SLM tried to malloc memory for swap and failed.
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: make_cancel_gr ant: SRPC memory allocation failed for BCB.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: make_cancel_gr ant: SRPC memory allocation failed for PCB.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: make_req_msg: SRPC memory allocation failed.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: srpc_bcb_send: Couldn't allocate memory for send_buf.
Critical
Empty
Empty
R N
U 1) Certain tasks on the dboard are consuming excessive memory, leaving no memory for others. 2) DBoard will inform HA about
October 30, 2008
MDG4-59

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r generated. 3) No additional action is needed 1) HA will trigger the reset of the D-Board. 2) For this critical issue, a core file will automatically be generated. 3) No additional action is needed Reset the MDG C board.
Comments & Notes
its ability to allocate memory
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: srpc_init_buf: Couldn't allocate <malloc_sz> bytes of memory for mssrpS.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100116
Buffer Error
MDG4_AP P
SRPI: Failed to allocate the buffer for <buffer>. SRPO: Couldn't allocate C_BUNDLE_CB.
Critical
Empty
Empty
R N
U SFU task can't allocate more memory
Critical
Empty
Empty
No user's action required. C-Board will reset.
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPO: Couldn't allocate C_PACKET_CB.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPO: Couldn't allocate iDEN C_BUNDLE_CB.
Critical
Empty
Empty
No user's action required. C-Board will reset..
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPO: Couldn't allocate iDEN C_PACKET_CB.
Critical
Empty
Empty
R N
U SFUT task could not allocate memory on C-Board due to C-Board run out of memory. SFUT task on C-Board detected that there was no more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board. U SFUT task could not allocate memory on C-Board due to C-Board run out of memory. SFUT task on C-Board detected that there was no more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board. U SFUT task could not allocate memory on C-Board due to C-Board run out of memory. SFUT task on C-Board detected that there was no more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board.. U SFUT task could not allocate memory on C-Board due to C-Board run out of memory. SFUT task on C-Board detected that there was no
MDG4-60
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r
Comments & Notes
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPO: Couldn't allocate iDEN CACHE_R.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPO: Couldn't allocate iDEN Extension Block SFU.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPO: Couldn't allocate iDEN Packet Header SFU.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPO: Couldn't allocate memory for SRPO.
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
VCRT: Couldn't allocate memory during backup VCRT: Couldn't allocate memory for complete req.
Critical
Empty
Empty
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
VCRT could not allocate memory. The board will be reset and the standby V board will recover. VCRT could not allocate memory. The board will be reset and the standby
R N
more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board. SFUT task could not allocate memory on C-Board due to C-Board run out of memory. SFUT task on C-Board detected that there was no more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board. SFUT task could not allocate memory on C-Board due to C-Board run out of memory. SFUT task on C-Board detected that there was no more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board. SFUT task could not allocate memory on C-Board due to C-Board run out of memory. SFUT task on C-Board detected that there was no more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board. SFUT task could not allocate memory on C-Board due to C-Board run out of memory. SFUT task on C-Board detected that there was no more memory left, logged a critical alarm, and generated a core file. HA detected it, and reset C-Board. Board Failure. The board will be reset to recover from this error.
R N
October 30, 2008
MDG4-61

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100116 Buffer Error 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 VCRT: Couldn't allocate memory for replication. VCRT: Couldn't allocate memory for the start req. VCRT: Couldn't allocate memory for VCRT lists. VCRT: Couldn't map the shared memory. VDRC: Couldn't allocate memory for advertisement request. VDRC: Couldn't allocate memory for advertisement response. VDRR: Couldn't allocate memory during initialization VLRC: Cannot create resynch client for RAG: <rag_id>. No memory. Critical Empty Empty V board will recover. VCRT could not allocate memory. The board will be reset and the standby V board will recover. VCRT could not allocate memory. The board will be reset and the standby V board will recover. VCRT could not allocate memory. The board will be reset and the standby V board will recover. VCRT could not allocate memory. The board will be reset and the standby V board will recover. VCRT could not allocate memory. The board will be reset and the standby V board will recover. VCRT could not allocate memory. The board will be reset and the standby V board will recover. VCRT could not allocate memory. The board will be reset and the standby V board will recover. No action necessary. R N
Comments & Notes
U Board Failure. The board will be reset to recover from this error. U Board Failure. The board will be reset to recover from this error. U Board Failure. The board will be reset to recover from this error. U Board Failure. The board will be reset to recover from this error. U Board Failure. The board will be reset to recover from this error.
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
R N
U Board Failure. The board will be reset to recover from this error. U VLRC failed to create resynch client for RAG: <rag_id>. No memory. The board has reached a critical software failure. The board will be reset and failover mechanisms will be engaged. U Board Failure. The board will be reset to recover from this error. U Memory allocation failure.
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100116
Buffer Error
MDG4_AP P
VLRM: Can not create ClientController. No Memory. VLRM: Can not create resynch client. No memory.
Critical
Empty
Empty
Critical
Empty
Empty
VLRM can not allocate memory. The board will failover and the standby V board will recover. VLRM process on the VBoard cannot allocate memory for the 'Resync Client'. No action
R N
R N
MDG4-62
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100116 Buffer Error 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 VLRM: Can not create the RAG Controller. No Memory. VLRM: Couldn't allocate memory during initialization VLRM: Couldn't allocate memory during RAG initialization MIPD : mip_ics_enqueu e : Can not allocate MIP_CONN_Q_ NODE. Critical Empty Empty necessary. VLRM can not allocate memory. The board will failover and the standby V board will recover. VLRM can not allocate memory. The board will failover and the standby V board will recover. VLRM can not allocate memory. The board will failover and the standby V board will recover. MIPD failed to allocate memory. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. 1)Check MDG-BA link status and take action to bring the link up if it is down. 2)Check health of BA Check health of BA. R N
Comments & Notes
U Board Failure. The board will be reset to recover from this error. U Board Failure. The board will be reset to recover from this error. U Board Failure. The board will be reset to recover from this error. U The PPRT process on the DBoard could not allocate memory to queue up MIP Registration message from the subscriber. The subscriber will retry.
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
MDG4_AP P
Critical
Empty
Empty
R N
100116
Buffer Error
MDG4_AP P
Major
Empty
Empty
R N
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Bill: Billing Block Q is full. Starting to discard billing data Bill: Cannot send Billing Block <curr_seq_num> to BA. Discarding after <MAX_ATTEMP TS> attempts Bill: Resuming to store Billing Records
Major
Empty
Empty
R N
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
U The Queue that stores billing records on the V board is full since Bill process has not been able to send the records to the BA. U MDG is unable to send a Billing information to the BA
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Clear
Empty
Empty
No action required.
C N
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Billgen: Resuming to generate Billing Records
Clear
Empty
Empty
No action required.
C N
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2
MDG4_AP P
Billgen:Billing Block Q size
Major
Empty
Empty
1)Check health of V board. 2)Verify that the
R N
U This alarm clears a previously sent alarm (Bill: Billing Block Q is full. Starting to discard billing data.). U This alarm clears a previously sent alarm (Billgen:Billing Block Q size reached max limit <MAX_BB_CNT>. Not generating anymore Billing Records.). U The process cannot generate anymore billing
October 30, 2008
MDG4-63

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r .1.0 reached max limit <MAX_BB_CNT >. Not generating anymore Billing Records LAPi: failed to queue event Bill process is running on the V board.
Comments & Notes
records as the queue on the D board has reached its maximum limit.The D board is probably not able to send records to the V board.
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
LAPi queue is full. Check D-board CPU usage. Check PD traffic rate on D-board.
R N
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: over 10 events in queue event.
Major
Empty
Empty
LAPi queue is almost full. Check D-board CPU usage. Check PD traffic rate on D-board.
R N
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
LAPi: only 2 slot left in queue event.
Major
Empty
Empty
LAPi queue is almost full. Check D-board CPU usage. Check PD traffic rate on D-board.
R N
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
processingF
100117
Queue Error
1.3.6.1.4.1.161.3
MDG4_AP
PPR: Health check failed for interboard communication queues, SRPO: Packet data traffic has halted for more than <msec> msec, slot <SLOT>, tick delta <ticks>, time_now_msec <msec>, time_bcb_rx_sfu _tx <msec>, time_delta_msec <msec>, sfu_in_count <COUNT>. SRPO: Packet
Critical
Empty
Empty
No action required.
R N
Major
Empty
Empty
No action required.
R N
U LAPi event queue is full and cannot process any more events. This can happen if PPRT task is starved not giving LAPi chance to process the events on its queue. U LAPi event queue is almost full. This can happen if PPRT task is starved not giving LAPi chance to process the events on its queue. U LAPi event queue is almost full. This can happen if PPRT task is starved not giving LAPi chance to process the events on its queue. U The PPRT process watchdog on the D-Board has detected an interboard communication failure. The D-Board will be reset. U The SFUT process watchdog on the C-Board has detected outbound packet data flow has halted. The CBoard will be reset.
Clear
Empty
Empty
No action necessary -
C N
U Outbound data traffic is
MDG4-64
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent .3.10.5.27.1.11.2 .1.0 P data traffic has halted for more than <msec> msec, slot <SLOT>. VLRC: vlrcToVlrmQ remained down for more than u msec. VLRM: pVlrmClientToVlr mServerQ remained down for more than u msec. SLM: Detected long period of congestion (X secs), rag_id X, acg_id X, sect_id X, heap_counter X. Bill:NELink:Bad BB Ack timer received in configuration. Using app's default. Bill:NELink:Bad client_conn_wait timer received in configuration. Using app's default. Bill:NELink:Bad Hold off timer received in configuration. Using app's default. Bill:NELink:Bad Reg Resp timer received in configuration. Using app's default. the outbound data processing will eventually be restored.
Comments & Notes
temporarily halted until the SFUT task regains processing time.
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
No action required.
R N
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Critical
Empty
Empty
No action required.
R N
U The PPRT process watchdog on the D-Board has detected an interboard communication failure. The D-Board will be reset. U The VLRM process watchdog on the V-Board has detected an interboard communication failure. The V-Board will be reset. U The SLM process may be indefinitely stuck in congestion.
100117
Queue Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.1
MDG4_AP P
Major
Empty
Empty
D-Board needs to be reset to clear this situation.
R Y
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer.
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download.
October 30, 2008
MDG4-65

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Bill:NELink:Bad SC Heartbeat timer received in configuration. Using app's default. Bill:NELink:Bad SC Hold timer received in configuration. Using app's default. CMNM:MLNK:IP Configuration information not received for MDG[<mdg_id>] CMNM:MLNK:M DG[<mdg_id>]:D id not receive valid port number
Major
Empty
Empty
No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. Verify that IP address for the MDG is configured in the Configuration file.
Y C / l N e a r R N
Comments & Notes
Major
Empty
Empty
R N
Critical
Empty
Empty
R N
U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process has not received IP address information for local MDG.
Minor
Empty
Empty
Verify that port number configured in the Configuration file is correct.
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
CMNM:MLNK:M ore than <MAX_MLink_M DG> MDGs configured in PD region. Establishing TCP links to all MDGs with ids <MAX_MLink_ID >. CMNM:NELink:B ad client_conn_wait timer received in configuration. Using app's default. CMNM:NELink:B ad Hold off timer received in configuration. Using app's
Major
Empty
Empty
Verify that there are up to a maximum of 32 MDGs configured in the Configuration file.
R N
U The process received an invalid port number to listen on. If the port number is configured correctly, look for alarms/information referring to problems during configuration download. U More than 32 MDGs are configured in the PD region. The process will establish TCP connections up to a maximum of 32 MDGs and ignore the rest.
Major
Empty
Empty
No remedy action needs to be taken as the process will use the default value for the timer.
R N
U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during
Major
Empty
Empty
R N
MDG4-66
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100120 Configuration Error 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 default. CMNM:NELink:B ad LVC Down timer received in configuration. Using app's default. CMNM:NELink:B ad LVC fail timer received in configuration. Using app's default. CMNM:NELink:B ad LVC Request timer received in configuration. Using app's default. CMNM:NELink:B ad SC Heartbeat timer received in configuration. Using app's default. CMNM:NELink:B ad SC Hold timer received in configuration. Using app's default. CMNM:NELink:B ad server_conn_wai t timer received in configuration. Using app's default. iLNK:More than <MAX_iLNK_iVP U> iVPUs configured in PD region. Establishing TCP links with all IVPUs with ids < <MAX_iLNK_ID+ Major Empty Empty No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. R N
Comments & Notes
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U MDG will establish TCP connections only with iVPUs with ids in the allowed range.
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
More than maximum allowed iVPUs are configured. Check Configuration file.
R N
October 30, 2008
MDG4-67

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100120 Configuration Error 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 1>. MIPR : ALARM_MSG_E MULATION : Emulation fail <n> times for DAP <dap_id> Warni ng Empty Empty MIPR failed to perform subscriber emulation because of invalid authentication key received during packet data registration. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. No action necessary. R N
Comments & Notes
U Invalid authentication key for emulation
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : ALARM_MSG_R EVERTUN : Error Code <code>: Rejection=<code >: IMSI = {<IMSI>}:{<IMSI >}:{<IMSI>}:{<IM SI>}:{<IMSI>} MIPR: RegRequestRcv d : Error code <code> : Rejection = <total number of rejection in 5 minutes>: IMSI = <imsi_1> <imsi_2> <imsi_3> <imsi_4> <imsi_5> VDRR:MLNK:IP Configuration information not received for MDG[<mdg_id>] VDRR:MLNK:M DG[<mdg_id>]:D id not receive valid port number
Warni ng
Empty
Empty
R N
U Reverse Tunneling is required by FA. However, the MN does not request the reverse tunneling service and the FA emulation is not enabled.
Warni ng
Empty
Empty
No action required.
R N
U Rejection of none reverse tunneling capable mobile node in the reverse tunneling required network
Critical
Empty
Empty
Verify that IP address for the MDG is configured in the Configuration file.
R N
U The process has not received IP address information for local MDG.
Minor
Empty
Empty
Verify that port number configured in the Configuration file is correct.
R N
U The process received an invalid port number to listen on. If the port number is configured correctly, look for alarms/information referring to problems during
MDG4-68
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent 100120 Configuration Error 1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0 MDG4_AP P 0 VDRR:MLNK:Mo re than <MAX_MLink_M DG> MDGs configured in PD region. Establishing TCP links to all MDGs with ids <MAX_MLink_ID >. VDRR:NELink:B ad client_conn_wait timer received in configuration. Using app's default. VDRR:NELink:B ad Hold off timer received in configuration. Using app's default. VDRR:NELink:B ad LVC Down timer received in configuration. Using app's default. VDRR:NELink:B ad LVC fail timer received in configuration. Using app's default. VDRR:NELink:B ad LVC Request timer received in configuration. Using app's default. VDRR:NELink:B ad SC Heartbeat timer received in configuration. Major Empty Empty Verify that there are upto a maximum of 32 MDGs configured in the Configuration file. R N
Comments & Notes
configuration download. U More than 32 MDGs are configured in the PD region. The process will establish TCP connections upto a maximum of 32 MDGs and ignore the rest.
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
October 30, 2008
MDG4-69

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Using app's default. VDRR:NELink:B ad SC Hold timer received in configuration. Using app's default. VDRR:NELink:B ad server_conn_wai t timer received in configuration. Using app's default. PLS: CPU threshold exceeded for board with physical slot ID: <id>, CPU = [<percentage>%] . PLS: CPU threshold alarm cleared for board with physical slot ID: <id>. PLS: Memory Threshold exceeded for board with physical slot ID: <id> <Memory pool name> [<percentage>%] . PLS: Memory threshold alarm cleared for board with physical slot ID: <id>. MIPD : MIPD_Visitor::Vi sitorAdd fail vlr_index = <index> timer. Major Empty Empty No remedy action needs to be taken as the process will use the default value for the timer. No remedy action needs to be taken as the process will use the default value for the timer. R N
Comments & Notes
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100120
Configuration Error
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
R N
there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U The process received an invalid timer value. The timer in the Configuration file was incorrectly configured or there was a problem during configuration download. U CPU usage on the D-board has exceeded the set threshold value. Packets will be dropped till the CPU usage falls below the low watermark.
100121
Load Shedding Info
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
No action required.
R N
100121
Load Shedding Info
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Clear
Empty
Empty
No action required.
C N
U CPU usage on the D-board has become available.
100121
Load Shedding Info
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
No action required.
R N
U Memory usage has exceeded the set threshold value for one or more of the memory pools. Packets will be dropped till the memory usage falls below the low watermark.
100121
Load Shedding Info
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Clear
Empty
Empty
No action required.
C N
U Memory has become available on the D-board to process outbound datagrams U Failed to insert visitor in MIP_Driver tree database
100411
MDG Application General Information
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
Major
Empty
Empty
MIPD failed to add visitor in local tree database. No action is necessary if this is intermittent, otherwise
R N
MDG4-70
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r contact the iDEN Customer Network Resolution Center for assistance. MIPD failed to remove visitor from local tree database. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. MIPR failed to add visitor in local tree database. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. MIPR failed to locate visitor in local tree database. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. MIPR failed to locate visitor in local tree database for request from home agent. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. MIPR failed to locate visitor in local tree database for request from VLRM. No action is necessary if this is intermittent, otherwise
Comments & Notes
100411
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPD_Visitor : VisitorRemove fail vlr_index = <index>
Major
Empty
Empty
R N
U Failed to remove visitor from MIP_Driver tree database
100411
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : MIPR_Visitor : VisitorAdd fail vlr_index = <index>
Major
Empty
Empty
R N
U Failed to insert visitor in MIPR tree database
100411
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : RegReplyRcvd : VisitorLocate or pending node fail mn <mn_ipaddr> ha <ha_ipaddr>
Minor
Empty
Empty
R N
U Failed to locate visitor in MIPR tree database
100411
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : AlarmTimeOut : HA VisitorLocate or pending node fail <#> times in last <#> minutes
Minor
Empty
Empty
R N
U Count of failure for home agent request to locate visitor in MIPR tree database in last N minutes.
100411
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR : AlarmTimeOut : VLRM VisitorLocate or pending node fail <#> times in last
Minor
Empty
Empty
R N
U Count of failure for VLRM request to locate visitor in MIPR tree database in last N minutes.
October 30, 2008
MDG4-71

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r <#> minutes contact the iDEN Customer Network Resolution Center for assistance. MIPR failed to remove visitor from local tree database. No action is necessary if this is intermittent, otherwise contact the iDEN Customer Network Resolution Center for assistance. 1) No specific action needed 2) While, packet data for this subscriber may be affected, other subscribers will not be affected No action necessary.
Comments & Notes
100411
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
MIPR_Visitor : VisitorRemove fail vlr_index = <index>
Major
Empty
Empty
R N
U Failed to remove visitor from MIPR tree database
100411
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100411
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
100411
1.3.6.1.4.1.161.3 .3.10.5.27.1.11.2 .1.0
MDG4_AP P
SRPC: process_bundle_ sent: srpc_get_ms_re cord(vlr_index <vlr_index>, tei 0xX) is NULL. VLRM: MIP UPDATE: DAP unrecoverable failure, the subscriber Tei = <TEI> VLRM: Max number of subscribers reached. <max_subs> ACG Link Version Check Failed for ACG <acg id> at DLCI <dlci> Port <port> DAP Link Version Check Failed for DAP <dap id> at DLCI <dlci> Port <port> ACG Link Version Check Failed for ACG
Warni ng
Empty
Empty
R N
Warni ng
Empty
Empty
R N
U 1) The D-Board in trying to forward the message from the ACG to its task is failing to obtain the subscriber information. 2) The subscriber database on the D-Board could be corrupted U DAP could not process the MIP update request from the MDG due to an unrecoverable failure
Warni ng
Empty
Empty
MDG at capacity. Increase MDG capacity or add additional MDGs
R N
100500
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Major
Empty
Empty
Check configuration to make sure that the correct ACG ID is being used
R N
U The MDG is at capacity. No more subscribers can be registered. A system change is required to recover from this situation. More capacity is needed. U Cause: Attempted to perform a link version check with an invalid ACG.
100500
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Major
Empty
Empty
Check configuration to make sure that the correct DAP ID is being used
R N
U Cause: Attempted to perform a link version check with an invalid DAP
100500
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Major
Empty
Empty
Check configuration to make sure that the correct ACG ID is being
R N
U Cause: Attempted to perform a link version check with an invalid ACG.
MDG4-72
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r <acg id> at <ip address>:<port> DAP Link Version Check Failed for DAP <acg id> at <ip address>:<port> Timedout waiting for VCheck request from ACG <acg id> DLCI <dlci> Port <port> used Major Empty Empty Check configuration to make sure that the correct DAP ID is being used Confirm that LAPD is configured between the ACG and MDG. Confirm that the ACG is sending a Link Version Request message and the MDG4 is sending a Link Version Response message Confirm that LAPD is configured between the DAP and MDG. Confirm that MDG4 is sending a Link Version Request message Confirm that LAPD is configured between the ACG and MDG. Confirm that the ACG is sending a Link Version Request message and the MDG4 is sending a Link Version Response message Confirm that LAPD is configured between the DAP and MDG. Confirm that MDG4 is sending a Link Version Request message No action required. R N
Comments & Notes
100500
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
U Cause: Attempted to perform a link version check with an invalid DAP
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Major
Empty
Empty
R N
U Cause: A link version request message was never received from an ACG
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Timedout waiting for VCheck response from DAP <dap id> DLCI <dlci> Port <port> Timedout waiting for VCheck request from ACG <acg id> at <ip address>:<port>
Major
Empty
Empty
R N
U Cause: A link version message was sent to a DAP but a response was never received
Major
Empty
Empty
R N
U Cause: A link version request message was never received from an ACG
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Timedout waiting for VCheck response from DAP <dap id> at <ip address>:<port> Timedout waiting for VCheck request from ACG <acg id> DLCI <dlci> Port <port> Timedout waiting for VCheck response from DAP <dap id>
Major
Empty
Empty
R N
U Cause: A link version message was sent to a DAP but a response was never received
Clear
Empty
Empty
C N
U This clears a previously reported alarm.
Clear
Empty
Empty
No action required.
C N
October 30, 2008
MDG4-73

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r DLCI <dlci> Port <port> Timedout waiting for VCheck request from ACG <acg id> at <ip address>:<port> Timedout waiting for VCheck response from DAP <dap id> at <ip address>:<port> Unrecognized ITC message from ACG <acg id> DLCI <dlci> Port <port> Unrecognized ITC message from DAP <dap id> DLCI <dlci> Port <port> Unrecognized ITC message from ACG <acg id> <ip address>:<port> Unrecognized ITC message from DAP <dap id> <ip address>:<port> Initial Synchronization failure Time Synchronization lost Configuration Mistmatch <item1> != <item 2> FGDL failed due
Comments & Notes
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Clear
Empty
Empty
No action required.
C N
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Clear
Empty
Empty
No action required.
C N
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Major
Empty
Empty
Verify the contents of the header in question
R N
U Cause: A link version message was received with an invalid header
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Major
Empty
Empty
R N
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Major
Empty
Empty
R N
100501
Link Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0
MDG4_PLA T
Major
Empty
Empty
R N
communicat ionFailureE vent communicat ionFailureE vent communicat ionFailureE vent processingF
100502
Time Synchronization Failure Time Synchronization Failure Port Status/Failure
1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0 1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0 1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0 1.3.6.1.4.1.161.3
MDG4_PLA T
Major
Empty
Empty
100502
MDG4_PLA T
Major
Empty
Empty
100503
MDG4_PLA T
Major
Empty
Empty
100507
Software
MDG4_PLA
Major
Empty
Empty
Confirm that the time server is running and that there is IP connectivity Confirm that the time server is running and that there is IP connectivity Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN
R N
U Cause: Synchronization with the time server was never established U Cause: Synchronization with the time server was established but lost U Reserved for Future Use
R N
R N
R N
U Cause: Attempted a FGDL
MDG4-74
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Sever ity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent Upgrade Failure .3.10.5.24.1.4.1. 1.0 1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0 1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0 1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0 1.3.6.1.4.1.161.3 .3.10.5.24.1.4.1. 1.0 T to <reason> Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance. Correct the MDGc iDEN IP Address so that it is on the same subnet mask as the default gateway.
Comments & Notes
and a failure was detected
100507
MDG4_PLA T
SU failed upgrading board <FRU> Internal Config file <name> missing Internal Software component <name> missing MDGc iDEN IP Address <address> logical slot <FRU> subnet differs from default gateway <address> with mask <mask>
Major
Empty
Empty
R N
U Cause: Attempted to upgrade a payload board and failed U Reserved for Future Use
100508
Initialization Failure
MDG4_PLA T
Major
Empty
Empty
R N
100508
Initialization Failure
MDG4_PLA T
Major
Empty
Empty
R N
U Reserved for Future Use
100509
Configuration Error
MDG4_PLA T
Critical
Empty
Empty
R N
N Cause: The MDGc iDEN IP Address is configured on a different subnet than the default gateway and cannot communicate to components outside the MDG chassis.
October 30, 2008
MDG4-75
Release SR17.0
__________________________________ State Changes

State Changes
Reason Code
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C Comments h & Notes a n g e S t a t u s U Empty
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
100700
A PD user deregisters A PD user deregisters A PD user deregisters A user assigned to the RAG Active to ColdStandby Active to ColdStandby Active to ColdStandby Active to ColdStandby Alarm to No Alarm Alarm to No Alarm Alarm to No Alarm Alarm to No Alarm Alarm to No Alarm Alarm to No Alarm Alarm to No Alarm ColdStandby to Active ColdStandby to Active
1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.7.2.4.1.2.<ragID> 1.3.6.1.4.1.161.3.3.10.5. 27.1.7.2.4.1.2.<ragID> 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0
MDG4_NO DE MDG4_NO DE MDG4_RA G MDG4_RA G MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_NO DE MDG4_MO DE MDG4_MO DE
U-EImp S-EImp U-EImp U-E-Idl L-D-Idl L-E-Idl L-D-A L-E-A L-D-A L-E-A U-D-A U-E-A S-IImp S-I-A L-EImp S-I-Idl
U-E-A
Empty
Empty
100700
S-E-A
Empty
Empty
100700 100701 100702 100702 100702 100702 100703 100703 100703 100703 100703 100703 100703 100704
1-32 1-32 0 0 0 0 0 0 0 0 0 0 0 0
U-E-A U-E-A S-I-Idl S-I-Idl S-I-A S-I-A L-D-Idl L-E-Idl U-DIdl U-E-Idl S-I-Idl S-I-Idl L-E-Idl L-D-Idl
Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty
Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty
A Packet Data user has deregistered from maximum number of SUs / Alarm state to No Alarm. A Packet Data user has deregistered from maximum number of SUs / Alarm state to No Alarm. OMC locked the node. At least one Packet Data user has been assigned to the RAG. The MDG has moved to ColdStandby status. The MDG has moved to ColdStandby status. The MDG has moved to ColdStandby status. The MDG has moved to ColdStandby status. The MDG alarm state has moved to No Alarm. The MDG alarm state has moved to No Alarm. The MDG alarm state has moved to No Alarm. The MDG alarm state has moved to No Alarm. The MDG alarm state has moved to No Alarm. The MDG alarm state has moved to No Alarm. The MDG alarm state has moved to No Alarm. The MDG has been moved from Coldstandby to Active status by the cluster manager. The MDG has been moved from Coldstandby to Active status by the
U Empty
N N N N N N N N N N N N N N
U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty
100704
S-I-Idl
L-E-Idl
Empty
Empty
U Empty
MDG4-76
October 30, 2008
Release SR17.0
State Changes
Reason Code

Event Description
O u t a g e ( Y / N )
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
100704
ColdStandby to Active ColdStandby to Active ColdStandby to HotStandby ColdStandby to HotStandby ColdStandby to HotStandby ColdStandby to HotStandby Hardware container state transitioned Hardware container state transitioned HotStandby to Active HotStandby to Active HotStandby to Active HotStandby to Active HotStandby to ColdStandby HotStandby to ColdStandby HotStandby to ColdStandby HotStandby to ColdStandby No Alarm to Alarm No Alarm to Alarm No Alarm to
1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5.
MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_NO DE MDG4_NO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO
S-I-A
L-D-A
Empty
Empty
100704
S-I-A
L-E-A
Empty
Empty
100705
S-I-Idl
U-DIdl U-E-Idl
Empty
Empty
100705
S-I-Idl
Empty
Empty
100705
S-I-A
U-D-A
Empty
Empty
100705
S-I-A
U-E-A
Empty
Empty
100707
L-D-Idl
L-E-Idl
Empty
Empty
cluster manager. The MDG has been moved from Coldstandby to Active status by the cluster manager. The MDG has been moved from Coldstandby to Active status by the cluster manager. The MDG has been moved from Coldstandby to HotStandby status by the cluster manager. The MDG has been moved from Coldstandby to HotStandby status by the cluster manager. The MDG has been moved from Coldstandby to HotStandby status by the cluster manager. The MDG has been moved from Coldstandby to HotStandby status by the cluster manager. The MDG node has been enabled.
U Empty
U Empty
U Empty
U Empty
U Empty
U Empty
100707
U-DIdl U-DIdl U-E-Idl U-D-A U-E-A U-DIdl U-E-Idl U-D-A U-E-A L-D-Idl L-E-Idl U-D-
U-E-Idl
Empty
Empty
The MDG node has been enabled.
U Empty
100708 100708 100708 100708 100709 100709 100709 100709 100710 100710 100710
0 0 0 0 0 0 0 0 0 0 0
L-D-Idl L-E-Idl L-D-A L-E-A S-I-Idl S-I-Idl S-I-A S-I-A L-D-A L-E-A U-D-A
Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty
Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty
The MDG has moved to Active status. The MDG has moved to Active status. The MDG has moved to Active status. The MDG has moved to Active status. The MDG has moved to ColdStandby status. The MDG has moved to ColdStandby status. The MDG has moved to ColdStandby status. The MDG has moved to ColdStandby status. The MDG alarm state has moved to Major Alarm. The MDG alarm state has moved to Major Alarm. The MDG alarm state has moved to
N N N N N N N N N N N
U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty
October 30, 2008
MDG4-77

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Event Description
O u t a g e ( Y / N )
C Comments h & Notes a n g e S t a t u s U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
100710 100710 100710 100710 100710 100710 100710 100710 100710 100724 100724 100724 100725 100725 100726 100726 100726 100726 100727 100727 100727 100727 100711
Alarm No Alarm to Alarm No Alarm to Alarm No Alarm to Alarm No Alarm to Alarm No Alarm to Alarm No Alarm to Alarm No Alarm to Alarm No Alarm to Alarm No Alarm to Alarm Major Alarm to Critical Alarm Major Alarm to Critical Alarm Major Alarm to Critical Alarm Critical Alarm to Major Alarm Critical Alarm to Major Alarm Coordinator to Participant Coordinator to Participant Coordinator to Participant Coordinator to Participant Participant to Coordinator Participant to Coordinator Participant to Coordinator Participant to Coordinator No user
27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5.
DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_MO DE MDG4_NO DE MDG4_NO DE MDG4_MO DE MDG4_NO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_RA
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1-32
Idl U-E-Idl S-I-Idl S-I-Idl U-E-Idl U-E-A L-E-Idl S-EImp S-E-A L-E-Idl S-I-A U-EImp L-EImp S-IImp L-D-Idl U-E-Idl U-E-A L-E-Idl L-E-A U-DIdl U-D-A L-D-Idl L-D-A U-E-A
U-E-A S-IImp S-I-A U-DIdl U-DIdl L-D-Idl L-D-Idl L-D-Idl L-EImp S-IImp U-DIdl L-D-Idl S-I-A L-EImp U-DIdl U-D-A L-D-Idl L-D-A U-E-Idl U-E-A L-E-Idl L-E-A U-E-Idl
Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty
Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty
Major Alarm. The MDG alarm state has moved to Major Alarm. The MDG alarm state has moved to Critical Alarm. The MDG alarm state has moved to Major Alarm. The MDG node has been disabled. The MDG node has been disabled. The MDG node has been disabled. The MDG node has been disabled. The MDG node has been disabled. The MDG node has been impaired. The MDG alarm state has moved to Critical Alarm. The MDG node has been disabled. The MDG node has been disabled. The MDG alarm state has moved to Major Alarm. The MDG node has been enabled. The MDG role has changed to Participant. The MDG role has changed to Participant. The MDG role has changed to Participant. The MDG role has changed to Participant. The MDG role has changed to Coordinator. The MDG role has changed to Coordinator. The MDG role has changed to Coordinator. The MDG role has changed to Coordinator. No PD user is assigned to the RAG.
N N N N N N N N N N N N N N N N N N N N N N N
MDG4-78
October 30, 2008
Release SR17.0
State Changes
Reason Code

Event Description
O u t a g e ( Y / N )
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent 100712 100712 100712
assigned to the RAG Node is prohibited Node is prohibited Node is prohibited Node is prohibited
27.1.7.2.4.1.2.<ragID> 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0
G MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_NO DE 0 0 0 U-E-A U-EImp U-E-Idl S-E-A S-EImp L-E-Idl Empty Empty Empty Empty Empty Empty OMC locking the node MDG switching from Unlocked to Shuttingdown state. OMC locking the node MDG switching from Unlocked to Shuttingdown state. OMC locking the node MDG switching from Unlocked with 0 subscribers directly to Locked state. OMC locking the node MDG switching from Unlocked with 0 subscribers directly to Locked state while having a Major alarm. OMC locking the node MDG switching from Unlocked with 0 subscribers directly to Locked state. The MDG node is unlocked. The MDG node is unlocked. The MDG node is unlocked. Shuttingdown to Locked. N N N U Empty U Empty U Empty
100712
U-DIdl
L-D-Idl
Empty
Empty
U Empty
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
100712
Node is prohibited Node is unlocked Node is unlocked Node is unlocked Node requests RAG group release Node requests RAG group release Node to release RAG Node to release RAG Node to release RAG Not providing PD service Not providing PD service Not providing PD service Providing PD service Providing PD
1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.7.2.4.1.2.<ragID> 1.3.6.1.4.1.161.3.3.10.5. 27.1.7.2.4.1.2.<ragID> 1.3.6.1.4.1.161.3.3.10.5. 27.1.7.2.4.1.2.<ragID> 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5.
MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_RA G MDG4_RA G MDG4_RA G MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_NO DE MDG4_NO
U-EImp L-D-Idl L-E-Idl L-EImp S-EImp S-E-A
L-EImp U-DIdl U-E-Idl U-EImp L-E-Idl
Empty
Empty
U Empty
100713 100713 100713 100714
0 0 0 0
Empty Empty Empty Empty
N N N N
U Empty U Empty U Empty U Empty
100714
L-E-Idl
Empty
Empty
Shuttingdown to Locked.
U Empty
100715
1-32
U-E-Idl
U-DIdl U-DIdl U-DIdl U-E-Idl U-E-Idl L-EImp U-E-A U-E-
Empty
Empty
100715
1-32
U-E-A
Empty
Empty
100715
1-32
U-EImp U-E-A U-EImp S-EImp U-E-Idl U-E-A
Empty
Empty
100716 100716 100716 100718 100718
0 0 0 0 0
Empty Empty Empty Empty Empty
Empty Empty Empty Empty Empty
The RAG is no longer assigned to the MDG another MDG has claimed it. The RAG has 0 subscribers. The RAG is no longer assigned to the MDG another MDG has claimed it. The RAG has >0 subscribers. The RAG is no longer assigned to the MDG another MDG has claimed it. The RAG has maximum subscribers. All mobiles have deregistered. MDG with 0 subscribers registered switching to no alarm state. The MDG node is locked. At least one mobile has PD registered. The MDG node has received alarms or
U Empty
U Empty
U Empty
N N N N N
U Empty U Empty U Empty U Empty U Empty
October 30, 2008
MDG4-79

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Event Description
O u t a g e ( Y / N )
C Comments h & Notes a n g e S t a t u s U Empty U Empty
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
100718 100719
service Providing PD service RAG assigned and activated RAG maximum capacity reached TCP connection down TCP connection down TCP connection down TCP connection down TCP connection down TCP connection established TCP connection established TCP connection established TCP connection established TCP connection established Platform Failure Platform Failure Platform Failure Platform Failure
27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.3.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.7.2.4.1.2.<ragID> 1.3.6.1.4.1.161.3.3.10.5. 27.1.7.2.4.1.2.<ragID> 1.3.6.1.4.1.161.3.3.10.5. 27.1.8.2.2.1.2.<billLinkN um> 1.3.6.1.4.1.161.3.3.10.5. 27.1.8.2.2.1.2.<billLinkN um> 1.3.6.1.4.1.161.3.3.10.5. 27.1.4.2.5.1.2.<mlnkNu m> 1.3.6.1.4.1.161.3.3.10.5. 27.1.4.2.5.1.2.<mlnkNu m> 1.3.6.1.4.1.161.3.3.10.5. 27.1.15.2.4.1.3.<devNu m> 1.3.6.1.4.1.161.3.3.10.5. 27.1.8.2.2.1.2.<billLinkN um> 1.3.6.1.4.1.161.3.3.10.5. 27.1.8.2.2.1.2.<billLinkN um> 1.3.6.1.4.1.161.3.3.10.5. 27.1.4.2.5.1.2.<mlnkNu m> 1.3.6.1.4.1.161.3.3.10.5. 27.1.4.2.5.1.2.<mlnkNu m> 1.3.6.1.4.1.161.3.3.10.5. 27.1.15.2.4.1.3.<devNu m> 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.2.2.1.7.0
DE MDG4_NO DE MDG4_RA G MDG4_RA G MDG4_BIL L MDG4_BIL L MDG4_ML NK MDG4_ML NK MDG4_iVP U MDG4_BIL L MDG4_BIL L MDG4_ML NK MDG4_ML NK MDG4_iVP U MDG4_MO DE MDG4_MO DE MDG4_MO DE MDG4_MO DE
0 1-32
U-E-Idl U-DIdl U-E-A U-E-Idl
Imp U-EImp U-E-Idl
Empty Empty
Empty Empty
has reached maximum capacity. The MDG node has received alarms. RAG with no subscribers assigned to the MDG (RAG being claimed by the MDG updating DAPs and ACGs). RAG maximum SU capacity has been reached. Billing TCP connection disabled.
N N
100720 100721
1-32 1-2
U-EImp U-DIdl U-DIdl U-DIdl U-DIdl U-DIdl U-E-A
Empty Empty
Empty Empty
N N
U Empty U Empty
100721
1-2
U-E-A
Empty
Empty
Billing TCP connection disabled.
U Empty
100721
1-36
U-E-Idl
Empty
Empty
MDG-MDG TCP connection disabled.
U Empty
100721
1-36
U-E-A
Empty
Empty
MDG-MDG TCP connection disabled.
U Empty
100721
1-252
U-E-A
Empty
Empty
Empty
U Empty
100722
1-2
U-E-Idl
Empty
Empty
Billing TCP connection enabled.
U Empty
100722
1-2
U-DIdl U-E-Idl
U-E-A
Empty
Empty
Billing TCP connection enabled.
U Empty
100722
1-36
U-E-A
Empty
Empty
MDG-MDG TCP connection enabled.
U Empty
100722
1-36
U-DIdl U-D-I
U-E-A
Empty
Empty
MDG-MDG TCP connection enabled.
U Empty
100722
1-252
U-E-A
Empty
Empty
Empty
U Empty
100723 100723 100723 100723
0 0 0 0
L-E-A L-D-A U-E-A U-D-A
S-IImp S-IImp S-IImp S-IImp
A platform failure has occurred. A platform failure has occurred. A platform failure has occurred. A platform failure has occurred.
N N N N
U Empty U Empty U Empty U Empty
MDG4-80
October 30, 2008
Release SR17.0
State Changes
Reason Code

Event Description
O u t a g e ( Y / N )
C Comments h & Notes a n g e S t a t u s U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty U Empty
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
100733 100733 100734 100734 100735 100735 100733 100733 100734 100734 100735 100735 100900
Link container active Link container active Link container impaired Link container impaired Link container disabled Link container disabled Link container active Link container active Link container impaired Link container impaired Link container disabled Link container disabled FRU Disabled
100900
FRU Disabled
100901
FRU HotStandby
100901
FRU HotStandby
100901
FRU HotStandby
100902
FRU InService
100902
FRU InService
100902
FRU InService
1.3.6.1.4.1.161.3.3.10.5. 27.1.4.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.4.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.4.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.4.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.4.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.4.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.15.2.2.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.15.2.2.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.15.2.2.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.15.2.2.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.15.2.2.1.0 1.3.6.1.4.1.161.3.3.10.5. 27.1.15.2.2.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5.
MDG4_ML NK_CT MDG4_ML NK_CT MDG4_ML NK_CT MDG4_ML NK_CT MDG4_ML NK_CT MDG4_ML NK_CT MDG4_iVP U_CT MDG4_iVP U_CT MDG4_iVP U_CT MDG4_iVP U_CT MDG4_iVP U_CT MDG4_iVP U_CT IRP_FRU
0 0 0 0 0 0 0 0 0 0 0 0 1-6, 118 1-6, 118 1-6, 118 1-6, 118 1-6, 118 1-6, 118 1-6, 118 1-6, 1-
U-EImp U-DIdl U-E-A U-DIdl U-E-A U-EImp U-EImp U-DIdl U-DIdl U-E-A U-E-A U-EImp U-E-Idl
U-E-A U-E-A U-EImp U-EImp U-DIdl U-DIdl U-E-A U-E-A U-EImp U-EImp U-DIdl U-DIdl U-DIdl U-DIdl U-E-Idl
Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty
Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty Empty
All links operational. All links operational. Some links operational. Some links operational. No links operational. No links operational. Empty Empty Empty Empty Empty Empty FRU has become non-operational.
N N N N N N N N N N N N N
IRP_FRU
U-E-A
Empty
Empty
FRU has become non-operational.
U Empty
IRP_FRU
U-DIdl U-E-A
Empty
Empty
FRU has become hot standby operational. FRU has become hot standby operational. FRU has become hot standby operational. FRU has become operational.
U Empty
IRP_FRU
U-E-Idl
Empty
Empty
U Empty
IRP_FRU
S-E-A
U-E-Idl
Empty
Empty
U Empty
IRP_FRU
U-E-Idl
U-E-A
Empty
Empty
U Empty
IRP_FRU
U-DIdl S-E-A
U-E-A
Empty
Empty
U Empty
IRP_FRU
U-E-A
Empty
Empty
U Empty
October 30, 2008
MDG4-81

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Event Description
O u t a g e ( Y / N )
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent 100903 FRU Locked/Spare FRU Locked/Spare FRU ShuttingDown Hardware Impaired Hardware Impaired Hardware Inoperable Hardware Inoperable Hardware Operational Hardware Operational FRU HotStandby
100903
100904
100905 100905 100906 100906 100907 100907 100908
100909
FRU InService
100910 100911
IR Link Up LAPD Link Down
24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.6.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.6.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.6.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.6.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.6.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.6.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.5.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.8.2.2.1.2.1.10.<dev Type>.<devNum>.<devL evel>
18 IRP_FRU 1-6, 118 1-6, 118 1-6, 118 0 0 0 0 0 0 1-6, 118 1-6, 118 0 3-4, 110000, 1-2 U-E-Idl L-E-Idl Empty Empty FRU has become spare. N U Empty
IRP_FRU
S-E-A
L-E-Idl
Empty
Empty
FRU has become spare.
U Empty
IRP_FRU
U-E-A
S-E-A
Empty
Empty
FRU is shutting down.
U Empty
IRP_HW_C T IRP_HW_C T IRP_HW_C T IRP_HW_C T IRP_HW_C T IRP_HW_C T IRP_FRU
U-E-A U-DIdl U-E-A U-EImp U-EImp U-DIdl L-E-Idl
U-EImp U-EImp U-DIdl U-DIdl U-E-A U-E-A U-E-Idl
Empty Empty Empty Empty Empty Empty Empty
Empty Empty Empty Empty Empty Empty Empty
Hardware container has become impared. Hardware container has become impared. Hardware container has become nonoperational. Hardware container has become nonoperational. Hardware container has become operational. Hardware container has become operational. FRU has become hot standby operational. FRU has become operational.
N N N N N N N
U Empty U Empty U Empty U Empty U Empty U Empty U Empty
IRP_FRU
L-E-Idl
U-E-A
Empty
Empty
U Empty
IRP_IR_LS IRP_LS
U-E-Idl U-E-A
U-E-A U-E-Idl
Empty Empty
Empty Empty
Link has become operational and in use. Link awaiting successful version check.
N N
U Empty U Empty
100912
LAPD Link Up 1.3.6.1.4.1.161.3.3.10.5. 24.1.8.2.2.1.2.1.10.<dev Type>.<devNum>.<devL evel>
IRP_LS
3-4, 110000, 1-2
U-E-Idl
U-E-A
Empty
Empty
Link has become operational.
U Empty
100913
Port Down 1.3.6.1.4.1.161.3.3.10.5. 24.1.8.2.2.1.2.1.10.<dev Type>.<devNum>.<devL evel>
IRP_LS
3-4, 110000, 1-2
U-E-A
U-DIdl
Empty
Empty
Link has become non-operational.
U Empty
MDG4-82
October 30, 2008
Release SR17.0
State Changes
Reason Code

Event Description
O u t a g e ( Y / N )
100913
Port Down 1.3.6.1.4.1.161.3.3.10.5. 24.1.8.2.2.1.2.1.10.<dev Type>.<devNum>.<devL evel> 1.3.6.1.4.1.161.3.3.10.5. 24.1.5.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.2.1.10.<devTyp e>.<devNum>.<portNum > 1.3.6.1.4.1.161.3.3.10.5. 24.1.8.2.2.1.2.1.10.<dev Type>.<devNum>.<devL evel> 1.3.6.1.4.1.161.3.3.10.5. 24.1.5.1.1.0 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.2.1.10.<devTyp e>.<devNum>.<portNum > 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.2.1.10.<devTyp e>.<devNum>.<portNum > 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.1.1.11.<devTyp e>.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.3.2.2.1.3.<devType >
IRP_LS
3-4, 110000, 1-2
U-E-Idl
U-DIdl
Empty
Empty
Link has become non-operational.
100913 100913
Port Down Port Down
IRP_IR_LS IRP_PORT _LS
0 1-6, 118, 124 3-4, 110000, 1-2
U-E-A U-E-A
U-DIdl U-DIdl
Empty Empty
Empty Empty
Link has become non-operational. Port has become non-operational.
N N
U Empty U Empty
100914
Port Up
IRP_LS
U-DIdl
U-E-Idl
Empty
Empty
Link awaiting successful version check.
U Empty
100914 100914
Port Up Port Up
IRP_IR_LS IRP_PORT _LS
0 1-6, 118, 124 1-6, 118, 124 1-6, 118 1-6, 118 1-6, 118 1-6, 118 1-6, 118 1-6, 118 3-10
U-DIdl U-DIdl
U-E-Idl U-E-Idl
Empty Empty
Empty Empty
Link has become operational. Port has become operational.
N N
U Empty U Empty
100914
Port Up
IRP_PORT _LS
U-E-Idl
U-E-A
Empty
Empty
Port has become operational and in use.
U Empty
100915
FRU Disabled
IRP_FRU
L-E-Idl
L-D-Idl
Empty
Empty
U Empty
100915
FRU Disabled
IRP_FRU
S-E-A
L-D-Idl
Empty
Empty
U Empty
100915
FRU Disabled
IRP_FRU
U-E-Idl
L-D-Idl
Empty
Empty
U Empty
100916
Inoperable FRU unlocked FRU Locked/Spare Inoperable FRU locked Link Container Impaired
IRP_FRU
L-D-Idl
U-DIdl L-E-Idl
Empty
Empty
U Empty
100917
IRP_FRU
L-D-Idl
Empty
Empty
FRU has become spare.
U Empty
100918
IRP_FRU
U-DIdl U-E-A
L-D-Idl
Empty
Empty
U Empty
100919
IRP_LS_CT
U-EImp
Empty
Empty
Some links operational.
U Empty
October 30, 2008
MDG4-83

State Changes
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Event Description
O u t a g e ( Y / N )
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
100919
Link Container Impaired Link Container Disabled Link Container Active Link Container Impaired Link Container Impaired Link Container Disabled Link Container Active FRU Disabled
100920
100921
100922
100922
100923
100924
100925
100925
FRU Disabled
100926
FRU HotStandby
100926
FRU HotStandby
100927
FRU InService
100927
FRU InService
100927
FRU InService
100928
FRU Locked/Spare FRU
100928
1.3.6.1.4.1.161.3.3.10.5. 24.1.3.2.2.1.3.<devType > 1.3.6.1.4.1.161.3.3.10.5. 24.1.3.2.2.1.3.<devType > 1.3.6.1.4.1.161.3.3.10.5. 24.1.3.2.2.1.3.<devType > 1.3.6.1.4.1.161.3.3.10.5. 24.1.8.2.2.1.1.1.6.<devT ype> 1.3.6.1.4.1.161.3.3.10.5. 24.1.8.2.2.1.1.1.6.<devT ype> 1.3.6.1.4.1.161.3.3.10.5. 24.1.8.2.2.1.1.1.6.<devT ype> 1.3.6.1.4.1.161.3.3.10.5. 24.1.8.2.2.1.1.1.6.<devT ype> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.3.1.9.<devType >.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.3.1.9.<devType >.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.3.1.9.<devType >.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.3.1.9.<devType >.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.3.1.9.<devType >.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.3.1.9.<devType >.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.3.1.9.<devType >.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.3.1.9.<devType >.<devNum> 1.3.6.1.4.1.161.3.3.10.5.
IRP_LS_CT
3-10
U-DIdl U-EImp U-EImp U-DIdl U-E-A
U-EImp U-DIdl U-E-A
Empty
Empty
Some links operational.
IRP_LS_CT
3-10
Empty
Empty
No links operational.
U Empty
IRP_LS_CT
3-10
Empty
Empty
All links operational.
U Empty
IRP_NLS_ CT IRP_NLS_ CT IRP_NLS_ CT IRP_NLS_ CT IRP_FRU_ PROTOCO L IRP_FRU_ PROTOCO L IRP_FRU_ PROTOCO L IRP_FRU_ PROTOCO L IRP_FRU_ PROTOCO L IRP_FRU_ PROTOCO L IRP_FRU_ PROTOCO L IRP_FRU_ PROTOCO L IRP_FRU_
3-4
Empty
Empty
Empty
U Empty
3-4
Empty
Empty
Empty
U Empty
3-4
U-EImp U-EImp U-E-Idl
Empty
Empty
Empty
U Empty
3-4
Empty
Empty
Empty
U Empty
1-2, 18 1-2, 18 1-2, 18 1-2, 18 1-2, 18 1-2, 18 1-2, 18 1-2, 18 1-2, 1-
U-DIdl U-DIdl U-E-Idl
Empty
Empty
Empty
U Empty
U-E-A
Empty
Empty
Empty
U Empty
U-DIdl S-E-A
Empty
Empty
Empty
U Empty
U-E-Idl
Empty
Empty
Empty
U Empty
U-E-Idl
U-E-A
Empty
Empty
Empty
U Empty
U-DIdl S-E-A
U-E-A
Empty
Empty
Empty
U Empty
U-E-A
Empty
Empty
Empty
U Empty
U-E-Idl
L-E-Idl
Empty
Empty
Empty
U Empty
S-E-A
L-E-Idl
Empty
Empty
Empty
U Empty
MDG4-84
October 30, 2008
Release SR17.0
State Changes
Reason Code

Event Description
O u t a g e ( Y / N )
angeEvent esmrStateCh angeEvent 100929
Locked/Spare FRU ShuttingDown
24.1.2.2.3.1.9.<devType >.<devNum> 1.3.6.1.4.1.161.3.3.10.5. 24.1.2.2.3.1.9.<devType >.<devNum>
PROTOCO L IRP_FRU_ PROTOCO L
8 1-2, 18 U-E-A S-E-A Empty Empty Empty N U Empty
October 30, 2008
MDG4-85
Release SR17.0
__________________________________ Events
Event Type
Reason Code
OMC Text
MOI Info (Id)
MOI Info (Labe l)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N ) N
availibility Event
reStartEve nt
0 = No Reason Code 1= Platform Hardware Fault 2= Platform OS Fault 3= Platform HA Fault 4= Platform Scheduled 5= Application Software Fault 9= Operator Initiated Platform 1= Indetermin ate 2= Operator Requested 3 = Power On Reset 4= Hardware Reset 5= Software Initiated 6 = Zero
New Mode: <new mode> Time of Switch: <time of switch> Reason Code: <reason code> Old Mode: <old mode> Additional Text: <additional text> Reason Text: <reason text>
Empty
MDG4
Empty
Empty
Empty
Empty
Empty
This trap is sent to indicate any change in the Node Availability.
C Comments & h Notes a n g e S t a t u s U The additional text field indicates current availability status for each FRU type (IPSB, V, D, C, PS, FAN) by listing the number of active, standby (where applicable), and configured number of FRUs of that type. The reason text indicates which FRU event (failure, repair, state change) and which FRU slot caused the availability to change.
New Operate State: <New Operate State> New Usage State: <New Usage State> New Admin State: <New Admin State> System ROM Version: <System ROM Version> System Load Version: <System Software Load Version> System DB Version: <System Database Version> System Code Version:
1.3.6.1.4.1.16 1.3.3.10.5.27. 1.2.2.1.3.0
MDG4 _NOD E
Empty
Empty
Empty
Empty
This trap is sent to indicate that a restart has occurred on the MDG board.
U Empty
MDG4-86
October 30, 2008
Release SR17.0
Event Type
Reason Code

Event Description
O u t a g e ( Y / N )
Comments & Notes
Downtime Upgrade
hwCardCo nfiguration Event
Empty
actionStat usEvent
2= Aborted
<System Code Version> Description: <System Description> System Reset Reason: <System Reset Reason> System Outage Time: <System outage Time> System Reboot Time: <System Reboot Time> System Boot Diagnostics: <System Boot Diagnostics> Device Status: <row status> Device Description: <description> Port 1: <row status> Port 2: <row status> Background Download Aborted
1.3.6.1.4.1.16 1.3.3.10.5.24. 1.2.2.1.1.10.< devType>.<de vNum> 1.3.6.1.4.1.16 1.3.3.10.2.10. 1.1.0
IRP_H WCC
1-6, 118
Empty
Empty
Empty
Empty
This trap is sent to indicate that a platform hardware card configuration event has been encountered.
U Empty
MDG4
Empty
Empty
Empty
Empty
actionStat usEvent
3 = Failed
1.3.6.1.4.1.16 1.3.3.10.2.10. 1.1.0
MDG4
Empty
Empty
Empty
Empty
actionStat usEvent
4= Successful
1.3.6.1.4.1.16 1.3.3.10.2.10. 1.1.0
MDG4
Empty
Empty
Empty
Empty
actionStat usEvent actionStat usEvent
4= Successful 2= Aborted
Background Download Aborted Successfully Background Download Switch Aborted
1.3.6.1.4.1.16 1.3.3.10.2.10. 1.2.0 1.3.6.1.4.1.16 1.3.3.10.2.11. 1.1.0 1.3.6.1.4.1.16 1.3.3.10.2.11. 1.1.0 1.3.6.1.4.1.16 1.3.3.10.2.11. 1.1.0
MDG4
Empty
Empty
Empty
Empty
MDG4
Empty
Empty
Empty
Empty
actionStat usEvent
3 = Failed
MDG4
Empty
Empty
Empty
Empty
actionStat usEvent
4= Successful
MDG4
Empty
Empty
Empty
Empty
Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download abort (bgdlAbort) is successful. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details.
U Empty
U Empty
U Empty
U Empty
U Empty
U Empty
U Empty
October 30, 2008
MDG4-87

Event Type
Reason Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Labe l)
Inst
Event Description
O u t a g e ( Y / N ) N
actionStat usEvent
2= Aborted
Upgrade Aborted
1.3.6.1.4.1.16 1.3.3.10.2.12. 2.1.0
MDG4
Empty
Empty
Empty
Empty
actionStat usEvent
3 = Failed
Upgrade Failed
1.3.6.1.4.1.16 1.3.3.10.2.12. 2.1.0
MDG4
Empty
Empty
Empty
Empty
actionStat usEvent
4= Successful
1.3.6.1.4.1.16 1.3.3.10.2.12. 2.1.0
MDG4
Empty
Empty
Empty
Empty
Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details.
C Comments h Notes a n g e S t a t u s U Empty
&
U Empty
U Empty
MDG4-88
October 30, 2008
Release SR17.0
_____________________________ Alarms
Alarm Type
Alarm Code
OMC-R
Related Alarms Relate d State Change s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Severity
Remedy
R e p o r t &
O u t a g e
communicati onFailureEve nt linkFailureEv ent
30102
All Dap-Links are DOWN x25CircuitDown
EMPTY
OMC
EMPTY
EMPTY
Critical/Clea r Critical/Clea r
EMPTY
EMPTY
Bring one of the dap links up.
Y C / l N e a r R Y C R N C
Comments & Notes
U EMPTY
30003
EMPTY
ne_type (EBTS, BSC, RXCDR)
EMPTY
linkFailureEv ent linkFailureEv ent linkFailureEv ent linkFailureEv ent linkFailureEv ent linkFailureEv ent
30018
Frame Relay PVC Down UDP Link Failure
EMPTY
MDG
EMPTY
"nnnn" where nnnn is unix port number for X25 process (this value is used for internal OMC processing and has little user value). For EBTS only. EMPTY for CP & XCDR. EMPTY
EMPTY
EMPTY
A site reset can cause this alarm. If that is the case then wait until the site comes up. If there is no apparent reason for the link to come down, wait three minutes and if the problem does not clear itself, call CRT.
U EMPTY
Critical/Clea r Critical/Clea r Critical/Clea r Critical/Clea r Critical/Clea r Critical/Clea r
EMPTY
EMPTY
30021
EMPTY
APD
EMPTY
EMPTY
EMPTY
EMPTY
30021
UDP Link Failure
EMPTY
IDAC
EMPTY
EMPTY
EMPTY
EMPTY
30021
UDP Link Failure
EMPTY
ISG
EMPTY
EMPTY
EMPTY
EMPTY
30021
UDP Link Failure
EMPTY
TDAP
EMPTY
EMPTY
EMPTY
EMPTY
30025
OMC Visibility Lost
EMPTY
ne_type (EBTS, iCP, iVPU, HADAP, MDG)
EMPTY
EMPTY
EMPTY
EMPTY
Frame Relay PVC is down. If alarm does not clear, call CRT. The UPD Link has failed. If alarm does not clear, call CRT. The UPD Link has failed. If alarm does not clear, call CRT. The UPD Link has failed. If alarm does not clear, call CRT. The UPD Link has failed. If alarm does not clear, call CRT. Mostly this issue can happen, when the NE lost/recover the connectivity with OMC. This can also happen, if NE doesn't respond for OMC poll requests or responds with invalid values. When this
R N C R N C R N C R N C R N C R N C
U EMPTY
U EMPTY
U EMPTY
U EMPTY
U EMPTY
U EBTS is iCP/iVPU Controlled; MDG is IP Based
October 30, 2008
OMC-R-1

Alarm Type
Alarm Code
Release SR17.0
Severity Related Alarms Relate d State Change s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Alarm is Generated as CRITICAL, the NE should be blue in SSD. If it is CLEAR, SSD shall indicate real time status of NE. This alarm usually clears itself. Anyway, it is a good idea to check for unnecessary files in the partition. The logs partition should only have log files. Call CRT if you find core files in the logs partition. Any other files shall be moved to another pl This alarm usually clears itself. Anyway, it is a good idea to check for unnecessary files in the partition. The logs partition should only have log files. Call CRT if you find core files in the logs partition. Any other files shall be moved to another pl This alarm means that the disk usage is nearing the upper limit on disk usage. If the disk space continues to be used, the system will attempt to clear up old log files. This alarm means that the disk usage is nearing the upper limit on disk usage. If the disk space continues to be used, the system will attempt to clear up old log files. DAP is not responding to a poll message from the OMC. If alarm does not clear, call CRT. EMPTY
Comments & Notes
30010
Exceeds upper limit disk usage
EMPTY
OMC
EMPTY
Old log files are removed.
Critical/Clea r
EMPTY
EMPTY
R N C
U EMPTY
30010
Exceeds upper limit disk usage
EMPTY
OMC
EMPTY
No log files are removed
Critical/Clea r
EMPTY
EMPTY
R N C
U EMPTY
30011
Exceeds lower limit disk usage
EMPTY
OMC
EMPTY
Old log files are removed.
Major/Clear
EMPTY
EMPTY
R N C
U EMPTY
30011
Exceeds lower limit disk usage
EMPTY
OMC
EMPTY
No log files removed
Major/Clear
EMPTY
EMPTY
R N C
U EMPTY
30015
DAP poll timeout
EMPTY
OMC
EMPTY
DAP: <dap_name> failed to respond to poll by OMC Swap space used on MMI processor: <mem_pct>%. Swap space problem on MMI processor clear.
Critical/Clea r
EMPTY
EMPTY
R N C
U EMPTY
30016
System Self Audit
EMPTY
OMC
EMPTY
Warning
EMPTY
EMPTY
R N
U EMPTY
30016
System Self Audit
EMPTY
OMC
EMPTY
Clear
EMPTY
EMPTY
EMPTY
C N
U EMPTY
OMC-R-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Relate d State Change s
Remedy
R e p o r t &
O u t a g e
qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent qualityOfSer viceFailureE vent
30016
System Self Audit
EMPTY
OMC
EMPTY
30016
System Self Audit
EMPTY
OMC
EMPTY
30016
System Self Audit
EMPTY
OMC
EMPTY
30016
System Self Audit
EMPTY
OMC
EMPTY
30016
System Self Audit
EMPTY
OMC
EMPTY
Hung tty_rlogin found on MMI processor. Hung PAD process found on MMI processor. Hung process tty_rlogin on MMI processor clear Hung process PAD on MMI processor clear. SA: SYSTEM: Disk hardware problem. MMI: Disk hardware problem. SA: Found in file %s\n%s %s
Warning
EMPTY
EMPTY
EMPTY
Y C / l N e a r R N
Comments & Notes
U EMPTY
Warning
EMPTY
EMPTY
EMPTY
R N
U EMPTY
Clear
EMPTY
EMPTY
EMPTY
C N
U EMPTY
Clear
EMPTY
EMPTY
EMPTY
C N
U EMPTY
Warning
EMPTY
EMPTY
EMPTY
R N
U EMPTY
30016
System Self Audit
EMPTY
OMC
EMPTY
Warning
EMPTY
EMPTY
EMPTY
R N
U EMPTY
30016
System Self Audit
EMPTY
OMC
EMPTY
Warning
EMPTY
EMPTY
EMPTY
R N
30016
System Self Audit
EMPTY
OMC
EMPTY
SA: Found in file %s\nINFORMIXOnLine Stopped. SA: Found in file /var/adm/messages \n%s at %s
Warning
EMPTY
EMPTY
EMPTY
R N
30016
System Self Audit
EMPTY
OMC
EMPTY
Warning
EMPTY
EMPTY
EMPTY
R N
30022
Primary Db Backup Deficient
EMPTY
MSO
<mso_id >
Primary database has not been backed up since mm/dd/yyyy hh:mm:ss
Minor
EMPTY
EMPTY
30022
EMPTY
MSO
<mso_id >
Primary database last backup time is unknown
Minor
EMPTY
EMPTY
The MSO's database backup is delinquent. Perform Informix backup as soon as possible. After backup is successfully completed, the alarm will no longer occur. Until then, the alarm will be generated hourly. The MSO's database's last backup time could not be calculated. Ensure that the file .last_backup is existing under the directory /usr/gsm/ne_data/dbroot.
R N
U In the Alarm Code Text, 3 strings are File name, Informix error code, Error brief description U In the Alarm Code Text, the string is the file name U In the Alarm Code Text, 2 strings are garbage string, time U EMPTY
R N
U EMPTY
October 30, 2008
OMC-R-3

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
30022
EMPTY
URB_DA TABASE
Primary database has not been backed up since mm/dd/yyyy hh:mm:ss
Minor
EMPTY
EMPTY
30022
EMPTY
URB_DA TABASE
Primary database last backup time is unknown
Minor
EMPTY
EMPTY
30101
Site in ISO
EMPTY
OMC
EMPTY
<NE Inst of Site>
Critical/Clea r
EMPTY
EMPTY
30000
downloadFailed
EMPTY
BSC
EMPTY
<Failure reason> <load> <release>.<version >.<subversion>.
Minor
EMPTY
EMPTY
30000
downloadFailed
EMPTY
EBTS
EMPTY
Minor
EMPTY
EMPTY
30000
downloadFailed
EMPTY
TDAP
EMPTY
30000
downloadFailed
EMPTY
RXCDR
EMPTY
<Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>.
Minor
EMPTY
EMPTY
Minor
EMPTY
EMPTY
The MSO's database backup is delinquent. Perform Informix backup as soon as possible. After backup is successfully completed, the alarm will no longer occur. Until then, the alarm will be generated hourly. The MSO's database's last backup time could not be calculated. Ensure that the file .last_backup is existing under the directory /usr/gsm/ne_data/dbroot. Verify whether the site has links towards all the DAPs if the severity is CRITICAL. No action is required if it is CLEAR. If "Booloading disabled for this NE" then Go to NE Nodes in the MMI and enable NE. If "Error reading timeout configuration data" then call CRT to check for file $SYS_CONFIG/bl_timeouts. If "Unable to access object database" then Check NE specific directory look for software load directory. If "Download aborted" then Operator just aborted download. If "Downloader configuration error" then Verify that standard omcadmin environment is being used. If "NE clears call in ROM" then Virtual circuit was cleared by NE or by the network while download was in progress. call CRT
Y C / l N e a r R N
Comments & Notes
U EMPTY
R N
U EMPTY
R N C
U EMPTY
R N
R N
R N
U The 'Failure reason' can be "Too many retries in protocol" or many more reasons U The 'Failure reason' can be "Too many retries in protocol" or many more reasons U EMPTY
R N
30000
downloadFailed
EMPTY
MDG
EMPTY
<Failure reason> <load> -
Minor
EMPTY
EMPTY
R N
U The 'Failure reason' can be "Too many retries in protocol" or many more reasons U The 'Failure reason' can be
OMC-R-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r <release>.<version >.<subversion>.
Comments & Notes
30000
downloadFailed
EMPTY
APD
EMPTY
30000
downloadFailed
EMPTY
ISG
EMPTY
30000
downloadFailed
EMPTY
IHLR
EMPTY
30000
downloadFailed
EMPTY
IDAC
EMPTY
30000
downloadFailed
EMPTY
MDG4
EMPTY
30000
downloadFailed
EMPTY
SSC
EMPTY
30000
downloadFailed
EMPTY
ICP
EMPTY
30000
downloadFailed
EMPTY
HADAP
EMPTY
processingF
30002
filexferFailed
EMPTY
BSC
EMPTY
<Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure
Minor
EMPTY
EMPTY
R N
"Too many retries in protocol" if FR based MDG or many more reasons U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
N EMPTY
Minor
EMPTY
EMPTY
R N
N Applicable only for ATCA ICP
Minor
EMPTY
EMPTY
R N
N Applicable only for ATCA HADAP
Minor
EMPTY
EMPTY
Call CRT
R N
U EMPTY
October 30, 2008
OMC-R-5

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure
Comments & Notes
30002
filexferFailed
EMPTY
XCDR
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
EBTS
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
MDG
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
IHLR
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
DAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
OMC-R-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type>
Comments & Notes
30002
filexferFailed
EMPTY
APD
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
ISG
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
IDAC
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
ICP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
OMC-R-7

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 =
Comments & Notes
30002
filexferFailed
EMPTY
IVPU
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
VSGW
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
XCDR3G
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
OMC-R-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort <Failure Reason><file type> - <filename> where file type is a number: 0 = Unknown 1 = Statistics. Failure reason: 2 = Tftp timeout, 11 = Tftp invalid state, 12 = Tftp unknown error, 13 = Tftp external abort Unexpected <param name> detected; got <version from site>; expected <version from OMC DB>
Comments & Notes
30002
filexferFailed
EMPTY
MDG4
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
30002
filexferFailed
EMPTY
HADAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
60001
Version Mismatch
EMPTY
EMPTY
EMPTY
Critical/Clea r
EMPTY
EMPTY
processingF
60002
No response from
EMPTY
EMPTY
EMPTY
Auto Validation
Warning/Cl
EMPTY
EMPTY
If this alarm is followed by Validation Failure and the OMC DB field is filled with question marks, then verify that this site has a running load built using Genesis. If the OMC DB field has a valid version number, then use NE Management to get the software load versions from the site. Compare these versions with the ones from Genesis. If the site contains the wrong version, then it may have to be reset, else there might be some problems with Genesis. Send some commands to the
R N C
U EMPTY
R N
U EMPTY
October 30, 2008
OMC-R-9

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
ailureEvent
NE
aborted after <n> attempts
ear
60003
Validation Failed
EMPTY
EMPTY
EMPTY
Auto Validation aborted after <n> attempts
Warning/Cl ear
EMPTY
EMPTY
60004
System call mv Failed
EMPTY
EMPTY
EMPTY
40000
bgdownloadFailed
EMPTY
BSC
EMPTY
OMC ERROR - can not move standby load directory to running <Failure reason> <load> <release>.<version >.<subversion>.
Major
EMPTY
EMPTY
Minor
EMPTY
EMPTY
40000
bgdownloadFailed
EMPTY
EBTS
EMPTY
Minor
EMPTY
EMPTY
40000
bgdownloadFailed
EMPTY
TDAP
EMPTY
40000
bgdownloadFailed
EMPTY
RXCDR
EMPTY
<Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>.
Minor
EMPTY
EMPTY
Minor
EMPTY
EMPTY
site using NE Management. If the link is up and the NE does not respond, then there might be some configuration problems or the NE is down. Verify that DTE address setup for this site is correct. If Version Mismatch alarms are followed by this one, then verify that this site has a running load built using Genesis. If that is not the case, then a more serious problem is affecting the AutoValidation process. Unix system call failed to move all files from standby directory into running directory If "Booloading disabled for this NE" then Go to NE Nodes in the MMI and enable NE. If "Error reading timeout configuration data" then call CRT to check for file $SYS_CONFIG/bl_timeouts. If "Unable to access object database" then Check NE specific directory look for software load directory. If "Download aborted" then Operator just aborted download. If "Downloader configuration error" then Verify that standard omcadmin environment is being used. If "NE clears call in ROM" then Virtual circuit was cleared by NE or by the network while download was in progress. call CRT
Y C / l N e a r C
Comments & Notes
R N C
U EMPTY
R N
U EMPTY
R N
R N
R N
U The 'Failure reason' can be "Too many retries in protocol" or many more reasons U The 'Failure reason' can be "Too many retries in protocol" or many more reasons U EMPTY
R N
40000
bgdownloadFailed
EMPTY
MDG
EMPTY
<Failure reason> <load> -
Minor
EMPTY
EMPTY
R N
U The 'Failure reason' can be "Too many retries in protocol" or many more reasons U The 'Failure reason' can be
OMC-R-10
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r <release>.<version >.<subversion>.
Comments & Notes
40000
bgdownloadFailed
EMPTY
APD
EMPTY
40000
bgdownloadFailed
EMPTY
ISG
EMPTY
40000
bgdownloadFailed
EMPTY
ICP
EMPTY
40000
bgdownloadFailed
EMPTY
IVPU
EMPTY
40000
bgdownloadFailed
EMPTY
VSGW
EMPTY
40000
bgdownloadFailed
EMPTY
XCDR3G
EMPTY
40000
bgdownloadFailed
EMPTY
IHLR
EMPTY
40000
bgdownloadFailed
EMPTY
IDAC
EMPTY
processingF
40000
bgdownloadFailed
EMPTY
MDG4
EMPTY
<Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason>
Minor
EMPTY
EMPTY
R N
"Too many retries in protocol" if FR based MDG or many more reasons U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
OMC-R-11

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification:
Comments & Notes
40000
bgdownloadFailed
EMPTY
HADAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40000
bgdownloadFailed
EMPTY
SSC
EMPTY
Minor
EMPTY
EMPTY
R N
N EMPTY
40001
loadVerificationFail ed
EMPTY
BSC
EMPTY
Minor
EMPTY
EMPTY
The background load on the NE is somehow corrupted. The remedy is to initiate a background download again and try a switch again or to initiate a foreground download.
R N
U EMPTY
40001
EMPTY
EBTS
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40001
EMPTY
DAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
OMC-R-12
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification:
Comments & Notes
40001
EMPTY
RXCDR
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40001
EMPTY
MDG
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40001
EMPTY
APD
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
OMC-R-13

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification:
Comments & Notes
40001
EMPTY
ISG
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40001
EMPTY
IVPU
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40001
EMPTY
ICP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
processingF
40001
loadVerificationFail
EMPTY
VSGW
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
OMC-R-14
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent ed Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched
Comments & Notes
40001
EMPTY
XCDR3G
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40001
EMPTY
IHLR
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40001
EMPTY
IDAC
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
OMC-R-15

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched and aborted checksum is mismatched Load verification: Load mismatched. Load verification: Error in link. Load verification: Load mismatched and aborted currDBVersion mismatch Load verification: Load mismatched
Comments & Notes
40001
EMPTY
MDG4
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40001
EMPTY
HADAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40001
EMPTY
SSC
EMPTY
Minor
EMPTY
EMPTY
R N
N EMPTY
OMC-R-16
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r and aborted checksum is mismatched Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed.
Comments & Notes
processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF
40002
switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchScheduleFail ed switchFailed
EMPTY
BSC
EMPTY
Minor
EMPTY
EMPTY
40002
EMPTY
EBTS
EMPTY
Minor
EMPTY
EMPTY
40002
EMPTY
RXCDR
EMPTY
Minor
EMPTY
EMPTY
40002
EMPTY
VSGW
EMPTY
Minor
EMPTY
EMPTY
40002
EMPTY
ICP
EMPTY
Minor
EMPTY
EMPTY
40002
EMPTY
IVPU
EMPTY
Minor
EMPTY
EMPTY
An X.25 circuit between the OMC and the NE is likely to be down. Check the event logs or an existing open event window to see if a linkFailureEvent was received for that NE recently. If so wait for some time and see if a CLEAR of this event is generated. Try pressing SWITCH again in the background download window. If the problem persists, abort the session and either reinitiate the background download or initiate a foreground download.
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
40002
EMPTY
XCDR3G
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40002
EMPTY
MDG4
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40002
EMPTY
HADAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40002
EMPTY
SSC
EMPTY
Minor
EMPTY
EMPTY
R N
N EMPTY
40002
EMPTY
IHLR
EMPTY
Minor
EMPTY
EMPTY
R N
N Applicable only for ATCA IHLR N Applicable only for ATCA ISG U EMPTY
40002
EMPTY
ISG
EMPTY
Minor
EMPTY
EMPTY
R N
40003
EMPTY
BSC
EMPTY
Minor
EMPTY
EMPTY
40003
switchFailed
EMPTY
RXCDR
EMPTY
Minor
EMPTY
EMPTY
Abort the background download session. Perform a foreground download to the NE. If the foreground download is not successful, call the CRT.
R N
R N
U EMPTY
40003
switchFailed
EMPTY
EBTS
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
OMC-R-17

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent 40003 switchFailed EMPTY IVPU EMPTY Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Revert PFTP not initiated. Revert SNMP set failed. Revert PFTP failed. Revert Ram mode transition failed. Commit failed <Failure reason> <load> <release>.<version >.<subversion>.
Comments & Notes
Minor
EMPTY
EMPTY
R N
U EMPTY
40003
switchFailed
EMPTY
ICP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40003
switchFailed
EMPTY
VSGW
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40003
switchFailed
EMPTY
XCDR3G
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40003
switchFailed
EMPTY
MDG4
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40003
switchFailed
EMPTY
HADAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40003
switchFailed
EMPTY
SSC
EMPTY
Minor
EMPTY
EMPTY
R N
N EMPTY
40003
switchFailed
EMPTY
IHLR
EMPTY
Minor
EMPTY
EMPTY
R N
N Applicable only for ATCA IHLR N Applicable only for ATCA ISG U EMPTY
40003
switchFailed
EMPTY
ISG
EMPTY
Minor
EMPTY
EMPTY
R N
40004
revertFailed
EMPTY
EMPTY
EMPTY
Minor
EMPTY
EMPTY
EMPTY
R N
40005 40006
commitFailed bgResetdownloadF ailed
EMPTY EMPTY
EMPTY BSC
EMPTY EMPTY
Minor Minor
EMPTY EMPTY
EMPTY EMPTY
EMPTY If "Booloading disabled for this NE" then Go to NE Nodes in the MMI and enable NE. If "Error reading timeout configuration data" then call CRT to check for file $SYS_CONFIG/bl_timeouts. If "Unable to access object database" then Check NE specific directory look for
R N R N
U EMPTY U The 'Failure reason' can be "Too many retries in protocol" or many more reasons U The 'Failure reason' can be "Too many
40006
bgResetdownloadF ailed
EMPTY
EBTS
EMPTY
<Failure reason> <load> <release>.<version
Minor
EMPTY
EMPTY
R N
OMC-R-18
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r >.<subversion>. software load directory. If "Download aborted" then Operator just aborted download. If "Downloader configuration error" then Verify that standard omcadmin environment is being used. If "NE clears call in ROM" then Virtual circuit was cleared by NE or by the network while download was in progress. call CRT
Comments & Notes
40006
EMPTY
RXCDR
EMPTY
Minor
EMPTY
EMPTY
R N
40006
EMPTY
MDG
EMPTY
Minor
EMPTY
EMPTY
R N
40006
EMPTY
APD
EMPTY
40006
EMPTY
IVPU
EMPTY
40006
EMPTY
VSGW
EMPTY
40006
EMPTY
XCDR3G
EMPTY
40006
EMPTY
ISG
EMPTY
40006
EMPTY
IDAC
EMPTY
<Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. <Failure reason> <load> <release>.<version
Minor
EMPTY
EMPTY
R N
retries in protocol" or many more reasons U The 'Failure reason' can be "Too many retries in protocol" or many more reasons U The 'Failure reason' can be "Too many retries in protocol" if FR based MDG or many more reasons U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
OMC-R-19

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r >.<subversion>. <Failure reason> <load> <release>.<version >.<subversion>. Bypass Failed Bypass Failed Bypass Failed Bypass Failed Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set
Comments & Notes
40006
EMPTY
MDG4
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF
40007 40007 40007 40007 40008
bypassFailed bypassFailed bypassFailed bypassFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched
BSC RXCDR ICP IVPU BSC
Minor Minor Minor Minor Minor
A file system error occurred. Call CRT for assistance.
R N R N R N R N
U EMPTY U EMPTY U EMPTY U EMPTY U EMPTY
40008
EMPTY
EBTS
EMPTY
Minor
EMPTY
EMPTY
40008
EMPTY
TDAP
EMPTY
Minor
EMPTY
EMPTY
40008
EMPTY
RXCDR
EMPTY
Minor
EMPTY
EMPTY
40008
EMPTY
MDG
EMPTY
Minor
EMPTY
EMPTY
40008
EMPTY
APD
EMPTY
Minor
EMPTY
EMPTY
An X.25 circuit between the OMC and the NE is likely to be down. Check the event logs or an existing open event window to see if a linkFailureEvent was received for that NE recently. If so wait for some time and see if a CLEAR of this event is generated. Try pressing SWITCH again in the background download window. If the problem persists, abort the session and either reinitiate the background download or initiate a foreground download.
R N
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
R N
U EMPTY
40008
EMPTY
ICP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40008
EMPTY
IVPU
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40008
EMPTY
VSGW
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40008
EMPTY
XCDR3G
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40008
EMPTY
IHLR
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
OMC-R-20
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent 40008 uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchSched uleFailed onlineSwitchFailed EMPTY IDAC EMPTY Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch SNMP Set Failed. Switch PFTP not initiated. Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode
Comments & Notes
Minor
EMPTY
EMPTY
R N
U EMPTY
40008
EMPTY
MDG4
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40008
EMPTY
HADAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40008
EMPTY
SSC
EMPTY
Minor
EMPTY
EMPTY
R N
N EMPTY
40008
EMPTY
ISG
EMPTY
Minor
EMPTY
EMPTY
R N
N EMPTY
40009
EMPTY
BSC
EMPTY
Minor
EMPTY
EMPTY
40009
onlineSwitchFailed
EMPTY
EBTS
EMPTY
Minor
EMPTY
EMPTY
Abort the background download session. Perform a foreground download to the NE. If the foreground download is not successful, call the CRT.
R N
U EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
TDAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
RXCDR
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
MDG
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
APD
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
IHLR
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
ICP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
IVPU
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
VSGW
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
October 30, 2008
OMC-R-21

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent 40009 onlineSwitchFailed EMPTY XCDR3G EMPTY transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed BSC failed to contact OMC in ROM, BGDL switch over still in progress. Check BSC to OMC connectivity. BSC failed to contact OMC in RAM, OMC polling BSC for current running version every 2 mins. Check BSC to OMC connectivity or click Abort. Minor EMPTY EMPTY R N
Comments & Notes
U EMPTY
40009
onlineSwitchFailed
EMPTY
IDAC
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
MDG4
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
HADAP
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40009
onlineSwitchFailed
EMPTY
SSC
EMPTY
Minor
EMPTY
EMPTY
R N
N EMPTY
40009
onlineSwitchFailed
EMPTY
ISG
EMPTY
Minor
EMPTY
EMPTY
R N
N EMPTY
40011
switchBSCtimeout
EMPTY
BSC
EMPTY
Minor
EMPTY
EMPTY
bsc has problems contacting omc during reinit bgdl switch. After generating this alarm, omc will set a 30 mins timer waiting for a clear of x25CircuitDown alarm. bsc has problems contacting omc during reinit bgdl switch. Switch will fail or success according to polling response. Abort button is enabled. In case of snmp link failure, omc keeps polling. Once operator clicks abort, BSC will move out of switch polling state and operator is allowed to do FGDL or BGDL again. EMPTY Try pressing SWITCH again in the background download window. If the problem persists, abort the session and either reinitiate the background download or initiate a foreground download.
R N
U EMPTY
40011
switchBSCtimeout
EMPTY
BSC
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
40012 40013
dlSessionOverLimit rupSwitchSchedule Failed
EMPTY EMPTY
OMC iVPU
EMPTY EMPTY
EMPTY Switch SNMP Set Failed. RUP caUpgradestart Failure. Load verification: Error in link Switch SNMP Set Failed. RUP
Minor Minor
EMPTY EMPTY
EMPTY EMPTY
R N R N
U EMPTY U EMPTY
40013
rupSwitchSchedule Failed
EMPTY
MDG4
EMPTY
Minor
EMPTY
EMPTY
R N
U EMPTY
OMC-R-22
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r caUpgradestart Failure. Load verification: Error in link Switch PFTP failed. Switch Ram mode transition failed Switch PFTP failed. Switch Ram mode transition failed EMPTY No CA Response or BSS Internal Protocol Error or BSS State Bad <Failure reason>
Comments & Notes
processingF ailureEvent processingF ailureEvent processingF ailureEvent processingF ailureEvent
40014
rupSwitchFailed
EMPTY
iVPU
EMPTY
Minor
EMPTY
EMPTY
40014
rupSwitchFailed
EMPTY
MDG4
EMPTY
Minor
EMPTY
EMPTY
30005 30006
BSSRespTimeout BSSErrorState
EMPTY EMPTY
EMPTY EMPTY
EMPTY EMPTY
Critical/Clea r Critical/Clea r
EMPTY EMPTY
EMPTY EMPTY
Abort the background download session. Perform a foreground download to the NE. If the foreground download is not successful, call the CRT. EMPTY EMPTY
R N
U EMPTY
R N
U EMPTY
R N C R N C
U EMPTY U EMPTY
40100
Backhaul negotiation failed
EMPTY
EBTS
EMPTY
Minor
EMPTY
EMPTY
EMPTY
R N
30019
ntpDaemonDown
EMPTY
OMC
EMPTY
OMC NTP Daemon DOWN
Critical
EMPTY
EMPTY
30019
ntpDaemonDown
EMPTY
OMC
EMPTY
OMC NTP Daemon UP
Clear
EMPTY
EMPTY
30020
timeSyncFailure
EMPTY
OMC
EMPTY
OMC time not synchronized (check connection to NTP server)
Critical
EMPTY
EMPTY
30020
timeSyncFailure
EMPTY
OMC
EMPTY
OMC time synchronized
Clear
EMPTY
EMPTY
OMC NTP Daemon DOWN. Check OMC status for NTP Daemon and if it is down contact CRT for assistance OMC NTP Daemon DOWN. Check OMC status for NTP Daemon and if it is down contact CRT for assistance OMC NTP Daemon DOWN could be one of the for this problem. Check NTP Server connection status and if it is not up contact CRT for assistance OMC NTP Daemon DOWN could be one of the for this problem. Check NTP Server connection status and if it is not up contact CRT for assistance
R N
U The 'Failure reason' can be "NE clears call in RAM" or "Protocol timed out" or "Invalid message received by protocol" or many more reasons. U EMPTY
C N
U EMPTY
R N
U EMPTY
C N
U EMPTY
October 30, 2008
OMC-R-23

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
Alarm Code Text
Remedy
R e p o r t &
O u t a g e
40015
backupAborted
EMPTY
OMC
EMPTY
OMC-R backup failed for <OMC-R name>
Major
EMPTY
EMPTY
14500 1
Exceeds upper limit syslog usage
EMPTY
OMC
EMPTY
Current usage at <%> of capacity
Major/Clear
EMPTY
EMPTY
14500 2
Exceeds upper limit CPU usage
EMPTY
OMC
EMPTY
Major/Clear
EMPTY
EMPTY
14500 3
Exceeds upper limit Virtual Memory usage
EMPTY
OMC
EMPTY
Major/Clear
EMPTY
EMPTY
14500 4
Exceeds upper limit Swap space usage
EMPTY
OMC
EMPTY
Major/Clear
EMPTY
EMPTY
14500 5
Exceeds upper limit dbSpace usage
EMPTY
OMC
EMPTY
Current usage of <dbspace> at <%> of capacity
Major/Clear
EMPTY
EMPTY
14500 6
Exceeds upper limit disk space usage
EMPTY
OMC
EMPTY
Major/Clear
EMPTY
EMPTY
qualityOfSer viceFailureE vent processingF
14500 8 14500
An OMC Subsystem Has not Restarted Attempted User
EMPTY
OMC
EMPTY
<process name> attempt 3. <User Name>
Critical
EMPTY
EMPTY
One alarm is generated for each failed OMC-R back up.Log on to the backup server console for additional failure information. Generated when syslog size reaches 80% or configurable value of total capacity. A Clear alarm shall be generated if usage comes down by 10%. Generated when CPU Usage reaches 70% or configurable value of total capacity. A Clear alarm shall be generated if usage comes down by 10% Generated when virtual memory usage reaches 80% or configurable value of total capacity. A Clear alarm shall be generated if usage comes down by 10%. Generated when swap space is less than 80% or configurable value of total capacity. A Clear alarm shall be generated if usage comes down by 10%. Generated when db space usage crosses the configured threshold. A Clear alarm shall be generated if usage comes down by 10%. Generated when disk space usage crosses the configured threshold. A Clear alarm shall be generated if usagecomes down by 10%. Stop/Start the omc.
Y C / l N e a r C N
Comments & Notes
N EMPTY
R N
N EMPTY
R N
N EMPTY
R N
N EMPTY
R N
N EMPTY
R N
N EMPTY
R N
N EMPTY
R Y
N EMPTY
EMPTY
OMC
EMPTY
Critical
EMPTY
EMPTY
Investigate whether this is
R Y
N EMPTY
OMC-R-24
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

Alarm Code Text
Severity
Related Alarms
Remedy
R e p o r t &
O u t a g e
Y C / l N e a r ailureEvent 9 Login Failed <hostname>. hacking attempt or a genuine user mistake
Comments & Notes
October 30, 2008
OMC-R-25
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From Stat e
To Stat e
Relat ed Alarm s
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 1 0 2 1
Clear GC session
1.3.6.1.4.1.161 .3.3.10.5.9.1.1. 1.2 1.3.6.1.4.1.161 .3.3.10.5.9.1.1. 1.3
URB_DATA BASE
EMPTY
L-E-A
L-D-Idl
EMPTY
EMPTY
OMC going down
S t a t u s Y U
Cleared GC DB tables for a session
OMC Urban OMC State down
URB_OMC _STATE
U-E-A
U-DIdl
EMPTY
EMPTY
OMC going down
N U
OMC Urban OMC State down
1.3.6.1.4.1.161 .3.3.10.5.9.1.1. 1.3
URB_OMC _STATE
I-I-I
U-DIdl
EMPTY
EMPTY
OMC going down
Y U
OMC Urban OMC State up
1.3.6.1.4.1.161 .3.3.10.5.9.1.1. 1.3
URB_OMC _STATE
U-DIdl U-EImp I-I-I
U-E-A
EMPTY
EMPTY
OMC coming up
Y U
OMC Urban OMC State up
1.3.6.1.4.1.161 .3.3.10.5.9.1.1. 1.3
URB_OMC _STATE
U-E-A
EMPTY
EMPTY
OMC coming up
Y U
OMC Urban OMC State impaired
1.3.6.1.4.1.161 .3.3.10.5.9.1.1. 1.3
URB_OMC _STATE
U-E-A
U-EImp
EMPTY
EMPTY
EMPTY
N U
OMC Urban OMC State impaired
1.3.6.1.4.1.161 .3.3.10.5.9.1.1. 1.3
URB_OMC _STATE
I-I-I
U-EImp
EMPTY
EMPTY
EMPTY
N U
OMC Urban MSO Link up
1.3.6.1.4.1.161 .3.3.10.5.9.1.1. 1.4
URB_MSO _LINK
1-6
U-DIdl
U-E-A
EMPTY
EMPTY
EMPTY
N U
URB_OMC_STATE - MSO <mso_id> URB_OMC_STATE 0 - <time-stamp> From: (Unlocked, Enabled, Active) To: (Unlocked, Enabled, Idle) - OMC Urban OMC state down URB_OMC_STATE - MSO <mso_id> URB_OMC_STATE 0 - <time-stamp> From: (Initial, Initial, Initial) To: (Unlocked, Disabled, Idle) - [2] OMC Urban OMC state down URB_OMC_STATE - MSO <mso_id> URB_OMC_STATE 0 - <time-stamp> From: (Unlocked, Enabled, Idle/Impaired) To: (Unlocked, Enabled, Active) - OMC Urban OMC state up URB_OMC_STATE - MSO <mso_id> URB_OMC_STATE 0 - <time-stamp> From: (Initial, Initial, Initial) To: (Unlocked, Enabled, Active) - [2] OMC Urban OMC state up URB_OMC_STATE - MSO <mso_id> URB_OMC_STATE 0 - <time-stamp> From: (Unlocked, Enabled, Idle/Impaired) To: (Unlocked, Enabled, Active) - OMC Urban OMC state impaired URB_OMC_STATE - MSO <mso_id> URB_OMC_STATE 0 - <time-stamp> From: (Initial, Initial, Initial) To: (Unlocked, Enabled, Impaired) - OMC Urban OMC state impaired URB_MSO_LINK - MSO <mso_id> URB_MSO_LINK <link_no - <time-stamp> From: (Unlocked, Disabled, Idle) To:
OMC-R-26
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From Stat e
To Stat e
Relat ed Alarm s
Event Description
O u t a g e ( Y / N )
Comments & Notes
OMC Urban MSO Link down
1.3.6.1.4.1.161 .3.3.10.5.9.1.1. 1.4
URB_MSO _LINK
1-6
U-E-A
U-DIdl
EMPTY
EMPTY
EMPTY
N U
2 1
NODE RESTORED FULL FUNCTIONA LITY
EMPTY
OMC
EMPTY
U-DIdl
U-E-A
EMPTY
EMPTY
EMPTY
N U
2 1
EMPTY
OMC
EMPTY
U-EImp
U-E-A
EMPTY
EMPTY
EMPTY
N U
2 2
NODE LOST PARTIAL FUNCTIONA LITY
EMPTY
OMC
EMPTY
U-E-A
U-EImp
EMPTY
EMPTY
EMPTY
N U
2 3
NODE LOST FULL FUNCTIONA LITY
EMPTY
OMC
EMPTY
U-E-A
U-DIdl
EMPTY
EMPTY
EMPTY
N U
2 3
EMPTY
OMC
EMPTY
U-EImp
U-DIdl
EMPTY
EMPTY
EMPTY
N U
(Unlocked, Enabled, Active) - OMC Urban MSO Link up URB_MSO_LINK - MSO <mso_id> URB_MSO_LINK <link_no - <time-stamp> From: (Unlocked, Disabled, Idle) To: (Unlocked, Enabled, Active) - OMC Urban MSO Link down This event is raised when the OMC detects that DAP/logical HADAP/Horizontal iVPU/IDAC/logical HAIHLR has transitioned to U-E-A from U-D-Idl thru the scheduled polling. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC detects that DAP/logical HADAP/Horizontal iVPU/IDAC/logical HAIHLR has transitioned to U-E-A from U-E-Imp thru the scheduled polling. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC detects that DAP/logical HADAP/Horizontal IVPU/IDAC/logical HAIHLR has transitioned to U-E-Imp from U-E-A thru the scheduled polling. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC detects that DAP/logical HAIHLR/Horizontal IVPU/IDAC/logical HAIHLR has transitioned to U-D-Idl from U-E-A thru the scheduled polling. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC detects that DAP/logical HADAP/Horizontal IVPU/IDAC/logical HAIHLR has transitioned to U-D-Idl from U-E-Imp thru the scheduled
October 30, 2008
OMC-R-27

State Changes
R e a s o n C o d e
Release SR17.0
To Stat e Related State Changes Relat ed Alarm s Event Description
O u t a g e ( Y / N ) C h a n g e S t a t u s polling. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC detects that DAP/logical HADAP/Horizontal iVPU/IDAC/logical HAIHLR has transitioned to U-E-Imp from U-D-Idl thru the scheduled polling. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC detects that IDAC_BOX has transitioned to U-E-Imp from L-D-Idl thru the scheduled polling. This event is raised when the OMC detects that IDAC_BOX has transitioned to U-E-A from L-E-Idl thru the scheduled polling. This event is raised when the OMC detects that IDAC_BOX has transitioned to L-E-Idl from U-E-Imp thru the scheduled polling. This event is raised when the OMC detects that IDAC_BOX has transitioned to L-E-Idl from U-D-Idl thru the scheduled polling. This event is raised when the OMC detects that IDAC_BOX has transitioned to L-D-Idl from L-E-Idl thru the scheduled polling. This event is raised when the OMC able to reach DAP/logical HADAP/Horizontal IVPU/IDAC/logical HAIHLR and NE is in UEA state. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC able to reach DAP/logical HADAP/Horizontal IVPU/IDAC/logical HAIHLR and NE is in UDIdl state. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC able to
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From Stat e
Comments & Notes
2 4
NODE RESTORED PARTIAL FUNCTIONA LITY
EMPTY
OMC
EMPTY
U-DIdl
U-EImp
EMPTY
EMPTY
EMPTY
N U
2 3
2 5 2 5 2 5 2 5 2 1
NODE LOST FULL FUNCTIONA LITY NODE LOCKED NODE LOCKED NODE LOCKED NODE LOCKED NODE RESTORED FULL FUNCTIONA LITY
EMPTY
OMC
EMPTY
L-D-Idl
U-DIdl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-EImp U-DIdl L-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-D-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
UdUd-Ud
U-E-A
EMPTY
EMPTY
EMPTY
N M
2 3
EMPTY
OMC
EMPTY
UdUd-Ud
U-DIdl
EMPTY
EMPTY
EMPTY
N M
esmrStateCh
NODE
EMPTY
OMC
EMPTY
Ud-
U-E-
EMPTY
EMPTY
EMPTY
N M
OMC-R-28
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From Stat e
To Stat e
Relat ed Alarm s
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
RESTORED PARTIAL FUNCTIONA LITY
Ud-Ud
Imp
2 5 2 5 2 6
NODE LOCKED NODE LOCKED NODE STATUS UNKNOWN
EMPTY EMPTY EMPTY
OMC OMC OMC
EMPTY EMPTY EMPTY
UdUd-Ud UdUd-Ud U-E-A
L-E-Idl L-D-Idl UdUd-Ud
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
N U N U N U
2 6
NODE STATUS UNKNOWN
EMPTY
OMC
EMPTY
U-DIdl
UdUd-Ud
EMPTY
EMPTY
EMPTY
N U
2 6
NODE STATUS UNKNOWN
EMPTY
OMC
EMPTY
U-EImp
UdUd-Ud
EMPTY
EMPTY
EMPTY
N U
2 6 2 6 5 5 5
NODE STATUS UNKNOWN NODE STATUS UNKNOWN NODE LOCKED NODE LOCKED NODE LOCKED
EMPTY
OMC
EMPTY
L-E-Idl
UdUd-Ud UdUd-Ud L-D-Idl L-D-Idl L-D-Idl
EMPTY
EMPTY
EMPTY
N U
reach DAP/logical HADAP/Horizontal IVPU/IDAC/logical HAIHLR and NE is in UEImp state. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC able to reach IDAC and IDAC is in LEIdl state. This event is raised when the OMC able to reach IDAC and IDAC is in LDIdl state. This event is raised when the OMC is not able to reach DAP/logical HADAP/Horizontal IVPU/IDAC/logical HAIHLR and NE was in UEA state. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC is not able to reach DAP/logical HADAP/Horizontal IVPU/IDAC/logical HAIHLR and NE was in UDIdl state. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC is not able to reach DAP/logical HADAP/Horizontal IVPU/IDAC/logical HAIHLR and NE was in UEImp state. In MMI Event Display, for HADAPs/HAIHLRs the NE name displayed can be any of the two Physical HA Nodes but the States & OMC Text represent the rolled up status of logical HADAP/HAIHLR. This event is raised when the OMC is not able to reach IDAC and NE was in LEIdl state. This event is raised when the OMC is not able to reach IDAC and NE was in LDIdl state. This event is raised when OMC able to reach VSGW and VSGW is in LDIdl state This event is raised when OMC able to reach VSGW and VSGW is in LDIdl state This event is raised when OMC able to reach VSGW and VSGW is in LDIdl state
EMPTY
OMC
EMPTY
L-D-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY EMPTY EMPTY
OMC OMC OMC
EMPTY EMPTY EMPTY
U-DIdl S-E-A S-EImp
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
N U N U N U
October 30, 2008
OMC-R-29

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From Stat e
Comments & Notes
NODE LOCKED NODE LOCKED NODE LOCKED NODE LOCKED NODE LOST FULL FUNCTIONA LITY NODE LOST FULL FUNCTIONA LITY NODE LOST FULL FUNCTIONA LITY NODE LOST FULL FUNCTIONA LITY NODE LOST FULL FUNCTIONA LITY NODE LOST FULL FUNCTIONA LITY NODE LOST FULL FUNCTIONA LITY NODE LOCKED NODE LOCKED NODE LOCKED NODE LOCKED NODE
EMPTY
OMC
EMPTY
L-E-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
S t a t u s N U
5 5 5 3
OMC OMC OMC OMC
U-EImp U-E-A U-E-Idl U-E-A
L-D-Idl L-D-Idl L-D-Idl U-DIdl
N U N U N U N U
This event is raised when the OMC detects that VSGW has transitioned to L-E-Idl from LD-Idl thru the scheduled polling. This event is raised when OMC able to reach VSGW and VSGW is in LDIdl state This event is raised when OMC able to reach VSGW and VSGW is in LDIdl state This event is raised when OMC able to reach VSGW and VSGW is in LDIdl state This event is raised when OMC able to reach VSGW and VSGW is in UDIdl state
EMPTY
OMC
EMPTY
U-E-Idl
U-DIdl
EMPTY
EMPTY
EMPTY
N U
This event is raised when OMC able to reach VSGW and VSGW is in UDIdl state
EMPTY
OMC
EMPTY
U-EImp
U-DIdl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-D-Idl
U-DIdl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-E-Idl
U-DIdl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-E-A
U-DIdl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-EImp
U-DIdl
EMPTY
EMPTY
EMPTY
N U
5 5 5 5 5
OMC OMC OMC OMC OMC
U-E-A U-E-Idl U-EImp S-E-A S-E-
L-E-Idl L-E-Idl L-E-Idl L-E-Idl L-E-Idl
N U N U N U N U N U
This event is raised when OMC able to reach VSGW and VSGW is in LEIdl state This event is raised when OMC able to reach VSGW and VSGW is in LEIdl state This event is raised when OMC able to reach VSGW and VSGW is in LEIdl state This event is raised when OMC able to reach VSGW and VSGW is in LEIdl state This event is raised when OMC able to reach
OMC-R-30
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From Stat e
To Stat e
Relat ed Alarm s
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh
LOCKED NODE LOCKED NODE LOCKED NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE SHUTTING DOWN NODE
EMPTY
OMC
EMPTY
Imp L-D-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
5 7
EMPTY EMPTY
OMC OMC
EMPTY EMPTY
U-DIdl U-EImp S-E-A
L-E-Idl S-EImp S-EImp S-EImp S-EImp S-EImp S-EImp S-EImp S-E-A
EMPTY EMPTY
EMPTY EMPTY
EMPTY EMPTY
N U N U
VSGW and VSGW is in LEIdl state This event is raised when the OMC detects that VSGW has transitioned to L-D-Idl from LE-Idl thru the scheduled polling. This event is raised when OMC able to reach VSGW and VSGW is in LEIdl state This event is raised when OMC able to reach VSGW and VSGW is in SEImp state This event is raised when the OMC detects that VSGW has transitioned to S-E-A from SE-Imp thru the scheduled polling. This event is raised when OMC able to reach VSGW and VSGW is in SEImp state This event is raised when OMC able to reach VSGW and VSGW is in SEImp state This event is raised when OMC able to reach VSGW and VSGW is in SEImp state This event is raised when OMC able to reach VSGW and VSGW is in SEImp state This event is raised when OMC able to reach VSGW and VSGW is in SEImp state This event is raised when OMC able to reach VSGW and VSGW is in SEA state This event is raised when the OMC detects that VSGW has transitioned to S-E-Imp from S-E-A thru the scheduled polling. This event is raised when OMC able to reach VSGW and VSGW is in SEA state This event is raised when OMC able to reach VSGW and VSGW is in SEA state This event is raised when OMC able to reach VSGW and VSGW is in SEA state This event is raised when OMC able to reach VSGW and VSGW is in SEA state This event is raised when OMC able to reach
EMPTY
OMC
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-DIdl U-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-D-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-EImp U-DIdl U-EImp U-E-Idl
S-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-D-Idl
S-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-E-Idl
S-E-A
EMPTY
EMPTY
EMPTY
N U
October 30, 2008
OMC-R-31

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s VSGW and VSGW is in SEA state
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From Stat e
Comments & Notes
angeEvent esmrStateCh angeEvent 2
SHUTTING DOWN NODE LOST PARTIAL FUNCTIONA LITY NODE LOST PARTIAL FUNCTIONA LITY NODE RESTORED PARTIAL FUNCTIONA LITY NODE RESTORED PARTIAL FUNCTIONA LITY NODE RESTORED PARTIAL FUNCTIONA LITY NODE RESTORED PARTIAL FUNCTIONA LITY NODE RESTORED PARTIAL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED
EMPTY
OMC
EMPTY
U-E-A
U-EImp
EMPTY
EMPTY
EMPTY
N U
This event is raised when OMC able to reach VSGW and VSGW is in UEImp state
EMPTY
OMC
EMPTY
U-E-Idl
U-EImp
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-DIdl
U-EImp
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-EImp
U-EImp
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-E-A
U-EImp
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-D-Idl
U-EImp
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-E-Idl
U-EImp
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-DIdl
U-E-A
EMPTY
EMPTY
EMPTY
N U
This event is raised when OMC able to reach VSGW and VSGW is in UEA state
EMPTY
OMC
EMPTY
U-E-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
This event is raised when the OMC detects that VSGW has transitioned to U-E-Idl from UE-A thru the scheduled polling.
EMPTY
OMC
EMPTY
U-EImp
U-E-A
EMPTY
EMPTY
EMPTY
N U
OMC-R-32
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From Stat e
To Stat e
Relat ed Alarm s
Event Description
O u t a g e ( Y / N )
Comments & Notes
FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA
EMPTY
OMC
EMPTY
S-E-A
U-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-EImp
U-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-D-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-E-Idl
U-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-DIdl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
This event is raised when OMC able to reach VSGW and VSGW is in UEIdl state
EMPTY
OMC
EMPTY
U-EImp
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-E-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-E-A
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
This event is raised when the OMC detects that VSGW has transitioned to U-E-A from UE-Idl thru the scheduled polling.
EMPTY
OMC
EMPTY
L-D-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
October 30, 2008
OMC-R-33

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s This event is raised when OMC able to reach VSGW and VSGW is in UEIdl state
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From Stat e
Comments & Notes
esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent esmrStateCh angeEvent
LITY NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE STATUS UNKNOWN NODE STATUS UNKNOWN NODE STATUS UNKNOWN NODE STATUS UNKNOWN NODE STATUS UNKNOWN NODE STATUS UNKNOWN NODE STATUS UNKNOWN NODE STATUS UNKNOWN NODE RESTORED FULL FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY NODE SHUTTING
EMPTY
OMC
EMPTY
S-E-A
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-EImp
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-E-A
UdUd-Ud UdUd-Ud UdUd-Ud UdUd-Ud UdUd-Ud UdUd-Ud UdUd-Ud UdUd-Ud U-E-A
EMPTY
EMPTY
EMPTY
N U
This event is raised when OMC unable to reach VSGW and VSGW was in UEA state This event is raised when OMC unable to reach VSGW and VSGW was in UEIdl state This event is raised when OMC unable to reach VSGW and VSGW was in SEA state This event is raised when OMC unable to reach VSGW and VSGW was in SEImp state This event is raised when OMC unable to reach VSGW and VSGW was in LDIdl state This event is raised when OMC unable to reach VSGW and VSGW was in LEIdl state This event is raised when OMC unable to reach VSGW and VSGW was in UEImp state This event is raised when OMC unable to reach VSGW and VSGW was in UDIdl state This event is raised when OMC able to reach VSGW and VSGW is in UEA state
EMPTY
OMC
EMPTY
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-E-A
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
S-EImp L-D-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
L-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
U-EImp U-DIdl UdUd-Ud
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
UdUd-Ud
U-E-Idl
EMPTY
EMPTY
EMPTY
N U
EMPTY
OMC
EMPTY
UdUd-Ud
S-E-A
EMPTY
EMPTY
EMPTY
N U
This event is raised when OMC able to reach VSGW and VSGW is in SEA state
OMC-R-34
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From Stat e
To Stat e
Relat ed Alarm s
Event Description
O u t a g e ( Y / N )
Comments & Notes
5 5 4
DOWN NODE SHUTTING DOWN NODE LOCKED NODE LOCKED NODE RESTORED PARTIAL FUNCTIONA LITY NODE LOST FULL FUNCTIONA LITY
EMPTY
OMC
EMPTY
UdUd-Ud UdUd-Ud UdUd-Ud UdUd-Ud
S-EImp L-D-Idl L-E-Idl U-EImp
EMPTY
EMPTY
EMPTY
N U
This event is raised when OMC able to reach VSGW and VSGW is in SEImp state This event is raised when OMC able to reach VSGW and VSGW is in LDIdl state This event is raised when OMC able to reach VSGW and VSGW is in LEIdl state This event is raised when OMC able to reach VSGW and VSGW is in UEImp state
EMPTY EMPTY EMPTY
OMC OMC OMC
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
EMPTY EMPTY EMPTY
N U N U N U
EMPTY
OMC
EMPTY
UdUd-Ud
U-DIdl
EMPTY
EMPTY
EMPTY
N U
October 30, 2008
OMC-R-35
Release SR17.0
__________________________________ Miscellaneous
Event Type
bgdlAbortEvent bgdownloadCompletedEvent bgdownloadFinishedEvent bgdownloadStartedEvent bgdownloadStartTimeoutEvent bgobjectDownloadingEvent bgResetdownloadCompletedEvent bgResetdownloadStartedEvent bgResetobjectDownloadingEvent bypassSucceededEvent commitSucceededEvent dbUpdateEvent distributionEvent distStatusEvent distSVCompleteEvent gttReadyFlagEvent GTTVersionVerificationEvent GTTVersionVerificationEvent GTTVersionVerificationEvent GTTVersionVerificationEvent downloadCompletedEvent downloadStartedEvent mismatchOfSiteConfigEvent neBuildStatusEvent neInfoEvent
Event Information
<NE type> - <NE name> Abort - Failed (or Success) <NE type> - <NE name> <Code version> <NE type> - <NE name> Background Download Successful <NE type> - <NE name> <Code version> <NE type> - <NE name> Init timed out <load> - <release>.<version>.<subversion>.<patchlevel> - <object number> - <object name> - <object size> - <total object number downloaded> <total object size downloaded> <NE type> - <NE name> <Code Version> <NE type> - <NE name> <Code Version> <Code Version>-<Object>-<Object Size> <Bypass Status> where Bypass Status can be SUCCESSFUL or FAILED NA The NE has completed its download and its operational with the new load. <Universal Time> <Source MSO ID> <System Running Version> <System Version TimeStamp>The System Version Distribution of <System Running Version> has begun at <Source MSO>. DistributionState: <Distribution result> DistributionText: <Distribution info> where Distribution result can be SUCCESS or FAILED <Universal Time> <Source MSO ID> <System Running Version> <System Version TimeStamp> <Reason Code>The System Version Distribution of <System Running Version> has completed at <Source MSO>. GTT <GTT Ready> where GTT Ready can be READY or NOT_READY <NE type> - <NE name> VerifyGTT - Started <NE type> - <NE name> VerifyGTT - Failed <NE type> - <NE name> VerifyGTT - Aborted <NE type> - <NE name> VerifyGTT - Succeeded <NE type> - <NE name> <Code version> <load> - <release>.<version>.<subversion>.<patchlevel> <NE type> - <NE name> Site/config mismatch NEBuildState: <NE Build Status> NEBuildText: <NE Build info> where NE Build Status can be FAILED or SUCCESSFUL This is the OMC generated Auto Load Validation Event:For ACG:codeLoadVersionAcg : <version> - databaseVersionAcg : <version> For BR: codeLoadVersionBr : <version> - databaseVersionBr : <version> For DAP: swLoadVersionRunningDap : <version> swFileVersionRunningDapPdConfig : <version> <Universal Time> <Source MSO> <Dest MSO> <NE Name> <NE Database Mode> <System Running Version> <System Version Timestamp> Configuration information for NE identified by <NE Instance> requires update at the <Dest MSO>. <load> - <release>.<version>.<subversion>.<patchlevel> - <object number> - <object name> - <object size> WARNING: An OMC Subsystem Has Died - <Restartable> - <subsystem> WARNING: An OMC Subsystem Has Died - <Non Restartable> - <subsystem> NOTE: An OMC Subsystem Has Restarted - <subsystem> <attempt#> SystemVersionState: <SV operation>SystemVersionText: (System Version <SV number.minor-id> (<SV name>) - <SV info>) where SV Operation can be New,Deleted, Merged or Distributed SystemVersionState: <SV operation>SystemVersionText: (System Version <SV number.minor-id> (<SV name>) - <SV info>) where SV Operation can be New,Deleted, Merged or Distributed <NE type> - <NE name> Swithing <NE type> - <NE name> Switch Scheduled <NE type> - <NE name> Switch Successful <NE type> - <NE name> Online Switch Scheduled <NE type> - <NE name> Online Switch Successful <NE type> - <NE name> Ack Successful NE Name : < NE name >
Report & Clear R R R R R R R R R R R R R R R R R R R R R R R R R
Change Status U U U U U U U U U U U U U U U U U U U U U U U U U
neReplicationEvent objectDownloadingEvent OmcSubsystemDieEvent OmcSubsystemDieEvent OmcSubsystemRestartedEvent SVOpStartEvent SVOpEndEvent switchOnEvent switchScheduledEvent switchSucceededEvent onlineSwitchScheduledEvent onlineSwitchSucceededEvent ackSucceededEvent updateAlarmDisplayAddrEvent
R R R R R R R R R R R R R R
U U U U M U U U U U U U U U
OMC-R-36
October 30, 2008
Release SR17.0
Event Type
omcStateChangeEvent uploadDeliveryStartEvent uploadDeliveryEndEvent msoChangeEvent DLReadyNotificationEvent rupSwitchScheduledEvent rupSwitchSucceededEvent iosEvent CodeVersionNotificationEvent neStatusEvent iosApprovalStatusEvent

Event Information
<OMC Name> <New OMC Status> <Old OMC Status>where New and Old OMC status can be one of Operational (1), Failed (2), Impaired (3), Indeterminate (4), Unknown <Number of Uploads> Uploads will be Attempted <Number of Uploads> Uploads Succeeded - <Number of Uploads> Uploads Failed <mso_id> <ChangeFlag> <Running SV> <run time stamp> <dl_ready_status> with values of NEDB_READY(1), NEDB_NOTREADY(2) & NEDB_UNKNOWN(3) will be notified for DAPs, IDACs, VSGWs, Horizontal iVPUs, logical HAIHLRs, logical HADAPs ( For HA NEs the Max Value of the 2 Nodes will be notified ) <NE type> - <NE name> RUP Switch Scheduled <NE type> - <NE name> RUP Switch Successful <SourceMSOID> <iosVersion> <iosOpType> <Old_Code_Version><New_Code_Version> will get printed for legacy DAPs, HADAPs, HAiHLRs ( For HA NEs, minimum Code Version of the two Nodes will get displayed ) NE Status: <NE Status> ; Reason:<Reason> DCC Status:<DCC Status> where Reason can be SNMP is not responding and NE Status & DCC Status can be Indeterminate additionalNote: IOS Collection is started, and IOS Approval Window is displayed Waiting for approval. <User Note>. (or) additionalNote: IOS Collection is approved. (or) additionalNote: IOS Collection is rejected. (or) additionalNote: IOS Collection is timeout, and rejected. <User Note> as per what the operator enters Urban Area backup started Urban Area backup successful for all OMC-Rs OMC-R backup started on <OMC-R name> OMC-R backup completed successfully on <OMC-R name> <NE type> - <NE name> Remove source : <source id> where source id can be OMC_DIST_RCV or OMC_MMI or UNKNOWN which represents the source that triggered the remove operation from pendingload for versioned load. Generated when an error is detected in NBI Log file. Can be generated only by the primary OMC. Cron Job is missing -<cron_job>.Generated when an expected cron job cannot be found. Cron Job Failed -<cron_job>. Generated when cron job can't be done or fails while running Cron Job is Completed Successfully-<cron_job> Generated when a cron job is completed successfully Post DEL syncup failed for NE_NAME. Generated when backlog has UpdDeltNe();Error; Machine is not Auto bootable.Generated if machine is not auto bootable. Machine is not bootable from disk.Generated if machine is not bootable from disk. WARNING:Maintenance needed on disk <backup is going on | >. Generated by Admin. Generated when system temperature is found to be unstable. Generated when backlog has UpdDownldNE():Error. Generated with the result of the onstat command. A report is generated at midnight every day to convey system power status ( redundant or not),power supply type ( AC power or other) and most recent AC power failure. NOTE: An OMC subsystem process <process name> not found. NOTE:Current version of OMC-<version> NOTE: An OMC Subsystem Has not Responded to Poll- <process name> NOTE: An OMC Subsystem Has not Restarted -<process name><attempt 1> NOTE: An OMC Subsystem Has not Restarted -<process name><attempt 2> NOTE: Attempted <User Operation> Failed for <user name> <host name>. Report & Clear R R R R R R R R R R R Change Status U U U U U U U U U U U
backupStartedEvent backupCompletedEvent backupStartedEvent backupCompletedEvent neRemoveEvent NbiLogFailureEvent CronJobStatusEvent CronJobStatusEvent CronJobStatusEvent PostDelDbSyncFailureEvent AutoBootEvent BootDeviceEvent DiskMaintenanceEvent SystemTemperatureEvent PostDlDbSyncFailureEvent InformixStatusEvent PowerSupplyStatusEvent OmcProcessNotfoundEvent OmcVersionEvent OmcSubsystemPollingEvent OmcSubsystemRestart FailureEvent OmcSubsystemRestart FailureEvent OmcUserOperationFailedEvent dqmRetryEvent dqmInitiatedEvent
R R R R R R R R R R R R R R R R R R R R R R R R R
N N N N N N N N N N N N N N N N N N N N N N N U U
<operation Type> which can be DOWNLOAD or SWITCH <retry> 1 if DQM will auto retry the failed download/switch, 0 if operator has to. <operation Type> which can be DOWNLOAD or SWITCH. This implies that DQM has sent out the download/Switch request to LMGI.
October 30, 2008
OMC-R-37
Release SR17.0
OMC-R-38
October 30, 2008
Release SR17.0
_________________________________ Alarms
Alarm Type
Alarm Code
SSC
Remedy
R e p o r t & C l e a r O u t a g e Y / N C h a n g e S t a t u s Ethernet Link is enabled or impaired or disabled. This alarm is used to detect the Ethernet link connection failure.
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Severit y
R e l a t e d A l a r m s E M P T Y
Comments & Notes
111301
Ethernet Link Down
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.420. 1.1.1.<Instanc e>
SSC_NIOC_A LM
12 3
E-Net id=<value>, name=<text_d esc> is <Enabled or Impaired or Disabled>
Critical
SSC_NIOC: 607, 608, 609, 610, 611, 612, SSC_HW_CONTA INTER: 601, 602, 603, 604, 605, 622, SSC_NODE: 901, 902, 903, 904
111335
111340
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.430. 1.1.1.<Instanc e> 1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.430. 1.1.1.<Instanc e> 1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.424.
SSC_LM_AL M
SSC_LM_AL M
Missing Object Files for Hardware Type <HWtype> <reason>
Critical
Critical
E EMPTY M P T Y E EMPTY M P T Y E EMPTY M P
Check for the following in the chassis: 1) SSC base interface ports on the RTM (RTM1 and RTM2) should be connected to the router 2) In a dual chassis configuration, SSC base interface port (RTM3) should be connected to the peer chassis 3)The configured processing blades should be installed in the chassis 4) Shelf managers should be installed in the chassis. If the chassis is configured as per the configuration given above and if this alarm is still seen, Contact the iDEN Customer Network Resolution Center for assistance. Contact the iDEN Customer Network Resolution Center for assistance.
R C
N N
N N
R C
Y N
111310
DEV_TEMP Out of Range
SSC_DEV_TE MP
14
DEV_TEMP DeviceType <DeviceTypeI
Critical
Try to maintain the temperature in the operating range. If the problem persists
R C
N N
Update Loads on OMC to versions that not support the hardware version installed. Software Upgrade Failure. Where: <reason> displays different reasons for different failure scenarios. Temperature is outside the operating range.
October 30, 2008
SSC-1

Alarm Type
Alarm Code
Release SR17.0
Severit y R e l a t e d A l a r m s T Y
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
1.1.1.<Instanc e>
d> DeviceId <DeviceID> <Enabled or Disabled> SSC_POWER _ALM 12 Power DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled> Critical
111302
Power Disabled
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.413. 1.1.1.<Instanc e>
E M P T Y
111303
Fan Disabled
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.412. 1.1.1.<Instanc e>
SSC_FAN_AL M
18
Fan DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled>
Critical
E M P T Y
SSC_MISC_HW_ CONTAINER: 606, 613, 615, 617, 619, 621, SSC_HW_CONTA INTER: 601, 602, 603, 604, 605, 622, SSC_NODE: 901, 902, 903, 904 SSC_MISC_HW_ CONTAINER: 606, 613, 615, 617, 619, 621, SSC_HW_CONTA INTER: 601, 602, 603, 604, 605, 622, SSC_NODE: 901, 902, 903, 904
even after the temperature is brought to a safe range, contact the iDEN Customer Resolution Center for assistance. Check circuit breaker connection and if Feed A / B is enabled and connected at the back of the chassis. If all connections are enabled and are valid, then contact the iDEN Customer Network Resolution Center for assistance. Check if latch of the Fan is closed. If problem persists contact the iDEN Customer Network Resolution Center for assistance.
R C
N N
A hardware failure has occurred. If there is a fault with one of the power supplies or if sufficient power is not fed to one of the power supplies.
R C
N N
111305
HARD_DISK Device Disabled
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.417. 1.1.1.<Instanc e>
SSC_SCSI_A LM
HARD_DISK DeviceType <DeviceTypeI d> Device Id <DeviceID> <Enabled or Disabled or
Critical
E M P T Y
SSC_SCSI: 607, 608, 609, 610, 611, 612, SSC_HW_CONTA INTER: 601, 602, 603, 604, 605, 622, SSC_NODE:
R C
N N
This alarm is reported as a cooling fan has been disabled. The SSC has 3 pairs of upper fans (front/rear), 3 lower fans. Any fans out of service is not service impacting but should be investigated for corrective action. Should one fan fail, open a minor ticket with Motorola CNRC. If all fans are disabled, the SSC will shutdown when it reaches its thermal limit to avoid heat damage. Should all fans fail, open a Critical ticket with Motorola CNRC for resolution and contact the market A hardware failure has occurred
SSC-2
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Severit y
Remedy
O u t a g e Y / N
Comments & Notes
111309
TOY_CLOCK Device Disabled
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.425. 1.1.1.<Instanc e>
SSC_TOY_CL OCK_ALM
111323
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.411. 1.1.1.<Instanc e>
SSC_CPU_AL M
19 9
111324
Memory Disabled
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.411. 1.1.1.<Instanc e>
SSC_CPU_AL M
Impaired> TOY_CLOCK DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled> DISK VOLUME DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Enabled> MEMORY DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Impaired or Enabled>
Critical
901, 902, 903, 904 E EMPTY M P T Y
Try to re-integrate the failed hardware, if possible. If hardware fails multiple attempts to re-integrate, replace the hardware or system unit. Contact the iDEN Customer Network Resolution Center for assistance
R C
N N
Critical
E EMPTY M P T Y
R C
N N
Critical
E EMPTY M P T Y
R C
N N
A hardware failure has occurred. 99 is the maximum instance of instance. The real instance of VOLUME is decided during run-time, which is around 20. A hardware failure has occurred. An alarm indicating enabled state of HW Device Memory is sent when memory is available, which is CLEAR alarm for HW DEVICE MEMORY. An alarm indicating impaired state of HW Device Memory is sent when total Memory decreased from last reboot or % mem used over alarm threshold (default = 85%), which is SET alarm for HW DEVICE MEMORY. An alarm indicating disabled state of HW Device Memory is sent when % mem used over recovery threshold (default = 90%) or total memory less than minimum required by config, which is SET alarm
October 30, 2008
SSC-3

Alarm Type
Alarm Code
Release SR17.0
Severit y R e l a t e d A l a r m s
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
111326
SYSTEM BUS Disabled
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.411. 1.1.1.<Instanc e>
SSC_CPU_AL M
111327
IPMI Bus Disabled
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.411. 1.1.1.<Instanc e>
SSC_CPU_AL M
SYSTEM_BU S DeviceType <DeviceTypeI d> Device Id <DeviceID> <Disabled or Impaired or Enabled> IPMI Bus Disabled
Critical
E EMPTY M P T Y
R C
N N
for HW DEVICE MEMORY also. In some scenarios, there can be one CLEAR alarm for more than one corresponding SET alarms. A hardware failure has occurred.
Critical
E M P T Y
111331
111332
111333
Latch Open
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.411. 1.1.1.<Instanc e> 1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.411. 1.1.1.<Instanc e> 1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.411. 1.1.1.<Instanc e>
SSC_CPU_AL M
11 5
SSC_CPU_AL M
SSC_CPU_AL M
12
Voltage Device <id> Outside Operating Range IPMI Controller <id> <Disabled or Enabled> Latch Open <id>
Critical
Critical
Critical
SSC_MISC_HW_ CONTAINER: 606, 613, 615, 617, 619, 621, SSC_HW_CONTA INTER: 601, 602, 603, 604, 605, 622, SSC_NODE: 901, 902, 903, 904 E EMPTY M P T Y E EMPTY M P T Y E EMPTY M P T Y
R C
N N
IPMI bus is not operational
R C
N N
Voltage Level Outside of given threshold range.
R C
N N
IPMI controller is not operational
111336
Shelf Manager Disabled
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.427. 1.1.1.<Instanc e>
SSC_MISC_A LM
12
Shelf Manager DeviceType <DeviceTypeI d> Device Id <DeviceID>
Critical
E M P T Y
SSC_MISC_HW_ CONTAINER: 606, 613, 615, 617, 619, 621, SSC_HW_CONTA
Check if latch is closed for the front blade and the rear transition blade. If problem persists contact the iDEN Customer Network Resolution Center for assistance Contact the iDEN Customer Network Resolution Center for assistance. Note that during shelf manager initialization after a dual shelf
R C
N N
close the latch to clear the condition
R C
N N
SSC-4
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Severit y
Remedy
O u t a g e Y / N
Comments & Notes
<Disabled or Enabled>
INTER: 601, 602, 603, 604, 605, 622, SSC_NODE: 901, 902, 903, 904
100054
Bad Value in config file
1.3.6.1.4.1.16 1.3.3.10.2.14. 1.1.0
CA_BADVAL_ ALM
Bad Value for OID:<object_i d>
Major
111330
Timezone Failure
111334
111337
111338
Blade Operation Failure
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e> 1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e> 1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e> 1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc
SSC_APP_AL M
Major
SSC_APP_AL M
Critical
SSC_APP_AL M
Critical
SSC_APP_AL M
21 3
Critical
E M P T Y E M P T Y E M P T Y E M P T Y E M P T
EMPTY
manager failure, ATCA chassis will experience failures that will cause the ATCA processing blades and/or SSC to be inaccessible. The chassis should restore itself to provide full functionality within 5 minutes from the time the shelf manager becomes online. If the failure conditions are not cleared and processing blades/SSC are still not accessible, reset the entire chassis from SSC LMT. Instructions to reset the chassis should be available in the SSC LMT user manual. If the failure condition persists, contact the iDEN Customer Network Resolution Center for assistance Contact the iDEN Customer Network Resolution Center for assistance
N N
Bad Value returned in the Configuration File. Where <object_id> = {x.x.x...} Timezone is set based on configuration downloaded from OMC-R This alarm is not supported and will be removed from this document in a future release. This alarm is not supported and will be removed from this document in a future release. OLCC operation to add/delete/update a blade has failed.
EMPTY
R C
N N
EMPTY
Y N
EMPTY
R C
Y N
EMPTY
Contact the iDEN Customer Network Resolution Center for assistance, if this alarm does not clear.
R C
Y N
October 30, 2008
SSC-5

Alarm Type
Alarm Code
Release SR17.0
Severit y R e l a t e d
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
111339
DHCP Server Failure
111500
SSC Replication Failure
e> 1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e> 1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
Critical
SSC_APP_AL M
<Node><Reas on>
Major
A l a r m s Y E EMPTY M P T Y E SSC_REPLICATI M ON: 702, 703 P T Y
R C
Y N
R C
N N
111501
SSC Replication Communication Failure
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
<Node><Com munication Failure>
Major
E SSC_REPLICATI M ON: 702, 703 P T Y
Contact the iDEN Customer Network Resolution Center for assistance, if condition does not clear
R C
N N
This alarm is not supported and will be removed from this document in a future release. SSC Replication services have transitioned to an inactive state and is no longer tracking information for replication to the other node. Until this information is refreshed from the iHLR and the subscriber reregisters, the subscriber might experience unexpected behaviors when a switchover occurs before the condition clears. One potential unexpected behavior is shadow subscribers caused by MSID/DGID assignments not being replicated. SSC Replication services encountered an issue with its communication path to the other node and is attempting to recover communications with the other node. When the condition does not clear, the HA-SSC nodes and the Ethernet cables should be examined for issues.
SSC-6
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Severit y
R e l a t e d
Remedy
O u t a g e Y / N
Comments & Notes
111502
SSC Replication Suspended
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
<Node Suspended On> <User Who Suspended>
Warning
A l a r m s E SSC_REPLICATI M ON: 702, 703 P T Y
When SSC Replication suspension was not planned, customer can utilize the LMT Replication Activation option to restart SSC Replication.
R C
N N
111503
SSC Replication Log 25% Full
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
Warning
E EMPTY M P T Y
Contact the iDEN Customer Network Resolution Center for assistance, if condition does not clear or a large number of events detected.
R C
N N
111504
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
Minor
1 EMPTY 1 1 5 0 3
R C
N N
SSC Replication services were suspended by a LMT User on the SSC. Communications with the other node have terminated until the SSC Replication services are activated again. SSC Replication services is experiencing a backlog of replication events, but is performing all operations normally. Because the synchronization activity is a likely source of this backlog, the throttling of the synchronization will commence if the backlog continues to grow. When this event does not clear within a reasonable period of time, additional investigation should be started. SSC Replication services is experiencing a serious backlog of replication events, where the synchronization activity is being throttled. If the backlog continues to grow, the synchronization activities will be halted. Customer should verify that SSC
October 30, 2008
SSC-7

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
111505
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
Major
1 EMPTY 1 1 5 0 4
R C
N N
111506
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
Critical
1 SSC_REPLICATI 1 ON: 702, 703 1 5 0 5
R C
N N
111507
SSC Replication Synchronized
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
<Node> <Type> <Scope>
Warning
E SSC_REPLICATI M ON: 702, 703 P T Y
Contact the iDEN Customer Network Resolution Center for assistance, if the node remains in a synchronization state.
R C
N N
Replication has not been suspended and SSC Replication Communications are functioning normally. SSC Replication services is experiencing a major backlog of replication events, and synchronization activities are being blocked. If the backlog continues to grow, SSC Replication services will automatically transition into an inactive state. Customer should verify that SSC Replication has not been suspended and SSC Replication Communications are functioning normally. SSC Replication services is experiencing a critical backlog of replication events and is transitioning replication to an inactive state. Customer should verify that SSC Replication has not been suspended and SSC Replication Communications are functioning normally. SSC Replication services has been requested to perform a synchronization activity on one or
SSC-8
October 30, 2008
Release SR17.0
Alarm Type
Alarm Code

I n s t
Alarm Code Text
Severit y
Remedy
O u t a g e Y / N
Comments & Notes
111508
SSC Replication No Region
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
<Node> <Region>
Warning
E EMPTY M P T Y
Contact the iDEN Customer Network Resolution Center for assistance in determining the impacted region.
R C
N N
111701
Task Monitor Failure
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
Critical
E M P T Y
111702
IP Configuration mismatch (MIB vs DHCP)
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
Critical
SSC_CCP_APP: 202, SSC_APP: 202, SCC_APP_CONT AINER: 301, 302, 303, SSC_NODE: 901, 902, 903, 904 E EMPTY M P T Y
Y N
more connected regions. The request could have been generated by a LMT user or internally. Customer should wait until the synchronization activity completes before performing maintenance on the node. SSC Replication services received a replication event for a region that was not connected. The replication event was dropped and the region flagged for a synchronization activity once the region reconnected. HA service has detected a failure of a critical/non-critical task.
Compare DHCP configuration and configuration downloaded from OMC. If the problem persists, contact the iDEN Customer Network Resolution Center for assistance
N N
100055
1.3.6.1.4.1.16 1.3.3.10.2.6.1. 0
CA_SNTP_AL M
Time Difference between NMS and NE exceeds maximum difference for
Major
E EMPTY M P T Y
N N
This alarm will be sent if there a mismatch in the nodal, logical, peer nodal Ip address and subnet between DHCP configuration and configuration downloaded from OMC The time difference between the NMS and the NE was larger than the maximum value for automatic synchronization to be completed.
October 30, 2008
SSC-9

Alarm Type
Alarm Code
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
Alarm Code Text
Remedy
O u t a g e Y / N
Comments & Notes
111312
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
synchronizatio n <File system name> File System <Set or Clear> Excessive at <%> utilization
Critical
E EMPTY M P T Y
R C
N N
111312
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
Critical
E EMPTY M P T Y
R C
N N
111704
SSC Shutting Down
1.3.6.1.4.1.16 1.3.3.10.5.7.1. 1.2.3.1.6.410. 1.1.1.<Instanc e>
SSC_APP_AL M
Critical
E M P T Y
SSC_MODE: 801,804 SSC_NODE: 901,903 SSC_APP_CONT AINER: 301,302
R C
Y N
The reported file system is almost full. WHERE: <file system name> = {a string containing the file system name (mount point with path)}, <% utilization> = {current utilization % 0 100%} The reported file system is unmounting. WHERE: <file system name> = {a string containing the file system name (mount point with path)} The SSC is being shut down for maintenance or software upgrade.
SSC-10
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
2 0 1
APPLICATIO N STARTED
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.24.<INST ANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.24.<INST ANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.202.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.202.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.202.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.203.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.203.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.203.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.203.<INS
SSC_CCP_APP
16
U-D-Idl
U-E-A
EMPTY
EMPTY
SSC is starting up
S t a t u s N N
2 0 2 2 0 1 2 0 2 2 0 5 3 0 1 3 0 1 3 0 2
APPLICATIO N FAILED
SSC_CCP_APP
16
U-E-A
U-D-Idl
EMPTY
111701
EMPTY
N N
APPLICATIO N STARTED
SSC_APP
U-D-Idl
U-E-A
SSC_CCP_A PP: 201
EMPTY
SSC is starting up
N N
APPLICATIO N FAILED
SSC_APP
U-E-A
U-D-Idl
SSC_CCP_A PP: 202
111701
EMPTY
N N
Application has been started/automatically restarted. MOC=24; Instances: 1 = Fault, 2 = Config, 3 = Monitor, 4 = Timer_1, 5 = Timer_2, 6 = Load Application has failed. MOC=24; Instances: 1 = Fault, 2 = Config, 3 = Monitor, 4 = Timer_1, 5 = Timer_2, 6 = Load Application has been started/automatically restarted. MOC=202; Instances: 1 = CCP App Cont Application has failed. MOC=202; Instances: 1 = CCP App Cont Application has shutdown. MOC=202; Instances: 1 = CCP App Cont Critical application functionality has been lost. MOC=203
APPLICATIO N SHUTDOWN CRITICAL FUNCTIONA LITY LOST CRITICAL FUNCTIONA LITY LOST ALL APPLICATIO NS FUNCTIONA L ALL APPLICATIO NS
SSC_APP
U-E-A
U-D-Idl
SSC_CCP_A PP: 202
111701
N N
SSC_APP_CONTAINER
U-E-Imp
U-D-Idl
SSC_APP: 202
111701
N N
SSC_APP_CONTAINER
U-E-A
U-D-Idl
SSC_APP: 202
111701, 111704
N N
Critical application functionality has been lost. MOC=203
SSC_APP_CONTAINER
U-D-Idl
U-E-A
SSC_APP: 201
111704
task is starting up
N N
3 0 2
SSC_APP_CONTAINER
U-E-Imp
U-E-A
SSC_APP: 201
111701
All tasks are up
N N
October 30, 2008
SSC-11

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
From State
Comments & Notes
3 0 3
3 0 3
6 0 1
FUNCTIONA L ONE OR MORE APPLICATIO NS NOT FUNCTIONA L ONE OR MORE APPLICATIO NS NOT FUNCTIONA L HW CONTAINER RESTORED FULL FUNCTIONA LITY
TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.203.<INS TANCE> SSC_APP_CONTAINER 1 U-D-Idl U-E-Imp SSC_APP: 201,202 111701 Task not responding to poll N N One or more applications are not fully operational. MOC=203
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.203.<INS TANCE>
SSC_APP_CONTAINER
U-E-A
U-E-Imp
SSC_APP: 201,202
111701
N N
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.101.<INS TANCE>
SSC_HW_CONTAINER
U-D-Idl
U-E-A
SSC_MISC_H W_CONTAIN ER: 606, 613, SSC_NIOC: 607, 610, SSC_SCSI: 608 SSC_MISC_H W_CONTAIN ER: 606, 613, 615, 617, 619, 621, SSC_NIOC: 607, 608, 609, 610, 611, 612, SSC_SCSI: 607, 608 SSC_MISC_H W_CONTAIN ER: 606, 613, 617, 621, SSC_NIOC: 607, 609, 610, 611, SSC_SCSI: 608 SSC_MISC_H W_CONTAIN ER: 606, 613, 615, 617, 619, 621, SSC_NIOC:
111301, 111302, 111303, 111305, 111327, 111336
6 0 2
HW CONTAINER LOST FULL FUNCTIONA LITY
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.101.<INS TANCE>
SSC_HW_CONTAINER
U-E-A
U-D-Idl
111301, 111302, 111303, 111305, 111327, 111336
Harward components (disk, enet, and miscellaneous components (fan, power, IPMB, and shelf manager)) are fully operational All hardware components are no longer operational
N N
HW Container has become operational. MOC=101
N N
6 0 3
HW CONTAINER LOST PARTIAL FUNCTIONA LITY
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.101.<INS TANCE>
SSC_HW_CONTAINER
U-E-A
U-E-Imp
111301, 111302, 111303, 111305, 111327, 111336
All hardware components are partially operational
N N
HW Container has partially failed - one or more FRUs are not operational. MOC=101
6 0 4
HW CONTAINER LOST FULL FUNCTIONA LITY
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.101.<INS TANCE>
SSC_HW_CONTAINER
U-E-Imp
U-D-Idl
111301, 111302, 111303, 111305, 111327, 111336
All hardware components are no longer operational
N N
SSC-12
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
6 0 5
HW CONTAINER RESTORED PARTIAL FUNCTIONA LITY
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.101.<INS TANCE>
SSC_HW_CONTAINER
U-D-Idl
U-E-Imp
6 2 2
HW CONTAINER RESTORED FULL FUNCTIONA LITY
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.101.<INS TANCE>
SSC_HW_CONTAINER
U-E-Imp
U-E-A
607, 608, 609, 610, 611, 612, SSC_SCSI: 607, 608 SSC_MISC_H W_CONTAIN ER: 606, 613, 617, 621, SSC_NIOC: 607, 609, 610, 611, SSC_SCSI: 608 SSC_MISC_H W_CONTAIN ER: 606, 613, SSC_NIOC: 607, 610, SSC_SCSI: 608 EMPTY
111301, 111302, 111303, 111305, 111327, 111336
All hardware components are partially operational
N N
111301, 111302, 111303, 111305, 111327, 111336
6 0 6
6 1 3
6 1 5 6 1 7
6 1 9
MISCELLANE OUS CONTAINER FULLY OPERATION AL MISCELLANE OUS CONTAINER FULLY OPERATION AL MISCELLANE OUS CONTAINER FAILURE MISCELLANE OUS CONTAINER PARTLY OPERATION AL MISCELLANE OUS CONTAINER FAILURE
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.107.<INS TANCE>
SSC_MISC_HW_CONT AINER
U-E-Imp
U-E-A
111302, 111303, 111327, 111336
Harward components (disk, enet, and miscellaneous components (fan, power, IPMB, and shelf manager)) are fully operational Miscellaneous components (fan, power, IPMB, and shelf manager) are fully operational Miscellaneous components (fan, power, IPMB, and shelf manager) are fully operational All miscellaneous components are no longer operational All miscellaneous components are partially operational
N N
All HW Container's FRUs are fully operational. MOC=101
N N
Miscellaneous Container's FRUs (fan, power, IPMB, and shelf manager) are fully operational. MOC=107
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.107.<INS TANCE>
U-D-Idl
U-E-A
EMPTY
111302, 111303, 111327, 111336
N N
Miscellaneous Container's FRUs (fan, power, IPMB, and shelf manager) has become operational. MOC=107
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.107.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.107.<INS TANCE>
U-E-A
U-D-Idl
EMPTY
U-E-A
U-E-Imp
EMPTY
111302, 111303, 111327, 111336 111302, 111303, 111327, 111336
N N
N N
All Miscellaneous Container's FRUs (fan, power, IPMB, and shelf manager) functionality has been lost. MOC=107 Miscellaneous Container FRU (fan, power, IPMB, and shelf manager) has partially failed one or more FRUs are not operational. MOC=107 All Miscellaneous Container's FRUs (fan, power, IPMB, and shelf manager) has become non-operational. MOC=107
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.107.<INS TANCE>
U-E-Imp
U-D-Idl
EMPTY
111302, 111303, 111327, 111336
N N
October 30, 2008
SSC-13

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
From State
Comments & Notes
6 2 1
MISCELLANE OUS CONTAINER PARTLY OPERATION AL NODE IN MAINTENAN CE MODE
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.107.<INS TANCE>
U-D-Idl
U-E-Imp
EMPTY
111302, 111303, 111327, 111336
S t a t u s N N
8 0 1
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.208.<INS TANCE>
SSC_MODE
U-E-A
U-D-Idl
8 0 2 8 0 3 8 0 4
NODE IN STANDBY MODE NODE IN ACTIVE MODE NODE IN MAINTENAN CE MODE
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.208.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.208.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.208.<INS TANCE>
SSC_MODE
U-E-A
U-E-Idl
SSC_APP_C ONTAINER: 301, SSC_HW_CO NTAINER: 601, 602, 603, 604, 605, 622 SSC_NODE: 901, 904
111704
Node moves from Active mode to Maintenance mode
N N
Operation of Miscellaneous Container FRU (fan, power, IPMB, and shelf manager) is partially restored.Still one or more FRUs but not all of FRUs of the same fru type, are failed. MOC=107 Mode of the SSC are Maintenance
EMPTY
Node moves from Active mode to Standby mode Node moves from Standby mode to Active mode Node moves from Standby mode to Maintenance mode
N N
Mode of the SSC are Standby
SSC_MODE
U-E-Idl
U-E-A
SSC_NODE: 901, 904
EMPTY
N N
Mode of the SSC are Active
SSC_MODE
U-E-Idl
U-D-Idl
8 0 5 6 0 7
NODE IN STANDBY MODE FRU RESTORED FULL FUNCTIONA LITY FRU LOST FUNCTIONA LITY FRU RESTORED PARTIAL FUNCTIONA LITY
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.208.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.105.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.105.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.105.<INS TANCE>
SSC_MODE
U-D-Idl
U-E-Idl
SSC_APP_C ONTAINER: 301, SSC_HW_CO NTAINER: 601, 602, 603, 604, 605, 622 SSC_NODE: 901, 904
111704
N N
Mode of the SSC are Maintenance
EMPTY
Node moves from Maintenance mode to Standby mode FRU has become operational
N N
Mode of the SSC are Standby
SSC_NIOC
U-D-Idl
U-E-A
EMPTY
111301
N N
FRUs has become fully operational. NIOC: MOC=105
6 0 8 6 0 9
SSC_NIOC
U-E-A
U-D-Idl
EMPTY
111301
FRU has become non-operational
N N
FRUs has become nonoperational or have been removed. NIOC: MOC=105 FRUs has become partial operational. NIOC: MOC=105
SSC_NIOC
U-D-Idl
U-E-Imp
EMPTY
111301
N N
SSC-14
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
6 1 0 6 1 1 6 1 2 9 0 1
FRU RESTORED FUNCTIONA LITY FRU LOST PARTIAL FUNCTIONA LITY FRU LOST FUNCTIONA LITY NODE RESTORED FULL FUNCTIONA LITY
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.105.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.105.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.105.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.204.<INS TANCE>
SSC_NIOC
U-E-Imp
U-E-A
EMPTY
111301
S t a t u s N N
FRUs has become operational. NIOC: MOC=105
SSC_NIOC
U-E-A
U-E-Imp
EMPTY
111301
N N
FRUs has become partial operational. NIOC: MOC=105
SSC_NIOC
U-E-Imp
U-D-Idl
EMPTY
111301
FRU has become non-operational
N N
FRUs has become nonoperational or have been removed. NIOC: MOC=105 The SSC has restored full functionality. MOC=204
SSC_NODE
U-D-Idl
U-E-A
SSC_APP_C ONTAINER: 302, SSC_HW_CO NTAINER: 601, 622
9 0 1
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.204.<INS TANCE>
SSC_NODE
U-E-Imp
U-E-A
SSC_APP_C ONTAINER: 302, SSC_HW_CO NTAINER: 601, 622
9 0 2
NODE LOST PARTIAL FUNCTIONA LITY
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.204.<INS TANCE>
SSC_NODE
U-E-A
U-E-Imp
9 0 3
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.204.<INS TANCE>
SSC_NODE
U-E-Imp
U-D-Idl
SSC_APP_C ONTAINER: 302, 303, SSC_HW_CO NTAINER: 601, 603, 605, 622 SSC_APP_C ONTAINER: 301, 302, 303, SSC_HW_CO NTAINER: 601, 602, 603, 604, 605, 622 SSC_APP_C ONTAINER: 301, 302, 303, SSC_HW_CO
9 0 3
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.204.<INS TANCE>
SSC_NODE
U-E-A
U-D-Idl
111301, 111302, 111303, 111305, 111327, 111336, 111701, 111704 111301, 111302, 111303, 111305, 111327, 111336, 111701, 111704 111301, 111302, 111303, 111305, 111327, 111336, 111701 111301, 111302, 111303, 111305, 111327, 111336, 111701, 111704 111301, 111302, 111303, 111305,
SSC is starting up
N N
Application task and hardware are restored
N N
The SSC has restored full functionality. MOC=204
One or more tasks or hardwares are failure
N N
The SSC has lost partial functionality. MOC=204
Application task shutdown or Hardware failure
N N
The SSC has lost full functionality. MOC=204
Application task shutdown or Hardware failure
N N
The SSC has lost full functionality. MOC=204
October 30, 2008
SSC-15

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) NTAINER: 601, 602, 603, 604, 605, 622 111327, 111336, 111701, 111704 111301, 111302, 111303, 111305, 111327, 111336, 111701 EMPTY C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Label)
I n s t
From State
Comments & Notes
9 0 4
NODE RESTORED PARTIAL FUNCTIONA LITY
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.204.<INS TANCE>
SSC_NODE
U-D-Idl
U-E-Imp
7 0 1 7 0 1 7 0 2
REPLICATIO N IS ACTIVE
REPLICATIO N IS ACTIVE
REPLICATIO N FAILED
1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.207.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.207.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.207.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.207.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.207.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.207.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.104.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.104.<INS
SSC_REPLICATION
U-D-Idl
U-E-A
SSC_APP_C ONTAINER: 302, 303, SSC_HW_CO NTAINER: 601, 603, 605, 622 EMPTY
One or more tasks or hardwares are failure
N N
The SSC has restored partial functionality. MOC=204
N N
Replication is active. MOC=207
SSC_REPLICATION
U-E-Imp
U-E-A
EMPTY
EMPTY
N N
Replication is active. MOC=207
SSC_REPLICATION
U-E-Imp
U-D-Idl
EMPTY
7 0 2
REPLICATIO N FAILED
SSC_REPLICATION
U-E-A
U-D-Idl
EMPTY
7 0 3
REPLICATIO N DEFFERED
SSC_REPLICATION
U-D-Idl
U-E-Imp
EMPTY
7 0 3
REPLICATIO N DEFFERED
SSC_REPLICATION
U-E-A
U-E-Imp
EMPTY
6 0 7
6 0 8
FRU RESTORED FULL FUNCTIONA LITY FRU LOST FUNCTIONA LITY
SSC_SCSI
U-D-Idl
U-E-A
EMPTY
111500, 111501, 111502, 111506, 111507 111500, 111501, 111502, 111506, 111507 111500, 111501, 111502, 111506, 111507 111500, 111501, 111502, 111506, 111507 111305
Replication has failed; Manual recovery is required
N N
Replication has failed; Manual recovery is required. MOC=207
Replication has failed; Manual recovery is required
N N
Replication has failed; Manual recovery is required. MOC=207
N N
Replication has been deferred. MOC=207
N N
Replication has been deferred. MOC=207
EMPTY
N N
FRUs has become operational. SCSI: MOC=104
SSC_SCSI
U-E-A
U-D-Idl
EMPTY
111305
EMPTY
N N
FRUs has become nonoperational or have been removed. SCSI: MOC=104
SSC-16
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
6 0 9
6 1 0 6 1 1 6 1 2
FRU RESTORED PARTIAL FUNCTIONA LITY FRU RESTORED FUNCTIONA LITY FRU LOST PARTIAL FUNCTIONA LITY FRU LOST FUNCTIONA LITY
TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.104.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.104.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.104.<INS TANCE> 1.3.6.1.4.1.161. 3.3.10.5.7.1.1.2 .4.1.3.104.<INS TANCE>
SSC_SCSI
U-D-Idl
U-E-Imp
EMPTY
111305
EMPTY
N N
FRUs has become partial operational SCSI: MOC=104
SSC_SCSI
U-E-Imp
U-E-A
EMPTY
111305
EMPTY
N N
FRUs has become operational. SCSI: MOC=104
SSC_SCSI
U-E-A
U-E-Imp
EMPTY
111305
EMPTY
N N
FRUs has become partial operational. SCSI: MOC=104
SSC_SCSI
U-E-Imp
U-D-Idl
EMPTY
111305
EMPTY
N N
FRUs has become nonoperational or have been removed. SCSI: MOC=104
October 30, 2008
SSC-17
Release SR17.0
__________________________________ Events
Event Type
Reason Code
OMC Text
MOI Info (Id)
MOI Info (Label )
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N ) N
reStartEvent
2, 5
availabilityEve nt
0, 1, 3, 5, 9, 10, 13
<universal time> <managed object instance> <usage state> <operational state> <administrative state> <boot ROM version> <software Load version> <database version> <code version> <system description> <latest reset reason> <outage time since latest reset> <reboot time> <boot diagnostics> <universal time> <sequence number> <secondary id> <new mode> <time of switch> <reason code> <old mode> <additional text> <reason text>
1.3.6.1. 4.1.161. 3.3.10.2 .3.1.0
SSC_S TATE
EMPTY
EMPTY
SSC_NOD E
EMPTY
This event is used to inform the OMC whenever SSC starts. The reason code are Operator Requested (2), Software Initiated (5). It also tells the OMC that SNMP agent is operational and is ready to handle request.
C Comments & Notes h a n g e S t a t u s N Changed the Event Type to reStartEvent to match OMC event window. Added reason code to provide enhanced description for restart trap
EMPTY
SSC
EMPT Y
EMPTY
EMPTY
EMPTY
EMPTY
Event is generated when the SSC mode changes to Maintenance (1), Standby (2), Active (3) . Universal time Time (in GMT) when the trap was generated. Sequence number Integer incremented for each new Availability trap; the valid range is 24 bits (0..16777215) and it wraps back to 1 when incremented past 24 bits. The value of 0 is only used to restart the sequence when no previous information is available. Secondary id SSC Node ID. New mode SSC nodes new mode. Maintenance (1), Standby (2), Active (3) Time of switch Time (in GMT format) when the
N N Changed the Event Type to availabilityEvent to match OMC event window.
SSC-18
October 30, 2008
Release SR17.0
Event Type
Reason Code

MOI Info (Label ) Inst From State To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
SSC node entered this mode. Reason Code Reason why the SSC node entered this mode. Old mode Mode the SSC node switched from. Unknown is represented as (0). Maintenance (1), Standby (2), Active (3). Reason text Optional text supplied by the operator explaining the reason for requesting a change in mode from Active to Maintenance, Standby to Maintenance, or Active to Standby. Reason text is only sent with the Reason Codes: 10 and 13. Additional text Additional information provided by the SSC if available to facilitate root cause analysis. {REASON CODE, ACTION, REASON TEXT, ADDITIONAL TEXT } {No Reason Code (0), Used for Standby to Active transitions, N/A, None} {Platform Hardware Fault (1), None, N/A, None} {Platform HA Software Fault (3), None, N/A, None} {Application Software Fault (5), None, N/A, None} {Operator Initiated Platform (9), Operator initiates the APP_SHUTDOWN_NODE command via the ELMT, N/A, None} {Operator Initiated Platform (9), Operator initiates the APP_RESTART_NODE command via the ELMT,
October 30, 2008
SSC-19

Event Type
Reason Code
Release SR17.0
From State To State
OMC Text
MOI Info (Id)
MOI Info (Label )
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Action Status
0x90
Action Status
0x91
Action Status
0x92
Session timed-out
1.3.6.1. 4.1.161. 3.3.10.2 .13.1.1. 0 1.3.6.1. 4.1.161. 3.3.10.2 .13.1.1. 0 1.3.6.1. 4.1.161. 3.3.10.2 .13.1.1. 0 1.3.6.1. 4.1.161. 3.3.10.2 .13.1.1. 0 1.3.6.1. 4.1.161. 3.3.10.2 .10.1.1. 0
SSC
EMPT Y
EMPTY
EMPTY
EMPTY
EMPTY
N/A, None} {Operator Initiated Application (10), Application started, N/A, None} {Operator Initiated Application (10), Reinit configuration downloaded from OMC, New configuration file downloaded, None} {Operator Initiated Application (10), Stop the application, LMT Userentered reason text, None} {Provider Active to Standby (13), Force to Standby, LMT User-entered reason text, None} A LMT or UNIX user has logged in. See the Action Status Information for details A LMT or UNIX user has logged out. See the Action Status Information for details A LMT user has been logged out due to session timedout. See the Action Status Information for details A LMT user login session has been manually terminated. See the Action Status Information for details Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition
SSC
EMPT Y
EMPTY
EMPTY
EMPTY
EMPTY
SSC
EMPT Y
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
0x94
SSC
EMPT Y
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
SSC
EMPTY
EMPTY
EMPTY
EMPTY
N N Action status information includes the following information: reason code <user login name> <access level> login. N N Action status information includes the following information: reason code <user login name> <access level> logout. N N Action status information includes the following information: reason code <user login name> <access level> login session timedout. N N Action status information includes the following information: reason code <user login name> <access level> login session manually terminated. N N The state change was updated to keep it consistent with the code and other documentation and avoid confusion.
SSC-20
October 30, 2008
Release SR17.0
Event Type
Reason Code

MOI Info (Label ) Inst From State To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Action Status
1.3.6.1. 4.1.161. 3.3.10.2 .10.1.1. 0
SSC
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
1.3.6.1. 4.1.161. 3.3.10.2 .10.1.1. 0
SSC
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
Background Download Aborted Successfully
Action Status
1.3.6.1. 4.1.161. 3.3.10.2 .10.1.2. 0 1.3.6.1. 4.1.161. 3.3.10.2 .11.1.1. 0 1.3.6.1. 4.1.161. 3.3.10.2 .11.1.1. 0 1.3.6.1. 4.1.161. 3.3.10.2 .11.1.1. 0 1.3.6.1. 4.1.161. 3.3.10.2 .12.2.1. 0
SSC
EMPTY
EMPTY
EMPTY
EMPTY
details. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download abort (bgdlAbort) is successful. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if switch has aborted, completed successfully or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted,
N N
N N
N N
SSC
EMPTY
EMPTY
EMPTY
EMPTY
The state change was updated to keep it consistent with the code and other documentation and avoid confusion. N N The state change was updated to keep it consistent with the code and other documentation and avoid confusion. N N The state change was updated to keep it consistent with the code and other documentation and avoid confusion. The state change was updated to keep it consistent with the code and other documentation and avoid confusion. The state change was updated to keep it consistent with the code and other documentation and avoid confusion.
Action Status
SSC
EMPTY
EMPTY
EMPTY
EMPTY
Action Status
SSC
EMPTY
EMPTY
EMPTY
EMPTY
N N
Action Status
Upgrade Aborted
SSC
EMPTY
EMPTY
EMPTY
EMPTY
N N
Action Status
Upgrade Failed
1.3.6.1. 4.1.161. 3.3.10.2
SSC
EMPTY
EMPTY
EMPTY
EMPTY
N N
The state change was updated to keep it consistent with the code
October 30, 2008
SSC-21

Event Type
Reason Code
Release SR17.0
From State To State
OMC Text
MOI Info (Id)
MOI Info (Label )
Inst
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
.12.2.1. 0
Action Status
1.3.6.1. 4.1.161. 3.3.10.2 .12.2.1. 0
SSC
EMPTY
EMPTY
EMPTY
EMPTY
completed successfully, or has failed. Action Status Error Code may contain addition details. Event is generated if background download upgrade has aborted, completed successfully, or has failed. Action Status Error Code may contain addition details.
and other documentation and avoid confusion.
N N
SSC-22
October 30, 2008
Release SR17.0
______________________________ Alarms
Alarm Type Alar m Code OMC Text MOI Info (Id) MOI Info (Label)
Inst
VSGW
Related State Changes Remedy
R e p o r t & C l e a r R / C Outage Y/N C h a n g e S t a t u s Depends on how many PSFT are Disabled. U Note that power supplies are N+1 redundant, so shutting down a supply is tolerable in properly loaded systems. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This means the individual outputs for each supply are outside tolerance. Power supply will shutdown. Note that power supplies are N+1 redundant, so shutting down a supply is tolerable in properly loaded systems. Clear is implicit after a NE reset and possibly after a CM switchover/failure. FeedFault indicates a failure in a DC power feed into the chassis. Either the DC power has been disconnected, or the DC power source has failed. On the 600W supplies, both A and B feeds are routed into each PSU, hence the separate messages. If a single feed fails (either A or B), the PSUs and system continue to operate. If both feeds
Alarm Code Text
Sev eri ty
Rel ate d Ala rms
Comments & Notes
80200
PSU/Fan Disabled
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID>
VSGW_PSFT
80201
PSU/Fan Power Problem
VSGW_PSFT
Device Type=5 376, ShelfID =1, BoardI D=101103 Device Type=5 376, ShelfID =1, BoardI D=101103
PowerSupply Disabled<A dditional Text or null>
Criti cal
EMP TY
202
Replace the PSU/Fan tray.
PowerSupply Problem<A dditional Text or null>
Criti cal
EMP TY
202
Replace the PSU/Fan Tray.
R / C
Depends on how many PSFT are Disabled.
80202
PSU/Fan Feed A Problem
VSGW_PSFT
Device Type=5 376, ShelfID =1, BoardI D=101103
PowerSupply Feed A Problem<A dditional Text or null>
Maj or
8020 3 (may prec ede 8020 0)
202 (If Alarm 80203 was also generated)
Verify the chassis power-feed. Possibly replace the PSU/Fan Tray. Contact the iDEN Customer Situation Center for assistance.
R / C
October 30, 2008
VSGW-1

Inst
Release SR17.0
Alarm Code Text
Sev eri ty Rel ate d Ala rms
Remedy
Outage Y/N
Comments & Notes
80203
PSU/Fan Feed B Problem
VSGW_PSFT
PowerSupply Feed B Problem<A dditional Text or null>
Maj or
8020 2 (may prec ede 8020 0)
202 (If Alarm 80202 was also generated)
R / C
80204
PSU/Fan Fan High
VSGW_PSFT
Fan High<Additi onal Text or null>
War ning
may prec ede 8020 5, 8020 6, 8020 7
EMPTY
Verify room temperature. Verify that the FAN filter is not clogged and that the fan air intake is not blocked. If the alarm is not associated to a failure in another PSU/Fan, the room temperature is within range, and the alarm does not clears automatically contact the iDEN Customer Situation
R / C
fails, then the system fails. Clear is implicit after a NE reset and possibly after a CM switchover/failure. FeedFault indicates a failure in a DC power feed into the chassis. Either the DC power has been disconnected, or the DC power source has failed. On the 600W supplies, both A and B feeds are routed into each PSU, hence the separate messages. If a single feed fails (either A or B), the PSUs and system continue to operate. If both feeds fails, then the system fails. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
VSGW-2
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
80205
PSU/Fan Fan Failure
VSGW_PSFT
Fan Failure <Additional Text or null>
Criti cal
sym path etic with 8020 6
202
80206
PSU/Fan Cooling Failure
VSGW_PSFT
PowerSupply Cooling Failure<Ad ditional Text or null>
Criti cal
sym path etic with 8020 7
202
Center for assistance. Verify that the FAN filter is not clogged and that the fan air intake is not blocked. Replace the PSU/Fan Tray. Verify that the FAN filter is not clogged and that the fan air intake is not blocked. Verify room temperature. Replace the PSU/Fan Tray. Contact the iDEN Customer Situation Center for assistance.
R / C
This means either the fan is dying or a clogged filter so that the operator either has to change the fan or filter. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Cooling fault indicates a reduction in airflow from a power supply or fan tray. Each PSFT has an onboard cooling sensor that monitors airflow coming from the fan on the unit. Cooling faults and alarms can be caused by fan blockage, or fan failure, or extreme temperature in the chassis. If one PSFT is generating a cooling fault, it's most likely fan blockage or failure. But if other boards in the system are starting to heat up past their temperature thresholds, more serious actions such as putting the chassis into power-inhibit mode should be considered. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Cooling problem indicates a reduction in airflow from a power supply or fan tray. Each PSFT has an onboard cooling sensor that monitors airflow coming from the fan on the unit. Cooling faults and alarms can be caused by fan
R / C
80207
PSU/Fan Cooling Problem
VSGW_PSFT
PowerSupply Cooling Problem<A dditional Text or null>
Maj or
may prec ede 8020 6
EMPTY
Verify that the FAN filter is not clogged and that the fan air intake is not blocked. Replace the PSU/Fan Tray. Contact
R / C
October 30, 2008
VSGW-3

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
the iDEN Customer Situation Center for assistance.
80220
IPSB Failure
VSGW_IPSB
IPSB Board Failure <Additional Text or null>
Criti cal
EMP TY
108 or 109
80221
IPSB Unlatched
VSGW_IPSB
IPSB Board Unlatched< Additional Text or null>
Maj or
EMP TY
EMPTY
80230
AMC Failure
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.<
VSGW_AMC
Device Type=5 376, ShelfID
AMC Board Failure<Ad ditional Text or
Criti cal
8211 0
302 or 303
If the alarm is not cleared automatically within 1 min, reset the IPSB board. If the problem is not solved replace the IPSB board. Contact the iDEN Customer Situation Center for assistance. If the alarm is not cleared automatically within 1 min, reset the IPSB board. If the problem is not solved replace the IPSB board. Contact the iDEN Customer Situation Center for assistance. If the alarm is not cleared automatically within 1 min,
R / C
N (If two IPSB fails there will be an outage, but the alarms would not be forwarde d)
blockage, or fan failure, or extreme temperature in the chassis. If one PSFT is generating a cooling problem alarm, it's most likely fan blockage or failure. Clear is implicit after a NE reset and possibly after a CM switchover/failure. The alarm is generated independently of whether the FRU has a backup that has taken over. This alarm is generated if the IPSBProxy is unable to heartbeat the IPSB board. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R / C
The alarm is generated independently of whether the FRU has a backup that has taken over. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R / C
The alarm is generated if the AMC reports a failure (as retrieved via IPMI). Clear is implicit after a NE
VSGW-4
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
ShelfID>.<Boa rdID>
=1, BoardI D=2930
null>
80231
AMC Unlatched
VSGW_AMC
80240
Payload Failure (Lost heartbeat)
VSGW_PAYL OAD
Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI D=3-18
AMC Board Unlatched< Additional Text or null>
Criti cal
8211 0
EMPTY
replace the AMC board. The alarm may be caused by an IPMI problem; if alarm 82110 has been generated, contact the iDEN Customer Situation Center for assistance. Relatch the AMC Board (and possibly a replacement is needed)
reset and possibly after a CM switchover/failure.
R / C
This alarm is generated if the AMC reports. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
Payload Board Failure<Ad ditional Text or null>
Criti cal
Payl oad spec ific alar m(s)
500 to 506
equipmentF
80250
Cluster Manager
1.3.6.1.4.1.16
VSGW_CM
Device
CM Board
Criti
EMP
49 to 54
If the alarm is not cleared automatically after the board is reset replace the failed board. If the problem persist, contact the iDEN Customer Situation Center for assistance. This alarm is also generated if the Operator resets or remove a board. If the alarm is
R / C
N (Yes if all SaB boards are failing)
This alarm applies only to payload that are configured in the service table. Alarm is generated as result of a heartbeat failed response or an IPMI event. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
This alarm is generated if
October 30, 2008
VSGW-5

Inst
Release SR17.0
Alarm Code Text
Remedy
R e p o r t & C l e a r / C
Outage Y/N
Comments & Notes
ailureEvent
Failure (Loss of heartbeat)
1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID>
Type=5 376, ShelfID =1, BoardI D=1-2
Failure<Ad ditional Text or null>
cal
TY
80260
Configured FRU Removed
VSGW_CM
Device Type=5 376, ShelfID =1, BoardI D=1-2
Cluster Manager Board Removed< Additional text or null>
Criti cal
poss ibly 8026 2 or 8026 3
EMPTY
not cleared automatically after the board is reset replace the CM board. Contact the iDEN Customer Situation Center for assistance. (Re)insert a new compatible unit in the slot.
the Cluster Manager has lost contact with the other Cluster Manager. Alarm is generated as result of a heartbeat failed response. If both CM fail all alarms may never be forwarded. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R / C
80260
VSGW_PAYL OAD
Payload Board Removed< Additional text or null>
Criti cal
poss ibly 8026 2 or 8026 3
EMPTY
(Re)insert a new compatible unit in the slot.
R / C
80260
VSGW_IPSB
Device Type=5 376, ShelfID =1, BoardI
IPSB Board Removed< Additional text or null>
Criti cal
poss ibly 8026 2
EMPTY
R / C
This alarm applies only to payload that are configured in the service table, IPSBs, and the CMs. Does not apply to payloads that are not configured. Does not apply to PSU/FAN and AMCs. No state changes are associated to this alarm because the board went UDI when unlatched. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This alarm applies only to payload that are configured in the service table, IPSBs, and the CMs. Does not apply to payloads that are not configured. Does not apply to PSU/FAN and AMCs. No state changes are associated to this alarm because the board went UDI when unlatched. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This alarm applies only to payload that are configured in the service table, IPSBs, and the CMs. Does not apply to payloads that are not configured. Does not
VSGW-6
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
D=2627
80261
Platform FRU Removed
VSGW_PSFT
PowerSupply Removed< Additional text or null>
Maj or
EMP TY
201
R / C
N (Yes if two or more PSFT are removed)
80261
Platform FRU Removed
VSGW_AMC
AMC Board Removed< Additional text or null>
Maj or
EMP TY
308 or 309
R / C
80262
Unlocked FRU Unlatched
VSGW_CM
Cluster Manager Board Unlatched< Additional text or null>
Maj or
EMP TY
42 to 47
The board should have been locked before being unlatched. If the wrong board was unlatched,
R / C
N (Yes if two CM or two IPSB are Unlatche d, however alarm is
apply to PSU/FAN and AMCs. No state changes are associated to this alarm because the board went UDI when unlatched. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Depending on the number of boards that are being removed the NE state can be modified. This alarm applies only to PSU/FAN and AMC. The AMC alarm is never generated in only one AMC is working. State changes are associated to this alarm because the FRU did not become UDI when unlatched. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Depending on the number of boards that are being removed the NE state can be modified. This alarm applies only to PSU/FAN and AMC. The AMC alarm is never generated in only one AMC is working. State changes are associated to this alarm because the FRU did not become UDI when unlatched. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Depending on the number of boards that are present the NE state can be modified. This alarm applies only to payload that are configured in the service table, CMs and IPSBs. Does not apply to
October 30, 2008
VSGW-7

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
80262
VSGW_PAYL OAD
Payload Board Unlatched< Additional text or null>
Maj or
EMP TY
EMPTY
80262
VSGW_IPSB
IPSB Board Unlatched< Additional text or null>
Maj or
EMP TY
EMPTY
80263
Locked FRU Unlatched
VSGW_CM
Cluster Manager Board Unlatched< Additional text or
Min or
Appli catio n spec ific alar
42 to 47
fasten the latches back and after the board is operational unlatch and remove the correct board. The board should have been locked before being unlatched. If the wrong board was unlatched, fasten the latches back and after the board is operational unlatch and remove the correct board. The board should have been locked before being unlatched. If the wrong board was unlatched, fasten the latches back and after the board is operational unlatch and remove the correct board. No action necessary.
not generate d)
payload that are not configured, PSU/FAN and AMCs. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R / C
N (Yes if two CM or two IPSB are Unlatche d, however alarm is not generate d)
Depending on the number of boards that are present the NE state can be modified. This alarm applies only to payload that are configured in the service table, CMs and IPSBs. Does not apply to payload that are not configured, PSU/FAN and AMCs. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R / C
Depending on the number of boards that are present the NE state can be modified. This alarm applies only to payload that are configured in the service table, CMs and IPSBs. Does not apply to payload that are not configured, PSU/FAN and AMCs. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R / C
N (Yes if payloads do not have backup and two
This alarm applies only to payload that are configured in the service table, CMs and IPSBs. Does not apply to payload that are not configured, PSU/FAN and
VSGW-8
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
D=1-2
null>
m(s)
80263
Locked FRU Unlatched
VSGW_PAYL OAD
Min or
Payl oad spec ific alar m(s)
42 to 47
R / C
80264
Platform FRU Unlatched
VSGW_AMC
81000
IPSB Communication Failure
VSGW_IPSB
AMC Board Unlatched< Additional text or null>
Maj or
EMP TY
EMPTY
No action necessary
R / C
CM Unlatche d, however alarm is not generate d) N (Yes if payloads do not have backup and two CM Unlatche d, however alarm is not generate d) N
AMCs. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
This alarm applies only to payload that are configured in the service table, CMs and IPSBs. Does not apply to payload that are not configured, PSU/FAN and AMCs. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
This alarm applies only to AMCs. This alarm cannot be generated if only one AMC is present. Clear is implicit after a NE reset and possibly after a CM switchover/failure. A redundant link is not operational (Gigabit interface only). Note that the lost of carrier is detected; if the connection between the IPSB and the Element Manager is lost for other causes --e.g. failure of an intermediate router-- the alarm is not generated. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Both redundant links are
Link Failure, redundant link <linkId> is not operational <Additional text or null>
Min or
may prec ede 8100 1
105
communicat
81001
IPSB
1.3.6.1.4.1.16
VSGW_IPSB
Device
Link
Maj
8100
104
Re-establish the physical connection ( disconnected Gigabit cable). Verify that the external router is properly working. Contact the iDEN Customer Situation Center for assistance. Re-establish
R / C
October 30, 2008
VSGW-9

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
ionFailureE vent
Type=5 376, ShelfID =1, BoardI D=2627
Failure, both redundant links are not operational <Additional text or null>
or
81050
Internal Communication Failure
VSGW_CM
Internal Link Failure<Ad ditional text or null>
Maj or
poss ibly sym path etic to 8022 0, 8025 0, 8026 0, 8026 2, 8026 4
EMPTY
81050
Internal Communication Failure
VSGW_PAYL OAD
Maj or
poss ibly sym path etic to
EMPTY
the physical connection ( disconnected Gigabit cable). Verify that the external router is properly working. If the fault condition cannot be solved, replace the IPSB board. Contact the iDEN Customer Situation Center for assistance. This alarm could be related to an IPSB or a CM board failing or being removed. If all CMs and IPSBs are not UDI Contact the iDEN Customer Situation Center for assistance. Note that after an IPSB is reinserted the alarm would not be cleared immediately. This alarm could be related to an IPSB or a CM board failing or being
not operational (Gigabit interface only). Note that the lost of carrier is detected; if the connection between the IPSB and the Element Manager is lost for other causes --e.g. failure of an intermediate router-- the alarm is not generated. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R / C
A redundant link between the CM and a payload card is not operational. The fault condition does not affect the payload service but it reduces its reliability, possibly replace the board. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R / C
A redundant link between the CM and a payload card is not operational. The fault condition does not affect the payload service but it reduces its reliability,
VSGW-10
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
D=3-18
8022 0, 8025 0, 8026 0, 8026 2, 8026 4
81100
Link Failure due to Payload Board Failure
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.1.1.1.< DeviceType>. <ShelfID>..<Link Type>.<UANC >.<LocalID>
VSGW_PiHLR _DAP_LINK
81100
VSGW_DAP_ DAP_LINK
Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=1, UANC =1167772 15, LocalI D=1300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=2, UANC =1167772 15,
Link(s) disabled due to board failure<Add itional Text or null>
Min or
sym path etic to 8024 0
600, 500 to 505
removed. If all CMs and IPSBs are not UDI Contact the iDEN Customer Situation Center for assistance. Note that after an IPSB is reinserted the alarm would not be cleared immediately. This alarm is related to the failure of a board that was managing one or more link. Solve the fault condition that caused the board failure (See 80240).
possibly replace the board. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
Alarm is not sent if the all links were already UDI
Min or
600, 500 to 505
This alarm is related to the failure of a board that was managing one or more link. Solve the fault condition that caused the board failure (See 80240).
October 30, 2008
VSGW-11

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
81100
VSGW_DAP_i HLR_LINK
81100
VSGW_IDAC _IDAC_LINK
81100
VSGW_XCDR _LINK
LocalI D=1300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=3, UANC =1167772 15, LocalI D=1300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=4, UANC =1167772 15, LocalI D=1800 Device Type=5 376, ShelfID =1, BoardI D=317, LinkTy
Min or
600, 500 to 505
Min or
600, 500 to 505
Min or
600, 500 to 505
This alarm is related to the failure of a board that was managing one or more link. Solve the fault condition that caused
VSGW-12
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
82001
Corrupted Data
VSGW_CM
pe=5, UANC =1167772 15, LocalI D=1-20 Device Type=5 376, ShelfID =1, BoardI D=1-2
the board failure (See 80240).
CM Corrupted Data <Additional Text or null>
Maj or
EMP TY
30, 33
82002
Missing Configuration Data
VSGW_CM
CM Missing Configurati on Data <Additional Text or null>
Maj or
EMP TY
30, 33
82003
Not enough System Resource
VSGW_CM
<Text>
Maj or
may prec ede 8025 0
30, 33
processingF
82100
Cluster Manager
1.3.6.1.4.1.16
VSGW_CM
Device
CM CPU
Maj
may
30, 33
Force the NE to reload the SW-load (force flag set). Replace the board if the problem persist (Possibly corrupted HD). Contact the iDEN Customer Situation Center for assistance. Force the NE to reload the SW-load (force flag set). Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance. Reset the Cluster manager, if the problem persist replace the board.. If a standby
A Configuration file is corrupted. Note that only some configuration files are monitored. This alarm also covers the event when a downloaded tar file is invalid and cannot be expanded.
A Configuration file is missing. Note that only some configuration files are monitored.
As example the CM is not able to allocate enough memory to perform some operation. Not enough interfaces, sockets
The CPU of the active
October 30, 2008
VSGW-13

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
ailureEvent
CPU Overload
Type=5 376, ShelfID =1, BoardI D=1-2
Overload <Additional Text or null>
or
prec ede 8025 0
CM exist shutdown the overloaded CM board. Contact the iDEN Customer Situation Center for assistance.
82101
CM Application Startup Error
VSGW_CM
Application Startup Error <Additional Text or null>
Criti cal
may prec ede 8025 0
31, 32
82102
CM Application Failure
VSGW_CM
Application Failure <Additional Text or null>
Criti cal
may prec ede 8025 0
31, 32
82106
CM Application Failure
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.<
VSGW_CM
Device Type=5 376, ShelfID
Application Failure<Ad ditional Text or
Maj or
EMP TY
30, 33
If a second CM board is available reset the board. If the problem persist, contact the iDEN Customer Situation Center for assistance. If a second CM board is available reset the board. If the problem persist, contact the iDEN Customer Situation Center for assistance. If a second CM board is available reset the board. If
cluster manager has reached a threshold at which the reliability of transactions cannot be guaranteed. CPU usage is computed as the ratio between the amount of time that the CPU has spent performing work (user and kernel mode) versus the overall time in a given interval. (i.e. (user+nice+system)*100/(u ser+nice+system+idle) as obtained via /proc/stat). Clear is implicit after a NE reset and possibly after a CM switchover/failure. An application that implements part of the cluster manager did not start correctly. The additional text specifies the specific application. Alarm is sent after the platform has retried to solve automatically the problem. Platform has switched to the standby CM (if available). An application that implements part of the cluster manager failed. The additional text specifies the specific application. Alarm is sent after the platform has retried to solve automatically the problem. Platform has switched to the standby CM (if available). An application that implements part of the cluster manager failed. The additional text specifies the
VSGW-14
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
ShelfID>.<Boa rdID>
=1, BoardI D=1-2
null>
82103
Version Mismatch
VSGW_CM
CM Version Mismatch <Additional Text or null>
Min or
EMP TY
EMPTY
the problem persist, contact the iDEN Customer Situation Center for assistance. No action necessary. Contact the iDEN Customer Situation Center for assistance.
specific application. Alarm is sent after the platform has retried to solve automatically the problem.
R / C
82104
LO Failure (Loss of heartbeat)
VSGW_CM
LO Failure <Additional Text or null>
Criti cal
poss ibly LO alar ms (vsg w spec ific)
30, 33
82105
Proxy Failure (Loss of heartbeat)
VSGW_IPSB
Proxy Failure <Additional Text or null>
Criti cal
EMP TY
30, 33
The platform will restart automatically the LO, if the alarm is not cleared within 1 min, contact the iDEN Customer Situation Center for assistance. The platform will restart automatically the Proxy, if the alarm is not cleared
The platform detected a version mismatch between the software load on the active CM and the standby one. The platform resync the two CM automatically to the newest version. Note that there may be times when components in the NE are temporarily executing different versions of software (during zero-downtime upgrades, etc). This alarm is only generated when the version mismatch is not expected. Clear is implicit after a NE reset and possibly after a CM switchover/failure. A LO-RM stop responding to heartbeat requests.
A Proxy-RM stop responding to heartbeat requests. Note that is the CM application (Proxy-RM) that is failing but the OID points to the proxy's one).
October 30, 2008
VSGW-15

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
D=2627
82105
VSGW_PSFT
Criti cal
EMP TY
30, 33
82105
VSGW_AMC
Criti cal
EMP TY
30, 33
82110
CM IPMI Application Failure
VSGW_CM
CM Error Reading IPMI <Additional Text or null>
Min or
The alar m may be repo rted multi ple time s (for each
EMPTY
within 1 min, contact the iDEN Customer Situation Center for assistance. The platform will restart automatically the Proxy, if the alarm is not cleared within 1 min, contact the iDEN Customer Situation Center for assistance. The platform will restart automatically the Proxy, if the alarm is not cleared within 1 min, contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance. The state of the HW (identified in the additional text) cannot be correctly determined.
The alarm is not providing information about the (proxied) hardware itself.
A Proxy-RM stop responding to heartbeat requests. Note that is the CM application (Proxy-RM) that is failing but the OID points to the proxy's one). The alarm is not providing information about the (proxied) hardware itself.
A Proxy-RM stop responding to heartbeat requests. Note that is the CM application (Proxy-RM) that is failing but the OID points to the proxy's one). The alarm is not providing information about the (proxied) hardware itself.
R / C
A Proxy-RM identified an error in the IPMI interface. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
VSGW-16
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
appli catio n that uses the IPMI )
82111
CM NVRAM Failure
VSGW_CM
CM Error NVRAM <Additional Text or null>
Criti cal
82200
Platform Black Box Threshold Exceeded
VSGW_CM
Platform Black Box Threshold Exceeded< Additional Text or null>
War ning
The alar m may be repo rted multi ple time s (for each appli catio n that acce ss NVR AM) EMP TY
31, 32
The system behavior should be monitored using other means and the operator should not rely on state changes reported by the NE. The NE may not be able to correctly assess the state of the system. Replace the CM board which reported the alarm (note this could be generated both from the active or standby CM). Contact the iDEN Customer Situation Center for assistance.
Restart and Availability Traps may report inconsistent information as the NE may be unable to store time and event information.
EMPTY
This is a normal condition. Using the LMT or the Craft Interface freeze the
R / C
The Black Box is the platform internal log. The Black Box has reached the configured limit for log entries. Additional write operations will overwrite previously entered entries.
October 30, 2008
VSGW-17

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
current platform Black Box log, alarm is cleared after the Black Box Log is frozen.
82201
Error Writing Platform Black Box File
VSGW_CM
Platform Black Box Writing Error<Addit ional Text or null>
Maj or
EMP TY
EMPTY
82202
Error Saving Platform Black Box File
VSGW_CM
Platform Black Box Freeze Error<Addit ional Text or null>
Min or
may prec ede 8026 0
EMPTY
Contact the iDEN Customer Situation Center for assistance. Using the Craft Interface verify the available Disk Space on the Cluster Manager board which reported the alarm. Verify the default file and directory permissions. Delete existing Platform Black Box snapshot files. Possibly replace the CM board. Contact the iDEN Customer Situation Center for assistance. Using the Craft Interface verify the available Disk
Alarm is raised only once when the threshold is reached the first time. Note that alarm means that the threshold limit has been reached not the overall size of the Black Box. Clear is implicit after a NE reset and possibly after a CM switchover/failure. The Black Box is the platform internal log.
The Black Box is the platform internal log.
VSGW-18
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
82203
Storage Capacity Exceeded
VSGW_CM
Storage Capacity Exceeded< Additional Text or null>
Maj or
EMP TY
EMPTY
82300
Cluster Manager Transition
VSGW_CM
Cluster Manager transition <Additional Text or null>
Maj or
multi ple alar ms
multiple state changes
Space on the Cluster Manager board that reported the alarm. Verify the default file and directory permissions. Delete existing platform Black Box snapshot files. Contact the iDEN Customer Situation Center for assistance. Using the Craft Interface verify the available Disk Space on the Cluster Manager. Delete temporary files and system logs (Refer to the NE/LINUX troubleshootin g guide). No Action necessary. The transition may have occurred due to various reasons: An internal error condition, in which case other alarms
The hard drive capacity on the active cluster manager has reached its capacity limit.
The alarm MOI represents the Cluster Manager who took over.
October 30, 2008
VSGW-19

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
82500
Time Sync Error
VSGW_CM
Time Sync error<Addit ional Text or null>
Maj or
EMP TY
30, 33
82501
Missing NTP Server
VSGW_CM
NTP server not configured, using default IP address<A dditional text or null>
Maj or
EMP TY
30, 33
would have been generated. A zero downtime upgrade which requires a Cluster Manager reset. A lock of the active Cluster Manager. This alarm is associated with various alarms and state changes. (1) Verify a NTP server exists and is functional, (2) verify the path to the NTP server exists and that server is reachable from the NE, and (3) verify the NTP server entry at the element manager has the correct IP address of the NTP server. Add the correct IP address of the NTP server to the NTP server entry (DHCP Configuration) at the element manager.
R / C
The platform is unable to obtain time synchronization with an NTP server. Time stamps in alarms, events, logs, and statistics files may not be aligned with the network time. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
The platform did not find an NTP entry in the DCHP/BOOTP response, and it using the OMC IP address as the address of the NTP server. The port is the default NTP port.
VSGW-20
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
R e p o r t & C l e a r R / C
Outage Y/N
Comments & Notes
82600
Missing Payload Configuration
VSGW_CM
Missing Payload Configurati on<Additio nal Text or null>
Min or
EMP TY
EMPTY
82601
Service Configuration Error
VSGW_CM
Invalid Service Configurati on Request<A dditional Text or null>
Maj or
poss ibly Actio nSta tusT rap
EMPTY
Verify that the board is being inserted in the right slot. The OLCC generated by the OMC contains specific board/service assignment, a board is inserted in a slot that is unassigned. Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance.
A payload board is attempting to initialize in the chassis but it has no entry specified in Service table MIB. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R / C
The platform has received a Service configuration request for a payload that does not match the list of service available on the platform (I.e. a matching entry Service directory does not exist). The payload will not be able to initialize. If the request is coming via the OLCC the OLCSwitch is rejected. Note that in normal condition this should never happen if the OMC ensures that the software load provided to the NE and the relevant service information provided in the OLCC match. This error may occur if the configuration is done manually from the LT. Clear is implicit after a NE reset and possibly after a
October 30, 2008
VSGW-21

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
82700
SNMP Configuration Error Mismatch in SubAgent Answers
VSGW_CM
SNMP Configurati on Error Mismatch in SubAgent Answers<A dditional Text or null>
Maj or
82701
SNMP Configuration Error SubAgent Timeout
VSGW_CM
SNMP Configurati on Error Sub-Agent Timeout<A dditional Text null>
Min or
Poss ibly vsg w spec ific alar ms. Poss ibly Actio n Stat us Trap for an OLC C rejec tion 8020 6( repo rting the failur e of the payl oad wher e the subagen t is runni ng)
EMPTY
Contact the iDEN Customer Situation Center for assistance. For a SETRequest modify the value supplied to the subagents or possibly shutdown the payload(s) that returned an inconsistent answer.
CM switchover/failure. An SNMP get/get-next request against a MIB Object for which there are multiple owners (subagents) has yielded different responses. The additional text will provide the name of the FRU that provided different answers. Note that the platform does not know which answer is the correct one.
EMPTY
Retry the command after the NE management framework has recognized the FRU failure. Once the FRU is marked as failed the configuration request is not forwarded to its sub-agents. If the error persists contact the iDEN Customer Situation Center for assistance.
An SNMP get/get-next request against a MIB Object for which there are multiple owners (subagents) has timeout. This alarm is generated only if the NE management framework hasn't recognized yet that the FRU failed.
VSGW-22
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
R e p o r t & C l e a r R / C
Outage Y/N
Comments & Notes
82800
Download Error
VSGW_CM
Download Error<Addit ional Text or null>
Min or
Actio nSta tusT rap
EMPTY
82801
Download aborted due to CM Adm State Change
VSGW_CM
Download Aborted<A dditional Text or null>
Maj or
Actio nSta tusT rap
21,22, 27
82802
Replication Error to standby CM
VSGW_CM
CM Replication Error<Addit ional Text or null>
Maj or
EMP TY
30
Retry the transfer from the OMC, if the problem persist contact the iDEN Customer Situation Center for assistance. The Download was aborted because the CM Adm state changed to Locked. Unlock the CM and retry the transfer. If the problem persist contact the iDEN Customer Situation Center for assistance. Reset the standby CM if the problem persist contact the iDEN Customer Situation Center for assistance.
Action Status trap also reports the info to the EM. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
Action Status trap also reports the info to the EM.
R / C
82900
Redundancy Scheme Failure
VSGW_CM
Redundanc y Scheme failure<Add itional Text or null>
Maj or
EMP TY
EMPTY
Add/replace boards.
The platform was unable to replicate software and/or configuration information to the standby cluster manager following a foreground/background download to the active cluster manager. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This alarm is generated only after a failure of all standby boards that are part of a redundancy schema if there are not FRUs to support redundancy requirements. This alarm implies that there are not standby
October 30, 2008
VSGW-23

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
82901
No Redundancy available
VSGW_CM
No Redundanc y Available< Additional Text or null>
Criti cal
EMP TY
EMPTY
Add/replace boards.
N/Y
82902
Reduced Redundancy available
VSGW_CM
Reduced Redundanc y<Addition al Text or null>
Min or
EMP TY
EMPTY
Add/replace boards.
N/Y
82903
Unsupported Redundancy Policy
VSGW_CM
Unsupporte d Redundanc y Policy<Add itional Text or null>
Maj or
EMP TY
EMPTY
85100
Pseudo DAP to HN DAP Link Version Request Timeout
VSGW_DAP_ DAP_LINK
Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=2, UANC =1167772
Pseudo DAP to HN DAP Link Version Request Timeout: UANC = <UANC>, Remote ID =<Remote _ID>
Criti cal
EMP TY
5504
Contact the iDEN Customer Situation Center for assistance. This problem is related to the reception of an incorrect SW load. 1) Troubleshoot the target DAP and repair. 2) Troubleshoot the Network and repair. 3) Troubleshoot the SaB and repair.
N/Y
boards left. A managed resource has failed that requires a backup but no backup is available. Outage is possible depending on the role of the failed payload. Alarm is thrown when there is an active board that goes disabled and had no standby to take over for it. This alarm is generated only after a failure of a standby board that is part of a redundancy schema if there are not enough FRUs to support redundancy requirements. This alarm implies that other standby are still present but not enough to fulfill the 'M' requirement. This alarm is generated after parsing the redundancy policy. The platform will not accept a 2N configuration where N is not equal to M or where extra boards are not marked as 'u'.
R / C
1) The DAP that is the target of the link version request is not responding. 2) Network Congestion. 3) Network Latency.Where: <UANC> = {1-16777215} <DAP_ID> = {1-300}. Clear is implicit after a NE reset and possibly after a payload failure.
VSGW-24
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
85101
Pseudo DAP to HN DAP Invalid Link Version
VSGW_DAP_ DAP_LINK
85102
Pseudo DAP to HN DAP Link Status Failure
VSGW_DAP_ DAP_LINK
85103
Remote Pseudo DAP to HN DAP Terminate TCP Connection
VSGW_DAP_ DAP_LINK
15, LocalI D=1300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=2, UANC =1167772 15, LocalI D=1300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=2, UANC =1167772 15, LocalI D=1300 Device Type = 5376, ShelfID =1, BoardI D=317,
Pseudo DAP to HN DAP Invalid Link Version: UANC = <UANC>, Remote ID =<Remote _ID>
Criti cal
EMP TY
5504
1) Troubleshoot SaB and reconfigure. 2)Contact the iDEN Customer Situation Center for Assistance.
R / C
Invalid Version Mismatch. Originating or peer DAP is misconfigured. Where: <UANC> = {1-16777215} <DAP_ID> = {1-300}. Clear is implicit after a NE reset and possibly after a payload failure.
Pseudo DAP to HN DAP Link Status Failure: UANC = <UANC>, Remote ID =<Remote _ID>
Criti cal
EMP TY
5503
1) Troubleshoot SaB and reconfigure. 2)Contact the iDEN Customer Situation Center for Assistance.
R / C
The DAP on the remote end is providing an invalid status. Where: <UANC> = {1-16777215} <DAP_ID> = {1-300}. Clear is implicit after a NE reset and possibly after a payload failure.
Remote Pseudo DAP to HN DAP Terminate TCP Connection : UANC =
Criti cal
EMP TY
5502
1) Troubleshoot the target DAP and repair. 2) Troubleshoot the Network and repair. 3)
R / C
The DAP on the remote end has broken the TCP connection. Where: <UANC> = {1-16777215} <DAP_ID> = {1-300}. Clear is implicit after a NE reset and possibly after a payload failure.
October 30, 2008
VSGW-25

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
85104
Incompatible DAP ID on Pseudo DAP to HN DAP Interface
VSGW_DAP_ DAP_LINK
85110
Pseudo DAP to HN iHLR Link Failure
VSGW_DAP_i HLR_LINK
85140
Private Call Failure 3G Threshold Exceeded
1.3.6.1.4.1.16 1.3.3.10.5.15. 1.1.3.1.1.1.<D
VSGW_SAB_ 3GDOMAIN_L INK
LinkTy pe=2, UANC =1167772 15, LocalI D=1300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=2, UANC =1167772 15, LocalI D=1300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=3, UANC =1167772 15, LocalI D=1300 Domai nID=1214748
<UANC>, Remote ID =<Remote _ID>
Troubleshoot the SaB and repair.
Incompatibl e DAP ID on Pseudo DAP to HN DAP Interface: UANC = <UANC>, Remote ID =<Remote _ID>
Maj or
EMP TY
EMPTY
Verify that the DAP ID and peer DAP ID configuration for each DAP match.
R / C
Originating Peer DAP is misconfigured.Where: <UANC> = {1-16777215} <DAP_ID> = {1-300}. Clear is implicit after a NE reset and possibly after a payload failure.
Pseudo DAP to HN iHLR Link Failure: UANC = <UANC>, Remote ID =<Remote _ID>
Criti cal
EMP TY
5507
3G Domain is <Domain id>
Criti cal
EMP TY
EMPTY
1) Troubleshoot the target iHLR and repair. 2) Troubleshoot the Network and repair. 3) Troubleshoot the SaB and repair. 4)Contact the iDEN Customer Situation Center for Assistance. 1) Troubleshoot the target IAS
R / C
1) The iHLR that is the target of the link version request is not responding or responded with a version mismatch. 2) The iHLR on the remote end is providing an invalid status. 3) The iHLR on the remote end has broken the TCP Link. 4) Network Congestion. Clear is implicit after a NE reset and possibly after a payload failure.
R / C
1) The IAS(es) for the Domain are providing too many error messages. 2)
VSGW-26
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
omainId>.<Sa bInstance>
3647, SabIns tance= 1-13
85320
Pseudo iHLR to HN DAP Link Down
VSGW_PiHLR _DAP_LINK
85200
Pseudo iDAC to HN iDAC Link Version Negotiation Failed
VSGW_IDAC _IDAC_LINK
85210
Partial iGTN Connection Failure
1.3.6.1.4.1.16 1.3.3.10.5.14.
VSGW_PAYL OAD
Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=1, UANC =1167772 15, LocalI D=1300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTy pe=4, UANC =1167772 15, LocalI D=1800 Device Type=5
Pseudo iHLR to HN DAP Link Down: UANC = <UANC>, Remote ID =<Remote _ID>
Criti cal
EMP TY
5402
and repair. 2) Troubleshoot the Network and repair. 3) Troubleshoot the SaB and repair. 4) Troubleshoot DNS configuration 1) Troubleshoot the target DAP and repair. 2) Troubleshoot the Network and repair.
Network Congestion or there may be a DNS configuration problem. Note the IAS domain name may be truncated to fix within 80 characters. Clear is implicit after a NE reset and possibly after a payload failure. R / C N U Cleared on successful link version negotiations. Reported on:1) Unsuccessful version negotiations.2) Link Heartbeat Time out. 3) TCP Connection dropped on DAP end. Where: <UANC> = {1-16777215} <Remote_ID> = {1-300}. Clear is implicit after a NE reset and possibly after a payload failure.
Pseudo iDAC - HN iDAC LV Negotiation Failed: UANC = <UANC>, Remote ID =<Remote _ID>
Criti cal
EMP TY
5302
Either the originating VSGW or the inter-urban iDAC must be upgraded to a software load that supports a compatible link protocol version.
R / C
VSGW Bearer cannot distribute voice to and from this inter-urban iDAC. Any existing calls with this iDAC will be dropped. Clear is implicit after a NE reset and possibly after a payload failure.
(Single) Physical
Min or
EMP TY
5000, 5002, 5006, 5013,
VSGW will persistently
R /
VSGW Bearer has lost redundancy on the
October 30, 2008
VSGW-27

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
vent
Enet1
1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID>
376, ShelfID =1, BoardI D=3-18
Link Failure; FRU: <Payload identifier>, Port: Enet1
5018, 5023
85211
Partial iGTN Connection Failure Enet2
VSGW_PAYL OAD
(Single) Physical Link Failure; FRU: <Payload identifier>, Port: Enet2
Min or
EMP TY
5000, 5002, 5006, 5013, 5018, 5023
85212
Total iGTN Connection Failure
VSGW_PAYL OAD
Double Physical Link Failure; FRU: <Payload
Criti cal
8521 0, 8521 1
5026, 5021, 5016, 5002, 5004, 5008, 5000, 5013
retry the connection. Verify network connectivity from VSGW SaB instance to switch/router. Verify switch/router functioning. If these are all working, there is a possible HW problem with the PPRB and FRU should be replaced. VSGW will persistently retry the connection. Verify network connectivity from VSGW SaB instance to switch/router. Verify switch/router functioning. If these are all working, there is a possible HW problem with the PPRB and FRU should be replaced. VSGW will persistently retry the connection. Verify network connectivity
physical connection. VSGW Bearer can still distribute voice packets as long as the second port doesn't fail. Clear is implicit after a NE reset and possibly after a payload failure.
R / C
VSGW Bearer has lost redundancy on the physical connection. VSGW Bearer can still distribute voice packets as long as the second port doesn't fail. Clear is implicit after a NE reset and possibly after a payload failure.
R / C
N(Y if this is true for all SaBs)
VSGW Bearer cannot distribute intra-urban voice packets. FRU will be disabled. Clear is implicit after a NE reset and possibly after a payload
VSGW-28
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
D=3-18
identifier>
85213
Error in configuration data IP Address Collision Enet1 will be unused
VSGW_PAYL OAD
Device detected using same phys IP addr as Enet1: <IP address>, <remote MAC address>
Maj or
EMP TY
5000, 5002, 5006, 5013, 5018, 5023
85214
Error in configuration data IP Address Collision Enet2 will be unused
VSGW_PAYL OAD
Device detected using same phys IP addr as Enet2: <IP address>, <remote MAC address>
Maj or
EMP TY
5000, 5002, 5006, 5013, 5018, 5023
85215
Error in configuration data IP Address Collision Ethernet 1 and 2 board is
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa
VSGW_PAYL OAD
Device Type=5 376, ShelfID =1,
Device detected using same phys IP addr as
Criti cal
8521 3, 8521 4
5026, 5021, 5016, 5002, 5004, 5008, 5000, 5013
from VSGW SaB instance to switch/router. Verify switch/router functioning. If these are all working, there is a possible HW problem with the PPRB and FRU should be replaced. Configured value from OMC conflicts with another device on the network. Analyze and change OMC configuration as needed for this VSGW Bearer to a unique value. Configured value from OMC conflicts with another device on the network. Analyze and change OMC configuration as needed for this VSGW Bearer to a unique value. Configured value from OMC conflicts with another device on the
failure.
VSGW Bearer cannot communicate using the physical port. If a redundant physical port is available VSGW Bearer can still distribute voice packets.
VSGW Bearer cannot communicate using the physical port. If a redundant physical port is available VSGW Bearer can still distribute voice packets.
VSGW Bearer cannot distribute intra-urban voice packets. FRU will be disabled.
October 30, 2008
VSGW-29

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
disabled
rdID>
BoardI D=3-18
85216
Error in configuration data Logical IP Address Collision
VSGW_PAYL OAD
Enet1, Enet2: <IP address>, <remote MAC address>, <IP address>, <remote MAC address> Device detected using same logical IP addr: <IP address>, <remote MAC address>, <VSGW config item name in MIB (HN or 3G)>
network. Analyze and change OMC configuration as needed for this VSGW Bearer to a unique value.
Criti cal
EMP TY
5000, 5002, 5006, 5013, 5018, 5023
85241
PPRB FRU C5 or RTM Failure
VSGW_PAYL OAD
<failure details if known>
Criti cal
EMP TY
5026, 5021, 5016, 5002, 5004, 5008
Configured value from OMC conflicts with another device on the network. Analyze and change OMC configuration as needed for this VSGW Bearer to a unique value. VSGW will still attempt to function. Replace the PPRB FRU or RTM FRU that failed.
Incoming packets may be misrouted to device with the same logical IP address.
85242
PPRB RTM Hardware Configuration Error
VSGW_PAYL OAD
Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5
85500
VSGW Log Disk is Full
1.3.6.1.4.1.16 1.3.3.10.5.14.
VSGW_PAYL OAD
Unrecogniz ed RTM type <RTM type> or version <version number> found VSGW Logs are
Criti cal
EMP TY
EMPTY
Take the installed RTM card out, if installed, and put in one with the correct RTM version. Delete old log files. If this
Either VSGW PPRB FRU or RTM FRU has failed. VSGW cannot communicate to DAPs, HLRs, and remote iDACs if PPRB FRU fails. VSGW cannot communicate to remote iDACs if RTM FRU fails. VSGW Bearer cannot function without the correct RTM.
Maj or
EMP TY
5006, 5018, 5023
R /
The VSGW Logging file space is full and the oldest
VSGW-30
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> processingF ailureEvent 85501 VSGW Log File Threshold Exceeded 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> VSGW_PAYL OAD
376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18
Full <size> FRU name: <Payload identifier> VSGW Log File Capacity Threshold Violation <percent utilized> War ning EMP TY EMPTY
alarm occurs frequently additional disk space may need to added Delete old log files. If this alarm occurs frequently additional disk space may need to added
log files are being deleted. Clear is implicit after a NE reset and possibly after a payload failure. N U The VSGW Logging disk space usage has exceeded the threshold. If the log entry arrival rate does not decrease it is likely that disk space usage will reach 100 %. Clear is implicit after a NE reset and possibly after a payload failure. The VSGW Call Trace or Registration Trace disk space is full and the oldest log files are being deleted. Clear is implicit after a NE reset and possibly after a payload failure.
R / C
85502
VSGW Trace disk is Full
VSGW_PAYL OAD
VSGW Trace disk is Full <size> FRU name: <Payload identifier>
Maj or
EMP TY
5006, 5018, 5023
85503
VSGW Trace File Threshold Exceeded
VSGW_PAYL OAD
VSGW Trace File Threshold Exceeded <percent utilized>
War ning
EMP TY
EMPTY
Delete old call trace or registration trace files. If this alarm occurs frequently additional disk space may need to added Delete old call trace or registration trace files. If this alarm occurs frequently additional disk space may need to added 1) Check the GTT tables to determine whether the specified IMSI is included in the IMSI ranges. 2) Verify the iDEN HLR
R / C
R / C
85504
Pseudo DAP cannot map to an iDEN HLR address for this IMSI
VSGW_PAYL OAD
Pseudo DAP cannot map to an iDEN HLR address for this IMSI <IMSI>
Min or
EMP TY
EMPTY
The VSGW Call Trace or Registration Trace disk space usage has exceeded the threshold. If the trace entry arrival rate does not decrease it is likely that disk space usage will reach 100 %. Clear is implicit after a NE reset and possibly after a payload failure. MS has attempted to register, but global title translation failed. As a result the Pseudo DAP was not able to determine a path to the iDEN HLR for the MS. 1) GTT IMSI ranges do not include MS. 2) GTT does not properly configure the iDEN HLR. 3)
October 30, 2008
VSGW-31

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
85505
VSGW_PAYL OAD
The iDEN HLR claimed that an IMSI is unknown <IMSI>
Min or
EMP TY
EMPTY
85507
Subscriber Not in DNS
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID>
VSGW_PAYL OAD
85508
VSGW Registration Failure Threshold Exceeded
VSGW_PAYL OAD
Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18
Subscriber Not in DNS <IMSI>
Min or
EMP TY
EMPTY
VSGW Registratio n Failure Threshold Exceeded <percent failures >
War ning
EMP TY
EMPTY
configuration in the GTT tables. 3) A `rogue' or `foreign' MS is attempting to access the system. 1) Pull up the listed IMSI at the iDEN HLR ADC. If the IDEN HLR ADC is missing, it should be added. If the record exists, verify that the IMSI is active. 2) Contact the iDEN Customer Situation Center for assistance. Check dns system for validity of subscriber. If valid, then add subscriber into the dns. 1) Troubleshoot the Network and repair. 2) Troubleshoot the SaB and PHaB and repair. 3) Troubleshoot the Home DRREP, the DAPs in the VSGW's
A 'rogue' MS has attempted to register with an invalid IMSI. Where: <IMSI>= {0x00000000000000000x9999999999999999}
MS attempted to register, but the iDEN HLR indicates that the MS is unknown. 1) MS missing from iDEN HLR. 2) Unknown. Where: <IMSI>= {0x00000000000000000x9999999999999999}
The subscriber <IMSI> is not defined in the dns. Where: <IMSI>= {0x00000000000000000x9999999999999999}
R / C
Registration failures have exceeded the threshold. Registration requires participation from the following network elements: Visited DAP, Visited iGW, DRREP, Home iGW, and the Home iHLR. 1) Links could be down. 2) NEs could be down. 3) Subscribers may not be provisioned properly (GTT and DNS).
VSGW-32
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
85520
Logging and Call Trace Disk Failure
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID>
VSGW_PAYL OAD
85400
Cannot connect to Primary NOSS Billing Server
VSGW_PAYL OAD
Logging and Call Trace Disk Failure
Maj or
EMP TY
5026, 5021, 5016, 5002, 5004, 5008
partition, and the iHLR. 4)Contact the iDEN Customer Situation Center for Assistance. Trouble shoot and replace failed disk.
R / C
Cannot connect to Primary NOSS Billing Server
Maj or
EMP TY
EMPTY
1) Troubleshoot the target Billing Server and repair. 2) Troubleshoot the Network and repair.
R / C
85401
Cannot connect to Primary or Secondary NOSS Billing Server
VSGW_PAYL OAD
Cannot connect to Primary or Secondary NOSS Billing Server
Criti cal
EMP TY
EMPTY
1) Troubleshoot the target Billing Server and repair. 2) Troubleshoot the Network and repair.
R / C
85420
Billing Server Disk Threshold Exceeded
VSGW_PAYL OAD
Billing Server Disk Threshold Exceeded <percentag e utilized>
War ning
EMP TY
EMPTY
Check that all files older than 7 days have been deleted. If they have not, contact the iDEN Customer Situation Center for assistance.
R / C
The VSGW will be unable to perform logging or call trace until the disk is replaced. Clear is implicit after a NE reset and possibly after a payload failure. The VSGW can not connect to the primary billing server in the NOSS. The VSGW will attempt to send the billing files to the Secondary NOSS billing server. Clear is implicit after a NE reset and possibly after a payload failure. The VSGW can not connect to the primary or the secondary billing server in the NOSS. The VSGW will be unable to transfer billing files until the problem is repaired. Clear is implicit after a NE reset and possibly after a payload failure. Billing disk space usage has increased above the current threshold. If the CDR input rate does not decrease it is likely that disk space usage will reach 100 % after which the oldest Billing files will be deleted. Clear is implicit after a NE reset and possibly after a payload
October 30, 2008
VSGW-33

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
85421
Billing Server Disk Full
VSGW_PAYL OAD
Billing Server Disk Full
Maj or
EMP TY
5006, 5018, 5023
85430
Billing Disk Error
VSGW_PAYL OAD
Billing Disk Error
Maj or
EMP TY
5026, 5021, 5016, 5002, 5004, 5008
85001
Payload FRU Overload Level 1
VSGW_PAYL OAD
Overload L1 Payload <Payload Identifier>, Cause: <text>
War ning
EMP TY
EMPTY
Check statistics to determine if the Billing board is running at or above the rated call profile. If this alarm occurs frequently, a larger disk may be required. Check statistics to determine if the Billing board is running at or above the rated call profile. If this alarm occurs frequently, a larger disk may be required. Trouble shoot and replace failed disk. If disk failed on primary PHaB, a failover will have occurred to the secondary PHaB Check statistics to determine if the Payload board is running at or above the rated call
failure.
R / C
Billing disk is 100% full. The oldest billing file will be deleted until enough disk space is freed to guarantee the current active billing file and the next active billing file can be created and filled with CDRs. Clear is implicit after a NE reset and possibly after a payload failure.
R / C
Clear is implicit after a NE reset and possibly after a payload failure.
R / C
VSGW processing functionality is limited based on the severity of overload. Cause value will be an enumerated value indicating: CPU Load, Ethernet Bandwidth, or Call Capacity. The Text
VSGW-34
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
profile. If this alarm occurs frequently, additional Payload Boards of this type may need to be added.
85002
VSGW_PAYL OAD
Maj or
EMP TY
EMPTY
Check statistics to determine if the Payload board is running at or above the rated call profile. If this alarm occurs frequently, additional Payload Boards of this type may need to be added.
R / C
85003
VSGW_PAYL OAD
Criti cal
EMP TY
5019
Check statistics to determine if the Payload board is running at or above the rated call profile. If this alarm occurs frequently, additional Payload Boards of this type may need to be
R / C
field supplied by the applications in the Text message parameter of the Overload Report. Alarm is raised by RM. Note that the payload identifier is SaB1, SaB2, SaB3, PHaB1, PHaB2, or LaT1. Clear is implicit after a NE reset and possibly after a payload failure. VSGW processing functionality is limited based on the severity of overload. Cause value will be an enumerated value indicating: CPU Load, Ethernet Bandwidth, or Call Capacity. The Text field supplied by the applications in the Text message parameter of the Overload Report. Alarm is raised by RM. Note that the payload identifier is SaB1, SaB2, SaB3, PHaB1, PHaB2, or LaT1. Clear is implicit after a NE reset and possibly after a payload failure. VSGW processing functionality is limited based on the severity of overload. Cause value will be an enumerated value indicating: CPU Load, Ethernet Bandwidth, or Call Capacity. The Text field supplied by the applications in the Text message parameter of the Overload Report. Alarm is raised by RM. Note that the payload identifier is SaB1, SaB2, SaB3, PHaB1, PHaB2, or LaT1.
October 30, 2008
VSGW-35

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
added.
85011
Payload FRU Initial Configuration Failure
VSGW_PAYL OAD
Initial Config Failure FRU <Payload identifier> Cause: <Text>
Criti cal
EMP TY
EMPTY
Possible configuration problem. Force VSGW to redownload configuration from OMC. Check OMC configuration for problems.
R / C
85012
Payload FRU Configuration Failure
VSGW_PAYL OAD
Config Update Failure FRU <Payload identifier> Cause: <Text>
Maj or
EMP TY
EMPTY
Possible problem with configured value from OMC. Analyze and change OMC configuration as needed.
R / C
85013
Payload FRU GTT Own Route not found
VSGW_PAYL OAD
Route not found in GTT: FRU: <Payload Identifier>, Interface:< Link Type>, UANC:<UA NC>, ID<Device ID>
Maj or
EMP TY
EMPTY
Possible configuration problem.
R / C
N(Y if true for all SaB boards)
Clear is implicit after a NE reset and possibly after a payload failure. The Payload FRU has detected a bad value in the set request or subsequent validation check. The Text contains the mib item and value of the offending parameter, or the name of the validation check that has failed. A subsequent check is required to clear this alarm. Alarm is raised by RM. Clear is implicit after a NE reset and possibly after a payload failure. The Payload FRU has detected a bad value in the set request or subsequent validation check. The Text contains the mib item and value of the offending parameter, or the name of the validation check that has failed. A subsequent check is required to clear this alarm. Alarm is raised by RM. Clear is implicit after a NE reset and possibly after a payload failure. The Payload FRU has detected a bad value in the set request or subsequent validation check. The Text contains the mib item and value of the offending parameter, or the name of the validation check that has failed. A subsequent check is required to clear this alarm. Alarm is raised by RM. Clear is implicit after a NE reset and
VSGW-36
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
85020
Payload FRU Software Failure
VSGW_PAYL OAD
Process failure FRU <Payload identifier> Cause: < Text>
Maj or
8502 1
5026, 5021, 5016, 5002, 5004, 5008, 5012
FRU will be automatically restarted.
R / C
85021
VSGW Internal Software Error
VSGW_PAYL OAD
Internal Software Error VSGW FRU may reset Cause <Text> VSGW to XCDR Link Failure: UANC = <UANC>, XCDR ID =<Remote _ID>
Maj or
8502 0
5026, 5021, 5016, 5002, 5004, 5008, 5012
85160
VSGW to XCDR Link Registration Failed Incompatible Interface Versions
VSGW_XCDR _LINK
85161
VSGW to XCDR Link Down Heartbeat Counter Exceeded
VSGW_XCDR _LINK
Device Type=5 376, ShelfID =1, BoardI D=317, LinkTy pe=5, UANC =1167772 15, LocalI D=1-20 Device Type=5 376, ShelfID =1, BoardI D=317, LinkTy pe=5, UANC
Criti cal
EMP TY
EMPTY
FRU may be automatically restarted. Contact the iDEN customer situation center for assistance. 1) Troubleshoot SaB or XCDR and reconfigure. 2)Contact the iDEN Customer Situation Center for Assistance.
R / C
possibly after a payload failure. A Payload FRU Process has failed. This resulted from an application level heartbeat failure. Alarm is raised by RM. Clear is implicit after a NE reset and possibly after a payload failure. VSGW processing functionality on FRU is interrupted until recovery. Alarm is raised by the application (signaling, bearer, piHLR, billing, or logging). Application is identified in the <text> part of the alarm code text field. 1) The XCDR responded with a version mismatch. Clear is implicit after a NE reset and possibly after a payload failure.
VSGW to XCDR Link Failure: UANC = <UANC>, XCDR ID =<Remote _ID>
Criti cal
EMP TY
5510
1) Troubleshoot the target XCDR and repair. 2) Troubleshoot the Network and repair. 3) Troubleshoot the SaB and repair.
R / C
1) The XCDR did not respond to the heartbeat request and the heartbeat counter has been exceeded. Clear is implicit after a NE reset and possibly after a payload failure.
October 30, 2008
VSGW-37

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
=1167772 15, LocalI D=1-20 communicat ionFailureE vent 85162 VSGW to XCDR Link Initialization Failure 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.1.1.1.< DeviceType>. <ShelfID>..<Link Type>.<UANC >.<LocalID> VSGW_XCDR _LINK Device Type=5 376, ShelfID =1, BoardI D=317, LinkTy pe=5, UANC =1167772 15, LocalI D=1-20 Device Type=5 376, ShelfID =1, BoardI D=3-18 VSGW to XCDR Link Failure: UANC = <UANC>, XCDR ID =<Remote _ID> Criti cal EMP TY EMPTY
85170
No Response From DNS Servers
VSGW_PAYL OAD
DNS IP Addresses = <IP address #1>, <IP address #2>, <IP address #3>
Criti cal
EMP TY
EMPTY
85180
Failed to Set Up SIP/TCP Connection
VSGW_PAYL OAD
<list of IP addresses >
Min or
EMP TY
EMPTY
4)Contact the iDEN Customer Situation Center for Assistance. 1) Troubleshoot the target XCDR and repair. 2) Troubleshoot the Network and repair. 3) Troubleshoot the SaB and repair. 4)Contact the iDEN Customer Situation Center for Assistance. 1) Troubleshoot the DNS servers and repair. 2) Troubleshoot the Network and repair. 3) Troubleshoot the SaB and repair. 4)Contact the iDEN Customer Situation Center for Assistance. 1) Troubleshoot the IAS or DRREP servers and repair. 2)
R / C
1) The XCDR did not respond to the request for the list of supported vocoders. Clear is implicit after a NE reset and possibly after a payload failure.
R / C
None of the DNS servers responded to queries. Clear is implicit after a NE reset and possibly after a payload failure.
R / C
The VSGW was unable to set up the TCP connection to the IAS or DRREP server as required in the GTT tables. This may be due to the fact that the
VSGW-38
October 30, 2008
Release SR17.0
Inst

Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
D=3-18
Troubleshoot the Network and repair. 3) Troubleshoot the SaB or PHAB and repair. 4) Contact the iDEN Customer Situation Center for Assistance.
85181
Exceeded VSGW limit on SIP/TCP connections
VSGW_PAYL OAD
EMPTY
Min or
EMP TY
EMPTY
1) Reconfigure GTT tables to reduce number of TCP connections 2) Contact the iDEN Customer
R / C
TCP connection failed (In the case of the IAS the calls are being setup using UDP. The DRREP does not support UDP). Note that if required by the GTT table for the IAS, the VSGW will attempt to setup every call destined for the IAS using TCP. The VSGW will always use TCP when communicating to the DRREP. In both cases where TCP is used the alarm is only reported once. The additional text reports the IP address of up to the most recent 5 failed TCP connections (note that the older ones may still be failed, but they will drop off the list). The list is updated as failures occur, however, the alarm is reported once per interval only if the list has changed since the last interval (in this case, the old alarm is cleared, and a new alarm containing the new list is raised). The alarm is cleared if there are no failures in the list. Clear is implicit after a NE reset and possibly after a payload failure. The VSGW was unable to set up the TCP connection to the IAS server because the VSGW is already supporting the maximum number of SIP/TCP connections. Call will be setup using UDP. The additional text specifies the remote endpoint of the
October 30, 2008
VSGW-39

Inst
Release SR17.0
Alarm Code Text
Remedy
Outage Y/N
Comments & Notes
Situation Center for Assistance. processingF ailureEvent 85530 SDGC CallSetupUnknown 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> VSGW_PAYL OAD Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 EMPTY Min or EMP TY EMPTY No action necessary R N U
requested TCP connection. Clear is implicit after a NE reset and possibly after a payload failure. Alarm is raised when a 3G domain cannot be found for at least one target UFMI in an SDGC call.
85531
SDGC CallSetupFail
VSGW_PAYL OAD
EMPTY
Min or
EMP TY
EMPTY
No action necessary
Alarm is raised when an INVITE to a 3G domain is redirected more than the configured maximum redirect count.
VSGW-40
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
2 0
Active CM Initialized
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D
VSG W_C M
2 1
Active CM Shutting Down
VSG W_C M
2 2
CM Shutting Down
VSG W_C M
2 3
CM Complete d Shutdown Successf ully CM Complete d Shutdown with errors CM Complete d
VSG W_C M
2 4
VSG W_C M
2 5
VSG W_C M
Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376,
U-D-Idl
U-E-A
EMPTY
Possibly restart trap
After board initialization, this component reached a stable state
S t a t u s N U
Note that the transition is from U-D-Idl to U-E-Idl and then to UE-A. However the U-E-Idl is a transient state that is not reported for optimization.
U-E-A
S-E-A
EMPTY
Possibly 82801
The Active Unlocked Managed Resource was shutdown.
N U
EMPTY
U-E-Imp
S-E-Imp
EMPTY
Possibly 82801
The Impaired Unlocked Managed Resource was shutdown.
N U
EMPTY
S-E-A
L-E-Idl
EMPTY
EMPTY
The Active Managed Resource completed shut down.
N U
EMPTY
S-E-A
L-D-Idl
EMPTY
EMPTY
The Active Managed Resource completed shut down with errors.
N U
EMPTY
S-E-Imp
L-E-Idl
EMPTY
EMPTY
The Impaired Managed Resource completed shut down.
N U
EMPTY
October 30, 2008
VSGW-41

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
Shutdown
eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> VSG W_C M
2 6
CM Complete d Shutdown with error
2 7
CM Locked
VSG W_C M
2 8
CM Locked
VSG W_C M
2 9
CM Locked
VSG W_C M
3 0
CM Impaired
VSG W_C M
3 1
CM Failed (Applicati on Failure)
VSG W_C M
ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2
S-E-Imp
L-D-Idl
EMPTY
EMPTY
The Impaired Managed Resource completed shut down with errors.
N U
EMPTY
U-E-A
L-E-Idl
EMPTY
Possibly 82801
The Active Managed Resource was locked.
N U
EMPTY
U-E-Imp
L-E-Idl
EMPTY
Possibly 82801
The Impaired Managed Resource was locked.
N U
EMPTY
U-D-Idl
L-D-Idl
EMPTY
EMPTY
The Disabled Managed Resource is shut-down or locked.
N U
EMPTY
U-E-A
U-E-Imp
EMPTY
Possibly 82001,82002, 82003, 82100, 82106, 82104, 82105, 82500, 82802 Possibly 82101, 82102, 82110, 82111
The Active Unlocked Managed Resource is impaired.
N U
EMPTY
U-E-A
U-D-Idl
EMPTY
The Active Unlocked Managed Resource failed. This transition occurs when the Cluster Manager identifies an internal failure and transit to Disabled. Operator
N U
EMPTY
VSGW-42
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
MOI Info (Lab el) Inst
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
3 2
VSG W_C M
U-E-Imp
U-D-Idl
EMPTY
Possibly 82101, 82102, 82110, 82111
3 3
CM Impaired
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID>
VSG W_C M
3 4
CM Recovere d
VSG W_C M
3 5
CM Unlocked
VSG W_C M
3 6
CM Unlocked
VSG W_C M
Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2
S-E-A
S-E-Imp
EMPTY
Possibly 82001,82002, 82003, 82100, 82106, 82104, 82105, 82500
intervention is required. An unlatch of the slot holding the cluster manager will cause the cluster manager to attempt to shutdown its applications before the board is removed. This may also cause this state change to occur. The Impaired Unlocked Managed Resource failed. This transition occurs when the Cluster Manager identifies an internal failure and transit to Disabled. Operator intervention is required. The Active Shuttingdown Managed Resource during the shutdown process transit into Impaired.
N U
EMPTY
N U
EMPTY
S-E-Imp
S-E-A
EMPTY
Possibly clear of 82100, 82106, 82104, 82105, 82500
S-E-Imp
U-E-Imp
EMPTY
EMPTY
The Impaired Shuttingdown Managed Resource during the shutdown process is restored due to the clear of outstanding alarms. The Impaired Shuttingdown Managed Resource during the shutdown process is unlocked.
N U
EMPTY
N U
EMPTY
S-E-A
U-E-A
EMPTY
EMPTY
The Active Shuttingdown Managed Resource during the shutdown process is unlocked.
N U
EMPTY
October 30, 2008
VSGW-43

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
3 7
CM Unlocked
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID>
VSG W_C M
3 8
CM Unlocked
VSG W_C M
3 9
CM Enabled
VSG W_C M
4 0
CM Disabled
VSG W_C M
4 1
CM Recovere d
VSG W_C M
4 2
CM Removed
VSG W_C M
Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2
L-E-Idl
U-E-A
EMPTY
EMPTY
The Locked Managed Resource is unlocked.
S t a t u s N U
Note that the transition is from L-E-Idl to U-E-Idl and then to UE-A. However the U-E-Idl is a transient state that is not reported for optimization.
L-D-Idl
U-D-Idl
EMPTY
EMPTY
The Locked Disabled Managed Resource is unlocked.
N U
EMPTY
L-D-Idl
L-E-Idl
EMPTY
EMPTY
The Locked Disabled Managed Resource is restored due to the clear of outstanding alarms.
N U
EMPTY
L-E-Idl
L-D-Idl
EMPTY
EMPTY
The Locked Managed Resource is disabled.
N U
EMPTY
U-E-Imp
U-E-A
EMPTY
The Impaired Managed Resource is restored due to the clear of outstanding alarms.
N U
EMPTY
U-E-A
U-D-Idl
EMPTY
Possibly 80262
The Active Unlocked Managed Resource has been removed. Operator intervention is removed. The component was removed without being administratively Locked. If the board is removed when its state is already U-D-Idl, no State Change Event is
N U
This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. The subsequent removal of the CM does not generate a state change event
VSGW-44
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
4 3
CM Removed
VSG W_C M
U-E-Imp
U-D-Idl
EMPTY
Possibly 80262
4 4
CM Removed
VSG W_C M
Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2
S-E-A
L-D-Idl
EMPTY
Possibly 80262
generated. The Impaired Unlocked Managed Resource has been removed. Operator intervention is required. The component was removed without being administratively Locked. The component was removed without being administratively Locked.
N U
N U
4 5
CM Removed
VSG W_C M
S-E-Imp
L-D-Idl
EMPTY
Possibly 80262
The component was removed without being administratively Locked.
N U
4 7
CM Removed
VSG W_C M
L-E-Idl
L-D-Idl
EMPTY
Possibly 80263
A Locked component was removed.
N U
4 8
Active CM Recovere d
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D
VSG W_C M
5 1
Standby CM disabled
VSG W_C M
Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376,
U-D-Idl
U-E-A
EMPTY
EMPTY
The clear of outstanding alarms restored the Usage state to "active"
N U
This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. The subsequent removal of the CM does not generate a state change event as its state is already U-D-Idl. This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. The subsequent removal of the CM does not generate a state change event This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. The subsequent removal of the CM does not generate a state change event. This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. Once the board is removed it is powered-off and its state becomes L-D-Idl. Adm state is lost. Note that the subsequent removal of the CM does not generate a state change event. Note that the transition is from U-D-Idl to U-E-Idl and then to UE-A. However the U-E-Idl is a transient state that is not reported for optimization.
U-E-Idl
U-D-Idl
EMPTY
Possibly 80250
During the shutdown process a CM lost contact with the other
N U
EMPTY
October 30, 2008
VSGW-45

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
(loss of heartbeat )
eviceType>.< ShelfID>.<Boa rdID>
ShelfID =1, BoardI D=1-2
5 3
Standby CM disabled (loss of heartbeat ) Active CM Initialized
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D
VSG W_C M
5 5
VSG W_C M
6 0
Standby CM Initialized
VSG W_C M
6 1
VSG W_C M
6 2
Standby CM Unlocked
VSG W_C M
6 3
Standby CM Locked
VSG W_C M
Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376,
L-E-Idl
L-D-Idl
EMPTY
Possibly 80250
CM. An unlatch of the slot holding the cluster manager will cause the cluster manager to attempt to shutdown its applications before the board is removed. This may also cause this state change to occur. During the shutdown process a CM lost contact with the other CM.
N U
EMPTY
L-D-Idl
U-E-A
EMPTY
N U
This represents the case where the board had been locked, was reset, and is now operational.
U-D-Idl
U-E-Idl
EMPTY
EMPTY
N U
The board is now acting as a standby to backup the active cluster manager.
L-D-Idl
U-E-Idl
EMPTY
EMPTY
N U
This represents the case where the board had been locked, was reset, and is now acting as a standby to backup the active cluster manager.
L-E-Idl
U-E-Idl
EMPTY
EMPTY
The standby cluster manager has become unlocked.
N U
U-E-Idl
L-E-Idl
EMPTY
EMPTY
The standby cluster manager has become locked.
N U
VSGW-46
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
eviceType>.< ShelfID>.<Boa rdID> esmrStateCh angeEvent 6 4 Standby CM Takeover 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> VSG W_C M
6 6
Standby CM Recovere d
VSG W_C M
1 0 0
IPSB Initialized
VSG W_IP SB
1 0 1
IPSB Removed
VSG W_IP SB
1 0 2
IPSB Removed
VSG W_IP SB
1 0 3
IPSB Inserted
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa
VSG W_IP SB
ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=1-2 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID =1,
U-E-Idl
U-E-A
EMPTY
The standby cluster manager has taken over as an active cluster manager.
N U
A restart trap is generated on this transition.
U-D-Idl
U-E-Idl
EMPTY
EMPTY
The failed cluster manager has recovered and is now the standby.
N U
U-D-Idl
U-E-A
EMPTY
EMPTY
N U
U-E-A
U-D-Idl
EMPTY
EMPTY
The component was removed
N U
This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management links are lost.
U-E-Imp
U-D-Idl
EMPTY
EMPTY
The component was removed when the IPSB was impaired.
N U
This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management functions are lost.
U-D-Idl
U-E-A
EMPTY
EMPTY
The component was inserted and after initialization reached the stable state.
N U
This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management links is not ready
October 30, 2008
VSGW-47

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s when this event is generated.
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
rdID>
1 0 4
IPSB Redunda nt Links Failure
VSG W_IP SB
1 0 5
IPSB Link Failure
VSG W_IP SB
1 0 6
IPSB Recovere d
VSG W_IP SB
1 0 7
IPSB Impaired
VSG W_IP SB
1 0 8
IPSB Failure
VSG W_IP SB
1 0 9
IPSB Failure
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.<
VSG W_IP SB
BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID
U-E-Imp
U-D-Idl
EMPTY
Possibly 81001
Both Physical Connection Failed (Gigabit interface)
N U
This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management links is not ready when this event is generated.
U-E-A
U-E-Imp
EMPTY
Possibly 81000
One of the Physical Connection Failed (Gigabit interface)
N U
EMPTY
U-E-Imp
U-E-A
EMPTY
Possibly clear of 81000
The clear of outstanding link alarms restored the Usage state to "active"
N U
EMPTY
U-D-Idl
U-E-Imp
EMPTY
The clear of outstanding link alarms restored the Usage state to Impaired
N U
Note that the transition is from U-D-Idl to U-E-Idl and then to UE-lm. However the U-E-Idl is a transient state that is not reported for optimization.
U-E-A
U-D-Idl
EMPTY
Possibly 80220
Heartbeat failure
N U
This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management links may not be ready when this event is generated. This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available,
U-E-Imp
U-D-Idl
EMPTY
Possibly 80220
Heartbeat failure on the Impaired IPSB
N U
VSGW-48
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
ShelfID>.<Boa rdID>
1 1 0
IPSB Recovere d
VSG W_IP SB
1 1 1
IPSB Impaired
VSG W_IP SB
2 0 0
PSFT Initialized
VSG W_P SFT
2 0 1
PSFT Removed
VSG W_P SFT
2 0 2
PSFT Failed
VSG W_P SFT
2 0 3
PSFT Inserted
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D
VSG W_P SFT
=1, BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=2627 Device Type=5 376, ShelfID =1, BoardI D=101103 Device Type=5 376, ShelfID =1, BoardI D=101103 Device Type=5 376, ShelfID =1, BoardI D=101103 Device Type=5 376,
management links may not be ready when this event is generated. U-D-Idl U-E-A EMPTY Possibly clear of 80220 Heartbeat restored N U Note that the transition is from U-D-Idl to U-E-Idl and then to UE-A. However the U-E-Idl is a transient state that is not reported for optimization.
U-D-Idl
U-E-Imp
EMPTY
Heartbeat restored one physical connection is still failing
N U
Note that the transition is from U-D-Idl to U-E-Idl and then to UE-Imp. However the U-E-Idl is a transient state that is not reported for optimization.
U-D-Idl
U-E-A
EMPTY
EMPTY
After component initialization, this component reached a stable state
N U
U-E-A
U-D-Idl
EMPTY
Possibly 80261
The component was removed from the slot.
N U
U-E-A
U-D-Idl
EMPTY
Possibly 80200, 80201, 80205, 80206, 80211,80212
A failure was identified.
N U
If the PSFT was already in U-DI, this state change event is not generated. Note that PSFTs have no latch, and that is why this event is generated for the physical removal or insertion of the PSFT rather than the normal latch event. If the PSFT is removed after the failure no state change event is generated.
U-D-Idl
U-E-A
EMPTY
The component was reinserted and no outstanding fault exist
N U
Note that the transition is from U-D-Idl to U-E-Idl and then to UE-A. However the U-E-Idl is a
October 30, 2008
VSGW-49

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s transient state that is not reported for optimization. Note that PSFTs have no latch, and that is why this event is generated for the physical removal or insertion of the PSFT rather than the normal latch event. Note that the transition is from U-D-Idl to U-E-Idl and then to UE-A. However the U-E-Idl is a transient state that is not reported for optimization. Note that 211,212 are generated if a Fan Tray is configured to replace a PSFT. Note that the transition is from U-D-Idl to U-E-Idl and then to UE-A. However the U-E-Idl is a transient state that is not reported for optimization.
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
eviceType>.< ShelfID>.<Boa rdID>
ShelfID =1, BoardI D=101103
2 0 4
PSFT Recovere d
VSG W_P SFT
3 0 0
Active AMC Initialized
VSG W_A MC
3 0 1
Standby AMC Initialized
VSG W_A MC
3 0 2
Active AMC Failed
VSG W_A MC
3 0 3
Standby AMC Failed
VSG W_A MC
Device Type=5 376, ShelfID =1, BoardI D=101103 Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI D=29-
U-D-Idl
U-E-A
EMPTY
Possibly clear of 80200, 80201,80202,80 203, 80205, 80206, 80211, 80212
The error condition(s) was removed.
N U
U-D-Idl
U-E-A
EMPTY
EMPTY
After AMC initialization, this component reached a stable state
N U
U-D-Idl
U-E-Idl
EMPTY
EMPTY
N U
EMPTY
U-E-A
U-D-Idl
EMPTY
Possibly 80230
N U
EMPTY
U-E-Idl
U-D-Idl
EMPTY
Possibly 80230
N U
EMPTY
VSGW-50
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
3 0 4
AMC Recovere d
VSG W_A MC
3 0 5
Standby AMC Recovere d
VSG W_A MC
3 0 6
Idle (Standby) AMC goes active
VSG W_A MC
3 0 7
Active AMC goes Standby
VSG W_A MC
3 0 8
Active AMC Removed
VSG W_A MC
3 0 9
Idle (Standby) AMC Removed
VSG W_A MC
30 Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI
U-D-Idl
U-E-A
EMPTY
N U
U-D-Idl
U-E-Idl
EMPTY
N U
EMPTY
U-E-Idl
U-E-A
EMPTY
EMPTY
The standby AMC became the active AMC
N U
EMPTY
U-E-A
U-E-Idl
EMPTY
EMPTY
The active AMC became the standby AMC
N U
EMPTY
U-E-A
U-D-Idl
EMPTY
Possibly 80261
N U
EMPTY
U-E-Idl
U-D-Idl
EMPTY
Possibly 80261
N U
EMPTY
October 30, 2008
VSGW-51

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
3 1 0
AMC Inserted
VSG W_A MC
5 0 0
5 0 1
5 0 2
Payload disabled during shutdown (loss of heartbeat ) Payload disabled during shutdown (loss of heartbeat ) Payload disabled (loss of heartbeat )
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14.
VSG W_P AYLO AD
VSG W_P AYLO AD
VSG W_P AYLO AD
5 0 3
Payload disabled (loss of heartbeat )
VSG W_P AYLO AD
5 0 4
Payload disabled (loss of heartbeat )
VSG W_P AYLO AD
5 0
Payload disabled
VSG W_P
D=2930 Device Type=5 376, ShelfID =1, BoardI D=2930 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5
U-D-Idl
U-E-Idl
EMPTY
The standby component was reinserted
N U
EMPTY
S-E-A
L-D-Idl
EMPTY
Possibly 80240, 80262,81100
During the shutdown process the management framework lost contact with the payload.
N U
EMPTY
S-E-Imp
L-D-Idl
EMPTY
Possibly 80240, 80262,81100
N U
EMPTY
U-E-Idl
U-D-Idl
EMPTY
Possibly 80240, 80262,81100
The management framework lost contact with the payload.
N U
EMPTY
U-E-A
U-D-Idl
EMPTY
Possibly 80240, 80262,81100
N U
EMPTY
U-E-Imp
U-D-Idl
EMPTY
Possibly 80240, 80262,81100
N U
EMPTY
L-E-Idl
L-D-Idl
EMPTY
Possibly 80240, 80262,81100
The management framework lost contact
N U
EMPTY
VSGW-52
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
(loss of heartbeat )
1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.1.1.1.< DeviceType>. <ShelfID>..<Link Type>.<UANC >.<LocalID>
AYLO AD
6 0 0
Link Disabled due to Payload failure
VSG W_Pi HLR_ DAP_ LINK
6 0 0
VSG W_D AP_D AP_LI NK
6 0 0
VSG W_D AP_i HLR_ LINK
376, ShelfID =1, BoardI D=3-18 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=1, UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=2, UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=3,
with the payload.
U-E-A
U-D-Idl
500..506
Possibly 81100
The payload failed, all associated links are disabled.
N U
Links have only two states U-EA or U-D-Idl. The State change is generated for each link that was still U-E-A when the board that managed the link stopped answering to heartbeat. Only links that were successfully registered in the Link Table are reported.
U-E-A
U-D-Idl
500..506
Possibly 81100
N U
U-E-A
U-D-Idl
500..506
Possibly 81100
N U
October 30, 2008
VSGW-53

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
6 0 0
VSG W_ID AC_I DAC_ LINK
6 0 0
VSG W_X CDR_ LINK
1 0 0 1 1 0 0 3
VSGW is Locked
VSGW is Locked
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.<
VSG W
VSG W
UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=4, UANC= 1167772 15, LocalID =1-800 Device Type=5 376, ShelfID =1, BoardI D=317, LinkTyp e=5, UANC= 1167772 15, LocalID =1-20 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3
U-E-A
U-D-Idl
500..506
Possibly 81100
N U
U-E-A
U-D-Idl
500..506
Possibly 81100
N U
U-D-Idl
L-D-Idl
5012, 29
EMPTY
S-E-A
L-D-Idl
5004, 24
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
The VSGW transits to L-D-Idl when the following condition is true: a) All SaB Boards are L-D-Idl The VSGW transits to L-D-Idl when the following condition is true: a) All SaB Boards
Y U
EMPTY
Y U
EMPTY
VSGW-54
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 0 0 4 1 0 0 6
VSGW is Locked
VSGW is Disabled
LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
VSG W
00 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00
S-E-Imp
L-D-Idl
5008, 26
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520 Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
L-E-Idl
L-D-Idl
5002, 40
1 0 1 0
VSGW is Disabled
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
Device Type =5376, LoID=3 00
U-E-A
U-D-Idl
31, 42, 51, 101, 104, 108, 201, 202, 5002, 5016, 5021, 5302, 5502, 5507, 5510
1 0 6 7
VSGW is Disabled
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
U-E-Idl
U-D-Idl
32, 43, 52, 101, 102, 104, 108, 109, 201, 202,5002, 5021
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520, 80200, 80201, 80202, 80203, 80205, 80206, 80211, 80212, 80261, 80262, 82101, 82102, 82110, 82111 Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520, 82001, 82002, 82003, 82100, 82104, 82105, 82106, 82500, 80262
1 0 1 2
VSGW is Disabled
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
U-E-Imp
U-D-Idl
32, 43, 52, 101, 102, 104, 108, 109, 201, 202, 5016, 5021, 5026, 5302, 5502, 5507
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520, 82001, 82002, 82003, 82100,
are L-D-Idl The VSGW transits to L-D-Idl when the following condition is true: a) All SaB Boards are L-D-Idl The VSGW transits to L-D-Idl when all the SaB boards are locked at least one of the following conditions is true: a) at least one SaB is L-D-Idl c) The CM-Group is U-D-Idl or L-D-Idl d) The IPSBGroup is U-D-Idl or LD-Idl e) The PSFTGroup is U-D-Idl or LD-Idl The VSGW transits to U-D-Idl when at least one of the following conditions is true: a) All SaB Boards are disabled and at least one is unlocked c) The CM-Group is U-D-Idl d) The IPSB-Group is UD-Idl e) The PSFTGroup is U-D-Idl The VSGW transits to U-D-Idl when at least one of the following conditions is true: a) All SaB Boards are disabled and at least one is unlocked c) The CM-Group is U-D-Idl d) The IPSB-Group is UD-Idl e) The PSFTGroup is U-D-Idl The VSGW transits to U-D-Idl when at least one of the following conditions is true: a) All SaB Boards are disabled and at least
Y U
EMPTY
Y U
EMPTY
Y U
EMPTY
Y U
EMPTY
Y U
EMPTY
October 30, 2008
VSGW-55

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) 82104, 82105, 82106, 82500, 80262 one is unlocked c) The CM-Group is U-D-Idl d) The IPSB-Group is UD-Idl e) The PSFTGroup is U-D-Idl The VSGW transits to U-D-Idl when at least one of the following conditions is true: a) All SaB Boards are disabled and at least one is unlocked c) The CM-Group is U-D-Idl d) The IPSB-Group is UD-Idl e) The PSFTGroup is U-D-Idl The VSGW transits to L-E-Idl when the following condition is true: a) All SaB boards are Locked, at least one is enabled The VSGW transits to L-E-Idl when the following condition is true: a) All SaB boards are Locked, at least one is enabled The VSGW transits to L-E-Idl when the following condition is true: a) All SaB boards are Locked, at least one is enabled The VSGW transits to L-E-Idl when the following condition is true: a) All SaB boards are Locked, at least one is enabled The VSGW transits to L-E-Idl when the following condition is true: a) All SaB boards are Locked, at least one is enabled The VSGW transits to C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
1 0 1 5
VSGW is Unlocked
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
L-D-Idl
U-D-Idl
32, 38, 43, 44, 45, 46, 47, 54, 101, 102, 104, 108, 109, 201, 202, 5001
Possibly 200, 201, 202, 203, 205, 206, 211, 212, 220, 261, 262, 263, 1001, 2101, 2102, 2110, 2111
Y U
EMPTY
1 0 2 0
VSGW is Locked
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16
VSG W
Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00 Device
U-E-A
L-E-Idl
5014, 5502, 5402, 5507, 5302, 27, 5510
Possibly 82801
Y U
EMPTY
1 0 6 9
VSGW is Locked
VSG W
U-E-Idl
L-E-Idl
5020
EMPTY
Y U
EMPTY
1 0 2 2
VSGW is Locked
VSG W
U-E-Imp
L-E-Idl
5024, 28
Possibly 82801
Y U
EMPTY
1 0 2 3
VSGW is Locked
VSG W
S-E-A
L-E-Idl
5004, 5005, 23
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
Y U
EMPTY
1 0 2 4
VSGW is Locked
VSG W
S-E-Imp
L-E-Idl
5008, 5009, 25
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
Y U
EMPTY
esmrStateCh
VSGW
VSG
L-D-Idl
L-E-Idl
5000, 39
EMPTY
Y U
EMPTY
VSGW-56
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 2 5
Recovere d
1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
Type =5376, LoID=3 00 Device Type =5376, LoID=3 00 U-E-Imp S-E-Imp 5009, 5025, 22 Possibly 82801
1 0 3 2
VSGW is Shutting Down
VSG W
1 0 3 3
VSGW is Impaired
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
S-E-A
S-E-Imp
5006, 5009, 33
Possibly 85210, 85211, 85213, 85214, 85216, 82001, 82002, 82003, 82100, 82104, 82105, 82106, 82500
1 0 4 0
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
U-E-A
S-E-A
5014, 5015, 5502, 5402, 5507, 5302, 21, 5510
Possibly 82801
1 0 4 4
VSGW Recovere d
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
S-E-Imp
S-E-A
5009, 5010, 34
1 0 5 0
VSGW is Impaired
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
U-E-A
U-E-Imp
30, 105, 5018
1 0 6
VSGW is Impaired
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D
VSG W
Device Type =5376,
U-E-Idl
U-E-Imp
5023
Possibly 81000, 82001, 82002, 82003, 82100, 82104, 82105, 82106, 82500, 82802, 85210, 85211, 85213, 85214, 85216 Possibly 85210, 85211, 85213, 85214, 85216
L-E-Idl when the following condition is true: a) All SaB boards are Locked, at least one is enabled The VSGW transits to S-E-Imp when the following condition is true: a) One or more SaB boards are S-EImp, and remaining SaBs are locked The VSGW transits to S-E-Imp when the following condition is true: a) One or more SaB boards are S-EImp, and remaining SaBs are locked and any other board transitions to U-E-Imp or U-D-Idl The VSGW transits to S-E-A when the following condition is true: a) One or more SaB boards are S-E-A, and remaining SaBs are locked The VSGW transits to S-E-A when the following condition is true: a) One or more SaB boards are S-E-A, and remaining SaBs are locked The VSGW transits to U-E-Imp when any board is not (U-E-A, UE-Idl)
Y U
EMPTY
Y U
EMPTY
N U
EMPTY
N U
EMPTY
N U
EMPTY
The VSGW transits to U-E-Imp when any board is not (U-E-A, U-
N U
EMPTY
October 30, 2008
VSGW-57

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
8 esmrStateCh angeEvent 1 0 5 1 VSGW is Impaired
eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
LoID=3 00 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00
E-Idl) U-D-Idl U-E-Imp 111 Possibly clear of 80220 The VSGW transits to U-E-Imp when any board is not (U-E-A, UE-Idl) and none of the disabling conditions listed in 1010 are true The VSGW transits to U-E-Imp when any board is not (U-E-A, UE-Idl) and none of the conditions listed in 1032 are true The VSGW transits to U-E-A when all the following conditions are true: a) At least one SaB board is U-E-A and the rest are U-E-Idl b) the PSFT group is U-E-A c) The CMGroup is U-E-A d) The IPSB-Group is U-E-A The VSGW transits to U-E-A when all the following conditions are true: a) At least one SaB board is U-E-A and the rest are U-E-Idl b) the PSFT group is U-E-A c) The CMGroup is U-E-A d) The IPSB-Group is U-E-A The VSGW transits to U-E-A when all the following conditions are true: a) At least one SaB board is U-E-A and the rest are U-E-Idl b) the PSFT group is U-E-A c) The CMGroup is U-E-A d) The IPSB-Group is U-E-A The VSGW transits to U-E-A when all the following conditions are N U EMPTY
1 0 5 4
VSGW is Unlocked
VSG W
S-E-Imp
U-E-Imp
35, 105, 5011
Possibly 81000
N U
EMPTY
1 0 6 0
VSGW Recovere d
VSG W
U-D-Idl
U-E-A
20, 48, 100, 103, 107, 110, 5013, 5022, 5301, 5501, 5506
N U
EMPTY
1 0 7 4
VSGW is Active
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
U-E-Idl
U-E-A
5501, 5301, 5506, 5022
EMPTY
N U
EMPTY
1 0 6 2
VSGW Recovere d
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
U-E-Imp
U-E-A
41, 106, 5027
Possibly clear of 82100, 82104, 82105, 82106, 82500, 81000
N U
EMPTY
1 0 6
VSGW is Unlocked
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D
VSG W
Device Type =5376,
S-E-A
U-E-A
36, 5007
EMPTY
N U
EMPTY
VSGW-58
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
eviceType>.< LoID>
LoID=3 00
1 0 7 0 1 0 7 1 1 0 7 2 1 0 7 3 1 0 7 5
VSGW is Idle
VSGW recovered
VSGW is Unlocked
VSGW is Idle
VSGW is Unlocked
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
VSG W
VSG W
VSG W
VSG W
Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00 Device Type =5376, LoID=3 00
U-D-Idl
U-E-Idl
5013
EMPTY
U-E-Imp
U-E-Idl
5029
EMPTY
L-E-Idl
U-E-Idl
5003
EMPTY
U-E-A
U-E-Idl
5502, 5507, 5302, 5017, 5510
Possibly 85200, 85102, 85103, 85110
L-E-Idl
U-E-Imp
1068, 1069, 1072
Possibly 92801
1 0 7 6
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
U-D-Idl
S-E-Imp
1068, 1069, 1072
Possibly 92801
true: a) At least one SaB board is U-E-A and the rest are U-E-Idl b) the PSFT group is U-E-A+K75 c) The CMGroup is U-E-A d) The IPSB-Group is U-E-A The VSGW transits to U-E-Idl when all the following conditions are true: a) All SaB boards are U-E-Idl The VSGW transits to U-E-Idl when all the following conditions are true: a) All SaB boards are U-E-Idl The VSGW transits to U-E-Idl when all the following conditions are true: a) All SaB boards are U-E-Idl The VSGW transits to U-E-Idl when all the following conditions are true: a) All SaB boards are U-E-Idl The VSGW transits to U-E-Imp when the following conditions is true: a)At least one board or PSU/Fan is not operational (not UE-A,U-E-I) and b) at least one Payload board is unlocked. The VSGW transitions to S-E-Imp when at least one of the following conditions is true: a) One or more Payload boards are SE-Imp, and remaining Payload Boards are locked. b) At least one IPSB, CM, or PSU/FAN is not operational (not
N U
EMPTY
N U
EMPTY
N U
EMPTY
N U
EMPTY
Y U
EMPTY
Y U
EMPTY
October 30, 2008
VSGW-59

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) U-E-A,U-E-I) (and the payload are S-E-A or S-E-Imp) The VSGW transitions to U-D-I when at least one of the following conditions is true: a) All Payload Board Boards are disabled and at least one is unlocked b) The CMGroup is U-D-I c) The IPSB-Group is U-D-I d) The PSFT-Group is U-D-I The VSGW transitions to S-E-A when at least one of the following conditions is true: a) One or more Payload boards are S-E-A, and remaining Payload boards are locked. The VSGW transitions to U-D-I when at least one of the following conditions is true: a) All Payload Board Boards are disabled and at least one is unlocked b) The CMGroup is U-D-I c) The IPSB-Group is U-D-I d) The PSFT-Group is U-D-I The board associated with the link container has become Enabled and all of its registered links (if any) remain Disabled. The board associated with the link container has become Disabled and all of its registered links (if any) remain Disabled. C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
1 0 7 7
VSGW is Unlocked
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
S-E-Imp
U-D-Idl
1068, 1069, 1072
Possibly 92801
Y U
EMPTY
1 0 7 8
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
U-D-Idl
S-E-A
1068, 1069, 1072
Possibly 92801
Y U
EMPTY
1 0 7 9
VSGW is Unlocked
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.7.2.1.1.1.<D eviceType>.< LoID>
VSG W
S-E-A
U-D-Idl
1068, 1069, 1072
Possibly 92801
Y U
EMPTY
1 2 0 0
Board Enabled, all links Disabled
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>.
VSG W_LI NK_C ONT
U-D-Idl
U-E-Idl
EMPTY
EMPTY
N U
OMC-R does not do any polling, all links for that board are automatically suppressed to UEI.
1 2 0 1
Board Disabled, all links Disabled
VSG W_LI NK_C ONT
U-E-Idl
U-D-Idl
EMPTY
EMPTY
N U
OMC-R does not do any polling, all links for that board are automatically suppressed to UDI.
VSGW-60
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
C h a n g e
Comments & Notes
1 2 0 2 1 2 0 3 1 2 0 4 1 2 0 5 1 2 0 6 1 2 0 7
All links Enabled
All links Deregiste red/Disabl ed Link Disabled
Last Disabled link Enabled Board Disabled, all links Idle Board Enabled, one or more links Disabled Link Enabled
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16
VSG W_LI NK_C ONT VSG W_LI NK_C ONT VSG W_LI NK_C ONT VSG W_LI NK_C ONT VSG W_LI NK_C ONT VSG W_LI NK_C ONT
ShelfID =1, BoardI D=3-17 ShelfID =1, BoardI D=3-17 ShelfID =1, BoardI D=3-17 ShelfID =1, BoardI D=3-17 ShelfID =1, BoardI D=3-17 ShelfID =1, BoardI D=3-17
U-E-Idl
U-E-A
EMPTY
EMPTY
The last remaining link in the container that was Disabled becomes Enabled. The last remaining link in the container that was Enabled either becomes Disabled or is deregistered. All links are Enabled and one becomes Disabled.
S t a t u s N U
OMC-R does not do any polling, all links for that board are automatically suppressed to UEA. OMC-R does not do any polling, all links for that board are automatically suppressed to UEI. OMC-R polls to determine which links under that Board Link Container is not UEA.
U-E-A
U-E-Idl
EMPTY
EMPTY
N U
U-E-A
U-E-Imp
EMPTY
EMPTY
N U
U-E-Imp
U-E-A
EMPTY
EMPTY
All but one link is Disabled and then that link becomes Enabled.
N U
OMC-R does not do any polling, all links for that board are automatically suppressed to UEA. OMC-R does not do any polling, all links for that board are automatically suppressed to UDI. OMC-R polls to determine which links under that Board Link Container is not UEA.
U-E-Imp
U-D-Idl
EMPTY
EMPTY
The board associated with the container became disabled.
N U
U-D-Idl
U-E-Imp
EMPTY
EMPTY
1 2 0 8 1 2 0 9 1 2 1 0 1
VSG W_LI NK_C ONT VSG W_LI NK_C ONT VSG W_LI NK_C ONT VSG
ShelfID =1, BoardI D=3-17 ShelfID =1, BoardI D=3-17 ShelfID =1, BoardI D=3-17 ShelfID
U-E-Idl
U-E-Imp
EMPTY
EMPTY
The board associated with the container became Enabled and some (but not all) of its links were previously Disabled. All links are Disabled and one becomes Enabled.
N U
N U
OMC-R polls to determine which links under that Board Link Container is not UEA.
All links Disabled
U-E-Imp
U-E-Idl
EMPTY
EMPTY
All but one link is Disabled and then that link becomes Disabled.
N U
OMC-R does not do any polling, all links for that board are automatically suppressed to UEI. OMC-R does not do any polling, all links for that board are automatically suppressed to UDI. OMC-R does not do any polling,
Board Disabled, all links Idle Board
U-E-A
U-D-Idl
EMPTY
EMPTY
The board associated with the container became disabled.
N U
esmrStateCh
U-D-Idl
U-E-A
EMPTY
EMPTY
The board associated
N U
October 30, 2008
VSGW-61

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s all links for that board are automatically suppressed to UEA. N U EMPTY
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
angeEvent
2 1 1 5 0 0 2
Enabled, all links Enabled Payload is disabled
1.3.3.10.5.14. 1.14.2.10.1.3. <ShelfID>. 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16
W_LI NK_C ONT VSG W_P AYLO AD
=1, BoardI D=3-17 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device L-E-Idl L-D-Idl EMPTY Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
with the container became Enabled and all of its links were previously Enabled. At least one application on the Payload has reported disabled
5 0 0 4
Payload is Disabled
VSG W_P AYLO AD
S-E-A
L-D-Idl
EMPTY
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
At least one application on the Payload has reported disabled
N U
EMPTY
5 0 0 8
Payload is Disabled
VSG W_P AYLO AD
S-E-Imp
L-D-Idl
EMPTY
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
N U
EMPTY
5 0 1 2
Payload is Locked
VSG W_P AYLO AD
U-D-Idl
L-D-Idl
EMPTY
EMPTY
Operator/Platform has locked the Payload
N U
EMPTY
5 0 0 0
Payload is enabled
VSG W_P AYLO AD
L-D-Idl
L-E-Idl
EMPTY
EMPTY
Locked Payload is no longer disabled
N U
This transition is reported at initialization if the Payload has been previously locked
5 0 0 5
Payload Locked
VSG W_P AYLO AD
S-E-A
L-E-Idl
EMPTY
EMPTY
N U
EMPTY
esmrStateCh
Payload
VSG
S-E-Imp
L-E-Idl
EMPTY
EMPTY
Operator/Platform has
N U
EMPTY
VSGW-62
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 0 9
Locked
1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID>
W_P AYLO AD
5 0 1 4
Payload Locked
VSG W_P AYLO AD
5 0 2 0
Payload Locked
VSG W_P AYLO AD
5 0 2 4
Payload Locked
VSG W_P AYLO AD
5 0 1 0
Payload recovered
VSG W_P AYLO AD
5 0 1 5
Payload is Shutting Down
VSG W_P AYLO AD
5 0 0 6
Payload is Impaired
VSG W_P AYLO AD
Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI
locked the Payload
U-E-A
L-E-Idl
5502, 5402, 5507, 5302, 5510
EMPTY
N U
EMPTY
U-E-Idl
L-E-Idl
EMPTY
EMPTY
N U
EMPTY
U-E-Imp
L-E-Idl
EMPTY
EMPTY
N U
EMPTY
S-E-Imp
S-E-A
EMPTY
EMPTY
At least one application on Payload is active and none are reporting impaired
N U
EMPTY
U-E-A
S-E-A
5502, 5402, 5507, 5302, 5510
EMPTY
Operator/Platform has shutdown the Payload
N U
EMPTY
S-E-A
S-E-Imp
EMPTY
Possibly 85210, 85211, 85213, 85214, 85216
At least one application is reporting impaired
N U
EMPTY
October 30, 2008
VSGW-63

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s EMPTY
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
5 0 2 5
Payload is Shutting Down
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.<
VSG W_P AYLO AD
5 0 0 1
Payload is Unlocked
VSG W_P AYLO AD
5 0 1 6
Payload is Disabled
VSG W_P AYLO AD
5 0 2 1
Payload is Disabled
VSG W_P AYLO AD
5 0 2 6
Payload is Disabled
VSG W_P AYLO AD
5 0 0 7
Payload Unlocked
VSG W_P AYLO AD
5 0 2 2
Payload is Active
VSG W_P AYLO AD
D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID
U-E-Imp
S-E-Imp
EMPTY
EMPTY
Operator/Platform has shutdown the Payload
N U
L-D-Idl
U-D-Idl
EMPTY
EMPTY
Operator/Platform has unlocked the Payload
N U
EMPTY
U-E-A
U-D-Idl
5502, 5402, 5507, 5302, 5510
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
N U
EMPTY
U-E-Idl
U-D-Idl
EMPTY
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
N U
EMPTY
U-E-Imp
U-D-Idl
EMPTY
Possibly 85020, 85021, 85212, 85215, 85241, 85430, 85520
N U
EMPTY
S-E-A
U-E-A
EMPTY
EMPTY
N U
EMPTY
U-E-Idl
U-E-A
5301, 5501, 5401, 5506
EMPTY
N U
Will get related link up state changes
VSGW-64
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
ShelfID>.<Boa rdID> esmrStateCh angeEvent 5 0 2 7 Payload is Active 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. VSG W_P AYLO AD
5 0 2 8
Payload no longer in Overload
VSG W_P AYLO AD
5 0 0 3
Payload Unlocked
VSG W_P AYLO AD
5 0 1 3
All Applicatio ns on Payload now Enabled All Applicatio ns on Payload are Idle
VSG W_P AYLO AD
5 0 1 7
VSG W_P AYLO AD
5 0 2 9
Payload recovered
VSG W_P AYLO AD
5 0
Payload Unlocked
VSG W_P
=1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5
U-E-Imp
U-E-A
EMPTY
EMPTY
N U
EMPTY
U-E-Imp
U-E-A
EMPTY
EMPTY
Payload overload level is below level 3
N U
EMPTY
L-E-Idl
U-E-Idl
EMPTY
EMPTY
N U
EMPTY
U-D-Idl
U-E-Idl
EMPTY
EMPTY
All applications on Payload are now enabled
N U
This transition is reported at initialization if the Payload is unlocked
U-E-A
U-E-Idl
5502, 5402, 5507, 5302, 5510
Possibly 85200, 85320, 85102, 85103, 85110
All applications on Payload are idle
N U
Will get related link down alarms and link down state changes
U-E-Imp
U-E-Idl
EMPTY
EMPTY
All applications on Payload are idle
N U
EMPTY
S-E-Imp
U-E-Imp
EMPTY
EMPTY
N U
EMPTY
October 30, 2008
VSGW-65

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
1 1
1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> Payload Impaired 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.6.2.1.1.1.<D eviceType>.< ShelfID>.<Boa rdID> 1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.1.1.1.< DeviceType>. <ShelfID>..<Link Type>.<UANC >.<LocalID>
AYLO AD
5 0 1 8
VSG W_P AYLO AD
5 0 1 9
Payload in Overload
VSG W_P AYLO AD
5 0 2 3
Payload Impaired
VSG W_P AYLO AD
5 3 0 1
iDAC LINK UP
5 3 0 2
iDAC LINK DOWN
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.1.1.1.< DeviceType>. <ShelfID>.<B
376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type=5 376, ShelfID =1, BoardI D=3-18 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=4, UANC= 1167772 15, LocalID =1-800 Device Type = 5376, ShelfID =1,
U-E-A
U-E-Imp
EMPTY
Possibly 85210, 85211, 85213, 85214, 85216
N U
EMPTY
U-E-A
U-E-Imp
EMPTY
Possibly 85003, 85231, 85233
Payload in overload level 3
N U
EMPTY
U-E-Idl
U-E-Imp
EMPTY
Possibly 85210, 85211, 85213, 85214, 85216
N U
EMPTY
U-D-Idl
U-E-A
EMPTY
EMPTY
VSGW establishes the iDAC link connection.
N U
VSGW can perform voice distribution functionality for enabled links.
U-E-A
U-D-Idl
EMPTY
Possibly 85200
VSGW has taken down the iDAC link connection.
N U
VSGW can no longer perform voice distribution functionality for enabled links.
VSGW-66
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
oardID>.<Link Type>.<UANC >.<LocalID>
5 3 0 3
iDAC Link Down Removed From GTT
5 4 0 1
PiHLR DAP Link Up Version Check Successf ul
5 4 0 2
PiHLR DAP Link Down
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.1.1.1.< DeviceType>.
VSG W_Pi HLR_ DAP_
BoardI D=317, LinkTyp e=4, UANC= 1167772 15, LocalID =1-800 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=4, UANC= 1167772 15, LocalID =1-800 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=1, UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID
U-E-A
U-D-Idl
EMPTY
EMPTY
VSGW has taken down the iDAC-iDAC link connection due to GTT data change.
N U
iDAC removed from GTT tables.
U-D-Idl
U-E-A
EMPTY
EMPTY
VSGW establishes the PiHLR-DAP link connection.
N U
Link Version Check procedure passed.
U-E-A
U-D-Idl
EMPTY
Possibly 85320
VSGW has lost or taken down the PiHLRDAP link connection.
N U
TCP/IP connectivity lost due to dropped link at DAP end, status or version check failure. PiHLR state change to Locked or
October 30, 2008
VSGW-67

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s Disabled or Ethernet redundant port failure.
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
<ShelfID>..<Link Type>.<UANC >.<LocalID>
LINK
5 4 0 3
PiHLR DAP Link Down Removed from GTT
5 5 0 1
VSGW DAP to DAP Link Up Version Check Successf ul
5 5 0
VSGW DAP to DAP Link
1.3.6.1.4.1.16 1.3.3.10.5.14. 1.14.2.1.1.1.<
VSG W_D AP_D
=1, BoardI D=317, LinkTyp e=1, UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=1, UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=2, UANC= 1167772 15, LocalID =1-300 Device Type = 5376,
U-E-A
U-D-Idl
EMPTY
EMPTY
VSGW has taken down the PiHLR-DAP link connection due to GTT data change.
N U
DAP or PiHLR or VSGW no longer in network.
U-D-Idl
U-E-A
EMPTY
EMPTY
DAP to DAP Link Up
N U
U-E-A
U-D-Idl
EMPTY
Possibly 85103
DAP to DAP Link Down
N U
TCP/IP connectivity lost
VSGW-68
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
Down TCP Connectiv ity Lost
DeviceType>. <ShelfID>..<Link Type>.<UANC >.<LocalID>
AP_LI NK
5 5 0 3
VSGW DAP to DAP Link Down Status Check Failed
5 5 0 4
VSGW DAP to DAP Link Down Version Check Failed
5 5
VSGW DAP to
1.3.6.1.4.1.16 1.3.3.10.5.14.
VSG W_D
ShelfID =1, BoardI D=317, LinkTyp e=2, UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=2, UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=2, UANC= 1167772 15, LocalID =1-300 Device Type =
U-E-A
U-D-Idl
EMPTY
Possibly 85502
N U
Link Status Check has failed.
U-E-A
U-D-Idl
EMPTY
Possibly 85100, 85101
N U
Link Version Check procedure failed.
U-E-A
U-D-Idl
EMPTY
EMPTY
VSGW has taken down the DAP-DAP link
N U
DAP has been removed from GTT data
October 30, 2008
VSGW-69

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
0 5
DAP Link Down Removed From GTT
1.14.2.1.1.1.< DeviceType>. <ShelfID>..<Link Type>.<UANC >.<LocalID>
AP_D AP_LI NK
5 5 0 6
VSGW DAP to iHLR Link Up Version Check Successf ul
5 5 0 7
VSGW DAP to iHLR Link Down TCP Connectiv ity Lost
esmrStateCh
VSGW
1.3.6.1.4.1.16
VSG
5376, ShelfID =1, BoardI D=317, LinkTyp e=2, UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=3, UANC= 1167772 15, LocalID =1-300 Device Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=3, UANC= 1167772 15, LocalID =1-300 Device
connection due to GTT data change.
U-D-Idl
U-E-A
EMPTY
EMPTY
DAP to iHLR Link Up
N U
U-E-A
U-D-Idl
EMPTY
Possibly 85110
DAP to iHLR Link Down
N U
TCP/IP connectivity lost
U-E-A
U-D-Idl
EMPTY
EMPTY
VSGW has taken down
N U
DAP or PiHLR or VSGW no
VSGW-70
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
5 0 8
DAP to iHLR Link Down Removed From GTT
1.3.3.10.5.14. 1.14.2.1.1.1.< DeviceType>. <ShelfID>..<Link Type>.<UANC >.<LocalID>
W_D AP_i HLR_ LINK
5 5 0 9
VSGW to XCDR Link Up
VSG W_X CDR_ LINK
5 5 1 0
VSGW to XCDR Link Down
VSG W_X CDR_ LINK
Type = 5376, ShelfID =1, BoardI D=317, LinkTyp e=3, UANC= 1167772 15, LocalID =1-300 Device Type=5 376, ShelfID =1, BoardI D=317, LinkTyp e=5, UANC= 1167772 15, LocalID =1-20 Device Type=5 376, ShelfID =1, BoardI D=317, LinkTyp e=5, UANC= 1167772 15, LocalID =1-20
the VSGW - 2G iHLR link connection due to GTT data change.
longer in network.
U-D-Idl
U-E-A
EMPTY
EMPTY
VSGW to XCDR Link Up
N U
XCDR has successfully registered with the VSGW and the VSGW has received the list of vocoders from the XCDR
U-E-A
U-D-Idl
EMPTY
Possibly 85161
VSGW to XCDR Link Down
N U
XCDR has not responded to the heartbeat request and the heartbeat counter has been exceeded, or the SaB has transitioned to idle and the link is no longer active.
October 30, 2008
VSGW-71

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Lab el)
Inst
From State
To State
Comments & Notes
5 5 1 1
VSGW to XCDR Link Removed by OMC
VSG W_X CDR_ LINK
Device Type=5 376, ShelfID =1, BoardI D=317, LinkTyp e=5, UANC= 1167772 15, LocalID =1-20
U-E-A
U-D-Idl
EMPTY
EMPTY
VSGW to XCDR link has been removed via configuration change from the OMC-R
S t a t u s N U
VSGW-72
October 30, 2008
Release SR17.0
__________________________________ Events
I n s t
Alarm Code Text
S Related e Alarms v e r i t y
Remedy
O u t a g e
C h a n g e
Comments & Notes
Y S / t N a t u s n U / a This event is used to inform the OMC whenever this NE starts. This event encodes some information about the active cluster manager. The rest of the information about the system can be determined from the FRU table, which contains the same information. State information is obtained from the Logical Object that represents the NE.CP3G will not provide the value for the ROM Version and boot diagnostic. For the system description, the trap contains a fixed string. The trap is sent upon Network Element start-up before a synchronization is attempted with the OMC (via a foreground download). The trap is sent upon initialization out of reset after a re-init upgrade, indicating the completion of the upgrade. In this case, no foreground download follows the generation of the trap. The Trap may be sent also after a Cluster Manager failover, after a zero downtime upgrade, in this cases the outage time could be zero. This event encodes information from the NE Logical Object. Note that maintenance will represent the state of "not providing service". Active will be the opposite state, "providing service". The standby state is not used by the cp3g NEs.
CA Restart Trap
EMPTY
New Operate State: <operational state> New Usage State: <usage state> New Admin State: <administrative state> System ROM Version: <boot ROM version> System Load Version: <software Load version> System DB Version: <database version> System Code Version: <code version> Description: <system description> System Reset Reason: <latest reset reason> System Outage Time: <outage time since latest reset> System Reboot Time: <reboot time> System Boot Diagnostics: <boot diagnostics>
1.3.6.1.4.1. 161.3.3.10. 2.3.1.0
VSGW_STAT E
0 <text OR null>
E CA M Availability P Trap T Y
All available FRUs and other Managed Objects will report their new state
No action necessary
CA Availability Trap
EMPTY
System Sequence Number: <seq no> System Secondary ID: <secondary id> System New Mode: <mode > System Switch Time: <switch time> System Reason Code: < reason code> System Old Mode: <old mode>
EMPTY
VSGW
E <text OR M null> P T Y
E CA Restart M Trap P T Y
EMPTY
No action necessary
n U / a
October 30, 2008
VSGW-73

I n s t
Release SR17.0
Alarm Code Text
Remedy
O u t a g e
C h a n g e
Comments & Notes
Y S / t N a t u s
CA Action Status Trap
System Additional Text: <Additional text> System Reason Text: <reason text> Background Download aborted
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
VSGW
E EMPTY M P T Y
EMPTY
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
VSGW
E EMPTY M P T Y
EMPTY
1.3.6.1.4.1. 161.3.3.10. 2.10.1.1.0
VSGW
1,2 or 3
1.3.6.1.4.1. 161.3.3.10. 2.10.1.2.0
VSGW
1.3.6.1.4.1. 161.3.3.10. 2.10.1.2.0
VSGW
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
VSGW
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
VSGW
<text OR null>
<text OR null>
<text OR null>
<text OR null>
<text OR null>
EMPTY
EMPTY
No action necessary, if transfer is still required retry transfer. Contact the iDEN Customer Situation Center for assistance. Retry transfer, if problem persist contact the iDEN Customer Situation Center for assistance. No action necessary
N U
Event is generated if background download has been aborted.
N U
Event is generated if background download has failed. Action Status Info details reason of failure.
N U
Event is generated if background download has completed successfully.
EMPTY
EMPTY
No action necessary
N U
Event is generated if background download was not aborted.
EMPTY
EMPTY
No action necessary
N U
EMPTY
EMPTY
No action necessary
N U
Event is generated when OLCC switch has started.
EMPTY
EMPTY
No action necessary
N U
Event is generated when OLCC switch has aborted. Action Status info details reason for failure (reason
VSGW-74
October 30, 2008
Release SR17.0
I n s t

Alarm Code Text
Remedy
O u t a g e
C h a n g e
Comments & Notes
Y S / t N a t u s and line number in configuration file).
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
VSGW
T Y E <text OR M null> P T Y
T Y E EMPTY M P T Y
EMPTY
1.3.6.1.4.1. 161.3.3.10. 2.11.1.1.0
VSGW
Upgrade aborted
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0
VSGW
Upgrade failed
1.3.6.1.4.1. 161.3.3.10. 2.12.2.1.0
VSGW
<text OR null>
<text OR null>
<text OR null>
EMPTY
Retry to transfer the configuration file and perform an olcSwitch request. If problem persist contact the iDEN Customer Situation Center for assistance. No action necessary
N U
Event is generated when OLCC switch has failed. Action Status info details reason for failure (reason and line number in configuration file).
N U
Event is generated when OLCC switch has completed.
EMPTY
No action necessary
N U
Event is generated when upgrade has aborted. Action Status info details reason for failure.
EMPTY
Retry upgrade possibly retransferring the software load. If problem persist contact the iDEN Customer Situation Center for assistance.
N U
Event is generated in case of a failure 1) Due to Internal Errors 2) NE is in an invalid transfer/upgrade state. Event is not generated if the active CM fails and it is reset.
October 30, 2008
VSGW-75
Release SR17.0
VSGW-76
October 30, 2008
Release SR17.0
_________________________________ Alarms
Alarm Type Alarm Code OMC Text MOI Info (Id) MOI Info (Label) Inst Alarm Code Text Severity Related Alarms Related State Changes Remedy
3gXCDR
Report & Clear Outage Y/N C h a n g e S t a t u s U Comments & Notes
90200
PSU/Fan Disabled
1.3.6.1.4.1. 161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic eType>.<S helfID>.<Bo ardID>
XCDR3G_PS FT
DeviceType =5632, ShelfID=1, BoardID=10 1-103
PowerSupply Disabled<A dditional Text or null>
Critical
EMPTY
202
Replace the PSU/Fan tray.
R/C
90201
PSU/Fan Power Problem
XCDR3G_PS FT
PowerSupply Problem<A dditional Text or null>
Critical
EMPTY
202
Replace the PSU/Fan Tray.
R/C
90202
PSU/Fan Feed A Problem
XCDR3G_PS FT
PowerSupply Feed A Problem<A dditional Text or null>
Major
90203 (may precede 90200)
202 (If Alarm 90203 was also generate d)
Verify the chassis power-feed. Possibly replace the PSU/Fan Tray. Contact the iDEN Customer
R/C
Note that power supplies are N+1 redundant, so shutting down a supply is tolerable in properly loaded systems. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This means the individual outputs for each supply are outside tolerance. Power supply will shutdown. Note that power supplies are N+1 redundant, so shutting down a supply is tolerable in properly loaded systems. Clear is implicit after a NE reset and possibly after a CM switchover/failure. FeedFault indicates a failure in a DC power feed into the chassis. Either the DC power has been disconnected, or the DC power source has failed. On the 600W supplies, both A and
October 30, 2008
3gXCDR-1

Alarm Type Alarm Code OMC Text MOI Info (Id) MOI Info (Label) Inst Alarm Code Text Severity Related Alarms Related State Changes Remedy Report & Clear Outage Y/N
Release SR17.0
C h a n g e S t a t u s Comments & Notes
Situation Center for assistance.
90203
PSU/Fan Feed B Problem
XCDR3G_PS FT
PowerSupply Feed B Problem<A dditional Text or null>
Major
90202 (may precede 90200)
202 (If Alarm 90202 was also generate d)
R/C
90204
PSU/Fan Fan High
XCDR3G_PS FT
Fan High<Additi onal Text or null>
Warning
may precede 90205, 90206, 90207
EMPTY
Verify room temperature. Verify that the FAN filter is not clogged and that the fan air intake is not blocked. If the alarm is not associated to a failure in another PSU/Fan, the
R/C
B feeds are routed into each PSU, hence the separate messages. If a single feed fails (either A or B), the PSUs and system continue to operate. If both feeds fail, then the system fails. Clear is implicit after a NE reset and possibly after a CM switchover/failure. FeedFault indicates a failure in a DC power feed into the chassis. Either the DC power has been disconnected, or the DC power source has failed. On the 600W supplies, both A and B feeds are routed into each PSU, hence the separate messages. If a single feed fails (either A or B), the PSUs and system continue to operate. If both feeds fail, then the system fails. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
3gXCDR-2
October 30, 2008
Release SR17.0
Alarm Type Alarm Code OMC Text MOI Info (Id) MOI Info (Label) Inst Alarm Code Text Severity

Related Alarms Related State Changes Remedy Report & Clear Outage Y/N C h a n g e S t a t u s Comments & Notes
90205
PSU/Fan Fan Failure
XCDR3G_PS FT
Fan Failure <Additional Text or null>
Critical
sympath etic with 90206
202
room temperature is within range, and the alarm does not clears automatically contact the iDEN Customer Situation Center for assistance. Verify that the FAN filter is not clogged and that the fan air intake is not blocked. Replace the PSU/Fan Tray. Verify that the FAN filter is not clogged and that the fan air intake is not blocked. Verify room temperature. Replace the PSU/Fan Tray. Contact the iDEN Customer Situation Center for assistance.
R/C
90206
PSU/Fan Cooling Failure
XCDR3G_PS FT
PowerSupply Cooling Failure<Ad ditional Text or null>
Critical
sympath etic with 90207
202
R/C
This means either the fan is dying or a clogged filter so that the operator either has to change the fan or filter. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Cooling fault indicates a reduction in airflow from a power supply or fan tray. Each PSFT has an on-board cooling sensor that monitors airflow coming from the fan on the unit. Cooling faults and alarms can be caused by fan blockage, or fan failure, or extreme temperature in the chassis. If one PSFT is generating a cooling fault, it's most likely fan blockage or failure. But if other boards in the system are starting to heat up past their temperature thresholds, more
October 30, 2008
3gXCDR-3

Release SR17.0
90207
PSU/Fan Cooling Problem
XCDR3G_PS FT
PowerSupply Cooling Problem<A dditional Text or null>
Major
may precede 90206
EMPTY
Verify that the FAN filter is not clogged and that the fan air intake is not blocked. Replace the PSU/Fan Tray. Contact the iDEN Customer Situation Center for assistance.
R/C
90220
IPSB Failure
XCDR3G_IPS B
DeviceType =5632, ShelfID=1, BoardID=26 -27
IPSB Board Failure <Additional Text or null>
Critical
EMPTY
108 or 109
If the alarm is not cleared automatically within 1 min, reset the IPSB board. If the problem is not solved replace the IPSB board. Contact the iDEN Customer Situation
R/C
N (If two IPSB fails there will be an outage, but the alarms would not be forwarde d)
serious actions such as putting the chassis into power-inhibit mode should be considered. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Cooling problem indicates a reduction in airflow from a power supply or fan tray. Each PSFT has an on-board cooling sensor that monitors airflow coming from the fan on the unit. Cooling faults and alarms can be caused by fan blockage, or fan failure, or extreme temperature in the chassis. If one PSFT is generating a cooling problem alarm, it's most likely fan blockage or failure. Clear is implicit after a NE reset and possibly after a CM switchover/failure. The alarm is generated independently of whether the FRU has a backup that has taken over. This alarm is generated if the IPSB-Proxy is unable to heartbeat the IPSB board. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
3gXCDR-4
October 30, 2008
Release SR17.0

90221
IPSB Unlatche d
XCDR3G_IPS B
IPSB Board Unlatched< Additional Text or null>
Major
EMPTY
EMPTY
90230
AMC Failure
XCDR3G_AM C
AMC Board Failure<Ad ditional Text or null>
Critical
92110
302 or 303
90231
AMC Unlatche d
90240
Payload Failure (Lost heartbeat
1.3.6.1.4.1. 161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic eType>.<S helfID>.<Bo ardID> 1.3.6.1.4.1. 161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic
XCDR3G_AM C
AMC Board Unlatched< Additional Text or null>
Critical
92110
EMPTY
Center for assistance. If the alarm is not cleared automatically within 1 min, reset the IPSB board. If the problem is not solved replace the IPSB board. Contact the iDEN Customer Situation Center for assistance. If the alarm is not cleared automatically within 1 min, replace the AMC board. The alarm may be caused by an IPMI problem; if alarm 92110 has been generated, contact the iDEN Customer Situation Center for assistance. Relatch the AMC Board (and possibly a replacement is needed)
R/C
The alarm is generated independently of whether the FRU has a backup that has taken over. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R/C
The alarm is generated if the AMC reports a failure (as retrieved via IPMI). Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R/C
XCDR3G_PA YLOAD
DeviceType =5632, ShelfID=1, BoardID=3-
Payload Board Failure<Ad ditional Text
Critical
Payload specific alarm(s)
500 to 506
If the alarm is not cleared automatically after the board
R/C
N (Yes if all boards are
This alarm is generated if the AMC reports. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This alarm applies only to payload that are configured in the service table. Alarm
October 30, 2008
3gXCDR-5

Release SR17.0
eType>.<S helfID>.<Bo ardID>
18
or null>
90250
Cluster Manager Failure (Loss of heartbeat )
XCDR3G_CM
DeviceType =5632, ShelfID=1, BoardID=12
CM Board Failure<Ad ditional Text or null>
Critical
EMPTY
49 to 54
is reset replace the failed board. If the problem persists, contact the iDEN Customer Situation Center for assistance. This alarm is also generated if the Operator resets or removes a board. If the alarm is not cleared automatically after the board is reset replace the CM board. Contact the iDEN Customer Situation Center for assistance.
failing)
is generated as result of an heartbeat failed response or an IPMI event. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R/C
90260
Configur ed FRU Remove d
XCDR3G_CM
Cluster Manager Board Removed< Additional text or null>
Critical
possibly 90262 or 90263
EMPTY
R/C
This alarm is generated if the Cluster Manager has lost contact with the other Cluster Manager. Alarm is generated as result of an heartbeat failed response. If both CM fail all alarms may never be forwarded. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This alarm applies only to payloads that are configured in the service table, IPSBs, and the CMs. Does not apply to payloads that are not configured. Does not apply to PSU/FAN and AMCs. No state changes are associated to this alarm because the board went UDI when unlatched. Clear is
3gXCDR-6
October 30, 2008
Release SR17.0

90260
XCDR3G_PA YLOAD
Payload Board Removed< Additional text or null>
Critical
possibly 90262 or 90263
EMPTY
R/C
90260
XCDR3G_IPS B
IPSB Board Removed< Additional text or null>
Critical
possibly 90262
EMPTY
R/C
90261
Platform FRU Remove d
1.3.6.1.4.1. 161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic eType>.<S helfID>.<Bo
XCDR3G_PS FT
PowerSupply Removed< Additional text or null>
Major
EMPTY
201
R/C
implicit after a NE reset and possibly after a CM switchover/failure. This alarm applies only to payloads that are configured in the service table, IPSBs, and the CMs. Does not apply to payloads that are not configured. Does not apply to PSU/FAN and AMCs. No state changes are associated to this alarm because the board went UDI when unlatched. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This alarm applies only to payloads that are configured in the service table, IPSBs, and the CMs. Does not apply to payloads that are not configured. Does not apply to PSU/FAN and AMCs. No state changes are associated to this alarm because the board went UDI when unlatched. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Depending on the number of boards that are being removed the NE state can be modified. This alarm applies only to
October 30, 2008
3gXCDR-7

Release SR17.0
ardID>
90261
Platform FRU Remove d
XCDR3G_AM C
AMC Board Removed< Additional text or null>
Major
EMPTY
308 or 309
R/C
90262
Unlocked FRU Unlatche d
XCDR3G_CM
Major
EMPTY
42 to 47
The board should have been locked before being unlatched. If the wrong board was unlatched, fasten the latches back and after the board is operational unlatch and
R/C
PSU/FAN and AMC. The AMC alarm is never generated in only one AMC is working. State changes are associated to this alarm because the FRU did not become UDI when unlatched. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Depending on the number of boards that are being removed the NE state can be modified. This alarm applies only to PSU/FAN and AMC. The AMC alarm is never generated in only one AMC is working. State changes are associated to this alarm because the FRU did not become UDI when unlatched. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Depending on the number of boards that are present the NE state can be modified. This alarm applies only to payloads that are configured in the service table, CMs and IPSBs. Does not apply to payload that are not configured, PSU/FAN and AMCs. Clear is implicit after
3gXCDR-8
October 30, 2008
Release SR17.0

remove the correct board. equipmentF ailureEvent 90262 Unlocked FRU Unlatche d 1.3.6.1.4.1. 161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic eType>.<S helfID>.<Bo ardID> XCDR3G_PA YLOAD DeviceType =5632, ShelfID=1, BoardID=318 Payload Board Unlatched< Additional text or null> Major EMPTY EMPTY The board should have been locked before being unlatched. If the wrong board was unlatched, fasten the latches back and after the board is operational unlatch and remove the correct board. The board should have been locked before being unlatched. If the wrong board was unlatched, fasten the latches back and after the board is operational unlatch and remove the correct board. No action necessary. R/C N (Yes if two CM or two IPSB are Unlatche d, however alarm is not generate d) U
90262
Unlocked FRU Unlatche d
XCDR3G_IPS B
IPSB Board Unlatched< Additional text or null>
Major
EMPTY
EMPTY
R/C
90263
Locked FRU Unlatche d
XCDR3G_CM
Minor
Applicati on specific alarm(s)
42 to 47
R/C
N (Yes if payloads do not have backup and two CM Unlatche d, however alarm is
a NE reset and possibly after a CM switchover/failure. Depending on the number of boards that are present the NE state can be modified. This alarm applies only to payloads that are configured in the service table, CMs and IPSBs. Does not apply to payload that are not configured, PSU/FAN and AMCs. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Depending on the number of boards that are present the NE state can be modified. This alarm applies only to payloads that are configured in the service table, CMs and IPSBs. Does not apply to payload that are not configured, PSU/FAN and AMCs. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This alarm applies only to payloads that are configured in the service table, CMs and IPSBs. Does not apply to payload that are not configured, PSU/FAN and AMCs. Clear is implicit after a NE reset and possibly after a CM
October 30, 2008
3gXCDR-9

Release SR17.0
90263
Locked FRU Unlatche d
XCDR3G_PA YLOAD
Minor
Payload specific alarm(s)
42 to 47
R/C
90264
Platform FRU Unlatche d
XCDR3G_AM C
AMC Board Unlatched< Additional text or null>
Major
EMPTY
EMPTY
No action necessary
R/C
not generate d) N (Yes if payloads do not have backup and two CM Unlatche d, however alarm is not generate d) N
switchover/failure.
This alarm applies only to payloads that are configured in the service table, CMs and IPSBs. Does not apply to payload that are not configured, PSU/FAN and AMCs. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
91000
IPSB Commun ication Failure
XCDR3G_IPS B
Link Failure, redundant link <linkId> is not operational <Additional text or null>
Minor
may precede 91001
105
Re-establish the physical connection ( disconnected Gigabit cable). Verify that the external router is properly working. Contact the iDEN Customer Situation Center for assistance.
R/C
91001
IPSB Commun ication Failure
1.3.6.1.4.1. 161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic
XCDR3G_IPS B
Link Failure, both redundant
Major
91000
104
Re-establish the physical connection ( disconnected
R/C
This alarm applies only to AMCs. This alarm cannot be generated if only one AMC is present. Clear is implicit after a NE reset and possibly after a CM switchover/failure. A redundant link is not operational (Gigabit interface only). Note that the lost of carrier is detected; if the connection between the IPSB and the Element Manager is lost for other causes -e.g. failure of an intermediate router-the alarm is not generated. Clear is implicit after a NE reset and possibly after a CM switchover/failure. Both redundant links are not operational (Gigabit interface only). Note that the
3gXCDR-10
October 30, 2008
Release SR17.0

-27
links are not operational <Additional text or null>
91050
Internal Commun ication Failure
XCDR3G_CM
Major
possibly sympath etic to 90220, 90250, 90260, 90262, 90264
EMPTY
91050
Internal Commun ication Failure
XCDR3G_PA YLOAD
Major
possibly sympath etic to 90220, 90250, 90260, 90262, 90264
EMPTY
Gigabit cable). Verify that the external router is properly working. If the fault condition cannot be solved, replace the IPSB board. Contact the iDEN Customer Situation Center for assistance. This alarm could be related to an IPSB or a CM board failing or being removed. If all CMs and IPSBs are not UDI Contact the iDEN Customer Situation Center for assistance. Note that after an IPSB is reinserted the alarm would not be cleared immediately. This alarm could be related to an IPSB or a CM board failing or being removed. If all CMs and IPSBs are not UDI Contact the iDEN
lost of carrier is detected; if the connection between the IPSB and the Element Manager is lost for other causes -e.g. failure of an intermediate router-the alarm is not generated. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R/C
A redundant link between the CM and a payload card is not operational. The fault condition does not affect the payload service but it reduces its reliability, possibly replace the board. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R/C
A redundant link between the CM and a payload card is not operational. The fault condition does not affect the payload service but it reduces its reliability, possibly replace the board. Clear is implicit after a NE reset and
October 30, 2008
3gXCDR-11

Release SR17.0
92001
Corrupte d Data
XCDR3G_CM
CM Corrupted Data <Additional Text or null>
Major
EMPTY
30, 33
92002
Missing Configur ation Data
XCDR3G_CM
CM Missing Configuratio n Data <Additional Text or null>
Major
EMPTY
30, 33
92003
Not enough System Resourc e
XCDR3G_CM
<Text>
Major
may precede 90250
30, 33
Customer Situation Center for assistance. Note that after an IPSB is reinserted the alarm would not be cleared immediately. Force the NE to reload the SW-load (force flag set). Replace the board if the problem persist (Possibly corrupted HD). Contact the iDEN Customer Situation Center for assistance. Force the NE to reload the SW-load (force flag set). Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance. Reset the Cluster manager, if the problem persists replace the
possibly after a CM switchover/failure.
A Configuration file is corrupted. Note that only some configuration files are monitored. This alarm also covers the event when a downloaded tar file is invalid and cannot be expanded.
A Configuration file is missing. Note that only some configuration files are monitored.
As example the CM is not able to allocate enough memory to perform some operation. Not enough interfaces, sockets
3gXCDR-12
October 30, 2008
Release SR17.0

Related Alarms Related State Changes Remedy Report & Clear Outage Y/N C h a n g e S t a t u s U Comments & Notes
92100
Cluster Manager CPU Overload
XCDR3G_CM
CM CPU Overload <Additional Text or null>
Major
may precede 90250
30, 33
board. If a standby CM exist shutdown the overloaded CM board. Contact the iDEN Customer Situation Center for assistance.
R/C
92101
CM Applicati on Startup Error
XCDR3G_CM
Application Startup Error <Additional Text or null>
Critical
may precede 90250
31, 32
If a second CM board is available reset the board. If the problem persist, contact the iDEN Customer Situation Center for assistance.
92102
CM Applicati on Failure
XCDR3G_CM
Critical
may precede 90250
31, 32
If a second CM board is available reset the board. If the problem persist, contact the iDEN
The CPU of the active cluster manager has reached a threshold at which the reliability of transactions cannot be guaranteed. CPU usage is computed as the ratio between the amount of time that the CPU has spent performing work (user and kernel mode) versus the overall time in a given interval. (i.e. (user+nice+system)* 100/(user+nice+syste m+idle) as obtained via /proc/stat). Clear is implicit after a NE reset and possibly after a CM switchover/failure. An application that implements part of the cluster manager did not start correctly. The additional text specifies the specific application. Alarm is sent after the platform has retried to solve automatically the problem. Platform has switched to the standby CM (if available). An application that implements part of the cluster manager failed. The additional text specifies the specific application. Alarm is sent after the platform has
October 30, 2008
3gXCDR-13

Release SR17.0
Customer Situation Center for assistance.
92106
CM Applicati on Failure
XCDR3G_CM
Application Failure<Ad ditional Text or null>
Major
EMPTY
30, 33
92103
Version Mismatc h
XCDR3G_CM
CM Version Mismatch <Additional Text or null>
Minor
EMPTY
EMPTY
If a second CM board is available reset the board. If the problem persist, contact the iDEN Customer Situation Center for assistance. No action necessary. Contact the iDEN Customer Situation Center for assistance.
retried to solve automatically the problem. Platform has switched to the standby CM (if available). An application that implements part of the cluster manager failed. The additional text specifies the specific application. Alarm is sent after the platform has retried to solve automatically the problem. The platform detected a version mismatch between the software load on the active CM and the standby one. The platform resync the two CM automatically to the newest version. Note that there may be times when components in the NE are temporarily executing different versions of software (during zero-downtime upgrades, etc). This alarm is only generated when the version mismatch is not expected. Clear is implicit after a NE reset and possibly after a CM switchover/failure. A LO-RM stop responding to heartbeat requests.
R/C
92104
LO Failure (Loss of heartbeat
1.3.6.1.4.1. 161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic
XCDR3G_CM
DeviceType =5632, ShelfID=1, BoardID=1-
LO Failure <Additional Text or null>
Critical
possibly LO alarms (vsgw
30, 33
The platform will restart automatically the LO, if the
3gXCDR-14
October 30, 2008
Release SR17.0

specific)
92105
Proxy Failure (Loss of heartbeat )
XCDR3G_IPS B
Critical
EMPTY
30, 33
92105
XCDR3G_PS FT
Critical
EMPTY
30, 33
92105
XCDR3G_AM C
Critical
EMPTY
30, 33
processingF
92110
CM IPMI
1.3.6.1.4.1.
XCDR3G_CM
DeviceType
CM Error
Minor
The
31, 32
alarm is not cleared within 1 min, contact the iDEN Customer Situation Center for assistance. The platform will restart automatically the Proxy, if the alarm is not cleared within 1 min, contact the iDEN Customer Situation Center for assistance. The platform will restart automatically the Proxy, if the alarm is not cleared within 1 min, contact the iDEN Customer Situation Center for assistance. The platform will restart automatically the Proxy, if the alarm is not cleared within 1 min, contact the iDEN Customer Situation Center for assistance. Contact the
A Proxy-RM stop responding to heartbeat requests. Note that is the CM application (ProxyRM) that is failing but the OID points to the proxy's one). The alarm is not providing information about the (proxied) hardware itself. A Proxy-RM stop responding to heartbeat requests. Note that is the CM application (ProxyRM) that is failing but the OID points to the proxy's one). The alarm is not providing information about the (proxied) hardware itself. A Proxy-RM stop responding to heartbeat requests. Note that is the CM application (ProxyRM) that is failing but the OID points to the proxy's one). The alarm is not providing information about the (proxied) hardware itself. A Proxy-RM identified
R/C
October 30, 2008
3gXCDR-15

Release SR17.0
ailureEvent
Applicati on Failure
161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic eType>.<S helfID>.<Bo ardID>
=5632, ShelfID=1, BoardID=12
Reading IPMI <Additional Text or null>
alarm may be reported multiple times (for each applicatio n that uses the IPMI)
92111
CM NVRAM Failure
XCDR3G_CM
CM Error NVRAM <Additional Text or null>
Critical
The alarm may be reported multiple times (for each applicatio n that access NVRAM)
31, 32
92200
Platform Black
1.3.6.1.4.1. 161.3.3.10.
XCDR3G_CM
DeviceType =5632,
Platform Black Box
Warning
EMPTY
EMPTY
iDEN Customer Situation Center for assistance. The state of the HW (identified in the additional text) cannot be correctly determined. The system behavior should be monitored using other means and the operator should not rely on state changes reported by the NE. The NE may not be able to correctly assess the state of the system. Replace the CM board which reported the alarm (note this could be generated both from the active or standby CM). Contact the iDEN Customer Situation Center for assistance. This is a normal
an error in the IPMI interface. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
Restart and Availability Traps may report inconsistent information as the NE may be unable to store time and event information.
R/C
3gXCDR-16
October 30, 2008
Release SR17.0

Box Threshol d Exceede d
5.14.1.6.2.1 .1.1.<Devic eType>.<S helfID>.<Bo ardID>
ShelfID=1, BoardID=12
Threshold Exceeded< Additional Text or null>
condition. Using the LMT or the Craft Interface freeze the current platform Black Box log, alarm is cleared after the Black Box Log is frozen.
92201
Error Writing Platform Black Box File
XCDR3G_CM
Platform Black Box Writing Error<Additi onal Text or null>
Major
EMPTY
EMPTY
92202
Error Saving
1.3.6.1.4.1. 161.3.3.10.
XCDR3G_CM
DeviceType =5632,
Platform Black Box
Minor
may precede
EMPTY
Contact the iDEN Customer Situation Center for assistance. Using the Craft Interface verify the available Disk Space on the Cluster Manager board which reported the alarm. Verify the default file and directory permissions. Delete existing Platform Black Box snapshot files. Possibly replace the CM board. Contact the iDEN
The Black Box has reached the configured limit for log entries. Additional write operations will overwrite previously entered entries. Alarm is raised only once when the threshold is reached the first time. Note that alarm means that the threshold limit has been reached not the overall size of the Black Box. Clear is implicit after a NE reset and possibly after a CM switchover/failure. The Black Box is the platform internal log.
October 30, 2008
3gXCDR-17

Release SR17.0
Platform Black Box File
Freeze Error<Additi onal Text or null>
90260
92203
Storage Capacity Exceede d
XCDR3G_CM
Storage Capacity Exceeded< Additional Text or null>
Major
EMPTY
EMPTY
92300
Cluster Manager Transitio n
1.3.6.1.4.1. 161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic eType>.<S
XCDR3G_CM
Cluster Manager transition <Additional Text or
Major
multiple alarms
multiple state changes
Customer Situation Center for assistance. Using the Craft Interface verify the available Disk Space on the Cluster Manager board that reported the alarm. Verify the default file and directory permissions. Delete existing platform Black Box snapshot files. Contact the iDEN Customer Situation Center for assistance. Using the Craft Interface verify the available Disk Space on the Cluster Manager. Delete temporary files and system logs (Refer to the NE/LINUX troubleshootin g guide). No Action necessary. The transition may have occurred due
The hard drive capacity on the active cluster manager has reached its capacity limit.
The alarm MOI represents the Cluster Manager who took over.
3gXCDR-18
October 30, 2008
Release SR17.0

helfID>.<Bo ardID>
null>
92500
Time Sync Error
XCDR3G_CM
Time Sync error<Additi onal Text or null>
Major
EMPTY
30, 33
92501
Missing NTP Server
1.3.6.1.4.1. 161.3.3.10. 5.14.1.6.2.1 .1.1.<Devic eType>.<S
XCDR3G_CM
NTP server not configured, using default IP
Major
EMPTY
30, 33
to various reasons: An internal error condition, in which case other alarms would have been generated. A zero downtime upgrade which requires a Cluster Manager reset. A lock of the active Cluster Manager. This alarm is associated with various alarms and state changes. (1) Verify a NTP server exists and is functional, (2) verify the path to the NTP server exists and that server is reachable from the NE, and (3) verify the NTP server entry at the element manager has the correct IP address of the NTP server. Add the correct IP address of the NTP server to the NTP
R/C
The platform is unable to obtain time synchronization with an NTP server. Time stamps in alarms, events, logs, and statistics files may not be aligned with the network time. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
The platform did not find an NTP entry in the DCHP/BOOTP response, and it using the OMC IP
October 30, 2008
3gXCDR-19

Release SR17.0
helfID>.<Bo ardID>
address<Ad ditional text or null>
92600
Missing Payload Configur ation
XCDR3G_CM
Missing Payload Configuratio n<Additiona l Text or null>
Minor
EMPTY
EMPTY
92601
Service Configur ation Error
XCDR3G_CM
Invalid Service Configuratio n Request<A dditional Text or null>
Major
possibly ActionSt atusTrap
EMPTY
server entry (DHCP Configuration) at the element manager. Verify that the board is being inserted in the right slot. The OLCC generated by the OMC contains specific board/service assignment, a board is inserted in a slot that is unassigned. Contact the iDEN Customer Situation Center for assistance. Contact the iDEN Customer Situation Center for assistance.
address as the address of the NTP server. The port is the default NTP port. R/C N U A payload board is attempting to initialize in the chassis but it has no entry specified in Service table MIB. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R/C
The platform has received a Service configuration request for a payload that does not match the list of service available on the platform (I.e. a matching entry Service directory does not exist). The payload will not be able to initialize. If the request is coming via the OLCC the OLCSwitch is rejected. Note that in normal condition this should never happen if the OMC ensures that the software load provided to the NE
3gXCDR-20
October 30, 2008
Release SR17.0

92700
SNMP Configur ation Error Mismatc h in SubAgen t Answers
XCDR3G_CM
SNMP Configuratio n Error Mismatch in Sub-Agent Answers<A dditional Text or null>
Major
Possibly vsgw specific alarms. Possibly Action Status Trap for an OLCC rejection
EMPTY
92701
SNMP Configur ation Error SubAgen t Timeout
XCDR3G_CM
SNMP Configuratio n Error Sub-Agent Timeout<A dditional Text null>
Minor
90206 ( reporting the failure of the payload where the subagent is running)
EMPTY
Contact the iDEN Customer Situation Center for assistance. For a SETRequest modify the value supplied to the subagents or possibly shutdown the payload(s) that returned an inconsistent answer. Retry the command after the NE management framework has recognized the FRU failure. Once the FRU is marked as failed the configuration request is not forwarded to its sub-agents. If the error persists
and the relevant service information provided in the OLCC match. This error may occur if the configuration is done manually from the LT. Clear is implicit after a NE reset and possibly after a CM switchover/failure. An SNMP get/getnext request against a MIB Object for which there are multiple owners (subagents) has yielded different responses. The additional text will provide the name of the FRU that provided different answers. Note that the platform does not know which answer is the correct one.
An SNMP get/getnext request against a MIB Object for which there are multiple owners (subagents) has timeout. This alarm is generated only if the NE management framework hasn't recognized yet that the FRU failed.
October 30, 2008
3gXCDR-21

Release SR17.0
92800
Downloa d Error
XCDR3G_CM
Download Error<Additi onal Text or null>
Minor
ActionSt atusTrap
EMPTY
92801
Downloa d aborted due to CM Adm State Change
XCDR3G_CM
Download Aborted<Ad ditional Text or null>
Major
ActionSt atusTrap
21,22, 27
92802
Replicati on Error to standby CM
XCDR3G_CM
CM Replication Error<Additi onal Text or null>
Major
EMPTY
30
contact the iDEN Customer Situation Center for assistance. Retry the transfer from the OMC, if the problem persist contact the iDEN Customer Situation Center for assistance. The Download was aborted because the CM Adm state changed to Locked. Unlock the CM and retry the transfer. If the problem persist contact the iDEN Customer Situation Center for assistance. Reset the standby CM if the problem persist contact the iDEN Customer Situation Center for assistance.
R/C
Action Status trap also reports the info to the EM. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
Action Status trap also reports the info to the EM.
R/C
processingF
92900
Redunda
1.3.6.1.4.1.
XCDR3G_CM
DeviceType
Redundanc
Major
EMPTY
EMPTY
Add/replace
The platform was unable to replicate software and/or configuration information to the standby cluster manager following a foreground/backgrou nd download to the active cluster manager. Clear is implicit after a NE reset and possibly after a CM switchover/failure. This alarm is
3gXCDR-22
October 30, 2008
Release SR17.0

ailureEvent
ncy Scheme Failure
y Scheme failure<Addi tional Text or null>
boards.
92901
No Redunda ncy available
XCDR3G_CM
No Redundanc y Available<A dditional Text or null>
Critical
EMPTY
EMPTY
Add/replace boards.
N/Y
92902
Reduced Redunda ncy available
XCDR3G_CM
Reduced Redundanc y<Additiona l Text or null>
Minor
EMPTY
EMPTY
Add/replace boards.
N/Y
92903
Unsuppo rted Redunda ncy Policy
XCDR3G_CM
Unsupporte d Redundanc y Policy<Addi tional Text or null>
Major
EMPTY
EMPTY
Contact the iDEN Customer Situation Center for assistance. This problem is related to the reception
N/Y
generated only after a failure of all standby boards that are part of a redundancy schema if there are not FRUs to support redundancy requirements. This alarm implies that there are not standby boards left. A managed resource has failed that requires a backup but no backup is available. Outage is possible depending on the role of the failed payload. Alarm is thrown when there is an active board that goes disabled and had no standby to take over for it. This alarm is generated only after a failure of a standby board that is part of a redundancy schema if there are not enough FRUs to support redundancy requirements. This alarm implies that other standby are still present but not enough to fulfill the 'M' requirement. This alarm is generated after parsing the redundancy policy. The platform will not accept a 2N configuration where N is not equal to M or where extra boards
October 30, 2008
3gXCDR-23

Release SR17.0
95001
Overload Level 1 for XCDR3G
1.3.6.1.4.1. 161.3.3.10. 5.14.1.7.2.1 .1.1.<Devic eType>.<Lo ID>
XCDR3G
DeviceType =5632, LoID=300
XCDR3G Overload L1, Cause: <text>
Warning
EMPTY
EMPTY
95002
1.3.6.1.4.1. 161.3.3.10. 5.14.1.7.2.1 .1.1.<Devic eType>.<Lo ID>
XCDR3G
Major
EMPTY
EMPTY
95003
1.3.6.1.4.1. 161.3.3.10. 5.14.1.7.2.1 .1.1.<Devic eType>.<Lo ID>
XCDR3G
Critical
EMPTY
EMPTY
of an incorrect SW load. Check statistics to determine if the XCDR3G is running at or above the rated call profile. If this alarm occurs frequently, additional DSP Boards may need to be added. Check statistics to determine if the XCDR3G is running at or above the rated call profile. If this alarm occurs frequently, additional DSP Boards may need to be added. Check statistics to determine if the XCDR3G is running at or above the rated call profile. If this alarm occurs frequently, additional DSP Boards may need to be added.
are not marked as 'u'. R/C N U XCDR3G processing functionality is limited based on the severity of overload. Cause value will be an enumerated value indicating: CPU Load, Ethernet Bandwidth, or Call Capacity. Clear is implicit after a NE reset and possibly after a CM switchover/failure. XCDR3G processing functionality is limited based on the severity of overload. Cause value will be an enumerated value indicating: CPU Load, Ethernet Bandwidth, or Call Capacity. Clear is implicit after a NE reset and possibly after a CM switchover/failure. XCDR3G processing functionality is limited based on the severity of overload. Cause value will be an enumerated value indicating: CPU Load, Ethernet Bandwidth, Call Capacity, or cannot support all vocoder combinations. Clear is implicit after a NE reset and possibly after a CM switchover/failure. The Payload FRU has detected a bad
R/C
R/C
95011
Payload FRU
1.3.6.1.4.1. 161.3.3.10.
XCDR3G_PA YLOAD
DeviceType =5632,
Initial Config
Major
EMPTY
5002, 5004,
Possible configuration
R/C
3gXCDR-24
October 30, 2008
Release SR17.0

Initial Configur ation Failure
Failure FRU <Payload identifier> Cause: <Text>
5016, 5021, 5026
problem. Force XCDR3G to re-download configuration from OMC. Check OMC configuration for problems.
95012
Payload FRU Configur ation Failure
XCDR3G_PA YLOAD
Config Update Failure FRU <Payload identifier> Cause: <Text>
Major
EMPTY
5002, 5004, 5016, 5021, 5026
R/C
95046
Initial Configur ation Failure
XCDR3G_CM
Initial Config Failure <Additional Text or null>
Major
EMPTY
EMPTY
Possible configuration problem. Force XCDR3G to re-download configuration from OMC. Check OMC configuration for problems.
R/C
value in the set request or subsequent validation check. The Text contains the MIB item and value of the offending parameter, or the name of the validation check that has failed. A subsequent check is required to clear this alarm. Alarm is raised by RM. Clear is implicit after a reset and possibly after a payload failure. The Payload FRU has detected a bad value in the set request or subsequent validation check. The Text contains the MIB item and value of the offending parameter, or the name of the validation check that has failed. A subsequent check is required to clear this alarm. Alarm is raised by RM. Clear is implicit after a reset and possibly after a payload failure. The application has detected a bad value in the set request or subsequent validation check. The Text contains the MIB item and value of the offending parameter, or the name of the validation check that has failed. A subsequent check is
October 30, 2008
3gXCDR-25

Release SR17.0
95047
Configur ation Failure
XCDR3G_CM
Config Update Failure <Additional Text or null>
Major
EMPTY
EMPTY
R/C
95020
XCDR3G Applicati on Failure
XCDR3G_PA YLOAD
Minor
95021, 95045
5021, 5016, 5026, 5002, 5004, 5008
95021
XCDR3G_PA YLOAD
Major
95020, 95045
5026, 5016, 5002, 5004, 5008
A minor internal software error occurred. Error may be automatically corrected. If problem persists contact the iDEN customer situation center for assistance. A major internal software error or application failure occurred. Error may automatically correct or application/FR U may be
R/C
required to clear this alarm. Alarm is raised by RM. Clear is implicit after a reset. The application has detected a bad value in the set request or subsequent validation check. The Text contains the MIB item and value of the offending parameter, or the name of the validation check that has failed. A subsequent check is required to clear this alarm. Alarm is raised by RM. Clear is implicit after a reset. 3GXCDR processing functionality on FRU is interrupted until recovery. Alarm is raised by the application. Application and/or failure are identified in the <text> part of the alarm code text field. Clear is implicit after a reset.
R/C
3GXCDR processing functionality on FRU is interrupted until recovery. Alarm is raised by the application. Application and/or failure are identified in the <text> part of the alarm code text field. Clear is implicit
3gXCDR-26
October 30, 2008
Release SR17.0

95045
XCDR3G_PA YLOAD
Critical
95020, 95021
5026, 5016, 5002, 5004, 5008
95048
Payload FRU Equipme nt Failure
XCDR3G_PA YLOAD
Equipment Failure <Additional Text or null>
Critical
EMPTY
5018, 5023
95040
SaB Registrati on Failure
1.3.6.1.4.1. 161.3.3.10. 5.14.1.7.2.1 .1.1.<Devic
XCDR3G
SaB Registration Failure <VSGW Id,
Major
91000, 91001, 91050
1050, 1068
automatically restarted. If problem persists contact the iDEN customer situation center for assistance. A critical internal software error or application failure occurred. Application/FR U may be automatically restarted. If problem persists contact the iDEN customer situation center for assistance. A critical equipment failure is detected within the Payload FRU. The FRU may be automatically restarted. If a restart does not correct the problem, the FRU may need to be replaced. The XCDR3G has failed to receive a response to a
after a reset.
3GXCDR processing functionality on FRU is interrupted until recovery. Alarm is raised by the application. Application and/or failure are identified in the <text> part of the alarm code text field.
3GXCDR processing functionality on FRU is interrupted until recovery. Alarm is raised by the application. Failure is identified in the <additional text> part of the alarm code text field.
R/C
VSGW Id and SaB Instance are from the XCDR-VSGWADDRESSING-MIB.
October 30, 2008
3gXCDR-27

Release SR17.0
between the XCDR3G to VSGW
eType>.<Lo ID>
SaB Instance><t ext>
95041
SaB Commun ication Failure Between the XCDR3G to VSGW
1.3.6.1.4.1. 161.3.3.10. 5.14.1.7.2.1 .1.1.<Devic eType>.<Lo ID>
XCDR3G
XCDR Resource Loading Status Request Failure <VSGW Id, SaB Instance><t ext>
Major
91000, 91001, 91050
1050, 1068
processingF
95042
XCDR3G
1.3.6.1.4.1.
XCDR3G_CM
DeviceType
Application
Minor
95043,
EMPTY
Registration Request to a VSGW SaB. Alarm is cleared when repeated Registration is successful or the IP Address of the VSGW SaB is removed from the XCDR3G. Correct communicatio n problem with VSGW SaB. Upon successful ReRegistration with VSGW SaB alarm is cleared The XCDR3G has not received a XCDR Resource Loading Status Request message from a VSGW SaB in the required period. Correct communicatio n problem with VSGW SaB. Successful ReRegistration with VSGW SaB clears alarm. A minor
Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R/C
VSGW Id and SaB Instance are from the XCDR-VSGWADDRESSING-MIB. Clear is implicit after a NE reset and possibly after a CM switchover/failure.
R/C
3GXCDR processing
3gXCDR-28
October 30, 2008
Release SR17.0

ailureEvent
Applicati on Failure
Failure <Additional Text or null>
95044
95043
XCDR3G_CM
Major
95042, 95044
EMPTY
95044
XCDR3G_CM
Critical
95042, 95043
EMPTY
internal software error occurred. Error may be automatically corrected. If problem persists contact the iDEN customer situation center for assistance. A major internal software error or application failure occurred. Error may automatically correct or application/FR U may be automatically restarted. If problem persists contact the iDEN customer situation center for assistance. A critical internal software error or application failure occurred. Application/FR U may be automatically restarted or switched to standby. If problem
functionality is interrupted until recovery. Alarm is raised by the application . Application and/or failure are identified in the <text> part of the alarm code text field. Clear is implicit after a reset.
R/C
3GXCDR processing functionality is interrupted until recovery. Alarm is raised by the application . Application and/or failure are identified in the <text> part of the alarm code text field. Clear is implicit after a reset.
3GXCDR processing functionality is interrupted until recovery. Alarm is raised by the application . Application and/or failure are identified in the <text> part of the alarm code text field.
October 30, 2008
3gXCDR-29

Release SR17.0
persists contact the iDEN customer situation center for assistance.
3gXCDR-30
October 30, 2008
Release SR17.0
__________________________________ State Changes

State Changes
R e a s o n C o d e
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
2 0
Active CM Initialized
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _CM
DeviceType=563 2, ShelfID=1, BoardID=1-2
U-D-Idl
U-E-A
EMPTY
Restart trap
2 1
Active CM Shutting Down CM Shutting Down
2 2
2 3
2 4
2 5
CM Complete d Shutdown Successf ully CM Complete d Shutdown with errors CM Complete d Shutdown CM Complete d
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy
XCDR3G _CM
U-E-A
S-E-A
EMPTY
Possibly 92801
The Active Unlocked Managed Resource was shutdown.
Note that the transition is from U-D-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. EMPTY
XCDR3G _CM
U-E-Imp
S-E-Imp
EMPTY
Possibly 92801
The Impaired Unlocked Managed Resource was shutdown.
EMPTY
XCDR3G _CM
S-E-A
L-E-Idl
EMPTY
EMPTY
The Active Managed Resource completed shut down.
EMPTY
XCDR3G _CM
S-E-A
L-D-Idl
EMPTY
EMPTY
The Active Managed Resource completed shut down with errors.
EMPTY
XCDR3G _CM
S-E-Imp
L-E-Idl
EMPTY
EMPTY
The Impaired Managed Resource completed shut down.
EMPTY
2 6
XCDR3G _CM
S-E-Imp
L-D-Idl
EMPTY
EMPTY
The Impaired Managed Resource completed shut down with errors.
EMPTY
October 30, 2008
3gXCDR-31

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
2 7
Shutdown with error CM Locked
2 8
CM Locked
2 9
CM Locked
3 0
CM Impaired
pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _CM
U-E-A
L-E-Idl
EMPTY
Possibly 92801
The Active Managed Resource was locked.
EMPTY
XCDR3G _CM
U-E-Imp
L-E-Idl
EMPTY
Possibly 92801
The Impaired Managed Resource was locked.
EMPTY
XCDR3G _CM
U-D-Idl
L-D-Idl
EMPTY
EMPTY
The Disabled Managed Resource is shut-down or locked.
EMPTY
XCDR3G _CM
U-E-A
U-E-Imp
EMPTY
3 1
XCDR3G _CM
U-E-A
U-D-Idl
EMPTY
Possibly 92001,92002, 92003, 92100, 92106, 92104, 92105, 92500, 92802 Possibly 92101, 92102, 92110, 92111
The Active Unlocked Managed Resource is impaired.
EMPTY
3 2
XCDR3G _CM
U-E-Imp
U-D-Idl
EMPTY
Possibly 92101, 92102, 92110, 92111
The Active Unlocked Managed Resource failed. This transition occurs when the Cluster Manager identifies an internal failure and transit to Disabled. Operator intervention is required. An unlatch of the slot holding the cluster manager will cause the cluster manager to attempt to shutdown its applications before the board is removed. This may also cause this state change to occur. The Impaired Unlocked Managed Resource failed. This transition occurs when the Cluster Manager identifies an internal failure and
EMPTY
EMPTY
3gXCDR-32
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
3 3
CM Impaired
3 4
CM Recovere d
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _CM
S-E-A
S-E-Imp
EMPTY
XCDR3G _CM
S-E-Imp
S-E-A
EMPTY
Possibly 92001,92002, 92003, 92100, 92106, 92104, 92105, 92500 Possibly 92100, 92106, 92104, 92105, 92500
3 5
CM Unlocked
XCDR3G _CM
S-E-Imp
U-E-Imp
EMPTY
EMPTY
3 6
CM Unlocked
XCDR3G _CM
S-E-A
U-E-A
EMPTY
EMPTY
3 7
CM Unlocked
XCDR3G _CM
L-E-Idl
U-E-A
EMPTY
EMPTY
transit to Disabled. Operator intervention is required. The Active Shuttingdown Managed Resource during the shutdown process transit into Impaired. The Impaired Shuttingdown Managed Resource during the shutdown process is restored due to the clear of outstanding alarms. The Impaired Shuttingdown Managed Resource during the shutdown process is unlocked. The Active Shuttingdown Managed Resource during the shutdown process is unlocked. The Locked Managed Resource is unlocked.
EMPTY
EMPTY
EMPTY
EMPTY
3 8
CM Unlocked
3 9
CM Enabled
4 0
CM Disabled
esmrStateCh
CM
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3
XCDR3G _CM
L-D-Idl
U-D-Idl
EMPTY
EMPTY
The Locked Disabled Managed Resource is unlocked.
Note that the transition is from L-E-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. EMPTY
XCDR3G _CM
L-D-Idl
L-E-Idl
EMPTY
EMPTY
The Locked Disabled Managed Resource is restored due to the clear of outstanding alarms. The Locked Managed Resource is disabled.
EMPTY
XCDR3G _CM
L-E-Idl
L-D-Idl
EMPTY
EMPTY
EMPTY
XCDR3G
DeviceType=563
U-E-Imp
U-E-A
EMPTY
Possibly
The Impaired Managed
EMPTY
October 30, 2008
3gXCDR-33

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
angeEvent
Recovere d
4 2
CM Removed
.3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
_CM
2, ShelfID=1, BoardID=1-2
92100, 92106, 92104, 92105, 92500 U-E-A U-D-Idl EMPTY Possibly 90262
Resource is restored due to the clear of outstanding alarms. The Active Unlocked Managed Resource has been removed. Operator intervention is removed. The component was removed without being administratively Locked. If the board is removed when its state is already U-D-Idl, no State Change Event is generated. The Impaired Unlocked Managed Resource has been removed. Operator intervention is required. The component was removed without being administratively Locked. N U This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. The subsequent removal of the CM does not generate a state change event This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. The subsequent removal of the CM does not generate a state change event as its state is already U-D-I. This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. The subsequent removal of the CM does not generate a state change event This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. The subsequent removal of
XCDR3G _CM
4 3
CM Removed
XCDR3G _CM
U-E-Imp
U-D-Idl
EMPTY
Possibly 90262
4 4
CM Removed
XCDR3G _CM
S-E-A
L-D-Idl
EMPTY
Possibly 90262
4 5
CM Removed
XCDR3G _CM
S-E-Imp
L-D-Idl
EMPTY
Possibly 90262
3gXCDR-34
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
4 7
CM Removed
XCDR3G _CM
L-E-Idl
L-D-Idl
EMPTY
Possibly 90263
A Locked component was removed.
4 8
Active CM Recovere d
XCDR3G _CM
U-D-Idl
U-E-A
EMPTY
EMPTY
The clear of outstanding alarms restored the Usage state to "active"
5 1
Standby CM disabled (loss of heartbeat )
XCDR3G _CM
U-E-Idl
U-D-Idl
EMPTY
Possibly 90250
5 3
5 5
Standby CM disabled (loss of heartbeat ) Active CM Initialized
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy
XCDR3G _CM
L-E-Idl
L-D-Idl
EMPTY
Possibly 90250
During the shutdown process a CM lost contact with the other CM. An unlatch of the slot holding the cluster manager will cause the cluster manager to attempt to shutdown its applications before the board is removed. This may also cause this state change to occur. During the shutdown process a CM lost contact with the other CM.
the CM does not generate a state change event. This State Change can be generated only if two CMs are installed and properly working; if only one CM is available, management functions are lost. Once the board is removed it is poweredoff and its state becomes L-D-Idl. Adm state is lost. Note that the subsequent removal of the CM does not generate a state change event. Note that the transition is from U-D-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. EMPTY
EMPTY
XCDR3G _CM
L-D-Idl
U-E-A
EMPTY
Restart trap
This represents the case where the board had been locked, was
October 30, 2008
3gXCDR-35

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s reset, and is now operational. The board is now acting as a standby to backup the active cluster manager. This represents the case where the board had been locked, was reset, and is now acting as a standby to backup the active cluster manager.
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
6 0
6 1
pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _CM
U-D-Idl
U-E-Idl
EMPTY
EMPTY
XCDR3G _CM
L-D-Idl
U-E-Idl
EMPTY
EMPTY
6 2
Standby CM Unlocked
6 3
Standby CM Locked
6 4
Standby CM Takeover
6 6
Standby CM Recovere d IPSB Initialized
1 0 0
XCDR3G _CM
L-E-Idl
U-E-Idl
EMPTY
EMPTY
The standby cluster manager has become unlocked.
XCDR3G _CM
U-E-Idl
L-E-Idl
EMPTY
EMPTY
The standby cluster manager has become locked.
XCDR3G _CM
U-E-Idl
U-E-A
EMPTY
Restart trap
The standby cluster manager has taken over as an active cluster manager. The failed cluster manager has recovered and is now the standby.
A restart trap is generated on this transition.
XCDR3G _CM
U-D-Idl
U-E-Idl
EMPTY
EMPTY
XCDR3G _IPSB
U-D-Idl
U-E-A
EMPTY
EMPTY
1 0 1
IPSB Removed
XCDR3G _IPSB
U-E-A
U-D-Idl
EMPTY
EMPTY
The component was removed
Note that the transition is from U-D-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management
3gXCDR-36
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 0 2
IPSB Removed
XCDR3G _IPSB
U-E-Imp
U-D-Idl
EMPTY
EMPTY
The component was removed when the IPSB was impaired.
1 0 3
IPSB Inserted
XCDR3G _IPSB
U-D-Idl
U-E-A
EMPTY
EMPTY
The component was inserted and after initialization reached the stable state.
1 0 4
IPSB Redunda nt Links Failure
XCDR3G _IPSB
U-E-Imp
U-D-Idl
EMPTY
Possibly 91001
Both Physical Connection Failed (Gigabit interface)
1 0 5
IPSB Link Failure
1 0 6
IPSB Recovere d
1 0 7
IPSB Impaired
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _IPSB
U-E-A
U-E-Imp
EMPTY
Possibly 91000
One of the Physical Connection Failed (Gigabit interface)
links are lost. This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management functions are lost. This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management links is not ready when this event is generated. This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management links is not ready when this event is generated. EMPTY
XCDR3G _IPSB
U-E-Imp
U-E-A
EMPTY
Clear of 91000
The clear of outstanding link alarms restored the Usage state to "active"
EMPTY
XCDR3G _IPSB
U-D-Idl
U-E-Imp
EMPTY
Clear of 91001
The clear of outstanding link alarms restored the Usage state to Impaired
1 0 8
IPSB Failure
XCDR3G _IPSB
U-E-A
U-D-Idl
EMPTY
Possibly 90220
Heartbeat failure
Note that the transition is from U-D-I to U-E-I and then to U-E-Imp. However the U-E-I is a transient state that is not reported for optimization. This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management
October 30, 2008
3gXCDR-37

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s links may not be ready when this event is generated. This State Change can be generated only if two IPSBs are installed and properly working; if only one IPSB is available, management links may not be ready when this event is generated. Note that the transition is from U-D-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. Note that the transition is from U-D-I to U-E-I and then to U-E-Imp. However the U-E-I is a transient state that is not reported for optimization. Note that the transition is from U-D-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. If the PSFT was already in U-D-I, this state change event is not generated. Note that PSFTs have no latch, and that is why this event is generated for the physical removal or insertion of the PSFT rather than the normal latch event. If the PSFT is removed after the failure no state change event is
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
1 0 9
IPSB Failure
XCDR3G _IPSB
U-E-Imp
U-D-Idl
EMPTY
Possibly 90220
Heartbeat failure on the Impaired IPSB
1 1 0
IPSB Recovere d
XCDR3G _IPSB
U-D-Idl
U-E-A
EMPTY
Clear of 90220
Heartbeat restored
1 1 1
IPSB Impaired
XCDR3G _IPSB
U-D-Idl
U-E-Imp
EMPTY
Clear of 90220
Heartbeat restored one physical connection is still failing
2 0 0
PSFT Initialized
XCDR3G _PSFT
DeviceType=563 2, ShelfID=1, BoardID=101103
U-D-Idl
U-E-A
EMPTY
EMPTY
After component initialization, this component reached a stable state
2 0 1
PSFT Removed
XCDR3G _PSFT
U-E-A
U-D-Idl
EMPTY
Possibly 90261
2 0 2
PSFT Failed
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy
XCDR3G _PSFT
DeviceType=563 2, ShelfID=1, BoardID=101-
U-E-A
U-D-Idl
EMPTY
Possibly 90200, 90201, 90205, 90206,
3gXCDR-38
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
2 0 3
PSFT Inserted
pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
103 XCDR3G _PSFT DeviceType=563 2, ShelfID=1, BoardID=101103 U-D-Idl U-E-A EMPTY
90211,90212 Clear of 90261 The component was reinserted and no outstanding fault exist N U
generated. Note that the transition is from U-D-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. Note that PSFTs have no latch, and that is why this event is generated for the physical removal or insertion of the PSFT rather than the normal latch event. Note that the transition is from U-D-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. Note that 211,212 are generated if a Fan Tray is configured to replace a PSFT. Note that the transition is from U-D-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. EMPTY
2 0 4
PSFT Recovere d
XCDR3G _PSFT
U-D-Idl
U-E-A
EMPTY
Clear of 90200, 90201,90202, 90203, 90205, 90206, 90211, 90212
3 0 0
Active AMC Initialized
XCDR3G _AMC
U-D-Idl
U-E-A
EMPTY
EMPTY
3 0 1
Standby AMC Initialized
3 0 2
Active AMC Failed
3 0 3
Standby AMC Failed
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy
XCDR3G _AMC
U-D-Idl
U-E-Idl
EMPTY
EMPTY
XCDR3G _AMC
U-E-A
U-D-Idl
EMPTY
Possibly 90230
EMPTY
XCDR3G _AMC
U-E-Idl
U-D-Idl
EMPTY
Possibly 90230
EMPTY
October 30, 2008
3gXCDR-39

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
3 0 4
AMC Recovere d
pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _AMC
U-D-Idl
U-E-A
EMPTY
Clear of 90230
3 0 5
Standby AMC Recovere d Idle (Standby) AMC goes active Active AMC goes Standby Active AMC Removed
3 0 6
3 0 7
3 0 8
3 0 9
Idle (Standby) AMC Removed AMC Inserted
3 1 0
5 0 0
esmrStateCh
Payload disabled during shutdown (loss of heartbeat ) Payload
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _AMC
U-D-Idl
U-E-Idl
EMPTY
Clear of 90230
Note that the transition is from U-D-I to U-E-I and then to U-E-A. However the U-E-I is a transient state that is not reported for optimization. EMPTY
XCDR3G _AMC
U-E-Idl
U-E-A
EMPTY
EMPTY
The standby AMC became the active AMC
EMPTY
XCDR3G _AMC
U-E-A
U-E-Idl
EMPTY
EMPTY
The active AMC became the standby AMC
EMPTY
XCDR3G _AMC
U-E-A
U-D-Idl
EMPTY
Possibly 90261
EMPTY
XCDR3G _AMC
U-E-Idl
U-D-Idl
EMPTY
Possibly 90261
EMPTY
XCDR3G _AMC
U-D-Idl
U-E-Idl
EMPTY
Clear of 90261
The standby component was reinserted
EMPTY
XCDR3G _PAYLO AD
S-E-A
L-D-Idl
EMPTY
Possibly 90240, 90262
EMPTY
1.3.6.1.4.1.161.3
XCDR3G
DeviceType=563
S-E-Imp
L-D-Idl
EMPTY
Possibly
During the shutdown
EMPTY
3gXCDR-40
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 1
5 0 2
5 0 3
5 0 4
5 0 5
1 0 0 1
disabled during shutdown (loss of heartbeat ) Payload disabled (loss of heartbeat ) Payload disabled (loss of heartbeat ) Payload disabled (loss of heartbeat ) Payload disabled (loss of heartbeat ) The XCDR3G is Locked
.3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
_PAYLO AD
90240, 90262
process the management framework lost contact with the payload.
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G _PAYLO AD
U-E-Idl
U-D-Idl
EMPTY
Possibly 90240, 90262
EMPTY
XCDR3G _PAYLO AD
U-E-A
U-D-Idl
EMPTY
Possibly 90240, 90262
EMPTY
XCDR3G _PAYLO AD
U-E-Imp
U-D-Idl
EMPTY
Possibly 90240, 90262
EMPTY
XCDR3G _PAYLO AD
L-E-Idl
L-D-Idl
EMPTY
Possibly 90240, 90262
EMPTY
XCDR3G
U-D-Idl
L-D-Idl
29, 5012
EMPTY
1 0 0 3
The XCDR3G is Locked
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-A
L-D-Idl
5004, 24
Possibly 95020, 95021
The XCDR3G transits to L-D-I when all DSP Board boards are locked and at least one of the following conditions is true: a) One or more DSP Board boards are L-D-I b) The CM-Group is L-D-I/U-D-I c) The IPSB-Group is U-D-I d) The PSFT-Group is UD-I The XCDR3G transits to L-D-I when all DSP Board boards are locked and at least one of the following conditions is true: a) One or more DSP Board boards are L-D-I b) The CM-Group is L-D-I/U-D-I c) The
EMPTY
EMPTY
October 30, 2008
3gXCDR-41

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) IPSB-Group is U-D-I d) The PSFT-Group is UD-I The XCDR3G transits to L-D-I when all DSP Board boards are locked and at least one of the following conditions is true: a) One or more DSP Board boards are L-D-I b) The CM-Group is L-D-I/U-D-I c) The IPSB-Group is U-D-I d) The PSFT-Group is UD-I The XCDR3G transits to L-D-I when all DSP Board boards are locked and at least one of the following conditions is true: a) One or more DSP Board boards are L-D-I b) The CM-Group is L-D-I/U-D-I c) The IPSB-Group is U-D-I d) The PSFT-Group is UD-I The XCDR3G transits to L-D-I when all DSP Board boards are locked and at least one of the following conditions is true: a) One or more DSP Board boards are L-D-I b) The CM-Group is L-D-I/U-D-I c) The IPSB-Group is U-D-I d) The PSFT-Group is UD-I The XCDR3G transits to U-D-I when at least one of the following conditions is true: a) All Payload Boards are disabled and at least one is unlocked b) The CM-Group is U-D-I c) C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
1 0 0 4
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-Imp
L-D-Idl
26, 109, 302, 5008
Possibly 95020, 95022
EMPTY
1 0 0 6
The XCDR3G is Disabled
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
L-E-Idl
L-D-Idl
5002, 40
Possibly 95020, 95021
EMPTY
1 0 7 6
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-A
L-D-Idl
5002, 40
Possibly 95020, 95021
EMPTY
1 0 1 0
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-A
U-D-Idl
31, 42, 51, 101, 104, 108, 201, 202, 5002, 5016, 5021
Possibly 95020, 95021, 90261, 90262, 92101, 92102, 92104, 92110, 92111
EMPTY
3gXCDR-42
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 0 6 7
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-Idl
U-D-Idl
32, 43, 52, 101, 102, 104, 108, 109, 201, 202, 2104, 5002, 5021
Possibly 95020, 95021, 92001, 92002, 92003, 92100, 92104, 92105, 92106, 92500, 90262
1 0 1 2
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-Imp
U-D-Idl
32, 43, 52, 101, 102, 104, 108, 109, 201, 202, 5016, 5021, 5026, 5302
Possibly 95020, 95021, 92001, 92002, 92003, 92100, 92104, 92105, 92106, 92500, 90262
1 0 1 5
The XCDR3G is Unlocked
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
L-D-Idl
U-D-Idl
32, 38, 43, 44, 45, 46, 47, 54, 101, 102, 104, 108, 109, 201, 202, 5001
1 0 2 0
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-A
L-E-Idl
5014, 5502, 27
Possibly 90200, 90201, 90202, 90203, 90205, 90206, 90211, 90212, 90220, 90261, 90262, 90263, 91001, 92101, 92102, 92110, 92111 Possibly 92801
1 0 6 9
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-Idl
L-E-Idl
5020
EMPTY
The IPSB-Group is U-DI d) The PSFT-Group is U-D-I The XCDR3G transits to U-D-I when at least one of the following conditions is true: a) All DSP Board Boards are disabled and at least one is unlocked b) The CM-Group is U-D-I c) The IPSB-Group is U-DI d) The PSFT-Group is U-D-I The XCDR3G transits to U-D-I when at least one of the following conditions is true: a) All DSP Board Boards are disabled and at least one is unlocked b) The CM-Group is U-D-I c) The IPSB-Group is U-DI d) The PSFT-Group is U-D-I The XCDR3G transits to U-D-I when at least one of the following conditions is true: a) All DSP Board Boards are disabled and at least one is unlocked b) The CM-Group is U-D-I c) The IPSB-Group is U-DI d) The PSFT-Group is U-D-I The XCDR3G transits to L-E-I when at least one of the following conditions is true: a) All Payload boards are Locked, at least one is enabled The XCDR3G transits to L-E-I when at least one of the following conditions is true: a) All
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
October 30, 2008
3gXCDR-43

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) Payload boards are Locked, at least one is enabled The XCDR3G transits to L-E-I when at least one of the following conditions is true: a) All Payload boards are Locked, at least one is enabled The XCDR3G transits to L-E-I when at least one of the following conditions is true: a) All Payload boards are Locked, at least one is enabled The XCDR3G transits to L-E-I when at least one of the following conditions is true: a) All Payload boards are Locked, at least one is enabled The XCDR3G transits to L-E-I when at least one of the following conditions is true: a) All Payload boards are Locked, at least one is enabled The XCDR3G transits to S-E-Imp when at least one of the following conditions is true: a) One or more Payload boards are S-E-Imp, and remaining Payload Boards are locked. The XCDR3G transits to S-E-Imp when at least one of the following conditions is true: a) One or more Payload boards are S-E-Imp, and remaining Payload Boards are locked. b) C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
1 0 2 2
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-Imp
L-E-Idl
5024, 28
Possibly 92801
EMPTY
1 0 2 3
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-A
L-E-Idl
5004, 5005, 23
Possibly 95020, 95021
EMPTY
1 0 2 4
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-Imp
L-E-Idl
5008, 5009, 25
Possibly 95020, 95022
EMPTY
1 0 2 5
The XCDR3G Recovere d
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
L-D-Idl
L-E-Idl
39, 107, 304, 5000
EMPTY
EMPTY
1 0 3 2
The XCDR3G is Shutting Down
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-Imp
S-E-Imp
22, 5015, 5025
Possibly 92801
EMPTY
1 0 3 3
The XCDR3G is Impaired
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-A
S-E-Imp
33, 5006, 5014, 5020
Possibly 92001, 92002, 92003, 92100, 92104, 92105, 92106, 92500
EMPTY
3gXCDR-44
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 0 4 0
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-A
S-E-A
21, 5015
Possibly 92801
1 0 4 4
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-Imp
S-E-A
34, 100, 107, 5010
Clear of 92100, 92104, 92105, 92106, 92500
1 0 5 0
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-A
U-E-Imp
302, 303, 308, 309, 201, 202, 30, 105, 5018
1 0 6 8
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-Idl
U-E-Imp
5023
1 0 5 1
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-D-Idl
U-E-Imp
111, 5013
Possibly 90200...90213 , 91000, 92001, 92002, 92003, 92100, 92104, 92105, 92106, 92500, 92802, 95040, 95041 Possibly 90200...90213 , 91000, 92001, 92002, 92003, 92100, 92104, 92105, 92106, 92500, 92803 95040, 95041 Clear of 90220
At least one IPSB, CM, or PSU/FAN is not operational (not U-EA,U-E-I) (and the payload are S-E-A or SE-Imp) The XCDR3G transits to S-E-A when at least one of the following conditions is true: a) One or more Payload boards are S-E-A, and remaining Payload boards are locked. The XCDR3G transits to S-E-A when at least one of the following conditions is true: a) One or more Payload boards are S-E-A, and remaining Payload boards are locked. The XCDR3G transits to U-E-Imp when the following conditions is true: a)At least one board or PSU/Fan is not operational (not U-EA,U-E-I) and none of the conditions in 1010 are true. The XCDR3G transits to U-E-Imp when the following conditions is true: a)At least one board or PSU/Fan is not operational (not U-EA,U-E-I)
EMPTY
EMPTY
EMPTY
EMPTY
The XCDR3G transits to U-E-Imp when at least one of the following conditions is true: a) One or more payload boards are U-E-Imp b) The CM-Group is U-E-
EMPTY
October 30, 2008
3gXCDR-45

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) Imp c) The IPSB-Group is U-E-Imp and none of the conditions listed in State 1010 are true. The XCDR3G transits to U-E-Imp when at least one of the following conditions is true: a) One or more payload boards are U-E-Imp b) The CM-Group is U-EImp c) The IPSB-Group is U-E-Imp and none of the conditions listed in State 1032 are true. The XCDR3G transits to U-E-A when all the following conditions are true: a) At least one Payload board is U-E-A and the others are either U-E-I or U-E-A b) The CM-Group is U-E-A c) The IPSB-Group is U-EA d) The PSFT Group is U-E-A The XCDR3G transits to U-E-A when all the following conditions are true: a) At least one Payload board is U-E-A and the others are either U-E-I or U-E-A b) The CM-Group is U-E-A c) The IPSB-Group is U-EA d) The PSFT Group is U-E-A The XCDR3G transits to U-E-A when all the following conditions are true: a) At least one Payload board is U-E-A and the others are either U-E-I or U-E-A b) The CM-Group is U-E-A c) The IPSB-Group is U-EA d) The PSFT Group C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
1 0 5 4
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-Imp
U-E-Imp
35, 105, 5011
Possibly 91000
EMPTY
1 0 6 0
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-D-Idl
U-E-A
20, 48, 100, 103, 107, 110, 5013
Restart trap
EMPTY
1 0 7 4
The XCDR3G is Active
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-Idl
U-E-A
5501, 5301, 5506, 5022
EMPTY
EMPTY
1 0 6 2
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-E-Imp
U-E-A
41, 106, 107, 31`0, 5027
Clear of 92100, 92104, 92105, 92106, 92500, 91000
EMPTY
3gXCDR-46
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
1 0 6 3
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-A
U-E-A
36, 5007
EMPTY
1 0 7 0 1 0 7 1 1 0 7 2 1 0 7 3 1 0 7 5
The XCDR3G is Idle
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-D-Idl
U-E-Idl
5013
EMPTY
The XCDR3G recovered
XCDR3G
U-E-Imp
U-E-Idl
41, 106, 107, 310, 5029
Clear of 92100, 92104, 92105, 92106, 92500, 91000 EMPTY
The XCDR3G is Unlocked The XCDR3G is Idle
XCDR3G
L-E-Idl
U-E-Idl
5003
XCDR3G
U-E-A
U-E-Idl
5017
EMPTY
XCDR3G
L-E-Idl
U-E-Imp
1068, 1069, 1072
EMPTY
1 0 8 0
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-D-Idl
S-E-Imp
EMPTY
EMPTY
is U-E-A The XCDR3G transits to U-E-A when all the following conditions are true: a) At least one Payload board is U-E-A and the others are either U-E-I or U-E-A b) The CM-Group is U-E-A c) The IPSB-Group is U-EA d) The PSFT Group is U-E-A The XCDR3G transits to U-E-I when all the following conditions are true: a) All Payload boards are U-E-I The XCDR3G transits to U-E-I when all the following conditions are true: a) All Payload boards are U-E-I The XCDR3G transits to U-E-I when all the following conditions are true: a) All Payload boards are U-E-I The XCDR3G transits to U-E-I when all the following conditions are true: a) All DSP Board boards are U-E-I The XCDR3G transits to U-E-Imp when the following conditions is true: a)At least one board or PSU/Fan is not operational (not U-EA,U-E-I) and b) at least one Payload board is unlocked. The XCDR3G transitions to S-E-Imp when at least one of the following conditions is true: a) One or more Payload boards are S-E-Imp, and
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
EMPTY
October 30, 2008
3gXCDR-47

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) remaining Payload Boards are locked. b) At least one IPSB, CM, or PSU/FAN is not operational (not U-EA,U-E-I) (and the payload are S-E-A or SE-Imp). The XCDR3G transitions to U-D-I when at least one of the following conditions is true: a) All DSP Board Boards are disabled and at least one is unlocked b) The CM-Group is U-D-I c) The IPSB-Group is U-DI d) The PSFT-Group is U-D-I. The XCDR3G transitions to S-E-A when at least one of the following conditions is true: a) One or more Payload boards are S-E-A, and remaining Payload boards are locked. The XCDR3G transitions to U-D-I when at least one of the following conditions is true: a) All DSP Board Boards are disabled and at least one is unlocked b) The CM-Group is U-D-I c) The IPSB-Group is U-DI d) The PSFT-Group is U-D-I. Board or software failure (i.e., all DSPs have failed, the application has failed, there are 0 Ethernet ports available) has occurred. Active calls are dropped. New calls are not accepted. Board or software failure C h a n g e S t a t u s
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
1 0 7 7
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-Imp
U-D-Idl
5007
EMPTY
EMPTY
1 0 7 8
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
U-D-Idl
S-E-A
EMPTY
EMPTY
EMPTY
1 0 7 9
1.3.6.1.4.1.161.3 .3.10.5.14.1.7.2. 1.1.1.<DeviceTy pe>.<LoID>
XCDR3G
S-E-A
U-D-Idl
5007
EMPTY
EMPTY
5 0 0 2
DSP FRU is Disabled
XCDR3G _PAYLO AD
L-E-Idl
L-D-Idl
EMPTY
Possibly 95020, 95021
EMPTY
esmrStateCh
DSP FRU
1.3.6.1.4.1.161.3
XCDR3G
DeviceType=563
S-E-A
L-D-Idl
EMPTY
Possibly
EMPTY
3gXCDR-48
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
angeEvent
0 0 4
is Disabled
.3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
_PAYLO AD
95020, 95021
5 0 0 8
DSP FRU is Disabled
XCDR3G _PAYLO AD
S-E-Imp
L-D-Idl
EMPTY
Possibly 95020, 95021
5 0 1 2 5 0 0 0
Disabled DSP FRU Locked
DSP FRU is enabled
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _PAYLO AD
U-D-Idl
L-D-Idl
EMPTY
EMPTY
(i.e., all DSPs have failed, the application has failed, there are 0 Ethernet ports available) has occurred. Active calls are dropped. New calls are not accepted. Board or software failure (i.e., all DSPs have failed, the application has failed, there are 0 Ethernet ports available) has occurred. Active calls are dropped. New calls are not accepted. The DSP Board is now locked. New calls are not accepted.
EMPTY
EMPTY
XCDR3G _PAYLO AD
L-D-Idl
L-E-Idl
EMPTY
EMPTY
5 0 0 5 5 0 0 9 5 0 1 4 5 0 2 0
Shutting Down DSP FRU Locked Impaired Shutting Down DSP FRU Locked DSP FRU Locked
DSP FRU Locked
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.<
XCDR3G _PAYLO AD
S-E-A
L-E-Idl
EMPTY
EMPTY
Locked DSP Board is no longer disabled (initialization successful, responds to heartbeats, no internal failures, and all DSPs have loaded successfully). New calls are not accepted. The DSP Board is now locked. Active calls are dropped. New calls are not accepted. The DSP Board is now locked. Active calls are dropped. New calls are not accepted. The DSP Board is now locked. Active calls are dropped. New calls are not accepted. The DSP Board is now locked. New calls are not accepted.
EMPTY
EMPTY
XCDR3G _PAYLO AD
S-E-Imp
L-E-Idl
EMPTY
EMPTY
EMPTY
XCDR3G _PAYLO AD
U-E-A
L-E-Idl
EMPTY
EMPTY
EMPTY
XCDR3G _PAYLO AD
U-E-Idl
L-E-Idl
EMPTY
EMPTY
EMPTY
October 30, 2008
3gXCDR-49

State Changes
R e a s o n C o d e
Release SR17.0
O u t a g e ( Y / N ) C h a n g e S t a t u s U EMPTY
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
5 0 2 4 5 0 1 0
DSP FRU Locked
DSP FRU is Recovere d
BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _PAYLO AD
U-E-Imp
L-E-Idl
EMPTY
EMPTY
The DSP Board is now locked. Active calls are dropped. New calls are not accepted. Due to a successful reset and initialization for a failed DSP, the DSP Board transitions from impaired to active, while continuing to shutdown. Active calls are maintained, but new calls are not accepted. The DSP Board has received a Shutdown Request. Active calls are maintained, but new calls are not accepted. At least 1 DSP element has failed (but not all) or 1 Ethernet connection is unavailable. Active calls are maintained, but new calls are not accepted. The DSP Board has received a Shutdown Request. Active calls are maintained, but new calls are not accepted. The DSP Board is unlocked. New calls are not accepted.
XCDR3G _PAYLO AD
S-E-Imp
S-E-A
EMPTY
EMPTY
5 0 1 5 5 0 0 6
DSP FRU is Shutting Down DSP FRU is Impaired
XCDR3G _PAYLO AD
U-E-A
S-E-A
EMPTY
EMPTY
This should not apply to going from Impaired to Active due to calls being released by the shutdown process. It should only apply to other reasons, such as recovery of an Ethernet connection. EMPTY
XCDR3G _PAYLO AD
S-E-A
S-E-Imp
EMPTY
EMPTY
EMPTY
5 0 2 5 5 0 0 1 5 0 1 6
DSP FRU is Shutting Down DSP FRU is Unlocked
XCDR3G _PAYLO AD
U-E-Imp
S-E-Imp
EMPTY
EMPTY
EMPTY
XCDR3G _PAYLO AD
L-D-Idl
U-D-Idl
EMPTY
EMPTY
EMPTY
DSP FRU is Disabled
XCDR3G _PAYLO AD
U-E-A
U-D-Idl
EMPTY
Possibly 95020, 95021
5 0 2
DSP FRU is Disabled
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy
XCDR3G _PAYLO AD
U-E-Idl
U-D-Idl
EMPTY
Possibly 95020, 95021
Board or software failure (i.e., all DSPs have failed, the application has failed, there are 0 Ethernet ports available) has occurred. Active calls are dropped. New calls are not accepted. Board or software failure (i.e., all DSPs have failed, the application
EMPTY
EMPTY
3gXCDR-50
October 30, 2008
Release SR17.0
State Changes
R e a s o n C o d e

MOI Info (Id)
OMC Text
From State
To State
Related Alarms
Event Description
O u t a g e ( Y / N )
Comments & Notes
pe>.<ShelfID>.< BoardID>
5 0 2 6
DSP FRU is Disabled
XCDR3G _PAYLO AD
U-E-Imp
U-D-Idl
EMPTY
Possibly 95020, 95021
5 0 0 7 5 0 2 2 5 0 2 7
DSP FRU Unlocked
DSP FRU is Active
DSP FRU is Active
XCDR3G _PAYLO AD
S-E-A
U-E-A
EMPTY
EMPTY
has failed, there are 0 Ethernet ports available) has occurred. Active calls are dropped. New calls are not accepted. Board or software failure (i.e., all DSPs have failed, the application has failed, there are 0 Ethernet ports available) has occurred. Active calls are dropped. New calls are not accepted. Lock or Shutdown has been aborted. Active calls are maintained and new calls are accepted. The DSP Board has transitioned from no active calls to at least 1 active call. Due to a successful reset and initialization for a failed DSP, the DSP Board transitions from impaired to active. New calls are accepted and Active calls are maintained. The DSP Board is unlocked. New calls are accepted.
EMPTY
EMPTY
XCDR3G _PAYLO AD
U-E-Idl
U-E-A
EMPTY
EMPTY
EMPTY
XCDR3G _PAYLO AD
U-E-Imp
U-E-A
EMPTY
EMPTY
EMPTY
5 0 0 3 5 0 1 3
DSP FRU Unlocked
DSP FRU now Enabled
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID> 1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2. 1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
XCDR3G _PAYLO AD
L-E-Idl
U-E-Idl
EMPTY
EMPTY
EMPTY
XCDR3G _PAYLO AD
U-D-Idl
U-E-Idl
EMPTY
EMPTY
5 0
All Current
1.3.6.1.4.1.161.3 .3.10.5.14.1.6.2.
XCDR3G _PAYLO
DeviceType=563 2, ShelfID=1,
U-E-A
U-E-Idl
EMPTY
EMPTY
The DSP board is fully operational (i.e., initialized successfully, responsive to heartbeat requests, has no internal failures, and all DSPs have loaded successfully). New calls are accepted. All calls on the DSP Board have completed.
EMPTY
EMPTY
October 30, 2008
3gXCDR-51

State Changes
R e a s o n C o d e
Release SR17.0
OMC Text
MOI Info (Id)
MOI Info (Label)
Inst
From State
Comments & Notes
1 7
5 0 2 9 5 0 1 1 5 0 1 8
Calls on the DSP FRU Complete d DSP FRU recovered
1.1.1.<DeviceTy pe>.<ShelfID>.< BoardID>
AD
BoardID=3-18
New calls are accepted.
DSP FRU Unlocked
DSP FRU Impaired
XCDR3G _PAYLO AD
U-E-Imp
U-E-Idl
EMPTY
EMPTY
XCDR3G _PAYLO AD
S-E-Imp
U-E-Imp
EMPTY
EMPTY
XCDR3G _PAYLO AD
U-E-A
U-E-Imp
EMPTY
EMPTY
5 0 2 3
DSP FRU Impaired
XCDR3G _PAYLO AD
U-E-Idl
U-E-Imp
EMPTY
EMPTY
The DSP Board has recovered from an Impaired State and no calls are being processed The DSP Board transitions to an unlocked state. Active calls are maintained and new calls are accepted. The DSP Board is Impaired (I.e. at least 1 DSP element has failed or only 1 Ethernet connection is available). Active calls are maintained and new calls are accepted. The DSP Board is Impaired (I.e. at least 1 DSP element has failed or only 1 Ethernet connection is available). New calls are accepted.
EMPTY
EMPTY
EMPTY
EMPTY
3gXCDR-52
October 30, 2008
Release SR17.0
__________________________________ Events
Alarm Type Alarm Code OMC Text MOI Info (Id) MOI Info (Label) I n s t Alarm Code Text Severity Related Alarms Related State Changes Remedy R e p o r t & C l e a r R O u t a g e Y / N C h a n g e S t a t u s U Comments & Notes
CA Restart Trap
EMPT Y
New Operate State: <operational state> New Usage State: <usage state> New Admin State: <administrative state> System ROM Version: <boot ROM version> System Load Version: <software Load version> System DB Version: <database version> System Code Version: <code version> Description: <system description> System Reset Reason: <latest reset reason> System Outage Time: <outage time since latest reset> System Reboot Time: <reboot time> System Boot Diagnostics: <boot diagnostics>
1.3.6.1.4. 1.161.3.3 .10.2.3.1. 0
XCDR3G_ST ATE
<text OR null>
EMPTY
CA Availabilit y Trap
All available FRUs and other Managed Objects will report their new state
No action necessary
n/ a
CA Availability Trap
EMPT Y
System Sequence Number: <seq no> System Secondary ID: <secondary id> System New Mode: <mode > System Switch Time: <switch time> System Reason Code: < reason code> System Old Mode: <old mode> System Additional Text: <Additional text> System Reason Text:
EMPTY
XCDR3G
E M P T Y
<text OR null>
EMPTY
CA Restart Trap
EMPTY
No action necessary
n/ a
This event is used to inform the OMC whenever this NE starts. This event encodes some information about the active cluster manager. The rest of the information about the system can be determined from the FRU table, which contains the same information. State information is obtained from the Logical Object that represents the NE.CP3G will not provide the value for the ROM Version and boot diagnostic. For the system description, the trap contains a fixed string. The trap is sent upon Network Element startup before a synchronization is attempted with the OMC (via a foreground download). The trap is sent upon initialization out of reset after a re-init upgrade, indicating the completion of the upgrade. In this case, no foreground download follows the generation of the trap. The Trap may be sent also after a Cluster Manager failover, after a zero downtime upgrade, in this cases the outage time could be zero. This event encodes information from the NE Logical Object. Note that maintenance will represent the state of "not providing service". Active will be the opposite state, "providing service". The standby state is not used by the cp3g NEs.
October 30, 2008
3gXCDR-53

Alarm Type Alarm Code OMC Text MOI Info (Id) MOI Info (Label) I n s t Alarm Code Text Severity Related Alarms Related State Changes Remedy R e p o r t & C l e a r R O u t a g e Y / N C h a n g e S t a t u s U
Release SR17.0
Comments & Notes
<reason text> Background Download aborted
1.3.6.1.4. 1.161.3.3 .10.2.10. 1.1.0
XCDR3G
E M P T Y
<text OR null>
EMPTY
EMPTY
EMPTY
1.3.6.1.4. 1.161.3.3 .10.2.10. 1.1.0
XCDR3G
E M P T Y
<text OR null>
EMPTY
EMPTY
EMPTY
1.3.6.1.4. 1.161.3.3 .10.2.10. 1.1.0 1.3.6.1.4. 1.161.3.3 .10.2.10. 1.2.0 1.3.6.1.4. 1.161.3.3 .10.2.10. 1.2.0 1.3.6.1.4. 1.161.3.3 .10.2.11. 1.1.0 1.3.6.1.4. 1.161.3.3 .10.2.11. 1.1.0
XCDR3G
1,2 or 3
XCDR3G
XCDR3G
XCDR3G
XCDR3G
E M P T Y E M P T Y E M P T Y E M P T Y E M P T Y
<text OR null>
EMPTY
EMPTY
EMPTY
No action necessary, if transfer is still required retry transfer. Contact the iDEN Customer Situation Center for assistance. Retry transfer, if problem persist contact the iDEN Customer Situation Center for assistance. No action necessary
Event is generated if background download has failed. Action Status Info details reason of failure.
Event is generated if background download has completed successfully.
<text OR null>
EMPTY
EMPTY
EMPTY
No action necessary
Event is generated if background download was not aborted.
<text OR null>
EMPTY
EMPTY
EMPTY
No action necessary
<text OR null>
EMPTY
EMPTY
EMPTY
No action necessary
Event is generated when OLCC switch has started.
<text OR null>
EMPTY
EMPTY
EMPTY
No action necessary
Event is generated when OLCC switch has aborted. Action Status info details reason for failure (reason and line number in configuration file).
3gXCDR-54
October 30, 2008
Release SR17.0
Alarm Type Alarm Code OMC Text MOI Info (Id) MOI Info (Label) I n s t Alarm Code Text Severity

Related Alarms Related State Changes Remedy R e p o r t & C l e a r R O u t a g e Y / N C h a n g e S t a t u s U Comments & Notes
1.3.6.1.4. 1.161.3.3 .10.2.11. 1.1.0
XCDR3G
E M P T Y
<text OR null>
EMPTY
EMPTY
EMPTY
1.3.6.1.4. 1.161.3.3 .10.2.11. 1.1.0 1.3.6.1.4. 1.161.3.3 .10.2.12. 2.1.0 1.3.6.1.4. 1.161.3.3 .10.2.12. 2.1.0
XCDR3G
Upgrade aborted
XCDR3G
Upgrade failed
XCDR3G
<text OR null>
EMPTY
EMPTY
EMPTY
Retry to transfer the configuratio n file and perform an olcSwitch request. If problem persist contact the iDEN Customer Situation Center for assistance. No action necessary
Event is generated when OLCC switch has failed. Action Status info details reason for failure (reason and line number in configuration file).
Event is generated when OLCC switch has completed.
<text OR null>
EMPTY
EMPTY
EMPTY
No action necessary
Event is generated when upgrade has aborted. Action Status info details reason for failure.
<text OR null>
EMPTY
EMPTY
EMPTY
Retry upgrade possibly retransferring the software load. If problem persist contact the iDEN Customer Situation Center for assistance.
Event is generated in case of a failure 1) Due to Internal Errors 2) NE is in an invalid transfer/upgrade state. Event is not generated if the active CM fails and it is reset.
October 30, 2008
3gXCDR-55
Release SR17.0
3gXCDR-56
October 30, 2008
Technical Manual
MOTOROLA and the Stylized M logo are registered in the U.S. Patent and Trademark Office. All other product or service names are the property of their respective owners. Motorola, Inc. 2008
6871000P20-B

1000 P 20 B

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

1000 P 20 B

Загружено:

Авторское право:

Доступные форматы

Technical Manual

iDEN Alarm and State Change Event Reference Manual

SYSTEM LEVEL INFORMATION

2008 - Motorola, Inc. All Rights Reserved

SPECIFICATIONS ARE SUBJECT TO CHANGE WITHOUT NOTICE.

iDEN Alarm and State Change Event Reference Manual iii

iDEN Alarm and State Change Event Reference Manual iv

How to Use this Manual

iDEN Alarm and State Change Event Reference Manual 1

Interpreting Alarm Tables

Alarm Table Column Heading Descriptions

iDEN Alarm and State Change Event Reference Manual 2

Alarm Table Column Heading Descriptions (continued)

Report & Clear

Whether the alarm is service-affecting: Outage

Yes An outage may occur. No An outage will not occur.

Change Status Comments & Notes

iDEN Alarm and State Change Event Reference Manual 3

Interpreting Event Tables

Event Table Column Heading Descriptions

Yes An outage may occur. No An outage will not occur.

Change Status Comments & Notes

iDEN Alarm and State Change Event Reference Manual 4

iDEN Alarm and State Change Event Reference Manual

MOI Info (Id)

MOI Info (Label)

Alarm Code Text

Related State Changes

Comments & Notes

communicat ionFailureE vent

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

The physical T1 or E1 line <number> is down.

communicat ionFailureE vent

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

The physical T1 or E1 line <number> is up. EMPTY

ACG_BMR or iMU Link Failure

note:m[1-2] indicates the T1/E1 link ID.

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

October 30, 2008

iDEN Alarm and State Change Event Reference Manual

MOI Info (Id)

MOI Info (Label)

Comments & Notes

communicat ionFailureE vent

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

October 30, 2008

iDEN Alarm and State Change Event Reference Manual

Alarm Code Text

Related State Changes

Comments & Notes

communicat ionFailureE vent

BSC_ACG MOBIS LAPD Link Failure

1.3.6.1.4.1.161.3 .3.2.2.14.1.4.100 .1.1.n

October 30, 2008

iDEN Alarm and State Change Event Reference Manual

MOI Info (Id)

MOI Info (Label)

Comments & Notes

communicat ionFailureE vent