800xA Networking topology screen
Hi Dear Experts,
i have two redundant cpu and their ethernet ports are redundant as 172.16.4... and 172.17.4... . I use 5 server and 4 client server which has two ports(172.16.4... and 172.17.4...) in my system. I want to display every ports' status and Computers' status in scada screen. When i open rnrp, i can see everything there.
Is it possible to display them in scada screen. If so how i can do that.
I' m kindly waiting for your help...
i have two redundant cpu and their ethernet ports are redundant as 172.16.4... and 172.17.4... . I use 5 server and 4 client server which has two ports(172.16.4... and 172.17.4...) in my system. I want to display every ports' status and Computers' status in scada screen. When i open rnrp, i can see everything there.
Is it possible to display them in scada screen. If so how i can do that.
I' m kindly waiting for your help...
Asked 1 year ago
Answers
0
Hi,
Please refer the below link for your reference same has been already discussed.
https://forum-controlsystems.abb.com/20200080/Status-of-Ethernet-cable-coonecti
on-of-Engineering-station-or-Operator-station
Please refer the below link for your reference same has been already discussed.
https://forum-controlsystems.abb.com/20200080/Status-of-Ethernet-cable-coonecti
on-of-Engineering-station-or-Operator-station
Answered 1 year ago
0
You can installer the Device Type from PNSM Device Libraries for the Network Switch and can get the port status . Refer "3BUA000447-xxx_x_en_System_800xA_PC_Network_and_Software_Monitoring_Configurat
ion" for details
ion" for details
Answered 1 year ago
2
There is no direct connection between RNRP status and any OPC property.
RNRP node status is highly local information and may differ between two nodes depending on the situation. The System Alarm List's "Network Connection" errors are derived from the primary aspect server's "feel" of the network. Depending on the actual error, it may show up different between the local and remote node(s). E.g if the primary aspect server is disconnected from the primary network it will report all those paths/nodes down while in fact there is only one path down at one node: AS1's primary connection.
There is currently no substitute to the RNRP Monitor and RNRP Network Status (v6->) tools.
The best alternative (in my opinion) I know of without involving too many relaying agents and services is to use the System Alarm List and the Network Connection alarms as input to process graphics.
This is no complete guide; you will have to find out some details yourself.
1) Create an Alarm Conditions aspect on an arbitrary node in the Node Administration Structure
2) Populate it using the Load button (hope it works...)
3) Examine the properties exposed by this aspect (call Object or Aspect Details from context menu go to Property information tab and Subscribe for live data)
4) The alarm priority value will reflect the network connection status
- 0 = no alarm (full connection with node)
- 1 = high alarm (no connection with node)
- 2 = medium alarm (limited connection with node, singular path only)
This method does not allow to identify if primary or secondary path is down, but you can at least display three different states (e.g. red, amber and green).
Bulk Data Manager or copy/pase the Alarm Conditions aspect to as many nodes you need to supervise.
Remember, the OPC data is reflecting the primary aspect server's view. Pull the primary connection out of AS1 and you will have red or amber for all nodes... which is not a perfect reflection of the network status.
RNRP node status is highly local information and may differ between two nodes depending on the situation. The System Alarm List's "Network Connection" errors are derived from the primary aspect server's "feel" of the network. Depending on the actual error, it may show up different between the local and remote node(s). E.g if the primary aspect server is disconnected from the primary network it will report all those paths/nodes down while in fact there is only one path down at one node: AS1's primary connection.
There is currently no substitute to the RNRP Monitor and RNRP Network Status (v6->) tools.
The best alternative (in my opinion) I know of without involving too many relaying agents and services is to use the System Alarm List and the Network Connection alarms as input to process graphics.
This is no complete guide; you will have to find out some details yourself.
1) Create an Alarm Conditions aspect on an arbitrary node in the Node Administration Structure
2) Populate it using the Load button (hope it works...)
3) Examine the properties exposed by this aspect (call Object or Aspect Details from context menu go to Property information tab and Subscribe for live data)
4) The alarm priority value will reflect the network connection status
- 0 = no alarm (full connection with node)
- 1 = high alarm (no connection with node)
- 2 = medium alarm (limited connection with node, singular path only)
This method does not allow to identify if primary or secondary path is down, but you can at least display three different states (e.g. red, amber and green).
Bulk Data Manager or copy/pase the Alarm Conditions aspect to as many nodes you need to supervise.
Remember, the OPC data is reflecting the primary aspect server's view. Pull the primary connection out of AS1 and you will have red or amber for all nodes... which is not a perfect reflection of the network status.
Add new comment