nandakishoreie14 at gmail
Mar 28, 2012, 8:43 AM
Post #4 of 4
(225 views)
Permalink
|
|
Re: Capabilities Not Negotiated] BGPD not sending NOTIFICATION message with Error Subcode Unsupported Optional Parameter
[In reply to]
|
|
Hi Nick,
Below is the bug details:
*Bug 716 <https://bugzilla.quagga.net/show_bug.cgi?id=716>* - [Capabilities
Not Negotiated] BGPD not sending NOTIFICATION message with Error Subcode
Unsupported Optional Parameter.
link to access bug: https://bugzilla.quagga.net/show_bug.cgi?id=716
Regards,
Nanda Kishore P
On Wed, Mar 28, 2012 at 7:55 PM, Nick Hilliard <nick [at] inex> wrote:
> On 28/03/2012 06:55, Nanda Kishore wrote:
> > You are right. But in this scenario TR1 and TR2 establishes BGP session.
> > Hence, BGP negotiation is not failed.
>
> Sorry, my misunderstanding. I think you're correct here after all - the
> .pcap is pretty clear on what's happening. Yes, the negotiation should
> fail rather than accepting the negotiation and failing once the first
> UPDATE comes through. Can you submit this to bugzilla, including the
> .pcap?
>
> Nick
>
>
> >
> > Please find the attached captured packets between TR1 and TR2.
> >
> >
> >
> > Regards,
> >
> > Nanda Kishore
> >
> > From: Nick Hilliard [mailto:nick [at] foobar] <mailto:[mailto:
> nick [at] foobar]>
> >
> > Sent: Wednesday, March 14, 2012 6:15 PM
> >
> > To: Quagga Users Lists
> >
> > Cc: Krishna P Vamsi-B38510
> >
> > Subject: Re: [quagga-users 12785] Re: Capabilities Not Negotiated] BGPD
> not
> > sending NOTIFICATION message with Error Subcode Unsupported Optional
> Parameter
> >
> >
> >
> > On 14/03/2012 11:56, Krishna P Vamsi-B38510 wrote:
> >
> >> Please find the problem that we are observing at out lab, please
> >
> >> respond if there are any suggestions
> >
> >
> >
> >> 2. TR1 does not support Capabilities Negotiation.
> >
> >
> >
> > strict-capability-match allows capabilities negotiation, but will cause
> the
> > connection to be reset if the capabilities are different on each side.
> In
> > your test rig, you've configured one side to have capabilities and not
> the
> > other. Therefore, BGP negotiation will fail.
> >
> >
> >
> > I.e. it's your configuration which is buggy, not quagga.
> >
> >
> >
> > Nick
> >
> >
> >
> >
> >
> >
> >
> > On Wed, Mar 14, 2012 at 5:26 PM, Krishna P Vamsi-B38510
> > <B38510 [at] freescale <mailto:B38510 [at] freescale>> wrote:
> >
> > __ __
> >
> > Hi All,____
> >
> > __ __
> >
> > Please find the problem that we are observing at out lab, please
> > respond if there are any suggestions____
> >
> > __ __
> >
> > Test Setup:____
> >
> > TR2(192.168.1.100)--------(192.168.1.1)TR1____
> >
> > __ __
> >
> > Here, TR1 and TR2 uses quagga routing suite.____
> >
> > __ __
> >
> > Test procedure:____
> >
> > 1. Quagga and TR1 are configured as external peers.____
> >
> > 2. TR1 does not support Capabilities Negotiation.____
> >
> > 3. BGP is started on the routers.____
> >
> > 4. Wait for the OPEN messages to be sent and check the packets.____
> >
> > __ __
> >
> > TR1 quagga Configuration:____
> >
> > __ __
> >
> > quagga-router(config-router)# do sh run____
> >
> > Building configuration...____
> >
> > __ __
> >
> > Current configuration:____
> >
> > !____
> >
> > hostname Router____
> >
> > hostname bgpd____
> >
> > log stdout____
> >
> > bgp config-type cisco____
> >
> > hostname quagga-router____
> >
> > !____
> >
> > password zebra____
> >
> > enable password zebra____
> >
> > !____
> >
> > interface eth0____
> >
> > ipv6 nd suppress-ra____
> >
> > !____
> >
> > interface eth1____
> >
> > ipv6 nd suppress-ra____
> >
> > !____
> >
> > interface eth2____
> >
> > ipv6 nd suppress-ra____
> >
> > !____
> >
> > interface lo____
> >
> > !____
> >
> > interface sit0____
> >
> > ipv6 nd suppress-ra____
> >
> > !____
> >
> > router bgp 6300____
> >
> > no synchronization____
> >
> > bgp router-id 3.3.3.3____
> >
> > network 1.1.1.0 mask 255.255.255.0____
> >
> > neighbor 192.168.1.100 remote-as 6200____
> >
> > neighbor 192.168.1.100 dont-capability-negotiate____
> >
> > no auto-summary____
> >
> > !____
> >
> > line vty____
> >
> > !____
> >
> > end____
> >
> > __ __
> >
> > __ __
> >
> > __ __
> >
> > TR2 Quagga Configuration:____
> >
> > __ __
> >
> > router bgp 6200____
> >
> > no synchronization____
> >
> > bgp router-id 2.2.2.2____
> >
> > neighbor 192.168.1.1 remote-as 6300____
> >
> > neighbor 192.168.1.1 strict-capability-match____
> >
> > no auto-summary____
> >
> > !____
> >
> > __ __
> >
> > __ __
> >
> > Please find the attached wireshark captured file between TR2 and
> TR1.____
> >
> > __ __
> >
> > __ __
> >
> > Issue:____
> >
> > TR2 sent an OPEN message containing the Capabilities Optional
> > Parameter. TR1____
> >
> > doesnot close the connection by sending the NOTIFICATION message with
> > Error____
> >
> > Subcode Unsupported Optional Parameter. ____
> >
> > __ __
> >
> > Observation:____
> >
> > TR1 and TR2 has established the BGP session but when BGP Update is
> sent
> > from____
> >
> > TR1 to TR2, TR2 sends the NOTIFICATION message with Error Subcode
> > Malformed____
> >
> > ASPATH and Malformed Attribute List.____
> >
> > Please find the attached captured wireshark for more details.____
> >
> > __ __
> >
> > Expected Result:____
> >
> > __ __
> >
> > TR2 should send an OPEN message containing the Capabilities Optional
> > Parameter.____
> >
> > TR1 should close the connection sending the NOTIFICATION message with
> > Error____
> >
> > Subcode Unsupported Optional Parameter. Upon receipt of the
> > NOTIFICATION____
> >
> > message, TR2 should attempt to reestablish the connection, without
> > sending the____
> >
> > Capabilities Optional Parameter.____
> >
> > __ __
> >
> > Regards,____
> >
> > -Vamsi____
> >
> > __ __
> >
> > __ __
> >
> > __ __
> >
> > __ __
> >
> > __ __
> >
> >
> > _______________________________________________
> > Quagga-users mailing list
> > Quagga-users [at] lists <mailto:Quagga-users [at] lists>
> > http://lists.quagga.net/mailman/listinfo/quagga-users
> >
> >
> >
> >
> > _______________________________________________
> > Quagga-users mailing list
> > Quagga-users [at] lists
> > http://lists.quagga.net/mailman/listinfo/quagga-users
>
>
> --
> Network Ability Ltd. | Chief Technical Officer | Tel: +353 1 6169698
> 3 Westland Square | INEX - Internet Neutral | Fax: +353 1 6041981
> Dublin 2, Ireland | Exchange Association | Email: nick [at] inex
> _______________________________________________
> Quagga-users mailing list
> Quagga-users [at] lists
> http://lists.quagga.net/mailman/listinfo/quagga-users
>
|
capabilityneighborupdatenotificationmessage1 (1).pcap
