more quick actions
minimize quick actions
Topic starter
Hi,
A customer has the following architeture
1 single active server realtime association with 3 server stations
Each server has 2 ethernet board (10.128.232.x,10.12.3.x)
5 clients stations are connected on network 1 (10.128.232.x)
5 clients stations are connected on network 2 (10.12.12.x)
The question is : how to configure it?
I think there's 2 options with pro and cons, you may give your thoughs about :
Option 1 : create all the configuration using station names rather than IP addresses.
PROs :
=> In this case Windows will solve Ip addresses(?) and there's no need to declare different nodes in PcVue
CONs :
=> A LMhost file may have to be created (?) and not easy to maintain in large company site
Option 2 : For each server, create 2 nodes (1 for each network) with a different port
For each client stations on Network1, create 1 node for the network1 with the corresponding port
For each client stations on Network2, create 1 node for the network2 with the corresponding port
Question : for the association, do we have to select boths nodes? In this case I'm not sure if PcVue is going to use one as main and the other as redndant?
Or do we have to create 2 associations, one using node for network1 and the other using the node for network2?
PROs : no need to use Lmhost
CONs : not the simplest...
What do you think?
Thank you
Francois
Posted : 13/03/2013 12:21 am
Hi Francois,
Nono did quite the same architecture few years ago (3 networks actually!). The best is to declare 1 node for each Network using 2 different TCP/Ip addresses.
About the Association you must include all nodes on it.
PcVue will manage the rest.
So far, no problems in the Nono's site...
Posted : 13/03/2013 7:14 am
Topic starter
Thank you Nico
That's interesting
Can you confirm that the port must be different for each node as well?
Posted : 13/03/2013 10:00 pm
Hi Francois,
I was very happy to read your question... because we have a similar consideration to take in our upcoming project.
The scenario is slightly different:
- There are two redundant data acquisition servers (SCADA stations).
- For various reasons these two servers shall be available in two networks: in the IT/office network and in the automation network. Thanks to Nico's reply it is clear how to configure this association.
- And then there is one notebook which shall behave as dedicateed client station to the system. The particularity of this station is that it travels between office network and automation network. During day-to-day usage it shall be part of the office network and DHCP client. During maintenance it shall be taken to the facility and be plugged into the automation network by using a static IP address. No DNS-server is available in the automation network.
What would you suggest in this case? To configure the client station with two different network nodes?
One node for usage in the office network using the host name.
And one node for usage in the automation network using the static IP.
Could it cause problems if one of the two nodes of a station is always disconnected?
Or is it safer to configure two different client stations and to launch either of them from the notebook depending on the context?
Posted : 13/03/2013 10:02 pm
Topic starter
Hi Armin,
I would say that declare 2 nodes for the client should not be an issue exept if this client is connected on both network at the same time (which should not be the case)
Posted : 13/03/2013 10:12 pm
Hi,
During multistation training I insist on the fact that it is forbidden to use Windows Station name when having more than one network board or if you only have one yet but another one later !
I confirm that you need to declare one node for each board and different ports for each.
IP addresses for the 2 boards have to be on 2 different subnets
Be careful with the links: subnet 1 = node 0 to other nodes 0 (if needed), subnet 2 = node 1 to other nodes 1 (if needed). Never cross the links 0 / 1
KR
Edouard
Posted : 14/03/2013 3:53 am
Yes, as said by Edouard you should take care on the Links between Nodes.
All Nodes 0 linked together and all Nodes 1 together too. Never cross them.
But, for the different ports, I am not sure it's mandatory. For safety better to do it. Then the IT has to open those 2 ports on the Networks.
Armin I guess you made a small mistake here:
"No DNS-server is available in the automation network."
I suppose you would say "No DHCP server..."
About your last question both solutions are OK. I would choose the second solution:
"Or is it safer to configure two different client stations and to launch either of them from the notebook depending on the context?"
Just using 2 icons launching PcVue with the shortcut -StationName xxx
Posted : 14/03/2013 8:14 am
Armin I guess you made a small mistake here:
"No DNS-server is available in the automation network."
I suppose you would say "No DHCP server..."
Actually, I really wanted to say "DNS-server" in order to emphasize that in the automation network we are obliged to identify the notebook client station by its IP-address. But in fact, I did not take into account that there are alternative ways to perform address lookup, such as the lmhosts file that was mentioned by Francois.
About your last question both solutions are OK. I would choose the second solution:
"Or is it safer to configure two different client stations and to launch either of them from the notebook depending on the context?"
Just using 2 icons launching PcVue with the shortcut -StationName xxx
Is there any technical constraint to consider or is your statement just a result of experience to not overcomplicate things? 😉
Posted : 14/03/2013 2:18 pm
Just a feeling...
Posted : 14/03/2013 2:51 pm
My guts feeling would be the same as Nico in order to not overcomplicated the LAN configuration.
2 user contexts 2 shortcuts on the desktop that make sense...
😉
Posted : 14/03/2013 11:11 pm