ExtremeSwitching (EXOS)

Expand all | Collapse all

problem with EAPS with shared port down involved

  • 1.  problem with EAPS with shared port down involved

    Posted 09-20-2017 20:35
    Hi all, We have had a problem with EAPS that has caused a high level CPU of the switches an the increase of traffic through the rings. A continuation I show the picture of the EAPS.



    External plant had a maintenance which involved that the links in red (the shared port )got down, after two or three hours the link between SJL -LN got up and the problem started, the cpu increase and the traffic also.



    These are the logs (SBJExtr had 30 minutes more):

    LN_Extreme.59 # show log 09/20/2017 02:04:03.63 EAPSD FLX_EAPS_MirSjlLnSbj - 49 state transition from Up => Down
    09/20/2017 02:04:03.63 EAPS Shared-port 50 - Segment-port 49 state transition from Up => Down
    09/20/2017 02:04:03.62 Remove port 49 from aggregator
    09/20/2017 02:04:03.62 Port 49 is Down, remove from aggregator 49
    09/20/2017 02:04:03.62 Port 49 link down - Local fault
    09/20/2017 01:44:10.04 Login passed for user admin through telnet (181.224.229.4)
    09/20/2017 01:34:41.09 EAPS Shared-port 50 - Not processing Link-Down-Pdu, because linkId 11 matches our own
    09/20/2017 01:34:41.09 EAPSD FLX_EAPS_MirSjlLnSbj - Received Link-Down-Pdu (MAC = 00:04:96:99:83:24)
    09/20/2017 01:34:41.09 EAPSD FLX_EAPS_MirSjlLnSbj - Received RingDown-FlushFdb-Pdu (MAC = 00:04:96:99:9E:3E)
    09/20/2017 01:34:41.07 EAPSD FLX_EAPS_MirSjlLnSbj - Link-Down State unchanged
    09/20/2017 01:34:41.07 EAPSD FLX_EAPS_MirSjlLnSbj - 49 state transition from Down => Up
    09/20/2017 01:34:41.06 EAPS Shared-port 50 - Segment-port 49 state transition from Down => Up
    09/20/2017 01:34:41.06 Add port 49 to aggregator
    09/20/2017 01:34:38.91 Port 49 link UP at speed 10 Gbps and full-duplex

    SBJ-EXT_AGREG.10 # show log
    09/20/2017 02:46:49.51 SNMP access from source 209.126.136.2 is denied by rule telnet_in. Dropping this Request.
    09/20/2017 02:32:39.34 EAPS Shared-port 2 - Processing Link-Down-Pdu on segment-port 5
    09/20/2017 02:32:39.34 EAPS Shared-port 5 - Segment-port 2 state transition from Up => Down
    09/20/2017 02:32:39.34 EAPS Shared-port 5 - Processing Link-Down-Pdu on segment-port 2
    09/20/2017 02:32:39.34 EAPSD FLX_EAPS_MirSjlLnSbj - Received Link-Down-Pdu (MAC = 00:04:96:99:9E:3E)
    09/20/2017 02:03:17.58 EAPS Shared-port 5 - Segment-port 2 state transition from Down => Up
    09/20/2017 02:03:16.79 EAPS Shared-port 2 - Processing Link-Down-Pdu on segment-port 5
    09/20/2017 02:03:16.79 EAPSD FLX_EAPS_MirSjlLnSbj - Received Link-Down-Pdu (MAC = 00:04:96:99:9E:40)
    09/20/2017 02:03:16.77 EAPSD FLX_EAPS_MirSjlLnSbj - Received RingDown-FlushFdb-Pdu (MAC = 00:04:96:99:9E:3E)

    And the state of the eaps in the nodes LN and SJL are the next one.

    LN_Extreme.75 # show eaps

    EAPS Enabled: Yes
    EAPS Fast-Convergence: Off
    EAPS Display Config Warnings: Off
    EAPS Multicast Add Ring Ports: Off
    EAPS Multicast Send IGMP and MLD Query: On
    EAPS Multicast Temporary Flooding: Off
    EAPS Multicast Temporary Flooding Duration: 15 sec
    Number of EAPS instances: 2
    # EAPS domain configuration :
    ----------------------------------------------------------------------------------
    Domain State Mo En Pri Sec Control-Vlan VID Count Prio
    ----------------------------------------------------------------------------------
    FLX_EAPS_SbLnSmi Links-Down T Y 51 50 FLX_CONTROL_SbLnSMi (701 ) 132 N
    FLX_EAPS_MirSjlLnSbj Links-Down T Y 49 50 FLX_control_MirSJLLNSBJ (412 ) 96 N
    ----------------------------------------------------------------------------------
    Flags : (!) CFM Down
    LN_Extreme.76 #

    LN_Extreme.76 # show eaps shared-port

    EAPS shared-port count: 1
    --------------------------------------------------------------------------------
    Link Domain Vlan RB RB
    Shared-port Mode Id Up State count count Nbr State Id
    --------------------------------------------------------------------------------
    50 Controller 11 Y Blocking 2 176 Yes None None

    --------------------------------------------------------------------------------
    LN_Extreme.77 #

    SBJ-EXT_AGREG.13 # show eaps shared-port

    EAPS shared-port count: 2
    --------------------------------------------------------------------------------
    Link Domain Vlan RB RB
    Shared-port Mode Id Up State count count Nbr State Id
    --------------------------------------------------------------------------------
    2 Partner 10 Y Ready 3 442 Yes None None

    5 Partner 11 Y Blocking 2 177 Yes None None

    --------------------------------------------------------------------------------
    SBJ-EXT_AGREG.14 #
    SBJ-EXT_AGREG.14 #
    SBJ-EXT_AGREG.14 # show eaps

    EAPS Enabled: Yes
    EAPS Fast-Convergence: Off
    EAPS Display Config Warnings: On
    EAPS Multicast Add Ring Ports: Off
    EAPS Multicast Send IGMP and MLD Query: On
    EAPS Multicast Temporary Flooding: Off
    EAPS Multicast Temporary Flooding Duration: 15 sec
    Number of EAPS instances: 4
    # EAPS domain configuration :
    ----------------------------------------------------------------------------------
    Domain State Mo En Pri Sec Control-Vlan VID Count Prio
    ----------------------------------------------------------------------------------
    FLX_EAPS-MiSaV Links-Up T Y 6 2 FLX_CONTROL_MiSaV (7 ) 274 N
    FLX_EAPS-MiSaLi Links-Up T Y 4 2 FLX_Control_Mir-SBJ-Lin (413 ) 129 N
    FLX_EAPS_SbLnSmi Links-Down T Y 5 10 FLX_Control_SbLnSMi (701 ) 132 N
    FLX_EAPS_MirSjlLnSbj Links-Down T Y 5 2 FLX_control_MirSJLLNSBJ (412 ) 96 N
    ----------------------------------------------------------------------------------
    Flags : (!) CFM Down
    SBJ-EXT_AGREG.15 #


  • 2.  RE: problem with EAPS with shared port down involved

    Posted 09-20-2017 20:46
    The firmware versions are:
    SBJExtr: Secondary ver: 16.1.3.6 patch1-9
    LNEXtr: Secondary ver: 21.1.3.7


  • 3.  RE: problem with EAPS with shared port down involved

    Posted 10-03-2017 17:51
    I realized that the problem was because of a vlan that was not configured completely in the rings.


  • 4.  RE: problem with EAPS with shared port down involved

    Posted 10-04-2017 01:56
    Earroyo,

    Glad you were able to identify the issue.

    We could always check our EAPS configuration using the command "debug eaps check config" as this would let us know if there are any configuration part missing in the EAPS.