With the Sun Leadville drive, there is still a way to create persistent mapping
of tape devices
Take a look at:
http://docs.sun.com/source/819-0139/ch_8_persist_binding.html#pgfId-999553
The config file is /dev/devlink.tab
For example, here is ours:
# Fields can be blank; seperated by single tab characters,
# Spaces are significant, and are considered part of a field. IN GENERAL THIS
# MEANS THERE SHOULD BE NO SPACE CHARACTERS IN THIS FILE!
# All fields must be present (even if blank)
#
#
# devfs-spec Dev-Namespec Extra-Link
#
type=ddi_pseudo;name=SUNW,rtvc;minor=ctl rtvc\M0
type=ddi_pseudo;name=SUNW,rtvc \M0
type=ddi_byte:tape;addr=w5005076300616bbc,0; rmt/0\M0
type=ddi_byte:tape;addr=w500507631360b0c2,0; rmt/1\M0
type=ddi_byte:tape;addr=w5005076300616b8c,0; rmt/2\M0
type=ddi_byte:tape;addr=w500507630061dbbd,0; rmt/3\M0
type=ddi_byte:tape;addr=w5005076313604685,0; rmt/4\M0
type=ddi_byte:tape;addr=w5005076313604409,0; rmt/5\M0
#begin - added by LGTOnode - do not EDIT
type=ddi_pseudo;name=op optical\N0
#end - added by LGTOnode - do not EDIT
----
Matthew Huff | One Manhattanville Rd
OTA Management LLC | Purchase, NY 10577
www.otaotr.com | Phone: 914-460-4039
aim: matthewbhuff | Fax: 914-460-4139
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Teresa Biehler
Sent: Tuesday, June 17, 2008 12:50 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Sol10, Emulex LP1002 and Sc10K drive ordering
We've got one NW server and a storage node - both on Solaris 10. The
two systems share a sc10K with 10 drives. Several of the drives are
shared with DDS. Since our current storage node's server hardware is
going end of life, we're replacing it with a new server.
So, we've got the new storage node installed with Solaris 10 update
5/08. The HBAs are Emulex LP11002 with the latest EMC supported
firmware using the Sun Emulex drivers.
The SNC connected to the shared drives should be presenting the drives
as 0cbn, 1cbn, 2cbn, 3cbn. This is the order the old storage node and
the NW server see them in. The new storage node, however, sees the
drives as 3cbn, 2cbn, 1cbn, 0cbn.
Has anyone ever seen something like this? My gut says that as long as
the addressing is persistent, the order doesn't matter. My gut also
says that an unexplained drive ordering may cause problems - like the
addressing unexpectedly changing to be 0cbn, 1cbn, 2cbn, 3cbn. Does
anyone have any thoughts about what is happening?
Thanks.
Teresa
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|