Helps_SV_V11_1 _ WORD FILES _ ENUSV_Networking

Overview of Networked Applications3About Client and Server Terminology4Networked Applications - Frequently Asked Questions5Understanding IP Addressing7Checking the Network Setup when Using TCP/IP9Checking the Network Setup When Using Netbios11Managing Networking in the Application Explorer13Networking Settings14How to Configure a Station15How to Configure a Node17The Station Advanced Tab19The Node Advanced Tab21How to Manually Configure Client Server Links23How the Station Number and Name is Allocated to a Physical PC24How to Configure Station Lists26How to Configure an Association28Distributing the Network Configuration File30Starting the Network Wizard31Step 1 - Clients and Servers Creation32Step 2 - Real-time Data Acquisition Server Association Configuration34Step 3 - Historical Data Server Association Configuration36Step 4 - Client and Server List Generation38Step RDS1 Remote Desktop Session Host Servers Configuration39Step RDS2 - Server Creation41Step RDS3 - Real-time Data Acquisition Server Association Configuration43Step RDS4 - Historical Data Server Association Configuration44Step RDS5 - Client Creation45Step RDS6 - RD Session Hosted Client as Network Dongle Renter47Step RDS7 - Client and Server Network Dongle Renter Assignment49Step RDS8 - IP Conflict and Network Architecture Preview51Step RDS9 - Client and Server List Generation53How to Configure the Variables Tree for Networked Applications54Behaviour of Variables on a Client Station56Overview of Redundant Configurations57Multiple Active Server Architecture58Single Active Server Architecture59One for Many Architecture60Behaviour of Variables on a Passive Server61Using Redundant Configurations for Historical Data62Controlling and Managing Redundant Operation Using SCADA Basic63Network Status Variables Naming Rules64Network Status Variables Availability65Variable Providing Station ID66Variables Providing the Connection Status Between Two Stations67Variables Related to an Association68Variables Related to the Number of Established Connections70Variables Related to Connection Activity71Variables used to Monitor Connections (Watchdogs)72Using the Network Status Variables73Important Note About Terminology75Overview of Deploying the Supervisor Using a RD Session Host76Licensing the Supervisor Using a Network Dongle77Why Use Central Project Management When Deploying the Supervisor Using a RDS Host?79The Startup Process When Running the Supervisor in an RD Session Host Session80Changes to the Management of Trace Files When Running the Supervisor in a RD Session Host Session82Architecture Examples When Deploying the Supervisor on a RD Session Host Server83RD Session Host Session Related Properties in Station Configuration84Properties Directly Related to Running the Supervisor in a RD Session Host Session85Configuring User Permissions for the Supervisors Folders When Running on an RD Session Host Session86Using the Supervisors RD Session Host Service89Changing the Supervisors Command Line When Running in a Remote Desktop Session90Allocating Port Numbers When Running in a RD Session Host Session92Architecture Examples When Deploying the Supervisor on a RD Session Host Server93Project Path When Using a RD Session Host Server94Managing Persistent Variables When Running the Supervisor in a RD Session Host Session96Optimizing the Project Size97Printing When Running the Supervisor in a RD Session Host Session98Issues Related to Sharing the Same Project99Architecture Examples - 1 Server Station and 2 Client Station100Architecture Examples - 2 SCADA Station and 1 Client Station101Architecture Examples - 2 Redundant Server Stations and 1 Client Station102Architecture Examples - 1 for Many Redundant Servers and 2 Clients103Overview of Networked ApplicationsThe Supervisors network capability allows two or more Supervisor stations to be connected together using a network supporting either TCP/IP or NetBIOS. When stations are connected in this way, the real time properties (value, status etc.) of identically named variables in the stations can be shared.The most usual reasons for using networked configurations are: Operation. An installation requires several operating stations. Application size. The application is simply too large or requires too much processing power to be accommodated on one PC. Redundancy. The Supervisor supports special types of multi-station configurations (known as associations) to provide redundancy, that may be used in situations where continuous operation is essential. Stations exchange information by holding a conversation over the network. The station that initiates the conversation is known as the client. The station that responds is known as the server. In practice it is possible for a station to be both client and server, communicating with one or more other stations.The flow of data between client and server stations is bidirectional. That is to say, a change in the value of a variable in one station will always be reflected by its equivalent variables in all other stations. For example the server may have a variable with Equipment source linked to a process controller. The variable has been given control attributes, so that a User may change its value and send it to the process controller. The equivalent variable in the client also has the control attribute set. When a User changes the value at the client, the change will be reflected at the server and the value sent to the process controller.TCP/IP is the preferred connection method. NetBIOS is now only included for compatibility with projects created with older versions of the Supervisor.The network architecture is configured from the Networking folder of the Application Explorer. Using the Application Explorer you: Define the stations of which the project comprises. Define the network connection (known as nodes) for each station. Define associations if you are developing a redundant application. Create the client and server lists used to control the behaviour of a number of aspects of the Supervisors configuration so that the same project can be used on all stations in a multi-station application.The maximum number of stations in a single networked application is 254.About Client and Server TerminologyAs the Supervisor has evolved the use of the terms Client and Server has proliferated to have several different meanings. Before configuring any aspect of the Supervisors networking it is essential to understand each meaning and the aspect of configuration to which it applies.Client and server licensesThe Supervisors license is determined by the software protection key (dongle) that has been purchased. A client license means that the Supervisor that has no communication capability other than with another Supervisor. The Supervisors data acquisition (native communication, OPC client, DDE, BACnet, IEC 60870-5-104, IEC 61850 and Lonworks) is disabled. All other aspects of the Supervisor are available. A server license means that the Supervisor can only display a single mimic. The mimic is normally used to display communication status. All other aspects of the Supervisor are available.A station with a SCADA license is able to communicate with other Supervisor stations and has none of the above functional limitations. You could consider it to be a combined client and server license.Client and server stationsA stations client and server capability is determined by the projects configuration. A Supervisor configured as a server station can send changes in value of one or more of its variables to other (client) stations. A server station is said to produce the value of variables. The value of a particular variable can only be produced on one server station at any one time. A Supervisor configured as a client station can obtain the value of one or more of its variables from another (server) station. A client station is said to consume the value of variables. The value of the same variable can be consumed on many client stations.By default a station is configured as both a client and a server station. It is normal to leave it configured in this way although it might only be required to produce the value of variables OR consume the value of variables (depending on the configuration and use of the client and server lists).Client and server listsClient and server lists are created as part of the project configuration and are used to control the behaviour of certain aspects of the Supervisors project according to the station on which it is loaded. A server list contains the name of one or more server stations or associations. A client list contains the name of one or more client stations.The most frequent use of the client and server lists is to control on which station the real-time value of a variable is produced and on which station(s) it is consumed. They can also be used to control on which station an archive unit is an archive server (recording real-time data and producing historical data) and on which station it is an archive client (consuming historical data).Networked Applications - Frequently Asked QuestionsWhat is a station?A station is a PC that is running the Supervisor.What is a node?A node defines the physical connection between a station and the network. The node defines the connection type (TCP/IP or NetBIOS), the connection properties and if the station is to behave as a client or server or both.Can I configure more than one node per station?It is possible to configure up to four nodes for each station. Additional nodes can be used for network redundancy or if access is required to stations on physically separate networks.What protocol can I use?The Supervisors networking can use either the NetBIOS or TCP/IP protocols.Can I mix NetBIOS and TCP/IP nodes on the same station?Yes, it is possible to mix NetBIOS and TCP/IP nodes on the same station.How is a station identified?Each station is identified by a unique station name and number. If you are using TCP/IP a stations name and number is linked to its TCP/IP address or Computer Name. If you are using NetBIOS a stations name and number is linked to a LANA number.What is a server station?A server station is a station that sends changes in value of one or more of its variables to other (client) stations. The origin of the value could be one of the Supervisors Data Acquisition sources or internally generated (Expression SCADA BAsic etc.)The mechanism of sending changes in value is known as producing. The value of a variable can only be produced on one station at any one time.What is a client station?A client station is a station where the value of one or more of its variables is obtained from another (server) station. The mechanism of obtaining values in this way is known as consuming. The value of a variable can be consumed on many stations.Can a station be both client and server?A station can be both client and server producing some variable values and consuming others.Can the value of a variable be changed on a client station?The value of a variable can be changed on a client station if the variables control attribute is enabled. The value can be changed by either a send type animation or a program. The client station sends the server station a request to change the value. The server station changes the value in its variables tree and then distributes it as it would any other value change. The client station does not change the value directly.How is a link between a server station and a client station established?The client is responsible for establishing the link to the server. The server has no knowledge of the client until it makes a request for connection.How does a station know that it is to produce or consume the value of a particular variable?When a variable is created it is allocated to a client list and a server list. If the name of the local station appears in a variables server list, the variables value is to be produced on that station. If the name of the local station appears in a variables client list, the variables value is to be consumed on that station. If the name of the local station does not appear in either the variables client or server list, the variable is not loaded and is not available on that station.What is an Association?An Association is a group of two or more servers operating together to provide redundant operation. As far as the client is concerned, an Association is treated in the same way as if it were just a single server station.What are the station lists?A station list contains the name of one or more stations. Station lists may contain the names of only server stations, only client stations or both.It is essential to understand the use of the station lists as they are used to control the behaviour of a number of aspects of the Supervisors configuration so that the same project can be used on all stations in a multi-station application.How do I develop the projects for each station?Projects are developed in the normal way. Careful use of the client and server station lists will allow an identical project to be used for all stations in the majority of cases. Does the network configuration have to be the same on all stations in the network?Yes, the network configuration should be the same on each station, except in some very specific cases.Understanding IP AddressingThis topic provides useful background information for someone intending to configure a networked application using TCP/IP.Each connection point (node) on an IP network has a unique IP address. For example a PC with two network cards would have two connection points and hence two IP addresses.IP addresses can either be static, allocated by a configuration tool on the equipment in which the node resides, or dynamic and allocated by a network administration tool each time the node connects to the network. For a PC running Microsoft Windows, static addresses are entered as part of Windows network configuration. If you are using a dynamic address then it is allocated by a device on the network known as DHCP (Dynamic Host Configuration Protocol) server. For use with the Supervisors networking it is recommended that you use static addressing.The IP address structureIP currently uses a 32 bit address allowing for a theoretical maximum of 232 addresses (approximately 4.3 billion). The address is represented as four bytes written as four decimal values separated by full stops, for example . The address is divided into two parts, the network number (often known as the subnet) and the host (or machine) number. All hosts on the same IP network must share the same network number but have a unique host number. The address split can be done in one of three ways resulting in what is known as the A, B and C address classes. ClassMask1st byte2nd byte3rd byte 4th byteASubnet number1 to 127Host number0 to 255Host number0 to 255Host number0 to 255BSubnet number128 to 191Subnet number0 to 255Host number0 to 255Host number0 to 255CSubnet number192 to 223Subnet number0 to 255Subnet number0 to 255Host number0 to 255Allocating IP addressesBlocks of IP addresses are allocated by an international organization known as the NIC. This ensures that each node has a unique address world-wide thereby eliminating problems that would occur with two identical addresses on the same network. All class A addresses and most class B addresses are already allocated.The exception to this is a range of IP addresses known as Private Addresses. These can be used for any nodes that are NOT exposed to the outside world, for example the Local Area Network (LAN) in a factory. There are three private address ranges, one in each of the address classes. For small LANs of under 255 machines the Class C range is generally used. The table below illustrates the three private address ranges.ClassStart of rangeEnd of rangeMaskA55B55C55255.3 and .255 host addresses have special use and are not used by normal nodes hence the practical limit to the number of addresses is 254.Examples of class C IP addressingComputerIP addressSubnet maskNetwork numberMachine numberPippin192.168.23Frodo192.168.24Gandalf192.168.223Aragorn192.168.224In the above example Pippin and Frodo are on one subnet whilst Gandalf and Aragorn are on another. Therefore Pippin and Frodo will be able to exchange information with one another but not with Gandalf and Aragorn.Important note about using more than one node on a PC running WindowsIf you use more than one node on a PC running Windows (for example to make use of the Supervisors dual network capability) then each node must use a different subnet.Checking the Network Setup when Using TCP/IPIf using NETbios see the topic Checking the network setup when using NETbios.Windows 71. Using the Start menu open the Control Panel and select View network status and tasks. The Network and Sharing Centre dialog opens.2. From the task list in the left pane select Change adapter settings. The Network Connections dialog opens displaying the connections available on your PC. Show picture3. Right click the icon representing the network connection that you will be using and, from the pop-up menu, select the Properties command. The