<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Very cool, thanks man.<br>
<br>
On 1/7/2011 8:37 PM, Mike Allen wrote:
<blockquote
cite="mid:AANLkTi=f8NckLYuoDv2Ti1Rmn9fKncQtKC3ABM=Zs5m6@mail.gmail.com"
type="cite">
<p>Let me look at the release notes and I will unicast you back.</p>
<p>Mike</p>
<div class="gmail_quote">On Jan 7, 2011 5:29 PM, "Joseph Hardeman"
<<a moz-do-not-send="true" href="mailto:jwhardeman@gmail.com">jwhardeman@gmail.com</a>>
wrote:<br type="attribution">
> Hey Mike,<br>
> <br>
> You wouldn't happen to know what version of code or when
they started <br>
> supporting dynamic LACP over tagged links would be would
you?<br>
> <br>
> Joe<br>
> <br>
> On 1/7/2011 8:15 PM, Mike Allen wrote:<br>
>> Joe, Scott is likely on the right track. Early versions
of B4000/8000 <br>
>> code did not support dynamic LACP over tagged links.
Given that, your <br>
>> options are upgrading to a newer release, or use static
trunks as you <br>
>> mentioned. If you do the upgrade and then do LACP over
a tagged port, <br>
>> make sure you use a LACP key. Other than that, it
should work just <br>
>> fine between vendors. Hope that helps.<br>
>> Mike<br>
>><br>
>> On Fri, Jan 7, 2011 at 4:53 PM, Joseph Hardeman <<a
moz-do-not-send="true" href="mailto:jwhardeman@gmail.com">jwhardeman@gmail.com</a>
<br>
>> <mailto:<a moz-do-not-send="true"
href="mailto:jwhardeman@gmail.com">jwhardeman@gmail.com</a>>>
wrote:<br>
>><br>
>><br>
>><br>
>> On 1/7/2011 7:36 PM, Big Wave Dave wrote:<br>
>><br>
>> On Fri, Jan 7, 2011 at 4:27 PM, Joseph<br>
>> Hardeman<<a moz-do-not-send="true"
href="mailto:jwhardeman@gmail.com">jwhardeman@gmail.com</a>
<mailto:<a moz-do-not-send="true"
href="mailto:jwhardeman@gmail.com">jwhardeman@gmail.com</a>>><br>
>> wrote:<br>
>><br>
>> Hi Everyone,<br>
>><br>
>> I am having a bit of an issue, I have gotten a pair of<br>
>> Cisco 6509's with the<br>
>> SUP-720 engines. I am trying to configure link<br>
>> aggregation between one of<br>
>> these to a BI4000 I have to test with before we put
them<br>
>> into production and<br>
>> connect them to our BI8000's and fight this problem
then.<br>
>> I have been<br>
>> searching and looking at the docs I have. The<br>
>> configuration I have on the<br>
>> Cisco's allow them to talk over the port channels
between<br>
>> each other with no<br>
>> issues.<br>
>><br>
>> I can setup the command "link-aggregation active" on
port<br>
>> "ethe 1/5" with no<br>
>> issues it takes the command, but when I go to add a
test<br>
>> VLAN on to that<br>
>> port I get the following error message:<br>
>><br>
>> error - some ports are running LACP and can not be
tagged<br>
>> ports.<br>
>><br>
>> Here is the command I am running on the BI:<br>
>><br>
>> test(config)#int e 1/5<br>
>> test(config-if-e1000-1/5)#link-aggregate configure key
10000<br>
>> test(config-if-e1000-1/5)#link-aggregate active<br>
>> test(config-if-e1000-1/5)#exit<br>
>> test(config)#vlan 14<br>
>> test(config-vlan-14)#tagged e 1/5<br>
>> error - some ports are running LACP and can not be
tagged<br>
>> ports.<br>
>> test(config-vlan-14)#end<br>
>><br>
>> Here is the output of sh int e 1/5"<br>
>> GigabitEthernet1/5 is up, line protocol is up<br>
>> Hardware is GigabitEthernet, address is 00e0.52cc.3b04<br>
>> (bia 00e0.52cc.3b04)<br>
>> Configured speed 1Gbit, actual 1Gbit, configured duplex<br>
>> fdx, actual fdx<br>
>> Member of L2 VLAN ID 1, port is untagged, port state is<br>
>> BLOCKING<br>
>> STP configured to ON, priority is level0, flow control<br>
>> disabled<br>
>> mirror disabled, monitor disabled<br>
>> Not member of any active trunks<br>
>> Not member of any configured trunks<br>
>> No port name<br>
>> MTU 1518 bytes, encapsulation ethernet<br>
>> 300 second input rate: 40104 bits/sec, 72 packets/sec,<br>
>> 0.00% utilization<br>
>> 300 second output rate: 0 bits/sec, 0 packets/sec,
0.00%<br>
>> utilization<br>
>> 899789 packets input, 62419802 bytes, 0 no buffer<br>
>> Received 372 broadcasts, 899417 multicasts, 0 unicasts<br>
>> 0 input errors, 0 CRC, 0 frame, 0 ignored<br>
>> 0 runts, 0 giants, DMA received 899786 packets<br>
>> 0 packets output, 0 bytes, 0 underruns<br>
>><br>
>> > Transmitted 0 broadcasts, 0 multicasts, 0
unicasts<br>
>><br>
>> 0 output errors, 0 collisions, DMA transmitted 0
packets<br>
>><br>
>><br>
>> Output of sh link-aggregation:<br>
>> Long timeout: 90, default: 90<br>
>> Short timeout: 3, default: 3<br>
>> Port [Sys P] [Port P] [ Key ]<br>
>> [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]<br>
>> 1/5 1 1 0 Yes S Agg Syn Col<br>
>> Dis Def No Blo<br>
>><br>
>><br>
>> So my question is what am I missing here? From<br>
>> everything I found, all I<br>
>> have to do after setting 1 or more ports into a<br>
>> link-aggregation is to add<br>
>> the VLAN's as tagged to the ports with the same key.
But<br>
>> its not allowing<br>
>> me to add the tagged vlans.<br>
>><br>
>> Any suggestions?<br>
>><br>
>> Thanks<br>
>><br>
>> Joe<br>
>> _______________________________________________<br>
>><br>
>><br>
>> I've had similar problems before.<br>
>> My bookmark takes me to:<br>
>><br>
>> <a moz-do-not-send="true"
href="http://www.techsneeze.com/create-vlan-trunk-between-cisco-ios-and-foundry-bigiron">http://www.techsneeze.com/create-vlan-trunk-between-cisco-ios-and-foundry-bigiron</a><br>
>><br>
>> Dave<br>
>><br>
>> Hi Dave<br>
>><br>
>> Thanks for the link, but its only showing how to tag a
vlan to the<br>
>> port, which what I am currently doing but with the new
ciscos and<br>
>> adding more fiber between our routers and switches I
wanted to be<br>
>> able to do link aggregation. I am guessing I can't with
this<br>
>> system unless I go with Trunk mode.<br>
>><br>
>> Joe<br>
>><br>
>> _______________________________________________<br>
>> foundry-nsp mailing list<br>
>> <a moz-do-not-send="true"
href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>
<mailto:<a moz-do-not-send="true"
href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a>><br>
>> <a moz-do-not-send="true"
href="http://puck.nether.net/mailman/listinfo/foundry-nsp">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
>><br>
>><br>
</div>
</blockquote>
</body>
</html>