cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
531
Views
2
Helpful
6
Replies
Highlighted

Gettinge XML RPC reply is taking 10 minutes for l2vpn evpn

Hi ,

We send below XML RPC to NCS5501 cisco router to get XML RPC reply output. Its taking 10 minutes to get output for received routes .

<bgp xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ipv4-bgp-oper">

        <instances>

          <instance>

            <instance-name>default</instance-name>

            <instance-active>

              <default-vrf>

                <afs>

                  <af>

                    <af-name>l2vpnevpn</af-name>

                    <path-table>

                      <path>

                        <rd/>

                        <network/>

                        <prefix-length/>

                        <neighbor-address></neighbor-address>

                        <attributes-after-policy-in>

                         <common-attributes>

                           <local-preference/>

                         </common-attributes>

                        </attributes-after-policy-in>

                        <path-information>

                          <neighbor-address>

                            <ipv4-address></ipv4-address>

                          </neighbor-address>

                          <is-path-received-only>false</is-path-received-only>

                          <next-hop/>

                          <path-weight/>

                        </path-information>

                      </path>

                    </path-table>

                  </af>

                </afs>

              </default-vrf>

            </instance-active>

          </instance>

        </instances>

      </bgp>

Corresponding CLI is below

RP/0/RP0/CPU0:dedsdf1002js1#sh bgp l2vpn evpn neighbors 10.80.11.19 received routes

Fri Jun  2 00:50:43.208 EDT

BGP router identifier 10.80.11.17, local AS number 62300

BGP generic scan interval 60 secs

Non-stop routing is enabled

BGP table state: Active

Table ID: 0x0   RD version: 0

BGP main routing table version 54806

BGP NSR Initial initsync version 8466 (Reached)

BGP NSR/ISSU Sync-Group versions 0/0

BGP scan interval 60 secs


Status codes: s suppressed, d damped, h history, * valid, > best

              i - internal, r RIB-failure, S stale, N Nexthop-discard

Origin codes: i - IGP, e - EGP, ? - incomplete

   Network            Next Hop            Metric LocPrf Weight Path

Route Distinguisher: 19:21023

*>i[1][0000.60d3.1000.0100.1248][0]/120

                      10.80.13.19                   100      0 i

*>i[2][0][48][0000.54f4.891b][32][10.64.203.3]/136

                      10.80.13.19                   100      0 i

*>i[2][0][48][0000.54fe.365a][32][10.64.203.4]/136

                      10.80.13.19                   100      0 i

*>i[2][0][48][0000.54fe.365c][32][10.64.203.5]/136

                      10.80.13.19                   100      0 i

*>i[2][0][48][0000.54fe.365e][32][10.64.203.6]/136

                      10.80.13.19                   100      0 i

Kindly let us know the resolution of this issue

Thanks

Jay

6 REPLIES 6
Highlighted
Cisco Employee

CLI output shows five prefixes. How many are retrieved programmatically?  What's the line count of the entire XML output?

Highlighted

CLI output shows onl 21 prefixes , but we are getting XML rpc reply for other unwanted info .

Needs only received routes prefixes and RD value, Please check our rpc is correct or not

Thanks

Jay

Highlighted

Hi Santiago,

Kindly let us know the XML rpc is correct or not , because we are getting rpc reply taking time 8 to 10 mins.

<bgp xmlns="http://cisco.com/ns/yang/Cisco-IOS-XR-ipv4-bgp-oper">

        <instances>

          <instance>

            <instance-name>default</instance-name>

            <instance-active>

              <default-vrf>

                <afs>

                  <af>

                    <af-name>l2vpnevpn</af-name>

                    <path-table>

                      <path>

                        <rd/>

                        <network/>

                        <prefix-length/>

                        <neighbor-address></neighbor-address>

                        <attributes-after-policy-in>

                         <common-attributes>

                           <local-preference/>

                         </common-attributes>

                        </attributes-after-policy-in>

                        <path-information>

                          <neighbor-address>

                            <ipv4-address></ipv4-address>

                          </neighbor-address>

                          <is-path-received-only>false</is-path-received-only>

                          <next-hop/>

                          <path-weight/>

                        </path-information>

                      </path>

                    </path-table>

                  </af>

                </afs>

              </default-vrf>

            </instance-active>

          </instance>

        </instances>

      </bgp>

We are not facing any issue for show bgp l2vpn evpn advertised routes  , only issue with received routes.

Thanks

Jay

Thanks

Jay

Highlighted

Jay,

I’ve passed on a query to the engineering team.

Cheers,

Einar

Highlighted

Thank you Einar !

Highlighted

We'll probably need some logging and sample output.  We'll reach out to you directly. Thanks.

This widget could not be displayed.