Primarily for static routing/tracking; Route leaking and vrf import/exports haven't proven to be as good a fit.
interface vasileft950 vrf forwarding vrf900 ip address 169.254.23.37 255.255.255.252 ip nat outside ! interface vasiright950 ip address 169.254.23.38 255.255.255.252 ip nat outside ! ip route 10.2.0.0 255.255.255.128 vasiright950 169.254.23.37 name vrf950 track 950 ! and basic nat ip nat inside source static network 10.0.81.0 10.2.0.0 /24 vrf vrf600 match-in-vrf Mick On 24 September 2015 at 12:35, Pshem Kowalczyk <[email protected]> wrote: > Hi, > > I don't expect that platform to ever support those sort of features (but > that's my personal opinion). The network chips in the platform can do very > minimal amount of manipulation and the CPU doesn't have a lot of power > either. > > What sort of functionality do you need on those devices? > > kind regards > Pshem > > > On Thu, 24 Sep 2015 at 13:09 Mick O'Rourke <[email protected]> wrote: > >> Hi, >> >> Is anyone able to confirm if VASI is supported on the ASR920 currently, if >> there are plans for it to be and or if there is a potential or equivalent >> way to achieve the same result on the 920? >> >> Cheers, >> >> Mick >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
