tag:blogger.com,1999:blog-2348929890740508728.comments2017-05-28T12:17:28.228+01:00Andrew Lord - IT consultantAndy Lordhttp://www.blogger.com/profile/02737288969524797514noreply@blogger.comBlogger14125tag:blogger.com,1999:blog-2348929890740508728.post-15803583004449881092014-06-13T20:42:45.898+01:002014-06-13T20:42:45.898+01:00Worked brilliantly, thanks for the TipWorked brilliantly, thanks for the TipAnonymoushttps://www.blogger.com/profile/09625032302566184712noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-82657567873852395352013-06-26T17:13:19.424+01:002013-06-26T17:13:19.424+01:00From extensive testing now, you'll find it wor...From extensive testing now, you'll find it works best with NFS as the LUN targest (saves a lot of space on snapshots) and doing it that way a single subnet with 1 NFS target on one SPA and a single NFS target on the other SP works fine with the luns split across them. Andy Lordhttps://www.blogger.com/profile/02737288969524797514noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-54941601486741729992013-06-26T15:09:22.071+01:002013-06-26T15:09:22.071+01:00Did you create 2 subnetworks? One for each SP con...Did you create 2 subnetworks? One for each SP connections?Anonymoushttps://www.blogger.com/profile/11797001847419927715noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-17233819407417492562013-03-15T11:52:19.874+00:002013-03-15T11:52:19.874+00:00Thx, worked for me and saved hours! :)Thx, worked for me and saved hours! :)Dominikhttps://www.blogger.com/profile/16761705813337807107noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-64562789575142924762013-03-01T16:48:54.548+00:002013-03-01T16:48:54.548+00:00In a stacked scenario you can create an LACP trunk...In a stacked scenario you can create an LACP trunk over multiple switches. So in that case you can trunk all 4 ports out of SPA (if you have the 4 port card) and take 2 of them to switch A and 2 of them two switch B. Create a LACP port-group containing the two ports from switch A and the two from switch B.<br /><br />Then do exactly the same for SPB. This will give you resilience from switch, cable and SP failure.<br /><br />Hope this helps.<br /><br />AndyAndy Lordhttps://www.blogger.com/profile/02737288969524797514noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-72959898680244405732013-03-01T16:28:02.626+00:002013-03-01T16:28:02.626+00:00Right. So in the case that it were a stacked envir...Right. So in the case that it were a stacked environment, then creating a LACP connection would be fine. Correct?<br /><br />Now then, how about between stacked switches and SAN? LACP too? Or all ports on Switch A go to SPA and all ports to Switch B will go to SPB?<br /><br />I appreciate your help and quick response.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-26557093994919976612013-03-01T15:26:10.856+00:002013-03-01T15:26:10.856+00:00Hi Luis,
In that senario the switches were non-st...Hi Luis,<br /><br />In that senario the switches were non-stackable. The switches where LCAP'd together for resiliance however. The VMware hosts would have a VM LAN connection to Switch A and another one two Switch B, then a SAN connection to Switch A and another one to Switch B. The VM LAN would have a vSwitch in VMware with just vmNic1 (going to switch A) and vmNic2 (Going to switch B). So an LACP trunk from the VM host to the switches is not needed.<br /><br />The only time you would need that is if you needed more than 1gbps and then trunk to each switch.<br /><br />If the switches are in a stack (so for example a set of cisco 3650's) then you can create a LACP trunk across two switch (so gigabit ethernet 0/1 and Gigabit ethernet 1/1) covering you for switch failure.<br /><br />Hope that helps and thanks for reading.<br /><br />Kind regards<br /><br />AndyAndy Lordhttps://www.blogger.com/profile/02737288969524797514noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-5936670979358231332013-03-01T15:17:39.352+00:002013-03-01T15:17:39.352+00:00Andy I just ran into you Blog. Very nice work by t...Andy I just ran into you Blog. Very nice work by the way. I have a quick question in regards to the communication between your VMWare Hosts and the Stacked Switches:<br /><br />Did you create a LACP between your VMware hosts and Switches?<br /><br />-LuisAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-57748680904359650602012-07-11T10:41:14.563+01:002012-07-11T10:41:14.563+01:00Please do not send links to external companies. Th...Please do not send links to external companies. This is an independant blog and external links to companies will be removed.<br /><br />Kind regards<br /><br />AndyAndy Lordhttps://www.blogger.com/profile/02737288969524797514noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-67705245258051434432012-07-11T10:37:04.597+01:002012-07-11T10:37:04.597+01:00Hi Ariel,
And thank you for your comments and ques...Hi Ariel,<br />And thank you for your comments and questions. Let me 1st say that there is nothing wrong with either the NetApp or the Lefthand, in fact they are two very good productions, but it’s a matter of finding the right product for the solution. The criteria for this particular solution was that it had to have VMware integration, support CIFS and NFS, be easy to manage and fit at a certain price point but still deliver the IOPS requirements.<br /><br />The LeftHand is a very good SAN, especially if you have two different buildings (with good bandwidth and low latency) whereby you can locate half of the array in one building an half in the other, giving the end customer excellent DR continuity. The downsides for this particular solution were that LeftHand (at the time I did this project) would only support iSCSI. HP’s recommendation was that we use a “Bridge server”, which in reality was to have a VM or physical server with a RDM to a LUN on the LeftHand. I would have preferred they were honest about this and just said we don’t support CIFS. The VMware integration is there, but isn’t (in my opinion) as good as the NetApp or the EMC, management of the devices wasn’t as intuitive as the EMC and the dual location was a nice to have rather than a necessity.<br /><br />The NetApp is a brilliant SAN and I don’t think if anyone purchased one of these they would be disappointed. The de-duplication features on the unit are brilliant, especially if you’re rolling out VMware view (lots of identical VM’s). The couple of negatives against the NetApp why it wasn’t selected for this implementation were that the user interface wasn’t a “friendly” for the end user as the EMC and the main killer was the price. At the time of this project the EMC came with 3 years warranty and the NetApp was only 1 year. To extend the warranty on the NetApp to be the same as the EMC was in the region of £6,000 per, year coupled with the fact the equivalent IOPS device was significantly more expensive than the EMC, the total solution would have been almost double that of the EMC VNXe.<br /><br />The VNXe supports CIFS, NFS and iSCSI our of the box and delivered what the customer required at the right price point.<br /><br />Thanks again for your comments and reading my blog.<br /><br />Kind regards<br /><br />AndyAndy Lordhttps://www.blogger.com/profile/02737288969524797514noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-72976137186429108022012-07-11T07:33:24.679+01:002012-07-11T07:33:24.679+01:00Hi,
first, let me say that your posts are great.
c...Hi,<br />first, let me say that your posts are great.<br />can you detail some more info why you didn't choose NetApp and lefthand, and why you prefer the EMC solution that is limited to iSCSI only? (exclude the price issue...)<br />thanks,<br />ArielAnonymoushttps://www.blogger.com/profile/01867463245717177506noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-384176521259197902012-07-10T14:44:41.364+01:002012-07-10T14:44:41.364+01:00This comment has been removed by a blog administrator.Amagesofthttps://www.blogger.com/profile/10354257979530606610noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-89254364783000018762011-11-02T14:55:57.475+00:002011-11-02T14:55:57.475+00:00This comment has been removed by the author.Andy Lordhttps://www.blogger.com/profile/02737288969524797514noreply@blogger.comtag:blogger.com,1999:blog-2348929890740508728.post-52108854346352797032011-07-18T18:20:22.462+01:002011-07-18T18:20:22.462+01:00A correction.
When you pull a network cable, the ...A correction.<br /><br />When you pull a network cable, the VNXe detects link down and routes the network connection across the VNXe backend to the corresponding port on the other storage processor. The "service" itself stays on the same storage processor. <br /><br />If a storage processor fails, then everything fails over.hillkemchttps://www.blogger.com/profile/10368446438071850039noreply@blogger.com