Aspect server in read only mode
We had a power failure and all our aspect servers (3 Nos) got restarted.
After restart, the three aspect servers came up and aspect directory service in service structure is in "Service" but we have following issues..
1) None of them is master ( We do not see "x" on any AD)
2) I cant add / modify anything as I get the message that system is in "Read-Only" mode.
What could be the issue?
Voted best answer
Recovering from Read-only Mode
The solution is to run a NewSession command on the Aspect Directory service provider of the only remaining aspect server node.
Locate the Service Provider object in the Service Structure (Service Structure >
Services > Aspect Directory > Basic > AspectDirectory_Basic_NodeName).
Open the Service Provider Definition aspect and select NewSession in the
Command drop-down menu and click Run. See Figure177. This will change the
node to run as a single Aspect Server node.
If the previous lost redundant Aspect Servers would recover and start up again, their Aspect Directory Service Provider must then be forced to resynchronize
(Cold Reset) to join the new single Aspect Server again.
To Cold Reset, run the following commands (in sequence): Suspend, Cold Reset
Readonly mode occur in 2oo3 configurations when an aspect directory service provider is "singled out" (unable to reach any of its other two peers).
It's very hard to tell what is wrong with the information you have made available; first - check that network communication between the aspect servers are OK. E.g. by using the RNRP Monitor and "ping".
Then check that system resources are nominal (CPU, memory, handles, etc) in all servers - not too seldom some component, included in System 800xA or not malfunction and allocates all available resources, e.g. network sockets (which contributes to a process' Handle count).
An incorrectly configured firewall can cause loss of connection.
The System 800xA communication layer "CSLib" may generate events in the Windows Event Log if networking resources are depleted or error codes are returned from the Windows networking APIs.
Any further investigation would be very complex and more or less require expert skills in System 800xA and/or a remote connection to an ABB support center.
With only layman skills available I would attempt to restart the aspect servers, possibly even by first stopping all aspect servers and then startup one of them and let it go into complete service state before continuing with the next.
To go deeper; I would like to startup a regular support case and work it through the normal channels. You are most welcome to contact your regional ABB support center and share this information with them.