EMC: Volume Logix operations

Title:

EMC: Volume Logix operations

Author:

Douglas O’Leary <dkoleary@olearycomputers.com>

Description:

EMC: Volume Logix operations

Date created:

06/2001

Date updated:

07/2005

Disclaimer:

Standard: Use the information that follows at your own risk. If you screw up a system, don’t blame it on me…

The order for getting fibre channel based hypervolume extentions (HVEs) viewable on systems, particularly SUN systems, is as follows:

• Appropriately zone so the Host Bus Adapter (HBA) can see the EMC Fibre Adapter (FA).

• Reboot the system so it can see the vcm database disk on the FA OR

  • SUN:

    • `` drvconfig -i sd; disks; devlinks`` (SunOS <= 5.7)

    • devfsadm -i sd (SunOS >= 5.7 (w/patches))

  • HP:

    • ioscan -f # Note the new hw address

    • insf -e -H ${hw}

• Execute vcmfind to ensure the system sees the Volume Logix database.

• ID mapped informationi

  • Map HVEs to the FA if not already done.

  • symdev list -SA ${fa} to see what’s mapped.

  • 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 (0x70=112) c#t#d112

• 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!

• 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

• Reboot the system so it can see the new disks on the FA OR

  • SUN:

    drvconfig -i sd; disks; devlinks (SunOS <= 5.7)
    devfsadm -i sd (SunOS >= 5.7 (w/patches))
    

  • HP:

    ioscan -f # Note the new hw address
    insf -e -H ${hw}