Cluster fails after solaris server is brought online after hardware replacement
We replaced one of our solaris servers (swapped the hard drives into the new server) after a hardware failure. When the server came back up, all the applications we have on the servers in the cluster...
To re-introduce a server to the cluster steps are:
- Install VCS and agents
- Copy following files from existing node:
/etc/llthosts /etc/gabtab /etc/llttab /etc/vx/.uuids/clusuuid (and /etc/vxfen* if you use I/O fencing)
- Create /etc/VRTSvcs/conf/sysname containing hostname of node
- Edit /etc/llttab so that set-node is set to either /etc/VRTSvcs/conf/sysname or the node name
- Start llt and gab on new node and check "lltstat -nvv" shows all heartbeats are connected and "gabconfig -a" shows port a membership
- Run "hastart" - this should do a remote build and create main.cf and types.cf files in /etc/VRTSvcs/conf/config
Mike
- Install VCS and agents
If you have disconnected heartbeats so that lltnode ids 0-6 are showing down and only lltnode id 7 (itself) is showing as UP, then this is why GAB is not seeding and hence the "port a" messages.
Mike
