09-28-2016 07:43 PM - edited 03-01-2019 12:54 PM
we refer a Cisco TAC document attached with this post and following it. In our environment , we have following :-
1) Windows 2012 R2 Hyper-V hosts (UCS B200 M4 Blade servers) are not configured for SAN boot but from local storage.
2) We are neither using SCVMM client nor we are using failover cluster manager. We are managing Virtual machines only through Hyper-v Manager on separate physical hosts.
3) Storage is EMC and we have external FC switch as Brocade 6510.
4) FC uplinks are in End host mode in UCS FI.
We have also referred Cisco UCS to Brocade connectivity guide published by Cisco attached with this post.
With our configuration, WWPNs of ucs vHBAs are able to hit on storage and through this , we are able to see LUNs on Hyper-v Physical host. But , as we want Virtual machines to boot from SAN, so with Fiber channel adapters created on Hyper-v Virtual SAN manager, we are unable to get LUNs on Virtual machines. (we are following attached document 116471 for this). This is the problem.
The way, UCS vHBA WWPN hits on brocade switch and also with show npv flogi table in FIs, we identify that which cisco UCS FC uplinks the ucs vHBAs are dynamically assigned to. In the same way, WWPNs of Fiber channel Adapters on Hyper-V vSAN manager are unable to hit on brocade switch and this time, with show npv flogi table command, we get the same status as mentioned earlier.
So, please suggest , where are we missing out ? Do we need to manually add the zoning on Brocade 6510 switches, I mean do we need to manually add the WWPNs of hyper-v fiber channel adapters to brocade switches in order to make sure that they can access the LUNs on VMs.
But storage person says that these Hyper-V WWPNs should atleast hit on brocade switch first. Here we are getting confused.
Kindly suggest.
09-29-2016 10:27 AM
Can you please provide more detailed information
- UCS version
- FI model
- I/O adaptor
- Blade Model (CPU v3 or v4)
- enic / fnic driver
http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html
For 2.2.8 and B200-M4 (V3) I see the following notes
Note 10: If running in MS Cluster mode and Ethernet and FC traffic on VM’s with NPIV enabled, please see CDETs CSCuj20256 or driver README notes
Note 12: iSCSI Boot is supported. Both Appliance and Uplink ports are supported unless otherwise noted
Note 21: Drivers can be found on the latest 2.2(8) B-Series Driver ISO
Note 35: iSCSI boot with NIC Teaming is currently not supported. Reference CDET CSCul82285
Note 38: 6100 Series Fabric Interconnects and 2100 Series Fabric Extender is not supported
10-05-2016 12:20 AM
Please find below information
UCS version - 3.1(1h)
- FI model - 6248UP
- I/O adaptor - Cisco UCS 2204XP
- Blade Model (CPU v3 or v4) - Intel(R) Xeon(R) E5-2697 v3
- enic / fnic driver - (Vic drivers - 3.1.1c)
Kindly suggest as per above query.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide