@Sachchidanand Are you referring to the old C# Windows Client? Also what version of ESXi ?

ESXi version -- 7.0 Update 3n

vCenter version -- 8.0 Update 1c

Regards,

Sachchidanand

Hello Sachchidanand,

Via the vCenter Object? Forget it, just wasted time, willy-nilly "things" work that way, and I've personally never figured out why.

Regards,
Ferdinando

The vSphere Client does not allow you to provide a name for a standard switch when you create it. Instead, it will automatically assign a name like vSwitch0, vSwitch1, and so on. This is a restriction of the vSphere Client.

The switch will be created with the default name vSwitch0,vSwitch1, etc..

If you want to create a standard switch with a custom name, you can do so from the ESXi Shell. To do this, run the following command

esxcli network vswitch standard create -d <name>

where <name> is the custom name for the switch.

Ex:- esxcli network vswitch standard create -d InterntSwitch

Please don't forget to accept this as an accepted solution or give me a KUDO if you find this post useful! Thanks! 

I understand that there is no such feature in vSphere client to give a specific name to a standard switch. So what is use of managing all hosts through vCenter if I have to use ESXi interface to perform some specific task?

Is there any mechanism in community where we can raise a request for the feature update?

Regards,

Sachchidanand

Hello,

For how to do it you could take a look here: https://kb.vmware.com/s/article/1002123

Regards,
Ferdinando

Hello scott28tt,

Because, for example, it's sometimes useful to describe/distinguish what a particular vswitch on an equally particular host is used for among many others.

Regards,
Ferdinando

@Sachchidanand 

How to log a feature request can be found at this KB - https://kb.vmware.com/s/article/1002123

This will link you to the vSphere ideas and requests Portal - https://vsphere.ideas.aha.io/

HTH

I understand the use case for renaming switches. In our environment we have multiple switches for separation of different networks for security reasons. We also have separate switches for storage.

So we need to rename them to identify which switch is which 

Hello,

Excuse me but in my humble opinion this is not the point,

Standard virtual switch can be named as you like via the ESXi GUI/CLI but is prevented via vCenter GUI, this feature was removed some time ago.
PortGroups can have a descriptive name up to 80 characters (if I remember correctly) but in the GUI "overview pane" of the vCenter object that name is displayed truncated to 27 characters while in the GUI/CLI of an ESXi host it isn't.

From ESXi GUI : "NET-192.168.253.0-28_vMotion_PG_B"
From vCenter GUI : "NET-192.168.253.0-28_vMotio..."

But aside from the "cosmetic stuff", I might want to name my standard object virtual switch to match my standard methods of naming objects part of the rest of my network infrastructure or whatever else I think meet my needs, for example to describe for reference "at a glance" which VMNIC it uses and to which port it is connected to on the other side.

To say: "VSW1>VMNIC0_SW1Core_G1/0/18 - VMNIC1_SW2Core_G1/0/18"

Anyway I don't want to bore anyone beyond measure, in case I apologize.

Regards,
Ferdinando

Hi @scott28tt 

As @markey165 said, I also have multiple switches in my setup and giving specific name helps me identifying during troubleshooting a issue.

So my question is, if the same feature is already exists in ESXi, why not through vCenter?

I don't want to manage specific task through individual ESXi nodes if I am managing all my nodes through vCenter and I think that is the purpose of vCenter, so you manage all your tasks from a single interface.

Regards,

Sachchidanand

Thanks @Kinnison @markey165 for sharing the link.

I will surely raise a feature request and see if VMware consider it feasible.

Regards,

Sachchidanand  

Recently I have created multiple switches through ESXi GUI only where you can give the whatever custom name you want to give.

Attaching a screenshot for the reference.

Regards,

Sachchidanand

Hi All,

I have raised this feature request through vSphere Ideas. Here is the link:

https://vsphere.ideas.aha.io/ideas/VSP-I-1514

If anyone else also required this feature, please support and add your additional comments.

Regards,

Sachchidanand

@Sachchidanand - I have voted