Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Creating a Multicast VPN Service Definition

 

This topic describes how the Network Activate 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 Layer 3 VPN Service Definition.

Note

Multicast VPN services are supported on LN2600, SRX 550/650, and MX devices only.

To create a L3VPN Service definition upon which to base a MVPN service order, in the Network Activate task pane, select Service Design > Manage Service Definitions > Create L3VPN Service Definition.

  1. Specify values for the parameters in the General, UNI Settings, and Connectivity Settings pages as described in the following tables.

    In the General settings page, add information in the relevant fields as described in the following table:

    Field

    Description

    Name

    Type a name for this service definition.

    Service type

    Select L3VPN (Full Mesh)

    Comments

    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.

  2. Click Next.
  3. In the UNI Settings page, add information in the relevant fields as described in the following table:

    Field

    Description

    Ethernet

    Select this check box.

    VLAN ID selection

    Select Auto pick.

    VLAN range for auto-pick

    N/A

    VLAN range for manual input

    N/A

  4. Click Next.
  5. In the Connectivity Settings page, add information in the relevant fields as described in the following table:

    Field

    Description

    Route target

    A site within a VPN that a PE router services and to which the PE router will distribute routes.

    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.

    Size of address block

    The size of the IPv4 addresses block allocated for each PE/CE link.

    Range: 28–32

    See Specifying IPv4 Addressing Assignment in Layer 3 VPN Service Definitions.

  6. Click Finish.