Contents | Index | Previous | Next

STAT MSDL (x (Full))

msdl-18

Get MSDL status.

This command outputs the status of MSDL cards. Without any optional parameters (no card number, etc.), the status of all MSDL cards in the system is output.

When a card number alone is provided with the command, the status of the card is output along with additional information regarding the applications configured on the card.

Specifically, for each D-channel or AML configured on the card, the application name, logical number and port status is output.

For example:

MSDL x: ENL
AML 11 DIS PORT 1
DCH 25 OPER PORT 2
AML 03 OPER PORT 3

msdl-24

With Release 24 and later, the status output will include the overloaded state of the individual ports. The benefit, individual ports with a high incoming message rate will be locked-out, operation of the other ports will be unaffected.

Prior to Release 24, one overloaded port would disable the MSDL card.

For example:

MSDL x: ENL
SDI 7 OVLD PORT 0
AML 11 DIS PORT 1
DCH 25 OPER PORT 2
AML 03 OPER PORT 3

If the FULL option is entered along with the MSDL number, the Meridian 1 outputs all the information output for the ’STAT MSDL x’ command along with the following additional information:

— card ID

— bootload firmware version

— basecode version

— basecode state

— when the basecode was activated (if it is active)

— each application version

— each application state

— when each the application was activated (if it is active)

The card status is output on the first line and can be any one of the following:

MSDL x: ENBL - card is enabled

MSDL x: MAN DSBL - card disabled by the DIS MSDL command

MSDL x: SYS DSBL reason - card has been disabled by the system

The system disabled state may be due to any of the following:

  1. SYS DSBL- NOT RESPONDING

• If the MSDL is in this state, the implication is that the Meridian 1 has attempted to communicate with the MSDL and was not successful. It is possible that the card is not present in the shelf. If it is present, then it is possible that the software on the card is unable to respond to messages from the Meridian 1.

• Action: Check to see if the card is properly inserted in its slot. If it is (and has been for more than a few minutes), then check the console output for MSDL or ERR messages and take the appropriate action for the error message.

• It may be that the rotary switch setting on the MSDL card is not set properly. To keep the Meridian 1 from continuously attempting recovery of the MSDL, use the ’DIS MSDL x’ command to put the card in the Manually Disabled (MAN DSBL) state.

  1. SYS DSBL- SELF-TESTING

• If the MSDL is in this state, self-tests are in progress.

• Action: Wait for self-tests to complete and for the Meridian 1 to examine the results. Under normal circumstances, self-tests take less than one minute to complete. However, when an erasable EPROM on the card has been cleared, self-tests may take between five and six minutes to complete. Therefore, it is prudent not to take any action at this time.

  1. SYS DSBL- SELF-TESTS PASSED

• This is a transient state. A card in a transient state has successfully completed self-tests and the Meridian 1 either is about to begin downloading the MSDL base software, or has just completed downloading the MSDL base software and is about to attempt to enable the card.

• Action: Wait for the Meridian 1 to begin the next step of recovery. If a more immediate recovery is desired, use the ’DIS MSDL x’ command followed by the ’ENL MSDL x’ command. This causes essentially the same recovery action to be taken. However, it may be faster (since it is being done as a result of input from the craftsperson).

  1. SYS DSBL- SELF-TESTS FAILED

• If the MSDL is in this state, self-tests have executed and failed on this card.

• Action: Use the ’STAT MSDL x’ command to determine reason for self-test failure. Disable the MSDL card using the ’DIS MSDL x’ command, then use the ’SLFT MSDL x’ command to execute the self-tests again.

• If the self-tests pass, attempt to enable the card using the ’ENL MSDL x’ command. If the card fails the self-tests again, record the results and replace the card.

  1. SYS DSBL- SRAM TESTS FAILED

• If the MSDL is in this state, self-tests have executed and passed, however when the Meridian 1 attempted to perform read/write tests to the shared RAM on the MSDL, it detected a failure.

• Action: Same as for self-test failure. If the attempt to enable the card fails, record the results and replace the card.

  1. SYS DSBL- OVERLOAD

• The Meridian 1 has received too many messages from the MSDL. This is considered to be unacceptable, in that this much of a demand may interfere with other system functions.

• Action: If the MSDL is left in this state, the Meridian 1 will attempt to bring the card back into service within a few minutes. If this is not desired, disable the card using the ’DIS MSDL x’ command.

• It is also advisable to identify a specific port or application that may be responsible for the overload. The identification can be made by disabling individual links/ports on the MSDL and letting the remaining links/ports operate normally.

  1. SYS DSBL- RESET THRESHOLD

• If the MSDL is in this state, the Meridian 1 has detected more than four resets within ten minutes. This is considered to be unacceptable, as a normally operating card should not reset so often.

• It is possible that the card may be in this state due to a Fatal Error or Self-test failure from which no recovery was successful. (As the recovery from Fatal Errors and Self-test failures begins with resetting the card, repeated attempts at recovery may cause the reset threshold to be reached.)

• Action: Disable the card using the ’DIS MSDL x’ command and execute the ’SLFT MSDL x’ command. If self-tests pass, attempt to enable the card using the ’ENL MSDL x’ command. If the problem recurs, try force downloading the software to the MSDL using the ’ENL MSDL x FDL’ command.

• If the problem continues to recur and resets continue because of a repeated fatal error, attempt to isolate the problem by disabling all links/ports controlled by one application (e.g., all D-channels or all AMLs). If no manual intervention is taken by the craftsperson, the Meridian 1 will attempt to bring the card back into service beginning at midnight.

  1. SYS DSBL- FATAL ERROR

• If the MSDL is in this state, the card encountered a fatal condition from which it could not recover. In response to the ’STAT’ command, the cause of the fatal error will be displayed.

• If the ’STAT’ command is not entered while the card is in this state, the MSDL302 message printed at the time of the state transition will indicate the cause of the fatal error.

• Action: The Meridian 1 will attempt to bring the card back into service automatically. While the card is in this state, it is recommended that the craftsperson do nothing. If the Meridian 1 is unable to recover the card, the system disabled substate will be changed to indicate the reason recovery was not possible. The craftsperson should then take the recommended action for that new substate.

  1. SYS DSBL- NO RECOVERY ATTEMPTED UNTIL MIDNIGHT

• When this is output after the SYS DSBL message, the Meridian 1 has attempted to recover the card but has repeatedly failed. One example of this condition is when the background recovery mechanism has failed to download the MSDL Base Code five times in a row.

• Action: Disable the card using the ’DIS MSDL x’ command, test the card using the ’SLFT MSDL x’ command, and if self-tests pass, enable the card using the ’ENL MSDL x’ command.

• If downloading of the MSDL Base Code is necessary, it will be attempted in response to the enable command. If no manual intervention is taken, the Meridian 1 will again attempt recovery beginning at midnight.