From: Timo Aaltonen (tjaalton@cc.hut.fi)
Date: Thu Jun 05 2003 - 09:02:08 EDT
thanks goes to... me!
<blushed> I checked the jumpers on the MC, and it was set for standard
hub.. Now it is set for virtual hub 0, and everything is a bliss..
On Thu, 5 Jun 2003, Timo Aaltonen wrote:
>
> Hi!
>
> I'm not able to boot a newly created single-member TC 5.1B+pk2:
>
> .
> .
> drd configured 0
> kch: configured
> dlm: configured
> Starting CFS daemons
> Registering CFS Services
> Initializing CFSREC ICS Service
> Registering CFSMSFS remote syscall interface
> Registering CMS Services
> CNX QDISK: Adding 1 quorum disk vote toward formation.
>
> and there it hangs. No disk access, nothing.
>
> The configuration:
>
> -DS20E 2*667
> KGPSA-CA HBA, firmware 3.81A4
> memory channel
>
> -RA8000
> HSG80, v8.6-13
>
> 8-port FC switch (8-EL?)
>
> I googled and found out that people had similar problems when adding
> members to a cluster (issues with MC). But this is different, yes? The
> other member is still running ASE 1.6, so the first member is fully
> isolated from it (MC cable not connected, 2nd member not on the fabric
> etc).
>
> The fabric has another cluster (TC 5.1A+pk4), but access paths are set for
> the units, so the clusters can't see each other..
>
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:21 EDT