Generally, geographically dispersed networks are connected through the MPLS VPN network of an Internet Service Provider (ISP). The system introduces a concept called MPLS Cloud to simulate the MPLS functions by following the rules of forwarding labeled packets. In the system, an MPLS Cloud is taken as a device and uses a virtual routing table to calculate A-B paths across the MPLS.

Here is a sample of MPLS VPN network. It includes the following types of elements:

Customer Edge (CE) — routers at the customer premises that is connected to the provider edge of a service provider IP/MPLS network. CE peers with the provider edge (PE) and exchanges routes with the corresponding VRF inside the provider edge (PE).

Provider Edge (PE) — routers in the provider's network that is connected to the customer edge (CE) routers located at customer sites. PE routers support VPN and MPLS label functionality. Within a single VPN, pairs of PE routers are connected through a virtual tunnel, typically a label-switched path (LSP).

Provider (P) — provider routers within the core of the provider's network are not connected to any routers at a customer site but are part of the tunnel between pairs of PE routers. Provider routers support LSP functionality as part of the tunnel support, but do not support VPN functionality.

Note: Only the domain admin, power users, or users with the Device Management privilege can add, edit, and delete an MPLS Cloud.

Adding an MPLS Cloud

1.Log in to the Domain Management page.

2.In the Domain Management page, click Fine Tune on the Start Page or select Operations > Fine Tune from the quick access toolbar.

3.On the Fine Tune tab, select Cloud Manager in the left pane and click Add in the right pane.

4.In the Cloud Definition dialog box, follow the steps below to define an MPLS Cloud.

1)Enter a name for the cloud.

2)Keep the default Cloud Type MPLS L3 VPN.

3)Enter a description of the MPLS cloud.

4)Add MPLS edge devices to the MPLS Cloud by either of the following ways:

Dynamic Search
Manually Add

5.(Optional) Click Exclude to select CE devices or interfaces that you want to exclude from the MPLS cloud.

6.Click OK.

Building Topology and NCT Table for MPLS Cloud through a Benchmark

After creating an MPLS cloud, you need to build the topology and NCT table (a virtual routing table used for path calculation) via a benchmark task.

To build the topology and NCT table for an MPLS Cloud, complete the following steps:

1.Edit a benchmark task and go to the Additional Operations after Benchmark tab.

2.In the Update MPLS Cloud area, select the Recalculate Cloud NCT option.

3.In the Build Topology area, select the IPv4 L3 topology option.

The system will build topology and NCTs for all MPLS clouds after the benchmark task is completed.

Calculating Paths across an MPLS Cloud

After building the NCT and topology, you can calculate paths across MPLS clouds. During the path calculation, the system looks up the virtual routing table to find the correct inbound and outbound traffic interfaces of the MPLS cloud.


Further operations:

Exporting MPLS Cloud
Viewing the NCT of an MPLS Cloud


See also:

Discovering Network Devices

Roles and Privileges