Skip to main content

Flapping LDP/RSVP on Olive

I had a strange problem where the LDP and RSVP was flapping on JunOS/Olive and I think I managed to fix it by changing the driver from e1000 to i82559er and lo0.0 with 127.0.0.1.  I don't want to spend more time investigating it but if someone have similar problem at least this comment could be a good start.





root@jr2> 
*** MPLS ***
May 21 14:27:21.472443 Session 4.4.4.4 hold timer expired in Operational state
May 21 14:27:21.473451 Connection 4.4.4.4 state Open -> Closed
May 21 14:27:21.473838 Session 4.4.4.4 GR state Operational -> Nonexistent
May 21 14:27:21.473923 Session 4.4.4.4 state Operational -> Closing
May 21 14:27:21.474054 LDP session 4.4.4.4 is down, reason: hold time expired
May 21 14:27:21.474364 RPD_LDP_SESSIONDOWN: LDP session 4.4.4.4 is down, reason: hold time expired
May 21 14:27:21.475567 Session 4.4.4.4 state Closing -> Nonexistent
May 21 14:27:21.476180 CHANGE   317024 /52          nhid 580 gw 10.10.24.4      LDP      pref 9/0 metric 1/0 em2.0 <Delete Int>
May 21 14:27:21.476333 rt_close: 1/1 route proto LDP
May 21 14:27:21.476333 
May 21 14:27:21.476597 CHANGE   317008 /52          nhid 579 gw 10.10.24.4      LDP      pref 9/0 metric 1/0 em2.0 <Delete Int>
May 21 14:27:21.476665 rt_close: 1/1 route proto LDP
May 21 14:27:21.476665 
May 21 14:27:21.476838 CHANGE   316992 /52          nhid 577 gw 10.10.24.4      LDP      pref 9/0 metric 1/0 em2.0 <Delete Int>
May 21 14:27:21.476954 CHANGE   316992 /56          nhid 578 gw 10.10.24.4      LDP      pref 9/0 metric 1/0 em2.0 <Delete Int>
May 21 14:27:21.477552 rt_close: 2/1 routes proto LDP
May 21 14:27:21.477552 
May 21 14:27:21.483708 Added route defer timer for  3.3.3.3/32
May 21 14:27:21.483923 Added route defer timer for  4.4.4.4/32
May 21 14:27:21.484062 Added route defer timer for  5.5.5.5/32
May 21 14:27:23.858507 RPD_LDP_NBRDOWN: LDP neighbor 10.10.24.4 (em2.0) is down
May 21 14:27:23.858920 Session 4.4.4.4 state Nonexistent -> Closing
May 21 14:27:23.859360 Session 4.4.4.4 state Closing -> Nonexistent
May 21 14:27:25.714548 Incoming connect from 4.4.4.4
May 21 14:27:25.715245 Incoming connect from 4.4.4.4
May 21 14:27:25.715536 Connection 4.4.4.4 state Closed -> Open
May 21 14:27:25.716483 LDP: Init without session from 4.4.4.4
May 21 14:27:25.716986 Connection 4.4.4.4 state Open -> Closed
May 21 14:27:27.201577 New adjacency 10.10.24.4 (em2.0), xport 4.4.4.4
May 21 14:27:27.202182 RPD_LDP_NBRUP: LDP neighbor 10.10.24.4 (em2.0) is up
May 21 14:27:27.202364 New session, 2.2.2.2:0-4.4.4.4:0
May 21 14:27:27.202429 Session 4.4.4.4 rsync state: Invalid -> Not in sync
May 21 14:27:27.202555 Enabled fast hellos on interface em2.0
May 21 14:27:28.673990 Disabled fast hellos on interface em2.0
May 21 14:27:34.176050 Incoming connect from 4.4.4.4
May 21 14:27:34.176795 Incoming connect from 4.4.4.4
May 21 14:27:34.177075 Connection 4.4.4.4 state Closed -> Open
May 21 14:27:34.178045 Session 4.4.4.4 state Nonexistent -> Initialized
May 21 14:27:34.178116 Session 4.4.4.4 state Initialized -> OpenRec
May 21 14:27:34.178199 Session 4.4.4.4 GR state Nonexistent -> Operational
May 21 14:27:34.181493 Session 4.4.4.4 state OpenRec -> Operational
May 21 14:27:34.181945 RPD_LDP_SESSIONUP: LDP session 4.4.4.4 is up
May 21 14:27:34.189901 Deleted route defer timer for  4.4.4.4/32
May 21 14:27:34.190504 CHANGE   317040 /52          nhid 0 gw 10.10.24.4      LDP      pref 9/0 metric 1/0 em2.0 <Active Int>
May 21 14:27:34.190638 ADD      317040 /52          nhid 0 gw 10.10.24.4      LDP      pref 9/0 metric 1/0 em2.0 <Active Int>
May 21 14:27:34.190801 CHANGE   317040 /56          nhid 0 gw 10.10.24.4      LDP      pref 9/0 metric 1/0 em2.0 <Active Int>
May 21 14:27:34.190906 ADD      317040 /56          nhid 0 gw


Labels:

Popular posts from this blog

IOS on Unix (IOU)

source http://evilrouters.net/2011/01/18/cisco-iou-faq/ What is IOU? From the Cisco Engineering Education web site (a long time ago): IOS on Unix (IOU) is a fully working version of IOS that runs as a user mode UNIX (Solaris) process. IOU is built as a native Solaris image and run just like any other program. IOU supports all platform independent protocols and features. What operating systems does IOU run on? It is my understanding that, initially, IOU was Solaris (SPARC) only. Nowadays, however, there are also builds for OS X and Linux. Similar to dynamips, IOU allows you to build out a network topology on a computer, without the need for physical routers. This is useful for validating designs, proof-of-concept testing, and certification self-study. Is my system compatible with IOU? You will need to be running the operating system that your IOU image were built for, obviously. Other than that, there are no special requirements to run IOU. It is not very CPU- or memory-intensive, unlik...
Read more >>

Beijing - China

I am not sure how to describe Beijing China, maybe everyone who goes their simply use the world 'Amazing' because it will be nearly impossible to describe it. I had a personal driver and tour guide which significantly simplify my trip around.  Of course, it was a business trip and I didn't have as much time as I needed to see everything from Beijing but I will try to share couple of pictures and some of my impressions. I will start with the food.  I remember when I was younger there was so many Chines restaurants in the neighbourhood and I could eat Chines food everyday, and at every time - my parents were joking that I will became a Chines if I continue to eat only Chines, but it was so good and I didn't care ;-)  In Beijing I tried so many different things and I am amazed by the quality of the food, and most amazingly I didn't have any problems with my stomach - which was a good sign ;-) . I uploaded few photos from my album, which are from different places I ...
Read more >>

Juniper IS-IS summary

##################################################################################################### ## ISIS ##################################################################################################### # Be sure to set family iso on the interface to be placed into ISIS set interfaces <interface> family iso # By default Junos places interfaces as L1/L2 # Default route leaking:         L1 to L2 - all internal routes         L2 to L1 - 0/0 route # L1/L2 will send the attached-bit down to L1 and it will act as a NSSA-like area.  When the L1 interface # receives the attached-bit it will inject a 0/0 route into the RIB point to the L1/L2 interface. # To disable the attached bit use: set protocols isis ignore-attached-bit # Be careful with the "interface all" command, as it may have some unexpected consequences such as trying # to establish a neighbor on your fxp0 management...
Read more >>