Re: [j-nsp] RSVP neighbor sequence changes
Duplicate IP on this shared segment? Just my guess... HTH Thanks Alex On 04/02/2014 14:38, Eric Van Tol wrote: 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:069 1282869/1282869 376297 x.x.x.x 0 2/119:29:029 7786/7786 18297 x.x.x.x 0 1/0 3:19:299 1322/1322 11192 x.x.x.x 5 2/1 2:54:209 1238/1220 1251 x.x.x.x 0 1/019:39:339 7817/7817 41623 x.x.x.x 10 0/0 89 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] RSVP neighbor sequence changes
-Original Message- From: Alex Arseniev [mailto:arsen...@btinternet.com] Sent: Wednesday, February 05, 2014 8:08 AM To: Eric Van Tol; juniper-nsp@puck.nether.net Subject: Re: [j-nsp] RSVP neighbor sequence changes Duplicate IP on this shared segment? Just my guess... HTH Thanks Alex Good suggestion, but alas, that was not the problem. This morning, I ended up just disabling the interfaces entirely, then re-enabling them and the issue stopped occurring. Thanks, evt ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] RSVP neighbor sequence changes
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-boun...@puck.nether.net] On Behalf Of Eric Van Tol Sent: Tuesday, February 04, 2014 8:39 AM To: juniper-nsp@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:069 1282869/1282869 376297 x.x.x.x 0 2/119:29:029 7786/7786 18297 x.x.x.x 0 1/0 3:19:299 1322/1322 11192 x.x.x.x 5 2/1 2:54:209 1238/1220 1251 x.x.x.x 0 1/019:39:339 7817/7817 41623 x.x.x.x 10 0/0 89 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@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] RSVP neighbor sequence changes
On Wednesday, February 05, 2014 07:30:58 PM Eduardo Barrios wrote: 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. You might be interested in Micro BFD which has arrived to Junos 13.3: http://tinyurl.com/mmzrene Mark. signature.asc Description: This is a digitally signed message part. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
