Below are just a few alarms and how they are displayed.
Span Alarms
Carrier Group Alarm (CGA) or Span Dead
Description:
The IMG will send a number of different alarms to EventView depending on what event has occurred to that span. Below is screen capture of what EventView will display if the cable is removed from one of the bearer spans.
Cable removed from interface 4 which has a bearer span configured on it
Possible Problem:
This alarm is generated when the IMG detects a carrier group alarm for more than the configured time period. Possible problems:
A clock source was lost.
A T1/E1 cable was removed or went bad. A physical connection to the TDM (Time Division Multiplexed) network went bad.
Is span configured correctly and are both local and remote ends configured the same.
Fix:
Repair or replace the bad cable
Data:
The data displayed in Eventview is shown in screen capture above
License Failure Alarms
License Logical Node ID Mismatch Alarm
Description:
The following alarm is generated when the Logical Node ID of an IMG and the Logical Node ID specified in the .csa file being loaded for that same IMG are not the same value.
Problem:
The alarm will display in Eventview if the following is true:
The Logical Node ID being reported by an IMG in the Poll (0x0170) message is not the same value as specified in the .csa file being loaded from ClientView for that same IMG and the Logical Node ID being reported is not 255.
All newly reset IMG’s report a Logical IMG of 255 to indicate that the Logical Node ID needs to be set.
Fix:
Reset the IMG. Upon completion of the reset, the IMG should configure normally.
Data:
"HostAlarm(Node=0, Type=Communications, SubType=Node Detected LNI Reset. Manual Reset Required., Severity=Major)"
SIP Gateway Alarm
SIP Gateway Alarm
A SIP gateway Alarm that will appear in both EventView and alarm.log. The alarm indicates the status of a particular SIP Gateway.
This alarm will contain the status (either “unreachable” or “reachable”) and the IP address of the Gateway. The SIP Gateway Alarm is first sent if the Gateway is considered Unreachable. Another alarm is the Alarm Cleared message. This alarm is sent whenthe Gateway is considered Reachable again. Below are samples of the alarm messages
SIP Gateway Alarm
Sep 19 2007 11:08:36.838 X0[88.235.44.169]->H : 00 b9 04 0a 00 03 0a 04 07 00 04 07 cc 09 c9 4a
Sep 19 2007 11:08:36 **Major: Node 0: Entity 0xa Alarm: Unrecognized Alarm 0x4
00 b9 Alarm Message
04 Reserved
0a Sequence Number
00 Logical Node ID
03 Severity (3=Major)
0a Alarm Type ALARMentGATEWAY
04 Gateway Unreachable 03=Gateway Reachable
07 DATA Length
00 Gateway Status 0=Down 1=Up
04 07 GATEWAY ID (1031)
cb 07 65 41 GATEWAY IP Address (203.7.101.65)
Alarm Cleared
Sep 19 2007 11:12:38.048 X0[88.235.44.169]->H : 00 c1 02 77 00 03 0a 03 07 01 04 07 cc 09 c9 4a
Sep 19 2007 11:12:38.048 X0[88.235.44.169]->H : 00 c1 02 77 00 03 0a 03 07 01 04 07 cc 09 c9 4a
Sep 19 2007 11:12:38 Major: Node 0: Entity 0xa Alarm: Unrecognized Alarm Cleared 0x3
00 c1 Alarm Cleared
02 Reserved
77 Sequence Number
00 Logical Node ID
03 Severity (3=Major)
0a Alarm Type Alarm Cleared
03 Gateway Reachable 04=Unreachable
07 DATA Length
01 Gateway Status 0=Down 1=Up
04 07 Gateway ID
cb 07 65 41 Gateway IP address
PPL Event Indication
PPL Event Indications
EventView also displays the PPL Event Indications for events that happen on the IMG. Below are a couple screen captures of the messages that are displayed in Eventview. Note that the Failure Reason is displayed in the message. The PPL Event Indications will print out any events that happen along with the failure reason for ease of troubleshooting
Cable removed from span that has link on it
Link brought into service through ClientView
