That was quick. An concise explanation of why, when and how. Similar quick replies from John England, gary Paveza, Todd Cox, Dave Magda, and Jim Musso. The corresponding Sun page is http://docs.sun.com/app/docs/doc/816-4554/eyprp?a=view. Thank you, --------------- Chris Hoogendyk - O__ ---- Systems Administrator c/ /'_ --- Biology & Geology Departments (*) \(*) -- 140 Morrill Science Center ~~~~~~~~~~ - University of Massachusetts, Amherst <hoogendyk@bio.umass.edu> --------------- Erdvs 4 Steve Harris wrote: > Not broken - typical behavior as far as I recall. Can be modified using > an eeprom setting:: > > http://www.tech-recipes.com/rx/194/configure-unique-mac-addresses-on-multiple-interfaces/ > > Cheers - Steve > > On 5/5/2010 10:58 AM, Chris Hoogendyk wrote: > >> After some massive campus wide power outages caused by a violent >> thunderstorm and downed power lines, I thought I had everything up and >> running smoothly. Then, this morning I noticed I hadn't gotten a report >> from my Amanda backup server (a Sun E250). I had a console connection to >> it, but couldn't ssh to it. Eventually, it turned out to be a flaky >> switch that randomly fails ports. >> >> Anyway, in the process of troubleshooting that, I noticed that `ifconfig >> -a` showed the same hardware address on ce0 and hme0. Initially I >> thought that was the problem, but it didn't make sense that it would >> just happen out of the blue. In searching around, I found: >> >> http://www.ewp.rpi.edu/hartford/webgen/sysdocs/C/solaris_9/SUNWdhshw/817-4189-10/install-apps.html >> >> >> Which is a copy of the Solaris 9 4/04 Sun Hardware Platform Guide. >> Toward the end of that, it has a couple of examples of `ifconfig -a` on >> systems with multiple interfaces (see below). In each case, it shows the >> same hardware address on all the interfaces for a particular machine. >> >> That just seems problematic to me. We don't use vlans. We do use subnets >> and a NAT box. So, in my case, the two interfaces have IP addresses that >> are on different subnets. They happen to go through different switches, >> but, ultimately, it's all the same network. Typically, I have ce0 as the >> primary interface, and all traffic goes through that. I have hme0 with >> an IP address on our switch and devices subnet, and it has almost no >> traffic. While troubleshooting, I ssh'd in through hme0, and it worked >> fine. After bashing on the flaky switch and getting it to come up >> properly, ce0 came back to life. I ssh'd in to that and it worked fine. >> But, then my sessions in through hme0 became unresponsive. I eventually >> got them to respond, but they were unbelievably sluggish and unresponsive. >> >> So, what's the deal with this? >> >> Why does Sun configure the hardware addresses this way? The card that is >> ce0 was bought much later and added on. >> >> Do other people think this is broken? >> >> Is there a way to fix it? >> >> My newer systems (Sun T5220's) have separate hardware addresses for each >> of the multiple interfaces. >> >> TIA >> >> >> -- >> --------------- >> >> Chris Hoogendyk >> >> - >> O__ ---- Systems Administrator >> c/ /'_ --- Biology & Geology Departments >> (*) \(*) -- 140 Morrill Science Center >> ~~~~~~~~~~ - University of Massachusetts, Amherst >> >> <hoogendyk@bio.umass.edu> >> >> --------------- >> >> Erdvs 4 >> >> >> >> >> >> The output of ifconfig -a on a system with VLAN devices ce123000 and >> ce224000: >> >> # ifconfig -a >> lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 >> inet 127.0.0.1 netmask ff000000 >> hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 >> inet 129.144.131.91 netmask ffffff00 broadcast 129.144.131.255 >> ether 8:0:20:a4:4f:b8 >> ce123000: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 >> index 3 >> inet 199.199.123.3 netmask ffffff00 broadcast 199.199.123.255 >> ether 8:0:20:a4:4f:b8 >> ce224000: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 >> index 4 >> inet 199.199.224.3 netmask ffffff00 broadcast 199.199.224.255 >> ether 8:0:20:a4:4f:b8 >> >> >> >> The output of ifconfig -a on a system with VLAN devices bge10000 and >> bge11000: >> >> # ifconfig -a >> lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 >> inet 127.0.0.1 netmask ff000000 >> bge0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 >> index 2 >> inet 129.156.205.172 netmask ffffff00 broadcast 129.156.205.255 >> ether 0:3:ba:29:f0:de >> bge10000: flags=201000842<BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 >> index 3 >> inet 10.0.0.2 netmask ffffff00 broadcast 10.0.0.255 >> ether 0:3:ba:29:f0:de >> bge11000: flags=201000842<BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 >> index 4 >> inet 10.0.1.2 netmask ffffff00 broadcast 10.0.1.255 >> ether 0:3:ba:29:f0:de >> _______________________________________________ >> sunmanagers mailing list >> sunmanagers@sunmanagers.org >> http://www.sunmanagers.org/mailman/listinfo/sunmanagers _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Wed May 5 14:42:17 2010
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:44:16 EST