Thanks everybody for your responses and information. I have a couple things I'm going to try. First thing I'm going to try is setting the ports to edge ports for spanning tree. My thought is that maybe fcoe is trying to communicate before the port is actually up. I'm also going to ask the server guys to try using version 5.0 of ESX. I'll let everyone know the results but if anyone else comes up with anything else, please let me know.
Thanks, Eric -----Original Message----- From: Andrew Jones [mailto:[email protected]] Sent: Tuesday, October 25, 2011 8:25 PM To: Nyman, Eric; Ryan West; [email protected] Subject: RE: HP VM ESX fcoe issues with Nexus 5020 We have a nexus 5020 and a HDS san (connected via FC module in 5020) in our lab, and when configuring the storage for the first time, ESX wouldn't discover the storage until after a reboot of host. I cant recall the chipset of CNA's in use though, will need to logon and have a look. Andrew Jones Alphawest -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Nyman, Eric Sent: Wednesday, 26 October 2011 1:30 AM To: Ryan West; [email protected] Subject: Re: [c-nsp] HP VM ESX fcoe issues with Nexus 5020 Thanks Ryan, I also ran into the rebooting bug which is actually how we discovered this issue. We are running HP CN1000E adapters which are using Emulex chipsets and the ports are trunked. One this I'm wondering is if spanning tree has anything to do with it? I just looked and the ports are not setup to be edge ports. Are your 5K's in NPV mode? -----Original Message----- From: Ryan West [mailto:[email protected]] Sent: Tuesday, October 25, 2011 9:42 AM To: Nyman, Eric; [email protected] Subject: RE: HP VM ESX fcoe issues with Nexus 5020 On Tue, Oct 25, 2011 at 08:45:25, Nyman, Eric wrote: > Subject: [c-nsp] HP VM ESX fcoe issues with Nexus 5020 > > All, > > I'm having an issue with my ESX servers that are connected to our > Nexus 5020's using FCOE to connect to our storage MDS9500's. > Basically, if for any reason connectivity (either FCOE or Ethernet) is > disrupted to the 5K's, the ESX servers will not recover and will > require a reboot to reconnect to the storage. Cisco TAC have been > looking into it for some time now but they have not been able to > provide any information. Cisco's recommendations were to try the 5K's in either NPV or NPIV mode but we get the same result. > In another scenario, we also had a Cisco UCS chassis that would not > connect to the storage unless a shut/no shut was initiated on the > switch port. That seems to be resolved with a driver update but only > on the 5K switch that is NOT NPV enabled. > > > > Anyone ever had any experiences with ESX servers connecting to storage > on the 5K's? > I had many issues in the beginning with FCoE coming online as an access port with Emulex cards. Trunking resolved that issue. As far as recovery goes, I was having problems with the 5010 rebooting on an earlier 5.0(2) code and corrupting portions of my voice lab. That's been resolved with 5.0(3)N1(1b), which has been running a little over a month with no incident. During the reload, the hosts were obviously disconnected from storage, but would reconnect when the fabric came back online. These are the versions I've tested: C210 M[12] - QLogic QLE8152 10 Gbps 2 port CAN 5010 w/ N5K-M1008 8x1/2/4G FC Module Hitachi AMS2100 directly attached to N5k-M1008 CIMC/BIOS version from 1.3 to 1.4(1a) currently ESXi 4.1 Initial release to 5.0 Haven't tested with NPV or NPIV though. Thanks, -ryan This email transmission may contain CONFIDENTIAL, PRIVILEGED, and or PROTECTED INFORMATION intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by email, do not disseminate or copy and delete immediately. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ This email transmission may contain CONFIDENTIAL, PRIVILEGED, and or PROTECTED INFORMATION intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, please notify the sender by email, do not disseminate or copy and delete immediately. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
