[c-nsp] VASI interfaces on IOS XR

[Nick Ryce]

Hi Bruce,

I was hoping to have an easy way out from import / export :-)


Nick

On 22 Feb 2012, at 00:21, "Bruce Pinsky" <bep at whack.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Nick Ryce wrote:
>> Hi Guys,
>>
>> Does anyone know if these type of interfaces can be used without a
>> services blade?  Also is there a specific version of XR required?
>>
>> I have been scouring documentation and can't really find anything.
>> Would InterFlex interfaces do the same thing?  I am looking to have 1
>> link in a VRF and the other in a separate VRF.  Then create ospf
>> adjacencies do redistribute routes between the 2 VRF tables.  Any
>> thoughts?
>>
>
> Are the routes from those different interfaces learned from other OSPF
> adjacencies?
>
> Seems like you should just be able to import the routes from the other VRF
> via an import statement?  Am I missing what you are trying to do?
>
> VASI interfaces are really designed to allow for services to be applied
> prior to label imposition on packets that would be label forwarded toward
> the core.  The VASI-left interface serves as a pseudo-CE and the VASI-right
> serves as a pseudo-PE.  If the routes you are learning and needing to be
> readvertised are coming and going from untagged interfaces, I don't think
> VASI is what you need.
>
> - --
> =========
> bep
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk9EM0MACgkQE1XcgMgrtybl5gCeMHq2qYSblgbNX+9xR79pJ22t
> t+0AoKau5fgjS//erKDT5ScwLT9B3TWp
> =hgr4
> -----END PGP SIGNATURE-----

--

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the sender. Any
offers or quotation of service are subject to formal specification.
Errors and omissions excepted.  Please note that any views or opinions
presented in this email are solely those of the author and do not
necessarily represent those of Lumison.
Finally, the recipient should check this email and any attachments for the
presence of viruses.  Lumison accept no liability for any
damage caused by any virus transmitted by this email.