Login
- Table of Contents
-
- 06-Network
- 01-Scanner
- 02-VRF
- 03-Interface
- 04-Interface pairs
- 05-Interface collaboration
- 06-Security zones
- 07-VLAN
- 08-MAC
- 09-DNS
- 10-ARP
- 11-ND
- 12-Forwarding advanced settings
- 13-Routing table
- 14-Static routing
- 15-Policy-based routing
- 16-OSPF
- 17-RIP
- 18-HTTP
- 19-SSH
- 20-NTP
- 21-FTP
- 22-Telnet
- 23-MAC authentication
- 24-MAC address whitelist
- 25-MAC access silent MAC info
- 26-MAC access advanced settings
- 27-IP authentication
- 28-IPv4 whitelist
- 29-IPv6 whitelist
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 02-VRF | 22.22 KB |
VRF
Introduction
Virtual Routing and Forwarding (VRF) implements route isolation, data independence, and data security for VPNs.
A VRF has the following components:
· A separate Label Forwarding Information Base (LFIB).
· An IP routing table.
· Interfaces bound to the VRF.
· VRF administration information including a route distinguishers (RD).
An RD is added before a site ID to distinguish the sites that have the same site ID but reside in different VPNs. An RD and a site ID uniquely identify a VPN site.
An RD is a string of 3 to 21 characters in one of the following formats:
· 16-bit AS number:32-bit user-defined number. For example, 101:3.
· 32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1.
· 32-bit AS number:16-bit user-defined number, where the minimum value of the AS number is 65536. For example, 65536:1.
VRFs can be bound to the multiple instances of a multicast or routing protocol to implement service isolation. For example, if a device supports multiple OSPF instances, you can bind a VRF to each OSPF process, so that routes learned by an OSPF process are added into the routing table of the bound VRF.
