The Datafile PD-CD 3

home *** CD-ROM | disk | FTP | other *** search

/ The Datafile PD-CD 3 / PDCD_3.iso / internet / bootnet / ReadMe-ANT next >

Wrap

Text File | 1995-08-08 | 36.2 KB | 1,256 lines

Introduction What's New? *configure etherX multiple *eXtest commands *showstat command Downloading new drivers from the Internet Downloading via WWW Downloading via anonymous FTP Configuration Commands Default Terse Verbose Single Multiple LiveWireTest NoLiveWireTest Strict Ignore Enable Disable Selftests and the *eXtest commands A couple of obscure points Statistics and trouble shooting The *showstat command Summary of *commands described Obtaining further assistance ----------------------------------------------------------------------------- Introduction This release of ANT's network device drivers for its ethernet cards conform to the new DCI4 interface specification. Additional support for PC cards has been added to the drivers, along with a separate program to collect statistic information and present it tidily. ----------------------------------------------------------------------------- What's New? The major enhancement of interest to PC card users is the ability to configure for multiple operation. This is a software trick that makes one ethernet card appear to be two cards, permitting RISC OS and the PC card to connect to differently named interfaces. Together with a network client such as OmniClient, this makes it possible to view the same network file server in both RISC OS and PC windows at the same time. This feature is available in both the Ether3 and EtherB drivers. See the section on configuration commands for usage details. For easier network administration, a *command has been added that runs the selftests. This can be used at any stage (selftests are normally only run when a network protocol first connects to an ethernet interface). See the section on selftests for The *showstat program collects statistics from any module that understands that ANT Statistics Protocol and presents them tidily. Currently, all our DCI4 network drivers and the Mbuf Manager are capable of supplying statistics suitably. We intend to increase the range of programs supporting this protocol. ----------------------------------------------------------------------------- Downloading new drivers from the Internet You can download the latest network device drivers from our WWW and anonymous FTP sites on the Internet. ----------------------------------------------------------------------------- Downloading via WWW For general information on our DCI4 drivers, you should access the URL http://www.ant.co.uk/dci4/ For specific downloading options, access the URL http://www.ant.co.uk/dci4/download.html ----------------------------------------------------------------------------- Downloading via FTP Important: if your FTP client permits you to vary the transfer mode, ensure that you have selected image (binary) transfer mode before downloading new device drivers or programs. For a traditional FTP client, the following information is relevant: host: ftp.ant.co.uk userid: anonymous password: <your email address> directory: /pub/dci4/ When using an FTP client built into a web browser (such as ANT's Fresco), the following URL should be used: ftp://ftp.ant.co.uk/pub/dci4/ ----------------------------------------------------------------------------- Configuration Commands In general, the configuration options available are the same across Ether3, EtherB and EtherP modules with the same version number. The EtherP module does not use CMOS RAM to store its configuration options, as there is none allocated (to the parallel port) that it may safely use. Instead, EtherP takes an argument string when being loaded that contains the necessary configuration options. Most of the configuration options are paired together. For example, the verbose option is paired with the terse option. The general form for configuration is: *Configure <driver-name> <option> [slot] Where: <driver-name> is Ether3, EtherB or EtherP <option> is one of the options listed below [slot] specifies a specific expansion card slot to apply the configuration option to. This paramater is optional. It is used when an Ether3 module is controlling more than one expansion card and it is desired to update the configuration options associated with only one of them. By way of example, the following illustrates how to configure "verbose" operation: For Ether3 modules: *configure Ether3 verbose For EtherB modules: *configure EtherB verbose For EtherP modules only: The RMload command in the startup file in the files subdirectory of the !Internet directory that loads the Ethernet module requires the options appending. A standard startup file contains a section similar to this: | Load driver and initialise Ethernet interface, if required IF "<Inet$EtherIPAddr>" <> "" AND "<Inet$EtherDevice>" <> "" THEN rmload inet:drivers.<Inet$EtherDevice> This should be changed to something similar to | Load driver and initialise Ethernet interface, if required, | including configuration options IF "<Inet$EtherIPAddr>" <> "" AND "<Inet$EtherDevice>" <> "" THEN rmload inet:drivers.<Inet$EtherDevice> verbose ----------------------------------------------------------------------------- Configuration option: default Applicability : ether3, etherb Description: ============ Selecting this configuration option restores all configuration options to their default values. Example: ======== *configure ether3 default This restores the configuration of an Ether3 card to the default values. These are equivalent to: *configure ether3 Enable *configure ether3 Strict *configure ether3 NoLiveWireTest *configure ether3 Terse *configure ether3 Single Notes: ====== This restoration happens automatically if the values recorded in CMOS RAM are detected as being incorrect (say because a different type of card was previously installed in the same expansion card slot the last time the machine was used). With EtherP, simply supply no command line arguments when the module is loaded. ----------------------------------------------------------------------------- Configuration option: terse Paired with : verbose Applicability : ether3, etherb Description: ============ 1) When performing selftests, terse operation causes printing to only occur if an error is encountered. 2) Terse selftests perform a quicker memory test than verbose selftests. 3) Terse operation generally omits printing a count for a statistic if the value is zero. Example: ======== *configure ether3 terse This configures an Ether3 card to operate in terse mode. Notes: ====== Terse operation is often the most convenient in normal use. ----------------------------------------------------------------------------- Configuration option: verbose Paired with : terse Applicability : ether3, etherb Description: ============ 1) When performing selftests, verbose operation always prints the test being conducted and the test result. 2) Verbose selftests perform a more extensive memory test than terse selftests. This adds notably to the time it takes to perform selftests, but can be a useful diagnostic aid. 3) A verbose configuration lists all available statistics, including those that are zero. Example: ======== *configure ether3 verbose This configures an Ether3 card to operate in verbose mode. Notes: ====== See also the *showstat command. ----------------------------------------------------------------------------- Configuration option: single Paired with : multiple Applicability : ether3, etherb Description: ============ When configured for single operation, each ethernet card presents one software interface to network protocols. This is the more traditional mode of operation, as contrasted with multiple operation. Example: ======== *configure ether3 single This configures an Ether3 card to operate in single mode. This causes an interface named "ea0" to be presented in software to the rest of the system. Notes: ====== ----------------------------------------------------------------------------- Configuration option: multiple Paired with : single Applicability : ether3, etherb Description: ============ When configured for multiple operation, each ethernet card presents two seperate software interfaces. In effect, multiple operation makes one ethernet card appear as if it were actually two ethernet cards at the software level. This can be very useful when using network clients from within the RISC OS desktop and !PC486 to examine the same file server. Example: ======== *configure ether3 multiple This configures an Ether3 card to operate in multiple mode. This causes two interfaces named "ea0" and "ea1" to be presented in software to the rest of the system. Notes: ====== Unless you require multiple operation, we recommend you use single operation - there can be a performance overhead when operating with multiple operation. ----------------------------------------------------------------------------- Configuration option: livewiretest Paired with : nolivewiretest Applicability : ether3, etherb Description: ============ When configured for livewiretest operation, the selftests performed when an ethernet card starts up include transmitting three packets onto the network and checking their receiption. Example: ======== *configure ether3 livewiretest This configures an Ether3 card to operate in livewiretest mode. Notes: ====== ----------------------------------------------------------------------------- Configuration option: nolivewiretest Paired with : livewiretest Applicability : ether3, etherb Description: ============ When configured for nolivewiretest operation, the selftests performed when an ethernet card starts up refrain from transmitting any packets onto the currently attached network. Loopback packet tests (which are performed entirely within the ethernet card itself) are still performed. Example: ======== *configure ether3 nolivewiretest This configures an Ether3 card to operate in nolivewiretest mode. Notes: ====== There are some network configurations where livewiretests can be guaranteed to fail. Nolivewiretest operation is intended for such situations. ----------------------------------------------------------------------------- Configuration option: strict Paired with : ignore Applicability : ether3, etherb Description: ============ When configured for strict operation, all selftests performed must pass. Example: ======== *configure ether3 strict This configures an Ether3 card to operate in strict mode. Notes: ====== Strict operation is the recommended mode of operation. ----------------------------------------------------------------------------- Configuration option: ignore Paired with : strict Applicability : ether3, etherb Description: ============ When configured for ignore operation, any failures encountered during live wire tests (if performed) are ignored. This option should be excercised with caution. Example: ======== *configure ether3 ignore This configures an Ether3 card to operate in ignore mode. Notes: ====== Ignore operation is only advised when specifically recommended by your network administrator. ----------------------------------------------------------------------------- Configuration option: enable Paired with : disable Applicability : ether3, etherb Description: ============ This option selects enable operation. Only if an ethernet card is configured for enable operation can it be used. Enable operation is the normal operation mode. Example: ======== *configure ether3 enable This configures an Ether3 card to operate in enable mode, permitting it to be used. Notes: ====== ----------------------------------------------------------------------------- Configuration option: disable Paired with : enable Applicability : ether3, etherb Description: ============ Selecting disable operation prevents an ethernet card from being used. Disable operation is rarely required. Example: ======== *configure ether3 disable This prevents an ethernet card from being used by selecting disable operation. Notes: ====== There are times when this mode of operation is extremely useful, but they are rare. ----------------------------------------------------------------------------- Selftests and the *eXtest commands Diagnosing network problems can be difficult at the best of times, so anything the network drivers can do to assist is very useful. The two major ways in which they do assist are the selftests and statistics gathering (described later). The selftests are a collection of thorough test routines that exercise a range of features of the ethernet card. They are invoked either from a *command or when a network protocol first connects to an ethernet interface. Some configuration options are available to alter the amount of testing performed (see the section detailing configuration commands). Whether any messages are printed for successfully passed tests is configurable. Any test that fails will always print a message. If any selftest fails, you are strongly recommended to contact their network administrator for advice. For example, an EtherB driver module with the following configuration options active: single verbose livewiretest enable strict produces the following output on selftests: Locate controller . . . . 80C04.AF Network slot Interrupts . . . . . . . . passed Buffer memory . . . . . . passed Loopback, correct CRC . . passed Loopback, incorrect CRC . passed Loopback, controller CRC . passed Livewire, correct CRC . . passed Livewire, incorrect CRC . passed Livewire, controller CRC . passed The first three tests perform basic functionality tests on the Ethernet controller and the associated buffer memory. Locate controller . . . . -------------------------- This tests that the Ethernet controller can be accessed and that it's internal registers are operative. This test should never fail. Interrupts . . . . . . . . -------------------------- This tests basic functionality of the interrupt generation of the Ethernet controller. This test should never fail. Buffer memory . . . . . . -------------------------- This tests the buffer memory contained on the Ethernet card. If the driver module is configured for verbose operation, then more extensive (and time consuming) tests of buffer memory are performed. This test should never fail. If there is insufficient RMA available for the buffers used by this test, then it cannot be performed and the test is deemed passed. If selftesting is being reported, this test is annotated as being skipped if there is not sufficient RMA. The tests that follow these three basic tests are packet transmission and receiption tests. There are three variants of the packet test, performed first in loopback mode and then on the live network (if *Configured for "livewiretest", see below). Loopback mode is a special mode of operation of the ethernet card for diagnostic purposes, where packets are not transmitted onto the connected network, but internally redirected back to the ethernet cards own receiver. This permits the ethernet card to transmit a packet and check its correctness. These tests verify the correct operation of many components of the interface. Loopback, correct CRC . . Loopback, incorrect CRC . Loopback, controller CRC . Livewire, correct CRC . . Livewire, incorrect CRC . Livewire, controller CRC . In general, if an error occurs during loopback testing, the ethernet card itself may be faulty. If loopback tests pass without error but live network tests fail, this normally indicates a problem with the network itself. Note: If "nolivewiretest" had been configured, the last three tests would not have been performed and the last three lines would not have been printed. ----------------------------------------------------------------------------- A couple of obscure points When a *eXtest command is issued, the interface being tested needs to be temporarily retracted from service, which causes network protocols using it to disconnect. When the testing is complete, the interface's existence is announced and network protocols reconnect to it. In normal operation this actually causes two selftests to be performed. The first in response to the *command itself and the second because, once testing is complete, the interface has been connected to by a network protocol. If no network protocol is connected to the interface being tested, then only one selftest is performed. When operating in multiple mode, selftests are testing the real hardware associated with an interface. This means both interfaces associated with the hardware must be withdrawn from service whilst the tests are being performed. If both interfaces were previously in use by network protocols, a single *ebtest command can lead to four seperate selftests being performed on the one piece of hardware! The sequence of actions actually performed is: test first interface - eb0 withdraw eb0 from service - being test withdraw eb1 from service - associated interface perform first selftest - *ebtest eb0 equivalent announce eb1 - network protocol reconnects perform second selftest - network protocol connection announce eb0 test second interface - eb1 withdraw eb1 from service - being test withdraw eb0 from service - associated interface perform third selftest - *ebtest eb1 equivalent announce eb0 - network protocol reconnects perform fourth selftest - network protocol connection announce eb1 ----------------------------------------------------------------------------- Statistics and trouble shooting Each of the ANT DCI4 device driver modules collects statistics (such as number of packets transmitted and received) during operation and supports a *command to print these accumlated interface statistics. Additionally, the *showstat command collects statistics from those modules offering them and presents them tidily. For an Ether3 module, use the *e3info to print interface statistics. For EtherB, use *ebinfo. For EtherP, use *epinfo. Under normal operation, the interface statistics gathered can be ignored. However, as a network problem diagnostic tool, they can be invaluable diagnostic tool. The most important thing to do when determing the cause of network problems is to determine at what level the error is occurring. It might be a physical problem (network not connected, server on a physically different and unconnected network), an Internet configuration problem (incorrectly assigned IP number or network mask), a routing problem (not uncommon when initially connecting multiple networks together), etc. Each type of fault requires a different type of remedy. Time spent examining working sections of a configuration is often better spent determining what is not working. If you suspect multiple parts of a configuration are not working, start with the lowest level and work upwards. Two major clues can be obtained from the interface statistics. Firstly, major packet errors have their own count - if any of these counts is non-zero, then a low level network problem exists and needs investigating and correcting. For example, receiption of packets of CRC errors suggests the network cabling might be faulty somewhere. Large numbers of transmission collisions might be due to the network not be correctly connected. The next major clue is the count of packets transmitted and received. When access to a fileserver or other network facility appears unavailable, the first thing to determine is whether the server machine is contactable at all over the network. This is typically performed with the "ping" (TCP/IP) and "netprobe" (AUN) commands. Under normal operation, each ping/netprobe causes (at least) one packet to be transmitted and (at least) one to be received under normal operation. As an example of the printing of interface statistics, the following shows the results of a *ebinfo when configured for terse operation. Remember that statistics which have a count of zero only have their names printed in terse mode. This makes it easier to spot non-zero values, which are generally the more significant values to observe. EtherB interface statistics eb0: 80C04.AF Network slot, slot 8, up, hardware address 00:00:A4:10:1A:9E Interface driver : eb (built Aug 3 1995) Interface unit : 0 Interface location : Netcard slot Interface address : 00:00:A4:10:1A:9E Interface controller: 80C04.AF Network slot Initialise time : Mon Aug 7 11:25:52 1995 Running time : 17 minutes, 50 seconds. Packets sent : 2021 Packets received : 2143 Bytes sent : 421963 Bytes received : 479185 Send errors : Receive errors : Broadcasts sent : Broadcasts received : 119 Multicasts sent : Multicasts received : 4 Monitor sends : Monitor receives : Send interrupts : 2021 Receive interrupts : 2143 Delivered packets : 2143 Undelivered packets : Sends too large : Send max collisions : Send overflows : Sends blocked : Receives too small : Receives too large : Incomplete receives : Receive CRC errors : Lack of mbufs : Receive overflows : Standard clients: Frame = &0800, ErrLvl=00, AddrLvl=01 Frame = &0806, ErrLvl=00, AddrLvl=01 Frame = &8035, ErrLvl=00, AddrLvl=01 IEEE 802.3 client: Frame = &0000, ErrLvl=00, AddrLvl=02 Log: EtherB messages can appear here The message log (the section prefixed by "Log:" above) is used to record the last error delivered by the ethernet driver module. This can be useful when an intervening layer of software translates an error to a different one. It is initialised with a message indicating it's purpose rather than leaving it empty. ----------------------------------------------------------------------------- The following output shows an example network fault (in this case, the network has been deliberately unplugged). Three commands are issued: *ebtest, *ebinfo and *showstat. Note the extra section marked Failures noted during testing: that has appeared in the *ebinfo output. The information that is printed here when a selftest fails is often enough to let a network administrator work out what to do to get a working setup. The reason why two selftests are performed is given in the section called "A couple of obscure points". *ebtest Locate controller . . . . 80C04.AF Network slot Interrupts . . . . . . . . passed Buffer memory . . . . . . passed Loopback, correct CRC . . passed Loopback, incorrect CRC . passed Loopback, controller CRC . passed Livewire, correct CRC . . FAILED Locate controller . . . . 80C04.AF Network slot Interrupts . . . . . . . . passed Buffer memory . . . . . . passed Loopback, correct CRC . . passed Loopback, incorrect CRC . passed Loopback, controller CRC . passed Livewire, correct CRC . . FAILED eb0 (Netcard slot) FAILED SELFTESTS Error: eb0: Interface faulty eb0: Interface faulty *ebinfo EtherB interface statistics eb0: 80C04.AF Network slot, slot 8, failed selftest, hardware address 00:00:A4:10:1A:9E Interface driver : eb (built Aug 3 1995) Interface unit : 0 Interface location : Netcard slot Interface address : 00:00:A4:10:1A:9E Interface controller: 80C04.AF Network slot Initialise time : Mon Aug 7 13:52:25 1995 Running time : Interface not active Packets sent : 6 Packets received : 7 Bytes sent : 6160 Bytes received : 6292 Send errors : 2 Receive errors : 2 Broadcasts sent : 0 Broadcasts received : 1 Multicasts sent : 0 Multicasts received : 0 Monitor sends : 0 Monitor receives : 0 Send interrupts : 8 Receive interrupts : 7 Delivered packets : 7 Undelivered packets : 0 Sends too large : 0 Send max collisions : 2 Send overflows : 0 Sends blocked : 0 Receives too small : 0 Receives too large : 0 Incomplete receives : 0 Receive CRC errors : 2 Lack of mbufs : 0 Receive overflows : 0 Failures noted during testing: Tx hw failed tests Receive interrupt failure Rx hw failed tests Live net tests failure Log: eb0: Interface faulty *showstat ANT DCI4 Statistic Gatherer 1.03 (Aug 3 1995) (C) Copyright ANT Limited 1994, 1995. All rights reserved. Device Driver Information Block Name : eb Unit : 0 Address : 00:00:A4:10:1A:9E Module : EtherB Location : Netcard slot Feature flags : : Multicast receiption is supported : Promiscuous receiption is supported : Interface receives its own transmissions : Interface can receive erroneous packets : Interface has a hardware address : Driver can alter interface's hardware address : Driver supplies standard statistics : Driver supplies extended statistics Interface type : 10Base5/10Base2/10BaseT ethernet Link Status : Interface bad Active Status : Interface inactive Receive mode : Directly addressed frames only Polarity : Correct TX excess collisions: 2 Packets transmitted : 6 Bytes transmitted : 6160 General TX errors : 2 Received packets : 7 Received bytes : 6292 General RX errors : 2 Module 'EtherB' is a supplier titled 'EtherB device driver' EtherB device driver: DCI4 Ethernet device driver for 16 bit EtherB cards Interface driver : eb (built Aug 3 1995) Interface unit : 0 Interface location : Netcard slot Interface address : 00:00:A4:10:1A:9E Interface controller: 80C04.AF Network slot Initialise time : Mon Aug 7 13:52:25 1995 Running time : Interface not active Packets sent : 6 Packets received : 7 Bytes sent : 6160 Bytes received : 6292 Send errors : 2 Receive errors : 2 Broadcasts sent : 0 Broadcasts received : 1 Multicasts sent : 0 Multicasts received : 0 Monitor sends : 0 Monitor receives : 0 Send interrupts : 8 Receive interrupts : 7 Delivered packets : 7 Undelivered packets : 0 Sends too large : 0 Send max collisions : 2 Send overflows : 0 Sends blocked : 0 Receives too small : 0 Receives too large : 0 Incomplete receives : 0 Receive CRC errors : 2 Lack of mbufs : 0 Receive overflows : 0 Module 'MbufManager' is a supplier titled 'Mbuf Manager' Mbuf Manager : System wide memory buffer (mbuf) memory management Active sessions : 2 Sessions opened : 4 Sessions closed : 2 Memory pool size : 102400 Small block size : 128 Large block size : 1536 Mbuf exhaustions : 0 Small mbufs in use : 3 Small mbufs free : 509 Large mbufs in use : 0 Large mbufs free : 24 ----------------------------------------------------------------------------- The *showstat command The *showstat command is a disc based program that produces a tidy presentation of the statistics from the network device driver modules. It does an excellent job at collecting together the information that is likely to be needed to diagnose low level network problems. Your network administrator will thank you if you have the output of *showstat to hand when reporting any network problems. Currently, the ethernet device drivers and the mbuf manager know how to supply statistics to it. Other ANT products are likely to support showstat in the future. An example of the output produced looks like: ANT DCI4 Statistic Gatherer 1.03 (Aug 3 1995) (C) Copyright ANT Limited 1994, 1995. All rights reserved. Device Driver Information Block Name : eb Unit : 0 Address : 00:00:A4:10:1A:9E Module : EtherB Location : Netcard slot Feature flags : : Multicast receiption is supported : Promiscuous receiption is supported : Interface receives its own transmissions : Interface can receive erroneous packets : Interface has a hardware address : Driver can alter interface's hardware address : Driver supplies standard statistics : Driver supplies extended statistics Interface type : 10Base5/10Base2/10BaseT ethernet Link Status : Interface okay Active Status : Interface active Receive mode : Direct, broadcast and multicast frames Polarity : Correct Packets transmitted : 2016 Bytes transmitted : 421649 Received packets : 2134 Received bytes : 478593 Device Driver Information Block Name : eb Unit : 1 Address : 00:00:A4:90:1A:9E Module : EtherB Location : Netcard slot Feature flags : : Multicast receiption is supported : Promiscuous receiption is supported : Interface receives its own transmissions : Interface can receive erroneous packets : Interface has a hardware address : Driver can alter interface's hardware address : Driver supplies standard statistics : Driver supplies extended statistics : Interface is a secondary interface Interface type : 10Base5/10Base2/10BaseT ethernet Link Status : Interface okay Active Status : Interface inactive Receive mode : Direct, broadcast and multicast frames Polarity : Correct Module 'EtherB' is a supplier titled 'EtherB device driver' EtherB device driver: DCI4 Ethernet device driver for 16 bit EtherB cards Interface driver : eb (built Aug 3 1995) Interface unit : 0 Interface location : Netcard slot Interface address : 00:00:A4:10:1A:9E Interface controller: 80C04.AF Network slot Initialise time : Mon Aug 7 11:25:52 1995 Running time : 17 minutes, 10 seconds. Packets sent : 2016 Packets received : 2136 Bytes sent : 421649 Bytes received : 478705 Send errors : 0 Receive errors : 0 Broadcasts sent : 0 Broadcasts received : 116 Multicasts sent : 0 Multicasts received : 4 Monitor sends : 0 Monitor receives : 0 Send interrupts : 2016 Receive interrupts : 2136 Delivered packets : 2136 Undelivered packets : 0 Sends too large : 0 Send max collisions : 0 Send overflows : 0 Sends blocked : 0 Receives too small : 0 Receives too large : 0 Incomplete receives : 0 Receive CRC errors : 0 Lack of mbufs : 0 Receive overflows : 0 Module 'EtherB' is a supplier titled 'EtherB device driver' EtherB device driver: DCI4 Ethernet device driver for 16 bit EtherB cards Interface driver : eb (built Aug 3 1995) Interface unit : 1 Interface location : Netcard slot Interface address : 00:00:A4:90:1A:9E Interface controller: 80C04.AF Network slot Initialise time : Mon Aug 7 11:25:52 1995 Running time : Interface not active Packets sent : 0 Packets received : 0 Bytes sent : 0 Bytes received : 0 Send errors : 0 Receive errors : 0 Broadcasts sent : 0 Broadcasts received : 0 Multicasts sent : 0 Multicasts received : 0 Monitor sends : 0 Monitor receives : 0 Send interrupts : 0 Receive interrupts : 0 Delivered packets : 0 Undelivered packets : 0 Sends too large : 0 Send max collisions : 0 Send overflows : 0 Sends blocked : 0 Receives too small : 0 Receives too large : 0 Incomplete receives : 0 Receive CRC errors : 0 Lack of mbufs : 0 Receive overflows : 0 Module 'MbufManager' is a supplier titled 'Mbuf Manager' Mbuf Manager : System wide memory buffer (mbuf) memory management Active sessions : 3 Sessions opened : 4 Sessions closed : 1 Memory pool size : 102400 Small block size : 128 Large block size : 1536 Mbuf exhaustions : 0 Small mbufs in use : 19 Small mbufs free : 493 Large mbufs in use : 0 Large mbufs free : 24 ----------------------------------------------------------------------------- For reference, contrast the above *showstat output with that produced by a *ebinfo command shortly afterwards: EtherB interface statistics eb1: 80C04.AF Network slot, slot 8, down, hardware address 00:00:A4:90:1A:9E Secondary interface Interface driver : eb (built Aug 3 1995) Interface unit : 1 Interface location : Netcard slot Interface address : 00:00:A4:90:1A:9E Interface controller: 80C04.AF Network slot Initialise time : Mon Aug 7 11:25:52 1995 Running time : Interface not active Packets sent : Packets received : Bytes sent : 0 Bytes received : 0 Send errors : Receive errors : Broadcasts sent : Broadcasts received : Multicasts sent : Multicasts received : Monitor sends : Monitor receives : Send interrupts : Receive interrupts : Delivered packets : Undelivered packets : Sends too large : Send max collisions : Send overflows : Sends blocked : Receives too small : Receives too large : Incomplete receives : Receive CRC errors : Lack of mbufs : Receive overflows : eb0: 80C04.AF Network slot, slot 8, up, hardware address 00:00:A4:10:1A:9E Interface driver : eb (built Aug 3 1995) Interface unit : 0 Interface location : Netcard slot Interface address : 00:00:A4:10:1A:9E Interface controller: 80C04.AF Network slot Initialise time : Mon Aug 7 11:25:52 1995 Running time : 17 minutes, 50 seconds. Packets sent : 2021 Packets received : 2143 Bytes sent : 421963 Bytes received : 479185 Send errors : Receive errors : Broadcasts sent : Broadcasts received : 119 Multicasts sent : Multicasts received : 4 Monitor sends : Monitor receives : Send interrupts : 2021 Receive interrupts : 2143 Delivered packets : 2143 Undelivered packets : Sends too large : Send max collisions : Send overflows : Sends blocked : Receives too small : Receives too large : Incomplete receives : Receive CRC errors : Lack of mbufs : Receive overflows : Standard clients: Frame = &0800, ErrLvl=00, AddrLvl=01 Frame = &0806, ErrLvl=00, AddrLvl=01 Frame = &8035, ErrLvl=00, AddrLvl=01 IEEE 802.3 client: Frame = &0000, ErrLvl=00, AddrLvl=02 Log: EtherB messages can appear here ----------------------------------------------------------------------------- Summary of *commands described *ebtest Perform selftests when using the EtherB module. *e3test Perform selftests when using the Ether3 module. *eptest Perform selftests when using the EtherP module. *ebtest Display statistics when using the EtherB module. *e3test Display statistics when using the Ether3 module. *eptest Display statistics when using the EtherP module. *showstat Collect and display available statistics *configure etherX default Restore default configuration for an ethernet device driver. *configure etherX terse Select terse operation *configure etherX verbose Select verbose operation *configure etherX single Each physical card presents one interface in software *configure etherX multiple Each physical card presents two interfaces in software *configure etherX livewiretest Configure selftests to perform packet tests on the attached network. *configure etherX nolivewiretest Configure selftests to not perform packet tests on the attached network. *configure etherX strict Any errors encountered during livewiretests are significant. *configure etherX ignore Errors encountered during livewiretests are ignored. *configure etherX enable Permit use of a network card *configure etherX disable Prevent use of a network cards ----------------------------------------------------------------------------- Obtaining further assistance You can contact us by email at the following address support@ant.co.uk You can fax your questions to +44 (0) 1223 567801 You can post enquires to ANT Limited PO BOX 300 Cambridge CB1 2EG You can browse support information on our WWW site http://www.ant.co.uk/ We also operate an FTP site ftp://ftp.ant.co.uk/ You can also receive assistance from the electronic news groups in the comp.sys.acorn hierarchy. ----------------------------------------------------------------------------- Document ends. Borris. 8th August 1995.