Mpls l3vpn concepts, Site, Vpn instance – H3C Technologies H3C S12500-X Series Switches User Manual

Page 322: Address space overlapping, Vpn-ipv4 address

Advertising
background image

311

MPLS L3VPN concepts

Site

A site has the following features:

A site is a group of IP systems with IP connectivity that does not rely on any service provider network.

The classification of a site depends on the topology relationship of the devices, rather than the
geographical positions, though the devices at a site are, in most cases, adjacent to each other

geographically.

The devices at a site can belong to multiple VPNs, which means that a site can belong to multiple
VPNs.

A site is connected to a provider network through one or more CEs. A site can contain multiple CEs,

but a CE can belong to only one site.

Sites connected to the same provider network can be classified into different sets by policies. Only the

sites in the same set can access each other through the provider network. Such a set is called a VPN.

VPN instance

VPN instances, also called virtual routing and forwarding (VRF) instances, implement route isolation,

data independence, and data security for VPNs.
A VPN instance has the following components:

A separate Label Forwarding Information Base (LFIB).

An IP routing table.

Interfaces bound to the VPN instance.

VPN instance administration information, including route distinguishers (RDs), route targets (RTs),
and route filtering policies.

To associate a site with a VPN instance, bind the VPN instance to the PE's interface connected to the site.

A site can be associated with only one VPN instance, and different sites can associate with the same

VPN instance. A VPN instance contains the VPN membership and routing rules of associated sites.

Address space overlapping

Each VPN independently manages its address space.
The address spaces of VPNs might overlap. For example, if both VPN 1 and VPN 2 use the addresses on

subnet 10.110.10.0/24, address space overlapping occurs.

VPN-IPv4 address

BGP cannot process overlapping VPN address spaces. For example, if both VPN 1 and VPN 2 use the
subnet 10.110.10.0/24 and each advertise a route destined for the subnet, BGP selects only one of them,

resulting in the loss of the other route.
Multiprotocol BGP (MP-BGP) can solve this problem by advertising VPN-IPv4 prefixes.

Figure 81 VPN-IPv4 address structure

Type

2 bytes

4 bytes

IPv4 address prefix

6 bytes

Route Distinguisher (8 bytes)

Assigned number subfield

Administrator subfield

Advertising