Linux NIC enumeration and Dell servers

Once again I am running into the weird issue where at install time my NICs are enumerated one way and after a reboot another. This first happened to me in 2007, while installing Oracle Enterprise Linux (OEL) 4u5 on a Dell PowerEdge 2950. The on-board NICs were numbered 'gb1' and 'gb2' but enumerated 'eth1' and 'eth0', respectively. Strangely, the problem went away silently and just now reappeared in OEL 5u3.

Today I am using new R11 servers from Dell, the R710 with two dual on-board Broadcom NICs as well the quad-NIC add-on from Intel. At boot, my 'eth0' seems to be what I expect it but after a reboot it becomes 'eth4'. Found an updated white paper from Dell, listing a work-around: nic-enum-whitepaper-v4.pdf.

Comments

Preventing PuTTY timeouts

Just found a great tip to prevent timeouts of PuTTY sessions. I'm fine with timeouts by the host, but in our case the firewall kills sessions after 30 minutes of inactivity... When using PuTTY to ssh to your Linux/Unix servers, be sure to use the feature to send NULL packets to prevent a timeout. I've set it to once every 900 seconds, i.e. 15 minutes... See screenshot on the right.

Tuning the nscd name cache daemon

I've been playing a bit with the nscd now and want to share some tips related to tuning the nscd.conf file. To see how the DNS cache is doing, use nscd -g. nscd configuration: 0 server debug level 26m 57s server runtime 5 current number of threads 32 maximum number of threads 0 number of times clients had to wait yes paranoia mode enabled 3600 restart internal passwd cache: no cache is enabled [other zero output removed] group cache: no cache is enabled [other zero output removed] hosts cache: yes cache is enabled yes cache is persistent yes cache is shared 211 suggested size 216064 total data pool size 1144 used data pool size 3600 seconds time to live for positive entries 20 seconds time to live for negative entries 66254 cache hi...

Dell Linux - OMSA Hardware Monitoring

Just getting started using Dell's OpenManage Server Administrator (OMSA) on our Oracle Linux platform. There are some confusing instructions going around so it's not immediately clear what to do, hence my blogging here. :) There is a site on Dell - Hardware Monitoring , as well as a wiki with instruction on how to setup their OMSA tooling using yum or up2date. [update]My first update for their instructions: be sure your server has Internet access, as most servers will use a proxy or so. use export http_proxy=http://yourproxy.example.com:port to configure it just for the session, and setup up2date to use an HTTP proxy by editing the settings in /etc/sysconfig/rhn/up2date .

Oracle: Unbreak my Linux Heart

Search This Blog