VPN Console: Setup Menu

Create Targets From Router Configurations

New Provider Administrative Domain

New VPN Customer

New VPN Definition

VPN Console: Setup Menu

Figure 6-1, "Setup Menu," 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.

Figure 6-1: Setup Menu

The Setup menu includes the following options:

Create Targets From Router Configurations, which creates targets from router configuration files to populate the Device Inventory.
New Provider Administrative Domain, which defines the core network and logical regions to populate the VPN Inventory with Provider Administrative Domains.
New VPN Customer, which defines the Customer and sites associated with the customer, to populate the VPN Inventory with VPN customers.
New VPN Definition, which defines the CE Routing Community (CERC) for the Provider Administrative Domain to populate the VPN Inventory.

Create T argets From Router Configurations

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:

Step 1 From the VPN Console window, choose Setup > Create Targets From Router Configurations, as shown in Figure 6-2, "Create Targets from Router Configurations."

Figure 6-2: Create Targets from Router Configurations

Note This approach only allows the creation of targets from router configuration files. To create a new target that is not a router, for example a NetFlow collector (UNIX workstation), or to create a router from DNS and password information, left click on Device Inventory in the hierarchy pane and then right click on Targets. Then left click on New Target.

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

Figure 6-3: INFO for Creating Targets

Step 2 Click OK to continue.

The next window to appear is shown in Figure 6-4, "Create Targets from Router Configurations Window."

Figure 6-4: Create Targets from Router Configurations Window

Step 3 In Figure 6-4, "Create Targets from Router Configurations Window," enter the following information:

Directory is the name of the directory where all the configuration files of all the routers are kept. You can click Select... and navigate to the directory of router configuration files of your choice and select it or enter the name of the directory in the field.
Network Name is a user-defined name used as a logical grouping within the Device Inventory. Later, routers will be defined as belonging to specific network name(s).
Domain Name (optional) is the provider's domain name if using Domain Name System (DNS).

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 6-5, "Device Inventory Population."

Figure 6-5: Device Inventory Population

Note Repeat these steps for each logical network you choose to define.

Note After the Device Inventory is populated in the hierarchy pane, to populate passwords, SNMP strings, and any time-outs and retries, you must do this through the hierarchy pane. Refer to the "New Target" section.

New Provider Administrative Domain

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:

Step 1 From the VPN Console window, choose Setup > New Provider Administrative Domain, as shown in Figure 6-6, "New Provider Administrative Domain."

Figure 6-6: New Provider Administrative Domain

Note An alternative to selecting Setup > New Provider Administrative Domain is to left click on VPN Inventory in the hierarchy pane and then right click on Provider Administrative Domains. Select New Provider A.D. and this path will navigate to the same location. When you choose the Setup > New Provider Administrative Domain path, you can only set up a new Provider Administrative Domain. From the hierarchy pane, you can also edit when you right click on a specific Provider Administrative Domain, displayed a level deeper.

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

Figure 6-7: New Provider Administrative Domain—General

Step 2 In the window as shown in Figure 6-7, "New Provider Administrative DomainGeneral," enter information in the following fields:

Name Enter a unique user-defined name to be given to this new Provider Administrative Domain that you are creating.
BGP AS Enter one BGP AS number. Each autonomous system is assigned a unique 16-bit number by the same central authority, the Internet Assigned Numbers Authority (IANA), that assigns IP network numbers.

Note Each Provider Administrative Domain has only one BGP AS number.

Contact Info (optional) You may include the name of the person who created this new Provider Administrative Domain and pertinent information about this person, for example the telephone number and e-mail address.

Step 3 Click Add and a window as shown in Figure 6-8, "Region Definition," appears.

Note Once you have added information to the Regions field, you can click Edit or Delete to vary the routers included in this Region.

Figure 6-8: Region Definition

Step 4 In the window as shown in Figure 6-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 field, you can click Edit or Delete to vary the PE routers.

Step 6 From the resulting window as shown in Figure 6-9, "Add Target Editor," select the following:

Network Click the drop-down menu to select a Network.
Role Click the drop-down menu to select a Role.
Highlight the row of router information you want added.

Figure 6-9: Add Target Editor

Step 7 Click OK to continue.

Otherwise, click Cancel.

From the New Provider Administrative Domain window, as shown in Figure 6-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 6-10, "New Provider Administrative DomainClass of Service (CoS) Profiles."

Figure 6-10: New Provider Administrative Domain—Class of Service (CoS) Profiles

Step 1 Click Add.

Note Once you have added information to the CoS Profiles field, you can click Edit or Delete to vary the information.

Step 2 Fill the resulting window, as shown in Figure 6-11, "New Class of Service (CoS) Profile," with specifics of how you want to shape traffic across your network.

Figure 6-11: New Class of Service (CoS) Profile

Step 3 Click OK to continue.

Otherwise, click Cancel.

From the New Provider Administrative Domain window, as shown in Figure 6-7, "New Provider Administrative DomainGeneral," you can select the Advanced tab and the result is a window as shown in Figure 6-12, "New Provider Administrative DomainAdvanced."

Figure 6-12: New Provider Administrative Domain—Advanced

Step 1 Click OK to keep the defaults or override the numbers with user-defined numbers to specify new values for the following and then click OK:

Start Route Distinguisher values at <BGP AS#>
Start Route Target values at <BGP AS#>

Otherwise, click Cancel.

New VPN Customer

This section defines the customer and sites associated with the customer.

To set up a new VPN customer, implement the following steps:

Step 1 From the VPN Console window, choose Setup > New VPN Customer, as shown in Figure 6-13, "New VPN Customer."

Figure 6-13: New VPN Customer

Note An alternative to selecting Setup > New VPN Customer is to left click on VPN Inventory in the hierarchy pane and then right click on VPN Customers. Select New VPN Customer and this path will navigate to the same location. When you choose the Setup > New VPN Customer path, you can only set up a new Customer. From the hierarchy pane, you can also edit when you right click on a specific Customer, displayed a level deeper.

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

Figure 6-14: New VPN Customer Window

Step 2 In the New VPN Customer window, enter information in the following fields:

Name Unique user-defined name to be given to this new Customer.
Contact Info (optional) You may include the name of the person who created this new Customer and pertinent information about this person, for example the telephone number and e-mail address.

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 6-15, "Add Customer Site," enter the following information:

Name Unique user-defined names with the Customer VPN of all logical Customer Sites where CEs reside.
Location Info (optional)

Figure 6-15: Add Customer Site

Step 5 Click Add.

Note Once you have added information to the Customer Edge (CE) Routers field, you can click Edit or Delete to vary the information.

Step 6 In the resulting window, as shown in Figure 6-16, "Add Assign Customer Edge Routers," enter the following information:

Choose a Network from a drop-down menu.
Choose a Role from a drop-down menu.
Highlight the row of CE router information you want to add, one CE at a time.
In the bottom area, choose whether this CE router is managed by the provider by checking or unchecking the box, and choose one of the following scenarios:
- No SA Agent
- Regular SA Agent
- Shadow SA Agent
- Management LAN
- Management LAN, SA Agent

Figure 6-16: Add Assig n Customer Edge Routers

Step 7 Click OK to continue.

Otherwise, click Cancel.

New VPN Defin ition

This section defines a CE Routing Community (CERC) for the Provider Administrative Domain.

To set up a new VPN definition, implement the following steps:

Step 1 From the VPN Console window, choose Setup > New VPN Definition, as shown in Figure 6-17, "New VPN Definition."

Figure 6-17: New VPN Definition

Note An alternative to selecting Setup > New VPN Definition is to left click on VPN Inventory in the hierarchy pane and then right click on VPNs. Select New VPN Definition and this path will navigate to the same wizard. When you choose the Setup > New VPN Definition path, you can only set up a new VPN. From the hierarchy pane, you can also edit when you right click on a specific VPN, displayed a level deeper.

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

Figure 6-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 6-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 i n Figure 6-19, "New VPN DefinitionGeneral Window."

Figure 6-19: New VPN Definition—General 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 6-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 6-19, "New VPN DefinitionGeneral Window," you can select the CERCs tab and a new window appears, as shown in Figure 6-20, "New VPN DefinitionCE Routing Communities (CERCs) Window."

Figure 6-20: New VPN Definition—CE Routing Communities (CERCs) Window

Step 1 Click Add.

Note Once you have added information to the CE Routing Communities field, you can click Edit or Delete to vary the information.

Step 2 In the resulting window, as shown in Figure 6-21, "Add CE Routing Community," you can build hub-and-spoke (recommended) and fully meshed VPNs with the CERC you choose.

Note As shown in Figure 6-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.

Figure 6-21: Add CE Ro uting Community

Step 3 Click OK to continue.

Otherwise, click Cancel.

Table of Contents