|
Go directly to: | Search through RFCs, STDs, BCPs, and FYIs View search tips View the RFC Index View the Most popular RFCs |
Network Working Group R. Enger Request for Comments: 1470 ANS FYI: 2 J. Reynolds Obsoletes: 1147 ISI Editors June 1993 FYI on a Network Management Tool Catalog: Tools for Monitoring and Debugging TCP/IP Internets and Interconnected Devices Status of this Memo This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited. Abstract The goal of this FYI memo is to provide an update to FYI 2, RFC 1147 [1], which provided practical information to site administrators and network managers. New and/or updated tools are listed in this RFC. Additonal descriptions are welcome, and should be sent to: noctools- entries@merit.edu. Introduction A static document cannot incorporate references to the latest tools nor recent revisions to the older catalog entries. To provide a more timely and responsive information source, the NOCtools catalog is available on-line via the Internet and Usenet. news comp.networks.noctools ftp wuarchive.wustl.edu:/doc/noctools Because of publication delays and other factors, some of the entries in this catalog may be out of date. The reader is urged to consult the on-line service to obtain the most up-to-date information. The index provided in this document reflects the current contents of the on-line documentation. The NOCtools2 Working Group of the Internet Engineering Task Force (IETF) has compiled this revised catalog. Future revisions will be incorporated into the on-line NOCtools catalog. The reader is encouraged to submit new or revised entries for (near-immediate) electronic publication. NOCTools2 Working Group [Page 1] RFC 1470 FYI: Network Management Tool Catalog June 1993 The tools described in this catalog are in no way endorsed by the IETF. For the most part, we have neither evaluated the tools in this catalog, nor validated their descriptions. Most of the descriptions of commercial tools have been provided by vendors. Caveat Emptor. Acknowledgements This catalog is the result of work on the part of the NOCTools2 Working Group of the User Services Area of the IETF. The following individuals made especially notable contributions: Chris Myers, Darren Kinley, Gary Malkin, Mohamed Ellozy, and Mike Patton. Current Postings The current contents of the NOCtools catalog may be retrieved via anonymous FTP from wuarchive.wustl.edu. The entries are stored as individual files in the directory /doc/noctools. "No-Writeups" Appendix This section contains references to tools which are known to exist, but which have not been fully cataloged. If anyone wishes to author an entry for one of these tools please contact us at: noctools-request@merit.edu Keep in mind that if these or other tools are included in the future, they will be available in the on-line version of the catalog. Each mention is separated by a <form-feed> for improved readability. If you intend to actually print-out this section of the catalog, then you should probably strip-out the <ff>. How to Submit/Update an Entry 1) review the template included below to determine what information you will need to collect, 2) review the keywords to see what your indexing options are, 3) assemble (update) catalog entry to include results of 1) and 2). 4) Submit your entry using either of the following two methods: a) Post your submission to: comp.internet.noctools.submissions b) Email your submission to: noctools-entries@merit.edu New entries will be circulated automatically upon reception. As time permits, the NOCtools editors will review recent submissions and incorporate them into the master indexes. Enquiries regarding the NOCTools2 Working Group [Page 2] RFC 1470 FYI: Network Management Tool Catalog June 1993 status of a submission should be E-Mailed to: noctools-request@merit.edu Those submitting an entry to the catalog should insure that any E- mail addresses provided are correct and functional. Either the catalog editors or prospective users of your tool may wish to reach you. NOCTools2 Working Group [Page 3] RFC 1470 FYI: Network Management Tool Catalog June 1993 TEMPLATE NAME <tool-name> KEYWORDS [<keyword-A1>[,<keyword-A2>[,...,<keyword-An>]]]; [<keyword-B1>[,<keyword-B2>[,...,<keyword-Bn>]]]; [<keyword-C1>[,<keyword-C2>[,...,<keyword-Cn>]]]; [<keyword-D1>[,<keyword-D2>[,...,<keyword-Dn>]]]; [<keyword-E1>[,<keyword-E2>[,...,<keyword-En>]]]. ABSTRACT <summary of the tool> <summary of the tool> <summary of the tool> MECHANISM <high level technical details of how it works> <high level technical details of how it works> <high level technical details of how it works> CAVEATS <any warnings or cautions> <any warnings or cautions> <any warnings or cautions> BUGS <any warnings or cautions> <any warnings or cautions> <any warnings or cautions> LIMITATIONS <any warnings or cautions> <any warnings or cautions> <any warnings or cautions> HARDWARE REQUIRED <list any hardware requirements> <list any hardware requirements> <list any hardware requirements> NOCTools2 Working Group [Page 4] RFC 1470 FYI: Network Management Tool Catalog June 1993 SOFTWARE REQUIRED <list any software requirements> <list any software requirements> <list any software requirements> AVAILABILITY AND CONTACT POINT FOR INFORMATION ABOUT THIS TOOL <How to acquire the tool.> <Location/Contact Info to access/obtain tool> CONTACT POINT FOR CHANGES TO THIS CATALOG ENTRY <Contact info for person responsible for catalog entry> DATE OF MOST RECENT UPDATE TO THIS CATALOG ENTRY <YYMMDD> Keywords This catalog uses "keywords" for terse characterizations of the tools. Keywords are abbreviated attributes of a tool or its use. To allow cross-comparison of tools, uniform keyword definitions have been developed, and are given below. Following the definitions, there is an index of catalog entries by keyword. Keyword Definitions The keywords are always listed in a prefined order, sorted first by the general category into which they fall, and then alphabetically. The categories that have been defined for management tool keywords are: o the general management area to which a tool relates or a tool's functional role; o the network resources or components that are managed; o the mechanisms or methods a tool uses to perform its functions; o the operating system and hardware environment of a tool; and o the characteristics of a tool as a hardware product or software release. NOCTools2 Working Group [Page 5] RFC 1470 FYI: Network Management Tool Catalog June 1993 The keywords used to describe the general management area or functional role of a tool are: Alarm a reporting/logging tool that can trigger on specific events within a network. Analyzer a traffic monitor that reconstructs and interprets pro- tocol messages that span several packets. Benchmark a tool used to evaluate the performance of network com- ponents. Control a tool that can change the state or status of a remote network resource. Debugger a tool that by generating arbitrary packets and moni- toring traffic, can drive a remote network component to various states and record its responses. Generator a traffic generation tool. Manager a distributed network management system or system com- ponent. Map a tool that can discover and report a system's topology or configuration. Reference a tool for documenting MIB structure or system confi- guration. Routing a packet route discovery tool. Security a tool for analyzing or reducing threats to security. Status a tool that remotely tracks the status of network com- ponents. NOCTools2 Working Group [Page 6] RFC 1470 FYI: Network Management Tool Catalog June 1993 Traffic a tool that monitors packet flow. The keywords used to identify the network resources or components that a tool manages are: Bridge a tool for controlling or monitoring LAN bridges. CHAOS a tool for controlling or monitoring implementations of the CHAOS protocol suite or network components that use it. DECnet a tool for controlling or monitoring implementations of the DECnet protocol suite or network components that use it. DNS a Domain Name System debugging tool. Ethernet a tool for controlling or monitoring network components on ethernet LANs. FDDI a tool for controlling or monitoring network components on FDDI LANs or WANs. IP a tool for controlling or monitoring implementations of the TCP/IP protocol suite or network components that use it. OSI a tool for controlling or monitoring implementations of the OSI protocol suite or network components that use it. NFS a Network File System debugging tool. Ring a tool for controlling or monitoring network components on Token Ring LANs. NOCTools2 Working Group [Page 7] RFC 1470 FYI: Network Management Tool Catalog June 1993 SMTP an SMTP debugging tool. Star a tool for controlling or monitoring network components on StarLANs. The keywords used to describe a tool's mechanism are: CMIS a network management system or component based on CMIS/CMIP, the Common Management Information System and Protocol. Curses a tool that uses the "curses" tty interface package. Eavesdrop a tool that silently monitors communications media (e.g., by putting an ethernet interface into "promiscu- ous" mode). NMS the tool is a component of or queries a Network Manage- ment System. Ping a tool that sends packet probes such as ICMP echo mes- sages; to help distinguish tools, we do not consider NMS queries or protocol spoofing (see below) as probes. Proprietary a distributed tool that uses proprietary communications techniques to link its components. RMON a tool which employs the RMON extensions to SNMP. SNMP a network management system or component based on SNMP, the Simple Network Management Protocol. Spoof a tool that tests operation of remote protocol modules by peer-level message exchange. X a tool that uses X-Windows. NOCTools2 Working Group [Page 8] RFC 1470 FYI: Network Management Tool Catalog June 1993 The keywords used to describe a tool's operating environment are: DOS a tool that runs under MS-DOS. HP a tool that runs on Hewlett-Packard systems. Macintosh a tool that runs on Macintosh personal computers. OS/2 a tool that runs under the OS/2 operating system. Standalone an integrated hardware/software tool that requires only a network interface for operation. Sun a tool that runs on Sun Microsystems platforms. (binary distribution built for use on a Sun.) UNIX a tool that runs under 4.xBSD UNIX or related OS. VMS a tool that runs under DEC's VMS operating system. The keywords used to describe a tool's characteristics as a hardware or software acquisition are: Free a tool is available at no charge, though other restric- tions may apply (tools that are part of an OS distribu- tion but not otherwise available are not listed as "free"). Library a tool packaged with either an Application Programming Interface (API) or object-level subroutines that may be loaded with programs. Sourcelib a collection of source code (subroutines) upon which developers may construct other tools. NOCTools2 Working Group [Page 9] RFC 1470 FYI: Network Management Tool Catalog June 1993 Tools Indexed by Keywords Following is an index of the most up-to-date catalog entries sorted by keyword, which is available via: news comp.networks.noctools.tools ftp wuarchive.wustl.edu:/doc/noctool This index can be used to locate the tools with a particular attribute: tools are listed under each keyword that characterizes them. The keywords and the subordinate lists of tools under them are in alphabetical order. Alarm ----- CMIP Library Dual Manager Eagle EMANATE EtherMeter LanProbe LANWatch MONET NetMetrix Load Monitor NetMetrix Protocol Analyzer NETMON for Windows NETscout NOCOL SNMP Libraries and Utilities from Empire Technologies SNMP Libraries and Utilities from SNMP Research snmpd from Empire Technologies SpiderMonitor XNETMON from SNMP Research xnetmon from Wellfleet Analyzer -------- LANVista LANWatch NetMetrix Protocol Analyzer NETscout PacketView Sniffer SpiderMonitor NOCTools2 Working Group [Page 10] RFC 1470 FYI: Network Management Tool Catalog June 1993 Benchmark --------- hammer & anvil iozone LADDIS LANVista nhfsstone SPIMS spray ttcp XNETMON from SNMP Research CMIS ---- CMIP library Generic Managed System MIB Browser Control ------- CMIP Library Dual Manager Eagle MIB Manager from Empire Technologies MONET NETMON for Windows proxyd SNMP Libraries and Utilities from Empire Technologies SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System snmpd from Empire Technologies TokenVIEW XNETMON from SNMP Research Debugger -------- Ethernet Box II LANVista NetMetrix Traffic Generator ping from UCB SPIMS XNETMON from SNMP Research Generator --------- hammer & anvil LADDIS LANVista NOCTools2 Working Group [Page 11] RFC 1470 FYI: Network Management Tool Catalog June 1993 NetMetrix Traffic Generator nhfsstone ping ping from UCB Sniffer SpiderMonitor spray TTCP Manager ------- Beholder CMIP Library CMU SNMP Distribution decaddrs by Wellfleet Dual Manager EMANATE Ethernet Box II getone by Wellfleet Interactive Network Map LanProbe LANVista MIB Manager from Empire Technologies MONET NetLabs CMOT Agent NetLabs SNMP Agent NETMON for Windows NETscout NNStat NOCOL OverVIEW SAS/CPE for Open Systems Software SNMP Development Kit SNMP Libraries and Utilities from Empire Technologies SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System snmpd from Empire Technologies tokenview Tricklet Wollongong-Manager XNETMON from SNMP Research XNETMON from Wellfleet xnetperfmon Map --- decaddrs by Wellfleet Dual Manager NOCTools2 Working Group [Page 12] RFC 1470 FYI: Network Management Tool Catalog June 1993 etherhostprobe EtherMeter Interactive Network Map LanProbe NETMON for Windows Network Integrator I NPRV SNMP Libraries and Utilities from SNMP Research XNETMON by SNMP Research XNETMON by Wellfleet Reference --------- EMANATE ethernet-codes HyperMIB MIB Manager from Empire Technologies XNETMON Routing ------- arp decaddrs by Wellfleet etherhostprobe getone by Wellfleet hopcheck MONET net_monitor NETMON for Windows netstat NPRV ping from UCB query traceroute Security -------- Computer Security Checklist Dual Manager Eagle EMANATE LAN Patrol SNMP Libraries and Utilities from SNMP Research XNETMON by SNMP Research xnetperfmon NOCTools2 Working Group [Page 13] RFC 1470 FYI: Network Management Tool Catalog June 1993 Status ------ Beholder CMIP Library CMU SNMP DiG dnsstats doc Dual Manager EMANATE fping getone by Wellfleet host Internet Rover lamers LanProbe mconnect MONET net_monitor Netlabs CMOT Agent Netlabs SNMP Agent NETscout NNStat NOCOL NPRV OverVIEW ping ping from UCB proxyd from SNMP Research SAS/CPE SNMP Development Kit SNMP Libraries and Utilities from Empire Technologies SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System PSI SNMP snmpd from Empire Technologies snmpd from SNMP Research TokenVIEW Tricklet vrfy XNETMON by SNMP Research xnetmon by Wellfleet xnetperfmon xup NOCTools2 Working Group [Page 14] RFC 1470 FYI: Network Management Tool Catalog June 1993 Traffic ------- etherfind EtherMeter Ethernet Box II EtherView getethers LAN Patrol LanProbe LANVista LANWatch ENTM MONET NetMetrix Load Monitor NetMetrix NFS Monitor NetMetrix Protocol Analyzer NetMetrix Traffic Generator NETMON by Mitre NETscout netwatch Network Integrator I nfswatch nhfsstone NNStat ositrace PacketView Sniffer SpiderMonitor spray tcpdump tcplogger trpt ttcp XNETMON by SNMP Research Bridge ------ decaddrs by Wellfleet EMANATE MIB Manager from Empire Technologies MONET proxyd by SNMP Research SAS/CPE SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System snmpd from SNMP Research XNETMON from SNMP Research NOCTools2 Working Group [Page 15] RFC 1470 FYI: Network Management Tool Catalog June 1993 CHAOS ----- Interactive Network Map LANWatch DECnet ------ decaddrs by Wellfleet LANVista LANWatch MONET net_monitor NetMetrix Protocol Analyzer NETMON for Windows NETscout Sniffer SNMP Libraries and Utilities from SNMP Research SpiderMonitor XNETMON from SNMP Research xnetperfmon from SNMP Research DNS --- DiG dnsstats doc lamers LANWatch NetMetrix Protocol Analyzer NOCOL Ethernet -------- arp Beholder Eagle EMANATE etherfind etherhostprobe EtherMeter Ethernet Box II ethernet-codes EtherView getethers LAN Patrol LanProbe LANVista LANWatch NOCTools2 Working Group [Page 16] RFC 1470 FYI: Network Management Tool Catalog June 1993 ENTM Interactive Network Map MONET NetMetrix Load Monitor NetMetrix NFS Monitor NetMetrix Protocol Analyzer NetMetrix Traffic Generator NETMON for Windows NETscout netwatch Network Integrator I nfswatch NNStat PacketView proxyd from SNMP Research SAS/CPE Sniffer SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System from SNMP Research snmpd from SNMP Research SpiderMonitor tcpdump XNETMON from SNMP Research xnetperfmon from SNMP Research FDDI ---- EMANATE ethernet-codes NetMetrix Load Monitor NetMetrix NFS Monitor NetMetrix Protocol Analyzer NetMetrix Traffic Generator nfswatch SAS/CPE SNMP Libraries and utilities from SNMP Research SNMP Packaged Agent System from SNMP Research snmpd from SNMP Research XNETMON from SNMP Research IP -- arp CMU SNMP Dual Manager Eagle EMANATE etherfind NOCTools2 Working Group [Page 17] RFC 1470 FYI: Network Management Tool Catalog June 1993 etherhostprobe EtherView fping getone from Wellfleet hammer & anvil hopcheck Internet Rover LanProbe LANVista LANWatch ENTM Interactive Network Map MIB Manager from Empire Technologies MONET net_monitor Netlabs CMOT Agent Netlabs SNMP Agent NetMetrix Load Monitor NetMetrix Protocol Analyzer NetMetrix Traffic Generator NETMON by Mitre NETMON for Windows NETscout netstat netwatch nfswatch nhfsstone NNStat NOCOL NPRV OverVIEW PacketView ping ping from UCB proxyd from SNMP Research query SAS/CPE SNMP Development Kit SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System from SNMP Research PSI SNMP snmpd from Empire Technologies snmpd from SNMP Research PSI SNMP SpiderMonitor SPIMS spray tcpdump NOCTools2 Working Group [Page 18] RFC 1470 FYI: Network Management Tool Catalog June 1993 tcplogger traceroute trpt ttcp XNETMON from SNMP Research xnetmon from Wellfleet xnetperfmon from SNMP Research OSI --- CMIP Library Dual Manager EMANATE LANVista LANWatch Netlabs CMOT Agent NetMetrix Protocol Analyzer NETMON for Windows NETscout NOCOL ositrace proxyd from SNMP Research SAS/CPE Sniffer SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System from SNMP Research snmpd from SNMP Research SpiderMonitor SPIMS XNETMON from SNMP Research xnetperfmon from SNMP Research NFS --- etherfind EtherView iozone LADDIS NetMetrix NFS Monitor NetMetrix Protocol Analyzer NETscout nfswatch nhfsstone Sniffer tcpdump NOCTools2 Working Group [Page 19] RFC 1470 FYI: Network Management Tool Catalog June 1993 Ring ---- Eagle EMANATE Interactive Network Map LANVista LANWatch NetMetrix Load Monitor NetMetrix NFS Monitor NetMetrix Protocol Analyzer NetMetrix Traffic Generator NETMON by Mitre NETMON for Windows NETscout netwatch PacketView proxyd from SNMP Research Sniffer SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System from SNMP Research snmpd from SNMP Research TokenVIEW XNETMON from SNMP Research xnetperfmon from SNMP Research SMTP ---- host Internet Rover LANWatch mconnect NetMetrix Protocol Analyzer Sniffer vrfy Star ---- EMANATE Interactive Network Map LAN Patrol LANWatch NETMON for Windows NETscout proxyd from SNMP Research Sniffer SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System from SNMP Research snmpd from SNMP Research NOCTools2 Working Group [Page 20] RFC 1470 FYI: Network Management Tool Catalog June 1993 XNETMON from SNMP Research xnetperfmon from SNMP Research Curses ------ Eagle Internet Rover net_monitor nfswatch NOCOL PSI SNMP Eavesdrop --------- etherfind Ethernet Box II EtherView LAN Patrol LANVista LANWatch ENTM NetMetrix Load Monitor NetMetrix NFS Monitor NetMetrix Protocol Analyzer NetNetrix Traffic Generator NETMON from Mitre NETscout netwatch nfswatch NNStat OSITRACE PacketView Sniffer SpiderMonitor tcplogger trpt NMS --- CMU SNMP decaddrs from Wellfleet Dual Manager EMANATE EtherMeter Ethernet Box II getone from Wellfleet Interactive Network Map MONET NOCTools2 Working Group [Page 21] RFC 1470 FYI: Network Management Tool Catalog June 1993 Netlabs CMOT Agent Netlabs SNMP Agent NETMON for Windows NETscout NNStat NOCOL OverVIEW proxyd from SNMP Research SNMP Development Kit SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System from SNMP Research PSI SNMP snmpd from Empire Technologies snmpd from SNMP Research TokenVIEW XNETMON from SNMP Research xnetmon from Wellfleet xnetperfmon from SNMP Research Ping ---- etherhostprobe fping getethers hopcheck Interactive Network Map Internet Rover LANWatch net_monitor NOCOL NPRV ping ping from UCB spray traceroute ttcp XNETMON from SNMP Research xup Proprietary ----------- Eagle EtherMeter Ethernet Box II LanProbe LANVista TokenVIEW NOCTools2 Working Group [Page 22] RFC 1470 FYI: Network Management Tool Catalog June 1993 RMON ---- Beholder SNMP ---- Beholder CMU SNMP decaddrs from Wellfleet Dual Manager EMANATE getone from Wellfleet Interactive Network Map MIB Manager from Empire Technologies MONET Netlabs SNMP Agent NetMetrix Load Monitor NetMetrix NFS Monitor NetMetrix Protocol Analyzer NetMetrix Traffic Generator NETMON for Windows NETscout NOCOL OverVIEW proxyd from SNMP Research SNMP Development Kit SNMP Libraries and utilities from SNMP Research SNMP Packaged Agent System from SNMP Research PSI SNMP snmpd from Empire Technologies snmpd from SNMP Research Wollongong-Manager XNETMON from SNMP Research xnetmon from Wellfleet xnetperfmon from SNMP Research Spoof ----- DiG doc Internet Rover host LADDIS mconnect nhfsstone NOCOL query SPIMS NOCTools2 Working Group [Page 23] RFC 1470 FYI: Network Management Tool Catalog June 1993 vrfy X - Dual Manager Interactive Network Map MIB Manager from Empire Technologies NetMetrix Load Monitor NetMetrix NFS Monitor NetMetrix Protocol Analyzer NetMetrix Traffic Generator SAS/CPE PSI SNMP XNETMON from SNMP Research xnetperfmon from SNMP Research xup DEC --- Wollongong-Manager DOS --- Computer Security Checklist Ethernet Box II hammer & anvil hopcheck iozone LAN Patrol LANVista netmon NETMON for Windows netwatch OverVIEW PacketView ping SAS/CPE SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System from SNMP Research snmpd from SNMP Research TokenVIEW Wollongong-Manager xnetperfmon from SNMP Research NOCTools2 Working Group [Page 24] RFC 1470 FYI: Network Management Tool Catalog June 1993 HP -- iozone SAS/CPE xup Macintosh --------- HyperMIB OS/2 ---- Beholder Tricklet Standalone ---------- LANVista Sniffer SNMP Packaged Agent System from SNMP Research SpiderMonitor Sun --- Avatar SunSNMPD Wollongong Manager UNIX ---- arp CMIP Library CMU SNMP decaddrs from Wellfleet DiG doc dnsstats Eagle etherfind etherhostprobe EtherView fping getethers getone from Wellfleet host Interactive Network Map Internet Rover iozone LADDIS NOCTools2 Working Group [Page 25] RFC 1470 FYI: Network Management Tool Catalog June 1993 lamers mconnect MIB Manager from Empire Technologies MONET net_monitor Dual Manager NetMetrix Load Monitor NetMetrix NFS Monitor NetMetrix Protocol Analyzer NetMetrix Traffic Generator NETMON from Mitre NETscout netstat Network Integrator I nfswatch nhfsstone NNStat NOCOL OSITRACE ping ping from UCB proxyd from SNMP Research query SAS/CPE SNMP Development Kit SNMP Libraries and Utilities from Empire Technologies SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System from SNMP Research PSI SNMP snmpd from Empire Technologies snmpd from SNMP Research SPIMS spray tcpdump tcplogger traceroute Tricklet trpt ttcp vrfy XNETMON from SNMP Research xnetmon from Wellfleet xnetperfmon from SNMP Research VMS --- arp ENTM NOCTools2 Working Group [Page 26] RFC 1470 FYI: Network Management Tool Catalog June 1993 fping net_monitor netstat NPRV ping SNMP Libraries and Utilities from SNMP Research tcpdump traceroute ttcp xnetperfmon from SNMP Research Free ---- arp Beholder CMIP Library CMU SNMP Distribution DiG dnsstats doc ENTM fping getethers hammer & anvil hopcheck host Interactive Network Map Internet Rover iozone lamers net_monitor netmon from Mitre netstat netwatch nfswatch nhfsstone NNStat NOCOL NPRV OSITRACE PING ping from UCB query SNMP Development Kit tcpdump tcplogger traceroute Tricklet NOCTools2 Working Group [Page 27] RFC 1470 FYI: Network Management Tool Catalog June 1993 trpt ttcp vrfy Library ------- CMIP Library CMU SNMP Dual Manager NetMetrix Protocol Analyzer NetMetrix Traffic Generator proxyd from SNMP Research SAS/CPE Sourcelib --------- Beholder CMIP Library CMU SNMP EMANATE HyperMIB Interactive Network Map Internet Rover LANWatch MIB Manager from Empire Technologies net_monitor NETMON for Windows NOCOL proxyd from SNMP Research SNMP Development Kit SNMP Libraries and Utilities from Empire Technologies SNMP Libraries and Utilities from SNMP Research SNMP Packaged Agent System from SNMP Research snmpd from SNMP Research SpiderMonitor Tricklet XNETMON from SNMP Research xnetperfmon from SNMP Research Tool Descriptions This section is an updated collection of brief descriptions of tools for managing TCP/IP internets. These entries are in alphabetical order, by tool name. The entries all follow a standard format. Immediately after the NAME of a tool are its associated KEYWORDS. Keywords are terse descriptions of the purposes or attributes of a tool. A more NOCTools2 Working Group [Page 28] RFC 1470 FYI: Network Management Tool Catalog June 1993 detailed description of a tool's purpose and characteristics is given in the ABSTRACT section. The MECHANISM section describes how a tool works. In CAVEATS, warnings about tool use are given. In BUGS, known bugs or bug-report procedures are given. LIMITATIONS describes the boundaries of a tool's capabilities. HARDWARE REQUIRED and SOFTWARE REQUIRED relate the operational environment a tool needs. Finally, in AVAILABILITY, pointers to vendors, online repositories, or other sources for a tool are given. Where tool names conflict, the vendor name is used as well. For example, MITRE, and SNMP Research each submitted an updated description of a tool called, "NETMON". These tools were independently developed, are functionally different, and run in different environments. MITRE's tool is listed as "NETMON_MITRE," and the tool from SNMP Research as "NETMON_WINDOWS_SNMP_RESEARCH". NOCTools2 Working Group [Page 29] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog ARP NAME arp KEYWORDS routing; ethernet, IP;; UNIX, VMS; free. ABSTRACT Arp displays and can modify the internet-to-ethernet address translations tables used by ARP, the address resolution protocol. MECHANISM The arp program accesses operating system memory to read the ARP data structures. CAVEATS None. BUGS None known. LIMITATIONS Only the super user can modify ARP entries. HARDWARE REQUIRED No restrictions. SOFTWARE REQUIRED BSD UNIX or related OS, or VMS. AVAILABILITY AND CONTACT POINT FOR INFORMATION ABOUT THIS TOOL Available via anonymous FTP from uunet.uu.net, in directory bsd-sources/src/etc. Available with 4.xBSD UNIX and related operating systems. For VMS, available as part of TGV MultiNet IP software package, as well as Wollongong's WIN/TCP and Process Software Corporation's TCPware for VMS. CONTACT POINT FOR CHANGES TO THIS CATALOG ENTRY This entry maintained by the NOCtools editors. Send email to noctools-request@merit.edu. NOCTools2 Working Group [Page 30] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog AVATAR-SNMP-TOOLKIT NAME SNMP Application Development Toolkit KEYWORDS manager;;SNMP;;sourcelib. ABSTRACT snmpapi is an api toolkit for developing SNMP applications and agents. The toolkit is simple and very fast that can be used for any type of application. It is very well suited for embedded systems such as bridges or routers. An example MIB II agent for Sun Sparcstations is provided. snmpapi is distributed in source form only. MECHANISM snmpapi is a library of C functions. CAVEATS None. BUGS None known. LIMITATIONS None. HARDWARE REQUIRED No restrictions. AVAILABILITY Available now. For more information, send e-mail to info@avatar.com. NOCTools2 Working Group [Page 31] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog AVATAR-SUNSNMPD NAME sunsnmpd KEYWORDS manager;;snmp;sun;. ABSTRACT sunsnmpd is a fully supported SNMP agent with MIB II support for Sun Sparscations running SunOS 4.1 or higher. sunsnmpd supports both SNMP GET and SET operations. MECHANISM sundnmpd is a daemon process which starts up at boot time from the rc.local file. It uses /dev/kmem to access kernel structures. CAVEATS None. BUGS None known. LIMITATIONS Must be started by a super user. HARDWARE REQUIRED Sun Sparcstations. AVAILABILITY Available now. Site licensing only. For more information, send e-mail to info@avatar.com. NOCTools2 Working Group [Page 32] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog ChameLAN-100 NAME ChameLAN 100 KEYWORDS analyzer, benchmark, debugger, generator, map, reference, status, traffic; bridge, DECnet, ethernet, FDDI, IP, OSI, NFS, ring; eavesdrop, SNMP, X; standalone, UNIX. ABSTRACT Tekelec's ChameLAN 100 is a portable diagnostic system for monitoring and simulation of FDDI, Ethernet and Token Ring networks -- simultaneously. Protocol analysis of multiple topologies, as well as mixed topoloies simultaneously, is a key feature of the product family. Tekelec's proprietary FDDI hardware guarantees complete real-time analysis of networks and network components at the full ring bandwidth of 125 Mbps. It passively connects to the network and captures 100 percent of the data, measures performance and isolates real-time problems. The simulation option offers full bandwidth load generation that allows you to create and simulate any network condition. It gives you the ability to inject errors and misformed frames. A set of confidence tests allow simple evaluation of new equipment. A ring map feature displays network topology and status of all nodes via the SMT process. Monitoring of FDDI, Ethernet and Token Ring allows the user to: view network status in real time; view network, node, or node pair statistics; capture frames; control capture using trigger and filter capabilities; view real-time statistics; view captured frames in decoded format; and view the last frame transmitted by each station. The following Real-Time Network Statistics of FDDI, Ethernet and Token Ring networks is displayed: frame rate, runts, byte rate, jabbers, CRC/align errors, and collisions. Product developers can use the ChameLAN 100 to observe NOCTools2 Working Group [Page 33] RFC 1470 FYI: Network Management Tool Catalog June 1993 and control various events to help debug their FDDI, Ethernet and Token Ring products. End users can perform real-time monitoring to test and diagnose problems that may occur when developing, installing or managing FDDI, Ethernet and Token Ring networks and network products. End users can use the ChameLAN 100 to aid in the installation and maintenance of Ethernet and Token Ring networks. To isolate specific network trouble spots the ChameLAN 100 uses filtering and triggering techniques for data capture. Higher level protocol decode includes TCP/IP, OSI and DECnet protocol suites. Protocol decode of IPX, SNMP, XTP, and AppleTalk are also supported. Development of additional protocol decodes is also under development. The ChameLAN 100 family also offers a Protocol Management Development System (PMDS) that enables users to develop custom protocol decode suites. The FDDI, Ethernet and Token Ring hardware interfaces feature independent processing power. Real-time data is monitored unobtrusively at full bandwidth without affecting network activity. Real-time data may also be saved to a 120MB or optional 200MB hard disk drive for later analysis. FDDI data is captured at 125 megabits per second (Mbps), Ethernet at 10 Mbps and Token Ring at 4 or 16 Mbps. MECHANISM This portable, standalone unit incorporates the power of UNIX, X-Windows and Motif. Its UNIX-based programming interface facilitates development of customized monitoring and simulation applications. The ChameLAN 100 may connect to the network at any location using standard equipment. Standard graphical Motif/X-Windows and TCP/IP allow remote control through Ethernet and 10Base T interfaces. Tekelec also offers a rackmounted model -- ChameLAN 100-X. Both models can be controlled via a Sun Workstation remotely. CAVEATS none. BUGS none known. NOCTools2 Working Group [Page 34] RFC 1470 FYI: Network Management Tool Catalog June 1993 LIMITATIONS none reported. HARDWARE REQUIRED None. The ChameLAN 100 is a self-contained unit, and includes its own interface cards. It installs into a network with standard interface connectors. SOFTWARE REQUIRED None. AVAILABILITY AND CONTACT POINT FOR INFORMATION ABOUT THIS TOOL The ChameLAN 100 product famil y is available commercially. For more information or a free demo, call or write: 1.800.tek.elec Tekelec 26580 West Agoura Road Calabasas, CA 91302 Phone: 818.880.5656 Fax: 818.880.6993 The ChameLAN 100 is listed on the GSA schedule. CONTACT POINT FOR CHANGES TO THIS CATALOG ENTRY Todd Koch Public Relations Specialist 818.880.7718 Internet: todd.koch@tekelec.com NOCTools2 Working Group [Page 35] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog CMU_SNMP NAME The CMU SNMP Distribution KEYWORDS manager, status; IP; NMS, SNMP; UNIX; free, sourcelib. ABSTRACT The CMU SNMP Distribution includes source code for an SNMP agent, several SNMP client applications, an ASN.1 library, and supporting documentation. The agent compiles into about 10 KB of 68000 code. The distribution includes a full agent that runs on a Kinetics FastPath2/3/4, and is built into the KIP appletalk/ethernet gateway. The machine independent portions of this agent also run on CMU's IBM PC/AT based router. The applications are designed to be useful in the real world. Information is collected and presented in a useful format and is suitable for everyday status monitoring. Input and output are interpreted symbolically. The tools can be used without referencing the RFCs. MECHANISM SNMP. CAVEATS None. BUGS None reported. Send bug reports to sw0l+snmp@andrew.cmu.edu. ("sw0l" is "ess double-you zero ell.") LIMITATIONS None reported. HARDWARE REQUIRED The KIP gateway agent runs on a Kinetics FastPath2/3/4. Otherwise, no restrictions. SOFTWARE REQUIRED The code was written with efficiency and portability in mind. The applications compile and run on the follow- NOCTools2 Working Group [Page 36] RFC 1470 FYI: Network Management Tool Catalog June 1993 ing systems: IBM PC/RT running ACIS Release 3, Sun3/50 running SUNOS 3.5, and the DEC microVax running Ultrix 2.2. They are expected to run on any system with a Berkeley socket interface. AVAILABILITY This distribution is copyrighted by CMU, but may be used and sold without permission. Consult the copy- right notices for further information. The distribu- tion is available by anonymous FTP from the host lancaster.andrew.cmu.edu (128.2.13.21) as the files pub/cmu-snmp.9.tar, and pub/kip-snmp.9.tar. The former includes the libraries and the applications, and the latter is the KIP SNMP agent. Please direct questions, comments, and bug reports to sw0l+snmp@andrew.cmu.edu. ("sw0l" is "ess double-you zero ell.") If you pick up this package, please send a note to the above address, so that you may be notified of future enhancements/changes and additions to the set of applications (several are planned). NOCTools2 Working Group [Page 37] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog COMPUTER-SECURITY-CHECKLIST NAME Computer Security Checklist KEYWORDS security; DOS. ABSTRACT This program consists of 858 computer security ques- tions divided up in thirteen sections. The program presents the questions to the user and records their responses. After answering the questions in one of the thirteen sections, the user can generate a report from the questions and the user's answers. The thirteen sections are: telecommunications security, physical access security, personnel security, systems develop- ment security, security awareness and training prac- tices, organizational and management security, data and program security, processing and operations security, ergonomics and error prevention, environmental secu- rity, and backup and recovery security. The questions are weighted as to their importance, and the report generator can sort the questions by weight. This way the most important issues can be tackled first. MECHANISM The questions are displayed on the screen and the user is prompted for a single keystroke reply. When the end of one of the thirteen sections is reached, the answers are written to a disk file. The question file and the answer file are merged to create the report file. CAVEATS None. BUGS None known. LIMITATIONS None reported. HARDWARE REQUIRED No restrictions. NOCTools2 Working Group [Page 38] RFC 1470 FYI: Network Management Tool Catalog June 1993 SOFTWARE REQUIRED DOS operating system. AVAILABILITY A commercial product available from: C.D., Ltd. P.O. Box 58363 Seattle, WA 98138 (206) 243-8700 NOCTools2 Working Group [Page 39] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog CMIP-LIBRARY NAME CMIP Library KEYWORDS manager; osi; cmis; unix; free, sourcelib. ABSTRACT The CMIP Library implements the functionality of the Common Management Information Service/Protocol as in the full international standards (ISO 9595, ISO 9596) published in 1990. It is designed to work with the ISODE package and can act as a building block for the construction of CMIP-based agent and manager applications. MECHANISM The CMIP library uses ISO ROS, ACSE and ASN.1 presentation, as implemented in ISODE, to provide its service. CAVEATS None. BUGS None known. LIMITATIONS None known. HARDWARE REQUIRED Has been tested on SUN 3 and SUN 4 architectures. SOFTWARE REQUIRED The ISODE protocol suite, BSD UNIX. AVAILABILITY The CMIP library and related management tools built upon it, known as OSIMIS (OSI Management Information Service), are publicly available from University College London, England via FTP and FTAM. To obtain information regarding a copy send email to osimis-request@cs.ucl.ac.uk or call +44 71 380 7366. NOCTools2 Working Group [Page 40] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog DECADDRS NAME decaddrs, decaroute, decnroute, xnsroutes, bridgetab KEYWORDS manager, map, routing; bridge, DECnet; NMS, SNMP; UNIX. ABSTRACT These commands display private MIB information from Wellfleet systems. They retrieve and format for display values of one or several MIB variables from the Wellfleet Communications private enterprise MIB, using the SNMP (RFC1098). In particular these tools are used to examine the non-IP modules (DECnet, XNS, and Bridg- ing) of a Wellfleet system. Decaddrs displays the DECnet configuration of a Wellfleet system acting as a DECnet router, showing the static parameters associated with each DECnet inter- face. Decaroute and decnroute display the DECnet inter-area and intra-area routing tables (that is area routes and node routes). Xnsroutes displays routes known to a Wellfleet system acting as an XNS router. Bridgetab displays the bridge forwarding table with the disposition of traffic arriving from or directed to each station known to the Wellfleet bridge module. All these commands take an IP address as the argument and can specify an SNMP community for the retrieval. One SNMP query is performed for each row of the table. Note that the Wellfleet system must be operating as an IP router for the SNMP to be accessible. MECHANISM Management information is exchanged by use of SNMP. CAVEATS None. BUGS None known. LIMITATIONS None reported. HARDWARE REQUIRED Distributed and supported for Sun 3 systems. NOCTools2 Working Group [Page 41] RFC 1470 FYI: Network Management Tool Catalog June 1993 SOFTWARE REQUIRED Distributed and supported for SunOS 3.5 and 4.x. AVAILABILITY Commercial product of: Wellfleet Communications, Inc. 12 DeAngelo Drive Bedford, MA 01730-2204 (617) 275-2400 NOCTools2 Working Group [Page 42] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog DIG NAME DiG KEYWORDS status; DNS; spoof; UNIX; free. ABSTRACT DiG (domain information groper), is a command line tool which queries DNS servers in either an interactive or a batch mode. It was developed to be more convenient/flexible than nslookup for gathering perfor- mance data and testing DNS servers. MECHANISM Dig is built on a slightly modified version of the bind resolver (release 4.8). CAVEATS none. BUGS None known. LIMITATIONS None reported. HARDWARE REQUIRED No restrictions. SOFTWARE REQUIRED BSD UNIX. AVAILABILITY DiG is available via anonymous FTP from venera.isi.edu in pub/dig.2.0.tar.Z. NOCTools2 Working Group [Page 43] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog EMANATE_SNMP_RESEARCH NAME EMANATE: Enhanced MANagement Agent Through Extensions from SNMP Research. KEYWORDS alarm, control, manager, reference, security, status; bridge, Ethernet, FDDI, IP, OSI, ring, star; NMS, SNMP; sourcelib. ABSTRACT The EMANATE system provides a run-time extensible SNMP agent that dynamically reconfigures an agent's MIB without having to recompile, relink, or restart the agent. An EMANATE capable SNMP agent can support zero, one, or many subagents and dynamically reconfigure to connect or disconnect those subagents' MIBs. The EMANATE system consists of several logically independent components and subsystems: o Master SNMP agent which contains an API to communicate with subagents. o Subagents which implement various MIBS. o Subagent Developer's Kit which contains tools to assist in the implementation of subagents. o EMANATE libraries which provide the API for the subagent. MECHANISM A concise API allows a standard means of communication between the master and subagents. System dependent mechanisms are employed for transfer of information between the master and subagents. CAVEATS None. BUGS None known. LIMITATIONS None reported. NOCTools2 Working Group [Page 44] RFC 1470 FYI: Network Management Tool Catalog June 1993 HARDWARE REQUIRED Multiple platforms including PC's, workstations, hosts, and servers are supported. Contact SNMP Research for more details. SOFTWARE REQUIRED C compiler. AVAILABILITY AND CONTACT POINT FOR INFORMATION ABOUT THIS TOOL This is a commercial product available under license from: SNMP Research 3001 Kimberlin Heights Road Knoxville, TN 37920-9716 Attn: John Southwood, Sales and Marketing (615) 573-1434 (Voice) (615) 573-9197 (FAX) CONTACT POINT FOR CHANGES TO THIS CATALOG ENTRY users@seymour1.cs.utk.edu NOCTools2 Working Group [Page 45] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog ETHERFIND_SUN NAME etherfind KEYWORDS traffic; ethernet, IP, NFS; eavesdrop; UNIX. ABSTRACT Etherfind examines the packets that traverse a network interface, and outputs a text file describing the traffic. In the file, a single line of text describes a single packet: it contains values such as protocol type, length, source, and destination. Etherfind can print out all packet traffic on the ethernet, or traffic for the local host. Further packet filtering can be done on the basis of protocol: IP, ARP, RARP, ICMP, UDP, ND, TCP, and filtering can also be done based on the source, destination addresses as well as TCP and UDP port numbers. MECHANISM In usual operations, and by default, etherfind puts the interface in promiscuous mode. In 4.3BSD UNIX and related OSs, it uses a Network Interface Tap (NIT) to obtain a copy of traffic on an ethernet interface. CAVEATS None. BUGS None known. LIMITATIONS Minimal protocol information is printed. Can only be run by the super user. The syntax is painful. HARDWARE REQUIRED Ethernet. SOFTWARE REQUIRED SunOS. AVAILABILITY Executable included in Sun OS "Networking Tools and Programs" software installation option. NOCTools2 Working Group [Page 46] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog ETHERNET-CODES NAME ethernet-codes KEYWORDS reference; ethernet, fddi; ; ; ; ABSTRACT Mike Patton of MIT LCS has compiled a very comprehensive list of the IEEE numbers used on Ethernet and FDDI (with some permutation). This file contains collected information on the various codes used on IEEE 802.3 and EtherNet. There are three "pages": type codes, vendor codes, and the uses of multicast (including broadcast) addresses. MECHANISM FTP the file and use it like a secret decoder ring. CAVEATS Since this information is from collected wisdom, there are certainly omissions. BUGS Mike welcomes any further additions. They can be sent to a special mailbox that he has set up: MAP=EtherNet-codes@LCS.MIT.Edu LIMITATIONS See caveats. HARDWARE REQUIRED No restrictions. SOFTWARE REQUIRED No restrictions. NOCTools2 Working Group [Page 47] RFC 1470 FYI: Network Management Tool Catalog June 1993 AVAILABILITY AND CONTACT POINT FOR INFORMATION ABOUT THIS TOOL The file is stored as flat, non-compressed ASCII text. It can be FTP'ed from: ftp.lcs.mit.edu Retreive the file: /pub/map/EtherNet-codes To submit additions or obtain further assistance, send email to: MAP=EtherNet-codes@LCS.MIT.Edu CONTACT POINT FOR CHANGES TO THIS CATALOG ENTRY This entry maintained by the NOCtools editors. Send email to noctools-request@merit.edu NOCTools2 Working Group [Page 48] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog GENERIC-MANAGED-SYSTEM NAME Generic Managed System KEYWORDS manager; osi; cmis; unix; free, sourcelib ABSTRACT The Generic Managed System (GMS) implements the functions that would be common to any OSI managed system. These include the parseing of CMIS requests, selection of managed objects according to the scoping and filtering rules, handling of notifications and event forwarding discriminators etc. The intention is that the implementors should use the GMS as a basis for their own managed object implementations. A support environment is provided to assist with this. MECHANISM The GMS uses the UCL CMIP library plus a library of C++ objects representing common managed objects and attribute types. CAVEATS The system is still experimental, is subject to change and is not yet well documented. BUGS See above. LIMITATIONS None known. HARDWARE REQUIRED Has been tested on SUN 3 and SUN 4 architectures. SOFTWARE REQUIRED The ISODE protocol suite, BSD UNIX, UCL CMIP Library, GNU C++ (g++). AVAILABILITY The CMIP library and related management tools built upon it, known as OSIMIS (OSI Management Information Service), are publicly available from University College London, England via FTP and FTAM. To obtain information regarding a copy send email to osimis-request@cs.ucl.ac.uk or call +44 71 380 7366. NOCTools2 Working Group [Page 49] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog GETETHERS NAME getethers KEYWORDS Traffic; Ethernet; Ping; UNIX; Free ABSTRACT Getethers runs through all addresses on an ethernet segment (a.b.c.1 to a.b.c.254) and pings each address, and then determines the ethernet address for that host. It produces a list, in either plain ASCII, the file format for the Excelan Lanalyzer, or the file format for the Network General Sniffer, of hostname/ethernet address pairs for all hosts on the local nework. The plain ASCII list optionally includes the vendor name of the ethernet card in each system, to aid in the determination of the identity of unknown systems. MECHANISM Getethers uses a raw IP socket to generate ICMP echo requests and receive ICMP echo replies, and then examines the kernel ARP table to determine the ethernet address of each responding system. CAVEATS Assumes that the ethernet it is looking at is either a Class C IP network, or part of a Class B IP network that is subnetted with a netmask of 255.255.255.0. (This is easy to change, but it's compiled in.) BUGS None known. LIMITATIONS None. HARDWARE REQUIRED Has been tested on Sun-3 and Sun-4 (SPARC) systems under SunOS 4.1.x, DEC VAXes under 4.3BSD. SOFTWARE REQUIRED Runs under SunOS 4.x and 4.3BSD; should be easy to port to any other Berkeley-like system. Requires raw sockets and the ioctl calls to get at the ARP table. NOCTools2 Working Group [Page 50] RFC 1470 FYI: Network Management Tool Catalog June 1993 AVAILABILITY AND CONTACT POINT FOR INFORMATION ABOUT THIS TOOL Public domain, and freely distributable. Available via anonymous FTP from harbor.ecn.purdue.edu; also has been posted to comp.sources.unix. The current version is Version 1.4 from May 1992. Contact point: Dave Curry Purdue University Engineering Computer Network 1285 Electrical Engineering Bldg. West Lafayette, IN 47907-1285 davy@ecn.purdue.edu CONTACT POINT FOR CHANGES TO THIS CATALOG ENTRY Dave Curry (see address above). NOCTools2 Working Group [Page 51] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog GETONE_WELLFLEET NAME getone, getmany, getroute, getarp, getaddr, getif, getid. KEYWORDS manager, routing, status; IP; NMS, SNMP; UNIX. ABSTRACT These commands retrieve and format for display values of one or several MIB variables (RFC1066) using the SNMP (RFC1098). Getone and getmany retrieve arbitrary MIB variables; getroute, getarp, getaddr, and getif retrieve and display tabular information (routing tables, ARP table, interface configuration, etc.), and getid retrieves and displays system name, identifica- tion and boot time. Getone <target> <mibvariable> retrieves and displays the value of the designated MIB variable from the specified target system. The SNMP community name to be used for the retrieval can also be specified. Getmany works similarly for groups of MIB variables rather than individual values. The name of each variable, its value and its data type is displayed. Getroute returns information from the ipRoutingTable MIB structure, displaying the retrieved information in an accessible format. Getarp behaves similarly for the address translation table; getaddr for the ipAddressTable; and getif displays information from the interfaces table, supplemented with information from the ipAddressTable. Getid displays the system name, identification, ipFor- warding state, and the boot time and date. All take a system name or IP address as an argument and can specify an SNMP community for the retrieval. One SNMP query is performed for each row of the table. MECHANISM Queries SNMP agent(s). CAVEATS None. BUGS None known. NOCTools2 Working Group [Page 52] RFC 1470 FYI: Network Management Tool Catalog June 1993 LIMITATIONS None reported. HARDWARE REQUIRED Distributed and supported for Sun 3 systems. SOFTWARE REQUIRED Distributed and supported for SunOS 3.5 and 4.x. AVAILABILITY Commercial product of: Wellfleet Communications, Inc. 12 DeAngelo Drive Bedford, MA 01730-2204 (617) 275-2400 NOCTools2 Working Group [Page 53] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog HAMMER_ANVIL NAME hammer & anvil KEYWORDS benchmark, generator; IP; DOS; free. ABSTRACT Hammer and Anvil are the benchmarking programs for IP routers. Using these tools, gateways have been tested for per-packet delay, router-generated traffic over- head, maximum sustained throughput, etc. MECHANISM Tests are performed on a gateway in an isolated testbed. Hammer generates packets at controlled rates. It can set the length and interpacket interval of a packet stream. Anvil counts packet arrivals. CAVEATS Hammer should not be run on a live network. BUGS None reported. LIMITATIONS Early versions of hammer could not produce inter-packet intervals shorter than 55 usec. HARDWARE REQUIRED Hammer runs on a PC/AT or compatible, and anvil requires a PC or clone. Both use a Micom Interlan NI5210 for LAN interface. SOFTWARE REQUIRED MS-DOS. AVAILABILITY Hammer and anvil are copyrighted, though free. Copies are available from pub/eutil on husc6.harvard.edu. NOCTools2 Working Group [Page 54] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog HOPCHECK NAME hopcheck KEYWORDS routing; IP; ping; DOS; free. ABSTRACT Hopcheck is a tool that lists the gateways traversed by packets sent from the hopcheck-resident PC to a desti- nation. Hopcheck uses the same mechanism as traceroute but is for use on IBM PC compatibles that have ethernet connections. Hopcheck is part of a larger TCP/IP pack- age that is known as ka9q that is for use with packet radio. Ka9q can coexist on a PC with other TCP/IP packages such as FTP Inc's PC/TCP, but must be used independently of other packages. Ka9q was written by Phil Karn. Hopcheck was added by Katie Stevens, dkstevens@ucdavis.edu. Unlike traceroute, which requires a UNIX kernel mod, hopcheck will run on the standard, unmodified ka9q release. MECHANISM See the description in traceroute. CAVEATS See the description in traceroute. BUGS None known. HARDWARE REQUIRED IBM PC compatible with ethernet network interface card; ethernet card supported through FTP spec packet driver. SOFTWARE REQUIRED DOS. AVAILABILITY Free for radio amateurs and educational institutions; others should contact Phil Karn, karn@ka9q.bellcore.com. Available via anonymous FTP at ucdavis.edu, in the directory "dist/nethop". NOCTools2 Working Group [Page 55] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog INTERNET_ROVER NAME Internet Rover KEYWORDS status; IP, SMTP; curses, ping, spoof; UNIX; free, sourcelib. ABSTRACT Internet Rover is a prototype network monitor that uses multiple protocol "modules" to test network functional- ity. This package consists of two primary pieces of code: the data collector and the problem display. There is one data collector that performs a series of network tests, and maintains a list of problems with the network. There can be many display processes all displaying the current list of problems which is useful in a multi-operator NOC. The display task uses curses, allowing many terminal types to display the problem file either locally or from a remote site. Full source is provided. The data collector is easily configured and extensible. Contri- butions such as additional protocol modules, and shell script extensions are welcome. MECHANISM A configuration file contains a list of nodes, addresses, NodeUp? protocol test (ping in most cases), and a list of further tests to be performed if the node is in fact up. Modules are included to test TELNET, FTP, and SMTP. If the configuration contains a test that isn't recognized, a generic test is assumed, and a filename is checked for existence. This way users can create scripts that create a file if there is a prob- lem, and the data collector simply checks the existence of that file to determine if there is problem. CAVEATS None. BUGS None known. NOCTools2 Working Group [Page 56] RFC 1470 FYI: Network Management Tool Catalog June 1993 LIMITATIONS This tool does not yet have the capability to perform actions based on the result of the test. Rather, it is intended for a multi-operator environment, and simply displays a list of what is wrong with the net. HARDWARE REQUIRED This software is known to run on Suns and IBM RTs. SOFTWARE REQUIRED Curses, 4.xBSD UNIX socket programming libraries, BSD ping. AVAILABILITY Full source available via anonymous FTP from merit.edu (35.1.1.42) in the ~ftp/pub/inetrover directory. Source and executables are public domain and can be freely distributed for non-commercial use. This pack- age is unsupported, but bug reports and fixes may be sent to: wbn@merit.edu. NOCTools2 Working Group [Page 57] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog IOZONE NAME iozone KEYWORDS benchmark; nfs;; dos,hp,unix,vmx; free. ABSTRACT Software to assess the sequential file I/O capability of a system. May be useful as reference to compare against results obtained when files are accessed via NFS, Andrew, etc. MECHANISM This test writes a X MEGABYTE sequential file in Y byte chunks, then rewinds it and reads it back. [The size of the file should be big enough to factor out the effect of any disk cache.]. Finally, IOZONE deletes the temporary file. Options allow one to vary X and Y. In addition, 'auto test' runs IOZONE repeatedly using record sizes from 512 to 8192 bytes (adjustable), and file sizes from 1 to 16 megabytes (adjustable). It creates a table of results. CAVEATS The file is written (filling any cache buffers), and then read. If the cache is >= X MB, then most if not all the reads will be satisfied from the cache. However, if it is less than or equal to .5X MB, then NONE of the reads will be satisfied from the cache. This is becase after the file is written, a .5X MB cache will contain the upper .5 MB of the test file, but we will start reading from the beginning of the file (data which is no longer in the cache). In order for this to be a fair test, the length of the test file must be AT LEAST 2X the amount of disk cache memory for your system. If not, you are really testing the speed at which your CPU can read blocks out of the cache (not a fair test). BUGS none known at this time. NOCTools2 Working Group [Page 58] RFC 1470 FYI: Network Management Tool Catalog June 1993 LIMITATIONS IOZONE does not normally test the raw I/O speed of your disk or system-em. It tests the speed of sequential I/O to actual files. Therefore, this measurement factors in the efficiency of you machines file system, operating system, C compiler, and C runtime library. It produces a measurement which is the number of bytes per second that your system can read or write to a file. HARDWARE REQUIRED This program has been ported and tested on the following computer operating systems: Vendor Operating System Notes on compiling IOzone ----------------------------------------------------------------------- Apollo Domain/OS no cc switches -- BSD domain AT&T UNIX System V R4 AT&T 6386WGS AT&T UNIX 5.3.2 define SYSTYPE_SYSV Generic AT&T UNIX System V R3 may need cc -DSVR3 Convergent Unisys/AT&T SVR3 cc -DCONVERGENT -o iozone iozone.c Digital Equipment ULTRIX V4.1 Digital Equipment VAX/VMS V5.4 see below ** Digital Equipment VAX/VMS (POSIX) Hewlett-Packard HP-UX 7.05 IBM AIX Ver. 3 rel. 1 Interactive UNIX System V R3 Microsoft MS-DOS 3.3 tested Borland, Microsoft C MIPS RISCos 4.52 NeXt NeXt OS 2.x OSF OSF/1 Portable! POSIX 1003.1-1988 may need to define _POSIX_SOURCE QNX QNX 4.0 SCO UNIX System V/386 3.2.2 SCO XENIX 2.3 SCO XENIX 3.2 Silicon Graphics UNIX cc -DSGI -o iozone iozone.c Sony Microsystems UNIX same as MIPS Sun Microsystems SUNOS 4.1.1 Tandem Computers GUARDIAN 90 1. call the source file IOZONEC 2. C/IN IOZONEC/IOZONE;RUNNABLE 3. RUN IOZONE Tandem Computers Non-Stop UX ** for VMS, define iozone as a foreign command via this DCL command: $IOZONE :== $SYS$DISK:[]IOZONE.EXE NOCTools2 Working Group [Page 59] RFC 1470 FYI: Network Management Tool Catalog June 1993 this lets you pass the command line arguments to IOZONE SOFTWARE REQUIRED OS as shown in the hardware listing above. AVAILABILITY AND CONTACT POINT FOR INFORMATION ABOUT THIS TOOL Author: Bill Norcott 1060 Hyde Avenue San Jose, CA 95129 norcott_bill@tandem.com Availability: This tool has been posted to comp.sources.misc. It is available from the usual archive sites. Program can be located using ARCHIE or other servers. CONTACT POINT FOR CHANGES TO THIS CATALOG ENTRY This entry is maintained by the noctools editors. Send email to noctools-request@merit.edu. NOCTools2 Working Group [Page 60] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog LADDIS NAME LADDIS KEYWORDS benchmark, generator; NFS; spoof; unix; free. ABSTRACT "LADDIS: A Multi-Vendor and Vendor-Neutral SPEC NFS Benchmark", Bruce Nelson, LADDIS Group & Auspex Systems. Over the past 24 months, engineers from Legato, Auspex, Data General, DEC, Interphase, and Sun (LADDIS) met regularly to create the LADDIS NFS benchmark: an unbiased, standard, vendor-independent, scalable NFS performance test. The purpose of the LADDIS benchmark is to give users a credible and undisputed test of NFS performance, and to give vendors a publishable standard performance measure that customers can use for load planning, system configuration, and equipment buying decisions. Toward this end, the LADDIS benchmark is being adopted by SPEC (the System Performance Evaluation Cooperative, creators of SPECmarks) as the first member of SPEC's System-level File Server (SFS) benchmark suite." "In particular, we have had unexpected interest from some router vendors in using LADDIS to both rate and stress-test IP routers. This is because LADDIS can send back-to-back full-size packet trains, and because it can generate a 90%-Ethernet util on simulated "real" NFS workloads, just like routers encounter in the real world. But LADDIS is for local Ethernet or FDDI nets only, not WAN." MECHANISM Generates NFS requests and measures responsiveness of the server. NOCTools2 Working Group [Page 61] RFC 1470 FYI: Network Management Tool Catalog June 1993 CAVEATS "LADDIS is not released yet by SPEC, although a free beta version, quite stable, is available now as PRE-LADDIS. So you might want to put PRE-LADDIS in your listing, noting that full LADDIS availability from SPEC is expected by the end of 1992." BUGS The licensee is requested to direct beta test comments via electronicmail to: "spec-preladdis-comments@riscee.pko.dec.com". This alias will forward all comments to the SPECSFS mailing list (which includes the LADDIS Group). LIMITATIONS LADDIS is for local Ethernet or FDDI nets only, not WAN. HARDWAE REQUIRED A host with LAN connectivity. Presumably, a host with enough horsepower to generate an adequate work load. SOFTWARE REQUIRED LADDIS is a sophisticated Unix-based NFS traffic generator program. AVAILABILITY AND CONTACT POINT FOR INFORMATION ABOUT THIS TOOL Date: Mon, 10 Feb 92 13:12:20 PST From: bnelson (Bruce Nelson) Dear Person: The SPEC PRE-LADDIS beta test process became operational on Monday, February 3, 1992. This email describes the process as announced during the LADDIS Group's presentation at UniForum '92 and also at Interop '91. The content of the beta test license and the license request process are consistent with the proposals approved by the SPEC Steering Committee at the January 1992 meeting in Milpitas, California. The SPEC PRE-LADDIS beta test will consist of one beta test version of PRE-LADDIS distributed ONLY by electronic mail. The SPEC PRE-LADDIS Beta test software is licensed by SPEC, not by the LADDIS Group. NOCTools2 Working Group [Page 62] RFC 1470 FYI: Network Management Tool Catalog June 1993 To obtain the PRE-LADDIS Beta test software, an individual must: 1. Request the SPEC PRE-LADDIS beta test License by electronic mail to "spec-preladdis-beta-test@riscee.pko.dec.com" with a subject line of "Request SPEC PRE-LADDIS Beta Test License". 2. Print a hardcopy of the license and sign. 3. Attach a cover letter written on the individual's company letterhead requesting the PRE-LADDIS Beta Test Kit. 4. U.S. Mail the signed license and cover letter to: SPEC PRE-LADDIS Beta Test c/o NCGA, 2722 Merrilee Drive, Suite 200 Fairfax, VA 22031 After completing these steps, the SPEC PRE-LADDIS beta test kit will be emailed to the requestor from riscee.pko.dec.com. The licensee is requested to direct beta test comments via electronic mail to "spec-preladdis-comments@riscee.pko.dec.com". This alias will forward all comments to the SPECSFS mailing list (which includes the LADDIS Group). Note that PRE-LADDIS is ONLY available through electronic mail and ONLY through the process listed above in steps 1-4. If you do not have internet email available to you (which is unlikely if you are receiving THIS email), you must arrange delivery of PRE-LADDIS through some email-capable part of your organization, not through LADDIS members like Auspex, DEC, Sun, etc. CONTACT POINT FOR CHANGES TO THIS CATALOG ENTRY This entry is maintained by the NOCtools editors. Send E-mail to noctools-request@merit.edu. NOCTools2 Working Group [Page 63] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog LAN_PATROL NAME LAN Patrol KEYWORDS security, traffic; ethernet, star; eavesdrop; DOS. ABSTRACT LAN Patrol is a full-featured network analyzer that provides essential information for effective fault and performance management. It allows network managers to easily monitor user activity, find traffic overloads, plan for growth, test cable, uncover intruders, balance network services, and so on. LAN Patrol uses state of the art data collection techniques to monitor all activity on a network, giving an accurate picture of how it is performing. LAN Patrol's reports can be saved as ASCII files to disk, and imported into spreadsheet or database pro- grams for further analysis. MECHANISM The LAN Patrol interface driver programs a standard interface card to capture all traffic on a network seg- ment. The driver operates from the background of a standard PC, maintaining statistics for each station on the network. The information can be viewed on the PC's screen, or as a user-defined report output either to file or printer. CAVEATS None. Normal operation is completely passive, making LAN Patrol transparent to the network. BUGS None known. LIMITATIONS LAN Patrol can monitor up to 10,000 packets/sec on an AT class PC, and is limited to monitoring a maximum of 1024 stations for intervals of up to 30 days. Because LAN Patrol operates at the physical level, it will only see traffic for the segment on which it is installed; it cannot see traffic across bridges. NOCTools2 Working Group [Page 64] RFC 1470 FYI: Network Management Tool Catalog June 1993 HARDWARE REQUIRED Computer: IBM PC/XT/AT, PS/2 Model 30, or compatible. Requires 512K memory and a hard drive or double-sided disk drive. Display: Color or monochrome text. Color display allows color-coding of traffic information. Ethernet, StarLAN, LattisNet, or StarLAN 10 network interface card. SOFTWARE REQUIRED PC DOS, MS-DOS version 3.1 or greater. AVAILABILITY LAN Patrol many be purchased through network dealers, or directly from: Legend Software, Inc. Phone: (201) 227-8771 FAX: (201) 906-1151 NOCTools2 Working Group [Page 65] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog LANVista NAME LANVista KEYWORDS analyzer, benchmark, debugger, generator, manager, traffic; DECnet, Ethernet, IP, OSI, Ring; Eavesdrop, Proprietary; DOS, Standalone. ABSTRACT CXR/Digilog's LANVista family of protocol and statistical analyzers provide the tools to troubleshoot an Ethernet and Token Ring 4/16Mbps network. LANVista lets you capture frames to RAM and or disk, generate traffic for stress testing, test your network cable for fault isolation, and decode all 7 layers of many popular protocol stacks. LANVista's 100 family offers exceptional price/performance and a wide range of options. Combined with an integrated upgrade path to the fully distributed LANVista 200 system, the 100 line provides a reasonably priced entry into LAN management and protocol analysis. All LANVista models are fully operable under Microsoft Windows. Under Windows, LANVista can be operated in the background, gathering data and alarms as other tasks are completed. Displayed data may easily be cut from LANVista and pasted into other Windows applications such as Excel, Lotus 1-2-3, Harvard Graphics, etc. The versatile LANVista family can also be remotely controlled through the use of PC Anywhere, Commute, Carbon Copy, or other PC remote control packages. This feature allows the use of "co-pilot" mode which enables an operator at the central site to guide and train a remote operator through network management or analysis tasks. All LANVista models provide features vital to effective network management and troubleshooting. Basic capabilities include: Network database, statistics based on the entire network and on a node basis, Token Ring functional address statistics, Bridged traffic statistics, Protocol statistics, logging of statistics to a printer or file of user definable alarms, Hardware Pre-Capture filtering, Post capture filtering, Playback of captured data, Traffic simulation and On-line context NOCTools2 Working Group [Page 66] RFC 1470 FYI: Network Management Tool Catalog June 1993 sensitive Help. Protocol Interpreters used for decoding network traffic supported by LANVista include: TCP/IP, DECnet, Banyan Vines, XNS/MS-Net, AppleTalk, IBM Token Ring, Novell, 3Com 3+ Open, SNMP and OSI. MECHANISM LANVista is available in three forms. A kit version which consists of a plug-in PC card and Master software, a self contained unit that packages the kit version in a portable PC, and a Distributed system. The LANVista distributed system allows slave units placed anywhere in the world to be controlled from a single central location for centralized management of an enterprise network. LANVista's PC cards provides a physical interface to the LAN and frame preprocessing power. The Master software controls the PC card, and the display and processing of information gathered from the network. CAVEATS Optimal performance of LANVista's master software is achieved with DOS 5.0 by utilizing RAMDRIVE.SYS, SMARTDRV.SYS and High memory. BUGS None Known. LIMITATIONS None Known. HARDWARE REQUIRED IBM PC AT, 386, 486 or compatible. SOFTWARE REQUIRED DOS AVAILABILITY AND CONTACT POINT FOR INFORMATION ABOUT THIS TOOL LANVista is available worldwide. For information on a local sales representative contact: CXR/DIGILOG 900 Business Center Drive Horsham, PA 19044 Phone 1-800-DIGILOG FAX: 215-956-0108 GSA schedule pricing is honored. NOCTools2 Working Group [Page 67] RFC 1470 FYI: Network Management Tool Catalog June 1993 CONTACT POINT FOR CHANGES TO THIS CATALOG ENTRY CXR/DIGILOG Help Desk 1-800-DIGILOG Send email to: lanvista@digilog.uucp NOCTools2 Working Group [Page 68] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog LANPROBE NAME LanProbe -- the HP 4990S LanProbe Distributed Analysis System. KEYWORDS alarm, manager, map, status, traffic; ethernet; eaves- drop, NMS; proprietary. ABSTRACT The LanProbe distributed monitoring system performs remote and local monitoring of ethernet LANs in a pro- tocol and vendor independent manner. LanProbe discovers each active node on a segment and displays it on a map with its adapter card vendor name, ethernet address, and IP address. Additional informa- tion about the nodes, such as equipment type and physi- cal location can be entered in to the data base by the user. When the NodeLocator option is used, data on the actual location of nodes is automatically entered and the map becomes an accurate representation of the physical lay- out of the segment. Thereafter when a new node is installed and becomes active, or when a node is moved or becomes inactive, the change is detected and shown on the map in real time. The system also provides the network manager with precise cable fault information displayed on the map. Traffic statistics are gathered and displayed and can be exported in (comma delimited) CSV format for further analysis. Alerts can be set on user defined thres- holds. Trace provides a remote protocol analyzer capability with decodes for common protocols. Significant events (like power failure, cable breaks, new node on network, broadcast IP source address seen, etc.) are tracked in a log that is uploaded to Pro- beView periodically. ProbeView generates reports that can be manipulated by MSDOS based word processors, spreadsheets, and DBMS. NOCTools2 Working Group [Page 69] RFC 1470 FYI: Network Management Tool Catalog June 1993 MECHANISM The system consists of one or more LanProbe segment monitors and ProbeView software running under Microsoft Windows. The LanProbe segment monitor attaches to the end of an ethernet segment and monitors all traffic. Attachment can be direct to a thin or thick coax cable, or via an external transceiver to fiber optic or twist- ed pair cabling. Network data relating to the segment is transferred to a workstation running ProbeView via RS-232, ethernet, or a modem connection. ProbeView software, which runs on a PC/AT class works- tation, presents network information in graphical displays. The HP4992A NodeLocator option attaches to the opposite end of the cable from the HP4991A LanProbe segment mon- itor. It automatically locates the position of nodes on the ethernet networks using coaxial cabling schemes. CAVEATS None. BUGS None known. LIMITATIONS None reported. HARDWARE REQUIRED HP 4991A LanProbe segment monitor HP 4992A NodeLocator (for optional capabilities) 80386 based PC capable of running MS-Windows SOFTWARE REQUIRED HP 4990A ProbeView MSDOS 3.0 or higher and Microsoft Windows/286 2.1. AVAILABILITY A commercial product available from: Hewlett-Packard Company P.O. Box 10301, Palo Alto, CA 94303-0890 NOCTools2 Working Group [Page 70] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog LANWATCH NAME LANWatch KEYWORDS alarm, analyzer, traffic; CHAOS, DECnet, DNS, ethernet, IP, OSI, ring, SMTP, star; eavesdrop; DOS; library, sourcelib. ABSTRACT LANWatch 2.0 is an inexpensive, powerful and flexible network analyzer that runs under DOS on personal com- puters and requires no hardware modifications to either the host or the network. LANWatch is an invaluable tool for installing, troubleshooting, and monitoring local area networks, and for developing and debugging new protocols. Network managers using LANWatch can inspect network traffic patterns and packet errors to isolate performance problems and bottlenecks. Protocol developers can use LANWatch to inspect and verify proper protocol handling. Since LANWatch is a software-only package which installs easily in existing PCs, network technicians and field service engineers can carry LANWatch in their briefcase for convenient network analysis at remote sites. LANWatch has two operating modes: Display and Examine. In Display Mode, LANWatch traces network traffic by displaying captured packets in real time. Examine Mode allows you to scroll back through stored packets to inspect them in detail. To select a subset of packets for display, storage or retrieval, there is an exten- sive set of built-in filters. Using filters, LANWatch collects only packets of interest, saving the user from having to sort through all network traffic to isolate specific packets. The built-in filters include alarm, trigger, capture, load, save and search. They can be controlled separately to match on source or destination address, protocol, or packet contents at the hardware and transport layers. LANWatch also includes suffi- cient source code so users can modify the existing filters and parsers or add new ones. The LANWatch distribution includes executables and source for several post-processors: a TCP protocol analyzer, a node-by-node traffic analyzer and a dump file listing tool. NOCTools2 Working Group [Page 71] RFC 1470 FYI: Network Management Tool Catalog June 1993 MECHANISM Uses many common PC network interfaces by placing them in promiscuous mode and capturing traffic. CAVEATS Most PC network interfaces will not capture 100% of the traffic on a fully-loaded network (primarily missing back-to-back packets). BUGS None known. LIMITATIONS LANWatch can't analyze what it doesn't see (see Caveats). HARDWARE REQUIRED LANWatch requires a PC or PS/2 with a supported network interface card. SOFTWARE REQUIRED LANWatch runs in DOS. Modification of the supplied source code or creation of additional filters and parsers requires Microsoft C 5.1 AVAILABILITY LANWatch is commercially available from FTP Software, Incorporated, 26 Princess Street, Wakefield, MA, 01880 (617 246-0900). NOCTools2 Working Group [Page 72] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog LLL_ENTM NAME ENTM -- Ethernet Traffic Monitor KEYWORDS traffic; ethernet, IP; eavesdrop; VMS; free. ABSTRACT ENTM is a screen-oriented utility that runs under VAX/VMS. It monitors local ethernet traffic and displays either a real time or cumulative, histogram showing a percent breakdown of traffic by ethernet pro- tocol type. The information in the display can be reported based on packet count or byte count. The per- cent of broadcast, multicast and approximate lost pack- ets is reported as well. The screen display is updated every three seconds. Additionally, a real time, slid- ing history window may be displayed showing ethernet traffic patterns for the last five minutes. ENTM can also report IP traffic statistics by packet count or byte count. The IP histograms reflect infor- mation collected at the TCP and UDP port level, includ- ing ICMP type/code combinations. Both the ethernet and IP histograms may be sorted by ASCII protocol/port name or by percent-value. All screen displays can be saved in a file for printing later. MECHANISM This utility simply places the ethernet controller in promiscuous mode and monitors the local area network traffic. It preallocates 10 receive buffers and attempts to keep 22 reads pending on the ethernet dev- ice. CAVEATS Placing the ethernet controller in promiscuous mode may severly slow down a VAX system. Depending on the speed of the VAX system and the amount of traffic on the lo- cal ethernet, a large amount of CPU time may be spent on the Interrupt Stack. Running this code on any pro- duction system during operational hours is discouraged. BUGS Due to a bug in the VAX/VMS ethernet/802 device driver, IEEE 802 format packets may not always be detected. A simple test is performed to "guess" which packets are NOCTools2 Working Group [Page 73] RFC 1470 FYI: Network Management Tool Catalog June 1993 in IEEE 802 format (DSAP equal to SSAP). Thus, some DSAP/SSAP pairs may be reported as an ethernet type, while valid ethernet types may be reported as IEEE 802 packets. In some hardware configurations, placing an ethernet controller in promiscuous mode with automatic-restart enabled will hang the controller. Our VAX 8650 hangs running this code, while our uVAX IIs and uVAX IIIs do not. Please report any additional bugs to the author at: Allen Sturtevant National Magnetic Fusion Energy Computer Center Lawrence Livermore National Laboratory P.O. Box 808; L-561 Livermore, CA 94550 Phone : (415) 422-8266 E-Mail: sturtevant@ccc.nmfecc.gov LIMITATIONS The user is required to have PHY_IO, TMPMBX and NETMBX privileges. When activated, the program first checks that the user process as enough quotas remaining (BYTLM, BIOLM, ASTLM and PAGFLQUO) to successfully run the program without entering into an involuntary wait state. Some quotas require a fairly generous setting. The contents of IEEE 802 packets are not examined. Only the presence of IEEE 802 packets on the wire is reported. The count of lost packets is approximated. If, after each read completes on the ethernet device, the utility detects that it has no reads pending on that device, the lost packet counter is incremented by one. When the total number of bytes processed exceeds 7fffffff hex, all counters are automatically reset to zero. HARDWARE REQUIRED A DEC ethernet controller. SOFTWARE REQUIRED VAX/VMS version V5.1+. NOCTools2 Working Group [Page 74] RFC 1470 FYI: Network Management Tool Catalog June 1993 AVAILABILITY For executables only, FTP to the ANONYMOUS account (password GUEST) on CCC.NMFECC.GOV and GET the follow- ing files: [ANONYMOUS.PROGRAMS.ENTM]ENTM.DOC (ASCII text) [ANONYMOUS.PROGRAMS.ENTM]ENTM.EXE (binary) [ANONYMOUS.PROGRAMS.ENTM]EN_TYPES.DAT (ASCII text) [ANONYMOUS.PROGRAMS.ENTM]IP_TYPES.DAT (ASCII text) NOCTools2 Working Group [Page 75] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog Interactive Network Map NAME map -- Interactive Network Map KEYWORDS manager, map; CHAOS, ethernet, IP, ring, star; NMS, ping, SNMP, X; UNIX; free, sourcelib. ABSTRACT Map draws a map of network connectivity and allows interactive examination of information about various components including whether hosts can be reached over the network. The program is supplied with complete source and is written in a modular fashion to make addition of dif- ferent protocols stacks, displays, or hardcopy devices relatively easy. This is one of the reasons why the initial version supports at least two of each. Contri- butions of additional drivers in any of these areas will be welcome as well as porting to additional plat- forms. MECHANISM Net components are pinged by use of ICMP echo and, optionally, CHAOS status requests and SNMP "gets." The program initializes itself from static data stored in the file system and therefore does not need to access the network in order to get running (unless the static files are network mounted). CAVEATS As of publication, the tool is in beta release. BUGS Several minor nits, documented in distribution files. Bug discoveries should be reported by email to Bug- Map@LCS.MIT.Edu. LIMITATIONS See distribution file for an indepth discussion of sys- tem capabilities and potential. HARDWARE REQUIRED An X display is needed for interactive display of the map, non-graphical interaction is available in non- display mode. For hardcopy output a PostScript or Tek- NOCTools2 Working Group [Page 76] RFC 1470 FYI: Network Management Tool Catalog June 1993 tronix 4692 printer is required. SOFTWARE REQUIRED BSD UNIX or related OS. IP/ICMP is required; CHAOS/STATUS and SNMP can be used but are optional. X-Windows is required for interactive display of the map. AVAILABILITY The program is Copyright MIT. It is available via anonymous FTP with a license making it free to use and distribute for non-commercial purposes. FTP to host FTP.LCS.MIT.Edu, directory nets. The complete distribution is in map.tar.Z and some short documentation files are there (as well as in the distribution). Of most interest are ReadMe and Intro. To be added to the email forum that discusses the software, or for other administrative details, send a request to: MAP-Request@LCS.MIT.Edu NOCTools2 Working Group [Page 77] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog MCONNECT NAME mconnect KEYWORDS status; SMTP; spoof; UNIX. ABSTRACT Mconnect allows an interactive session with a remote mailer. Mail delivery problems can be diagnosed by connecting to the remote mailer and issuing SMTP com- mands directly. MECHANISM Opens a TCP connection to remote SMTP on port 25. Pro- vides local line buffering and editing, which is the distinction between mconnect and a TELNET to port 25. CAVEATS None. BUGS None known. LIMITATIONS Mconnect is not a large improvement over using a TELNET connection to port 25. HARDWARE REQUIRED No restrictions. SOFTWARE REQUIRED BSD UNIX or related OS. AVAILABILITY Available with 4.xBSD UNIX and related operating sys- tems. NOCTools2 Working Group [Page 78] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog MIB-BROWSER NAME MIB Browser KEYWORDS manager; osi; cmis, x; unix; free, sourcelib. ABSTRACT The MIB Browser is an X Windows HCI tool that allows you to "browse" through the objects in a Management Information Base (MIB). The browser is generic in that it can connect to a CMIS agent without having any prior knowledge of the structure of the MIB in the agent. MECHANISM CMIP is used to transfer the values of attributes between the managed system and the browser. CAVEATS None. BUGS Unexpected termination of the agent can cause browser to crash (ISODE bug!). HARDWARE REQUIRED Unix workstation, has been tested on SUN 3 and SUN 4 architectures. SOFTWARE REQUIRED The ISODE protocol suite, BSD UNIX, X Windows, GNU C++ (g++), Interviews (2.6). AVAILABILITY The CMIP library and related management tools built upon it, known as OSIMIS (OSI Management Information Service), are publicly available from University College London, England via FTP and FTAM. To obtain information regarding a copy send email to osimis-request@cs.ucl.ac.uk or call +44 71 380 7366. NOCTools2 Working Group [Page 79] RFC 1470 FYI: Network Management Tool Catalog June 1993 Internet Tool Catalog MONET NAME MONET -- the Hughes LAN Systems SNMP Network Management Center (formerly the Hughes LAN Systems 9100) software product runs on a Sun SPARCStation hardware platform. KEYWORDS control, graphics, network topology,manager, routing, status, traffic; bridge, configuration, performance, alarm management, relational database, mib parser for RDBMS, intelligent hub management, DECnet, ethernet, IP; NMS, SNMP; UNIX. ABSTRACT Monet provides the capability to manage and control SNMP-based networking products from any vendor including those from Hughes LAN Systems. A comprehensive relational database manages the data and ensures easy access and control of resources throughout the network. Monet provides multivendor management through its advanced Mib master MIB parser that allows the parsing of enterprise MIBs (ASN.1 format per RFC1212) directly into the RDBMS for use by Monet's applications. Major features include: Remote access with X: Use of the X/Motif user-interface, enabling remote access to the all applications. Database Management Stores and retrieves the information required to administer and configure the network. It can be used to: - Store and recall configuration data for all devices. - Provide availability history for devices. - Assign new internet addresses. - Provide administrative information such as physical location of devices, responsible person, maintenance history, asset data, hardware/software versions, etc. - Full-function SQL interface. - User-customizable RDBMS report generation. NOCTools2 Working Group [Page 80] RFC 1470 FYI: Network Management Tool Catalog June 1993 Graphics and Network Mapping The Graphics module enables the user to view the nodes in the network as "dynamic" icons in heirarchical maps. The network is represented by these heirarchical maps. Though there is a library of device icons, cities and geographical maps included, the user has access to a graphics editor that allows customizing and the creation of new icons and maps. A Device's icon may be selected to: - Register/deregister the device, - Access the open alarms and acknowledge faults for the selected device, - Ping the device to determine accessibility, - Draw graphs of any of the |