[c-nsp] Port-channel not working Juniper vs Cisco
Saku Ytti
saku at ytti.fi
Sun Jun 11 07:01:22 EDT 2023
Your output says the JNPR side is still fast/1s.
I'd actually prefer to look at the LACP PDU from the wire 'monitor traffic ....'
Flap would be expected if CSCO sends every 30s, JNPR sends every 1s.
We should expect JNPR to be happy about 3s after receiving PDU from
CSCO. I thoroughly recommend setting both ends fast, always. Because
unless all your ports are purely lighted from local optic,the ability
to know if a link carries traffic or not is generally really poor, and
LACP at least will guarantee you won't blackhole longer than 3s when
the link stops carrying traffic for some reason unobservable to you.
On Sun, 11 Jun 2023 at 13:31, james list <jameslist72 at gmail.com> wrote:
>
> Hi
> I've deactivated the FAST on Juniper but nothing changes...
>
> As I wrote on Cisco remains down hence you will not see any LACP while on Juniper it flaps, once I shut on cisco it stop to flap
> I'm not sure it is a cabling issue...
> we should try to setup a pure L3 p2p link and test that I guess...
>
> See the output:
>
> JUNIPER
>
> # run show interfaces diagnostics optics ge-0/2/3
> Physical interface: ge-0/2/3
> Laser bias current : 5.686 mA
> Laser output power : 0.2420 mW / -6.16 dBm
> Module temperature : 39 degrees C / 102 degrees F
> Module voltage : 3.3000 V
> Laser receiver power : 0.2093 mW / -6.79 dBm
> Laser bias current high alarm : Off
> Laser bias current low alarm : Off
> Laser bias current high warning : Off
> Laser bias current low warning : Off
> Laser output power high alarm : Off
> Laser output power low alarm : Off
> Laser output power high warning : Off
> Laser output power low warning : Off
> Module temperature high alarm : Off
> Module temperature low alarm : Off
> Module temperature high warning : Off
> Module temperature low warning : Off
> Module voltage high alarm : Off
> Module voltage low alarm : Off
> Module voltage high warning : Off
> Module voltage low warning : Off
> Laser rx power high alarm : Off
> Laser rx power low alarm : Off
> Laser rx power high warning : Off
> Laser rx power low warning : Off
> Laser bias current high alarm threshold : 12.000 mA
> Laser bias current low alarm threshold : 2.000 mA
> Laser bias current high warning threshold : 10.000 mA
> Laser bias current low warning threshold : 2.000 mA
> Laser output power high alarm threshold : 1.1000 mW / 0.41 dBm
> Laser output power low alarm threshold : 0.0600 mW / -12.22 dBm
> Laser output power high warning threshold : 1.0000 mW / 0.00 dBm
> Laser output power low warning threshold : 0.0850 mW / -10.71 dBm
> Module temperature high alarm threshold : 100 degrees C / 212 degrees F
> Module temperature low alarm threshold : -40 degrees C / -40 degrees F
> Module temperature high warning threshold : 85 degrees C / 185 degrees F
> Module temperature low warning threshold : -10 degrees C / 14 degrees F
> Module voltage high alarm threshold : 3.630 V
> Module voltage low alarm threshold : 2.970 V
> Module voltage high warning threshold : 3.465 V
> Module voltage low warning threshold : 3.134 V
> Laser rx power high alarm threshold : 1.8000 mW / 2.55 dBm
> Laser rx power low alarm threshold : 0.0000 mW / - Inf dBm
> Laser rx power high warning threshold : 1.0000 mW / 0.00 dBm
> Laser rx power low warning threshold : 0.0200 mW / -16.99 dBm
>
>
>
> # run show lacp statistics interfaces ae10
> Aggregated interface: ae10
> LACP Statistics: LACP Rx LACP Tx Unknown Rx Illegal Rx
> ge-0/2/3 0 233 0 0
>
>
> # run show lacp interfaces ae10 extensive
> Aggregated interface: ae10
> LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
> ge-0/2/3 Actor No Yes No No No Yes Fast Active
> ge-0/2/3 Partner No Yes No No No Yes Fast Passive
> LACP protocol: Receive State Transmit State Mux State
> ge-0/2/3 Defaulted Fast periodic Detached
> LACP info: Role System System Port Port Port
> priority identifier priority number key
> ge-0/2/3 Actor 127 f8:c1:16:56:0a:00 127 7 11
> ge-0/2/3 Partner 1 00:00:00:00:00:00 1 7 11
>
> Jun 11 12:18:09.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 745, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3
> Jun 11 12:18:09.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 585, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3.0
> Jun 11 12:18:14.221 2023 mib2d[9005]: SNMP_TRAP_LINK_DOWN: ifIndex 745, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-0/2/3
> Jun 11 12:18:15.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 745, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3
> Jun 11 12:18:15.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 585, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3.0
> Jun 11 12:18:19.721 2023 mib2d[9005]: SNMP_TRAP_LINK_DOWN: ifIndex 745, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-0/2/3
> Jun 11 12:18:20.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 745, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3
> Jun 11 12:18:20.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 585, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3.0
> Jun 11 12:18:25.221 2023 mib2d[9005]: SNMP_TRAP_LINK_DOWN: ifIndex 745, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-0/2/3
> Jun 11 12:18:26.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 745, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3
> Jun 11 12:18:26.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 585, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3.0
> Jun 11 12:18:31.221 2023 mib2d[9005]: SNMP_TRAP_LINK_DOWN: ifIndex 745, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-0/2/3
> Jun 11 12:18:32.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 745, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3
> Jun 11 12:18:32.621 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 585, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3.0
> Jun 11 12:18:36.721 2023 mib2d[9005]: SNMP_TRAP_LINK_DOWN: ifIndex 745, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-0/2/3
> Jun 11 12:18:37.721 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 745, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3
> Jun 11 12:18:37.721 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 585, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3.0
> Jun 11 12:18:42.221 2023 mib2d[9005]: SNMP_TRAP_LINK_DOWN: ifIndex 745, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-0/2/3
> Jun 11 12:18:42.721 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 745, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3
> Jun 11 12:18:42.721 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 585, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3.0
> Jun 11 12:18:47.721 2023 mib2d[9005]: SNMP_TRAP_LINK_DOWN: ifIndex 745, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-0/2/3
> Jun 11 12:18:48.721 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 745, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3
> Jun 11 12:18:48.721 2023 mib2d[9005]: SNMP_TRAP_LINK_UP: ifIndex 585, ifAdminStatus up(1), ifOperStatus up(1), ifName ge-0/2/3.0
> Jun 11 12:18:53.221 2023 mib2d[9005]: SNMP_TRAP_LINK_DOWN: ifIndex 745, ifAdminStatus up(1), ifOperStatus down(2), ifName ge-0/2/3
>
> CISCO
>
> #sh int eth1/41 transceiver calibrations
> Ethernet1/41
> transceiver is present
> type is 1000base-SX
> name is CISCO-FINISAR
> part number is FTLF8519P2BCL-CS
> revision is 0000
> serial number is FNS11150LN8
> nominal bitrate is 1300 MBit/sec
> cisco id is 3
> cisco extended id number is 4
> cisco part number is 30-1301-02
>
> SFP is internally calibrated
>
>
>
> # sh int eth1/41
> Ethernet1/41 is down (Link not connected)
> admin state is up, Dedicated Interface
> Belongs to Po41
> Hardware: 100/1000/10000/25000 Ethernet, address: 502f.a8ea.bbb0 (bia 502f.a8ea.bbb0)
> Description: <[To EX4400]>
> MTU 1500 bytes, BW 25000000 Kbit, DLY 10 usec
> reliability 255/255, txload 1/255, rxload 1/255
> Encapsulation ARPA, medium is broadcast
> Port mode is trunk
> auto-duplex, auto-speed, media type is 1G
> Beacon is turned off
> Auto-Negotiation is turned on FEC mode is Auto
> Input flow-control is off, output flow-control is off
> Auto-mdix is turned off
> Rate mode is dedicated
> Switchport monitor is off
> EtherType is 0x8100
> EEE (efficient-ethernet) : n/a
> Last link flapped never
> Last clearing of "show interface" counters 3d20h
> 0 interface resets
> Load-Interval #1: 30 seconds
> 30 seconds input rate 0 bits/sec, 0 packets/sec
> 30 seconds output rate 0 bits/sec, 0 packets/sec
> input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
> Load-Interval #2: 5 minute (300 seconds)
> 300 seconds input rate 0 bits/sec, 0 packets/sec
> 300 seconds output rate 0 bits/sec, 0 packets/sec
> input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
> RX
> 0 unicast packets 0 multicast packets 0 broadcast packets
> 0 input packets 0 bytes
> 0 jumbo packets 0 storm suppression bytes
> 0 runts 0 giants 0 CRC 0 no buffer
> 0 input error 0 short frame 0 overrun 0 underrun 0 ignored
> 0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
> 0 input with dribble 0 input discard
> 0 Rx pause
> TX
> 0 unicast packets 0 multicast packets 0 broadcast packets
> 0 output packets 0 bytes
> 0 jumbo packets
> 0 output error 0 collision 0 deferred 0 late collision
> 0 lost carrier 0 no carrier 0 babble 0 output discard
> 0 Tx pause
>
>
> Il giorno dom 11 giu 2023 alle ore 09:59 Saku Ytti <saku at ytti.fi> ha scritto:
>>
>> You've changed JNPR from 30s to 1s, but not CSCO. I'm not sure if this
>> is the only problem, as insufficient data is shown about the state and
>> LACP PDUs.
>>
>> I believe the command is 'lacp rate fast' or 'lacp period short', to
>> reduce risk of operators getting bored, In your case, the former.
>>
>> On Sun, 11 Jun 2023 at 10:38, james list via cisco-nsp
>> <cisco-nsp at puck.nether.net> wrote:
>> >
>> > Dear expert
>> > we've an issue in setting up a port-channel between a Juniper EX4400 and a
>> > Cisco Nexus N9K-C93180YC-EX over an SX 1 Gbs link.
>> >
>> > We've implemented the following configuration but on Juniper side it is
>> > interface flapping while on Cisco side it remains down.
>> > Light levels seem ok.
>> >
>> > Has anyone ever experienced the same ? Any suggestions ?
>> >
>> > Thanks in advance for any hint
>> > Kind regards
>> > James
>> >
>> > JUNIPER *****************************
>> >
>> > > show configuration interfaces ae10 | display set
>> > set interfaces ae10 description "to Cisco leaf"
>> > set interfaces ae10 aggregated-ether-options lacp active
>> > set interfaces ae10 aggregated-ether-options lacp periodic fast
>> > set interfaces ae10 unit 0 family ethernet-switching interface-mode trunk
>> > set interfaces ae10 unit 0 family ethernet-switching vlan members 301
>> >
>> > > show configuration interfaces ge-0/2/3 | display set
>> > set interfaces ge-0/2/3 description "to Cisco leaf"
>> > set interfaces ge-0/2/3 ether-options 802.3ad ae10
>> >
>> > > show vlans VLAN_301
>> >
>> > Routing instance VLAN name Tag Interfaces
>> > default-switch VLAN_301 301
>> > ae10.0
>> >
>> >
>> >
>> >
>> > CISCO *******************************
>> >
>> > interface Ethernet1/41
>> > description <[To EX4400]>
>> > switchport
>> > switchport mode trunk
>> > switchport trunk allowed vlan 301
>> > channel-group 41 mode active
>> > no shutdown
>> >
>> > interface port-channel41
>> > description <[To EX4400]>
>> > switchport
>> > switchport mode trunk
>> > switchport trunk allowed vlan 301
>> >
>> >
>> > # sh vlan id 301
>> >
>> > VLAN Name Status Ports
>> > ---- -------------------------------- ---------
>> > -------------------------------
>> > 301 P2P_xxx active Po1, Po41, Eth1/1, Eth1/41
>> >
>> > VLAN Type Vlan-mode
>> > ---- ----- ----------
>> > 301 enet CE
>> >
>> > Remote SPAN VLAN
>> > ----------------
>> > Disabled
>> >
>> > Primary Secondary Type Ports
>> > ------- --------- ---------------
>> > -------------------------------------------
>> > _______________________________________________
>> > cisco-nsp mailing list cisco-nsp at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/cisco-nsp
>> > archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>>
>>
>> --
>> ++ytti
--
++ytti
More information about the cisco-nsp
mailing list