BGP Notification Message

Unanswered Question
Nov 26th, 2008
User Badges:

We partner with other MPLS providers via NNI to offer MPLS connectivity to customers.


CPE Logs:


Nov 27 07:39:57.432 TOKYO: %BGP-3-NOTIFICATION: received from neighbor 10.101.63.146 6/6 (cease) 0 bytes

Nov 27 07:39:57.432 TOKYO: %BGP-5-ADJCHANGE: neighbor 10.101.63.146 Down BGP Notification received

Nov 27 07:40:00.835 TOKYO: %BGP-5-ADJCHANGE: neighbor 10.101.63.146 Up


CPE BGP Config:


router bgp 65555

no synchronization

bgp log-neighbor-changes

network 10.253.1.1 mask 255.255.255.255

network 192.168.8.0

neighbor 10.101.63.146 remote-as 10134

no auto-summary



Recently we have been getting this message in our CPE which connects to the PE of international provider from where MPLS cloud starts. We manage customer CPEs. Since we have BGP configured between CPE and PE we are getting this kind of BGP notification message. We have 2-3 other customers running static routes between CPE-PE where we are not getting any logs in CPE. But for all these CPEs, we are receiving BGP route reset in our management router which is also connected to the same partner's MPLS cloud just for management purpose. I strongly suspect the issue is with local loop(Between CPE-PE). We have done BERT tests on local loop, but didnt yield any result may be because the issue happens once in a day.


Anybody here experienced similar problems?? How to resolve this?


Thanks in advance


AneesH

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Giuseppe Larosa Wed, 11/26/2008 - 23:55
User Badges:
  • Super Silver, 17500 points or more
  • Hall of Fame,

    Founding Member

Hello Aneesh,

depending on the platform you use for CPE you may need QoS to prioritize BGP packets exiting the interface during link congestion: usually you receive the BGP notification because the hold-time expired on the neighbor without seeing any BGP keepalive.

This can be caused by line errors but also by a congested link where BGP packets sit in a queue.


However, the subcode is cease and not expired:

Nov 27 07:39:57.432 TOKYO: %BGP-3-NOTIFICATION: received from neighbor 10.101.63.146 6/6 >>>(cease) 0 bytes


this points to the neighbor thinking of having received a not acceptable BGP packet.


Hope to help

Giuseppe


rajivrajan1 Thu, 11/27/2008 - 00:00
User Badges:
  • Bronze, 100 points or more

Hi,

can u post


debug ip bgp neigh &

sh tcp brief


any port blocking ?

so all 170 tcp connection established ?

any authentication issue ?



milan.kulik Thu, 11/27/2008 - 05:05
User Badges:
  • Red, 2250 points or more

Hi,


are you really using

router bgp 65555 ?

Or are you just masking the real AS number used in your config?


BR,

Milan



deshpande-s Sat, 11/29/2008 - 09:25
User Badges:

Hi Aneesh,

i am oberving the time to BGP Neighbourship come up that is only 3sec,however if there is any fluctuations then it takes atlest 240sec to eshtablish the session.

kindly confirm that whether BGP timers are configured on default basis.

kindly reply whether my suggestion is useful ot not.

Actions

This Discussion