tos36013 08 07 vprn configuration

7/25/2019 TOS36013 08 07 VPRN Configuration

1/36

Section 8 Module 5 Page 1

All Rights Reserved Alcatel-Lucent 2009TOS36013-0807 Issue 1.0

Do not delete this graphic elements in here:

85All Rights Reserved Alcatel-Lucent 2009Module 5

VPRN ConfigurationTOS36013-0807 Issue 1.0

Section 8Basic Services

5620 SAM5620 SAM (Service Aware Manager) R7.0 Operator

TOS36010 Issue 1.0


2/36



All Rights Reserved Alcatel-Lucent 2009

5620 SAM 5620 SAM (Service Aware Manager) R7.0 OperatorBasic Services VPRN Configuration

8 5 2

Document History

Switch to notes view!

This page is left blank intentionally

First editionGARCIA LOZANO, Ren2009-08-1401

RemarksAuthorDateEdition

Document History


3/36





8 5 3

Module Objectives

Upon completion of this module, you will be able to:

Describe the operation and benefits of a VPRN service

List VPRN features, functions, components and topologies

Describe VPRN configuration on the Service Router using the SAM


4/36





8 5 4

Virtual Private Routed Network

PE A PE C

PE B

PE D

IP / MPLSNetwork

MP-IBGP RouteExchange

For all Services

VPRN ServiceRed

RI-1

RI-2

RI-1

RI-2

RI-1

RI-2

RI-1

RI-2

VPRN ServiceGreen

CE A

CE D

CE C

CE B

VPRN is a class of VPN that allows the connection of multiple sites ina routed domain over a provider managed IP/MPLS network

As of R4.0, inter-AS VPRNs are supported.

In Feb. 2006, Internet Draft RFC2547bis was moved to standard status, as RFC 4364.

A Virtual Private Routed Network (VPRN) service allows service providers to use their IP backbone toprovide a Layer 3 VPN service to their customers. VPRNs are also known as BGP/MPLS VPNs becauseBGP is used to distribute VPN routing information across the provider's backbone and MPLS is usedto forward VPN traffic from one VPN site to another.

From the customers perspective it looks as if all sites are connected to a routed domain

Service provider can reuse the IP/MPLS infrastructure to offer multiple services

Each VPRN appears like an additional routing instance, routes for a service between the variousPEs are exchanged using MP-BGP

Customer data is encapsulated using MPLS or GRE encapsulation

Each CE router becomes a peer of the PE router that it is directly connected to, not a peer to the

other CE routers. A CE router provides the PE router with route information for the privatecustomer network. Each associated PE router maintains a separate IP forwarding table for eachVPRN. Additionally, the PE routers exchange the routing information configured or learned fromall customer sites via MP-BGP peering. Each route exchanged via the MP-BGP protocol includes aRoute Distinguisher (RD), which makes the router unique and a Route Target, which identifies theVPRN association.

MPLS handles the forwarding between the PE routers. This means that the routers in the core of thenetwork need not know about the routes connecting the private networks. A VPRN service uses atwo-level label stack the ingress PE router pushes both an inner VC label and an outer tunnellabel onto a packet. After reaching the egress PE router via one or more MPLS Label SwitchedPaths (LSPs), the PE router pops the MPLS headers and delivers a normal IP packet to thecustomer.


5/36





8 5 5

VPRN Features

Consistent QoS model used across all VPN services

Highly scalable implementation

Per VPN controls to limit route table growth Consistent service and feature support over IP or MPLS

backbone

PE-CE routing support

Comprehensive set of OA&M tools

Statistics, billing and accounting data

Highly scalable:

VPN routing and forwarding (VRF) tables

Total routes

BGP Peerings

IP Interfaces

PE-CE routing supports:

Static Routes

BGP

RIP

OSPF

Statistics, billing and accounting data: Per IP-VPN (VPRN)

Current routes

Current routes per protocol source (Static, Local, BGP (PE-CE or Network), OSPF

Maximum number of routes (high watermark)

Per IP-VPN Interface:

Packets (In/Out)

Bytes (In/Out)

Errors In/Out


6/36





8 5 6

VPRN Architecture and Components

CE

CE

CE

CEPE

PE

CE

CE

CE

CE

PE

PE

Core Network

VPN Instance #1

Customer 1VPN

VRF for Customer 1 VPRN

VPN Instance #2

Customer 2VPN

VRF for Customer 2 VPRN

CE to PE Routing:

BGPRIP

StaticOSPF

Tunneling Mechanisms:RSVP-TE

LDP

GRE

CE

In a Virtual Private Routed Network (VPRN) the service provider network distributes its customers routing

information using MP-BGP and forwards their data packets using MPLS or GRE tunnels.

The routers in the service providers network perform one of two possible roles:

Provider (P) routers in the core. These routers simply support the switching of LSPs. They do not have anyknowledge of the existence of the VPRNs.

Provider Edge (PE) routers at the edge of the service providers network. These devices provide the MPLSsignaling and forwarding and partitioned IP routing and forwarding capabilities to partition customer dataflows received from or destined to the various customer sites.

The routers in the customers network which connect to the PEs are known as CE (Customer Edge) devices andare simple IP routers that forward and receive IP packets and distribute routing information using standardIP routing protocols or configured static routes and

are VPRN unaware. The architecture of the VPRN service is shown on the above diagram.

The components of a VPRN VPN are:

1.MP-BGP sessions between PEs to distribute customer routes across the service providers backbone.

2. Virtual Routing and Forwarding (VRF) tables on PEs specifying the import and export rules for customerroutes advertised between PEs.

3. Configured or learned VPRN routes from the customer sites.

4. MPLS or GRE tunnels between PEs for transporting customers traffic across the service providersbackbone.


7/36





8 5 7

VPRN Functions

Switch to notes view!Learning Routes from Local CEsA PE learns the routes from a CE through static routes or a dynamic routing protocol such as BGP. Locally

reachable IPv4 addresses as well as remote routes learned from other PEs are stored in the appropriate VRF.

Distributing RoutesThe PEs establish MP-BGP sessions with each other to distribute the routes they have learned from locally

connected CEs. The PEs maintain one or more VRF for each VPRN it is involved with, depending on the VPNtopology (mesh or hub and spoke, intranet or extranet).

Ensuring Unique Customer RoutesBecause different customers may use the same IP addresses within their respective networks, a method is

need to ensure that they remain unique when they are distributed across the service provider network. Thisis achieved by pre-pending the 4-byte IPv4 address with an 8-byte Route Distinguisher to form a newaddress called the VPN-IPv4 address. A distinct RD value can be associated with individual routes or with

all routes learned from a particular CE.

Populating Routes Into VRFsWhen a PE receives routes from another PE via their MP-BGP session it adds the learned routes into the

appropriate VRFs based on the route targets configured in each VRF, and contained in the routeadvertisement. An export route target is included in the route advertisement. If it matches the importroute target configured in a VRF, those routes are populated into the VRF.

Forwarding Data Among Customer SitesThe PEs forward customer traffic across the service providers network via GRE or LSP tunnels (outer label).

LSPs can be established using LDP or RSVP-TE signaling.

When the destination PE receives a data packet it determines the appropriate VRF to use to forward thepacket onward to the correct CE based on the inner label associated to a given VRF. The inner label isallocated by the local PE and advertised to the peer PE as part of a VPN-IPv4 route update.


8/36





8 5 8

Transport Tunnels

Switch to notes view!Each PE involved in a given VPRN service must be configured with a tunnel to every other PE participating inthe same VPRN service to transport a customers VPN traffic from one site to another.

The tunnel is created either through the configuration of a SDP or using the auto-bind option when creating a

VPRN service instance. For VPRN services, SDP tunnels can be created using MPLS with RSVP-TE or GREencapsulation. The auto-bind method for creating tunnels can be used with LDP or GRE.

If SDP tunnels are used, they must be created prior to the creation of the VPRN services. The configuration ofa SDP includes specifying the far-end PE and the type of encapsulation used, GRE or MPLS with RSVP-TE.

When RSVP-TE signaling is used, the outer LSP tunnels must be explicitly configured in addition to thecreation of the SDPs. When the outer tunnels are created using auto-bind with LDP there is no need toexplicitly configure the LSP tunnels. It is only necessary to enable LDP signaling on the appropriateinterfaces and once the MP-BGP sessions have been established, the LSP is automatically established.Similarly, outer tunnels created using auto-bind with GRE do not require any preliminary configuration theVPRN service only needs to be auto-bound to GRE.

When the auto-bind option is used traffic from all VPRN services (configured with the auto-bind option)traverse the same LSPs. In this case it is not possible to have alternate tunneling mechanisms (like GRE) or

the ability to configure sets of LSP's with bandwidth reservations for specific customers as is available withexplicit SDPs for the service. If LSPs with reserved bandwidth are needed then SDPs with RSVP-TE signalingshould be used for the outer tunnels.

If distinct tunnels per VPRN service are desired, then SDPs with GRE or RSVP-TE signaling should be used sothat VPRN instances can be explicitly bound to specific SDPs.


9/36





8 5 9

Transport Tunnels and Service Binding

Outer Label Each PE in the VPRN connected by a tunnel

Tunnels created by:

Creating an SDP (RSVP-TE or GRE)

Auto-bind (LDP or GRE)

Tunnel binding depends on the tunnel signaling protocol: LDP signaled LSP tunnels

GRE tunnels

RSVP-TE signaled tunnels

Each PE involved in a given VPRN service must be configured with a tunnel to every other PE participating in

the same VPRN service to transport a customers VPN traffic from one site to another.

The tunnel is created either through the configuration of a SDP or using the auto-bind option when creating aVPRN service instance. For VPRN services, SDP tunnels can be created using MPLS with RSVP-TE or GREencapsulation. The auto-bind method for creating tunnels can be used with LDP or GRE.

If SDP tunnels are used, they must be created prior to the creation of the VPRN services. The configuration ofa SDP includes specifying the far-end PE and the type of encapsulation used, GRE or MPLS with RSVP-TE.

When RSVP-TE signaling is used, the outer LSP tunnels must be explicitly configured in addition to thecreation of the SDPs. When the outer tunnels are created using auto-bind with LDP there is no need toexplicitly configure the LSP tunnels. It is only necessary to enable LDP signaling on the appropriateinterfaces and once the MP-BGP sessions have been established, the LSP is automatically established.Similarly, outer tunnels created using auto-bind with GRE do not require any preliminary configuration the

VPRN service only needs to be auto-bound to GRE.When the auto-bind option is used traffic from all VPRN services (configured with the auto-bind option)

traverse the same LSPs. In this case it is not possible to have alternate tunneling mechanisms (like GRE) orthe ability to configure sets of LSP's with bandwidth reservations for specific customers as is available withexplicit SDPs for the service. If LSPs with reserved bandwidth are needed then SDPs with RSVP-TE signalingshould be used for the outer tunnels.

If distinct tunnels per VPRN service are desired, then SDPs with GRE or RSVP-TE signaling should be used sothat VPRN instances can be explicitly bound to specific SDPs.


10/36





8 5 10

PE to CE Route Distribution

Switch to notes view!Static RoutesAll routes to be advertised by the CE to other CEs belonging to the VPRN are configured as static routes in the

VPRN service instance.

eBGP RoutingeBGP is configured between the PE and each attached CE belonging to the same VPRN in the VPRN service

instance.

The explicit configuration of the autonomous system number and router-id is optional. If omitted, thesevalues simply inherit the routers global AS number and router-id. The local address is also an optionalparameter. When it is not specified, it inherits the system IP address when communicating with IBGP peersand the interface address for directly connected eBGP peers.

If no import route policy is specified, then all BGP routes advertised by the CE are accepted by the PE.

An export policy is needed for the PE to advertise the routes learned from other PE sites in the VPRN instance

via MP-BGP to the CE router via eBGP.

RIP RoutingWhen RIP is used as the PE-CE routing protocol, a RIP instance must be enabled on the PE router in the router

context. Subsequently RIP can be configured on the PE-CE interface during the configuration of the VPRNservice. RIP is configured between the PE and each attached CE belonging to the same VPN in the VPRNservice instance.

By default RIP does not export routes it has learned to its neighbors. Therefore it is necessary to configure anexport policy to enable MP-BGP routes learned from remote CEs belonging to the VPN, to be redistributedinto RIP and to the local CE.

OSPF RoutingAs of R4.0 of the 7X50 routers, OSPF can be used at the PE-CE routing protocol. This provides a way for a

network to continue using a single protocol as it is migrated to an IP-VPN backbone.

OSPF LSA information is not transmitted natively across the IP-VPN. The OSPF routes are imported into MP-BGP as AS externals. As a result, other OSPF-attached VPRN sites on remote PEs will receive these via type5 LSA. This process is not automatic and requires the configuration of (existing) Route Policies.

Stub areas, OSPF-TE and sham links are not currently supported.


11/36


12/36





8 5 12

BGP Configuration - Configure BGP AS

3. Select Routing4. Enter the AS Number as 100

1. Select the Routing Instance-12. Select Properties

5. Select Protocols6. Verify that BGP is enabled

The following steps will cover the configuration of an iBGP mesh, which will be used for theadvertisement of VPRN routes from each customers VRFs.

An BGP mesh will be required among all participating sites in the VPRN service.

Configure BGP ASSelect the the Routing view in the tree window

Select each Router in turn where a VPRN site is required

Select the Routing instance-1 and then Properties.

Select the Routing tab, and enter the Autonomous System Number; 100 is used here as an

example.

Leave all other entries as the defaults.

Enable BGP On the Protocols tab

Check that BGP is enabled; if not, select the BGP Enabled check box, select OKor Apply.


13/36





8 5 13

Configure BGP AS

1. Select the BGP Routing Instance2. Select Properties

3.Verify the Site ID is theSystem Interface Address

Select the BGP routing instance for your router from the Navigation Tree Routing view, rightclick and select Properties.

In the General tab, verify the Site ID is the system interface IP address.


14/36





8 5 14

Configure BGP AS [Cont.]

1. Select the AS Properties tab2. Verify the AS number is 100

3.In the VPN tab, enable Family:VPN-IPVN4 and IPv4

Select the AS properties tab, and verify that the AS number is 100; 100 is used here as anexample.

In the VPN tab, enable Family: VPN-IPV4 and IPv4.It is essential that you enable the VPN-IPV4 family as this is required to carry VPRN routes. ClickApply or OK.


15/36





8 5 15

Create Peer Group

1. Select the Group tab2. Select Add3. Specify the Name.

4. Select the AS Properties tab5. Set the Peer AS to 1006. Select OK, OK, Apply and Yes

Select the Group tab. Select Add. Specify the Name. Click Apply and OK.

Select the AS Properties tab and set the Peer AS to 100. Other parameters will be inheritedfrom the global configuration. Select OK, OK, Apply and Yes.


16/36





8 5 16

Create BGP Peers

1. Select the Peer tab2. Select Add

3.Enter the System ID for the other router4.In the General tab, choose Select under

the Routing Instance group

Select the Peer tab, and create a BGP peer to one of the PE routers.

Select Add, and enter the system ID for the other router in the Peer Address field.

Under Routing Instance Group: choose Select.


17/36





8 5 17

Create BGP Peers [Cont.]

1. Select the Peer Group from the list2. Click OK, OK, Apply and Yes

3. Click Close or Cancel

Select the peer group from the list.

Click OK, OK, Apply and Yes. Click Close or Cancel.


18/36





8 5 18

Verify BGP Configuration

1. Double click on a Peer

2. Ensure the connection state is Established

Repeat the steps on the previous two pages for all PE routers in your network.

Your peering relationships will be up when all objects and aggregated alarms have cleared.

Double click on each peer and check that the connection state is Established.


19/36





8 5 19

Configure a Customer

1.Select ManageCustomers

2.Select

Create

3.Define theCustomerAttributes

Services must be associated with a customer. Though a service may only have one customer, thatcustomer may have more than one associated to them.

To create a Customer using the 5620 SAM, the network administrator or operator will use thefollowing sequence:From the Main Menu, select Manage CustomersIn the new window, click on the Create buttonComplete the customers details as provided in the configuration windowClick on the OK button.

To verify that the customer was created, or edit any detail:Select Manage Customers from the Main MenuClick on the Search button

Double-click on the appropriate entry or, select the appropriate customer and click on the Editbutton.Review or modify the details, as required.Click OK or Apply to save the changes or Cancel to disregard any modifications and close thewindow.


20/36





8 5 20

Configure Access Port

Configure Access PortAs discussed, a service requires a port facing the customer edge to be configured for Access and anEncapsulation type specified. To configure a port:

Navigate to the Equipment view in the Navigation Tree

Expand the tree and select the appropriate port or ports. It is possible to configure multipleports at the same time by through the Shift Click or Ctrl Click method.

Right-click and select Properties from the contextual menu

From the Mode drop-down menu, select Access

From the Encapsulation Type drop-down menu, select the appropriate encapsulation type

Set the port MTU. Remember that the port MTU must be set to a value set to support the

largest service MTU to be supported on that port. Select OK to complete the configuration.


21/36





8 5 21

Create a VPRN

3.Select the Customer

2.Choose Select

Description (optional)

Service Name

1. Select CreateService VPRN

To create a service, select the service type and assign the managed devices upon which theservice will terminate, referred to as the Service Sites.

To create a VPRN:

Select Create Service VPRN from the Main Menu

Click the Select button in the Customer block

Select a customer from the list that appears and click the OK button

Complete the remaining parameters, as required. Though optional, providing a service name andrelevant description will enable the network administrator or operator to find the service using theSearch filter.

Click Apply


22/36





8 5 22

Create a VPRN [Cont.]

1. Select the Components Tab

2. Select the Site IDs (PE Sites)participating in the service

3. Click OK

4. Select the Components Tab to view the service sites

Add and configure PE Sites:

Click on the Components Tab then right click on VPRN.

Select Create Site

Select the sites participating in the service.

Click OK

Select the Components Tab to view the service sites.


23/36





8 5 23


3.Give a selected site a Nameand Description

1. Select the Routing Instance2. Select Properties

Select the first Routing Instance

Right click and select Properties.

Give the site a Name and a Description.


24/36





8 5 24


1.Assign values as shown

Click on the Routing tab. This enables us to configure the virtual router instance. Configure thefollowing properties:

Router id = the system address of the router

AS number = 100

Route Distinguisher Type = Type 0 (use an assigned value as a route distinguisher)

Type 0 Administrative Value = 100

Type 0 Assigned Value = a unique identifier in order to make the network address unique tothis VPRN; 60 is used as an example.


25/36





8 5 25


1. Assign values as shown

Click on the VRF-Target sub tab and set the VRF route target properties as follows:

VRF Target Type = Define Default

Target Format = AS

Target AS Value = 100

Target Extended Community Value = unique value, which must match each distant end RouteTarget Value of the other sites participating in the service in order to allow the population ofnetwork addresses in the VRF; 95 is used as an example.


26/36





8 5 26


1. Set the transport toMPLS:LDP

2. Click OK and OK

Click on the Auto-Bind tab and set the Transport to MPLS:LDP. This will enable the use of LDPsignaled LSPs to reach each remote site, rather than SDPs.Click OKand OK.


27/36





8 5 27

Layer 3 Access Interfaces

4.Give the Layer 3 Access Interfacea Name and Description

1.Select Access Interfaces2.Select Create L3 Access Interface3.Select a Site

In the Components window, select Access Interfaces,

Right click and select on the Create L3 Access Interface. This will add a Layer 3 customer facinginterface to the virtual router on this site for this VPRN instance.

Give the interface a Name and Description.


28/36





8 5 28

Layer 3 Access Interfaces [Cont.]

1.Choose Select

2.Click OK

3.Click Search4. Select a Port5. Click OK

Port Selection Add a SAP to the interface via the Port tab

In the Port tab, Choose Select in the Terminating Port Region. Click OK.

In the Select Terminating Port window, select Search.


29/36





8 5 29


3.Assign an Outer Encapsulation Value

4.Enter a SAP Description

1.Select a port2.Click OK

Outer Encapsulation Value Assignment In the Port tab, assign the port an Outer Encapsulation Value or use the Auto-Assign ID

feature.

Enter a SAP Description.


30/36





8 5 30


Configure the IPaddress for a specificsite as shown.

IP Address Assignment Select the Address tab. Click Add. Configure an address on the interface of the specific router.

Note: Unlike IES, it does not matter if customer address spaces overlap on each VPRN service asthe route distinguisher keeps them unique.

In the IP Address window, type in the IP Address and Prefix Length, and click OK, OK, OK, OK.

Repeat all of the previous steps, starting with assigning a Name and Description for the othersite(s) participating in the service. In this example, the other site is node 146.


31/36





8 5 31

Final Steps

1.Click Apply, Yes2. Select Topology View

Final Steps In the Components window, select Apply, Yes and then Topology View to view the newlycreated VPRN.


32/36





8 5 32

Service Topology View

Service Topology View Having selected Topology View, the Service Topology window above will appear.

An alternative is to elect Manage Services, search for your VPRN service, select it.

Click on the Topology View button.

View the properties of the service.


33/36





8 5 33

Questions

?1. What method does a VPRN service use to differentiate overlapping customer address space?

a. Router target

b. Policies

c. Route Distinguisher

d. Filters

2. Select all CE to PE routing methods or protocols supported on the SR:

a. Static Routes

b. RIP

c. OSPF

d. IS-IS

e. BGP

3. Which two types of Route Distinguisher are used in the SR?

a. IP-Address and Autonomous System Number

b. Router Id and Autonomous System Number

c. IP-Address and Cluster-Id

d. Router-Id and Cluster-Id

4. What method is used to exchange routes between PEs?

a. OSPF

b. RIP

c. Static

d. MP-BGP


34/36





8 5 34

Answers

Switch to notes view!1. What method does a VPRN service use to differentiate overlapping customer address space?a. Router target

b. Policies

c. Route Distinguisher

d. Filters

2. Select all CE to PE routing methods or protocols supported on the SR:

a. Static Routes

b. RIP

c. OSPF

d. IS-IS

e. BGP

3. Which two types of Route Distinguisher are used in the SR?

a. IP-Address and Autonomous System Number

b. Router Id and Autonomous System Number

c. IP-Address and Cluster-Id

d. Router-Id and Cluster-Id

4. What method is used to exchange routes between PEs?

a. OSPF

b. RIP

c. Staticd. MP-BGP


35/36





8 5 35

End of ModuleVPRN Configuration


36/36



8 5 36

Last Blank Page

Switch to notes view!

This page is left blank intentionally

tos36013 08 07 vprn configuration

Documents