|
|
This chapter describes how to configure network management features on the Catalyst 6000 and 6500 series switches.
This chapter consists of these sections:
These sections describe how to use the Simple Network Management Protocol (SNMP) on the Catalyst 6000 and 6500 series switches:
The components of SNMP network management fall into three categories:
SNMP network management uses these SNMP agent functions:
Catalyst 6000 and 6500 series switches are managed devices that support SNMP network management with the following features:
Table 10-1 describes the SNMP default configuration.
| Feature | Default Setting |
|---|---|
SNMP community strings |
|
SNMP trap receiver | None configured |
SNMP traps | None enabled |
To configure SNMP from a NMS, refer to the NMS documentation (see the "Using CiscoWorks2000 with Catalyst 6000 Series and 6500 Series Switches" section).
The switch supports up to 20 trap receivers through the RMON2 trap destination table. Configure the RMON2 trap destination table from the NMS.
To configure SNMP from the command-line interface (CLI), perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Define the SNMP community strings for each access type. | set snmp community read-only community_string |
Step 2 Assign a trap receiver and community. You can specify up to ten trap receivers. | set snmp trap rcvr_address rcvr_community |
Step 3 Specify the SNMP traps to send to the trap receiver. | set snmp trap enable [all | module | chassis | bridge | repeater | auth | vtp | ippermit | vmps | config | entity | stpx] |
Step 4 Verify the SNMP configuration. | show snmp |
This example shows how to define community strings, assign a trap receiver, and specify which traps to send to the trap receiver:
Console> (enable) set snmp community read-only Everyone SNMP read-only community string set to 'Everyone'. Console> (enable) set snmp community read-write Administrators SNMP read-write community string set to 'Administrators'. Console> (enable) set snmp community read-write-all Root SNMP read-write-all community string set to 'Root'. Console> (enable) set snmp trap 172.16.10.10 read-write SNMP trap receiver added. Console> (enable) set snmp trap 172.16.10.20 read-write-all SNMP trap receiver added. Console> (enable) set snmp trap enable all All SNMP traps enabled. Console> (enable) show snmp RMON: Disabled Extended Rmon: Extended RMON module is not present Traps Enabled: Port,Module,Chassis,Bridge,Repeater,Vtp,Auth,ippermit,Vmps,config,entity,stpx Port Traps Enabled: 1/1-2,4/1-48,5/1 Community-Access Community-String ---------------- -------------------- read-only Everyone read-write Administrators read-write-all Root Trap-Rec-Address Trap-Rec-Community ---------------------------------------- -------------------- 172.16.10.10 read-write 172.16.10.20 read-write-all Console> (enable)
CiscoWorks2000 is a family of Web-based and management platform-independent products for managing Cisco enterprise networks and devices. CiscoWorks2000 includes Resource Manager Essentials and CWSI Campus, which allow you to deploy, configure, monitor, manage, and troubleshoot a switched internetwork. For more information, see the following publications:
These sections describe how to use RMON on the Catalyst 6000 and 6500 series switches:
RMON is an Internet Engineering Task Force (IETF) standard monitoring specification that allows various network agents and console systems to exchange network monitoring data. The Catalyst 6000 and 6500 series supervisor engine software supports these components of the RMON specification:
The embedded RMON agent allows the switch to monitor network traffic from all ports simultaneously at the data-link layer of the OSI model without requiring a dedicated monitoring probe or network analyzer.
To enable RMON, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Enable RMON on the switch. | set snmp rmon enable |
Step 2 Verify that RMON is enabled. | show snmp |
This example shows how to enable RMON on the switch and how to verify that RMON is enabled:
Console> (enable) set snmp rmon enable SNMP RMON support enabled. Console> (enable) show snmp RMON: Enabled Extended Rmon: Extended RMON module is not present Traps Enabled: Port,Module,Chassis,Bridge,Repeater,Vtp,Auth,ippermit,Vmps,config,entity,stpx Port Traps Enabled: 1/1-2,4/1-48,5/1 Community-Access Community-String ---------------- -------------------- read-only Everyone read-write Administrators read-write-all Root Trap-Rec-Address Trap-Rec-Community ---------------------------------------- -------------------- 172.16.10.10 read-write 172.16.10.20 read-write-all Console> (enable)
Access to RMON data is available only on an NMS that supports RFC 1757 and RFC 1513.
(See the "Using CiscoWorks2000 with Catalyst 6000 Series and 6500 Series Switches" section.) You cannot access RMON data through the CLI; however, CLI show commands provide similar information. (Refer to the Catalyst 6000 and 6500 Series Command Reference publication.)
These sections describe how to use the Switched Port Analyzer (SPAN) on the Catalyst 6000 and 6500 series switches:
SPAN selects network traffic for analysis by a SwitchProbe device or other RMON probe. SPAN mirrors traffic from one or more source ports on the same VLAN to a destination port for analysis (see Figure 10-1).
When the SPAN feature is configured to mirror only the traffic transmitted from a port, Catalyst 6000 series and 6500 series switches support up to four SPAN sessions, each with separate sources and destinations; when configured to mirror received traffic or both transmitted and received traffic, the switches support up to two separate SPAN sessions.
In the figure, all traffic on Ethernet port 5 (the source port) is mirrored to Ethernet port 10. A network analyzer on Ethernet port 10 receives all network traffic from Ethernet port 5 without being physically attached to it.
To configure SPAN from the NMS, refer to the NMS documentation. (See the "Using CiscoWorks2000 with Catalyst 6000 Series and 6500 Series Switches" section.)
Specify the source ports, the destination port, the direction of the traffic through the source ports that you want to mirror to the destination port, and whether or not the destination port can receive packets. Use the create keyword to configure a second SPAN port. To monitor the traffic generated by the switch itself, use the sc0 keyword to select the console as the source port. Use the multicast keyword to include or exclude multicasts from the traffic sent to the SPAN destination port.
To configure a SPAN port on the Catalyst 6000 and 6500 series switch, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Configure SPAN source and destination ports. | set span {src_mod/src_ports | src_vlan | sc0} {dest_mod/dest_port} [rx | tx | both] [inpkts {enable | disable}] [multicast {enable | disable}] [create] |
Step 2 Verify the SPAN configuration. | show span |
This example shows how to configure SPAN so that both transmit and receive traffic from port 1/1 (the SPAN source) is mirrored on port 2/1 (the SPAN destination):
Console> (enable) set span 1/1 2/1 Enabled monitoring of Port 1/1 transmit/receive traffic by Port 2/1 Console> (enable) show span Status : enabled Admin Source : Port 1/1 Oper Source : Port 1/1 Destination : Port 2/1 Direction : transmit/receive Incoming Packets: disabled Console> (enable)
This example shows how to set VLAN 522 as the SPAN source and port 2/1 as the SPAN destination:
Console> (enable) set span 522 2/1 Enabled monitoring of VLAN 522 transmit/receive traffic by Port 2/1 Console> (enable) show span Status : enabled Admin Source : VLAN 522 Oper Source : Port 3/1-2 Destination : Port 2/1 Direction : transmit/receive Incoming Packets: disabled Console> (enable)
This example shows how to set VLAN 522 as the SPAN source and port 2/12 as the SPAN destination. Only transmit traffic is monitored. Normal incoming packets on the SPAN destination port are allowed.
Console> (enable) set span 522 2/12 tx inpkts enable SPAN destination port incoming packets enabled. Enabled monitoring of VLAN 522 transmit traffic by Port 2/12 Console> (enable) show span Status : enabled Admin Source : VLAN 522 Oper Source : Port 2/1-2 Destination : Port 2/12 Direction : transmit Incoming Packets: enabled Console> (enable)
To disable SPAN, perform this task in privileged mode:
| Task | Command |
|---|---|
Disable SPAN on the switch. | set span disable |
This example shows how to disable SPAN on the switch:
Console> (enable) set span disable Disabled monitoring of VLAN 522 transmit traffic by Port 2/1 Console> (enable)
These sections describe how to use the Cisco Discovery Protocol (CDP) on the Catalyst 6000 and 6500 series switches:
CDP is a media- and protocol-independent Layer 2 protocol that runs on all Cisco routers, bridges, access and communication servers, and switches. Using CDP, you can view information about all the Cisco devices directly attached to a Catalyst 6000 or 6500 series switch.
CDP allows network management applications to discover Cisco devices that are neighbors of already known devices, in particular, neighbors running lower-layer, transparent protocols.
CDP runs on all media that support Subnetwork Access Protocol (SNAP), including LAN and Frame Relay.
Cisco devices never forward CDP packets. When new CDP information is received, Cisco devices discard old information.
To configure CDP, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Enable CDP on the switch or on selected ports. | set cdp enable [mod_num/port_num] |
Step 2 (Optional) Set the message interval for CDP. The allowed range is 5-900 seconds (default: 60 seconds). | set cdp interval interval |
Step 3 (Optional) Set the time that CDP frames are held by the device that receives them before being aged out. The allowed range is 10-255 seconds (default: 180 seconds). | set cdp holdtime interval |
Step 4 Verify the CDP configuration. | show cdp port [mod_num[/port_num]] |
Step 5 View information about CDP neighbors. | show cdp neighbors [mod_num[/port_num]] [vlan | duplex | capabilities | detail] |
This example shows how to configure CDP on all ports and verify the configuration:
Console> (enable) set cdp enable CDP enabled for all ports. Console> (enable) set cdp interval 100 CDP message interval set to 100 seconds for all ports. Console> (enable) show cdp port CDP :enabled Message Interval :60 Hold Time :180 Port CDP Status -------- ---------- 1/1 enabled 1/2 enabled Console> (enable) show cdp neighbors * - indicates vlan mismatch. # - indicates duplex mismatch. Port Device-ID Port-ID Platform -------- ------------------------------- ------------------------- ------------ 3/5 002267619(cat1.cisco.com) 3/6 * WS-C5000 3/6 002267619(cat1.cisco.com) 3/5 WS-C5000 4/1 002267619(cat1.cisco.com) 4/2 WS-C5000 4/2 002267619(cat1.cisco.com) 4/1 # WS-C5000 4/20 069000057(cat2.cisco.com) 8/5 WS-C5500 5/1 005763872(cat3.cisco.com) 2/1 WS-C5000 5/1 066506245(cat4.cisco.com) 2/1 WS-C5505 5/1 066508595(cat5.cisco.com) 5/12 *# WS-C5505 5/1 066508596(cat6.cisco.com) 5/1 WS-C5505 Console> (enable) show cdp neighbors 1/2 detail Device-ID: 002267633 Device Addresses: IP Address:172.20.24.111 Holdtime:143 sec Capabilities:TRANSPARENT_BRIDGE SWITCH Version: WS-C5500 Software, Version McpSW:2.4(1) NmpSW:2.4(1) Copyright (c) 1995-1997 by Cisco Systems Platform:WS-C5500 Port-ID (Port on Device):5/12 Port (Our Port):1/2 VTP Management Domain:lab Native VLAN:1 Duplex:full Console> (enable)
These sections describe how to use system message logging on the Catalyst 6000 and 6500 series switches:
By default, the switch logs normal but significant system messages to its internal buffer and sends these messages to the switch console. You can specify which system messages should be saved based on the facility type (see Table 10-2) and the severity level (see Table 10-3). Messages are time-stamped to enhance real-time debugging and management.
You can access logged system messages using the switch CLI or by saving them to a properly-configured UNIX server. The switch software saves syslog messages in an internal buffer that can store up to 1024 messages. Thus, you can monitor system messages remotely by accessing the switch through Telnet or through the console port, or by viewing the logs on a UNIX server.
Table 10-2 describes the facility types supported by the system message logs.
| Facility Name | Definition |
|---|---|
CDP | Cisco Discovery Protocol |
DTP | Dynamic Trunking Protocol |
EARL | Enhanced Address Recognition Logic |
FILESYS | Flash File System |
GVRP | GARP VLAN Registration Protocol |
IP | Internet Protocol |
KERNEL | Kernel |
MGMT | Management messages |
Mcast | Multicast messages |
PAgP | Port Aggregation Protocol |
PROTFILT | Protocol Filtering |
PRUNING | VLAN Trunking Protocol Pruning |
QOS | Quality of Service |
SNMP | Simple Network Management Protocol |
SPANTREE | Spanning-Tree Protocol |
SYS | System |
TAC | Terminal Access Controller Access Control System |
VTP | VLAN Trunking Protocol |
SECURITY | Port Security |
UDLD | UniDirectional Link Detection Protocol |
Table 10-3 describes the severity levels supported by the system message logs.
| Severity Level | Keyword | Description |
|---|---|---|
0 | emergencies | System unusable |
1 | alerts | Immediate action required |
2 | critical | Critical condition |
3 | errors | Error conditions |
4 | warnings | Warning conditions |
5 | notifications | Normal but significant condition |
6 | informational | Informational messages |
7 | debugging | Debugging messages |
System log messages begin with a percent sign (%) and can contain up to 80 characters. Messages are displayed in the following format:
%TIMESTAMP: FACILITY-SEVERITY: Message-text;
Table 10-4 defines the four elements of syslog messages.
| Element | Description |
TIMESTAMP | Current date and time in the following format: mm/dd/yy,hh:mm:ss. |
FACILITY | Two or more uppercase letters that indicate the facility to which the message refers (for example, SNMP, SYS, etc.). |
SEVERITY | Single-digit code from 0 to 7 that indicates the severity of the message. |
Message-text | Text string containing detailed information about the event being reported. |
These examples show typical system messages:
8/15/1998,13:52:46:SYS-5:Module 1 is online 8/15/1998,13:52:52:SYS-5:Module 5 is online 8/15/1998,13:52:54:SYS-5:Module 3 failed due to CBL0, CBL1, or CBL2 Error 8/15/1998,13:52:54:SYS-5:Module 3 failed configuration
Table 10-5 describes the default system message logging configuration.
| Configuration Parameter | Default Setting |
|---|---|
System message logging to the console | Enabled |
syslog server | None configured |
System message logging to Telnet sessions | Enabled |
Facility/severity level for system messages | dtp/5 |
To change the default system message logging facility and severity settings, perform one of these tasks in privileged mode:
| Task | Command |
|---|---|
| set logging level facility severity |
| set logging console disable |
Before you can send system log messages to a UNIX syslog server, you must configure the syslog daemon on the UNIX server. Log in as root, and perform these steps:
Step 1 Add a line such as the following to the file /etc/syslog.conf:
user.debug/var/log/myfile.log
The switch sends messages according to specified facility types and severity levels. The user keyword specifies the UNIX logging facility used. The messages from the switch are generated by user processes. The debug keyword specifies the severity level of the condition being logged. You can set UNIX systems to receive all messages from the switch.
Step 2 Create the log file by entering these commands at the UNIX shell prompt:
$ touch /var/log/myfile.log $ chmod 666 /var/log/myfile.log
Step 3 Make sure the syslog daemon reads the new changes by entering this command:
$ kill -HUP \Qcat /etc/syslog.pid
Before you can send system log messages to a UNIX syslog server, you must configure the syslog daemon on the UNIX server.
To configure the switch to log messages to a syslog server, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Add a syslog server to the configuration1. | set logging server ip_addr |
Step 2 Enable system message logging to configured syslog servers. | set logging server enable |
Step 3 Set the facility and severity level for syslog server messages. | set logging level facility severity default |
| 1You can configure a maximum of three syslog servers at any time. |
Console> (enable) clear logging server ip_addr
Console> (enable) set logging server disable
By default, Telnet login sessions to the switch are enabled and receive system messages based on the default facility and severity values.
To configure the logging settings for Telnet sessions, perform one of these tasks in privileged mode:
| Task | Command |
|---|---|
| set logging level facility severity |
| set logging session disable or set logging console disable |
| set logging session enable or set logging console enable |
To display the current configuration for system messages, perform this task in privileged mode:
| Task | Command |
|---|---|
Display the current system message log configuration. | show logging |
To display the first N system messages in the internal buffer of the switch, perform this task in privileged mode:
| Task | Command |
|---|---|
Display the first N messages in the buffer. | show logging buffer N |
To display the last N system messages in the internal buffer of the switch, perform this task in privileged mode:
| Task | Command |
|---|---|
Display the last N messages in the buffer. | show logging buffer -N |
To verify the system message log configuration, enter the show logging command. If you are verifying the system message log configuration for the console and the syslog server is disabled, the first two lines of output look as follows:
Console> (enable) show logging Logging console:enabledLogging server:disabled
If you are verifying the system message log configuration for a Telnet login session, an additional line showing the current logging session is displayed as follows:
Console> (enable) show logging Logging console:enabled Logging server:disabled Current Logging Session: enabled
This section provides examples for entering the system message log commands to perform the following tasks:
Console> (enable) set logging server enable System logging messages will be sent to the configured syslog servers.
Console> (enable) set logging server 171.69.192.205 171.69.192.205 added to the System logging server table.
Console> (enable) set logging session enable System logging messages will be sent to the current login session.
Console> (enable) set logging level all 1 default System logging facility <all> set to severity 1(alerts).
Console> (enable) show logging Logging console: enabled Logging server: disabled Current Logging Session: enabled Facility Server/Default Severity Current Session Severity ------------- ----------------------- ------------------------ cdp 1 1 mcast 1 1 dtp 1 1 dvlan 1 1 earl 1 1 fddi 1 1 ip 1 1 pruning 1 1 snmp 1 1 spantree 1 1 sys 1 1 tac 1 1 tcp 1 1 telnet 1 1 tftp 1 1 vtp 1 1 vmps 1 1 kernel 1 1 filesys 1 1 drip 1 1 pagp 1 1 mgmt 1 1 mls 1 1 protfilt 1 1 security 1 1 0(emergencies) 1(alerts) 2(critical) 3(errors) 4(warnings) 5(notifications) 6(information) 7(debugging) Console> (enable)
Console> (enable) set logging level snmp 3 System logging facility <snmp> set to severity 3(errors).
Console> (enable) show logging Logging console: enabled Logging server: disabled Current Logging Session: enabled Facility Server/Default Severity Current Session Severity ------------- ----------------------- ------------------------ cdp 1 1 mcast 1 1 dtp 1 1 dvlan 1 1 earl 1 1 fddi 1 1 ip 1 1 pruning 1 1
snmp 1 3 spantree 1 1 sys 1 1 tac 1 1 tcp 1 1 telnet 1 1 tftp 1 1 vtp 1 1 vmps 1 1 kernel 1 1 filesys 1 1 drip 1 1 pagp 1 1 mgmt 1 1 mls 1 1 protfilt 1 1 security 1 1 0(emergencies) 1(alerts) 2(critical) 3(errors) 4(warnings) 5(notifications) 6(information) 7(debugging) Console> (enable)
Console> (enable) show logging buffer 4 07/30/1998,12:59:24:SYS-5:Module 1 is online 07/30/1998,12:59:32:SYS-5:Module 9 is online 07/30/1998,12:59:35:SYS-5:Module 5 is online 07/30/1998,12:59:49:SYS-5:Module 2 is online Console> (enable)
Console> (enable) show logging buffer -4 07/30/1998,15:44:19:PAGP-5:Port 1/1 joined bridge port 1/1. 07/30/1998,15:46:52:DTP-5:Port 1/1 has become isl trunk 07/30/1998,15:46:52:PAGP-5:Port 1/1 left bridge port 1/1. 07/30/1998,15:47:03:PAGP-5:Port 1/1 joined bridge port 1/1. Console> (enable)
These sections describe how to use Switch TopN Reports utility on the Catalyst 6000 and 6500 series switches:
The Switch TopN Reports utility allows you to collect and analyze data for each physical port on the switch.
The Switch TopN Reports utility collects the following data for each physical port:
When the Switch TopN Reports utility starts, it gathers data from the appropriate hardware counters and then goes into sleep mode for a user-specified period of time. When the sleep time ends, the utility gathers the current data from the same hardware counters, compares the current data from the earlier data, and stores the difference. The data for each port is sorted using a user-specified metric chosen from the values shown in Table 10-6.
| Metric Value | Definition |
|---|---|
util | Utilization |
bytes | Input/output bytes |
pkts | Input/output packets |
bcst | Input/output broadcast packets |
mcst | Input/output multicast packets |
errors | Input errors |
overflow | Buffer overflows |
If you enter the show top command without specifying the background option, processing begins but the system prompt does not reappear on the screen and you cannot enter other commands while the report is being generated.
You can terminate the Switch TopN process before it finishes by pressing Ctrl-C from the same console or Telnet session, or by opening a separate console or Telnet session and entering the clear top [report_num] command. After the Switch TopN Reports utility finishes processing the data, it displays the output on the screen immediately. The output is not saved.
If you enter the show top command and specify the background option, processing begins and the system prompt reappears immediately. When processing completes, Switch TopN reports do not display immediately on the screen, but are saved for later viewing.
The switch notifies you when the Switch TopN reports are complete by sending a syslog message to the screen. Enter the show top report [report_num] command to view the completed Switch TopN reports. The switch displays only those reports that are completed. For reports that are not completed, the switch displays a short description of the Switch TopN process information.
You can terminate a Switch TopN process invoked with the background option only by entering the clear top [report_num] command. Pressing Ctrl-C does not terminate the process. Completed Switch TopN reports remain available for viewing until you remove them using the clear top {all | report_num} command.
To start the Switch TopN Report utility in the background and view the results, perform this task in privileged mode:
| Task | Command |
|---|---|
Step 1 Start the Switch TopN Reports utility in the background. | show top [N] [metric] [interval interval] [port_type] background |
Step 2 View the generated report when it is complete. | show top report [report_num] |
If you specify the report_num with the show top report command, the associated Switch TopN report is displayed. Each process is associated with a unique report number.
If you do not specify the report_num variable, all active Switch TopN processes and all available Switch TopN reports for the switch are displayed. All Switch TopN processes (both with and without the background option) are shown in the list.
This example shows how to start the Switch TopN Reports utility with the background option:
Console> (enable) show top 5 pkts background
Console> (enable) 06/16/1998,17:21:08:MGMT-5:TopN report 4 started by Console//.
Console> (enable) 06/16/1998,17:21:39:MGMT-5:TopN report 4 available.
Console> (enable) show top report 4
Start Time: 06/16/1998,17:21:08
End Time: 06/16/1998,17:21:39
PortType: all
Metric: pkts (Tx + Rx)
Port Band- Uti Bytes Pkts Bcst Mcst Error Over
width % (Tx + Rx) (Tx + Rx) (Tx + Rx) (Tx + Rx) (Rx) flow
----- ----- --- -------------------- ---------- ---------- ---------- ----- ----
1/1 100 0 7950 81 0 81 0 0
2/1 100 0 2244 29 0 23 0 0
1/2 100 0 1548 12 0 12 0 0
2/10 100 0 0 0 0 0 0 0
2/9 100 0 0 0 0 0 0 0
Console> (enable)
To start the Switch TopN Report utility in the foreground and view the results immediately, perform this task in privileged mode:
| Task | Command |
|---|---|
Start the Switch TopN Reports utility in the foreground. | show top [N] [metric] [interval interval] [port_type] |
This example shows how to start the Switch TopN Reports utility in the foreground:
Console> (enable) show top 5 pkts
Start Time: 06/16/1998,17:26:38
End Time: 06/16/1998,17:27:09
PortType: all
Metric: pkts (Tx + Rx)
Port Band- Uti Bytes Pkts Bcst Mcst Error Over
width % (Tx + Rx) (Tx + Rx) (Tx + Rx) (Tx + Rx) (Rx) flow
----- ----- --- -------------------- ---------- ---------- ---------- ----- ----
2/1 100 0 10838 94 2 26 0 0
1/1 100 0 7504 79 0 79 0 0
1/2 100 0 2622 21 0 21 0 0
2/10 100 0 0 0 0 0 0 0
2/9 100 0 0 0 0 0 0 0
Console> (enable)
To display stored and pending Switch TopN reports, perform this task in privileged mode:
| Task | Command |
|---|---|
Display a Switch TopN report. To display all stored and pending reports, do not specify a report_num. | show top report [report_num] |
This example shows how to display a specific report and how to display all stored and pending reports:
Console> (enable) show top report 5
Start Time: 06/16/1998,17:29:40
End Time: 06/16/1998,17:30:11
PortType: all
Metric: overflow
Port Band- Uti Bytes Pkts Bcst Mcst Error Over
width % (Tx + Rx) (Tx + Rx) (Tx + Rx) (Tx + Rx) (Rx) flow
----- ----- --- -------------------- ---------- ---------- ---------- ----- ----
1/1 100 0 7880 83 0 83 0 0
2/12 100 0 0 0 0 0 0 0
2/11 100 0 0 0 0 0 0 0
2/10 100 0 0 0 0 0 0 0
2/9 100 0 0 0 0 0 0 0
Console> (enable) show top report
Rpt Start time Int N Metric Status Owner (type/machine/user)
--- ------------------- --- --- ---------- -------- -------------------------
1 06/16/1998,17:05:00 30 20 Util done telnet/172.16.52.3/
2 06/16/1998,17:05:59 30 5 Util done telnet/172.16.52.3/
3 06/16/1998,17:08:06 30 5 Pkts done telnet/172.16.52.3/
4 06/16/1998,17:21:08 30 5 Pkts done Console//
5 06/16/1998,17:29:40 30 5 Overflow pending Console//
Console> (enable)
To remove stored reports, perform this task in privileged mode:
| Task | Command |
|---|---|
Remove Switch TopN reports. Use the all keyword to remove all completed Switch TopN reports. | clear top {all | report_num} |
This example shows how to remove a specific Switch TopN report and how to remove all stored reports:
Console> (enable) clear top 4 Console> (enable) 06/16/1998,17:36:45:MGMT-5:TopN report 4 killed by Console//. Console> (enable) clear top all 06/16/1998,17:36:52:MGMT-5:TopN report 1 killed by Console//. 06/16/1998,17:36:52:MGMT-5:TopN report 2 killed by Console//. Console> (enable) 06/16/1998,17:36:52:MGMT-5:TopN report 3 killed by Console//. 06/16/1998,17:36:52:MGMT-5:TopN report 5 killed by Console//. Console> (enable)
Posted: Thu Apr 8 14:25:32 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.