-
Cisco Active Network Abstraction Technology Support and Information Model Reference Manual, 3.6.2
-
Preface
-
Introduction
-
Internet Protocol “IP”
-
Routing Protocols “BGP/OSPF”
-
Ethernet (IEEE 802.3)
-
Token Ring “TR” (IEEE 802.5)
-
Asynchronous Transfer Mode “ATM”
-
Frame Relay “FR”
-
Point-to-Point Protocol “PPP” and High Level Data
-
Layer 2 Tunnel Protocol “L2TP”
-
Digital Subscriber Line “DSL” and Integrated
-
Physical Technologies
-
Multiprotocol Label Switching “MPLS”
-
Multi Protocol Label Switching Traffic Engineering
-
Virtual Private Networks “VPNs”
-
Pseudo Wire Emulation Edge to Edge (PWE3)
-
Access Control Lists “ACLs”
-
Physical Equipment
-
Base Logical Components
-
Common (Shared by Several)
-
Cisco ANA VNE Topology
-
Table Of Contents
Virtual Private Networks "VPNs"
Inventory and Information Model Objects (IMOs)
Virtual Routing Forwarding (VRF) Entity
Equivalent Cross Virtual Routing Entry
Virtual Private Networks "VPNs"
This chapter describes the level of support that Cisco ANA provides for VPNs, as follows:
•
Inventory and Information Model Objects (IMOs)
Technology Description
VPN
BGP/MPLS VPNs, as defined in RFC 2547 and related drafts and standards, provide a Layer 3 VPN. With Layer 3 VPNs, each Provider Edge (PE) device acts like a set of virtual routers, one per VPN. The network provider configures the VPN membership of each PE router interface. In most cases, one port is used for multiple interfaces where each is associated with different VPNs. The port's view of the network is restricted to the VPNs of which it is a member, and it cannot address devices outside that environment. Either static routes are provisioned on both the Customer Edge (CE) and PE, or, for more complex scenarios, a routing protocol (such as RIP, OSPF or BGP) is run between CE and PE. So the interface between the CE and PE devices is conventional IP routing.
The network provider also establishes a suitable mesh of MPLS Label Switched Paths (LSPs) between all the PE routers that need to communicate. The PE devices qualify each external IP address that they learn with a per VPN identifier, and broadcast them to all other PE routers using an extended form of BGP depending on BGP connectivity. They also include an MPLS label that is specific to the destination route (or, in some implementations, the destination port). Through this process, the PE devices build up a complete map of the VPNs and destination labels.
The PE routers then use this information to route the packets across the backbone network to the correct destination within the relevant VPN.
Inventory and Information Model Objects (IMOs)
This section includes the following tables:
•
•
•
•
•
•
Virtual Routing Forwarding (VRF) Entity
The following Virtual Routing Forwarding (VRF) Entity object describes the routing and address resolution protocols independent forwarding component of a MPLS-BGP based VPN router, which is bound by its Logical Sons attribute to all Network layer IP Interface objects, which IP Packets are being routed between, by this Virtual Routing Forwarding Entity.
Table 14-1 Virtual Routing Forwarding (VRF) Entity (IVrf)
Virtual Routing Table
Array of Equivalent Routing Entries
IP Core
Configuration
Exported Route Targets
Array of route target identifiers
IP Core
Configuration
Imported Route Targets
Array of route target identifiers
IP Core
Configuration
Route Distinguisher
Route distinguisher
IP Core
Configuration
ARP Entity
Address Resolution Entity (ARP Entity) (see Internet Protocol "IP")
IP Core
Configuration
Name
VRF name
IP Core
Configuration
Logical Sons
Array of all IP Interfaces, which IP packets are being routed between, by this Virtual Routing Forwarding (VRF) Entity
IP Core
N/A
Equivalent Routing Entry
The following Equivalent Routing Entry and Virtual Routing Entry objects describe a routing table's entries, each as an array of Virtual Routing Entries sharing a single IP Subnetwork destination.
Table 14-2 Equivalent Routing Entry (IRoutingEntries)
Routing Entries
Array of Virtual Routing Entries (sharing a single destination)
IP Core
Configuration
Virtual Routing Entry
Multi Protocol BGP Entity
The following Multi Protocol BGP Entity object describes the BGP component of a MPLS-BGP based VPN router, which is bound by its Logical Sons attribute to all Virtual Routing Forwarding (VRF) Entity objects, which IP Packets are being routed between by this Multi Protocol BGP Entity.
Table 14-4 Multi Protocol BGP Entity (IMpBgp)
BGP Identifier
Border Gateway Protocol (BGP) identifier
IP Core
Configuration
Local Autonomous System
Local peer autonomous system
IP Core
Configuration
Cross Virtual Routing Table
IP Core
Configuration
BGP Neighbors
Array of BGP neighbor entries (see Routing Protocols "BGP/OSPF")
IP Core
Configuration
Logical Sons
Array of all Virtual Routing Entries, which IP packets are being routed between, by this Multi Protocol BGP Entity
IP Core
N/A
Equivalent Cross Virtual Routing Entry
The following Equivalent Cross Virtual Routing Entry and Cross Virtual Routing Entry objects describe the first dimension of a cross virtual routing table, as an array of Cross Virtual Routing Entries sharing a single Virtual Routing Forwarding (VRF) Entity destination.
Table 14-5 Equivalent Cross Virtual Routing Entry (ICrossVrf)
Virtual Routing Entries
Array of Cross Virtual Routing Entries (sharing a single destination)
IP Core
Configuration
Virtual Routing Entity Name
Virtual Routing Entity (VRF) name
IP Core
Configuration
Cross Virtual Routing Entry
Network Topology
The discovery of MPLS-BGP based Virtual Private (VPN) network topology is done by searching for the existence of the local Virtual Routing Forwarding (VRF) Entity's imported route targets in any remote side's VRF entity exported route targets.
Service Alarms
The following alarm is supported for this technology:
•
Note
Note
