<div>address-based only with this release/configuration</div>
<div><br> </div>
<div class="gmail_quote">On Tue, Jul 14, 2009 at 2:49 PM, Marcin Kuczera <span dir="ltr"><marcin@leon.pl></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">hello,<br><br>I'am just testing sharing in Summit400-48t and... there is only dynamic algorythm that sais:<br>
* Summit400-48t:16 # enable sharing 47 grouping 47,48 a<br>Next possible completions:<br> <cr><br><br>* Summit400-48t:16 # enable sharing 47 grouping 47,48 algorithm address-based<br><br>* Summit400-48t:17 # show ports 47 info detail<br>
Port 47:<br> Type: UTP<br> Diagnostic: passed<br> Admin state: Enabled, with auto-duplex auto-speed sensing<br> Link state: Active. Full-duplex 1000 Mbps.<br> Link counter: Up 6 time(s), Down 5 times(s)<br>
Link Filter counter: Up 6 time(s), Down 5 times(s)<br> VLAN cfg:<br> test [802.1Q Tag=0100,Mac-Limit:Cfg=No-limit,LRN=37,BlkHole=0]<br><br> STP cfg:<br> s0(enable), Tag=(none), Mode=802.1D, State=FORWARDING<br>
<br> Trunking: Master port with 2 members using address-based algorithm<br> Members: 47 48 [Current runtime master is 47]<br><br>well, if I set "dynamic" it is still address-based.<br><br>
Will that allways be address based or can automatically switch to round-robin if the link is quite loaded ?<br>Or this switch can do only address based ?<br><br>In Alpine I could pick up round-robin method :(<br><br>Regards,<br>
Marcin<br>_______________________________________________<br>extreme-nsp mailing list<br><a href="mailto:extreme-nsp@puck.nether.net" target="_blank">extreme-nsp@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/extreme-nsp" target="_blank">https://puck.nether.net/mailman/listinfo/extreme-nsp</a><br>
</blockquote></div><br>