Archive for the ‘Networking’ Category
We needed to update the firmware for some Intel XL710 nics which only has a Windows or Linux firmware utility ATM so we booted KNOPPIX Linux and tried to patch the firmware only to be presented with:
./nvmupdate64e: No such file or directory
The binary was there, the OS was 64bit (the same as the binary) so what was going on. After much head scratching it turned out that the kernel was 64bit but userland is 32bit only for KNOPPIX meaning there was no way to run the the provided 64bit binary.
Fix use another distro…
We recently found ourselves trying to install Windows 2008R2 on a 2 year old Intel Sandy Bridge system with an Intel 82579V onboard network card.
As part of the install, we pushed out the standard Intel ProWinx64 drivers, along with Intel Chipset Software installer to install all missing drivers.
Annoyingly this left us without a working network card, which is slightly bit problematic when trying to finish off the install remotely.
It turns out the fix is to extract the ProWinx64.exe file to a folder on the desktop and update a single inf file:
Find the following section
ExcludeFromSelect = \
This needs replacing with just:
Further down in this file, you’ll need to update the [Intel.NTamd64.6.1] block to also include:
; DisplayName Section DeviceID
; ----------- ------- --------
%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502
%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503
Following on from this, you should be able to run APPS\PROSETDX\Winx64\DxSetup.exe
This will then do the install with the local edited files and install the missing drivers
Newer Supermicro IPMI interfaces come configured by default in “failover” mode which means that the IPMI will bind to either the dedicated IPMI NIC port or share with one the the machine NIC ports.
This can cause IPMI to come up on wrong NIC and hence be inaccessible if the dedicated NIC doesn’t detect a link.
You can use ipmitool to change this behavour
First query the current setting:
ipmitool raw 0x30 0x70 0x0c 0
The result will be one of the following
0x00 = Dedicated
0x01 = Onboard / Shared
0x02 = Failover
Next to configure it you can use one of the following.
For older models:
ipmitool raw 0x30 0x70 0x0c 1 1 0
For X9 motherboards:
ipmitool raw 0x30 0x70 0x0c 1 0
References for this can be found here:
Once you know its really simple the key is ensuring that the extreme end is using “dyanmic” sharing which enables LACP.
The following example configures a LACP trunk of 2 ports between an Cisco 6500 port 8/10, 8/11 and Extreme 400-48t ports 1, 2
interface Port-channel1 switchport switchport trunk encapsulation dot1q switchport mode trunk interface GigabitEthernet8/11 switchport switchport trunk encapsulation dot1q switchport mode trunk channel-group 1 mode active interface GigabitEthernet8/11 switchport switchport trunk encapsulation dot1q switchport mode trunk channel-group 1 mode active
enable sharing 1 grouping 1,2 dynamic
You can then use “sh ports 1 sharing” to check the Extreme end and “sh etherchannel 1 summary” to check the cisco end