Multi-Role Host; Hovpn - 3Com MSR 50 Series Configuration Manual

3com msr 30-16: software guide

Hide thumbs Also See for MSR 50 Series:

Table of Contents

Figure 416 Network diagram for inter-provider VPN option C using RRs

MPLS backbone

Multi-Role Host

The VPN attributes of the packets forwarded from a CE to a PE depend on the VPN

instance bound to the inbound interface. Therefore, all CEs whose packets are

forwarded through the same inbound interface of a PE must belong to the same

In a real networking environment, however, a CE may need to access multiple

VPNs through a single physical interface. In this case, you can set multiple logical

interfaces to satisfy the requirement. But this needs extra configurations and

brings limitations to the application.

Using multi-role host, you can configure policy routing on the PE to allow packets

from the CE to access multiple VPNs.

To allow information from other VPNs to reach the CE from the PE, you must

configure static routes on other VPNs that take the interface connected to the CE

as the next hop.

All IP addresses associated with the PE must be unique to implement the multi-role

host feature.

In practice, you are recommended to centralize the addresses of each VPN to

improve the forwarding efficiency.

1 Hierarchical model and plane model

In MPLS L3VPN solutions, PEs are the key devices. They provide two functions:

User access. This means that the PEs must have a large amount of interfaces.

VPN route managing and advertising, and user packet processing. These

require that a PE must have a large-capacity memory and high forwarding

Multi-hop MP-EBGP

MPLS L3VPN Overview

MPLS backbone

Show Quick Links

Table of Contents