Swapping hard drives to another chassis - Networking issues
Hey all. :) I recently posted this question over on FedoraForum, but as yet I've not had any feedback. Thought I'd try here, as well. For simplicity's sake, I'll just cut and paste:
Quote:
Two unavoidable things: A moderator on FedoraForum pointed out was that Fedora should not be used on a production server. I agree... sort of... but this was not my call. This is several separate LANs of a dozen or more servers apiece, all over the service area I drive to. It's unavoidable. Also, yes, they run FC6. I realize that we went beyond support for FC6 in about 2007. This server type was installed in 2007-2008 initially, and for our purposes we had to remain constant. We will not be upgrading. It is what it is. These servers run one proprietary application, that's it. So that's out of the way... Any advice? Since I posted the above, my efforts in troubleshooting have rather fallen flat. The most helpful documents I found are here: http://zenit.senecac.on.ca/wiki/inde...sses_on_Fedora This unfortunately does not work. We don't use Gnome/GUI (console only) for our purposes, but even under the system-network-config command line utility, there is no option for unbinding a MAC address associated to an ethernet port. https://bugzilla.redhat.com/show_bug...iple&id=212869 That bug seems to comment on the file /etc/udev/rules.d/70-persistent-net.rules not being present in older Fedora releases. Looks like maybe it started with FC8, not sure. Maybe relevant, maybe not... I've tried changing the HWADDR settings under /etc/sysconfig/network-scripts/ifg-eth0 (we only use the one port), but no dice. Yet. This is a tricky one. Sorry if I got confusing, but any help would be grand. :) -S2- |
One thing: I did mention that our older servers, running Debian work fine. Swap the drives into the other chassis, accept the drive configuration in ServeRAID, and the OS loads and that's it. One thing I'd really love to know is *why* it works there, but not Fedora.... could be helpful in troubleshooting this.
http://forums.debian.net/viewtopic.php?f=7&t=54894 The third response in that thread is long and has a few key points, but nothing that goes so far as to give a real answer, to me at least. |
Don't post to your own post. Makes it look like someone answered it.
Yep, I have seen Fedora do that. I forgot now what the issue was and the fix. I just ended up reloading it. From what I recall it was still trying to load up the other nic's. It was actually calling the new nics (supposed to be the same hardware) by new names like eth5 and eth6. There is a simple sort of fix out there but not sure what it was. |
A simple fix is what I'm hoping for.....I've figured for the past few days that it would be something simple-ish, at least. I did notice that after the drives were swapped, the eth0 and eth1 addresses changed, or went like you said to eth1 and eth2 or something like that. So I'm almost wondering if it IS a RAID controller configuration that has to be set? Only trouble is that these ServeRAID 8K modules don't have any kind of acceptance prompt when a new drive pair is inserted. It just starts to boot normally.
IBM servers have a CTRL+A option at boot during the RAID initialization phase, but that's just to modify or delete the existing RAID. I don't think it has a mini-configuration option anymore. As for posting to my post, sorry I'm not quite sure what you mean - the quoted section perhaps? |
Have you considered that in your original networking config you have directives to bind eth0/eth1/ethX to specific MAC addresses?
If the MAC address isn't seen in the new backplane then maybe your OS is assuming that NIC has gone and disables the config for it. We get something similar when we "clone" VMs in XenCenter which is what gave me the idea to suggest it. |
That's sort of what I think is going on, but I do not know how to fix it.
|
One thing I've noticed is that when the drives are initially swapped to the other chassis, the MAC addresses swap. eth0 becomes eth1 and vice-versa.
Very, very peculiar. I simply cannot figure this out! |
I've only seen this issue on Fedora. I did find the answer after looking for it but I forgot what it was. There is a solution out there but it isn't exactly worded easy to find as I recall. It is one of those things that I said that I will remember and then forgot.
|
Well it happens on RHeL too, I've seen it firsthand. Curiously, with that it kind of resolved itself after a number of reboots.
I think it's got to be something related to just changing the MAC. Post-swap perhaps since the OS seems to pick up on the hardware once it's installed (as designed). |
All times are GMT -5. The time now is 05:54 PM. |