A clause with multiple values matches a route that has any of the values; that is, the
multiple values are logical ORed.
host1(config-route-map)#
match ip address lisbon madrid
host1(config-route-map)#
match as-path 10 20 30
You can also issue successive
match
commands to add new values to a route map entry
for any of the commands listed above.
host1(config-route-map)#
match ip address boston
host1(config-route-map)#
match ip address newyork
This method is equivalent to issuing the following single command:
host1(config-route-map)#
match ip address boston newyork
You cannot specify multiple values for the
match metric-type
command, because it has
only two acceptable values, which are mutually exclusive. Specifying both values has
the same effect as not specifying a metric type at all; specifying the same value more
than once has no meaning.
Negating Match Clauses
If you specify a value when you negate a
match
command configured in a route map,
only that value for the match entry is deleted. The routing software deletes the entire
match entry only if the entry contains no other values. In some earlier releases, any value
specified with a
no match
command was ignored, and the entire match entry was deleted.
This change applies to all
match
commands configured in a route map.
For example, consider the following match entry to route map miami:
host1(config)#
ip community-list corporate5 permit 32 463 21
host1(config)#
ip community-list dade2 permit 41 53 22
host1(config)#
route-map miami permit 1
host1(config-route-map)#
match community corporate5 dade2
host1(config-route-map)#
exit
host1(config)#
exit
host1#
show route-map
route-map miami, permit, sequence 10
Match clauses:
match community corporate5 dade2
In earlier releases, issuing a command like the following to remove a community (see
“Community Lists” on page 37) not specified in the entry deleted the whole entry, but
now nothing happens:
host1(config-route-map)#
no match community southbeach
host1(config-route-map)#
exit
host1(config)#
exit
host1#
show route-map
route-map miami, permit, sequence 10
Match clauses:
match community corporate5 dade2
If you instead issue the following commands, the specified value is deleted:
host1(config-route-map)#
no match community dade2
7
Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring Routing Policy
Содержание JUNOSE 11.2.X IP SERVICES
Страница 6: ...Copyright 2010 Juniper Networks Inc vi...
Страница 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x IP Services Configuration Guide...
Страница 18: ...Copyright 2010 Juniper Networks Inc xviii JunosE 11 2 x IP Services Configuration Guide...
Страница 22: ...Copyright 2010 Juniper Networks Inc xxii JunosE 11 2 x IP Services Configuration Guide...
Страница 28: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x IP Services Configuration Guide...
Страница 116: ...Copyright 2010 Juniper Networks Inc 90 JunosE 11 2 x IP Services Configuration Guide...
Страница 144: ...Copyright 2010 Juniper Networks Inc 118 JunosE 11 2 x IP Services Configuration Guide...
Страница 230: ...Copyright 2010 Juniper Networks Inc 204 JunosE 11 2 x IP Services Configuration Guide...
Страница 262: ...Copyright 2010 Juniper Networks Inc 236 JunosE 11 2 x IP Services Configuration Guide...
Страница 294: ...Copyright 2010 Juniper Networks Inc 268 JunosE 11 2 x IP Services Configuration Guide...
Страница 328: ...Copyright 2010 Juniper Networks Inc 302 JunosE 11 2 x IP Services Configuration Guide...
Страница 345: ...PART 2 Index Index on page 321 319 Copyright 2010 Juniper Networks Inc...
Страница 346: ...Copyright 2010 Juniper Networks Inc 320 JunosE 11 2 x IP Services Configuration Guide...
Страница 356: ...Copyright 2010 Juniper Networks Inc 330 JunosE 11 2 x IP Services Configuration Guide...