|
|
Figure 5-1, "Setup," provides a view of the Setup menu. Selections from this menu are used to initially populate the Device Inventory and VPN Inventory, as shown in the hierarchy pane.

The Setup menu includes the following options:
![]() |
Note Refer to the Cisco VPN Solutions Center: MPLS Solution User Guide for more details. |
The objective of creating targets from router configuration files is to populate the Device Inventory and make these router configuration files usable by MPLS VPN Solution.
To create targets from router configurations, implement the following steps:

The next window to appear is shown in Figure 5-3, "INFO for Creating Targets," which explains what is required to proceed.

Step 2 Click OK to continue.
The next window to appear is shown in Figure 5-4, "Create Targets from Router Configurations Window."

Step 3 In Figure 5-4, "Create Targets from Router Configurations Window," enter the following information:
Step 4 Click OK to continue.
Otherwise, click Cancel.
When you continue, the Device Inventory is populated in the hierarchy pane, as shown in Figure 5-5, "Device Inventory Population."

![]() |
Note Repeat these steps for each logical network you choose to define. |
The creation of a new Provider Administrative Domain defines the core network, that contains all the PEs, and the logical regions belonging to one Border Gateway Protocol (BGP) autonomous system (AS).
To set up a new Provider Administrative Domain, implement the following steps:

The next window to appear is the New Provider Administrative Domain with the General tab, as shown in Figure 5-7, "New Provider Administrative DomainGeneral."

Step 2 In the window as shown in Figure 5-7, "New Provider Administrative DomainGeneral," enter information in the following fields:
![]() |
Note Each Provider Administrative Domain has only one BGP AS number. |
Step 3 Click Add and a window as shown in Figure 5-8, "Region Definition," appears.
![]() |
Note Once you have added information to the Regions pane, you can click Edit or Delete to vary the routers included in this Region. |

Step 4 In the window as shown in Figure 5-8, "Region Definition," enter the unique user-defined Name of the logical Region you are creating, where PEs reside.
Step 5 Click Add.
![]() |
Note Once you have added information to the PE Routers pane, you can click Edit or Delete to vary the PE routers. |
Step 6 From the resulting window as shown in Figure 5-9, "Add Target Editor," select the following:

Step 7 Click OK to continue.
Otherwise, click Cancel.
From the New Provider Administrative Domain window, as shown in Figure 5-7, "New Provider Administrative DomainGeneral," you can select the Class of Service (CoS) Profiles tab and the result is a window as shown in Figure 5-10, "New Provider Administrative DomainClass of Service (CoS) Profiles."

![]() |
Note Once you have added information to the CoS Profiles pane, you can click Edit or Delete to vary the information. |
Step 2 Fill the resulting window, as shown in Figure 5-11, "New Class of Service (CoS) Profile," with specifics of how you want to shape traffic across your network.

Step 3 Click OK to continue.
Otherwise, click Cancel.
From the New Provider Administrative Domain window, as shown in Figure 5-7, "New Provider Administrative DomainGeneral," you can select the Advanced tab and the result is a window as shown in Figure 5-12, "New Provider Administrative DomainAdvanced."

Otherwise, click Cancel.
This section defines the customer and sites associated with the customer.
To set up a new VPN customer, implement the following steps:

The next window to appear is the New VPN Customer window, as shown in Figure 5-14, "New VPN Customer Window."

Step 2 In the New VPN Customer window, enter information in the following fields:
Step 3 Click Add.
![]() |
Note Once you have added information to the Customer Sites pane, you can click Edit or Delete to vary the information. |
Step 4 In the resulting window, as shown in Figure 5-15, "Add Customer Site," enter the following information:

Step 5 Click Add.
![]() |
Note Once you have added information to the Customer Edge (CE) Routers pane, you can click Edit or Delete to vary the information. |
Step 6 In the resulting window, as shown in Figure 5-16, "Add Assign Customer Edge Routers," enter the following information:

Step 7 Click OK to continue.
Otherwise, click Cancel.
This section defines a CE Routing Community (CERC) for the Provider Administrative Domain.
To set up a new VPN definition, implement the following steps:

The next window to appear is the Select Provider Administrative Domain window, as shown in Figure 5-18, "Select Provider Administrative Domain Window."

Step 2 In the Select Provider Administrative Domain window, click on the drop-down menu and select the Provider Administrative Domain for the new VPN. The choices you receive are the names you provided for the Provider Administrative Domains, as shown in Figure 5-6, "New Provider Administrative Domain."
Step 3 If you click OK to continue, the next window to appear is the New VPN Definition window, as shown in Figure 5-19, "New VPN DefinitionGeneral Window."

Step 4 In this window, specify the Name, a unique user-defined name that specifies your CERC.
The Provider A.D. field is completed by default based on what you entered in the previous window, as shown in Figure 5-18, "Select Provider Administrative Domain Window."
Step 5 Click OK to continue.
Otherwise, click Cancel.
From the New VPN Definition window, as shown in Figure 5-19, "New VPN DefinitionGeneral Window," you can select the CERCs tab and a new window appears, as shown in Figure 5-20, "New VPN DefinitionCE Routing Communities (CERCs) Window."

![]() |
Note Once you have added information to the CE Routing Communities pane, you can click Edit or Delete to vary the information. |
Step 2 In the resulting window, as shown in Figure 5-21, "Add CE Routing Community," you can build hub and- poke (recommended) and fully meshed VPNs with the CERC you choose.
![]() |
Note As shown in Figure 5-20, "New VPN DefinitionCE Routing Communities (CERCs) Window," a default CERC, which is configured for hub and spoke and autopick route target values, already exists. |

Step 3 Click OK to continue.
Otherwise, click Cancel.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Thu Apr 20 16:22:47 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.