Skip to main content

ESXi vmnic shows 20gb or 40gb instead of 10gb On UCS


After configuring UCS Service profile, installing VMWare ESXi and configuring Nexus 1000v, i found VMWare vmnics were showing 20 gbps per nic. It was little confusing for me as each UCS Server port from blade to Fabric Interconnect should show 10 gbps. I started exploring it and found an interesting design of Cisco UCS VIC Cards 1340/1380 or UCS Port expander.

As you can see there is hardware port channel between the virtual nics, and the outward ports connected to the IO modules.

 As you can see it depends upon different type of connectivity between VIC cards and IO Modules, if you are connecting VIC 1340 without port expander then hardware port-channel see only two 10 gig interfaces connected to it and it presents 20 gig connections to each server Ethernet link, vmnic on ESXi in our case. And if a port expander is connected then the hardware port-channel sees four 10 gig interfaces connected to it so it represents as 40 gig connection for each Ethernet link down the Server. This bandwidth is provided only when UCS IO Modules of 2208xp are installed, if the IO Module 2104 is installed then the bandwidth will be reduced by half, as only four 10 gig connections are provided from 2104 IO module to each blade Server.

Comments

Popular posts from this blog

a file I/O error has occurred while accessing vmware converter

While converting physical Windows 7 machine to Virtual machine of infrastructure type, I got this error. The error seems it is unable to read/write source or destination datastore.

I have installed VMware-converter-en-6.2.0-8466193 on Windows 7 physical machine with option locally selected. (not at server/client option)

All of my ESXi servers are connected to the vCenter Server, so I had to use vCenter Server's IP address to send this physical machine to the virtual world.

The issue i found was with the dns resolution to the vCenter Server's hostname. Since I am not using the same dns server on the Windows 7 client machine. So I updated the host entries manually for the vCenter Server's hosname to it IP address.

After adding dns eteries to the hostfile of windows 7, I am not getting this "a file I/O error has occurred while accessing vmware converter" and the migration has started.

Connection control operation failed for disk 'ide1:0'

I was getting this error while removing Operating System ISO image mounted on the Virtual Machine.

What worked for me, is
1. Uncheck the "Connected and Connect at power on" from Device Status.
2. Then Change the Device type from "Datastore ISO File to Client Device" Radio Button
3. and press OK to save the changes.

Note:- I was able to remove the mounted ISO only by directly logging to the ESXi at https://esxi-ip-address/ui

where it asks

"The guest operating system has locked the CD-ROM door and is probably using the CD-ROM, which can prevent the guest from recognizing media changes. If possible, eject the CD-ROM from inside the guest before disconnecting. Disconnect anyway and override the lock?"

You need to select yes to eject the CD-ROM and then remove the ISO file successfully.

GNS3 Docker Error while creating node: Docker has returned an error: Cannot connect to host docker:80

Error while creating node: Docker has returned an error: Cannot connect to host docker:80 ssl:False [No such file or directory]

After adding docker template for Alpine Linux in gns3, you get above mentioned message when you want to use alpine linux in GNS3.

To get rid of this message you have to install Docker by following below link
curl -fsSL https://get.docker.com/ | sh

If you do not have curl installed then instal curl first with below command.apt-get install curl
After installing Docker you need to add your user name in the docker group with the following command. $ sudo usermod -aG docker your_username

Verify if the docker service is started with following command$ service docker status
If docker is not started then start with following command $ sudo service docker start
Logout from GNS3 Virtual Machines and log back. Start gns3 and use alpine linux.