search

sonic-net / sonic-buildimage

Scripts which perform an installable binary image build for SONiC
Other
741 stars 1.43k forks source link

Learned EVPN routes are getting disappeared after we advertise IMET route #9694

Open kamalsahu0001 opened 2 years ago

kamalsahu0001 commented 2 years ago

Description

Steps to reproduce the issue:

  1. Configure BGP EVPN VxLAN with one L2VNI
  2. Advertise the IMET route from other end
  3. See that the learned routes disappear after advertising IMET routes

Output of show version:

SONiC Software Version: SONiC.202106.62436-dirty-20211231.160323 Distribution: Debian 10.11 Kernel: 4.19.0-12-2-amd64 Build commit: c4bc9933f Build date: Fri Dec 31 16:11:59 UTC 2021 Built by: AzDevOps@sonic-build-workers-0010ZQ

Platform: x86_64-accton_wedge100bf_32x-r0 HwSKU: montara ASIC: barefoot ASIC Count: 1 Serial Number: AJ19015463 Model Number: N0PCH7632002S Hardware Revision: N/A Uptime: 19:57:29 up 21:27, 1 user, load average: 0.34, 0.43, 0.49

Docker images: REPOSITORY TAG IMAGE ID SIZE docker-syncd-bfn 202106.62436-dirty-20211231.160323 935c2d0db7fd 1.22GB docker-syncd-bfn latest 935c2d0db7fd 1.22GB docker-dhcp-relay latest d39456adfbb9 428MB docker-sflow 202106.62436-dirty-20211231.160323 0e8db0f162e3 433MB docker-sflow latest 0e8db0f162e3 433MB docker-teamd 202106.62436-dirty-20211231.160323 24995eb51b94 433MB docker-teamd latest 24995eb51b94 433MB docker-nat 202106.62436-dirty-20211231.160323 5838f4042cb5 435MB docker-nat latest 5838f4042cb5 435MB docker-platform-monitor 202106.62436-dirty-20211231.160323 1e955988e030 636MB docker-platform-monitor latest 1e955988e030 636MB docker-lldp 202106.62436-dirty-20211231.160323 1fe4e309a4d5 461MB docker-lldp latest 1fe4e309a4d5 461MB docker-database 202106.62436-dirty-20211231.160323 9833e61e799f 421MB docker-database latest 9833e61e799f 421MB docker-router-advertiser 202106.62436-dirty-20211231.160323 9f4e8ee0103d 421MB docker-router-advertiser latest 9f4e8ee0103d 421MB docker-orchagent 202106.62436-dirty-20211231.160323 9a080b7c0949 451MB docker-orchagent latest 9a080b7c0949 451MB docker-snmp 202106.62436-dirty-20211231.160323 d7591a6f7870 463MB docker-snmp latest d7591a6f7870 463MB docker-sonic-telemetry 202106.62436-dirty-20211231.160323 b474a5b0a441 510MB docker-sonic-telemetry latest b474a5b0a441 510MB docker-sonic-mgmt-framework 202106.62436-dirty-20211231.160323 b0f6723cb712 577MB docker-sonic-mgmt-framework latest b0f6723cb712 577MB docker-fpm-frr 202106.62436-dirty-20211231.160323 137f24d148b2 451MB docker-fpm-frr latest 137f24d148b2 451MB docker-macsec 202106.62436-dirty-20211231.160323 56b7ee2d7313 436MB docker-macsec latest 56b7ee2d7313 436MB

Output of show techsupport:

Screen Shot 2022-01-06 at 11 45 52 AM

kamalsahu0001 commented 2 years ago

sonic_dump_sonic_20220106_194626.tar.gz

zhangyanzhao commented 2 years ago

Need BRCM to take a look.

adyeung commented 2 years ago

@hasan-brcm: pls help followup

prsunny commented 2 years ago

@adyeung , @hasan-brcm, @srj102, could you please update?

adyeung commented 2 years ago

The vxlan interface is not created in the kernel, Rajesh S will take a look

srj102 commented 2 years ago

Jan 6 17:58:41.523541 sonic WARNING swss#vxlanmgrd: :- doVxlanTunnelMapCreateTask: State VXLAN tunnel table not yet empty.

The above is preventing the kernel device from being created and also an APP_DB entry for the VLAN-VNI map entry.

The STATE_DB.json contains an entry for VXLAN tunnel. "VXLAN_TUNNEL_TABLE|EVPN_2.2.2.2": { "expireat": 1641498428.590671, "ttl": -0.001, "type": "hash", "value": { "dst_ip": "2.2.2.2", "operstatus": "down", "src_ip": "1.1.1.1", "tnl_src": "EVPN" } },

Jan 6 17:57:25.416801 sonic ERR syncd[23]: 2022-01-06 17:57:25.416453 ERROR (BF_SAI:(file=null):(func=null):0) - sai_create_tunnel:302: Failed to create tunnel: Unsupported value SAI_TUNNEL_PEER_MODE_P2P of attribute SAI_TUNNEL_ATTR_PEER_MODE Jan 6 17:57:25.416801 sonic ERR syncd[23]: :- sendApiResponse: api SAI_COMMON_API_CREATE failed in syncd mode: SAI_STATUS_NOT_SUPPORTED Jan 6 17:57:25.417038 sonic INFO /supervisord: syncd 2022-01-06 17:57:25.416453 BF_SAI ERROR - sai_create_tunnel:302: Failed to create tunnel: Unsupported value SAI_TUNNEL_PEER_MODE_P2P of attribute SAI_TUNNEL_ATTR_PEER_MODE

Jan 6 17:57:25.417766 sonic ERR swss#orchagent: :- handleSaiCreateStatus: Encountered failure in create operation, exiting orchagent, SAI API: SAI_API_BRIDGE, status: SAI_STATUS_INVALID_PARAMETER

After the above step OA restarts, however the STATE_DB does not seem to be getting flushed.

srj102 commented 2 years ago

The sai_create_tunnel error needs to be solved by support for P2P tunnels (SAI_TUNNEL_PEER_MODE_P2P ).

The STATE_DB cleanup to be fixed by adding VXLAN_TUNNEL_TABLE to the files/scripts/swss.sh