I have 2 servers in a redundant arrangement.
Each server has 2 Ethernet cards. They have static ip addresses in different subnets:
Server 1 NIC A - 10.150.12.21
Server 1 NIC B - 10.150.13.21
Server 2 NIC A - 10.150.12.20
Server 2 NIC B - 10.150.13.20
Also, I have 3 clients (Remote UI).
All of them configured to use redundant servers over redundant network connections:
"config" file looks like
data = "server1-1,server1-2$server2-1,server2-2"
data = "server1-1,server1-2$server2-1,server2-2"
"hosts" file looks like:
10.150.12.21 server1 server1-1
10.150.13.21 server1-2
10.150.12.20 server2 server2-1
10.150.13.20 server2-2
The first 2 clients actually have 2 ethernet cards and are connected to the same subnets as servers are.
client 1 NIC A - 10.150.12.xxx
client 1 NIC B - 10.150.13.xxx
client 2 NIC A - 10.150.12.xxx
client 2 NIC B - 10.150.13.xxx
The third client is actually located on the other side of town, has only one ethernet card, different ip address subnet (10.160.xxx.xxx) and connects to servers via the enterprise network via some gateways and routers. I've checked that I can ping all servers ip addresses OK.
Now here's the issue...
I start testing with both servers up and running, server 2 is master, then I start all three clients. They all connect OK and I can operate my devices with no problems.
Then I physically unplug ethernet cable from server 2 NIC A (10.150.12.20).
Clients 1 & 2 continue to work fine, they seem to pick up another connection straight away. BUT! Client 3 freezes for quite some time. I can't open any dialogs. If any dialog was open, I can't close it. Then about 30-40 seconds later, the log viewer shows a few hundred connection loss messages, then it happens a couple more times and eventually after about a minute and a half the client seems to re-connect and un-freezes. I can again open popups and control devices.
Judging by a quick glance at log viewer it seems to me that clients 1 & 2 are always connected to servers on BOTH networks, therefore when I drop the first network, they stay operational straight away.
It also seems like client 3 connects to only one network at a time. So when I disconnect it, it takes some time for it to realise this and re-connect on the second network.
The "config" and "hosts" file are exactly the same on all 3 clients. The difference is only the fact that clients 1 & 2 have 2 NIC's and client 3 - only one NIC and goes via some routers.
Anyone experienced similar issues before? Is client always supposed to have two NIC's to use redundant network connections?
Remote UI problem with redundant servers with redundant connections
- n_lev
- Posts:73
- Joined: Tue May 28, 2013 2:24 am
Remote UI problem with redundant servers with redundant connections
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Remote UI problem with redundant servers with redundant connections
Hello,
the connections between the servers and clients are established all the time if the network is not broken. Establishing the connections is done during startup of the WinCC OA process.
If you want to use redundant network connections between the server and clients you need two seperate networks.
The client 3 in your configuration has only one connection to every server. Therefore the configuration of a redundant network does not make sense for this client.
When the network is disconnected it may take some time unless the TCP-connection (basic function of the operating system) detects that the connection is broken. This information is then forwarded to the process using the network socket. This time may vary depending on the fact where the network is broken and how complex the network is.
The other clients have two connections therefore they can still communicate with the (active) server2, when the first network connection is interrupted.
If you are loosing the connection to the active server the UI cannot be operated. In your case also a switch of the active/passive state may have occured after you have disconnected one network card at the active server. Please check when the state has changed.
Then the UI operation is possible again when the UI has detected that one network connection lost and the active/passive state has changed.
Best Regards
Leopold Knipp
Senior Support Specialist
the connections between the servers and clients are established all the time if the network is not broken. Establishing the connections is done during startup of the WinCC OA process.
If you want to use redundant network connections between the server and clients you need two seperate networks.
The client 3 in your configuration has only one connection to every server. Therefore the configuration of a redundant network does not make sense for this client.
When the network is disconnected it may take some time unless the TCP-connection (basic function of the operating system) detects that the connection is broken. This information is then forwarded to the process using the network socket. This time may vary depending on the fact where the network is broken and how complex the network is.
The other clients have two connections therefore they can still communicate with the (active) server2, when the first network connection is interrupted.
If you are loosing the connection to the active server the UI cannot be operated. In your case also a switch of the active/passive state may have occured after you have disconnected one network card at the active server. Please check when the state has changed.
Then the UI operation is possible again when the UI has detected that one network connection lost and the active/passive state has changed.
Best Regards
Leopold Knipp
Senior Support Specialist
- n_lev
- Posts:73
- Joined: Tue May 28, 2013 2:24 am
Re: Remote UI problem with redundant servers with redundant connections
Leopold Knipp wrote:
Therefore I think even the client with only one NIC should be able to use redundant network connection, no?
Leopold Knipp wrote:
I've analyzed a log of client 1 (two NIC's) and client 3 (1 NIC).
Here is a client 1 (two NIC's) log when it starts:
---------------------------------------------------------------------------
WCCILpmon (1), 2014.07.17 13:49:01.515, SYS, INFO, 24/pmon, Got START command from 127.0.0.1, starting the manager WCCOAui(7) at index 1
WCCILpmon (1), 2014.07.17 13:49:01.531, SYS, INFO, 1, Manager Start, C:\\Siemens\\Automation\\WinCC_OA\\3.11\\bin\\WCCOAui.exe -PROJ SHB_ELCS_Client -pmonIndex 1 -p vision/login.pnl
WCCOAui (0), 2014.07.17 13:49:02.796, SYS, INFO, 1, Manager Start, PROJ, SHB_ELCS_Client, V 3.11 - 3.11 SP1 platform Windows x86 linked at Apr 17 2013 19:15:19
WCCOAui (0), 2014.07.17 13:49:02.812, SYS, INFO, 3, Trying to connect to, (SYS: 0 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN-1:4897,WIN-MKGTLG38PJN-2:4897$WIN-5LC1C5HHGJ4-1:4897,WIN-5LC1C5HHGJ4-2:4897
WCCOAui (0), 2014.07.17 13:49:03.171, SYS, INFO, 4, Connected to, (SYS: 0 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (0), 2014.07.17 13:49:03.203, SYS, INFO, 4, Connected to, (SYS: 0 Data -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4 (10.150.12.20)
WCCOAui (0), 2014.07.17 13:49:06.859, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (0), 2014.07.17 13:49:06.906, REDU, INFO, 0, , Closing connection to passive data during initialization. This may terminate the manager., (SYS: 0 Data -num 0 CONN: 1)
WCCOAui (0), 2014.07.17 13:49:06.906, SYS, INFO, 181, Closing connection to (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (0), 2014.07.17 13:49:06.921, SYS, WARNING, 184, The time on WIN-5LC1C5HHGJ4 and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:06.968, REDU, INFO, 0, , Closing connection to redundant data during initialization, (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (8), 2014.07.17 13:49:06.968, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection reset by peer (10054)
WCCOAui (8), 2014.07.17 13:49:07.015, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (8), 2014.07.17 13:49:07.015, SYS, INFO, 3, Trying to connect to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4-1:4998,WIN-5LC1C5HHGJ4-2:4998
WCCOAui (8), 2014.07.17 13:49:07.203, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4 (10.150.12.20)
WCCOAui (8), 2014.07.17 13:49:11.515, SYS, WARNING, 184, The time on WIN-5LC1C5HHGJ4 and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:11.578, SYS, INFO, 102, Waiting for user names/passwords
WCCOAui (8), 2014.07.17 13:49:11.578, SYS, INFO, 103, User names/passwords initialized
WCCOAui (8), 2014.07.17 13:49:11.671, PARAM,WARNING, 3/ctrl, Library "sdSymbolDynamics.ctl" (defined in config) could not be found.
WCCOAui (8), 2014.07.17 13:49:12.593, SYS, INFO, 4, Connected to, (SYS: 1 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (8), 2014.07.17 13:49:12.625, SYS, INFO, 4, Connected to, (SYS: 1 Data -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4-2 (10.150.13.20)
WCCOAui (8), 2014.07.17 13:49:12.625, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (8), 2014.07.17 13:49:12.656, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4-2 (10.150.13.20)
WCCOAui (8), 2014.07.17 13:49:14.812, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:15.375, SYS, WARNING, 184, The time on WIN-5LC1C5HHGJ4 and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:17.234, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:18.375, SYS, WARNING, 184, The time on WIN-5LC1C5HHGJ4 and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:32.312, SYS, INFO, 4, Connected to, (SYS: 1 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN-2 (10.150.13.21)
WCCOAui (8), 2014.07.17 13:49:32.312, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 1) @ WIN-MKGTLG38PJN-2 (10.150.13.21)
WCCOAui (8), 2014.07.17 13:49:35.031, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:38.046, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
Here is the server log when client 1 connects:
WCCILdata (0), 2014.07.17 13:47:59.277, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 8 CONN: 2(R)) @ ABUTBTMC01 (::ffff:10.150.12.23)
WCCILdata (0), 2014.07.17 13:47:59.407, SYS, INFO, 0, , Manager (SYS: 1 Ui -num 8 CONN: 2(R)) initialised
WCCILevent (0), 2014.07.17 13:48:03.329, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 8 CONN: 2(R)) @ ABUTBTMC01 (::ffff:10.150.12.23)
WCCILdata (0), 2014.07.17 13:48:07.796, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 8 CONN: 2(R)) @ ABUTBTMC01 (::ffff:10.150.13.23)
WCCILevent (0), 2014.07.17 13:48:09.597, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 8 CONN: 2(R)) @ ABUTBTMC01 (::ffff:10.150.13.23)
---------------------------------------------------------------------------
If I understand this correctly (highlighted in green) this client establishes a total of 8 connections (data and event manager x 2 servers x 2 networks)
Now, here is client 3 (1 NIC) log when it starts:
---------------------------------------------------------------------------
WCCILpmon (1), 2014.07.17 12:36:57.847, SYS, INFO, 24/pmon, Got START command from 127.0.0.1, starting the manager WCCOAui(8) at index 1
WCCILpmon (1), 2014.07.17 12:36:57.847, SYS, INFO, 1, Manager Start, C:\\Siemens\\Automation\\WinCC_OA\\3.11\\bin\\WCCOAui.exe -PROJ SHB_ELCS_Client -pmonIndex 1 -p vision/login.pnl
WCCOAui (0), 2014.07.17 12:36:58.644, SYS, INFO, 1, Manager Start, PROJ, SHB_ELCS_Client, V 3.11 - 3.11 SP1 platform Windows x86 linked at Apr 17 2013 19:15:19
WCCOAui (0), 2014.07.17 12:36:58.659, SYS, INFO, 3, Trying to connect to, (SYS: 0 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN-1:4897,WIN-MKGTLG38PJN-2:4897$WIN-5LC1C5HHGJ4-1:4897,WIN-5LC1C5HHGJ4-2:4897
WCCOAui (0), 2014.07.17 12:36:58.815, SYS, INFO, 4, Connected to, (SYS: 0 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (0), 2014.07.17 12:36:58.831, SYS, INFO, 4, Connected to, (SYS: 0 Data -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4 (10.150.12.20)
WCCOAui (0), 2014.07.17 12:37:01.878, REDU, INFO, 0, , Closing connection to passive data during initialization. This may terminate the manager., (SYS: 0 Data -num 0 CONN: 1)
WCCOAui (0), 2014.07.17 12:37:01.878, SYS, INFO, 181, Closing connection to (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (7), 2014.07.17 12:37:01.909, REDU, INFO, 0, , Closing connection to redundant data during initialization, (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (7), 2014.07.17 12:37:01.909, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection reset by peer (10054)
WCCOAui (7), 2014.07.17 12:37:01.972, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (7), 2014.07.17 12:37:01.972, SYS, INFO, 3, Trying to connect to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4-1:4998,WIN-5LC1C5HHGJ4-2:4998
WCCOAui (7), 2014.07.17 12:37:02.065, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4 (10.150.12.20)
WCCOAui (7), 2014.07.17 12:37:07.737, SYS, INFO, 102, Waiting for user names/passwords
WCCOAui (7), 2014.07.17 12:37:07.737, SYS, INFO, 103, User names/passwords initialized
WCCOAui (7), 2014.07.17 12:37:07.831, PARAM,WARNING, 3/ctrl, Library "sdSymbolDynamics.ctl" (defined in config) could not be found.
WCCOAui (7), 2014.07.17 12:37:08.722, SYS, INFO, 4, Connected to, (SYS: 1 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (7), 2014.07.17 12:37:08.753, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
Here is the server log when client 3 connects:
WCCILdata (0), 2014.07.17 12:37:13.840, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 7 CONN: 2(R)) @ VUIS85 (::ffff:163.189.13.66)
WCCILdata (0), 2014.07.17 12:37:13.906, SYS, INFO, 0, , Manager (SYS: 1 Ui -num 7 CONN: 2(R)) initialised
WCCILevent (0), 2014.07.17 12:37:17.130, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 7 CONN: 2(R)) @ VUIS85 (::ffff:163.189.13.66)
---------------------------------------------------------------------------
I can clearly see that client 3 never establishes connections to data or event managers via the second network.
So this raises several questions:
1. Why doesn't client 3 want to establish secondary network connections? Yes, I've got 1 NIC on it, but I can still happily ping BOTH server IP addresses. Is that the client not sending connection requests? Or is it the server ignoring the second connection requests since they come from the same IP address?
2. What can I do to make client 3 connect to both server network addresses? What are my options?
A. Fix something in WinCC config files, windows hosts file or somewhere else to make client use both networks? (Would be the best option is it doesn't require any changes to client's PC's or corporate network infrustructure
B. Install second NIC into every client? (Do-able but hard)
C. Configure second IP address on the single NIC on every client ans set routers accordingly? (Do-able but hard)
D. Change regular client to Web-client? (Will have to change licences, etc.)
The biggest problem with doing any changes to client PC's is the fact that they do not belong to us, it is an existing infrastructure that the customer has and they run other apps on those PC's, so they don't want us to disturb them too much.
I hope this information helps, please, let me know your thoughts on this. Thank you very much for your help
Regards,
Nick Levchenko
That is not entirely true. I agree, client has only one NIC, that means that if that NIC fails, client is dead. But! That NIC is actually connected to a corporate network that has TWO separate paths through the city and reaches BOTH networks on the server. So if one NIC on the server dies, or a switch dies, I should still be able to communicate through the other server NIC.Hello,
the connections between the servers and clients are established all the time if the network is not broken. Establishing the connections is done during startup of the WinCC OA process.
If you want to use redundant network connections between the server and clients you need two seperate networks.
The client 3 in your configuration has only one connection to every server. Therefore the configuration of a redundant network does not make sense for this client.
Therefore I think even the client with only one NIC should be able to use redundant network connection, no?
Leopold Knipp wrote:
Just a note, I don't think servers switched over, I made sure the same server stayed active while the first network is down.When the network is disconnected it may take some time unless the TCP-connection (basic function of the operating system) detects that the connection is broken. This information is then forwarded to the process using the network socket. This time may vary depending on the fact where the network is broken and how complex the network is.
The other clients have two connections therefore they can still communicate with the (active) server2, when the first network connection is interrupted.
If you are loosing the connection to the active server the UI cannot be operated. In your case also a switch of the active/passive state may have occured after you have disconnected one network card at the active server. Please check when the state has changed.
Then the UI operation is possible again when the UI has detected that one network connection lost and the active/passive state has changed.
Best Regards
Leopold Knipp
Senior Support Specialist
I've analyzed a log of client 1 (two NIC's) and client 3 (1 NIC).
Here is a client 1 (two NIC's) log when it starts:
---------------------------------------------------------------------------
WCCILpmon (1), 2014.07.17 13:49:01.515, SYS, INFO, 24/pmon, Got START command from 127.0.0.1, starting the manager WCCOAui(7) at index 1
WCCILpmon (1), 2014.07.17 13:49:01.531, SYS, INFO, 1, Manager Start, C:\\Siemens\\Automation\\WinCC_OA\\3.11\\bin\\WCCOAui.exe -PROJ SHB_ELCS_Client -pmonIndex 1 -p vision/login.pnl
WCCOAui (0), 2014.07.17 13:49:02.796, SYS, INFO, 1, Manager Start, PROJ, SHB_ELCS_Client, V 3.11 - 3.11 SP1 platform Windows x86 linked at Apr 17 2013 19:15:19
WCCOAui (0), 2014.07.17 13:49:02.812, SYS, INFO, 3, Trying to connect to, (SYS: 0 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN-1:4897,WIN-MKGTLG38PJN-2:4897$WIN-5LC1C5HHGJ4-1:4897,WIN-5LC1C5HHGJ4-2:4897
WCCOAui (0), 2014.07.17 13:49:03.171, SYS, INFO, 4, Connected to, (SYS: 0 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (0), 2014.07.17 13:49:03.203, SYS, INFO, 4, Connected to, (SYS: 0 Data -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4 (10.150.12.20)
WCCOAui (0), 2014.07.17 13:49:06.859, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (0), 2014.07.17 13:49:06.906, REDU, INFO, 0, , Closing connection to passive data during initialization. This may terminate the manager., (SYS: 0 Data -num 0 CONN: 1)
WCCOAui (0), 2014.07.17 13:49:06.906, SYS, INFO, 181, Closing connection to (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (0), 2014.07.17 13:49:06.921, SYS, WARNING, 184, The time on WIN-5LC1C5HHGJ4 and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:06.968, REDU, INFO, 0, , Closing connection to redundant data during initialization, (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (8), 2014.07.17 13:49:06.968, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection reset by peer (10054)
WCCOAui (8), 2014.07.17 13:49:07.015, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (8), 2014.07.17 13:49:07.015, SYS, INFO, 3, Trying to connect to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4-1:4998,WIN-5LC1C5HHGJ4-2:4998
WCCOAui (8), 2014.07.17 13:49:07.203, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4 (10.150.12.20)
WCCOAui (8), 2014.07.17 13:49:11.515, SYS, WARNING, 184, The time on WIN-5LC1C5HHGJ4 and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:11.578, SYS, INFO, 102, Waiting for user names/passwords
WCCOAui (8), 2014.07.17 13:49:11.578, SYS, INFO, 103, User names/passwords initialized
WCCOAui (8), 2014.07.17 13:49:11.671, PARAM,WARNING, 3/ctrl, Library "sdSymbolDynamics.ctl" (defined in config) could not be found.
WCCOAui (8), 2014.07.17 13:49:12.593, SYS, INFO, 4, Connected to, (SYS: 1 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (8), 2014.07.17 13:49:12.625, SYS, INFO, 4, Connected to, (SYS: 1 Data -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4-2 (10.150.13.20)
WCCOAui (8), 2014.07.17 13:49:12.625, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (8), 2014.07.17 13:49:12.656, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4-2 (10.150.13.20)
WCCOAui (8), 2014.07.17 13:49:14.812, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:15.375, SYS, WARNING, 184, The time on WIN-5LC1C5HHGJ4 and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:17.234, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:18.375, SYS, WARNING, 184, The time on WIN-5LC1C5HHGJ4 and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:32.312, SYS, INFO, 4, Connected to, (SYS: 1 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN-2 (10.150.13.21)
WCCOAui (8), 2014.07.17 13:49:32.312, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 1) @ WIN-MKGTLG38PJN-2 (10.150.13.21)
WCCOAui (8), 2014.07.17 13:49:35.031, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
WCCOAui (8), 2014.07.17 13:49:38.046, SYS, WARNING, 184, The time on WIN-MKGTLG38PJN and ABUTBTMC01 differs approximately 67 sec. Please correct this., This is handled by time correction but other problems may occur.
Here is the server log when client 1 connects:
WCCILdata (0), 2014.07.17 13:47:59.277, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 8 CONN: 2(R)) @ ABUTBTMC01 (::ffff:10.150.12.23)
WCCILdata (0), 2014.07.17 13:47:59.407, SYS, INFO, 0, , Manager (SYS: 1 Ui -num 8 CONN: 2(R)) initialised
WCCILevent (0), 2014.07.17 13:48:03.329, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 8 CONN: 2(R)) @ ABUTBTMC01 (::ffff:10.150.12.23)
WCCILdata (0), 2014.07.17 13:48:07.796, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 8 CONN: 2(R)) @ ABUTBTMC01 (::ffff:10.150.13.23)
WCCILevent (0), 2014.07.17 13:48:09.597, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 8 CONN: 2(R)) @ ABUTBTMC01 (::ffff:10.150.13.23)
---------------------------------------------------------------------------
If I understand this correctly (highlighted in green) this client establishes a total of 8 connections (data and event manager x 2 servers x 2 networks)
Now, here is client 3 (1 NIC) log when it starts:
---------------------------------------------------------------------------
WCCILpmon (1), 2014.07.17 12:36:57.847, SYS, INFO, 24/pmon, Got START command from 127.0.0.1, starting the manager WCCOAui(8) at index 1
WCCILpmon (1), 2014.07.17 12:36:57.847, SYS, INFO, 1, Manager Start, C:\\Siemens\\Automation\\WinCC_OA\\3.11\\bin\\WCCOAui.exe -PROJ SHB_ELCS_Client -pmonIndex 1 -p vision/login.pnl
WCCOAui (0), 2014.07.17 12:36:58.644, SYS, INFO, 1, Manager Start, PROJ, SHB_ELCS_Client, V 3.11 - 3.11 SP1 platform Windows x86 linked at Apr 17 2013 19:15:19
WCCOAui (0), 2014.07.17 12:36:58.659, SYS, INFO, 3, Trying to connect to, (SYS: 0 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN-1:4897,WIN-MKGTLG38PJN-2:4897$WIN-5LC1C5HHGJ4-1:4897,WIN-5LC1C5HHGJ4-2:4897
WCCOAui (0), 2014.07.17 12:36:58.815, SYS, INFO, 4, Connected to, (SYS: 0 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (0), 2014.07.17 12:36:58.831, SYS, INFO, 4, Connected to, (SYS: 0 Data -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4 (10.150.12.20)
WCCOAui (0), 2014.07.17 12:37:01.878, REDU, INFO, 0, , Closing connection to passive data during initialization. This may terminate the manager., (SYS: 0 Data -num 0 CONN: 1)
WCCOAui (0), 2014.07.17 12:37:01.878, SYS, INFO, 181, Closing connection to (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (7), 2014.07.17 12:37:01.909, REDU, INFO, 0, , Closing connection to redundant data during initialization, (SYS: 1 Data -num 0 CONN: 1)
WCCOAui (7), 2014.07.17 12:37:01.909, SYS, WARNING, 39, Connection lost, MAN: (SYS: 1 Data -num 0 CONN: 1), Connection reset by peer (10054)
WCCOAui (7), 2014.07.17 12:37:01.972, SYS, INFO, 6, Initialization by Data Manager finished
WCCOAui (7), 2014.07.17 12:37:01.972, SYS, INFO, 3, Trying to connect to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4-1:4998,WIN-5LC1C5HHGJ4-2:4998
WCCOAui (7), 2014.07.17 12:37:02.065, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 2) @ WIN-5LC1C5HHGJ4 (10.150.12.20)
WCCOAui (7), 2014.07.17 12:37:07.737, SYS, INFO, 102, Waiting for user names/passwords
WCCOAui (7), 2014.07.17 12:37:07.737, SYS, INFO, 103, User names/passwords initialized
WCCOAui (7), 2014.07.17 12:37:07.831, PARAM,WARNING, 3/ctrl, Library "sdSymbolDynamics.ctl" (defined in config) could not be found.
WCCOAui (7), 2014.07.17 12:37:08.722, SYS, INFO, 4, Connected to, (SYS: 1 Data -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
WCCOAui (7), 2014.07.17 12:37:08.753, SYS, INFO, 4, Connected to, (SYS: 1 Event -num 0 CONN: 1) @ WIN-MKGTLG38PJN (10.150.12.21)
Here is the server log when client 3 connects:
WCCILdata (0), 2014.07.17 12:37:13.840, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 7 CONN: 2(R)) @ VUIS85 (::ffff:163.189.13.66)
WCCILdata (0), 2014.07.17 12:37:13.906, SYS, INFO, 0, , Manager (SYS: 1 Ui -num 7 CONN: 2(R)) initialised
WCCILevent (0), 2014.07.17 12:37:17.130, SYS, INFO, 4, Connected to, (SYS: 1 Ui -num 7 CONN: 2(R)) @ VUIS85 (::ffff:163.189.13.66)
---------------------------------------------------------------------------
I can clearly see that client 3 never establishes connections to data or event managers via the second network.
So this raises several questions:
1. Why doesn't client 3 want to establish secondary network connections? Yes, I've got 1 NIC on it, but I can still happily ping BOTH server IP addresses. Is that the client not sending connection requests? Or is it the server ignoring the second connection requests since they come from the same IP address?
2. What can I do to make client 3 connect to both server network addresses? What are my options?
A. Fix something in WinCC config files, windows hosts file or somewhere else to make client use both networks? (Would be the best option is it doesn't require any changes to client's PC's or corporate network infrustructure
B. Install second NIC into every client? (Do-able but hard)
C. Configure second IP address on the single NIC on every client ans set routers accordingly? (Do-able but hard)
D. Change regular client to Web-client? (Will have to change licences, etc.)
The biggest problem with doing any changes to client PC's is the fact that they do not belong to us, it is an existing infrastructure that the customer has and they run other apps on those PC's, so they don't want us to disturb them too much.
I hope this information helps, please, let me know your thoughts on this. Thank you very much for your help
Regards,
Nick Levchenko
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Remote UI problem with redundant servers with redundant connections
Hello,
when looking at the log output for client 3 you'll see that only one connection is established to every server. You will not see that a connection for the network interfaces with the prefix "-2" is made. At the other client log output you'll see that this connection is established too, which is the indication that redundant networks are used.
There is no difference for the connection handling if a Web-client or a normal installed UI is used. In all cases a UI-process is started which uses the same functionality for the connections to the servers.
If there is only one network connection at the client you'll not be able to use the full functionality of redundant network connections in WinCC OA.
In your configuration you have a single network connection between the UI and some network devices (router, switches, ...). These network devices than have redundant connections to the servers.
To allow a second connection in between this network for the same incoming IP-address you have to make some changes at the server configuration.
Therefore please define the following entries at the config-file for the servers:
[data]
singleSourceConnect = 1
[event]
singleSourceConnect = 1
Afterwards the server project at every server needs to be restarted to take effect of the changes.
Then you can this test again. During startup and the initialization of the UI you can check if all connections are established.
If still some problems occur please get in contact with the official WinCC OA support.
For a detailed analysis we would need the complete PVSS_II.log-file for both servers and all clients. Also it would be useful to have the config-file for the server- and client-projects.
If you need additional information please open a support request using the link below and attach the requested files.
http://support.automation.siemens.com
Best Regards
Leopold Knipp
Senior Support Specialist
when looking at the log output for client 3 you'll see that only one connection is established to every server. You will not see that a connection for the network interfaces with the prefix "-2" is made. At the other client log output you'll see that this connection is established too, which is the indication that redundant networks are used.
There is no difference for the connection handling if a Web-client or a normal installed UI is used. In all cases a UI-process is started which uses the same functionality for the connections to the servers.
If there is only one network connection at the client you'll not be able to use the full functionality of redundant network connections in WinCC OA.
In your configuration you have a single network connection between the UI and some network devices (router, switches, ...). These network devices than have redundant connections to the servers.
To allow a second connection in between this network for the same incoming IP-address you have to make some changes at the server configuration.
Therefore please define the following entries at the config-file for the servers:
[data]
singleSourceConnect = 1
[event]
singleSourceConnect = 1
Afterwards the server project at every server needs to be restarted to take effect of the changes.
Then you can this test again. During startup and the initialization of the UI you can check if all connections are established.
If still some problems occur please get in contact with the official WinCC OA support.
For a detailed analysis we would need the complete PVSS_II.log-file for both servers and all clients. Also it would be useful to have the config-file for the server- and client-projects.
If you need additional information please open a support request using the link below and attach the requested files.
http://support.automation.siemens.com
Best Regards
Leopold Knipp
Senior Support Specialist
- n_lev
- Posts:73
- Joined: Tue May 28, 2013 2:24 am
Re: Remote UI problem with redundant servers with redundant connections
Hi Leopold,
Thanks a lot for your help.
I got it working now.
The fix that you've proposed didn't work initially.
First, I put
into both servers, restarted them, then restarted the single NIC client and it still only connected to 1 network on each server
I then added
to the client's config file, restarted it and this time it connected to both networks on both servers.
Problem solved, I think!
Thanks again for your time and help
Thanks a lot for your help.
I got it working now.
The fix that you've proposed didn't work initially.
First, I put
Code: Select all
[data]
singleSourceConnect = 1
[event]
singleSourceConnect = 1
I then added
Code: Select all
[ui]
singleSourceConnect = 1Problem solved, I think!
Thanks again for your time and help