It is possible through the Control Port to access configuration and supervising functions.
The Control Port is not a physic port, that is there is no connector, but it is a "virtual" port of the Abilis CPX. It is possible to send commands and get answers, to configure and supervise the Abilis CPX.
it is possible to log in to the Control Port by using three different privilege levels, each of them has got a set of allowed operations and it is provided with a set of suitable commands:
It is possible to access the different levels through the proper passwords: if no password is configured, User will access directly the level which provides more privileges.
Once the CP has been accessed, it is possible to check or modify the privilege level by using the command LOGIN, described in section Access commands to the system of General and system commands document.
Here is an example on how to access the Control Port through the TELNET port, with USER privileges:
[192.168.0.60] TELNETS>00-CP COM CPX system release 4.1.0 - build 1129 Wednesday 27/03/2002 18:31:04 (GMT+1.00) Login:USER Password:********* Logged as USER [11:32:37] ABILIS_CPX:
As the previous example shows, the User is asked to specify the requested access level (USER, ADMINISTRATOR or SUPERUSER) and then to insert the correspondent password.
If the password is wrong, it will be asked again. After the third wrong try the connection will be cleared.
[192.168.0.60] TELNETS>00-CP COM CPX system release 4.1.0 - build 1129 Wednesday 27/03/2002 18:31:04 (GMT+1.00) Login:USER Password:***** INVALID PASSWORD Password:******** INVALID PASSWORD Password:******* CLR F0 AE [192.168.0.60] TELNETS>
The Control Port is identified by the mnemonic "CP", correspondent to the Abilis CPX port "0" and it is provided with the parameters described in this section.
Here is an example on how to display the Control Port parameters. Shown values are the default ones.
[11:47:16] ABILIS_CPX: D P PO:0
PO:0 - Not Saved (SAVE CONF), Not Refreshed (INIT) --------------------------
CP ------------------------------------------------------------------------
PI:ABILIS_CPX: bsvc:3 ps:128
PWD-U: PWD-A: PWD-S:
X29A:02010102010302040006050C010D000E000F011008111812121302
X29B:020100020003000402050006000700080009000A000C000D000E000F001500
To activate changes made on the parameters displayed by low case characters, it is needed to restart the system; on the contrary changes made on upper case parameters are immediately active.
The "Not Saved (SAVE CONF)" message is displayed every time the port configuration is modified but not saved with the SAVE CONF command.
The "Not Refreshed (INIT)" message is displayed every time the port configuration is modified but not refreshed with the INIT PO: command.
| PI: | Prompt of CP command interpreter |
| ABILIS_CPX: | from 0 up to 16 ASCII characters [33..126] |
This parameter set the command interpreter prompt of the Control Port.
Information about current local time "[hh:mm:ss]" always precedes the user defined prompt.
It is possible to use from 0 up to 16 ASCII characters [33..126], spaces are not allowed. No differences between low and high case characters are made.
To remove the port identifier, the prompt parameter has to be set to "S P PO:0 PI:".
| BSVC: | Number of sessions |
| 3 | 3 - 8 |
It sets the maximum number of connections that can be opened at the same time with the Control Port.
| PS: | Packet size |
| 128 | 16, 32, 64, 128, 256, 512, 1024, 2048 (bytes) |
It sets the maximum size (in bytes) of packets to be sent or received.
| PWD-U: | Access Password to the CP of the USER level |
| no value | from 0 up to 16 ASCII characters [33..126] |
It sets the access password to the CP of the USER level.
It is possible to use from 0 up to 16 ASCII characters in the range [33..126], spaces are not allowed. No differences between low and high case characters are made
Once it is configured, the new password will be saved on the Abilis CPX disk, in a encrypted way, using the command SAVE CONF.
Every time the user wants to connect to the Control Port, he is asked to specify the requested access level (USER, ADMINISTRATOR or SUPERUSER) and then to insert the correspondent password. If the password is wrong, it will be asked again. After the third wrong try the connection will be cleared.
To delete the password, this parameter has to be set to "S P PO:0 PWD-U:".
This parameter can me modified at the privilege levels Administrator/Super-User.
| PWD-A: | Access Password to the CP of the ADMINISTRATOR level |
| no value | from 0 up to 16 ASCII characters [33..126] |
It sets the access password to the CP of the ADMINISTRATOR level.
It is possible to use from 0 up to 16 ASCII characters in the range [33..126], spaces are not allowed. No differences between low and high case characters are made
Once it is configured, the new password will be saved on the Abilis CPX disk, in a encrypted way, using the command SAVE CONF.
Every time the user wants to connect to the Control Port, he is asked to specify the requested access level (USER, ADMINISTRATOR or SUPERUSER) and then to insert the correspondent password. If the password is wrong, it will be asked again. After the third wrong try the connection will be cleared.
To delete the password, this parameter has to be set to "S P PO:0 PWD-AU:".
This parameter can me modified at the privilege levels Administrator/Super-User.
| PWD-S: | Access Password to the CP of the SUPER-USER level |
| no value | from 0 up to 16 ASCII characters [33..126] |
It sets the access password to the CP of the SUPER-USER level.
It is possible to use from 0 up to 16 ASCII characters in the range [33..126], spaces are not allowed. No differences between low and high case characters are made
Once it is configured, the new password will be saved on the Abilis CPX disk, in a encrypted way, using the command SAVE CONF.
Every time the user wants to connect to the Control Port, he is asked to specify the requested access level (USER, ADMINISTRATOR or SUPERUSER) and then to insert the correspondent password. If the password is wrong, it will be asked again. After the third wrong try the connection will be cleared.
To delete the password, this parameter has to be set to "S P PO:0 PWD-S:".
This parameter can me modified at the privilege level Super-User.
| X29A: | X29 String to be sent before reach the "COMMAND-MODE" |
| See example | from 0 up to 64 hexadecimal digits |
This parameter represents the content of the X29 packet that has to the Control Port has to send to the PAD port every time it activates the exchange command procedure COMMAND-MODE.
It means the content of this parameter will be used when:
The string configured in the parameter "X29A:" will be send into a packet with Q-bit set to 1.
To delete the X29 string and to not send it, the parameter must have no value: "S P PO:0 X29A:".
| X29B: | X29 String to be sent on exiting the "COMMAND MODE" |
| See example | from 0 up to 64 hexadecimal digits |
This parameter represents the content of the X29 packet that has to the Control Port has to send to the PAD port every time it activates the procedures of file transferring using the XMODEM protocol.
The string configured in the parameter "X29B:" will be send into a packet with Q-bit set to 1.
To delete the X29 string and to not send it, the parameter must have no value: "S P PO:0 X29B:".
Example on how to show state and statistics of the Control Port through the command D S:
[11:32:37] ABILIS_CPX: D S PO:0
PO:0 ------------------------------------------------------------------------
CP STATE:UP
Ses State AccessLevel Action
------------------------------------------------------------------------
1 CONNECTED SUPERUSER COMMAND-MODE
2 READY
3 READY
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 64| 4|CHAR | 3798| 21|
------------------------------------------------------------------------
The Control Port has no extended statistics, so that the execution of the command D SE will display again the not extended statistics by the format:
[11:32:37] ABILIS_CPX: D SE PO:0
PO:0 ------------------------------------------------------------------------
CP --- Cleared 001:01:38:54 ago, on 25/03/2002 at 08:34:47 ----------------
-----------|---INPUT---|--OUTPUT---|-----------|---INPUT---|--OUTPUT---|
SEG | 64| 4|CHAR | 3798| 21|
------------------------------------------------------------------------
The information "Cleared DDD:HH:MM:SS ago, at DD/MM/YYYY HH:MM:SS", referred by the extended statistics, shows 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").
| STATE: | Current state of the Control Port |
| UP, ERR |
It shows the current state of the Control Port driver.
| Driver | States | Description | Values shown in: | ||
|---|---|---|---|---|---|
| System Log | Events Log | Display LCD | |||
| CP | UP | The port is active. This is a virtual port, so it is always active. | UP | ||
| ERR | Software error. Contact Abilis CPX assistance. | NA | |||
| SEG: | Number of data segments sent/received |
| 0 - 4.294.967.295 |
The counter SEG (INPUT) is incremented every time data are received by the Control Port. The counter SEG (OUTPUT) is incremented every time data are sent by the Control Port.
Segments are calculated by dividing the number of bytes per 64.
| CHAR: | Number of characters sent/received |
| 0 - 4.294.967.295 |
The counter CHAR (INPUT) is incremented every time data are received by the Control Port. The counter CHAR (OUTPUT) is incremented every time data are sent by the Control Port.
| Ses: | Session of the Control Port |
| 3 - 8 |
Session of the CP. The number of connections that can be opened at the same time with the Control Port is set by the BSVC: parameter.
| State: | Current state of the Control Port |
| DOWN, READY, CALLED, CALLING, CONNECTED, REST, RESETTING, CLEARED, CLEARING, ERR |
It shows the current state of each connection.
| Driver | States | Description | Values shown in: | ||
|---|---|---|---|---|---|
| System Log | Events Log | Display LCD | |||
| CP (Sessions) | DOWN | Session is not ready to open a new connection | |||
| READY | Session is ready to open an eventual connection | ||||
| CALLED | Session is opening the connection | ||||
| CALLING | |||||
| CONNECTED | Session is connected | ||||
| RESET | Session is resetting the connection | ||||
| RESETTING | |||||
| CLEARED | Session is clearing the connection | ||||
| CLEARING | |||||
| ERR | Software error. Contact Abilis assistance. | ||||
| AccessLevel: | Session access level currently in use |
| USER, ADMINISTRATOR, SUPERUSER |
It shows the session privilege level actually in use, only if the session is in its state CONNECTED.
| Driver | Access Level | Description |
|---|---|---|
| CP (Sessions) | USER | User is actually connected using a USER privilege level |
| ADMINISTRATOR | User is actually connected using a ADMINISTRATOR privilege level | |
| SUPERUSER | User is actually connected using a SUPER-USER privilege level |
| Action: | Operative current state of the session |
| LOGIN-PHASE, COMMAND-MODE, SENDING-FILE, SENDING-TRACE, RECEIVING-FILE, UPDATING-SYSTEM |
Current operative state of the CP session, only if the session is in its state CONNECTED.
| Driver | Operative states | Description |
|---|---|---|
| CP (Sessions) | LOGIN-PHASE | Session is connected and Login/password request procedure is in act |
| COMMAND-MODE | Session is connected and data are exchanged (COMMAND-MODE) | |
| SENDING-FILE | On the actual session, files are sent to a remote destination | |
| SENDING-TRACE | On the actual session, the events trace is sent to a remote destination | |
| RECEIVING-FILE | A file is received from a remote destination | |
| UPDATING-SYSTEM | System updating is received from a remote destination |
There are several ways to connect to the Control Port:
Figure 1. Connecting through the PAD configuration port.
In this case the asynchronous terminal is connected to the male DB-25 plug, placed on the back of the Abilis CPX.
The terminal must be set to 9600 bit/sec, 8 data bit, 1 stop bit, no parity check and no flow control. After switching on the terminal, press the key <Enter> to get the PAD local port prompt, digit 00-CP and the command interpreter of the local CPX Control Port will appear.
It is also possible to connect to a remote CPX Control Port through a local CPX.
When the connection to the CP is established, all the needed commands can be sent, the answer will be displayed on the video.
Instead of the asynchronous terminal it is always possible to use a personal computer provided with a emulation program TTY or VT100 or similar.
Abilis CPX asynchronous interface is a DTE type, the suitable connecting cable
must be chosen.
Figure 2. Connecting to the CP through the SVC X.25 channel, from a remote PAD.
In this case the asynchronous terminal connected to a PAD must be provided with a terminal emulation program such as TTY or VT100 (or similar).
The terminal makes a call to the Abilis CPX address, inserting in the User data the string "CP".
Abilis CPX receives the call, open the connection to the Control Port, and send back to the terminal a packet containing the prompt (for example ABILIS_CPX:); from this moment terminal and CP can communicate.
Procedure for making a X.25 call depends on the PAD type, however here is an example of the mostly used:
PAD_PROMPT:12345678DCP It calls the 12345678 NUA with user data RP ACP:COM Call has been accepted. PAD_PROMPT:C 12345678DCP It calls the 12345678 NUA with user data RP. PAD:COM Call has been accepted. PAD_PROMPT:12345678-CP It calls the 12345678 NUA with user data RP. COM
Refer to PAD instructions for the procedure to use.
The connection to the Control Port via the SVC channel requires the routing table to have, at least, one routing whose destination is "0". Into the default table there are two routings able to connect to the CP: the first one containing the "RP" user data, the second one with the called address "00".
By modifying the routings according to the instructions described in the section Configuration of SVC routing of chapter SVC routing, it is possible to change the CP accessing rules, or simply to remove the routing, whose destination port is "0", in such a way to avoid any remote connection to it.
If routings, with destination port "0", have been removed, there two possibilities to recover the access to the Control Port:
PAD and the Control Port must communicate through packets, that is every command sent by the terminal has to be contained in a single X.25 packet, otherwise the Control Port won't accept it. That's why it is really important that PAD is configured to send packet only after receiving the character <CR> (carriage return).
Here there is an example of PAD parameter configuration; the obligatory ones are highlighted:
01:001 02:001 03:002 04:000 05:001 06:005 07:000 08:000 09:000 10:000 11:015 12:001 13:004 14:000 15:001 16:008 17:024 18:002
Instead of the asynchronous terminal it is always possible to use a personal computer provided with a emulation program TTY or VT100 or similar.
Connection to the Control Port requires a SVC channel.
If Abilis CPX is only using PVC channels, it is better to add at least one SVC channel.
If the Abilis is only using SVC channels, it is better to add a new SVC channel. If all the SVC channels are
busy it is not possible to connect to the Control Port.
Figure 3. Connecting to the CP via X.25 SVC, from a remote DTE X.25.
In this case the X.25 DTE connected to the network must be provided with X.25 adapter and a terminal emulation program such as TTY or VT100 (or similar).
The X.25 DTE makes a call to the Abilis CPX address, inserting in the User data, starting from the 5th byte, the string "CP".
Abilis CPX receives the call, open the connection to the Control Port, and send back to the X.25 DTE a packet containing the prompt (for example ABILIS_CPX:); from this moment DTE and CP can communicate.
X.25 DTE and the Control Port must communicate through packets, that is every command sent by the DTE has to be contained in a single X.25 packet, otherwise the Control Port won't accept the command.
Discussions about routings of the previous examples are still valid.
The Control Port needs at least one routing to be reached: the default routing table has got a routing for connection to the Control Port ("CP" user data of the call).
In this case it is possible to use a personal computer provided with a TELNET (or SSH) Client program such as Windows 2000 Telnet Client (or similar).
The TELNET (or SSH) Client application makes a TCP/IP call to the Abilis CPX IP address.
The TELNET (or SSH) Server of the Abilis CPX receives the call, establishes the TCP connection and sends back the TELNET (or SSH) Server prompt (for example TELNETS>).
From this moment the TELNET (or SSH) Server of the Abilis CPX and the remote TELNET (or SSH) Client application are interconnected.
[192.168.0.60] TELNETS>
To open the connection to the Control Port, the user must enter the proper Called address and User data values to the TELENET (or SSH) application prompt.
The TELNET (or SSH) makes a call to the Control Port, that sends back the packet containing the configured prompt (for example ABILIS_CPX:).
[192.168.0.60] TELNETS>00-CP COM CPX system release 4.1.0 - build 1129 Wednesday 27/03/2002 18:31:04 (GMT+1.00) Logged as SUPERUSER [18:13:50] ABILIS_CPX:
To cut short the connection phase the user can activate the Auto-Connection procedure on the TELNET (or SSH) Server of the Abilis CPX, setting the AC: parameter to YES. The CDO: and the UDO: parameters of the TELNET (or SSH) port must be also set respectively to the proper Called address and User data values.
Acordingly to the features of the Auto-Connection procedure, once the TELNET (or SSH) Server of the Abilis CPX will receive the TCP/IP call from the TELNET (or SSH) Client application, it will atomatically call the Control Port, establishing the connection.
COM CPX system release 4.1.0 - build 1129 Wednesday 27/03/2002 18:31:04 (GMT+1.00) Logged as SUPERUSER [18:28:22] ABILIS_CPX:
Discussions about routings of the previous examples are still valid.
The Control Port needs at least one routing to be reached: the default routing table has got a routing for connection to the Control Port ("CP" user data of the call).
Print this page