[cisco-voip] Replacing motherboard in MCS-7815-I2 server --Ethernet issues

[Jason Aarons (US)]

It was likely beyond their experience level.  Did they open a case with
Red Hat support? Probably should have pushed them to do so.

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan
Charles
Sent: Thursday, January 31, 2008 10:10 AM
To: Kelemen Zoltan
Cc: Cisco VoIPoE List
Subject: Re: [cisco-voip] Replacing motherboard in MCS-7815-I2 server
--Ethernet issues

All of this implies there is a way to do it and Cisco TAC refused to
even try...


Jonathan

On Jan 31, 2008 2:26 AM, Kelemen Zoltan <keli at carocomp.ro> wrote:
>
>  This is probably a typical linux issue, that probably can't be solved
from
> the CCM 5.x walled garden >:) Unfortunately I have not seen neither
CCM 5.x,
> nor this problem happening with it, but I've seen the same problem
happening
> with other linux boxes. It's about changing NIC in a system based on
udev
> (probably all modern linux distros)
>
>  I think what happened to you could be very much the same thing:
>  - udev registers NICs based on MAC address as eth0, eth1, etc. and
when the
> system detects new NICs added (irrelevant whether the old ones were
removed
> or not) they will be added as eth2, eth3 etc (the next available, of
course)
>  - this means, that the GUI (probably) hardwired for eth0 will never
find
> the new NIC sitting on eth1, or eth2 etc.
>
>  on my gentoo linux, these reside in
> /etc/udev/rules.d/70-persistent-net.rules and the file is
autogenerated on
> bootup time.
>
>  for example, this file contains for me right now:
>  # PCI device 0x8086:0x4220 (ipw2200)
>  SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:0e:35:d8:bf:6c",
> NAME="eth1"
>
>  # PCI device 0x8086:0x103d (eepro100)
>  SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:0f:1f:a6:82:c0",
> NAME="eth0"
>
>  Bringing back the new NIC to eth0 involves deleting this file
rebooting /
> deleting / rebooting :-)
>  *for me* as I'm certain there is a better/nicer way to do it, but I
don't
> know enough about udev myself, to do it more elegantly (and I'm not
sure why
> it takes me two reboots, but I know from experience, that this works
:) ).
>
>  I hope from these ideas Cisco developers could figure out a solution
for
> changing NICs.
>
>  Or maybe I'm mistaken and this has no relevance at all ;-) just my
two
> cents.
>
>  best regards,
>    Zoltan
>
>
>
>  Erick Bergquist wrote:
>  FYI,
>
> The solution to this was to reinstall the system from scratch. :( :(
>
> We worked with TAC for along time and different people there and
> developers but could not get past this MAC address issue and could not
> get the Eth0 to take a IP Address with a motherboard swap.
>
> Has anyone had a hardware failure with the system motherboard on CCM
> 5.x and didn't have to reinstall from scratch?
>
> The set network commands did not save the settings, it seems. On
> reboot the network setting changes made did not take effect. When you
> issued the set network ip command to change the IP address, it would
> prompt yes for changes and to reboot but did not automatically reboot
> after typing yes.
>
> Anyone go through this before with CCM 5.x on a IBM box? I just would
> like to find a better way for the future as there has to be a way to
> get the eth0 working again and set a IP address, upload new license,
> and get on with life.
>
> On Jan 28, 2008 10:02 PM, Erick Bergquist <erickbee at gmail.com> wrote:
>
>
>  Hi,
>
> Anyone ever have the system board fail in a IBM 7815-I2 and have a new
> one put in by IBM, and then CCM 5.1.1.3126-1 complain about the MAC
> address not being what it used to be and fixing this without a
> rebuild? The Ethernet interface is not coming up at all.
>
> We went through the Recovery DVD and that did not help, and we set the
> IP Address, etc on the eth0 interface through console but we can not
> bring the Eth0 interface up. When we try it sits there and seems to
> get hung up.
>
> Erick
>
>
>  _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer:

This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only.  If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful.  If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.