Table Of Contents
Information Model Objects (IMOs)
Virtual Routing Forwarding (VRF) Entity
Equivalent Cross Virtual Routing Entry
Vendor-Specific Inventory and IMOs
VPN and VRF
This chapter describes the level of support that Cisco ANA provides for Virtual Private Networks (VPN) and Virtual Routing and Forwarding (VRF), as follows:
•Information Model Objects (IMOs)
•Vendor-Specific Inventory and IMOs
For information on network topology, see Chapter 38 "Cisco ANA VNE Topology."
Technology Description
This section provides the following VPN and VRF technology descriptions:
•VRF
•6VPE
Please see Part 1: Cisco VNEs in this guide for information about which devices support the various technologies.
VRF
Virtual Routing and Forwarding (VRF) is an IP technology that allows multiple instances of a routing table to coexist on the same router at the same time. Because the routing instances are independent, the same or overlapping IP addresses can be used without conflict. "VRF" is also used to refer to a routing table instance that can exist in one or multiple instances per each VPN on a Provider Edge (PE) router.
VRF-Lite (Multi-VRF)
VRF-Lite is an application based on VRF that extends the concept of VRF to the Customer Edge (CE) router on the customer's premises. It supports multiple, overlapping, independent routing and forwarding tables per customer.
Any routing protocol supported by normal VRF can be used in a VRF-Lite CE implementation. The CE supports traffic separation between customer networks. As there is no MPLS functionality on the CE, no label exchange happens between the CE and PE.
6VPE
IPv6 on VPN to Provider Edge (6VPE, RFC 2547) permits IPv6 domains to communicate with each other over an IPv4 core network, without explicit tunnel setup, requiring only one IPv4 address per IPv6 domain. 6VPE operates much like a normal IPv4 MPLS VPN provider edge, but with the addition of IPv6 support within VRF. It lets service providers support IPv6 over operational IPv4 MPLS backbones without requiring dual-stacking within the MPLS core, representing a large cost savings over core re-engineering. Only PE equipment must be dual-stack, to support awareness of both IPv4 and IPv6 access devices. 6VPE provides logically separate routing table entries for VPN member devices.
Information Model Objects (IMOs)
This section describes the following IMOs:
•Virtual Routing Forwarding (VRF) Entity (IVrf)
•Virtual Routing Entry (IVrfEntry)
•Multi Protocol BGP Entity (IMpBgp)
•Equivalent Cross Virtual Routing Entry (ICrossVrf)
•Cross Virtual Routing Entry (ICrossVrfRoutingEntry)
Virtual Routing Forwarding (VRF) Entity
The Virtual Routing Forwarding (VRF) Entity object describes the routing and address resolution protocols' independent forwarding component of a MPLS-BGP based VPN router. It is bound by its Logical Sons attribute to all the Network layer IP Interface objects among which it is routing IP packets.
Table 12-1 Virtual Routing Forwarding (VRF) Entity (IVrf)
Attribute Name Attribute Description Scheme Polling IntervalVirtual Routing Table
Array of Equivalent Routing Entries
IpCore
Configuration
Exported Route Targets
Array of route target identifiers
IpCore
Configuration
Imported Route Targets
Array of route target identifiers
IpCore
Configuration
Address Families
List of the address families (IPv4, IPv6, or both)
IpCore
Configuration
Route Distinguisher
Route distinguisher
IpCore
Configuration
ARP Entity
Address Resolution Entity (ARP Entity) (see Internet Protocol)
IpCore
Configuration
Name
VRF name
IpCore
Configuration
Logical Sons
Array of all IP Interfaces among which this Virtual Routing Forwarding (VRF) Entity is routing IP packets
IpCore
N/A
Description
Description of the VRF
IpCore
Configuration
Import Route-map
Name of the VRF import route map used to import IP prefixes into the VRF.
IpCore
Configuration
Export Route-map
Name of the VRF export route map used to export IP prefixes from the VRF.
IpCore
Configuration
Virtual Routing Entry
The Virtual Routing Entry object describes a routing table's entries.
Multi Protocol BGP Entity
The Multi Protocol BGP Entity object describes the BGP component of a MPLS-BGP based VPN router. It is bound by its Logical Sons attribute to all Virtual Routing Forwarding (VRF) Entity objects among which it is routing IP packets.
Table 12-3 Multi Protocol BGP Entity (IMpBgp)
Attribute Name Attribute Description Scheme Polling IntervalBGP Identifier
Border Gateway Protocol (BGP) identifier
IpCore
Configuration
Local Autonomous System
Local peer autonomous system
IpCore
Configuration
Cross Virtual Routing Table
IpCore
Configuration
BGP Neighbors
Array of BGP neighbor entries (see Routing Protocols)
IpCore
Configuration
Logical Sons
Array of all Virtual Routing Forwarding (VRF) Entity objects among which this Multi Protocol BGP Entity is routing IP packets
IpCore
N/A
Equivalent Cross Virtual Routing Entry
The 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 Entry objects sharing a single Virtual Routing Forwarding (VRF) Entity destination.
Table 12-4 Equivalent Cross Virtual Routing Entry (ICrossVrf)
Attribute Name Attribute Description Scheme Polling IntervalVirtual Routing Entries
Array of Cross Virtual Routing Entry objects sharing a single destination
IpCore
Configuration
Virtual Routing Entity Name
Virtual Routing Entity (VRF) name
IpCore
Configuration
Cross Virtual Routing Entry
Vendor-Specific Inventory and IMOs
There are no vendor-specific inventory or IMOs for this technology.
Service Alarms
There are no faults or alarms associated with this technology.