Home.... | log in.... | Pub my question! | Sign-up....
Java-index >> Storage Forums >> Storage General Discussion

StorEdge Traffic Manger and EMC Symmetrix

Hey all. I've read the Traffic Manager docs and done online searches, but can find very little detail about connecting a SunFire 280R running Solaris 9 to an EMC Symmetrix, using 2 Emulex HBAs, and using Traffic Manager to handle failover.

I've installed the Traffic Manager (TM) packages and the required patches for TM, and made many different modifications to /kernel/drv/scsi_vhci.conf but I still can't get TM to combine the paths as advertised.

I've ran the inq command EMC provides and the Vendor ID comes back as EMC and the Product ID comes back as SYMMETRIX. In the docs it says that VID must be 5 characters and PID 8 characters. I've tried various combinations of EMC and SYMMETRIX and spaces and such, but still, no worky.

One thing I've noticed is that every reference I've found to TM always mentions QLogic HBAs. Is that the only HBA that TM supports? Has anyone successfully used TM to connect to an EMC Symm and provide failover?

Help please!

Bob Jones

[1022 byte] By [OneTrueBob] at [2007-11-25 23:16:25]
«« Anyone had connect SE3960 to a Redhat Linux ?
»» Solaris version that RAID Manager 6.22.1 supported
# 1

We have an EMC Clarion, & I asked our Sun SE about the Traffic Manager, and I was told that TM only supports Sun HBAs & switches & arrays. So, we're planning to get & use EMC PowerPath s/w which handles failover. IIRC, the PowerPath s/w isn't *too* expensive per system. And,I think that EMC is having a special on PP training, free WBT PowerPath training. Shouldn't be too hard. HTH.

curmudge1 at 2007-7-5 18:05:17 > top of Java-index,Storage Forums,Storage General Discussion...
# 2

I would like to know if you were able to use MPXIO on 3rd party devices like an EMC?

Sun has not been too helpful on helping to configure MPXIO on an EMC symmetrics.

My Config:

# echo | format >> /users.support.out

Searching for disks...done

c5t50060482CCB4A449d0: configured with capacity of 21.56MB

c6t50060482CCB4A446d0: configured with capacity of 21.56MB

AVAILABLE DISK SELECTIONS:

0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>

/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e74293,0

1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>

/pci@8,600000/SUNW,qlc@4/fp@0,0/ssd@w2100002037e73dba,0

2. c2t2d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>

/pci@8,700000/scsi@6,1/sd@2,0

3. c2t3d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>

/pci@8,700000/scsi@6,1/sd@3,0

4. c5t50060482CCB4A449d0 <EMC-SYMMETRIX-5670 cyl 46 alt 2 hd 15 sec 64>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w50060482ccb4a449,0

5. c5t50060482CCB4A449d24 <EMC-SYMMETRIX-5670 cyl 36826 alt 2 hd 30 sec 64>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w50060482ccb4a449,18

6. c5t50060482CCB4A449d25 <EMC-SYMMETRIX-5567 cyl 36822 alt 2 hd 15 sec 64>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w50060482ccb4a449,19

7. c5t50060482CCB4A449d26 <EMC-SYMMETRIX-5670 cyl 36826 alt 2 hd 30 sec 64>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w50060482ccb4a449,1a

8. c5t50060482CCB4A449d27 <EMC-SYMMETRIX-5670 cyl 36826 alt 2 hd 30 sec 64>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w50060482ccb4a449,1b

9. c5t5006016110601B9Fd0 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016110601b9f,0

10. c5t5006016910601B9Fd0 <drive type unknown>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016910601b9f,0

11. c5t5006016910601B9Fd1 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016910601b9f,1

12. c5t5006016110601B9Fd1 <drive type unknown>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016110601b9f,1

13. c5t5006016910601B9Fd2 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016910601b9f,2

14. c5t5006016110601B9Fd2 <drive type unknown>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016110601b9f,2

15. c5t5006016110601B9Fd3 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016110601b9f,3

16. c5t5006016910601B9Fd3 <drive type unknown>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016910601b9f,3

17. c5t5006016110601B9Fd4 <drive type unknown>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016110601b9f,4

18. c5t5006016910601B9Fd4 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016910601b9f,4

19. c5t5006016110601B9Fd5 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016110601b9f,5

20. c5t5006016910601B9Fd5 <drive type unknown>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016910601b9f,5

21. c5t5006016110601B9Fd6 <drive type unknown>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016110601b9f,6

22. c5t5006016910601B9Fd6 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@1/fp@0,0/ssd@w5006016910601b9f,6

23. c6t50060482CCB4A446d0 <EMC-SYMMETRIX-5670 cyl 46 alt 2 hd 15 sec 64>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w50060482ccb4a446,0

24. c6t50060482CCB4A446d24 <EMC-SYMMETRIX-5670 cyl 36826 alt 2 hd 30 sec 64>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w50060482ccb4a446,18

25. c6t50060482CCB4A446d25 <EMC-SYMMETRIX-5567 cyl 36822 alt 2 hd 15 sec 64>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w50060482ccb4a446,19

26. c6t50060482CCB4A446d26 <EMC-SYMMETRIX-5670 cyl 36826 alt 2 hd 30 sec 64>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w50060482ccb4a446,1a

27. c6t50060482CCB4A446d27 <EMC-SYMMETRIX-5670 cyl 36826 alt 2 hd 30 sec 64>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w50060482ccb4a446,1b

28. c6t5006016010601B9Fd0 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016010601b9f,0

29. c6t5006016810601B9Fd0 <drive type unknown>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016810601b9f,0

30. c6t5006016010601B9Fd1 <drive type unknown>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016010601b9f,1

31. c6t5006016810601B9Fd1 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016810601b9f,1

32. c6t5006016010601B9Fd2 <drive type unknown>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016010601b9f,2

33. c6t5006016810601B9Fd2 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016810601b9f,2

34. c6t5006016010601B9Fd3 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016010601b9f,3

35. c6t5006016810601B9Fd3 <drive type unknown>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016810601b9f,3

36. c6t5006016010601B9Fd4 <drive type unknown>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016010601b9f,4

37. c6t5006016810601B9Fd4 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016810601b9f,4

38. c6t5006016010601B9Fd5 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016010601b9f,5

39. c6t5006016810601B9Fd5 <drive type unknown>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016810601b9f,5

40. c6t5006016810601B9Fd6 <DGC-RAID5-0205 cyl 35796 alt 2 hd 128 sec 14>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016810601b9f,6

41. c6t5006016010601B9Fd6 <drive type unknown>

/pci@8,700000/SUNW,qlc@2/fp@0,0/ssd@w5006016010601b9f,6

Specify disk (enter its number): Specify disk (enter its number):

# cfgadm -al

Ap_Id Type ReceptacleOccupantCondition

c0scsi-busconnectedconfiguredunknown

c0::dsk/c0t6d0CD-ROMconnectedconfiguredunknown

c1fc-privateconnectedconfiguredunknown

c1::2100002037e73dbadisk connectedconfiguredunknown

c1::2100002037e74293disk connectedconfiguredunknown

c2scsi-busconnectedconfiguredunknown

c2::dsk/c2t2d0disk connectedconfiguredunknown

c2::dsk/c2t3d0disk connectedconfiguredunknown

c2::rmt/0 tape connectedconfiguredunknown

c5fc-fabricconnectedconfiguredunknown

c5::5006016110601b9fdisk connectedconfiguredunknown

c5::5006016910601b9fdisk connectedconfiguredunknown

c5::50060482ccb4a449disk connectedconfiguredunknown

c6fc-fabricconnectedconfiguredunknown

c6::5006016010601b9fdisk connectedconfiguredunknown

c6::5006016810601b9fdisk connectedconfiguredunknown

c6::50060482ccb4a446disk connectedconfiguredunknown

c7fcconnectedunconfigured unknown

c8fcconnectedunconfigured unknown

c9fcconnectedunconfigured unknown

c10fcconnectedunconfigured unknown

# luxadm qlgc >> /users.support.out

Found Path to 3 FC100/P, ISP2200, ISP23xx Devices

Opening Device: /devices/pci@8,700000/SUNW,qlc@1/fp@0,0:devctl

Detected FCode Version:ISP2300 Host Adapter Driver: 1.14.01 12/20/02

Opening Device: /devices/pci@8,700000/SUNW,qlc@2/fp@0,0:devctl

Detected FCode Version:ISP2300 Host Adapter Driver: 1.14.01 12/20/02

Opening Device: /devices/pci@8,600000/SUNW,qlc@4/fp@0,0:devctl

Detected FCode Version:ISP2200 FC-AL Host Adapter Driver: 1.14 01/11/20

Complete

# luxadm probe

No Network Array enclosures found in /dev/es

Found Fibre Channel device(s):

Node WWN:2000002037e74293 Device Type:Disk device

Logical Path:/dev/rdsk/c1t0d0s2

Node WWN:2000002037e73dba Device Type:Disk device

Logical Path:/dev/rdsk/c1t1d0s2

Node WWN:50060482ccb4a449 Device Type:Disk device

Logical Path:/dev/rdsk/c5t50060482CCB4A449d0s2

Node WWN:50060482ccb4a449 Device Type:Disk device

Logical Path:/dev/rdsk/c5t50060482CCB4A449d24s2

Node WWN:50060482ccb4a449 Device Type:Disk device

Logical Path:/dev/rdsk/c5t50060482CCB4A449d25s2

Node WWN:50060482ccb4a449 Device Type:Disk device

Logical Path:/dev/rdsk/c5t50060482CCB4A449d26s2

Node WWN:50060482ccb4a449 Device Type:Disk device

Logical Path:/dev/rdsk/c5t50060482CCB4A449d27s2

Node WWN:5006016090601b9f Device Type:Disk device

Logical Path:/dev/rdsk/c5t5006016110601B9Fd0s2

Logical Path:/dev/rdsk/c5t5006016910601B9Fd0s2

Logical Path:/dev/rdsk/c6t5006016810601B9Fd0s2

Logical Path:/dev/rdsk/c6t5006016010601B9Fd0s2

Node WWN:5006016090601b9f Device Type:Disk device

Logical Path:/dev/rdsk/c5t5006016110601B9Fd1s2

Logical Path:/dev/rdsk/c5t5006016910601B9Fd1s2

Logical Path:/dev/rdsk/c6t5006016010601B9Fd1s2

Logical Path:/dev/rdsk/c6t5006016810601B9Fd1s2

Node WWN:5006016090601b9f Device Type:Disk device

Logical Path:/dev/rdsk/c5t5006016910601B9Fd2s2

Logical Path:/dev/rdsk/c5t5006016110601B9Fd2s2

Logical Path:/dev/rdsk/c6t5006016010601B9Fd2s2

Logical Path:/dev/rdsk/c6t5006016810601B9Fd2s2

Node WWN:5006016090601b9f Device Type:Disk device

Logical Path:/dev/rdsk/c5t5006016110601B9Fd3s2

Logical Path:/dev/rdsk/c5t5006016910601B9Fd3s2

Logical Path:/dev/rdsk/c6t5006016010601B9Fd3s2

Logical Path:/dev/rdsk/c6t5006016810601B9Fd3s2

Node WWN:5006016090601b9f Device Type:Disk device

Logical Path:/dev/rdsk/c5t5006016110601B9Fd4s2

Logical Path:/dev/rdsk/c5t5006016910601B9Fd4s2

Logical Path:/dev/rdsk/c6t5006016010601B9Fd4s2

Logical Path:/dev/rdsk/c6t5006016810601B9Fd4s2

Node WWN:5006016090601b9f Device Type:Disk device

Logical Path:/dev/rdsk/c5t5006016110601B9Fd5s2

Logical Path:/dev/rdsk/c5t5006016910601B9Fd5s2

Logical Path:/dev/rdsk/c6t5006016010601B9Fd5s2

Logical Path:/dev/rdsk/c6t5006016810601B9Fd5s2

Node WWN:5006016090601b9f Device Type:Disk device

Logical Path:/dev/rdsk/c5t5006016110601B9Fd6s2

Logical Path:/dev/rdsk/c5t5006016910601B9Fd6s2

Logical Path:/dev/rdsk/c6t5006016810601B9Fd6s2

Logical Path:/dev/rdsk/c6t5006016010601B9Fd6s2

Node WWN:50060482ccb4a446 Device Type:Disk device

Logical Path:/dev/rdsk/c6t50060482CCB4A446d0s2

Node WWN:50060482ccb4a446 Device Type:Disk device

Logical Path:/dev/rdsk/c6t50060482CCB4A446d24s2

Node WWN:50060482ccb4a446 Device Type:Disk device

Logical Path:/dev/rdsk/c6t50060482CCB4A446d25s2

Node WWN:50060482ccb4a446 Device Type:Disk device

Logical Path:/dev/rdsk/c6t50060482CCB4A446d26s2

Node WWN:50060482ccb4a446 Device Type:Disk device

Logical Path:/dev/rdsk/c6t50060482CCB4A446d27s2

# cat /kernel/drv/scsi_vhci.conf

# Copyright 2001-2003 Sun Microsystems, Inc. All rights reserved.

# Use is subject to license terms.

#

#pragma ident"@(#)scsi_vhci.conf1.1003/11/13 SMI"

#

name="scsi_vhci" class="root";

#

# mpxio Global enable/disable configuration

# possible values are mpxio-disable="no" or mpxio-disable="yes"

#

mpxio-disable="no";

#

# Load Balancing global configuration

# possible values are load-balance="none" or load-balance="round-robin"

#

load-balance="round-robin";

#

# Automatic failback configuration

# possible values are auto-failback="enable" or auto-failback="disable"

auto-failback="disable";

#

# For enabling MPxIO support for 3rd party symmetric device need an

# entry similar to following in this file. Just replace the "SUNSENA"

# part with the Vendor ID/Product ID for the device, exactly as reported by

# Inquiry cmd.

#

# device-type-scsi-options-list =

# "SUNSENA", "symmetric-option";

#

# symmetric-option = 0x1000000;

#

#device-type-scsi-options-list =

#"SUNStorEdge 3510", "symmetric-option";

#symmetric-option = 0x1000000;

#

device-type-scsi-options-list =

"EMCSYMMETRIX 5670", "symmetric-option";

symmetric-option = 0x1000000;

FAUSA at 2007-7-5 18:05:17 > top of Java-index,Storage Forums,Storage General Discussion...
# 3

I know this is a bit late and probably too late. I happen to stumble across this thread.

Traffic Manager (aka MPxIO) does in fact support EMC or rather EMC supports TM on Symmetrix.

The catch is, you must be using either QLogic or JNI cards running Sun's SAN Foundation software (think drivers). As far as I know, Emulex is not currently supported. My guess is the HBAs are cheaper than PP.

So if you are having problems, EMC support should be your next call. The deal is, Sun is willing to make TM work w/ any third-party vendors storage, as long as they provide the configuration/first line support.

Regards.

dgdoami at 2007-7-5 18:05:17 > top of Java-index,Storage Forums,Storage General Discussion...
# 4

This may also be helpful...

I have seen so much grief concerning editing the scsi_vhci.conf file, and have bee pretty well beaten up by editing it to accept my 3rd party disks.

In the IBM docs, it very specifically states "there are 5 trailing blanks spaces between vendor name and model". Couldn't find that ANYWHERE in a SUN doc...but anyway....

I have fouind out that if I do not have exactly 5 spaces, it will NEVER reconize a different disks, or place it under scsi_vhci's control...

What a mind-bender.

SAN_shrink at 2007-7-5 18:05:17 > top of Java-index,Storage Forums,Storage General Discussion...
# 5
Adding one small note of clarification...The Device type MUST be 8 chars long...for the example "SUN" or "IBM", you have to follow those 3 chars with 5 blank spaces as filler.Model can be up to 16 chars.(whew)
SAN_shrink at 2007-7-5 18:05:17 > top of Java-index,Storage Forums,Storage General Discussion...
# 6

An other clarification.......or two or three.

1) Look to the third party vendors for the "is this supported" info. The way the storage biz works, for some reason, is that the array vendor gets to qual the hba, drivers, mp software, etc. EMC and some others have Traffic Manager on their qual lists.

2) The instructions to edit the scsi_vhic.conf file should also come from the vendors. They know the correct vendor and inq sting to use....though you can get it from the OS as well.

3) They aren't Qlogic or JNI Hbas with Sun drivers. They are Sun HBAS, sourced via Qlogic of AMCC, that run Sun drivers. The devil is in the semantics. ;)

tmcmahon2 at 2007-7-5 18:05:17 > top of Java-index,Storage Forums,Storage General Discussion...
Storage General Discussion

Storage Forums New Topic

Storage Forums Hot Topic

Storage Forums

All Classified