Need a little help with BGP routing - default route (cisco)

V

vxspiritxv

[H]ard|Gawd
Joined
Feb 10, 2001
Messages
1,610
I have a bunch of routers talking, everything is good except for the default route.
The router with the default route:

interface GigabitEthernet0/0/0.5
encapsulation dot1Q 5
ip address 10.1.1.3 255.255.255.0
no ip redirects
no ip unreachables
no ip proxy-arp
interface GigabitEthernet0/0/2.727
bandwidth 100000
encapsulation dot1Q 727
ip address 10.1.10.1 255.255.255.252
no ip redirects
router bgp 65005
bgp log-neighbor-changes
network 10.1.1.0 mask 255.255.255.0
redistribute static
neighbor 10.1.10.2 remote-as 10009
neighbor 10.1.10.2 default-originate
ip route 0.0.0.0 0.0.0.0 10.1.1.254

10.1.1.254 is the firewall which then goes to the internet.

Anyways seems the default route in BGP is working, but the router isn't routing the data from BGP to the static route.

la-router#traceroute 8.8.8.8
Type escape sequence to abort.
Tracing the route to google-public-dns-a.google.com (8.8.8.8)
VRF info: (vrf in name/id, vrf out name/id)
1 att-la-router.xxxxxx.com (10.1.10.22) [AS 10009] 4 msec 2 msec 3 msec
2 att-idc-router.xxxxxx.com (10.1.10.2) [AS 10009] 2 msec 2 msec 2 msec
3 idc-router.xxxxxx.com (10.1.10.1) [AS 10009] 3 msec 3 msec 3 msec
4 * * *
5 * *
 
Update:

It's just the router not doing traces, everything behind the router is just fine.
So it is working, but I'm still scratching my head about it lol.
 
To me, it doesnt look like your default route is working at all since there is no hop to 10.1.1.254. To better understand this, a diagram would be very helpful with indications of where you are trying to run tests from and where they are breaking down. BGP is a relatively straight forward protocol. Is LA-Router your edge that connects to the firewall? I'm guessing here that gi0/0/0 connects to the firewall and gi0/0/2 connects to another router downstream? From the way you are describing this, it sounds like you are trying to do a Hub-Spoke setup correct?
 
vxspiritxv said:
Update:

It's just the router not doing traces, everything behind the router is just fine.
So it is working, but I'm still scratching my head about it lol.
Click to expand...

Maybe because a trace from the router is not sourcing from the interface you think it is?...

Hard to say with the info provided. What does a trace look like behind the router?
 
Wheres the NAT being done? If it's using an interface with a private IP, it won't route to the internet (unless its NAT'd)
 
Thanks, source works.

#traceroute 8.8.8.8 source gigabitEthernet 0/0/1
Type escape sequence to abort.
Tracing the route to google-public-dns-a.google.com (8.8.8.8)
VRF info: (vrf in name/id, vrf out name/id)
1 att-la-router.xxxxxx.com (10.1.10.22) [AS 13979] 6 msec 3 msec 3 msec
2 att-idc-router.xxxxxx.com (10.1.10.2) [AS 13979] 2 msec 2 msec 2 msec
3 idc-router.xxxxxx.com (10.1.10.1) [AS 13979] 3 msec 4 msec 3 msec
4 fortigate.xxxxxx.com (10.1.1.254) [AS 13979] 3 msec 4 msec 3 msec
5 216.65.xxx.xxx [AS 13979] 4 msec 5 msec 3 msec
6 podz01c6513r0002-tge-10-4.lax2.attens.net (206.19.184.93) [AS 13979] 4 msec 3 msec 3 msec
7 12.91.217.158 [AS 13979] 5 msec 6 msec 5 msec
8 12.91.217.158 [AS 13979] 6 msec 5 msec 5 msec
9 209.85.245.189 [AS 13979] 6 msec
64.233.174.213 [AS 13979] 6 msec 5 msec
10 216.239.62.81 [AS 13979] 6 msec
216.239.58.217 [AS 13979] 6 msec
209.85.255.75 [AS 13979] 6 msec
11 google-public-dns-a.google.com (8.8.8.8) [AS 13979] 6 msec 6 msec 6 msec
#
 
You must log in or register to reply here.
Back
Top