Comware

 View Only
  • 1.  LACP Across IRF

    Posted Sep 27, 2013 03:58 PM

    Just checking real quick, but I bet LACP doesn't work across an IRF bond. I have a StoreOnce 2620 setup with LACP connected to 2 A-Series switches on P1211P01. I can ping the device from the same subnet but I cannot ping it successfully from another VLAN. 

     

    Port 1 is on 1/0/1 and port 2 of is on 2/0/1. Both ports are members of the link agg group. Jumbo frames and flow-control are on. Just looking for a quick answer on this. 

    Thanks all.



  • 2.  RE: LACP Across IRF

    Posted Sep 28, 2013 08:48 AM

    Hi,

     

    Please post config.

     

    LACP is fully supported across IRF boards, this must be other issue.

     

    To verify lacp:

    dis link-agg summary

    dis link-agg verbose

     

    You should see both links are in selected state.

     

    The fact you cannot ping from a remote subnet must be a routing issue, so we need more config (ip information, switch config, ports used) to help you with this,

     

    Best regards,Peter.



  • 3.  RE: LACP Across IRF

    Posted Sep 30, 2013 10:58 AM

    Normally I would say you are right with the routing thing, but the device worked fine before I converted to an LACP config with the same IP address. Here is my config:

     

    [A3IDC_DR_10.1-GigabitEthernet2/0/11]disp int brief | inc D2D
    The brief information of interface(s) under bridge mode:
    Link: ADM - administratively down; Stby - standby
    Speed or Duplex: (a)/A - auto; H - half; F - full
    Type: A - access; T - trunk; H - hybrid
    Interface Link Speed Duplex Type PVID Description
    BAGG1 UP 2G(a) F(a) A 5 Uplink for HP D2D Device
    GE1/0/11 UP 1G(a) F(a) A 5 HPD2D Port 2
    GE1/0/17 UP 100M(a) F(a) A 2 HPD2D iLO
    GE2/0/11 UP 1G(a) F(a) A 5 HPD2D Port 1

    #
    interface Bridge-Aggregation1
    description Uplink for HP D2D Device
    port access vlan 5
    #
    #
    interface Vlan-interface5
    ip address 10.248.67.1 255.255.255.0
    #
    #
    interface GigabitEthernet1/0/11
    port link-mode bridge
    description HPD2D Port 2
    port access vlan 5
    flow-control receive enable
    jumboframe enable 9000
    port link-aggregation group 1
    #
    #
    interface GigabitEthernet2/0/11
    port link-mode bridge
    description HPD2D Port 1
    port access vlan 5
    flow-control receive enable
    jumboframe enable 9000
    port link-aggregation group 1
    #
    #
    irf-port 1/1
    port group interface Ten-GigabitEthernet1/0/25 mode enhanced
    #
    irf-port 2/2
    port group interface Ten-GigabitEthernet2/0/25 mode enhanced

     

    dis ling-agg sum:

    <A3IDC_DR_10.1>disp link-agg summ

    Aggregation Interface Type:
    BAGG -- Bridge-Aggregation, RAGG -- Route-Aggregation
    Aggregation Mode: S -- Static, D -- Dynamic
    Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
    Actor System ID: 0x8000, b8af-673d-bfd3

    AGG AGG Partner ID Select Unselect Share
    Interface Mode Ports Ports Type
    -------------------------------------------------------------------------------
    BAGG1 S none 2 0 Shar
    BAGG2 S none 0 0 Shar
    BAGG3 S none 0 0 Shar

     

    dis link-agg verbose

     

    <A3IDC_DR_10.1>disp link-agg verb

    Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
    Port Status: S -- Selected, U -- Unselected
    Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
    D -- Synchronization, E -- Collecting, F -- Distributing,
    G -- Defaulted, H -- Expired

    Aggregation Interface: Bridge-Aggregation1
    Aggregation Mode: Static
    Loadsharing Type: Shar
    Port Status Oper-Key
    --------------------------------------------------------------------------------
    GE1/0/11 S 1
    GE2/0/11 S 1

    Aggregation Interface: Bridge-Aggregation2
    Aggregation Mode: Static
    Loadsharing Type: Shar
    Port Status Oper-Key
    --------------------------------------------------------------------------------

    Aggregation Interface: Bridge-Aggregation3
    Aggregation Mode: Static
    Loadsharing Type: Shar
    Port Status Oper-Key
    --------------------------------------------------------------------------------

     



  • 4.  RE: LACP Across IRF

    Posted Sep 30, 2013 11:21 AM

    Here's a random Q: Do I have to use the following command when configuring an LACP group across switches?

     

    > link-aggregation lacp taffic-redirect-notification  enable



  • 5.  RE: LACP Across IRF

    Posted Sep 30, 2013 11:35 AM
    This issue is not resolved.


  • 6.  RE: LACP Across IRF

    Posted Sep 30, 2013 11:54 AM

    I think I corrected the issue on my own after messing around with it all morning. Here's what I had previously:

     

    #
    interface Bridge-Aggregation1
    description Uplink for HP D2D Device
    port access vlan 5
    #

     

     

    I found a command about dynamic configuration so I changed it to this:

     

    #
    interface Bridge-Aggregation1
    description Uplink for HP D2D Device
    port access vlan 5

    link-aggregation mode dynamic
    #

     

    Can someone explain to me why this helped?



  • 7.  RE: LACP Across IRF

    Posted Sep 30, 2013 12:24 PM

    Hi,

     

    link-aggregation mode dynamic = use LACP.

    So by default, when a bridge-agg interface is defined, it is a static link-agg (no lacp), so if the remote end has LACP turn on, then it is possible that the remote end is blocking (in sw) 1 of the 2 links ( since no LACP packet activity), which could explain why some traffic was not working.

     

    The traffic redirect is only used between comware based switches, when ISSU is being doing (it will signal the remote switch  to stop using 1 of the links, since the unit will soon reboot for firmware update).

     

    Best regards,Peter.



  • 8.  RE: LACP Across IRF

    Posted Sep 30, 2013 04:53 PM
    Your explanation was much better than the one I got from the HP Networking group. Thank you.