[c-nsp] IOS XR RPL

[Nick Ryce]

Just found prepend as-path most-recent.  I assume this is the one I need?


Nick

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Nick Ryce
Sent: 22 September 2011 11:48
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] IOS XR RPL

Hi,

I'm trying to write a route-policy that will prepend a customers' announcement when they send a certain community.  The prepend should be their own AS number rather than our AS.

I know how to do this is Junos but could anyone point me in the right direction for IOS XR?

Thanks

Nick

________________________________
--

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.
_______________________________________________
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 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.