Dell OS10 Route-Map Configuration: Match, Set and Verify

2026年10月4日 LOG admin

Dell SmartFabric OS10 route-maps look like Cisco IOS route-maps, which is exactly why people get them wrong: they copy an IOS habit across, and the redistribution silently does nothing. This guide covers how OS10 evaluates route-map clauses, how match and set interact, and the verification commands that prove a route-map is actually doing what you think.

Route-Map Fundamentals in OS10

A route-map in OS10 is an ordered list of statements, each with a sequence number. An ACL or prefix-list can only permit or deny; a route-map can rewrite attributes as it matches. OS10 evaluates clauses top-down and stops at the first match for a permit with set actions, or drops the route on a deny.

route-map REDIST-OSPFIGP permit 10
 match metric 20
 set tag 250000

Matching on Metric, Tag and Interface

OS10 supports metric, tag and interface match conditions. Keep the number of match filters low — every additional filter runs per route per update cycle.

route-map MATCH-EXAMPLE permit 10
 match metric 100
 match tag 65001
 match interface vlan 100

To remove a single condition, prefix it with no; to remove the whole map you must supply the sequence number, otherwise every clause sharing the name is deleted.

Combining Route-Maps with Prefix-Lists

The real filtering work happens when a prefix-list gates which routes reach the set clause. OS10's evaluation table is unforgiving:

Route-map clause	Prefix-list	Incoming route	Action
permit	permit	MATCH	Route is permitted
permit	permit	NO MATCH	Continue to next clause
deny	permit	MATCH	Route is denied
permit	deny	MATCH	Continue to next clause

ip prefix-list PL-CUST seq 10 permit 10.10.0.0/16 le 24
route-map RM-CUST permit 10
 match ip address prefix-list PL-CUST
 set local-preference 200
 set community 65000:100 additive

Applying the Route-Map

router bgp 65000
 neighbor 10.0.0.1 remote-as 65001
 neighbor 10.0.0.1 address-family ipv4 unicast
  route-map RM-CUST in
  route-map RM-EXPORT out
 exit-address-family

For redistribution, apply the map on the redistribution statement rather than the neighbor:

router ospf 1
 redistribute bgp 65000 route-map REDIST-OSPFIGP

Verification

show route-map
show route-map RM-CUST
show ip prefix-list
show ip bgp neighbors 10.0.0.1 routes
show ip bgp community 65000:100

If show route-map prints a Match clauses line you did not expect, you have a leftover clause from an earlier edit — order and content both matter and stale clauses are the single most common cause of “the route-map is not working” tickets.

Troubleshooting Checklist

show route-map shows no Set clauses → the set command failed silently due to a missing permit.
Routes missing after a deny insertion → remember deny terminates evaluation for that route.
Redistribution drops everything → your prefix-list has a final implicit deny; add seq 9999 permit 0.0.0.0/0 le 32 if that is not the intent.
Changes not taking effect → confirm with do show route-map from config mode and remember OS10 requires end then write memory for persistence.