LACP configuration

[Tugen]

Hello friends!

I am trying to configure LACP between my Juniper SRX240 (JunOS 12.3) and Quanta LB6M. So far, I'm stuck. Let me show you my current configuration on both devices.

Quanta LB6M configuration

interface 0/25
addport 1/1
exit

interface 0/26
addport 1/1
exit

interface 0/27
addport 1/1
exit

interface 0/28
addport 1/1
exit

interface 0/25
port lacptimeout actor short
port lacptimeout partner short
no lacp actor admin state longtimeout
no lacp partner admin state longtimeout
exit

interface 0/26
port lacptimeout actor short
port lacptimeout partner short
no lacp actor admin state longtimeout
no lacp partner admin state longtimeout
exit

interface 0/27
port lacptimeout actor short
port lacptimeout partner short
no lacp actor admin state longtimeout
no lacp partner admin state longtimeout
exit

interface 0/28
port lacptimeout actor short
port lacptimeout partner short
no lacp actor admin state longtimeout
no lacp partner admin state longtimeout
exit

interface 1/1
no port-channel static
vlan acceptframe vlanonly
vlan participation include 10,20,30,100
vlan tagging 10,20,30,100
exit

Status:

Local Interface................................ 1/1
Channel Name................................... ch1
Link State..................................... Down
Admin Mode..................................... Enabled
Type........................................... Dynamic
Port-channel Min-links......................... 1
Load Balance Option............................ 3
(Src/Dest MAC, VLAN, EType, incoming port)

Mbr    Device/       Port      Port
Ports  Timeout       Speed     Active
------ ------------- --------- -------
0/25   actor/short   Auto      False
       partner/short
0/26   actor/short   Auto      False
       partner/short
0/27   actor/short   Auto      False
       partner/short
0/28   actor/short   Auto      False
       partner/short

Juniper SRX240 configuration

ge-0/0/12 {
    gigether-options {
        802.3ad ae0;
    }
    inactive: unit 0 {
        family ethernet-switching {
            vlan {
                members vlan-trust;
            }
        }
    }
}
ge-0/0/13 {
    gigether-options {
        802.3ad ae0;
    }
    inactive: unit 0 {
        family ethernet-switching {
            vlan {
                members vlan-trust;
            }
        }
    }
}
ge-0/0/14 {
    gigether-options {
        802.3ad ae0;
    }
    inactive: unit 0 {
        family ethernet-switching {
            vlan {
                members vlan-trust;
            }
        }
    }
}
ge-0/0/15 {
    gigether-options {
        802.3ad ae0;
    }
    inactive: unit 0 {
        family ethernet-switching {
            vlan {
                members vlan-trust;
            }
        }
    }
}
ae0 {
    aggregated-ether-options {
        lacp {
            active;
        }
    }
    unit 0 {
        family bridge {
            interface-mode trunk;
            vlan-id-list [ 10 20 30 100 ];
        }
    }
}

LACP status:

root> show lacp interfaces
Aggregated interface: ae0
    LACP state:       Role   Exp   Def  Dist  Col  Syn  Aggr  Timeout  Activity
      ge-0/0/12      Actor    No   Yes    No   No   No   Yes     Fast    Active
      ge-0/0/12    Partner    No   Yes    No   No   No   Yes     Fast   Passive
      ge-0/0/13      Actor    No   Yes    No   No   No   Yes     Fast    Active
      ge-0/0/13    Partner    No   Yes    No   No   No   Yes     Fast   Passive
      ge-0/0/14      Actor    No   Yes    No   No   No   Yes     Fast    Active
      ge-0/0/14    Partner    No   Yes    No   No   No   Yes     Fast   Passive
      ge-0/0/15      Actor    No   Yes    No   No   No   Yes     Fast    Active
      ge-0/0/15    Partner    No   Yes    No   No   No   Yes     Fast   Passive
    LACP protocol:        Receive State  Transmit State          Mux State
      ge-0/0/12               Defaulted   Fast periodic           Detached
      ge-0/0/13               Defaulted   Fast periodic           Detached
      ge-0/0/14               Defaulted   Fast periodic           Detached
      ge-0/0/15               Defaulted   Fast periodic           Detached

Status on the SRX is detatched and the LB6M status shows down. I am not sure what to do here. Do you have any advice?

 

[Tugen]

Managed to solve the issue by rebooting the systems...
Had to move them to another location, and now it's just working like a dream

 

[shishir]

Managed to solve the issue by rebooting the systems...
Had to move them to another location, and now it's just working like a dream

Hi Tugen,

My doubt is that as we are aware partner system is the one whose values are strategised only from the packet what we are receiving, Why we have the option to Configure Partner state ? If we are configuring partner details should it get changed or not upon receiving the packet details from the remote(partner) node ? Do we need to store the "User Configured" values of Partner ? If yes, then why ? The decisions to send BPDU or not, will be taken based upon "User Configured" partner values or not ? If the decision will be taken upon "Dynamic Remote-Partner-Value" then what will be the use of "User-Configured Partner values", at the end should we have only 1 value after the negotiation or we need to store both the values(user configured values + remote_partner_packet received value)