Cisco Device Management

Transcription

1 Cisco Device Management User Guide Document 0809

2 Notice Copyright Notice Copyright 2002-present by Aprisma Management Technologies, Inc. All rights reserved worldwide. Use, duplication, or disclosure by the United States government is subject to the restrictions set forth in DFARS (c)(1)(ii) and FAR Liability Disclaimer Aprisma Management Technologies, Inc. ( Aprisma ) reserves the right to make changes in specifications and other information contained in this document without prior notice. In all cases, the reader should contact Aprisma to inquire if any changes have been made. The hardware, firmware, or software described in this manual is subject to change without notice. IN NO EVENT SHALL APRISMA, ITS EMPLOYEES, OFFICERS, DIRECTORS, AGENTS, OR AFFILIATES BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF APRISMA HAS BEEN ADVISED OF, HAS KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES. Trademark, Service Mark, and Logo Information SPECTRUM, IMT, and the SPECTRUM IMT/VNM logo are registered trademarks of Aprisma Management Technologies, Inc., or its affiliates. APRISMA, APRISMA MANAGEMENT TECHNOLOGIES, the APRISMA MANAGEMENT TECHNOLOGIES logo, MANAGE WHAT MATTERS, DCM, VNM, SpectroGRAPH, SpectroSERVER, Inductive Modeling Technology, Device Communications Manager, SPECTRUM Security Manager, and Virtual Network Machine are unregistered trademarks of Aprisma Management Technologies, Inc., or its affiliates. For a complete list of Aprisma trademarks, service marks, and trade names, go to: All referenced trademarks, service marks, and trade names identified in this document, whether registered or unregistered, are the intellectual property of their respective owners. No rights are granted by Aprisma Management Technologies, Inc., to use such marks, whether by implication, estoppel, or otherwise. If you have comments or concerns about trademark or copyright references, please send an to spectrum-docs@aprisma.com; we will do our best to help. Restricted Rights Notice (Applicable to licenses to the United States government only.) This software and/or user documentation is/are provided with RESTRICTED AND LIMITED RIGHTS. Use, duplication, or disclosure by the government is subject to restrictions as set forth in FAR (June 1987) Alternate III(g)(3) (June 1987), FAR (June 1987), or DFARS (c)(1)(ii) (June 1988), and/or in similar or successor clauses in the FAR or DFARS, or in the DOD or NASA FAR Supplement, as applicable. Contractor/manufacturer is Aprisma Management Technologies, Inc. In the event the government seeks to obtain the software pursuant to standard commercial practice, this software agreement, instead of the noted regulatory clauses, shall control the terms of the government's license. Virus Disclaimer Aprisma makes no representations or warranties to the effect that the licensed software is virus-free. Aprisma has tested its software with current virus-checking technologies. However, because no antivirus system is 100- percent effective, we strongly recommend that you write protect the licensed software and verify (with an antivirus system with which you have confidence) that the licensed software, prior to installation, is virus-free. Contact Information Aprisma Management Technologies, Inc., 273 Corporate Drive, Portsmouth, NH USA Phone: U.S. toll-free: Web site:

3 Contents Preface Chapter 1: Overview Cisco device support Cisco Catalyst device support Chapter 2: Application Support RFC and IEEE standard applications Proprietary application support Chapter 3: SpectroGRAPH Device Views Device Interface view Secondary Address Panel view Interface Device Topology view Sub-Interfaces Topology view Device Performance view Cisco Processes CPU Statistics Table view Device Configuration view Redundancy and Model Reconfiguration Options view Network/Host Configuration view Cisco Buffer Management view Cisco Memory Pool Monitor Table view Cisco Config-Copy Table view Cisco Running Config Event/Alarm Configuration view Entity tables Chapter 4: Syslog Trap Support Chapter 5: CiscoView Index

4 Contents 4 Cisco Device Management User Guide

5 Preface This guide is intended SPECTRUM users who are modeling Cisco devices. What is in this book This guide contains the following chapters: Chapter 1: Overview - This chapter gives an overview of how SPECTRUM models and manages Cisco devices. Chapter 2: Application Support - This chapter describes the applications supported by Cisco devices. Chapter 3: SpectroGRAPH Device Views - This chapter describes the SpectroGRAPH views available from Cisco device models. Chapter 4: Syslog Trap Support - This chapter describes the Syslog Trap Support available for the Rtr_Cisco model type. Chapter 5: CiscoView - This chapter describes how to access Cisco s CiscoView management software from SPECTRUM. Text conventions The following text conventions are used in this document: Element Convention Used Example Variables (The user supplies a value for the variable.) The directory where you installed SPECTRUM (The user supplies a value for the variable.) Courier and Italic in angle brackets (<>) <$SPECROOT> Type the following: DISPLAY=<workstation name>:0.0 export display Navigate to: <$SPECROOT>/app-defaults 5

6 Preface Element Convention Used Example Solaris and Windows directory paths Unless otherwise noted, directory paths are common to both operating systems, with the exception that slashes (/) should be used in Solaris paths, and backslashes (\) should be used in Windows paths. <$SPECROOT>/app-defaults on Solaris is equivalent to <$SPECROOT>\app-defaults on Windows. On-screen text Courier The following line displays: path= /audit User-typed text Courier Type the following path name: C:\ABC\lib\db Cross-references References to SPECTRUM documents (title and number) Underlined and hypertextblue Italic See Document feedback on page 6. SPECTRUM Installation Guide (0675) Document feedback Please send feedback regarding SPECTRUM documents to the following address: Thank you for helping us improve our documentation. Online documents SPECTRUM documents are available online at: Check this site for the latest updates and additions. 6 Cisco Device Management User Guide

7 Chapter 1: Overview This chapter gives an overview of how SPECTRUM models and manages Cisco devices. In this chapter Cisco device support on page 7 Cisco Catalyst device support on page 8 Cisco device support In general, Cisco devices are capable of running either CiscoIOS or CatOS firmware. In order for SPECTRUM to effectively manage these devices and provide access to the capabilities of each firmware, the model type used to represent the device must take into account the type of firmware the device is running. Management Modules that provide support for specific Cisco devices are set up to provide functionality based on the type of firmware the device supports. If specific Management Module has not been developed, one of the following model types will be used. As noted below, SPECTRUM chooses a model type appropriate for the firmware that the device is running. Rtr_Cisco: If a specific Management Module for the device is not available, this model type is used to model Cisco routers running IOS firmware Figure 1-1: Rtr_Cisco Device Model. SwCiscoIOS: If a specific Management Module for the device is not available, this model type is used to model Cisco switches running IOS firmware. 7

8 Chapter 1: Overview Figure 1-2: SwCiscoIOS Device Model RtrCatOS: If a specific Management Module for the device is not available, this model type is used to model Cisco routers running CatOS firmware. Figure 1-3: RtrCatOS Device Model SwCatOS: If a specific Management Module for the device is not available, this model type is used to model Cisco switches running CatOS firmware. Figure 1-4: SwCatOS Device Model The additional chapters of this guide discuss the functionality available for the Rtr_Cisco, SwCiscoIOS, RtrCatOS, and SwCatOS model types. Cisco Catalyst device support When SPECTRUM discovers a Catalyst 29xx series device, it is modeled according to the following criteria: The HubCat29xx model type is used to model Catalyst 2900 series switches that run IOS firmware and support the CISCO-C2900-MIB. The SwCiscoIOS model type is used to model Catalyst 2900 series switches that run IOS firmware, but do not support the CISCO-C2900-MIB. The Catalyst 2970 and Catalyst 2948g devices fall into this category. The SwCat4xxx model type is used to model Catalyst 2900 series switches that run CatOS firmware. When SPECTRUM discovers a Catalyst 35xx series device, it is modeled using the following rules: The HubCat29xx model type is used to model Catalyst 3500 series switches that run IOS firmware and support the CISCO-C2900-MIB. The SwCiscoIOS model type is used to model Catalyst 3500 series switches that run IOS firmware, but do not support the CISCO-C2900-MIB. The Catalyst 3550 series falls into this category. 8 Cisco Device Management User Guide

9 Chapter 2: Application Support This chapter describes the applications supported by Cisco devices. In this chapter RFC and IEEE standard applications on page 9 Proprietary application support on page 9 RFC and IEEE standard applications Cisco devices support various RFC and IEEE standard applications. The applications are created and associated with the device model based on the specific device s capabilities. The following guides contain complete documentation for each of the standard applications supported by SPECTRUM: Bridging Applications (2562) MIB II Applications (2561) Routing Applications (3080) Technology Applications (5065) Transmission Applications (5064) Proprietary application support The Cisco model types described in this guide support a number of applications based on Cisco proprietary MIBs. For complete documentation of these applications, see the Cisco Applications (5127) guide. 9

10 Chapter 2: Application Support 10 Cisco Device Management User Guide

11 Chapter 3: SpectroGRAPH Device Views This chapter describes the SpectroGRAPH views available from Cisco device models. In this chapter Device Interface view on page 11 Interface Device Topology view on page 11 Sub-Interfaces Topology view on page 12 Device Performance view on page 12 Device Configuration view on page 13 Device Interface view Note: From the Icon Subviews menu for the Interface icon, select Device. This view provides dynamic configuration and performance information for each of the device s serial/network I/O ports, which are represented by Interface icons in the bottom panel of the view. The middle panel of the view also displays a Device icon, which allows you to monitor the device operation and access other device-specific views. Secondary Address Panel view Note: From the Icon Subviews menu for the Interface icon in the Interface Device view, select Secondary Address Panel. This panel provides a table of IP addresses and masks obtained from the Address Translation table within the device s firmware. You can change the current address displayed in the IP Address field by selecting an entry from the table in this panel and clicking the Update button. Interface Device Topology view Note: From the Icon Subviews menu for the Device icon, select DevTop. The lower panel uses Interface icons to represent the device s serial/network/i/o ports. If a device is connected to an interface, a Device icon appears on the vertical bar above the Interface icon 11

12 Chapter 3: SpectroGRAPH Device Views along with an icon representing the network group that contains the device. See SPECTRUM Views (2517) for more details. Sub-Interfaces Topology view Note: From the Icon Subviews menu for an Interface icon whose interface contains subinterfaces, select Sub-Interfaces. When present, the endpoints associated with multiplexed, physical connections are modeled by SPECTRUM as sub-interfaces. This includes, for example, Permanent Virtual Circuits (PVCs) on a physical ATM interface and DCL circuits on a physical Frame Relay interface. The lower panel of the Sub-Interfaces Topology view uses Interface icons to represent these nonphysical entities and circuits that are connected to the physical interface. Device Performance view Note: From the Icon Subviews menu for the Device icon, select Device Performance. This view is not available for the RtrCatOS or SwCatOS model types. For devices with a firmware level below 12.0, the Device Performance view includes both a graph and a table that show current, average, and peak values for the following performance statistics: CPU Utilization 1 Minute Average 5 Minute Average The view also provides button access to the Enterprise Alarm Manager and the Event Log. For devices with a firmware level of 12.0 or above, selecting Device Performance opens the Cisco Processes CPU Statistics Table view on page 12. Cisco Processes CPU Statistics Table view This table displays overall CPU statistics. Column headings are as follows. CPU An index that uniquely represents a CPU (or group of CPUs) whose load information is reported by a row in this table. This index is assigned arbitrarily by the engine and is not saved over reboots. Physical Index The physical entity for which the CPU statistics in this entry are maintained. The physical entity can be a CPU chip, a group of CPUs, a CPU card etc. The exact type of this entity is described by its entphysicalvendortype value. If the CPU statistics in this entry correspond to more than one physical entity (or to no physical entity), or if the entphysicaltable is not supported on the SNMP agent, the value of this field must be zero. 5 Sec Busy % The overall CPU busy percentage in the last 5 second period. 12 Cisco Device Management User Guide

13 Device Configuration view 1 Min Busy % The overall CPU busy percentage in the last 1 minute period. 5 Min Busy % The overall CPU busy percentage in the last 5 minute period. Device Configuration view Note: From the Icon Subviews menu for the Device icon, select Configuration. This view includes fields that display device information as well as an Interface Configuration Table that lists interface parameters. See the SPECTRUM Views (2517) guide for more information. The buttons available in this view depend on the firmware level the device is running. Each of these buttons are described below. Interface Address Translation This button is available to all firmware levels. It accesses the Interface Address Translation view. Refer to the SPECTRUM Views (2517) guide for more information. Redundancy and Model Reconfiguration Options This button is available to all models running a firmware version below It the Redundancy and Model Reconfiguration Options view on page 13. Network Host Config This button is available to all models running a firmware version below It accesses the Network/Host Configuration view on page 14. Buffer Management This button is available to all models running a firmware version below It accesses the Cisco Buffer Management view on page 16. Memory Pool Monitor This button is available to all models running a firmware version 12.0 or greater. It accesses the Cisco Memory Pool Monitor Table view on page 19. Config Copy Table This button is available to all models running a firmware version 12.0 or greater. It accesses the Cisco Config-Copy Table view on page 20. Running Configuration Changes This button is available to all models running a firmware version 12.0 or greater. It accesses the Cisco Running Config Event/Alarm Configuration view on page 21. Redundancy and Model Reconfiguration Options view This view allows you to enable redundant addresses, have SPECTRUM notify you of a redundancy update, and reconfigure aspects of your network connections. Cisco Device Management User Guide 13

14 Chapter 3: SpectroGRAPH Device Views Preferred Addresses This button opens the Preferred Addresses dialog box which allows you to select the redundant preferred address for the device. Redundancy Administrative Status Set this button to Enabled to cause SPECTRUM to update this model with an address from the Redundant Preferred Address list when the primary address is not accessible. Generate Redundancy Alarms Set this button to True to cause SPECTRUM to generate an alarm when a redundant address is selected. Automatically Reconfigure Interfaces Set this button to True to cause SPECTRUM to monitor the number of interfaces for this device. If a change is detected by SPECTRUM, the interfaces displayed in SPECTRUM are updated to reflect the change. Create Sub-Interfaces Set this button to determine if SPECTRUM should model the device s sub-interfaces. If set to True, these models will be displayed in the Sub-Interface view of the Physical Interface model. Reconfigure due to LINK UP/Down events Set this button to True to cause SPECTRUM to verify the interfaces displayed when a LINK UP or LINK DOWN event is received. Topologically Relocate Model Set this button to True to allow SPECTRUM to relocate the model to a different topological location as part of the AutoDiscovery process. Device Discovery after Reconfiguration Set this button to True to cause SPECTRUM to verify the interfaces displayed after a model reconfiguration occurs. Reconfigure Model This button does a complete re-read of the device and its ports. The SpectroSERVER information for this device will be updated if any of the port addresses have been changed or removed, or if the port type has been changed. Discover LANs This button discovers the devices that are connected to the ports for this device. Clicking on this button will create all LANS which are defined for each port. Network/Host Configuration view This view displays the following information. 14 Cisco Device Management User Guide

15 Device Configuration view Network Configuration The network configuration file contains commands that apply to all network servers and terminal services on a network. Previous Host Addr Provides the address of the host that supplied the network configuration file for the managed device. Previous File Name Provides the name of the network configuration file that resides on the managed device. New Host Addr This field replaces the Previous Host Addr field when the Upload Net Config file is selected. New File Name This field replaces the Previous File Name field when the Upload Net Config file is selected. Upload Net Config File Initiates the transfer of configuration file from host to server. TFTP Server Addr Address used to send the configuration file from server to a host. File Name The file name where you are storing the configuration. Copy Config to Net Initiates the transfer of configuration file from server to host. Host Configuration The host configuration file contains commands that apply to one network server in particular. Previous Host Addr The address of the host that provided the host configuration file for the managed device. Previous File Name The name of the last host configuration file used by the device. New Host Addr This field replaces the Previous Host Addr field when the Upload Host Config file is selected. New File Name This field replaces the Previous File Name field when the Upload Host Config file is selected. Upload Host Config File Initiates the transfer of configuration file from host to server. Cisco Device Management User Guide 15

16 Chapter 3: SpectroGRAPH Device Views Copy Config to NVRAM Clicking this button writes the current (running) server configuration into Non-Volatile Random Access Memory (NVRAM) where it can be stored and retained even if the server is reloaded. Clear NVRAM Clicking this button erases whatever was in Non-Volatile Random Access Memory (NVRAM) on the server. Cisco Buffer Management view This view provides the following information: Free Memory The amount of available memory in bytes. Buffer Failures The number of packets discarded due to no memory. An attempted packet buffer allocation failed. Buffer No Memory The number of buffer creation failures due to no memory. Max Buffer Elements The maximum number of buffer elements the device may create. Buffer Elements This area of the Cisco Buffer Management view displays statistics on buffer elements (data structures used to enqueue buffers in multiple output queues). Each attribute is summarized for the total interval since first poll and the rate interval between polls (Delta). Buffer Elements Free The number of buffer elements available. Buffer Element Hits The number of successful requests for buffer elements. Buffer Element Misses The number of unsuccessful requests for buffer elements. Buffer Element Creates The number of new buffer elements created by the device. Buffer Management Buttons These five buttons located in the Cisco Buffer Management view allow you to access additional buffer management information according to buffer size. Each attribute is summarized for the total interval since first poll and the rate interval between polls (Delta). 16 Cisco Device Management User Guide

17 Device Configuration view Small Buffers This button opens the Small Buffer Management view. Table 3-1 provides descriptions for the fields presented in the Small Buffer Management view. Table 3-1: Small Buffer Fields Field Description Small Buffer Size Max Small Buffers Small Buffer Total Small Buffer Free The maximum size of a small buffer. The maximum number of small buffers the device can create. The total number of enqueued small buffers. The number of small buffers available. Small Buffer Hits The number of successful requests for small buffers. Small Buffer Misses The number of unsuccessful requests for small buffers. Small Buffer Creates The number of new small buffers created by the device. Small Buffer Trims The number of small buffers returned to the free buffer pool. Medium Buffers This button opens the Cisco Medium Buffer Management view. Table 3-2 provides descriptions for the fields in the Medium Buffer Management view. Table 3-2: Medium Buffer Fields Field Medium Buffer Size Max Medium Buffers Medium Buffer Total Medium Buffer Free Medium Buffer Hits Medium Buffer Misses Description The maximum size of a medium buffer. The maximum number of medium buffers the device can create. The total number of enqueued medium buffers. The number of medium buffers available. The number of successful requests for medium buffers. The number of unsuccessful requests for medium buffers. Medium Buffer Creates The number of new medium buffers created by the device. Medium Buffer Trims The number of medium buffers returned to the free buffer pool. Big Buffers The button opens the Big Buffers view. Table 3-3 provides descriptions for the fields presented in the Big Buffer Management view. Cisco Device Management User Guide 17

18 Chapter 3: SpectroGRAPH Device Views Table 3-3: Big Buffer Fields Field Big Buffer Size Max Big Buffers Big Buffer Total Big Buffer Free Big Buffer Hits Big Buffer Misses Description The maximum size of a big buffer. The maximum number of big buffers the device can create. The total number of enqueued big buffers. The number of big buffers available. The number of successful requests for big buffers. The number of unsuccessful requests for big buffers. Big Buffer Creates The number of new big buffers created by the device. Big Buffer Trims The number of big buffers returned to the free buffer pool. Large Buffers This button opens the Cisco Large Buffer Management view. Table 3-4 provides descriptions for the fields presented in the Large Buffer Management view. Table 3-4: Large Buffer Fields Field Large Buffer Size Max Large Buffers Large Buffer Total Large Buffer Free Large Buffer Hits Large Buffer Misses Large Buffer Creates Large Buffer Trims Description The maximum number of bytes in a large buffer. The maximum number of large buffers the device can create. The total number of enqueued large buffers. The number of large buffers available. The number of successful requests for large buffers. The number of unsuccessful requests for large buffers. The number of new large buffers created by the device. The number of large buffers returned to the free buffer pool. 18 Cisco Device Management User Guide

19 Device Configuration view Huge Buffers This button opens the Cisco Huge Buffer Management view. Table 3-5 provides descriptions for the fields presented in the Huge Buffer Management view. Table 3-5: Huge Buffer Fields Field Huge Buffer Size Max Huge Buffers Huge Buffer Total Huge Buffer Free Huge Buffer Hits Huge Buffer Misses Huge Buffer Creates Huge Buffer Trims Description The maximum number of bytes in a huge buffer. The maximum number of huge buffers the device can create. The total number of enqueued huge buffers. The number of huge buffers available. The number of successful requests for huge buffers. The number of unsuccessful requests for huge buffers. The number of new huge buffers created by the device. The number of huge buffers returned to the free buffer pool. Cisco Memory Pool Monitor Table view This table displays memory pool monitoring entries. Name Displays the name assigned to a memory pool. Alternate Indicates whether or not this memory pool has an alternate pool configured. Alternate pools are used for fallback when the current pool runs out of memory. If this has a value of zero than there is no alternate. Valid This indicates whether or not the remaining fields in this entry contain accurate data. If an instance of this field has a false value, the values of this row may contain inaccurate information. Used Indicates the number of bytes from the memory pool that are currently in use by applications on the managed device. Free The number of bytes from the memory pool that are currently unused on the managed device. Largest Free Indicates the largest number of contiguous bytes from the memory pool that are currently unused on the managed device. Cisco Device Management User Guide 19

20 Chapter 3: SpectroGRAPH Device Views Cisco Config-Copy Table view A config-copy operation is a request to copy a configuration file of an SNMP Agent running Cisco s IOS software. There are several ways in which this can be done: copying to or from the net (via a protocol like tftp, ftp, or rcp), copying running configurations and vice-versa, or by copying a running or startup config to a file to the local IOS file system and vice versa. This view displays the cccopytable which provides the following information. Index Specifies a unique entry in the cccopytable. Protocol The protocol to be used for any copy. Will default to tftp if not specified. If the copy operation occurs locally on the SNMP agent, this value may be ignored by the implementation. Source File Type The type of file to copy from. Either the Source File Type or the Dest File Type (or both) must be of type runningconfig or startupconfig. Also, the Source File Type must be different from the Dest File Type. If the Source File Type has the value of networkfile, the Server Address and File Name must also be created, and these 3 values together (Source File Type, Server Address, File Name) will uniquely identify the source file. Possible types are networkfile, iosfile, startupconfig, runningconfig, and terminal. If the Source File Type is iosfile, the File Name must also be created, and the 2 values together (Source File Type, File Name) will uniquely identify the source file. Dest File Type The Destination File Type, which is the type of file to copy to. Either the Source File Type or the Dest File Type (or both) must be of type runningconfig or startupconfig. Also, the Source File Type must be different from the Dest File Type. If the Dest File Type has the value of networkfile, the Server Address and File Name must also be created, and these three values together (Dest File Type, Server Address, File Name) will uniquely identify the destination file. If the Dest File Type is iosfile, the File Name must also be created, and the two values together (Dest File Type, File Name) will uniquely identify the destination file. Possible types are networkfile, iosfile, startupconfig, runningconfig, and terminal. Server Address The IP address of the TFTP server from (or to) which to copy the configuration file. This value must be created when either the Source File Type or Dest File Type has the value networkfile. Values of or FF.FF.FF.FF. for Server Address are not allowed. File Name The file name (including the path, if applicable) of the file. This value must be created when either the Source File or Dest File Type has the value networkfile or iosfile. User Name Remote user name for copy via rcp protocol. This value must be created when the Protocol is rcp or ftp. If the protocol is rcp, it will override the remote user name configured through the rcmd 20 Cisco Device Management User Guide

21 Device Configuration view remote-username configuration command. The remote user name is sent as the server user-name in an rcp command request sent by the system to a remote rcp server. User Password Password used by ftp for copying a file to/from an ftp server. This value must be created when the Protocol is ftp. Reading it returns a zero-length string for security reasons. Notification On Completion Specifies whether or not a Notification on Completion should be issued on completion of the tftp transfer. If such a notification is desired, it is the responsibility of the management entity to ensure that the SNMP administrative model is configured in such a way as to allow the notification to be delivered. State The state of this config-copy request. The value of this field is instantiated only after the row has been instantiated, i.e., after the Row Status has been made active. Time Started The time the Copy State last transitioned to running, or 0 if the state has never transitioned to running (for e.g., stuck in waiting state). This field is instantiated only after the row has been instantiated. Time Completed The time the Copy State last transitioned from running to successful or failed states. This field is instantiated only after the row has been instantiated. Its value will remain 0 until the request has completed. Fail Reason The reason why the config-copy operation failed. This field is instantiated only when the Copy State for this entry is in the failed state. Row Status The status of this table entry. Once the entry status is set to active, the associated entry cannot be modified until the request completes (Copy State transitions to successful or failed state). Add an Entry This button opens the Add a Cisco Copy Config Entry view which allows you to add an entry to the Cisco Config-Copy Table. Cisco Running Config Event/Alarm Configuration view This view lets you set when the attribute ccmhistoryrunninglastchanged is checked. This attribute tells you if and when the configuration has changed. This view also lets you set the generation of either an event or an alarm if it does change. Alarms and events can be set to apply to just the current model or all models of this model type, as described below. Note: If ccmhistoryrunninglastchanged does change, the user may want to rediscover applications. Cisco Device Management User Guide 21

22 Chapter 3: SpectroGRAPH Device Views Hour to Run Cron Job This button allows you to select the hour of day to run the cron job. Generate Event for This Model This button allows you to select if you wish to generate an event for this model. Valid options are True and False. Generate Event For All Models Of This Model Type This button allows you to select if you wish to generate an event for all models of this model type. Valid options are True and False. Generate Alarm For This Model This button allows you to select if you wish to generate an alarm for this model. Valid options are True and False. Generate Alarm For All Models Of This Model Type This button allows you to select if you wish to generate an alarm for all models of this model type. Valid options are True and False. Running Configuration Was last Changed At: The date and time the running configuration was last updated. Entity tables Note: From the Icon Subviews menu for the Device icon, select Entity Tables > Physical/ Logical Tables. This menu selection provides access to the RFC2737App s Physical and Logical Entity tables. See the Technology Applications (5065) guide for more information. 22 Cisco Device Management User Guide

23 Chapter 4: Syslog Trap Support This chapter describes the Syslog Trap Support available for the Rtr_Cisco model type. The System Message Log (syslog) protocol is used to send text messages from a Cisco Router to the Network Management Software. These messages are sent to the SPECTRUM Event Manager as SNMP traps. For more information about syslog trap support and the Cisco Syslog Application (CiscSysLogApp), see the Cisco Applications (5127) guide. Note: The Rtr_Cisco model type supports the system error messages for the Cisco IOS Release 12.1 T. Go to for more information about Cisco Router syslog messages, including a list of facility codes and of error messages with their corresponding recommended actions. 23

24 Chapter 4: Syslog Trap Support 24 Cisco Device Management User Guide

25 Chapter 5: CiscoView This chapter describes how to access Cisco s CiscoView management software from SPECTRUM. CiscoView is management software specific to Cisco Routers. You can enable the model types described in this guide to provide a menu option used to launch CiscoView as shown in Figure 5-1. Figure 5-1: CiscoView Cisco_12012 Zoom - > CiscoView Device DevTop Application Device Performance Acknowledge Enabling CiscoView in the Solaris environment 1. Add the following information to the /opt/spectrum/spectrum60.env file: #CiscoView 3.0 CVIEW =<path_to_ciscoview> Enabling CiscoView in the Windows environment 1. From the Start > Run window, type regedit (registry editor) 2. Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > Aprisma Management Technologies > Spectrum60 > Environment 3. Choose Edit > New > String Value 25

26 Chapter 5: CiscoView 4. Type CVIEW for the name, and <path_to_ciscoview> as the string value. 5. CiscoView 3.0 will appear as Cisco View on your device menu after the above steps have been followed. This should not be confused with CiscoView, which denotes the CiscoWorks 2000 CiscoView. The CiscoWorks 2000 menu picks will only appear in the device menu if the SPECTRUM Adapter script has been run. See the CiscoWorks 2000 documentation for further information. 26 Cisco Device Management User Guide

27 Index 1 Min Busy % 13 5 Min Busy % 13 5 Sec Busy % 12 Numerics B Big Buffers button 17 Buffer Elements 16 Buffer Management button 16 Physical Index 12 Preferred Addresses 14 P R Reconfigure Model 14 Redundancy and Model Reconfiguration Options 13 C ccmhistoryrunninglastchanged 21 Cisco Applications (5127) guide 23 Cisco Buffer Management View 16 Cisco Syslog Application 23 CiscSysLogApp 23 Configuration Device 13 CPU 12 Discover LANs 14 D Large Buffers button 18 L M Medium Buffers button 17 27

28 Index 28 Cisco Device Management User Guide