[c-nsp] BGP error with optional attribute

[Harold Ritter (hritter)]

Hi Thiyagarajan,

You are apparently running into CSCtf27303.

https://tools.cisco.com/bugsearch/bug/CSCtf27303

Regards,

Harold



Le 2014-12-19 10:29, « thiyagarajan b » <bn.thiyagarajan at gmail.com> a
écrit :

>Hi everyone,
>
>I have a problem in iBGP between Cisco 7301 and juniper mx series router
>where the BGP got flapped throwing the following error in cisco end:
>
>%BGP-3-NOTIFICATION: received from neighbor 119.227.0.65 3/9 (unsupported
>option specified) 0 bytes
>%BGP-5-ADJCHANGE: neighbor 119.227.0.65 Down BGP Notification received
>
>%BGP-3-NOTIFICATION: received from neighbor 119.227.0.65 6/5 (cease) 0
>bytes
>
>and found the following log in juniper
>
>rpd[1296]: bgp_read_v4_update:9690: NOTIFICATION sent to 210.18.0.181
>(Internal AS 9583): code 3 (Update Message Error) subcode 9 (error with
>optional attribute), Reason: peer 210.18.0.181 (Internal AS 9583) UPDATE -
>NLRI inet6-unicast not negotiated
>rpd[1296]: Received BAD update from 210.18.0.181 (Internal AS 9583),
>family
>inet6-unicast(16), prefix 2a02:2158::/32
>
>So is this problem caused by the prefix 2a02:2158::/32 because of it
>invalid attribute? or is it because of any mismatch SAFI update between
>the
>routers?
>
>Please suggest.
>
>
>Warm Regards,
>Thiyagarajan B.
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/