cancel
Showing results for 
Search instead for 
Did you mean: 

scan for a new media server does not work

YAG55
Level 4

scan for a new media server (SunOS SERV  5.11 11.3 sun4v sparc sun4v)  does not work :

   

1 ACCEPTED SOLUTION

Accepted Solutions

tunix2k
Level 5
Partner Accredited

Hi @YAG55

you have a problem with driver on OS Level. Prior to configure and install sg driver you have to solve this.

Please have a look at devoce pathes. In cfgadm output you have c6 and c7 on pci bus pci@300. Your tape drivers are linked to qlc hbas in pci bus pci@3c0. Did you change the slots for hba ? Did you add a pci slot/bus to root ldom ?

Please remove the dead links for *cbn (devfsadm -C)

Solve the fc connection to see tapes

generate new cbn devices (if not happend by solaris itselv) started with 0cbn

configure and install sg drivers

ciao

tunix2k

View solution in original post

6 REPLIES 6

mph999
Level 6
Employee Accredited

I presume you mean tape device / library ...

I will hazard a guess that /usr/openv/volmgr/bin/scan isn;t showing anthing.

Do you see devices at OS level

cfgadm -lva -o show_FCP_dev

Do you have OS device files for the drives /dev/rm/0cbn etc ...)

If not, you need to resolve this at OS level first, if you do, you most likely need to rebuild the sg drivers.

https://www.veritas.com/content/support/en_US/article.100019093.html

exactly, it's a tape device / library
I confirm that the order does not return any output
 
cfgadm -lva -o show_FCP_dev :
Ap_Id                          Receptacle   Occupant     Condition  Information
When         Type         Busy     Phys_Id
c6                             connected    unconfigured unknown
unavailable  fc           n        /devices/pci@300/pci@1/pci@0/pci@4/SUNW,qlc@0/fp@0,0:fc
c7                             connected    configured   unknown
unavailable  fc-fabric    n        /devices/pci@300/pci@1/pci@0/pci@4/SUNW,qlc@0,1/fp@0,0:fc
c7::50060e80164dfe10,0         connected    configured   unknown
unavailable  disk         n        /devices/pci@300/pci@1/pci@0/pci@4/SUNW,qlc@0,1/fp@0,0:fc::50060e80164dfe10,0

ls -altr /dev/rmt/*cbn
lrwxrwxrwx   1 root     root          84 Feb 14 16:16 /dev/rmt/0cbn -> ../../devices/pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0/fp@0,0/st@w2100000d7754a0d0,a:cbn
lrwxrwxrwx   1 root     root          84 Feb 14 16:16 /dev/rmt/1cbn -> ../../devices/pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0/fp@0,0/st@w2100000d7754a0d0,9:cbn
lrwxrwxrwx   1 root     root          84 Feb 14 16:16 /dev/rmt/2cbn -> ../../devices/pci@3c0/pci@1/pci@0/pci@7/SUNW,qlc@0/fp@0,0/st@w2100000d7754a0d0,8:cbn

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@YAG55

Have you tried to rebuild the sg driver? 
On Solaris, this is a requirement once visibility at OS-level has been verified.

These steps have always worked for me:

# cd /usr/openv/volmgr/bin/driver
# /usr/openv/volmgr/bin/sg.build all 

Install the new sg driver configuration:

# /usr/bin/rm -f /kernel/drv/sg.conf
# /usr/openv/volmgr/bin/driver/sg.install

Check/verify config:

# /usr/openv/volmgr/bin/sgscan

 

tunix2k
Level 5
Partner Accredited

Hi @YAG55

you have a problem with driver on OS Level. Prior to configure and install sg driver you have to solve this.

Please have a look at devoce pathes. In cfgadm output you have c6 and c7 on pci bus pci@300. Your tape drivers are linked to qlc hbas in pci bus pci@3c0. Did you change the slots for hba ? Did you add a pci slot/bus to root ldom ?

Please remove the dead links for *cbn (devfsadm -C)

Solve the fc connection to see tapes

generate new cbn devices (if not happend by solaris itselv) started with 0cbn

configure and install sg drivers

ciao

tunix2k

Hi Marianne,

 Actually, the actions below have been performed
 the result is:
 One tape drive detected out of 10

/usr/openv/volmgr/bin# sgscan
/dev/sg/c0tw2100000d7754a0d0l0: Changer: "STK L700"
/dev/sg/c0tw2100000d7754a0d0l1: Tape (/dev/rmt/9): "IBM ULTRIUM-TD4"

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@YAG55 

Please go back to @tunix2k 's post.
Seems you still have a problem at OS-level.