Intel x520-t2 NIC problem on Windows Server 2012 (Nic keeps disconnecting/reconnecting constantly)

Hello Daniel,

Thanks for responding.  There are not any port configurations on the switch yet.  Just completed the initial setup and only enabled jumbo frames on the switch.  Strange I "think" I may have already tried that driver on my WServer2012 machine (said was not for this os), but I will download again using the link you gave me and update this thread immediately.  I disabled jumbo frames on the NIC as a test but that did not make a difference. 

Hello rhoninpowers

If you would like to provide the configuration of the interfaces that the NIC is attached to on the switch I will let you know if there are issues. Also, let me know if you have the NIC configured for LACP or any other advanced features. Since this is a beta operating system the driver included with the OS is probably the best to use. If that driver is causing problems then you can try the latest we have available:

http://downloads.dell.com/FOLDER00410451M/1/Network_Driver_8D5KK_WN32_13.5.0_A00.EXE

You can get the interface information by performing a show run, or running:

show interfaces configuration

or

show interfaces configuration gi1/0/1

If you do not specify an interface it will show the information for all interfaces.

Thanks

Okay, let's try to narrow down the problem.

You have the NIC connected to the 1GB ports and not the 10Gb uplink ports correct?
Is the NIC correctly auto-negotiating to 1Gb?
Have you tested the switch with another NIC to verify it is functioning?
Have you tested the NIC with another switch/router?

If we can rule out a hardware or configuration issue then it becomes a driver problem. If that is the case then you will likely have to wait for the driver supplied to Microsoft to be updated.

Thanks

From the guide I have the HDMI Port 2 on the top switch and HDMI port 1 used on the bottom switch to link and manage together....should I reverse them or???

That is fine.

Let's see if spanning tree is blocking any ports. Run this command and post the output:

#show spanning-tree

After you copy the output then make sure the interfaces connected to the NIC are in access mode. This will remove any VLAN tagging and should also cause them to not be blocked by RSTP. Here is an example of how to put an interface into access mode:

Console(config)# interface gigabitethernet 1/0/1
Console(config-if)# switchport mode access

Thanks

Update:  I tried the driver pack and it is the one that I had downloaded and tried.  I tried this to be sure and got the error message that the package was not for Windows Server 2012.

Serial connection (Top Window) shows links bouncing and Port config (bottom window) shows the port config (nothing changed.)

On the server the error is on the ixgbi and will go back between connecting/disconnecting as mentioned

I disabled one of the nics...and the other nic grabbed an IP and stopped bouncing.  It does look like a driver issue.  Thanks for the link...I did not read closely...sweet!!!!  although I could fill a book with OMSA questions.  thanks.

Ahhh yes...I actually just downloaded that (Centos) a few days ago to do some Hadoop testing.  2 questions before I go...how do I surpress the updates in the serial window on the switch and is there a way to "redirect" that output over the network so I can view from other machines?  (I don't log into switches much and I am really rusty...wow.  :)

thanks for the help.

Ok...as a test I unplugged 1 of the adapters and put it into an old linksys switch that I unplugged and it's doing the same thing on that switch.  

Adapter a has started working and adapter b has stopped (almost like STP found a nother path or something???)  here the log fromt the switch...notice that only the second port on the x520 is having problems.  The other port has "stabilized" I guess and seems to be working????

Below is the nics on the server (note as above adapter A appears to be working fine now????)

I am completely lost at this point.

how do I surpress the updates in the serial window on the switch

This command will allow you to set what updates are shown in the console window. The default is informational:

Console(config)# logging console ?

is there a way to "redirect" that output over the network so I can view from other machines?

You can connect to the switch from any location on the network if you assign an IP address to the management VLAN(VLAN 1). I would recommend that you create a password protected user account if you have not already:

console(config)# username ###### password ####### level 15

The command sequence to assign an IP address to the management VLAN is something like this:

console# configure
console(config)# interface vlan 1
console(config-if)# ip address 192.168.1.45 /24
console(config-if)# exit
console(config)# ip default-gateway 192.168.1.1
console(config)# exit
console# show ip interface

You will then need to enable the connection method you want to use(telnet or SSH). Telnet will send plain text and SSH will encrypt, so SSH is more secure but requires a little more setup. Telnet setup is just:

console(config)# ip telnet server

You can then use a command line interface within most OS's or a utility like PuTTY to connect to the swtich. For more detailed information for configuring SSH you can look at page 203 of the CLI guide. It is quite extensive, so I'm not going to type it all up.

Thanks

I have the exact same issue with a x520-da2 on a R810 with Windows 2012 RC.

Disabling one of the 2 ports fixed it.

I'm guessing this will be fixed in the RTM release.