Mailing List Archive: nsp: foundry

Remove one interface from LACP group

Index | Next | Previous | View Threaded

robhass at gmail

Jun 4, 2012, 12:56 PM

Post #1 of 11 (1093 views)
Permalink

Remove one interface from LACP group

Hi

I have problem removing one interface from LACP trunk group. Here is
my configuration:

interface ethernet 1/1/5
port-name link01
no flow-control
link-aggregate configure key 30000
link-aggregate active
!
interface ethernet 1/1/6
port-name link02
link-aggregate configure key 30000
link-aggregate active
!
interface ethernet 1/1/7
port-name link03
link-aggregate configure key 30000
link-aggregate active

telnet [at] la#show link-ag
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/1/5 1 1 30000 Yes L Agg Syn Col Dis No No Ope
1/1/6 1 1 30000 Yes L Agg Syn Col Dis No No Ope
1/1/7 1 1 30000 Yes L Agg Syn Col Dis No No Ope

I would like to remove port 1/1/6 from link-aggregation, but how I can do this ?

telnet [at] la(config)#no trunk ethernet 1/1/6
Error - Please provide all (3) Lacp Trunk Ports

This not work.

telnet [at] la(config)#trunk ethernet 1/1/5 to 1/1/7
telnet [at] la(config-trunk-1/1/5-1/1/7)#disable ethernet 1/1/6
telnet [at] la(config-trunk-1/1/5-1/1/7)#no trunk e 1/1/6
Error - Please provide all (3) Lacp Trunk Ports

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

frnkblk at iname

Jun 4, 2012, 1:30 PM

Post #2 of 11 (1065 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

I think you're confusing static (non-LACP) and active (LACP) trunks.

If you use active you don't use trunk statements. You should just be able
to remove the link-aggregate statements from the Ethernet interface.

Frank

-----Original Message-----
From: foundry-nsp-bounces [at] puck
[mailto:foundry-nsp-bounces [at] puck] On Behalf Of Robert Hass
Sent: Monday, June 04, 2012 2:56 PM
To: foundry-nsp [at] puck
Subject: [f-nsp] Remove one interface from LACP group

Hi

I have problem removing one interface from LACP trunk group. Here is
my configuration:

interface ethernet 1/1/5
port-name link01
no flow-control
link-aggregate configure key 30000
link-aggregate active
!
interface ethernet 1/1/6
port-name link02
link-aggregate configure key 30000
link-aggregate active
!
interface ethernet 1/1/7
port-name link03
link-aggregate configure key 30000
link-aggregate active

telnet [at] la#show link-ag
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/1/5 1 1 30000 Yes L Agg Syn Col Dis No No
Ope
1/1/6 1 1 30000 Yes L Agg Syn Col Dis No No
Ope
1/1/7 1 1 30000 Yes L Agg Syn Col Dis No No
Ope

I would like to remove port 1/1/6 from link-aggregation, but how I can do
this ?

telnet [at] la(config)#no trunk ethernet 1/1/6
Error - Please provide all (3) Lacp Trunk Ports

This not work.

telnet [at] la(config)#trunk ethernet 1/1/5 to 1/1/7
telnet [at] la(config-trunk-1/1/5-1/1/7)#disable ethernet 1/1/6
telnet [at] la(config-trunk-1/1/5-1/1/7)#no trunk e 1/1/6
Error - Please provide all (3) Lacp Trunk Ports

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

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

mkallen at gmail

Jun 4, 2012, 2:05 PM

Post #3 of 11 (1069 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

Robert, now that you have the port disabled, you should be able to go into
the interface e 1/1/16, and do a no link-agg active. Follow with a no
link-agg conf key 30000 (might not be needed once you pull off the link-agg
active), and you should be good to go.

Mike

On Mon, Jun 4, 2012 at 12:56 PM, Robert Hass <robhass [at] gmail> wrote:

> Hi
>
> I have problem removing one interface from LACP trunk group. Here is
> my configuration:
>
> interface ethernet 1/1/5
> port-name link01
> no flow-control
> link-aggregate configure key 30000
> link-aggregate active
> !
> interface ethernet 1/1/6
> port-name link02
> link-aggregate configure key 30000
> link-aggregate active
> !
> interface ethernet 1/1/7
> port-name link03
> link-aggregate configure key 30000
> link-aggregate active
>
> telnet [at] la#show link-ag
> 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/1/5 1 1 30000 Yes L Agg Syn Col Dis No No
> Ope
> 1/1/6 1 1 30000 Yes L Agg Syn Col Dis No No
> Ope
> 1/1/7 1 1 30000 Yes L Agg Syn Col Dis No No
> Ope
>
> I would like to remove port 1/1/6 from link-aggregation, but how I can do
> this ?
>
> telnet [at] la(config)#no trunk ethernet 1/1/6
> Error - Please provide all (3) Lacp Trunk Ports
>
> This not work.
>
> telnet [at] la(config)#trunk ethernet 1/1/5 to 1/1/7
> telnet [at] la(config-trunk-1/1/5-1/1/7)#disable ethernet 1/1/6
> telnet [at] la(config-trunk-1/1/5-1/1/7)#no trunk e 1/1/6
> Error - Please provide all (3) Lacp Trunk Ports
>
> Rob
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp [at] puck
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>

robhass at gmail

Jun 4, 2012, 2:37 PM

Post #4 of 11 (1066 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

On Mon, Jun 4, 2012 at 11:05 PM, Mike Allen <mkallen [at] gmail> wrote:
> Robert, now that you have the port disabled, you should be able to go into
> the interface e 1/1/16, and do a no link-agg active. �Follow with a no
> link-agg conf key 30000 (might not be needed once you pull off the link-agg
> active), and you should be good to go.

Yeah. I tried. But I cannot enter interface 1/1/6. It doesn't matter
it's disabled or enabled.

telnet [at] la(config-trunk-1/1/6)#int e 1/1/6
Error - cannot configure secondary ports of a trunk

telnet [at] la(config)#show link-a | inc 1/1/6
1/1/6 1 1 30000 Yes L Agg Syn Col Dis Def No Dwn

:(

Rob

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

robhass at gmail

Jun 4, 2012, 2:39 PM

Post #5 of 11 (1067 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

On Mon, Jun 4, 2012 at 10:30 PM, Frank Bulk <frnkblk [at] iname> wrote:
> I think you're confusing static (non-LACP) and active (LACP) trunks.
>
> If you use active you don't use trunk statements. �You should just be able
> to remove the link-aggregate statements from the Ethernet interface.

You're wrong. You have to use trunk statements if you want
disable/enable single port from LACP LAG or change port-name for
individual link within LACP LAG.

Rob

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

frnkblk at iname

Jun 4, 2012, 2:53 PM

Post #6 of 11 (1072 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

I haven't seemed to need to do that on the ICX6610 platform -- perhaps
that's the difference?

Frank

-----Original Message-----
From: Robert Hass [mailto:robhass [at] gmail]
Sent: Monday, June 04, 2012 4:39 PM
To: frnkblk [at] iname
Cc: foundry-nsp [at] puck
Subject: Re: [f-nsp] Remove one interface from LACP group

On Mon, Jun 4, 2012 at 10:30 PM, Frank Bulk <frnkblk [at] iname> wrote:
> I think you're confusing static (non-LACP) and active (LACP) trunks.
>
> If you use active you don't use trunk statements. �You should just be able
> to remove the link-aggregate statements from the Ethernet interface.

You're wrong. You have to use trunk statements if you want
disable/enable single port from LACP LAG or change port-name for
individual link within LACP LAG.

Rob

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

robhass at gmail

Jun 4, 2012, 3:09 PM

Post #7 of 11 (1070 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

On Mon, Jun 4, 2012 at 11:53 PM, Frank Bulk <frnkblk [at] iname> wrote:
> I haven't seemed to need to do that on the ICX6610 platform -- perhaps
> that's the difference?

It's ICX 6450 not 6610 :-)
IronWare 7.4

But it's not ICX related. I have same issue on old FastIron LS624 running 7.2.2d

BR-telnet [at] fl(config)#trunk ethernet 0/1/3 to 0/1/6
BR-telnet [at] fl(config-trunk-0/1/3-0/1/6)#config-trunk-ind
BR-telnet [at] fl(config-trunk-0/1/3-0/1/6)#disable ethernet 0/1/6
BR-telnet [at] fl(config-trunk-0/1/3-0/1/6)#int ethernet 0/1/6
Error - cannot configure secondary ports of a trunk

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

tcsillag at interware

Jun 4, 2012, 3:27 PM

Post #8 of 11 (1062 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

I think you just set up a static trunk over the lacp trunk with this:

BR-telnet [at] fl(config)#trunk ethernet 0/1/3 to 0/1/6

Check a 'show trunk' and a 'show link-ag' output, just to be sure...

Tamas

On 06/05/2012 12:09 AM, Robert Hass wrote:
> On Mon, Jun 4, 2012 at 11:53 PM, Frank Bulk<frnkblk [at] iname> wrote:
>> I haven't seemed to need to do that on the ICX6610 platform -- perhaps
>> that's the difference?
>
> It's ICX 6450 not 6610 :-)
> IronWare 7.4
>
> But it's not ICX related. I have same issue on old FastIron LS624 running 7.2.2d
>
> BR-telnet [at] fl(config)#trunk ethernet 0/1/3 to 0/1/6
> BR-telnet [at] fl(config-trunk-0/1/3-0/1/6)#config-trunk-ind
> BR-telnet [at] fl(config-trunk-0/1/3-0/1/6)#disable ethernet 0/1/6
> BR-telnet [at] fl(config-trunk-0/1/3-0/1/6)#int ethernet 0/1/6
> Error - cannot configure secondary ports of a trunk
>
> Rob
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp [at] puck
> http://puck.nether.net/mailman/listinfo/foundry-nsp

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

mkallen at gmail

Jun 4, 2012, 4:59 PM

Post #9 of 11 (1064 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

Try exit after you disable the port within the trunk. You are still in the
trunk configuration, different context. I don't have one to check this on
right now.

Mike

On Mon, Jun 4, 2012 at 3:09 PM, Robert Hass <robhass [at] gmail> wrote:

> On Mon, Jun 4, 2012 at 11:53 PM, Frank Bulk <frnkblk [at] iname> wrote:
> > I haven't seemed to need to do that on the ICX6610 platform -- perhaps
> > that's the difference?
>
> It's ICX 6450 not 6610 :-)
> IronWare 7.4
>
> But it's not ICX related. I have same issue on old FastIron LS624 running
> 7.2.2d
>
> BR-telnet [at] fl(config)#trunk ethernet 0/1/3 to 0/1/6
> BR-telnet [at] fl(config-trunk-0/1/3-0/1/6)#config-trunk-ind
> BR-telnet [at] fl(config-trunk-0/1/3-0/1/6)#disable ethernet 0/1/6
> BR-telnet [at] fl(config-trunk-0/1/3-0/1/6)#int ethernet 0/1/6
> Error - cannot configure secondary ports of a trunk
>
> Rob
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp [at] puck
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>

mkallen at gmail

Jun 4, 2012, 8:06 PM

Post #10 of 11 (1069 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

And yes, Tamas is correct. There are two methods to configure trunks in
the FastIron code base. Static trunking (Etherchannel) via the trunk
ethernet command, and true dynamic 802.3ad through the use of the link-agg
commands under the physical interface. You don't want/need to do both. In
your config Robert, the reason you are getting that error is you are under
the trunk context. If you exit out to the global config, then enter the
interface 1/1/6, you should be able to take out the link-agg commands,
though you may need to disable it first.

Mike

On Mon, Jun 4, 2012 at 3:27 PM, Tamas Csillag <tcsillag [at] interware> wrote:

> I think you just set up a static trunk over the lacp trunk with this:
>
>
> BR-telnet [at] fl(config)#trunk ethernet 0/1/3 to 0/1/6
>
> Check a 'show trunk' and a 'show link-ag' output, just to be sure...
>
> Tamas
>
>
>
> On 06/05/2012 12:09 AM, Robert Hass wrote:
>
>> On Mon, Jun 4, 2012 at 11:53 PM, Frank Bulk<frnkblk [at] iname> wrote:
>>
>>> I haven't seemed to need to do that on the ICX6610 platform -- perhaps
>>> that's the difference?
>>>
>>
>> It's ICX 6450 not 6610 :-)
>> IronWare 7.4
>>
>> But it's not ICX related. I have same issue on old FastIron LS624 running
>> 7.2.2d
>>
>> BR-telnet [at] fl(config)#trunk ethernet 0/1/3 to 0/1/6
>> BR-telnet [at] fl(config-trunk-0/**1/3-0/1/6)#config-trunk-ind
>> BR-telnet [at] fl(config-trunk-0/**1/3-0/1/6)#disable ethernet 0/1/6
>> BR-telnet [at] fl(config-trunk-0/**1/3-0/1/6)#int ethernet 0/1/6
>> Error - cannot configure secondary ports of a trunk
>>
>> Rob
>> ______________________________**_________________
>> foundry-nsp mailing list
>> foundry-nsp [at] puck
>> http://puck.nether.net/**mailman/listinfo/foundry-nsp<http://puck.nether.net/mailman/listinfo/foundry-nsp>
>>
>
> ______________________________**_________________
> foundry-nsp mailing list
> foundry-nsp [at] puck
> http://puck.nether.net/**mailman/listinfo/foundry-nsp<http://puck.nether.net/mailman/listinfo/foundry-nsp>
>

robhass at gmail

Jun 4, 2012, 11:18 PM

Post #11 of 11 (1073 views)
Permalink

Re: Remove one interface from LACP group [In reply to]

On Tue, Jun 5, 2012 at 12:27 AM, Tamas Csillag <tcsillag [at] interware> wrote:
> I think you just set up a static trunk over the lacp trunk with this:

No

telnet [at] la#sh run | inc trunk
trunk hash-options include-layer2
telnet [at] la#
_______________________________________________
foundry-nsp mailing list
foundry-nsp [at] puck
http://puck.nether.net/mailman/listinfo/foundry-nsp

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads