MPLS support in sFlow

From: Peter Phaal (Peter_Phaal@inmon.com)
Date: 06/20/02

Next message: Marc Lavine: "sFlow Datagram Extensibility"

Previous message: Peter Phaal: "Using sFlow to analyze TCP connection statistics"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mail actions: [ respond to this message ] [ mail a new topic ]

Currently sFlow has somewhat limited support for MPLS. MPLS information may
be included in captured packet headers, but there is no explicit means for
an MPLS router to export MPLS information...

A natural way to add support for MPLS would be to add a new
extended_information type to the sFlow Datagram (
http://www.sflow.org/SFLOW-DATAGRAM.txt ). Here is an initial attempt at
specifying the structure:

struct extended_mpls {
      address mplsNextHop; /* Address of the next hop */
      unsigned int mplsInLabel; /* Top label of received mpls packet
                                             (See RFC 3032 for label encoding) */
      unsigned int mplsOutLabelStack<>; /* Label stack for transmitted mpls packet
                                             Note: First entry is top of stack. */
}

Is this sufficient? Are there other fields that should be included? Any
comments or suggestions are welcome.

Peter

----------------------
Peter Phaal
InMon Corp.

Peter_Phaal@inmon.com

Next message: Marc Lavine: "sFlow Datagram Extensibility"
Previous message: Peter Phaal: "Using sFlow to analyze TCP connection statistics"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2b29 : 06/20/02 EDT