Node object has two ip adresses, causes system alarm about PU410 node down.

I have a reocurring system alarm, which I think is caused because there are two entries for IP adresses in the node object. In attachement the whole setup is displayed.

Anyone know a solution to solve this? I had made a mistake at the initial setup of the system (rnrp config) and this is the result from that mistake.

 NetworkSetup_documen.pdf


Add New Comment


WvanWees   

asked 2 years ago
Closed



Best Answer

1

A PU410 should be on a local RNRP network area (suggested IP address is 172.16.168.x - third byte contain "128" which hides the area, the remainder is 40 throwing RNRP Area 10) making it invisible to all nodes, except for the ones with physical connection to the area.

If AS and CS is combined, the System Alarm service will see & monitor the local PU410 (but not the redundant which is "beyond" another server that should have Local flag set for the PU410 area).

If the RNRP Monitor (and log file; C:\ProgramData\RnrpEvent.log) agree, i.e. PU410 being reported down there seem to be some issue with the network; check NIC settings, cabling, VMware settings (type of virtual NIC, etc.), etc.

Regardless of hidden or not hidden, the PU410 connection should not be reported down unless you have unplugged or shut the PU410 down.

The IP-addresses displayed in the Node Definition aspect's Configuration tab is not what you might expect.

The aspect works in "three modes":

Mode 1 : The "own" node's Node Definition is called for display (the node where your workplace was launched in): the addresses returned come from "ipconfig" (all local interfaces with an IP address will show up).

Mode 2: A different node is being displayed (your workplace is running at ENG1, but you called AS1's Node Definition): the addresses returned come from what the "hosts" file contain in your node. Starting with 5.1, RNRP injects addresses into the hosts file. In previous versions, I believe a DNS request is made and the content is drawn from the DNS server's Forward Lookup Zone.

Below; I have "injected" a phony address into the hosts file - which is then showed when calling the Node Definition aspect.

Mode 3: The aspect has been manually edited (which is possible after hitting the "F2" key) and the addresses are hardcoded. This *was* recommended in SV 2.1, but should not be made in SV 3 and later; nodename is expected!

So depending on what you checked it can be:

a) A problem with the network that need to be sorted out.

b) You checked your local machine and some additional NIC was listed; no worries...

c) You checked a remote node, but the hosts file (or DNS) need to be cleaned from the bad address

d) Someone has manually edited the entry. Restore original (nodename)

Stefan Stromqvist   

answered 2 years ago


 


Add New Comment


Answers

0

RNRP config:

Why have you changed the "Base Adress (implicit adresses)"? If you use the standard entry "172.16.0.0 then your PU410 adresses will be implicit as Network 10. You need only "Number of used exlicit addr Tabs = 1" on both servers for your 152.128... adress.

But I don't know if it solve your original problem, just give it a try. Remember to restart RNRP.

erik   

answered 2 years ago


 


By WvanWees on 4/11/2016 | Like (0) | Report

Well I quess I mis interpret the manual at that time. If I read it now I could have gone for a mix of implicit and explicit.


Add New Comment


1

A PU410 should be on a local RNRP network area (suggested IP address is 172.16.168.x - third byte contain "128" which hides the area, the remainder is 40 throwing RNRP Area 10) making it invisible to all nodes, except for the ones with physical connection to the area.

If AS and CS is combined, the System Alarm service will see & monitor the local PU410 (but not the redundant which is "beyond" another server that should have Local flag set for the PU410 area).

If the RNRP Monitor (and log file; C:\ProgramData\RnrpEvent.log) agree, i.e. PU410 being reported down there seem to be some issue with the network; check NIC settings, cabling, VMware settings (type of virtual NIC, etc.), etc.

Regardless of hidden or not hidden, the PU410 connection should not be reported down unless you have unplugged or shut the PU410 down.

The IP-addresses displayed in the Node Definition aspect's Configuration tab is not what you might expect.

The aspect works in "three modes":

Mode 1 : The "own" node's Node Definition is called for display (the node where your workplace was launched in): the addresses returned come from "ipconfig" (all local interfaces with an IP address will show up).

Mode 2: A different node is being displayed (your workplace is running at ENG1, but you called AS1's Node Definition): the addresses returned come from what the "hosts" file contain in your node. Starting with 5.1, RNRP injects addresses into the hosts file. In previous versions, I believe a DNS request is made and the content is drawn from the DNS server's Forward Lookup Zone.

Below; I have "injected" a phony address into the hosts file - which is then showed when calling the Node Definition aspect.

Mode 3: The aspect has been manually edited (which is possible after hitting the "F2" key) and the addresses are hardcoded. This *was* recommended in SV 2.1, but should not be made in SV 3 and later; nodename is expected!

So depending on what you checked it can be:

a) A problem with the network that need to be sorted out.

b) You checked your local machine and some additional NIC was listed; no worries...

c) You checked a remote node, but the hosts file (or DNS) need to be cleaned from the bad address

d) Someone has manually edited the entry. Restore original (nodename)

Stefan Stromqvist   

answered 2 years ago


 


Add New Comment


0

Thanks for your reply. System is a 5.1 system in a workgroup (no DNS) and it's physical hardware. PU410 works correct for PRIASCS400. I tried editting the node object but the ip adress returns. The thing that I don't understand is that it doesn't happen on the SECASCS400. So the primay server has an extra entry in the node object and has the alarm, but works correct. To me it looks like a stale alarm from the engineering fase.

WvanWees   

answered 2 years ago


 


Add New Comment


1

Did you observe the "mode issue" when reviewing IP addresses in the Node Definitions?

Any edited data should be reverted to pure/sole hostname. Then the hosts file content will be shown in mode 2 (viewing another node's addresses).

Compare hosts files if mode 2 show differences - use RNRP wizard to refresh hosts file(s).

The "Register This Connection In DNS" setting on a NIC decide if the node/NIC will be inserted to remote hosts files or not. RNRP Monitor will list a node appended with "h,name=..." if this setting is enabled and only "name=..." if not. The setting should be enabled for NICs on all Client/Server network paths, but *may* be off for other NICs to prevent undesired addresses to show up in the Node Definition.


Last; the RNRP Filter in the Base Config Wizard should be set with the Client/Server network paths to restrict 800xA traffic to those paths only.

Stefan Stromqvist   

answered 2 years ago


 


By erik on 4/13/2016 | Like (0) | Report

interesting information, I was ever wondering about the difference "h,name" and "name"


By WvanWees on 4/13/2016 | Like (0) | Report

I've read your previous answer again about the mode and I'm not sure. I'll have to check that. The customer is in a remote location and I haven't got access to the system. I'll close this for now ang get back if it's solved or if I have new info. Thank's for your help.


By Stefan Stromqvist on 4/13/2016 | Like (0) | Report

OK; once you've cracked how this "strange" aspect works (content will differ depending on "viewing angle") you can start trusting its content.

In brief; *never* use it to check your local machine's IP addresses.

Ergo: To reliably check all node IPs using this aspect; you *must* use Plant Explorer in at least two different computers (avoid mode 1).


Add New Comment



Get weekly AKS updates


Partner Exclusive Webinars

 

> – Login to the partner portal to register



Points Redemption Program - Redeem your points for ABB training, Bluetooth speakers and mugs. Terms and conditions >


Earn points when you refer a friend
AKS Referral Program is "Live" - Learn more



AKS Experts


avatar
Ask nikismith   

Rank: 255

I have been a part of the Recording & Control Factory team for 17 years in total, having spent a number of years as a repairs technician withi the manufacturing department, but being in my current role for 9 years now.


avatar
Ask kstoilov   

Rank: 11

Control System Engineer: 800xA, Compact 800, AC500, AC31-50, Advant Master, Simatic, AC&DC Drives 11 years worked for ABB - Control Systems


avatar
Ask Dieter Henkel   

Rank: 19


avatar
Ask Rob Lyon   

Rank: 2

info@lymac.co.nz I'm an independent DCS software and commissioning engineer with extensive experience in 800xA and other ABB products. I've worked in almost every corner of the world and still haven't seen it all.


avatar
Ask Flavio Mussolin   

Rank: 4

ABB AVP, Senior Electronic and Automation Engineer with over 30 years of experience in the field of process automation automotive, pharmaceutical, hollow glass, steel and rolling.


avatar
Ask Govindaraj   

Rank: 9

Working in ABB India Operation Center. Have Project engineering and commissioning experience in ABB 800xA, Freelance, AC500.


avatar
Ask Harsha.D   

Rank: 7

Tech.Support,software and commisioning engineer with Proficient knowledge in 800xA and its products, RNRP,Networking in general.


avatar
Ask MMM   

Rank: 5

ABB PA CT Technical Support


avatar
Ask Sumit Gargav   

Rank: 3

I have worked with Freelance in majority, with 800xA FD and Melody system partly. Also had opportunity to work with Protocols - HART,Profibus,FF & Modbus.


avatar
Ask Ronny Lindström   

Rank: 16

ABB Service Engineer


avatar
Ask Stefan Stromqvist   

Rank: 1

I joined ABB in the year of 1994 and has since 1999 been working as a Service & Support Engineer at BU Control Technologies in Västerås, Sweden. My areas of expertise are: 800xA Base, 800xA for Advant Master, Information Management, operating systems, RNRP and Ethernet comms/networking in general.


avatar
Ask WvanWees   

Rank: 6

I'm a senior service engineer working for ABB in The Netherlands.