Nortel SGSN Alarms Reference Manual

411-5221-500
GSM UMTS Packet Core Network
Nortel SGSN
Alarms Reference Manual
SGSN5.0 Standard 04.05 January 2007 411-5221-500
Nortel SGSN
Document number: 411-5221-500 Product release: SGSN5.0 Document version: Standard 04.05 Date: January 2007
Copyright Country of printing Confidentiality Legal statements Trademarks
Copyright 20042007 Nortel Networks, All Rights Reserved Originated in the United States of America NORTEL NETWORKS CONFIDENTIAL
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein. Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. NORTEL, NORTEL NETWORKS, the globemark design, and the NORTEL corporate logo are trademarks of Nortel.GSM is a trademark of GSM MOU Association. Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
Nortel Networks Confidential
i Copyright 20042007 Nortel Networks
Contents
New in this Release for SGSN Alarms Reference Manual
Feature impacts 1 Other changes 1
1
1
SGSN Alarms
7056_1300 - TDM Link Failure Alarm (UMTS; Obsolete) 19 7065_0000 - Mapping Table Full Alarm (UMTS) 20 7066_0000 - SCCP Connections Near Limit Alarm (UMTS) 21 7066_0100 - Signalling Link Test Failed Alarm (UMTS) 22 7066_0101 - Destination Inaccessible Alarm (UMTS) 23 7066_0102 - MTP3 Link Incorrect Mapping Alarm (UMTS) 24 7066_0103 - MTP3 Link Buffering Error Alarm (UMTS) 25 7066_0300 - Alignment Failure Alarm (UMTS) 26 7066_0301 - Layer 2 Peer Disconnect Alarm (UMTS; Obsolete) 29 7067_0000 - Media Gateway Heartbeat Alarm (UMTS; Obsolete) 30 7067_0001 - MgIf Claim Failure Alarm (UMTS; Obsolete) 31 7067_0002 - Tdmc Claim Failure Alarm (UMTS; Obsolete) 32 7067_0003 - Q.2630 Blocking Failure Alarm (UMTS; Obsolete) 33 7067_0004 - Vmg High Resource Usage Alarm (UMTS; Obsolete) 34 7068_1000 - SAS Disk Almost Full Alarm (GPRS; Obsolete) 35 7068_1001 - SAS Disk High Usage Alarm (GPRS/UMTS) 36 7068_1002 - SAS Disk Failure Alarm (GPRS/UMTS) 37 7068_1003 - CGF Link Failure Alarm (GPRS/UMTS) 38 7068_1004 - Secondary CGF Link Failure Alarm (GPRS; Obsolete) 39 7068_1005 - GSC Memory Exhausted Alarm (GPRS) 40 7068_1006 - Subscriber Count Overload Alarm (GPRS/UMTS) 41 7068_1008 - GSD Memory Exhausted Alarm (GPRS; Obsolete) 42 7068_1009 - Maximum Active Subscribers Reached Alarm (GPRS) 43 7068_1010 - GSC Memory Near Exhaustion Alarm (GPRS; Obsolete) 44 7068_1011 - Routing Area ID Missing Alarm (GPRS/UMTS) 45 7068_1012 - GSD Maximum Allocated LLEs Reached Alarm (GPRS) 46 7068_1013 - Loss of connection with SIG (GPRS; Obsolete) 47 7068_1016 - SAS Initialization Failure Alarm (GPRS/UMTS) 48 7068_1017 - GTL Initialization Failure Alarm (GPRS) 49 7068_1018 - GSC Initialization Failed Alarm (GPRS) 50 7068_1019 - GSD Initialization Failed Alarm (GPRS) 51 7068_1020 - Maximum Number of BVCs Per NSE Exceeded Alarm (GPRS; Obsolete) 52 GSM UMTS Packet Core Network Nortel SGSN Alarms Reference Manual
SGSN5.0
ii Contents Nortel Networks Confidential
Copyright 20042007 Nortel Networks
7068_1021 - GSD Downlink Buffer Component Add Failed Alarm (GPRS) 53 7068_1022 - GSD Hardware-Assist Failure Alarm (GPRS) 54 7068_1023 - The Number of Unavailable BVCs Has Exceeded the Threshold (GPRS) 55 7068_1024 - SVC Audit Failed Alarm (GPRS/UMTS) 56 7068_1025 - Nodal Manager Critical Component Missing Alarm (GPRS/UMTS) 58 7068_1026 - Nodal Manager Non-critical Component Missing Alarm (GPRS/ UMTS) 60 7068_1027 - I/RAU Requests Rejected Alarm (GPRS/UMTS; Obsolete) 61 7068_1028 - Attach Reject Cause Code Reporting Alarm (GPRS/UMTS; Obsolete) 62 7068_1029 - Sgsn-Initiated Session Deactivations Cause Code Reporting Alarm (GPRS/UMTS; Obsolete) 64 7068_1030 - Mobile-Originated SMS Overload Alarm (GPRS) 66 7068_1031 - Mobile-Terminated SMS Overload Alarm (GPRS) 67 7068_1032 - HLR Reset Triggered UGL Overload Alarm (GPRS/UMTS) 68 7068_1033 - NSVC Unavailable Alarm (GPRS) 69 7068_1034 - GSC IMSI Diagnostic Alarm (GPRS/UMTS) 70 7068_1035 - BSSAP MS-Activity-Indication Overload Alarm (GPRS) 71 7068_1036 - BSSAP Location Update Request Overload Alarm (GPRS) 72 7068_1037 - Maximum Header Compression Memory Usage Alarm (GPRS) 73 7068_1038 - FrameBuf Congestion Alarm (GPRS) 74 7068_1039 - GSD Max Allocated LLC-ABM Data Entities Reached Alarm (GPRS) 75 7068_1040 - GSD Max Allocated Session Entities Reached Alarm (GPRS) 76 7068_1041 - Signaling BVC Reset Alarm (GPRS) 77 7068_1043 - Max BVCs per NSE Reached Alarm (GPRS) 78 7068_1044 - GbIP Data NS-VC Unavailable Alarm (GPRS) 79 7068_1045 - GbIP Signaling NS-VC Unavailable Alarm (GPRS) 80 7068_1046 - GbIP Dynamic Configuration Failure Alarm (GPRS) 81 7068_1047 - GbIP Dynamic Configuration Attempts while using Static Configuration Alarm (GPRS) 84 7068_1200 - Primary CGF Link Up Alarm (GPRS; Obsolete) 85 7068_1201 - Secondary CGF Link Up Alarm (GPRS; Obsolete) 86 7068_1202 - NRI Lock Constraint Alarm (GPRS) 87 7068_1203 - All NRIs Locked Message Alarm (GPRS) 88 7068_1495 - MapStack Overload Alarm (GPRS; Obsolete) 89 7068_1496 - GSC/USC Overload Alarm (GPRS/UMTS; Obsolete) 90 7068_1499 - Mismatched PTP BVC States Alarm (GPRS) 91 7068_1500 - Context Memory Exhausted Alarm (UMTS; Obsolete) 92 7068_1501 - GMM Max Attaches Exceeded Alarm (UMTS; Obsolete) 93 7068_1502 - SM Max Active Sessions Exceeded Alarm (UMTS; Obsolete) 94 7068_1503 - GSD or USD Out of Resources Alarm (UMTS) (GPRS: Obsolete) 95 7068_1504 - Max Active Sessions Exceeded Alarm (UMTS) 96 7068_1505 - TcapStack Out of Subsystem Resources Alarm (GPRS/UMTS) 97 7068_1506 - MapStack Out of SGSN MAP Subsystem Resources Alarm (GPRS/ UMTS) 98 7068_1507 - Initialization Failure Alarm (GPRS/UMTS; Obsolete) 99 7068_1508 - GSD or USD Memory Initialization Alarm (GPRS/UMTS) 100 7068_1509 - MapStack Out of SGSN MSC Subsystem Resources Alarm (GPRS/ UMTS) 101 411-5221-500 Standard 04.05 January 2007
Contents iii Copyright 20042007 Nortel Networks
7068_1510 - TcapStack Out of SGSN CAP Subsystem Resources Alarm (GPRS/ UMTS) 102 7068_1511 - MAP Client out of Resources Alarm (GPRS/UMTS) 103 7068_1512 - Max SGSN MAP Invokes Exceeded Alarm (GPRS; Obsolete) 104 7068_1513 - Max MSC MAP invokes Exceeded Alarm (GPRS; Obsolete) 105 7068_1514 - Max CAP invokes Exceeded Alarm (GPRS; Obsolete) 106 7068_1515 - SGSN MAP Subsystem Bind Failed Alarm (GPRS/UMTS) 107 7068_1516 - SGSN MSC Subsystem Bind Failed Alarm (GPRS/UMTS) 108 7068_1517 - SGSN CAP Subsystem Bind Failed Alarm (GPRS/UMTS) 109 7068_1518 - SSF SCP Communication Failure Alarm (GPRS/UMTS) 110 7068_1519 - SSF Max Camel Dialogues Exceeded Alarm (GPRS/UMTS) 111 7068_1520 - MAP Notice Indication Display Alarm (GPRS/UMTS; Obsolete) 112 7068_1521 - GSC or USC CPU Overload Alarm (GPRS/UMTS) 113 7068_1522 - Loss of Communication with the DnsAgent Servers Alarm (GPRS/ UMTS; Obsolete) 114 7068_1523 - Loss of Connection with the SIG or SIGTRAN Alarm (GPRS/ UMTS) 115 7068_1524 - LIAF out of Resources Alarm (GPRS/UMTS) 116 7068_1525 - LIAF Maximum Subscribers Reached Alarm (GPRS/UMTS) 117 7068_1526 - LIAF Initialization Failure Alarm (GPRS/UMTS) 118 7068_1527 - Loss of Communication with LIG ADMF Alarm (GPRS/UMTS) 119 7068_1528 - Loss of Communication with LIG DF Server Alarm (GPRS/UMTS) 120 7068_1529 - Invalid PDP Context Received Alarm (GPRS/UMTS) 121 7068_1530 - Loss of Redundancy with the DnsAgent Servers Alarm (GPRS/UMTS; Obsolete) 122 7068_1531 - Attach Requests Rejected or not Received Alarm (GPRS/UMTS; Obsolete) 123 7068_1532 - PDP Activations Requests Rejected or not Received Alarm (GPRS/ UMTS; Obsolete) 124 7068_1533 - SS7 SIG Problem Alarm (GPRS/UMTS; Obsolete) 126 7068_1534 - SCCP Notice Indication Throttling Alarm (GPRS/UMTS; Obsolete) 127 7068_1535 - HLR Reset Received Alarm (GPRS/UMTS) 128 7068_1536 - TCAP Mobile-Terminated FSM Overload Alarm (GPRS; Obsolete) 129 7068_1537 - Registration with IP Server Failure Alarm (GPRS/UMTS) 130 7068_1538 - GTP Path High Usage Alarm (GPRS/UMTS) 131 7068_1539 - GTP Transaction High Usage Alarm (GPRS/UMTS) 132 7068_1540 - GTP Path Failure Alarm (GPRS/UMTS) 133 7068_1544 - Attach Overload Alarm (GPRS/UMTS) 134 7068_1545 - InterSGSN RAU Overload Alarm (GPRS/UMTS) 135 7068_1546 - Mobile-Terminated SMS TCAP Overload Alarm (GPRS) 136 7068_1547 - SAI Overload Alarm (GPRS/UMTS) 137 7068_1548 - Non-SAI Overload Alarm (GPRS/UMTS) 138 7068_1549 - SSF InitialDPGPRS Overload Alarm (GPRS/UMTS) 139 7068_1550 - MAP Client Registration Failure Alarm (GPRS/UMTS) 140 7068_1551 - Ss7IpIf Reg Failure alarm (GPRS/UMTS) 141 7068_1552 - Ss7IpIf Ni Failure alarm (GPRS/UMTS) 142 7068_1553 - MAP Client IP Network Error Alarm (GPRS/UMTS) 143 7068_1554 - Sgsn Audit Memory Corruption Alarm (GPRS/UMTS) 144 7068_1555 - Ss7IpIf Noisy Link Alarm (GPRS/UMTS) 145 7068_1556 - Mobile Context Mismatch In GMM Alarm (UMTS; Obsolete) 146 GSM UMTS Packet Core Network Nortel SGSN Alarms Reference Manual SGSN5.0
iv Contents Nortel Networks Confidential
7068_1557 - Nodal Manager Call Released Alarm (GPRS/UMTS) 147 7068_1558 - Nodal Manager Resource Failure Alarm (GPRS/UMTS) 148 7068_1559 - Nodal Manager Registration Alarm (GPRS/UMTS) 149 7068_1560 - Nodal Manager Outgoing Call Request Failure Alarm (GPRS/ UMTS) 150 7068_1561 - Nodal Manager Incoming Call Timeout Alarm (GPRS/UMTS) 151 7068_1562 - Nodal Manager Invalid Master Alarm (GPRS/UMTS) 152 7068_1564 - SAS Fail to Send Message to SC Alarm (GPRS/UMTS) 153 7068_1565 - Activation Reject Counter Alarm (UMTS; Obsolete) 154 7068_1566 - SAS Not Ready for Switchover Alarm (GPRS/UMTS) 157 7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/UMTS) 158 7068_1568 - Loss of Communication with MapStack Alarm (GPRS/UMTS) 159 7068_1569 - Loss of Communication with TcapStack Alarm (GPRS/UMTS) 160 7068_1570 - SNR Audit Memory Corruption Alarm (GPRS/UMTS) 161 7068_1571 - GTP Version Mismatch Alarm (GPRS; Obsolete) 162 7068_1572 - SC Redundancy Sync Loss Alarm (GPRS/UMTS) 163 7068_1573 - Switchover During Checkpointing Alarm (GPRS/UMTS) 164 7068_1574 - GPRS Attach Success Rate Threshold Alarm (GPRS) 165 7068_1575 - GPRS Activation Success Rate Threshold Alarm (GPRS) 166 7068_1576 - SAS Memory Pool High Usage Alarm (GPRS/UMTS) 167 7068_1577 - SAS Card Memory High Usage Alarm (GPRS/UMTS) 168 7068_1578 - Loss of Communication with the DNS Server Alarm (GPRS/ UMTS) 169 7068_1579 - NPI Calculation Data for Activation Rejects Alarm (UMTS; Obsolete) 170 7068_1580 - Internal Diagnostic Alarm (GPRS/UMTS) 171 7068_1581 - SC Resource Exhaustion Alarm (GPRS/UMTS) 172 7068_1585 - Sigtran Remote Address Inactive alarm (GPRS/UMTS) 174 7068_1586 - Sigtran No Destination Routable alarm (GPRS/UMTS) 175 7068_1587 - Sigtran No SG Available alarm (GPRS/UMTS) 176 7068_1588 - Sigtran PeerProcess Not Active alarm (GPRS/UMTS) 177 7068_1589 - Sigtran Sgsn PeerProcess Blocked alarm (GPRS/UMTS) 178 7068_1590 - Sigtran PeerProcess Congested alarm (GPRS/UMTS) 179 7068_1591 - Sigtran Destination Unroutable alarm (GPRS/UMTS) 180 7068_1592 - Sigtran Destination Restricted alarm (GPRS/UMTS) 181 7068_1593 - Sigtran Destination Congested alarm (GPRS/UMTS) 182 7068_1594 - Sigtran Unauthorized Associate alarm (GPRS/UMTS) 183 7068_1595 - Sigtran Remote Subsystem Unavailable alarm (GPRS/UMTS) 184 7068_1596 - Sigtran Local Subsystem Unavailable alarm (GPRS/UMTS) 185 7068_1597 - Sigtran Unknown Destination alarm (GPRS/UMTS) 186 7068_1598 - Sigtran TcpConn Congested alarm (GPRS/UMTS) 187 7068_1599 - Sigtran No Scip Clients Registered alarm (GPRS/UMTS) 188 7068_1600 - Sigtran SigConn Down alarm (GPRS/UMTS) 189 7068_1601 - Sigtran SigConn Congested alarm (GPRS/UMTS) 190 7068_1602 - Sigtran TcpConn Dropped alarm (GPRS/UMTS) 191 7068_1603 - Sigtran Asp Initialization Failure alarm (GPRS/UMTS) 192 7068_1604 - Ss7IpIf NoticeInd Congestion alarm (GPRS/UMTS) 193 7068_1605 - Too Many GSDs Alarm (GPRS/UMTS) 194 7068_1606 - Too Many GSCs Alarm (GPRS/UMTS) 195 7068_1607 - UMTS Attach Success Rate Threshold Alarm (UMTS) 196 7068_1608 - UMTS Activation Success Rate Threshold Alarm (UMTS) 197 411-5221-500 Standard 04.05 January 2007
Contents v Copyright 20042007 Nortel Networks
7068_1610 - GIPS Unavailable Alarm (GPRS) 198 7068_1612 - Potential Ethernet Port Issue On 2pGPDsk Card (GPRS) 199 7068_1996 - GMM Context Resources Low Alarm (GPRS; Obsolete) 200
Adding SGSN Alarms

Adding Minor SGSN Alarms Adding Major Alarms 203 201
201
MDM Alarm Screening Macro MDM Alarm Injection Script (Obsolete)

Scope 207 Overview 207 Implementation 207 Location of Alarm Injection Script
205 207
208
Alarm Change Summary

Alarms Changed in GPRS4 (G3016AG to G4003AK) 210 Alarms Changed in GPRS5 (G4003AK to G5003AK) 210 Alarms Changed in GPRS5 Mtce. (G5003AK to G5025AW) 212 Alarms Changed in GPRS6 (G5025AW-G6001CF) 212 Alarms Changed in UMTS3 (U2003AK to U3001AO) 216 Alarms Changed in UMTS3 Mtce. (U3001AO to U3029AW) 216 Alarms Changed in UMTS4 (U3029AW to U4002CF) 218 Alarms Changed in SGSN5.0 (G6001CF, U4002CF to LATEST) 221
209
Nortel SGSN Alarms Reference Manual
SGSN5.0
vi Contents Nortel Networks Confidential
411-5221-500
Standard
04.05
January 2007
New in this Release for SGSN Alarms Reference Manual 1-1 Copyright 20042007 Nortel Networks
New in this release 1

The following section details whats new in the Nortel SGSN Alarm Reference Manual NTP for the SGSN5.0 release: Feature impacts Other changes
Feature impacts
The following SGSN5.0 features impact the SGSN Alarms Reference Manual: Combined UMTS/GPRS SGSN Gb over IP 3GPP Gb Flex infrastructure SIGTRAN on SGSN OSPF MD5 authentication on SGSN Radius authentication on SGSN RaConn robustness Diagnostic Failure Enhancements
For details on which alarms changed please see NTP 411-5221-202, Nortel SGSN New in this Release.
Other changes
There are no other changes in this NTP at this time.
GSM UMTS Packet Core Network Nortel SGSN Alarms Reference Manual
SGSN5.0
1-2 New in this Release for SGSN Alarms Reference Manual Nortel Networks Confidential Copyright 20042007 Nortel Networks
411-5221-500
Standard
04.05
January 2007
3 Copyright 20042007 Nortel Networks
SGSN Alarms
This section describes alarms that may be generated by the SGSN. Alarms are listed in sequential order by alarm index. The alarm number is an eight-digit BCD value which consists of two parts. The first part of the alarm number is the index group. For the GPRS and UMTS SGSN, the index group has the assigned value of 7068. The second part of the alarm number is an offset used to identify individual alarms in the SGSN index group. GPRS alarms typically have offsets in the range [1000 1499], while UMTS alarms typically have offsets in the range [1500 - 1999]. Common (GPRS/UMTS) alarms can have offsets in either range. The alarms generated by SGSN components are largely caused by the unavailability of a critical resource or communication link problems. Severity and Status fields in the following tables reflect the behavior of the node, and do not document changes made to alarms by external tools running on the MDM server. The following alarms may be generated by the SGSN for GPRS, UMTS, or both, as indicated in the alarm headings. Any differences between the GPRS and UMTS implementations of alarms generated against common (GPRS and UMTS) components are described in the Details sections for those alarms. Starting in SGSN5.0, the GPRS and UMTS functionality is delivered in one combined software load, and the Usc and Usgsn components are obsoleted. However, there are still some components that are UMTS only (e.g. Usd, Sg, SaalNni), and some that are GPRS only (e.g. Gsd, SgGtl), so the distinction is still made in this document. This document is intended to apply to SGSN5.0 and 2 prior releases, namely GPRS6/UMTS4, and GPRS5/UMTS3. As such, any references to Usc or Usgsn are retained for usage by releases prior to SGSN5.0. A record of which alarms are added/deleted per release is maintained in Appendix D of this document. Table 1 shows a summary of the SGSN5.0 alarms based on each component.
Table 1 Alarm summary per component Comp onent All
sheet 1 of 16
Alarm ID and Name
Alarm severity
Status
SGSN5.0
4 SGSN Alarms Nortel Networks Confidential Table 1 Alarm summary per component (continued) Comp onent Alarm ID and Name
Alarm severity Minor
Status Set/Clear
7068_1580 - Internal Diagnostic Alarm (GPRS/UMTS) DnsAgent 7068_1522 - Loss of Communication with the DnsAgent Servers Alarm (GPRS/UMTS; Obsolete) 7068_1530 - Loss of Redundancy with the DnsAgent Servers Alarm (GPRS/UMTS; Obsolete) 7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) 7068_1578 - Loss of Communication with the DNS Server Alarm (GPRS/UMTS) 7068_1581 - SC Resource Exhaustion Alarm (GPRS/UMTS)
Critical/ Major Minor Major Minor/ Critical Major/ Minor/ Warning
Message Message Message Set/ Clear Set/Clear
Eth100 7068_1612 - Potential Ethernet Port Issue On 2pGPDsk Card (GPRS) Gsc 7068_1005 - GSC Memory Exhausted Alarm (GPRS) 7068_1006 - Subscriber Count Overload Alarm (GPRS/UMTS) Major Critical/ Major/ Minor Major Major Major Major Major Warning Message Set/ Clear/ Message Message Message Message Set Set/Clear Message Critical Set
7068_1010 - GSC Memory Near Exhaustion Alarm (GPRS; Obsolete) 7068_1011 - Routing Area ID Missing Alarm (GPRS/UMTS) 7068_1013 - Loss of connection with SIG (GPRS; Obsolete) 7068_1018 - GSC Initialization Failed Alarm (GPRS) 7068_1024 - SVC Audit Failed Alarm (GPRS/UMTS) 7068_1027 - I/RAU Requests Rejected Alarm (GPRS/UMTS; Obsolete)
sheet 2 of 16
411-5221-500
Standard
04.05
January 2007
Nortel Networks Confidential Table 1 Alarm summary per component (continued) Comp onent Alarm ID and Name
Alarm severity Warning Warning Minor Minor/ Cleared G: Minor Minor Minor Minor Major/ Cleared Major Critical Major Major G:Minor U:Minor/ Cleared
Status Message Message Set/Clear Message G:Set/ Clear Message Set/Clear Set/Clear Message Set/Clear Set/Clear Message Set/Clear Message
7068_1028 - Attach Reject Cause Code Reporting Alarm (GPRS/ UMTS; Obsolete) 7068_1029 - Sgsn-Initiated Session Deactivations Cause Code Reporting Alarm (GPRS/UMTS; Obsolete) 7068_1030 - Mobile-Originated SMS Overload Alarm (GPRS) 7068_1031 - Mobile-Terminated SMS Overload Alarm (GPRS) 7068_1032 - HLR Reset Triggered UGL Overload Alarm (GPRS/ UMTS) 7068_1034 - GSC IMSI Diagnostic Alarm (GPRS/UMTS) 7068_1035 - BSSAP MS-Activity-Indication Overload Alarm (GPRS) 7068_1036 - BSSAP Location Update Request Overload Alarm (GPRS) 7068_1496 - GSC/USC Overload Alarm (GPRS/UMTS; Obsolete) 7068_1507 - Initialization Failure Alarm (GPRS/UMTS; Obsolete) 7068_1511 - MAP Client out of Resources Alarm (GPRS/UMTS) 7068_1518 - SSF SCP Communication Failure Alarm (GPRS/ UMTS) 7068_1519 - SSF Max Camel Dialogues Exceeded Alarm (GPRS/ UMTS) 7068_1520 - MAP Notice Indication Display Alarm (GPRS/UMTS; Obsolete)
7068_1521 - GSC or USC CPU Overload Alarm (GPRS/UMTS)
Critical/ Major/ Minor
Set/Clear
sheet 3 of 16
SGSN5.0
Alarm severity Critical Warning Critical/ Major/ Minor/ Cleared Critical/ Major/ Minor/ Cleared Warning Critical Minor Minor Minor Minor Minor Minor Critical Minor Minor Major Minor/ Major
Status Set/Clear Message G:Messa ge U:Set/ Clear Message
7068_1523 - Loss of Connection with the SIG or SIGTRAN Alarm (GPRS/UMTS) 7068_1529 - Invalid PDP Context Received Alarm (GPRS/ UMTS) 7068_1531 - Attach Requests Rejected or not Received Alarm (GPRS/UMTS; Obsolete)
7068_1532 - PDP Activations Requests Rejected or not Received Alarm (GPRS/UMTS; Obsolete)
7068_1535 - HLR Reset Received Alarm (GPRS/UMTS) 7068_1537 - Registration with IP Server Failure Alarm (GPRS/ UMTS) 7068_1538 - GTP Path High Usage Alarm (GPRS/UMTS) 7068_1539 - GTP Transaction High Usage Alarm (GPRS/UMTS) 7068_1540 - GTP Path Failure Alarm (GPRS/UMTS) 7068_1544 - Attach Overload Alarm (GPRS/UMTS) 7068_1545 - InterSGSN RAU Overload Alarm (GPRS/UMTS) 7068_1549 - SSF InitialDPGPRS Overload Alarm (GPRS/UMTS) 7068_1550 - MAP Client Registration Failure Alarm (GPRS/ UMTS) 7068_1551 - Ss7IpIf Reg Failure alarm (GPRS/UMTS) 7068_1552 - Ss7IpIf Ni Failure alarm (GPRS/UMTS) 7068_1553 - MAP Client IP Network Error Alarm (GPRS/UMTS) 7068_1554 - Sgsn Audit Memory Corruption Alarm (GPRS/ UMTS)
sheet 4 of 16
Message Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear
411-5221-500
Standard
04.05
January 2007
Alarm severity Major Critical Critical Major Minor
Status Message Set/Clear Set/Clear Set/Clear Set/ Clear/ Message Message Message Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear
7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) 7068_1568 - Loss of Communication with MapStack Alarm (GPRS/UMTS) 7068_1569 - Loss of Communication with TcapStack Alarm (GPRS/UMTS) 7068_1570 - SNR Audit Memory Corruption Alarm (GPRS/ UMTS) 7068_1571 - GTP Version Mismatch Alarm (GPRS; Obsolete)
7068_1572 - SC Redundancy Sync Loss Alarm (GPRS/UMTS) 7068_1573 - Switchover During Checkpointing Alarm (GPRS/ UMTS) 7068_1574 - GPRS Attach Success Rate Threshold Alarm (GPRS) 7068_1575 - GPRS Activation Success Rate Threshold Alarm (GPRS) 7068_1607 - UMTS Attach Success Rate Threshold Alarm (UMTS) 7068_1608 - UMTS Activation Success Rate Threshold Alarm (UMTS) 7068_1996 - GMM Context Resources Low Alarm (GPRS; Obsolete) Gsd 7068_1008 - GSD Memory Exhausted Alarm (GPRS; Obsolete) 7068_1009 - Maximum Active Subscribers Reached Alarm (GPRS) 7068_1010 - GSC Memory Near Exhaustion Alarm (GPRS; Obsolete)
sheet 5 of 16
Major Major Major/ Minor Major/ Minor Major/ Minor Major/ Minor Major
Major Major Major
Message Set/Clear Message
SGSN5.0
Alarm severity Minor Major Minor Minor Major Warning Minor/ Major/ Critical Minor Minor Major Major
Status Set/Clear Set Set Set/Clear Set/Clear Set/Clear Message
7068_1012 - GSD Maximum Allocated LLEs Reached Alarm (GPRS) 7068_1019 - GSD Initialization Failed Alarm (GPRS) 7068_1021 - GSD Downlink Buffer Component Add Failed Alarm (GPRS) 7068_1022 - GSD Hardware-Assist Failure Alarm (GPRS) 7068_1024 - SVC Audit Failed Alarm (GPRS/UMTS) 7068_1037 - Maximum Header Compression Memory Usage Alarm (GPRS) 7068_1038 - FrameBuf Congestion Alarm (GPRS)
7068_1039 - GSD Max Allocated LLC-ABM Data Entities Reached Alarm (GPRS) 7068_1040 - GSD Max Allocated Session Entities Reached Alarm (GPRS) 7068_1503 - GSD or USD Out of Resources Alarm (UMTS) (GPRS: Obsolete) 7068_1508 - GSD or USD Memory Initialization Alarm (GPRS/ UMTS)
Set/Clear Set/Clear Set/Clear G: Message U: Set
7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) Liaf 7068_1024 - SVC Audit Failed Alarm (GPRS/UMTS) 7068_1524 - LIAF out of Resources Alarm (GPRS/UMTS) 7068_1525 - LIAF Maximum Subscribers Reached Alarm (GPRS/ UMTS) 7068_1526 - LIAF Initialization Failure Alarm (GPRS/UMTS)
sheet 6 of 16
Major
Message
Major Major Major Major
Set/Clear Set/Clear Set/Clear Set/Clear
411-5221-500
Standard
04.05
January 2007
Alarm severity Major Major Major
Status Set/Clear Message Message
7068_1527 - Loss of Communication with LIG ADMF Alarm (GPRS/UMTS) 7068_1528 - Loss of Communication with LIG DF Server Alarm (GPRS/UMTS) 7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) Mtp3 7066_0100 - Signalling Link Test Failed Alarm (UMTS) 7066_0101 - Destination Inaccessible Alarm (UMTS) 7066_0102 - MTP3 Link Incorrect Mapping Alarm (UMTS) 7066_0103 - MTP3 Link Buffering Error Alarm (UMTS) Nsta 7056_1300 - TDM Link Failure Alarm (UMTS; Obsolete) Saal-nni 7066_0300 - Alignment Failure Alarm (UMTS) 7066_0301 - Layer 2 Peer Disconnect Alarm (UMTS; Obsolete) Sas 7068_1000 - SAS Disk Almost Full Alarm (GPRS; Obsolete) 7068_1001 - SAS Disk High Usage Alarm (GPRS/UMTS)
Major Critical Major Minor
Set/Clear Set/Clear Set Message
Major
Message
Major Major
Set/Clear Message
Minor Critical/ Major/ Minor Critical/ Clear Critical/ Minor Major
Message Set/Clear
7068_1002 - SAS Disk Failure Alarm (GPRS/UMTS) 7068_1003 - CGF Link Failure Alarm (GPRS/UMTS) 7068_1004 - Secondary CGF Link Failure Alarm (GPRS; Obsolete)
sheet 7 of 16
Message Set/Clear Message
SGSN5.0
Alarm severity Critical Warning Major Minor Critical Major Critical/ Major/ Minor Critical/ Major/ Minor
Status Set/Clear Message Message Message Set/Clear Message Set/Clear
7068_1016 - SAS Initialization Failure Alarm (GPRS/UMTS) 7068_1200 - Primary CGF Link Up Alarm (GPRS; Obsolete) 7068_1201 - Secondary CGF Link Up Alarm (GPRS; Obsolete) 7068_1564 - SAS Fail to Send Message to SC Alarm (GPRS/ UMTS) 7068_1566 - SAS Not Ready for Switchover Alarm (GPRS/ UMTS) 7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) 7068_1576 - SAS Memory Pool High Usage Alarm (GPRS/ UMTS) 7068_1577 - SAS Card Memory High Usage Alarm (GPRS/ UMTS) Sccp 7066_0000 - SCCP Connections Near Limit Alarm (UMTS) SctpLayer 7068_1585 - Sigtran Remote Address Inactive alarm (GPRS/ UMTS) Sg 7065_0000 - Mapping Table Full Alarm (UMTS) SgGtl 7068_1017 - GTL Initialization Failure Alarm (GPRS) 7068_1023 - The Number of Unavailable BVCs Has Exceeded the Threshold (GPRS) 7068_1024 - SVC Audit Failed Alarm (GPRS/UMTS)
sheet 8 of 16
Set/Clear
Major
Set/Clear
Minor
Set/Clear
Major
Set/Clear
Major Major Major
Set Set/Clear Set/Clear
411-5221-500
Standard
04.05
January 2007
Nortel Networks Confidential Table 1 Alarm summary per component (continued) Comp onent Alarm ID and Name 7068_1033 - NSVC Unavailable Alarm (GPRS)
Alarm severity Critical/ Major/ Minor Critical/ Major Minor Critical/ Major/ Minor Critical/ Major/ Minor Critical
Status Set/Clear
7068_1041 - Signaling BVC Reset Alarm (GPRS)
Set/ Clear/ Message Message Set/Clear
7068_1043 - Max BVCs per NSE Reached Alarm (GPRS) 7068_1044 - GbIP Data NS-VC Unavailable Alarm (GPRS)
7068_1045 - GbIP Signaling NS-VC Unavailable Alarm (GPRS)
Set/ Clear/ Message Set/ Clear/ Message Message Message Message Set/Clear
7068_1046 - GbIP Dynamic Configuration Failure Alarm (GPRS)
7068_1047 - GbIP Dynamic Configuration Attempts while using Static Configuration Alarm (GPRS) 7068_1499 - Mismatched PTP BVC States Alarm (GPRS) 7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) 7068_1610 - GIPS Unavailable Alarm (GPRS) Sgsn 7068_1020 - Maximum Number of BVCs Per NSE Exceeded Alarm (GPRS; Obsolete) 7068_1025 - Nodal Manager Critical Component Missing Alarm (GPRS/UMTS) 7068_1026 - Nodal Manager Non-critical Component Missing Alarm (GPRS/UMTS) 7068_1202 - NRI Lock Constraint Alarm (GPRS)
sheet 9 of 16
Critical Warning Major Critical
Warning Critical Minor
Message Set/Clear Set/ Clear/ Message Message
Major
SGSN5.0
Alarm severity Major Critical Critical Critical Critical Critical Minor Major Major Major
Status Message Set/Clear Set/Clear Set/Clear Message Set/Clear Set/Clear Set/Clear Message Set/Clear Set/Clear
7068_1203 - All NRIs Locked Message Alarm (GPRS) 7068_1557 - Nodal Manager Call Released Alarm (GPRS/ UMTS) 7068_1558 - Nodal Manager Resource Failure Alarm (GPRS/ UMTS) 7068_1559 - Nodal Manager Registration Alarm (GPRS/UMTS) 7068_1560 - Nodal Manager Outgoing Call Request Failure Alarm (GPRS/UMTS) 7068_1561 - Nodal Manager Incoming Call Timeout Alarm (GPRS/UMTS) 7068_1562 - Nodal Manager Invalid Master Alarm (GPRS/ UMTS) 7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) 7068_1605 - Too Many GSDs Alarm (GPRS/UMTS) 7068_1606 - Too Many GSCs Alarm (GPRS/UMTS) SigtranAsp 7068_1585 - Sigtran Remote Address Inactive alarm (GPRS/ UMTS) 7068_1586 - Sigtran No Destination Routable alarm (GPRS/ UMTS) 7068_1587 - Sigtran No SG Available alarm (GPRS/UMTS) 7068_1588 - Sigtran PeerProcess Not Active alarm (GPRS/ UMTS) 7068_1589 - Sigtran Sgsn PeerProcess Blocked alarm (GPRS/ UMTS) 7068_1590 - Sigtran PeerProcess Congested alarm (GPRS/ UMTS)
sheet 10 of 16
Minor Critical Major Minor Minor Minor
Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear
411-5221-500
Standard
04.05
January 2007
Alarm severity Major Minor Minor Major Major Major Minor Minor Minor Minor Minor Major Critical
Status Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear
7068_1591 - Sigtran Destination Unroutable alarm (GPRS/ UMTS) 7068_1592 - Sigtran Destination Restricted alarm (GPRS/UMTS) 7068_1593 - Sigtran Destination Congested alarm (GPRS/ UMTS) 7068_1594 - Sigtran Unauthorized Associate alarm (GPRS/ UMTS) 7068_1595 - Sigtran Remote Subsystem Unavailable alarm (GPRS/UMTS) 7068_1596 - Sigtran Local Subsystem Unavailable alarm (GPRS/ UMTS) 7068_1597 - Sigtran Unknown Destination alarm (GPRS/UMTS) 7068_1598 - Sigtran TcpConn Congested alarm (GPRS/UMTS) 7068_1599 - Sigtran No Scip Clients Registered alarm (GPRS/ UMTS) 7068_1600 - Sigtran SigConn Down alarm (GPRS/UMTS) 7068_1601 - Sigtran SigConn Congested alarm (GPRS/UMTS) 7068_1602 - Sigtran TcpConn Dropped alarm (GPRS/UMTS) 7068_1603 - Sigtran Asp Initialization Failure alarm (GPRS/ UMTS) Tcap 7068_1495 - MapStack Overload Alarm (GPRS; Obsolete) 7068_1505 - TcapStack Out of Subsystem Resources Alarm (GPRS/UMTS) 7068_1506 - MapStack Out of SGSN MAP Subsystem Resources Alarm (GPRS/UMTS) 7068_1509 - MapStack Out of SGSN MSC Subsystem Resources Alarm (GPRS/UMTS)
sheet 11 of 16
Major/ Cleared Critical/ Minor Critical/ Minor Critical/ Minor
Message Set/Clear Set/Clear Set/Clear
SGSN5.0
Alarm severity Critical/ Minor Major Major Major Minor Minor Minor Major Critical Warning Major/ Cleared Major/ Cleared Minor Minor Minor Minor Minor
Status Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Message Set/Clear Message Message Message Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear
7068_1510 - TcapStack Out of SGSN CAP Subsystem Resources Alarm (GPRS/UMTS) 7068_1512 - Max SGSN MAP Invokes Exceeded Alarm (GPRS; Obsolete) 7068_1513 - Max MSC MAP invokes Exceeded Alarm (GPRS; Obsolete) 7068_1514 - Max CAP invokes Exceeded Alarm (GPRS; Obsolete) 7068_1515 - SGSN MAP Subsystem Bind Failed Alarm (GPRS/ UMTS) 7068_1516 - SGSN MSC Subsystem Bind Failed Alarm (GPRS/ UMTS) 7068_1517 - SGSN CAP Subsystem Bind Failed Alarm (GPRS/ UMTS) 7068_1520 - MAP Notice Indication Display Alarm (GPRS/UMTS; Obsolete) 7068_1523 - Loss of Connection with the SIG or SIGTRAN Alarm (GPRS/UMTS) 7068_1533 - SS7 SIG Problem Alarm (GPRS/UMTS; Obsolete) 7068_1534 - SCCP Notice Indication Throttling Alarm (GPRS/ UMTS; Obsolete) 7068_1536 - TCAP Mobile-Terminated FSM Overload Alarm (GPRS; Obsolete) 7068_1546 - Mobile-Terminated SMS TCAP Overload Alarm (GPRS) 7068_1547 - SAI Overload Alarm (GPRS/UMTS) 7068_1548 - Non-SAI Overload Alarm (GPRS/UMTS) 7068_1551 - Ss7IpIf Reg Failure alarm (GPRS/UMTS) 7068_1552 - Ss7IpIf Ni Failure alarm (GPRS/UMTS)
sheet 12 of 16
411-5221-500
Standard
04.05
January 2007
Alarm severity Minor Major Minor
Status Set/Clear Message Set/Clear
7068_1555 - Ss7IpIf Noisy Link Alarm (GPRS/UMTS) 7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) 7068_1604 - Ss7IpIf NoticeInd Congestion alarm (GPRS/UMTS) Usc 7068_1024 - SVC Audit Failed Alarm (GPRS/UMTS) 7068_1027 - I/RAU Requests Rejected Alarm (GPRS/UMTS; Obsolete) 7068_1028 - Attach Reject Cause Code Reporting Alarm (GPRS/ UMTS; Obsolete) 7068_1029 - Sgsn-Initiated Session Deactivations Cause Code Reporting Alarm (GPRS/UMTS; Obsolete) 7068_1032 - HLR Reset Triggered UGL Overload Alarm (GPRS/ UMTS) 7068_1034 - GSC IMSI Diagnostic Alarm (GPRS/UMTS) 7068_1496 - GSC/USC Overload Alarm (GPRS/UMTS; Obsolete) 7068_1500 - Context Memory Exhausted Alarm (UMTS; Obsolete) 7068_1501 - GMM Max Attaches Exceeded Alarm (UMTS; Obsolete) 7068_1502 - SM Max Active Sessions Exceeded Alarm (UMTS; Obsolete) 7068_1507 - Initialization Failure Alarm (GPRS/UMTS; Obsolete) 7068_1511 - MAP Client out of Resources Alarm (GPRS/UMTS) 7068_1518 - SSF SCP Communication Failure Alarm (GPRS/ UMTS)
sheet 13 of 16
Major Warning Warning Warning U: Major/ Cleared Minor Major/ Cleared Major Critical/ Major/ Minor Major Major Critical Major
Set/Clear Message Message Message U: Message Message Message Set/Clear Set/Clear
Set/Clear Set/Clear Set/Clear Message
SGSN5.0
Alarm severity Major G:Minor U:Minor/ Cleared Critical/ Major/ Minor Critical Warning Critical/ Major/ Minor/ Cleared Critical/ Major/ Minor/ Cleared Warning Critical Minor Minor Minor Minor Major Major/ Minor
Status Set/Clear Message
7068_1519 - SSF Max Camel Dialogues Exceeded Alarm (GPRS/ UMTS) 7068_1520 - MAP Notice Indication Display Alarm (GPRS/UMTS; Obsolete) 7068_1521 - GSC or USC CPU Overload Alarm (GPRS/UMTS)
Set/Clear
7068_1523 - Loss of Connection with the SIG or SIGTRAN Alarm (GPRS/UMTS) 7068_1529 - Invalid PDP Context Received Alarm (GPRS/ UMTS) 7068_1531 - Attach Requests Rejected or not Received Alarm (GPRS/UMTS; Obsolete)
Set/Clear Message Message
Message
7068_1535 - HLR Reset Received Alarm (GPRS/UMTS) 7068_1537 - Registration with IP Server Failure Alarm (GPRS/ UMTS) 7068_1538 - GTP Path High Usage Alarm (GPRS/UMTS) 7068_1539 - GTP Transaction High Usage Alarm (GPRS/UMTS) 7068_1540 - GTP Path Failure Alarm (GPRS/UMTS) 7068_1551 - Ss7IpIf Reg Failure alarm (GPRS/UMTS) 7068_1553 - MAP Client IP Network Error Alarm (GPRS/UMTS) 7068_1554 - Sgsn Audit Memory Corruption Alarm (GPRS/ UMTS)
sheet 14 of 16
Message Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear Set/Clear
411-5221-500
Standard
04.05
January 2007
Alarm severity Minor Warning Major Critical Critical Major Major Major Major/ Minor Warning
Status Message Message Message Set/Clear Set/Clear Set/Clear Message Message Set/Clear Message
7068_1556 - Mobile Context Mismatch In GMM Alarm (UMTS; Obsolete) 7068_1565 - Activation Reject Counter Alarm (UMTS; Obsolete) 7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) 7068_1568 - Loss of Communication with MapStack Alarm (GPRS/UMTS) 7068_1569 - Loss of Communication with TcapStack Alarm (GPRS/UMTS) 7068_1570 - SNR Audit Memory Corruption Alarm (GPRS/ UMTS) 7068_1572 - SC Redundancy Sync Loss Alarm (GPRS/UMTS) 7068_1573 - Switchover During Checkpointing Alarm (GPRS/ UMTS) 7068_1574 - GPRS Attach Success Rate Threshold Alarm (GPRS) 7068_1579 - NPI Calculation Data for Activation Rejects Alarm (UMTS; Obsolete)
Usd 7068_1024 - SVC Audit Failed Alarm (GPRS/UMTS) 7068_1503 - GSD or USD Out of Resources Alarm (UMTS) (GPRS: Obsolete) 7068_1504 - Max Active Sessions Exceeded Alarm (UMTS) 7068_1508 - GSD or USD Memory Initialization Alarm (GPRS/ UMTS) Major Major Major Major Set/Clear Set/Clear Set/Clear G: Message U: Set
sheet 15 of 16
SGSN5.0
Alarm severity Major
Status Message
7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS) VMG 7067_0000 - Media Gateway Heartbeat Alarm (UMTS; Obsolete) 7067_0001 - MgIf Claim Failure Alarm (UMTS; Obsolete) 7067_0002 - Tdmc Claim Failure Alarm (UMTS; Obsolete) 7067_0003 - Q.2630 Blocking Failure Alarm (UMTS; Obsolete) 7067_0004 - Vmg High Resource Usage Alarm (UMTS; Obsolete)
sheet 16 of 16
Major Major Major Major Major
Set/Clear Set/Clear Set/Clear Message Set/Clear
411-5221-500
Standard
04.05
January 2007
7056_1300 - TDM Link Failure Alarm (UMTS; Obsolete) 19 Copyright 20042007 Nortel Networks
7056_1300 - TDM Link Failure Alarm (UMTS; Obsolete)

Alarm 7056 1300 Component Nsta/<x> Vgs Brag/<y> Mtp2 Legend <x>, <y> = component instance identifiers Details The TDM link failure alarm is generated by MTP2 when an error occurs on the TDM link resulting in the link being taken out of service. The link failure could be due to an error in the provisioning of the link, such as a bad timeslot, or to a physical connectivity problem. This alarm is obsoleted in G6001CF and U4002CF. Probable Cause callEstablishmentErrorCause_c Type communicationsType_c Remedial action Confirm provisioning is correct for the link. Verify the health of the physical connectivity of the link. Severity major Status message
SGSN5.0
20 SGSN Alarms Nortel Networks Confidential
7065_0000 - Mapping Table Full Alarm (UMTS)

Alarm 7065 0000 Component Sg/<x> PsDomain Legend <x> = component instance identifier Details The Mapping Table Full alarm is set by Signalling Gateway's RANAP-PS when the mapping table storing the context data for ongoing signalling connections has reached 95% of the value of the maxSigConn attribute under the Sg/x PsDomain component. If the mapping table completely fills up, subsequent connection requests from either SCCP or GPRS Mobility Management (GMM) are rejected. There are two possible reasons for this to occur. First, the mapping table size may be insufficient for the network's demand for connections. A second, and less likely reason, is that stale signalling connections may stay in the mapping table because of the loss of disconnect requests from either SCCP or GMM. This alarm is cleared when the mapping table usage is below 80% of the value of the maxSigConn attribute. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify that the value of the maxSigCon attribute under this Sg/x PsDomain component is sufficient to handle the level of network demand required and increase the maximum if necessary. Also, compare the values of the currentOpenConnections attribute under this Sg/x PsDomain component and the Sccp component. If the value of the currentOpenConnections attribute of the PsDomain component is much lower than that of the Sccp component, then this can indicate that the SG mapping table has stale connections. An LP switchover can be performed on the affected SG to free stale connections. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7066_0000 - SCCP Connections Near Limit Alarm (UMTS) 21 Copyright 20042007 Nortel Networks
7066_0000 - SCCP Connections Near Limit Alarm (UMTS)

Alarm 7066 0000 Component Sccp/<x> Legend <x> = component instance identifier Details When the status is set, at least 95% of the provisioned connections are consumed and in use. The connections are from the local SCCP to the remote SCCP. When all connections are in use, further connection requests will fail until some in-use connections are relinquished. When the status is clear, less than 80% of the provisioned connections are in use, so an adequate pool of connections is available. Probable Cause atOrNearCapacityCause_c Type operatorType_c Remedial action Increase the number of available connections provisioned in SCCP (Sccp maxConnections), or determine why so many connections are being used and decrease the number of connection requests by SCCP users. Severity major Status set/clear
SGSN5.0
7066_0100 - Signalling Link Test Failed Alarm (UMTS)

Alarm 7066 0100 Component Mtp3/<x> Linkset/<y> Link/<z> Legend <x>, <y> = component instance identifiers <z> = link instance identifier; z = 0 - 15 Details This alarm is set by an MTP3 Link when the Signalling Link Test (SLT) fails, indicating the Signalling Link Test Controller (SLTC) detected a failed link. Once the link failure is detected, it will be restarted. This alarm is cleared when an SLT for the same link is successful. Probable Cause callEstablishmentErrorCause_c Type communicationsType_c Remedial action Monitor the failed link to ensure the link comes back into service. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7066_0101 - Destination Inaccessible Alarm (UMTS) 23 Copyright 20042007 Nortel Networks
7066_0101 - Destination Inaccessible Alarm (UMTS)

Alarm 7066 0101 Component Mtp3/<x> Linkset/<y> Legend <x>, <y> = component instance identifiers Details The Destination Inaccessible Alarm is raised by the Mtp3/<x> Linkset/<y> component when a destination (i.e. remote MTP3) is inaccessible due to all links in the linkset being inaccessible. The destination is considered inaccessible when all links in the linkset are either locked or disabled. The destination point code is displayed in the alarm along with some link debug information. This alarm is cleared when a destination becomes accessible due to one or more links in the linkset becoming accessible. The destination becomes accessible when a locked linked becomes unlocked or a disabled link becomes enabled. Probable Cause localTransmissionErrorCause_c Type communicationsType_c Remedial action When the status is set, links that are locked may be unlocked as appropriate. For disabled links, they should be monitored to ensure the links come back into service. When the status is clear, no remedial action is necessary. Severity critical Status set/clear
SGSN5.0
7066_0102 - MTP3 Link Incorrect Mapping Alarm (UMTS)

Alarm 7066 0102 Component Mtp3/<x> Linkset/<y> Link/<z> Legend <x>, <y> = component instance identifiers <z> = link instance identifier; z = 0 - 15 Details When the status is set, an MTP3 link has failed because the link has been mapped incorrectly. The link is incorrectly mapped since it is disabled and carrying payload traffic. Probable Cause localTransmissionErrorCause_c Type communicationsType_c Remedial action When the status is set, the MTP3 link is disabled. The mapping for this MTP3 linkset is incorrect. Reset the card to recover this linkset. Severity major Status set
411-5221-500
Standard
04.05
January 2007
7066_0103 - MTP3 Link Buffering Error Alarm (UMTS) 25 Copyright 20042007 Nortel Networks
7066_0103 - MTP3 Link Buffering Error Alarm (UMTS)

Alarm 7066 0103 Component Mtp3/<x> Linkset/<y> Link/<z> Legend <x>, <y> = component instance identifiers <z> = link instance identifier; z = 0 - 15 Details This alarm has been raised since an audit of the MTP3 links has detected a problem scenario. The audit will detect if an enabled MTP3 link is buffering payload traffic. The alarm will notify the operator that this condition has been encountered on an MTP3 link. The link may be marked as failed when the alarm is generated (look in the remedial action section for more details). This will allow the MTP3 link to clean up this error scenario and come up to a stable state. Probable Cause callEstablishmentErrorCause_c Type communicationsType_c Remedial action The MTP3 link audit is implemented in debug and action mode. In debug mode, the alarm will be generated to notify the operator that the above scenario has been detected, no action will be taken to recover this link. In action mode, the link will be marked as failed, along with the generated alarm. Severity minor Status message
SGSN5.0
7066_0300 - Alignment Failure Alarm (UMTS)

Alarm 7066 0300 Component SaalNni/<x> Legend <x> = component instance identifier Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
Nortel Networks Confidential Alarm Component
7066_0300 - Alignment Failure Alarm (UMTS) 27 Copyright 20042007 Nortel Networks Severity Status
Details The Alignment Failure alarm is raised by the SaalNni component when alignment fails with the peer SaalNni layer. The alignment fails when the operational attribute SaalNni/<x> currentProvingPdus is lower than operational attribute SaalNni/<x> targetProvingPdus. If SaalNni receives less than the expected value then there is a communication problem which could be due to congestion. The following cause codes are used in the alarm text: ATM I/F is Down This cause code indicates a failure on the ATM layer. This cause code can be displayed for SONET and SDH failures. Remote Release This cause code indicates that the remote end has released the connection. This is most likely to occur in the case where the Core Network (CN) is not responding to an SLT (Signalling Link Test) message from the RNC. This will happen during SG card resets and IP failures between Layer2 and Layer3. Local Release This cause code indicates that a local Layer3 connection has released the link and has sent a STOP request to Layer2. This happens in cases where SLT messages are not being acknowledged by the RNC. This also happens if an IP failure occurs between Layer2 and Layer3. noResponse Timer Expired This cause code indicates that Layer2 did not receive an acknowledgement from the RNC for a POLL message (an integrity message sent every 500 msec) within the provisioned noResponse time. This will result in Layer2 releasing the link and sending an OOS (Out of Service) message to Layer2. This cause code can be displayed if the RNC is down or any ATM layer connections are down between the AN and the RNC. Alignment Interval Expired This cause code indicates that an alignment message from Layer2 was not acknowledged by the RNC within the provisioned time. This cause code can be displayed if the RNC is down or any ATM layer connections are down between the AN and the RNC.
When currentProvingPdus is equal to the targetProvingPdus, then the link is working properly, since there was no loss of PDUS during the proving process. The alarm is cleared when alignment on the link completes successfully as a result of increased bandwidth or the reduction of traffic.
SGSN5.0
28 SGSN Alarms Nortel Networks Confidential Alarm Component Probable Cause callEstablishmentErrorCause_c Type communicationsType_c
Copyright 20042007 Nortel Networks Severity Status
Remedial action When the status is set, verify the bandwidth is sufficient to support the link and increase it if necessary. Verify the health of the physical connectivity (e.g. optical link or interface). When the status is clear, no remedial action is necessary.
411-5221-500
Standard
04.05
January 2007
7066_0301 - Layer 2 Peer Disconnect Alarm (UMTS; Obsolete) 29 Copyright 20042007 Nortel Networks
7066_0301 - Layer 2 Peer Disconnect Alarm (UMTS; Obsolete)

Alarm 7066 0301 Component SaalNni/<x> Legend <x> = component instance identifier Details The layer 2 peer disconnect alarm is generated by SaalNni when a peer SaalNni releases the link and disconnects. The disconnect occurs as a result of the peer SaalNni sending a release indication to the local SaalNni which ultimately results in the link being taken out of service. This alarm is obsoleted in UMTS3 Mtce. Probable Cause remoteTransmissionErrorCause_c Type communicationsType_c Remedial action Determine what incompatibility or engineering change has occurred at the peer SaalNni to cause it to generate a release indication. Severity major Status message
SGSN5.0
7067_0000 - Media Gateway Heartbeat Alarm (UMTS; Obsolete)

Alarm 7067 0000 Component Vmg/<x> MgIf/<y> Legend <x>, <y> = component instance identifiers Details When the status is set, the Virtual Media Gateway has lost the signalling connection with the Media Gateway indicated by failed heartbeat messages. As a result no Aspen messaging to or from the Media Gateway will occur. While the condition persists, the Virtual Media Gateway will discard any unsendable messages and reject any new calls. Possible causes for the loss of heartbeat is a Media Gateway Reset or a loss of physical connectivity with the Media Gateway. When the status is clear, the component has re-established its connection with the Media Gateway indicated by the success of heartbeat messages. This alarm is obsoleted in G6001CF and U4002CF. Probable Cause lossOfSignalCause_c Type communicationsType_c Remedial action When the status is set, verify the Media Gateway is available and connectivity is correct. When the status is clear, no remedial action is necessary. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7067_0001 - MgIf Claim Failure Alarm (UMTS; Obsolete) 31 Copyright 20042007 Nortel Networks
7067_0001 - MgIf Claim Failure Alarm (UMTS; Obsolete)

Alarm 7067 0001 Component Vmg/<x> MgIf/<y> Legend <x>, <y> = component instance identifiers Details This alarm indicates that an MGIfController instance needs to be provisioned on the Media Gateway. The alarm will trigger if SG fails to claim a partition on the MG. That means there are a less partitions provisioned on the MG than the number of SGs trying to claim them. MG will accept a partition claim from SG if it has a free partition. If there is no free partition available it will Nack the claim message from SG, and SG will generate Mgif Claim Failure Alarm. This alarm is obsoleted in G6001CF and U4002CF. Probable Cause operationalConditionCause_c Type operatorType_c Remedial action The corresponding Media Gateway MGIfController instance has to be provisioned. Severity major Status set/clear
SGSN5.0
7067_0002 - Tdmc Claim Failure Alarm (UMTS; Obsolete)

Alarm 7067 0002 Component Vmg/<x> MgIf/<y> TdmRes/<z> Legend <x>, <y>, <z> = component instance identifiers Details The TDM resource component will try to acquire the TDM Resource (E1) by sending a claim message to the MediaGateway. This alarm indicates this Mediagateway Interface (MgIf) on Signalling Gateway failed to claim the TdmResource(E1) on the Media Gateway. This could happen if this E1 or one or more timeslots on this E1 are not provisioned or have been claimed by other MgIfs. The alarm will be set when the problem is detected and it will be cleared when the remedial action is taken on the Media Gateway. This alarm is obsoleted in G6001CF and U4002CF. Probable Cause operationalConditionCause_c Type operatorType_c Remedial action When this alarm comes out, the customer shall check corresponding Media Gateway (VSP card) by displaying Nsta Vgs AmrBrag or Nsta Vgs CsdBrag component to find out which time slots on this E1 have been claimed or not provisioned. The timeslots of the TDMResource have to be reprovisioned. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7067_0003 - Q.2630 Blocking Failure Alarm (UMTS; Obsolete) 33 Copyright 20042007 Nortel Networks
7067_0003 - Q.2630 Blocking Failure Alarm (UMTS; Obsolete)

Alarm 7067 0003 Component Vmg/<x> Legend <x> = component instance identifier Details This alarm is set and shows Block was sent, and no Block Confirm was received. upon the Block timer expiry after the Q.2630 Block is sent to the RNC. This alarm is set and shows Unlock was sent, and no Unblock Confirm was received. upon the Unblock timer expiry after the Q.2630 Block is sent to the RNC. The alarm is cleared after the information is displayed. This alarm is obsoleted in G6001CF and U4002CF. Probable Cause callEstablishmentErrorCause_c Type communicationsType_c Remedial action Severity major Status message
This is an information alarm. No remedial action is expected.
SGSN5.0
7067_0004 - Vmg High Resource Usage Alarm (UMTS; Obsolete)

Alarm 7067 0004 Component Vmg/<x> Legend <x> = component instance identifier Details This alarm indicates that the DS0 resource usage has exceeded the provisioned Threshold. The alarm will trigger if the total DS0 in used, this include actual call connections, blocked channels or out of service channels, has exceeded the threshold percentage set by the provisionable attribute. i.e if there is 100 DS0s provisioned and the alarm threshold is set to 75%, then when more than 75 DS0s has been used either by call connection, blocked or Out of Service, the alarm will trigger. Vice versa, the alarm will clear when the usage percentage has dropped below the provisionable clear threshold. This alarm is obsoleted in G6001CF and U4002CF. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action Provision additional TDM. Unlock resources. Clear Out of Service resources. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1000 - SAS Disk Almost Full Alarm (GPRS; Obsolete) 35 Copyright 20042007 Nortel Networks
7068_1000 - SAS Disk Almost Full Alarm (GPRS; Obsolete)

Alarm 7068 1000 Component Sas/<x> Legend <x> = component instance identifier Details The SAS Disk Almost Full alarm is raised by the SAS component when the hard disk usage exceeds 85%. This alarm may indicate that there is be a problem off-loading the collected charging information to the Charging Gateway Function (CGF). This could be due to a problem with the network path to the CGF, or due to a problem with the CGF itself. This alarm is obsoleted in GPRS05. Probable Cause equipmentFailureCause_c Type equipmentType_c Remedial action Verify the health of the network path to the CGF. Verify that the CGF is functioning properly. Severity minor Status message
SGSN5.0
7068_1001 - SAS Disk High Usage Alarm (GPRS/UMTS)

Alarm 7068 1001 Component Sas/<x> Legend <x> = component instance identifier Details The SAS Disk High Usage alarm is raised by the Sas component when certain disk usage thresholds are crossed on the SASs hard disk. The severities and usage levels are as follows: Minor -- the disk usage reached 85% full. Major -- the disk usage reached 90% full. Critical -- the disk usage reached 99% full. Clear -- the disk usage fell below 75% full. This alarm indicates that there is a danger of rendering the SAS application inoperable if the disk runs out of space. Since the disk will fill up if the SAS application is unable to off-load collected charging information to the CGF, the likely cause is a problem with the network path to the CGF or the CGF itself. The severity of this alarm is raised to higher levels as more disk space is consumed. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c Type communicationsType_c Remedial action Verify the health of the network path to the CGF. Verify that the CGF is functioning properly. Severity critical/ major/minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1002 - SAS Disk Failure Alarm (GPRS/UMTS) 37 Copyright 20042007 Nortel Networks
7068_1002 - SAS Disk Failure Alarm (GPRS/UMTS)

Alarm 7068 1002 Component Sas/<x> Legend <x> = component instance identifier Details The SAS Disk Failure Alarm is raised by the Sas component when a hard disk failure is detected rendering the hard disk inaccessible. This alarm indicates that the collected charging information cannot be saved to the hard disk or sent to the Charging Gateway Functionality (CGF). All information on the hard disk not transferred to the CGF is lost. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause equipmentFailureCause_c Type equipmentType_c Remedial action Replace the disk drive or the entire FP card. Severity critical/ cleared Status message
SGSN5.0
7068_1003 - CGF Link Failure Alarm (GPRS/UMTS)

Alarm 7068 1003 Component Sas/<x> Legend <x> = component instance identifier Details The CGF Link Failure alarm is raised by the Sas component when a loss of communication is detected with the Primary or Secondary Charging Gateway Functionality (CGF). This communication link problem is detected by the Sas component when a GTP protocol message is not acknowledged by the CGF, or if the CGF fails to respond to an Echo Request Message from the SAS component. When a communication problem is detected with the primary CGF, the SAS application sends the collected charging information to the secondary CGF. The alarm severity is set to the following: Minor -- When both the Primary and Secondary CGF are provisioned, and one of the two is unreachable. Critical -- When both the Primary and Secondary CGF are provisioned, and both are unreachable; or when only one CGF is provisioned, and it is unreachable. This alarm is cleared when all of the provisioned CGFs are reachable. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause underlyingResourceUnavailableCause_c Type communicationsType_c Remedial action Verify the health of the network path to the primary CGF. Verify the primary CGF is functioning properly. Severity critical/minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1004 - Secondary CGF Link Failure Alarm (GPRS; Obsolete) 39 Copyright 20042007 Nortel Networks
7068_1004 - Secondary CGF Link Failure Alarm (GPRS; Obsolete) 2

Alarm 7068 1004 Component Sas/<x> Legend <x> = component instance identifier Details The secondary CGF link failure alarm is generated by the Sas component when a loss of communication is detected with the secondary Charging Gateway Functionality (CGF). The communication link problem is detected by the SAS application when a GTP protocol message is not ackd by the CGF or if the CGF fails to respond to a echo request message from the SAS. If this communication is lost at the same time as communication to the primary CGF is lost, no billing records can be sent to a CGF. Billing records are stored locally on the SGSN until either the primary or secondary CGF becomes available. This alarm is obsoleted in GPRS05 and replaced with CGF Link Failure (7068 1003). Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action Verify the health of the network path to the secondary CGF. Verify the secondary CGF is functioning properly. Severity major Status message
SGSN5.0
7068_1005 - GSC Memory Exhausted Alarm (GPRS)

Alarm 7068 1005 Component Gsc/<x> Legend <x> = component instance identifier Details The GSC Memory Exhausted alarm is raised by the Gsc component when it is unable to reserve additional contexts because of memory exhaustion. This alarm will be raised when there is a failure to allocate memory for the following context types: BSSAP Subscriber GMM Attach GMM Detach GMM RAU GMM Security GMM User Requested Security GMM Suspend Resume GMM Reset GMM Assign GTPS Message GTPS PDP SM Session The alarm text describes what context type failed because of unavailable memory resources. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify and lower the values of the following provisioned attributes for the GSC, since the amount of memory needed is derived from them. Gsc avgActivePdpCPerActiveSub Gsc maxAttachedSubscribers Gsc Gmm percentSimulAttaches Gsc Gmm percentSimulDetaches Gsc Gmm percentSimulPagingRequests Gsc Gmm percentSimulRoutingAreaUpdates Gsc Gmm percentSimulAuthAndCiphReqs Gsc Gmm percentSimulBssgpSuspResumeInds Gsc Gtp maxTransactions Severity major Status message
411-5221-500
Standard
04.05
January 2007
7068_1006 - Subscriber Count Overload Alarm (GPRS/UMTS) 41 Copyright 20042007 Nortel Networks
7068_1006 - Subscriber Count Overload Alarm (GPRS/UMTS)

Alarm 7068 1006 Component Gsc/<x> Severity critical/ major/minor Status set/ clear/ message
Legend <x> = component instance identifier Details The Subscriber Count Overload alarm is raised by the Gsc component when the number of attached subscribers exceeds the preset percentages of the provisionable attribute maxAttachedSubscribers under the Gsc component. The alarm severity is increased as the currently attached subscribers exceeds the following thresholds: Minor - 90% of the maximum allowed attached subscribers Major - 95% of the maximum allowed attached subscribers Critical - 100% of the maximum allowed attached subscribers The alarm severity is reduced as the currently attached subscribers falls below the following thresholds: Major - 98% of the maximum allowed attached subscribers. Minor - 93% of the maximum allowed attached subscribers. Cleared - 88% of the maximum allowed attached subscribers. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c Type processingType_c Remedial action Verify that the value of the maxAttachedSubscribers provisionable attribute under this GSC component is sufficient to handle the level of subscriber demand required and increase the maximum if necessary.
SGSN5.0
7068_1008 - GSD Memory Exhausted Alarm (GPRS; Obsolete)

Alarm 7068 1008 Component Gsd/<x> Legend <x> = component instance identifier Details The alarm is generated by the GSD when it is unable to acquire any more memory. This alarm is obsoleted in GPRS05. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify and lower values of the GSDs, and of its subcomponents provisioned attributes for maxLlcActiveSubscribers, maxRfc144Entities, maxV42bisEntities and v42bisCompressionDirections, since the amount of memory needed is derived from them. Severity major Status message
411-5221-500
Standard
04.05
January 2007
7068_1009 - Maximum Active Subscribers Reached Alarm (GPRS) 43 Copyright 20042007 Nortel Networks
7068_1009 - Maximum Active Subscribers Reached Alarm (GPRS) 2

Alarm 7068 1009 Component Gsd/<x> Legend <x> = component instance identifier Details The GSD Maximum Active Subscribers Reached alarm is raised by the Gsd component when the number of active subscribers reaches the provisioned limit (Gsd maxLlcActiveSubscribers). No new subscribers are allowed to activate on this Gsd until after the number of active subscribers falls below the provisioned limit. This alarm is cleared when the number of active subscribers falls below 95% of the provisioned limit. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify that the value of the maxLlcActiveSubscribers provisionable attribute under this Gsd component is sufficient to handle the level of subscriber demand required, and increase the maximum if necessary. Severity major Status set/clear
SGSN5.0
7068_1010 - GSC Memory Near Exhaustion Alarm (GPRS; Obsolete)2

Alarm 7068 1010 Component Gsc/<x> Legend <x> = component instance identifier Details The alarm is generated by the GSC when after GSCs initialization the amount of available memory is below 50000KB. This alarm is obsoleted in GPRS05 and replaced by Initialization Failed (7068 1018). Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify and lower values of the GSCs provisioned attributes, since the amount of memory needed is derived from them. Severity major Status message
411-5221-500
Standard
04.05
January 2007
7068_1011 - Routing Area ID Missing Alarm (GPRS/UMTS) 45 Copyright 20042007 Nortel Networks
7068_1011 - Routing Area ID Missing Alarm (GPRS/UMTS)

Alarm 7068 1011 Component Gsc/<x> Legend <x> = component instance identifier Details The Routing Area ID (RAI) Missing alarm is raised by the Gsc component once every hour if, during the preceding hour, GMM sent at least one message to a routing area that was not found on this SGSN. This alarm can be generated if the RAI is not provisioned on this SGSN or is provisioned incorrectly. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause configurationErrorCause_c Type processingType_c Remedial action Provision the Sgsn Mcc/<x> Mnc/<x> Lac/<x> Rac/<x> for the new routing area using the values specified in the alarm text. Severity major Status message
SGSN5.0
7068_1012 - GSD Maximum Allocated LLEs Reached Alarm (GPRS) 2

Alarm 7068 1012 Component Gsd/<x> Legend <x> = component instance identifier Details The GSD Maximum Allocated LLEs Reached alarm is raised by the Gsd component when the number of allocated Logical Link Entities (LLEs) reaches the calculated limit, which is the product of the provisionable attributes Gsd Llc LleToMobileRatio and Gsd MaxLlcActiveSubscribers under this Gsd component. No new LLEs are allocated on this Gsd component until after the number of LLEs falls below the limit. The impact is that new PDP sessions are not able to activate on new data LLEs and mobiles may not be able to use SMS. Mobiles attached on this GSD trying to activate a new PDP session on a new data SAPI will receive a PDP activation rejection with the Insufficient Resource cause value. This alarm is cleared when the number of allocated LLEs falls below 95% of the calculated limit. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify that the values of the provisionable attributes Gsd MaxLlcActiveSubscribers and Gsd Llc LleToMobileRatio under this Gsd component are sufficient to handle the level of subscriber demand required. Increase if necessary. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1013 - Loss of connection with SIG (GPRS; Obsolete) 47 Copyright 20042007 Nortel Networks
7068_1013 - Loss of connection with SIG (GPRS; Obsolete)

Alarm 7068 1013 Component Gsc/<x> Legend <x> = component instance identifier Details The alarm is generated by the GSC when MapClient loses tcp connection with the SIG. This alarm has been obsoleted in GPRS05. Probable Cause commSubsystemFailureCause_c Type communicationsType_c Remedial action Verify the connection of the GSC application with the SIG Severity major Status message
SGSN5.0
7068_1016 - SAS Initialization Failure Alarm (GPRS/UMTS)

Alarm 7068 1016 Component Sas/<x> Legend <x> = component instance identifier Details The SAS Initialization Failure alarm is raised by the Sas component when the SAS application initialization fails. The alarm is cleared when the card is reset and initialization completes successfully. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause configurationErrorCause_c Type processingType_c Remedial action Review the alarm text and check the provisioning is set appropriately and then reset the card. Severity critical Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1017 - GTL Initialization Failure Alarm (GPRS) 49 Copyright 20042007 Nortel Networks
7068_1017 - GTL Initialization Failure Alarm (GPRS)

Alarm 7068 1017 Component SgGtl/<x> Legend <x> = component instance identifier Details This alarm is set if the GTL application fails to initialize, which includes such tasks as reserving memory and creating objects. The alarm is cleared hierarchically after a card reset. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Check the GTL for over-provisioning and reset the card. Severity major Status set
SGSN5.0
7068_1018 - GSC Initialization Failed Alarm (GPRS)

Alarm 7068 1018 Component Gsc/<x> Legend <x> = component instance identifier Details The GSC Initialization Failed alarm is raised when the Gsc component fails to initialize and the GSC application is not ready. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Using the alarm text, verify that the Gsc components provisioning is within the engineered limits and then reset the card. Severity major Status set
411-5221-500
Standard
04.05
January 2007
7068_1019 - GSD Initialization Failed Alarm (GPRS) 51 Copyright 20042007 Nortel Networks
7068_1019 - GSD Initialization Failed Alarm (GPRS)

Alarm 7068 1019 Component Gsd/<x> Legend <x> = component instance identifier Details The GSD Initialization Failed alarm is raised when the Gsd component fails to initialize and the GSD application is not ready. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Using the alarm text, verify that the Gsd components provisioning is within the engineered limits and then reset the card. Severity major Status set
SGSN5.0
7068_1020 - Maximum Number of BVCs Per NSE Exceeded Alarm (GPRS; Obsolete)
Alarm 7068 1020 Component Sgsn Legend N/A Details The Maximum Number of BVCs Per NSE Exceeded alarm is raised by the Sgsn component when the number of BSSGP Virtual Connections (BVCs) per Network Services Entity (NSE) provisioned limit has been exceeded. This alarm is raised whenever a BVC Reset message is received from the BSS and the number of BVCs currently active on that NSE is greater than the value provisioned by the maxBvcsPerNse attribute under the Sgsn component. This alarm is obsoleted by 7068_1043. Probable Cause unknownCause_c Type unknownType_c Remedial action None Severity warning Status message
411-5221-500
Standard
04.05
January 2007
7068_1021 - GSD Downlink Buffer Component Add Failed Alarm (GPRS) 53 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1021 - GSD Downlink Buffer Component Add Failed Alarm (GPRS)

Alarm 7068 1021 Component Gsd/<x> Legend <x> = component instance identifier Details The GSD Downlink Buffer Component Add Failed alarm is raised by the Gsd component when an attempt to add the DownlinkBuffer component under this Gsd PduBuf component fails. This alarm indicates that there is not enough free memory available to accommodate this component. This error does not cause provisioning to fail; however, the DownlinkBuffer is not added and the DownlinkBuffer functionality is not enabled. Probable Cause outOfMemoryCause_c Type equipmentType_c Remedial action Re-provision the Gsd component to use less memory resources and re-add the DBuff component to the Gsd PduBuf component. Severity minor Status set
SGSN5.0
7068_1022 - GSD Hardware-Assist Failure Alarm (GPRS)

Alarm 7068 1022 Component Gsd/<x> Legend <x> = component instance identifier Details The Hardware-Assist Failure alarm is raised by the Gsd component when the Logical Link Controller (LLC) switches from hardware ciphering to software ciphering. This alarm is raised when there is a hardware failure on the WPDS FP card upon which this Gsd component is provisioned. To avoid further loss of frames, the frame processing is switched from hardware ciphering to software ciphering. The impact of using software ciphering is that the ciphered frame capacity is reduced. This alarm is cleared hierarchically upon card reset, but a clear alarm is also provided for the possible future functionality of switching back to hardware ciphering automatically. Probable Cause lossOfFrameCause_c Type equipmentType_c Remedial action To re-enable hardware ciphering the card must be reset. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1023 - The Number of Unavailable BVCs Has Exceeded the Threshold (GPRS) 55 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1023 - The Number of Unavailable BVCs Has Exceeded the Threshold (GPRS)
Alarm 7068 1023 Component SgGtl/<x> Nse Legend <x> = component instance identifier Details The Number of Unavailable BVCs Has Exceeded the Threshold alarm is raised by the Nse component when the number of unavailable BSSGP Virtual Connections (BVCs) has exceeded the threshold set by the provisionable attribute bvcBlockedSetThreshold under the SgGtl component. A BVC is defined as unavailable when any of the following are true: A BVC is blocked beyond an amount of time specified by the provisionable attribute bvcBlockedTimer under the SgGtl component. Flow Control parameter Bmax=0 beyond an amount of time specified by the provisionable attribute bvcBmaxTimer under the SgGtl component. Flow Control parameter LeakRate=0 beyond an amount of time specified by the provisionable attribute bvcLeakRateTimer under the SgGtl component. The alarm is cleared when the number of unavailable BVCs falls below the provisionable attribute bvcBlockedClrThreshold. Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action Verify that the threshold and timer provisionable attributes are set properly. Severity major Status set/clear
SGSN5.0
7068_1024 - SVC Audit Failed Alarm (GPRS/UMTS)

Alarm 7068 1024 Component Gsc/<x> Gsd/<x> Liaf/<x> Sas/<x> Sg/<x> SgGtl/<x> SigtranAsp/<x> Tcap/<x> Usd/<x> Legend <x> = component instance identifier Details The SVC Audit Failed alarm is raised by the following components when they are unable to establish any applicable outgoing or incoming switched virtual circuit (SVC) as follows: - Gsc: The GSC application is unable to establish outgoing SVCs to the GSD, USD, SAS, or TCAP applications, or when the SVCs from SG, LIAF or other GSCs are not established. - Gsd: The GSD application is unable to establish outgoing SVCs to the GTL application, or when the SVCs from GSC, LIAF are not established. - Liaf: The LIAF application is unable to establish outgoing SVCs to the GSD, GSC, or USD applications. - Sas: The SVCs from GSC applications are not established. - Sg: The SG application is unable to establish outgoing SVCs to the GSC application. - SgGtl: The SVCs from/to other GTL applications, or from GSD applications are not established. - Tcap: The SVCs from GSC applications are not established. - Usd: The USD application is unable to establish incoming SVCs from GSC or LIAF applications. -SigtranAsp: The SVCs from/to other SigtranAsp applications are not established. This alarm is cleared when all applicable outgoing and incoming SVCs for a given component are established. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause lossOfSignalCause_c Severity Status
major
set/clear
411-5221-500
Standard
04.05
January 2007
Nortel Networks Confidential Alarm Component Type communicationsType_c
7068_1024 - SVC Audit Failed Alarm (GPRS/UMTS) 57 Copyright 20042007 Nortel Networks Severity Status
Remedial action Verify the health of the ATM connections between the Passport shelves, including cabling and provisioning.
SGSN5.0
7068_1025 - Nodal Manager Critical Component Missing Alarm (GPRS/UMTS)

Alarm 7068 1025 Component Sgsn Usgsn Legend N/A Details The Nodal Manager Critical Component Missing alarm is raised when a critical component such as the Gsd, Gtl (GPRS) or Usd, Sg (UMTS) or Gsc, Map (GPRS/UMTS) does not register with the Nodal Manager application. The registration failure could be caused by critical components not being provisioned. The alarm generation is based on the following: Since there can be either a GPRS only or a UMTS only or a combo GPRS and UMTS SGSN, the alarm also indicates three different types of impacts i.e. GPRS, UMTS or both. If either Gsc or Map components are not registered, then it is assumed to have both GPRS and UMTS impact. Further, if neither GPRS specific critical component pair namely Gtl and Gsd nor UMTS specific critical component pair namely Sg and Usd are registered i.e. the SGSN is not able to process either GPRS or UMTS calls, then the impact is considered as both. If Gtl application is registered but not Gsd or vice versa and none of UMTS specific components Sg and Usd are registered, then the impact is considered as GPRS only. Similarly, if Sg application is registered but not Usd or vice versa and none of GPRS specific components namely Gtl and Gsd are registered, then the impact is considered as UMTS only. For GPRS only impact: Alarm text begins with - "The following GPRS critical applications do not have an instance registered: " Missing applications included in alarm text - only Gsc, Map, Gtl and Gsd. Sg and Usd are not included even if provisioned but not registered. Severity critical Status set/clear
For UMTS only impact: Alarm text begins with - "The following UMTS critical applications do not have an instance registered: " Missing applications included in alarm text - only Gsc, Map, Sg and Usd. Gtl and Gsd not included even if provisioned but not registered.
411-5221-500
Standard
04.05
January 2007
7068_1025 - Nodal Manager Critical Component Missing Alarm (GPRS/UMTS) 59 Nortel Networks Confidential Copyright 20042007 Nortel Networks Alarm Component Details For GPRS and UMTS impact: Alarm text begins with - "The following GPRS and UMTS critical applications do not have an instance registered: " Missing applications included in alarm text - All critical applications. Severity Status
Clearing the Alarm: The alarm is cleared if the SGSN is able to process either GPRS or UMTS calls or both and there is no mismatch on the other interface (Gb/Iu). If on a combo SGSN with both Iu and Gb configured, the alarm will still be cleared if all required GPRS components are registered but none of UMTS specific components namely Sg and Usd are registered. On the other hand, the alarm will be set if either Sg or Usd is registered but not the other (with all GPRS components registered). Similarly, on a combo SGSN with both Iu and Gb configured, the alarm will still be cleared if all required UMTS components are registered but none of the GPRS specific components namely Gtl and Gsd are registered. On the other hand, the alarm will be set if either Gtl or Gsd is registered but not the other (with all UMTS components registered). Probable Cause applSubsystemFailCause_c configurationErrorCause_c Type processingType_c Remedial action Verify that the critical components have been provisioned properly.
SGSN5.0
7068_1026 - Nodal Manager Non-critical Component Missing Alarm (GPRS/UMTS) 2

Alarm 7068 1026 Component Sgsn Usgsn Legend N/A Details The Nodal Manager Non-critical Component Missing alarm is raised by the master shelf when a non-critical component such as the Sas, Liaf or Sigtran component does not register with the Nodal Manager application. The registration failure could be caused by non-critical components not being provisioned. The alarm is cleared when at least one instance of each non-critical component registers with the Nodal Manager application. Note: Sas, Liaf, and Sigtran are not required for proper system operation. Specifically: Sigtran is not required if the Gr interface is implemented using the more traditional SS7 transport. Liaf is not required if lawful intercept capabilities are not needed. Sas is not required if billing records are not to be generated by the SGSN, but rather by some other node in the network, possibly the GGSN. Severity minor Status set/ clear/ message
In SGSN5.0 and later, this alarm is just a message alarm,as it can not always be determined whether the applications are wanted by the operator, so an informational alarm is more appropriate. Probable Cause applSubsystemFailCause_c configurationErrorCause_c Type processingType_c Remedial action Verify that the non-critical components have been provisioned properly.
411-5221-500
Standard
04.05
January 2007
7068_1027 - I/RAU Requests Rejected Alarm (GPRS/UMTS; Obsolete) 61 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1027 - I/RAU Requests Rejected Alarm (GPRS/UMTS; Obsolete)2

Alarm 7068 1027 Component Gsc/<x> Gmm Usc/<x> Gmm Legend <x> = component instance identifier Details This alarm is raised by the Gmm component at the end of the collection interval if the alarm generation is enabled and if IRAU or RAU requests are rejected for specific reasons during that period. The alarm text lists the reject counts for the collection interval for each of the reject reasons. IRAU reject reasons displayed: Network failure Msg not compatible with the protocol state Congestion MS ID cannot be derived by the network Invalid mandatory information Illegal ME Illegal MS GPRS service not allowed Implicitly detached Protocol error unspecified Severity warning Status message
RAU reject reasons displayed: Network failure Implicitly detached
This alarm is obsoleted in G6001CF and U4002CF. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action Verify the health of the network. This alarm is informational in nature.
SGSN5.0
7068_1028 - Attach Reject Cause Code Reporting Alarm (GPRS/ UMTS; Obsolete)
Alarm 7068 1028 Component Gsc/<x> Gmm Usc/<x> Gmm Legend <x> = component instance identifier Details This alarm is raised by the Gmm component for each DCS cycle when alarm generation is enabled, and the number of attach requests rejected due to packet network failure is greater than zero. The message text lists the reject counts for packet network and SGSN congestion causes. GPRS Packet Network failure counts: noPrimCtxt canNotAllocateTempCtxt genFailureFromLlc canNotAllocateHlrcCtxt assignReqFailure msResetProcFailure deactReqFailure iovReqFailure mapClientFailure UMTS Packet Network failure counts: couldNotAllocPrcdCtxt couldNotCreateMobCtxt couldNotSendAttAcc couldNotUpdMobCtxt mapError noHlrcCtxt noPrcdCtxt raiNotFound securityFailed snrReject unknownCancelType unsuppScenario unsuppUglAckError GPRS SGSN Congestion failure counts: maxSubsReached mapResourceError tlliCollision actConfirmFailure UMTS SGSN Congestion failure counts: maxSubsReached This alarm is obsoleted in G6001CF and U4002CF. Severity warning Status message
411-5221-500
Standard
04.05
January 2007
7068_1028 - Attach Reject Cause Code Reporting Alarm (GPRS/UMTS; Obsolete) 63 Nortel Networks Confidential Copyright 20042007 Nortel Networks Alarm Component Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action Verify the health of the network based on the counters listed. This alarm is informational in nature. Severity Status
SGSN5.0
7068_1029 - Sgsn-Initiated Session Deactivations Cause Code Reporting Alarm (GPRS/UMTS; Obsolete)
Alarm 7068 1029 Component Gsc/<x> Sm Usc/<x> Sm Legend <x> = component instance identifier Details This alarm is raised by the Sm component for each DCS cycle when alarm generation is enabled, and the number of SGSN-initiated session deactivations is greater than zero. The message text lists the deactivation cause counts: GPRS: gsdFailure cancelLoc duplActReq statusFromSndcp trafficVolQuery UMTS: Duplicate Activation DataPlane Error Gn Failure Detach For Reattach Abort RAU Detach Normal/Poweroff Detach RNC Error RNC Requested Failed to Start Timer SD Timer Exhausted RNC Timer Exhausted Error from SCP/SSF Mod-GGSN Msg Xmit Fail Mod-MS Msg Xmit Fail Mod-SD Msg Xmit Fail Mod-SSF Msg Xmit Fail Mod-Bad Trigger RNC Msg Xmit Failure SD Msg Xmit Failure GGSN Msg Xmit Failure MS Page Failure PDPC on SGSN, not GGSN This alarm is obsoleted in G6001CF and U4002CF. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Severity warning Status message
411-5221-500
Standard
04.05
January 2007
7068_1029 - Sgsn-Initiated Session Deactivations Cause Code Reporting Alarm (GPRS/UMTS; Obsolete) 65 Alarm Component Severity Status
Remedial action Verify the health of the network based on the counters listed. This alarm is informational in nature.
SGSN5.0
7068_1030 - Mobile-Originated SMS Overload Alarm (GPRS)

Alarm 7068 1030 Component Gsc/<x> Sms Legend <x> = component instance identifier Details This alarm is raised by the Gsc Sms component (a) if the rate of the MobileOriginated SMS (MOFSM) messages from the MS, adjusted by the SIG or SIGTRAN congestion feedback, exceeds the provisioned rate threshold, or (b) if the current MapClient buffer occupancy exceeds the provisioned (engineered) occupancy for the MOFSM message. In either of these cases, the MOFSM message is dropped, and this alarm is set. If no MOFSM message is dropped for the provisioned duration of time, this alarm is cleared. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action The SMS messaging is greater than the GSC can handle, possibly because of node outages or link failures. Verify that all Gd links and SMS-GMSC or SMSIWMS nodes are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1031 - Mobile-Terminated SMS Overload Alarm (GPRS) 67 Copyright 20042007 Nortel Networks
7068_1031 - Mobile-Terminated SMS Overload Alarm (GPRS)

Alarm 7068 1031 Component Gsc/<x> MapClient Legend <x> = component instance identifier Details This alarm is raised by the Gsc MapClient component if (a) the rate of the Mobile-Terminated SMS (MTFSM) messages from the Map/Tcap card exceeds the provisioned rate threshold or (b) if the current MapClient buffer occupancy exceeds the provisioned (engineered) occupancy for the MTFSM message. In either of these cases, the MTFSM message is dropped, and this alarm is set. If no MTFSM message is aborted due to overload situation for a provisioned duration of time, this alarm is cleared. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action The SMS messaging is greater than the GSC can handle, possibly because of node outages or link failures. Verify that all Gd links and SMS-GMSC or SMSIWMS nodes are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor/ cleared Status message
SGSN5.0
7068_1032 - HLR Reset Triggered UGL Overload Alarm (GPRS/UMTS)2

Alarm 7068 1032 Component Gsc/<x> Gmm Usc/<x> Gmm Legend <x> = component instance identifier Details This alarm is raised by the Gsc Gmm component (a) if the rate of HLR Reset triggered UGL messages, adjusted by the SIG or SIGTRAN congestion feedback, exceeds the provisioned rate threshold or (b) if the current MapClient buffer occupancy exceeds the provisioned (engineered) occupancy for the HLR Reset triggered message. In either of these cases, the HLR Reset triggered UGL message will be dropped and this alarm is set. If no HLR Reset triggered UGL message is dropped for the provisioned duration of time, this alarm is cleared. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Verify that all Gr links and the HLR are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1033 - NSVC Unavailable Alarm (GPRS) 69 Copyright 20042007 Nortel Networks
7068_1033 - NSVC Unavailable Alarm (GPRS)

Alarm 7068 1033 Component SgGtl/<x> Nse/<y> Legend <x>, <y> = component instance identifiers Details This alarm is raised to indicate that the number of unavailable Network Service Virtual Circuits (NSVCs) on a Network Service Entity (NSE) has crossed a threshold. If the number of unavailable NSVCs reaches 1% of the total, a minor alarm is raised. If the number reaches 50%, a major alarm is raised, and if the number reaches 100%, a critical alarm is raised. Which operational NSVC states are considered unavailable is provisionable via the Sgsn Gtl NsvcAlarmCondition attribute and can be any of idle, blocked and dead; the default is all three. This alarm is cleared when none of the given NSEs NSVCs are unavailable. Probable Cause underlyingResourceUnavailableCause_c (communicationsType_c in GPRS5 only) Type processingType_c (communicationSubsystemFailureCause_c in GPRS5 only) Remedial action Check the NSVCs for the NSE specified in the alarm and try to resolve any issues with those in idle, blocked or dead states. Severity minor/major/ critical Status set/clear
SGSN5.0
7068_1034 - GSC IMSI Diagnostic Alarm (GPRS/UMTS)

Alarm 7068 1034 Component Gsc/<x> Usc/<x> Legend <x> = component instance identifier Details This alarm is used to diagnose failures encountered during mobility management or session management operations. The maximum number of diagnostic alarms reported in a given time period is provisionable (Gsc/x Diag alarmMaxMessages and Gsc/x Diag alarmPeriod or Usc/x Diag alarmMaxMessages and Usc/x Diag alarmPeriod). This is 0 by default. A short list of IMSIs can be provisioned as pilot IMSIs (Gsc/x Diag pilotMobileList or Usc/x Diag pilotMobileList ). Alarms for these IMSIs will be generated without taking the provisioned alarm rate into consideration. Alarm generation can be filtered based on the type of failures- attach, activate, security and general (Gsc/x Diag alarmEvents or Usc/x Diag alarmEvents). Further filtering can also be done via two attributes: gmmCauseCodes and smCauseCodes. If a GMM or SM procedure fails, and the cause code matches a provisioned cause code, then that alarm will be displayed. These two attributes allow up to 10 cause codes to be provisioned. If the gmmCauseCodes or smCauseCodes attributes are not provisioned, then all applicable alarms will be displayed providing that the Diagnostic component attributes are set such that alarms can be displayed. Failures for pilot IMSIs will be reported regardless of the provisioning. The alarm message string will provide as much information as possible to help determine the root cause of a failure. A typical usage for this would be to cover statistically configured testheads (with known IMSIs) that periodically place calls and measure performance. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause debuggingCause_c Type debugType_c Remedial action This alarm is intended to help diagnose attach/activate related failures reported by the GSC or USC application. It may be useful to divert all alarms with this index to a single text file on the MDM server for the entire network to get a good view of specific IMSI performance on a continuous basis. See the Preside MDM Customization Administrator Guide (NTP 241-6001-303) for more information on how this can be done with MDM. Severity minor Status message
411-5221-500
Standard
04.05
January 2007
7068_1035 - BSSAP MS-Activity-Indication Overload Alarm (GPRS) 71 Copyright 20042007 Nortel Networks
7068_1035 - BSSAP MS-Activity-Indication Overload Alarm (GPRS) 2

Alarm 7068 1035 Component Gsc/<x> Bssap Legend <x> = component instance identifier Details This alarm is raised by the Gsc Bssap component when GSC application has received an HLR Reset message from a HLR, if the rate of the subsequently triggered BSSAP MS-Activity-Indication (BMAI) messages exceeds the current BMAI rate threshold (adjusted based on SIG or SIGTRAN congestion feedback), the BMAI message is dropped and this alarm is set. If no HLR Reset triggered BMAI message is dropped for the provisioned duration of time, this Set/Clear alarm is cleared. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Verify that all Gs links and MSC/VLR nodes are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor Status set/clear
SGSN5.0
7068_1036 - BSSAP Location Update Request Overload Alarm (GPRS)

Alarm 7068 1036 Component Gsc/<x> Bssap Legend <x> = component instance identifier Details This alarm is raised by the Gsc Bssap component when GSC application has received an IntraSGSN RAU (periodic or combined) request message from a mobile, if the rate of the associated Location Update request messages exceeds the current Location Update rate threshold (adjusted based on SIG or SIGTRAN congestion feedback), the Location Update request message is rejected with a congestion cause and this alarm is set. If no Location Update request is rejected due to congestion for the provisioned duration of time, this alarm is cleared. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Verify that all Gs links and MSC/VLR nodes are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed.. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1037 - Maximum Header Compression Memory Usage Alarm (GPRS) 73 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1037 - Maximum Header Compression Memory Usage Alarm (GPRS) 2

Alarm 7068 1037 Component Gsd/<x> Legend <x> = component instance identifier Details This alarm is set against the Gsd component when an attempt to allocate a TCP/ IP Header Compression object takes the memory pool usage to 100%. A clear alarm is issued when a TCP/IP Header Compression object is destroyed, provided memory pool usage is less than or equal to 90%. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Increase the provisioned value of Gsd/x Sndcp maxHeaderCompressionEntities. Severity warning Status set/clear
SGSN5.0
7068_1038 - FrameBuf Congestion Alarm (GPRS)

Alarm 7068 1038 Component Gsd/<x> Legend <x> = component instance identifier Details The GSD FrameBuf Congestion alarm is raised by the Gsd component with minor or major severity when the FrameBuf memory on the GSD application reaches a threshold level of 80% (default for minor) or 100% (default for major), respectively. If software determines, based on the number of allocation failures over time, that the Gsd is unlikely to recover from the congestion automatically, a critical alarm is raised, indicating that the card is likely to be reset within a few minutes to force recovery. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify that the PduBuffer subcomponent under the Gsd component is provisioned with the recommended (default) values. If the problem persists, contact Nortel support personnel. Severity minor/major/ critical Status message
411-5221-500
Standard
04.05
January 2007
7068_1039 - GSD Max Allocated LLC-ABM Data Entities Reached Alarm (GPRS) 75 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1039 - GSD Max Allocated LLC-ABM Data Entities Reached Alarm (GPRS)
Alarm 7068 1039 Component Gsd/<x> Legend <x> = component instance identifier Details The GSD Maximum Allocated LLC-ABM DATA Entities Reached alarm is raised by the Gsd component when the number of allocated LLC-ABM Data Entities reaches the calculated limit, which is the product of the provisionable attributes Gsd Llc abmModeLleToMobiloRatio and Gsd maxLlcActiveSubscribers under this Gsd component. No new LLC-ABM Data Entities are allocated on this GSD application until after the number of LLC-ABM Data Entities falls below the limit. The impact is that PDP sessions are not able to negotiate to a Reliability class of 1 or 2 (LLC Acknowledge mode). Mobiles attached on this GSD trying to activate a new PDP session with Reliability class 1 or 2 will get their PDP session deactivated. This alarm is cleared when the number of allocated LLC-ABM Data Entities falls below 95% of the calculated limit. Probable Cause atOrNearCapacityCause_c Type processingType_c Remedial action Verify that the values of the provisionable attributes Gsd maxLlcActiveSubscribers and Gsd Llc abmModeLleToMobioRatio under this Gsd component are sufficient to handle the level of subscriber demand required. Increase if necessary. Severity minor Status set/clear
SGSN5.0
7068_1040 - GSD Max Allocated Session Entities Reached Alarm (GPRS)

Alarm 7068 1040 Component Gsd/<x> Legend <x> = component instance identifier Details The GSD Maximum Allocated Session Entities Reached alarm is raised by the Gsd component when the number of allocated Session Entities reaches the calculated limit, which is the product of the provisionable attributes Gsd sessionsToMobileRatio and Gsd maxLlcActiveSubscribers under this Gsd component. No new Session Entities are allocated on this GSD application until after the number of Session Entities falls below the limit. The impact is that new PDP sessions are not able to activate on this GSD. This alarm is cleared when the number of allocated Session Entities falls below 95% of the calculated limit. Probable Cause atOrNearCapacityCause_c Type processingType_c Remedial action Verify that the values of the provisionable attributes Gsd maxLlcActiveSubscribers and Gsd sessionsToMobileRatio under this Gsd component are sufficient to handle the level of subscriber demand required. Increase if necessary. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1041 - Signaling BVC Reset Alarm (GPRS) 77 Copyright 20042007 Nortel Networks
7068_1041 - Signaling BVC Reset Alarm (GPRS)

Alarm 7068 1041 Component SgGtl/<x> Nse/<y> major/critical Legend <x>, <y> = component instance identifiers Details This alarm is raised as a critical message alarm if the PCUSN sends a signaling BVC reset message to the SGSN, or if the SGSN sends a signaling BVC reset message to the PCUSN. This alarm is raised as a major message alarm if the PCUSN sends a signaling BVC reset message to the SGSN but the SGSN ignores it because its mate GTLs are in the process of synchronizing BVCs. This alarm is raised as a critical SET alarm five seconds after a signaling BVC reset procedure is initiated if a PCUSN fails to create at least one point-to-point BVC on the NSE. It is cleared when at least one point-to-point BVC is created on the NSE by the PCUSN after a signaling BVC reset procedure, or when another signaling BVC reset procedure is initiated by the SGSN or PCUSN. Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action This alarm is informational in nature. No remedial action is necessary. Severity Status set/ clear/ message
SGSN5.0
7068_1043 - Max BVCs per NSE Reached Alarm (GPRS)

Alarm 7068 1043 Component SgGtl/<x> Nse/<y> Legend <x>, <y> = component instance identifiers Details This alarm displays a list of BSSGP Virtual Connections (BVCs) that failed to get created after a BVC Reset message was received from the PCUSN because the provisioned limit of BVCs per NSE had been reached. This alarm is generated every 5 minutes if there are any BVCs to be displayed. Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action This alarm is informational in nature. Severity minor Status message
411-5221-500
Standard
04.05
January 2007
7068_1044 - GbIP Data NS-VC Unavailable Alarm (GPRS) 79 Copyright 20042007 Nortel Networks
7068_1044 - GbIP Data NS-VC Unavailable Alarm (GPRS)

Alarm 7068 1044 Component SgGtl/<x> NseIp/<y> Legend <x>, <y> = component instance identifiers Details This alarm is raised to indicate that the number of unavailable data NS-VCs on an NSE has crossed a threshold. If the number of unavailable data NS-VCs reaches 1% of the total, a minor alarm is raised. If the number reaches 50%, a major alarm is raised, and if the number reaches 100%, a critical alarm is raised. The alarm is downgraded to a lower severity if the number of unavailable data NS-VCs has crossed an Abate threshold. The abate threshold from critical to major is set to 90% of unavailable data NS-VCs. The abate threshold from major to minor is set to 40%. This alarm is raised when problem occurs after the initialization successfully completes, or when the PCU tries to dynamically configure the IP endpoints while the SGSN is provisioned as static configuration. In GbIP, the operational NS-VC state becomes available when the PCU successfully acknowledges the NS-ALIVE messages from the SGSN, i.e. the Test Procedure for the NS-VC passes on the SGSN. NS-VC becomes unavailable when the PCU fails to acknowledge the NS-ALIVE messages from the SGSN and when the NS-ALIVE retries have exhausted, i.e. the Test Procedure for the NS-VC fails on the SGSN. This alarm is cleared when all data NS-VCs of the given NSE-IP are available. Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action Check the data NS-VCs for the NSE specified in the alarm and try to resolve any issues with those in unavailable states. Severity critical/ major/minor Status set/clear
SGSN5.0
7068_1045 - GbIP Signaling NS-VC Unavailable Alarm (GPRS)

Alarm 7068 1045 Component SgGtl/<x> NseIp/<y> Severity critical/ major/minor Status set/ clear/ message
Legend <x>, <y> = component instance identifiers Details This alarm is raised to indicate that the number of unavailable signaling NS-VCs on an NSE has crossed a threshold. If the number of unavailable signaling NSVCs reaches 1% of the total, a minor alarm is raised. If the number reaches 50%, a major alarm is raised, and if the number reaches 100%, a critical alarm is raised. The alarm is downgraded to a lower severity if the number of unavailable signaling NS-VCs has crossed an Abate threshold. The abate threshold from critical to major is set to 90% of unavailable signaling NS-VCs. The abate threshold from major to minor is set to 40%. This alarm is raised when problem occurs after the initialization successfully completes, or when the PCU tries to dynamically configure the IP endpoints while the SGSN is provisioned as static configuration. In GbIP, the operational NS-VC state becomes available when the PCU successfully acknowledges the NS-ALIVE messages from the SGSN, i.e. the Test Procedure for the NS-VC passes on the SGSN. NS-VC becomes unavailable when the PCU fails to acknowledge the NS-ALIVE messages from the SGSN and when the NS-ALIVE retries have exhausted, i.e. the Test Procedure for the NS-VC fails on the SGSN. This alarm is also raised as a periodic critical MSG alarm when all signaling NSVCs have failed the Test Procedure resulting in the deletion of all PCU remote endpoints at the SGSN. The PCU NSE must reconfigure itself with this SGSN NSE. This alarm is cleared when all signaling NS-VCs of the given NSE-IP are available. Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action Check the signaling NS-VCs for the NSE specified in the alarm and try to resolve any issues with those in unavailable states.
411-5221-500
Standard
04.05
January 2007
7068_1046 - GbIP Dynamic Configuration Failure Alarm (GPRS) 81 Copyright 20042007 Nortel Networks
7068_1046 - GbIP Dynamic Configuration Failure Alarm (GPRS)

Alarm 7068 1046 Component SgGtl/<x> NseIp/<y> critical Legend <x>, <y> = component instance identifiers Details This alarm is raised as a SET alarm by the SgGtl NseIp component when there are problems during one of the following SNS procedures which exchange dynamic IP configuration information between the SGSN and the PCU:
1. PCU failed to initiate or successfully complete the Size Procedure. The PCU failed to initiate or successfully complete the Size Procedure within a reasonable amount of time after SGSN startup or recovery. The SGSN raises this alarm and continues to wait for the PCU to initiate the SNS-SIZE message. 2. PCU failed to initiate or successfully complete the Configuration Procedure The PCU failed to initiate or successfully complete an SNS-CONFIG message within a reasonable amount of time after the Size Procedure successfully completes. The SGSN raises this alarm and continues to wait for the PCU to initiate the SNS-CONFIG message, or to reinitiate the Size Procedure. 3. PCU failed to successfully respond to the SGSN initiated SNSCONFIG message. The PCU failed to successfully respond to the SGSN SNS-CONFIG message after maximum retries. The maximum retry count is defined in provisioning attribute snsConfigRetries. The Configuration Procedure is aborted on the SGSN. Note: If this condition occurs and the mate ("slave") NSE is in service, then this SET alarm is not raised. Instead the mate NSE will be elected "master" and the PCU will need to reinitiate Configuration Procedures. 4. PCU failed to successfully respond to the SGSN-initiated SNS-ADD message The PCU failed to successfully respond to the SGSN SNS-ADD message after three retries at which time this alarm is raised. The SGSN continues to retry the Add Procedure until it is successful or the PCU initiates an Size Procedure against the SGSN.
Severity
Status set/ clear/ message
The NseIp component is disabled after this alarm is set.
SGSN5.0
82 SGSN Alarms Nortel Networks Confidential Alarm Component Details (Cont...) This alarm is cleared when:
1.
The NSE-IP component receives a valid SNS-SIZE message from the PCU with the ResetFlag set. 2. The NSE-IP component receives a valid SNS-ADD-ACK message from the PCU. 3. The NSE-IP component has successfully completes dynamic configuration with the PCU. 4. The NSE-IP component is reconfigured (e.g. from "dynamic" to "static" configuration) or performs a soft-reset. The NseIp component is enabled after the PCU successfully completes configuration procedures, at least one signaling and data NS-VC is available, and at least one PTP BVC is created. "When an NseIp component is unprovisioned. 3. The PCU initiated an SNS-DELETE message which flushed all remote endpoints but then failed to add new remote endpoints within a reasonable amount of time. 4. An SGSN audit detects an internal conflict between the mated NSE pair. 5. This NSE was designated 'Master' and failed to complete configuration with the PCU. Master's responsibilities have been transferred to the mate NSE.
This alarm is also raised as a MESSAGE alarm by the SgGtl NseIp component when there are temporary or transient problems during one of the following SNS procedures which exchange dynamic IP configuration information between the SGSN and the PCU. For some scenarios, the alarm is informational only and there is no service impact. For others, there is a temporary service impact and the SGSN expects the PCU to restart the dynamic IP configuration procedure(s). If those subsequent configuration procedures do not happen or do not complete as expected, this alarm is regenerated as a Set alarm as it requires operator attention. If those subsequent procedures complete successfully, there is operator action is required.
The PCU initiated an SNS-ADD message which exceeded SGSN NSE capabilities. 2. The PCU failed to successfully respond to the SNS-DELETE message initiated by this NSE after maximum retries. The SGSN initiates the SNS-DELETE message for the following two scenarios: "Change the existing local IP endpoint on the SGSN The SGSN initiates the SNS-DELETE message to inform the PCU to delete the existing SGSN IP endpoint. After the Delete Procedure, the SGSN starts the Add procedure to exchange the new SGSN local IP endpoint with the PCU. "When an NseIp component is unprovisioned. 3. The PCU initiated an SNS-DELETE message which flushed all remote endpoints but then failed to add new remote endpoints within a reasonable amount of time. 4. An SGSN audit detects an internal conflict between the mated NSE pair. 5. This NSE was designated 'Master' and failed to complete configuration with the PCU. Master's responsibilities have been transferred to the mate NSE. 1.
411-5221-500
Standard
04.05
January 2007
7068_1046 - GbIP Dynamic Configuration Failure Alarm (GPRS) 83 Copyright 20042007 Nortel Networks Severity Status
Probable Cause remoteTransmissionErrorCause_c Type communicationsType_c Remedial action Verify the health of the network path to the PCU. Verify that the PCU is functioning properly.
SGSN5.0
7068_1047 - GbIP Dynamic Configuration Attempts while using Static Configuration Alarm (GPRS)
Alarm 7068 1047 Component SgGtl/<x> Legend <x> = component instance identifiers Details This periodic message alarm is raised by the SgGtl component to indicate an NseIp has received an unexpected 'dynamic' SNS message from the PCU when it was 'statically' configured. This alarm indicates that a static / dynamic provisioning mismatch exists between the SGSN and PCU for the specified list of NseIp instances. This alarm is raised every 15 minutes only if NseIp instances encountered this problem during that interval. Probable Cause configurationErrorCause_c Type processingType_c Remedial action Verify that the PCU is using static configuration, or reconfigure the NseIp component on the SGSN to use dynamic configuration (i.e. delete all configured remote endpoints under the NseIp component). Severity critical Status message
411-5221-500
Standard
04.05
January 2007
7068_1200 - Primary CGF Link Up Alarm (GPRS; Obsolete) 85 Copyright 20042007 Nortel Networks
7068_1200 - Primary CGF Link Up Alarm (GPRS; Obsolete)

Alarm 7068 1200 Component Sas/<x> Legend <x> = component instance identifier Details
The primary CGF link up alarm is generated by the SAS when a communication is successful with the primary Charging Gateway Functionality (CGF) after the communication was previously lost. The communication link up is detected by the SAS when the primary CGF sends an echo request or a node alive message to the SGSN or when the CGF acknowledges an echo request or node alive message sent by the SGSN. All billing capability is available.
Severity warning
Status message
This alarm is obsoleted in GPRS05 and replaced with CGF Link Failure (7068 1003). Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action
No action is needed.
SGSN5.0
7068_1201 - Secondary CGF Link Up Alarm (GPRS; Obsolete)

Alarm 7068 1201 Component Sas/<x> Legend <x> = component instance identifier Details The secondary CGF link up alarm is generated by the SAS when a communication is successful with the secondary Charging Gateway Functionality (CGF) after the
communication was previously lost. The communication link up is detected by the SAS when the secondary CGF sends an echo request or a node alive message to the SGSN or when the CGF acknowledges an echo request or node alive message sent by the SGSN. All billing capability is available.
Severity major
Status message
This alarm is obsoleted in GPRS05 and replaced with CGF Link Failure (7068 1003). Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action
No action is needed.
411-5221-500
Standard
04.05
January 2007
7068_1202 - NRI Lock Constraint Alarm (GPRS) 87 Copyright 20042007 Nortel Networks
7068_1202 - NRI Lock Constraint Alarm (GPRS)

Alarm 7068 1202 Component Sgsn AccessSharing AccessArea/x Legend <x> = component instance identifier Details The "NRI Lock Constraint" message alarm is raised by an AccessArea instance when an NRI lock constraint is violated. The following constraints are enforced when locking an NRI, in order to ensure that the SGSN service is not impacted: "If nriBitLength is 6, at least 2 NRI instances need to be unlocked. "If nriBitLength is 7, at least 4 NRI instances need to be unlocked. "If nriBitLength is 8, at least 8 NRI instances need to be unlocked. "If nriBitLength is 9, at least 16NRI instances need to be unlocked. "If nriBitLength is 10, at least 32 NRI instances need to be unlocked. Probable Cause operationalConditionCause_c Type operatorType_c Remedial action
If nriBitLength is 6, then at least 2 Nri instances must be unlocked in order to avoid an SGSN service interruption. If nriBitLength is 7, then at least 4 Nri instances must be unlocked in order to avoid an SGSN service interruption. If nriBitLength is 8, then at least 8 Nri instances must be unlocked in order to avoid an SGSN service interruption. If nriBitLength is 9, then at least 16 Nri instances must be unlocked in order to avoid an SGSN service interruption. If nriBitLength is 10, then at least 32 Nri instances must be unlocked in order to avoid an SGSN service interruption.
2
Status message
Severity major
SGSN5.0
7068_1203 - All NRIs Locked Message Alarm (GPRS)

Alarm 7068 1203 Component Sgsn AccessSharing AccessArea/x Legend <x> = component instance identifier Details The "All NRIs Locked" message alarm is raised by an AccessArea instance when an operator attempts to lock all Nri instances under the concerned AccessArea instance. This alarm is raised to warn the operator that it will lead to service interruption since the SGSN no longer has an available NRI to allocate any PTMSI/TLLIs. Probable Cause operationalConditionCause_c Type operatorType_c Remedial action
At least one Nri instance must be unlocked in order to avoid service interruption. If nriBitLength is 6, then at least 2 Nri instances must be unlocked in order to avoid a service interruption. If nriBitLength is 7, then at least 4 Nri instances must be unlocked in order to avoid a service interruption. If nriBitLength is 8, then at least 8 Nri instances must be unlocked in order to avoid a service interruption. If nriBitLength is 9, then at least 16 Nri instances must be unlocked in order to avoid a service interruption. If nriBitLength is 10, then at least 32 Nri instances must be unlocked in order to avoid a service interruption.
2
Status message
Severity major
411-5221-500
Standard
04.05
January 2007
7068_1495 - MapStack Overload Alarm (GPRS; Obsolete) 89 Copyright 20042007 Nortel Networks
7068_1495 - MapStack Overload Alarm (GPRS; Obsolete)

Alarm 7068 1495 Component Tcap/<x> Legend <x> = component instance identifier Details The MapStack Overload alarm is raised by the Tcap component when the rate of messages sent by GSC application exceeds the MAP application capacity limit. Messages received from the GSC application are dropped until the message rate falls below the capacity limit. Probable Cause congestionCause_c Type communicationsType_c Remedial action No action is required for a temporary overload condition such as the possible overload triggered by a GSC application reset. If the overload condition persists, the GSC application may be under-engineered. Severity major/cleared Status message
SGSN5.0
7068_1496 - GSC/USC Overload Alarm (GPRS/UMTS; Obsolete)

Alarm 7068 1496 Component Gsc/<x> Usc/<x> Legend <x> = component instance identifier Details The GSC (USC) Overload alarm is raised by the Gsc (Usc) component when the rate of mobile Attach Requests or Inter-SGSN RAU Requests exceeds the GSC (USC) applications capacity. In order to protect the GSC (USC) from overload, Attaches/IRAUs are dropped. This alarm is obsoleted in G6001CF and U4002CF. Probable Cause congestionCause_c Type communicationsType_c Remedial action No action is required for a temporary overload condition such as the possible overload triggered by a GSC (USC) application reset. If the overload condition persists, the GSC (USC) application may be under-engineered. Severity major/cleared Status message
411-5221-500
Standard
04.05
January 2007
7068_1499 - Mismatched PTP BVC States Alarm (GPRS) 91 Copyright 20042007 Nortel Networks
7068_1499 - Mismatched PTP BVC States Alarm (GPRS)

Alarm 7068 1499 Component SgGtl/<x> Em/<y> Legend <x> = component instance identifier <y> = module name of the Em Details SgGtl/<x>: This alarm is emitted when a Signaling BVC Reset message is received by the SGSN for NSE(s) as a result of any activity affecting the NSE(s), such as PCUSN maintenance, card resets or Gb link failures. Em/<y>: The alarm is emitted for either of these conditions: 1. When a Signaling BVC Reset message is sent to the PCUSN, as a result of any activity affecting the NSE(s), such as PCUSN maintenance, card resets or Gb link failures. 2. At a fixed interval if a Status message has been sent to the PCUSN for any of the following scenarios: (a) an Unblock message is received for a PTP BVC that does not exist on the GTL card, (b) a Block message is received for a PTP BVC that does not exist on the GTL card, (c) a Flow Control message is received for a PTP BVC that does not exist on the GTL card, or (d) A mobile related traffic (like Attach Request) message is received on a PTP BVC that is in the Blocked state on the GTL card. The alarm text for the second condition indicates the affected NSEs. Some of these alarms may not be seen in cases of card congestion, as they have lower priority than NSE related messages. Probable Cause debuggingCause_c Type debugType_c Remedial action SgGtl/<x>: This alarm is informative in nature. Em/<y>: For condition 1 listed in the EM portion of the Description above, the alarm is informative in nature. For condition 2, perform an audit on the Nse component instances shown in the alarm on both the SGSN and PCUSN. Verify that PTP BVC state mismatches exist and take appropriate action on the PCUSN to unblock any PTP BVCs with mismatched states. GSM UMTS Packet Core Network Nortel SGSN Alarms Reference Manual Severity warning Status message
SGSN5.0
7068_1500 - Context Memory Exhausted Alarm (UMTS; Obsolete)

Alarm 7068 1500 Component Usc/<x> Legend <x> = component instance identifier Details When the status is set, the context memory exhausted alarm is generated by the USC caused by the Context Manager being unable to acquire any more memory from the Pool Manager. When the status is clear, sufficient memory resources have been freed, and the USC has available Pool Manager capacity. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. This alarm is obsoleted in SGSN5.0. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action When the status is set, verify the USCs provisioned attributes for the maximum number of attached subscribers and maximum number of active sessions, since the amount of memory allocated is derived from these provisioned attributes. When the status is clear, no remedial action is necessary. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1501 - GMM Max Attaches Exceeded Alarm (UMTS; Obsolete) 93 Copyright 20042007 Nortel Networks
7068_1501 - GMM Max Attaches Exceeded Alarm (UMTS; Obsolete) 2

Alarm 7068 1501 Component Usc/<x> Legend <x> = component instance identifier Details When the status is set with a severity level of minor, means that the number of attached subscribers on the USC has reached the minor water mark for USC attached subscribers. When the status is set with a severity level of major, means that the number of attached subscribers on the USC has reached the major water mark for USC attached subscribers. When the status is set with a severity level of critical, means that the number of attached subscribers on the USC has reached its limit on the number of allowable attached subscribers. In this situation future subscriber attaches are rejected. When the status is clear, a low water mark has been reached for current number of subscribers and the USC has available capacity. The default exit/entry thresholds for each level are: Minor: exit(88%) entry(90) Major: exit(93%) entry(95%) Critical: exit(98%) entry(100%) These thresholds can be changed by Nortel support personnel upon request. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. This alarm is obsoleted in SGSN5.0 and replaced with alarm 7068 1006. Probable Cause thresholdCrossedCause_c Type processingType_c Remedial action When the status is set with critical severity, verify the provisioned attribute for the maximum number of attached subscribers is sufficient to handle the level of subscriber demand and increase the maximum if necessary (assumed that increase is possible). When the status is clear, no remedial action is necessary Severity critical/ major/minor Status set/clear
SGSN5.0
7068_1502 - SM Max Active Sessions Exceeded Alarm (UMTS; Obsolete)

Alarm 7068 1502 Component Usc/<x> Legend <x> = component instance identifier Details When the status is set, the max active sessions exceeded alarm is generated by the USC caused by the Session Management (SM) function receiving a session activation request when the USC has reached its limit on the number of allowable active sessions. When the status is clear, a low water mark has been reached for current number of active sessions and the USC has available capacity. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c Type processingType_c Remedial action When the status is set, verify the provisioned attribute for the maximum number of active sessions is sufficient to handle the level of demand and increase the maximum if necessary. When the status is clear, no remedial action is necessary Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1503 - GSD or USD Out of Resources Alarm (UMTS) (GPRS: Obsolete) 95 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1503 - GSD or USD Out of Resources Alarm (UMTS) (GPRS: Obsolete)

Alarm 7068 1503 Component Gsd/<x> Usd/<x> Legend <x> = component instance identifier Details GPRS: This alarm is set when the provisioned value of maxLlcActiveSubscribers results in insufficient memory to support the requirements for mobile sessions, including SMS support; this value varies with the supported card type. The alarm is cleared when the card is reset as a result of changing the provisioned value. This alarm is obsoleted for the Gsd component in SGSN5.0 and replaced with a provisioning check. UMTS: This alarm is set by the USD application when the Context Manager is unable to acquire any more memory from the Pool Manager. When sufficient memory resources have been freed and the Pool Manager makes them available to the USD, this alarm is cleared. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action GPRS: Change the value of Gsd/ maxLlcActiveSubscribers to a lower level, based on the value of the currentAttachedSubscribers operational attribute. Note: changing this value and activating provisioning results in a reset of the card, and a corresponding loss of service. UMTS: Verify that the provisioned attribute for the maximum number of active sessions is sufficient to handle the level of demand, and increase the maximum if necessary. Severity major Status set/clear
SGSN5.0
7068_1504 - Max Active Sessions Exceeded Alarm (UMTS)

Alarm 7068 1504 Component Usd/<x> Legend <x> = component instance identifier Details When the status is set, the max active sessions exceeded alarm is generated by the USD because it received a session activation request when the USD has reached its limit on the number of allowable active sessions. When the status is clear, a low water mark has been reached for current number of active sessions and the USD has available capacity. Probable Cause atOrNearCapacityCause_c Type processingType_c Remedial action When the status is set, verify the provisioned attribute for the maximum number of active sessions is sufficient to handle the level of demand and increase the maximum if necessary. When the status is clear, no remedial action is necessary. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1505 - TcapStack Out of Subsystem Resources Alarm (GPRS/UMTS) 97 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1505 - TcapStack Out of Subsystem Resources Alarm (GPRS/ UMTS) 2

Alarm 7068 1505 Component TcapStack/<x> Legend <x> = component instance identifier Details The TcapStack Out of Subsystem Resources alarm is raised by the TcapStack component when the sum of the values of the operational attribute currentTransactionsBySubsystem for each subsystem exceeds 95% of the sum of the values of the provisionable attribute maxTransactionsBySubsystem for the MAP, MSC, and CAP subsystems under this TcapStack component. TCAP transactions for these subsystems will continue to be allowed until the number of concurrent TCAP transactions for each subsystem reaches the value of the maxTransactionsBySubsystem attribute for each subsystem. Once reached, no new TCAP transactions for that subsystem will be allowed on this TcapStack component until at least one TCAP transaction for that subsystem has been relinquished. This alarm is cleared when the sum of concurrent TCAP transactions for all subsystems falls below 90% of the sum of the values of the maxTransactionsBySubsystem attribute for each subsystem. The MapStack Out of SGSN MAP Subsystem Resources Alarm (alarm index 7068_1506), MapStack Out of SGSN MSC Subsystem Resources Alarm (alarm index 7068_1509) and TcapStack Out of SGSN CAP Subsystem Resources Alarm (alarm index 7068_1510) raise Out of Resources alarms for the individual subsystems. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c (set) outOfMemoryCause_c (clear) Type qualityOfServiceType_c (set) processingType_c (clear) Remedial action Verify that the maxTransactionsBySubsystem provisionable attribute under this TcapStack component is provisioned to an adequate size. Severity critical/minor Status set/clear
SGSN5.0
7068_1506 - MapStack Out of SGSN MAP Subsystem Resources Alarm (GPRS/UMTS)

Alarm 7068 1506 Component TcapStack/<x> MapStack Legend <x> = component instance identifier Details The MapStack Out of SGSN MAP Subsystem Resources alarm is raised by the MapStack component when the number of TCAP transactions allocated for the SGSN MAP subsystem exceeds 95% of the value of the provisionable attribute maxTransactionsBySubsystem that is under this TcapStack component. TCAP transactions for this subsystem will continue to be allowed until the number of concurrent TCAP transactions for this subsystem reaches the value of the maxTransactionsBySubsystem attribute. Once reached, no new TCAP transactions for this subsystem will be allowed on this TcapStack component until at least one TCAP transaction for this subsystem has been relinquished. This affects service on the Gr interface. Attaches and IRAUs will be impacted. This alarm is cleared when the number of concurrent TCAP transactions for this subsystem falls below 90% of the value of the maxTransactionsBySubsystem attribute. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c (set) outOfMemoryCause_c (clear) Type qualityOfServiceType_c (set) processingType_c (clear) Remedial action Verify that the maxTransactionsBySubsystem provisionable attribute under this TcapStack component is provisioned to an adequate size. If more than one MapStack component is being used, verify that MAP Clients are evenly distributed across the available MapStack applications. Some of the alarming MapStacks MAP Clients may need to be re-distributed to a different MapStack components. Severity critical/minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1507 - Initialization Failure Alarm (GPRS/UMTS; Obsolete) 99 Copyright 20042007 Nortel Networks
7068_1507 - Initialization Failure Alarm (GPRS/UMTS; Obsolete)

Alarm 7068 1507 Component Gsc/<x> Usc/<x> Legend <x> = component instance identifier Details GPRS: This alarm is set when the Sms application is unable to reserve memory for SMS Primary, Mobile-Originated, or Mobile-Terminated contexts during initialization, based on a limit of 5000. UMTS: The USC or one of its subcomponents failed to initialize or provision properly resulting in the Uscs inability to operate correctly. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. This alarm is obsolete in SGSN5.0 and replaced by alarm 7068 1018. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action GPRS: Re-provision the GSC to utilize less memory; a major contributor is the setting of maxAttachedSubscribers. UMTS: Reinitialize the Usc by resetting the card or replace the FP. Severity major Status set/clear
SGSN5.0
7068_1508 - GSD or USD Memory Initialization Alarm (GPRS/UMTS) 2

Alarm 7068 1508 Component Gsd/<x> Usd/<x> Severity Status GPRS: message UMTS: set
major
Legend <x> = component instance identifier Details GPRS: This alarm is set when memory allocations for mobile sessions, SAP, and NSAP pools fail, based on the provisioned value of maxLlcActiveSubscribers. The alarm is cleared when the card is reset as a result of changing the provisioned value. UMTS: The USD or one of its subcomponents failed to initialize or provision properly resulting in the Usds inability to operate correctly. Probable Cause GPRS: outOfMemoryCause_c UMTS: configurationErrorCause_c Type processingType_c Remedial action GPRS: Change the value of Gsd/ maxLlcActiveSubscribers to a lower level, based on the value of the currentAttachedSubscribers operational attribute. Note: changing this value and activating provisioning results in a reset of the card, and a corresponding loss of service. UMTS: Reinitialize the Usd by resetting the card or replace the FP.
411-5221-500
Standard
04.05
January 2007
7068_1509 - MapStack Out of SGSN MSC Subsystem Resources Alarm (GPRS/UMTS) 101 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1509 - MapStack Out of SGSN MSC Subsystem Resources Alarm (GPRS/UMTS)

Alarm 7068 1509 Component TcapStack/<x> MapStack Legend <x> = component instance identifier Details The MapStack Out of SGSN MSC Subsystem Resources alarm is raised by the MapStack component when the number of TCAP transactions allocated for the SGSN MSC subsystem exceeds 95% of the value of the provisionable attribute maxTransactionsBySubsystem that is under this TcapStack component. This alarm may only be raised if the provisionable attribute mscEmulationMode under the Sgsn Gsc component is set to on. TCAP transactions for this subsystem will continue to be allowed until the number of concurrent TCAP transactions for this subsystem reaches the value of the maxTransactionsBySubsystem attribute. Once reached, no new TCAP transactions for this subsystem will be allowed on this TcapStack component until at least one TCAP transaction for this subsystem has been relinquished. This affects service on the Gd interface. SMS will be impacted. This alarm is cleared when the number of concurrent TCAP transactions for this subsystem falls below 90% of the value of the maxTransactionsBySubsystem attribute. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c (set) outOfMemoryCause_c (clear) Type qualityOfServiceType_c (set) processingType_c (clear) Remedial action Verify that the maxTransactionsBySubsystem provisionable attribute under this TcapStack component is provisioned to an adequate size. Severity critical/minor Status set/clear
SGSN5.0
7068_1510 - TcapStack Out of SGSN CAP Subsystem Resources Alarm (GPRS/UMTS)

Alarm 7068 1510 Component TcapStack/<x> Legend <x> = component instance identifier Details The TcapStack Out of SGSN MSC Subsystem Resources alarm is raised by the TcapStack component when the number of TCAP transactions allocated for the SGSN CAP subsystem exceeds 95% of the value of the provisionable attribute maxTransactionsBySubsystem that is under this TcapStack component. TCAP transactions will continue to be allowed for this subsystem until the number of concurrent TCAP transactions for this subsystem reaches the value of the maxTransactionsBySubsystem attribute. Once reached, no new TCAP transactions for this subsystem will be allowed on this TcapStack component until at least one TCAP transaction for this subsystem has been relinquished. This affects service on the Ge interface. CAMEL services will be impacted. This alarm is cleared when the number of concurrent TCAP transactions for this subsystem falls below 90% of the value of the maxTransactionsBySubsystem attribute. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c (set) outOfMemoryCause_c (clear) Type qualityOfServiceType_c (set) processingType_c (clear) Remedial action Verify that the maxTransactionsBySubsystem provisionable attribute under this TcapStack component is provisioned to an adequate size. Severity critical/minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1511 - MAP Client out of Resources Alarm (GPRS/UMTS) 103 Copyright 20042007 Nortel Networks
7068_1511 - MAP Client out of Resources Alarm (GPRS/UMTS)

Alarm 7068 1511 Component Gsc/<x> MapClient Usc/<x> MapClient Legend <x> = component instance identifier Details This alarm is set when the number of map dialogues reaches the high water mark of the static maximum number of dialogues allowed. Additional map dialogues may be established until the maximum limit is reached at which time the MapClient will start failing requests from the MapClient or MapStack until inuse dialogues are relinquished. The alarm is cleared when a low water mark has been reached for in-use MAP dialogues providing an adequate pool of dialogues available for use. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c Type qualityOfServiceType_c Remedial action Verify that MapClient has enough memory allocated to handle the traffic. If it does, additional GSC (USC) MapClient components should be added to additional FP cards. Severity critical Status set/clear
SGSN5.0
7068_1512 - Max SGSN MAP Invokes Exceeded Alarm (GPRS; Obsolete)

Alarm 7068 1512 Component TcapStack/<x> MapStack Legend <x> = component instance identifier Details When the status is set, all of the provisioned MAP invokes for the SGSN subsystem are consumed and are in use. This results in the max SGSN MAP invokes exceeded alarm being generated by the MAP Stack because a MAP Client, HLR, or VLR requested a MAP dialogue but was denied. No new TCAP Invokes for SGSN MAP will be established by the MAP Stack once the maximum number of concurrent invokes is exceeded. All future attempts to send a TCAP Invokes for a SGSN MAP subsystem will fail until inuse dialogues are relinquished. When the status is clear, a low water mark has been reached for in-use TCAP Invokes for SGSN MAP, providing an adequate pool of invokes available for use. This alarm is obsoleted in GPRS5 and UMTS3. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action When the status is set, verify that the maxInvokesBySubsystem is provisioned to an adequate size. If more than one MAP Stack is being used, verify that MAP Clients are evenly distributed across the available MAP Stacks. Some of the alarming MAP Stacks MAP Clients may need to be re-distributed to a different MAP Stack. When the status is clear, no remedial action is necessary. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1513 - Max MSC MAP invokes Exceeded Alarm (GPRS; Obsolete) 105 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1513 - Max MSC MAP invokes Exceeded Alarm (GPRS; Obsolete)

Alarm 7068 1513 Component TcapStack/<x> MapStack Legend <x> = component instance identifier Details When the status is set, all of the provisioned invokes for the MSC subsystem (when the MapClient is running in MSC Emulation mode) are consumed and are in use. This results in the max MSC Map invokes exceeded alarm being generated by the MAP Stack because a TCAP invoke was required for the MSC Subsystem, but was denied. No new invokes will be established by the MAP Stack for the MSC subsystem once the maximum number of concurrent invokes is exceeded. All future attempts to establish a TCAP invoke for the MSC subsystem will fail until in-use invokes are relinquished. When the status is clear, a low water mark has been reached for in-use TCAP invokes for the MSC subsystem, providing an adequate pool of invokes available for use. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action When the status is set, verify that the maxInvokesBySubsystem for the MSC subsystem is provisioned to an adequate size. When the status is clear, no remedial action is necessary. Severity major Status set/clear
SGSN5.0
7068_1514 - Max CAP invokes Exceeded Alarm (GPRS; Obsolete)

Alarm 7068 1514 Component TcapStack/<x> Legend <x> = component instance identifier Details When the status is set, all of the provisioned TCAP invokes for use by the CAP subsystem are consumed and are in use. This results in the max CAP invokes exceeded alarm being generated by the TcapStack because a TCAP invoke was required for the CAP subsystem, but was denied. No new TCAP invokes will be established for the CAP subsystem by the TCAP Stack once the maximum number of concurrent invokes is exceeded. All future attempts to establish a TCAP invoke for the CAP subsystem will fail until in-use invokes are relinquished. When the status is clear, a low water mark has been reached for in-use TCAP invokes for the Cap Subsystem, providing an adequate pool of invokes available for use. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action When the status is set, verify that the maxInvokesBySubsystem attribute for the CAP subsystem is provisioned to an adequate value. When the status is clear, no remedial action is necessary. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1515 - SGSN MAP Subsystem Bind Failed Alarm (GPRS/UMTS) 107 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1515 - SGSN MAP Subsystem Bind Failed Alarm (GPRS/UMTS)2

Alarm 7068 1515 Component TcapStack/<x> MapStack Legend <x> = component instance identifier Details The SGSN MAP Subsystem Bind Failed alarm is raised on the MapStack component when the MapStack is unable to bind to the SGSN MAP subsystem. Once this alarm is raised, the SGSN MAP subsystem cannot be used and any MapClient trying to register with this SGSN MAP subsystem will receive registration failures. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify that the provisionable attribute maxTransactionsBySubsystem for the SGSN MAP under the TcapStack component is set to a value greater than zero. If the SGSN MAP subsystem is not needed, the alarm may be manually cleared and the MapStack will continue to work for any MapClient that registers with the SGSN MSC subsystem. If the SGSN MAP subsystem is needed, the FP this MapStack is provisioned upon should be reset. Severity minor Status set/clear
SGSN5.0
7068_1516 - SGSN MSC Subsystem Bind Failed Alarm (GPRS/UMTS)2

Alarm 7068 1516 Component TcapStack/<x> Legend <x> = component instance identifier Details The SGSN MSC Subsystem Bind Failed alarm is raised on the TcapStack component when the MapStack is unable to bind to the SGSN MSC subsystem. Once this alarm is raised, the SGSN MSC subsystem cannot be used and any MapClient trying to register with this SGSN MSC subsystem will receive registration failures. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify that the provisionable attribute maxTransactionsBySubsystem for the SGSN MSC under this TcapStack component is set to a value greater than zero. If the SGSN MSC subsystem is not needed, the alarm may be manually cleared and the MapStack will continue to work for any MapClient that registers with the SGSN MAP subsystem. If the SGSN MSC subsystem is needed, the FP this MapStack is provisioned upon should be reset. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1517 - SGSN CAP Subsystem Bind Failed Alarm (GPRS/UMTS) 109 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1517 - SGSN CAP Subsystem Bind Failed Alarm (GPRS/UMTS)2

Alarm 7068 1517 Component TcapStack/<x> Legend <x> = component instance identifier Details The SGSN CAP Subsystem Bind Failed alarm is raised on this TcapStack component when the MapStack is unable to bind to the SGSN CAP subsystem. Once this alarm is raised, the SGSN CAP subsystem cannot be used and any Service Switching Function (SSF) trying to register with this SGSN CAP subsystem will receive registration failures. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause outOfMemoryCause_c Type processingType_c Remedial action Verify that the provisionable attribute maxTransactionsBySubsystem for the SGSN CAP under the TcapStack component is set to a value greater than zero. If the SGSN CAP subsystem is not needed, the alarm may be manually cleared and the MapStack will continue to work for any MapClient that registers with the SGSN MAP subsystem or the SGSN CAP subsystem. If the SGSN CAP subsystem is needed, the FP this MapStack is provisioned upon should be reset. Severity minor Status set/clear
SGSN5.0
7068_1518 - SSF SCP Communication Failure Alarm (GPRS/UMTS) 2

Alarm 7068 1518 Component Gsc/<x> Ssf Usc/<x> Ssf Legend <x> = component instance identifier Details The SSF SCP Communication Failure alarm is raised by the Gsc Ssf (Usc Ssf) component when the Service Switching Function (SSF) process is no longer able to communicate with the Service Control Point (SCP). The communication failure is detected by the Ssf component when a Camel Application Part (CAP) dialogue with the SCP times out during each of the provisioned retries. If this communication link is lost, it may indicate a temporary or permanent link failure between the SGSN and the SCP or indicate that the SCP is down. This alarm is not present in GPRS05 Maintenance or UMTS3.0.1 Maintenance. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause localTransmissionErrorCause_c Type communicationsType_c Remedial action Verify the health of the network path to the SCP. Verify the SCP is functioning properly. Severity major Status message
411-5221-500
Standard
04.05
January 2007
7068_1519 - SSF Max Camel Dialogues Exceeded Alarm (GPRS/UMTS) 111 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1519 - SSF Max Camel Dialogues Exceeded Alarm (GPRS/ UMTS)

Alarm 7068 1519 Component Gsc/<x> Ssf Usc/<x> Ssf Legend <x> = component instance identifier Details The SSF Max Camel Dialogues Exceeded alarm is raised by the Ssf component when an SCP requests a camel dialogue and all of the provisioned camel dialogues are consumed and are in use. Once the maximum number of concurrent dialogues is reached, no new camel dialogues will be established by this Service Switching Function (SSF) application. All future attempts to establish a camel dialogue will fail until at least one in-use camel dialogue is relinquished. The alarm is cleared when the number of camel dialogues in-use falls below a low water mark. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c (set) localTransmissionErrorCause_c (clear) Type qualityOfServiceType_c (set) communicationsType_c (clear) Remedial action Verify that the maxCamelDialogues provisionable attribute under the SSF component is provisioned to an adequate size. If more than one GSC (USC) application is being used, verify that the SCPs are evenly distributed across the available GSC (USC) applications. Severity major Status set/clear
SGSN5.0
7068_1520 - MAP Notice Indication Display Alarm (GPRS/UMTS; Obsolete)

Alarm 7068 1520 Component TcapStack/<x> Severity GPRS: minor UMTS: minor/ cleared Legend <x> = component instance identifier Details The MAP Notice Indication Display alarm is raised to display the following MAP message counters destined for the SS7 Network Entity: AFR-- noTranslationSpecific, otherReturnCause ISD -- noTranslationSpecific, otherReturnCause MOFSM -- noTranslationSpecific, otherReturnCause MTFSM -- noTranslationSpecific, otherReturnCause RFSM -- noTranslationSpecific, otherReturnCause SAI -- noTranslationSpecific, otherReturnCause UGL -- noTranslationSpecific, otherReturnCause This alarm is displayed every 60 minutes. There are two counter values displayed for each MAP message. The noTranslationSpecific counter displays how many times an SCCP Notice Indication with Return Cause = No Translation Specific is received, and the otherReturnCause displays the number of times any other SCCP Notice Indication Return Cause value is received for a particular message. Once the alarm has been raised, the counters for these values are reset to zero. This alarm is obsoleted in G6001CF and U4002CF. Probable Cause debuggingCause_c Type debugType_c Remedial action When any of the message counter values are not equal to zero, this means that there was a failure to route the message destined for the SS7 Network Entity. Verify that all of the routing tables are provisioned correctly on both the SIG and the SS7 Network Entity, and ensure that an active connection exists between the SIG and the SS7 Network Entity. If the message counter values are equal to zero, no remedial action is necessary. message Status
411-5221-500
Standard
04.05
January 2007
7068_1521 - GSC or USC CPU Overload Alarm (GPRS/UMTS) 113 Copyright 20042007 Nortel Networks
7068_1521 - GSC or USC CPU Overload Alarm (GPRS/UMTS)

Alarm 7068 1521 Component Gsc/<x> Usc/<x> Legend <x> = component instance identifier Details This alarm is raised by the Gsc or Usc component when the CPU usage exceeds the preset percentages. The alarm severity is increased as the CPU usage exceeds the following thresholds: Minor - 96% CPU usage. Major - 98% CPU usage. Critical - 100% CPU usage. The alarm severity is reduced as the CPU usage falls below the following thresholds: Major - 99% CPU usage. Minor - 97% CPU usage. Cleared- 95% CPU usage. Note: this alarm is permanently disabled in GPRS6, but is enabled in UMTS4 and SGSN5.0 onwards. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause thresholdCrossedCause_c Type processingType_c Remedial action Verify that there are enough GSC or USC applications running on enough FP cards to satisfy the level of subscriber activity. Severity critical/ major/minor Status set/clear
SGSN5.0
7068_1522 - Loss of Communication with the DnsAgent Servers Alarm (GPRS/UMTS; Obsolete)
Alarm 7068 1522 Component DnsAg/<x>,<y> Legend <x> = instance identifier of the VR <y> = instance identifier of the dnsAgent Details The Loss of Communication with the DnsAgent Servers alarm is raised by the DnsAg component when DNS Agent application can not communicate with any Name Server. The following are possible causes of this condition: ICMP network errors: Bad Net Host is unreachable Protocol error Port is unreachable Fragmentation is needed Source Failed IP Server is unavailable Name Server failure If the DNS Agent does not support static query, the severity is set to Critical, otherwise, the severity is set to Major. Note: The alarm will only change status when the DNSAgent queries the server. Note: This alarm is obsoleted in G6001CF and U4002CF, and is replaced with 7068_1578. Probable Cause lossOfSignalCause_c Type communicationsType_c Remedial action Verify the IP Server, Network and Name Server availability. Severity critical/major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1523 - Loss of Connection with the SIG or SIGTRAN Alarm (GPRS/UMTS) 115 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1523 - Loss of Connection with the SIG or SIGTRAN Alarm (GPRS/UMTS)

Alarm 7068 1523 Component Tcap/<x> Ss7ipif/<y> Gsc/<m> Bssap Ss7ipif/<n> Severity critical Status set/clear
Legend <x>, <y>, <m>, <n> = component instance identifiers Details The Loss of Connection with the SIG or SIGTRAN alarm is raised by the Ss7IpIf component when the SGSN loses the TCP connection with the SIG node or SIGTRAN application. The alarm is cleared when the TCP connection between Ss7IpIf component and the SIG or SIGTRAN is restored. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause lossOfSignalCause_c Type communicationsType_c Remedial action Verify the connection of the GSC appplication or TCAP application with SIG or SIGTRAN.
SGSN5.0
7068_1524 - LIAF out of Resources Alarm (GPRS/UMTS)

Alarm 7068 1524 Component Liaf/<x> Legend <x> = component instance identifier Details The LIAF out of Resources alarm is raised by the Liaf component when it fails to initialize because it is unable to acquire memory resources. The alarm is cleared when the card is reset. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause outOfMemeoryCause_c Type processingType_c Remedial action Verify that the components that share this FP card with the Liaf component are provisioned within their engineering limits, and then reset the card. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1525 - LIAF Maximum Subscribers Reached Alarm (GPRS/UMTS) 117 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1525 - LIAF Maximum Subscribers Reached Alarm (GPRS/ UMTS)

Alarm 7068 1525 Component Liaf/<x> Legend <x> = component instance identifier Details The LIAF Maximum Subscribers Reached alarm is raised by the Liaf component when the number of subscribers to intercept reaches the limit specified by the provisionable attribute nsInterceptions under the Liaf component. The alarm is cleared when the number of subscribers to intercept falls below the limit. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c Type qualityOfServiceType_c Remedial action Verify the provisionable attribute nsInterceptions is sufficient to handle the level of subscriber interception demands and increase the maximum if necessary. Severity major Status set/clear
SGSN5.0
7068_1526 - LIAF Initialization Failure Alarm (GPRS/UMTS)

Alarm 7068 1526 Component Liaf/<x> Legend <x> = component instance identifier Details The LIAF Initialization Failure alarm is raised by the Liaf component when the Liaf application fails to initialize properly. The alarm is cleared when the card is reset. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause configurationErrorCause_c Type ProcessingType_c Remedial action Verify that the components that share this FP card with the Liaf component are provisioned within their engineering limits, and then reset the card. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1527 - Loss of Communication with LIG ADMF Alarm (GPRS/UMTS) 119 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1527 - Loss of Communication with LIG ADMF Alarm (GPRS/ UMTS) 2

Alarm 7068 1527 Component Liaf/<x> Legend <x> = component instance identifier Details The Loss of Communication with LIG ADMF alarm is raised by the Liaf component when its TCP connection is lost, and it can not communicate with the provisioned Lawful Intercept Gateway (LIG) Administrative Function (ADMF) network device. This results in the loss of a targets interception provisioning information being retrieved from the LIG ADMF. The alarm is cleared when the TCP connection is restored. If this communication link is lost, it could mean a temporary or permanent link failure between the SGSN and LIGA or indicate that the LIGA is down. If the communication loss is due to a permanent failure of the link (e.g., Ethernet cable cut or disconnected) then it may take up to 18 minutes to generate the alarm from the time of the failure. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause lossOfSignalCause_c Type communicationsType_c Remedial action Verify that the IP address and IP port number specified by the provisionable attributes admfAddr and admfPortIP respectively under this Liaf component are set correctly. Verify the supporting networks physical connection, and the availability of the LIG ADMF network device. Severity major Status set/clear
SGSN5.0
7068_1528 - Loss of Communication with LIG DF Server Alarm (GPRS/UMTS)

Alarm 7068 1528 Component Liaf/<x> Legend <x> = component instance identifier Details The Loss of Communication with the LIG DF alarm is raised by the LIAF component when the Lawful Intercept Access Function (LIAF) process can not communicate with the Lawful Intercept Gateway (LIG) Delivery Function (DF) network device. The LIAF process delivers intercepted data to a LIG DF network device. There may be multiple, simultaneous LIG DF connections and an alarm is generated for each connection failure. This connection failure results in the loss of intercepted target data destined for the LIG DF. If this communication link is lost, it could mean a temporary or permanent link failure between the SGSN and LIGA or indicate that the LIGA is down. If the communication loss is due to a permanent failure of the link (e.g., Ethernet cable cut or disconnected) then it may take up to 18 minutes to generate the alarm from the time of the failure. If this communication link is lost, it could mean a temporary or permanent link failure between the SGSN and LIGD or indicate that the LIGD is down. If the communication loss is due to a permanent failure of the link (e.g., Ethernet cable cut or disconnected) then it may take up to 18 minutes to generate the alarm from the time of the failure. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause lossOfSignalCause_c Type communicationsType_c Remedial action Verify the IP Server, the supporting networks physical connection and the LIG DF network device are functioning properly. Severity major Status message
411-5221-500
Standard
04.05
January 2007
7068_1529 - Invalid PDP Context Received Alarm (GPRS/UMTS) 121 Copyright 20042007 Nortel Networks
7068_1529 - Invalid PDP Context Received Alarm (GPRS/UMTS)

Alarm 7068 1529 Component Gsc/<x> MapClient Usc/<x> MapClient Legend <x> = component instance identifier Details This alarm is raised by the MapClient component when the MapClient process attempts to insert a PDP context into the HLR cache that contains invalid data. Possible causes are invalid QoS, invalid ETSI PDP type, invalid IETF PDP type, or no PDP contexts in the HLR cache. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause operationalConditionCause_c Type operatorType_c Remedial action Verify the PDP context provisioning in the HLR for the indicated subscriber. Severity warning Status message
SGSN5.0
7068_1530 - Loss of Redundancy with the DnsAgent Servers Alarm (GPRS/UMTS; Obsolete) 2
Alarm 7068 1530 Component DnsAg/<x>,<y> Legend <x> = instance identifier of the VR <y> = instance identifier of the dnsAgent Details The Loss of Redundancy with the DnsAgent Servers alarm is raised by the DnsAg component when there is more than one Name Server provisioned and the DNS Agent application can only communicate with one of the Name Servers. The following are possible causes of this condition: ICMP network errors: Bad Net Host is unreachable Protocol error Port is unreachable Fragmentation is needed Source Failed IP Server is unavailable Name Server failure The alarm is cleared when the DNS Agent application is able to communicate with all of the provisioned Name Servers. Note: The alarm will only change status when the DNSAgent queries the server. Note: This alarm is obsoleted in G6001CF and U4002CF, and is replaced with 7068_1578. Probable Cause lossOfSignalCause_c Type communicationsType_c Remedial action Verify the IP Server, Networks or Servers availability. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1531 - Attach Requests Rejected or not Received Alarm (GPRS/UMTS; Obsolete) 123 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1531 - Attach Requests Rejected or not Received Alarm (GPRS/ UMTS; Obsolete) 2
Alarm 7068 1531 Component Gsc/<x> Gmm Usc/<x> Gmm Legend <x> = component instance identifier Details This alarm is raised by the Gmm component at the end of the collection interval when the number of Attach Request rejections exceeds the thresholds mentioned below or when the total number of Attach Request messages received is zero. The successful attaches percentage is recalculated each collection period. A Major alarm is raised when the number of Attach Request rejections reaches 10% or more of the total number of Attach Request messages received. A Minor alarm is raised when the number of Attach Request rejections reaches 5% or more of the total number of Attach Request messages received. A Critical alarm is raised when the number of Attach Request messages received is zero. The successful attaches percentage is calculated using the following formula: % Successful Attaches = (attachesSuccessful / (attachesSuccessful + attachRejPacketNetworkFailure + attachRejSgsnCongestion)) * 100 These values correspond to the indicated collected statistics for the DCS interval just concluded. The alarm is cleared when the number of Attach Request rejections is below 5% of the total number of Attach Request and the total number of Attach Request messages received is greater than zero. This alarm is set/clear for umts3, and message only for gprs5. It is obsoleted in gprs6 and umts4, and replaced with alarm 1574. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action Examine the GMM attach failure counters (for GPRS05 (UMTS03) and later, include the counters reported in alarm 70681028). Verify the health of the network. Severity critical/ major/minor/ cleared Status message /set/ clear
SGSN5.0
Alarm 7068 1532 Component Gsc/<x> Sm Usc/<x> Sm Legend <x> = component instance identifier Details This alarm is raised by the Sm component at the end of the collection interval when the number of PDP Activation rejections exceeds the thresholds mentioned below or when the total number of PDP Activation Request messages received is zero. The success activation percentage is recalculated each collection period. A Major alarm is raised when the number of PDP Activation rejections reaches 10% (default) or more of the total number of PDP Activation request messages received. A Minor alarm is raised when the number of PDP Activation rejections reaches 5% (default) or more of the total number of PDP Activation request messages received. If enabled (default), a Critical alarm is raised when the total number of PDP Activation Request messages received during 2 (default) collection intervals is zero. The successful activation percentage is calculated using the following formula: % Successful Activations = (mobileinitActivations / totalDataSessionActivations) * 100 and totalDataSessionActivations = mobileInitActivations + insufficientResources + missingOrUnknownApn + unknownPdpAddrOrPdpType + userAuthenticationsFailed + activationRejectedByGgsn + activationRejectedUnspecified + serviceOptionTempOutOfOrder + nsapiAlreadyUsed + semanticallyIncorrectMessage + invalidMandatoryInfoElement + msgTypeNotCompWithProtState + protocolErrorUnspecified The alarm is cleared when the number of PDP Activation rejections is below 5% (default) of the total number of PDP Activation requests and the total number of PDP Activation Request messages is greater than zero. This alarm is message only for umts3 and gprs5. It is obsoleted in gprs6 and umts4, and replaced with alarm 1575. Probable Cause thresholdCrossedCause_c Severity critical/ major/minor/ cleared Status message
411-5221-500
Standard
04.05
January 2007
7068_1532 - PDP Activations Requests Rejected or not Received Alarm (GPRS/UMTS; Obsolete) 125 Nortel Networks Confidential Copyright 20042007 Nortel Networks Alarm Component Type qualityOfServiceType_c Remedial action Examine the SM activation failure counters. Verify the health of the network. Severity Status
SGSN5.0
7068_1533 - SS7 SIG Problem Alarm (GPRS/UMTS; Obsolete)

Alarm 7068 1533 Component TcapStack/<x> Ss7IpIf/<y> Legend <x>, <y> = component instance identifiers Details The SS7 SIG Problem alarm is raised by the Ss7IpIf component when the total number of SCCP Notice Indication messages received from the SIG exceeds the predetermined threshold during the predetermined minimum reporting interval. This alarm is raised to report that a problem with the SIG occured in its SS7 layer. Separate counters for the SCCP Return Causes are displayed in this alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Check the condition of the SIG to which the TCAP application or the GSC (USC) application uses for SS7 services. Causes of networkCongestion and networkFailure codes may indicate SS7 link congestion due to insufficient SS7 links in high traffic situations. Severity warning Status message
411-5221-500
Standard
04.05
January 2007
7068_1534 - SCCP Notice Indication Throttling Alarm (GPRS/UMTS; Obsolete) 127 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1534 - SCCP Notice Indication Throttling Alarm (GPRS/UMTS; Obsolete) 2

Alarm 7068 1534 Component TcapStack/<x> Ss7IpIf/<y> Legend <x>, <y> = component instance identifiers Details The SCCP Notice Indication Throttling alarm is raised when, during one second, the total number of SCCP Notice Indications received from the SIG with SCCP Return Cause codes of networkCongestion or networkFailure exceeds the predetermined threshold. When this threshold is exceeded, any new SCCP Notice Indications received from the SIG will be dropped until the alarm is cleared. This alarm is cleared when, during one second, the total number of SCCP Notice Indications received from the SIG with SCCP Return Cause codes of networkCongestion or networkFailure falls below the predetermined threshold. This alarm is obsoleted in G6001CF and U4002CF. Probable Cause congestionCause_c Type communicationsType_c Remedial action Check the status of the links on the SIG which provides SS7 services to the TCAP application. Severity major/cleared Status message
SGSN5.0
7068_1535 - HLR Reset Received Alarm (GPRS/UMTS)

Alarm 7068 1535 Component Gsc/<x> HlrC Usc/<x> HlrC Legend <x> = component instance identifier Details The HLR Reset Received alarm is raised by the HlrC component when a MAP Reset message is received from the HLR. The alarm will display the E.164 HLR address and the number of subscribers stored in HlrC that are associated with this HLR. The HLR sends a Reset message to the SGSN when the HLR experiences a failure. The SGSN, in response to the Reset message, requests subscription information from the HLR for all subscribers attached on the SGSN in order to restore the subscribers. This process may impact the GSC's or USCs utilization and performance. The level of impact varies with the number of subscribers to be restored and GSC or USC utilization prior to receiving the Reset request. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause equipmentFailureCause_c Type equipmentType_c Remedial action Verify that the HLR is functioning properly. Severity warning Status message
411-5221-500
Standard
04.05
January 2007
7068_1536 - TCAP Mobile-Terminated FSM Overload Alarm (GPRS; Obsolete) 129 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1536 - TCAP Mobile-Terminated FSM Overload Alarm (GPRS; Obsolete) 2

Alarm 7068 1536 Component Tcap/<x> MapStack Legend <x> = component instance identifier Details This alarm is raised by the MAP component (a) if the rate of the MTFSM messages received from the SIG exceeds the provisioned rate threshold, or (b) if the currently available MAP transaction buffers in the MAP/TCAP card are below the provisioned buffer threshold, the MTFSM message will be dropped and this alarm is set. If no MTFSM message is dropped due to overload situation for a provisioned duration of time, this alarm is cleared. Probable Cause congestionCause_c Type communicationsType_c Remedial action Check the condition of the SIG which the TCAP application uses for MAP services. Severity major/cleared Status message
SGSN5.0
7068_1537 - Registration with IP Server Failure Alarm (GPRS/UMTS)2

Alarm 7068 1537 Component Gsc/<x> GtpM Usc/<x> GtpC Sas/<x> SgGtl/<x> Legend <x> = component instance identifier Details This alarm is set against the appropriate component (GtpC, GtpM, Sas or SgGtl) when three attempts to register that component with the IP Server fail. The alarm is cleared when the component successfully registers with the IP Server. When this alarm is raised against Sas due to a response or event message from the IP server, the information received is displayed so that any provisioning issues can be highlighted and corrected to re-establish communication. When this alarm is raised against SgGtl, it indicates that the SgGtl receives an error indication message from the IP server when the SgGtl tries to register with it. When this alarm is raised against SgGtl, GbIP functionality is disabled and all NseIp components go disabled. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause GtpC: underlyingResourceUnavailableCause_c Sas: configurationErrorCause_c SgGtl: underlyingResourceUnavailableCause_c Type processingType_c Remedial action GtpC: Verify the IP Server is functioning properly. Sas: Check CGF connectivity and verify the IP Server is functioning properly. SgGtl: Verify the IP Server is functioning properly. Severity Status
critical
set/clear
411-5221-500
Standard
04.05
January 2007
7068_1538 - GTP Path High Usage Alarm (GPRS/UMTS) 131 Copyright 20042007 Nortel Networks
7068_1538 - GTP Path High Usage Alarm (GPRS/UMTS)

Alarm 7068 1538 Component Gsc/<x> GtpM Usc/<x> GtpC Legend <x> = component instance identifier Details This alarm is set against the GtpC component when the number of GTP Paths exceeds the trigger threshold, which is defined as a percentage (90% default) of the provisioned maximum number of GTP Paths. This alarm is cleared when the number of GTP Paths falls below the clearing threshold, which is also defined as a percentage (80% default) of the provisioned maximum number of GTP Paths. Note: The thresholds described above are effectively lowered due to truncation if the percentage of the maximum number of GTP paths is not an integer. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c Type qualityOfServiceType_c Remedial action Monitor the situation. If the condition persists, the GSC or USC application may be under-engineered. Severity minor Status set/clear
SGSN5.0
7068_1539 - GTP Transaction High Usage Alarm (GPRS/UMTS)

Alarm 7068 1539 Component Gsc/<x> GtpM Usc/<x> GtpC Legend <x> = component instance identifier Details This alarm is set against the GtpC component when: a) the number of outstanding GTP transactions exceeds the overall trigger threshold, which is defined as a percentage of the provisioned maximum number of simultaneous GTP transactions (90% default), or b) the number of outstanding GTP transactions per path exceeds the per path trigger threshold, which is defined as a percentage of the transaction limit on a per path basis (90% default). The transaction limit per path is defined as a percentage of the provisioned maximum number of simultaneous GTP transactions (50% default). This alarm is cleared when the number of outstanding GTP transactions falls below the appropriate clearing threshold, which is defined for case (a) as 85% (default) of the provisioned maximum number of simultaneous GTP transactions and for case (b) as 85% (default) of the transaction limit on a per path basis. Note: The thresholds described above are effectively lowered due to truncation if the percentage of the maximum number of GTP transactions is not an integer. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c Type qualityOfServiceType_c Remedial action Monitor the situation. If the condition persists, the GSC or USC application may be under-engineered. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1540 - GTP Path Failure Alarm (GPRS/UMTS) 133 Copyright 20042007 Nortel Networks
7068_1540 - GTP Path Failure Alarm (GPRS/UMTS)

Alarm 7068 1540 Component Gsc/<x> GtpM Path/<y> Usc/<x> GtpC Path/<y> Legend <x> = component instance identifier <y> = IP address Details This alarm is raised by the Gsc (Usc) component to declare a path failure to an IP address of a GSN. The declaration of the path failure will occur shortly after its detection (as defined in the 3GPP 29.060 spec), in case the other GSN is having a very short period of congestion. This alarm is raised with minor severity when at least one GTP path has declared failure. It is cleared when all of the failed GTP paths have recovered or are deleted. If this alarm is SET on the active card and a switchover occurs, then the newly active card will check the paths for failures so that the alarm can be re-issued on the active card. If echo requests are enabled (via Sgsn Gsc EchoRequest or Usgsn Usc EchoRequest), then the GTP paths are checked immediately upon switchover. If echo requests are disabled, then GTP paths are only checked when new activation requests are processed. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause remoteTransmissionErrorCause_c Type communicationsType_c Remedial action Verify the health of the GSN with the reported IP address. Verify the health of the network. Severity minor Status set/clear
SGSN5.0
7068_1544 - Attach Overload Alarm (GPRS/UMTS)

Alarm 7068 1544 Component Gsc/<x> Gmm Usc/<x> Gmm Legend <x> = component instance identifier Details This alarm is raised by the Gmm component (a) if the rate of the received Attach (normal or combined) request messages from a mobile exceeds the current attach rate threshold (adjusted based on SIG or SIGTRAN congestion feedback) or (b) if the current MapClient buffer occupancy exceeds the provisioned (engineered) occupancy for the Attach request message. In either of these cases, the Attach request message is dropped and this alarm is set. If no Attach request message is dropped for the provisioned duration of time, this alarm is cleared. This alarm is generated as a Msg alarm when current allowable rate for Attach request messages has been adjusted based on SIG or SIGTRAN congestion feedback. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Since this overload condition can be impacted by the SIG node or SIGTRAN application, verify the SIG nodes or SIGTRAN applications are functioning properly. Also verify the Gr and Gs links are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor Status set/ clear/ msg
411-5221-500
Standard
04.05
January 2007
7068_1545 - InterSGSN RAU Overload Alarm (GPRS/UMTS) 135 Copyright 20042007 Nortel Networks
7068_1545 - InterSGSN RAU Overload Alarm (GPRS/UMTS)

Alarm 7068 1545 Component Gsc/<x> Gmm Usc/<x> Gmm Legend <x> = component instance identifier Details This alarm is raised by the Gmm component (a) if the rate of the received InterSGSN RAU (normal or combined) request messages from a mobile exceeds the current InterSGSN RAU rate threshold (adjusted based on SIG or SIGTRAN congestion feedback) or (b) if the current MapClient buffer occupancy exceeds the provisioned (engineered) occupancy for the InterSGSN RAU request message. In either of these cases, the InterSGSN RAU request message is dropped and this alarm is set. If no InterSGSN RAU request is dropped for the provisioned duration of time, this alarm is cleared. This alarm is generated as a Msg alarm when current allowable rate for InterSGSN RAU request messages has been adjusted based on SIG or SIGTRAN congestion feedback. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Since this overload condition can be impacted by the SIG node or SIGTRAN application, verify the SIG nodes or SIGTRAN applications are functioning properly. Also verify the Gr and Gs links are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor Status set/ clear/ msg
SGSN5.0
7068_1546 - Mobile-Terminated SMS TCAP Overload Alarm (GPRS) 2

Alarm 7068 1546 Component Tcap/<x> Legend <x> = component instance identifier Details This alarm is raised by the Tcap component if (a) the rate of the MobileTerminated SMS TCAP (MTFSM) messages from the SIG or SIGTRAN exceeds the provisioned MTFMS rate threshold or (b) if the current TCAP buffer occupancy for the SGSN and MSC subsystems exceeds the provisioned (engineered) occupancy for the MTFSM message. In either of these cases, the MTFSM message is dropped and this alarm is set. If no MTFSM message is dropped due to overload situation for a provisioned duration of time, this alarm is cleared. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Since this overload condition can be impacted by the SIG node or SIGTRAN application, verify the SIG nodes or SIGTRAN applications are functioning properly. Also verify the Gd links and the SMS-GMSC and SMS-IWMSC nodes are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1547 - SAI Overload Alarm (GPRS/UMTS) 137 Copyright 20042007 Nortel Networks
7068_1547 - SAI Overload Alarm (GPRS/UMTS)

Alarm 7068 1547 Component Tcap/<x> Legend <x> = component instance identifier Details This alarm is raised by the Tcap component (a) if the rate of the received SAI messages from each of the GSC applications exceeds the provisioned SAI rate threshold or (b) if the current MapStack buffer occupancy exceeds the provisioned (engineered) occupancy for the SAI message. In either of these cases, the SAI message is dropped and this alarm is set. If no SAI message is dropped due to overload situation for a provisioned duration of time, this alarm is cleared. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Since this overload condition can be impacted by the SIG node or SIGTRAN application, verify the SIG nodes or SIGTRAN applications are functioning properly. Also verify the Gr links and the HLR nodes are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor Status set/clear
SGSN5.0
7068_1548 - Non-SAI Overload Alarm (GPRS/UMTS)

Alarm 7068 1548 Component Tcap/<x> Legend <x> = component instance identifier Details This alarm is raised by the Tcap component if the rate of the received non-SAI messages from each of the GSC applications exceeds the provisioned non-SAI rate threshold, the non-SAI message is dropped and this alarm is set. If no nonSAI message is dropped due to overload situation for a provisioned duration of time, this alarm is cleared. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Since this overload condition can be impacted by the SIG node or SIGTRAN application, verify the SIG nodes or SIGTRAN applications are functioning properly. Also verify the Gr, Gd, Gs, and Ge links and associated nodes are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1549 - SSF InitialDPGPRS Overload Alarm (GPRS/UMTS) 139 Copyright 20042007 Nortel Networks
7068_1549 - SSF InitialDPGPRS Overload Alarm (GPRS/UMTS)

Alarm 7068 1549 Component Gsc/<x> Ssf Usc/<x> Ssf Legend <x> = component instance identifier Details This alarm is raised by the Ssf component if the rate of the received CAMEL PDP-Establish (CPE) or CAMEL PDP-ChangeOfPosition Context (CPCOPC) request messages from a mobile exceeds the current InitialDPGPRS rate threshold (adjusted based on SIG or SIGTRAN congestion feedback), the CPE/ CPCOPC request message receives default handling treatment and this alarm is set. If no CPE/CPCOPC request is received overload treatment for the provisioned duration of time, this alarm is cleared. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause congestionCause_c Type communicationsType_c Remedial action Since this overload condition can be impacted by the SIG node or SIGTRAN application, verify the SIG nodes or SIGTRAN applications are functioning properly. Also verify the Ge links and CAMEL GSM-SCF nodes are functioning properly. If the overload condition is unexpected, contact Nortel support personnel. Otherwise no further action is needed. Severity minor Status set/clear
SGSN5.0
7068_1550 - MAP Client Registration Failure Alarm (GPRS/UMTS)

Alarm 7068 1550 Component Gsc/<x> MapClient Usc/<x> MapClient Legend <x> = component instance identifier Details The MAP Client registration failure alarm is raised by the MapClient component when it cannot register with MapStack. The alarm is raised when the registration timer pops or when a failed registration acknowledgement message is received from MapStack. The alarm is cleared when a successful registration acknowledgement message is received from MapStack. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause commSubsystemFailureCause_c Type communicationsType_c Remedial action Registration failures occur because of setup problems on the SGSN or the SIG. Configuration must be checked on the SGSN and the SIG. Severity critical Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1551 - Ss7IpIf Reg Failure alarm (GPRS/UMTS) 141 Copyright 20042007 Nortel Networks
7068_1551 - Ss7IpIf Reg Failure alarm (GPRS/UMTS)

Alarm 7068 1551 Component Tcap/<x> Ss7ipif/<y> Gsc/<m> Bssap Ss7ipif/<n> Severity minor Status set/clear
Legend <x>, <y>, <n>, <m> = component instance identifiers Details The Registration Failure alarm is raised by Ss7IpIf component when the registration Timer pops or when a failed registration acknowledgement message is received for all SCIP clients of any subsystem. The alarm is cleared when a successful registration acknowledgement message is received for all the SCIP clients of the subsystem. Note: To identify which SCIP client is failing the registration, check the debug trace logs on the HP-SIG, or check the client statistics under the SigtranAsp Siwf Client component. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause commSubsystemFailureCause_c Type communicationsType_c Remedial action Registration failures occur because of setup problems on the SGSN/ASP or the HP-SIG. Configuration must be checked on the SGSN/ASP (the Sgsn SigtranAsp and SigtranAsp component hierarchies) and the HP-SIG.
SGSN5.0
7068_1552 - Ss7IpIf Ni Failure alarm (GPRS/UMTS)

Alarm 7068 1552 Component Tcap/<x> Ss7ipif/<y> Gsc/<m> Bssap Ss7ipif/<n> Severity minor Status set/clear
Legend <x>, <y>, <m>, <n> = component instance identifiers Details The Notice Indication Failure alarm is raised by Ss7IpIf component when the rate of Notice Indication messages with a cause of Network Failure for a subsystem has reached the rate of which the traffic is re-routed to a different HPSIG or SigtranAsp. This can be caused due to a SS7 link being down on the HP-SIG, or due to an SCTP association being down on a SigranAsp. The alarm is cleared when traffic for all subsystems is re-routed to the original HP-SIG or SigtranAsp. Note: To identify which subsystem has been re-routed, check the operational attribute subsystemUsageStatus under the TCAP Ss7IpIf on the SGSN. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause commSubsystemFailureCause_c Type communicationsType_c Remedial action No action needs to be taken.
411-5221-500
Standard
04.05
January 2007
7068_1553 - MAP Client IP Network Error Alarm (GPRS/UMTS) 143 Copyright 20042007 Nortel Networks
7068_1553 - MAP Client IP Network Error Alarm (GPRS/UMTS)

Alarm 7068 1553 Component Gsc/<x> MapClient Legend <x> = component instance identifier Details This alarm is generated against the MapClient component when the IP Server returns an error while sending a message from HLRSIM to MapClient. Possible error causes are: Bad Net Host unreachable Protocol error Port unreachable Fragmentation needed Destination unreachable Source Route Failed This alarm is cleared when MapClient is able communicate with the IP Server. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause lossOfSignalCause_c Type communicationsType_c Remedial action Verify the IP Server is functioning properly. Severity major Status set/clear
SGSN5.0
7068_1554 - Sgsn Audit Memory Corruption Alarm (GPRS/UMTS)

Alarm 7068 1554 Component Gsc/<x> Usc/<x> Legend <x> = component instance identifier Details This alarm indicates that the system has identified blocks of memory that may be corrupted and could cause performance degradation. It is raised with major severity when the number of identified blocks exceeds the high water mark (100). This alarm is cleared when the number falls below the high water mark. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause corruptDataCause_c Type processingType_c Remedial action If this alarm is seen, contact Nortel support personnel. The following remedial action must be taken when the alarm is generated (number of corrupt data blocks exceeds the high water mark). Each of the actions below can reduce the likelihood of an unplanned outage. They are listed in order from the smallest to the largest system impact. Note: If the alarm is set on both the active and the standby instances of a USC or GSC, then a card reset (action 3 below) is required. 1. If a standby instance of the affected USC or GSC exists and the provisionable attribute Sgsn rexType or Usgsn rexType is set to switchActiveAndStandby, then no action is required. At the provisioned time (Sgsn rexTime or Usgsn rexTime), the Rex test will reset the standby card, re-synchronize data between the active and standby cards, reset the active card (resulting in a switchover), and again resynchronize data between the active and standby cards. 2. If a standby instance of the affected USC or GSC exists but rexType is not set to switchActiveAndStandby, then a manual switchover can be performed. This will impact any GMM or SM activities currently in progress. 3. If standby instances do not exist, then the affected USC or GSC can be reset. This will result in a temporary total service interruption for subscribers currently served by the USC or GSC. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1555 - Ss7IpIf Noisy Link Alarm (GPRS/UMTS) 145 Copyright 20042007 Nortel Networks
7068_1555 - Ss7IpIf Noisy Link Alarm (GPRS/UMTS)

Alarm 7068 1555 Component Tcap/<x> Ss7IpIf/<x> Legend <x> = component instance identifier Details The alarm will be set when the number of outstanding lost messages that are being tracked by the High-Level Data Link Control (HDLC) layer surpasses the number specified by the lostMessagesThreshold provisionable attribute. The alarm will be cleared when the number of outstanding lost messages dips below the lostMessagesThreshold attribute (plus some buffer to prevent alarm oscillation). Note: this alarm is only raised for UDP connections. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause performanceDegradedCause_c Type qualityOfServiceType_c Remedial action This alarm indicates that the UDP/IP link between the MapStack and the SS7 IP Gateway (SIG) is excessively noisy. Try to limit the number of hops or configure a more optimal network path between the two nodes. Severity minor Status set/clear
SGSN5.0
7068_1556 - Mobile Context Mismatch In GMM Alarm (UMTS; Obsolete)

Alarm 7068 1556 Component Usc/<x> Legend <x> = component instance identifier Details This alarm indicates a very rarely occurring software error within the SGSN. The USC emits this alarm when it encounters a software error while processing the Attach Request received from an MS. The error is mainly due to a mismatch between the IMSI stored inside the mobile context and the IMSI to which it is mapped in the mapping table. The alarm message string provides information such as PMM State, PTMSI and other internal data belonging to the original mobile context. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. This alarm is obsoleted in SGSN5.0. Probable Cause debuggingCause_c Type debugType_c Remedial action This alarm is intended to help diagnose attach failures reported by the USC due to an internal software error. It may be useful to divert all alarms with this index to a single text file on the MDM server for the entire network to get a good view of failures related to this specific error. See Appendix B for more information on how this can be done with MDM. Severity minor Status message
411-5221-500
Standard
04.05
January 2007
7068_1557 - Nodal Manager Call Released Alarm (GPRS/UMTS) 147 Copyright 20042007 Nortel Networks
7068_1557 - Nodal Manager Call Released Alarm (GPRS/UMTS)

Alarm 7068 1557 Component Sgsn Sh ConS/<x> Sgsn Sh ConM Legend <x> = component instance identifier Details When the status is SET, a call has been dropped because the far end released it. When the status is CLR, an outgoing call (Master NM) or incoming call (affected Slave NM) has been established. Probable Cause callEstablishmentErrorCause_c Type communicationsType_c Remedial action Check connectivity between the master NM and the slave NM. The master NM will try to re-establish the call automatically. Severity critical Status set/clear
SGSN5.0
7068_1558 - Nodal Manager Resource Failure Alarm (GPRS/UMTS) 2

Alarm 7068 1558 Component Sgsn Sh ConS/<x> Sgsn Sh ConM Legend <x> = component instance identifier Details When the status is SET, a call has been dropped or will not be established because of a resource failure. When the status is CLR, an outgoing call (Master NM) or incoming call (affected Slave NM) has been established. Probable Cause callEstablishmentErrorCause_c Type communicationsType_c Remedial action None. The master NM will try to establish/re-establish the call automatically. Severity critical Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1559 - Nodal Manager Registration Alarm (GPRS/UMTS) 149 Copyright 20042007 Nortel Networks
7068_1559 - Nodal Manager Registration Alarm (GPRS/UMTS)

Alarm 7068 1559 Component Sgsn Sh ConS/<x> Sgsn Sh ConM Legend <x> = component instance identifier Details When the status is SET, a Slave NMs registration request to the Master NM has been rejected or has not been acknowledged within a reasonable amount of time. (Only SET on the slave.) When the status is CLR, the Slave NMs registration request has been accepted and acknowledged. (Only CLR on the slave.) When the status is MSG, the slave has successfully registered with the master. If a SET alarm has already been generated on the slave, a CLR alarm will be generated on the slave instead of a MSG alarm. Probable Cause callEstablishmentErrorCause_c Type communicationsType_c Remedial action None. The slave NM will continue to try to register until it is successful. Severity critical Status set/ clear/ message
SGSN5.0
7068_1560 - Nodal Manager Outgoing Call Request Failure Alarm (GPRS/UMTS)

Alarm 7068 1560 Component Sgsn Sh ConS/<x> Legend <x> = component instance identifier Details When the status is SET, the master NM could not establish a call with a slave NM. When the status is CLR, an outgoing call to the affected slave NM has been established. Probable Cause callEstablishmentErrorCause_c Type communicationsType_c Remedial action Check the provisioning of NSAP addresses and check the connectivity between the master NM and the slave NM. The master NM will continue to try to establish the call automatically. Severity critical Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1561 - Nodal Manager Incoming Call Timeout Alarm (GPRS/UMTS) 151 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1561 - Nodal Manager Incoming Call Timeout Alarm (GPRS/ UMTS)

Alarm 7068 1561 Component Sgsn Sh ConM Legend <x> = component instance identifier Details When the status is SET, a slave NM has completed the initialization period without receiving a call from the master NM. When the status is CLR, the slave NM has received a call from the master NM. Probable Cause callEstablishmentErrorCause_c Type communicationsType_c Remedial action Check the provisioning of the masters ConS components and associated NSAP addresses. Severity critical Status set/clear
SGSN5.0
7068_1562 - Nodal Manager Invalid Master Alarm (GPRS/UMTS)

Alarm 7068 1562 Component Sgsn Sh ConM Legend <x> = component instance identifier Details When the status is SET, a slave NM has rejected a call from a master NM because the masters NSAP did not match that provisioned on the slaves ConM subcomponent. When the status is CLR, a quiet period has passed during which no calls were made from an invalid Master NM. Probable Cause configurationErrorCause_c Type processingType_c Remedial action Check the provisioning and verify that only one passport has ConSs, and all NSAP addresses are correct. Severity minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1564 - SAS Fail to Send Message to SC Alarm (GPRS/UMTS) 153 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1564 - SAS Fail to Send Message to SC Alarm (GPRS/UMTS) 2

Alarm 7068 1564 Component Sas/<x> Legend <x> = component instance identifier Details This alarm is used to inform the operator that attempts to send a message to Subscriber Control have failed. The SC instance that SAS is attempting to send a message to is not available. This may occur if an SC switchover or reset has occurred and the SAS component has not been notified yet. All messages from SAS to SC are part of audits and there is no long term billing data loss. The billing information will be updated at the next audit interval. The operator is informed because some partial records may not be generated at the expected interval. Audit messages related to a Tariff Time change are retried and if the retry is unsuccessful, this message alarm is issued. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause commSubsystemFailureCause_c Type processingType_c Remedial action None. Either the next audit interval will retrieve the billing information or the CDR will be closed due to SC reset. Severity minor Status message
SGSN5.0
7068_1565 - Activation Reject Counter Alarm (UMTS; Obsolete)

Alarm 7068 1565 Component Usc/<x> Sm Legend <x> = component instance identifier Severity warning Status message
411-5221-500
Standard
04.05
January 2007
7068_1565 - Activation Reject Counter Alarm (UMTS; Obsolete) 155 Copyright 20042007 Nortel Networks Severity Status
Details This alarm captures internal debug counters that can facilitate identification of activation rejections with the following causes: Activation Reject Unspecified, Insufficient Resources, Network Failure. It is generated at the provisioned number of DCS intervals specified by the Usgsn customSpare/8 spare7Prov attribute. The following internal debug counters are included in the alarm text. They are divided by Activation Reject cause values as follows:
Activation Reject Unspecified: DNS Proxy Error DNS Response Error Dup Act Reject SSF Failure Response GTP Failure MS/RNC/RELAY Proxy Failure RAB Setup Timer Expiry RNC Down Error GGSN Errors Timers Expiry Insufficient Resources: USC In Ovrld SM Cntxt Retrv Fail Timers Fail Relay Create Ssn Fail SSF Resources Network Failures: GGSN Path Failure USD Failure GGSN Deact Request RNC Failure RAB Setup Failure
This alarm was introduced in GPRS5 and UMTS3 as part of the following patches: usgsnQ00806750, sgsncQ00806750 and genuQ00806750. Probable Cause debuggingCause_c
SGSN5.0
156 SGSN Alarms Nortel Networks Confidential Alarm Component Type debugType_c
Remedial action Examine the SM activation failure counters. Verify the health of the network.
411-5221-500
Standard
04.05
January 2007
7068_1566 - SAS Not Ready for Switchover Alarm (GPRS/UMTS) 157 Copyright 20042007 Nortel Networks
7068_1566 - SAS Not Ready for Switchover Alarm (GPRS/UMTS)

Alarm 7068 1566 Component Sas/<x> Legend <x> = component instance identifier Details This alarm is used to inform the operator of the availability of hot standby services for SAS. It is set with critical severity on the active card when problems are encountered while synchronizing data on the standby card and the active card. This indicates that the standby card is not ready to provide standby services. This condition is cleared when data on the active and standby cards is successfully synchronized. When the condition is cleared, this alarm is cleared to indicate that standby services are available. This alarm is generated from both the active card and the standby card with text that indicates which card is issuing the alarm. This is done to make sure the correct information is given to the operator in a situation where the channel between the active and standby is not functioning correctly. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause applSubsystemFailCause_c Type processingType_c Remedial action None. Re-synchronization is attempted automatically. Severity critical Status set/clear
SGSN5.0
7068_1567 - NMA Application Info Report Corrupt Alarm (GPRS/ UMTS)

Alarm 7068 1567 Component Gsc Gsd Liaf Sg SgGtl SigtranAsp Tcap Usd Legend N/A Details When a Nodal Manager Agent (NMA) receives an application information report from the CP indicating that a new application is up, the NMA tries to verify that all entries are valid. If some entry is invalid (e.g., application type, shelf ID, application instance number, active/standby indication), then the report is considered corrupt. If the report is corrupt, this alarm is issued and the report is discarded. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause applSubsystemFailCause_c Type processingType_c Remedial action On each FP, run displayNmaTable and check for missing applications. On the active CP, run displayNmTable and check for missing applications. Reset the card whose information is missing from the tables. Note that resetting a card will cause that card to lose service. Severity Status
major
message
411-5221-500
Standard
04.05
January 2007
7068_1568 - Loss of Communication with MapStack Alarm (GPRS/UMTS) 159 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1568 - Loss of Communication with MapStack Alarm (GPRS/ UMTS) 2

Alarm 7068 1568 Component Gsc/<x> MapClient Usc/<x> MapClient Legend <x> = component instance identifier Details This alarm is raised when the MapClient component is unable to establish communication with the MapStack component. The cause for this alarm may be any of the following: - Invalid provisioning of the remoteMapStackServer attribute. - Unavailability of the MapStack component (i.e. no MAP/TCAP card present) - Failure of MapStack component. While this alarm is active, the MapClients OSI state is Unlocked, Disabled, Idle. The MapClient component continues to retry the connection once every minute until it is successfully established. The alarm is cleared once the MapClient and MapStack are able to communicate. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause commSubsystemFailureCause_c Type communicationsType_c Remedial action 1. Verify the provisioning of the remoteMapStackServer attribute. 2. Make sure that such provisioning is set to an existing MAP/TCAP card. 3. Make sure that the MapStack component is provisioned on the MAP/TCAP card and that it is working properly. Severity critical Status set/clear
SGSN5.0
7068_1569 - Loss of Communication with TcapStack Alarm (GPRS/ UMTS) 2

Alarm 7068 1569 Component Gsc/<x> ServiceSwitchingFunction Usc/<x> ServiceSwitchingFunction Legend <x> = component instance identifier Details This alarm is raised when the Ssf component is unable to establish communication with the TcapStack component. The cause for this alarm may be any of the following: - Invalid provisioning of the remoteTcapStackServer attribute when desired TCAP application is on a different SGSN shelf. - Unavailability of the TcapStack component (i.e. no MAP/TCAP card present) - Failure of TcapStack component. While this alarm is active, the Ssf components OSI state is Unlocked, Disabled, Idle. The Ssf component continues to retry the connection once every minute until it is successfully established. The alarm is cleared once the SSF application and TcapStack are able to communicate. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause commSubsystemFailureCause_c Type communicationsType_c Remedial action 1. Verify the provisioning of the Gsc Ssf remoteTcapStackServer or Usc Ssf remoteTcapStackServer attribute. 2. Make sure that such provisioning is set to an existing TCAP application. 3. Make sure that the TCAP application is working properly. Severity critical Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1570 - SNR Audit Memory Corruption Alarm (GPRS/UMTS) 161 Copyright 20042007 Nortel Networks
7068_1570 - SNR Audit Memory Corruption Alarm (GPRS/UMTS)

Alarm 7068 1570 Component Gsc/<x> Usc/<x> Legend <x> = component instance identifier Details The SNR Audit Memory Corruption alarm is set when a corrupted block of memory is detected for Seamless National Roaming (SNR) by the memory pool auditor, which runs periodically on GSCs and USCs. This alarm is cleared when the SNR provisioning data is resent to the GSC or USC application. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause corruptDataCause_c Type processingType_c Remedial action Reset the logical processor associated with the card on which the alarm is raised. Severity major Status set/clear
SGSN5.0
7068_1571 - GTP Version Mismatch Alarm (GPRS; Obsolete)

Alarm 7068 1571 Component Gsc/<x> minor Legend <x> = component instance identifier Details This alarm is generated if the version of the GTP path to a GGSN is different than the version of the message received, or if the SGSN sends a message with a certain message-version on a GTP path but the reply is received on a different GTP path whose version does not match the received message-version. This alarm can be disabled by setting the Q00871465_gtpAlarmGeneration_g global to zero. This alarm is cleared when all GTP paths with a version mismatch are deleted. This alarm was introduced in GPRS5 as part of patch sgsncQ00871465. Probable Cause remoteTransmissionErrorCause_c Type communicationsType_c Remedial action GTP paths that experience a version mismatch may be unable to process GTP messages. GTP paths identified by this alarm can be deleted through the deleteGtpPath eggshell function to fix the problem. Also, the displayVerMismatchPaths eggshell function can be used to display all GTP paths identified as having a version mismatch. Severity Status set/ clear/ message
411-5221-500
Standard
04.05
January 2007
7068_1572 - SC Redundancy Sync Loss Alarm (GPRS/UMTS) 163 Copyright 20042007 Nortel Networks
7068_1572 - SC Redundancy Sync Loss Alarm (GPRS/UMTS)

Alarm 7068 1572 Component Gsc/<x> Usc/<x> Legend <x> = component instance identifier Details This alarm is raised for redundant subscriber cards when synchronization loss is detected between the active and standby instances. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause applSubsystemFailCause_c Type processingType_c Remedial action Remedial action depends on provisioned REX Type. If REX Type is set to 1. Disabled: Operator is expected to manually reset the standby card to recover from synchronization loss. 2. resyncStandbyOnly: Standby card will be reset automatically at the provisioned 'REX Time' to recover from synchronization loss. 3. switchActiveAndStandby: Standby card will be reset automatically at the provisioned 'REX Time' to recover from synchronization loss. Severity major Status message
SGSN5.0
7068_1573 - Switchover During Checkpointing Alarm (GPRS/UMTS) 2

Alarm 7068 1573 Component Gsc/<x> Usc/<x> Legend <x> = component instance identifier Details This alarm is generated if a switchover occurs during checkpointing. The alarm has information about the percentage of mobiles that lost service because of the switchover occurring before all the mobiles could be checkpointed. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause applSubsystemFailCause_c Type processingType_c Remedial action This alarm is informational in nature. No remedial action is necessary. Severity major Status message
411-5221-500
Standard
04.05
January 2007
7068_1574 - GPRS Attach Success Rate Threshold Alarm (GPRS) 165 Copyright 20042007 Nortel Networks
7068_1574 - GPRS Attach Success Rate Threshold Alarm (GPRS)

Alarm 7068 1574 Component Gsc/<x> Legend <x> = component instance identifier Details This alarm is issued with major or minor severity depending on the current state of the alarm and the relationship between the calculated attach success rate for GPRS subscribers and the provisioned thresholds. The attach success rate formula is defined in the SGSN Monitoring Guide, NTP 411-5221-050 for GPRS. This alarm is based on the nodal success rate, not the network success rate. The attach success rate for GPRS subscribers is calculated over data from the past 15 minutes (default), and is updated every 3 minutes (default). If fewer than 100 attempts (default) are made, then the success rate for GPRS subscribers is not updated, since insufficient information is available for making a decision on the status of the node. Alarms are generated when the success rate for GPRS subscribers crosses the thresholds as follows. If the calculated success rate for GPRS subscribers rises above the clear threshold (98% default) then a clear alarm is issued (or the alarm remains inactive). If the calculated success rate for GPRS subscribers falls below or rises above the minor threshold (95% default), while staying between the major and clear thresholds, then a minor alarm is issued (or remains active). If the calculated success rate for GPRS subscribers falls below the major threshold (90% default) then a major alarm is issued (or remains active). Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action Examine the GMM attach failure counters (in the Gsc Gmm component hierarchy) and verify the health of the network. Severity major/minor Status set/clear
SGSN5.0
7068_1575 - GPRS Activation Success Rate Threshold Alarm (GPRS)2

Alarm 7068 1575 Component Gsc/<x> Legend <x> = component instance identifier Details This alarm is issued with major or minor severity depending on the current state of the alarm and the relationship between the calculated activation success rate for GPRS subscribers and the provisioned thresholds. The activation success rate formula is defined in the SGSN Monitoring Guide, NTP 411-5221-050 for GPRS. This alarm is based on the nodal success rate, not the network success rate. The activation success rate for GPRS subscribers is calculated over data from the past 15 minutes (default), and is updated every 3 minutes (default). If fewer than 100 attempts (default) are made, then the success rate for GPRS subscribers is not updated, since insufficient information is available for making a decision on the status of the node. Alarms are generated when the success rate for GPRS subscribers crosses the thresholds as follows. If the calculated success rate for GPRS subscribers rises above the clear threshold (98% default) then a clear alarm is issued (or the alarm remains inactive). If the calculated success rate for GPRS subscribers falls below or rises above the minor threshold (95% default), while staying between the major and clear thresholds, then a minor alarm is issued (or remains active). If the calculated success rate for GPRS subscribers falls below the major threshold (90% default) then a major alarm is issued (or remains active). Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action Examine the SM activation failure counters (in the Gsc Sm component hierarchy) and verify the health of the network. Severity major/minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1576 - SAS Memory Pool High Usage Alarm (GPRS/UMTS) 167 Copyright 20042007 Nortel Networks
7068_1576 - SAS Memory Pool High Usage Alarm (GPRS/UMTS)

Alarm 7068 1576 Component Sas/<x> Legend <x> = component instance identifier Details The SAS Memory Pool High Usage alarm is raised by the Sas component when certain memory pool usage thresholds are crossed for any memory pool associated with CDR generation. The alarms are issued each time any pool crosses a threshold. The highest severity of all pools is used for the severity of the alarm. Information in the alarm indicates which memory pool usage has changed to cause the alarm to be issued. The following memory pools are analyzed to determine the status of the alarm: S-CDR memory pool S-CDR Container memory pool Camel Information memory pool M-CDR memory pool M-CDR Container memory pool The severities and usage levels are defined as follows: Minor - the pool usage has reached 70% Major - the pool usage has reached 80% Critical - the pool usage has reached 99% Clear - the pool usage has fallen below 65% At the critical level, this alarm indicates that there is a danger of CDR information loss or corruption. The major and minor alarms are issued to provide the operator with information so that a configuration change may be made to alleviate memory usage problems. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c Type processingType_c Remedial action Modify the provisioning for the Sas component to reduce the maximum number of containers allowed for S-CDRs and M-CDRs. If M-CDRs are not being used for billing purposes, modify provisioning to discontinue the capture of M-CDRs. Severity critical/ major/minor Status set/clear
SGSN5.0
7068_1577 - SAS Card Memory High Usage Alarm (GPRS/UMTS)

Alarm 7068 1577 Component Sas/<x> Legend <x> = component instance identifier Details The SAS Card Memory High Usage alarm is raised by the Sas component when the card on which the Sas component is configured has crossed certain memory usage thresholds for the effective memory available. The severities and usage levels are defined as follows: Minor - the pool usage has reached 70% Major - the pool usage has reached 80% Critical - the pool usage has reached 99% Clear - the pool usage has fallen below 65% At the critical level, this alarm indicates that there is a danger of CDR information loss or corruption. The major and minor alarms are issued to provide the operator with information so that a configuration change may be made to alleviate memory usage problems. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause atOrNearCapacityCause_c Type processingType_c Remedial action Modify the provisioning for the Sas component to reduce the maximum number of containers allowed for S-CDRs and M-CDRs. If M-CDRs are not being used for billing purposes, modify provisioning to discontinue the capture of M-CDRs. Severity critical/ major/minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1578 - Loss of Communication with the DNS Server Alarm (GPRS/UMTS) 169 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1578 - Loss of Communication with the DNS Server Alarm (GPRS/UMTS)

Alarm 7068 1578 Component DnsAg/<x>,<y> Legend <x> = instance identifier of the VR <y> = instance identifier of the dnsAgent Details The Loss of Communication with DNS Server alarm is raised by the DnsAg component with minor severity when there is a communication problem between the DNS Agent application and one or more but not all of the provisioned DNS servers. If DNS Agent is unable to communicate with any of the provisioned DNS servers, then this alarm is raised with critical severity. This alarm is reissued periodically (every 5 minutes by default) as the status of communication between the provisioned servers and DNS Agent changes. If there is no status change to report, the alarm is not reissued. When DNS Agent can communicate with all provisioned DNS servers, this alarm is cleared. The following are possible causes of communication failure: Severity minor/critical Status set/clear
ICMP network errors: Bad Net Host is unreachable Protocol error Port is unreachable Fragmentation is needed Source Failed IP Server is unavailable DNS Server failure Server Response Timeout
Probable Cause lossOfSignalCause_c Type communicationsType_c Remedial action Verify the IP Server, Network and DNS Server availability.
SGSN5.0
7068_1579 - NPI Calculation Data for Activation Rejects Alarm (UMTS; Obsolete)
Alarm 7068 1579 Component Usc/<x> Sm Legend <x> = component instance identifier Details This alarm captures activation rejection (cause) counters required to calculate the Active Performance Rate, which is based on activation failure-specific counters. It is generated at the provisioned number of DCS intervals specified by the Usgsn customSpare/8 spare6Prov attribute. The following counters are included in the alarm text. Severity warning Status message
ActivationRejUnspecified ReqServiceOpNotSubscribed ServiceOpTempOutOfOrder InvalidMandatoryInfo MsgNotCompatibleWithProtocolState NetworkFailure ProtocolErrorUnspecified ReactivationRequired InvalidTiValue
Each counter has two values associated with it. The first is the current value and the second is the cumulative value. The current value is added to the cumulative value and then reset after the alarm is generated. This alarm was introduced in GPRS5as part of the following patches: usgsnQ00806750, sgsncQ00806750 and genuQ00806750. Probable Cause debuggingCause_c Type debugType_c Remedial action Examine the SM activation failure counters. Verify the health of the network.
411-5221-500
Standard
04.05
January 2007
7068_1580 - Internal Diagnostic Alarm (GPRS/UMTS) 171 Copyright 20042007 Nortel Networks
7068_1580 - Internal Diagnostic Alarm (GPRS/UMTS)

Alarm 7068 1580 Component Em<x> Legend N/A Details An internal diagnostic file has been made available on the disk of the active CP. Contact next level of support personnel to retrieve this file. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. It should not be generated from a standby state. But in either case, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause softwareErrorCause_c Type processingType_c Remedial action Contact next level of support. Severity minor Status set/clear
SGSN5.0
7068_1581 - SC Resource Exhaustion Alarm (GPRS/UMTS)

Alarm 7068 1581 Component Gsc/<x> DnsAg/<y>, <z> Legend <x> = component instance identifier <y> = instance identifier of the VR <z> = instance identifier of the dnsAgent Details This alarm is raised against the Gsc and DnsAg components when the following pools reach predefined usage thresholds. Note: The pool manager and pool name are shown next to each pool title, followed by the impact of exhausting the pool. Gsc: - SM Context (cmPoolManager_smp/SmSessionContext) Impact: no more activations. - GMM Detach Procedure Context (cmPoolManager_smp/GmmDetCtxt) Impact: GMM context hangs; no detaches - GPRS GMM RAU PDP Context (cmPoolManager_smp/Gmm2gRauPdpCtxt) Impact: no RAUs into the GPRS system. - GMM Procedure Context (cmPoolManager_smp/GmmPrcdCtxt) Impact: no more attaches; no RAUs into the UMTS system; all GMM procedures fail except for RAUs into the GPRS system and detaches from either system. - IU Connection Context (cmPoolManager_smp/RncData) Impact: all initial UE messages fail - SRNS New SGSN Context (rncMemPoolManager_smp/ RncSrnsNewSgsnCtxt) Impact: SRNS fails - SRNS Old SGSN Context (rncMemPoolManager_smp/RncSrnsOldSgsnCtxt) Impact: SRNS fails - HLRC PDP Context (hlrcPoolManager_mp/HlrcPdpContext) Impact: no more attaches - SM Procedure Context (cmPoolManager_smp/SmProcedureContext) Impact: all SM procedures other than deactivate fail - SM GTP-C Procedure Context (cmPoolManager_smp/SmGtpcData) Impact: all SM to GTP-C messaging fails DnsAg: - DNS Query Message (dnsAgentPoolMgr_mp/GprsDnsAgentQueryElement) Impact: external DNS queries fail Severity major/minor/ warning Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1581 - SC Resource Exhaustion Alarm (GPRS/UMTS) 173 Copyright 20042007 Nortel Networks Severity Status
Details The alarm severities for each pool are based on the percentage of the maximum pool size currently in use as shown below. Major Set: 100% Major Abate: 95% Minor Set: 95% Minor Abate: 90% Warning Set: 90% Warning Abate: 85%
If usage for a given pool crosses a Set threshold from below, the alarm is set with the associated severity. If usage crosses an Abate threshold from above, the alarm is downgraded to a lower severity. The alarm text shows which pools are in a high usage state along with the associated severity. The alarm is generated each time any pool crosses a threshold, but the severity of the alarm is the highest severity of all the pools. Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action Contact Nortel support personnel.
SGSN5.0
7068_1585 - Sigtran Remote Address Inactive alarm (GPRS/UMTS)

Alarm 7068 1585 Component SctpLayer/<a> Ep/ Assoc/<c> RemAddr/<d> Legend <a>, , <c>, <d> = component instance identifiers Details The SCTP remote address inactive alarm is raised when the provisioned address identified by this component is not responding to SCTP messages. This alarm indicates that there is a loss of redundancy on this SCTP association. Controls within the SCTP protocol prevent this alarm flooding the system or rapidly transitioning from cleared to set. This alarm is cleared when the remote address starts responding to messages again, or the provisioning for this remote address is removed. Probable Cause remoteTransmissionError Type communication Remedial action Check IP network status. Check IP network configuration between SGSN and the remote address. Severity Minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1586 - Sigtran No Destination Routable alarm (GPRS/UMTS) 175 Copyright 20042007 Nortel Networks
7068_1586 - Sigtran No Destination Routable alarm (GPRS/UMTS)

Alarm 7068 1586 Component SigtranAsp/<a> Legend <a> = component instance identifier Details The SigtranAsp raises this alarm and becomes disabled when there are no destinations routable through the SIGTRAN network. This will occur when there are no established M3UA connections to end points. Outgoing traffic to SIGTRAN destinations is not possible. If the SGSN has HP-SIG(s) installed and configured, the MAP, BSSAP+ and SMS clients will automatically fall back to communicating directly with the HPSIG(s). This will have minimal impact on traffic processing to legacy SS7 destinations, but SIGTRAN destinations will remain unreachable. If no HP-SIG(s) are present, this alarm represents a complete failure of SGSN signalling. This alarm has a blackout period to avoid a noisy/unstable M3UA connection from flooding alarms into the system. This alarm will not be set again or cleared during a 5 second blackout period. At the end of the blackout period, the latest event (either set or cleared) will be applied to the alarm. This alarm is cleared when the SigtranAsp M3UA layer establishes at least one connection to a provisioned destination, or all M3ua Destination components are removed. Probable Cause remoteTransmissionError Type communication Remedial action If this alarm persists after startup, check the details of the SigtranAsp M3ua Dest/ <a> components for indication of why the destination is unreachable Severity Critical Status set/clear
SGSN5.0
7068_1587 - Sigtran No SG Available alarm (GPRS/UMTS)

Alarm 7068 1587 Component SigtranAsp/<a> M3ua Legend <a> = component instance identifier Details No provisioned SIGTRAN signalling gateways are reachable from this SigtranAsp. For this alarm to be raised, at least one SigtranAsp M3ua PeerProcess must be configured of peerType = sgp. If there are no SIGTRAN signalling gateways provisioned, then this alarm is not raised. This alarm has a blackout period to avoid a noisy/unstable M3ua connection to a SIGTRAN signalling gateway from flodding alarms into the system. This alarm will not be set again or cleared during a 1 minute blackout period. At the end of the blackout period, the latest event (either set or cleared) will be applied to the alarm. This alarm is cleared when at least one PeerProcess component of type = sgp is reachable from this SigtranAsp; or all PeerProcess components of type = sgp have been removed. Probable Cause remoteTransmissionError Type communication Remedial action If this alarm persists after startup, check the details of the SigtranAsp/<a> M3ua PeerProcess/<a> components having peerType attribute to sgp. Severity Major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1588 - Sigtran PeerProcess Not Active alarm (GPRS/UMTS) 177 Copyright 20042007 Nortel Networks
7068_1588 - Sigtran PeerProcess Not Active alarm (GPRS/UMTS)

Alarm 7068 1588 Component SigtranAsp/<a> M3ua PeerProcess/ Legend <a>, = component instance identifiers Details The remote peer process represented by this component is unavailable for routing purposes. This alarm is set for any PeerProcess/ component having a state other than active. PeerProcess/ components with this alarm raised are remo ved from the M3ua dynamic routing table. Depending on SIGTRAN configuration, this may reduce redundancy to a destination(s), or make the destination unroutable. Each SigtranAsp may have up to 1024 PeerProcess/ components; each component may raise this alarm independantly. This alarm has a blackout period to avoid a noisy/unstable M3ua connection from flooding alarms into the system. This alarm will not be set again or cleared during a 5 second blackout period. At the end of the blackout period, the latest event (either set or cleared) will be applied to the alarm. This alarm is cleared when connection is established to the peer process or the PeerProcess/ component is removed Probable Cause remoteTransmissionError Type communication Remedial action If this alarm persists after startup, check the status of the destination represented by this PeerProcess component Severity Minor Status set/clear
SGSN5.0
7068_1589 - Sigtran Sgsn PeerProcess Blocked alarm (GPRS/UMTS)

Alarm 7068 1589 Component SigtranAsp/<a> M3ua PeerProcess/ Legend <a>, = component instance identifiers Details The SCTP of the remote peer process represented by this component is blocked. No messages can be routed to the destination through this association while the remote socket remains blocked. PeerProcess/ components with this alarm raised are removed from the M3ua dynamic routing table. Depending on SIGTRAN configuration, this may reduce redundancy to a destination(s), or make the destination unroutable. Each SigtranAsp may have up to 1024 PeerProcess/ components; each component may raise this alarm independantly. This alarm has a blackout period to avoid a noisy/unstable remote-end SCTP socket from flodding alarms into the SGSN system. This alarm will not be set again or cleared during a 5 second blackout period. At the end of the blackout period, the latest event (either set or cleared) will be applied to the alarm. This alarm is cleared when the remote SCTP socket for this peer process is unblocked or this PeerProcess/ is removed. Probable Cause underlyingResourceUnavailable Type processing Remedial action If this alarm occurs during normal operating traffic load with all subsystems functional, consider increasing the local peerProcTxBufferSize attribute. This allows more traffic to queue for the destination before this alarm is raised. Severity Minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1590 - Sigtran PeerProcess Congested alarm (GPRS/UMTS) 179 Copyright 20042007 Nortel Networks
7068_1590 - Sigtran PeerProcess Congested alarm (GPRS/UMTS)

Alarm 7068 1590 Component SigtranAsp/<a> M3ua PeerProcess/ Legend <a>, = component instance identifiers Details The peer process represented by this component is reporting congestion. For networks supporting a single congestion level, this is an informative alarm and messages will continue to be routed to the affected peer process. For networks supporting multiple congestion levels, if the peer process is reporting partial congestion the PeerProcess/ components with this alarm raised may not be considered available when routing low-priority messages. If this peer process is reporting that it is blocked, then no messages can be routed through this peer process association while the remote end remains congested. Depending on SIGTRAN configuration, this may reduce redundancy to destinations that are available through this peer process association, or make these same destinations unroutable. Each SigtranAsp may have up to 1024 PeerProcess/ components; each component may raise this alarm independantly. This alarm has a blackout period to avoid a noisy/unstable remote-end SCTP socket from flodding alarms into the SGSN system. This alarm will not be set again or cleared during a 5 second blackout period. At the end of the blackout period, the latest event (either set or cleared) will be applied to the alarm. This alarm is cleared when the remote SCTP for this peer process reports that congestion has abated, or this PeerProcess/ component is removed. Probable Cause congestion Type qualityOfService Remedial action If traffic rates are within normal operating limits and all subsystems are available, then the processing capacity of the remote peer process has likely been over-estimated. The resolution is to address engineering considerations on the remote destination. Severity Minor Status set/clear
SGSN5.0
7068_1591 - Sigtran Destination Unroutable alarm (GPRS/UMTS)

Alarm 7068 1591 Component SigtranAsp/<a> M3ua Dest/ Legend <a>, = component instance identifiers Details This alarm is set for any M3ua Destination/ component that has a state of unroutable. There is no way to route traffic to the destination while the alarm is set. All destinations are assumed to be unroutable until a message is successfully sent to the destination. Each SigtranAsp may have up to 1024 Destination/ components; each component may raise this alarm independantly. This alarm has a blackout period to avoid an intermittent or chattering issue from flodding alarms into the SGSN system. This alarm will not be set again or cleared during a 5 second blackout period. At the end of the blackout period, the latest event (either set or cleared) will be applied to the alarm. This alarm is cleared when messages can be successfully sent to the destination, or the Dest/ component has been removed. Probable Cause remoteTransmissionError Type communication Remedial action If this alarm persists after startup, check the details of the PeerProcess components that correspond to this destination. Information in these PeerProcess components will identify the source of the fault. Check the remote destination. Severity Major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1592 - Sigtran Destination Restricted alarm (GPRS/UMTS) 181 Copyright 20042007 Nortel Networks
7068_1592 - Sigtran Destination Restricted alarm (GPRS/UMTS)

Alarm 7068 1592 Component SigtranAsp/<a> M3ua Dest/ Legend <a>, = component instance identifiers Details The destination node represented by this component has declared itself to be restricted. No traffic can be routed to this destination. Setting of the restricted state on a remote node occurs manually as a part of network operation and management. A destination will remain restricted until such time as the restriction is removed by the network operator. This alarm is never raised with the destinationUnroutable alarm on the same destination. If the destination reports restricted and the destinationUnroutable alarm is already set, then destinationUnroutable is cleared, and destinationRestricted is set. Each SigtranAsp may have up to 1024 Destination components; each component may raise this alarm independantly. This alarm has a blackout period to avoid an intermittent or chattering issue from flodding alarms into the SGSN system. This alarm will not be set again or cleared during a 1 minute blackout period. At the end of the blackout period, the latest event (either set or cleared) will be applied to the alarm. This alarm is cleared when the remote node declares that the restricted state has ended, or the Dest/ component is removed. Probable Cause underlyingResourceUnavailable Type processing Remedial action This alarm is caused through an operator management action on a remote node setting the destination node to a restricted state. The operator must return the destination node to service to clear this alarm. Severity Minor Status set/clear
SGSN5.0
7068_1593 - Sigtran Destination Congested alarm (GPRS/UMTS)

Alarm 7068 1593 Component SigtranAsp/<a> M3ua Dest/ Legend <a>, = component instance identifiers Details The destination represented by this component is reporting congestion. For networks supporting a single congestion level, no messages can be routed to this destination while it remains congested. For networks supporting multiple congestion levels, if the destination is reporting partial congestion then Destination/ components with this alarm raised may not be considered available when routing low-priority messages. If the destination is reporting that it is blocked, then no messages can be routed to this destination while it remains congested. Each SigtranAsp may have up to 1024 Destination/ components; each component may raise this alarm independantly. This alarm has a blackout period to avoid a noisy/unstable destination from flodding alarms into the SGSN system. This alarm will not be set again or cleared during a 5 second blackout period. At the end of the blackout period, the latest event (either set or cleared) will be applied to the alarm. This alarm is cleared when the remote destination reports that congestion has abated, or when the Dest/ component is removed. Probable Cause congestion Type qualityOfService Remedial action If traffic rates are within normal operating limits and all subsystems are available, then the processing capacity of the destination has likely been overestimated. The resolution is to address engineering considerations on the remote destination. Severity Minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1594 - Sigtran Unauthorized Associate alarm (GPRS/UMTS) 183 Copyright 20042007 Nortel Networks
7068_1594 - Sigtran Unauthorized Associate alarm (GPRS/UMTS)

Alarm 7068 1594 Component SigtranAsp/<a> M3ua Legend <a> = component instance identifier Details An attempt to create an M3UA association from an unauthorized (nonprovisioned) IP address and port has been failed. This alarm indicates an unexpected destination has attempted to connect to this SGSN SigtranAsp. This alarm is raised on each attempt to initialize an SCTP association from a peer whose IP address does not match an ipAddress attribute of a provisioned PeerProcess. This could indicate a mis -provisioning on SigtranAsp M3ua PeerProcess, or an attack on the node. Due to the possibility of a denial of service attack flooding the system with alarms, this alarm is throttled. Once raised, no new sets of this alarm are created in the next 5 seconds. If additional instances of this message alarm are supressed during that period, then a summary message alarm is raised with details of the number of events supressed. Probable Cause denialOfService Type security Remedial action Most likely, this alarm will indicate a provisioning error. This can also occur if both M3ua and the peer Process are configured to initiate the connection. Check for mismatches between the IP address and port in the alarm and those in PeerProcess components. However, in the case of an unsecure or public network, this message alarm indicates that an intrusion has been successfully defeated. No further action is required. Severity Major Status Message
SGSN5.0
7068_1595 - Sigtran Remote Subsystem Unavailable alarm (GPRS/UMTS) 2

Alarm 7068 1595 Component SigtranAsp/<a> Sccp Rpc/ Rem/<c> Legend <a>, , <c> = component instance identifiers Details This alarm is set when a SubsystemProhibited message is received at the SigtranAsp SCCP layer from a remote SCCP layer. There are up to 1024*8 Rpc components per SigtranAsp; each may raise this alarm independently. This alarm is cleared when the remote subsystem becomes available, or the Rem/ <c> component is removed. Probable Cause commSubsystemFailureCause Type communications Remedial action Analyze the status of the remote subsystem. This alarm will remain set as long as the remote subsystem remains prohibited. Alternate paths to the subsystem may be possible; analyse the provisioned network configuration and add appropriate entries. Also Check the remote node and verify the state it is reporting to its subsystem. Severity Major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1596 - Sigtran Local Subsystem Unavailable alarm (GPRS/UMTS) 185 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1596 - Sigtran Local Subsystem Unavailable alarm (GPRS/UMTS)

Alarm 7068 1596 Component SigtranAsp/<a> Sccp Loc/ Legend <a>, = component instance identifiers Details This alarm indicates that a local SGSN subsystem is unavailable. This alarm will be raised when an incoming message is received for a local subsystem (such as TCAP or BSSAP+) that is provisioned as an sccp loc/, but is not currently registered as being available. The SigtranAsp SCCP layer supports the definition of up to 254 local subsystem components; each may raise this alarm independantly. No traffic can be routed to the affected subsystem while this alarm remains raised. The alarm is cleared when the local subsystem reports that it is active, or the Loc/ component is removed. Probable Cause commSubsystemFailureCause Type communications Remedial action Investigate the local subsystem indicated by the alarm. Severity Major Status set/clear
SGSN5.0
7068_1597 - Sigtran Unknown Destination alarm (GPRS/UMTS)

Alarm 7068 1597 Component SigtranAsp/<a> Sccp Legend <a> = component instance identifier Details A signalling message has arrived at the SCCP component from an internal client or the network and SCCP has no GTT information to route this message to its destination. The message is discarded. This message alarm is likely caused by a misconfiguration within the SCCP provisioning. The alarm provides details of the destination point code and subsystem that can be used to debug the error. Due to the possibility of a configuration error flooding the system with these message alarms, this alarm is throttled. Once raised, no new sets of this alarm are created in the next 10 seconds. If additional instances of this message alarm are supressed during that period, then a summary message alarm is raised with details of the number of events supressed. As this alarm is predominantly for use in debugging misconfigurations, its generation is toggled on and off by setting the Sgsn SigtranAsp Sccp unknownDestinationAlarm attribute. By default, this alarm is disabled. Probable Cause configurationErrorCause Type processing Remedial action Use point code and subsystem information in the alarm to diagnose misconfiguration. Severity Minor Status Message
411-5221-500
Standard
04.05
January 2007
7068_1598 - Sigtran TcpConn Congested alarm (GPRS/UMTS) 187 Copyright 20042007 Nortel Networks
7068_1598 - Sigtran TcpConn Congested alarm (GPRS/UMTS)

Alarm 7068 1598 Component SigtranAsp/<a> Siwf Legend <a> = component instance identifier Details This alarm indicates that the SigtranAsp processing capacity has been impacted due to the TCP congestion occurred between the SigtranAsp and internal SGSN clients. Some of the incoming messages (to the SGSN) may not be delivered to the internal clients for processing. This alarm has hysteresis onset and abatement thresholds that prevent the alarm being raised unnecessarily. The alarm will clear once the TCP congestion falls below the abatement threshold. Probable Cause congestion Type qualityOfService Remedial action If the traffic rate is within specificed limits and all subsystems are active, then the processing capacity of the internal clients must be increased. Severity Minor Status set/clear
SGSN5.0
7068_1599 - Sigtran No Scip Clients Registered alarm (GPRS/UMTS)

Alarm 7068 1599 Component SigtranAsp/<a> Siwf Legend <a> = component instance identifier Details SIGTRAN provides a messaging interface between internal SGSN Clients (such as TCAP and BSSAP+) and the network. This alarm is raised when SIGTRAN has no active connections to internal SGSN clients. All ingress messages from the network to the SGSN that are routed through SIGTRAN will be discarded for the duration of this alarm as there is nowhere to route them to. This alarm is cleared when SIGTRAN has at least one healthy connection to an internal client. Probable Cause commSubsystemFailureCause Type communications Remedial action If this alarm persists after startup, verify that the internal SGSN clients are present, active and provisioned to connect to SIGTRAN. Ensure that IP addresses and port numbers to SIGTRAN are provisioned correctly in the client Ss7IpIf components. Severity Minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1600 - Sigtran SigConn Down alarm (GPRS/UMTS) 189 Copyright 20042007 Nortel Networks
7068_1600 - Sigtran SigConn Down alarm (GPRS/UMTS)

Alarm 7068 1600 Component SigtranAsp/<a> Siwf Sfa SigIpIf/ Legend <a>, = component instance identifiers Details This alarm is raised when the SCIP-level connection (heartbeating) fails between the SS7-IP Gateway (SIG) Forwarding Agent (SFA) and an HP-SIG. It is also raised when the initial attempt to connect to the HP-SIG upon SFA startup fails. Any egress (SGSN outgoing) messages that might be routed to the HP-SIG represented by this SigIpIf component will be discarded for the duration of this alarm. This alarm is cleared when a heartbeat is established with the HP-SIG over an active connection, or the SigIpIf/ component is removed. Probable Cause lossOfSignalCause Type communications Remedial action Verify that the status of the HP-SIG in question is active. Verify IP connectivity and VR provisioning. Severity Minor Status set/clear
SGSN5.0
7068_1601 - Sigtran SigConn Congested alarm (GPRS/UMTS)

Alarm 7068 1601 Component SigtranAsp/<a> Siwf Sfa SigIpIf/ Legend <a>, = component instance identifiers Details This alarm is raised when the outgoing TCP buffers for the HP-SIG connection represented by this component are higher than the threshold for congestion onset. A higher than expected traffic rate or an unusually lossy/noisy IP connection can cause this condition. Any traffic routed to this HP-SIG may be discarded. To prevent the alarm being set/cleared unnecessairly, the alarm will only be cleared when the buffer utilization falls below the congestion abatement threshold; indicating that the HP-SIG is processing traffic at (or above) the rate it is being sent. Probable Cause congestion Type qualityOfService Remedial action If traffic rate is within engineered limits and all subsystems are functional, then the system has likely reached processing capacity. Consider routing more traffic through the SIGTRAN interface. Severity Minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1602 - Sigtran TcpConn Dropped alarm (GPRS/UMTS) 191 Copyright 20042007 Nortel Networks
7068_1602 - Sigtran TcpConn Dropped alarm (GPRS/UMTS)

Alarm 7068 1602 Component SigtranAsp/<a> Legend <a>, = component instance identifiers Details This message alarm is raised when the SigtranAsp detects that a TCP connection has been unexpectedly closed prior to client deregistration procedures occuring. This may be caused by a reset on a client card, or failure in the internal passport IP routing. Probable Cause commSubsystemFailure Type communications Remedial action Check for other SGSN events at the time of the message alarm. Severity Major Status Message
SGSN5.0
7068_1603 - Sigtran Asp Initialization Failure alarm (GPRS/UMTS)

Alarm 7068 1603 Component SigtranAsp/<a> Legend <a> = component instance identifier Details The SigtranAsp represented by this component has failed to initialize and it not ready to support traffic. This alarm will be cleared when the SigtranAsp initializes successfully, or is reset. Probable Cause outOfMemoryCause Type processing Remedial action Referencing the reasons in the alarm text, verify that the SigtranAsp provisioning is within engineered limits and reset the SigtranAsp card. Severity Critical Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1604 - Ss7IpIf NoticeInd Congestion alarm (GPRS/UMTS) 193 Copyright 20042007 Nortel Networks
7068_1604 - Ss7IpIf NoticeInd Congestion alarm (GPRS/UMTS)

Alarm 7068 1604 Component Tcap/<a> Ss7IpIf/ Gsc/<c> Bssap Ss7IpIf/<d> Legend <a>, , <c>, <d> = component instance identifiers Details The Notice Indication Congestion alarm is raised by Ss7IpIf component when the rate of Notice Indication messages with a cause of Network Congestion for a subsystem has reached the rate of which the traffic is re-routed to load balance over the remaining SigtranAsp components. This can be caused due to a SigtranAsp experiencing local congestion. The alarm is cleared when traffic for all subsystems is re-routed to the congested SigtranAsp. Note: To identify which subsystem has been re-routed, check the operational attribute subsystemUsageStatus under the Tcap Ss7IpIf components on the SGSN. Probable Cause congestionCause Type qualityOfService Remedial action No action needs to be taken. Severity Minor Status set/clear
SGSN5.0
7068_1605 - Too Many GSDs Alarm (GPRS/UMTS)

Alarm 7068 1605 Component Sgsn Legend N/A Details The GSD PTMSI Block Manager (PBM) Block Routing Table (BRT) can support up to a maximum of 24 GSD card instances. When the PBM BRT receives a GSD PBM BRT resource registration request for a new previously unknown GSD instance, the current number of GSD instances registered is checked. If it is already 24, this GSD PBM BRT Resource Congestion Alarm with major severity is generated. A clear alarm is raised when the system detects that the PBM BRT GSD resource congestion condition has abated. The GSD application that is attempting to register for PBM resources will not be given any new PBM blocks (resource) and its Nodal Manager registration is denied. This makes the application unavailable for any mobile traffic. The application will continue to retry its Nodal Manager registration until it succeeds or the Gsd component is deleted. Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action Remove GSD instances which are already added and no longer needed. If the GSD instances listed in the alarm have been de-provisioned then contact next level of support for details to recover from potential memory leaks using the manual recovery procedure. Severity Major Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1606 - Too Many GSCs Alarm (GPRS/UMTS) 195 Copyright 20042007 Nortel Networks
7068_1606 - Too Many GSCs Alarm (GPRS/UMTS)

Alarm 7068 1606 Component Sgsn Legend N/A Details The GSC PTMSI Block Manager (PBM) Block Routing Table (BRT) can support up to a maximum of 16 GSC card instances. When the PBM BRT receives a GSC PBM BRT resource registration request for a new previously unknown GSC instance, the current number of GSC instances registered is checked. If it is already 16, this GSC PBM BRT Resource Congestion Alarm with major severity is generated. A clear alarm is raised when the system detects that the PBM BRT GSC resource congestion condition has abated The GSC application that is attempting to register for PBM resources will not be given any new PBM blocks (resource) and its Nodal Manager registration is denied. This makes the application unavailable for any mobile traffic. The application will continue to retry its Nodal Manager registration until it succeeds or the Gsc component is deleted. Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action Remove GSC instances which are already added and no longer needed. If the GSC instances listed in the alarm have been de-provisioned then contact next level of support for details to recover from potential memory leaks using the manual recovery procedure. Severity Major Status set/clear
SGSN5.0
7068_1607 - UMTS Attach Success Rate Threshold Alarm (UMTS)

Alarm 7068 1607 Component Gsc/<x> Legend <x> = component instance identifier Details This alarm is issued with major or minor severity depending on the current state of the alarm and the relationship between the calculated attach success rate for UMTS subscribers and the provisioned thresholds. The attach success rate formula is defined in the SGSN Monitoring Guide, NTP 411-8111-050 for UMTS. The attach success rate for UMTS subscribers is calculated over data from the past 15 minutes (default), and is updated every 3 minutes (default). If fewer than 100 attempts (default) are made, then the success rate for UMTS subscribers is not updated, since insufficient information is available for making a decision on the status of the node. Alarms are generated when the success rate for UMTS subscribers crosses the thresholds as follows. If the calculated success rate for UMTS subscribers rises above the clear threshold (98% default) then a clear alarm is issued (or the alarm remains inactive). If the calculated success rate for UMTS subscribers falls below or rises above the minor threshold (95% default), while staying between the major and clear thresholds, then a minor alarm is issued (or remains active). If the calculated success rate for UMTS subscribers falls below the major threshold (90% default) then a major alarm is issued (or remains active). Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action Examine the GMM attach failure counters (in the Gsc Gmm component hierarchy) and verify the health of the network. Severity major/minor Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1608 - UMTS Activation Success Rate Threshold Alarm (UMTS) 197 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1608 - UMTS Activation Success Rate Threshold Alarm (UMTS)2

Alarm 7068 1608 Component Gsc/<x> Legend <x> = component instance identifier Details This alarm is issued with major or minor severity depending on the current state of the alarm and the relationship between the calculated activation success rate for UMTS subscribers and the provisioned thresholds. The activation success rate formula is defined in the SGSN Monitoring Guide, NTP 411-8111-050 for UMTS. The activation success rate for UMTS subscribers is calculated over data from the past 15 minutes (default), and is updated every 3 minutes (default). If fewer than 100 attempts (default) are made, then the success rate for UMTS subscribers is not updated, since insufficient information is available for making a decision on the status of the node. Alarms are generated when the success rate for UMTS subscribers crosses the thresholds as follows. If the calculated success rate for UMTS subscribers rises above the clear threshold (98% default) then a clear alarm is issued (or the alarm remains inactive). If the calculated success rate for UMTS subscribers falls below or rises above the minor threshold (95% default), while staying between the major and clear thresholds, then a minor alarm is issued (or remains active). If the calculated success rate for UMTS subscribers falls below the major threshold (90% default) then a major alarm is issued (or remains active). Note: If this alarm is generated from a migration active state, it will be converted to a warning message alarm with index 7000_0034 against the Prov Migration component. If this alarm is generated from a standby state, it will be converted to a warning message alarm with index 7012_0300 against the Shelf Card/x SparedServices component. In both cases, the original alarm is embedded as text in the comment field of the new alarm. Probable Cause thresholdCrossedCause_c Type qualityOfServiceType_c Remedial action Examine the SM activation failure counters (in the Gsc Sm component hierarchy) and verify the health of the network. Severity major/minor Status set/clear
SGSN5.0
7068_1610 - GIPS Unavailable Alarm (GPRS)

Alarm 7068 1610 Component SgGtl/<x> Legend <x> = component instance identifier Details This alarm is raised by the SgGtl component when the IP server instance for the SgGtl is no longer available. When this alarm is raised against SgGtl, it indicates that the SgGtl receives an error indication message from the IP server. The possible causes could be either the virtual router has been locked or the IP server has been reset. This alarm is cleared upon receiving a message from IP server that indicates it becomes available. Probable Cause underlyingResourceUnavailableCause_c Type processingType_c Remedial action Verify that IP Server is functioning properly after the reset. Verify the Virtual Router is not locked. Severity critical Status set/clear
411-5221-500
Standard
04.05
January 2007
7068_1612 - Potential Ethernet Port Issue On 2pGPDsk Card (GPRS) 199 Nortel Networks Confidential Copyright 20042007 Nortel Networks
7068_1612 - Potential Ethernet Port Issue On 2pGPDsk Card (GPRS)2

Alarm 7068 1612 Component Lp/<x> Eth100/<x> Legend <x> = component instance identifier Details This alarm is generated when the 2pGPDsk card with the following release indicators is using the Eth100 component: 40, 54, 69, 70, or A40. These release indicators can also be checked by displaying the productCode attribute under the Shelf Card component. This alarm is introduced in GPRS 6.0 by patch baseQ01222019. Probable Cause equipmentFailureCause_c Type equipmentType_c Remedial action Contact Nortel next level of support Severity critical Status set
SGSN5.0
7068_1996 - GMM Context Resources Low Alarm (GPRS; Obsolete) 2

Alarm 7068 1996 Component Gsc/<x> Legend <x> = component instance identifier Details The GMM Context Resources Low Alarm is raised when the number of resources in use exceeds 80% of the resources allocated. The alarm will be raised when any of the following resources are low: Primary Contexts Attach Contexts Rau Contexts User Requested Security Contexts Security Contexts Sus Res Contexts Reset Contexts Paging Contexts Assignment Contexts This alarm is cleared when all of the contexts in use falls below 75% of the resources allocated. Probable Cause atOrNearCapacityCause_c Type processingType_c Remedial action None. Severity major Status set/clear
411-5221-500
Standard
04.05
January 2007
Adding Minor SGSN Alarms 201 Copyright 20042007 Nortel Networks
Adding SGSN Alarms

Adding Minor SGSN Alarms
A
2
Note: Developers are encouraged to use the DCS API directly. The following discussion of a wireless fault management object is historical.
Minor alarms in UMTS can be added by any developer. The perceived severity is an OSI defined field. For the UMTS Fault Management Objects, the defined severities have the following meanings indeterminate - Not Used critical - Immediate corrective action is required. The resource is completely disabled and service is affected. Not Used major - Urgent corrective action is required. The resource is severely disabled and service is affected. Reserved for alarms that cause the OSI State to change. minor - Corrective action should be taken to prevent more serious fault. The resource is partially disabled and service may be affected. Should be used for all alarms not affecting OSI State. warning - Not Used cleared - Used automatically when calling clrAlarm or clrMinorAlarm_v. Reference MD-1995-0066-04 for a complete discussion of perceived alarm severity.
Steps to add minor alarms. The alarm number The alarm number is an eight-digit BCD value which consists of two parts. The first part of the alarm number is the index group. It is defined in the gblAlarmNtpIndex.h base file. For GPRS and UMTS Sgsn, the index group is indexGroupSgsn_c, which has the assigned value of 7068. The second part of the alarm number is the value from the sgsnAlarmNtpIndex.h file. This is a local file that we use to assign values for individual alarms in the Sgsn index group. To select an alarm number, take the next sequential entry from the appropriate range [1000 - 1499, for GPRS SGSN; 1500 - 1999 for UMTS SGSN] For alarms that are used in both, chose either range. Note: The values in the gbl and sgsn AlarmNtpIndex.h files are shown as hexadecimal, i.e. 0x7068 for the indexGroupSgsn_c, and SGSN_INDEX + 0x1499 for the specific sgsnPatchAlarm5 (where SGSN_INDEX = 0x7068 << 16). Note: PLEASE ENTER EACH ALARM NUMBER IN ASCENDING NUMERICAL ORDER!!!!!!
GSM UMTS Packet Core Network Nortel SGSN Alarms Reference Manual SGSN5.0
202 Adding SGSN Alarms Nortel Networks Confidential
Documenting the alarm Each alarm is required to be documented in two places. First, Ottawa keeps an NTP Alarm document which consists of alarm documentation across all passport use. Sgsn alarm documentation is a subset. Secondly, each Sgsn alarm is documented in this document. The Ottawa documentation is entered and submitted online at http:// ntponline/PassportForms/Alarms.html. The fields in the online form are the same and have the same meaning as the fields shown in section 2.3 above. For the minor alarms, some fields have been predetermined in the code. They are as follows: alarm number - 70681xxx [selected from sgsnAlarmNtpIndex.h] component name - Usc/<x>, Usd/<x>,... severity - minor status - Set, Clr, Set/Clr legend - <x> = instance identifier of Component probable cause - softwareProgramError type - processingType details - a description of the conditions that cause the alarm to be set, cleared, or set/clr remedial action - describes the steps the operator should take in response to the alarm.
Implementing the alarm There is a base Fault Management class, SgsnFaultMgmt. The setMinorAlarm_v and clrMinorAlarm_v methods are implemented there. Any developer wishing to implement a minor alarm can either instantiate the base class, or inherit through the UscFaultMgmt or UsdFaultMgmt classes. NOTE - these minor alarm methods are NOT DME safe, they should only be called from PEV processes. The API for both methods is the same, the use of these methods are: NAME: setMinorAlarm_v IMPLEMENTATION NOTES: This method is used to generate a minor SET alarm. This alarm is reported to CAS on the CP and to the Network monitor function. This type of alarm should be used in code that does not impact the OSI State of the component, or for components that do not have OSI State to alert the operator of conditions which require action in the near term. void SgsnFaultMgmt::setMinorAlarm_v
411-5221-500 Standard 04.05 January 2007
Adding Major Alarms 203 Copyright 20042007 Nortel Networks
(SgsnAlarmType ntpIndex, char* msg, char* fileName, Uint32 lineNumber, ComponentName* myCompName) where: ntpIndex is the full alarm number msg is the comments to be printed in the alarm fileName is from the __FILE__ macro lineNumber is from the __LINE__ macro myCompName is the component name of the component or subcomponent generating the alarm. [the related component field of the alarm will always show the corresponding LP]
Adding Major Alarms
Since major alarms impact the OSI State of the component, all major alarms should be implemented via a customized Fault Management object for that component. Please refer to the UscFaultMgmt and UsdFaultMgmt code for implementation examples.
SGSN5.0
204 Adding SGSN Alarms Nortel Networks Confidential
411-5221-500
Standard
04.05
January 2007
Adding Major Alarms 205 Copyright 20042007 Nortel Networks
MDM Alarm Screening Macro
This appendix provides information related to the setup of an MDM trigger for improved visibility of selected alarms. For more information refer to the MDM 12.5 Customization Administrator Guide (NTP 241-6001-301). This macro will bring up a warning window and ring a bell upon receiving specified kinds of alarms, and log the alarm to a file. The pop up window will stand for 10 seconds (configurable) then disappear. You can stop this screening anytime you want without affecting normal MDM logging. Example of starting a trigger:
1. 2.
Go to /opt/MagellanNMS/cfg/macros/nms Run: AlarmTrigger -pfault "7068" -cmd "/opt/MagellanNMS/cfg/macros/user/screen". The preceding command used 7068 which contains the first four digits of NTP indices assigned to SGSN alarms. The word in bold is the screening option (for more see options below), the word in italics is the script (for contents of that script see below) that generates a new log. The final log is "screenedAlarm" under the current directory. # Synopsis : AlarmTrigger [-fault "<faultcode>"]* # # # # # # # # # # Example macro: $ cat /opt/MagellanNMS/cfg/macros/user/screen /opt/MagellanNMS/bin/xmsg "SGSN Alarm! Go check log file screenedAlarm" -title AlarmWarning -pixmap /usr/dt/include/bitmaps/ xm_warning -delay 10 -bell tail -7 /opt/MagellanNMS/data/log/MDMalarmtest >> screenedAlarm
GSM UMTS Packet Core Network Nortel SGSN Alarms Reference Manual SGSN5.0
[-pfault "<faultcode pattern (post filtered)>"]* [-pref "<component prefix>"]* [-comp "<component>"]* [-pcomp "<component pattern (post filtered)>"]* [-cfile "<component pattern file (post filtered)>"] [-event set|clear|message]* [-sev critical|major|minor|warning|cleared|indeterminate]* [-serv <GMDR service name>] [-host <GMDR hostname>] [-or (alternative filters)]*
206 MDM Alarm Screening Macro Nortel Networks Confidential
411-5221-500
Standard
04.05
January 2007
Scope 207 Copyright 20042007 Nortel Networks
MDM Alarm Injection Script (Obsolete)C

Scope 2
This appendix is provided for historical reference only. The alarm injection script is obsoleted in G6001CF and U4002CF with the CEM pass-through list maintained by the CEM team. The SGSN list that provides input to the CEM team is available here: http://clearcase.us.nortel.com/cgi-bin/ searchDocVob.cgi?str=alarm_cem_passthru.txt This search may return multiple results, so be sure to select the link associated with the appropriate release.
Overview
2
Some of the message alarms being generated by the SGSN/MG and base Passport need greater visibility to the operator and have been requested to be reported in NSP, CEM and MDM GUIs as set/clear alarms. To meet this requirement on a temporary basis without SGSN/MG recompile, a script on the MDM Main Server is introduced that intercepts and converts them into Set alarms on a per index basis. Alarm indices that are injected using this script are candidates for implementation as set alarms on the SGSN/MG in future releases of the product, and typically imply the need for OSI state on the affected component. If the passport does not emit a clear alarm for a particular index, the injection of the message alarm as a set alarm by this script implies that clearing must occur manually at the MDM/NSP.
Implementation
Fragments of the alarm script are shown below. To promote an alarm index to Set/Clear, add corresponding lines using the approach shown in bold type. The first two lines are the form of comments in the revision table, listing the version, author, date of change, and a description of the change. The convention here reflects Nortel Networks document control versioning.
# # PC02.04 Bryon Ford 03/17/03 Add Alarms 7007 1000, 7068 1523, 7068 1499
The next three document the new alarm index in comment form; here the version from the revision table is included parenthetically where applicable.
# 7068 1496 gscOverload (PC02.03) # 7068 1499 BVCI Alarms (PC02.04) # 7068 1518 ssfAnScpLinkFailed
SGSN5.0
208 MDM Alarm Injection Script (Obsolete) Nortel Networks Confidential
The last three lines illustrate the actual alarm index added to the alarm sieve. This is done by copying an existing line and changing the index to match the new alarm.
_attr: eventFilter SS faultCode EQ S 70681496 _attr: eventFilter SS faultCode EQ S 70681499 _attr: eventFilter SS faultCode EQ S 70681518
Please observe the convention of adding indexes in ascending order, and document the meaning of the alarm in both the revision comment section as well as the alarm comments.
Location of Alarm Injection Script

This URL may return multiple results; please choose the link appropriate to the release of interest. For example, GPRS05 is supported by the script currently located in: http://clearcase.us.nortel.com/wlsrchdoc/platform/passport/sgsn/ umts3_gprs5/function/system/common/oam/
URL: http://clearcase.us.nortel.com/cgi-bin/searchDocVob.cgi?str=Alarm_inj
411-5221-500
Standard
04.05
January 2007
Location of Alarm Injection Script 209 Copyright 20042007 Nortel Networks
Alarm Change Summary
The following sections summarize changes made in alarm indexes by product release. These sections are arranged chronologically and are updated prior to the final compilation of the load.
SGSN5.0
210 Alarm Change Summary Nortel Networks Confidential
Alarms Changed in GPRS4 (G3016AG to G4003AK)

Alarm Name GSC Initialization Done GSD (Memory Preallocation) Initialization Done GSC Initialization Failed GSD Initialization Failed Maximum Number of BVCs Per NSE Exceeded GSD Downlink Buffer Component Add Failed GSD Hardware-Assist Failure MapStack Out of SGSN MSC Subsystem Resources TcapStack Out of SGSN CAP Subsystem Resources Max MAP Client Dialogues Exceeded SGSN MAP Subsystem Bind Failed SGSN MSC Subsystem Bind Failed SGSN CAP Subsystem Bind Failed SSF SCP Communication Failure SSF Max Camel Dialogues Exceeded MAP Notice Indication Display Alarm ID 7068_1014 7068_1015 7068_1018 7068_1019 7068_1020 7068_1021 7068_1022 7068_1509 7068_1510 7068_1511 7068_1515 7068_1516 7068_1517 7068_1518 7068_1519 7068_1520 Added/ Obsoleted Obsoleted Obsoleted Added Added Added Added Added Added Added Added Added Added Added Added Added Added
Alarms Changed in GPRS5 (G4003AK to G5003AK)

Alarm Name SAS Disk Almost Full Secondary CGF Link Failure GSD Memory Exhausted Memory Near Exhaustion Loss of connection with SIG Unavailable BVCs Has Exceeded the Threshold Primary CGF Link Up Alarm ID 7068_1000 7068_1004 7068_1008 7068_1010 7068_1013 7068_1023 7068_1200 Added/ Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Added Obsoleted
411-5221-500
Standard
04.05
January 2007
Alarms Changed in GPRS5 (G4003AK to G5003AK) 211 Copyright 20042007 Nortel Networks
Alarm Name Secondary CGF Link Up Max SGSN MAP Invokes Exceeded GSC CPU Overload Loss of Communication with the DnsAgent Servers Loss of Connection with the SIG LIAF out of Resources LIAF Maximum Subscribers Reached LIAF Initialization Failure Loss of Communication with LIG ADMF Loss of Communication with LIG DF Server Invalid PDP Context Received Loss of Redundancy with the DnsAgent Servers
Alarm ID 7068_1201 7068_1512 7068_1521 7068_1522 7068_1523 7068_1524 7068_1525 7068_1526 7068_1527 7068_1528 7068_1529 7068_1530
Added/ Obsoleted Obsoleted Obsoleted Added Added Added Added Added Added Added Added Added Added
SGSN5.0
Alarms Changed in GPRS5 Mtce. (G5003AK to G5025AW)

Alarm Name GSC/GSD SVC Audit Failed Nodal Manager Critical Component Missing Nodal Manager Noncritical Component Missing I/RAU Requests Rejected Attach Reject Cause Code Reporting Sgsn-Initiated Session Deactivations Cause Code Reporting Mobile-Originated SMS Overload Mobile-Terminated SMS Overload HLR Reset Triggered UGL Overload GSC IMSI Diagnostic MapStack Overload GSC Overload PTP BVC Mismatched States SSF SCP Communication Failure Attach Requests Rejected or not Received PDP Activations Requests Rejected or not Received SS7 SIG Problem SCCP Notice Indication Throttling HLR Reset Received TCAP Mobile-Terminated FSM Overload Gsc GtpM Keep-Alive GMM Context Resources Low Alarm ID 7068_1024 7068_1025 7068_1026 7068_1027 7068_1028 7068_1029 7068_1030 7068_1031 7068_1032 7068_1034 7068_1495 7068_1496 7068_1499 7068_1518 7068_1531 7068_1532 7068_1533 7068_1534 7068_1535 7068_1536 7068_1540 7068_1996 Added/ Obsoleted Added Added Added Added Added Added Added Added Added Added Added Added Added Obsoleted Added Added Added Added Added Added Added Obsoleted
Alarms Changed in GPRS6 (G5025AW-G6001CF)

Alarm Name Maximum Number of BVCs Per NSE Exceeded Alarm ID 7068_1020 Added/ Obsoleted Obsoleted
411-5221-500
Standard
04.05
January 2007
Alarms Changed in GPRS6 (G5025AW-G6001CF) 213 Copyright 20042007 Nortel Networks
Alarm Name I/RAU Requests Rejected Attach Reject Cause Code Reporting Sgsn-Initiated Session Deactivations Cause Code Reporting NSVC Unavailable BSSAP MS-Activity-Indication Overload BSSAP Location Update Request Overload Maximum Header Compression Memory Usage FrameBuf Congestion GSD Max Allocated LLC-ABM Data Entities Reached GSD Max Allocated Session Entities Reached Signaling BVC Reset Max BVCs per NSE Reached GSC/USC Overload Max SGSN MAP Invokes Exceeded Max MSC MAP invokes Exceeded Max CAP invokes Exceeded SSF SCP Communication Failure MAP Notice Indication Display Loss of Communication with the DnsAgent Servers Loss of Redundancy with the DnsAgent Servers Attach Requests Rejected or not Received PDP Activations Requests Rejected or not Received SS7 SIG Problem SCCP Notice Indication Throttling Registration with IP Server Failure GTP Path Usage GTP Transaction High Usage LCS SLPP Out of Resources
Alarm ID 7068_1027 7068_1028 7068_1029 7068_1033 7068_1035 7068_1036 7068_1037 7068_1038 7068_1039 7068_1040 7068_1041 7068_1043 7068_1496 7068_1512 7068_1513 7068_1514 7068_1518 7068_1520 7068_1522 7068_1530 7068_1531 7068_1532 7068_1533 7068_1534 7068_1537 7068_1538 7068_1539 7068_1541
Added/ Obsoleted Obsoleted Obsoleted Obsoleted Added Added Added Added Added Added Added Added Added Obsoleted Obsoleted Obsoleted Obsoleted Not Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Added Added Added Added
SGSN5.0
Alarm Name LCS Client Address Out of Resources LCS Context Out of Resources Attach Overload Inter-SGSN RAU Overload Mobile-Terminated SMS TCAP Overload SAI Overload Alarm Non-SAI Overload SSF InitialDPGPRS Overload MAP Client Registration Failure Registration Failure Notice Indication Failure MAP Client IP Network Error Sgsn Audit Memory Corruption Ss7IpIf Noisy Link Nodal Manager Call Released Nodal Manager Resource Failure Nodal Manager Registration Nodal Manager Outgoing Call Request Failure Nodal Manager Incoming Call Timeout Nodal Manager Invalid Master SAS Fail to Send Message to SC SAS Not Ready for Switchover NMA Application Info Report Corrupt MapClient Loss of Communication with MapStack Loss of Communication with TcapStack SNR Audit Memory Corruption SC Redundancy Sync Loss Switchover During Checkpointing
Alarm ID 7068_1542 7068_1543 7068_1544 7068_1545 7068_1546 7068_1547 7068_1548 7068_1549 7068_1550 7068_1551 7068_1552 7068_1553 7068_1554 7068_1555 7068_1557 7068_1558 7068_1559 7068_1560 7068_1561 7068_1562 7068_1564 7068_1566 7068_1567 7068_1568 7068_1569 7068_1570 7068_1572 7068_1573
Added/ Obsoleted Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added
411-5221-500
Standard
04.05
January 2007
Alarms Changed in GPRS6 (G5025AW-G6001CF) 215 Copyright 20042007 Nortel Networks
Alarm Name Attach Success Rate Threshold Activation Success Rate Threshold SAS Memory Pool High Usage SAS Card Memory High Usage Loss of Communication with the DNS Server Internal Diagnostic SC Resource Exhaustion Potential Ethernet Port Issue On 2pGPDsk Card
Alarm ID 7068_1574 7068_1575 7068_1576 7068_1577 7068_1578 7068_1580 7068_1581 7068_1612
Added/ Obsoleted Added Added Added Added Added Added Added Added (patch)
SGSN5.0
Alarms Changed in UMTS3 (U2003AK to U3001AO)

Alarm Name Layer 2 Peer Disconnect Secondary CGF Link Failure GSD Memory Exhausted Memory Near Exhaustion Loss of connection with SIG Unavailable BVCs Has Exceeded the Threshold Primary CGF Link Up Secondary CGF Link Up Max SGSN MAP Invokes Exceeded GSC or USC CPU Overload Alarm Loss of Communication with the DnsAgent Servers Alarm Loss of Connection with the SIG Alarm LIAF out of Resources Alarm LIAF Maximum Subscribers Reached Alarm LIAF Initialization Failure Alarm Loss of Communication with LIG ADMF Alarm Loss of Communication with LIG DF Server Alarm Invalid PDP Context Received Alarm Loss of Redundancy with the DnsAgent Servers Alarm ID 7066_0301 7068_1004 7068_1008 7068_1010 7068_1013 7068_1023 7068_1200 7068_1201 7068_1512 7068_1521 7068_1522 7068_1523 7068_1524 7068_1525 7068_1526 7068_1527 7068_1528 7068_1529 7068_1530 Added/ Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Added Obsoleted Obsoleted Obsoleted Added Added Added Added Added Added Added Added Added Added
Alarms Changed in UMTS3 Mtce. (U3001AO to U3029AW)

Alarm Name SVC Audit Failed Nodal Manager Critical Component Missing Nodal Manager Noncritical Component Missing I/RAU Requests Rejected Alarm ID 7068_1024 7068_1025 7068_1026 7068_1027 Added/ Obsoleted Added Added Added Added
411-5221-500
Standard
04.05
January 2007
Alarms Changed in UMTS3 Mtce. (U3001AO to U3029AW) 217 Copyright 20042007 Nortel Networks
Alarm Name Attach Reject Cause Code Reporting Sgsn-Initiated Session Deactivations Cause Code Reporting Mobile-Originated SMS Overload Mobile-Terminated SMS Overload HLR Reset Triggered UGL Overload USC IMSI Diagnostic MapStack Overload USC Message Overload Alarm PTP BVC Mismatched States SSF SCP Communication Failure Attach Requests Rejected or not Received PDP Activations Requests Rejected or not Received SS7 SIG Problem SCCP Notice Indication Throttling HLR Reset Received TCAP Mobile-Terminated FSM Overload GTP Path Failure Alarm Mobile Context Mismatch In GMM Alarm
Alarm ID 7068_1028 7068_1029 7068_1030 7068_1031 7068_1032 7068_1034 7068_1495 7068_1496 7068_1499 7068_1518 7068_1531 7068_1532 7068_1533 7068_1534 7068_1535 7068_1536 7068_1540 7068_1556
Added/ Obsoleted Added Added Added Added Added Added Added Added Added Obsoleted Added Added Added Added Added Added Added Added
SGSN5.0
Alarms Changed in UMTS4 (U3029AW to U4002CF)

Alarm Name TDM Link Failure Media Gateway Heartbeat MgIf Claim Failure Tdmc Claim Failure Q.2630 Blocking Failure Vmg High Resource Usage I/RAU Requests Rejected Attach Reject Cause Code Reporting Sgsn-Initiated Session Deactivations Cause Code Reporting BSSAP MS-Activity-Indication Overload BSSAP Location Update Request Overload Maximum Header Compression Memory Usage GSC or USC Overload Max SGSN MAP Invokes Exceeded Max MSC MAP invokes Exceeded Max CAP invokes Exceeded SSF SCP Communication Failure MAP Notice Indication Display Loss of Communication with the DnsAgent Servers Loss of Redundancy with the DnsAgent Servers Attach Requests Rejected or not Received PDP Activations Requests Rejected or not Received SS7 SIG Problem SCCP Notice Indication Throttling Registration with IP Server Failure GTP Path Usage GTP Transaction High Usage Alarm ID 7056_1300 7067_1000 7067_1001 7067_1002 7067_1003 7067_1004 7068_1027 7068_1028 7068_1029 7068_1035 7068_1036 7068_1037 7068_1496 7068_1512 7068_1513 7068_1514 7068_1518 7068_1520 7068_1522 7068_1530 7068_1531 7068_1532 7068_1533 7068_1534 7068_1537 7068_1538 7068_1539 Added/ Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Added Added Added Obsoleted Obsoleted Obsoleted Obsoleted Not Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Added Added Added
411-5221-500
Standard
04.05
January 2007
Alarms Changed in UMTS4 (U3029AW to U4002CF) 219 Copyright 20042007 Nortel Networks
Alarm Name LCS SLPP Out of Resources LCS Client Address Out of Resources LCS Context Out of Resources Attach Overload Inter-SGSN RAU Overload Mobile-Terminated SMS TCAP Overload SAI Overload Alarm Non-SAI Overload SSF InitialDPGPRS Overload MAP Client Registration Failure Registration Failure Notice Indication Failure MAP Client IP Network Error Sgsn Audit Memory Corruption Ss7IpIf Noisy Link Nodal Manager Call Released Nodal Manager Resource Failure Nodal Manager Registration Nodal Manager Outgoing Call Request Failure Nodal Manager Incoming Call Timeout Nodal Manager Invalid Master SAS Fail to Send Message to SC SAS Not Ready for Switchover NMA Application Info Report Corrupt MapClient Loss of Communication with MapStack Loss of Communication with TcapStack SNR Audit Memory Corruption SC Redundancy Sync Loss
Alarm ID 7068_1541 7068_1542 7068_1543 7068_1544 7068_1545 7068_1546 7068_1547 7068_1548 7068_1549 7068_1550 7068_1551 7068_1552 7068_1553 7068_1554 7068_1555 7068_1557 7068_1558 7068_1559 7068_1560 7068_1561 7068_1562 7068_1564 7068_1566 7068_1567 7068_1568 7068_1569 7068_1570 7068_1572
Added/ Obsoleted Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added
SGSN5.0
Alarm Name Switchover During Checkpointing Attach Success Rate Threshold Activation Success Rate Threshold SAS Memory Pool High Usage SAS Card Memory High Usage Loss of Communication with the DNS Server Internal Diagnostic SC Resource Exhaustion
Alarm ID 7068_1573 7068_1574 7068_1575 7068_1576 7068_1577 7068_1578 7068_1580 7068_1581
Added/ Obsoleted Added Added Added Added Added Added Added Added
411-5221-500
Standard
04.05
January 2007
Alarms Changed in SGSN5.0 (G6001CF, U4002CF to LATEST) 221 Copyright 20042007 Nortel Networks
Alarms Changed in SGSN5.0 (G6001CF, U4002CF to LATEST)

Alarm Name Alarm ID Added/ Obsoleted/ Modified Modified Modified Modified Modified Modified Modified Added Added Added Added Added Added Obsoleted Obsoleted Obsoleted Obsoleted Obsoleted Modified Modified Changed Modified Modified Obsoleted Modified Modified Modified
Subscriber Count Overload Alarm Routing Area ID Missing Alarm SVC Audit Failed Alarm Nodal Manager Critical Component Missing Nodal Manager Noncritical Component Missing GSC or USC IMSI Diagnostic Alarm GbIP Data NS-VC Unavailable Alarm GbIP Signaling NS-VC Unavailable Alarm GbIP Dynamic Configuration Failure Alarm GbIP Dynamic Configuration Attempts while using Static Configuration Alarm NRI Lock Constraint Alarm All NRIs Locked Message Alarm Context Memory Exhausted Alarm GMM Max Attaches Exceeded Alarm SM Max Active Sessions Exceeded Alarm Initialization Failure Alarm GSC or USC CPU Overload Alarm Registration with IP Server Failure Alarm Attach Overload Alarm InterSGSN RAU Overload Alarm Ss7IpIf Reg Failure alarm Ss7IpIf Ni Failure alarm Mobile Context Mismatch In GMM Alarm GPRS Attach Success Rate Threshold GPRS Activation Success Rate Threshold SC Resource Exhaustion
7068_1006 7068_1011 7068_1024 7068_1025 7068_1026 7068_1034 7068_1044 7068_1045 7068_1046 7068_1047 7068_1202 7068_1203 7068_1500 7068_1501 7068_1502 7068_1507 7068_1521 7068_1537 7068_1544 7068_1545 7068_1551 7068_1552 7068_1556 7068_1574 7068_1575 7068_1581
SGSN5.0
Alarm Name
Alarm ID
Added/ Obsoleted/ Modified Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Added Obsoleted (for GPRS only)
Sigtran Remote Address Inactive alarm Sigtran No Destination Routable alarm Sigtran No SG Available alarm Sigtran PeerProcess Not Active alarm Sigtran Sgsn PeerProcess Blocked alarm Sigtran PeerProcess Congested alarm Sigtran Destination Unroutable alarm Sigtran Destination Restricted alarm Sigtran Destination Congested alarm Sigtran Unauthorized Associate alarm Sigtran Remote Subsystem Unavailable alarm Sigtran Local Subsystem Unavailable alarm Sigtran Unknown Destination alarm Sigtran TcpConn Congested alarm Sigtran No Scip Clients Registered alarm Sigtran SigConn Down alarm Sigtran SigConn Congested alarm Sigtran TcpConn Dropped alarm Sigtran Asp Initialization Failure alarm Ss7IpIf NoticeInd Congestion alarm Too Many GSDs or USDs Alarm Too Many GSCs Alarm UMTS Attach Success Rate Threshold UMTS Activation Success Rate Threshold GIPS Unavailable Alarm GSD orUSD Out of Resources Alarm
7068_1585 7068_1586 7068_1587 7068_1588 7068_1589 7068_1590 7068_1591 7068_1592 7068_1593 7068_1594 7068_1595 7068_1596 7068_1597 7068_1598 7068_1599 7068_1600 7068_1601 7068_1602 7068_1603 7068_1604 7068_1605 7068_1606 7068_1607 7068_1608 7068_1610 7068_1503
411-5221-500
Standard
04.05
January 2007
test
Family Product Manual Contacts Copyright Confidentiality Legal
Nortel SGSN
To order documentation from Nortel Global Wireless Knowledge Services, call (1) (877) 662-5669 To report a problem in this document, call (1) (877) 662-5669 or send e-mail from the Nortel Customer Training & Documentation World Wide Web site at http://www.nortel.com/td Copyright 20042007 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein. Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. NORTEL, NORTEL NETWORKS, the globemark design, and the NORTEL corporate logo are trademarks of Nortel.GSM is a trademark of GSM MOU Association. Trademarks are acknowledged with an asterisk (*) at their first appearance in the document. Document number: 411-5221-500 Product release: SGSN5.0 Document version: Standard 04.05 Date: January 2007 Originated in the United States of America

Nortel SGSN Alarms Reference Manual

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Nortel SGSN Alarms Reference Manual

Cargado por

Copyright:

Formatos disponibles

411-5221-500

GSM UMTS Packet Core Network

GSM UMTS Packet Core Network

Copyright Country of printing Confidentiality Legal statements Trademarks

Nortel Networks Confidential

i Copyright 20042007 Nortel Networks

ii Contents Nortel Networks Confidential

Copyright 20042007 Nortel Networks

Nortel Networks Confidential

Contents iii Copyright 20042007 Nortel Networks

iv Contents Nortel Networks Confidential

Copyright 20042007 Nortel Networks

Nortel Networks Confidential

Contents v Copyright 20042007 Nortel Networks

Adding SGSN Alarms

MDM Alarm Screening Macro MDM Alarm Injection Script (Obsolete)

Alarm Change Summary

GSM UMTS Packet Core Network