Course T305, 800xA System Administration

Chapter 7 Network and Network Monitoring

Chapter 7 Network and Network Monitoring

TABLE OF CONTENTS

Chapter 7 Network and Network Monitoring..............................................................................................................................7-1

7.1 General Information...........................................................................................................................................................7-2
7.1.1 Description..................................................................................................................................................................7-2
7.1.2 Status report.................................................................................................................................................................7-2
7.1.3 Objectives....................................................................................................................................................................7-2
7.1.4 Reference Documentation...........................................................................................................................................7-2
7.2 Network introduction..........................................................................................................................................................7-3
7.2.1 Network topologies.....................................................................................................................................................7-3
7.2.2 Basic Network Redundancy........................................................................................................................................7-4
7.3 Redundant Network Configuration....................................................................................................................................7-5
7.3.1 Redundant Network Routing Protocol (RNRP)..........................................................................................................7-5
7.3.2 Network Areas.............................................................................................................................................................7-6
7.3.3 Fault Handling within a Network Area.......................................................................................................................7-7
7.3.4 Network fail over time.................................................................................................................................................7-7
7.3.5 Multiple Network Areas..............................................................................................................................................7-8
7.3.6 RNRP Addressing.......................................................................................................................................................7-8
7.3.7 Address Rules for Implicit RNRP Configuration......................................................................................................7-13
7.3.8 Explicit RNRP Configuration....................................................................................................................................7-17
7.3.9 Domain Name System DNS......................................................................................................................................7-19
7.3.10 NetBIOS Considerations.........................................................................................................................................7-19
7.3.11 TCP/IP Interface Configuration..............................................................................................................................7-20
7.4 Network Monitoring.........................................................................................................................................................7-29
7.4.1 System Status Viewer................................................................................................................................................7-29
7.4.2 Network Event and Alarms.......................................................................................................................................7-30
7.4.3 Verifying DNS Configuration, nslookup..................................................................................................................7-31
7.4.4 Verifying NetBIOS Configuration............................................................................................................................7-31
7.4.5 Ping............................................................................................................................................................................7-31
7.4.6 RNRP Network Monitor............................................................................................................................................7-32
7.4.7 Network Interface Supervision in a Controller.........................................................................................................7-33
7.4.8 Network monitoring from within Windows..............................................................................................................7-33

1
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.1 General Information

This Chapter does not describe configuration of general purpose networks, such as an
office or plant network, neither does it cover the situation where 800xA System
products are connected to a general purpose network.

7.1.1 Description
This chapter contains the basic requirements to configure a single network and a
redundant network using RNRP in an 800xA system.
This Chapter describes how to configure the 800xA Automation System Network,
including the Client Server Network, the Control Network, and how to connect to a
Plant Network.

7.1.2 Status report

A non-redundant 800xA system ABBSx1 and one client ABBSx2 are running. The
User accounts 800xAAdmin, 800xAService, Administrator and opx are configured.
The TCP/IP configuration for one adapter/interface is done in all computers. The
Lookup Zones are configured for one TCP/IP adapter in all computers (collapsed
server/client and control network). A redundant switch and redundant TCP/IP adapters
are physically installed. The redundancy will be configured later. The application is
down loaded in the AC800M, and the OPC/AD, OPC/AE and OPC/HDA services are
verified.
Security & Audit configuration of the 800xA System is done.

7.1.3 Objectives
On completion of this chapter you will be able to:
 Describe the different network topologies within the 800xA system
 Describe the difference between a Network area and multiple Network areas
 Describe how to select and IP addresses.
 Configure TCP/IP interface and RNRP settings.
 Describe the system supervision for networking.
 Use Network monitoring tools.

7.1.4 Reference Documentation

Automation System Network – Design and Configuration 3BSE034463R101

2
 Course T305, 800xA Core System Administration

7.2 Network introduction

This section introduces the main areas covered by this Chapter:
 Network Topologies.
 Network Redundancy.
 Selection of IP addresses.
 TCP/IP Configuration.
 Network Monitoring.

7.2.1 Network topologies

System communication in the Industrial IT System is based on Ethernet and TCP/IP
networks, which are functionally and, in most cases, also physically built in levels.

Thin Clients
Internet

Firewall
Thin Clients

Plant Network
Router
Firewall
Citrix Application Workplaces
Server(s) Server(s)

Client/Server Network

Aspect Connectivity
Server(s) Server(s)

Control Network

Controllers

Fieldbus
Field
devices

3
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.2.1.1 Plant Network

The Plant Network can be dedicated for process automation purposes or be a part of
the plant intranet already available on a site.

7.2.1.2 Client/Server Network

The Client/Server network is used for communication between servers, and between
client Workplaces and servers. The Client/Server Network is a trusted network zone
that should be protected by firewalls. It is a private IP network that uses static
addresses. The Client/Server Network can optionally be made redundant.

7.2.1.3 Control Network

The Control Network is a local area network (LAN) optimized for high performance
and reliable communication, with predictable response times in real time. Controllers
and Connectivity Servers are connected to the control network. The Control Network
is based on Ethernet using the MMS protocol on top of a TCP/IP protocol stack, plus
additional services for time distribution, redundancy features, etc.
The control network can optionally be made redundant using the RNRP redundancy
protocol. Controllers connect to the control network via dual built-in network ports.
Server and client PCs need additional network cards to adapt to redundant networks.
Due to security and performance reasons only Industrial IT Certified products should
be connected on the Client/Server Network.

7.2.2 Basic Network Redundancy

Industrial applications require high availability. The effects of a network error must be
reduced to a minimum. Single points of failure should, if possible, be avoided. For
high availability, all network devices (cables, switches, routers and network adapters)
should be duplicated in physically separated network paths. The two network paths are
named Primary Network and Secondary Network or Back-up Network.
As long as the primary network paths is working, all process data is sent on that
network. The secondary network carries NO traffic and, is always 100% available.
This guarantees that network performance is not affected after a network fail over.
Both supervision of network paths and fail-over between Primary and Secondary
networks are performed by RNRP, The Redundant Network Routing protocol. RNRP
is a IPv4 routing protocol developed by ABB.
In order to have a robust redundant system, it is very important to have continuous
supervision of all network paths on a node-to-node basis, not only on individual
network devices. A detected network error results in fault annunciation.

4
 Course T305, 800xA Core System Administration

7.3 Redundant Network Configuration

This section describes the Network Redundancy based on the Redundant Network
Routing Protocol (RNRP). The main areas covered are:
 The concepts of the RNRP protocol
 How to build different network structures
 How to choose addresses
 How to configure nodes; PCs and Controllers

7.3.1 Redundant Network Routing Protocol (RNRP)

RNRP is an IPv4 routing protocol developed by ABB. It is specially designed for use
in automation networks with limited topology but with high demands on network
availability. RNRP provides the following features:
 Network redundancy
The protocol supports redundant physical networks, full redundancy including
network interface boards, between end nodes.
Each node cyclically sends a routing vector as a multicast message on both
networks. The routing vector indicates which other nodes this node can see on the
network. Each node uses received routing vectors to build a table listing which
nodes can be reached on which of the two networks. Routing vectors are
distributed with a cycle of 1 second.
If a network error occurs, RNRP updates the system IP Routing Table with a
good network path within the time of the RNRP send period. The send period is
as default 1 second.

Primary
Network

Secondary
Network

5
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

 Routing between network areas

IP routes to all neighbor nodes and subnet are automatically maintained in the IP
Routing Table in every node. A node with RNRP can act as an IP router and
forward messages on best path to destination nodes.
 Node and network supervision RNRP quickly detects if a node or remote network
is down and sends this events to connected applications. This information is used
to detect if a redundant server is down and whether a new server can be
connected.
The RNRP redundancy concept works with standard network devices (hubs, switches
or bridges), no special network interface cards (NICs) are required. The protocol gives
high flexibility to integrate networks with different types of data links like PPP and
Ethernet. The routing update period can be configured to fit on very slow serial links
as well as on high-speed networks mixed in the same Control Network.

7.3.2 Network Areas

 A network that uses RNRP is built up by one or more Network Areas.
 A Network Area is a logically flat network structure without routers.
Routers are not allowed within a Network Area. A Network Area with redundancy
contains two independent IP networks with equal capacity. The individual networks
within a Network Area are assigned Path Numbers.
 The primary network has Path Number = 0 and the secondary network has Path
Number = 1.

Primary Network
Path Number = 0 Node Numbers
11 12

Secondary Network
Path Number = 1 151 152 153

A node is identified in RNRP by:

 Network area number (0 - 31)
 Node number (1 - 500)
The path number is a parameter on each network interface
In case of error on the primary network, the Redundant Network Routing Protocol
(RNRP) redirects traffic over to the secondary network (the backup network) without
involving any application program. Nodes with redundant interfaces and nodes with a
single interface can be mixed on the same Network Area. A node with only one
interface must only be connected to the primary network.

6
 Course T305, 800xA Core System Administration

7.3.3 Fault Handling within a Network Area

Within a Network Area RNRP can handle single network errors in all node-to-node
connections. In the example below, node A has an error on the connection to the
primary network and node B an error on the connection to the secondary network.

A B

Network Errors

C D E

In this example communication between node A and node B is not possible but all
other peer communication will work.
Node A can communicate over secondary network with nodes C, D and E.
Node B can communicate over primary network with nodes C, D and E.
Nodes C, D and E are fully redundant to each other.

7.3.4 Network fail over time

The time required for RNRP to redirect traffic from a faulty path to a good path is the
same as the configured RNRP parameter Send Period.

7
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.3.5 Multiple Network Areas

There are a number of reasons why a network should be divided into Network Areas
(subnetworks):
 Fault isolation. An erroneous network segment (bad cable, Ethernet switch or
interface card) cannot affect nodes on other Network Areas.
 Traffic filtering. A router can block undesired traffic if filter software is installed.
This is true for a Windows Server node.
 Limitation of broadcast traffic. A router does not (by default) forward broadcast
and multicast messages.
 The network is distributed over large distances using link protocols with different
network characteristics. PPP is one example.
 The IP routing resources (Routing table, ARP table or CPU power et.c.) in a
single node are not large enough to handle a large number of nodes on the same
Network Area.

7.3.5.1 Connectivity Servers as Routers

In systems where the Control Network and the Client Server network are separated,
the addresses on the networks must use different network areas. The connectivity
servers that are connected to both networks will work as RNRP routers. This requires
that the flag “Enable TCP/IP forwarding” be set to 1
All nodes with IP forwarding enabled running the RNRP protocol and are connected
to more than one Network Area and have router capability.

7.3.6 RNRP Addressing

When planning a system the user must decide what IP addresses to use for all nodes in
the system. It is recommended that addresses be selected from a private address space.
This has the following advantages:
 There is no requirement to apply to the licensing authorities for an IP address, i.e.
it is easy to allocate a large IP address space especially in redundant network
configurations.
 Some protection is gained against illegal access because private addresses are not
permitted on the public Internet.
The recommendation below gives a recommendation on IP addresses that will work
for most installations. If this suggestion is followed, then disregard much of the details
about RNRP configuration.
Network Area numbers 1 - 19 for the Client/Server Networks
Network Area numbers 20 - 31 for the Control Networks.
Use the IP address mask 255.255.252.0 on all addresses.
Caution Do not connect more than 50 nodes on a Control
Network Area.

8
 Course T305, 800xA Core System Administration

Addresses recommended on the Client/Server/Control Network Area 1.

Nodes Node Addr on Primary Addr on Secondary

Number Network Network

Domain and DNS 1-10 172.16.0.1- 172.17.0.1-

Servers 172.16.0.10 172.17.0.10
Aspect Servers 11-20 172.16.0.11- 172.17.0.11-
172.16.0.20 172.17.0.20
Connectivity Servers 21-50 172.16.0.21 172.17.0.21-
172.16.0.50 172.17.0.50
Application Servers 51-70 172.16.0.51- 172.17.0.51-
Information Manager 172.16.0.70 172.17.0.70
Batch, 3rd Part Nodes
Workplace Clients 71-150 172.16.0.71- 172.17.0.71-
172.16.0.150 172.17.0.150
Controllers 151-255 172.16.0.151- 172.17.0.151-
172.16.0.255 172.17.0.255
Backup CPU’s for 663-767 172.16.2.151- 172.17.2.151-
Redundant Controllers 172.16.2.255 172.17.2.255
Switches, Gateways, (501-511) 172.16.1.245- 172.17.1.245-
Firewalls 172.16.1.255 172.17.1.255
(not RNRP addresses) (1013-1022) 172.16.3.245- 172.17.3.245-
172.16.3.254 172.17.3.254
Spare, Unused RNRP 256-500 172.16.1.0- 172.17.1.0-
addresses 172.16.1.244 172.17.1.244
Spare (512-662) 172.16.2.0- 172.17.2.0-
(not RNRP addresses) 172.16.2.150 172.17.2.150
(768-1012) 172.16.3.0- 172.17.3.0-
172.16.3.244 172.17.3.244

9
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

Internet

Firewall
Workplaces
Plant Network

Network
Isolation Server
Workplaces
Device
Client/server Network

Servers

Control Network

Controllers

Fieldbus

Field devices

Networks using RNRP

RNRP is used at the Client/Server Network and at the Control Network
RNRP organizes the network into Areas, Paths and Nodes
 A Network Area is a Logically flat network structure with One or two parallel IP
networks (One or two Paths) and No Routing within a Network Area

10
 Course T305, 800xA Core System Administration

Node
Primary network Numbers
1 5
Path = 0

Secondary network
Path = 1
10 20 30

 All nodes within a network area are given unique node numbers

Node 1 Node 2

Path 0 Hub 1
NW Area 0
Path 1 Hub 2

Router Node Node 11

Node 31

Path 0 Hub 5
NW Area 1
NW Area 3 Path 1 Hub 6

Router Node Node 200 Router Node

Node 400 400

Path 0 Hub 3
NW Area 2
Path 1 Hub 4

Node 21

Routing between Network areas.

11
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

A node on a TCP/IP network is identified by its 32-bit IP address. The IP address

consists of a NetID part and a HostID part. The subnet mask specifies the boundary
between the NetID and the HostID. A node with more than one network interface
must have a unique IP address for each interface. Since RNRP is based on IP routing
this is also true for all nodes running RNRP. The interfaces in a node running RNRP
are, however, in addition to the IP address and the subnet mask also configured with
the following logical address parameters:
 Network Area 0 – 31
 Local Flag 0 = Normal Network Area
1 = Local Network Area, no routing to this area.
This area is not announced to other areas.
 Node Number 1 - 500
 Path Number 0 - 1
 The only mandatory rules for these parameters are:
 The Node number must be the same as the HostID (the least significant, right
 most bits in the IP address).
 The NetID (the most significant, left most bits in the IP address) must be the
same for all Interfaces (in all nodes) on the same path in one Network Area, i.e.
all interfaces on one path of a network area must be on the same subnet (as for
normal IP communication, or they cannot reach each other).
To simplify the configuration of the network interfaces there is a set of additional
rules. If these rules are also followed, the RNRP address parameters are automatically
configured. This is called the Implicit RNRP Configuration Method.

If only the mandatory rules are followed, the RNRP address parameters have to be
configured manually for each network interface. This is called the Explicit RNRP
Configuration Method.
Caution If the Explicit RNRP Configuration Method is used,
then AC 800M Controllers and Control Builder M must be in the
same Network Area.
The reason is that AC800M will loose explicitly given RNRP parameters if the
hardware configuration is erased, that is, after a controller reset. If this happens the
AC 800M cannot route to any other network.

12
 Course T305, 800xA Core System Administration

7.3.7 Address Rules for Implicit RNRP Configuration

With the implicit RNRP configuration method all IP addresses have a strict
relationship to the RNRP address parameters. This relationship means that it is
sufficient to configure only the IP address. RNRP can calculate the other address
parameters from the IP address. This is done in each node. The user primarily needs to
complete a reverse calculation to get the IP address:
1. Choose the RNRP address parameters
2. Choose the Base Address.
The base part of the IP addresses: N1.N2.0.0
(the 14 most significant bits with 2 additional zero bits)
This may be chosen freely from RNRP’s point of view, but they must be the same
in the whole system.
3. Calculate the IP address based on the RNRP address parameters
4. Set subnet mask to 255.255.252.0
When using implicit configuration the address mask must be set to 255.255.252.0.
This gives 10 bits for the HostID, i.e. 1024 addresses. This allows the HostID to be
identical to the RNRP Node number that can be 1-500 for normal nodes and 513-1013
for backup CPUs in Redundant Controllers
Caution For a full description of Implicit and explicit address
rules see reference manual Automation System Network Design and
Configuration 3BSE 034 463R101

7.3.7.1 Configuring RNRP (implicit or explicit)

 The RNRP address parameters
(Network Area, Path, Node number, Local Flag) must be assigned to each IP
interface (port) connected to the network.
 Interfaces can be configured in two ways:
 Implicit:
RNRP calculates the RNRP address parameters
based on the IP address of the interface:
1 Decide RNRP parameters (Network Area, Node, Path, Local)
2 Calculate the IP address based on the RNRP address parameters
3 RNRP extracts the RNRP address parameters from the IP address
NOTE! The user configures only the IP address for each
interface
 Explicit:
The user manually configures both the IP address
and the RNRP address parameters for each interface

13
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.3.7.2 Calculating the IP Address Bit by Bit

With a binary representation the IP address must be created as:
XXXXXXXX.XXXXXXPP.LAAAAARN.NNNNNNNN
Where the bits are:
XXXXXXXX.XXXXXX XXXXXXXX.XXXXXX00.00000000.00000000 is
equal to the Base Address
The 14 first bits is the Network Identity
PP Path Number (0 or 1)
L Local Flag, Normally 0 = Routing Enabled
AAAAA Network Area Number (0 to 31)
R Redundant controller CPU
N.NNNNNNNN Node Number (1-500)
The IP network mask must be set to (Subnet mask)
11111111.11111111.11111100.00000000 (= 255.255.252.0)

7.3.7.3 Calculating the IP Address Byte by Byte

With a byte wise representation the IP address must be created as: A.B.C.D where the
bytes are:
A = N1
B = N2 + Path
C = Local*128 + Area*4 + Node DIV 256
D = Node MOD 256
N1.N2 is the Network Identity. Path, Local, Area and Node are the other RNRP
address parameters.
DIV means an integer division and MOD means the Modulo operation, i.e. the rest
after the integer division.
If the Local flag is 0 and the node number is less than 256 the formula is a bit simpler:
A = N1
B = N2 + Path
C = Area*4
D = Node
Example:
Base Address = 172.16.0.0, Network Area = 2, Node number = 201
(Local = 0, Node number < 256) =>
Primary Network Interface (Path = 0): 172.(16+0).(2*4).201 = 172.16.8.201
Secondary Network Interface (Path = 1)172.(16+1).(2*4).201 = 172.17.8.201

14
 Course T305, 800xA Core System Administration

7.3.7.4 Example 1: 24 bit NetID, 8 bit HostID

Bit wise Byte wise

AAAAAAAA.AAAAAAAA.AAAAAAAA.AAAAAAAA A.A.A.A
11111111.11111111.11111111.00000000 X.X.X.0
NNNNNNNN.NNNNNNNN.NNNNNNNN.HHHHHHHH N.N.N.H
 IP Address: 192. 16. 10.56
Subnet mask : 255.255.255. 0
 NetID: 192. 16. 10
HostID : 56

7.3.7.5 Example 2: 22 bit NetID, 10 bit HostID:

Bit wise Byte wise

AAAAAAAA.AAAAAAAA.AAAAAAAA.AAAAAAAA A.A.A .A
11111111.11111111.11111100.00000000 X.X.X0.0
NNNNNNNN.NNNNNNNN.NNNNNNHH.HHHHHHHH N.N.NH.H
 IP Address: 172. 16. 5.101
Subnet mask : 255.255.252. 0
 NetID: 172. 16. 4
HostID : 1.101(=256+101=357)
 The 3:rd byte contains bits from both NetID and HostID

15
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.3.7.6 Base Address

 Base addresses (from private address space) recommended for the Implicit
configuration method:
IP Class A addresses: IP Class B addresses:
10. n*4. 0. 0 n=0,1,2,,,,,63 172.16.0.0
172.20.0.0
172.24.0.0
172.28.0.0
 When using implicit RNRP configuration 2 complete Class B networks shall be
reserved (one if non redundant):
With the base address N1.N2.0.0, this means that the addresses between N1.N2.0.0
and N1.N2+1.255.255 must be free to use, e.g. 172.16.0.0 – 172.17.255.255
 Example:
Implicit Configuration
Two Nodes connected to Network Area 4, one with node number 1 and one with node
number 201. Base address is 172.16.0.0
The Rule: Node 1: Node 201:
A = N1 A = 172 A = 172
B = N2 + Path B = 16 and 17 B = 16 and 17
C = Area*4 C = 4*4 = 16 C = 4*4 = 16
D = Node D=1 C = 4*4 = 16
The nodes will be configured with the following IP addresses:
Node 1: 172.16.16.1 Node 201: 172.16.16.201
172.17.16.1 172.17.16.201
More RNRP parameters
 Parameters for the network size (In most cases the default values can be used):
 Maximum number of Network Areas that can be installed in this node.
An end node always uses one Network Area.
 Maximum number of remote Network Areas to which this node can be
connected.
 The maximum accepted hop count (number of passed routers) in the network.
 Supervision tuning parameters:
 Send Period: The time period for multicasting of routing messages. This is
also the minimum time for fail over in a redundant network.
 Number of routing messages that may be lost until a path to a node is down.
 Time(s) to detect node down = Send Period * (Max Lost Messages + 1)

16
 Course T305, 800xA Core System Administration

7.3.8 Explicit RNRP Configuration

 Cases when implicit configuration can not be used:
 If the user has some special requirement on choice of IP addresses so that two
consecutive class B addresses can not be reserved
(N1.N2.0.0 – N1.N2+1.255.255)
 If the supervision tuning parameters (e.g. send period) can not be the same for
all interfaces in a node
 For special interfaces: PPP and Tunnel Areas

PC is done with the Setup Wizard

17
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

Controller done with the Control Builder

Choosing IP addresses
 Use addresses that allow implicit RNRP configuration
Define groups for similar node types
Use the same group definitions on all Network areas, e.g. 101 is always a client
 Nodes connected to several areas shall use the same node number on all networks
 Use the default rule for redundant controllers
(Backup address = Primary address + 0.0.2.0)
 Use node numbers below 256 if possible
 Node number = Last digit in IP address
 Use only one network area if it is possible

7.3.8.1 Mixing Explicit and Implicit RNRP Configuration

All nodes on the same network area must use the same configuration method for the
interfaces towards that area.
In different Network areas of a system it is possible to use different methods.

18
 Course T305, 800xA Core System Administration

7.3.9 Domain Name System DNS

DNS (Domain Name system) is a hierarchical name service for domains and IP
addresses. The DNS service enables client nodes on your network to register and
resolve DNS domain names. All Industrial IT applications that identify other nodes by
name, i.e. not only by IP Address, use DNS to find the corresponding IP address.
The names and IP Addresses are stored in a DNS database. A DNS Server is a server
containing information about a portion of the DNS database. The DNS server handles
queries from DNS clients.
There are two types of DNS queries:
 I know the name of a node. What is its IP address?
This is called Forward Lookup.
 I know the IP Address of a node. What is its name?
This is called Reverse Lookup.
To serve these queries the information in a DNS database is organized in Forward
Lookup Zones and Reverse Lookup Zones.

DNS Client DNS Server

172.16.0.11 – AspectServer1
172.16.0.12 – AspectServer2
172.16.0.21 – ConnectivityServer1
172.16.0.22 – ConnectivityServer2 Lookup tables
172.16.0.51 – BatchManager1
172.16.0.71 – Client1
172.16.0.72 – Client2

7.3.10 NetBIOS Considerations

NetBIOS is an old Microsoft protocol for network communication between computers
with Microsoft Windows operating systems. There are however still some functions
that need NetBIOS. It is used by the Windows Explorer to browse neighbor computers
under “My Network Places\Entire Network\Microsoft Windows Network”, and it is
also used to locate possible nodes for connection of Clients and Servers when running
the Configuration Wizard.
This means that NetBIOS is needed on the Client Server network. It is however not
needed on the Control Network. NetBIOS and the browsing functions do however not
work well if the Domain Controller is “Multi Homed”, i.e. is connected to more than
one network. Therefore using redundant networks, NetBIOS should be disabled on the
secondary network.
 The recommendation for NetBIOS configuration is therefore:
 Enable NetBIOS on all interfaces for the Primary Client Server Network.
 Disable NetBIOS on all interfaces for the Secondary Client Server Network.
 Disable NetBIOS on all interfaces for the Control Network.

19
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.3.11 TCP/IP Interface Configuration

7.3.11.1 AC800M Ethernet Configuration

Configure the redundant Ethernet interface and download to the AC800 M

Don’ forget to enable the ethernet channel.

Down load and restart the AC800M.

20
 Course T305, 800xA Core System Administration

7.3.11.2 TCP/IP Network Access

Right click on My Network Places and select Properties to view Network
Connections
Select Advanced Settings in the Advanced menu.

The network service should access Primary TCP/IP interface first, Path 0.

21
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.3.11.3 TCP/IP Properties

Right click on a TCP/IP Interface in the Network Connections window and select
Properties.
Select Internet Protocol (TCP/IP) and click on Properties.

Set the Implicit IP address, subnet mask and DNS server addresses.
When use of redundant Domain Controllers with DNS, each node must be configured
with one DNS Server as the Preferred DNS Server. Normally it is suggested to appoint
one of the Domain Controllers to be the Primary DNS Server.
The Primary Network Interface (which is first in the list of interfaces) must configure
the Primary DNS Server as the Preferred DNS Server, and the Secondary DNS Server
as the Alternate DNS Server.
The Secondary Network Interface must configure the Secondary DNS Server as the
Preferred DNS Server, and the Primary DNS Server as the Alternate DNS Server.

22
 Course T305, 800xA Core System Administration

7.3.11.3.1 Advanced TCP/IP Setting, DNS tab

Check “Append primary and connection specific DNS suffixes”

on the Primary and Secondary TCP/IP interface.
Check “ Register this connection’s addresses in DNS on the Primary TCP/IP interface.
(This will automatically create lookup zones in the DNS server. It’s recommended to
create zones manually for the second interface)

23
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.3.11.4 Advanced TCP/IP Setting, WINS tab

Enable NetBIOS over TCP/IP on the Primary TCP/IP interface.

Disable NetBIOS over TCP/IP on the Secondary TCP/IP interface.

7.3.11.4.1 Enable the TCP/IP Interface

24
 Course T305, 800xA Core System Administration

7.3.11.5 DNS Configuration in the Domain Controller

Start the DNS

The DNS server is running and there are DNS Lookup Zones for each path on each
network area that is included in the domain and where there are nodes that use DNS.
Lookup zones are only needed for a Network if there will be PCs that communicate
with each other via the Network.
The DNS Zones will be automatically or manually populated with records for the PCs
when they join the domain.

Manually add the Reverse Lookup Zone for the Secondary TCP/IP interface.
The Forward Lookup Zone should only be added for the Primary TCP/IP interface,
and the Reverse Lookup Zone for both interfaces.
Select “Active Directory-integrated” Zone Type. It’s recommended; the
synchronization between redundant domain controllers will be better. The Standard
secondary dies about 24 ours after the primary has gone down, and the secondary is of
“read only” type.

25
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

Click next in the configuration wizard until you set the Network ID, next.

Accept the default filename, next and then Finish.

Select properties of the zone.

26
 Course T305, 800xA Core System Administration

Allow dynamic updates

Right click on the new zone and select New Pointer, add one for each interface.

Add Host IP and browse to the Host name, OK!

27
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.3.11.6 TCP/IP Interface Configuration Table

Node name Node Area Path IP address Preferred Alternate NetBIOS Auto Forward Reverse
no. DNS server DNS server reg. in lookup lookup
DNS zone zone
Domain 1 2 0 172.16.8.1 172.16.8.1 172.16.8.2 Yes Yes Yes Yes
Controller 1
1 172.17.8.1 172.16.8.2 172.16.8.1 No No No Yes

Domain 2 2 0 172.16.8.2 172.16.8.2 172.16.8.1 Yes Yes Yes Yes

Controller 2
1 172.17.8.2 172.16.8.1 172.16.8.2 No No No Yes

Aspect & 15 2 0 172.16.8.15 172.16.8.1 172.16.8.2 Yes Yes Yes Yes

Connectivity
server 1 1 172.17.8.15 172.16.8.2 172.16.8.1 No No No Yes

10 0 172.16.40.15 - - No No No No

1 172.17.40.15 - - No No No No

Aspect & 16 2 0 172.16.8.16 172.16.8.1 172.16.8.2 Yes Yes Yes Yes

Connectivity
server 2 1 172.17.8.16 172.16.8.2 172.16.8.1 No No No Yes

10 0 172.16.40.16 - - No No No No

1 172.17.40.16 - - No No No No

1 Client 60 2 0 172.16.8.60 172.16.8.1 172.16.8.2 Yes Yes Yes Yes

Workplace1
1 172.17.8.60 172.16.8.2 172.16.8.1 No No No Yes

AC800M 1 151 10 0 172.16.40.151 - - - - No No

1 172.17.40.151 - - - - No No

AC800M 1 0 172.16.42.151 - - - - No No
redundant cpu
1 172.17.42.151 - - - - No No

Example.

Domain Domain Client

controller 1 controller 2 Workplace 1

Client/Server
Network
Aspect & Aspect &
Connectivity Connectivity
Server 1 Server 2
Control
Network
Redundant Controllers

28
 Course T305, 800xA Core System Administration

7.3.11.7 Redundant Network Interface in the Domain Controller

It’s necessary to change the registry to prevent the DNS to automatically register the
redundant network interface in the forward lookup zone.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\
Parameters\RegisterDnsARecords.
Read more about this in the Microsoft Knowledgebase KB246804 - Dynamic DNS
registrations.
http://support.microsoft.com/default.aspx?scid=kb;en-us;246804
Note: Don’t change the key before the creation of the domain or before adding a
second one. During maintenance of a domain controller (add/remove/reinstall, etc) the
key setting has to be set back to the original.

7.4 Network Monitoring

7.4.1 System Status Viewer

The System Status Viewer in the main Aspect system is used for on line supervision
of the system. Servers and Controllers have system status providers that show their
status. Clients do not have any System Status providers. The System Status viewer can
be added as an aspect on any object. It is by default added to all node objects in the
Node Administration structure,

There are System Status providers for the Controllers. By adding a System Status
Viewer aspect for the Aspect Object representing a Control Network it is possible to
show System Status for all Controllers on that Control Network.

29
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.4.2 Network Event and Alarms

The network events that RNRP detects create a System Messages. These have the
class Network. The messages are:
 Connection Down
 Connection Up
 Node Down
All three event messages generate alarms via System Alarm. It is by that possible to
include these in an alarm list.

30
 Course T305, 800xA Core System Administration

7.4.3 Verifying DNS Configuration, nslookup

Use the command line utility nslookup to verify that the DNS server and the different
nodes in the system are configured correctly. nslookup can do both forward and
reverse lookup queries.

7.4.4 Verifying NetBIOS Configuration

The consequences of an in correctly configured NetBIOS are not always obvious. First
check that all nodes on the Client Server network are visible under “My Network
Places\Entire Network\Microsoft Windows Network”.

7.4.5 Ping
Ping is a simple program for checking whether one node has contact with another
node. Ping is available on all PCs. It is used from the Command prompt and its syntax
is as follows: drive:>ping address
Example:
C:\>ping 172.16.0.201
Pinging 172.16.0.201 with 32 bytes of data:
Reply from 172.16.0.201: bytes=32 time<10ms TTL=64
Reply from 172.16.0.201: bytes=32 time<10ms TTL=64
Reply from 172.16.0.201: bytes=32 time<10ms TTL=64
Reply from 172.16.0.201: bytes=32 time<10ms TTL=64
Ping statistics for 172.16.0.201:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
The node can be specified by name or by IP address, but note that ping is not the
recommended tool for fault tracing of DNS problems.

31
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.4.6 RNRP Network Monitor

In PCs where RNRP is installed there is a tool called the RNRP Network Monitor.
When it starts up, it gives an overview of the entire network as seen from the node
where it is running. For all nodes that are connected, it reports if there is a working
connection for each network interface. After the initial overview all changes to the
current status will be reported as for example node up and node down events. The
RNRP Network Monitor is started with a left-click on the RNRP icon in the Windows
system tray.

32
 Course T305, 800xA Core System Administration

7.4.7 Network Interface Supervision in a Controller

The status of the network interfaces in a controller is indicated in the hardware tree in
the Control Builder when the Control Builder is in on-line mode. The indication No
communication means that RNRP does not detect any nodes via that particular
Network interface.

7.4.8 Network monitoring from within Windows.

Microsoft Management Console (MMC) hosts administrative tools that you can use to
administer networks, computers, services, and other system components.
You can use Microsoft Management Console (MMC) to create, save, and open
administrative tools (called MMC consoles) that manage the hardware, software, and
network components of your Windows system. MMC is a feature of the
Windows 2000 operating system, but you can also run MMC on Windows NT,
Windows 95, and Windows 98 operating systems. In addition, MMC is a feature of
several software applications designed to run on Windows.
MMC does not perform administrative functions, but hosts tools that do. The primary
type of tool you can add to a console is called a snap-in. Other items that you can add
include ActiveX controls, links to Web pages, folders, taskpad views, and tasks. A
MMC console consists of a window divided into two panes. The left pane contains
two tabs: the Tree tab and the Favorites tab. The right pane contains the details pane.
The Tree tab, also called the console tree, shows the items that are available in a given
console. The details pane shows information about, and functions pertaining to, these
items. As you click different items in the console tree, the information in the details
pane changes. The details pane can display many types of information including Web
pages, graphics, charts, tables, and columns.
Each console has its own menus and toolbar, separate from those of the main MMC
window, that help a user perform tasks. For more information about the main MMC
window,
The operating system does have preconfigured and saved console files available in the
Administrative Tools folder in Control Panel.

33
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

7.4.8.1 Using Performance console to Monitor the network

To use a console, you must have access to the services and administrative tools
included in the console, either installed on the local computer or available on the
network. You must also have administrative permissions for the components on the
system that is administered by the console.
 Do the following:

 Click Start, click Settings, click Control Panel and open Administrator tools.

 Open Performance Tools:

34
 Course T305, 800xA Core System Administration

 In the Tree Select System Monitor and select ADD Counters:

 In the Add Counters menu select Network Interface and Select counters from the list

35
Course T305, 800xA System Administration
Chapter 7 Network and Network Monitoring

36
 Course T305, 800xA Core System Administration

 From the console several views are possible, Chart, Histogram, Report

 The MMC can also be saved for later use:

37