Ethernet Switches & Routers

Reply
Occasional Contributor
Posts: 5
Registered: ‎12-12-2016

LAG problem between 6610-24f and 7250

dears

i create a LAG between 6610-24f and 7250 ,but one of the two links are down.

 i have use the configuration bellow:

in 7250:

 

lag 7250-6610 daynamic
ports e 1/2/2 e 1/2/8

prim  1/2/2
deploy

 

in 6610

 

lag 7250-6610 daynamic
ports e 1/1/1 e 1/1/19

prim  1/2/2
deploy

 

and there is some show commands:

 

7250(config)#sh span

STP instance owned by VLAN 1

Global STP (IEEE 802.1D) Parameters:

     Root             Root Root      Prio Max He- Ho- Fwd Last    Chg Bridge
      ID              Cost Port      rity Age llo ld  dly Chang   cnt Address
                                     Hex  sec sec sec sec sec
     8000609c9f038ff8 8    1/2/2     8000 20  2   1   15  3167    20  609c9f039844

Port STP Parameters:

Port      Prio Path  State       Fwd    Design  Designated       Designated
Num       rity Cost              Trans  Cost    Root             Bridge
          Hex
1/1/1     80   19    FORWARDING  3      8       8000609c9f038ff8 8000609c9f039844
1/1/2     80   19    FORWARDING  3      8       8000609c9f038ff8 8000609c9f039844
1/1/3     80   0     DISABLED    0      0       0000000000000000 0000000000000000
1/1/4     80   0     DISABLED    0      0       0000000000000000 0000000000000000
1/1/5     80   19    FORWARDING  3      8       8000609c9f038ff8 8000609c9f039844
1/1/6     80   0     DISABLED    0      0       0000000000000000 0000000000000000
1/1/7     80   19    FORWARDING  3      8       8000609c9f038ff8 8000609c9f039844
1/1/8     80   19    FORWARDING  3      8       8000609c9f038ff8 8000609c9f039844
1/1/9     80   19    FORWARDING  3      8       8000609c9f038ff8 8000609c9f039844
1/1/10    80   4     FORWARDING  1      8       8000609c9f038ff8 8000609c9f039844
1/1/11    80   4     FORWARDING  2      8       8000609c9f038ff8 8000609c9f039844
1/1/12    80   4     FORWARDING  1      8       8000609c9f038ff8 8000609c9f039844
1/1/13    80   4     FORWARDING  1      8       8000609c9f038ff8 8000609c9f039844
1/1/14    80   4     FORWARDING  1      8       8000609c9f038ff8 8000609c9f039844
1/1/15    80   4     FORWARDING  5      8       8000609c9f038ff8 8000609c9f039844
1/1/16    80   4     FORWARDING  1      8       8000609c9f038ff8 8000609c9f039844
1/1/17    80   4     FORWARDING  1      8       8000609c9f038ff8 8000609c9f039844
1/1/18    80   4     FORWARDING  1      8       8000609c9f038ff8 8000609c9f039844
1/1/19    80   100   FORWARDING  1      8       8000609c9f038ff8 8000609c9f039844
1/1/20    80   4     FORWARDING  5      8       8000609c9f038ff8 8000609c9f039844
1/1/21    80   4     FORWARDING  6      8       8000609c9f038ff8 8000609c9f039844
1/1/22    80   4     FORWARDING  39     8       8000609c9f038ff8 8000609c9f039844
1/1/23    80   4     FORWARDING  9      8       8000609c9f038ff8 8000609c9f039844
1/1/24    80   4     DISABLED    1      8       8000609c9f038ff8 8000609c9f039844
1/2/1     80   0     DISABLED    0      0       0000000000000000 0000000000000000
1/2/2     80   4     FORWARDING  5      4       8000609c9f038ff8 8000cc4e24c55c0c
1/2/3     80   0     DISABLED    0      0       0000000000000000 0000000000000000
1/2/4     80   0     DISABLED    0      0       0000000000000000 0000000000000000
1/2/5     80   0     DISABLED    0      0       0000000000000000 0000000000000000
1/2/6     80   0     DISABLED    0      0       0000000000000000 0000000000000000
1/2/7     80   0     DISABLED    0      0       0000000000000000 0000000000000000
1/2/8     80   4     FORWARDING  5      4       8000609c9f038ff8 8000cc4e24c55c0c
=====================================

7250(config)#sh lag
Total number of LAGs:          1
Total number of deployed LAGs: 1
Total number of trunks created:1 (126 available)
LACP System Priority / ID:     1 / 609c.9f03.9844
LACP Long timeout:             90, default: 90
LACP Short timeout:            3, default: 3

=== LAG "7250to6610" ID 1 (dynamic Deployed) ===
LAG Configuration:
   Ports:         e 1/2/2 e 1/2/8
   Port Count:    2
   Primary Port:  1/2/2
   Trunk Type:    hash-based
   LACP Key:      20001
Deployment: HW Trunk ID 1
Port       Link    State   Dupl Speed Trunk Tag Pvid Pri MAC             Name
1/2/2      Down    None    None None  1     No  1    0   609c.9f03.985e
1/2/8      Up      Forward Full 1G    1     No  1    0   609c.9f03.985e

Port       [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope]
1/2/2           1        1   20001   Yes   L   Agg  Syn  No   No   Def  No   Dwn
1/2/8           1        1   20001   Yes   L   Agg  Syn  Col  Dis  No   No   Ope


 Partner Info and PDU Statistics
Port          Partner         Partner     LACP      LACP
             System MAC         Key     Rx Count  Tx Count
1/2/2        0000.0000.0000       65        0         0
1/2/8        cc4e.24c5.5c0c    20001      114       113

 

 

 

i alrady tried the Static LAG and same problem,

i tried to off the spanning tree and same problem too.

 

note:no other configs in the switches.

and im sure that the SFPs and cables works properly.

 

 

regards

External Moderator
Posts: 4,857
Registered: ‎02-23-2004

Re: LAG problem between 6610-24f and 7250

[ Edited ]

@sajjad

 

@bhadley

 

http://community.brocade.com/t5/Ethernet-Switches-Routers/how-to-connect-two-switch-with-more-than-one-link/m-p/92674

 

in you case, and as per my opinion you have different Produts Lines as descripted in this Guide

 

http://www.brocade.com/content/html/en/configuration-guide/FI_08030_L2/GUID-347A20B4-1425-42B6-A7EA-F4295AB5A1A0.html

 

You cannot create a LAG between devices that belong to different product lines in a mixed stack. For example, between an ICX 6610 and an ICX 6450.

 

but I'll not insist and is probable I'm wrong here.....

TechHelp24
Frequent Contributor
Posts: 91
Registered: ‎07-20-2015

Re: LAG problem between 6610-24f and 7250

Actually that should wrok perfectly fine.

 

What they mean by between different product lines is that you cannot stack two compatible but different chassis units from different switch families and put part of the LAG on physical switch 1 and another part on switch 2.

 

As long as both primary and secondary ports are on the same stack unit, you should be perfectly fine.

 

The LAG itself is an open standard taht uses LACP vs the proprietary PaGP used on Cisco.  You can even create a LAG from say Brocade devices to HP Procurve... or from Brocade to Cisco (provided you chagne the EtherChannel to LACP).

 

What they mean is you cannot do 1/x/y and 2/x/y if those stanced members are from different product lines.

Brocadian
Posts: 3
Registered: ‎02-21-2012

Re: LAG problem between 6610-24f and 7250

Are you sure about ICX6610 LAG config?
In ICx6610 LAG config, the ports are e1/1/1 and e1/1/19 but primary is e1/2/2 (?).
Then, e1/2/2 on the 7250 is down.
Is it connected to e1/1/1 on the 6610?
Try to change the primary to e1/1/1 on the 6610
Highlighted
Frequent Contributor
Posts: 91
Registered: ‎07-20-2015

Re: LAG problem between 6610-24f and 7250

[ Edited ]

Primary would have to be 1/1/1 or 1/1/19

 

After that it will work fine as a LAG to a 7250

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.