Ethernet Switches & Routers

Reply
Contributor
arrowsivac
Posts: 37
Registered: ‎05-24-2010

LACP Brocade 8000 to IBM Blade Convergence Switch Protocol Down

Hardware: IBM Blade H chassis with Brocade  Convergence switch http://www.redbooks.ibm.com/abstracts/tips0789.html   connected to top of rack pair of Brocade branded 8000 switches.  Servers  are HS22 blades with Broade CNA 10Gb.

Issues:  Trying to get two ethernet 10Gb links to join into LACP aggregate, from  the blade switch to the 8000.  End design will have cross connected  20Gb links to the pair of 8000 to provide LAN NSPOF.   I am just not at  this time able to get any single link to go "protocol up"

Diagram:

<attached>

Configureation:

sw12sw28

!
interface TenGigabitEthernet 0/16
description sw28-22
channel-group 1 mode active type standard
no shutdown
lacp timeout long
!
interface TenGigabitEthernet 0/17
description sw28-21
channel-group 1 mode active type standard
no shutdown
lacp timeout long
!

!
interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown
!

!
interface ExTengigabitEthernet 0/21
description sw12-17
channel-group 1 mode passive type standard
no shutdown
lacp timeout long
!
interface ExTengigabitEthernet 0/22
description sw12-16
channel-group 1 mode passive type standard
no shutdown
lacp timeout long
!
interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
shutdown
!
sw12#sh interface Port-channel 1
Port-channel 1 is up, line protocol is down
Hardware is AGGREGATE, address is 0005.1ee0.b9bc
    Current address is 0005.1ee0.b9bc
  Description: sw12-16_17 to sw28-21-22
Interface index (ifindex) is 671088641
MTU 2500 bytes
LineSpeed: Auto
sw28#sh interface Port-channel 1
Port-channel 1 is up, line protocol is down (link protocol down)
Hardware is AGGREGATE, address is 0005.33a9.9335
    Current address is 0005.33a9.9335
  Description: sw12-16_17 to sw28-21-22
Interface index (ifindex) is 671088641
Minimum number of links to bring Port-channel up is 1
Members in this channel: ExT 0/22(up) ExT 0/21(up)
MTU 2500 bytes
LineSpeed: Auto
sw12#sh port-channel 1
% Aggregator Po 1 0 Admin Key: 0001 - Oper Key 0001 Partner System ID: 0x0000,00-00-00-00-00-00 Partner Oper Key 0000
%   Link: Te 0/16 (403702272) sync: 0
%   Link: Te 0/17 (403767809) sync: 0
sw28#sh port-channel 1
Aggregator Po 1 0 Admin Key: 0001 - Oper Key 0001 Partner System ID: 0x0000,00-00-00-00-00-00 Partner Oper Key 0000
   Link: ExT 0/21 (404029461) sync: 0
   Link: ExT 0/22 (404094998) sync: 0
sw12#sh port-channel detail
% Aggregator Po 1
%  Actor System ID - 0x8000,00-05-1e-e0-b9-a4
%  Admin Key: 0001 - Oper Key 0001
%  Receive link count: 0 - Transmit link count: 0
%  Individual: 0 - Ready: 0
%  Partner System ID - 0x0000,00-00-00-00-00-00
%   Link: Te 0/16 (0x18100200) sync: 0
%   Link: Te 0/17 (0x18110201) sync: 0
sw28#sh port-channel detail
Static Aggregator: Po 2
Aggregator type: Standard
Member:
Aggregator Po 1
  Actor System ID - 0x8000,00-05-33-a9-93-2c
  Admin Key: 0001 - Oper Key 0001
  Receive link count: 0 - Transmit link count: 0
  Individual: 0 - Ready: 0
  Partner System ID - 0x0000,00-00-00-00-00-00
   Link: ExT 0/21 (0x18150015) sync: 0
   Link: ExT 0/22 (0x18160016) sync: 0

I  set the type of trunk on the 8000 to LACP mode "active" and the mode  type on the IBM Blade switch to "passive" (I have tried other variations  but no change)

I have read through the Brocade 8000  Advanced Administration guide and deployment, not finding much that I  could use to detail mode types.   If someone has a better manual they  can point me to that would be appreciated.

Thanks.

Contributor
serhat.kahraman
Posts: 61
Registered: ‎12-08-2009

Re: LACP Brocade 8000 to IBM Blade Convergence Switch Protocol Down

Hi Can you try as below?

sw12sw28

interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown

interface TenGigabitEthernet 0/16
description sw28-22
channel-group 1 mode on
no shutdown


interface TenGigabitEthernet 0/17
description sw28-21
channel-group 1 mode on
no shutdown

interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown


interface ExTengigabitEthernet 0/21
description sw12-17
channel-group 1 mode on
no shutdown


interface ExTengigabitEthernet 0/22
description sw12-16
channel-group 1 mode on
no shutdown



After this you can play with the configuration of server adapters, they should be set as static LAG with this configuration.
Btw I see 4 ports are involved in the connection for each 8000 but you have two ports configured.

Hope this helps

Contributor
arrowsivac
Posts: 37
Registered: ‎05-24-2010

Re: LACP Brocade 8000 to IBM Blade Convergence Switch Protocol Down

I made changes as noted and no difference.  I am about 90% sure I tried that variation (and many others) to get the link to come up.

Here is the current state:

sw12sw28

!
interface TenGigabitEthernet 0/16
description sw28-22
channel-group 1 mode on type standard
no shutdown
!
interface TenGigabitEthernet 0/17
description sw28-21
channel-group 1 mode on type standard
no shutdown

!
interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown
!

!
interface ExTengigabitEthernet 0/21
description sw12-17
channel-group 1 mode on type standard
no shutdown
!
interface ExTengigabitEthernet 0/22
description sw12-16
channel-group 1 mode on type standard
no shutdown
!

interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown
!

sw12#sh interface port-channel 1
Port-channel 1 is up, line protocol is down
Hardware is AGGREGATE, address is 0005.1ee0.b9bc
    Current address is 0005.1ee0.b9bc
  Description: sw12-16_17 to sw28-21-22
Interface index (ifindex) is 671088641
MTU 2500 bytes
LineSpeed: 20000 Mbit
Last clearing of show interface counters: 1w6d23h
Queueing strategy: fifo
Receive Statistics:
    0 packets, 0 bytes
sw28#sh interface port-channel 1
Port-channel 1 is up, line protocol is down (link protocol down)
Hardware is AGGREGATE, address is 0005.33a9.9335
    Current address is 0005.33a9.9335
  Description: sw12-16_17 to sw28-21-22
Interface index (ifindex) is 671088641
Minimum number of links to bring Port-channel up is 1
Members in this channel: ExT 0/22(up) ExT 0/21(up)
MTU 2500 bytes
LineSpeed: Auto

Thanks for the post.. Still looking for other ideas.

Valued Contributor
TechHelp24
Posts: 3,634
Registered: ‎02-23-2004

Re: LACP Brocade 8000 to IBM Blade Convergence Switch Protocol Down

arrowsivac,

just a Tipp....

I have no experienced, and I'm no familiary with those IBM Converged Switch, but is know to me from Standard FC Blade Switch in IBM Blade Center that External Port must be Activated, by default are External Port Deactivated.

Go to Management Mudule and check if all Port are Correct Active and Up.

TechHelp24
Contributor
serhat.kahraman
Posts: 61
Registered: ‎12-08-2009

Re: LACP Brocade 8000 to IBM Blade Convergence Switch Protocol Down

I just realized there is a "no" missing before shutdown on your first configuration(in second coloumn)
So you can try same LACP config as below:

sw12sw28

interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown

interface TenGigabitEthernet 0/16
description sw28-22
channel-group 1 mode active type standard
no shutdown


interface TenGigabitEthernet 0/17
description sw28-21
channel-group 1 mode active type standard
no shutdown

interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown


interface ExTengigabitEthernet 0/21
description sw12-17
channel-group 1 mode active type standard
no shutdown


interface ExTengigabitEthernet 0/22
description sw12-16
channel-group 1 mode active type standard
no shutdown

you can try  plugging the cables after you apply this config.

and be sure you have correct LACP configuration on your blade switch

you should be  able to see synch:1 under
sh port-channel detail
command

Also this post can be helpful:

http://community.brocade.com/message/21137#21137

hope this helps,

Contributor
arrowsivac
Posts: 37
Registered: ‎05-24-2010

Re: LACP Brocade 8000 to IBM Blade Convergence Switch Protocol Down

THanks for reply.

I originally set the "channel-group 1 mode active" on all physical intefaces for that reason, in that both sides need to work to handshake the LACP link.

In other switch vendors you can set one side to "pasive" and other side to "active" and that is also typical. My original post was based on that... SW12 the Brocade TOR 8000 was active with SW28 in the IBM chassis as passive.

All physical ports on both switches are now "channel-group 1 mode active"

sw28#sh interface Port-channel 1
Port-channel 1 is up, line protocol is down (link protocol down)
Hardware is AGGREGATE, address is 0005.33a9.9335
    Current address is 0005.33a9.9335
  Description: sw12-16_17 to sw28-21-22
Interface index (ifindex) is 671088641
Minimum number of links to bring Port-channel up is 1
Members in this channel: ExT 0/21(up) ExT 0/22(up)
MTU 2500 bytes
LineSpeed: Auto
Last clearing of show interface counters: 1w3d22h
Queueing strategy: fifo

sw12#sh interface Port-channel 1
Port-channel 1 is up, line protocol is down
Hardware is AGGREGATE, address is 0005.1ee0.b9bc
    Current address is 0005.1ee0.b9bc
  Description: sw12-16_17 to sw28-21-22
Interface index (ifindex) is 671088641
MTU 2500 bytes
LineSpeed: Auto
Last clearing of show interface counters: 2w0d02h
Queueing strategy: fifo
Receive Statistics:

Still looking for resolution

Contributor
arrowsivac
Posts: 37
Registered: ‎05-24-2010

Re: LACP Brocade 8000 to IBM Blade Convergence Switch Protocol Down

This has been resolved.

I had to step back a bit and do some baselining:  Tested the cables by connecting each switch "to itself" with the SFP + Copper cable with a simple "switchport" mode connection. Once that link came admin up protocol up it was just taking one step at a time to connect.  In the end I don't know what I had done wrong, but below is a working and valid configuation.

(Brocade 8000 TOR Switches)
SW28 Brocade Blade IBM Switch  69Y1909

##### SW12

!
interface TenGigabitEthernet 0/16
description sw28-22
channel-group 1 mode active type standard
no shutdown
lacp timeout long
!
interface TenGigabitEthernet 0/17
description sw28-21
channel-group 1 mode active type standard
no shutdown
lacp timeout long

!
interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown
!

##### SW13

!
interface TenGigabitEthernet 0/20
description sw28-20
channel-group 2 mode active type standard
no shutdown
lacp timeout long
!
interface TenGigabitEthernet 0/21
description sw28-19
channel-group 4 mode active type standard
no shutdown
lacp timeout long
!
interface Port-channel 2
description sw13-20_21 to sw28-19-20
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown
!

!
interface ExTengigabitEthernet 0/19
description sw13-21
channel-group 2 mode passive type standard
no shutdown
lacp timeout long
!
interface ExTengigabitEthernet 0/20
description sw13-20
channel-group 2 mode passive type standard
no shutdown
lacp timeout long
!

interface ExTengigabitEthernet 0/21
description sw12-17
channel-group 1 mode passive type standard
no shutdown
lacp timeout long
!
interface ExTengigabitEthernet 0/22
description sw12-16
channel-group 1 mode passive type standard
no shutdown
lacp timeout long
!
interface Port-channel 1
description sw12-16_17 to sw28-21-22
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown

!
interface Port-channel 2
description sw13-20_21 to sw28-20_19
switchport
switchport mode trunk
switchport trunk allowed vlan all
no shutdown
!

protocol lldp

Thanks for all the help and ideas.

Join the Community

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