You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In topology t0 of the testbed, once DUT is connected to VM0100 (or other VMs), the static route entries in the VM will be sent to DUT.
It seems the routing table of DUT is not big enough for the 6K entries of both ipv4 and ipv6, and syncd receives the table full event, thus exit_and_notify.
Is the handling action meant to be for SAI_STATUS_TABLE_FULL?
Should I try to increase the routing table size, or there are other ways to proceed the tests?
Describe the results you received:
In /var/log/syslog:
sonic ERR syncd: _brcm_sai_l3_route_config:1095 L3 route add failed with error Table full (0xfffffffa).
sonic ERR syncd: brcm_sai_create_route_entry:340 L3 route add failed with error -13.
sonic ERR syncd: :- processEvent: attr: SAI_ROUTE_ENTRY_ATTR_NEXT_HOP_ID: oid:0x50000000006a0
sonic ERR syncd: :- processEvent: failed to execute api: create, key: SAI_OBJECT_TYPE_ROUTE_ENTRY:{"dest":"20c0:aef0::/64","switch_id":"oid:0x21000000000000","vr":"oid:0x3000000000024"}, status: SAI_STATUS_TABLE_FULL
sonic ERR syncd: :- syncd_main: Runtime error: :- processEvent: failed to execute api: create, key: SAI_OBJECT_TYPE_ROUTE_ENTRY:{"dest":"20c0:aef0::/64","switch_id":"oid:0x21000000000000","vr":"oid:0x3000000000024"}, status: SAI_STATUS_TABLE_FULL
sonic NOTICE syncd: :- exit_and_notify: sending switch_shutdown_request notification to OA
sonic NOTICE syncd: :- exit_and_notify: notification send successfull
The text was updated successfully, but these errors were encountered:
Description
In topology t0 of the testbed, once DUT is connected to VM0100 (or other VMs), the static route entries in the VM will be sent to DUT.
It seems the routing table of DUT is not big enough for the 6K entries of both ipv4 and ipv6, and syncd receives the table full event, thus exit_and_notify.
Is the handling action meant to be for SAI_STATUS_TABLE_FULL?
Should I try to increase the routing table size, or there are other ways to proceed the tests?
Describe the results you received:
In /var/log/syslog:
sonic ERR syncd: _brcm_sai_l3_route_config:1095 L3 route add failed with error Table full (0xfffffffa).
sonic ERR syncd: brcm_sai_create_route_entry:340 L3 route add failed with error -13.
sonic ERR syncd: :- processEvent: attr: SAI_ROUTE_ENTRY_ATTR_NEXT_HOP_ID: oid:0x50000000006a0
sonic ERR syncd: :- processEvent: failed to execute api: create, key: SAI_OBJECT_TYPE_ROUTE_ENTRY:{"dest":"20c0:aef0::/64","switch_id":"oid:0x21000000000000","vr":"oid:0x3000000000024"}, status: SAI_STATUS_TABLE_FULL
sonic ERR syncd: :- syncd_main: Runtime error: :- processEvent: failed to execute api: create, key: SAI_OBJECT_TYPE_ROUTE_ENTRY:{"dest":"20c0:aef0::/64","switch_id":"oid:0x21000000000000","vr":"oid:0x3000000000024"}, status: SAI_STATUS_TABLE_FULL
sonic NOTICE syncd: :- exit_and_notify: sending switch_shutdown_request notification to OA
sonic NOTICE syncd: :- exit_and_notify: notification send successfull
The text was updated successfully, but these errors were encountered: