Improved zoning (MDS-6248)

Similar Questions

• Only initiator zones with different targets

  Possible to have a single identical HBA initiator according to the different areas on an SDM with different targets in each area? or an initiator can only log into the area under one?

  Is below allowed on the MDS as well as the same vsan?

  zone name VM005_S05_C1_TO_VNX5300_SPA0_SPA1_SPB0_SPB1 vsan 10
  Member pwwn 20:01:b4:e1:0f:28:02:0 d init
  ! [VM005_S05_C1]
  Member pwwn 50:06:01:60:3e:e0:2 target: f2
  ! [VNX5300_SPA0]
  Member pwwn 50:06:01:61:3e:e0:2 target: f2
  ! [VNX5300_SPA1]
  Member pwwn 50:06:01:68:3e:e0:2 target: f2
  ! [VNX5300_SPB0]
  Member pwwn 50:06:01:69:3e:e0:2 target: f2
  ! [VNX5300_SPB1]

  zone name VM005_S05_C1_TO_VNX5400_SPA2_SPB2 vsan 10
  Member pwwn 20:01:b4:e1:0f:28:02:0 d init
  ! [VM005_S05_C1]
  Member pwwn 50:06:01:62:36:e0:14:2d target
  ! [VNX5400_SPA2]
  Member pwwn 50:06:01:6 target: 36:e0:14:2d
  ! [VNX5400_SPB2]

  If you use device aliases? fix?

  Do you use the improved zoning?

  Maybe you should do a

  "commit vsan 10.

  and finally, you also need to enable the zonset!

  BTW. you see error messages, while sticking to this list of 5300 areas?

  SSM

  Take a look at the "show running" and you see how areas and whole areas are configured and activated

• Fabric 6248 with MDS

  Hi all

  We are at the stage of inter-connecting simple IBM V3700 SAN box with double FI 6248 (redundant) via unique Cisco MDS 9000 SAN Switch with single UCS 5108 chasis.

  We have four blades B200 M3 in UCS 5108. The blades have no local hard disks. Our requirement is to install hyperV/Windows on IBM storage.

  I did the physical connections between IBM and MDS & MDS FI 6248 and FI 6248 dual Core 6509 VSS enabled.

  I don't have issues with part FI 6248 and LAN, I have doubts about FI 6248 with SAN kindly advise.

  6248 FI are default mode (Host End). I need to change FI on switch mode?
  I change ports Uplink FC, unified FI ports connected to the MDS are configured as storage CF?
  How vNIC, vSAN (vSAN how do I need), vHBA & Service profile works to each other? can any advise please?
  What steps do we need to set up in FI & MDS so that we can use SAN storage for hyperV/Windows installation?

  It's my first deployment of the UCS 5108, to apologize to ask fundamental questions.

  Kind regards

  1. what would be the impact of multiple VSANS vs default vSAN, I plan to use default vSan in the two FI-6248 & I can't find any problem with this, please advise.

  Please do not use default vsan (vsan nr or 1); best practices: create different VSAN fabric A and B; e.g. vsan 10A, vsan 20 b

  2 - pool WWPN, should I create two different WWPN pool 1 for FI-6248-A & others for FI-6248-B? I have only a UCS 5108 chasis, we cannot set an unique WWPN for the two FI-6248 Pool? What is the best practice? I can't find any problem with single WWPN pool. Please advise.

  Best practices: use pools of different pwwn to fabric A and B; useful for troubleshooting; in General: all pools must also encode a field id UCS (your starting with 1). just in case in the future, you have another! See attachment.

  3 - incase, if I will configure 1 WWPN pool would I face any problem in mapping the area in MDS? According to my understanding there will be no problem because the area is just the initiator (Server Blade) mapping & target (IBM Storage). Keep in mind, I only Cisco MDS SAN Switch NOT redundant. Please advise.

  Even with an SDM, you create a virtual double fabric with 10 and 20 VSANs. zoning is done by VSANs, zones and activation as well!

  what adapter policy 4 - Creating Service profile should I choose in the menu Dynamics vNIC? I want to install Windows on Hyper V environment, but I'm not hyper V option. It has linux, VMWare, VMWare passthrough, window, default & some HyperV more but not?

  You do not create dynamic vNIC! This only applies to the VM - FEX, resp. SR - IOV. Hyper-V means political adapter = window

  Good luck

  Walter.

• 6248 fabric interconnects FC interfaces and MDS ports license

  Hello

  I need help. I need to configure port-channel of CF between 2 x 9148 MDS and 2 x Cisco fabric interconnects. My main problem here is interfaces CF appear not on the fabric of interconnections (UCS Manager). I don't see ethernet ports. I have to turn on the unified ports or do I license for CF?

  I also connected the ds-sfp-fc8g-sw FPS but I get the error "operation status failed, reason: SFP Validation failed.

  Another thing, all 48 FC ports on switches DMS 9148 acquire the license. Aren't they supposed to come with 16 ports enabled by default?

  Any ideas?

  Hi Selby

  6248 FI unified ports, by default, all are Ethernet; so as a first step, you must configure the FC ports.

  You just need Ethernet port licenses, which are also universal.

  See, for example.

  https://supportforums.Cisco.com/message/3763853#3763853

  For SDM 9148 licenses take a look on

  http://www.Cisco.com/c/en/us/products/collateral/storage-networking/MDS-9148-multilayer-fabric-switch/data_sheet_c78-571411.html

  There are packages with

  Cisco MDS 9148 48 - Port Multilayer Fabric Switch with 16, 32 or 48 active ports of 8 Gbps

  Good luck

• If we improve FI 6296UP UCS 3.1, what version of the firmware for our 9148 MDS is interoperable?

  We are looking at upgrading our UCS UCS 3.1 environment.

  We currently organize UCS 2.2 (3 c) on our FIs of 6296UP, and our 9148 MDS switches are currently on firmware 6.2(5a)

  If we improve UCS to 3.1 (1e) or 3.1(1g), how do we find what MDS firmware version will work best for us?

  Interoperability matrices I found so far indicate what firmware and drivers for the HBA/CNA adapter to use, but seem to not very specific with what MDS switch firmware version to use with which version of the UCS.

  Is this something that Cisco has no guidance on?

  Hi, DQ.

  If you look at the link (table 1-4) this should help show what MDS firmware below works better with respect to UCS;

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/MDS9000/Interop...

  It says expressly "NX - OS 6.x and higher of table 1-1" which is on Page 7 and 8 of the guide above.

  Please note and mark the correct answers to other users can find specific solutions easier.

  Hope this helps,

  Qiese Sa'di

• Unable to see FLOGI database on MDS 9148

  Hello

  Just found out with strange problem

  

  In above scenairo I can't see my on switch MDS 9148 WWN blades where I see WWN on Nexus 5548

  Please help me solve this problem

  Kind regards

  Amit Vyas

  Hi Amit

  Which manifest the flogi by going on fc 1/29 and 1/30?

  Your problem is clear: it is a routing problem? How for example a pwwn to the initiator. in 100 VSAN decide, on which port it should go north?

  The solution:

  Create 2 other VSANS, for example, 102 and 103; 100/101 will be used to reach N5k, 102/103 join MDS; of course, you need 2 additional vhba, one in 102, 103 RESP.

  I hope you did your zoning with device-alias (improved); so this change will be easy.

  Another ugly solution would be to use groups of static ping, which is hardly used, a management and a nightmare of scalabilty and therefore not recommended.

  Good luck

  Walter.

• VLAN function 6248 switch IP address

  We have a nice and simple class C private address space private on 4 x Dell 6248 switches. We are running out of IP addresses. We could change the netmask (add more bits), but who is to reach each node and potentially finding devices that do not work with anything other than 24. We have a lot of old material that we must keep functioning. In addition, we want to limit emissions, since here we have projects that do a lot of UDP broadcasts. If each project in one VLAN, the load on the switches would be less. Hosts on VLANS must get to the common servers well.

  So I did some reading and thought we would use of VLANS, routing and others to have several C class spaces. We turn the material around the office at an alarming rate so I thought that an IP based VLAN would be an excellent solution. I have problems with the documentation and configuration to make it work.

  We have 2 x 2716 Dell and 2 x Dell 2724 switches in the mix as well. They are connected to the 6248 s switches dumb and all seems to work now.

  I created 2 VLAN and reports the following:

  Curetes #show ip interface vlan 2

  State of the Routing Interface... Down
  Primary IP address... 192.168.3.1/255.255.255.0
  Routing mode... Enable
  Administrative mode... Enable
  NET before realized emissions... Disable
  Proxy ARP...................................... Enable
  Local Proxy ARP... Disable
  Statement of assets... Inactive
  MAC address... 0019.B998. E71E
  Type of encapsulation... Ethernet
  IP MTU......................................... 1500
  Bandwidth...................................... 10000 Kbps
  Destination unreachable... Activated
  ICMP redirects... Activated

  I am running firmware V3.3.3.3. I have improved the switches on the weekend of 2.2.0.3 I read that VLAN does work well with this version.

  I can't find in the documentation "Setup Guide" or "CLI_EN.pdf" how to get the "Routing Interface status" that up to.

  My config running is pretty simple:

  ! Current configuration:
  ! Description of the system "PowerConnect 6248, 3.3.3.3, VxWorks 6.5.
  ! 3.3.3.3 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 2-3, 10-11
  VLAN 2 1 routing
  VLAN 3 2 routing
  subnet of VLAN association 192.168.3.0 255.255.255.0 2
  output
  hostname "curetes.
  Select the SNTP client distribution
  192.139.238.68 SNTP server
  battery
  1 2 Member
  2 2 Member
  3 2 Member
  4 2 Member
  output

  IP 192.139.238.79 255.255.255.0
  default IP gateway - 192.139.238.27
  IP routing
  interface vlan 2
  name '192-168-3-x-address. "
  Routing
  address 192.168.3.1 IP 255.255.255.0
  output
  interface vlan 3
  Routing
  output
  level XXXXXXXXXXXXXXXXXXX username 'admin' password encrypted 15
  output

  Question (in order of importance):

  What is the best way to go to solve my problem (limit/exhaustion of Ip address space broadcast domain)?

  How to make "Routing Interface Status" on VLAN 2 upward? Do I need it upward?

  How to configure a VLAN to do what I want?

  Thanks in advance.

  Don

  Yes, that's my suggestion.

• Can not do anything on the VLAN ping on 6248

  Hello

  I've spent a day and a half trying to solve this problem, but I'm not getting anywhere. Here is a breakdown of the test configuration database.

  Port 1: Connected to the existing network (if I can get to the host ESXi from my PC)
  : 3 my ESXi host is connected to this
  Virtual machines are tag VLAN through port ESXi group properties.
  All VLANS have 1 VM except VLAN 10, which has 2.
  All the VLANS are IP address ending with 24 par.1 the subnet mask.
  All virtual machines have the corresponding default gateway pointing to the IP of the VLAN (XXX1)
  I am able to get the IP address of the DHCP server to different VLANS.

  Things that work:
  From a virtual machine, I can ping to IP of any VLAN (so MV in VLAN 10 can ping IP of the VLAN 20)
  The console, I can ping IP of any VLAN

  Things that DON'T work:
  The console, I cannot ping any computer virtual IP.
  From a virtual machine, I can not ping any address (including the virtual machines in the same VLAN)

  Here is my config running:

  ! Current configuration:
  ! Description of the system "PowerConnect 6248, 3.3.7.3, VxWorks 6.5.
  ! 3.3.7.3 system software version
  ! Passage mode is configured as disabled
  !
  Configure
  database of VLAN
  VLAN 10,20,30,40,50,300
  VLAN 10 1 routing
  VLAN 20 2 routing
  VLAN 30 3 routing
  VLAN routing 40 4
  VLAN 50 5 routing
  VLAN routing 300 6
  output
  unicast SNTP client enable
  customer survey SNTP 1024 timer
  SNTP server 0.north - america.pool.ntp.org
  clock timezone-7 minutes 0
  battery
  1 2 Member

  output
  IP 192.168.8.250 255.255.255.0
  default IP gateway - 192.168.8.230
  IP routing
  IP helper-address 10.80.10.10 dhcp
  interface vlan 10
  name 'server '.
  Routing
  IP 10.80.10.1 255.255.255.0
  output
  interface vlan 20
  name "printer - Switch."
  Routing
  IP 10.80.20.1 255.255.255.0
  IP helper 10.80.10.10
  output
  interface vlan 30
  name "Workstation".
  Routing
  IP 10.80.30.1 255.255.255.0
  IP helper 10.80.10.10
  output
  interface vlan 40
  name "phones".
  Routing
  IP 10.80.40.1 255.255.255.0
  IP helper 10.80.10.10
  output
  interface vlan 50
  name of the 'Camera '.
  Routing
  IP 10.80.50.1 255.255.255.0
  IP helper 10.80.10.10
  output
  interface vlan 300
  name "router".
  Routing
  IP address 192.168.1.250 255.255.255.0
  output
  user name 'root' password XXXXXXX level encrypted 15
  l2relay DHCP
  DHCP l2relay vlan 10,20,30,40,50
  !
  interface ethernet 1/g1
  switchport mode general
  output
  !
  interface ethernet 1/g2
  switchport mode general
  output
  !
  interface ethernet 1/g3
  spanning tree portfast
  switchport mode general
  switchport general allowed vlan add 10,20,30,40 tag
  output
  output

  Looking at the config on the switch, I can't predict whether the switch. The config is pretty basic, and the only way I guess whether the switch is if there were problems with the overall performance of the network. Love packages ignored, times of high ping, etc. Doing some research I found a few posts of blogs, KB and forum various with some things to look at what can help.

  http://msmvps.com/blogs/netman66/archive/2010/03/25/VMware-vSphere-4-client-slow-to-load-fixed.aspx

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1027836

  http://www.v-front.de/2011/07/improve-your-vSphere-clients.html

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1029665

  http://hardforum.com/showthread.php?t=1698368

  http://d1it.WordPress.com/2010/12/23/slow-vSphere-client/

  See you soon

• Configuration MDS MDS ISL and behavior

  Hello

  I've been Googling for days and really learn anywhere with this, so I hope someone here has some knowledge that I can draw!

  The situation:

  We have a new SAN and MDS (9148) installed and just about to start the migration of servers to virtual or physical machines to him.

  One needs to get a copy of SAN of the old SAN block data to the new San to allow the migration of some machines. Once this is done, these physical machines will then be repatched the new MDS and zoned accordingly.

  We can not connect the old SAN for the new MDS (for several reasons), and can connect the new SAN for the old MDS (for several reasons).

  It is a 24/7 business. Downtime has been negotiated on a basis to derisk the migration and application, it will be held over a period of 8 weeks.

  My conclusion is that we need an ISL between the MDS. I found a few guides on Google and YouTube for this but miss me something because is not quite make sense yet.

  My questions:

  • Is setting the mode of the interface to 'E' on each side enough to connect an ISL? Or other measures are necessary?
  • I saw something saying the ISL that VSAN (s) are allowed on the ISL - but do not see how to do it. Clues would be appreciated! FYI, MDS1 old and new MDS1 both have a single VSAN (10), and MDS2 both old and new MDS2 have a single VSAN (20). There is no inter VSAN routing.
  • I saw the reference to "behavior of fusion Zone. Can anyone confirm that this is please? The old MDS have their sets of areas that are suitable for devices connected to them. The new MDS have their sets of areas for the devices they are connected. Creation of an ISL will cause to merge into a single set of areas? If so, is that what I should wait no downtime?
  • Finally, everything would change if the "old MDS" were actually Nexus 5K (-5548UP which is what is on the site of DR)?

  I'm happy if you tell me the CLI or VIEW-based methods. I should add here that I can do the "basics" (alias, zoning, zonesets, etc.) in MDS, but this isn't something I've met before. There is no devices MDS test to test with, and at this point I am writing at the request of modification rather trying to run on the fly.

  I've attached a ' great plan' in case this is useful!

  Thanks in advance.

  Andrew

  Hi André,.

  I don't see where anyone has answered it.

  • Is setting the mode of the interface to 'E' on each side enough to connect an ISL? Or other measures are necessary?

  If you connect two MDS all ports that are AUTO (default) mode, and then they connect as an ISL.   Setting the mode of E is a good idea too.

  • I saw something saying the ISL that VSAN (s) are allowed on the ISL - but do not see how to do it. Clues would be appreciated! FYI, MDS1 old and new MDS1 both have a single VSAN (10), and MDS2 both old and new MDS2 have a single VSAN (20). There is no inter VSAN routing.

  By default, if trunk mode is enabled, then all the vsan configured which is on both switches will be trunked. If there are only 10 of the VSAN on the switches, it will be to resources shared, providing that there is no failure of the merger.  FCDOMAINs must be unique on each switch by VSAN.

  • I saw the reference to "behavior of fusion Zone. Can anyone confirm that this is please? The old MDS have their sets of areas that are suitable for devices connected to them. The new MDS have their sets of areas for the devices they are connected. Creation of an ISL will cause to merge into a single set of areas? If so, is that what I should wait no downtime?

  Look at this reference, it has information:

  Behavior of fusion zone when two MDS switches have names different set of active areas are connected

  In addition, you can use DCNM to a Zone merge analysis before doing this.

  In this document, see "analyze a Zone merge":

  http://www.Cisco.com/c/en/us/TD/docs/switches/Datacenter/MDS9000/SW/6_x/configuration/guides/fabric/DCNM-SAN_published/fm_fabric/zone.PDF

  • Finally, everything would change if the "old MDS" were actually Nexus 5K (-5548UP which is what is on the site of DR)?

  N °

• FI6248 FC connectivity with MDS SAN switches problem

  Hello

  We have two FI6248 in a cluster must be connected to two MDS SAN switches, using FC ports.

  However, I am not able to configure the ports on the FI.

  There is no "Set up as FC storage Port" option. I don't see what "configure as FCoE storage Port."

  I have the FC SFP (DS-SFP-FC8G - SW--> 8 Gbps Fibre Channel SW SFP +, LC) installed on the two FI6248 on the first 16 ports.

  No idea what is the problem?

  Kind regards

  The 6248UP unified ports.  The ports can be configured as Ethernet Ports or FC ports.  By default, all ports are of type Ethernet.  The ports that you configure is currently an Ethernet port.  You need config of the ports as FC ports.  Ethernet ports will be on the left side of your FI and FC ports will be on the right side.

  The following link explains how to convert a port UP Ethernet CF.  Since it's on your FI and not a plug-in, you have to restart the FI in last step.

  Configuration of the Port Modes for a fabric interconnect 6248

  http://www.Cisco.com/en/us/docs/unified_computing/UCS/SW/GUI/config/Guide/2.0/b_UCSM_GUI_Configuration_Guide_2_0_chapter_0101.html#task_3161F8BE44DA49F6BA9068A5D7594A6C

  Thank you

  Responsible Dan

  Need help with implementation?

  http://www.Cisco.com/go/pdihelpdesk

• Reference Dell 6248, 7048 or force S50N 10?

  Hello

  We want to improve our switches ISCSI 5424 to Dell Powerconnect 6248, 7048, or Force 10 S50N toggle. The switches will be devoted to traffic for 3 en berries Equallogic ISCSI must be able to support a few additional tables.

  Any advice?

  Thank you.

  Ok thank you.

• Masking vs. zoning for UCS and NetApp storage LUNS

  I know it's more a matter of Cisco MDS/storage, but nobody knows masking the LUNS and zoning, which one would be the most preferred method? I have two switches Cisco fabric 9148, two controllers SAN Netapp FAS3210 1 UCS chassis with 4 blades B200 M2. I said that I should not connect the Cisco UCS fabric interconnect directly at the back of the NetApp SAN and configure with LUN masking, but I rather configure a fabric zoning on switches Cisco 9148 MDS. Normally, this wouldn't be a problem but we have an offsite location where we have not all DMS switches to, and I would like to connect them directly to the San.

  I was told that this could lead to corruption if misconfigured dsik and point of view of Cisco is to use a zoning by some type of switch Cisco Fabric. Of course, I have of course this Cisco advises anyone to manage this type of configuration through their facilities instead of on the SAN. Does anyone have an opinion on the matter?

  Zoning and masking are two completely different characteristics.

  Zoning occurs on your storage switches and is the equivalent of an ACL (Access Control List).  It limits who may be considering other targets and/or initiators.  (Who I see?)

  Occurs on your storage array and masking limits what initiator LUN has access to.  (What do I see?)

  * UCS is not supported to directly connect a storage array in the interconnection of fabric, at least to have a storage upstream switch (MDS or equivalent) to push the zoning.  The use of zoning prevents a faulty initiator potentially impacting on the operation of the others by limiting what they can see in the fabric.

  If you happen to have a Nexus 5 K by chance, they can also work as your storage switch.  The N5K is able to perform almost all of the same services as MDS fabric and is fully supported.

  Kind regards

  Robert

• Read only zoning

  Hello

  On Nexus, possible possible is it to configure read-only zoning? If so, how?

  MDS, we have the attribute "read only".

  A9124-2 # config t

  Enter configuration commands, one per line.  End with CNTL/Z.

  A9124-2 (config) # area name Z_sresx1_HBA1_CX340_SPB_P0 vsan 2

  A9124-2(config-zone) # read-only attribute

  License ENTERPRISE_PKG not installed. Play only zoning will be stopped after the grace period of approximately 120 day (s).

  Thanks for your comments

  Nicolas.

  You can use fabric Manager to create read-only zones.

  http://www.Cisco.com/en/us/docs/switches/Datacenter/nexus5000/SW/configuration/guide/FM/zone.PDF

  Kind regards

  Robert

• The physical connectivity of fabric interconnect with MDS and failover please suggest

  Dear team

  We have 2 FI and 2 MDS 1 SAN

  Currenlty connectivity is

  2 physical connections of FI - has direct MDS1

  2 direct physical links to FI - B MDS2

  SDM 1 connection to the main controller of SAN

  SDM 1 connection to the secondary controller SAN

  Connection of 2 MDS to the PDC of SAN

  2 MDS to the secondary controller SAN connection

  Hope the above connectivity is good?

  We had watched

  http://www.Cisco.com/en/US/prod/Collateral/ps4159/ps6409/ps5990/white_paper_c11_586100.html (as a team always preferred to go through the standards of cisco)

  We could consolidate the FI and the primary and subordinate, even here for MDS in we need FI. or it will be through FIS?

  If not these 2 MDs they work as independent but share the configs that happens between them?

  Now this never changes (creation area) we do on MDS1 hope that will get relpicated in MDS2 through FIS?

  If MDS1 fails will be all the configuration is available on MDS2 and yet infra smooth it won't work? and vice versa?

  All the additional steps to be performed to achieve this?

  Which is the best way to do this please suggest

  Thanks and greetings

  Jose

  Hi Jose.

  Physically, your connection is good.

  On the side of the UCS, the role of "Primary" and "Subordinate" refer only to the management of the system and the device that actually performs UCS Manager.

  Each MDS device will have a separate configuration (zoning).  It's different between the 2 devices.

  The blade itself will be a connection on each side, or the "fabric SAN.

  for example

  +----+

  +---+    +-----+

  |   |    |     |

  |   |    |     |

  |   | 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 has a different WWPN, and on the Bay of SAN, each controller will have a WWPN

  So on MDS - A, the zoning will be:

  Blade WWPN

  WWPN primary storage has

  WWPN secondary storage has

  MDS - B, the zoning will be:

  Blade WWPN B

  Storage WWPN primary B

  Storage WWPN secondary B

  So the configuration is * not * synchronized between both MDS devices, but each of them have visibility to the device of vHBA of blades.  At the level of the blade, the software of multiple paths on the operating system will handle any failover.

  On the UCS, we would usually use a channel from Port to the MDS.

• VSAN, MDS, areas... and many doubs

  Hello

  After reading lots of documentation, I'm very confuse and it is very difficult for me to do a picture in my head of how this work.

  For example. I have a table of storage, 2 MDS 9148 and 3 servings (independent, no blades) with 2 HBAS each. Each HBA has 2fc ports of 8G each.

  So on the final configuration, each server will have own OS ESX and virtual machines, all within the storage Bay (serves him didn't have HDs).

  Topology of connection: I have 2 MDS for redundancy. So I guess that's Connect ports FC 2 (combination mode) from the server to each MDS switch. But what I need to connect 2 MDS using an ISL trunk?

  Design VSAN. VSAN is as VLAN but what are the criteria that I should follow to assign VSAN? A VSAN by ESX and the other by virtual machines. Or a VSAN by MDS switch, server...

  Area, pwwn and nwwn: if I understand correctly. nwwn is the address of my adapter HBA and the MDS and the pwwn is an address of each port on the HBA and SDM.  But dissing the areas, what are the criteria?

  And finally. The Vswitch on the sphere and on the storage array logical unit number. they have their own pwwn? Can I assign them to areas?

  Thank you very much.

  Best regards

  Check figure 4 of the

  http://www.Cisco.com/c/en/us/products/collateral/interfaces-modules/Stor...

  you do not have a core - edge, but only the kernel.

  All devices, storage and ESXi hosts have two hosted this 9148 2.

  NO ISL links between the 2 MDS. The CF philosophy is double fabric, A and B.

  You create 2 separate VSANS, for example 10 to fabric and 20 for fabric B.

  Zoning is directed by VSAN.

  Single initiator - single target areas: port hba - storage controller port pwwn pwwn.

  Your ESXi will then discover the FC LUNs.

  VM can't see CF, they see peripheral scsi (RDM is an exception).

  CF Multipathing driver may be installed on the host allowing failover and load balancing.

  See, for example.
  http://www.Cisco.com/c/en/us/TD/docs/solutions/Enterprise/Data_Center/VM...