Re: [j-nsp] Error BGP RECV Notification code 2 (Open Message Error) subcode 7 (unsupported capability)

2010-05-20 Thread sthaug
> M10i already has many peers that support *2 byte asn only* and is running > without any issues, but *why it is not able to negotiate with Maipu to make > the peer up without disabling the 4byte asn capability*. > > ASFAIK, 4 byte ASN or AS4_PATH is an optional transitive attribute unlike > AS_P

Re: [j-nsp] Error BGP RECV Notification code 2 (Open Message Error) subcode 7 (unsupported capability)

2010-05-20 Thread khagendra dhakal
Hi Chuck, I applied the command (hidden/ undocumented) and it worked. M10i already has many peers that support *2 byte asn only* and is running without any issues, but *why it is not able to negotiate with Maipu to make the peer up without disabling the 4byte asn capability*. ASFAIK, 4 byte AS

Re: [j-nsp] Error BGP RECV Notification code 2 (Open Message Error) subcode 7 (unsupported capability)

2010-05-20 Thread Chuck Anderson
set neighbor w.x.y.z disable-4byte-as On Thu, May 20, 2010 at 09:03:55PM +0545, khagendra dhakal wrote: > Dear all, > > Platform: M10i > JUNOS: JUNOS 9.2R2.15 > > Platform: Maipu 2800 > IOS: rp8-i-6.1.37(xnwt-11).bin), version 6.1.37 > > > PROBLEM: Has anyone had any bad experience on bgp peer

[j-nsp] Error BGP RECV Notification code 2 (Open Message Error) subcode 7 (unsupported capability)

2010-05-20 Thread khagendra dhakal
Dear all, Platform: M10i JUNOS: JUNOS 9.2R2.15 Platform: Maipu 2800 IOS: rp8-i-6.1.37(xnwt-11).bin), version 6.1.37 PROBLEM: Has anyone had any bad experience on bgp peering between the above mentioned Devices with the following error: ? Error: BGP RECV xxx.xxx.xxx.xxx+3407 -> xxx.xxx.xxx.xxx