800xA Server redundancy issue
We have a server redundancy issue at one of our platform installation. I tried many steps to fix the issue but no luck.
800xA System Version: 5.1 Rev D
We did migration from workgroup to domain. We followed below procedure.
1. Deleted 800xAsystem from Primary AS+CS+RAS then joined system to domain
2. Deleted 800xAsystem from Secondary AS+CS+RAS then joined system to domain
3. User settings updated to domain users
4. All services running in local 800xAService configured to domain 800xAService account
5. Configured Preferred DNS and Alternate DNS for both computers all NIC’s
6. RNRP showing all computers correctly
7. Full back up Restored in primary AS+CS+RAS server
8. Connected secondary AS+CS+RAS to the primary through configuration wizard of secondary
9. 800xASystem was up and running fine all services in primary and secondary are in service state
10. Restarted the secondary server but the services related to secondary never came to service state(only aspect directory and FSD came to service state)
11. No idea what was going on.
Note that the domain controller is running on another platform. We have issue on unmanned platform there is only one pair of redundant servers to control the process(same domain).
I have tried several checks
1. Reapplied the user settings in both computers - no luck
2. Tried to delete the system from secondary then connect again – no luck
3. Checked the ping and RNRP – working fine
4. Switch of windows firewall – No luck
5. Disable Mcafee- no luck
6. Deleted system from secondary server, reinstalled 800xABase,CLS, connected secondary server again – no luck
7. Remove the secondary server through configuration wizard of primary, added redundant server again – no luck(now aspect directory and FSD of secondary server is down)
Please go through the attachment for more information.
I believe you should ask regional ABB to open a support case for you.
I can only provide hints here.
- Some computers on the "Island" (area 0) are missing their "Register this connection in DNS" setting (set on each NIC). Notice the missing "h," left of the name for those machines. All should display "h,name".
- Having DCs on a remote (routed) area may require you to manually add them to the hosts file of every domain member on the "island" (unless they already are inserted there by RNRP)
As per snap GRVPRIASCS800RA and GRVSECASCS800RA are in the network area 0
(172.16.0.0/172.17.0.0 with subnet/22 means u can reach network from 172.16.0.1 to 172.16.3.254 same for secondary)
Your domain in the network area 1 means 172.16.4.0 so are u using any router/gateway to configure the same?
Also check the network settings for all cleint server network should be DNS enabled and WINS keep at default and refresh all RNRP nodes (you should able to see the Host (h) registered in host files)
Check the network settings in the configuration wizard for the primary ASCS (GRVPRIASCS800RA) it should be 172.16.0.0 and 172.17.0.0 with subnet 255.255.252.0