One of the advantages of Solaris 10 FC drivers is that MPXio can present 1 target for the two paths. This feature is coming RSN to vxdmp. So consider disabling vxdmp and let native Solaris do the multipathing with "stmsboot -e".
================= Dana Hudes UNIX and Imaging group NYC-HRA MIS +1 718 510 8586 Nextel: 172*26*16684 ================= -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Asim Zuberi Sent: Wednesday, February 27, 2008 9:55 AM To: 'Sundaram Ramasamy'; veritas-vx@mailman.eng.auburn.edu Subject: Re: [Veritas-vx] Issue with EMC SAN LUN Multipath Hi SR -- I don't see this as an issue. Apparently, you have two controllers (HBAs) on the host. At OS level, they show-up as "c43" and "c35". The target "t18" is what you have defined in the "sd.conf" file. The disk "d27" is the assigned from the SAN. It is the same disk across each controllers. That's why you only had to labeled once on one path and not on both paths. Do "vxdisk -e list" and see if this disk "d27" is displayed twice? Hope this helps, --Asim; _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sundaram Ramasamy Sent: Tuesday, February 26, 2008 6:17 PM To: veritas-vx@mailman.eng.auburn.edu Subject: [Veritas-vx] Issue with EMC SAN LUN Multipath Hi all, We are adding new ECM SYMMETRIX LUN our Solaris 9 server. According to SAN team LUN's zoned and masked for this host with two paths. We updated lpfc.conf and sd.conf rebooted the server. We are able to see this LUNs in format. If we make the label change on one path we are able to view it on other path. The problem is its giving different serial number on each path. Since serial number is different Veritas thinks its two different disks. We check with Storage engineers, they said configuration looks good on their side. We don't have access to SAN configuration. We can run SYMCLI commands from host. I would like to know why we are getting different serial number for same disk. Where the configuration mismatches server side or host side?. Can we use SYMCLI command to check SAN configuration? If problem with SAN side, what information I need ask SAN engineers to check? Any troubleshooting tips will help. Here some more information. First path: ======= HBA: ....3f1 Sym Dev LUN Name Dir:P Physical Device Name VBUS TID SYMM HOST Attr Cap(MB) ------ ----- ----------------------- ---- --- ---- ---- ---- ------- 0721 14B:1 /dev/vx/rdmp/c43t18d27s2 0 0 1b 1b 30468 Second path: ========= HBA: ....64d2 Sym Dev LUN Name Dir:P Physical Device Name VBUS TID SYMM HOST Attr Cap(MB) ------ ----- ----------------------- ---- --- ---- ---- ---- ------- 0721 3B:1 /dev/vx/rdmp/c35t18d27s2 0 0 1b 1b 30468 Inquiry for /dev/rdsk/c43t18d27s2, evpd 0x0, page code 0x0 Vendor id : EMC Product id : SYMMETRIX Revision : 5771 Serial Number : 17721301Q Inquiry for /dev/rdsk/c35t18d27s2, evpd 0x0, page code 0x0 Vendor id : EMC Product id : SYMMETRIX Revision : 5771 Serial Number : 17721191Q Thanks -SR
_______________________________________________ Veritas-vx maillist - Veritas-vx@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
