• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1162
  • Last Modified:

Hyper-V Server 2012 Guest Failover Cluster WWNN settings and SAN from address not in hard zone error

I am experiencing several errors on my san switches on ports that my hyper-v cluster servers are plugged into.
2 SANbox 5802 FC Switch without any zones setup.
1 XIO ISE2
2 Dell R710
The two dell servers are part of a hyper-v cluster.  I have two vm's running in the hyper-v cluster that is a guest cluster.
Each server has a dual port qlogic QLE2562 hba.  One port goes to one san switch and one goes to the other.
Each hyper-v server has two VSAN's setup on each and each one is mapped to a different port on the QLE2562.
2 Server 2008 R2 Vm's running guest SQL cluster
Each Guest VM has two Fibre Channel adapters which means that each VM has 4 WWPN's for a total of 8.  By default hyper-v sets the WWNN all to the same address for every fibre channel adapter I add.  Does this matter?  I feel like I should change the WWNN so each of the virtual Fibre Channel adapters should have a unigue WWNN so I should have 2 WWNN for each VM and 4 total of both VM's.  Is this not the case?  Should I leave them the same??  I can't find any documentation about whether the WWNN should be changed.  It seems like I should.
On SAN switchs, specific to the ports the hyper-v servers are connected to I see several of these messages that happen every so often.:
"
][Eport][Port: 3][Received 1 frame(s) from address not in hard zone (current frame src address = 0x10000, dest address = 0x10301)]
"
Anyone have any thoughts to why I am seeing this message and about how the WWNN should be configured?
Thank you for your time.
0
gacus
Asked:
gacus
  • 5
  • 2
1 Solution
 
andyalderSaggar makers bottom knockerCommented:
By default hyper-v sets the WWNN all to the same address for every fibre channel adapter I add.  Does this matter?  

AFAIK you have to use SANsurfer
"Click the Generate button in the vPort WWN Generation dialogue box and let SANsurfer FC HBA Manager generate a unique WWN." (from a PDF which I have locally.

http://filedownloads.qlogic.com/files/driver/npiv/readme_fc_hba_mgr_NPIV_config.html#Virtualization
0
 
gacusAuthor Commented:
Thank you for the information, but this document doesn't apply to Hyper-v 2012.  It creates the vports for you.
0
 
gacusAuthor Commented:
Anyone able to provide more information about what this error means?

][Eport][Port: 3][Received 1 frame(s) from address not in hard zone (current frame src address = 0x10000, dest address = 0x10301)]

Is it saying that port 3 received a packet originating from port ID 0x10000 intended for 0x10301?

I see one of these events at least every hour.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
andyalderSaggar makers bottom knockerCommented:
Well, you may be right but http://pic.dhe.ibm.com/infocenter/strhosts/ic/index.jsp?topic=%2Fcom.ibm.help.strghosts.doc%2FVSS+VDS%2F4.4.0%2FUG%2FVSS_VDS_config_NPIV_Hyper-V.html says you still have to "Create a virtual port using the FC HBA Manager GUI". OF course Microsoft may be automatically creating the virtual ports on the HBAs by using an API provided by the HBA manufacturer. The WWNN being the same doesn't matters so long as the WWPNs are different for each virtual HBA.
0
 
gacusAuthor Commented:
I checked and I can see the vports so Hyper-v is auto creating the ports for me.

Anyone able to provide more information about what this error means?

][Eport][Port: 3][Received 1 frame(s) from address not in hard zone (current frame src address = 0x10000, dest address = 0x10301)]

Is it saying that port 3 received a packet originating from port ID 0x10000 intended for 0x10301?

I see one of these events at least every hour and it seems like it is maybe related to something the vsan switch is doing??.  Maybe some kind of heartbeat??
0
 
gacusAuthor Commented:
A bad SFP was causing this issue.  Replacing the SFP and the error is no longer happening.
0
 
gacusAuthor Commented:
Because this is what fixed the issue
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 5
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now