topic Re: 93180YC-FX 9.3(13) sflow not showing egress information in Switching

93180YC-FX 9.3(13) sflow not showing egress information

sp2720401 — Sat, 01 Mar 2025 18:11:30 GMT

When running sflow on the above mentioned switch and nxos version. I am not seeing an output index.

I wrote a python script to receive the raw xdr using xdrlib, struct, and socket. I can see the 2 UINT 32 bit fields for "input interface value" and "output interface value". The output interface value is set to zero but should have a 32 bit integer other than 0.

These values are set on other devices, nexus 9272, 9372, 9396, Fortigate 1100E...

Re: 93180YC-FX 9.3(13) sflow not showing egress information

marce1000 — Sat, 01 Mar 2025 18:43:39 GMT

- FYI : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCve57917

Re: 93180YC-FX 9.3(13) sflow not showing egress information

sp2720401 — Sat, 01 Mar 2025 19:59:06 GMT

does this relate to the 93180. max-mode l3 cannot be changed but it shows up in show run all as

"no system routing max-mode l3"

Am I supposed to change the system routing template from the default LPM to something else so I can see sflow egress interface information?

Re: 93180YC-FX 9.3(13) sflow not showing egress information

vishalbhandari — Sun, 02 Mar 2025 04:21:08 GMT

@sp2720401 It looks like the Nexus switch running the specified NX-OS version isn't populating the output interface index in the sFlow data, while other devices (including Nexus 9272, 9372, 9396, and Fortigate 1100E) are providing a valid value. This could be due to an NX-OS software limitation, a bug, or specific hardware behavior. You might want to check if the NX-OS version has any known sFlow-related bugs or if there's a configuration tweak required to enable the output interface reporting. Running show sflow or checking the sFlow agent settings could help. If the issue persists, capturing and comparing sFlow records from working and non-working devices might give more insights.