VMware Cloud Community
Sachchidanand
Expert
Expert

Create standard switch through vsphere client

While creating a standard switch through vsphere client, it's not giving option to provide a name to switch. Instead it's taking standard name automatically like vSwitch0, vSwitch1, and so on. While creating the switch on the same host via ESXi client, I am able give it any name I want to give.

So is it a restriction on vsphere client? Or I go through a different way to create a switch through vsphere client?

Regards,

Sachchidanand

27 Replies
Sachchidanand
Expert
Expert

Thanks @markey165 

Reply
0 Kudos
Sachchidanand
Expert
Expert

Hi @scott28tt 

I am just looking at the current scenario. If at present I am able to do this via esxi, the same I am looking for vCenter.

Anyway I have raised a request through VMware ideas, so what are the percentage for getting it accepted or implemented?

Is there any criteria for ideas to be getting selected?

Regards,

Sachchidanand 

Reply
0 Kudos
Kinnison
Expert
Expert

Hello @scott28tt,


I'm sorry but it's not like that, Sachchidanand is absolutely right.


Via the GUI of HOST ESXi version 8.0U1c (and it was the same with all previous versions starting from version 7.0) it is very possible to create a standard vSwitch by giving it a name with almost any sort of characters not part of the "US ASCII" table, and up to a certain point it was possible to do the same thing also through the GUI of a vCenter object.


Regards,
Ferdinando


Result:

Kinnison_0-1692464525200.png

 

 

Reply
0 Kudos
scott28tt
VMware Employee
VMware Employee

@Kinnison 

You might be right about 7.0 onwards. I’m not disputing that at all. All I am saying is that it hasn’t always been possible to do that via any kind of GUI - I’ve worked with ESXi since it first appeared alongside ESX, and with vCenter Server since when it was VirtualCenter.

 

 


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
Reply
0 Kudos
scott28tt
VMware Employee
VMware Employee

@Sachchidanand 

No idea, I don’t work in any of the product teams.

 


-------------------------------------------------------------------------------------------------------------------------------------------------------------

Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
Reply
0 Kudos
tahmeed
Contributor
Contributor

They have always had this naming convention as standard.

Reply
0 Kudos
Kinnison
Expert
Expert

Hello scott28tt,


I'm sorry again,


I'm not here and I don't even dare to discuss your experience and knowledge of VMware products.


What I'm saying is that through the GUI of a host running ESXi it's been years since it's possible to create a new standard virtual switch using a "custom" name, which instead is not, in practical terms, possible with the GUI of a vCenter object otherwise I wouldn't have written to @Sachchidanand: "Forget it, just wasted time". But that some past build, unintentionally, under certain conditions had let him do I had kept it positive "feature".


Then perhaps it would also be appropriate to discuss to what extent a HOST running ESXi lets you name a standard virtual switch object.


Regards
Ferdinando

Reply
0 Kudos
KeithHardyNapie
Contributor
Contributor

I came across this thread when faced with the same issue.

If you log directly into the web interface of the host - not via vCenter - then you can create a standard switch with a custom name. 

You can then configure it as you like from vCenter.

 

Reply
0 Kudos