2 Message Type

This chapter provides an overview of the format of the messages and their general purpose.

2.1 System Alarm Levels

There are three levels of alarms in the EAGLE system. They are:

Critical
A critical alarm is an indication of a severe service affecting problem that can be related to traffic, billing, and maintenance capabilities and requires immediate maintenance attention, regardless of time of day.
Major
A major alarm is an indication of a problem that seriously affects system operation, maintenance and administration, etc. and requires immediate attention. The urgency is less than in critical situations because of a lesser immediate or impending effect on system performance, customers, and operating company operations and revenue.
Minor
A minor alarm is an indication of a problem that does not have a serious impact on service, and does not require immediate maintenance attention.

Note:

Some UAMs are considered informational if they satisfy the following conditions in the SNMP V2 traps generated by EAGLE E5OAM:
  1. The Alarm Level is stated as "No alarm condition" in this user's guide.
  2. The alarm is not intended to clear any higher severity UAM as per the corresponding UAM Balancing Matrix.
These UAMs are informational only and neither contribute to the total number of alarms in the system nor change the alarm state of the device on EAGLE.

2.2 Output Messages

The EAGLE generates output messages in response to command input or fault conditions in the EAGLE or in the network. The format for these messages is generally uniform. Some messages include additional data.

Network messages provide the text description of the event, and on the lines below the text line, any additional information.

The following example shows the general format of an output message.

Figure 2-1 Output Message Format

img/r_output_messages_maintmanual_fig1.jpg

The fields in an output message (shown in the figure above) are described next:

  • Host CLLI code - a maximum of one alpha character and ten alphanumeric characters. The CLLI code uniquely identifies the system in terms of its physical location. The CLLI code must be unique among all elements in the system.

    The CLLI code consists of the following:

    • City = 4 characters

    • State = 2 characters

    • Building = 2 characters

    • Equipment type = 3 characters

  • Date - The date the message was generated, in the format year-month-day.

  • Time - The time the message was generated with time zone, in the format hour: minutes: second time zone.

  • System Release Number - contains a system identifier and the version ID number. The system identifier, can be EAGLE or EAGLE5 depending on the product key enabled on the system. The version ID number has the software release specific GPL set that is expected to be installed on the system as approved loads. The format of the version ID number is in the form of maj.min.maint, defined as follows:

    • maj - the major release ID

    • min - the minor release ID

    • maint - the maintenance release ID

  • Alarm Level - a one or two character indicator of the alarm level, defined as follows:

    • *C = Critical Alarm

    • ** = Major Alarm

    • * = Minor Alarm

    • blank = No Alarm

  • Message Sequence Number - This number is an index for all output messages. The number increments sequentially for every message. The output messages originating from the card in location 1113 has a range from 0001 through 4999. The range for location 1115 is 5000 through 9999.

  • Message Reference Number - Messages that are associated with a specific action are numbered for reference. These messages are defined in this chapter, along with a corrective action.

  • Affected Device - The device that caused the message to be generated. This generally describes the card type.

Network messages with additional data display the additional lines below the text string and message reference number (MRN). See individual messages for examples of output.

All network messages are non-alarm and are used to notify the user of network events. There may or may not be a procedure associated with these messages.

2.3 Unsolicited Alarm Messages (UAM)

The system sends unsolicited alarm messages to the system terminal whenever there is a system fault, whenever a previous fault condition is corrected, when a subsystem, equipment, and/or service is placed in or taken out of service. Each message has a trouble code and text associated with the trouble condition.

2.4 Unsolicited Information Messages (UIM)

The system sends unsolicited information messages to the system terminal whenever there is a non-service affecting condition. This includes MSUs with invalid information, conversion failures, and/or a failed gateway screening function. Each message has a numbered code and informational text associated with the condition.