[j-nsp] RSVP neighbor sequence changes

[Eduardo Barrios]

I remember we shy'd away from using RSVP + BFD on LAG interfaces. The reason was that BFD was only sent on 1 link and we couldn't make sure the other links were reliable for BFD to trigger FRR (other than having lacp detect them). We didn't try other traffic distribution algorithms though.



Not sure how RSVP path refresh messages are sent across LAGs.



Thanks,

Eduardo



Eduardo Barrios, EIT, JNCIP-SP

Telecommunications Specialist

Lower Colorado River Authority  | 3505 Montopolis Dr. |  Austin, TX 78744

512.730.6332 ph









-----Original Message-----

From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Eric Van Tol

Sent: Tuesday, February 04, 2014 8:39 AM

To: juniper-nsp at puck.nether.net

Subject: [External] [j-nsp] RSVP neighbor sequence changes



Hi all,

Two sets of routers in my network keep logging the following message:



rpd[1559]: RPD_RSVP_NBRDOWN: RSVP neighbor x.x.x.x down on interface ae0.1 nbr-type Direct, neighbor seq number change



The interface is different on the two sets of routers, obviously.  All other RSVP sessions seem to work fine:



RSVP neighbor: 6 learned

Address       Idle Up/Dn LastChange HelloInt HelloTx/Rx MsgRcvd

x.x.x.x          0  2/1  12w4d 21:39:06        9 1282869/1282869 376297

x.x.x.x          0  2/1    19:29:02        9  7786/7786 18297

x.x.x.x          0  1/0     3:19:29        9  1322/1322 11192

x.x.x.x          5  2/1     2:54:20        9  1238/1220 1251

x.x.x.x          0  1/0    19:39:33        9  7817/7817 41623

x.x.x.x         10  0/0           8        9  1361/1361 16225



It's that last one which keeps resetting every 9 seconds.  Communication between the opposing interfaces is fine with no errors that I can see.  I've tried disabling RSVP on both sides, but this doesn't resolve the issue when it's re-enabled.



What type of situation can cause both neighbors to constantly change their sequence number?  RFC3209 shows:



"This value MUST change when the sender is reset, when the node reboots, or when communication is lost to the neighboring node and otherwise remains the same."



None of those conditions appear to be getting met, so I'm a bit puzzled.



-evt



_______________________________________________

juniper-nsp mailing list juniper-nsp at puck.nether.net

https://puck.nether.net/mailman/listinfo/juniper-nsp