route-map does not continue (match source-protocol)

[Jacob Zartmann]

Hi,

I'm trying to set local-preference with a route-map using the contition of the source protocol like this:

route-map ospfv3-to-bgp permit 10
 match source-protocol ospfv3 1
 set local-pref 200
route-map ospfv3-to-bgp permit 20
 match source-protocol ospfv3 2
 set local-pref 300

If I have NO ospfv3 process with id 1, I see local-preference of 200. If I create the process with id 1 (no neighbors) I see local-pref of 200. If I get some adj with the ospfv3 1 process (I prefer using ospf cost the ospfv3 2 process), I see local-pref of 200.

Looks like the route-map doesn't go any further than sequence 10! :(

Any comments/suggestions are quite welcome.

Thanks,

/JZ

[milan.kulik]

Hi,

I believe the syntax is
match source-protocol source-protocol [autonomous-system-number]

But ospfv3 process with id 1 does NOT mean an  autonomous-system-number 1!

So it's possibly ignoring the process number and only matching the source protocol?

Best regards,

Milan

[Jacob Zartmann]

Hi,

Yes, usually it is the ASN, but look at this:

PE(config-route-map)#mat source-protocol ospfv3 ?
  <1-65535>  Process ID

PE(config-route-map)#mat source-protocol ospfv3

Also the documentation says valid options are: bgp, connected, eigrp, isis, ospf, rip, and static

Of the mentioned only BGP and EIGRP has ASN.

Thanks

/JZ

[ASIER GONZALEZ DIAZ]

Hi
I use match source-protocol only to match EIGRP external routes.
This protocol, EIGRP, includes some useful "attributes" of redistributed prefixes as "metadata", I mean the External Data displayed at the EIGRP topology.
The attributes, among others, can be:
-The external AS number: AS or PID, according to the protocol
-The external protocol and metric: BGP,OSPF, etc...and the metric of the redistributed prefix at the redistribution point
-Administrator tag: for example in BGP it is the AS where the route has been learned from, tag is added automatically.

Regards