Swapping MAC addresses?

Chase Bolt cbolt at datinggold.com
Wed Sep 2 19:18:48 CDT 2009


I can't imagine he is rebooting once a week, though if he was I would 
lean more towards Bryan on this.

Only time I have seen macs flipping like this so often is when your have 
bonded your nics. Are you doing a load balance or active/passive setup 
on your nics?


Bryan wrote:
> Assuming this is RHEL or equivalent, do you have a HWADDR line 
> assigned to each interface in network config?  Otherwise, the physical 
> nics can show up in different order depending on how they're 
> enumerated on boot.
>
> On Wed, Sep 2, 2009 at 6:43 PM, John Oliver <joliver at john-oliver.net 
> <mailto:joliver at john-oliver.net>> wrote:
>
>     I have a 2950 with an IP address configured on each NIC.  A few weeks
>     ago, the network folks started asking why my primary IP was showing up
>     on different MAC addresses.
>
>       Registered Macaddress = 0019.b9ca.5b46
>       mac address(es) this week:      0019.b9ca.5b44
>                                       0019.b9ca.5b46
>       mac addresses during week 1:    0019.b9ca.5b44
>                                       0019.b9ca.5b46
>       mac addresses during week 2:    0019.b9ca.5b44
>                                       0019.b9ca.5b46
>       mac addresses during week 3:    0019.b9ca.5b44
>                                       0019.b9ca.5b46
>       mac addresses during week 4:    0019.b9ca.5b44
>                                       0019.b9ca.5b46
>       mac addresses during week 5:    0019.b9ca.5b44
>       mac addresses during week 6:    0019.b9ca.5b44
>       mac addresses during week 7:    0019.b9ca.5b44
>       mac addresses during week 8:    0019.b9ca.5b44
>       mac addresses during week 9:    0019.b9ca.5b44
>
>
>     eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
>     133MHz
>     found at
>      mem f8000000, IRQ 169, node addr 0019b9ca5b44
>     eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
>     133MHz
>     found at
>      mem f4000000, IRQ 169, node addr 0019b9ca5b46
>
>
>     The cables haven't been touched.  I see nothing in the logs.  My
>     assumption was, there's something wrong with the switch.  They insist
>     the switch is fine and it's got to be the server.
>
>     Has anyone seen this before?  It isn't affecting operations, but
>     they do
>     get warnings about this, and it's always nice to at least get an
>     explanation for weird things :-)
>
>     --
>     ***********************************************************************
>     * John Oliver                            
>     http://www.john-oliver.net/ *
>     *                                                                
>         *
>     ***********************************************************************
>
>     _______________________________________________
>     Linux-PowerEdge mailing list
>     Linux-PowerEdge at lists.us.dell.com
>     <mailto:Linux-PowerEdge at lists.us.dell.com>
>     https://lists.us.dell.com/mailman/listinfo/linux-poweredge
>     Please read the FAQ at http://lists.us.dell.com/faq
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at lists.us.dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> Please read the FAQ at http://lists.us.dell.com/faq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20090902/516fd937/attachment-0001.htm 


More information about the Linux-PowerEdge mailing list