Brocade Network OS Administrator’s Guide v4.1.1 - Manual (Page 612)

5. Enable the VRRP or VRRP-E protocol for the interface. (In this example, VRRP-E.)
switch(config-rbridge-id-1)# vrrp-extended 10
6. Set the virtual IP address.
switch(config-rbridge-id-1)# virtual-ip 172.128.20.1
Configuring OSPF VRF-Lite for customer-edge routers
When you enable VRF-Lite on a customer-edge (CE) router, the down (DN) bit setting is ignored,
allowing the CE router to add these routes to the Virtual Routing and Forwarding (VRF) routing table.
To enable VRF-Lite, perform the following steps:
1. Enable OSPF routing on a VRF instance.
switch(config)# router ospf vrf 1
2. Enable VRF-Lite for the VRF instance.
switch(config-ospf-router-vrf-1)# vrf-lite-capability
NOTE
To disable VRF-Lite, use the no vrf-lite-capability command. This disables the VRF instance only.
It does not disable the default VRF.
Inter-VRF route leaking
Virtual Routing and Forwarding (VRF) is a technology that provides you with the ability to have
multiple virtual routers on a single physical router or switch. VRFs operate without knowledge of one
another unless they are imported or exported into one another using Inter-VRF Route Leaking. Inter-
VRF route leaking allows leaking of specific route prefixes from one VRF instance to another VRF
instance on the same physical router, which eliminates the need for external routing. This is useful in
cases where multiple VRFs share the same path to reach an external domain, while maintaining their
internal routing information limited to their own VRF. This feature enables a data center to consolidate
multiple VRF services onto a single server.
The restrictions on Inter-VRF route leaking are:
• Each routed interface (whether virtual or physical) can only belong to one VRF.
• Dynamic routes from BGP or OSPF cannot be leaked.
• HA is not supported.
For more information on VRF functionality, refer to VRF overview on page 609.
Inter-VRF route conflicts
VRF Route Leaking is a feature which should only be deployed by an advanced user, as route leak
configuration in source VRFs may collide with route/interface definitions in target VRFs. This may lead
to unpredictable behavior in packet forwarding.
Some of the ways that leaked route conflicts can occur are:
• Static route conflict
• Dynamic route conflict
• Connected route conflict
Configuring OSPF VRF-Lite for customer-edge routers
612 Network OS Administrator’s Guide
53-1003225-04