On 15-Sep-04, at 2:06 AM, Cengiz Alaettinoglu wrote:
On Mon, 2004-09-13 at 09:10, Jason Lixfeld wrote:
I have some more questions about configureRouter
My inet-rtr object:
peer: BGP4 198.32.245.8 asno(AS13657)
My aut-num object:
import: from AS13657 198.32.245.8 at 198.32.245.49 accept <^AS13657 AS13657:AS-CUSTOMERS* $> AND AS13657 AND AS13657:AS-CUSTOMERS
You probably mean: ... AND (AS13657 OR AS13657:AS-CUSTOMERS)
It was actually: ... AND (AS13657 AS13657:AS-CUSTOMERS)
When I run the inet-rtr object through configureRouter, I get the correct as-path list as per the import attribute's accept policy filter, however it's not generating the proper prefix information. All it's generating is:
no ip prefix-list pl100 ip prefix-list pl100 permit 199.246.110.0/23 ip prefix-list pl100 deny 0.0.0.0/0 le 32
That prefix has an origin of one of the AS' inside the as-set referenced above.
The number of route objects with origins of AS13657 or origins of AS' inside AS13678:AS-CUSTOMERS is far more than the single prefix listed above.
The idea of what I'm trying to do above should work, right? Generating as-path info from the as-path policy then generating the prefix info shouldn't be a problem, correct?
Can anyone see anything wrong with what I'm trying to do? Anyone know of a better way to do it? -- Cengiz