ESX 3.5 creating a new vswitch during production hours?

Experts,

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!

Raymo12Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

65tdRetiredCommented:
A vswitch  can definitely done from the viclient.

Is the vswitch should not cause any issues re an outage.
0
coolsport00Commented:
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.

~coolsport00
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
pschakravarthiCommented:
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.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

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.

0
Raymo12Author Commented:
coolsport00

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!

Thanks!
0
coolsport00Commented:
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:
http://www.vmware.com/pdf/vsphere4/r40/vsp_40_esx_server_config.pdf


Regards,
~coolsport00
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.