Modifying a Hub-and-Spoke IP Service Order
You can modify and deploy previously configured IP hub-and-spoke service orders. Modifying a service order involves the following tasks:
When you modify a service or a service order, the read-only fields in the different pages of the wizard for service or service order modification are grayed out to indicate that you cannot modify those attributes.
Viewing the Service Definition
To view the service definition on which the service order is based:
Configuring Service Parameters Information
In this topic you configure general settings, VPN settings that can be applied to all end points, and routing protocol settings for the provider edge (PE) and customer edge (CE) devices.
Specifying General Settings
You must add the customer to the database before proceeding. See Adding a New Customer.
You configure general information about the service order in the General Settings box of the Enter Order Information window.
If a service template is attached to the service definition, there is a link to that template at the bottom of the Endpoint Settings section of the window. For instructions on working with service templates in service orders, see Creating a Service Order Based on a Service Definition with a Template.
To enter general settings information:
To enter connectivity settings information:
Specify whether the Autopick Route Target can be selected automatically or manually.
To assign the Route Target automatically, select the Auto Pick Route target check box.
To assign the Route Target, clear the Auto Pick Route Target check box.
The window expands to include the Route Target field. In the Route Target field, type a value.
Note:For Hub-and-Spoke service order, clear the Auto Pick Hub Route Target and Autopick Spoke Route Target check boxes to activate the Hub Route Target and Spoke Route Target fields, respectively.
When you manually type a route target, Junos Space accepts either of the following two formats:
prefix-number:assigned-number
Where prefix-number can be any numeric value from 1 through 65,535. The assigned-number can be any numeric value from 0 through 2,147,483,647.
IPV4-address:assigned-number
Where IPV4-address can be any valid IPv4 address, and assigned-number can be any numeric value from 0 through 65,535.
Note:You cannot edit this field if you have not selected the Editable in Service Order check box in the service definition.
Specify whether the Auto Pick Route Distinguisher can be selected automatically or manually.
To assign the Route Distinguisher automatically, select the Auto Pick Route Distinguisher check box.
To assign the Route Distinguisher manually, clear the Auto Pick Route Distinguisher check box.
The window expands to include the Route Distinguisher field. In the Route Distinguisher field, type a value.
When you manually type route distinguishers, Junos Space accepts either of the following two formats:
prefix-number: assigned-number
Where prefix-number can be any numeric value from 1 through 65,535. The assigned-number can be any numeric value from 0 through 2,147,483,647.
IPV4-address: assigned-number
Where IPV4-address can be any valid IPv4 address, and assigned-number can be any numeric value from 0 through 65,535.
Note:You cannot edit this field if you have not selected the Editable in Service Order check box in the service definition.
Select the Autopick Hub Route Target and Autopick Spoke Route Target check boxes if you want the Route target chosen automatically by the Connectivity Services Director application.
Note:You cannot edit this field if you have not selected the Editable in Service Order check box in the service definition.
To manually assign a Route target:
Clear the Autopick Hub Route Target and Autopick Spoke Route Target check boxes to activate the Hub Route Target and Spoke Route Target fields respectively.
In the Route Target field, enter a value.
When you manually enter route target, Junos Space accepts either of the following two formats:
<prefix-number>: <assigned-number>
Where <prefix-number> can be any numeric value from 1 to 65535, inclusive. The <assigned-number> can be any numeric value from 0 to 2,147,483,647, inclusive.
<IPV4-address>: <assigned-number>
Where <IPV4-address> can be any valid IPV4 address (in W.X.Y.Z "dot" notation), and <assigned-number> can be any numeric value from 0 to 65535, inclusive.
Select the Autopick Hub Route Distinguisher and the Autopick Spoke Route Distinguisher check boxes if you want the Route distinguisher chosen automatically by the Connectivity Services Director application.
To manually assign a Route distinguisher:
Clear the Autopick Hub Route Distinguisher and the Autopick Spoke Route Distinguisher check boxes to activate the Hub Route distinguisher and Spoke Route distinguisher fields respectively.
In the Route distinguisher field, enter a value.
When you manually enter route distinguishers, Junos Space accepts either of the following two formats:
<prefix-number>: <assigned-number>
Where <prefix-number> can be any numeric value from 1 to 65535, inclusive. The <assigned-number> can be any numeric value from 0 to 2,147,483,647, inclusive.
<IPV4-address>: <assigned-number>
Where <IPV4-address> can be any valid IPV4 address (in W.X.Y.Z "dot" notation), and <assigned-number> can be any numeric value from 0 to 65535, inclusive.
To enter VPN settings details:
To configure a separate label for each VRF to provide double lookup and egress filtering, select the VRF Table label check box.
Note:You cannot edit this field if you have not selected the Editable in Service Order check box in the service definition.
The Export Direct Routes check box is not editable in the service order.
Select the Enable MVPN check box to enable multicast virtual private network (MVPN).
To enter default UNI settings information:
Select a value for Ethernet Option:
Port
Dot1Q
Specifying the Dot1Q Ethernet option enables you to apply a Unit ID, a single VLAN ID, a VLAN Range, or a VLAN list to the service order.
QinQ
Specifying the QinQ Ethernet option enables you to apply a single VLAN, a VLAN Range, or a VLAN list to the service order. For an IP service deployed on a dual tagged interface, the inner tag determines the VPN routing and forwarding instance(VRF).
Select or clear the Autopick Interface IP check box.
To specify the Interface IP address, clear the Autopick interface IP check box.
To specify the IP Address Pool and IP Block Size field values in the Site Settings page of the service order creation wizard, select the Autopick interface IP check box.
If you have selected the Enable MC- LAG check box in the Service Settings section, the maximum and minimum values for IP block size are 29 and 28, respectively.
Note:You cannot edit the Autopick Interface IP check box if you have not selected the Editable in Service Order check box in the service definition.
Note:The fields specified in the Default UNI Settings section are based on the Ethernet Option type. The Logical IF Settings box is not available if you have selected the Ethernet Option as Port.
Specify whether the Autopick Interface Unit can be selected automatically or manually.
To assign the Unit ID automatically, select the Autopick Interface Unit check box.
To assign the Unit ID manually, clear the Autopick Interface Unit check box.
The window expands to include the Unit ID field. In the Unit ID field, type a value.
Range: 1 through 1073741823
Note:You can edit this field only if you have selected the Editable in Service Order check box for the VLAN ID selection in the service definition.
Specify whether the Autopick VLAN ID can be selected automatically or manually.
To assign the VLAN ID automatically, select the Autopick VLAN ID check box.
To assign the VLAN ID manually, clear the Autopick VLAN ID check box.
The window expands to include the VLAN ID field. In the VLAN ID field, type a value.
Note:You cannot edit this field if you have not selected the Editable in Service Order check box in the service definition.
Specifying PE-CE Settings Information
You configure VPN attributes that are usually common for all the endpoints in the service. The values that you provide vary, depending on the service definition on which the service order is based.
If you do not expect these attributes to be the same on all endpoints, you can set them to be the same for now and then make changes later, or you can skip this step and apply the attribute values one at a time later.
In the PE-CE Settings section of the Service Parameters page, depending on the PE-CE routing protocol—OSPF/Static Route or BGP/Static Route—do one of the following:
If BGP/Static Route routing protocol is specified in the service definition:
The AS override option is selected to allow a service provisioner to override the AS number. Clear the AS override check box to prevent a service provisioner from overriding the AS number.
Enter a value for the maximum number of prefixes accepted by a PE router from a CE router.
If OSPF/Static Route routing protocol is specified in the service definition, in the OSPF domain ID field, enter a IP address.
You can enter from 1.0.0.1 to 223.255.255.254. excluding 127.x.x.x.
The Node Parameters page appears.
Selecting N-PE Devices or Nodes
In this topic you select the N-PE devices that you want to host the service endpoints. The selection is made from the Select Endpoint PE Devices window.
The Choose Endpoints window, which you can view by clicking the Add icon on the Node Parameters page, shows only assigned N-PE devices that have an AS number configured. If you do not see the device you are looking for, use the CLI on the device to check for and assign an AS number.
N-PE devices that have L2VPN only do not appear.
To select endpoint N-PE devices:
Setting Attributes for Endpoints or Nodes
If a service template is attached to the service definition, there is a link to that template at the bottom of the Endpoint Settings section of the window. For instructions on working with service templates in service orders, see Creating a Service Order Based on a Service Definition with a Template.
You set attributes for each endpoint in the service from the Endpoint Settings window.
The interface shown in the UNI Interface field is automatically selected by the Connectivity Services Director application, which chooses the UNI that has the highest available capacity among interfaces that are in the Up state. To calculate the available capacity of the interface, the system subtracts the bandwidth reserved for each service deployed on that interface from the total capacity of the interface.
For each endpoint, the Endpoint Settings window shows the value for each UNI attribute.
As a service provider, you can create static routes on the service. To specify static routes for a CE device on the Node Parameters page:
- Click the Add icon above the Static Routes table. A new row is added to the table and highlighted in yellow to denote that you can enter the destination prefix and next-hop address.
- In the Destination Prefix field, enter the endpoint for the static route.
- In the Next-Hop field, enter the IP address of the next-hop. You can enter a dotted decimal notation, between 1.0.0.1 and 223.255.255.254 except 127.x.x.x.
- Insert as many static routes as you require. To delete an existing route, select the check box beside the route, and click Delete above the listed routes.
The MVPN and PIM Settings sections are displayed only if you selected the Enable MVPN check box in the Service Parameters page of the creation of service order wizard. To specify PIM settings for the service order:
From the PIM Mode list, specify the mode of PIM. Only PIM sparse mode is currently supported.
Note:A Protocol Independent Multicast (PIM) sparse-mode domain uses reverse-path forwarding (RPF) to create a path from a data source to the receiver requesting the data. When a receiver issues an explicit join request, an RPF check is triggered. A (*,G) PIM join message is sent toward the RP from the receiver's designated router (DR). (By definition, this message is actually called a join/prune message, but for clarity in this description, it is called either join or prune, depending on its context.) The join message is multicast hop by hop upstream to the ALL-PIM-ROUTERS group (224.0.0.13) by means of each router’s RPF interface until it reaches the RP. The RP router receives the (*,G) PIM join message and adds the interface on which it was received to the outgoing interface list (OIL) of the rendezvous-point tree (RPT) forwarding state entry. This builds the RPT connecting the receiver with the RP. The RPT remains in effect, even if no active sources generate traffic.
From the Interface list, select the interface to be used for PIM. When you modify a UNI from the list of interfaces on the Site Settings page, the GUI does not automatically delete the UNI from the Endpoint list. However, the newly added UNIs are added to the Interface list for the selected device or node.
To specify rendezvous point (RP) settings:
Click the Add icon above the table of RP addresses. The Add Rendezvous Point Address dialog box is displayed.
In the Rendezvous Point (device) field, configure the routing device as an actual or potential rendezvous point (RP). A routing device can be an RP for more than one group.
In the Interface field, specify the name of the interface on which PIM must be enabled. Specify the full interface name, including the physical and logical address components. UNIs for the selected device include lo0 if the selected device is enabled with loopback.
In the Group Address field, configure the address ranges of the multicast groups for which this routing device can be a rendezvous point (RP). By default, the routing device is eligible to be the RP for all IPv4 or IPv6 groups (224.0.0.0/4 or FF70::/12 to FFF0::/12).
Click OK to add the RP addresses to the table on the Node Parameters page.
To modify an added RP address, select the check box beside the row and click Edit. The dialog box is displayed to enable you modify the settings.
To delete an added RP address, select the check box beside the row and click Delete. The selected RP address is removed from the table.
To define MVPN settings for the service order:
From the MVPN mode list, indicate whether the shared-tree data distribution mode (RPT-SPT) or the shortest path tree only (SPT-only) mode of MVPN must be enabled to learn about active multicast sources using multicast VPN source-active routes. the default mode of operation is shortest path tree only (SPT-only) mode. In SPT-only mode, the active multicast sources are learned through multicast VPN source-active routes. This mode of operation is described in section 14 of the BGP-MVPN draft (draft-ietf-l3vpn-2547bis-mcast-bgp- 00.txt). If the default mode is not suitable for your environment, you can configure RPT-SPT mode (also known as shared-tree data distribution), as documented in section 13 of the BGP-MVPN draft (draft-ietf-l3vpn-2547bis-mcast-bgp-00.txt). RPT-SPT mode supports the native PIM model of transmitting (*,G) messages from the receiver to the RP for intersite shared-tree join messages. This means that the type 6 (*,G) routes get transmitted from one PE router to another. In RPT-SPT mode, the shared-tree multicast routes are advertised from an egress PE router to the upstream router connected to the VPN site with the C-RP
In the Provider Tunnel Name field, specify the provider tunnel name to configure virtual private LAN service (VPLS) flooding of unknown unicast, broadcast, and multicast traffic using point-to- multipoint LSPs. Also configure point-to-multipoint LSPs for MBGP MVPNs.
From the Site Type list, specify the site type of the MBGP MVPN. An MBGP MVPN defines two types of site sets, a sender site set and a receiver.
Select the Upstream Multicast Hop check box to configure the upstream multicast hop (UMH) to denote a router to use the unicast route preference to determine the single forwarder election.
In the Import Unicast Target field, specify the import targets specifically for sender sites or receiver sites, or can be borrowed from a configured unicast route target. Note that a sender site export route target is always advertised when security association routes are exported. By default, the VPN routing and forwarding (VRF) import and export route targets (configured either using VRF import and export policies or using the
vrf-target
statement) are used for importing and exporting routes with the MBGP MVPN network layer reachability information (NLRI). You can use theexport-target
andimport-target
options to override the default VRF import and export route targets. Select the Sender radio button to import unicast targets for sender sites, select the Receiver radio button to import unicast targets for receiver sites, or select None to disable the import of unicast targets.In the Import Target field, specify the import targets for sender and receiver sites. Select the Sender radio button to import targets for sender sites, select the Receiver radio button to import targets for receiver sites.
Select the Export Unicast Target check box to specify the export target to enable you to override the Layer 3 VPN export route targets used for importing and exporting routes for the MBGP MVPN network layer reachability information (NLRI).
In the Target Community field, specify the target community value to be used when exporting sender and receiver site routes. You can specify this value manually if you deselect the Autopick Export Target check box.
Select the Autopick Export Target check box to specify that you want to enable automatic selection of an export targert if a configuration is not provided. An imported automatic discovery route is treated as belonging to both the sender site set and the receiver site set.
If you have selected the Enable MC- LAG check box in the General Settings window, the Is Stitching Point check box is available for each endpoint. If you select this check box, all the parameters of that endpoint are disabled.
To configure or change the topology settings on the Node Parameters page:
The type of network circuit is displayed in the Topology field as full-mesh or hub-and-spoke.
Make sure the Is Stitching Point check box is not selected.
To add the loopback interface for an IP service, select the Add Loopback check box.
Note:If you provision a loopback interface for an IP service, an operator is able to identify a VRF routing instance. Thereafter, an operator can manually ping a remote CE router from a local PE router.
Select the Is Hub check box to enable the node to function as a hub. Deselect the check box if you want the device to function as a spoke. This field is not applicable for full-mesh IP services.
When you have finished configuring the endpoint settings, click Next.
The Site Settings page of the Create IP Service Order wizard appears.
Adding and Deleting UNI Interfaces
You can add or delete UNI interfaces on the PE devices that participate in a service:
To add a UNI interface on a selected device:
Select the Add icon in above the table of listed UNI interfaces, and from the Choose Endpoints window, select the device from which you want to retrieve the UNI interface to associate with the service order. The window refreshes to display all the UNI interfaces configured on the selected device.
Select the check boxes beside the UNIs that you want to associate.
Click Add to close the window. You are returned to the Site Settings page, and the selected UNIs are displayed in the table.
If the interface you selected in the previous step is already configured (duplicate) either type a different value in the VLAN ID field manually, or check the Autopick VLAN ID field.
To delete a UNI interface from a selected device:
Select the check box adjacent to the interface you want to delete, and click the Delete icon above the list of displayed interfaces.
If the deleted UNI is the only UNI selected from the device, then the device is deleted from the service configuration.
You can set or modify attributes for a UNI endpoint.
To modify a UNI interface for a selected device:
Select the row for the UNI endpoint that you want to modify.
The UNI Settings dialog box appears.
Modify the UNI Settings fields.
Either apply the attributes you already specified or add values that you did not configure for different attributes of a UNI.
When you have finished modifying the endpoint settings, click OK.
The Site Settings page appears.
Setting Attributes for UNIs or Sites
If there is a service template attached to the service definition, there is a link to that template at the bottom of the Site Settings section of the screen. For instructions on working with service templates in service orders, see Creating a Service Order Based on a Service Definition with a Template.
This part of the create Ethernet service order procedure sets the attributes for each UNI or interface in the service. Selection is made using the Site Settings screen.
The interface shown in the UNI Interface field is automatically selected by the Connectivity Services Director application, which chooses the UNI that has the highest available capacity among interfaces that are in the Up state. To calculate the available capacity of the interface, the system subtracts the bandwidth reserved for each service deployed on that interface from the total capacity of the interface.
For each endpoint, the Site Settings page shows the value for each UNI attribute.
To configure or change the site or UNI settings:
Deploying the New Service
To deploy the service:
The service order is now complete.