Nokia IPSO 4.0 manual Redistributing Routes to BGP

„Refines—Matches a route only if it is more specific than the given prefix.

„Range—Matches any route whose IP address equals the given prefix’s IP address and whose mask length falls within the specified mask length range.

A sample route redistribution examples follow.

Note

The Route Redistribution link contains over thirty possible route redistribution options.

The redistribute_list specifies the source of a set of routes based on parameters such as the protocol from which the source has been learned. The redistribute_list indirectly controls the redistribution of routes between protocols.

The syntax varies slightly per source protocol. BGP routes may be specified by source AS. RIP and IGRP routes may be redistributed by protocol, source interface, and/or source gateway. Both OSPF and OSPF ASE routes may be redistributed into other protocols. All routes may be redistributed by AS path.

When BGP is configured, all routes are assigned an AS path when they are added to the routing table. For all interior routes, this AS path specifies IGP as the origin and no ASes in the AS path. The current AS is added when the route is redistributed. For BGP routes, the AS path is stored as learned from BGP.

Redistributing Routes to BGP

Redistributing to BGP is controlled by an AS. The same policy is applied to all firewalls in the AS. BGP metrics are 16-bit, unsigned quantities; that is, they range from 0 to 65535 inclusive, with zero being the most attractive. While BGP version 4 supports 32-bit unsigned quantities, IPSRD does not.

Note

If you do not specify a redistribution policy, only routes to attached interfaces are redistributed. If you specify any policy, the defaults are overridden. You must explicitly specify everything that should be redistributed.

Nokia Network Voyager for IPSO 4.0 Reference Guide 439