2 STATIC ROUTES AND REDISTRIBUTIONYOU COULD ALWAYS USE STATIC ROUTES...

You could always use static routes to originate a network or a subnet.

The only difference is that BGP will consider these routes as having

an origin of incomplete (unknown). In the above example the same could

have been accomplished by doing:

RTC#

router eigrp 10

network 175.220.0.0

redistribute bgp 200

default-metric 1000 100 250 100 1500

router bgp 200

neighbor 1.1.1.1 remote-as 300

redistribute static

ip route 175.220.0.0 255.255.255.0 null0

The null 0 interface means to disregard the packet. So if I get the

packet and there is a more specific match than 175.220.0.0 (which exists

of course) the router will send it to the specific match otherwise it

will disregard it. This is a nice way to advertise a supernet.

We have discussed how we can use different methods to originate routes

out of our autonomous system. Please remember that these routes are

generated in addition to other BGP routes that BGP has learned via

neighbors (internal or external). BGP passes on information that it

learns from one peer to other peers. The difference is that routes

generated by the network command, or redistribution or static, will

indicate your AS as the origin for these networks.

Injecting BGP into IGP is always done by redistribution.

Example: