12-09-2004 02:55 AM
Looking through my MPLS course notes i noticed that they say if you are using statics for PE-CE connectivity then you "MUST" specify the outgoing interface even if you have already specified the next hop.
Could someone please confirm if this is just legacy commands as we have got some customers on our network that we use statics with and we do not specify the outgoing interface, only the next hop and everything seems to work.
Thanks
Solved! Go to Solution.
12-09-2004 04:14 AM
The interface parameter is optional. see below.
ip route vrf
To establish static routes for a VRF, use the ip route vrf global configuration command. To disable static routes, use the no form of this command.
ip route vrf vrf-name prefix mask [next-hop-address] [interface {interface-number}]
[global] [distance] [permanent] [tag tag]
no ip route vrf vrf-name prefix mask [next-hop-address] [interface {interface-number}]
[global] [distance] [permanent] [tag tag]
Syntax Description
vrf-name
Name of the VPN routing/forwarding instance (VRF) for the static route.
prefix
IP route prefix for the destination, in dotted-decimal format.
mask
Prefix mask for the destination, in dotted-decimal format.
next-hop-address
(Optional) IP address of the next hop (the forwarding router that can be used to reach that network).
interface
(Optional) Type of network interface to use: ATM, Ethernet, loopback, POS (packet over SONET), or null.
interface-number
Number identifying the network interface to use.
global
Specifies that the given next hop address is in the non-VRF routing table.
distance
(Optional) An administrative distance for this route.
permanent
(Optional) Specifies that this route will not be removed, even if the interface shuts down.
tag tag
(Optional) Label value that can be used for controlling redistribution of routes through route maps.
12-09-2004 04:05 AM
:-)
12-09-2004 04:14 AM
The interface parameter is optional. see below.
ip route vrf
To establish static routes for a VRF, use the ip route vrf global configuration command. To disable static routes, use the no form of this command.
ip route vrf vrf-name prefix mask [next-hop-address] [interface {interface-number}]
[global] [distance] [permanent] [tag tag]
no ip route vrf vrf-name prefix mask [next-hop-address] [interface {interface-number}]
[global] [distance] [permanent] [tag tag]
Syntax Description
vrf-name
Name of the VPN routing/forwarding instance (VRF) for the static route.
prefix
IP route prefix for the destination, in dotted-decimal format.
mask
Prefix mask for the destination, in dotted-decimal format.
next-hop-address
(Optional) IP address of the next hop (the forwarding router that can be used to reach that network).
interface
(Optional) Type of network interface to use: ATM, Ethernet, loopback, POS (packet over SONET), or null.
interface-number
Number identifying the network interface to use.
global
Specifies that the given next hop address is in the non-VRF routing table.
distance
(Optional) An administrative distance for this route.
permanent
(Optional) Specifies that this route will not be removed, even if the interface shuts down.
tag tag
(Optional) Label value that can be used for controlling redistribution of routes through route maps.
12-09-2004 05:58 AM
Thanks Rab :-)
01-05-2005 05:56 AM
Hi
As I know you it is better to use the outgoing interface in vrf aware static routes, because your router doesn't need double lookup so it'll faster. What do you think?
Gabor
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide