Combined And Independent Ipv4 And Ipv6 Services In A Dual Stack Overview - Juniper JUNOSE SOFTWARE 11.0.X - BROADBAND ACCESS CONFIGURATION GUIDE 4-1-2010 Configuration Manual

3.

Combined and Independent IPv4 and IPv6 Services in a Dual Stack Overview

Internet Protocol version 6 (IPv6) is designed to enhance IP addressing and maintain
other IPv4 functions that work well. Organizations worldwide are developing new
applications to take advantage of the many feature enhancements within IPv6 to
help bring back end-to-end controlled communications across a transparent network
infrastructure. To ensure optimum performance, such applications implement a
dual-stack architecture in which IPv4 and IPv6 protocols share a common transport
and framing layer.
A dual-stack implementation supports both IPv4 and IPv6 hosts to help provide a
smooth transition to all parts of a enterprise network. With this flexible method of
implementation, providers can carry IPv6 traffic over their existing core networks
and customers can roll out IPv6 to more sites.
The PPP link between the customer premises equipment (CPE) and the provider
edge (PE) device or E Series router equipment might require both IPv4 and IPv6
protocols for transmission of data. Such networks require that PE devices run a dual
stack of IPv4 and IPv6 services. In this release, the Service Manager application on
the E Series router supports authentication, service selection, and service activation
and deactivation to subscribers for both IPv4 and IPv6 protocols in a dual stack
configuration.
You can configure services in a dual stack for IPv4 and IPv6 either independently or
as a single entity. Service Manager only tracks JUNOSe objects that are passed back
in the env.setResult method when a service definition is executed. In an IPv6
environment, you must modify the service definition macro file to include the objects
that the Service Manager requires to categorize a service as IPv4, IPv6, or a
combination of both IPv4 and IPv6.
Use a RADIUS CoA-Request message and the new service definition to create
the mutex service. The new service is considered a mutex service because it
belongs to a mutex group.
Service Manager activates the new service and deactivates any existing active
service that is a member of the same mutex group as the new service.
(Optional) Verify the status of the new service.
host1# show service-management subscriber-session client1@isp.com interface
ip 192.168.0.1
User Name: CLIENT1@ISP.COM, Interface: ip 192.168.0.1
Id: 1
Owner: AAA 4194326
Non-volatile: False
State: Active
ServiceSessions:
Name
----------------------- -----
tiered(2000000,3000000)
Name
----------------------- ------------
tiered(2000000,3000000)
Combined and Independent IPv4 and IPv6 Services in a Dual Stack Overview
Chapter 27: Configuring Service Manager
mutex Owner/Id State
----------- ------------------
12 AAA 4194326 ConfigApplySuccess
Non-volatile
False
Operation
---------
Activate
663