[c-nsp] unnumbered SVI on 6500/sup720
Tim Durack
tdurack at gmail.com
Wed Apr 27 08:21:18 EDT 2011
On Wed, Apr 27, 2011 at 7:36 AM, Phil Mayers <p.mayers at imperial.ac.uk> wrote:
> On 27/04/11 12:25, Phil Mayers wrote:
>
>> ...but if you're using VRFs/MPLS VPNs as we are, the sup complains:
>>
>> % For VPN routes, must specify a next hop IP address if not a
>> point-to-point interface
>>
>> ...so you need to give a null next-hop:
>>
>> ip route vrf PROD 155.198.60.248 255.255.255.255 vl600 0.0.0.0
>>
>> Worryingly this is NVGENed as:
>>
>> ip route vrf PROD 155.198.60.248 255.255.255.255 vl600
>>
>> ...which makes we wonder if it'll parse it on a reload, given that it
>> won't at the CLI.
>
> Sure enough, this doesn't parse on reload.
>
> Oh well. Back to the drawing board.
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
This works: "ip route vrf PROD 155.198.60.248 255.255.255.255 vl600
155.198.60.248"
I've used this in the lab to export "host routes" from a VRF.
I messed with the unnumbered VLAN scenario. Didn't really like the
DHCP dependency though, especially as a router reload will then cause
significant problems.
--
Tim:>
More information about the cisco-nsp
mailing list