That's it. Once you connect the interfaces on the SAN controller and configure the fc port, you should see it FLOGI in to the MDS.  So you can verify the WWPN via 'show flogi database' ... View more

Hi Jose, Very close Typically the SAN has the two controllers - but each port will have a different WWPN. So Controller A, port 1 will have a WWPN and then Controller A, port 2, will have a different WWPN Here is an example from my lab: MDS-A zone name grscarle-ESXi vsan 1000     member pwwn 20:00:00:25:b5:b5:03:3f  << UCS Blade vHBA-A     member pwwn 50:06:01:62:44:60:44:fa  << EMC SP-A1     member pwwn 50:06:01:6a:44:60:44:fa  << EMC SP-B1 MDS-B zone name grscarle-ESXi vsan 2000     member pwwn 20:00:00:25:b5:b5:03:2f << UCS Blade vHBA-Fabric-B     member pwwn 50:06:01:68:44:60:44:fa << EMC SP-B0     member pwwn 50:06:01:60:44:60:44:fa << EMC SP-A0 In this example, each MDS only has a *single* VSAN. ... View more

Hi Jose. Physically your connectivity is good. On the UCS side, the 'Primary' and 'Subordinate' role refer only to the Management of the system and which device is actually running UCS Manager. Each MDS device will have separate configuration (zoning).  It's different between the 2 devices. The blade itself will have a connection out each side, or 'SAN Fabric'. e.g.            +----+        +---+    +-----+        |   |    |     |        |   |    |     |        |   |SAN |     |        | +->----<--+  |        | |         |  |        | |         |  |    +---+-+-+    +--+--+--+    |       |    |        |    |MDS-A  |    |MDS-B   |    +--^-^--+    +---^-^--+       | |           | |    +--+-+--+    +---+-+--+    |       |    |        |    |UCS-A  |    | UCS-B  |    +--+----+    +-----+--+       |               |       |               | VSAN100    +-----+    | VSAN200       |    |     |    |       +---->     <----+            |Blade|            +-----+ The blade will have a HBA on FabricA (VSAN100) and FabricB (VSAN200) Each HBA will have a different WWPN, and on the SAN array, each controller will have a WWPN So on MDS-A, the zoning will be: Blade WWPN A Storage WWPN Primary A Storage WWPN Secondary A MDS-B, the zoning will be: Blade WWPN B Storage WWPN Primary B Storage WWPN Secondary B So the configuration is *not* synced between the two MDS devices, but they each have visibility to the blades vHBA device.  At the blade level, the Multipathing software on the Operating System will handle any failover. On the UCS, we would generally use a Port Channel up to the MDS. ... View more

Hi Michael, It sounds like you may be hitting a known bug : http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCto68104 I'd suggest raising a TAC case and we can apply the workaround to resolve the issue.  The process doesn't take too long for us to perform. ... View more

The UCS will be in FC Switching Mode, which means it has a default zone.  We cannot do a Zone Merge with the Brocade as we have no control to configure specific items such as Domain ID's and other FC items that need to be changed when connecting a Cisco FC Switch to a Brocade. Generally in this situation with a 5k or a MDS you would be putting them into InterOp mode, which changes default settings and let's them talk together - in this case we cannot change these parameters, so the only supported configuration is Cisco to Cisco FC. Cheers, Greg Scarlett. ... View more