ce0 is primary over hme0, how do I switch?

From: Phillip Pacheco (ppacheco_at_sbcglobal.net)
Date: 09/24/04


Date: 23 Sep 2004 16:38:36 -0700

I have a 420r running Solaris 9. I have installed a Quad Gigaswift
ethernet card and configured ce0 along with the built in hme0. I
setup the system with host name 'foo' under /etc/hostname.hme0 ,
/etc/nodename , and the /etc/net/ files. I setup ce0 to be 'foo-ce'
under /etc/hostname.ce0. Both are on the same network. I want to
route management traffic through the hme0 interface. But the
logserver, for example receives logs from 'foo-ce' instead of 'foo'.
ifconfig -a also shows the wrong preference:

lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index
1
        inet 127.0.0.1 netmask ff000000
ce0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index
2
        inet 192.168.20.73 netmask ffffff00 broadcast 192.168.20.255
        
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index 3
        inet 192.168.20.13 netmask ffffff00 broadcast 192.168.20.255

Why is ce0 considered the primary, and how do I change that? I
manually added a route to the logserver, but the client called that a
workaround, and wants hme0 to be considered the primary interface.
Yes, we have also considered setting up a management network, as
separate from production, but we are not in a position to do that
right now.

Phil



Relevant Pages

  • IPMP errors
    ... configured ipmp. ... It failover and fail back to the primary interface in ... hme0 to NIC hme1 ...
    (SunManagers)
  • Two NICs, one primary, one standby??
    ... I am having trouble parsing how to use the two NIC's (hme0 and hme1) ... lo0: flags=1000849mtu 8232 index ... This all looked good, but when I killed the switchport that held hme0, ...
    (comp.sys.sun.admin)
  • Re: Why so many default interfaces?
    ... fxp0: flags=9843mtu 1500 ... hme0: flags=8063mtu 1500 ... hme1: flags=8822mtu 1500 ... hme2: flags=8822mtu 1500 ...
    (comp.unix.bsd.openbsd.misc)