Veritas-bu

[Veritas-bu] Fibre Channel Library & Drives Not Showing Up in sgscan

2006-07-19 04:44:36
Subject: [Veritas-bu] Fibre Channel Library & Drives Not Showing Up in sgscan
From: william.d.brown at gsk.com (william.d.brown AT gsk DOT com)
Date: Wed, 19 Jul 2006 09:44:36 +0100
Well, you say that you have followed the Device Configuration manual, but 
the message you show suggests that there is some step that has not worked. 
 The 'special procedure' is described in the manual, but what it says is 
that this is done for you by sg.build and sg.install, which is why there 
are no manual steps:

<<
Configuring the Sun StorEdge Network Foundation HBA Driver
The StorEdge Network Foundation HBA requires special configuration to bind 
device World Wide port names for use by the VERITAS sg driver.
The script /usr/openv/volmgr/bin/sg.build adds the proper entries to the 
sg.linksand sg.conf files. Before running the script, make sure that all 
devices are powered on and connected to the HBA.
An example of the additional entries in 
/usr/openv/volmgr/bin/driver/sg.conf follows:
name="sg" parent="fp" target=0 lun=0 fc-port-wwn="22000090a50001c8";
name="sg" parent="fp" target=0 lun=1 fc-port-wwn="22000090a50001c8";
An example ofthe additional entriesin 
/usr/openv/volmgr/bin/driver/sg.links follows:
type=ddi_pseudo;name=sg;addr=w22000090a50001c8,0; sg/c\N0t\A1l0
type=ddi_pseudo;name=sg;addr=w22000090a50001c8,1; sg/c\N0t\A1l1
Note Each time a new device is added or an old device removed, re-create 
and re-install the new sg configuration (see ?Configuring SG and ST 
Drivers? on page 9).
The script /usr/openv/volmgr/bin/sgscanchecks for devices that are not 
configured, and produces output similar to the following example:
#WARNING: detected StorEdge Network Foundation connected devices not
in sg configuration file:
#
#
Device World Wide Port Name 21000090a50001c8
#
#
See /usr/openv/volmgr/MediaMgr_DeviceConfig_Guide.txt topic
#
"Configuring the Sun StorEdge Network Foundation HBA/Driver"
#
for information on how to use sg.build and sg.install
#
to configure these devices

>>
What you need to check is that the 'live' /kernel/drv/sg.conf does have 
the name="sg" entries , and /etc/devlink.tab contains the type=ddi_pseudo 
entries for your drives.  And finally that you really did unload and 
reload the sg driver. 

William D L Brown




"Katauskas, Daryl" <dkatauskas at nst-inc.com> 
Sent by: veritas-bu-bounces at mailman.eng.auburn.edu
18-Jul-2006 23:03
 
To
veritas-bu at mailman.eng.auburn.edu
cc

Subject
[Veritas-bu] Fibre Channel Library & Drives Not Showing Up in sgscan






Sirs:

We recently added a StorageTek SL500 library with HP LTO3 (Fibre) tape 
drives on our Solaris 9 NetBackup (v6.0 MP2) Media server. (Also using a 
Sun branded QLOGIC 2342 HBA running under Sun SAN Foundation v4.4.10 
drivers & packages).

Drives & library are recognized by the O/S (Brocade 4100 switch zoning was 
done and a reconfiguration boot of the Media Server was performed.)

We also ran the procedure for adding new devices under the SG driver 
control as documented in the NetBAckup Media Manager Device Configuration 
Manual (page 8).

After completing the documented procedure and performing the necessary 
reconfiguration reboots, we again ran the sgscan command and did not see 
the new SL 500 Robot or LTO3 drives as being under SG driver control. 
(They were not listed at all).

We did recieve the following message:



WARNING: detected StorEdge Network Foundation connected devices not in
#         SG configuration file:
#
#    Device World Wide Port Name XXXXXXXXXXXXXXXXX
#    Device World Wide Port Name XXXXXXXXXXXXXXXXX
#    Device World Wide Port Name XXXXXXXXXXXXXXXXX
#    Device World Wide Port Name XXXXXXXXXXXXXXXXX
#    Device World Wide Port Name XXXXXXXXXXXXXXXXX

The Media Manager Device Configuration Guide refererences a "Special 
Procedure" for adding Sun StorEdge Network Foundation HBA with the Veritas 
sg driver. What this "Special Procedure" is and what steps need to be 
taken to successfully add the Sun StorEdge Network Foundation HBA devices 
doesn't seem to be documented anywhere.

I would appreciate any assistance in locating and applying the correct 
procedure to bring these devices under the SG driver control.

Thanks in Advance,

Daryl Katauskas

_______________________________________________
Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu





<Prev in Thread] Current Thread [Next in Thread>