VMware Cloud Community
avf925
Contributor
Contributor
Jump to solution

Adding 2nd NIC Kills ESX Server

All,

Thanks for taking time to read my post. Here is the environment and then my question.

3 - DELL R510 - Dual Quad Core - Intel Systems

The box has "2" Integrated NIC's

as well as "2" QUAD Port - PCI Intel Nics

NIC 0 - Integrated is the NIC the systems where installed on - and it is plugged into a standard CISCO GIG Switch, Tagged with VLAN 108

NIC 1 - Integrated is configured for iSCSI connectivity

SLOT 0 - PCI Quad Port NICs

Port # 3 is plugged into a TRUNK GROUP on a CISCO SWITCH with VLANS 108, 107, 104 and 110 on it

Port # 1 is used for the 2nd iSCSI connection

SLOT 1 - PCI Quad Port NICs

Port # 7 is plugged into another TRUNK GROUP on a CISCO SWITCH with VLANS 108, 107, 104 and 110 on it

All three of the servers are installed with ESX4 Update 1

When I go into vCenter to any of the three servers and go to the primary Virtual Switch in Networking, if I add either Port #3 NIC or Port #7 NIC to the virtual switch (it currently has integrated NIC 0 in it) the system disconnects from the network, and losses it's connection to vCenter, and the entire network. If I physically reboot the ESX server, it DOES NOT come back on the network. I have the VLAN tag in NIC0 set to 4095 to accept all VLAN's as well. ( I have tried it with and without the VLAN Tag of 4095 - same result)

Here are my questions:

1 - Why is this happening? How should it be configured?

2 - Is there a way to get NIC0 to come back onto the network without having to re-install ESX?

I've reinstalled these boxes many times now, and tried lots of variations of nic combinations, and they all end with the ESX server disconnected from the network and not responding.

Really looking for some good direction here . . . .please and thank you.

Tags (3)
Reply
0 Kudos
1 Solution

Accepted Solutions
jpdicicco
Hot Shot
Hot Shot
Jump to solution

Hmmmm, kinda shooting in the dark, but I think your next 2 steps are:

1) Get the MAC of the SC (vswif0) and check your switch MAC address table for thrashing across ports

2) On the console, use esxcfg-vswitch to first list the uplinks associated with SC port group, then remove the 2nd NIC. This should get your SC back live and leave the new NIC available to the vswitch, just not the SC port group. (And keep you from having to reinstall :-).

Happy virtualizing!

JP

Please consider awarding points for correct and/or helpful answers

Happy virtualizing! JP Please consider awarding points to helpful or correct replies.

View solution in original post

Reply
0 Kudos
3 Replies
jpdicicco
Hot Shot
Hot Shot
Jump to solution

Hmmmm, kinda shooting in the dark, but I think your next 2 steps are:

1) Get the MAC of the SC (vswif0) and check your switch MAC address table for thrashing across ports

2) On the console, use esxcfg-vswitch to first list the uplinks associated with SC port group, then remove the 2nd NIC. This should get your SC back live and leave the new NIC available to the vswitch, just not the SC port group. (And keep you from having to reinstall :-).

Happy virtualizing!

JP

Please consider awarding points for correct and/or helpful answers

Happy virtualizing! JP Please consider awarding points to helpful or correct replies.
Reply
0 Kudos
AndreTheGiant
Immortal
Immortal
Jump to solution

As I undestand you want to have a vSwitch with NIC0, Port #3 and Port #7? It is correct?

But this 3 ports have differenct configuration (for example one port is tagged the others not).

If you use trunk mode, then you have to tag your portgroup (and also the service console port).

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
Reply
0 Kudos
avf925
Contributor
Contributor
Jump to solution

Thanks for the help, this is exactly what I needed.

Reply
0 Kudos