Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
Next time try doing a `cfgadm -al`. You'll probably see the tape device as unconfigured. do a `cfgadm -c unconfigure cX` (cX is the channel...it's the left hand collumn in `cfgamd -al` such as c6 or c5, etc...) and then a `cfgadm -c configure cX` That's worked for me in the past. You'll also need to make sure that your sg.conf file has the correct targets and luns defined in itwhen you do your `sg.build all -mt X -ml X` -- Mike Sponsler [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vines, Peter (psv2b) Sent: Friday, December 28, 2007 3:31 PM To: [EMAIL PROTECTED] Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. A solution that worked, and suggested by a Veritas-bu subscriber, was to manually add the tape drives to st.conf and reload the driver. This successfully generated the missing /dev/rmt entries and allowed me to proceed with the robot and drive configuration using tpconfig. Steps: Added entries to /kernel/drv/st.conf: name=st parent=fp target=0 lun=0 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=1 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=2 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=3 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=4 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=0 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=1 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=2 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=3 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=4 fc-port-wwn=500308c00189780b; Determine st driver Id and display details: modinfo | grep st ... modinfo -i 49 Id Loadaddr Size Info Rev Module Name 49 786e 132e4 33 1 st (SCSI tape Driver 1.221) Reloaded st driver: modunload -i 49 modinfo -i 49 can't get module information: Invalid argument devfsadm -i st tpconfig work. Backups now working fine to the new tape drives. From: Vines, Peter (psv2b) Sent: Monday, December 24, 2007 12:49 PM To: Vines, Peter (psv2b); psv2b; [EMAIL PROTECTED] Subject: RE: [Veritas-bu] New tape drives not appearing in /dev/rmt. Adding the entry to st.conf followed by a boot -r did NOT fix my problem. The missing /dev/rmt entries are still missing. I've opened another issue with SUN. The original six drvies in the L700 are still there and usable. The new four drives in the Scalar i2000 do not exist in /dev/rmt, yet are shown in cfgadm. -Original Message- From: [EMAIL PROTECTED] on behalf of Peter Vines Sent: Wed 12/12/2007 7:13 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. SUN's response is that my st.conf is missing: name=st parent=fp target=0; From looking at old files, this line was probably removed by mistake in 2005 during another drive configuration, and obviously is not needed for the existing L700 and 9840 drives which are working fine. Now to find time and get permission to boot the production server... On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnected configured unknown c8::500308c00189780a,0 med-changer connected configured unknown c8::500308c00189780a,1 tape connected configured unknown c8::500308c00189780a,2 tape connected configured unknown c9 fc-fabricconnected configured unknown c9::500308c00189780b,0 med-changer connected configured unknown c9::500308c00189780b,3 tape connected configured unknown c9::500308c00189780b,4 tape connected configured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt
[Veritas-bu] New tape drives not appearing in /dev/rmt.
You don't need to unconfigure first. Also, depending on your setup, you may not want to configure all devices on the adapter. I tend to be more granular and run cfgadm -c configure cX::WWPN where WWPN is the world wide number of the device you would like to configure. You also may be able to do this at the lun level (which would be cX::WWPN,LUN), but I've never tried to, nor do I have any real reason to. msponsler wrote: Next time try doing a `cfgadm -al`. You'll probably see the tape device as unconfigured. do a `cfgadm -c unconfigure cX` (cX is the channel...it's the left hand collumn in `cfgamd -al` such as c6 or c5, etc...) and then a `cfgadm -c configure cX` That's worked for me in the past. You'll also need to make sure that your sg.conf file has the correct targets and luns defined in itwhen you do your `sg.build all -mt X -ml X` -- Mike Sponsler Michael.Sponsler at ngc.com -Original Message- From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Vines, Peter (psv2b) Sent: Friday, December 28, 2007 3:31 PM To: mail=veritas-bu at mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. A solution that worked, and suggested by a Veritas-bu subscriber, was to manually add the tape drives to st.conf and reload the driver. This successfully generated the missing /dev/rmt entries and allowed me to proceed with the robot and drive configuration using tpconfig. Steps: Added entries to /kernel/drv/st.conf: name=st parent=fp target=0 lun=0 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=1 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=2 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=3 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=4 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=0 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=1 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=2 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=3 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=4 fc-port-wwn=500308c00189780b; Determine st driver Id and display details: modinfo | grep st ... modinfo -i 49 Id Loadaddr Size Info Rev Module Name 49 786e 132e4 33 1 st (SCSI tape Driver 1.221) Reloaded st driver: modunload -i 49 modinfo -i 49 can't get module information: Invalid argument devfsadm -i st tpconfig work. Backups now working fine to the new tape drives. From: Vines, Peter (psv2b) Sent: Monday, December 24, 2007 12:49 PM To: Vines, Peter (psv2b); psv2b; mail=veritas-bu at mailman.eng.auburn.edu Subject: RE: [Veritas-bu] New tape drives not appearing in /dev/rmt. Adding the entry to st.conf followed by a boot -r did NOT fix my problem. The missing /dev/rmt entries are still missing. I've opened another issue with SUN. The original six drvies in the L700 are still there and usable. The new four drives in the Scalar i2000 do not exist in /dev/rmt, yet are shown in cfgadm. -Original Message- From: veritas-bu-bounces at mailman.eng.auburn.edu on behalf of Peter Vines Sent: Wed 12/12/2007 7:13 PM To: veritas-bu at mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. SUN's response is that my st.conf is missing: name=st parent=fp target=0; From looking at old files, this line was probably removed by mistake in 2005 during another drive configuration, and obviously is not needed for the existing L700 and 9840 drives which are working fine. Now to find time and get permission to boot the production server... On Dec 10, 2007 6:39 PM, Peter Vines psv2b at virginia.edu wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnected configured unknown c8::500308c00189780a,0 med-changer connected configured unknown c8::500308c00189780a,1 tape connected configured unknown
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
A solution that worked, and suggested by a Veritas-bu subscriber, was to manually add the tape drives to st.conf and reload the driver. This successfully generated the missing /dev/rmt entries and allowed me to proceed with the robot and drive configuration using tpconfig. Steps: Added entries to /kernel/drv/st.conf: name=st parent=fp target=0 lun=0 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=1 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=2 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=3 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=4 fc-port-wwn=500308c00189780a; name=st parent=fp target=0 lun=0 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=1 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=2 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=3 fc-port-wwn=500308c00189780b; name=st parent=fp target=0 lun=4 fc-port-wwn=500308c00189780b; Determine st driver Id and display details: modinfo | grep st ... modinfo -i 49 Id Loadaddr Size Info Rev Module Name 49 786e 132e4 33 1 st (SCSI tape Driver 1.221) Reloaded st driver: modunload -i 49 modinfo -i 49 can't get module information: Invalid argument devfsadm -i st tpconfig work. Backups now working fine to the new tape drives. From: Vines, Peter (psv2b) Sent: Monday, December 24, 2007 12:49 PM To: Vines, Peter (psv2b); psv2b; [EMAIL PROTECTED] Subject: RE: [Veritas-bu] New tape drives not appearing in /dev/rmt. Adding the entry to st.conf followed by a boot -r did NOT fix my problem. The missing /dev/rmt entries are still missing. I've opened another issue with SUN. The original six drvies in the L700 are still there and usable. The new four drives in the Scalar i2000 do not exist in /dev/rmt, yet are shown in cfgadm. -Original Message- From: [EMAIL PROTECTED] on behalf of Peter Vines Sent: Wed 12/12/2007 7:13 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. SUN's response is that my st.conf is missing: name=st parent=fp target=0; From looking at old files, this line was probably removed by mistake in 2005 during another drive configuration, and obviously is not needed for the existing L700 and 9840 drives which are working fine. Now to find time and get permission to boot the production server... On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnectedconfigured unknown c8::500308c00189780a,0 med-changer connectedconfigured unknown c8::500308c00189780a,1 tape connectedconfigured unknown c8::500308c00189780a,2 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::500308c00189780b,0 med-changer connectedconfigured unknown c9::500308c00189780b,3 tape connectedconfigured unknown c9::500308c00189780b,4 tape connectedconfigured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt/2): STK 9840 /dev/sg/c0tw500104f00043e256l0: (/dev/rmt/0): STK 9840 /dev/sg/c0tw500104f00045cbb4l0: (/dev/rmt/1): STK 9840 /dev/sg/c1tw500104f000438e6el0: (/dev/rmt/3): STK 9840 /dev/sg/c1tw500104f000438f10l0: (/dev/rmt/4): STK 9840 /dev/sg/c1tw500104f000480658l0: (/dev/rmt/5): STK 9840 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu _http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu_ -- next part -- An HTML attachment was scrubbed... URL: _http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20071210/637ebd20
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
It sounds like you do not have the driver for your hba installed on the solaris box. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vines, Peter (psv2b) Sent: Monday, December 24, 2007 12:49 PM To: Vines, Peter (psv2b); psv2b; [EMAIL PROTECTED] Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. Adding the entry to st.conf followed by a boot -r did NOT fix my problem. The missing /dev/rmt entries are still missing. I've opened another issue with SUN. The original six drvies in the L700 are still there and usable. The new four drives in the Scalar i2000 do not exist in /dev/rmt, yet are shown in cfgadm. -Original Message- From: [EMAIL PROTECTED] on behalf of Peter Vines Sent: Wed 12/12/2007 7:13 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. SUN's response is that my st.conf is missing: name=st parent=fp target=0; From looking at old files, this line was probably removed by mistake in 2005 during another drive configuration, and obviously is not needed for the existing L700 and 9840 drives which are working fine. Now to find time and get permission to boot the production server... On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnectedconfigured unknown c8::500308c00189780a,0 med-changer connectedconfigured unknown c8::500308c00189780a,1 tape connectedconfigured unknown c8::500308c00189780a,2 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::500308c00189780b,0 med-changer connectedconfigured unknown c9::500308c00189780b,3 tape connectedconfigured unknown c9::500308c00189780b,4 tape connectedconfigured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt/2): STK 9840 /dev/sg/c0tw500104f00043e256l0: (/dev/rmt/0): STK 9840 /dev/sg/c0tw500104f00045cbb4l0: (/dev/rmt/1): STK 9840 /dev/sg/c1tw500104f000438e6el0: (/dev/rmt/3): STK 9840 /dev/sg/c1tw500104f000438f10l0: (/dev/rmt/4): STK 9840 /dev/sg/c1tw500104f000480658l0: (/dev/rmt/5): STK 9840 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu _http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu_ -- next part -- An HTML attachment was scrubbed... URL: _http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20071210/637ebd20/attachment-0001.htm_ -- - Peter Vines : [EMAIL PROTECTED] : (434) 924-4644 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
My guess is that you need to add the WWN to the st.conf... Something like this: name=st class=scsi target=c0tw500308c00189780al1; Do that for each drive and then reload the st driver... modinfo -i |grep st modunload -i (number of st driver) devfsadm -i st That ought to clear it up. One other possibility is to run the /usr/openv/volmgr/bin/sg.build command and have it build the sg.conf entries. Then, just change the 'name=sg' to be name=st and put that in st.conf. -Tim On 12/24/07, Vines, Peter (psv2b) [EMAIL PROTECTED] wrote: Adding the entry to st.conf followed by a boot -r did NOT fix my problem. The missing /dev/rmt entries are still missing. I've opened another issue with SUN. The original six drvies in the L700 are still there and usable. The new four drives in the Scalar i2000 do not exist in /dev/rmt, yet are shown in cfgadm. -Original Message- From: [EMAIL PROTECTED] on behalf of Peter Vines Sent: Wed 12/12/2007 7:13 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. SUN's response is that my st.conf is missing: name=st parent=fp target=0; From looking at old files, this line was probably removed by mistake in 2005 during another drive configuration, and obviously is not needed for the existing L700 and 9840 drives which are working fine. Now to find time and get permission to boot the production server... On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnectedconfigured unknown c8::500308c00189780a,0 med-changer connectedconfigured unknown c8::500308c00189780a,1 tape connectedconfigured unknown c8::500308c00189780a,2 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::500308c00189780b,0 med-changer connectedconfigured unknown c9::500308c00189780b,3 tape connectedconfigured unknown c9::500308c00189780b,4 tape connectedconfigured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt/2): STK 9840 /dev/sg/c0tw500104f00043e256l0: (/dev/rmt/0): STK 9840 /dev/sg/c0tw500104f00045cbb4l0: (/dev/rmt/1): STK 9840 /dev/sg/c1tw500104f000438e6el0: (/dev/rmt/3): STK 9840 /dev/sg/c1tw500104f000438f10l0: (/dev/rmt/4): STK 9840 /dev/sg/c1tw500104f000480658l0: (/dev/rmt/5): STK 9840 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu _http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu_ -- next part -- An HTML attachment was scrubbed... URL: _http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20071210/637ebd20/attachment-0001.htm_ -- - Peter Vines : [EMAIL PROTECTED] : (434) 924-4644 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
On Wed, Dec 12, 2007 at 12:13:38PM -0500, Peter Vines wrote: SUN's response is that my st.conf is missing: name=st parent=fp target=0; From looking at old files, this line was probably removed by mistake in 2005 during another drive configuration, and obviously is not needed for the existing L700 and 9840 drives which are working fine. Now to find time and get permission to boot the production server... Just for future use, it's often possible to reload 'st' without a reboot. Unlike the 'sd' driver, you can probably stop using the 'st' driver for a minute (any time no drives are in use or open in an application). If so, use 'modinfo' to find the id of the 'st' driver, then use 'modunload -i id' to unload it. After that, simply accessing a device will reload the driver, and it will reread the st.conf at that time. On more recent versions of Solaris you may be able to use 'update_drv' instead, but the above will work on older versions as well. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
SUN's response is that my st.conf is missing: name=st parent=fp target=0; From looking at old files, this line was probably removed by mistake in 2005 during another drive configuration, and obviously is not needed for the existing L700 and 9840 drives which are working fine. Now to find time and get permission to boot the production server... On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnectedconfigured unknown c8::500308c00189780a,0 med-changer connectedconfigured unknown c8::500308c00189780a,1 tape connectedconfigured unknown c8::500308c00189780a,2 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::500308c00189780b,0 med-changer connectedconfigured unknown c9::500308c00189780b,3 tape connectedconfigured unknown c9::500308c00189780b,4 tape connectedconfigured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt/2): STK 9840 /dev/sg/c0tw500104f00043e256l0: (/dev/rmt/0): STK 9840 /dev/sg/c0tw500104f00045cbb4l0: (/dev/rmt/1): STK 9840 /dev/sg/c1tw500104f000438e6el0: (/dev/rmt/3): STK 9840 /dev/sg/c1tw500104f000438f10l0: (/dev/rmt/4): STK 9840 /dev/sg/c1tw500104f000480658l0: (/dev/rmt/5): STK 9840 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu _http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu_ -- next part -- An HTML attachment was scrubbed... URL: _http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20071210/637ebd20/attachment-0001.htm_ -- - Peter Vines : [EMAIL PROTECTED] : (434) 924-4644 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
I've been a bit out of practice with Solaris, but have you tried running devfsadm or performing a reconfiguration reboot? Failing that you could, as some suggested, rebuild your path_to_inst file by renaming it and running 'devfsadm -r /a -p /a/etc/path_to_inst' or 'boot -ar' and accepting all the defaults except for the path_to_inst file. Hope that helps. Jason Ellis -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Vines Sent: Wednesday, December 12, 2007 7:12 AM To: Peters, Devon C Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. Hum, the new drives are NOT in /devices, nor in /etc/path_to_inst. And they do appear in cfgadm. On a Solaris 10 system, path_to_inst contains: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 0 st /[EMAIL PROTECTED],0/[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 7 st /[EMAIL PROTECTED],0/[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 14 st /[EMAIL PROTECTED],0/[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED],4 2 st new /[EMAIL PROTECTED],0/[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED],3 4 st new /[EMAIL PROTECTED],0/[EMAIL PROTECTED],60/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 15 st /[EMAIL PROTECTED],0/[EMAIL PROTECTED],60/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 16 st /[EMAIL PROTECTED],0/[EMAIL PROTECTED],60/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 17 st /[EMAIL PROTECTED],0/[EMAIL PROTECTED],60/SUNW,[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED],2 1 st new /[EMAIL PROTECTED],0/[EMAIL PROTECTED],60/SUNW,[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED],1 3 st new which has the 6 drives from the old tape library, and the 4 new drives. The Solaris 8 path_to_inst has: /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 135 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 136 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 137 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 28 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 29 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 30 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 126 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 128 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 129 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 130 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 133 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 134 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 31 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 32 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 33 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 127 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 131 st /[EMAIL PROTECTED],70/SUNW,[EMAIL PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 132 st which has the 6 drives from the old tape library, as well as entries from tape drives that no longer exist. Looking like an st driver issue. I'll update my SUN issue with this info. Peters, Devon C wrote: There goes that idea... :) So, your HBA's can see the LUNs, and cfgadm has identified them as tape devices. It seems like it's just devfs that isn't getting updated correctly... A couple other things to consider: Are there device files for these drives under /devices?find /devices | grep st.*cbn$ Are there entries in /etc/path_to_inst for these new tape drives? grep st /etc/path_to_inst If the /devices files exist, then I believe the st driver is doing it's thing. If there are no entries in path_to_inst then the devfs stuff is failing, if the entries are there, then I don't know what to say... You could try re-building path_to_inst, but Sun support would probably be your best bet. -devon -Original Message- From: Peter Vines [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 11, 2007 3:53 PM To: Peters, Devon C Cc: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
Thanks for the thought, but my st.conf already has those entries. name=st class=scsi target=0 lun=0; name=st class=scsi target=0 lun=1; name=st class=scsi target=0 lun=2; name=st class=scsi target=0 lun=3; name=st class=scsi target=0 lun=4; name=st class=scsi target=1 lun=0; name=st class=scsi target=1 lun=1; name=st class=scsi target=1 lun=2; name=st class=scsi target=1 lun=3; name=st class=scsi target=1 lun=4; ... continuing through target=15. Peters, Devon C wrote: Peter, I would guess that Sean is correct. I don't believe the default st.conf file for Solaris 10 includes support for tape drives that aren't lun 0. From what you show below your tape drives all start after LUN 0 (1, 2, 3, and 4). I'd suggest changing your st.conf entries from this: name=st class=scsi target=0 lun=0; name=st class=scsi target=1 lun=0; name=st class=scsi target=2 lun=0; name=st class=scsi target=3 lun=0; name=st class=scsi target=4 lun=0; name=st class=scsi target=5 lun=0; name=st class=scsi target=6 lun=0; To something like this: name=st class=scsi target=0 lun=0; name=st class=scsi target=0 lun=1; name=st class=scsi target=0 lun=2; name=st class=scsi target=0 lun=3; name=st class=scsi target=0 lun=4; name=st class=scsi target=1 lun=0; name=st class=scsi target=1 lun=1; name=st class=scsi target=1 lun=2; name=st class=scsi target=1 lun=3; name=st class=scsi target=1 lun=4; etc... Then run devfsadm and see if they're there. You may have to run update_drv st, or reload the st driver to pickup the changes. -devon - Date: Mon, 10 Dec 2007 19:14:10 -0500 From: Sean Mohr [EMAIL PROTECTED] Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. To: Peter Vines [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 Did you make sure you have /kernel/st.conf and (lpfc.conf if emulex fiber attached) entries. I'm not fully up on Solaris 10 at the moment but Solaris 10 does a lot a new things automatically that solaris 8/9 does not. Hope this helps Sean Mohr New York Life Storage Management Team On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnectedconfigured unknown c8::500308c00189780a,0 med-changer connectedconfigured unknown c8::500308c00189780a,1 tape connectedconfigured unknown c8::500308c00189780a,2 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::500308c00189780b,0 med-changer connectedconfigured unknown c9::500308c00189780b,3 tape connectedconfigured unknown c9::500308c00189780b,4 tape connectedconfigured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt/2): STK 9840 /dev/sg/c0tw500104f00043e256l0: (/dev/rmt/0): STK 9840 /dev/sg/c0tw500104f00045cbb4l0: (/dev/rmt/1): STK 9840 /dev/sg/c1tw500104f000438e6el0: (/dev/rmt/3): STK 9840 /dev/sg/c1tw500104f000438f10l0: (/dev/rmt/4): STK 9840 /dev/sg/c1tw500104f000480658l0: (/dev/rmt/5): STK 9840 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu _http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu_ -- next part -- An HTML attachment was scrubbed... URL: _http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20071210/637ebd20/attachment-0001.htm_ ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
Interesting... I just noticed that you mention you're using Solaris 8 on this host. Do you know if you have the st patch that provides IBM LTO3 drive support? A quick way to check is to run strings /kernel/drv/sparcv9/st | grep LTO, and see if IBM Gen 3 LTO is listed. -devon -Original Message- From: Peter Vines [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 11, 2007 3:35 PM To: Peters, Devon C Cc: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. Thanks for the thought, but my st.conf already has those entries. name=st class=scsi target=0 lun=0; name=st class=scsi target=0 lun=1; name=st class=scsi target=0 lun=2; name=st class=scsi target=0 lun=3; name=st class=scsi target=0 lun=4; name=st class=scsi target=1 lun=0; name=st class=scsi target=1 lun=1; name=st class=scsi target=1 lun=2; name=st class=scsi target=1 lun=3; name=st class=scsi target=1 lun=4; ... continuing through target=15. Peters, Devon C wrote: Peter, I would guess that Sean is correct. I don't believe the default st.conf file for Solaris 10 includes support for tape drives that aren't lun 0. From what you show below your tape drives all start after LUN 0 (1, 2, 3, and 4). I'd suggest changing your st.conf entries from this: name=st class=scsi target=0 lun=0; name=st class=scsi target=1 lun=0; name=st class=scsi target=2 lun=0; name=st class=scsi target=3 lun=0; name=st class=scsi target=4 lun=0; name=st class=scsi target=5 lun=0; name=st class=scsi target=6 lun=0; To something like this: name=st class=scsi target=0 lun=0; name=st class=scsi target=0 lun=1; name=st class=scsi target=0 lun=2; name=st class=scsi target=0 lun=3; name=st class=scsi target=0 lun=4; name=st class=scsi target=1 lun=0; name=st class=scsi target=1 lun=1; name=st class=scsi target=1 lun=2; name=st class=scsi target=1 lun=3; name=st class=scsi target=1 lun=4; etc... Then run devfsadm and see if they're there. You may have to run update_drv st, or reload the st driver to pickup the changes. -devon - Date: Mon, 10 Dec 2007 19:14:10 -0500 From: Sean Mohr [EMAIL PROTECTED] Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. To: Peter Vines [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 Did you make sure you have /kernel/st.conf and (lpfc.conf if emulex fiber attached) entries. I'm not fully up on Solaris 10 at the moment but Solaris 10 does a lot a new things automatically that solaris 8/9 does not. Hope this helps Sean Mohr New York Life Storage Management Team On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnectedconfigured unknown c8::500308c00189780a,0 med-changer connectedconfigured unknown c8::500308c00189780a,1 tape connectedconfigured unknown c8::500308c00189780a,2 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::500308c00189780b,0 med-changer connectedconfigured unknown c9::500308c00189780b,3 tape connectedconfigured unknown c9::500308c00189780b,4 tape connectedconfigured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt/2): STK 9840 /dev/sg/c0tw500104f00043e256l0: (/dev/rmt/0): STK 9840 /dev/sg/c0tw500104f00045cbb4l0: (/dev/rmt/1): STK 9840 /dev/sg/c1tw500104f000438e6el0: (/dev/rmt/3): STK 9840 /dev/sg/c1tw500104f000438f10l0: (/dev/rmt/4): STK 9840 /dev/sg/c1tw500104f000480658l0: (/dev/rmt/5): STK 9840
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
There goes that idea... :) So, your HBA's can see the LUNs, and cfgadm has identified them as tape devices. It seems like it's just devfs that isn't getting updated correctly... A couple other things to consider: Are there device files for these drives under /devices?find /devices | grep st.*cbn$ Are there entries in /etc/path_to_inst for these new tape drives? grep st /etc/path_to_inst If the /devices files exist, then I believe the st driver is doing it's thing. If there are no entries in path_to_inst then the devfs stuff is failing, if the entries are there, then I don't know what to say... You could try re-building path_to_inst, but Sun support would probably be your best bet. -devon -Original Message- From: Peter Vines [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 11, 2007 3:53 PM To: Peters, Devon C Cc: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. Thanks again for the thoughts, although I checked this earlier today. I've got 108725-26 installed. -27 is the latest, pertaining to HP LTO-4 drives. The patch is one level down, but has the IBM Ultrium Gen 3 LTO in the st driver. strings /kernel/drv/st | grep IBM IBM ULTRIUM-TD4 IBM ULT3580-TD4 IBM ULTRIUM-TD3 IBM ULT3580-TD3 IBM ULTRIUM-TD2 IBM ULT3580-TD2 IBM ULTRIUM-TD1 IBM ULT3580-TD1 IBM Ultrium Gen 4 LTO IBM Ultrium Gen 4 LTO IBM Ultrium Gen 3 LTO IBM Ultrium Gen 3 LTO IBM Ultrium Gen 2 LTO IBM Ultrium Gen 2 LTO IBM Ultrium LTO IBM Ultrium LTO Peters, Devon C wrote: Interesting... I just noticed that you mention you're using Solaris 8 on this host. Do you know if you have the st patch that provides IBM LTO3 drive support? A quick way to check is to run strings /kernel/drv/sparcv9/st | grep LTO, and see if IBM Gen 3 LTO is listed. -devon -Original Message- From: Peter Vines [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 11, 2007 3:35 PM To: Peters, Devon C Cc: [EMAIL PROTECTED]; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. Thanks for the thought, but my st.conf already has those entries. name=st class=scsi target=0 lun=0; name=st class=scsi target=0 lun=1; name=st class=scsi target=0 lun=2; name=st class=scsi target=0 lun=3; name=st class=scsi target=0 lun=4; name=st class=scsi target=1 lun=0; name=st class=scsi target=1 lun=1; name=st class=scsi target=1 lun=2; name=st class=scsi target=1 lun=3; name=st class=scsi target=1 lun=4; ... continuing through target=15. Peters, Devon C wrote: Peter, I would guess that Sean is correct. I don't believe the default st.conf file for Solaris 10 includes support for tape drives that aren't lun 0. From what you show below your tape drives all start after LUN 0 (1, 2, 3, and 4). I'd suggest changing your st.conf entries from this: name=st class=scsi target=0 lun=0; name=st class=scsi target=1 lun=0; name=st class=scsi target=2 lun=0; name=st class=scsi target=3 lun=0; name=st class=scsi target=4 lun=0; name=st class=scsi target=5 lun=0; name=st class=scsi target=6 lun=0; To something like this: name=st class=scsi target=0 lun=0; name=st class=scsi target=0 lun=1; name=st class=scsi target=0 lun=2; name=st class=scsi target=0 lun=3; name=st class=scsi target=0 lun=4; name=st class=scsi target=1 lun=0; name=st class=scsi target=1 lun=1; name=st class=scsi target=1 lun=2; name=st class=scsi target=1 lun=3; name=st class=scsi target=1 lun=4; etc... Then run devfsadm and see if they're there. You may have to run update_drv st, or reload the st driver to pickup the changes. -devon - Date: Mon, 10 Dec 2007 19:14:10 -0500 From: Sean Mohr [EMAIL PROTECTED] Subject: Re: [Veritas-bu] New tape drives not appearing in /dev/rmt. To: Peter Vines [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=iso-8859-1 Did you make sure you have /kernel/st.conf and (lpfc.conf if emulex fiber attached) entries. I'm not fully up on Solaris 10 at the moment but Solaris 10 does a lot a new things automatically that solaris 8/9 does not. Hope this helps Sean Mohr New York Life Storage Management Team On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt
[Veritas-bu] New tape drives not appearing in /dev/rmt.
I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnectedconfigured unknown c8::500308c00189780a,0 med-changer connectedconfigured unknown c8::500308c00189780a,1 tape connectedconfigured unknown c8::500308c00189780a,2 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::500308c00189780b,0 med-changer connectedconfigured unknown c9::500308c00189780b,3 tape connectedconfigured unknown c9::500308c00189780b,4 tape connectedconfigured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt/2): STK 9840 /dev/sg/c0tw500104f00043e256l0: (/dev/rmt/0): STK 9840 /dev/sg/c0tw500104f00045cbb4l0: (/dev/rmt/1): STK 9840 /dev/sg/c1tw500104f000438e6el0: (/dev/rmt/3): STK 9840 /dev/sg/c1tw500104f000438f10l0: (/dev/rmt/4): STK 9840 /dev/sg/c1tw500104f000480658l0: (/dev/rmt/5): STK 9840 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] New tape drives not appearing in /dev/rmt.
Did you make sure you have /kernel/st.conf and (lpfc.conf if emulex fiber attached) entries. I'm not fully up on Solaris 10 at the moment but Solaris 10 does a lot a new things automatically that solaris 8/9 does not. Hope this helps Sean Mohr New York Life Storage Management Team On Dec 10, 2007 6:39 PM, Peter Vines [EMAIL PROTECTED] wrote: I recently added connectivity to a Scalar i2000 with 4 LTO3 drives, to a Solaris 8 server. I removed all the entries in /dev/rmt, reconfigure booted, went through the sg install process, yet the server does not have entries in /dev/rmt for the new drives. The server is connected to two tape libraries: 1-L700 with 6 9840 drives, 2-i2000 with 4 LTO3 drives. The L700 drives continue to be present on the system and usable. I've also tried devfsadm, drvconfig, tapes, etc... Why don't the entries appear in /dev/rmt? I've done the same process on multiple Solaris 10 servers, connected to the same SAN and they all work fine. cfgadm -o show_FCP_dev -al c8 fc-fabricconnectedconfigured unknown c8::500308c00189780a,0 med-changer connectedconfigured unknown c8::500308c00189780a,1 tape connectedconfigured unknown c8::500308c00189780a,2 tape connectedconfigured unknown c9 fc-fabricconnectedconfigured unknown c9::500308c00189780b,0 med-changer connectedconfigured unknown c9::500308c00189780b,3 tape connectedconfigured unknown c9::500308c00189780b,4 tape connectedconfigured unknown sgscan /dev/sg/c0tw500308c00189780al0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780al1: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780al2: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl0: Changer: ADICScalar i2000 /dev/sg/c0tw500308c00189780bl3: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500308c00189780bl4: Tape (???): IBM ULTRIUM-TD3 /dev/sg/c0tw500104f000438becl0: (/dev/rmt/2): STK 9840 /dev/sg/c0tw500104f00043e256l0: (/dev/rmt/0): STK 9840 /dev/sg/c0tw500104f00045cbb4l0: (/dev/rmt/1): STK 9840 /dev/sg/c1tw500104f000438e6el0: (/dev/rmt/3): STK 9840 /dev/sg/c1tw500104f000438f10l0: (/dev/rmt/4): STK 9840 /dev/sg/c1tw500104f000480658l0: (/dev/rmt/5): STK 9840 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
