2Management44Deleting a single fileThe ‐rm option can be used to delete files from permanent storage. For example, to removethe file 2011‐01‐01_00.00.52_dpcore.dump, the command would be:Device:/> crashdump ‐rm=2011‐01‐01_00.00.52_dpcore.dumpDeleting all filesAll crashdump files stored in memory can be deleted with the command:Device:/> crashdump ‐rm=allInstead of all, the asterisk character (*) can also be used as a wildcard:Device:/> crashdump ‐rm=*Important: The size of non‐volatile memory available for crashdump file storage is limited, soit is important to delete crashdump files as soon they have been downloaded.StatisticsThe SEG maintains a large number of counters in memory that keep track of system activity.This information is kept only in memory and is mostly made up of single numerical values. Thepurpose of this is to be able to give the administrator an overview of the tasks beingperformed by the system. The counters are collectively known as SEG statistics.A separate document called the SEG‐100 Statistics Reference provides a detailed listing of allavailable statistical values. This section is designed to give a short introduction to theirstructure and use.Accessing statisticsThere are two methods for the administrator to view SEG statistics:• By using the statistics command in a CLI console.• Using an SNMP client in conjunction with the Clavister MIB file.This section describes examining statistics through the CLI. SNMP access to the SEG isdescribed in SNMP monitoring on page 31.Hierarchical statistics structureAll statistics are part of a hierarchical tree structure that divides them into related values. Thisstructure can be clearly seen in the contents of the Statistics Reference.An individual statistic is identified by means of a “path” that includes everything above it inthe hierarchy. The form of this path is described in the Statistics Reference. For example, thepath definition for an interface’s bytes_in statistic is:/ifaces/[..n]/bytes_inWhere [..n] represents the name of the interface.