Rick,
> I followed Jim Dunham's AVS & ZFS seamless guide on OpenSolaris
> 2008.11,
> and I'm running into a problem. Actually, I ran into a few problems,
> but this is where I'm really stuck :)
>
> Both nodes /var/adm/ds.log show the same errors for each disk:
> Jan 19 15:37:08 librdc: SNDR: Could not open file
> sysvoltwo:/dev/rdsk/c4d0s0 on remote node
> Jan 19 15:37:09 sndr: SNDR: Could not open file
> sysvoltwo:/dev/rdsk/c5d0s0 on remote node
SNDR is a client / server replication model, and thus all of AVS must
be running on both nodes involved in replication. This can be verified
by running "dscfgadm -i", and assuring there are no errors. If there
are errors, "dscfgsdm -d" (disable), following be "dscfgadm -
e" (enable), should resolve all errors. Check "dscfgadm -i", one more
time.
> I ran rpcinfo -p on each node and they're identical:
From rpcinfo(1M), the following command syntax is covered in the AVS
troubleshooting guide (819-6151-10)
# rpcinfo -T tcp node1 100143
rpcinfo -T transport host prognum [versnum]
SNDR's program number is 100143
> rpcinfo -p sysvoltwo
> program vers proto port service
> 100000 4 tcp 111 rpcbind
> 100000 3 tcp 111 rpcbind
> 100000 2 tcp 111 rpcbind
> 100000 4 udp 111 rpcbind
> 100000 3 udp 111 rpcbind
> 100000 2 udp 111 rpcbind
> 100229 1 tcp 62457 metad
> 100229 2 tcp 62457 metad
> 100143 5 tcp 121
> 100143 6 tcp 121
> 100143 7 tcp 121
>
> Originally, I couldn't connect with rpcinfo at all and then I was
> missing port 121 on one node - but I've fixed those services and I
> turned off the 'local only' setting for the rpc/bind service.
I am concerned about the above statement. There is never a need for a
system admin to use rpcinfo on behalf of AVS (SNDR). I am therefore
concerned have made incompatible changes.
> So this is where I'm stuck. I'm a Solaris newbie, and I'm finding
> it a
> little difficult because things like the AVS Troubleshooting guide
> just
> give commands to run - but I don't know what output I'm looking for.
The encapsulation of AVS startup and shutdown into 'dscfgadm', is an
improvement over prior versions. If 'dscfgadm -i' does not come back
without errors, one can run 'dscfgadm -i -x', to get a look inside the
script as to what operations are failing.
> The above output looks fine to me, but am I missing something else?
There are two places, one either the SNDR primary or SNDR secondary
node where error messages are logged on behalf of AVS. They are /var/
adm/messages, and /var/svc/log/*nws_*
> I feel like I'm just missing one little piece (I've had to put a lot
> more together than I thought), and it would be wonderful to have this
> working.
>
> Thanks,
> Rick
>
> _______________________________________________
> storage-discuss mailing list
> [email protected]
> http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Jim Dunham
Engineering Manager
Storage Platform Software Group
Sun Microsystems, Inc.
work: 781-442-4042, x24042
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
