[j-nsp] Aggregate route BGP tagging
Harry Reynolds
harry at juniper.net
Thu Jul 18 14:24:14 EDT 2013
As it's an aggregate not bgp route on the originating router, what about removing the bgp qualifier or using aggregate?
show route protocol bgp community 1111:3000 all
^^^^^^^
{master}[edit]
regress at mse-b# run show route community 1111:3000 all protocol aggregate detail
inet.0: 8756 destinations, 8756 routes (8756 active, 0 holddown, 0 hidden)
1.0.2.0/24 (1 entry, 1 announced)
*Aggregate Preference: 130
Next hop type: Discard
Address: 0x8d28d84
Next-hop reference count: 1006
State: <Active Int Ext>
Local AS: 65056
Age: 50
Task: Aggregate
Announcement bits (4): 0-KRT 4-LDP 7-Resolve tree 2 8-Resolve tree 3
AS path: I (LocalAgg)
Communities: 1111:1000 1111:3000 1111:6000
Flags: Discard Depth: 0 Active
AS path list:
AS path: I Refcount: 1
Contributing Routes (1):
1.0.2.0/30 proto OSPF
-----Original Message-----
From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Gmail
Sent: Thursday, July 18, 2013 11:11 AM
To: juniper-nsp at puck.nether.net Puck
Subject: [j-nsp] Aggregate route BGP tagging
Hello Everyone,
Looking to get some help on something that may be very simple; I'm trying to advertise aggregate routes based on their community tags, which is working. However, I can't seem to see the aggregate routes when when searching for them on based on communicates on the originating router.
Is there a config line that can use to make these visible?
Any help would be great appreciated.
Thanks,
Michael
output;
user at rtr1# show routing-options aggregate route 192.168.30.0/23 {
community [ 1111:1000 1111:3000 1111:6000 ];
discard;
}
user@ rtr1 > show route 192.168.30.0/23 detail
inet.0: 453579 destinations, 906938 routes (453204 active, 2 holddown, 741 hidden) Restart Complete
192.168.30.0/23 (1 entry, 1 announced)
*Aggregate Preference: 130
Next hop type: Discard
Address: 0x23693e0
Next-hop reference count: 19
State: <Active Int Ext>
Local AS: 1111
Age: 1:14:35
Task: Aggregate
Announcement bits (4): 0-KRT 2-RT 3-BGP_RT_Background 6-Resolve tree 4
AS path: I (LocalAgg)
AS path: Recorded
Communities: 1111:1000 1111:3000 1111:6000
Flags: Discard Depth: 0 Active
AS path list:
AS path: I
AS path: Recorded Refcount: 1
Contributing Routes (1):
192.168.31.0/24 proto Direct
192.168.31.0/24 (1 entry, 1 announced)
*Direct Preference: 0
Next hop type: Interface
Address: 0x27a2494
Next-hop reference count: 2
Next hop: via irb.1, selected
State: <Active Int>
Local AS: 1111
Age: 53w1d 18:50:30
Task: IF
Announcement bits (4): 2-RT 3-BGP_RT_Background 6-Resolve tree 4 7-Aggregate
AS path: I
AS path: Recorded
192.168.31.1/32 (1 entry, 1 announced)
*Local Preference: 0
Next hop type: Local
Address: 0x236a418
Next-hop reference count: 259
Next hop:
Interface: irb.1
State: <Active NoReadvrt Int>
Local AS: 1111
Age: 57w6d 23:52:38
Task: IF
Announcement bits (2): 2-RT 6-Resolve tree 4
AS path: I
AS path: Recorded
user at rtr1> show route protocol bgp community 1111:3000 all
inet.0: 453581 destinations, 906940 routes (453203 active, 4 holddown, 743 hidden) Restart Complete
__juniper_private1__.inet.0: 5 destinations, 6 routes (5 active, 0 holddown, 0 hidden)
__juniper_private2__.inet.0: 1 destinations, 1 routes (0 active, 0 holddown, 1 hidden)
iso.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden) Restart Complete
__juniper_private1__.inet6.0: 4 destinations, 4 routes (4 active, 0 holddown, 0 hidden)
user at rtr1>
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list