VMware Cloud Community
arturka
Expert
Expert

Problem with network after BIOS update

Hi all

I've updated BIOS on one of my ESX3.5.4 server, after reboot vmnic chenge order:

Before BIOS update

vmnic0 ServiceConsole

vmnic1 - production|

-- NIC teamming

vmnic2 - production

vmnic3 - second network

After BIOS Update

vmnic0 ServiceConsole

vmnic1 - production|

-- NIC teamming

vmnic4 - production

vmnic5 - second network

Problem is with VMNIC4 - doesn't recive any packages, only sending it.

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:13286522 errors:0 dropped:0 overruns:0 frame:0

TX packets:13286522 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:2558453953 (2439.9 Mb) TX bytes:2558453953 (2439.9 Mb)

vmnic0 Link encap:Ethernet HWaddr 00:1A:64:33:11:80

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:49011839 errors:0 dropped:0 overruns:0 frame:0

TX packets:19698804 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:2851416041 (2719.3 Mb) TX bytes:4058190601 (3870.1 Mb)

Interrupt:145 Memory:d8000000-d8012100

vmnic1 Link encap:Ethernet HWaddr 00:1A:64:33:11:7E

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:29252798 errors:0 dropped:0 overruns:0 frame:0

TX packets:712861 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:2173588804 (2072.8 Mb) TX bytes:94632907 (90.2 Mb)

Interrupt:137 Memory:da000000-da012100

vmnic4 Link encap:Ethernet HWaddr 00:14:5E:A7:3F:E2

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:1035673158 errors:0 dropped:0 overruns:0 frame:0

TX packets:1182 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1888822192 (1801.3 Mb) TX bytes:92655 (90.4 Kb)

Interrupt:153

vmnic5 Link encap:Ethernet HWaddr 00:14:5E:A7:3F:E3

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:562449648 errors:0 dropped:0 overruns:0 frame:0

TX packets:1538228 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1027331799 (979.7 Mb) TX bytes:102008512 (97.2 Mb)

Interrupt:145

vswif0 Link encap:Ethernet HWaddr 00:50:56:4B:5F:7A

inet addr:10.128.208.63 Bcast:10.128.208.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:33074823 errors:0 dropped:0 overruns:0 frame:0

TX packets:19627290 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:1863922927 (1777.5 Mb) TX bytes:4000266747 (3814.9 Mb)

Name PCI Driver Link Speed Duplex MTU Description

vmnic0 06:00.00 bnx2 Up 1000Mbps Full 1500 Broadcom Corporation Broadcom NetXtreme II BCM5708 1000Base-SX

vmnic1 04:00.00 bnx2 Up 1000Mbps Full 1500 Broadcom Corporation Broadcom NetXtreme II BCM5708 1000Base-SX

vmnic4 0f:04.00 tg3 Up 1000Mbps Full 1500 Broadcom Corporation Broadcom BCM5715S Gigabit Ethernet

vmnic5 0f:04.01 tg3 Up 1000Mbps Full 1500 Broadcom Corporation Broadcom BCM5715S Gigabit Ethernet

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch0 64 4 64 1500 vmnic0

PortGroup Name VLAN ID Used Ports Uplinks

Service Console 0 1 vmnic0

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch1 64 5 64 1500 vmnic4,vmnic1

PortGroup Name VLAN ID Used Ports Uplinks

10.128.208.x 0 1 vmnic1,vmnic4

Switch Name Num Ports Used Ports Configured Ports MTU Uplinks

vSwitch2 64 4 64 1500 vmnic5

PortGroup Name VLAN ID Used Ports Uplinks

10.128.210.x 0 0 vmnic5

VMotion 0 1 vmnic5

I was remove vmnic4 from Vswitch and add back, nothing has changed. I've founf in vswitch configuration that vmnic4 doesn't see network range (check attachment) like vmnic1.

Any ideas what can be wrong.

Thanks in advance for help

VCDX77 My blog - http://vmwaremine.com
Reply
0 Kudos
5 Replies
MikeS1983
Enthusiast
Enthusiast

Hi,

Have you checked the port on the physical switch that connects to nic4? I've had issues in the past where absent network ranges and nothing showing up in the cisco dicovery protocol is caused by either a faulty cable/switch port.

Looking at you're before and after bios configs it looks like the service console still has the same nic and still has connectivity so you can manage the host.

I take it there is no VM's running on this host. Have tried deleting your vswitches and recreating them?

Mike.

Reply
0 Kudos
andosm
Enthusiast
Enthusiast

Hi,

you can also try to revert to original vmnic numbers. Info how to make it here.

--

Pozdrawiam/Best Regards

Andrzej

Pozdrawiam/Best Regards Andrzej
Reply
0 Kudos
arturka
Expert
Expert

Hi all

"I take it there is no VM's running on this host. Have tried deleting your vswitches and recreating them?"

I didn't delete my vswitches yet. I've just create next vswicht with vmnic4 attached to it, moved on test VM from another node in cluster and make a ping or RDP to VM and it doesn't work.

Tomorrow I'll delete all my switches and recreate them, maybe it will help.

"Have you checked the port on the physical switch that connects to nic4?

I've had issues in the past where absent network ranges and nothing

showing up in the cisco dicovery protocol is caused by either a faulty

cable/switch port."

I've been contacted with network team, seems to be like network switch and port are fine, but tomorrow I will call to local support and ask to change cable and later change network switch port.

Artur

VCDX77 My blog - http://vmwaremine.com
Reply
0 Kudos
bulletprooffool
Champion
Champion

Have you tried rebooting it again, just to make sure that the Nics do not re-order themselves?

The odd thing is that it seems as if a Nic 'went missing' Did you make any changes in the Bios or replace the physical NIC? Did your BIOS rewrite the MAC etc for one of your NICs?

If a Nic changes, it will keep a space for the old Nic and create a new number for the new Nic - so replacing is not as simple as swapping a NIC out.

One day I will virtualise myself . . .
Reply
0 Kudos
arturka
Expert
Expert

thanks for all of you for your answers

today morning I've found where is the problem, "foulty vmnic was plugged to INFA VLAN instead of production VLAN, now network team is changing configuration on switch port.

Artur

VCDX77 My blog - http://vmwaremine.com
Reply
0 Kudos