VPN Console: Provisioning Menu

Add VPN Service to CE, which explains how to submit a new Service Request to add VPN service between a PE and a CE.
Deploy Service Requests, which explains how to set up a scheduled task that deploys Service Request(s) to the appropriate routers.
View Deployment Log, which explains how to view a deployment log.
Export Service Request Configlets, which explains how to export configlets to a directory.
List All New Service Requests, which explains how to get a report of all new Service Requests with the state of Requested.
List All Service Requests, which explains how to get a report of all Service Requests in the system.
Purge Closed Requests from Database, which explains how to purge all closed Service Requests from the database.

Add VPN Se rvice to CE

This section explains how to submit a new Service Request to add VPN service between a PE and a CE.

To add VPN service to a CE, implement the following steps:

Step 1 From the VPN Console window, choose Provisioning > Add VPN Service to CE, as shown in Figure 7-2, "Add VPN Service to CE."

Note An alternative to selecting Provisioning > Add VPN Service to CE is to select Tools > Tasks and then in the Actions menu item select New Task > Add VPN Service to CE and click Ok. Both paths navigate to the same set of wizards.

Figure 7-2: Add VPN Service to CE

The next window to appear is an Introduction that explains what occurs when taking this path.

Step 2 Click Next in the Introduction window to continue.

Step 3 In Figure 7-3, "Add VPN Service to CE," use the drop down menu to select the Customer from which you want to select a CE.

Figure 7-3: Add VPN Service to CE

Step 4 Use the drop-down menu to select the Site from which you want to select the CE.

Step 5 In the CE Routers area, highlight one CE router you want to select.

Step 6 Click Next to continue.

Step 7 In the resulting window, as shown in Figure 7-4, "Add VPN Service to CESelect PE," use the drop-down menu to select the Provider from which you want to select a PE.

Figure 7-4: Add VPN Service to CE—Select PE

Step 8 Use the drop-down menu to select the Region from which you want to select a PE.

Step 9 In the PE Routers area, highlight one PE router that you want to select.

Step 10 Click Next to continue.

Step 11 From the Select a VPN area in Figure 7-5, "Add VPN Service to CESelect VPN," select the VPN for which you want to become a member.

Figure 7-5: Add VPN Service to CE—Select VPN

Step 12 Optionally click one of the following:

Join as spoke The default is to join as hub. Check this option to define the VPN membership as spoke.
Advanced setup required If checked, a new window appears that allows you to join multiple VPNs and/or multiple CERCs.
Join the management VPN When a Management VPN has been previously created, this choice is automatically checked. Uncheck this option if you choose not to join the Management VPN.

Note Refer to the Cisco VPN Solutions Center: MPLS Solution Provisioning and Operations Guide for more information.

Step 13 Click Next to continue.

Step 14 In the next window to appear, the layout depends on which of the following routing protocols is chosen:

Static to select manual routing; proceed to the "Static Protocol" section.
OSPF to select the Open Shortest Path First (OSPF) routing protocol; proceed to the "OSPF Protocol" section.
BGP to select the Border Gateway Protocol; proceed to the "BGP Protocol" section .
RIP to select the Routing Information Protocol; proceed to the "RIP Protocol" section.
None (recommended for Service Requests using cable link); proceed to the "None" section.

With each routing protocol selected, certain choices are made available.

Static Proto col

This section explains the navigation path when you select the Static routing protocol.

Step 1 When you choose the Static protocol, a window, as shown in Figure 7-6, "Add VPN Service to CESelect Static," appears. Do the following:

Select Give Only default routes to CE if you want to give a default route.
Select Redistribute Connected (BGP only) if you want to redistribute your connected routes into BGP.

Figure 7-6: Add VPN Service to CE—Select Static

Step 2 Click Next.

Step 3 The next window to appear is shown in Figure 7-7, "Add VPN Service to CEStatic Type."

Figure 7-7: Add VPN Service to CE—Static Type

Note If in Figure 7-6, "Add VPN Service to CESelect Static," you chose Give Only Default Routes to CE, the defaults will be chosen and the window that appears will not have the bottom area as shown in Figure 7-7.

Step 4 In the top area in Figure 7-7, "Add VPN Service to CEStatic Type," click Add.

Step 5 In the resulting window, as shown in Figure 7-8, "Advertised Routes," you can enter all CE routes that you want advertised to other CEs in the same VPN. Enter the specific address in IP Address and click Add.

This populates the top area. Then you can choose to Modify or Delete entries in this top area.

Figure 7-8: Advertised Rou tes

Click Ok to continue.

Step 6 In the bottom area in Figure 7-7, "Add VPN Service to CEStatic Type," click Add.

Step 7 In the resulting window, as shown in Figure 7-9, "Routes to Reach All Sites," you can enter routes to reach all sites. Enter the specific address in IP Address and click Add.

This populates the bottom field. Then you can choose to Modify or Delete entries in this bottom field.

Figure 7-9: Routes to Reach All Sites

Step 8 Click Ok to continue.

Step 9 You will be returned to a window as in Figure 7-7, "Add VPN Service to CEStatic Type," and you will find the field populated.

Click Next to continue.

Step 10 Proceed to the "Steps After Choosing the Protocol" section.

OSPF Protocol

This section explains the navigation path when you select the OSPF routing protocol.

Step 1 When you choose the OSPF protocol, a window, as shown in Figure 7-10, "Add VPN Service to CESelect OSPF," appears. Do the following:

Select Give Only default routes to CE if you want to give a default route.
Select Redistribute Static (BGP & OSPF) if you want to redistribute your Static routes into BGP and OSPF.
Select Redistribute Connected (BGP only) if you want to redistribute your connected routes into BGP.
In the OSPF Process ID on CE field, enter a process identifier number from 1 through 65535.
In the OSPF Area Number on CE selections, choose to enter an area number from 0 through 4294967295 or choose to enter an area in IP format.
In the OSPF Process ID on PE field, enter a process identifier number from 1 through 65535.
In the OSPF Area Number on PE selections, choose to enter an area number from 0 through 4294967295 or choose to enter an area in IP format.

Figure 7-10: Add VPN Service to CE—Select OSPF

Step 2 Click Next.

Step 3 The next window to appear is shown in Figure 7-11, "Add VPN Service to CERedistributed Protocols."

Click Add to add the routing protocol you want to redistribute into OSPF.

Figure 7-11: Add VPN Service to CE—Redistributed Protocols

Step 4 In the resulting window, as shown in Figure 7-12, "Redistributed Protocols," select a redistributed protocol. Note: Only OSPF is not available for selection. This allows a CE using OSPF to learn its routing information by redistribution.

Figure 7-12: Redistributed Protocols

Step 5 Click Add to populate the lower area with the protocol you choose.

Step 6 Repeat Step 4 and Step 5 until you have populated the bottom area with all the redistributed protocols you want to use.

Note Once information exists in the bottom area, you can highlight an item and click Delete to delete it.

Step 7 Click Ok to continue.

Step 8 You will be returned to a window as in Figure 7-11, "Add VPN Service to CERedistributed Protocols," and you will find the area populated.

Click Next to continue.

Step 9 Proceed to the "Steps After Choosing the Protocol" section.

BGP Proto co l

This section explains the navigation path when you select the BGP routing protocol.

Step 1 When you choose the BGP protocol, a window, as shown in Figure 7-13, "Add VPN Service to CESelect BGP," appears. Do the following:

Select Redistribute Static (BGP only) if you want to redistribute your Static routes into BGP.
Select Redistribute Connected (BGP only) if you want to redistribute your connected routes into BGP.
Select Neighbor AllowAS-in if you want to go to multiple BGP sites with the same AS number. Fill in the associated field with a number 1 to 10, which specifies the number of hops allowed.
Select Neighbor AS-Override if you want to re-use the same AS number for multiple BGP sites.
Fill in the BGP AS ID with an autonomous system identifier number 1 through 65535.

Figure 7-13: Add VPN Service to CE—Select BGP

Step 2 Click Next.

Step 3 The next window to appear is shown in Figure 7-14, "Add VPN Service to CEBGP Type."

Click Add to add the routing protocol you want to redistribute into BGP.

Figure 7-14: Add VPN Service to CE—BGP Type

Step 4 In the resulting window, shown in Figure 7-15, "Redistributed Protocols," select a redistributed protocol. Note: Only BGP is not available for selection. This allows a CE using BGP to learn its routing information by redistribution.

Figure 7-15: Redistributed Prot ocols

Step 5 Click Add to populate the lower field with the protocol you choose.

Step 6 Repeat Step 4 and Step 5 until you have populated the bottom field with all the redistributed protocols you want to use.

Note Once information exists in the bottom field, you can highlight an item and click Delete to delete it.

Step 7 Click Ok to continue.

Step 8 You will be returned to a window as in Figure 7-14, "Add VPN Service to CEBGP Type," and you will find the field populated.

Click Next to continue.

Step 9 Proceed to the "Steps After Choosing the Protocol" section.

RIP Prot ocol

This section explains the navigation path when you select the RIP routing protocol.

Step 1 When you choose the RIP protocol, a window, as shown in Figure 7-16, "Add VPN Service to CESelect RIP," appears. Do the following:

Select Give Only default routes to CE if you want to give a default route.
Select Redistribute Static (BGP & RIP) if you want to redistribute your Static routes into BGP and RIP.
Select Redistribute Connected (BGP only) if you want to redistribute your connected routes into BGP.

Figure 7-16: Add VPN Service to CE—Select RIP

Step 2 Click Next.

Step 3 The next window to appear is shown in Figure 7-17, "Add VPN Service to CERIP Type."

Click Add to add the routing protocol you want to redistribute into RIP.

Figure 7-17: Add VPN Service to CE—RIP Type

Step 4 In the resulting window, shown in Figure 7-18, "Redistributed Protocols," select a redistributed protocol. Note: Only RIP is not available for selection. This allows a CE using RIP to learn its routing information by redistribution.

Figure 7-18: Redistributed Proto cols

Step 5 Click Add to populate the lower field with the protocol you choose.

Step 6 Repeat Step 4 and Step 5 until you have populated the bottom field with all the redistributed protocols you want to use.

Note Once information exists in the bottom field, you can highlight an item and click Delete to delete it.

Step 7 Click Ok to continue.

Step 8 You will be returned to a window as in Figure 7-17, "Add VPN Service to CERIP Type," and you will find the field populated.

Click Next to continue.

Step 9 Proceed to the "Steps After Choosing the Protocol" section.

None

This section explains the navigation path when you select the None option (recommended for cable).

Step 1 When you choose the None option, a window, as shown in Figure 7-19, "Add VPN Service to CESelect None," appears. Do the following:

Select Redistribute Static (BGP only) if you want to redistribute your connected routes into BGP.
Select Redistribute Connected (BGP only) if you want to redistribute your connected routes into BGP.

Figure 7-19: Add VPN Service to CE—Select None

Step 2 Click Next.

Step 3 Proceed to the "Steps After Choosing the Protocol" section.

Steps After Choosing the Protocol

After choosing a routing protocol, in the resulting window, shown in Figure 7-20, "Add VPN Service to CESelect PE CE Interface," you select in formation about the type of interface.

Figure 7-20: Add VPN Service to CE—Select PE CE Interface

Step 1 Choose the WAN or LAN interface.

Step 2 In the second area, do the following:

Select the interface and encapsulation types for the PE from the Interface and Encapsulation drop-down menus, respectively. The Interface choices come from the configuration file and the Encapsulation choices are associated by the interface.
Select Shutdown PE Interface if you want to shut down the PE interface.
Select The selected interface is a maintenance interface if you want to provision the maintenance subinterface for cable interfaces, which is always the subinterface numbered 1.

Step 3 In the final area, select the interface and encapsulation types for the CE from the Interface and Encapsulation drop-down menus, respectively. The Interface choices come from the configuration file and the Encapsulation choices are associated by the interface.

Step 4 Click Next to continue.

Step 5 The layout of the next window to appear depends on the interface and encapsulation you chose in Figure 7-20, "Add VPN Service to CESelect PE CE Interface." Figure 7-21, "Example of Add VPN Service to CESelect Encap Info," is an example of selecting encapsulation information.

Enter the following information for the associated encapsulation types:

Frame Relay: Enter the data-link connection identifier (DLCI). (Refer to the "Modifying Frame Relay LMI Types" section for information about setting up the Local Management Interface (LMI) types.)
Frame Relay IETF: Enter the data-link connection identifier (DLCI). (Refer to the "Modifying Frame Relay LMI Types" section for information about setting up the Local Management Interface (LMI) types.)
ATM: Enter the Sub-interface, virtual path identifier (VPI), and virtual channel identifier (VCI).
ISL: Enter the virtual LAN (VLAN) identifier.

For other encapsulation types, this window does not appear. Proceed to Step 6.

Figure 7-21: Example of Add VPN Service to CE—Select Encap Info

Step 6 In the next window, as shown in Figure 7-22, "Add VPN Service to CESelect IP Address," select an IP addressing scheme for the PE and CE.

Select one of the following:

IP Unn umbered is only available if you chose WAN in Figure 7-20, "Add VPN Service to CESelect PE CE Interface." IP unnumbered is configured on the PE and CE interfaces.
IP Numb ered is available if you chose WAN or LAN in Figure 7-20, "Add VPN Service to CESelect PE CE Interface." IP numbered is configured on the PE and CE interfaces.
IP Numbered With Extra CE Loopback is available if you chose WAN or LAN in Figure 7-20, "Add VPN Service to CESelect PE CE Interface." IP numbered is configured on the PE and CE interfaces and a loopback is configured on the CE.

Additionally, you can check the box to Use Automatically Assigned IP Address (only if you chose WAN in Figure 7-20, "Add VPN Service to CESelect PE CE Interface") or uncheck the box and enter IP address information for the following (the choices available depend on the address scheme you chose):

PE Interface If IP Unnumbered was chosen, this is from pool /32; if IP Numbered was chosen, this is from pool /30; if IP Numbered With Extra CE Loopback was chosen, this is from pool /30.
CE Interface If IP Unnumbered was chosen, this is from pool /32; if IP Numbered was chosen, this is from pool /30; if IP Numbered With Extra CE Loopback was chosen, this is from pool /30.
CE Loopback This choice is only available if IP Numbered With Extra CE Loopback was chosen. It is from pool /32.

Figure 7-22: Add VPN Service to CE—Select IP Address

Step 7 Click Next to continue.

Step 8 In the resulting window, as shown in Figure 7-23, "Add VPN Service to CESelect VRF Parameters," enter the following information:

Export Map Enter the name of an existing export route map on the PE.
Import Map Enter the name of an existing import route map on the PE.
Maximum Ro ute Enter the maximum number of routes that can be imported into the VPN routing/forwarding instance (VRF) on this PE.
Turn on NetFlow accounting Check this box if you want to turn on NetFlow accounting. Otherwise, be sure this box is not checked.

Note The bottom part of this window with the WARNING and the ability to enter VRF Name and RD Value only appears when you have set the property netsys.srvc.VRFRDOverride.unix to true in the csm.properties file. This setting allows the manual modification of the VRF name and route distinguisher (RD).

VRF Name This advanced feature gives you the opportunity to rename the system-generated VRF name to a name of your choice. Enter a maximum 32-character name in this field.
RD Value This advanced feature gives you the opportunity to renumber the system-generated RD number to a number of your choice. Enter a number in conventional RD numbering format in this field.

Figure 7-23: Add VPN Service to CE—Select VRF Parameters

Step 9 Click Next to continue.

Step 10 In the next window, as shown in Figure 7-24, "Add VPN Service to CESelect CoS Profile," from the list, you can optionally highlight a Class of Service (CoS) profile to assign to the PE to CE link.

Figure 7-24: Add VPN Service to CE—Select CoS Profile

Step 11 Click Next to continue.

Step 12 The final window, as shown in Figure 7-25, "Add VPN Service to CEConfirm," provides a list of all the information for Add VPN Service to CE. Review this information. If information is inaccurate, be sure to continue to click < Back until you reach the window to update the invalid information. Then click Next until you exit.

Figure 7-25: Add VPN Service to CE—Confirm

If the information in this final window is accurate, click Next to complete this path.

Modifying Frame Relay LMI Types

The information in this section is only applicable if you chose the encapsulation type Frame Relay or Frame Relay IETF in Step 5 in the "Steps After Choosing the Protocol" section.

Local Management Interface (LMI) is a signalling standard between the router and the Frame Relay switch that provides a Frame Relay management mechanism. The LMI type must match the type used by the network. Changing the LMI type is a global change that affects all service requests (for related information, see the next section, "Applying a Mixed Set of LMI Types").

If a service provider or customer needs to modify the Frame Relay Local LMI types, they can do so by modifying the appropriate property in the csm.properties file. Changing the LMI type in this way applies the Frame Relay modification to the Customer Edge router (CE) only.

You can set the LMI type to any one of three values:

LMI Value Description

ansi

Annex D defined by ANSI standard T1.617

cisco

LMI type defined jointly by Cisco and other companies. This is the default.

q933a

ITU-T Q.933 Annex A

LMI Value	Description
ansi	Annex D defined by ANSI standard T1.617
cisco	LMI type defined jointly by Cisco and other companies. This is the default.
q933a	ITU-T Q.933 Annex A

To modify the LMI type in the csm.properties file, follow these steps:

Step 1 On the MPLS VPN Solution workstation, log in as the vpnadm user.

Step 2 Go to the directory /<install_directory>/vpn/etc.

Step 3 Open the csm.properties file with a text editor.

Step 4 Find the following line in the csm.properties file:

netsys.watchdog.server.CVPIMServer.frameRelayLmiType = none

Step 5 Change the none value to the appropriate LMI type value. For example, to change the LMI type to cisco, you would edit the line as follows:

netsys.watchdog.server.CVPIMServer.frameRelayLmiType = cisco

Step 6 Save your changes and exit the file.

Step 7 Log out (exit) from the vpnadm user.

Applying a Mixed Set of LMI Types

Changing the LMI type is a global change that affects all active service requests. To apply a mixed set of LMI types, do the following:

Step 1 Modify the csm.properties file to set the desired LMI type as described in the previous section.

Step 2 In the VPN Console, deploy the service requests that are associated with the LMI value set in Step 1.

Step 3 Modify the csm.properties file again to set the desired LMI type for the next set of service requests.

Step 4 In the VPN Console, deploy the service requests that are associated with the LMI value set in Step 3.

Deploy Service Requests

This section explains how to set up a scheduled task that deploys Service Request(s) to the appropriate routers.

To deploy Service Requests, implement the following step:

Step 1 From the VPN Console window, choose Provisioning > Deploy Service Requests, as shown in Figure 7-26, "Deploy Service Requests."

Note An alternative to selecting Provisioning > Deploy Service Requests is to select Tools > Tasks and then in the Actions menu item select New Task > Deploy Service Requests and click Ok. Both paths navigate to the same set of wizards.

Figure 7-26: Deploy Service Requests

The next window to appear is an Introduction that explains what occurs when taking this path.

Step 2 Click Next in the Introduction window to continue.

The next window to appear is shown in Figure 7-27, "Deploy Service RequestsDeploy Which Requests."

Figure 7-27: Deploy Service Requests—Deploy Which Requests

Step 3 From the window in Figure 7-27, "Deploy Service RequestsDeploy Which Requests," choose which of the following you want to deploy:

Deploy all new service requests
Deploy selected service requests

Step 4 Click Next to continue.

If you selected Deploy selected service requests the next window to appear is as shown in Figure 7-28, "Deploy Service RequestsSelect Requests," and you should proceed to Step 5.

If you selected Deploy all new service requests, proceed to Step 7.

Figure 7-28: Deploy Service Requests—Select Requests

Step 5 From the window in Figure 7-28, "Deploy Service RequestsSelect Requests," choose one or more specific Service Request IDs.

Step 6 Click Next to continue.

Step 7 From the window in Figure 7-29, "Deploy Service RequestsSelect Audit Options," choose either of the following:

Generate audit reports
Do not generate audit reports

Figure 7-29: Deploy Service Requests—Select Audit Options

Step 8 Click Next to continue.

Step 9 In the next window, as shown in Figure 7-30, "Deploy Service RequestsSave," provide a unique Task Name.

Note From the drop-down menu, you can view the last 30 existing task names for this specific task type. This can facilitate the creation of a unique task name and the adherence to the existing task naming conventions.

From the drop-down list, you can highlight a similar task name to the one you want to create and then click on it. The name will appear in the Task Name field. Then you can edit the name to be a unique name. Otherwise, you can highlight Enter Name Here and enter a unique name in the Task Name field.

Figure 7-30: Deploy Service Requests—Save

Step 10 Click Next to continue.

Step 11 In the next window you can choose to schedule the task by selecting Yes and clicking Next. In this case, the next step is Step 12.

You can choose not to schedule the task by selecting No and clicking Next. In this case, the next step is Step 13.

Step 12 If you chose to schedule the task, in the next window, choose the scheduling directions and click Next. See Chapter 13, "Scheduling," for a detailed description of scheduling.

Step 13 If you did not schedule the task, you are informed that "The task manager is about to save the task." If you did schedule the task, you are informed that "The task manager is about to save and schedule the task." If you want to change your mind on the scheduling instructions, click Back and return to Step 11 or Step 12. When you are ready to save and schedule the task, click Next.

Step 14 You are informed that "All steps are done." Click Close to close the wizard.

View Deployment Log

This section explains how to view a deployment log.

To view the deployment log, implement the following step:

Step 1 From the VPN Console window, choose Provisioning > View Deployment Log, as shown in Figure 7-31, "View Deployment Log."

Figure 7-31: View Deployment Log

The window that appears is as shown in Figure 7-32, "Task Logs Information." This presently is the same information as when you navigate Tools > Task Logs. See the "Task Logs" section.

Figure 7-32: Task Logs Information

Export Service Request Configlets

This section explains how to export configlets to a directory.

To export Service Request configlets, implement the following steps:

Step 1 From the VPN Console window, choose Provisioning > Export Service Request Configlets, as shown in Figure 7-33, "Export Service Request Configlets."

Note An alternative to selecting Provisioning > Export Service Request Configlets is to select Tools > Tasks and then in the Actions menu item select New Task > Export Service Request Configlets and click Ok. Both paths navigate to the same set of wizards.

Figure 7-33: Export Service Request Configlets

The next window to appear is an Introduction that explains what occurs when taking this path.

Step 2 Click Next in the Introduction window to continue.

Figure 7-34: Export Service Request Configlets—Specify Output Directory

Step 3 From the window as shown in Figure 7-34, "Export Service Request ConfigletsSpecify Output Directory," in the field enter the output directory for the configlets.

Step 4 Click Next to continue.

Step 5 From the window as shown in Figure 7-35, "Export Service Request ConfigletsSpecify Type of Requests," select the button Specific requests or a button for one of the states: Pending; Invalid; Failed Deploy; Deployed; Broken; Functional; Lost; or Closed.

Figure 7-35: Export Service Request Configlets—Specify Type of Requests

Step 6 From the window as shown in Figure 7-36, "Export Service Request ConfigletsSelect Specific Requests," select one or more Service Requests.

Figure 7-36: Export Service Request Configlets—Select Specific Requests

Step 7 Click Next to continue.

The resulting window indicates completion and the name of the directory where the configuration files for the CE and PE reside.

Step 8 Click Close.

List All New Service Requests

This section explains how to get a report of all new Service Requests with the state of Requested.

To list all new Service Requests, implement the following step:

Step 1 From the VPN Console window, choose Provisioning > List All New Service Requests, as shown in Figure 7-37, "List All New Service Requests."

Figure 7-37: List All New Service Requests

An example of a report that lists new service requests is provided in Figure 7-38, "Sample New VPN Service Requests Report."

Figure 7-38: Sample New VPN Service Requests Report

For information within the List New Service Requests reports, first see the generic report fields and their explanations in Chapter 14, "Reports Overview." Additionally each report has a report-specific Results area and bottom task bar information, as shown in the following sections.

Results Area for List All Service Requests

The columns of information are as follows:

ID is the internal identification of the service request.
Type is the service request type. The valid values are: Add VPN Service; Modify VPN Service; Remove VPN Service.
State is the service request state. The only valid value is Requested.
PE Router is the name of the PE Router that is chosen when you create a service request.
CE Router is the name of the CE Router that is chosen when you create a service request.
Customer is the name of the customer to which the service request belongs.
VPN is the name of the VPN to which the service request belongs.
Created At is the time that the service request was created.
Last State Change is the time of the last state change.

Bottom Task Bar

The buttons are described from left to right as follows:

Request Details button. Click this button to get a Service Request Detail Report, as shown in Figure 7-39, "Example of Service Request Detail Report."
Provisioning button. Click this button to point to actions of what to do with Service Requests. Remove VPN Service to create a new Service Request to remove the selected Service Request; Modify VPN Service to bring up Service Request Modification to modify the Service Request; or Deploy VPN Service to call the servers to deploy the Service Request to the network

Note The system does not automatically purge Service Requests that have been removed (Remove VPN Service). These Service Requests are just marked as closed. To purge these closed Service Requests and therefore free up disk space, refer to the "Purge Closed Requests from Database" section.

Service Request Detail Report

The Service Request Detail Report contains the detailed information of a Service Request entered at creation time and/or at the process of Provisioning. An example of the Service Request Detail Report is shown in Figure 7-39, "Example of Service Request Detail Report."

Figure 7-39: Example of Service Request Detail Report

The buttons on the bottom task bar are described from left to right as follows:

Provisioning. Click this drop-down menu and then choose Remove VPN Service to create a new Service Request to remove the selected Service Request; Modify VPN Service to bring up Service Request Modification task to modify the Service Request; or Deploy VPN Service to call the servers to deploy the Service Request to the network.
Configlets. Click this button to produce a report that contains configlets that have been downloaded to PE and CE for Service Requests.
Audit Detail. Click this button to get audit information about this Service Request.
State History. Click this button to produce a report that contains the detailed history of state changes: each of the historical states of the chosen Service Request; the reason the Service Request changed for each state; and the time and date each state change occurred.
Prior Request. If the current Service Request was created to remove or modify a previous Service Request, this button is available. Click this button to see the replaced Service Request.

List All Service Requests

This section explains how to get a report of all Service Requests in the system.

To list all Service Requests, implement the following step:

Step 1 From the VPN Console window, choose Provisioning > List All Service Requests, as shown in Figure 7-40, "List All Service Requests."

Figure 7-40: List All Service Requests

An example of a report that lists all service requests is provided in Figure 7-41, "Sample All VPN Service Requests Report."

Figure 7-41: Sample All VPN Service Requests Report

For information within the List All Service Requests reports, first see the generic report fields and their explanations in Chapter 14, "Reports Overview." Additionally each report has a report-specific Results area and bottom task bar information, as shown in the following sections.

Results Area for List All Service Requests

The columns of information are as follows:

ID is the internal identification of the service request.
Type is the service request type. The valid values are: Add VPN Service; Modify VPN Service; Remove VPN Service.
State is the service request state. The valid values are: Requested; Pending; Invalid; Failed Deploy; Deployed; Broken; Functional; Lost; Closed.
PE Router is the name of the PE Router that is chosen when you create a service request.
CE Router is the name of the CE Router that is chosen when you create a service request.
Customer is the name of the customer to which the service request belongs.
VPN is the name of the VPN to which the service request belongs.
Created At is the time that the service request was created.
Last State Change is the time of the last state change.

Bottom Task Bar

The buttons are described from left to right as follows:

Request Details button. Click this button to get a Service Request Detail Report, as shown in Figure 7-42, "Example of Service Request Detail Report."
Provisioning button. Click this button to point to actions of what to do with Service Requests. Remove VPN Service to create a new Service Request to remove the selected Service Request; Modify VPN Service to bring up Service Request Modification to modify the Service Request; or Deploy VPN Service to call the servers to deploy the Service Request to the network

Service Request Detail Report

Figure 7-42: Example of Service Request Detail Report

The buttons on the bottom task bar are described from left to right as follows:

Provisioning. Click this drop-down menu and then choose Remove VPN Service to create a new Service Request to remove the selected Service Request; Modify VPN Service to bring up Service Request Modification task to modify the Service Request; or Deploy VPN Service to call the servers to deploy the Service Request to the network.
Configlets. Click this button to produce a report that contains configlets that have been downloaded to PE and CE for Service Requests.
Audit Detail. Click this button to get audit information about this Service Request.
State History. Click this button to produce a report that contains the detailed history of state changes: each of the historical states of the chosen Service Request; the reason the Service Request changed for each state; and the time and date each state change occurred.
Prior Request. If the current Service Request was created to remove or modify a previous Service Request, this button is available. Click this button to see the replaced Service Request.

Purge Closed Requests from Database

This section explains how to purge all closed Service Requests from the database.

Note This is a maintenance task to eliminate waste of disk space. This purges closed Service Requests to clean up the database

To purge closed requests from the database, implement the following steps:

Step 1 Before a Service Request can be purged, it must be in the closed state. If you want to place more Service Requests in the closed state, you can repeat the following steps for each Service Request:

a. Navigate to Provisioning > List All New Service Requests or Provisioning > List All Service Requests.

b. Select one Service Request.

c. From the bottom task bar, use the Provisioning drop-down menu, and choose Remove VPN Service.

d. Deploy the Service Request (refer to the "Deploy Service Requests" section).

e. Once the deployed Service Request goes to the pending state, you must audit the Service Request in order to close it (refer to Chapter 8, "VPN Console: Auditing Menu").

Step 2 From the VPN Console window, choose Provisioning > Purge Closed Requests from Database, as shown in Figure 7-43, "Purge Closed Requests from Database."

Figure 7-43: Purge Closed Requests from Database

Step 3 From the resulting window shown in Figure 7-44, "WarningPurging Service Requests," choose one of the following:

Yes Be very careful. This will purge all closed Service Requests from the database.
No This will cancel this procedure and not purge closed Service Requests from the database.

Figure 7-44: Warning—Purgin g Service Requests

Note Remove VPN Service is an option in the bottom task bar from Provisioning > List All New Service Requests or Provisioning > List All Service Requests. It is not available directly from the Provisioning menu task bar.

Table of Contents

VPN Console: Provisioning Menu