North American Network Operators Group
Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: BGP unsupported capability code

  • From: Mike White
  • Date: Mon Aug 21 12:55:50 2006
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=1zjpTsJMEylyvEOL2vSfYZNmBUlfH1yq8A+e+ADhTU9CGyTsxLRjqebd014c7xcBBLo7uc3/2VabUlQAGNcGEZlj+qObqfs4I4oD08xwZgexPVtK2DPrAqrr5SY70JYjSD2PlVuhwAC/0FwYQwU1P45oj981+R5y7CFa93FktXg= ;
I recently implemented BGP graceful restart capability in a custom BGP
app and encountered the same notification.  By looking at the
capabilities being advertised by the router, and advertising various
subsets of those capabilities, I narrowed it down to the MPLS
capability.  It turned out the router deemed MPLS capability as a
prerequisite for graceful restart.  Adding the MPLS IPv4 unicast
capability to the OPEN message along with the graceful restart
capability fixed things for me.

Hope this helps.
- Mike