HTTP/2 302 date: Mon, 14 Jul 2025 07:06:39 GMT content-type: text/html content-length: 143 location: https://get.ietf.org/implementation-report/report-rfc1513.txt cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 expires: Thu, 01 Jan 1970 00:00:01 GMT vary: Accept-Encoding server: cloudflare cf-ray: 95ef2dbb6a01d3d4-BLR alt-svc: h3=":443"; ma=86400 HTTP/2 200 date: Mon, 14 Jul 2025 07:06:40 GMT content-type: text/plain etag: W/"1bc32dfcf85fa12f8cc0b4dafc5e2783" vary: Accept-Encoding server: cloudflare cf-ray: 95ef2dbbd9039dfa-BLR content-encoding: gzip alt-svc: h3=":443"; ma=86400 Interoperability Report for RFC 1513 Andy Bierman RMONMIB WG Chair April 7, 1999 1.0) Introduction Interoperability documentation must be gathered to support the advancement of documents on the IETF standards track. This memo documents the agent and NMS implementations of the Token Ring RMON MIB, and intends to demonstrate that RFC 1513 should be advanced from Proposed Standard to Draft Standard by the IESG. 1.1) Background The following email was sent by the WG Chair to the RMONMIB WG mailing list (rmonmib@cisco.com) on November 20, 1998: In accordance with section 5 of RFC 2438, I am requesting that parties which have implemented all or part of Token Ring RMON MIB (RFC 1513) send an implementation report to the WG mailing list or a private email to me. The WG is attempting to advance RFC 1513 from Proposed Draft to Draft Standard status. This implementation report should include the following information: - specify MIB objects implemented and/or not implemented - specify for each object whether the implementation is for agent, NMS, or both. - specify at least one product name and SW version that contains the implementation. This does not have to be a commercial implementation. - specify origin of the implementation(s), e.g. internal development or purchased engine code from XYZ corp. or a combination of both. - specify any independent product implementations that you believe your product(s) to interoperate with. Be specific as to agent vs. application, and which MIB objects are used. I will compile an interoperability report and forward it to the OPS Area Directors when the survey is completed. The survey will close in 6 weeks (on 1-1-99). [Actual survey close: 3-12-99] --------------------------------------------------------------- 2) Interoperability Summary The following charts show the MIB groups implemented and the multi-vendor interoperability for RFC 1513. These tables are derived from the detailed responses from each implementor. Table 1: Implementation Summary ------------------------------- MIB Group | V1 | V2 | V3 | V4 | V5 | V6 | V7 | V8 | V9 | -------------+----+----+----+----+----+----+----+----+----+ ML Stats | A | AM | AM | AM | AM | A | AM | M | AM | -------------+----+----+----+----+----+----+----+----+----+ P Stats | A | AM | AM | AM | AM | A | AM | M | AM | -------------+----+----+----+----+----+----+----+----+----+ ML History | A | AM | AM | AM | | A | AM | | AM | -------------+----+----+----+----+----+----+----+----+----+ P History | A | AM | AM | AM | | A | AM | | AM | -------------+----+----+----+----+----+----+----+----+----+ Ring Station | a | AM | AM | AM | | A | AM | | AM | -------------+----+----+----+----+----+----+----+----+----+ RS Order | A | AM | AM | AM | | A | AM | | AM | -------------+----+----+----+----+----+----+----+----+----+ RS Config | | AM | AM | AM | | A | AM | | AM | -------------+----+----+----+----+----+----+----+----+----+ Source Route | | AM | AM | AM | | A | AM | | AM | -------------+----+----+----+----+----+----+----+----+----+ Key --- a = partial agent implementation A = full agent implementation m = partial manager application implementation M = full manager application implementation Vn = Vendor code, listed below ------------------------------ V1 = Cisco Systems V2 = Cabletron V3 = HP V4 = Bay/Nortel Networks V5 = 3Com V6 = IBM V7 = Netscout V8 = INS V9 = Technically Elite Table 2: Interoperability Matrix -------------------------------- Mgr Apps ---> Agents | V | V1 | V2 | V3 | V4 | V5 | V6 | V7 | V8 | V9 | Other ----+----+----+----+----+----+----+----+----+----+------+ V1 | | | | | | | X | | | | ----+----+----+----+----+----+----+----+----+----+------+ V2 | | X | | | | | | | | | ----+----+----+----+----+----+----+----+----+----+------+ V3 | | | X | | X | | X | | X | X | ----+----+----+----+----+----+----+----+----+----+------+ V4 | | | | X | | | X | | X | | ----+----+----+----+----+----+----+----+----+----+------+ V5 | | | | | X | | X | | | | ----+----+----+----+----+----+----+----+----+----+------+ V6 | | | | | | | | | | | ----+----+----+----+----+----+----+----+----+----+------+ V7 | X | | | | | | X | X | | X | ----+----+----+----+----+----+----+----+----+----+------+ V8 | | | | | | | | | | | ----+----+----+----+----+----+----+----+----+----+------+ V9 | X | | X | X | X | | X | | | | ----+----+----+----+----+----+----+----+----+----+------+ Other | | | | | X | | X | | X | | ----+----+----+----+----+----+----+----+----+----+------+ Key --- X = interoperability reported Vn = Vendor code, listed below ------------------------------ V1 = Cisco Systems V2 = Cabletron V3 = HP V4 = Bay/Nortel Networks V5 = 3Com V6 = IBM V7 = Netscout V8 = INS V9 = Technically Elite 3) Conclusions Based on the survey responses received, there is sufficient evidence to recommend to the IESG that RFC 1513 should be advanced from Proposed Standard to Draft Standard status. This MIB has been deployed in commercial products by many venders, and has been proven useful over the years by the customers of these vendors. There are more implementations of part or all of this RFC than are documented in this implementation report, because no anonymous reports are included. In some cases of 'known implementations', th authors/owners of the implementation did not respond the survey at all. Appendix A) Interoperability Report Responses Responses are presented in the order received. They have been editing for formatting and brevity. ========================= A.1) Cisco Systems (klingle@cisco.com) a) Objects Implemented: Agent tokenRingMLStatsTable tokenRingPStatsTable tokenRingMLHistoryTable tokenRingPHistoryTable ringStationControlTable ringStationOrderTable b) Objects not Implemented: Agent ringStationTable (note 1) ringStationConfigControlTable (note 1) ringStationConfigTable sourceRoutingStatsTable note 1: Will be supported in the future (sometime in 1999). c) Product names and versions of implementation HW: Catalyst 5000 Token Ring Switching modules (wsx5030 & wsx5031) SW: Catalyst 5000 Token Ring Switching Module software version 3.2(3) Catalyst 5xxx Supervisor software versions 3.2(3), 4.3(1a) There are other versions, but these are some of the most current. SNMP and RMON agent code runs on supervisor card. TR switch module supplies the instrumentation. RFC 1513 MIB support is not available unless at least one TR switch module is installed in the chassis. d) Interoperability with products from other vendors - NetScout Traffic Director 5.3/5.5 (management application) on all platforms - Technically Elite MeterWare 2.3 on unix platform ========================= A.2) Cabletron Systems (frechett@cabletron.com) We have an agent implementation that was internally developed on the following products: 1)Token Ring Management Module (TRMM-2) 2)Token Ring MicroLAN switch (9T125-24) 3)Token Ring Concentrator (MicroMMAC-T) 4)Token Ring Switch (9T425-16) We support an NMS implementation within: 1)Spectrum Element Manager software. ========================= A.3) HP (MARK_PHANEUF@HP-ColSprings-om1.om.hp.com) - specify MIB objects implemented and/or not implemented - specify for each All of the HP Token-Ring LanProbe's fully implement RFC1513. -object whether the implementation is for agent, NMS, or both. The HP LanProbe, WanProbe and ATMProbes are of the 'agent' class. The HP NetMetrix application suite is of the 'NMS' class. - specify at least one product name and SW version that contains the implementation. This does not have to be a commercial implementation. For Probes: 4985B - Token-Ring LanProbe For NMS HP Openview NetMetrix/UX version 6.0 - specify origin of the implementation(s), e.g. internal development or purchased engine code from XYZ corp. or a combination of both. Internal development of RMON implementations - specify any independent product implementations that you believe your product(s) to interoperate with. Be specific as to agent vs. application, and which MIB objects are used. Concord Communications - "Network Heath" NMS RFC 1513 complete ========================= A.4) Bay/Nortel Networks (Yu_Huang@BayNetworks.COM) The rfc1513 was implemented and has been working well in token ring products of Bay Networks. As requested in your call for interoperability survey, I address some items listed in the implementation report information. 1. MIB groups implemented for rfc1513 : Token ring statistics group : MAC layer and promiscuous statistics groups Token ring history group : MAC layer and promiscuous history groups Token ring station group Token ring station order group Token ring station config group Token ring source routing group 2. The rfc1513 implementation is for both agent and NMS 3. The rfc1513 was implemented and has been using in token ring products. ========================= A.5) 3Com (Ian_Partridge@3com.com) [ed. - converted from Word to ASCII] 3Com Network Management Hardware/Software RFC 1513, Token Ring Extensions to RMON MIB, Implementation Report Agents The RMON agent for the RMON Probes listed below implements all groups/objects of RFC 1513: SuperStack II Enterprise Monitor Transcend Enterprise Monitor 570 Single Port Token-Ring AXON Token-Ring LANServant RMON Probe AXON Token-Ring LANServant RMON Probe Analysis Server This agent, the latest version of which is 4.17, is an internal development of AXON Networks Inc. and later 3Com Corporation. NMS Applications ---------------- LANsentry --------- Transcend LANsentry Manager, an internal AXON Networks Inc. and 3Com Corporation development implements all groups/objects from RFC 1513. The current version of LANsentry/unix in the field is 5.2.0, which is part of Transcend Enterprise Manager/unix 4.2.2 The current version of LANsentry/windows in the field is 5.1, which is part of Transcend Enterprise Manager/NT 1.0 LANsentry is known to inter-operate with among others the following third party RMON probe agents: - Hewlett Packard HP Ethernet LanProbe - SNMP 1.0 (B.02.00.00), (Boot ROM A.00.01 8M) HP Quad Ethernet LanProbe - SNMP 1.0 (A.00.00.1A), (Boot ROM A.00.02.02 64M) HP LAN Probe II Token-Ring agent A.01.02 - SolCom 8Mb Single Port Ethernet RMON Probe - SNMP 1.0 (2.11) (Boot ROM V1.54 8M) - Shomiti Systems Inc. 8-port, 256Mb, Fast Ethernet Voyager probe V1.0 Build 118 MODEL NUMBER: 1005, REVISION NUMBER: 1.1 - TEC [ed. - Technically Elite] Ethermeter1000 RMON2 probe agent version 4.0.2.4 / 4.0.2.5 Traffix ------- Transcend Traffix Manager, an internal AXON Networks Inc. and 3Com Corporation development, which is now at version 2.0, implements the following objects from RFC 1513 tokenRingMLStats index datasource dropevents macoctets macpkts ringpurgeevents beaconevents claimtokenevents lineerrors internalerrors bursterrors acerrors abortErrors lostframerrors congestionerrors framecopiederrors frequencyerrors tokenerrors softerrorreports ringpollevents owner status tokenRingPStats index datasource dataoctets datapkts databcastpkts datamcastpkts owner status Traffix works with 3Com RMON devices that support RFC1513 including the SuperStack II Enterprise Monitor and Transcend Enterprise Monitor 570 RMON Probes. However no explicit token ring interoperability testing has been carried out with third party agents. ========================= A.6) IBM (bmillard@us.ibm.com) The IBM 8239 (token ring hub) fully supports RFC1757 and RFC1513. Also, the IBM HTMAC (High-End Token Ring Mac Daughter Card for the 8260) fully supports RFC1757 and RFC1513. The code for both was purchased from 3COM (AXON part)-- with internal development done as well. Becky (919) 543-1816 JXFA/B660-C207 8239 Level -3 Support Device Management Development IBM Networking Hardware ========================= A.7) Netscout (anil@netscout.com) 1) We have implemented all objects in RFC 1513. 2) All the objects have been implemented in both the agent (NetScout Probe) and the manager (NetScout manager). 3) Product line name is NetScout. It is also sold as a private label by Cisco as SwitchProbe and TrafficDirector. The latest versions supporting this functionality are 4.2.0 and 5.2.0 for agent and manager respectively. 4) All development has been done internally. We have also OEMed our agent code to Cisco, Paradyne and many other vendors through Eplilogue/ISI. 5) NetScout agents have been officially certified to work with the following applications: Cisco Concord INS DeskTalk Apogee We also have (anecdotal) evidence that our product works with many other vendors like NAI, Optimal, CACI and many others. Most of these vendors do very little configuration (SNMP Sets) and make use of the stats, history, host and conversation groups of these two RFCs. 6) Our manager is known to work with most agent implementations (unofficially certified by our customers) including those from HP, Bay, Cisco, 3Com, Fore and TEC. 7) NetScout has also participated in all the RMON1/RMON2 interoperability tests conducted by outside organizations during the last 3 years. Any fixes required have been incorporated into the released version of NetScout. Anil Singhal ========================= A.8) INS (stevew@ins.com) INS EnterprisePRO supports: rfc1513: tokenRingMLStatsTable tokenRingPStatsTable ========================= A.9) Technically Elite (rsdietz@tecelite.com) [ed. - reformatted from Excel, due to the late submission, only 1 table was converted to ASCII. The entire report in Excel format will be posted on the RMONMIB WG ftp site.] MIB Group P1 P2 P3 P4 P5 ----------------------------------------------------------- tokenRingMLStatsTable Y Y Y Y Y tokenRingPStatsTable Y Y Y Y Y historyControlTable Y Y Y Y Y tokenRingMLHistoryTable Y Y Y Y Y tokenRingPHistoryTable Y Y Y Y Y alarmTable Y Y Y Y Y hostControlTable Y Y Y N Y hostTable Y Y Y N Y hostTimeTable Y Y Y N Y hostTopNControlTable Y Y Y N Y hostTopNTable Y Y Y N Y matrixControlTable Y Y Y N Y matrixSDTable Y Y Y N Y matrixDSTable Y Y Y N Y filterTable Y Y Y N Y channelTable Y Y Y N Y bufferControlTable Y Y Y N Y captureBufferTable Y Y Y N Y eventTable Y Y Y Y Y logTable Y Y Y Y Y Product Key: ------------ P1 = RMONplus (V 2.0) P2 = TokenMeter 1000 (V 5.2.0.2) P3 = MultiMeter 3000 (V 4.0.2.4) P4 = MeterWorks Lite (V 5.01) P5 = MeterWork Std (V 5.01)