800xA 5.1 AC800M Faceplate issue
Hi,
In one of site we have AC800M and AC400 connectivity servers and Aspect Servers(Combined with Domain). All these servers are redundant.
Recently AC400 connectivity server restarted due to some server issue. As per customer complaint post this incident 2 of operator station started AC800 related tags faceplate issue but in remaining OS everything works fine.
In these 2 particular OS AC800M tags dynamic values are updating correctly in graphics but when customer opens faceplates those shows greyed.
Tried below general solutions.
1. Restarted the both the OS and tried with different log ins.
2. Restarted the AC800M connectivity servers one by one.
With the above two options doesn't solved issue.
There is no affinity configuration defined.
System configuration
1. Aspect and Domain combined Redundant servers.
2. 4 CS's (2 for AC800M and 2 For AC400)
3. IMS
4. AO Server
5. 8 OS
Pls let me know the solution.
Thanks
In one of site we have AC800M and AC400 connectivity servers and Aspect Servers(Combined with Domain). All these servers are redundant.
Recently AC400 connectivity server restarted due to some server issue. As per customer complaint post this incident 2 of operator station started AC800 related tags faceplate issue but in remaining OS everything works fine.
In these 2 particular OS AC800M tags dynamic values are updating correctly in graphics but when customer opens faceplates those shows greyed.
Tried below general solutions.
1. Restarted the both the OS and tried with different log ins.
2. Restarted the AC800M connectivity servers one by one.
With the above two options doesn't solved issue.
There is no affinity configuration defined.
System configuration
1. Aspect and Domain combined Redundant servers.
2. 4 CS's (2 for AC800M and 2 For AC400)
3. IMS
4. AO Server
5. 8 OS
Pls let me know the solution.
Thanks
Answers
Hi,
Can you give the windows version also?
Can you give the windows version also?
Problem with faceplate only ?
"Affinity is a means to ensure a predictable system configuration. To achieve predictable load balancing, affinity must be set up correctly. This section provides a brief overview of the affinity concept, guidelines for planning affinity, and instructions for configuring affinity in the system. Configuring affinity is optional; however, if affinity is not configured, clients will randomly select providers for their services, which may lead to unpredictable performance."
Possible cause: Since affinity is not defined the affected Operator stations are trying to select 400 connectivity server as the service provider to get data for the AC800M tags.
Try to configure affinity and check - it might solve the issue.
Possible cause: Since affinity is not defined the affected Operator stations are trying to select 400 connectivity server as the service provider to get data for the AC800M tags.
Try to configure affinity and check - it might solve the issue.
Source: 3BUA000156-510 C page 40 - Affinity
Hi,
change the service provider in affected two operator stations. By this we can check, which connectivity server is healthy.
select service connection viewer in operator station- view- edit. change the service provider (connectivity server).
if currently Operator station is using server 1 as service provider, change it to server 2 then check faceplate status.
if that didn’t work,same process you can try with aspect servers services.
change the service provider in affected two operator stations. By this we can check, which connectivity server is healthy.
select service connection viewer in operator station- view- edit. change the service provider (connectivity server).
if currently Operator station is using server 1 as service provider, change it to server 2 then check faceplate status.
if that didn’t work,same process you can try with aspect servers services.
graphics showing correctly but greyed out on faceplates sounds like a Security Definition. this is what it does.
it almost seems like when the server rebooted it lost some security privelege after polcicies were applied.
check your service accounts and do a search for all the security definitions in the system
regards
it almost seems like when the server rebooted it lost some security privelege after polcicies were applied.
check your service accounts and do a search for all the security definitions in the system
regards
Add new comment