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

ESX 3.5 creating a new vswitch during production hours?


I have 2 esx 3.5 hosts which need another vswitch configured for vmotion network. Can this be done during production hours? Adding the new vswitch and configuring the vmnic does not cause any connectivity issues does it?

Also, can this all be done from the vi client? Thank you for your help!

2 Solutions
A vswitch  can definitely done from the viclient.

Is the vswitch should not cause any issues re an outage.
Yes, it can be done during production; no, it doesn't cause connectivity issues; and yes, you can do it via the VI Client. :)
I guess I'm wondering why you're going to configure your VMotion on a whole different vSwitch? You can use a 2nd NIC within the same vSwitch....just a thought/suggestion. There really isn't a performance jump configuring a 2nd vSwitch for VMotion...just FYI.

Just go to the Config tab -> Networking and 'Add Networking'. In the wizard choose to create a vSwitch.

Adding the new vswitch and configuring the vmnic does not cause any connectivity issues
But if you are changing the trunk ports, then there would be an issue.
Its better to go by a maintenance window.
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Matthew EnglandTechnology ConsultantCommented:
Ideally you would want to use a separate NIC for your VMotion & Production networks. If you're doing so, then you should have no problems either with the configuration or, when you start using VMotion.

If you have them running on the same NIC, and are not able to add a second NIC to that machine, then I would recommend setting this up & testing it after hours. While 65td is correct in that the configuration will not result in an outage, you will want to test your VMotion configuration once you're finished with the configuration, which could impact your production network traffic.

It's also a best practice to segregate VMotion networks through the use of VLANS. Again, while setting up a VLAN on your physical switches is not generally disruptive to traffic, (although it depends on the switch) complications can occur, and I always prefer to error on the side of caution. If you're not using VLANS or already have your switch configured to pass the appropriate VLAN's to the vSwitch, you can disregard this paragraph.

As for performing it all from the viClient, yes you can. Just point it to your vCenter server as normal. Select the desired server, click on the Configuration tab, then under Hardware, click on Networking & then the Add Networking link, or if you already have an existing vSwitch you want to reconfigure, click on the Properties link for that switch.

Make sure you have a test VM available to test out VMotion with.

I hope this helps.

Raymo12Author Commented:

Thanks for pointing that out. I'm coming into a new job and they have separate vswitch configured for vmotion on all the other esx hosts so I figured I would just continue on with that template.

PacificMist - Thank you for the info. I'm getting the feeling that alot of this work was done without many best practices considered so I am sure I will have more questions!

Well, that makes sense...consistency :) I would actually keep the infrastructure consistent as well. You can read more about networking (if you haven't already) in the ESX Config Guide:


Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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