Toinstall IBMtape,followthisprocedure:
1. Notify usersthatsystem maintenanceanda rebootwillbeperformed.
2. Choose atimewhenallsystemactivity canbe stoppedtoperformthe installation.
3. Logontothetargetsystemasroot.
4. Ensure thatall userandtapedriveactivityonthesystemhashalted.
5. If tapedrivesnotcontrolledbyIBMtapeareinstalledonthesystem,listthe lowdensitydevicespecial filesandfindtheSCSIaddresseswith whichthey are associatedcurrently.
% ls -l /dev/rmt/*l
lrwxrwxrwx 1 root root 72 Aug 26 15:47 /dev/rmt/5l ->
../../devices/iommu@f,e0000000/sbus@f,e0001000/QLGC,isp@3,10000/st@2,0:l The lastportionoftheresultsshowsthecontrollingdevicedriverand SCSI address.Intheprecedingexample,/dev/rmt/5landtherelated5m,5h,andso on,arecontrolled bythestdevicedriverandareassociatedwith thedeviceat SCSI address2,LUN 0.Recordthedevicetype,/dev/rmtspecial filenumber, owningdriver,SCSItarget addressandLUN;youwillneedthemlaterduring theinstallation.
For example,supposeaninstallationhastwonon-IBMdevicesownedbystat SCSI addresses2and8. Thelowdensitydevicesareaccessedasspecialfiles /dev/rmt/5l and/dev/rmt/6l.Fortheequipmentlistingafter recordingthedevice information,seeTable15.
Table15.IBMtapeInstallorUpdate
Device OldSpecialFile OldDriver
SCSIAddress/LUN (Old)
QIC /dev/rmt/5l st 2/0
QIC /dev/rmt/6l st 8/0
Solaris Device Driver (IBMtape)
6. Ifthis isan updatetoIBMtape,thereare alreadyIBMtapeowneddevices installed.Inthiscase,listtheprimarydevicespecialfiles andfindtheSCSI addresseswith whichtheyareassociatedcurrently.
% ls -l /dev/rmt/*st /dev/rmt/*smc
lrwxrwxrwx 1 root other 46 Aug 26 16:36 /dev/rmt/0st ->
../../devices/pci@6,4000/scsi@3/IBMtape@b,0:st
lrwxrwxrwx 1 root other 47 Aug 26 16:36 /dev/rmt/1smc ->
../../devices/pci@6,4000/scsi@3/IBMtape@b,1:smc
Thelast portionoftheresultsshowsthecontrollingdevicedriverand SCSI address.Intheprecedingexample,/dev/rmt/0st(aSCSI tapedrive)is controlled byIBMtapeandisassociatedwith thedeviceat SCSIaddressb, LUN 0.Theaddressisreportedinhexadecimal:0xb=11decimal./dev/rmt/1smc (a SCSImediumchanger)isassociatedwiththedeviceatSCSI addressb, LUN 1.Recordthedevicetype,/dev/rmtspecial filenumber,owningdriver, SCSI targetaddressand LUN;youwillneedthemlaterduringthe
installation.
For example,supposeaninstallationhasonlyanIBMtapeowneddevice installed,atSCSI address8.Thedeviceconsistsofbotha tapedriveandSCSI medium changer.Thetapedriveisaccessedas/dev/rmt/2standthemedium changeras/dev/rmt/3smc.For asimilarequipmentlisting afterrecordingthe deviceinformation,seeTable16.
Table16.EquipmentListing
Device OldSpecialFile OldDriver
SCSIAddress/LUN (Old)
3580-H11drive /dev/rmt/2st IBMtape 8/0
3581-H17changer /dev/rmt/3smc IBMtape 8/1
7. Choose oneofthefollowingmethodstopreventconflictsbetweenIBMtape and otherSCSItapedevicedrivers,dependingontheequipmentattachedto your system.
Attention: Failuretopreventmorethanonedevicedriverfromoperatingthe same SCSItapedrivemaycausesystempanicsordatalossonthetapedrive.
a. IfthesystemhasonlyIBMtapeowneddevicesattached,followthesesteps topreventstandothernon-IBMSCSItapedevicedriversfromclaiming theIBMdevices.
1) Edit/kernel/drv/st.conf andcommentoutallSCSI targetentriesby placingapoundsign(#)inthefirstcolumn ofeachtargetentry.The followingexampleshowstheentriesforSCSItarget addresses0and1 commentedout.Repeatthis operationforalltargetentries.
#name="st" class="scsi"
#target=0 lun=0;
#name="st" class="scsi"
#target=1 lun=0;
2) Forothernon-IBMSCSItapedevicedriversthatareinstalled,remove thedrivers iftheyarenotneeded.Ifa driverisforSCSI tapedevices only,it shouldnotbeneeded. Ifadriverisforbothtapeand disk devices,followthesupplier’sinstructionstodisableitsaccesstoall SCSItapedevices.
b. IfthesystemhasamixtureofIBMtapeowneddevicesandothertape drives,followthesestepstoconfigurestandothernon-IBMSCSItape
Solaris Device Driver (IBMtape)
Chapter32.Installation,Removal,andConfiguration 163
devicedriverssotheycontrolarangeoftargetaddressesdistinctfromthe rangethatIBMtapeuses.Thesestepsleavetargetaddresses7 and15 unclaimedbyalltargetdevicedrivers,becauseSCSI adapterstypicallyuse oneofthose twoaddresses.
1) Edit/kernel/drv/st.conf andcommentoutSCSItarget entriesfor addresses7–15byplacingapoundsign(#)in thefirst columnofeach targetentry.Inthefollowingexample,theentriesforSCSIaddresses7 and8havebeen commentedout.Repeatthis operationforallentries inthetargetaddressrange7–15.
#name="st" class="scsi"
# target=7 lun=0;
#name="st" class="scsi"
# target=8 lun=0;
2) Forothernon-IBMSCSItapedevicedriversthatareinstalled,follow thesuppliers’instructionstodisabletheiraccesstoallSCSI tape devicesintheaddressrange7–15.
3) Later,afterthev packagehasbeen installed,youalteritsconfiguration filesoitdoesnotuseSCSI targetaddressesintherange0–7 oraddress 15.
Nowstandothernon-IBMSCSItapedevicedrivershavebeenconfigured toavoidconflictingwithIBMtape.
8. Remove allspecialfileentriesunder/dev/rmt.Thisensuresthatstaleentriesdo notexist afterthesystemisrebooted.Newentriesarecreatedwhenthe system isrebooted.
% rm /dev/rmt/*
9. If youareupdatingthelevelof IBMtape,removethecurrentlyinstalled IBMtape package.Ifthisisanew installationofIBMtape,skipthis step.
a. Usepkgrmtoremovethecurrentlevel.
% /usr/sbin/pkgrm IBMtape
Respondtothepkgrm prompts.
b. Examinetheresultsfrompkgrm.Ifyoufindthesemessages:
...
Device busy
Cannot unload module: IBMtape Will be unloaded upon reboot.
...
ThenoneormoreIBMtapeownedtapedrives werestillinuse. Identify thedrivesand endtheprocessesthatareusingthem.Ifyoucannot identifytheprocesses,youmustreboot thesystem tofreethetapedrive, then continuewith theinstallation fromthispoint.
10. Choose oneofthefollowingmethodstoinstall theIBMtapepackage, dependingonthepackagedistribution mediumandthelocationofsystem resources.
Note: Ifthisisanew installationofIBMtape,IBMdevicesarenotyet attachedtothesystem,andyouseepkgadderrormessagessimilarto thefollowing:
...
drvconfig: Driverv) successfully added to system but failed to attach
## The device driver was unable to detect any supported devices!
Solaris Device Driver (IBMtape)
## Verify that the device(s) are properly connected and powered on.
## Ensure that the SCSI adapter device driver is installed/configured.
## Then try re-installing the device driver as follows:
## -enter the command: rem_drv IBMtape
## -enter the command: add_drv -m ’* 0666 bin bin’ IBMtape
## If problems persist, contact your IBM service representative.
pkgadd: ERROR: postinstall script did not complete successfully ...
Later,after youhavecabledIBMdrives tothesystem andrebooted,the driverisattachednormally.
a. Ifthedistributionmediumisa CD,followthesesteps:
1) Determineifvolume managementisrunningbydisplayingthefile systemtypeforthe/voldirectory.Volumemanagement mountsanNFS filesystemonthe/voldirectory.Use thevol commandtodisplaythefile systemtype.
% df -n /vol
/vol :nfs
Inthis example,thefilesystemtype isNFS; thereforevolume
managementisrunning.Ifvolumemanagement isnotrunning, the/vol directoryisshownasaUFSfilesystem.
2) Insertthedistribution CDintothelocalCD-ROMdrive.
3) Ifvolumemanagementisrunning,wait forthevolume management servicestodetectandmounttheCD-ROMfilesystem.Typically,this completeswithin30seconds.
4) Ifvolumemanagementisnotrunning,youmustmounttheCD-ROM filesystemmanually.Todoso,youmustknowthedevicespecialfile nameforyour CDdrive.Forexample,ifyour CDdriveisoncontroller 1atSCSI target6,youwouldusethiscommand:
% mount -o ro /dev/dsk/c1t6d0s0 /mnt
5) Reviewthecontentsofthe../Solaris/IBMtape.Readme foranyupdated instructions.
6) Usepkgaddtoinstall thedriver.DependingonwheretheCD-ROM filesystemismounted, useoneofthesecommands:
%/usr/sbin/pkgadd -d /cdrom/cdrom0/Solaris/IBMtape.x.x.x.x
%/usr/sbin/pkgadd -d /mnt/Solaris/IBMtape.x.x.x.x
wherex.x.x.xistheversion numberofIBMtapeincludedontheCD.
7) Ifvolumemanagementisrunning,eject theCD:
% /usr/bin/eject cd
8) Otherwise,unmountthedevice,then ejectthemediamanually:
% /usr/bin/unmount /mnt
b. Ifthedistributionmediumisa disketteandthesystemonwhichyouare installinghasadiskettedrive,performthese steps:
1) Insertthedistribution disketteintothelocaldiskettedrive.
2) Mountthediskette usingvolume managementservices:
% /usr/bin/volcheck
3) Usepkgaddtoinstall thedriver.Inthisexample,volcheckmounted the disketteas/vol/dev/aliases/floppy0.Usetheappropriatenameasassigned byyour system.
% /usr/sbin/pkgadd -d /vol/dev/aliases/floppy0 4) Ejectthediskette:
Solaris Device Driver (IBMtape)
Chapter32.Installation,Removal,andConfiguration 165
% /usr/bin/eject floppy
c. Ifthedistribution mediumisa disketteandthesystemonwhichyouare installingthepackagedoesnothaveadiskettedrivebut isconnected toa network, followthesesteps:
1) Locateanothersystem onthesamenetworkthathasadiskettedrive.
Logontothatsystem.
2) Insertthedistributiondisketteand mountitusingvolumemanagement services:
% /usr/bin/volcheck
3) Useddtotransfer theinstallation packagetoapackage file.Inthis example,volcheckmountedthedisketteas/vol/dev/aliases/floppy0.Use theappropriatenameasassignedbyyoursystem.
% /usr/bin/dd if=/vol/dev/aliases/floppy0 of=/tmp/image.pkg 4) Ejectthediskette:
% /usr/bin/eject floppy
5) FTPthepackagefiletothetargetsystem.Usebinarytransfer mode.
Placethepackage fileinthetarget system’s/tmpdirectory.
6) Logontothetarget systemasroot.
7) Usepkgaddtoinstall thedriver.Inthisexample,thepackagefilewas FTPedtothe/tmpdirectoryasimage.pkg.
% /usr/sbin/pkgadd -d /tmp/image.pkg
d. Ifthedistributionmediumisa packagefileinaUNIXfilesystem,follow thesesteps. Youmayhaveobtaineda packagefilebyextractingitfroma distribution disketteorbydownloading itfromIBM’sanonymousFTP site. Thisexamplepresumesa packagefilenamedIBMtape.4.0.2.7,located inthe/tmpdirectory.
1) Ifnecessary,FTPthepackagefiletothetargetsystem.Usebinary transfermode. Placethepackagefileinthetargetsystem’s/tmp directory.
2) Usepkgaddtoinstall thedriver:
% /usr/sbin/pkgadd -d /tmp/IBMtape.4.0.2.7
11. Ifyour systemenvironmentincludesamixtureof IBMtapeowneddevicesand devices ownedbystoranotherthirdpartySCSItapedevicedriver,you alreadymodifiedtheconfigurationfilesforthenon-IBMdevicedriversand restricted themto targetaddressesintherange0–6.
NowyoumustrestrictIBMtapetotargetaddressesintherange8–14.Edit IBMtape.conf,locatedin/usr/kernel/drv, andcommentoutentriesforSCSI target addresses0–7 and15byplacinga poundsign(#)inthefirstcolumnofeach linemakinguptheentries.Inthefollowingexample,theentriesforaddress0, LUN 0andaddress 0,LUN1 havebeen commentedout.Repeattheoperation forall stanzasintheaddressrange0–7,andaddress 15.NotethateachSCSI target addresshasastanzaforbothLUN 0and1.
#name="IBMtape" class="scsi"
# buffering=1
# immediate=0
# trailer=0
# sili=0;
12. Shut downthesystem.Onecommonmethodtoperform ashutdownis shown herebutuseyour normalprocedures.
% /usr/sbin/shutdown -y -g0 -i0
13. Address orreaddressdevicesasdeterminedbyyourinstallation:
a. IfthesystemhasonlyIBMtapeowneddevicesattached,youmaychoose addressesintherange0–6 or8–14.Leave addresses7and15unused, becausethese addressesare usedtypicallybytheSCSI adapter.
1) Foreachdevice,seetheappropriateIBM hardwarereference forany specialinstructionsaboutaddressing.Thenset theaddress andrecord thedevicetype,SCSI address,andLUN.Forexample,supposean installationhasonlyIBMtapeowneddevices attached.An IBMdevice withtapedriveandmediumchangerisadded.Itisaddressedattarget 4,andtheinformationisrecorded.Fortheresults,seeTable17.
Table17.EquipmentListing
Device OldSpecialFile OldDriver
SCSI
b. Ifyouareusingdistinctaddressrangestoseparate tapedrives thatare IBMtapeownedfromdevicesthatareownedbystoranotherdriver, readdressthetapedrives now.
1) Foreachdevicetobeownedbystor anotherSCSItapedevicedriver, seethemanufacturer’shardwarereferenceforanyspecial instructions aboutreaddressing. Thenreaddress eachdevicetoan addressinthe range0–6.For eachtapedrivethatisreaddressed,record thenew SCSI addressnexttothespecial filenumber andoldSCSIaddressthatyou recordedpreviously.
2) ReaddressalltapedrivesthatareownedbyIBMtapeto addressesin therange8–14.SeetheappropriateIBMhardwarereferencesforany specialinstructionsaboutreaddressing.For eachtapedrivethatis readdressed,recordthenewSCSI addressnexttothespecialfile numberandoldSCSIaddress,if any,thatyourecordedpreviously.
Forexample,supposeaninstallationhastwonon-IBMdevicesowned bystatSCSI addresses9andB(12indecimal).AnIBM devicewith tapedriveand mediumchangerisadded.Topreventconflictsbetween IBMtapeandst,thenon-IBMdevicesare allplacedataddressesinthe range0–6.Thenew IBMdeviceisaddressedintherange8–14,at address10(X'0A').Dependingontheaddresseschosenforthe
non-IBMdevices,afterreaddressingand recordingdeviceinformation, seeTable17forthepossibleequipmentlisting.
Table18.EquipmentListing
Device OldSpecialFile OldDriver
SCSI
QIC /dev/rmt/2l st 9/0 3/0
Solaris Device Driver (IBMtape)
Chapter32.Installation,Removal,andConfiguration 167
Table18.EquipmentListing (continued)
Device OldSpecialFile OldDriver
SCSI
QIC /dev/rmt/3l st b/0 5/0
3580-H11drive – – – a/0
3581-H17 changer
– – – a/1
NotethattheSCSItarget addressoffibre channeltapedevicemaybe over15.
14. Cablethetapedrivestothesystem,ifnotyetdone.Seethemanufacturer’s hardwarereferencesforanyspecial instructionsaboutcabling.Besureto terminateeachSCSI busproperly.
15. Boot thesystemaccordingtoyourinstallation’snormalprocedures.
16. Logonasrootandlistthedevicespecialfilesin/dev/rmtasyoudidearlier during theinstallation.
% ls -l /dev/rmt/*l
% ls -l /dev/rmt/*st /dev/rmt/*smc
Compare theSCSIaddressesobtainedfromlswiththereaddressedSCSI targetsyourecorded.Writethenewdevicespecial filenumbersandowning drivernext tothematchingnewSCSI addresses.
For example,supposeaninstallationhadtwonon-IBMdevicesowned previouslybystatSCSIaddresses2 and8.AnIBMdevicewith tapedrive and mediumchangerisadded.TopreventconflictsbetweenIBMtapeandst, thenon-IBMdevicesare allplacedataddressesintherange0–6.Thenew IBM deviceisaddressedintherange8–14.Dependingontheaddresses chosen, aftercompletinginstallationand recordingdeviceinformation,see Table19forsampleequipmentlistingentries.
Table19.SampleEquipmentListing
Device
QIC /dev/rmt/5l st 2/0 2/0 st /dev/rmt/0l
QIC /dev/rmt/6l st 8/0 0/0 st /dev/rmt/1l
3580-H11 drive
– – – 8/0 IBMtape /dev/rmt/2st
3581-H17 changer
– – – 8/1 IBMtape /dev/rmt/3smc
Based onthelisting,youcanseethatthetapedriveaccessedpreviouslyas /dev/rmt/5isnow accessedas/dev/rmt/0,thenewmediumchangerisaccessible as/dev/rmt/3smc, andsoon.
17. Verifyoperationofthenewlyinstalledorreaddressedequipment.
18. Notify usersof anychangeddevicespecialfiles numbers.
Solaris Device Driver (IBMtape)
|
|