Creating a Multicast VPN Service Definition
This topic describes how the Connectivity Services Director application enables you to create an L3VPN service definition preliminary to creating a Multicast VPN (MVPN) service order.
Refer to the topic Creating a Full-Mesh IP Service Definition.
Multicast VPN services are supported on LN2600 and MX devices only.
To create a L3VPN Service definition upon which to base a MVPN service order, in the Network Services > Connectivity view pane, select Service Design > Manage Service Definitions > New > L3VPN Service Definition.
- Specify values for the parameters in the General and Site Settings windows as described in the following
tables.
In the General settings window, add information in the relevant fields as described in the following table:
Field
Description
Service Definition Name
Type a name for this service definition.
Service type
Select L3VPN (Full Mesh)
Description
Type comments to describe the service definition.
Service Template
None
Enable MVPN
Select this check box to enable MVPN settings in L3VPN service orders to be based on this service definition.
Decouple Service Status from Port Status
Do not select this check box.
- Click Next.
- In the Site Settings window, add information
in the relevant fields as described in the following table:
Field
Description
Ethernet
Select this check box.
Auto-pick VLAN ID
Select this check box.
VLAN range for auto-pick
N/A
VLAN range for manual input
N/A
Auto-pick Route Target
A site within a VPN that a PE router services and to which the PE router will distribute routes.
Auto-pick Router Distinguisher
An identifier attached to a route that distinguishes the VPN to which the route belongs. Each routing instance must have a unique route distinguisher associated with it.
Select Auto pick. JUNOS Space selects the route distinguisher automatically.
VRF Table label
A VRF table label distinguishes one VRF instance from another and enables double lookup and egress filtering.
Select this check box.
Export Direct Routes
Select this check box.
Allowed Routing Protocols
Select BGP/Static Route
PE Interface IP Address
The IP address of the interface on the PE device.
Select Auto pick.
IP Pool Type
Global—A Global IP address pertains to the service provider. There can be more than one global IPv4 address pool. However, each global pool must have its own unique name and its set of IPv4 addresses must not overlap with those of any other global pool. You can allocate addresses from global pools across multiple Layer 3 VPNs across multiple customers.
Customer—A Customer IP address pool pertains to an existing customer. These pools are associated with the corresponding customer. You can associate more than one customer IPv4 pool with each customer. However, each customer pool must have its own set of IPv4 addresses which must not overlap with those of any other pool belonging to the same customer. You can allocate addresses from customer pools across multiple Layer 3 VPNs for a particular customer.
IP Address Bock Size
The size of the IPv4 addresses block allocated for each PE/CE link.
Range: 28–32
- Click Review to examine the settings and modify
any attributes as required.
Note On the Review page, in the Service Templates section, the names of the service templates with which the service definition is associated are displayed. The Default Service Template column indicates whether the attached template is the default template.
- Click Finish.