Issue with XenServer Node
-
@scottalanmiller I'll reboot it again: I did try that.
-
Didn't work.
What all have you tested thus far? What lights are on on the switch, has the port been switched? Have you switched the port on the server itself? It's very hard to assist when I only get partial information. -
The server has been rebooted twice. The cable was switched from eth port 1 to 2, and the other end at the switch was removed and reseated. Still not reachable by ping from my computer on the network. I'll try another switch port, but I don't think that's it.
-
Different port on the switch, still no reply.
-
It's back on the network. It always was. Even though the IP was not changed in the management console, and it even showed correctly, when it booted up it somehow assigned itself to .26. No clue why, but refreshing the management settings put it right and I added it as a server to Xen Center again and it's connected and pingable on the network and all that good stuff.
-
@art_of_shred said:
It's back on the network. It always was. Even though the IP was not changed in the management console, and it even showed correctly, when it booted up it somehow assigned itself to .26. No clue why, but refreshing the management settings put it right and I added it as a server to Xen Center again and it's connected and pingable on the network and all that good stuff.
Awesome, thanks.
-
The IP address is pingable now, but it is still showing as disconnected in XenCenter.
-
@Mike-Ralston said:
@scottalanmiller How do I ping something from it? It's not a command prompt.
It should be, you have the other machine at a command prompt...
-
@scottalanmiller that was me when I was checking the connectivity...
-
Found what the issue was with the Red X.... it was crash dump files for the host.
Click on the server with the right mouse button. There you see "Remove crash dump files.
-
Got the SAN issue addressed too. That was actually a setup issue on the Drobo. If you don't select "Cluster" on the Volume tab it will lock out all but the first node to connect to it. Unselect that and then right click on the SAN in the pool and select "Repair" and it will attempt to connect again and ta da. All set.
-
@scottalanmiller said:
Found what the issue was with the Red X.... it was crash dump files for the host.
Click on the server with the right mouse button. There you see "Remove crash dump files.
But you still can't ping it?
-
@Mike-Ralston said:
But you still can't ping it?
Now we can. The IP address was 192.168.1.26 instead of 192.168.1.11. For some reason the changes hadn't saved.
-
@scottalanmiller The prompt on the server itself said 192.168.1.11, I wonder why it wasn't doing that on the network end...
-
There is a very high possibility that the IP it was operating on was the iDRAC's IP. I wonder if the iDRAC console somehow became the active connection.
-
@art_of_shred said:
There is a very high possibility that the IP it was operating on was the iDRAC's IP. I wonder if the iDRAC console somehow became the active connection.
That's an interesting thought. Not sure how that could have happened but since the IPs overlapped.... hmmm...
