From: Steven Sim (steven.sim@faplccc.net)
Date: Thu Mar 15 2007 - 12:00:57 EST
To All;
Thanks to all who replied!
As requested by some members, here is a summary (and some new questions)
of the replies I received;
Original Problem Summary
----------------------------------
After a proper dladm link aggregation on a Sun Fire 240 bge0 and bge1
network port, I get the following messages;
mysolaris console login: WARNING: IP: Proxy ARP problem? Hardware address '00:14:4f:65:2d:86' thinks it is 192.168.023.040WARNING: IP: Hardware address '00:14:4f:65:2d:86' trying to be our address 192.168.023.040!Mar 14 13:14:01 inetd[223]: authdes_refresh: keyserv(1m) is unable to encrypt session keyWARNING: IP: Hardware address '00:14:4f:65:2d:86' trying to be our address 192.168.023.040!
Replies;
----------
My thanks to John Riddoch who pointed out that the switch does need to be
configured in order for the said messages to go away.
Sherry Moore of Sun also mentioned that the network ports on the switch
side would have to be in the same LGA. (LGA?)
Sherry gave an useful example of the dladm show-aggr command; (system
side)
-bash-3.00# dladm show-aggr -s
key: 100 ipackets rbytes opackets obytes %ipkts %opkts
Total 947433516 7512767679121005161348887977457412
e1000g0 505752998 343937378054616165566 629853173302 53.4 61.3
e1000g1 441680519 407339389922388995784 258124284466 46.6 38.7
I was a little confused by Sherry's last paragraph on the "underlying
interfaced exposed" and "you had to pick one of the interface to be
active when you install Solaris" statements.
My original installation did indeed use bge0 as the network port IP to be
tied to the hostname. However, after aggregation we deliberately renamed
"/etc/hostname.bge0" to "/etc/hostname.aggr1". Therefore bge0 was no
longer "stand-alone" but part of an active aggregate group and was not
plumbed up independently (/etc/hostname.bge0 no longer existed) upon
bootup. But we still experienced the original issue.
Darren Dunham confirmed that there would have to be a switch side
configuration, i.e. to enable LACP on the switch side.
Andy Harrison mentioned that he set "LACP to passive" (i am guessing on
the switch side) and subsequently had a successful negotiation between
the system side ports and network switch ports. (question! would doing
this permit me to create connect multiple link aggregate groups from
multiple systems to the same switch?)
Short Summary.
-----------------
Everybody seems to agree that LACP must be enabled on the switch side and
that this would resolve the issue. According to the links below, a proper
switch side configuration would also increase overall performance.
I will ask my network admin for this and hope that he understands LACP
and a LGA for the ports I am aggregating.
Useful and Related links
http://www.opensolaris.org/jive/thread.jspa?messageID=78624
http://blogs.sun.com/droux/entry/link_aggregation_plumbing
http://blogs.sun.com/droux/entry/link_aggregation_vs_ip_multipathing
Warmest Regards
Steven Sim
Fujitsu Asia Pte. Ltd.
_____________________________________________________
This e-mail is confidential and may also be privileged. If you are not
the intended recipient, please notify us immediately. You should not copy
or use it for any purpose, nor disclose its contents to any other person.
Opinions, conclusions and other information in this message that do not
relate to the official business of my firm shall be understood as neither
given nor endorsed by it.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:41:46 EDT