TruCluster
Showing results for 
Search instead for 
Do you mean 

Waiting for cluster boot disk to become registered

Occasional Contributor

Waiting for cluster boot disk to become registered

I am building a new cluster using DS-15s and EMC Clariion LUNs. I can see the LUNs in the console and have reachability. I can build the cluster as well as mount the cluster and member boot disks however when it comes time to boot the disks I get the following error "Waiting for cluster boot disk to become registered"

I have checked the WWIDs and the major/minor numbers to ensure they match and they do. I tried rebuilding the boot disk with clu_bdmgr and this still has not cleared my error.

Any Ideas?? This is all new hardware and new LUNs....
5 REPLIES
Honored Contributor

Re: Waiting for cluster boot disk to become registered

is the clusternode the same as the node on wich you created the cluster?

how many other hosts have access to these lun's at the time you boot the first cluster node?

Do you have multiple paths to the storage system?
if so did you use wwidmgr to make the references to the bootdevice fixed?
wwidmgr -clear all
init
wwidmgr -show wwid
Wwidmgr â quickset â udid

Did you set the console variable 'boot_osflags' to 'A'?
Advisor

Re: Waiting for cluster boot disk to become registered

Hello Mandy !

TruCluster likes to do persistant reservations with then SCSI devices.
And the devices need to be configured for it. As far as I remember
you also need to add entries for your EMC-Clarion to the
/etc/ddr.dbase File and run /sbin/ddr_config
of course that is best done before you do the clu_create.

You should ask your storage vendor for how the details of the
DGC entry in ddr.dbase look like. (about 20 lines with Attribute definitions)

regards,
--Uwe.
Occasional Contributor

Re: Waiting for cluster boot disk to become registered

Thank-you for the fast reply.

I have quickset the LUNs and set the bootosflags already. I have also added to the ddr.dbase for access.

It will be a 2 node cluster so however one is not added yet. The node that I am building the cluster on is run from a local drive and when booted can see all LUNs and can even mount the LUNs. All files look like it should run.

Is this possibly a setting on the EMC that allows access to mount but not boot?? This does not quite make sense either because it does boot but only up to a point.. Here are the last couple of lines in the boot process before it hangs:

Starting CFS daemons
Registering CFS services
Initializing CFSREC ICS Service
Registering CFSMSFS Remote Syscall interface
Registering CMS Services
TNC kproc_creator_daemon Initialized and Ready
Waiting for cluster boot disk to become registered
(repeat last line until computer is rebooted)

Any other ideas??
Advisor

Re: Waiting for cluster boot disk to become registered

Hello Mandy,

yes I recall that you need to set some flags on the EMC Storage side
for the presented LUNs to work correctly.
I digged through some old documentations and found some notes and
think these are still vaild or at least a good point for you to start
investigation on the Storage side.
the first Note...
"
V5.x: 255 LUNs/Symmetrix Fibre director port (LUNs 000-0FE valid) on Symmetrix 8000 Series,
requires OVMS director bit setting (minimum 5265.48.30 or 5566.26.19),
LUN 000 must be mapped to gatekeeper device, the LUN 000 array controller device will not
be usable by the Tru64 host.
"

and the second...this mentions the certain flag for the LUNs.
"
TruCluster V5.x Persistent Reservation support requires minimum 5567.53.30, Symm "PER" Volume flag,
minimum V5.1 Patch Kit-0003 (BL17), and "ubyte[0] = 8" in /etc/ddr.dbase EMC entry.
Configurations that cannot support Persistent Reservation must set "ubyte[0] = 25"
to enable alternate barrier patch and direct access devices.
"


regards
--Uwe.
Occasional Visitor

Re: Waiting for cluster boot disk to become registered

These are really good ideas for implementation.
//Add this to "OnDomLoad" event