RSVP including link coloring and bgp senalization process, route refresh issue

last person joined: 4 days ago

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.

Back to discussions

Expand all | Collapse all

RSVP including link coloring and bgp senalization process, route refresh issue

Jump to Best Answer

1. RSVP including link coloring and bgp senalization process, route refresh issue

0 Recommend
jorgeU
Posted 11-08-2016 08:35
| view attached

Reply Reply Privately
Hi ALL,

Topology A - AS (A) uses ISISI + RSVP + LINK COLORING + STATIC LSP with AUTO-BAND configured and at the background we have AUTO-TUNNELS LSP in order to establish back-up tunnels for protection, we use a select policy attached to the RIB to ensure each static LSP to the proper Customer Service

RR Topology A is a two-member cluster same protocols.

Topology B Logical System – AS (B) uses ISIS + LDP.

We are facing different routes refresh behaviors over L3VPN services.

RR Topology B is a two-member cluster same protocols.

Topology A: The route refresh or BGP information about the route is the following or similar to:

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:42:05, localpref 100, from RR1

                    [BGP/170] 01:07:43, localpref 100, from RR2

                   *[BGP/170] 00:37:43, localpref 100, from RR2

                    [BGP/170] 03:27:08, localpref 100, from RR1

                   *[BGP/170] 00:37:43, localpref 100, from RR2

                    [BGP/170] 03:27:08, localpref 100, from RR1

                   *[BGP/170] 00:37:43, localpref 100, from RR2

                    [BGP/170] 03:27:08, localpref 100, from RR1

                   *[BGP/170] 00:37:44, localpref 100, from RR2

                    [BGP/170] 03:27:08, localpref 100, from RR1

                   *[BGP/170] 00:37:43, localpref 100, from RR2

RR information:



                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                 *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w0d 17:08:29, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w0d 17:08:29, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w0d 17:08:29, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w0d 17:08:29, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w0d 17:08:29, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w0d 17:08:29, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:19, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

                   *[BGP/170] 2w6d 21:29:18, MED 50, localpref 100, from RR2 or RR1

                    > to xxx.xxx.xxx.xxx via ge-0/1/0.0, label-switched-path RR2 or RR1:dt-rsvp-AUTO

Topology B: The route refresh or BGP information about the route is more stable.

                *[BGP/170] 20:43:33, localpref 100, from RR1-AS(B)

                    [BGP/170] 20:43:33, localpref 100, from RR2-AS(B)

                   *[BGP/170] 20:43:33, localpref 100, from RR1-AS(B)

                    [BGP/170] 20:43:33, localpref 100, from RR2-AS(B)

                   *[BGP/170] 22:11:58, localpref 100, from RR1-AS(B)

                    [BGP/170] 22:11:58, localpref 100, from RR2-AS(B)

                   *[BGP/170] 07:46:08, localpref 100, from RR1-AS(B)

                    [BGP/170] 07:46:08, localpref 100, from RR2-AS(B)

                   *[BGP/170] 22:41:45, localpref 100, from RR1-AS(B)

                    [BGP/170] 22:41:45, localpref 100, from RR2-AS(B)

                   *[BGP/170] 20:43:33, localpref 100, from RR1-AS(B)

                    [BGP/170] 20:43:33, localpref 100, from RR2-AS(B)

                   *[BGP/170] 20:43:33, localpref 100, from RR1-AS(B)

                    [BGP/170] 20:43:33, localpref 100, from RR2-AS(B)

                   *[BGP/170] 20:43:33, localpref 100, from RR1-AS(B)

                    [BGP/170] 20:43:33, localpref 100, from RR2-AS(B)

                   *[BGP/170] 22:41:45, localpref 100, from RR1-AS(B)

                    [BGP/170] 22:41:45, localpref 100, from RR2-AS(B)

                   *[BGP/170] 20:43:33, localpref 100, from RR1-AS(B)

                    [BGP/170] 20:43:33, localpref 100, from RR2-AS(B)

                   *[BGP/170] 20:43:33, localpref 100, from RR1-AS(B)

                    [BGP/170] 20:43:33, localpref 100, from RR2-AS(B)

                   *[BGP/170] 22:44:48, localpref 100, from RR1-AS(B)

                    [BGP/170] 22:44:48, localpref 100, from RR2-AS(B)

                 *[BGP/170] 22:44:52, localpref 100, from RR1-AS(B)

                    [BGP/170] 22:44:52, localpref 100, from RR2-AS(B)

                   *[BGP/170] 23:40:41, localpref 100, from RR1-AS(B)

                    [BGP/170] 23:40:41, localpref 100, from RR2-AS(B)

                   *[BGP/170] 21:25:41, localpref 100, from RR1-AS(B)

                    [BGP/170] 21:25:41, localpref 100, from RR2-AS(B)

Questions:

1 – Why I’m having different BGP route timers over the different topologies. Just remember both topologies use the same boxes, the same hardware, the same link basically are placed at the same infrastructure.

2 – We are not having a full-mesh of strict LSP towards the RR architecture as you can see learned routes are using full-mesh of auto-tunnel. Which is the best practice on this scenarios?

3 – BGP message signalizations should be placed over an specific LSP?

4 – Could rsvp-AUTO tunnel be the originator of this behavior?

I have run a small lab and saw more or less a similar behavior:

CE à PE BGP SESSION

Refresh each 15 minutes.

We are not using dampening policy, the policy is default.

Default damping information:

Halflife: 15 minutes

Reuse merit: 750 Suppress/cutoff merit: 3000

Maximum suppress time: 60 minutes

Computed values:

    Merit ceiling: 12110

    Maximum decay: 6193

5 – There isn’t any topology change on the lab, Which is the reason of this route refresh?

192.1.1.8/32       *[BGP/170] 00:00:23, localpref 100, from 172.16.0.201

                    [BGP/170] 00:14:59, localpref 100, from 172.16.0.202

192.128.111.0/30   *[BGP/170] 00:00:23, localpref 100, from 172.16.0.201

                    [BGP/170] 00:14:59, localpref 100, from 172.16.0.202

192.165.111.0/30   *[BGP/170] 00:00:23, localpref 100, from 172.16.0.201

                    [BGP/170] 00:14:59, localpref 100, from 172.16.0.202

---(refreshed at 2016-11-07 17:19:02 GMT)---

192.1.1.8/32       *[BGP/170] 00:00:24, localpref 100, from 172.16.0.201

                    [BGP/170] 00:00:00, localpref 100, from 172.16.0.202

192.128.111.0/30   *[BGP/170] 00:00:24, localpref 100, from 172.16.0.201

                    [BGP/170] 00:00:01, localpref 100, from 172.16.0.202

192.165.111.0/30   *[BGP/170] 00:00:24, localpref 100, from 172.16.0.201

                    [BGP/170] 00:00:01, localpref 100, from 172.16.0.202

---(refreshed at 2016-11-07 17:19:03 GMT)---

PE -> RR

bgp.l3vpn.0: 30 destinations, 30 routes (30 active, 0 holddown, 0 hidden)

+ = Active Route, - = Last Active, * = Both

55:601:192.165.111.0/30

                   *[BGP/170] 1d 02:04:15, localpref 100, from 172.16.0.22

                      AS path: I, validation-state: unverified

                    > to 10.0.0.10 via ge-1/1/9.100, label-switched-path 172.16.0.22:dt-rsvp-AUTO
2. RE: RSVP including link coloring and bgp senalization process, route refresh issue

0 Recommend
jorgeU
Posted 11-10-2016 10:44

Reply Reply Privately
We found that using a full mesh LSP between RR and PE avoids this problem, any suggestion on what is going on?
3. RE: RSVP including link coloring and bgp senalization process, route refresh issue

0 Recommend
aarseniev
Posted 11-10-2016 23:30

Reply Reply Privately
Hello,

The BGP reflector for VPLS/L3VPN/L2VPN families has to have PE loopback /32 addresses in table inet.3 (and inet6.3 if You are doing 6PE/6VPE) to resolve next-hops. And that's what Your "full mesh LSP between PE & RR" does.

You can circumvent this requirement by configuring IGP /32 route leak from inet.0 to inet.3/inet6.3, or configuring a default/summary route in inet.3/inet6.3.

HTH

Thx

Alex
4. RE: RSVP including link coloring and bgp senalization process, route refresh issue

0 Recommend
jorgeU
Posted 11-11-2016 04:41

Reply Reply Privately
HI,

by research I have found than an expected behavior for auto mesh LSPs that doesn't carry any traffic or in other words are inactive they will go down after 15 minutes.

This timer can be modified under this:

set routing-options dynamic-tunnels inactivity-timeout <60-900 seconds> this is a hidden command, the good news is I have decreased the time and match the BGP route refresh:

---(refreshed at 2016-11-11 02:36:12 GMT)---

192.1.1.8/32       *[BGP/170] 00:00:57, localpref 100, from 172.16.0.202

192.128.111.0/30   *[BGP/170] 00:00:57, localpref 100, from 172.16.0.202

192.165.111.0/30   *[BGP/170] 00:00:57, localpref 100, from 172.16.0.202

---(refreshed at 2016-11-11 02:36:13 GMT)---

192.1.1.8/32       *[BGP/170] 00:00:58, localpref 100, from 172.16.0.202

192.128.111.0/30   *[BGP/170] 00:00:58, localpref 100, from 172.16.0.202

192.165.111.0/30   *[BGP/170] 00:00:58, localpref 100, from 172.16.0.202

---(refreshed at 2016-11-11 02:36:14 GMT)---

192.1.1.8/32       *[BGP/170] 00:00:59, localpref 100, from 172.16.0.202

192.128.111.0/30   *[BGP/170] 00:00:59, localpref 100, from 172.16.0.202

192.165.111.0/30   *[BGP/170] 00:00:59, localpref 100, from 172.16.0.202

---(refreshed at 2016-11-11 02:36:15 GMT)---

192.1.1.8/32       *[BGP/170] 00:00:01, localpref 100, from 172.16.0.202

192.128.111.0/30   *[BGP/170] 00:00:01, localpref 100, from 172.16.0.202

192.165.111.0/30   *[BGP/170] 00:00:01, localpref 100, from 172.16.0.202

---(refreshed at 2016-11-11 02:36:16 GMT)---

192.1.1.8/32       *[BGP/170] 00:00:02, localpref 100, from 172.16.0.202

192.128.111.0/30   *[BGP/170] 00:00:02, localpref 100, from 172.16.0.202

192.165.111.0/30   *[BGP/170] 00:00:02, localpref 100, from 172.16.0.202

---(refreshed at 2016-11-11 02:36:17 GMT)---

192.1.1.8/32       *[BGP/170] 00:00:03, localpref 100, from 172.16.0.202

192.128.111.0/30   *[BGP/170] 00:00:03, localpref 100, from 172.16.0.202

192.165.111.0/30   *[BGP/170] 00:00:03, localpref 100, from 172.16.0.202

jorge@MX5_1> show configuration routing-options dynamic-tunnels

AUTO {

    rsvp-te AUTO {

        label-switched-path-template {

            t_AUTO;

        }

        destination-networks {

            172.16.0.0/24;

        }

    }

}

inactivity-timeout 60; (hidden command) .

Any idea of what is happenning?
5. RE: RSVP including link coloring and bgp senalization process, route refresh issue
Best Answer

0 Recommend
jorgeU
Posted 11-14-2016 19:27

Reply Reply Privately
PR1202926

Full mesh required to RR until version 16.1R4.

regards.

Routing

RSVP including link coloring and bgp senalization process, route refresh issue

jorgeU11-08-2016 08:35

jorgeU11-10-2016 10:44

aarseniev11-10-2016 23:30

jorgeU11-11-2016 04:41

jorgeU11-14-2016 19:27Best Answer

1. RSVP including link coloring and bgp senalization process, route refresh issue

2. RE: RSVP including link coloring and bgp senalization process, route refresh issue

3. RE: RSVP including link coloring and bgp senalization process, route refresh issue

4. RE: RSVP including link coloring and bgp senalization process, route refresh issue

5. RE: RSVP including link coloring and bgp senalization process, route refresh issue Best Answer

5. RE: RSVP including link coloring and bgp senalization process, route refresh issue
Best Answer