Multi-Link Manager (MLM) basic concepts.
The MLM driver is a very versatile driver. Originally devised as an intermediate layer to offer switched services for ISDN B-Channels to drivers and protocols that can support only permanent connections, has become an "always present" adaptation driver which provides many extra functions like Dial-on-Demand, Short-Hold-Mode, and true link backup.
MLM driver is the "gate" to:
Within CPX the MLM appears to upper drivers as a single P-LINK port while it is able to use two lower ports of P-LINK and S-LINK types.
The Multi-Link Manager port is referred in the Abilis CPX by the "MLM" abbreviation, it has all the parameters described in the following section.
The layout of the MLM port parameters changes considerably according to the used P-Link and S-Link port types.
Here are some examples of the MLM port parameters.
MLM over SYNC.
[18:42:32] ABILIS_CPX: D P PO:MLM PO:501 ------------------------------------------------------------------------ MLM LOG:NO MPX:YES LC:YES T1:1000 T3:3000 N2:3 CIPHER:NO CRKEY:DFT PLINK:1 SLINK:NONE
MLM over FRAME-RELAY.
PO:502 ------------------------------------------------------------------------ MLM LOG:NO MPX:YES LC:YES T1:1000 T3:3000 N2:3 CIPHER:NO CRKEY:DFT PLINK:102 DLCI:16 CC:YES SC:4 CIR:19200 BC:19200 BE:0 SLINK:NONE
MLM over PLINK-E.
PO:503 ------------------------------------------------------------------------ MLM LOG:NO MPX:YES LC:YES T1:1000 T3:3000 N2:3 CIPHER:NO CRKEY:DFT PLINK:701 SLINK:NONE
MLM over ISDN (over permanent B-Channel).
PO:504 ------------------------------------------------------------------------ MLM LOG:NO MPX:YES LC:YES T1:1000 T3:3000 N2:3 CIPHER:NO CRKEY:DFT PLINK:17 BCHAN:B2 SLINK:NONE
MLM over EIR (PLINK).
PO:505 ------------------------------------------------------------------------ MLM LOG:NO MPX:YES LC:YES T1:1000 T3:3000 N2:3 CIPHER:NO CRKEY:DFT PLINK:200 VSP-ID:10 SLINK:NONE
MLM over EIR (SLINK).
PO:506 ------------------------------------------------------------------------ MLM LOG:NO MPX:YES LC:YES T1:1000 T3:3000 N2:3 CIPHER:NO CRKEY:DFT PLINK:NONE SLINK:200 RTY:LIN NRTY:5 TB:3 DDT:220 VDT:10 CGI:777 SGI:* CDI:* SDI:* CGO:# SGO:# CDO:123 SDO:#
MLM over FRAME-RELAY and EIR.
PO:507 ------------------------------------------------------------------------ MLM LOG:NO MPX:YES LC:YES T1:1000 T3:3000 N2:3 CIPHER:NO CRKEY:DFT PLINK:102 DLCI:16 CC:YES SC:4 CIR:19200 BC:19200 BE:0 SLINK:200 RTY:LIN NRTY:5 TB:3 DDT:220 VDT:10 CGI:777 SGI:* CDI:* SDI:* CGO:# SGO:# CDO:123 SDO:#
MLM over NO LINKS.
PO:508 ------------------------------------------------------------------------ MLM LOG:NO MPX:YES LC:YES T1:1000 T3:3000 N2:3 CIPHER:NO CRKEY:DFT PLINK:NONE SLINK:NONE
By the previous example, it is possible to underline that:
the shown values for the port "501" appear for P-Link port of SYNC type;
the shown values for the port "502" appear for P-Link port of FR type;
the shown values for the port "503" appear for P-Link port of PLINKE type;
the shown values for the port "504" appear for P-Link port of ISDN type;
the shown values for the port "505" appear for P-Link port of EIR (PLINK) type;
the shown values for the port "506" appear for S-Link port of EIR (SLINK) type;
the shown values for the port "507" appear for P-Link port of FR type and S-Link port of EIR (SLINK) type;
the shown values for the port "508" are the default ones.
All the changes made on the MLM port parameters can be immediately activated through the initialization command INIT PO: (this property is underlined by uppercase characters in their name), however it has to be noted that a possible active connection on the S-Link channel is closed with 80 90 80 8A code. The MLM port will immediately be ready for a new communication, without affecting the upper level driver.
The changes made on the parameter LOG: are immediately active.
LOG: | Events logging activation and generation of alarm signals |
DS | NO, D, S, A, L, T, ALL, +E |
Usually this parameter makes possible to activate/deactivate logging functionalities of meaningful events of the port as well as the detection and signalling of alarms in case of critical events.
The following table shows the available options and the related functionalities usable by the parameter:
Option | Meaning |
---|---|
D | Recording of the driver state changes and/or the meaningful events in Debug Log |
S | Recording of the driver state changes and/or the meaningful events in the System Log |
A | Periodic detection of possible alarms. The detected alarms can be displayed the command ALARM VIEW or by the analogous command available on the UTILITY of the LCD display on the front panel |
L | On alarm detection, acoustic signal generation plus a message on the LCD display. This function depends on activation of alarms detection by the "A" option |
T | Generation by the Agent SNMP of Abilis CPX of SNMP traps corresponding to any change of the driver state and/or occurring of meaningful events |
Beside the already described options the following values are also allowed:
Option | Meaning |
---|---|
NO | It means that all the logging functionalities, alarms detection and generation, above mentioned, are disabled. |
ALL | It means that all the logging functionalities, alarms detection and generation, above mentioned, are enabled. |
+E | This option added to one or more of the previous ones, extends its (their) set of meaningful events. The value "ALL+E" activates all the options and extends the set of meaningful events. The value "NO+E" is meaningless so it is ignored. |
Options can be combined together.
Some examples:
By using the characters "+" and "-" as prefix of one or more options is possible to add or delete one or more functionalities without setting from the scratch the value of the parameters.
Some examples:
The changes made on this parameter are immediately activated, without the need of initialization commands.
MPX: | Activation of the Abilis MPX protocol |
YES | NO, YES, EXT |
It makes possible to activate the multiplexing of DATA, "Link-Check", VOICE frames type.
Value | Meaning |
---|---|
NO | Abilis MPX multiplexing is not active. MLM is running in "transparent" mode over the P-LINK interface, as if it would not be there. |
YES | Abilis MPX multiplexing is active only for the data protocols LAPB and LINK-FR. |
EXT | Abilis MPX multiplexing is active for ANY data protocol. |
The activation of the Abilis MPX multiplexing protocol, a proprietary protocol, requires that the counterpart is running MPX as well. It is also necessary that the MPX value is identical for the counterparts.
LC: | Activation of the Abilis MPX Link-check protocol |
YES | NO, YES |
It enables/disables the use of the "Link-Check" protocol, and consequently the transmission of "Link-check" frames.
The link-check protocol is automatically disabled when MPX:NO.
Most of the application have benefits from the Link-check protocol, however there are cases where the generated traffic is not desired while the voice/data multiplexing is still required, as in the cases of VoIP applications with dial-up accesses.
It is also important to note that with LC:NO the "true link backup" is disabled.
Value | Meaning |
---|---|
NO | Link-Check protocol is not active. |
YES | Link-Check protocol is not active. |
T1: | Link-Check "probes" Timeout |
1000 | 200-3000 (in milliseconds) |
Maximum time to wait for a Link-Check "probe" acknowledge. If this time elapses without receiving the acknowledge the "probe" is immediately repeated, as a result "not acknowldged probes" are repeated every T1: milliseconds.
T3: | Time interval between transmission of Link-Check "probes" when link is functioning |
3000 | 600-9000 (in milliseconds) |
This is the time interval between a correctly sent and acknowledged Link-Check "probe" and the next one to send while the link is regularly working (e.g. P-LINK state is READY). It has relationships with the parameter T1: and it has to satisfy the simple rule: T3 > T1 * 2.
N2: | Maximum number of Link-Check "probes" retransmission |
3 | 1 - 99 |
Sets the maximum number of Link-Check "probes" retransmission.
If this counter runs over, it means "N2" Link-Check "probes" have been sent without receiving any acknowledge, the P-Link or S-Link channel is declared out of service.
In the case it occurs on the P-Link channel, the communication will be activated on the S-Link channel, providing that it is properly configured.
In the case it occurs with the S-Link channel, the connection is closed with the code 80 90 80 8B; if it happens three times consecutively the port will be placed in the "STOPPED2" state, without being able to receive or make further calls.
To recover from the error it is necessary to execute the INIT PO: command.
If alarm detection was enabled, i.e. if LOG is set with the "A" option, it is also possible to recover from the error with the ALARM RESET command or using the analogous menu available on the LCD display of the front panel.
If the communication cannot go on any longer either on P-Link or S-Link, the upper level driver will be advised of the error and point out a "Level 1 Down".
CIPHER: | Enable and select cryptography |
NO | NO, DATA, VOICE, ALL |
It enables and selects the cryptography to be applied on the frames passing through the port. Cryptography can be selectively applied to the different traffic types (VOICE and DATA):
Value | Meaning |
---|---|
NO | No cryptography is applied. |
DATA | Cryptography is applied only on DATA traffic type. |
VOICE | Cryptography is applied only on VOICE traffic type. |
ALL | Cryptography is always in use, whatever is the traffic data type. |
CRKEY: | Index of the key used for the cryptography |
DFT | DFT, 1 - 63 |
It selects the key to be used for cryptography operations.
Users can choose either the default key supplied by the system ("CRKEY:DFT"), or one of the keys defined in the cryptography keys table, in which case the numeric value (from 1 to 63) corresponding to the desired CRKEY has to be specified.
If the configured value refers to a missing CRKEY it will be shown inside square brackets, e.g. "CRKEY:[5]" means that the key number 5 is not present in the table.
If the parameter CIPHER: is set to "NO", the value of CRKEY: is useless.
PLINK: | Identifier of the Abilis CPX port of P-Link level |
NONE | 1 - 999, NONE |
It defines the P-Link port of the lower level, which can only be SYNC, FR, ISDN, PLINKE or EIR type.
If no P-Link port is required, the value "NONE" must be set.
BCHAN: | Identifier of the channel B to use (only if the P-Link is an ISDN port type) |
B1 | B1, B2 |
The parameter appears and can be modified only if the port referred by the parameter PLINK: is an ISDN Basic Rate port type, i.e. the service provided by "only data" ISDN adaptors.
It defines the channel to be used on the lower level ISDN port.
DLCI: | Identifier of the DLCI to use (only if the P-Link is a FR port type) |
NONE | 16-991, 1024-63487, 131072-8126463, NONE |
The parameter appears and can be modified only if the port referred by the parameter PLINK: is a FR port type.
It defines the identifier of the DLCI to use the lower lever FR port.
The value "NONE" means "no DLCI" and it disables the connection with the lower level FR port.
The validity of allowed values intervals for the DLCI identifier depends on the length of the header Frame-Relay in use:
Value | Meaning |
---|---|
NO | No cryptography is applied. |
DATA | Cryptography is applied only on DATA traffic type. |
VOICE | Cryptography is applied only on VOICE traffic type. |
ALL | Cryptography is always in use, whatever is the traffic data type. |
CC: | Activation of the congestion control |
YES | NO, YES |
The parameter appears and can be modified only if the port referred by the parameter PLINK: is a FR port type.
It makes possible to apply or to not apply the throughput reduction as reaction to congestion notifications.
Not obeying to congestion notification may cause severe malfunctioning, therefore we strongly reccommend to always use CC:YES. Ignoring congestion notification may be needed for some testing activities, certainly not during the regular work.
SC: | Value of the constant "step count", used in congestion control (only if the P-Link is a FR port type) |
4 | 1 - 50 |
The parameter appears and can be modified only if the port referred by the parameter PLINK: is a FR port type.
It sets how many consecutive frames with BECN=1 have to be received for reducing the throughput, according to the rule fixed by ANSI T1.618 annex A §2.1.1.
Value 4 suits the most frequent situations, however the right value can be evaluated by using the Calculator.
CIR: | Value of "Committed Information Rate" (only if the P-Link is a FR port type) |
0 | 0, 4800 - 2500000 in bit/sec |
The parameter appears and can be modified only if the port referred by the parameter PLINK: is a FR port type.
It defines the value of "Committed Information Rate", i.e. the throughput the frame-relay network has to guarantee in normal working conditions. This throughput is measured in the time interval TC (Time Committed) given by the following formula: TC=BC/CIR.
The set up value must correspond to that one established by contract with the operator of the frame-relay network.
BC: | Value of "Burst Committed" (only if the P-Link port is a FR port type) |
0 | 0, 2400 - 5000000 in bits |
The parameter appears and can be modified only if the port referred by the parameter PLINK: is a FR port type.
It defines the "Burst Committed", i.e. the number of bits the network can accept, during the time interval TC, to guarantee the CIR.
If the network is congested, it sends a signal (BECN or FECN) that require the user to progressively reduce his throughput to values smaller than CIR.
The set up value must correspond to that one established by contract with the operator of the frame-relay network.
BE: | Value of "Burst Excess" (only if the P-Link is a FR port type) |
0 | 0 - 5000000 in bits |
The appears and can be modified only if the port referred by the parameter PLINK: is a FR port type.
It defines the "Burst Excess", i.e. the number of bits in excess that the network can manage, during the time interval TC, if there is availability of exceeding resources. The "exceeding throughput" is evaluated by using the following formula ThExcess=BE*TC.
When the network does not have resources in excess sends a signal (BECN or FECN) that engages the user to immediately limit the throughput to the value of the CIR.
The set up value must correspond to that one established by contract with the operator of the frame-relay network.
VSP-ID: | Service identifier (only if the P-Link is a EIR port type) |
NONE | NONE, 1 - 32 |
This parameter indicates which Virtual Synchronous Port (VSP) of those defined in the TDM table the MLM must use.
SLINK: | Identifier of the Abilis CPX port of S-Link level |
NONE | 1 - 999, NONE |
It defines the S-Link port of lower level, it can be of EIR or Q931 type.
If the S-Link port is not desired, the parameter has to be set to "NONE".
RTY: | Calls repetition rule on failures |
INC | LIN, INC, US |
It allows to select the calls repetition rule on the S-Link channel following an unsuccessful call, and if the attempts are exhausted the S-Link channel is placed in STOPPED1 state.
If the switched connection is established the attempts counter is reset (connection was established!), however if "link-checks" are active a "second level verification" is executed and if it fails the connection is classified as "link-check failure". Three consecitive "link-check failures" forces the S-Link channel in STOPPED2 state preventing any further outgoing or incoming call!
The behaviour upon exhausted attempts is slightly different when RTY:US, see below or details.
Value | Calls repetition rules |
---|---|
LIN | The time interval between a call attempt and the next one is
fixed and configurable through the parameter TB:. |
INC | The time interval between a call attempt and the next one, is doubled at every attempt, starting with the value defined in the parameter TB:. |
US | The abbreviation "US" stands for "unattended site". In this case the S-Link channel driver activates the following procedure until success:
It is important to emphasize that points 2,3,4,5,6 of the procedure do not distinguish between failure's reason (connection not established or connection established with "link-check" error) until the last attempt is reached and the last failure reason is used to set the final state (STOPPED1 or STOPPED2). |
NRTY: | Maximum number of call repetitions |
5 | 0 - 65534, NOMAX |
It specifies the maximum number of call repetitions for the S-Link channel when the connection cannot be established. Once attempts are exhausted the S-Link chennel is place in STOPPED1 state.
If the channel is established BUT the "link-check protocol" detects link-check failure for three times consecutively the port is placed in STOPPED2 state regardless the NRTY counter.
The behaviour upon exhausted attempts is slightly different when RTY:US.
Value | Meaning |
---|---|
0 | Outgoing calls are disabled. |
1-65534 | Calls are repeated as many times as the value. |
NOMAX | Calls are repeated indefinitely. For "RTY:INC" the time interval of calls after the 65535th will not increase further, keeping the interval TB: * 65535 seconds. For "RTY:US" the actual behaviour is identical to RTY:LIN because the condition that starts the "unattended site retries" will not be reached. |
TB: | Time base interval between calls repetitions |
3 | 3 - 255 (in seconds) |
It defines the "base" time interval that the retry procedure set in RTY: uses to calculate the delay between a call attempt that fails and the next one.
DDT: | Data disconnect timeout |
220 | from 10 up to 65535 (in seconds) |
After "DDT:" seconds from the last sent or received "data" frame the S-LINK connection will be closed, unless "voice" frames still need the connection.
The disconnection actually occur when both DDT: and VDT: expire.
VDT: | Voice disconnection timeout |
10 | from 5 up to 900 (in seconds) |
After "VDT:" seconds from the last sent or received "voice" frame the S-LINK connection will be closed, unless "data" frames still need the connection.
The disconnection actually occur when both DDT: and VDT: expire.
CGI: | Calling address of the incoming call |
* | from 1 up to 20 numerical characters [0- 9], * |
It sets up the calling address, that the incoming call must contain.
The character "*" means "any number".
SGI: | Calling sub-address of the incoming call |
* | from 1 up to 20 alphanumerical [0- 9, a - z, A- Z], * |
It sets up the calling sub-address, that the incoming call must contain.
The character "*" means "any character".
CDI: | Called address of the incoming call |
* | from 1 up to 20 numerical characters [0- 9], * |
It sets up the called address, that the incoming call must contain.
The character "*" means "any number".
SDI: | Called sub-address of the incoming call |
* | from 1 up to 20 alphanumerical [0- 9, a - z, A- Z], * |
It sets up the called sub-address, that the incoming call must contain.
The character "*" means "any character".
CGO: | Calling address of the outgoing call |
# | from 1 up to 20 numerical characters [0- 9], # |
It sets up the calling number of the outgoing call.
The character "#" means "no number", if it is set, the outgoing call will not contain the calling address.
SGO: | Calling sub-address of the outgoing call |
# | from 1 up to 6 alphanumerical [0- 9, a - z, A- Z], # |
It sets up the calling sub-address of the outgoing call.
The character "#" means "no number", if it is set, the outgoing call will not contain the calling sub-address.
CDO: | Called address of the outgoing call |
# | from 1 up to 20 numerical characters [0- 9], # |
It sets up the called number of the outgoing call.
The character "#" means "no number", if it is set, the outgoing call will not contain the called address.
SDO: | Called sub-address of the outgoing call |
# | from 1 up to 6 alphanumerical [0- 9, a - z, A- Z], # |
It sets up the called sub-address of the outgoing call.
The character "#" means "no number", if it is set, the outgoing call will not contain the called sub-address.
Example of how to check the state and statistics of MLM ports by the command D S
[18:42:32] ABILIS_CPX: D S PO:501 PO:501 ------------------------------------------------------------------------ MLM +--------+--- Global ----+------- P-Link -------+------- S-Link -------+ | STATE: | READY | READY | LINK-NOT-PRESENT | +--------+---------------+----------------------+----------------------+ PLINK-DN1:1 PLINK-DN2:1 SLINK-ST1:0 SLINK-ST2:0 TIME-CUR-CALL:0 RTY:0 DDT:0 VDT:0 USRTY:0 TDEL:0 TREM:0 -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---| FAIL-CALL | 0| 0|SUCC-CALL | 0| 0| TIME-CALL | 0| 0| | | | V-NO-CRKEY | 0| 0|D-NO-CRKEY | 0| 0| V-BAD-CIPH | 0| |D-BAD-CIPH | 0| | ------------------------------------------------------------------------
The MLM ports have not extended statistics, that's why the execution of the command D SE will show again the not extended ones in the following format:
[18:42:32] ABILIS_CPX: D SE PO:501 PO:501 ------------------------------------------------------------------------ MLM --- Cleared 028:00:15:01 ago, on 14/04/2000 at 11:05:34 ---------------- PLINK-DN1:1 PLINK-DN2:1 SLINK-ST1:0 SLINK-ST2:0 TIME-CUR-CALL:0 -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---| FAIL-CALL | 0| 0|SUCC-CALL | 0| 0| TIME-CALL | 0| 0| | | | V-NO-CRKEY | 0| 0|D-NO-CRKEY | 0| 0| V-BAD-CIPH | 0| |D-BAD-CIPH | 0| | ------------------------------------------------------------------------
The information "Cleared DDD:HH:MM:SS ago, at DD/MM/YYYY HH:MM:SS", referred by the extended statistics, shows both the elapsed time from the last reset of the statistics (by the format "days:hours:minutes:seconds") and date/time of its execution (by the format "day/month/year" and "hours:minutes:seconds").
Global STATE: | Global current state |
READY, DOWN, ERR |
It reports the global current state, as seen by the upper port (e.g. IPRTR, LPAB, etc ...):
Driver | States | Meaning |
---|---|---|
MLM (Global) | READY | MLM is READY and usable. |
DOWN | MLM is DOWN. | |
ERR | Software error. Contact Abilis service. |
P-Link STATE: | P-Link channel current state |
READY, LINK-NOT-PRESENT, DOWN1, DOWN2, ERR |
It reports the P-Link channel current state:
Driver | States | Meaning | Values reported into: | ||
---|---|---|---|---|---|
System Log | Events Log | LCD display | |||
MLM (P-Link) |
READY | The P-Link is ready and usable. | RD | ||
LINK-NOT-PRESENT | The value configured in PLINK: does not refer to a valid or running port. | ln | |||
LINK-ERROR | The port configured in PLINK: is a valid and running port, however there are problems with
other parameters. E.g. when MLM uses a frame relay port and it tries to use a DLCI already used, require an unacceptable CIR, etc... |
le | |||
DOWN1 | P-Link channel is down because of a DOWN state in the lower protocol driver, as in the case of SYNC port with CD:YES and current DCD state is DOWN. | d1 | |||
DOWN2 | P-Link channel is down because the "link-check protocol" detected a failure, while the state in the lower protocol driver is "UP". | d2 | |||
ERR | Software error. Contact Abilis service. | NA |
S-Link STATE: | S-Link channel current state |
READY, READY-DELAY, CALLING, CALLED, CONNECTED TO, CONNECTED FROM, CLEARING, CLEARED, LINK-NOT-PRESENT, STOPPED1, STOPPED2, US-DELAY, ERR |
It reports the S-Link channel current state:
Driver | States | Meaning | Values reported into in: | ||
---|---|---|---|---|---|
System Log | Events Log | LCD Display | |||
MLM (S-Link) |
READY | The S-Link is ready and usable. | RD | ||
READY-DELAY | The S-Link channel is ready to receive a call but not to place it. It is executing a delay because of a previous call attempt failure. | ||||
CALLING | A call is outgoing. Waiting for call acceptance or call refusal. | ||||
CALLED | A call is incoming. Waiting to accept/refuse the call. | ||||
CLEARING | A call disconnection has been generated from the local MLM. Waiting for completion of the disconnection procedure. | ||||
CLEARED | A disconnection request has been received. Waiting to complete the disconnection procedure. | ||||
US-DELAY | The S-Link channel is in the "unattended site" procedure and it is executing the delay before the next attempt. It can appear only if RTY:US. | ||||
CONNECTED-TO | it is connected as a result of one outgoing call. | CN | |||
CONNECTED-FROM | it is connected as a result of one incoming call. | CN | |||
LINK-NOT-PRESENT | The value configured in SLINK: does not refer to a valid or running port. | ln | |||
STOPPED1 | The S-Link channel exhausted the call retry attempts that was configured through RTY: and NRTY: parameters. Further outgoing calls are not possible while incoming calls can be accepted. This error condition can be reset with the INIT PO: command or, if alarm is active, with either the ALARM RESET command or the analogous menu available on the LCD display of the front panel. |
s1 | |||
STOPPED2 | The "link-check protocol" detected three consecutive failures on either incoming or outgoing calls. Both outgoing and incoming calls are not anymore possible. This error condition can be reset with the INIT PO: command or, if alarm is active, with either the ALARM RESET command or the analogous menu available on the LCD display of the front panel. |
s2 | |||
ERR | Software error. Contact Abilis service. | NA |
PLINK-DN1: | Number of times that P-Link channel reached the DOWN1 state |
0 - 4.294.967.295 |
The counter PLINK-DN1 reports the number of times the P-Link channel reached the DOWN1 state.
PLINK-DN2: | Number of times that P-Link channel reached the DOWN2 state |
0 - 4.294.967.295 |
The counter PLINK-DN2 reports the number of times the P-Link channel reached the DOWN2 state.
SLINK-ST1: | Number of times that S-Link channel reached then STOPPED1 state |
0 - 4.294.967.295 |
The counter SLINK-ST1 reports the number of times that S-Link channel reached the STOPPED1 state.
SLINK-ST2: | Number of times that S-Link channel reached the STOPPED2 state |
0 - 4.294.967.295 |
The counter SLINK-ST2 reports the number of times that S-Link channel reached the STOPPED2 state.
TIME-CUR-CALL: | Duration of the current connection |
0 - 4.294.967.295 |
The counter TIME-CUR-CALL reports the overall duration of the current connection.
RTY: | Number of reattempt of the current call |
0 - NRTY |
The counter RTY reports the number of reattempt of the current call, as used by RTY:LIN/INC/US procedures.
DDT: | Number of seconds to go for the channel disconnecion by "DATA frames inactivity". |
60 - 65535 (in seconds) |
The counter DDT shows how many seconds to go for the channel disconnecion by "DATA frames inactivity".
The channel will be actually disconnected when both DDT: and VDT: values will reach 0.
VDT: | Number of seconds to go for the channel disconnecion by "VOICE frames inactivity". |
1 - 900 (in seconds) |
The counter VDT shows how many seconds to go for the channel disconnecion by "VOICE frames inactivity".
The channel will be actually disconnected when both DDT: and VDT: values will reach 0.
USRTY: | Number of reattempt in modality "Unattended Site" |
0 - 65.535 |
The counter USRTY reports the number of reattempt in modality "Unattended Site" (parameter RTY:US).
TDEL: | S-Link channel: seconds elapsed since entering the READY-DELAY state |
0 - 65.535 (in seconds) |
The counter TDEL reports the seconds elapsed since the S-Link channel entered the READY-DELAY state.
TREM: | S-Link channel: seconds to go to move from READY-DELAY to READY state |
0 - TDEL (in seconds) |
The counter TREM reports the seconds to go before the S-Link channel leaves the current READY-DELAY state and enters the READY one.
FAIL-CALL | Number of incoming/outgoing calls failed |
0 - 4.294.967.295 |
The counter FAIL-CALL (INPUT) reports the number of incoming calls failed.
The counter FAIL-CALL (OUTPUT) reports the number of outgoing calls failed.
SUCC-CALL | Number of incoming/outgoing calls successful |
0 - 4.294.967.295 |
The counter SUCC-CALL (INPUT) reports the overall number of incoming call successful.
The counter SUCC-CALL (OUTPUT)reports the overall number of outgoing calls successful.
TIME-CALL | Duration of connections caused by incoming/outgoing calls |
0 - 4.294.967.295 |
The counter TIME-CALL (INPUT) reports the overall duration of those connections caused by incoming calls.
The counter TIME-CALL (OUTPUT) reports the overall duration of those connections caused by outgoing calls.
V-NO-CRKEY | Number of VOICE frames discarded because of missing CRKEY. |
0 - 4.294.967.295 |
The counter V-NO-CRKEY (INPUT) is incremented every time a VOICE frame is received, but it is not decryptable because the index of the cryptographic key, set in the parameter CRKEY:, refers to a non-existent cipher key.
The counter V-NO-CRKEY (OUTPUT) is incremented every time a VOICE frame is received from the upper level, but it is not encryptable because the index of the cryptographic key, set in the parameter CRKEY:, refers to a non-existent cipher key.
V-BAD-CIPH | Number of discarded VOICE frames because of decryption failure |
0 - 4.294.967.295 |
The counter V-BAD-CIPH (INPUT) is incremented every time a received VOICE frame must be discarded because the decryption failed. This can be caused by:
D-NO-CRKEY | Number of DATA frames discarded because of missing CRKEY. |
0 - 4.294.967.295 |
The counter D-NO-CRKEY (INPUT) is incremented every time a DATA frame is received, but it is not decryptable because the index of the cryptographic key, set in the parameter CRKEY:, refers to a non-existent cipher key.
The counter D-NO-CRKEY (OUTPUT) is incremented every time a DATA frame is received from the upper level, but it is not encryptable because the index of the cryptographic key, set in the parameter CRKEY:, refers to a non-existent cipher key.
D-BAD-CIPH | Number of discarded DATA frames because of decryption failure |
0 - 4.294.967.295 |
The counter D-BAD-CIPH (INPUT) is incremented every time a received DATA frame must be discarded because the decryption failed. This can be caused by:
The SNMP Agent of Abilis CPX is able to generate traps owing to meaningful state changes pertinent either to P-Link or S-Link channel of the MLM.
The traps listed below are generated when the "T" option is set in the LOG: parameter.
Trap own code | Mnemonic of the trap | SNMP variables reported in the trap | Description |
---|---|---|---|
1 | cxTrapPLinkDown | cxPortIndex, cxPortType, cxMlmDiagPLinkState, cxMlmDiagSLinkState, sysUpTime |
The SNMP Agent of the Abilis CPX generates this kind of trap every time the P-Link channel of the MLM goes into the DOWN1 state or DOWN2 state. |
2 | cxTrapPLinkReady | cxPortIndex, cxPortType, cxMlmDiagPLinkState, cxMlmDiagSLinkState, sysUpTime |
The SNMP Agent of the Abilis CPX generates this kind of trap every time the P-Link channel of the MLM leaves the DOWN1 state or DOWN2 state. |
The traps listed below are generated when the "T" option is set in the LOG: parameter.
Trap own code | Mnemonic of the trap | SNMP variables reported in the trap | Description |
---|---|---|---|
3 | cxTrapSLinkStopped | cxPortIndex, cxPortType, cxMlmDiagPLinkState, cxMlmDiagSLinkState, sysUpTime |
The SNMP Agent of the Abilis CPX generates this kind of trap every time the S-Link channel of the MLM goes into the STOPPED1 state or STOPPED2 state. |
4 | cxTrapSLinkReady | cxPortIndex, cxPortType, cxMlmDiagPLinkState, cxMlmDiagSLinkState, sysUpTime |
The SNMP Agent of the Abilis CPX generates this kind of trap every time the S-Link channel of the MLM leaves the STOPPED1 state or STOPPED2 state. |
5 | cxTrapSLinkUSStart | cxPortIndex, cxPortType, cxMlmDiagPLinkState, cxMlmDiagSLinkState, sysUpTime |
The SNMP Agent of the Abilis CPX generates this kind of trap every time the repetition calls procedure, specified in the parameter RTY:, if set to the value "US", starts on the S-Link channel of the MLM port. |
cxPortIndex | FR port, which the SNMP trap refers to |
0 - 999 |
This variable stores the CPX port number, which the SNMP trap refers to.
cxPortType | Type and description of the MLM port, which the trap refers to |
type - description |
This variable reports either the port type which the trap refers to (in this case it will be MLM) and the description that eventually the user can give to the CPX port.
cxMlmDiagPLinkState | P-Link channel current state |
ready(0), link-not-present(1), link-error(2), down1(3), down2(4) |
This variable reports the current state of the P-Link channel, which the trap refers to. The following table shows the relationship between the state values, referred by the SNMP variables, and the states carried out by executing the command D S.
SNMP variable value | P-Link channel corresponding state |
---|---|
ready(0) | READY |
link-not-present(1) | LINK-NOT-RESENT |
link-error(2) | LINK-ERROR |
down1(3) | DOWN1 |
down2(4) | DOWN2 |
cxMlmDiagSLinkState | S-Link channel current state |
ready(0), ready-delay(1), calling(2), called(3), connected(4), clearing(5), cleared(6), link-not-present(7), stopped1(8), stopped2(9), us-delay(10) |
This variable reports the current state of the S-Link channel, which the trap refers to. The following table shows the relationship between the state values, referred by the SNMP variables, and the states carried out by executing the command D S.
Value of the SNMP variable | Corresponding state of the S-Link channel |
---|---|
ready(0) | READY |
ready-delay(1) | READY-DELAY |
calling(2) | CALLING |
called(3) | CALLED |
connected(4) | CONNECTED |
clearing(5) | CLEARING |
cleared(6) | CLEARED |
link-not-present(7) | LINK-NOT-PRESENT |
stopped1(8) | STOPPED1 |
stopped2(9) | STOPPED2 |
us-delay(10) | US-DELAY |
sysUpTime | Elapsed time since the system has been started by the occurred event |
0 - 4.294.967.295 or "ddd:hh:mm:ss" |
This variable reports the elapsed time (in cents of second) since the occurred event, which has generated the SNMP, started the system. This value is usually shown by using the format days:hours:minutes:seconds.