Download
Share
Print this page
  1. Manuals
  2. Brands
  3. Cisco Manuals
  4. Network Router
  5. Dial NMS
  6. Implementation manual

Cisco Dial NMS Implementation Manual

Cisco systems basic dial nms implementation guide
Hide thumbs

Advertisement

Quick Links

Download this manual

Advertisement

loading

Related Manuals for Cisco Dial NMS

Summary of Contents for Cisco Dial NMS

  • Page 2 FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company.
  • Page 3 C O N T E N T S...
  • Page 5 I N D E X...
  • Page 7 (NMS) that provides management functions for a dial Internet access service (DIAS). This guide is intended for network engineers and operators who implement and operate dial NMS systems. This guide assumes that you have the following level of knowledge and experience: An understanding of NMS protocols, such as Simple Network Management Protocol (SNMP), Network Time Protocol (NTP), and syslog.
  • Page 8 This guide describes the following network protocols, functions, and NMS applications: Protocols—SNMP and NTP. Functions—Syslog, modem call records, Cisco IOS command-line interface (CLI), Log File Rotator, Device Navigator, web-based management, and War Dialer. NMS applications—UCD-SNMP, Multi Router Traffic Grapher (MRTG), HP OpenView (HPOV), and CiscoWorks 2000 Resource Manager Essentials (CW2000 RME).
  • Page 9 Center of Excellence Internet Access Engineering—A site dedicated to developing lightweight tools and techniques for supporting the implementation and operation of Internet access services. This site is an educational endeavor of the University of Texas at Austin and Cisco Systems, Inc. http://mccain.ots.utexas.edu/index.html Wholesale Dial Resources—Provides links to technical documents related to wholesale dial...
  • Page 10 Access Technology Software Center—Provides the firmware for modem upgrades. http://www.cisco.com/kobayashi/sw-center/sw-access.shtml Increasing Security on IP Networks—Addresses network-layer security issues. http://www.cisco.com/univercd/cc/td/doc/cisintwk/ics/cs003.htm Carnegie Mellon CERT® Security Improvement Modules—Provides information about security management. http://www.cert.org/security-improvement/ Cisco AS5x00 Case Study for Basic IP Modem Services—Describes how to configure, verify, and troubleshoot basic IP modem services.
  • Page 11 CiscoWorks 2000 Documentation Set—A collection of configuration guides and reference manuals. http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/index.htm Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services. Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners.
  • Page 12 Cisco documentation and additional literature are available in a CD-ROM package that ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service.
  • Page 13 SNMP Version 3 (SNMPv3)—SNMPv3 has yet to be standardized. The case study in this guide describes how to create a dial NMS environment. To successfully manage the environment, you must be familiar with the SNMP feature set. The following NMS applications use...
  • Page 14 SNMP Technology TAC Page—Network design tips, implementation and operation guidelines, which are continually updated by Cisco TAC engineers. The SimpleWeb—Public domain software packages, which are available on the Internet. Most of the software is a spin-off from SNMP related research. SNMP FAQ—Frequently asked questions about SNMP.
  • Page 15 Figure 1 illustrates the relationship between the managed devices, the agent, and the NMS. Management Entity Agent Agent Management Management Database Database Managed Devices There are three basic SNMP message types: Get—NMS-initiated requests used by an NMS to monitor managed devices. The NMS examines different variables that are maintained by managed devices.
  • Page 16 Get request Response Get next Response Get next Response Trap (agent initiated) Agent (Cisco IOS device) A Management Information Base (MIB): Presents a collection of information that is organized hierarchically. Is accessed by using a network-management protocol, such as SNMP. References managed objects and object identifiers.
  • Page 17 ccitt (0) … standard (0) registration- authority (1) directory (1) mgmt (2) experimental (3) … mib-2 (1) … … … … … DECnet (1) XNS (2) Apple Talk (3) … … … … As shown in Figure 3, top-level MIB object IDs belong to different standards organizations while low-level object IDs are allocated by associated organizations.
  • Page 18 SNMP must account for and adjust to incompatibilities between managed devices. Different computers use different data-representation techniques, which can compromise the ability of SNMP to exchange information between managed devices. SNMPv1 is the initial implementation of the SNMP protocol and is described in RFC 1157 (http://www.ietf.org/rfc/rfc1157).
  • Page 19 Application-wide data types—Including these seven types: Network addresses—Represent addresses from a protocol family. SNMPv1 supports only 32-bit IP addresses. Counters—Nonnegative integers that increase until they reach a maximum value; then, the integers return to zero. In SNMPv1, a 32-bit counter size is specified. Gauges—Nonnegative integers that can increase or decrease but retain the maximum value reached.
  • Page 20 The SMI defines the rules for describing management information by using ASN.1. RFC 1902 (http://www.ietf.org/rfc/rfc1902) describes the SNMPv2 SMI and enhances the SNMPv1 SMI-specific data types by including: Bit strings—Comprise zero or more named bits that specify a value. Network addresses—Represent an address from a protocol family. SNMPv1 supports 32-bit IP addresses, but SNMPv2 can support other types of addresses too.
  • Page 21 SNMP lacks authentication capabilities, which results in a variety of security threats: Masquerading—An unauthorized entity attempting to perform management operations by assuming the identity of an authorized management entity. Modification of information—An unauthorized entity attempting to alter a message generated by an authorized entity, so the message results in unauthorized accounting management or configuration management operations.
  • Page 23 How to implement dial NMS protocols, applications, and other utilities. THEnet is an ISP in Austin, Texas that wants to develop a dial NMS and integrate it with its existing Network Operations Center (NOC). THEnet has two dial point-of-presences (POPs) that provide...
  • Page 24 Describing how traffic is re-routed is outside the scope of this case study, and the diagrams in the case study show simplified IP paths only. THEnet uses this model to identify the different functional areas of the dial NMS: F = Fault management...
  • Page 25 This planning questionnaire describes information that is essential for creating a dial NMS service definition. A questionnaire helps network engineers make accurate design decisions and consider alternative solutions. The network engineers at THEnet answered the design questions as shown in Table 2.
  • Page 26 What security protocols do you use for authentication, authorization, and accounting (AAA)? What dial NMS freeware do you plan to use? What software tools do you plan to develop internally? Do you plan to build and maintain customized scripts?
  • Page 27 A service definition is a statement that describes required services for a network design. The dial NMS service definition determined for THEnet is based on: The answers provided in Table 2 The FCAPS model Fault management Configuration management Accounting management...
  • Page 28 Configuration SNMP—Use CW2000 RME to archive configuration files, manage management Cisco IOS images, determine how much memory is installed, and discover which boot ROMs are present. CLI—Inspect and modify Cisco IOS configuration files and images. For example, use the following commands: show version show running show modem version...
  • Page 29 Performance SNMP—For the initial installation, use MRTG to monitor key Object management Identifications (OIDs) in the device MIBs. In the future, use commercial software applications that collect mass scale management data streams for large numbers of access servers. CLI—Monitor the performance of the access servers. For example, use the following commands: show modem operational-status show modem connect-speeds...
  • Page 30 Based on the dial NMS service definition in Table 3, the network engineers at THEnet defined the network topology for the POPs and NOC. Cisco AS5800 access servers Control Data An intranet WAN connects the two POPs together and routes traffic to the Internet. The NOC collects management data from both POPs.
  • Page 31 Collecting syslog locally in each POP is a future design consideration. To design the dial NMS for the two POPs and the NOC, the network engineers at THEnet defined these hardware requirements:...
  • Page 32 Required number of AAA servers Required number of Cisco 2511s (OOB ports) WAN link capacity To design the dial NMS inside the NOC, the network engineers at THEnet identified these software and management system requirements: UCD-SNMP Multi Router Traffic Grapher (MRTG), version 2.8.12...
  • Page 33 CiscoSecure Unix, version 2.3(3) War Dialer Before THEnet can implement and operate the dial NMS, several design parameters must be defined by the network engineers and operators. Each dial POP requires enough IP address space for the POP to grow to its maximum size. For THEnet, each POP must support up to 50,000 lines.
  • Page 34 POP #1 172.21.0.0/16 POP #2 172.22.0.0/16 172.23.10.0/24 Access 172.21.101.0/24 172.21.102.0/24 172.22.101.0/24 172.22.102.0/24 DeviceID 172.21.10.0/24 172.22.10.0/24 IP pool 172.21.103.0/24 172.21.104.0/22 172.22.103.0/24 172.22.104.0/22 5urf5h0p Assigns a read-only (RO) community string to enable SNMP polling and SNMP get requests. 5crapmeta1 Assigns a read-write (RW) community string to enable router configuration changes.
  • Page 35 512-333-4444 72ABCA047006-002PT THEnet implements and operates the dial NMS in two phases: Phase A—Exploring and setting up basic dial NMS functions by using free management software and light-weight NMS tools: Task 1—Enabling SNMP in a Cisco IOS Device Task 2— Exploring SNMP Capabilities by Using UCD-SNMP Task 3—Using MRTG to Monitor and Graph Traffic Loads...
  • Page 37 This section describes the MIBs and OIDs used to manage the dial Internet access service in the case study. See the following tables and choose the variables you want to use in your network. Explore the OIDs and determine whether to poll and graph the results on a regular basis. To explore the MIBs and OIDs, use UCD-SNMP.
  • Page 38 For more information about other NMS enhancements for dial, see Call Tracker plus ISDN and AAA Enhancements for the Cisco AS5300 and Cisco AS5800 at http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121limit/121x/121xh /121xh_2/dt_cltrk.htm To protect a network access server from over polling, use the SNMP get bulk feature. It’s available in SNMP v2 in CISCO-BULK-FILE-MIB.
  • Page 39 Total packets transmitted on a DS0 cpmOutPackets Number of active PPP calls Number of active V120 calls Number of active V110 calls Maximum number of DS0s used simultaneously Type of call currently connected to each DS0 Modems available to take calls Average call duration for each modem Number of times each modem...
  • Page 40 List of user CLIDs List of called DNIS phone numbers cpmActiveLocalPhoneNumber List of TTY interfaces in use List of which user is using which modem slot List of which user is using which modem port List of which IP addresses are currently in use cpmActiveRemotePhoneNumber show caller ip...
  • Page 41 One block of loopback IP addresses is used to simplify IP-security filtering at the NOC. This technique protects the NOC from devices that should not access management services, such as TACACS+, RADIUS, syslog, and SNMP. The dial NMS environment interfaces with SNMP through these applications: UCD-SNMP SNMP Commander...
  • Page 42 To enable SNMP on a Cisco IOS device in the network, follow these steps. In some software releases, the commands snmp-server engineID local and snmp-server packetsize are enabled by default. To use Loopback0 for device management and set SNMP traps to use that IP address, enter the following commands.
  • Page 43 snmp-server enable traps snmp host 172.23.10.1 traps SNMPv1 Enables traps for unsolicited notifications for configuration changes, environmental variables, and critical device conditions. This command enables 14+ other commands for distinct types of SNMP traps. Edit this command list to include only the traps that are used by your network environment.
  • Page 45 Researching and identifying which functions are available in SNMP are part of building a dial NMS environment. In this case study, UCD-SNMP, an opensource freeware application that allows access to SNMP functions from a command line interface (CLI), is used to explore the capabilities of SNMP.
  • Page 46 To install UCD-SNMP and download MIBs from the Cisco FTP site, follow these steps. You can also download individual MIBs from http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml Go to http://ucd-snmp.ucdavis.edu Download, compile, and install UCD-SNMP. In this case study, the UCD-SNMP commands are installed in the /usr/local/bin directory. From the Cisco FTP site, download the MIBs into the /usr/local/share/snmp/mibs directory on your Solaris workstation.
  • Page 47 5urf5h0p system 2> /dev/null system.sysDescr.0 = "Cisco Internetwork Operating System Software ..IOS (tm) 5800 Software (C5800-P4-M), Version 12.1(2a)T1, (c) 1986-2000 by cisco Systems, Inc...Compiled Mon 12-Jun-00 23:13 by ccai" system.sysObjectID.0 = OID: enterprises.9.1.188 system.sysUpTime.0 = Timeticks: (45492606) 5 days, 6:22:06.06 system.sysContact.0 = "net-admin@aurora.the.net"...
  • Page 48 Poll the interfaces table and redirect the output to a text file by entering the snmptable command and ifTable OID: onionring:~$ snmptable travis-nas-01.the.net 5urf5h0p interfaces.ifTable > /export/home/www/travis-nas-01_ifTable.txt onionring:~$ Do not forget the space between > and /export Inspect the contents of the interfaces table by entering the cat command. In the following Cisco AS5800 example, notice the interface descriptions (ifDescr) and types (ifType).
  • Page 49 The dial engineers at THEnet created a tool called SNMP Commander that: Provides web-based access to UCD-SNMP CLI commands. Builds web-based OID bookmarks, which enable you to go to OIDs without using a keyboard. Aids the MIB exploration and NMS design tasks. By using SNMP Commander and a web browser, you can: Create URL links for the network staff and help desk.
  • Page 53 Multi Router Traffic Grapher (MRTG) is a free performance management application for Unix that monitors SNMP statistics from any SNMP capable device on your network and performs the following functions: Captures, stores, and graphically presents SNMP data. By default, a web page with four graphs per MIB object (OID) is created by MRTG.
  • Page 54 For each OID referenced in the configuration file, MRTG creates the following graphs: Daily graph—5 minute average data points with approximately 33 hours of data presented. Weekly graph—30 minute average data points with approximately 8 days of data presented. Monthly graph—2 hour average data points with approximately 5 weeks of data presented. Yearly graph—1 day average data points with approximately 1 year of data presented.
  • Page 55 Time in use CISCO-POP-MGMT-MIB 1.3.6.1.4.1.9.10.19.1.1.1.1.8 PPP calls CISCO-POP-MGMT-MIB 1.3.6.1.4.1.9.10.19.1.1.5 DS0 high CISCO-POP-MGMT-MIB water mark 1.3.6.1.4.1.9.10.19.1.1.8 Modems CISCO-MODEM-MGMT-MIB available 1.3.6.1.4.1.9.9.47.1.1.7 Average call CISCO-MODEM-MGMT-MIB duration 1.3.6.1.4.1.9.9.47.1.3.1.1.9 No answers CISCO-MODEM-MGMT-MIB 1.3.6.1.4.1.9.9.47.1.3.3.1.1 Failed Train CISCO-MODEM-MGMT-MIB 1.3.6.1.4.1.9.9.47.1.3.3.1.2 Successful CISCO-MODEM-MGMT-MIB train 1.3.6.1.4.1.9.9.47.1.3.3.1.3 TX speed CISCO-MODEM-MGMT-MIB 1.3.6.1.4.1.9.9.47.1.3.1.1.14 RX speed CISCO-MODEM-MGMT-MIB 1.3.6.1.4.1.9.9.47.1.3.1.1.15...
  • Page 56 CISCO-MODEM-MGMT-MIB Active user ID .1.3.6.1.4.1.9.10.19.1.3.1.1.3 Active call duration CISCO-MODEM-MGMT-MIB .1.3.6.1.4.1.9.10.19.1.3.1.1.8 User CLID CISCO-MODEM-MGMT-MIB .1.3.6.1.4.1.9.10.19.1.3.1.1.2 DNIS phone number CISCO-MODEM-MGMT-MIB .1.3.6.1.4.1.9.10.19.1.3.1.1.13 Active TTY CISCO-MODEM-MGMT-MIB .1.3.6.1.4.1.9.10.19.1.3.1.1.14 Active modem slot CISCO-MODEM-MGMT-MIB .1.3.6.1.4.1.9.10.19.1.3.1.1.6 Active modem port CISCO-MODEM-MGMT-MIB .1.3.6.1.4.1.9.10.19.1.3.1.1.7 Active user IP CISCO-MODEM-MGMT-MIB .1.3.6.1.4.1.9.10.19.1.3.1.1.4 Internet users spend approximately 80 percent of their time reading information—not downloading data.
  • Page 57 The Connection Success Rate (CSR) is an important metric for tracking and measuring the stability of a dial service. The CSR is defined by the number of modems that successfully train up and go in to connected state. In addition to the CSR, you must track and analyze additional areas. For example, SNMP MIBs can be used to measure the success rate for items such as PPP, AAA, and IP negotiation.
  • Page 58 MRTG efficiently compresses and archives data to create graphs. For example, you can keep information for an entire year on a server without using much disk space. The configuration file used to create these graphs is posted at http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/dialnms/mrtg53.txt Note the numeric OIDs in the configuration file.
  • Page 59 Because dial interfaces normally go up and down as calls connect and disconnect, monitor counters such as: PPP sessions in use DS0s in use Modem calls that have been rejected Depending on how the dial interfaces are used on a access server, different types of counters may not be valuable to monitor, such as byte-packet counters on the interfaces in Table 17.
  • Page 60 Example: ./cfgmaker 5urf5h0p@travis-nas-01 >> travis-nas-01.cfg In the previous example: is the SNMP community string. 5urf5h0p is the hostname of the managed device. travis-nas-01 is the configuration file that MRTG reads each time it starts up. travis-nas-01.cfg If the domain name server (DNS) is not working, MRTG cannot use a hostname. You must use an IP address instead.
  • Page 61 #--------------------------------------------------------------------------------------- # purpose: DS0s and Analog #--------------------------------------------------------------------------------------- Target[travis-nas-01_DS0ANALOG]: 1.3.6.1.4.1.9.10.19.1.1.4.0&1.3.6.1.4.1.9.10.19.1.1.2.0:5urf5h0p@travis-nas-01 MaxBytes1[travis-nas-01_DS0ANALOG]: 200 MaxBytes2[travis-nas-01_DS0ANALOG]: 200 Title[travis-nas-01_DS0ANALOG]: DS0s and Analog in Use PageTop[travis-nas-01_DS0ANALOG]: <H2>DS0s and Analog in Use</H2> <TABLE> <TR><TD>Device:</TD><TD>travis-nas-01</TD></TR> <TR><TD><a href="/mrtg/mrtg.html">HOME</a></TD></TR> </TABLE> Options[travis-nas-01_DS0ANALOG]: gauge #---------------------------------------------------------------------------------------- ------ # purpose: DS0s and SerialX:Y #---------------------------------------------------------------------------------------- ------ Target[travis-nas-01_DS0SERIAL]: 1.3.6.1.4.1.9.10.19.1.1.4.0&1.3.6.1.4.1.9.10.19.1.1.3.0:5urf5h0p@travis-nas-01...
  • Page 62 <TR><TD><a href="/mrtg/mrtg.html">HOME</a></TD></TR> </TABLE> #---------------------------------------------------------------------------------------- ------ # purpose: cpmISDNCallsClearedAbnormally and cpmModemCallsClearedAbnormally #---------------------------------------------------------------------------------------- ------ Target[travis-nas-01_clearAbnormal]: 1.3.6.1.4.1.9.10.19.1.2.3.0&1.3.6.1.4.1.9.10.19.1.2.4.0:5urf5h0p@travis-nas-01 MaxBytes1[travis-nas-01_clearAbnormal]: 200 MaxBytes2[travis-nas-01_clearAbnormal]: 200 Title[travis-nas-01_clearAbnormal]: travis-nas-01 cpmISDNCallsClearedAbnormally and cpmModemCallsClearedAbnormally PageTop[travis-nas-01_clearAbnormal]: <H2>cpmISDNCallsClearedAbnormally and cpmModemCallsClearedAbnormally</H2> <TABLE> <TR><TD>Device:</TD><TD>travis-nas-01</TD></TR> <TR><TD><a href="/mrtg/mrtg.html">HOME</a></TD></TR> </TABLE> #---------------------------------------------------------------------------------------- ------ # purpose: cpmISDNNoResource and cpmModemNoResource #---------------------------------------------------------------------------------------- ------ Target[travis-nas-01_callNoResource]: 1.3.6.1.4.1.9.10.19.1.2.5.0&1.3.6.1.4.1.9.10.19.1.2.6.0:5urf5h0p@travis-nas-01...
  • Page 63 MaxBytes2[travis-nas-01_vpdn_tunnelanddenied]: 200 Title[travis-nas-01_vpdn_tunnelanddenied]: cvpdnTunnelTotal and cvpdnDeniedUsersTotal PageTop[travis-nas-01_vpdn_tunnelanddenied]: <H2>cvpdnTunnelTotal and cvpdnDeniedUsersTotal</H2> <TABLE> <TR><TD>Device:</TD><TD>travis-nas-01</TD></TR> <TR><TD><a href="/mrtg/mrtg.html">HOME</a></TD></TR> </TABLE> Options[travis-nas-01_vpdn_tunnelanddenied]: gauge #---------------------------------------------------------------------------------------- ------ # purpose: activeDS0s and cvpdnSessionTotal #---------------------------------------------------------------------------------------- ------ Target[travis-nas-01_activeDS0vpdnSession]: 1.3.6.1.4.1.9.10.19.1.1.4.0&1.3.6.1.4.1.9.10.24.1.1.2.0:5urf5h0p@travis-nas-01 MaxBytes1[travis-nas-01_activeDS0vpdnSession]: 200 MaxBytes2[travis-nas-01_activeDS0vpdnSession]: 200 Title[travis-nas-01_activeDS0vpdnSession]: activeDS0s and cvpdnSessionTotal PageTop[travis-nas-01_activeDS0vpdnSession]: <H2>activeDS0s and cvpdnSessionTotal</H2> <TABLE>...
  • Page 64 "/tmp/crontabmMaqZd" 14 lines, 610 characters #ident "@(#)root 1.19 98/07/06 SMI" /* SVr4.0 1.1.3.1 # The root crontab should be used to perform accounting data collection. # The rtc command is run to adjust the real time clock if and when # daylight savings time changes.
  • Page 65 Use a web browser to view the MRTG output files in the web page directory. If the domain name server (DNS) is not working, a hostname cannot be used by MRTG. Use the IP address instead.
  • Page 67 Syslog, Network Time Protocol (NTP), and modem call records work together to isolate and troubleshoot faults in a dial access network. Syslog enables you to: Centrally log and analyze configuration events and system error messages, such as router configuration changes, interface up and down status, modem events, security alerts, environmental conditions, trace backs, and CPU process overloads.
  • Page 68 By using the logging ? command, you can see the log settings for distinct destinations: travis-nas-01(config)#logging ? Hostname or A.B.C.D IP address of the logging host buffered Set buffered logging parameters console Set console logging level facility Facility parameter for syslog messages history Configure syslog history table monitor...
  • Page 69 The Network Time Protocol (NTP): Provides a synchronized time base for networked routers, servers, and other devices. Coordinates the time of network events, which helps you understand and troubleshoot the time sequence of network events. For example, call records for specific users can be correlated within one millisecond.
  • Page 70 You can view entire log files or portions of logs in the MCR viewer. In addition, you can parse for specific users and other call attributes for a modem call (for example, modulation, error correction, compression, disconnect causes, and retrains). Modem call records are available in syslog starting with Cisco IOS Releases 11.3AA and 12.0T.
  • Page 71 To enable NTP and related clocking services, follow these steps. From the Cisco IOS device, enter the following commands. Enable debug timestamps and include the date, time, and milliseconds relative to the local time zone: service timestamps debug datetime msec localtime show-timezone service timestamps log datetime msec localtime show-timezone Identify the local timezone and enable recurring time adjustments for daylight savings time by entering the following commands:...
  • Page 72 Verify that the router is receiving NTP packets from the NTP server by entering the following command: travis-nas-01>show ntp association address ref clock *~172.22.255.1 127.127.7.1 * master (synced), # master (unsynced), + selected, - candidate, ~ configured travis-nas-01> The tilde (~) next to the IP address of the NTP server means the NTP service is configured. The asterisk (*) indicates successful synchronization with the master clock.
  • Page 73 Edit the ntp.conf file by changing multicastclient to server followed by the IP address of the target NTP server: # @(#)ntp.client # /etc/inet/ntp.client # An example file that could be copied over to /etc/inet/ntp.conf; it # provides a configuration for a host that passively waits for a server # to provide NTP packets on the ntp multicast net.
  • Page 74 The ntp.client file or the xntpd daemon cannot be found in the directories shown in the examples. The error message “No Associations IDs Returned” when you enter the ntpq -p command. To enable syslog messages in the Cisco IOS software and send them to a syslog server, follow these steps: Inspect the current logging status by entering the following command: travis-nas-01#show logging...
  • Page 75 logging buffered 10000 debugging logging console informational no logging console guaranteed logging trap debugging logging 172.21.100.100 logging facility local0 Enable modem call records in the Cisco IOS by entering the following command: modem call-record terse A modem call record, which is a syslog message, looks like this: May 26 22:04:23.346 CST: %CALLRECORD-3-MICA_TERSE_CALL_REC: DS0 slot/contr/chan= 0/0/0, slot/port=2/14, call_id=26, userid=(n/a), ip=0.0.0.0, calling=4082322078, called=3241933, std=V.34+, prot=LAP-M, comp=V.42bis both, init-rx/tx b-rate=264...
  • Page 76 (Optional) To disable syslog messages and SNMP traps when dial interfaces go up and down, use the commands no logging event link-status and no snmp trap link-status. Although up and down events are legitimate events on dial interfaces, these events should not cause alarms as LAN and WAN interfaces would.
  • Page 77 #Following is the new line. It adds a logging facility number and direcory path for the #log file (router.log). local0.debug /var/log/router.log The previous syslog.conf example has been abbreviated to fit this document. The actual file size is much larger than the example. Add the new line to the end of the file.
  • Page 78 To inspect syslog messages by using Cisco IOS commands, Unix commands, FTP, and a web browser, follow these steps: From the Cisco IOS device, create basic syslog messages by entering these commands: travis-nas-01#configure terminal Enter configuration commands, one per line. travis-nas-01(config)#^Z travis-nas-01#configure terminal Enter configuration commands, one per line.
  • Page 79 Table 21 shows the generic URL syntax to use. Be sure to replace the variables with your own information. The FTP server automatically prompts you for a login password. ftp://username@host/directory-path file://directory-path Uses FTP to view ftp://sam@172.23.84.22/var/log/router.l logs from a remote location.
  • Page 81 A web portal for the dial NMS is a combination of CGI scripts and HTML links used to support a dial Internet access service. As the number of devices and applications in a network increase, the operations support team may become inundated with a myriad of management products.
  • Page 82 Cisco IOS CLI Command Center A web page that provides HTTP access to frequently used Cisco IOS CLI commands. The operations team and help desk can use this utility to troubleshoot connectivity problems. See the “Using HTTP to Access CLI Commands” section on page 86.
  • Page 83 A device linker web page: Simplifies access to the many device-management interfaces in the network. Provides links to the telnet, console, and HTTP ports of Cisco IOS devices. Cisco 2511 terminal server Line 1 RS-232 Telnet access cable telnet://172.21.10.10 Cisco AS5800 HTTP access to the CLI http://172.21.10.10 OOB console access...
  • Page 84 <td><a href="http://172.21.10.1">travis-nas-01</a></td> <td><a href="telnet://172.21.10.1">172.21.10.1</a></td> <td><a href="telnet://172.21.101.250:2001">travis-oob-01:2001</a></td> <td>5800</td> <td>Dial POP #1</td> </tr> </table> </body> </html> OOB console access telnet://termserver-ip:20XX Basic IP access telnet://ip-address IOS HTTP access http://ip-address Post the device linker web page to a WWW server in the NOC. telnet://172.21.101.250:2001 telnet://172.21.10.1 http://172.21.10.1...
  • Page 85 Click on an active device link. After a telnet session opens, log in. If you cannot access the console of a device, follow these steps: Verify that the configuration on the terminal server is correct. Telnet is the only service that must be supported to access the lines.
  • Page 86 (Optional) Sometimes administrators inadvertently leave lines in use. To make idle telnet sessions end after 30 minutes, enter the exec-timeout 30 0 command on all the lines. line 1 16 no exec exec-timeout 30 0 transport input telnet Using web-based access to the CLI reduces the need for telnet sessions to monitor or verify network operations.
  • Page 87 Create a table in an HTML web page and enter your list of frequently used Cisco IOS CLI commands. To create the link for a CLI command, specify the IP address of the Cisco IOS device followed by the command. Remember to include the forward slashes (/) between each command mode and key word.
  • Page 88 show modem show caller show modem call-stats show caller ip show modem ? show caller timeout show caller ? show logging debug isdn q931 clear counters debug modem clear logging debug ppp negotiation show debug debug ppp authentication undebug all debug dialer debug dialerpacket Post the HTML page that you created in Step 2 to a web server.
  • Page 89 For the source code that created the Cisco IOS CLI Commander in Figure 22, go to http://www.cisco.com/univercd/cc/td/doc/cisintwk/intsolns/dialnms/httpcli.txt...
  • Page 90 Click on a CLI command and view the command output in a web page.
  • Page 91 Managing IP addresses is a primary network administration function. Assigning and removing IP addresses can be tedious and error prone. Regardless—you must manage IP addresses to avoid duplicate IP subnets and addresses. Domain Name System (DNS) servers provide two kinds of fundamental lookup services: Forward lookups—Used for looking up the IP address of a provided device name.
  • Page 92 Database locking prevents multiple users from writing to the same database records concurrently. However, an administrator may occasionally not exit a session properly, and the database may be left locked. To release the lock on the database, use the force-lock network registrar command. Network registrar commands sent from the Unix shell lock the database only while commands are running.
  • Page 93 When working with a reverse zone, you can map an IP address to a router by entering the zone command and the addRR resource record (RR) option: nrcmd> zone 101.21.172.in-addr.arpa. addRR 7 PTR bobslake-nas-01.the.net Remove a resource record by entering the zone command and removeRR option: nrcmd>...
  • Page 94 To add an “A” Resource Record (RR) to a forward zone (domain) and map a name to an IP address, enter the zone command: nrcmd> zone the.net. addRR bobslake-nas-02 A 172.21.10.18 3600 604800 86400 Dynamic Resource Records Static Resource Records aurora bobslake-nas-01 bobslake-nas-02...
  • Page 95 CNR can use batch files to make large and small-scale changes to the DNS configuration within your network. To use the batch-file facility to add and remove entries, follow these steps: Define the batch file by entering zone commands: zone the.net. addRR doc-core-02 A 172.21.10.6 zone the.net.
  • Page 96 To create a domain (or forward zone) and include all forward mapping (the “A” records) for the domain, follow these steps: Create a domain and include all forward mapping (the “A” records) by entering the zone command with the create option: nrcmd>...
  • Page 97 To create an IP tracker web page, follow these steps: Become familiar with the layout of an IP tracker web page. In Figure 24, the subnet column shows a list of all managed zones. The assignment column describes the purpose of each zone.
  • Page 98 Understand how the CGI scripts function. There are two scripts that work together to return an NSLOOKUP list query (ls) for a specified zone in a CGI link. dnszone.pl—Runs the CGI process. In the subnet column in Figure 24, the entry 172.21.10.0/24 is an active link that calls the dnszone.pl script.
  • Page 99 By creating reverse lookup zones for each IP subnet, you gain a robust database that can be used to track assignments within an IP address space. Reverse lookups can determine the allocation status of any address from any DNS client. Network operators must account for used and unused IP addresses.
  • Page 101 The primary function of HP OpenView (HPOV) is to manage faults. In this case study, HP OpenView: Discovers all the devices in the network. Functions as the central-starting point for other element managers (EM). After HPOV is installed, the remaining components of the network management architecture are built around HPOV. Resides on the same Unix workstation as CiscoWorks 2000 Resource Manager Essentials, which gathers the following database information from HPOV: Device names and IP addresses...
  • Page 102 Describing the advanced capabilities of HPOV is outside the scope of this document. For more information, go to http://ovweb.external.hp.com/lpe/doc_serv/ and http://www.openview.hp.com For Cisco IOS SNMP configurations, see the “Task 1—Enabling SNMP in a Cisco IOS Device” section on page 41. To verify that the HPOV daemons are running and the SNMP configuration is correct, follow these steps: Start HPOV from the command line by entering the ovw&...
  • Page 103 object manager name: snmpCollect state: RUNNING PID: last message: No values configured for collection. exit status: object manager name: ovrepld state: RUNNING PID: last message: Initialization Complete. exit status: If a daemon is not running, try restarting it by using the commands ovstop daemon-name and ovstart daemon-name.
  • Page 104 Click Add and Apply to submit the entries.
  • Page 105 Perform an SNMP demand poll for a new managed device if you do not want to wait for the next automatic topology poll. HPOV performs less frequent automatic topology demand polls as your network and the HPOV device database becomes more static. When the HPOV daemons start, HPOV discovers the devices in your network.

  • Page 106: Snmpv1 And Snmpv2C

    Map color legend: Green—The device is up. Yellow—Multiple interfaces are down. Light blue—One interface is down. Dark blue—The device is detected, but it has never been managed. The device is unreachable. Red—The device is down and unreachable. Select a device icon in the map (single click). Go to Fault.
  • Page 107 Confirms the interfaces were successfully pinged. Interface Verifies that the system description information was collected, so Get system description you can identify the software version running on the device. To test that a device responds to SNMP Get requests, follow these steps: Select a device icon in the map (single click).
  • Page 108 If a device is not responding to a demand poll, follow these steps: Poll a different device to see if it responds to SNMP. If the device responds, HPOV is not the problem. Ping the device that is not responding. If the ping works, the devices are communicating. A firewall in the communication path can block ping and SNMP packets.
  • Page 109 Setting up alarms for different kinds of traps is outside the scope of this document. To verify that HPOV is receiving traps from devices in the network, follow these steps: Open the All Events Browser. From the Fault menu, select Events. Force a trap to be sent into the browser by manually causing a fault.
  • Page 110 Do not poll the asynchronous and serial interfaces on Cisco access servers. The reasons for this recommendation include: As remote users dial in to an access server, it is normal behavior for asynchronous and serial interfaces to regularly go up and down. On an average 20-minute call, one modem normally produces three alerts.
  • Page 111 Find the following interfaces: Serial interface channels (B and D channels). For example, Se1/0/0:6 and Se1/0/0:23 Asynchronous interfaces. For example, Async 1/2/1 Select a group of ports to unmanage. Draw a box around the ports, or select them individually. From the Map menu, select Unmanage Objects. Unmange all ports except the T1 trunks, loopback management interface, and Ethernet interface.
  • Page 112 To manually re-structure device maps to adequately represent your network and turn off the automatic-layout function for the top-level map, follow these steps: Re-structure the top-level map by selecting and moving device icons. For example, put a collapsed backbone in the center of the map; then, position devices around the backbone. Go to View.
  • Page 113 After a filter is set up, HPOV will not discover devices unless they are defined by the filter. Edit the filter each time a new device is added to the network. For more information about discovery filters, go to http://www.openview.hp.com The filter file is located in the /etc/opt/OV/share/conf/C directory.
  • Page 114 FilterExpressions { // The following combines the two set filters // defined above into one FilterExpression. // It works unmodified as a discovery filter. // To work as a map filter, network and segment filtering // must be added (see below). VitalNodes "All Gateways and Servers"...
  • Page 115 Sometimes devices do not appear in the device map, or they are accidentally deleted from the HPOV database. To manually load devices in to the HPOV database by using the CLI, follow these steps: This step ensures that new host entries are safely loaded in to the database. Shutdown the netmon daemon by entering the ovstop netmon command from the root directory.
  • Page 117 Cisco Works 2000 Resource Manager Essentials (CW2000 RME) is an element manager used to routinely manage Cisco equipment. In this case study, CW2000 RME is used for the following tasks: Inspecting syslogs to isolate faults and device problems. Sorting syslog messages based on device and date. Polling for device and interface status.
  • Page 118 In this case study, CW2000 RME relies on the automatic-discovery mechanism in HPOV to discover devices in the network. CW2000 RME extracts the following information from the HPOV database after HPOV discovers the devices: SNMP community strings Device IP addresses Device names Device information is stored in the following database locations: For HPOV, /var/opt/OV/share/databases...
  • Page 119 In the Import from Local NMS screen: Select HP Openview from the NM Product rectangular-shaped menu. Choose Resolve conflicts after importing. Choose Cisco devices only. The SNMP community strings are automatically set during the import operation. Click Next. The devices are imported and a status summary appears. Click Update until you see all the devices classified as managed devices.
  • Page 120 To verify that polling is enabled or to alter any polling settings, follow these steps. From the Admin menu, click on Availability: Change Polling Options. In the Select Polled Views screen, select All Views and All Polled Views. Click Next. To accept the default settings, click Finish.
  • Page 121 To inspect the status and availability of the devices, follow these steps. From the Tasks menu, click on Availability: Reachability Dashboard. Click a device to become familiar with the different management elements. Green arrows indicate devices that are up. Red arrows indicate devices that are down. To turn on continuous availability monitoring and reporting, go to the Tasks menu.
  • Page 122 Select All in the Views window. Select one or more devices. Click Finish. Inspect the available elements for the devices.
  • Page 123 Having quick access to archived configuration files reduces network downtime when problems occur. You can only back up managed devices. To back up the Cisco IOS start-up configuration files for devices within the network, follow these steps: From the Tasks menu, select Device Configuration: Update Archive. Select All Devices.
  • Page 124 CiscoView is a GUI-based device management software application that lets you access dynamic status, statistics, and comprehensive configuration information for Cisco products. To inspect device-specific characteristics on different Cisco devices, follow these steps: From the top-level map in HPOV, select a device. Go to Monitor: CiscoView.

  • Page 127: I N D E X

    case study CLI commands design negotiation servers busy hour ratio capacity planning Cisco 2511 setting up Cisco 2511, console connection, troubleshooting Cisco AS5300 MRTG configuration file MRTG graphs Cisco AS5800 Cisco IOS CLI Commander Cisco IOS configurations HTTP modem call records SNMP syslog terminal server, Cisco 2511...
  • Page 128 SNMP, troubleshooting SNMP configuration, verifying sysobjectID traps, verifying web site HTTP access to CLI commands, using implemenation tasks for a dial NMS interface loopback command interfaces capacity planning unmanaging IOS, See Cisco IOS IP addresses, managing IP design...
  • Page 129 OIDs circuit utilization description modem information user information OpenView, See HP OpenView operation tasks for a dial NMS out-of-band console ovstatus command ovstop command ovw& command performance management CLI commands Connection Success Rate OIDs to query...
  • Page 130 CiscoWorks 2000 RME warnings portal, for a dial NMS PRI lines ps -elf command RADIUS design security management AAA case study CLI commands for IP networks HTTP incident tracking SNMP service definition service timestamps command show caller command...
  • Page 131 console warnings daemon, configuring design destinations enabling on a Cisco IOS device link status events, disabling log file, inspecting server severity levels WAN links T3 cards TACACS+ design tail -f command terminal server, setting up topology touch command troubleshooting HP OpenView terminal server using modem call records using NTP...