This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.

Replacing Linux/Quagga routers with Juniper MX204

  • 1.  Replacing Linux/Quagga routers with Juniper MX204

    Posted 08-31-2021 05:48


    I have a task to replace all Linux/Quagga routers with Juniper MX204.

    Description of the existing solution:

    Customers <-> Quagga Routers <-OSPF-> Juniper MX204 <-> External BGP Peers

    We have 2 Juniper MX204s, which are connected via BGP to external BGP Peers.
    Some of our clients (> 2000) are connected to Quagga routers and they have a static global IP address.
    Quagga routers are gateways for customers networks (/ 30, / 29 ...).
    For example:
    interface eth0.555
     description of Customers_OfficeCentre1
     IP address / 30
     IP address / 30
     IP address / 30
     IP address / 30
    interface eth0.566
     Description of Customers_OfficeCentre2
     IP address / 30
     IP address / 30
     IP address / 30
     IP address / 30

    Also on these Linux / Quagga routers the 'tc htb' traffic shaper works.
    We have all the mechanisms (scripts) to automatically add / remove networks and configure traffic shaper (bandwidth).

    We want to completely abandon Quagga and switch customers to Juniper:

    In this regard, I had several questions:

    1. How can you automate the process of migrating a large number of networks?

    I am also interested in the possibility of managing these networks:

        1.automatic addition of new networks

        2.deleting networks


    2. How to limit the bandwidth for each client individually (for each subnet)?

    3. A customer can have multiple subnets and we need to configure one common traffic shape (bandwith) for them. 

    4. It is necessary to be able to classify traffic by destination.

    For example:

    - World
    - Google (we have BGP peering with them)
    - Traffic exchange points
    be able to limit bandwidth based on destination.

    Now we classify destinations using BGP community and realms.

    5. Is it possible, if a failure occurs on one of the Junipers, to raise its configuration on the second? How to do it?

    I understand that the answers to my questions will be very voluminous, but I am not asking for a ready-made solution (but I will not refuse :)).
    Please tell me which way to look, what to look for and, if possible, your recommendations on how to do it better.