Re: EIGRP Routing to MPLS via Cisco 9500 Core

navydivervet · ‎02-12-2019

From Cat 9500 Cores, trying to reach MPLS circuit connected on adjacent Cat 9300. An additional pair of Cat 9500s and 9300 (in separate MDF), are connected to a backup LTE circuit. Routing keeps defaulting to LTE circuit, despite various routing and metric adjustments. Routers are vendor-managed and connectivity from switches are via access vlan. Thoughts/advice?

Jon Marshall · ‎02-12-2019

Not really a lot to go on.

Are you using BGP for MPLS and redistributing into EIGRP ?

What are you doing across the backup link in terms of routing ?

Jon

Jon Marshall · ‎02-12-2019

Sorry, forgot the obvious one.

What do the routing and EIGRP topology tables show ?

Jon

navydivervet · ‎02-12-2019

Thanks for your help. No BGP. The 9300 Switch port is just configured for an access vlan 82, to the vendor router. On both the MPLS and LTE circuits.

MDF2SWI01#sh ip ei top
EIGRP-IPv4 Topology Table for AS(100)/ID(10.80.70.17)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status

P 10.80.52.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.80.43.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.80.38.0/24, 1 successors, FD is 2816
via Connected, Vlanx
P 10.80.55.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.80.49.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.99.85.128/28, 1 successors, FD is 2816
via Connected, Vlan82
P 10.80.41.0/24, 1 successors, FD is 2816
via Connected, Vlan500
P 10.80.63.0/24, 1 successors, FD is 2816
via Connected, Vlan121
P 10.80.60.0/24, 1 successors, FD is 2816
via Connected, Vlan118
P 10.80.56.0/24, 1 successors, FD is 2816
via Connected, Vlan114
P 10.80.32.0/24, 1 successors, FD is 2816
via Connected, Vlan10
P 10.80.64.0/24, 1 successors, FD is 2816
via Connected, Vlan310
P 10.80.35.0/24, 1 successors, FD is 2816
via Connected, Vlan135
P 10.80.39.0/24, 1 successors, FD is 2816
via Connected, Vlan300
P 10.80.58.0/24, 1 successors, FD is 2816
via Connected, Vlan116
P 10.80.65.0/24, 1 successors, FD is 2816
via Connected, Vlan320
P 10.80.50.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.80.62.0/24, 1 successors, FD is 2816
via Connected, Vlan120
P 10.80.40.0/24, 1 successors, FD is 2816
via Connected, Vlan400
P 10.80.46.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.80.37.0/24, 1 successors, FD is 2816
via Connected, Vlan137
P 10.80.61.0/24, 1 successors, FD is 2816
via Connected, Vlan119
P 10.99.81.128/28, 1 successors, FD is 2816
via Connected, Vlan801
P 10.80.45.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.80.70.8/30, 1 successors, FD is 3072
via 10.80.32.130 (3072/2816), Vlan10
P 10.80.36.0/24, 1 successors, FD is 2816
via Connected, Vlan136
P 10.80.47.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.80.48.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 0.0.0.0/0, 1 successors, FD is 2562560256, tag is 65000
via 10.99.85.129 (2562560256/2562560000), Vlan82
P 10.80.42.0/24, 1 successors, FD is 2816
via Connected, Vlan200
P 10.80.33.0/24, 1 successors, FD is 2816
via Connected, Vlan20
P 10.80.57.0/24, 1 successors, FD is 2816
via Connected, Vlan115
P 10.80.54.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.50.192.218/32, 1 successors, FD is 82688, tag is 65000
via 10.99.85.130 (82688/82432), Vlan82
P 10.80.34.0/24, 1 successors, FD is 2816
via Connected, Vlan125
P 10.80.51.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.80.71.14/32, 1 successors, FD is 3328
via 10.80.32.130 (3328/3072), Vlan10
P 10.80.44.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10
P 10.80.66.0/24, 1 successors, FD is 2816
via Connected, Vlan333
P 10.80.59.0/24, 1 successors, FD is 2816
via Connected, Vlan117
P 10.80.70.0/30, 1 successors, FD is 3072
via 10.80.32.130 (3072/2816), Vlan10
P 10.80.53.0/24, 2 successors, FD is 3072
via 10.99.85.140 (3072/2816), Vlan82
via 10.80.32.252 (3072/2816), Vlan10

MDF2SWI01#sh ip route ei

Gateway of last resort is 10.99.85.129 to network 0.0.0.0

D*EX 0.0.0.0/0 [170/2562560256] via 10.99.85.129, 05:21:41, Vlan82
10.0.0.0/8 is variably subnetted, 65 subnets, 4 masks
D EX 10.50.192.218/32 [170/82688] via 10.99.85.130, 05:05:33, Vlan82
D 10.80.43.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.44.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.45.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.46.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.47.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.48.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.49.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.50.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.51.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.52.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.53.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.54.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.55.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.70.0/30 [90/3072] via 10.80.32.130, 07:03:14, Vlan10
D 10.80.70.8/30 [90/3072] via 10.80.32.130, 07:03:14, Vlan10
D 10.80.71.14/32 [90/3328] via 10.80.32.130, 07:03:14, Vlan10

MDF2SWI01#sh ip route

Gateway of last resort is 10.99.85.129 to network 0.0.0.0

D*EX 0.0.0.0/0 [170/2562560256] via 10.99.85.129, 05:21:59, Vlan82
10.0.0.0/8 is variably subnetted, 65 subnets, 4 masks
D EX 10.50.192.218/32 [170/82688] via 10.99.85.130, 05:05:51, Vlan82
C 10.99.81.128/28 is directly connected, Vlan801
L 10.99.81.141/32 is directly connected, Vlan801
C 10.99.85.128/28 is directly connected, Vlan82
L 10.99.85.141/32 is directly connected, Vlan82
C 10.80.32.0/24 is directly connected, Vlan10
L 10.80.32.253/32 is directly connected, Vlan10
C 10.80.33.0/24 is directly connected, Vlan20
L 10.80.33.253/32 is directly connected, Vlan20
C 10.80.34.0/24 is directly connected, Vlan125
L 10.80.34.253/32 is directly connected, Vlan125
C 10.80.35.0/24 is directly connected, Vlan135
L 10.80.35.253/32 is directly connected, Vlan135
C 10.80.36.0/24 is directly connected, Vlan136
L 10.80.36.253/32 is directly connected, Vlan136
C 10.80.37.0/24 is directly connected, Vlan137
L 10.80.37.253/32 is directly connected, Vlan137
C 10.80.38.0/24 is directly connected, Vlanx
L 10.80.38.253/32 is directly connected, Vlanx
C 10.80.39.0/24 is directly connected, Vlan300
L 10.80.39.253/32 is directly connected, Vlan300
C 10.80.40.0/24 is directly connected, Vlan400
L 10.80.40.253/32 is directly connected, Vlan400
C 10.80.41.0/24 is directly connected, Vlan500
L 10.80.41.253/32 is directly connected, Vlan500
C 10.80.42.0/24 is directly connected, Vlan200
L 10.80.42.253/32 is directly connected, Vlan200
D 10.80.43.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.44.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.45.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.46.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.47.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.48.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.49.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.50.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.51.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.52.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.53.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.54.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
D 10.80.55.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10
[90/3072] via 10.99.85.140, 2w5d, Vlan82
C 10.80.56.0/24 is directly connected, Vlan114
L 10.80.56.253/32 is directly connected, Vlan114
C 10.80.57.0/24 is directly connected, Vlan115
L 10.80.57.253/32 is directly connected, Vlan115
C 10.80.58.0/24 is directly connected, Vlan116
L 10.80.58.253/32 is directly connected, Vlan116
C 10.80.59.0/24 is directly connected, Vlan117
L 10.80.59.253/32 is directly connected, Vlan117
C 10.80.60.0/24 is directly connected, Vlan118
L 10.80.60.253/32 is directly connected, Vlan118
C 10.80.61.0/24 is directly connected, Vlan119
L 10.80.61.253/32 is directly connected, Vlan119
C 10.80.62.0/24 is directly connected, Vlan120
L 10.80.62.253/32 is directly connected, Vlan120
C 10.80.63.0/24 is directly connected, Vlan121
L 10.80.63.253/32 is directly connected, Vlan121
C 10.80.64.0/24 is directly connected, Vlan310
L 10.80.64.253/32 is directly connected, Vlan310
C 10.80.65.0/24 is directly connected, Vlan320
L 10.80.65.253/32 is directly connected, Vlan320
C 10.80.66.0/24 is directly connected, Vlan333
L 10.80.66.253/32 is directly connected, Vlan333
D 10.80.70.0/30 [90/3072] via 10.80.32.130, 07:03:33, Vlan10
D 10.80.70.8/30 [90/3072] via 10.80.32.130, 07:03:33, Vlan10
D 10.80.71.14/32 [90/3328] via 10.80.32.130, 07:03:33, Vlan10

Jon Marshall · ‎02-12-2019

Probably going need to a quick schematic with some IPs showing the layout.

Also can you pick just one route that you want reached via MPLS and show the route entries and topology entry off each switch.

Jon

navydivervet · ‎02-12-2019

I have Cat 9500 as my Core/L3 device. The vendor router was not compatible with the sfp on the core switch, so it is connected to a downstream Cat 9300. The port is just an access port on vlan 82, for MPLS connectivity to a vendor router. Trying to use EIGRP to route all traffic through the MPLS circuit, but for some reason, it keeps routing to the other MDF, to the backup LTE circuit, which has the exact switch connectivity. Guess I'm questioning, or seeking an example of the proper EIGRP configs on the Core 9500, and the Cat 9300 switches

MDF 1)

Core 9500 connects to 9300 via L2 etherchannel

9300 connects to MPLS Vendor router, via access port vlan 82

MDF 2)

Core 9500 connects to 9300 via L2 etherchannel

9300 connects to LTE Vendor router, via access port vlan 82

MDFs are connected to each other via L2 etherchannel. Trying to get all traffic to route to MPLS, not LTE. Was routing properly, but changed for some unknown reason

Jon Marshall · ‎02-13-2019

Apologies for the delay in replying, been a bit busy.

You should be able to use delay or if not use an offset list to choose the routes you want to use, it is just a question of working out where to apply the configuration

As the 9300s are interconnected is the path from the 9500 direct to the LTE 9300 and then the LTE router or is to the MPLS 9300 , then the LTE 9300 and then the LTE router ?

In addition are you using the same vlan to connect to both 9300s from the 9500 ?

Jon

navydivervet · ‎02-13-2019

Appreciate your help, Jon. The 9500 stacks are in separate MDFs, with an L2 connection between them, with all vlans. The SVIs are configured in HSRP on the 9500s.

A 9300 is connected to each 9500, layer 2, with multiple vlans. The MPLS and LTE circuits are on different 9300s, in separate MDFs, on an access port to a single vlan.

I tried a major delay difference on the interfaces, which seemed to work for several days. Can't figure out why it recently jumped to the LTE path, when no changes were made.

The carrier may not be using the correct advertised networks, as they say they keep losing neighborship.

Jon Marshall · ‎02-13-2019

Are the 9300s doing any routing or are they just L2 switches ?

And if they are just L2 are both 9500s using the same vlan (vlan 82) to peer with their equivalent provider router ?

Finally (for the moment !) which interface(s) did you apply delay to ?

Apologies for all the questions but still trying to work out the topology.

Jon