Juniper JUNOSE 11.0.X MULTICAST ROUTING, Configuration Manual

Page: 704 / 788

You can use the service-interface-type object in the service definition macro file to
specify whether a service must be defined for IPv4 or IPv6. Configuring the
service-interface-type object is not mandatory if a service is required only for IPv4
or L2TP subscribers. However, you must specify the service-interface-type object
when a service is required for IPv6 subscribers or IPv4 and IPv6 subscribers in a dual
stack. After you create a new service definition file with the service-interface-type
object and install it on the router, the Service Manager determines whether a service
must be tagged as IPv4, IPv6, or a combination of the two by parsing the objects
passed using the macro environment command,
env.setResult . The
service-interface-type object can be configured with one of the following values:
■
ipv4—Specifies that the service session profile must be applied to IPv4 interfaces
only. This object is optional only when IPv4 or L2TP subscribers are in a network.
■
l2tp—Specifies that the service session profile must be applied to L2TP interfaces.
This object is optional only when IPv4 or L2TP subscribers are in a network.
■
ipv4-ipv6—Specifies that the service session profile must be applied to both IPv4
and IPv6 interfaces in a dual stack. You must configure this object when IPv6
subscribers or IPv4/IPv6 subscribers in a dual stack are in a network.
■
ipv6—Specifies that the service session profile must be applied to IPv6 interfaces
only. You must configure this object when IPv6 subscribers or IPv4 and IPv6
subscribers in a dual stack are in a network.
When you create the service definition, include the following service attribute in the
service definition if you want the service to be defined for IPv4 interfaces only. The
profile identifier returned from the activate-profile object is applied to IPv4 interfaces.
<# env.setResult("service-interface-type", ipv4 ) #>
To configure a service macro to be used for IPv6 interfaces only, specify the following
object in the macro definition file. The profile identifier returned from the
activate-profile object is applied to IPv6 interfaces.
<# env.setResult("service-interface-type", ipv6 ) #>
To configure a service macro to be used for IPv4 and IPv6 interfaces in a dual stack,
specify the following object in the macro definition file. The profile identifier returned
from the activate-profile object is applied to both IPv4 and IPv6 interfaces.
<# env.setResult("service-interface-type", ipv4-ipv6 ) #>
Activation and Deactivation of IPv4 and IPv6 Services in a Dual Stack
You can configure IPv4 and IPv6 services in a dual stack either as independent
services or as a combined service. The following sections describe the two types of
configurations and their behavior when they are activated and deactivated.
Independent IPv4 and IPv6 Services in a Dual Stack
To configure separate services for IPv4 and IPv6 interfaces you must create and
install separate service definitions on the router. For example, you can create a
service definition called iponeV4 to be used for IPv4 traffic and service definition
664 ■
Activation and Deactivation of IPv4 and IPv6 Services in a Dual Stack
JUNOSe 11.0.x Broadband Access Configuration Guide