Ipv4SlaveForwBmanChk error

[bjelf]

Does anyone know what these errors mean?

DEC 16 14:43:53 css-1 3/1 1 IPV4-2: Ipv4SlaveForwBmanChk: no ingress LP in buffer

DEC 16 14:43:58 css-1 3/1 2 IPV4-2: Ipv4SlaveForwBmanChk: no ingress LP in buffer

DEC 16 14:44:03 css-1 3/1 3 IPV4-2: Ipv4SlaveForwBmanChk: no ingress LP in buffer

DEC 16 14:45:18 css-1 2/1 8 IPV4-2: Ipv4SlaveForwBmanChk: no ingress LP in buffer

DEC 16 14:45:24 css-1 1/1 3629 IPV4-2: Ipv4SlaveForwBmanChk: no ingress LP in buffer

This happened during a period of low traffic.

Thanks

[Gilles Dufour]

This indicates a packet that could not be fastswitched and was forwarded to main cpu for process switching but the CSS could not handle it because it had no information about ingress port.

We have seen this issue recently and are still investigating.

If you could capture a sniffer trace when this error occurs that would be great.

Thanks.

Gilles.