ZIV SIP-2 User manual

Making the Smart Grid Real
1/145
ZIV
Antonio Machado,78-80
08840 Viladecans, Barcelona-Spain
Tel.: [phone]
Fax: [phone]
Mail to: [e-mail]
www.zivautomation.com
COMMUNICATION NODE
TYPE SIP-2
USER GUIDE
Rev. 3 - January 2018

SIP-2
COMMUNICATION NODE TYPE SIP-2 2/145
USER GUIDE - Rev. 3 (January 2018)

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
equipment or even injury to the personnel handling it.
NOTE:
Information or important aspects to take into account in a procedure,
operation or alike.

SIP-2
COMMUNICATION NODE TYPE SIP-2 3/145
USER GUIDE - Rev. 3 (January 2018)
TABLE OF CONTENTS
Page
1INTRODUCTION 6
1.1 GENERAL 6
1.2 PORT INTERCONNECTION 9
1.3 VERSION WITH GW 104-101 12
1.4 TECHNICAL SPECIFICATIONS 13
1.4.1 Equipment interfaces 13
1.4.2 Encapsulation protocols 13
1.4.3 Equipment management 13
1.4.4 Additional services 14
1.4.5 Accessories 14
1.4.6 Certifications 14
1.4.7 Asynchronous serial data ports (DCE) characteristics 14
1.4.8 WAN interface characteristics 15
1.4.9 Mechanical characteristics 16
1.4.10 Operating conditions 16
1.5 WARNINGS 18
1.5.1 Warnings before installing 18
1.5.2 Equipment safety considerations 19
2MECHANICAL AND ELECTRICAL CHARACTERISTICS 20
2.1 POWER SUPPLY 23
2.2 FAST ETHERNET PORTS (Eth 0 & Eth 1) 24
2.3 RS-232/RS-485 PORT (COM 1) 26
2.4 RS-232 PORT (COM 2) 27
2.5 DIGITAL INPUTS 28
2.6 WAN INTERFACE 29
2.7 SERVICE INTERFACE (COM 0) 31
2.8 INITIALIZATION PUSH-BUTTON 32

SIP-2
COMMUNICATION NODE TYPE SIP-2 4/145
USER GUIDE - Rev. 3 (January 2018)
Page
3LED SIGNALLING 33
4ACCESS TO THE EQUIPMENT 36
4.1 CONSOLE 36
4.2 HTTP SERVER 36
5CONFIGURATION AND MANAGEMENT 38
5.1 GENERAL PARAMETERS 40
5.1.1 Equipment identification 41
5.1.2 Access control 41
5.1.3 Others 42
5.2 ADMINISTRATION 42
5.3 LAN CONFIGURATION 43
5.4 SERIAL PORT CONFIGURATION 44
5.5 WAN CONFIGURATION 46
5.5.1 cell0 submenu 46
5.5.2 Tunnel submenu 55
5.6 STATIC ROUTES CONFIGURATION 58
5.7 DNS SERVER CONFIGURATION 61
5.8 FILTERING CONFIGURATION 61
5.9 GW 104-101 CONFIGURATION 64
5.9.1 IEC 60870-5-104 configuration 64
5.9.2 IEC 60870-5-101 configuration 66
5.9.3 RTU configuration 67
5.10 NAT CONFIGURATION 70
5.11 DHCP SERVER CONFIGURATION 71
5.12 VPN CONFIGURATION 73
5.13 SNMP CONFIGURATION 78
5.14 NTP CONFIGURATION 81
5.15 ACCESS CONFIGURATION 82

SIP-2
COMMUNICATION NODE TYPE SIP-2 5/145
USER GUIDE - Rev. 3 (January 2018)
Page
5.16 DATA FLOW CONFIGURATION 84
5.16.1 Encapsulation protocols 84
5.16.2 Connection 92
5.16.3 Policy 93
5.16.4 Other 95
5.16.5 Transparent 96
5.17 CONFIGURATION OF THE SERIAL PORT AS ModemEmulator 96
5.18 REBOOT 99
5.19 CODE REFLASH 99
5.20 CONFIGURATION FILE 100
5.20.1 Upload (from the computer to the equipment) 100
5.20.2 Download (from the equipment to the computer) 101
6STATISTICS 102
APPENDIX A
BIBLIOGRAPHY AND ABBREVIATIONS 105
APPENDIX B
DATA STRUCTURE IN CLI 110

SIP-2
COMMUNICATION NODE TYPE SIP-2 6/145
USER GUIDE - Rev. 3 (January 2018)
1 INTRODUCTION
1.1 GENERAL
The SIP-2 is a communication node designed to operate as a WAN router and a serial to IP
encapsulation device. Next, several examples of application are indicated.
The equipment can have one or two serial ports, one or two Fast Ethernet interfaces, and a
cellular 2G (GSM/GPRS), 3G (UMTS/HSPA) or 4G (LTE) interface.
The cellular interface admits dual SIM operation. It allows increasing the service availability
since it provides access to more than one operator, and the user configures how the
equipment will manage the WAN connection and the operator in use.
The equipment can also have two digital inputs, galvanically isolated, which can be
managed via SNMP. Upon request, it can also have two digital outputs.
As regards its installation, the SIP-2 can be supplied with a chassis suitable for mounting in
DIN rail or wall mounting.
FIGURE 1 Remote access to Ethernet device

SIP-2
COMMUNICATION NODE TYPE SIP-2 7/145
USER GUIDE - Rev. 3 (January 2018)
FIGURE 2 Serial to IP encapsulation on wired interface
FIGURE 3 Serial to IP encapsulation on GPRS network
FIGURE 4 Remote connection between two SIP-2s

SIP-2
COMMUNICATION NODE TYPE SIP-2 8/145
USER GUIDE - Rev. 3 (January 2018)
The SIP-2 can be managed locally and remotely, through a console or through a built-in
web server (http/https), SSH and Telnet server.
The SIP-2 also supports the SNMPv1, SNMPv2c and SNMPv3 protocols, as well as other
protocols and services such as NAT, DHCP, NTP and TACACS+.
The basic encapsulation function is the creation of a point-to-point connection, equivalent to
a direct connection between two serial devices, even when the actual data transfer is done
on a TCP/IP network.
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 equipment
admits two processing modes with the PAD function: direct or with packets.
SIP-2 equipment 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-2 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 encapsulator operations modes is the SIP-2
capability to offer the basic HAYES modem behaviour towards the client equipment, so that
the encapsulator point-to-point connections are made upon demand and with the
determined receiver by application or the client equipment. The operation in HAYES mode
is enabled separately for each one of the serial ports present in the SIP-2.

SIP-2
COMMUNICATION NODE TYPE SIP-2 9/145
USER GUIDE - Rev. 3 (January 2018)
1.2 PORT INTERCONNECTION
In addition to the serial ports -which are called physical ports-, the equipment 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 equipment basic operation is the determination of the port characteristics, both
physical as well as virtual, and then establishes the “connections” between them; which in
practice sets the ends where the transfer of encapsulated data is done.
On the other hand, if the equipment has an optional WAN interface, there will be an
additional virtual port related to the GSM data call, in order to establish a connection
between said virtual port and a serial port.
Next, for a better understanding when approaching the SIP-2 configuration by accessing
the equipment 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
(speed, 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 the COM port, that is, the name, is done in the Physical Ports
section of the Flow menu configuration screen.

SIP-2
COMMUNICATION NODE TYPE SIP-2 10/145
USER GUIDE - Rev. 3 (January 2018)
2. Create and configure the parameters of the TCP/UDP virtual ports. For this, access the
Flow menu configuration screen (see section 5.16 for more detailed information).
The Flow menu configuration screen has two well differentiated sections. Physical
Ports and Virtual Ports.
Establish 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 equipment 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.
The operation of the datacall will depend on the services permitted by the operator,
especially in 3G and 4G networks.
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 equipment will take the initiative as regards establishing the TCP connection. On
the contrary, passive means that the equipment 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-established
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).