5. Enter the vpsInactiveSet command from the service terminal.
6. Startup one of the hosts.
7. If the host can access all of the target devices, shut down the host and repeat
steps 6 and 7 for each of the other hosts.
8. If each host can access all devices then there is a problem with the Virtual
Private SAN Access settings. Go to step 10.
9. If the host cannot access all of the target devices, then there is a problem with
the devices or their SAN connections. After you resolve the problem, proceed
to step 10.
10. Shut down all of the hosts.
11. Reactivate Virtual Private SAN by entering the vpsActiveSet command
from the service terminal.
12. Use the ADIC Management Console
menu to verify the host and target device access settings.
SAN
13. Restart the hosts and verify that each host can access the devices that have
been assigned by VPS.
SCSI MAP
These steps are performed if:
Get ADIC Gateway SCSI Information
1. Connect the service terminal to the Service Port (see See "Connecting to the
Service Port" on page 217)
2. If the ADIC Gateway is off, then turn it on and wait until the ADIC Gateways
Ready
3. As the ADIC Gateway is booting, several status messages should be
displayed on the service terminal. If no status messages are displayed, go to
"Service Port MAP" on page 191 to determine whether the RS-232 cable and
SCSI MAP
•
Errors are reported on the SCSI bus
•
SCSI I/O fails to operate
•
Parity errors are detected on the SCSI bus
•
SCSI device reports unit attention on non-removable device
•
Unexpected SCSI bus reset occurs
•
Unexpected SCSI disconnect reported by a SCSI device
LED is blinking once per second.
Controls > Access Options > Virtual Private
171