Can't access my server's web interface ONLY idrac6 is available

Hello

I would change the iDRAC IP to something new like 192.168.1.21, restart, and check the connection. If it connects then change it back to .20 and test again.

It could be an issue with the iDRAC not operating on the IP it has listed, but it is more likely a network or cabling issue.

Thanks

I apologize but some browser plugins were blocking my ability to post earlier and that was my third attempt. 

I neglected to mention that I am not trying to access idrac at all.  I just want to get to the web interface of my OS on 192.168.1.20.  Definitely not a cabling issue because the server is plugged directly into a brand new switch with only basic configuration at this point.

I'm not sure changing the idrac ip is going to accomplish what I am looking for.  I'm just confused as to why dirac took over my ethernet ports.  This was never an issue before.

SK

192.168.0.120.  It should have a static address of 192.168.1.20.

I plugged a monitor in and the server boots normally and gives me the login prompt telling me to go to 192.168.1.20 to manage but that IP address is not available on my network. 

What is the IP you are looking for?

You refer to the iDrac as having 192.168.1.20 for it's IP, but then refer to that same IP as the web address for the CentOS server (web server?!).

If both have the same IP, you may find that the CentOS system is finding the conflict and not bringing up the interface. 

The steps i would look at would be;

1) Is the interface up (CentOS)

2) Is the webserver running? (CentOS)

3) Can I curl/wget localhost (CentOS)

4) Is my firewall on/blocking TCP:80/TCP:443 from coming in AND going out?

If these are all fine, then the CentOS aspect is fine and its purely networking..

Next steps:

4) Can I Ping the gateway? (CentOS)

5) Can i ping the gateway? (Switch)

6) Does the switch show any issues on the ports?

7) Is the port in the correct VLAN/Tagging configured as expected (both for the switch AND CentOS).

8) Is your client your attempting to access the web server from on the same switch/VLAN/Port Config?

9) Are you running a DHCP server that is on the same subnet/providing IP's on that subnet?

10) Any conflicts?

That should hopefully highlight any concerns, and if all good by that stage it gets a bit darker!

That's strange!

Can you plug directly to the server from a desktop/laptop and connect to the web server?

Are there any logs showing anything in the httpd logging files?

Is there any thing else on the switch and does that all work? Have you tried changing ports?

Maybe check the httpd.conf for anything?

If you do a netstat -tulpn does it show ::80 or 192.168..1.20:80?

I assume ifconfig shows the correct IP and the ifcfg-eth0 shows an expected configure?

Journal -xe show anything?

Very strange.

The CentOS IP is 192.168.1.20.  when the server is booted up, it is showing on my network as 192.168.0.120 which is the IP for IDRAC which has never shown up before like that

1.  CentOS is up

2.  Web server is running

3. Not sure.  will check tomorrow

4. No firewall blocking

4. Not sure.  will check tomorrow

5. yes

6. No issues on any of the ports

7. No VLANs setup yet.  This is a very vanilla install for now

8. yes, accessing from the same switch.

9. DHCP server is providing IPs on the 192.168.1.0 subnet

10.  No conflicts.  All DHCPs are 50 and up.  Only 4 other devices with statics on the network currently and they are 1-4

I'm really at a loss.  All we did was physically move the server 5 miles up the road.  Should be a straight forward plug and go.

OK.  So here's the rub.  Another R610, This one running Windows Server 2008 is doing the same thing.  I can log into Windows on boot but it is showing as an unidentified network with no internet access.  Logging into the switch, it is showing, again, that a device with the IP of 192.168.0.120 is connected to that port.  What the ***?  Why, after 9 years, would idrac start taking over the NIC at boot and not pass any data to these operating systems?  This is completely nuts.  

To answer a previous question: There are other devices plugged into the switch and all operating normally.  The cabling is all brand new and has been tested and certified.  Thats a non-factor here though because both of these servers are plugged directly into the switch.

Aaaaaaaand.  Magically it just started working at 3pm today on both servers.  I have no explanation.  No config changes, no moved cables.  They just came up and started reporting properly on the network.

/confused