JN0-351 High Availability

High Availability Detailed Explanation

High Availability (HA) refers to a network's ability to maintain uninterrupted operations even in the event of hardware failures, link disruptions, or software updates. HA mechanisms are crucial for ensuring reliability and minimizing downtime in modern networks.

1. Basic Concepts

What is High Availability?

• Purpose: To provide redundancy and fault tolerance in network infrastructure.
• Core Goals:
  • Minimize service disruptions caused by hardware or software issues.
  • Ensure seamless failover to backup systems during failures.
  • Support updates and maintenance without service interruption.

Key Features of HA:

• Redundancy: Duplicate critical components to ensure availability.
• Load Balancing: Distribute traffic to optimize resource utilization.
• Failover: Automatically switch to backup systems in case of failure.

2. Detailed Knowledge

Link Aggregation Group (LAG)

What is LAG?

• LAG (Link Aggregation Group) combines multiple physical links into a single logical link to:
  • Increase bandwidth.
  • Provide redundancy.
  • Distribute traffic across multiple links.

Key Characteristics:

• If one link in the group fails, traffic is redistributed to the remaining active links.
• Supported by protocols like LACP (Link Aggregation Control Protocol) to dynamically manage aggregated links.

Use Cases:

• Connecting switches or routers to handle high-bandwidth traffic.
• Ensuring resilience for critical connections.

Redundant Trunk Group (RTG)

What is RTG?

• RTG (Redundant Trunk Group) provides failover capabilities for trunk interfaces.
• It ensures that if a primary interface fails, traffic switches to the backup interface automatically.

Key Characteristics:

• Unlike LAG, only one link in the trunk is active at a time.
• The backup link becomes active only if the primary fails.

Use Cases:

• Simple, cost-effective redundancy for links that do not require load balancing.

Virtual Chassis

What is Virtual Chassis?

• Virtual Chassis technology combines multiple physical switches into a single logical device.
• All switches in the chassis operate as one unit, sharing a control plane and behaving as a single entity.

Key Characteristics:

• Simplifies management by reducing the need for separate configurations for each switch.
• Ensures high availability by allowing traffic to reroute within the virtual chassis if one member fails.

Use Cases:

• Deploying in data centers or large campus networks for simplified management and enhanced fault tolerance.

Non-Stop Routing (NSR)

What is NSR?

• Non-Stop Routing (NSR) ensures that routing protocol sessions remain active even during control plane failovers.

Key Characteristics:

• Keeps routing protocol states synchronized between primary and backup control planes.
• Avoids the need to reestablish neighbor relationships during failover.

Supported Protocols:

• OSPF, BGP, IS-IS, and others.

Use Cases:

• Critical environments where reestablishing routing sessions would cause unacceptable downtime.

In-Service Software Upgrade (ISSU)

What is ISSU?

• ISSU (In-Service Software Upgrade) allows network devices to upgrade their software without interrupting ongoing services.

Key Characteristics:

• Achieved by using redundant control and forwarding planes.
• Ensures continuous packet forwarding during the upgrade process.

Use Cases:

• Minimizing downtime during maintenance in high-availability environments.
• Ensuring seamless upgrades in service provider or enterprise networks.

3. Key Takeaways

• LAG: Combines multiple links for increased bandwidth and redundancy.
• RTG: Provides failover for trunk interfaces without load balancing.
• Virtual Chassis: Virtualizes multiple switches into one logical device for simplified management and resilience.
• NSR: Maintains routing protocol states during failovers, avoiding service disruptions.
• ISSU: Enables seamless software upgrades without downtime.

High Availability (Additional Content)

1. NSR vs Graceful Restart (GR)

Both Non-Stop Routing (NSR) and Graceful Restart (GR) aim to maintain routing stability during control plane failures or restarts. However, they differ fundamentally in how they function and what dependencies they have.

Feature	NSR	Graceful Restart (GR)
Peer cooperation required?	No	Yes – peer must support GR
Neighbor session reset?	No – sessions are preserved	Yes – sessions reset but retain state
Visibility to peer?	Transparent (peers unaware of switchover)	Peer must detect and cooperate
Juniper recommended use case	Internal HA (between REs on same device)	Interoperability with external routers

NSR is internal and transparent to peers; GR requires peer cooperation and is used when NSR is unavailable.

Exam Tip:
If a question asks:

“Which mechanism requires peer support and maintains routing information during control plane reboot?”
The answer is: Graceful Restart (GR)

2. LAG vs RTG – Use Case and Design Considerations

Link Aggregation Group (LAG) and Redundant Trunk Group (RTG) both offer redundancy but are designed for different purposes.

• LAG provides load balancing and bandwidth aggregation across multiple active links.

• RTG offers simple failover where only one link is active at a time.

RTG is used where bandwidth aggregation is not required, and simplicity or hardware constraints favor active/backup topology.

Example Use Cases:

Use Case	Preferred Method
Connect two switches with multiple links	LAG
Connect to a device that only supports one uplink	RTG
Require load balancing and higher throughput	LAG
Only need backup path for failover	RTG

Exam Tip:
You may be asked:

“When is RTG more appropriate than LAG?”
Correct answer: When load balancing is not needed and simplicity is preferred.

3. ISSU – Conditions for Support and Operation

In-Service Software Upgrade (ISSU) allows a Juniper device to upgrade its OS without dropping control or data plane traffic. However, ISSU is not universally supported and depends on specific platform and configuration criteria.

Required Conditions:

• Device must support redundant Routing Engines (REs)

• NSR must be enabled to preserve protocol sessions

• Only certain platforms (e.g., MX, QFX) support ISSU

• Must use non-disruptive protocols (e.g., OSPF, IS-IS with NSR)

For ISSU to work, the system must support NSR and have redundant REs (Routing Engines) in place.

Exam Tip:
A question might ask what causes an ISSU to fail. One valid answer could be: NSR is not configured.

4. Virtual Chassis – Master Election Logic

In a Virtual Chassis, multiple physical switches operate as a single logical switch. One of the member switches becomes the master, responsible for managing the control and configuration plane of the entire chassis.

One switch becomes the master in a Virtual Chassis, determined by configured priority or MAC address as a tie-breaker.

Master Election Criteria:

1. Manually configured priority (higher wins)

2. If priorities are equal, the switch with the highest MAC address becomes master

Exam Tip:
You may be shown a VC configuration with two members and asked which becomes the master. Focus on the priority value first.

Summary – High Availability Concepts for JN0-351 Success

Feature	Exam-Relevant Insight
NSR vs GR	NSR = local and transparent; GR = external peer cooperation required
LAG vs RTG	LAG = aggregation + load balancing; RTG = active/passive simplicity
ISSU Support	Requires NSR and dual REs; limited to supported platforms (e.g., MX, QFX)
Virtual Chassis Master	Determined by priority, then MAC address; only one master at a time