Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
3738
Views
0
Helpful
9
Replies

Route not showing up in routing table.

raul saurez
Level 1
Level 1

‎05-04-2015 10:48 AM - edited ‎03-07-2019 11:51 PM

I have my core switch connecting to my router which connects to our MPLS provider. My router has a BGP default route going to the MPLS provider edge router B*   0.0.0.0/0 [20/0] via 172.30.252.78, 1w4d .... This route is not showing up in my core switch. Shouldnt it show up as an eigrp ex default route? Can anyone assist me? my routing table for each device is below. Thank you!

Router

USJONELAWTN01R#sho ip route
Codes: C - connected, S - static, 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
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 172.30.252.78 to network 0.0.0.0

     68.0.0.0/32 is subnetted, 1 subnets
S       68.142.83.236 is directly connected, Null0
     198.63.196.0/32 is subnetted, 1 subnets
S       198.63.196.103 is directly connected, Null0
     64.0.0.0/32 is subnetted, 1 subnets
S       64.234.192.40 is directly connected, Null0
     172.26.0.0/16 is variably subnetted, 3 subnets, 2 masks
D       172.26.82.0/24 [90/28416] via 172.28.82.10, 1w5d, GigabitEthernet0/1
                       [90/28416] via 172.28.80.10, 1w5d, GigabitEthernet0/0.1
                       [90/28416] via 172.28.80.9, 1w5d, GigabitEthernet0/0.1
D       172.26.83.0/24 [90/28416] via 172.28.82.10, 1w5d, GigabitEthernet0/1
                       [90/28416] via 172.28.80.10, 1w5d, GigabitEthernet0/0.1
                       [90/28416] via 172.28.80.9, 1w5d, GigabitEthernet0/0.1
D       172.26.80.0/23 [90/28416] via 172.28.82.10, 1w5d, GigabitEthernet0/1
                       [90/28416] via 172.28.80.10, 1w5d, GigabitEthernet0/0.1
                       [90/28416] via 172.28.80.9, 1w5d, GigabitEthernet0/0.1
     172.28.0.0/16 is variably subnetted, 4 subnets, 2 masks
C       172.28.176.0/23 is directly connected, GigabitEthernet0/0.6
C       172.28.80.0/23 is directly connected, GigabitEthernet0/0.1
C       172.28.82.0/23 is directly connected, GigabitEthernet0/1
D       172.28.80.20/32
           [90/30720] via 172.28.176.3, 1w5d, GigabitEthernet0/0.6
           [90/30720] via 172.28.82.3, 1w5d, GigabitEthernet0/1
           [90/30720] via 172.28.80.3, 1w5d, GigabitEthernet0/0.1
     172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
C       172.30.252.78/32 is directly connected, Multilink1
C       172.30.252.76/30 is directly connected, Multilink1
D       172.30.252.114/32
           [90/3415808] via 172.28.176.3, 4d00h, GigabitEthernet0/0.6
           [90/3415808] via 172.28.82.3, 4d00h, GigabitEthernet0/1
           [90/3415808] via 172.28.80.3, 4d00h, GigabitEthernet0/0.1
D       172.30.252.112/30
           [90/3415808] via 172.28.176.3, 4d00h, GigabitEthernet0/0.6
           [90/3415808] via 172.28.82.3, 4d00h, GigabitEthernet0/1
           [90/3415808] via 172.28.80.3, 4d00h, GigabitEthernet0/0.1
D       172.30.254.24/32
           [90/156160] via 172.28.176.3, 1w5d, GigabitEthernet0/0.6
           [90/156160] via 172.28.82.3, 1w5d, GigabitEthernet0/1
           [90/156160] via 172.28.80.3, 1w5d, GigabitEthernet0/0.1
C       172.30.254.25/32 is directly connected, Loopback10
C    192.168.202.0/24 is directly connected, GigabitEthernet0/0.1
     10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
S       10.192.254.0/24 [1/0] via 172.28.82.10, GigabitEthernet0/1
S       10.201.0.0/16 [1/0] via 172.28.82.10, GigabitEthernet0/1
S       10.200.1.0/24 [1/0] via 172.28.82.10, GigabitEthernet0/1
C    192.168.203.0/24 is directly connected, GigabitEthernet0/0.1
C    192.168.51.0/24 is directly connected, GigabitEthernet0/0.1
B*   0.0.0.0/0 [20/0] via 172.30.252.78, 1w4d
B    200.200.0.0/16 [20/0] via 172.30.252.78, 1w4d
B    201.1.0.0/16 [20/0] via 172.30.252.78, 1w4d
B    172.16.0.0/12 [20/0] via 172.30.252.78, 1w4d
B    198.30.0.0/16 [20/0] via 172.30.252.78, 1w4d
B    192.168.0.0/16 [20/0] via 172.30.252.78, 1w4d

 

Core Switch

TNLAW-TN1COREA# sho ip route
Codes: C - connected, S - static, 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
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 10.192.61.1 to network 0.0.0.0

     172.26.0.0/16 is variably subnetted, 3 subnets, 2 masks
C       172.26.82.0/24 is directly connected, Vlan601
C       172.26.83.0/24 is directly connected, Vlan603
C       172.26.80.0/23 is directly connected, Vlan602
     172.28.0.0/16 is variably subnetted, 4 subnets, 2 masks
D       172.28.176.0/23 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                        [90/28416] via 172.28.82.2, 7w0d, Vlan2
                        [90/28416] via 172.28.80.3, 7w0d, Vlan1
                        [90/28416] via 172.28.80.2, 7w0d, Vlan1
C       172.28.80.0/23 is directly connected, Vlan1
C       172.28.82.0/23 is directly connected, Vlan2
D       172.28.80.20/32 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                        [90/28416] via 172.28.80.3, 7w0d, Vlan1
     172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
D       172.30.252.78/32 [90/3413504] via 172.28.82.2, 1w4d, Vlan2
                         [90/3413504] via 172.28.80.2, 1w4d, Vlan1
D       172.30.252.76/30 [90/3413504] via 172.28.82.2, 1w4d, Vlan2
                         [90/3413504] via 172.28.80.2, 1w4d, Vlan1
D       172.30.252.114/32 [90/3413504] via 172.28.82.3, 4d00h, Vlan2
                          [90/3413504] via 172.28.80.3, 4d00h, Vlan1
D       172.30.252.112/30 [90/3413504] via 172.28.82.3, 4d00h, Vlan2
                          [90/3413504] via 172.28.80.3, 4d00h, Vlan1
D       172.30.254.24/32 [90/130816] via 172.28.82.3, 7w0d, Vlan2
                         [90/130816] via 172.28.80.3, 7w0d, Vlan1
D       172.30.254.25/32 [90/130816] via 172.28.82.2, 7w0d, Vlan2
                         [90/130816] via 172.28.80.2, 7w0d, Vlan1
D    192.168.202.0/24 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                      [90/28416] via 172.28.82.2, 7w0d, Vlan2
     10.0.0.0/8 is variably subnetted, 4 subnets, 3 masks
S       10.192.254.0/24 [1/0] via 10.192.61.1, GigabitEthernet3/47
S       10.201.0.0/16 [1/0] via 10.192.61.1, GigabitEthernet3/47
S       10.200.1.0/24 [1/0] via 10.192.61.1, GigabitEthernet3/47
C       10.192.61.0/28 is directly connected, GigabitEthernet3/47
D    192.168.203.0/24 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                      [90/28416] via 172.28.82.2, 7w0d, Vlan2
D    192.168.51.0/24 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                     [90/28416] via 172.28.82.2, 7w0d, Vlan2
S*   0.0.0.0/0 [250/0] via 10.192.61.1, GigabitEthernet3/47

Labels:
0 Helpful
9 Replies 9

Henrik Grankvist
Level 4
Level 4

‎05-04-2015 11:19 PM

Hi

Are you redistributing the BGP routes into EIGRP?

0 Helpful

raul saurez
Level 1
Level 1
In response to Henrik Grankvist

‎05-07-2015 07:40 AM

Hello,

Yes I am redistributing BGP into EIGRP. I was able to address the default route situation, however, one of my routers are receiving traffic from the MPLS but not transmitting. My other router is doing both. I tried duplicating the config from router 1 to router 2 but that only brought router 2 down. Right now I have router 2 receiving just not TX. Here is a snip of my weathermap and my diagram. What am I missing?

 

 

Preview file
87 KB
Preview file
38 KB
0 Helpful

Jon Marshall
Hall of Fame
Hall of Fame
In response to raul saurez

‎05-07-2015 07:46 AM

Depends on what the L3 switches see in their routing tables.

Each switch is going to need to see equal cost paths to use both routers.

Not sure why you are using vlans between the switches and routers instead of using L3 links ?

Basicially we don't have enough information to answer your question but the first place to look is on your L3 switches to see what routes they have for remote networks.

Jon

0 Helpful

raul saurez
Level 1
Level 1
In response to raul saurez

‎05-07-2015 07:52 AM

Here is the router and core switch that are working properly

USJONELAWTN01R#sho run | b r e
router eigrp 20
 redistribute static
 redistribute bgp 64523 metric 100000 1 255 1 1500
 network 172.26.80.0 0.0.1.255
 network 172.26.82.0 0.0.0.255
 network 172.26.83.0 0.0.0.255
 network 172.28.0.0
 network 172.30.0.0
 network 192.168.51.0
 network 192.168.202.0
 network 192.168.203.0
 no auto-summary
!
router bgp 64523
 no synchronization
 bgp log-neighbor-changes
 network 172.26.80.0 mask 255.255.254.0
 network 172.26.82.0 mask 255.255.255.0
 network 172.26.83.0 mask 255.255.255.0
 redistribute connected route-map connected
 neighbor 172.30.252.78 remote-as 13979
 neighbor 172.30.252.78 soft-reconfiguration inbound
 neighbor 172.30.252.78 distribute-list 100 in
 no auto-summary

!

ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0 172.28.80.10 250
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/1 172.28.82.10 250
ip route 10.192.254.0 255.255.255.0 GigabitEthernet0/0 172.28.80.10
ip route 10.192.254.0 255.255.255.0 GigabitEthernet0/1 172.28.82.10
ip route 10.200.1.0 255.255.255.0 GigabitEthernet0/0 172.28.80.10
ip route 10.200.1.0 255.255.255.0 GigabitEthernet0/1 172.28.82.10
ip route 10.201.0.0 255.255.0.0 GigabitEthernet0/0 172.28.80.10
ip route 10.201.0.0 255.255.0.0 GigabitEthernet0/1 172.28.82.10
ip route 64.234.192.40 255.255.255.255 Null0
ip route 68.142.83.236 255.255.255.255 Null0
ip route 198.63.196.103 255.255.255.255 Null0

 

TNLAW-TN1COREA#sho run | b r e
router eigrp 20
 redistribute bgp 64523 metric 100000 1 255 1 1500
 network 172.26.80.0 0.0.1.255
 network 172.26.82.0 0.0.0.255
 network 172.26.83.0 0.0.0.255
 network 172.28.0.0
 no auto-summary
!
ip route 0.0.0.0 0.0.0.0 GigabitEthernet3/47 10.192.61.1 250
ip route 10.192.254.0 255.255.255.0 GigabitEthernet3/47 10.192.61.1
ip route 10.200.1.0 255.255.255.0 GigabitEthernet3/47 10.192.61.1
ip route 10.201.0.0 255.255.0.0 GigabitEthernet3/47 10.192.61.1

 

 

Here is the router and core switch that are NOT working properly

USJONELAWTN02R#sho run | b r e
router eigrp 20
 redistribute bgp 64523 metric 100000 1 255 1 1500
 network 172.26.80.0 0.0.1.255
 network 172.26.82.0 0.0.0.255
 network 172.26.83.0 0.0.0.255
 network 172.28.0.0
 network 172.30.0.0
 network 192.168.51.0
 network 192.168.202.0
 network 192.168.203.0
 no auto-summary
!
router bgp 64523
 no synchronization
 bgp log-neighbor-changes
 network 172.26.80.0 mask 255.255.254.0
 network 172.26.82.0 mask 255.255.255.0
 network 172.26.83.0 mask 255.255.255.0
 network 172.28.80.20 mask 255.255.255.255
 redistribute connected
 neighbor 172.30.252.114 remote-as 13979
 neighbor 172.30.252.114 soft-reconfiguration inbound
 neighbor 172.30.252.114 distribute-list 100 in
 no auto-summary
!
ip forward-protocol nd
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0 172.28.80.10 250
ip route 0.0.0.0 0.0.0.0 FastEthernet0/1 172.28.82.10 250
ip route 10.192.254.0 255.255.255.0 FastEthernet0/0 172.28.80.10
ip route 10.192.254.0 255.255.255.0 FastEthernet0/1 172.28.82.10
ip route 10.200.1.0 255.255.255.0 FastEthernet0/0 172.28.80.10
ip route 10.200.1.0 255.255.255.0 FastEthernet0/1 172.28.82.10
ip route 10.201.0.0 255.255.0.0 FastEthernet0/0 172.28.80.10
ip route 10.201.0.0 255.255.0.0 FastEthernet0/1 172.28.82.10
ip route 172.28.80.20 255.255.255.255 FastEthernet0/0.1

 

 

TNLAW-TN1COREB#sho run | b r e
 spanning-tree bpdufilter enable
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/16
 switchport access vlan 90
 switchport mode access
 speed 100
 duplex full
 no cdp enable
 spanning-tree portfast
 spanning-tree bpdufilter enable
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/17
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/18
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/19
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/20
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/21
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/22
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/23
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/24
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/25
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/26
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/27
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/28
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/29
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/30
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/31
 switchport mode access
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/32
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/33
 switchport access vlan 2
 switchport mode access
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/34
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/35
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/36
 description link to temp 2950MDF
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/37
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/38
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/39
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/40
 description link to Local Perle Controller
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/41
 description TEN-BDC-01 Local Server
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/42
 description link to Spry Engery Controller
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/43
 duplex full
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/44
 description link to BB HUB with fiber 10 meg out
 speed 10
 duplex half
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/45
 description link to BB Switch Local
 speed 100
 duplex full
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/46
 description link to Motorola RTR 203 250 dup for backup ---
 shutdown
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/47
 description TRUNK ink to RTR FE 01 Net 80
 switchport trunk encapsulation dot1q
 switchport mode trunk
 speed 100
 duplex full
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface GigabitEthernet3/48
 description CONNECTION TO 2811 ROUTER
 switchport access vlan 2
 speed 100
 duplex full
 spanning-tree portfast
 spanning-tree bpduguard enable
!
interface Vlan1
 ip address 172.28.80.9 255.255.254.0
 no ip route-cache cef
 no ip route-cache
!
interface Vlan2
 ip address 172.28.82.9 255.255.254.0
 no ip route-cache cef
 no ip route-cache
 shutdown
!
interface Vlan601
 description --- WIRELESS EQUIPMENT NETWORK ---
 ip address 172.26.82.3 255.255.255.0
 ip helper-address 172.28.80.20
 no ip proxy-arp
 standby 7 ip 172.26.82.1
 standby 7 preempt
!
interface Vlan602
 description --- WIRELESS USER NETWORK ---
 ip address 172.26.80.3 255.255.254.0
 ip access-group 102 in
 ip helper-address 172.28.80.20
 no ip proxy-arp
 standby 8 ip 172.26.80.1
 standby 8 preempt
!
interface Vlan603
 description --- WIRELESS CORPORATE USER NETWORK ---
 ip address 172.26.83.3 255.255.255.0
 ip helper-address 172.28.80.20
 no ip proxy-arp
 standby 9 ip 172.26.83.1
 standby 9 preempt
!
define interface-range gig2all GigabitEthernet2/1 - 18
!
router eigrp 20
 redistribute bgp 64523 metric 100000 1 255 1 1500
 network 172.26.80.0 0.0.1.255
 network 172.26.82.0 0.0.0.255
 network 172.26.83.0 0.0.0.255
 network 172.28.0.0
 no auto-summary
!

0 Helpful

raul saurez
Level 1
Level 1
In response to raul saurez

‎05-07-2015 07:55 AM

Here is coreb routing table

TNLAW-TN1COREB#sho ip route
Codes: C - connected, S - static, 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
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 172.28.80.3 to network 0.0.0.0

     68.0.0.0/32 is subnetted, 1 subnets
D EX    68.142.83.236 [170/2816] via 172.28.80.2, 21:59:07, Vlan1
     198.63.196.0/32 is subnetted, 1 subnets
D EX    198.63.196.103 [170/2816] via 172.28.80.2, 21:59:07, Vlan1
     64.0.0.0/32 is subnetted, 1 subnets
D EX    64.234.192.40 [170/2816] via 172.28.80.2, 21:59:07, Vlan1
     172.26.0.0/16 is variably subnetted, 3 subnets, 2 masks
C       172.26.82.0/24 is directly connected, Vlan601
C       172.26.83.0/24 is directly connected, Vlan603
C       172.26.80.0/23 is directly connected, Vlan602
     172.28.0.0/16 is variably subnetted, 4 subnets, 2 masks
D       172.28.176.0/23 [90/28416] via 172.28.80.3, 00:36:54, Vlan1
                        [90/28416] via 172.28.80.2, 00:36:54, Vlan1
C       172.28.80.0/23 is directly connected, Vlan1
D       172.28.82.0/23 [90/3072] via 172.28.80.10, 00:36:55, Vlan1
                       [90/3072] via 172.26.83.2, 00:36:55, Vlan603
                       [90/3072] via 172.26.82.2, 00:36:55, Vlan601
                       [90/3072] via 172.26.80.2, 00:36:55, Vlan602
D       172.28.80.20/32 [90/28416] via 172.28.80.3, 00:36:55, Vlan1
     172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
D       172.30.252.78/32 [90/3413504] via 172.28.80.2, 21:59:08, Vlan1
D       172.30.252.76/30 [90/3413504] via 172.28.80.2, 21:59:08, Vlan1
D       172.30.252.114/32 [90/3413504] via 172.28.80.3, 00:36:55, Vlan1
D       172.30.252.112/30 [90/3413504] via 172.28.80.3, 00:36:55, Vlan1
D       172.30.254.24/32 [90/130816] via 172.28.80.3, 00:36:55, Vlan1
D       172.30.254.25/32 [90/130816] via 172.28.80.2, 21:59:08, Vlan1
D    192.168.202.0/24 [90/28672] via 172.28.80.10, 21:59:08, Vlan1
                      [90/28672] via 172.26.83.2, 21:59:08, Vlan603
                      [90/28672] via 172.26.82.2, 21:59:08, Vlan601
                      [90/28672] via 172.26.80.2, 21:59:08, Vlan602
     10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
D EX    10.192.254.0/24 [170/28416] via 172.28.80.2, 00:38:49, Vlan1
D EX    10.201.0.0/16 [170/28416] via 172.28.80.2, 00:38:49, Vlan1
D EX    10.200.1.0/24 [170/28416] via 172.28.80.2, 00:38:49, Vlan1
D    192.168.203.0/24 [90/28672] via 172.28.80.10, 21:59:08, Vlan1
                      [90/28672] via 172.26.83.2, 21:59:08, Vlan603
                      [90/28672] via 172.26.82.2, 21:59:08, Vlan601
                      [90/28672] via 172.26.80.2, 21:59:12, Vlan602
D    192.168.51.0/24 [90/28672] via 172.28.80.10, 21:59:12, Vlan1
                     [90/28672] via 172.26.83.2, 21:59:12, Vlan603
                     [90/28672] via 172.26.82.2, 21:59:12, Vlan601
                     [90/28672] via 172.26.80.2, 21:59:12, Vlan602
D*EX 0.0.0.0/0 [170/26112] via 172.28.80.3, 00:36:59, Vlan1
               [170/26112] via 172.28.80.2, 00:36:59, Vlan1
D EX 200.200.0.0/16 [170/26112] via 172.28.80.3, 00:36:59, Vlan1
                    [170/26112] via 172.28.80.2, 00:36:59, Vlan1
D EX 201.1.0.0/16 [170/26112] via 172.28.80.3, 00:36:59, Vlan1
                  [170/26112] via 172.28.80.2, 00:36:59, Vlan1
D EX 172.16.0.0/12 [170/26112] via 172.28.80.3, 00:36:59, Vlan1
                   [170/26112] via 172.28.80.2, 00:36:59, Vlan1
D EX 198.30.0.0/16 [170/26112] via 172.28.80.3, 00:36:59, Vlan1
                   [170/26112] via 172.28.80.2, 00:36:59, Vlan1
D EX 192.168.0.0/16 [170/26112] via 172.28.80.3, 00:36:59, Vlan1
                    [170/26112] via 172.28.80.2, 00:36:59, Vlan1

 

Here is corea routing table

TNLAW-TN1COREA#sho ip route
Codes: C - connected, S - static, 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
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route

Gateway of last resort is 172.28.82.3 to network 0.0.0.0

     68.0.0.0/32 is subnetted, 1 subnets
D EX    68.142.83.236 [170/2816] via 172.28.82.2, 2d19h, Vlan2
                      [170/2816] via 172.28.80.2, 2d19h, Vlan1
     198.63.196.0/32 is subnetted, 1 subnets
D EX    198.63.196.103 [170/2816] via 172.28.82.2, 2d19h, Vlan2
                       [170/2816] via 172.28.80.2, 2d19h, Vlan1
     64.0.0.0/32 is subnetted, 1 subnets
D EX    64.234.192.40 [170/2816] via 172.28.82.2, 2d19h, Vlan2
                      [170/2816] via 172.28.80.2, 2d19h, Vlan1
     172.26.0.0/16 is variably subnetted, 3 subnets, 2 masks
C       172.26.82.0/24 is directly connected, Vlan601
C       172.26.83.0/24 is directly connected, Vlan603
C       172.26.80.0/23 is directly connected, Vlan602
     172.28.0.0/16 is variably subnetted, 4 subnets, 2 masks
D       172.28.176.0/23 [90/28416] via 172.28.82.3, 00:39:02, Vlan2
                        [90/28416] via 172.28.82.2, 00:39:02, Vlan2
                        [90/28416] via 172.28.80.3, 00:39:02, Vlan1
                        [90/28416] via 172.28.80.2, 00:39:02, Vlan1
C       172.28.80.0/23 is directly connected, Vlan1
C       172.28.82.0/23 is directly connected, Vlan2
D       172.28.80.20/32 [90/28416] via 172.28.82.3, 00:39:01, Vlan2
                        [90/28416] via 172.28.80.3, 00:39:01, Vlan1
     172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
D       172.30.252.78/32 [90/3413504] via 172.28.82.2, 2d19h, Vlan2
                         [90/3413504] via 172.28.80.2, 2d19h, Vlan1
D       172.30.252.76/30 [90/3413504] via 172.28.82.2, 2d19h, Vlan2
                         [90/3413504] via 172.28.80.2, 2d19h, Vlan1
D       172.30.252.114/32 [90/3413504] via 172.28.82.3, 00:39:01, Vlan2
                          [90/3413504] via 172.28.80.3, 00:39:01, Vlan1
D       172.30.252.112/30 [90/3413504] via 172.28.82.3, 00:39:01, Vlan2
                          [90/3413504] via 172.28.80.3, 00:39:01, Vlan1
D       172.30.254.24/32 [90/130816] via 172.28.82.3, 00:39:01, Vlan2
                         [90/130816] via 172.28.80.3, 00:39:01, Vlan1
D       172.30.254.25/32 [90/130816] via 172.28.82.2, 2d19h, Vlan2
                         [90/130816] via 172.28.80.2, 2d19h, Vlan1
D    192.168.202.0/24 [90/28416] via 172.28.82.3, 00:39:34, Vlan2
                      [90/28416] via 172.28.82.2, 00:39:34, Vlan2
     10.0.0.0/8 is variably subnetted, 4 subnets, 3 masks
S       10.192.254.0/24 [1/0] via 10.192.61.1, GigabitEthernet3/47
S       10.201.0.0/16 [1/0] via 10.192.61.1, GigabitEthernet3/47
S       10.200.1.0/24 [1/0] via 10.192.61.1, GigabitEthernet3/47
C       10.192.61.0/28 is directly connected, GigabitEthernet3/47
D    192.168.203.0/24 [90/28416] via 172.28.82.3, 00:39:35, Vlan2
                      [90/28416] via 172.28.82.2, 00:39:35, Vlan2
D    192.168.51.0/24 [90/28416] via 172.28.82.3, 00:39:35, Vlan2
                     [90/28416] via 172.28.82.2, 00:39:35, Vlan2
D*EX 0.0.0.0/0 [170/26112] via 172.28.82.3, 00:39:02, Vlan2
               [170/26112] via 172.28.82.2, 00:39:02, Vlan2
               [170/26112] via 172.28.80.3, 00:39:02, Vlan1
               [170/26112] via 172.28.80.2, 00:39:02, Vlan1
D EX 200.200.0.0/16 [170/26112] via 172.28.82.3, 00:39:02, Vlan2
                    [170/26112] via 172.28.82.2, 00:39:02, Vlan2
                    [170/26112] via 172.28.80.3, 00:39:02, Vlan1
                    [170/26112] via 172.28.80.2, 00:39:02, Vlan1
D EX 201.1.0.0/16 [170/26112] via 172.28.82.3, 00:39:02, Vlan2
                  [170/26112] via 172.28.82.2, 00:39:02, Vlan2
                  [170/26112] via 172.28.80.3, 00:39:02, Vlan1
                  [170/26112] via 172.28.80.2, 00:39:02, Vlan1
D EX 172.16.0.0/12 [170/26112] via 172.28.82.3, 00:39:02, Vlan2
                   [170/26112] via 172.28.82.2, 00:39:02, Vlan2
                   [170/26112] via 172.28.80.3, 00:39:02, Vlan1
                   [170/26112] via 172.28.80.2, 00:39:02, Vlan1
D EX 198.30.0.0/16 [170/26112] via 172.28.82.3, 00:39:02, Vlan2
                   [170/26112] via 172.28.82.2, 00:39:02, Vlan2
                   [170/26112] via 172.28.80.3, 00:39:02, Vlan1
                   [170/26112] via 172.28.80.2, 00:39:02, Vlan1
D EX 192.168.0.0/16 [170/26112] via 172.28.82.3, 00:39:02, Vlan2
                    [170/26112] via 172.28.82.2, 00:39:02, Vlan2
                    [170/26112] via 172.28.80.3, 00:39:02, Vlan1
                    [170/26112] via 172.28.80.2, 00:39:02, Vlan1

 

I dont see an difference

0 Helpful

Jon Marshall
Hall of Fame
Hall of Fame
In response to raul saurez

‎05-07-2015 01:45 PM

I dont see an difference.

Look at the last set of routes, which includes the default route,  to see a difference ie. core B has no path via vlan 2 to one of the MPLS routers.

So any traffic arriving at core B for those remote networks cannot be sent direct to that MPLS router ie. the MPLS router that is not transmitting any traffic.

It is dependant partly on your HSRP setup, assuming you are running HSRP ie. which switch traffic ends up at and what routes that switch then sees.

You seem to be using two vlans to peer with the routers and peer the switches with each as well.

I personally wouldn't do that ie. I would peer the switches with P2P L3 links but you may have a reason for doing it your way.

Jon

 

0 Helpful

Krishnendu AR
Level 1
Level 1

‎05-04-2015 11:19 PM

Hello,

The core switch has got a static default route pointing to 10.192.61.1. It has got a better AD value than the EIGRP routes.

Even if you are redistributing the BGP routes into EIGRP, EIGRP default route will not make it to the routing table because of the higher AD value than the static route.

However, you can view that it the EIGRP topology table. Check 'Sh ip ei topo'.

Krishna

0 Helpful

raul saurez
Level 1
Level 1
In response to Krishnendu AR

‎05-06-2015 09:50 AM

but Eigrp is 90 and the static is 250. ISnt the eigrp better? That static is to the satelite incase the MPLS goes down. How would I set it to make it the last resort?

0 Helpful

Jon Marshall
Hall of Fame
Hall of Fame
In response to raul saurez

‎05-06-2015 09:52 AM

EIGRP will be 170 if you are redistributing from BGP so yes it should replace the static you have.

So, as Henrik asked, are you redistributing BGP into EIGRP ?

Jon

0 Helpful
Customers Also Viewed These Support Documents
Review Cisco Networking products for a $25 gift card