Hi all, I wanted raise awareness about the following activity on the sFlow.org mailing list that relates to the optics work being done in OCP (http://groups.google.com/group/sflow). Comments are welcome, please respond on the sFlow list.
Thanks, Peter > The following proposal defines an extended counter structure to augment > interface counters with management information from SFP/QSFP optical modules: > > http://sflow.org/draft_sflow_optics.txt > <http://sflow.org/draft_sflow_optics.txt> > > Extending sFlow to report optical module measurements supports a number of > important use cases, including: > Power loss across link > Dirty connectors > Proactive replacement of failing components > Discover relationship between switch ports and optical underlay > Correlate optical errors with affected traffic > Debug network lane failure, locate source as Tx, Rx, or cable plant > The Host sFlow agent implements the draft spec and has been tested on 10G > production switches. Source code using the Linux ethtool API is available on > github: > > https://github.com/sflow/host-sflow/blob/master/src/Linux/readNioCounters.c#L291-L613 > > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fsflow%2Fhost-sflow%2Fblob%2Fmaster%2Fsrc%2FLinux%2FreadNioCounters.c%23L291-L613&sa=D&sntz=1&usg=AFQjCNEp5-nd3BlMvj8VKfc_DDwr6MjJbA> > > Please review and comment.
_______________________________________________ opencompute-networking mailing list Unsubscribe: http://lists.opencompute.org/mailman/options/opencompute-networking opencompute-networking@lists.opencompute.org http://lists.opencompute.org/mailman/listinfo/opencompute-networking
