Controlling Route Generation; Prerequisites; Injecting A Local Network; Configuring Bgp Route Redistribution - 3Com S7906E Configuration Manual

To do...
Allow the establishment of
eBGP connection to a non
directly connected peer/peer
group
The peer ebgp-max-hop command needs not be configured if the two eBGP peers are directly
connected.

Controlling Route Generation

Different from IGP, BGP focuses on route generation and advertisement control and optimal route
selection.
There are to ways to generate BGP routes:
Configure BGP to advertise local networks
Configure BGP to redistribute routes from other routing protocols, including the default route

Prerequisites

BGP connections have been created.

Injecting a Local Network

In BGP view, you can inject a local network to allow BGP to advertise it to BGP peers. The origin
attribute of routes advertised in this way is IGP. You can also reference a route policy to flexibly control
route advertisement. The network to be injected must be available in the local IP routing table.
Follow these steps to inject a local network:
To do...
Enter system view
Enter BGP view
Inject a network to the BGP
routing table

Configuring BGP Route Redistribution

BGP does not find routes by itself. Rather, it redistributes routing information in the local AS from other
routing protocols. During route redistribution, you can configure BGP to filter routing information from
specific routing protocols.
The origin attribute of routes redistributed using the import-route command is Incomplete.
Follow these steps to configure BGP route redistribution:
Use the command...
peer { group-name |
ip-address } ebgp-max-hop
[ hop-count ]
Use the command...
system-view
bgp as-number
network ip-address [ mask |
mask-length ] route-policy
route-policy-name
1-20
Remarks
Optional
Not allowed by default.
Remarks
—
—
Optional
Not injected by default