Thanks for the reply Sundar.

I noticed the WC mask and thought it was incorrect, I changed it to 31.

can you explain why it is 3?

also, after putting it back to 3, I still do not see the desired subnet in the routing table:

Edge#sh ip route

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default

U - per-user static route, o - ODR

Gateway of last resort is 63.65.190.189 to network 0.0.0.0

4.0.0.0/32 is subnetted, 1 subnets

S 4.2.2.2 [1/0] via 63.65.190.189

65.0.0.0/27 is subnetted, 1 subnets

C 65.207.187.128 is directly connected, Ethernet0

10.0.0.0/24 is subnetted, 1 subnets

O 10.100.73.0 [110/20] via 65.207.187.130, 00:01:19, Ethernet0

63.0.0.0/30 is subnetted, 1 subnets

C 63.65.190.188 is directly connected, Serial0

B* 0.0.0.0/0 [20/0] via 63.65.190.189, 00:02:20

BGP>en

Password:

BGP#sh ip route

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area

N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2

E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP

i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default

U - per-user static route, o - ODR

Gateway of last resort is 20.30.40.1 to network 0.0.0.0

65.0.0.0/27 is subnetted, 1 subnets

B 65.207.187.128 [20/0] via 63.65.190.190, 00:01:47

20.0.0.0/30 is subnetted, 1 subnets

C 20.30.40.0 is directly connected, Ethernet0

63.0.0.0/30 is subnetted, 1 subnets

C 63.65.190.188 is directly connected, Serial0

S* 0.0.0.0/0 [1/0] via 20.30.40.1

As Sundar indicated, it needs to be 0.0.0.3 and not 0.0.0.31 based on you network

statement under bgp and mask "network 6.6.1.184 mask 255.255.255.252

,this is very important when using ACLs to get the right inversed mask.

go to this link which will explain in much more details.

http://www.mdh.se/netcenter/ct3790/ct3790_HT2005_p2/ACLs.pdf

Also, when making changes to bgp you need to do a bgp soft reset for the new changes to take effect.

http://www.cisco.com/en/US/products/ps6599/products_data_sheet09186a0080087b3a.html

Rgds

Jorge

Wilson,

The reason why network 2.1.1.64/27 isn't being advertised by BGP is because the Edge router does not have a route to that network in the routing table. The network statement under BGP process alone doesn't cause the router to advertise the network but it also requires a route to that network exist in the routing table.

Try adding 'ip route 2.1.1.64 255.255.224.0 (null0)' and test. You can substitute the null interface with another interface or next hop. As Jorge indicated you may have to do 'clear ip bgp soft * out' for any configuration change to take effect.

HTH

Sundar

Thanks Sundar and Jorge,

Ok, so I understand this:

If I had two locations DR (where both the edge and BGP routers are located),

And I want to advertise the 2.1.1.64 subnet from DR when it is no longer available (site is wiped out and DR is not getting updates via MPLS connection from HQ)

Wouldnt it be removed out of the Edge router route table at that point?

Also, what are these lines doing:

ip prefix-list 1 seq 5 permit 65.207.187.128/27

ip prefix-list 1 seq 6 permit 206.113.198.64/27

ip prefix-list 1 seq 10 deny 0.0.0.0/0 le 32

In your configuration, prefix-list lines allow only two networks (65.207.187.128/27 and 206.113.198.64/27) to be advertised to the neighbor 6.6.1.189.

thanks, so that leaves the last question:

If BGP will not advertise the subnet unless it is in the route table of that router, and the only way it is in the route table is from the HQ site that has been wiped out,

Does that mean that if you want to advertise the subnet in the Disaster Recovery scenario, that you have to put a static route in the Edge router to make sure the router is advertised with the advertise and non exist maps?

That's correct!!

If you want the Edge Router to not use the static route if it's learning the network that you want to advertise from the HQ router then you can configure a floating static route aka route with a higher admin distance. This would cause the Edge router to use the static route only when the route learned from the HQ via the routing protocol disappears.

ip route 2.1.1.64 255255.255.224 200 --> 200 is the Admin distance.

HTH

Sundar