The X.25 level 3 ports (X25)

[18:38:04] ABILIS_CPX: D P PO:301

PO:301 ------------------------------------------------------------------------
X25    LOG:DS      lowpo:201   TYPE:USER     MCAU:NO     PW:2     ps:128    
       fpvc:1      fisvc:1     fbsvc:1       fosvc:11    x25:DTE   
       pvc:0       isvc:0      bsvc:10       osvc:0     
       T20:30      T21:30      T22:30        T23:30      N3:3     

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:

• setting "LOG:DS+E", activates the extended logging functions for Events Log and System Log
• setting "LOG:STA", activates the extended logging functions for System Log, SNMP traps generation and periodic detection of alarm states;

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:

• Suppose the current value of the parameter is "LOG:DSTA", by setting "LOG:-A", the periodic detection of eventual alarm states is removed, leaving unchanged all the remaining options; in such way the final value of the parameter will be "LOG:DST";
• Suppose the current value of the parameter is "LOG:ST", by setting "LOG:+DA", the logging function of the events on the Events Log and the periodic alarm detection are added to the already activated options; in such way the final value of the parameter will be "LOG:DSTA".

The changes made on this parameter are immediately activated, without the need of initialization commands.

It sets the Abilis CPX lower level port, which can only be a LAPB or LAPD, EBLAPD or EPLAPD port type.

The value "NONE" is used to isolate the X25 port.

This parameter sets how the port behaves if data compression is activated.

The port connected to the X.25 network is defined NETWORK port; the one connected to the user device 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.

Wrong configuration of this parameter will cause connection to close as soon as data is exchanged. If the error is detected by the user equipment it closes the connection and provides its own X25 diagnostic code, if the error is detected by Abilis CPX it closes the connection providing one of the following diagnostic codes:

• F0,C2 : Error in the expansion phase

• F0,C3 : Format of the compressed data not valid

• F0,AA: Compression protocol not compatible

The changes made on this parameter are immediately activated, without the need of initialisation commands.

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.

It sets the default size of the Level 3 window.

It must match the value set for the port at the other side of the line.

Abilis CPX supports packet window negotiation as for X25 recommendation.

It sets the maximum size (in bytes) of the packets to be sent/received.

Abilis CPX does not support packet size negotiation.

It allows to choose the level 3 behaviour between DTE and DCE.

The ports of the two devices that face each other, that is the two ports connected through the line, must be configured complementary. It means that connection will work only if one is DCE and the other is DTE.

Network ports are usually set as DCE therefore user devices ports have to be set as DTE. As a result, Abilis CPX ports connected to a public network will be set as DTE while those connected to a user device will be set to DCE.

The difference between level 3 DTE and DCE consists in the way they manage the logical channels:

• DTE makes the outgoing calls starting from the higher logical channel, while DCE from the lower;

• DTE makes calls on OSVC channels and receives them on the ISVC ones;

• DCE makes calls on ISVC channels and receives them on the OSVC ones:

• Both make and receive calls on BSVC channels.

It sets the number of the first permanent logical channel (PVC).

If ISVC: is set to 0, this parameter is meaningless.

It sets the number of the first ISVC logical channel in the X.25 connection.

If the port is connected to an X25 network, the value to set is specified in the network provider subscription.

If the port is connected to a user device, the value of the parameter has to match the device configuration.

If this parameter is wrongly set, no calls could be received or made.

If ISVC: is set to 0, this parameter is meaningless.

It sets the number of the first BSVC logical channel in the X.25 connection.

If the port is connected to an X25 network, the value to set is specified in the network provider subscription.

If the port is connected to a user device, the value of the parameter has to match the device configuration.

If this parameter is wrongly set, no calls could be received or made.

If BSVC: is set to 0, this parameter is meaningless.

It reports the number of the first OSVC logical channel in the X.25 connection.

If the port is connected to an X25 network, the value to set is specified in the network provider subscription.

If the port is connected to a user device, the value of the parameter has to match the device configuration.

If this parameter is wrongly set, no calls could be received or made.

If OSVC: is set to 0, this parameter is meaningless.

It sets the number of permanent logical channels (PVC) in the X.25 connection.

If the port is connected to an X25 network, the value to set is specified in the network provider subscription.

If the port is connected to a user device, the value of the parameter has to match the device configuration.

A wrong setting of this parameter could prevent the activation of PVC connections and the ability of making and receiving calls.

Value 0 means that no PVC is configured.

Permanent channels numbering ALWAYS starts from 1 and it is SEQUENTIAL.

If, for instance, PVC channels 4 and 5 have to be used, while the 1,2,3 ones shall not, then the parameter PVC: has to be set to 5 and in the PVC connection table only the channels 4 and 5 have to be configured.

It reports the number of ISVC logical channels in the X.25 connection.

If the port is connected to an X25 network, the value to set is specified in the network provider subscription.

If the port is connected to a user device, the value of the parameter has to match the device configuration.

If this parameter is wrongly set, no calls could be received or made.

Value 0 means that no ISVC are configured.

It reports the number of BSVC logical channels in the X.25 connection.

If the port is connected to an X25 network, the value to set is specified in the network provider subscription.

If the port is connected to a user device, the value of the parameter has to match the device configuration.

If this parameter is wrongly set, no calls could be received or made.

Value 0 means that no BSVC are configured.

It reports the number of OSVC logical channels in the X.25 connection.

If the port is connected to an X25 network, the value to set is specified in the network provider subscription.

If the port is connected to a user device, the value of the parameter has to match the device configuration.

If this parameter is wrongly set, no calls could be received or made.

Value 0 means that no OSVC are configured.

Maximum time to wait for receiving a Restart Confirmation after sending a Restart Request.

If it elapses the Restart Request is repeated indefinitely.

Maximum time to wait for receiving a Call Connect or Clear Request, after sending a Call Request.

If it elapses a Clear Request packet is sent with cause and diagnostic 13,31.

Maximum time to wait for receiving a Reset Confirmation after sending a Reset Request.

If it elapses the behaviour is different for PVC and SVC channels:

• in PVC, Reset Request is repeated indefinitely.

• In SVC, Reset Request is repeated up to N3 times, after which a Clear Request packet is sent with cause and diagnostic 13,31.

Maximum time to wait for receiving a Clear Confirmation after sending a Clear Request.

If it elapses the Clear Request is repeated up to N3 times, after which the call clearing is considered complete.

It sets how many times Clear Request and Reset Request (SVC) can be repeated before reporting an error.

[18:38:04] ABILIS_CPX: D S PO:301

PO:301 ------------------------------------------------------------------------
X25    STATE:READY     
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       SEG        |0          |0          |CHAR       |0          |0          |
       PCK        |0          |0          |
       ------------------------------------------------------------------------

[18:38:04] ABILIS_CPX: D SE PO:301

PO:301 ------------------------------------------------------------------------
X25    --- Cleared 003:23:51:21 ago, on 12/05/2000 at 12:11:28 ----------------
       -----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
       RES-REQ    |0          |1          |RES-CON    |1          |0          |
       CAL-REQ    |0          |0          |CAL-CON    |0          |0          |
       CLR-REQ    |0          |0          |CLR-CON    |0          |0          |
       RST-REQ    |0          |0          |RST-CON    |0          |0          |
       INT-REQ    |0          |0          |INT-CON    |0          |0          |
       PCK        |0          |0          |SEG        |0          |0          |
       CHAR       |0          |0          |RR         |0          |0          |
       RNR        |0          |0          |REJ        |0          |0          |
       BAD-PCK    |0          |           |T20-OVR    |           |0          |
       T21-OVR    |           |0          |T22-OVR    |           |0          |
       T23-OVR    |           |0          |N3-OVR     |           |0          |
       ------------------------------------------------------------------------

This is the current state of the X25 driver.

Driver type	States	Meaning	Values shown in:
			System Log	Events Log	LCD Display
X25	DOWN	Port is not active.	down
	RESTARTING	Waiting level 3 initialisation. The port sent a RESTART Request packet and waits to receive the RESTART Confirmation one.	rstg
	RESTARTED	Waiting level 3 initialisation. The port received a RESTART Request packet and it is waiting to send a RESTART Confirmation packet.	rstd
	READY	Level 3 is in the READY state	RDY
	ERR	Software error. Please contact the Abilis assistance.	NA

The counter SEG (INPUT) is incremented every time the X25 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; if a packet length is not exactly multiple of 64 bytes, the excess is counted as 1 segment.

The counter CHAR (INPUT) is incremented every time the X25 port receives data, while the counter CHAR (OUTPUT) every time data are sent.

The counter PCK (INPUT) is incremented every time the X25 port receives data packets, while the counter PCK (OUTPUT) every time it sends them.

The counter RES-REQ (INPUT) is incremented every time a RESTART Request is received, while the counter RES-REQ (OUTPUT) every time a RESTART Request is sent.

The counter RES-CON (INPUT) is incremented every time a RESTART Confirmation is received, while the counter RES-CON (OUTPUT) every time RESTART Confirmation is sent.

The counter CAL-REQ (INPUT) is incremented every time a Call Request is received, while the counter CAL-REQ (OUTPUT) every time a Call Request is sent.

The counter CAL-CON (INPUT) is incremented every time a Call Connect is received, while the counter CAL-CON (OUTPUT) every time a Call Connect is sent.

The counter CLR-REQ (INPUT) is incremented every time a Clear Request is received, while the counter CLR-REQ (OUTPUT) every time a Clear Request is sent.

The counter CLR-CON (INPUT) is incremented every time a Clear Confirmation is received, while the counter CLR-CON (OUTPUT) every time a Clear Confirmation is sent.

The counter RST-REQ (INPUT) is incremented every time a Reset Request is received, while the counter RST-REQ (OUTPUT) every time a Reset Request is sent.

The counter RST-CON (INPUT) is incremented every time a Reset Confirmation is received, while the counter RST-CON (OUTPUT) every time a Reset Confirmation is sent.

The counter INT-REQ (INPUT) is incremented every time a INTERRUPT Request is received, while the counter INT-REQ (OUTPUT) every time a INTERRUPT Request is sent.

The counter INT-CON (INPUT) is incremented every time a INTERRUPT Confirmation is received, while the counter INT-CON (OUTPUT) every time a INTERRUPT Confirmation is sent.

The counter PCK (INPUT) is incremented every time the X25 port receives data packets, while the counter PCK (OUTPUT) every time it sends them.

The counter SEG (INPUT) is incremented every time the X25 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; if a packet length is not exactly multiple of 64 bytes, the excess is counted as 1 segment.

The counter CHAR (INPUT) is incremented every time the X25 port receives data, while the counter CHAR (OUTPUT) every time data are sent.

The counter RR (INPUT) is incremented every time a RR packet is received, while the counter RR (OUTPUT) every time a RR is sent.

The counter RNR (INPUT) is incremented every time a RNR packet is received, while the counter RNR (OUTPUT) every time a RNR is sent.

The counter REJ (INPUT) is incremented every time a REJ packet is received, while the counter REJ (OUTPUT) every time a REJ is sent.

The counter BAD-PCK (INPUT) is incremented every time any unknown packet is received.

The counter T20-OVR (OUTPUT) is incremented every time the timeout configured in the parameter T20: occurs.

The counter T21-OVR (OUTPUT) is incremented every time the timeout configured in the parameter T21: occurs.

The counter T22-OVR (OUTPUT) is incremented every time the timeout configured in the parameter T22: occurs.

The counter T23-OVR (OUTPUT) is incremented every time the timeout configured in the parameter T23: occurs.

The counter N3-OVR (OUTPUT) is incremented every time the maximum retransmission number, set in the parameter N3: has been reached.

This variable shows the CPX port number which the SNMP trap refers to.

This variable shows either the port type which the trap refers to (in this case X25) and the description eventually associated to it.

This variable shows the current state of the X25 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.

SNMP variable value	Corresponding state of the X25 port
down(0)	DOWN
restarting(1)	RESTARTING
restarted(2)	RESTARTED
ready(3)	READY

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 in SNMP consoles as days:hours:minutes:seconds.