US 7,639,632 B2Grant
System and method for managing and provisioning virtual routers
Issue Date:2009-12-29
•24 Claims
•7 Drawing Sheets
Abstract
Site reachability information is determined for a service processing switch that is communicably coupled to one or more sites. In addition, global routing profiles, customer site profiles and OSPF profiles are defined. The profile data, in addition to or instead of the reachability information is used to generate routing configuration data for one or more Virtual Routers and Virtual Private Networks implemented within the service processing switch.
Metadata
Assignee
- Fortinet, Inc.
Inventors
- Manojit Sarkar
- Dileep Kumar
Application Information
Application Number:US 11/616,243
Filing Date:2006-12-26
Priority Date:2000-09-13
Art Unit:2475
Classifications
IPC:
H04L12/28
Patent Drawings (7 sheets)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a Divisional of application Ser. No. 09/663,485, filed on Sep. 13, 2000, now U.S. Pat. No. 7,272,643, which is hereby incorporated by reference for all purposes.
FIELD
[0002] The present invention relates generally to computer network routers, and more particularly to systems and methods of managing virtual routers.
COPYRIGHT NOTICE/PERMISSION
[0003] A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data described below and in the drawings hereto: Copyright® 2000-2006 Fortinet, Inc. All Rights Reserved.
BACKGROUND
[0004] The interest in the deployment of virtual private networks (VPNs) across IP backbone facilities is growing every-day. In general, VPNs fall into two categories: CPE-based (Customer Provided Equipment) VPNs and network-based VPNs.
[0005] With CPE-based VPNs, the ISP network provides only layer 2 connectivity to the customer. The CPE router takes ownership of setting up tunnels and handling routing with other sites. Network-based VPNs consist of a mesh of tunnels between ISP routers. They also have the routing capabilities required to forward traffic from each customer site. Each ISP router has a VPN-specific forwarding table that contains VPN member sites. The benefit offered by network-based VPNs is that the ISP is responsible for routing configuration and tunnel setup. In addition, other services, such as firewall, Quality of Service (QOS) processing, virus scanning, and intrusion detection can be handled by a small number of ISP routers. New services can be introduced and managed without the need to upgrade CPE devices.
[0006] There are typically three steps to building a VPN's infrastructure:
-
- [0007] 1) Define a topology and create tunnels using IPSec, LT2P, PPTP, GRE, or MPLS.
- [0008] 2) Configure routing on the edge routers to disseminate site- and intra-VPN reachability information.
- [0009] 3) Enable such services as firewall, QOS, and so forth.
[0010] Usually, IP network managers use the following model for building and maintaining their networks:
-
- [0011] 1) With the help of some network experts, design the network.
- [0012] 2) Use the command line interface (CLI) or ASCII configuration files to define the routing configuration.
- [0013] 3) Use trial-and-error method to determine a working solution for the network configuration.
- [0014] 4) Manually manage configuration files for routers.
[0015] The process of building or changing a network requires significant manual effort, and is slow, expensive, and error-prone. For ISPs that plan to provide VPN services, this model for provisioning VPNs is problematic. ISPs need to configure routing for VPNs, each of which can be considered separate networks.
[0016] As noted above, building and managing one network is difficult, the problem is made much worse when the ISP must build and manage thousands of networks. For ISPs to succeed at this, a facilitation framework is required.
[0017] As a result, there is a need in the art for the present invention.
SUMMARY
[0018] The above-mentioned shortcomings, disadvantages and problems are addressed by the present invention, which will be understood by reading and studying the following specification.
[0019] To enable ISPs to deliver services using service processing switches, systems and methods are provided that make provisioning VPNs very easy. The systems and methods described reduce the resources required to provision and manage a VPN network. For example, it is possible for ISPs to provision thousands of VPNs, each with a variety of services. The routing is a component of the VPN infrastructure.
[0020] In one embodiment of the invention, site reachability information is determined for a service processing switch that is communicably coupled to one or more sites. In addition, global routing profiles, customer site profiles and OSPF profiles are defined. The profile data, in addition to or instead of the reachability information is used to generate routing configuration data for one or more Virtual Routers and Virtual Private Networks implemented within the service processing switch.
[0021] The present invention describes systems, clients, servers, methods, and computer-readable media of varying scope. In addition to the aspects and advantages of the present invention described in this summary, further aspects and advantages of the invention will become apparent by reference to the drawings and by reading the detailed description that follows.
BRIEF DESCRIPTION OF THE DRAWINGS
[0022] FIG. 1 is a block diagram of the hardware and operating environment in which different embodiments of the invention can be practiced;
[0023] FIG. 2 is a diagram illustrating an exemplary Virtual Private Network used in embodiments of the invention;
[0024] FIG. 3 is a diagram illustrating further details segments of an exemplary Virtual Private Network used in embodiments of the invention;
[0025] FIG. 4 is a diagram illustrating Inter-VPN reachability; and
[0026] FIG. 5 is a diagram illustrating dynamic intra-VPN routing; and
[0027] FIG. 6 is a flowchart illustrating a method for provisioning a router configuration according to an embodiment of the invention.
DETAILED DESCRIPTION
[0028] In the following detailed description of exemplary embodiments of the invention, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific exemplary embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical and other changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense.
[0029] In the Figures, the same reference number is used throughout to refer to an identical component which appears in multiple Figures. Signals and connections may be referred to by the same reference number or label, and the actual meaning will be clear from its use in the context of the description.
[0030] The detailed description is divided into multiple sections. In the first section the hardware and operating environment of different embodiments of the invention is described. In the second section, the software environment of varying embodiments of the invention is described. In the final section, a conclusion is provided.
Hardware and Operating Environment
[0031] FIG. 1 is a diagram of the hardware and operating environment in conjunction with which embodiments of the invention may be practiced. The description of FIG. 1 is intended to provide a brief, general description of suitable computer routing hardware and a suitable computing environment in conjunction with which the invention may be implemented. Although not required, the invention is described in the general context of computer-executable instructions, such as program modules, being executed by a computer, such as a personal computer or a server computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types.
[0032] As shown in FIG. 1 , the system 100 includes a service processing switch 110, access routers 104, service management system 118, and customer network management system 106. In some embodiments, service processing switch 110 provides switching, routing and computing resources that can be allocated by a service provider to customers. In one embodiment, the service processing switch 110 is the IPSX 9000 service processing switch from CoSine Communications, Inc. However, the invention is not limited to any particular switch, router or service processing hardware.
[0033] Service processing switch can contain one or more blades 112. In some embodiments of the invention, blades 112 have a type associated with them. Examples of blade types include, processing functions such as network blades, control blades, trunk blades, and processor blades. Network blades provide interfaces to different types of networks. Control blades provide system management and accounting functions to the service processing system 110. Trunk blades provide access to high speed trunk networks. Processor blades provide general purpose computer processors that in some embodiments of the invention provide firewall, intrusion detection, or directory services. Blades are communicably coupled to one another, in one embodiment a packet ring is used to couple the blades.
[0034] In some embodiments, each of blades 112 includes one more processing elements 114. Processing elements 114 include CPU and memory that provide computing resources for the blade. The invention is not limited to any particular number of processing elements on a blade, nor is the invention limited to any particular number of blades in a service processing switch 110.
[0035] Service processing system 110 is typically communicably coupled to a network 116, for example the Internet. Network 116 can also be a Wide Area Network (WAN), a Local Area Network (LAN), or a private network.
[0036] Service processing system 110 is also typically communicably coupled to a plurality of customer networks 102 via customer access routers 104.
[0037] Service management system 118 hosts software that is used to configure and control the operation of service processing switch 110. In one embodiment of the invention, the service management system is a SPARC system available from Sun Microsystems, Inc. running the In Vision product from CoSine Communications, Inc. Service management system 118 can be used to allocate resources within service processing switch 110 to various customers. In one embodiment of the invention, service management system 118 communicates with service processing switch 110 using the Simple Network Management Protocol (SNMP). The operation of service management system 118 will be described in further detail in the sections that follow.
[0038] Customer network management system 106 hosts software that configures and controls the resources within service processing switch 110 that have been allocated to the particular customer. The operation of service management system 118 will be described in further detail in the sections that follow.
[0039] Those skilled in the art will appreciate that the invention may be practiced with other routing system hardware configurations besides those described above.
Software Environment
[0040] The embodiments of the invention include a software environment of systems and methods that provide a mechanism for simplifying the provisioning and management of VPN (Virtual Private Networks) and VRs (Virtual Routers) within a service processing switch. The embodiments of the invention provide a policy-based mechanism for network provisioning. Thus a service provider, for example, an ISP (Internet Service Provider), managing a service processing switch can create various service policies, which are used in defining VPN profiles. These profiles are used to automatically generate tunnels, routing, and other service configurations for VPNs. Resources within switch 110 such as blades and processing elements are allocated by a service provider to one or more customers, who then can configure those elements allocated to it. Configuration from the service provider's perspective, and from the customer's perspective can be driven based on profiles.
[0041] FIG. 2 provides an illustration of a VPN as used in various embodiments of the invention. A VPN is typically a logical grouping of virtual routers (VRs) 206. The connectivity between VPNs and customer sites 202 is provided by means of virtual interfaces (VIs). Users can create VIs and connect them to customer sites or to VIs of other VRs. The virtual connection can also be configured to be a tunnel interface (TI) to a type of secured tunnel, such as an IPSec tunnel. Customer sites can be connected via a network interface 204, which can be a leased line interface such as DS3. The invention is not limited to any particular type of network interface.
[0042] In some embodiments of the invention, two types of virtual routers are supported: Customer VRs and ISP VRs. Customer VRs are used to build customer VPNs, and ISP VRs are used to build ISP VPN. The ISP VPN is connected to an ISP backbone network 310 (FIG. 3 ). In this framework, each ISP needs only one ISP VPN. Customer VRs can be connected to the ISP VPN by means of VIs. Every virtual router can use one or more routing protocols, including STATIC, RIP, OSPF, and BGP, to disseminate reachability information. For routing purposes, every VPN based on this framework can be treated as an extension of the customer network.
[0043] The embodiments of the invention allow network managers to define profiles. The profile information is used to automatically generate the routing configuration for a VPN. In some embodiments, to profile the routing on a VPN, a customer VPN is divided into three segments, which are illustrated in FIG. 3 .
[0044] ISP-Edge segment 306 is a VPN segment that connects the VPN to customer sites. This segment includes all virtual interfaces connected to logical interfaces and tunnel interfaces whose remote end is outside the VPN. This segment is used for disseminating customer site reachability information.
[0045] Inside-VPN segment 304 (also referred to as an Intra-VPN segment) is a VPN segment that provides connectivity among different VRs 206. This segment is used to disseminate intra-VPN reachability information.
[0046] Inter-VPN segment 302 is a VPN segment that connects different types of VPNs; for example, the interfaces that connect a customer VPN with an ISP VPN.
[0047] It is desirable to identify segment types, because it provides a mechanism for generating profiles that can be optimized depending on the segment type.
Profile-Based Routing Configuration
[0048] FIG. 4 illustrates how the routing needs of the Inter-VPN segment 302 are taken care of at the time a VR is created. When a customer VR 206 is created, the user is given the option to automatically connect the VR with an ISP VR 308. At that time, service management system 118 (FIG. 1 ) also creates a default route 402 on the customer VR 206 and a static route 406 on the ISP VR 308, which accommodates customer VR 206 to ISP VR 308 connectivity. In this model, for all network address translation (NAT) addresses 404, the user must add static routes on the ISP VPN.
[0049] The profile discussed here takes care of the first two VPN segments: ISP-Edge 306 and Intra-VPN 304. Given a VPN's routing requirements, there are typically three routing aspects that are considered:
-
- [0050] 1) The routing protocol that should be turned on a virtual interface in a VR
- [0051] 2) When and how to redistribute routes between various routing protocols.
- [0052] 3) When enabling a routing protocol on a router or interface, the routing parameters to use for optimizing performance.
[0053] Service management system 118 (FIG. 1 ) uses VPN profile data to automatically generate the required routing configuration. In some embodiments of the invention BGP (Border Gateway Protocol) is excluded as a possible choice for configuring customer VPNs. There are a few reasons for this. First, there are only two cases in which BGP would be used in a VPN environment. ISP-VPNs might use BGP to talk to the Internet core. Also, if a VPN connects two very large customer sites, IBGP might be needed for the Intra-VPN segment to ensure scalability. There will generally be very few ISP VPNs (in most networks, there is only one), and it's unlikely that a VPN will be used to connect two or more large sites.
[0054] The second reason for excluding BGP from the profile is the VR-specific customization that is required to make BGP work in a VPN environment. Because BGP connects ISP VRs to the ISP core, a careful selection of export and import policies is needed to minimize the number of routes in each ISP VR. It is very difficult to represent this type of configuration by means of a generic routing profile. Service management system 118 (FIG. 1 ) provides an interface to configure BGP on VRs. This interface allows user to enable BGP on a VR, set its BGP neighbors, and add import and export policies.
[0055] In some embodiments of the invention, the profile defines a simple routing configuration, that is, static routing for the Intra-VPN segment. Thus static routing will be used to communicate with each customer site. This configuration is desirable because it puts a minimum load on the device, thus increasing the number of VPNs that can be managed by each service processing switch 110.
[0056] There are two issues with static routing. First, ISPs need to manage static routes for each customer. As new subnets are added to customer networks and old ones are removed, the static routes corresponding to these subnets should be added or removed in the corresponding VPNs. In some embodiments, this problem can be solved by having service management system 118 (FIG. 1 ) takes ownership of automatically managing static routes based on the customer site subnet information. In these cases, customers can directly add or remove subnet information using tools such as the customer network management system 106 (FIG. 1 ). This capability will transfer the ownership of managing routing to customers.
[0057] A second issue with static routing is that the routing by definition is STATIC. If a site interface is down, traffic cannot be re-routed to an alternate path. A partial solution to this problem can be provided by allowing customer to disable routing on a site that is down. This can be done by means of a customer network management system 106 (FIG. 1 ). In this scenario, service management system 118 (FIG. 1 ) would remove the static routes from the network that belongs to the site that is down. This action would allow the traffic to go through the backup path.
[0058] To resolve the two issues described above, the embodiments of the invention provide a mechanism for a user to choose more advanced routing options in profiles. For smaller sites, a viable option is RIP (Routing Information Protocol), while for large sites operators might choose OSPF (Open Shortest Path First gateway protocol). The dynamic routing transfers the burden of managing route changes from the network manager to the device. If a user selects dynamic routing at the edge, then the service management system will also have to use dynamic routing to disseminate Intra-VPN reachability information. FIG. 5 illustrates this scenario. If a site link to virtual router A 206.1 is down, virtual router B 206.2 will know that the traffic going through that link needs to be rerouted to virtual router C 206.3 only if dynamic routing is specified for Intra-VPN segment 504.
[0059] If all the sites (ISP-Edge segment) are using static or RIP routing, service management system 118 will allow the user to choose between RIP and OSPF for Intra-VPN routing. The user will typically select RIP if there are relatively few VRs in the VPN. Because OSPF is more scalable, it is a logical choice for bigger VPNs. If a user decides to run OSPF at a site edge, it is desirable to select OSPF for the Intra-VPN segment.
[0060] This section has described the various software components in a system that provides for the automatic generation and provisioning of routing configurations. As those of skill in the art will appreciate, the software can be written in any of a number of programming languages known in the art, including but not limited to C/C++, Java, Visual Basic, Smalltalk, Pascal, Ada and similar programming languages. The invention is not limited to any particular programming language for implementation.
Methods for Performing Profile-Based Routing Configuration
[0061] In the previous section, a system level overviews of the operation of exemplary embodiments of the invention were described. In this section, the particular methods of the invention performed by an operating environment executing an exemplary embodiment are described by reference to a flowchart shown in FIG. 6 . The methods to be performed by the operating environment constitute computer programs made up of computer-executable instructions. Describing the methods by reference to a flowchart enables one skilled in the art to develop such programs including such instructions to carry out the methods on suitable computers (the processor of the computer executing the instructions from computer-readable media). The method illustrated in FIG. 6 is inclusive of the acts required to be taken by an operating environment executing an exemplary embodiment of the invention.
[0062] The method begins at block 602 when a system executing the method learns, or discovers, the current routes to sites connected via the service processing switch 110 (FIG. 1 ). To build or include new sites in a VPN, each edge router must learn the routes to all sites connected to all the edges in the network. An edge in a network is a boundary between two routers, an edge router is a typically network device that routes data between one or more local area networks backbone network. Two components of routing information are typically needed for the VPN:
-
- [0063] 1) Site Reachability Information: Each edge router needs to learn the set of VPN addresses and address prefixes reachable at each site. The reachability information needed by the CPE (Customer Provided Equipment) router depends on site configuration. Customer sites are characterized into two categories: stub sites and non-stub sites. The CPE routers of stub sites have default routes pointing to an ISP edge router, while the CPE router of non-stub site do not, and therefor need to know the set of non-local destinations reachable via that link. Usually, if a VPN also provides Internet connectivity to a site and there is no backdoor connection between this and any other site, it is a stub site.
- [0064] 2) Intra-VPN Reachability Information: Once an edge router has learned the set of prefixes associated with each of its customer site's links, this information must be disseminated to each other router in the VPN.
[0065] After learning routes to sites, the system disseminates site reachability information (block 604). Various embodiments of the invention employ different mechanisms to disseminate the information. In one embodiment, static configuration is used. In static configuration, all the subnets associated with each customer site are manually configured into the VPN. To increase the manageability of this information, customer network management (CNM) 116 (FIG. 1 ) tools can be enhanced to allow customers to directly add and remove subnet information from the VPN. The subnet information can be used to automatically create the static routes in the VPN. In this case, the customer also needs to add static routes to the CPE routers of non-stub sites.
[0066] In an alternative embodiment, directory lookup is used to disseminate the site routing information. A central directory server can maintain the identities of edge routers associated with a VPN, and the set of customer site links bound to the VPN per edge router. Each edge router can query this information using some defined mechanism (for example, LDAP) upon startup. This mechanism requires some kind of database synchronization mechanism in order for all edge routers to learn the addition and deletion of sites from the VPN.
[0067] In a further alternative embodiment, a routing protocol can be run between the CPE edge router and the ISP edge router to exchange reachability information. This allows an ISP edge router to learn the prefixes that can be reached at a customer site, and enables a CPE router to learn the destinations that can be reached via the provider network.
[0068] In a still further embodiment, if a CPE router runs Multiprotocol Label Switching (MPLS), the MPLS LDP (Label Distribution Protocol) can be extended to convey the set of prefixes at each stub site, together with the appropriate labeling information.
[0069] In addition to the above, several mechanisms for Disseminating Intra-VPN Reachability Information can be used. In one embodiment employing static configuration, The service management system 118 can use the subnets configured for each site to automatically create static routes for dissemination of intra-VPN reachability information.
[0070] In an alternative embodiment, directory lookup information is used. In addition to VPN membership information, a central directory can maintain a listing of the address prefixes associated with each end point.
[0071] In a further alternative embodiment, each edge router runs an instance of a routing protocol on each VPN to disseminate intra-VPN reachability information. Using this mechanism, both full-mesh and arbitrary, VPN topologies can be easily supported.
[0072] A still further alternative embodiment uses a Link Reachability Protocol. Here each edge router can run a link reachability protocol carrying the necessary information. This protocol runs across the tunnel between the two edge routers. The two preferred choices for this approach are a variation of MPLS LDP and IBGP. The link reachability protocol-based schemes can support only fully meshed VPNs.
[0073] In yet a further alternative embodiment, site reachability information is disseminated by Piggybacking on IP Backbone Routing Protocols. The set of address prefixes associated with each stub interface can also be piggybacked into the routing advertisements from each edge router and propagated through the network. Other edge routers extract this information from received route advertisements. This scheme typically requires that intermediate routers cache intra-VPN routing information to propagate the data further. This also has implications for the level of security possible for intra-VPN routing information.
[0074] In addition to learning and disseminating site reachability information, a global routing profile can be defined (block 606). In one embodiment of the invention, the global routing profile includes the following parameters:
-
- [0075] a. Routing administration status
- [0076] b. Routing protocol for Intra-VPN segments
- [0077] c. Default routing protocol at the ISP edge. All the customer sites will generally inherit this.
- [0078] d. Default site type: stub or non-stub: Stub sites have a default route going toward the ISP VPN (Internet). For stub sites, there is no need to export routes from the VPN. This information is used in creating default export and import policies.
- [0079] e. If the routing protocol for the Intra-VPN segment is OSPF, define the OSPF profile topology type.
[0080] When a site is added, it inherits the routing configuration from the routing profile.
[0081] In addition, the system provides for the definition of a custom site profile (block 608) Multiple types of site information can be configured. First, if the site routing profile needs to be customized, the user may do so. Second, if a user wants static routing at the edge, the network subnets that are associated with the site must be provided. This configuration will allow the service management system to automatically create static routes. In one embodiment of the invention, the site profile contains following parameters:
-
- [0082] a. Routing Protocol at the ISP edge
- [0083] b. Site Type: stub or non-stub
- [0084] c. OSPF Area ID: If OSPF is enabled at the edge
- [0085] d. Site subnets.
[0086] In addition, a custom OSPF profile can be defined (block 610). When a user configures a routing profile, service management system 118 (FIG. 1 ) automatically generates OSPF, RIP, and static profiles, if needed. In many cases, the user will want to customize the generic OSPF profile. The user can customize the generated profile using a policy-based profile configuration workflow. The workflow includes the following features:
-
- [0087] 1) The user can define custom OSPF areas. He only needs to configure what VRs are included in what areas; Service management system 118 (
FIG. 1 ) generates the required configuration for each VR and VI. - [0088] 2) The user can define a route aggregation policy for an OSPF area; Service management system 118 (
FIG. 1 ) will auto-generate this configuration for all the VRs in that area. - [0089] 3) By default, Service management system 118 (
FIG. 1 ) generates one VR routing parameter policy, which applies to all VRs, and three VI routing parameter policies which apply to tunnel interfaces, customer site edges, and VI-VI connections. When routing configuration is generated, these policies are used to define routing parameters. The user can make changes in any of these policies, or create his own policies and assign them as defaults. The user also can define policies and set them to be applied on a set of VRs or VIs. Service management system 118 (FIG. 1 ) allows users to individually customize parameters for a VR or VI.
- [0087] 1) The user can define custom OSPF areas. He only needs to configure what VRs are included in what areas; Service management system 118 (
[0090] When configuring OSPF for intra-VPN segment, the service management system cannot use the same guidelines as those used in setting up a normal OSPF network, because each router in a VPN is a virtual router. To optimize performance, it is desirable to minimize the size of the routing table. This can be accomplished by keeping the OSPF areas small. In a normal OSPF network, the network manager would not let the size of an OSPF area grow beyond 50-60 routers. With a VPN, it is desirable to not let the OSPF area grow beyond 20-25 VRs. The larger the OSPF area, the higher the load on each VR, and hence the fewer the VRs that can be created on the service processing switch. As a result, it is not desirable to make a complete mesh of all the VRs in a large VPN. The user should use a custom OSPF topology and create areas of reasonable size to ensure scalability and stability of the OSPF network.
[0091] The system also provides for the definition of custom export/import policies (block 612). Using the router and site profile defined above, service management system 118 (FIG. 1 ) generates default policies necessary for different routing protocols to talk to each other. In some situations, custom export and import policies are needed to control access to critical networks. The system allows users to add custom export and import policies.
[0092] Based on the site reachability information and/or the global and custom profiles described above, the service management system generates routing configuration (block 614). Described below are items that are considered during the generation of the configuration:
-
- [0093] The user can only configure one protocol for the Intra-VPN segment. This configuration is used to configure the routing on all the interfaces that connect one VR to another in the same VPN. In most cases, this takes care of all tunnel interfaces.
- [0094] If the user selects static routing for a site, service management system 118 (
FIG. 1 ) will auto-generate one static route per site subnet on the local VR. If the routing for the Intra-VPN segment is also static, service management system 118 (FIG. 1 ) will also generate one static route per subnet on each remote VR. Auto-generation of static routes assumes a meshed-topology for the VPN. If the topology is not meshed, some additional configuration may be needed for the routing to work. - [0095] If select dynamic routing is selected for the Intra-VPN segment, service management system 118 (
FIG. 1 ) auto-generates export policies to disseminate site reachability information to other VRs. - [0096] For a non-stub site that is using dynamic routing to communicate with the VPN, service management system 118 (
FIG. 1 ) will create an export policy to inject all the routes learned from the Intra-VPN segment's routing into the customer network. - [0097] If the user selects a custom OSPF topology for the Intra-VPN segment, he does not have to explicitly assign an area ID for each interface. Service management system 118 (
FIG. 1 ) automatically interprets this information from the area configuration. - [0098] Once the profile is set, Service management system 118 (
FIG. 1 ) automatically handles the routing configuration for the addition and deletion of VRs and VIs. For example, if standard OSPF routing has been selected for the Intra-VPN segment, whenever the user creates an IPSec tunnel connecting two VRs, OSPF will be enabled with area ID 0.0.0.0. - [0099] If a VPN is using only one routing protocol for the Intra-VPN segment, service management system 118 (
FIG. 1 ) can discover routing profiles from the device configuration. - [0100] Service management system 118 (
FIG. 1 ) supports explicit two-phase provisioning of routing profile configurations. In the first phase, the user makes changes to the routing profile and saves them in the database. In the second phase, the user commits the profile to the network. In this phase, the server translates delta changes in the profile configuration into a required low-level configuration and pushes it to appropriate devices. - [0101] Service management system 118 (
FIG. 1 ) allows users to temporarily remove routing configurations from the device. Users can do this by providing administration status attributes for the routing profile. Setting this attribute to a “disabled” state and committing the profile removes configurations from the device. Routing can be turned on again by setting the admin status to “enabled.”
[0102] As can be seen from the above, the generated and customized policies can act as templates that can be applied to particular VPNs, particular VRs, or groups of VRs. For example, assume an existing policy has been changed or further customized. In one embodiment of the invention, the user is presented with a list of VRs or VPNs that were configured with the existing policy. The user can then select the VRs to which the new policy should be applied.
[0103] Similarly, assume that the user wishes to change the policy for a particular VR. In one embodiment of the invention, the user selects the desired VR, and then selects a new policy to be applied to the VR. The new policy can then be applied immediately, or it can be applied at a later scheduled time.
[0104] In addition, the policies can be used as a differentiator in providing VPN services. If user selects STATIC routing for ISP-Edge and Intra-VPN segments, the service processing switch does not need to run any routing instances per customer VR. On the other hand, if a user has chosen to run dynamic routing for Intra-VPN and ISP edge segments, the switch may have to run instances of routing protocols such as OSPF and RIP. Running routing instances on virtual routers consumes both processing power and memory on the processing elements and blades. The demand on the resources will depend on the size of VPN and its interaction with various customer sites. An ISP can recover the cost of the increased resource usage, by using routing as a differentiator in providing VPN services. There are few methods of providing services:
-
- [0105] 1) Allow user to select the routing protocol per site: STATIC, RIP, or OSPF. Based on the site configuration, ISP can automatically configure routing protocol for intra-VPN segment. The cost of the service should be the lowest for STATIC and the highest for OSPF.
- [0106] 2) Define a few fixed routing profiles and sell them as a part of service packages such as Gold, Silver, and Bronze. For instance, Gold will allow user to select OSPF for intra-VPN as well as ISP edge segment. Silver will allow user to configure OSPF for intra-VPN segment, while RIP for ISPF edge. The bronze package will permit customer to configure STATIC for ISP edge as well as Intra-VPN segment.
- [0107] 3) Provide additional services as part of a profile, For example, include firewall, intrusion detection, network address translation, proxy services, or other network services as part of a differentiated service package. The service can then be included in profiles defined as part of the service package, and excluded from profiles for customers that do not pay for the service.
CONCLUSION
[0108] Systems and methods for generating and provisioning router configurations are disclosed. The embodiments of the invention provide advantages over previous systems. For example, the embodiments of the invention provide a mechanism for easily and rapidly generating configuration information for large numbers of virtual routers and virtual private networks based on profiles. In addition, the embodiments of the invention separate the connectivity and routing needs of each VPN, thus significantly reduced the complexity of the network design. This separation also enables layering of advanced services to specific subscribers' networks. Visibility of subscriber services is end-to-end. The topology and routing needs of each VPN depend on the number and size of customer sites.
[0109] Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the present invention.
[0110] The terminology used in this application is meant to include all of these environments. It is to be understood that the above description is intended to be illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. Therefore, it is manifestly intended that this invention be limited only by the following claims and equivalents thereof.
Claims
What is claimed is:
1. A method comprising:
a service management system of a service provider causing a subset of processing resources of a plurality of processing elements of a service processing switch to be allocated among a plurality of customers of the service provider by establishing a plurality of virtual routers (VRs) and assigning a subset of the VRs to the plurality of customers;
the service management system provisioning the subset of VRs to support a plurality of customer virtual private networks (VPNs) for the plurality of customers by generating a routing configuration for each of the plurality of customer VPNs based on a set of site reachability data for sites of the plurality of customers that are communicatively coupled to the service processing switch;
receiving, at the service management system from a customer network management system associated with a customer of the plurality of customers, a custom routing profile for a VPN of the plurality of customer VPNs, the custom routing profile identifying one or more routing protocols to be used for one or more segments of the VPN; and
the service management system automatically reconfiguring the VPN by (i) programmatically generating appropriate routing configurations for associated customer VRs of the subset of the VRs based on site reachability data of the set of site reachability data associated with sites of the customer and the custom routing profile.
2. The method of claim 1, wherein the custom routing profile is based upon a global routing profile.
3. The method of claim 1, wherein the global routing profile includes a default routing protocol for a plurality of edge segments of the one or more segments of the customer VPN.
4. The method of claim 1, further comprising disseminating the site reachability data to other routers associated with the VPN.
5. The method of claim 4, wherein said disseminating the site reachability data comprises reading a set of subnets for one or more of the sites of the customer and creating static routes for the set of subnets.
6. The method of claim 4, wherein said disseminating the site reachability data comprises placing the site reachability information in a directory and providing access to the directory via Lightweight Directory Access Protocol (LDAP).
7. The method of claim 4, wherein said disseminating the site reachability data comprises use of a static configuration in which all subnets associated with the sites are manually configured into the VPN.
8. The method of claim 4, wherein said disseminating the site reachability data comprises exchanging the site reachability data via a routing protocol.
9. The method of claim 4, wherein said disseminating the site reachability data comprises conveying the site reachability data via Multiprotocol Label Switching Label Distribution Protocol (MPLS LDP).
10. The method of claim 4, wherein the custom routing profile comprises an Open Shortest Path First (OSPF) profile and wherein the OSPF profile includes a route aggregation policy.
11. The method of claim 4, wherein the custom routing profile includes parameters relating to one or more of Internet Protocol Security (IPSec), LT2P, Point-to-Point Tunneling Protocol (PPTP), Generic Route Encapsulation (GRE) protocol and Multiprotocol Label Switching (MPLS).
12. The method of claim 1, further comprising the service management system receiving an information identifying the associated customer VRs for which appropriate routing configurations are to be generated.
13. The method of claim 1, wherein the custom routing profile comprises information regarding one or more of a routing administration status, a default site type, and an Open Shortest Path First (OSPF) profile topology type.
14. A non-transitory computer-readable storage medium having tangibly embodied thereon instructions, which when executed by one or more computer processors of a service management system (SMS) of a service provider, cause a method to be performed comprising the following computer-implemented steps:
causing a subset of processing resources of a plurality of processing elements of a service processing switch to be allocated among a plurality of customers of the service provider by establishing a plurality of virtual routers (VRs) and assigning a subset of the VRs to the plurality of customers;
provisioning the subset of VRs to support a plurality of customer virtual private networks (VPNs) for the plurality of customers by generating a routing configuration for each of the plurality of customer VPNs based on a set of site reachability data for sites of the plurality of customers that are communicatively coupled to the service processing switch;
receiving, from a customer network management system associated with a customer of the plurality of customers, a custom routing profile for a VPN of the plurality of customer VPNs, the custom routing profile identifying one or more routing protocols to be used for one or more segments of the VPN; and
reconfiguring the VPN by (i) programmatically generating appropriate routing configurations for associated customer VRs of the subset of the VRs based on site reachability data of the set of site reachability data associated with sites of the customer and the custom routing profile.
15. The non-transitory computer-readable storage medium of claim 14, wherein the method further comprises disseminating the site reachability data to other routers associated with the VPN.
16. The non-transitory computer-readable storage medium of claim 15, wherein said disseminating the site reachability data comprises reading a set of subnets for one or more of the sites of the customer and creating static routes for the set of subnets.
17. The non-transitory computer-readable storage medium of claim 15, wherein said disseminating the site reachability data comprises placing the site reachability information in a directory and providing access to the directory via Lightweight Directory Access Protocol (LDAP).
18. The non-transitory computer-readable storage medium of claim 15, wherein said disseminating the site reachability data comprises use of a static configuration in which all subnets associated with the sites are manually configured into the VPN.
19. The non-transitory computer-readable storage medium of claim 15, wherein said disseminating the site reachability data comprises exchanging the site reachability data via a routing protocol.
20. The non-transitory computer-readable storage medium of claim 15, wherein said disseminating the site reachability data comprises conveying the site reachability data via Multiprotocol Label Switching Label Distribution Protocol (MPLS LDP).
21. The non-transitory computer-readable storage medium of claim 15, wherein the custom routing profile comprises an Open Shortest Path First (OSPF) profile and wherein the OSPF profile includes a route aggregation policy.
22. The non-transitory computer-readable storage medium of claim 15, wherein the custom routing profile includes parameters relating to one or more of Internet Protocol Security (IPSec), LT2P, Point-to-Point Tunneling Protocol (PPTP), Generic Route Encapsulation (GRE) protocol and Multiprotocol Label Switching (MPLS).
23. The non-transitory computer-readable storage medium of claim 14, wherein the custom routing profile comprises information regarding one or more of a routing administration status, a default site type, and an Open Shortest Path First (OSPF) profile topology type.
24. A service processing system comprising:
a service processing switch including a plurality of processing elements;
a service management system (SMS) of a service provider communicably coupled to the service processing switch and sites of a plurality of customers of the service provider, the SMS operable to:
provision the subset of VRs to support a plurality of customer virtual private networks (VPNs) for the plurality of customers by generating a routing configuration for each of the plurality of customer VPNs based on a set of site reachability data for the sites;
receive, from a customer network management system associated with a customer of the plurality of customers, a custom routing profile for a VPN of the plurality of customer VPNs, the custom routing profile identifying one or more routing protocols to be used for one or more segments of the VPN; and
reconfigure the VPN by (i) programmatically generating appropriate routing configurations for associated customer VRs of the subset of the VRs based on site reachability data of the set of site reachability data associated with sites of the customer and the custom routing profile.
Patent Citations (155)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4667287(A) | 1987-05-01 | Allen et al. | Applicant |
| US5473599(A) | 1995-12-01 | Li et al. | Applicant |
| US5490252(A) | 1996-02-01 | Macera et al. | Applicant |
| US5550816(A) | 1996-08-01 | Hardwick et al. | Applicant |
| US5581705(A) | 1996-12-01 | Passint et al. | Applicant |
| US5745778(A) | 1998-04-01 | Alfieri | Applicant |
| US5825772(A) | 1998-10-01 | Dobbins et al. | Examiner |
| US5841973(A) | 1998-11-01 | Kessler et al. | Applicant |
| US5841990(A) | 1998-11-01 | Picazo et al. | Applicant |
| US5875290(A) | 1999-02-01 | Bartfai et al. | Applicant |
| US5892924(A) | 1999-04-01 | Lyon et al. | Applicant |
| US5920705(A) | 1999-07-01 | Lyon et al. | Applicant |
| US5963555(A) | 1999-10-01 | Takase et al. | Applicant |
| US5964847(A) | 1999-10-01 | Booth et al. | Applicant |
| US6014669(A) | 2000-01-01 | Slaughter et al. | Applicant |
| US6047330(A) | 2000-04-01 | Stracke | Applicant |
| US6069895(A) | 2000-05-01 | Ayandeh | Applicant |
| US6098110(A) | 2000-08-01 | Witkowski et al. | Applicant |
| US6108699(A) | 2000-08-01 | Moiin | Applicant |
| US6169739(B1) | 2001-01-01 | Isoyama | Applicant |
| US6173399(B1) | 2001-01-01 | Gilbrech | Applicant |
| US6175867(B1) | 2001-01-01 | Taghadoss | Applicant |
| US6220768(B1) | 2001-04-01 | Barroux | Applicant |
| US6226788(B1) | 2001-05-01 | Schoening et al. | Applicant |
| US6243580(B1) | 2001-06-01 | Garner | Applicant |
| US6256295(B1) | 2001-07-01 | Callon | Applicant |
| US6260072(B1) | 2001-07-01 | Rodriguez | Applicant |
| US6260073(B1) | 2001-07-01 | Walker et al. | Applicant |
| US6266695(B1) | 2001-07-01 | Huang et al. | Applicant |
| US6286038(B1) | 2001-09-01 | Reichmeyer et al. | Examiner |
| US6295297(B1) | 2001-09-01 | Lee | Applicant |
| US6298130(B1) | 2001-10-01 | Galvin | Applicant |
| US6317748(B1) | 2001-11-01 | Menzies et al. | Applicant |
| US6330602(B1) | 2001-12-01 | Law et al. | Applicant |
| US6338092(B1) | 2002-01-01 | Chao et al. | Applicant |
| US6405262(B1) | 2002-06-01 | Vogel et al. | Applicant |
| US6414595(B1) | 2002-07-01 | Scrandis et al. | Applicant |
| US6434619(B1) | 2002-08-01 | Lim et al. | Applicant |
| US6438612(B1) | 2002-08-01 | Ylonen et al. | Applicant |
| US6449650(B1) | 2002-09-01 | Westfall et al. | Applicant |
| US6453406(B1) | 2002-09-01 | Sarnikowski et al. | Applicant |
| US6459682(B1) | 2002-10-01 | Ellesson et al. | Applicant |
| US6463061(B1) | 2002-10-01 | Rekhter et al. | Applicant |
| US6466976(B1) | 2002-10-01 | Alles et al. | Applicant |
| US6493349(B1) | 2002-12-01 | Casey | Applicant |
| US6496935(B1) | 2002-12-01 | Fink et al. | Applicant |
| US6526056(B1) | 2003-02-01 | Rekhter et al. | Applicant |
| US6532088(B1) | 2003-03-01 | Dantu et al. | Applicant |
| US6542515(B1) | 2003-04-01 | Kumar et al. | Applicant |
| US6553423(B1) | 2003-04-01 | Chen | Applicant |
| US6556544(B1) | 2003-04-01 | Lee | Applicant |
| US6611498(B1) | 2003-08-01 | Baker et al. | Applicant |
| US6611522(B1) | 2003-08-01 | Zheng et al. | Applicant |
| US6625169(B1) | 2003-09-01 | Tofano | Applicant |
| US6631519(B1) | 2003-10-01 | Nicholson et al. | Applicant |
| US6636516(B1) | 2003-10-01 | Yamano | Applicant |
| US6639897(B1) | 2003-10-01 | Shiomoto et al. | Applicant |
| US6658013(B1) | 2003-12-01 | de Boer et al. | Applicant |
| US6668282(B1) | 2003-12-01 | Booth et al. | Applicant |
| US6697360(B1) | 2004-02-01 | Gai et al. | Applicant |
| US6738371(B1) | 2004-05-01 | Ayres | Applicant |
| US6738821(B1) | 2004-05-01 | Wilson et al. | Applicant |
| US6763236(B2) | 2004-07-01 | Siren | Applicant |
| US6769124(B1) | 2004-07-01 | Schoening et al. | Applicant |
| US6775267(B1) | 2004-08-01 | Kung et al. | Applicant |
| US6775284(B1) | 2004-08-01 | Calvignac et al. | Applicant |
| US6778502(B2) | 2004-08-01 | Ricciulli | Applicant |
| US6807181(B1) | 2004-10-01 | Weschler | Applicant |
| US6816462(B1) | 2004-11-01 | Booth et al. | Applicant |
| US6856676(B1) | 2005-02-01 | Pirot et al. | Applicant |
| US6883170(B1) | 2005-04-01 | Garcia | Applicant |
| US6894994(B1) | 2005-05-01 | Grob et al. | Applicant |
| US6907039(B2) | 2005-06-01 | Shen | Applicant |
| US6922774(B2) | 2005-07-01 | Meushaw et al. | Applicant |
| US6959194(B2) | 2005-10-01 | Brouwer et al. | Applicant |
| US6982987(B2) | 2006-01-01 | Asayesh | Applicant |
| US6985956(B2) | 2006-01-01 | Luke et al. | Applicant |
| US6990103(B1) | 2006-01-01 | Gollamudi | Applicant |
| US7028333(B2) | 2006-04-01 | Tuomenoksa et al. | Applicant |
| US7042843(B2) | 2006-05-01 | Ni | Applicant |
| US7054311(B2) | 2006-05-01 | Norman et al. | Applicant |
| US7062642(B1) | 2006-06-01 | Langrind et al. | Applicant |
| US7068656(B2) | 2006-06-01 | Sainomoto et al. | Applicant |
| US7082477(B1) | 2006-07-01 | Sadhasivam et al. | Applicant |
| US7089293(B2) | 2006-08-01 | Grosner et al. | Applicant |
| US7096383(B2) | 2006-08-01 | Talaugon | Applicant |
| US7096495(B1) | 2006-08-01 | Warrier et al. | Applicant |
| US7111072(B1) | 2006-09-01 | Matthews | Applicant |
| US7116665(B2) | 2006-10-01 | Balay | Applicant |
| US7159031(B1) | 2007-01-01 | Larkin | Applicant |
| US7159035(B2) | 2007-01-01 | Garcia-Luna-Aceves et al. | Applicant |
| US7161904(B2) | 2007-01-01 | Hussain | Applicant |
| US7174372(B1) | 2007-02-01 | Sarkar | Examiner |
| US7177311(B1) | 2007-02-01 | Hussain | Applicant |
| US7181547(B1) | 2007-02-01 | Millet | Applicant |
| US7181766(B2) | 2007-02-01 | Bendinelli et al. | Applicant |
| US7187676(B2) | 2007-03-01 | DiMambro | Applicant |
| US7197553(B2) | 2007-03-01 | Roberts et al. | Applicant |
| US7203192(B2) | 2007-04-01 | Desai | Applicant |
| US7221945(B2) | 2007-05-01 | Milford et al. | Applicant |
| US7225259(B2) | 2007-05-01 | Ho et al. | Applicant |
| US7263106(B2) | 2007-08-01 | Matthews | Applicant |
| US7266120(B2) | 2007-09-01 | Cheng | Applicant |
| US7272643(B1) | 2007-09-01 | Sarkar et al. | Examiner |
| US7278055(B2) | 2007-10-01 | Talaugon | Applicant |
| US7313614(B2) | 2007-12-01 | Considine et al. | Applicant |
| US7316029(B1) | 2008-01-01 | Parker et al. | Applicant |
| US7324489(B1) | 2008-01-01 | Iyer | Applicant |
| US7337221(B2) | 2008-02-01 | Radi et al. | Applicant |
| US7340535(B1) | 2008-03-01 | Alam | Applicant |
| US7376125(B1) | 2008-05-01 | Hussain | Applicant |
| US7376827(B1) | 2008-05-01 | Jiao | Applicant |
| US7386010(B2) | 2008-06-01 | Solomon et al. | Applicant |
| US7389358(B1) | 2008-06-01 | Matthews | Applicant |
| US2001/0024425(A1) | 2001-09-01 | Tsunoda et al. | Applicant |
| US2001/0028636(A1) | 2001-10-01 | Skog et al. | Applicant |
| US2001/0034733(A1) | 2001-10-01 | Prompt et al. | Applicant |
| US2001/0043571(A1) | 2001-11-01 | Jang et al. | Applicant |
| US2001/0048661(A1) | 2001-12-01 | Clear et al. | Applicant |
| US2001/0052013(A1) | 2001-12-01 | Munguia et al. | Applicant |
| US2002/0071389(A1) | 2002-06-01 | Seo | Applicant |
| US2002/0150093(A1) | 2002-10-01 | Ott et al. | Applicant |
| US2002/0150114(A1) | 2002-10-01 | Sainomoto et al. | Applicant |
| US2002/0152373(A1) | 2002-10-01 | Sun | Applicant |
| US2003/0012209(A1) | 2003-01-01 | Abdelilah et al. | Applicant |
| US2003/0033401(A1) | 2003-02-01 | Poisson et al. | Applicant |
| US2003/0063590(A1) | 2003-04-01 | Mohan et al. | Applicant |
| US2003/0108041(A1) | 2003-06-01 | Aysan et al. | Applicant |
| US2003/0169747(A1) | 2003-09-01 | Wang | Applicant |
| US2003/0185221(A1) | 2003-10-01 | Deikman et al. | Applicant |
| US2003/0212735(A1) | 2003-11-01 | Hicok et al. | Applicant |
| US2004/0006601(A1) | 2004-01-01 | Bernstein et al. | Applicant |
| US2004/0078772(A1) | 2004-04-01 | Balay | Applicant |
| US2004/0095932(A1) | 2004-05-01 | Astarabadi et al. | Applicant |
| US2004/0095934(A1) | 2004-05-01 | Cheng et al. | Applicant |
| US2004/0160900(A1) | 2004-08-01 | Lund et al. | Applicant |
| US2004/0199567(A1) | 2004-10-01 | Lund | Applicant |
| US2004/0199568(A1) | 2004-10-01 | Lund | Applicant |
| US2004/0199569(A1) | 2004-10-01 | Kalkunte et al. | Applicant |
| US2005/0047407(A1) | 2005-03-01 | Desai | Applicant |
| US2005/0213589(A1) | 2005-09-01 | Shih | Applicant |
| US2006/0265519(A1) | 2006-11-01 | Millet | Applicant |
| US2007/0058648(A1) | 2007-03-01 | Millet | Applicant |
| US2007/0064704(A1) | 2007-03-01 | Balay | Applicant |
| US2007/0073733(A1) | 2007-03-01 | Matthews | Applicant |
| US2007/0083528(A1) | 2007-04-01 | Matthews | Applicant |
| US2007/0109968(A1) | 2007-05-01 | Hussain | Applicant |
| US2007/0110062(A1) | 2007-05-01 | Balay | Applicant |
| US2007/0121579(A1) | 2007-05-01 | Matthews | Applicant |
| US2007/0127382(A1) | 2007-06-01 | Hussain | Applicant |
| US2007/0147368(A1) | 2007-06-01 | Desai | Applicant |
| US2007/0291755(A1) | 2007-12-01 | Cheng | Applicant |
| US2008/0013470(A1) | 2008-01-01 | Kopplin | Applicant |
| US2008/0016389(A1) | 2008-01-01 | Talaugon | Applicant |
| US2008/0117917(A1) | 2008-05-01 | Balay | Applicant |
Non-Patent Literature (156)
- Notice of Allowance dated Dec. 1, 2004 for U.S. Appl. No. 09/661,636.Applicant
- Amendment and Response filed on Sep. 2, 2004 for U.S. Appl. No. 09/661,636.Applicant
- Office Action dated May 28, 2004 for U.S. Appl. No. 09/661,636.Applicant
- Amendment and Response filed on Mar. 22, 2004 for U.S. Appl. No. 09/661,636.Applicant
- Office Action dated Nov. 18, 2003 U.S. Appl. No. 09/661,636.Applicant
- Amendment and Response filed on Apr. 29, 2007 for U.S. Appl. No. 09/661,130.Applicant
- Office Action dated Dec. 28, 2006 for U.S. Appl. No. 09/661,130.Applicant
- Amendment and Response filed on Mar. 6, 2006 for U.S. Appl. No. 09/661,130.Applicant
- Office Action dated Oct. 18, 2004 for U.S. Appl. No. 09/661,130.Applicant
- Amendment and Response filed on Apr. 9, 2004 for U.S. Appl. No. 09/661,130.Applicant
- Office Action dated Nov. 5, 2003 for U.S. Appl. No. 09/661,130.Applicant
- Notice of Allowance dated Jun. 14, 2007 for U.S. Appl. No. 10/067,106.Applicant
- Amendment and Response filed on Mar. 10, 2007 for U.S. Appl. No. 10/067,106.Applicant
- Office Action dated Nov. 16, 2006 for U.S. Appl. No. 10/067,106.Applicant
- Amendment and Response filed on Aug. 28, 2006 for U.S. Appl. No. 10/067,106.Applicant
- Office Action dated Mar. 27, 2006 for U.S. Appl. No. 10/067,106.Applicant
- Amendment and Response filed on Nov. 6, 2006 for U.S. Appl. No. 09/663,483.Applicant
- Office Action dated Jul. 6, 2006 for U.S. Appl. No. 09/663,483.Applicant
- Amendment and Response filed on Mar. 13, 2006 for U.S. Appl. No. 09/663,483.Applicant
- Advisory Action dated Nov. 12, 2004 for U.S. Appl. No. 09/663,483.Applicant
- Amendment and Response filed on Oct. 8, 2004 for U.S. Appl. No. 09/663,483.Applicant
- Office Action dated Jun. 3, 2004 for U.S. Appl. No. 09/663,483.Applicant
- Amendment and Response filed on Feb. 26, 2004 for U.S. Appl. No. 09/663,483.Applicant
- Office Action dated Aug. 21, 2003 for U.S. Appl. No. 09/663,483.Applicant
- Amendment and Response filed on Mar. 13, 2006 for U.S. Appl. No. 09/952,520.Applicant
- Office Action dated Mar. 14, 2005 for U.S. Appl. No. 09/952,520.Applicant
- Notice of Allowance dated Jul. 30, 2007 for U.S. Appl. No. 09/663,485.Applicant
- Amendment and Response filed on Jun. 11, 2007 for U.S. Appl. No. 09/663,485.Applicant
- Office Action dated Jan. 11, 2007 for U.S. Appl. No. 09/663,485.Applicant
- Amendment and Response filed on Aug. 28, 2006 for U.S. Appl. No. 09/663,485.Applicant
- Office Action dated Jul. 26, 2007 for U.S. Appl. No. 09/663,485.Applicant
- Amendment and Response filed on Feb. 2, 2006 for U.S. Appl. No. 09/663,485.Applicant
- Office Action dated Dec. 21, 2004 for U.S. Appl. No. 09/663,485.Applicant
- Amendment and Response filed on Nov. 16, 2004 for U.S. Appl. No. 09/663,485.Applicant
- Office Action dated May 14, 2004 for U.S. Appl. No. 09/663,485.Applicant
- Amendment and Response filed on Mar. 15, 2004 for U.S. Appl. No. 09/663,485.Applicant
- Office Action dated Sep. 8, 2003 for U.S. Appl. No. 09/663,485.Applicant
- Office Action dated Aug. 8, 2007 for U.S. Appl. No. 09/663,457.Applicant
- Amendment and Response filed on Jul. 11, 2007 for U.S. Appl. Serial No. 09/663,457.Applicant
- Office Action dated May 17, 2007 for U.S. Appl. No. 09/663,457.Applicant
- Amendment and Response filed on Oct. 2, 2006 for U.S. Appl. No. 09/663,457.Applicant
- Office Action dated Apr. 22, 2005 for U.S. Appl. No. 09/663,457.Applicant
- Office Action dated Aug. 27, 2004 for U.S. Appl. No. 09/663,457.Applicant
- Amendment and Response filed on Jun. 21, 2004 for U.S. Appl. No. 09/663,457.Applicant
- Office Action dated Dec. 11, 2003 for U.S. Appl. No. 09/663,457.Applicant
- Notice of Allowance dated Nov. 21, 2006 for U.S. Appl. No. 09/663,484.Applicant
- Amendment and Response filed on Aug. 24, 2006 for U.S. Appl. No. 09/663,484.Applicant
- Office Action dated Feb. 24, 2006 for U.S. Appl. No. 09/663,484.Applicant
- Amendment and Response filed on Feb. 7, 2006 for U.S. Appl. No. 09/663,484.Applicant
- Office Action dated Apr. 6, 2005 for U.S. Appl. No. 09/663,484.Applicant
- Office Action dated Aug. 1, 2007 for U.S. Appl. No. 10/163,260.Applicant
- Amendment and Response filed on May 23, 2007 for U.S. Appl. No. 10/163,260.Applicant
- Office Action dated Apr. 13, 2007 for U.S. Appl. No. 10/163,260.Applicant
- Amendment and Response filed on Mar. 13, 2007 for U.S. Appl. No. 10/163,260.Applicant
- Office Action dated Dec. 21, 2006 for U.S. Appl. No. 10/163,260.Applicant
- Amendment and Response filed on Sep. 18, 2006 for U.S. Appl. No. 10/163,260.Applicant
- Office Action dated May 18, 2006 for U.S. Appl. No. 10/163,260.Applicant
- Office Action dated Aug. 22, 2007 for U.S. Appl. No. 10/650,298.Applicant
- Response to Restriction Requirement Apr. 26, 2004 for U.S. Appl. No. 09/663,483.Applicant
- Restriction Requirement dated Mar. 22, 2004 for U.S. Appl. No. 09/663,483.Applicant
- Office Action dated Sep. 11, 2007 for U.S. Appl. No. 09/661,637.Applicant
- Amendment and Response filed on Jun. 20, 2007 for U.S. Appl. No. 09/661,637.Applicant
- Office Action dated Feb. 8, 2007 for U.S. Appl. No. 09/661,637.Applicant
- Amendment and Response filed on Mar. 6, 2006 for U.S. Appl. No. 09/661,637.Applicant
- Office Action dated Dec. 23, 2004 for U.S. Appl. No. 09/661,637.Applicant
- Amendment and Response filed on Aug. 5, 2004 for U.S. Appl. No. 09/661,637.Applicant
- Office Action dated May 5, 2004 for U.S. Appl. No. 09/661,637.Applicant
- Supplemental Amendment and Response filed on Sep. 17, 2007, 2007 for U.S. Appl. No. 09/663,457.Applicant
- Non-Final Office Office for U.S. Appl. No. 11/671,462, mailed Oct. 8, 2008.Applicant
- Restriction Requirement for U.S. Appl. No. 10/949,943, mailed Oct. 20, 2008.Applicant
- Non-Final Office Action for U.S. Appl. No. 11/556,697, dated Jul. 9, 2008.Applicant
- Restriction Requirement for U.S. Appl. No. 10/991,970, dated Jul. 15, 2008.Applicant
- Non-Final Office Action for U.S. Appl. No. 09/663,457, dated Jul. 15, 2008.Applicant
- Non-Final Office Action for U.S. Appl. No. 09/952,520, dated May 30, 2008.Applicant
- Advisory Action for U.S. Appl. No. 09/663,483, dated Apr. 11, 2008.Applicant
- Fowler, D., “VPNs Become a Virtual Reality.” Netnews, Apr./May 1998. pp. 1-4.Applicant
- Chan, Mun C. et al., “An architecture for broadband virtual networks under customer control.” IEEE Network Operations and Management Symposium. Apr. 1996. pp. 135-144.Applicant
- Chan, Mun C. et al “Customer Management and Control of Broadband VPN Services.” Proc. Fifth IFIP/IEEE International Symposium of Integrated Network Management. May 1997. pp. 301-314.Applicant
- Gasparro, D.M., “Next-Gen VPNs: The Design Challenge.” Data Communications. Sep. 1999. pp. 83-95.Applicant
- Hanaki, M. et al., “LAN/WAN management integration using ATM CNM interface.” IEEE Network Operations Management Symposium, vol. 1. Apr. 1996. pp. 12-21.Applicant
- Kapustka, S., “CoSine Communications Move VPNs ‘Into the Cloud’ with the Leading Managed IP Service Delivery Platform.” http://wwwcosinecom.com/news/pr—5—24.html. Press Release, CoSine Communications. 1995. p. 5.Applicant
- Keshav, S., “An Engineering Approach to Computer Networking: ATM networks, the internet, and the telephone network.” Reading Mass: Addison-Wesley, Addison-Wesley Professional Computing Series. 1992. pp. 318-324.Applicant
- Kim, E.C. et al., “The Multi-Layer VPN Management Architecture.” Proc. Sixth IFIP/IEEE International Symposium on Integrated Network Management. May 1999. pp. 187-200.Applicant
- Rao, J.R., Intranets and VPNs: Strategic Approach. 1988 Annual Review of Communications. 1998. pp. 669-674.Applicant
- Tanenbaum, A.S., “Computer Networks.” Upper Saddle River, N.J.: Prentice Hall PTR, 3rd Edition. 1996. pp. 348-364.Applicant
- European Search Report for PCT/US03/37009 (Jul. 4, 2009) 2 pgs.Applicant
- International Search Report for PCTUS03/17674. 6 pgs.Applicant
- A Lightweight Protocol for Interconnecting Heterogenous Devices in Dynamic Environments, (c) 1999, obtained from the Internet at: http//ieeexplore.ieee.org/iel5/6322/16898/00778477.pdf.Applicant
- The Guide to Computing Literature, Jairo A: A Framework and Lightweight Protocol for Multimedia Network Management, vol. 8, Issue 1, published 2000, ISSN: 1064-7570.Applicant
- Bookfinder4u.com: High Performance Networks By Ahmed N. Tantawy, ISBN-10: 0792393716, Published 1993, Lightweight Protocols.Applicant
- ipinfusion white paper: Virtual Routing for Provider Edge application, obtained from the Internet at: http://www. ipinfusion.com/pdf/VirtualRouting—app-note—3rev0302.pdf, pp. 1-8.Applicant
- Non-Final Office Action for U.S. Appl. No. 10/991,969, dated Feb. 20, 2008.Applicant
- Non-Final Office Action for U.S. Appl. No. 10/273,669, dated Feb. 20, 2008.Applicant
- Non-Final Office Action for U.S. Appl. No. 10/949,943, dated Feb. 14, 2008.Applicant
- Restriction Requirement for U.S. Appl. No. 11/556,697, dated Feb. 13, 2008.Applicant
- Lawrence, J. Lang et al.“Connecting Remote FDDI Installations with Single-Mode Fiber, Dedicated Lines, or SMDS.” Jul. 1990; ACM SIGCOMM Computer Communication Review. vol. 20, Issue 3; pp. 72-82.Applicant
- IEEE Potentials Publication; “Local Area Networks” Dec. 95/Jan. 96; pp. 6. http://www.ece.uc.edu/-paw/potentials/sample.Applicant
- Office Action dated Oct. 18, 2007 for U.S. Appl. No. 09/663,483.Applicant
- Office Action dated Oct. 16, 2007 for U.S. Appl. No. 09/661,130.Applicant
- Office Action dated Nov. 28, 2007 for U.S. Appl. No. 09/952,520.Applicant
- Amendment and Response filed on Nov. 12, 2004 for U.S. Appl. No. 09/663,484.Applicant
- Office Action dated May 6, 2004 for U.S. Appl. No. 09/663,484.Applicant
- Amendment and Response filed on Feb. 18, 2004 for U.S. Appl. No. 09/663,484.Applicant
- Office Action dated Aug. 12, 2003 for U.S. Appl. No. 09/663,484.Applicant
- Notice of Allowance dated Jan. 4, 2007 for U.S. Appl. No. 09/894,471.Applicant
- Amendment and Response filed on Nov. 2, 2006 for U.S. Appl. No. 09/894,471.Applicant
- Office Action dated Oct. 26, 2006 for U.S. Appl. Serial No. 09/894,471.Applicant
- Amendment and Response filed on Mar. 10, 2006 for U.S. Appl. No. 09/894,471.Applicant
- Office Action dated Dec. 14, 2004 for U.S. Appl. No. 09/894,471.Applicant
- Notice of Allowance dated Nov. 7, 2006 for U.S. Appl. No. 09/771,346.Applicant
- Amendment and Response filed on Oct. 18, 2006 for U.S. Appl. No. 09/771,346.Applicant
- Office Action dated Jul. 18, 2006 for U.S. Appl. No. 09/771,346.Applicant
- Amendment and Response filed on Mar. 13, 2006 for U.S. Appl. No. 09/771,346.Applicant
- Office Action dated Jan. 25, 2005 for U.S. Appl. No. 09/771,346.Applicant
- Amendment and Response filed on Oct. 14, 2004 for U.S. Appl. No. 09/771,346.Applicant
- Office Action dated Mar. 26, 2004 for U.S. Appl. No. 09/771,346.Applicant
- Notice of Allowance dated Nov. 19, 2006 for U.S. Appl. No. 10/163,162.Applicant
- Amendment and Response filed on Aug. 5, 2006 for U.S. Appl. No. 10/163,162.Applicant
- Office Action dated May 5, 2006 for U.S. Appl. No. 10/163,162.Applicant
- Notice of Allowance dated Jan. 4, 2007 for U.S. Appl. No. 10/163,261.Applicant
- Amendment and Response filed on Nov. 9, 2006 for U.S. Appl. No. 10/163,261.Applicant
- Office Action dated Nov. 3, 2006 for U.S. Appl. No. 10/163,261.Applicant
- Amendment and Response filed on Aug. 22, 2006 for U.S. Appl. No. 10/163,261.Applicant
- Office Action dated May 22, 2006 for U.S. Appl. No. 10/163,261.Applicant
- Notice of Allowance dated Jul. 27, 2006 for U.S. Appl. No. 10/163,073.Applicant
- Office Action dated May 30, 2007 for U.S. Appl. No. 10/273,669.Applicant
- Amendment and Response filed on Mar. 9, 2007 for U.S. Appl. No. 10/273,669.Applicant
- Office Action dated Sep. 21, 2006 for U.S. Appl. No. 10/273,669.Applicant
- Amendment and Response filed on Jun. 21, 2006 for U.S. Appl. No. 10/273,669.Applicant
- Office Action dated Feb. 21, 2006 for U.S. Appl. No. 10/273,669.Applicant
- Notice of Allowance dated Aug. 14, 2007 for U.S. Appl. No. 10/163,071.Applicant
- Amendment and Response filed on Jul. 17, 2007 for U.S. Appl. No. 10/163,071.Applicant
- Office Action dated Jul. 3, 2007 for U.S. Appl. No. 10/163,071.Applicant
- Amendment and Response filed on May 6, 2007 for U.S. Appl. No. 10/163,071.Applicant
- Office Action dated Nov. 7, 2006 for U.S. Appl. No. 10/163,071.Applicant
- Amendment and Response filed on Sep. 1, 2006 for U.S. Appl. No. 10/163,071.Applicant
- Office Action dated Jun. 1, 2006 for U.S. Appl. No. 10/163,071.Applicant
- Amendment and Response filed on Mar. 6, 2006 for U.S. Appl. No. 10/163,071.Applicant
- Office Action dated Dec. 2, 2005 for U.S. Appl. No. 10/163,071.Applicant
- Notice of Allowance dated Nov. 29, 2006 for U.S. Appl. No. 10/163,079.Applicant
- Amendment and Response filed on Nov. 1, 2006 for U.S. Appl. No. 10/163,079.Applicant
- Office Action dated Oct. 27, 2006 for U.S. Appl. No. 10/163,079.Applicant
- Amendment and Response filed on Aug. 17, 2006 for U.S. Appl. No. 10/163,079.Applicant
- Office Action dated May 17, 2006 for U.S. Appl. No. 10/163,079.Applicant
- Notice of Allowance dated Jul. 17, 2007 for U.S. Appl. No. 10/298,815.Applicant
- Amendment and Response filed on Mar. 9, 2007 for U.S. Appl. No. 10/298,815.Applicant
- Office Action dated Feb. 23, 2007 for U.S. Appl. No. 10/298,815.Applicant
- Notice of Allowance dated Jun. 27, 2005 for U.S. Appl. No. 10/232,979.Applicant
- Notice of Allowance dated Jul. 05, 2007 for U.S. Appl. No. 11/466,098.Applicant
- Amendment and Response filed on Aug. 10, 2007 for U.S. Appl. No. 10/163,260.Applicant
- Final Office Action for U.S. Appl. No. 10/650,298, mailing date Sep. 3, 2008.Applicant
- Final Office Action for U.S. Appl. No. 10/991,969, mailing date Sep. 22, 2008.Applicant
- Non-Final Office Action for U.S. Appl. No. 11/849,352 mailed Jul. 17, 2009.Applicant
- Non-Final Office Action for U.S. Appl. No. 10/991,970 mailed May 18, 2009.Applicant
- Non-Final Office Action for U.S. Appl. No. 10/991,969 mailed Apr. 27, 2009.Applicant
- Non-Final Office Action for U.S. Appl. No. 11/684,614 mailed Apr. 24, 2009.Applicant