Since it is in the Slowpath stage, it has the session ID generated in the ingress-backlogs command but this is NOT searchable with CLI command ‘show session id id’ and will always give the error message below: Bad Key: c2s: 'c2s' Bad Key: s2c: 's2c' index(local): : index number This is of course because the session is not fully established and has not generated a session ID. When investigating the ingress-backlogs command for spikes in traffic that cause latency or outages, finding the offender can be crucial in knowing the resolution path to take Seeing a large amount of sessions that are in Group-ID 2 Slowpath stage lets you know that it is not currently being allowed, but may be generating large amounts of information which are impacting your buffers Hope that answers your question. Cheers! Suresh
... View more