Matching A Community List Exactly; Removing Community Lists From A Route Map - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - IP SERVICES CONFIGURATION GUIDE 2010-10-01 Configuration Manual

Software for e series broadband services routers ip services configuration guide
Table of Contents

Advertisement

JunosE 11.3.x IP Services Configuration Guide

Matching a Community List Exactly

Removing Community Lists from a Route Map

8
host1(config-route-map)#exit
host1(config)#exit
host1#show route-map
route-map miami, permit, sequence 10
Match clauses:
match community corporate5
Issue either of the following commands to delete the entire match community entry:
host1(config-route-map)#no match community
host1(config-route-map)#no match community corporate5 dade2
You can use the exact-match keyword for the match community command to specify
that a match exists only for the exact community numbers specified in the community
list. The exact-match keyword applies only to a standard community list—that is, one
not specified by a regular expression. You cannot use the exact-match keyword with a
community list that is specified by a regular expression.
Consider the following example:
host1(config)#ip community-list 1 permit 100 200 300
host1(config)#exit
host1#show ip community-list
Community standard list 1
permit 0:100 0:200 0:300
host1(config)#route-map example1 permit 10
host1(config-route-map)#match community 1 exact-match
host1(config)#exit
host1#show route-map example1
route-map example, permit, sequence 10
Match clauses:
community (community-list filter): 1 exact-match
The route map example1 permits a route only if the route contains community 100 and
community 200 and community 300 and no additional communities.
If you do not specify the exact-match option, the route map also permits a match on a
route that contains additional communities. For example, a route that contains
communities 100, 200, 300, 400, and 450 matches.
You can use the set comm-list delete command to remove the specified community
list from routes matching the route map, provided that you created the community list
with a single community number per list entry. For example, you cannot remove the
community lists 231:10 and 231:20 with the set comm-list delete command if you created
them with the following command:
host1(config)#ip community list 1 permit 231:10 231:20
You can, however, remove the lists with the set comm-list delete command if you created
them separately with the following commands:
host1(config)#ip community list 1 permit 231:10
Copyright © 2010, Juniper Networks, Inc.

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents