The HDLCT ports provide a simple service of HDLC frames "transparent transport" to their destination, they do not manage any acknowledgement procedure. It means, for a correct use of this service, proper transmission timeouts have to be set.
The HDLC transparent port is labelled within the Abilis CPX with the acronym "HDLCT" and it is provided with the parameters described in this section.
Here is an example on how to display the HDLCT port parameters. Shown values are the default ones.
[15:03:33] ABILIS_CPX: D P PO:341 .
PO:341 ------------------------------------------------------------------------
HDLCT LOG:ALL lowpo:1 TYPE:USER MCAU:NO ps:2048 vc:BSVC
n1:2100 AC:NO RTY:INC TB:6 NRTY:1 DT:0
rxbuf:1 txbuf:14
To activate changes made on the parameters displayed by low case characters, it is needed to restart the system; on the contrary for activating changes made on low case parameters it is enough to execute the initialisation command INIT PO:. 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.
| LOWPO: | Identifier of the Abilis CPX lower level port |
| NONE | 1 - 999, NONE |
It sets the Abilis CPX lower level port.
The value "NONE" isolates the HDCLT port from the lower level ones.
| TYPE: | Port type |
| USER | USER |
The port connected to the network is defined NETWORK port; the one connected to the user equipment USER port.
The NETWORK port sends compressed data and expands the received ones; the USER port compresses the received data and sends the expanded ones.
The HDLCT port can be only USER.
| MCAU: | Cause code modification in CLEAR packets sent |
| NO | NO, YES |
If MCAU is set to NO, Abilis CPX transports, without any changes, the cause and diagnostic code of the CLEAR packets; it also uses the F0 cause code and the suitable diagnostic one for all the CLEAR packets internally generated.
If MCAU is set to YES, Abilis CPX forces the cause code of the CLEAR packet sent to the value 00 (DTE originated), either for the external CLEAR and the internal ones.
The changes made on this parameter are immediately activated, without the need of
initialisation commands.
| PS: | Packet size (bytes) |
| 2048 | 16, 32, 64, 128, 256, 512, 1024, 2048 |
It sets the maximum size (bytes) of packets to be sent or received.
| VC: | Type of logical channel |
| BSVC | BSVC, PVC |
It sets the connection type: BSVC=bidirectional switched, PVC= bidirectional permanent.
| N1: | Maximum HDLCT frame size (CRC not included) |
| 2100 | 128 - 2100 bytes |
It sets the maximum size (bytes) of HDLCT frames to be sent or received, CRC is not included.
| AC: | Autoconnection mode |
| NO | NO, DCD, DATA |
It sets how the port behaves during the connection set up.
| Value | Description |
|---|---|
| NO | No "autoconnection" procedure is enabled and the connection is established only because of requests calls |
| DCD | The "autoconnection" procedure is used: the HDLCT driver, whenever it reaches the READY state, will start to set up the connection |
| DATA | The "autoconnection" procedure is used: the HDLCT driver will start to set up the connection, only if a frame is received |
| RTY: | Calls repetition mode |
| INC | LIN, INC |
It allows to select the calls repetition mode.
| Value | Description |
|---|---|
| LIN | The time interval to wait, between a call attempt and the successive one, is fixed and configurable through the parameter TB: |
| INC | The time interval to wait, between a call attempt and the successive one, is doubled to every attempt starting from the value defined in the parameter TB: |
If the connection type is PVC (that is parameter VC: set to "PVC") the value of the parameter "RTY:" is ignored.
| TB: | Time interval between calls repetitions |
| 6 | 6 - 255 seconds |
It defines the smallest time interval to be waited between a call attempt and its successive one.
If the connection type is PVC (that is parameter VC: set to "PVC") the value of the parameter "RTY:" is ignored.
| NRTY: | Maximum number of call repetitions |
| 0 | 0 - 65534, NOMAX |
| Value | Description |
| 0 | No call is made |
| AUTO | Calls are repeated indefinitely |
| 1 - 65534 | Calls are repeated as many times as the configured value |
If the connection type is PVC (that is parameter VC: set to "PVC") the value of the parameter "RTY:" is ignored.
| DT: | Disconnection Timeout |
| 0 | 0 - 255 minutes |
Every time the HDLCT driver is in its "CONNECTED" state and no frames are exchanged from both directions for longer than this parameter value, connection will teared down with codes F0,D0 and the driver will reach the "READY" state.
If the connection type is PVC (that is parameter VC: set to "PVC") the value of the parameter "RTY:" is ignored.
| RXBUF: | Number of receiving buffers |
| 1 | 1 - 255 |
It sets the number of receiving buffers.
| TXBUF: | Number of transmission buffers |
| 14 | 1 - 255 |
It sets the number of transmission buffers.
How to check state and statistics of the HDLCT ports by the command D S.
[15:03:33] ABILIS_CPX: D S PO:341 .
PO:341 ------------------------------------------------------------------------
HDLCT STATE:READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG |0 |0 |FRAME |0 |0 |
CHAR |0 |0 |
------------------------------------------------------------------------
Extended statistics are not available for HDLCT ports. The command D SE execution will display again the not extended statistics by the following format:
[15:03:33] ABILIS_CPX: D SE PO:341
PO:341 ------------------------------------------------------------------------
HDLCT --- Cleared 000:00:01:38 ago, on 01/01/1997 at 01:50:31 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG |0 |0 |FRAME |0 |0 |
CHAR |0 |0 |
------------------------------------------------------------------------
The information "Cleared DDD:HH:MM:SS ago, at DD/MM/YYYY HH:MM:SS", referred by the extended statistics, shows the time interval elapsed from the last reset of statistics (by the format "days:hours:minutes:seconds") and date/time of its execution (by the format "day:month:year" and "hours:minutes:seconds").
| STATE: | Current state of the driver HDLCT |
| DOWN, READY, READY-DELAYED, STOPPED, CALLING, CONNECTED, CLEARING, ERR |
| Driver | States | Meaning | Values shown in: | ||
|---|---|---|---|---|---|
| System Log | Debug Log | Display LCD | |||
| HDLCT | DOWN | Port is active | DN | ||
| READY | Port is active, but the Level 2 is not connected | RD | |||
| READY-DELAY | Waiting for level 2 connecting. A SABM frame has been sent and the driver is waiting to receive an UA frame | ||||
| STOPPED | Port is blocked | ST | |||
| CALLING | Waiting for disconnecting; a DISC frame has been sent and the driver is waiting to receive a DM or UA frame | CL | |||
| CONNECTED | Level 2 is active; a SABM frame has been sent and an UA one was received or the SABM was received and the UA one sent | CN | |||
| CLEARING | A FRMR frame has been sent | CR | |||
| ERR | Software error. Contact Abilis assistance. | NA | |||
| SEG: | Number of data segments received/sent |
| 0 - 4.294.967.295 |
The counter SEG (INPUT) is incremented every time the HDLCT port receives data, while the counter SEG (OUTPUT) every time data are sent.
Segments are calculated on a per packet basis as 64 bytes units.
| FRAME: | Number of frames received/sent |
| 0 - 4.294.967.295 |
The counter FRAME (INPUT) is incremented every time the HDLCT port receives one frame, while the counter FRAME (OUTPUT) every time a frame is sent.
| CHAR: | Number of characters received/sent |
| 0 - 4.294.967.295 |
The counter CHAR (INPUT) is incremented every time the HDLCT port receives data, while the counter CHAR (OUTPUT) every time data are sent.
| Trap own code | Mnemonic of the trap | SNMP variables reported in the trap | Description |
|---|---|---|---|
| 33 | cxTrapHdlctDown | cxPortIndex, cxPortType, cxHdlctDiagState, sysUpTime | The SNMP Agent of the Abilis CPX generates this kind of trap every time the HDLCT port leaves the READY or READY-DELAY or CALLING or CONNECTED or CLEARING state and reaches one of the following states: DOWN or STOPPED |
| 34 | cxTrapHdlctUp | cxPortIndex, cxPortType, cxHdlctDiagState, sysUpTime | The SNMP Agent of the Abilis CPX generates this kind of trap every time the HDLCT port leaves one of the following states: DOWN or STOPPED and reaches the READY or READY-DELAY or CALLING or CONNECTED or CLEARING state |
| cxPortIndex | HDLCT 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 HDLCT port, which the trap refers to |
| type - description |
This variable shows either the port type which the trap refers to (in this case HDLCT) and the description eventually associated to it.
| cxHdlctDiagState | Current state of the HDLCT port driver which the trap refers to |
| down(0), ready(1), ready-delay(2), stopped(3), calling(4), connected(5), clearing(6) |
This variable shows the current state of the HDLCT port driver which the trap refers to. The following table shows the relationship among the state value stored in the SNMP variable and the ones obtained executing the command D S.
| Value of the SNMP variable | Correspondent state of the HDLCT driver |
|---|---|
| down(0) | DOWN |
| ready(1) | READY |
| ready-delay(2) | READY-DELAY |
| stopped(3) | STOPPED |
| calling(4) | CALLING |
| connecteded(5) | CONNECTED |
| clearing(6) | CLEARING |
| sysUpTime | Elapsed time from the system start to the event occurrence |
| 0 - 4.294.967.295 or "ddd:hh:mm:ss" |
This variable stores the elapsed time (in cent of second) from the system start to the SNMP trap event occurrence.
This value is usually shown by the format days:hours:minutes:seconds.
Print this page