Scribd Logo
Upload

Welcome to Scribd!

  • 332 views

    241 - Ceragon - LAG CONFIG - Presentation v1.0

    Uploaded by

    mehdi_mehdi
    241 CERAGON

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd

    241 - Ceragon - LAG CONFIG - Presentation v1.0

    Uploaded by

    mehdi_mehdi
    332 views17 pages
    241 CERAGON

    Copyright

    © © All Rights Reserved

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    241 CERAGON

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    332 views17 pages

    241 - Ceragon - LAG CONFIG - Presentation v1.0

    Uploaded by

    mehdi_mehdi
    241 CERAGON

    Copyright:

    © All Rights Reserved
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 17
    At a glance
    Powered by AI
    The key takeaways are about configuring and analyzing Link Aggregation Groups (LAGs) in network switches, including guidelines for creating and managing LAGs, port requirements, and using RMON to monitor traffic distribution.

    Ports can be grouped into LAGs as long as they are in the same switch, have the same settings, and follow guidelines such as only traffic ports can be in a LAG and ports of different types cannot be combined. A LAG can contain between 1-5 ports.

    The settings that must be identical across ports in a LAG include QoS configuration, speed, type, interface settings, duplex mode, auto-negotiation, VLANs, and learning state. VLAN lists specifically must be an exact match.

    Link Aggregation Group Configuration

    (IEEE 802.3ad)

    Proprietary and Confidential

    Agenda
    Agenda

    Proprietary and Confidential

    Static LAG guidelines


    1. Only traffic ports (including radio port) can belong to a LAG
    2. Management ports / WSC ports cannot be grouped in a LAG
    3. LAG is supported in IDUs configured as Managed or Metro switch
    4. LAG is not supported in a Single Pipe mode
    5. All ports in a LAG must be in the same IDU (same switch)
    6. There may be up to 3 LAGs per IDU
    7. A LAG may contain from 1 to 5 physical ports

    Proprietary and Confidential

    Static LAG guidelines (continued)


    8. LAGs are virtual ports that do not permanently exist in the system
    9. When a LAG is created, it will automatically inherit all the ports
    characteristics, except for the following:

    xSTP role (edge, non-edge)


    path cost
    10. The LAG will initially receive default values for these parameters
    11. Dynamic Link Aggregation (LACP) is not supported

    Proprietary and Confidential

    Grouping ports in LAG


    Ports 1-2 (GBE ports) and ports 3-7 (FE only ports) cannot be in the same LAG
    group even if the GBE ports are configured as 100Mbps.

    GbE
    1

    FE
    3

    GbE
    6

    FE
    3

    IP-10 IDU

    t
    No
    5

    sib
    a
    e
    f

    8
    IP-10 IDU

    le

    OK
    Proprietary and Confidential

    Grouping ports in LAG (continued)


    Radio port (port 8) may be in a LAG with the GBE ports only

    GbE
    1

    FE
    3

    GbE
    6

    FE
    3

    IP-10 IDU

    t
    No
    6

    sib
    a
    e
    f

    8
    IP-10 IDU

    le

    OK

    Proprietary and Confidential

    Configuring LAG
    The following settings must be identical on all LAG ports
    (Port(s) with different settings will not be added to the LAG)

    QoS configuration (Classification Criteria, Port ReMap table, Egress Scheduler)


    Speed (data rate)
    Type (access/trunk or CN/PN)
    interface (electrical/optical)
    Full Duplex
    Auto-Negotiation
    VLANs
    VLAN list must be identical
    allow all is considered a different value (must be equal in all ports)
    Port Learning State
    Please note - ports with CFM MEP/MIPs will not be added to a LAG (which
    may have its own MEP/MIPs).

    Proprietary and Confidential

    Configuring LAG (continued)


    The following parameters CANNOT be configured on ports that are already
    grouped in a LAG:

    Admin status
    Flow control
    Ingress rate limiting Policer name
    Shaper (egress rate limiting)
    Peer port parameters
    MAC address
    IP address
    Slot ID
    Port number
    Description
    :

    Proprietary and Confidential

    Removing a Port from LAG


    Ports removed from a LAG will keep the existing port parameters, but will
    be initially disabled in order to prevent loops.

    In addition, when the last port is removed from a LAG, the LAG will be
    deleted.

    Therefore it is necessary to remove all MEP/MIPs from a LAG before


    removing the last port.

    Proprietary and Confidential

    EMS Configuration

    Setting Load Balance Policy


    Open page:
    Configuration / Ethernet Switch
    Select Simple XOR or HASH
    Create VLAN(s) per service(s) in
    the switch DB (if such VID do not
    exist yet)

    11

    Proprietary and Confidential

    Selecting ports to LAG


    Open page: Configuration / Interfaces / Ethernet Ports
    Click on LAG Configuration and select the LAG ports and group ID

    Available ports highlight in blue when selected


    Non-available ports (part of an existing LAG) are not configurable

    12

    Proprietary and Confidential

    Example
    1.
    2.
    3.
    4.
    5.
    6.

    We generate a data stream through GbE SFP port 1 of both lower IDUs
    Port 2 & 8 form a LAG on both sites
    Upper IDUs are set as Pipe
    Traffic will be evenly distributed among the radio ports
    Assign Radio license > Line rate
    Clear all PM data
    50
    %
    1

    50
    %

    Data stream
    Proprietary and Confidential

    Data stream

    Using RMON (PM) to analyze LAG


    Make note of received &
    transmitted traffic through port 1
    Please note:
    Slight differences may appear
    since EMS is a web based
    application and data is
    accumulating

    Data stream
    Proprietary and Confidential

    Using RMON (PM) to analyze LAG


    Check the received & sent
    registers of port 1 and LAG
    ports:
    Data received on Port 1 is
    equally distributed through
    Port 2 and Port 8

    Proprietary and Confidential

    Using RMON (PM) to analyze LAG


    Disconnect the ETH cable
    connecting lower IDU to
    upper IDU (port 2)
    LAG port 2 does not
    transmit data now
    Port 8 takes 100% of data
    transmission

    Proprietary and Confidential

    Thank You !
    [email protected]

    17

    Proprietary and Confidential

    You might also like