[j-nsp] Link aggregation between a 3750 and a M320

ILTCHEV Alain Alain.ILTCHEV at ncnumericable.com
Wed Feb 21 07:55:39 EST 2007


I am using indeed 7.6R1.9 . I wasn't aware of this bug. Thanks!

By redoing it again, I managed to activate the trunk by forcing "channel-group 1 mode on" on both 3750 interfaces, putting the M320 in LACP passive mode and forcing all ports in a "no negociation" mode (they were already in this state before).

As far as I have understood, in this mode, LACP is not activated on Cisco side. 

CBV1SC(config-if)#channel-group 1 mode ?
  active     Enable LACP unconditionally
  auto       Enable PAgP only if a PAgP device is detected
  desirable  Enable PAgP unconditionally
  on         Enable Etherchannel only   <---- HERE
  passive    Enable LACP only if a LACP device is detected

What does LACP bring more when it is working compared to this "Etherchannel only" mode ? Is it less reliable to leave it in this state without LACP activated ?

For Vijay, I think that in my case , the M320 and the 3750 are negotiating themselves which actor and partner key.

Alain



-----Message d'origine-----
De : Josef Buchsteiner [mailto:josefb at juniper.net]
Envoyé : mercredi 21 février 2007 13:39
À : ILTCHEV Alain
Cc : juniper-nsp at puck.nether.net
Objet : Re: [j-nsp] Link aggregation between a 3750 and a M320




What version are you running ? If you are on 7.6-8.1 then you are
effected  with  PR95015.  LACP  did  not used always the correct
interface  index  .32767  once  you  have  received  it.  If  you
deactivate/activate  the  ge-4/1/4  and  ge-4/1/5 then you should
get the aggregate into up state.

thanks
Josef

Wednesday, February 21, 2007, 11:02:17 AM, you wrote:

IA>    
IA>    
IA> Hello,
IA>  
IA>  I have been reading some past discussions in this mailing
IA> and trying things suggested in these discussions but I am not
IA> able to setup a LACP link between a Cisco switch and a M320.
IA>  
IA>  In the following, the M320 was in active mode and the 3750 in passive mode.
IA>  
IA>  On the 3750 :
IA>  interface GigabitEthernet1/0/49
IA>   switchport trunk encapsulation dot1q
IA>   switchport trunk allowed vlan 701,702,705
IA>   switchport mode trunk
IA>   switchport nonegotiate
IA>   speed nonegotiate
IA>   channel-group 1 mode active
IA>  end
IA>  
IA>  interface GigabitEthernet1/0/50
IA>   switchport trunk encapsulation dot1q
IA>   switchport trunk allowed vlan 701,702,705
IA>   switchport mode trunk
IA>   switchport nonegotiate
IA>   speed nonegotiate
IA>   channel-group 1 mode active
IA>  end
IA>  
IA>  interface Port-channel1
IA>   switchport trunk encapsulation dot1q
IA>   switchport trunk allowed vlan 701,702,705
IA>   switchport mode trunk
IA>   switchport nonegotiate
IA>   speed nonegotiate
IA>  
IA>  On the M320 :
IA>  chassis {
IA>      aggregated-devices {
IA>          ethernet {
IA>              device-count 16;
IA>          }
IA>  ...
IA>  ge-4/1/4 {
IA>      description "LAG 3750-1 VOIP Port 1";
IA>      gigether-options {
IA>          no-auto-negotiation;
IA>          802.3ad ae4;
IA>      }
IA>  }
IA>  ge-4/1/5 {
IA>      description "LAG 3750-1 VOIP Port 2";
IA>      gigether-options {
IA>          no-auto-negotiation;
IA>          802.3ad ae4;
IA>      }
IA>  }
IA>  ...
IA>  ae4 {
IA>      description "LAG 3750-1 VOIP";
IA>      vlan-tagging;
IA>      aggregated-ether-options {
IA>          no-flow-control;
IA>          link-speed 1g;
IA>          lacp {
IA>              active;
IA>          }
IA>      }
IA>      unit 705 {
IA>          vlan-id 705;
IA>          family inet {
IA>              address X.X.0.148/28 {
IA>                  vrrp-group 72 {
IA>                      virtual-address X.X.0.145;
IA>                      priority 2;
IA>                      preempt;
IA>                      accept-data;
IA>                  }
IA>              }
IA>          }
IA>  
IA>  
IA>  I have activated traces on the M320, is anybody able to
IA> understand this Juniper log ? ge-4/1/4 and ge-4/1/5 are the
IA> ports I am trying to bundle. They keep on switching between
IA> the states FAST_PERIODIC and PERIODIC_TX. What's wrong ?
IA>  
IA>  Feb 21 10:43:38 ge-4/1/5: process timer expired on
IA> 0x8144a00 in FAST_PERIODIC state
IA>  Feb 21 10:43:38 lacp_periodic_transmission_machine: begin
IA> 0, lacp enable 1, port 1, actor state 0x47, partner state 0x46
IA>  Feb 21 10:43:38 ge-4/1/5: lacp xmit state transition from FAST_PERIODIC to PERIODIC_TX
IA>  Feb 21 10:43:38 ge-4/1/5: process_periodic_tx_state: need to transmit lacpdu
IA>  Feb 21 10:43:38 Transmitting LACP pdu - interface ge-4/1/5
IA>  Feb 21 10:43:38 lacp subtype 0x1 lacp version number 0x1
IA>  Feb 21 10:43:38 first tlv type 0x1 actor info len 0x14
IA>  Feb 21 10:43:38 actor sys priority 0x7f actor sys 00:14:f6:b8:af:f0
IA>  Feb 21 10:43:38 actor key 0x5 actor port priority 0x7f
IA> actor port 0x30d actor state 0x47
IA>  Feb 21 10:43:38 second tlv type 0x2 partner info len 0x14
IA>  Feb 21 10:43:38 partner sys priority 0x1 partner sys 00:00:00:00:00:00
IA>  Feb 21 10:43:38 partner key 0x5 partner port priority 0x1
IA> partner port 0x30d partner state 0x46
IA>  Feb 21 10:43:38 third tlv type 0x3 collector info len 0x10
IA> collector max del 0x0 fourth tlv type 0x0 terminator len 0
IA>  Feb 21 10:43:38 lacp_periodic_transmission_machine: begin
IA> 0, lacp enable 1, port 1, actor state 0x47, partner state 0x46
IA>  Feb 21 10:43:38 ge-4/1/5: lacp xmit state transition from PERIODIC_TX to FAST_PERIODIC
IA>  Feb 21 10:43:38 lacpd_msg_input: iflidx 138 not found
IA>  Feb 21 10:43:38 ge-4/1/4: process timer expired on
IA> 0x8144600 in FAST_PERIODIC state
IA>  Feb 21 10:43:38 lacp_periodic_transmission_machine: begin
IA> 0, lacp enable 1, port 1, actor state 0x47, partner state 0x46
IA>  Feb 21 10:43:38 ge-4/1/4: lacp xmit state transition from FAST_PERIODIC to PERIODIC_TX
IA>  Feb 21 10:43:38 ge-4/1/4: process_periodic_tx_state: need to transmit lacpdu
IA>  Feb 21 10:43:38 Transmitting LACP pdu - interface ge-4/1/4
IA>  Feb 21 10:43:38 lacp subtype 0x1 lacp version number 0x1
IA>  Feb 21 10:43:38 first tlv type 0x1 actor info len 0x14
IA>  Feb 21 10:43:38 actor sys priority 0x7f actor sys 00:14:f6:b8:af:f0
IA>  Feb 21 10:43:38 actor key 0x5 actor port priority 0x7f
IA> actor port 0x30c actor state 0x47
IA>  Feb 21 10:43:38 second tlv type 0x2 partner info len 0x14
IA>  Feb 21 10:43:38 partner sys priority 0x1 partner sys 00:00:00:00:00:00
IA>  Feb 21 10:43:38 partner key 0x5 partner port priority 0x1
IA> partner port 0x30c partner state 0x46
IA>  Feb 21 10:43:38 third tlv type 0x3 collector info len 0x10
IA> collector max del 0x0 fourth tlv type 0x0 terminator len 0
IA>  Feb 21 10:43:38 lacp_periodic_transmission_machine: begin
IA> 0, lacp enable 1, port 1, actor state 0x47, partner state 0x46
IA>  Feb 21 10:43:38 ge-4/1/4: lacp xmit state transition from PERIODIC_TX to FAST_PERIODIC
IA>  Feb 21 10:43:38 lacpd_msg_input: iflidx 137 not found
IA>  Feb 21 10:43:38 lacpd_msg_input: iflidx 137 not found
IA>  Feb 21 10:43:38 lacpd_msg_input: iflidx 138 not found
IA>  Feb 21 10:43:38 lacpd_msg_input: iflidx 138 not found
IA>  Feb 21 10:43:38 lacpd_msg_input: iflidx 137 not found
IA>  
IA>  Best regards,
IA>  
IA>  Alain Iltchev
IA>  
IA>  _______________________________________________
IA>  juniper-nsp mailing list juniper-nsp at puck.nether.net
IA>  https://puck.nether.net/mailman/listinfo/juniper-nsp
IA>   
IA>   
IA>    
 



More information about the juniper-nsp mailing list