Create Service Console Port in vMWare Server 4.1

Glen Knight
Glen Knight used Ask the Experts™
on
Hi All,

Having just migrated from VMWare Server 4.0.0.1 to VMWare Server 4.1 I am now adding an additional host to the cluster.

I have added the host and am in the process of configuring the networking.

I have created my vSwitches and don't seem to be able to create a Service Console port.  When I click Add the only options I get are Virtual Machine and VMkernel.  However, if I do the same on the other hosts I do get the option to add a Service Console port.

Any ideas why this would be happening and how to correct it?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Kruno DžoićSystem Engineer

Commented:
i found this

copy paste from http://virtual.bist.be/?p=102

There might be occasions where you lose you Service Console switch or configuration. Ofcourse for the lazy people among us a reinstall helps the situation. There is another way to recover your service console if you have server access ofcourse. You need to be able to physically reach the server.

Logon to the Server Console and logon, then follow the steps below.

 

1.Run the following command to list the name of the vswif adapter:

esxcfg-vswif -l

2.Run the following command to delete the vswif adapter:

esxcfg-vswif –del vswif0

3.Run the following command to list the name of the vSwitch:

esxcfg-vswitch -l

4.Run the following command to delete the vSwitch:

esxcfg-vswitch -d vSwitch0

5.Run the following command to create the vSwitch:

esxcfg-vswitch -a vSwitch0

6.Run the following commands to create default port groups for vSwitch:

esxcfg-vswitch -A “VM Network” vSwitch0


esxcfg-vswitch -A “Service Console” vSwitch0


7.Run the following command to create the vswif adapter:

esxcfg-vswif –add –portgroup “Service Console” –ip=nnn.nnn.nnn.nnn –netmask=255.255.255.0 vswif0

8.Run the following command to verify that the settings in the network file are correct:

cat /etc/sysconfig/network

NETWORKING=yes

GATEWAYDEV=vswif0

HOSTNAME=host.domain.com

GATEWAY=nnn.nnn.nnn.nnn

9.Run the following commands to list all of the network adapters and associate a vmnic which has a link status of up:

esxcfg-nics -l


esxcfg-vswitch -L vmnic1 vSwitch0


10.Run the following command to verify that the vmnic is associated with the vSwitch:

esxcfg-vswitch -l
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Is this ESX or ESXi, ESXi has no service console.
Awarded 2009
Top Expert 2010

Author

Commented:
@M3rc74 > Thank you for your google search.  I had already done this myself and found no useful information which is why I posted a question here at EE.

@hanccocka

Oh :(

Now I feel like a donut.  It is indeed ESXi.  So has the Service Console port been replaced with something else or was it just decided it was no longer required?
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Kruno DžoićSystem Engineer

Commented:
The "Management Network" is a VMkernel port.  
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
ESXi has no Linux component anymore, so the Service Console (COS) has gone. (if we ever meet, over beers, we can discuss this more openly as to why! or call me!!!)

ESXi has a Management Interface.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
We generally setup ESXi networking as follows


An-Example-of-vSwitches-and-NICs.jpg
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
The Management Network "*can*" be associated with the VMKernel, but it's not best practice, see above for Best Practice, with resilience. (with two NICs Load Balancing, Failover) for Management Network, VMKernel, and VM Network (Four NICs) and FT.
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
ESXi is supported on smaller set of certified hardware because it is standalone system and it doesn't depend on RHEL service console which provides drivers for other hardware.
Awarded 2009
Top Expert 2010

Author

Commented:
Now, if only I had bitten the bullet 2 hours ago and asked!!! Problem is, I am just helping you close the gap on my lead on the leaderboard :)

On a plus point, the sooner I finish this job, the sooner I turn my question filter back on :-)
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
In Summary, as per your questions, this is the expected bevahiour of ESXi.

(ESXi is supported on smaller set of certified hardware because it is standalone system and it doesn't depend on RHEL service console which provides drivers for other hardware.)

Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Not bad considering I was nowhere 6 months ago!!!

that gap is getting closer!
Awarded 2009
Top Expert 2010

Author

Commented:
As I am coming to expect, excellent advice from hanccocka.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial