Mailing List Archive: nsp: foundry

Link Aggregation between Foundry and Cisco

Index | Next | Previous | View Threaded

jwhardeman at gmail

Jan 7, 2011, 4:27 PM

Post #1 of 10 (1436 views)
Permalink

Link Aggregation between Foundry and Cisco

Hi Everyone,

I am having a bit of an issue, I have gotten a pair of Cisco 6509's with
the SUP-720 engines. I am trying to configure link aggregation between
one of these to a BI4000 I have to test with before we put them into
production and connect them to our BI8000's and fight this problem
then. I have been searching and looking at the docs I have. The
configuration I have on the Cisco's allow them to talk over the port
channels between each other with no issues.

I can setup the command "link-aggregation active" on port "ethe 1/5"
with no issues it takes the command, but when I go to add a test VLAN on
to that port I get the following error message:

error - some ports are running LACP and can not be tagged ports.

Here is the command I am running on the BI:

test(config)#int e 1/5
test(config-if-e1000-1/5)#link-aggregate configure key 10000
test(config-if-e1000-1/5)#link-aggregate active
test(config-if-e1000-1/5)#exit
test(config)#vlan 14
test(config-vlan-14)#tagged e 1/5
error - some ports are running LACP and can not be tagged ports.
test(config-vlan-14)#end

Here is the output of sh int e 1/5"
GigabitEthernet1/5 is up, line protocol is up
Hardware is GigabitEthernet, address is 00e0.52cc.3b04 (bia
00e0.52cc.3b04)
Configured speed 1Gbit, actual 1Gbit, configured duplex fdx, actual fdx
Member of L2 VLAN ID 1, port is untagged, port state is BLOCKING
STP configured to ON, priority is level0, flow control disabled
mirror disabled, monitor disabled
Not member of any active trunks
Not member of any configured trunks
No port name
MTU 1518 bytes, encapsulation ethernet
300 second input rate: 40104 bits/sec, 72 packets/sec, 0.00% utilization
300 second output rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
899789 packets input, 62419802 bytes, 0 no buffer
Received 372 broadcasts, 899417 multicasts, 0 unicasts
0 input errors, 0 CRC, 0 frame, 0 ignored
0 runts, 0 giants, DMA received 899786 packets
0 packets output, 0 bytes, 0 underruns
Transmitted 0 broadcasts, 0 multicasts, 0 unicasts
0 output errors, 0 collisions, DMA transmitted 0 packets

Output of sh link-aggregation:
Long timeout: 90, default: 90
Short timeout: 3, default: 3
Port [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]
1/5 1 1 0 Yes S Agg Syn Col Dis Def No Blo

So my question is what am I missing here? From everything I found, all
I have to do after setting 1 or more ports into a link-aggregation is to
add the VLAN's as tagged to the ports with the same key. But its not
allowing me to add the tagged vlans.

Any suggestions?

Thanks

Joe
_______________________________________________
foundry-nsp mailing list
foundry-nsp [at] puck
http://puck.nether.net/mailman/listinfo/foundry-nsp

routehero at gmail

Jan 7, 2011, 4:34 PM

Post #2 of 10 (1415 views)
Permalink

Re: Link Aggregation between Foundry and Cisco [In reply to]

On Fri, Jan 7, 2011 at 7:27 PM, Joseph Hardeman <jwhardeman [at] gmail>wrote:

> Hi Everyone,
>
> I am having a bit of an issue, I have gotten a pair of Cisco 6509's with
> the SUP-720 engines. I am trying to configure link aggregation between one
> of these to a BI4000 I have to test with before we put them into production
> and connect them to our BI8000's and fight this problem then. I have been
> searching and looking at the docs I have. The configuration I have on the
> Cisco's allow them to talk over the port channels between each other with no
> issues.
>
> I can setup the command "link-aggregation active" on port "ethe 1/5" with
> no issues it takes the command, but when I go to add a test VLAN on to that
> port I get the following error message:
>
> error - some ports are running LACP and can not be tagged ports.
>
> Here is the command I am running on the BI:
>
> test(config)#int e 1/5
> test(config-if-e1000-1/5)#link-aggregate configure key 10000
> test(config-if-e1000-1/5)#link-aggregate active
> test(config-if-e1000-1/5)#exit
> test(config)#vlan 14
> test(config-vlan-14)#tagged e 1/5
> error - some ports are running LACP and can not be tagged ports.
>

I run this very config on FESX648 to Catalyst and SuperX to Catalyst without
any problems. Are you running ancient code?

Scott

bigwavedave at gmail

Jan 7, 2011, 4:36 PM

Post #3 of 10 (1425 views)
Permalink

Re: Link Aggregation between Foundry and Cisco [In reply to]

On Fri, Jan 7, 2011 at 4:27 PM, Joseph Hardeman <jwhardeman [at] gmail> wrote:
> Hi Everyone,
>
> I am having a bit of an issue, I have gotten a pair of Cisco 6509's with the
> SUP-720 engines. I am trying to configure link aggregation between one of
> these to a BI4000 I have to test with before we put them into production and
> connect them to our BI8000's and fight this problem then. I have been
> searching and looking at the docs I have. The configuration I have on the
> Cisco's allow them to talk over the port channels between each other with no
> issues.
>
> I can setup the command "link-aggregation active" on port "ethe 1/5" with no
> issues it takes the command, but when I go to add a test VLAN on to that
> port I get the following error message:
>
> error - some ports are running LACP and can not be tagged ports.
>
> Here is the command I am running on the BI:
>
> test(config)#int e 1/5
> test(config-if-e1000-1/5)#link-aggregate configure key 10000
> test(config-if-e1000-1/5)#link-aggregate active
> test(config-if-e1000-1/5)#exit
> test(config)#vlan 14
> test(config-vlan-14)#tagged e 1/5
> error - some ports are running LACP and can not be tagged ports.
> test(config-vlan-14)#end
>
> Here is the output of sh int e 1/5"
> GigabitEthernet1/5 is up, line protocol is up
> Hardware is GigabitEthernet, address is 00e0.52cc.3b04 (bia 00e0.52cc.3b04)
> Configured speed 1Gbit, actual 1Gbit, configured duplex fdx, actual fdx
> Member of L2 VLAN ID 1, port is untagged, port state is BLOCKING
> STP configured to ON, priority is level0, flow control disabled
> mirror disabled, monitor disabled
> Not member of any active trunks
> Not member of any configured trunks
> No port name
> MTU 1518 bytes, encapsulation ethernet
> 300 second input rate: 40104 bits/sec, 72 packets/sec, 0.00% utilization
> 300 second output rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
> 899789 packets input, 62419802 bytes, 0 no buffer
> Received 372 broadcasts, 899417 multicasts, 0 unicasts
> 0 input errors, 0 CRC, 0 frame, 0 ignored
> 0 runts, 0 giants, DMA received 899786 packets
> 0 packets output, 0 bytes, 0 underruns
> Transmitted 0 broadcasts, 0 multicasts, 0 unicasts
> 0 output errors, 0 collisions, DMA transmitted 0 packets
>
>
> Output of sh link-aggregation:
> Long timeout: 90, default: 90
> Short timeout: 3, default: 3
> Port [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]
> 1/5 1 1 0 Yes S Agg Syn Col Dis Def No Blo
>
>
> So my question is what am I missing here? From everything I found, all I
> have to do after setting 1 or more ports into a link-aggregation is to add
> the VLAN's as tagged to the ports with the same key. But its not allowing
> me to add the tagged vlans.
>
> Any suggestions?
>
> Thanks
>
> Joe
> _______________________________________________

I've had similar problems before.
My bookmark takes me to:

http://www.techsneeze.com/create-vlan-trunk-between-cisco-ios-and-foundry-bigiron

Dave

_______________________________________________
foundry-nsp mailing list
foundry-nsp [at] puck
http://puck.nether.net/mailman/listinfo/foundry-nsp

jwhardeman at gmail

Jan 7, 2011, 4:53 PM

Post #4 of 10 (1427 views)
Permalink

Re: Link Aggregation between Foundry and Cisco [In reply to]

On 1/7/2011 7:36 PM, Big Wave Dave wrote:
> On Fri, Jan 7, 2011 at 4:27 PM, Joseph Hardeman<jwhardeman [at] gmail> wrote:
>> Hi Everyone,
>>
>> I am having a bit of an issue, I have gotten a pair of Cisco 6509's with the
>> SUP-720 engines. I am trying to configure link aggregation between one of
>> these to a BI4000 I have to test with before we put them into production and
>> connect them to our BI8000's and fight this problem then. I have been
>> searching and looking at the docs I have. The configuration I have on the
>> Cisco's allow them to talk over the port channels between each other with no
>> issues.
>>
>> I can setup the command "link-aggregation active" on port "ethe 1/5" with no
>> issues it takes the command, but when I go to add a test VLAN on to that
>> port I get the following error message:
>>
>> error - some ports are running LACP and can not be tagged ports.
>>
>> Here is the command I am running on the BI:
>>
>> test(config)#int e 1/5
>> test(config-if-e1000-1/5)#link-aggregate configure key 10000
>> test(config-if-e1000-1/5)#link-aggregate active
>> test(config-if-e1000-1/5)#exit
>> test(config)#vlan 14
>> test(config-vlan-14)#tagged e 1/5
>> error - some ports are running LACP and can not be tagged ports.
>> test(config-vlan-14)#end
>>
>> Here is the output of sh int e 1/5"
>> GigabitEthernet1/5 is up, line protocol is up
>> Hardware is GigabitEthernet, address is 00e0.52cc.3b04 (bia 00e0.52cc.3b04)
>> Configured speed 1Gbit, actual 1Gbit, configured duplex fdx, actual fdx
>> Member of L2 VLAN ID 1, port is untagged, port state is BLOCKING
>> STP configured to ON, priority is level0, flow control disabled
>> mirror disabled, monitor disabled
>> Not member of any active trunks
>> Not member of any configured trunks
>> No port name
>> MTU 1518 bytes, encapsulation ethernet
>> 300 second input rate: 40104 bits/sec, 72 packets/sec, 0.00% utilization
>> 300 second output rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
>> 899789 packets input, 62419802 bytes, 0 no buffer
>> Received 372 broadcasts, 899417 multicasts, 0 unicasts
>> 0 input errors, 0 CRC, 0 frame, 0 ignored
>> 0 runts, 0 giants, DMA received 899786 packets
>> 0 packets output, 0 bytes, 0 underruns
> > Transmitted 0 broadcasts, 0 multicasts, 0 unicasts
>> 0 output errors, 0 collisions, DMA transmitted 0 packets
>>
>>
>> Output of sh link-aggregation:
>> Long timeout: 90, default: 90
>> Short timeout: 3, default: 3
>> Port [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]
>> 1/5 1 1 0 Yes S Agg Syn Col Dis Def No Blo
>>
>>
>> So my question is what am I missing here? From everything I found, all I
>> have to do after setting 1 or more ports into a link-aggregation is to add
>> the VLAN's as tagged to the ports with the same key. But its not allowing
>> me to add the tagged vlans.
>>
>> Any suggestions?
>>
>> Thanks
>>
>> Joe
>> _______________________________________________
>
> I've had similar problems before.
> My bookmark takes me to:
>
> http://www.techsneeze.com/create-vlan-trunk-between-cisco-ios-and-foundry-bigiron
>
> Dave
>
Hi Dave

Thanks for the link, but its only showing how to tag a vlan to the port,
which what I am currently doing but with the new ciscos and adding more
fiber between our routers and switches I wanted to be able to do link
aggregation. I am guessing I can't with this system unless I go with
Trunk mode.

Joe
_______________________________________________
foundry-nsp mailing list
foundry-nsp [at] puck
http://puck.nether.net/mailman/listinfo/foundry-nsp

jwhardeman at gmail

Jan 7, 2011, 5:11 PM

Post #5 of 10 (1416 views)
Permalink

Re: Link Aggregation between Foundry and Cisco [In reply to]

On 1/7/2011 7:34 PM, Scott T. Cameron wrote:
> On Fri, Jan 7, 2011 at 7:27 PM, Joseph Hardeman <jwhardeman [at] gmail
> <mailto:jwhardeman [at] gmail>> wrote:
>
> Hi Everyone,
>
> I am having a bit of an issue, I have gotten a pair of Cisco
> 6509's with the SUP-720 engines. I am trying to configure link
> aggregation between one of these to a BI4000 I have to test with
> before we put them into production and connect them to our
> BI8000's and fight this problem then. I have been searching and
> looking at the docs I have. The configuration I have on the
> Cisco's allow them to talk over the port channels between each
> other with no issues.
>
> I can setup the command "link-aggregation active" on port "ethe
> 1/5" with no issues it takes the command, but when I go to add a
> test VLAN on to that port I get the following error message:
>
> error - some ports are running LACP and can not be tagged ports.
>
> Here is the command I am running on the BI:
>
> test(config)#int e 1/5
> test(config-if-e1000-1/5)#link-aggregate configure key 10000
> test(config-if-e1000-1/5)#link-aggregate active
> test(config-if-e1000-1/5)#exit
> test(config)#vlan 14
> test(config-vlan-14)#tagged e 1/5
> error - some ports are running LACP and can not be tagged ports.
>
>
> I run this very config on FESX648 to Catalyst and SuperX to Catalyst
> without any problems. Are you running ancient code?
>
> Scott
Hi Scott,

Oh yeah, its pretty old, from 2004. I was testing with this system
since I had it laying around, I just don't want to try to connect it up
to the switches and other BI's just to run into this problem and have it
fark out on me like this. Guess, we will have to give it a shot with
the other systems once we put the Cisco's in and if I can't pass any
traffic or get the same errors then we will tear down the port-channel
config on the cisco's and figure another alternative out.

But since this is the same configuration that I am finding and everyone
else is using, then by all rights it should work.

Thanks for the response.

Joe

mkallen at gmail

Jan 7, 2011, 5:15 PM

Post #6 of 10 (1423 views)
Permalink

Re: Link Aggregation between Foundry and Cisco [In reply to]

Joe, Scott is likely on the right track. Early versions of B4000/8000 code
did not support dynamic LACP over tagged links. Given that, your options
are upgrading to a newer release, or use static trunks as you mentioned. If
you do the upgrade and then do LACP over a tagged port, make sure you use a
LACP key. Other than that, it should work just fine between vendors. Hope
that helps.

Mike

On Fri, Jan 7, 2011 at 4:53 PM, Joseph Hardeman <jwhardeman [at] gmail>wrote:

>
>
> On 1/7/2011 7:36 PM, Big Wave Dave wrote:
>
>> On Fri, Jan 7, 2011 at 4:27 PM, Joseph Hardeman<jwhardeman [at] gmail>
>> wrote:
>>
>>> Hi Everyone,
>>>
>>> I am having a bit of an issue, I have gotten a pair of Cisco 6509's with
>>> the
>>> SUP-720 engines. I am trying to configure link aggregation between one
>>> of
>>> these to a BI4000 I have to test with before we put them into production
>>> and
>>> connect them to our BI8000's and fight this problem then. I have been
>>> searching and looking at the docs I have. The configuration I have on
>>> the
>>> Cisco's allow them to talk over the port channels between each other with
>>> no
>>> issues.
>>>
>>> I can setup the command "link-aggregation active" on port "ethe 1/5" with
>>> no
>>> issues it takes the command, but when I go to add a test VLAN on to that
>>> port I get the following error message:
>>>
>>> error - some ports are running LACP and can not be tagged ports.
>>>
>>> Here is the command I am running on the BI:
>>>
>>> test(config)#int e 1/5
>>> test(config-if-e1000-1/5)#link-aggregate configure key 10000
>>> test(config-if-e1000-1/5)#link-aggregate active
>>> test(config-if-e1000-1/5)#exit
>>> test(config)#vlan 14
>>> test(config-vlan-14)#tagged e 1/5
>>> error - some ports are running LACP and can not be tagged ports.
>>> test(config-vlan-14)#end
>>>
>>> Here is the output of sh int e 1/5"
>>> GigabitEthernet1/5 is up, line protocol is up
>>> Hardware is GigabitEthernet, address is 00e0.52cc.3b04 (bia
>>> 00e0.52cc.3b04)
>>> Configured speed 1Gbit, actual 1Gbit, configured duplex fdx, actual fdx
>>> Member of L2 VLAN ID 1, port is untagged, port state is BLOCKING
>>> STP configured to ON, priority is level0, flow control disabled
>>> mirror disabled, monitor disabled
>>> Not member of any active trunks
>>> Not member of any configured trunks
>>> No port name
>>> MTU 1518 bytes, encapsulation ethernet
>>> 300 second input rate: 40104 bits/sec, 72 packets/sec, 0.00% utilization
>>> 300 second output rate: 0 bits/sec, 0 packets/sec, 0.00% utilization
>>> 899789 packets input, 62419802 bytes, 0 no buffer
>>> Received 372 broadcasts, 899417 multicasts, 0 unicasts
>>> 0 input errors, 0 CRC, 0 frame, 0 ignored
>>> 0 runts, 0 giants, DMA received 899786 packets
>>> 0 packets output, 0 bytes, 0 underruns
>>>
>> > Transmitted 0 broadcasts, 0 multicasts, 0 unicasts
>>
>>> 0 output errors, 0 collisions, DMA transmitted 0 packets
>>>
>>>
>>> Output of sh link-aggregation:
>>> Long timeout: 90, default: 90
>>> Short timeout: 3, default: 3
>>> Port [Sys P] [Port P] [ Key ]
>>> [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]
>>> 1/5 1 1 0 Yes S Agg Syn Col Dis Def No
>>> Blo
>>>
>>>
>>> So my question is what am I missing here? From everything I found, all
>>> I
>>> have to do after setting 1 or more ports into a link-aggregation is to
>>> add
>>> the VLAN's as tagged to the ports with the same key. But its not
>>> allowing
>>> me to add the tagged vlans.
>>>
>>> Any suggestions?
>>>
>>> Thanks
>>>
>>> Joe
>>> _______________________________________________
>>>
>>
>> I've had similar problems before.
>> My bookmark takes me to:
>>
>>
>> http://www.techsneeze.com/create-vlan-trunk-between-cisco-ios-and-foundry-bigiron
>>
>> Dave
>>
>> Hi Dave
>
> Thanks for the link, but its only showing how to tag a vlan to the port,
> which what I am currently doing but with the new ciscos and adding more
> fiber between our routers and switches I wanted to be able to do link
> aggregation. I am guessing I can't with this system unless I go with Trunk
> mode.
>
> Joe
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp [at] puck
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>

jwhardeman at gmail

Jan 7, 2011, 5:28 PM

Post #7 of 10 (1423 views)
Permalink

Re: Link Aggregation between Foundry and Cisco [In reply to]

Hey Mike,

You wouldn't happen to know what version of code or when they started
supporting dynamic LACP over tagged links would be would you?

Joe

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

mkallen at gmail

Jan 7, 2011, 5:37 PM

Post #8 of 10 (1415 views)
Permalink

Re: Link Aggregation between Foundry and Cisco [In reply to]

Let me look at the release notes and I will unicast you back.

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

jwhardeman at gmail

Jan 7, 2011, 5:56 PM

Post #9 of 10 (1422 views)
Permalink

Re: Link Aggregation between Foundry and Cisco [In reply to]

Very cool, thanks man.

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

nick.sandone at cdicorp

Jan 10, 2011, 6:07 AM

Post #10 of 10 (1574 views)
Permalink

Re: Link Aggregation between Foundry and Cisco [In reply to]

Do a show link-agg and check to make sure that nothing else is using key 10000

From: foundry-nsp-bounces [at] puck [mailto:foundry-nsp-bounces [at] puck] On Behalf Of Joseph Hardeman
Sent: Friday, January 07, 2011 8:57 PM
To: Mike Allen
Cc: foundry-nsp [at] puck
Subject: Re: [f-nsp] Link Aggregation between Foundry and Cisco

Very cool, thanks man.

On 1/7/2011 8:37 PM, Mike Allen wrote:

Let me look at the release notes and I will unicast you back.

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

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

______________________________________________________________________
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain information which is confidential to, and/or privileged in favor of, CDI Corporation or its affiliated companies (CDI) or CDI's customers. Any review, use, reproduction, disclosure or distribution by the recipient is prohibited without prior written approval from an authorized CDI representative. This notice must appear in any such authorized reproduction, disclosure or distribution. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments. Thank you.

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads