Routing

Hi, do you know where this problem can come from?

It's about a peer to a Tier 2 provider, which shows us its full routing table.

> show log messages

Nov 20 23:30:14 rpd[1437]: bgp_hold_timeout:4169: NOTIFICATION sent to 200.69.129.43 (External AS 11664): code 4 (Hold Timer Expired Error), Reason: holdtime expired for 200.69.129.43 (External AS 11664), socket buffer sndcc: 57 rcvcc: 0 TCP state: 4, snd_una: 4049026493 snd_nxt: 4049026550 snd_wnd: 16023 rcv_nxt: 1889923684 rcv_adv: 1889940068, hold timer out 90s, hold timer remain 0s
Nov 20 23:30:25 rpd[1437]: bgp_pp_recv: rejecting connection from 200.69.129.43 (External AS 11664), peer in state Idle
Nov 20 23:30:25 rpd[1437]: bgp_pp_recv:3592: NOTIFICATION sent to 200.69.129.43+36398 (proto): code 6 (Cease) subcode 5 (Connection Rejected)
Nov 20 23:30:37 rpd[1437]: bgp_pp_recv: rejecting connection from 200.69.129.43 (External AS 11664), peer in state Idle
Nov 20 23:30:37 rpd[1437]: bgp_pp_recv:3592: NOTIFICATION sent to 200.69.129.43+40567 (proto): code 6 (Cease) subcode 5 (Connection Rejected)

neighbor 200.69.129.43 {
        description claro;
        multihop {
            ttl 4;
        }
        import set-local-pref;
        export claro-out;
        peer-as 11664;
    }

Thank You!

Luciano

What is the peer end device? What is the hold time value configured on it?

if required - you may set the hold time value as follows to match..

set protocols bgp group abc hold-time 180

Also what ithe CPU utilization on the box currently?

You may read about hold time in following kb.

https://www.juniper.net/documentation/en_US/junos13.2/topics/reference/configuration-statement/hold-time-edit-protocols-bgp.html

Hi Luciano,

Since the NOTIFICATION is generated by local router with a reason of Hold Timer Expiration. You need to figure out couple of things:

1. Is the Peer sending the Keepalive messsgaes at the agreed interval ?

2. If yes, is it being dropped anywhere on the transport path ?

3. if Keepalives are receieved on the interface locally on the router, then it would be better off to enable BGP traces for this neighbor and check what it shows.

4.  You can take a tcpdump locally on the router on exit interface towards the peer. 

 monitor traffic interface <interface-name> size 9999 no-resolve matching "host 200.69.129.43 && tcp port 179"  detail

You can play around with the above command: https://www.juniper.net/documentation/en_US/junos/topics/reference/command-summary/monitor-traffic.html

Regards,

Hitesh 

show system connections inet extensive – verify the local ports BGP is using. Also check out the MSS
show bgp neighbor <IP>

turn on traceoptions use the detail switch also.