Anonymous_User Absent Member.
Absent Member.
1578 views

Macs and Clustering

Anyone have any experience with Netware clusters and Macintosh computers?
We're setting up a new 6.5 cluster and are trying to figure out if there
is a way to keep our Mac users from having to relogin when a volume is
migrated or fails over.

We are planning to use SMB or NFS instead of AFP. It seems that once a
volume fails over and is transferred back the connection is sometimes
retained when using SMB. Anyone seen this before?

Thanks.
Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Macs and Clustering

Lots of folks here have this set up and though I am wary of speaking for others,
I think many of them would recommend sticking with AFP (you'll have fewer issues
with filenames and the like).

The trick to keeping a connection from a Mac to a cluster volume is having at
least (IIRC) OS X 10.3, and ensuring the volume has the same Mac name regardless
of which node it is mounted on. The latter part is accomplished via the
sys:\etc\afpvol.cfg file which determines how volumes are renamed for Macs (see
the docs for the details).

Here on node1, the afpvol.cfg file looks like:

NODE1.VOL1 "Volume1"
NODE1.VOL2 "Volume2"

On node2 afpvol.cfg looks like:

NODE2.VOL1 "Volume1"
NODE2.VOL2 "Volume2"

This ensures that whether VOL1 is mounted on node1 or node2 that it always
appears as "Volume1" to the Macs. Having this consistent naming scheme is
required for the Macs to maintain a connection to the volume during failovers
and migrations.

ajs

roger.keast@us-resources.com wrote:
> Anyone have any experience with Netware clusters and Macintosh computers?
> We're setting up a new 6.5 cluster and are trying to figure out if there
> is a way to keep our Mac users from having to relogin when a volume is
> migrated or fails over.
>
> We are planning to use SMB or NFS instead of AFP. It seems that once a
> volume fails over and is transferred back the connection is sometimes
> retained when using SMB. Anyone seen this before?
>
> Thanks.



--
Tony Skalski
Systems Administrator
ajs.NOSPAM@stolaf.edu
-------------------------------------------------------
St. Olaf College 1510 St. Olaf Avenue
Information and Northfield, MN
Instructional Technologies 55057-1097
=======================================================
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Macs and Clustering

AFPTCP in 6.5 supports the Volume auto-reconnect feature of AFP. You'll need
10.3+ on the client end and then your users won't notice when the resource
moves.

Don't know if SMB supports this or not, but there are a host of known issues
in Apple's SMB support that make it a less desirable solution.

best,
jeff


<roger.keast@us-resources.com> wrote in message
news:o0nRe.2213$xP3.772@prv-forum2.provo.novell.com...
> Anyone have any experience with Netware clusters and Macintosh computers?
> We're setting up a new 6.5 cluster and are trying to figure out if there
> is a way to keep our Mac users from having to relogin when a volume is
> migrated or fails over.
>
> We are planning to use SMB or NFS instead of AFP. It seems that once a
> volume fails over and is transferred back the connection is sometimes
> retained when using SMB. Anyone seen this before?
>
> Thanks.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Macs and Clustering

> there are a host of known
> issues in Apple's SMB support that make it a less desirable solution.


Agree, AFPTCP is the better solution.

--
Timothy Leerhoff
Novell Support Forum Volunteer Sysop

The future comes slowly, the present flies and the past stands still
forever
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.