M0SIP3E2012Iv02 SIP-3 User Guide R2-I
M0SIP3E2012Iv02 SIP-3 User Guide R2-I
TYPE SIP-3
USER GUIDE
V02 - December 2020
M0SIP3E2012Iv02
ZIV
Carrer de les Ciències,149-151
08908 l’Hospitalet de Llobregat,
Barcelona-Spain
Tel.: +34 933 490 700
Fax: +34 933 492 258
Mail to: [email protected]
www.zivautomation.com
SAFETY SYMBOLS
WARNING OR CAUTION:
This symbol denotes a hazard. Not following the indicated procedure,
operation or alike could mean total or partial breakdown of the unit or
even injury to the personnel handling it.
NOTE:
Information or important aspects to take into account in a procedure,
operation or alike.
TABLE OF CONTENTS
Page
1 INTRODUCTION 6
1.4 WARNINGS 17
1.4.1 Warnings before installing 17
1.4.2 Unit safety considerations 18
3 LED SIGNALLING 33
4.1 CONSOLE 36
5.2 ADMINISTRATION 44
5.15 REBOOT 94
6 STATISTICS 98
APPENDIX A
APPENDIX B
1 INTRODUCTION
SIP-3 allows serial to IP encapsulation. The unit has different configurations regarding the
number of interfaces.
In terms of number of serial ports, the unit can be equipped with a single serial port with
RS-232/RS-485 (DB9) interface or three ports, one with RS-232/RS-485 (DB9) interface
and two with RS-232 (DB9) interface.
All the serial ports are configured as DCE (Data Communications Equipment).
As regards the network interface, the unit can have one or two electrical Fast Ethernet
(RJ-45) ports or an electrical Fast Ethernet (RJ-45) port and an optical Fast Ethernet
(MT-RJ or LC) port.
The two Fast Ethernet ports can operate as part of a two-port Ethernet switch or either
as two independent Ethernet interfaces.
The power supply of the unit can be Multirange (36-360 VDC, 88-265 VAC) isolated or DC
isolated (10.5-72 VDC).
As regards its installation, the SIP-3 can be supplied with a chassis suitable for mounting in
DIN rail or wall mount.
The SIP-3 can be managed locally and remotely through a console or through a built-in
web server (HTTP/HTTPS), SSH and Telnet server.
The SIP-3 also supports the SNMPv1, SNMPv2c and SNMPv3 protocols, as well as other
services as DHCP, NTP, FTP/FTPs and TACACS+.
The encapsulation function guarantees delivery of the data accepted in one of the serial
ports of an end, free of errors, and with unaltered order at the other end of the connection.
This function is usually called PAD (Packet Assembler-Disassembler).
The encapsulation function does not depend on the user data content. The unit admits two
processing modes with the PAD function: direct or with packets.
Even though the encapsulation basic function is the execution of the PAD processes, the
SIP-3 unit has the necessary procedures to perform an intelligent encapsulation so as to
process the data as higher level transmission units for a series of specific protocols of
Telemetry and Telecontrol. Thus, the operations on the data are not limited to their mere
transmission, but possible errors are identified, or the SIP-3 is capable of identifying
different data flows in a unique shared channel and of transferring them towards
differentiated destinations (demultiplexing).
Some of the supported protocols are IEC 60870-5-101/102/103, DLMS, GESTEL, DNP3.0,
PROCOME, SAP20, MODBUS, Pid1, Twc, etc.
Another additional characteristic for any of the encapsulation modes is the SIP-3 capability
to offer the basic HAYES modem behaviour towards the client unit, so that the
encapsulation point-to-point connections are made upon demand and with the determined
receiver by application or the client unit. The operation in HAYES mode is enabled
separately for each one of the serial ports present in the SIP-3.
In addition to the serial ports -which are called physical ports-, the unit operates with
resources that are TCP/UDP connections, which are used to encapsulate data on the
TCP/IP networks; these TCP/UDP connections are called virtual ports, as opposed to the
tangible ports.
The unit basic operation is the determination of the port characteristics, both physical as
well as virtual, and then selects the “connections” between them; which in practice sets the
ends where the transfer of encapsulated data is done.
Next, for a better understanding when approaching the SIP-3 configuration by accessing
the unit HTML pages, there is a description of the main operations that should be
performed for the interconnection between physical ports (COM) and virtual ports
(TCP/UDP). It is advisable to perform the indicated operations in the order that they appear.
See chapter 5 for more detailed information about the configuration menus and their
parameters.
1. Configure the serial port parameters. For this, access the Serial menu (see section 5.4
for more information).
El Serial menu has two well differentiated sections: Physical and Logical.
In the Physical section, configure the basic operation parameters of the COM ports
(data rate, data bits, parity and stop bits).
In the Logical section, configure either the encapsulation protocol or the use of an
encapsulation policy (policy-based option), and an identifier for it. The policy
configuration itself is done from the Policy submenu from the Flow menu.
The identification of each COM port, that is, the name, is done in the Physical Ports
section of the Flow menu configuration screen.
2. Create and configure the parameters of the TCP/UDP virtual ports. For this, access the
Flow menu configuration screen (see section 5.13 for more detailed information).
The Flow menu configuration screen has two well differentiated sections. Physical
Ports and Virtual Ports.
Selects a different and unequivocal name for each COM port in the Physical Ports
section.
All the ports have the name serial0 configured by default and, therefore, it is essential
to assign a specific name to each of them.
On the other hand, if the unit has a WAN interface, the Use autocli box should be OFF,
that is, not ticked, in the Datacall parameter so that the data call-serial connection
(GSM) is effective.
NOTE: In SIP-3 devices with PHS8 modem (3G), datacall will not be possible from a PSTN
type analog modem.
Define the configuration of the virtual ports in the Virtual Ports section. For this, take
into account the following:
- The TCP connections may have two behaviours, active and passive. Active means
that the unit will take the initiative as regards establishing the TCP connection. On the
contrary, passive means that the unit will await for external connection requests. The
behaviours are complementary between them.
- The UDP connections do not need any prior establishment procedure; it is just
assumed that the receiver is configured to accept data in the indicated port. The UDP
connections do not offer end-to-end confirmation, or any guarantee as long as the
delivery sequence is the original one.
- It is usual to configure ports with values above 1000 since there are pre-set ports for
the use of general services in TCP/IP networks; thus, possible collisions are avoided.
The virtual ports may also have an assigned encapsulation protocol or policy,
although, as a general rule, just one encapsulation protocol or policy is assigned to a
sole end of each connection, understanding that it already includes a physical and a
virtual port as well. Thus, it is usual to assign the encapsulation protocol to the
physical port and leave the virtual port without a protocol, that is, with the raw
protocol option (default option).
The inactivity time is the maximum period of time desired to maintain the
connection in the case of a lack of data, either in transmission or reception.
This parameter is configured at 0 by default, that is, the activity is not monitored
at the data level, which implies that the connection will be permanent regardless
of its activity. The parameter units are seconds.
3. Establish the connections between the ports through their identifiers. For this, access
the Connection submenu (see section 5.13.2 for more information) from the Flow
menu.
The number of ports of the unit are the result of the combination of:
➢ 1 or 3 asynchronous serial data ports (COM), with female DB9 standard connector,
configurable by software for RS-232 interface and, only for port 1, for RS-232 or RS-485
(2-wire or 4-wire) interface. All the serial ports are configured as DCE.
➢ 1 service serial port (DCE mode) with female DB9 standard connector.
➢ IEC 60870-5 101/102/103 (the first two with the variants to support link addresses of 1
or 2 bytes).
➢ Data bits: 5, 6, 7 or 8.
➢ Stop bits: 1 or 2.
➢ Interface: V.24/V.28 of the ITU-T (EIA RS-232C) or, only for port 1, RS-485 (2-wire or
4-wire).
GSM/GPRS (2G)
UMTS/HSPA (3G)
PHS8 modem
HE910 modem
➢ Local and remote management through a CLI console (Command Line Interface) or a
built-in web server (HTTP/HTTPS), SSH and Telnet server.
➢ TACACS+ client.
➢ FTP/FTPs server.
➢ NAT rules.
➢ DNS client.
➢ TLS 1.2.
1.3.7 Accessories
➢ Ethernet cables.
➢ Serial cables.
➢ Antenna cables.
➢ Antennas.
➢ CE.
➢ DIN rail mounting (EN 50022, BS 5584, DIN 46277-3) or wall mounting.
➢ Dimensions:
• DIN rail model: Height: 127.5 mm; Width: 36.5 mm; Depth: 147 mm.
• Wall mount model: Height: 138.5 mm; Width: 164 mm; Depth: 36.5 mm.
➢ Weight: 549 g
➢ Power supply: 10.5-72 VDC (isolated) or multirange (36-360 VDC, 88-265 VAC) isolated.
In DC supply-voltage operation the unit is protected against polarity inversion.
The unit has an earth connection.
➢ Relative humidity not greater than 95%, in accordance with IEC 721-3-3 class 3K5
(climatogram 3K5).
➢ Electromagnetic compatibility.
1.4 WARNINGS
1.4.1 Warnings before installing
2. In order to install and handle the SIP-3 the following points must be
complied with:
- Only qualified personnel appointed by the electricity company that owns
the installation should carry out the installation and handling of the SIP-3.
- The environment in which it is to operate should be suitable for the SIP-3,
fulfilling all the conditions indicated in section 1.3.10.
3. ZIV will not accept responsibility for any injury to persons, installations or third
parties, caused by the non-fulfilment of points 1 and 2.
The diverse elements comprising the SIP-3 are supplied in a box ready for wall mounting,
see general dimensions in mm in FIGURE 4, or DIN rail mounting, see general dimensions
in mm in FIGURE 5.
FIGURE 6 shows the detail of the DIN rail fastening element. The installation procedure
can be seen in the attached detailed drawing.
Step 1: Fit the upper claws of the fastening piece Step 2: Press the equipment down firmly
into the upper profile of the DIN rail. in order to fix the lower claws.
Step 1: By pivoting on the upper claws, pull Step 2: Remove fully the equipment
strongly from the equipment until by pulling it upwards.
release the lower claws.
Pertenece a: Cód. Prod. Rev.
SIP-3
- 0
Fecha Realizado Vº Bº Comprobado Vº Bº Aprobado Vº Bº Archivo
14-02-2017 J. F. Gil MGSIP30100
Siglas Hoja
INSTALL AND UNINSTALL IN DIN RAIL
SIP-3 1/1
SIP-3
There are two power-supply models: isolated Multirange (36-360 VDC, 88-265 VAC) or
isolated DC (10.5-72 VDC).
The female connector supplied with the unit is suitable for rigid or flexible conductors of up
to 2.5 mm2.
There is an earth connection, see FIGURE 7. When using the multirange model,
this connection must be made before connecting any other power-supply cable.
Next to the power-supply connector, there are the Eth0 and Eth1 Fast Ethernet ports, see
FIGURE 8.
As shown in the figure, the SIP-3 can be equipped with 1 or 2 electrical ports (RJ-45) or
1 electrical port (RJ-45) and 1 optical port (multimode, MT-RJ or LC), which always
corresponds to Eth1.
The two Fast Ethernet ports can operate as part of a two-port Ethernet switch or either
as two independent Ethernet interfaces.
FIGURE 8 Location of the Eth0 and Eth1 Fast Ethernet ports in a SIP-3 (DIN-rail model)
The cable used to connect a 10/100Base-Tx port should be an unshielded twisted 4 pair
category five cable (UTP-5) with 8-pin RJ-45 connectors. The cable length should not be
more than 100 m.
The UTP-5 cable is made up of eight copper wires that form the four twisted pairs, covered
in different coloured insulating material. FIGURE 9 shows the colour of the wires that make
up each one of the pairs, according to ANSI/TIA/EIA-568-A standard.
FIGURE 9 Unshielded twisted pair category five cable (UTP-5) with RJ-45 connector according to
ANSI/TIA/EIA-568-A standard
Straight-through cables must be used, see FIGURE 11, where the 4 pairs correspond at
both ends of the cable.
Instead of a second electrical port, the SIP-3 can have an optical 100Base-Fx port, which
will always correspond to Eth1, with connector type MT-RJ or type LC.
The cable required to make the connection should be a fiber optic cable made up of two
multimode optical fibers, one to transmit data and the other to receive it. Each of the fibers
should be 125 μm in diameter. The core and the cladding of the fiber are included in this
diameter, as can be seen in FIGURE 12.
The core can be 50 μm or 62.5 μm in diameter. The wavelength used should be 1300 nm
(multimode). The cable length should not be more than 2 km.
FIGURE 12 also shows the most important input and output optical power characteristics
according to the type of multimode fiber used.
The SIP-3 can have 1 or 3 COM (DB9 female) connectors, identified as COM 1, COM 2
and COM 3. FIGURE 13 shows the arrangement of these connectors in the unit.
FIGURE 13 Location of the three COM (DB9) connectors in a SIP-3 (DIN-rail model)
The COM 1 can be configured by software for RS-232 or RS-485 interface, whilst COM 2
and COM 3 for RS-232 interface.
1 DCD
2 RD
3 TD
4 DTR
5 GND
6 DSR RX–
7 RTS RX+
8 CTS TX– TX/RX–
9 RI TX+ TX/RX+
The SIP-3 has a service serial connector, identified as SRV, for accessing the unit through
a console. FIGURE 14 shows its arrangement in the unit.
Pin RS-232
2 RD
3 TD
5 GND
Data Asynchronous
When the SIP-3 is equipped with the wireless WAN interface, there is a SMA female
connector for antenna, identified as ANT, see FIGURE 15, and two slots for housing Mini
Sim (2FF) cards, identified as SIM A and SIM B, see FIGURE 16.
FIGURE 15 Detail of the female SMA antenna connector in a SIP-3 (DIN-rail model)
Check that the unit ANT connector is firm and not loose and that it is not damaged or
dented, and that it makes good connection with the conducting core of the antenna cable
connector.
FIGURE 16 Detail of the slots for housing SIM cards in a SIP-3 (DIN-rail model)
Both SIMs CANNOT be activated simultaneously. In the case of dual SIM operation, one
SIM behaves as the primary one and the other as the secondary or back-up one.
The inserting and removing procedure of the SIM cards is indicated in the attached detailed
drawing.
SIM card
Card holder
Step 1: Put the SIM card into the card holder, Step 2: Snap the card onto Step 3: Fully insert the card holder, with
as shown in the figure. the card holder. the card located at the bottom,
in the corresponding slot.
Step 1: Using a sharp object, press the button Step 2: When the card holder appears, Step 3: Finally, remove the SIM card
at one end of the slot in order take it with the fingers and from the card holder.
to release the card holder. finish the removal.
Pertenece a: Cód. Prod. Rev.
SIP-3
- 0
Fecha Realizado Vº Bº Comprobado Vº Bº Aprobado Vº Bº Archivo
14-02-2017 J. F. Gil MGSIP30200
Siglas Hoja
INSERTION AND REMOVAL OF THE SIM CARDS
SIP-3 1/1
SIP-3
3 LED SIGNALLING
The SIP-3 has on the front plate two basic LEDs (SRV and ON), and several specific LEDs
associated with the different interfaces.
The location and identification of the LEDs can be seen in FIGURE 17.
LED Session Green. It stays on when the operator session has been
established for the wireless interface.
LED Net Green. It flashes when the wireless interface has been
registered in the operator network, except in the case of SIP-3
units with PHS8 modem in which it stays on.
LED SIM A/B Two-coloured. It stays on, indicating which of the two SIMs is in
use.
The SIP-3 can be managed locally and remotely, through a console or through a built-in
web server (HTTP/HTTPS).
It is assumed that the user has a basic knowledge of IP addressing and networking devices
such as hubs, switches, routers, etc.
All the parameters controlling the unit operation are described in detail in chapter 5, using
the HTML pages as an auxiliary graph example.
4.1 CONSOLE
The SIP-3 provides a user console application called CLI (Command Line Interface),
enabling information about the unit status (traces) and configuration parameters to be
obtained.
Appendix B contains all the information required to use the CLI user console. The appendix
explains the access methods, commands available on the console and how to obtain
information on the status and configuration of the unit.
The HTTP server included in the unit provides access to the HTML pages that gives access
to all the configuration data.
In order to access the HTTP server included in the ZIV unit, the IP address and mask of the
management PC have to be properly configured.
If the ZIV unit and the PC are connected directly or through a LAN (they belong to the same
network), the IP address of each of them must have the same network number and
different host numbers. The subnet mask must be the same for both. The default gateway
does not need to be configured. FIGURE 18 shows an example of configuration.
The factory IP address of the ZIV unit is 192.168.0.1 with mask 255.255.255.0.
All the parameters controlling the SIP-3 operation are described below in detail, using the
real HTML pages as an auxiliary graph example.
Whenever changes are made, regardless of whether they are made through the console
or the HTTP server, the unit must be informed what is to be done with them. There are
two options:
- the first is to execute the Apply command, which entails the immediate use of the
changes made.
- the second is to execute the Save command, which means that the changes will be
operative once the unit is rebooted.
If accessing through the HTTP server, after making the changes and before executing
Apply or Save, the Send button must be pushed to allow the unit to obtain the new
desired values.
If executing the Apply command, if the changes are required to be permanent, the Save
command must also be executed.
The only exceptions are changes affecting the SNMP configuration. Changes made to
the SNMP agent configuration will only be active after RESETTING the unit. The Apply
command is not sufficient, and so the changes must previously be saved using the Save
command before requesting the re-initialisation.
For information about the Reboot, Reflash, Configuration files and Event files, see
sections 5.15, 5.16, 5.17 and 5.18, respectively.
The Apply, Save and Reboot commands request the user to confirm the operation before
being executed.
The general parameters are grouped on the first page, see FIGURE 20, which is shown
when the SIP-3 validates the user identity.
The tree menu is permanently displayed on all the pages used by the HTTP server.
The identification zone has three parameters; the unit name (hostname), its location
(location) and the contact data of the responsible person or company (contact). At least
one string of text is required, with at least one character.
The DHCP client ID configures the Client ID option of the RFC 2131 in DHCP configuration
requests. If this parameter is not configured, the MAC address of the interface on which the
request is sent is used as a default value for the Client ID.
The identification parameters coincide with those assigned with the same name in the
SNMP data.
Access control allows the user logins and associated passwords to be determined for the
two pre-set profiles: guest and admin.
The guest profile can only access query operations. On the contrary, the admin. profile has
access to all the system configuration data.
As summarised in TABLE 1, the default values of these parameters are guest and admin
as the logins, with passwd01 and passwd02 being the respective passwords.
It should be borne in mind that the system makes a distinction between upper and lower
case characters.
Login Password
It is highly recommended to change at least the password of the admin. profile when
executing the first configuration in each unit.
It is advisable to store the new password in some type of register as, should the new
password be forgotten, it is not possible to access the web server.
5.1.3 Others
This section deals with four parameters. The first of them sets the hour zone in relation to
UTC.
The second parameter, Enable periodic reset, allows users to indicate whether they want
to reboot the unit automatically every so often. This is set by the next parameters.
The Start of the reset parameter set an exact date and time for the restart of the device or,
with the boot value, configure that the restart of the device is carried out when, since the
last restart, the time configured in Periodic reset period has elapsed.
The Periodic reset period parameter set how often the device will restart automatically.
Time is expressed in days, hours, minutes and seconds. The minimum value is 5 minutes.
5.1.4 Syslog
This section deals with four parameters. The first of them, Local Syslog Level, sets the
maximum level of severity which is stored in the local Log. Valid values are 1 to 8. The
default value is 4.
The levels involve storing all information tagged with a level equal to or lower than the level
specified.
Level Description
Error. Level 4 An application has exceeded it file storage limit and attempts
to write are failing.
Warning. Level 5 May indicate that an error will occur if action is not taken. For
example, a non-root file system has only 2GB remaining.
Notice. Level 6 Events that are unusual but not error conditions.
The second parameter, Remote Syslog Level, selects the maximum severity level to be
sent to the Remote Syslog server. Valid values are 1 to 8. The default value is 4. See
information about the levels in the previous parameter.
The third parameter, Syslog Log, is a Checkbox control. By default, it is NOT selected,
which means that a remote server is configured, and the traces are NOT stored in the local
Log. When the control is selected, the traces are sent to the remote server and are also
stored in the local Log with the corresponding severity level.
The last parameter, Syslog Server IP, sets the IP address of the Remote Syslog server to
which the information is sent.
The system can order the selective activation/deactivation of log information associated
to some operating blocks (see command log).
Through CLI it is possible to consult the local log files other than the current one (see
command show).
The unit has an integrated HTTP server for management purposes. The server supports
the HTTP and the HTTPS protocols, and users can selectively enable their use and the
respective port.
The following files can be found in the root directory of the FTP server:
• Auth
• Auth.0
• Conf.txt
• Conf.xml
• CoverageFile_x
• Customer.txt
• Events
• Events.0
• Messages
• Messages.0
• Messages.1
• Messages.2
• Messages.3
• Security
• Security.0
The credentials for accessing the FTP folder are the same as for accessing the unit.
The FTP Idle Timeout (s) parameter is the idle timeout in an FTP/FTPS established
connection. Valid values are 0 to 3600 seconds. A value 0 for idle timeout means that the
feature is disabled.
Telnet and SSH servers can be disabled, although by default they are enabled. The service
ports can be configured and, in the case of the SSH server, the idle timeout as well. For this
last parameter, valid values are 0 to 300 seconds. A value 0 for idle timeout means that the
feature is disabled.
In addition, RSA, DSS and ECDSA keys can be enabled/disabled separately for SSH
connection.
The procedure for the installation of the certificates is described in section B.4 of
Appendix B, Data structure in CLI.
The LAN menu contains the configuration data of the operation parameters of the Fast
Ethernet ports.
The main screen associated with the LAN menu is used to indicate whether the two
Ethernet interfaces form a two-port Ethernet switch (Dual Ethernet box not selected), or if
they are independent interfaces (Dual Ethernet box selected).
Port configuration is then carried out through the eth0 and eth1 submenus.
Configuration data associated with eth1 interface affect the behaviour of the unit only when
the Dual Ethernet option is selected.
The screen related to each eth submenu of the LAN menu has two well differentiated
sections, which are described below.
LAN:
The main IP address and its mask may be obtained automatically through the DHCP client,
which is called dynamic or NON-static configuration. The user may activate this feature
through the CheckBox type control with the Static IP label. When the control is ticked, the
unit uses the data provided by the user.
IP Alias:
The unit is capable of responding to IP addresses different from the main one if they have
been previously added through the Add CommandButton.
The Serial menu provides access to the configuration page of the operation parameters of
the unit serial ports (COM).
The unit has 1 asynchronous serial port, COM 1, configurable by software for RS-232 or
RS-485 (2-wire or 4-wire) interface. Apart from the previous, the unit can have two
additional RS-232 serial ports (COM2 and COM3).
The screen related to the Serial menu has two well differentiated sections, which are
described below. See section 1.2 for more general information about the port
interconnection.
Physical:
• #. It identifies the unit physical port number. Port 1 for port COM1, Port 2 for port
COM2 and Port 3 for port COM3.
• Interface. It selects the interface type. By default, RS-232. Port 1 is the only port
that also supports RS-485 interface at 2 or 4 wires.
• Baudrate. It selects the serial port data rate. Valid values are 600, 1200, 2400,
4800, 9600, 19200, 38400, 57600 and 115200 bit/s.
• Stopbits. It selects the number of stop bits. Valid values are 1 and 2.
• Flow control. It selects the flow control mechanism. Valid values are none,
hardware (control signals) and software (Xon and Xoff).
Logical:
• #. It identifies the unit physical port number. Port 1 for port COM1, Port 2 for port
COM2 and Port 3 for port COM3.
• Mode. It selects the port operation mode: flow or emulator. By default, Flow, that
is, serial port mode. The emulator mode implies the activation of the HAYES
modem emulator additional characteristic, and it should only be selected to define a
ModemEmulator behaviour for the port, which is similar to a HAYES modem. In this
last case, there are additional options in the ModemEmulator menu.
• Protocol. It sets the protocol of the data to be encapsulated. Valid values are raw
(without processing, it is transparent to the information), packed, (the data will be
grouped in packets according to the related parameters, being also transparent as
regards the encapsulated information), one of the identifiers of the telecontrol
protocols being hold (iec101_1, iec101, iec102_1, iec102, pid1, dlms, gestel,
sap20, twc, dnp3, procome, iec103, modbusrtu, modbusrtu_cc) or the policy-based
mode (policybased).
• Policy. This field should be configured when the policybased mode has been set
in the Protocol parameter. It sets an identifier, whose policy should be configured in
the Policy submenu of the Flow menu.
• Packed time (ms). This field should be configured when the packed mode has
been set in the Protocol parameter. It sets the maximum waiting time after receiving
the last character, in ms, before sending a packet with the data received so far. It
forces sending the data for inactivity time when not reaching the data selected as
desired packet size (see next parameter).
• Packed size. This field should be configured when the packed mode has been
selected in the Protocol parameter. It selects the maximum number of characters to
be transmitted in a packet on the network.
This menu only appears when the SIP-3 device has the optional wireless WAN interface.
The submenu has four different sections, which are described below.
WAN:
• Enable Wireless WAN. This allows the WAN interface of the device to be enabled
and disabled by selecting ON and OFF, respectively.
Selecting the ON option will make the device try a new GPRS/UMTS/HSDPA/LTE
session, in accordance with the subscriber data (PIN, APN, Authentication method,
user, password). In the case of dual SIM functionality, the subscriber data will be
those corresponding to the primary SIM.
The OFF option disables the WAN interface, and is the default option.
Consequently, you should enable this option if you want the GPRS/UMTS/LTE
service, after FIRST configuring the necessary parameters for setting the
operator session.
• Primary SIM. In the case of dual SIM functionality, this permits users to determine
which of the two available SIMs will behave as the primary one: SIMA or SIMB. In
this operation mode the SIM that is not selected is therefore the secondary or back-
up SIM. It is also possible to set an operation mode with alternation of the SIMs
(alternated) each time the unit is started up, as well as an operation mode for
random selection of the primary SIM each time the unit is started up (random).
• Request DNS. Tick this box and the unit will request the addresses for DNS
servers if connected to the GPRS/UMTS/LTE service.
• Maximum time to connect (minutes). This specifies the time in minutes (0 to 20)
for the unit to wait in order to obtain the WAN IP address from the operator. If after
that time, a WAN IP has not been obtained, the unit will be rebooted.
In the case of dual SIM functionality, it must be taken into account that the
Maximum time to connect counter starts operation at the same time that the
Maximum number of retries counter. In this way, the unit will be rebooted when
one of the two counters reaches at zero, that is to say, when it is not possible to
connect once the number of retries of both SIMs has been used up (see Maximum
number of retries counter) or once the time configured in the Maximum time to
connect counter has been used up.
It is therefore advisable to give a higher value in the Maximum time to connect
than in the Maximum number of retries.
The value 0 of the parameter, with dual SIM enabled, disables the reinitialization of
the equipment due to the impossibility of establishing the configured connection
while maintaining the alternation between the use of the SIMs.
• Low Coverage Level Alarm. It specifies the coverage level under which the low
coverage level alarm should be activated.
• Low Coverage Alarm Period. It specifies the time the coverage level should
remain below the level indicated in the previous paragraph before the low coverage
alarm is activated.
• Quality Sample Period (sec). This parameter defines the period of time that the
unit uses for sampling the received signal measure, RSSI when operating on a 2G
network, RSCP and EC/n0 when the network is 3G or RSRP and RSRQ when the
network is 4G.
• Quality Evaluation Period (sec). The user defines the period of time and thus,
indirectly, the number of samples of the received signal measure to determine
compliance with minimum quality. The signal value is individualized for each
possible operator and network type, see Min Signal GPRS, Min Signal UMTS and
Min Signal LTE. The criteria for determining if the level is correct or not is that all
samples of the current evaluation period does not meet the minimum set.
• Enable dual SIM. This box must be ticket to determine whether the unit will use the
secondary SIM or not. It enables the options: SIMB, alternated and random.
• Enable inactivity time for datacalls. Selecting this box determines if the unit will
use the next parameter.
• Inactivity time for datacalls (s). It sets the inactivity time in seconds that will imply
the voluntary and controlled shutdown of the GSM datacall connection.
• PIN 1 and PIN 2 values. These are the safety codes associated with the SIM card.
Normally, PIN1 is sufficient to access the general services provided by the
operator. Check that the code entered is correct. Entering a wrong code will block
the SIM card.
Once the PIN 1 and PIN 2 values are introduced from the Change option,
execute the send command of said option, and then, if you want the values to be
applied and saved in the device, DO NOT forget to execute the apply and save
commands from the main menu tree.
• Preferred network. This allows the device behaviour to be specified in the case of
a failure in coverage. When GPRS is selected, the device will only connect to a 2G
network. If UMTS is selected, the device will only connect to a 3G network. If LTE
is selected, the device will only connect to a 4G network. In the ANY option, the
device supports any technology and, in the absence of coverage, it will switch from
one network to another.
When UMTS_GPRS is selected, the device will connect to a 3G network and, in the
absence of 3G coverage, it will connect to a 2G network.
• Force Home Network. On ticking this box connection with the operator of the local
network associated with the SIM card is forced (home network). If this option is
selected, the unit will not connect to any operator other than the one specified.
• User Name. User name selected by the operator during the authentication process
(see preceding point).
Once the Password is introduced from the Change option, execute the send
command of said option, and then, if you want the password to be applied and
saved in the unit, DO NOT forget to execute the apply and save commands
from the main menu tree.
• Min Signal GPRS (dBm). This parameter allows a minimum level of received
power to be specified (RSSI in dBm) as a quality parameter for the GPRS (2G)
connection. The minimum value is -113 dBm (default value), and the maximum
value is -51 dBm.
• Min Signal UMTS (dBm). This parameter allows a power minimum level of the
received signal to be specified (RSCP in dBm) as a quality parameter for the UMTS
(3G) connection. The minimum value is -125 dBm (default value), and the
maximum value is 0 dBm.
• Max EC/n0 UMTS (dB). This parameter specifies the maximum threshold of the
EC/n0 measure to be considered as acceptable. The minimum value is -25 dB, and
the maximum value is 0 dB.
• Min Signal LTE (dBm). This parameter allows a power minimum level of the
received signal to be specified (RSRP in dBm) as a quality parameter for the LTE
(4G) connection. The minimum value is -140 dBm (default value), and the
maximum value is -44 dBm.
• Max RSRQ LTE (dB). This parameter specifies the maximum threshold of the
RSRQ measure to be considered as acceptable. The minimum value is -20 dB, and
the maximum value is -3 dB.
• Min Coverage (%). The system calculates the coverage as a percentage from the
received power (RSSI), in the case of 2G networks (see TABLE 2), or as a
combination of the received power (RSCP) and the EC/n0 measure, in the case of
3G networks (see FIGURE 26), or as a combination of the received power (RSRP)
and the RSRQ measure, in the case of 4G networks (see FIGURE 27).
This parameter sets the minimum threshold required to be evaluated.
0 0% <-113 dBm -
1 0% -111 dBm -
2 1% -109 dBm -
3 1% -107 dBm -
4 2% -105 dBm -
5 2% -103 dBm -
6 3% -101 dBm -
7 3% -99 dBm -
8 4% -97 dBm -
9 5% -95 dBm -
10 6% -93 dBm -
11 11% -91 dBm 1
12 17% -89 dBm 1
13 23% -87 dBm 2
14 29% -85 dBm 2
15 35% -83 dBm 3
16 41% -81 dBm 4
17 47% -79 dBm 4
18 53% -77 dBm 5
19 59% -75 dBm 5
20 65% -73 dBm 6
21 71% -71 dBm 7
22 77% -69 dBm 7
23 83% -67 dBm 8
24 90% -65 dBm 9
25 92% -63 dBm 9
26 94% -61 dBm 9
27 96% -59 dBm 9
28 97% -57 dBm 9
29 98% -55 dBm 9
30 99% -53 dBm 9
31 100% >-51 dBm 10
FIGURE 26 3G coverage measurement depending on the received power (RSCP) and EC/n0 measure
FIGURE 27 4G coverage measurement depending on the received power (RSRP) and RSRQ measure
o Signal: The system will analyze RSSI (2G), RSCP (3G) or RSRP (4G) as
the only measure of quality.
o Coverage: The system shall refer the measure Min. Coverage with the
corresponding configured value to evaluate the compliance of the required
level.
o Signal_and_ecn0/rsrq: The system will monitor both RSSI (2G) / RSCP
(3G) / RSRP (4G) signal and EC/n0/RSRQ, and for the quality criteria to be
satisfied, both measures must meet the corresponding thresholds
simultaneously and for the entire evaluation period.
o Signal_or_ecn0/rsrq: The system will monitor both RSSI (2G) / RSCP
(3G) / RSRP (4G) signal and EC/n0/RSRQ, and quality criteria are satisfied
if one of the two measures meets the corresponding threshold for the entire
evaluation period.
o ecn0/rsrq: The system will analyze EC/n0 or RSRQ as the only measure
of quality. Applicable only operating on 3G or 4G networks, respectively.
Dynamic DNS:
A dynamic DNS service permits the assigning of a DNS name to the unit with a
non-permanent IP address, and the Dynamic DNS client is responsible for updating it
when it changes. In this way, from the user standpoint the unit is always accessible via
a DNS name, and so it is not necessary to always know the IP address assigned.
The Dynamic DNS client is entrusted with connecting to the chosen server and
updating the IP address.
To use the Dynamic DNS client, users must first register the DNS name of the unit
with the service provider. The client can only update the IP address.
• Dyn Service Id. Allows you to select one of the dynamic DNS service providers
supported.
• Login and Password. It sets the user name (login) and password (password) for
accessing the service provider.
• Host name. Name of the unit registered with the service provider, i.e., the name of
the unit used to identify the SIP-3 via DNS.
• Time interval (seconds). Time between accesses for the Dynamic DNS client to
update the IP address.
• Remote IP1 and Remote IP2. This selects the IP addresses of the unit with which
accessibility will be checked, through the sending of ICMP (ping) packets. If the
fields are at 0.0.0.0 this means the "Ping Test" function is disabled. It is sufficient
for any one of the remote unit to respond to consider the accessibility test valid. A
field with the value 0.0.0.0 means that the option is not enabled.
• Frequency (minutes). This allows the time passing between the sending of ICMP
(ping) packets to be specified.
• Timeout (secs). This allows the maximum response time to the ICMP (ping)
packets sent by the Ping Keep Alive function to be specified. Valid values are 5 to
60.
• Size of ICMP packets. This allows the size of the ICMP packet to be specified.
The configuration consists of indicating the extra bytes to be added to the smallest
ICMP packet, which is, by default, 28 bytes.
• Number of ICMP packets. This allows the number of ICMP packets that are sent
in each verification to be specified.
• Max Lost Ratio (%). This allows the maximum valid percentage of failure in the
Evaluation period to be specified for the results of the Ping Keep Alive messages.
• Action. This selects the desired behaviour of the unit if the accessibility test is
failed. The options are: None (no action taken), Reconnect (set up a new
GPRS/UMTS/LTE session) or Reboot (reboot the unit).
• Strict. This option allows users to inhibit the accessibility test when there is traffic.
If the option is not activated, the test will only be executed when the period of time
indicated in frequency without traffic has passed. When the option is enabled, the
test will be performed regardless of whether traffic is present or not.
In the figure given as an example in the Ping Keep Alive configuration, connectivity
of the IP addresses 192.168.1.5 and 192.168.1.10 is verified every 15 minutes by
sending 2 ICMP packets of 29 bytes (28+1). In case of failure, the behaviour is
Single and, in this case, if there is no response to the "Ping Test", the unit will be
rebooted.
FOTA:
This functionality is available on SIP-3 devices with a 3G modem (HE910).
It is used to update the version of the communications module via WAN, by means of a
file posted on an FTP server.
This file is a differential version, that is, it is not a complete version but it contains the
difference between a previous version and the next.
The recommendation is to configure the field associated with the IP address of the FTP
server, the fields associated with the login credentials (user and password) to access
the FTP, the field associated with the route within the FTP server where the update file
is located, and the field associated with the name of the file.
Next, enable FOTA by selecting the Enable box.
After the configuration, execute the Save and Apply commands.
In doing so, the download of the image and the reflash process of the unit will start.
Once the process is finished, the unit will restart with the new software.
The Routing menu contains two submenus: Static Routes and DNS servers.
By means of the Static Routes submenu of the Routing menu, the user can provide the
system with the static and permanent data for the routing service.
Explicit static routes are configured in the Static Routes section. The address acting as a
route by default in the case that the service has no specific data for reaching a destination
is configured in the Default Static Routes section.
If the unit has the optional wireless interface, the operator will not only provide the IP
address of the interface but also specifies a default router associated with that interface,
which takes precedence over any configuration set by the user.
FIGURE 29 Configuration page of the Static Routes submenu of the Routing menu
Static Routes:
The parameters for configuring a static route are:
• Destination. This allows the IP address to be specified, and the remote or destination
network subnet mask. The field requires the values to be entered in the IP address
format. Example: 192.168.0.0/255.255.255.0 or 192.168.0.0/24.
• Service. This allows an additional filter to be set in the remote IP address for
determining the selection of the next jump. The condition is set based on a specific
service (tcp/udp/icmp). After the service the port number (1÷65535) must be indicated,
separated by two points. The default value is any, that is to say, the route applies for all
types of traffic (only the IP destination is taken into account). Example: tcp:5000, which
means that all the packets with tcp traffic on port 5000 will be sent to the indicated
router.
• Dest I/F (Destination interface). This allows the interface through which the routed
traffic coinciding with this route will be sent.
Example:
The figure shows an example of assigning a static route between two different network
segments. All the TCP packets of port 40000 can reach the network segment 172.23.0.0/24
through router 192.168.0.11.
• Gateway. This allows the IP address of the next router to be specified for routing traffic
whose destination does not coincide with any known route.
• Dest I/F (Destination interface). This permits the specification of the interface through
which traffic routed to the router indicated in the previous field will be sent.
• Metric. This permits a value to be specified originating from among the default different
routes that could be created. A higher metric means a lower priority.
If the wireless interface is operative, this parameter must be different and higher than
1, the value 10 being recommendable as values higher and next to 1 could be
reserved to other routes set by the operator.
The DNS servers submenu of the Routing menu provides access to the configuration
screen through which the user can configure the DNS server addresses manually.
• Enable DNS resolver. Enables the DNS service. The DNS servers can be
configured manually when the option is selected.
For proper operation of this service, the DHCP client must NOT be configured.
The Filtering menu permits firewall functionalities, defining which traffic is allowed and
which traffic is rejected and the application of additional conditions to the traffic processed
through the routing function.
The menu parameters are divided into three quite different blocks, which are:
− Filtering of packets through the incoming/outgoing service for the Ethernet (eth0/eth1)
interface.
• Origin. This allows the IP source of the traffic to be specified, i.e., from a specific
IP address or any IP address (any). The default value is any. The specification of a
particular IP address requires the values to be entered in the IP address format.
Example: Subnet (192.168.50.0/255.255.255.0 or 192.168.50.0/24) or Host
(192.168.50.5/255.255.255.255 or 192.168.50.5/32 or 192.168.50.5). Only present
in the sections in which this makes sense.
• Service. This allows any type of traffic to be specified (any) or a specific traffic
(tcp/udp/icmp). The default value is any. If a specific traffic is indicated, the port
number can be indicated together with the service, if required (1÷65535) or a
range. Example: tcp or tcp:23 or udp:5001-5005.
• Dir. This allows the traffic direction to be specified, i.e., whether it is incoming (in)
or outgoing (out).
• Policy. This allows the filtering policy to be specified (accept, drop or reject).
When the filtering policy is accept, only packets complying with the selected rule
are accepted. When the filtering policy is drop, on the other hand, packets
complying with the selected rule are dropped. The reject filtering policy also rules
out packets complying with the selected rule, but unlike drop, when the packet is
ruled out, the appropriate ICMP message is sent to the source address of the
packet.
• Default Policy. This allows the behaviour of the device filtering to be determined
as regards not being included in any specific rule of the respective section.
A filtering policy is to be set to eliminate traffic present in the Ethernet (eth0) interface
coming from host 10.0.0.5, whose destination is within the IP range 192.168.0.0/24. The
eth0 block configuration will be that shown in the figure.
NAT is the IP address translation service which allows users to combine the use of private
IP address without this preventing them from accessing resources with a public IP address,
or preserve the address schema in different interconnected network areas.
The NAT menu defines the rules that allow IP addresses to be selectively translated and
change the transmission service ports.
• Origin. This selects a range of IP addresses. It admits the value any, in the case
that the origin IP address is not relevant.
• Destination. This selects a range of IP addresses. It admits the value any, in the
case that the IP destination address is not relevant.
• Transl. Origin. This selects the IP address that must replace the origin IP. An IP
address may be specified or the respective interface identifier. In the case of not
wanting to change the original address, the value must be original.
• Transl. Dest. This selects the IP address that must replace the destination IP. An
IP address may be specified or the respective interface identifier. In the case of not
wanting to change the original address, the value must be original.
• T. Dest. Port. This selects the identifier of the port that must replace the
destination port in the packet. It admits a range configuration. In the case of not
wanting to change the destination port, the value must be original.
The SIP-3 has a built-in DHCP server which allows IP addresses to be assigned
automatically to the unit requesting this.
• Enable DHCP server. This allows the DHCP service to be activated. The DHCP
server is operative when the option is selected.
• First IP Addr. Allows the first IP address of the IP addresses pool managed by the
DHCP Server to be specified.
• Last IP Addr. Allows the last IP address of the IP addresses pool managed by the
DHCP Server to be specified.
• Mask. This selects the net mask that will communicate with the DHCP clients.
• Default Gateway. This selects the default router address (Default Gateway) that
will communicate with the DHCP clients.
• Lease time. This allows the time in seconds to be specified for an IP address to be
assigned following a request from a DHCP client. After the indicated time, if the
DHCP has not requested a renewal, the IP address will be considered available for
dealing with new requests.
• 2nd DNS server. This allows the IP address of a secondary DNS server to be
specified to the DHCP client. If left blank (0.0.0.0) this means that no information
will be sent to the client in this respect.
• WINS server. This allows the IP address of the WINS server to be selected, which
will be notified to the DHCP client. WINS is a names resolution system owned by
Microsoft for units executing the Windows operating system.
• DNS Domain Name. This sets the DNS domain to be used by the client for
creating its full DNS name.
• Boot TFTP Server. This selects the IP address of the TFTP server that stores the
remote boot file, thereby allowing the client to execute a request to download the
file.
• Bootfile Name. This selects the name of the remote boot file which the client will
request from the TFTP server configured in the preceding point.
The unit has an SNMP agent with the capacity to generate spontaneous messages to
control units, based on that protocol.
The agent admits the emitting of messages based on the SNMPv1 [1] y SNMPv2c [2] and
SNMPv3 protocol, and the selection of the type of message, trap and inform.
Changes made to the SNMP agent configuration will only be active after RESETTING
the unit. The Apply command is not sufficient, and so the changes must previously be
saved using the Save command before requesting the reboot.
• Enable: Enables/disables the execution of the SNMP agent. The agent is operative
when the option is selected.
• User: Parameter associated with SNMPv3. Tabulate information that allows the
users, including the privileges and the operating mode associated with each user,
to be defined. That is to say, the rights of access (Access), read only rights (ro) or
reading/writing rights (rw), and the way in which the data transference (Security)
will be carried out, without encryption (clear), authentication (auth) or authentication
and encryption (priv).
In case of authentication transmission (auth), it is necessary to select the type of
algorithm (Auth Alg.), MD5 or SHA, and configure the authentication password
(Auth Password). The password sets the word to be used to generate the
authentication information. The authentication word must be known by the receiver
in order to be able to verify the authenticity of the identity of the transmitter.
The password is not shown for security reasons and so when it is changed
(Change option), it must be entered twice.
Once the Password is introduced from the Change option, execute the send
command of said option, and then, if you want the password to be applied and
saved in the unit, DO NOT forget to execute the apply and save commands
from the main menu tree.
SNMP Traps:
• Traps SNMPv1/v2c: Tabulate information allowing several destination units for the
traps to be defined.
For each of the spontaneous SNMP message addressees, a profile must be
provided, which must be included in the spontaneous message, the SNMP protocol
version with which it will be coded, the IP address of the addressee and the UDP
port to which the messages will be sent. The default value configured in the
standard is port 162. It can be changed to adapt to the operating data of each
addressee.
The transmission of the messages in a confirmed (inform) way is only accepted for
the v2c and v3 versions of the protocol.
• Trap v1 agent address: This selects the IP address the agent will communicate as
being its own when sending spontaneous messages. This parameter is only used
to create the traps when using SNMPv1.
• Traps SNMPv3: Tabulate information allowing several destination units for the
notifications to be defined.
The receivers are identified by means of their IP address and the UDP port to
which the notifications are to be sent. The standard UDP port for the SNMP
notifications is the 162, being the value by default.
The Type control is used to select whether the transmission of the notifications is
carried out in an unconfirmed (trap) or confirmed (inform) way.
The unit has an NTP/SNTP client, meaning that it can synchronise time-related information
by accessing NTP servers. The NTP [3] protocol is a standard that is widely used in
TCP/IP-based networks. It admits the use of several NTP servers simultaneously, and the
option of using authentication.
The SNTP variant means a faster synchronization but less accurate and, on the other hand,
it is necessary to run it periodically.
• Enable. Enables/disables the execution of the NTP client. The client is operative
when the option is selected.
The NTP client supports the configuration of multiple NTP servers to carry out
synchronization. Each has a set of customized parameters that determine the access
procedure:
• Type. This sets the type of messages to be sent to the NTP server. The messages
can be individual (unicast) or collective (manycast).
• Minpoll. Minimum time between requests. The parameter is the exponent of the
power of 2 that corresponds to the minimum period.
• Maxpoll. Maximum time between requests. The parameter is the exponent of the
power of 2 that corresponds to the maximum period.
There is an additional parameter not dependent on the configuration of NTP servers that
sets whether broadcast NTP-type messages will be accepted.
• Accept broadcast. Enables the acceptance of NTP messages that are received
with broadcast address.
The SNTP client only supports the configuration of a server, and the necessary parameters
are:
• Poll. This sets the period of generation of synchronization messages. Valid values
are 1 to 60.
• Units. Time unit for the period of generation of synchronization messages. It can
be minutes or hours.
The unit offers users several means of access: operating console, access via HTTP/HTTPS
server (web), SSH, telnet and FTP access.
Local users predefined in the system are always present but an external resources can be
used to validate users for different types of access, for which reason the user database is a
centralised and independent resource with respect to the unit itself. For this purpose the
unit has a TACACS+ client.
• Encrypted. This permits user to select whether the unit communication with the
TACACS+ servers must be made in the ciphered mode or not.
• Secret Shared Key. This selects the code to be used for ciphering the
communication when the encrypted option is active.
• Guest Privilege Level. This sets the privilege level (0 to 15) in the request to the
TACACS+ server to gain access as guest user (guest). The privilege level must be
consistent with the one configured in the TACACS+ server queried.
• Admin Privilege Level. This sets the privilege level (0 to 15) in the request to the
TACACS+ server to gain access as administrator user (admin). The privilege level
must be consistent with the one configured in the TACACS+ server queried.
The parameters associated with each access option (console, web, telnet, SSH and FTP
access) are the following:
• Authentication method. This sets whether the user validation must be made
locally or by consulting the configured tacacsplus servers.
The Flow menu basically permits the virtual ports (TCP/UDP) configuration parameters to
be selected, as well as to define the connections and/or flows between any of the available
interfaces. See section 1.2 for more general information about the port interconnection.
Each one of the ports should be configured for operation with a specific protocol, either to
operate in transparent mode (raw and packed), with one of the telecontrol protocols
being hold or with a policy defined by the user.
Some protocols have multiple identifiers, which not only indicate the protocol itself, but also
the size of the link address, when the standard requires it as a user option.
The protocols with multiple identifiers and values related to them are listed below:
• iec101_1. IEC 60870-5 101, with FT1.2 frame and a link address size of 1 byte.
• iec101. IEC 60870-5 101, with FT1.2 frame and a link address size of 2 byte.
• iec102_1. IEC 60870-5 102, with FT1.2 frame and a link address size of 1 byte.
• iec102. IEC 60870-5 102, with FT1.2 frame and a link address size of 2 byte.
Although always present in the configuration registers, the next parameters are only useful
when the packed protocol is selected.
• Packed time (ms). It selects the maximum waiting time after receiving the last
character, in ms, before sending a packet with the data received so far. It forces
sending the data for inactivity time when not reaching the data configured as
desired packet size (see next parameter).
The operation of the datacall will depend on the services permitted by the operator,
especially in 3G and 4G networks. To receive the datacall on SIP-3, the GPRS
connection (forced to 2G) must generally be configured as the preferred network.
NOTE: In SIP-3 devices with PHS8 modem (3G), datacall will not be possible from a PSTN type
analog modem.
Physical Ports:
• Serial #. It identifies the unit physical port number. Port 1 for port COM1, Port 2 for
port COM2 and Port 3 for port COM3.
• Identifier. It selects a different and unequivocal name for each one of the serial
ports configured in the Serial menu. All the ports have the name serial0 configured
by default, and therefore, it is essential to assign a specific name to each of them.
The parameters to configure a serial-datacall (GSM) connection appear if the SIP-3
is equipped with the optional WAN interface.
• Identifier. It selects the identifier related to the GSM datacall; datacall0 is the value
by default.
• Use autocli. Upon receiving a data call, the unit connects the call to the cli
management service if this option is activated (ticked box); thus, it is equivalent to a
remote access to the service console. If the option is NOT activated (unchecked
box), the data call will be redirected to the physical port configured by the user in
the Connection block (see section 5.13.2).
• Escape sequence. If the data call does not have direct access to the management
service, but to a determined port (autocli parameter NOT activated), it is still
possible to access the cli management service by inserting the escape chain
defined in this parameter. If the cli management service is accessed through the
escape sequence, it is necessary to end the call and establish it again in order to
recover the initial data flow.
Virtual Ports:
• Full UDP.
#. It is a sequence identifier provided by the unit itself.
Identifier. It selects a different and unequivocal name for each one the bidirectional
UDP virtual ports. When added, all the ports have the name fulludp0 configured by
default and, therefore, it is essential to assign a specific name to each of them.
Interface. It selects the possible interfaces the data will be accepted on; therefore,
it restricts the possible input points of the packets. The possible values are the
following: all, eth0 or cell0, if the unit has the WAN interface.
Local Port. It selects the UDP port to be used to receive packets.
Group-ID. Multicast IP address that will accept data in reception, as long as the
parameter value is a valid address, and the multicast option is active. The 0.0.0.0
default value is not a valid IP address.
Remote Port. It selects the destination UDP port. If set to 0, the destination port
will be that of the last received UDP datagram.
Spy:
• Identifier. It selects a different and unequivocal name for each of the spy ports. All
the ports have the name sniff0 configured by default when they are added. For that
reason, it is necessary to assign a specific name to each of them.
• Header. It sets the text appearing before each one of the messages provided by
this instance in order to facilitate their origin if there are multiple spies.
• Mode. It sets the representation format of the data available in the spy connection.
Valid values are raw (original data format) or hex (hexadecimal representation).
• Enable. It sets if the spy port is active or not. The spy port is enabled if the box is
ticked.
Example:
The figure shows an example of a spy port definition to check the connection between a
serial0 port and a passivetcp0 port. In addition to defining the spy port (sniff0), it will be
necessary to define a port (passivetcp1) that will provide the information we are spying on.
5.13.2 Connection
The Connection submenu of the Flow menu permits defining the connections determined
by the physical and/or virtual ports, where the user traffic will be exchanged.
See section 1.2 for more general information about the port interconnection.
• 1st data flow. It determines the first port included in this connection through its
identifier.
• 2nd data flow. It determines the second port included in this connection through
its identifier.
It is essential to introduce the identifier name correctly in the two previous fields,
so that it is one of those set in the Physical ports and Virtual ports sections of the
Flow menu configuration screen. In order to avoid possible errors, it is advisable
to use the commands Ctrl.+C (copy) and Ctrl.+V (paste) instead of the keyboard.
In the case of unidirectional connections, the traffic flow is just from the port with
the identifier specified on 1st data flow towards the port with the identifier
specified on 2nd data flow.
• Enable. It sets that the connection is active. The connection, or flow, is enabled if
the box is ticked.
The size of the link address is specified when selecting the encapsulation protocol, or when
the encapsulation policy is defined (in this last case, only for iec101/102).
5.13.3 Policy
The Policy submenu of the Flow menu permits the creation of variants of some protocols,
which enhances the encapsulation functions (see bibliography [4]).
The protocols that admit said variants are the following: iec101/iec102, pid1, gestel and
sap20.
The additional functions implemented are designed for the use of the non-balanced mode
protocols so as to minimize the traffic between the encapsulation unit at the same time.
When the remote unit is in non-balanced mode, it can only send information to the
controlling unit as a response to explicit requests (polling mechanism). So, in order to have
response time to possible events that occurred and were detected by the remote entities,
the control center should transmit cyclic inquiry messages and with a sufficiently high
cadence. Therefore, these messages transit the TCP/IP network. The cyclical messages
that are part of the polling are called Quick Check (QC).
The enhanced functions imply that the cyclic inquiry of the polling mechanism will be
created and sent by the encapsulation unit connected directly to the remote unit. Only when
the remote responds to the QC messages will the encapsulation unit from the remote side
send them to the encapsulation unit from the controlling side to be delivered to the control
center. Thus, the control center is released of the cyclic inquiry mission and, in turn, the use
of the related wideband is avoided.
• Identifier. It selects a different and unequivocal name for each one the policies.
When added, all the policies have the name policy0 configured by default and,
therefore, it is essential to assign a specific name to each of them.
• Quick Check Mode. The none option means that the Quick Check enhanced
functions will not be executed. Any other option enables the Quick Check option
and, in turn, determines if the unit is connected to the control center (system), or to
the remote unit (rtu).
• Quick Check Period (secs). It selects the period of time for the local generation of
the QC messages to the remote unit.
• Quick Check Timeout. It selects the maximum waiting time for a response from
the remote unit to the transmission of a QC message by the encapsulation device.
• Link Address Size. Only for the iec101/102 policies. It selects the size of the link
address used in this profile, since these protocols admit two options as regards the
size.
5.13.4 Other
The Other submenu of the Flow menu permits the activation of some additional facilities,
mainly focused towards the obtainment of information to facilitate the resolution of possible
configuration errors or events.
The screen related to the Other submenu has three well differentiated sections, which are
described below.
Device:
• Identifier. This parameter specifies the identity of the related Control Center when
using Quick Check policies. It only applies to the unit working with the system
profile, that is, the unit the Control Center is connected to.
Socket:
• Maximum time with sockets down (min). It sets the maximum time acceptable,
in minutes, during which there is no connection between the unit executing Quick
Checks.
Debug:
The Transparent submenu of the Flow menu allows a transparent connection to be set up.
• Passive Port. Sets the passive TCP port on which the unit accepts a connection to
be relayed to another unit in a transparent way.
• Active IP. Sets the IP address of the destination unit to which the information of the
passive TCP connection will be retransmitted.
• Active Port. Sets the TCP port used to set up the TCP connection to the
destination unit.
The ModemEmulator menu implies that the unit is presented as a HAYES modem to the
client unit; thus, the connections are set automatically based on the parameters provided by
the client unit, through the dialling commands.
The HAYES emulation offers the following behaviours according to the received command:
ATDT. It launches a TCP connection whose addressee and port results from the
number included in the command itself. The number accepts two interpretations:
• Direct number, which corresponds to the IP address and the desired destination
port. It is a 17-digit number: 12 correspond to the IP address, and 5 to the
destination port. The IP address, as well as the port, should clearly include the
digits whose value is null. That is, the destination with the IP address
10.89.1.123 and the port 348 would suppose that the command to be sent would
be ATDT 010 089 001 123 00348 (there are intentional blank spaces in the
example chain to show the presentation mode, but there should not be included
in the actual command).
• To consult the configured Dialling Table. The table permits the translation of a
clearly arbitrary numbering plan to IP address and ports.
ATD*. The serial port behaves as a PPP server, requesting the credentials (user and
password) from the client unit, and providing an IP address to it. The indicated
parameters are selected in the registers included in the Modem Emulator table.
ATD. It launches a GSM datacall to the destination number included in the command
itself.
The following are other commands accepted by the device in emulation mode related to the
management of calls:
In addition, as regards the behaviour management as MODEM, the unit has the S2
register; it admits the configuration of the ECHO (E) parameters, management of the
DCD (&C) signal and management of the DTR (&D) signal, and it supports the following
standard commands: ATA, ATO, ATI, AT&F, AT&W and AT&V.
The screen related to the ModemEmulator menu has two well differentiated sections, which
are described below.
Modem Emulator:
• #. It is a correspondence identifier with the physical port (serial port) related to the
emulation function, to which the configuration register corresponds.
• Identifier. It sets a different and unequivocal name for each one of the
configurations. All of them have the name emulator0 configured by default and,
therefore, it is essential to assign a specific name to each of them.
• User. It selects the admissible user when the unit behaves as a PPP server.
• Password. It selects the password related to the PPP user from the previous field.
• Authentication method. It selects the standard protocol used for the exchange of
credentials with the external unit; the values are none (without authentication), pap
(Password Authentication Protocol) and chap (Challenge Handshake
Authentication Protocol).
• Own IP. The IP address related to the unit serial interface when acting as a PPP
server.
• Enable. It selects if the table should be used for the translation of the numbering
plan of the calls made with the ATDT command, or not.
• Telephone Number. The number of the numbering plan related to the register.
• Destination IP. The destination IP address for the number specified in the previous
parameter.
• TCP Port. The destination TCP port for the number specified in the telephone
number parameter.
5.15 REBOOT
The unit can be rebooted by executing the Reboot command, through the console or
through the HTML pages. The command is available only for the administrator profile.
The unit admits the updating of applicative software by executing the Reflash command,
which is only available in the HTML pages and for the administrator profile.
The code reflash process does not alter the configuration data, unless this is expressly
indicated. Nevertheless, once terminated, it entails a momentary loss of service due to
the automatic rebooting of the unit.
A binary image that is appropriate for the unit is necessary, which can be selected by
pressing the button Examine.
The Only verify option allows users to check that the code saved is coincident with the
binary image selected without affecting the installed image.
FIGURE 48 Options for uploading (Upload) or downloading (Download) the configuration file
The user must select the file containing the configuration to be uploaded by pressing the
button Examine.
In order to only verify the configuration without upload it, the Only verify box must be
ticked.
Once the unit has received the file, the system checks the file contents and verifies that the
variables are valid and that the values assigned to them comply with the existing syntactic
requirements. If errors are detected in the received file, irrespective of whether the Only
verify option is selected or not, the system automatically rejects all the information received
and indicates the error situation to the user.
If the received configuration is valid, it is indicated by the system to the user, and it is then
possible to continue (Continue button). When continue is selected, the configuration is
activated and stored.
When applying the new configuration, the system issues a warning due to the possible
loss of device access.
If the Only verify option has been selected, and verification has been successful, it is
indicated by the system to the user. If desired, the configuration can be applied by means
of the Apply and Save commands or both.
With this option the user obtains a local copy of the operating configuration in .txt format or
.xml format.
The procedure for downloading this file depends on both the HTTP browser and the actions
to perform with the received file (for example, where to store it).
With this option, the user can download different log files in txt format.
The total event log (General Log “log.txt”), the most relevant event log (General Events
“events.txt”), the authentication event log (Authority Events “authority.txt”) and the security
event log (Security Events “security.txt”) are available. The latter is only accessible for
Admin users.
As in the case of the downloading of the configuration of the unit, the procedure for
obtaining the file will depend on the HTTP browser used by the user, as well as the actions
that must be performed with the received file (for example, where to store it, etc.).
6 STATISTICS
The system provides statistics divided into eight blocks, each of them corresponding to a
specific functionality.
The first block shows general information related to the unit, and is displayed automatically
when the Statistics object is selected.
The remaining statistics are grouped into data belonging to the ModemEmulator function,
the Fast Ethernet ports (LAN), wireless WAN interface, the Routing rules, DHCP servers,
synchronization client (NTP) and port interconnection (Flow), each of which can be
accessed by selecting the respective tag located under the heading Statistics.
Each statistical data table can be updated by pressing the Reload button without having
to select the respective option again in the tree menu.
The statistics can be REBOOTED by the user at will, from the console by executing the
clear command in the prompt, or using the menu option Clear Statistics.
APPENDIX A
APPENDIX A
A.1 BIBLIOGRAPHY
[1] STD 15. IEEE RFC 1157. May 1990. A Simple Network Management Protocol (SNMP).
[2] STD 62. IEEE RFC 3416. December 2002. Version 2 of the Protocol Operations for the
Simple Network Management Protocol (SNMP) (Obsoletes RFC 1905).
[3] IEEE RFC 1305, March 1992. Network Time Protocol (Version 3) Specification,
Implementation and Analysis.
[4] Development specification of the terminals used for the creation of a point-multipoint
channel via GPRS_Rev.06 (14/4/2008) of IBD reference GPF070302CVG.
A.2 ABBREVIATIONS
IP Internet Protocol
IPSec IP Security
APPENDIX B
APPENDIX B
This appendix contains all the information required to use the CLI user console. It explains
the access methods, commands available on the console and gives a step-by-step
example of how to obtain information on the status and configuration of the unit.
Conventions:
The unit configuration parameters are laid out in a tree directory, in which parameters and
related subdirectories are grouped, where:
The system makes a distinction between upper and lower case characters.
The data stored in table form, identified by the inclusion in the variable name of the
symbol [], have specific commands for adding and removing rows, which are add and
remove respectively. To query or select the value of the data in one row, the row identifier
must be included between square brackets in the get or set command. To have the table
with factory settings, the available command is restore.
Changes made with the set command are not operative merely because they have been
executed. Effective, immediate use of the changes made is achieved by executing the
Apply command. On the contrary, the Save commands entails storing the changes
made permanently, without requiring their immediate use, but applied in the case of an
initialisation.
In this way, the changes are implemented as an operating procedure through the Apply
command, and after checking that the behaviour is correct, it is saved using the Save
command. Consequently in the case of obtaining undesirable results, it is always
possible to eliminate the Save command and reboot the unit to recover the previous
status, even in the case that the changed activated lead to the user not being able to
obtain access.
Users and their passwords are, by default, the same as in the web interface, that is to say:
Login Password
There are two ways of accessing the unit through the CLI user console:
in the local mode, through the service serial port (SRV port).
Local mode access is obtained through a flat serial cable that connects the serial port of the
computer to the serial port of the unit (SRV).
Run the Call option of the Call menu (or press, under the main menu options, the icon of
the phone hanged).
After the appearance of the starting frames, press the return key. When at the prompt is
displayed the sip login text, enter the user name and press return. When at the prompt is
displayed the sip password text, enter the password and press return (the user name and
password are the same as in the web interface).
Remember that no text will appear in the HyperTerminal window when entering the
password.
The Putty program is accessible on the www.putty.org web. Simply select the Putty that
suits the operating system in use (usually the first, called putty.exe), copy it in the
computer and run it.
If an USB converter is used, first, consult the COM number in the Device administrator
(Control panel).
Pressing the Open button, and return if necessary, a window is shown in which the sip
login: prompt will appear, ready for the user to enter the login and password for starting the
session (the user name and password are the same as in the web interface).
Remember that no text will appear in the Putty window when entering the password.
Remote mode access is obtained with the Telnet command and unit IP address.
! To use this access mode the unit must have its IP address configured and be
connected to the management computer network.
Telnet can be executed in Windows XP© from the Start button: Start → Execute, and in the
text box, enter: telnet + space + Unit_IP_address (111.222.0.123 in the example), and then
press Accept (see FIGURE 63).
On pressing the Accept button a System symbol window will appear with the Telnet
programme connected to the unit (see FIGURE 64).
HyperTerminal can be used as the Telnet graphic interface. To do this, when configuring
the connection select TCP/IP (Winsock) in the Connect using drop down menu.
Telnet can also be run from the Putty program. Simply, type the IP address of the unit in the
main window, and press Open.
Whatever the method chosen to establish connection with the unit, the sip login: prompt
will appear, ready for the user to enter the login and password for starting the session (the
user name and password are the same as in the web interface).
To enable it, from the Start button: Start → Control panel → All Programmes, in
Programs and characteristics, select Activate or deactivate the Windows characteristics.
Then, in the window of Characteristics of Windows, select Telnet client, see FIGURE 65.
By pressing Accept, the Telnet client of Windows may be used.
After starting the session with a valid login and password, the prompt will change to unit />
waiting for the user to enter a command.
The commands are instructions sent to the unit to request or change a value or to “browse”
through the tree in which the unit parameters are organised.
The following table shows a full list of available commands with a brief description of each
one and their availability depending on the type of user starting the session, highlighting the
most useful ones:
User
Command Description
admin guest
add Adds a new item to a matrix-type parameter ✓
apply Applies the new configuration ✓
cd Changes the directory in the parameters tree ✓ ✓
clear Deletes the statistics ✓
coverlog Allows the query of the cellular coverage log ✓ ✓
date Shows the date stored in the unit ✓
download Generates a configuration command file ✓ ✓
exit Interrupts the connection with the unit ✓ ✓
get Shows the parameter values ✓ ✓
help Shows the list of available commands ✓ ✓
log Shows the log file in use (current) ✓ ✓
ls Shows the lists of available parameters in the current directory ✓ ✓
ping Sends a ping to the indicated host ✓ ✓
qdownload Generates a command file with the complete configuration of
the unit ✓ ✓
quit Interrupts the connection with the unit ✓ ✓
reboot Reboots the unit ✓
reload Loads a previously-saved configuration ✓
remove Eliminates an item from a matrix-type parameter ✓
restore Loads a default configuration ✓
route Shows the routing table ✓ ✓
save Saves all the changes made during the session ✓
set Modifies the value of a parameter ✓
show Allows the query of the log file in use and of the old log files. It
also allows to display the file containing the customer default ✓ ✓
configuration
stats Allows to obtain the status parameters of the unit. ✓ ✓
tail It is useful for monitoring the unit during operation. It shows
the list of events stored in the log file in use and it remains to ✓ ✓
show events as they occur. It closes with Ctrl+C
telnet Open a telnet session without interrupting the connection with
the unit ✓ ✓
traceroute Shows the path followed by packets to reach destination, and
measures transit latencies and the back and forth times over ✓ ✓
the network
xmldownload Generates a command file with the unit configuration in XML
format ✓ ✓
add cd clear
apply exit coverlog
download quit date
get reboot help
qdownload reload log
remove telnet ls
restore ping
save route
set show
xmldownload stats
tail
traceroute
The events that are generated at the system level and sent to the log include an
identification level.
The system supports 8 different levels, separated into two blocks. The first set corresponds
to unwanted situations and the second block on information without affecting the
functionality.
In the first block, the values are emerg, alert, crit, err and warning, which represents a
decreasing level of severity in terms of the detected situation.
In the information block, the values are notice, info and debug, without having any
connotation whatsoever for impact.
Configuration commands
Arguments:
name Parameter to which a new item is to be added.
apply This applies the configuration changes in the unit, but without saving them.
Arguments: -
Arguments: -
get This show the current values of one or several unit configuration parameters.
Arguments: -
name (optional) name of the parameter to be shown.
qdownload As with the download command, this allows a copy (back up) of the
parameters configured in the unit, which will have a value different from the
default value (factory), to be obtained. Unlike the download command, the
qdownload obtains all the parameters at once, without having to press enter.
Arguments: -
Arguments:
name Parameter from which the item is to be removed.
nº (Optional) Order number of the parameter item
Arguments: -
Arguments: -
set This changes the value stored in the configuration parameters or in the
attributes of an item in a matrix-type parameter.
Arguments: -
name name of the parameter to be changed.
nº item number of a matrix-type parameter.
name2 name of an attribute in a matrix-type parameter.
Observations: When this command is executed the system waits for the
new value to be entered.
The parameter to be changed must be in the current
directory or its relative route must be entered.
In the case of wanting to change the value of any attribute
in the item of a matrix-type parameter, the argument must
include the parameter name, the item number and the
attribute number.
xmldownload As with the download command, this allows a copy (back up) of the
parameters configured in the unit, which will have a value different from
the default value (factory), to be obtained. Unlike the download
command, the xmldownload command generates the copy in xml
format.
Arguments : -
Control commands
Arguments:
name Name of the destination directory.
exit This closes the connection between the computer and the unit, and therefore
the CLI programme session.
Arguments: -
Observations: -
quit This closes the connection between the computer and the unit, and therefore
the CLI programme session.
Arguments: -
Observations: -
reboot This reboots the unit without having to turn it off and on again, for instance, in
order to apply the saved configuration changes.
Arguments: -
Observations: -
Arguments: -
Arguments:
Host Name of the destination host to which open a Telnet
session.
Port (optional) Number of the destination port where to open a
Telnet session.
Arguments: -
Observations: -
Arguments:
Observations:
Arguments: -
Observations: -
help Displays a list of all the available commands and a brief description of their
functions.
Arguments: -
Observations: -
log Shows the list of events stored in the log file in use (current).
Arguments:
- Without arguments, this command shows the events
recorded in the current log file.
all (Optional) Equivalent to using the command without
option.
Observations: All the events taking place in the unit are stored in files
permanently. The maximum number of files is 5. The files
are used in rotation but always remains a name that sets
the timing, by using a suffix. The higher the suffix oldest is
the file contents.
You can filter at will the temporary log, using the text as a
filter after the command. This operation works with any
ls Shows a list from the active directory. This command is useful for verifying
whether the configuration parameter to be consulted/changed is in the active
directory.
Arguments: -
Observations: -
Arguments:
host Host name or destination IP address.
Arguments: -
Observations: -
Arguments:
file Name of the file desired to display. The log file in use
(current) is named messages. Oldest log files include a
suffix, e.g. messages.1.
The events, security and auth files can also be displayed.
Arguments:
parameter (Optional) Name of the parameter whose status is to be
consulted.
tail This command is useful for monitoring the unit and detecting potential errors
during operation. It shows the list of events stored in the log file in use
(current) and it remains to show events as they occur. It closes with Ctrl.+C.
Arguments:
- Without arguments, this command shows the events
recorded in the unit non-volatile memory.
Arguments:
host host name or destination IP address.
Observations: -
To obtain information about the status and configuration of unit, proceed as follows:
As explained in chapter B.1, the unit connection differs slightly depending on the
chosen method. In this example, it is assumed that the unit is a DRA-2, connected to a
network and with an IP address configured, which in the case of this example will be
111.222.0.123. In addition, the computer used to make the connection is also
connected to that network and the O.S. used is Windows XP©.
To establish the connection through Telnet, click on the Windows XP© Start button
and once the menu has appeared, click on the command Execute. In the window that
appears, enter “telnet 111.222.0.123” (without inverted commas) and then press
Accept.
If everything is functioning normally, a window will pop up with a system symbol, which
is the interface for the connection.
On establishing connection with the unit, the prompt drn login: indicates that the
system is waiting for a user name to connect with the drn unit.
Given that we only want information, it makes no difference which login is entered
(admin or guest). Enter guest and then press enter.
Now the system is waiting for us to enter the respective password. Enter passwd01
which is the one associated with the guest user and press enter.
Remember that no text will appear in the Telnet window when entering the
password.
If the login and password entered are correct, the prompt drn /> will appear, indicating
that the unit is waiting for a command to be entered.
The unit configuration is obtained through the command download. On pressing enter
after this command, the full unit configuration will be displayed. In the example the unit
corresponds to a DRA-2.
If the information extends beyond the edges of the window, the system will only show
the information at the start and it will be necessary to press enter once or several
times for all the information to be shown. You will know whether the system has
finished showing all the information when the unit prompt reappears: drn />.
The qdownload command obtains all the parameters at once, without having to
press enter.
It is important to save the information in a .txt file using the download command so that
it can be used whenever necessary.
To copy the text from the Windows XP© command window, right-click with the mouse
and select Mark in the menu that appears.
Now open Windows Notepad and paste the text (Ctrl. + V) in a .txt file and save it.
The get command shows the full status of the unit. Since the information shown is very
lengthy, every time a window is filled, it will wait for the user to press a key to continue
displaying the information. In the example the unit corresponds to a DRA-2.
The unit statistics list is shown through the command stats. In the example the unit
corresponds to a DRA-2.
Like the previous commands, if the information to be displayed exceeds the edges of
the window, it will stop and wait for the user to press a key to continue.
The log command allows you to consult the list of events stored in the log file in use
(current). Use the show command to display the oldest log files. In the example the
unit corresponds to a DRA-2.
The tail command allows users to monitor the events taking place in the unit in real
time. Once the command is activated, it will remain to show events as they occur until
the user presses Ctrl.+C.
9- Example of a list showing the status of an unit obtained with the get command
and saved in a .txt file
sip />
The server integrated in the unit supports the HTTP and the HTTPS protocols, in the last
case being necessary the installation of certificates.
The procedure for loading the certificates for HTTPS management, once the certificate,
the private key and the password of the last one have been got, is the following:
1- Access the configuration section of the web interface, through the SRV port (service
port)
(“cd /admin/web”)
2- Load in “cert” a valid certificate with the command “upload cert raw”.
The procedure for loading the certificate is the following. Copy in the clipboard the
certificate. Then, execute the indicated upload command and, when it is in wait
period, paste the data from the clipboard. Wait approximately 30s. When the
time is elapsed, the data are shown.
3- Load in “privatekey” a valid private key with the command “upload privatekey
raw”.
The procedure is the same that the one indicated previously for the certificate.
4- Introduce the password of the private key in “privatekeypwd” with the command
“set privatekeypwd”.
Confirmation of the password is required twice as much.
Although the certificate operates correctly, this message is a warning indicating that
the certificate has not been validated by a trusted authority.
Select “Go to this web site (not recommended)”.
Then, the device access control requires the user login and password.
The unit also supports the loading of a maximum of 4 certificates belonging to certification
authorities (CA), so that it can verify certificates signed by these entities. The procedure for
loading is equivalent to the one of the certificate itself:
1- Access the section associated with the configuration of the web interface, via the
SRV port (“cd /admin/web/ca[n]”), with n in the range 1 to 4.
2- Load a valid certificate in “cert” with the command “upload cert raw”.
The procedure for loading the certificate consists firstly of have previously copied
the certificate to the clipboard (Copy). Then, execute the upload command and,
when it is in stand-by condition, paste the data from the clipboard (Paste). Wait
about 30s. After this time, the data will be displayed.
In the unit with HTTPS operation, the certificate, the private key and the password of the
last, as well as the certificates of the CA if configured, are part of the data obtained by
means of the “download” command. Therefore, it is possible to add this information to the
configuration pattern.
If there are no available certificate, private password and password of the last, it is possible
to create them. For example, following the instructions in
http://www.akadia.com/services/ssh_test_certificate.html, but in this case it is necessary a
Linux unit to execute the instructions.
Pay attention that both the header and bottom lines are part of the certificate.
-----BEGIN CERTIFICATE-----
MIICWzCCAcQCCQCcL+NbBdYynDANBgkqhkiG9w0BAQUFADByMQswCQYDVQQGEwJF
UzESMBAGA1UECBMJQmFyY2Vsb25hMRIwEAYDVQQHEwlCYXJjZWxvbmExDDAKBgNV
BAoTA1pJVjEOMAwGA1UEAxMFSm9zZXAxHTAbBgkqhkiG9w0BCQEWDmouc2FsYXRA
eml2LmVzMB4XDTEzMDMyNzE1NTAzOVoXDTE0MDMyNzE1NTAzOVowcjELMAkGA1UE
BhMCRVMxEjAQBgNVBAgTCUJhcmNlbG9uYTESMBAGA1UEBxMJQmFyY2Vsb25hMQww
CgYDVQQKEwNaSVYxDjAMBgNVBAMTBUpvc2VwMR0wGwYJKoZIhvcNAQkBFg5qLnNh
bGF0QHppdi5lczCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAt49IfdfD/xVO
GsqL217s6aumdFWr9NYoJw68LbrHY0VZ9OGwen+alXAjBcl2lqLZjf1lOh250aWE
eZLH31lD5bxS9c+w8YrwXoWEnYOxUQpK49YGvH7DnqLAyI5ptyQbdyMoTkMcxBOZ
jNoToVioGiZ9GRBg6nKCDC4+PxN3/90CAwEAATANBgkqhkiG9w0BAQUFAAOBgQAT
7QtOOJT6lLcGciF4R5aooiRoZEiTJQBFm6PoTZ21apGGhF1Bz0FPn3LRxC1Mb6PI
kNatYteCq5FJNjGunF8hDIQVc1x7O2ju2vmGOiyVfSz1eqiy+Tx0dMYsgpBeY3K+
8fb+J1jmLPNzPhgMlzPK6VGNA70/QhfCG9l5xK1oWQ==
-----END CERTIFICATE-----