This summer has seriously flown by! It’s hard to believe that in three weeks I’ll be flying out to Vegas for VMworld. Between the sessions, labs, networking events, and a party or two, the week is shaping up to be awesome!
I have a bunch of great sessions scheduled for this year. I’m also really glad they are doing scheduling this time, it will avoid the hour and a half lines that I waited in last year. This will allow for more time to talk with presenters afterwards so I’m excited! I won’t list all my sessions out, but here are a few that are on the top of my list:
VSP1926- Getting Started with VMware vSphere Design
I’m really looking forward to Scott’s session on vSphere design. His book that came out this year on the same topic was excellent, so it will be good to expand on this and hear from experiences in the field!
VSP1425- Ask the Expert vBloggers
Put this many vExperts in a room, throw out some user submitted questions, what more do you need?
CIM1644- The Path from Lab Manager to VMware vCloud Director: A Customer Journey
I submitted a session on a similar topic, so I’m very interested to hear this one. The migration from Lab Manager to vCloud Director is not trivial and it is a big step forward in cloud strategy. I’m interested to hear the customer experience on this one!
VSP3111- Cisco Nexus 1000v: Architecture, Deployment and Management
One of my top sessions from last year, Jason has updated the content for vSphere 5 and as a Cisco guy at heart, how can you not get excited for this one?
VSP2757- A Deep Dive on Virtual Distributed Switching and Cisco Nexus 1000v
vSphere 5 brings some much needed enhancements to the vDS. I’m really looking forward to the discussion around vDS vs. Nexus 1000v and real-world implementation advice for both! This, and Jason’s dedicated Nexus 1000V session, are ones you won’t want to miss!
VSP1682- VMware vSphere Clustering Q&A
What’s better than an early morning session from the two guys that wrote the book on Clustering and HA?
All things are pointing towards this year being epic! Not only do you have all the great sessions, but the Hands on Labs will be bigger and even more awesome than last year! There were some insane numbers on how many VM’s were deployed over the week last year and their goal is to crush that number!
At the EMC booth, we will also have our own Hands on Labs in the solutions exchange. RSA will be well represented with some excellent content around vShield Data Security. A lot of people have put in a ton of work on these labs, so I’m really looking forward to these! I’ll be around the booth, so come stop by and check out the labs!
Most of all though, I’m looking forward to seeing a lot of my friends from the community who for some, I only get to see at this event. I’m also excited to meet a lot of new faces and chat with my fellow vNerds. So drop me a note in the comments here if you’ll be attending and make sure to say Hi!
Will Vegas be ready for us? I sure hope so!
To start things off, welcome to vPrimer! This blog will be a source of how-to’s, information, and news centered around virtualization, security, and networking. I hope to provide a viewpoint from inside the industry that will be useful no matter if you are a home lab user or large enterprise administrator. I always welcome comments and discussions as one of the best ways to learn is from everyone around you!
Now, what fun is a first post without some technical content? So let’s get to it! Today’s post will briefly go over the changes to setting up a software iSCSI adapter and VMkernel port bindings in vSphere 5. One of the biggest changes you’ll notice is the addition of iSCSI port bindings to the vSphere GUI. To setup and use multiple pNIC’s for iSCSI in 4.1, part of the process had to be done via CLI. It is now all wrapped into the client for a much cleaner look.
The first step is to setup your vSwitches/VMkernel ports. In this example, I’ll be using a vDS, but the process is very similar for a vSS. Below is an example of a vDS setup with two uplink ports as well as two Port Groups:
Once your vSwitch is created, we’ll go ahead and create the VMKernel ports. Select Manage Virtual Adapters and then Add:
We’ll select a New Virtual Adapter and then add it to our first iSCSI port group:
Next we’ll give the VMKernel it’s IP info:
Finally, if everything looks okay, click finish to complete the process:
Next you’ll want to repeat these same steps and add a second VMkernel adapter and make sure to add it to the second iSCSI port group (iSCSI2 in my case).
In order to make sure each VMkernel port is bound to one pNIC, we need to explicitly set the failover order. This needs to be done for both ports. One the first port, set it to dvUplink1 and the rest to unused. On the second, use the same procedure, but with dvUplink2. Here’s what they should look like:
Now that we have our port groups and ports created, let’s add a software iSCSI adapter. Under Storage Adapters, click on Add, then choose Software iSCSI Adapter:
Once this task completes, you should see the newly created adapter:
Now click on the iSCSI adapter and choose properties. Under the Network tab, the VMkernel Port Bindings section should be empty. Let’s fix this by clicking Add.
The next screen allows you to choose which VMkernel ports you want to bind to the iSCSI adapter. You can see the two ports we just created (vmk1 and vmk2) that are on our StoragedvSwitch. You can only select one port at a time, so select the first one and then repeat this procedure for the second.
If all has gone well, you should see a summary screen similar to following:
At this point, you’re free to add in your iSCSI discovery targets and proceed with adding storage. This process is not drastically different than in 4.1, but if you’ve had to do the CLI work before, this makes it a lot cleaner. I’m also a graphical person, so it’s nice to see the status/bindings right in the GUI.
And that about wraps it up for this post. Thanks for reading and I hope you found this useful. Look for more content to come and as always, I welcome any comments or feedback!