YOKOGAWA Vnet/IP Technical Information
  1. Manuals
  2. Brands
  3. YOKOGAWA Manuals
  4. Network Card
  5. Vnet/IP
  6. Technical information
YOKOGAWA Vnet/IP Technical Information

YOKOGAWA Vnet/IP Technical Information

Hide thumbs
Table of Contents

Advertisement

Quick Links

Technical
Information
TI 30A10A05-01E
Vnet/IP Network
Construction Guide
Yokogawa Electric Corporation
2-9-32, Nakacho, Musashino-shi, Tokyo, 180-8750 Japan
TI30A10A05-01E
©Copyright Aug. 2011 (YK)
5th Edition Mar. 2019 (YK)

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Vnet/IP and is the answer not in the manual?

Questions and answers

Summary of Contents for YOKOGAWA Vnet/IP

  • Page 1 Technical Vnet/IP Network Construction Guide Information TI 30A10A05-01E Yokogawa Electric Corporation TI30A10A05-01E 2-9-32, Nakacho, Musashino-shi, Tokyo, 180-8750 Japan ©Copyright Aug. 2011 (YK) 5th Edition Mar. 2019 (YK)
  • Page 2 Blank Page...
  • Page 3 Vnet/IP system. Chapter 1 describes Vnet/IP. Chapters 2 and 3 provide the information required to configure a Vnet/IP system. Ensure that you read Chapter 1 first if you are not familiar with the background of Vnet/IP.
  • Page 4 Glossary The following table describes the terms commonly used in this document. Table Glossary terms (1/2) Term Description 1000BASE-LX A gigabit Ethernet optical interface standard specified in IEEE 802.3 with a transmission rate of 1 Gbps. 1000BASE-T A gigabit Ethernet UTP interface standard specified in IEEE 802.3 with a transmission rate of 1 Gbps.
  • Page 5 A process automation control network that uses the token passing method. It has a transmission rate of 10 Mbps. V net router A device that connects a Vnet/IP domain to a V net or VL net domain. It is used to relay control communications. VL net A control network for CENTUM CS 1000.
  • Page 6 Symbol Marks Throughout this Technical Information, you will find several different types of symbols are used to identify different sections of text. This section describes these icons. WARNING Indicates precautions to avoid a danger that may lead to death or severe injury. CAUTION Indicates precautions to avoid a danger that may lead to minor or moderate injury or property damage.
  • Page 7 • Vnet/IP, CENTUM, ProSafe, Exaopc, Exapilot and Exaquantum are either registered trademarks or trademarks of Yokogawa Electric Corporation. • PRM is registered trademarks of YOKOGAWA in the United States and/or Japan. • Windows is registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
  • Page 8 Blank Page...

  • Page 9: Table Of Contents

    Toc-1 Vnet/IP Network Construction Guide TI 30A10A05-01E 5th Edition CONTENTS Overview of Vnet/IP .................. 1-1 Vnet/IP Features ....................1-2 Vnet/IP System Components ................1-3 1.2.1 Vnet/IP Stations ................. 1-5 1.2.2 Vnet/IP Network Devices ..............1-7 1.2.3 Cable for Vnet/IP ................1-7 1.2.4...
  • Page 10 Toc-2 Appendix ....................4-1 Layer 2 Switch (L2SW) ..................4-1 Layer 3 Switch (L3SW) ..................4-1 Cable for Vnet/IP ....................4-2 Time Synchronization ..................4-4 4.5 Precautions when Installing Network Devices ..........4-9 Notes on System Power-on ................4-10 4.7 Ring network configuration ................4-11 TI 30A10A05-01E...

  • Page 11: Overview Of Vnet/Ip

    1. Overview of Vnet/IP Overview of Vnet/IP Vnet/IP is a highly reliable and responsive control network that is developed by YOKOGAWA. This section provides an overview of Vnet/IP by describing its functions and specifications. TI 30A10A05-01E Aug.19,2011-00...

  • Page 12: Vnet/Ip Features

    Ed.2.0) and conforms to IEEE 802.3 and UDP/IP. n High reliability Vnet/IP is a control network with dual redundant buses and consists of independent subnets, bus 1 and bus 2. The control communication is usually performed by using bus 1. However, when a problem occurs in bus 1, the path switches immediately and automatically so that the control communication is performed by using bus 2.

  • Page 13: Vnet/Ip System Components

    L3SW: Layer 3 switch L2SW: Layer 2 switch Subsystem 010201E.ai WAC router is used for connecting to other Vnet/IP domain via WAN. (Refer to GS 33J01A10-01EN for an example of system configuration including WAC router.) Figure System Configuration Example TI 30A10A05-01E Mar. 15,2019-00...
  • Page 14 1. Overview of Vnet/IP In this document, devices such as stations in which a Vnet/IP interface card is installed, FCS and SCS for Vnet/IP, and V net router are all referred to as Vnet/IP stations. Vnet/IP stations support Vnet/IP protocols.

  • Page 15: Vnet/Ip Stations

    An APCS performs control functions with a station to improve advanced control and plant efficiency. The APCS requires installation of the “LFS1200 APCS Control Functions.” A Vnet/IP interface card is required to connect to Vnet/IP. A UGS is a station that integrates subsystem controllers such as STARDOM controllers (FCN/ FCJ) or third party PLCs with the CENTUM VP system.
  • Page 16 A SENG is a station of ProSafe-RS that performs engineering functions such as application configuration, downloading, application testing, and carrying out of maintenance tasks on SCSs. You can install the SENG functions on a station that has HIS or ENG functions. A Vnet/IP interface card is required to connect to Vnet/IP.

  • Page 17: Vnet/Ip Network Devices

    1. Overview of Vnet/IP V net router A V net router is a device that connects a Vnet/IP domain to a V net or VL net domain. It relays communication between Vnet/IP stations and V net or VL net stations.

  • Page 18: Vnet/Ip Main Specifications

    1. Overview of Vnet/IP 1.3 Vnet/IP Main Specifications This section describes the main specifications of Vnet/IP. 1.3.1 Communications Specifications Control communications Communication method: Read/write communications, message communications, and link transmission Link transmission period: 100 msec Transmission path Network topology: Star topology (tree or ring topology for multiple connection) Transmission path redundancy:...

  • Page 19: Achieving High Reliability With Redundancy

    Vnet/IP usually uses bus 1 for the control communication path. It does not use bus 1 and bus 2 alternately. When a problem occurs in bus 1, the communication path switches to bus 2.
  • Page 20 CPUs is connected to layer 2 switches in a dual-redundant Vnet/IP. As mentioned earlier, a Vnet/IP station stores information of other stations that are on Vnet/IP. This includes information about CPU control rights. The sending station uses the control rights information of the receiving station to determine the path to take for sending the control information, and the CPU module to which the information is sent.

  • Page 21: Achieving High Reliability With Ring Configuration

    1.3.3 Achieving high reliability with Ring Configuration Vnet/IP is a dual-redundant control network. When bus 1 fails, the communication is continued by switching the route to bus 2. When the bus 1 and bus 2 are installed in parallel, there may be a case when both of the buses fail at the same time caused by an incident. In such case, connecting multiple network switches in ring configuration, redundancy of the communication route can be established.
  • Page 22 As in the figure (3), when the L2SW “B” on the bus 1 fails, the bus 1 switches to detour by the ring structure; however, the failure point (the communication to the Vnet/IP station connected to the switch B) will not recover and the Vnet/IP communication switch to the bus 2.

  • Page 23: Vnet/Ip System Structure

    1-13 1. Overview of Vnet/IP Vnet/IP System Structure In Vnet/IP, a region that uses only layer 2 switches for connections without using devices such as a V net router or layer 3 switch is referred to as a Vnet/IP domain. Vnet/IP builds a network for each domain. When building networks, it is important to consider the limitations for each domain and for all the domains. Vnet/IP domain In a Vnet/IP domain, Vnet/IP stations are connected to layer 2 switches that are configured by star or ring topology.
  • Page 24 1. Overview of Vnet/IP Connection within a Vnet/IP domain A dual-redundant Vnet/IP bus consists of independent subnets, bus 1 and bus 2. A Layer 2 switch is installed in each line.In Vnet/IP stations with dual redundant CPU modules, each CPU module has ports for bus 1 and bus 2, which connect to layer 2 switches in their respective paths.
  • Page 25 1. Overview of Vnet/IP n Connecting Vnet/IP domains with each other Layer 3 switches connect Vnet/IP domains with each other. There can be up to 16 domains connected in a system. Ensure that the communication bandwidth between domains is 1 Gbps or more. To connect wide-area communication services in a narrow band network where the link speed is less than 1 Gbps, contact YOKOGAWA.
  • Page 26 Bridge connection A connection securing independence of the domains. Messages from FCS, SCS, and/or HIS generated in one of the domains are not received by the Vnet/IP stations in the other domain. Time synchronization between the domains can also be disabled.
  • Page 27 Number of hierarchical connections through a V net router (*1): Three (two levels of bus converters, three levels of control buses) The number of levels of Vnet/IP domains and V net routers are not counted as an acceptable number of hierarchical V net connections.
  • Page 28 1. Overview of Vnet/IP l Connection between Vnet/IP domains through V net When using AVR10D style S3 V net routers, you can set either Vnet/IP or V net as the upper domain. However, you must set Vnet/IP as the upper domain for AVR10D style S2 V net routers.
  • Page 29 1-19 1. Overview of Vnet/IP l Example of an incorrect connection You cannot set one V net domain as the lower domain of multiple V net routers. You also cannot have more than one communication path between domains. Vnet/IP Domain Vnet/IP Domain L2SW L2SW...

  • Page 30: Information Network Communication

    1-20 1. Overview of Vnet/IP Information Network Communication Data communications with other Ethernet communication devices and between Vnet/ IP stations are performed on the information network that is connected to the network interface card of a computer. Data transferred to an information network The HIS, ENG, and SENG transfer the following types of data to the information network: •...

  • Page 31: Conditions Without An Information Network

    When the number of PC with Vnet/IP interface card exceeds 16, it is suggested to perform Ethernet communication by the network connected to a PC’s Ethernet card, and do not use Vnet/IP Bus 2 communication. When the number of PC exceeds 50, this method is strongly recommended.

  • Page 32: Vnet/Ip Network Configuration

    2. Vnet/IP Network Configuration Vnet/IP Network Configuration When setting up a Vnet/IP network, you have to consider some settings regarding the system configuration. This section describes the information required to set up a Vnet/ IP network and provides detailed examples. It also describes the normal configuration where Vnet/IP performs only control communication, while other data communications are performed on the information network. TI 30A10A05-01E Aug.19,2011-00...

  • Page 33: Ip Address Setting

    In each Vnet/IP station, the host address for control communications is automatically set to the station number 2 to 129. A station number is set for each Vnet/IP station by using a DIP switch. A host address is assigned to each CPU module in duplexed FCS, duplexed SCS, and duplexed V net routers.
  • Page 34 Figure Virtual IP address for control network TCP/IP communications Vnet/IP station IP address The following table provides the Vnet/IP station IP addresses corresponding to the Vnet/ IP station types. The IP addresses for control network TCP/IP protocol communications are recommended for CENTUM and ProSafe-RS. This table also provides the recommended IP addresses for network interface cards that are used for information networks.
  • Page 35 2. Vnet/IP Network Configuration Table Vnet/IP station IP address (1/2) Station Required IP addresses IP address Setting procedure HIS, ENG, SENG For bus 1 192.168.<dd>.<2×ss> Automatically set by the DIP switch in Vnet/IP For bus 2 192.168.<128+dd>.<2×ss> interface cards. Control bus TCP/IP 172.16.<dd>.<ss> Manually set from the...
  • Page 36 2. Vnet/IP Network Configuration Table Vnet/IP station IP address (2/2) Station Required IP addresses IP address Setting procedure For bus 1 192.168.<dd>.<2×ss> Automatically set by the DIP switch in Vnet/IP For bus 2 192.168.<128+dd>.<2×ss> interface cards. For information network 172.17.<dd>.<ss> Manually set from the Windows operating system.

  • Page 37: Network Configuration Example

    Connection within a Domain n System configuration for a single domain There can be up to 64 Vnet/IP stations in one domain. The following figure shows an example of a system configuration that consists of two HISs, one SENG, two duplexed FCSs, and one duplexed SCS.

  • Page 38: Connecting Multiple Domains

    System configuration for multiple domains If there are more than 64 Vnet/IP stations in a system, you have to split the Vnet/IP domain. To connect the split domains, use a layer 3 switch for each bus 1 and bus 2 of the split domains. Use a HUB to connect the information network between domains.
  • Page 39 If one set of layer 3 switch is not enough to connect all domains, you can use multiple sets of layer 3 switches to connect Vnet/IP domains in a cascade. The following figure shows an example of an inter-domain cascade connection.
  • Page 40 2. Vnet/IP Network Configuration n Operating a system with split domains Even if there are 64 or less Vnet/IP stations in a system, you can split the domain according to the operation scope and maintenance unit to enable optimal management of messages in each domain. The following figure shows an example of a connection between domains that are split according to the operation scope for a system integrated with CENTUM and ProSafe-RS.

  • Page 41: Connection With Existing Systems

    2.2.3 Connection with Existing Systems You can connect an existing V net or VL net system to Vnet/IP by using a V net router. You cannot connect existing control networks such as HF Bus or RL Bus to Vnet/IP directly. However, you can do so by using a BCV on V net.
  • Page 42 Figure Example of a connection between Vnet/IP and existing V net n V net router setting You can configure the V net router by using the CENTUM engineering function in Vnet/IP. You can also configure the AVR10D style S3 router from CENTUM in V net. The following table shows an example of a V net router configuration as shown in the previous figure.
  • Page 43 Type of V net router. Apply Vnet/IP to Upper-Level Check Bus type of the upper-level domain. The upper Domain upper-level domain can be Vnet/IP or V net. Domain Number Domain number of the upper-level domain. Station Number Station number of the upper-level domain.
  • Page 44 Vnet/IP domain specified in the Vnet/IP domain is transferred to a V net domain. It is not necessary to set a Vnet/IP domain to which this V net router is connected because a frame is always transferred in this case.

  • Page 45: Connecting Network Switches By Ring Topology

    A system configuration where Vnet/IP network is configured in a ring network is as shown below. (1) Setting Ring protocol Ring protocol has to be set to both Bus 1 and Bus 2 of the network switch for Vnet/IP to make both of the Bus 1 and Bus 2 have ring configuration.

  • Page 46: Connection With External Network

    2-15 2. Vnet/IP Network Configuration 2.3 Connection with External Network Vnet/IP is a control network. For security purposes, do not connect it to external networks directly. If Exaopc is installed on the system, you have to implement security measures such as using a firewall when connecting to OPC clients on external networks from the information network. Contact the network administrator to determine the security policy to apply for the firewall. For more information about the security countermeasures, refer to the following: ALSO “Security Standard of System Product” (TI 33Y01B30-01E) TI 30A10A05-01E...

  • Page 47: Vnet/Ip Network Configuration Without Using Information Network

    In Vnet/IP systems, we usually recommend that you set up an information network that is separate from Vnet/IP. However, you can choose not to use an information network if certain conditions (*1) are satisfied. In this case, use Vnet/IP bus 2 to perform information network communication. The information network communication that is performed through Vnet/IP bus 2 is referred to as open communications.

  • Page 48: Bandwidth Used For Open Communications

    However, when bus 1 fails, bus 2 performs both control and open communications. To ensure stable control communications, restrict the bandwidth of open communications used in the Vnet/IP domain to 500 Mbps or less, which should already include the 200 Mbps used for communication between Vnet/IP stations.

  • Page 49: Ip Address Setting

    In each Vnet/IP station, the host address for control communications is automatically set to the station number 2 to 129. A station number is set for each Vnet/IP station by using a DIP switch. A host address is assigned to each CPU module in duplexed FCS.
  • Page 50 3. Vnet/IP Network Configuration without using Information Network Host address for open communications Select the host address for open communications from the range of Vnet/IP network addresses—which are 130 to 253—that you can use in open communications. The default host address for recommended layer 3 switches is set to 253. Ensure that the host address is not duplicated in Vnet/IP stations and all other devices in a Vnet/IP domain.
  • Page 51 3. Vnet/IP Network Configuration without using Information Network Vnet/IP station IP address The following table provides the Vnet/IP station IP addresses corresponding to the Vnet/IP station types. The IP addresses for open communications and control network TCP/IP protocol communications are recommended for CENTUM. Table Vnet/IP station IP address...

  • Page 52: Network Configuration Example

    2 switch. Number of ports required for a layer 2 switch = (number of Vnet/IP stations that use Vnet/IP interface cards) + (number of single FCSs and single SCSs) + (number of duplexed FCSs and duplexed SCSs) x 2 In the previous figure, the system configuration uses one HIS, one ENG, and two duplexed FCSs.

  • Page 53: Connecting Multiple Domains

    3 switch for each bus 1 and bus 2 of the split domains. The following figure shows an example of how to split a Vnet/IP domain. The IP address for each port in the recommended layer 3 switch is set by default. Therefore, to set up a system, you only have to connect to the layer 2 switches in each domain and to those ports with the same number as the domain number.
  • Page 54 1 can centrally monitor the entire system, while the individual operation scopes can operate without handling system alarms and operation logs from other operation scopes. Vnet/IP Domain 1 (All System Management) Hierarchical Port1...
  • Page 55 If one set of layer 3 switch is not enough to connect all domains, you can use multiple sets of layer 3 switches to connect Vnet/IP domains in a cascade. The following figure shows an example of an inter-domain cascade connection.

  • Page 56: Appendix

    Layer 2 Switch (L2SW) If there are no requirements for network monitoring or security strengthening, you can connect Vnet/IP stations to any ports of the recommended layer 2 switch in its default state. Even if you use the layer 2 switch as a trunk port between layer 2 switches or with layer 3 switches, you do not have to use a cross cable or change any of the layer 2 switch settings.

  • Page 57: Cable For Vnet/Ip

    ANSI TIA/EIA-568-B. UTP cables usually use RJ45 plugs as connectors. The maximum length of UTP cables is 100 m. We recommend that you use cables with different coating colors for Vnet/IP bus 1 and bus 2 for easier maintenance.
  • Page 58 5 km. (*2) We do not recommend the use of multi-mode optical fiber cable type for connecting switches in a Vnet/IP domain. Use the single- mode optical fiber cable type when installing new optical fiber cables.

  • Page 59: Time Synchronization

    The time synchronization process standardizes the network time for all Vnet/IP stations connected to the Vnet/IP network. Furthermore, the system software for Vnet/IP stations updates its system time to match the network time. The following table describes the deviation between the network time and system time in Vnet/IP stations.
  • Page 60 4. Appendix Time synchronization within a Vnet/IP domain The time is synchronized in each Vnet/IP station within a domain so that the clock time is set to its own domain master station clock. The domain master station manages the setting of information within a domain. It broadcasts its own network time and periodically performs clock time multicasting to the Vnet/IP stations.
  • Page 61 It is not necessary for you to identify the network time master. Vnet/IP defines time groups in the domain properties of the CENTUM engineering function on a domain-by-domain basis. The time group is specified by using numbers 0 to 7. The time is not synchronized for domains whose time group is 0.
  • Page 62 • SNTP server for bus 2: 192.168.<128 + domain number>.254 If there are multiple Vnet/IP domains in a time group, you can set the IP address for SNTP servers only through the CENTUM engineering function of the domain that is connected to the SNTP server.
  • Page 63 Time synchronization with a V net domain When a V net domain is connected to a Vnet/IP network, the time on Vnet/IP is used as the master time, and the time of V net domains synchronizes with it. You can set the time on V net as the master time.

  • Page 64: Precautions When Installing Network Devices

    Devices Power supply for network devices To avoid redundant Vnet/IP network devices connected to bus1 and bus 2 from failing at the same time during a power failure, you must separate the power supply for network devices connected to bus 1 and bus 2. In addition, use an uninterruptible power supply (UPS) for each power supply system to prepare for temporary power failure of both systems.

  • Page 65: Notes On System Power-On

    Vnet/IP stations. If the Vnet/IP stations are powered-on prior to the Layer 2 (or the Layer 3) switches, the local security zone may be automatically configured by the Vnet/IP’s security function. This causes the failure of the Vnet/IP stations communication establishment.

  • Page 66: Ring Network Configuration

    Background of why ring network is requiring in control network Vnet/IP has achieved redundancy by isolating the network using bus 1 and bus 2, and the ring network has not been supported in its standard network structure. However, when the bus 1 and bus 2 cables are routed in the same location, both of the communications break in cases the place is disturbed by a natural disaster or alike.
  • Page 67 DI signal in the FCS to generate alarms. n Requirements for Vnet/IP Ring network Network switch The table below shows the list of Vnet/IP network switches applicable for structuring a ring network. Do not use any other switches for the ring networks. Table Vnet/IP network switches applicable for Ring network...
  • Page 68 4-13 4. Appendix CENTUM VP For detecting failures and acknowledging recovery of alarms of the ring network, the following components are required. • HIS × 1 unit For detecting failures/acknowledging recovery of alarms. An HIS in the existing system can be utilized.
  • Page 69 “Ring topology” is added to the network topology. 1.3.3 A new chapter “High Reliability with Ring Configuration” is added. The description of “Vnet/IP domain” is revised to add “ring topology.” A figure “Sample Structure of Multiple Domains (Ring Topology)” is added. 2.2.2 Changed the pages order of “Cascade connection between domains”...
  • Page 70 Written by Yokogawa Electric Corporation Published by Yokogawa Electric Corporation 2-9-32 Nakacho, Musashino-shi, Tokyo 180-8750, JAPAN Printed by KOHOKU PUBLISHING & PRINTING INC. Subject to change without notice.

Table of Contents

Save PDF