spectrum configuration manager - ca...

SPECTRUM Configuration Manager

User GuideDocument 5099

NoticeCopyright 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 252.227-7013(c)(1)(ii) and FAR 52.227-19.

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:

http://www.aprisma.com/support/secure/manuals/trademark-list.htm

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 e-mail to [email protected]; 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 52.227-14 (June 1987) Alternate III(g)(3) (June 1987), FAR 52.227-19 (June 1987), or DFARS 52.227-7013(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 03801 USA

Phone: 603.334.2100U.S. toll-free: 877.468.1448Web site: http://www.aprisma.com

http://www.aprisma.com/support/secure/manuals/trademark-list.htm

http://www.aprisma.com

3

Contents

Preface 7

Chapter 1: About SPECTRUM Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About installing SPECTRUM Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

What is configuration management? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

What are configurations? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

What is SPECTRUM Configuration Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

How does SPECTRUM Configuration Manager work? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Uses for SPECTRUM Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 2: About Device Templates and Host Configuration Files . . . . . . . . . . . . . . . . 17

What is a device template? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

The Templates window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Host configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Setting up your workstation as a TFTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

For Solaris machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

For Windows NT/2000 machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Devices with host configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Selecting devices and host configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Interface models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Device-Specific configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Shared configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Host configuration file masking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Masking host configuration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Chapter 3: Loading Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Configuration loading details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Loading configurations from the ConfigurationManager: Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Logging and finding load results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

What if a load fails? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Special load information for devices with hostconfiguration files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 4: Verifying Host Configuration File Captures . . . . . . . . . . . . . . . . . . . . . . . . . 31

Verifying the configuration capture status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

What if a verification fails? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Verification options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Chapter 5: About Security in SPECTRUM Configuration Manager . . . . . . . . . . . . . . . . . 33

4 SPECTRUM Configuration Manager User Guide

Contents

Security features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Hiding passwords, keywords, or tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Viewing and editing host configuration passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 6: About the Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Why schedule operations in SCM? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

About the Windows® NT/2000 Task Scheduler service . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Working with the scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Accessing the scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Viewing the results of scheduled operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 7: About the SPECTRUM Event Log and the SCM Log File . . . . . . . . . . . . . . . . 41

About the SPECTRUM event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

How to use the SPECTRUM event log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Interpreting SCM event codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

About the SCM log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Chapter 8: About the Scm Resource File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Scm resource file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Keyboard shortcuts for menu items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 9: SCM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Understanding and modifying SCM alarms in SPECTRUM . . . . . . . . . . . . . . . . . . . . . . . . 51

SCM events that trigger alarms in SPECTRUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

How SPECTRUM notifies you of an SCM alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

How to modify, turn off, or clear SCM alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 10: Running SCM from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Using SCM commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Invoking SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Capturing a configuration from a model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Loading a configuration to one or more models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Verifying a configuration to one or more models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Importing configurations and templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Exporting configurations and templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 11: Device-Specific SCM Implementations . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Using SCM with supported juniper devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Secure Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Performing a juniper host capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 12: The User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Starting SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Contents

SPECTRUM Configuration Manager User Guide 5

Configuration Manager: Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Configuration List box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Configuration Information section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Search/Filter option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Device Specific Configurations window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Shared Configurations window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

SCM: Templates window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Template Information section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Template Detail section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Chapter 13: Menus, Icons, and Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Pull Down Menus—Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Model menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Options menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Preferences menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Setup menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Pull Down Menus—Templates window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

File > Delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

File > Rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

File > Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Model > Navigate Components... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Model > Select Model... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Options > Capture... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Options > Load... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Options > Verify... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Options > Compare... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Host Config Diff window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Attribute Diff window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Options > Schedule... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Options > Edit Host Configuration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Options > Edit Model Configuration... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87


Contents

Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

View menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Options > Edit Mask... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Edit menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Options > Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Options > Preferences > Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Options > Preferences > Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Options > Preferences > Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Setup > Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Help > About Configuration Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Help > Online Manuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Chapter 14: Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Appendix A 147SPECTRUM database storage constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Index 149

7

Preface

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 SPECTRUM Configuration Manager who are learning about the application in their work environment or a training class setting.

What is in this book

This guide contains the following chapters:

• Chapter 1: About SPECTRUM Configuration Manager - This chapter discusses configuration management in general terms, and how the SPECTRUM solution addresses specific needs and concerns of network administrators.

• Chapter 2: About Device Templates and Host Configuration Files - This chapter contains detailed information about device templates in SCM and the specific devices that allow host configuration file access.

• Chapter 3: Loading Configurations - This chapter contains information on loading configurations to one or more target devices, and some potential solutions for load failures.

• Chapter 4: Verifying Host Configuration File Captures - This chapter contains information about confirming the successful or unsuccessful capture statuses of host configuration files.

• Chapter 5: About Security in SPECTRUM Configuration Manager - This chapter contains information on setting security features in SCM that either allow or restrict access to devices and files.

• Chapter 6: About the Scheduler - This chapter covers information about using the Scheduler feature in SCM to automate functions, and customize the Scheduler for your business environment.

• Chapter 7: About the SPECTRUM Event Log and the SCM Log File - This chapter contains information about the means to view SCM operation status.

• Chapter 8: About the Scm Resource File - This chapter describes the parameter values in the SPECTRUM Configuration Manager resource file Scm.

• Chapter 9: SCM Alarms - This chapter describes how to modify, turn off, or clear SCM alarms in SPECTRUM.


Preface

• Chapter 10: Running SCM from the Command Line - This chapter describes how to perform SCM operations from the command line. The chapter displays the commands in a modified man page format.

• Chapter 11: Device-Specific SCM Implementations - This chapter describes device-specific integrations for using SCM with additional supported devices.

• Chapter 12: The User Interface - This chapter describes the Configuration Manager: Main window and its subordinate views.

• Chapter 13: Menus, Icons, and Buttons - This chapter contains descriptive information about all interactive elements in the SCM interface.

• Chapter 14: Figures - This chapter contains a sequential listing of all figures in this document.

• Appendix A: This chapter contains information about database constraints when working with SCM configurations.

Text conventions

The following text conventions are used in this document:

Document feedback

Please send feedback regarding SPECTRUM documents to the following e-mail address:

[email protected]

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 www.aprisma.com/support/secure/global_atac.shtml, or by calling (603) 334-2100.

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 Underlined and hypertext-blue

See “Document feedback” on page 8.

References to SPECTRUM documents (title and number)

Italic SPECTRUM Installation Guide (9030675)

Functionality enabled by SPECTRUM Alarm Notification Manager (SANM)

SANM in brackets []. [SANM] AGE_FIELD_ID

http://www.aprisma.com/support/secure/global_atac.shtml


Online documents

SPECTRUM documents are available online at:

http://www.aprisma.com/manuals

Check this site for the latest updates and additions.

http://www.aprisma.com/manuals


Preface

11

Chapter 1: About SPECTRUM Configuration Manager

This chapter discusses configuration management in general terms, and how the SPECTRUM solution addresses specific needs and concerns of network administrators.

In this chapter

• “About installing SPECTRUM Configuration Manager” on page 11

• “What is configuration management?” on page 12

• “What are configurations?” on page 12

• “What is SPECTRUM Configuration Manager?” on page 13

• “How does SPECTRUM Configuration Manager work?” on page 15

• “Uses for SPECTRUM Configuration Manager” on page 16

About installing SPECTRUM Configuration ManagerReferences

For information about installing SPECTRUM Configuration Manager™, see the SPECTRUM Installation Guide (0675), or consult the ATAC; see “Aprisma Technical Assistance Center (ATAC) contact information” on page 8.

Overview

SPECTRUM Configuration Manager (SCM) 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.

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.

What are configurations?References

See “Host configuration files” on page 19.

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:

• 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).

Overview

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

What is SPECTRUM Configuration Manager?


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.

Configurations include values like IP address, interface configuration, enabled protocols, SNMP community names, and passwords. The values can be Management Information Base (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.

What is SPECTRUM Configuration Manager?References

See “About the SPECTRUM event log” on page 41.

Overview

SPECTRUM Configuration Manager (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.

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.

The “last known good” configuration must be identified and managed hands-on by the network administrator. SCM does not automatically identify and store the “last known good” configuration for each device type.

2 Bringing a replacement device quickly online by loading the “last known good” stored configuration on it.

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.

3 Making on-demand, manual changes to a device configuration.

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.

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.

“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.

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.

How does SPECTRUM Configuration Manager work?


How does SPECTRUM Configuration Manager work?References

• See Figure 14-1 on page 95 for the configuration capture data flow.

• See Figure 14-2 on page 96 for the configuration load data flow.

• See Figure 14-3 on page 97 for the SNMP attribute capture data flow.

• See Figure 14-4 on page 98 for the SNMP attribute load data flow.

• See “What are configurations?” on page 12.

• See “Device Specific Configurations window” on page 69.

• See “Shared Configurations window” on page 69.

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:

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.

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.

Item Benefit Comments



Device specific Used only on the device from which it was captured.

Shared Can be used by all models of the same model type.

Uses for SPECTRUM Configuration ManagerOverview

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.

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.

17

Chapter 2: About Device Templates and Host Configuration Files

This chapter contains detailed information about device templates in SCM and the specific devices that allow host configuration file access.

In this chapter

• “What is a device template?” on page 17

• “The Templates window” on page 18

• “Host configuration files” on page 19

• “Devices with host configuration files” on page 21

• “Selecting devices and host configuration files” on page 21

• “Host configuration file masking” on page 22

What is a device template?References

• See “What are configurations?” on page 12

• See “Host configuration files” on page 19.

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.

18

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” on page 37.

• 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.

The Templates windowReferences

• See “Setup > Templates” on page 91.

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.

Host configuration files


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.

Host configuration filesReferences

• See “Devices with host configuration files” on page 21.

• See “Setting up your workstation as a TFTP server” on page 19 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” on page 19).

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.

Setting up your workstation as a TFTP serverIf 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 /tftpbootchmod 777 /tftpboot

3. Make sure there is a tftp entry in the /etc/services file. To search for the entry, type:cd /etcgrep 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

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.

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

Figure 2-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.

Devices with host configuration files


Devices with host configuration filesReferences

• See “Loading Configurations” on page 25.

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.

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

To resolve this:

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.

Selecting devices and host configuration filesOverview

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 one-to-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.

Host configuration file maskingOverview

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-2 on page 23).

Host configuration file masking


2. Click the Mask button to activate the Add Mask window (see Figure 2-2 on page 23). If the current configuration contains Mask strings, the window displays those strings; otherwise the window will be empty.

Figure 2-2: The Add Mask Window

3. 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 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.

3

5

4



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.]

25

Chapter 3: Loading Configurations

This chapter contains information on loading configurations to one or more target devices, and some potential solutions for load failures.

• In this chapter

• “Configuration loading details” on page 25

• “Loading configurations from the Configuration Manager: Main window” on page 27

• “Logging and finding load results” on page 28

• “What if a load fails?” on page 28

• “Special load information for devices with host configuration files” on page 30

Configuration loading detailsReferences

• See “Loading configurations from the Configuration Manager: Main window” on page 27.

• See “SCM Alarms” on page 51 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.

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 3-1: Load Status Messages

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” on page 41.

Modifying Load Failure Alarms You can modify or turn off the Load Failure alarms that appear in SPECTRUM.

Message Description

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?” on page 28.

Partially Loaded Some attributes in the configuration did not load.

Loading configurations from the Configuration Manager: Main window


Loading configurations from the ConfigurationManager: Main window

• References


• See “Configuration loading details” on page 25.

• See “Options > Load...” on page 82.

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 14-6 on page 100.

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.

Table 3-2: Load Status Codes

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 14-7 on page 101.

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

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?” on page 28.

P Partially Loaded Some attributes in the configuration did not load.



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...” on page 82. 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” on page 76.

• As a permanent SCM change by editing the Scm resource file; see “Scm resource file” on page 45.

Logging and finding load resultsReferences

• See “About the SPECTRUM Event Log and the SCM Log File” on page 41.

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.

What if a load fails?References

• See “SCM Alarms” on page 51 to change the alarm color or turn the alarm function off.

• See “Interpreting SCM event codes” on page 42 and “SCM Event Codes” on page 43.

Overview

Any load operation that fails to load an attribute is a load failure.

What if a load fails?


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.

Note: SCM alarm defaults are set at installation. After installation, you can change the alarm color or turn the alarm function off.

Details

Table 3-3 on page 29 contains information about resolving load failure issues.

Table 3-3: Troubleshooting for Configuration Load Failures

Issue Solution

A configuration fails to load to one or more devices.

- 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” on page 19.

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.



Special load information for devices with hostconfiguration files

References


• See “Devices with host configuration files” on page 21

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.

31

Chapter 4: Verifying Host Configuration File Captures

This chapter contains information about confirming the successful or unsuccessful capture statuses of host configuration files.

• In this chapter

• “Verifying the configuration capture status” on page 31

• “What if a verification fails?” on page 32

• “Verification options” on page 32

Verifying the configuration capture statusReferences


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.

32

What if a verification fails?References

• See “SCM Alarms” on page 51 to verify the alarm color or turn the alarm function off.

• See “Interpreting SCM event codes” on page 42.

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.

Verification optionsReferences


• See “Devices with host configuration files” on page 21.

• See “SCM Alarms” on page 51 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.

33

Chapter 5: About Security in SPECTRUM Configuration Manager

This chapter contains information on setting security features in SCM that either allow or restrict access to devices and files.

In this chapter

• “Security features” on page 33

• “Hiding passwords, keywords, or tokens” on page 35

• “Viewing and editing host configuration passwords” on page 35

Security featuresReferences

• See Table 5-1 on page 34 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.

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.

34

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.

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 5-1 on page 34 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.

Table 5-1: SCM Community Strings and Associated Access

Community String Associated Access

SCM,0

SCM,1

View, verify, and load configurations; create/edit templates and configurations.

The user can access all operations in all SCM windows.

SCM,2 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.

SCM,3

SCM,4

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.

SCM,5

SCM,6

SCM,7

SCM,8

SCM,9

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.

Hiding passwords, keywords, or tokens


Hiding passwords, keywords, or tokensReferences

• See Figure 14-5 on page 99.

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-passwordsnmp-set communityenable-passwordsnmp-server communitypassword

You can hide passwords, keywords, or tokens in host configuration files for certain devices.

Viewing and editing host configuration passwordsReferences


• See “Security features” on page 33.

Overview

You can view and edit host configuration passwords if you access (see “Options > Edit Host Configuration...” on page 130) 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.


Chapter 5: About Security in SPECTRUM Configuration Manager

37

Chapter 6: About the Scheduler

This chapter covers information about using the Scheduler feature in SCM to automate functions, and customize the Scheduler for your business environment.

In this chapter

• “Why schedule operations in SCM?” on page 37

• “About the Windows® NT/2000 Task Scheduler service” on page 38

• “Working with the scheduler” on page 38

• “Viewing the results of scheduled operations” on page 38

Why schedule operations in SCM?References

• See “About the Windows® NT/2000 Task Scheduler service” on page 38.

• See “Interpreting SCM event codes” on page 42 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.



About the Windows® NT/2000 Task Scheduler serviceReferences

• 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.

Working with the schedulerReferences

• See “Options > Schedule...” on page 84 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.

Viewing the results of scheduled operationsReferences

• See “About the SPECTRUM event log” on page 41.

• See “About the SCM log file” on page 43.

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.

Viewing the results of scheduled operations


• 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.

41

Chapter 7: About the SPECTRUM Event Log and the SCM Log File

This chapter contains information about the means to view SCM operation status.

In this chapter

• “About the SPECTRUM event log” on page 41

• “How to use the SPECTRUM event log” on page 42

• “Interpreting SCM event codes” on page 42

• “About the SCM log file” on page 43

About the SPECTRUM event logReferences

• See the Event Log User Guide (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.

42

• 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.

How to use the SPECTRUM event logReferences


• See “Interpreting SCM event codes” on page 42.

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 00820007 (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.

Interpreting SCM event codesReferences


• See “How to use the SPECTRUM event log” on page 42.

• See Table 7-1 on page 43 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.

About the SCM log file


Table 7-1: SCM Event Codes

About the SCM log fileReferences

• See “Scm resource file” on page 45 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.

Event Code Type of SCM Event

00820000 Configuration created

00820001 Configuration creation failed

00820002 Configuration loaded to a device

00820003 Configuration load failed

00820004 Configuration captured from a device

00820005 Configuration capture failed

00820006 Configuration verified

00820007 Configuration verification failed

00820008 Configuration modified

00820009 Configuration modification failed

0082000a Configuration deleted

0082000b Configuration deletion failed

0082000c Template created

0082000d Template creation failed

0082000e Template modified

0082000f Template modification failed

00820010 Template deleted

00820011 Template deletion failed

00820012 Capture partial success

00820013 Load partial success


Chapter 7: About the SPECTRUM Event Log and the SCM Log File

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.

45

Chapter 8: About the Scm Resource File

This chapter describes the parameter values in the SPECTRUM Configuration Manager resource file Scm.

In this chapter

• “Scm resource file” on page 45

• “Keyboard shortcuts for menu items” on page 49

Scm resource fileReferences

• See Table 8-1: Scm Resource File—Timeout and Pathname Parameters page 46.

• See Table 8-2: Scm Resource File—Operational Parameters page 46.

• See Table 8-3: Scm Resource File—Display Parameters page 48.

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.

46

Table 8-1: Scm Resource File—Timeout and Pathname Parameters

Table 8-2: Scm Resource File—Operational Parameters

Timeout or Pathname Parameter

Description and Default Value

DcmTimeoutvalue Server timeout in milliseconds waiting for device to reply.

Default: 6000 milliseconds (6 seconds)

DefaultTimeout Mail service timeout in milliseconds.

Default: 100000 milliseconds (100 seconds)

VnmConnectionTimeout Handshake timeout for the creation of sockets used by the mail service and its servers.

Default: 20 seconds

ScmPath Path for locating SCM utilities and associated data file.

Default: <$SPECROOT>/SG-Tools/scm

ScmLogFile Name of the background task log file.

Default: <$SPECROOT>/SG-Tools/scm/log/scmbg.log

TftpfilePath The default tftp server setting path.

Windows NT: <$SPECROOT>/SG-Tools/scm/tftpboot

Solaris: /tftpboot

Operational Parameter Description and Default Value

Committonvram Specifies whether to commit the device’s configuration non-volatile RAM after download.

Default: ON

ScmShowSharedConfigs Specifies whether shared or device-specific configurations display first at startup.

Valid values: YES—show shared configurations; NO—show device specific configurations.

Default: YES

ScmSearchOption Specifies how the ‘Search’ operation functions.

Valid values: YES—use the extended search function; NO—use the regular search function.

Default: NO

AttributeFlags 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

Scm resource file


AlwaysRetrieveAttributes 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

CaseSensitive Specifies the default case-sensitivity for Search and Filter.

Valid values: 0 = case insensitive; 1 = case sensitive.

Default: 1

SearchDefault Specifies whether Search or Filter is the default operation at startup.

Valid values: 0 = filter default; 1 = search default.

Default: 1

modelNameDisplayLength Specifies the maximum number of characters in a model name to display.

Valid values: 1 <= length <= 1024

Default: 1024

LongModelNamePopup 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

Operational Parameter Description and Default Value



Table 8-3: Scm Resource File—Display Parameters

Display Parameter Description and Default Value

BackgroundColor Colored border in all windows.

Default: 208 (baby blue — SCM blue)

FrameBackgroundColor Window background color in all windows.

Default: 251 (medium gray)

MenuColor Menu background color in all windows.

Default: 251 (medium gray)

LabelColor Foreground color for text in all windows.

Default: 45 (black)

SearchHighlightColor Color used to indicate whether search or filter is active.

Default: 170 (yellow).

OverviewSelectionColor Color used to indicate selected entries in the Navigational Overview window.

Default: 170 (yellow).

FontAliasFile Specifies the file to search when a given font cannot be found.

Default: <$SPECROOT>/spectrum.fonts

WindowTextColor Foreground color for text in all windows.

Default: 245 (black)

MenuTextColor Foreground color for text in all windows.

245 (black)

DarkBackgroundColor Highlight color and scroll bar trough color in all windows.

Default: 249 (dark gray)

SelectionColor Color for toggle buttons when selected.

Default: 249 (dark gray)

LabelFont Font used in labels and push buttons.

Default:-*-helvetica-medium-r-normal--*-120-75-75-p-*-iso8859-1

ListFont Font used in lists.

Default: -*-courier-medium-r-normal--*-120-75-75-m-*-iso8859-1

MenuFont Font used in menus.

Default: -*-helvetica-medium-r-normal--*-140-75-75-p-*-iso8859-1

TextFont Font used in text entry fields.

Default: -*-helvetica-medium-r-normal--*-140-75-75-p-*-iso8859-1

Keyboard shortcuts for menu items


Keyboard shortcuts for menu itemsReferences

• See “Scm resource file” on page 45.

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 8-4: Keyboard Shortcuts for Menu Items

dragInitiatorProtocolStyle Drag and drop parameter, disabled because it causes problems.

Default: XmDRAG_NONE

dragReceiverProtocolStyle Drag and drop parameter, disabled because it causes problems.

Default: XmDRAG_NONE

SCM Parameter Description and Default Value

cut_button.accelerator Ctrl<Key>x

cut_button.acceleratorText Ctrl+X

copy_button.accelerator Ctrl<Key>c

copy_button.acceleratorText Ctrl+C

paste_button.accelerator Ctrl<Key>v

paste_button.acceleratorText Ctrl+V

Display Parameter Description and Default Value

51

Chapter 9: SCM Alarms

This chapter describes how to modify, turn off, or clear SCM alarms in SPECTRUM.

Reference

• See “About the SPECTRUM Event Log and the SCM Log File” on page 41 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 00820003).

• Verify Failure (Event Code 00820007).

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.


Chapter 9: SCM Alarms

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:0x00820003 E 50 A 1, 0x8200030x00820007 E 50 A 2, 0x820007

• To turn off one or both alarms, delete the appropriate line(s) from the file: 0x820003 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.

53

Chapter 10: Running SCM from the Command Line

This chapter describes how to perform SCM operations from the command line. The chapter displays the commands in a modified man page format.

In this chapter

• “Using SCM commands” on page 53Requirements for using SCM commands

• “Invoking SCM” on page 54How to start SCM

• “Capturing a configuration from a model” on page 55How to capture a configuration

• “Loading a configuration to one or more models” on page 56How to load a configuration

• “Verifying a configuration to one or more models” on page 57How to verify a configuration

• “Importing configurations and templates” on page 58How to import templates and configurations

• “Exporting configurations and templates” on page 59How to export templates and configurations

Using SCM commandsSCM 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.

54

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: 100000*ScmPath: /usr/data/Spectrum/SG-Tools/scm*ScmLogFile: /usr/data/Spectrum/SG-Tools/scm/log/scmbg.log*ModelHandles: 0x6801eb, 0x6801ae, 0x680029*DeviceHandles: (used only with the -ds argument)

Invoking SCMScm — 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

Capturing a configuration from a model


SpectroSERVER to which you are connecting

-vnmsocket

Socket number on the SpectroSERVER

Capturing a configuration from a modelscmbg -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)-ol (overwrite lastest configuration that has the samename as the new configuration) <ON/OFF>-cname <SCM output configuration name>[-dhc (dump host config)] \[-path <host config output path>]

Input

-vnm


-file

Data file containing the following parameters and their values:Vnmsocket, DefaultTimeout, ScmPath,ScmLogFile, DeviceHandles (device modelhandles), and ModelHandles (template modelhandle(s))

-ds

Capture in device specific mode

-ol

Overwrite the latest configuration that has the same configuration name as the new configuration. This can be set to ON or OFF.

-cname

Name of the captured configuration

-dhc



Dump host configuration to a file (See page 56)

-path

Host configuration output path

Note: For capture and verify, you can specify a “-path” that includes a format string. The allowed fields in the format string are: @C = Config Name, @D = Device Name, and @L = Landscape/Server Name, as well as format specifiers allowed by strftime. Note that the file name will always be "@[email protected]". 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 modelsscmbg -f load — load a configuration to model(s)

Location


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


-file

Data file containing the following parameters andtheir values:Vnmsocket, DefaultTimeout, ScmPath,ScmLogFile, ModelHandles (device modelhandle(s)) or ConfigHandles (configuration modelhandle(s)), used only with the -ds argument

-ds

Load device specific configuration

-nv

Verifying a configuration to one or more models


Commit the loaded configuration to the selecteddevice’s non-volatile RAM (NVRAM), ON or OFF

Verifying a configuration to one or more modelsNote: 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


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


-file

Data file containing the following parameters and their values: Vnmsocket, DefaultTimeout, ScmPath,ScmLogFile, ModelHandles (device modelhandle(s)) or ConfigHandles (configuration modelhandle(s)), used only with the -ds argument

-ds

Verify device specific configuration

-dhc

Dump host configuration to a file (See page 56)

-path

Host configuration output path (See page 56)



Importing configurations and templatesimport — 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” on page 59) 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


Syntaximport \

-vnm <SpectroSERVER host name> \-port <VNM socket number> \-clh <create landscape handle> \-file <data-file name> \-scmpath <SCM directory path> \-time <VNM timeout>

Input

-vnm


-port

VNM socket number

-file

The file created by export

Options

-scmpath

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


Exporting configurations and templatesexport — retrieve templates/configurations, print output to the screen

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” on page 58).

Location


Syntax

For specifying one SCM configuration model handle:export \

-vnm <SpectroSERVER host name> \-port <VNM socket number> \-ch <SCM configuration model handle> \-scmpath <SCM directory path> \-time <VNM timeout>

For specifying one SCM template model handle:export \

-vnm <SpectroSERVER host name> \-port <VNM socket number> \-th <SCM template model handle> \-scmpath <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> \-scmpath <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> \-scmpath <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> \



-scmpath <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> \-scmpath <SCM directory path> \-time <VNM timeout>

For specifying all SCM configuration models:export \

-vnm <SpectroSERVER host name> \-elh <export landscape handle> \-port <VNM socket number> \-ac \-scmpath <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 \-scmpath <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 \-scmpath <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

Exporting configurations and templates


-elh

Landscape handle of destination SpectroSERVER for export

-mth

Model type handle

-mtn

Model type name

-port

VNM socket number

-th

SCM template model handle

-tn

SCM template name

-vnm


Options

-scmpath

SCM directory path

-time

VNM timeout value (The minimum and default value is 5,000).

63

Chapter 11: Device-Specific SCM Implementations

This chapter describes device-specific integrations for using SCM with additional supported devices.

In this chapter

• “Using SCM with supported juniper devices” on page 63

Using SCM with supported juniper devicesUsing SCM, you can perform host configuration operations (capture/load) for the following Juniper devices:

• M20

• M7i

• M5

These Juniper devices must be modeled using one of the following model types:

• JnprRedundRtr

• Jnpr_MXXX

SCM operates differently with supported Juniper devices when performing host configuration tasks. Traditionally, SCM performs an SNMP set to a device to initiate the TFTP transfer of configuration files to and from that device. With supported Juniper devices, SCM uses the JUNOScript server embedded within the JunOS software running on the devices. Communication is established from SCM to the JUNOScript server using SSH, and a session is opened. Next, SCM sends "get-configuration" or "load-configuration" commands via an XML stream to the JUNOScript server. In the case of "get-configuration," the contents of the Host Config file are sent to SCM via an XML stream. Correspondingly, in the case of "load-configuration," the contents of the Host Config file are sent to the JUNOScript server via an XML stream. The JUNOScript server and client application exchange initialization tags in order to determine if they are using compatible versions of the JUNOS software and the JUNOScript API. The client application sends one or more requests to the JUNOScript server and parses its responses.

64

Secure Configuration

To perform Host Configuration operations on Juniper devices, a username and password must be entered. To accomplish this, SCM includes a device icon subviews menu option (Secure Configuration) which appears only for the Juniper model types listed under “Using SCM with supported juniper devices” on page 63. Secure Configuration contains a UserName/Password dialog box for use when connecting to supported Juniper devices via SSH. A similar dialog box is available by choosing Options > Capture in SCM (also only available for selected Juniper model types).

Note: The device model Username/Password data persists in the SPECTRUM database in the attribute secureModelInfo on the ScmTemplate model type. User names and passwords do not appear as text when stored in this attribute, enhancing security.

Performing a juniper host capture

1. Model a supported Juniper device (see “Using SCM with supported juniper devices” on page 63).

2. Launch SCM from the device model (Utilities > Configuration Manager).

3. Create an SCM template for this model type (Setup > Templates).

4. Perform a host configuration capture using the user name and password required by the device (you must also name the configuration).

65

Chapter 12: The User Interface

Most SCM work is completed in the Configuration Manager: Main window, the Configurations window, and the Templates window. This chapter describes the Configuration Manager: Main window and its subordinate views.

In this chapter

• “Starting SCM” on page 65

• “Configuration Manager: Main window” on page 66

• “Device Specific Configurations window” on page 69

• “Shared Configurations window” on page 69

• “SCM: Templates window” on page 70

Starting SCMProcedure

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 windowPrerequisites

• Start SpectroGRAPH.

• Start SCM: see “Starting SCM” on page 65

References


• See “Configuration List box” on page 67.

• See “Configuration Information section” on page 68.

• See “Search/Filter option” on page 68.

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.

• 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 14-6 on page 100 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” on page 74.

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 device-specific, and identifies the selected device type.

Configuration Manager: Main window


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” on page 67 for information about this interface feature.

Configuration Information Section (F) Contains historical information about the selected configuration. See “Configuration Information section” on page 68.

Search/Filter Option (G) A tool that helps search the contents of the Configuration list box. See “Search/Filter option” on page 68.

Configuration List box

References


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” on page 76.

• The Scm resource file to create new defaults that are used each time SCM is started; see “Scm resource file” on page 45.

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 LoadedP = Partially Loaded— = Not Loaded



Configuration Information section

References


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.

Search/Filter option

References

• See Figure 14-10 on page 103

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.

Device Specific Configurations window


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.

Device Specific Configurations windowPrerequisites



• Select View > Device Specific Configurations.

References


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.

Shared Configurations windowPrerequisites



• Select View > Shared Configurations.

References


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.

SCM: Templates windowPrerequisites



• Select Setup > Templates.

or

Right-click within the Configuration Manager: Main window; then select Templates.

References


• See “Setup > Templates” on page 91.

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” on page 78, “Edit menu” on page 78, and “View menu” on page 79.

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” on page 68.

Template Information Section (E) Contains historical information about the selected template. See “Template Information section” on page 71.

Status Bar (F) This window element is inactive for this product release.

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.

SCM: Templates window


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” on page 76.

• Through the Scm resource file to create a new default that is used each time SCM is started; see “Scm resource file” on page 45.

Template Detail Section (I) Lists information on devices, attributes, and flags used in the selected templates. See “Template Detail section” on page 71.

Template Information section

References


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.

TimeModified (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.

Template Detail section

References


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.

73

Chapter 13: Menus, Icons, and Buttons

This chapter contains descriptive information about all interactive elements in the SCM interface.

In this chapter

• “Pull Down Menus—Main Window” on page 74

• “Pull Down Menus—Templates window” on page 77

• “File > Delete” on page 80

• “File > Rename” on page 80

• “File > Exit” on page 80

• “Model > Navigate Components...” on page 80

• “Model > Select Model...” on page 81

• “Options > Capture...” on page 82

• “Options > Load...” on page 82

• “Options > Verify...” on page 83

• “Options > Compare...” on page 83

• “Options > Schedule...” on page 84

• “Options > Edit Host Configuration...” on page 86

• “Options > Edit Model Configuration...” on page 87

• “Options > Edit Mask...” on page 88

• “Options > Preferences” on page 89

• “Options > Preferences > Settings” on page 89

• “Options > Preferences > Attributes” on page 90

• “Options > Preferences > Search” on page 90

• “Setup > Templates” on page 91

• “Help > About Configuration Manager” on page 91

74

• “Help > About Configuration Manager” on page 91

• “Help > Online Manuals” on page 91

Pull Down Menus—Main WindowPrerequisites

• Start SpectroGRAPH; see Getting Started with SPECTRUM for Administrators (0985).


References


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.

File menu

References


• See Figure 14-28 on page 120 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.

View menu

References


Description

Shared Configurations (A) Displays shared configurations. The diamond-shaped button indicates the selected menu item.

Device Specific Configurations (B) Displays device-specific configurations. The diamond-shaped button indicates the selected menu item.

Pull Down Menus—Main Window


Model menu

References


• See “Model > Navigate Components...” on page 80.

• See “Model > Select Model...” on page 81.

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.

Options menu

References


• See “Security features” on page 33.

• See “Options > Capture...” on page 82.

• See “Options > Load...” on page 82

• See “Options > Verify...” on page 83

• See “Options > Compare...” on page 83

• See “Options > Schedule...” on page 84

• See “Options > Edit Host Configuration...” on page 86.

• See “Options > Edit Model Configuration...” on page 87

• See “Options > Edit Mask...” on page 88

• See “Preferences menu” on page 76

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.

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” on page 76

To create new defaults that apply each time SCM is started, edit the Scm resource file; see “Scm resource file” on page 45.

Preferences menu

References


• See “Options > Preferences” on page 89.

• See “Options > Preferences > Settings” on page 89.

• See “Options > Preferences > Attributes” on page 90.

• See “Options > Preferences > Search” on page 90.

Description

Preferences Dialog Box (A) Displays tabs for viewing and changing landscapes, settings, attributes, and search parameters.

Pull Down Menus—Templates window


Setup menu

References


• See “SCM: Templates window” on page 70

Description

Templates (A) Opens the SCM: Templates window in which you can create, edit, delete, and save templates.

Help menu

References


• See “Help > About Configuration Manager” on page 91.

• See “Help > Online Manuals” on page 91.

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.

Pull Down Menus—Templates windowPrerequisites

• Start SpectroGRAPH; see Getting Started with SPECTRUM for Administrators (0985).


• Select Setup > Templates.

References


Description

SCM: Templates Window (A) Contains three pull down menus organized as follows: “File menu” on page 78, “Edit menu” on page 78, and “View menu” on page 79.



File menu

References


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” on page 76.

• To set the modified Save functionality as the new default each time SCM is started. edit the Scm resource file; see “Scm resource file” on page 45.

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.

Edit menu

References

• See Figure 14-17 on page 109

Description

Discard All Changes (A) Discards the in-process <UNTITLED> template and displays a list of existing templates.

Pull Down Menus—Templates window


View menu

References

• See Figure 14-18 on page 110 to see the View menu.

• See Figure 14-13 on page 106 to locate the Template list box.

• See Figure 14-15 on page 107 to locate the Attribute list box.

Overview

The View menu (Figure 14-18 on page 110) is split into two sections divided by a light gray line. The top three menu selections determine the sort order of templates in the Template list box; the bottom three menu selections determine the sort order of attributes in the Attribute list box.

The diamond-shaped button on the View menu indicates which menu item is currently selected.

Description

View By Template Name (A) Sorts the templates in the Template list by template name (alphabetically).

View By Create Time (B) Sorts the templates in the Template list by the time the templates were created.

View By Modify Time (C) Sorts the templates in the Template list by the last time the templates were changed.

View By Attributes (D) Sorts the attributes in the Attribute list by Device, with a secondary alphabetical sort by Attribute. This is the default sort order in a new template that has not yet been saved.

View By Flags (E) Sorts the attributes in the Attribute list by Flags, with a secondary alphabetical sort by Device and Attribute.

View By Sequence (F) Sorts the attributes in the Attribute list by the sequence in which they were originally added to the template. Whenever a template is saved, the default sort order changes to View by Sequence.

Generally, when you add an attribute to the Attribute list in the Templates window, SCM makes it last in terms of sequence. To insert a new attribute at another point in the sequence:

1. Choose View > View By Sequence.

2. Select the attribute you want to add from the Insertable Attribute list.

3. Select the attribute in the Attribute list you want the new attribute to follow sequentially.

4. Click the left arrow button to insert the new attribute at the desired point in the Attribute list.



File > DeleteReferences


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.

File > RenameReferences


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.

File > ExitReferences


Description

Yes Button (A) Confirms the close operation to exit SCM.

No Button (B) Cancels the close operation.

Model > Navigate Components...References


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.

Model > Select Model...


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.

Model > Select Model...References


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.



Options > Capture...References


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” on page 68.

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.

Options > Load...References


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.

Options > Verify...


Options > Verify...References


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.

Options > Compare...References


• See “Host Config Diff window” on page 83.

• See “Attribute Diff window” on page 84.

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.

Host Config Diff window

Prerequisites

Select Option > Compare...; then select Host Config Diff.

References


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.

Attribute Diff window

Prerequisites

Select Option > Compare...; then select Attribute Diff.

References


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.

Options > Schedule...References


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.

Options > Schedule...


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.

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.



Options > Edit Host Configuration...References


• See “File menu” on page 86.

• See “Edit Menu” on page 86.

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.

File menu

References


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.

Edit Menu

References


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.

Options > Edit Model Configuration...


Options > Edit Model Configuration...References


• See “File menu” on page 87.

• See “Edit menu” on page 87.

• See “View menu” on page 88.

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” on page 68.

Model Attribute Editing Area (D) An interactive area for changing model attributes.

File menu

References


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.

Edit menu

References


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.




View menu

References


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.

Options > Edit Mask...References


• See “Options menu” on page 75 for a description of the Edit Mask... feature.

• See “File Menu” on page 88.

• See “Edit menu” on page 89.

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.

File Menu

References


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.

Options > Preferences


Edit menu

References


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.


Options > PreferencesReferences


• See “Options > Preferences > Settings” on page 89.

• See “Options > Preferences > Attributes” on page 90.

• See “Options > Preferences > Search” on page 90.

Description

Preferences Dialog Box Tabs (A) Allows users to temporarily set attributes, settings, and search parameters for the current SCM session.

Options > Preferences > SettingsReferences


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...” on page 82.

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.

Options > Preferences > AttributesReferences


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.

Options > Preferences > SearchReferences


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.

Setup > Templates


Setup > TemplatesReferences


• See “SCM: Templates window” on page 70.

Description

SCM: Templates Window (A) Enables the user to create templates for capturing configurations.

Help > About Configuration ManagerReferences


Description

SCM General Information Pop Up (A) Contains SCM version, Aprisma contact, and product copyright information.

Help > Online ManualsReferences


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.

93

Chapter 14: Figures

This chapter contains a sequential listing of all figures in this document.

In this chapter

• Figure 14-1: How SPECTRUM Configuration Manager Works: Capturing a Configuration File page 95

• Figure 14-2: How SPECTRUM Configuration Manager Works: Loading a Configuration File page 96

• Figure 14-3: How SPECTRUM Configuration Manager Works: Capturing SNMP Attributes page 97

• Figure 14-4: How SPECTRUM Configuration Manager Works: Loading SNMP Attributes page 98

• Figure 14-5: Security Token File page 99

• Figure 14-6: Configuration Manager: Main Window page 100

• Figure 14-8: Main Window—Configuration List Box page 102

• Figure 14-9: Main Window—Configuration Information Section page 103

• Figure 14-10: Main Window—Search/Filter Option page 103

• Figure 14-11: Main Window—Device Specific Configurations page 104

• Figure 14-12: Main Window—Shared Configurations page 105

• Figure 14-13: SCM: Templates Window page 106

• Figure 14-14: SCM: Templates Window—Template Information Section page 107

• Figure 14-15: Templates Window—Template Detail Section page 107

• Figure 14-16: Templates Window—File Menu page 108

• Figure 14-17: Templates Window—Edit Menu page 109

• Figure 14-18: Templates Window—View Menu page 110

• Figure 14-19: Main Window—Pull Down Menus page 111

• Figure 14-20: File Menu page 112


Chapter 14: Figures

• Figure 14-21: View Menu page 113

• Figure 14-22: Model Menu page 114

• Figure 14-23: Options Menu page 115

• Figure 14-24: Setup Menu page 116

• Figure 14-25: Help Menu page 117

• Figure 14-26: File > Delete page 118

• Figure 14-27: File > Rename page 119

• Figure 14-28: File > Exit page 120

• Figure 14-29: Model > Navigate Components... page 121

• Figure 14-30: Model > Select Model... page 122

• Figure 14-31: Options > Capture... page 123

• Figure 14-32: Options > Load... page 124

• Figure 14-33: Options > Verify... page 125

• Figure 14-34: Options > Compare... page 126

• Figure 14-37: Options > Schedule... page 129

• Figure 14-38: Options > Edit Host Configuration... page 130

• Figure 14-41: Options > Edit Model Configuration... page 132

• Figure 14-46: Options > Edit Mask... page 136

• Figure 14-49: Options > Preferences page 138

• Figure 14-50: Options > Preferences > Settings page 139

• Figure 14-51: Options > Preferences > Attributes page 140

• Figure 14-52: Options > Preferences > Search page 141

• Figure 14-53: Setup > Templates... page 142

• Figure 14-54: Help > About Configuration Manager page 143

• Figure 14-55: Help > Online Manuals page 144


Figure 14-1: How SPECTRUM Configuration Manager Works:Capturing a Configuration File

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.

1>

>

Administrator PC or Workstation includes:

- SCM

- TFTP Server

13

3

2

Administrator’s PC or Workstation SPECTRUM SpectroSERVER (Database)

TFTP Server

>

>

4

>5>

>

Physical Device(For Example, Router)

>

>


Chapter 14: Figures

Figure 14-2: How SPECTRUM Configuration Manager Works:Loading a Configuration File

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.

2>

>


- SCM

- TFTP Server

24

4

3


TFTP Server

>

>

1

>


>

>

>

5

>


Figure 14-3: How SPECTRUM Configuration Manager Works:Capturing SNMP Attributes

1 SCM makes a request through the SpectroSERVER for SNMP values from the physical device.

1>


- SCM

1


>Physical Device(For Example, Router)


Chapter 14: Figures

Figure 14-4: How SPECTRUM Configuration Manager Works:Loading SNMP Attributes

1 SCM makes a request through the SpectroSERVER for the physical device to set SNMP attribute values on the physical device.

1>


- SCM

1


>



Figure 14-5: Security Token File


Chapter 14: Figures

Figure 14-6: Configuration Manager: Main Window

A Toolbar Buttons E Configuration List Box; see Figure 14-8

B Pull Down Menus F Configuration Information Section; see Figure 14-9

C Navigational Overview Window G Search/Filter Option; see Figure 14-10

D Window Title Bar

G

A B DC E F


Figure 14-7: Configuration Load Scenarios.

Scenario 1 Load configuration in db to device as running and startup configurations.

Scenario 2 Load configuration in db to device as running configuration only; startup configuration is loaded manually through local management.

Scenario 3 Load configuration in db to device as startup configuration only; device loads the startup configuration as the running configuration when the device is rebooted.

Running Startup

Device

SpectroSERVER

>

> >

ConfigurationConfiguration

Running Startup

Device

>

>

ConfigurationConfigurationRunning Startup

Device

>

>

ConfigurationConfiguration

>

SpectroSERVER DatabaseSpectroSERVER Database

Scenario 1

Scenario 2 Scenario 3

>

>

Local

>

Management

Database


Chapter 14: Figures

Figure 14-8: Main Window—Configuration List Box

A Landscape Name C Date Modified

B Device Name D Load Status

AB

DC


Figure 14-9: Main Window—Configuration Information Section

Figure 14-10: Main Window—Search/Filter Option

A Source F Time Loaded

B Time Created G Loaded By

C Created By H Text Box

D Time Modified I Notes Button

E Modified By

A Small Flashlight Icon C Search/Filter Button

B Case Sensitive Button D Text Box

AB

H

CDEFG

I

B C D

A


Chapter 14: Figures

Figure 14-11: Main Window—Device Specific Configurations

A Configuration List Box

B Window Title Bar

C View Pull Down Menu

BC

A


Figure 14-12: Main Window—Shared Configurations

A Configuration List Box D Text Box

B Window Title Bar E Choose... Button

C View Pull Down Menu

BC

A

ED


Chapter 14: Figures

Figure 14-13: SCM: Templates Window

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-14 on page 107

J Template Detail Section; see Figure 14-15 on page 107

A B C D D E

G HF JI


Figure 14-14: SCM: Templates Window—Template Information Section

Figure 14-15: Templates Window—Template Detail Section

A Time Created D Modified By

B Created By E Text Box

C Time Modified F Notes Button

A Template Detail Button E Insertable Attribute List

B Device List F Include Host Configuration Field

C Attribute List G Transfer Arrows

D Flags List (scroll window to view)

A

BCD

E F

A B C D E

F G


Chapter 14: Figures

Figure 14-16: Templates Window—File Menu

A New D Delete

B Save E Close

C Save As

ABCDE


Figure 14-17: Templates Window—Edit Menu

A Discard All Changes

A


Chapter 14: Figures

Figure 14-18: Templates Window—View Menu

A View by Template Name D View by Attributes

B View by Create Time E View by Flags

C View by Modify Time F View by Sequence

ABCDEF


Figure 14-19: Main Window—Pull Down Menus

A Pull Down Menu Items:

- File; see Figure 14-20 on page 112

- View; see Figure 14-21 on page 113

- Model; see Figure 14-22 on page 114

- Options; see Figure 14-23 on page 115

- Setup; see Figure 14-24 on page 116

- Help; see Figure 14-25 on page 117

A


Chapter 14: Figures

Figure 14-20: File Menu

A Delete; see Figure 14-26 on page 118

B Rename...; see Figure 14-27 on page 119

C Exit; see Figure 14-28 on page 120

A

B

C


Figure 14-21: View Menu

A Shared Configurations; see Figure 14-12 on page 105

B Device Specific Configurations; see Figure 14-11 on page 104

A

B


Chapter 14: Figures

Figure 14-22: Model Menu

A Navigate Components...; see Figure 14-29 on page 121

B Select Model...; see Figure 14-30 on page 122

A

B


Figure 14-23: Options Menu

A Capture... F Edit Host Configuration...; see Figure 14-38 on page 130

B Load... G Edit Model Configuration...; see Figure 14-41 on page 132

C Verify... H Edit Mask...; see Figure 14-46 on page 136

D Compare... I Preferences; see Figure 14-49 on page 138

E Schedule...

ABCDEFGHI


Chapter 14: Figures

Figure 14-24: Setup Menu

A Templates...; see Figure 14-53 on page 142

A


Figure 14-25: Help Menu

A About Configuration Manager; see Figure 14-54 on page 143

B Online Manuals; see Figure 14-55 on page 144

A

B


Chapter 14: Figures

Figure 14-26: File > Delete

A Yes Button

B No Button

>

>A B


Figure 14-27: File > Rename

A Text Box

B OK Button

C Cancel Button

>

>

B C

A


Chapter 14: Figures

Figure 14-28: File > Exit

A Yes Button

B No Button

>

>A B


Figure 14-29: Model > Navigate Components...

A Device Selection Box

B OK Button

C Apply Button

D Cancel Button

>

>

B C D

A


Chapter 14: Figures

Figure 14-30: Model > Select Model...

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

>

>

G H I J

C

D

E

F

A B


Figure 14-31: Options > Capture...

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

F C

A

B

E D

G


Chapter 14: Figures

Figure 14-32: Options > Load...

A Commit Loaded configuration to NVRAM Button

B Yes Button

C No Button

>

>

B C

A


Figure 14-33: Options > Verify...

A Yes Button

B No Button

>

>

A B


Chapter 14: Figures

Figure 14-34: Options > Compare...

A OK Button

B Host Config Diff Button; see Figure 14-35 on page 127

C Attribute Diff Button; see Figure 14-36 on page 128

>

>

A CB


Figure 14-35: Host Config Diff Window

A Configuration Name

B Highlighted Difference(s)

C Close Button

> A

B

C


Chapter 14: Figures

Figure 14-36: Attr Diff Window

A Model Name D Configuration Name

B Attribute Name E Close Button

C Configuration Name

>A B C D

E


Figure 14-37: Options > Schedule...

A Save Button

B Reset Button

C Close Button

>

>

A B C


Chapter 14: Figures

Figure 14-38: Options > Edit Host Configuration...

A Edit Host Configuration Window

B Pull Down Menus

- See File Menu; Figure 14-39 on page 131

- See Edit Menu; Figure 14-40 on page 131

>

>

AB


Figure 14-39: Edit Host Configuration...—File Menu

Figure 14-40: Edit Host Configuration...—Edit Menu

A Save & Close C Save To File...

B Print... D Close

A Cut D Find

B Copy E Find Again

C Paste

AB

>

CD

AB

>

CDE


Chapter 14: Figures

Figure 14-41: Options > Edit Model Configuration...

A Toolbar Button C Search/Filter Option

B Pull Down Menus

- File Menu; see Figure 14-42 on page 133

- Edit Menu; see Figure 14-43 on page 133

- View Menu; see Figure 14-44 on page 134

D Model Attribute Editing Area

>

>

D

B CA


Figure 14-42: Edit Model Configuration...—File Menu

Figure 14-43: Edit Model Configuration...—Edit Menu

A Save

B Close

A Cut D Find

B Copy E Find Again

C Paste

A

>

B

A

>

BCDE


Chapter 14: Figures

Figure 14-44: Edit Model Configuration...—View Menu

A View by Attributes

B View by Flags

C View by Sequence

A

>

BC


Figure 14-45: Edit Model Configuration...—Model Attribute Editing Area

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

A B C D

E>

}

J I H

G

F


Chapter 14: Figures

Figure 14-46: Options > Edit Mask...

A Pull Down Menus



B Text Field

>

>A B


Figure 14-47: Edit Mask...—File Menu

Figure 14-48: Edit Mask...—Edit Menu

A Save & Close C Save To File

B Print D Close

A Cut D Find

B Copy E Find Again

C Paste

A

>

BC

D

A

>

BC

DE


Chapter 14: Figures

Figure 14-49: Options > Preferences

A Preferences Dialog Box Tabs

>

>

A


Figure 14-50: Options > Preferences > Settings

A Settings Tab D Apply Button

B Commit Loaded configuration to NVRAM Button; see “Options > Load...” on page 82

E Reset Button

C OK Button F Cancel Button

>

>

C D E F

A

B


Chapter 14: Figures

Figure 14-51: Options > Preferences > Attributes

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

>

>

D E F G

A

B {C {


Figure 14-52: Options > Preferences > Search

A Search Tab D Apply Button

B Enable Extended Search Button E Reset Button

C OK Button F Cancel Button

>

>

C D E F

A

B


Chapter 14: Figures

Figure 14-53: Setup > Templates...

A SCM: Templates Window; see Figure 14-13 on page 106

>

>

A


Figure 14-54: Help > About Configuration Manager

A OK Button

A

>

>


Chapter 14: Figures

Figure 14-55: Help > Online Manuals

A Documentation Location Dialog Box D OK Button

B Browse... Button E Text Box

C Cancel Button

B

>

D C

E

>A


Figure 14-56: Templates Window—Pull Down Menus

A Pull Down Menus



- View Menu; see Figure 14-18 on page 110

A


Chapter 14: Figures

147

Appendix A

This chapter contains information about database constraints when working with SCM configurations.

SPECTRUM database storage constraintsOverview

Because of SPECTRUM’s database storage limitations, there are constraints on the size of SCM configurations and templates. When you work with SCM, do not exceed the maximums listed in Table 15-1:

Table 15-1: SPECTRUM Database Storage Constraints

SCM displays an error message if you try to save a configuration or template that is too large, or if you try to capture a configuration that is too large. At present, SCM does not indicate whether it is the size of the configuration or the number of attributes that exceeds the limit.

Type Maximum Limit Comments

Templates 4.0 MB The largest template you create probably will not exceed the maximum size allowed.

Configurations 4.0 MB If you capture a configuration from a device with attributes that have many instance IDs, the size of the configuration could possibly exceed the maximum limit.

In this case, split the large configuration into two or three smaller configurations.

Cisco Host Configuration Files

4.0 MB Although unlikely, it is possible that the host configuration file size could exceed the maximum limit.

In this case, SCM cannot capture the host configuration file.


Appendix A

149

Index

Aabout device templates and host configuration

files 17about installing SPECTRUM Configuration

Managerinstalling SCM 11

about SCM 11about security in SPECTRUM Configuration

Manager 33about SPECTRUM Configuration Manager 11about the scheduler 37about the SCM log file 43about the Scm resource file 45about the SPECTRUM event log 41about the SPECTRUM event log and the SCM log

file 41about the Windows® NT/2000 Task Scheduler

service 38alarms

configure 51Aprisma Technical Assistance Center (ATAC)

contact informationcontact information

Aprisma contact information 8attributes

adding to a template 79

Bbenefits

SCM 16buttons

menus and icons 73

Ccapture

configurationverify 31

capture statusverifying 31

Cisco routershost configuration file 23

codesevent 42

configurationcapture

verify status 31configuration captures 31configuration files 17, 19

devices with 21selecting 21

configuration information section 68configuration list box 67configuration loading

failure 28configuration loading details 25configuration manager

main window 66configurations 12

command line capture 55loading 25

Configurations and TemplatesExporting 59Importing 58

configurations windowdevice specific 69


Index

Ddata file

required for some CLI commands 54definition

configuration management 12definitions

configurations 12SCM 13, 15

device specific configurations window 69device templates 17devices

selecting 21devices with host configuration files 21

installation information 19document feedback 8documents

online 9

Eedit

passwords 35edit menu 78error message

No instance exists 21event codes 42event log 41, 42Exporting Configurations and Templates 59

Ffailure

verification 32features

security 33feedback 8figures 93File > Delete 80File > Exit 80File > Rename 80file menu 74, 78files

configuration 19filter option 68finding load results

logging 28

Hhelp menu 77hiding passwords, keywords, or tokens 35

host configuration file masking 22host configuration files 17, 19

devices with 21selecting 21

how does SPECTRUM configuration manager work? 15

how to use the SPECTRUM event log 42

Iicons

menus and buttons 73Importing Configurations and Templates 58interface

user 65Interface Models 22interpreting SCM event codes 42

JJuniper

SCM 63

Kkeyboard shortcuts for menu items 49keywords

hiding 35

Lload

configurationsdevices

special information 30failure 28

Load Failure alarms 51load results

logging and finding 28loading a configuration

from command line 56loading configurations 25

details 25loading configurations from the configuration

manager main window 27log file 41, 43logging and finding load results 28


Mmain window 66

loading configurations 27pull down menus 74

maskhost configuration files 22

menu itemskeyboard shortcuts 49

menuspull down

main window 74menus, icons, and buttons 73Model > Navigate Components... 80Model > Select Model... 81model menu 75

NNT

setting up TFTP 20

Oonline documents 9options

verification 32Options > Capture... 82Options > Compare... 83Options > Load... 82Options > Verify... 83options menu 75

Ppassword editing 35passwords

hiding 35preferences menu 76pull down menus

main window 74templates window 77

Rresource file

Scm 45

Sscheduler 37, 38

view results 38SCM 13, 15

event codes 42event log 41, 42

log file 41general information 11log file 43password editing 35running from command line 53scheduler 37, 38

view results 38security 33, 34starting from command line 54templates 17templates window 70uses 16

SCM configurations 12SCM functionality 15SCM installation 11Scm resource file 45search/filter option 68security

SCM 33, 34SNMP 33

security features 33selecting devices and host configuration files 21sequence

of attributes in a template 79setup menu 77shared configurations window 69shortcuts

keyboard 49SNMP security 33special load information for devices with host

configuration files 30Starting SCM 65

Ttemplate detail section 71template information section 71templates

adding attributes to 79device 17

templates window 70pull down menus 77

text conventionsconventions

text 8TFTP 19

setting up NT for 20tokens

hiding 35


Index

Uuser interface 65uses for SPECTRUM Configuration Manager 16

Vverification failure 32verification options 32Verify Failure alarms 51verifying host configuration file captures 31verifying the configuration

from command line 57, 58, 59verifying the configuration capture status 31view menu 74, 79viewing and editing host configuration

passwords 35viewing the results of scheduled operations 38

Wwhat are configurations? 12what if a load fails? 28what if a verification fails? 32what is a device template? 17what is configuration management?

configuration management 12what is SPECTRUM Configuration Manager? 13window

shared configurations 69templates 70

working with the scheduler 38

spectrum configuration manager - ca...

Documents