|
|
In order to manage I/O Signal Channels, the user needs the ability to call these channels from the database. This is done using the MML commands. The MML command RTRV-SC displays the names and attributes of the I/O signaling channels and identifies the associated signaling channel used for the conversion.
The RTRV-SC MML command displays the name and attribute for a specific I/O signaling channel, and identifies the associated signal channel used for the conversion. Use the following command syntax:
mml>RTRV-SC:<sigPath>
The name of the signaling channel being retrieved is <sigPath>. For example:
mml> RTRV-SC:T-1-1
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 15:12:46 M RTRV "T-1-1:PKG=DPNSS,ASSOC=T-1-16 ,PST=IS" ;
In this example, T-1-1 is the specific I/O signaling channel, and DPNSS is the provisioned protocol. The associated signaling channel used for the conversion is T-1-16, and IS indicates that it is in service.
There are two signaling channel states:
IS | In-Service |
OOS | Out-of-Service |
To display names and attributes of all I/O signaling channels and identify the associated signal channels used for the conversions, use the following command:
mml> RTRV-SC:ALL
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 15:15:18 M RTRV "T-1-16:PKG=Q931ETSI,ASSOC=T-1-1 ,PST=IS" "T-1-1:PKG=DPNSS,ASSOC=T-1-16 ,PST=IS" "T-2-16:PKG=Q931ETSI,ASSOC=T-2-1 ,PST=IS" "T-2-1:PKG=DPNSS,ASSOC=T-2-16 ,PST=IS" ;
A signaling channel can be set to one of four states listed in the following table.
In-Service (IS) | Link is available for calls to be placed. |
Out-Of-Service (OOS) | Link is made unavailable for calls to be placed after last active calls terminate. |
Inhibit (INH) | Datalink is established but no calls are processed by the Engine. This option is used to test link integrity and reliability. If there is only one channel in the link set which is uninhibited, it can not be inhibited until the other channel is back in service. |
Uninhibit (UNH) | Places the link back in service |
To change the status of a specific signaling channel from one service state to another state, use any of these MML command options.
There are four Out-of-Service options: Out-of-Service, Forced Out-of-Service, Manually Out-of-Service, and Automatically Out-of-Service.
Out-of-Service (OOS) | Allows in process calls to terminate before the channel is removed from service |
Forced Out-of-Service (FOOS) | Abruptly terminates calls and the channel is immediately taken out of service |
Manually Out-of-Service (MOOS) | User sets the channel out-of-service |
Automatically Out-of-Service (AOOS) | System recognizes that there is problem with the channel and takes it out-of-service |
To set a signaling channel to any of these states, enter the following command:
mml>SET-SC-STATE:<sigPath>:<state>
The name of the signaling channel being retrieved is <sigPath>, and the name of the service state you want to set is <state>. Enter the name of the signaling channel being retrieved. For example, to set a signaling channel to Out-Of-Service (OOS), use the following command:
mml>SET-SC-STATE:<sigPath>:oos
The name of the signaling channel being set to OOS is <sigPath>. Enter the name of the signaling channel to be set. For example:
mml>SET-SC-STATE:T-1-1:OOS
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 16:09:37 M COMPLD ;
For further explanation of this procedure, see "MML Commands."
To set a signaling channel to In-Service (IS), use the following command:
mml> SET-SC-STATE:<sigPath>:IS
The name of the signaling channel being retrieved is <sigPath>. Enter the name of the channel being retrieved. For example:
mml> SET-SC-STATE:T-1-1:IS
Sample Response:
CONFIG01/BUILD 13.6 97-05-15 16:09:48 M COMPLD ;
For further explanation for this procedure see "MML Commands."
To retrieve traffic channel states, enter the following MML Command:
mml>RTRV-TC:<sigPath>
The MML command rtrv-tc:<sigPath> displays the number and status of all traffic channels for a signaling channel. The name of the signaling channel being retrieved is <sigPath>. Enter the name of the signaling channel being retrieved. For example:
mml> RTRV-TC:T-2-1
Sample Response:
CONFIG01/REL 1.1 97-08-28 18:00:32 M RTRV "T-2-1:1=is, 2=is, 3=is, 4=is, 5=is, 6=is, 7=is, 8=is, 9=IS,10=IS,11=IS,12=OOS,13=IS,14=IS,15=OOS,16=IS,17=IS, 18=IS,19=IS,20=IS,21=IS,22=IS,23=IS,24=IS,25=IS,26=IS, 27=IS,28=IS,29=IS,30=IS,31=IS";
Enter the MML command RTRV-ALMS to retrieve all active alarms from the Alarm Manager. The alarm category retrieved is contained in the last two characters on the response line. Major is MJ, minor is MN, and critical is CR. Informational alarms are not retrievable. The following is an example of the RTRV-ALMS command:
mml> RTRV-ALMS
Sample Response:
ALARM01 97-05-01 07:46:38 M RTRV "T-1-16:SC FAIL,MJ" "T-2-16:SC FAIL,MJ" ; mml>
| ALARM NAME | ALARM CATEGORY | SECTION |
|---|---|---|
CHAN BAD TOT 15 | 15 Minute Information Alarm | |
CHAN BAD TOT 24 | 24 Hours Information Alarm | |
CHAN BAD TOT 60 | 60 Minute Information Alarm | |
CHAN LINK ESTAB 15 | 15 Minute Information Alarm | |
CHAN LINK ESTAB 24 | 24 Hours Information Alarm | |
CHAN LINK ESTAB 60 | 60 Minute Information Alarm | |
IO CARD | Major Alarm | |
LIF FAIL | Major Alarm | |
LIF LOF | Major Alarm | |
LIF LOS | Major Alarm | |
LIF SES 15 | Information Alarm | |
LIF SES 24 | Information Alarm | |
LIF SES 60 | Information Alarm | |
LIF YELLOW | Minor Alarm | |
SC CONFIG FAIL | Major Alarm | |
SC FAIL | Major Alarm | |
SC M-OOS | Minor Alarm | |
SUPPORT FAIL | Minor Alarm |
Alarm cause | The Signal Channel is down due to a support element failure. |
Recovery action | Investigate the associated alarms. Check the network transport facilities. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm cause | The E1/IO card has failed operations. |
Recovery action | Verify that the Card is properly installed and that all associated support software is resident and configured correctly. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm cause | The signaling channel is down and unable to process traffic. The channel is failing to negotiate a D channel session. Automatic restarts are also not able to recover the session. |
Recovery Action | Attempt to manually reset the channel using the MML command SET-SC-STATE to stop and restart the channel. Investigate distant end switching systems signal channel status, and coordinate channel return to service with them. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm Cause | The database parameters for the signal channel are not compatible with the distant ends channel parameters, and the data channel will not initialize to an "In-Service" state (level 3). |
Recovery Action | Check the database to make sure both ends of the circuit have been provisioned correctly. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm Cause | The signal channel has been manually taken out of service by an operator on the platform. |
Recovery Action | None, except for confirming the disposition with site operations, etc. The circuit can be returned to service via the MML command |
Alarm Cause | The distant end facilities are reporting a loss of the receive signal at their end. |
Recovery Action | Advise the distant end of the error condition and take appropriate steps to return the transport facilities to an operational state. See "Alarm Support Diagrams". |
Alarm Cause | The Identified T1/E1 is not operational and is down. |
Recovery Action | Check the T1/E1 network facilities for loss of T1/E1 source. Note: other associated alarms may be generated under this condition as part of the T1/E1 failure. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm Cause | The transport signal receive end has been lost in the T1/E1. |
Recovery Action | Take appropriate action to restore the end to end carrier facilities to an operational state. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm Cause | A loss of T1/E1 framing has been detected on the LIF. |
Recovery Action | Take appropriate action to restore the end to end carrier facilities to an operational state. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm Cause | The severe error seconds measurement counter has exceeded the threshold value set in the |
Recovery Action | If this problem persists in the next consecutive 15 minute intervals, remove the signal channel from service and investigate the conditioning equipment. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm Cause | The severe error seconds measurement counter has exceeded the threshold value set in the |
Recovery Action | If this problem persists in the next consecutive 15 or 60 minute intervals, remove the signal channel from service and investigate the conditioning equipment. Once the T1/E1 connectivity has been checked, restore the channel to an "In-Service" state and monitor the measurement statistics for recurring errors. See "Alarm Support Diagrams." |
Alarm Cause | The severe error seconds measurement counter has exceeded the threshold value set in the |
Recovery Action | If this problem persists in the next 24 hour interval, the signal channel should be removed from service and the conditioning equipment investigated. Once the T1/E1 connectivity has been checked, restore the channel to an "In-Service" state and continue to monitor the measurement statistics for recurring errors on the error signal channel. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm Cause | The number of bad HDLC frames received on this channel (DS-0 time slot) has exceeded the threshold value set in the |
Recovery Action | If this problem persists in the next consecutive 15 minute intervals, remove the signal channel from service and investigate the conditioning equipment. See "Alarm Support Diagrams." |
Alarm Cause | The number of bad HDLC frames received on this channel (DS-0 time slot) has exceeded the threshold value set in the |
Recovery Action | If this problem persists in the next consecutive 15 minute interval, remove the signal channel from service, and investigate the conditioning equipment. See "Alarm Support Diagrams." |
Alarm Cause | The number of bad HDLC frames received on this channel (DS-0 time slot) has exceeded the threshold value set in the |
Recovery Action | If this problem persists in the next 15 minute interval, remove the signal channel from service and investigate the conditioning equipment. See "Alarm Support Diagrams." |
Alarm Cause | The number of resets on this channel (DS-0) has exceeded the threshold value set in the |
Recovery Action | If this problem persists in the next 15 minute interval, remove the signal channel from service and investigate the network support equipment or distant end switching system. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm Cause | The number of resets on this channel (DS-0) has exceeded the threshold value set in the |
Recovery Action | If this problem persists in the next 15 minute intervals, remove the signal channel from service and investigate the network support equipment or distant end switching system. See "Alarm Support Diagrams" for method of resolving this alarm. |
Alarm Cause | The number of resets on this channel (DS-0) has exceeded the threshold value set in the |
Recovery Action | If this problem persists in the next 15 minute interval, remove the signal channel from service and investigate the network support equipment or distant end switching system. See "Alarm Support Diagrams" for method of resolving this alarm. |
|
|