RE: [ippm] Way to store traceroutes
Andy Bierman <[email protected]> Fri, 14 Jan 2005 11:25:16 -0800
| Newsgroups | gmane.ietf.disman |
|---|---|
| Message-ID | <[email protected]> |
At 07:59 AM 1/14/2005, Saverio Niccolini wrote: >Dear all, >thanks a lot for your useful suggestions. This work is already established in the DISMAN WG. See RFC 2925, or its update (in progress): http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-06.txt I strongly urge you to work with the DISMAN WG to resolve perceived deficiencies with the RemOps MIB, rather than create a spin-off MIB. Andy >We have tried to draft a "traceroute object" based on what we discussed >on the list and what we had in mind. We think this will serve as a >starting point of our information model. > >We have taken the disman draft as a starting point and we have erased >some fields not useful in the scope of our draft (that we do not specify >here), moreover we have added and changed other ones: > >NEW fields: >1) traceRouteResultsLastGoodPathDuration (duration of single running of >the last good traceroute path determination) >2) traceRouteResultsLastRun (when the last traceroute with these >characteristics was launched) >3) traceRouteHopsASNumber (AS number of the hop) > >CHANGED fields: >1) traceRouteProbeHistoryTime (timestamp of when the traceroute probe >came back) was changed to traceRouteProbeHistorySentTime (timestamp of >when the traceroute probe was sent) > > >Please find here how the "traceroute object" looks like right now: > >--traceRouteObjects > | > +--traceRouteCtlTable > | | > | +--traceRouteCtlEntry > | | > | +--traceRouteCtlOwnerIndex > | +--traceRouteCtlTestName > | +--traceRouteCtlTargetAddressType > | +--traceRouteCtlTargetAddress > | +--traceRouteCtlByPassRouteTable > | +--traceRouteCtlDataSize > | +--traceRouteCtlTimeOut > | +--traceRouteCtlProbesPerHop > | +--traceRouteCtlPort > | +--traceRouteCtlMaxTtl > | +--traceRouteCtlDSField > | +--traceRouteCtlSourceAddressType > | +--traceRouteCtlSourceAddress > | +--traceRouteCtlIfIndex > | +--traceRouteCtlMiscOptions > | +--traceRouteCtlMaxFailures > | +--traceRouteCtlDontFragment > | +--traceRouteCtlInitialTtl > | +--traceRouteCtlDescr > | +--traceRouteCtlMaxRows > | +--traceRouteCtlCreateHopsEntries > | +--traceRouteCtlType > | > +--traceRouteResultsTable > | | > | +--traceRouteResultsEntry > | | > | +--traceRouteResultsOperStatus > | +--traceRouteResultsIpTgtAddrType > | +--traceRouteResultsIpTgtAddr > | +--traceRouteResultsTestAttempts > | +--traceRouteResultsTestSuccesses > | +--traceRouteResultsLastGoodPath > | +--traceRouteResultsLastGoodPathDuration > | +--traceRouteResultsLastRun > | > +--traceRouteProbeHistoryTable > | | > | +--traceRouteProbeHistoryEntry > | | > | +--traceRouteProbeHistoryIndex > | +--traceRouteProbeHistoryHopIndex > | +--traceRouteProbeHistoryProbeIndex > | +--traceRouteProbeHistoryHAddrType > | +--traceRouteProbeHistoryHAddr > | +--traceRouteProbeHistoryResponse > | +--traceRouteProbeHistoryStatus > | +--traceRouteProbeHistorySentTime > | > +--traceRouteHopsTable > | > +--traceRouteHopsEntry > | > +--traceRouteHopsHopIndex > +--traceRouteHopsIpTgtAddressType > +--traceRouteHopsIpTgtAddress > +--traceRouteHopsASNumber > +--traceRouteHopsMinRtt > +--traceRouteHopsMaxRtt > +--traceRouteHopsAverageRtt > +--traceRouteHopsRttSumOfSquares > +--traceRouteHopsSentProbes > +--traceRouteHopsProbeResponses > >We believe that most of the fields are self-explaining, for the unclear >ones please refer to the disman draft: >http://www.ietf.org/internet-drafts/draft-ietf-disman-remops-mib-v2-06.t >xt > >Looking forward to receive your comments. > >Best regards, >Saverio Niccolini > >============================================================ >Dr. Saverio Niccolini >Research Staff Member >Network Laboratories, NEC Europe Ltd. >Kurfuerstenanlage 36, D-69115 Heidelberg >Tel. +49 (0)6221 90511-18 >Fax: +49 (0)6221 90511-55 >e-mail: [email protected] >============================================================ > > >_______________________________________________ >ippm mailing list >[email protected] >https://www1.ietf.org/mailman/listinfo/ippm