EasyManua.ls Logo

Symantec NetBackup 5230 - Page 75

Symantec NetBackup 5230
201 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
It's possible for you to see expected entries in the /proc/scsi/scsi directory and
yet have the information be stale. To ensure that the information is not stale, use
the sg_inq command to query the current status.
appsanclient1:~ # sg_inq -I /dev/sg3
VPD INQUIRY: Device Identification page
Designation descriptor number 1, descriptor length: 55
id_type: T10 vendor identification, code_set: ASCII
associated with the addressed logical unit
vendor id: SYMANTEC
vendor specific: FATPIPE 1.0 Testsys.enx1.symantec.com
appsanclient1:~ # sg_inq -I /dev/sg4
VPD INQUIRY: Device Identification page
Designation descriptor number 1, descriptor length: 55
id_type: T10 vendor identification, code_set: ASCII
associated with the addressed logical unit
vendor id: SYMANTEC
vendor specific: FATPIPE 1.1 Testsys.enx1.symantec.com
If these commands fail then it is likely that there is stale information in the operating
system . You can run the rescan-scsi-bus util (/bin/rescan-scsi-bus.sh) to
force a refresh. Run it first with the -r option to remove the stale entries. If that
does not work, try the following:
If you do not see the entries you expect after you run the rescan-scsi-bus
util -r command, try it with the -I option. That forces the FC link to be
renegotiated.
Restart the FT media server on the appliance (enable and then disable it). Then
rescan with the rescan-scsi-bus util command.
If that command fails, the most likely root cause is a zoning issue. You should
contact Support to help identify the zoning on the appliance.
Finally, if you have had to rescan the SCSI devices or there are new SCSI
devices, restart the FT client daemon. Once it has been restarted, you can look
at the VxUL log for originator 200 to check that it sees the SCSI devices correctly:
appsanclient1:~ # /usr/openv/netbackup/bin/vxlogview -p nb -o 200
04/27/11 13:58:25.736 [FATClientMgrService::init] Client
successfully started (FATClientMgrService.cpp:277)
04/27/11 13:58:25.822 [DiscoveryTaskThread] DiscoveryTask Thread
1094740288 Startup
04/27/11 13:58:25.822 [AddDevice] /dev/sg3
Inquiry "SYMANTECFATPIPE 1.0 nbapp36.engba.symantec.com"
TargetHBA:LUN:InitiatorHBA = 1:0:0x40 State = 1 RefCount = 0
75Troubleshooting generic issues
Troubleshooting target mode port from the client

Table of Contents

Other manuals for Symantec NetBackup 5230

Related product manuals