Setting up shared storage: SCSI
| Article:HOWTO77040 | | | Created: 2012-05-23 | | | Updated: 2012-05-24 | | | Article URL http://www.symantec.com/docs/HOWTO77040 |
Perform the following steps to set up shared storage.
SCSI adapters are typically set with a default identifier value of 7. Each device on a SCSI bus must have a unique SCSI identifier value. When more than one system is connected to a SCSI bus, you must change the SCSI identifier to a unique number. You must make this change to one or more systems, usually the unique number is 5 or 6.
Perform the procedure if you want to connect to shared storage with shared SCSI devices.
To set the SCSI identifier value on AIX
Determine the SCSI adapters on each system:
north # lsdev -C -c adapter | grep scsi scsi0 Available 11-08 Wide/Ultra-2 SCSI I/O Controller scsi1 Available 11-09 Wide/Ultra-2 SCSI I/O Controller south # lsdev -C -c adapter | grep scsi scsi0 Available 11-08 Wide/Ultra-2 SCSI I/O Controller scsi1 Available 11-09 Wide/Ultra-2 SCSI I/O Controller
Verify the SCSI ID of each adapter:
north # lsattr -E -l scsi0 -a id id 7 Adapter card SCSI ID True north # lsattr -E -l scsi1 -a id id 7 Adapter card SCSI ID True south # lsattr -E -l scsi0 -a id id 7 Adapter card SCSI ID True south # lsattr -E -l scsi1 -a id id 7 Adapter card SCSI ID True
If necessary, change the SCSI identifier on each system so that it is unique:
south # chdev -P -l scsi0 -a id=5 scsi0 changed south # chdev -P -l scsi1 -a id=5 scsi1 changed
Cable the shared storage as illustrated in Figure: Cabling the shared storage.
Restart each system. After all systems have booted, use the lspv command to verify that each system can see all shared devices needed by the application.
To set up shared storage on HP-UX
Install the required SCSI host bus adapters and set up the external shared SCSI storage devices.
Cable the external shared storage devices. With cables connected to shared storage between two systems, you must terminate the two ends of the SCSI bus on the systems as shown in the Figure: Cabling the shared storage.
For more than two systems, disable SCSI termination on the systems that are not positioned at the ends of the SCSI chain.
To set up shared storage on Linux
Boot the system. The disk is detected while the system boots.
Press CTRL+A to bring up the SCSI BIOS settings for that disk.
Format the shared disk and create required partitions on it.
Perform the following:
Identify your shared disk name. If you have two internal SCSI hard disks, your shared disk is
/dev/sdc.# fdisk /dev/shareddiskname
For example, if your shared disk is
sdc, type:# fdisk /dev/sdc
Create disk groups and volumes using Volume Manager utilities.
To apply a file system on the volumes, type:
# mkfs -t fs-type /dev/vx/dsk/disk-group/volume
For example, enter the following command:
# mkfs -t vxfs /dev/vx/dsk/dg/vol01
Where the name of the disk group is
dg, the name of the volume isvol01, and the file system type isvxfs.
Remove the terminator from the disk and connect the disk to the other cluster system.
Press Ctrl+A to bring up the SCSI BIOS settings for the disk.
Verify that you can view the shared disk using the fdisk command.
When SCSI devices are used for shared storage, the SCSI address or SCSI initiator ID of each node must be unique. Since each node typically has the default SCSI address of "7," the addresses of one or more nodes must be changed to avoid a conflict. In the following example, two nodes share SCSI devices. The SCSI address of one node is changed to "5" by using nvedit commands to edit the nvramrc script.
To set up shared storage on Solaris
Install the required SCSI host adapters on each node that connects to the storage, and make cable connections to the storage.
Refer to the documentation that is shipped with the host adapters, the storage, and the systems.
Power on one system, but do not allow it to boot. If necessary, halt the system so that you can use the ok prompt.
Note that only one system must run at a time to avoid address conflicts.
Find the paths to the host adapters:
{0} ok show-disks ...b) /sbus@6,0/QLGC,isp@2,10000/sdThe example output shows the path to one host adapter. You must include the path information without the "/sd" directory, in the nvramrc script. The path information varies from system to system.
Edit the nvramrc script on to change the scsi-initiator-id to 5. (The Solaris OpenBoot 3.x Command Reference Manual contains a full list of nvedit commands and keystrokes.) For example:
{0} ok nveditIn this example, edit the nvramrc script as follows:
0: probe-all 1: cd /sbus@6,0/QLGC,isp@2,10000 2: 5 " scsi-initiator-id" integer-property 3: device-end 4: install-console 5: banner 6: <CTRL-C>
Store the changes you make to the nvramrc script. The changes you make are temporary until you store them.
{0} ok nvstoreIf you are not sure of the changes you made, you can re-edit the script without risk before you store it. You can display the contents of the nvramrc script by entering:
{0} ok printenv nvramrcYou can re-edit the file to make corrections:
{0} ok nveditOr, discard the changes if necessary by entering:
{0} ok nvquitInstruct the OpenBoot PROM Monitor to use the nvramrc script on the node.
{0} ok setenv use-nvramrc? trueReboot the node. If necessary, halt the system so that you can use the ok prompt.
Verify that the scsi-initiator-id has changed. Go to the ok prompt. Use the output of the show-disks command to find the paths for the host adapters. Then, display the properties for the paths. For example:
{0} ok show-disks ...b) /sbus@6,0/QLGC,isp@2,10000/sd {0} ok cd /sbus@6,0/QLGC,isp@2,10000 {0} ok .properties scsi-initiator-id 00000005Boot the second node. If necessary, halt the system to use the ok prompt. Verify that the scsi-initiator-id is 7. Use the output of the show-disks command to find the paths for the host adapters. Then, display the properties for that paths. For example:
{0} ok show-disks ...b) /sbus@6,0/QLGC,isp@2,10000/sd {0} ok cd /sbus@6,0/QLGC,isp@2,10000 {0} ok .properties scsi-initiator-id 00000007
|
|
Legacy ID
uxrt-60_v74034983_v73071783
Article URL http://www.symantec.com/docs/HOWTO77040
Terms of use for this information are found in Legal Notices










Thank you.