Jump to content

IBM X3650 M3, IMM unreachable (Webpage doesn't Load)

Go to solution Solved by Astrophel,
On 12/4/2023 at 3:16 AM, ieleja said:

If you try to ping your server?

 

ping -t 192.168.70.125

 

Is your DHCP server also think, that server get this address?

 

(your computer must have IP address within 192.168.70.0/24)

I ended up solving the problem but jumping into Linux and doing,

sudo ip addr flush dev eno1
sudo ip route flush dev eno1
sudo ip addr add 192.168.1.69/24 brd + dev eno1
sudo ip route add 192.168.1.182 dev eno1

 

To setup a static IP,  I set in the IMM settings and set it to "192.168.1.182" and made sure it was a static IP on the server's end. After that I was so relieved I forgot to close this forum but it took me 4 days to figure this out which is crazy. **After you do all this use ASU64 and set the IMM Http Service to Enable.** I also had to use Google Chrome because Firefox and other browser's refused to work.

20231203_212225.webp

2424242444.webp

I'm unable to access the IMM login page at all, i've reset the CMOS i've reset the IMM module back to defaults and I can't get anything out of it, i've tried all the steps I could on my end so now I reach out to see if anyone has worked with these or knows what's going can help. It's important I gain access to it because windows server won't install because I need drivers for it to see the RAID. (I plan on using Unraid after I test things out on that)

The Setup:

IBM Server x3650 M3 Duel Xeon X5680 6 core 3.33GHz 144GB Ram, 12, Hitachi/HGST 10K 600GB drives (Currently in RAID 5)

 

20231203_151150.webp

20231203_151118.webp

20231203_144827.webp

20231203_151106.webp

Link to comment
Share on other sites

Link to post
Share on other sites

If you try to ping your server?

 

ping -t 192.168.70.125

 

Is your DHCP server also think, that server get this address?

 

(your computer must have IP address within 192.168.70.0/24)

 

ad infinitum

Link to comment
Share on other sites

Link to post
Share on other sites

  • 1 month later...
On 12/4/2023 at 3:16 AM, ieleja said:

If you try to ping your server?

 

ping -t 192.168.70.125

 

Is your DHCP server also think, that server get this address?

 

(your computer must have IP address within 192.168.70.0/24)

I ended up solving the problem but jumping into Linux and doing,

sudo ip addr flush dev eno1
sudo ip route flush dev eno1
sudo ip addr add 192.168.1.69/24 brd + dev eno1
sudo ip route add 192.168.1.182 dev eno1

 

To setup a static IP,  I set in the IMM settings and set it to "192.168.1.182" and made sure it was a static IP on the server's end. After that I was so relieved I forgot to close this forum but it took me 4 days to figure this out which is crazy. **After you do all this use ASU64 and set the IMM Http Service to Enable.** I also had to use Google Chrome because Firefox and other browser's refused to work.

20231203_212225.webp

2424242444.webp

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×