Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Quagga: Users

Re: Quagga-users Digest, Vol 104, Issue 6

 

 

Quagga users RSS feed   Index | Next | Previous | View Threaded


ganeshreddyk at gmail

Apr 12, 2012, 3:15 AM

Post #1 of 1 (354 views)
Permalink
Re: Quagga-users Digest, Vol 104, Issue 6

On Wed, Mar 14, 2012 at 5:26 PM, <quagga-users-request [at] lists> wrote:
> Send Quagga-users mailing list submissions to
>        quagga-users [at] lists
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://lists.quagga.net/mailman/listinfo/quagga-users
> or, via email, send a message with subject or body 'help' to
>        quagga-users-request [at] lists
>
> You can reach the person managing the list at
>        quagga-users-owner [at] lists
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Quagga-users digest..."
>
>
> Today's Topics:
>
>   1. [quagga-users 12783] Re: Regarding redistribute kernel and
>      redistribute static configuration in quagga-bgpd (Renato Westphal)
>   2. [quagga-users 12784] R [osfp6d] ospfv3 Summary Ranges
>      functionality     is not working (Krishna P Vamsi-B38510)
>   3. [quagga-users 12785] Re: Capabilities Not Negotiated] BGPD
>      not sending NOTIFICATION message with Error Subcode Unsupported
>      Optional Parameter (Krishna P Vamsi-B38510)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 14 Mar 2012 08:32:59 -0300
> From: Renato Westphal <renatowestphal [at] gmail>
> To: Quagga Users Lists <quagga-users [at] lists>
> Subject: [quagga-users 12783] Re: Regarding redistribute kernel and
>        redistribute static configuration in quagga-bgpd
> Message-ID:
>        <CAChaeg=bbJSR5JQciJ3UyXh5EWv_SnXzz9=G_Yc9rE6+Q_LfOA [at] mail>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 2012/3/14 Ganesh Reddy K <ganeshreddyk [at] gmail>:
>> Hi,
>>
>> We are seeing a typical behavior with quagga bgp redistribute configuration.
>> ?quagga 0.99.20 is installed ?on a powerpc .
>>
>> When bgpd is configured to redistribute v4 and V6 routes, it is not working
>> properly. Only one of the "v4" or "v6" alone ?working fine. we did not
>> observe any issue.
>>
>>
>> If we do configure v4 first and v6 second, V4 routes are properly
>> redistributed. V6 routes are not properly distributed. Inconsistency
>> observed.
>> If we do configure v6 first and v4 second, V6 routes are properly
>> redistributed. V4 routes are not properly distributed. Inconsistency
>> observed.
>> Even though if we delete the firstly configured redistribute configuration,
>> still the issue is observable
>>
>> Is anybody observed this behaviour ? Any solution/fix for this ??
>>
>> Thanks in advance,
>> Ganesh
>>
>> below are the commands used for v4 and v6 redistribute routes in bgp
>>
>> V4 redistribute configuration commands:-
>>
>> "redistribute static"
>>
>> V6 redistribute configuration commands:-
>>
>> "address-family ipv6"
>> ? "redistribute static"
>> "exit-address-family"
>>
>> _______________________________________________
>> Quagga-users mailing list
>> Quagga-users [at] lists
>> http://lists.quagga.net/mailman/listinfo/quagga-users
>>
>
> Hi,
>
> You may want to try these patches:
> http://lists.quagga.net/pipermail/quagga-dev/2011-September/008869.html
>
> These patches won't apply cleanly on the current HEAD of git, but I
> think they will on 0.99.20.
>
> --
> Renato Westphal
>
>
Hi Westphal,

Thanks for the help.

We have tested bgpd with the mentioned patch. Now v4 and v6 routing
table updates (addition/deletion of a route) via bgp are properly
advertized. This is perfectly working.
But, the full routing table update is not happening from BGP
redistribute (the secondly configured redistribute command i.e IPV4
(if and only if "address-family ipv6" and "redistribute static" is
configured first). The same behaviour if the order of commands is
reversed (i.e IPv4 first and IPV6 second)
Did you notice this behavior any time ?

If you have any workaround, please help us.

Thanks a lot.
- Ganesh



> ------------------------------
>
> Message: 2
> Date: Wed, 14 Mar 2012 11:55:04 +0000
> From: Krishna P Vamsi-B38510 <B38510 [at] freescale>
> To: "quagga-users [at] lists" <quagga-users [at] lists>
> Subject: [quagga-users 12784] R [osfp6d] ospfv3 Summary Ranges
>        functionality   is not working
> Message-ID:
>        <A996AD2165CEC2429013E92C0B329251D60161 [at] 039-SN2MPN1-012>
>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi All,
>
> Please find the problem that we are observing at out lab, please respond if there are any suggestions
>
> Test Setup:
>
> Cisco1(fa0/0)--[area 1]----(eth0)Quagga(eth1)---[area 0]----(fa0/1)Cisco2
>            3ffe:501:ffff:300::/64          2000:1000:0:100::/64
>
> Cisco1 contains loopback addresses as below:
> 3ffe:501:ffff:100::1/64
> 3ffe:501:ffff:200::1/64
>
> Below ipv6 network is used between Cisco1(fa0/0) and Quagga(eth0)
> 3ffe:501:ffff:300::/64
>
> Below ipv6 network is used between Quagga(eth1) and Cisco2
> 2000:1000:0:100::/64
>
> Test Procedure:
>
> 1)Configure OSPFv3 as per setup
> Enable ospfv3 on fa0/0 of Cisco1, quagga(eth0,eth1) and on Cisco2(fa0/0)
> Cisco1(fa0/0) and quagga (eth0) are in area 0.0.0.1.
> Cisco2(fa0/1) and quagga (eth1) are in area 0.0.0.0.
>
> 2) Wait for the OSPFv3 adjacencies to come up and for their databases to
> synchronize.
>
> 3)Check IPv6 routes in Cisco2
> Below networks should display in Cisco2
> 3ffe:501:ffff:100::
> 3ffe:501:ffff:200::
> 3ffe:501:ffff:300::
>
> 4)Configure Summary Ranges in Quagga
> Area ID    Action         IP Address       Subnet Mask
> 0.0.0.0    Advertise   3ffe:501:ffff::    48
>
> 5)Check IPv6 route in Cisco2
> Only one network should display in Cisco2
> 3ffe:501:ffff::
>
> ISSUE:-
> 1)At Step 4 QUAGGA(osfp6d) is not sending Summary Ranges info to Cisco2
> 2)At Step 5 showing 3 ipv6 networks as shown in Step 3.
>
> Regards,
> -vamsi
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.quagga.net/pipermail/quagga-users/attachments/20120314/97d13c21/attachment-0001.html>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 14 Mar 2012 11:56:09 +0000
> From: Krishna P Vamsi-B38510 <B38510 [at] freescale>
> To: "quagga-users [at] lists" <quagga-users [at] lists>
> Subject: [quagga-users 12785] Re: Capabilities Not Negotiated] BGPD
>        not sending NOTIFICATION message with Error Subcode Unsupported
>        Optional Parameter
> Message-ID:
>        <A996AD2165CEC2429013E92C0B329251D6016F [at] 039-SN2MPN1-012>
>
> Content-Type: text/plain; charset="us-ascii"
>
>
> 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
>
>
>
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.quagga.net/pipermail/quagga-users/attachments/20120314/d6187e26/attachment.html>
>
> ------------------------------
>
> _______________________________________________
> Quagga-users mailing list
> Quagga-users [at] lists
> http://lists.quagga.net/mailman/listinfo/quagga-users
>
>
> End of Quagga-users Digest, Vol 104, Issue 6
> ********************************************

_______________________________________________
Quagga-users mailing list
Quagga-users [at] lists
http://lists.quagga.net/mailman/listinfo/quagga-users

Quagga users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.