I just installed CentOS 5.2 on a mini Atom server and it wont recognize the nics. Not sure what kind they are, think they are Intel. (built in)It's the first time this has happened to me. Where do I start to get it to recognize the nics? Normally it works out of the box.
View 5 Replies
I am looking into 1026TT-TF and 6016TT-TF for a CentOS 5.4 or 5.5 64bit installation:
SuperMicro 6016TT-TF
SuperMicro 1026TT-TF
It will be used as a Web-server mostly. Since they are twin nodes, one node will be one strong firewall. I have been checking all over and I can't find any driver, bios, or issues with this specific motherboard from Supermicro and Intel 5500/5600 series CPUs. Is there anything that would concern you with these servers?
I am also looking to put in a 4-port Gigabit LAN card into one node which I doubt makes any difference in the whole equation. Further more, and most importantly, the first one takes only 2.5" HDDs and the second option accepts 3.5" HDDs. Other than size availability and price, are there any concerns regarding performance when chosing one over the other? System which accepts 3.5" HDDs only takes two per node so I have to opt for 1TB drives. For the 2.5" system I can go with 4 of 2.5" HDDs of 500GB in size. Either of options selected will be setup in RAID-1.
I am trying to install CentOS 5.4 64-bit on a server with two NICs, one of which allows for iSCSI boot. I want the NIC that allows for iSCSI boot to connect to the iSCSI target on my 169.254 subnet. I want the other NIC to be connected to my 192.168.1 subnet so that it can reach the Internet for the CentOS Network Install.
Anaconda only configures one NIC, leaving me with an iSCSI target and no Internet or with Internet and no iSCSI target. Is it possible to configure both NICs in Anaconda?
configuring DHCP server with two NICs. I need DHCP server with 2 NICs:
eth1 - 192.168.103.11
eth2 - 192.168.123.11
The client also has two NICs and suppose to receive ip addresses eth1 from 192.168.103.0 and eth2 from 192.168.123.0 Here is the dhcpd.conf from dhcp server:
ddns-update-style interim;
authoritative;
ignore client-updates;
[code]....
I have a client with a pair of Supermicro 6025B-T servers that he wants to have Ubuntu 10.10 64bit Server running on for VM/Cloud experimenting. He needs these to be set up RAID 10. I can go into the Adaptec utility and make the array and make it bootable and get to the point in the installer where it asks me if I want to use the SATA array - then it gets to the partitioning screen and the array is nowhere to be found.
View 1 Replies View RelatedI have updated bind using yum on a Centos 5.3 server, after restarting, I have this error now.
Error in named configuration:
zone localhost/IN: loaded serial 42
/var/named/mydomain.hosts:20: unknown RR type 'SPF'
My version of is : bind.x86_64 30:9.3.6-16.P1.el5
I have two NICs and both having different IPs and Default Gateways. Now CentOS by default picks only one default gateway and puts entry in routing table (route -n). I want to keep both default gateway in active mode to achieve redundancy. For example if traffic enters through eth0 then it goes out using default gateway of eth0 and if traffic enters from eth1 then it goes out using default gateway of eth1. I use command route add default gw 192.168.0.1 netmask 0.0.0.0 dev eth2 then both default gateways becomes active. Now I want to make sure that when server reboots both default gateways are setup. For this I wrote shell script/sbin/route add default gw 192.168.0.1 netmask 0.0.0.0 dev eth0/sbin/route add default gw 192.168.0.10 netmask 0.0.0.0 dev eth1I am calling this script via /etc/rc.local but it doesn't work on boot time however once server is booted and I execute script (sh script.sh) then it works fine.
View 1 Replies View RelatedI have a motherboard which has 4 x 1Gbps Ethernet controllers. I would like to use it as a Gateway for my home network. I have a static IP from my ISP which I can use to configure eth0 (I haven't done it yet as the LE-565 is currently sitting behind my Netgear router until I've got DHCP working). I would like to use eth1, eth2 and eth3 for my LAN. How do I set things up so that DHCP is handing out IP addresses on the same subnet (192.168.0.0/24) on all three interfaces?
P.S. I think what I'm asking is: how do I combine all 3 interfaces to behave like a switch (ie. just like my Netgear router)?
I have a Proliant DL 120 G5 with CentOS 5.4 and I have installed a Brodcom Corporation Netxtrem BCM 5722 Gigabit Ethernet PCI. So I have two interfaces: eth0 broadcom eth1 Intel The eth1 works, instead eth0 don't work. I can ping itself and 127.0.0.1 but I can't ping the gateway. The results of netstat -nr is:
[code]....
My setup is as follows:
eth0 - lan ip
eth1 - WAN ip
I have installed a sip server on the box. From the box I would like to access machines on wan and lan. First of all, is it possible? If yes, I have setup up the nics with default wan gateway. However, when I try to ping wan url, no response. Are there other things I need to do to accomplish this?
Just something that struck me while working on our virtual servers today.
I have bonded 3 NICs at the host in Ubuntu Server 8.04 LTS. They are using mode 0 for Round-robin. Point is to increase the speed/performance of all the servers, but mainly the fileserver. The fileserver is a virtual server running Ubuntu Server 8.04 LTS on VMware Server 2.0.
1) I noticed the NIC in the slave OS reported link speed as 1000 and Im unable to change it as the NIC (virtual one) doesnt support it. Does this not really matter, as the NIC doesnt exist, and it will run at higher speeds anyway? Or do I have to remove the bond on the host, bridge all 3 interfaces from the host to the slave OS, and then make a bond in the slave OS?
2) While at it, does mode 0 only increase performance on data being sent from the host or does it also increase the available incoming bandwidth?
I have a program that attaches to an interface. I can run two copies of the program on two systems (each running one instance), connect it to a switch, say 1.1.1.1 & 1.1.2.1. In this configuration two instances of the program can communicate and everything is fine.
Now, to reduce cost, it want to use only one system with two nics connected to the same switch, running two instances of the above program, each instance attached to two interfaces respectively on the system. I have the following settings:
eth1 Link encap:Ethernet HWaddr XXXXXXXXXXXXXXX
inet addr:1.1.1.1 Bcast:1.1.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
eth2 Link encap:Ethernet HWaddr XXXXXXXXXXXXXXX
inet addr:1.1.2.1 Bcast:1.1.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[Code]...
I have configured CentOS 5.4 as a router/firewall (iptables) as such, and it is working fine:
eth0 - Public IP/Intenet, DHCP
eth1 - 192.168.0.0 internal "net1"
eth2 -10.0.0.0 internal "net2"
I want to add a fourth NIC, eth3, which will be assigned its own Public IP/Internet address (thru DHCP; my ISP provides two). The purpose it to route all net1's internet-bound traffic through eth0, and all of net2's internet traffic to eth3. This allows me to use one router/firewall machine instead of two separate ones. I anticipate that without some specific routing instructions, the default route will be eth0 for all net1 and net2 internet traffic (eth3 will be ignored).
I thought of using just one NIC (eth0) but create an alias (eth0:0), but IPtables (and possible DHCP) can't differentiate between the two (besides, nics are inexpensive). Is there a way to do this through routing commands, or even use iptables prerouting/forward functions (or is using iptables problematic)?
I have a whitebox server with three network adapters, two gigabit adapters using the intel 82573V chips, and an intel pro/100 adapter based on the 82562 chip. These are embedded on an MSI motherboard. None are passing traffic.I initially booted the box using a Knoppix 5.0.1 CD, and the NICs worked fine. When I installed CentOS 5.4, no joy.Interestingly, Intel recommends the e1000e driver (which I am using), but the Knoppix CD used the e1000 driver. Anyway, I pulled an updated e1000e driver from elrepo,installed it, and verified that it was in use with 'ethtool --driver eth2', and the correct driver/version was displayed.
Symptoms are no traffic passes, rx/tx packet counts in ifconfig are both 0 (no errors, either). Routing table looks fine; three routes: one for 169.x.x.x, 172.16.x.x (my subnet), and one for 0.0.0.0, all destined for eth2, and all up. When I ping 127.0.0.1, and the local adapter address, I get good replies. As soon as I ping a remote host on my subnet, I get 'Destination host unreachable'. Now, at one point, I actually got it to work. I applied a small patch from Intel to change a value in the EEPROM, rebooted as instructed, and the adapter came up and passed traffic. I did a 'yum update' to update my packages, and shortly thereafter, everything stopped working again.
i have a Server, which has 2 nics installed. Each of those is connected to a router, which is connected to internet. On the server, i have apache, maillserver and im-server running. On the other hand, also squid, dansguardian and clam are running. so now: via eth0 i would like to have just the traffic, which is requested from outside (the big bad internet..) to my server (apache, mail, etc). via eth1 i would like to have all OUTGOING (also to the big bad internet) from the server, which is requested by a internal client. And of course all requests to my own server
both nics shall route their traffic to their own router. For better comprehension please consult the enclosed graph. Until now, i did not find a good solution, the default route is set to the traffic from eth0, if not, no external request will find back to a client do you have a idea how to handle this the easiest way?
I am currently investigating channel bonding for rhel5.5.Is there any way I can create one bond from nics on two different linux machines.They will be a cluster without any clustering software like beowulf or LVS.There will be a cluster interconnect through which they can communicate.Should I tweak the bonding module??
View 3 Replies View RelatedI have a clean installation of Ubuntu Server 10.04 x64 on an HP Proliant DL380 G3. It has two Broadcom NICs in addition to its ILO. During the installation, both NICs were listed... but neither was able to pull DHCP, nor did they function with manual settings. The first NIC is currently connected and is known good. So I left it alone and figured I'd troubleshoot it later (which is now). This server is going to be a VMware Server host. I wanted to install ESXi on it, but it doesn't like the old server's cheap ICH RAID controller.
[Code]...
I noticed here it says they're disabled. so I thought perhaps this was a 64-bit driver issue. So, I booted my trusty Ubuntu desktop 10.04 32-bit live cd, and the NIC works fine. Now, here's where it gets weird. Seeing that, I booted it to Ubuntu server 10.04 32-bit installation from a flash drive, expecting to see the NICs working fine during the installation.
I am trying to setup a HP blade (BL460) server with 2 nics on sles10sp3. I want one nic to connect to a management vlan and and second to connect to the standard network. It should be possible for a desktop in the standard network to connect to either nic by providing the correct ip address.use this server as our first virtualisation hosts server using Xen. I dont want traffic used to upload / download images to the server through nic1 to effect the users traffic on the standard network on nic2. However any attempt at routing (which Im not good at) has led to the tx traffic all going out the default route (users subnet).
Each time I setup the nics via yast2 lan I can get the standard lan nic working ok. but cannot get the management nic working correctly. The server can ping a workstation on another vlan, but the workstation cannot ping the management nic. The default route appears to be forcing all traffic on the host out through this route, which I presume is normal behaviour. Using tcpdump I can see the ping packets received by the server, the server then responds through the default gateway, which the workstation does not see.
However, this normal behaviour will result in extra traffic on the users network when image downloads are initiated from the management interface.If I use a 172.24.1.0 network routed through 172.24.1.1 router setup as our management vlan , and 200.200.1.0 with router 200.200.1.1 as our lan for general users. Where server ips are nic1 10.1.1.10 and nic2 200.200.1.10 My workstation would be 200.200.1.10. If I ping the server at 10.1.1.10
I get no response. If I ping the server at 200.200.1.20 no problem.
Basically I used the network setup recommended by vmware to manage a virtual server. I actually have 4 nics, I thought by just talking about 2 nics the problem would be easier to explain. vmware specify that two nics should be used for management and two for the Lan. This is what I am trying to achieve, but both subnets must operate independently.
Did fedora 11 compatible to Geforce 95GT super? or did fedora 11 compatible to mother board SuperMicro X8SIE? bcoz I cant install my Video card.
View 7 Replies View RelatedI have had a Supermicro X7DCL-3 motherboard based machine, running CentOS 5.2 x86_64, recently upgraded to 5.3.Strangely enough, although I must have installed the 5.2 using DVD disk, the running system does not show the DVD drive. The machine was not used very much so I noticed that only today, after the update. There is no trace of it in 'dmesg', thera are no /dev/cd* and/or /dev/dvd* devices. The IDE controller is IT8213 (as shown by 'lspci'). In 5.2 kernel (2.6.18-92.el5-x86_64) lspci says "unknown device". I have checked the /usr/src/kernels/*/.config files and both kernels (5.2 and 2.6.18-128.el5-x86_64 of 5.3) seam to have the support for that controller added into the kernel:CONFIG_BLK_DEV_IT821X=yAny idea why it is not working? The Supermicro has apparently noticed this also as their OS compatibility chart lists the IDE interface for that motherboard as supported up to RHEL 5.1 but not for 5.2.
View 2 Replies View RelatedI recently set up a new web/file server with 9.10 server x64 with 2 NICs and I am trying to configure eth0 to respond to my LAN for internal samba filesharing and eth1 to handle website/ftp requests on my static IP, but whenever eth0 is up the server is not accessible at 173.XX.165.65 for web or ftp but both work fine at 10.1.10.100. When eth0 is down, public IP works fine. I have set /etc/network/interfaces like this:
Code:
# The primary network interface
auto eth0
iface eth0 inet static
address 10.1.10.100
[Code].....
I have installed Ubuntu 64 10.04 server. I have two nics and have set them up to both be static with their own IP with the correct gateway, network, broadcast, subnet and dns-nameserver. When I have both enabled, I can ping local pc's but I can't ping Internet sites like Google nor can I get out to the Internet with apt-get or Lynx.
If I disable one, then I am able to get out to the Internet. All my configs look good, and it does not matter which one I disable, just so long as there is only one NIC on, everything is good.
On a Supermicro 6027R TRF, I run the latest Debian Wheezy. I have a problem with the server, because I cannot control fan speed anymore.
My plan was to control the drive bay LEDs via software, so I installed i2c-tools and ledmon packages. While I was at it, I also installed fancontrol and lm-sensors.
Then I ran the Superdoctor program (distributed on the Supermicro website) that prints information on fan speed, temperatures and system voltages. I ran it only once by executing the command "sdt" as root. After the command completed, the 3 system fans started spinning at max RPM. And this is extremely noisy! The program had run before, but without spinning up the fans.
Since then I didn't manage to regain control of the fans. Even after a reboot the fans start to speed. Also, removing the installed packages again does not work.
I also tried to control the fans with the fancontrol package, but this fails because I do not have a correct fancontrol config file. I am supposed to run pwmconfig first to create such a file, but this fails as well ("/usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed")
I have collected the output of sensors-detect, sensors and pwmconfig here: [URL] ....
I have a copy of the DVD Iso for centos 5.3. I downloaded the updated packages to the Centos directory and then ran the repomanage perl script to remove the old files from the directory. I then ran the createrepo and the new iso image with the script code below.
baseDir=`pwd`
rhelBuild=`pwd`/dvd-iso-contents
rm -f CentOS_1.0.0.iso
echo "Updating repository"
dvd_discinfo=`head -1 $rhelBuild/.discinfo`
echo "$dvd_discinfo
[Code]...
I am using VMWare to test the build, so I have the cd pointing to the iso image. I get the CentOS to start up find and dandy asking the questions for the interactive boot. It gets thru the stage of checking dependencies and then when it starts to copy down the image to the "harddrive" that is when the problem occurs.
One of the updated files is file-4.17-15.el5_3.1.i386.rpm (file-4.17-15.el5.i386.rpm was removed using repomanage), but the loader is looking for the removed file. I've looked thru any dependencies, but nothing specific for the removed file, all are asking for /usr/bin/file with no specific version numbers. I have run a rpm -test on all the rpms, but haven't been able to look thru that to see if there is a specific request for the version.
I did try this, but it just moved on to the next file. I did not replace the file version, but then it found another problem that was the same as this, the updated file is in the repo, but it is requesting the old version. I looked thru the fileslist and others to see if maybe that was the problem, but they were updated to the new versions.
I have a CentOS 5.3 box with three network interfaces in it. Each interface is attached to a separate VLAN and I want traffic to stay on each network segment.What I can�t figure out is why I cannot get each interface to have its own gateway and everything gets sent through the default gateway.The basically takes my possible 3Gb total bandwidth and throws it down a single 1Gb pipe.Then on top of that, if I take down the interface (ifdown) that has the current default gateway,I loose contact to the other two interfaces.When I look at the routes, each one of the interfaces shows the gw as 0.0.0.0 and defers to the default route. So I delete the route and try to add a new route with:
[root@testsan ~]# ip route add 10.1.15.0/24 via 10.1.15.1 dev eth2
but end up with the error:
RTNETLINK answers: Network is unreachable
[root@testsan sysconfig]# cat network
NETWORKING=yes
NETWORKING_IPV6=no[code].....
I had a problem with centos 5 not recognising usb sticks dispite installing and using centos 5 on different computers. This was cured by slotting the stick in imediatly after start up which seems odd but I have seen others having similar problems.
View 6 Replies View RelatedI installed new CentOS 5.5(X86_64) on my server. My server has 48 G RAM (12*4G) and can be found when starting server. Moreover, I installed dmidecode software to detect the memory. This software can find all the memory. I used command (top, cat /proc/meminfo) to check memory. Both commands can only find 33G RAM. uname -a command output like this: 2.6.18-194.el5xen #1 SMP Fri Apr 2 15:34:40 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
View 1 Replies View RelatedI am having a problem trying to get my UPS (APC BACK-UPS ES 750) to be recognized (via USB) on my new CentOS 5.4 system. I had no trouble a while ago getting it to work on an old Fedora Core 3 system, and I don't think the problem is even with the apcupsd package because at the very least, I expect to see the device appear when I plug in the usb cable and use (from the APCUPSD User Manual):
View 7 Replies View Relatedi have installed centos 5.1 but it won't recognize 2nd nic card (eth1). i was unable to install the driver supplied by the cd. i am using intellinet gigabite pci network card. the network card recognize by centos 5.3 but i need to use centos 5.1. i also tried another intel gigabite adopter but it also won't recognize by centos 5.1.
View 2 Replies View Relatedi can't see the USB Blaster when i plug in my computer
View 1 Replies View Related
