Users Guide

Table Of Contents
Deleting a non-default VRF instance
Before deleting a non-default VRF instance, ensure all the dependencies and associations corresponding to that VRF instance
are first deleted or disabled. The following procedure describes how to delete a non-default VRF instance:
After deleting all dependencies, you can delete the non-default VRF instances that you have created.
Delete a non-default VRF instance using the following command:
CONFIGURATION
no ip vrf vrf-name
NOTE: You cannot delete the default VRF instance.
Configure a static route for a non-default VRF instance
Configure a static route in a non-default VRF instance. Static routes contain IP addresses of the next-hop neighbors that
are reachable through the non-default VRF. These IP addresses could also belong to the interfaces that are part of the
non-default VRF instance.
CONFIGURATION
ip route vrf vrf-name ip-address mask next-hop-ip-address or ipv6 route vrf vrf-name ipv6-
address prefix-length next-hop-ipv6address
For example: ip route vrf red 10.1.1.0/24 20.1.1.6 or ipv6 route vrf red 2::/64 3::1
Configure the route to direct traffic to a front-panel port in case of a non-default VRF instance.
CONFIGURATION
ip route ip-address-mask ethernet interface-type or ipv6 route ipv6address-mask ethernet
interface-type
For example: ip route 10.1.1.0/24 ethernet 1/1/1 or ipv6 route 2::/64 ethernet 1/1/1. Where
ethernet 1/1/1 is part of the non-default VRF.
Configuring static entry in IPv6 neighbor
Configure a static entry in the IPv6 neighbor discovery.
CONFIGURATION
ipv6 neighbor vrf vrftest 1::1 ethernet 1/1/1 xx:xx:xx:xx:xx:xx
VRF configuration
The following configuration illustrates a typical VRF setup:
Layer 3
727