Emerson Exchange 365

• Not Answered

Node Address Keeps Changing

Hi,

Our Application workstation has a primary node address of 10.4.0.58. So too does the Engineering Workstation. However, the AWS does not sync with the 10.4.0.58 address. It keeps toggling between 10.4.0.58, and 10.5.0.58. To my knowledge, there isn't any subnet with 5 currently configured. Kindly assist. 

• DeltaV #DCS
• DeltaV

Andy Kay

• 19 Sep 2018 1:04 AM
• Cancel

2 Replies

• Andre Dicaire

  

  • 19 Sep 2018 1:33 AM

  John, you should not have the same IP address on two nodes.
  
  The DeltaV networks use a sub net mask of 255.254.0.0. That means the subnet extends from 10.4.0.1 to 10.5.255.255 for primary and 10.8.0.1 to 10.9.255.255.
  
  Normally redundant nodes have mirrored addresses such that one has 10.4.x.y and 10.5.x.y
  as the primary adresses, and 10.8.x.yand 10.9.x.y for the secondary.
  
  A simplex node would only use the 10.4.x.y and 10.8.x.y addresses.
  
  But under no circumstances should you see two deltaV nodes using the same address as you describe.
  
  Check the properties for each node in Explore and you will see the addresses Deltav has generated for these nodes. If these are the same in the database you have an invalid assignment and you need to engage Emerson GSC to investigate.
  
  If addresses are unique in the database you need to run workstation config with the current devdata.cfg file.
  
  Looking forward to your next post.

  Andre Dicaire

  • Cancel
• Andy Kay

  

  • 4 Oct 2018 3:30 PM

  In reply to Andre Dicaire:

  Thanks for your reply Andre. The problem was fixed. Someone changed the password on our Application Workstation and it was restarted without us knowing about the change. This apparently led to the data not being available due to the different passwords for our EWS and AWS.
  
  I'm doing more research into determining how that affected the node addresses though. As once the password was changed to that of the EWS, the node address worked as expected.

  • Cancel