Cradlepoint IBR1100 User Manual page 59

User Manual / IBR1100/IBR1150
Certain match conditions and set actions are protocol-
specific. Referencing a protocol-specific route map from an
incompatible protocol will cause errors during operation that
prevent the routing protocol from starting.
• OSPF-specific: metric-type.
• BGP-specific: as-path, weight, comm-list, local-preference,
community, ext community.
A community is identified by a 32-bit value (e.g. 1234567890)
usually expressed as two 16-bit values separated by a colon
(e.g. 18838:722). A received or well-known community can be
referenced by its number (or number pair), while defining a
community list allows naming and refering to it by name.
Note certain well-known communities can be used by name
without definition: no-advertise (never advertise these
routes), no-export (don't advertise beyond confederation
boundary), local-AS (don't advertise to external peers),
internet (advertise to everyone), and none (used to clear any
community associated with a route).
BGP route filters are only used by the BGP protocol. Access
lists are prepended with 'fl:' when shown in selection UI.
Community lists are prepended with 'cl:'. Filter names must be
unique across all filters, common and protocol-specific.
Route filter entries are processed in the order in which they
appear in the grid. A match will apply the action (permit or
deny) specified for the entry and processing will stop. If a
filter is referenced and no match is found, the route is denied.
Access List: The ip as-path access-list allows filtering by BGP as-path. The as-path value can be specified as a
regular expression (regex).
Community List: Allows filtering by community. In essence a community is a label which is attached to routes
learned from that community. Then that community or label can be used to select which policy(s) should be
applied to those routes.
©2016 Cradlepoint. All Rights Reserved. | +1.855.813.3385 | cradlepoint.com
7/15/16
59