Country

- China
- France
- Germany
- Japan
- Korea
- Spain
- Taiwan
- United Kingdom
- United States

Contact Us
|
Country
United States

# Technical Documentation

- Download Software
- Research a Problem
- Case Management
- Contract & Product Management
- Technical Documentation
  - Advanced Search
  - Documentation Archive
  - Documentation Bug Report
  - Enterprise MIBs
  - File Format Help
  - Glossary
  - Portable Libraries
- End-of-Life Products
- Contact Support
- Guidelines and Policies
- Security Resources

- Related Topics
- ICR Scaling Considerations
- Configuring an ICR Partition

# ICR Overview

A broadband services router (BSR) aggregates many subscribers and services such as video on demand (VoD), voice over IP (VoIP), Internet Protocol television (IPTV), and the Internet, simultaneously. If the router fails because of hardware failures, subscriber downtime can result.

Interchassis redundancy (ICR) enables you to minimize subscriber downtime when the router or access interface on the edge router fails. ICR accomplishes this by re-creating subscriber sessions on the backup router that were originally terminated on the failed router. In this way, ICR enables you to completely recover from router failure. ICR uses Virtual Router Redundancy Protocol (VRRP) to detect failures. ICR also enables you to track the failure of uplink interfaces. ICR currently supports only PPPoE subscribers.

Figure 1 illustrates ICR deployment.

Figure 1: ICR Deployment

The subscriber broadcasts a PPPoE Active Discovery Initiation (PADI) packet to both the master and backup router. Only the master router processes the packet and creates the subscriber session. When the master router fails, VRRP switchover occurs and the backup router becomes the new master router. When receiving traffic for non-existent PPPoE sessions, the new master router sends early termination requests by sending PPPoE Active Discovery Termination (PADT) packets to the clients instead of waiting for the client to reconnect after the PPPoE session expires. The clients respond by sending requests to log in again. Then, the new master router creates new sessions for the PPPoE subscribers.

In lower-numbered releases, the new master router dropped the PPPoE packets because a session did not exist for the PPPoE subscribers and did not send PADT packets.

ICR achieves load balancing in case of failures on a per physical port basis by enabling you to create partitions. An ICR partition is a set of S-VLANs (and CVLANs) associated with a unique VRRP instance. There can be multiple partitions per physical port. A partition is the basic unit of redundancy. A partition cannot span multiple physical ports.

You can also create ICR clusters. An ICR cluster consists of a group of routers participating in ICR. You can use different E Series routers to configure a heterogeneous ICR cluster. For example, you can use an E120 or E320 router with an ES2 4G LM as a backup for subscribers on an ERX1440 router, or use an ERX1440 router with a GE-HDE LM as a backup for subscribers on an E120 or E320 router. However, you must keep in mind the hardware scaling limitations when you configure an ICR cluster containing both E320 routers and ERX routers.

| Note: While deploying ICR, service providers must ensure that the aggregation layer between the E Series router and access node (DSLAM) provides a broadcast domain per VLAN or per S-VLAN between active and backup routers. In the case of a direct connect model the access node must provide the broadcast domain per VLAN or per S-VLAN between the active and backup routers or instead provide an Ethernet switch such as EX Series Ethernet Switch between the access node and E Series router.

#### Related Topics

- ICR Scaling Considerations
- Configuring an ICR Partition

#### Published: 2010-06-30

Help
|
My Account
|
Log Out