[ixpmanager] peer-to-peer statistics | sFlow

Vladislav Leontjev vladislav.leontjev at gmail.com
Sun Mar 24 07:13:20 GMT 2019


Good day,

Thank a lot for such a wide answer, will get back after Huawei support
resolves this issue.

Vlad.

On Sat, 23 Mar 2019, 00:40 Nick Hilliard, <nick at foobar.org> wrote:

> Vladislav Leontjev wrote on 22/03/2019 16:11:
> >
> FLOW,10.81.7.25,25,0,0027e360dd85,141877e02d33,0x0800,10,0,194.176.58.39,213.197.181.78,6,0x08,62,22,55515,0x18,150,114,8192
> >
> FLOW,10.81.7.25,25,0,0027e360dd85,141877e02d33,0x0800,10,0,194.176.58.39,213.197.181.78,6,0x08,62,22,55515,0x18,150,114,8192
> >
> > But ther's the same 0 vlan if I understand write according your script
> > and output?
>
> This looks badly broken, and the problem is the sflow output from the
> switch.
>
> Fields #3 and #4 (25, 0) are the SNMP indexes of the source and
> destination interfaces of the switch.  The destination interface ID is
> set to 0, which is impossible because SNMP IDs are indexed from 1 upwards.
>
> Fields #8 and #9 are the source and destination VLAN id.  Neither should
> be zero because dot1q vlan ID 0 does not exist.
>
> I think you need to talk to Huawei about this.  Each sflow record should
> contain a legitimate ifIndex ID for both the source and destination
> interface, and should also contain valid VLAN IDs, which are provided by
> the Sflow Extended Switch Data field in the sflow header.  This switch
> provides incorrect data for both these fields, which is a bug.
>
> Nick
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.inex.ie/pipermail/ixpmanager/attachments/20190324/5a4aa435/attachment.html>


More information about the ixpmanager mailing list