HelloYou are correct, ACI

MARK HEUZENROEDER · ‎11-18-2014

Hi APICs (Application Policy Infrastructure Colleagues),

I'm finding,

http://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c07-732033.html

... thrilling reading.

I understand ACI uses MP-BGP for propagating routes between Neverland and Boringsville.

Could you please clarify why the ACi CLI output mentions MPLS in,

0.0.0.0/0, ubest/mbest: 2/0
*via 10.0.82.221%overlay-1, [200/1], 1d10h, bgp-100, internal, tag 100 (mpls -vpn)

I didn't think ACI had either labels or switching there-by ?!?!

Cheers, MH

dpita · ‎11-19-2014

Hello

You are correct, ACI uses MP-BGP to propagate routes and there is no MPLS happening in the ACI fabric. That is really strange output. I do not see mpls-vpn anywhere in our lab. Just the standard output one would expect to see.

0.0.0.0/0, ubest/mbest: 1/0

*via 10.0.168.90%overlay-1, [200/1], 6d20h, bgp-100, internal, tag 100

I will follow up with the Document Team as to why that is shown on the overlay routes pointing to other switches in the fabric and hopefully get it straightened out.

Please do not let that deter you from the exciting read! Continue down the rabbit hole into ACI Wonderland!

Thanks for using Cisco Support Forums. Ill reply to this post when I have an answer for you.

MARK HEUZENROEDER · ‎11-19-2014

Thanks heaps Daniel. This reminds me of the Collisions counter in the output of the SHOW INTERFACE for token ring interfaces and many other examples like it. Look forward for hearing from Doc Team via yourself.

cooperb01 · ‎11-20-2014

I am also advertising into OSPF 3.3.3.3 from my router that's connected to leaf 1 and you can see that on leaf 2 there is no 'mpls'

IP Route Table for VRF "Test_Lab:CTX1"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>

1.1.1.1/32, ubest/mbest: 1/0
*via 10.0.184.92%overlay-1, [200/0], 03:51:54, bgp-100, internal, tag 100
2.2.2.2/32, ubest/mbest: 2/0, attached, direct
*via 2.2.2.2, lo5, [1/0], 03:49:03, local
*via 2.2.2.2, lo5, [1/0], 03:49:03, direct
3.3.3.3/32, ubest/mbest: 1/0
*via 10.0.184.92%overlay-1, [200/20], 00:01:04, bgp-100, internal, tag 100
10.1.1.0/24, ubest/mbest: 1/0, attached, direct, pervasive
*via 10.0.240.32%overlay-1, [1/0], 03w22d, static
10.1.1.1/32, ubest/mbest: 1/0, attached
*via 10.1.1.1, vlan36, [1/0], 6d02h, local
10.1.1.32/32, ubest/mbest: 1/0, attached
*via 10.1.1.32, vlan36, [1/0], 6d02h, local
10.2.2.0/24, ubest/mbest: 1/0, attached, direct, pervasive
*via 10.0.240.32%overlay-1, [1/0], 03w22d, static
10.2.2.1/32, ubest/mbest: 1/0, attached
*via 10.2.2.1, vlan36, [1/0], 6d02h, local
10.3.3.0/24, ubest/mbest: 1/0, attached, direct, pervasive
*via 10.0.240.32%overlay-1, [1/0], 03w22d, static
10.3.3.1/32, ubest/mbest: 1/0, attached
*via 10.3.3.1, vlan36, [1/0], 6d02h, local
40.40.40.0/24, ubest/mbest: 1/0, attached, direct, pervasive
*via 10.0.240.32%overlay-1, [1/0], 00:27:09, static
100.1.1.0/30, ubest/mbest: 1/0
*via 10.0.184.92%overlay-1, [200/0], 02:16:24, bgp-100, internal, tag 100
100.1.1.4/30, ubest/mbest: 1/0
*via 10.0.184.92%overlay-1, [200/0], 02:15:54, bgp-100, internal, tag 100
100.1.1.8/30, ubest/mbest: 1/0, attached, direct
*via 100.1.1.9, eth1/25, [1/0], 02:21:04, direct
100.1.1.9/32, ubest/mbest: 1/0, attached
*via 100.1.1.9, eth1/25, [1/0], 02:21:04, local
192.168.10.0/24, ubest/mbest: 1/0
*via 10.0.184.92%overlay-1, [200/20], 00:03:27, bgp-100, internal, tag 100

MARK HEUZENROEDER · ‎11-24-2014

Thanks cooperb01

ACI & 'mpls'