Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
Expand All close
Expand All close
list Table of Contents
file_download PDF
{ "lCode": "en_US", "lName": "English", "folder": "en_US" }
English
 

Configuring VRFs and PNE Details for a Site in a Centralized Deployment

date_range 19-Jun-18

If you use a physical network element (PNE) for a centralized deployment, you can use the Device Configuration page to configure the virtual routing and forwarding instances for your customer sites if you have not done so in Contrail and in Junos OS on the MX Series router.

To configure a VRF and PNE details for a site:

  1. Click Sites.

    The Sites page appears.

  2. Select the site name.
  3. Click More > Advanced Configuration.

    The Device Configuration page appears.

  4. Complete the configuration according to the guidelines provided in Table 1.
  5. Click OK.

Table 1: Fields on the Device Configuration Page

Field

Description

Site VRF Name

Specify the name of the virtual routing and forwarding (VRF) instance for the tenant.

Example: tenantA-VRF

Interface Name

Specify the MX Series router interface that connects to the customer site. This value matches the interface that you configure for the MX Series router physical network element (PNE).

Example: xe-2/2/2

Interface VLAN

(Optional) Specify a valid VLAN identifier, which is an integer in the range 1 to 4094. Specifying a VLAN identifier enables VLAN tagging. If you do not specify a value, the VLAN is untagged.

Example: 52

Interface Address

(Optional) Specify an IPv4 address with a network mask for the VLAN interface.

Example: 192.0.2.16/24

Default Gateway

(Optional) Specify the IPv4 address for the default route for Internet traffic.

Example: 192.0.2.20

Route Target

Specify the route target for the site. This value matches the route target value that you configure for the MX Series router PNE.

Example: 64512:1102

Route Distinguisher

Specify a unique route distinguisher for the site. You can specify any unique route distinguisher, such as the route target for the site.

Example: 64512:1102

footer-navigation