1 / 11

RMONMIB WG 55th IETF Atlanta, Georgia November 18, 2002

Summary of discussions and implementation reports at the RMONMIB WG meeting during IETF 55th in Atlanta, GA, November 18, 2002. Includes agenda items on RFC advancements and real-time application monitoring.

johnldavis
Download Presentation

RMONMIB WG 55th IETF Atlanta, Georgia November 18, 2002

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RMONMIB WG55th IETFAtlanta, GeorgiaNovember 18, 2002 Discussion: rmonmib@ietf.orgAdmin: http://www.ietf.org/mailman/listinfo/rmonmib

  2. RMONMIB WG Agenda -- I-Ds • (A) draft-ietf-rmonmib-framework-02.txt • (B) draft-siddiqui-rmonmib-raqmon-framework-00.txt • (C) draft-siddiqui-rmonmib-raqmon-pdu-00.txt • (D) draft-siddiqui-rmonmib-raqmon-mib-00.txt • (E) draft-bakke-dhc-snmp-trap-01.txt

  3. RMONMIB WG Agenda -- IETF 55 (1/2) 1) Implementation Reports (20 min) • Discussion of the implementation reports for: • SMON MIB (RFC 2613) Advancement • RMON2-MIB (RFC 2021) Advancement • RMON-PI (RFC 2074) Advancement • Goals: • Determine if RFC 2021 should be advanced by deprecating unimplemented objects or not advanced at this time. 2) RMON Framework Document (30 min) • Discussion of the RMON Framework document (A) • Determine if the framework is complete and ready for WG Last Call

  4. RMONMIB WG Agenda -- IETF 55 (2/2) 3) Real-time Application Quality of Service Monitoring (70 min) • Discussion of the RAQMON Framework (B) • Determine if the framework is complete • Should the framework provide extensibility and allow for future PDU types and/or delivery mechanisms • Discussion of the RAQMON PDU (C) • Determine if the PDU contains all appropriate fields • Should there be different high-level conformance levels to allow devices to subset the PDU fields in a consistent manner? • Should devices which use the SNMP Notification transport be required to support any command responder features? • Can the 'DHCP Option for SNMP' (E) mechanism be used to fully configure RAQMON devices which use the SNMP based PDU? • Discussion of the RAQMON MIB (D) • Determine (if possible) if the MIB is complete for: • configuration • reported attributes collected from RAQMON PDU

  5. RFC 2613 Implementation Report • Only 4 reports received; 2 from the same vendor • Includes 2 manager and 4 agent reports • Agents: 2 probe and 2 embedded switch implementations • At least 2 other implementations; did not respond in time • There are at least 2 independent implementations of every object in the MIB • Not every SmonDataSource value represented • All 4 did IfIndex.<I>; 1 did Vlan.<V> and 1 did EntPhysicalIndex.<N> • Not every Port Copy mode supported • 2 did 1:1; 1 did N:1; 1 did N:M • Recommend that RFC 2613 be advanced to Draft Standard

  6. RFC 2074 Implementation Report • Only 2 RMON-PI reports received • Includes 2 agent reports • Both agents are probe implementations • At least 2 other implementations; did not respond in time • There are at least 2 independent implementations of every feature of the Protocol Identifier macro • ProtocolDirTable mibwalks indicates consistent protocol representations • Only 1 RMON-PI report indicates support for ‘countsFragments’ and ‘trackSessions’ parameters, but RMON-2 reports indicate more support • Recommend RFC 2074 be advanced to Draft Standard

  7. RFC 2021 Implementation Report (1/5) • Only 3 RMON-2 reports received • Includes 3 agent reports • 2 agents are probe implementations, 1 is SW-only • At least 2 other implementations; did not respond in time • All 3 agents implement every statistics table • Some objects implemented by only 1 agent • Some objects not implemented by any agent

  8. RFC 2021 Implementation Report (2/5) • Following objects have 1 implementation: • probeHardwareRev • probeResetControl • probeDownloadFile • probeDownloadTFTPServer • probeDownloadAction • probeDownloadStatus • netDefaultGateway • tokenRingMLStatsDroppedFrames • tokenRingMLStatsCreateTime • tokenRingPStatsDroppedFrames • tokenRingPStatsCreateTime • ringStationControlDroppedFrames • ringStationControlCreateTime • sourceRoutingStatsDroppedFrames • sourceRoutingStatsCreateTime

  9. RFC 2021 Implementation Report (3/5) • Following objects have no implementations: • serialConfigTable • serialMode • serialProtocol • serialTimeout • serialModemInitString • serialModemHangUpString • serialModemConnectResp • serialModemNoConnectResp • serialDialoutTimeout • serialStatus • serialConnectionTable • serialConnectDestIpAddress • serialConnectType • serialConnectDialString • serialConnectSwitchConnectSeq • serialConnectSwitchDisconnectSeq • serialConnectSwitchResetSeq • serialConnectOwner • serialConnectStatus

  10. RFC 2021 Implementation Report (4/5) • Following objects have no implementations: • netConfigTable • netConfigIPAddress • netConfigSubnetMask • netConfigStatus • TimeFilter implementations vary • Mibwalk/GetBulk/GetNext friendly • wrap to next object when TF index changes • Strict compliance • iterate through every TF value; mibwalk/getbulk may never end • Both modes supported • Proprietary MIB object to select mode

  11. RFC 2021 Implementation Report (5/5) • Decision needed on RFC 2021 Advancement • Wait for more implementation reports • Deprecate objects without 2 implementations and advance rest of MIB to Draft Standard • ‘Fix’ TimeFilter somehow and cycle at Proposed Standard • Add standard TF mode select object • Change TF behavior somehow to allow mibwalk/getbulk friendly behavior

More Related