Media Server HBA Port : 1
Media Server Port Mode : FABRIC
Media Server LUN : 0
If the output does not display correctly, you can use the nbftconfig -rescanclient
client command. Wait a few minutes and attempt to list the clients again. If running
this command fails, go to the client system and verify that the operating system can
detect the SCSI devices. You can see a list of devices in the /proc/scsi/scsi
directory.
appsanclient1:~ # cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 08 Lun: 00
Vendor: DP Model: BACKPLANE Rev: 1.00
Type: Enclosure ANSI SCSI revision: 05
Host: scsi0 Channel: 02 Id: 00 Lun: 00
Vendor: DELL Model: PERC 5/I Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi0 Channel: 02 Id: 01 Lun: 00
Vendor: DELL Model: PERC 5/I Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: Dell Model: Virtual CDROM Rev: 123
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: Dell Model: Virtual Floppy Rev: 123
Type: Direct-Access ANSI SCSI revision: 02
Note: If the nbftconfig -rescanclient client command works, Symantec
recommends that you still go to the client system and verify that the operating
system can detect the SCSI devices. It's possible that the output that is received
after the nbftconfig -rescanclient client command is run can contain stale
information.
From the example, the expected SCSI devices are missing. You should have seen
two devices from the vendor, ARCHIVE, and the model Python. In this situation,
you should look at the /sys/class/fc_remote_ports directory. This directory
shows you the remote FC ports that the operating system can see.
appsanclient1:~ # ls -la /sys/class/fc_remote_ports/
total 0
drwxr-xr-x 2 root root 0 Apr 25 11:06 .
drwxr-xr-x 24 root root 0 Apr 24 17:55 ..
73Troubleshooting generic issues
Troubleshooting target mode port from the client
To Next Page
Loading...
