1. EAGLE Unsolicited Alarm and Information Messages Reference
  2. UAM and UIM Troubleshooting Procedures

3 UAM and UIM Troubleshooting Procedures

3.1 Troubleshooting Procedures

The following procedures are listed by message reference number (MRN). Locate the message reference number in the output message on your screen, find the MRN in this chapter, and follow the procedure to troubleshoot the problem.

Note:

The outputs in the following procedures are examples. Some outputs have several variations. In most cases only one variation is shown.

If a linkset is in test mode, any GWS failure UIMs are reported, but the failed traffic is still switched through. The UIM displays a line identifying the test mode state. A linkset in test mode performs the GWS action, but does not screen out MSUs which do not pass screening. The GWSM action is on and the GWSA or GWS Activated action is off.

The system header information is shown in the example outputs and includes the following information:

Figure 3-1 System Header Information

img/c_uam_and_uim_troubleshooting_procedures_maintmanual-fig1.jpg
Legend
ASSY SN
Assembly Serial Number
SLC
Signaling Link Code
FECLLI
Far End CLLI - the CLLI designation, i.e., name, of the machine interacting with this machine.
ILSN
Incoming Linkset Name

3.2 UAMs

The following are UAMs that may be displayed.

3.2.1 0001 - Card Has Reset

This could have been the result of a manual reset, or software reset. If the system software detects trouble with a card, the processors on the card (application or communication processors) are reset by software. The system software is responsible for this function.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0001 ** CARD 1113 OAM   Card has reset

Alarm Level: Major

Recovery

  1. The system recovers from this condition by reloading the card software.
    If the card continually resets, replace the affected card. Refer to the Maintenance Manual for card removal/replacement procedures.

    The recovery message sequence should be similar to: 

    **  0057.0001 ** CARD 1201 SS7ANSI   Card has reset
    0058.0096    CARD 1201 SS7ANSI   Card has been reloaded
    0059.0236    SLK 1201,A nc00027  REPT-LKF: not aligned
    0060.0236    SLK 1201,B nc00027  REPT-LKF: not aligned
    0061.0200    SLK 1201,A nc00027  RCVRY-LKF: link available
    0062.0200    SLK 1201,B nc00027  RCVRY-LKF: link available
  2. If the card resets without explanation or continues to reset, contact My Oracle Support (MOS).

3.2.2 0002 - Card is not Running Approved GPL

This alarm indicates a card or cards are running a generic program load (GPL) other than the approved GPL. This is determined by a system audit, which compares the GPL running on each card with the approved version for each card type. If any card(s) are running a GPL other than its approved GPL, an alarm is created. Only one alarm for each card application is displayed.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0002  * GPLSYSTEMOAM   Card is not running approved GPL

Alarm Level: Minor

Recovery

There are three procedures for this output. Choose the procedure based on the GPL System indicated in the alarm message. Refer to the following to help determine the correct procedure:

  1. Use the Recovery Procedure for All Cards Without Flash Memory if the following GPLs are indicated in the output as the GPL System.

    ATMANSI, ATMITU, CCS7ITU, EBDABLM, EBDADCM, EMDC, EOAM, EROUTE, GLS, IMT, IPGWI, IPLIM, IPLIMI, IPS, MCP, SCCP, SS7ANSI, SS7HC, SS7IPGW, SS7ML, VSCCP

  2. Use the Recovery Procedure for Cards With Flash Memory (Except HMUX and HIPR) if the following GPLs are indicated in the output as the GPL System.

    BLBIOS, BLCPLD, BLDIAG, BLVXW, BPDCM, BPHCAP, BPHCAPT, BPMPL, BPMPLT, IMTPCI, PLDE1T1, PLDPMC1

  3. Use the Recovery Procedure for HIPR2 Card if the following GPL is indicated in the output as the GPL System.

    BPHMUX, HIPR

3.2.2.1 Recovery Procedure for All Cards Without Flash Memory

Caution:

This procedure causes the identified card to reload, and should be used only during periods of low traffic or the maintenance window.
  1. Enter this command to verify the GPLs running for the card identified in the output:
    rept-stat-gpl:gpl=xxxxxxx
    where xxxxxxx is the GPL

    Note:

    Mismatched GPLs should occur only during upgrades or running a trial GPL.
    identified in the output.

    Example of the output: 

    tekelecstp 03-07-03 16:53:23 EST  EAGLE5 32.0.0-55.0.0
    GPL Auditing  ON
    GPL        CARD      RUNNING            APPROVED      TRIAL
    SS7HC      1203      025-015-001 ALM   025-015-000   -----------
  2. Verify GPL Auditing is ON. If not, enter this command:
    chg-gpl:audit=on
  3. Enter the command to reload the card:
    init-card:loc=xxxx
    where xxxx is the card location stenciled on the shelf of the EAGLE 5 ISS

    Note:

    Wait for the card to finish loading before continuing.
  4. Enter the command to verify the approved GPLs match the running GPLs:
    rept-stat-gpl:gpl=xxxxxxx

    where xxxxxxx is the GPL identified in the output.

  5. If the GPLs match, you have completed this procedure.

    If the GPLs do not match, continue with the next step.

  6. Enter this command to determine which cards are in alarm condition (indicated by the acronym ALM in the rept-stat-gpl display):
    rept-stat-gpl
  7. Note which cards are in an alarm condition and contact My Oracle Support (MOS).
3.2.2.2 Recovery Procedure for Cards With Flash Memory (Except HMUX and HIPR)

Caution:

This procedure causes the identified card to reload, and should be used only during periods of low traffic or the maintenance window.
  1. Enter the command to display the card locations running the GPL identified in the output.
    rept-stat-gpl:gpl=xxxxxxx

    where xxxxxxx is the GPL identified in the output.

    Example of the output. 
    tekelecstp 03-07-03 16:53:23 EST  EAGLE5 35.0.0-55.0.0
GPL Auditing  ON
GPL        CARD      RUNNING            APPROVED      TRIAL
BLCPLD     1203      025-015-001 ALM   025-025-000   -----------

    Note:

    Mismatched GPLs should occur only during upgrades or running a trial GPL.
  2. Verify GPL Auditing is ON. If not enter the command:
    chg-gpl:audit=on
  3. Enter the command to deactivate all links on the card.
    dact-slk:loc=xxxx:link=y

    where xxxx is the card location identified in the output and y is the link.

  4. Enter the command to change the state of the appropriate card to the out of service - maintenance disabled state:
    inh-card:loc=xxxx:force=yes

    where xxxx is the card location stenciled on the shelf of the EAGLE 5 ISS.

    Example of the output: 
    RLGHNCXA03W  00-06-05  11:11:28 EDT  EAGLE 35.0.0
Card has been inhibited.
  5. Enter the command to load and activate the approved GPL onto the inhibited card:
    flash-card:code=appr:loc=xxxx:force=yes

    where xxxx is the card location used in the previous step. The optional force=yes is used to force the command to work on an IS-NR card. Links provisioned on the card are inhibited during command execution. The card and inhibited links are restored to their previous state when the command is completed.

    Example of the output using card location 1112: 
    Command Accepted - Processing

    tekelecstp 18-01-18 16:06:22 MST  EAGLE 46.5.1.5.0-73.3.0
    flash-card:code=appr:force=yes:loc=1112
    Command entered at terminal #1.
;
    tekelecstp 18-01-18 16:06:55 MST  EAGLE 46.5.1.5.0-73.3.0
    Flash Card: FLASH GPL required to be downloaded on card 1112
    BLMCAP    : Running version 143-001-000  Expected version 143-002-000
;
    tekelecstp 18-01-18 16:07:14 MST  EAGLE 46.5.1.5.0-73.3.0
    Flash Card: Downloading BLMCAP on card 1112
    Flash Card: Card(s) will reset after the flash GPL download.
;
    tekelecstp 18-01-18 16:07:56 MST  EAGLE 46.5.1.5.0-73.3.0
    Flash Card: Activating BLMCAP on card 1112
;
    tekelecstp 18-01-18 16:08:25 MST  EAGLE 46.5.1.5.0-73.3.0
    Flash Card: Card 1112 flash activation complete.
;
    Flash Card: Activating links on card 1112. 
;
    tekelecstp 18-01-11 16:09:11 EST  EAGLE5 39.0.0
    Command Completed.
  6. Enter the command to put the card that was inhibited in 4 back into service:
    alw-card:loc=xxxx

    where xxxx is the card location used in 4.

    Example of the output: 
    RLGHNCXA03W  00-06-05  11:11:28 EDT  EAGLE 35.0.0
Card has been allowed.

    Note:

    Allow the card to run for 5 minutes before continuing.
  7. Enter the command to activate all links on the card.
    act-slk:loc=xxxx:link=y

    where xxxx is the card location identified in the output and y is the link.

  8. Enter the command to verify all links on the card are active.
    rept-stat-slk:loc=xxxx:link=y

    where xxxx is the card location identified in the output and y is the link.

  9. Enter the command to verify the approved GPLs match the running GPLs:
    rept-stat-gpl:gpl=xxxxxxx

    where xxxxxxx is the GPL identified in the output.

  10. If the GPLs match, you have completed this procedure.

    If the GPLs do not match, continue with the following step.

  11. Repeat this procedure for each card that shows ALM in the output.
  12. If the same card shows in an alarm condition after executing the procedure, please contact My Oracle Support (MOS).
3.2.2.3 Recovery Procedure for HIPR2 Card

Caution:

This procedure causes the identified card to reload and resets the respective IMT bus, and should be used only during periods of low traffic or the maintenance window.
  1. Enter the command to verify the GPLs running for the card identified in the output:
    rept-stat-gpl:gpl=xxxxxx

    where xxxxxxx is the GPL (HIPR2 identified in the output.

    Example of a HIPR2 output : 
    tekelecstp 03-07-03 16:53:23 EST  EAGLE5 35.0.0-55.0.0
GPL Auditing  ON
GPL 
 
CARD  RUNNING      APPROVED         TRIAL        
HIPR2    1209  028-005-000  028-005-000      
-----------
  
HIPR2    1210  028-005-000  028-005-000      
-----------
  
HIPR2    1309  028-004-000  028-005-000 ALM  
-----------
  
HIPR2    1310  028-005-000  028-005-000      
-----------

    Note:

    Mismatched GPLs should occur only during upgrades or running a trial GPL.
  2. Verify GPL Auditing is ON.
    If not enter the command:
    chg-gpl:audit=on
  3. Enter the command to load the GPL onto the HIPR2 card:
    init-flash:code=appr:loc=xxxx

    where xxxx is the HIPR2 card location with the alarm condition in 1.

    Example of the output using card location 1309: 
    RLGHNCXA03W  00-06-05  11:11:28 EDT  EAGLE 35.0.0
    FLASH Memory Downloading for card 1309 Started.
;
    RLGHNCXA03W  00-06-05  11:11:28 EDT EAGLE 35.0.0
    HIPR2 Downloading for card 1309 Complete.
;
    RLGHNCXA03W  00-06-05  11:11:28 EDT  EAGLE 35.0.0
    Command Completed.
  4. Enter the command to initialize the HIPR2.

    Caution:

    This command boots the HIPR2 processor and brings down the respective IMT bus temporarily (approximately 10 seconds) until the HIPR2 card comes back into service.

    • To flash an individual HIPR2 card:

      init-mux:loc=xxxx

      where xxxx is the card location.

    • To flash all cards on a particular bus:

      init-mux:bus=y

      where y is the bus.

    Note:

    Allow the card to run for 5 minutes before continuing.
  5. Enter the command to activate the trial GPL loaded onto the card in 4:
    act-flash:loc=xxxx

    where xxxx is the card location used in 3.

    Example of the output using card location 1309: 
    RLGHNCXA03W  00-06-05  11:11:28 EDT  EAGLE 35.0.0
    FLASH Memory Activation for card 1309 Completed.
;
    RLGHNCXA03W  00-06-05  11:11:28 EDT  EAGLE 35.0.0
    Command Completed.
  6. Enter the command to verify the approved GPLs match the running GPLs:
    rept-stat-gpl:gpl=xxxxxx

    where xxxxxxx is the GPL (HIPR2) identified in the output.

    Example of a HIPR2 output: 
    tekelecstp 03-07-03 16:53:23 EST  EAGLE5 35.0.0-55.0.0
GPL Auditing  ON
GPL 

CARD  RUNNING      APPROVED         TRIAL        
HIPR2    1209  028-005-000  028-005-000      
-----------
  
HIPR2    1210  028-005-000  028-005-000      
-----------
  
HIPR2    1309  028-005-000  028-005-000      
-----------
HIPR2    1310  028-005-000  028-005-000      
-----------
  7. If the GPLs match, you have completed this procedure.

    If the GPLs do not match, continue with the procedure.

  8. Enter the command to determine which cards are in alarm condition (indicated by the acronym ALM in the rept-stat-gpl display):
    rept-stat-gpl
  9. Note which cards are in an alarm condition and contact My Oracle Support (MOS).

3.2.3 0003 - Alarm Cleared for GPL

This message indicates that all the cards of a specific type are running the approved GPL and the alarm condition, specified by message “0002 - Card is not running approved GPL” has been cleared.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0003    GPL SYSTEM OAM   Alarm cleared for GPL

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.4 0004 - Card is Running Non-activated GPL

This alarm indicates a card or cards are running a non-activated Trial or Approved generic program load (GPL). This output is expected when changing a flash GPL. This alarm occurs after a successful download to the card, and the card boots. This is determined by a system audit, which compares the GPL running on each card with the activated version for each card type. If any card(s) are running a GPL other than its activated GPL, an alarm is created. Only one alarm for each card application is displayed. UAM 0002 might also be produced.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0004  * GPLSYSTEMBPDCM   Card is running non-activated GPL

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the release GPLs match the GPLs on the disk: rtrv-gpl

    Note:

    Mismatched GPLs should occur only during upgrades or running a trial GPL.
  2. Enter the following command to determine which cards are in alarm condition (indicated by the acronym ALM in the rept-stat-gpl display): rept-stat-gpl
  3. If the GPLs do not match from 1, note which cards are in an alarm condition and contact My Oracle Support (MOS).

3.2.5 0005 - Alarm Cleared Running Non-activated GPL

This message indicates that all the cards of a specific type are running the non-activated GPL and the alarm condition, specified by message “0004 - Card is running non-activated GPL” has been cleared.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0005    GPL SYSTEM BPDCM   Alarm cleared running non-activated GPL

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This message indicates a previous fault has been corrected.
    No further action is necessary.

3.2.6 0008 - Active MASP has Become Isolated

This messages indicates the active MASP has a fault and the system switched to the standby MASP. This could be caused by the MASP losing a connection to the IMT, a failure with the GPSM-II card, or a card reset.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0008  ** CARD 1113 OAM         Active MASP has become isolated

Alarm Level: Major

Recovery

  1. Enter the following command to check the status of the IMT: rept-stat-imt
    If the IMT is at fault, verify the IMT cables are connected to the shelf backplane (refer to the Installation Manual for cable locations).
  2. If the state of the IMT appears good but the GPSM-II boots repeatedly, try reseating the GPSM-II card.
    If the problem persists, replace the GPSM-II card. Refer to the Maintenance Manual for card removal/replacement procedures.
  3. If the trouble does not clear, obtain any obituary reports and contact My Oracle Support (MOS).

3.2.7 0009 - MASP Became Active

This message indicates which MASP is active.

Example 
  RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
  0014.0009   CARD 1113 OAM   MASP became active

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault or condition has been corrected.

No further action is necessary.

3.2.8 0010 - MASP Became Standby

This message indicates which MASP is standby.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0012.0010   CARD 1113 OAM   MASP became standby

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This message indicates a previous fault or condition has been corrected.
    No further action is necessary.

3.2.9 0012 - Invalid HW for Integrated Measurements

The E5-OAM Integrated Measurements feature runs on the E5-MASP card. This UAM indicates that the E5-OAM Integrated Measurements feature is enabled and on, but one of the paired E5-MASP cards was removed from the active or standby MASP locations and replaced with an incompatible GPSM-II (OAM) card.

Example 
**  0014.0012 ** CARD 1113 OAM           Invalid HW for Integrated Measurements

Alarm Level: Major

Recovery

  1. Replace the GPSM-II (OAM) card in the active or standby position with a working E5-MASP card so that the E5-OAM Integrated Measurements feature can run correctly.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.10 0013 - Card is Isolated from the System

This indicates a card has become isolated and is unable to communicate to other cards in the system. This could be caused by a defective card, a power failure occurred on the card, a thermtrip when the shutdown temperature is exceeded, or the system software ordering a reset.

This also appears when the card has been manually reset by a command.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0013  **  CARD 1113 OAM   Card is isolated from the system
               ASSY SN: 102199815a1234

Alarm Level: Major

Recovery

  1. Enter the following command to check the status of the card:
    rept-stat-card:loc=x:mode=full

    where x is the card location stenciled on the shelf of the system.

    Following is an example of the possible output using card 1106: 

    integrat40 00-05-24 10:37:22 EST EAGLE 35.0.0
    CARD   VERSION      TYPE      APPL      PST           SST     AST
    1106   021-101-000  TSM       SCCP      IS-NR         Active  -----
      ALARM STATUS       = No Alarms.
      IMT VERSION        = 021-001-000
      PROM VERSION       = 021-001-000
      IMT BUS A          = Conn
      IMT BUS B          = Conn
      CLOCK A            = Active
      CLOCK B            = Idle
      CLOCK I            = Idle
      MBD BIP STATUS     = valid
      DB STATUS          = valid
      DBD MEMORY SIZE    = 64M
      SCCP SERVICE       = 1201, , 1214, 1215, 1217, 1102
      SCCP % OCCUP       = 0%
      SLK A   PST        = OOS-MT           LS=ls11234567  CLLI=
      SLK B   PST        = OOS-MT           LS=ls11345678  CLLI=
      SNM    TVG RESULT  = 24 hr: ------,  5 min: ------   
      SCCP   TVG RESULT  = 24 hr: ------,  5 min: ------ 
    Command Completed.
  2. If only one card is isolated, wait to see if the card is recovering.
    If not, reset the card.
  3. If resetting the card does not clear the fault, reseat the card.

    Note:

    For EPM-B based cards, the CPU shuts down automatically when the shutdown temperature is exceeded (thermtrip). After the temperature returns to normal operating conditions, you must reseat the card to restore operation.
  4. If reseating the card does not clear the fault, replace the card.
    Refer to the Maintenance Manual for card removal/replacement procedures.
  5. If the alarm still does not clear, contact My Oracle Support (MOS).

3.2.11 0014 - Card is Present

The card indicated was isolated from the system, but is now communicating with the active MASP. The maintenance software has begun recovery action.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0014    CARD 1201 SS7ANSI   Card is present
             ASSY SN: 102199815a1234

Alarm Level: No alarm condition. The message is informational only.

Recovery

No immediate action is required.

The maintenance software is attempting to recover the card by reinitialization of the card.

3.2.12 0021 - Clock A for Card Failed, B Normal

This indicates that the A clock signal for the indicated card is not present.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0021  * CARD 1116 OAM   Clock A for card failed, Clock B normal

Alarm Level: Minor

Recovery

  1. Enter the following command to determine the status of the clock:
    rept-stat-clk

    The output indicates how many cards are using the specified clock, and how many cards are reporting fault with the specified clock.

    Following is an example of the possible output: 

    tekelecstp 00-04-23 13:34:15 EST EAGLE 35.0.0
    CARD LOC= 1114 (Active   )    CARD LOC= 1116 (Isolated )
    PRIMARY BITS   = Active       PRIMARY BITS   = -----
    SECONDARY BITS = Idle         SECONDARY BITS = -----
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 009     # Cards with bad CLK A = 000
    # Cards using CLK B = 000     # Cards with bad CLK B = 009
    # Cards using CLK I = 000
    Command Completed.

    Caution:

    Resetting, reseating, or replacing a LIM will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  2. If only one card is reporting fault, reset the card.
  3. If the fault has not cleared, reseat the card.
  4. If the fault has not cleared, replace the card.
    Refer to the Maintenance Manual for card removal/replacement procedures.
  5. If the fault has not cleared, replace the TDM card in MASP A.
  6. If more than one card is reporting fault with the designated clock, check the clock cable connection at the shelf backplane (refer to the Installation Manual for cable location).
    If the clock cable is at fault, replace the clock cable.
  7. If the fault has cleared and any of these cards are LIMs, place the links assigned to these cards back into service using the act-slk command.

3.2.13 0022 - Clock B for Card Failed, A Normal

This indicates that the B clock signal for the indicated card is not present.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0022  * CARD 1116 OAM   Clock B for card failed, Clock A normal

Alarm Level: Minor

Recovery

  1. Enter the following command to determine the status of the clock:
    rept-stat-clk

    The output indicates how many cards are using the specified clock, and how many cards are reporting fault with the specified clock.

    Following is an example of the possible output: 

    tekelecstp 00-04-23 13:34:15 EST EAGLE 35.0.0
    CARD LOC= 1114 (Active   )    CARD LOC= 1116 (Isolated )
    PRIMARY BITS   = Active       PRIMARY BITS   = -----
    SECONDARY BITS = Idle         SECONDARY BITS = -----
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 009     # Cards with bad CLK A = 000
    # Cards using CLK B = 000     # Cards with bad CLK B = 009
    # Cards using CLK I = 000
    Command Completed.

    Caution:

    Resetting, reseating, or replacing a LIM will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  2. If only one card is reporting fault, reset the card.
  3. If the fault has not cleared, reseat the card.
  4. If the fault has not cleared, replace the card.
    Refer to the Maintenance Manual for card removal/replacement procedures.
  5. If the fault has not cleared, replace the TDM card in MASP B.
  6. If more than one card is reporting fault with a clock, check the clock cable connection at the shelf backplane (refer to the Installation Manual for cable location).
    If the clock cable is at fault, replace the clock cable.
  7. If the fault has cleared and any of these cards are LIMs, place the links assigned to these cards back into service using the act-slk command.

3.2.14 0023 - Clocks A and B for Card Failed

The A and B clock sources for the indicated card are not present.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0023  * CARD 1116 OAM   Clocks A and B for card failed

Alarm Level: Minor

Recovery

  1. Enter the following command to determine the status of the clocks:
    rept-stat-clk

    The output indicates how many cards are using the specified clocks, and how many cards are reporting fault with the specified clock.

    Following is an example of the possible output: 

    tekelecstp 00-04-23 13:34:15 EST EAGLE 35.0.0
    CARD LOC= 1114 (Active   )    CARD LOC= 1116 (Isolated )
    PRIMARY BITS   = Active       PRIMARY BITS   = -----
    SECONDARY BITS = Idle         SECONDARY BITS = -----
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 009     # Cards with bad CLK A = 000
    # Cards using CLK B = 000     # Cards with bad CLK B = 009
    # Cards using CLK I = 000
    Command Completed.

    Caution:

    Resetting, reseating, or replacing a LIM will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  2. If the rept-stat-clk command indicates both clocks are healthy, reset the affected card.
  3. If the fault has not cleared, reseat the affected card.
  4. If the fault has not cleared, replace the affected card.
    Refer to the Maintenance Manual for card removal/replacement procedures.
  5. If the BITS clock is not at fault, replace the TDM cards in both MASP A and B.
  6. If the fault has cleared and any of these cards are LIMs, place the links assigned to these cards back into service using the following command:
    act-slk:loc=x:port=y

    where x is the card location stenciled on the shelf of the system and y is the port on the card designated in the loc parameter.

  7. If the fault has not cleared, contact My Oracle Support (MOS).

3.2.15 0024 - Clock A for card normal

This message indicates that the clock A distribution for the specified card is now normal.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0024    CARD 1116 OAM   Clock A for card normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault in the clock A distribution has been cleared.

No action is necessary.

3.2.16 0025 - Clock B for card normal

This message indicates that the clock B distribution for the specified card is now normal.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0025    CARD 1116 OAM   Clock B for card normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault in the clock B distribution has been cleared.

No action is necessary.

3.2.17 0026 - Clocks A and B for card normal

This message indicates that clock A and B for the indicated card has returned to a normal state.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0026    CARD 1116 OAM   Clocks A and B for card normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.18 0027 - IMT Bus util Rate Exceeds Minor Thresh

This message indicates that the combined IMT bus utilization rate has exceeded its minor threshold level.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
*   0590.0027 *  IMT SYSTEM        IMT Bus util rate exceeds minor thresh

Alarm Level: Minor

Recovery

  1. Note the time, duration, and frequency of the alarm(s).
  2. Enter the rept-stat-mux command to note the rate at which the high-speed ring is operating.
  3. Note any unusual conditions, such as one IMT bus inhibited, mate failed, SS7 link failures, etc.
  4. If this is an isolated occurrence, no further action is required other than monitoring the system for a re-occurrence.
  5. If the problem persists and the high-speed ring is operating at "low bit rate," this is an indication that the system is operating at low capacity and an upgrade of the high-speed ring to operate at "high rate" is required. Contact My Oracle Support (MOS) for information on how to purchase the HIPR2 High Rate Mode feature.
  6. If the problem persists and the high-speed ring is operating at "high rate," contact My Oracle Support (MOS) for assistance.

3.2.19 0028 - IMT Bus util Rate Exceeds Major Thresh

This message indicates that the combined IMT bus utilization rate has exceeded its major threshold level.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
**  0590.0028 ** IMT SYSTEM        IMT Bus util rate exceeds major thresh

Alarm Level: Major

Recovery

  1. Note the time, duration, and frequency of the alarm(s).
  2. Enter the rept-stat-mux command to note the rate at which the high-speed ring is operating.
  3. Note any unusual conditions, such as one IMT bus inhibited, mate failed, SS7 link failures, etc.
  4. If this is an isolated occurrence, no further action is required other than monitoring the system for a re-occurrence.
  5. If the problem persists and the high-speed ring is operating at "low bit rate," this is an indication that the system is operating at low capacity and an upgrade of the high-speed ring to operate at "high rate" is required. Contact My Oracle Support (MOS) for information on how to purchase the HIPR2 High Rate Mode feature.
  6. If the problem persists and the high-speed ring is operating at "high rate," contact My Oracle Support (MOS) for assistance.

3.2.20 0029 - IMT Bus utilization threshold cleared

This message indicates that the alarm condition specified by the previous IMT bus utilization alarm has been cleared.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
    0590.0029    IMT SYSTEM        IMT Bus utilization threshold cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.21 0030 - HIPR2 Detected a Minor Congested Second

The congestion on an IMT bus segment has reached a level 1 congestion threshold. A congested second is a one second time slice that contains 10 or more congestion events that happen on that node.

When there are no minor congested second events being reported for a node for a period of five minutes, all congested second alarms are cleared for that node.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
*   0594.0030 *  Card 1109         HIPR2 detected a minor Congested Second

Alarm Level: Minor

Recovery

  1. Note the time, duration, and frequency of the alarm(s).
  2. Enter the rept-stat-mux command to note the rate at which the high-speed ring is operating.
  3. Note any unusual conditions, such as one IMT bus inhibited, mate failed, SS7 link failures, etc.
  4. Note the segment(s) reporting the congestion.
  5. If this is an isolated occurrence, no further action is required other than monitoring the system for a re-occurrence.
  6. If the problem persists and the high-speed ring is operating at "low rate," this is an indication that the system is operating at capacity and an upgrade of the high-speed ring to operate at "high rate" is required. Contact My Oracle Support (MOS) for information on how to purchase the HIPR2 High Rate Mode feature.
  7. If the problem persists and the high-speed ring is operating at "high rate," contact My Oracle Support (MOS) for assistance.

3.2.22 0031 - HIPR2 Detected a Major Congested Second

This message indicates that the congestion on an IMT bus segment has reached a level 2 congestion threshold. A congested second is a one-second time slice that contains 10 or more congestion events that happen on that node.

When there are no major congested second events reported for a node for a period of five minutes, the major congested alarm is replaced with the minor congested second alarm for that node.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
**  0590.0031 ** Card 1110         HIPR2 detected a major Congested Second

Alarm Level: Major

Recovery

  1. Note the time, duration, and frequency of the alarm(s).
  2. Enter the rept-stat-mux command to note the rate at which the high-speed ring is operating.
  3. Note any unusual conditions, such as one IMT bus inhibited, mate failed, SS7 link failures, etc.
  4. Note the segment(s) reporting the congestion.
  5. If this is an isolated occurrence, no further action is required other than monitoring the system for a re-occurrence.
  6. If the problem persists and the high-speed ring is operating at "low rate," this is an indication that the system is operating at capacity and an upgrade of the high-speed ring to operate at "high rate" is required. Contact My Oracle Support (MOS) for information on how to purchase the HIPR2 High Rate Mode feature.
  7. If the problem persists and the high-speed ring is operating at "high rate," contact My Oracle Support (MOS) for assistance.

3.2.23 0032 - HIPR2 Congestion cleared

This message indicates that the alarm condition specified by the previous HIPR2 congestion alarm has been cleared.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
    0590.0032    Card 1209         HIPR2 Congestion cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.24 0033 - Card database has been corrected

This message indicates that the database has been reloaded to the indicated card by system software. This typically occurs when the system software finds the card database is not synchronized with the other cards in the system (incoherent database).

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0033    CARD 1113 OAM      Card database has been corrected

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.25 0034 - Card database is inconsistent

This message indicates that the database on the indicated card is not at the same level as the source database level. For more information about database management procedures, refer to the Database Administration Manual - System Management.

Example 
  RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0034  * CARD 1201 LIMDS0    Card database is inconsistent

Alarm Level: Minor

3.2.25.1 Recovery Procedure for a MASP Card
  1. Enter the following command to retrieve the terminal types and port numbers:
    rtrv-trm
  2. Enter the following command to inhibit each OAP terminal displayed in the output from 1:
    inh-trm:trm=x
    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  3. Enter the following command to check the database level on all cards:
    rept-stat-db:display=all

    Pay special attention to note the database levels on both the active and standby current partitions and the levels represented on all the network cards. It is important that the database level of the network cards matches the database level of the active MASP.

    Note:

    If the database on the OAM is repaired and ends up at a lower level than the network cards, the system must be initialized.
  4. If neither database is at the same level as the network cards, contact My Oracle Support (MOS).
  5. Depending on what the message indicates, do one of the following:
    • If the active fixed disk is inconsistent, continue with 6.
    • If the standby fixed disk is inconsistent, continue with 9.
    • If both fixed disks are inconsistent, continue with 14.
  6. Enter the following command on the active GPSM-II card to force it to become standby:
    init-card:loc=xxxx

    where xxxx is the card location stenciled on the shelf of the system.

  7. Enter the following command to log back into the system:
    login:uid=xxxx

    where xxxx is the User ID.

  8. Enter the following command to check the database level on all cards:
    rept-stat-db:display=all

    Pay special attention to note the database levels on both the active and standby current partitions and the levels represented on all the network cards. It is important that the database level of the network cards matches the database level of the active MASP.

    Note:

    If the database on the OAM is repaired and ends up at a lower level than the network cards, the system must be initialized.
  9. Enter the following command to copy the current and backup database partitions on the active fixed disk, to the current and backup database partitions on the standby fixed disk:
    chg-db:action=repair

    After the command is executed, the standby GPSM-II card reboots, the old database data is purged from memory, and the new database is loaded.

  10. After the card has been reloaded (a message appears to confirm completion of the load), enter the following command to verify the database is consistent (same level as the other cards in the system):
    rept-stat-db:display=all
    1. If standby and current active databases are consistent, continue with 11.
    2. If the current active or standby database is inconsistent, continue with 13.
  11. Enter the following command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number of the terminals of type OAP from 1.

  12. For more information on database management, refer to the Database Administration Manual - System Management.
    STOP! YOU HAVE COMPLETED THIS PROCEDURE.
  13. Enter the following command for the inconsistent fixed disk:
    tst-disk:loc=xxxx

    where xxxx is the location of the inconsistent fixed disk. When the command completes, continue with 14.

  14. Contact My Oracle Support (MOS).
3.2.25.2 Recovery Procedure for a Non-MASP Card

Caution:

Resetting, reseating, or replacing a LIM will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  1. Wait five minutes to see if the card corrects itself.
  2. Enter the following command to check the database level on the card:
    rept-stat-db:display=all
  3. If the problem persists, enter the following command to retrieve the terminal types and port numbers:
    rtrv-trm
  4. If the card is a LIM, enter the following command to deactivate the slk:
    dact-slk:loc=xxxx:port=y

    where xxxx is the card location, and y is the port on the card specified in the location parameter.

  5. Enter the following command to inhibit each OAP terminal displayed in the output from 3:
    inh-trm:trm=x

    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  6. Enter the following command to change the state of the card to OOS-MT-DSBLD
    init-card:loc=xxxx

    where xxxx is the card location stenciled on the shelf of the system.

  7. Enter the following command to change the state of the card to IS-NR:
    alw-card:loc=xxxx

    where xxxx is the card location stenciled on the shelf of the system.

  8. If the card is a LIM, enter the following command to activate the slk:
    act-slk:loc=xxxx:port=y

    where xxxx is the card location, and y is the port on the card specified in the location parameter.

  9. After the card has been reloaded (a message appears to confirm completion of the load), enter the following command to verify the database is consistent (same level as the other cards in the system).
    rept-stat-card
  10. Check the consistency of the card by entering the following command:
    rept-stat-db:display=except
  11. Enter the following command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number.

  12. If the problem persists, contact My Oracle Support (MOS).

3.2.26 0035 - Card database is corrupted

This message indicates that the card database has been modified by some unknown process and is not usable. For more information about database management procedures, refer to the Database Administration Manual - System Management.

Example 
  RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0035  * CARD 1113 OAM       Card database is corrupted

Alarm Level: Minor

3.2.26.1 Recovery Procedure for a MASP Card
  1. Enter the following command to retrieve the terminal types and port numbers:
    rtrv-trm
  2. Enter the following command to inhibit each OAP terminal displayed in the output from 1:
    inh-trm:trm=x

    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  3. Enter the following command for each OAP terminal inhibited in 2:
    chg-trm:trm=x:type=none

    where x is the port number.

  4. If the message indicates the standby fixed disk is corrupted, continue with 6.
    If the message indicates the active fixed disk is corrupted, continue with 5.
  5. Enter the following command on the active GPSM-II card to force it to become standby:
    init-card:loc=x

    where x is the card location stenciled on the shelf of the system.

  6. Enter the following command to copy the current and backup database partitions on the active fixed disk, to the current and backup database partitions on the standby fixed disk:
    chg-db:action=repair

    After the command is executed, the standby GPSM-II card reboots, the old database data is purged from memory, and the new database is loaded.

  7. After the card has been reloaded (a message appears to confirm completion of the load), enter the following command to verify the database is consistent (same level as the other cards in the system):
    rept-stat-card
  8. Enter the following command for each OAP terminal inhibited in 2:
    chg-trm:trm=x:type=oap

    where x is the port number.

  9. Enter the following command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number.

  10. If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
3.2.26.2 Recovery Procedure for a Non-MASP Card

Caution:

Resetting, reseating, or replacing a LIM will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  1. Wait five minutes to see if the card corrects itself.
  2. If the problem persists, enter the following command to retrieve the terminal types and port numbers:
    rtrv-trm
  3. Enter the following command to inhibit each OAP terminal displayed in the output from 2.
    inh-trm:trm=x
    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  4. Enter the following command to reinitialize the indicated card and force the card to load the current level of database.
    init-card:loc=x

    where x is the card location stenciled on the shelf of the system.

3.2.27 0036 - Card backup database has been corrected

This message indicates that the backup database version level and content on the standby MASP is synchronized with the reference database.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0036    CARD 1113 OAM       Card backup database has been corrected

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.28 0037 - Card Backup Database is Inconsistent

This message indicates that the backup database version level and/or content on the MASP is not synchronized with the database on the active MASP. This typically occurs if a different level counter, last update day/time-stamp, or contents is detected, or the database is incoherent.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0037  * CARD 1113 OAM     Card backup database is inconsistent

Alarm Level: Minor

Recovery

  1. Enter the following command to confirm both active and standby current databases contain correct and identical information (coherent and consistent):
    rept-stat-db

    Example of the output from a coherent database: 

    > rept-stat-db
Command Accepted - Processing
oflnmoxa11w 00-10-08 15:56:40 CDT EAGLE 35.0.0
rept-stat-db
Command entered at terminal #4.
;
oflnmoxa11w 00-10-08 15:56:40 CDT EAGLE 35.0.0
DATABASE STATUS: >> OK <<
    TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
       C   LEVEL    TIME LAST BACKUP     C   LEVEL    TIME LAST BACKUP
       - -------- ---------------------  - -------- ---------------------
FD BKUP  Y   342256 00-10-07 00:40:29 CDT  Y   342256 00-10-07 00:40:29 CDT
FD CRNT  N   342374                        Y   342375
    MDAL 1117
    - --------
  2. Enter the following command to perform a backup (to fixed disk) of both active and standby databases:
    chg-db:action=backup:dest=fixed

3.2.29 0038 - Card backup database is corrupted

This message indicates that the backup database has been modified by some unknown process and is no longer usable.

Example 
  RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0038  * CARD 1113 OAM       Card backup database is corrupted

Alarm Level: Minor

Recovery

  1. Enter this command to confirm that both active and standby current databases contain correct and identical information (coherent and consistent):
    rept-stat-db

    Example of the output from a coherent database. 

    
> rept-stat-db
Command Accepted - Processing
    oflnmoxa11w 00-10-08 15:56:40 CDT EAGLE 35.0.0
    rept-stat-db
    Command entered at terminal #4.
;
    oflnmoxa11w 00-10-08 15:56:40 CDT EAGLE 35.0.0
    DATABASE STATUS: >> OK <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
             C   LEVEL    TIME LAST BACKUP     C   LEVEL    TIME LAST BACKUP
             - -------- ---------------------  - -------- ------------------
    FD BKUP  Y   342256 00-10-07 00:40:29 CDT  Y   342256 00-10-07 00:40:29 CDT
    FD CRNT  N   342374                        Y   342375
            MDAL 1117
             - --------
  2. Enter the following command to perform a backup (to fixed disk) of both active and standby databases:
    chg-db:action=backup:dest=fixed

3.2.30 0039 - GPL has been corrected

All copies of the generic program load are satisfactory.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0039    GPL SYSTEM OAM      GPL has been corrected

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.31 0040 - GPL is Corrupted

This message indicates that a generic program load (GPL) has become corrupted. This typically occurs when the system software detects that a generic program load has been unexpectedly modified.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
* 0100.0040  * GPL SYSTEM OAM      GPL is corrupted

Alarm Level: Minor

Recovery

  1. Enter the following command to determine the status of the system generic program loads:
    rtrv-gpl

    This command indicates the generic program loads that have become corrupted.

  2. Enter the command to reload the generic program load from a system removable cartridge.
    chg-gpl

    If the approved GPL is corrupted, insure that the trial GPL is the correct one using rtrv-gpl and activate it using the act-gpl command.

3.2.32 0041 - LSMS Bulk Load Required

This message indicates that the entire system LNP database must be repopulated, either from the LSMS or a backup disk. This process must be started manually.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
* C0009.0041 *C LSMS SYSTEM        LSMS bulk load required

Alarm Level: Critical

Recovery

Refer to the LNP Database Synchronization Manual for the LSMS Bulk Load procedure.

3.2.33 0042 - LSMS Bulk Load Complete

This message indicates that the alarm condition is removed, the association is reestablished, the LSMS is downloading transactions, and the automatic resynchronization is in progress.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0042  LSMS SYSTEM        LSMS bulk load complete

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.34 0044 - Real Time Clock Battery Low

The battery power in the HC MIM card is low.

Example 
station1234 00-11-30 16:28:08 EST  EAGLE 35.0.0
* 0012.0044 *   CARD 1201  LIMT1  Real time clock battery low

Alarm Level: Minor

Recovery

Replace the HC MIM card with a spare and call Tekelec for a RMA to send the card back to Tekelec for replacement.

Note:

Refer to the Maintenance Manual for card removal/replacement procedures for details about replacing cards.

3.2.35 0045 - Real Time Clock Battery Restored

The HC MIM card has been replaced and the battery power in the HC MIM card is normal.

Example 
station1234 00-11-30 16:28:08 EST  EAGLE 35.0.0
0012.0045    CARD 1201  LIMT1  Real time clock battery restored

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.36 0046 - Terminal enabled

The indicated terminal has been returned to service and can handle normal user input and output.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0046    TERMINAL   15       Terminal enabled

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.37 0047 - Card Type Not Valid for Application

This message indicates that a TSM card was replaced by an ASM card. The ASM card is automatically inhibited because it is no longer supported.

Example 
station1234 00-11-30 16:28:08 EST  EAGLE 35.0.0
** 0012.0047  **  CARD 1109 Card type not valid for application
HW VERIFICATION CODE: xxx

Alarm Level: Major

Recovery

Replace the ASM card with the correct version of the TSM card.

Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.38 0048 - Terminal Failed

The MASP has detected that the terminal is faulty. The maintenance software has removed the terminal from service.

Example 
  RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0048  * TERMINAL   15       Terminal failed

Alarm Level: Minor

Recovery

  1. Verify that the power to the terminal is on and that the terminal is physically connected to the control shelf backplane.
    If the fault does not clear, disconnect the terminal from the control shelf backplane and connect another terminal (with the same communication attributes as the old terminal) to the same port on the control shelf backplane.
  2. Enter the following command to verify the communication attributes of the terminal port:
    rtrv-trm
  3. If the communication attributes need to be changed, refer to the Commands Manual and enter the following command with the appropriate parameters to make the required changes to the communication attributes:
    chg-trm
  4. Terminals are connected to ports on the TDM card.

    Enter the following command to determine which ports are idle:

    rept-stat-user
  5. Move the terminal to another port on the TDM card or on the backplane.
    If the fault does not clear, replace the TDM card. Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.39 0049 - Bit Rate change ACK failure

This error is displayed when OAM does not receive the acknowledgement of the Rate change request from an all HIPR2 IMT Bus.

Note:

During IMT Bus Rate change execution, no physical status change of IMT Bus (such as unplugging HIPR2 cards) should take place.
Example 
  RLGHNCXA21W 00-02-09 12:01:43 EST  EAGLE 41.1.0
*   0100.0049 *  IMT Bus A               Bit Rate change ACK failure

Alarm Level: Minor

Recovery

No action necessary.

3.2.40 0050 - Bit Rate change ACK received

This message is the clearing alarm for the previous IMT rate change alarm.

Example 
  RLGHNCXA21W 00-02-09 12:01:43 EST  EAGLE 41.1.0
0101.0050    IMT Bus A               Bit Rate change ACK received

Alarm Level:None

Recovery

No action necessary.

3.2.41 0051 - TSC Sync is in Simplex Mode

Due to one or both GPSM-II cards being replaced with MCAPs after the feature bit has been set, the hardware configuration no longer supports the TSC Synchronization feature.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0051  ** CARD 1113  OAM    TSC sync is in simplex mode

Alarm Level: Major

Recovery

Replace the MCAP(s) with GPSM-II card(s).

Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.42 0052 - TSC sync feature is available

This indicates that the GPSM-II card(s) is now seated in the appropriate slot and is functioning correctly.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0052     CARD 1113  OAM   TSC sync feature is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.43 0053 - Standby TDM Failure

This message indicates the communication between the GPSM-II and TDM has failed.

Example 
station1234 94-03-30 16:28:08 EST EAGLE 35.0.0
** 0012.0053 **  CARD 1113 OAM         Standby TDM failure

Alarm Level: Major

Recovery

  1. Enter the following command to verify card status:
    rept-stat-card
  2. Enter the following command to verify the database status:
    rept-stat-db
  3. Replace the failed TDM, that is in IS-ANR state with the backup TDM.

    Note:

    If possible, replace the card during the maintenance window.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.44 0054 - Standby TDM failure cleared

This message indicates that the communication between the GPSM-II and TDM has been reestablished.

Example 
station1234 94-03-30 16:28:08 EST EAGLE 35.0.0
0012.0054    CARD 1113 OAM         Standby TDM failure cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.45 0055 - Persistent device state tbl corrupt

This message indicates that after attempting an automatic recovery from a first checksum error, a Persistent Device States (PDS) checksum error still exists in the standby System Configuration Manager (SCM). PDS features are disabled.

Example 
  RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0055  * CARD 1115 OAM    Persistent device state tbl corrupt

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the status of the database:
    rept-stat-db
  2. Enter the following command to update the PDS table.
    This command reinitializes the card and forces the card to load the current level of the database:
    init-card:loc=xxxx
    where xxxx is the location of the card identified in output.
  3. Enter the following command to verify the that the database is the same level as the active OAM:
    rept-stat-db
  4. If the problem persists, contact My Oracle Support (MOS).

3.2.46 0056 - Persistent Device State tbl diff Version

This message indicates that the PDS table version in the standby SCM does not match the PDS table version in the active SCM. PDS features are disabled.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0056  * CARD 1115 OAM    Persistent device state tbl diff version

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the status of the database:
    rept-stat-db
  2. Enter the following command to update the PDS table.
    This command reinitializes the card and forces the card to load the current level of the database:
    init-card:loc=xxxx
    where xxxx is the location of the card identified in output.
  3. Enter the following command to verify the that the database is the same level as the active OAM:
    rept-stat-db
  4. If the problem persists, contact My Oracle Support (MOS).

3.2.47 0057 - Persistent device state tbl corrected

This indicates that the This message indicates that a problem PDS table has been corrected.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0057     CARD 1115  OAM   Persistent device state tbl corrected

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.48 0058 - Critical customer trouble detected

A critical customer trouble has been detected. There are connections on the control shelf backplane for customer detected troubles (CDTs). Each connection is assigned an identifier 1-16. CDT connections 2-4 are applicable to UAM 0058. CDT connections 6-8 are applicable to UAM 0059. CDT connections 10-16 are applicable to UAM 0060. The customer determines the connections on the backplane (these are dry contact closures). The system reports the alarm according to the connection location.

Example 
RLGHNCXA21W 96:07:02 11:02:30 EST  EAGLE 35.0.0
*C 0100.0058  *C CDT 4           Critical customer trouble detected

Alarm Level: Critical

Recovery

Follow local procedures for clearing the indicated trouble.

3.2.49 0059 - Major customer trouble detected

A major customer trouble has been detected. There are connections on the control shelf backplane for customer detected troubles (CDTs). Each connection is assigned an identifier 1-16. CDT connections 2-4 are applicable to UAM 0058. CDT connections 6-8 are applicable to UAM 0059. CDT connections 10-16 are applicable to UAM 0060. The customer determines the connections on the backplane (these are dry contact closures). The system reports the alarm according to the connection location.

Example 
RLGHNCXA21W 96:07:02 11:02:30 EST EAGLE 35.0.0
** 0100.0059  ** CDT 8           Major customer trouble detected

Alarm Level: Major

Recovery

Follow local procedures for clearing the indicated trouble.

3.2.50 0060 - Minor customer trouble detected

A minor customer trouble has been detected. There are connections on the control shelf backplane for customer detected troubles (CDTs). Each connection is assigned an identifier 1-16. CDT connections 2-4 are applicable to UAM 0058. CDT connections 6-8 are applicable to UAM 0059. CDT connections 10-16 are applicable to UAM 0060. The customer determines the connections on the backplane (these are dry contact closures). The system reports the alarm according to the connection location.

Example 
RLGHNCXA21W 96:07:02 11:02:30  EST EAGLE 35.0.0
* 0100.0060   * CDT 16          Minor customer trouble detected

Alarm Level: Minor

Recovery

Follow local procedures for clearing the indicated trouble.

3.2.51 0061 - Customer trouble detected

A customer trouble has been detected.

Example 
RLGHNCXA21W 96:07:02 11:02:30  ESTEAGLE 35.0.0
0100.0061       CDT 11        Customer trouble detected

Alarm Level: No alarm condition. The message is informational.

Recovery

This message indicates that a customer-defined trouble is detected. Follow local procedures to clear the trouble.

3.2.52 0062 - Customer trouble cleared

A customer trouble has been cleared.

Example 
RLGHNCXA21W 96:07:02 11:02:30  EST EAGLE 35.0.0
0100.0062       CDT 11         Customer trouble cleared

Alarm Level: No alarm condition. The message is informational.

Recovery

No action is necessary.

3.2.53 0063 - Critical Holdover Clock trbl Detected

A critical trouble has been detected with the holdover clock. This could include a problem with the reference input and stratum clock cards.

Example 
RLGHNCXA21W  96:07:02 11:02:30  EST  EAGLE 35.0.0
   *C  0100.0063    *C CLOCK    Critical holdover clock trbl detected

Alarm Level: Critical

Recovery

Check for any visual alarms.

Note any visual alarms and refer to the Maintenance Manual for Holdover Clock Troubleshooting Procedures to perform the corrective action procedures.

3.2.54 0064 - Major Holdover Clock Trouble Detected

A major trouble has been detected with the holdover clock. This could include a problem with the reference input and/or stratum clock cards.

Example 
RLGHNCXA21W 96:07:02 11:02:30    EST EAGLE 35.0.0
**  0100.0064   ** CLOCK    Major holdover clock trouble detected

Alarm Level: Major

Recovery

Check for any visual alarms.

Note any visual alarms and refer to the Maintenance Manual for Holdover Clock Troubleshooting Procedures to perform the corrective action procedures.

3.2.55 0065 - Minor Holdover Clock Trouble Detected

A minor trouble has been detected with the holdover clock. This could include a problem with the reference input and/or stratum clock cards.

Example 
RLGHNCXA21W 96:07:02 11:02:30 EST EAGLE 35.0.0
*  0100.0065    *  CLOCK         Minor holdover clock trouble detected

Alarm Level: Minor

Recovery

Check for any visual alarms.

Note any visual alarms and refer to the Maintenance Manual for Holdover Clock Troubleshooting Procedures to perform the corrective action procedures.

3.2.56 0066 - Holdover clock trouble cleared

A problem with the holdover clock has been corrected.

Example 
RLGHNCXA21W 96:07:02 11:02:30 EST EAGLE 35.0.0
0100.0066       CLOCK Holdover clock trouble cleared

Alarm Level: No alarm condition. The message is informational.

Recovery

This message indicates that a problem with the holdover clock has been cleared.

3.2.57 0077 - Card Temperature is Critical lvl:T2

An HC-MIM card, EPM based card (E5-E1T1, E5-ATM, E5-ENET, ET-IPSM, E5-TSM) EPM-B based card (E5-ATM-B, E5-ENET-B, E5-MCPM-B), or E5-SM8G-B card has reached an operating temperature that is above the operational limit.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*C 0100.0077  *C CARD 1102  LIMT1 Card temperature is critical lvl:T2

Alarm Level: Critical

Recovery

WARNING:

There is a very limited time to solve this problem. For an HC-MIM card, once the card exceeds its operation limit, all the links on the HC-MIM card will be blocked (ACT-LPO), causing the links to go into local processor outage. All traffic on the blocked links is re-directed elsewhere in the system (based on the current route provisioning). For information about EPM based, EPM-B based, and E5-SM8G-B cards, see "Changing the High-Capacity Card Temperature Alarm Thresholds" procedure in Database Administration Manual - SS7.
  1. Verify that the fan assembly located in that shelf is working properly and that the fan filters are clean.
    • Check to make sure there is both A and B power.
    • Check the fans.
    • Check the fan controller card and verify that all LEDs are green.

      For proper operation (as a minimum B power must be present and good fans for fan 2 and fan 3 must be installed before removing the controller).

    • Check the fan filters.
    • Replace any hardware in the fan assembly that is not functioning properly. Clean or replace fan filters as needed.
    • Replace the fan tray only after checking power, fans, fan filters, and control card.

      Contact My Oracle Support (MOS) for assistance.

    The hierarchy of maintenance activity is based on Table 3-1. See the Maintenance Manual for card removal/replacement procedures.

    Table 3-1 Maintenance Activity Hierarchy

    Condition Cntrl LED FAN 1 LED FAN 2 LED FAN 3 LED Alarm Status Actions
    Normal Operation Green Green Green Green No Alarm** None
    A power feed fail Blink RED     Alarm* Check the fuse, the power source, and cables
    Interconnect card OR circuit fail Blink   RED   Alarm* Check the fuse, the power source, and cables
    B power feed fail Blink     RED Alarm* Check the fuse, the power source, and cables
    Fan 1 fail Green RED     Alarm*

    Make sure that there is A power

    Make sure that there is B power and that Fan 2 and Fan 3 are operating properly.

    Replace the fan.

    Fan 2 fail Green   RED   Alarm*

    Make sure that there is both A and B power

    Make sure that Fan 1 and Fan 3 are operating properly

    Replace the fan

    Fan 3 fail Green     RED Alarm*

    Make sure that there is B power

    Make sure that there is A power and that Fan 1 and Fan 2 are operating properly

    Replace the fan

    Fan 1 Removed Green Blink     Alarm*

    Make sure that the fan is seated properly

    Replace the fan

    Fan 2 Removed Green   Blink   Alarm*

    Make sure that the fan is seated properly

    Replace the fan

    Fan 3 Removed Green     Blink Alarm*

    Make sure that the fan is seated properly

    Replace the fan

    Controller card partial fail RED       Alarm*

    Make sure there is both A and B power.

    Make sure the fans are working properly

    Remove Fan 1

    Replace the Fan Tray Controller

    Controller card fail OFF OFF OFF OFF Alarm*

    Make sure there is both A and B power

    Make sure the fans are working properly

    Remove Fan 1

    Replace the Fan Tray Controller

    Interconnect Failure           Replace shelf

    Note:

    • *If there is no alarm for this condition, it is likely that the relay on the Interconnect card has failed (opened).
    • **If there is an alarm when all 4 LEDs are green, it is likely that the relay on the Interconnect card has failed (closed).
    • Try replacing the controller before replacing the fan tray.
  2. If the fan unit is working properly, employ additional cooling methods to the card reporting a high-operating temperature.
  3. This Critical Temperature Alarm will remain in the system until the operational temperature of the HC-MIM card (HC Blade), EPM based card (E5-E1T1, E5-ATM, E5-ENET, ET-IPSM, E5-TSM) EPM-B based card (E5-ATM-B, E5-ENET-B, E5-MCPM-B), or E5-SM8G-B card goes below the critical temperature threshold.
  4. If this procedure did not clear the fault, contact My Oracle Support (MOS).

    Note:

    For the complete list of cards supported by EAGLE Release 47.0, see Hardware Reference Guide.

3.2.58 0078 - Card Temperature Exceeds Nominal lvl:T1

An HC-MIM card, EPM based card (E5-E1T1, E5-ATM, E5-ENET, E5-IPSM, E5-TSM), EPM-B based card (E5-ATM-B, E5-ENET-B, E5-MCPM-B), or E5-SM8G-B card has reached an operating temperature that is above the pre-defined limit.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0078  ** CARD 1102  LIMT1 Card temperature exceeds nominal lvl:T1

Alarm Level: Major

Recovery

warning:

There is a very limited time to solve this problem. Once the card exceeds its operation limit, all the links on the HC-MIM card will be blocked (ACT-LPO), causing the links to go into local processor outage. All traffic on the blocked links is re-directed elsewhere in the system (based on the current route provisioning). For information about EPM based, EPM-B based, and E5-SM8G-B cards, see "Changing the High-Capacity Card Temperature Alarm Thresholds" procedure in Database Administration Manual - SS7.
  1. Enter the following command to verify the temperature threshold defaults are within the correct range for the card:
    rtrv-th-alm

    For HC-MIM cards, the maximum operating temperature is 82 degrees Celsius. For EPM based cards (E5-E1T1, E5-ATM, E5-ENET, ET-IPSM, E5-TSM), the maximum operating temperature is 95 degrees Celsius. For EPM-B based cards (E5-ATM-B, E5-ENET-B, E5-MCPM-B) and E5-SM8G-B cards, maximum operating temperature is 90 degrees Celsius. Temperature Level 1 threshold (Thermal Alarm Level 1) and Temperature Level 2 threshold (Thermal Alarm Level 2) are user configurable. Temperature Level 1 threshold can be configured between 73%–92% (default is 92%) of maximum operating temperature of the card and Temperature Level 2 threshold can be configured between 74%–100% (default is 100%) of maximum operating temperature of the card.

    If the thresholds are set incorrectly (or to temporarily suppress the alarm), go to 2. If the thresholds are correct, go to 3.

  2. The threshold can be reset by entering the following command:
    chg-th-alm:thermallv1c=xxxx

    where xxxx is temperature.

  3. Skip this step for EPM-based cards. Verify that the fan assembly located in that shelf is working properly and that the fan filters are clean.
    • Check to make sure there is both A and B power.
    • Check the fans.
    • Check the fan controller card and verify that all LEDs are green.

      For proper operation (as a minimum B power must be present and good fans for fan 2 and fan 3 must be installed before removing the controller).

    • Check the fan filters.
    • Replace any hardware in the fan assembly that is not functioning properly. Clean or replace fan filters as needed.
    • Replace the fan tray only after checking power, fans, fan filters, and control card.

      Contact My Oracle Support (MOS) for assistance.

    The hierarchy of maintenance activity is based on Table 3-2. See the Maintenance Manual for card removal/replacement procedures.

    Table 3-2 Maintenance Activity Hierarchy

    Condition Cntrl LED FAN 1 LED FAN 2 LED FAN 3 LED Alarm Status Actions
    Normal Operation Green Green Green Green No Alarm** None
    A power feed fail Blink RED     Alarm* Check the fuse, the power source, and cables.
    Interconnect card OR circuit fail Blink   RED   Alarm* Check the fuse, the power source, and cables.
    B power feed fail Blink     RED Alarm* Check the fuse, the power source, and cables.
    Fan 1 fail Green RED     Alarm*

    Make sure that there is A power.

    Make sure that there is B power and that Fan 2 and Fan 3 are operating properly.

    Replace the fan.

    Fan 2 fail Green   RED   Alarm*

    Make sure that there is both A and B power.

    Make sure that Fan 1 and Fan 3 are operating properly.

    Replace the fan.

    Fan 3 fail Green     RED Alarm*

    Make sure that there is B power.

    Make sure that there is A power and that Fan 1 and Fan 2 are operating properly.

    Replace the fan.

    Fan 1 Removed Green Blink     Alarm*

    Make sure that the fan is seated properly.

    Replace the fan.

    Fan 2 Removed Green   Blink   Alarm*

    Make sure that the fan is seated properly.

    Replace the fan.

    Fan 3 Removed Green     Blink Alarm*

    Make sure that the fan is seated properly.

    Replace the fan.

    Controller card partial fail RED       Alarm*

    Make sure there is both A and B power.

    Make sure the fans are working properly.

    Remove Fan 1.

    Replace the Fan Tray Controller.

    Controller card fail. OFF OFF OFF OFF Alarm*

    Make sure there is both A and B power.

    Make sure the fans are working properly.

    Remove Fan 1.

    Replace the Fan Tray Controller.

    Interconnect Failure           Replace shelf.

    Note:

    • * If there is no alarm for this condition, it is likely that the relay on the Interconnect card has failed (opened).
    • ** If there is an alarm when all 4 LEDs are green, it is likely that the relay on the Interconnect card has failed (closed).
    • Try replacing the controller before replacing the fan tray.
  4. If the fan unit is working properly, employ additional cooling methods to the card reporting a high-operating temperature.
  5. If the running temperature of the HC-MIM card, EPM based card (E5-E1T1, E5-ATM, E5-ENET, E5-IPSM, E5-TSM), EPM-B based card (E5-ATM-B, E5-ENET-B, E5-MCPM-B), or E5-SM8G-B card exceeds its operational limit, UAM 0077 is generated. HC-MIM links go into Local Processor Outage (LPO). For information about EPM based, EPM-B based, and E5-SM8G-B cards, see "Changing the High-Capacity Card Temperature Alarm Thresholds" procedure in Database Administration Manual - SS7.
  6. This Temperature Alarm will remain in the system until the operational temperature of the HC-MIM card (HC Blade), EPM based card (E5-E1T1, E5-ATM, E5-ENET, E5-IPSM, E5-TSM), EPM-B based card (E5-ATM-B, E5-ENET-B, E5-MCPM-B), or E5-SM8G-B card returns to normal levels.
  7. If performing the steps in this procedure did not clear the fault, contact My Oracle Support (MOS) for assistance.
  8. If the threshold was changed in 2 to temporarily suppress the alarm, enter the following command to reset the threshold to the original setting:
    chg-th-alm:thermallv1c=xxxx

    where xxxx is temperature.

3.2.59 0079 - Card temperature again at nominal levels

The operational temperature of the HC-MIM (HC Blade), EPM based card (E5-E1T1, E5-ATM, E5-ENET, ET-IPSM, E5-TSM), EPM-B based card (E5-ATM-B, E5-ENET-B, E5-MCPM-B), or E5-SM8G-B has returned to normal levels.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0079 CARD 1102   LIMT1 Card temperature again at nominal levels

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This message indicates a previous fault has been corrected.
    No further action is necessary.

3.2.60 0080 - Shelf FAN bit is OFF

The Eagle Shelf FAN bit is not turned on.

Example 
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    xxxx.0080 *C CARD 1103  LIMT1     Shelf FAN bit is OFF

Alarm Level: Major

Recovery

To turn the Shelf FAN bit on, use the following command:

chg-shlf

3.2.61 0081 - Shelf FAN bit is ON

The Eagle Shelf FAN bit is turned on. This UAM is an informational message that confirms that the feature is restored to operational status

Example 
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    xxxx.0081 *C CARD 1103  LIMT1     Shelf FAN bit is ON

Alarm Level: Normal

Recovery

This message indicates that the feature previously was OFF and now has been turned ON.

No further action is necessary.

3.2.62 0082 - Alarm in Fuse Panel

A blown fuse has been detected in the fuse panel located on top of the designated frame.

Example 
   RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0082  ** FUSE PANEL  11xx     Alarm in Fuse panel

Alarm Level: Major

Recovery

  1. Locate the fuse and alarm panel (FAP) indicated in the alarm message.
  2. Look at the set of fuses and find the fuse with the “flag” standing out.
    This indicates the fuse is blown. Replace the fuse with a GMT 3 amp or 1 amp (depending on the type being replaced). See the Installation Manual for the correct fuse type.

    Caution:

    Arbitrarily removing a good fuse will cause all cards serviced by the removed fuse to fail. Verify the fuse output before pulling a fuse that appears to be good.
  3. If no fuses appear to be blown, use a VOM and measure the voltage outputs on the rear of the panel (refer to the Installation Manual for voltage test points).
  4. If the fuse blows again, visually inspect the shelf backplanes for shorts or metallic debris.
  5. If nothing can be found visually, put all cards serviced by the affected fuse out of service with the following command:
    rmv-card:loc=x

    where x is the card location stenciled on the shelf of the system.

  6. Unplug the cards serviced by the affected fuse.
  7. Replace the fuse.
  8. Plug in each card one at a time.
    As each card is plugged in, verify the fuse does not blow. When the fuse does blow, replace the card just plugged in.
  9. Replace the fuse again.
  10. Continue plugging in the remaining cards, verifying the fuse does not blow with each card.
    Each time the fuse does blow, replace the card and continue. There may be more than one card at fault. If you encounter a card which blows the fuse, do not stop the procedure. Continue until all cards have been plugged in. Refer to the Maintenance Manual for card removal/replacement procedures.
  11. If all the cards are plugged in and the fault has cleared, place the affected cards back into service by entering the following command:
    rst-card:loc=x

    where x is the card location stenciled on the shelf of the system.

  12. If this does not clear the fault, contact My Oracle Support (MOS).

3.2.63 0083 - Fuse Panel alarm has cleared

This indicates that the fuse alarm has been cleared.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0083    FUSE PANEL  11xx    Fuse Panel alarm has cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.64 0084 - IP Connection Unavailable

The TCP/IP and SIGTRAN protocols both have an IP layer. This UAM indicates that either a TCP/IP socket or an SCTP/IP (SIGTRAN) association is unavailable.

Example 
RLGHNCXA03W 09-11-06 16:28:08 EST EAGLE5 41.1.0
**  1234.0084 ** IP7CONN LONGSOCKETNAME1 IP Connection Unavailable

Alarm Level: Major

Recovery

There are six recovery procedures for this UAM. The first two procedures are for TCP/IP socket problems; the third procedure is for SCTP/IP (SIGTRAN) problems. Read the UAM to see which entity has been affected, then refer to the following scenarios to help determine which procedure to use:

3.2.64.1 Recovery Procedure for EDCMs running STC GPL
In this scenario, this message typically occurs if STC port does not get a DHCP lease from IMF/ESP side. However, it could also be due to bad hardware or bad port on STC card. This error may be due to mis-configured IMF/ESP switches that may not send DHCP lease to STC card.
  1. Use the rept-stat-card command to view STC status.
    The following is an example of a possible output: 
    tekelecstp 07-05-06 15:40:32 EST  EAGLE 37.0.0

    CARD   VERSION      TYPE      GPL        PST            SST        AST
    1103   128-002-000  STC       ERTHC      IS-NR          Active     -----
      ALARM STATUS       = No Alarms.
      IMTPCI  GPL version = 128-002-000
      BLVXW6  GPL version = 128-002-000
      BLDIAG6 GPL version = 128-002-000
      BLBEPM  GPL version = 128-002-000
      BLCPLD  GPL version = 128-002-000
      IMT BUS A           = Conn
      IMT BUS B           = Conn
      CLOCK A             = Active
      CLOCK B             = Idle
      CLOCK I             = Idle
      MBD BIP STATUS      = Valid
      MOTHER BOARD ID     = EPM A
      DBD STATUS          = Valid
      DBD TYPE            = 1G ENET
      DBD MEMORY SIZE     = 512M
      HW VERIFICATION CODE = ----
      CURRENT TEMPERATURE   =  51C (124F)
      PEAK TEMPERATURE:     =  51C (124F)     [02-09-20 10:48]
      EROUTE % OCCUP     = 0%
      NTP broadcast = VALID
      STC IP PORT A:                         IS-NR          Active     -----
          ALARM STATUS  = No Alarms.
      STC IP PORT B:                         OOS-MT         Unavail    -----
          ALARM STATUS  = **  0084 IP Connection Unavailable
          ERROR STATUS  = DHCP Lease. Physical Link.

    Command Completed.
    If the STC is in service and one of the ports is showing UAM0084, then this port is not getting the address from the DHCP server.
  2. If rept-stat-card shows that both ports are in UAM0084 state then use the netstat –I command to determine if the Ethernet interfaces are up.
    1. If they are up, then IMF/ESP support should be involved to find out why this port is not getting the DHCP.
    2. If the concerned ports are not up, then it could be a hardware issue, replace the card. See the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  3. If the alarm is not cleared, contact My Oracle Support (MOS).
3.2.64.2 Recovery Procedure for DSM with EPAP or ELAP
  1. Use the rep-stat-mps command to obtain MPS status.
    The following is an example of a possible output: 
    > rept-stat-mps

Command Accepted - Processing
   peliscaa00w 04-08-13 11:11:04 EDT EAGLE 29.0.2-46.33.1
   rept-stat-mps
   Command entered at terminal #2.
;

   peliscaa00w 04-08-13 11:11:04 EDT EAGLE 29.0.2-46.33.1
                      VERSION       PST            SST        AST
   ELAP A             002-002-000   IS-NR          Active     -----
      CRITICAL PLATFORM    ALARM DATA = No Alarms
      MAJOR    PLATFORM    ALARM DATA = No Alarms
      MINOR    PLATFORM    ALARM DATA = No Alarms
      CRITICAL APPLICATION ALARM DATA = No Alarms
      MAJOR    APPLICATION ALARM DATA = No Alarms
      MINOR    APPLICATION ALARM DATA = No Alarms
             ALARM STATUS       = No Alarms.
                      VERSION       PST            SST        AST
   ELAP B             002-002-000   IS-NR          Standby    -----
      CRITICAL PLATFORM    ALARM DATA = No Alarms
      MAJOR    PLATFORM    ALARM DATA = No Alarms
      MINOR    PLATFORM    ALARM DATA = No Alarms
      CRITICAL APPLICATION ALARM DATA = No Alarms
      MAJOR    APPLICATION ALARM DATA = No Alarms
      MINOR    APPLICATION ALARM DATA = No Alarms
             ALARM STATUS       = No Alarms.
   CARD   PST          SST         LNP STAT
   1101 P IS-NR        Active      ACT
   1103   IS-NR        Active      ACT
   CARD 1101 ALARM STATUS = No Alarms.
     DSM PORT A:      ALARM STATUS       = **  0084 IP Connection Unavailable
     DSM PORT B:      ALARM STATUS       = **  0084 IP Connection Unavailable
   CARD 1103 ALARM STATUS = No Alarms.
     DSM PORT A:      ALARM STATUS       = **  0084 IP Connection Unavailable
     DSM PORT B:      ALARM STATUS       = **  0084 IP Connection Unavailable
   Command Completed.
  2. Use the rept-stat-db:display=all:db=mps to determine the “LEVEL” on the DSM cards are not incrementing.
    The following is an example of a possible output: 
    > rept-stat-db:display=all:db=mps
 
  Command Accepted - Processing
   peliscaa00w 04-08-13 11:14:32 EDT EAGLE 29.0.2-46.33.1
   rept-stat-db:display=all:db=mps
   Command entered at terminal #2.
;

   peliscaa00w 04-08-13 11:14:32 EDT EAGLE 29.0.2-46.33.1

                   ELAP A  ( ACTV )
                    C  BIRTHDATE          LEVEL       EXCEPTION
                    -  -----------------  ----------  --------------
   RTDB             Y  04-08-13 02:32:02        1264        -
   RTDB-EAGLE          04-08-13 02:29:22        1264        -

                   ELAP B ( STDBY )
                    C  BIRTHDATE          LEVEL       EXCEPTION
                    -  -----------------  ----------  --------------
   RTDB             Y  04-08-13 02:32:02        1264        -
   RTDB-EAGLE          04-08-13 02:29:22        1264        -
 
                   EAGLE RTDB REPORT
   CARD/APPL  LOC   C  BIRTHDATE          LEVEL       EXCEPTION
   ---------  ----  -  -----------------  ----------  --------------
   VSCCP      1101  Y  04-08-13 02:29:22        1108        -
   VSCCP      1103  Y  04-08-13 02:29:22        1108        -
  3. Execute rept-stat-trbl:display=timestamp to see if all of the UAM 0084 occurred at nearly the same time.
    If all of the DSMs are reporting IP connection unavailable and all of the alarms came in at one time, check whether the associated EPAP or ELAP has a problem. If so, go to 7.
  4. Perform the following to verify IP network connectivity.
    1. Use the following command to ping the local host:
      pass:loc=XXXX:cmd=”ping 127.0.0.1”

      This is the loopback address and testing it will indicate if networking support is functioning.

    2. Ping the MPS using:
      pass:loc=XXXX:cmd=”ping 192.168.120.100” for 100 Megabit Network
      pass:loc=XXXX:cmd=”ping 192.168.120.200” for 100 Megabit Network
      pass:loc=XXXX:cmd=”ping 192.168.121.100” for 10 Megabit Network
      pass:loc=XXXX:cmd=”ping 192.168.121.200” for 10 Megabit Network

      Example of a possible output: 

      192.168.120.100 for EPAP A, via DSM Port A / 100 Megabit Network
192.168.120.200 for EPAP B, via DSM Port A / 100 Megabit Network,
192.168.121.100 for EPAP A, via DSM Port B / 10 Megabit Network,
192.168.121.200 for EPAP B, via DSM Port B / 10 Megabit Network
    3. If the ping command is not working, verify the IP network cabling.

      Note:

      The network between the MPS and the DSMs is a private network.
    4. Replace the DSM card if you can’t ping the local host and the IP network has been verified.

      See the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

      Note:

      This step applies to a single DSM having IP connection unavailable.
  5. If all of the DSMs are reporting IP connection unavailable, reboot the "primary" DSM card. If no primary card is available go to 3. If only one card is reporting IP connection unavailable, use the init command to take down the card and reload it. See the Commands Manual for the INIT-CARD command.
  6. Power cycle the hubs between the MPS and the EAGLE STP.
  7. Task to be completed by either the customer or an Engineer from the LSMS/MPS group: Run a syscheck on the EPAP or ELAP.
  8. Task to be completed by either the customer or an Engineer from the LSMS/MPS group: Switch activity on the EPAP or ELAP.

    If this action does not clear the alarm, continue to 9.

  9. Task to be completed by either the customer or an Engineer from the LSMS/MPS group: Stop and restart the software on the EPAP or ELAP.

    In case of failure of the Active EPAP, the Standby EPAP takes over the role of Active EPAP and continues to provision the database. If the main DSM network fails, the Active EPAP switches to the backup DSM network to continue provisioning the Service Module cards. The switchover to the backup DSM network is possible only when all connectivity is lost on the main DSM network. In case of HUB failure, impact on the provisioning may be partial, so switchover to the backup provisioning network might not be automatically triggered. At any given time, there is only one Active EPAP using one DSM network per EPAP system.

    If this action does not clear the alarm, continue to 10.

  10. If these steps do not clear the fault, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
When the IP connection recovers you will see an IP Connection Available message. 
UAM: 
1481.0085    DSM A   1101          IP Connection Available
1482.0085    DSM B   1101          IP Connection Available
3.2.64.3 Recovery Procedure for IPLMx, IPGWx, and IPSG
  1. Enter the rept-stat-card:loc=<location>:mode=full command.
    Example of command and possible output: 
    rept-stat-card:loc=1301:mode=full
    Command entered at terminal #3.
;

    eagle10212 01-05-27 07:44:48 EST   ??.?.?-63.18.0
    CARD   VERSION      TYPE      GPL        PST            SST        AST
    1301   067-018-000  DCM       IPLIM      IS-NR          Active     -----
      ALARM STATUS       = No Alarms.
      BPDCM   GPL version = 133-009-000
      IMT BUS A           = Conn
      IMT BUS B           = Conn
      CLOCK A             = Active
      CLOCK B             = Idle
      CLOCK I             = Idle
      MBD BIP STATUS      = Valid
      MOTHER BOARD ID     = SS EDCM
      DBD STATUS          = Valid
      DBD TYPE            = None
      DBD MEMORY SIZE     = 0M
      HW VERIFICATION CODE = ----
      SIGNALING LINK STATUS
          SLK    PST                LS            CLLI
          A      OOS-MT             e3e4          -----------
          B      OOS-MT             e3e4          -----------
      IPLNK STATUS
          IPLNK IPADDR STATUS PST
          A 10.254.110.9 DOWN OOS-MT
          B      192.168.51.14      UP         IS-NR
      ASSOCIATION STATUS
          ANAME PST SST
          ipl1301a OOS-MT CONNECTING
          ipl1301b OOS-MT CONNECTING
      TVG STATUS
          SNM     TVG RESULT   = 24 hr: G-----, 5 min: ------
          SCCP    TVG RESULT   = 24 hr: ------, 5 min: ------
          INM     TVG RESULT   = 24 hr: G-----, 5 min: ------

    Command Completed.
  2. If the hardware interface is down, there is nothing more you can do. Contact the far end, which is where the problem must be resolved. If the hardware interface is up, execute the following commands to get more troubleshooting information:
    1. Errors (collisions, etc.) on the network interface?

      netstat -d 0/1t

    2. Far end reachable?

      ping

      traceroute

    3. Near end and far end use same SCTP CRC?

      netstat –p sctp

      rtrv-sg-opts

  3. Failure at the lower IP level causes problems for the Application Servers (AS) higher in the SCTP/IP stack, so you can use the rep-stat-as command to get more information about the association status.
  4. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
3.2.64.4 Recovery Procedure for MCP or MCPHC
In this scenario, the message typically occurs if the Measurements application loses the connection with the measurements FTP server. The error could be caused by a network connectivity problem or a misconfiguration of the FTP server parameters.
  1. Enter the rtrv-ftp-serv command. If a measurement server is listed, verify the parameters.
    Example of command and possible output: 
    rtrv-ftp-serv
    Command entered at terminal #6.
;

    e1061001 11-09-30 02:31:38 MST  EAGLE5 44.0.0-64.10.0

    APP       IPADDR           LOGIN            PRIO  PATH
    --------  ---------------  ---------------  ----  ----
    meas      10.241.14.62     eagleuser        1     /meas/reports

    FTP SERV table is (1  of 10)  10% full
  2. If the output does not show an entry for the meas application, configure a measurements FTP server in accordance with the “Adding an FTP Server” procedure in Database Administration Manual - System Management to clear the alarm.
  3. Verify connectivity with the FTP server with the ping command. Enter the pass:loc=<mcp>:cmd=”ping <server ipaddr>” command.
    Example of command and possible output: 
    > pass:loc=1105:cmd="ping 10.241.14.62"

Command Accepted - Processing

    e1061001 11-09-30 02:53:17 MST  EAGLE5 44.0.0-64.10.0
    pass:loc=1105:cmd="ping 10.241.14.62"
    Command entered at terminal #6.
;

    e1061001 11-09-30 02:53:17 MST  EAGLE5 44.0.0-64.10.0
    PASS: Command sent to card
;

    e1061001 11-09-30 02:53:17 MST  EAGLE5 44.0.0-64.10.0

    PING command in progress

;

    e1061001 11-09-30 02:53:18 MST  EAGLE5 44.0.0-64.10.0

;

    e1061001 11-09-30 02:53:20 MST  EAGLE5 44.0.0-64.10.0
    PING 10.241.14.62: 56 data bytes
    64 bytes from 10.241.14.62: icmp_seq=0. time=5. ms
    64 bytes from 10.241.14.62: icmp_seq=1. time=5. ms
    64 bytes from 10.241.14.62: icmp_seq=2. time=5. ms
    ----10.241.14.62 PING Statistics----
    3 packets transmitted, 3 packets received, 0% packet loss
    round-trip (ms)  min/avg/max = 5/5/5

    PING command complete.
    If the ping test fails, verify the physical network connectivity between the Eagle and the FTP server.
  4. If the ping command is successful, attempt to transfer a file to the FTP server. Enter the pass:loc=<mcp>:cmd=”ftptest –a meas” command.
    Example of command and possible output: 
    > pass:loc=1105:cmd="ftptest -a meas"
Command Accepted - Processing
    e1061001 11-09-30 02:56:02 MST  EAGLE5 44.0.0-64.10.0
    pass:loc=1105:cmd="ftptest -a meas"
    Command entered at terminal #6.
;
    e1061001 11-09-30 02:56:02 MST  EAGLE5 44.0.0-64.10.0
    PASS: Command sent to card
;
    e1061001 11-09-30 02:56:02 MST  EAGLE5 44.0.0-64.10.0
    FTPTEST: Command In Progress
;
    e1061001 11-09-30 02:56:02 MST  EAGLE5 44.0.0-64.10.0
    FTP Interface Test
       Test Results: PASS
       Server IP:    10.241.14.62
       FTP Error:    0
       Segment:      190004fa
       Diag Msg:

    FTPTEST: Command Complete.
  5. If the alarm is not cleared, try the FTP from another system and verify the login and directory. If this is unsuccessful, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
3.2.64.5 Recovery Procedure for OAMHC
In this scenario, the message typically occurs if the Measurements application or the SNMP application loses the connection with the measurements host server. The error could be caused by a network connectivity problem or a misconfiguration of the server parameters.
  1. Enter the rtrv-ctrl-feat command.
    Example of command and possible output: 
    rtrv-ctrl-feat
Command entered at terminal #4.
;

tekelecstp1 12-09-22 01:53:11 EST  EAGLE5 45.0.0-64.42.0
The following features have been permanently enabled:

Feature Name              Partnum   Status Quantity
Routesets                 893006405 on     10000
Telnet                    893005701 on     ----
EAGLE5 Product            893007101 on     ----
HC-MIM SLK Capacity       893012707 on     64
EAGLE OA&M IP Security    893400001 on     ----
Integrated Measurements   893037301 on     ----
EAGLE SNMP                893040401 on     ----
  2. If the Integrated Measurements feature is enabled, perform Recovery Procedure for Integrated Measurements. If the Eagle SNMP feature is enabled, perform Recovery Procedure for SNMP.
3.2.64.5.1 Recovery Procedure for Integrated Measurements
In this scenario, the message typically occurs if the Integrated Measurements application loses the connection with the measurements FTP server. The error could be caused by a network connectivity problem or a misconfiguration of the FTP server parameters.
  1. Enter the rtrv-ftp-serv command. If a measurement server is listed, verify the parameters.
    Example of command and possible output: 
    rtrv-ftp-serv
Command entered at terminal #6.
;
e1061001 12-09-30 02:31:38 EST EAGLE5 45.0.0-64.44.0
APP      IPADDR          LOGIN           PRIO PATH
-------- --------------- --------------- ---- ----
meas     10.241.14.62    eagleuser       1    /meas/reports
FTP SERV table is (1 of 10) 10% full
  2. If the output does not show an entry for the meas application, configure a measurements FTP server in accordance with the “Adding an FTP Server” procedure in Database Administration Manual - System Management to clear the alarm.
  3. Verify connectivity with the FTP server with the ping command. Enter the pass:loc=[1113 | 1115]:cmd="ping <server ipaddr>" command.
    Example of command and possible output: 
    > pass:loc=1105:cmd="ping 10.241.14.62"

Command Accepted - Processing

    e1061001 11-09-30 02:53:17 MST  EAGLE5 44.0.0-64.10.0
    pass:loc=1105:cmd="ping 10.241.14.62"
    Command entered at terminal #6.
;

    e1061001 11-09-30 02:53:17 MST  EAGLE5 44.0.0-64.10.0
    PASS: Command sent to card
;

    e1061001 11-09-30 02:53:17 MST  EAGLE5 44.0.0-64.10.0

    PING command in progress

;

    e1061001 11-09-30 02:53:18 MST  EAGLE5 44.0.0-64.10.0

;

    e1061001 11-09-30 02:53:20 MST  EAGLE5 44.0.0-64.10.0
    PING 10.241.14.62: 56 data bytes
    64 bytes from 10.241.14.62: icmp_seq=0. time=5. ms
    64 bytes from 10.241.14.62: icmp_seq=1. time=5. ms
    64 bytes from 10.241.14.62: icmp_seq=2. time=5. ms
    ----10.241.14.62 PING Statistics----
    3 packets transmitted, 3 packets received, 0% packet loss
    round-trip (ms)  min/avg/max = 5/5/5

    PING command complete.
    If the ping test fails, verify the physical network connectivity between the Eagle and the FTP server.
  4. If the ping command is successful, attempt to transfer a file to the FTP server. Enter the pass:loc=[1113 | 1115]:cmd="ftptest -a meas"command.
    Example of command and possible output: 
    > pass:loc=1113:cmd="ftptest -a meas"

Command Accepted – Processing

e1061001 12-09-30 02:56:02 EST EAGLE5 45.0.0-64.44.0
pass:loc=1113:cmd="ftptest -a meas"
Command entered at terminal #6.
;

e1061001 12-09-30 02:56:02 EST EAGLE5 45.0.0-64.44.0
PASS: Command sent to card
;

e1061001 12-09-30 02:56:02 EST EAGLE5 45.0.0-64.44.0
FTPTEST: Command In Progress
;

e1061001 12-09-30 02:56:02 EST EAGLE5 45.0.0-64.44.0
FTP Interface Test
   Test Results: PASS
   Server IP: 10.241.14.62
   FTP Error: 0
   Segment: 190004fa
   Diag Msg:

FTPTEST: Command Complete.
  5. If the alarm is not cleared, try the FTP from another system and verify the login and directory. If this is unsuccessful, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
3.2.64.5.2 Recovery Procedure for SNMP
In this scenario, the message typically occurs if the SNMP application loses the connection with the host servers. The error could be caused by a network connectivity problem or a misconfiguration of the SNMP server parameters.
  1. Enter the rtrv-snmp-host command. If server is listed, verify the parameters.
    Example of command and possible output: 
    rtrv-snmp-host
Command entered at terminal #6.
;

e1061001 12-09-30 08:58:40 EST  EAGLE5 45.0.0-64.44.0
IPADDR   10.25.60.20
  HOST      snmp-host-houston
  CMDPORT   161
  TRAPPORT  162
  HB        60
  TRAPCOMM  public

IPADDR   10.25.60.19
  HOST      snmp-host-dallas
  CMDPORT   161
  TRAPPORT  162
  HB        60
  TRAPCOMM  public

SNMP HOST table is (2 of 2) 100% full
  2. If the output does not show a configured SNMP host entry, configure an SNMP host in accordance with the “Adding an FTP Server” procedure in Database Administration Manual - System Management to clear the alarm.
  3. Verify connectivity with the host servers with the ping command. Enter the pass:loc=[1113 | 1115]:cmd="ping <server ipaddr>" command.
    Example of command and possible output: 
    > pass:loc=1113:cmd="ping 10.25.60.20"

Command Accepted – Processing

e1061001 12-09-30 02:53:17 EST EAGLE5 45.0.0-64.44.0
pass:loc=1113:cmd="ping 10.25.60.20"
Command entered at terminal #6.
;

e1061001 12-09-30 02:53:17 EST EAGLE5 45.0.0-64.44.0
PASS: Command sent to card
;

e1061001 12-09-30 02:53:17 EST EAGLE5 45.0.0-64.44.0
PING command in progress
;

e1061001 12-09-30 02:53:18 EST EAGLE5 45.0.0-64.44.0
;

e1061001 12-09-30 02:53:20 EST EAGLE5 45.0.0-64.44.0
PING 10.25.60.20: 56 data bytes
64 bytes from 10.25.60.20: icmp_seq=0. time=5. ms
64 bytes from 10.25.60.20: icmp_seq=1. time=5. ms
64 bytes from 10.25.60.20: icmp_seq=2. time=5. ms
----10.25.60.20 PING Statistics----
3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 5/5/5

PING command complete.
    If the ping test fails, verify the physical network connectivity between the EAGLE and the host servers.
  4. If the alarm is not cleared, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.65 0085 - IP connection available

IP system: This message indicates that for an IPLIM, MCP, MCPHC, OAMHC, or SS7IPGW link, one or more connections have been opened for SS7 traffic. IPLIM hosts multiple links, and each link corresponds to exactly one connection. SS7IPGW also hosts multiple links, but each link may have more than one corresponding connection.

EAGLE 5 ISS system: This indicates that a previously broken link with either the far end (external customer link) or between the SIGRAN card and the far end now exists and is functioning properly. This UAM is also used to indicate that a previously broken link between the EPAP and DSM card is now functioning properly.

Example 
station1234 09-11-06 16:28:08 EST EAGLE5 41.1.0
    1234.0085    IP7CONN LONGSOCKETNAME1 IP Connection Available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.66 0086 - IP Connection Congested

This message indicates that an IP application socket or association is congested. The card's memory has been exceeded, so the card cannot process all of the MSUs being received.

In addition to the basic number of MSUs the card is rated to handle, other factors that affect the card's capacity such as the number of connections sharing the card. Network conditions can cause extra memory to be consumed as the card stores MSUs while waiting for acknowledgments from the far end.

Note:

IP Connection UAMs 0086 (Congested), 0535 (Restricted), and 0536 (Excess Retransmits) conditions can occur simultaneously. However, only one alarm per device can be displayed at a time. If two or more are present, the display of these alarms is prioritized as follows:
  1. 0086 - IP Connection Congested (MSUs are being dropped)
  2. 0536 - IP Connection Excess Retransmits (MSUs may be dropped. The EAGLE 5 ISS sustains a certain rate of dropped MSUs without triggering this alarm, then issues UIM 0536 when that rate is exceeded.)
  3. 0535 - IP Connection Restricted (MSUs are being transmitted at reduced rate. A path of a multi-homed association has failed. )
Example 
RLGHNCXA03W 99-04-10 16:28:08 EST EAGLE5 41.1.0
0046.0086  * IP7CONN LONGSOCKETNAME1 IP Connection Congested

Alarm Level: Minor

Recovery

  1. Use your company procedures to check the network.
  2. Reports on status can be obtained for each SIGTRAN card with the following commands:
    • rept-stat-applsock displays the status of the IP application sockets.
    • rept-stat-ls displays the status of the MTP linksets.
    • rept-stat-slk displays the status of the MTP signaling links.
    • pass:loc=xxxx:cmd=”sockrtt” displays the application socket statistical data.
    • pass:loc=xxxx:cmd=”netstat -i” displays TCP/IP network statistical information for all interfaces.
    • pass:loc=xxxx:cmd=”netstat -p tcp” displays TCP/IP network statistical information for the transmission control protocol.
    • pass:loc=xxxx:cmd=”netstat -p udp” displays TCP/IP network statistical information for the user datagram protocol.
    • pass:loc=xxxx:cmd=”netstat -p ip” displays TCP/IP network statistical information for the internet protocol.
    • pass:loc=xxxx:cmd=”netstat -p icmp” displays TCP/IP network statistical information for the internet control message protocol.
    • pass:loc=xxxx:cmd=”netstat -m” displays TCP/IP network statistical information for buffer pools.
    • pass:loc=xxxxx:cmd="sctp -a xxxxx" displays SS7-over IP (SIGTRAN) troubleshooting information.
      For example, to see the information for the location 1301 and the entity ipl1301a, enter 
      pass:loc=1301:cmd="sctp -a ipl1301a"
  3. Is SCTP buffering set correctly for network RTT?

    rtrv-assoc

    assocrtt pass command

    sctp pass command

  4. Is IPTPS set correctly for IPGWx?

    rept-stat-iptps

    rtrv-ls

  5. Is an interface set to half-duplex somewhere in the path to the far end, causing excessive retransmissions?

    rtrv-ip-lnk

    sctp pass command

  6. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.67 0087 - IP Connection manually removed

This message indicates that an IP application socket has been manually removed from the system.

Example 
RLGHNCXA03W 99-04-10 16:28:08 EST EAGLE 35.0.0.0
0046.0087    IP7 LONGSOCKETNAME1 IP Connection manually removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.2.68 0088 - Clocks A and B TSCs are Out of Sync

It was detected by the OAM that clocks A and B have been out of synch for a excessive period of time. This alarm indicates the clock sources being used for TSCSYNC feature have failed or a hardware failure in the OAM card. This may impact the EAGLE Integrated Monitoring Support feature functionality.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0088 ** CARD 1113 EOAM   Clocks A and B are out of sync

Alarm Level: Major

Recovery

  1. Check the status of the OAM card by entering the following command:
    rept-stat-card:loc=xxxx

    where xxxx is the card location in the output.

  2. Verify the status of the system clocks with the rept-stat-clock command. If Eagle is reporting the clock alarm indicating a problem with clock sources, then check the status of the clock sources, the cables, and termination points. Refer to Clock System Alarms for additional details on handling clock-specific UAMs.
  3. Reseat the OAM card.
  4. If the problem persists, replace the OAM card.
    Refer to Maintenance Manual for card removal/replacement procedures.

3.2.69 0089 - Clocks A and B TSCs are resynchronized

A previous GPSM-II card fault is cleared.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0089    CARD 1113 EOAM    Clocks A and B TSCs are resynchronized

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.70 0092 - MDAL Not Responding

This message indicates a problem with the maintenance disk and alarm card (MDAL).

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
*C 0014.0092 *C CARD 1117 MDAL       MDAL not responding

Alarm Level: Critical

Recovery

  1. Check the status of the MDAL card by entering the command:
    rept-stat-card:loc=x

    where x is the card location stenciled on the shelf of the system.

    Example of the output using card location 1117: 
    RLGHNCXA03W 00-09-27 16:43:42 EST
CARD   VERSION    TYPE    APPL      PST           SST       AST
1117  ----------- MDAL    --------  OOS-MT        Isolated  -----
Command Completed.
  2. Reseat the MDAL card.
  3. If the problem persists, replace the MDAL card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.71 0093 - MDAL alarm cleared

A previous maintenance disk and alarm card (MDAL) card fault is cleared.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0093    CARD 1117 MDAL       MDAL alarm cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.72 0096 - Card has been Reloaded

The indicated card has been reinitialized and reloaded with the appropriate data. This occurs as a result of a manual reset or software maintenance intervention.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0096    CARD 1218 SS7ANSI   Card has been reloaded

Alarm Level: No alarm condition. The message is informational only.

Recovery

Look for other reports associated with the indicated card.

If an obituary report exists, the card malfunctioned. If this happens continuously, replace the defective card. If this is only an occasional condition, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA. Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.73 0097 - IMT allowed

The IMT bus has been returned to service.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0097    IMT SYSTEM            IMT allowed
             Card 1101, 1102, 1107, 1108

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected. No further action is necessary

3.2.74 0098 - IMT inhibited

The IMT bus has been removed from service by using the rmv-imt:bus=x command. The bus is no longer available to carry traffic.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0098    IMT SYSTEM        IMT inhibited
             Card 1101, 1102, 1107, 1108

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify the bus is not inhibited for maintenance purposes.
    If the bus has been inhibited for maintenance purposes, consult with the technician responsible before placing it back into service.

    Caution:

    The IMT bus should not be left inhibited, as this may affect system performance.
  2. If the IMT bus has not been inhibited for maintenance, or the maintenance is complete, enter the following command to place the IMT back into service:
    rst-imt:bus=x

    where x is the IMT bus to be returned to service.

3.2.75 0099 - Incompatible HW for Provisioned Slot

An MPL card is in a slot provisioned for a different card type and application. The card is automatically inhibited.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0099  ** CARD 1201  SS7ANSI  Incompatible HW for provisioned slot
                HW VERIFICATION CODE: xxx

Alarm Level: Major

Recovery

  1. If this message contains the optional line HW VERIFICATION CODE: xxx:
    1. See Hardware Verification Codes in UAMs the section on hardware verification codes in the Unsolicited Alarms and Information Messages manual and decode the xxx value.
      Correct the indicated problem. A card with Verification Code 002, 003, 004, or 102 may possibly begin to boot continually before this alarm is displayed.
    2. After correcting the problem, the card will be in out-of-service maintenance-disabled state (OOS-MT-DSBLD).
      Restore the card back to in-service normal state (IS-NR) with the alw-card command.
  2. If this message does not contain the optional line ‘HWVERIFICATIONCODE: xxx’, perform either of the following steps:
    1. Replace the MPL card with a DCM card.
      Refer to the Maintenance Manual for card removal/replacement procedures.
    2. Re-provision the slot for a LIMDS0 card.
      Refer to the Database Administration Manual - System Management manual for the correct procedures.

3.2.76 0102 - Motherboard BIP Invalid

The motherboard in the location indicated has an invalid Board ID Prom (BIP).

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0102  * CARD 1201 SS7ANSI   Motherboard BIP invalid

Alarm Level: Minor

Recovery

  1. The indicated card must be reprogrammed.
    Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA. You will need to know the part number, revision level, and serial number of the card.
  2. The card can be reprogrammed with instructions from unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA, or unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA can dial into the system and reprogram the card remotely.

3.2.77 0103 - Motherboard BIP Valid

The Board ID Prom (BIP) for the specified motherboard is correctly programmed.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0103    CARD 1201 SS7ANSI   Motherboard BIP valid

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.78 0106 - IMT Bus Alarm Cleared

The specified IMT bus has recovered from a fault.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0106    IMT BUS A          IMT Bus alarm cleared
             Card 1101, 1102, 1107, 1108

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.79 0107 - Minor IMT Failure Detected

A minor fault has been detected on one of the IMT buses. A minor fault consists of at least one card fault but no more than two card faults.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0107  * IMT BUS A                Minor IMT failure detected
                Card 1101, 1102

Alarm Level: Minor

Recovery

  1. Visually check the IMTLEDS on the front of the cards.
    A red LED or LEDs denotes an IMT fault. If the top LED of the pair is red, there is a fault on IMT A. If the bottom LED is red, there is a fault on IMT B. See Figure 3-2.

    Figure 3-2 Card LEDs

    img/t_uam0107_corrective_procedure_maintmanual_fig1.jpg
  2. Note the card location or locations for cards with a red LED(s).
  3. Using the card location(s) noted in 2, enter the following command to connect the card back to the IMT:
    conn-imt : loc =x : bus = y

    where x is the card location stenciled on the shelf of the system and y is the IMT bus to be returned to service.

    The following message appears using card location 1106 and IMT bus A: 
    RLGHNCXA03W 00-02-07 11:02:30 EST  EAGLE 35.0.0
    Connect IMT Bus A command issued to card 1106
  4. If the fault does not clear, reseat the affected card.

    warning:

    Reseating or replacing a LIM will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  5. If the fault does not clear, replace the affected card.
  6. If the fault does not clear, replace the IPMX card servicing the affected card.

    warning:

    Replacing an IPMX card causes the IMT to go down. (IPMX in Slot 09 affects IMT A and IPMX in Slot 10 affects IMT B.) Do not perform this step if the other bus also has a fault. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  7. If the fault has cleared and any of these cards are LIMs, place the links assigned to these cards back into service using the act-slk command.
  8. If these steps do not clear the fault, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.80 0108 - Major IMT Failure Detected

A major fault has been detected on one of the IMT buses. A major fault consists of three or more faults on the IMT bus.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0108 ** IMTBUS A      Major IMT failure detected
                Card 1101, 1102, 1107, 1108

Alarm Level: Major

Recovery

  1. Enter the following command to check the status of the IMT:
    rept-stat-imt

    If the entire IMT is down, continue with 6.

  2. Visually check the IMTLEDS on the front of the cards.
    A red LED or LEDs denotes an IMT fault. If the top LED of the pair is red, there is a fault on IMT A. If the bottom LED is red, there is a fault on IMT B. See Figure 3-3.

    Figure 3-3 Card LEDs

    img/t_uam0108_corrective_procedure_maintmanual_fig1.jpg
  3. Note the card location or locations for cards with a red LED(s).
  4. Using the card location(s) noted in 3 enter the following command to connect the card(s) back to the IMT:
    conn-imt : loc =x : bus = y

    where x is the card location stenciled on the shelf of the system, and y is the IMT bus to be returned to service.

    The following message appears using card location 1106 and IMT bus A: 
    RLGHNCXA03W 00-02-07 11:02:30 EST  EAGLE 35.0.0
    Connect IMT Bus A command issued to card 1106
  5. If the connection command is successful, the Card connected message appears. 
    RLGHNCXA03W 00-02-07 11:02:30 EST  EAGLE 35.0.0
    0100.0006    IMT   BUS A         Card connected to IMT
  6. If the fault does not clear, enter the following command:
    inh-imt:bus=x

    where x = faulty IMT bus.

    warning:

    This command removes the faulty IMT bus from service, causing all cards to disconnect from the designated bus. 8 must be completed once 6 is performed. If the technician has any questions about using this command, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  7. Enter the following command to test the IMT bus:
    tst-imt:bus=x

    where x = the inhibited IMT bus.

    An example of the output follows: 
    RLGHNCXA03W 97-09-27 12:47:07 EST EAGLE 35.0.0
IMT Fault Isolation Bus B
Fault Location    Probable Cause  Failure(s)
Card  1201        Card 1201
                                  Pass-through Test Failed
Card  1301        Card 1301
                                  Pass-through Test Failed

    Note:

    When tst-imt completes, either through normal termination of the command or because the command is aborted, uam-and-uim-troubleshooting-procedures1.html MUST be completed.
  8. Enter the following command to change the state of inhibited IMT to IS-ANR:
    alw-imt:bus=x

    where x = the inhibited IMT bus.

  9. Reseat the affected card(s).
    Probable causes are listed in order of most probable to least probable. The listed components should be reseated in order listed by the output of the tst-imt command.

    warning:

    Reseating or replacing a LIM will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  10. If the fault does not clear, replace the affected card(s).
    Probable causes are listed in order of most probable to least probable. The listed components should be replaced in order listed by the output of the tst-imt command.
  11. If the fault does not clear, replace the IPMX card servicing the affected card(s).

    Caution:

    Replacing an IPMX card causes the IMT to go down. (IPMX in Slot 09 affects IMT A and IPMX in Slot 10 affects IMTB.)
  12. If the fault has cleared and any of these cards are LIMs, place the links assigned to these cards back into service using the act-slk command.
  13. If these steps do not clear the fault, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.81 0109 - All IMT System Level Alarms Cleared

Both IMT busses are functioning.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0109    IMT SYSTEM           All IMT System level alarms cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.82 0110 - Failure Detected on One IMT bus

A fault has been detected on one IMT bus.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0110  * IMT SYSTEM          Failure detected on one IMT bus

Alarm Level: Minor

Recovery

  1. Visually check the IMT LEDS on the front of the cards.
    A red LED or LEDs denotes an IMT fault. If the top LED of the pair is red, there is a fault on IMT A. If the bottom LED is red, there is a fault on IMT B. See Figure 3-4.

    Figure 3-4 Card LEDs

    img/t_uam0110_corrective_procedure_maintmanual_fig1.jpg
  2. Note the card location or locations for cards with a red LED(s).
  3. Using the card location(s) noted in 2, connect the card back to the IMT with the command conn-imt.

    For example, enter:

    conn-imt : loc =x : bus = y

    where x is the card location stenciled on the shelf of the system and y is the IMT bus to be returned to service.

    The following message appears using card location 1106 and IMT bus A : 
    RLGHNCXA03W 00-02-07 11:02:30 EST  EAGLE 35.0.0
    Connect IMT Bus A command issued to card 1106
  4. If the connection command is successful, the Card connected to IMT message appears. 
    RLGHNCXA03W 00-02-07 11:02:30 EST  EAGLE 35.0.0
    0100.0006    IMT   BUS A         Card connected to IMT
  5. If the connection command is not successful and the fault does not clear, reseat the card

    warning:

    Resetting, reseating, or replacing a LIM will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  6. If the fault does not clear, replace the affected card.
  7. If the fault does not clear, replace the IPMX card servicing the affected card.

    warning:

    Replacing an IPMX card causes the IMT to go down. (IPMX in Slot 09 affects IMT A and IPMX in Slot 10 affects IMT B.) Do not perform this step if the other bus also has a fault. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  8. If the fault has cleared and any of these cards are LIMs, place the links assigned to these cards back into service using the act-slk command.
  9. If these steps do not clear the fault, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.83 0111 - Failure on Both IMT A and IMT B

A major fault occurred on one IMT bus and a minor fault has occurred on the other. Or, there is a minor fault on both IMT buses. A minor fault occurs when one or two cards are disconnected from the IMT bus. A major fault occurs when three or more cards are disconnected from the IMT bus.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0111 ** IMT SYSTEM          Failure on both IMT A and IMT B

Alarm Level: Major

Recovery

Check the status of the IMTs by entering the rept-stat-imt command.

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.84 0112 - Major Failures Detected on Both IMTs

Major faults have been detected on both IMT buses.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
* C0100.0112 *C IMT SYSTEM        Major failures detected on both IMTs

Alarm Level: Critical

Recovery

Check the status of the IMTs by entering the rept-stat-imt command.

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.85 0113 - Clock alarm(s) Cleared

All primary and secondary clock sources are functioning.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0113    CLOCK SYSTEM        Clock alarm(s) cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.86 0115 - Linkset IP TPS Threshold Exceeded

This message indicates that the actual linkset transaction rate exceeds the provisioned linkset IPSG TPS.

This message indicates that the actual linkset transaction rate exceeds the linkset capacity alarm threshold defined by lsusealm, tpsalmtype, slktps (rsvdslktps or maxslktps based on tpsalmtype) parameters and the number of links in the linkset.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0115 **   LSN lsgw1103   Linkset IP TPS threshold exceeded

Alarm Level: Major

Recovery

  1. Enter this command to display the current and peak IPSG TPS utilization of the linkset specified in the output: rept-stat-iptps
    Example of the output: 
    eagle10115 03-05-06 09:49:20 EST EAGLE 31.6.0
    IP TPS USAGE REPORT
               THRESH  CONFIG         TPS     PEAK      PEAKTIMESTAMP
    -----------------------------------------------------------------
    SYSTEM
    CLLI1234567  100%  100000  TX:   4127     4550  03-05-05 09:49:19 
                              RCV:   3962     4450  03-05-05 09:49:19
    -----------------------------------------------------------------
    LSN
    LSGW1101      80%    4000  TX:   3700     4000  03-05-05 09:49:19 
                              RCV:   3650     4000  03-05-05 09:49:19
    LSGW1103      80%     500  TX:    427      550  03-05-05 09:49:19 
                              RCV:    312      450  03-05-05 09:49:19
    -----------------------------------------------------------------
    Command Completed.
  2. Enter the rtrv-ls:lsn=xxxxxx command, where xxxxxx is the linkset name, to review current lsusealm, tpsalmtype (TPSALM), rsvdslktps and maxslktps parameter values and the number of links in the linkset: 
    Searching link set table on disk - please wait...

Command Accepted - Processing

    eagle11 16-10-13 12:11:41 EST  EAGLE 46.3.0.0.1-68.27.0
    rtrv-ls:lsn=lab2m2pa
    Command entered at terminal #1.
;

    eagle11 16-10-13 12:11:42 EST  EAGLE 46.3.0.0.1-68.27.0

                                     L3T SLT              GWS GWS GWS
    LSN           APCN   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
    lab2m2pa      02000         none 1   2   no  B   1    off off off no    off

                  SPCN          CLLI         TFATCABMLQ MTPRSE ASL8
               ---------------- -----------  1          ---    ---

               SLSRSB RANDSLS ITUTFR
               1      off     off

               IPSG  IPGWAPC  GTTMODE           CGGTMOD   PCT  CHGMTP3OPC
               yes   no       SysDflt             no      off  on

               ADAPTER    RSVDSLKTPS  MAXSLKTPS
               m2pa       500         500

               TPSALM     LSUSEALM    SLKUSEALM
               rsvdslktps 100%        80%

               LOC  LINK SLC TYPE     ANAME
               1216 A2   0   IPSG     lab2m2pa


    Link set table is (16 of 1024) 2% full.
  3. Refer to the Commands User's Guide to interpret the output.
    If the linkset has adequate bandwidth, then the IP TPS for the linkset can be increased (using the chg-ls command), provided the current IPGWx IPSG system IP TPS setting allows for this. The IP TPS LS alarm threshold percent (lsusealm) can also be adjusted if allowed by the current setting. If the linkset does not have adequate bandwidth, then more links or different routing strategies may be required to correct the problem.

3.2.87 0116 - Link Expected IP TPS Threshold Exceeded

This message indicates that the actual link transaction rate is approaching the link's fair share of provisioned linkset capacity.

This message indicates that the actual link transaction rate exceeds the link capacity alarm threshold defined by slkusealm, tpsalmtype and slktps (rsvdslktps or maxslktps based on tpsalmtype) parameters.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0116  * SLK 1104,A LSA01   Link expected IP TPS threshold exceeded
               SLC=01   FECLLI=A1234567890

Alarm Level: Minor

Recovery

  1. Enter the following command to display the current and peak IPSG TPS utilization of the linkset specified in the output:
    rept-stat-iptps:lsn=xxxxxx

    where xxxxxx is the linkset name as defined in the output.

    Example of the output: 
    eagle10115 03-05-06 09:49:20 EST EAGLE 31.6.0
    IP TPS USAGE REPORT
               THRESH  CONFIG         TPS     PEAK       PEAKTIMESTAMP
    ------------------------------------------------------------------
    LSN
    LSGW1101     100%  188000  TX:    800      800  03-05-05 09:49:19 
                              RCV:    800      800  03-05-05 09:49:19
    ------------------------------------------------------------------
    LOC  PORT
    1101    A     80%    ----  TX:    800      800  03-05-05 09:49:19 
                              RCV:    800      800  03-05-05 09:49:19
    1103    A     80%    ----  TX:    800      800  03-05-05 09:49:19 
                              RCV:    800      800  03-05-05 09:49:19
    ------------------------------------------------------------------
    Command Completed.
  2. Enter the rtrv-ls:lsn=xxxxxx command, where xxxxxx is the linkset name, to review current slkusealm, tpsalmtype (TPSALM), rsvdslktps and maxslktps parameter values: 
    Searching link set table on disk - please wait...

Command Accepted - Processing

    eagle11 16-10-13 12:11:41 EST  EAGLE 46.3.0.0.1-68.27.0
    rtrv-ls:lsn=lab2m2pa
    Command entered at terminal #1.
;

    eagle11 16-10-13 12:11:42 EST  EAGLE 46.3.0.0.1-68.27.0

                                     L3T SLT              GWS GWS GWS
    LSN           APCN   (SS7)  SCRN SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
    lab2m2pa      02000         none 1   2   no  B   1    off off off no    off

                  SPCN          CLLI         TFATCABMLQ MTPRSE ASL8
               ---------------- -----------  1          ---    ---

               SLSRSB RANDSLS ITUTFR
               1      off     off

               IPSG  IPGWAPC  GTTMODE           CGGTMOD   PCT  CHGMTP3OPC
               yes   no       SysDflt             no      off  on

               ADAPTER    RSVDSLKTPS  MAXSLKTPS
               m2pa       500         500

               TPSALM     LSUSEALM    SLKUSEALM
               rsvdslktps 100%        80%

               LOC  LINK SLC TYPE     ANAME
               1216 A2   0   IPSG     lab2m2pa


    Link set table is (16 of 1024) 2% full.
  3. Refer to the Commands User's Guide to interpret the output.
    If the linkset has adequate bandwidth, then the IP TPS for the linkset can be increased (using the chg-ls command), provided the current IPGWx IPSG system IP TPS setting allows for this. The IP TPS SLK alarm threshold percent (slkusealm) can also be adjusted if allowed by the current setting. If the linkset does not have adequate bandwidth, then more links are required to correct the problem.

3.2.88 0118 - Linkset IP TPS Normal

This message indicates the total usage for the linkset TPS rate has fallen below the configured linkset TPS rate.

This message indicates that the actual linkset transaction rate has fallen below the linkset capacity alarm threshold defined by lsusealm, tpsalmtype, slktps (rsvdslktps or maxslktps based on tpsalmtype) parameters and the number of links in the linkset.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0118      LSN lsgw1103   Linkset IP TPS normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.89 0119 - Link IP TPS Normal

This message indicates the total usage for the linkset exceeds the linkset threshold for the linkset’s IP TPS.

This message indicates that the actual link transaction has fallen below the link capacity alarm threshold defined by slkusealm, tpsalmtype and slktps (rsvdslktps or maxslktps based on tpsalmtype) parameters.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
0014.0119    SLK 1104,A LSA01   Link IP TPS normal
             SLC=01   FECLLI=A1234567890

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.90 0120 - ENUM SYSTEM is not available

This message indicates none of the ENUM cards is Active/IS-NR.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
*C  0002.0120 *C ENUM SYSTEM             ENUM SYSTEM is not available

Alarm Level: Critical.

Recovery

Activate (Active/IS-NR) any one of the ENUM cards in the system.

3.2.91 0121 - ENUM SYSTEM is available

This message indicates half or more of the configured ENUM cards are in IS-NR state.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0121    ENUM SYSTEM             ENUM SYSTEM is available

Alarm Level: None. The message is informational only.

Recovery

No further action necessary.

3.2.92 0122 - ENUM SYSTEM normal, card(s) abnormal

This message indicates the Active/IS-NR number of ENUM cards is less than half of the configured ENUM cards.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  0002.0122 ** ENUM SYSTEM             ENUM SYSTEM normal, card(s) abnormal

Alarm Level: Major.

Recovery

Activate (Active/IS-NR) half or more ENUM cards in the system.

3.2.93 0123 - ENUM SYSTEM is removed

This message indicates all the ENUM cards are deleted from the system.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0123    ENUM SYSTEM             ENUM SYSTEM is removed

Alarm Level: None. The message is informational only.

Recovery

No further action necessary.

3.2.94 0124 - ENUM Threshold -Level1 exceeded

This message indicates the card TPS exceeds the configured level-1 value in ENUMOPTS.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
*   0002.0124 *  CARD xxxx ENUMHC        ENUM Threshold -Level1 exceeded

Alarm Level: Minor.

Recovery

Reduce the card TPS below the configured level-1 value in ENUMOPTS.

3.2.95 0125 - ENUM Threshold -Level 2 exceeded

This message indicates the card TPS exceeds the configured level-2 value in ENUMOPTS.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  0002.0125 ** CARD xxxx ENUMHC        ENUM Threshold –Level 2 exceeded

Alarm Level: Major.

Recovery

Reduce the card TPS below the configured level-2 value in ENUMOPTS.

3.2.96 0126 - ENUM Threshold Condition cleared

This message indicates the card TPS has been reduced to below the configured level-1 value in ENUMOPTS.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0126   CARD xxxx ENUMHC        ENUM Threshold Condition cleared

Alarm Level: None. The message is informational only.

Recovery

No further action necessary.

3.2.97 0127 - ENUM card capacity exceeded

This message indicates the card TPS exceeds the maximum allowable TPS (4000) on a single ENUM card.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
*C  0002.0127 *C CARD xxxx ENUMHC        ENUM card capacity exceeded

Alarm Level:Critical

Recovery

Reduce the card TPS below the maximum allowed card TPS.

3.2.98 0128 - All Clocks Have Failed

A fault has been detected on all system clocks.

Example 
RLGHNCXA21W 00-12-07 11:02:30 EST  EAGLE 35.0.0
*C 0100.0128 *C CLOCK SYSTEM        All clocks have failed

Alarm Level: Critical

Recovery

  1. Verify the status of the clock with the rept-stat-clk command.
    If both clocks are idle, check the source clock into the system. Follow local maintenance procedures to repair the source clock.
  2. Verify the clock cables are connected to the shelf backplane (refer to the Installation Manual for cable location).
    If any cables are loose, reconnect the cable.
  3. If the clock source is not at fault, try reseating the TDM cards.
  4. If the message appears again, replace the TDM cards.
    Refer to the Maintenance Manual for card removal/replacement procedures.
  5. If the fault still does not clear, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.99 0129 - ENUM Card TPS is normal

This message indicates the card TPS is normal.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0129   CARD xxxx ENUMHC        ENUM Card TPS is normal

Alarm Level: None. The message is informational only.

Recovery

No further action necessary.

3.2.100 0130 - Card successfully loaded with data

The indicated card has been reloaded by the system with the appropriate GPL and tables.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
0014.0130    CARD 1304 SCCP      Card successfully loaded with data

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.101 0132 - Loading Failed: Table Not Found

This indicates an error in an upgrade procedure. Either an incorrect file or table was entered. This message could also indicate the file or table being loaded is corrupted and is not recognized by the system.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0132  ** CARD 1304 SCCP      Loading failed: table not found

Alarm Level: Major

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.102 0133 - Loading Failed: Data Read Error

An error occurred on the active MASP while data tables were loaded.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0133  ** CARD 1304 SCCP    Loading failed: data read error

Alarm Level: Major

Recovery

  1. To verify that both databases are at the same level and are not corrupted, enter:
    rept-stat-db
    Example output for a corrupted database 
    bothwagm03w 99-01-08 19:52:08 EST EAGLE 35.0.0
    rept-stat-lsms
    Command entered at terminal #1.
;
    bothwagm03w 99-01-08 19:52:08 EST EAGLE 35.0.0
                         GPL          PST             SST          AST
    --------------------------------------------------------------------
    LSMS SYSTEM                       IS-NR           Active       -----
    TDM TRM       8                   IS-NR           Active       -----
    TDM TRM       9                   IS-NR           Active       -----
    OAP          A    023-065-000     IS-NR           Active       -----
    OAP          B    023-065-000     IS-NR           Active       -----
    Q.3 Assoc    A1                   IS-NR           Active       -----
    Q.3 Assoc    B1                   IS-NR           Active       -----
    LSMS SYSTEM ALARM STATUS  = No Alarms.
    OAP A  ALARM STATUS       = No Alarms.
    OAP B  ALARM STATUS       = No Alarms.
    Q.3 Assoc A1 ALARM STATUS = No Alarms.
    Q.3 Assoc B1 ALARM STATUS = No Alarms.
    Command Completed.
  2. To verify the integrity of the database, enter:
    aud-data
  3. If there is a problem with the database, follow the procedures in the Database Administration Manual - System Management for resolving database inconsistencies.
  4. If the problem still exists, contactunresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.103 0134 - Loading Failed: Bad Checksum Returned

The GPL checksum, which is used to verify the data, indicates an error during file transfer. The file (GPL) needs to be downloaded again.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0134  ** CARD 1304 SCCP  Loading failed: bad checksum returned

Alarm Level: Major

Recovery

  1. Reseat the indicated card.
    This may have caused the transmission error.
  2. When the card has been reseated, it attempts to reload automatically.
  3. If the download fails again, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.104 0135 - Loading failed: GPL load timeout

There was a timeout caused by the loading process.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0135  ** CARD 1304 SCCP    Loading failed: GPL load timeout

Alarm Level: Major

Recovery

  1. Verify the card is properly seated.
    If not, reseat the indicated card.
  2. If the card is properly seated, the problem corrects itself.
    No further action is necessary.

3.2.105 0136 - Loading Failed: Data Load Timeout

The download process timed out on the MASP. This could be caused by an improperly programmed BIP on the daughterboard of the card being loaded.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0136  ** CARD 1304 SCCP    Loading failed: data load timeout

Alarm Level: Major

Recovery

  1. Use the rtrv-bip command (debug command) to verify the BIP on the applique of the indicated card.
    Refer to the Commands Manual for details on how to use this command.
  2. If the BIP is invalid, it must be reprogrammed.
    Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA. You will need to know the part number, revision level, and serial number of the card.
  3. The card can be reprogrammed with instructions from unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA, or unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA can dial into the system and reprogram the card remotely.
  4. If the BIP is valid, reseat the card.
    This should correct the problem. If not, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.106 0137 - Loading Failed: Invalid GPL

This message indicates the GPL file is corrupt or there was a failure in the IMT bus.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0137  ** CARD 1304 SCCP   Loading failed: invalid GPL

Alarm Level: Major

Recovery

  1. This problem should correct itself.
  2. If the problem still exists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.107 0138 - Loading failed: GPL format error

This message indicates a corrupted GPL file.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0138  ** CARD 1304 SCCP     Loading failed: GPL format error

Alarm Level: Major

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.108 0139 - Loading Failed: Disk Read Prep Error

This message indicates the GPL version is not current, and incompatible with the system load.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0139  ** CARD 1304 SCCP   Loading failed: disk read prep error

Alarm Level: Major

Recovery

Refer to the upgrade procedure sent with the software.

If this procedure was followed correctly, and the problem still exists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.109 0140 - Loading Failed: Disk Read Response Error

This message indicates there was an error in reading the fixed disk.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0140  ** CARD 1304 SCCP  Loading failed:disk read response error

Alarm Level: Major

Recovery

  1. If the disk was just installed in the system, try the load again.
  2. If the problem occurs again, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.110 0141 - Loading Failed: Disk Read Failed

This message indicates there was a failure while reading the fixed disk on the active TDM.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0141  ** CARD 1304 SCCP     Loading failed: disk read failed

Alarm Level: Major

Recovery

  1. Try the load again.
  2. If the problem persists, replace the TDM with the corrupted media.
    Refer to the Maintenance Manual for card removal/replacement procedures.
  3. If this message appears again, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.111 0142 - System release alarm cleared

The SYSREL.SYS file has been installed on the active fixed disk and the alarm has been cleared.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
0014.0142    GPL SYSTEM OAM     System release alarm clea

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.112 0143 - System release GPL(s) not approved

This message indicates that one or more approved GPLs do not match the version specified in the SYSREL.SYS file.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0143  * GPL SYSTEM OAM       System release GPL(s) not approved

Alarm Level: Minor

Recovery

  1. Use the rtrv-gpl command to display the GPLs on the system.
    The output of the rtrv-gpl command can be used to identify the GPLs that do not match the versions specified in the SYSREL.SYS file.
  2. Use the chg-gpl command to upload the required version of the GPL.
  3. Use the act-gpl command to make the uploaded GPL the approved GPL.

3.2.113 0144 - System Release Version Unknown

This message indicates that a failure has occurred while accessing the SYSREL.SYS file. Either the SYSREL.SYS file could not be found on the active fixed disk or has become corrupted and is not accessible.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST
* 0014.0144  * GPL SYSTEM OAM       System release version unknown

Alarm Level: Minor

Recovery

  1. Insert the system removable cartridge containing the SYSREL.SYS file into the maintenance disk and alarm card (MDAL). For E5-OAM, insert the system removable USB thumb drive containing the SYSREL.SYS file into the REMOVABLE MEDIA slot of the active MASP.
  2. Enter the following command to upload the SYSREL.SYS file from the system removable cartridge to the active fixed disk:
    chg-gpl:gpl=utility:ver<cdu/vcdu GPL version>

    Since the actual name of the utility application is CDU or VCDU, the version CDU/VCDU must be specified for appl=utility.

  3. If this message appears again, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.114 0145 - HS Clock A for Card Failed, B Normal

This indicates that the High Speed clock A signal for the indicated card is not present.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0
* 0053.0145    * CARD 1115 OAM   HS Clock A for card failed, B normal

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the status of the clock.
    The output indicates how many cards are using the specified clock, and how many cards are reporting fault with the specified clock.
    Example of the possible output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.

    Caution:

    Resetting, reseating, or replacing a card will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  2. If only one card is reporting fault, reset the card.
  3. If the fault has not cleared, reseat the card.
  4. If the fault has not cleared, replace the card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  5. If the fault still has not cleared, replace the TDM card in MASP A.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  6. If more than one card is reporting fault with the designated clock, check the clock cable connection at the shelf backplane (refer to the Installation Manual for cable location).
    If the clock cable is at fault, replace the clock cable.
  7. If the fault has cleared and any of these cards are LIMs, place the links assigned to these cards back into service using the act-slk command.

3.2.115 0146 - HS Clock B for Card Failed, A Normal

This indicates the High Speed clock B signal for the indicated card is not present.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0
* 0053.0146    * CARD 1115 OAM   HS Clock B for card failed, A normal

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the status of the clock.
    The output indicates how many cards are using the specified clock, and how many cards are reporting fault with the specified clock.
    Example of the possible output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.

    Caution:

    Resetting, reseating, or replacing a card will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  2. If only one card is reporting fault, reset the card.
  3. If the fault has not cleared, reseat the card.
  4. If the fault has not cleared, replace the card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  5. If the fault still has not cleared, replace the TDM card in MASP B.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  6. If more than one card is reporting fault with the designated clock, check the clock cable connection at the shelf backplane (refer to the Installation Manual for cable location).
    If the clock cable is at fault, replace the clock cable.
  7. If the fault has cleared and any of these cards are LIMs, place the links assigned to these cards back into service using the act-slk command.

3.2.116 0147 - High Speed Clocks A and B for Card Failed

The High Speed A and B clock sources for the indicated card are not present.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0
* 0053.0147  * CARD 1115 OAM   High Speed Clocks A and B for card failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the status of the clocks.
    The output indicates how many cards are using one of the specified clocks, and how many cards are reporting faults.
    Example of the possible output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.

    Caution:

    Resetting, reseating, or replacing a card will cause both links on the card to fail. If the card is a LIM, place the links on the LIM out of service by entering the dact-slk command.
  2. If only one card is reporting fault, reset the card.
  3. If the fault has not cleared, reseat the card.
  4. If the fault has not cleared, replace the card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  5. If the fault still has not cleared, replace the TDM card in MASP B.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  6. If more than one card is reporting fault with the designated clock, check the clock cable connection at the shelf backplane (refer to the Installation Manual for cable location).
    If the clock cable is at fault, replace the clock cable.
  7. If the fault has cleared and any of these cards are LIMs, place the links assigned to these cards back into service using the act-slk command.

3.2.117 0148 - High Speed Clock A for card normal

This indicates that the High Speed clock A signal for the indicated card has returned to a normal, functional state.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0
0053.0148     CARD 1115 OAM   High Speed Clock A for card normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.118 0149 - High Speed Clock B for card normal

This indicates that the High Speed clock B signal for the indicated card has returned to a normal, functional state.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 35.0.0
0053.0149    CARD 1115 OAM      High Speed Clock B for card normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.119 0157 - OA&M IP Security feature risk detected

This UAM indicates the OA&M IP Security feature is currently ON, and there is 1 or more FTP Servers not using a secure FTP or Telnet terminals not using SSH.

The EAGLE OA&M IP Security feature entry is used to control only the alarming if the SSH for terminals or Security of FTP Server entries is OFF. SSH for terminals and Security of FTP Server entries are controlled via the SECU-DFLT:SSH parameter and SECUIRTY parameter against the FTP servers entries, respectively.

Example 
eagle11 17-12-07 09:22:34 EST  EAGLE 46.5.0.0.0-0.0.0
*   1988.0157  * SECURITY SYSTEM         OA&M IP Security feature risk detected

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. To clear this alarm, either turn ON the SSH for terminals and security for all FTP sever entries, or turn the EAGLE OA&M IP Security feature OFF.
  2. Run the rtrv-secu-dflt and chg-secu-dflt commands to view and modify the SSH parameter value.
  3. Run rtrv-ftp-serv and chg-ftp-serv commands to view and modify the SECURITY parameter values for the FTP servers entries.
  4. Run the rtrv-ctrl-feat and chg-ctrl-feat commands to view and modify the EAGLE OA&M IP Security feature status.

3.2.120 0158 - OA&M IP Security feature risk cleared

This UAM indicates the OA&M IP Security feature risk alarm has been cleared.

Example 
eagle11 17-12-07 09:22:48 EST  EAGLE 46.5.0.0.0-0.0.0
    1991.0158    SECURITY SYSTEM         OA&M IP Security feature risk cleared
;

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.121 0159 - High Speed Clocks A and B for card normal

The High Speed A and B clock sources for the indicated card are now functioning normally.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 35.0.0
0053.0159    CARD 1115 OAM   High Speed Clocks A and B for card normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.122 0160 - 1116-S Clock Failed

This message indicates the secondary BITS clock failed on the TDM card in slot 1116.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
* 0014.0160  * CLOCK SYSTEM    1116-S clock failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock status.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Active   )    CARD LOC= 1116 (Isolated )
    PRIMARY BITS   = Active       PRIMARY BITS   = -----
    SECONDARY BITS = Idle         SECONDARY BITS = -----
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed.
  2. The primary BITS clock should be active.
    Reseat the TDM card in slot 1116.
  3. If the problem persists, replace the TDM card.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.123 0161 - 1116-P Clock Failed

This message indicates that the primary clock on the TDM card in slot 1116 failed.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0161  * CLOCK SYSTEM    1116-P clock failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Standby  )    CARD LOC= 1116 (Active )
    PRIMARY BITS   = Idle       PRIMARY BITS   = Fault
    SECONDARY BITS = Active     SECONDARY BITS = Active
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         Idle      ------ 
    # Cards using CLK A = 0     # Cards with bad CLK A = 0
    # Cards using CLK B = 8     # Cards with bad CLK B = 0
    # Cards using CLK I = 0
    Command Completed.
  2. The system automatically reverts from the primary to secondary BITS if the primary clock fails.
    Reseat the TDM card in slot 1116.
  3. If the problem persists, replace the TDM card in slot 1116.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.124 0162 - 1116-P, 1116-S Clocks Failed

This message indicates that both BITS clocks have failed on the TDM card located in slot 1116.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
**  0014.0162  ** CLOCK SYSTEM    1116-P, 1116-S clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Standby  )    CARD LOC= 1116 (Active )
    PRIMARY BITS   = ------       PRIMARY BITS   = Fault
    SECONDARY BITS = ------       SECONDARY BITS = Fault
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         Idle      ------ 
    # Cards using CLK A = 0     # Cards with bad CLK A = 8
    # Cards using CLK B = 0     # Cards with bad CLK B = 8
    # Cards using CLK I = 8
    Command Completed
  2. Reseat the TDM card in slot 1116.
  3. If the problem persists, replace the TDM card in slot 1116.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.125 0163 - 1114-S Clock Failed

This message indicates the secondary BITS clock for the TDM card in slot 1114 has failed.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*   0014.0163  * CLOCK SYSTEM    1114-S clock failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Active   )    CARD LOC= 1116 (Isolated )
    PRIMARY BITS   = Active       PRIMARY BITS   = Fault
    SECONDARY BITS = Fault        SECONDARY BITS = Fault
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed.
  2. The primary BITS clock should be active.
    Reseat the TDM card in slot 1114.
  3. If the problem persists, replace the TDM card in slot 1114.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.126 0164 - 1114-S, 1116-S Clocks Failed

This message indicates the secondary BITS clock source has failed on both the active and standby TDM cards.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
**  0014.0164  ** CLOCK SYSTEM    1114-S, 1116-S clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock status.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Isolated )   CARD LOC= 1116 (Active )
    PRIMARY BITS   = Fault       PRIMARY BITS   = Active
    SECONDARY BITS = Fault       SECONDARY BITS = Fault
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed
  2. Follow local procedures to troubleshoot and repair the secondary BITS clock.
  3. If this message appears again, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.127 0165 - 1114-S, 1116-P Clocks Failed

This message indicates the secondary BITS clock on the TDM card in slot 1114, and the primary BITS clock on the TDM card in slot 1116 have failed.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0165  * CLOCK SYSTEM    1114-S, 1116-P clocks failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Isolated )    CARD LOC= 1116 (Active )
    PRIMARY BITS   = Fault        PRIMARY BITS   = Fault
    SECONDARY BITS = Fault        SECONDARY BITS = Active
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed
  2. Follow local procedures to troubleshoot and repair the BITS clock.
  3. If one of the reference clocks is still not functioning, replace the TDM card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.
  4. If this message appears again, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.128 0166 - 1114-S, 1116-P, 1116-S Clocks Failed

This message indicates the following clocks failed:

  • The secondary clock on the TDM card in slot 1114.

  • The primary clock on the TDM card in slot 1116.

  • The secondary clock on the TDM card in slot 1116.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0166  ** CLOCK SYSTEM    1114-S, 1116-P, 1116-S clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Active   )    CARD LOC= 1116 (Isolated )
    PRIMARY BITS   = Active       PRIMARY BITS   = Fault
    SECONDARY BITS = Fault        SECONDARY BITS = Fault
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the BITS clock.
  3. If one of the reference clocks is still not functioning, replace the TDM card(s).
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.129 0167 - 1114-P Clock Failed

This message indicates the primary BITS clock on the TDM card in slot 1114 has failed.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0167  * CLOCK SYSTEM    1114-P clock failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Isolated  )   CARD LOC= 1116 (Active )
    PRIMARY BITS   = Fault        PRIMARY BITS   = Active
    SECONDARY BITS = Fault        SECONDARY BITS = Fault
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed
  2. Follow local procedures to troubleshoot and repair the BITS clock.
  3. If the reference clock is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.130 0168 - 1114-P, 1116-S Clocks Failed

This message indicates the primary BITS clock on the TDM card in slot 1114, and the secondary BITS clock on the TDM card in slot 1116 have failed.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0168  * CLOCK SYSTEM    1114-P, 1116-S clocks failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
CARD LOC= 1114 (Isolated)    CARD LOC= 1116 (Active )
PRIMARY BITS   = Fault       PRIMARY BITS   = Active
SECONDARY BITS = Fault        SECONDARY BITS = Fault
                              PST           SST       AST
SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
# Cards using CLK A = 9     # Cards with bad CLK A = 0
# Cards using CLK B = 0     # Cards with bad CLK B = 9
# Cards using CLK I = 0
Command Completed
  2. Follow local procedures to troubleshoot and repair the BITS clock.
  3. If one of the reference clocks is still not functioning, reseat the associated TDM card.
    Make sure the system clock reference is active on the other TDM card.
  4. If one of the reference clocks is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.131 0169 - 1114-P, 1116-P Clocks Failed

This message indicates the primary BITS clock on the TDM cards in slots 1114 and slot 1116 have failed.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
**  0014.0169  ** CLOCK SYSTEM    1114-P, 1116-P clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Isolated )    CARD LOC= 1116 (Active )
    PRIMARY BITS   = Fault        PRIMARY BITS   = Fault
    SECONDARY BITS = Fault        SECONDARY BITS = Active
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed
  2. Follow local procedures to troubleshoot and repair the BITS clock.
  3. If one of the reference clocks is still not functioning, reseat the associated TDM card.
    Make sure the system clock reference is active on the other TDM card.
  4. If one of the reference clocks is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.132 0170 - 1114-P, 1116-P, 1116-S Clocks Failed

This message indicates the following clocks failed:

  • The primary clock on the TDM card in slot 1114.

  • The primary clock on the TDM card in slot 1116.

  • The secondary clock on the TDM card in slot 1116.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
**  0014.0170  ** CLOCK SYSTEM    1114-P, 1116-P, 1116-S clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Standby )     CARD LOC= 1116 (Isolated )
    PRIMARY BITS   = ------       PRIMARY BITS   = Fault
    SECONDARY BITS = ------       SECONDARY BITS = Active
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed
  2. Follow local procedures to troubleshoot and repair the BITS clock.
  3. If one of the reference clocks is still not functioning, reseat the associated TDM card.
    Make sure the system clock reference is active on the other TDM card.
  4. If one of the reference clocks is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.133 0171 - 1114-P, 1114-S Clocks Failed

This message indicates the primary and secondary BITS clocks on the TDM card in slot 1114 have failed.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0171  ** CLOCK SYSTEM    1114-P, 1114-S clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Isolated )    CARD LOC= 1116 (Active )
    PRIMARY BITS   = Fault        PRIMARY BITS   = Fault
    SECONDARY BITS = Fault        SECONDARY BITS = Active
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the BITS clock.
  3. If one of the reference clocks is still not functioning, reseat the associated TDM card.
    Make sure the system clock reference is active on the other TDM card.
  4. If one of the reference clocks is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.134 0172 - 1114-P, 1114-S, 1116-S Clocks Failed

This message indicates the following clocks failed:

  • The primary clock on the TDM card in slot 1114.

  • The secondary clock on the TDM card in slot 1114.

  • The secondary clock on the TDM card in slot 1116.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0172  ** CLOCK SYSTEM    1114-P, 1114-S, 1116-S clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
    CARD LOC= 1114 (Isolated )    CARD LOC= 1116 (Isolated )
    PRIMARY BITS   = Fault       PRIMARY BITS   = Fault
    SECONDARY BITS = Fault        SECONDARY BITS = Active
                                  PST           SST       AST
    SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    # Cards using CLK A = 9     # Cards with bad CLK A = 0
    # Cards using CLK B = 0     # Cards with bad CLK B = 9
    # Cards using CLK I = 0
    Command Completed
  2. Follow local procedures to troubleshoot and repair the secondary BITS clock.
  3. If one of the reference clocks is still not functioning, reseat that TDM card.
  4. If one of the reference clocks is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.135 0173 - 1114-P, 1114-S, 1116-P clocks failed

This message indicates the following clocks failed:

  • The primary clock on the TDM card in slot 1114.

  • The secondary clock on the TDM card in slot 1114.

  • The primary clock on the TDM card in slot 1116.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0173  ** CLOCK SYSTEM    1114-P, 1114-S, 1116-P clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    tekelecstp 00-04-23  13:34:15 EST  EAGLE 35.0.0
CARD LOC= 1114 (Isolated )    CARD LOC= 1116 (Active )
PRIMARY BITS   = Fault        PRIMARY BITS   = Fault
SECONDARY BITS = Fault        SECONDARY BITS = Active
                              PST           SST       AST
SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
# Cards using CLK A = 9     # Cards with bad CLK A = 0
# Cards using CLK B = 0     # Cards with bad CLK B = 9
# Cards using CLK I = 0
Command Completed
  2. Follow local procedures to troubleshoot and repair the primary BITS clock.
  3. If one of the reference clocks is still not functioning, reseat the associated TDM card.
  4. If one of the reference clocks is still not functioning, replace the associated TDM card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement procedures.

3.2.136 0174 - %-Full Threshold Reached-Upload Required

This alarm is part of the Security Logging feature. When the security log reaches a threshold (administered by the chg-attr-seculog command), this alarm is raised. If the system detects that the percent full condition of new entries has reached the threshold, this alarm is raised to alert the system administrator that the security log must be uploaded to avoid an overflow condition. If the log is not uploaded before the log is completely full, entries will be lost. When the security log is uploaded, the alarm is lowered.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 46.3.0.0 
*  0047.0174    *SECULOG 1114  %-Full level reached-upload required

Alarm Level: Minor

Recovery

Note:

This alarm appears only on the security administrator terminal.
  1. To clear this alarm, you must copy the security log to the file transfer area (FTA) in the system.
    To do this, enter the copy-seculog command.
  2. From the file transfer area, you can use the act-file-trns command to transfer the file to a remote PC.
    Follow local procedures for transferring and storing security logs.

3.2.137 0175 - LOGBUFROVFL-SECULOG - Upload Required

This alarm is part of the Security Logging feature. When the security log reaches a threshold (administered by the chg-attr-seculog command) UAM 174 is raised. When the log fills completely, new entries are lost and this alarm is raised. When the security log is uploaded, this alarm is lowered.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
* 0014.0175    *SECULOG 1114  LOGBUFROVFL-SECULOG - upload required

Alarm Level: Minor

Recovery

Note:

This alarm appears only on the security administrator terminal.
  1. To clear this alarm, you must copy the security log to the file transfer area (FTA) in the system.
    To do this, enter the copy-seculog command.
  2. From the file transfer area, you can use the act-file-trns command to transfer the file to a remote PC.
    Follow local procedures for transferring and storing security logs.

3.2.138 0176 - Stdby Security Log - Upload Required

This alarm is part of the Security Logging feature. All of the security log entries should be written to the active MASP and none to the standby MASP. However, should a problem occur and the standby MASP switches to active, the security logs are split between the two MASPs. If there are any new log entries on the standby MASP, the standby log should be uploaded.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
* 0014.0176    *SECULOG 1116  Stdby security log - upload required

Alarm Level: Minor

Recovery

Note:

This alarm appears only on the security administrator terminal.

Enter this command to clear the alarm and copy the security log to the file transfer area (FTA) in the system: copy-seculog:slog=stb

3.2.139 0177 - Security Log Exception Cleared

This alarm is part of the Security Logging feature and indicates that a previous alarm has been cleared by doing one of the following:

  • Upload the security log to the file transfer area.

  • Turn off the security logging feature.

  • Raise the threshold for the number of log entries that will generate UAM 174.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0177     SECULOG 1114            Security log exception cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

Note:

This alarm appears only on the security administrator terminal.

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.140 0178 - Security log failed

This alarm is part of the Security Logging feature and indicates that a command could not be recorded in the security log.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0178      SECULOG 1114       Security log failed

Alarm Level: No alarm condition. The message is informational only.

Recovery

Note:

This alarm appears only on the security administrator terminal.

This message indicates a logging failure has occurred.

If the problem persists, check for other alarms, such as a disk failure, and troubleshoot that alarm.

3.2.141 0183 - 1116-SHS Clock Failed

This message indicates that the secondary E1/T1 High Speed clock has failed for the TDM card located in slot 1116.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
*  0052.0183  * HS CLOCK SYSTEM  1116-SHS clock failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE      = E1 UNFRAMED    HS CLK TYPE      = -----
    HS CLK LINELEN   = SHORTHAUL      HS CLK LINELEN   = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Reseat the TDM card in slot 1116.
  3. If the problem persists, replace the TDM card in slot 1116.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.142 0184 - 1116-PHS Clock Failed

This message indicates that the primary E1/T1 High Speed clock has failed for the TDM card located in slot 1116.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
*  0052.0184  * HS CLOCK SYSTEM  1116-PHS clock failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE      = E1 UNFRAMED    HS CLK TYPE      = -----
    HS CLK LINELEN   = SHORTHAUL      HS CLK LINELEN   = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Reseat the TDM card in slot 1116.
  3. If the problem persists, replace the TDM card in slot 1116.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.143 0185 - 1116-PHS, 1116-SHS Clocks Failed

This message indicates that both E1/T1 High Speed clocks have failed for the TDM card located in slot 1116.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0185  ** HS CLOCK SYSTEM 1116-PHS, 1116-SHS clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE      = E1 UNFRAMED    HS CLK TYPE      = -----
    HS CLK LINELEN   = SHORTHAUL      HS CLK LINELEN   = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Reseat the TDM card in slot 1116.
  3. If the problem persists, replace the TDM card in slot 1116.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.144 0186 - 1114-SHS Clock Failed

This message indicates that the secondary E1/T1 High Speed clock has failed for the TDM card located in slot 1114.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
*  0052.0186  * HS CLOCK SYSTEM  1114-SHS clock failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Reseat the TDM card in slot 1114.
  3. If the problem persists, replace the TDM card in slot 1114.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.145 0187 - 1114-SHS, 1116-SHS Clocks Failed

This message indicates the secondary E1/T1 High Speed clock source has failed for both the active and standby TDM cards.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0187  ** HS CLOCK SYSTEM 1114-SHS, 1116-SHS clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock status.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the secondary E1/T1 High Speed clock.
  3. If this message appears again, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.146 0188 - 1114-SHS, 1116-PHS Clocks Failed

This message indicates the following High Speed clocks failed:

  • The secondary High Speed clock for the TDM card in slot 1114.

  • The primary High Speed clock for the TDM card in slot 1116.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
*  0052.0188  * HS CLOCK SYSTEM  1114-SHS, 1116-PHS clocks failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock status.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the E1/T1 High Speed clocks.
  3. If this message appears again, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.147 0189 - 1114-SHS, 1116-PHS, 1116-SHS Clocks Failed

This message indicates the following High Speed clocks failed:

  • The secondary High Speed clock for the TDM card in slot 1114

  • The primary High Speed clock for the TDM card in slot 1116

  • The secondary High Speed clock for the TDM card in slot 1116

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0189 ** HS CLOCK SYSTEM  1114-SHS, 1116-PHS,1116-SHS clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the E1/T1 High Speed clocks.
  3. If one of the reference clocks is still not functioning, replace the TDM card(s).
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.148 0190 - 1114-PHS Clock Failed

This message indicates the primary High Speed clock for the TDM card in slot 1114 has failed.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
*  0052.0190  ** HS CLOCK SYSTEM 1114-PHS  clock failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the E1/T1 High Speed clock.
  3. If the clock is still not functioning properly, replace the TDM card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.149 0191 - 1114-PHS, 1116-SHS Clocks Failed

This message indicates the following High Speed clocks failed:

  • The primary High Speed clock for the TDM card in slot 1114

  • The secondary High Speed clock for the TDM card in slot 1116

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
*  0052.0191  * HS CLOCK SYSTEM  1114-PHS, 1116-SHS clocks failed

Alarm Level: Minor

Recovery

  1. Use the rept-stat-clk command to determine the current clock status.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the E1/T1 High Speed clocks.
  3. If this message appears again, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.150 0192 - 1114-PHS, 1116-PHS Clocks Failed

This message indicates the primary E1/T1 High Speed clocks for the TDM cards in slots 1114 and 1116 have failed.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0192  ** HS CLOCK SYSTEM 1114-PHS, 1116-PHS clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the E1/T1 High Speed clocks.
  3. If one of the reference clocks is still not functioning, reseat the associated TDM card.
    Make sure the system clock reference is active on the other TDM card.
  4. If one of the reference clocks is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.151 0193 - 1114-PHS, 1116-PHS, 1116-SHS clks Failed

This message indicates the following clocks failed:

  • The primary High Speed clock for the TDM card in slot 1114

  • The primary High Speed clock for the TDM card in slot 1116

  • The secondary High Speed clock for the TDM card in slot 1116

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0193 ** HS CLOCK SYSTEM  1114-PHS, 1116-PHS,1116-SHS clks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the E1/T1 High Speed clocks.
  3. If one of the reference clocks is still not functioning, reseat the associated TDM card.
    Make sure the system clock reference is active on the other TDM card.
  4. If one of the reference clocks is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.152 0194 - 1114-PHS, 1114-SHS Clocks Failed

This message indicates the primary and secondary E1/T1 High Speed clocks for the TDM card in slot 1114 have failed.

Example 
   station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0194  ** HS CLOCK SYSTEM 1114-PHS, 1114-SHS clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the E1/T1 High Speed clocks.
  3. If one of the reference clocks is still not functioning, reseat the associated TDM card.
    Make sure the system clock reference is active on the other TDM card.
  4. If one of the reference clocks is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.153 0195 - 1114-PHS, 1114-SHS, 1116-SHS clks Failed

This message indicates the following clocks failed:

  • The primary High Speed clock for the TDM card in slot 1114

  • The secondary High Speed clock for the TDM card in slot 1114

  • The secondary High Speed clock for the TDM card in slot 1116

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0194  ** HS CLOCK SYSTEM 1114-PHS, 1114-SHS clocks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the secondary E1/T1 High Speed clock.
  3. If one of the reference clocks is still not functioning, reseat that TDM card.
  4. If one of the reference clocks is still not functioning, replace the TDM card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.154 0196 - 1114-PHS, 1114-SHS, 1116-PHS clks Failed

This message indicates the following clocks failed:

  • The primary High Speed clock for the TDM card in slot 1114

  • The secondary High Speed clock for the TDM card in slot 1114

  • The primary High Speed clock for the TDM card in slot 1116

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0196  ** HS CLOCK SYSTEM 1114-PHS, 1114-SHS,1116-PHS clks failed

Alarm Level: Major

Recovery

  1. Use the rept-stat-clk command to determine the current clock configuration.
    Example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Follow local procedures to troubleshoot and repair the primary E1/T1 High Speed clock.
  3. If one of the reference clocks is still not functioning, reseat the associated TDM card.
  4. If one of the reference clocks is still not functioning, replace the associated TDM card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.155 0197 - All High Speed Clocks Have Failed

A fault has been detected on all high speed system clocks.

Example 
RLGHNCXA21W 00-12-07 11:02:30 EST  EAGLE 31.6.0
*C 0100.0197 *C HS CLOCK SYSTEM  All high speed clocks have failed

Alarm Level: Critical

Recovery

  1. Verify the status of the clock with the rept-stat-clk command.
    If both clocks are idle, check the source clock into the system. Follow local maintenance procedures to repair the source clock.
  2. Verify the clock cables are connected to the shelf backplane (refer to the Installation Manual for cable location).
    If any cables are loose, reconnect the cable.
  3. If the clock source is not at fault, try reseating the TDM cards.
  4. If the message appears again, replace the TDM cards.
    Refer to the Maintenance Manual for card removal/replacement procedures.
  5. If the fault still does not clear, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.156 0198 - High speed clock alarm(s) cleared

All primary and secondary high speed clock sources are functioning.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0198    HS CLOCK SYSTEM  High speed clock alarm(s) cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.157 0199 - OA&M IP Security feature disabled

The Eagle OA&M IP Security Enhancements Feature is not operational. This UAM is issued because the temporary key for the QA&M IP Security feature has expired.

With this feature disabled, you do not have the tools to securely pass data across an otherwise non-secure network. Until the Eagle OA&M IP Security Enhancements Feature is restored, the Eagle cannot provide secure connections from approved clients, and does not protect sensitive passwords and information while in transit between the Eagle and a host.

Example 
RLGHNCXA21W 03-03-03 12:01:43 EST  EAGLE 35.0.0 
0047.0199    SECURITY SYSTEM         OA&M IP Security feature disabled

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. First, to restore OA&M IP Security Enhancements feature, you must enable it permanently.
    To enable a control feature, you can purchase it from Oracle. You will receive a feature access key to use with the enable-ctrl-feat command.
  2. Next, turn on the feature by using the chg-ctrl-feat command.

3.2.158 0200 - RCVRY-LKF: Link Available

The link has become available for SS7 signaling traffic. SS7 traffic has been restored to the link.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0200  SLK 1202,A nc00027  RCVRY-LKF: link available
             SLC=01    FECLLI=A1234567890        CLASS=MTP2

Note:

The Class parameter in the example is optional. SS7IPGW and IPLIM links are considered high-speed links by the EAGLE 5 ISS. They are reported as CLASS=SAAL.

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.159 0201 - REPT-LKF: Remote NE Loopback

This message indicates the link is in loopback. This alarm is repeated every 15 minutes until the loopback is deactivated.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0201  ** SLK 1205,A nc00027  REPT-LKF:remote NE loopback
                SLC=01    FECLLI=A1234567890            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the loopback was established in error, enter the following command, specifying the location and port from the output message:

dact-lbp:loc=xxxx:port=y

where xxxx = the card location from the outputy = the port A or B from the output.

3.2.160 0202 - REPT-LKF: HWP - too many link interrupts

This message indicates the link has had numerous interruptions.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.202 ** SLK 1205,A nc00027 REPT-LKF:HWP - too many link interrupts
                SLC=01   FECLLI=A1234567890            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. The number of interruptions has exceeded the threshold.
    This situation can be caused by excessive noise from unshielded cables, loose or disconnected cables.
  2. Check the physical connections to the specified card.
  3. Follow local procedures to test the link facilities.

3.2.161 0203 - REPT-LKF: lost data

The signaling link has lost data.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0203  ** SLK 1205,A nc00027  REPT-LKF:lost data
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Check the physical connections to the signaling link.
  2. Review current NODATA timer configuration (rtrv-slk, rtrv-l2t) for signaling link.
  3. Using an analyzer, test for level 1 and level 2 functions.
    Follow local procedures to test and return links to service.

3.2.162 0204 - REPT-LKF: XER - ERM threshold exceeded

The signal unit error rate monitor (ERM) has exceeded the threshold because there are too many errors on the link.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0204 ** SLK 1205,A nc00027  REPT-LKF:XER-ERM threshold exceeded
                SLC=01    FECLLI=A1234567890            CLASS=SAAL

Alarm Level: Major

Recovery

Follow local procedures to test the link facilities.

3.2.163 0205 - REPT-LKF: APF - lvl-2 T1 expd (ready)

The signaling link did not receive a fill-in or message signal unit after the proving period.

Example 
    RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0313.0205  ** SLK 1205,A nc00027  REPT-LKF:APF-lvl-2 T1 expd (ready)
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.164 0206 - REPT-LKF: APF - lvl-2 T1 expd (not ready)

The signaling link did not receive a fill-in or message signal unit after the proving period.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0313.0206 ** SLK 1205,A nc00027 REPT-LKF:APF - lvl-2 T1 expd (not ready)
                SLC=01   FECLLI=A1234567890            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.165 0207 - REPT-LKF: APF - lvl-2 T3 expired

The link did not receive an SIN or an SIE before the T3 timer expired.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0207  ** SLK 1205,A nc00027  REPT-LKF:APF - lvl-2 T3 expired
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.166 0208 - REPT-LKF: APF - lvl-2 T2 expired

The link did not receive an SIN, SIE, or SIOS.

Example 
    RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0208  ** SLK 1205,A nc00027  REPT-LKF:APF - lvl-2 T2 expired
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.167 0209 - REPT-LKF: APF - failed proving period

The signaling link has failed the proving period.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0209 ** SLK 1205,A nc00027 REPT-LKF: APF - failed proving period
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.168 0210 - REPT-LKF: OSA - received SIO

The signaling terminal has received the status indication Out of Alignment from the far end.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0210  ** SLK 1205,A nc00027  REPT-LKF: OSA - received SIO
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.169 0211 - REPT-LKF: OSA - received SIN

The signaling terminal has received the status indication normal proving from the far end.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0211 **  SLK 1205,A nc00027  REPT-LKF: OSA - received SIN
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.170 0212 - REPT-LKF: OSA - received SIE

The signaling terminal has received the status indication emergency alignment, from the far end.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0212  **  SLK 1205,A nc00027  REPT-LKF: OSA - received SIE
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.171 0213 - REPT-LKF: OSA - received SIOS

The signaling link has received the status indication out of service from the far end.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0213 **  SLK 1205,A nc00027  REPT-LKF: OSA - received SIOS
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.172 0214 - REPT-LKF: ABN - rcvd 2 of 3 invalid BSN

The link has received 2 out of 3 invalid backward sequence numbers (BSNs) from the far end.

Example 
    RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0214 ** SLK 1205,A nc00027  REPT-LKF: ABN - rcvd 2 of 3 invalid BSN
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.173 0215 - REPT-LKF: ABN - rcvd 2 of 3 invalid FIB

The signaling link has received 2 out of 3 invalid forward indicator bits (FIB) from the far end.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0215 **  SLK 1205,A nc00027  REPT-LKF: ABN-rcvd 2 of 3 invalid FIB
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.174 0216 - REPT-LKF: remote congestion timeout

The remote node has been in congestion too long. The T6 timer has timed out.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0216 ** SLK 1205,A nc00027  REPT-LKF:remote congestion timeout
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far end is not responding correctly.

  1. Enter rept-stat-card:mode=full:loc=xxxx to determine if the signaling link is M2PA. If so, continue to 2. If not, skip to 3.
  2. If this alarm is raised for IPSG M2PA signaling links, do the following:
    1. Enter the rept-stat-iptps and msucount –l commands to determine how much traffic is received and transmitted on the M2PA links.
    2. Enter the rtrv-ls command to determine the amount of rsvdslktps and maxslktps traffic that the M2PA signaling link can receive based on what is provisioned. (The rsvdslktps is the reserved-per-signaling-link TPS for IPSG linkset; this indicates the minimum guaranteed capacity for each link in the linkset. The maxslktps is the maximum-per-signaling-link TPS; this indicates the maximum traffic permitted when sufficient unused capacity is present on the host card.)
    3. Determine if the value exceeds the incoming traffic rate that the near end can accept. If the value is incorrect, enter the chg-ls command to increase or decrease the minimum and maximum TPS for the M2PA signaling link.

    Note:

    This step applies to only IPSG M2PA links and not to IPLIM M2PA links.
  3. If the problem persists, follow local procedures to determine why the far end is not responding correctly.

3.2.175 0217 - REPT-LKF: XDA - excess acknowledge delay

The T7 timer has timed out. Either there is too much incoming traffic on M2PA signaling links, or the far end node is taking too long to acknowledge the messages sent to it by the signaling terminal.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0217 ** SLK 1205,A nc00027  REPT-LKF: XDA-excess acknowledge delay
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Enter rept-stat-card:mode=full:loc=xxxx to determine if the signaling link is M2PA. If so, continue to 2. If not, skip to 3.
  2. If this alarm is raised for M2PA signaling links, do the following:
    1. Enter the rept-stat-iptps and msucount –l commands to determine how much traffic is received and transmitted on the M2PA links.
    2. Enter the rtrv-ls command to determine the amount of rsvdslktps and maxslktps traffic that the M2PA signaling link can receive based on what is provisioned. (The rsvdslktps is the reserved-per-signaling-link TPS for IPSG linkset; this indicates the minimum guaranteed capacity for each link in the linkset. The maxslktps is the maximum-per-signaling-link TPS; this indicates the maximum traffic permitted when sufficient unused capacity is present on the host card.)
    3. If the value is incorrect to handle the incoming traffic rate, enter the chg-ls command to increase or decrease the minimum and maximum TPS for the M2PA signaling link.
  3. If the problem persists, follow local procedures to determine why the far end is not responding correctly.

3.2.176 0218 - REPT-LKF: COO - rcvd changeover order

The signaling link has received a changeover order from the far end.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0218 **  SLK 1205,A nc00027  REPT-LKF:COO-rcvd changeover order
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If the problem persists, follow local procedures to determine why the far-end is not responding correctly.

3.2.177 0219 - REPT-LKF: False Congestion Restart

This message indicates the signaling link has entered a congestion state even though the traffic on the linkset is not high enough to cause congestion. For example, if the link has a high number of re-transmissions, the throughput on the link could drop enough to cause congestion on the link. A T31 timer has started. If the link stays in congestion for a specified period, the link is restarted.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0219 **  SLK 1205,A nc00027  REPT-LKF:false congestion restart
                 SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Activate measurements using the chg-meas:collect=on command.
    This starts measurements collection.
  2. If the link is placed OOS-MT, use the measurements collected over the appropriate time period to determine the cause, and determine which action is now necessary.

    Note:

    Refer to the Measurements Manual for traffic measurements information.

3.2.178 0220 - REPT-LKF: MTP Link Restart Delayed

This message indicates that a link has gone in and out-of-service. To avoid links going in and out-of-service repeatedly, the EAGLE system uses level 3 T32 timer procedure, which delays restarting a link if the link has an unstable history.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0220 **  SLK 1205,A nc00027  REPT-LKF:MTP link restart delayed
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional. SS7IPGW and IPLIM links are considered high-speed links by the EAGLE 5 ISS system. They are reported as CLASS=SAAL.

Alarm Level: Major

Recovery

The link should become available.

If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.179 0222 - REPT-LKF: remote FE loopback

This message indicates that the specified link has been looped back from the far-end.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0222 **  SLK 1205,A nc00027  REPT-LKF:remote FE loopback
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

If you wish to stop the loopback testing, notify the far-end to stop the testing.

3.2.180 0223 - REPT-LKF: remote NE loopback cleared

This message indicates the link was in loopback and now the loopback has been deactivated.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0223   SLK 1205,A nc00027  REPT-LKF:remote NE loopback cleared
             SLC=01    FECLLI=A1234567890            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.181 0224 - REPT-LKF: link test failed

This message indicates that the specified link was automatically removed from service (OOS) because of a failed signaling link test.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0224 **  SLK 1205,A nc00027  REPT-LKF:link test failed
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Check the physical connections to the signaling link.
  2. Follow local procedures to check link data at both ends.
  3. Using an analyzer, test for level 1 and level 2 functions.
    Follow local procedures to test and return links to service.

3.2.182 0225 - CARD running outdated Flash GPL

This message indicates an OAM/MCP/IPS card is running a GPL with VxWorks6.4 version or Service Module card is running 32-bit SM GPLs (SCCPHC, DEIRHC, SIPHC, ENUMHC). EAGLE release 46.6 is going to be the last release in which 32-bit SM GPLs (SCCPHC, DEIRHC, SIPHC, ENUMHC) is available. EAGLE running/getting upgraded to release 46.6 generates UAM 0225, "CARD running outdated Flash GPL", if there are SM cards running 32-bit GPLs. All SM cards should be converted to run 64-bit GPLs to clear the alarm. SM cards can be converted to 64-bit during the upgrade maintenance window or during next available maintenance window.

Example 
          1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  5019.0225 ** CARD 1101 MCPHC         CARD running outdated Flash GPL
                 HW VERIFICATION CODE:   182

Alarm Level: Major

Recovery

  1. Upgrade the OAM/MCP/IPS card to VXworks6.9.
  2. Upgrade the SM card to 64 bit GPL.

3.2.183 0230 - REPT-LKF: Local Blocked - Thermal

All links to the HC MIM are blocked because the temperature of the HC MIM is above operational limits.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
**  0014.0230 **  SLK 1205,A nc00027  REPT-LKF: local blocked - thermal
                  SLC=03   FECLLI=testclli            CLASS=MTP2

Alarm Level: Major

Recovery

Review the output.

Correct the associated alarms to clear this alarm.

3.2.184 0232 - REPT-LKF: remote blocked

The link is blocked due to an event at the far-end.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0232 **  SLK 1205,A nc00027  REPT-LKF: remote blocked
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

Contact the far-end office to verify a processor outage and correct.

3.2.185 0233 - REPT-LINK-MANUAV: local blocked

A local technician has put the signaling link in processor outage.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0233 **  SLK 1205,A nc00027  REPT-LINK-MANUAV: local blocked
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Verify the condition is not intentional.
    If it is not intentionally blocked, enter the following command to place the link in service: ublk-slk:loc=xxxx:port=y where xxxx is the card location y is the port
  2. This should place the processor back into service.
    The following message should appear. 
    
RLGHNCXA03W  00-02-07  11:11:28 EST  EAGLE 35.0.0
Local processor outage being cleared.

3.2.186 0234 - REPT-LKF: RMI remote inhibited

The link has been remotely inhibited by a technician at the far-end office.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0234 **  SLK 1205,A nc00027  REPT-LKF: RMI remote inhibited
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

Contact the far-end office to verify the reason for inhibiting the link.

3.2.187 0235 - REPT-LINK-MGTINH: local inhibited

The link has been inhibited locally by a technician.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0235 **  SLK 1205,A nc00027  REPT-LINK-MGTINH: local inhibited
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Ensure the link should not be inhibited.
    Enter the following command to place the link in service:
    unhb-slk:loc=xxxx:port=y
    where xxxx is the card location y is the port
  2. The link should begin transmitting and receiving MSUs.
    The following message should appear. 
    
RLGHNCXA03W  00-02-07  11:11:28 EST  EAGLE 35.0.0
Allow link message sent to card.

3.2.188 0236 - REPT-LKF: Not Aligned

The signaling link has lost alignment. It can no longer carry traffic.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0236 **  SLK 1205,A nc00027  REPT-LKF: not aligned
                 SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Put the link into a local loopback state.
  2. If the link does not align, enter the following command to determine the status of the card:
    rept-stat-card
  3. If the card has reinitialized, the system software will restore the card.
    If both links on the card are out of service, but the card is IS-NR (In-Service-Normal), reseat the card.
  4. If the links restore after reseating the card, this procedure is complete.
  5. If the links do not restore after reseating the card, enter the following command:
    rmv-card:loc=xxxx

    where xxxx = the card location.

  6. After the command is complete, enter the following command:
    rst-card:loc=xxxx

    where xxxx = the card location.

  7. If the links restore after restoring the card, this procedure is complete.
  8. If the fault does not clear, replace the indicated card.
    Refer to the Maintenance Manual for card removal/replacement procedures.
  9. If the link aligns when it is in a loopback state, enter the following command to determine the DPC of the far end office:
    rtrv-slk:loc=xxxx

    where xxxx = the card location. Contact the far end office to determine if the trouble is at that end.

  10. If the fault does not clear, determine if any other links on the same carrier are affected.
    If other links on the same carrier are affected, you may have trouble in your carrier.
  11. Using measurements, review the activity over the last day and determine if there were a number of retransmits, message losses and so forth.
    Use this data to isolate the problem to the appropriate level (MTP level 2, MTP level 3, and so forth). Use your company maintenance procedures for testing and clearing faults in carriers.

3.2.189 0237 - REPT-LKF: LM Timer NO-CREDIT expired

The remote node has held the local node in a no-credit state for too long.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0237 **  SLK 1205,A nc00027  REPT-LKF: LM Timer NO-CREDIT expired
                SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

Contact the far-end office to test and correct the link congestion problem.

3.2.190 0238 - REPT-LKF: XDA-Timer NO-RESPONSE expired

The far end is not responding to the outgoing POLL messages.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0238 **  SLK 1205,A nc00027  REPT-LKF: Timer NO-RESPONSE expired
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

Contact the far-end office to determine why no STAT messages are being sent.

3.2.191 0239 - REPT-LKF:MBL - Local Processor Outage

Indicates a spontaneous or management-initiated processor outage.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0239 **  SLK 1205,A nc00027  REPT-LKF:MBL - local processor outage
                 SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Enter the following command to determine whether the outage was spontaneous or management-initiated:
    rept-stat-slk:l2stats=both
  2. Analyze the output.
    If the processor outage was spontaneous, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.192 0240 - REPT-LKF: rcvd remote processor outage

The far end sent an END processor outage protocol data unit (PDU).

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0240 **  SLK 1205,A nc00027  REPT-LKF: rcvd remote processor outage
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

Contact the far-end office to verify a processor outage and the cause.

3.2.193 0241 - REPT-LKF: rcvd remote out of service

The far end sent an END out of service protocol data unit (PDU).

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0241 **  SLK 1205,A nc00027  REPT-LKF: rcvd remote out of service
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

Contact the far-end office to correct the problem.

3.2.194 0242 - REPT-LKF:rcvd remote protocol error

A protocol error has occurred on the far end.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0242 **  SLK 1205,A nc00027  REPT-LKF:rcvd remote protocol error
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

Contact the far-end office to test and correct the problem.

3.2.195 0243 - REPT-LKF:rcvd Remote mgmt Inititated

The MAAL layer (not a user) on the far end released a link.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0243 **  SLK 1205,A nc00027  REPT-LKF:rcvd remote mgmt inititated
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

Contact the far-end office for the details about releasing the link.

3.2.196 0244 - REPT-LKF: FAC – DS1/E1 LOS failure

A level 1 facility outage: loss of signal.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0244 **  SLK 1205,A nc00027  REPT-LKF: FAC – DS1/E1 LOS failure
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Enter the following command to display the service data:
    rept-stat-slk:l2stats=both
  2. Check the physical connections to the signaling link.
  3. Using an analyzer, test for level 1 and level 2 functions.
    Follow local procedures to test and return links to service.

3.2.197 0245 - REPT-LKF: FAC – DS1/E1 LOF failure

A level 1 facility outage: loss of frame.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0245 **  SLK 1205,A nc00027  REPT-LKF: FAC – DS1/E1 LOF failure
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Enter the following command to display the service data:
    rept-stat-slk:l2stats=both
  2. Check the physical connections to the signaling link.
  3. Using an analyzer, test for level 1 and level 2 functions.
    Follow local procedures to test and return links to service.

3.2.198 0246 - REPT-LKF: FAC – DS1/E1 LCD failure

A level 1 facility outage: loss of cell delineation.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0246 **  SLK 1205,A nc00027  REPT-LKF: FAC – DS1/E1 LCD failure
                SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

  1. Enter the following command to display the service data:
    rept-stat-slk:l2stats=both
  2. Check the physical connections to the signaling link.
  3. Using an analyzer, test for level 1 and level 2 functions.
    Follow local procedures to test and return links to service.

3.2.199 0247 - REPT-LKF: XER - ISERM threshold exceeded

The in-service error rate monitor (ISERM) maintains a counter to estimate the PDU error rate. The ISERM counter exceeded the estimated threshold.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0247 **  SLK 1205,A nc00027 REPT-LKF:XER - ISERM threshold exceeded
                SLC=03   FECLLI=testclli            CLASS=MTP

Note:

The Class parameter in the example is optional.

Alarm Level: Major

Recovery

Contact the far-end office to determine why the error rate is so high.

3.2.200 0248 - DDL Unstable

This alarm indicates the DDL unstable has been detected.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  0002.0248 ** Card 1212            DDL Unstable

Alarm Level: Major

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.201 0249 - DDL Stable

This indicates the DDL is no longer unstable.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0249 *  Card 1212            DDL Stable

Alarm Level: None

No further action necessary.

3.2.202 0250 - MPS Available

This indicates that a previous MPS platform association loss has been reestablished and is currently functioning properly.

Example 
station1234 99-03-30 16:28:08 EST  EAGLE 35.0.0
3535.0250    MPS A         MPS available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.203 0261 - MPS Unavailable

This message indicates that the EAGLE 5 ISS system is unable to communicate with the MPS or the MPS has an internal failure.

Example 
station1234 99-03-30 16:28:08 EST  EAGLE 35.0.0
*C 3535.0261  *C  MPS A         MPS unavailable

Alarm Level: Critical

Recovery

  1. This message reports that communication with the MPS is not occurring.
    You should verify the MPS is operating and the IP link is functioning by performing the following steps.
  2. Verify the IP connection from the MPS to Eagle is operating.
    If not, restore the communication link between the them.
  3. Once the communications link with the MPS is assured, verify the status of the MPS.
    The following example shows a possible system response when a specified DSM card is queried with the rept-stat-mps command. rept-stat-mps:loc=1205 
    rlghncxa03w 01-03-07 10:23:93 EST  EAGLE 35.0.0
     CARD   VERSION       TYPE    PST            SST          AST
     1205   -----------   DSM     OOS-MT-DSBLD   Manual       -----
       DSM PORT A                 OOS-MT         Unavail      -----
                 ALARM STATUS       = **  0084 IP Connection Unavailable
       DSM PORT B                 OOS-MT         Unavail      -----
                 ALARM STATUS       = **  0084 IP Connection Unavailable
       INP STAT           = -------
       CARD ALARM STATUS  = No Alarms.
       DSM MEMORY USAGE   = 0%
     Command Completed.
    Determine from the output whether the MPS is active and available for service. If it is not, refer to the ELAP Administration and LNP Feature Actiivation or EPAP Administration Manual about restoring an MPS server to the active state.

3.2.204 0262 - GTT Duplicate Actn processing stopped

The Service Module card received too many MSUs requiring GTT Duplicate Actions at one time. As a result, the Service Module card was generating more duplicate MSUs than the card could handle. To prevent the number of duplicates from overwhelming the Service Module card, the card stopped processing GTT Duplicate Actions.

Example 
**  0002.0262 ** SCCP SYSTEM             GTT Duplicate Actn processing stopped
                    Service: GTT

Alarm Level: Major

Recovery

The Service Module card will begin processing GTT Duplicate Actions again with no further action. To prevent the problem from occurring again, do the following:

  1. Run the rept-stat-sccp command to see the location of the Service Module cards that are not processing GTT Duplicate Actions. Note that this command does not display the GTT Actions that resulted in the disabling of GTT Duplicate Actions.
  2. To reduce the chance of the overwhelming the Service Module card, do one of the following:
    • Provision fewer GTT Duplicate Actions so that the Service Module card does not generate excess duplicate messages.
    • Rearrange the location of LIM and Service Module cards so that the traffic is evenly distributed among the Service Module cards.

3.2.205 0263 - GTT Duplicate Actn processing resumed

The Service Module card stopped GTT Duplicate Action processing temporarily, because the number of duplicate MSUs was more than the card could handle. This UAM is issued when GTT Duplicate Action processing resumes.

Example 
    0002.0263    SCCP SYSTEM             GTT Duplicate Actn processing resumed
                    Service: GTT

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.206 0264 - REPT-LINK-CGST: Congestion Level 0 to 1

The amount of MSU traffic on the link has reached a congestion level 1.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0264   SLK 1205,A nc00027  REPT-LINK-CGST: congestion level 0 to 1
             SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Since congestion usually peaks and subsides quickly, a measurements report should be printed to understand what SS7 events took place.
    Use the command rept-meas to obtain a report.

    Note:

    The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.
  2. Ensure that there are enough links in the linkset based on the traffic load.

3.2.207 0265 - REPT-LINK-CGST: Congestion Level 1 to 2

The amount of MSU traffic on the link has reached a congestion level 2.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0265    SLK 1205,A nc00027  REPT-LINK-CGST: congestion level 1 to 2
             SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Since congestion usually peaks and subsides quickly, a measurements report should be printed to understand what SS7 events took place.
    Use the command rept-meas to obtain a report.

    Note:

    The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.
  2. Ensure there are enough links in the linkset based on the traffic load.

3.2.208 0266 - REPT-LINK-CGST: Congestion level 2 to 3

The congestion on a link has risen to level 3. That is, the amount of MSU traffic on the signaling link has reached the onset level defined for congestion level 3. This usually indicates the node is under provisioned.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0266   SLK 1205,A nc00027  REPT-LINK-CGST: congestion level 2 to 3
             SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Since congestion usually peaks and subsides quickly, a measurements report should be printed to understand what SS7 events took place.
    Use the command rept-meas to obtain a report.

    Note:

    The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.
  2. Ensure that there are enough links in the linkset based on the traffic load.

3.2.209 0267 - RCVRY-LINK-CGST:Congestion Level 3 to 2

The congestion on a link has fallen to level 2. That is, the amount of MSU traffic on the signaling link has reached the abatement level defined for congestion level 3. This indicates congestion is clearing.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0267   SLK 1205,A nc00027   RCVRY-LINK-CGST:congestion level 3 to 2
             SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

Since congestion usually peaks and subsides quickly, a measurements report should be printed to understand what SS7 events took place.

Use the command rept-meas to obtain a report.

Note:

The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.

3.2.210 0268 - RCVRY-LINK-CGST:Congestion Level 2 to 1

The congestion on a link has fallen to level 1. That is, the amount of MSU traffic on the signaling link has reached the abatement level defined for congestion level 2. This indicates congestion is clearing.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0268   SLK 1205,A nc00027   RCVRY-LINK-CGST:congestion level 2 to 1
             SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

Since congestion usually peaks and subsides quickly, a measurements report should be printed to understand what SS7 events took place.

Use the command rept-meas to obtain a report.

Note:

The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.

3.2.211 0269 - RCVRY-LINK-CGST: congestion has cleared

This message is generated when the congested state of a link has been removed.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0269   SLK 1205,A nc00027 RCVRY-LINK-CGST: congestion has cleared
             SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.212 0270 - REPT-LINK-CGST: Discard Level 0 to 1

The amount of MSU traffic on the link has reached an overflow level 1. Messages with an SIO priority of 0 are being discarded.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0270    SLK 1205,A nc00027  REPT-LINK-CGST: discard level 0 to 1
             SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Since overflow conditions usually peak and subside quickly, a measurements report should be printed to understand what SS7 events took place.
    Use the command rept-meas to obtain a report.

    Note:

    The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.
  2. Ensure that there are enough links in the linkset based on the traffic load.

3.2.213 0271 - REPT-LINK-CGST: Discard Level 1 to 2

The link has reached an overflow level 2. The percentage of MSU traffic on the signaling link has exceeded the discard/overflow level defined for level 2. Messages with SIO priority of 0 or 1 are being discarded.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0271    SLK 1205,A nc00027  REPT-LINK-CGST: discard level 1 to 2
             SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Since overflow conditions usually peak and subside quickly, a measurements report should be printed to understand what SS7 events took place.
    Use the command rept-meas to obtain a report.

    Note:

    The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.
  2. Ensure that there are enough links in the linkset based on the traffic load.

3.2.214 0272 - REPT-LINK-CGST: Discard Level 2 to 3

The amount of MSU traffic on the link has reached an overflow level 3. Messages with an SIO priority of 0, 1, or 2 are being discarded.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0272    SLK 1205,A nc00027  REPT-LINK-CGST: discard level 2 to 3
             SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Since overflow conditions usually peak and subside quickly, a measurements report should be printed to understand what SS7 events took place.
    Use the command rept-meas to obtain a report.

    Note:

    The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.
  2. Ensure that there are enough links in the linkset based on the traffic load.

3.2.215 0273 - RCVRY-LINK-CGST: Discard Level 3 to 2

The amount of MSU traffic on the link has reached an overflow level 2 and congestion is clearing. Messages with an SIO priority of 0 or 1 are being discarded.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0273    SLK 1205,A nc00027  RCVRY-LINK-CGST: discard level 3 to 2
             SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

Since overflow conditions usually peak and subside quickly, a measurements report should be printed to understand what SS7 events took place.

Use the command rept-meas to obtain a report.

Note:

The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.

3.2.216 0274 - RCVRY-LINK-CGST: Discard Level 2 to 1

The amount of MSU traffic on the link has decreased to an overflow level 1 and congestion is clearing. Messages with an SIO priority of 0 are being discarded.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0274   SLK 1205,A nc00027  RCVRY-LINK-CGST: discard level 2 to 1
             SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

Since overflow conditions usually peak and subside quickly, a measurements report should be printed to understand what SS7 events took place.

Use the command rept-meas to obtain a report.

Note:

The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.

3.2.217 0275 - RCVRY-LINK-CGST: discard has cleared

The overflow level of the link has reached level 0. No messages are being discarded.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0275    SLK 1205,A nc00027  RCVRY-LINK-CGST: discard has cleared
             SLC=03   FECLLI=testclli            CLASS=MTP2

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.218 0276 - Insufficient HW for IP7 Provisioning

The DCM or EDCM does not have enough memory to provision for sockets and associations.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0276 ** CARD  1115 DCM   Insufficient HW for IP7 provisioning
                HW VERIFICATION CODE: xxx

Alarm Level: Major

Recovery

  1. If this message contains the optional line ‘HW VERIFICATIONCODE: xxx’:
    1. Decode the xxx value and correct the indicated problem.
      See Hardware Verification Codes in UAMs the section on hardware verification codes in the Unsolicited Alarms and Information Messages manual.
    2. After correcting the problem, the card will be in out-of-service maintenance disabled state (OOS-MT-DSBLD).
      Restore the card back to in-service normal state (IS-NR) with the alw-card command.
    If this message does not contain the optional line ‘HW VERIFICATIONCODE: xxx’, continue with the next step.
  2. Verify the DCM/EDCM hardware.
    Verify the provisioning rules.

    Table 3-3 Maximum Sockets/Associations per Card

    Card Type Socket to Association Ratio Maximum Associations Maximum Sockets
    DCM 8:1 50 4
    EDCM 1:1 50 50
  3. If necessary, reduce the number of associations to four or less for DCMs or 50 or less for EDCMs.
    Refer to the Database Administration Manual - IP7 Secure Gateway for detailed provisioning information.

3.2.219 0277 - AS Unavailable

This Application Server (AS) is not available to carry service traffic. All ASPs in this AS are not available to carry service traffic.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0277  **  IP7    as3        AS Unavailable

Alarm Level: Major

Recovery

  1. If the connection is in service, enter this command to generate a report of the AS association status: rept-stat-as:asname="application_server_name"
  2. If the connection is not in service, there is nothing more you can do to fix the problem without further information from the far end, because the far end node is in control of this state.

3.2.220 0278 - AS Available

The Application Server (AS) is now available to carrying traffic.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0278    IP7    as2        AS Available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.221 0279 - AS Restricted

At least half of the paths are not working, so the traffic is considered restricted. The Application Server (AS) is carrying traffic, but one of the Application Server Processes (ASPs) is not functioning properly.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 28.1.0 
*  0014.0279  *  IP7    as2        AS Restricted

Alarm Level: Minor

Recovery

  1. Enter this command to generate a report of the AS association status:
    rept-stat-as:asname="application_server_name"
  2. If you have verified that the connection is established, there is nothing more you can do to fix the problem with further information from the far end. The far end node is in control of this state. Notify the PSTN associated with the restricted AS of the problem.

3.2.222 0280 - AS Unrestricted

The Application Server (AS) is carrying traffic. A previous restriction has been cleared.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
0014.0280    IP7    as2        AS Unrestricted

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.223 0283 - LNP Ported LRNs approaching Feat. Cap.

The number of LNP ported LRNs is greater than the capacity this feature supports.

This UAM appears when the DSMV SCCP cards are cold-restarted after the ELAP RTDBs were pre-populated offline with LRN totals that exceed the LRN Quantity Feature keys capacities that are currently configured for the EAGLE 5 ISS.

Example 
RLGHNCXA21W 03-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0283 ** CARD  1115 DCM  LNP Ported LRNs approaching Feat. Cap.

Alarm Level: Major

Recovery

  1. Enter the following command to verify the quantity of LRNs specified for this system:
    rtrv-ctrl-feat
  2. Either reduce the number of LRNs to the level specified by the output of 1, or respecify the capacity with the enable-ctrl-feat command.

3.2.224 0284 - LNP Ported LRNs Capacity Normal

This UAM is a clearing message that appears when the operator enables the LRN feature key quantities on the Eagle that exceed the quantities currently populated in the ELAP RTDBs.

Example 
RLGHNCXA21W 03-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0284    CARD  1115 DCM  LNP Ported LRNs Capacity Normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.225 0285 - LNP Ported NPAs Approaching Feat. Cap.

The number of LNP ported NPANXXs is greater than the capacity this feature supports.

This UAM appears when the DSMVSCCP cards are cold-restarted after the ELAPRTDBs were pre-populated offline with NPANXX totals that exceed the NPANXX Quantity Feature keys capacities that are currently configured for the EAGLE 5 ISS.

Example 
RLGHNCXA21W 03-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0285 ** CARD  1115 DCM  LNP Ported NPAs approaching Feat. Cap.

Alarm Level: Major

Recovery

  1. Enter the following command to verify the quantity of NPANXXs specified for this system:
    rtrv-ctrl-feat
  2. Either reduce the number of NPANXXs to the level specified by the output of 1, or respecify the capacity with the enable-ctrl-feat command.

3.2.226 0286 - LNP Ported NPAs Capacity Normal

This UAM is a clearing message that appears when the operator enables the NPANXX feature key quantities on the Eagle that exceed the quantities currently populated in the ELAP RTDBs.

Example 
RLGHNCXA21W 03-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0286    CARD  1115 DCM  LNP Ported NPAs Capacity Normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.227 0287 - RTDB Table Level 2 FAK Cap Exceeded

This UAM warns the customer that the total TNs in the LNP database has reached 95% of the LNP database Feature Access Key (FAK) capacity.

Example 
RLGHNCXA21W 03-02-07 11:02:30 EST EAGLE 35.0.0
*C 0100.0287 *C LNP 1115 DCM   RTDB Table Level 2 FAK Cap Exceeded
                TABLE: TN        Threshold Value:                95%
                                 Exceeds 88320000 of 96000000

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the database threshold:
    rtrv-th-alm

    If the threshold is below 95% go to 2 .

  2. Enter the following command:
    chg-th-alm:lnptndblv2=xxxx

    where xxxx=percentage.

  3. If the threshold is at 95% contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.228 0288 - RTDB Table Level 1 FAK Cap Exceeded

This UAM warns the customer that the total TNs in the LNP database has reached 80% of the LNP database Feature Access Key (FAK) capacity.

Example 
RLGHNCXA21W 03-02-07 11:02:30 ESTEAGLE 35.0.0
 ** 0100.0288 ** LNP 1115 DCM   RTDB Table Level 1 FAK Cap Exceeded
                 TABLE: TN        Threshold Value: 80%
                                  Exceeds 76800000 of 96000000

Alarm Level: Major

Recovery

  1. Enter the following command to verify the database threshold:
    rtrv-th-alm

    If the threshold is below 80% go to 2.

  2. Enter the following command:
    chg-th-alm:lnptndblv2=xxxx

    where xxxx=percentage.

  3. If the threshold is at 80% contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.229 0289 - RTDB Table FAK Capacity Normal

This UAM appears when the LNP FAK alarm condition no longer exists.

Example 
RLGHNCXA21W 03-02-07 11:02:30 EST  EAGLE 35.0.0
   0100.0289  LNP 1115 DCM   RTDB Table FAK Capacity Normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous condition has been corrected.

No further action is necessary.

3.2.230 0290 - GLS is Available

The TSM cards configured as generic loader services (GLS) are functioning. These cards are used to download gateway screening (GWS) data to the LIMs.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0290    GLS SYSTEM          GLS is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous condition has been corrected.

No further action is necessary.

3.2.231 0291 - GLS is at Minimum Service Limit

Only one TSM configured for generic loader services (GLS) is in service. When this module fails, GLS is unavailable.

Generic loader services (GLS) are used to download gateway screening data to the LIMs. GLS consists of TSM cards configured with GLS software. They are only needed when LIMs or TSMs must be reloaded.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0291 ** GLS SYSTEM          GLS is at minimum service limit

Alarm Level: Major

Recovery

  1. Use the rept-stat-card command to verify status of the TSM cards providing GLS.
    This command identifies the cards still IS-NR (In-Service – Normal) and those cards which are out of service. For example, enter:
    rept-stat-card
  2. Use the init-card command to reinitialize the card and force gateway screening (GWS) data to be downloaded from the active MASP to the TSM.
  3. After GWS data has been successfully downloaded, use rept-stat-card to verify the card(s) have returned to service.
  4. If the card(s) do not return to IS-NR, then reseat the card(s).
  5. If the card(s) still do not return to IS-NR, replace the card(s).
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.232 0292 - GLS is Not Available

Generic loading services (GLS) is not able to function; the EAGLE 5 ISS may not be performing gateway screening (GWS).

At least one card should be returned to IS-NR status. This makes GLS available and changes the alarm level to major (0291 - GLS is at Minimum Service Limit). The alarm clears after two TSM cards have returned to IS-NR.

Example 
   RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*C 0100 0292 *C GLS SYSTEM          GLS is not available

Alarm Level: Critical

Recovery

  1. Use the rept-stat-card command to verify status of the TSM cards providing GLS.

    For example, enter:

    rept-stat-card
    Example of the output: 
    RLGHNCXA03W 00-09-27 16:43:42 EST   EAGLE  31.3.0
CARD   VERSION    TYPE    APPL      PST           SST       AST
1113  022-000-000 MCAP    OAM       IS-NR         Active    -----
1114  ----------- TDM     --------  -----         -----     -----
1115  022-000-000 MCAP    OAM       IS-NR         Standby   -----
1116  ----------- TDM     --------  -----         -----     -----
1117  ----------- MDAL    --------  IS-NR         Standby   -----
1204  022-000-000 LIMOCU  SS7ANSI   OOS-MT        Isolated  -----
1205  022-000-000 LIMOCU  SS7ANSI   IS-NR         Active    -----
1206  022-000-000 LIMOCU  SS7ANSI   OOS-MT        Isolated  -----
1216  022-000-000 TSM     SCCP      IS-ANR        Standby   -----
1218  022-000-000 TSM     GLS       OOS-MT        Isolated  -----
1312  022-000-000 LIMDS0  SS7ANSI   IS-NR         Active    -----
1313  022-000-000 LIMOCU  SS7ANSI   OOS-MT        Idle      -----
Command Completed.
  2. Use the init-card command to reinitialize the card and force gateway screening (GWS) data to be downloaded from the active MASP to the TSM.
  3. The following message should appear. 
    RLGHNCXA03W  00-02-07  11:11:28 EST  EAGLE 35.0.0
Init Card command issued to card 1218
  4. After GWS data has been successfully downloaded, use rept-stat-card to verify the card(s) have returned to service.
  5. If the card(s) do not return to IS-NR, then reseat the card(s).
  6. If the card(s) still do not return to IS-NR, replace the card(s).
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.233 0293 - GLS Have Been Removed From The System

Generic loading services (GLS) has been removed from the system, because all TSMs configured for GLS have been deleted through database administration commands.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0293    GLS SYSTEM          GLS have been removed from the system

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message alerts the user that all TSMs configured for GLS have been deleted from the system.

No action is necessary unless gateway screening is required.

3.2.234 0294 - REPT-ALMINH: Alarm Output PERM Inhibit

This message indicates that alarms for the indicated device are permanently inhibited at the indicated level.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    6277.0294    RTXA    001-101-001     REPT-ALMINH: alarm output PERM Inhibit
                 OPCA=   004-004-004
                 ALARM INHIBIT LEVEL:   MAJR

Note:

The output can vary significantly. Alarm Inhibit alarms are generic and the output varies depending on which alarm/device is inhibited. This example utilizes the CARD format.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.235 0295 - REPT-ALMINH: Alarm Output Enabled

This message indicates the restoration of the reporting of alarms for the indicated device at the indicated level.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 31.5.0
0100.0295    CARD 1101 SCCP        REPT-ALMINH: alarm output enabled
             ALARM INHIBIT LEVEL:   MAJR

Note:

The output can vary significantly. Alarm Inhibit alarms are generic and the output varies depending on which alarm/device is inhibited.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.236 0296 - REPT-ALMINH: Alarm Output TEMP Inhibit

This message indicates that alarms for the indicated device are temporarily inhibited at the indicated level.

Example 
tekelecstp 09-11-06 14:56:48 EST  EAGLE 41.1.0
0045.0296    IP7CONN applsock1       REPT-ALMINH: alarm output TEMP Inhibit      ALARM INHIBIT LEVEL:   MAJR

Note:

The output can vary significantly. Alarm Inhibit alarms are generic and the output varies depending on which alarm/device is inhibited.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.237 0297 - Incorrect Port Configuration

This message indicates that a MPL card with more than ports A and B provisioned has been replaced with a 2 port DS0-A LIM card. This alarm is also generated if an MPL card is placed in a LIM slot which has either port A or port B provisioned as non-56K bps link speed.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0297  ** CARD 1108  SS7ML     Incorrect LIM port configuration
                HW VERIFICATION CODE: xxx

Alarm Level: Major

Recovery

  1. If this message contains the optional line ‘HWVERIFICATIONCODE: xxx’:
    • Decode the xxx value and correct the indicated problem.

      See Hardware Verification Codes in UAMs the section on hardware verification codes in the Unsolicited Alarms and Information Messages manual.

    • After correcting the problem, the card will be in out-of-service maintenance disabled state (OOS-MT-DSBLD).

      Restore the card back to in-service normal state (IS-NR) with the alw-card command.

  2. If this message does not contain the optional line ‘HWVERIFICATIONCODE: xxx’, perform either of the following:
    • Replace the LIM DS0-A card with an MPL card.

      OR

    • This card has only 2 ports.

      Re-provision this DS0-A card and provision only ports A and B. Refer to the Database Administration Manual - SS7 to fix the incorrect port configuration.

    Note:

    For the complete list of cards supported by EAGLE Release 47.0, see Hardware Reference Guide.

3.2.238 0298 - Card Not Using config. SCTP csum Method

The IPLIMx/IPGWx card issues this UAM alarm when the card's active SCTP checksum algorithm does not match the configured SCTP checksum algorithm in the IP OPTIONS table.

Example 
RLGHNCXA21W 03-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0298  * CARD  1115 DCM   Card not using config. SCTP csum method

Alarm Level: Minor

Recovery

  1. The SCTP checksum algorithm option is configured via the chg-sg-opts command and is stored in the IP OPTIONS table.
    The update applies to the IP OPTIONS tables on disk and IPLIMx/IPGWx card memory. Note that when the SCTP checksum algorithm is updated, IPLIMx/IPGWx cards may not immediately change to the updated checksum algorithm. Before IPLIMx/IPGWx cards can use the configured SCTP checksum algorithm, one of the following conditions must exist.
    • No SCTP associations exist on the IPLIMx/IPGWx card.
    • All SCTP associations provisioned on the IPLIMx/IPGWx card are open=no.
    • The IPLIMx/IPGWx card is initialized.
  2. In an installed system, use either of two methods to condition the cards to accept the change in checksum algorithms:
    • Card initialization (use the init-card command) or
    • Change card association (chg-assoc:aname=xxx:open=no)

      For details about these commands, refer to the Commands Manual.

  3. Issue the chg-sg-opts:sctp_csum=value command to define the checksum algorithm to be used in all SCTP associations.

3.2.239 0299 - Config. SCTP csum Method Alarm Cleared

The SCTP checksum UAM alarm is cleared when the card's active SCTP checksum algorithm matches the configured SCTP checksum algorithm.

Example 
RLGHNCXA21W 03-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0299    CARD  1115 DCM  Config. SCTP csum method alarm cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.240 0300 - TVG Grant Failure

This message indicates that for some card in the system, the grant mechanism (as part of the Multicast Capacity Feature) failed for at least 60 seconds, or more than one time for a 15-second period. A TVG granter failure is defined as a TVG request that completes with a time-out (hardware or software) and/or a status value where the Granter Present bit is not set.

Example 
RLGHNCXA21W 09-04-06 11:55:14 EST  EAGLE5 40.3.0-62.15.21
**  0016.0300 ** CARD 1203 SS7ML    TVG Grant Failure
                 INFO:   SCCP  --N---

Alarm Level: Major

Recovery

  1. Enter the following command to verify the status of the TVG granter:
    rept-stat-card:loc=xxxx:mode=full

    where xxxx is the card location identified in the output.

    Example of the output: 
    tekelecstp 08-09-25 12:06:24 IST  EST  EAGLE 39.2.0
    CARD   VERSION      TYPE      GPL        PST            SST        AST
    1204   131-016-000  LIME1     SS7HC      IS-NR          Active     -----
      ALARM STATUS       =  No Alarms.
      IMTPCI  GPL version = 131-007-000
      BLVXW6  GPL version = 131-009-000
      BLDIAG6 GPL version = 131-008-000
      BLBEPM  GPL version = 128-021-000
      PLDPMC1 GPL version = 128-021-000
      BLCPLD  GPL version = 128-021-000
      IMT BUS A           = Conn
      IMT BUS B           = Conn
      CLOCK A             = Active
      CLOCK B             = Fault
      CLOCK I             = Idle
      HS CLOCK A          = Fault
      HS CLOCK B          = Fault
      HS CLOCK I          = Idle
      MBD BIP STATUS      = Valid
      MOTHER BOARD ID     = EPM A
      DBD STATUS          = Valid
      DBD TYPE            = E1T1
      DBD MEMORY SIZE     = 512M
      HW VERIFICATION CODE = ----
      CARD WARNING        = OBSOLETE FRAMER
      CURRENT TEMPERATURE   =  36C ( 97F)
      PEAK TEMPERATURE:     =  37C ( 99F)     [04-01-05 11:33]
      SIGNALING LINK STATUS
          SLK    PST                LS            CLLI
          A      OOS-MT-DSBLD       lsb           -----------
      TVG STATUS
          SNM     TVG RESULT   = 24 hr: ------, 5 min: ------
          SCCP    TVG RESULT   = 24 hr: ------, 5 min: ------
          INM     TVG RESULT   = 24 hr: ------, 5 min: ------

    Command Completed.
  2. The group ticket voucher status is displayed in these fields:
    • SCCP TVG RESULT (for SCCP messages)
    • INM TVG RESULT (for INM messages)
    • SNM TVG RESULT (for SNM messages)

    Note:

    SNM represents network management messages received by the EAGLE (for example, TFP). INM represents network management events internal event processing.
    Group ticket voucher status output is displayed as a series of these letters:
    G
    Service Granted. Indicates normal system behavior.
    D
    Service Denied. Indicates an overload, but the group ticket voucher hardware and software are working correctly.
    N
    No granter in the system. For GTT traffic, there may be no TSM-SCCP cards or ACMs in the system. If there are TSM-SCCP cards or ACMs in the system, then a serious failure is indicated (hardware or software bug or hardware failure)
    H
    Hardware time-out. Indicates the hardware timed out waiting for a group ticket voucher packet to return. Group ticket voucher packets can be lost when a card is plugged in or booted. This is a serious condition if cards have not been connecting or disconnecting from the IMT.
    S
    Software time-out. No result was ever returned from hardware, indicating a probable hardware failure.
    I
    Invalid result from hardware.

3.2.241 0301 - TVG Grant Recovery

This message indicates the Multicast Capacity Feature for handling SNM or SCCP traffic is functioning, and a previous problem has cleared.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0301     CARD 1201  OAM    TVG Grant Recovery

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.242 0302 - Cooling Fan Failure

The cooling fan hardware is not working.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0302  *  SYSTEM       Cooling fan failure

Alarm Level: Minor

Recovery

  1. At the fan assembly, verify that the Fan Switch on the grill panel is in the ON position.
  2. At the FAP, verify the fuses for the fan assembly.
    The fuse card will be marked FAN A and FAN B, fuse positions 6, 12, and 18 (A and B). Fuse position 6 is for the fan unit directly below the control shelf. Fuse position 12 is for the fan directly below the 1200 shelf. Fuse position 18 is for the fan directly below the 1300 shelf. All fans are to be fused at 2 amps (with orange flags) per feed.
  3. At the EAGLE 5 ISS terminal, enter the following command to verify that the fan feature is turned on.
    rtrv-feat

    Note:

    Once you have turned on the feature, you cannot turn it off. The feature applies to any and all fans installed within the system. When replacing a fan assembly, the feature should already be turned on.
    The output displays a list of optional features and their status on the system. 
    RLGHNCXA03W 99-01-28 11:34:04 EST EAGLE 35.0.0
EAGLE FEATURE LIST
GTT = off
GWS = on
CRMD = off
X25G = on
LAN = on
SEAS = on
LNP = off
LNP12MIL = off FAN = on
DSTN4000 = on
WNP = on
CNCF = on
SCCPCNV = on
TCAPCNV = on
TLNP = on
x252000 = on
  4. If FAN = on does not appear in the output, enable the fan feature by entering the following command:
    chg-feat:fan=on
    After the program updates, the system returns output similar to the following: 
    RLGHNCXA03W 97-03-11 11:34:04 EST EAGLE 35.0.0
CHG-FEAT: MASP A - COMPLD
  5. At the rear of the frame, verify the A power cable from the A fan assembly is securely attached.
  6. At the rear of the frame, verify the B power cable from the B fan assembly is securely attached.
  7. At the EAGLE 5 ISS terminal, type in this command:
    rept-stat-trbl
    If the EAGLE 5 ISS reports the following alarm, replace the cooling fan. 
    302 COOLING FAN FAILURE
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.243 0303 - Cooling Fans Normal

The cooling fan hardware has returned to service.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0303     SYSTEM      Cooling Fans Normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.244 0304 - REPT-NMTSK-DSCD: SNM Discard Onset

This message indicates that the number of system network messages has exceeded the threshold and messages are being discarded.

Example 
   RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0304   *   CARD 1113 OAM     REPT-NMTSK-DSCD: SNM Discard Onset

Alarm Level: Minor

Recovery

Check for problems in the network that would cause excessive network management messages to be broadcast.

3.2.245 0305 - RECVY-NMTSK-DSCD: SNM Discard Abated

This message indicates that network messages are no longer being discarded.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0305      CARD 1113 OAM      REPT-NMTSK-DSCD: SNM Discard Abated

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous condition has been corrected.

No further action is necessary.

3.2.246 0306 - SNM Overload Onset

This message indicates that network management messages are approaching the threshold where they will be discarded.

Example 
   RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0306   *   CARD 1113 OAM        SNM Overload Onset

Alarm Level: Minor.

Recovery

Check for problems in the network that would cause excessive network management messages to be broadcast.

3.2.247 0307 - SNM Overload Abated

This message indicates that the threat of network messages being discarded no longer exists.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0307    CARD 1113 OAM        SNM Overload Abated

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous condition has been corrected.

No further action is necessary.

3.2.248 0308 - Node Isolated Due to SLK Failures

The EAGLE 5 ISS is isolated from other signaling points. All system links are down. Possible causes are as follows:

  • Primary and secondary clock sources have failed.

  • Signaling links have been manually cancelled.

  • All cards have been manually inhibited.

  • Both IMT busses have failed.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*C 0100.0308 *C SYSTEM            Node isolated due to SLK failures

Alarm Level: Critical

Recovery

  1. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  2. Restore the signaling links to service by entering the following:
    act-slk:loc=xx:port=x
    The following message should appear: 
    RLGHNCXA03W  00-02-07  11:11:28 EST  EAGLE 35.0.0
Activate SLK message sent to card.
  3. Enter the following to restore the cards:
    rst-card:loc=xxxx

    Note:

    The card locations (xxxx) must be specified and the command repeated for each card.
    Automatic recovery of the SLKs should occur.
  4. Activate measurements using the chg-meas:collect=on command.
    This starts measurements collection.

    Note:

    Refer to the Measurements Manual for traffic measurements information.

3.2.249 0309 - Node is no longer isolated

This message occurs when the node has been in node isolation due to signaling link failures. Enough links have recovered so that the node is no longer isolated and signaling can occur.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0309    SYSTEM              Node is no longer isolated

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.250 0311 - DPC is allowed

A previous fault is corrected and the EAGLE 5 ISS system can send traffic to a specified point code.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0311    DPC 144-201-001     DPC is allowed
             LSN=nc00027
             Prohibited SS  1, 5, 18
             Allowed SS     3, 6
             Blocked SS     100, 103
             Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.251 0312 - DPC is Restricted

A transfer-restricted message has been received concerning the DPC. Possible causes:

  • One or more routes to this DPC are unavailable.

  • A low priority route is carrying the traffic. The primary and combined routes are not available for traffic to the given DPC.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
*  0014.0312  * DPC 144-201-001     DPC is restricted
                LSN=nc00027
                Prohibited SS  1, 5, 18
                Allowed SS     3, 6
                Blocked SS     100, 103
                Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: Minor

Recovery

  1. Enter the rept-stat-rte command using the DPC specified from the output message to determine which linkset has a problem.
  2. Enter the rept-stat-ls using the linkset name specified from the output of Step 1 to determine which link(s) could have a problem.
  3. Use local procedures to test the link facilities.

3.2.252 0313 - DPC is prohibited

Traffic to the DPC is prohibited. Possible causes:

  • All routes to this DPC are unavailable.

  • Adjacent point code link failures or nonadjacent failure in the route.

Example 
 12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  0044.0313 *C DPCN24    001-001-001   DPC is prohibited
                 LSN=lsn012345
                 Prohibited SS  5, 20
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: Critical

Recovery

  1. Enter the rept-stat-rte command using the DPC specified from the output message to determine which linkset has a problem.
  2. Enter the rept-stat-ls using the linkset name specified from the output of Step 1 to determine which link(s) could have a problem.
  3. Use local procedures to test the link facilities.

3.2.253 0314 - Route is Allowed

The primary route to the DPC can carry traffic.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0314    DPC 144-201-001     Route is allowed
             LSN=nc00027
             Prohibited SS  1, 5, 18
             Allowed SS     3, 6
             Blocked SS     100, 103
             Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.254 0315 - Route is Restricted

Traffic in the primary route to the DPC is restricted. This could indicate signaling link failures for a non-adjacent DPC.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0315    DPC 144-201-001     Route is restricted
             LSN=nc00027
             Prohibited SS  1, 5, 18
             Allowed SS     3, 6
             Blocked SS     100, 103
             Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact the far-end to test and correct the problem.

3.2.255 0316 - Route is Prohibited

The route to the DPC cannot carry traffic to the DPC. Following are the possible causes:

  • Local SLK failures

  • Non-adjacent DPC SLK failures

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0316    DPC 144-201-001     Route is prohibited
             LSN=nc00027
             Prohibited SS  1, 5, 18
             Allowed SS     3, 6
             Blocked SS     100, 103
             Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the rept-stat-rte command using the DPC specified from the output message to determine which linkset has a problem.
    If it specifies a non-adjacent linkset, contact the far-end to test and correct the problem.
  2. If it appears to be a local signaling link failure enter the rept-stat-ls using the linkset name specified from the output of 1 to determine which link(s) could have a problem.
  3. Verify the link status using the rept-stat-slk command.
    For example, enter:
    rept-stat-slk:loc=:port=b
    Example of the output: 
    RLGHNCXA03W 00-09-27 17:00:36 EST  EAGLE 35.0.0
SLK     LSN          CLLI         PST           SST        AST
1203,B  nsp1         ls02clli     OOS-MT        Unavail     ----
  ALARM STATUS       =  No alarm
  UNAVAIL REASON     =  FL NA LI RI 
Command Completed.
  4. Check the UNAVAIL REASON field in the output of the rept-stat-slk command.
    Following is an explanation of the UNAVAIL REASON codes:
    FL – The signaling link has a fault.
    NA – The signaling link is not aligned.
    LI – The signaling link has been inhibited locallyRI – The signaling link has been inhibited remotely.
    LB – The signaling link has been blocked locally.
    RB – The signaling link has been blocked remotely.
    FC – The signaling link is unavailable because of false congestion.
    RD(xx.xxx) - The signaling link is unavailable because of a restart delay to prevent signaling link oscillation. The number in parentheses indicates the amount of time, in seconds, remaining in the restart delay period. The link is restarted automatically after this amount of time has elapsed.
  5. If the UNAVAIL REASON indicates an alignment problem or fault, activate a loopback using the act-lpb command, or use a physical loopback.
    (For a V.35, you must use an appropriate physical V.35 loopback.) If the signaling link aligns, contact the far-end to correct the problem.
  6. If the UNAVAIL REASON still indicates an alignment problem or fault, check the status of the card by entering the rept-stat-card command for the specified card.
  7. If the rept-stat-card command indicates a problem with the card, reset the card by entering the init-card command with the specified card location.
    If the card still does not align, try first reseating the card, then replacing the card. Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  8. If the UNAVAIL REASON indicates a locally inhibited link, enter the unhb-slk command with the specified card location.
  9. If the UNAVAIL REASON indicates a locally blocked link, enter the ublk-slk command with the specified card location.
  10. If the signaling is blocked or inhibited remotely, contact the far-end to place the link in-service.

3.2.256 0317 - RCVRY-LKSTO: Link set allowed

The linkset is returned to service.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0317    LSN a24546     RCVRY-LKSTO: Link set allowed

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous condition has been corrected.

No further action is necessary.

3.2.257 0318 - REPT-LKSTO: Link Set Prohibited

This message indicates a linkset is out of service.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
** 0014.0318 **   LSN a54646     REPT-LKSTO: Link set prohibited

Alarm Level: Major

Recovery

  1. Verify the link status using the rept-stat-slk command.

    For example, enter:

    rept-stat-slk:loc=1203:port=b
    Example of the output: 
    RLGHNCX A03W 00-02-07 12:02:36 EST  EAGLE 35.0.0 
    SLK     LSN          CLLI         PST           SST        AST
    1203,B  nsp1         ls02clli     OOS-MT        Unavail     ----
       ALARM STATUS       =  No alarm
       UNAVAIL REASON     =  FL NA LI RI 
    Command Completed.
  2. Check the UNAVAIL REASON field in the output of the rept-stat-slk command.
    Following is an explanation of the UNAVAIL REASON codes:
    • FC – The signaling link is unavailable because of false congestion.
    • FL – The signaling link has a fault.
    • NA – The signaling link is not aligned.
    • LI – The signaling link has been inhibited locallyRI – The signaling link has been inhibited remotely.
    • LB – The signaling link has been blocked locally.
    • RB – The signaling link has been blocked remotely.
    • RD(xx.xxx) – The signaling link is unavailable because of a restart delay to prevent signaling link oscillation. The number in parentheses indicates the amount of time, in seconds, remaining in the restart delay period. The link is restarted automatically after this amount of time has elapsed.
  3. If the UNAVAIL REASON indicates an alignment problem or fault, activate a loopback using the act-lpb command, or use a physical loopback.
    (For a V.35, you must use an appropriate physical V.35 loopback.) If the signaling link aligns, contact the far-end to correct the problem.
  4. If the UNAVAIL REASON still indicates an alignment problem or fault, check the status of the card by entering the rept-stat-card command for the specified card.
  5. If the rept-stat-card command indicates a problem with the card, reset the card by entering the init-card command with the specified card location.
    If the card still does not align, try first reseating the card, then replacing the card. Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  6. If the UNAVAIL REASON indicates a locally inhibited link, enter the unhb-slk command with the specified card location.
  7. If the UNAVAIL REASON indicates a locally blocked link, enter the ublk-slk command with the specified card location.
  8. If the signaling is blocked or inhibited remotely, contact the far-end to place the link in-service.

3.2.258 0319 - REPT-MTPLP-DET: Circ rte det(cong)

The system automatically tests for circular routing when congestion occurs on an ANSI signaling link. If the routing data was provisioned incorrectly, or was corrupted, MSUs could be routed in an endless circular route. The incorrect routing data could be on the system or at a remote STP. This message indicates that circular routing has been detected.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
*C  0044.0319 *C RTXN24    001-101-001   REPT-MTPLP-DET: Circ rte det(cong)
                 OPCA=   007-001-000
                 XMIT LSN=ls04   RC=20
                 RCV LSN=lsna05
                 MEMBER=011-210-004

Alarm Level: Critical

Recovery

  1. Enter the following command to check the routing information for the specified DPC:
    rtrv-rte
    If the problem is in the routing table of an adjacent node, contact the node (identified in the rtrv-rte command output) to resolve the circular routing problem. If the routing information is correct, continue with 4. If there is an error in the routing information, continue with 2.
  2. Enter the following command to delete the route in the error message from the database:
    dlt-rte:aaaa=xxx-xxx-xxx:lsn=yyyy

    whereaaa = dpc, dpca, dpci, or dpcn xxx-xxx-xxx = destination point code and yyyy = the linkset name associated with the route.

  3. To enter the correct route information, refer to Database Administration - SS7 User's Guide for the procedure on adding a route to the SS7 configuration.
  4. Enter the following command to reset the destination circular routing status:
    rst-dstn:dpc=x-x-x

    where x-x-x = the destination point code of the destination.

3.2.259 0320 - REPT-MTPLP-SUST: Sustained circ rt(cong)

The system automatically tests for circular routing when congestion occurs on an ANSI signaling link. If the routing data was provisioned incorrectly, or was corrupted, MSUs could be routed in an endless circular route. The incorrect routing data could be on the system or at a remote STP. This message indicates that circular routing has been detected.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0
*C 0014.0320 *C DPC 011-210-*   REPT-MTPLP-SUST: Sustained circ rt(cong)
                XMT LSN=ls01  RC=10
                RCV LSN=ls14
                MEMBER=011-210-007

Alarm Level: Critical

Recovery

  1. Enter the following command to check the routing information for the specified DPC:
    rtrv-rte

    If the problem is in the routing table of an adjacent node, contact the node (identified in the rtrv-rte command output) to resolve the circular routing problem. If the routing information is correct, continue with 4. If there is an error in the routing information, continue with 2.

  2. Enter the following command to delete the route in the error message from the database:
    dlt-rte:aaaa=xxx-xxx-xxx:lsn=yyyy

    where aaa = dpc, dpca, dpci, or dpcn xxx-xxx-xxx = destination point code and yyyy = the linkset name associated with the route.

  3. Refer to the "Adding a Route" procedures in Database Administration Manual - SS7 to enter the correct route information.
  4. Enter the following command to reset the destination circular routing status:
    rst-dstn:dpc=x-x-x

    where x-x-x = the destination point code of the destination.

3.2.260 0321 - X-LIST occupancy threshold exceeded

This message indicates that the number of x-list entries has exceeded a specified threshold.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0321  *  XLIST             X-LIST occupancy threshold exceeded

Alarm Level: Minor

Recovery

  1. To display the system-wide parameters for cluster routing, enter the command:
    rtrv-stpopts
    Example of the output: 
    
RLGHNCXA03W  00-07-23  16:02:34 EST  EAGLE. 31.3.0   STP OPTIONS
-------------------------
MTPT31CTL               1
MTPLT1                yes
MTPLTCTDPCQ             3
MTPLTST             10000
MTPXLQ                500
MTPXLET              0100
MTPXLOT               90%
MTPDPCQ              2000
TFATFRPR             1000
MTPRSI                yes
MTPRSIT              5000
    The mtpxlq parameter is the total number of dynamic status exception list (x-list) entries the EAGLE 5 ISS maintains. There are 2500 total table entries. The default values allow for 2000 entries for provisioned destinations and 500 for x-list entries. (If you increase the number of x-list entries, you must decrease the number of DPCs that can be provisioned by changing the mtpdpcq parameter.) The mtpxlet parameter is the maximum amount of time the EAGLE 5 ISS maintains an unreferenced x-list entry. The mtpxlot parameter is the threshold that this message refers to.
  2. Use the chg-stpopts to change the number of x-list entries, the x-list expiration timer, or to raise the threshold for notification of a full x-list.
  3. If the problem persists, use the dact-rstst command to eliminate specific x-list entries.

3.2.261 0322 - X-LIST occupancy below threshold

This message indicates that the number of x-list entries has fallen below a specified threshold.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0322    XLIST               X-LIST occupancy below threshold

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.262 0324 - DPC Subsystem is Allowed

All subsystems at the indicated DPC are reachable.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0   0014.0324    DPC 144-201-001     DPC subsystem is allowed
LSN=nc00027                
Prohibited SS  1, 5, 18                
Allowed SS     3, 6                
Blocked SS     100, 103                
Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.263 0325 - DPC Subsystem is Blocked

The DPC subsystem is blocked due to administrative action.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
*C 0014.0325 *C DPC 144-201-001     DPC subsystem is blocked
                LSN=nc00027
                Prohibited SS  1, 5, 18
                Allowed SS     3, 6
                Blocked SS     100, 103
                Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: Critical

Recovery

Contact the far-end to correct the problem.

3.2.264 0326 - DPC Subsystem is Prohibited

The indicated DPC Subsystem is prohibited.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
*C 0014.0326 *C DPC 144-201-001     DPC subsystem is prohibited
                LSN=nc00027
                Prohibited SS  1, 5, 18
                Allowed SS     3, 6
                Blocked SS     100, 103
                Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: Critical

Recovery

Contact the far-end to correct the problem.

3.2.265 0327 - DPC Subsystem Has Been Deleted

This indicates a DPC subsystem has been deleted from the system global title translation (GTT) tables.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0327    DPC 144-201-001     DPC subsystem has been deleted
             LSN=nc00027
             Prohibited SS  1, 5, 18
             Allowed SS     3, 6
             Blocked SS     100, 103
             Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected by deletion of the entity.

No further action is necessary.

3.2.266 0328 - SCCP is available

The SCCP subsystem was previously unavailable and has returned to service.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0328    SCCP SYSTEM           SCCP is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.267 0329 - System SCCP TPS Normal

The SCCP subsystem is operating normally, using the TVG (Group Ticket Voucher load balancing algorithm) message transport method. The TPS (Transactions Per Second) rate is below its capacity threshold, as defined by the chg-th-alm command.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0329    SCCP SYSTEM         SCCP capacity normal, card(s) abnormal

Note:

UAM 329 will only be raised only if there is at least one IS-ANR SCCP card in EAGLE.

Alarm Level: Minor.

Recovery

  1. This alarm is used in conjunction with alarm #0330 “System SCCP TPS Threshold Exceeded.” For every five minutes the Eagle is above the threshold, the ATH (Application Trouble Handler) reports the minimum, maximum and average TPS value seen during the past five minute period.
    When the TPS level drops below the threshold level for 30 seconds, the alarm stops, and alarm #0329 confirms that normal operation has resumed. (Alternatively, the user can clear this alarm by raising the threshold limit to a value greater than the maximum value, in which case, the alarm stops immediately.)
  2. To obtain details, use the rept-stat-sccp command, which displays the status of the SCCP and VSCCP cards and other services and determines the capacity threshold of the SCCP TPS rate.
    This command also identifies which DSM cards are OOS-MT. For example, enter:
    rept-stat-sccp
    Example of the output: 
    eaglestp 00-10-24 20:38:58 EST EAGLE 35.0.0
    SCCP SUBSYSTEM REPORT IS-NR          Active      -----
    SCCP Cards Configured= 1  Cards IS-NR= 1   Capacity Threshold = 80%
    CARD   VERSION     PST        SST         AST      MSU USAGE   CPU USAGE 
    -------------------------------------------------------------------------
    1212   021-001-000 IS-NR      ACTIVE      ALMINH       47%         32%
    -------------------------------------------------------------------------
    SCCP Service Average MSU Capacity = 47%      Average CPU Capacity = 32%
    
    Command Completed.

3.2.268 0330 - System SCCP TPS Threshold Exceeded

This message indicates EAGLE has exceeded its TPS (Transactions Per Second) message transport rate threshold. For every 30 seconds EAGLE is above the threshold, an ATH (Application Trouble Handler) reports the minimum, maximum and average TPS value seen during the past 30-second period.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0330 ** SCCP SYSTEM      System SCCP TPS Threshold exceeded

Alarm Level: Major

Recovery

  1. Use rept-stat-sccp to determine the status of the SCCP subsystem.
    This command also identifies which SCCP cards are OOS-MT. For example, enter:
    rept-stat-sccp
    Example of the output: 
    eaglestp 00-10-24 20:38:58 EST EAGLE 35.0.0
    SCCP SUBSYSTEM REPORT IS-NR          Ovflw-1       -----
    SCCP Cards Configured= 4 Cards       IS-NR= 4
    System TCP Alarm Threshold =  80% Total capacity 
    System Peak SCCP Load =  3000 TPS
    System Total SCCP Capacity =  5000 TPS
    CARD   VERSION     PST        SST         AST      MSU USAGE   CPU USAGE 
    -------------------------------------------------------------------------
    1212   021-001-000 IS-NR      ACTIVE      ALMINH       47%         32%
    -------------------------------------------------------------------------
    SCCP Service Average MSU Capacity = 47%     Average CPU Capacity = 32%
    
    Command Completed.
    Use the command rept-stat-sccp:mode=perf to retrieve the maximum and average values, if desired.
  2. The user may clear this alarm by raising the threshold limit to a value greater than the maximum value.
    In this case, the alarm stops immediately. You should use the rtrv-th-alm command to list the threshold rate, and you may use the chg-th-alm command to change the threshold value.
  3. The user should evaluate this new traffic level and determine whether additional SCCP cards are required to maintain the TPS level the system is processing.
  4. Use the rept-stat-card command to display the card status and maintenance activity states.
    Examine the report for any cards that may be OOS-MT.
  5. Use the init-card command to initialize any cards(s) that are OOS-MT.
    This causes the card(s) to reload the MTP data as well as GTT data tables.
  6. Again using the rept-stat-sccp command, verify the card(s) have returned to service.
    If any card(s) have failed to return to IS-NR, reseat the card(s).
  7. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.269 0331 - SCCP is Not Available

The SCCP subsystem is not available to any LIM(s). All TSM/DSM-SCCP cards have failed.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*C 0100.0331 *C SCCP SYSTEM         SCCP is not available

Alarm Level: Critical

Recovery

  1. Use rept-stat-sccp command to determine the status of the SCCP subsystem.
    This command also identifies which TSM/DSM cards are OOS-MT. For example, enter:
    rept-stat-sccp
    Example of the output: 
    RLGHNCXA03W 00-02-07 16:10:50 EST  EAGLE 35.0.0
SCCP SUBSYSTEM REPORT IS-NR          Active     -----
SCCP Cards Configured= 1  Cards IS-NR= 1  Capacity Threshold = 100%
CARD   VERSION      PST        SST        AST       MSU USAGE  CPU USAGE
    ---------------------------------------------------------------------
1212   021-001-000  IS-NR      Active     ALMINH       47%      32%
    ---------------------------------------------------------------------
SCCP Service Average MSU Capacity = 47%    Average CPU Capacity = 32%
    Command Completed.
  2. Reinitialize any card(s) not in an IS-NR state using the init-card command.
  3. After the card(s) have been reloaded, use the rept-stat-sccp command to verify the SCCP subsystem has returned to full capacity.
  4. If any card(s) fail to return to IS-NR, reseat the card(s).
  5. If the card(s) still do not return to IS-NR, replace the card(s).
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.

3.2.270 0332 - DPC Subsystem is prohibited and blocked

A subsystem is both prohibited and blocked as reported by the network.

Example 
   RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
*C 0014.0332 *C DPC 144-201-001   DPC Subsystem is prohibited and blocked
                LSN=nc00027
                Prohibited SS  1, 5, 18
                Allowed SS     3, 6
                Blocked SS     100, 103
                Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: Critical

Recovery

Contact the far-end to test and correct the problem.

3.2.271 0333 - DPC Subsystem is Normal

The DPC subsystem indicated in the output message is now allowed.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0333    DPC 144-201-001     DPC Subsystem is Normal
             LSN=nc00027
             Prohibited SS  1, 5, 18
             Allowed SS     3, 6
             Blocked SS     100, 103
             Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.272 0334 - DPC Subsystem is Abnormal

The indicated DPC subsystem is not reachable through the normal route.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
*C 0014.0334 *C DPC 144-201-001     DPC Subsystem is Abnormal
                LSN=nc00027
                Prohibited SS  1, 5, 18
                Allowed SS     3, 6
                Blocked SS     100, 103
                Unblocked SS   2, 102, 221
Legend
ALLOWED SS
Allowed subsystem
BLOCKED SS
Blocked subsystem
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem
UNBLOCKED SS
Unblocked subsystem

Alarm Level: Critical

Recovery

  1. Enter the rept-stat-rte command using the DPC specified from the output message to determine which linkset has a problem.
  2. Enter the rept-stat-ls using the linkset name specified from the output of Step 1 to determine which link(s) could have a problem.
  3. Use local procedures to test the link facilities.

3.2.273 0335 - SCCP is Removed

All Service Module cards have been deleted from the database; SCCP services are not available to the system. This message is the result of a deliberate action. Removing all Service Module cards from the database may have been an action from another maintenance procedure. If you wish to restore SCCP services to the system, perform the following procedure. For more information about adding a card to the system, refer to the Database Administration Manual - Global Title Translation.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0335    SCCP SYSTEM         SCCP is removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Use the ent-card command to reenter the Service Module cards into the system database.
  2. Use the rst-card command to return the card(s) to service.
    This causes the MASP to begin downloading global title translation (GTT) tables to the Service Module card.
  3. Use the rept-stat-sccp command to verify that the card(s) have been restored, after the MASP has completed loading.

3.2.274 0336 - LIM(s) Have Been Denied SCCP Service

Some LIM(s) are using the SCCP subsystem, but others have been denied service. This is due to underprovisioning, and will require more Service Module cards to be added.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0336 ** SCCP SYSTEM       LIM(s) have been denied SCCP service

Alarm Level: Major

Recovery

  1. Use rept-stat-sccp command to determine which LIMs have been denied SCCP service.
    For example, enter:
    rept-stat-sccp
    Example of the output: 
    RLGHNCXA03W 00-02-07 16:10:50 EST  EAGLE 35.0.0
SCCP SUBSYSTEM REPORT IS-NR          Active     -----
SCCP Cards Configured= 1  Cards IS-NR= 1  Capacity Threshold = 100%
CARD   VERSION      PST        SST        AST       MSU USAGE  CPU USAGE
    ---------------------------------------------------------------------
1212   021-001-000  IS-NR      Active     ALMINH       47%       32%
    ---------------------------------------------------------------------
SCCP Service Average MSU Capacity = 47%    Average CPU Capacity = 32%
    Command Completed.
  2. Add TSM/DSM-SCCP cards one at a time.
    Monitor the performance of the SCCP subsystem with the rept-stat-sccp command to determine whether additional cards are needed.

3.2.275 0337 - DPC - SS Status Changed

This output is related to other DPC alarm messages. It indicates that one or more subsystems with an existing alarm condition has had a change in status. The message indicates the new status of the subsystem. A previous alarm condition has not cleared.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0337    DPC 001-001-001       DPC-SS status changed
             LSN=A1234567
             Prohibited SS 5, 20
Legend
LSN
Linkset name. The name must be unique.
PROHIBITED SS
Prohibited subsystem

Alarm Level: No alarm condition. The message is informational only.

Recovery

Follow the troubleshooting procedure for the previous alarm.

3.2.276 0338 - X-LIST space full-entry(s) discarded

This message indicates that the total number of dynamic status exception list (x-list) entries for cluster routing has exceeded the maximum number configured. No more entries can be added to the list. This can occur because the maximum number of x-list entries is set too low, the timer that eliminates x-list entries after a specified period is set too long, or the x-list needs to be culled.

Example 
   RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0338  **  XLIST            X-LIST space full-entry(s) discarded

Alarm Level: Major

Recovery

  1. To display the system-wide parameters for cluster routing, enter the rtrv-stpopts command.
    Example of the output: 
    
RLGHNCXA03W  00-07-23  16:02:34 EST  EAGLE. 31.3.0   STP OPTIONS
-------------------------
MTPT31CTL               1
MTPLT1                yes
MTPLTCTDPCQ             3
MTPLTST             10000
MTPXLQ                500
MTPXLET              0100
MTPXLOT               90%
MTPDPCQ              2000
TFATFRPR             1000
MTPRSI                yes
MTPRSIT              5000
    The mtpxlq parameter is the total number of dynamic status exception list (x-list) entries the EAGLE 5 ISS maintains. There are 2500 total table entries. The default values allow for 2000 entries for provisioned destinations and 500 for x-list entries. (If you increase the number of x-list entries, you must decrease the number of DPCs that can be provisioned by changing the mtpdpcq parameter.) The mtpxlet parameter is the maximum amount of time the EAGLE 5 ISS maintains an unreferenced x-list entry.
  2. Use the chg-stpopts to change the number of x-list entries or the x-list expiration timer.
  3. If the problem persists, use the dact-rstst command to eliminate specific x-list entries.

3.2.277 0339 - X-LIST space full condition abated

This message indicates the total number of dynamic status exception list (x-list) entries no longer exceeds the maximum allowed.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0339      XLIST               X-LIST space full condition abated

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.278 0340 - RCVRY-MTPLP-RST: Circ rte Status Cleared

The system automatically tests for circular routing when congestion occurs on an ANSI signaling link. This message indicates that the circular routing has been cleared.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0340    DPC 001-001-001     RCVRY-MTPLP-RST: Circ rte status cleared
             XMIT LSN=A1234567
             RCV LSN=ls14 
             MEMBER=011-210-007

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.279 0341 - OAP Unavailable

This message indicates that the EAGLE 5 ISS system is unable to communicate with the OAP or the OAP has an internal failure.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0341  **  OAP B       OAP Unavailable

Alarm Level: Major

Recovery

  1. Enter the command to determine the status of the OAP(s):
    rept-stat-seas
    Example of the output: 
    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = ** 0358 LSMS Q.3 association unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
Command Completed.
    Refer to the Commands Manual to interpret the output.

    Note:

    If the OAP has an internal failure, yet it can still communicate with the system, the state for the OAP appears in the output as OOS-MT/Fault instead of OOS-MT/Isolated. For instance, if the OAP has a hard disk failure the state would appear as OOS-MT/Fault. If the hard disk is full, it will not communicate.
  2. If the OAP has a hard disk failure or the hard disk is full, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  3. If the OAP(s) are out-of-service, check the physical connections.
    See the Installation Manual for more information about these system components.
  4. Check for any fuse alarms on the Fuse and Alarm Panel in the OAP frame.
    There are two 7.5 amp fuses for each OAP. The fuses for OAP1 are marked “Fuse 1A” and “Fuse 1B”. The fuses for OAP2 are marked “Fuse 2A” and “Fuse 2B”. If there is a fuse alarm, replace the fuses for the OAP that is unavailable. Also, make sure the two 10 amp breakers are not tripped.
  5. Enter the command to verify that the SEAS ports are functioning:
    rept-stat-trm
    Example of the output: 
    RLGHNCXA03W 00-02-07 09:50:17 EST  EAGLE 35.0.0
TRM  PST            SST           AST
1     IS-NR          Active        -----
2     IS-NR          Active        -----
3     IS-NR          Active        -----
4     OOS-MT-DSBLD   MANUAL        -----
5     IS-NR          Active        -----
6     IS-NR          Active        -----
7     IS-NR          Active        -----
8     IS-NR          Active        -----
9     IS-NR          Active        -----
10    IS-NR          Active        -----
11    IS-NR          Active        -----
12    IS-NR          Active        -----
13    OOS-MT-DSBLD   MANUAL        -----
14    OOS-MT-DSBLD   MANUAL        -----
15    OOS-MT-DSBLD   MANUAL        -----
16    OOS-MT-DSBLD   MANUAL        -----
Command Completed.
    Use the output from uam-and-uim-troubleshooting-procedures1.html (TRM) to identify the OAP ports. Refer to the Commands Manual to interpret the output.
  6. If a SEAS port is OOS-MT-DSBLD, enable the port with this command:
    rst-trm:trm=x

    where x is the OAP port number. If this action corrects the problem, you are done with this procedure.

  7. If the problem persists, verify that the OAP cables are connected to the correct SEAS TDM port(s).
  8. If the problem persists, verify that the OAP cables are connected to the correct OAP serial ports.
  9. Verify the RS-232 parameters are configured properly for the SEAS port by entering the rtrv-trm command for the specified port.
    The port should be configured to 19200 baud, even parity, one stop bit, and hardware flow control.
  10. If the problem still persists, reset the OAP by entering the init-oap command.
    The OAP comes back in-service within five minutes and the system clears the alarm.
  11. If the problem is still not corrected, reseat the TDM card.
    If the OAP still does not respond, replace the TDM card. Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  12. If the OAP is still not available, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.280 0342 - SEAS UAL Unavailable

This message indicates the SEAS User Application Layer (UAL) process on the OAP is not running. Layer 4 (UPL) is not available for the specified OAP.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0342  **  SEAS OAP B       SEAS UAL unavailable

Alarm Level: Major

Recovery

  1. The UAL should recover automatically by restarting.
  2. Enter this command to verify the status of the OAP(s):
    rept-stat-seas
    Example of the output: 
    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0342 SEAS UAL unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = ** 0358 LSMS Q.3 association unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
Command Completed.
    Refer to the Commands Manual to interpret the output.
  3. If the UAL does not recover, contact the SEAC to test from their equipment to the local synchronous modem.
    Make sure the X.25 link is activated at their end and the link tests within specifications. If possible, have the SEAC or PDN swap X.25 cards at their end with a known good card.
  4. If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.281 0343 - SEAS X.25 Link Unavailable

This message indicates the X.25 link to the specified OAP is down. Layer 2 is not available for the indicated SEAS X.25 link.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0343  **  X25 Link A1         SEAS X.25 Link unavailable

Alarm Level: Major

Recovery

  1. Enter the command to determine the status of the SEAS subsystem:
    rept-stat-seas
    Example of the output: 
    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = ** 0343 SEAS X.25 Link unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
Command Completed.
    Refer to the Commands Manual to interpret the output.
  2. Check the connections from the synchronous modem (in the OAP frame) to the OAP.
    See the Installation Manual for more information about these system components. If the connections are firmly seated, test and if necessary, replace the modem.
  3. Determine the status of the X.25 link by entering the following command:
    rept-stat-seas

    where x is the appropriate TRM number from 1.

    Example of the output: 
    RLGHNCXA03W 00-01-04 15:59:06 EST EAGLE 35.0.0
SEAS COMPONENT             PST           SST         AST
-----------------------------------------------------------
SEAS Interface             IS_ANR        Restricted  ------
TRM            = 2         IS-NR         Active      ------
OAP            = A         IS-NR         Active      ------
X25 port       = A1        IS-NR         Active      ALMINH
PVCs IS-NR     = 1, 3
PVCs OOS-MT    = 2
OAP  GPL       = 022-003-000
ALARM STATUS   = *   0344  PVC unavailable.
Command Completed.
    Refer to the Commands Manual to interpret the output.
  4. If the problem persists, contact the SEAC to test from their equipment to the local synchronous modem.
    Make sure the X.25 link is activated at their end and the link tests within specifications. If possible, have the SEAC or PDN swap X.25 cards at their end with a known good card.
  5. If the problem still persists, reset the OAP by entering the init-oap command.
    The OAP comes back in-service within three minutes and the system clears the alarm.
  6. Determine the status of the X.25 link by entering the command:
    rept-stat-seas

    where x is the appropriate TRM number from 1.

  7. If the X.25 link is still unavailable, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.282 0344 - SEAS PVC Unavailable

This message indicates that the permanent virtual circuit (PVC) connected to the OAP is not available.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0344  *  SEAS X25 Link A1          SEAS PVC unavailable

Alarm Level: Minor

Recovery

  1. Enter the command to determine the status of the SEAS subsystem:
    rept-stat-seas
    Example of the output: 
    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = * 0344 SEAS PVC unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
Command Completed.
    Refer to the Commands Manual to interpret the output.
  2. Determine the status of the OAP and PVC by entering the command:
    rept-stat-seas
    Example of the output: 
    RLGHNCXA03W 00-01-04 15:59:06 EST EAGLE 35.0.0
SEAS COMPONENT             PST           SST         AST
-----------------------------------------------------------
SEAS Interface             IS_ANR        Restricted  ------
TRM            = 2         IS-NR         Active      ------
OAP            = A         IS-NR         Active      ------
X25 port       = A1        IS-NR         Active      ALMINH
PVCs IS-NR     = 1, 3
PVCs OOS-MT    = 2
OAP  GPL       = 022-003-000
ALARM STATUS   = *   0344  PVC unavailable.
Command Completed.
    Refer to the Commands Manual to interpret the output.
  3. If there are any PVCs, the X.25 link physical layer is good.
  4. If the problem persists, contact the SEAC to test from their equipment to the local synchronous modem.
  5. If the PVC is still not available, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.283 0345 - All SEAS UAL Sessions Unavailable

This message indicates the X.25 User Application Layer (UAL) is not available. If all PVCs for the indicated X.25 link have failed, UAL is no longer available, or all UAL sessions are unavailable.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0345  **  SEAS X25 Link B1       All SEAS UAL sessions unavailable

Alarm Level: Major

Recovery

  1. Enter this command to determine the status of the OAP(s):
    rept-stat-seas
    Example of the output: 
    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = ** 0345 All SEAS UAL sessions unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
Command Completed.
  2. Contact the SEAC to verify the X.25 PVCs are correctly configured and activated.
    The SEAC should also deactivate and activate the X.25 link.
  3. If the problem persists, reset the OAP by entering the init-oap command.
    The OAP comes back in-service within three minutes and the system clears the alarm.
  4. If the problem persists, contact the SEAC to test from their equipment to the local synchronous modem.
  5. If the X.25 UAL is still not available, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.284 0346 - SEAS UAL Session Unavailable

This message indicates that the SEAS X.25 link UAL session on one PVC is not available.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0346  *  SEAS X25 Link B1        SEAS UAL session unavailable

Alarm Level: Minor

Recovery

  1. Enter this command to determine the status of the OAP(s):
    rept-stat-seas
    Example of the output: 
    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = * 0346 SEAS UAL session unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
Command Completed.
    Refer to the Commands Manual to interpret the output.
  2. If the problem persists, contact the SEAC to test from their equipment to the local synchronous modem.
  3. If the problem still persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.285 0347 - SEAS X.25 Link is available

This message indicates that a previous problem with the X.25 link has been corrected.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0347    SEAS X.25 Link B1         SEAS X.25 Link is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.286 0348 - SEAS is at Min Service Limit

This message indicates that some part of the SEAS subsystem has failed. When there are two OAPs, this could mean that one OAP has failed, or some part of the path to the SEAC for that OAP has failed. When there is only one OAP with two X.25 links to the SEAC and two connections to the TDM serial ports, either one of the X.25 links has failed, or one of the serial port connections to the TDM has failed. One more failure in either case will cause the SEAS subsystem to fail.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0348  **  SEAS SYSTEM       SEAS is at min service limit

Alarm Level: Major

Recovery

  1. Determine the status of the OAP(s) by entering the following command:
    rept-stat-seas

    Example of the output: 

    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = ** 0348  SEAS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = ** 0358 LSMS Q.3 association unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
    Refer to the Commands Manual to interpret the output.
  2. If 0341 OAP unavailable is displayed, follow recovery procedure 0341 - OAP Unavailable.
  3. If 0343 SEAS X.25
    Link unavailable is displayed, follow recovery procedure 0343 - SEAS X.25 Link Unavailable .
  4. If 0354 OAP TDM Port unavailable is displayed, follow recovery procedure 0354 - One OAP Terminal Unavailable.
  5. If the OAP(s) are out-of-service check the physical connections.
    See the for more information about these system components. If the connections are firmly seated, test and if necessary, replace the modem.
  6. Check for any fuse alarms on the Fuse and Alarm Panel in the OAP frame.
    There are two 7.5 amp fuses for each OAP. The fuses for OAP1 are marked “Fuse 1A” and “Fuse 1B”. The fuses for OAP2 are marked “Fuse 2A” and “Fuse 2B”. If there is a fuse alarm, replace the fuses for the OAP that is unavailable. Also, make sure the two 10 amp breakers are not tripped.
  7. Ensure that the other serial port devices are functioning by entering the following command:
    rept-stat-trm

    Example of the output: 

    RLGHNCXA03W 00-02-07 09:50:17 EST  EAGLE 35.0.0
TRM  PST            SST           AST
1     IS-NR          Active        -----
2     IS-NR          Active        -----
3     IS-NR          Active        -----
4     OOS-MT-DSBLD   MANUAL        -----
5     IS-NR          Active        -----
6     IS-NR          Active        -----
7     IS-NR          Active        -----
8     IS-NR          Active        -----
9     IS-NR          Active        -----
10    IS-NR          Active        -----
11    IS-NR          Active        -----
12    IS-NR          Active        -----
13    OOS-MT-DSBLD   MANUAL        -----
14    OOS-MT-DSBLD   MANUAL        -----
15    OOS-MT-DSBLD   MANUAL        -----
16    OOS-MT-DSBLD   MANUAL        -----
Command Completed.

    Refer to the Commands Manual to interpret the output.

  8. Enable the terminal port with the following command:
    rst-trm:trm=x

    where xis the OAP port number. If this action corrects the problem, you are done with this procedure.

  9. Enter the following command to inhibit the unavailable OAP terminal displayed in the output from 1:
    inh-trm:trm=x
    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  10. If the problem persists, enter the following command to reset the OAP:
    init-oap:oap=x

    where x is the OAP to be initialized. Verify that the OAP comes back in-service within five minutes and the system clears the alarm. If this clears the alarm, continue with 14.

  11. Enter the following command for the inhibited OAP terminal:
    chg-trm:trm=x:type=none

    where x is the port number.

  12. If the problem is still not corrected, reseat the TDM card.
    If the OAP still does not respond, replace the TDM card. Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  13. Enter the following command for each OAP terminal inhibited:
    chg-trm:trm=x:type=oap

    where x is the port number.

  14. Enter the command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number.

  15. If the problem persists, contact the SEAC to test from their equipment to the local synchronous modem.
  16. If the problem is still not corrected, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.287 0349 - SEAS Unavailable

This message indicates the EAGLE 5 ISS system is unable to communicate with the SEAS subsystem.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*C 0100.0349  *C  SEAS SYSTEM         SEAS unavailable

Alarm Level: Critical

Recovery

  1. Enter the following command to determine the status of the OAP(s):
    rept-stat-seas

    Following is an example of the output: 

    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = *C 0349  SEAS unavailable
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = ** 0358 LSMS Q.3 association unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
Command Completed.

    Refer to the Commands Manual to interpret the output.

  2. If the OAP(s) are out-of-service, check the physical connections.
    See the Installation Manual for more information about these system components. If the connections are firmly seated, test and if necessary, replace the modem.
  3. If 0341 OAP unavailable is displayed, follow recovery procedure 0341 - OAP Unavailable.
  4. If 0342 SEAS UAL unavailable is displayed, follow recovery procedure 0342 - SEAS UAL Unavailable.
  5. If 0343 SEAS X.25 Link unavailable is displayed, follow recovery procedure 0343 - SEAS X.25 Link Unavailable.
  6. If 0345 All SEAS UAL sessions unavailable is displayed, follow recovery procedure 0345 - All SEAS UAL Sessions Unavailable.
  7. If 0350 OAP terminals inhibited is displayed, follow recovery procedure 0350 - OAP Terminals Inhibited.
  8. Check for any fuse alarms on the Fuse and Alarm Panel in the OAP frame.
    There are two 7.5 amp fuses for each OAP. The fuses for OAP1 are marked “Fuse 1A” and “Fuse 1B”. The fuses for OAP2 are marked “Fuse 2A” and “Fuse 2B”. If there is a fuse alarm, replace the fuses for the OAP that is unavailable. Also, make sure the two 10 amp breakers are not tripped.
  9. Enter the following command to verify the status of the other serial port devices:
    rept-stat-trm

    Example of the output: 

    RLGHNCXA03W 00-02-07 09:50:17 EST  EAGLE 35.0.0
TRM  PST            SST           AST
1     IS-NR          Active        -----
2     IS-NR          Active        -----
3     IS-NR          Active        -----
4     OOS-MT-DSBLD   MANUAL        -----
5     IS-NR          Active        -----
6     IS-NR          Active        -----
7     IS-NR          Active        -----
8     IS-NR          Active        -----
9     IS-NR          Active        -----
10    IS-NR          Active        -----
11    IS-NR          Active        -----
12    IS-NR          Active        -----
13    OOS-MT-DSBLD   MANUAL        -----
14    OOS-MT-DSBLD   MANUAL        -----
15    OOS-MT-DSBLD   MANUAL        -----
16    OOS-MT-DSBLD   MANUAL        -----
Command Completed.
    Refer to the Commands Manual to interpret the output.
  10. Enable the terminal port with the following command:
    rst-trm:trm=x

    where x is the serial port number. If this action corrects the problem, you are done with this procedure.

  11. Enter the following command to inhibit the unavailable OAP terminal displayed in the output from 1:
    inh-trm:trm=x
    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  12. If the problem persists, enter this command to reset the OAP:
    init-oap:oap=x

    where x is the OAP to be initialized. Verify that the OAP comes back in-service within five minutes and the system clears the alarm. If this clears the alarm, continue with 14.

  13. Enter the following command for the inhibited OAP terminal:
    chg-trm:trm=x:type=none

    where x is the port number.

  14. If the problem is still not corrected, reseat the TDM card.
    If the OAP still does not respond, replace the TDM card. Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
  15. Enter the following command for each OAP terminal inhibited:
    chg-trm:trm=x:type=oap

    where x is the port number.

  16. Enter the following command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number.

  17. If the problem persists, contact the SEAC to test from their equipment to the local X.25 equipment.
  18. If the OAP is still not available, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.288 0350 - OAP Terminals Inhibited

This message indicates that the OAP terminals are inhibited.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST EAGLE 35.0.0
*C 0100.0350  *C  SEAS SYSTEM     OAP terminals inhibited

Alarm Level: Critical

Recovery

  1. Enter the following command to determine which ports are inhibited:
    rept-stat-seas

    Following is an example of the output: 

    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = *C 0350  OAP terminals inhibited
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = ** 0358 LSMS Q.3 association unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
Command Completed.

    Refer to the Commands Manual to interpret the output.

  2. Enter the following command to verify that the other serial port devices are functioning:
    rept-stat-trm

    Following is an example of the output: 

    RLGHNCXA03W 00-02-07 09:50:17 EST  EAGLE 35.0.0
    TRM  PST           SST           AST
    1     IS-NR         Active        -----
    2     IS-NR         Active        -----
    3     IS-NR         Active        ALMINH
    4     IS-NR         Active        -----
    5     OOS-MT-DSBLD  Manual        -----
    6     IS-NR         Active        -----
    7     IS-NR         Active        -----
    8     IS-NR         Active        -----
    9     IS-NR         Active        -----
    10    IS-NR         Active        -----
    11    IS-NR         Active        ALMINH
    12    IS-NR         Active        -----
    13    IS-NR         Active        -----
    14    IS-NR         Active        -----
    15    IS-NR         Active        -----
    16    IS-NR         Active        -----
    Command Completed.

    Refer to the Commands Manual to interpret the output.

  3. If only the SEAS port(s) are not functioning, enable the SEAS port(s) with the following command:
    rst-trm:trm=x

    where x is the OAP port number. If this action corrects the problem, you are done with this procedure.

  4. Enter the following command to inhibit the unavailable OAP terminal displayed in the output from 1:
    inh-trm:trm=x
    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  5. Enter the following command for the inhibited OAP terminal:
    chg-trm:trm=x:type=none

    where x is the port number.

  6. If the problem is still not corrected, reseat the TDM card.
    If the problem persists, replace the TDM card. Refer to the Maintenance Manual for card removal/replacement procedures.
  7. Enter the following command for each OAP terminal inhibited:
    chg-trm:trm=x:type=oap

    where x is the port number.

  8. Enter the following command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number.

3.2.289 0351 - SEAS is Available

This message indicates that a problem with SEAS system has been corrected.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0351    SEAS SYSTEM           SEAS is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.290 0352 - SEAS is Removed

This message indicates that the SEAS feature has been manually removed by removing both SEAS TDM ports.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0352    SEAS SYSTEM           SEAS is removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.291 0353 - OAP is Available

This indicates a previous problem with the OAP has been corrected.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0353    OAP A            OAP is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.292 0354 - One OAP Terminal Unavailable

This message indicates that the OAP terminal specified in the output message is not available.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST EAGLE 35.0.0
** 0100.0354  **  OAP B         One OAP terminal unavailable

Alarm Level: Major

Recovery

  1. Enter the following command to determine which port is unavailable:
    rept-stat-seas

    Following is an example of the output: 

    RLGHNCXA03W 00-04-17 14:59:11 EST  EAGLE 35.0.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
SEAS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
TDM TRM           9                 IS-NR       Active        -----
OAP              A    220-001-000   IS-NR       Active        -----
OAP              B    -----------   OOS-MT      Isolated      -----
X25 Link         A1                 IS-NR       Active        -----
X25 Link         B1                 OS-MT       Fault         -----
SEAS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0354 One OAP terminal unavailable
X25          ALARM STATUS = No Alarms.
X25          ALARM STATUS = ** 0358 LSMS Q.3 association unavailable
X25 A1 PVCs IS-NR   = 1,2,3
X25 A1 PVCs OOS-MT  = ---
X25 B1 PVCs IS-NR   = ---
X25 B1 PVCs OOS-MT  = 1,2,3
Command Completed.

    Refer to the Commands Manual to interpret the output.

  2. Enter the following command to verify that the other ports are functioning:
    rept-stat-trm

    Following is an example of the output: 

    RLGHNCXA03W 00-02-07 09:50:17 EST  EAGLE 35.0.0
TRM  PST            SST           AST
1     IS-NR          Active        -----
2     IS-NR          Active        -----
3     IS-NR          Active        -----
4     OOS-MT-DSBLD   MANUAL        -----
5     IS-NR          Active        -----
6     IS-NR          Active        -----
7     IS-NR          Active        -----
8     IS-NR          Active        -----
9     IS-NR          Active        -----
10    IS-NR          Active        -----
11    IS-NR          Active        -----
12    IS-NR          Active        -----
13    OOS-MT-DSBLD   MANUAL        -----
14    OOS-MT-DSBLD   MANUAL        -----
15    OOS-MT-DSBLD   MANUAL        -----
16    OOS-MT-DSBLD   MANUAL        -----
Command Completed.

    Refer to the Commands Manual to interpret the output.

  3. Enable the terminal port with the following command:
    rst-trm:trm=x

    where x is the serial port number. If this action corrects the problem, you are done with this procedure.

  4. Check the physical connections between the OAP and the system.
    Make sure the connectors are firmly seated. If this action corrects the problem, you are done with this procedure.
  5. Enter the following command to inhibit the unavailable OAP terminal displayed in the output from 1:
    inh-trm:trm=x
    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  6. If the problem persists, enter the following command to reset the OAP:
    init-oap:oap=x

    where x is the OAP to be initialized. Verify that the OAP comes back in-service within five minutes and the system clears the alarm. If this clears the alarm, continue with 10.

  7. Enter the following command for the inhibited OAP terminal:
    chg-trm:trm=x:type=none

    where x is the port number.

  8. If the problem is still not corrected, reseat the TDM card.
    If the OAP still does not respond, replace the TDM card. Refer to the Maintenance Manual for card removal/replacement procedures.
  9. Enter the following command for each OAP terminal inhibited:
    chg-trm:trm=x:type=oap

    where x is the port number.

  10. Enter the following command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number.

  11. If the problem is still not corrected, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.293 0355 - LSMS is Available

All communication paths are complete to the LSMS.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0355     LSMS SYSTEM         LSMS is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous condition has been corrected.

No further action is necessary.

3.2.294 0356 - LSMS is Unavailable

There are no communication paths available to the LSMS. This condition is reached when all OAP terminals are manually inhibited or all LSMS associations are down.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
*C 0014.0356  *C   LSMS SYSTEM        LSMS is unavailable

Alarm Level: Critical

Recovery

  1. Enter the command to verify the status of the terminals:
    rept-stat-trm

    Example of the output: 

    RLGHNCXA03W 00-02-07 09:50:17 EST  EAGLE 35.0.0
TRM  PST            SST           AST
1     IS-NR          Active        -----
2     IS-NR          Active        -----
3     IS-NR          Active        -----
4     OOS-MT-DSBLD   MANUAL        -----
5     IS-NR          Active        -----
6     IS-NR          Active        -----
7     IS-NR          Active        -----
8     IS-NR          Active        -----
9     IS-NR          Active        -----
10    IS-NR          Active        -----
11    IS-NR          Active        -----
12    IS-NR          Active        -----
13    OOS-MT-DSBLD   MANUAL        -----
14    OOS-MT-DSBLD   MANUAL        -----
15    OOS-MT-DSBLD   MANUAL        -----
16    OOS-MT-DSBLD   MANUAL        -----
Command Completed.

    Refer to the Commands Manual to interpret the output.

  2. Enable the terminal port with the following command:
    alw-trm:trm=x

    where x is the serial port number. If this action corrects the problem, you are done with this procedure.

  3. Check the physical connections between the OAP and the LSMS.
    Make sure the connectors are firmly seated.
  4. Check the physical connections between the OAP and the system.
    Make sure the connectors are firmly seated.
  5. Enter the command to verify the status of the LSMS:
    rept-stat-lsms

    Sample output: 

    RLGHNCXA03W 00-04-17 14:59:11 EST  Release 31.3.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
LSMS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
OAP              A    220-001-000   OOS-MT      Isolated      -----
OAP              B    -----------   OOS-MT      Isolated      -----
Q.3 Assoc        A1                 IS-NR       Active        -----
Q.3 Assoc        B1                 OS-MT       Fault         -----
LSMS SYSTEM  ALARM STATUS = *C 0356  LSMS is unavailable
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
Q.3 Assoc A1 ALARM STATUS = No Alarms.
Q.3 Assoc B1 ALARM STATUS = ** 0358 LSMS Q.3 association unavailable
Command Completed.

    Refer to the Commands Manual to interpret the output.

  6. If the problem still persists, reset the OAP by entering the command:
    init-oap:oap=x

    where x is a, b, or both. See the Commands Manual for the correct usage. This procedure is complete if the OAP comes back in-service within five minutes and the system clears the alarm.

  7. Enter the command to verify the status of the LSMS:
    rept-stat-lsms

    Refer to 5 for a sample output.

  8. Enter the command to inhibit the unavailable OAP terminal displayed in the output from 1:
    inh-trm:trm=x
    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  9. Enter the command for the inhibited OAP terminal:
    chg-trm:trm=x:type=none

    where x is the port number.

  10. If the problem is still not corrected, reseat the TDM card.
    If the OAP still does not respond, replace the TDM card. Refer to the Maintenance Manual for card removal/replacement procedures.
  11. Enter the command for each OAP terminal inhibited:
    chg-trm:trm=x:type=oap

    where x is the port number.

  12. Enter this command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number.

  13. Enter the command to verify the status of the LSMS:
    rept-stat-lsms

    Refer to 5 for a sample output.

  14. If the LSMS is still not available, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.295 0357 - All OAP Terminals are Removed

The OAP terminals have been modified to another type using the chg-trm command.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0357   LSMS SYSTEM           All OAP terminals are removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.296 0358 - LSMS Connection Unavailable

An LSMS connection is not available.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
** 0014.0358  **  LSMS  Q.3 Assoc. A1    LSMS connection unavailable

Alarm Level: Major

Recovery

  1. Check the physical connections between the OAP and the LSMS.
    Make sure the connectors are firmly seated.
  2. Enter the following command to verify the status of the LSMS:
    rept-stat-lsms

    A sample output follows: 

    RLGHNCXA03W 00-04-17 14:59:11 EST  Release 31.3.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
LSMS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
OAP              A    220-001-000   OOS-MT      Isolated      -----
OAP              B    -----------   OOS-MT      Isolated      -----
Q.3 Assoc        A1                 IS-NR       Active        -----
Q.3 Assoc        B1                 OS-MT       Fault         -----
LSMS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
Q.3 Assoc A1 ALARM STATUS = No Alarms.
Q.3 Assoc B1 ALARM STATUS = ** 0358 LSMS connection unavailable
Command Completed.

    Refer to the Commands Manual to interpret the output.

  3. If the problem still persists, reset the OAP by entering the following command:
    init-oap:oap=x

    where x is a, b, or both. See the Commands Manual for the correct usage. This procedure is complete if the OAP comes back in-service within three minutes and the system clears the alarm.

  4. Enter the following command to verify the status of the LSMS:
    rept-stat-lsms

    Refer to 2 for a sample output.

  5. Enter the following command to inhibit the unavailable OAP terminal displayed in the output from 2:
    inh-trm:trm=x
    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  6. Enter the following command for the inhibited OAP terminal:
    chg-trm:trm=x:type=none

    where x is the port number.

  7. If the problem is still not corrected, reseat the TDM card.
    If the OAP still does not respond, replace the TDM card. Refer to the Maintenance Manual for card removal/replacement procedures.
  8. Enter the following command for each OAP terminal inhibited:
    chg-trm:trm=x:type=oap

    where x is the port number.

  9. Enter the following command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number.

  10. Enter the following command to verify the status of the LSMS:
    rept-stat-lsms

    Refer to 2 for a sample output.

  11. If the LSMS connection is still not available, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.297 0359 - LSMS connection available

A LSMS connection is available.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0359  LSMS  Q.3 Assoc. A1     LSMS connection available

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.298 0360 - EMS Agent Unavailable

An EMS agent is not available.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0360  **  OAP B         EMS Agent unavailable

Alarm Level: Major

Recovery

  1. Reset the OAP by entering the following command:
    init-oap:oap=x

    where x is a, b, or both. Refer to the Commands Manual for the correct usage. This procedure is complete if the OAP comes back in-service within five minutes and the system clears the alarm.

  2. Enter the following command to determine the reason for the failure: rept-stat-lsms
    Following is an example of the output: 
    RLGHNCXA03W 00-04-17 14:59:11 EST  Release 31.3.0
                         GPL        PST         SST           AST
---------------------------------------------------------------------
LSMS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
OAP              A    220-001-000   OOS-MT      Isolated      -----
OAP              B    -----------   OOS-MT      Isolated      -----
Q.3 Assoc        A1                 IS-NR       Active        -----
Q.3 Assoc        B1                 OS-MT       Fault         -----
LSMS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0360 EMS Agent unavailable
Q.3 Assoc A1 ALARM STATUS = No Alarms.
Q.3 Assoc B1 ALARM STATUS = ** 0358 LSMS Q.3 association unavailable
Command Completed.
    Refer to the Commands Manual to interpret the output.
  3. Enter the following command to inhibit the unavailable OAP terminal displayed in the output from Step 2:
    inh-trm:trm=x

    where x is the port number.

    Note:

    The force parameter is required for the last OAP terminal inhibited.
  4. Enter the following command for the inhibited OAP terminal:
    chg-trm:trm=x:type=none

    where x is the port number.

  5. If the problem is still not corrected, reseat the TDM card.
    If the OAP still does not respond, replace the TDM card. Refer to the Maintenance Manual for card removal/replacement procedures.
  6. Enter the following command for each OAP terminal inhibited:
    chg-trm:trm=x:type=oap

    where x is the port number.

  7. Enter the following command to return the OAP terminals to the in-service state:
    alw-trm:trm=x

    where x is the port number.

  8. If the EMS agent is still not available, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.299 0361 - EMS Agent Available

An EMS agent is available.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0361         OAP A          EMS Agent available

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.300 0362 - LSMS is at min. Service Limit

Only one communication path is available to the LSMS.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
** 0014.0362  **   LSMS SYSTEM        LSMS is at min. service limit

Alarm Level: Major

Recovery

  1. Enter the following command to determine the reason for the failure:
    rept-stat-lsms

    Following is an example of the output: 

                             GPL        PST         SST           AST
RLGHNCXA03W 00-04-17 14:59:11 EST  Release 31.3.0
---------------------------------------------------------------------
LSMS SYSTEM                         IS-ANR      Restricted    -----
TDM TRM           6                 IS-NR       Active        -----
OAP              A    220-001-000   OOS-MT      Isolated      -----
OAP              B    -----------   OOS-MT      Isolated      -----
Q.3 Assoc        A1                 IS-NR       Active        -----
Q.3 Assoc        B1                 OS-MT       Fault         -----
LSMS SYSTEM  ALARM STATUS = ** 0362  LSMS is at min service limit
OAP A        ALARM STATUS = No Alarms.
OAP B        ALARM STATUS = ** 0341 OAP unavailable
Q.3 Assoc A1 ALARM STATUS = No Alarms.
Q.3 Assoc B1 ALARM STATUS = ** 0358 LSMS Q.3 association unavailable
Command Completed.

    Refer to the Commands Manual to interpret the output.

  2. If 0341 OAP unavailable is displayed, follow recovery procedure 0341 - OAP Unavailable.
  3. If 0358 LSMS Q.3 association unavailable is displayed, follow recovery procedure 0358 - LSMS Connection Unavailable.
  4. If 0354 OAP TDM Port unavailable is displayed, follow recovery procedure 0354 - One OAP Terminal Unavailable.
  5. If the problem is not solved, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.301 0363 - OAP Filesystem Full

One of the OAP file systems has exceeded a 95% threshold.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0363  * OAP A   OAP filesystem full.

Alarm Level: Minor

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.302 0364 - Config. Data Checksum Mismatch

This indicates the OAP configuration data does not match the OAP configuration data stored in the system database. There is a mismatch between the system and OAP databases.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST EAGLE 35.0.0
* 0014.0364  * OAP A   Config. Data checksum mismatch

Alarm Level: Minor

Recovery

  1. Enter the following command to retrieve the OAP configuration data stored in the system:
    rtrv-oap-config

    The output of the rtrv-oap-config command displays different fields depending on whether the SEAS feature is on, the LNP feature is on, or both features are on. The following output example shows both the SEAS and LNP features on. 

    rtrv-oap-config
    RLGHNCXA03W 99-01-07 00:57:31 EST EAGLE 35.0.0
    OAP CONFIGURATION REPORT
DATA               OAP A                  OAP B
Hostname           tekelec-8              tekelec-9
IP Address         128.132.064.015        128.132.064.016
IP Netmask         <Not Configured>       <Not Configured>
Default Router     <Not Configured>       <Not Configured>
Config             dual                   dual
SEAC CLLI          SEASNJPYRRC            SEASNJPYRRC
X25 Packet Size    7                      7
X25 Mode           DTE                    DTE
Active LSMS        shadow                 shadow
Main LSMS NSAP     198.089.039.022        198.089.039.022
Main LSMS SSEL     emss                   emss
Main LSMS PSEL     emsp                   emsp
Shadow LSMS NSAP   198.089.039.023        198.089.039.023
Shadow LSMS SSEL   emss                   emss
Shadow LSMS PSEL   emsp                   emsp
  2. Review the retrieved information, looking for errors or unprovisioned parameters.
    Table 3-4 lists OAP configuration parameters from the above output that must be provisioned if a given feature is on.

    Table 3-4 OAP Configuration Parameters

    Output Legend Feature
    Hostname Host name of OAP A or OAP B LNP or SEAS
    IP Address IP address of OAP A or OAP B LNP
    IP Netmask The netmask for OAP A or OAP B Not required
    Default Router The IP address of the default router assigned to OAP A or OAP B Not required
    Config The number of OAPs configured (single or dual) LNP or SEAS
    SEAC CLLI The common language location identifier (CLLI) of the SEAC to which the OAP connects. SEAS
    X25 Packet Size The X.25 package size for the link to the SEAC (7 or 8) SEAS
    X25 Mode The mode of the X.25 link to the SEAC (DTE or DTC) SEAS
    Active LSMS The LSMS associated with the OAP (main or shadow) LNP
    Main LSMS NSAP

    The network service access point of the main LSMS

    (If lsms=shadow, this parameter set is not mandatory.)

    		LNP
    Main LSMS SSEL

    The session selector of the main LSMS

    (If lsms=shadow, this parameter set is not mandatory.)

    		LNP
    Main LSMS PSEL

    The presentation selector of the main LSMS

    (If lsms=shadow, this parameter set is not mandatory.)

    		LNP
    Shadow LSMS NSAP

    The network service access point of the shadow LSMS

    (If lsms=main, this parameter set is not mandatory.)

    		LNP
    Shadow LSMS SSEL

    The session selector of the shadow LSMS

    (If lsms=main, this parameter set is not mandatory.)

    		LNP
    Shadow LSMS PSEL

    The presentation selector of the shadow LSMS

    (If lsms=main, this parameter set is not mandatory.)

    		LNP

    Note:

    If you find no errors or provision omissions, go to 4. If you find errors or provision omissions, contact your IS department to obtain the correct values and contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  3. Enter the following command to update the OAP database:
    act-oap-config
  4. If the fault does not clear, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.303 0365 - Config. Data checksum alarm cleared

This indicates that the system databases once out of sync are now back in sync.

Example 
RLGHNCXA21W 94-02-07 12:01:43 EST  EAGLE 35.0.0 
0014.0365   OAP A   Config. Data checksum alarm cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.304 0366 - Temp Key(s) Expiration Alarm Cleared

This message indicates that there are no temporary keys currently in the expired state, and the alarm condition, specified by message “0368 - Temp Key(s) have expired,” has been cleared.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 5.0.0-32.0.0
0100.0366    SYSTEM     Temp Key(s) expiration alarm cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

Note:

Further access to this controlled feature requires the purchase of a permanent key.

3.2.305 0367 - Temp Key(s) Expiring Soon

This alarm indicates that one or more temporary keys used to enable a controlled feature will expire within the next seven days.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 5.0.0-32.0.0
** 0100.0367    SYSTEM     Temp Key(s) expiring soon

Alarm Level: Major

Recovery

  1. Enter the following command to retrieve information about controlled features: rtrv-ctrl-feat:enable=temp
    The output of the rtrv-ctrl-feat:enable=temp command displays information about the number of days left for temporarily enabled features.
    Following is an example of the output: 
    The following features have been temporarily enabled:
RLGHNCXA03W 99-01-07 00:57:31 EST EAGLE 5.0.0-32.0.0
Feature Name              Partnum    Status  Quantity     Trial Period Left
TPS 893000140 on 4000 6 days 5 hrs 3 mins
  2. If you do nothing within the remaining trial period, the critical alarm, “0368 - Temp Key(s) have expired” will display when the trial period expires.
  3. If you wish to acquire this feature permanently, you can purchase it from Tekelec.
    The alarm will be cleared when the purchased feature is enabled using the enable-ctrl-feat command.

3.2.306 0368 - Temp Key(s) have expired

This alarm indicates that one or more temporary keys used to enable a controlled feature have expired.

Example 
   RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 5.0.0-32.0.0
*C 0100.0368    SYSTEM     Temp Key(s) have expired

Alarm Level: Critical

Recovery

  1. Enter the following command to retrieve information about controlled features: rtrv-ctrl-feat:expired=yes
    The output of the rtrv-ctrl-feat:expired=yes command displays information about expired temporarily enabled features.
    Following is an example of the output: 
    
RLGHNCXA03W 99-01-07 00:57:31 EST EAGLE 5.0.0-32.0.0
The following features have expired temporary keys:
Feature Name              Part Num
TPS 8930000140
  2. You can enter the chg-ctrl-feat:partnum=893xxxxxx:alarm=clear command to clear this alarm.
  3. If you wish to acquire this feature permanently, you can purchase it from Tekelec and enable it using the enable-ctrl-feat command.
    The alarm will clear when the purchased feature is installed with a permanent key.

3.2.307 0369 - REPT-T1F:FAC-T1 unavailable

There is a problem at the far end and the far end is not communicating with the EAGLE 5 ISS.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0369 ** T1/J1PORT 1201,2     REPT-T1F:FAC-T1 unavailable

Alarm Level: Major

Recovery

  1. Contact the far-end office to determine the cause and to correct the problem.

3.2.308 0370 - Critical Platform Failure(s)

This message indicates the application running in the MPS server has detected a critical platform failure. The Alarm Data in the message contains a 16-character hexadecimal string in the format of h’1xxxxxxxxxxxxxxx’. This alarm will be reset when UAM #250, MPS Available is issued.

Example 
station1234 00-09-30 16:28:08 EST EAGLE 35.0.0
*C 0259.0370 *C MPS B                Critical Platform Failure(s)
                ALARM DATA = h'1000000000000008'

Alarm Level: Critical

Recovery

  1. To decode the ALARM DATA included in this alarm, write down the Alarm Data string.
  2. To decode the alarm and for the correct procedure to solve the problem, refer to the MPS Platform Software and Maintenance Manual.
  3. This alarm will be reset when the problem is resolved and you receive UIM #250 MPS Available.

3.2.309 0371 - Critical Application Failure(s)

This message indicates the application running in the MPS server has detected a critical application failure. The Alarm Data in the message contains a 16-character hexadecimal string in the format of h’2xxxxxxxxxxxxxxx’. This alarm will be reset when UAM #250, MPS Available is issued.

Example 
station1234 00-09-30 16:28:08 EST EAGLE 35.0.0
*C 0259.0371 *C MPS B                Critical Application Failure(s)
               ALARM DATA = h'2000000000000001'

Alarm Level: Critical

Recovery

  1. To decode the ALARMDATA included in this alarm, write down the Alarm Data string.
  2. To decode the alarm and for the correct procedure to solve the problem, refer to the MPS Platform Software and Maintenance Manual.
  3. This alarm will be reset when the problem is resolved and you receive UIM #250 MPS Available.

3.2.310 0372 - Major Platform Failure(s)

This message indicates the application running in the MPS server has detected a major platform failure. The Alarm Data in the message contains a 16-character hexadecimal string in the format of h’3xxxxxxxxxxxxxxx’. This alarm will be reset when UAM #250, MPS Available is issued.

Example 
station1234 00-09-30 16:28:08 EST EAGLE 35.0.0
** 0259.0372 ** MPS B                Major Platform Failure(s)
                ALARM DATA = h'3000000000000002'

Alarm Level: Major

Recovery

  1. To decode the ALARMDATA included in this alarm, write down the Alarm Data string.
  2. To decode the alarm and for the correct procedure to solve the problem, refer to the MPS Platform Software and Maintenance Manual.
  3. This alarm will be reset when the problem is resolved and you receive UIM #250 MPS Available.

3.2.311 0373 - Major Application Failure(s)

This message indicates the application running in the MPS server has detected a major application failure. The Alarm Data in the message contains a 16-character hexadecimal string in the format of h’4xxxxxxxxxxxxxxx’. This alarm will be reset when UAM #250, MPS Available is issued.

Example 
station1234 00-09-30 16:28:08 EST EAGLE 35.0.0
** 0259.0373 ** MPS B                Major Application Failure(s)
                ALARM DATA = h'4000000000000008'

Alarm Level: Major

Recovery

  1. To decode the Alarm Data included in this alarm, write down the Alarm Data string.
  2. To decode the alarm and for the correct procedure to solve the problem, refer to the MPS Platform Software and Maintenance Manual.
  3. This alarm will be reset when the problem is resolved and you receive UIM #250 MPS Available.

3.2.312 0374 - Minor Platform Failure(s)

This message indicates the application running in the MPS server has detected a minor platform failure. The Alarm Data in the message contains a 16-character hexadecimal string in the format of h’5xxxxxxxxxxxxxxx’. This alarm will be reset when UAM #250, MPS Available is issued.

Example 
station1234 00-09-30 16:28:08 EST EAGLE 35.0.0
*  0259.0374 *  MPS B                Minor Platform Failure(s)
                ALARM DATA = h'5000000000000004'

Alarm Level: Minor

Recovery

  1. To decode the ALARM DATA included in this alarm, write down the Alarm Data string.
  2. To decode the alarm and for the correct procedure to solve the problem, refer to the MPS Platform Software and Maintenance Manual.
  3. This alarm will be reset when the problem is resolved and you receive UIM #250 MPS Available.

3.2.313 0375 - Minor Application Failure(s)

This message indicates the application running in the MPS server has detected a minor application failure. The Alarm Data in the message contains a 16-character hexadecimal string in the format of h’6xxxxxxxxxxxxxxx’. This alarm will be reset when UAM #250, MPS Available is issued.

Example 
station1234 00-09-30 16:28:08 EST EAGLE 35.0.0
*  0259.0375 *  MPS B                Minor Application Failure(s)
                ALARM DATA = h'6000000000000001'

Alarm Level: Minor

Recovery

  1. To decode the Alarm Data included in this alarm, write down the Alarm Data string.
  2. To decode the alarm and for the correct procedure to solve the problem, refer to the MPS Platform Software and Maintenance Manual.
  3. This alarm will be reset when the problem is resolved and you receive UIM #250 MPS Available.

3.2.314 0376 - REPT-T1F:FAC-T1 LOS Failure

No signal is being received on the T1 Port.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0376 ** T1PORT 1201,2   REPT-T1F:FAC-T1 LOS failure

Alarm Level: Major

Recovery

Check the physical connections.

3.2.315 0377 - REPT-T1F:FAC-T1 LOF failure

The 7-bit frame alignment signal does not match the pattern the EAGLE 5 ISS is expecting.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0377 ** T1PORT 1201,2   REPT-T1F:FAC-T1 LOF failure

Alarm Level: Major

Recovery

Contact the far-end office to correct their framing problem.

3.2.316 0378 - REPT-T1F:FAC-T1 Remote Alarm

This indicates there is some type of failure on the far end.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0378 ** T1PORT 1201,2   REPT-T1F:FAC-T1 Remote Alarm

Alarm Level: Major

Recovery

Contact the far-end office to determine the cause and correct the problem.

3.2.317 0379 - REPT-T1F:FAC-T1 Alarm

The far end is transmitting an alarm indication signal (AIS) due to an excessive bit error rate, loss of signal, or loss of frame.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0377 ** T1PORT 1201,2   REPT-T1F:FAC-T1 Alarm

Alarm Level: Major

Recovery

Contact the far-end office to determine the cause of the AIS and to correct the problem.

3.2.318 0380 - RCVRY-T1F:FAC-T1 Available

The T1 port 1 is back in-service.

Example 
RLGHNCXA21W 00-11-07 11:02:30 EST  EAGLE 35.0.0
0014.0380    T1PORT  1201,2   RCVRY-T1F:FAC-T1 available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.319 0381 - REPT-E1F:FAC-E1 LOS failure

No signal is being received on the signaling link.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0381 ** E1PORT 1201,2   REPT-E1F:FAC-E1 LOS failure

Alarm Level: Major

Recovery

Check the physical connections.

3.2.320 0382 - REPT-E1F:FAC-E1 LOF failure

The 7-bit frame alignment signal does not match the pattern the EAGLE 5 ISS is expecting.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0382 ** E1PORT 1201,2   REPT-E1F:FAC-E1 LOF failure

Alarm Level: Major

Recovery

Contact the far-end office to correct their framing problem.

3.2.321 0383 - REPT-E1F:FAC-E1 AIS detected

The far end is transmitting an alarm indication signal (AIS) due to an excessive bit error rate, loss of signal, or loss of frame.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0383 ** E1PORT 1201,2   REPT-E1F:FAC-E1 AIS detected

Alarm Level: Major

Recovery

Contact the far-end office to determine the cause of the AIS and to correct the problem.

3.2.322 0384 - REPT-E1F:FAC-E1 Far End Failure

This indicates there is some type of failure on the far end.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0384 ** E1PORT 1201,2   REPT-E1F:FAC-E1 Far End Failure

Alarm Level: Major

Recovery

Contact the far-end office to determine the cause and to correct the problem.

3.2.323 0385 - REPT-E1F:FAC-E1 10E-3 BER failed

A framing bit error rate is maintained for in-service links because the error rate is high.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0385 ** E1PORT 1201,2   REPT-E1F:FAC-E1 10E-3 BER failed

Alarm Level: Major

Recovery

Contact the far-end office to determine the cause of the high framing bit error rate.

3.2.324 0386 - RCVRY-E1F:FAC-E1 Available

The E1 port 1 is back in-service.

Example 
RLGHNCXA21W 00-11-07 11:02:30 EST  EAGLE 35.0.0
0014.0386    E1PORT  1201,2   RCVRY-E1F:FAC-E1 available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.325 0387- REPT-E1F:FAC-E1 unavailable

There is a problem at the far end and the far end is not communicating with the EAGLE 5 ISS.

Example 
   RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0387 ** E1PORT 1201,2     REPT-E1F:FAC-E1 unavailable

Alarm Level: Major

Recovery

Contact the far-end office to determine the cause and to correct the problem.

3.2.326 0388 - Illegal Address Error has Cleared

This message indicates the clearing of a prior illegal address error. Previously, the HMUX-assigned shelf ID address received from OAM did not match the value read from the Assigned Shelf Address Register, resulting in major alarm UAM #0390. This message shows the previous alarm has cleared.

Example 
station1234 00-11-30 16:28:08 EST  EAGLE 35.0.0
0012.0388        CARD 1109 HMUX    Illegal Address Error has Cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault, which was indicated by UAM #0390, has been corrected.

No further action is necessary.

3.2.327 0389 - Card Responding Normally

This message indicates the clearing of a prior card problem.

Example 
0014.0389 CARD 1201 Card Responding Normally

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.328 0390 - Illegal Address Error

This message indicates an HMUX (High Speed Multiplexer) illegal address error. The ATH (Application Trouble Handler) displays this alarm when an HMUX-assigned shelf ID address, which was received from OAM and written to the Assigned Shelf Address Register, did not match the value read from the Assigned Shelf Address Register. Furthermore, the error was not corrected after an automatic attempt to correct the address discrepancy.

Example 
station1234 00-11-30 16:28:08 EST  EAGLE 35.0.0
** 0012.0390  **  CARD 1109 HMUX Illegal Address Error

Alarm Level: Major

Recovery

  1. Reset the HMUX card in question by entering the command:
    init-mux:loc=xy09 (or loc=xy10)

    This command resets the card, but it does not take down the IMT bus on which the card resides; operation of the bus is unaffected by this command.

  2. If the problem persists, then you should reseat the HMUX card in question.
    Remember that this action will take down the IMT bus of the HMUX card.
  3. If the problem remains, the card must be replaced.
    Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.329 0391 - Card Not Responding Error

This message indicates an HMUX (High Speed Multiplexer)/HIPR (High-Speed IMT Packet Router) is not responding. This alarm is displayed when an HMUX/HIPR in a provisioned shelf card does not respond.

Example 
station1234 00-11-30 16:28:08 EST  EAGLE 35.0.0
** 0012.0391 **  CARD 1109 HIPR Card not responding Error

Alarm Level: Major

Recovery

  1. Reset the HMUX/HIPR card in question by entering the command:
    init-mux:loc=xy09 (or loc=xy10)

    This command resets the card, but it does not take down the IMT bus on which the card resides; operation of the bus is unaffected by this command.

  2. If the problem persists, then you should reseat the HMUX/HIPR card in question.
    Remember that this action will take down the IMT bus of the HMUX/HIPR card.
  3. If the problem remains, the card must be replaced.
    Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.330 0392 - OA&M IP Security Feature is OFF

The Eagle OA&M IP Security Enhancements Feature is not turned on. One of the following occurred: and OAM init, or OAM role change, or the chg-ctrl-feat command turned the feature off.

With this feature not operating, you do not have the tools to securely pass data across an otherwise non-secure network. Until the Eagle OA&M IP Security Enhancements Feature is restored, the Eagle cannot provide secure connections from approved clients, and does not protect sensitive passwords and information while in transit between the Eagle and a host.

Example 
eagle11 17-12-07 09:23:41 EST  EAGLE 46.5.0.0.0-0.0.0
    2001.0392    SECURITY SYSTEM         OA&M IP Security feature status is OFF

Alarm Level: Major

Recovery

To restore the OA&M IP Security Enhancements feature, you turn it on permanently.

To turn the feature on, use the command.

enable-ctrl-feat

3.2.331 0393 - OA&M IP Security feature is ON

The Eagle OA&M IP Security Enhancements Feature is turned on. This UAM is an informational message that confirms that the feature is restored to operational status.

With this feature operating, you have the tools to securely pass data across an otherwise non-secure network. With the Eagle OA&M IP Security Enhancements Feature operational, the Eagle can provide secure connections from approved clients, and protects sensitive passwords and information while in transit between the Eagle and a host.

Example 
RLGHNCXA21W 03-03-03 12:01:43 EST  EAGLE 35.0.0 
0047.0393    SECURITY SYSTEM         OA&M IP Security feature status is ON

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates that the feature previously was OFF and now has been turned ON.

No further action is necessary.

3.2.332 0394 - INP Subsystem is Available

This message indicates that a problem with the INP subsystem has been corrected.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
0056.0394     INP SYSTEM    INP Subsystem is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.333 0395 - INP Subsystem is Not Available

The INP subsystem is not available. There are no IS-NR VSCCP cards associated with this INP subsystem. The INP subsystem was not taken off-line via command.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
*C 0056.0395  *C  INP SYSTEM    INP Subsystem  is not available

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  2. Enter the following command to move the VSCCP cards to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT-DSBLD VSCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  4. Verify the VSCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.334 0396 - INP Subsystem is disabled

The INP subsystem has been manually disabled using the inh-map-ss command.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
*C 0056.0396  *C  INP SYSTEM      INP Subsystem  is disabled

Alarm Level: Critical

Recovery

  1. Enter this command to verify the status and location of the INP subsystem cards:
    rept-stat-mps
  2. Enter this command to to reserve the subsystem number and to change the state of the INP subsystem status to on-line:
    ent-ss-appl:appl=inp:ssn=xx:stat=online

    where xx is primary subsystem number.

  3. Enter this command to change the state of the INP subsystem to on-line:
    alw-map-ss:ssn=xx

    where xx is primary subsystem number.

  4. Enter this command to verify the status of the INP subsystem:
    rept-stat-mps

3.2.335 0397 - INP Subsystem is Removed

The INP subsystem is not fully equipped. There are no VSCCP cards configured with this INP subsystem.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
0056.0397      INP SYSTEM      INP Subsystem  is removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the VSCCP hardware.

Configure the INP system with VSCCP cards. Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.336 0398 - INP Subsystem Normal, Card(s) Abnormal

One or more of the VSCCP cards do not have an ACTIVE status.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
*  0056.0398  *   INP SYSTEM   INP Subsystem normal,card(s) abnormal

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  2. Enter the following command to move the VSCCP card to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT-DSBLDVSCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  4. Verify the VSCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.337 0399 - RCVRY-LKSTO:Alarm clr’d by deleting SLK

A signaling link (SLK) that was out of service and had an outstanding alarm has been deleted from the database. The alarm is cleared.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
0014.0399    LSN a24546   RCVRY-LKSTO:Alarm clr’d by deleting SLK

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.338 0400 - Alarm cleared by deleting card

A card that was out of service and had an outstanding alarm has been deleted from the system database. The alarm is cleared.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
0014.0400    CARD 1202 SCCP      Alarm cleared by deleting card

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous failure has been corrected.

No further action is necessary.

3.2.339 0401 - Alarm cleared by deleting SLK

A signaling link (SLK) that was out of service and had an outstanding alarm has been deleted from the database. The alarm is cleared.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0 
0014.0401    SLK 1205,A SS7ANSI  Alarm cleared by deleting SLK
             SLC=01   FECLLI=A1234567890

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.340 0402 - Alarm cleared by deleting route

A route that was out of service and had an outstanding alarm has been deleted from the database. The alarm is cleared.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.0402    DPC 001-001-001     Alarm cleared by deleting route

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.341 0403 - 1114 E1/T1 Clock Requires TDM-GTI

This message indicates that the high speed clock is provisioned as T1 framed, E1 framed, or E1 unframed. A non TDM-GTI card has been placed in this system where recovered clocks are provisioned. The TDM-GTI version of the TDM card is required.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 35.0.0 
** 0052.0403 ** HS CLOCK SYSTEM  1114 E1/T1 clock requires TDM-GTI

Alarm Level: Major

Recovery

Perform one of the following:
  • Replace the card in location 1114 with a TDM-GTI card. Refer to the Maintenance Manual for card removal/replacement procedures for the replacement procedure.

    OR

  • Use the chg-clkoptschg-stpopts command to change the hsclksrc parameter to RS422. Refer to the Commands Manual for proper usage of the command.

3.2.342 0404 - 1116 E1/T1 Clock Requires TDM-GTI

This message indicates the high speed clock is provisioned as T1 framed, E1 framed, or E1 unframed. A non TDM-GTI card has been placed in this system where recovered clocks are provisioned. The TDM-GTI version of the TDM card is required.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 35.0.0
** 0052.0404 ** HS CLOCK SYSTEM  1116 E1/T1 clock requires TDM-GTI

Alarm Level: Major

Recovery

Perform one of the following:
  • Replace the card in location 1116 with a TDM-GTI card. Refer to the Maintenance Manual for card removal/replacement procedures for the replacement procedure.

    OR

  • Use the chg-clkoptschg-stpopts command to change the HSCLKSRC parameter to RS422. Refer to the Commands Manual for proper usage of the command.

3.2.343 0405 - 1114, 1116 E1/T1 Clock Requires TDM-GTI

This message indicates that the high speed clock is provisioned as T1 framed, E1 framed, or E1 unframed. A non TDM-GTI card has been placed in this system in slots 1114 and 1116 where recovered clocks are provisioned. The TDM-GTI version of the TDM card is required.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 35.0.0
** 0052.0405 ** HS CLOCK SYSTEM  1114, 1116 E1/T1 clock requires TDM-GTI

Alarm Level: Major

Recovery

Perform one of the following:
  • Replace the cards in locations 1114 and 1116 with a TDM-GTI card. Refer to the Maintenance Manual for card removal/replacement procedures for the replacement procedure.

    OR

  • Use the chg-clkoptschg-stpopts command to change the HSCLKSRC parameter to RS422. Refer to the Commands Manual for proper usage of the command.

3.2.344 0406 - 1114 Clock selection mismatch

This message indicates that the database has been restored and the provisioned clocks do not match what is running on the TDM.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0406 ** HS CLOCK SYSTEM  1114 Clock selection mismatch

Alarm Level: Major

Recovery

  1. Enter the following command to determine the current clock settings on the TDM:
    rept-stat-clk
    Following is an example of the output: 
        rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Use the chg-clkoptschg-stpopts command to update the database to match the output displayed when you issued the previous command.
    Refer to the Commands Manual for proper usage of the command.

3.2.345 0407 - 1116 Clock selection mismatch

This message indicates that the database has been restored and the provisioned clocks do not match what is running on the TDM.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0407 ** HS CLOCK SYSTEM  1116 Clock selection mismatch

Alarm Level: Major

Recovery

  1. Enter the following command to determine the current clock settings on the TDM:
    rept-stat-clk
    Following is an example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Use the chg-clkoptschg-stpopts command to update the database to match the output displayed when you issued the previous command.
    Refer to the Commands Manual for proper usage of the command.

3.2.346 0408 - 1114, 1116 Clock selection mismatch

This message indicates that the database has been restored and the provisioned clocks do not match what is running on the TDM.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
** 0052.0408 ** HS CLOCK SYSTEM  1114, 1116 Clock selection mismatch

Alarm Level: Major

Recovery

  1. Enter the following command to determine the current clock settings on the TDM:
    rept-stat-clk
    Following is an example of the output: 
    rept-stat-clk
    Command entered at terminal #3.
;
    tekelecstp 99-03-05 13:34:15 EST EAGLE 31.6.0
    CARD LOC= 1114 (Active   )       CARD LOC= 1116 (Isolated )
    PRIMARY BITS      = Active        PRIMARY BITS      = -----
    SECONDARY BITS    = Idle          SECONDARY BITS    = -----
    HS PRIMARY CLK    = Active        HS PRIMARY CLK    = -----
    HS SECONDARY CLK  = Idle          HS SECONDARY CLK  = -----
    HS CLK TYPE       = E1 UNFRAMED   HS CLK TYPE       = -----
    HS CLK LINELEN    = SHORTHAUL     HS CLK LINELEN    = -----
                                     PST           SST       AST
    SYSTEM CLOCK                     IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using CLK A = 009        # Cards with bad CLK A = 000
    # Cards using CLK B = 000        # Cards with bad CLK B = 009
    # Cards using CLK I = 000
                                     PST           SST       AST
    HS SYSTEM CLOCK                  IS-NR         ACTIVE    ALMINH 
    ALARM STATUS     = No Alarms. 
    # Cards using HSCLK A = 001      # Cards with bad HSCLK A = 000
    # Cards using HSCLK B = 000      # Cards with bad HSCLK B = 002
    # Cards using HSCLK I = 000
    Command Completed.
  2. Use the chg-clkoptschg-stpopts command to update the database to match the output displayed when you issued the previous command.
    Refer to the Commands Manual for proper usage of the command.

3.2.347 0409 - Clock configuration corrected

This message indicates that a problem with the high speed clock configuration database has been corrected.

Example 
station1234 99-03-05 16:28:08 EST  EAGLE 31.6.0 
0052.0409    HS CLOCK SYSTEM      Clock configuration corrected

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.348 0422 - Insufficient Extended Memory

At least one SCCP card does not have enough memory for the LNP application. Loading of the SCCP card is automatically inhibited.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0422 ** CARD  1113 SCCP  Insufficient extended memory
                HW VERIFICATION CODE: xxx

Alarm Level: Major

Recovery

  1. If this message contains the optional line ‘HW VERIFICATION CODE: xxx’:
    1. Decode the xxx value and correct the indicated problem.
      See the Hardware Verification Codes in UAMs section on hardware verification codes in the Unsolicited Alarms and Information Messages manual.
    2. After correcting the problem, the card will be in out-of-service maintenance disabled state (OOS-MT-DSBLD).
      Restore the card back to in-service normal state (IS-NR) with the alw-card command. If this message does not contain the optional line ‘HW VERIFICATION CODE: xxx’, continue with the next step.
  2. Verify the SCCP hardware.
    Verify the SCCP cards have at least 256M of memory.
  3. If necessary, replace the SCCP card with the correct combination of motherboard and daughterboard.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.349 0423 - Card Reload Attempted

Card loading is no longer inhibited. The once inhibited card is now attempting to load.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0423    CARD  1108 SCCP   Card reload attempted

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.350 0424 - LNP Subsystem is Not Available

The LNP subsystem is not available. There are no IS-NR SCCP cards associated with this LNP subsystem. The LNP subsystem was not taken off-line via command.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
*C 0056.0424  *C  LNP SYSTEM      LNP Subsystem  is not available

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-lnp
  2. Enter the following command to move the SCCP cards to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT-DSBLD SCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-lnp
  4. Verify the SCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.351 0425 - LNP Subsystem Normal, Card(s) Abnormal

One or more of the SCCP cards do not have an ACTIVE status.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 46.0.0
*  0056.0425  *    LNP SYSTEM   LNP Subsystem normal, card(s) abnormal

Alarm Level: Minor.

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-lnp
  2. Enter the following command to move the SCCP card to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT-DSBLD SCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-lnp
  4. Verify the SCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to Maintenance Manual for card removal/replacement procedures.

3.2.352 0426 - LNP Subsystem is Available

This message indicates that a problem with LNP system has been corrected.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0056.0426     LNP SYSTEM    LNP Subsystem is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.353 0427 - LNP Subsystem degraded, card(s) abnormal

One or more LNP cards goes out of service in (N or N+1) configuration or not IS-NR.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 46.0.0
**  0056.0427   **    LNP SYSTEM   LNP Subsystem degraded, card(s) abnormal

Alarm Level: Major.

Recovery

  1. Restore the one or more LNP out of service cards in (N or N+1) configuration or not IS-NR.

3.2.354 0428 - INP Subsystem degraded, card(s) abnormal

One or more INP cards goes out of service in (N or N+1) configuration or not IS-NR.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 46.0.0
0056.0428      INP SYSTEM   INP Subsystem degraded, card(s) abnormal

Alarm Level: Major.

Recovery

  1. Restore the one or more INP out of service cards in (N or N+1) configuration or not IS-NR.

3.2.355 0429 - ATINPQ Subsystem degraded, card(s) abnormal

One or more ATINPQ cards goes out of service in (N or N+1) configuration or not IS-NR.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 46.0.0
0056.0429      ATINPQ SYSTEM   ATINPQ Subsystem degraded, card(s) abnormal

Alarm Level: Major.

Recovery

  1. Restore the one or more ATINPQ out of service cards in (N or N+1) configuration or not IS-NR.

3.2.356 0434 - LNP Subsystem is Removed

The LNP subsystem is not fully equipped. There are no SCCP cards configured with this LNP subsystem.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0056.0434      LNP SYSTEM      LNP Subsystem  is removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the SCCP hardware.

Configure the LNP system with SCCP cards. Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.357 0435 - LNP Subsystem is Disabled

The LNP subsystem has been manually disabled using the inh-map-ss command.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
*C 0056.0435  *C  LNP SYSTEM      LNP Subsystem  is disabled

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the LNP subsystem cards:
    rept-stat-lnp
  2. Enter the following command to change the state of the LNP subsystem status to on-line:
    ent-ss-appl:appl=lnp:ssn=xx:stat=online

    where xx is primary subsystem number.

  3. Enter the following command to change the state of the LNP subsystem to on-line:
    alw-map-ss:ssn=xx

    where xx is primary subsystem number.

  4. Enter the following command to verify the status of the LNP subsystem:
    rept-stat-lnp

3.2.358 0436 - LNP ACG node overload

This message indicates that the number of LNP subsystem queries has exceeded the supported level.

Example 
station1234 94-03-30 16:28:08 EST EAGLE 35.0.0
** 0056.0436 ** LNP SYSTEM            LNP ACG node overload

Alarm Level: Major

Recovery

  1. Enter the following command to verify the status, quantity, and capacity of the SCCP cards:
    rept-stat-lnp
  2. Refer to the ELAP Administration and LNP Feature Activation to verify that provisioning rules are being followed.
  3. If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.359 0437 - System SCCP TPS Capacity Exceeded

This message indicates the Eagle has exceeded its TPS (Transactions Per Second) message transport rate. The alarm will not stop until the TPS rate is below its rated TPS for the system for a period of 30 seconds. The alarm is cleared by the UIM #329 “SCCP capacity normal, card(s) abnormal”.

Example 
RLGHNCXA21W 00-11-07 11:02:30 EST  EAGLE 35.0.0
*C 0100.0437 *C SYSTEM           System SCCP TPS Capacity Exceeded

Alarm Level: Critical

Recovery

  1. Use rept-stat-sccp to determine the status of the SCCP subsystem.
    This command also identifies which SCCP cards are OOS-MT. For example, enter:
    rept-stat-sccp
    Example of the output: 
    eaglestp 00-10-24 20:38:58 EST EAGLE 35.0.0
    SCCP SUBSYSTEM REPORT IS-NR          Ovflw-1       -----
    SCCP Cards Configured= 4 Cards       IS-NR= 4
    System TCP Alarm Threshold =  80% Total capacity 
    System Peak SCCP Load =  3000 TPS
    System Total SCCP Capacity =  5000 TPS
    CARD   VERSION     PST        SST         AST      MSU USAGE   CPU USAGE 
    -------------------------------------------------------------------------
    1212   021-001-000 IS-NR      ACTIVE      ALMINH       47%         32%
    -------------------------------------------------------------------------
    SCCP Service Average MSU Capacity = 47%     Average CPU Capacity = 32%
    
    Command Completed.
  2. The user should evaluate this new traffic level and determine whether additional SCCP cards are required to maintain the TPS level the system is processing.

3.2.360 0438 - Degraded Mode, Invalid OAM HW Config

This UAM alarm occurs when the system does not have the required baseline hardware. Baseline hardware required includes TDM-10 or greater. The alarm recurs every minute. Also, the act_upgrade command is rejected if alarm is present.

Example 
RLGHNCXA21W 02-12-07 12:01:43 EST  EAGLE 35.0.0 
*C 0014.0438 *C SECULOG 1114   Degraded Mode, Invalid OAM HW config

Alarm Level: Critical

Recovery

Ensure that the Eagle has the required hardware baseline, that is, the TDM-10 or greater is installed.

3.2.361 0439 - Exiting Degraded Mode

The Degraded Mode due to a invalid OAM hardware configuration has been cleared, and the mode has been exited. The HMUX is restored to its full operating capacity.

Example 
RLGHNCXA21W 02-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0439    SECULOG 1114   Exiting Degraded Mode

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.362 0441 - Incorrect MBD - CPU

An SM card does not have the required hardware configuration for the application.

Example 
eagle11 18-10-30 09:58:56 MST  EAGLE 46.7.0.0.0-75.27.0 
**  5881.0441 ** CARD 1215 SCCP64        Incorrect MBD - CPU
                 HW VERIFICATION CODE:   180

Alarm Level: Major

Recovery

  1. If this message contains the optional line HW VERIFICATION CODE: 180:
    • Decode the 180 value and correct the indicated problem.

      See the Hardware Verification Codes in UAMs section of hardware verification codes in the Unsolicited Alarms and Information Messages manual.

    • After correcting the problem, the card is in out-of-service maintenance disabled state (OOS-MT-DSBLD).

      Restore the card back to in-service normal state (IS-NR) with the alw-card command.

    If this message does not contain the optional line HW VERIFICATION CODE: 180, continue with the next step.
  2. Verify the hardware.

    Verify the SM card(s) supports the provisioned database capacity.

    Refer to the Maintenance manual for card removal/replacement procedures.

3.2.363 0442 - RTDB Database Capacity is 90% Full

EPAP database capacity alarms are triggered by allocated capacity, whereas EAGLE alarms are triggered by provisioned capacity.

Allocated Capacity refers to the amount of memory that is currently dedicated to storing each RTDB entity-type. For instance when the very first DN is added to the EPAP RTDB, the EPAP allocates a block of memory large enough to store 6 million DNs. Although most of this memory is not in-use (provisioned) it has been demarcated for future use and cannot be utilized to store other non-DN entities (such as IMSIs or DN-Blocks, etc).

Provisioned Capacity refers to the provisioned RTDB entries versus the max RTDB entries allowed on an EAGLE SM card by the EPAP/ELAP related quantity features activated on EAGLE. EAGLE RTDB capacity alarms are triggered when the provisioned capacity passes the 80% and 90% levels. Furthermore, if the EAGLE RTDB provisioned capacity is below 80% and the allocation of the next memory block by EPAP would cause overallocation of the DSM Memory on an EPAP SM card, the EAGLE will report the 80% capacity alarm for that card.

Example 
RLGHNCXA21W 14-05-07 11:02:30 EST  EAGLE 46.0.0
0100.0442  *C CARD 1108  VSCCP   RTDB database capacity is 90% full

Alarm Level:Critical

Recovery

  1. For ELAP, perform the following:
    1. Use the rept-stat-sccp command to identify all SCCP cards. 
      tekelecstp 000623 13:34:22 EST  EAGLE5 36.0.0
    SCCP SUBSYSTEM REPORT IS-NR          Active      
         SCCP ALARM STATUS = No Alarms
    INPQ SUBSYSTEM REPORT IS-ANR         Restricted  -----
         ASSUMING MATE’S LOAD
         INPQ: SSN STATUS = Allowed     MATE SSN STATUS  = Prohibited
         INPQ ALARM STATUS = No Alarms
    GFLEX SERVICE REPORT IS-ANR         Active
         GFLEX ALARM STATUS = No Alarms
    MNP SERVICE REPORT   IS-ANR         Active
         MNP ALARM STATUS   = No Alarms

    SCCP Cards Configured=4  Cards IS-NR=2
    System TPS Alarm Threshold = 100% Total Capacity
    System Peak SCCP Load = 3000 TPS
    System Total SCCP Capacity = 5000 TPS

    CARD   VERSION      PST          SST         AST       MSU USAGE  CPU USAGE
    --------------------------
    1212   101-001-000  IS-NR        Active      ALMINH       45%         30%
    1301 P 101-001-000  IS-NR        Active      ------       35%         40%
    1305   -----------  OOS-MT       Isolated    ------        0%          0%
    2112   -----------  OOS-MT-DSBLD Manual      ------        0%          0%
    ---------------------------
    SCCP Service Average MSU Capacity = 40%       Average CPU Capacity = 35%

    AVERAGE CPU USAGE PER SERVICE: 
      GTT   = 15%  GFLEX =  5%  MNP = 10%
      INPMR =  2%  INPQ  =  3%   

    TOTAL SERVICE STATISTICS:
                                      FAIL     REROUTE\      FORWARD
      SERVICE    SUCCESS    ERRORS   RATIO     WARNINGS        TO GTT     TOTAL
      GTT:          1995         5      0%            -             -     2000  
      GFLEX:         500         1      0%            4            10      515
      MNP:           800         0      0%            2             3      805
      INPMR:          50         5      0%            0            15       70
      INPQ:          499         1      0%            -             -      500

    Command Completed.
    2. Use the rept-stat-card:loc=xxxx:mode=full command to determine daughterboard memory on each SCCP card.

      where xxxx is the SCCP card location. Verify the DSM’s database memory size. 

      rlghncxa03w 05-07-27 16:43:42 EST  EAGLE 30.0.0
CARD  VERSION     TYPE    APPL     PST           SST       AST
1113  023-102-000 GPSM    EOAM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL version = 023-001-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  CLOCK A           = Active
  CLOCK B           = Idle
  CLOCK I           = Idle
  MBD BIP STATUS    = valid 
  DB STATUS         = valid
  DBD MEMORY SIZE   = 256M
  TROUBLE TEXT VER. = Rev 1.6
Command Completed.
;
    3. Use the rtrv-ctrl-feat command to verify the LNP Database feature quantity purchased for this system.
    4. Refer to ELAP Administration and LNP Feature Activation Guide to view the DSM requirements for the LNP telephone number quantity verified under rtrv-ctrl-feat. Contact your Oracle Communications Sales Representative or Account Representative if larger DSMs are needed.

      Proceed to next step if DSM capacity is not the issue.

    5. From the ELAP GUI, execute View RTDB Status and verify the ELAP is reporting the same alarm as the EAGLE.
    6. Verify the TN Counts listed on the GUI.
    7. Go to View LNP Qty Features on the ELAP GUI and verify the LNP ported TNs. This value should reflect the same information as seen under rtrv-ctrl-feat in the EAGLE.
    8. If the TN Count under View RTDB Status is 90% of the LNP ported TNs shown under View LNP Qty Features, this is the cause of the UAM 0442 – RTDB database capacity is 90% full.
    9. If the TN Count is not 90% of the LNP ported TNs, check to see if the NPANXX or LRN Counts are 90% of the LNP ported NPANXXs or LRNs values.
    10. Reduce the number of either TNs, LRNs, or NPANXXs by utilizing features/tools on the LSMS. Refer to Database Administrator's Guide for LSMS.
    11. If reducing the number of TNs, LRNs, or NPANXXs is not a viable option, increase the LNP telephone number quantity. Refer to the section "Activating the LNP Feature on the EAGLE" in Administration and LNP Feature Activation Guide for ELAP. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA if you do not currently have the next higher TN quantity key.
  2. For EPAP, perform the following:
    1. Use the rtrv-stpopts command to determine the status of EPAP data quantity related options. The following example shows the status of the EPAP240M Feature: 
      Command Accepted - Processing
    tekelecstp 16-03-16 12:05:53 MST  EAGLE5 46.3.0.0.0-68.14.0
    STP OPTIONS
    -------------------------------
    EPAP240M                    off
    2. Use the rtrv-ctrl-feat:status=on command to determine the status of EPAP data related features that are currently activated. The following example shows the status of the EPAP Data Split feature: 
      rlghncxa03w 12-03-13 16:40:40 EST EAGLE 46.4.0
The following features have been permanently enabled:

Feature Name               Partnum    Status  Quantity

EPAP Data Split            893039801   on     ----
Dual ExAP Config           893040501   on     ----
    3. Run the rtrv-bip:loc=<> command and use the part number of the card to determine the hardware type: 
      Command Accepted - Processing

    eagle1 16-10-03 18:31:34 EST   EAGLE 46.3.0.0.1-68.27.0
    rtrv-bip:loc=1317
    Command entered at terminal #13.
;

    eagle1 16-10-03 18:31:34 EST   EAGLE 46.3.0.0.1-68.27.0
    --------------------------------------------------------------------------
    Location:  1317 - MBD

    Part Number:    870-2990-01
    Revision:       F                          Week/Year:        14/2012
    Serial Number:  10212145089

    Software Match ID:   EG - 001              Max Power Rating :  1537mA
    --------------------------------------------------------------------------
    END OF REPORT
      See the "Hardware Baseline EAGLE Release 45.0 - 46.x" table in Hardware Reference for card part numbers.
    4. Run the rept-stat-card:mode=full:loc=<> command and use the GPL name to determine the GPL type (32-bit or 64-bit) the card is running.
      See Chapter 3, "Introduction" in Database Administration - System Management to determine the GPL types. 
      Command Accepted - Processing

    eagle1 16-10-03 18:18:12 EST   EAGLE 46.3.0.0.1-68.27.0
    rept-stat-card:mode=full:loc=1317
    Command entered at terminal #13.
;

    eagle1 16-10-03 18:18:12 EST   EAGLE 46.3.0.0.1-68.27.0
    CARD   VERSION      TYPE      GPL        PST            SST        AST
    1317   138-022-000  DSM       SCCP64     IS-NR          Active     -----
      ALARM STATUS       = No Alarms.
      BLDC64  GPL version = 138-023-000
      IMT BUS A           = Conn
      IMT BUS B           = Disc
      CLOCK A             = Active
      CLOCK B             = Fault
      CLOCK I             = Idle
      MBD BIP STATUS      = Valid
      MOTHER BOARD ID     = SMXG B
      DBD STATUS          = Valid
      DBD TYPE            = None
      DBD MEMORY SIZE     = 8192M
      HW VERIFICATION CODE = ----
      CURRENT TEMPERATURE   =  28C ( 83F)
      PEAK TEMPERATURE:     =  32C ( 90F)     [16-09-21 02:02]
      SCCP % OCCUP        = 0%
      SCCP SM DATA TYPE   = DN
      APPLICATION SERVICING
                                        MFC         MFC
          SNM     REQ STATUS =   24 hr: ---, 5 min: ---
          INM     REQ STATUS =   24 hr: ---, 5 min: ---
          MTP3    REQ STATUS =   24 hr: ---, 5 min: ---
          SFLOG   REQ STATUS =   24 hr: ---, 5 min: ---
      IPLNK STATUS
          IPLNK  IPADDR             STATUS     PST
          A      192.168.120.13     UP         IS-NR
          B      192.168.121.13     UP         IS-NR
      DSM IP CONNECTION
          PORT   PST             SST
          A      IS-NR           Active          
          B      IS-NR           Active

    Command Completed.
    5. Refer to the "EAGLE Feature and EPAP DB Capacity Combinations" table in Database Administration - GTT User's Guide to determine the maximum RTDB capacity based on the installed hardware and EPAP Quantity features activated in the system.
    6. Do one of the following:
      • Reduce the size of the database to match the installed hardware capacities.
      • Obtain and install a larger capacity SM card.
      • Obtain and activate the appropriate EPAP Quantity features.
      • Verify that the SM card is running the appropriate GPL type (32-bit or 64-bit).
    7. If the SM card requires 64-bit GPLs and the card is currently running 32-bit GPLs, see "Conversion of SM8G-B Cards" or "Conversion of SLIC Cards" in Database Administration - System Management User's Guide to convert 32-bit GPLs to 64-bit.

3.2.364 0443 - RTDB Database Corrupted

A RTDB database is corrupt. The calculated checksum did not match the checksum value stored for one or more records.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
* 0100.0443 * CARD  1108 VSCCP     RTDB database corrupted

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the status of the RTDB database:
    rept-stat-db:display=all:db=mps

    Caution:

    If more than one card is corrupt, perform 2 through 5 to completion for one card at a time.
  2. Enter the following command to verify the status of the corrupt card:
    rept-stat-card:loc=xxxx

    Where xxxx is the location of the card identified in the output.

  3. Examine the output from 2 Verify that the SST (secondary state of the card) is not Restrict.
    If the SST is Restrict, do not continue with this procedure. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  4. Enter the following command to correct the VSCCP card.

    This command reinitializes the card and forces the card to load the current level of the database. Wait for the reload to complete before continuing.

    init-card:loc=xxxx

    Where xxxx is the location of the card identified in output.

  5. Enter the following command to verify that the database is the same level as the other cards in the system:
    rept-stat-db:display=all:db=mps
  6. If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.365 0444 - RTDB Database is Inconsistent

One or more DSM card’s real time database is not identical to the current real time database on the active EPAP fixed disks.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
* 0100.0444 * CARD  1108 VSCCP    RTDB database is inconsistent

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the status of the RTDB database:
    rept-stat-db:display=all:db=mps

    Caution:

    If more than one card is inconsistent, perform 2 through 5 to completion for one card at a time.
  2. Enter the following command to verify the status of the inconsistent card:
    rept-stat-card:loc=xxxx

    Where xxxx is the location of the card identified in the output.

  3. Examine the output from 2. Verify the SST (secondary state of the card) is not Restrict.
    If the SST is Restrict, do not continue with this procedure. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  4. Enter the following command to correct the VSCCP card.
    This command reinitializes the card and forces the card to load the current level of the database. Wait for the reload to complete before continuing.
    init-card:loc=xxxx
    Where xxxx is the location of the card identified in the output.
  5. Enter the following command to verify the that the database is the same level as the other cards in the system:
    rept-stat-db:display=all:db=mps
  6. If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.366 0445 - RTDB Database Has Been Corrected

This message indicates that a problem with the RTDB has been corrected.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0445    CARD  1108 VSCCP    RTDB database has been corrected

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.367 0446 - RTDB Satabase Capacity is 80% Full

EPAP database capacity alarms are triggered by allocated capacity, whereas EAGLE alarms are triggered by provisioned capacity.

Allocated Capacity refers to the amount of memory that is currently dedicated to storing each RTDB entity-type. For instance when the very first DN is added to the EPAP RTDB, the EPAP allocates a block of memory large enough to store 6 million DNs. Although most of this memory is not in-use (provisioned) it has been demarcated for future use and cannot be utilized to store other non-DN entities (such as IMSIs or DN-Blocks, etc.).

Provisioned Capacity refers to the provisioned RTDB entries versus the max RTDB entries allowed on an EAGLE SM card by the EPAP/ELAP related quantity features activated on EAGLE. EAGLE RTDB capacity alarms are triggered when the provisioned capacity passes the 80% and 90% levels. Furthermore, if the EAGLE RTDB provisioned capacity is below 80% and the allocation of the next memory block by EPAP would cause overallocation of the DSM Memory on an EPAP SM card, the EAGLE will report the 80% capacity alarm for that card.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0.0
*   0100.0446  * CARD 1108 VSCCP   RTDB database capacity is 80% full

Alarm Level: Minor

Recovery

  1. For ELAP, perform the following from the EAGLE STP:
    1. Use the rept-stat-sccp command to identify all SCCP cards. 
      tekelecstp 000623 13:34:22 EST  EAGLE5 36.0.0
    SCCP SUBSYSTEM REPORT IS-NR          Active      
         SCCP ALARM STATUS = No Alarms
    INPQ SUBSYSTEM REPORT IS-ANR         Restricted  -----
         ASSUMING MATE’S LOAD
         INPQ: SSN STATUS = Allowed     MATE SSN STATUS  = Prohibited
         INPQ ALARM STATUS = No Alarms
    GFLEX SERVICE REPORT IS-ANR         Active
         GFLEX ALARM STATUS = No Alarms
    MNP SERVICE REPORT   IS-ANR         Active
         MNP ALARM STATUS   = No Alarms

    SCCP Cards Configured=4  Cards IS-NR=2
    System TPS Alarm Threshold = 100% Total Capacity
    System Peak SCCP Load = 3000 TPS
    System Total SCCP Capacity = 5000 TPS

    CARD   VERSION      PST          SST         AST       MSU USAGE  CPU USAGE
    --------------------------
    1212   101-001-000  IS-NR        Active      ALMINH       45%         30%
    1301 P 101-001-000  IS-NR        Active      ------       35%         40%
    1305   -----------  OOS-MT       Isolated    ------        0%          0%
    2112   -----------  OOS-MT-DSBLD Manual      ------        0%          0%
    ---------------------------
    SCCP Service Average MSU Capacity = 40%       Average CPU Capacity = 35%

    AVERAGE CPU USAGE PER SERVICE: 
      GTT   = 15%  GFLEX =  5%  MNP = 10%
      INPMR =  2%  INPQ  =  3%   

    TOTAL SERVICE STATISTICS:
                                      FAIL     REROUTE\      FORWARD
      SERVICE    SUCCESS    ERRORS   RATIO     WARNINGS        TO GTT     TOTAL
      GTT:          1995         5      0%            -             -     2000  
      GFLEX:         500         1      0%            4            10      515
      MNP:           800         0      0%            2             3      805
      INPMR:          50         5      0%            0            15       70
      INPQ:          499         1      0%            -             -      500

    Command Completed.
    2. Use the rept-stat-card:loc=xxxx:mode=full command to determine daughterboard memory for each SCCP card.
      where xxxx is the SCCP card location. 
      rlghncxa03w 05-07-27 16:43:42 EST  EAGLE 30.0.0
CARD  VERSION     TYPE    APPL     PST           SST       AST
1113  023-102-000 GPSM    EOAM     IS-NR         Active    -----
  ALARM STATUS      = No Alarms.
  BPDCM GPL version = 023-001-000
  IMT BUS A         = Conn
  IMT BUS B         = Conn
  CLOCK A           = Active
  CLOCK B           = Idle
  CLOCK I           = Idle
  MBD BIP STATUS    = valid 
  DB STATUS         = valid
  DBD MEMORY SIZE   = 256M
  TROUBLE TEXT VER. = Rev 1.6
Command Completed.
    3. Use the rtrv-ctrl-feat command to verify the LNP Database feature quantity purchased for this system.
    4. Refer to ELAP Administration and LNP Feature Activation to view the DSM requirements for the LNP telephone number quantity verified under rtrv-ctrl-feat. Contact your Sales Representative or Account Representative if larger DSMs are needed.

      Proceed to next step if DSM capacity is not the issue.

    5. From the ELAP GUI, execute View RTDB Status and verify the ELAP is reporting the same alarm as the EAGLE.
    6. Verify the TN Counts listed on the GUI.
    7. Go to View LNP Qty Features on the ELAP GUI and verify the LNP ported TNs. This value should reflect the same information as seen under rtrv-ctrl-feat in the EAGLE.
    8. If the TN Count under View RTDB Status is 80% of the LNP ported TNs shown under View LNP Qty Features, this is the cause of the UAM 0446 – RTDB database capacity is 80% full.
    9. If the TN Count is not 80% of the LNP ported TNs, check to see if the NPANXX or LRN Counts are 80% of the LNP ported NPANXXs or LRNs values.
    10. Reduce the number of either TNs, LRNs, or NPANXXs by utilizing features/tools on the LSMS. Refer to Database Administration Guide for LSMS.
    11. If reducing the number of TNs, LRNs, or NPANXXs is not a viable option, increase the LNP telephone number quantity. Refer to the section Activating the LNP Feature on the EAGLE in ELAP Administration and LNP Feature Activation.

      Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA, if you do not currently have the next higher TN quantity key.

  2. For EPAP, perform the following:
    1. Use the rtrv-stpopts command to determine the status of EPAP data quantity related options. The following example shows the status of the EPAP240M Feature: 
      Command Accepted - Processing
    tekelecstp 16-03-16 12:05:53 MST  EAGLE5 46.3.0.0.0-68.14.0
    STP OPTIONS
    -------------------------------
    EPAP240M                    off
    2. Use the rtrv-ctrl-feat:status=on command to determine the status of EPAP data related features that are currently activated. The following example shows the status of the EPAP Data Split feature: 
      rlghncxa03w 12-03-13 16:40:40 EST EAGLE 46.4.0
The following features have been permanently enabled:

Feature Name               Partnum    Status  Quantity

EPAP Data Split            893039801   on     ----
Dual ExAP Config           893040501   on     ----
    3. Run the rtrv-bip:loc=<> command and use the part number of the card to determine the hardware type: 
      Command Accepted - Processing

    eagle1 16-10-03 18:31:34 EST   EAGLE 46.3.0.0.1-68.27.0
    rtrv-bip:loc=1317
    Command entered at terminal #13.
;

    eagle1 16-10-03 18:31:34 EST   EAGLE 46.3.0.0.1-68.27.0
    --------------------------------------------------------------------------
    Location:  1317 - MBD

    Part Number:    870-2990-01
    Revision:       F                          Week/Year:        14/2012
    Serial Number:  10212145089

    Software Match ID:   EG - 001              Max Power Rating :  1537mA
    --------------------------------------------------------------------------
    END OF REPORT
      See the "Hardware Baseline EAGLE Release 45.0 - 46.x" table in Hardware Reference for card part numbers.
    4. Run the rept-stat-card:mode=full:loc=<> command and use the GPL name to determine the GPL type (32-bit or 64-bit) the card is running.
      See Chapter 3, "Introduction" in Database Administration - System Management to determine the GPL types. 
      Command Accepted - Processing

    eagle1 16-10-03 18:18:12 EST   EAGLE 46.3.0.0.1-68.27.0
    rept-stat-card:mode=full:loc=1317
    Command entered at terminal #13.
;

    eagle1 16-10-03 18:18:12 EST   EAGLE 46.3.0.0.1-68.27.0
    CARD   VERSION      TYPE      GPL        PST            SST        AST
    1317   138-022-000  DSM       SCCP64     IS-NR          Active     -----
      ALARM STATUS       = No Alarms.
      BLDC64  GPL version = 138-023-000
      IMT BUS A           = Conn
      IMT BUS B           = Disc
      CLOCK A             = Active
      CLOCK B             = Fault
      CLOCK I             = Idle
      MBD BIP STATUS      = Valid
      MOTHER BOARD ID     = SMXG B
      DBD STATUS          = Valid
      DBD TYPE            = None
      DBD MEMORY SIZE     = 8192M
      HW VERIFICATION CODE = ----
      CURRENT TEMPERATURE   =  28C ( 83F)
      PEAK TEMPERATURE:     =  32C ( 90F)     [16-09-21 02:02]
      SCCP % OCCUP        = 0%
      SCCP SM DATA TYPE   = DN
      APPLICATION SERVICING
                                        MFC         MFC
          SNM     REQ STATUS =   24 hr: ---, 5 min: ---
          INM     REQ STATUS =   24 hr: ---, 5 min: ---
          MTP3    REQ STATUS =   24 hr: ---, 5 min: ---
          SFLOG   REQ STATUS =   24 hr: ---, 5 min: ---
      IPLNK STATUS
          IPLNK  IPADDR             STATUS     PST
          A      192.168.120.13     UP         IS-NR
          B      192.168.121.13     UP         IS-NR
      DSM IP CONNECTION
          PORT   PST             SST
          A      IS-NR           Active          
          B      IS-NR           Active

    Command Completed.
    5. Refer to the "EAGLE Feature and EPAP DB Capacity Combinations" table in Database Administration - GTT User's Guide to determine the maximum RTDB capacity based on the installed hardware and EPAP Quantity features activated in the system.
    6. Do one of the following:
      • Reduce the size of the database to match the installed hardware capacities.
      • Obtain and install a larger capacity SM card.
      • Obtain and activate the appropriate EPAP Quantity features.
      • Verify that the SM card is running the appropriate GPL type (32-bit or 64-bit).
    7. If the SM card requires 64-bit GPLs and the card is currently running 32-bit GPLs, see "Conversion of SM8G-B Cards" or "Conversion of SLIC Cards" in Database Administration - System Management User's Guide to convert 32-bit GPLs to 64-bit.

3.2.368 0447 - RTDB Database Capacity Alarm Cleared

This message indicates that a problem with the RTDB memory has been corrected.

When the TN, LRN, or NPA control features are involved, this UAM message indicates either the feature key quantity has been increased or the RTDB database size has been reduced to clear the condition.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0447    CARD  1108 VSCCP   RTDB database capacity alarm cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This message indicates a previous fault has been corrected.
    No further action is necessary.

3.2.369 0448 - RTDB Database Incoherent

This message indicates that the RTDB database download is in-process or that the update failed.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
* 0100.0448 * CARD  1108 VSCCP      RTDB database incoherent

Alarm Level: Minor

Recovery

  1. If the message RTDB database has been corrected is displayed after the download is complete, no further action is necessary. 
    0445 - RTDB database has been corrected
  2. Enter the following command to verify the status of the RTDB database:
    rept-stat-db:display=all:db=mps

    Caution:

    Continue with the remainder of this procedure only if 1 did not compete successfully. If more than one card is incoherent, perform 2 through 6 to completion for one card at a time.
  3. Enter the following command to verify the status of the incoherent card:
    rept-stat-card:loc=xxxx

    Where xxxx is the location of the card identified in the output.

  4. Examine the output from 3. Verify that the SST (secondary state of the card) is not Restrict.
    If the SST is Restrict, do not continue with this procedure. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  5. Enter the following command to correct the VSCCP card.
    This command reinitializes the card and forces the card to load the current level of the database. Wait for the reload to complete before continuing.
    init-card:loc=xxxx
    Where xxxx is the location of the card identified in the output.
  6. Enter the following command to verify the that the database is the same level as the other cards in the system:
    rept-stat-db:display=all:db=mps
  7. If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.370 0449 - RTDB Resynchronization in Progress

This message indicates the MPS database resynchronization is in process.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0449  **  CARD  1108 VSCCP   RTDB resynchronization in progress

Alarm Level: Major

Recovery

When the resynchronization is complete, the RTDB database has been corrected message is displayed. 
0445 - RTDB database has been corrected
No further action is necessary

If the MPS has been inhibited, the generic clearing alarm 0500 is displayed. Otherwise, when the resynchronization is complete, the 0445 - RTDB database has been corrected message is displayed.

3.2.371 0450 - Invalid HW for Integrated GLS

The Integrated GLS Feature requires E5-based control cards. This UAM is generated when legacy control cards are installed in the standby MASP location after the Integrated GLS feature is turned on. This action changes the GLS subsystem state to IS-ANR.

Example 
*   0002.0450 *  GLS System            Invalid HW for Integrated GLS

Alarm Level: Major

Recovery

Replace the legacy control cards (labeled GPSM-II and TDM on the cards) with E5-based control cards (labeled E5-MASP) when enabling the Integrated GLS Feature.

3.2.372 0451 - RTDB Reload Required

The RTDB database on the DSM card needs to be reloaded because the resynch log does not contain all of the required updates.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0451 ** CARD  1108 VSCCP    RTDB reload required

Alarm Level: Major

Recovery

  1. Enter the following command to verify the status of the RTDB:
    rept-stat-db:display=all:db=mps
  2. Enter the following command to correct the VSCCP card.
    This command reinitializes the card and forces the card to load the current level of the database:
    init-card:loc=xxxx
    where xxxx is the location of the card identified in output.
  3. When the reload is complete, the RTDB database has been corrected message is displayed. 
    0445 - RTDB database has been corrected
No further action is necessary
  4. If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.373 0452 - Exceeded Service Error Threshold Lvl 1

This UAM is generated when the EAGLE 5 ISS detects SCCP or Application traffic failure rates greater than the defined level 1 Service Error Threshold.

Note:

UAM 527 is also expected when the errors exceed the threshold level (UAM452/453). These alarms are auto-cleared when the error condition abates (below threshold level1 for UAM 452 and level 2 for UAM 453)
Example 
RLGHNCXA21W 00-11-07 11:02:30 EST  EAGLE 35.0.0
** 0014.0452 ** SCCP SYSTEM       Exceeded Service Error Threshold Lvl 1

Alarm Level: Major

Recovery

  1. Enter the following command to verify the database threshold:
    rtrv-th-alm
  2. Enter the following command to verify the Fail Ratio of the service in question:
    rept-stat-sccp
  3. Enter the following command up to three times to ensure all DSMs are accepting updates:
    rept-stat-db:display=all:db=mps
    • If the DSMs are accepting updates, proceed to 4.
    • If the DSMs are not accepting the updates and they all stopped at the same level, inspect the respective EPAP or ELAP application attached to the EAGLE, and correct any issues on the EPAP or ELAP application.
  4. Enter the following command to retrieve records from the active or standby Alarm and UIM logs generated by the Maintenance system:
    rtrv-log:type=xxx

    where: xxx=ALL, ALARM, or UIM.

    For more information on available parameters, refer to the Commands Manual.
  5. For further assistance, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.374 0453 - Exceeded Service Error Threshold Lvl 2

This UAM is generated when the EAGLE 5 ISS detects SCCP or Application traffic failure rates greater than the defined level 2 Service Error Threshold.

Note:

UAM 527 is also expected when the errors exceed the threshold level (UAM 452/453). These alarms are auto-cleared when the error condition abates (below threshold level1 for UAM 452 and level 2 for UAM 453).
Example 
RLGHNCXA21W 00-11-07 11:02:30 EST  EAGLE 35.0.0
*C  0014.0453 *C SCCP SYSTEM       Exceeded Service Error Threshold Lvl 2

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the database threshold:
    rtrv-th-alm
  2. Enter the following command to verify the Fail Ratio of the service in question:
    rept-stat-sccp
  3. Enter the following command up to three times to ensure all DSMs are accepting updates:
    rept-stat-db:display=all:db=mps
    • If the DSMs are accepting updates, proceed to the next step.
    • If the DSMs are not accepting the updates and they all stopped at the same level, inspect the respective EPAP or ELAP application attached to the EAGLE. Correct any issues on the EPAP or ELAP application.
  4. Enter the following command to retrieve records from the active or standby Alarm and UIM logs generated by the Maintenance system:
    rtrv-log:type=xxx

    where: xxx=ALL, ALARM, or UIM.

    For more information on available parameters, refer to the Commands Manual.
  5. For further assistance, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.375 0454 - Service Error Threshold Alarm Cleared

This message is generated when the Service Error Threshold alarm is cleared.

Example 
    RLGHNCXA21W 00-11-07 11:02:30 EST  EAGLE 35.0.0
    0014.0454 SCCP    1205,Service Error Threshold Cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.376 0455 - EIR Subsystem is Not Available

The EIR subsystem is not available. No IS-NR VSCCP cards are associated with this EIR subsystem. No VSCCP cards have an Active EIR status; all are either out-of service (OOS) or loading. The EIR subsystem was not taken off-line via command.

Example 
RLGHNCXA21W 03-08-18 12:01:43 EST  EAGLE 35.0.0
*C 0056.0455  *C  EIR SYSTEM    EIR Subsystem is not available

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  2. Enter the following command to move the VSCCP cards to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT-DSBLD VSCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  4. Verify the VSCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.377 0456 - EIR Subsystem is Disabled

The EIR subsystem has been manually disabled with the inh-map-ss command. All IS-NR (in service normal) cards have EIR status of Offline, with at least one card IS-NR.

Example 
RLGHNCXA21W 03-08-18 12:01:43 EST  EAGLE 35.0.0
*C 0056.0456  *C  EIR SYSTEM   EIR Subsystem is disabled

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the EIR subsystem cards:
    rept-stat-mps
  2. Enter the following command to reserve the subsystem number and to change the state of the EIR subsystem status to on-line:
    ent-ss-appl:appl=eir:ssn=xx:stat=online

    where xx is primary subsystem number.

  3. Enter the following command to change the state of the EIR subsystem to on-line:
    alw-map-ss:ssn=xx

    where xx is primary subsystem number.

  4. Enter the following command to verify the status of the EIR subsystem:
    rept-stat-mps

3.2.378 0457 - EIR Subsystem Normal, Card(s) Abnormal

One or more of the VSCCP cards do not have an Active status.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
*C 0056.0457      EIR SYSTEM   EIR Subsystem normal, card(s) abnormal

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  2. Enter the following command to move the VSCCP card to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT-DSBLD VSCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  4. Verify the VSCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.379 0458 - EIR Subsystem is Available

This message indicates that a problem with the EIR subsystem has been corrected. All VSCCP cards are IS-NR and have an EIR status of Active.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0056.0458     EIR SYSTEM   EIR Subsystem is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.380 0459 - EIR Subsystem is Removed

The EIR subsystem is not equipped. No VSCCP cards are configured with the EIR subsystem.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0056.0459      EIR SYSTEM    EIR Subsystem is removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the VSCCP hardware.

Configure the EIR system with VSCCP cards. Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.381 0460 - EIR Subsystem degraded, card(s) abnormal

One or more EIR cards goes out of service in (N or N+1) configuration or not IS-NR.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 46.0.0
0056.0460      EIR SYSTEM   EIR Subsystem degraded, card(s) abnormal

Alarm Level: Major.

Recovery

  1. Restore the one or more EIR out of service cards in (N or N+1) configuration or not IS-NR.

3.2.382 0466 - STC Network Unavailable

This indicates the network connected to the STC (port A/B) is inaccessible.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0466 ** CARD 1201 STC  STC Network Unavailable

Alarm Level: Major

Recovery

Re-association should take place automatically.

If it does not, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.383 0467 - STC Network Available

This indicates the network connected to the STC (port A/B) is now accessible.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0467    CARD 1201 STC  STC Network Available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.384 0468 - All STC Networks Unavailable

All connections off all the STC cards (port A/B) are inaccessible.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*C 0014.0468  *C EROUTE System  All STC Networks Unavailable

Alarm Level: Critical

Recovery

Re-association should take place automatically.

If it does not, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.385 0469 - All STC Cards Unavailable

All the STC cards are not accessible.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*C 0014.0469 *C EROUTE System  All STC Cards unavailable

Alarm Level: Critical

Recovery

  1. Determine if all STC cards are out of service by entering the following command:
    rept-stat-card
  2. Reinitialize the STC cards by entering the following command:
    init-card:appl=eroute
  3. If the fault has not cleared, reseat each faulty STC card.
  4. If the alarm is not cleared, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.386 0470 - EROUTE is Removed

All the STC cards have been deleted.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0470    EROUTE System  EROUTE is Removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.2.387 0471 - EROUTE System is Available

This message indicates that the EROUTE system is available and fully functional.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0471    EROUTE System  EROUTE System is Available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.388 0472 - EROUTE System Threshold Exceeded

The EROUTE system has reached a rate higher than its threshold of 80% capacity.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0472  * EROUTE System  EROUTE System Threshold Exceeded

Alarm Level: Minor

Recovery

  1. Decrease the number of links being monitored until more STC cards are added to the System.
  2. Refer to the Database Administration Manual - Features for the correct procedure on adding STC cards.

3.2.389 0473 - EROUTE System Capacity Exceeded

The EROUTE system has reached a rate higher than its capacity. There is the possibility of a loss of traffic monitoring.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0473 ** EROUTE System  EROUTE System Capacity Exceeded

Alarm Level: Major

Recovery

  1. Decrease the number of links being monitored until more STC cards are added to the System.
  2. Refer to the Database Administration Manual - Features for the correct procedure on adding STC cards.

3.2.390 0474 - EROUTE Capacity Normal, Card(s) Abnormal

The EROUTE system is operating normally even though one or more card(s) is OOS-MT.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0474    EROUTE System  EROUTE capacity normal, card(s) abnormal

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the following command to determine which STC cards are out of service:
    rept-stat-mon
  2. Reinitialize each faulty STC card using the following command:
    init-card:loc=xxxx

    Where xxxx is the location of each faulty card identified in Step 1.

  3. If the fault has not cleared, reseat each faulty card.

3.2.391 0475 - NTP Time Unavailable

The STC cards are not able to get NTP time from the ESP.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0475  * EROUTE System  NTP Time Unavailable

Alarm Level: Minor

Recovery

Have the far-end (Sentinel) to verify the status of the time process.

Note:

For the complete list of cards supported by EAGLE Release 47.0, see Hardware Reference Guide.

3.2.392 0476 - NTP Time Available

The STC cards are now able to get NTP time from the ESP.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0476    EROUTE System  NTP Time Available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.393 0477 - Congestion: Copy Function De-activated

The Copy Function on the SS7 cards have been de-activated.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0477 * SLK 1205,A nc00027  Congestion: Copy Function De-activated
               SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: Minor

Recovery

  1. Since congestion usually peaks and subsides quickly, a measurements report should be printed to understand what SS7 events took place.
    Use the command rept-meas to obtain a report.

    Note:

    The measurements collection must first be turned on so measurements can be collected. If measurements are not turned on, no report will be available. Refer to the Measurements Manual for traffic measurements information.
  2. Ensure there are enough links in the linkset based on the traffic load.

3.2.394 0478 - Copy Function Activated

The congestion has cleared and the copy function on the SS7 cards have been re-activated.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0478   SLK 1205,A nc00027  Copy Function Activated
             SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.395 0479 - Link Not Monitored

This is a possible clearing condition for UAM 477, Congestion: Copy Function Deactivated or Sentinel Socket Inactive. This implies that the Link's attempt to establish monitoring session is not successful, hence, not being monitored. Therefore any monitoring alarms should be cleared.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0479   SLK 1205,A nc00027  Link not Monitored
            SLC=03   FECLLI=testclli            CLASS=SAAL

Note:

The Class parameter in the example is optional.

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.396 0480 - Timestamp Invalid

This indicates that the LIM card timestamp is invalid.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
*  0014.0480  * CARD 1201 STC  Timestamp Invalid

Alarm Level: Minor

Recovery

This alarm should clear automatically.

If it does not, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.397 0481 - Timestamp Valid

This indicates that the LIM card timestamp is valid.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
0014.0467    CARD 1201 STC  STC Network Available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.398 0482 - Card(s) Have Been Denied EROUTE Service

EROUTE service is being denied service because there is a shortage of STC cards.

Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 35.0.0 
** 0014.0482 ** EROUTE System  Card(s) have been denied EROUTE service

Alarm Level: Major

Recovery

  1. Enter the following command to determine the cards that are denied EROUTE service: rept-stat-mon
  2. Refer to the Database Administration Manual - Features for the correct procedure on adding STC cards.

3.2.399 0483 - DEIR System is not available

The S13 Feature is not ON or the System has no S23 card in ACTIVE/IS_NR.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
*C  0002.0483 *C DEIR SYSTEM            DEIR System is not available

Alarm Level: Critical

Recovery

  1. Activate (Active/IS-NR) any of the DEIR cards in the system.

3.2.400 0484 - DEIR System Normal, Card(s) Abnormal

The number of active S13 cards (i.e., in IS-NR state) is less than half the configured S13 cards.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
*  0002.0484 * DEIR SYSTEM            DEIR System normal, card(s) abnormal

Alarm Level: Major

Recovery

  1. Activate (Active/IS-NR) half or more DEIR cards in the system.

3.2.401 0485 - DEIR System is available

The number of active (Active/IS-NR) S13 cards is equal to or more than half of the configured S13 cards.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0003.0485    DEIR SYSTEM            DEIR System is available

Alarm Level: None

Recovery

No further action necessary.

3.2.402 0486 - DEIR Threshold - Level1 exceeded

The DEIR Card TPS has exceeded configured level-1 value in DEIROPTS.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
*  0002.0486 * DEIR SYSTEM            DEIR Threshold - Level1 exceeded

Alarm Level: Minor

Recovery

  1. Reduce the card TPS below configured level-1 value in DEIROPTS.

3.2.403 0487 - DEIR System Threshold - Level2 exceeded

The DEIR Card TPS has exceeded configured level-2 value in DEIROPTS.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  0002.0487 ** DEIR SYSTEM            DEIR System Threshold - Level2 exceeded

Alarm Level: Major

Recovery

  1. Reduce Card TPS below configured level-2 value in DEIROPTS.

3.2.404 0488 - DEIR Threshold Condition Cleared

The DEIR Card TPS is below configured level-1 value in DEIROPTS..

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
  0002.0488  DEIR SYSTEM            DEIR Threshold Condition Cleared

Alarm Level: None

Recovery

No further action necessary.

3.2.405 0489 - DEIR capacity exceeded

The DEIR Card TPS has exceeded the maximum allowable cards TPS (8000).

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
*C  0002.0489 *C DEIR SYSTEM            DEIR capacity exceeded

Alarm Level: Critical

Recovery

  1. Reduce the card TPS below the overall cards TPS.

3.2.406 0490 - DEIR normal

The S13 card capacity has returned to normal.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
  0002.0490  DEIR SYSTEM            DEIR normal

Alarm Level: None

Recovery

No further action necessary.

3.2.407 0491 - Connection TPS exceeded

The connection present on the DEIR Card has exceeded the maximum allowable connection TPS (MaxTPS) configured in the DCONN table.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  0002.0491 ** DEIR SYSTEM            Connection TPS exceeded

Alarm Level: Major

Recovery

  1. Reduce the connection TPS to below the configured MaxTPS for that connection in the DCONN table.

3.2.408 0492 - Connection TPS normal

The TPS on a connection present DEIR card is below or equal to the maximum allowed TPS (MaxTPS) configured in the DCONN table.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
  0002.0492   DEIR SYSTEM            Connection TPS normal

Alarm Level: None

Recovery

No further action necessary.

3.2.409 0493 - Diameter Connection Down

The SCTP association is Open (open=yes) and the Diameter connection status is down.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
 **   0004.0493 ** DCONN DCNAME1          Diameter Connection Down

Alarm Level: Major

Recovery

  1. Get the diameter connection UP.

3.2.410 0494 - Diameter Connection UP

The SCTP association is Open (open=yes) and the Diameter connection status is UP.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0003.0494    DEIR SYSTEM            Diameter Connection UP

Alarm Level: None

Recovery

No further action is necessary.

3.2.411 0495 - Diameter Connection Closed

The Diameter connection or SCTP association for a diameter connection is closed.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0495   DEIR SYSTEM            Diameter Connection Closed

Alarm Level: None

Recovery

No further action necessary.

3.2.412 0496 - DEIR System is removed

The last S13 card has been deleted from the system.

Example 
   12345678901234567890123456789012345678901234567890123456789012345678901234567890   
  0002.0496    DEIR SYSTEM            DEIR System is removed

Alarm Level: None.

Recovery

No further action is necessary.

3.2.413 0497 - REPT-J1F:FAC-J1 LOS failure

This alarm is present when no signal is being received on the signaling link.

Example
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
**  0123.0497 ** J1PORT 1103,2           REPT-J1F:FAC-J1 LOS failure

Alarm Level: Major

Recovery

Check the physical connections.

3.2.414 0498 - REPT-J1F:FAC-J1 LOF failure

The 7-bit frame alignment signal does not match the pattern the EAGLE is expecting.

Example
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
**  0124.0498 ** J1PORT 1103,2           REPT-J1F:FAC-J1 LOF failure

Alarm Level: Major

Recovery

Contact the far-end office to correct their framing problem.

3.2.415 0499 - REPT-J1F:FAC-J1 Remote Alarm

This alarm is present when there is some type of failure on the far end.

Example
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
**  0125.0499 ** J1PORT 1103,2           REPT-J1F:FAC-J1 Remote Alarm

Alarm Level: Major

Recovery

Contact the far-end office to determine the cause and correct the problem.

3.2.416 0500 - Alarm for This Entity is Being Cleared

This is a generic alarm clearing output that applies to all setting alarms (Critical, Major, or Minor). The alarm for the indicated device is being cleared.

Example 
tekelecstp 99-01-19 14:56:48 EST  EAGLE 31.5.0
0045.0500    DLK 1104,A1             Alarm for this entity is being cleared

Note:

The output can vary significantly. The output varies depending on which device the alarm is being cleared. In this example the alarm is being cleared for a Data Link.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.417 0501 - OAM ITT Sample Minor Alarm

This is an alarm clearing output that applies to Minor setting alarms. The alarm for the indicated device is being cleared.

Example 
tekelecstp 01-01-19 14:56:48 EST  EAGLE 34.0
0045.0501    DLK 1104,A1             Alarm for this entity is being cleared

Note:

The output can vary significantly. The output varies depending on which device the alarm is being cleared. In this example the alarm is being cleared for a Data Link.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.418 0502 - OAM ITT Sample Minor Alarm

This is an alarm clearing output that applies to Minor alarms. The alarm for the indicated device is being cleared.

Example 
tekelecstp 01-01-19 14:56:48 EST  EAGLE 34.0
0045.0502    DLK 1104,A1             Alarm for this entity is being cleared

Note:

The output can vary significantly. The output varies depending on which device the alarm is being cleared. In this example the alarm is being cleared for a Data Link.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.419 0503 - OAM ITT sample Critical Alarm

This is an alarm clearing output that applies to Major alarms. The alarm for the indicated device is being cleared.

Example 
tekelecstp 01-01-19 14:56:48 EST  EAGLE 34.0
0045.0503    DLK 1104,A1             Alarm for this entity is being cleared

Note:

The output can vary significantly. The output varies depending on which device the alarm is being cleared. In this example the alarm is being cleared for a Data Link.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.420 0504 - REPT-J1F:FAC-J1 Alarm

This alarm is present when the J1 port becomes unavailable.

Example
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
**  0126.0504 ** J1PORT 1103,2           REPT-J1F:FAC-J1 Alarm

Alarm Level: Major

Recovery

Contact the far-end office to determine the cause and correct the problem.

3.2.421 0505 - RRCVRY-J1F:FAC-J1 available

This alarm is present when the J1 port is back in-service.

Example
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
0127.0505    J1PORT 1103,2           REPT-J1F::FAC-J1 available

Alarm Level: Normal

Recovery

None.

3.2.422 0506 - REPT-J1F:FAC-J1 unavailable

This alarm is present when the J1 port goes down.

Example
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
**  0128.0506 ** T1/J1PORT 1103,2           REPT-J1F::FAC-J1 unavailable

Alarm Level: Major

Recovery

When the J1 port becomes available.

3.2.423 0514 - Standby MASP Inhibited

This message indicates that the standby OAM is inhibited. Database updates will be rejected until the standby OAM is allowed.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
** 0076.0514 ** CARD 1115 OAM     Standby MASP inhibited

Alarm Level: Major

Recovery

  1. Verify the status of the OAM entering a rept-stat-card command.
  2. Enter the following command to allow the card:
    alw-card:loc=xxxx

    where xxxx = card location (1115 or 1113)

  3. If the card is restored, you have completed this procedure.
    If the card is not restored, check and follow the output to correct the problem, then enter the alw-card command.
  4. If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.424 0515 - Standby MASP Allowed

This message indicates that the inhibited standby OAM has been restored.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
0076.0515  CARD 1115 OAM     Standby MASP allowed

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.425 0516 - Degraded Mode - 1 Card Failed

Measurements are degraded because a card is out of service:

  • If the E5-OAM Integrated Measurements feature is in use, the problem is that one E5-MCAP card is out of service.

  • If the Measurements Platform is in use, the problem is that one MCPM card is out of service.

The E5-OAM Integrated Measurements feature or the Measurements Platform (depending on which is in use) can successfully complete all of its work, but with no spare E5-MCAP card or no spare MCPM card.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*  0100.0516 * MEAS SYSTEM    Degraded Mode - 1 card failed

Alarm Level: Minor

Recovery

  1. Enter the following command to determine the status of the E5-MCAP or MCPM card:.
    rept-stat-meas
  2. Reinitialize the faulty card using the init-card command.
  3. If the fault has not cleared, reseat the faulty card.
  4. If the fault has not cleared, replace the faulty card:
    • If you use E5-OAM Integrated Measurements, the E5-MCAP card is out of service. The E5-MCAP card is part of the E5-MASP card assembly, so replace the E5-MASP card.
    • If you use the Measurements platform, replace the MCPM card.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.426 0517 - Degraded Mode - Multiple Cards Failed

The Measurements Platform subsystem is degraded because more than one MCPM card is out of service. The Measurements Platform subsystem can successfully complete all of its work, but may have no spare MCPM.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
** 0100.0517 ** MEAS SYSTEM    Degraded Mode - multiple cards failed

Alarm Level: Major

Recovery

  1. Enter the following command to determine the status of the MCPM cards:
    rept-stat-meas
  2. Reinitialize the faulty card using the command.
    init-card
  3. If the fault has not cleared, reseat the faulty card.
  4. If the fault has not cleared, replace the faulty MCPM card.
  5. Repeat 2 through 4 for each faulty MCPM card.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.427 0518 - Measurements Subsystem Unavailable

The Measurements Platform subsystem is not available. All MCPM cards are out of service.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
*C 0100.0518   *C   MEAS SYSTEM    Measurements subsystem unavailable

Alarm Level: Critical

Recovery

  1. Enter the following command to determine the status of the MCPM cards:
    rept-stat-meas
  2. Reinitialize the faulty MCPM card using the init-card command.
  3. If the fault has not cleared, reseat the faulty card.
  4. If the fault has not cleared, replace the faulty MCPM card.
  5. Repeat 2 through 4 for each faulty MCPM card.
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.428 0519 - Measurements subsystem available

This message indicates that the Measurements subsystem has been restored to service.

Example
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
0076.0519  MEAS SYSTEM     Measurements subsystem available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.429 0520 - Frame Power Usage Reached LVL3

Frame power usage reached 98% of threshold value.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
*C 0002.0520 *C FRAME CF01 Frame power usage reached LVL3

Alarm Level: Critical

Recovery

  1. Verify that the Frame Power Threshold value is properly configured for the frame for which UAM is generated using the following command:
    rtrv-frm-pwr
  2. Verify that the card population is correct for that particular frame using the following command:
    rtrv-stp:display-power
  3. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA about the generated UAM.

3.2.430 0521 - Frame Power Usage Reached LVL2

Frame power usage reached 95% but is below 98% of threshold value.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
** 0002.0521 ** FRAME CF01 Frame power usage reached LVL2

Alarm Level: Major

Recovery

  1. Verify that the Frame Power Threshold value is properly configured for the frame for which UAM is generated using the following command:
    rtrv-frm-pwr
  2. Verify that the card population is correct for that particular frame using the following command:
    rtrv-stp:display-power
  3. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA about the generated UAM.

3.2.431 0522 - Frame Power Usage Reached LVL1

Frame power usage reached 90% but is below 95% of threshold value.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
*  0002.0521 * FRAME CF01 Frame power usage reached LVL1

Alarm Level: Minor

Recovery

  1. Verify that the Frame Power Threshold value is properly configured for the frame for which UAM is generated using the following command:
    rtrv-frm-pwr
  2. Verify that the card population is correct for that particular frame using the following command:
    rtrv-stp:display-power
  3. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA about the generated UAM.

3.2.432 0523 - Frame power usage normal

Frame power usage is normal.

Example
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
0002.0521 FRAME CF01 Frame power usage normal

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.2.433 0524 - REPT-ALMINH: alarm output TIMED inhibit

A device’s alarm is Timed inhibited using the inh-alm command.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    6277.0524    RTXA    001-101-001     REPT-ALMINH: alarm output TIMED inhibit
                 OPCA=   004-004-004
                 ALARM INHIBIT LEVEL:   MINR

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.2.434 0525 - Timed alm inh rdy to expire

Timed inhibition on a device is about to expire in the next 12 hours.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    6277.0525    RTXA    001-101-001     REPT-ALMINH:Timed alm inh rdy to expire
                 OPCA=   004-004-004
  ALARM INHIBIT LEVEL:   MINR       Expires:      05/05/20 16:00

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.2.435 0526 - Service is Available

A problem with the specified SCCP service has been corrected. All SCCP cards are IS-NR and have a service status of Active.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 34.3.0
0056.0526 GFLEX SERVICE Service is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.436 0527 - Service Abnormal

One or more of the cards providing the specified SCCP service do not have a service status of Active.

Note:

If UAM 527 is subsequent to UAM 452 or 453, then UAM 527 is auto cleared when the error condition abates (below threshold level 1 for UAM 452 and level 2 for UAM 453).

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 34.3.0
* 0056.0527 * GFLEX SERVICE Service abnormal

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the status and location of the SCCP service cards:
    rept-stat-sccp
  2. Enter the following command to move the SCCP service card to an ACTIVE status if loading is successful:
    rst-card:loc-xxxx

    where: xxxx is the location of the OOS-MT-DSBLDSCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the SCCP service cards:
    rept-stat-sccp
  4. Verify the SCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).

    Note:

    Do not reboot the DSMs if UAM 527 is subsequent to UAM 452 or 453. This will not fix the alarm.

  5. If any card(s) remain OOS-MT, replace the card(s).

    Note:

    Refer to the Maintenance Manual for card removal/replacement procedures. for card replacement procedures.

3.2.437 0528 - Service is Not Available

The specified SCCP service is not available. No IS-NRSCCP cards are associated with this specified SCCP service. No SCCP cards providing the specified service have a service status of Active.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 34.3.0
*C 0056.0528 *C GFLEX SERVICE Service is not available

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the SCCP service cards:
    rept-stat-sccp
  2. Enter the following command to move the SCCP service card to an ACTIVE status if loading is successful:
    rst-card:loc-xxxx

    where: xxxx is the location of the OOS-MT-DSBLD SCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the SCCP service cards:
    rept-stat-sccp
  4. Verify the SCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).

    Note:

    Refer to the Maintenance Manual for card removal/replacement procedures. for card replacement procedures.

3.2.438 0529 - Service is Disabled

The specified SCCP service has been manually disabled with the chg-sccp-serv command. All IS-NR cards providing the service have service status of Offline.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 34.3.0
*C 0056.0529 *C GFLEX SERVICE Service is disabled

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the SCCP service cards:
    rept-stat-sccp
  2. Enter the following command to change the state of the SCCP service status to on-line:
    chg-sccp-serv:serv-xxxx:state=online

    where: xxxx is the SCCP service name.

  3. Enter the following command to verify the status of the SCCP service cards:
    rept-stat-sccp

3.2.439 0530 - Service is Removed

The specified SCCP service is not equipped. No SCCP cards are configured with the service.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 34.3.0
0056.0530 GFLEX SERVICE Service is removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the SCCP hardware.

Configure the specified service with SCCP cards.

Note:

Refer to the Maintenance Manual for card removal/replacement procedures. for card replacement procedures.

3.2.440 0531 - Insufficient HW Copy Function Inhibited

HIPR cards must be installed in the same shelf as the IPLIMx and IPGWx card if their links are monitored. Therefore, monitoring will be inhibited on links on IPLIMx or IPGWx cards if a HIPR card is not installed in the same shelf. This is accomplished by ignoring an EMP service accept message after a service request is sent when HPIR cards are not installed. In addition, any active EMP TCP connections on an IPLIM or IPGW link is disconnected if both HIPR cards in the same shelf are removed. A new minor link alarm is implemented to report when monitoring on a link has been inhibited in this manner.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
*0 044.0531 *SLK 1201,A lsnabcde Insufficient HW Copy Function Inhibited

Alarm Level: Minor

Recovery

Replace the HMUX cards in the same shelf as the IPLIMx or IPGWx cards that produced the alarm with HIPR cards.

Note:

Refer to the Maintenance Manual for card removal/replacement procedures. for card replacement procedures.

3.2.441 0532 - RTX is Allowed

A previous fault is corrected and the EAGLE 5 ISS system can send traffic to the specified DPC using the exception route set identified by the specified class and criterion.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
0044.0532 RTX 001-101-001 RTX is allowed
          ILSN=lsn012345

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.2.442 0533 - RTX is Restricted

A transfer-restricted message has been received concerning the exception route set. Possible causes are as follows:

  • One or more routes in this exception route set are unavailable.

  • A low priority route is carrying the traffic. The primary and combined routes are not available for traffic in this exception route set.

Example 
RLGHNCXA3W 00-11-06 10:55:49 EST EAGLE 35.0.0
*  0044.0533 * RTX 001-101-001 RTX is restricted
               ILSN=lsn012345

Alarm Level: Minor

Recovery

  1. Enter the following command using the DPC and RTX exception class specified in the output message to determine which linkset has a problem:
    rept-stat-rtx:dpc=aaaa=xxx-xxx-xxx:cccc=zzzz
    where
    • aaaa = dpc/dpca, dpci, dpcn, or dpcn24
    • xxx-xxx-xxx = the specified destination point code
    • cccc = opc/opca, opci, opcn, opcn24, ilsn, cic, or si
    • zzzz = the specified value of the above exception class, that establishes the exception routing criterion
  2. Enter the following command using the linkset name specified from the output of 1 to determine which link(s) could have a problem:
    rept-stat-ls
  3. Use local procedures to test the link facilities.

3.2.443 0534 - RTX is Prohibited

Traffic to the DPC through this exception route set is prohibited. Possible causes are as follows:

  • All routes in this exception route set are unavailable.

  • Adjacent point code link failures or non-adjacent failure exist in the route.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
*C  0044.0534 *C RTXN24    001-101-001   RTX is prohibited
                 ILSN=lsn012345

Alarm Level: Critical

Recovery

  1. Enter the following command using the DPC and RTX class/criterion specified from the output message to determine which linkset has a problem:
    rept-stat-rtx:dpc=<dpc>:<class>=<criterion>
  2. Enter the following command using the linkset name specified from the output of 1 to determine which link(s) could have a problem:
    rept-stat-ls
  3. Use local procedures to test the link facilities.

3.2.444 0535 - IP Connection Restricted

Although an IP connection has failed, some traffic is still flowing through an alternate SIGTRAN (SS7-over-IP) link.

The following two scenarios exist:

  • The SCTP association is established and the SCTP far-end is multi-homed and the Eagle determines one or more far-end IP destinations for the association are unreachable.

  • The SCTP association is established and the SCTP far-end is uni-homed and the SCTP near_end has an LHOST and an ALHOST configured.

Note:

IP Connection UAMs 0086 (Congested), 0535 (Restricted), and 0536 (Excess Retransmits) conditions can occur simultaneously. However, only one alarm per device can be displayed at a time. If two or more are present, the display of these alarms is prioritized as follows:
  1. 0086 - IP Connection Congested (MSUs are being dropped)
  2. 0536 - IP Connection Excess Retransmits (MSUs may be dropped. The EAGLE 5 ISS sustains a certain rate of dropped MSUs without triggering this alarm, then issues UIM 0536 when that rate is exceeded.)
  3. 0535 - IP Connection Restricted (MSUs are being transmitted at reduced rate. A path of a multi-homed association has failed. )
Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 31.3.0
*   0014.0535  *  IP7 assoc1        IP Connection Restricted

Alarm Level: Minor

Recovery

  1. Issue a pass command to determine which scenario is occurring. For example, for the association name (ANAME) ipl1301a at location 1301, enter the command: pass:loc=1301:cmd="sctp -a ipl1301a"
    Refer to the resulting output to troubleshoot the problem. 
    eagle10212 01-05-27 08:09:42 EST  UNKNOWN ??.?.?-63.18.0
    Aname             Local              Local   Remote             Remote
                      Address            Port    Address            Port
    ipl1301a          10.254.110.9       1301    10.254.110.2       1301

               Configuration                            State
            Retransmission Mode = LIN         State = OPEN
    Min. Retransmission Timeout = 120000      ULP association id = 0
    Max. Retransmission Timeout = 800000      Number of nets = 1
         Max. Number of Retries = 10          Inbound Streams = 2
         Min. Congestion Window = 3000        Outbound Streams = 2
                Inbound Streams = 2
               Outbound Streams = 2
             Checksum Algorithm = crc32c
           Send/Rcv Buffer Size = 204800
 
                                 Nets Data
         IP Address     10.254.110.2            State   Reachable
               Port     1301                  Primary   YES
                MTU     1500                     cwnd   3000
           ssthresh     204800                    RTO   120
                        Last Net Sent To = 10.254.110.2
                      Last Net Rcvd From = 10.254.110.2
                     Over All Eror Count = 0
                              Peers Rwnd = 204800
                                 My Rwnd = 204800
                              Max Window = 204800
                      Initial Seq Number = 11209
                 Next Sending Seq Number = 11728
                   Last Acked Seq Number = 11727
             Maximum Outbound Char Count = 204800
             Current Outbound Char Count = 0
                Number Unsent Char Count = 0
               Outbound Data Chunk Count = 0
                           Number Unsent = 0
                    Number To Retransmit = 0

                       ip datagrams rcvd = 10
      ip datagrams with data chunks rcvd = 10
                        data chunks rcvd = 10
                        data chunks read = 10
                           dup tsns rcvd = 0
                              sacks rcvd = 58
                     gap ack blocks rcvd = 0
                 heartbeat requests rcvd = 1392
                     heartbeat acks rcvd = 1412
                 heartbeat requests sent = 1412
                       ip datagrams sent = 2921
      ip datagrams with data chunks sent = 110
                        data chunks sent = 519
             retransmit data chunks sent = 1
                              sacks sent = 10
                             send failed = 0
                  retransmit timer count = 1
         consecutive retransmit timeouts = 0
     RTT between RMIN and RMAX inclusive = 0
                   RTT greater than RMAX = 0
                   fast retransmit count = 0
                        recv timer count = 4
                   heartbeat timer count = 1415
                        none left tosend = 0
                     none left rwnd gate = 0
                     none left cwnd gate = 0
                                 UNKNOWN = 1
  2. Determine why the other end is unreachable (for example, is a cable pulled?).
    All connections at the far end need to be reachable. After they are reachable, the alarm will clear – IP Connection Available.

    Refer to the SIGTRAN User Guide for additional troubleshooting information for SS7-over-IP connections.

  3. Reconfigure the association to be either both ends uni-homed or both ends multi-homed and make sure all connections are reachable.
  4. Errors (collisions, etc.) on the network interface?

    netstat -d 0/1t

  5. Far end reachable?

    ping

    traceroute

  6. Near end and far end use same SCTP CRC?

    netstat –p sctp

    rtrv-sg-opts

3.2.445 0536 - IP Connection Excess Retransmits

An SCTP association has excessive retransmissions. The retransmission errors may cause a connection to congest and fail in the presence of a sufficiently high load.

Note:

IP Connection UAMs 0086 (Congested), 0535 (Restricted), and 0536 (Excess Retransmits) conditions can occur simultaneously. However, only one alarm per device can be displayed at a time. If two or more are present, the display of these alarms is prioritized as follows:
  1. 0086 - IP Connection Congested (MSUs are being dropped)
  2. 0536 - IP Connection Excess Retransmits (MSUs may be dropped. The EAGLE 5 ISS sustains a certain rate of dropped MSUs without triggering this alarm, then issues UIM 0536 when that rate is exceeded.)
  3. 0535 - IP Connection Restricted (MSUs are being transmitted at reduced rate. A path of a multi-homed association has failed. )
Example 
   RLGHNCXA21W 06-12-07 12:01:43 EST  EAGLE 35.6.0 
*  1111.0536 * IP7 assoc1234567890         IP Connection Excess Retransmits

Alarm Level: Minor

Recovery

This error may be due to:

  • Misconfiguration or improper tuning of SCTP attributes to match the network conditions and traffic volumes

  • Packet loss

  • Excessive round-trip times

  • The receive buffer of the SCTP peer being full for extended periods (probes by Eagle SCTP to update window size may result in discards by the peer)

  • Timer settings that are too close in value

  1. Use the following pass commands to aid in determining the cause of the error:
    • sctp - gives how many retransmits are occurring
    • assocrtt - gives round-trip time information on a per-association basis
    • netstat - gives information on interface and per-protocol statistics (IP, SCTP and others)
    • ping - gives information on reachability and round-trip times
  2. If the error is due to configuration problems, correct the configuration.
  3. If the number of retransmissions is within expected values, the alarm threshold can be changed.

    Note:

    Changing the threshold does not affect link traffic, it only affects the alarm trigger level.
    1. Use the rtrv-assoc:aname=xxxx command to determine the current retransmit threshold (RTXTHR) value.
    2. Use the chg-assoc:aname=xxxx command to change the retransmit threshold (RTXTHR) value. Increasing the value will make the alarm less likely to occur.

    Refer to the Commands Manual for additional information.

  4. False retransmissions can occur if the RTO and SACK timer on either side of the connection are close in value. Refer to the SIGTRAN User Guide for more information about these timers.

3.2.446 0537 - Ethernet error threshold exceeded

There are two types of error that can generate UAM 0537:

  • Too much data received on the port.

  • An Ethernet interface experiences excessive errors at the physical layer, such as CRC or framing errors. This error is issued when the Ethernet statistics indicate errors occurring in any 15-second window. The alarm will clear when no errors have occurred in the previous 15 second window. In full-duplex mode, collisions will not be ignored but when configured for half-duplex mode, they will be ignored, since collisions are expected in half-duplex mode. When collisions occur repeatedly for the same packet more than 16 times then the “excess collisions” error count is pegged.

Example 
    RLGHNCXA21W 06-12-07 12:01:43 EST  EAGLE 35.6.0 
**  2315.0537 ** ENET 1201,B             Ethernet error threshold exceeded

Alarm Level: Major

Recovery

This error may be due to
  • Too much incoming data for the port to handle.
  • Faulty hardware; an EAGLE card, cable, or immediate IP switch/router.
  • Configuration mismatch problems; the following items should match on both ends:
    • Duplex
    • Speed
    • Ethernet type
    • Autonegotiate used on EAGLE or immediate IP switch/router (it is recommended to lock down your IP connection and do not use AUTONEGOTIATE)
  1. Perform this step if UAM 0537 is issued and the card boots; otherwise, skip to 2. If the card boots, the problem is probably too much incoming data on the port. Deactivate the port that has too much data using the dact-ip-lnk:loc=xxxx:port=xxxx command. Fix the network problem, then reactivate the port using the act-ip-lnk:loc=xxxx:port=xxxx.

    Note:

    An external hardware failure can cause IP overload on the port resulting in card boot. This problem is uncommon, but can occur when a problem with the customer network overwhelms the Ethernet port with a storm of traffic. The solution is to resolve the network problem. The dact-ip-lnk:loc=xxxx:port=xxxx also makes it possible to deactivate a bad Ethernet port so the other port can work.
  2. Use the following command to determine the current EAGLE configuration for the IP card reporting the errors.
    rtrv-ip-lnk:loc=xxxx

    wherexxxx is the card location identified in the error message.

  3. Use the netstat -d pass command to view the driver statistics for the local interface.

    • For the A ethernet interface, pass:loc=XXXX:cmd="netstat -d 0"

    • For the B ethernet interface, pass:loc=XXXX:cmd="netstat -d 1"

      where xxxx is the card location identified in the error message.

    Table 3-5 and Table 3-6 show the errors that show up on the DCM/DSM/EDCM/SSEDCM and E5-ENET/E5-ENET-B card types. Because the boards use different ethernet chips, the statistics that are available are different.

    Table 3-5 See (DCM/DSM/EDCM/SSEDCM) Ethernet Error Statistics

    Statistic Peg Description Half Duplex threshold count Full Duplex threshold count

    overflow

    Number of times the RX FIFO overflowed for frames received.

    1

    1

    CRC errors

    Number of frames received or discarded with CRC errors but no framing errors.

    1

    1

    short frame

    Number of frames received or discarded with carrier sense or RX-D.V. activity less than the “ShortEventMaxTime” (74-82 bit times).

    1

    1

    oversize frame

    Number of receive frames with greater than the 1518 byte maximum frame size.

    1

    1

    terminal count

    Receive DMA tried to receive more than the buffer capacity.

    1

    1

    excess collisions

    Number of times a frame collided 16 times without successful transmission.

    1

    1

    underflow

    Count of transmit underflow errors.

    1

    1

    CS error

    Number of times the transmitter had transmit data available and was ready to transmit but had to defer transmission due to carrier sense going HIGH. (Tx defer count in the See data sheet).

    n/a

    1

    alignment error

    Number of frames received or discarded with both a framing error and a CRC error.

    1

    1

    very long event

    Number of times the transmitter is active for greater than the MAU Jabber Lockup Protection Timer allows ([4-7ms] at 10 Mbit and [0.4 – 0.75ms] at 100 Mb.11 rxerrorNumber of times RXERR is asserted by the Ethernet PHY.

    1

    1

    num_job_q_full

    Number of times the net task job queue was full.

    1

    1

    rxerror

    Number of times RXERR is asserted by the Ethernet PHY.

    1

    		 1

    Table 3-6 GEI (E5-ENET/E5-ENET-B) Ethernet Error Statistics

    Statistic Peg Description Half Duplex threshold count Full Duplex threshold count

    crcerrs

    Number of receive frames with CRC errors.

    1

    1

    algnerrc

    Number of receive frames with alignment errors (the frame is not an integer number of bytes in length).

    1

    1

    rxerrc

    Number of frames received in which I_RX_ER was asserted by the PHY.

    1

    1

    ecol

    When 16 or more collisions have occurred on a frame, this register increments, regardless of the value of collision threshold.

    1

    1

    tncrs

    This register counts the number of successful frame transmissions in which the internal carrier sense signal from the PHY was not asserted within one slot time of start of transmission.

    n/a

    1

    tuc

    Transmit underrun count.

    1

    1

    rlec

    This register counts receive length error events.

    1

    1

    rnbc

    The number of times that frames were received when there were no available buffers in host memory to store those frames.

    1

    1

    ruc

    This register counts the number of received frames that passed address filtering, and were less than minimum size (64 bytes from <Destination Address> through <CRC>, inclusively), and had a valid CRC.

    1

    1

    roc

    This register counts the number of received frames with valid CRC field that passed address filtering, and were greater than maximum size.

    1

    1
  4. If the error is due to configuration problems, correct the configurationso the EAGLE and the IP switch/router match.
  5. If the configuration matches on both ends of the IP segment, replace the EAGLE card as identified in the error message.

    If replacing the card does not fix the issue, begin local procedures to verify the local IP segment.

3.2.447 0538 - Ethernet error threshold cleared

A problem with the Ethernet error threshold has been corrected.

Example
    RLGHNCXA21W 06-12-07 12:01:43 EST  EAGLE 35.6.0 
    2359.0538    ENET 1201,B             Ethernet error threshold cleared

Alarm Level: No alarm condition. The message is informational.

Recovery

This message indicates that a problem with the Ethernet error threshold has been cleared.

3.2.448 0539 - Ethernet Interface Down

An Ethernet interface is reporting that it is down.

Example
    RLGHNCXA21W 06-12-09 12:01:43 EST  EAGLE 40.1 
**  2315.0539 ** DLK 1201,B1  IPSG       Ethernet Interface Down

Alarm Level: Major

Recovery

An Ethernet interface is provisioned (rtrv-ip-lnk reports a non-zero IP address and the card on which the Ethernet resides is in service), but the interface is reporting that it is down.

If this UAM comes from the E5-OAM card and rept-stat-meas command output shows this E5-OAM card as Primary, a loss of reports on the measurement server is possible and MASP swap must be done manually.

If this UAM comes from the E5-OAM card, rept-stat-card shows this card is active, and rtrv-ctrl-feat command output shows the SNMP feature is activated, a loss of SNMP traps is possible. MASP swap must be done manually.

3.2.449 0540 - Ethernet Interface Up

A problem with the Ethernet interface has been corrected.

Example
    RLGHNCXA21W 06-12-09 12:01:43 EST  EAGLE 40.1 
    2359.0540    DLK 1201,B1  IPSG       Ethernet Interface Up

Alarm Level: No alarm condition. The message is informational.

Recovery

This message indicates that a problem with the Ethernet interface has been cleared.

3.2.450 0541 - MSU cksum Error Threshold Exceeded

One or more MSU checksum validation errors have been reported by a LIM or SCCP card during internal card integrity checks.

A LIM or SCCP card has reported a checksum validation failure for a MSU received from another card. The failure may be due to a hardware problem or other issue affecting the data transfer path on a particular card. It may indicate a problem with data corruption in an MSU sent to or received from another card.

The alarm is raised when a checksum validation failure occurs during internal card integrity checks. It remains active in the system until the Run-Time Diagnostic subsystem (RTD) statistics are reset and no further indications of MSU checksum validation failures are reported.

Example 
     RLGHNCXA21W 06-12-07 12:01:43 EST  EAGLE 35.6.0 
 *C  2315.0541 *C RTD SYSTEM              MSU cksum error threshold exceeded

Alarm Level: Critical

Recovery

  1. Issue the following command with no parameters to obtain the Run-Time Diagnostic subsystem (RTD) report.

    Note:

    Save all command outputs and reports obtained during this procedure to provide to unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
    rept-stat-rtd
    Following is an example output of the rept-stat-rtd command. 
    RLGHNCXA21W 06-12-07 12:01:43 EST EAGLE 35.6.0
    Retrieving data from the cards…

    RTD  SUBSYSTEM REPORT IS-ANR         Active     -----
    RTD  ALARM STATUS =  541 MSU cksum error threshold exceeded
        
              MSU Validation Statistics                        
            ==============================     
            Total Rx   Total Rx      Total      
    CARD    Error      Validated        Tx          
    1101         275         275       710
    1102           0         200       200
    1103           0         200      1000     
    1105           0        1360       275     
    1107           0         200       100     
    1108           0         100       100
  2. Record the timestamp reported for the alarm.
  3. Record the locations for cards reporting 1 or more errors in the Total Rx Error column.
  4. Determine if a single error or multiple errors were reported when the alarm occurred.

    • Multiple errors - if multiple cards report errors or a single card reports more than 1 error in the Total Rx Error column.

    • Single error - if only 1 card reports errors and the value in the Total Rx Error column is 1.

  5. Issue the following command for each card reporting 1 or more errors in uam-and-uim-troubleshooting-procedures1.html
    rept-stat-rtd:loc=xxxx

    Where xxxx is the card location determined from the output in uam-and-uim-troubleshooting-procedures1.html.

    The following is an example output of a card summary for card 1101. 
    rept-stat-rtd:loc=1101

    RLGHNCXA21W 06-12-07 12:01:43 EST EAGLE 35.6.0
    Retrieving data from card …

    CARD SUMMARY: 1101     Last Alarm Timestamp: 06-12-07 12:01:43
        
                          MSU Validation Statistics                       
                     =================================   
  
                     Total Rx     Total Rx    Total Tx     
    SRC/DEST            Error    Validated 
    CARD 
    1102                  100          100         100
    1103                    0            0           0       
    1105                   75           75         360        
    1107                  100          100         200      
    1108                    0           50          50
  6. Issue the following command to clear the RTD statistics
    rept-stat-rtd:reset=yes:force=yes
    Following is an example output of the command. 
    rept-stat-rtd:reset=yes

    RLGHNCXA21W 06-12-07 12:09:43 EST EAGLE 35.6.0
    Reset all RTD statistics sent to each card

COMMAND COMPLETE
  7. Issue the following command with no parameters to obtain the Run-Time Diagnostic subsystem (RTD) report.
    rept-stat-rtd
    Following is an example output of the command showing no alarms. 
    RLGHNCXA21W 06-12-07 12:10:43 EST EAGLE 35.6.0
    Retrieving data from the cards…

    RTD  SUBSYSTEM REPORT IS-NR         Active     -----
    RTD  ALARM STATUS =  No Alarms
        
              MSU Validation Statistics                        
            ==============================     
            Total Rx   Total Rx      Total      
    CARD    Error      Validated        Tx          
    1101           0         275       710
    1102           0         200       200
    1103           0         200      1000     
    1105           0        1360       275     
    1107           0         200       100     
    1108           0         100       100

    Note that the alarm did clear.

  8. Have all command outputs and reports obtained during this procedure available.

    This information will be used by unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA in determining the cause of the alarm and monitoring the system for errors.

  9. If RTD alarm status reported in step 7 indicates that the alarm did not clear, then proceed with below steps. Otherwise, continue to uam-and-uim-troubleshooting-procedures1.html
  10. Enter the rtrv-log:dir=bkwd:snum=1355:num=10 command to retrieve the 10 latest UIM 1355 records.
  11. Count the total number of times a particular card location appeared in the 10 UIM 1355 samples collected in the previous step, either as the source or as the destination location.
    For example, if card 1102 appeared as the source location in 4 UIM 1355 samples, and card 1102 appeared as the destination location in 6 UIM 1355 samples, then card 1102 appeared a total of 10 times in 10 UIM 1355 samples.
  12. Notify unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA of the occurrence of the alarm immediately if none of the locations appeared exactly 10 times. Otherwise, proceed with the next step.
  13. If more than one location appeared 10 times, go to step 18. If only one card location appeared 10 times, then go to the next step.
  14. Inhibit the card location that appeared 10 times.
  15. Enter the rept-stat-rtd:reset=yes:force=yes command to reset the RTD alarm.
  16. Enter the rept-stat-rtd command to verify the RTD alarm status.
  17. Notify unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA of the occurrence of the alarm immediately if the previous steps did not clear the RTD alarm. Otherwise, go to uam-and-uim-troubleshooting-procedures1.html.
  18. Inhibit the card location that appeared 10 times as the source card location in the UIM 1355 samples collected in uam-and-uim-troubleshooting-procedures1.html.
  19. Enter the rept-stat-rtd:reset=yes:force=yes command to reset the RTD alarm.
  20. Enter the rept-stat-rtd command to verify the RTD alarm status.
  21. If the previous steps did not clear the RTD alarm, allow the card location that was previously inhibited and bring it back in service.
  22. Inhibit the card location that appeared 10 times as the source card location in the UIM 1355 samples collected in uam-and-uim-troubleshooting-procedures1.html.
  23. Enter the rept-stat-rtd:reset=yes:force=yes command to reset the RTD alarm.
  24. Enter the rept-stat-rtd command to verify the RTD alarm status.
  25. Notify unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA of the occurrence of the alarm immediately if the previous steps did not clear the RTD alarm. Otherwise, go to the next step.
  26. Notify unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA of the occurrence of the alarm within 1 business day, along with captures covering the recovery steps performed and all necessary system logs (UIM, UAM, seculog, trouble, obit, etc.) covering the incident.

3.2.451 0542 - MSU cksum error threshold cleared

The MSU checksum threshold exceeded alarm has been corrected.

Example
    RLGHNCXA21W 06-12-07 12:01:43 EST  EAGLE 35.6.0 
    2359.054238    RTD SYSTEM            MSU Cksum error threshold cleared

Alarm Level: No alarm condition. The message is informational.

Recovery

This message indicates that the MSU checksum threshold exceeded alarm has been cleared.

3.2.452 0543 - VLR Dynamic Learning is suspended

This alarm occurs if only one SFAPP card is present in the system and the mode parameter "is not set to OFF" in the SFAPPOPTS table.

Example 

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0543    SFAPP SYSTEM                VLR Dynamic Learning is suspended

Alarm Level: Critical

Recovery

  1. Place more than one SFAPP card IS-NR.

3.2.453 0544 - VLR Dynamic Learning Started

This alarm occurs if more than one SFAPP card is present in the system and the mode parameter "is not set to OFF" in the SFAPPOPTS table.

Example 

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0544    SFAPP SYSTEM                VLR Dynamic Learning Started

Alarm Level: Normal.

Recovery

None. This alarm is a corrective alarm.

3.2.454 0545 - SEAS Terminal Available

This message indicates a problem with SEAS system has been corrected.

Example 
    RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 37.5.0
*   0043.0545 ** TERMINAL   17          SEAS Terminal Available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.455 0546 - SEAS Terminal Unavailable

This message indicates that the EAGLE 5 ISS system is unable to communicate with the SEAS subsystem.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 37.5.0
*   0043.0546 ** TERMINAL   17          SEAS Terminal Unavailable

Alarm Level: Major

Recovery

  1. Enter the following command to determine the status of the SEAS terminal(s):
    rept-stat-seas
    Following are some examples of possible outputs:
    • Both Terminals Down (Duplex) 
      > rept-stat-seas 

    tekelecstp 20-01-16 12:50:00 GMT  UNKNOWN ??.?.?-58.32.0 
    rept-stat-seas 
    Command entered at terminal #25. 
; 

Command Accepted - Processing 
    tekelecstp 20-01-16 12:50:00 GMT  UNKNOWN ??.?.?-58.32.0 
    SEAS SYSTEM                                 PST           SST       AST 
    ------------------------------------------------------------------------- 
                                                OOS-MT        Fault     ----- 

    ALARM STATUS = *C 0349 SEAS unavailable 

    TERM           IPADDR           PORT        PST           SST       AST 
    ------------------------------------------------------------------------- 
    26             192.168.63.235   1600        OOS-MT        Disc      ----- 

    ALARM STATUS = ** 0546 SEAS Terminal unavailable 

    24             192.168.63.235   1700        OOS-MT        Disc      ----- 

    ALARM STATUS = ** 0546 SEAS Terminal unavailable 


    Command Completed.
    • One Terminal Up (Duplex) 
      > rept-stat-seas 

    tekelecstp 20-01-16 12:50:00 GMT  UNKNOWN ??.?.?-58.32.0 
    rept-stat-seas 
    Command entered at terminal #25. 
; 

Command Accepted - Processing 
    tekelecstp 20-01-16 12:50:00 GMT  UNKNOWN ??.?.?-58.32.0 
    SEAS SYSTEM                                 PST           SST       AST 
    ------------------------------------------------------------------------- 
                                                IS-ANR        Restrict  ----- 

    ALARM STATUS = ** 0348 SEAS is at min service limit 

    TERM           IPADDR           PORT        PST           SST       AST 
    ------------------------------------------------------------------------- 
    26             192.168.63.235   1600        IS-NR         Active    ----- 

    ALARM STATUS = No Alarms. 

    24             192.168.63.235   1700        OOS-MT        Disc      ----- 

    ALARM STATUS = ** 0546 SEAS Terminal unavailable 


    Command Completed.
    • One Terminal Down (Simplex) 
      > rept-stat-seas 

    tekelecstp 20-01-16 12:50:00 GMT  UNKNOWN ??.?.?-58.32.0 
    rept-stat-seas 
    Command entered at terminal #25. 
; 

Command Accepted - Processing 
    tekelecstp 20-01-16 12:50:00 GMT  UNKNOWN ??.?.?-58.32.0 
    SEAS SYSTEM                                 PST           SST       AST 
    ------------------------------------------------------------------------- 
                                                OOS-MT        Fault     ----- 

    ALARM STATUS = *C 0349 SEAS unavailable 

    TERM           IPADDR           PORT        PST           SST       AST 
    ------------------------------------------------------------------------- 
    26             192.168.63.235   1600        OOS-MT        Disc      ----- 

    ALARM STATUS = ** 0546 SEAS Terminal unavailable 


    Command Completed.
    Refer to the Commands Manual to interpret the output.
  2. Verify that the IP addresses and ports are correct.

    Correct any discrepancy found.

  3. Check the physical connections.
    See the Installation Manual for more information about these system components. If the connections are firmly seated.
  4. Check for any fuse alarms on the Fuse and Alarm Panel in the frame.
  5. Check that all terminals for the IPSM card are inhibited before inhibiting the card for replacement.
  6. Replace the E5-IPSM card. Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.456 0547 - Service degraded

One or more SS cards goes out of service in (N or N+1) configuration or not IS-NR.

Example 
    RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 46.0.0
0056.0547      APSS   Service degraded

Alarm Level: Major.

Recovery

  1. Restore the one or more SS out of service cards in (N or N+1) configuration or not IS-NR.

3.2.457 0548 - GTT HexTree DB corrupted. TPS derated

This message indicates there is a memory corruption in the HexTree DB that is affecting the lookup of GTT translations.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  0002.0548 ** CARD 1203               GTT HexTree DB corrupted. TPS derated

Alarm Level: No alarm condition. The message is informational only.

Recovery

Reboot the card or turn OFF GTTHITPS.

3.2.458 0549 - GTT HexTree DB incoherent. TPS derated

This message indicates the HexTree DB could not be updated successfully on the RADB command and the DB is incoherent..

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  0002.0549 ** CARD 1203               GTT HexTree DB incoherent. TPS derated

Alarm Level: No alarm condition. The message is informational only.

Recovery

Reboot the card or turn OFF GTTHITPS.

3.2.459 0550 - GTT HexTree DB alarm cleared

This message indicates the HexTree DB error has been cleared.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0550    CARD 1203               GTT HexTree DB alarm cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.460 0551 - V-Flex Subsystem is not available

No SCCP cards have a V-Flex status of Active. (All SCCP cards are OOS or loading)

Example
     RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 37.6.0
 *C  0056.0551 *C VFLEX SYSTEM            VFLEX Subsystem is not available

Alarm Level: Critical.

Recovery

  1. The V-Flex feature must be turned on and activated.

3.2.461 0552 - V-Flex Subsystem is disabled

All IS-NR SCCP cards have V-Flex status of Offline (with at least 1 card IS-NR). INH-MAP-SS command has been executed.

Example
     RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 37.6.0
 *C  0056.0552 *C VFLEX SYSTEM            VFLEX Subsystem is disabled

Alarm Level: Critical.

Recovery

  1. The V-Flex feature must be enabled and turned on.

3.2.462 0553 - VFLX Subsystem normal, card(s) abnormal

One Service Module card has V-Flex status of Active and there are 1 or more cards with an V-Flex status other than Active (a status not equal to OOS (out of service), loading or Offline).

Example 
    RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 37.6.0
*C  0056.0553 *C VFLEX SYSTEM            VFLX Subsystem normal, card(s) abnormal

Alarm Level: Minor.

Recovery

  1. No action necessary.

3.2.463 0554 - V-Flex Subsystem is available

All Service Module cards are IS-NR and have an V-Flex status of Active.

Example 
     RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 37.6.0
*C  0056.0554 *C VFLEX SYSTEM            VFLEX VFLEX Subsystem is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. No action necessary.

3.2.464 0555 - V-Flex Subsystem is removed

Last Service Module card was deleted.

Example 
    RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 37.6.0
*C  0056.0555 *C VFLEX SYSTEM            VFLEX Subsystem is removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. No action necessary.

3.2.465 0556 - V-Flex Subsystem degraded, card(s) abnormal

One or more V-Flex cards goes out of service in (N or N+1) configuration or not IS-NR.

Example 
    RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 46.0.0
0056.0556      VFLEX Subsystem   VFLX Subsystem degraded, cards abnormal

Alarm Level: Major.

Recovery

  1. Restore the one or more V-Flex out of service cards in (N or N+1) configuration or not IS-NR.

3.2.466 0560 - REPT-LKSTO: Link Set Restricted

This message indicates a linkset has been restricted.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 38.0.0
*  0014.0560  *   LSN a54646     REPT-LKSTO: link set restricted

Alarm Level: Minor

Recovery

  1. Verify the link status using the rept-stat-slk command.

    For example, enter:

    rept-stat-slk:loc=1203:link=b
  2. Check the UNAVAIL REASON field in the output of the rept-stat-slk command.
    UNAVAIL REASON codes:
    FC
    The signaling link is unavailable because of false congestion.
    FL
    The signaling link has a fault.
    NA
    The signaling link is not aligned.
    LI
    The signaling link has been inhibited locally
    LB
    The signaling link has been blocked locally.
    RB
    The signaling link has been blocked remotely.
    RD (xx.xxx)
    The signaling link is unavailable because of a restart delay to prevent signaling link oscillation. The number in parentheses indicates the amount of time, in seconds, remaining in the restart delay period. The link is restarted automatically after this amount of time has elapsed.
    RI
    The signaling link has been inhibited remotely.
  3. If the UNAVAIL REASON indicates an alignment problem or fault, activate a loopback using the act-lpb command, or use a physical loopback.
    (For a V.35, you must use an appropriate physical V.35 loopback.) If the signaling link aligns, contact the far-end to correct the problem.
  4. If the UNAVAIL REASON still indicates an alignment problem or fault, check the status of the card by entering the rept-stat-card command for the specified card.
  5. If the rept-stat-card command indicates a problem with the card, reset the card by entering the init-card command with the specified card location.
    If the card still does not align, try first reseating the card, then replacing the card. Refer to the Maintenance Manual for card removal/replacement procedures.
  6. If the UNAVAIL REASON indicates a locally inhibited link, enter the unhb-slk command with the specified card location.
  7. If the UNAVAIL REASON indicates a locally blocked link, enter the ublk-slk command with the specified card location.
  8. If the signaling is blocked or inhibited remotely, contact the far-end to place the link in-service.

3.2.467 0561 - Can't Establish Hi Bit Rate; All HW OK

This message is issued if the system cannot establish high bit rate operation when it is equipped with HIPR2 cards at all MUX locations and the HIPR2 High Rate Mode feature is ON.

Note:

This UAM might appear during transition phase when the HIPR2 High Rate Mode feature status has changed, but eventually it will be cleared if high bit rate is established on both IMT buses.
Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
*C  5025.0561 *C SYSTEM            Can't establish Hi Bit rate;All HW OK

Alarm Level: Critical

Recovery

  1. Verify the status of the cards using the command: rept-stat-mux.
    Example of the output: 
    CARD   TYPE       PST            SST        AST       BITRATE   BITRATE
                                                      (OPER)    (ACT)
------------------------------------------------------------------------
1109   HIPR2      IS-ANR         Restrict   -----     HIGH      LOW
1110   HIPR2      IS-NR          Active     -----     HIGH      HIGH
1209   HIPR2      IS-ANR         Restrict   -----     HIGH      LOW
1210   HIPR2      IS-NR          Active     -----     HIGH      HIGH
1309   HIPR2      IS-ANR         Restrict   -----     HIGH      LOW
1310   HIPR2      IS-NR          Active     -----     HIGH      HIGH
Command Completed.
  2. Replace any faulty HIPR2 cards with a new HIPR2 card.
    Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures for information on replacing the HIPR2 cards.
  3. If the alarm does not clear, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.468 0562 - High Bit rate established

This message indicates that the alarm condition specified by the previous alarm has been cleared.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
0590.0562    SYSTEM               High Bit rate established

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.469 0563 - IMT Bit rate mismatch detected

This message indicates that the the IMT Bus A and B are operating at different bit rates. This can occur if the BERT Test fails for only one bus, or if some of the HIPR2 cards have been replaced with HMUX/HIPR cards after the HIPR2 High Rate Mode feature was turned ON.

Note:

This UAM might appear during transition phase when the HIPR2 High Rate Mode feature status has changed, but eventually it will be cleared if high bit rate is established on both IMT buses.
Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
**  0590.0563 ** IMT SYSTEM        IMT Bit rate mismatch detected

Alarm Level: Major

Recovery

  1. Verify the card status. Enter this command: rept-stat-mux.
    Example of the output:
        CARD   TYPE       PST            SST        AST       BITRATE   BITRATE
                                                           (OPER)    (ACT)
    ------------------------------------------------------------------------
    1109   HIPR2      IS-ANR         Restrict   -----     HIGH      LOW
    1110   HIPR2      IS-NR          Active     -----     HIGH      HIGH
    1209   HIPR2      IS-ANR         Restrict   -----     HIGH      LOW
    1210   HIPR2      IS-NR          Active     -----     HIGH      HIGH
    1309   HIPR2      IS-ANR         Restrict   -----     HIGH      LOW
    1310   HIPR2      IS-NR          Active     -----     HIGH      HIGH
    Command Completed.
  2. Enter the command to verify the IMT status: rept-stat-imt.
    Example of the output: 
    
     IMT   PST              SST          AST
      A    IS-ANR          Restrict     -----
      ALARM STATUS       = No alarms

     IMT   PST             SST         AST
     B     IS-NR           Active      -----
     ALARM STATUS       = No alarms

    Command Completed.
  3. Replace the faulty HIPR2 card or replace the HMUX/HIPR cards with HIPR2 cards.

3.2.470 0564 - IMT Bit rate mismatch cleared

This message indicates that the alarm condition specified by the previous alarm has been cleared.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
  0014.0564       IMT SYSTEM      IMT Bit rate mismatch cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.471 0565 - ATINPQ Subsystem is Not Available

The ATINP subsystem is not available. There are no IS-NR SCCP cards associated with this ATINP subsystem. The ATINP subsystem was not taken off-line via command.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
*C  0056.0565 *C ATINP SYSTEM           ATINPQ Subsystem is not available

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  2. Enter the following command to move the SCCP cards to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT-DSBLD SCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  4. Verify the SCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.472 0566 - ATINPQ Subsystem is disabled

The ATINP subsystem has been manually disabled using the inh-map-ss command.

Example 
    RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
*C  0056.0566 *C ATINP SYSTEM           ATINPQ Subsystem is disabled

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the ATINP subsystem cards:
    rept-stat-mps
  2. Enter the following command to to reserve the subsystem number and to change the state of the ATINP subsystem status to on-line:
    ent-ss-appl:appl=ATINPQ:ssn=xx:stat=online

    where xx is primary subsystem number.

  3. Enter the following command to activate the ATINP subsystem and to bring it on-line:
    alw-map-ss:ssn=xx

    where xx is primary subsystem number.

  4. Enter the following command to verify the status of the ATINP subsystem:
    rept-stat-mps

3.2.473 0567 - ATINPQ Subsystem Normal, Card(s) Abnorml

One SCCP card has ATINP status of Active and there are one or more cards with an ATINP status other than Active.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
*   0056.0567 *  ATINP SYSTEM           ATINPQ Subsystm normal, card(s) abnorml

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  2. Enter the following command to move the SCCP card to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT- DSBLDSCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-mps
  4. Verify the SCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.474 0568 - ATINPQ Subsystem is available

This message indicates that a problem with the ATINP subsystem has been corrected.

Example 
    RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
    0056.0568    ATINP SYSTEM           ATINPQ Subsystem is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.475 0569 - ATINPQ Subsystem is Removed

The ATINP subsystem is not fully equipped. There are no SCCP cards configured with this ATINP subsystem.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 39.2.0
    0056.0569    ATINP SYSTEM           ATINPQ Subsystem is removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the SCCP hardware.

Configure the ATINP system with SCCP cards. Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.476 0570 - Incompatible Flash Image for sys rel

The new card inserted into system with a flash image is not compatible with the system release. The card is auto-inhibited. A manual flash download is required.

Example 
isht01 09-07-21 09:19:16 EST  EAGLE5 41.1  
  
ALARM STATUS       = **  0570 Incompatible flash image for sys rel
   99  Inserted H/W is not compatible with the provisioned slot
                   HW VERIFICATION CODE: 98

Alarm Level: Major

Recovery

  1. Enter the command to load and activate the approved GPL onto the inhibited card:
    flash-card:code=appr:loc=xxxx:force=yes

    where xxxx is the card location used in the previous step. The optional force=yes is used to force the command to work on an IS-NR card. Links provisioned on the card are inhibited during command execution. The card and inhibited links are restored to their previous state when the command is completed.

    Example of the output using card location 1112: 
    Command Accepted - Processing

    tekelecstp 18-01-18 16:06:22 MST  EAGLE 46.5.1.5.0-73.3.0
    flash-card:code=appr:force=yes:loc=1112
    Command entered at terminal #1.
;

    tekelecstp 18-01-18 16:06:55 MST  EAGLE 46.5.1.5.0-73.3.0
    Flash Card: FLASH GPL required to be downloaded on card 1112
    BLMCAP    : Running version 143-001-000  Expected version 143-002-000

;
    tekelecstp 18-01-18 16:07:14 MST  EAGLE 46.5.1.5.0-73.3.0
    Flash Card: Downloading BLMCAP on card 1112
    Flash Card: Card(s) will reset after the flash GPL download.

;
    tekelecstp 18-01-18 16:07:56 MST  EAGLE 46.5.1.5.0-73.3.0
    Flash Card: Activating BLMCAP on card 1112

;
    tekelecstp 18-01-18 16:08:25 MST  EAGLE 46.5.1.5.0-73.3.0
    Flash Card: Card 1112 flash activation complete.
;
    Flash Card: Activating links on card 1112. 
;
    tekelecstp 18-01-11 16:09:11 EST  EAGLE5 39.0.0
    Command Completed.
  2. Enter the command to put the card that was inhibited in 1 back into service:
    alw-card:loc=xxxx

    where xxxx is the card location used in 1.

    Example of the output: 
    RLGHNCXA03W  00-06-05  11:11:28 EDT  EAGLE 35.0.0
Card has been allowed.

    Note:

    Allow the card to run for 5 minutes before continuing.
  3. Enter the command to activate all links on the card.
    act-slk:loc=xxxx:link=y

    where xxxx is the card location identified in the output and y is the link.

  4. Enter the command to verify all links on the card are active.
    rept-stat-slk:loc=xxxx:link=y

    where xxxx is the card location identified in the output and y is the link

  5. Enter the command to verify the approved GPLs match the running GPLs:
    rept-stat-gpl:gpl=xxxxxxx

    where xxxxxxx is the GPL identified in the output.

  6. If the GPLs match, you have completed this procedure.

    If the GPLs do not match, continue with the following step.

  7. Repeat this procedure for each card that shows ALM in the output.
  8. If the same card shows in an alarm condition after executing the procedure, please contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.477 0571 - Sentinel Socket is Inactive

The EAGLE 5 ISS - Sentinel socket connection is inactive. Any of the following conditions may be a cause.
  • Turned off scopy bit through chg-eiscopy command if it is already on
  • Lost connection with Sentinel/IMF server
  • Link being monitored is deleted
  • Adaptor type is changed to non-M2PA on the IPLIM card connected to IMF/sentinel server using chg-assoc/chg-appl-sock
  • Internal problem occured at the LIM card hosting the corresponding link
Example 
RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 38.0.0
*   0100.0571 *  SLK 1201,A   lsn123     Sentinel Socket is inactive

Alarm Level: Minor

Recovery

  1. Check the physical connectivity to the Sentinel/IMF server and application status running at the Sentinel/IMF servers.
    Correct any physical connection discrepancy found.
  2. If the physical connectivity is good, then there may be an internal problem at the LIM card hosting the corresponding link. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.478 0572 - Sentinel socket is active

A problem with the EAGLE 5 ISS - Sentinel socket has been corrected and the socket is active.

Example
    RLGHNCXA21W 00-12-07 12:01:43 EST  EAGLE 38.0.0
    0100.0572    SLK 1201,A   lsn123     Sentinel Socket is active

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. No action neccessary

3.2.479 0573 - BERT Test Failed

This message is displayed when the BERT diagnostic test, which is initiated by the HIPR2 card as a part of the IMT bus alignment process, has failed. This message may indicate that a HIPR2 card has failed; it may also indicate that there is a bad high rate Fibre-Channel cable, or that the high rate Fibre-Channel cables have not been installed.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
**  0590.0573 ** Card 1109         BERT Test Failed

Alarm Level: Major

Recovery

  1. Determine the status of the HIPR2 cards using the command: rept-stat-mux.
    Replace any faulty HIPR2 card with a new HIPR2 card.
  2. Verify that the high rate Fibre-Channel cables have been installed.
  3. Inspect the cables and verify that the cable connections are secure.
  4. The BERT test will run again during the bus alignment. Once the BERT Test is successful, the alarm will be cleared.
  5. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA for more information.

3.2.480 0574 - BERT Test failure cleared

This message indicates that the alarm condition specified by the UAM 0573 (BERT Test Failed) has been cleared.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
    0590.0574  Card 1109           BERT Test failure cleared

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.481 0575 - Card type not HIPR2

This message is displayed when the HIPR2 High Rate Mode feature is ON and a non-HIPR2 card has replaced the HIPR2 card.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST  EAGLE 41.1.0
**  0590.0575 ** Card 1309         Card type not HIPR2

Alarm Level: Major

Recovery

This alarm will be cleared when:
  1. The HIPR/HMUX card is replaced with a HIPR2 card.
  2. The HIPR2 High Rate Mode feature is turned OFF.

3.2.482 0576 - All FC Network Unavailable

This indicates that the FC Network is down on all FC enabled cards.

Example 
RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
**  0100.0576 ** FCS                    All FC Network Unavailable

Alarm Level: Major

Recovery

Re-association should take place automatically.

If it does not, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.483 0577 - All FC cards removed

This indicates that all Fast Copy enabled cards have been deleted from the system.

Example 
    RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
    0101.0577    FCS                    All FC cards removed

Alarm Level: None

Recovery

No action necessary.

3.2.484 0578 - FC System is Available

This indicates that the FC Network is available on any of the FC enabled cards.

Example 
     RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
     0101.0578    FCS                    FC System is Available

Alarm Level: None

Recovery

No action necessary.

3.2.485 0579 - FC Network Unavailable

This indicates the FC enabled card is unable to reach any XMF server.

Example 
RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
*   0107.0579 *      Card 1104           FC Network Unavailable

Alarm Level: Minor

Recovery

Re-association should take place automatically.

If it does not, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.486 0580 - FC Network Available

This indicates that FC enabled card is able to reach any XMF server.

Example 
     RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
     0108.0580        Card 1104           FC Network Available

Alarm Level: None

Recovery

No action necessary.

3.2.487 0581 - Loss of heartbeat

This indicates that an FC enabled card did not receive a heartbeat message from XMF server before the expiry of RCV heartbeat timer.

Example 
     RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
 *   0108.0581 *      Card 1104           Loss of heartbeat

Alarm Level: Minor

Recovery

No action necessary.

  1. Inspect the backplane for loose dongle cables (P/N 830-1343-0X).
  2. Verify the RJ45 cables are connected completely on the backplane.

3.2.488 0582 - Heartbeat Available

This indicates that FC enabled card receives heartbeat from the XMF.

Example 
     RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
     0107.0582        Card 1104           Heartbeat Available

Alarm Level: None

Recovery

No action necessary.

3.2.489 0583 - Unexpected SAM Received

This indicates that an FC enabled card received an erroneous SAM from IMF.

Example 
      RLGHNCXA21W 00-12-09 12:01:43 EST EAGLE 40.1
    * 0102.0583 * SLK 1201,A lsnabcde Unexpected SAM Received
             REASON: Mismatched Fast Copy Network Addresses

Alarm Level: Minor

Recovery

No action necessary.

3.2.490 0584 - Expected SAM Received

This indicates that FC enabled card received a valid SAM on a link from DAS.

Example 
    RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
    0102.0584    SLK 1201,A   lsnabcde   Expected SAM Received

Alarm Level: None

Recovery

No action necessary.

3.2.491 0588 - FC Port De-activated

This indicates that FC enabled Card CPU Idle reached Threshold level 1 and deactivated the FCS IP port (see Example 1) or if negotiation for data rate and traffic flow do not result in 100 Mbps and full duplex mode for the FC port (see Example 2).

Example 1 
    RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1
**  0705.0588 ** DLK 1106,B1  IPSG       FC Port De-activated
                 REASON: Onset of CPU Congestion
Example 2 
    RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
**  0772.0588 ** DLK 1106,B1  IPSG       FC Port De-activated
                 REASON: Auto-Neg Fails

Alarm Level: Major

Recovery - Onset of CPU Congestion

No action necessary.

Recovery - Auto-Negotiation Fails

Corrective action needs to be taken at the switch to auto-negotiate successfully with Fast Copy Ports, for data rate and traffic as 100 Mbps/Full Duplex.

3.2.492 0589 - FC Port Activated

This indicates that FCS IP Port on FC Enabled card CPU Idle reached the Abatement Level.

Example 
    RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
    2359.0589    DLK 1201,B1  IPSG       FC Port Activated

Alarm Level: None

Recovery

No action necessary.

3.2.493 0590 - Fast Copy Application De-activated

This UAM can be raised under the following conditions:
  • Fast Copy CPU Load Shedding condition or Auto-Negotiation failure on both the FC Ports
  • One FC port is down due to network failure and another one is down either due to CPU load-shedding or Auto-Negotiation failure
  • Fast Copy CPU Load Shedding condition on one FC Port and Auto-Negotiation failure on another FC Port
Example 1 
    RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1
*   0642.0590  * CARD 1105 IPSG          Fast Copy Application De-activated
                 REASON:  CPU Threshold Exceeded
Example 2 
    RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1
*   0587.0590  * CARD 1106 IPSG          Fast Copy Application De-activated
                 REASON:  Auto-Neg Fails

Alarm Level: Minor

Recovery - CPU Threshold Exceeded

No action necessary.

Recovery - Auto-Negotiation Fails

Corrective action needs to be taken at the switch to auto-negotiate successfully with Fast Copy Ports, for data rate and traffic as 100 Mbps/Full Duplex.

3.2.494 0591 - Fast Copy Application Activated

This indicates that FC enabled Card CPU Idle reached abatement level and activated the Fact Copy application.

Example 
    RLGHNCXA21W 00-12-09 12:01:43 EST  EAGLE 40.1 
    0107.0591        Card 1104           Fast Copy Application Activated

Alarm Level: None

Recovery

No action necessary.

3.2.495 0592 - AIQ Subsystem is Not Available

The AIQ subsystem is not available. There are no IS-NR SCCP cards associated with this AIQ subsystem. The AIQ subsystem was not taken off-line via command.

Example 
RLGHNCXA21W 00-02-10 12:01:43 EST EAGLE 42.0.0
*C  0135.0592 *C LSS AIQ      Subsystem is not available

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-sccp
  2. Enter the following command to move the SCCP cards to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT-DSBLD SCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-sccp
  4. Verify the VSCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.496 0593 - AIQ: Subsystem is Disabled

The AIQ subsystem has been manually disabled using the inh-map-ss command.

Example 
RLGHNCXA21W 00-02-10 12:01:43 EST EAGLE 42.0.0
*C  1571.0593 *C LSS AIQ      Subsystem is disabled

Alarm Level: Critical

Recovery

  1. Enter this command to verify the status and location of the AIQ subsystem cards:
    rept-stat-sccp
  2. Enter this command to to reserve the subsystem number and to change the state of the AIQ subsystem status to on-line:
    ent-ss-appl:appl=aiq:ssn=xx:stat=online

    where xx is primary subsystem number.

  3. Enter this command to change the state of the AIQ subsystem to on-line:
    alw-map-ss:ssn=xx

    where xx is primary subsystem number.

  4. Enter this command to verify the status of the AIQ subsystem:
    rept-stat-sccp

3.2.497 0594 - AIQ: Subsystem Normal, Card(s) Abnormal

One or more of the SCCP cards do not have an ACTIVE status.

Example 
RLGHNCXA21W 00-02-10 12:01:43 EST EAGLE 42.0.0
*   0212.0594  * LSS AIQ      Subsystem normal, card(s) abnormal

Alarm Level: Minor

Recovery

  1. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-sccp
  2. Enter the following command to move the SCCP card to an ACTIVE status if loading is successful:
    rst-card:loc=xxxx

    where xxxx is the location of the OOS-MT-DSBLD SCCP card(s) identified in 1.

  3. Enter the following command to verify the status and location of the subsystem cards:
    rept-stat-sccp
  4. Verify the SCCP card(s) reset in 2 are IS-NR.
    If not, reseat the card(s).
  5. If any card(s) remain OOS-MT, replace the card(s).
    Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.498 0595 - AIQ: Subsystem is available

This message indicates that a problem with AIQ system has been corrected.

Example 
RLGHNCXA21W 00-02-10 12:01:43 EST EAGLE 42.0.0
    0144.0595    LSS AIQ      Subsystem is available
;

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected. No further action is necessary.

3.2.499 0596 - AIQ: Subsystem is Removed

The AIQ subsystem is not fully equipped. There are no SCCP cards configured with this AIQ subsystem.

Example 
RLGHNCXA21W 00-02-10 12:01:43 EST EAGLE 42.0.0
    0144.0595    LSS AIQ      Subsystem is removed

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify the SCCP hardware.
  2. Configure the AIQ system with SCCP cards. Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.500 0597 - FC System is Deactivated

This alarm indicates that the Fast Copy application is de-activated on all FC Capable cards.

Example 
    RLGHNCXA21W 09-08-19 12:01:43 EST  EAGLE 41.1
*   0302.0597  * FCS                     FC System is Deactivated

Alarm Level: Minor

Recovery

No action necessary.

3.2.501 0598 - Subsystem degraded, card(s) abnormal

One or more SS cards goes out of service in (N or N+1) configuration or not IS-NR.

Example 
    RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 46.0.0
0056.0598    Subsystem   Subsystem degraded, cards abnormal

Alarm Level: Major.

Recovery

  1. Restore the one or more SS out of service cards in (N or N+1) configuration or not IS-NR.

3.2.502 0599 - RW Time Mismatch

This alarm indicates that there is a mismatch of RW Timing.

Example 
tklc1170501 22-03-25 03:09:33 EST EAGLE 47.0.0.0.0-78.38.0
        *  0277.0599 * CARD 2307 SS7HC69      RW Time Mismatch

Alarm Level: Minor

Recovery

Remove the alarm from the system, when the time between EAGLE and IMF synchronizes.

3.2.503 0619 - SIP SYSTEM is Not Available

This alarm indicates SIP feature is not ON and System has no SIP card that is Active/IS-NR.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
*C  0002.0619 *C SIP SYSTEM             SIP System is not available

Alarm Level: Critical

Recovery

  1. Enter the following command to verify the status and location of the SIP card: rept-stat-sip.
  2. Enter the following command to move the SIP card to an ACTIVE status if loading is successful: rst-card:loc=xxx where xxxx is the location of the SIP card identified in 1.
  3. Enter the following command to verify the status and location of the SIP card: rept-stat-sip.
  4. Verify the SIP card reset in 2 are ACTIVE/IS-NR.
  5. If the SIP card remains INACTIVE, replace the card. Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.504 0620 - SIP SYSTEM is available

This message indicates that at least one SIP card is ACTIVE/IS-NR.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0620    SIP SYSTEM             SIP SYSTEM is available

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.2.505 0622 - SIP Threshold - Level 1

This UAM is generated when the EAGLE detects SIP Congestion Level 1 based on the threshold set in TH-ALM table for the SIP card.

Example 
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0622    SIP SYSTEM             SIP Threshold - Level1

Alarm Level: Minor

Recovery

  1. Use rept-stat-sip command to determine the status of the SIP SYSTEM. If the TPS is beyond the allowed limit, decrease the TPS.
  2. Follow the procedures to add more SIP cards to handle the increased SIP traffic.

3.2.506 0623 - SIP Threshold - Level2

This UAM is generated when the EAGLE 5 detects SIP Congestion Level 2 based on the threshold set in TH-ALM table for the SIP card.

Example 
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0623    SIP SYSTEM             SIP Threshold - Level2

Alarm Level: Major

Recovery

  1. Use rept-stat-sip command to determine the status of the SIP SYSTEM. If the TPS is beyond the allowed limit, decrease the TPS.
  2. Follow the procedures to add more SIP cards to handle the increased SIP traffic.

3.2.507 0624 - SIP Threshold Condition Cleared

This UAM is generated when the SIP Threshold congestion is cleared.

Example 
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0624    SIP SYSTEM             SIP Threshold Condition Cleared

Alarm Level: No Alarm Condition.

Recovery

This alarm indicates a previous fault has been corrected.

No further action is necessary.

3.2.508 0625 - SIP SYSTEM Normal, Card(s) Abnormal

This message indicates that the number of active SIP cards (i.e., in IS-NR state) is less than half of the configured SIP cards.

Example 
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0625    SIP SYSTEM             SIP SYSTEM normal, card(s) abnormal

Alarm Level: NO alarm condition. The message is informational only.

Recovery

  1. Enter the following command to determine which SIP cards are out of service: rept-stat-sip.
  2. Use the init-card command to reinitialize any SIP cards OOS-MT.
  3. Use the rept-stat-sip command again to determine if the card(s) have returned to IS-NR. If not, reseat the card(s).
  4. If the SIP card remains OOS-MT, replace the card(s). Refer to the Maintenance Manual for card removal/replacement procedures.

3.2.509 0626 - SIP Threshold Level Critical

This message indicates that there is a Congestion Level of Critical based on the threshold set in TH-ALM table for the SIP card.

Example 
   1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    0002.0626    SIP SYSTEM             SIP Threshold Level Critical

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Use rept-stat-sip command to determine the status of the SIP SYSTEM. If the TPS is beyond the allowed limit, decrease the TPS.
  2. Follow the procedures to add more SIP cards to handle the increased SIP traffic.

3.2.510 0627 - SFLOG SYSTEM is not available

This message indicates the system has no SFLOG card that is Active/IS_NR status.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    *C  yyyy.0627 *C SFLOG SYSTEM               SFLOG SYSTEM is not available

Alarm Level: Critical.

Recovery

Activate (Active/IS-NR) any one of the SFLOG card in the system.

3.2.511 0628 - SFLOG SYSTEM is available

This message indicates the system has at least one SFLOG card that is Active/IS_NR status.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0628    SFLOG SYSTEM               SFLOG SYSTEM is available

Alarm Level: Normal.

Recovery

No further action necessary.

3.2.512 0629 - SFLOG SYSTEM is removed

This message indicates that all SFLOG cards are deleted from the system.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
   yyyy.0629    SFLOG SYSTEM               SFLOG SYSTEM is removed

Alarm Level: Normal.

Recovery

No further action necessary.

3.2.513 0630 - Throttle Threshold - exceeded

This message indicates the Throttle threshold for a particular Throttling GTT Action has exceeded. Any new messages hitting this Throttling Action will be discarded for the remaining duration of the current 30-second window. This alarm is issued for each Throttling Action for which the threshold has exceeded.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
**  yyyy.0630 ** TA – abc                Throttle Threshold – exceeded

Alarm Level: Major.

Recovery

Review and modify the throttle threshold for the Throttle GTT action if it is not currently set appropriately to handle the desired traffic volume.

  1. Use the rept-stat-sfthrot command to verify the Throttle Action status.
  2. Use the rtrv-gttact and chg-gttact commands to review and modify the Throttle Action settings.

3.2.514 0631 - Throttle Threshold - cleared

This message indicates the Throttle threshold for a particular Throttling GTT Action, or alarm threshold for UAM 0632, has cleared.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
   yyyy.0631    TA – abc                Throttle Threshold - cleared

Alarm Level: Normal.

Recovery

No further action necessary.

3.2.515 0632 - Alarm Threshold - exceeded

This message indicates the system wide alarm threshold for the throttling GTT Action has exceeded.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
  *   yyyy.0632 *  SCCP SYSTEM                Alarm Threshold – exceeded

Alarm Level: Minor.

Recovery

  1. Use the rept-stat-sfthrot command to verify the number of MSUs currently received by the throttling GTT Action in the 30-second window.
    Example of the output: 
    
Command Accepted - Processing
    tklc1181001 16-01-08 05:40:53 MST  EAGLE5 46.3.0.0.0-68.8.0
    rept-stat-sfthrot
    Command entered at terminal #3.
;
    tklc1181001 16-01-08 05:40:53 MST  EAGLE5 46.3.0.0.0-68.8.0

    SCCP Cards Configured= 5      Cards IS-NR= 5
    Average CPU Usage  =  5%

    CARD   VERSION     PST             SST           AST        TPS

--------------------------------------------------------------------------
   
    2201   138-008-000 IS-NR           Active        -----      0      
    2213   138-008-000 IS-NR           Active        -----      0 
    2217 P 138-008-000 IS-NR           Active        -----      0 
    2317   138-008-000 IS-NR           Active        -----      0 
    1111   138-008-000 IS-NR           Active        -----      116 

    PER TA TPS STATISTICS:

==========================================================================
                        CURRENT 30 SECS            PREVIOUS 30 SECS
                        ----------------------     ----------------------
    TA         STATUS   SUCCESS     DISCARD        SUCCESS     DISCARD
    
--------------------------------------------------------------------------
    throt1     ALLOWED  0           0              0           0
    throt2     ALLOWED  0           0              0           0

     Command Completed.
;
  2. Use the rtrv-gttact command to display throttle threshold (THRESHOLD) configured for the throttling GTT Action.
  3. Use the rtrv-th-alm command to display the system wide alarm threshold percentage (SFTHROTTHRESH) configured for throttling GTT Actions.
  4. No action is required if the throttle threshold for the throttling GTT Action and system wide alarm threshold percentage for throttling GTT Actions are configured as necessary.
  5. Use the chg-gttact command to update the throttle threshold if the throttle threshold currently configured for the throttling GTT Action is not adequate.
  6. Use the chg-th-alm command to update the system wide alarm threshold percentage for throttling GTT Actions, if a higher alarm threshold percentage needs to be set.

3.2.516 0633 - Alarm Threshold - cleared

This message indicates the system wide alarm threshold has cleared.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
   yyyy.0633    SCCP SYSTEM                Alarm Threshold - cleared

Alarm Level: Normal.

Recovery

No further action necessary.

3.2.517 0634 - SFAPP is available

This message indicates all the SFAPP cards are IS-NR in the system.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0634    SFAPP SYSTEM            SFAPP is available

Alarm Level: Normal.

Recovery

  1. Alarm itself is a corrective alarm.

3.2.518 0635 - SFAPP is not available

This message indicates all the SFAPP cards are isolated from the system.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0635    SFAPP SYSTEM            SFAPP is not available

Alarm Level: Critical.

Recovery

  1. Check if the SFAPP card is faulty or inhibited.

3.2.519 0636 - SFAPP is removed

This message indicates the last SFAPP card is deleted from the system.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0636    SFAPP SYSTEM            SFAPP is removed

Alarm Level: Normal.

Recovery

  1. Check if the SFAPP card is removed.

3.2.520 0637 - SFAPP Threshold Level1 Exceeded

This message indicates the SFAPP traffic is above the SFAPP Congestion Alarm Lvl 1 threshold.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0637    SFAPP SYSTEM            SFAPP Threshold Level1 Exceeded

Alarm Level: Minor.

Recovery

  1. Reduce the TPS of the card below the configured threshold level 1 value.

3.2.521 0638 - SFAPP Threshold Level2 Exceeded

This message indicates the SFAPP traffic is above the SFAPP Congestion Alarm Lvl 2 threshold.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0638    SFAPP SYSTEM            SFAPP Threshold Level2 Exceeded

Alarm Level: Major.

Recovery

  1. Reduce the TPS of the card below the configured threshold level 2 value.

3.2.522 0639 - SFAPP Threshold Level Critical

This message indicates the SFAPP traffic is above the system supported traffic limit.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0639    SFAPP SYSTEM            SFAPP Threshold Level Critical

Alarm Level: Critical.

Recovery

  1. Reduce the TPS of the card below the system maximum limit.

3.2.523 0640 - SFAPP Threshold Condition Cleared

This message indicates the SFAPP traffic is below the SFAPP Congestion Alarm Lvl 1 threshold.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0640    SFAPP SYSTEM            SFAPP Threshold Condition Cleared

Alarm Level: Normal.

Recovery

  1. Alarm itself is a corrective alarm..

3.2.524 0641 - SFAPP Capacity normal, card(s) abnormal

This message indicates that any provisioned SFAPP card is isolated from the system.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0641    SFAPP SYSTEM            SFAPP Capacity normal, card(s) abnormal

Alarm Level: Minor.

Recovery

  1. Check if the SFAPP card is faulty or inhibited.

3.2.525 0642 - System SFAPP TPS normal

This message indicates the isolated SFAPP card comes in service.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0642    SFAPP SYSTEM            System SFAPP TPS normal

Alarm Level: Normal.

Recovery

Alarm itself is a corrective alarm.

3.2.526 0643 - System SFAPP Threshold Exceeded

This message indicates the SFAPP TPS is above the SFAPP TPS Threshold Lvl (rtrv-th-alm).

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0643    SFAPP SYSTEM            System SFAPP Threshold Execeeded

Alarm Level: Major.

Recovery

  1. Reduce the overall TPS of the SFAPP subsystem below the SFAPP TPS threshold Lvl.

3.2.527 0644 - System SFAPP capacity exceeded

This message indicates the SFAPP capacity exceeds the maximum system limit.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0644    SFAPP SYSTEM            System SFAPP Capacity Exceeded

Alarm Level: Critical.

Recovery

  1. Reduce the overall TPS of the SFAPP subsystem below the Maximum system capacity.

3.2.528 0645 - LIM/SCCP card(s) denied SFAPP service

This message indicates the isolated SFAPP card comes in service.

Example 
e1061501 17-12-22 11:03:03 EST  EAGLE 46.5.1.5.0-73.10.0
**  0141.0645 ** SFAPP SYSTEM              LIM/SCCP card(s) denied SFAPP service

Alarm Level: Major.

Recovery

  1. Configure the LIM/SCCP card for SFAPP service.

3.2.529 0646 - SFAPP Dynamic Learning Alarm Cleared

This occurs if alarm 0543 (VLR Dynamic Learning is suspended) is raised and changed the value of the mode parameter of the SFAPPOPTS table to OFF. 

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0646    SFAPP SYSTEM                SFAPP Dynamic Learning Alarm Cleared

Alarm Level: Normal.

Recovery

None. This alarm is a clearing alarm.

3.2.530 0647 - EEDB Connectivity Down

This occurs when connectivity between the EAGLE and its EEDB has been lost. 

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0647    SYSTEM                EEDB Connectivity Down

Alarm Level: Major.

Recovery

  1. Check the connectivity between the EAGLE and its EEDB.

3.2.531 0648 - EEDB Connectivity Up

This occurs when connectivity between the EAGLE and its EEDB has been restored. 

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890   
    yyyy.0648    SYSTEM                EEDB Connectivity Up

Alarm Level: Normal.

Recovery

None. This alarm is a clearing alarm.

3.2.532 0649 - Card is Non-responsive

This alarm indicates that a specific card is non-responsive due to some software or hardware issue.

Example

tklc1111101 23-04-28 08:20:50 EST  EAGLE 47.0.0.1.0-79.13.12
**  0621.0649 ** CARD 1108 IPSG69        CARD is non-responsive
Alarm Level: Major

Recovery:

Reseat the card again.

3.2.533 0650 - MTP3 MFC Discard

This alarm indicates that MTP3 routed messages are getting discarded on the card.

Example

tklc1111101 23-04-28 08:20:50 EST  EAGLE 47.0.0.1.0-79.13.12
**  0621.0650 ** CARD 1108 IPSG69        MTP3 MFC Discard

Alarm Level: Major

Recovery:

This issue will be resolved automatically within a few seconds. However, the alarm will be cleared if there is no MTP3 MFC discard for five minutes. If the issue is not auto-corrected, then reseat the card again along with the corresponding destination cards.

3.2.534 0901 - Card DB Load Timeout, Check GLS SS

This message indicates that the database of a card or subsystem has been in a transition for 9 minutes. This alarm shows the unavailability of the GLS subsystem. If the Integrated GLS feature is OFF or not yet enabled, this alarm shows that no TSM/E5-TSM is in IS-NR state or no TSM/E5-TSM card is responding to GWS requests. If the Integrated GLS feature is ON, this alarm shows that the E5-OAM cards are not performing the GLS functionality properly.

Example 
tekelecstp 02-09-21 17:09:58 EST EAGLE5 42.0.2-63.38.33
** 0076.0901 ** CARD 1201 SS7ANSI Card DB load timeout, check GLS SS

Alarm Level: Major

Recovery

  1. Use the rtrv-ctrl-feat command to check the state of Integrated GLS feature. If the Integrated GLS feature is enabled and ON, the GLS subsystem is running. Go to step 6.
  2. If the Integrated GLS feature is OFF or not yet enabled, the GLS subsystem is a collection of TSM/E5-TSM cards running the GLS application. Verify that at least one TSM/E5-TSM card is in IS-NR state using the rept-stat-card:appl=gls command.
  3. If TSM/E5-TSM card(s) are not in IS-NR state, enter the init-card:appl=gls command to boot the GLS subsystem.
  4. Verify that the cards come back in service. Use the rept-stat-card:appl=gls command.

  5. Run the rept-stat-db:display=all command to identify which cards are in transition, and note all cards that are in transition state (T column set to "Y"). If the transition is not cleared, turn the Integrated GLS feature ON again, then contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

    Example of rept-stat-db command: 
    tekelecstp 02-09-21 16:01:58 EST  EAGLE5 42.0.2-63.38.33
    DATABASE STATUS: >> NOT OK (DMS) <<
            TDM 1114 ( STDBY)                 TDM 1116 ( ACTV )
            C   LEVEL    TIME LAST BACKUP     C   LEVEL    TIME LAST BACKUP
            - -------- ---------------------- - -------- ----------------------
    FD BKUP Y       22 02-09-07 13:33:18 EST  Y        1     -        -
    FD CRNT Y       71                        Y       71
            MCAP 1113                         MCAP 1115
            - --------                        - --------
    RD BKUP -    -         -        -         -    -         -        -
    USB BKP -    -         -        -         -    -         -        -

    CARD/APPL  LOC   C  T  LEVEL       TIME LAST UPDATE   EXCEPTION
    ---------  ----  -  -  ----------  -----------------  --------------
    VSCCP      1101  Y  N  71          02-09-20 13:25:06       -
    MCP        1104  -  -      -           -        -          -
    CCS7ITU    1105  Y  N  71          02-09-20 13:25:06       -
    MCP        1107  -  -      -           -        -          -
    VSCCP      1111  Y  N  71          02-09-20 13:25:06       -
    OAM-RMV    1113  -  -      -           -        -          -
    TDM-CRNT   1114  Y  N  71          02-09-20 13:25:06       -
    TDM-BKUP   1114  Y  -  22          02-08-31 10:31:00  DIFF LEVEL
    OAM-RMV    1115  -  -      -           -        -          -
    OAM-USB    1115  -  -      -           -        -          -
    TDM-CRNT   1116  Y  N  71          02-09-20 13:25:06       -
    TDM-BKUP   1116  Y  -  1           00-00-00 00:00:00  DIFF LEVEL
  6. If the Integrated GLS feature is ON, turn it OFF with the CHG-CTRL-FEAT:partnum=893038901:status=OFF command.
  7. Wait for 5 minutes, and use the rept-stat-db:display=all command to verify that there are no cards in transition. Turn the Integrated GLS feature back on using the CHG-CTRL-FEAT:partnum=893038901:status=ON command.
  8. If the problem persists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.535 0902 - Card DB is stable

This message indicates that the database of a card was in transition but has recovered.

Example
RLGHNCXA3W 99-12-06 10:56:18 EST EAGLE 35.0.0
0104.0902    CARD 1201 SS7ANSI     Card DB is stable

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is needed.

3.2.536 0903 - IP Link A is Down

This message indicates that an IP application socket is out of service due to a IP link down (ethernet problem) or due to the signaling link being deactivated.

Example 
RLGHNCXA03W 01-01-10 16:28:08 EST EAGLE 35.0.0
** 0046.0903  ** CARD 1111  EBDADCM   IP Link A is down

Alarm Level: Major

Recovery

  1. Enter the following command to determine the IP address of the link:
    rtrv-ip-lnk:loc=xxxx:port=a

    Where xxxx is the card identified in the alarm output.

  2. Enter the following command to retrieve the name of the local host:
    rtrv-ip-host:ipadr=xxxx.xxxx.xxxx.xxxx

    Where xxxx.xxxx.xxxx.xxxx = the link IP address from 1.

  3. Enter the following command to get the name of the remote host:
    rtrv-appl-sock:lhost=xxxxxxxx

    Where xxxxxxxx = local host name from 2.

  4. Enter the following command to test the TCP/IP connection:
    pass:loc=xxxx:cmd=”ping yyyyyyyyyy”

    Where: xxxx = Card location from the alarm output. yyyyyyyyyy = logical name of the remote host from 3.

  5. If the ping command fails, perform the following checks:
    1. Check the remote host hardware and software.
    2. Use your company procedures to check the network.
    3. Check cable connections at the IP7 Secure Gateway and at the remote host.
  6. If the UNAVAIL REASON still indicates an alignment problem, enter the following command:
    rept-stat-slk:loc=xxxx:port=a

    Where xxxx is the card identified in the alarm output. If the DCM card is not OOS-MT, proceed to 8.

  7. If the DCM card is OOS-MT, do the following, using the rept-stat-card command to check for card IS-NR state after each action:
    1. Reinitialize card using the init-card command.
    2. Reseat the card.
    3. Replace the card.
      Refer to the Maintenance Manual for card removal/replacement procedures.
  8. If the fault is not cleared, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.537 0904 - IP Link A is Up

This indicates that a previously broken link between the DCM card and the OAP now exists and is functioning properly.

Example 
RLGHNCXA03W 01-01-10 16:28:08 EST EAGLE 35.0.0
0046.0904   CARD 1111  EBDADCM   IP Link A is up

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.538 0905 - IP Link B is Down

This message indicates that an IP application socket is out of service due to a IP link down (ethernet problem) or due to the signaling link being deactivated.

Example 
RLGHNCXA03W 01-01-10 16:28:08 EST EAGLE 35.0.0
** 0046.0905 ** CARD  1111 EBDADCM    IP Link B is down

Alarm Level: Major

Recovery

  1. Enter the following command to determine the IP address of the link:
    rtrv-ip-lnk:loc=xxxx:port=b
    Where xxxx is the card identified in the alarm output.
  2. Enter the following command to retrieve the name of the local host:
    rtrv-ip-host:ipadr=xxxx.xxxx.xxxx.xxxx
    Where xxxx.xxxx.xxxx.xxxx = the link IP address from 1.
  3. Enter the following command to get the name of the remote host:
    rtrv-appl-sock:lhost=xxxxxxxx
    Where xxxxxxxx = local host name from 2.
  4. Enter the following command to test the TCP/IP connection:
    pass:loc=xxxx:cmd=”ping yyyyyyyyyy”
    Where xxxx = Card location from the alarm output. yyyyyyyyyy = logical name of the remote host from 3.
  5. If the ping command fails, perform the following checks:
    • Check the remote host hardware and software.
    • Use your company procedures to check the network.
    • Check cable connections at the IP7 Secure Gateway and at the remote host.
  6. If the UNAVAIL REASON still indicates an alignment problem, enter the following command:
    rept-stat-slk:loc=xxxx:port=b
    Where xxxx is the card identified in the alarm output. If the DCM card is not OOS-MT, proceed to 8.
  7. If the DCM card is OOS-MT, do the following, using the rept-stat-card command to check for card IS-NR state after each action:
    • Reinitialize card using the init-card command
    • Reseat the card
    • Replace the card
    Refer to the Maintenance Manual for card removal/replacement procedures.
  8. If the fault is not cleared, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.539 0906 - IP Link B is Up

This indicates that a previously broken link between the DCM card and the OAP now exists and is functioning properly.

Example 
RLGHNCXA03W 01-01-10 16:28:08 EST EAGLE 35.0.0
0046.0906   CARD 1111  EBDADCM   IP Link B is up

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.540 0907 - HW limiting TPS Rate Alarm Cleared

This message indicates that the alarm condition, specified by message “0908 - HW cannot support purchased TPS rate,” has been cleared.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 5.0.0-32.0.0 
0100.0907    CARD 1101 SS7IPGW   HW limiting TPS rate alarm cleared
             ASSY SN:  102199815a1234

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.2.541 0908 - HW Cannot Support Purchased TPS Rate

This message indicates that the purchased transactions per second (TPS) rate running on the DCM(s) is higher than can be supported by you current hardware.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 5.0.0-32.0.0 
** 0100.0908 ** CARD 1101 SS7IPGW  HW cannot support purchased TPS rate
                ASSY SN:  102199815a1234
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 5.0.0-32.0.0
** 0100.0908 ** CARD 1101 SS7IPGW  HW cannot support purchased TPS rate
                ASSY SN:  102199815a1234

Alarm Level: Major

Recovery

  1. Upgrade your DCM hardware.
    This alarm can be cleared only when the concerned DCM hardware is unplugged.
  2. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA for information about upgrading your DCM hardware.

3.2.542 0911 - Dynamic Database is Inconsistent

The dynamic database (DDB) audit (whether running automatically or on-demand) has detected that checksums are inconsistent. This means that one or more cards do not concur with the current network configuration. (The UIM lists a maximum of four affected cards.)

The dynamic database audit looks for checksum errors in dynamic database tables on LIM and Service Module cards. The fixed database, which is entered via the OAM card, includes all provisionable tables and options. The dynamic database has information about the state of those static-database entries (for example, which links are actually available). Each LIM and Service Module card has a copy of the fixed database and the dynamic database. The entries in the tables in the dynamic database on each card change as network conditions change. Cards calculate and record dynamic database checksums in real time as updates are applied.

If the dynamic database is being updated during the dynamic database audit, then the inconsistent checksums might not indicate a true problem. To ensure that all dynamic database changes have been received and applied, the OAM processes audit replies after a required quiet period.

Note:

You can use the “DDBAUDTIMER” SS7OPTS option to enable and disable the background audit.

Typically, when the dynamic database copies are consistent among all the cards except one, then there is a problem on that one card. It is possible, however, for one card to have the correct information when the other cards do not (for example, a card might have a link on it that is actually available when the other cards incorrectly show the link as unavailable). When this alarm occurs, further troubleshooting is necessary to determine the actual status of the routes, links, linksets, and subsystems.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 41.0
**  0100.0911 ** SYSTEM                  Dynamic database is inconsistent
                 Card 1101, 1102, 1107, 1108, ... (3 others)

Alarm Level: Major

Recovery

The Eagle cannot automatically determine which cards are inconsistent. Do the following to address a dynamic-database inconsistency alarm:

  1. Run the rept-stat-ddb command to display the last dynamic database audit report.
  2. Initialize the affected cards identified in the dynamic database audit report:
    1. If a small number of cards are reported inconsistent, initialize them using the init-card:loc= command. You should initialize the affected cards immediately.
    2. If all cards of the same type report inconsistencies, initialize them using the init-card:appl=command.

      Caution:

      This command could affect service as it will boot all the appl cards at the same time (for example, the command could cause loss of SCCP if the init-card:appl=VSCCPcommand is run).
  3. Run the rept-stat-card:mode=full:loc= command on each card identified as inconsistent to verify the card is IS-NR.
  4. If a large number of cards of various types report inconsistent, you might need to issue the init-network or the init-sys command to clear the inconsistency.

    Caution:

    These commandswill cause a nodal outage.
  5. After the cards are initialized, run the aud-data:type=DDB command. If the report shows no inconsistency, then the problem is fixed.
  6. Next, you can use the dbg-ddb command to troubleshoot the problem. The parameters to use in the dbg-ddb command depend on the type of dynamic database update that was missed (route/link/linkset).
    When a system reports dynamic database inconsistencies, first check the IMT buses statistics to make sure they are clean. This is important because multicast updates resulting from network activity transit via the IMT buses and any outstanding issue on this part of the system may lead some cards to miss the updates and OAM to report dynamic database inconsistencies. When a checksum is identified to be incorrect and is updated by a wild write audit, you may want to know that a dynamic database inconsistency reported on a card was due to a wild write (rather than any other cause, such as a missed multicast). In the scenario where one or a group of cards miss a dynamic database update related to a network state change, then the counter collecting the total number of update misses is incremented. Use the dbg-ddb command to retrieve this counter.
  7. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.2.543 0912 - Dynamic database is now consistent

The dynamic database audit has run and determined that the checksums are consistent.

Example
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.0912  SYSTEM       Dynamic database is now consistent

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates a previous fault has been corrected.

No further action is necessary.

3.3 UIMs

The following are UIMs that may be displayed.

3.3.1 1000 - MTP rcvd UPU - User Part is not SCCP

The system forwarded a unit data (UDT) message to a distant node that does not support SCCP. In response, the distant node sent back a user part unavailable (UPU) message.

The message provides the affected point code (which sent the UPU), as well as the service information octet (SIO) field of the message and the cause code.

All fields are in decimal values. The SIO field values applicable to this message are:

03 – SCCP

04 – Telephone User Part (TUP)

05 – ISDN User Part (ISUP)

06 – Data User Part (call and circuit related messages)

07 – Data User Part (facility registration and cancellation)

08 – MTP Testing User Part

The message also provides the value for the User Part that was unavailable (UPU=). The values shown above apply to this field as well.

The Cause Codes (Unavail Cause =) applicable to this message are:

000 – Unknown

001 – Unequipped Remote User

002 – Inaccessible User Part

Unequipped remote user indicates the distant node is not equipped for SCCP. Inaccessible user part indicates that the distant node is equipped with SCCP capability, but there has been a failure in SCCP making it impossible to handle messages sent to it by MTP.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0   
0100.1000    CARD 1201,A  INFO   MTP rcvd UPU - user part is not SCCP
SIO=03   OPC=003-232-000  DPC=001-004-000                
AFTPC=004-000-001  UPU=03 UNAVAIL CAUSE=001                
LSN=A1234567

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.2 1001 - MTP rcvd Transfer Controlled (TFC)

The system is generating traffic for a remote node that is congested. The distant node sent a transfer controlled (TFC) message in response.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
   0100.1001    CARD 1201,A  INFO   MTP rcvd Transfer Controlled (TFC)
                SIO=0a   OPC=003-232-000  DPC=000-000-000
                AFTPC=004-000-000  CONG STATUS=000
LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
CONG STATUS
Congestion status
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. The affected point code field of the output message identifies the node that is congested.
    The system discards MSUs with a priority lower than the congestion status value sent with the TFC.
  2. The system sends only messages with a priority higher or equal to the congestion status value of the TFC.
    Refer to TR-NPT-000246, Issue 2, June 1987, Chapter 1.111.5, Annex A for priority assignments.
  3. Contact the far-end to determine the reason for congestion.

3.3.3 1002 - MTP rcvd invalid TFC - status 0

The EAGLE 5 ISS system received a transfer controlled (TFC) message with a status of 0 (protocol violation). No action on the part of the EAGLE 5 ISS system has been taken.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
   0100.1002    CARD 1205,B  INFO   MTP rcvd invalid TFC - status 0
SIO=0a   OPC=003-234-000  DPC=000-024-000
AFTPC=055-000-046  CONG STATUS=000
LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
CONG STATUS
Congestion status
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. The EAGLE 5 ISS system does not take any action based on this TFC message.
    The output above is provided only to indicate the event took place, but does not require any action by maintenance personnel.
  2. Contact the far-end to determine the reason for congestion.

3.3.4 1003 - MTP rcvd invalid H0/H1 code

SS7 received a level 3 message with an unrecognized H0H1 code.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
   0100.1003    CARD 1205,B  INFO   MTP rcvd invalid H0/H1 code
                SIO=0a   OPC=003-235-000  DPC=000-024-000
H0H1=43
LSN=A1234567
Legend
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This message could indicate that the MTP restart feature is not enabled. If the MTP restart feature should be enabled, use the chg-feat to turn on the MTP restart feature.

    Note:

    Once the feature is enabled using the chg-feat command, it cannot be turned off, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA before executing the chg-feat command.
  2. This output is informational only.
    The SS7 traffic is not interrupted and service is not affected.
  3. Contact the far-end to determine the reason for congestion.

3.3.5 1004 - MTP rcvd unknown DPC

The EAGLE 5 ISS system received an MSU with a DPC that is not in the routing table.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.1004    CARD 1205,B  INFO   MTP rcvd unknown DPC
SIO=0a   OPC=003-236-000  DPC=000-071-000
LSN=A1234567
Legend
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If the EAGLE 5 ISS system should be able to route to the DPC (indicated in the message output), add the DPC to the EAGLE 5 ISS system routing table using the ent-rte and ent-dstn commands.
  2. If the DPC is not one that the EAGLE 5 ISS system should be able to route to, no action is necessary.

3.3.6 1005 - GWS rcvd OPC that is not allowed

This message indicates the EAGLE 5 ISS received an MSU with an origination point code (OPC) that is not allowed in gateway screening (GWS).

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.1005    CARD 1205,A  INFO   GWS rcvd OPC that is not allowed
SIO=b2   OPC=003-237-000  DPC=003-003-003
H0H1=32  AFTPC=03-03-03
SR=osp3   LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this origination point code (OPC) is one that should be allowed to pass through the network, add the OPC to the gateway screening (GWS) tables assigned to the link reporting this message.
    Use the ent-scr-opc command to add the OPC to the list of allowed OPC codes. Refer to the Database Administration Manual - Gateway Screening for instructions on how to add an OPC to gateway screening (GWS).
  2. If the OPC should not be allowed to pass through the network, no action is necessary.

3.3.7 1006 - GWS rcvd DPC that is not allowed

This message indicates the EAGLE 5 ISS received an MSU with a destination point code (DPC) that is not allowed in gateway screening (GWS).

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.1006    CARD 1205,A  INFO   GWS rcvd DPC that is not allowed
SIO=b2   OPC=003-237-000  DPC=003-003-003
H0H1=23  AFTPC=03-03-03
SR=osp3   LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this destination point code (DPC) is one that should be allowed to pass through the network, add the DPC to the gateway screening (GWS) tables assigned to the link reporting this message.
    Use the ent-scr-dpc command to add the DPC to the list of allowed DPC codes. Refer to the Database Administration Manual- Gateway Screening for instructions on adding a DPC to gateway screening (GWS).
  2. If the DPC should not be allowed to pass through the network, no action is necessary.

3.3.8 1007 - GWS rcvd OPC That is Blocked

This message indicates the EAGLE 5 ISS received an MSU from an origination point code (OPC) that is blocked from this network by gateway screening (GWS).

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.1007    CARD 1205,A  INFO   GWS rcvd OPC that is blocked
SIO=93   OPC=001-001-004  DPC=003-003-003
H0H1=31  AFTPC=03-03-03
SR=osp3   LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this origination point code (OPC) should be allowed to send messages through the network, use the command dlt-scr-blkopc to delete the OPC from the blocked OPC screen set assigned to this link.
  2. If this OPC should be blocked from entering this network, no further action is necessary.

3.3.9 1008 - GWS rcvd DPC that is blocked

This message indicates the EAGLE 5 ISS received an MSU from a destination point code (DPC) that is blocked from this network by gateway screening (GWS).

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.1008    CARD 1205,A  INFO   GWS rcvd DPC that is blocked
SIO=b2   OPC=007-008-000  DPC=003-003-003
H0H1=32  AFTPC=03-03-03
SR=osp3   LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this destination point code (DPC) should be allowed to send messages through the network, use the command dlt-scr-blkdpc to delete the DPC from the blocked DPC screen set assigned to this link.
  2. If this DPC should be blocked from entering this network, no further action is necessary.

3.3.10 1009 - GWS rcvd SIO that is not allowed

This message indicates that gateway screening (GWS) has discarded an MSU that is not allowed in the network.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.1009    CARD 1205,B  INFO   GWS rcvd SIO that is not allowed
SIO=b2   OPC=003-237-000  DPC=003-003-003
H0H1=33  AFTPC=03-03-03
SR=osp3   LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This indicates that a MSU was discarded because it failed screening.
    No action is necessary, unless the MSU should have passed. If the MSU should have passed (verified by the fields displayed in the above message), go to 2.
  2. Using the rtrv-scr-sio command, verify that the screening reference specified in the above message does not allow MSUs with the SI/H0/H1 values indicated.
  3. If the MSU should have passed screening, use the ent-scr-sio command to add the si data to the screening reference assigned to this link.

3.3.11 1010 - GWS rcvd a priority that is not allowed

This message indicates gateway screening (GWS) has discarded an MSU because the priority is listed as one that is not allowed in this network.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.1010    CARD 1205,A  INFO   GWS rcvd a priority that is not allowed
SIO=0a   OPC=003-242-000  DPC=000-071-000
H0H1=54  AFTPC=03-03-03
SR=osp3   LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H11
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This indicates that a MSU was discarded because it failed screening.
    No action is necessary, unless the MSU should have passed. If the MSU should have passed (verified by the fields displayed in the above message), go to 2.
  2. Using the rtrv-scr-sio command, verify that the screening reference specified in the above message does not allow MSUs with the priority value indicated.
  3. If the MSU should have passed screening, use the chg-scr-sio command to add the pri data to the screening reference.

3.3.12 1011 - GWS rcvd TFC, AFTPC not in routing tbl

This indicates that a transfer controlled message was received by a gateway link and failed screening because of an affected point code value in the message.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST  EAGLE 35.0.0
0100.1011    CARD 1105,B  INFO   GWS rcvd TFC, AFTPC not in routing tbl SIO=0a   OPC=003-243-000  DPC=000-024-000
H0H1=35   AFTPC=099-099-003
SR=osp3    LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  2. If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  3. If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.13 1012 - GWS rcvd Clg Party That is Not Allowed

This indicates an MSU was received on a gateway link but failed screening because of the SCCP calling party address.

Example 1 (non-SCMG) 
RLGHNCXA21W 00-04-18 18:59:23 EST  EAGLE 31.3.0
0101.1012    CARD 1205,B1  INFO   GWS rcvd Clg Party that is not allowed SIO=0a   OPC=003-244-000  DPC=000-071-000
SCCP MT=  18
CDPA:  AI=10  PC=003-003-003  SSN=005  TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA:  AI=10  PC=004-004-004  SSN=005  TT=251
ADDR=ABCDEF1234567890ABCDE
SR=scrb     LSN=A1234567
Example 2 (SCMG) 
RLGHNCXA21W 00-04-18 18:59:30 EST  EAGLE 31.3.0
0102.1012    CARD 1205,B1  INFO   GWS rcvd Clg Party that is not allowed SIO=03  OPC=003-245-000  DPC=001-004-000
SCMG:    TYPE=000  AFTPC=003-003-003
MULT=000  AFTSS=005
SR=scrb  LSN=A1234567
Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This output indicates that a SCCP message was discarded because it failed screening.
    No action is necessary, unless the message should have passed. If the message should have passed (verified by the fields displayed in the above message), continue with 2.
  2. Using the rtrv-scr-cgpa command, verify the screen name specified in the output does not allow SCCP messages.
    Check the following fields in the output:
    • For non-SCMG messages, check the SCCP MT, SSN, and OPC.
    • For SCMG messages, check the TYPE, AFTSS, and AFTPC (or OPC if the AFTPC is not present).
  3. If the SCCP message should have passed screening, use the ent-scr-cgpa or chg-scr-cgpa command to add the appropriate information to the screening reference.

3.3.14 1013 - GWS rcvd Cld Party that is not allowed

This indicates an MSU was received on a gateway link but failed screening because of the called party value in the SCCP called party address field.

Example

The following is an output example when an SCCP management message, such as SSP, SST, SSA, or SSC generates this UIM. 
RLGHNCXA21W 00-04-18 18:59:30 EST  EAGLE 35.0.0
0102.1013    CARD 1205,B  INFO   GWS rcvd Cld Party that is not allowed
SIO=03  OPC=003-245-000  DPC=001-004-000
SCMG:    TYPE=000  AFTPC=003-003-003
MULT=000  AFTSS=005
SR=scrb  LSN=A1234567
Report Date:06-09-13  Time:00:13:22
The following is an output example when an SCCP report message, such as UDT, UDTS, or XUDT, generates this UIM. 
RLGHNCXA21W 00-04-18 18:59:30 EST  EAGLE 35.0.0
0185.1005    CARD 1101,A2  INFO      GWS rcvd OPC that is not allowed
SIO=03   OPC=007-021-067       DPC=005-022-019
SCCP MT=018
CDPA: AI=05 PC=005-006-007      SSN=006 TT=007
ADDR=0
CGPA: AI=14 PC=015-016-017      SSN=022 TT=023
ADDR=9194603655
SR=scr1  LSN=ABCD123
Report Date:02-07-21  Time:16:20:19
Legend
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This output indicates that a SCCP message was discarded because it failed screening.
    No action is necessary, unless the message should have passed. If the message should have passed (verified by the fields displayed in the above message), go to 2.
  2. Using the rtrv-scr-cdpa command, verify that the screening reference specified in the above message does not allow SCCP messages with the called party address indicated.
  3. If the SCCP message should have passed screening, use the ent-scr-cdpa command to add the called party address to the screening reference.

3.3.15 1014 - GWS rcvd Translation Type not allowed

This indicates an MSU requiring global title was received on a gateway link but failed screening because of the translation type indicated in the message.

Example 
RLGHNCXA21W 00-04-18 18:59:23 EST  EAGLE 31.3.0
0101.1014    CARD 1205,B  INFO   GWS rcvd Translation Type not allowed
SIO=0a   OPC=003-244-000  DPC=000-071-000
SCCP MT=  18
CDPA:  AI=10  PC=003-003-003  SSN=005  TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA:  AI=10  PC=004-004-004  SSN=005  TT=251
ADDR=ABCDEF1234567890ABCDE
SR=scrb   LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This output indicates that an MSU requiring global title translation was discarded because it failed screening.
    No action is necessary, unless the message should have passed. If the message should have passed (verified by the fields displayed in the above message), go to 2.
  2. Using the rtrv-scr-tt command, verify that the screen name specified in the above message does not allow MSUs with the translation type indicated.
  3. If the MSU should have passed screening, use the ent-scr-tt command to add the translation type to the screening reference.

3.3.16 1015 - GWS rcvd SCMG with not allowed AFTPC

This message indicates that an SCCP management message (SCMG) was received on a gateway link and failed gateway screening because of the affected point code.

Example 
RLGHNCXA21W 00-04-18 18:59:30 EST  EAGLE 31.3.0
0102.1015    CARD 1205,B  INFO   GWS rcvd Cld Party that is not allowed
SIO=03   OPC=003-245-000  DPC=001-004-000
SCMG:    TYPE=000  AFTPC=003-003-003
MULT=000  AFTSS=005
SR=scrb  LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This output indicates that an SCCP management message was discarded because it failed screening.
    No action is necessary, unless the message should have passed. If the message should have passed (verified by the fields displayed in the above message), go to 2.
  2. Using the rtrv-scr-aftpc command, verify that the screening reference specified in the above message does not allow SCCP management messages with the affected point code indicated.
  3. If the message should have passed screening, use the ent-scr-aftpc command to add the affected point code to the screening reference.

3.3.17 1016 - MTP Adj PC not in routing table

This message indicates that an MSU was received with an adjacent point code not found in the EAGLE 5 ISS routing table.

Example 
RLGHNCXA21W 00-11-18 19:12:00 EST  EAGLE 35.0.0
0147.1016    CARD 1201,A  INFO   MTP Adj PC not in routing table
OPC=001-001-001  CPC=002-002-002
LSN=lsn01a
Legend
CPC
Capability point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This output indicates that an MSU was discarded because the DPC did not appear in the system linkset table.
    Network messages are valid only from adjacent point codes.
  2. If the MSU should have passed screening, use the chg-scr-sio command to add the pri data to the screening reference.

3.3.18 1018 - REPT-MTPERR: MTP rcvd invalid SIO

A MSU is discarded when the EAGLE 5 ISS is unable to perform MTP-level routing.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST  EAGLE 31.3.0
0140.1018  CARD 1201,A  INFOREPT-MTPERR: MTP rcvd invalid SIO
SIO=07   OPC=001-001-001   DPC=002-002-002
LSN=A1234567
Legend
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This indicates that a MSU was discarded because of an undefined point code or an invalid SIO.
    This message is displayed only when the total number of discarded SIOs is less than a specified limit over a specified period time. No action is necessary, unless the MSU should have passed. If the MSU should have passed (verified by the fields displayed in the above message), go to 2.
  2. Using the rtrv-scr-sio command, verify that the screening reference specified in the above message does not allow MSUs with the value indicated.
    1. If the MSU should have passed screening, use the chg-scr-sio command to add the appropriate data to the screening reference.
    2. If the SIO is not one that the EAGLE 5 ISS should be able to route to, no action is necessary.

3.3.19 1019 - SCCP rcvd invalid UDTS/XUDTS msg

SCCP received a user data service (UDTS)/extended user data service (XUDTS) message from the network that was discarded because of an invalid message type indicator.

Example 
RLGHNCXA21W 00-04-18 19:00:05 EST  EAGLE 31.3.0
0106.1019    CARD 1103,A  INFO   SCCP rcvd invalid UDTS/XUDTS msg
SIO=03   OPC=003-251-000  DPC=001-004-000
CDPA: SSN=005    TT=250
CGPA: SSN=000    TT=000
RETURN CAUSE=001
DATA=26 80 03 09 0e 06 09 00 fe 08 50 55 05
43 00 00 00 00 00
LSN=A1234567
Legend
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
return cause
Identifies the reason for the returned message (for connectionless protocols)
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

This indicates that SCCP received a UDTS/XUDTS message that was discarded because the message type field contained a value invalid in the system.

No action is necessary.

Note:

The UDTS/XUDTS message is used in the SCCP protocol to indicate an error in a UDT message. The UDT was sent to another node, an error was found, and the UDTS/XUDTS message was returned with the following fields:
  • Message type
  • Return cause
  • Called party address
  • Calling party address
  • Data

3.3.20 1020 - IARCDPN NPP Service is off

This message is issued when the IARCDPN NPP service is called for at run-time, but the service status is currently set to OFF instead of ON.

Example 
    RLGHNCXA21W 09-07-21 16:20:19 EST  EAGLE 41.1.0
    0002.1020    CARD 1113     INFO      IARCDPN NPP Service is off
                 Report Date:09-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Use the chg-npp-serv command to change the service status to ON. Enter chg-npp-serv:srvn=iarcdpn:status=on.

3.3.21 1021 - IARCGPN NPP Service is off

This message is issued when the IARCGPN NPP service is called for at run-time, but the service status is currently set to OFF instead of ON.

Example 
    RLGHNCXA21W 09-07-21 16:20:19 EST  EAGLE 41.1.0
    0002.1021    CARD 1113     INFO      IARCGPN NPP Service is off
                 Report Date:09-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Use the chg-npp-serv command to change the service status to ON. Enter chg-npp-serv:srvn=iarcgpn:status=on.

3.3.22 1022 - System Meas. Limit Exceeded for LSONISMT

This UIM alarm is issued when the either of these limits is exceeded:

  • Maximum of 3000 LSONISMT measurements, or

  • Maximum of 100 ISUP message type measurements per linkset.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST  EAGLE 31.3.0
0140.1022  SYSTEM  INFO   System Meas. limit exceeded for LSONISMT

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Each link in a linkset collects measurements for 100 ISUP message type measurements.
    Only the first 100 types collected per linkset are reported. Those links that are not reported in the LSONISMT Report have their counts added to the totals in the LSORIGNI Gateway Report and the STP Report (MSUDSCRD field).
  2. If the system total exceeds 3000, only the first 3000 collected are reported in the LSONISMT Gateway Report.
    Any counts not included in this report are added to the totals in the LSORIGNI Gateway Report and the STP Report (MSUDSCRD field).

3.3.23 1023 - SCCP rcvd unknown msg type

This UIM may indicate that the SCCP received a message from the network that was discarded because of an unknown message type indicator. The generation of this UIM does not necessarily mean that an MSU has been discarded, however. This UIM can indicate that some feature did not handle an MSU due to its package type. (For example, features such as PPSMS or MO SMS NP/NPP feature that do not handle some SCCP MSU types.) In this case, the feature issues this UIM and passes the MSU to GTT to process.

Example 
RLGHNCXA21W 00-04-18 19:01:09 EST  EAGLE 31.3.0
0109.1023    CARD 1103,A  INFO   SCCP rcvd unknown msg type
SIO=0a   OPC=003-255-000  DPC=000-024-000
DATA=26 80 03 09 0e 06 09 00 fe 08 50 55 05
43 00 00 00 00 00
LSN=A1234567
Legend
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.24 1024 - SCCP rcvd inv msg length

The SCCP received a message from the network that was discarded because of an invalid message length.

Example 
RLGHNCXA21W 00-04-18 19:01:15 EST  EAGLE 31.3.0
0110.1024    CARD 1103,A  INFO   SCCP rcvd inv msg length
SIO=0a   OPC=004-000-000  DPC=000-071-000
DATA=26 80 03 09 0e 06 09 00 fe 08 50 55 05
43 00 00 00 00 00
LSN=A1234567
Legend
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

The SCCP received a message that was discarded because the message length field contained an invalid field for the system.

No action is necessary.

3.3.25 1025 - SCCP rcvd inv msg class

The SCCP received a message from the network that was discarded because of an invalid message class.

Example 
RLGHNCXA21W 00-04-18 19:01:40 EST  EAGLE 31.3.0
0111.1025    CARD 1103,A  INFO   SCCP rcvd inv msg class
SIO=0a   OPC=004-001-000  DPC=000-071-000
CDPA SS=000    CDPA TT=000
CGPA SS=00    CGPA TT=000
CLASS=000      MSG TYPE=00
LSN=A1234567
Legend
CDPA
Called party address
CGPA
Calling party address
class
Message classl
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
SIO
Service information octet
SS
Subsystem
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

The SCCP received a message that was discarded because the message class field contained an invalid value for the system.

No action is necessary.

3.3.26 1026 - System Meas Limit exceeded for LSORIGNI

This gateway related data has exceeded its threshold for the accumulation interval.

Example 
RLGHNCXA21W 00-04-18 19:05:43 EST  EAGLE 31.3.0
0128.1026    CARD 1105  INFO   System Meas Limit exceeded for LSORGNI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.27 1027 - System Meas Limit exceeded for LSDESTNI

This gateway related data has exceeded its threshold for the accumulation interval.

Example
RLGHNCXA21W 00-04-18 19:05:43 EST  EAGLE 31.3.0
0128.1027    CARD 1105  INFO   System Meas Limit exceeded for LSDESTNI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.28 1028 - System Meas. Limit exceeded for ORIGNI/NINC

This gateway related data has exceeded its threshold for the accumulation interval.

Example 
RLGHNCXA21W 00-04-18 19:05:43 EST  EAGLE 31.3.0
0128.1028   CARD 1105  INFO   System Meas. Limit exceeded for ORIGNI/NINC

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.29 1029 - SCCP rcvd inv Cld Party - bad GT ind

The SCCP received a message from the network that was discarded because of a bad global title indicator in the called party address.

Example 
RLGHNCXA21W 00-04-18 19:02:05 EST  EAGLE 31.3.0
0112.1029    CARD 1103,A1  INFO   SCCP rcvd inv Cld Party - bad GT ind
SIO=03   OPC=001-001-001  DPC=002-002-002
CDPA LENGTH=000   MSG TYPE=04
CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
ADDR=12345678901234567890
DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
2e cf 01 00 d0 02 83 01 f2 25 aa 0b
84 09 01 00 11 0a 19 49
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CDPA LENGTH
Called party address length
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

The SCCP received a message that was discarded because the global title field in the called party address was invalid in the EAGLE 5 ISS.

No action is necessary.

3.3.30 1030 - Inh EIR SS request already outstanding

An inh-map-ss command is already entered and queued.

For more information about the inh-map-ss command, refer to the Commands Manual.

Example 
RLGHNCXA21W 03-08-18 19:09:14 EST  EAGLE 31.3.0
0140.1030  CARD 1201  INFO  Inh EIR SS request already outstanding

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.31 1031 - Failure Inhibiting EIR SS

The inh-map-ss command was unsuccessful in taking the EIR subsystem off-line. For more information about the inh-map-ss command, refer to the Commands Manual.

Example 
RLGHNCXA21W 03-08-18 19:09:14 EST  EAGLE 31.3.0
0140.1031  CARD 1201  INFO  Failure Inhibiting EIR SS

Alarm Level: No alarm condition. The message is informational only.

Recovery

Enter the inh-map-ss command specifying the force=yes parameter.

3.3.32 1032 - Set ETS Mismatch

There is a discontinuity between the ETS broadcast and what the card expects. A discontinuity can occur when both OAM cards are booted at the same time and ETS gets reset to zero.

Example 
RLGHNCXA21W 03-08-18 19:09:14 EST  EAGLE 31.3.0
0140.1032  CARD 1201  INFO  Set ETS Mismatch

Alarm Level: No alarm condition. The message is informational only.

Recovery

The affected LIM/ATM/STC card recalibrates to the new ETS value and should continue to operate correctly.

If not, this is a reference point for possible invalid timestamps to Sentinel.

3.3.33 1033 - SCCP rcvd inv Cld Party - bad network

The SCCP received a message from the network that it could not route and was discarded because of an invalid network indicator in the called party address.

Example 
RLGHNCXA21W 00-04-18 19:02:12 EST  EAGLE 31.3.0
0113.1033    CARD 1103,A1  INFO   SCCP rcvd inv Cld Party - bad network
SIO=03   OPC=001-001-001  DPC=002-002-002
CDPA LENGTH=000   MSG TYPE=04
CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
ADDR=12345678901234567890
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CDPA LENGTH
Called party address length
CGPA
Calling party address
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

This indicates that SCCP discarded a message because the network indicator (national or international) provided in the called party address is invalid in the EAGLE 5 ISS.

No action is necessary.

3.3.34 1034 - SCCP rcvd inv Cld Party - no SSN

The SCCP received a message from the network that it could not route and was discarded because no subsystem number was present in the called party address.

Example 
RLGHNCXA21W 00-04-18 19:02:41 EST  EAGLE 31.3.0
0114.1034    CARD 1201,A  INFO   SCCP rcvd inv Cld Party - no SSN
SIO=03   OPC=001-001-001  DPC=002-002-002
CDPA LENGTH=000   MSG TYPE=04
CDPA: AI=10 PC=003-003-003  SSN=005  TT=250 
ADDR=12345678901234567890
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CDPA LENGTH
Called party address length
CGPA
Calling party address
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

The sender of the discarded message is using an invalid message format.

If there is only one occurrence, no action is necessary. However, if the condition continues, there may be a problem at the node that is sending the invalid message. Contact that node and inform them of the problem.

3.3.35 1035 - SCCP rsp did not route - invalid GTI

This message indicates the SCCP response did not route because of an invalid GTI in the calling party of the query.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1035    CARD 1103,A     INFO    SCCP rsp did not route - invalid GTI
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1035    CARD 1103,A     INFO    SCCP rsp did not route - invalid GTI
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Change the message to include a valid GTI in the CGPA part of the query.

Specify GTI=2 for ANSI, and specify GTI=2 or GTI=4, as appropriate for ITU.

3.3.36 1036 - SCCP rsp did not route - invalid TT

This message indicates the SCCP response did not route because of an invalid TT in the calling party of the query.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1036    CARD 1103,A     INFO    SCCP rsp did not route - invalid TT
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1036    CARD 1103,A     INFO    SCCP rsp did not route - invalid TT
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Provision the CGPA TT in the GTT TT table using the ent-tt command.

3.3.37 1037 - SCCP rsp did not route - bad Xlation

This message indicates the SCCP response did not route because of an invalid translation in the calling party of the query.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1037    CARD 1103,A     INFO    SCCP rsp did not route - bad Xlation
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1037    CARD 1103,A     INFO    SCCP rsp did not route - bad Xlation
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Provision the CGPA GTA address in the GTT database using the ent-gtt command.

3.3.38 1038 - SCCP rsp did not route -SSP not True PC

This message indicates the SCCP response did not route because the SSP (OPC or CGPA Point Code) is not the True Point Code.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1038    CARD 1103,A     INFO    SCCP rsp did not route -SSP not True PC
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1038    CARD 1103,A     INFO    SCCP rsp did not route -SSP not True PC
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Change the message to use the True Point Code in the CGPA point code or OPC of the query.

Note:

The True Point Code is the primary PC of the route, not an ALIAS PC.

3.3.39 1039 - SCCP rsp did not route - bad Selectors

This message indicates the SCCP response did not route because of invalid selectors (e.g., GTI, TT, NP, NAI) in the calling party of the query.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1039    CARD 1103,A     INFO    SCCP rsp did not route - bad Selectors
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1039    CARD 1103,A     INFO    SCCP rsp did not route - bad Selectors
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Provision the CGPAGTI, TT, NP, and NAI in the EGTT selector table using the commands ent-gttsel (to assign global title selectors to a GTT set for EGTT) and ent-gttset (to specify the attributes for a new GTT set).

3.3.40 1040 - ITU <-> ANSI translation not supported

This message indicates an invalid translation PC type in attempting to cross the ANSI to ITU domain.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1040    CARD 1103,A     INFO    ITU <-> ANSI translation not supported
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1040    CARD 1103,A     INFO    ITU <-> ANSI translation not supported
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Change the translation PC type to not cross the domain (ANSI <-> ITU), by using the appropriate GTT/GTA commands.

Refer to the EPAP Administration Manual.

3.3.41 1041 - SCCP did not route -no SSN in msg or DB

This message indicates the SCCP message did not route because the SSN was not found in the message or translation data.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1041    CARD 1103,A     INFO    SCCP did not route -no SSN in msg or DB
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 

RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1041    CARD 1103,A     INFO    SCCP did not route -no SSN in msg or DB
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Change the message to include the CDPASSN in the message or provision the SSN in the translation table.

You can change the translation table by using the appropriate GTT (ent-gtt or ent-gta) or the EPAP commands.

Refer to the Commands Manual or the EPAP Administration Manual, respectively for details.

3.3.42 1042 - SCCP rcvd inv GT - bad Translation Type

The SCCP received a message from the network requiring global title translation but the message was discarded because the system did not recognize the translation type.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1042    CARD 1103,A     INFO    SCCP rcvd inv GT - bad Translation Type
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1042    CARD 1103,A     INFO    SCCP rcvd inv GT - bad Translation Type
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
AI
Address Indicator
CDPA LENGTH
Called party address length
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This indicates a SCCP message was received with an invalid global title.
    The translation type indicator was invalid in the EAGLE 5 ISS. If this message should have been routed (verified by the output shown above), continue to 2.
  2. Use the command rtrv-tt, and verify that the indicated translation type does not appear in the translation types table.
  3. If there is no entry for the translation type indicated in the message, and there should be, use the ent-tt command to add the translation type to the Eagle STP translation type table.

    Refer to the Database Administration Manual - Global Title Translation for more information about entering translation types.

3.3.43 1043 - SCCP did not route - bad translation

The SCCP did not route a message because it could not translate the global title. The message was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0241.1043    CARD 1101,A1  INFO      SCCP did not route - bad translation
                 SIO=03   OPC=1-200-2           DPC=3-054-4
                 CDPA LENGTH=019   MSG TYPE=04
                 CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                       ADDR=ABCDEF0123456789ABCDE
                 LSN=ABCD123
                 Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0241.1043    CARD 1101,A1  INFO      SCCP did not route - bad translation
                 SIO=03   OPC=1-200-2           DPC=3-054-4
                 CDPA LENGTH=019   MSG TYPE=04
                    GTT on CdPA used MOSMSGTA=9193802053
                 CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                       ADDR=ABCDEF0123456789ABCDE
                 LSN=ABCD123
                 Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
AI
Address Indicator
CDPA LENGTH
Called party address length
CGPA
Calling party address
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

The SCCP received a message with a global title translation it could not interpret.

The message was discarded. Check translations on the originating switch to determine the trouble.

3.3.44 1044 - SCCP did not route - DPC OOS

The SCCP did not route a message because the destination point code (DPC) was out-of-service (OOS). The message was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1044    CARD 1101,A1  INFO      SCCP did not route - DPC OOS
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1044    CARD 1101,A1  INFO      SCCP did not route - DPC OOS
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:1
Legend
ADDR
Address
AI
Address Indicator
CDPA LENGTH
Called party address length
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Check the route and linksets by entering the rept-stat-dstn and rept-stat-ls commands.
  2. Verify the link status using the rept-stat-slk command.
    For example, enter:
    rept-stat-slk:loc=:port=b
    Example of the output: 
    RLGHNCXA03W 00-09-27 17:00:36 EST  EAGLE 35.0.0
SLK     LSN          CLLI         PST           SST        AST
1203,B  nsp1         ls02clli     OOS-MT        Unavail     ----
   ALARM STATUS       =  No alarm
   UNAVAIL REASON     =  FL NA LI RI 
Command Completed.
  3. Check the UNAVAIL REASON field in the output of the rept-stat-slk command.
    UNAVAIL REASON codes:
    FL – The signaling link has a fault.
    NA – The signaling link is not aligned.
    LI – The signaling link has been inhibited locallyRI – The signaling link has been inhibited remotely.
    LB – The signaling link has been blocked locally.
    RB – The signaling link has been blocked remotely.
    FC – The signaling link is unavailable because of false congestion. RD (xx.xxx) – The signaling link is unavailable because of a restart delay to prevent signaling link oscillation. The number in parentheses indicates the amount of time, in seconds, remaining in the restart delay period. The link is restarted automatically after this amount of time has elapsed.
  4. If the UNAVAIL REASON indicates an alignment problem or fault, activate a loopback using the act-lpb command, or use a physical loopback.
    (For a V.35, you must use an appropriate physical V.35 loopback.) If the signaling link aligns, contact the far-end to correct the problem.
  5. If the UNAVAIL REASON still indicates an alignment problem or fault, check the status of the card by entering the rept-stat-card command for the specified card.
  6. If the rept-stat-card command indicates a problem with the card, reset the card by entering the init-card command with the specified card location.
    If the card still does not align, try first reseating the card, then replacing the card. Refer to the Maintenance Manual, Appendix A, Card Removal/Replacement Procedures.
    1. If the UNAVAIL REASON indicates a locally inhibited link, enter the unhb-slk command with the specified card location.
    2. If the UNAVAIL REASON indicates a locally blocked link, enter the ublk-slk command with the specified card location.
  7. Otherwise, this indicates a failure at the distant node.
    Routing to this node has been halted as a result of network management. Maintenance personnel should be aware of the OOS condition, but no action is necessary. Monitor the links to the DPC and verify the DPC status changes to IS-NR (In-Service - Normal).

3.3.45 1045 - SCCP did not route - DPC congested

The SCCP did not route a message because the destination point code (DPC) was congested. The message was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1045    CARD 1101,A1  INFO      SCCP did not route - DPC congested
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1045    CARD 1101,A1  INFO      SCCP did not route - DPC congested
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SS
Subsystem
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

This indicates an SCCP message was discarded due to congestion at a distant node. Maintenance personnel should monitor the network and verify the nodes congestion status changes to zero (no congestion).

Note:

A transfer controlled (TFC) should have been received on the link to indicate congestion to this node. When the congestion status changes, the congestion status indicator in the flow control messages indicates what message type priorities can be transmitted to the distant node. If the condition persists, follow normal company procedures in dealing with congestion at distant nodes.

3.3.46 1046 - SCCP didn't route - PC/SSN not in MAP tbl

SCCP did not route a message because the destination point code was not in the mated application (MAP) table. The message was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1046    CARD 1103,A     INFO    SCCP didn't route - PC/SSN not in MAP tbl
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1046    CARD 1103,A     INFO    SCCP did not route - DPC not in MAP tbl
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SS
Subsystem
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If the DPC indicated in the message should not be routed to, no further action is necessary.
  2. If the DPC should be routed to from the EAGLE 5 ISS, use the ent-map command to enter the DPC into the mated application (MAP) table.

3.3.47 1047 - SCCP did not route - SS OOS

The SCCP did not route a message because the destination subsystem (SSN) was Out-of -Service. The message was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1047    CARD 1101,A1  INFO      SCCP did not route - SS OOS
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1047    CARD 1101,A1  INFO      SCCP did not route - SS OOS
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SS
Subsystem
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

This indicates that an SCCP was discarded because the DPC SSN to which it was addressed to is out-of-service (OOS).

Contact the distant end node that this message refers to and verify that action is being taken to bring the SCCP back into service.

3.3.48 1048 - SCCP did not Route - SS Congested

The SCCP did not route a message because the subsystem was congested. The message was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1048    CARD 1101,A1  INFO      SCCP did not route -  SS congested
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1048    CARD 1101,A1  INFO      SCCP did not route -  SS congested
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SS
Subsystem
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

An SCCP message was discarded due to congestion at a subsystem.

Maintenance personnel should monitor the network and verify the subsystems congestion status changes to zero (no congestion).

3.3.49 1049 - SCCP did not route - SS not in MAP tbl

The SCCP did not route a message because the destination subsystem was not in the Mated Application (MAP) table. The message was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1049    CARD 1101,A1  INFO      SCCP did not route - SS not in MAP tbl
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0246.1049    CARD 1101,A1  INFO      SCCP did not route - SS not in MAP tbl
             OPC=1-200-2
             TRANSLATED PC=5-038-6           TRANSLATED SS=202
             CDPA LENGTH=019            MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                   ADDR=ABCDEF0123456789ABCDE
             LSN=ABCD123
             Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SS
Subsystem
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If the subsystem indicated in the message is not a mated application to the EAGLE 5 ISS, no further action is necessary.
  2. If the SCCP message should have been routed, use the ent-map command to add the subsystem number to the mated application (MAP) table.

3.3.50 1050 - SCCP-CNV: Unable to convert ANSI CDPA GT

This message indicates that a SCCP MSU contained an undefined CDPA PC. The GTCNVDFLT STP Option is not enabled.

Example 
5054.1050    CARD 1105     INFO    SCCP-CNV: Unable to convert ANSI CDPA GT
        SIO=83   OPC=   001-011-001    DPC=   001-001-001
        SCCP MSG TYPE=09   GTCNV:Cld ANSI->ITU fail
        CDPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=0
               TT=000  NP=--  NAI=---  ADDR=101010
               PC=--------------    SSN=024
        CGPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=0
               TT=001  NP=--  NAI=---  ADDR=654321
               PC=--------------    SSN=000
        LSN=lsa1111  GTTSET=(2)
        Report Date:09-01-05  Time:16:38:41
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG GYPE
Message type
optional text field
Optional text field providing additional information about the error. Possible text display and definitions may include:
INV DMA LEN=xxx
DMA Length too big or too small: After SCCP encoding of translated MSU DMA Length became too big or too small.
UNSUP Clg GTI=x
GTT attempted on Unsupported CgPA GTI=x
UNSUP Cld GTI=x
GTT attempted on Unsupported CdPA GTI=x
INV Clg GTI=x
GTT attempted on INV CgPA GTI=x
INV Cld GTI=x
GTT attempted on INV CdPA GTI=x
GTCNV:Cld ANSI->ITU fail
Invalid CdPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Clg ANSI->ITU fail
Invalid CgPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Cld ITU->ANSI fail
Invalid CdPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
GTCNV:Clg ITU->ANSI fail
Invalid CgPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Perform one of the following actions:
  • Enable the GTCNVDFLTSTP Option, which would cause a default GT conversion to occur.

    Refer to the Database Administration Manual - Global Title Translation for details.

  • Add the proper ANSI to ITU entry (matching TT) into the Default GT Conversion Table.

    Refer to the Database Administration Manual - Global Title Translation for details.

  • Add a wildcard ANSI to ITU entry into the Default GT Conversion Table.

    Refer to the Database Administration Manual - Global Title Translation for details.

3.3.51 1051 - SCCP-CNV: Unable to convert ANSI CGPA GT

This message indicates that a SCCP MSU contained an undefined CGPA PC. The GTCNVDFLT STP Option is not enabled.

Example 
tekelecstp 09-01-05 16:41:51 EDT  RAGLE 41.0
5058.1051    CARD 1105     INFO    SCCP-CNV: Unable to convert ANSI CGPA GT
             SIO=83   OPC=   001-011-001    DPC=   001-001-001
             SCCP MSG TYPE=09   GTCNV:Clg ANSI->ITU fail
             CDPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=0
                    TT=000  NP=--  NAI=---  ADDR=101010
                    PC=--------------    SSN=024
             CGPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=0
                    TT=001  NP=--  NAI=---  ADDR=654321
                    PC=--------------    SSN=000
             LSN=lsa1111  GTTSET=(2)
             Report Date:09-01-05  Time:16:41:51
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
optional text field
Optional text field providing additional information about the error. Possible text display and definitions may include:
INV DMA LEN=xxx
DMA Length too big or too small: After SCCP encoding of translated MSU DMA Length became too big or too small.
UNSUP Clg GTI=x
GTT attempted on Unsupported CgPA GTI=x
UNSUP Cld GTI=x
GTT attempted on Unsupported CdPA GTI=x
INV Clg GTI=x
GTT attempted on INV CgPA GTI=x
INV Cld GTI=x
GTT attempted on INV CdPA GTI=x
GTCNV:Cld ANSI->ITU fail
Invalid CdPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Clg ANSI->ITU fail
Invalid CgPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Cld ITU->ANSI fail
Invalid CdPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
GTCNV:Clg ITU->ANSI fail
Invalid CgPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Perform one of the following actions:
  • Enable the GTCNVDFLTSTP Option, which would cause a default GT conversion to occur.

    Refer to the Database Administration Manual - Global Title Translation for details.

    OR

  • Add the proper ANSI to ITU entry (matching TT) into the Default GT Conversion Table.

    Refer to the Database Administration Manual - Global Title Translation for details.

    OR

  • Add a wildcard ANSI to ITU entry into the Default GT Conversion Table.

    Refer to the Database Administration Manual - Global Title Translation for details.

3.3.52 1052 - SCCP-CNV: Unable to convert ITU CDPA GT

This message indicates that a SCCP MSU contained an undefined CDPA PC. The GTCNVDFLT STP Option is not enabled.

Example 
tekelecstp 09-01-05 16:22:30 EDT  EAGLE 41.0
5038.1052    CARD 1105     INFO    SCCP-CNV: Unable to convert ITU CDPA GT
             SIO=b3   OPC=   2-011-1        DPC=   1-001-1
             SCCP MSG TYPE=09   GTCNV:Cld ITU->ANSI fail
             CDPA:  NI=0  RI=0  GTI=02  SSNI=0  PCI=1
                    TT=000  NP=--  NAI=---  ADDR=111111
                    PC=   1-001-1        SSN=---
             CGPA:  NI=0  RI=0  GTI=02  SSNI=0  PCI=1
                    TT=000  NP=--  NAI=---  ADDR=654321
                    PC=   2-011-1        SSN=---
             LSN=lsn2111  GTTSET=(1)
             Report Date:09-01-05  Time:16:22:30
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
optional text field
Optional text field providing additional information about the error. Possible text display and definitions may include:
INV DMA LEN=xxx
DMA Length too big or too small: After SCCP encoding of translated MSU DMA Length became too big or too small.
UNSUP Clg GTI=x
GTT attempted on Unsupported CgPA GTI=x
UNSUP Cld GTI=x
GTT attempted on Unsupported CdPA GTI=x
INV Clg GTI=x
GTT attempted on INV CgPA GTI=x
INV Cld GTI=x
GTT attempted on INV CdPA GTI=x
GTCNV:Cld ANSI->ITU fail
Invalid CdPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Clg ANSI->ITU fail
Invalid CgPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Cld ITU->ANSI fail
Invalid CdPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
GTCNV:Clg ITU->ANSI fail
Invalid CgPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Perform one of the following actions:
  • Enable the GTCNVDFLT STP Option, which would cause a default GT conversion to occur.

    Refer to the Database Administration Manual - Global Title Translation for details.

    OR

  • Add the proper ANSI to ITU entry (matching NP/NAI/TT) into the Default GT Conversion Table.

    Refer to the Database Administration Manual - Global Title Translation for details.

    OR

  • Add a wildcard ITU to ANSI entry into the Default GT Conversion Table.

    Refer to the Database Administration Manual - Global Title Translation for details.

3.3.53 1053 - SCCP-CNV: Unable to convert ITU CGPA GT

This message indicates that a SCCP MSU contained an undefined CGPA PC. The GTCNVDFLT STP Option is not enabled.

Example 
tekelecstp 08-12-26 15:17:59 EDT  EAGLE 41.0
5007.1053    CARD 1105     INFO    SCCP-CNV: Unable to convert ITU CGPA GT
             SIO=83   OPC=   2-011-1        DPC=   1-001-1
             SCCP MSG TYPE=09   INV Clg GTI=1
             CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=0
                    TT=000  NP=--  NAI=---  ADDR=123456
                    PC=--------------    SSN=008
             CGPA:  NI=0  RI=0  GTI=01  SSNI=1  PCI=1
                    TT=---  NP=--  NAI=000  ADDR=000000000000000000000
                    PC=   2-011-1        SSN=008
             LSN=lsn2111  GTTSET=(1)
             Report Date:08-12-26  Time:15:17:59
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
optional text field
Optional text field providing additional information about the error. Possible text display and definitions may include:
INV DMA LEN=xxx
DMA Length too big or too small: After SCCP encoding of translated MSU DMA Length became too big or too small.
UNSUP Clg GTI=x
GTT attempted on Unsupported CgPA GTI=x
UNSUP Cld GTI=x
GTT attempted on Unsupported CdPA GTI=x
INV Clg GTI=x
GTT attempted on INV CgPA GTI=x
INV Cld GTI=x
GTT attempted on INV CdPA GTI=x
GTCNV:Cld ANSI->ITU fail
Invalid CdPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Clg ANSI->ITU fail
Invalid CgPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Cld ITU->ANSI fail
Invalid CdPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
GTCNV:Clg ITU->ANSI fail
Invalid CgPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Perform one of the following actions:
  • Enable the GTCNVDFLT STP Option, which would cause a default GT conversion to occur.

    Refer to the Database Administration Manual - Global Title Translation for details.

    OR

  • Add the proper ANSI to ITU entry (matching NP/NAI/TT) into the Default GT Conversion Table.

    Refer to the Database Administration Manual - Global Title Translation for details.

    OR

  • Add a wildcard ITU to ANSI entry into the Default GT Conversion Table.

    Refer to the Database Administration Manual - Global Title Translation for details.

3.3.54 1054 - SCCP rcvd inv LSS - bad SSN

The SCCP received a message destined to a local subsystem that was discarded because of a bad subsystem number (SSN).

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0241.1054    CARD 1101,A1  INFO      SCCP rcvd inv LSS - bad SSN
                 SIO=03   OPC=1-200-2           DPC=3-054-4
                 CDPA LENGTH=019   MSG TYPE=04
                 CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                       ADDR=ABCDEF0123456789ABCDE
                 LSN=ABCD123
                 Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0241.1054    CARD 1101,A1  INFO      SCCP rcvd inv LSS - bad SSN
                 SIO=03   OPC=1-200-2           DPC=3-054-4
                 CDPA LENGTH=019   MSG TYPE=04
                    GTT on CdPA used MOSMSGTA=9193802053
                 CDPA: AI=05 PC=1-050-1          SSN=006 TT=007
                       ADDR=ABCDEF0123456789ABCDE
                 LSN=ABCD123
                 Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
gti
Global title indicator
LSN
Linkset name. The name must be unique.
msg type
Message type
nai
Nature of address indicator
ni
Network indicator value
np
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
pci
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
ssni
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

The EAGLE 5 ISS supports only one subsystem.

All other local subsystem numbers are invalid. Check translations on the originating switch to determine the problem.

3.3.55 1055 - SCCP rcvd inv SCMG - bad AFTPC

SCCP received an SCCP management message (SCMG) that was discarded because of a bad affected point code (AFTPC). The point code does not appear in the EAGLE 5 ISS routing tables.

Example 
RLGHNCXA21W 00-04-18 19:04:15 EST  EAGLE 31.3.0
0124.1055    CARD 1106  INFO   SCCP rcvd inv SCMG - bad AFTPC
SIO=0a   OPC=004-031-000  DPC=000-071-000
SCMG: MSG TYPE=000  MSG LEN=003
AFTPC=004-219-000  AFTSS=000   MULT=000
LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG LEN
Message length
MSG TYPE
Message type
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
SCMG
SCCP management message
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify the point code in the message, and verify whether the point code is required to be in the EAGLE 5 ISS routing tables.
  2. If the point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  3. If the point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the point code to the EAGLE 5 ISS routing tables.
    Refer to the Database Administration Manual - SS7 for more information about the procedure used to enter point codes to the EAGLE 5 ISS routing tables.

3.3.56 1056 - SCCP rcvd inv SCMG - bad subsystem

SCCP received an SCCP management message (SCMG) that was discarded because of an invalid subsystem.

Example 
RLGHNCXA21W 00-04-18 19:04:15 EST  EAGLE 31.3.0
0124.1056    CARD 1106  INFO   SCCP rcvd inv SCMG - bad subsystem
SIO=0a   OPC=004-031-000  DPC=000-071-000
SCMG: MSG TYPE=000  MSG LEN=003
AFTPC=004-219-000  AFTSS=000   MULT=000
LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG LEN
Message length
MSG TYPE
Message type
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
SCMG
SCCP management message
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify the point code in the message, and verify the subsystem number as a valid SSN for the network.
  2. Add the subsystem number to the EAGLE 5 ISS map tables using the ent-map command.

3.3.57 1057 - SCCP rcvd inv SCMG - bad length

SCCP received an SCCP management message (SCMG) that was discarded because of an invalid length indicator.

SCCP received an SCCP/Subsystem congested (SSC) SCMG message (MSG TYPE=006) that was discarded because EAGLE does not support SSC procedures. However, for through switched SCMG, EAGLE handles SSC messages, and there should not be an issue.

Example 
RLGHNCXA21W 00-04-18 19:04:15 EST  EAGLE 31.3.0
0124.1057    CARD 1106  INFO   SCCP rcvd inv SCMG - bad length
SIO=0a   OPC=004-031-000  DPC=000-071-000
SCMG: MSG TYPE=000  MSG LEN=003
AFTPC=004-219-000  AFTSS=000   MULT=000
LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG LEN
Message length
MSG TYPE
Message type
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
SCMG
SCCP management message
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates an SCCP message was discarded due to an invalid length indicator.

No further action is necessary.

3.3.58 1058 - SCCP rcvd inv SCMG - bad msg type

SCCP received an SCCP management message (SCMG) that was discarded because of an invalid message type.

Example 
RLGHNCXA21W 00-04-18 19:05:37 EST  EAGLE 31.3.0
0128.1058    CARD 1106  INFO   SCCP rcvd inv SCMG - bad msg type
SIO=0a   OPC=004-034-000  DPC=000-000-000
SCMG: MSG TYPE=000  MSG LEN=003
AFTPC=004-219-000  AFTSS=000   MULT=000
LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG LEN
Message length
MSG TYPE
Message type
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
SCMG
SCCP management message
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

This indicates an SCCP message was discarded due to an invalid message type.

No further action is necessary.

3.3.59 1059 - Telnet terminal connection disconnected

Indicates that an established telnet connection on the EAGLE has disconnected.

Example 
RLGHNCXA21W 02-08-08 20:52:04 EST  EAGLE 39.0
5024.1059    CARD 1105     INFO      Telnet terminal disconnected.
             REASON=Remote End Unreachable
             RIPADDR=192.168.57.52
             RIPORT=2336
             LIPADDR=192.168.53.46
             LIPORT=23 
             Report Date:02-08-08  Time:20:52:04
Legend
LIPADDR
Local IP Address
LIPORT
Local TCP Port Number
REASON
REASON is only displayed when the reason for the disconnection is ping failure. The REASON field is not displayed if the disconnection is due to any other reason.
RIPADDR
Remote IP Address
RIPORT
Remote TCP Port Number

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.60 1060 - Map Screening cannot generate ATIER

This message is generated because the MSU passed the SCCP conversion before the MAP screening and is of a different domain than the OPC of the inbound MSU. Therefore, the MSU is discarded and the Any Time Interrogation error (ATIER) is not generated.

Example 
RLGHNCXA21W 00-11-18 18:59:23 EST  EAGLE 35.0.0
0018.1060 CARD 1103    INFO Map Screening cannot generate ATIER
OPC=001-001-001
CDPA:  NI=1     RI=0   GTI=04 SSNI=0  PCI=1
TT=250   NP=04  NAI=010  ADDR=123456789012345678901
PC=003-003-003  SSN=005
CGPA:  NI=1     RI=0   GTI=04 SSNI=0  PCI=1
TT=100   NP=07  NAI=012  ADDR=012345678901234567890
PC=001-001-001  SSN=004
Op-Code=61  Forbidden Param=N/A  Action=Discard
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
OP-CODE
Operation Code
PARAM
Parameter
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

The MSU indicated in the message was discarded.

No further action is necessary.

3.3.61 1061 - Meas Sync Not Allowed From Old Version

This UIM is generated when the secondary MCP receives measurements data from a primary MCP that is running an older version of the software. This message indicates that measurements data was discarded by the secondary MCP due to the version mismatch. This problem occurs during a system upgrade to a new release.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST  EAGLE 31.4.0
0140.1061  CARD 1201  INFO   Meas sync not allowed from old version

Alarm Level: No alarm condition. The message is informational only.

Recovery

This UIM should only occur during an upgrade.

Complete the upgrade per approved procedure.

3.3.62 1062 - String Data Dump

A screen set was created with too many rows.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    9912.1062    CARD 1113     INFO    a50 too large   
         Report Date:14-08-01  Time:13:32:14

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This message indicates that the screen set is too large to be loaded.
    Remove some of the entries (one entry at a time).
  2. If the screen set is still too large, use the rtrv-scrset command to see if there are any unnecessary entries already in the screen set that can be deleted.
  3. Retry adding to the screen set with the chg-scrset command.
    If the message appears again, your screen set is too large. Try a different screen set or change the existing screen set.

3.3.63 1063 - SCCP Screen Set is Too Large

The screen set is too large to fit on a LIM or SCCP card and has failed loading.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    5946.1063    CARD 1113     INFO    SCCP screen set is too large 
         Report Date:14-08-02  Time:17:01:45

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This message indicates the screen set is too large to be loaded to a LIM or SCCP.
    Remove some of the entries (one entry at a time).
  2. If the screen set is still too large, use the rtrv-scrset command to see if there are any unnecessary entries already in the screen set that can be deleted.
  3. Retry adding to the screen set with the chg-scrset command.
    If the message appears again, your screen set is too large. Try a different screen set or change the existing screen set.

3.3.64 1064 - GWS rcvd TFP, AFTPC not in routing tbl

The EAGLE 5 ISS has received a transfer controlled (TCP) for an affected point code (AFTPC) which does not appear in the EAGLE 5 ISS routing tables. The message was discarded by Gateway Screening (GWS).

Example 
RLGHNCXA21W 00-04-18 19:05:52 EST  EAGLE 31.3.0
0129.1064    CARD 1105,A  INFO   GWS rcvd TFP, AFTPC not in routing tbl SIO=b0   OPC=004-040-000  DPC=000-001-000
H0H1=41  AFTPC=099-099-003
SR=scrb   LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  • If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  • If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.65 1065 - GWS rcvd TFR, AFTPC not in Routing tbl

The EAGLE has received a transfer restricted (TFR) for an affected point code (AFTPC) which does not appear in the EAGLE routing tables. The message was discarded by gateway screening (GWS).

Example 
RLGHNCXA21W 00-04-18 19:05:57 EST  EAGLE 31.3.0
0130.1065    CARD 1201,A  INFO   GWS rcvd TFR, AFTPC not in routing tbl
SIO=b0   OPC=004-041-000  DPC=001-000-000
H0H1=43  AFTPC=099-099-003
SR=scrb   LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  • If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  • If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.66 1066 - GWS rcvd TFA, AFTPC not in routing tbl

The EAGLE 5 ISS has received a transfer allowed (TFA) for an affected point code (AFTPC) that does not appear in the EAGLE 5 ISS routing tables. The message was discarded by the gateway screening (GWS) feature.

Example 
RLGHNCXA21W 00-04-18 19:06:35 EST  EAGLE 31.3.0
0131.1066    CARD 1201,A  INFO   GWS rcvd TFA, AFTPC not in routing tbl
SIO=b0   OPC=004-042-000  DPC=002-000-000
H0H1=45  AFTPC=099-099-003
SR=scrb   LSN=A1234567

Legend

AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  • If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  • If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.67 1067 - GWS rcvd UPU, AFTPC not in routing tbl

The EAGLE 5 ISS has received a user part unavailable (UPU) for an affected point code (AFTPC) which does not appear in the EAGLE 5 ISS routing tables. The message was discarded by gateway screening (GWS).

Example 
RLGHNCXA21W 00-04-18 19:06:42 EST  EAGLE 31.3.0
0132.1067    CARD 1201,A  INFO   GWS rcvd UPU, AFTPC not in routing tblSIO=90   OPC=004-043-000  DPC=002-000-000
H0H1=A1  AFTPC=099-099-003
SR=scrb   LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  • If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  • If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.68 1068 - GWS rcvd RSP, AFTPC not in Routing tbl

The EAGLE 5 ISS has received a signaling route set test prohibited message (RSP) for an affected point code (AFTPC) which does not appear in the EAGLE 5 ISS routing tables. The message was discarded by gateway screening (GWS).

Example 
RLGHNCXA21W 00-04-18 19:06:48 EST  EAGLE 31.3.0
0133.1068    CARD 1201,A  INFO   GWS rcvd RSP, AFTPC not in routing tbl SIO=b0   OPC=004-044-000  DPC=008-010-000
H0H1=51  AFTPC=099-099-003
SR=scrb   LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  • If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  • If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.69 1069 - GWS rcvd RSR, AFTPC not in routing table

The EAGLE 5 ISS has received a signaling route test set restricted (RSR) for an affected point code (AFTPC) which does not appear in the EAGLE 5 ISS routing tables. The message was discarded by gateway screening (GWS).

Example 
RLGHNCXA21W 00-04-18 19:07:27 EST  EAGLE 31.3.0
0134.1069   CARD 1201,A  INFO   GWS rcvd RSR with AFTPC not in routing tbl
SIO=b0   OPC=004-045-004  DPC=002-072-002
H0H1=52  AFTPC=099-099-003
SR=scrb   LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  • If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  • If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.70 1070 - SLTC failure: invalid Point Code (OPC)

The signaling link test control has reported an invalid point code in the signaling link test message (SLTM) received from the far end. The point code for the adjacent signaling point does not match the point code in the adjacent point code field in the linkset table.

Example 
RLGHNCXA21W 00-04-18 19:08:05 EST  EAGLE 31.3.0
0135.1070    CARD 1201,A  INFO   SLTC failure: invalid Point Code (OPC)SIO=0a   OPC=003-236-000  DPC=000-071-000
LSN=A1234567
Legend
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter this command to display the linkset names and the adjacent point codes: rtrv-ls
    Example of the output: 
    RLGHNCXA03W 00-06-10 11:43:04 EST EAGLE 35.0.0
                                 L3T SLT              GWS GWS GWS
LSN          APCA   (SS7)  SCRN  SET SET BEI LST LNKS ACT MES DIS SLSCI NIS
lsa1         240-020-000   none  1   1   no  A   1    off off off no    off
lsa2         240-030-000   none  1   1   no  A   3    on  on  on  yes   off
     
Link set table is (114 of 255)  45 % FULL
  2. The adjacent point code should match the adjacent point code in the message (004-046-000, for example).
    If it does not match, the link is not physically connected to the adjacent node. Determine the correct linkset name and adjacent point code. Use the ent-ls command to enter the correct information in the linkset table.

3.3.71 1071 - SLTC failure: invalid SLC

The signaling link test control has reported an invalid signaling link code (SLC) in the signaling link test message (SLTM) received from the far end.

Example 
RLGHNCXA21W 00-04-18 19:08:13 EST  EAGLE 31.3.0
0136.1071    CARD 1201,A  INFO   SLTC failure: invalid SLC
ADJ PC=004-046-000    SLC=02     LEN=0f
DATA= 01 02 03 04 05 06 07 08 09 11 12 13 14 15
Legend
ADJ PC
Adjacent point code
DATA
Information from the upper layers of SCCP management
LEN
Data length
SLC
Signaling link code

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact the far-end to make sure both ends have provisioned the same SLC for the signaling link.

3.3.72 1072 - SLTC failure: no response

The signaling link test control has reported “No Response” received for a signaling link test message (SLTM) sent to the far end.

Example 
tekelecstp 13-07-11 06:06:31 EST  EAGLE5 44.0.4-64.34.24 
5757.1072    CARD 4205,B1  INFO    SLTC failure: no response

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact the far-end to find out why there is no response to the SLTM.

3.3.73 1073 - SLTC failure: bad data pattern

The signaling link test control has detected an invalid data pattern in the signaling link test message (SLTM) received from the far end.

Example 
RLGHNCXA21W 00-04-18 19:08:28 EST  EAGLE 31.3.0
0138.1073    CARD 1201,A  INFO   SLTC failure:bad data pattern
ADJ PC=004-046-000    SLC=02     LEN=0f
DATA= 01 02 03 04 05 06 07 08 09 11 12 13 14 15
Legend
ADJ PC
Adjacent point code
DATA
Information from the upper layers of SCCP management
LEN
Data length
SLC
Signaling link code

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact the far-end and use your company procedures to test the facilities for the signaling link.

3.3.74 1074 – MSU Arrived on Wrong SM Card

SCCP MSU ended up on an Service Module card, which does not contain the needed RIDB/RTDB table (ELAP, DN, or IMSI).

Format

“MSU for xxxx needs ExAP yyyy data”

where xxxx = Service Name (LNP, INPQ, INPMR, VFLEX, IDPR, IAR, APORT, GPORT, TATI, ATINPQ, SMSMR, GFLEX, EIR), ExAP = ELAP/EPAP, and Yyyy = IMSI/DN

Example 
0226.1074    CARD 1101,A1  INFO      MSU for INPMR needs EPAP DN data
                 SIO=05   OPC=1-200-2           DPC=3-054-4
                 CDPA: AI=05  SSN=006  TT=007
                       ADDR=ABCDEF0123456789ABCDE
                 CGPA: AI=14  PC=2-054-2            SSN=022
                 DATA=3a e2 38 c7 04 e7 04 35 ae e8 30 e9
                      2e cf 01 00 d0 02 83 01 f2 25 aa 0b
                      84 09 01 00 11 0a 19 49
                 LSN=ABCD123
                 Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is only informational and MSU will be discarded.

Recovery: Make sure that the EAGLE has the SM card available for the service for which UIM is generated.

3.3.75 1075 - MTP: Link Bypassed SLT Phase

The link has aligned and may be brought into service without a successful signaling link test (SLT).

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST  EAGLE 31.3.0
0140.1075    CARD 1201,A  INFO   MTP: link bypassed SLT phase

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the rtrv-slk command with the card location and port shown in this message (for example, card location 1201, port A).
    Example of the output: 
    tekelecstp 00-02-19 21:17:04 EST EAGLE 35.0.0
rtrv-slk:loc = 1202:port = a
Command entered at terminal #3. 
tekelecstp 94-02-19 21:17:04 EST EAGLE 35.0.0
                                       L2T         L1               PCR  PCR
LOC  PORT LSN         SLC TYPE     SET  BPS    MODE TSET  ECM   N1   N2
1201 A    lsa1         0  LIMV35   2    64000  DTE  ---   PCR   ---  3800
  2. Use the rtrv-ls command using the linkset name (lsn) displayed in the output of 1 .
    Example of the output: 
    >  rtrv-ls:lsn = lsa1
tekelecstp 00-06-10 11:43:04 EST EAGLE 35.0.0
                           SCR   L3T  SLT
    LSN       APCA (SS7)   SET   SET  SET BEI  LST LNKS GWSA GWSM GWSD DOMAIN
    lsa1      240-020-000  scr1  1    1   yes  A   4    off  off  off  SS7
              TFATCABMLQ
              2
                                      L2T          L1              PCR  PCR 
              LOC   PORT SLC TYPE     SET  BPS    MODE TSET  ECM   N1   N2
              1201  a    3   LIMV35   2    64000  DTE  ---   BASIC ---  -----
              1205  b    0   LIMDS0   1    56000  ---  ---   BASIC ---  -----
                b    1   LIMOCU   1    56000  ---  ---   BASIC ---  -----
              1211  a    2   LIMDS0   1    56000  ---  ---   BASIC ---  -----
    Link set table is (114 of 255) 45% full.
  3. Enter the rtrv-slt command with the sltset parameter and the value shown in the SLTSET column from the output of Step 2 to determine whether the signaling link test message is on or off.
  4. If the signaling link test message is off, enter the chg-slt command with the sltset parameter and the value used in Step 3, and the enabled=on parameter.
  5. If the signaling link test message is on, enter the rept-stat-card command to verify the status of the card that contains the specified signaling link.
    The status of the card should be IS-NR (In-Service - Normal).
  6. If the card is out of service, put it back into service by entering the rst-card command.
  7. If the fault is not cleared, enter the rept-stat-slk command to verify the status of the signaling link.
    The status of the signaling should be IS-NR (In-Service - Normal).
  8. If the signaling link is out of service, enter the act-slk command to put the signaling link back into service.
  9. If the fault is not cleared, enter the tst-slk command specifying the signaling link that generated this message.
  10. If the fault is not cleared, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.76 1076 - SLTC Failure: Invalid Point Code (DPC)

The signaling link test control (SLTC) has detected an invalid data pattern in the signaling link test message (SLTM) received from the adjacent point code.

Example 
RLGHNCXA21W 00-04-18 19:09:22 EST  EAGLE 31.3.0
0141.1076    CARD 1201,A  INFO   SLTC failure:invalid Point Code (DPC)
ADJ PC=004-046-000   SLC=02     LEN=0f
DATA= 01 02 03 04 05 06 07 08 09 11 12 13 14 15
Legend
ADJ PC
Adjacent point code
DATA
Information from the upper layers of SCCP management
LEN
Data length
SLC
Signaling link code

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact the far-end and use local procedures to test the facilities for the signaling link.

3.3.77 1077 - GTT Action TCAP ERROR DISCARDED MSU

This UIM indicates that the TCAP Error Action executed and UIMREQD is ON.

There are two cases in which this alarm is generated:
  1. When this GTT Action (DISC, UDTS or TCERR) is provisioned as the main GTT Action for the translation (GTA)
  2. When this GTT Action (DISC, UDTS or TCERR) is provisioned as the default action (ENT/CHG-GTTACT:DEFACTID) for some other GTT Action (FWD, DUP, SFTHROT or SCPVAL) that is provisioned for the translation (GTA), and this default action is executed when the main GTT Action fails.

When these DISCARD Actions are executed as main GTT Action for the translation, the output will look like the following example:

Example 
6053.1077    CARD 1101     INFO    GTT Action TCAP ERROR DISCARDED MSU
             OPC=   1-001-4        DPC=   1-001-5
             CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                    TT=010  NP=--  NAI=---  ADDR=9818316478
                    PC=   1-001-1        SSN=016
             CGPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                    TT=011  NP=--  NAI=---  ADDR=9910929095
                    PC=   1-002-3        SSN=049
             Op-Code=--- Action Set=tcapset
             Report Date:03-01-03  Time:16:45:01

When these DISCARD Actions are executed as the "failure outcome" of the main GTT Action for the translation, this UIM generates an additional line displaying the cause of that main GTT Action failing:

Example 
tekelecstp 15-12-08 13:55:11 MST  EAGLE5 46.3.0.0.0-66.18.1
6053.1077    CARD 1101     INFO    GTT Action TCAP ERROR DISCARDED MSU
             Cause: SMRPOA-CGPA Digits Mismatch
             OPC=   1-001-4        DPC=   1-001-5
             CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                    TT=010  NP=--  NAI=---  ADDR=9818316478
                    PC=   1-001-1        SSN=016
             CGPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                    TT=011  NP=--  NAI=---  ADDR=9910929095
                    PC=   1-002-3        SSN=049
             Op-Code=--- Action Set=tcapset
             Report Date:15-12-08  Time:13:55:11
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
OP-CODE
Operation Code
PARAM
Parameter
PC
Point code for the SS7 end user
PCI
Protocol control information
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery:

  1. To prevent the MSU from being discarded post-GTT, remove the "TCAP Error" GTT action associated with the GTT translation.
    If you want to suppress this UIM, turn off the UIMREQD option for the given “TCAP ERROR” GTT action.

3.3.78 1078 - GTT Action Duplicate Failed

This UIM indicates that the EAGLE 5 ISS failed to route or prepare Duplicate MSU for the reason indicated in the UIM.

Example 
6618.1078    CARD 1105     INFO    GTT Action DUPLICATE FAILED
             OPC=   1-001-4        DPC=   001-001-002
             CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=0
                    TT=200  NP=--  NAI=---  ADDR=123456
                    PC=--------------    SSN=005
             CGPA:  NI=0  RI=0  GTI=02  SSNI=0  PCI=1
                    TT=010  NP=--  NAI=---  ADDR=234567
                    PC=--------------    SSN=---
             Op-Code=--- Action Set=aset1
             Cause=CLG PC Conv fail
             Report Date:03-04-27  Time:07:42:09
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
OP-CODE
Operation Code
PARAM
Parameter
PC
Point code for the SS7 end user
PCI
Protocol control information
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery:

The cause of the error is included as a reason string in the UIM. Refer to the following table for the recovery steps:

Table 3-7 Error Recovery

Cause Recovery
CDPA GTMOD Failure

CdPA GT Modification failed resulting in Forward action failure.

Correct the GT Modification data in CDGTMODID associated with the GTT Action.

CGPA GTMOD Failure

CgPA GT Modification failed resulting in Forward action failure.

Correct the GT Modification data in CGGTMODID associated with the GTT Action.

Encoding Failure

Encoding of forward MSU failed resulting in Forward action failure.

The True PC for the DPC or EAGLE for destination Network must be configured AND/OR The SCCP data (GTI/SSN) must be corrected such that the message length does not exceed the Maximum MSU length limit.

MAP Lookup Failure

Error in MAP load sharing caused Forward action failure.

Configure the DPC/SSN displayed in UIM within the MAPSETID associated with GTT Action. OR Configure correct MAP SETID (which contains the DPC/SSN displayed in UIM) in GTT Action entry.

Routing Failure

Error in routing the forward MSU caused Forward action failure.

The route for DPC must be provisioned and at least one route to the DPC must be available.

DFLT GT Conv Failure

Default GT conversion failed while creating Forward MSU.

Provision correct Default GT Conversion data for successful network conversion of the MSU.

CLG PC Conv fail

Error in conversion of Calling PC.

Provision correct Conversion data for Calling PC for successful network conversion of the MSU.

Unknown Error

Error in creating Forward MSU for any other reason.

Correct the data associated with Forward GTT Action.

3.3.79 1079 - GTT Action Forward Failed

This UIM indicates that the EAGLE 5 ISS failed to route or prepare Forward MSU for the reason indicated in the UIM.

Example 
6618.1079    CARD 1105     INFO    GTT Action FORWARD FAILED
             OPC=   1-001-4        DPC=   001-001-002
             CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=0
                    TT=200  NP=--  NAI=---  ADDR=123456
                    PC=--------------    SSN=005
             CGPA:  NI=0  RI=0  GTI=02  SSNI=0  PCI=1
                    TT=010  NP=--  NAI=---  ADDR=234567
                    PC=--------------    SSN=---
             Op-Code=--- Action Set=aset1
             Cause=CLG PC Conv fail
             Report Date:03-04-27  Time:07:42:09
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
OP-CODE
Operation Code
PARAM
Parameter
PC
Point code for the SS7 end user
PCI
Protocol control information
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery:

The cause of the error is included as a reason string in the UIM. Refer to Table 3-8 for the recovery steps.

Table 3-8 Error Recovery

Cause Recovery
CDPA GTMOD Failure

CdPA GT Modification failed resulting in Forward action failure.

Correct the GT Modification data in CDGTMODID associated with the GTT Action.

CGPA GTMOD Failure

CgPA GT Modification failed resulting in Forward action failure.

Correct the GT Modification data in CGGTMODID associated with the GTT Action.

Encoding Failure

Encoding of forward MSU failed resulting in Forward action failure.

The True PC for the DPC or EAGLE for destination Network must be configured AND/OR The SCCP data (GTI/SSN) must be corrected such that the message length does not exceed the Maximum MSU length limit.

MAP Lookup Failure

Error in MAP load sharing caused Forward action failure.

Configure the DPC/SSN displayed in UIM within the MAPSETID associated with GTT Action. OR Configure correct MAP SETID (which contains the DPC/SSN displayed in UIM) in GTT Action entry.

Routing Failure

Error in routing the forward MSU caused Forward action failure.

The route for DPC must be provisioned and at least one route to the DPC must be available.

DFLT GT Conv Failure

Default GT conversion failed while creating Forward MSU.

Provision correct Default GT Conversion data for successful network conversion of the MSU.

CLG PC Conv fail

Error in conversion of Calling PC.

Provision correct Conversion data for Calling PC for successful network conversion of the MSU.

Unknown Error

Error in creating Forward MSU for any other reason.

Correct the data associated with Forward GTT Action.

3.3.80 1080 - disk measurement status unreadable

The active MASP could not determine the measurement collection status so that the measurements task could perform routine polling and measurement collection. If the measurement collection status cannot be determined, the routine polling and measurement collection tasks cannot be performed.

Example 
RLGHNCXA21W 00-04-18 19:10:54 EST  EAGLE 31.3.0
0145.1080    CARD 1116  INFO   disk measurement status unreadable

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the rept-meas command.
    If the rept-meas command fails, a system problem is the likely cause.
    1. If any messages are generated with the rept-meas command failure, take the appropriate action for that message.
    2. If no messages are generated, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.
  2. If the rept-meas command is rejected with a system busy message, the disk is reserved by another command (for example, copy-disk).
    Check to see if another command is running (copy-disk or a chg-db command).

3.3.81 1081 - MTP: Changeback T5 Timeout

When a link changes back, the EAGLE 5 ISS sends up to six changeback declaration messages and starts the T4 timer. The EAGLE 5 ISS waits for a changeback acknowledgment message for each of these declarations. If the T4 timer expires before the EAGLE 5 ISS receives an acknowledgment message, the EAGLE 5 ISS sends the changeback declaration message again and starts the T5 timer. If the T5 timer expires before the EAGLE 5 ISS receives an acknowledgment message, this message is generated and the EAGLE 5 ISS restarts traffic on the link.

Example 
RLGHNCXA21W 00-04-18 19:11:03 EST  EAGLE 31.3.0
0146.1081    CARD 1105, A  INFO   MTP: Changeback T5 timeout

Alarm Level: No alarm condition. The message is informational only.

Recovery

The system restarts traffic and no further action is necessary.

3.3.82 1082 - Amem single bit error report

This message indicates that an SCCP, GLSHC, SIP or S13 (DEIR) card encountered a single bit dynamic ram error. This message gives the user a record of single bit errors for the last 24 hours.

Example 
RLGHNCXA21W 14-05-18 19:12:00 EST  EAGLE 46.0.0
0147.1082    CARD 1101     INFO   Amem single bit error report
Any Errors   : YES  current hour-------v
24 Hour History : NNNYNN NNNNNN NNNNYN NYNNNY

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that the error was encountered and corrected.

If many errors are reported then the card may be beginning to fail and should be targeted for replacement in the future.

3.3.83 1083 - REPT COND: system alive

This message is a periodic system message indicating that the system is alive.

Example 
RLGHNCXA21W 00-04-18 19:12:00 EST  EAGLE 31.3.0
0147.1083    SYSTEM     INFO   REPT COND: system alive

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.84 1084 - GWS MSU discarded by redirect function

This message indicates that an MSU has been discarded rather than redirected to the SCP as part of the Database Transport Access (DTA) feature.

Example 
RLGHNCXA21W 00-04-18 19:12:00 EST  EAGLE 31.3.0
0003.1084    CARD 1205,A   INFO   GWSMSU discarded by redirect function SIO=01 OPC=003-237-002 DPC=006-006-000
SR=scrb
LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TN
Telephone number
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Check to see if the redirect function is disabled by entering the following: rtrv-gws-redirect
  2. If the enabled parameter is set to OFF as in the following output, the redirect function needs to be enabled. 
    RLGHNCXA03W 00-02-10 11:43:04 EST EAGLE 35.0.0
ENABLED DPC RI SSN TT GTA
 
off 001-030-001 GT 10 25 1800833
  3. Enter the following command to enable the redirect function: chg-gws-redirect:enabled=on

3.3.85 1085 - GWS MSU too large to be redirected

This message indicates that the system tried to encapsulate an MSU for redirection to an SCP (as part of the Database Transport Access feature).

The DTA feature encapsulates the entire data packet including level 2 MTP. Because the DTA feature requires approximately 24 octets, the original packet can contain a maximum of about 248 octets of “user data.” If the size of the data is larger, the MSU cannot be redirected and is routed to its original destination.

Example 
RLGHNCXA21W 00-04-18 19:12:00 EST  EAGLE 31.3.0
0003.1085    CARD 1205,A   INFO   GWSMSU too large to be redirected
SIO=01 OPC=003-237-002 DPC=006-006-000
SR=scrb
LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TN
Telephone number
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If MSUs are frequently discarded, there may be a problem on the origination end.
    To determine the number of MSUs that are discarded because the MSU is too large to be encapsulated, enter the following command:
    rept-meas:type=systot:enttype=stp:period=last
  2. Check the DTAMSULOST report in the output message.
    If the number of discarded MSUs is low, no further action is necessary. If large quantities are MSUs are lost, the originating node may need to be reconfigured.

3.3.86 1086 - LFS Test Aborted with OAM Switch Over

The link fault sectionalization (LFS) test aborted with OAM switch over.

Example 
RLGHNCXA21W 14-05-18 19:11:03 EST  EAGLE 46.0.0
1111.1086 CARD 1115 LFS test terminated with OAM switch over

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.87 1087 - MTP RSTRT rcvd Unexpected User Traffic

This message indicates the system encountered traffic during the MTP restart process.

Example 
RLGHNCXA21W 00-04-18 19:12:00 EST  EAGLE 31.3.0
0147.1087    CARD 1101    INFO   MTP RSTRT rcvd unexpected user traffic
Report Date:00-03-30      Time:  16:27:19 

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that the error was encountered.

3.3.88 1088 - REPT-MTP-RSTRT MTP Restart Started

This message indicates that a full MTP Restart has begun.

Example 
RLGHNCXA21W 00-04-18 19:12:00 EST  EAGLE 31.3.0
0147.1088    CARD 1101    INFO   REPT-MTP-RSTRT MTP Restart started
Report Date:00-03-30      Time:  16:27:19  

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that MTP Restart has begun.

3.3.89 1089 - RCVRY-MTP-RSTRT MTP Restart Completed

This message indicates a full MTP Restart is complete.

Example 
RLGHNCXA21W 00-04-18 19:12:00 EST  EAGLE 31.3.0
0147.1089    CARD 1101    INFO   RCVRY-MTP-RSTRT MTP Restart completed
             Report Date:00-03-30      Time:  16:27:19 

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that MTP Restart is complete.

3.3.90 1090 - ITU GWY:CPC conversion failure

This message indicates a protocol conversion failure. There are three possible reasons for the conversion failure.

  • The point code was not in the database.

  • The appropriate point code type was unavailable. There is no true point code or alias point code that matches the CPC.

  • The database is corrupted. The master database and the card database must be synchronized.

Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0010.1090    CARD 1205,B  INFO  ITU GWY: CPC conversion failure
SIO=0a   OPC=3-236-1  DPC=1-014-2
CPC=3-095-6  
LSN=A1234567890
Legend
CPC
Capability point code
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Check the database to make sure the card database is synchronized with the master database.
    Enter the rept-stat-db:display=except command. If the databases are not synchronized, reload the card data by initializing the card. If the databases are synchronized, go to Step 2.
  2. Enter the rtrv-dstn:dpccommand.
    If the rtrv-dstn command fails, the point code is undefined or the destination point code is an alias and not a true point code.
  3. To verify that the point code is an alias, enter the rtrv-dstn:alias command.
    If the command succeeds, you must provision the database with the true point code using the chg-dstn:dpc=xxx:alias=yyycommand.
  4. If the point code is not an alias, you must define the point code using the ent-dstn:dpci=xxx:aliasi=yyy command.
  5. Check translations on the originating switch to determine the trouble.

3.3.91 1091 - ITU GWY:OPC conversion failure

This message indicates a protocol conversion failure. There are three possible reasons for the conversion failure.

  • The point code is not in the database.

  • The appropriate point code type was unavailable. There is no true point code or alias point code that matches the OPC.

  • The database is corrupted.

Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0010.1091    CARD 1205,B  INFO  ITU GWY: OPC conversion failure
SIO=0a   OPC=3-236-1  DPC=1-014-2
LSN=A1234567890
Legend
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Check the database to make sure the card database is synchronized with the master database.
    Enter the rept-stat-db:display=except command. If the databases are not synchronized, reload the card data by initializing the card. If the databases are synchronized, go to Step 2.
  2. Enter the rtrv-dstn:dpccommand.
    If the rtrv-dstn command fails, the point code is undefined or the destination point code is an alias and not a true point code.
  3. To verify that the point code is an alias, enter the rtrv-dstn:alias command.
    If the command succeeds, you must provision the database with the true point code using the chg-dstn:dpc=xxx:alias=yyycommand.
  4. If the point code is not an alias, you must define the point code using the ent-dstn:dpci=xxx:aliasi=yyy command.

3.3.92 1092 - ITU GWY:HOH1 conversion failure

This message occurs when there is an ANSI message with no ITU equivalent. Table 3-9 shows the ANSI messages with no ITU equivalent.

Table 3-9 ANSI Messages with No ITU Equivalent

Message H0/H1 Code (Hex)
Transfer Restricted (TFR) when generated by an ITU National network 43
Transfer-Cluster Restricted (TCR) 44
Transfer-Cluster Allowed (TCA) 46
Transfer-Cluster Prohibit Signal (TCP) 42
Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0010.1092    CARD 1205,B  INFO  ITU GWY: H0H1 conversion failure
SIO=08   OPC=003-235-001  DPC=006-006-000
H0H1=42  
LSN=A1234567890
Legend
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

Check translations on the originating switch to determine the trouble.

3.3.93 1093 - ITU GWY:rcvd msg type cannot convert

This message indicates the STP received a message type that has no equivalent in the opposite protocol. Table 3-10 shows the list of message types that have no equivalents and are discarded.

Table 3-10 Message Type with No Opposite Protocol Equivalent

Message Type Code
Confusion Message (CNF) 2F
Connect Message (CONN) 07
Continuity Test Message (COT) 05
Continuity Check Request Message (CCR) 11
Information Message (INF) 04
Information Request Message (INR) 03
Loop Back Acknowledge Message (LPA) 24
Overload Message (OLM) 30
Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0110.1093    CARD 1205,B  INFO   ITU GWY:rcvd msg type cannot convert
SIO=0e  OPC=4-013-1      DPC=1-003-0
MSG TYPE=07
LSN=A1234567890
Legend
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

Check translations on the originating switch to determine the trouble.

3.3.94 1094 - ITU GWY:Invalid ISUP msg structure

This message indicates that an ISUP parameter or pointer to a parameter was invalid.

Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0110.1094    CARD 1205,B  INFO   ITU GWY:Invalid ISUP msg structure
SIO=0e  OPC=4-013-1      DPC=1-003-0
MSG TYPE=07
LSN=A1234567890
Legend
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that the error was encountered.

3.3.95 1095 - ITU GWY:GRS Buffer Full

This message indicates the circuit group reset (GRS) buffer is full.

Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0110.1095    CARD 1205,B  INFO   ITU GWY:GRS buffer full

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that the error was encountered.

3.3.96 1096 - ITU GWY:RSC Buffer Full

This message indicates the reset circuit (RSC) buffer is full.

Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0110.1096    CARD 1205,B  INFO   ITU GWY: RSC buffer full

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that the error was encountered.

3.3.97 1097 - ITU GWY:CGB Buffer Full

This message indicates the circuit group blocking (CGB) buffer is full.

Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0110.1097    CARD 1205,B  INFO   ITU GWY: CGB buffer full

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that the error was encountered.

3.3.98 1098 - Unexpected Disk Access Timeout

This message is used to determine whether there are problems with the disk access system.

Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0110.1098    CARD 1113    INFO   Unexpected disk access timeout

Alarm Level: No alarm condition. The message is informational only.

Recovery

If the target disk is the same CARD that corresponds to the GPSM-II, there is a software timing issue that needs to be addressed.

If the target disk is the mate GPSM-II/TDM or the removable and access is physically impossible, no action is necessary.

3.3.99 1099 - String Data Dump

This is a generic UIM. The informational message in the UIM varies.

Example 
FTP Transfer Failed due to network congestion

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.100 1100 - GWS rcvd H0/H1 that is not allowed

This message indicates the STP has received an H0/H1 that is not allowed.

Example 
RLGHNCXA21W 00-04-18 18:59:58 EST EAGLE 31.3.0
0105.1100    CARD 1201,A INFO GWS rcvd H0H1 that is not allowed
             SIO=02   OPC=009-009-009 DPC=006-006-006
             H0H1=01  AFTPC=255-009-009
             SR=osp3  LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TN
Telephone number
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that the error was encountered and corrected.

3.3.101 1101 - SDRAM Single Bit Error Report

This message indicates SDRAM memory on HIPR (or IMTPCI) is detecting Single Bit Errors (SBEs). This may be an indication that the card should be replaced (memory becoming faulty) before Multi Bit Errors (MBEs) begin to occur, which results in an OBIT of the card.

Example 
RLGHNCXA21W 02-07-21 16:20:19 EST EAGLE 35.0
    0024.1101    CARD 1109     INFO      SDRAM single bit error report
                 Any Errors      : YES     current hour------v  
                 24 Hour History : NNNYNN NNNNNN NNNNYN NYNNNY
                 Microengine Count : 12345678
                 PCI         Count : 12345678
                 StrongARM   Count : 12345678
                 Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

The card generating the error may need replacement. Refer to the Maintenance Manual for card removal/replacement procedures. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.102 1102 - Invalid Length for Map IMEI Parameter

This message indicates that the EIR subsystem received a Check-IMEI message in which the Map IMEI parameter had an invalid length.

Example 
RLGHNCXA21W 00-04-18 19:00:11 EST EAGLE 31.3.0
0107.1102    CARD 1103,A1 INFO Invalid Length for Map IMEI Parameter
             SIO=03   OPC=003-252-000 DPC=000-071-000
             CDPA:   AI=10 SSN=05 TT=250
                      ADDR=ABCDEF1234567890ABCDE
             CGPA:   AI=12 PC=001-001-001 SSN=002
             DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
                      2e cf 01 00 d0 02 83 01 f2 25 aa 0b
                      84 09 01 00 11 0a 19 49
             LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.103 1103 - LSS:No Map IMEI Parameter present

This message indicates that the EIR subsystem received a Check-IMEI message in which the Map IMEI parameter is not present.

Example 
RLGHNCXA21W 00-04-18 19:00:11 EST EAGLE 31.3.0
0107.1103 CARD 1103,A1 INFO LSS:No Map IMEI Parameter present
          SIO=03 OPC=003-252-000 DPC=000-071-000
          CDPA: AI=10 SSN=05 TT=250
                 ADDR=ABCDEF1234567890ABCDE
          CGPA: AI=12 PC=001-001-001 SSN=002
          DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
                   2e cf 01 00 d0 02 83 01 f2 25 aa 0b
                   84 09 01 00 11 0a 19 49
          LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.104 1104 - IP Connection Failed

Reports that either an attempt to connect to an IP server failed, or that a client socket failed to establish a connection with the system (IP7 Secure Gateway).

Example 
RLGHNCXA03W 99-04-10 16:28:08 EST EAGLE 35.0.0
0003.1104 DCM 1213,A IP Connection Failed
          RIPADDR = 123.123.123.123
          RPORT = 1314
          LIPADDR = 123.123.123.124
          LPORT = 1315
          SNAME=LONGSOCKETNAME1
          Report Date: 02-04-10 Time: 16:27:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

Reports on connection status can be obtained for each DCM card with the following commands:
  • pass:loc=xxxx:cmd=”connmgr -l” displays the connection manager event log.
  • pass:loc=xxxx:cmd=”connmgr -c” displays socket client data.
  • pass:loc=xxxx:cmd=”connmgr -s” displays socket server data.

3.3.105 1105 - REPT EVT:IMT GPL Reloading

This message indicates the IMT software download procedure is initiated. This is the first message that the system displays.

Example 
RLGHNCXA21W 00-04-18 18:59:58 EST EAGLE 31.3.0
0105.1105 SYSTEM INFO REPT EVT:IMT GPL reloading
          cards loaded : 1 of 25

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.106 1106 - REPT COND:IMT GPL Reloading

This message displays the progress of the IMT software downloading procedure.

Example 
RLGHNCXA21W 00-04-18 18:59:58 EST EAGLE 31.3.0
0105.1106 SYSTEM INFO REPT COND:IMT GPL reloading
          cards loaded : 10 of 25

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.107 1107 - SCCP XUDT (S) msg: Hop Counter violation

This message indicates that the incoming MSU has a Hop counter value of zero or greater than 15 and the F bit in the segmentation parameter is not set. An XUDTS error response is generated and sent to the originating node. The message is discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1107    CARD 1103,A     INFO    SCCP XUDT (S) msg: Hop Counter violation
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1107    CARD 1103,A     INFO    SCCP XUDT (S) msg: Hop Counter violation
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

The sender of the discarded message is using an invalid message format.

If there is only one occurrence, no action is necessary. However, if the condition continues, there may be a problem at the node that is sending the invalid message. Contact that node and inform them of the problem.

3.3.108 1108 - SCCP XUDT (S) msg: inv opt portion len

This message indicates that the incoming MSU has an invalid length in the optional portion (optional parameter length exceeding the MSU length or no end of optional parameters octet). The message is discarded.

Example 
RLGHNCXA21W 00-04-18 19:02:05 EST EAGLE 31.3.0
0112.1108 CARD 1103,A1 INFO SCCP XUDT (S) msg: inv opt portion len
            SIO=03 OPC=001-001-001 DPC=002-002-002
            SCCP MSG TYPE=04
            CDPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
                    TT=250 NP=04 NAI=010 ADDR=123456789012345678901
                    PC=003-003-003 SSN=005
            CGPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
                    TT=100 NP=07 NAI=012 ADDR=012345678901234567890
                    PC=001-001-001 SSN=004
            LSN=A1234567
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates an SCCP message was discarded due to an invalid length.

No further action is necessary.

3.3.109 1109 - SCCP XUDT(S) msg: inv segmentation parm

This message indicates that the length of the optional segmentation parameter is not equal to 6. The length of the segmentation parameter must be equal to 6. The message is discarded.

Example 
RLGHNCXA21W 00-04-18 19:02:05 EST EAGLE 31.3.0
0112.1109 CARD 1103,A1 INFO SCCP XUDT(S) msg: inv segmentation parm
            SIO=03 OPC=001-001-001 DPC=002-002-002
            SCCP MSG TYPE=04
            CDPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
                    TT=250 NP=04 NAI=010 ADDR=123456789012345678901
                    PC=003-003-003 SSN=005
            CGPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
                    TT=100 NP=07 NAI=012 ADDR=012345678901234567890
                    PC=001-001-001 SSN=004
            LSN=A1234567
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

This message indicates an SCCP message was discarded due to an invalid segmentation parameter.

No further action is necessary.

3.3.110 1110 - GWS rcvd AFTPC that is not allowed

This indicates that a message was received by a gateway link and failed DESTFLD screening because of an affected point code value in the message.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST EAGLE 35.0.0
0100.1110 CARD 1105,B INFO GWS rcvd AFTPC that is not allowed
          SIO=0a OPC=003-243-000 DPC=000-024-000
          H0H1=41 AFTPC=099-099-003
          SR=osp3 LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  2. If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  3. If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.111 1111 - GWS rcvd TCA, AFTPC not in routing tbl

This indicates that a TCA message was received by a gateway link and failed DESTFLD screening because of an affected point code value in the message.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST EAGLE 35.0.0
0100.1111 CARD 1105,B INFO GWS rcvd TCA, AFTPC not in routing tbl
SIO=0a OPC=003-243-000 DPC=000-024-000
H0H1=46 AFTPC=099-099-003
SR=osp3 LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  2. If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  3. If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.112 1112 - GWS rcvd TCR, AFTPC not in routing tbl

This indicates that a TCR message was received by a gateway link and failed DESTFLD screening because of an affected point code value in the message.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST EAGLE 35.0.0
0100.1112 CARD 1105,B INFO GWS rcvd TCR, AFTPC not in routing tbl
          SIO=0a OPC=003-243-000 DPC=000-024-000
          H0H1=44 AFTPC=099-099-003
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  2. If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  3. If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.113 1113 - GWS rcvd TCP, AFTPC not in routing tbl

This indicates that a TCP message was received by a gateway link and failed DESTFLD screening because of an affected point code value in the message.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST EAGLE 35.0.0
0100.1113 CARD 1105,B INFO GWS rcvd TCP, AFTPC not in routing tbl
          SIO=0a OPC=003-243-000 DPC=000-024-000
          H0H1=42 AFTPC=099-099-003
          SR=osp3 LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify the affected point code in the message, and verify whether the affected point code is required to be in the EAGLE 5 ISS routing tables.
  2. If the affected point code is not required to be in the EAGLE 5 ISS routing tables, no further action is necessary.
  3. If the affected point code is required to be in the EAGLE 5 ISS routing table, use the ent-dstn command to add the affected point code to the EAGLE 5 ISS routing tables.

3.3.114 1114 - Database BACKUP Started

A local database backup is beginning. This UIM follows the issue of the chg-db:action=backup command.

Example 
RLGHNCXA21W 00-06-18 19:12:00 EST EAGLE 31.3.0
0147.1114 CARD 1201,A INFO Database BACKUP started

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.115 1115 - Database RESTORE Started

A local database restore is beginning. This UIM follows the issue of the chg-db:action=restore command.

Example 
RLGHNCXA21W 00-06-18 19:12:00 EST EAGLE 31.3.0
0147.1115 CARD 1201,A INFO Database RESTORE started

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.116 1116 - Database Action Ended - OK

A local database backup or restore has successfully completed. This UIM follows the issue of the chg-db command.

Example 
RLGHNCXA21W 00-06-18 19:12:00 EST EAGLE 31.3.0
0147.1116 CARD 1201,A INFO Database action ended - OK

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.117 1117 - Database action ended - FAIL

This error message indicates that one or more cards specified in the init-flash/act-flash command is out of phase with the command.

Example
RLGHNCXA21W 00-06-18 19:12:00 EST EAGLE 31.3.0
0147.1117 CARD 1201,A INFO Database action ended - FAILED

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.118 1118 - TOD change affects MEAS collection

This message indicates that due to a time change, the measurements in a specific period may be inaccurate.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0020.1118    CARD 1106     INFO      TOD change affects MEAS collection
                 Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.119 1119 - Cards out of phase with flash procedure

This message indicates that the collection sequence has been disrupted and the 60-minute and/or 30-minute data may be inaccurate.

Example

12345678901234567890123456789012345678901234567890123456789012345678901234567890
0020.1119    CARD 1115     INFO      Cards out of phase with flash procedure
                                               Card List: 1101, 1201, 1302, 2103, 2204, ... (2 others)
                 Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.120 1120 - TRBL Queue is full:elements overwritten

This message indicates that too many UIMs per second are being output. One or more might be lost.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1120 CARD 1113 INFO RBL Queue is full;elements overwritten

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.121 1121 - LNP rcvd query from unknown CGPA PC

The LNP query receives a calling party point code that is not in the routing table. The system LNP subsystem normally sends a response back to the calling party PC in the query. The system did not respond to this query.

Example 
RLGHNCXA21W 00-04-18 19:00:11 EST EAGLE 31.3.0
0107.1121 CARD 1103,A1 INFO LNP rcvd query from unknown CGPA PC
          SIO=03 OPC=003-252-000 DPC=000-071-000
          CDPA: AI=10 SSN=05 TT=250
                 ADDR=ABCDEF1234567890ABCDE
          CGPA: AI=12 PC=001-001-001 SSN=002
          DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
                   2e cf 01 00 d0 02 83 01 f2 25 aa 0b
                   84 09 01 00 11 0a 19 49
          LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Provision a route to the Calling Party Point Code using the ent-dstn and ent-rte commands.

3.3.122 1122 - LNP rcvd query with undefined TT/SERV

The LNP Query Subsystem received a message with an undefined Service. The Called Party Translation type in the incoming message determines the format of the MSU. This UIM can be issued when there is no LNP Service associated with the Translation Type of this MSU.

If the Translation Type of the MSU is provisioned as a Translation Type for LNPQS Service, the Eagle attempts to determine the actual LNP Service for this message by examining the OP CODE value. If the OP CODE does not match any supported by the Eagle Service (IN, AIN, IS-41), this UIM is issued.

This UIM can also be issued as a result of an error response from an end office because the Eagle LNP database response returned an LRN that was not provisioned in the end office.

Trace tools and/or the hex dump in the UIM can be used to determine the TCAP information. Note that the GTT data is not contained in the SCCP layer because the Eagle does not return this information in the LNP response to the end office.

Example 
RLGHNCXA21W 00-04-18 19:00:11 EST EAGLE 31.3.0
0107.1122 CARD 1103,A1 INFO LNP rcvd query with undefined TT/SERV
          SIO=03 OPC=003-252-000 DPC=000-071-000
          CDPA: AI=10 SSN=05 TT=250
                 ADDR=ABCDEF1234567890ABCDE
          CGPA: AI=12 PC=001-001-001 SSN=002
          DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
                   2e cf 01 00 d0 02 83 01 f2 25 aa 0b
                   84 09 01 00 11 0a 19 49
          LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If the IN, AIN, IS-41, PCS 1900, or LNPQS LNP Query translation type has not been provisioned, it needs to be provisioned using the ent-lnp-serv command.

    If any of the above LNP Query Translation Types has not been provisioned, it can be changed using the chg-lnp-serv command.

  2. If the Translation Type has been provisioned correctly, an SSP node in the network is using the wrong Translation Type or an invalid query.

3.3.123 1123 - LNP rcvd query with Message Relay TT

The LNP Query Subsystem received a message with a Translation Type reserved for Message Relay. This happens if another node sent a message to the system for Message Relay with the routing indicator set to rt-on-ssn and ssn set to system’s LNP subsystem.

Example 
RLGHNCXA21W 00-04-18 19:00:11 EST EAGLE 31.3.0
0107.1123 CARD 1103,A1 INFO LNP rcvd query with Message Relay TT
          SIO=03 OPC=003-252-000 DPC=000-071-000
          CDPA: AI=10 SSN=05 TT=250
                 ADDR=ABCDEF1234567890ABCDE
          CGPA: AI=12 PC=001-001-001 SSN=002
          DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
                   2e cf 01 00 d0 02 83 01 f2 25 aa 0b
                   84 09 01 00 11 0a 19 49
          LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. No further action is necessary.

3.3.124 1124 - SIP: Dgts truncated in 302 response

SIP 302 response shall encode only 30 digits in dialed string/telephone number and 25 digits in RN. The remaining digits shall be truncated.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0014.1124    CARD 1103,B   INFO      Dgts truncated in 302 response
                 CNAME= conn1
                 Branch ID = z9hG4bKnashds8
                 RURI: INVITE sip:+1 206 555-0146@127.0.0.1:5070;user=phone

                 Report Date:10-10-12  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is required.

3.3.125 1125 - GWS rcvd CDPA that could not be RDCTd

This message indicates the EAGLE 5 ISS received an MSU, with a called party address (CDPA) that is not allowed in gateway screening (GWS) and cannot be redirected.

Example 
RLGHNCXA21W 00-04-18 18:59:23 EST EAGLE 31.3.0
0101.1125 CARD 1205,B INFO GWS rcvd CDPA that could not be RDCTd
          SIO=0a OPC=003-244-000 DPC=000-071-000
          SCCP MT= 18
          CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
                  ADDR=123456789012345678909
          CGPA: AI=10 PC=004-004-004 SSN=005 TT=251
                  ADDR=123456789012345678909
          SR=scrb LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC)
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this called party address (CDPA) is one that should be redirected through the network, add the CDPA to the gateway screening (GWS) tables assigned to the link reporting this message.

    Use the chg-scr-cdpa command to add the CDPA to the list of allowed CDPA codes. Refer to the Database Administration Manual - Gateway Screening for instructions on adding a CDPA to GWS.

  2. If the CDPA should not be redirected through the network, no action is necessary.

3.3.126 1126 - GWS rcvd CGPA that could not be RDCTd

This message indicates the EAGLE 5 ISS received an MSU, with a calling party address (CGPA) that is not allowed in gateway screening (GWS) and cannot be redirected.

Example 
RLGHNCXA21W 00-04-18 18:59:23 EST EAGLE 31.3.0
0101.1126 CARD 1205,B INFO GWS rcvd CGPA that could not be RDCTd
          SIO=0a OPC=003-244-000 DPC=000-071-000
          SCCP MT= 18
          CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
                  ADDR=123456789012345678909
          CGPA: AI=10 PC=004-004-004 SSN=005 TT=251
                  ADDR=123456789012345678909
          SR=scrb LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this calling party address (CGPA) is one that should be redirected through the network, add the CGPA to the gateway screening (GWS) tables assigned to the link reporting this message.

    Use the chg-scr-cgpa command to add the CGPA to the list of allowed CGPA codes. Refer to the Database Administration Manual - Gateway Screening for instructions on adding a CGPA to GWS.

  2. If the CGPA should not be redirected through the network, no action is necessary.

3.3.127 1127 - GWS rcvd AFTPC that could not be RDCTd

This message indicates the EAGLE 5 ISS received an MSU, with an allowed affected point code (AFTPC) that is not allowed in gateway screening (GWS) and cannot be redirected.

Example 
RLGHNCXA21W 00-04-18 18:59:23 EST EAGLE 31.3.0
0101.1127 CARD 1205,B INFO GWS rcvd AFTPC that could not be RDCTd
          SIO=0a OPC=003-244-000 DPC=000-071-000
          SCCP MT= 18
          CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
                  ADDR=123456789012345678909
          CGPA: AI=10 PC=004-004-004 SSN=005 TT=251
                  ADDR=123456789012345678909
          SR=scrb LSN=A1234567

Four outputs are possible.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this calling allowed affected point code (AFTPC) is one that should be redirected through the network, add the AFTPC to the gateway screening (GWS) tables assigned to the link reporting this message.

    Use the chg-scr-aftpc command to add the AFTPC to the list of allowed AFTPC codes. Refer to the Database Administration Manual - Gateway Screening for instructions on adding a AFTPC to GWS.

  2. If the AFTPC should not be redirected through the network, no action is necessary.

3.3.128 1128 - GWS rcvd TT that could not be RDCTd

This message indicates the EAGLE 5 ISS received an MSU, with a translation type (TT) that is not allowed in gateway screening (GWS) and cannot be redirected.

Example 
RLGHNCXA21W 00-04-18 18:59:23 EST EAGLE 31.3.0
0101.1128 CARD 1205,B INFO GWS rcvd TT that could not be RDCTd
          SIO=0a OPC=003-244-000 DPC=000-071-000
          SCCP MT= 18
          CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
                  ADDR=123456789012345678909
          CGPA: AI=10 PC=004-004-004 SSN=005 TT=251
                  ADDR=123456789012345678909
          SR=scrb LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this TT is one that should be redirected through the network, add the TT to the gateway screening (GWS) tables assigned to the link reporting this message.

    Use the chg-scr-tt command to add the TT to the list of allowed TT codes. Refer to the Database Administration Manual - Gateway Screening for instructions on adding a TT to GWS.

  2. If this TT should not be redirected through the network, no action is necessary.

3.3.129 1129 - Ported subs SMSC matches Home SMSC Addr

This message indicates that a ported out subscriber is fraudulently attempted to send SMS using the old networks SMSC. An error message was generated and returned to the originating MSC.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1129    CARD 1103,A     INFO    Ported subs SMSC matches Home SMSC Addr
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1129    CARD 1103,A     INFO    Ported subs SMSC matches Home SMSC Addr
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.130 1130 - IS412GSM not provisioned

The GSMOPTS: IS412GSM digits have not been provisioned.

To be able to perform the IS-41 GSM Migration feature and to accept LOCREQ Request messages, first specify the IS412GSM prefix in GSMOPTS.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 08-01-13 16:20:19 EST  EAGLE 37.5.0
0712.1130    CARD 1105     INFO    IS412GSM not provisioned
                 SIO=83   OPC=   00100          DPC=   00456
                 SCCP MSG TYPE=09
                 CDPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=1
                        TT=010  NP=01  NAI=004  ADDR=19876543210
                        PC=   08238          SSN=010
                 CGPA:  NI=0  RI=1  GTI=00  SSNI=0  PCI=0
                        PC=--------------    SSN=---
                 LSN=ls1
                 Report Date:08-01-13  Time:23:20:02
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0712.1130    CARD 1105     INFO    IS412GSM not provisioned
                 SIO=03   OPC=001-001-001      DPC=002-002-002
                 SCCP MSG TYPE=04
                   GTT on CdPA used MOSMSGTA=9193802053
                 CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                        PC=003-003-003       SSN=005
                 CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                        PC=001-001-001       SSN=004
                 LSN=ABCD123  GTTSET=3 203 46
                 Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the rtrv-gsmopts command to display the IS412GSM setting in the GSM System Options.

    Example of the output: 

    rlghncxa03w 03-05-20 09:04:14 EST  EAGLE 30.1.0
    GSM OPTIONS
    -----------------------
    DEFMCC      = NONE
    DEFMNC      = NONE
    SRFADDR     = 123456789abcdef
    MSRNDIG     = RN
    DEFMAPVR    = 1
    SRIDN       = TCAP
    IS412GSM    = 0123456789abcde
    
    rlghncxa03w 03-03-20 09:04:14 EST  EAGLE 30.1.0
    SRFADDR=123456789abcdef    SRFNAI=7    SRFNP=15
    MSRNDIG=CCRNDN
    MSRNNAI=7    MSRNNP=15 DEFMAPVR=2

    This example shows a setting supporting the IS-41 LOC Request message.

    If the IS412GSM parameter is not specified, proceed to Step 2. However, if it is set with a valid value, proceed to Step 3.

  2. Use the chg-gsmopts command to specify the IS-41 to GSM migration prefix.

    Refer to the Commands Manual for details. Then re-issue the command that caused this UIM.

  3. If the problem persists with the IS412GSM parameter specified, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.131 1131 - Invalid Digits in IS41 MAP Digits Parm

A LOC Request message contained invalid data and will be passed to the GTT. G-Port determined a received Location Request message had invalid data in the called party number parameter fields. The verified fields must contain:

  • Digits: from 5 to 21 digits

  • Encoding scheme: BCD

  • Numbering plan: Telephony

Example 
RLGHNCXA21W 00-04-18 19:02:05 EST EAGLE 31.3.0
0112.1131 CARD 1103,A1 INFO Invalid digits in IS41 MAP Digits parm
          SIO=03 OPC=001-001-001 DPC=002-002-002
          SCCP MSG TYPE=04
          CDPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
                  TT=250 NP=04 NAI=010 ADDR=123456789012345678901
                  PC=003-003-003 SSN=005
          CGPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
                  TT=100 NP=07 NAI=012 ADDR=012345678901234567890
                  PC=001-001-001 SSN=004
          LSN=A1234567

Legend

ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.132 1133 - Diameter msg decode failed

This message indicates that the Diameter message parsing has failed. This may be cause by:

  • ECR Message does not have IMEI AVP or a value in IMEI AVP
  • CER Message does not have mandatory AVP present
  • DPR message received does not have disconnect cause AVP present
Example

12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1133    CARD 1103,B   INFO     Diameter msg decode failed 
                 DCNAME= dcon1    
                 Command Code=(R)            AVP Code=
                 Origin Host= host1
                 Error Cause= avp not present

Alarm Level: No alarm condition. The message is informational only.

3.3.133 1134 - Diameter msg encode Failed

This message indicates that the Diameter message Encoding has failed.

Example

12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1134    CARD 1101,B INFO     Diameter msg encode failed
                 DCNAME=dcon2     
                 Command Code= (A)
                 Origin Host=host1
                 Error Cause=Invalid IMEI digits

Alarm Level: No alarm condition. The message is informational only.

3.3.134 1135 - Invalid diameter Msg received

This message indicates that the Diameter message received is not supported by the EAGLE.

Example

12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1135    CARD 1101,B INFO     Invalid Diameter Msg received 
                 DCNAME= dcon1           
                 Command Code= 4022 (R)
                 Origin Host=---
                 Error Cause=---

Alarm Level: No alarm condition. The message is informational only.

3.3.135 1136 - Invalid Diameter Msg length

This message indicates one of the following conditions:
  1. The total Diameter message length specified in the diameter header does not match the actual diameter message length.
  2. The diameter message length is greater than the maximum length of 448 bytes supported by current EIR S13/S13's implementation.
Example

12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1136    CARD 1101,B INFO     Invalid Diameter Msg length 
                 DCNAME= dcon1           
                 Command Code=  (R)
                 Origin Host=---
                 Error Cause=---

Alarm Level: No alarm condition. The message is informational only.

3.3.136 1137 - Diameter AVP Decode Fail

This message indicates an invalid length for the IMEI/IMSI AVP has received.

Example

12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1137    CARD 1101,B INFO     Diameter AVP Decode Fail
                 DCNAME= dcon1           
                 Command Code=  (R)          AVP Code= 
                 Origin Host=---
                 Error Cause=AVP Decode Error

Alarm Level: No alarm condition. The message is informational only.

3.3.137 1138 - Connection Refused

This message indicates that the Origin host and Origin Realm AVPs in the CER message does not match the host and real values provisioned in the IPAPSOCK table. The Source IP Address of the CER does not match the IP Address present in the Host-IP-Address AVP. This may be cause by:

  • Origin Host Mismatch
  • Origin Realm Mismatch
  • IP Address Mismatch
  • No common Application
Example

12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1138    CARD 1101,B INFO     Connection Refused
                 DCNAME= dcon1           
                 Command Code=  (R)
                 Origin Realm=aricent.com
                 Error Cause=Origin Realm Mismatch

Alarm Level: No alarm condition. The message is informational only.

3.3.138 1139 - DEIROPTS: DEIR Global Response is ON

This message indicates that the DEIR Global response is ON.

Example

12345678901234567890123456789012345678901234567890123456789012345678901234567890
    6056.1139    CARD 1115     INFO    DEIROPTS: DEIR Global Response is ON

Alarm Level: No alarm condition. The message is informational only.

3.3.139 1140 - DEIROPTS: DEIR Global Response is OFF

This message indicates that the DEIR Global response is OFF.

Example

12345678901234567890123456789012345678901234567890123456789012345678901234567890
    6056.1140    CARD 1115     INFO    DEIROPTS: DEIR Global Response is OFF

Alarm Level: No alarm condition. The message is informational only.

3.3.140 1141 - AIN INP Qry Rejected: AINPQ is OFF

The EAGLE 5 ISS has rejected an ANSI INP query that is decoded as an AIN query because the appropriate AINPQ (ANSI INP Query) feature key is not on.

Example 
6812.1141    CARD 1103     INFO    AIN INP Qry rejected: AINPQ is OFF
                 TRANSLATED PC= 001-001-001        TRANSLATED SS=002
                 CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                        TT=006  NP=--  NAI=---  ADDR=234567
                        PC=   003-003-001    SSN=002
                 CGPA:  NI=0  RI=1  GTI=00  SSNI=1  PCI=1
                        PC=   002-002-001    SSN=002
                 LSN=ls221

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If you want to support the AINPQ feature, issue the following commands to process ANSI AIN queries: enable-ctrl-feat:partnum:893017801:fak=<ANSI-41 INP Query FAK>
  2. Enter chg-ctrl-feat:partnum:893017801:status=on command.
  3. If you do not want to support the AINPQ feature, ignore this informational message.
  4. For additional information or assistance about the AINPQ or any feature to purchase, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.141 1142 - GWS Strip Stop Action Failed

GWS Strip stop action has failed to de-encapsulate the MSU.

Example
6812.1142    CARD 1103     INFO      GWS Strip Stop Action Failed
                 Report Date:13-10-10  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Send the redirected MSU for the STRIP action to be applied.
  2. Verify that the filtering criteria of the 'STRIP' action matches the parameters encoded by REDIRECT stop action.

3.3.142 1143 - GTT(FLOBR) failure: duplicate settype

This message indicates that any one of the MBR GTT Settypes (IMSI\MSISDN\VLRnb\SMRPOA\SMRPDA) is found twice in the FLOBR search path, and the fallback is set to "NO" in the last matched translation. This results in GTT failure.

Example
    0018.1143    CARD 1103     INFO      GTT(FLOBR) failure: duplicate settype    
                 SIO=03 OPC=4-123-5 DPC=6-018-7
                 CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=25   NP=04  NAI=010  ADDR=123456789012345678901
                        PC=3-026-5           SSN=005
                 CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                        PC=-----------       SSN=004
                        LSN=ls2314n2 GTTSETIDX=211 215

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Update the FLOBR GTT search path configuration via the chg-gta command so that the same MBR GTT settype is not encountered in the search path again.

3.3.143 1144 - GTT(FLOBR) warning: duplicate settype

This message indicates that any one of the MBR GTT Settypes (IMSI\MSISDN\VLRnb\SMRPOA\SMRPDA) is found twice in the FLOBR search path, and the fallback is set to "Yes" in the last matched translation. GTT is then performed on the basis of the last matched translation. This is a successful scenario.

Example
    0028.1144    CARD 1103     INFO      GTT(FLOBR) warning: duplicate settype
                 SIO=03 OPC=4-123-5 DPC=6-018-7
                 CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=25   NP=04  NAI=010  ADDR=123456789012345678901
                        PC=3-026-5           SSN=005
                 CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                        PC=-----------       SSN=004
                        LSN=ls2314n2 GTTSETIDX=211 215

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Update the FLOBR GTT search path configuration via the chg-gta command so that the same MBR GTT settype is not encountered in the search path again.

3.3.144 1145 - MBR decoding failed

This message indicates that there is a problem with decoding the TCAP portion of the incoming MSU. The UIM information displays the error reason and the parameter value. The GTT will be performed on the basis of the "fallback" value set in the last matched translation.

Example
0018.1145    CARD 1103     INFO      MBR decoding failed
                 Reason= MSISDN decoding failed (Extension bit is zero)
                 OPC=4-123-5      DPC=6-018-7
                 CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=25   NP=04  NAI=010  ADDR=123456789012345678901
                        PC=3-026-5           SSN=005
                 CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                        PC=-----------       SSN=004
                 Op-Code=2  PKG-Type= TC BEGIN(0x62)  
                 Comp-Type= Invoke(0xA1)
                MAP PARAM: NP=1  NON=1  Ext-Bit=0
                 MAP Digits=12345678912

                 Report Date:15-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.145 1146 - REPT-XLST-TIMO: X-LIST entry expired

This message indicates that the timer has expired for an x-list entry and that entry has been removed.

Example

RLGHNCXA21W 00-06-18 19:12:00 EST EAGLE 31.3.0
0147.1146 CARD 1201 INFO REPT-XLST-TIMO:X-LIST entry expired
          DPC=001-001-001

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.3.146 1147 - MTP Invalid TFA received

This message indicates the network elements of an adjacent node have not been configured properly.

Example 
RLGHNCXA21W 00-06-18 19:12:00 EST EAGLE 31.3.0
0147.1147 CARD 1201,A INFO MTP Invalid TFA received
          OPC=001-001-001 CPC=002-002-002
          LSN=lsn01a
Legend
CPC
Capability point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code

Alarm Level: No alarm condition. The message is informational only.

Recovery

Notify the craftsperson at the adjacent node of this error.

3.3.147 1148 - MTP Invalid TFR received

This message indicates the network elements of an adjacent node have not been configured properly.

Example 
RLGHNCXA21W 00-06-18 19:12:00 EST EAGLE 31.3.0
0147.1148 CARD 1201,A INFO MTP Invalid TFR received
          OPC=001-001-001 CPC=002-002-002
          LSN=lsn01a
Legend
CPC
Capability point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code

Alarm Level: No alarm condition. The message is informational only.

Recovery

Notify the craftsperson at the adjacent node of this error.

3.3.148 1149 - SLK Level-3 T19 Timer Expired

The link has been down for 5 minutes or the timer T19 has timed out.

Example 
RLGHNCXA21W 00-06-18 19:12:00 EST EAGLE 31.3.0
0147.1149    CARD 1201,A INFO SLK Level-3 T19 timer expired

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Activate measurements using the chg-meas:collect=on command.

    This starts measurements collection.

  2. If the link is placed OOS-MT, use the measurements collected over the appropriate time period to determine the cause, and determine which action is now necessary.

    Note:

    Refer to the Measurements Manual for traffic measurements information.

3.3.149 1150 - SLK Inhibit Denied

The request to inhibit the link has been denied.

Example

  • The following is an example of an error occurring at the near end. 

        RLGHNCXA21W 03-12-22 21:49:03 EST EAGLE 40.1
    7271.1150    CARD 1202,A   INFO    SLK Inhibit denied
                 Source:  Local
                 Reason:  Only one link available in the linkset
    Report Date:03-12-22  Time:21:49:03

  • The following is an example of an error occurring at the far end. 

        RLGHNCXA21W 03-12-22 21:49:03 EST EAGLE 40.1
    7271.1150    CARD 1202,A   INFO    SLK Inhibit denied
                 Source:  Remote
                 Reason:  Unknown
    Report Date:03-12-22  Time:21:49:03

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If denied locally, inhibiting the link would cause the far end to prohibit the point code. If remotely denied, contact the far-end office to determine the cause and to correct the problem.

3.3.150 1151 - SLK Inhibit Response Timeout

The system has sent a link inhibit request, but no inhibit acknowledge was received.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1151    CARD 1205,A nc00027 SLK Inhibit Response Timeout

Alarm Level: No alarm condition. The message is informational only.

Recovery

Try the inhibit command again.

If still unsuccessful, contact the far-end office and verify the status.

3.3.151 1152 - SLK Uninhibit Denied

The far end has denied the craftsperson’s request to uninhibit the link.

Example

RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1152    CARD 1205,A nc00027 SLK Uninhibit Denied

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact the far end office to determine why this was denied.

3.3.152 1153 - SLK Uninhibit Response Timeout

An uninhibit request was sent, but an uninhibit acknowledge was not received.

Example

RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1153    CARD 1205,A nc00027 SLK Uninhibit Response Timeout

Alarm Level: No alarm condition. The message is informational only.

Recovery

Try the uninhibit request again.

If still unsuccessful, contact the far-end.

3.3.153 1154 - MSU received threshold exceeded

This UIM is produced by the OAM. It is produced whenever the cumulative count of MSUs received due to gateway screening on a given linkset exceeds the specified GWS activity threshold (MSU_recvd_threshold) within a specified time period.

Example

RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1154    SYSTEM   INFO   MSU-received threshold exceeded

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.3.154 1155 - MSU-rejected threshold exceeded

This UIM is produced by the OAM. It is produced whenever the cumulative count of MSUs discarded due to gateway screening on a given linkset exceeds the specified GWS activity threshold (MSU_reject_threshold) within a specified time period.

Example

RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1155    SYSTEM   INFO   MSU-rejected threshold exceeded

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.3.155 1156 - Minor congestion event detected

This message is issued when a HIPR2 card detects a minor congestion event. A congestion event is one 10 millisecond time slice that exceeds the specified bus utilization for that time slice on a segment as detected by the HIPR2.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST EAGLE 41.1.0
    0023.1156    CARD 1109     INFO     Minor congestion event detected
                 Report Date:09-02-07  Time:12:01:43

Alarm Level: No alarm condition. The message is informational only.

Recovery

Although no action is required, the message can serve as a notification that this particular section of the IMT bus is reaching its saturation.

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA for more information.

3.3.156 1157 - Major congestion event detected

This message is issued whenever a HIPR2 card detects a major congestion event. A congestion event is one 10 millisecond time slice that exceeds the specified bus utilization for that time slice on that segment.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST EAGLE 41.1.0
    0023.1157    CARD 1109     INFO     Major congestion event detected
                 Report Date:09-02-07  Time:12:01:43

Alarm Level: No alarm condition. The message is informational only.

Recovery

Although no action is required, the message can serve as a notification that this particular section of the IMT bus is reaching its saturation.

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA for more information.

3.3.157 1158 - Minor HIPR2 switching capacity reached

This message is issued when the minor switching rate is observed by the HIPR2 card. This rate is a measure of the switching capacity of the HIPR2 card.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST EAGLE 41.1.0
    0023.1158    CARD 1109     INFO     Minor HIPR2 switching capacity reached
                 Report Date:09-02-07  Time:12:01:43

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.158 1159 - Major HIPR2 switching capacity reached

This message is issued when the major switching rate is observed by the HIPR2 card. This rate is a measure of the switching capacity of the HIPR2 card.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST EAGLE 41.1.0
    0023.1159    CARD 1109     INFO     Major HIPR2 switching capacity reached
                 Report Date:09-02-07  Time:12:01:43

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.159 1160 - GWS rcvd ISUP that is not allowed

This message indicates gateway screening (GWS) has discarded an MSU because the ISUP is listed as one that is not allowed in this network.

Example 
RLGHNCXA21W 00-04-18 18:59:58 EST EAGLE 31.3.0
0105.1160   CARD 1205,A INFO GWS rcvd ISUP that is not allowed
             SIO=0a OPC=003-247-000 DPC=002-000-000
             DATA=12 34 56 78 90 12 34 56 78 90 12 34
                      56 78 90 12 34 56 78 90 12 34 56 78
             SR=scrb LSN=A1234567
Legend
CPC
Capability point code
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This indicates that a MSU was discarded because it failed screening.

    No action is necessary, unless the MSU should have passed. If the MSU should have passed (verified by the fields displayed in the above message), go to Step 2.

  2. Using the rtrv-scr-sio command, verify that the screening reference specified in the above message does not allow MSUs with the priority value indicated.
  3. If the MSU should have passed screening, use the chg-scr-sio command to add the pri data to the screening reference.

3.3.160 1161 - GWS rcvd nonSNM DESTFLD screening msg

This message indicates gateway screening (GWS) received a message that is not a MTP network management message. Affected Destination (DESTFLD) screening makes sense only for MTP Network Management (SNM) messages. When a non-SNM message is screened for Affected Destination, it is forced to pass screening and this message is generated.

Example 
RLGHNCXA21W 00-04-18 18:59:58 EST EAGLE 31.3.0
0105.1161 CARD 1103,A INFO GWS rcvd ISUP nonSNM DESTFLD screening msg
          SIO=0a OPC=003-247-000 DPC=002-000-000
          DATA=12 34 56 78 90 12 34 56 78 90 12 34
               56 78 90 12 34 56 78 90 12 34 56 78
          SR=scrb LSN=A1234567
Legend
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.3.161 1162 - GWS rcvd nonSCCP CGPA/CDPA Screen Msg

This message indicates that a message that was not a SCCP message passed CGPA/CDPA screening. CDPA orCGPA screening makes sense only for SCCP messages. When a non-SCCP message is screened for CDPA or CGPA, it is forced to pass screening and this message is generated.

Example 
RLGHNCXA21W 00-04-18 18:59:58 EST EAGLE 31.3.0
0105.1162 CARD 1103,A INFO GWS rcvd nonSCCP CGPA/CDPA screen msg
             SIO=0a OPC=003-247-000 DPC=002-000-000
             DATA=12 34 56 78 90 12 34 56 78 90 12 34
                      56 78 90 12 34 56 78 90 12 34 56 78
             SR=scrb LSN=A1234567
Legend
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.3.162 1163 - GWS rcvd invalid GTI in TT screening

This message indicates that a message that was not a SCCP message or an SCCP message that does not contain a TT passed the Allowed TT screening. Allowed TT screening makes sense only for SCCP messages that contain TT. When a non-SCCP message or a SCCP message that does not contain a TT is screened for Allowed TT, it is forced to pass screening and this message is generated.

Example 
RLGHNCXA21W 00-04-18 18:59:58 EST EAGLE 31.3.0
0105.1163 CARD 1103,A INFO GWS rcvd invalid GTI in TT screening
SIO=0a OPC=003-247-000 DPC=002-000-000
DATA=12 34 56 78 90 12 34 56 78 90 12 34
56 78 90 12 34 56 78 90 12 34 56 78
SR=scrb LSN=A1234567
Legend
CPC
Capability point code
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.3.163 1164 - Inh LNP SS request already outstanding

An inh-map-ss command is already entered and queued.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1164 SYSTEM INFO Inh LNP SS request already outstanding

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.164 1166 - ACG Node Overload Level Change

The SCM has detected that the node overload level for the system has changed.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1166   SYSTEM    INFO        ACG Node Overload Level Change
OLD ACG LEVEL= 0    NEW ACG LEVEL= 10

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.165 1167 - SIP connection established

This message indicates that the SIP connection has been established.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0014.1167    CARD 1101     INFO    SIP connection established
                 Connection Name : tcp1101d
                 Report Date:10-10-12  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.166 1168 - SIP connection terminated

This message indicates that the SIP connection has been terminated.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0014.1168    CARD 1101     INFO    SIP connection terminated
                 Connection Name : tcp1101d
                 Report Date:10-10-12  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.167 1169 - SCCP rcvd inv TCAP portion

SCCP received a message with a Transaction Capabilities Application Part (TCAP) that is unsupported or not valid.This UIM can be generated by features LNP MR or GSM MAP Screening as defined in the following table.

Table 3-11 Feature Settings

LNP MR GSM Map Screening Description
On Off SCCP discarded a message. No action is necessary.
Off On GSM MAP Screening does not discard the MSU. The action provisioned in the GSMDECERR parameter in the STPOPTS table is performed. No action is necessary.
On On The TCAP Package Type from the DATA portion of the UIM must be decoded to determine which feature generated the message.
  • If ANSI TCAP (IS41), then LNP MR generated the message. See the LNP MR description above.
  • If ITU TCAP (GSM), then GSM MAP Screening generated the message. See the GSM MAP screening description above.
Example 
RLGHNCXA21W 00-04-18 19:02:12 EST  EAGLE 31.3.0
0113.1169    CARD 1103,A1  INFO   SCCP rcvd inv TCAP portion
             SIO=0a   OPC=004-009-000  DPC=002-000-000
                      CDPA:  AI=10  SSN=005  TT=250  
             ADDR=ABCDEF1234567890ABCDE
             CGPA:  AI=12  PC=001-001-001   SSN=002 
             DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9 
                  2e cf 01 00 d0 02 83 01 f2 25 aa 0b
                  84 09 01 00 11 0a 19 49
             LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
SR
Screening reference name
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.168 1170 - OAMHC Meas transition complete.

The full capabilities of the E5-OAM Integrated Measurements feature are available now. The Measurements Platform, if in use before the transition, has been replaced by the the E5-OAM Integrated Measurements feature.

Example 
RLGHNCXA21W 09-11-17 12:01:43 EST  EAGLE 42.0.0
    yyyy.1170    SYSTEM        INFO      OAMHC Meas transition complete.
                 Report Date:09-11-17  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action required.

3.3.169 1171 - Schd UI Rpt disbld-link cnt exceeds 700

To prevent sending too much information to the terminal during the time available, the E5-OAM Measurements Interface feature disables UI reports whenever the number of provisioned links is greater than 700 .

Example 
RLGHNCXA21W 09-11-17 16:20:19 EST  EAGLE 42.0.0
    0014.1171    SYSTEM        INFO      Schd UI Rpt disbld-link cnt exceeds 700

                 Report Date:09-11-17  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action required.

3.3.170 1172 - REPT-OVSZMSG: MTP MSU Too Large to rte

An oversized MTP MSU was received and discarded.

Example 
0056.1172    CARD 1113     INFO    REPT-OVSZMSG: SCCP MSU too large to rte
                 LEN=50
                 SIO=04   OPC=   016-032-048    DPC=   032-032-048  
                 SCCP MT=012
                 CDPA: AI=04 PC=   016-032-048   SSN=004 TT=004
                       ADDR=43210FEDCBA9876543210
                 CGPA: AI=04 PC=   016-032-048   SSN=004 TT=004
                       ADDR=0123456789ABCDEF01234
                 LSN=ls211
                 Report Date:12-12-15  Time:11:03:31

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.171 1173 - REPT-OVSZMSG: SCCP MSU Too Large to rte

An oversized SCCP MSU was received and discarded.

Example 
0045.1173    CARD 1113     INFO    REPT-OVSZMSG: MTP MSU too large to rte
             LEN=50
             SIO=04   OPC=   016-032-048    DPC=   032-032-048  
             DATA=01 02 03 04 05 06 07 08 09 0a 0b 0c 
                  0d 0e 0f 10 11 12 13 14 15 16 17 18 
                  19 1a 1b 1c 
             LSN=ls211
             Report Date:12-12-15  Time:11:01:20
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
LEN
Data length
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SCCP MT
SCCP message type
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.172 1174 - Inh INP SS request alrdy outstanding

An inh-map-ss command is already entered and queued.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1174   SYSTEM  INFO  Inh INP SS request alrdy outstanding

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.173 1176 - Unexpected DB version - Using UDT

This message indicates that an unexpected DB version was received from the MPS during the database download. As a result, the UDP-based Data Transfer protocol will be used to transfer the database from the MPS to the Eagle 5.

Example 
0020.1176    CARD 1113    INFO      Unexpected DB version – using UDT
                 Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.174 1177 - Cnvrsn Discard: SCCP MSU too large

An SCCP MSU received was too large and discarded.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1177  CARD 1103,A2  INFO   Cnvrsn Discard: SCCP MSU too large
LEN=279
SIO=03    OPC=002-002-002    DPC=001-001-001
SCCP MT=004
CDPA:  AI=8B  PC=003-003-003  SSN=005  TT=250
ADDR=ABCDEF0123456789ABCDE
CGPA:  AI=8B  PC=004-004-004  SSN=006  TT=251
ADDR=919460365512345678912
LSN=A1234657
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
LEN
Data length
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SCCP MT
SCCP message type
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.175 1178 - Conversion Discard: Invalid SCCP msg type

This message indicates the STP received a message type that has no equivalent in the opposite protocol.

Example 
station5 00-04-18 19:12:00 EST  EAGLE 31.3.0
0110.1178   CARD 1205,B  INFO  Conversion Discard: Invalid SCCP msg type
SIO=0e  OPC=4-013-1      DPC=1-003-0
MSG TYPE=004
LSN=A1234657
Legend
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
OPC
Origination point code
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that the error was encountered.

3.3.176 1179 - Cnvrsn Discard: CGPA PC alias undefined

An SCCP MSU contained an undefined CGPA PC and was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1042    CARD 1103,A     INFO    SCCP rcvd inv GT - bad Translation Type
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1042    CARD 1103,A     INFO    SCCP rcvd inv GT - bad Translation Type
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
LEN
Data length
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SCCP MT
SCCP message type
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Perform one of the following actions:
  • Enable the proper Discard CGPA PC STP Option, based on the network type of the incoming message.

    Refer to the Database Administration Manual - Global Title Translation for details.

    OR

  • Add the proper alias for the Calling Party Point Code corresponding to the destination network.

    Refer to the Database Administration Manual - Global Title Translation for details.

3.3.177 1180 - Conversion Discard: Aft. PC alias undefined

An SCCP MSU contained an undefined affected point code alias. The message was discarded.

Example 
RLGHNCXA21W 00-04-18 19:04:15 EST  EAGLE 31.3.0
0124.1180   CARD 1106  INFO  Conversion Discard: Aft. PC alias undefined
SIO=0a   OPC=004-031-000  DPC=000-071-000
SCMG:    MSG TYPE=000         MSG LEN=003
AFTPC=004-219-000    AFTSS=000   MULT=000
LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG LEN
Message length
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
SCMG
SCCP management message
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

Add the proper alias for the Affected point code corresponding to the destination network.

Refer to the Database Administration Manual - Global Title Translation for details.

3.3.178 1181 - Conversion Discard: Invalid SCMG msg type

An SCCP MSU contained an invalid SCCP management message (SCMG) and was discarded

Example 
RLGHNCXA21W 00-04-18 19:04:15 EST  EAGLE 31.3.0
0124.1181   CARD 1106  INFO   Conversion Discard: Invalid SCMG msg type
SIO=0a   OPC=004-031-000  DPC=000-071-000
SCMG:    MSG TYPE=000         MSG LEN=003
Legend
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG LEN
Message length
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
SCMG
SCCP management message
SIO
Service information octet

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.179 1182 - Cnvrsn Discard - Invalid TCAP element

An invalid element has been detected.

Example 
Station 1234 00-03-30 16:20:08 EST  EAGLE 31.3.0
0018.1182 - CARD 1103,A  INFO Cnvrsn Discard:Invalid TCAP element
SIO=03 OPC=001-001-001  DPC=002-002-002
LEN=037 SCCP MT=009
CGPA: AI=C3 PC=004-004-004  SSN=005  TT=053
ADDR=ABCDEF0123456789ABCDE
PKG=E2  CMPNT=EA OFFSET=030 EXPECTED=OA  ACTUAL=AO
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CMPNT
Component
DPC
Destination point code
LEN
Data length
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
PKG
Package
SCCP MT
SCCP message type
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.180 1183 - Cnvrsn Discard - Invalid TCAP elem’t len

An element’s length of contents field has received an element that extends beyond the end of its container element.

Example 
Station 1234 00-03-30 16:20:08 EST  EAGLE 31.3.0
0018.1183  CARD 1103,A   INFO Cnvrsn Discard: Invalid TCAP elem’t len
SIO=03 OPC=001-001-001  DPC=002-002-002
LEN=037 SCCP MT=009
CGPA: AI=C3 PC=004-004-004  SSN=005  TT=053
ADDR=ABCDEF0123456789ABCDE
PKG=E2  CMPNT=EA OFFSET=030 EXPECTED=OA  ACTUAL=AO
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CMPNT
Component
DPC
Destination point code
LEN
Data length
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
PKG
Package
SCCP MT
SCCP message type
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.181 1184 - Cnvrsn Discard: Invalid SCCP elem’t len

An element’s length of contents field has received an element that extends beyond the end of its container element.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1184  CARD 1103,A2  INFO   Cnvrsn Discard: Invalid SCCP elem’t len
LEN=279
SIO=03    OPC=002-002-002    DPC=001-001-001
SCCP MT=004
CDPA:  AI=8B  PC=003-003-003  SSN=005  TT=250
ADDR=ABCDEF0123456789ABCDE
CGPA:  AI=8B  PC=004-004-004  SSN=006  TT=251
ADDR=919460365512345678912
LSN=A1234657
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CMPNT
Component
DPC
Destination point code
LEN
Data length
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
pkg
Package
SCCP MT
SCCP message type
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.182 1185 - GTI input clock anomalies detected

This message indicates additional high speed clock diagnostic data is available although the high speed clocks are valid.

Example
RLGHNCXA21W 03-01-06 13:46:23 EST  EAGLE 35.0.0 
0379.1185    CARD 1113     INFO    GTI input clock anomalies detected 
             Reporting TDM Location        : 1114 
             GTI Clock Status Register     : H'0021 
             Primary LIU Violation Count   :  56 
             Secondary LIU Violation Count : 129 
             GTI Status Register           : H'0022 
             Report Date:03-01-05  Time:13:46:25

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.183 1186 - Meas data load failure: old version

This message can be generated if the primary MCP is running an older version of the GPL than the secondary MCP. This could possibly occur in an upgrade failure or upgrade back out procedure.

Example
 RLGHNCXA21W 02-07-21  16:20:19  EST EAGLE 31.3.0
 0002.1186    CARD 1103     INFO      Meas data load failure: old version
                Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Boot the primary and/or secondary MCPs with the approved GPL version of the system release.

3.3.184 1187 - Table Checksum Mismatch

This message indicates additional diagnostic information in the event of a GPL or a specific table corruption alarm. Whenever a GPL corruption alarm (UAM 0040) is raised during the GPL Audit or a subset data corruption alarm (UIM 1188) is raised during static data Audit, this UIM 1187 is also output to provide the Table ID, Reference Checksum, and Calculated Checksum of the GPL or the specific tablein question.

Example
    RLGHNCXA21W 07-01-06 13:46:23 EST  EAGLE 41.0.0 
    0014.1187    CARD 1113     INFO      Table Checksum Mismatch
                 TBL ID = 136  CALC CHKSUM=H’B7C0   REF CHKSUM=H’4A5F

Alarm Level: No alarm condition. The message is informational only.

Recovery

Refer to the recovery procedure for the appropriate UAM that accompanied this alarm.

3.3.185 1188 - DB Subset Checksum Mismatch

This message indicates additional diagnostic information in the event of DB corruption alarm (UAM 35, 38, or 427). Whenever a DB corruption is detected during the DB audit, this UIM 1188 is also output to provide the Table ID, Reference Checksum, and Calculated Checksum of the DB Subset in question.

Example
    RLGHNCXA21W 03-01-06 13:46:23 EST  EAGLE 35.0.0 
    0008.1188    CARD 1113     INFO      DB Subset Checksum Mismatch
                 SUBSET = 3  CALC CHKSUM = H'abcd  REF CHKSUM = H'
             Report Date:03-01-06  Time:13:46:25

Alarm Level: No alarm condition. The message is informational only.

Recovery

Refer to the recovery procedure for the appropriate UAM that accompanied this alarm.

3.3.186 1189 - SCCP did not Route - DPC not in RTE Table

SCCP did not route a message because the destination point code (DPC) is not in the route (RTE) table. The message was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1189    CARD 1103,A     INFO    SCCP did not Route - DPC not in RTE Table
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1189    CARD 1103,A     INFO    SCCP did not Route - DPC not in RTE Table
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
Legend
ADD
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No alarm condition. The message is informational only.

Recovery

Check the absence of the DPC in the Routing table by entering the appropriate DPC type (DPCA, DPCN, DPCN24, whichever is applicable).

For example: rtrv-rte:dpc=<ni-nc-ncm>
  • If routing to this destination is required, provision the Routing table.

    See Configuring Destination Tables - Adding a Destination Point Code in the Database Administration Manual - SS7

  • If routing to this destination is not required, remove the destination point code from the Routing table.

    See Configuring Destination Tables - Removing a Destination Point Code in the Database Administration Manual - SS7.

3.3.187 1190 - SCCP rcvd inv Clg Party - bad GT ind

The SCCP received a message from the network that was discarded because of a bad global title indicator in the calling party address and that GTT on CGPA is required.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1190    CARD 1103,A     INFO    SCCP rcvd inv Clg Party - bad GT ind
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1190    CARD 1103,A     INFO    SCCP rcvd inv Clg Party - bad GT ind
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADD
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indictor
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.188 1191 - SCCP rcvd inv Clg Party - bad Selectors

The SCCP received a message from the network requiring CGPA GTT, but the Enhanced GTT could not find a CGPA GTT set using the CGPA GTT selectors from the message.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1191    CARD 1103,A     INFO    SCCP rcvd inv Clg Party - bad Selectors
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1191    CARD 1103,A     INFO    SCCP rcvd inv Clg Party - bad Selectors
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADD
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indictor
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. This UIM indicates that Enhanced GTT was attempted, but the GTT selectors lookup failed.
    GTT selectors are GTI & TT (along with NP & NAI for ITUMSUs with GTI=4). If this MSU should have been routed, continue to 2.
  2. Use the following command to check whether GTT selectors in the arrived MSU are provisioned in the GTTSEL table:rtrv=gttsel
  3. If the GTTSEL table does not have an entry with the GTT selectors in the arrived MSU, use the following command to add a record with the GTT selectors in the arrived MSU to the GTTSEL table.ent-gttsel

3.3.189 1192 - GTT Action UDTS DISCARDED MSU

GTT is found with a UDTS action.

There are two cases in which this alarm is generated:
  1. When this GTT Action (DISC, UDTS or TCERR) is provisioned as the main GTT Action for the translation (GTA)
  2. When this GTT Action (DISC, UDTS or TCERR) is provisioned as the default action (ENT/CHG-GTTACT:DEFACTID) for some other GTT Action (FWD, DUP, SFTHROT or SCPVAL) that is provisioned for the translation (GTA), and this default action is executed when the main GTT Action fails.

When these DISCARD Actions are executed as main GTT Action for the translation, the output will look like the following example:

Example 

8878.1192    CARD 1101     INFO    GTT Action UDTS DISCARDED MSU
             OPC=   7-112-0        DPC=   1-001-0
             CDPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=0
                    TT=111  NP=01  NAI=002  ADDR=123456
                    PC=--------------    SSN=006
             CGPA:  NI=0  RI=1  GTI=02  SSNI=1  PCI=1
                    TT=017  NP=--  NAI=---  ADDR=999997999999990999999
                    PC=   7-112-0        SSN=008
             SMRPOA: NP=1    NON=5    ADDR=55566677770000
             LSN=ls711200  Op-Code= 46  GTT Action Set=scpval1
             Report Date:02-12-09  Time:01:22:05

When these DISCARD Actions are executed as the "failure outcome" of the main GTT Action for the translation, this UIM generates an additional line displaying the cause of that main GTT Action failing:

Example 
tekelecstp 15-12-08 13:55:11 MST  EAGLE5 46.3.0.0.0-66.18.1
8878.1192    CARD 1101     INFO    GTT Action UDTS DISCARDED MSU
             Cause: SMRPOA-CGPA Digits Mismatch
             OPC=   7-112-0        DPC=   1-001-0
             CDPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=0
                    TT=111  NP=01  NAI=002  ADDR=123456
                    PC=--------------    SSN=006
             CGPA:  NI=0  RI=1  GTI=02  SSNI=1  PCI=1
                    TT=017  NP=--  NAI=---  ADDR=999997999999990999999
                    PC=   7-112-0        SSN=008
             SMRPOA: NP=1    NON=5    ADDR=55566677770000
             LSN=ls711200  Op-Code= 46  GTT Action Set=scpval1
             Report Date:15-12-08  Time:13:55:11
Legend
ADD
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No alarm condition. The message is informational only.

Recovery

To prevent the MSU from being discarded post-GTT, remove the "UDTS" GTT action associated with the GTT translation. If you want to suppress this UIM, turn off the UIMREQD option for the given "UDTS" GTT action.

3.3.190 1193 - GTT Action DISCARD DISCARDED MSU

GTT is found with a DISCARD action.

There are two cases in which this alarm is generated:
  1. When this GTT Action (DISC, UDTS or TCERR) is provisioned as the main GTT Action for the translation (GTA)
  2. When this GTT Action (DISC, UDTS or TCERR) is provisioned as the default action (ENT/CHG-GTTACT:DEFACTID) for some other GTT Action (FWD, DUP, SFTHROT or SCPVAL) that is provisioned for the translation (GTA), and this default action is executed when the main GTT Action fails.

When these DISCARD Actions are executed as main GTT Action for the translation, the output will look like the following example:

Example 

8872.1193    CARD 1101     INFO    GTT Action DISCARD DISCARDED MSU
             OPC=   1-202-1        DPC=   1-202-4
             CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                    TT=010  NP=--  NAI=---  ADDR=9818316478
                    PC=   3-003-3        SSN=241
             CGPA:  NI=0  RI=1  GTI=04  SSNI=0  PCI=1
                    TT=000  NP=01  NAI=000  ADDR=00
                    PC=   1-202-1        SSN=---
             Op-Code=--- Action Set=disc1
             Report Date:02-12-09  Time:01:20:45

When these DISCARD Actions are executed as the "failure outcome" of the main GTT Action for the translation, this UIM generates an additional line displaying the cause of that main GTT Action failing:

Example 
tekelecstp 15-12-08 13:55:11 MST  EAGLE5 46.3.0.0.0-66.18.1
8872.1193    CARD 1101     INFO    GTT Action DISCARD DISCARDED MSU
             Cause: SMRPOA-CGPA Digits Mismatch
             OPC=   1-202-1        DPC=   1-202-4
             CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                    TT=010  NP=--  NAI=---  ADDR=9818316478
                    PC=   3-003-3        SSN=241
             CGPA:  NI=0  RI=1  GTI=04  SSNI=0  PCI=1
                    TT=000  NP=01  NAI=000  ADDR=00
                    PC=   1-202-1        SSN=---
             Op-Code=--- Action Set=disc1
             Report Date:15-12-08  Time:13:55:11
Legend
ADD
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

  1. To prevent the MSU from being discarded post-GTT, disassociate the "DISCARD" GTT action from the GTT translation.
    If you want to suppress this UIM, turn off the UIMREQD option for the given “DISCARD” GTT action.

3.3.191 1194 - IP Connection Refused, RHOST Mismatch

This message indicates that an association in MATCH validation mode cannot be established due to mismatch in configured RHOST or ARHOST with the INIT message contents.

Example 
station1234 09-09-21 16:28:08 EST Rel 41.0.0-62.6.0
0003.1194    CARD 1213,A   INFO     IP Connection Refused, RHOST mismatch
                  RIPADDR = 123.123.123.123
                  RPORT   = 1314
                  LIPADDR = 123.123.123.124
                  LPORT   = 1315
                  SNAME   = LONGSOCKETNAME1

Alarm Level: No alarm condition. The message is informational only.

Recovery

Check ARHOST provisioning.

Reports on connection status can be obtained for each DCM card with the following commands:
  • pass:loc=xxxx:cmd=”connmgr -l” displays the connection manager event log.
  • pass:loc=xxxx:cmd=”connmgr -c” displays socket client data.
  • pass:loc=xxxx:cmd=”connmgr -s” displays socket server data.

3.3.192 1195 - SCCP did not route - DPC/SS not in mapset

The SCCP did not route a message because the destination point code and destination subsystem was not in the mapset. The message was discarded.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1195    CARD 1103,A     INFO    SCCP did not route - DPC/SS not in mapset
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1195    CARD 1103,A     INFO    SCCP did not route - DPC/SS not in mapset
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
Legend
ADD
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indictor
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If the DPC/SS indicated in the message should not be routed to, no further action is necessary.
  2. If the DPC/SS should be routed to from the EAGLE 5 ISS, use the ent-map command to enter the DPC/SS into the mapset (obtained as outcome of GT translation, with which load sharing is desired) in the MAP table.

3.3.193 1196 - IP Connection Congestion Timeout

This UIM indicates an M3UA or SUA association on the IPGWx GPL has been congested for 30 seconds. At the end of the 30 second period, the congested association is moved to the out-of-service state. All traffic buffered for the association is discarded, at which time this UIM message is displayed.

To prevent a M3UA or a SUA association from remaining congested forever, a 30 second timer is started when an association becomes congested. A separate timer is started for each association that becomes congested.

Approximately one second after the traffic has been discarded, the association is automatically allowed to accept incoming requests to reestablish the association. The timer is not configurable and is not displayed.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0003.1196    CARD 1213,A   INFO      IP Connection Congestion Timeout
ANAME   = LONGASSOCNAME1
Legend
ANAME
Long Association Name

Alarm Level: No alarm condition. The message is informational only.

Recovery

This is an informational message. No further action is necessary.

3.3.194 1197 - IP Connection Refused

Reports that an attempt to connect to an IP client was rejected by the client.

Example 
RLGHNCXA03W 99-04-10 16:28:08 EST EAGLE 35.0.0
0003.1197    DCM 1213,A    IP Connection refused
RIPADDR = 123.123.123.123
RPORT = 1314
LIPADDR = 123.123.123.124  
LPORT = 1315
SNAME=Unknown
Report Date: 02-04-10  Time: 16:27:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

Reports on connection status can be obtained for each DCM card with the following commands:
  • pass:loc=xxxx:cmd=”connmgr -l” displays the connection manager event log.
  • pass:loc=xxxx:cmd=”connmgr -c” displays socket client data.
  • pass:loc=xxxx:cmd=”connmgr -s” displays socket server data.

3.3.195 1198 - IP Connection, Cannot resolve RHOST(S)

Reports that an attempt to connect to an IP client failed because the hostname, RHOST and ARHOST (if configured), could not be found on the IP network.

Example 
RLGHNCXA03W 02-07-21 16:20:19 EST EAGLE 41.0.0
    0003.1198    CARD 1213,A   INFO      IP Connection, Cannot resolve RHOST(S)
                      RIPADDR = Unknown
                      RPORT   = 1314
                      LIPADDR = 123.123.123.124
                      LPORT   = 1315
                      SNAME   = LONGSOCKETNAME1
                 Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

Reports on connection status can be obtained for each DCM card with the following commands:
  • pass:loc=xxxx:cmd=”connmgr -l” displays the connection manager event log.
  • pass:loc=xxxx:cmd=”connmgr -c” displays socket client data.
  • pass:loc=xxxx:cmd=”connmgr -s” displays socket server data.

3.3.196 1199 - LNP DTH Measurements Discarded for DPC

Reports that LNP DTH measurements are being discarded because the capacity of the SSP DTH table has been exceeded.

Example 
RLGHNCXA03W 00-04-10 16:28:08 EST EAGLE 35.0.0
1234.1199    SYSTEM       INFO LNP DTH Measurements Discarded for DPC
DPC=001-001-001
Non-Zero Measurements Discarded: Yes

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If the Non-Zero Measurements Discarded flag is set No, the discarded measurements are all zero, no action is necessary.

    Note:

    If the Non-Zero Measurements Discarded flag is set Yes, Daily LNP Measurements will be lost for the specified DPC from the time of the LIM 1199 occurrence until the end of the day.
  2. To retrieve the prior hour LNP SSP measurement pegs. Refer to the Measurements Manual.
    To retrieve the prior hour LNP measurements or other specific periods, set the Accessible Collection Period: Last or Specific.
    Example: rept-meas:type=mtch:enttye=lnp:period=last

3.3.197 1200 - INW ALT Card as First to be Preloaded

Reports the alternate card the system selected to be loaded with GPLs and data.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1200   SYSTEM      INFO  INW ALT card as first to be preloaded
CARD=1203   GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.198 1201 - INW MAIN Card as Last to be Reset

Reports the main card the system selected to be loaded with GPLs and data.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1201   SYSTEM      INFO  INW MAIN card as last to be reset
CARD=1203   GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.199 1202 - INW Asserted DDL Inhibition

Reports that card cross loading is inhibited.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1202   SYSTEM      INFO  INW Asserted DDL inhibition
CARD=1203   GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.200 1203 - INW Card reset command issued

Reports that a card reset command has been issued.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1203   SYSTEM      INFO  INW Card reset command issued
CARD=1203   GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.201 1204 - INW Waiting for Card Loading Validation

Reports that INW is waiting for validation of card loading.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1204   SYSTEM      INFO  INW Waiting for card loading validation
CARD=1203   GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.202 1205 - INW Detected Card Loaded

Reports that INW has detected a successful completion of a card loading.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1205   SYSTEM      INFO  INW Detected card loaded
CARD=1203   GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.203 1206 - INW Detected Card Reset or Removed

Reports that INW has detected the reset or removal of a card.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1206   SYSTEM      INFO  INW Detected card reset or removed
CARD=1203   GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.204 1207 - INW Allowed Card to Skip DDL Inhibited

Reports that a card is being allowed to crossload.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 35.0.0
0014.1207   SYSTEM      INFO  INW Allowed card to skip DDL inhibited
CARD=1203   GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.205 1208 - INW Removed DDL inhibition

Reports that INW has removed the Dynamic Data Loading (DDL) inhibition on a card.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1208 SYSTEM INFO INW Removed DDL inhibition
CARD=1203 GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.206 1209 - INW Need to reset/remove/inhibit card

Reports that card must be manually reset, removed, or inhibited.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1209 SYSTEM INFO INW Need to reset/remove/inhibit card
CARD=1203 GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.207 1210 - INW Card failed to reset

Reports that card has failed to reset.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1210 SYSTEM INFO INW Card failed to reset
CARD=1203 GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.208 1211 - INW Failed to assert DDL inhibition

Reports that a DDL inhibition has failed.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1211 SYSTEM INFO INW Failed to assert DDL inhibition
CARD=1203 GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.209 1212 - INW Failed to remove DDL inhibition

Reports that an attempt to remove DDL inhibition has failed.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1212 SYSTEM INFO INW Failed to remove DDL inhibition
CARD=1203 GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.210 1213- INW Card failed to DDL crossload

Reports that a card failed to DDL crossload.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014. SYSTEM INFO INW Card failed to DDL crossload
CARD=1203 GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.211 1214 - INW Allowed card to DDL crossload

Reports that a card was allowed to crossload.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1214 SYSTEM INFO INW Allowed card to DDL crossload
CARD=1203 GPL=SS7ANSI

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.212 1215 - GWS rcvd CDPA That Could Not be CNCFd

This message indicates the EAGLE 5 ISS received an MSU, with a called party address (CDPA) that is not allowed in gateway screening (GWS) and cannot be converted.

Example 
RLGHNCXA21W 00-04-18 18:59:23 EST EAGLE 31.3.0
0101.1215 CARD 1205,B INFO GWS rcvd CDPA that could not be CNCFd
SIO=0a OPC=003-244-000 DPC=000-071-000
SCCP MT= 18
CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=10 PC=004-004-004 SSN=005 TT=251
ADDR=ABCDEF1234567890ABCDE
SR=scrb LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this called party address (CDPA) is one that should be converted, add the CDPA to the gateway screening (GWS) tables assigned to the link reporting this message.

    Use the chg-scr-cdpa command to add the CDPA to the list of allowed CDPA codes. Refer to the Database Administration Manual - Gateway Screening for instructions on adding a CDPA to GWS.

  2. If the CDPA should not be converted, no action is necessary.

3.3.213 1216 - GWS rcvd CGPA that could not be CNCFd

This message indicates the EAGLE 5 ISS received an MSU, with a calling party address (CGPA) that is not allowed in gateway screening (GWS) and cannot be converted.

Example 
RLGHNCXA21W 00-04-18 18:59:23 EST EAGLE 31.3.0
0101.1216 CARD 1205,B INFO GWS rcvd CGPA that could not be CNCFd
SIO=0a OPC=003-244-000 DPC=000-071-000
SCCP MT= 18
CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=10 PC=004-004-004 SSN=005 TT=251
ADDR=ABCDEF1234567890ABCDE
SR=scrb LSN=A1234567

Four outputs are possible.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this calling party address (CGPA) is one that should be converted, add the CGPA to the gateway screening (GWS) tables assigned to the link reporting this message.

    Use the chg-scr-cgpa command to add the CGPA to the list of allowed CGPA codes. Refer to the Database Administration Manual - Gateway Screening for instructions on adding a CGPA to GWS.

  2. If the CGPA should not be converted, no action is necessary.

3.3.214 1217 - GWS rcvd AFTPC that could not be CNCFd

This message indicates the EAGLE 5 ISS received an MSU, with an allowed affected point code (AFTPC) that is not allowed in gateway screening (GWS) and cannot be converted.

Example 
RLGHNCXA21W 00-04-18 18:59:23 EST EAGLE 31.3.0
0101.1217 CARD 1205,B INFO GWS rcvd AFTPC that could not be CNCFd
SIO=0a OPC=003-244-000 DPC=000-071-000
SCCP MT= 18
CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=10 PC=004-004-004 SSN=005 TT=251
ADDR=ABCDEF1234567890ABCDE
SR=scrb LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this calling allowed affected point code (AFTPC) is one that should be converted, add the AFTPC to the gateway screening (GWS) tables assigned to the link reporting this message.

    Use the chg-scr-aftpc command to add the AFTPC to the list of allowed AFTPC codes. Refer to the Database Administration Manual - Gateway Screening for instructions on adding a AFTPC to GWS.

  2. If the AFTPC should not be converted, no action is necessary.

3.3.215 1218 - GWS rcvd TT that could not be CNCFd

This message indicates the EAGLE 5 ISS received an MSU, with a translation type (TT) that is not allowed in gateway screening (GWS) and cannot be converted.

Example 
RLGHNCXA21W 00-04-18 18:59:23 EST EAGLE 31.3.0
0101.1218 CARD 1205,B INFO GWS rcvd TT that could not be CNCFd
SIO=0a OPC=003-244-000 DPC=000-071-000
SCCP MT= 18
CDPA: AI=10 PC=003-003-003 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=10 PC=004-004-004 SSN=005 TT=251
ADDR=ABCDEF1234567890ABCDE
SR=scrb LSN=A1234567

Note:

Four outputs are possible. The Legend includes abbreviations found in all variations.

Legend
ADDR
Address
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
AI
Address Indicator
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
SCCP MT
SCCP message type
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
SSN
Subsystem number
TT
Translation type
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this TT is one that should be converted, add the TT to the gateway screening (GWS) tables assigned to the link reporting this message.

    Use the chg-scr-tt command to add the TT to the list of allowed TT codes. Refer to the Database Administration Manual - Gateway Screening for instructions on adding a TT to GWS.

  2. If this TT should not be converted, no action is necessary.

3.3.216 1231 - SCCP Encode Failure

This message indicates that there is an SCCP encode failure.

Example

The UIM is generated by the basic Global Title Translation (GTT) feature. This output indicates an error against the original destination rather than the redirected destination. 
tekelecstp 08-12-26 17:02:48 EDT  EAGLE 41.0
5093.1231    CARD 1105     INFO    SCCP Encode Failure
             SIO=03   OPC=   2-011-1        DPC=   1-001-1
             CDPA LENGTH=008   MSG TYPE=09   INV DMA LEN=280
             CDPA: AI=0b PC=   1-001-0       SSN=002 TT=000
                   ADDR=123456
             LSN=lsn2111
             Report Date:08-12-26  Time:17:02
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
tekelecstp 08-12-26 17:02:48 EDT  EAGLE 41.0
5133.1231    CARD 1105     INFO    SCCP Encode Failure 2
             SIO=03   OPC=   2-011-1        DPC=   1-001-1
             SCCP MSG TYPE=09   INV DMA LEN=280
             CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                    TT=000  NP=--  NAI=---  ADDR=123456
                    PC=   1-001-0        SSN=002
             CGPA:  NI=0  RI=1  GTI=02  SSNI=1  PCI=1
                    TT=027  NP=--  NAI=---  ADDR=123410
                    PC=   2-011-1        SSN=002
             LSN=lsn2111  GTTSET=(1)
             Report Date:08-12-26  Time:17:51:26
Legend
ADDR
Address
AI
Address Indicator
CDPA LENGTH
Called party address length
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
optional text field
Optional text field providing additional information about the error. Possible text display and definitions may include:
INV DMA LEN=xxx
DMA Length too big or too small: After SCCP encoding of translated MSU DMA Length became too big or too small.
UNSUP Clg GTI=x
GTT attempted on Unsupported CgPA GTI=x
UNSUP Cld GTI=x
GTT attempted on Unsupported CdPA GTI=x
INV Clg GTI=x
GTT attempted on INV CgPA GTI=x
INV Cld GTI=x
GTT attempted on INV CdPA GTI=x
GTCNV:Cld ANSI->ITU fail
Invalid CdPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Clg ANSI->ITU fail
Invalid CgPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Cld ITU->ANSI fail
Invalid CdPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
GTCNV:Clg ITU->ANSI fail
Invalid CgPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact the distant end node this message refers to and verify action is being taken to correct the SCCP encode failure problem.

3.3.217 1232 - SCCP Encode Failure

This message indicates that there is an SCCP encode failure. This UIM may be triggered by a service when network crossing (ANSI <-> ITU) is attempted, or the problem could originate at the far end.

Example

This output indicates an error against the original destination rather than the redirected destination. 
tekelecstp 08-12-26 17:02:48 EDT  EAGLE 41.0
5093.1232    CARD 1105     INFO    SCCP Encode Failure 2 
             SIO=03   OPC=   2-011-1        DPC=   1-001-1
             CDPA LENGTH=008   MSG TYPE=09   INV DMA LEN=280
             CDPA: AI=0b PC=   1-001-0       SSN=002 TT=000
                   ADDR=123456
             LSN=lsn2111
             Report Date:08-12-26  Time:17:02
This output includes the redirected destination and is used when a redirected MSU encounters an error. 
tekelecstp 08-12-26 17:02:48 EDT  EAGLE 41.0
5133.1232    CARD 1105     INFO    SCCP Encode Failure 2
             SIO=03   OPC=   2-011-1        DPC=   1-001-1
             SCCP MSG TYPE=09   INV DMA LEN=280
             CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                    TT=000  NP=--  NAI=---  ADDR=123456
                    PC=   1-001-0        SSN=002
             CGPA:  NI=0  RI=1  GTI=02  SSNI=1  PCI=1
                    TT=027  NP=--  NAI=---  ADDR=123410
                    PC=   2-011-1        SSN=002
             LSN=lsn2111  GTTSET=(1)
             Report Date:08-12-26  Time:17:51:26
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
optional text field
Optional text field providing additional information about the error. Possible text display and definitions may include:
INV DMA LEN=xxx
DMA Length too big or too small: After SCCP encoding of translated MSU DMA Length became too big or too small.
UNSUP Clg GTI=x
GTT attempted on Unsupported CgPA GTI=x
UNSUP Cld GTI=x
GTT attempted on Unsupported CdPA GTI=x
INV Clg GTI=x
GTT attempted on INV CgPA GTI=x
INV Cld GTI=x
GTT attempted on INV CdPA GTI=x
GTCNV:Cld ANSI->ITU fail
Invalid CdPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Clg ANSI->ITU fail
Invalid CgPA GTI for ANSI-to-ITU GTCNV table: ANSI MSU is GTT translated to ITU, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT) are not found in GTCNV table
GTCNV:Cld ITU->ANSI fail
Invalid CdPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CdPA GTA record has NGTI as not provisioned, so GTT is using Default GTT (GTCNV table) to convert CdPA, but CdPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
GTCNV:Clg ITU->ANSI fail
Invalid CgPA GTI for ITU-to-ANSI GTCNV table: ITU MSU is GTT translated to ANSI, CgPA RI=GT, SCCP Conversion used Default GTT (GTCNV table) to convert CgPA, but CgPA GTCNV Selectors (GTI, TT, possibly NP and NAI if GTI=4) are not found in GTCNV table
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact the distant end node this message refers to and verify action is being taken to correct the SCCP encode failure problem.

  1. Determine whether the MSU was processed by a service that does not support network crossing (ANSI <-> ITU).
    The following are some of the services that do not support network crossing (not a complete list):
    • AIQ
    • APORT
    • GPORT
    • ATINPQ
    • EIR
    • INPQ
    • MNP SMS
    • VFLEX
  2. If the MSU was processed by a service that does not support network crossing, check the originating network domain and the destination network domain to determine whether network crossing (ANSI <-> ITU) occurred. If so, the MSU was discarded and UIM 1332 was issued. Correct the network crossing problem.
  3. If the problem is not caused by a service that does not support network crossing, contact the distant end node that this message refers to and verify that action is being taken to correct the SCCP encode failure problem.

3.3.218 1233 - MTP Invalid ITU TFR RCVD

This message indicates an ITU TFR (Transfer Restricted) procedure was received on a linkset that is not configured to receive these procedures.

Example 
RLGHNCXA21W 00-11-18 19:12:00 EST EAGLE 35.0.0
0147.1233 CARD 1201,A INFO MTP Invalid ITU TFR RCVD
OPC=001-001-001 CPC=002-002-002
LSN=lsn01a
Legend
CPC
Concerned point code
LSN
Linkset name
OPC
Origination point code

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify whether the MTP (Message Transfer Part) is supposed to support an ITU TFR on the linkset on which it was received.

    The ITUTFR procedure is valid for ITU national linksets only. As currently configured, the linkset does not accept TFRs.

  2. If ITUTFRs are to be accepted on the linkset, you must reconfigure the linkset to accept them.

    Use the itutfr=on parameter in the chg-ls command to enable the transfer restricted procedure. You must specify this parameter on each ITU national linkset you want to receive ITUTFRs.

3.3.219 1234 - LNP Day Meas. Discarded for NPANXX

This message is indicates the Daily LNP NPANXX measurement counts are incorrect because of discards due to provisioning.

Example 
station5 00-04-18 19:12:00 EST EAGLE 31.0
0002.1234 CARD 1201 INFO LNP Day Meas. Discarded for NPANXX

Alarm Level: No alarm condition. The message is informational only.

Recovery

Correct counts can be derived via calculation from LNP queries - discards - LRN pegs.

3.3.220 1235 - Unable to connect Primary SFLOG Server

This message indicates the connection to Primary SFLOG server cannot be established.

Example

0002.1235    CARD 1201     INFO    Unable to connect Primary SFLOG server
                 IP: 123.678.123.467   FTP Error: 24
                 File Name: tekelecstp_sflog_150429_031655.pcap

  Report Date: 15-04-30  Time: 16:27:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.221 1236 - Unable to connect both SFLOG Servers

This message indicates the connection to the Primary and Secondary SFLOG servers cannot be established.

Example

0002.1236    CARD 1202     INFO    Unable to connect both SFLOG servers
                 IP: 123.678.123.467   FTP Error: 11
                 File Name: tekelecstp_sflog_150429_031655.pcap

  Report Date: 15-04-30  Time: 16:27:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.222 1237 - Dynamic database audit not current

The dynamic database audit cannot determine whether the dynamic database is inconsistent because there has not been the required quiet period (500 milliseconds by default) to perform the audit. There are always inconsistencies among the copies of the dynamic database on the LIM and Service Module cards while the networks is updating the cards.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1237 SYSTEM INFO Dynamic database audit not current

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Determine whether there are issues with links, point codes, linksets, or SSN that are causing network status changes. If so, use your site's normal procedures to address the problems.
  2. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.223 1238 - Full LNP Database Reload Initiated

This message indicates that a cold restart is required for a TSM/BLM card. In this case, the entire LNP database is reloaded to the card.

Example 
station1234 96-08-01 16:28:08 EST EAGLE 35.0.0
1234.1238 SYSTEM INFO Full LNP database reload initiated:
CARD=1101 GPL=SCCP CAUSE=<xxxxxxxx>
where <xxxxxxxx> is one of the following parameters:

Table 3-12 CAUSE Parameters

Parameter Description
XILINX M256 Xilinx version has changed.
POWER ON Power on reset.
DB VER LNP database version has changed.
DB LVL Database level is not supported or difference exceeds incremental loading capability.
HW ERR Hardware error bit checks on the card fail.
CHECKSUM Checksum comparisons of the LNP database fail.
NO AUDIT Unable to perform LNP DB audit. LNP audit not on or excessive number of unknown checksums.
USER REQ User initiated init-card or init-sys command reload type cold.
OTHER Other or unknown.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If this UIM indicates that there is a hardware error or the database checksum test failed, there may be a hardware problem.

    When this condition repeats (the board resets and displays the same conditions again), do the following:

    1. Reseat the card.
    2. Replace the card to determine if it is defective.
  2. For additional support, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.224 1239 - Ntwrk Card Reload Failed during Upg

This message indicates the OAM has determined that a card has failed to load.

Example

xxxx.1239    SYSTEM        INFO      Ntwrk Card Reload Failed during Upg
                         CARD=1103    GPL=SS7ANSI
                         Report Date:02-01-08  Time:01:24:34

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Manually download card(s) running non-approved flash.

3.3.225 1240 - MAP SCCP Validation Fail

This message indicates that the MAP and SCCP parameter validation performed by SCPVAL GTT Action has failed. Look for the validation failure reason printed by the UIM.

Example

5072.1240    CARD 1105     INFO    GTT Action MAP-SCCP validation FAILED
                 Cause: SMRPDA-CDPA Digits Mismatch
                 OPC=   7-101-0        DPC=   1-001-0
                 CDPA:  NI=0  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=010  NP=01  NAI=004  ADDR=9192051234
                        PC=   1-001-0        SSN=---
                 CGPA:  NI=0  RI=1  GTI=00  SSNI=1  PCI=1
                        PC=   7-101-0        SSN=008
                 SMRPDA: NP=1    NON=1    ADDR=9192056000
                 LSN=ls710100  Op-Code= 46  GTT Action Set=scpval1
                 Report Date:15-08-01  Time:15:50:30

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.226 1241 - SCCP/SFAPP Card logging capacity exceeded

This message indicates the SCCP/SFAPP card logging capacity has been exceeded.

Example 

XXXX.1241    CARD XXXX     INFO      SCCP/SFAPP Card logging capacity exceeded

Alarm Level: No alarm condition. The message is informational only.

Recovery

Reduce the card logging below the recommended capacity level.

3.3.227 1242 - Conv to intl num - Dflt CC not found

This message indicates that the default country code is not defined.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1242    CARD 1103,A     INFO    Conv to intl num - Dflt CC not found
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1242    CARD 1103,A     INFO    Conv to intl num - Dflt CC not found
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
[/concept/concept/task/taskbody/context/p/dl/dlentry/dt {"acro"}) LSN (dt]
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Define the default CC using the chg-stpopts:defcc command. Refer to the Commands Manual for the proper usage.

3.3.228 1243 - Conv to intl num - Dflt NC not found

This message indicates that the default network destination code is not defined.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1243    CARD 1103,A     INFO    Conv to intl num - Dflt NC not found
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1243    CARD 1103,A     INFO    Conv to intl num - Dflt NC not found
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
[/concept/concept/task/taskbody/context/p/dl/dlentry/dt {"acro"}) LSN (dt]
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Define the default CC using the chg-stpopts:defndc command. Refer to the Commands Manual for the proper usage.

3.3.229 1244 - Conv to intl num - Dflt MCC Not Found

This message indicates that the default E212 mobile country code is not defined.

Example 
station1234 99-08-30 16:28:08 EST EAGLE 35.0.0
0018.1244 CARD 1103,A INFO Conv to intl num - Dflt MCC not found
SIO=03 OPC=001-001-001 DPC=002-002-002
SCCP MSG TYPE=04
CDPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
TT=250 NP=04 NAI=010 ADDR=123456789012345678901
PC=003-003-003 SSN=005
CGPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
TT=100 NP=07 NAI=012 ADDR=012345678901234567890
PC=001-001-001 SSN=004
LSN=A1234567
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Define the default CC using the chg-gsmopts:defmcc command. Refer to the Commands Manual for the proper usage.

3.3.230 1245 - Conv to intl num - Dflt MNC Not Found

This message indicates that the default E212 mobile network code is not defined.

Example 
station1234 99-08-30 16:28:08 EST EAGLE 35.0.0
0018.1245 CARD 1103,A INFO Conv to intl num - Dflt MNC not found
          SIO=03 OPC=001-001-001 DPC=002-002-002
          SCCP MSG TYPE=04
          CDPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
                TT=250 NP=04 NAI=010 ADDR=123456789012345678901
                PC=003-003-003 SSN=005
          CGPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
                TT=100 NP=07 NAI=012 ADDR=012345678901234567890
                PC=001-001-001 SSN=004
          LSN=A1234567
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Define the default CC using the chg-gsmopts:defmnc command. Refer to the Commands Manual for the proper usage.

3.3.231 1246 - Invalid Length of Conditioned Digits

This message indicates that the length of the conditioned international number is less than 5 or greater than 15 digits.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 46.3.0.0
0018.1246    CARD 1103,A     INFO    Invalid length of conditioned digits
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              INCM DN: 4605523 
COND DN: 19194605523
LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1246    CARD 1103,A     INFO    Invalid length of conditioned digits
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              INCM DN: 4605523 
COND DN: 19194605523
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Use an international number that is within the proper range - 5 or greater and 15 or less.

3.3.232 1247 - Conversion of MGT to IMSI not possible

This message indicates that the E212 mobile country code for the E214 mobile network code is not defined.

Example 
station1234 99-08-30 16:28:08 EST EAGLE 35.0.0
0018.1247 CARD 1103,A INFO Conversion of MGT to IMSI not possible
SIO=03 OPC=001-001-001 DPC=002-002-002
SCCP MSG TYPE=04
CDPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
TT=250 NP=04 NAI=010 ADDR=123456789012345678901
PC=003-003-003 SSN=005
CGPA: NI=1 RI=0 GTI=04 SSNI=1 PCI=1
TT=100 NP=07 NAI=012 ADDR=012345678901234567890
PC=001-001-001 SSN=004
LSN=A1234567
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Enter the E214 part for the E214 code in the database using the chg-gsmopts:ccnc=xxxxxxxx:mccmnc=xxxxxxx command. Refer to the Commands Manual for the proper usage.

3.3.233 1248 - GSM MAP Screening rcvd unknown originator

This message occurs when an MSU arrives with a SSN and MAP Op-Code that exist in the GSM SSN and MAP Op-Code tables, but the CGPA address does not exist in the GSM MAP Screening table or the CgPA address exists in the table but with an incorrect NPV/NAIV. In this case, the default action for the Op-Code applies.

Example 
RLGHNCXA21W 00-11-18 18:59:23 EST EAGLE 35.0.0
0018.1248 CARD 1103 INFO GSM MAP Screening rcvd unknown originator
OPC=001-001-001
CDPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=250 NP=04 NAI=010 ADDR=123456789012345678901
PC=003-003-003 SSN=005
CGPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=100 NP=07 NAI=012 ADDR=012345678901234567890
PC=001-001-001 SSN=004
DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
2e cf 01 00 d0 02 83 01 f2 25 aa 0b
84 09 01 00 11 0a 19 49
Op-Code=61 Forbidden Param=N/A Action=Discard
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
GTI
Global title indicator
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OP-CODE
Operation Code
OPC
Origination point code
PARAM
Parameter
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. To prevent the GSM screening from disallowing this MSU, you can add the CgPA address to the GSMMAP or correct the CgPA address NPV or NAIV.
  2. Alternatively, you may choose to disable MPS Screening on the specific linkset entirely.

    In an emergency situation for example, you can prevent MAP Screening from occurring on any suspected linkset with the chg-ls:gsmscrn=off command. Using this command means no MAP Screening will be performed on any MSU arriving through the linkset, which results in UIM #1248 no longer appearing.

  3. Another choice is to change the default action shown in the example.

    It shows the Action=Discard for any MSU with Op-Code=61. This choice lets you set the default action to Pass; specify the command chg-gsms-opcode:opname= <insert the opname corresponding to the Op-Code> :ndfltact=pass. This action does not prevent UIMs from being reported, but it does prevent the specified Op-Code from being discarded.

  4. If the frequency of UIM #1248 messages is distracting, you can limit the number of UIMs displayed per time interval for a specific UIM.

    Use the command set-uim-acthresh:limit=1:intrvl=5:uimn=1248 to limit the output of UIM #1248 to one output every 5 minutes.

    Note:

    Use this suggestion sparingly, if at all. This action has value in temporarily suppressing a large volume of UIMs while diagnosing a MAP Screening situation.

3.3.234 1249 - SCCP rcvd GSM MAP Opcode w/forbidden param

This message occurs when an MSU is screened in the GSM MAP Screening table and the MSU was found to contain a forbidden parameter as provisioned in the GSM MAP Screening table. The action that applies is taken from the matching entry in the GSM MAP Screening table.

Example 
RLGHNCXA21W 00-11-18 18:59:23 EST EAGLE 35.0.0
0018.1249 CARD 1103 INFO SCCP rcvd GSM MAP Op-Code w/forbidden param
OPC=001-001-001
CDPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=250 NP=04 NAI=010 ADDR=123456789012345678901
PC=003-003-003 SSN=005
CGPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=100 NP=07 NAI=012 ADDR=012345678901234567890
PC=001-001-001 SSN=004
DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
2e cf 01 00 d0 02 83 01 f2 25 aa 0b
84 09 01 00 11 0a 19 49
Op-Code=### Forbidden Param=N/A Action=PASS
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
GTI
Global title indicator
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OP-CODE
Operation Code
OPC
Origination point code
PARAM
Parameter
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. The GSM MAP Screening table has successfully screened the forbidden parameter.

    The resultant action is performed from the matching entry.

  2. To alter the screening being performed, redefine the GSM MAP Screening table using the gsmmap commands.

3.3.235 1250 - SCCP rcvd undefined MAP Op-Code

This message occurs when an MSU passes the origination or destination SSN screening process and the MAPOp-Code table is searched, but the Op-Code of the MSU is not found in the MAP Op-Code table. In this case, the default action from the STPOPTS table applies.

Example 
RLGHNCXA21W 00-11-18 18:59:23 EST EAGLE 35.0.0
0018.1250 CARD 1103 INFO SCCP rcvd undefined MAP Op-Code
OPC=001-001-001
CDPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=250 NP=04 NAI=010 ADDR=123456789012345678901
PC=003-003-003 SSN=005
CGPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=100 NP=07 NAI=012 ADDR=012345678901234567890
PC=001-001-001 SSN=004
DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
2e cf 01 00 d0 02 83 01 f2 25 aa 0b
84 09 01 00 11 0a 19 49
Op-Code=### Forbidden Param=N/A Action=ATIERR
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
GTI
Global title indicator
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OP-CODE
Operation Code
OPC
Origination point code
param
Parameter
PC
Point code
pci
Protocol control information
ri
Routing indicator
SIO
Service information octet
SSN
Subsystem number
ssni
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. The GSM MAP Op-Code table was searched, and the Op-Code of the MSU was not found.
  2. The GSM MAP Op-Code table has successfully screened an Op-Code that was not included in the GSM MAP Opcode table.
  3. However, if the Op-Code should not be screened, you can add it into the GSM MAP Op-Code table.
  4. To alter the screening being performed, change the default action for GSM screening when the Op-Code is not defined with the STPOPTS commands.

3.3.236 1251 - Measurements Data Copy Failure

Measurements data is copied to all MCPM cards after collection. Measurements data copy to a Secondary MCPM failed.

Example 
station5 00-04-18 19:12:00 EST EAGLE 31.3.0
0002.1251 CARD 1201 INFO Measurements data copy failure

Alarm Level: No alarm condition. The message is informational only.

Recovery

There is no immediate action needed, but the message indicates that the error was encountered.

3.3.237 1252 - Report Generation Failure

This message is generated by the Primary MCPM. The measurement report identified in the output message did not generate.

Example 
station5 00-04-18 19:12:00 EST EAGLE 31.3.0
0002.1252 CARD 1201 INFO Report generation failure
IP:111.111.111.111 FTP Error: XXXX
File Name: tues_serv.csv

Alarm Level: No alarm condition. The message is informational only.

Recovery

Enter the rept-ftp-meas command to manually initiate the generation and FTP transfer of the indicated measurement report.

Refer to the Commands Manual for the correct usage of this command.

3.3.238 1253 - Report transfer failure FTP Server

This message is generated by the Primary MCPM. The FTP transfer of the indicated report failed.

Example 
station5 00-04-18 19:12:00 EST EAGLE 31.3.0
0002.1253 CARD 1201,A INFO Report transfer failure FTP Server
IP:111.111.111.111 FTP Error: XXXX
File Name: tues_serv.csv

Alarm Level: No alarm condition. The message is informational only.

Recovery

Enter the rept-ftp-meas command to manually initiate the generation and FTP transfer of the indicated measurement report. Refer to the Commands Manual for the correct usage of this command.

3.3.239 1254 - Scheduled transfer failure

This message is generated by the Primary MCPM. Some of the reports scheduled to be generated and transferred were not transferred.

Example 
station5 00-04-18 19:12:00 EST EAGLE 31.3.0
0002.1254 CARD 1201 INFO Scheduled transfer failure

Alarm Level: No alarm condition. The message is informational only.

Recovery

Enter the rept-ftp-meas command to manually initiate the generation and FTP transfer of the affected measurement report. Refer to the Commands Manual for the correct usage of this command.

3.3.240 1255 - IS-41 LNP Qry rejected: WNP is OFF

The EAGLE has rejected an LNPQS query that is decoded as an IS-41 Query because the appropriate WNP (Wireless Number Portability) feature is not on.

Example 
RLGHNCXA21W 03-04-18 19:02:05 EST EAGLE 31.3.0
0112.1255 CARD 1103,A1 INFO IS-41 LNP Qry rejected: WNP is OFF
SIO=83 OPC=001-101-001 DPC=001-001-001
CDPA: AI=cb SSN=016 TT=012
ADDR=919380
CGPA: AI=c3 PC=001-101-001 SSN=016
DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
2e cf 01 00 d0 02 83 01 f2 25 aa 0b
84 09 01 00 11 0a 19 49
LSN=e1m1s1
Legend
ADDR
Address
AI
Address Indicator
cdpa length
Called party address length
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type (for example, connection request, connection confirm, connection refused)
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If you want to support the WNP feature, issue the chg-feat:wnp=on command to process IS-41 LNP queries.
  2. If you do not want to support the WNP feature, ignore this informational message.
  3. For additional information or assistance about the WNP or any feature to purchase, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.241 1256 - NP Circular Route Detected

This message indicates the network has incorrect number portability data for a subscriber.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1256    CARD 1103,A     INFO    NP Circular Route Detected
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1256    CARD 1103,A     INFO    NP Circular Route Detected
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
GTI
Global title indicator
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify and update number portability data.

3.3.242 1257 - DB restore has cleared and Disabled PDS

A DB restore has rendered the data on PDS table obsolete. The PDS table will be updated when the OAM is rebooted.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0014.1257 SYSTEM INFO DB restore has cleared and Disabled PDS

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.243 1258 - Map Screening cannot Forward MSU

This message occurs when an MSU selected by MAP Screening for the Forward screening action cannot be forwarded.

Note:

Additional reasons for this alarm include:
  1. If unsupported domain crossing is occurring (from or to ANSI/ITUN24)
  2. If Alias PC was not found for CgPA PC
  3. If there is no space to insert CdPA PC when it was not there in the original MSU
Example 
RLGHNCXA21W 00-11-18 18:59:23 EST EAGLE 35.0.0
0018.1258 CARD 1103 INFO Map Screening cannot Forward MSU
OPC=001-001-001
CDPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=250 NP=04 NAI=010 ADDR=123456789012345678901
PC=003-003-003 SSN=005
CGPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=100 NP=07 NAI=012 ADDR=012345678901234567890
PC=001-001-001 SSN=004
Op-Code=61 Forbidden Param=N/A Action=Discard
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
GTI
Global title indicator
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OP-CODE
Operation Code
OPC
Origination point code
PARAM
Parameter
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If the DPC indicated in the message should not be routed to, no further action is necessary.
  2. If the DPC should be routed to from the EAGLE 5 ISS, use the ent-map command to enter the DPC into the mated application (MAP) table.
  3. If the subsystem indicated in the message is not a mated application to the EAGLE 5 ISS, no further action is necessary.
  4. If the SCCP message should have been routed, use the ent-map command to add the subsystem number to the mated application (MAP) table.

3.3.244 1259 - Map Screening cannot Duplicate MSU

This message occurs when an MSU selected by MAP Screening for the Duplicate screening action cannot be duplicated and/or routed to the duplicate node.

Example 
RLGHNCXA21W 00-11-18 18:59:23 EST EAGLE 35.0.0
0018.1259 CARD 1103 INFO Map Screening cannot Duplicate MSU
OPC=001-001-001
CDPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=250 NP=04 NAI=010 ADDR=123456789012345678901
PC=003-003-003 SSN=005
CGPA: NI=1 RI=0 GTI=04 SSNI=0 PCI=1
TT=100 NP=07 NAI=012 ADDR=012345678901234567890
PC=001-001-001 SSN=004
Op-Code=61 Forbidden Param=N/A Action=Discard
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
GTI
Global title indicator
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OP-CODE
Operation Code
OPC
Origination point code
PARAM
Parameter
PC
Point code
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If the DPC indicated in the message should not be routed to, no further action is necessary.
  2. If the DPC should be routed to from the EAGLE 5 ISS, use the ent-map command to enter the DPC into the mated application (MAP) table.
  3. If the subsystem indicated in the message is not a mated application to the EAGLE 5 ISS, no further action is necessary.
  4. If the SCCP message should have been routed, use the ent-map command to add the subsystem number to the mated application (MAP) table.

3.3.245 1260 - LSS: Unsupported TCAP msg type

This message indicates that the LSS (local subsystem) received an SCCP message containing an unsupported TCAP (transaction capabilities application portion) message type.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1260 CARD 1103,A1 INFO LSS: Unsupported TCAP msg type
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.246 1261 - LSS: Invalid len in transaction portion

This message indicates that the LSS (local subsystem) received a TCAP message containing an invalid length in the transaction portion of the message.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1261 CARD 1103,A1 INFO LSS: Invalid len in transaction portion
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.247 1262 - LSS: Invalid len in dialogue portion

This message indicates that the LSS (local subsystem) received a TCAP message with an invalid length in the dialogue portion of the message.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1262 CARD 1103,A1 INFO LSS: Invalid len in dialogue portion
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.248 1263 - LSS: Invalid len in component portion

This message indicates that the LSS (local subsystem) received a TCAP message with an invalid length in the component portion of the message.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1263 CARD 1103,A INFO LSS: Invalid len in component portion
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.249 1264 - LSS: No originating transaction ID

This message indicates that the LSS (local subsystem) received a TCAP message that does not have an originating transaction ID.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1264 CARD 1103,A1 INFO LSS: No originating transaction ID
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.250 1265 - LSS: Invalid transaction ID len

This message indicates that the LSS (local subsystem) received a TCAP message containing an invalid transaction ID length.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1265 CARD 1103,A1 INFO LSS: Invalid transaction ID len
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.251 1266 - LSS: Destination transaction ID in Begin

This message indicates that the LSS (local subsystem) received a Begin TCAP message containing a destination transaction ID. (The Begin message should have an originating transaction ID only. A destination transaction ID is valid only in Abort, Continue, and End TCAP messages.)

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1266 CARD 1103,A1 INFO LSS: Destination transaction ID in Begin
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.252 1267 - LSS: No External element

This message indicates that the LSS (local subsystem) received a TCAP message that does not contain an External element in the dialogue portion of the message.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1267 CARD 1103,A1 INFO LSS: No External element
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.253 1268 - LSS: No External Object Identifier

This message indicates that the LSS (local subsystem) received a TCAP message that does not contain an Object Identifier element in the External element in the dialogue portion of the message.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1268 CARD 1103,A1 INFO LSS: No External Object Identifier
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.254 1269 - LSS: Not Structured Dialogue

This message indicates that the LSS (local subsystem) received a TCAP message with an Object Identifier value in the External element in the dialogue portion that does not indicate a structured dialogue as specified in ITU Q.773.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1269 CARD 1103,A1 INFO LSS: Not Structured Dialogue
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.255 1270 - LSS: No External ASN1-Type

This message indicates that the LSS (local subsystem) received a TCAP message that does not have an ASN1-Type element in the External element in the dialogue portion of the message.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1270 CARD 1103,A1 INFO LSS: No External ANS1-Type
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.256 1271 - LSS: No Dialogue Request

This message indicates that the LSS (local subsystem) received a TCAP message that odes not have a Dialogue Request element in the ASN1-Type element in the dialogue portion of the message.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1271 CARD 1103,A1 INFO LSS: No Dialogue Request
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.257 1272 - LSS: No Application Context Name

This message indicates that the LSS (local subsystem) received a TCAP message that does not have an Application Context Name element in the Dialogue Request element in the dialogue portion of the message.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1272 CARD 1103,A1 INFO LSS: No Application Context Name
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.258 1273 - LSS: No ACN Object Identifier

This message indicates that the LSS (local subsystem) received a TCAP message that does not have an Object Identifier element in the Application Context Name element in the dialogue portion of the message.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1273 CARD 1103,A1 INFO LSS: No ACN Object Identifier
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.259 1274 - LSS: No component portion

This message indicates that the LSS (local subsystem) received a TCAP message that does not contain a component portion tag.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1274 CARD 1103,A1 INFO LSS: No component portion
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.260 1275 - LSS: No Invoke component

This message indicates that the LSS (local subsystem) received a TCAP message that does not contain an Invoke component.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1275 CARD 1103,A1 INFO LSS: No Invoke component
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.261 1276 - LSS: No Invoke ID

This message indicates that the LSS (local subsystem) received a TCAP message that does not contain an Invoke ID within the component.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1276 CARD 1103,A1 INFO LSS: No Invoke ID
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.262 1277 - LSS: No operation code

This message indicates that the LSS (local subsystem) received a TCAP message that does not contain an operation code tag within the component.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1277 CARD 1103,A2 INFO LSS: No operation code
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.263 1278 - LSS: No parameter (set/sequence)

This message indicates that the LSS (local subsystem) received a TCAP message that does not contain a parameter, parameter set, or a parameter sequence within the component.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1278 CARD 1103,A1 INFO LSS: No parameter (set/sequence)
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.264 1279 - LSS: Unsupported network type

This message indicates that the LSS (local subsystem) received an SCCP message of an unsupported network type.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1279 CARD 1103,A INFO LSS: Unsupported network type
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.265 1280 - LSS: Unsupported SCCP msg type

This message indicates that the LSS (local subsystem) received an SCCP message of an unsupported SCCP message type.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1280    CARD 1103,A     INFO    LSS: Unsupported SCCP msg type
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1280    CARD 1103,A     INFO    LSS: Unsupported SCCP msg type
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Check translations on the originating switch to determine the trouble.

3.3.266 1282 - LSS: Unsupported SCCP CDPA GTI

This message indicates that the LSS (local subsystem) received an SCCP message for which the GTI (Global Title Indicator) value for the called party (CDPA) is unsupported.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1282 CARD 1103,A1 INFO LSS: Unsupported SCCP CDPA GTI
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.267 1283 - LSS: Unsupported SCCP CGPA RI

This message indicates that the LSS (local subsystem) received an SCCP message for which the RI (Routing Indicator) value for the calling party (CGPA) is unsupported.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1283 CARD 1103,A1 INFO LSS: Unsupported SCCP CGPA RI
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.268 1284 - LSS: Unknown SSP PC

This message indicates that the LSS (local subsystem) received an SCCP message that contained an SSP (Service Switching Point) point code (PC) that is not in the Eagle routing table. The SSP PC is the CGPA PC (if it exists) or the OPC, otherwise. In the example below, the SSP PC is 001-001-002.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1284 CARD 1103,A2 INFO LSS: Unknown SSP PC
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. The LSS received a message that does not have a corresponding SSP point code entry in the Eagle routing table.
  2. You must decide whether you want to accept queries from that SSP.
    1. If you choose to not respond to queries from that SSP, use the gateway screening feature to stop this information message from re-appearing by having the Eagle system reject queries from that specific SSP.

      No further action is necessary.

    2. If you want to respond to queries from that SSP, continue with the next step.
  3. List the routing table entry for the SSP in question with the rtrv-rte command.
    1. If the retrieve route command shows the SSP point code has an Eagle routing table entry, which is not expected since this message says no entry exists, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA about this situation.

      Do not continue to other steps of this procedure.

    2. If the retrieve route command shows no entry in the routing table, which is expected here, continue with the next step.
  4. List the destination table entry for the SSP in question with the rtrv-dstn command.
    1. If the SSP point code is not in the Eagle destination table, add that entry with the ent-dstn command.

      (For detailed information about using the ent-dstncommand, refer to “Adding a Destination Point Code” in Chapter 2, “Configuring Destination Tables” in the Database Administration Manual - SS7 manual.) Proceed to uam-and-uim-troubleshooting-procedures1.html.

    2. If the SSP point code is in the Eagle destination table, continue with the next step.
  5. Enter the route set for the SSP point code by issuing one of more ent-rte commands.

    (For detailed information about using the ent-rte command, refer to “Adding a Route” in the chapter “SS7 Configuration” in the Database Administration Manual - SS7 manual.)

3.3.269 1285 - LSS: No SCCP CGPA SSN

This message indicates that the LSS (local subsystem) received an SCCP message in which the subsystem number (SSN) for the calling party (CGPA) is missing.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1285 CARD 1103,A1 INFO LSS: No SCCP CGPA SSN
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.270 1286 - LSS: Invalid INAP/CAMEL digits length

This message indicates that the LSS (local subsystem) received an INAP message in which the Called Party Number parameter length is invalid.

Example 
RLGHNCXA21W 07-12-18 18:59:23 EST EAGLE 37.6.0
0101.1286    CARD 1103,A1  INFO      LSS: Invalid INAP/CAMEL digits length
             SIO=03   OPC=001-001-001       DPC=002-002-002
             CDPA: AI=52  SSN=005 TT=250
                   ADDR=ABCDEF1234567890ABCDE
             CGPA: AI=43  PC=001-001-001         SSN=002
             LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary. The querying node should be modified to generate less than 22 digits in the parameter.

3.3.271 1287 - LSS: Unsupported ACN Object ID len

This message indicates that the LSS (local subsystem) received a TCAP message in which the length of the Application Context Name’s Object Identifier is unsupported.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1287 CARD 1103,A1 INFO LSS: Unsupported ACN Object ID len
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.272 1288 - LSS: Unsupported operation code

This message indicates that the LSS (local subsystem) received a TCAP message in which the operation code is unsupported.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1288 CARD 1103,A1 INFO LSS: Unsupported operation code
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.273 1289 - LSS: No parameter sequence

This message indicates that the LSS (local subsystem) received a TCAP message that has a single parameter or a parameter set instead of the expected parameter sequence.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1289 CARD 1103,A1 INFO LSS: No parameter sequence
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.274 1290 - LSS: No INAP ServiceKey parameter

This message indicates that the LSS (local subsystem) received an INAP message that does not contain the Service Key parameter.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1290 CARD 1103,A1 INFO LSS: No INAP ServiceKey parameter
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.275 1291 - LSS: No INAP/CAP CalledPartyNumber param

This message indicates that the LSS (local subsystem) received an INAP message that does not contain an Called Party Number parameter.

Example 
RLGHNCXA21W 07-12-18 18:59:23 EST EAGLE 37.6.0
0101.1286    CARD 1103,A1  INFO      LSS: No INAP/CAP CalledPartyNumber param
             SIO=03   OPC=001-001-001       DPC=002-002-002
             CDPA: AI=52  SSN=005 TT=250
                   ADDR=ABCDEF1234567890ABCDE
             CGPA: AI=43  PC=001-001-001         SSN=002
             LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.276 1292 - LSS: Parameters out of sequence

This message indicates that the LSS (local subsystem) received a TCAP message in which the mandatory and conditional parameters are not in the correct sequence.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1292 CARD 1103,A1 INFO LSS: Parameters out of sequence
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.277 1293 - LSS: Invalid num of digits in INAP CdPN

This message indicates that the LSS (local subsystem) received an INAP message containing an invalid number of digits in the Called Party Number (CdPN) parameter.

Example 
RLGHNCXA21W 99-12-18 18:59:23 EST EAGLE 31.3.0
0101.1293 CARD 1103,A1 INFO LSS: Invalid num of digits in INAP CdPN
SIO=03 OPC=001-001-001 DPC=002-002-002
CDPA: AI=52 SSN=005 TT=250
ADDR=ABCDEF1234567890ABCDE
CGPA: AI=43 PC=001-001-001 SSN=002
LSN=A1234567
Legend
ADDR
Address
AI
Address Indicator
CGPA
Calling party address
CDPA
Called party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.278 1294 - Invalid digits in MAP MSISDN parameter

This message indicates that no valid digits were found in the MAP MSISDN parameter.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1294    CARD 1103,A     INFO    Invalid digits in MAP MSISDN parameter
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1294    CARD 1103,A     INFO    Invalid digits in MAP MSISDN parameter
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
gti
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Change the message to have valid digits (digits length greater than 0) in the MSISDN parameter.

3.3.279 1295 - Translation PC is EAGLE 5 ISS’s

This message indicates that the point code translation is invalid because it is one the EAGLE 5 ISS’s own point codes.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1295    CARD 1103,A     INFO    Translation PC is EAGLE 5 ISS’s
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1295    CARD 1103,A     INFO    Translation PC is EAGLE 5 ISS’s
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
add
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indictor
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No alarm condition. The message is informational only.

Recovery

Change the translation point code for the entry to a non-Eagle’s point code.

Provision the entity data from the EPAP/ELAP. Refer to the EPAP Administration Manual or the ELAP Administration and LNP Feature Actiivation, and see the topic “Manage Network Entities” for details about changing this entity data.

3.3.280 1296 - Translation PC type is ANSI

This message indicates that the point code translation is invalid because it is an ANSI point code.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1296    CARD 1103,A     INFO    Translation PC type is ANSI
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1296    CARD 1103,A     INFO    Translation PC type is ANSI
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Change the translation point code type to a non-ANSI type.

Provision the point code type from the EPAP. Refer to the EPAP Administration Manual and see the topic “Manage Network Entities” for details about changing this entity data.

3.3.281 1297 - Invalid prefix/suffix digit length

This message indicates that the attempted digit action of prefixing or suffixing the entity ID is invalid because the combined length of the entity ID and GT digits is greater than 21 digits.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1297    CARD 1103,A     INFO    Invalid prefix/suffix digit length
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1297    CARD 1103,A     INFO    Invalid prefix/suffix digit length
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Change the attempted digit action or decrease the length of the entity ID or the GT digits to a length of 21 digits or less.

Provision the digit action or the entity ID length from the EPAP. Refer to the EPAP Administration Manual for details.

3.3.282 1298 - SIP message decode failed

SIP message parsing FAILS. Examples of decoding fail:

  1. TEL-URI with a Local Number does not contain a "phone-context" parameter
  2. SIP-URI does not contain "user=phone" parameter
  3. SIP INVITE does not have E164 num
Example
         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0014.1298    CARD 1103,B   INFO     SIP msg decode failed 
                 CSeq No: 96781            Cname: tcp1107d
                 Reason: Incorrect Content-Length Header
                 Report Date:10-10-12  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.283 1301 - SECMTPMATE - rcvd mate PC on non C-link

This message indicates the Eagle received a MTP message that failed the mate SID verification. The message was discarded.

Example 
RLGHNCXA21W 00-04-18 18:59:58 EST EAGLE 31.3.0
0105.1301 CARD 1205,A INFO SECMTPMATE - rcvd mate PC on non C-link
SIO=0a OPC=003-247-000 DPC=002-000-000
DATA=12 34 56 78 90 12 34 56 78 90 12 34
56 78 90 12 34 56 78 90 12 34 56 78
SR=scrb LSN=A1234567
Legend
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.284 1302 - SECMTPSID - rcvd MSU with OPC = SID

This message indicates the Eagle received a MTP message that failed the self SID verification. The message was discarded.

Example 
RLGHNCXA21W 00-04-18 18:59:58 EST EAGLE 31.3.0
0105.1302 CARD 1205,A INFO SECMTPSID - rcvd MSU with OPC = SID
SIO=0a OPC=003-247-000 DPC=002-000-000
DATA=12 34 56 78 90 12 34 56 78 90 12 34
56 78 90 12 34 56 78 90 12 34 56 78
SR=scrb LSN=A1234567
Legend
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.285 1303 - SECMTPSNM - no rte to OPC/AFTPC

This message indicates the Eagle received a MTP network management message that failed the MTP Network Management Message OPC Verification. The message was discarded.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST EAGLE 35.0.0
0100.1303 CARD 1105,B INFO SECMTPSNM - no rte to OPC/AFTPC
SIO=0a OPC=003-243-000 DPC=000-024-000
H0H1=41 AFTPC=099-099-003
SR=osp3 LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
H0H1
H0/H1 heading code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.286 1304 - SECSCCPSCMG - no rte to AFTPC

This message indicates the Eagle received a MTP network management message that failed the SCMG AFTPC Verification. The message was discarded.

Example 
RLGHNCXA21W 00-04-18 18:59:30 EST EAGLE 31.3.0
0102.1304 CARD 1205,B INFO SECSCCPSCMG - no rte to AFTPC
SIO=03 OPC=003-245-000 DPC=001-004-000
SCMG: TYPE=000 AFTPC=003-003-003
MULT=000 AFTSS=005
SR=scrb LSN=A1234567
Legend
AFTPC
Affected point code (for SCCP messages)
AFTSS
Affected subsystem (identifies the subsystem that failed)
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MULT
SCCP management message multiplicity indicator
OPC
Origination point code
SCMG
SCCP management message
SIO
Service information octet
SR
Screening reference name
TYPE
SCCP management message type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.287 1305 - MTP rcvd UPU - User SCCP, Cause Invalid

This message is generated for a UPU message for a SCCP user when the unavailability cause indicates a SCCP translation exists for a node that does not have a SCCP user part.

Example 
RLGHNCXA21W 00-02-07 11:02:30 EST EAGLE 35.0.0
0100.1305 CARD 1201,A INFO MTP rcvd UPU - user SCCP, Cause invalid
SIO=03 OPC=003-232-000 DPC=001-004-000
AFTPC=004-000-001 UPU=03 UNAVAIL CAUSE=001
LSN=A1234567

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.288 1306 - GSMOPTS: EIR Global Response is ON

The EIR Global Response Type is on. The EIR Global Response Type is set by the chg-gsmopts command and the eirgrsp parameter.

The Global Response Type is used to override the response that is returned to the MSC (Mobile Switching Center). The default value is OFF. When this parameter to OFF, the normal list logic is applied to the IMEI. If the Global Response Type is set to a value other than OFF, there is no list logic processing, and the response corresponding to the eirgrsp value is sent to the MSC.

For more information about eirgrsp, refer to the chg-gsmopts command in the Commands Manual.

Example 
RLGHNCXA21W 03-08-18 19:09:14 EST EAGLE 31.3.0
0140.1306 CARD 1201 INFO GSMOPTS: EIR Global Response is ON

Alarm Level: No alarm condition. The message is informational only.

Recovery

No corrective action is required.

3.3.289 1307 - GSMOPTS: EIR Global Response is OFF

The EIR Global Response Type is off. The EIR Global Response Type is set by the chg-gsmopts command and the eirgrspparameter.

The Global Response Type is used to override the response that is returned to the MSC (Mobile Switching Center). The default value is OFF. When this parameter to OFF, the normal list logic is applied to the IMEI. If the Global Response Type is set to a value other than OFF, there is no list logic processing, and the response corresponding to the eirgrsp value is sent to the MSC.

For more information about eirgrsp, refer to the chg-gsmopts command in the Commands Manual.

Example 
RLGHNCXA21W 03-08-18 19:09:14 EST EAGLE 31.3.0
0140.1307 CARD 1201 INFO GSMOPTS: EIR Global Response is OFF

Alarm Level: No alarm condition. The message is informational only.

Recovery

No corrective action is required.

3.3.290 1308 - Updates inhibited: Target-Cell CRC Fail

This message appears if the new source-cell and the target-cell checksums do not match. This message, similar to UIM 1239, but including the table id, shall be issued by the Eagle User Interface (UI) for each event.

Example
     station1234 96-08-01 16:28:08 EST EAGLE 34.0.0
     1234.1308   SYSTEM INFO    Updates inhibited:Target-Cell CRC Fail
            CARD=1107 TABLE=50  OFFSET=XXXX TRGT CRC=1423697

Alarm Level: No alarm condition. The message is informational only.

Recovery

This is an automatic process and no action is necessary.

3.3.291 1309 - Updates inhibited: Source-Cell CRC Fail

If the source cell fails validation this message, similar to UIM 1239, but including the table ID, shall be issued by the Eagle User Interface (UI) for each event.

Example
    
    station1234 96-08-01 16:28:08 EST EAGLE 34.0.0
    1234.1309 SYSTEM INFO Updates inhibited:Source-Cell CRC Fail
              CARD=1107 TABLE=50 OFFSET=XXXX

Alarm Level: No alarm condition. The message is informational only.

Recovery

This is an automatic process and no action is necessary.

3.3.292 1310 - System Meas. Limit Exceeded for LRN

This UIM is issued if the Measurements Platform is not enabled and if the number of provisioned LRNs exceeds 100,000. When the limit of 100,000 is exceeded, this UIM is notification that the LNP LRN measurements report will be truncated, and additional LRN measurements will not be collected or reported.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 31.3.0
0140.1310 CARD 1201 INFO System Meas. Limit exceeded for LRN

Alarm Level: No alarm condition. The message is informational only.

Recovery

You have two options if this UIM appears:
  • Install the Measurements Platform to increase the reporting limits, or
  • If you have any unused LRN entries, you can remove them such that the number of provisioned LRNs does not exceed the limit of 100,000.

3.3.293 1311 - System Meas. Limit exceeded for NPANXX

This UIM is issued if the Measurements Platform is not enabled and if the number of provisioned NPANXXs exceeds 150,000. When the limit of 150,000 is exceeded, this UIM is notification that the LNP NPANXX measurements report will be truncated, and additional NPANXX measurements will not be collected or reported.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 31.3.0
0140.1311 CARD 1201 INFO System Meas. limit exceeded for NPANXX

Alarm Level: No alarm condition. The message is informational only.

Recovery

You have two options if this UIM appears:
  • Install the Measurements Platform to increase the reporting limits, or
  • If you have any unused NPANXX entries, you can remove them such that the number of provisioned NPANXXs does not exceed the limit of 150,000.

3.3.294 1312 - Dynamic VLR Profile Table Full

This UIM occurs when the VLR profile table is full.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0002.1312    SYSTEM        INFO      Dynamic VLR profile table full
                 Report Date:28-06-18  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Delete entries in the VLR profile table.

3.3.295 1313 - Dynamic VLR Roaming Table Full

This UIM occurs when the VLR roaming table is full.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0002.1313    SYSTEM        INFO      Dynamic VLR roaming table full
                 Report Date:28-06-18  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Delete entries in the VLR roaming table.

3.3.296 1314 - IPS TCP Connection Established

This UIM occurs when any IPS TCP connection is established.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890  
    6731.1314    CARD 1112     INFO    IPS TCP connection established
                 Connection Name : ipstcp
                 Report Date:18-09-21  Time:16:38:33

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.3.297 1315 - IPS TCP connection terminated

This UIM occurs when any IPS TCP connection is terminated.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    6730.1315    CARD 1112     INFO    IPS TCP connection terminated
                 Connection Name : ipstcp
                 Report Date:18-09-21  Time:16:38:33

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Check that the network cable is properly inserted for this card.
  2. Check the remote host to determine if the connection is pingable or not.
  3. Execute the chg-ip-conn:cname=<>:open command.

3.3.298 1316 - SFAPP(P) to OAM Sync Started

This UIM occurs when an SFAPP(P) to OAM Sync has started.

Example 
RLGHNC12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0007.1316    SYSTEM        INFO      SFAPP(P) to OAM Sync started
                 Report Date:18-09-25  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.3.299 1317 - SFAPP(P) to OAM Sync Completed

This UIM occurs when the SFAPP(P) to OAM Sync is complete.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0007.1317    SYSTEM        INFO      SFAPP(P) to OAM Sync Completed
                 Report Date:18-09-25  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is necessary.

3.3.300 1318 - ICNP: OPC/DPC Correlation Problem

This UIM occurs when the DPC of the IAM is not the True or Secondary Point Code assigned to the OPC in the routing table.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 33.2.0
0140.1318 CARD 1201 INFO ICNP:  OPC/DPC correlation problem

Alarm Level: No alarm condition. The message is informational only.

Recovery

Make sure that the OPC is using the True or Secondary Point code assigned to it in the routing table as the DPC of the IAM.

3.3.301 1319 - ICNP: IDCA Not Reachable

This UIM when the required IDCA application is not currently reachable.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 31.3.0
0140.1319 CARD 1201 INFO ICNP:  IDCA is not reachable

Alarm Level: No alarm condition. The message is informational only.

Recovery

If this UIM appears, take these actions:
  • Bring the IDCA application online.
  • Verify the connection between the EAGLE and IDCA.

3.3.302 1320 - FPT value Unprovisioned for Frame

This UIM is periodically raised at hourly intervals, starting at the system initialization time, for all the provisioned frames if the Frame Power Threshold value is not provisioned for that frame.

Example 
RLGHNCXA21W 00-04-18 19:05:43 EST EAGLE 35.0
0021.1320 CARD 1113 INFO FTP value unprovisioned for frame CF00

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Verify that the Frame Power Threshold value is not configured for the provisioned frame for which the UIM is generated by using the following command:

    rtrv-frm-pwr

  2. Configure the appropriate Frame Power Threshold value for the frame using the following command:

    ent-frm-pwr

    Otherwise, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA about the generated UIM.

3.3.303 1321 - Eagle RTDB Birthdate Mismatch

This message appears if the EAGLE 5 ISS connects to an ELAP and the birthdates do not match between the RTDB on the ELAP and the RTDB on the EAGLE 5 ISS.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 35.0.0
0008.1321 SYSTEM INFO Eagle RTDB Birthdate Mismatch

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.304 1322 - EAGLE RTDB Levels Invalid

This message appears if the EAGLE 5 ISS connects to an ELAP and the ELAP's RTDB db-level is less-than the EAGLE 5 ISS's RTDB db-level.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 35.0.0
0008.1322 SYSTEM INFO Eagle RTDB Levels Invalid

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.305 1323 - EAGLE/ELAP TN Quantity Mismatch

This message appears if the EAGLE 5 ISS connects to an ELAP that has a greater number of TNs provisioned than the EAGLE 5 ISS's quantity keys allow.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 35.0.0
0008.1323 SYSTEM INFO Eagle/Elap TN Quantity Mismatch

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.306 1324 - Eagle/Elap NPANXX Quantity Mismatch

This message appears if the EAGLE 5 ISS connects to an ELAP that has a greater number of NPANXXs provisioned than the EAGLE 5 ISS's quantity keys allow.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 35.0.0
0008.1324 SYSTEM INFO Eagle/Elap NPANXX Quantity Mismatch

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.307 1325 - EAGLE/ELAP LRN Quantity Mismatch

This message appears if the EAGLE 5 ISS connects to an ELAP that has a greater number of LRN s provisioned than the EAGLE 5 ISS's quantity keys allow.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 35.0.0
0008.1325 SYSTEM INFO Eagle/Elap LRN Quantity Mismatch

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.308 1326 - Eagle RTDB Depth Alert

RTDB data is stored as inverse tree structures the trees have a maximum depth allowed. This alarm indicates that the maximum depth has been reached for a tree. If the alarm was initiated during a data update, the update will continually fail until there is manual intervention.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 35.0.0
0008.1326 SYSTEM INFO Eagle RTDB Depth Alert

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.309 1327 - Mate PC not Found in table

This UIM indicates the Mate Point Code was not found in the table.

Example 

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    3281.1327    SYSTEM        INFO      Mate PC not Found in table
                 Report Date:28-06-18  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action necessary.

3.3.310 1328 - Incorrect network domain

This UIM indicates the incorrect network domain was entered.

Example 

1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    3281.1328    SYSTEM        INFO      Incorrect network domain
                 Report Date:28-06-18  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Check the network domain entry.

3.3.311 1330 - Mismatched UA Routing Context

This message is issued in the following scenarios:

  1. If routing context is present in a M3UA Data message received by the EAGLE 5 ISS, and no routing key for the receiving M3UA association contains a matching routing context value.

  2. If routing context is absent in a M3UA Data message received by the EAGLE 5 ISS, and the receiving M3UA association’s application server is referenced by a routing key containing routing context.

  3. If routing context is present in a M3UA ASP-Active or ASP-Inactive or DAUD message received by the EAGLE 5 ISS, and no routing key for the receiving M3UA association contains a matching routing context value, then a UIM will be generated.

  4. If routing context is present in a SUA message received by the EAGLE 5 ISS, and no routing key for the receiving SUA association contains a matching routing context value.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
3409.1330 CARD 1305,A INFO Mismatched UA Routing Context
ANAME = m3ua_assoc_0003 M3UA RC=3
Legend
ANAME
The name of the M3UA or SUA Association. This is followed by the user adapter type (M3UA or SUA) and the value of the Routing Context received in the message. If the Routing Context is absent from the message, RC will be displayed as “none.”

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. The use of Routing Context in the Eagle Routing Key configuration and the use of the Routing Context by the far-end Application Server should be made to match so that they are either both using Routing Context –OR- they are both not using Routing Context.
  2. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.312 1331 - IP Route Table Entry Conflict

A conflict exists between user configured static IP routes and dynamically added routes. (The Integrate Message Feeder application monitoring dynamically creates host specific IP routes to an IMF VIP address.) There are two scenarios in which such a conflict can result:

  1. If an Integrated Message Feeder application receives a service accept message and attempts to add a host specific IP route for the IP address received in the service accept message and there is an user configured static IP route (entered by ent-ip-rteEAGLE 5 ISS command) whose destination is the same IP address, then the route is not added and the UIM is sent indicating the route and result.

  2. If a user enters a host specific IP route using the ent-ip-rte command and there currently exists a dynamically added route with the same destination IP address, then the dynamic route is deleted, the static route is added, and this UIM indicating the result is generated.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0003.1331 CARD 1213 INFO IP Route Table Entry Conflict
Dynamic IP Route Add Fail
Destination = 172.130.155.110
Gateway = 172.120.154.111
Mask = 255.255.255.255
Report “Date:02-02-21 Time:02:07:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Resolve the IP Address conflict.

One must either change the Integrated Message Feeder application VIP address or delete the static IP address using the following command:

dlt-ip-rte

3.3.313 1332 - Invalid Initial M2PA FSN Received

The Eagle received an initial M2PA DATA message with an invalid FSN (Forward Sequence Number). The expected FSN in M2PA for the first DATA message received after link alignment is 0 for M2PA RFC. Older versions of M2PA (before Draft 9) used an initial FSN of 1. This UIM indicates that the two ends of the link have mismatched configurations.

  • Eagle versions prior to 34.3 support M2PA Draft 6 but do not support M2PA RFC.

  • If both ends of the M2PA association are on Eagle release 34.3 or later, verify that both ends have the VER parameter set to match on the M2PA association (VER=D6 or VER=M2PA must be the same on both ends).

  • If one end of the M2PA association is on an Eagle release prior to 34.3 and the other is 34.3 or greater, verify that the association VER parameter in the later release is set to D6 for backward compatibility.

Example 
RLGHNCXA21W 00-04-18 19:09:14 EST EAGLE 34.3.0
5781.1332 CARD 1301,A INFO Invalid Initial M2PA FSN Received
Legend
FSN
Forward Sequence Number
M2PA
SS7 MTP2 - User Peer-to-Peer Adaptation Layer

Alarm Level: No alarm condition. The message is informational only. However, the link will not stay aligned and a link alarm will be present.

Recovery

  1. To change the M2PA version used by the signaling link at the Eagle perform the following commands:
    1. Use the dact-slk:loc=xxxx:link=yy command to deactivate the signaling link.
    2. Use the chg-assoc:open=no command to close the M2PA association used by the signaling link.
    3. Use the chg-assoc:ver=<d6/rfc> command to change the M2PA version on the association used by the signaling link to match the configured M2PA version of the M2PA peer.
    4. Use the chg-assoc:open=yes command to activate the M2PA association used by the signaling link.
    5. Activate the signaling using the act-slk:loc=xxxx:link=yy command.
  2. Otherwise change the M2PA version at the M2PA peer to match the version configured for the signaling link/association at the Eagle.
  3. If the fault is not cleared, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.314 1333 - UA RCVD MSG DISCARDED

When processing a received PDU at the UA L2 layer, various errors can be detected which cause the MSU to be pegged and discarded. The SG responds to a number of these MSU’s with error messages and transmits them to the customer. Some scenarios exist where a received PDU causes an error to be pegged, the message to be discarded, and the SG to not respond with an error message. A new UIM is issued when a PDU excluding UA ERROR messages is received at the UA L2 layer and results in the SG discarding the message plus pegging an error count. The generation of this UIM is paced (every 30 seconds), and in situations where multiple messages are discarded within a 30 second window of time, a UIM is only generated for the first message discarded.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 38.0.0 
0003.1333    CARD 1305,A   INFO    UA RCVD MSG DISCARDED
             IP CONNECTION NAME=LONGCONNECTNAME ADPTR=M3UA
             REASON=Large MSU for IP Sig Not Supported
             SIO=0D OPC=1-1-1          DPC=2-2-2
             Report Date:yy-mm-dd  Time:hh:mm:ss

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. The following table summarizes why the UIM was issued.
    The reason text in the UIM identifies why the UIM was displayed. Look at the reason and take action based on that field. Most of the time, to correct the issue, the customer needs to stop issuing the message. The UIM’s diagnostic field usually indicates which message was received.

    Table 3-13 SG Received Messages Discarded

    Reason Message Discarded and Pegged UIM Reason Text UIM Diagnostic Text

    PDU received with invalid version

    		Invalid Version (Error Code=0x01)

    <msg rcvd> Rcvd; Version=<version value rcvd>

    Ex. ASP-Inactive Rcvd; Version=0x02

    1. PDU has unsupported class

    2. PDU received was SUA CLDT/CLDR on an M3UA Association

    		Unsupported Message Class (Error Code=0x03) Class=<Message Class Value>; Type=<Message Type Value> Ex: Class=0x09; Type=0x01
    PDU has unsupported type Unsupported Message Type (Error Code=0x04)

    Type=<Msg Type Value >; Class=<Message Class Value >

    Ex: Type=0x15; Class=0x02

    ASP-ACTIVE contains an unsupported traffic mode Type. Unsupported Traffic Mode (Error Code=0x05)

    <MSG> Rcvd; Mode=<traffic mode received >

    Ex : ASP-Active Rcvd; Mode=0x03

    1. PDU received was DAVA/DUNA/DRST/DUPU in the ASP-Inactive/ASP-Active States(end nodes should not generate these)

    2. ASP-UP received while in ASP-ACTIVE state

    3. ASP-ACTIVE received while in ASP-DOWN state

    		Unexpected Message (Error Code=0x06)

    1. DUNA Msg Rcvd

    2. DAVA Msg Rcvd

    3. DRST Msg Rcvd

    4. DUPU Msg Rcvd

    5. ASP-UP Rcvd while in ASP-Act State

    6. ASP-Act Rcvd while in ASP-Down State

    1. PDU could not be decoded or invalid length.

    2. ASP-UP-ACK/ASP-DOWN-ACK/

    ASP-ACTIVE-ACK/ASP-INACTIVE-ACK received in the ASP-Inactive/ASP-Active States while in server mode (not client)

    3. ASP-INACTIVE-ACK received while in client mode and in ASP-ACTIVE state

    4. DATA contains multiple routing contexts

    		Protocol Error (Error Code=0x07)

    1. <Message> Decode Failed

    2. <Message> Encode Failed

    3. <Message> Length Invalid

    4. ASP-UP-Ack Rcvd

    5. ASP-Down-Ack Rcvd

    6. ASP-Active-Ack Rcvd

    7. ASP-Inactive-Ack Rcvd

    8. M3UA to MTP3 Conversion Failed

    ASP-UP received on a connection this is Deactivated or Blocked. Refused Managment Blocking (Error Code=0x0d) ASP-Active Rcvd when SLK OOS-MT-DSBLD
    Sent if a UA Message is received with an invalid parameter value. Invalid Parameter Value (Error Code=0x11)

    <msg rcvd> Rcvd; Value=<parameter value rcvd >

    Ex. ASP-Inactive Rcvd; Value=0x00000009

    PDU has fixed length parameters of incorrect size Parameter Field Error (Error Code=0x12)

    <msg rcvd> Rcvd; Length=<invalid parameter length >

    Ex. ASP-Inactive Rcvd; Length=0x0200

    Sent if a UA message received contains an invalid parameter. Unexpected Parameter (Error Code=0x13)

    <msg rcvd> Rcvd; Parm Tag=<parameter tag rcvd >

    Ex. DATA Rcvd; Parm Tag=0x0500

    Invalid Network Appearance value received in a M3UA message Invalid Network Appearance (Error Code=0x15)

    <Msg Type> Rcvd; NA=<NA value rcvd >

    Ex: DAUD Rcvd; NA=0x00000011

    1. PDU is missing one or more mandatory parameters

    2. DATA contains no routing context and the association the PDU was received on is configured with more than 1 routing context

    		Missing Parameter (Error Code=0x16)

    1. <Msg Type> Rcvd; Missing Tag=<tag value >

    2. Hdr Len Invalid

    1. ASP-ACTIVE received with routing context but no routing key(s) are provisioned for linkset

    2. PDU contains one or more routing contexts that could not be matched to one associated with the connection the PDU was received on

    		Invalid Routing Context (Error Code=0x19)

    For this error code, use existing UIM “Mismatched UA Routing Context” only if the message is still processed. If the message is discarded, issue UIM format 62.

    <msg rcvd> Rcvd; RC=<routing context value>

    Ex: DAUD Rcvd; RC=0x00000008

    DATA received while in the ASP-Inactive State (server mode) Invalid ASP State DATA Rcvd while in ASP-Inact State
    A message was discarded and there is no error code. No ERR Received Reason Unknown
  2. Otherwise change the M2PA version at the M2PA peer to match the version configured for the signaling link/association at the Eagle.
  3. If the fault is not cleared contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.315 1334 - UA TX MSG Discarded

The generation of this UIM is paced (every 30 seconds), and in situations where multiple messages are discarded within a 30-second window of time, a UIM is only generated for the first transmitted message that is discarded.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 37.0.0
    0003.1334    CARD 1305,A   INFO    UA TX MSG DISCARDED
                 IP CONNECTION NAME=LONGCONNECTNAME ADPTR=M3UA
                 REASON=M3UA Conversion Error
                 SIO=0D OPC=1-1-1          DPC=2-2-2
                 Report Date:yy-mm-dd  Time:hh:mm:ss

Alarm Level: No alarm condition. The message is informational only.

Recovery

Correct the problem based on the reason text displayed.

The reasons listed in this UIM cause a discard in the transmit path.

Table 3-14 SG Messages Discarded in the Transmit Path

UIM Reason Text UIM Specific Text
M3UA Conversion Error MTP3 to M3UA Conversion Failed

3.3.316 1335 - Table Information

An update to the SCCP contained an invalid table identifier.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0003.1335 CARD 1105 INFO Table Information
Table 4294967296 Invalid Table ID
Report Date:02-07-21 Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.317 1336 - UA Error Msg Received

This UIM is issued for message discards in the transmit path. The generation of this UIM is paced (every 30 seconds), and in situations where multiple messages are discarded within a 30-second window of time, a UIM is only generated for the first transmitted message that was discarded.

This UIM is being displayed because the customer is sending an error message to the SG. The following is a list of all the possible error codes that can appear in the UIM for received UA ERROR messages. Each one has the error code appended in parenthesis.

  • Invalid Version (0x01)

  • Unsupported Message Class (0x03)

  • Unsupported Message Type (0x04)

  • Unsupported Traffic Mode (0x05)

  • Unexpected Message (0x06)

  • Protocol Error (0x07)

  • Invalid Stream Identifier (0x09)

  • Refused Management Blocking (0x0d)

  • ASP Identifier Required (0x0e)

  • Invalid ASP Identifier (0x0f)

  • Invalid Parameter Value (0x11)

  • Parameter Field Error (0x12)

  • Unexpected Parameter (0x13)

  • Destination Status Unknown (0x14)

  • Invalid Network Appearance (0x15)

  • Missing Parameter (0x16)

  • Invalid Routing Context (0x19)

  • No Configured AS for ASP (0x1a)

  • Subsystem Status Unknown (0x1b)

  • Invalid Loadsharing Label (0x1c)

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 38.0.0
0003.1336    CARD 1305,A   INFO   UA ERROR MSG RECEIVED
             IP CONNECTION NAME=association1 ADPTR=M3UA
             ERROR CODE=Missing Parameter (0x16)
             Report Date:02-07-21 Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact far end node and investigate reason for error.

3.3.318 1337 - UA HEARTBEAT TIMEOUT

If T(beat ack) expires before a Heartbeat Ack message is received from the customer, the association is torn down. A new UIM is issued when the association is torn down and the existing format I53 is used for this UIM. The generation of this UIM is paced (every 30 seconds).

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST EAGLE 35.0.0
0003.1337 CARD 1305,A INFO UA HEARTBEAT TIMEOUT
ANAME = LONGASSOCNAME1 M3UA
Legend
ANAME
Long Association Name

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Reestablish the connection.

    If this UIM was displayed on the screen, then the connection was torn down.

  2. If this scenario keeps repeating after reestablishing a connection, then there is a problem with the connection and that will need to be investigated.

3.3.319 1338 - SCCP did not route - no PC in CgPA

GTT on CgPA PC is required, but CgPA PC is not present in the MSU.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1338    CARD 1103,A     INFO    SCCP did not route - no PC in CgPA
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1338    CARD 1103,A     INFO    SCCP did not route - no PC in CgPA
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Originating point code
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Check translations on the originating switch to determine the trouble.

3.3.320 1340 - REPT COND: TRBL Resynch Required

Under conditions of prolonged, high alarm activity the alarm processing capacity of the EAGLE 5 ISS can be reached. In an effort to keep the internal state machine current, alarms normally generated to the UI are discarded.

Under this scenario, when alarm processing recovers sufficiently, this message is generated to indicate to the attached network or element management systems that they should resynchronize with the EAGLE 5 ISS.

The generation of this message is expected to be limited to large configurations during severe outages, and the expected occurrence rate of this message is low; however, it has been added as a precaution. Although alarms may have been discarded, the internal alarm state of the EAGLE 5 ISS has been maintained and is stable.

Example 
tekelecstp 99-03-09 12:01:43 EST EAGLE 35.0.0
5061.1340 SYSTEM INFO REPT COND: TRBL resynch required

Alarm Level: No alarm condition. The message is informational only.

Recovery

The attached network or element management systems (such as Harris NetBoss) should use this message as an indication that they should perform the following command to synchronize alarm status with the EAGLE 5 ISS:

rept-stat-trbl

Note:

Network or element management systems attached through terminals configured as EMSALM type terminals must not filter this message. See the chg-trm command in the Commands Manual for further details.

  1. Use the following command to check whether GTT selectors in the arrived MSU are provisioned in SCCPOPTS table:

    rtrv=sccpopts

  2. If the SCCPOPTS table does not have an entry with the GTT selectors in the arrived MSU, use the following command to add a record with the GTT selectors in the arrived MSU to the SCCPOPTS table:

    ent-sccpopts

3.3.321 1341 - SRI rcvd - GSM2IS41 not provisioned

The system received an SRI Query message for which it attempted to generate a response. However, IS41 GSM Migration(IGM) feature found the GSM to IS-41 Migration prefix (specified by the GSM2IS41 parameter) is not provisioned on this system. With this UIM, IGM is notifying the operator it cannot process the SRI messages and is allowing it to fall through to the GTT for handling.

To be able to perform the IS-41GSM Migration feature and to accept SRI Request messages, you must first specify the GSM2IS41 prefix in GSMOPTS.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1341    CARD 1103,A     INFO    SRI rcvd - GSM2IS41not provisioned
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1341    CARD 1103,A     INFO    SRI rcvd - GSM2IS41not provisioned
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADD
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the rtrv-gsmopts command to display the GSM2IS41 setting in the GSM System Options.

    Example of the output: 

    rlghncxa03w 03-05-20 09:04:14 EST  EAGLE 30.1.0
GSM OPTIONS
-----------------------
DEFMCC      = NONE
DEFMNC      = NONE
SRFADDR     = 123456789abcdef
MSRNDIG     = RN
DEFMAPVR    = 1
SRIDN       = TCAP
GSM2IS41 = 0123456789abcde
rlghncxa03w 03-03-20 09:04:14 EST  EAGLE 30.1.0
SRFADDR=123456789abcdef    SRFNAI=7    SRFNP=15
MSRNDIG=CCRNDN
MSRNNAI=7    MSRNNP=15 DEFMAPVR=2

    If the GSM2IS41 parameter is not specified, proceed to 2. However, if it is set with a valid value, proceed to 3.

  2. Use the chg-gsmopts command to specify the GSM to IS-41 migration prefix.

    Refer to the Commands Manual for details. Then re-issue the command that caused this UIM.

  3. If the problem persists with the GSM2IS41 parameter specified, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.322 1342 - ANSI IS-41 INP Qry rejected: AINPQ is OFF

The EAGLE 5 ISS has rejected an INP query that is decoded as an ANSI-41NPREQ query because the appropriate AINPQ (ANSI-41 INP Query) feature key is not on.

Example 
RLGHNCXA21W 03-04-18 19:02:05 EST EAGLE 35.0.0
0112.1342 CARD 1103,A1 INFO ANSI IS-41 INP Qry rejected: AINPQ is OFF
SIO=83 OPC= 001-101-001 DPC= 001-001-001
CDPA: AI=cb SSN=016 TT=012
ADDR=919380
CGPA: AI=c3 PC= 001-101-001 SSN=016
DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
2e cf 01 00 d0 02 83 01 f2 25 aa 0b
84 09 01 00 11 0a 19 49
LSN=e1m1s1
Legend
ADDR
Address
AI
Address Indicator
CDPA LENGTH
Called party address length
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If you want to support the AINPQ feature, issue the chg-ctrl-feat:ainpq=on command to process ANSI-41 INP queries.
  2. If you do not want to support the AINPQ feature, ignore this informational message.
  3. For additional information or assistance about the AINPQ or any feature to purchase, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.323 1343 - INAP INP Qry rejected: INPQ is OFF

The EAGLE 5 ISS has rejected an INP query that is decoded as an INAP NPREQ query because the appropriate INPQ (ITU INP Query) feature key is not on.

Example 
RLGHNCXA21W 03-04-18 19:02:05 EST EAGLE 35.0.0
0112.1343 CARD 1103,A1 INFO INAP INP Qry rejected: INPQ is OFF
SIO=83 OPC= 001-101-001 DPC= 001-001-001
CDPA: AI=cb SSN=016 TT=012
ADDR=919380
CGPA: AI=c3 PC= 001-101-001 SSN=016
DATA=3a e2 38 c7 04 56 04 72 e0 e8 30 e9
2e cf 01 00 d0 02 83 01 f2 25 aa 0b
84 09 01 00 11 0a 19 49
LSN=e1m1s1
Legend
ADDR
Address
AI
Address Indicator
CDPA LENGTH
Called party address length
CGPA
Calling party address
DATA
Hex dump of TCAP part of MSU
DPC
Destination point code
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
OPC
Origination point code
PC
Point code
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. If you want to support the INPQ feature, issue the chg-ctrl-feat:ainpq=on command to process ITU INP queries.
  2. If you do not want to support the INPQ feature, ignore this informational message.
  3. For additional information or assistance about the INPQ or any feature to purchase, contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA.

3.3.324 1344 - MSU discarded: In-Service Thresholding

The EAGLE 5 ISS discarded an SCCP message because the MRN or MAP Group selected by GTT does not have enough available weight to satisfy the In-Service threshold.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1344    CARD 1103,A     INFO    MSU discarded: In-Service Thresholding
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 37.5.0
0018.1344    CARD 1103,A     INFO    MSU discarded: In-Service Thresholding
             TRANSLATED PC=003-003-003       TRANSLATED SS=005
                GTT on CdPA used MOSMSGTA=9193802053
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                    PC=001-001-001     SSN=004 
             LSN=ABCD123  GTTSET=3 (8)
             Report Date:02-07-21  Time:16:20:19
Legend
ADD
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indictor
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Use rtrv-mrn and rtrv-map to determine the MRN and MAP Group information for that PC/PC+SSN combination.
  2. Validate that the In-Service Threshold (THR) parameter is set correctly for each Group.

    If not, use the chg-mrn or chg-map command to change the THR parameter to the correct value.

  3. If THR is correct, validate that the weight parameter is set correctly for each member of the group.

    If not, use the chg-mrn or chg-map command to alter the weights to the correct values.

  4. Use rept-stat-dstn to determine which PC/PC+SSNs are not available.

    Perform corrective maintenance to get the unavailable PC/PC+SSNs back into service. Potential causes for unavailability are link deactivation, prohibited routes, network congestion or subsystem outages.

3.3.325 1345 - CRD Auto-Clear Sent to All MTP Cards

EAGLE 5 ISS generates this UIM when Circular Route Auto-Recovery procedure clears the Circular Route Detection (CRD) status of a destination that was marked prohibited.

Example 
RLGHNCXA21W 03-04-18 19:02:05 EST  EAGLE 36.0.0
1234.1345    CARD 1203     INFO      CRD Auto-Clear Sent to All MTP Cards
DPC=001-001-001
Report Date:06-06-19  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.326 1346 - IS-41 Missing Mandatory Parameters

EAGLE 5 ISS has rejected the ANSI IS-41 INP Query message, because the TCAP portion of the message does not contain mandatory parameters (e.g. digits).

Example 
tklc1091301 07-01-19 03:47:19 EST EAGLE5 36.0.0-57.9.0
6962.1346 CARD 2113 INFO IS-41 Missing Mandatory Parameters
SIO=83 OPC= 0-000-0-aa DPC= 5-090-5-aa
CDPA: AI=d3 SSN=250 TT=025
ADDR=197055512340
CGPA: AI=c3 PC= 1-137-4-aa SSN=250
DATA=15 e2 13 c7 04 00 00 00 00 e8 0b e9
09 cf 01 00 d1 02 09 3e f2
LSN=ls1102n0
Report Date:07-01-19 Time:03:47:19
Legend
ADD
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
PC
Point code
PCI
Point code indicator
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type
TRANSLATED PC
Translated point code
TRANSLATED SS
Translated subsystem

Note:

If Global Title Translation is found, the GTTSET in which the translation is found appears. If Global Title Translation is not found, the GTTSET does not display.

Alarm Level: No Alarm condition. Message is for information only.

Recovery

Ensure ANSI IS-41 INP Query message contains mandatory TCAP parameters for valid query processing.

3.3.327 1347 - IS-41 Digits - Bad Encoding Scheme

EAGLE 5 ISS has rejected the ANSI IS 41 INP Query message, because the encoding scheme of the DIGITS parameter of the ANSI IS-41 TCAP portion is invalid.

Example 
tklc1091301 07-01-19 03:31:57 EST EAGLE5 36.0.0-57.9.0
6925.1347 CARD 2113 INFO IS-41 Digits - Bad Encoding Scheme
SIO=83 OPC= 0-000-0-aa DPC= 5-090-5-aa
CDPA: AI=d3 SSN=250 TT=025
ADDR=197055512340
CGPA: AI=c3 PC= 1-137-4-aa SSN=250
DATA=23 e2 21 c7 04 00 00 00 00 e8 19 e9
17 cf 01 00 d1 02 09 3e f2 0e 84 0c
01 01 12 0f 76 18 79 70
LSN=ls1102n0
Report Date:07-01-19 Time:03:31:57

Alarm Level: No Alarm condition. Message is for information only.

Recovery

Ensure ANSI IS 41 INP Query message contains only digits with BCD encoding scheme.

3.3.328 1348 - IS-41 Number of dgts Exceeds the Maximum

EAGLE 5 ISS has rejected the ANSI IS 41 INP Query message; because the number of digits in the DIGITS parameter exceeds 21 digits.

Example 
tklc1091301 07-01-19 03:34:40 EST EAGLE5 36.0.0-57.9.0
6936.1348 CARD 2317 INFO IS-41 Num of dgts exceeds the maximum
SIO=83 OPC= 0-000-0-aa DPC= 5-090-5-aa
CDPA: AI=d3 SSN=250 TT=025
ADDR=197055512340
CGPA: AI=c3 PC= 1-137-4-aa SSN=250
DATA=27 e2 25 c7 04 00 00 00 00 e8 1d e9
1b cf 01 00 d1 02 09 3e f2 12 84 10
01 01 11 18 76 18 79 70
LSN=ls1102n0
Report Date:07-01-19 Time:03:34:40

Alarm Level: No Alarm condition. Message is for information only.

Recovery

Ensure ANSI IS 41 INP Query message’s DIGITS parameter contains less than 21 digits.

3.3.329 1349 - MSU invalid size – discarded

An MSU less than 5 bytes or greater than 279 bytes was detected by the MTP layer 3 software in an ATM card. A four byte MSU may cause the ATM connection to bounce (four byte PDUs are used for SSCF control). MSU length limit is 279 bytes.

Example 
2864.1349    CARD 6112,A  INFO    MSU invalid size - discarded
            LEN=114
            SIO=93  OPC=  227-040-000    DPC=  209-122-150
            DATA=09 81 03 0c 15 09 89 06 0a 21 80 95
                 97 10 89 09 89 95 0a 21 80 95 89 30
                 03 44 62 42
            LSN=n209068063
            Report Date:13-11-09  Time:09:48:33

Note:

The length of the MSU (for example, LEN=114) includes the length of the SIF plus some other parameters. The length of these other parameters varies depending on the protocol managed by the LIM card issuing the UIM.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.330 1350 - Discrd Rcvd Lrg MSU CTRL-FEAT Off

IPL receives on a M2PA connection a large MSU greater than 272 bytes and the feature is not enabled.

Example 
    0047.1350    CARD 1113     INFO    Discrd Rcvd Large MSU CTRL-FEAT Off
                 LEN=50
                 SIO=04   OPC=   016-032-048    DPC=   032-032-048  
                 DATA=01 02 03 04 05 06 07 08 09 0a 0b 0c 
                      0d 0e 0f 10 11 12 13 14 15 16 17 18 
                      19 1a 1b 1c 
                 LSN=ls211
                 Report Date:12-12-15  Time:11:01:50
;

Note:

The length of the MSU (for example, LEN=50) includes the length of the SIF plus some other parameters. The length of these other parameters varies depending on the protocol managed by the LIM card issuing the UIM.

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the following command to retrieve information about controlled features:
    rtrv-ctrl-feat
    The output of the rtrv-ctrl-feat command displays information about the enabled features.
  2. The alarm will be cleared when the feature is enabled using the enable-ctrl-feat command.

3.3.331 1351 - Discrd Trans Lrg MSU Unsupported SLK

An MSU less than 5 bytes or greater than 279 bytes was detected by the MTP layer 3 software in an ATM card. A four-byte MSU may cause the ATM connection to bounce (four byte PDUs are used for SSCF control). The MSU length limit is 279 bytes. IN this case, an SSEDCM-IPLIM SAAL/TALI signaling link receives from IMT a large MSU greater than 272 bytes. The discard occurs on the outbound card.

Example 
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 37.0.0
0003.1351    CARD 1105,B   INFO     Discrd Trans Lrg MSU Unsupported SLK
             LEN=475
             SIO=0D   OPC=001-001-001    DPC=002-002-002
             LSN=ABCD123
             Report Date:yy-mm-dd  Time:hh:mm:ss

Note:

The length of the MSU (for example, LEN=50) includes the length of the SIF plus some other parameters. The length of these other parameters varies depending on the protocol managed by the LIM card issuing the UIM.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.332 1352 - Discrd Rcvd Lrg MSU Unsptd Outbnd SLK

An IP7 GPL receives a large MSU greater than 272 bytes, the BICC controlled feature is on, there are available routes for the destination point code, but selected outbound card does not support large MSUs.

Example 
    0049.1352    CARD 1113     INFO    Discrd Rcvd Lrg MSU Unsprtd Outbnd SLK
                 LEN=50
                 SIO=04   OPC=   016-032-048    DPC=   032-032-048  
                 DATA=01 02 03 04 05 06 07 08 09 0a 0b 0c 
                      0d 0e 0f 10 11 12 13 14 15 16 17 18 
                      19 1a 1b 1c 
                 LSN=ls211
                 Report Date:12-12-15  Time:11:02:11
;

Note:

The length of the MSU (for example, LEN=50) includes the length of the SIF plus some other parameters. The length of these other parameters varies depending on the protocol managed by the LIM card issuing the UIM.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.333 1353 - DTA Bypassed for Rcvd Lrg MSU

An IP7 GPL receives a large MSU that triggers DTA processing instead of converting the MSU (the MSU is routed normally, DTA is bypassed).

Example 
    0050.1353    CARD 1113     INFO    DTA Bypassed for Rcvd Large MSU
                 LEN=50
                 SIO=04   OPC=   016-032-048    DPC=   032-032-048  
                 DATA=01 02 03 04 05 06 07 08 09 0a 0b 0c 
                      0d 0e 0f 10 11 12 13 14 15 16 17 18 
                      19 1a 1b 1c 
                 LSN=ls211
                 Report Date:12-12-15  Time:11:02:21
;

Note:

The length of the MSU (for example, LEN=50) includes the length of the SIF plus some other parameters. The length of these other parameters varies depending on the protocol managed by the LIM card issuing the UIM.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.334 1355 - Card Integ Chk: MSU cksum err

An MSU was discarded because a card received an MSU which failed checksum validation.

Example 
RLGHNCXA21W 06-09-07 16:20:19 GMT  EAGLE5 35.6.0
0008.1355    CARD 1301 INFO          Card Integ Chk:MSU cksum err
             SIO=03   OPC=001-001-001    DPC=002-002-002
             DATA=12 34 56 78 90 12 34 56 78 90 12 34
                  56 78 90 12 34 56 78 90 12 34 56 78                     
             Source Loc: 1303        Destination loc: 1301                                                       
             Report Date:  09-07-06  Time:16:20:19

Note:

On a LIM card the destination SS7 port is shown after the card address (it is not printed when this UIM is issued on a SCCP card). 
CARD 1301,a
Legend
DATA
Hex dump of USER PART data
DESTINATION LOC
Card receiving the MSU
DPC
Destination point code
OPC
Originating point code
SIO
Service information octet
SOURCE LOC
Card originating the MSU

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.335 1356 - EXT BERT terminated with OAM switchover

This message is issued when the Extended BERT is aborted due to OAM switchover.

Example 

RLGHNCXA21W 09-09-07 16:20:19 EST EAGLE 42.0.0
    0023.1356    CARD 1115     INFO     EXT BERT terminated with OAM switchover
                 Report Date:09-09-07  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.336 1357 - Negotiation at 100Mbps/Full Duplex failed

The negotiation for data rate and traffic flow did not result in 100 Mbps and full duplex mode respectively, for all data links.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 37.0.0
0010.1357    CARD 1103     INFO    Negotiation at 100Mbps/Full Duplex failed
             DLK configuration: SPEED = 100 Mbps, DUPLEX = HALF
             Report Date:00-02-07  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Use a valid combination of speed and duplex parameters on the card and Ethernet switch for configuring a data link. An invalid combination may cause link degradation and unreliable behavior.

3.3.337 1358 - MSU discarded - too big after MTP conv.

  • When ITUI or ITUN MSU, routed to ANSI or ITUN24 network, with SI less than or equal to 5 is received on any card type where the original MSU is of sufficient size that when the 14-bit point codes are converted to 24-bit point codes the resulting converted MSU will have SIF greater than 272 bytes.

  • When ITUI or ITUN MSU, routed to ANSI or ITUN24 network, with SI ranging from 6 to 15 is received on any non-IP card type where the original MSU is of sufficient size that when the 14-bit point codes are converted to 24-bit point codes the resulting converted MSU will have SIF greater than 272 bytes. The MSU will be discarded even if the outbound linkset is on IP card type and Large MSU Support is enabled (Large MSU for IP Sig, Feature P/N 893018401) because conversion is performed on the inbound card, so both the inbound and outbound cards must be able to support MSU greater than 272 bytes.

  • When ITUI or ITUN MSU, routed to ANSI or ITUN24 network, with SI ranging from 6 to 15 is received on any IP card type where the original MSU is of sufficient size that when the 14-bit point codes are converted to 24-bit point codes the resulting converted MSU will have SIF greater than 4095 bytes.

Example 
    0055.1358    CARD 1113     INFO    MSU discarded - too big after MTP conv.
                 LEN=50
                 SIO=04   OPC=   016-032-048    DPC=   032-032-048  
                 DATA=01 02 03 04 05 06 07 08 09 0a 0b 0c 
                      0d 0e 0f 10 11 12 13 14 15 16 17 18 
                      19 1a 1b 1c 
                 LSN=ls211
                 Report Date:12-12-15  Time:11:03:11
;

Note:

The length of the MSU (for example, LEN=50) includes the length of the SIF plus some other parameters. The length of these other parameters varies depending on the protocol managed by the LIM card issuing the UIM.

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action required.

3.3.338 1359 - SCCP Looping Detected

When a SCCP Looping condition is found, the mode of operation of the loopset will be notify or discard (based on provisioning). The mode of operation either only notifies the user (via this UIM), or notifies the user (via this UIM) and discards the MSU. The data shown in the output will be from the original MSU, before any GTT modifications were applied to it.

A hop counter violation message is also sent by EAGLE to the UDTS. The message indicates either ANSI or ITU Networks based on the provisioned GTT Translation point code type.

Example

nbsa01 12-01-23 19:41:10 BRA  EAGLE5 41.1.1-62.67.1 
    0527.1359    CARD 3217    INFO    SCCP Looping Detected 
                SIO=83  OPC=  000-004-666      DPC=  000-006-500        
                SCCP MSG TYPE=09 
                CDPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=0 
                        TT=000  NP=01  NAI=004  ADDR=554197388383 
                        PC=--------------    SSN=008 
                CGPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=0 
                        TT=000  NP=01  NAI=004  ADDR=551181134001 
                        PC=--------------    SSN=008 
                LSN=ylrjo1  GTTSETIDX=(0)                                        
                Report Date:12-01-23  Time:19:41:00

Alarm Level: No alarm condition. The message is informational only.

Recovery

Analysis of measurements and messages is required to ensure messages are correctly being discarded.

Note:

Entering the wrong data in the SCCP Loop Table and/or incorrectly connecting a GTT translation with a particular SCCP Loop Table entry could result in unwanted traffic loss.

Refer to the Commands Manual for more information using ENT/CHG/DEL/RTRV-LOOPSET commands.

  1. Remove invalid or unwanted entries from the SCCP Loop Tables.
  2. Create a valid SCCP Loop Table entry for a GTT translation if the available tables are valid for other translations, but not the one in error.
  3. Set the "notify only" mode until confidence is gained in the EAGLE SCCP Loop Tables, this is also the recommended setting for initial provisioning with a subsequent change.
  4. Periodic auditing of UIMs to ensure that valid messages are not being discarded.

3.3.339 1360 - Inv SR-5129 msg rcvd, Bad Src.

An SR-5129 message was received with a bad source name in the message header.

Example
    station1234 06-12-21 16:28:08 EST Rel 37.5.0-58.12.0
    0020.1360    SYSTEM        INFO     Inv SR-5129 msg rcvd, Bad Src.
                 Terminal = 17
                 Name = SNAMNJCCSM1YSA701 
                 Report Date:06-12-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.340 1361 - Inv SR-5129 msg rcvd, Bad Dst.

An SR-5129 message was received with a bad destination name in the message header.

Example
    station1234 06-12-21 16:28:08 EST Rel 37.5.0-58.12.0
    0020.1361    SYSTEM        INFO     Inv SR-5129 msg rcvd, Bad Dst.
                 Terminal = 17
                 Name = SNAMNJCCSM1YSA701 
                 Report Date:06-12-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.341 1362 - Inv SR-5129 msg rcvd, Bad Ver.

An SR-5129 message was received with a bad version in the message header.

Example
    station1234 06-12-21 16:28:08 EST Rel 37.5.0-58.12.0
    0020.1362    SYSTEM         INFO    Inv SR-5129 msg rcvd, Bad Ver.   
                 Terminal = 17
                 Ver = xxxx 
                 Report Date:06-12-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.342 1363 - SR-5129 Err Msg rcvd Err Code 1(Bad Src)

An SR-5129 Error Message received with Error Code as 1 (Bad Source).

Example
    station1234 06-12-21 16:28:08 EST Rel 37.5.0-58.12.0
    0020.1363    SYSTEM         INFO    Inv SR-5129 Err Msg rcvd Err Code 1(Bad Src)
                 Terminal = 17
                 
                 Report Date:06-12-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.343 1364 - SR-5129 Err Msg rcvd Err Code 2(Bad Dst)

An SR-5129 Error Message received with Error Code as 2 (Bad Destination).

Example
    station1234 06-12-21 16:28:08 EST Rel 37.5.0-58.12.0
    0020.1364    SYSTEM         INFO    Inv SR-5129 Err Msg rcvd Err Code 2(Bad Dst)
                 Terminal = 17
                 
                 Report Date:06-12-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.344 1365 - SR-5129 Err Msg rcvd Err Code 3(Bad Ver)

An SR-5129 Error Message received with Error Code as 3 (Bad Version).

Example
    station1234 06-12-21 16:28:08 EST Rel 37.5.0-58.12.0
    0020.1365    SYSTEM         INFO    Inv SR-5129 Err Msg rcvd Err Code 3(Bad Ver)
                 Terminal = 17
                 
                 Report Date:06-12-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.345 1366 - SR-5129 Err Msg rcvd Err Code Other

An SR-5129 Error Message received with Error Code other than 1, 2 and 3.

Example
    station1234 06-12-21 16:28:08 EST Rel 37.5.0-58.12.0
    0020.1366    SYSTEM         INFO    Inv SR-5129 Err Msg rcvd Err Code Other   
                 Terminal = 17
                 
                 Report Date:06-12-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.346 1367 - SOIP connection failed.

Failed to start SOIP connection.

Example
    station1234 06-12-21 16:28:08 EST Rel 37.5.0-58.12.0
    0009.1367    SYSTEM        INFO     SOIP connection failed.
                 Terminal=17
                 IPADDR=192.168.57.52 
                 PORT = 2336
                 Report Date:06-12-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.347 1368 - Inv SR-5129 msg rcvd, Other

An SR-5129 Message Received with error other than Bad Source Name, Bad Destination Name and Bad Version in the Message Header.

Example
    station1234 06-12-21 16:28:08 EST Rel 37.5.0-58.12.0
    0020.1368    SYSTEM         INFO    Inv SR-5129 msg rcvd, Other   
                 Terminal = 17
                 
                 Report Date:06-12-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.348 1369 - ISUP IAM decode failed

An ISUP IAM decode failed with error other than Bad Source Name, Bad Destination Name, and Bad Version in the Message Header.

Example
         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0020.1369    CARD 1201,A INFO      ISUP IAM decode failed
                 SIO=3   OPC=&&-001-001-001 DPC=&&-002-002-002
                 DATA=26 80 03 09 0e 06 09 00fe 08 50 55 43
                      00
                 LSN=LS0032

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.349 1370 - ISUP IAM Cld Pty decode failed

An ISUP IAM Cld Pty decode failed with error other than Bad Source Name, Bad Destination Name and Bad Version in the Message Header.

Example
         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0020.1370    CARD 1201,A INFO      ISUP IAM Cld Pty decode failed
                 SIO=3   OPC=&&-001-001-001 DPC=&&-002-002-002
                 DATA=26 80 03 09 0e 06 09 00fe 08 50 55 43
                      00
                 LSN=LS0032

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.350 1371 - ISUP encode Failed

An ISUP encode failed with error other than Bad Source Name, Bad Destination Name and Bad Version in the Message Header.

Example
         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0020.1371    CARD 1201,A INFO      ISUP encode failed
                 SIO=3   OPC=&&-001-001-001 DPC=&&-002-002-002
                 DATA=26 80 03 09 0e 06 09 00fe 08 50 55 43
                      00
                 LSN=LS0032

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.351 1372 - SLTC Failure-SLTM not sent, Invalid SIO

The EAGLE attempted to send SLTM with SIO=2 for ITU APC.

Example
RLGHNCXA21W 00-02-07 12:01:43 EST  EAGLE 37.0.0
1230.1372    CARD 1201,A   INFO    SLTC Failure-SLTM not sent, Invalid SIO
             ADJ PC=001-001-001        SLC=02    LEN=0f
             DATA=01 02 03 04 05 06 07 08 09 10 11 12 13 14 15
             Report Date:00-02-07  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Change the sltset corresponding to the link/port to the one that has sio=1 (Regular SLTM message).

Note:

Special maintenance messages are not supported for ITU PCs.

3.3.352 1373 - TFC Generated for Congested Link

Implementation of auto decrementing of congestion abatement is multicast to all MTP cards (SRC and DEST).

In both ANSI and ITU networks, UIM 1373 indicates the level of congestion; for example, CONG STATUS=001 is a lower level of congestion than CONG STATUS=003 (the highest level of congestion).

For M3UA links, signaling congestion (SCON) network-management messages also report congestion:
  • In an ANSI network, the value in the SCON always matches the value in UIM 1373.
  • In a non-ANSI (ITU) network, SCON messages report only 0 (not congested) or 1 (congested), so the congestion value reported in UIM 1373 can differ from the value in the SCON. For example, if UIM 1373 reports CONG STATUS=002 or CONG STATUS=003, then the value in the related SCON will be 1 (not 2 or 3).
Example
    station1234 02-07-21 16:28:08 EST Rel 37.0.0 -46.12.0
    8441.1373    CARD 1101,A   INFO      TFC Generated for Congested Link
                 DPC=   001-115-000    CPC=   008-001-001
                 CONG SLK: 1305,A3     CONG STATUS=001
  Report Date:07-01-05  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Use local troubleshooting procedures to determine the cause for congestion.

3.3.353 1374 - SMS B-Party address decode failed

An error was detected during decode of SMS message destination address.

Example
    tekelecstp 02-03-20 07:40:50 EST  EAGLE 39.1.0-61.4.0
    6815.1374    CARD 1103     INFO    SMS B-Party Address decode failed    
                 SIO=83   OPC=   002-002-001    DPC=   009-008-007
                 CDPA: AI=8b  SSN=002  TT=006
                       ADDR=110000
                 CGPA: AI=43  PC=   002-002-001     SSN=002
                 DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                      3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                      01 00 9f 74 02 00 00 89
                 LSN=ls221
                 Report Date:02-03-20  Time:07:40:50

Alarm Level: No alarm condition. The message is informational only.

Recovery

The message should be analyzed to determine the error, and the originating node should be contacted to send corrected message.

When processing MSU for SMS MO, this UIM is generated when one of the following occurs:
  • Mandatory SM-RP-UI parameter is absent from the MO ForwardSM message.
  • The TPDU type is SMS-SUBMIT and the parameter length is less then 4 + number of digit bytes specified in the number of digit field.
  • The TPDU type is SMS-COMMAND and the parameter length is less then 7 + number of digit bytes specified in the number of digit field.
  • Number of digits is 0 or greater than 20.

3.3.354 1375 - SMS B-party Failed to modify TCAP MSU

The formatted outbound digit string length generated by SMS NP for encoding the TCAP message exceeded system limits.The formatted outbound digit string length generated by SMS NP or MO SMS B-Party Routing for encoding the TCAP message exceeded system limits.

Example
 tekelecstp 02-03-20 07:40:50 EST  EAGLE 39.1.0-61.4.0
 6815.1375    CARD 1103     INFO    SMS B-party Failed to modify TCAP MSU    
              SIO=83   OPC=   002-002-001    DPC=   009-008-007
              CDPA: AI=8b  SSN=002  TT=006
                    ADDR=110000
              CGPA: AI=43  PC=   002-002-001     SSN=002
              DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                   3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                   01 00 9f 74 02 00 00 89
              LSN=ls221
              Report Date:02-03-20  Time:07:40:50

Alarm Level: No alarm condition. The message is informational only.

Recovery

The message and outbound digits formatting options should be analyzed to determine the error and the originating node or the requested outbound digit formatting option should be modified to correct the encoding error.

This UIM is generated when processing MSU for SMS MO and TCAP message needed to be expanded to accommodate new digits and either
  • New SM-RP-UI parameter length exceeds 127 digits.
  • The length of new parameter sequence, Invoke component, component portion or TCAP package exceeds 127 bytes.
  • The SCCP user data length (TCAP payload size) exceeds 255 bytes.
  • The MSU length exceeds 279 bytes.

3.3.355 1376 - SMS Failed to modify B-Party digits

During processing of SMS message, the formatted outbound digit string length exceeded limit for number of digits.

This message is raised when:

  • During processing of SMS message, the formatted outbound digit string length exceeded limit for number of digits.

  • For MO SMS B-Party routing, AMGTT data provisioned in the GTT Table entry corresponding to MAP B-Party number is used to modify MAP B-Party digits. If outbound length exceeds 20 or becomes less than 0.

Example
    tekelecstp 02-03-20 07:40:50 EST  EAGLE 39.1.0-61.4.0
    6815.1376    CARD 1103     INFO    SMS Failed to modify B-Party digits    
                 SIO=83   OPC=   002-002-001    DPC=   009-008-007
                 CDPA: AI=8b  SSN=002  TT=006
                       ADDR=110000
                 CGPA: AI=43  PC=   002-002-001     SSN=002
                 DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                      3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                      01 00 9f 74 02 00 00 89
                 LSN=ls221
                 Report Date:02-03-20  Time:07:40:50

Alarm Level: No alarm condition. The message is informational only.

Recovery

The message and the digit format provisioning should be analyzed to determine the error and the originating node or the requested outbound digit formatting option should be modified to correct the encoding error. For MO SMS B-Party Routing, AMGTT data (NSDD/NPDD/NSDS/NPDS) provisioned in GTT entry corresponding to MAP B-Party number should be modified to correct the encoding error.

This UIM is generated when SMS NP or MO SMS B-Party Routing feature generated an outbound digit string for encode in TCAP message, which exceeded 20 digits in length or is less than 0 digits in length forcing SMS NP/MO SMS B-Party Routing to route original MSU.

3.3.356 1377 - SSH session disconnected - server busy

Indicates that an established SSH connection on the EAGLE has disconnected.

Example 
RLGHNCXA21W 02-08-08 20:52:04 EST  EAGLE 39.0
5024.1377    CARD 1105     INFO      SSH session disconnected - server busy
             RIPADDR=192.168.57.52
             RIPORT=2336
             LIPADDR=192.168.53.46
             LIPORT=23 
             Report Date:02-08-08  Time:20:52:04
Legend
LIPADDR
Local IP Address
LIPORT
Local TCP Port Number
RIPADDR
Remote IP Address
RIPORT
Remote TCP Port Number

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.357 1378 - Inh VFlex SS request already outstanding

A second attempt to inhibit the V-Flex subsystem has been made while the first is still being processed. The second attempt will be ignored.

Example
tekelecstp 07-03-09 12:01:43 EST EAGLE 37.6.0
5061.1378 SYSTEM INFO Inh VFlex SS request already outstanding

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.358 1379 - Failure Inhibiting VFlex SS

The attempted inhibit of the V-Flex subsystem failed. A response SOG was not received from the mate.

Example
tekelecstp 07-03-09 12:01:43 EST EAGLE 37.6.0
5061.1379 SYSTEM INFO Failure Inhibiting VFlex SS

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.359 1380 - VFLEX: No RN digits provisioned

The digits in the VMS at the requested VMRN index were not provisioned. The provisioning information for the VMS ID accessed via the MSU information should be verified.

Example
    RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 37.6.0
    0002.1380    SYSTEM        INFO      VFlex: RN is not provisioned
              SIO=03   OPC=001-001-001      DPC=002-002-002
                 SCCP MSG TYPE=04
                 CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=250  NP=04  NAI=010  ADDR=1234567890901
                        PC=003-003-003       SSN=005
                 CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=100  NP=07  NAI=012  ADDR=012345677890
                        PC=001-001-001       SSN=004
                 LSN=ABCD123  GTTSET=3 203 46
                 Report Date:07-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the VMS ID accessed via the MSU information.

3.3.360 1381 - VFlex: CD entry not found

The call decision table entry matching the incoming MSU criteria is not found. Call decision tree provisioning should be updated.

Example
    RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 37.6.0
    0002.1381    SYSTEM        INFO      VFlex: CD entry not found
              SIO=03   OPC=001-001-001      DPC=002-002-002
                 SCCP MSG TYPE=04
                 CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=250  NP=04  NAI=010  ADDR=1234567890901
                        PC=003-003-003       SSN=005
                 CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=100  NP=07  NAI=012  ADDR=012345677890
                        PC=001-001-001       SSN=004
                 LSN=ABCD123  GTTSET=3 203 46
                 Report Date:07-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Call decision tree provisioning should be updated.

3.3.361 1382 - Too many digits for DRA parameter

Too many digits in the DRA parameter to encode.

Example
    RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 37.6.0
    0002.1382    SYSTEM        INFO      Too many digits for DRA parameter
              SIO=03   OPC=001-001-001      DPC=002-002-002
                 SCCP MSG TYPE=04
                 CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=250  NP=04  NAI=010  ADDR=1234567890901
                        PC=003-003-003       SSN=005
                 CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=100  NP=07  NAI=012  ADDR=012345677890
                        PC=001-001-001       SSN=004
                 LSN=ABCD123  GTTSET=3 203 46
                 Report Date:07-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Decrease the number of RN digits or modify the querying node to send fewer digits in DN.

3.3.362 1383 - SLTC Failed: No route to APC on linkset

An SLTC message is sent/received for a linkset that is not in the route-set of its APC.

Example 
  1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    8606.1383    CARD 1105,B   INFO    SLTC Failed: No route to APC on linkset
                 ADJ PC=   002-14-00       SLC=000   LEN=002
                 DATA=11 77
                 Report Date:02-04-01  Time:17:40:42

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.363 1384 - G-Flex MLR: Op without IMSI erroneous

The G-Flex MLR Function encountered a message that did not contain an IMSI parameter.

Example 
station1234 06-12-21 16:28:08 EST Rel 38.0.0
0020.1384    CARD  1106    INFO     G-Flex MLR: Op without IMSI erroneous
0018.1384    CARD 1103,A     INFO    G-Flex MLR: Op without IMSI erroneous
             SIO=83   OPC=   002-002-001    DPC=   009-008-007
             CDPA: AI=8b  SSN=002  TT=006
                   ADDR=110000
             CGPA: AI=43  PC=   002-002-001     SSN=002
             DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                  3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                  01 00 9f 74 02 00 00
             LSN=ls221
             Report Date:10-10-10  Time:07:40:50
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code of the SCCP calling party or called party address
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact far end node and investigate reason for error.

3.3.364 1385 - G-Flex MLR: Op without IMSI skipped

The G-Flex MLR Function encountered a sendParameters operation that did not contain an IMSI parameter.

Example 
station1234 06-12-21 16:28:08 EST Rel 38.0.0
0020.1385    CARD  1106    INFO     G-Flex MLR: Op without IMSI skipped
0018.1385    CARD 1103,A     INFO    G-Flex MLR: Op without IMSI skipped
             SIO=83   OPC=   002-002-001    DPC=   009-008-007
             CDPA: AI=8b  SSN=002  TT=006
                   ADDR=110000
             CGPA: AI=43  PC=   002-002-001     SSN=002
             DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                  3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                  01 00 9f 74 02 00 00
             LSN=ls221
             Report Date:10-10-10  Time:07:40:50
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code of the SCCP calling party or called party address
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact far end node and investigate reason for error.

3.3.365 1386 - G-Flex MLR: Op with bad TCAP skipped

The G-Flex MLR Function encountered problems decoding the TCAP and MAP layers of a message prior to attempting to identify an IMSI parameter.

Example 
station1234 06-12-21 16:28:08 EST Rel 38.0.0
    0020.1386    CARD  1106    INFO     G-Flex MLR: Op with bad TCAP skipped    
0018.1386    CARD 1103,A     INFO    G-Flex MLR: Op with bad TCAP skipped
             SIO=83   OPC=   002-002-001    DPC=   009-008-007
             CDPA: AI=8b  SSN=002  TT=006
                   ADDR=110000
             CGPA: AI=43  PC=   002-002-001     SSN=002
             DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                  3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                  01 00 9f 74 02 00 00
             LSN=ls221
             Report Date:10-10-10  Time:07:40:50
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code of the SCCP calling party or called party address
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact far end node and investigate reason for error.

3.3.366 1387 - G-Flex MLR: Op with bad IMSI skipped

The G-Flex MLR Function encountered an IMSI parameter that contains fewer than 5 digits or more than 15 digits.

Example 
station1234 06-12-21 16:28:08 EST Rel 38.0.0
0020.1386    CARD  1106    INFO     G-Flex MLR: Op with bad IMSI skipped    
 
0018.1387    CARD 1103,A     INFO    G-Flex MLR: Op with bad IMSI skipped
            SIO=83   OPC=   002-002-001    DPC=   009-008-007
            CDPA: AI=8b  SSN=002  TT=006
                  ADDR=110000
            CGPA: AI=43  PC=   002-002-001     SSN=002
            DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                 3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                 01 00 9f 74 02 00 00
            LSN=ls221
            Report Date:10-10-10  Time:07:40:50
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code of the SCCP calling party or called party address
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact far end node and investigate reason for error.

3.3.367 1388 - Invalid prefix/suffix digit len for CdPA

This message indicates that the the length of the prefix/suffix of the CdPA is not valid.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 38.0.0
0018.1388    CARD 1103,A     INFO    Invalid prefix/suffix digit len for CdPA
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 38.0.0
0018.1388    CARD 1103,A     INFO    Invalid prefix/suffix digit len for CdPA
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact far end node and investigate reason for error.

3.3.368 1389 - Invalid prefix/suffix digit len for CgPA

This message indicates that the the length of the prefix/suffix of the CgPA is not valid.

Example

This output indicates an error against the original destination rather than the redirected destination. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 38.0.0
0018.1389    CARD 1103,A     INFO    Invalid prefix/suffix digit len for CgPA
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
This alternate output includes the redirected destination and is used when a redirected MSU encounters an error. 
RLGHNCXA21W 02-07-21 16:20:19 EST  EAGLE 38.0.0
0018.1389    CARD 1103,A     INFO    Invalid prefix/suffix digit len for CgPA
           SIO=03   OPC=001-001-001      DPC=002-002-002
              SCCP MSG TYPE=04
                GTT on CdPA used MOSMSGTA=9193802053
              CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                     PC=003-003-003       SSN=005
              CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                     PC=001-001-001       SSN=004
              LSN=ABCD123  GTTSET=3 203 46
              Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact far end node and investigate reason for error.

3.3.369 1390 - EMAP connection established

This message is generated whenever an EMAP connection is established.

Example 

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1390    CARD xxxx     INFO    EMAP connection established
                 Connection Name : emap1101
                 Report Date:18-06-26  Time:06:50:07

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action necessary.

3.3.370 1391 - EMAP connection terminated

This message is generated whenever an EMAP connection is terminated.

Example 

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1391    CARD xxxx     INFO    EMAP connection terminated
                 Connection Name : emap1101
                 Report Date:18-06-26  Time: 06:50:15

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action necessary.

3.3.371 1392 - IDPRCDPN(X) NPP SERVICE is OFF

The status of the IDPRCDPN(X) NPP service is OFF while processing an IDP message.

Example 
1         2         3         4         5         6         7         8 12345678901234567890123456789012345678901234567890123456789012345678901234567890         tekelecstp 20-12-11 03:56:48 WET  UNKNOWN ??.?.?-64.12.0             5090.1392    CARD 1105     INFO    IDPRCDPN(X) NPP SERVICE is OFF                      Report Date:20-12-11  Time:03:56:48

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the following command to check the status of the IDPRCDPN(X) service: rtrv-npp-serv:srvn=idprcdpn:mode=full
    The following is an example of a possible output. 
    rtrv-npp-serv:srvn=idprcdpn:mode=full
 
    tekelecstp 11-01-28 08:34:00 EST  43.0.0-63.51.0
    rtrv-npp-serv:srvn=idprcdpn:mode=full
    Command entered at terminal #4.
 
    SERVICE     STATUS  SA          PRECEDENCE  FNAI  NAI
    ------------------------------------------------------
    idprcdpn    off     cdial       10          unkn  0
                        ccncchk     100         intl  4
                        cdpnnp      80          natl  3
                        lacck       60          nai1  none
                        cgpnsvcrqd  60          nai2  none
                        asdlkup     50          nai3  none
                        grnlkup     50
                        cgpnasdrqd  50
                        cgpngrnrqd  50
                        inprtg      95
                        skgtartg    50
 
                               DELIMITERS
        dlma=none              dlmb=none              dlmc=none
        dlmd=none              dlme=none              dlmf=none
        dlmg=none              dlmh=none              dlmi=none
        dlmj=none              dlmk=none              dlml=none
        dlmm=none              dlmn=none              dlmo=none
        dlmp=none
 
;
  2. Use the following command to enable the IDPRCGPN(X) NPP service: chg-npp-serv:srvn=idprcgpn:mode=full
    This is an example of a possible output. 
    rtrv-npp-serv:srvn=idprcgpn:mode=full
 
    tekelecstp 11-01-28 08:37:46 EST  43.0.0-63.51.0
    rtrv-npp-serv:srvn=idprcgpn:mode=full
    Command entered at terminal #4.
 
    SERVICE     STATUS  SA          PRECEDENCE  FNAI  NAI
    ------------------------------------------------------
    idprcgpn    off     cdial       10          unkn  0
                        cgpnnp      80          intl  4
                        asdlkup     50          natl  3
                        grnlkup     50          nai1  none
                        blklstqry   90          nai2  none
                        blklstrly   90          nai3  none
                        cgpnrtg     70
                        inprtg      95
 
                               DELIMITERS
        dlma=none              dlmb=none              dlmc=none
        dlmd=none              dlme=none              dlmf=none
        dlmg=none              dlmh=none              dlmi=none
        dlmj=none              dlmk=none              dlml=none
        dlmm=none              dlmn=none              dlmo=none
        dlmp=none
 
;

3.3.372 1393 - IDPRCGPN NPP SERVICE is OFF

The status of the IDPRCGPN NPPservice is OFF while processing an IDP message.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
        tekelecstp 20-12-11 03:56:48 WET  UNKNOWN ??.?.?-63.33.0     
        5090.1392    CARD 1105     INFO    IDPRCDPN NPP SERVICE is Off
                     Report Date:20-12-11  Time:03:56:48

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the following command to check the status of the IDPRCGPN service: rtrv-npp-serv:srvn=idprcgpn
    The following is an example of a possible output. 
        tekelecstp 08-06-17 11:54:09 EST  39.0.0
    rtrv-npp-serv:srvn=idprcgpn
    Command entered at terminal #4.
    SERVICE     STATUS   FNAI   NAI    SA          PRECEDENCE
    _________________________________________________________
    idprcgpn    off      unkn   0      cgpnnp      100
                         intl   4
                         natl   3
                         nai1   none
                         nai2   none
                         nai3   none
;
  2. Use the following command to enable the IDPRCDPN service: chg-npp-serv:srvn=idprcgpn:status=ON

3.3.373 1394 - Flushing undelivered MSUs

The destination EAGLE card for an SS7 message is not reachable by the origination EAGLE card and the dynamic database is not updated to reflect the unreachable status.

Example 
  tekelecstp 02-01-05 20:39:14 MST  EAGLE 41.0
    0010.1394    CARD 1108     INFO    Flushing undelivered MSUs
                 Card List: 1101, 1201, 1302, 2103, 2204
                 LSN=lg1104a0
                 Report Date:02-01-05  Time:20:39:14
;

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Enter the following command to check the IMT bus status for both the source and destination card.
    rept-stat-card:loc=x:mode=full
    wherex is the card location. The source card is identified in the message. The destination card can be obtained from the linkset name in UIM.

    Note:

    There could be several cards involved with the linkset name and thus they all should be checked.

    Following is an example of the possible output using card 1106: 

    
 RLGHNCXA21W 08-01-21 12:01:43 EST  EAGLE 38.0.0
    CARD   VERSION      TYPE      APPL      PST           SST     AST
    1106   021-101-000  TSM       SCCP      IS-NR         Active  -----
      ALARM STATUS       = No Alarms.
      IMT VERSION        = 021-001-000
      PROM VERSION       = 021-001-000
      IMT BUS A          = Conn
      IMT BUS B          = Conn
      CLOCK A            = Active
      CLOCK B            = Idle
      CLOCK I            = Idle
      MBD BIP STATUS     = valid
      DB STATUS          = valid
      DBD MEMORY SIZE    = 64M
      SCCP SERVICE       = 1201, 1214, 1215, 1217, 1102
      SCCP % OCCUP       = 0%
      SLK A   PST        = OOS-MT           LS=ls11234567  CLLI=
      SLK B   PST        = OOS-MT           LS=ls11345678  CLLI=
      SNM    TVG RESULT  = 24 hr: ------,  5 min: ------   
      SCCP   TVG RESULT  = 24 hr: ------,  5 min: ------ 
    Command Completed.
  2. Make sure the cards are correctly connected to both A and B buses of the IMT.

3.3.374 1395 - Inh ATINPQ SS request alrdy outstanding

A second attempt to inhibit the ATINPQ subsystem has been made while the first is still being processed. The second attempt will be ignored.

Example
    station1234 06-12-21 16:28:08 EST Rel 39.2.0
    0020.1395    CARD  1106    INFO     Inh ATINPQ SS request alrdy outstanding

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.375 1396 - Failure Inhibiting ATINPQ SS

The attempted inhibit of the ATINPQ subsystem failed. A response SOG was not received from the mate.

Example
    station1234 06-12-21 16:28:08 EST Rel 39.2.0
    0020.1396    CARD  1106    INFO     Failure Inhibiting ATINPQ SS

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.376 1397 - LSS: Missing Mandatory Parameter

A required parameter was missing in ATI NP query.

Example 
RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 39.2.0
0002.1397    SYSTEM        INFO      LSS:  Missing Mandatory Parameter
          SIO=03   OPC=001-001-001      DPC=002-002-002
             SCCP MSG TYPE=04
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=1234567890901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345677890
                    re cseCD123  GTTSET=3 203 46
             Report Date:07-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify that incoming ATI NP query has Subscriber Identity and Requested Info parameters.

3.3.377 1398 - ATINPQ: Badly formatted Subs Id

The subscriber Identity parameter in ATI NP query was found to be mistyped.
Example 
RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 39.2.0
0002.1398  SYSTEM        INFO      ATINPQ: Badly formatted Subs Id
           SIO=03   OPC=001-001-001      DPC=002-002-002
           SCCP MSG TYPE=04
           CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                  TT=250  NP=04  NAI=010  ADDR=1234567890901
                  PC=003-003-003       SSN=005
           CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                  TT=100  NP=07  NAI=012  ADDR=012345677890
                  re cseCD123  GTTSET=3 203 46
           Report Date:07-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify that Subscriber Identity parameter length is at least 2 bytes (1 byte length field of MSISDN, 1 byte choice for MSISDN). If greater than 2 bytes, the Subscriber identity length must be equal to 2 + length of MSISDN.

3.3.378 1399 - ATINPQ: Subscriber Identity not MSISDN

The Choice for Subscriber Identity in ATI NP query is not MSISDN.
Example 
    RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 39.2.0
    0002.1399    SYSTEM        INFO      ATINPQ: Subscriber Identity not MSISDN
              SIO=03   OPC=001-001-001      DPC=002-002-002
                 SCCP MSG TYPE=04
                 CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=250  NP=04  NAI=010  ADDR=1234567890901
                        PC=003-003-003       SSN=005
                 CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=100  NP=07  NAI=012  ADDR=012345677890
                       re cseCD123  GTTSET=3 203 46
                 Report Date:07-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.379 1400 - LSS: Invalid MSISDN digits length

The MSISDN length in Subscriber Information was 0, or the MSISDN length was 1 ( ‘ /byte) and the MSISDN had only one 0xF (filler) digit.

Example 
RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 39.2.0
0002.1400    SYSTEM        INFO      LSS: Invalid MSISDN digits length
             SIO=03   OPC=001-001-001      DPC=002-002-002
             SCCP MSG TYPE=04
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=1234567890901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345677890
                    re cseCD123  GTTSET=3 203 46
             Report Date:07-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.380 1401 - LSS: Unsupported numbering plan

The Numbering Plan in MSISDN from Subscriber Identity in the incoming ATI NP query is not supported (not ISDN/Telephony (0x1)).

Example 
RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 39.2.0
0002.1401    SYSTEM        INFO      LSS: Unsupported numbering plan
          SIO=03   OPC=001-001-001      DPC=002-002-002
             SCCP MSG TYPE=04
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=1234567890901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345677890
                    re cseCD123  GTTSET=3 203 46
             Report Date:07-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.381 1402 - ATINPQ: Invalid Requested Info

The Requested Info parameter in incoming ATI NP query was invalid. Either, length of Requested Info parameter < 2, or the Requested Info parameter does not contain MNP Requested Info, or the parameter is badly formatted.

Example 
RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 39.2.0
0002.1402    SYSTEM        INFO      ATINPQ: Invalid Requested Info
          SIO=03   OPC=001-001-001      DPC=002-002-002
             SCCP MSG TYPE=04
             CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=250  NP=04  NAI=010  ADDR=1234567890901
                    PC=003-003-003       SSN=005
             CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=100  NP=07  NAI=012  ADDR=012345677890
                    re cseCD123  GTTSET=3 203 46
             Report Date:07-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.382 1403 - LSS: Dgts truncated in encd parms

One or more encoded digits parameters in ATI ACK response had to be truncated to fit maximum allowed encoded digits.

Example 
    RLGHNCXA21W 07-07-21 12:01:43 EST  EAGLE 39.2.0
    0002.1403    SYSTEM        INFO      LSS: Dgts truncated in encd parms
              SIO=03   OPC=001-001-001      DPC=002-002-002
                 SCCP MSG TYPE=04
                 CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=250  NP=04  NAI=010  ADDR=1234567890901
                        PC=003-003-003       SSN=005
                 CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                        TT=100  NP=07  NAI=012  ADDR=012345677890
                       re cseCD123  GTTSET=3 203 46
                 Report Date:07-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the expected number of digits in routing Number and MSISDN fields. These depend on combination of requested formatting for routing Number and MSISDN fields (ATINPQOPTS:ATIACKRN and ATIACKMSISDN options), digits in incoming ATI NP query and result of RTDB lookup.

3.3.383 1407 - Unexpected SI in TIF Stop Action

An MSU is received by TIF/TIF2/TIF3 stop action that is not ISUP. MSUs delivered to a TIF stop action that are not ISUP (SI=5) or TUP (SI=4) shall be routed without modification.

Example 
RLGHNCXA21W 09-09-21 16:20:19 GMT  EAGLE5 39.2.0
    0017.1407    CARD 1103,A   INFO      Unexpected SI in TIF Stop Action
                 SIO=08   OPC=001-001-001       DPC=s-002-002-002
                 DATA=12 34 56 78 90 12 34 56 78 90 12 34
                      56 78 90 12 34 56 78 90 12 34 56 78
                      12 34
                 SR=scrb  LSN=ABCD123
                 Report Date:09-09-21  Time:16:20:19
Legend
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

The TIF Support of TUP feature is not turned on.

3.3.384 1408 - TIF: Modified MSU Too Large to Route

The MSU is too large to transmit after modification (>273 bytes from SIO onward). The original MSU is routed without modification.

Example 
RLGHNCXA21W 09-09-21 16:20:19 GMT  EAGLE5 39.2.0
    0017.1408    CARD 1103,A   INFO      TIF: Modified MSU too large to route
                 SIO=03   OPC=001-001-001       DPC=002-002-002
                 DATA=26 80 03 09 0e 06 09 00 fe 08 50 55 05
                      43 00 00 00 00 00
                 LSN=ABCD123
                 Report Date:09-09-21  Time:16:20:19
Legend
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
SIO
Service information octet
SR
Screening reference name

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.385 1410 - MOSMS: Migrated Subscriber with No Entity

There is no entity defined in the RTDB for the migrated subscriber. The subscriber is found migrated and the migration prefix has to be the entity resulted from RTDB lookup.

Example 
    tekelecstp 02-03-20 07:40:50 EST  EAGLE 40.1
    6815.1410    CARD 1103     INFO    MOSMS: Migrated Subscriber with no entity   
                 SIO=83   OPC=   002-002-001    DPC=   009-008-007
                 CDPA: AI=8b  SSN=002  TT=006
                       ADDR=110000
                 CGPA: AI=43  PC=   002-002-001     SSN=002
                 DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                      3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                      01 00 9f 74 02 00 00 89
                 LSN=ls221
                 Report Date:02-03-20  Time:07:40:50

Alarm Level: No Alarm condition. Message is for information only.

Recovery

Ensure the subscriber has an Entity in the Database, or change MOIGMPFX value of IS41SMSOPTS Table.

3.3.386 1411 - TIF CgPN NS Failure: CC mismatch in DN

A CC mismatch in DN occurred during TIF framework conversion. The CgPN will not be modified.

Example
    tekelecstp 02-03-20 07:40:50 EST  EAGLE 41.0
    0226.1411    CARD 1101   INFO      TIF CgPN NS Failure: CC mismatch in DN
                 International CGPN: 911111012345678
                 EPAP DN           : 899111632226337
                 
                 Report Date:08-09-10  Time:16:20:19

Alarm Level: No Alarm condition. Message is for information only.

Recovery

Verify the Public and Private DNs CC match. If the CCs do not match, reconcile the issue within the subscriber database.

3.3.387 1412 - GTT(FLOBR) failure: max search depth

This message indicates GTT failed when FLOBR encountered a chain longer than maximum depth. The MSU is discarded.

Example 
stpa1071501 09-04-24 13:05:10 EDT  EAGLE5 41.0.0-62.23.1
9941.1412    CARD 2317     INFO    GTT(FLOBR) failure: max search depth
             SIO=83   OPC=   14472-aa       DPC=   07347-aa
             SCCP MSG TYPE=09
             CDPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=1
                    TT=036  NP=01  NAI=004  ADDR=106001000000000000000
                    PC=   07347-aa       SSN=005
             CGPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=1
                    TT=085  NP=07  NAI=003  ADDR=206001000000000000000
                    PC=   14472-aa       SSN=101
             LSN=ls2314n2  GTTSETIDX=211 230 231 232
             Report Date:09-04-24  Time:13:05:10
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
In the CDPA section, PC refers to the Called Party Point Code. In the CGPA section, PC refers to the Calling Party Point Code.
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the provisioning of the GTT information using the rtrv-gta, rtrv-gttsel, and rtrv-gttset commands to determine why the MSU encountered an excessive search depth.

3.3.388 1413 - GTT(FLOBR) failure: duplicate set name

This message indicates GTT failed when FLOBR encountered a duplicate GTT set name in the GTT search. This UIM is issued when the Fallback option is OFF in GTA entry. The MSU is discarded.

Example 
stpa1071501 09-04-24 10:01:40 EDT  EAGLE5 41.0.0-62.23.1
7386.1413    CARD 2317     INFO    GTT(FLOBR) failure: duplicate set name
             SIO=83   OPC=   14504-aa       DPC=   07347-aa
             SCCP MSG TYPE=09
             CDPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=1
                    TT=036  NP=01  NAI=004  ADDR=106005000000000000000
                    PC=   07347-aa       SSN=005
             CGPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=1
                    TT=085  NP=07  NAI=003  ADDR=206005000000000000000
                    PC=   14472-aa       SSN=101
             LSN=ls2314n2  GTTSETIDX=211 215
             Report Date:09-04-24  Time:10:01:40
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Link set name
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
In the CDPA section, PC refers to the Called Party Point Code. In the CGPA section, PC refers to the Calling Party Point Code.
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the provisioning of the GTT information using the rtrv-gta, rtrv-gttsel, and rtrv-gttset commands to determine why the MSU encountered a duplicate GTT set name.

3.3.389 1414 - GTT(FLOBR) warning: max search depth

This message indicates GTT succeeded but searched had encountered a chain longer than the maximum depth. The MSU is routed, as indicated by the index value within the parenthesis of the GTTSETIDX string.

Example 
stpa1071501 09-04-24 13:05:10 EDT  EAGLE5 41.0.0-62.23.1
5096.1414    CARD 2317     INFO    GTT(FLOBR) warning: max search depth
             SIO=83   OPC=   14472-aa       DPC=   07347-aa
             SCCP MSG TYPE=09
             CDPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=1
                    TT=036  NP=01  NAI=004  ADDR=106001000000000000000
                    PC=   07347-aa       SSN=005
             CGPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=1
                    TT=085  NP=07  NAI=003  ADDR=206001000000000000000
                    PC=   14472-aa       SSN=101
             LSN=ls2314n2  GTTSETIDX=211 230 231 (232)
             Report Date:09-04-24  Time:13:18:22
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
In the CDPA section, PC refers to the Called Party Point Code. In the CGPA section, PC refers to the Calling Party Point Code.
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the provisioning of the GTT information using the rtrv-gta, rtrv-gttsel, and rtrv-gttset commands to determine why the MSU encountered an excessive search depth.

3.3.390 1415 - GTT(FLOBR) warning: duplicate set name

This message indicates GTT succeeded, but a duplicate GTT set name was encountered in the GTT Search. This UIM is issued when the Fallback option is ON in GTA entry. The MSU is routed as indicated by the index value within the parenthesis of the GTTSETIDX string.

Example 
stpa1071501 09-04-24 09:56:40 EDT  EAGLE5 41.0.0-62.23.1
7367.1415    CARD 2317     INFO    GTT(FLOBR) warning: duplicate set name
             SIO=83   OPC=   14504-aa       DPC=   07347-aa
             SCCP MSG TYPE=09
             CDPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=1
                    TT=036  NP=01  NAI=004  ADDR=106005000000000000000
                    PC=   07347-aa       SSN=005
             CGPA:  NI=0  RI=0  GTI=04  SSNI=1  PCI=1
                    TT=085  NP=07  NAI=003  ADDR=206005000000000000000
                    PC=   14472-aa       SSN=101
             LSN=ls2314n2  GTTSETIDX=(211) 215

             Report Date:09-04-24  Time:09:56:40
;
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Link set name
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
In the CDPA section, PC refers to the Called Party Point Code. In the CGPA section, PC refers to the Calling Party Point Code.
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the provisioning of the GTT information using the rtrv-gta, rtrv-gttsel, and rtrv-gttset commands to determine why the MSU encountered a duplicate GTT set name.

3.3.391 1416 - MAP Missing Mandatory Parameters

MOSMS Feature could not decode the GSM MAP message, since there are missing mandatory parameters in the TCAP portion of the message, e.g., SM-RP-UI or SM-RP-OA.

Example 
tekelecstp 02-03-20 07:40:50 EST  EAGLE 40.1
    6815.1416    CARD 1103     INFO    MAP Missing Mandatory Parameters
                 SIO=83   OPC=   002-002-001    DPC=   009-008-007
                 CDPA: AI=8b  SSN=002  TT=006
                       ADDR=110000
                 CGPA: AI=43  PC=   002-002-001     SSN=002
                 DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                      3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                      01 00 9f 74 02 00 00 89
                 LSN=ls221
                 Report Date:02-03-20  Time:07:40:50

Alarm Level: No Alarm condition. Message is for information only.

Recovery

Ensure the message contains all mandatory parameters.

3.3.392 1417 - PublicKey doesn’t match known-host file

This message indicates that the SSH public key that is exchanged between the host and server has changed. This could be due to a legitimate configuration change on the server, or it could be caused by a security breach, such as a man-in-the-middle attack.

If strict-host-key-checking is in effect, the connection will be rejected. Otherwise, the new key will be automatically added to the known-host file

Example
    RLGHNCXA21W 13-07-30 21:18:09 EDT  EAGLE5 45.0.0-64.70.1
0130.1417    CARD 1113     INFO    PublicKey doesnt match known-host file
FTP Server IP Address =  xxx.xxx.xxx.xxx
;

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact the server system administrator to determine if the host key change is legitimate.

3.3.393 1418 - SCCP did not route - no SSN in CgPA

This message indicates the GTT failed because a CgPA SSN Set Type was encountered, but no CgPA SSN in MSU. The MSU is discarded.

Example 
stpa1071501 09-04-24 13:05:10 EDT  EAGLE5 41.0.0-62.23.1
 9941.1418    CARD 2317     INFO    SCCP did not route - no SSN in CgPA
              SIO=83   OPC=   14472-aa       DPC=   07347-aa
              SCCP MSG TYPE=09
              CDPA:  NI=0  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=036  NP=01  NAI=004  ADDR=106001000000000000000
                     PC=   07347-aa       SSN=---
              CGPA:  NI=0  RI=0  GTI=04  SSNI=0  PCI=1
                     TT=085  NP=07  NAI=003  ADDR=206001000000000000000
                     PC=   14472-aa       SSN=---
              LSN=ls2314n2  GTTSETIDX=211 230 231 232

              Report Date:09-04-24  Time:13:05:10
;
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
In the CDPA section, PC refers to the Called Party Point Code. In the CGPA section, PC refers to the Calling Party Point Code.
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the provisioning of the GTT information using the rtrv-gta, rtrv-gttsel, and rtrv-gttset commands to determine if the GTT processing path and fallback options are set properly for the incoming MSU.

3.3.394 1419 - SCCP did not route - no SSN in CdPA

This message indicates the GTT failed because a CdPA SSN Set Type was encountered, but no CdPA SSN in MSU. The MSU is discarded.

Example 
    stpa1071501 09-04-24 13:05:10 EDT  EAGLE5 41.0.0-62.23.1
9941.1419    CARD 2317     INFO    SCCP did not route - no SSN in CdPA
             SIO=83   OPC=   14472-aa       DPC=   07347-aa
             SCCP MSG TYPE=09
             CDPA:  NI=0  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=036  NP=01  NAI=004  ADDR=106001000000000000000
                    PC=   07347-aa       SSN=---
             CGPA:  NI=0  RI=0  GTI=04  SSNI=0  PCI=1
                    TT=085  NP=07  NAI=003  ADDR=206001000000000000000
                    PC=   14472-aa       SSN=---
             LSN=ls2314n2  GTTSETIDX=211 230 231 232

             Report Date:09-04-24  Time:13:05:10
;
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
LSN
Linkset name.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
In the CDPA section, PC refers to the Called Party Point Code. In the CGPA section, PC refers to the Calling Party Point Code.
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the provisioning of the GTT information using the rtrv-gta, rtrv-gttsel, and rtrv-gttset commands to determine if the GTT processing path and fallback options are set properly for the incoming MSU.

3.3.395 1424 - IMT A [B] requested to re-align at LOW [HIGH] Rate

This message is issued when a rate change request is sent by the OAM to the HIPR2 cards on a particular bus (to re-align at the requested rate). The HIPR2 cards will initiate the alignment protocol on receiving the request.

Example

RLGHNCXA21W 09-02-07 12:01:43 EST EAGLE 41.1.0
    0023.1424    CARD 1115     INFO     IMT A requested to re-align at HIGH Rate
                 Report Date:09-02-07  Time:12:01:43

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.396 1425 - SMS A-party Address decode failed

Decoding fields of the SMS_OOA parameter of IS41 SMDPP message failed.

Example
    tekelecstp 02-03-20 07:40:50 EST  EAGLE 40.1
    6815.1425    CARD 1103     INFO    SMS A-party Address decode failed
                 SIO=83   OPC=   002-002-001    DPC=   009-008-007
                 CDPA: AI=8b  SSN=002  TT=006
                       ADDR=110000
                 CGPA: AI=43  PC=   002-002-001     SSN=002
                 DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
                      3d cf 01 e9 d1 02 09 35 f2 34 9f 69
                      01 00 9f 74 02 00 00 89
                 LSN=ls221
                 Report Date:02-03-20  Time:07:40:50

Alarm Level: No Alarm condition. Message is for information only.

Recovery

Ensure that SMDPP message contains properly formatted SMS_OOA parameter.

3.3.397 1426 - S-Port: Missing GRN for srvc prtd subs

Service Portability required RTDB data “GRN” to format outbound digits, which was not found.

Example 1 
 0017.1042    CARD 1103,A   INFO      S-Port: Missing GRN for srvc prtd subs
                 SIO=03   OPC=001-001-001       DPC=002-002-002
                 INCM DN: 4605500 
                 COND DN: 19194605500
                 LSN=ABCD123
Example 2 

  6850.1426    CARD 1103     INFO    S-Port: Missing GRN for srvc prtd subs   
                 SIO=83   OPC=   002-002-001    DPC=   009-008-007
                 CDPA: AI=8b  SSN=002  TT=006
                       ADDR=987654
                 CGPA: AI=09  PC=--------------     SSN=003
                 INCM DN: 4605500 
                 COND DN: 19194605500
                 LSN=ABCD123

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify that a GRN has been provisioned for the conditioned DN (specified in the COND DN field in the UIM output) in EPAP.

3.3.398 1427 - IAR CdPN parameter invalid or not found

This message is issued when the IAR Base feature cannot find a CdPN parameter within a message, when it cannot decode the parameter after it finds it, or when the parameter does not contain the required information in a usable format.

Example 
    RLGHNCXA21W 09-07-21 16:20:19 EST  EAGLE 41.1.0
    0002.1427    CARD 1113     INFO      IAR CdPN parameter invalid or not found
                 Report Date:09-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.399 1428 - IAR CgPN parameter invalid or not found

This message is issued when the IAR Base feature cannot find the CgPN parameter within a message, when it cannot decode the parameter after it finds it, or when the parameter does not contain the required information in a usable format.

Example 
    RLGHNCXA21W 09-07-21 16:20:19 EST  EAGLE 41.1.0
    0002.1428    CARD 1113     INFO      IAR CgPN parameter invalid or not found
                 Report Date:09-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.400 1429 - IAR TRIGTYPE invalid or not found

This message is issued when the IAR Base feature cannot find the TRIGTYPE parameter within a message, when it cannot decode the parameter after it finds it, or when the parameter does not contain the required information in a usable format.

Example 
    RLGHNCXA21W 09-07-21 16:20:19 EST  EAGLE 41.1.0
    0002.1429    CARD 1113     INFO      IAR TRIGTYPE invalid or not found
                 Report Date:09-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.401 1430 - IAR CdPN parameter encoding failed

This message is issued when the IAR Base feature cannot encode the message after modifying its CdPN parameter. One way that this can occur without invalid data is when a CdPN parameter length increases, and the containing message grows too large.

Example 
    RLGHNCXA21W 09-07-21 16:20:19 EST  EAGLE 41.1.0
    0002.1430    CARD 1113     INFO      IAR CdPN parameter encoding failed
                 Report Date:09-07-21  Time:16:20:19

Alarm Level: No Alarm condition. Message is for information only.

Recovery

No action necessary.

3.3.402 1431 - IAR CgPN parameter encoding failed

This message is issued when the IAR Base feature cannot encode the message after modifying its CgPN parameter. One way that this can occur without invalid data is when a CgPN parameter length increases, and the containing message grows too large.

Example 
    RLGHNCXA21W 09-07-21 16:20:19 EST  EAGLE 41.1.0
    0002.1431    CARD 1113     INFO      IAR CgPN parameter encoding failed
                 Report Date:09-07-21  Time:16:20:19

Alarm Level: No Alarm condition. Message is for information only.

Recovery

No action necessary.

3.3.403 1432 - IGM Relay Failed - Bad IS41SMSC Xlation

This message indicates that the GTT translation lookup on DEFIS41SMSC digits (within GTTSET specified by IS41SMSCGTTSN) failed.

Example 

station1234 09-08-30 16:28:08 EST EAGLE5 41.1.0
1234.1432    CARD 1101     INFO    IGM Relay Failed - Bad IS41SMSC Xlation
             SIO=03   OPC=   7-001-7        DPC=   1-001-1
             SCCP MSG TYPE=09
             CDPA:  NI=0  RI=0  GTI=02  SSNI=0  PCI=0
                    TT=010  NP=--  NAI=---  ADDR=9911308117   
                    PC=--------------    SSN=---
             CGPA:  NI=0  RI=1  GTI=00  SSNI=1  PCI=1
                    PC=   7-001-7        SSN=010
             LSN=lsi1  GTTSETIDX=1
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Provision the translation entry for DEFIS41SMSC digits within the GTTSET specified by IS41SMSCGTTSN. Use the rtrv-gttset command to search the GTT set name based on the GTTSET index displayed in the UIM.
  2. Change the IS41SMSCGTTSN option value in the GSMOPTS table to a valid GTT set name that contains translation for DEFIS41SMSC digits.

3.3.404 1433 - AIQ: Inhibit request already pending

An inh-map-ss command is already entered and queued.

Example

RLGHNCXA21W 00-02-10 12:01:43 EST EAGLE 42.0.0
0014.1433 SYSTEM INFO AIQ: Inhibit request already pending

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.405 1434 - AIQ: Failure Inhibiting SS

The inh-map-ss command did not take the AIQ subsystem off-line.

Example

RLGHNCXA21W 00-02-10 12:01:43 EST EAGLE 42.0.0
0014.1434 SYSTEM INFO AIQ: Failure Inhibiting SS

Alarm Level: No alarm condition. The message is informational only.

Recovery

Enter the inh-map-ss command with the force parameter.

3.3.406 1435 - AIQ: TriggerType not provisioned

This message indicates that the AIQ subsystem received an AIQ message where the value of the TriggerType parameter is not provisioned in the AIQOPTS table.

Example

    5193.1435    CARD 1105     INFO    AIQ: TriggerType not provisioned
                 SIO=83   OPC=   001-001-001    DPC=   009-008-007
                 CDPA: AI=cb  SSN=014  TT=004
                       ADDR=9873946354
                 CGPA: AI=cb  PC=   001-001-001     SSN=014
                 DATA=3f e2 3d c7 04 00 01 02 03 e8 35 e9
                      33 cf 01 2a d1 02 09 40 f2 29 81 07
                      00 00 00 00 00 00 00 84
                 LSN=ls1
                 Report Date:20-08-29  Time:02:55:22

Alarm Level: No alarm condition. The message is informational only.

Recovery

Ensure the AIQ message’s TriggerType parameter value is one of those provisioned in the AIQOPTS table.

3.3.407 1436 - AIQ: Unsupported Digits(Dialed) length

This message indicates that the AIQ subsystem received an AIQ message where the length of the Digits(Dialed) parameter is outside of the range provisioned in the AIQOPTS table.

Example

    0643.1436    CARD 1105     INFO    AIQ: Unsupported Digits(Dialed) length 
                 SIO=83   OPC=   001-001-001    DPC=   009-008-007
                 CDPA: AI=cb  SSN=014  TT=004
                       ADDR=9873946354
                 CGPA: AI=cb  PC=   001-001-001     SSN=014
                 DATA=3f e2 3d c7 04 00 01 02 03 e8 35 e9
                      33 cf 01 2a d1 02 09 40 f2 29 81 07
                      00 00 00 00 00 00 00 84
                 LSN=ls1
                 Report Date:20-08-29  Time:03:04:25

Alarm Level: No alarm condition. The message is informational only.

Recovery

Ensure the AIQ message’s Digits(Dialed) parameter length is within the range provisioned in the AIQOPTS table.

3.3.408 1437 - IMT [A|B]: Rate change not initiated

This message is issued when the IMT Rate change could not proceed due to bus being in alarming state.

Example 
RLGHNCXA21W 09-02-07 12:01:43 EST EAGLE 41.1.0
    0023.1437    CARD 1115     INFO      IMT A: Rate change not initiated
                 Report Date:09-02-07  Time:12:01:43

Alarm Level: No alarm condition. The message is informational only.

Recovery

Although no action is required, this message can serve as a notification to verify status of the IMT bus and to start recovery procedures if needed.

  1. Enter the rept-stat-imt command to verify the status of the IMT bus.
  2. Replace any faulty cards with a new HIPR2 card.
  3. Contact unresolvable-reference.html#GUID-6A9FA28A-A250-400D-B162-873CF95A69FA for more information.

3.3.409 1439 - SIP card exceeded threshold TPS

The alarm indicates that the SIP card has reached maximum TPS.

Example
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1439    CARD 1106     INFO      SIP card exceeded threshold TPS
                 Report Date:13-09-03  Time:18:57:35

Alarm Level: No alarm condition. The message is informational only.

Recovery

Traffic must be reduced to the SIP card. Failure to reduce SIP card traffic may result in traffic or card failure.

3.3.410 1440 - G-Flex MLR: Op with bad MSISDN skipped

The G-Flex MLR Function encountered an MSISDN parameter that contains fewer than 5 digits or more than 15 digits

Example
    station1234 06-12-21 16:28:08 EST Rel 42.0.0
    0020.1440    CARD  1106    INFO     G-Flex MLR: Op with bad MSISDN skipped

Alarm Level: No alarm condition. The message is informational only.

Recovery

Abnormal length of the MSISDN indicates a configuration issue on the far-end node, which can be confirmed with a message trace.

3.3.411 1441 - IP Info mismatch, card reset required

The card stated in the message has an IP mismatch and must be reset. This occurs when the database is updated and a manual reset must be performed for the newly provisioned values to be used.

The IP configuration commands support the MCAP locations when OAMHC is running. Usually these commands require the target card to be inhibited, however for MCAP locations, the command is expected to be run while the card is IS-NR. Since these commands result in a database update, they require the MCAP to be IS-NR. Once the database has been modified, manual reset of the card must be performed for the newly provisioned values to be used. A notice is displayed to the user regarding the reset requirement for an MCAP location. If the MCAP location is not reset, then a UIM is displayed once every hour indicating that the card has an IP Mismatch and must be reset.

Example
RLGHNCXA03W 10-01-11 16:20:19 EST EAGLE 42.0.0
    0020.1441    CARD 1113     INFO      Active OAM IP mismatch, 1113 reset req
                 Report Date:10-01-11  Time:16:20:19


    0020.1441    CARD 1113     INFO      Standby OAM IP mismatch, 1115 reset req
                 Report Date:10-01-11  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Reset the card in the appropriate slot as specified in the message text.

3.3.412 1442 - Invalid EMP SCR Message Received

This UIM indicates that the EAGLE 5 ISS received and rejected an invalid Service Configuration Request (SCR) EMP message. The UIM includes the IP address where the request originated and the reason the EAGLE 5 ISS rejected the SCR message.

Example 
    0020.1442    CARD 1106,A   INFO      Invalid EMP SCR Message Received
                 MSG Length=6             
                 REQ EMP Version=4       RSP EMP Version=4 
                 REQ Transaction ID=123  RSP Transaction ID=123
                 IMF IP Address= 172.21.48.15
                 Reason=Invalid Message Length     
                 Report Date:10-02-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary if there is only one occurrence. If the condition continues, use the information provided in the message to debug the problem.

3.3.413 1443 - GTT Action Failed to Send TCAP Error

This UIM indicates that the TCAP error action could not generate a TCAP error response due to any failure in decoding TCAP.

Example 
6054.1443    CARD 1101     INFO    GTT Action FAILED TO SEND TCAP ERROR
           OPC=   1-001-4        DPC=   1-001-5
           CDPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                  TT=010  NP=--  NAI=---  ADDR=9818316478
                  PC=   1-001-1        SSN=016
           CGPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=1
                  TT=011  NP=--  NAI=---  ADDR=9910929095
                  PC=   1-002-3        SSN=049
           Op-Code=--- Action Set=tcapset
           Report Date:03-01-03  Time:16:55:23
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
OP-CODE
Operation Code
PARAM
Parameter
PC
Point code for the SS7 end user
PCI
Protocol control information
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery:

Do just one of the following to fix the problem:

  1. Correct the TCAP Portion.
  2. Disassociate “TCAP Error” GTT Action from the GTT Translation.
  3. Change the “TCAP ERROR” action to either “UDTS” or “DISCARD” GTT Action.

3.3.414 1444 - GTT Loadsharing fail: PC not in MRNSET

This UIM indicates that the EAGLE 5 ISS failed to loadshare a MSU, because the translated DPC is not present in the specified non-default MRNSET.

Example 
0019.1444    CARD 1104,A   INFO      GTT Loadsharing fail: PC not in MRNSET
           TRANSLATED PC=003-003-003       TRANSLATED SS=005
              GTT on CdPA used MOSMSGTA= 9193802053
           CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                  TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                  PC=003-003-003       SSN=005
           CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                  TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                  PC=001-001-001     SSN=004 
           LSN=ABCD123  GTTSET=3 (8)
           Report Date:02-07-21  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
GTI
Global title indicator
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
OP-CODE
Operation Code
PARAM
Parameter
PC
Point code for the SS7 end user
PCI
Protocol control information
RI
Routing indicator
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery:

Do one the following to fix the problem:

  1. Configure the DPC displayed in UIM within the displayed MRNSETID.
  2. Configure correct MRNSETID (which contains the DPC displayed in the UIM) in associated GTT Translation entry.
  3. Configure “Default” MRNSETID in the GTT Translation entry.

3.3.415 1445 - LNP Day Meas. Discarded for LRN

This message is indicates that the Daily LNR measurement counts are incorrect because of discards due to provisioning.

Example 
RLGHNCXA03W 10-01-11 16:20:19 EST EAGLE 42.0.0
     0020.1015    CARD 1106     INFO      LNP Day Meas. Discarded for LRN 
                 Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action required.

3.3.416 1446 - XUDT UDT conversion failed

The conversion from XUDT to UDT (or UDT to XUDT) failed, and the message was routed without the XUDT UDT conversion. Depending on which features are applied after XUDT UDT conversion, other processing of the message may occur after the failed XUDT UDT conversion.
Example 
0018.1446    CARD 1103,A     INFO    XUDT UDT conversion failed
        SIO=03   OPC=001-001-001      DPC=002-002-002
           SCCP MSG TYPE=04
           CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                  TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                  PC=003-003-003       SSN=005
           CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                  TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                  PC=001-001-001       SSN=004
           LSN=ABCD123  GTTSET=3 203 46
           Report Date:10-06-14  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Refer to the following to correct the problem:
  • Database Administration Manual - Global Title Translation
  • The ent/chg/rtrv-dstn commands in the Commands Manual
manual to correct the problem.

3.3.417 1447 - Cnvrsn Discard: inv segmentation parm

This UIM is issued when the EAGLE 5 ISS receives an XUDT message that has a segmentation parameter that is incorrect for the message undergoing ANSI/ITU SCCP conversion.

Example 
0018.1447    CARD 1103,A     INFO    Cnvrsn Discard: inv segmentation parm
        SIO=03   OPC=001-001-001      DPC=002-002-002
           SCCP MSG TYPE=04
           CDPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                  TT=250  NP=04  NAI=010  ADDR=123456789012345678901
                  PC=003-003-003       SSN=005
           CGPA:  NI=1  RI=0  GTI=04  SSNI=0  PCI=1
                  TT=100  NP=07  NAI=012  ADDR=012345678901234567890
                  PC=001-001-001       SSN=004
           LSN=ABCD123  GTTSET=3 203 46
           Report Date:10-06-14  Time:16:20:19
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DPC
Destination point code
GTI
Global title indicator
GTTSET
GTT Set Index
LSN
Linkset name. The name must be unique.
MSG TYPE
Message type
NAI
Nature of address indicator
NI
Network indicator value
NP
Numbering plan
OPC
Origination point code
PC
Point code for the SS7 end user (OPC).
PCI
Protocol control information
RI
Routing indicator
SIO
Service information octet
SSN
Subsystem number
SSNI
Subsystem number indicator
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Check the incoming XUDT message to find the incorrectly formatted Segmentation parameter. Contact the node that is sending the messages.

3.3.418 1448 - G-Flex MLR: Op w/o IMSI/MSISDN skipped

The G-Flex MAP Layer Routing Function encountered problems because the IMSI or MSISDN parameter is missing. Normal G-Flex processing is applied to the associated message.

Example 
0018.1448    CARD 1103,A     INFO    G-Flex MLR: Op w/o IMSI/MSISDN skipped
          SIO=83   OPC=   002-002-001    DPC=   009-008-007
          CDPA: AI=8b  SSN=002  TT=006
                ADDR=110000
          CGPA: AI=43  PC=   002-002-001     SSN=002
          DATA=49 e2 47 c7 04 47 04 25 1e e8 3f e9
               3d cf 01 e9 d1 02 09 35 f2 34 9f 69
               01 00 9f 74 02 00 00
          LSN=ls221
          Report Date:10-10-10  Time:07:40:50
Legend
ADDR
Address
CDPA
Called party address
CGPA
Calling party address
DATA
Information from the upper layers of SCCP management
DPC
Destination point code
LSN
Linkset name. The name must be unique.
OPC
Origination point code
PC
Point code for the SS7 calling user (CgPA)
SIO
Service information octet
SSN
Subsystem number
TT
Translation type

Alarm Level: No alarm condition. The message is informational only.

Recovery

Contact far end note and investigate reason for error.

3.3.419 1449 - Binding Failed for screen set: <screen set name>

This UIM indicates a screen-set binding failure in Gateway Screening (GWS).

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
   0023.1449    CARD 1105    INFO       Binding Failed for screen set: ayyy 
                Report Date:11-05-26  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

Refer to the UIM for the name of the failed screen set. The LIM or Service Module card regenerates a binding request.

3.3.420 1450 - IDPRCDPN CDPN Encoding Failed

This UIM is raised if IDPRCDPN encoding fails.

Example 
    1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    eagle4 02-03-06 14:31:03 MST  UNKNOWN ??.?.?-64.19.0
    9442.XXXX    CARD 1105     INFO    IDPR CDPN  encoding failed
                 SIO=03   OPC=   1-010-1        DPC=   1-001-1
                 CDPA: AI=0b  SSN=051  TT=025
                       ADDR=9900112233
                 CGPA: AI=4a  PC=--------------     SSN=051
                 INCM DN: 9992222226
                 COND DN: 9992222226
                 LSN=itu1
                 Report Date:02-03-06  Time:14:31:03

Alarm Level: No alarm condition. The message is informational only.

Recovery

One or more of following actions must be taken:

  1. The Formatting Action list in the NPP Action Set that processed the IDP Query must be corrected.
  2. The data associated with DN in the RTDB must be corrected.
  3. The message must have enough space for the CDPN parameter expansion.

3.3.421 1451 - IDPRCGPN CGPN Encoding Failed

This UIM is raised if IDPRCGPN encoding fails.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
        9452.1451    CARD 1105     INFO    IDPR CGPN  encoding failed
                 SIO=03   OPC=   1-010-1        DPC=   1-001-1
                 CDPA: AI=0b  SSN=051  TT=025
                       ADDR=9900112233
                 CGPA: AI=4a  PC=--------------     SSN=051
                 INCM DN: 9992222227
                 COND DN: 9992222227
                 LSN=itu1
                 Report Date:02-03-06  Time:14:37:31

Alarm Level: No alarm condition. The message is informational only.

Recovery

One or more of following actions must be taken:

  1. The Formatting Action list in the NPP Action Set that processed the IDP Query must be corrected.
  2. The data associated with DN in the RTDB must be corrected.
  3. The message must have enough space for the CGPN parameter expansion.

3.3.422 1452 - Invalid IP Address from SCTP Heartbeat Response

This UIM indicates an SCTP layer received a Heartbeat Response (HB) with a source IP address that did not match the IP address from where the original HB message was sent.

Example 
    1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
0388.1452    CARD 1308,A   INFO     SCTP HB ACK from unexpected IP address
   HB RESP IPADDR = 10.254.111.21
   HB RESP PORT   = 4002
   HB INFO IPADDR = 10.254.111.21
   HB INFO PORT   = 4002
   SNAME          = sg1308b
                 Report Date:12-07-10  Time:13:45:24

Alarm Level: No alarm condition. The message is informational only.

Recovery

Correct the IP network setup for the SCTP association.

3.3.423 1453 - EE Collection started

This UIM indicates collection has started on a network card when Eagle Eyes proper is in Active state.

Example 
    1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
0023.1453    CARD 1105     INFO      Collection started on card

Alarm Level: No alarm condition. The message is informational only.

Recovery

None.

3.3.424 1454 - EE Collection end

This UIM indicates the collection ends when Eagle Eyes proper enters idle state.

Note:

EAGLE may not output this UIM when Eagle Eye Collection termination is initiated by the system based on the set capture limit (SECLIM, PKTLIM, and KBLIM).
Example 
    1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
0023.1454    CARD 1105     INFO      EE Collection end

Alarm Level: No alarm condition. The message is informational only.

Recovery

None.

3.3.425 1455 - EE Queue full, Packets Dropped

This UIM indicates the message queue on the GEDTI card is full; no more packets can be enqueued..

Example 
    1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
0023.1455    CARD 1105     INFO      EE Queue Full Packets Dropped

Alarm Level: No alarm condition. The message is informational only.

Recovery

None.

3.3.426 1456 - Hub Congested, Packets Dropped

This UIM indicates the message queue between the GEDTI and EEPC is full.

Example 
    1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
0023.1456    CARD 1105     INFO      Hub Congested Packets Dropped

Alarm Level: No alarm condition. The message is informational only.

Recovery

None.

3.3.427 1457 - GEDTI Port Enabled

This UIM indicates the GEDTI port is enabled on the IPSM card.

Example 
    1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
9671.1457    CARD 1112     INFO      GEDTI Port Enable
                 PORT = 5555

Alarm Level: No alarm condition. The message is informational only.

Recovery

None.

3.3.428 1458 - GEDTI Port Disabled

This UIM indicates the GEDTI port is disabled on the IPSM card.

Example 
    1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
9642.1458    CARD 1112     INFO      GEDTI Port Disabled
                 PORT = 5555

Alarm Level: No alarm condition. The message is informational only.

Recovery

When the GEDTI port is enabled.

3.3.429 1459 - TCP Connection lost b/w IPSM and EEPC

This UIM indicates the TCP Connection between the IPSM card and network card has been lost.

Example 
    1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
0023.1459    CARD 1105     INFO      TCP Connection lost b/w IPSM and EEPC
                 SESSION ID = 1

Alarm Level: No alarm condition. The message is informational only.

Recovery

When the TCP Connection is re-established.

3.3.430 1460 - GWS Duplicate Stop Action Failed

This message indicates the gateway screening (GWS) Duplicate and Route stop action failed to duplicate an incoming MSU.

Example 
5347.1460    CARD 1103     INFO      GWS Duplicate Stop Action Failed
                 Report Date:13-10-10  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No further action is required.

3.3.431 1461 - Link status on card needs re-sync

This message indicates the Link status on the card needs to be re-synched and the system has initiated a re-synchronization.

Example 
0020.1461    CARD 1106     INFO      Link status on card needs re-sync
                 Card=xxxx Port=xxx
                 Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

3.3.432 1462 - EE not Configured

This message indicates the EE capture does not start when the network card under capture is not configured as Eagle Eyes Proper.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0023.1462    CARD 1105     INFO      EE not Configured

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.433 1463 - ENUM connection established

This message indicates the ENUM connection has come into IS-NR state.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1463    CARD 1463     INFO    ENUM connection established
                 Connection Name : enum1101
                 Report Date: 06-05-14  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.434 1464 - ENUM connection terminated

This message indicates the ENUM connection has gone down.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1464    CARD 1464     INFO    ENUM connection terminated
                 Connection Name : enum1101
                 Report Date:06-05-14  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.435 1466 - ENUM Dflt Prof & query type mismatch

The Default ENUM Profile response type and incoming query type do not match.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1466    CARD 1466     INFO      ENUM Dflt Prof & query type mismatch
        Report Date: 06-05-14 Time:18:57:35

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.436 1467 - ENUM msg decode failed

This message indicates an ENUM message validation has FAILED.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1467    CARD 1467,B   INFO      ENUM  msg decode failed
                 Reason: Response Recieved
                 Header: QR(1)
                 Domain: ----
                 IP    : 10.248.13.3
                 QType : ----
                 Entity ID: ----
                 Report Date:06-05-14  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.437 1468 - ENUM rcvd invalid msg

This message indicates the ENUM has received a query with unsupported field values.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1468    CARD 1468,B   INFO      ENUM rcvd invalid msg
                 Reason: Invalid Domain
                 Header: QR(0)
                 Domain: e164.abcd
                 IP    : 10.248.13.3
                 QType : NAPTR(35)
                 Entity ID: ----
                 Report Date: 06-05-14 Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.438 1469 - ENUM request rejected

This message indicates an ENUM request rejected is coming from invalid IP addresses.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1469    CARD 1469,B   INFO      ENUM request rejected
                 Reason: Unauthorized ENUM Client
                 Header: ----
                 Domain: ----
                 IP    : 10.248.13.9
                 QType : ----
                 Entity ID: ----
                 Report Date: 06-05-14 Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.439 1471 - ENUM matching prof for qry not found

This message indicates the ENUM Profile Table is missing an entry of a matching ENUM query type.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1471    CARD 1471,B   INFO      ENUM matching prof for qry not found
                 Reason: Queried Response type not found
                 Header: QR(0)
                 Domain: e164.arpa
                 IP    : 10.248.13.3
                 QType : NAPTR(35)
                 Entity ID: 123456
                 Report Date: 06-05-14 Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.440 1472 - SCTP Buffer full timer expired, Restart

This message indicates the SCTP Buffer full timer has expired and requires a restart.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.1472    CARD 1104     INFO      SCTP Buffer full timer expired, Restart
                 Report Date: 06-05-14  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.441 1473 - Unable to connect to socket

This message indicates the EAGLE is unable to connect to the EAGLE Application Processor. Verify the IP configuration for connectivity to the far end.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0002.1473    CARD 1113     INFO      Unable to connect to socket
                 Report Date:02-07-21  Time:16:20:19

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.442 1475 - TOBR Multiple Comp: Translation found

This message indicates a translation has been found for more than one component even if its priority numbers are lower than the first component.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    5902.1475    CARD 1101     INFO    TOBR Multiple Comp: Translation found
                 SIO=03   OPC=   6-006-1        DPC=   7-007-7
                 SCCP MSG TYPE=09
                 CDPA:  NI=0  RI=0  GTI=00  SSNI=0  PCI=1
                        PC=   3-132-5        SSN=---
                 CGPA:  NI=0  RI=1  GTI=00  SSNI=1  PCI=1
                        PC=   0-141-7        SSN=146
                 LSN=ls661  GTTSETIDX=2
                 Report Date:16-12-07  Time:11:20:32

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.443 1476 - TCAPMulComp: Dup Opcode MSU discarded

This message indicates the duplicate in a TCAP Message with the same Opcode in more than one component has been discarded.

Example
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    5902.1476    CARD 1101     INFO    TCAPMulComp: Dup Opcode MSU discarded
                 SIO=03   OPC=   6-006-1        DPC=   7-007-7
                 SCCP MSG TYPE=09
                 CDPA:  NI=0  RI=0  GTI=00  SSNI=0  PCI=1
                        PC=   3-132-5        SSN=---
                 CGPA:  NI=0  RI=1  GTI=00  SSNI=1  PCI=1
                        PC=   0-141-7        SSN=146
                 LSN=ls661  GTTSETIDX=2
                 Report Date:16-12-07  Time:11:20:32

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.444 1477 - SFAPP Validation Response Timeout Error

This message indicates an SFAPP validation response timeout error.

Example 
   0156.1477    CARD 1103     INFO    SFAPP Validation Response Timeout Error
                 Reason: ----
                 OPC=   001-001-001    DPC=   003-003-001
                 CDPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=1
                        TT=010  NP=--  NAI=---  ADDR=9999
                        PC=   003-003-001    SSN=009
                 CGPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=1
                        TT=034  NP=--  NAI=---  ADDR=131313
                        PC=   003-003-001    SSN=009
                 ACN=4-0-0-1-0-18-2          PKG-Type=TC BEGIN(0x62)
                 MSISDN: NP=1    NON=1    ADDR=123456
                 LSN=ls331  Op-Code= 12  GTT Action Set=sfapp1
                 Report Date:17-12-14  Time:17:26:35

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.445 1478 - SFAPP Validation Encoding Error

This message indicates an SFAPP validation encoding error.

Example 
    1053.1478    CARD 1107     INFO    SFAPP Validation Encoding Error
                 Reason: INVALID ACN
                 OPC=   003-003-001    DPC=   001-001-001
                 CDPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=1
                        TT=010  NP=--  NAI=---  ADDR=9999
                        PC=   003-003-001    SSN=008
                 CGPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=1
                        TT=011  NP=--  NAI=---  ADDR=131313
                        PC=   001-001-001    SSN=009
                 ACN=---                     PKG-Type=TC BEGIN(0x62)
                 ---   : NP=---  NON=---  ADDR=-----
                 LSN=ls331  Op-Code=  0  GTT Action Set=
                 Report Date:17-12-15  Time:19:47:46

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.446 1479 - SFAPP Validation Matching State not fnd

This message indicates the SFAPP validation matching state was not found.

Example 
    7604.1479    CARD 1107     INFO    SFAPP Validation Matching State not fnd
                 Reason: TID NOT FOUND
                 OPC=   3-003-1        DPC=   1-001-1
                 CDPA:  NI=0  RI=1  GTI=00  SSNI=1  PCI=1
                        PC=   1-001-1        SSN=005
                 CGPA:  NI=0  RI=1  GTI=00  SSNI=1  PCI=1
                        PC=   3-003-1        SSN=005
                 ACN=---                     PKG-Type=TC END(0x64)
                 IMSI  : NP=---  NON=---  ADDR=-----
                 LSN=ls331  Op-Code=---  GTT Action Set=-----
                 Report Date:17-12-18  Time:15:59:17

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.447 1480 - SFAPP Validation Error

This message indicates an SFAPP validation error.

Example 
    1053.1480    CARD 1107     INFO    SFAPP Validation Error
                 Reason: INVALID ACN
                 OPC=   003-003-001    DPC=   001-001-001
                 CDPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=1
                        TT=010  NP=--  NAI=---  ADDR=9999
                        PC=   003-003-001    SSN=008
                 CGPA:  NI=1  RI=0  GTI=02  SSNI=1  PCI=1
                        TT=011  NP=--  NAI=---  ADDR=131313
                        PC=   001-001-001    SSN=009
                 ACN=---                     PKG-Type=TC BEGIN(0x62)
                 ---   : NP=---  NON=---  ADDR=-----
                 LSN=ls331  Op-Code=  0  GTT Action Set=
                 Report Date:17-12-15  Time:19:47:46

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.448 1481 - SFAPP Validation Velocity Chk Failed

This message indicates the SFAPP validation velocity check has failed.

Example 
    5184.1481    CARD 1107     INFO    SFAPP Validation Velocity Chk Failed
                 Reason: THRESHOLD EXCEEDED
                 OPC=   1-001-1       LSN=  ls331 GTT Action=sfapp1
                 CGPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=0
                        TT=017  NP=--  NAI=---  ADDR=12345678
                        PC=--------------    SSN=000
                 PKGTYPE=TC BEGIN(0x62) ACN=  4-0-0-1-0-32-3 OpCode=23
                 Loc from HLR      :  NP= 1  NoN=  1  ADDR=121212
                 AgeOfLocation     :  257
                 Threshold         :  999
                 SubscriberState   :  SFAPP_NOT_PROVIDED_BY_VLR_SGSN
                 Report Date:17-12-14  Time:13:46:15

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.449 1482 - SFAPP Validation Failed

This message indicates the SFAPP validation has failed.

Example 
   7735.1482    CARD 1107     INFO    SFAPP Validation Failed
                 Reason: VLR MISMATCH
                 OPC=   1-001-1       LSN=  ls331 GTT Action=sfapp1
                 CGPA:  NI=0  RI=0  GTI=02  SSNI=1  PCI=0
                        TT=017  NP=--  NAI=---  ADDR=12345678
                        PC=--------------    SSN=000
                 PKGTYPE=TC BEGIN(0x62) ACN=  4-0-0-1-0-18-3 OpCode=12
                 Loc from HLR      :  NP= 1  NoN=  1  ADDR=123456
                 AgeOfLocation     :  28784
                 Threshold         :  ----
                 SubscriberState   :  SFAPP_CS_ASSUME_IDLE
                 Report Date:17-12-18  Time:16:35:10

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.450 1483 - SFAPP VLR Status Changed

This message indicates the SFAPP VLR status has changed.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
        5105.1483    CARD 1101     INFO    SFAPP VLR Status Changed
  VLR=727272          : PREV STATUS=GrayList
  CURR STATUS=Whitelist  : Updated DB=No
  Report Date:18-05-21  Time:15:37:11
;

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.451 1484 - SFAPP New VLR Created

This message indicates a new SFAPP VLR has been created.

Example 
1         2         3         4         5         6         7         8
1234567890123456789012345678901234567890123456789012345678901234567890123456789
    5039.1484    CARD 1101     INFO    SFAPP New VLR Created
  VLR=727272          : STATUS=Graylist
                 Report Date:18-05-21  Time:15:32:00;

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.452 1485 - SFAPP New Roaming Entry Created

This message indicates a new SFAPP roaming entry has been created.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    5039.1485    CARD 1101     INFO    SFAPP New Roaming Entry Created
  OLD_VLR=727272          : NEW_VLR=999999
  THRESHOLD=999
                 Report Date:18-05-21  Time:15:32:00

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.453 1486 - SFAPP New Primary Card Chosen

This message indicates a new primary SFAPP card has been chosen.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    5016.1486    CARD 1101     INFO    SFAPP New Primary Card Chosen
                 PRIMARY_SFAPP: LOC=1101
                 Report Date:18-05-21  Time:15:24:13

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.454 1487 - SFAPP Dyn VLR ROAM Entry Deleted

This message indicates an SFAPP Dynamic VLR Roaming entry has been deleted.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    5039.1487    CARD 1101     INFO    SFAPP Dyn VLR ROAM Entry Deleted
                 OLD_VLR=727272          : NEW_VLR=999999
                 THRESHOLD=999
                 Report Date:18-05-21  Time:15:32:00

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.455 1488 - SFAPP Velocity Threshold Crossed

This message indicates the SFAPP velocity threshold has been crossed.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    5039.1488    CARD 1101     INFO    SFAPP Velocity Threshold Crossed
                 OLD_VLR=727272          : NEW_VLR=999999
                 THRESHOLD=999
                 Report Date:18-05-21  Time:15:32:00

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.456 1489 - SFAPP Dyn VLR Prof Entry deleted

This message indicates an SFAPP Dynamic VLR Profile entry has been deleted.

Example 
1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    5039.1489    CARD 1101     INFO    SFAPP Dyn VLR Prof Entry deleted
                 VLR=727272          : STATUS=Graylist
                 Report Date:18-05-21  Time:15:32:00

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.

3.3.457 1490 - Telnet terminal connection successful

Indicates that a telnet connection has been established with the EAGLE from the specified location, but no terminal has yet been selected.

Example 
RLGHNCXA21W 00-04-18 18:59:30 EST EAGLE 39.0
    0010.1490    CARD 1105     INFO    Telnet terminal connection successful.
                 RIPADDR=192.168.210.48
                 RIPORT=3805
                 LIPADDR=192.168.63.116
                 LIPORT=23
                 Report Date:03-01-01  Time:12:41:11
Legend
LIPADDR
Local IP Address
LIPORT
Local TCP Port Number
RIPADDR
Remote IP Address
RIPORT
Remote TCP Port Number

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.458 1491 - Terminal enabled

This message indicates that the specified telnet terminal has been successfully selected by a user via telnet.

Example

RLGHNCXA21W 00-04-18 18:59:30 EST EAGLE 31.3.0
0105.1491 SYSTEM INFO Terminal enabled.
TERMINAL 20

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.459 1492 - Terminal failed

This message indicates that the specified telnet terminal has been disconnected.

Example
RLGHNCXA21W 00-04-18 18:59:30 EST EAGLE 31.3.0
0105.1492 SYSTEM INFO Terminal failed.
TERMINAL 20

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.460 1493 - SSH Host Keys Regenerated

This message indicates that the OA&M IP Security Enhancements feature has successfully generated new host pubic/private key pairs. This occurs during cold restarts of an IPSM card. During initialization, this UIM displays the new key.

Note:

This UIM indicates a new public/private key is in effect. The old key is now invalid. The new key must be installed on SSH clients (on the FTRA) before any connections are permitted.

Example 
RLGHNCXA21W 03-08-18 18:59:30 EST EAGLE 30.2.0
0105.1493 SYSTEM INFO SSH Host Keys Regenerated
DSA Server Host Key FTRA-formatted Fingerprint=
xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Record the DSA Server Host Key FTRA-formatted fingerprint that is in the last line of the UIM.
  2. Save the fingerprint.

    The fingerprint will be installed on the FTRA if the FTP Retrieve and Replace feature is used.

    Note:

    Refer to the FTP-Based Table Retrieve Application (FTRA) User Guide for the fingerprint installation procedure.

3.3.461 1494 - SSH Host Keys Loaded

This message indicates that the OA&M IP Security Enhancements feature has successfully preserved existing host pubic/private key pairs. This occurs during reloads, init-card, and alw-card operations. During initialization, this UIM shows the state of the existing host key.

Example 
RLGHNCXA21W 03-08-18 18:59:30 EST EAGLE 30.2.0
0105.1494 SYSTEM INFO SSH Host Keys Loaded
DSA Server Host Key FTRA-formatted Fingerprint=
xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx xx

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action necessary.

3.3.462 1495 - TCP IPS Message Failure

This UIM occurs when a TCP IPS message Failure has occurred.

Example 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    6729.1495    CARD 1112     INFO    TCP IPS Message Failure
                 Reason: INCORRECT CHECKSUM
                 Connection Name : ipstcp
                 Report Date:18-09-21  Time:16:38:33

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Executing the rtrv-ip-conn:open command should display open=yes. If not, execute the chg-ip-conn command and set open=yes.
  2. Execute the rept-stat-ipconn command and check if the connection is down. Ping the EEDB server, which is added as RHOST for this connection. If the ping response is not received, check the network connection.
  3. Check the error cause to determine why the error occurred; some errors are autocorrected. If not autocorrected, execute the following commands: chg-ip-conn:cname=<>:open=no and chg-ip-conn:cname=<>:open=yes

3.3.463 1496 - EAGLE EEDB Message Failure

This UIM occurs when an EAGLE EEDB Message Failure has occurred.

Example 
7643.1496    CARD 1101     INFO    EAGLE EEDB Message Failure
                 Reason: EEDB RESPONSE TIMEOUT
                 VLR=7171            : STATUS=Whitelist
                 IMSI=69980645
                 Report Date:18-09-21  Time:17:45:33

Alarm Level: No alarm condition. The message is informational only.

Recovery

  1. Executing the rtrv-ip-conn:open command should display open=yes. If not, execute the chg-ip-conn command and set open=yes.
  2. Execute the rept-stat-ipconn command and check if the connection is down. Ping the EEDB server, which is added as RHOST for this connection. If the ping response is not received, check the network connection.
  3. Check the error cause to determine why the error occurred; some errors are autocorrected. If not autocorrected, execute the following commands: chg-ip-conn:cname=<>:open=no and chg-ip-conn:cname=<>:open=yes
  4. check if the maximum TPS limit is exceeded. If so, stop the traffic.

3.3.464 1501 - Visualization connection terminated

This UIM occurs when visualization TCP connection goes down.

Example 
tklc1111101 20-07-08 05:58:08 MST  EAGLE 46.9.0.0.0-76.22.0    
6924.1502    CARD 1111     INFO    Visualization connection terminated                 
Connection Name : conn7                 
Report Date:20-07-08  Time:05:58:08

Alarm Level: No alarm condition. The message is informational only.

Recovery

Verify the remote end (visualization server) availability. However, connection will be established automatically if the remote end is available. Therefore, no action is necessary.

3.3.465 1502 - Visualization connection established

This UIM occurs when visualization TCP connection is established.

Example 
tklc1111101 20-07-08 05:58:00 MST  EAGLE 46.9.0.0.0-76.22.0    
6922.1501    CARD 1211     INFO    Visualization connection established                 
Connection Name : conn7                 
Report Date:20-07-08  Time:05:58:00

Alarm Level: No alarm condition. The message is informational only.

Recovery

No action is necessary.