The order for getting fibre channel based hypervolume extentions (HVEs) viewable on systems, particularly SUN systems, is as follows:
1. Appropriately zone so the Host Bus Adapter (HBA) can see the EMC Fibre Adapter (FA).
2. Reboot the system so it can see the vcm database disk on the FA OR
1. SUN:
1. drvconfig -i sd; disks; devlinks (SunOS <= 5.7)
2. devfsadm -i sd (SunOS >= 5.7 (w/patches))
2. HP:
1. ioscan -f # Note the new hw address
2. insf -e -H ${hw}
3. Execute vcmfind to ensure the system sees the Volume Logix database.
4. ID mapped informationi
1. Map HVEs to the FA if not already done.
2. symdev list -SA ${fa} to see what’s mapped.
3. symdev show ${dev} to ID the lun that ${dev} is mapped as. The display should look something like:
Front Director Paths (4):
{
———————————————————————————————–
POWERPATH DIRECTOR PORT
———————- —————– ————
PdevName Type Num Type Num Sts VBUS TID LUN
———————————————————————————————–
Not Visible N/A 03A FA 0 RW 000 00 70
Not Visible N/A 14A FA 0 NR 000 00 70
Not Visible N/A 03B FA 0 NR 000 00 70
Not Visible N/A 14B FA 0 NR 000 00 70
}
The number you’re looking for is under the column LUN. Remember, it’s HEX, so the lun that’ll show up on the ctd is (0×70=112) c#t#d112
5. On SUN systems, modify the /kernel/drv/sd.conf file so the system will see the new disks. You’ll need to do a reconfig reboot after modifying this file. If the system doesn’t see it on a reconfig reboot, this file is probably the culprit!
6. fpath adddev -w ${hba_wwn} -f ${fa} -r “${list_of_EMC_devs}”
You can specify multiple EMC device ranges; just separate them by spaces, not commas
7. Reboot the system so it can see the new disks on the FA OR
1. SUN:
1. drvconfig -i sd; disks; devlinks (SunOS <= 5.7)
2. devfsadm -i sd (SunOS >= 5.7 (w/patches))
2. HP:
1. ioscan -f # Note the new hw address
2. insf -e -H ${hw}
1. Appropriately zone so the Host Bus Adapter (HBA) can see the EMC Fibre Adapter (FA).
2. Reboot the system so it can see the vcm database disk on the FA OR
1. SUN:
1. drvconfig -i sd; disks; devlinks (SunOS <= 5.7)
2. devfsadm -i sd (SunOS >= 5.7 (w/patches))
2. HP:
1. ioscan -f # Note the new hw address
2. insf -e -H ${hw}
3. Execute vcmfind to ensure the system sees the Volume Logix database.
4. ID mapped informationi
1. Map HVEs to the FA if not already done.
2. symdev list -SA ${fa} to see what’s mapped.
3. symdev show ${dev} to ID the lun that ${dev} is mapped as. The display should look something like:
Front Director Paths (4):
{
———————————————————————————————–
POWERPATH DIRECTOR PORT
———————- —————– ————
PdevName Type Num Type Num Sts VBUS TID LUN
———————————————————————————————–
Not Visible N/A 03A FA 0 RW 000 00 70
Not Visible N/A 14A FA 0 NR 000 00 70
Not Visible N/A 03B FA 0 NR 000 00 70
Not Visible N/A 14B FA 0 NR 000 00 70
}
The number you’re looking for is under the column LUN. Remember, it’s HEX, so the lun that’ll show up on the ctd is (0×70=112) c#t#d112
5. On SUN systems, modify the /kernel/drv/sd.conf file so the system will see the new disks. You’ll need to do a reconfig reboot after modifying this file. If the system doesn’t see it on a reconfig reboot, this file is probably the culprit!
6. fpath adddev -w ${hba_wwn} -f ${fa} -r “${list_of_EMC_devs}”
You can specify multiple EMC device ranges; just separate them by spaces, not commas
7. Reboot the system so it can see the new disks on the FA OR
1. SUN:
1. drvconfig -i sd; disks; devlinks (SunOS <= 5.7)
2. devfsadm -i sd (SunOS >= 5.7 (w/patches))
2. HP:
1. ioscan -f # Note the new hw address
2. insf -e -H ${hw}
No comments:
Post a Comment