[voq][orchagent][fabric]"Failed to get port object for portid" error during line card boot up

[vganesan-nokia]

Description

In VOQ chassis, in the linecard syslog, series of following error logs are seen for all asic instances. These errors are seen during the linecard boot up

ERR swss0#orchagent: :- doTask: Failed to get port object for port id 0x10000000000a9
ERR swss0#orchagent: :- doTask: Failed to get port object for port id 0x10000000000ac
ERR swss0#orchagent: :- doTask: Failed to get port object for port id 0x1000000000130
.
.
.
ERR swss1#orchagent: :- doTask: Failed to get port object for port id 0x101000000000118
ERR swss1#orchagent: :- doTask: Failed to get port object for port id 0x101000000000105
ERR swss1#orchagent: :- doTask: Failed to get port object for port id 0x101000000000115
.
.
.

Steps to reproduce the issue:

1. Have a VOQ chassis with a supervisor card and a linecard (single asic or multiple asic)
2. Reboot chassis with appropriate minimum configuration like switch_type = "voq"
3. Check the syslog. For all asics instances of the linecard the above error will be seen dring initialization time.

Describe the results you received:

As given in the description section above

Describe the results you expected:

The reported errors should not be seen.

Output of show version:

N/A

Output of show techsupport:

N/A

Additional information you deem important (e.g. issue happens only occasionally):

• The issue happens all the time.
• These errors occur when port state change notification (form down to up) come for fabric ports from syncd. Since orchagent in linecard only knows about the front panel ports and recycle port (as supplied in port_config.ini and confirmed by configuration), orchagent does not have corresponding port oids for the received fabric ports. Hence these errors are displayed. We need to either mask these error messages coming for the fabric ports or linecard orchagent should retrieve fabric port oids from SAI and match them with port oids given via port state notifications to avoid these error messages.

[rlhui]

@sanmalho-git will check if Nokia could help, thanks.

[skeesara-nokia]

The VID (Virtual OID) encoding the ports only includes the object type (port) and does not indicate what kind of port (Fabric port or a regular ethernet port for example) it is. Also the VID structure is private to syncd where it is allocated.

It is possible to do a VID to RID translation and the RID (Real OID) may have a the port-type encoded in it. But the structure of the RID on the SAI implementation and cannot be relied upon in common code.

At this point the options are -

1. Implement Fabric port configuration so that the SWSS can find the object when the notifcation is received from syncd for Fabric port state transistions OR
2. Make changes to syncd to encode the PORT_TYPE in the VID structure OR
3. Make changes to the sonic-mgmt tests to ignore these log messages on the LC when executing tests that cause fabric links ot bounce.

[abdosi]

@mlorrillere can you confirm if your PR: sonic-net/sonic-swss#1944 will fix this

[abdosi]

Sandeep from Nokia please add test pr link here that ignores this error.

[sanmalho-git]

Test PR to ignore these messages at in reload/reboot scenarios of supervisor is sonic-net/sonic-mgmt#6056