Open aseaudi opened 2 years ago
Adam will follow up with BRCM
meta_sai_on_port_state_change_single needs to also handle SAI_OBJECT_TYPE_TUNNEL
switch (ot)
{
// TODO hardcoded types, must advance SAI repository commit to get metadata for this
case SAI_OBJECT_TYPE_PORT:
case SAI_OBJECT_TYPE_BRIDGE_PORT:
case SAI_OBJECT_TYPE_LAG:
case SAI_OBJECT_TYPE_TUNNEL:
valid = true;
break;
Hi, I have the same error (chipset : Trident 2) This is the log:
Mar 16 17:26:57.335089 sonic ERR syncd#syncd: [none] SAI_API_TUNNEL:_brcm_sai_vxlan_create_vpn:875 create tunnel initiator setup for net port failed with error Invalid parameter (0xfffffffc). Mar 16 17:26:57.335089 sonic ERR syncd#syncd: [none] SAI_API_TUNNEL:_brcm_sai_vxlan_enable:1167 create a vxlan decap tunnel failed with error -5. Mar 16 17:26:57.335089 sonic ERR syncd#syncd: [none] SAI_API_TUNNEL:brc
m_sai_create_tunnel_map_entry:2667 Can't create brcm vxlan tunnel Mar 16 17:26:57.335125 sonic ERR syncd#syncd: :- sendApiResponse: api SAI_COMMON_API_CREATE failed in syncd mode: SAI_STATUS_FAILURE Mar 16 17:26:57.335690 sonic ERR syncd#syncd: :- processQuadEvent: attr: SAI_TUNNEL_MAP_ENTRY_ATTR_TUNNEL_MAP_TYPE: SAI_TUNNEL_MAP_TYPE_VNI_TO_VLAN_ID Mar 16 17:26:57.335690 sonic ERR syncd#syncd: :- processQuadEvent: attr: SAI_TUNNEL_MAP_ENTRY_ATTR_TUNNEL_MAP: oid:0x29000000000beb Mar 16 17:26:57.335690 sonic ERR syncd#syncd: :- processQuadEvent: attr: SAI_TUNNEL_MAP_ENTRY_ATTR_VLAN_ID_VALUE: 30 Mar 16 17:26:57.335727 sonic ERR syncd#syncd: :- processQuadEvent: attr: SAI_TUNNEL_MAP_ENTRY_ATTR_VNI_ID_KEY: 3000 Mar 16 17:26:57.337023 sonic ERR swss#orchagent: :- create: create status: SAI_STATUS_FAILURE Mar 16 17:26:57.339149 sonic WARNING swss#orchagent: :- addOperation: Error adding tunnel map entry. Tunnel: vtep2. Entry: map_3000_Vlan30. Error: Can't create a tunnel map entry object
EVPN VXLAN is supported only on Trident 3.
@srj102, Thanks for your response. So what I must do with Trident 2 based switch? As I know Trident 2 supports VXLAN (VLAN to VNI at least), but it is not supported in SAI as you said.
@srj102
meta_sai_on_port_state_change_single needs to also handle SAI_OBJECT_TYPE_TUNNEL
switch (ot) { // TODO hardcoded types, must advance SAI repository commit to get metadata for this case SAI_OBJECT_TYPE_PORT: case SAI_OBJECT_TYPE_BRIDGE_PORT: case SAI_OBJECT_TYPE_LAG: case SAI_OBJECT_TYPE_TUNNEL: valid = true; break;
Ok, so as per https://github.com/sonic-net/sonic-sairedis/pull/1467 this is not the proper solution to the error message Aug 16 03:14:19.373668 Odin-ec58a ERR swss#orchagent: :- meta_sai_on_port_state_change_single: data.port_id oid:0x2a0000000009bf has unexpected type: SAI_OBJECT_TYPE_TUNNEL, expected PORT, BRIDGE_PORT or LAG
. The replacement PR that was created also does not resolve the issue, they just made the metadata type check dynamic rather than depending on a static list. I should clarify this ERR
is meaningless other than the fact that it causes confusion when VXLAN isn't working.
I'm adding some debug into sonic-swss/orchagent/portsarch to see how its presented there and see if we can keep it from propagating into the SAI Metadata as according to https://github.com/opencomputeproject/SAI/blob/master/inc/saiport.h#L137 the tunnel type should never be passed to that in the first place. That said, the person who rejected the PR said it could be a vendor issue, meaning broadcom in my case sending an event when it shouldn't. Not sure. I'll update after I debug a bit.
Description
I created a Vxlan EVPN tunnel between 2 sonic switches using the Loopback interfaces as SRC and DST, but it didn't work.
Steps to reproduce the issue:
Configure OSPF and BGP EVPN between 2 sonic switches, and ensure Loopback0 is in the routing tables. Create Vlan 50 and add it as tagged egress pvid on a port on each switch. Connect 2 hosts on each switch.
Describe the results you received:
I get the following error in the syslog,
Describe the results you expected:
Expected that the VXLAN oper_status is up, and connectivity over the vxlan to work, but it does not work
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):