Same issue here since day 0 when I moved to 10.8. MacPro is connected to Netgear GS108T and Bond0 interface cannot come up after reload, unless I clear bond config (by deleting it) and re-configure it again.
Hopefully I don't need to restart the box frequently otherwise I would be moving back to Lion
DimsBE & All
I have established that when the machine is commanded to SLEEP, upon recovery the aggregated link stilll works fine and has not reset.
So although not ideal, at least an interim workaround.
I've also dug a little deeper into the perference files and compared OS X Lion to OS X Mountain Lion (NetworkInterfaces.plist)
I notice that in Lion each ethernet is called up as:
whereas in Mountain Lion each ethernet is called up as:
I'm continuing to explore, to see what other changes/differences exist, maybe somewhere there is the key to this problem? ?
I've contacted Apple Support directly this afternoon on this subject to get a solution!
After a 46 minute call I have been informed that Apple 'Enterprise' team are aware of this issue and are working on a patch solution now which is likely to be part of the first round of issues to be resolved in the 10.8.1 update.
No timescale for the patch could be provided , but the Apple representative did say historically the first patch normally comes out quickly to resolve issues. Let's hope this issue get's fixed.
One other thought that I had, is there anyone in the OS X community able to bring together an applescript to automate the the workaround that I originally posted, at least then it would be quicker to get the aggregated bond up working after a restart.
Until either the patch or a really nice person can put out an applescript, i'll either endure the daily procedure to get the bond working or keep the Mac Pro in sleep mode overnight.
Two weeks with this Mountain Lion 802.3ad issue (the most polished OS X yet......apparently...), and it's all too much of an inconvenience.
No updates from Apple as to roll out of update/patch/fix/service pack, so........
Restored back to Lion, 802.3ad works, the Mac Pro works, I can work.
P.S. Sorry to hear of others having same issue (those having posted in this thread), and possibily others of the 470+ that have read this thread to date.
I had the same problem with Mountain Lion and had to manually active Trunking on our HP Procurve Switch J4904A in Switch Configuration>Port-Trunk Settings>the two ports for your System>then activate "TRK1 with LCAP" on the first and the second port. After saving these settings on our Switch the bond worked in 10.8. Ethernet1 and 2 are now working together again. Green lights :-)
phocus-it, Thanks for your post.
A question if I may, I and others can get 802.3ad link aggregation bonds to work (see original post), I guess our issues are when the Mac is restarted or booted post shutdown the bond does not come back up live as it does within OS X Lion, so i'm interested in your case do you have to re-make the virtual interface (bond) within OS X Mountain Lion with your setup upon every restart or not?
If you're not needing to remake the virtual interface upon every restart, maybe this issue is a function of hardware setup (802.3ad Switch type) used, or a susceptibility within OS X Mountain Lion over OS X Lion?
phocus-it, Thanks again for your post.
Sorry to hear you have the exact same symptoms, if you're happy to never restart OS X Mountain Lion the bond once made will keep working, the bond will still be active is you resume from Sleep, any restarting and you'll be deleting the virtual interface and making a new one after each restart.
I did a couple of weeks everyday make the bond work, after which got bored and went back to OS X Lion.
It's interesting to note the symptoms occur regardless with manufacturer of 802.3ad compliant Switch is being used, I run TP-LINK, you're running HP, others on Netgear.
On my side my L2 managed switch allows me to make a 802.3ad aggregated link as either a 'Static LAG Link' or dynamic 'LACP', i've tried both types with OS X Mountain Lion, same end results - makes No difference.