Advertising an Aggregate Route

   This is a simple advertisement of an aggregate route between two routers. Router3 is advertising the aggregate via BGP to Router2. I see that Router2 is receiving the route from Router3 but it's hidden it. When I check why it states that it's "looped". However, I don't see how that can be looped if the AS that Router3 is using is 3333 and the AS the Router2 is using is 2222. Can you guys please check what mistake you see? Thank you

Router2 Output:
root# bgp table Router2.inet.0 hidden
Router2.inet.0: 5 destinations, 5 routes (4 active, 0 holddown, 1 hidden)
Prefix Nexthop MED Lclpref AS path 3333 I
root# run show route protocol bgp table Router2.inet.0 hidden extensive
Router2.inet.0: 5 destinations, 5 routes (4 active, 0 holddown, 1 hidden) (1 entry, 0 announced)
Next hop type: Router
Address: 0x15c0944
Next-hop reference count: 1
Next hop: via lt-0/0/0.6, selected
State: <Hidden Ext>
Peer AS: 3333
Age: 37:00
Task: BGP_3333_2222.
AS path: 3333 I (Looped: 3333) Aggregator: 3333
Router ID:
Router3 Output:
root# show routing-instances Router3
routing-options {
aggregate {
protocols {
bgp {
group ROUTER2 {
type external;
description "Advertise Router3 Loopbacks to Router2";
export ADV_AGR;
peer-as 2222;
local-as 3333;
root# run show interfaces terse routing-instance Router3
Interface Admin Link Proto Local Remote
lt-0/0/0.3 up up inet
lt-0/0/0.7 up up inet
lo0.102 up up inet
root# show policy-options
policy-statement ADV_AGR {
from protocol aggregate;
then accept;

Who is Participating?
vreyesiiConnect With a Mentor Author Commented:
Thank you for your help. But I found the issue. The issue is that since I am using Virtual Instance within a single physical device that router is seeing it's own AS_PATH within the AS_PATH list. To correct it one has to use the "loops" command to allow loops when you are configuring EBGP within a Virtual Instance within a single device.

set protocols bgp group TEST local-as xxxx loops x
Can you attach the full routing tables?

I see you have an additional LT interface, so possibly there are actually "old garbage" left from other exercises...
You should have been able to just configure the AS under routing-options, under each routing-instance. With a different AS for each routing-instance.

Even better is to use an MX and logical-system instead of routing-instance...
vreyesiiAuthor Commented:
This corrected my issue and I was able to see the hidden route in BGP.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.