Juniper MX routing-engine failover configuration

-


Having recently worked on a project that incorporated this functionality, here is a sample configuration for Juniper MX routing engine failover:


Configuration


{master}

tema@mx-router> show configuration | find redundancy
    redundancy {
        routing-engine 0 master;
        routing-engine 1 backup;
        graceful-switchover {
            apply-groups [ re0 re1 ];
        }
    }
    routing-engine {
        on-disk-failure disk-failure-action reboot;
    }
    fpc 1 {
        pic 0 {
            max-queues-per-interface 8;
        }
        pic 1 {
            max-queues-per-interface 8;
        }
    }
}

{backup}

tema@mx-router> show configuration | find redundancy
    redundancy {
        routing-engine 0 master;
        routing-engine 1 backup;
        graceful-switchover {
            apply-groups [ re0 re1 ];
        }
    }
    routing-engine {
        on-disk-failure disk-failure-action reboot;
    }
    fpc 1 {
        pic 0 {
            max-queues-per-interface 8;
        }
        pic 1 {
            max-queues-per-interface 8;
        }
    }
}

1. To switch manual switch from master to backup, RE0(Master-slot0) to RE1(Backup-slot1)
From the console on RE0(master):

tema@mx-router> request chassis routing-engine master switch

2. Force to synchronize between RE0 and RE1

tema@mx-router# commit synchronize


3. Status of routing-engine redundancy

tema@mx-router> show chassis routing-engine

Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 40 degrees C / 82 degrees F
DRAM 2048 MB
Memory utilization 14 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 3 percent
Interrupt 0 percent
Idle 97 percent
Model RE-3.0
Serial ID Pxxxxxxx
Start time 2016-04-15 18:45:12 UTC
Uptime 36 days, 3 hours, 56 minutes, 8 seconds
Routing Engine status:
Slot 1:
Current state Backup
Election priority Backup (default)
Temperature 27 degrees C / 78 degrees F
DRAM 2048 MB
Memory utilization 10 percent
CPU utilization:
[...deleted...]


4. Successive routing-engine switchovers must be a minimum of 240 seconds (4 minutes) apart after both routing-engines have come up. So, once RE1 has become master, allow 4 minutes before switching back to RE0 as master.

5. To verify that Graceful RE Switchover is enabled, on the backup Routing Engine, issue the show system switchover command:

tema@mx-router> show system switchover
Graceful switchover: On
Configuration database: Ready
Kernel database: Ready
Peer state: Steady state

Comments

Post a Comment

Popular posts from this blog

Why Datacentre Operators Are Prioritising Regions with Lower Energy Costs Over Traditional Locations

-
Image
Introduction Data centres have become the backbone of the digital economy, supporting everything from cloud computing to artificial intelligence and e-commerce. However, their enormous energy consumption presents a significant challenge for operators , especially as sustainability and cost-efficiency become critical concerns. Traditionally, data centres were built in regions with established infrastructure and access to major markets. However, a growing trend sees operators shifting to locations with lower energy costs , often at the expense of traditional business hubs. This analysis explores the key drivers behind this shift and its implications for the industry. The Impact of Energy Costs on Datacentre Operations The High Energy Demand of Data Centres Data centres consume vast amounts of electricity, primarily for powering servers and cooling systems. Estimates suggest that global data centres use approximately 1-2% of the world’s electricity, with some hyperscale facilities consumi...
Read more

Data Sovereignty and AI

-
Image
I have recently been speaking to customers who have concerns with using AI and large language models (LLM) within a specific geographic area. As always, reading up on this stuff, these are my notes - trying not to make it a complete word-salad: The Labyrinth of Sovereignty Navigating the Challenges of AI in a Data-Defined World The rise of artificial intelligence (AI) has ushered in an era of unprecedented potential, transforming industries and reshaping the very fabric of our lives. However, this technological revolution is unfolding against a complex backdrop of evolving data privacy regulations and a growing emphasis on data sovereignty. For enterprises seeking to harness the power of AI, navigating this intricate landscape presents a formidable challenge.  Data sovereignty, at its core, is the principle that data is subject to the laws and regulations of the jurisdiction in which it is collected or processed. This concept, while seemingly straightforward, becomes incredibly nu...
Read more

The Rise of the 25GE interface ?

-
Image
Remember the good old days of dial-up? The screeching modem, the agonising wait for a single webpage to load? Okay, maybe some of you don’t, and that’s probably a good thing for your sanity. But the point is, our need for speed online has exploded faster than a cat startled by a cucumber. And while 10 Gigabit Ethernet (10GE) was once the king of the hill, a new contender has emerged, promising more oomph without breaking the bank (or requiring you to sell a kidney for the privilege): 25 Gigabit Ethernet (25GE) . So, why is 25GE suddenly the cool kid on the block in both Wide Area Networks (WANs) and the bustling datacentre? Let’s dive in with a bit of humour and some real-world examples. The Insatiable Appetite for Bandwidth: It's Not Just for Streaming Netflix Anymore Whether it's across the vast expanse of the WAN or within the tightly packed racks of a datacentre, the demand for bandwidth is like a teenager’s appetite – seemingly endless. In the WAN:  Enterprise orgs ar...
Read more