host1(config-route-map)#
exit
host1(config)#
ip community-list 1 permit 25
host1(config)#
ip community-list 2 permit 62
host1(config)#
ip community-list 3 permit internet
Community list 1 comprises routes with a community of 25; their metric is set to 20.
Community list 2 comprises routes with a community of 62; their metric is set to 75.
Community 3 catches all remaining routes by matching the Internet community; their
metric is set to 85.
ip bgp-community new-format
•
Use to specify that communities must be displayed in
AA
:
NN
format, where
AA
is a
number that identifies the autonomous system and
NN
is a number that identifies the
community within the autonomous system.
•
Example
host1(config)#
ip bgp-community new-format
•
Use the
no
version to restore the default display.
•
See ip bgp-community new-format.
ip community-list
•
Use to create a community list for BGP and control access to it.
•
The list name can be up to 32 characters long.
•
A route can belong to any number of communities, so a community list can have many
entries comprising many communities.
•
You can specify one or more community values when you create a community list. A
clause in a route map that includes a list that has more than one value matches only
a route that has all of the values; that is, the multiple values are logical ANDed.
•
You can specify community values with a number or a regular expression.
•
Example
host1(config)#
ip community-list 1 permit 100:2 100:3 100:4
host1(config)#
route-map marengo permit 10
host1(config-route-map)#
match community 1
A route matches this community list only if it belongs to at least all three communities
in community list 1: communities 100:2, 100:3, and 100:4.
•
Use the
no
version to remove the specified community list, including all list entries.
•
See ip community-list.
neighbor send-community
•
Use to specify that a community attribute be sent to a BGP neighbor.
•
If you specify a BGP peer group by using the
peer-group-name
argument, all the
members of the peer group inherit the characteristic configured with this command.
•
Example
39
Copyright © 2010, Juniper Networks, Inc.
Chapter 1: Configuring Routing Policy
Summary of Contents for JUNOSE 11.2.X IP SERVICES
Page 6: ...Copyright 2010 Juniper Networks Inc vi...
Page 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x IP Services Configuration Guide...
Page 18: ...Copyright 2010 Juniper Networks Inc xviii JunosE 11 2 x IP Services Configuration Guide...
Page 22: ...Copyright 2010 Juniper Networks Inc xxii JunosE 11 2 x IP Services Configuration Guide...
Page 28: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x IP Services Configuration Guide...
Page 116: ...Copyright 2010 Juniper Networks Inc 90 JunosE 11 2 x IP Services Configuration Guide...
Page 144: ...Copyright 2010 Juniper Networks Inc 118 JunosE 11 2 x IP Services Configuration Guide...
Page 230: ...Copyright 2010 Juniper Networks Inc 204 JunosE 11 2 x IP Services Configuration Guide...
Page 262: ...Copyright 2010 Juniper Networks Inc 236 JunosE 11 2 x IP Services Configuration Guide...
Page 294: ...Copyright 2010 Juniper Networks Inc 268 JunosE 11 2 x IP Services Configuration Guide...
Page 328: ...Copyright 2010 Juniper Networks Inc 302 JunosE 11 2 x IP Services Configuration Guide...
Page 345: ...PART 2 Index Index on page 321 319 Copyright 2010 Juniper Networks Inc...
Page 346: ...Copyright 2010 Juniper Networks Inc 320 JunosE 11 2 x IP Services Configuration Guide...
Page 356: ...Copyright 2010 Juniper Networks Inc 330 JunosE 11 2 x IP Services Configuration Guide...