Finally, let's explore the newly added cluster member and verify that everything is configured and operational.
First, let's take a look at the cluster using the hwmgr(8) command.
# /sbin/hwmgr -view cluster Member ID State Member HostName --------- ----- --------------- 1 UP molari.dec.com 2 UP sheridan.dec.com (localhost)
Now let's see what file systems are mounted. As we can see, the new cluster member's boot_partition is mounted.
# mount cluster_root#root on / type advfs (rw) root2_domain#root on /cluster/members/member2/boot_partition type advfs (rw) cluster_var#var on /var type advfs (rw) root1_domain#root on /cluster/members/member1/boot_partition type advfs (rw) cluster_usr#usr on /usr type advfs (rw) /proc on /proc type procfs (rw)
Finally, let's check the cluster configuration and see what it looks like. To examine the cluster configuration, we use the clu_check_config(8) command, which checks the majority of the TruCluster Server's individual subsystems. We have trimmed the output to show only member2's information.
# /usr/sbin/clu_check_config Starting Cluster Configuration Check... ***************** Log Start ***************** Sun Apr 21 00:59:06 PDT 2002 ***** ***** Output from running clu_get_info -full ***** Cluster information for cluster babylon5 Number of members configured in this cluster = 2 memberid for this member = 1 Cluster incarnation = 0x15512 Cluster expected votes = 3 Current votes = 3 Votes required for quorum = 2 Quorum disk = dsk5h Quorum disk votes = 1 Information on each cluster member ... Cluster memberid = 2 Hostname = sheridan.dec.com Cluster interconnect IP name = sheridan-ics0 Cluster interconnect IP address = 10.0.0.2 Member state = UP Member base O/S version = Compaq Tru64 UNIX V5.1A (Rev. 1885) Member cluster version = TruCluster Server V5.1A (Rev. 1312) Member running version = INSTALLED Member name = sheridan Member votes = 1 csid = 0x20002 ***** ***** Output from running cfsmgr –v ***** ... Domain or filesystem name = root2_domain#root Mounted On = /cluster/members/member2/boot_partition Server Name = sheridan Server Status : OK ***** ***** Output from running cluamgr -s all ***** ... ***** Running cluamgr on member sheridan-ics0 Status of Cluster Alias: babylon5.dec.com netmask: 0 aliasid: 1 flags: 7<ENABLED,DEFAULT,IP_V4> connections rcvd from net: 16 connections forwarded: 4 connections rcvd within cluster: 34 data packets received from network: 1050
data packets forwarded within cluster: 325 datagrams received from network: 884 datagrams forwarded within cluster: 878 datagrams received within cluster: 30 fragments received from network: 0 fragments forwarded within cluster: 0 fragments received within cluster: 0 Member Attributes: memberid: 1, selw=3, selp=1, rpri=1 flags=11<JOINED,ENABLED> memberid: 2, selw=3, selp=1, rpri=1 flags=11<JOINED,ENABLED> ***** ***** Checking daemons on members ***** ***** ... ***** Checking member sheridan-ics0 daemons aliasd is RUNNING aliasd_niff is RUNNING /sbin/kloadsrv is RUNNING /usr/sbin/evmd is RUNNING /usr/sbin/niffd is RUNNING /usr/sbin/portmap is RUNNING /usr/sbin/caad is RUNNING /usr/sbin/clu_wall is RUNNING /usr/sbin/xntpd is RUNNING /usr/sbin/gated is RUNNING /usr/sbin/clu_mibs is RUNNING /usr/sbin/rdginit is RUNNING /usr/sbin/snmpd is RUNNING /usr/sbin/syslogd is RUNNING /usr/sbin/binlogd is RUNNING /usr/sbin/mountd is RUNNING /usr/sbin/nfsd is RUNNING /usr/sbin/smsd is RUNNING /usr/sbin/clu_wall is RUNNING /usr/sbin/xntpd is RUNNING /usr/sbin/gated is RUNNING /usr/sbin/clu_mibs is RUNNING /usr/sbin/rdginit is RUNNING /usr/sbin/snmpd is RUNNING /usr/sbin/syslogd is RUNNING /usr/sbin/binlogd is RUNNING /usr/sbin/mountd is RUNNING /usr/sbin/nfsd is RUNNING /usr/sbin/smsd is RUNNING ***** ***** Checking time synchronization between members ***** ***** molari-ics0: delay:0.000976 offset:0.000488 Sun Apr 21 00:59:10 2002 sheridan-ics0: delay:0.000976 offset:-0.000093 Sun Apr 21 00:59:10 2002 check_cdsl_config : Checking installed CDSLs check_cdsl_config : Successfully verified CDSLs configuration
As we can see from the clu_check_config output, this cluster looks like it is indeed configured and operational.