Showing posts with label Networking. Show all posts
Showing posts with label Networking. Show all posts

Monday, May 18, 2015

Adding an uplink to VDS fails with an error "Call "HostNetworkSystem.UpdateNetworkConfig" failed

Hi,

I was just working on VDS and found out that while adding an additional Uplink to the existing VDS failed with the following error.

The environment consists of ESXi/VC 5.5 U2 and I have tried configuring the same using the vSphere client and also the Web Client and getting the same error using both methods. ESXi using Cisco UCS B-200 M3.

"Call "HostNetworkSystem.UpdateNetworkConfig" for object "networkSystem-416016" on vCenter Server "esxhostname" failed"





Now I tried finding out the KB site of VMware and found out only few KBs related to the same error.

First one is KB 2081478 which I worked on at some time and mostly talks about the IBM 3650 M2 or M3 servers and the other one is KB 2013558 which is discussing the issue when migrating the vmkernel interface to VDS fails. My issue was not following in either of the categories.

So I started looking in to the issue further from VDS perspective and found out that the existing VDS is using two uplinks and I was trying to add 3rd uplink.

I looked at the properties of the VDS by going into  Home -> Inventory -> Networking and right click the VDS in question and hit Edit Settings and I saw the following.



As you can see the configured number of uplink ports are only 2 and I cant add more than that.

Now this simply very obvious that there are lot of factors / situations which can play the part here e.g. You forgot what you have setup initially when you built the environment for the first time or you are working on a pre-configured environment by someone else and you never know such configuration was done by whom and how long ago or there is no documentation available for such configuration.

Either of the cases will lead back to the troubleshooting process which was just to find out where things are wrong based on the error. But at the same time as the error itself if not do descriptive, you are in hands of your own knowledge and experience for the product or you need to engage the Support.

By now you might have already figured out the resolution, which was nothing else but just to increase the number of dvuplinks for that VDS. Once I increased to 3 I was able to add the 3rd pNIC as an uplink to that VDS.

Hopefully this will help to the readers.

Please share and care.

Cheers !!



Sunday, February 8, 2015

Recommendation on Linkedin - Yes, I need it !

Hi All,

I never thought about this before to write a blog post of about requesting the community members and friends and others who are in touch with me one or the other way, to provide recommendation to me through Linkedin.  Now  a days Social media is the way to reach out to mass and seems to be very effective too.

After serving 8 years at VMware, now I am in a position where I am searching for a new challenge so at the same time feeling necessity about having Recommendation of my Work done in that duration.

If my contribution / reply / update / pointers helped you in any way or at least put you in the direction you want, then please just take few minutes to provide a Recommendation as its very valuable for me a lot. I would say it will be priceless.

As everyone knows Linkedin is the platform for all professionals to be in touch with each other and this is a most respective way in our professional world where one can find out everything about other person in this very space.

I have provided recommendations to those who needs them time to time and never thought of the need at that time but now I am in the same boat as them. Time is same for everyone and you never know when it will change. As it changed for me, I humbly request to provide the same at your earliest convenience and me and my Family are truly grateful to you for your time and help.

So please feel free to reach out to me if you need the same and I am happy to provide it as well.

This is a general stand I am taking to get the recommendation as it will take lot of time to reach out to people individually (in fact I am doing that too) but as the person might be busy or not checking his linkedin, the message may be sitting there idle. I have seen few messages like that in my inbox which I just acted and agreed that they were requested by the person/s almost a year back. Now providing the recommendation at present, may or may not help as it was not done on time (may be they need at that time) and I have provided today. So please check your inbox for such message and at least let the person know the status about it. Going forward, I will be taking care of it for sure as now realized the importance of it. As everyone has their own priorities to do things so please dont take this as any advice or such. but consider it as a general thought of a person who is in need at the moment.

If you are not in my circle then just send out the request on my way and my doors are open.

If you see any request from me about the recommendation then once again, just requesting few minutes of your busy schedule to provide it.

Community is all about help and hence this blog post.

Hope you will help and also spread the message to others.

Thanks for your time and help

Please share and care !

Wish me luck !





Wednesday, February 20, 2013

Need 5 mins of your valuable Time

Hi All,


Back in 2012 the announcement of vExpert for 2011 was made and I was not selected based on the standards and criteria but I took that as a challenge and committed to myself to do blogging about all VMware related technologies and actively started blogging from April 2012 onwards and here I am with 70 Blog posts so far.

This blog is dedicated to all the VMware Community and to the people who are using VMware on a daily basis.

Spreading knowledge is the key for me when it comes to VMware. I am not in the race but just to get the support from you in one of the categories such as the following would be highly appreciated.

"Best New Blog"

"Best Networking Blog" 

"Best Storage Blog"



There are others blogs out there but if you think a single blog post helped you then Vote for my blog just for the support and extend the help to contribute more and more going further.

It will take few minutes of your time but will make more long time effect on me and will give enough fuel for the upcoming years. I expect nothing else as your invaluable Vote will have everything.

Use the following link to vote and urging not to do any Fake multiple voting.


http://www.surveygizmo.com/s3/1165270/Top-vBlog-2013

Thanks for your time and appreciate all the help you are doing to recognize the efforts




Share and care !!

Cheers !!


Vote for the "Best New Blog" of 2012

Wednesday, November 7, 2012

LACP and vSphere 5.1


LACP is the new feature introduced in new vSphere 5.1 VDS (vSphere Distributed Switch).

With that there are some articles published out by VMware for the issues involved with it.

The articles are listed below.


Enabling or disabling LACP on an Uplink Port Group using the vSphere Web Client (2034277)      
LACP is enabled for Virtual Distributed Switch (2036296)      
Inconsistent uplink speeds disable LACP (2036303)

http://kb.vmware.com/kb/2036303    
LACP cannot be enabled (2034683)     

http://kb.vmware.com/kb/2034683
Inactive uplinks disable LACP (2036302)  

http://kb.vmware.com/kb/2036302  
Duplicate packets or packet loss when using using LACP (2034807)     

http://kb.vmware.com/kb/2034807
Inconsistent uplink duplex modes disable LACP (2036304)      
LACP is disabled for Virtual Distributed Switch (2036299)  

http://kb.vmware.com/kb/2036299  

Cannot enable LACP because of incompatible teaming policy (2036300) 

http://kb.vmware.com/kb/2036300  

No peer response from uplink disables LACP (2036305)     
Uplink moved out of link aggregation group (2036306)     

http://kb.vmware.com/kb/2036306

Uplink blocked on virtual distributed switch (2036308)      
Uplink unblocked on virtual distributed switch (2036309)     

http://kb.vmware.com/kb/2036309
Uplink disconnected on virtual distributed switch (2036310)    

http://kb.vmware.com/kb/2036310

Uplink connected on virtual distributed switch (2036311)   

http://kb.vmware.com/kb/2036311

@chriswahl has put up a nice video on configuring LACP here.


Enjoy working with LACP