-
Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.1
-
Table of Contents
-
About the Cisco IOS Documentation Set
-
Configuration Fundamentals Overview
- Part 1: Cisco IOS User Interfaces
- Part 2: Cisco IOS File Management
-
Part 3: Cisco IOS System Management
-
Configuring SNMP Support
-
Configuring RMON Support
-
Configuring Cisco Discovery Protocol (CDP)
-
Network Monitoring Using Cisco Service Assurance Agent (SAA)
-
Troubleshooting the Router
-
Performing Basic System Management
-
System Management Using System Controllers
-
Configuring Web Cache Services Using WCCP
-
Managing Dial Shelves
-
-
Appendix: Cisco IOS Command Modes
-
Index: Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.1
-
Table Of Contents
System Management Using System Controllers
System Controller Configuration Task List
Configuring Shelf Discovery and Autoconfiguration
Shelf Discovery and Autoconfiguration Task List
Configure the System Controller
Configuring the Virtual Console Feature
Using the Virtual Console Feature
Configuring the Health Monitor Feature
Configuring Performance Data Collection
Performance Data Collection Task List
Configure Performance Data Collection on the System Controller
Configuring Syslog Disk Logging
Creating the Syslog-Server Subfiles
Configuring the FTP Server Feature
System Controller and Managed Shelves Examples
Shelf Discovery and Autoconfiguration Examples
Performance Data Collection Examples
System Management Using System Controllers
The SC3640 System Controller runs Cisco IOS software and is designed to monitor and control up to seven Cisco AS5800 access servers (approximately 5000 ports) at a single location. The system controller can be installed at a remote facility so users can access multiple systems through a console port or Web interface. System administrators can download software configurations to any Cisco universal access server using Simple Network Management Protocol (SNMP) or Telnet. The system controller monitors Cisco equipment to provide performance data collection, accounting data collection, and logging.
For a complete description of the system controller and managed shelves commands in this chapter, refer to the "System Controller and Managed Shelves Commands" chapter of the Cisco IOS Configuration Fundamentals Configuration Command Reference. To locate documentation of other commands that appear in this chapter, use the command reference master index or search online. For an overview of the SC3640 System Controller, see the "Cisco SC3640 System Controller" document on CCO at http://www.cisco.com/warp/public/cc/pd/as/as5800/prodlit/3640_ov.htm. For additional hardware configuration details, see the Cisco SC3640 System Controller ICG at http://www.cisco.com/univercd/cc/td/doc/product/access/acs_serv/as5800/sc3600dx/3640icg .
System Controller Configuration Task List
To configure the system controller and managed shelves, complete the tasks in the following sections:
•
Configuring Shelf Discovery and Autoconfiguration
•
•
•
•
•
See the end of this chapter for "System Controller and Managed Shelves Examples."
Configuring Shelf Discovery and Autoconfiguration
The Shelf Discovery and Autoconfiguration feature allows a system controller to automatically discover new shelves and properly configure them to interact with the system controller. The system controller communicates with its managed shelves through the Shelf Discovery Protocol (SDP), which runs on top of UDP.
The Shelf Discovery and Autoconfiguration features provide the following benefits:
•
•
•
When the system controller detects that a shelf has been added or reloaded, it sends the following configuration commands to the shelf:
•
–
–
–
•
–
–
–
•
–
–
Shelf Discovery and Autoconfiguration Task List
For a system controller to automatically discover and configure a shelf, both the system controller and the managed shelf must be configured. Perform the tasks described in the following sections:
•
Once you have configured the Shelf Discovery and Autoconfiguration feature on the system controller and managed shelves, you can increase the functionality of the system controller by configuring these additional features:
•
•
•
•
•
Later sections in this chapter describe how to configure or use these features.
Configure the Shelf
To configure the shelf to use the system controller, use the following commands in global configuration mode:
To monitor the SDP process, use the show syscon sdp and debug syscon sdp commands.
Configure the System Controller
To configure the system controller, use the following commands in global configuration mode:
Use the following commands to monitor SDP events and status:
show syscon discover [brief | full]
Display information about managed shelves.
show syscon sdp
Display information about SDP.
debug syscon sdp
Debug SDP.
Configuring the Virtual Console Feature
The Virtual Console feature allows you to access dial and router shelves connected to a system controller. During a system controller session, you can connect to a router or dial shelf at the same privilege level as the current system controller session. By entering one command, you can Telnet directly to a shelf, provide a username and password, and then go to the same privilege level as the system controller.
The Virtual Console feature allows you to connect to all managed shelves through one session and switch between sessions easily. You do not have to reenable privileged EXEC mode every time you switch to another shelf session.
This feature is useful when you need to do quick tasks on different managed shelves.
The Virtual Console feature has the following security aspects:
•
•
•
To use the Virtual Console feature, you must first configure the Shelf Discovery and Autoconfiguration feature. Refer to the "Configuring Shelf Discovery and Autoconfiguration"section for these tasks.
To use the Virtual Console feature, complete the tasks in the section that follows.
Using the Virtual Console Feature
To use the virtual console feature, use the following command beginning in user EXEC or privileged EXEC mode:
attach shelf shelf-id
On the system controller, connect to the managed shelf.
Enter commands on the managed shelf.
You are connected to the managed system until one of the following occurs:
•
•
•
•
In every case except the first, control is returned to the system controller. In the first case, the connection to the current shelf is closed and a new connection to the specified shelf is opened.
Configuring the Health Monitor Feature
The Health Monitor feature monitors key performance attributes of the shelves managed by the system controller.
The Health Monitor feature continually polls its managed shelves to obtain the information stored in the Health Monitor MIB. Management stations collect information for all the shelves from the system controller rather than by polling each shelf individually.
In addition, you can configure specific performance thresholds for all managed shelves through simple commands on the system controller. The system controller uses SNMP to automatically configure the following on each managed shelf:
•
•
•
When threshold traps are received by the system controller, they are converted to Health Monitor traps and sent to trap destinations configured in the system controller.
The Health Monitor feature provides the following benefits:
•
•
Health Monitor Task List
To use this feature, you must first configure the Shelf Discovery and Autoconfiguration feature. Refer to the "Configuring Shelf Discovery and Autoconfiguration" section for these tasks.
In addition, the SNMP Manager feature should be configured on the system controller. Use the snmp-server manager command to enable this feature. For details, see the "Configuring the Router as an SNMP Manager" section in the "Monitoring the Router and Network" chapter of this book.
To configure the Health Monitor feature, complete the tasks in the following sections:
Using the Health Monitor
When the Shelf Discovery and Autoconfiguration feature is enabled, the system controller automatically polls its managed shelves for Health Monitor MIB data. The system controller polls all the discovered shelves once a minute to obtain this data. Use the show syscon mibpoll EXEC command to display the current Health Monitor MIB data.
Optionally, you can configure the managed shelves to monitor certain attributes and notify the system controller when the attribute thresholds are exceeded, as described in the following section.
Monitoring Shelf Attributes
To configure monitored attributes for the managed shelves, use the following commands in global configuration mode on the system controller:
The Health Monitor MIB traps sent by the system controller are more readable than the traps sent to the system controller from the managed shelves. To send Health Monitor MIB traps to a management station, you should configure the syscon monitor traps command, the snmp-server enable traps command, and the appropriate snmp-server host command.
To view the status of the monitoring process, use the show syscon monitor EXEC command.
Supported MIBs and RFCs
This feature implements the Health Monitor MIB and utilizes MIB2 and POP-MGMT-MIB on the managed shelves.
Configuring Performance Data Collection
The Performance Data Collection feature allows a Cisco 3640 system controller to collect and store SNMP MIB data from its managed router and dial shelves. The system controller then serves as a central point for network management data collection.
The system controller collects the raw data from the managed shelves periodically, saves the data, and provides a single access point for a central network management application. The data can then be uploaded to a network management station using FTP or TFTP.
Performance data is stored on a disk local to the system controller. The files are located at disk0:/performance/shelf-shelfid/pollgroupname.unixtimestamp. A new file is created each time the system controller collects data from a shelf.
The Performance Data Collection feature provides the following benefits:
•
•
Performance Data Collection Task List
To use this feature, you must first configure the following features:
•
•
•
In addition, the system clock should be set to the current time before the data collection starts. For system clock configuration details, see the "Performing Basic System Management" chapter in this book. Network Time Protocol (NTP) is the recommended method for obtaining the time.
To configure and use the Performance Data Collection feature, complete the tasks in the following sections:
•
Configure Performance Data Collection on the System Controller
To configure Performance Data Collection on the system controller, use the following commands beginning in global configuration mode:
Configure the system controller to collect all the MIB variables that your network management station uses. Thus, the network management station can obtain all the information from the system controller without ever polling a managed shelf.
What to Do Next
After the system controller has collected the data, you must copy data from the system controller's disk (via FTP or TFTP) to the network management station. Use the poll-interval and samples commands to determine how long the data is stored on the disk before it is erased.
Configuring Syslog Disk Logging
The Syslog Disk Logging feature allows you to collect, store, and retrieve all managed shelf syslog (system log) messages through the system controller. The system controller receives syslog messages from managed shelves and stores these messages in subfiles on its disk.
Each syslog message stored in a subfile contains the following information:
•
•
•
•
•
In addition, this feature provides an enhanced method of viewing messages in the logging history table. Messages can be displayed based on host IP address, time received, and order received.
The Syslog Disk Logging feature provides the following benefits:
•
•
•
•
Subfiles
Subfiles provide additional storage space for syslog messages. They contain the large logging history tables and preserve the tables even when the machine is reloaded.
The system controller creates subfiles using the same name as the root and a different extension for each subfile:
•
•
•
•
The file space is preallocated before any messages are received to provide deterministic disk space allocation. When the system controller receives a new syslog message, the following events occur:
•
•
•
–
–
–
Syslog Disk Logging Task List
To use this feature, you must first configure the Shelf Discovery and Autoconfiguration feature, which automatically configures the managed shelves to send syslog messages to the system controller. In addition, the service timestamp log datetime command is configured on all the shelves. Refer to the "Configuring Shelf Discovery and Autoconfiguration" section for these tasks.
If you want messages generated by the system controller to be stored in the subfiles along with messages received from managed shelves, configure the system controller as the syslog server for its own messages using the logging host command.
To enable and use the Syslog Disk Logging feature, perform the following tasks:
•
Creating the Syslog-Server Subfiles
Normally, the system controller just stores messages in the logging history table. However, to store a larger number of messages and preserve the messages across reboots of the machine, you need to create syslog server subfiles. To create these subfiles, use the following commands in global configuration mode:
logging syslog-server size number dir-name
Creates the syslog-server subfiles.
dir disk0:
Verifies that the files have been created.
A typical subfile configuration is five subfiles with a size of 500 KB. This configuration stores significant volumes of syslog data but still allows efficient searching. If the subfiles are too large or numerous, the show syslog-server command might be slow.
Displaying Syslog Messages
To view syslog messages stored in subfiles, use the following command in EXEC mode:
show syslog-server [last number | since [date] hh:mm:ss] [source ip-address]
Displays syslog messages.
Configuring the FTP Server Feature
The FTP Server feature configures a router to act as an FTP server. FTP clients can copy files to and from certain directories on the router. In addition, the router can perform many other standard FTP server functions. For example, the FTP Server allows you to retrieve files, such as syslog files, from the disk file system on the router.
Supported FTP Commands
When the router receives a request for an FTP connection, the FTP Server process is started. The FTP Server prompts for a username and password.
After you supply a valid username and password, you can enter various commands. Not all FTP commands are supported by this FTP Server implementation. The FTP Server responds to the following FTP client commands:
Refer to the documentation for your FTP client for detailed information on these commands. For example, if you are using a UNIX workstation as the FTP client, enter the man ftp command for descriptions of these commands.
To use the FTP Server feature, complete the task in the section that follows.
Enabling the FTP Server
To enable the FTP Server, use the following commands in global configuration mode:
ftp-server enable
Enables the FTP Server.
ftp-server topdir directory
Restricts the region where the FTP clients can read or write files.
System Controller and Managed Shelves Examples
The following sections provide system controller and managed shelves examples:
•
•
Shelf Discovery and Autoconfiguration Examples
The following sample configuration enables a device to begin serving as a system controller. The system controller waits to be contacted by shelves and then provides them with the appropriate configuration.
syscon password syspasswordsyscon community publicThe follow example configures a shelf to use the system controller at 172.23.66.111. The shelf ID is 99. If you are using a Cisco AS5800, you do not need to specify a shelf ID with the syscon shelf-id command.
syscon address 172.23.66.111 syspasswordsyscon shelf-id 99After the shelf has contacted the system controller through SDP, the system controller configures the managed shelf with the following commands:
snmp-server community public RWsnmp-server enable trapssnmp-server host 172.23.66.111 traps version 2c publicsnmp-server packetsize 1480ntp server 172.23.66.111ntp update-calendarservice timestamps log datetime mseclogging 172.23.66.111logging trapThe following sample debug syscon sdp output on the managed shelf shows the shelf contacting the system controller. The shelf sends a Hello packet to the system controller at 172.23.66.111. The system controller responds with the autoconfiguration commands. The remaining lines show the Hello packets exchanged between the shelf and the system controller.
Shelf# debug syscon sdpSYSCTLR: Hello packet sent to the SYSCTLR at 172.23.66.111SYSCTLR: Command packet received from SYSCTLRFeb 24 17:24:16.713: %SHELF-6-SYSCTLR_ESTABLISHED: Configured via system controller located at 172.23.66.111SYSCTLR: Rcvd HELLO from SYSCTLR at 172.23.66.111SYSCTLR: Hello packet sent to the SYSCTLR at 172.23.66.111SYSCTLR: Rcvd HELLO from SYSCTLR at 172.23.66.111The following sample debug syscon sdp output on the system controller shows the system controller discovering the managed shelf. In the first few lines, the system controller receives a Hello packet from shelf 99 at 172.23.66.106. The system controller responds with a Hello packet. When the shelf sends another Hello packet, the system controller resets the timer and sends another packet.
Syscon# debug syscon sdpSYSCTLR: Hello packet received via UDP from 172.23.66.106%SYSCTLR-6-SHELF_ADD: Shelf 99 discovered located at address 172.23.66.106Hello packet sent to the RS located at 172.23.66.106SYSCTLR: Hello packet received via UDP from 172.23.66.106Timer for shelf 99 updated, shelf is aliveHello packet sent to the RS located at 172.23.66.106Virtual Console Examples
In the following example, a user connects to a managed shelf from the system controller from user EXEC and privileged EXEC modes. Notice that the user connects to the shelf at the current user privilege level.
systemcont> show sysconShelf# 2 172.23.66.102 SDB update 09:09:16 PST Jan 27 1998systemcont> attach shelf 2Trying 172.23.66.102 ... Openshelf2> show sysconCurrent uptime 09:10:00 PST Jan 27 1998, system controller 172.23.66.100Last hello packet received at 09:09:16 PST Jan 27 19988625 Total SDP packets0 packets with bad MD5 hash4311 Hello packets received4314 Hello packets sent0 Command packets received0 Command packets sentshelf2> quit[Connection to 172.23.66.102 closed by foreign host]systemcont> enablePassword:systemcont# attach shelf 2Trying 172.23.66.102 ... Openshelf2# show syscon sdpCurrent uptime 09:10:45 PST Jan 27 1998, system controller 172.23.66.100Last hello packet received at 09:10:14 PST Jan 27 19988627 Total SDP packets0 packets with bad MD5 hash4312 Hello packets received4315 Hello packets sent0 Command packets received0 Command packets sentshelf2# exit[Connection to 172.23.66.102 closed by foreign host]systemcont#Health Monitor Examples
The following system controller sample configuration monitors three attributes and forwards traps to myhost.cisco.com.
! The following commands are configured as part of the Shelf Discovery and! Autoconfiguration feature.!syscon password syspasswordsyscon community syscommunity!! The following lines configure the shelves to monitor IO memory on all the shelves and! total modem and trunk utilization.! If IO memory utilization exceeds 10%, the shelf sends a trap to the system controller.! If the total utilization of all modems or trunk on all shelves exceeds 5%, the system! controller generates a trap.!syscon monitor modem 5syscon monitor trunk 5syscon monitor io-mem 10!! The following commands enable forwarding of traps. When the system controller receives! a trap from a managed shelf or generates one itself, it forwards the trap to the host! called myhost using the community string public.!syscon monitor trapssnmp-server host myhost.cisco.com publicsnmp-server enable traps!! The following line enables the SNMP manager process.!snmp-server managerYou can view the current configuration of Health Monitor on the system controller with the show syscon monitor command.
nnm3640-2# show syscon monitorHealth Monitor setup status on the shel(f,ves):Shelf# Shelf IP Address Monitoring Type Threshold Value Status3 172.23.66.109 IO-Mem 10 ActiveHealth Monitor setup status on the system controller:Monitoring Type Threshold Value StatusTrunk 5 ActiveModem 5 ActiveThe system will automatically configure each shelf to monitor its IO memory utilization. You can check the RMON configuration using the show rmon alarms and show rmon events commands on a managed shelf.
nnm7206-6# show rmon alarmsAlarm 596 is active, owned by IOMemMonitors ciscoExperiment.22.1.4.1.1.2.1.0.0.0 every 120 second(s)Taking absolute samples, last value was 66Rising threshold is 10, assigned to event 514Falling threshold is 0, assigned to event 0On startup enable rising or falling alarmnnm7206-6# show rmon eventsEvent 514 is active, owned by IOMemDescription is Send snmp trap to health_monitorEvent firing causes trap to community syscommunity, last fired 00:04:02Performance Data Collection Examples
The following partial sample configuration file configures Performance Data Collection on a system controller:
! Enable the FTP Server on the system controller and specify the top-level directory! for FTP operations.!ftp-server enableftp-server topdir disk0:/performance!! Configure the device to act as a system controller and specify the passwords.!syscon password semtestsyscon community private!! Configure and enable the different poll groups.!syscon poll-group popmgmtoid cpmDS0Usage.1.*oid cpmActiveCallSummary.1.*oid cpmCallHistorySummary.3.*transfer-mode bulkpoll-interval 25samples 5enablesyscon poll-group cmlineinfooid cmLineInfo.1.*oid cmLineInfo.2.*oid cmLineInfo.3.*oid cmLineInfo.4.*transfer-mode bulkpoll-interval 20samples 5enablesyscon poll-group cpmds0usageoid cpmDS0Usage.2.0oid cpmDS0Usage.3.0oid cpmDS0Usage.4.0oid cpmDS0Usage.5.0oid cpmDS0Usage.6.0oid cpmDS0Usage.7.0transfer-mode pollpoll-interval 15samples 10enablesyscon poll-group callfailureoid cpmCallFailure.1.0oid cpmCallFailure.2.0oid cpmCallFailure.3.0oid cpmCallFailure.4.0oid cpmCallFailure.5.0oid cpmCallFailure.6.0oid cpmCallHistorySummary.1.0oid cpmCallHistorySummary.2.0transfer-mode pollpoll-interval 20samples 10enablesyscon poll-group cmsysteminfooid cmSystemInfo.1.0oid cmSystemInfo.2.0oid cmSystemInfo.3.0oid cmSystemInfo.4.0oid cmSystemInfo.5.0oid cmSystemInfo.6.0oid cmSystemInfo.7.0oid cmSystemInfo.8.0oid cmSystemInfo.9.0oid cmSystemInfo.10.0transfer-mode pollpoll-interval 25shelf-type 108samples 12enablesyscon poll-group iftableoid ifEntry.3.*oid ifEntry.4.*oid ifEntry.5.*oid ifEntry.8.*transfer-mode pollpoll-interval 20samples 10enableThe following show syscon perfdata output indicates that the system controller is collecting data from shelf 0:
SysCont# show syscon perfdataPerformance Data Collection:Poll Last Total Get GetBulk Bulk XferShelf# Group File Requests Requests Requests Requests Errors0 popmgmt 891873300 5 0 0 5 0cmlineinfo 891873600 5 0 0 5 0cpmds0usage 891873000 1 1 0 0 0callfailure 891873600 1 1 0 0 0cmsysteminfo 891873300 1 1 0 0 0iftable 891873647 651 1 650 0 0Use the dir command to view the data sets. Note that the file extension corresponds to the "Last File" time in the show syscon perfdata command.
SysCont# dir disk0:/performance/shelf-0Directory of disk0:/performance/shelf-0/128 -rw- 238 Apr 06 1998 14:29:59 cpmds0usage.891873000192 -rw- 402 Apr 06 1998 14:34:59 cmsysteminfo.891873300194 -rw- 385 Apr 06 1998 14:39:59 callfailure.891873600196 -rw- 119967 Apr 06 1998 14:40:59 iftable.891873647219791360 bytes total (218087424 bytes free)You can watch the details of the data collection using the debug syscon perfdata command:
SysCont# debug syscon perfdataPERF: Start 'cmlineinfo' timer, next cycle in 5 mins, 31 secsPERF: Timer event: 'popmgmt', 15 minutesPERF: Bulk file create: 'popmgmt', shelf 0, pc 60ACBB10PERF: SNMP resp: Type 4, 'popmgmt', shelf 0, error_st 0PERF: FTP transfer: 'popmgmt', shelf 0, pc 60ACBB10PERF: SNMP resp: Type 5, 'popmgmt', shelf 0, error_st 0PERF: Deleted disk0:/performance/shelf-0/popmgmt.891809700PERF: Timer event: 'cpmds0usage', 15 minutesPERF: Polling 'cpmds0usage', shelf 0, pc 60ADE004PERF: SNMP resp: Type 6, 'cpmds0usage', shelf 0, error_st 0PERF: Logged polled data to disk0:/performance/shelf-0/cpmds0usage.891873900PERF: Timer event: 'iftable', 12 minutesPERF: Bulk file create: 'iftable', shelf 0, pc 60BE16ACPERF: SNMP resp: Type 4, 'iftable', shelf 0, error_st 0PERF: FTP transfer: 'iftable', shelf 0, pc 60BE16ACPERF: SNMP resp: Type 5, 'iftable', shelf 0, error_st 0PERF: Deleted disk0:/performance/shelf-0/iftable.891883559Syslog Disk Logging Examples
The following example creates five subfiles. Each subfile has a maximum size of 2000 KB; thus, the total available size is 10000 KB. The subfiles are named mysyslog.cur, mysyslog.1, mysyslog.2, mysyslog.3, and mysyslog.4.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# logging syslog-server 2000 5 mysyslogRouter(config)# end%SYS-5-CONFIG_I: Configured from console by consoleRouter# dir disk0:Directory of disk0:/3 drw- 0 Jan 17 1998 07:03:53 syslogd.dir4 drw- 0 Jan 12 1998 11:02:29 performance12 drw- 0 Jan 12 1998 11:56:37 configs242 drw- 0 Jan 21 1998 17:51:29 mysyslog.dir340492288 bytes total (336560128 bytes free)Router# dir disk0:/mysyslog.dirDirectory of disk0:/mysyslog.dir/0 -rw- 0 Jan 21 1998 17:51:29 mysyslog.10 -rw- 0 Jan 21 1998 17:51:29 mysyslog.20 -rw- 0 Jan 21 1998 17:51:29 mysyslog.30 -rw- 0 Jan 21 1998 17:51:31 mysyslog.40 -rw- 0 Jan 21 1998 17:51:31 mysyslog.cur340492288 bytes total (336560128 bytes free)FTP Server Examples
The following example enables the FTP Server and limits client access to the syslogd.dir directory on disk0:
ftp-server enableftp-server topdir disk0:/syslogd.dirAfter these commands have been entered, you can FTP to the router. In the following example, a user connects to the router and gets the file syslogd.1. Notice that the user starts in the directory specified by the ftp-server topdir command.
FTPclient% ftp FTProuterConnected to FTProuter.cisco.com.220 FTProuter IOS-FTP server (version 1.00) ready.Name (FTProuter:me): aa331 Password required for 'aa'.Password:230 Logged in.Remote system type is Cisco.ftp> pwd257 "disk0:/syslogd.dir/" is current directory.ftp> dir200 PORT command successful.150 Opening ASCII mode data connection for file list.syslogd.1syslogd.2syslogd.3syslogd.4syslogd.5syslogd.6syslogd.7syslogd.8syslogd.9syslogd.cur226 Transfer complete.ftp> bin200 Type set to I.ftp> get syslogd.1200 PORT command successful.150 Opening BINARY mode data connection for syslogd.1 (607317 bytes).226 Transfer complete.607317 bytes received in 7.7 seconds (77 Kbytes/s)ftp>Use the debug ftpserver command to observe the process on the router.