SPECTRUM Configuration Manager

Transcription

1 SPECTRUM Configuration Manager

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: Page 2

3 Contents Notice... 2 Preface... 8 Intended Audience... 8 Text Conventions... 8 Document Feedback... 9 Aprisma Technical Assistance Center (ATAC) Contact Information... 9 Online Documents... 9 About About Installing...11 What is Configuration Management?...12 What are Configurations?...13 What is?...15 How Does Work?...19 Uses for...20 About Device Templates and Host Configuration Files What is a Device Template?...23 The Templates Window...24 Host Configuration Files...25 Setting Up Your Workstation as a TFTP Server...26 For Solaris Machines...26 For Windows NT/2000 Machines...28 Devices with Host Configuration Files...29 Selecting Devices and Host Configuration Files...30 Interface Models...30 Device-Specific Configurations...30 Shared Configurations...30 Host Configuration File Masking...31 Masking Host Configuration Files...31 Page 3

4 Loading Configurations Configuration Loading Details...35 Loading Configurations From the Configuration Manager: Main Window...37 Logging and Finding Load Results...39 What If a Load Fails?...40 Special Load Information for Devices with Host Configuration Files...42 Verifying Host Configuration File Captures Verifying the Configuration Capture Status...44 What if a Verification Fails?...45 Verification Options...46 About Security in Security Features...48 Hiding Passwords, Keywords, or Tokens...52 Viewing and Editing Host Configuration Passwords...53 About the Scheduler Why Schedule Operations in SCM?...55 About the Windows NT/2000 Task Scheduler Service...56 Working With the Scheduler...57 Accessing the Scheduler...57 Viewing the Results of Scheduled Operations...58 About the SPECTRUM Event Log and the SCM Log File About the SPECTRUM Event Log...60 How to Use the SPECTRUM Event Log...61 Interpreting SCM Event Codes...62 About the SCM Log File...64 About the Scm Resource File Scm Resource File...66 Keyboard Shortcuts for Menu Items...72 Page 4

5 SCM Alarms Understanding and Modifying SCM Alarms in SPECTRUM...73 SCM Events that Trigger Alarms in SPECTRUM...73 How SPECTRUM Notifies You of an SCM Alarm...73 How to Modify, Turn off, or Clear SCM Alarms...74 Running SCM from the Command Line Using SCM Commands...76 Invoking SCM...77 Capturing a Configuration from a Model...78 Loading a Configuration to One or More Models...79 Verifying a Configuration to One or More Models...80 Importing Configurations and Templates...81 Exporting Configurations and Templates...82 The User Interface Starting SCM...87 Configuration Manager: Main Window...87 Configuration List Box...89 Configuration Information Section...90 Search/Filter Option...91 Device Specific Configurations Window...92 Shared Configurations Window...93 SCM: Templates Window...94 Template Information Section...96 Template Detail Section...97 Menus, Icons, and Buttons Pull Down Menus Main Window...99 File Menu View Menu Model Menu Options Menu Preferences Menu Page 5

6 Setup Menu Help Menu Pull Down Menus Templates Window File Menu Edit Menu View Menu File > Delete File > Rename File > Exit Model > Navigate Components Model > Select Model Options > Capture Options > Load Options > Verify Options > Compare Host Config Diff Window Attribute Diff Window Options > Schedule Options > Edit Host Configuration File Menu Edit Menu Options > Edit Model Configuration File Menu Edit Menu View Menu Options > Edit Mask File Menu Edit Menu Options > Preferences Options > Preferences > Settings Options > Preferences > Attributes Options > Preferences > Search Setup > Templates Page 6

7 Help > About Configuration Manager Help > Online Manuals Figures Appendix A SPECTRUM Database Storage Constraints Index Page 7

8 Preface In This Section Intended Audience [page 8] Text Conventions [page 8] Document Feedback [page 9] Online Documents [page 9] Intended Audience This guide is intended for network administrators who want to monitor, control, troubleshoot, and document an array of network device configurations from one or more locations on a network. It is also intended for novice users of who are learning about the application in their work environment or a training class setting. Text Conventions The following text conventions are used in this document: Element Convention Used Example Variables Courier with Italic in angle brackets <>. The user needs to type the password in place of <password>. 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) Functionality enabled by SPECTRUM Alarm Notification Manager (SANM) Underlined and hypertextblue Italic SANM in brackets []. See Document Feedback [page 9]. SPECTRUM Installation Guide ( ) [SANM] AGE_FIELD_ID Page 8

9 Document Feedback Please send feedback regarding SPECTRUM documents to the following address: Thank you for helping us improve our documentation. Aprisma Technical Assistance Center (ATAC) Contact Information Contact the ATAC by calling the toll-free number for your region (listed on the Aprisma support Web site global_atac.shtml, or by calling (603) Online Documents SPECTRUM documents are available online at: Check this site for the latest updates and additions. Page 9

10 About SPECTRUM Configuration Manager This section discusses configuration management in general terms, and how the SPECTRUM solution addresses specific needs and concerns of network administrators. In This Section About Installing [page 11] What is Configuration Management? [page 12] What are Configurations? [page 13] What is? [page 15] How Does Work? [page 19] Uses for [page 20] Page 10

11 About Installing References For information about installing, see the SPECTRUM Installation Guide (0675), or consult the ATAC; see Aprisma Technical Assistance Center (ATAC) Contact Information [page 9]. Overview (CM) is an optional, separately purchased SPECTRUM component that installs with the standard SPECTRUM Install program. If necessary, you can install the SpectroSERVER and client portions of SCM on different machines. Page 11

12 What is Configuration Management? Overview Configuration management means different things to different people. This document defines configuration management as infrastructure, network, and device change management; the process of identifying, controlling, and monitoring all managed objects that comprise a communication network (where a managed object is any device modeled by SPECTRUM). Managed objects can be hardware devices (such as PCs, workstations, hubs, and routers) or the software applications that run on the devices. The benefits of using a configuration management tool include: Increased network uptime by reducing the time to resolve network issues. Lower network support costs by reducing the occurrence of network issues that require reactive troubleshooting and fixes. Lower network operational costs by reducing the time to administer system-wide changes. Page 12

13 What are Configurations? References See Host Configuration Files [page 25]. Definitions Running Configuration The version of a configuration that is loaded on a device and defines how the device operates. It is only valid for the current run-time session; the device replaces the previous running configuration with a copy of the startup configuration when it is rebooted. Startup Configuration The backup version of a configuration that is stored on the device and is used when the device is rebooted. Some devices have primary and secondary startup configurations. Host Configuration File A subset of attributes from a running configuration, selected by the device manufacturer, and converted to a text format that is human readable and device readable. SCM Configuration Model A configuration stored in the SPECTRUM SpectroSERVER database that could include: Overview Only the attributes supported by the SPECTRUM management module for the specific device, and that were captured using an SCM template. Any number of attributes from the running configuration. The host configuration file (if supported by the device manufacturer and SCM). A configuration is a set of values assigned to a managed object so it functions on a network as expected. Each managed object on the network is configured to provide specific services. Details about how a device operates and how it is customized from other network devices are contained in its configuration. Basically: Configurations are used to load attribute values or compare attribute values on device models. Configurations can only be created by using an SCM template model. Page 13

14 Configurations include values like IP address, interface configuration, enabled protocols, SNMP community names, and passwords. The values can be Management Information Block (MIB) objects, part of a host configuration file, or both. Details You must be in the Configurations window to edit a configuration. You can create configurations for devices or software of devices. You can select a device or a device component either in SpectroGRAPH or in SCM. If you select a device, you can access all sub-components of that device and all other devices of the same type in the selected landscape. You can configure an entire device with all its sub-components in one step, or you can configure any sub-component separately. Page 14

15 What is? References See About the SPECTRUM Event Log [page 60]. Overview (SCM) is an application that lets network administrators monitor, control, troubleshoot, and document an array of network device configurations from one or more locations on a network. Specifically, SCM can: Manage configurations for all devices modeled in SPECTRUM. Capture network device configurations and store them in the SPECTRUM database. Load configurations to one or more devices of the same type. Modify configurations for one or more devices of the same type. Verify that the correct configuration is running on the device. Run on all SPECTRUM platforms. Capitalize on functionality built into SPECTRUM, event/alarm, reporting, and scheduler systems, because it is fully integrated with the SpectroSERVER and SPECTRUM applications. Since SCM uses the SPECTRUM event log to record a history of SCM activity, administrators can use Web Operator s event report and alarm report features to create summaries of configuration event history. SPECTRUM alarms can be used to trigger SCM, notify personnel of problems, and/or generate trouble tickets. Page 15

16 Benefits SCM lets administrators reduce the time to deploy, replace, and configure changes to network devices. Item Benefit Comments 1 Loading the last known good configuration to a newly installed network device. 2 Bringing a replacement device quickly online by loading the last known good stored configuration on it. 3 Making on-demand, manual changes to a device configuration. 4 Efficiently manage device SNMP attribute and configuration changes by: - Supporting standard and vendor-specific MIBs. - Supporting device host configuration files from multiple vendors. - Allowing bulk gets and sets of attributes across multiple devices. - Allowing bulk uploads and downloads of device host configuration files. The last known good configuration must be identified and managed handson by the network administrator. SCM does not automatically identify and store the last known good configuration for each device type. A replacement device is also known as a standby device. An example of this benefit is when a technician installs a device on a network at one physical location, then an administrator loads its configuration from a different physical location. An example of this benefit is when a employee leaves a company and the administrator makes on-demand, system-wide community string, password, and Access Control List (ACL) changes. Bulk means manipulating multiple configurations at the same time. Bulk commands only affect one model type at a time. Multi-vendor host configuration file support is not a bulk process. Page 16

17 Item Benefit Comments 5 Make multiple configuration changes to multiple devices with a simple command sequence by: - Capturing data from a device, or simultaneously from multiple devices. - Loading and verifying a configuration on multiple devices. - Loading and verifying multiple configurations on multiple devices. - Comparing historical configuration information for one device or between multiple devices. 6 Support multiple vendors with an out-of-the-box solution by: - Letting network administrators manage SNMP attributes for all managed devices. - Including device host configuration file support for Cisco, Enterasys, Riverstone, Extreme, and Foundry Networks devices. 7 Conduct 24/7 network operations from multiple network locations, or manage multiple domains from a single network location by: - Employing follow-the-sun management. - Letting administrators manage their network(s) from any location in the infrastructure. Follow-the-sun management means locally managing a network that spans different time zones. It concerns enabling geographically dispersed organizations (region-wide, countrywide, worldwide) to manage their network(s) from different time zones to increase network monitoring time, and decrease device configuration repair time. Page 17

18 Item Benefit Comments 8 Perform distributed automatic (scheduled) or manual (on demand) configuration updates, restorations, and validations by: -Scheduling and automating the launch of one-time tasks or recurring tasks. -Managing distributed client/ server applications through a graphical front-end. -Providing a command line interface for customer-specific integration and scripting purposes. 9 Enhanced network security through automatic verification and rapid deployment of device security changes by: - Generating alarms for verification of network operational anomalies. - Generating events as a means to track all device configuration changes. - Quickly updating device security through on-demand or scheduled changes. Automatic verifications must be scheduled. Page 18

19 How Does Work? References See Figure 1 [page 144] for the configuration capture data flow. See Figure 2 [page 145] for the configuration load data flow. See Figure 3 [page 146] for the SNMP attribute capture data flow. See Figure 4 [page 147] for the SNMP attribute load data flow. See What are Configurations? [page 13]. See Device Specific Configurations Window [page 92]. See Shared Configurations Window [page 93]. Overview SCM uses configurations to compare, load, or capture attribute values from device models. SCM configuration models are model-type specific and can contain a host configuration file and/or attributes from the running configuration. Attributes can be selected directly from the SCM configuration model, changed, then loaded to the device to create a new running configuration. SCM configuration models can be either: Device specific Used only on the device from which it was captured. Shared Can be used by all models of the same model type. Page 19

20 Uses for Overview Network experts use SCM to: Create templates with the attribute lists that SCM provides. Create configurations by capturing attribute values from existing devices, then modifying them (if necessary). Set up a schedule of automatic captures, loads, and verifications to ensure reliable device configurations. System administrators use SCM to: Detect performance problems by verifying device configurations. Load configurations to one or more devices on the network. Page 20

21 Network administrators use SCM to: Maintain a library of network-specific configuration models for comparing and reconfiguring purposes. Administrators troubleshoot running configurations by comparing them with their SCM configuration model (a.k.a. last known good configuration) stored in the SpectroSERVER database. If a device must be reconfigured, the stored configuration can be loaded from anywhere on the network. Create configurations that when loaded: - Shut down network segments (as needed). Administrators can schedule regular shutdowns of network segments with SCM. - Change SNMP community strings. SNMP community name changes on multiple devices can be scheduled with SCM. - Turn interfaces, channels, and/or router protocols on and off. Interfaces, channels, and router protocols can be disabled based on a fixed schedule or a particular network event. Page 21

22 About Device Templates and Host Configuration Files This section contains detailed information about device templates in SCM and the specific devices that allow host configuration file access. In This Section What is a Device Template? [page 23] The Templates Window [page 24] Host Configuration Files [page 25] Devices with Host Configuration Files [page 29] Selecting Devices and Host Configuration Files [page 30] Host Configuration File Masking [page 31] Page 22

23 What is a Device Template? References See What are Configurations? [page 13] See Host Configuration Files [page 25]. Overview A device template is a list of pre-selected, device-specific attributes that do not have values and flags. Templates are created by selecting attributes from the Insertable Attribute list, which is basically a listing of readable and writable attributes for the target device type (and its sub-devices, if selected). Depending on purpose, a template can contain a single attribute or dozens of attributes. When you use a template, SCM captures the values and flags of all listed attributes. This information makes up the new configuration. The configuration can then be stored as an SCM configuration model for the device type, or loaded directly on a device as a running configuration. Use templates to: Create device configurations for several models of a model type. Template libraries enable administrators to quickly and conveniently create a range of configurations. Delegate network responsibilities. The network expert can create templates; the network administrator can use the templates to capture device configurations. Initiate automatic captures with the Scheduler; see About the Scheduler [page 54]. Capture host configuration files. Make sure the device configuration contains only attribute/value pairs that can be retrieved from the target device. If SCM cannot capture a value for an attribute specified in a template, the attribute is not included in the configuration. Page 23

24 The Templates Window References See Setup > Templates [page 139]. Overview The Templates window displays any template models that exist for the model type. Selecting a template displays that template s information and attributes. The attributes can then be selected and edited. The Templates window looks similar to the Configuration Manager: Main window, except it displays information about templates rather than configurations. Details From the Templates window, you can: Create templates from the list of attributes for a device type. Edit templates by adding and deleting attributes. Copy, save, and delete templates. The Templates window lists all readable and writable attributes of the target device type you can select to create a template. When you use a template to capture a configuration, SCM: Searches the selected running configuration for attributes specified in the selected template(s). Captures values of the target attributes and includes the information in the new configuration. Might not be able to capture values for attributes specified in the template. If this is true, SCM indicates the attributes/values it could not retrieve, and does not include them in the configuration. You can manually insert other attributes later, if necessary. Page 24

25 Host Configuration Files References See Devices with Host Configuration Files [page 29]. See Setting Up Your Workstation as a TFTP Server [page 26] for information on setting up a TFTP server. Overview A host configuration file is a subset list of device-specific, readable, and writable attributes and their values. The file is in a text format that is both human readable and device readable. Some devices let SCM capture complete host configuration files. The captured host configuration files can then be edited with SCM. However, to enable configuration capture and loading, the administrator must first configure the SCM platform as a TFTP server (see Setting Up Your Workstation as a TFTP Server [page 26]). Note: If your device does not support TFTP access to its host configuration file, you must work with individual SNMP attributes to change device operation. Page 25

26 Setting Up Your Workstation as a TFTP Server If you are planning to work with model types listed in the *_MTYPES files (located in the <$SPECROOT>/SG-Tools/scm directory), you must perform additional steps after you install the Enterprise Configuration Manager. These devices use TFTP, Trivial File Transfer Protocol, to transfer configuration files. Therefore, if you want to configure these devices, you must make sure your workstation is set up as a TFTP server. For Solaris Machines Follow these steps to set up your workstation to support TFTP: 1. Become root (superuser). 2. Create the /tftpboot directory and give all users read/write permission to the directory. Type the following: mkdir /tftpboot chmod 777 /tftpboot 3. Make sure there is a tftp entry in the /etc/services file. To search for the entry, type: cd /etc grep tftp services You should see the following entry in the /etc/services file: tftp 69/udp If you don t see the tftp entry, enter it in the Host specific functions section. 4. In the /etc/inetd.conf file, find the following line and uncomment it by deleting the pound character (#) from the beginning of the line: #tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot Page 26

27 Make sure the entry ends with the -s /tftpboot option. This indicates the directory (in this case, /tftpboot) that will be used to serve files from. 5. Find the inetd process ID and reinitialize the process. a. Type the following command to get the inetd process ID: ps -ef grep inetd b. Notice the process ID number the first number in the line after the user ID. Then type: kill -1 <process_id> The kill command with the -1 (minus one) option reinitializes the process. 6. Now that your workstation is set up as a TFTP server, make sure that devices are modeled with the read/write community string for tftp transfer to work. Page 27

28 For Windows NT/2000 Machines Follow these steps to set up your Windows NT/2000 machine to support TFTP: 1. Navigate to the <$SPECROOT>\SG-Tools\scm\tftpboot directory. For example: C:\Win32App\Spectrum\SG-Tools\scm\tftpboot 2. By double-clicking on the file s icon, run tftpserv.exe This starts the TFTP server and displays a dialog box similar to that shown in Figure 1: Figure 1: TFTP Server Window The Start server button will be grayed out since the TFTP server will be running. 3. You can click the minimize or the Close button. Page 28

29 Devices with Host Configuration Files References See Loading Configurations [page 34]. Overview If a device allows host configuration file access: An Edit Host Configuration button appears at the bottom of the window after you capture or create a configuration. An Include Host Configuration button appears at the bottom of the window after you create a template. This function lets you select a new or edited template to capture the configuration of the target device. It also shows whether existing templates can capture the configuration. The two buttons defined above let you capture the host configuration file; then modify the commands, verify them, and load them to devices as part of the configuration. To resolve this: Note: If you create or capture a configuration that includes external list-type attributes with an OID reference, it generates the error message: No instance exists 1. Use the Model Type Editor to create an attribute identical to the one you need to use in configurations (but do not make it list-type) and 2. Use the new attribute in configurations to access and set the value on the device. If SCM and the device manufacturer support host configuration file capture, when you click a template name, the Include Host Configuration buttons display. If you select the Yes button (selected button appears indented), the template attempts to capture the host configuration file; if you select the No button, the template does not try to capture the file. If the device and/or SCM do not support host configuration file capture, the Include Host Configuration buttons do not display. Note: You can only capture the host configuration file using a template. Page 29

30 Selecting Devices and Host Configuration Files Overview Once you create a configuration, you can load it from the Configuration Manager: Main window as a device-specific or shared configuration. If you want to load a device-specific configuration to more than one device, you must capture it as a shared configuration first. After determining if the configuration is device-specific or shared, you can then load the configuration: As a device-specific configuration to the same device from which it was captured (a one-to-one load). As many individual device-specific configurations to many individual devices on a one-to-one basis (a many-to-many load). As one shared configuration to one specific device (a one-to-one load). As one shared configuration to many devices of the same type (a oneto-many load). Interface Models It is possible to capture a configuration from an interface model on one device and load it onto an interface model on another device. It is also possible to capture a configuration from an interface model on a device and load to another interface model on that same device. Device-Specific Configurations When working with a device-specific configuration, you can capture an interface configuration using the device model for that interface model. The interface configuration can then be loaded onto another interface of the same type via related device model. Shared Configurations If you are working with a shared configuration, you must open SPECTRUM Configuration Manager from that interface model (or another interface of the same model type) and perform the capture directly on the interface model involved. The configuration must then be loaded directly onto the appropriate interface model. Page 30

31 Host Configuration File Masking Overview Masking is used during the verify operation to ignore any line in the host configuration file that contains a specified mask string. Masking Host Configuration Files If you are working with a model type that supports host configuration transfers, you can add the Mask feature to a host configuration that has already been created or captured. Masking can be used for any line in the host configuration file. Any line in the host configuration file that begins with the specified mask string will be ignored in the Verify operation. Consider a configuration containing an encrypted password; the Host Configuration window will show a different encrypted sequence each time the password protected configuration is displayed. This situation will cause a Verify operation to fail, because the encryption will be different each time the password is read. Masking the password will allow the Verify operation to proceed successfully, as the password protected lines will be ignored. To mask the host configuration, proceed as follows: 1. In the Configuration window, select a configuration which contains the Host Configuration of a device listed in either the CISCO_MTYPES or SMARTSW_MTYPES files (located in the <$SPECROOT>/SG-Tools/scm directory). This situation enables the Mask button in the row of editing buttons located below the Device/Attribute/Flags/Value window (see Figure 2 [page 32]). 2. Click the Mask button to activate the Add Mask window (see Figure 2 [page 32]). If the current configuration contains Mask strings, the window displays those strings; otherwise the window will be empty. Page 31

32 Figure 2: The Add Mask Window Click in the text field of the Add Mask dialog box to enable insert/edit/ delete capability. a. If the Add Mask field is empty, type in the desired mask string(s), making sure that each different mask string begins on a new line. [Any host configuration line that begins with any mask string specified here will be ignored while doing a Verify comparison.] b. If the Add Mask field contains one or more mask strings but you wish to add more, proceed in the same way as described above, making sure that each added string is followed by a Return to establish a new line. c. If the Add Mask field contains an entry (or part of one) that you wish to remove or move to a different location, click on that entry to highlight it and then click on the Edit > Cut option (or use the Ctrl+X keyboard shortcut) to remove that entry. Since this action puts the removed text string in the buffer, you can move the cursor to a different location. and use the Edit > Paste function (or the Ctrl+V keyboard shortcut) to move the copied text to that new location, if desired. d. If the Add Mask field contains a mask entry that you wish to modify, you have flexible editing possibilities. You can click anywhere in an entry and type in new additional text as desired. You also can double-click in a term to highlight it, or sweep the mouse cursor through a sequence of terms to highlight that Page 32

33 sequence, or triple-click anywhere in the text to highlight the whole entry you can then replace the highlighted material simply by typing in the replacement text. Keep in mind, too, that the buffer acts as a conventional clipboard: whatever was last copied or cut remains available in the buffer for reconstruction with the Edit > Paste option (or the Ctrl+V keyboard shortcut). 4. When you have completed all desired changes, select the File > Update option. This action copies the edited Mask string(s) into the buffer, so that the new version will be saved when you save the SCM configuration in the Configurations window. 5. If you want a printout of the new configuration for your records, select the File > Print option. 6. Select the File > Close option to close the Add Mask window, returning you to the Configuration window. 7. In the Configuration window, select either the File > Save or the File > Save As option to save the modified host configuration (automatically including the information still stored in the buffer). [SCM stores the new configuration, associated with the added/edited mask strings, as a new version.] Page 33

34 Loading Configurations This section contains information on loading configurations to one or more target devices, and some potential solutions for load failures. In This Section Configuration Loading Details [page 35] Loading Configurations From the Configuration Manager: Main Window [page 37] Logging and Finding Load Results [page 39] What If a Load Fails? [page 40] Special Load Information for Devices with Host Configuration Files [page 42] Page 34

35 Configuration Loading Details References See Loading Configurations From the Configuration Manager: Main Window [page 37]. See SCM Alarms [page 73] for information on modifying the Load Failure alarms or turning them on/off. Overview Familiarize yourself with the following information before loading host configuration files: Selecting Landscapes You can expand all landscapes that contain the configurations you want to load, and all landscapes that contain the devices you want to configure. Once you expand the landscapes, the associated configurations and devices display. Selecting a Configuration Type There are two types of configurations: device-specific and shared. The default window is device specific (unless you change the default). Viewing the types separately helps prevent confusion. Viewing Device-specific Configurations This information displays as a three-level hierarchy. Device-specific configurations nest under their associated devices; each device nests under its associated landscape. Note: Be careful when loading shared configurations! It is possible to misconfigure devices and severely impact network operations. Viewing Shared Configurations This information displays as a two-level hierarchy. Shared configurations nest under their associated landscapes. Since shared configurations load to all selected devices, the configurations display in a separate device list below the configuration list. The name that appears in the device list is either the device you selected when you started SCM from SpectroGRAPH, or the device component you selected from the SCM Navigate Components option of the Configuration Manager: Main window. To choose a different type or range of devices, click the Choose button next to the device list; then select the target devices for the configuration. Page 35

36 Viewing Configuration Date Modified The date modified displays next to each configuration. To help you track configurations, the date modified changes with each save. Consequently, you can capture new configurations with the same name, because they are differentiated by the date and time of capture. Loading Device-specific Configurations In one operation, you can load a device-specific configuration to the same device from which it was captured, or load many device-specific configurations to the same devices from which they were individually captured (on a one-to-one basis). Loading Shared Configurations You can load a shared configuration to one device or many devices of the same type in the selected landscape(s). Viewing Load Statuses After a load, you can see the configuration load status in the Load Results area and the load detail results (attributes and the load status of each) in the Load Detail area of the Configuration Manager: Main window. Table 1: Load Status Messages Message Fully Loaded Not Loaded Partially Loaded Description The configuration and all its attributes are loaded on the device. The configuration did not load. See What If a Load Fails? [page 40]. Some attributes in the configuration did not load. Note: Read-only attributes cannot be loaded; check the load status for more information. Logging Load Results The load summary results are stored in the SPECTRUM event log; see About the SPECTRUM Event Log and the SCM Log File [page 59]. Modifying Load Failure Alarms You can modify or turn off the Load Failure alarms that appear in SPECTRUM. Page 36

37 Loading Configurations From the Configuration Manager: Main Window References See What are Configurations? [page 13]. See Configuration Loading Details [page 35]. See Options > Load... [page 118]. Overview You should understand the following Configuration Manager: Main window details before loading a configuration: Device landscapes for locating configurations and devices. Load button. Load status codes. Load setting options. Description Configuration List Box Use this area to locate configurations and devices in that target landscape(s); see Figure 6 [page 149]. Load Status Codes The Load Status column in the Configuration Manager: Main window indicates the load status of your configurations. When you create and load configurations, SCM automatically updates the load statuses. Page 37

38 Table 2: Load Status Codes StatusCode Meaning Description L Fully Loaded The configuration and all its attributes are loaded on the device. Not Loaded The configuration did not load. See What If a Load Fails? [page 40]. P Partially Loaded Some attributes in the configuration did not load. Load Scenarios Configuration loading is a device-specific process. Some devices let you load a configuration as the running configuration and the startup configuration; some let you only load a configuration as the running configuration (and make you use local management to manually load the configuration as the startup configuration); still others let you only load a configuration as the startup configuration and make you reboot the device to copy it over as the running configuration. See Figure 7 [page 150]. SCM tries to provide the same degree of user control over the configuration load process as the device manufacturer allows through SNMP access. For example, if a device manufacturer lets you load a configuration as the startup configuration, you see a selectable Commit Loaded configuration to NVRAM button in the configuration load dialog box. If the device manufacturer does not permit this operation, the button is not included in the dialog box; see Options > Load... [page 118]. In this case, to save the configuration as the startup configuration, you must manually save the configuration using local device management. You can change the default setting for the Commit Loaded configuration to NVRAM button: For the current SCM session by using the SCM Preferences dialog box; see Preferences Menu [page 105]. As a permanent SCM change by editing the Scm resource file; see Scm Resource File [page 66]. Page 38

39 Logging and Finding Load Results References See About the SPECTRUM Event Log and the SCM Log File [page 59]. Overview SCM logs events to the SPECTRUM landscape that contain the particular configuration, template, or device. The SPECTRUM event log saves information about: When a configuration was loaded. Who loaded the configuration. The status of the load process. You can find information on the: Historical record of loads in the SPECTRUM event log. Latest statuses of loads in the Configuration Manager: Main window (Device Specific window and Shared window). Load details in the Load Detail window. Note: SCM does not save the detailed load result information about the status of each attribute. Page 39

40 What If a Load Fails? References See SCM Alarms [page 73] to change the alarm color or turn the alarm function off. See Interpreting SCM Event Codes [page 62] and SCM Event Codes [page 63]. Overview Any load operation that fails to load an attribute is a load failure. In addition to displaying the configuration load failure details in the Load Detail window, all load failures generate an alarm in SpectroGRAPH by default. SpectroGRAPH indicates a load failure alarm condition by making: The device flash yellow in the Topology view. An alarm entry appear in the Alarms window. An alarm event be written to the event log. Details Note: SCM alarm defaults are set at installation. After installation, you can change the alarm color or turn the alarm function off. Table3 [page41] contains information about resolving load failure issues. Page 40

41 Table 3: Troubleshooting for Configuration Load Failures Issue A configuration fails to load to one or more devices. Solution - Make sure the community names are correct. - Check the device connection and reconnect it if it is not connected. - Check to see if the same configuration was previously loaded correctly. - View the load result details and find the attribute that failed. Eliminate that attribute from the configuration and reload the configuration. If it works, create a separate configuration for the failed attribute and then load that. (The failed attribute might require another attribute to be set before it can be loaded.) - Break the configuration into smaller configurations to locate a hard-to-find problem. - For the scheduled task, check the result details in the log for the scheduled operations. - Check to see if the attributes contained in the configurations are writable. Solaris Only - Need to enable TFTP; see Setting Up Your Workstation as a TFTP Server [page 26]. Windows NT/2000 Only - Check to see if the Task Scheduler service is running. - Check to see if the TFTP executable (tftpserv.exe) is running. Page 41

42 Special Load Information for Devices with Host Configuration Files References See What are Configurations? [page 13]. See Devices with Host Configuration Files [page 29] Overview If the target SCM configuration model includes a host configuration file, you can view the host configuration load results in the Load Detail window. This includes the name <Host Configuration> in the Attribute field and the status (Success, Failure, or other error messages) in the Load Status field. SCM attempts to load both the attributes and host configuration file, even if some attributes cannot be loaded to the device. In the Load Detail window, the load status for the host configuration commands can be either Success or Failure. Page 42

43 Verifying Host Configuration File Captures This section contains information about confirming the successful or unsuccessful capture statuses of host configuration files. In This Section Verifying the Configuration Capture Status [page 44] What if a Verification Fails? [page 45] Verification Options [page 46] Page 43

44 Verifying the Configuration Capture Status References See What are Configurations? [page 13]. Overview SCM captures the running (loaded) configuration from the selected device. It then compares each attribute/value pair in the captured configuration with the SCM configuration model in the SpectroSERVER database. Once the comparison is complete, SCM displays the results in the Verify Results and the Verify Detail windows. If a verification fails, the information is saved to the SpectroSERVER database with the same name but a different date/time stamp, so you can see the state of the device when it failed. Page 44

45 What if a Verification Fails? References See SCM Alarms [page 73] to verify the alarm color or turn the alarm function off. See Interpreting SCM Event Codes [page 62]. Overview By default, all SCM verification failures generate an alarm in SpectroGRAPH. SpectroGRAPH indicates a verify failure alarm by: Making the device flash orange in the Topology view. Displaying an alarm entry in the Alarms window. Writing an alarm event to the event log. Page 45

46 Verification Options References See What are Configurations? [page 13]. See Devices with Host Configuration Files [page 29]. See SCM Alarms [page 73] to turn the alarm function off. Overview The verification process tells you whether the running configuration matches the SCM configuration model of the selected device, or other devices of the same type. If the configurations do not match, SCM tells you why. When verifying a configuration, you can also verify the host configuration file of either the selected device or other devices of the same type. Note: The verification process ignores additional lines when done with a shared configuration and will continue to do a line by line comparison for device specific configurations. Page 46

47 About Security in SPECTRUM Configuration Manager This section contains information on setting security features in SCM that either allow or restrict access to devices and files. In this section Security Features [page 48] Hiding Passwords, Keywords, or Tokens [page 52] Viewing and Editing Host Configuration Passwords [page 53] Page 47

48 Security Features References See Table4 [page51] for SCM community string definitions. Overview SCM is a powerful network configuration management tool that gives users the ability to quickly reconfigure large numbers of devices from any location on a network. It is not intended for novice users; it is intended for network administrators and technicians who understand how to manually configure network devices. An inexperienced user could easily reconfigure devices that are central to a network and adversely impact network performance. SCM uses two levels of security that help administrators manage the risks associated with using this application. SNMP security controls user access to single devices. SCM security controls user access to all network management operations for each device. Page 48

49 SNMP Security Administrators can control access to network devices by assigning each user an SNMP community name, which gets stored on the device and in the SpectroSERVER database. If the community name on the device and the community name in the database do not match, the user cannot access the device. The administrator can also control device access with the read and write privileges specified in the SNMP community name. To run all SCM operations, both read and write access are necessary. If an SNMP community name on a device specifies only read access, the respective user cannot load configurations to the referenced device. Page 49

50 SCM Security SCM community strings provide a layer of security beyond SNMP security. A community string can have one or more parts, each part specifying permissions for a certain community. User access to devices is defined in the second part of the community string; see Table 4 for SCM community string access levels. Note: Although other community name prefixes can allow access to network devices, Aprisma recommends always assigning an ADMIN,0 prefix to SCM community strings. The ADMIN portion of the community string does not override the device access defined by the SCM portion of the community string. For example, the community string ADMIN,0:SCM,3 gives a user access to all SPECTRUM administration privileges, but only view, verify, and load privileges in SCM. Administrators should be careful when assigning SCM community strings to users so each user has appropriate access to SCM operations. The correct community string format is: ADMIN,#:SCM,# (Where # equals the appropriate single-digit access code.) When creating SCM community strings, consider that ADMIN,0 ADMIN,1 or ADMIN 2 (without an additional SCM community string) give a user full access to SCM. Page 50

51 Table 4: SCM Community Strings and Associated Access Community String SCM,0 SCM,1 SCM,2 SCM,3 SCM,4 SCM,5 SCM,6 SCM,7 SCM,8 SCM,9 Associated Access View, verify, and load configurations; create/edit templates and configurations. The user can access all operations in all SCM windows. View and verify configurations; create/edit templates and configurations. The user can access all SCM operations in the Configuration Manager: Main window except the load option, which is grayed out. View, verify, and load configurations. The user can access all operations in the Configuration Manager: Main window except the capture option, which is grayed out. Access to the Templates window is denied. View and verify configurations. The user can access only limited operations in the Configuration Manager: Main window; the capture option and load option are grayed out. Access to the Templates window is denied. Page 51

52 Hiding Passwords, Keywords, or Tokens References See Figure 5 [page 148]. Overview The SECURITY_TOKENS file defines which lines are hidden when you view and verify host configurations for devices listed in the model type files in the <$SPECROOT>/SG-Tools/scm directory. Administrators can use this file to hide passwords, keywords, and tokens for security purposes by duplicating the setup command syntax used in the file. Note that the following keywords/tokens are hidden by default: system set hashed-password snmp-set community enable-password snmp-server community password You can hide passwords, keywords, or tokens in host configuration files for certain devices. Page 52

53 Viewing and Editing Host Configuration Passwords References See Figure 38 [page 181]. See Security Features [page 48]. Overview You can view and edit host configuration passwords if you access (see Options > Edit Host Configuration... [page 181]) the host configuration file through the Edit Host Configurations window. Hidden passwords and keywords are visible only from the Edit Host Configurations window. Note: The Edit Host Configurations window can be viewed only by users who have SCM,0 SCM,1 or SCM,2 privileges. Page 53

54 About the Scheduler This section covers information about using the Scheduler feature in SCM to automate functions, and customize the Scheduler for your business environment. In This Section Why Schedule Operations in SCM? [page 55] About the Windows NT/2000 Task Scheduler Service [page 56] Working With the Scheduler [page 57] Viewing the Results of Scheduled Operations [page 58] Page 54

55 Why Schedule Operations in SCM? References See About the Windows NT/2000 Task Scheduler Service [page 56]. See Interpreting SCM Event Codes [page 62] for information on the SPECTRUM event log and the SCM log file. Overview SCM provides administrators with the option of scheduling the time and frequency of automatic captures, loads, and verifications. This feature has several benefits. Specifically, the administrator can: Schedule loads, captures, and verifications during low-traffic hours. Maintain more stable configurations by scheduling automatic loads at regular intervals. Check the integrity of the network with periodic, automatic captures and verifications of configurations. Automate many of the day-to-day configuration management operations. SCM sends information about the operations that the Scheduler performs to the SPECTRUM event log and the SCM log file. In these two files, you can view the results of any operation initiated by the Scheduler. Note: The Scheduler displays time in a 24-hour format. Page 55

56 About the Windows NT/2000 Task Scheduler Service References See the SPECTRUM Installation Guide (0675) for information on setting up the Windows NT/2000 Task Scheduler service. Overview Windows NT/2000 uses the Task Scheduler service instead of the cron utility to schedule SCM operations. Windows NT/2000 users should make sure the Task Scheduler service is set up properly before scheduling tasks in SCM. Page 56

57 Working With the Scheduler References See Options > Schedule... [page 123] for descriptions of the Scheduler dialog box buttons. Accessing the Scheduler To access the scheduler, first select what you want to schedule then click the Schedule button/option. The SCM Schedule button is located in the Configuration Manager: Main window; it lets you schedule captures, loads, and verifications for the selected device(s). Use the Scheduler editing options to: Change entries before and after saving them to the scheduled queue. Remove entries from the Scheduled Entries field and the scheduled queue. A scheduled entry has two parts: the scheduled time at the beginning of the line, and the command (enclosed in quotes) which comprises the rest of the line. To learn about modifying the schedule, experiment with the options. If you enlarge the Scheduler dialog box by dragging the corners, you can view the whole entry. Page 57

58 Viewing the Results of Scheduled Operations References See About the SPECTRUM Event Log [page 60]. See About the SCM Log File [page 64]. Overview You can view the results of scheduled operations in two places: The SPECTRUM event log. The event log, accessed in SpectroGRAPH, contains basic information about each operation, such as the operation time, operation status (success or failure), device name(s), configuration(s), and template(s), when applicable. The SCM log file. (by default, scmbg.log located in <SCM directory>/log) The SCM log file contains more detailed information about the scheduled operation. In addition to the basic information that you would see in the event log, it contains a listing of attribute names and the status of attributes, if appropriate. Note: Both the manual SCM operations and the scheduled SCM operations are logged in the SPECTRUM event log. However, only scheduled operations are logged in the SCM log file. Page 58

59 About the SPECTRUM Event Log and the SCM Log File This section contains information about the means to view SCM operation status. In This Section About the SPECTRUM Event Log [page 60] How to Use the SPECTRUM Event Log [page 61] Interpreting SCM Event Codes [page 62] About the SCM Log File [page 64] Page 59

60 About the SPECTRUM Event Log References See the Event Log (2583) for detailed information on the SPECTRUM event log. Overview SPECTRUM constantly maintains a log of events that occur on networks. These events can be routine (for example, when a user establishes a session with SPECTRUM) to critical (when a configuration status changes). Network administrators should check the SPECTRUM event log frequently for information on network configuration changes. When the Scheduler initiates an SCM operation, the results are written to the event log, which contains the following information: The time and date of the SCM event. The words Configuration Manager after the date and time. The operation that was performed (for example, load, capture, verify, create, modify, or delete). A status of whether or not the operation was successful. The name of the user who performed the operation. The names of configurations, templates, devices, and device types, when appropriate, and the landscapes where they are located. The event code number that identifies the type of SCM operation performed. A text explanation of the event. Note: The event log does not distinguish between operations performed directly by the user and operations performed by the Scheduler. Page 60

61 How to Use the SPECTRUM Event Log References See the Event Log (2583) for detailed information on the SPECTRUM event log. See Interpreting SCM Event Codes [page 62]. Overview The SPECTRUM event log provides administrators with not only a history of events that occurred on the network, but also information that can be used to manage the network. Following are a few ways to use the SPECTRUM event log with SCM: The event log filter lets you perform searches in the event log. If you schedule automatic verifications of configurations, you can then use the event log filter to search for (verification failure). This is a quick way to see which configurations have changed. You can also key the event log search to a model name, model type name, and/or user name to find information about a specific model, model type, or user. You can scroll to a specific time in the event log and see what events took place. Page 61

62 Interpreting SCM Event Codes References See the Event Log (2583) for detailed information on the SPECTRUM event log. See How to Use the SPECTRUM Event Log [page 61]. See Table5 [page63] for a listing of SCM event codes. Overview Each event log entry ends with an SCM event code that identifies the operation performed, and the success or failure of the operation. Use these event codes when you search in the SPECTRUM event log. Page 62

63 Table 5: SCM Event Codes Event Code Type of SCM Event Configuration created Configuration creation failed Configuration loaded to a device Configuration load failed Configuration captured from a device Configuration capture failed Configuration verified Configuration verification failed Configuration modified Configuration modification failed a b c d e f Configuration deleted Configuration deletion failed Template created Template creation failed Template modified Template modification failed Template deleted Template deletion failed Capture partial success Load partial success Page 63

64 About the SCM Log File References See Scm Resource File [page 66] for information on editing the Scm resource file. Overview The SCM log file is updated by the Scheduler; it contains more detailed information about scheduled operations than the SPECTRUM event log. For example, the SCM log file contains status information for specific attributes from a scheduled configuration load, verification, or capture. For a scheduled load The file indicates the attribute/value pairs that did not load successfully. If the configuration includes a host configuration file, the words <host configuration> appear in the Attribute list, and the load status of the host configuration file appears in the Error list. For a scheduled verification The file contains only the attribute/value pairs that did not match. The attributes/values pairs from the configuration and the device appear on adjacent lines so they are easy to compare. If the configuration includes a host configuration file, the non-matching command lines of the host configuration file and the device s host configuration appear on adjacent lines so they are easy to compare. For a scheduled capture The file contains only the attributes that were not captured successfully. If the host configuration file was not captured successfully, the words <host configuration> appear in the Attribute list and the error code appears in the Error list. Note: After the Scheduler completes a task, SCM logs the results in the SCM log file, appending the new entry to the other entries. As a result, the log file can become very large. It is a good practice to check the SCM log file periodically and delete old entries. By default the scmbg.log file is located at <$SPECROOT>/SG-Tools/scm/ log/. However, you can specify a different name and location for the file by editing the Scm resource file. Page 64

65 About the Scm Resource File This section describes the parameter values in the resource file Scm. In This Section Scm Resource File [page 66] Keyboard Shortcuts for Menu Items [page 72] Page 65

66 Scm Resource File References See Table 6: Scm Resource File Timeout and Pathname Parameters [page 67]. See Table 7: Scm Resource File Operational Parameters [page 68]. See Table 8: Scm Resource File Display Parameters [page 70]. Overview The Scm resource file is located in the <$SPECROOT>/app-defaults directory; it contains three groups of parameters used by SCM: Timeout and Pathname Parameters Includes mail service timeout, handshake timeout for socket creation, and the path(s) to SCM utilities and files. Display Parameters Define the fonts and colors used in SCM windows. You can specify the display parameters only in the Scm resource file. Although parameter values in the resource file are set at installation, you can edit the file at any time. However, the new values only take effect once you restart SCM. Note: When modifying the Scm resource file, be aware that: YES, TRUE, ON, and 1 are equivalent. NO, FALSE, OFF, and 0 are equivalent. Page 66

67 Table 6: Scm Resource File Timeout and Pathname Parameters Timeout or Pathname Parameter DcmTimeoutvalue DefaultTimeout VnmConnectionTimeout ScmPath ScmLogFile TftpfilePath Description and Default Value Server timeout in milliseconds waiting for device to reply. Default: 6000 milliseconds (6 seconds) Mail service timeout in milliseconds. Default: milliseconds (100 seconds) Handshake timeout for the creation of sockets used by the mail service and its servers. Default: 20 seconds Path for locating SCM utilities and associated data file. Default: <$SPECROOT>/SG-Tools/scm Name of the background task log file. Default: <$SPECROOT>/SG-Tools/scm/log/scmbg.log The default tftp server setting path. Windows NT: <$SPECROOT>/SG-Tools/scm/tftpboot Solaris: /tftpboot Page 67

68 Table 7: Scm Resource File Operational Parameters Operational Parameter Committonvram ScmShowSharedConfigs ScmSearchOption AttributeFlags AlwaysRetrieveAttributes CaseSensitive SearchDefault modelnamedisplaylength Description and Default Value Specifies whether to commit the device s configuration non-volatile RAM after download. Default: ON Specifies whether shared or device-specific configurations display first at startup. Valid values: YES show shared configurations; NO show device specific configurations. Default: YES Specifies how the Search operation functions. Valid values: YES use the extended search function; NO use the regular search function. Default: NO Specifies which attribute flag(s) to test when retrieving the attributes and values for the insertable attributes list in both the Configurations and Templates windows. The list of flags should be comma separated. Valid values: readable, writable, internal, external Default: readable, writable, internal, external Specifies whether SCM polls the device each time when retrieving the attributes for the insertable attributes list in both the Configurations and Templates windows, for every configuration or template selection. Valid values: YES always retrieve attributes; NO only retrieve attributes the first time. Default: NO Specifies the default case-sensitivity for Search and Filter. Valid values: 0 = case insensitive; 1 = case sensitive. Default: 1 Specifies whether Search or Filter is the default operation at startup. Valid values: 0 = filter default; 1 = search default. Default: 1 Specifies the maximum number of characters in a model name to display. Valid values: 1 <= length <= 1024 Default: 1024 Page 68

69 Operational Parameter LongModelNamePopup Description and Default Value Specifies whether a popup window is required when a long model name is selected. Valid values: YES display a popup window; NO do not display a popup window. Default: NO Page 69

70 Table 8: Scm Resource File Display Parameters Display Parameter BackgroundColor FrameBackgroundColor MenuColor LabelColor SearchHighlightColor OverviewSelectionColor FontAliasFile WindowTextColor MenuTextColor DarkBackgroundColor SelectionColor LabelFont ListFont Description and Default Value Colored border in all windows. Default: 208 (baby blue SCM blue) Window background color in all windows. Default: 251 (medium gray) Menu background color in all windows. Default: 251 (medium gray) Foreground color for text in all windows. Default: 45 (black) Color used to indicate whether search or filter is active. Default: 170 (yellow). Color used to indicate selected entries in the Navigational Overview window. Default: 170 (yellow). Specifies the file to search when a given font cannot be found. Default: <$SPECROOT>/spectrum.fonts Foreground color for text in all windows. Default: 245 (black) Foreground color for text in all windows. 245 (black) Highlight color and scroll bar trough color in all windows. Default: 249 (dark gray) Color for toggle buttons when selected. Default: 249 (dark gray) Font used in labels and push buttons. Default: -*-helvetica-medium-r-normal--* p-*- iso Font used in lists. Default: -*-courier-medium-r-normal--* m-*- iso Page 70

71 Display Parameter MenuFont TextFont draginitiatorprotocolstyle dragreceiverprotocolstyle Description and Default Value Font used in menus. Default: -*-helvetica-medium-r-normal--* p-*- iso Font used in text entry fields. Default: -*-helvetica-medium-r-normal--* p-*- iso Drag and drop parameter, disabled because it causes problems. Default: XmDRAG_NONE Drag and drop parameter, disabled because it causes problems. Default: XmDRAG_NONE Page 71

72 Keyboard Shortcuts for Menu Items References See Scm Resource File [page 66]. Overview These parameters define the keyboard shortcuts used to initiate SCM menu item actions. You can specify these parameter values only in the Scm resource file. Table 9: Keyboard Shortcuts for Menu Items SCM Parameter cut_button.accelerator cut_button.acceleratortext copy_button.accelerator copy_button.acceleratortext paste_button.accelerator paste_button.acceleratortext Description and Default Value Ctrl<Key>x Ctrl+X Ctrl<Key>c Ctrl+C Ctrl<Key>v Ctrl+V Page 72

73 SCM Alarms This section describes how to modify, turn off, or clear SCM alarms in SPECTRUM. Reference See About the SPECTRUM Event Log and the SCM Log File [page 59] for information about SCM event codes. Understanding and Modifying SCM Alarms in SPECTRUM SPECTRUM Alarms, which are visible in SpectroGRAPH, show you when an SCM load or a verification fails. By default, SPECTRUM generates a yellow alarm for the load failure and an orange alarm for the verification failure. This section shows you how to change the color of the Alarm and to turn off SCM alarms completely. SCM Events that Trigger Alarms in SPECTRUM Two events in SCM trigger alarms in SpectroGRAPH: Load Failure (Event Code ). Verify Failure (Event Code ). How SPECTRUM Notifies You of an SCM Alarm When an SCM load or verification fails, SPECTRUM notifies you in the following ways: In the Topology View, the icon of the model displays an orange alarm for a Verify Failure or yellow alarm for a Load Failure. The Alarms window displays an alarm entry for the SCM alarm. The Event Log displays two entries for each alarm, one for the event of Load Failure or Verify Failure and one for the event of generating an alarm. Page 73

74 How to Modify, Turn off, or Clear SCM Alarms SCM alarm features are added to SPECTRUM when you install SCM. Although you cannot change the types of alarms that are generated, you can modify the color of the alarm, turn off the alarms altogether, or clear them. To modify colors or turn off SCM alarms: 1. Navigate to the <$SPECROOT>/SS/CsVendor/Ctron_SCM directory. 2. Open the EventDisp file with a text editor and locate the following lines, which generate alarms for Load Failure and Verify Failure: 0x E 50 A 1, 0x x E 50 A 2, 0x To turn off one or both alarms, delete the appropriate line(s) from the file: 0x generates the alarm for Load Failure. 0x80007 generates the alarm for Verification Failure. To change the color of an alarm, change the number that follows the A and precedes the comma. The choices you have are: 1 - YELLOW (Minor)CONDITION/Severity 2 - ORANGE (Major) CONDITION/Severity 3 - RED (Critical)CONDITION/Severity 3. After you have modified the EventDisp file, bring down SpectroSERVER and start it up again. The SpectroGRAPH will then display the modified SCM alarms. To clear an alarm: 1. Select the alarm in the Alarms window. 2. Click on the Clear option under the Tools menu. See Getting Started with SPECTRUM for Administrators (0985) for more information about alarms. Page 74

75 Running SCM from the Command Line This section describes how to perform SCM operations from the command line. The section displays the commands in a modified man page format. In This Section Using SCM Commands [page 76] Requirements for using SCM commands Invoking SCM [page 77] How to start SCM Capturing a Configuration from a Model [page 78] How to capture a configuration Loading a Configuration to One or More Models [page 79] How to load a configuration Verifying a Configuration to One or More Models [page 80] How to verify a configuration Importing Configurations and Templates [page 81] How to import templates and configurations Exporting Configurations and Templates [page 82] How to export templates and configurations Page 75

76 Using SCM Commands SCM commands require information such as model names and model type handles, which you retrieve through the Command Line Interface (CLI) commands. Therefore, unless you are an experienced CLI user, do not attempt to run SCM with the commands in this section. To run SCM from the command line: 1. Make sure the SpectroSERVER is up and running. 2. Navigate to the directory where the SCM command is located. See the Location category under each command. 3. To check the syntax of a CLI command, go to the directory where the command is located and type the first word of the command. Or in any directory, type the complete pathname along with the command. To see the syntax of an SCM command (for example, load, verify, or capture), in the <$SPECROOT>/SG-Tools/scm/bckgrnd> directory, use the following syntax: scmbg -f command For example: scmbg -f capture or <$SPECROOT>/SG-Tools/scm/bckgrnd/scmbg -f capture 4. Use CLI to find the input information required by the command. 5. Enter the command in the format described in this section or in the command line description. If commands require a data file, create a file with the information required. Use the following format for the file: *vnmsocket: 0xbeef *DefaultTimeout: *ScmPath: /usr/data/spectrum/sg-tools/scm *ScmLogFile: /usr/data/spectrum/sg-tools/scm/log/scmbg.log *ModelHandles: 0x6801eb, 0x6801ae, 0x *DeviceHandles: (used only with the -ds argument) Page 76

77 Invoking SCM Scm start Configuration Manager Location <$SPECROOT>/SG-Tools/scm directory Syntax Scm \ -vnm <SpectroSERVER host name> \ -vnmsocket <VNM socket number> \ -mh <device model handle> Input -mh Model handle of the device you are going to work with -vnm SpectroSERVER to which you are connecting -vnmsocket Socket number on the SpectroSERVER Page 77

78 Capturing a Configuration from a Model scmbg -f capture capture a configuration from a model Location <$SPECROOT>/SG-Tools/scm/bckgrnd directory Syntax scmbg -f capture \ -vnm <SpectroSERVER host name> \ -file < data file name> \ -ds (capture in device specific mode) -cname <SCM output configuration name> [-dhc (dump host config)] \ [-path <host config output path>] Input -vnm SpectroSERVER to which you are connecting -file Data file containing the following parameters and their values: Vnmsocket, DefaultTimeout, ScmPath, ScmLogFile, DeviceHandles (device model handles), and ModelHandles (template model handle(s)) -ds Capture in device specific mode -cname Name of the captured configuration -dhc Dump host configuration to a file (See [page 79]) -path Host configuration output path Page 78

79 Note: For capture and verify, you can specify a -path that includes a format string. The allowed fields in the format string = Config = Device Name, = Landscape/Server Name, as well as format specifiers allowed by strftime. Note that the file name will always be "@D_@C.txt". You can also use the -dhc and - path options alone to cause scmbg to write all device specific configurations to disk. Loading a Configuration to One or More Models scmbg -f load load a configuration to model(s) Location <$SPECROOT>/SG-Tools/scm/bckgrnd directory Syntax scmbg -f load \ -vnm <SpectroSERVER host name> \ -file <the Data-File name which will contain \ vnm socket and timeout; \ SCM directory path, log file path, dcm_timeout, \ device model or configuration model handles> \ -ds (load device specific configurations) -nv <copy to nvram flag, ON or OFF> \ Input -vnm SpectroSERVER to which you are connecting -file Data file containing the following parameters and their values: Vnmsocket, DefaultTimeout, ScmPath, ScmLogFile, ModelHandles (device model handle(s)) or ConfigHandles (configuration model handle(s)), used only with the -ds argument Page 79

80 -ds Load device specific configuration -nv Commit the loaded configuration to the selected device s non-volatile RAM (NVRAM), ON or OFF Verifying a Configuration to One or More Models Note: Verify will ignore additional lines when done with a shared configuration. It will continue to do a line by line comparison for device specific configurations. scmbg -f verify verify one or more models Location <$SPECROOT>/SG-Tools/scm/bckgrnd directory Syntax scmbg -f verify \ -vnm <SpectroSERVER host name> \ -file <the Data-File name which will contain \ vnm socket and timeout; \ SCM directory path, log file path, dcm_timeout, \ device model or configuration model handles> \ -ds (verify device specific configurations) \ [-dhc (dump host config)] \ [-path <host config output path>] Input -vnm SpectroSERVER to which you are connecting -file Data file containing the following parameters and their values: Vnmsocket, DefaultTimeout, ScmPath, ScmLogFile, ModelHandles (device model handle(s)) or ConfigHandles (configuration model handle(s)), used only with the -ds argument Page 80

81 -ds Verify device specific configuration -dhc Dump host configuration to a file (See [page 79]) -path Host configuration output path (See [page 79]) Importing Configurations and Templates import import configurations and/or templates Configuration files used with import must contain model handles that are valid for the destination SpectroSERVER. Configuration files exported using the export tool (see Exporting Configurations and Templates [page 82]) contain model handles that are only valid for the SpectroSERVER the file was exported from. Without first modifying a given file created with export, that file can only be imported into the originating SpectroSERVER. To import an exported configuration file into a SpectroSERVER other than the originating SpectroSERVER, you must first edit the file so that the model handles correspond to devices on the destination SpectroSERVER. Location <$SPECROOT>/SG-Tools/scm/bckgrnd directory Syntax import \ -vnm <SpectroSERVER host name> \ -port <VNM socket number> \ -clh <create landscape handle> \ -file <data-file name> \ -ecmpath <SCM directory path> \ -time <VNM timeout> Input -vnm SpectroSERVER to which you are connecting -port Page 81

82 VNM socket number -file The file created by export Options -ecmpath SCM directory path -clh Landscape handle of SpectroSERVER where configuration will be saved -time VNM timeout value (The minimum and default value is 5,000). Exporting Configurations and Templates export retrieve templates/configurations, print output to the screen Location Note: The export command directs output to your screen. Therefore, whenever you use the export command, be sure to redirect the output to a file. To do this, use the redirection symbol (>) and specify the destination filename. Later, you can import configurations and templates from this file (see Importing Configurations and Templates [page 81]). <$SPECROOT>/SG-Tools/scm/bckgrnd directory Syntax For specifying one SCM configuration model handle: export \ -vnm <SpectroSERVER host name> \ -port <VNM socket number> \ -ch <SCM configuration model handle> \ -ecmpath <SCM directory path> \ -time <VNM timeout> Page 82

83 For specifying one SCM template model handle: export \ -vnm <SpectroSERVER host name> \ -port <VNM socket number> \ -th <SCM template model handle> \ -ecmpath <SCM directory path> \ -time <VNM timeout> For specifying one SCM configuration name and model type handle: export \ -vnm <SpectroSERVER host name> \ -elh <export landscape handle> \ -port <VNM socket number> \ -mth <model type handle> \ -cn <SCM configuration name> \ -ecmpath <SCM directory path> \ -time <VNM timeout> For specifying one SCM configuration name and model type name: export \ -vnm <SpectroSERVER host name> \ -elh <export landscape handle> \ -port <VNM socket number> \ -mtn <model type name> \ -cn <SCM configuration name> \ -ecmpath <SCM directory path> \ -time <VNM timeout> For specifying one SCM template name and model type handle: export \ -vnm <SpectroSERVER host name> \ -elh <export landscape handle> \ -port <VNM socket number> \ -mth <model type handle> \ -tn <SCM template name> \ -ecmpath <SCM directory path> \ -time <VNM timeout> For specifying one SCM template name and model type name: export \ -vnm <SpectroSERVER host name> \ -elh <export landscape handle> \ -port <VNM socket number> \ -mtn <model type name> \ -tn <SCM template name> \ -ecmpath <SCM directory path> \ -time <VNM timeout> Page 83

84 For specifying all SCM configuration models: export \ -vnm <SpectroSERVER host name> \ -elh <export landscape handle> \ -port <VNM socket number> \ -ac \ -ecmpath <SCM directory path> \ -time <VNM timeout> For specifying all SCM template models: export \ -vnm <SpectroSERVER host name> \ -elh <export landscape handle> \ -port <VNM socket number> \ -at \ -ecmpath <SCM directory path> \ -time <VNM timeout> For specifying all SCM models: export \ -vnm <SpectroSERVER host name> \ -elh <export landscape handle> \ -port <VNM socket number> \ -a \ -ecmpath <SCM directory path> \ -time <VNM timeout> Input -a All templates and configurations (no value needed) -ac All configurations (no value needed) -at All templates (no value needed) -ch SCM configuration model handle -cn SCM configuration name -elh Landscape handle of destination SpectroSERVER for export Page 84

85 -mth Model type handle -mtn Model type name -port VNM socket number -th SCM template model handle -tn SCM template name -vnm SpectroSERVER to which you are connecting Options -ecmpath SCM directory path -time VNM timeout value (The minimum and default value is 5,000). Page 85

86 The User Interface Most SCM work is completed in the Configuration Manager: Main window, the Configurations window, and the Templates window. This section describes the Configuration Manager: Main window and its subordinate views. In This Section Starting SCM [page 87] Configuration Manager: Main Window [page 87] Device Specific Configurations Window [page 92] Shared Configurations Window [page 93] SCM: Templates Window [page 94] Page 86

87 Starting SCM Procedure To start SCM: 1. Select the device icon of the model you want to invoke SCM for. 2. Right-click the device icon an choose Utilities > Configuration Manager. Configuration Manager: Main Window Prerequisites Start SpectroGRAPH. Start SCM: see Starting SCM [page 87] References See Figure 6 [page 149]. See Configuration List Box [page 89]. See Configuration Information Section [page 90]. See Search/Filter Option [page 91]. Definitions A shared configuration can be loaded to multiple devices of the same type. A device-specific configuration can be loaded only to the same physical device from which it was captured. Overview After selecting a device in SpectroGRAPH and starting SCM, the Configuration Manager: Main window displays. From this window, you can: View all device-specific configurations of the same device type, to include load status. View all shared configurations of the same device type to include load status. Capture configurations from multiple devices of the same type. Load and verify device-specific configurations to multiple devices of the same type on an individual basis. Page 87

88 Load and verify a shared configuration to multiple devices of the same type. Schedule automatic loads and verifications. Compare two device configurations. Description See Figure 6 [page 149] for a graphic of the Configuration Manager: Main window. Toolbar Buttons (A) Provide graphic shortcuts to specific functions as an alternative to selections on the pull down menus. To identify a button, hover the cursor over the button and its name appears. Pull Down Menus (B) Give access to all SCM functionality. See Pull Down Menus Main Window [page 99]. Navigational Overview Window (C) A navigational aid. The rectangle box indicates the relative position of the screen view within the complete contents of the Configuration list box. Window Title Bar (D) Includes a description of the active window, indicates whether the displayed configurations are shared or devicespecific, and identifies the selected device type. Configuration List Box (E) Contains the names of configurations created for device models of the same type as the selected device in SpectroGRAPH or in the SCM Components dialog box. See Configuration List Box [page 89] for information about this interface feature. Configuration Information Section (F) Contains historical information about the selected configuration. See Configuration Information Section [page 90]. Search/Filter Option (G) A tool that helps search the contents of the Configuration list box. See Search/Filter Option [page 91]. Page 88

89 Configuration List Box References See Figure 8 [page 151]. Description Landscape Name (A) Appears flush left in the list. Double-click a landscape name to expand or collapse it. An expanded landscape shows all configurations associated with it. A collapsed landscape displays only the landscape name. The specific landscapes that display in the window are user-definable. You can identify which landscapes to display by editing: The SCM Preferences dialog box to temporarily change the settings for the current SCM session; see Preferences Menu [page 105]. The Scm resource file to create new defaults that are used each time SCM is started; see Scm Resource File [page 66]. Note: If the SpectroSERVER loses its connection to a landscape, the landscape name is removed from the list. Device Name (B) Is nested under its associated landscape and only appears in the Device Specific Configurations window. This lets you view all configurations of all devices of the same type in the selected landscape(s). Date Modified (C) Helps you track configuration changes. Load Status (D) Shows the most recent load status of the configuration. The load status can be one of the following: L = Fully Loaded P = Partially Loaded = Not Loaded Page 89

90 Configuration Information Section References See Figure 9 [page 152]. Description Source (A) This field contains one of the following: Name of the device from which the configuration was captured. Name of the user who manually created the configuration. Time Created (B) Indicates the last date and time the configuration was created. Created By (C) Indicates the login name of the person who created the configuration. Time Modified (D) Indicates the last date and time the configuration was modified. If the configuration was not modified, the Time Modified field says NOT MODIFIED. Modified By (E) Indicates the login name of the person who modified the configuration. If the configuration was not modified, the Modified By field says NOT MODIFIED. Time Loaded (F) Indicates the last date and time the configuration was loaded. If the configuration was not loaded, the Time Loaded field says NOT LOADED. Loaded By (G) Indicates the login name of the person who loaded the configuration. If the configuration was not loaded, the Loaded field says NOT LOADED. Text Box (H) A field for users to enter configuration-specific comments. You can edit or enter text only if you click the Notes... button to open the Description dialog box. Notes Button (I) Opens a Notes dialog box that lets you view and edit complete configuration-specific comments. Page 90

91 Search/Filter Option References See Figure 10 [page 153] Overview Use the search/filter option to locate a configuration, a template, an attribute, or a device displayed in the associated list box. Description Small Flashlight Icon (A) Click the small flashlight icon to activate a text search within the associated list box. The active search window is outlined in yellow. Case Sensitive Button (B) Helps refine a search. When the button appears indented, the character string entered in the Search text box is applied as it is capitalized. If the button appears raised, capitalization does not influence the search results. Search/Filter Button (C) (Available only for attribute lists.) Select Search to scan the associated list box for specific character strings; select Filter to scan the contents for files that are identified by common character patterns. Text Box (D) Enter one or more characters in the text box as a search criterion or filter pattern. Page 91

92 Device Specific Configurations Window Prerequisites Start SpectroGRAPH. Start SCM: see Starting SCM [page 87] Select View > Device Specific Configurations. References See Figure 11 [page 154]. Description The Configuration list box (A) of the Device Specific Configurations window shows a three-level hierarchy of landscapes that contains device models which, in turn, contain device-specific configurations. Configurations in the selected landscape(s) are indented under their associated devices. You cannot see shared configurations in this view. If the Device Specific window does not list configurations, the Configuration list box only shows devices under their associated landscapes. The window title bar (B) shows which mode the window is in (C). The diamond-shaped button indicates the selected menu item. Note: Unlike the Shared Configurations window, the Device Specific Configurations window does not have a separate device selection field or Choose... button beneath the Configuration list box, since configurations are already applied to all listed devices. Page 92

93 Shared Configurations Window Prerequisites Start SpectroGRAPH. Start SCM: see Starting SCM [page 87] Select View > Shared Configurations. References See Figure 12 [page 155]. Description The Configuration list box (A) of the Shared Configurations window shows a two-level hierarchy of landscapes that contains shared configurations. Configurations are indented under their associated landscapes. You cannot see device-specific configurations in this view. The window title bar (B) shows which mode the window is in (C). The diamond-shaped button indicates the selected menu item. Note: If Options > Auto Expand Landscapes is turned off, the list collapses and only displays landscape names. Double-click a landscape name to view the configurations in the landscape. Beneath the Configuration list box is a device selection area that consists of a text box (D) and a Choose... button (E). It identifies device components in the Shared Configurations view and lets you select one or more devices to which you can load and verify. The first device listed in the text box is the preselected device. Select the Choose... button to bring up a device-selection window from where you can load a shared configuration to one or more devices. Page 93

94 SCM: Templates Window Prerequisites Start SpectroGRAPH. Start SCM: see Starting SCM [page 87] Select Setup > Templates. or Right-click within the Configuration Manager: Main window; then select Templates. References See Figure 13 [page 156]. See Setup > Templates [page 139]. Description Toolbar Buttons (A) Provide graphic shortcuts for creating new templates and saving templates to the database, as alternatives to function selections on the pull down menus. Pull Down Menus (B) Give access to all SCM template-related functionality. See File Menu [page 109], Edit Menu [page 110], and View Menu [page 111]. Window Title Bar (C) Includes a description of the active window and identifies the selected device type. Search/Filter Option (D) Click the small flashlight icon to launch a search within the associated list box. The active search window is outlined in yellow; see Search/Filter Option [page 91]. Template Information Section (E) Contains historical information about the selected template. See Template Information Section [page 96]. Status Bar (F) This window element is inactive for this product release. Page 94

95 Navigational Overview Window (G) Helps orient you as you scroll through the Template list. The rectangular box outlines the templates currently displayed in the Template section. As you scroll up or down in the list, the rectangular box moves in the same direction. Template List Box (H) Refers to the template names created for devices of the same type as the selected device in SpectroGRAPH or in the SCM Components dialog box. Templates appear indented under their associated landscapes. If the Auto Expand Landscapes option is turned off, the list collapses only the landscape names are visible. In this case, double-click the landscape name to view the associated templates. Change the Auto Expand Landscapes option: Through the SCM Preferences dialog box to temporarily change the setting for the current session; see Preferences Menu [page 105]. Through the Scm resource file to create a new default that is used each time SCM is started; see Scm Resource File [page 66]. Template Detail Section (I) Lists information on devices, attributes, and flags used in the selected templates. See Template Detail Section [page 97]. Page 95

96 Template Information Section References See Figure 14 [page 157]. Description Time Created (A) Indicates the date and time the template was created. Created By (B) Indicates the login name of the person who created the template. Time Modified (C) Indicates the last date and time the template was modified. If the template has not been modified, the Time Modified field says NOT MODIFIED. Modified By (D) Indicates the login name of the person who modified the template. If the template has not been modified, the Modified By field says NOT MODIFIED. Text Box (E) Use this area to input comments you want to include in all captures that use the selected template. Notes Button (F) Opens a Notes dialog box that lets you view complete template-specific comments. Page 96

97 Template Detail Section References See Figure 15 [page 158]. Description Template Detail Button (A) Toggle this button to turn the template details on and off. When the button appears indented, the window shows attribute details of the selected template and insertable attribute list. When the button appears raised, both list boxes in the Template Detail section are blank. Note: Configuration listings display faster if the Template Detail button is turned off, since the system does not have to collect attribute information. To view only general configuration information (for example, if a configuration was modified), turn the Template Detail button off. Device List Box (B) Indicates all the subcomponents of the selected device. These can be applications, boards, interfaces, etc. Attribute List Box (C) Indicates the attributes and their flags that are in the selected template. If you are creating a new template, there are no attributes in the list. You must select attributes from the Insertable Attribute list and add them to the template. Flags List (D) Indicates whether an attribute is readable (R), writable (W), or both (RW). You can sort and filter the attributes based on their flags. Insertable Attribute List (E) Contains all readable and writable attributes for the selected device type. Select attributes for a new template from this list. Include Host Configuration Field (F) Shows whether the selected template can capture a host configuration file; then lets you create templates that capture a host configuration file. Note: If the selected template includes a host configuration file, view the file by selecting the Edit Host Configuration button. Transfer Arrows (G) Use these arrows to move attributes between the two list boxes in the Template Detail section. Page 97

98 Menus, Icons, and Buttons This section contains descriptive information about all interactive elements in the SCM interface. In This Section Pull Down Menus Main Window [page 99] Pull Down Menus Templates Window [page 108] File > Delete [page 112] File > Rename [page 113] File > Exit [page 114] Model > Navigate Components... [page 115] Model > Select Model... [page 116] Options > Capture... [page 117] Options > Load... [page 118] Options > Verify... [page 119] Options > Compare... [page 120] Options > Schedule... [page 123] Options > Edit Host Configuration... [page 125] Options > Edit Model Configuration... [page 128] Options > Edit Mask... [page 132] Options > Preferences [page 135] Options > Preferences > Settings [page 136] Options > Preferences > Attributes [page 137] Options > Preferences > Search [page 138] Setup > Templates [page 139] Help > About Configuration Manager [page 140] Help > About Configuration Manager [page 140] Help > Online Manuals [page 141] Page 98

99 Pull Down Menus Main Window Prerequisites Start SpectroGRAPH; see Getting Started with SPECTRUM for Administrators (0985). Start SCM: see Starting SCM [page 87] References See Figure 19 [page 162]. Description Configuration Manager: Main Window (A) Contains six pull down menus organized as follows: File Menu, View Menu, Model Menu, Options Menu, Setup Menu, and Help Menu. Note: SCM also provides toolbar buttons for some of the items in the Options menu. To identify a button, hover the cursor over the button and its name appears. Page 99

100 File Menu References See Figure 20 [page 163]. See Figure 28 [page 171] for the Exit message box. Description Delete (A) Deletes the selected (highlighted) configuration(s) in the main window. Rename... (B) Changes the name of a configuration. Exit (C) Displays a message box asking you if you want to exit from SCM. Select OK to close the Configuration Manager: Main window. Page 100

101 View Menu References See Figure 21 [page 164]. Description Shared Configurations (A) Displays shared configurations. The diamondshaped button indicates the selected menu item. Device Specific Configurations (B) Displays device-specific configurations. The diamond-shaped button indicates the selected menu item. Page 101

102 Model Menu References See Figure 22 [page 165]. See Model > Navigate Components... [page 115]. See Model > Select Model... [page 116]. Description Navigate Components... (A) Displays the SCM: Components dialog box that contains all components of the selected device in SpectroGRAPH. Note: Sub-components of the selected device could include ports and secondary applications. Select Model... (B) Displays the Configuration Manager: Select Model using... dialog box, which lets you select additional devices (aside from the selected device in SpectroGRAPH) to manage through SCM. Page 102

103 Options Menu References See Figure 23 [page 166]. See Security Features [page 48]. See Options > Capture... [page 117]. See Options > Load... [page 118] See Options > Verify... [page 119] See Options > Compare... [page 120] See Options > Schedule... [page 123] See Options > Edit Host Configuration... [page 125]. See Options > Edit Model Configuration... [page 128] See Options > Edit Mask... [page 132] See Preferences Menu [page 105] Description Capture... (A) Opens the SCM: Capture Configuration dialog box. Use this dialog box to capture a configuration from the selected device in SpectroGRAPH. Load... (B) Loads the selected configuration(s) to the selected device(s) or component(s). When you select Load..., SCM asks you to confirm the action. Verify... (C) Verifies the configuration of the selected device(s) or component(s). When you select Verify..., SCM asks you to confirm the action. Compare... (D) Compares two configurations. You can also view two configurations (if available) in another Comparison Detail window. Page 103

104 Schedule... (E) Opens the SCM: Scheduler dialog box. This dialog box lets you schedule the time and frequency of automatic configuration loads, verifications, or captures. Edit Host Configuration (F) Displays the host configuration file. If the letters on the menu item are not grayed out, the configuration includes the device s host configuration file. If the letters are grayed-out, the selected configuration does not include the host configuration file. The Edit Host Configuration menu item appears as View Host Configuration on the pull down menu if the user has low-level permissions. Edit Model Configuration... (G) Displays the SCM configuration model for the selected device. The Edit Model Configuration menu item appears as View Model Configuration on the pull down menu if the user has low-level permissions. Edit Mask (H) Displays a text field that allows the user to enter specific words, phrases, and elements that hide (or mask) parts of a configuration. This feature is used when comparing two configurations; it allows SCM to ignore certain lines in the configuration so only necessary information is displayed in the Host Config Diff and Attribute Diff windows. Preferences (I) Lets you temporarily define preferences for the current SCM session, such as landscapes for locating configurations, templates, and devices; save and load settings; attribute flag settings; and enabling an extended search. See Preferences Menu [page 105] To create new defaults that apply each time SCM is started, edit the Scm resource file; see Scm Resource File [page 66]. Page 104

105 Preferences Menu References See Figure 49 [page 192]. See Options > Preferences [page 135]. See Options > Preferences > Settings [page 136]. See Options > Preferences > Attributes [page 137]. See Options > Preferences > Search [page 138]. Description Preferences Dialog Box (A) Displays tabs for viewing and changing landscapes, settings, attributes, and search parameters. Page 105

106 Setup Menu References See Figure 24 [page 167]. See SCM: Templates Window [page 94] Description Templates (A) Opens the SCM: Templates window in which you can create, edit, delete, and save templates. Page 106

107 Help Menu References See Figure 25 [page 168]. See Help > About Configuration Manager [page 140]. See Help > Online Manuals [page 141]. Description Online Manuals (A) Enables direct access to SCM documentation as part of the SPECTRUM documentation set. About Configuration Manager (B) Displays a pop up screen with general company and product information. Page 107

108 Pull Down Menus Templates Window Prerequisites Start SpectroGRAPH; see Getting Started with SPECTRUM for Administrators (0985). Start SCM: see Starting SCM [page 87] Select Setup > Templates. References See Figure 56 [page 199]. Description SCM: Templates Window (A) Contains three pull down menus organized as follows: File Menu [page 109], Edit Menu [page 110], and View Menu [page 111]. Page 108

109 File Menu References See Figure 16 [page 159]. Description New (A) Creates a new template. When you click New, SCM adds the name <UNTITLED> to the template list. You can then select attributes for the untitled template. You can also click the New button on the tool bar to create a new template. Note: To identify a button, hover the cursor over the button and the name appears. Save (B) Saves a modified template with its same name and landscape location, but with an updated Date Modified. You can also click the Save button on the tool bar. The Save option in the File menu and the Save button on the tool bar are grayed out if you are creating a new template, because you must use the Save As option to name and save a new template. You can specify Save options to overwrite an existing template or create a new one. To temporarily change the Save functionality for the current session, use the SCM Preferences dialog box; see Preferences Menu [page 105]. To set the modified Save functionality as the new default each time SCM is started. edit the Scm resource file; see Scm Resource File [page 66]. Save As... (C) Names a new template, renames an existing template, or saves a template to a new landscape. When you use the Save As option, you can name an untitled template. Delete (D) Deletes the selected (highlighted) template(s) in the SCM: Templates window. Close (E) Closes the SCM: Templates window. Page 109

110 Edit Menu References See Figure 17 [page 160] Description Discard All Changes (A) Discards the in-process <UNTITLED> template and displays a list of existing templates. Page 110

111 View Menu References See Figure 18 [page 161]. See Figure 13 [page 156] to locate the list boxes in the SCM: Templates window. Overview The View menu is split into two sections divided by a light gray line. The top three menu selections determine the order of the information in Template list box; the bottom three menu selections determine the order of the information in the Template Details list box. The diamond-shaped button on the pull down menu indicates the selected menu item. Description View By Template Name (A) Rearranges the templates listed in the SCM: Templates window by template name (alphabetically). View By Create Time (B) Rearranges the templates listed in the SCM: Templates window by the time the templates were created. View By Modify Time (C) Rearranges the templates listed in the SCM: Templates window by the last time the templates were changed. View By Attributes (D) For the current session, temporarily rearranges the templates listed in the SCM: Templates window with a secondary alphabetical sort order being by attributes. View By Flags (E) For the current session, temporarily rearranges the templates listed in the SCM: Templates window with a secondary alphabetical sort order by flags. View By Sequence (F) For the current session, temporarily rearranges the templates listed in the SCM: Templates window with a secondary alphabetical sort order by sequence. Page 111

112 File > Delete References See Figure 26 [page 169]. Description Yes Button (A) Confirms the configuration delete operation, which removes the selected configuration from the database and display. No Button (B) Cancels the delete operation. Page 112

113 File > Rename References See Figure 27 [page 170]. Description Text Box (A) Use this text box to enter the new name for the currently selected configuration. Yes Button (B) Confirms the renaming operation, which overwrites and renames the currently selected configuration. No Button (C) Cancels the renaming operation. Page 113

114 File > Exit References See Figure 28 [page 171]. Description Yes Button (A) Confirms the close operation to exit SCM. No Button (B) Cancels the close operation. Page 114

115 Model > Navigate Components... References See Figure 29 [page 172]. Overview This view shows any applications, interfaces, and boards in a device, as well as the sub-components of the applications, interfaces, and boards. You can also create configurations and templates on the sub-components. Description Device Selection Box (A) Use this area to select the target device or subcomponent. OK Button (B) Confirms the device or subcomponent selection, navigates to the subcomponent level, and closes the window. Apply Button (C) Confirms the device or subcomponent selection, navigates to the subcomponent level, but leaves the window open. Cancel Button (D) Cancels any device or subcomponent selection and closes the window. Page 115

116 Model > Select Model... References See Figure 30 [page 173]. Description Landscape Selection Button (A) Lets you select from a list of available landscapes. Note: To list landscapes in a distributed SpectroSERVER environment, add the respective landscape handles in the Scm resource file. Landscape Name (B) Name of the landscape selected for a model search. Model Handle Selection and Text Box (C) Click the respective button on the left side of the dialog box, or click inside the respective text box to select this search criterion; then type a model handle in the text box. Note: Only one criterion can be applied per search. Search strings (i.e, model handles, model names, etc.) can be fragments and are not case sensitive. Model Name Selection and Text Box (D) Click the respective button on the left side of the dialog box, or click inside the respective text box to select this search criterion; then type a model name in the text box. Model Type Name Selection, Drop Down List, and Text Box (E) Click the respective button on the left side of the dialog box, click the drop down list button, or click inside the text box to select this search criterion. The selection from the drop down list automatically displays in the text box. You can also enter a model type name directly in the text box; you do not have to use the drop down list. IP Address (F) Click the respective button on the left side of the dialog box, or click inside the respective text box to select this search criterion; then type a IP address in the text box. OK Button (G) Starts the model search based on the entered information. Cancel Button (H) Cancels the model search operation. Clear All Button (I) Clears all entered information. Help Button (J) Displays a few tips about the model search function. Page 116

117 Options > Capture... References See Figure 31 [page 174]. Description Choose... Button (A) Displays the SCM: Select Device dialog box from which you can select a different device. Small Flashlight Icon (B) Launches a text search within the associated list box. The active search window is outlined in yellow; see Search/Filter Option [page 91]. Cancel Button (C) Cancels the configuration capture operation and closes the dialog box. Configuration name Text Box (D) Use this area to enter a name for the configuration. Search/Filter Option (E) Click this button to select between the search and filter operations. OK Button (F) Confirms and launches the configuration capture operation. Case Sensitive Button (G) Restricts the search to the exact case of the characters as entered in the Configuration name text box. Page 117

118 Options > Load... References See Figure 32 [page 175]. Description Commit Loaded configuration to NVRAM (A) When the button appears indented, the operation loads the selected configuration on the target device(s) as the running configuration, and also stores the configuration as the startup configuration for the target device(s). When the button appears raised, the configuration can be loaded to the device(s) only as a running configuration. Note: Some configurations do not allow SCM to automatically store them as startup configurations. If this is the case, the Commit Loaded configuration to NVRAM button does not appear on the load confirmation dialog box. Yes (B) Confirms and launches the configuration load operation. No (C) Cancels the configuration load operation and returns you to the main window. Page 118

119 Options > Verify... References See Figure 33 [page 176]. Description Yes Button (A) Confirms and launches the configuration verify operation. No Button (B) Cancels the configuration verify operation and returns you to the main window. Note: Verify will ignore additional lines when done with a shared configuration. It will continue to do a line by line comparison for device specific configurations. Page 119

120 Options > Compare... References See Figure 34 [page 177]. See Host Config Diff Window [page 121]. See Attribute Diff Window [page 122]. Description OK Button (A) Confirms the results of the configuration compare operation and returns you to the main window. Host Config Diff Button (B) Displays a window that highlights the differences between the two selected host configuration files. Attribute Diff Button (C) Displays a window that lists only the attributes that differ between two device models. Note: Compare does a line by line comparison whether or not the configuration is device specific or shared. Page 120

121 Host Config Diff Window Prerequisites Select Option > Compare...; then select Host Config Diff. References See Figure 35 [page 178]. Description Configuration Name (A) Identifies the column of information below with its associated configuration. Highlighted Differences (B) Are indicated in red with white text. Close Button (C) Closes the Host Config Differences window and returns you to the Compare Results dialog box. Page 121

122 Attribute Diff Window Prerequisites Select Option > Compare...; then select Attribute Diff. References See Figure 36 [page 179]. Description Model Name (A) Identifies the selected device model. Attribute Name (B) Identifies only the selected attribute(s) from the complete device attribute list. Configuration Name (C) If the two selected configurations share the same name, this column lists the most current of the two configurations. If the configurations have different names, this column lists the configuration that has first alphabetical position. The window shows only attributes shared by the two configurations. The column under each configuration contains unique values for the shared attribute(s). Configuration Name (D) Identifies the oldest of the two selected configurations. The last two columns contain unique values for each shared attribute in the selected configurations. Close Button (E) Closes the Attribute Differences window and returns you to the Compare Results dialog box. Page 122

123 Options > Schedule... References See Figure 37 [page 180]. Description The Scheduler lets you organize the time and frequency of automatic SCM loads, verifications, and captures. Add (A) Adds the highlighted entry in the Scheduled Entries field. To add an entry: specify the task, frequency, date, and time of the task in the appropriate fields. Then click Add. Note: Add inserts entries only in the Scheduled Entries field whereas Save schedules the entries. Modify (B) Modifies the highlighted entry in the Scheduled Entries field. To modify an entry: highlight the entry in the Scheduled Entries field, click the appropriate buttons in the Schedule and Frequency sections, and then click Modify, and finally Save to schedule the modified entry. Remove (C) Removes an entry in the Scheduled Entries field or in the scheduled queue itself. To delete an entry: highlight the entry, click the Remove button and then on Save to remove the entry from the scheduled queue. Save (D) Sends the new or modified entries in the Scheduled Entries field to the scheduled queue. Click the Save button after you use the Add, Modify, and Remove buttons. If you forget to use the Save button before you click Close, SCM prompts you to save the scheduled entry. Reset (E) Discards all changes, rereads the scheduled queue, and displays the entries in the Scheduled Entries field. Click the Reset button to see the entries that are in the scheduled queue. Close (F) Closes the Scheduler dialog box. If you have forgotten to use the Save button to send entries to the scheduled queue, the Scheduler asks you if you want to discard the changes. You can click either Yes or No. Current Date and Time (G) Display the current date and time on the system where you are running SpectroGRAPH. Page 123

124 Task (H) Enables you to specify the task that you want to schedule either Verify or Load if you accessed the Scheduler from the Configuration Manager: Main window or Capture if you accessed the Scheduler from the Configurations window. You must select the desired operation (even if it is visible when you open the window) so that the Scheduler enters the command in the Command field. When you select the Load, Verify, or Capture button, SCM prompts you to confirm your choice. Command (I) Displays the scheduled command. When you specify the task Capture, Verify, or Load the Scheduler enters the information in the Command field. Frequency (J) Enables you to specify the frequency of captures, loads, or verifications. Frequency options are: Once, Hourly, Daily, Weekly, Monthly. You can schedule the Once frequency any time between the current date and one year later. Tasks scheduled for an Hourly, Daily, Weekly, or Monthly frequency will be performed indefinitely or until you delete or change the entry. Note: The Scheduler does not include the Hourly frequency on Windows NT. Also, the Once frequency only lets you schedule SCM operations a maximum of one month from the current date. Other dates appear grayed-out. Scheduled Entries (K) Contains both the entries saved to the queue and entries that you have just added to the field. After you specify the frequency, date, and time of a task and press the Add button, SCM displays the entry in this field. Then when you click Save, SCM schedules the entry. If you want to see the whole entry, enlarge the dialog box. An entry in the Scheduled Entries field is made up of two parts: The scheduling information at the beginning of the line and the command, enclosed in quotes, in the rest of the line. The Command field, on the other hand, contains only the command. Note: Some buttons in the Scheduler dialog box are grayed-out when you open the dialog box and when you make selections. A grayed-out button indicates that the option is not available at that time. Page 124

125 Options > Edit Host Configuration... References See Figure 38 [page 181]. See File Menu [page 126]. See Edit Menu [page 127]. Description Edit/View Host Configuration Window (A) Use this window to make changes to host configuration files and overwrite the same files, or save them as new files. Pull Down Menus (B) Click the File and Edit pull down menu choices to edit, print, and save host configuration files. Page 125

126 File Menu References See Figure 39 [page 182]. Description Save & Close (A) Overwrites the existing file with the changes, then closes the Edit/View Host Configuration window. Print... (B) Prints the host configuration file changes to your specified printer. Save To File... (C) Saves the host configuration file changes under a new file name. Close (D) Closes the Edit/View Host Configuration window. Page 126

127 Edit Menu References See Figure 40 [page 183]. Description Cut (A) Removes selected character strings from the host configuration file and stores them temporarily in the paste buffer. Copy (B) Copies selected character strings from the host configuration file and stores them temporarily in the paste buffer. Paste (C) Pastes the character strings stored in the paste buffer into the host configuration file. Find (D) Searches the host configuration file for character strings entered in the Find dialog box. Find Again (E) Repeats the character string search initiated by the Find command. Page 127

128 Options > Edit Model Configuration... References See Figure 41 [page 184]. See File Menu [page 129]. See Edit Menu [page 130]. See View Menu [page 131]. Description Toolbar Button (A) Provides a graphic shortcut for the save function. Pull Down Menus (B) Click the File, Edit, and View pull down menu choices to edit, print, save, and view attribute changes to model configurations. Search/Filter Option (C) A tool that helps search the contents of the Configuration list box. See Search/Filter Option [page 91]. Model Attribute Editing Area (D) An interactive area for changing model attributes. Page 128

129 File Menu References See Figure 42 [page 185]. Description Save (A) Overwrites the existing file with the changes, then closes the Edit Model Configuration... window. Close (D) Closes the Edit Model Configuration... window. If changes were made and not saved, a close confirmation box appears. Page 129

130 Edit Menu References See Figure 43 [page 186]. Description Cut (A) Removes selected character strings from the model configuration and stores them temporarily in the paste buffer. Copy (B) Copies selected character strings from the model configuration and stores them temporarily in the paste buffer. Paste (C) Pastes the character strings stored in the paste buffer into the model configuration. Find (D) Searches the model configuration for character strings entered in the Find dialog box. Find Again (E) Repeats the character string search initiated by the Find command. Page 130

131 View Menu References See Figure 44 [page 187]. Description View By Attributes (D) For the current SCM session, temporarily rearranges the information listed in the Device Attributes window with a secondary alphabetical sort order by attributes. View By Flags (E) For the current SCM session, temporarily rearranges information listed in the Device Attributes window with a secondary alphabetical sort order by flags. View By Sequence (F) For the current SCM session, temporarily rearranges information listed in the Device Attributes window with a secondary alphabetical sort order by sequence. Note: The diamond-shaped button on the pull down menu indicates the selected menu item. Page 131

132 Options > Edit Mask... References See Figure 46 [page 189]. See Options Menu [page 103] for a description of the Edit Mask... feature. See File Menu [page 133]. See Edit Menu [page 134]. Description Pull Down Menus (A) Click the File and Edit pull down menu choices to edit, print, and save specific configuration masks. Text Field (B) Use this area to enter character strings that enable SCM to mask portions of the selected configuration. Page 132

133 File Menu References See Figure 47 [page 190]. Description Save & Close (A) Updates the saved configuration with a new mask; then closes the Edit Mask... window. Print... (B) Prints the configuration mask to your specified printer. Save To File... (C) Saves the edited configuration mask to a file. Close (D) Closes the Edit Mask... window. Page 133

134 Edit Menu References See Figure 48 [page 191]. Description Cut (A) Removes selected character strings from the mask editing text area and stores them temporarily in the paste buffer. Copy (B) Copies selected character strings from the mask editing text area and stores them temporarily in the paste buffer. Paste (C) Pastes the character strings stored in the paste buffer into the mask editing text area. Find (D) Searches the mask editing text area for character strings entered in the Find dialog box. Find Again (E) Repeats the character string search initiated by the Find command. Page 134

135 Options > Preferences References See Figure 49 [page 192]. See Options > Preferences > Settings [page 136]. See Options > Preferences > Attributes [page 137]. See Options > Preferences > Search [page 138]. Description Preferences Dialog Box Tabs (A) Allows users to temporarily set attributes, settings, and search parameters for the current SCM session. Page 135

136 Options > Preferences > Settings References See Figure 50 [page 193]. Description Settings Tab (A) Displays the option to temporarily set the selected configuration as a startup configuration for the current SCM session. Commit Loaded configuration to NVRAM Button (B) See Options > Load... [page 118]. OK Button (C) Confirms the option the save (or not save) the configuration as a startup configuration; then returns you to the main window. Apply Button (D) Confirms the option the save (or not save) the configuration as a startup configuration, but leaves the Preferences dialog box open. Reset Button (E) Resets the option the save (or not save) the configuration as a startup configuration to its default setting. Cancel Button (F) Cancels the preference operation and returns you to the main window. Page 136

137 Options > Preferences > Attributes References See Figure 51 [page 194]. Description Attributes Tab (A) Displays a series of options to temporarily set attributes for the current SCM session. List of Insertable Attributes Buttons (B) Give the user choices when configuration and templates attributes are captured. Flags for Insertable Attributes Buttons (C) Set the read, write, internal, and external attributes for the selected configuration. OK Button (D) Confirms all option selections; then returns you to the main window. Apply Button (E) Confirms all option selections, but leaves the Preferences dialog box open. Reset Button (F) Resets all options to their default settings. Cancel Button (G) Cancels the preference operation and returns you to the main window. Page 137

138 Options > Preferences > Search References See Figure 52 [page 195]. Description Search Tab (A) Displays the option to temporarily enable a recursive search in the current SCM session. Enable Extended Search Button (B) Scrolls to the area for the first match of either the device name or attribute name found in the list. OK Button (C) Confirms the Enable Extended Search option; then returns you to the main window. Apply Button (D) Confirms the Enable Extended Search option, but leaves the Preferences dialog box open. Reset Button (E) Resets the Enable Extended Search option to its default setting. Cancel Button (F) Cancels the preference operation and returns you to the main window. Page 138

139 Setup > Templates References See Figure 53 [page 196]. See SCM: Templates Window [page 94]. Description SCM: Templates Window (A) Enables the user to create templates for capturing configurations. Page 139

140 Help > About Configuration Manager References See Figure 54 [page 197]. Description SCM General Information Pop Up (A) Contains SCM version, Aprisma contact, and product copyright information. Page 140

141 Help > Online Manuals References See Figure 55 [page 198]. See the SPECTRUM Installation Guide (0675) for instructions on copying the SPECTRUM documentation set. Overview SCM documentation is provided on the SPECTRUM Documentation CD; however, you can also copy the contents of the CD to a local directory or network directory for convenient use. The first time you try to access Online Manuals from any Help menu within SPECTRUM, you are prompted for the location of the documentation set (CD drive, local drive, or network drive). You can either browse to the location or enter the directory path in the text box. Description Documentation Location Dialog Box (A) Appears the first time you try to access the documentation set through any Help menu in SPECTRUM. Once the documentation set is located, this screen does not appear again. Browse... Button (B) Displays accessible local and remote directories in your network in an interactive interface, which allows you to select the location of the SPECTRUM documentation set. Cancel Button (C) Cancels the documentation locating operation and returns you to the active window. OK Button (D) Confirms and launches the documentation locating operation; then closes the search dialog box. Text Box (E) Provides an area to enter the path to the SPECTRUM documentation set on your CD drive, local drive, or network drive. Page 141

142 Figures This section contains a sequential listing of all figures in this document. In This Section Figure 1: How Works: Capturing a Configuration File [page 144] Figure 2: How Works: Loading a Configuration File [page 145] Figure 3: How Works: Capturing SNMP Attributes [page 146] Figure 4: How Works: Loading SNMP Attributes [page 147] Figure 5: Security Token File [page 148] Figure 6: Configuration Manager: Main Window [page 149] Figure 8: Main Window Configuration List Box [page 151] Figure 9: Main Window Configuration Information Section [page 152] Figure 10: Main Window Search/Filter Option [page 153] Figure 11: Main Window Device Specific Configurations [page 154] Figure 12: Main Window Shared Configurations [page 155] Figure 13: SCM: Templates Window [page 156] Figure 14: SCM: Templates Window Template Information Section [page 157] Figure 15: Templates Window Template Detail Section [page 158] Figure 16: Templates Window File Menu [page 159] Figure 17: Templates Window Edit Menu [page 160] Figure 18: Templates Window View Menu [page 161] Figure 19: Main Window Pull Down Menus [page 162] Figure 20: File Menu [page 163] Figure 21: View Menu [page 164] Page 142

143 Figure 22: Model Menu [page 165] Figure 23: Options Menu [page 166] Figure 24: Setup Menu [page 167] Figure 25: Help Menu [page 168] Figure 26: File > Delete [page 169] Figure 27: File > Rename [page 170] Figure 28: File > Exit [page 171] Figure 29: Model > Navigate Components... [page 172] Figure 30: Model > Select Model... [page 173] Figure 31: Options > Capture... [page 174] Figure 32: Options > Load... [page 175] Figure 33: Options > Verify... [page 176] Figure 34: Options > Compare... [page 177] Figure 37: Options > Schedule... [page 180] Figure 38: Options > Edit Host Configuration... [page 181] Figure 41: Options > Edit Model Configuration... [page 184] Figure 46: Options > Edit Mask... [page 189] Figure 49: Options > Preferences [page 192] Figure 50: Options > Preferences > Settings [page 193] Figure 51: Options > Preferences > Attributes [page 194] Figure 52: Options > Preferences > Search [page 195] Figure 53: Setup > Templates... [page 196] Figure 54: Help > About Configuration Manager [page 197] Figure 55: Help > Online Manuals [page 198] Page 143

144 Figure 1: How Works: Capturing a Configuration File Administrator s PC or Workstation SPECTRUM SpectroSERVER (Database) > > > > > > > > TFTP Server Administrator PC or Workstation includes: - SCM - TFTP Server > 2 Physical Device (For Example, Router) 1 SCM makes a request through the SpectroSERVER for the physical device to send its configuration file to the TFTP server. 2 The physical device begins transferring its host configuration file to the TFTP server. 3 SCM polls the physical device (again through the SpectroSERVER) for the transfer status. 4 Once the configuration file transfer is complete, SCM gets the file from the TFTP server. Note: The TFTP server can be installed on a different machine, as long as it shares the same file system as the administrator s machine. 5 The configuration file is then saved in the SpectroSERVER database and the configuration information can be accessed by any SCM client. Page 144

145 Figure 2: How Works: Loading a Configuration File Administrator s PC or Workstation SPECTRUM SpectroSERVER (Database) > 2 4 > > > > > > > TFTP Server Administrator PC or Workstation includes: - SCM - TFTP Server 3 > Physical Device (For Example, Router) 1 SCM writes the configuration file to the TFTP server. 2 SCM makes a request through the SpectroSERVER for the physical device to get its configuration file from the TFTP server. 3 The physical device begins transferring the configuration file from the TFTP server. 4 SCM polls the physical device (again through the SpectroSERVER) for the transfer status. 5 Once the configuration file transfer is complete, SCM removes the file from the TFTP server. Note: The TFTP server can be installed on a different machine, as long as it shares the same file system as the administrator s machine. Page 145

146 Figure 3: How Works: Capturing SNMP Attributes Administrator s PC or Workstation SPECTRUM SpectroSERVER (Database) > 1 Administrator PC or Workstation includes: - SCM > 1 Physical Device (For Example, Router) 1 SCM makes a request through the SpectroSERVER for SNMP values from the physical device. Page 146

147 Figure 4: How Works: Loading SNMP Attributes Administrator s PC or Workstation SPECTRUM SpectroSERVER (Database) 1 > Administrator PC or Workstation includes: - SCM 1 > Physical Device (For Example, Router) 1 SCM makes a request through the SpectroSERVER for the physical device to set SNMP attribute values on the physical device. Page 147

148 Figure 5: Security Token File Page 148

149 Figure 6: Configuration Manager: Main Window A B C D E F G A Toolbar Buttons E Configuration List Box; see Figure 8 B Pull Down Menus F Configuration Information Section; see Figure 9 C Navigational Overview Window G Search/Filter Option; see Figure 10 D Window Title Bar Page 149

150 Figure 7: Configuration Load Scenarios Scenario 1 Running Startup Configuration Configuration > > Device > > SpectroSERVER Database Scenario 2 Scenario 3 Running Startup Running Startup Configuration Configuration Configuration Configuration > > Device > > Device > > Local Management > SpectroSERVER Database SpectroSERVER Database Scenario 1 Scenario 2 Scenario 3 Load configuration in db to device as running and startup configurations. Load configuration in db to device as running configuration only; startup configuration is loaded manually through local management. Load configuration in db to device as startup configuration only; device loads the startup configuration as the running configuration when the device is rebooted. Page 150

151 Figure 8: Main Window Configuration List Box C D A B A B C D Landscape Name Device Name Date Modified Load Status Page 151

152 A B C D E F G Figure 9: Main Window Configuration Information Section H I A B C D E F G H I Source Time Created Created By Time Modified Modified By Time Loaded Loaded By Text Box Notes Button Page 152

153 Figure 10: Main Window Search/Filter Option A B C D A B C D Small Flashlight Icon Case Sensitive Button Search/Filter Button Text Box Page 153

154 Figure 11: Main Window Device Specific Configurations C B A A B C Configuration List Box Window Title Bar View Pull Down Menu Page 154

155 Figure 12: Main Window Shared Configurations C B A D E A B C D E Configuration List Box Window Title Bar View Pull Down Menu Text Box Choose... Button Page 155

156 Figure 13: SCM: Templates Window A B C D D E F G H I J A Toolbar Buttons F Status Bar B Pull Down Menus G Navigational Overview Window C Window Title Bar H Template List Box D Search/Filter Option I Template Details List Box E Template Information Section; see Figure 14 [page 157] J Template Detail Section; see Figure 15 [page 158] Page 156

157 Figure 14: SCM: Templates Window Template Information Section A B C D E F A B C D E F Time Created Created By Time Modified Modified By Text Box Notes Button Page 157

158 Figure 15: Templates Window Template Detail Section A B C D E F G A B C D E F G Template Detail Button Device List Attribute List Flags List (scroll window to view) Insertable Attribute List Include Host Configuration Field Transfer Arrows Page 158

159 Figure 16: Templates Window File Menu A B C D E A B C D E New Save Save As Delete Close Page 159

160 Figure 17: Templates Window Edit Menu A A Discard All Changes Page 160

161 Figure 18: Templates Window View Menu A B C D E F A B C D E F View by Template Name View by Create Time View by Modify Time View by Attributes View by Flags View by Sequence Page 161

162 Figure 19: Main Window Pull Down Menus A A Pull Down Menu Items: - File; see Figure 20 [page 163] - View; see Figure 21 [page 164] - Model; see Figure 22 [page 165] - Options; see Figure 23 [page 166] - Setup; see Figure 24 [page 167] - Help; see Figure 25 [page 168] Page 162

163 Figure 20: File Menu A B C A Delete; see Figure 26 [page 169] B Rename...; see Figure 27 [page 170] C Exit; see Figure 28 [page 171] Page 163

164 Figure 21: View Menu A B A Shared Configurations; see Figure 12 [page 155] B Device Specific Configurations; see Figure 11 [page 154] Page 164

165 Figure 22: Model Menu A B A Navigate Components...; see Figure 29 [page 172] B Select Model...; see Figure 30 [page 173] Page 165

166 Figure 23: Options Menu A B C D E F G H I A Capture... F Edit Host Configuration...; see Figure 38 [page 181] B Load... G Edit Model Configuration...; see Figure 41 [page 184] C Verify... H Edit Mask...; see Figure 46 [page 189] D Compare... I Preferences; see Figure 49 [page 192] E Schedule... Page 166

167 Figure 24: Setup Menu A A Templates...; see Figure 53 [page 196] Page 167

168 Figure 25: Help Menu A B A About Configuration Manager; see Figure 54 [page 197] B Online Manuals; see Figure 55 [page 198] Page 168

169 Figure 26: File > Delete > > A B A B Yes Button No Button Page 169

170 Figure 27: File > Rename > A > B C A B C Text Box OK Button Cancel Button Page 170

171 Figure 28: File > Exit > > A B A B Yes Button No Button Page 171

172 Figure 29: Model > Navigate Components... > A > B C D A B C D Device Selection Box OK Button Apply Button Cancel Button Page 172

173 Figure 30: Model > Select Model... > > A B > C D E F G H I J A Landscape Selection Button F IP Address Selection and Text Box B Landscape Name G OK Button C Model Handle Selection and Text Box H Cancel Button D Model Name Selection and Text Box I Clear All Button E Model Type Name Selection, Drop Down List, and Text Box J Help Button Page 173

174 Figure 31: Options > Capture... > > A G B F E D C A Choose... Button E Search/Filter Option B Small Flashlight Icon F OK Button C Cancel Button G Case Sensitive Search/Filter Button D Configuration Name Text Box Page 174

175 Figure 32: Options > Load... > > A B C A B C Commit Loaded configuration to NVRAM Button Yes Button No Button Page 175

176 Figure 33: Options > Verify... > > A B A B Yes Button No Button Page 176

177 Figure 34: Options > Compare... > > A B C A OK Button B Host Config Diff Button; see Figure 35 [page 178] C Attribute Diff Button; see Figure 36 [page 179] Page 177

178 Figure 35: Host Config Diff Window A > B C A B C Configuration Name Highlighted Difference(s) Close Button Page 178

179 Figure 36: Attr Diff Window A B C D > E A Model Name D Configuration Name B Attribute Name E Close Button C Configuration Name Page 179

180 Figure 37: Options > Schedule... > > A B C A B C Save Button Reset Button Close Button Page 180

181 Figure 38: Options > Edit Host Configuration... > B A > A B Edit Host Configuration Window Pull Down Menus - See File Menu; Figure 39 [page 182] - See Edit Menu; Figure 40 [page 183] Page 181

182 Figure 39: Edit Host Configuration... File Menu A B C D > A B C D Save & Close Print... Save To File... Close Page 182

183 Figure 40: Edit Host Configuration... Edit Menu A B C D E > A B C D E Cut Copy Paste Find Find Again Page 183

184 Figure 41: Options > Edit Model Configuration... > A B C > D A Toolbar Button C Search/Filter Option B Pull Down Menus - File Menu; see Figure 42 [page 185] - Edit Menu; see Figure 43 [page 186] - View Menu; see Figure 44 [page 187] D Model Attribute Editing Area Page 184

185 Figure 42: Edit Model Configuration... File Menu A B > A B Save Close Page 185

186 Figure 43: Edit Model Configuration... Edit Menu A B C D E > A B C D E Cut Copy Paste Find Find Again Page 186

187 Figure 44: Edit Model Configuration... View Menu A B C > A B C View by Attributes View by Flags View by Sequence Page 187

188 Figure 45: Edit Model Configuration... Model Attribute Editing Area A B C D E > F } G J I H A Update Button F Text Box B Device Attribute List Box G Display Format Options C Transfer Arrows H Cancel Button D Host Configuration Attribute List Box I Apply Button E Value Button J OK Button Page 188

189 Figure 46: Options > Edit Mask... > A B > A B Pull Down Menus - File Menu; see Figure 47 [page 190] - Edit Menu; see Figure 48 [page 191] Text Field Page 189

190 Figure 47: Edit Mask... File Menu A B C D > A B C D Save & Close Print Save To File Close Page 190

191 Figure 48: Edit Mask... Edit Menu A B C D E > A B C D E Cut Copy Paste Find Find Again Page 191

192 Figure 49: Options > Preferences > A > A Preferences Dialog Box Tabs Page 192

193 Figure 50: Options > Preferences > Settings > A > B C D E F A Settings Tab D Apply Button B Commit Loaded configuration to NVRAM Button; see Options > Load... [page 118] E Reset Button C OK Button F Cancel Button Page 193

194 Figure 51: Options > Preferences > Attributes > A > B { C { D E F G A Attributes Tab E Apply Button B List of Insertable Attributes F Reset Button C Flags for Insertable Attributes G Cancel Button D OK Button Page 194

195 Figure 52: Options > Preferences > Search > A > B C D E F A Search Tab D Apply Button B Enable Extended Search Button E Reset Button C OK Button F Cancel Button Page 195

196 Figure 53: Setup > Templates... > A > A SCM: Templates Window; see Figure 13 [page 156] Page 196

197 Figure 54: Help > About Configuration Manager > > A A OK Button Page 197

198 Figure 55: Help > Online Manuals > A > E B D C A B C D E Documentation Location Dialog Box Browse... Button Cancel Button OK Button Text Box Page 198