AutoDiscovery. User Guide. Document 0727

Transcription

1

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

3 Contents Notice... 2 Preface... 6 Intended Audience... 6 Text Conventions... 6 Document Feedback... 7 Online Documents... 7 Overview... 8 What Is?... 8 Understanding s Functionality... 9 User Interface Main Window Layout...10 File Menu...11 Edit Menu...11 View Menu...13 Configurations Menu...13 Result Sets Menu...14 Tools Menu...14 Window Menu...15 Help Menu...15 Toolbar...15 Creating Your Network Model What Are Configurations?...16 Discovery Configurations...16 Modeling Configurations...17 Discovery and Modeling Configurations...17 Why Use Different Types of Configurations?...17 Creating a Configuration...17 Discovery by IP List...18 Page 3

4 Step 1: The Custom and Existing Options...20 Step 2: The Community Strings Panel...20 Step 3: The SNMP Ports Panel...20 Step 4: The Attempt Panel...21 Step 5: The Options Panel...21 Step 6: The IP Addresses Panel...21 Step 7: Completing the Configuration...22 Discovery by Range...22 Step 1: The Custom and Existing Options...24 Step 2: The IP Range Boundary List Panel...24 Step 3: The Community Strings Panel...24 Step 4: The SNMP Ports Panel...25 Step 5: The Attempt Panel...25 Step 6: The Options Panel...25 Step 7: Completing the Configuration...25 Discovery by Router...26 Step 2: The IP Boundary List Panel...28 Step 3: The IP Addresses Panel...28 Step 4: The Community Strings Panel...29 Step 5: The SNMP Ports Panel...29 Step 6: The Attempt Panel...29 Step 7: The Options Panel...30 Step 8: The Subnet Discovery Panel...30 The Subnet Discovery Level...30 The Maximum Subnet Size...32 Step 9: Completing the Configuration...32 Modeling to SPECTRUM...33 Step 1: The Custom and Existing Options...35 Step 2: The Root Container Panel...35 Step 3: The Modeling Layout Panel...36 Step 4: The Modeling Options Panel...37 Step 5: The Protocol Options Panel...38 Step 6: Activation Time...39 Page 4

5 Step 7: Completing the Configuration...40 Stored Configurations Accessing a Stored Configuration...41 Scheduling a Stored Configuration for Execution...42 Step 1: Enable the Scheduler...43 Step 2: Select the Date and Time...43 Step 3: Select How Often the Configuration Runs...44 Step 4: Review the Continuous Modeling Options Panel...45 Step 5: Configure the Automatic Results Panel...46 Step 6: Save the Schedule Options...47 Running a Stored Configuration From the Command Line...47 Result Sets What Are Result Sets?...49 Device Information...51 Accessing and Using Result Sets...53 Sorting Results...54 Filtering Results...54 Exporting Results...56 Comparing Results...58 Continuous Discovery Result Sets...60 Accessing a Global Result Set...60 Accessing an Individual Result Set...61 Analyzing the Result Sets...62 Appendix A: SPECTRUM s SNMP Service Appendix B: Unplaced Models Index Page 5

6 Preface In This Section Intended Audience [page 6] Text Conventions [page 6] Document Feedback [page 7] Online Documents [page 7] Intended Audience This document is intended to serve as a guide for network managers who are using the application to model their networks in SPECTRUM. Text Conventions The following text conventions are used in this document: Element Convention Used Example Variables (The user supplies a value for the variable.) The directory where you installed SPECTRUM (The user supplies a value for the variable.) Courier and Italic in angle brackets (<>) <$SPECROOT> Type the following: DISPLAY=<workstation name>:0.0 export display Navigate to: <$SPECROOT>/app-defaults Solaris and Windows directory paths Unless otherwise noted, directory paths are common to both operating systems, with the exception that slashes (/) should be used in Solaris paths, and backslashes (\) should be used in Windows paths. <$SPECROOT>/app-defaults on Solaris is equivalent to <$SPECROOT>\app-defaults on Windows. On-screen text Courier The following line displays: path= /audit Page 6

7 Element Convention Used Example User-typed text Courier Type the following path name: C:\ABC\lib\db Cross-references References to SPECTRUM documents (title and number) Underlined and hypertextblue Italic See Document Feedback [page 7]. OneClick Console (5130) Document Feedback Please send feedback regarding SPECTRUM documents to the following address: Thank you for helping us improve our documentation. Online Documents SPECTRUM documents are available online at: Check this site for the latest updates and additions. Page 7

8 Overview This section provides a general description of functionality. In This Section Note: This guide describes the capability of the legacy SpectroGRAPH interface. For Spectrum Release 8.1 and later, run discovery using the OneClick interface. For more information about discover operations and capabilities in OneClick, refer to the Modeling Your IT Infrastructure Administrator Guide (5167). What Is? [page 8] Understanding s Functionality [page 9] What Is? is an automated discovery and modeling system. It is a SPECTRUM application that can be launched from the SpectroGRAPH and can be used to automatically discover and model your network elements including devices, interfaces, and connections. Using only the discovery functionality, which is available to all users, you can perform network inventories and export the resulting data to various display formats for distribution across your organization. If you have readwrite privileges, you can use discovery capabilities in conjunction with SPECTRUM s patented modeling technology to create and maintain an accurate software model of your network. This intelligent network model is what enables SPECTRUM to determine actual points of failure and suppress superfluous downstream alarms. Note: uses a high percentage of resources on the machine hosting SpectroSERVER. Other client applications may have reduced performance when is running. Page 8

9 Understanding s Functionality This guide is divided into sections to help you understand the interface and the tasks you can perform using it. User Interface [page 10] section explains each of the menus and toolbars available in the interface. Creating Your Network Model [page 16] explains how to set up a new configuration to discover and, if desired, model your network infrastructure. See also What Are Configurations? [page 16]. Stored Configurations [page 41] explains how to access and use saved configurations that store information on how a network should be discovered or discovered and modeled. Result Sets [page 49] explains how to interpret and use the data that gathers when discovering your network infrastructure. Page 9

10 User Interface This section explains the commands and options found in the interface. In This Section Main Window Layout [page 10] File Menu [page 11] Edit Menu [page 11] View Menu [page 13] Configurations Menu [page 13] Result Sets Menu [page 14] Tools Menu [page 14] Window Menu [page 15] Help Menu [page 15] Toolbar [page 15] Main Window Layout s main window consists of various menus and a toolbar (all described in the following sections) plus the three panels described below: The Stored Configurations panel (in the upper left area of the window) lists and provides access to each of the discovery/modeling configurations you have created and saved. For more information on using this panel, refer to Stored Configurations [page 41]. See also What Are Configurations? [page 16]. The Results list (in the lower left area of the window) lists and provides access to each of the result sets generated by executed configurations. For more information on using this panel, refer to Result Sets [page 49]. The large work area on the right side of the window displays the dialog boxes you use to create/modify configurations and to view/filter/export result sets. Page 10

11 File Menu The main window s File menu offers the following four commands: Open - Opens any configuration file selected from the Stored Configurations panel or any result set selected from the Results list. Close - Closes a configuration creation dialog box, reopened configuration, or result set in the main window s work area. If there are multiple displays open, this option closes the one in the foreground. Scheduled jobs - Opens the Scheduled jobs dialog box, which lists configurations that have been scheduled for future execution. (See Scheduling a Stored Configuration for Execution [page 42]) Exit - Closes the main window and exits. Edit Menu The main window s Edit menu offers the following six commands: Cut - Removes selected text from text entry boxes in dialog boxes and stores it in the paste buffer. Copy - Copies selected text from text entry boxes in dialog boxes into the paste buffer. Paste - Places the current contents of the paste buffer into a text box where the cursor is positioned or overlays selected text with paste buffer contents. Delete - Removes a selected configuration from the Stored Configurations panel or a selected result set from the Results list. Rename - Displays a dialog box allowing you to enter a new name for an existing configuration or result set. Preferences - Displays the Preferences dialog box. Page 11

12 Figure 1: Preferences Dialog Box - On the Preferences dialog box s General tab, clear the Cascade windows check box if you want dialog boxes to be stacked directly on top of each other in the main window s work area. - You can also edit the ICMP daemon Port Number box to change the server port used when attempting to discover pingable devices. - The Output Level menu lets you dictate the amount of information sent to the modeling output window and log file for each discovery process. The menu provides three choices: None, Simple, and Verbose. - None indicates that no messages are sent. - Simple (the default value) dictates that only summary messages are sent to both the modeling output window and the log file. - Verbose dictates that more detailed messages be sent to the window and log file. Note: In addition, you can have modeling and mapping status information written to an output file. This debugging functionality can be turned on in the Model Information view. See the Distributed SpectroSERVER (2770) guide for instructions and more information. Page 12

13 The Output Level setting does not persist between shutdowns of. Thus, if you would like something other than the default value of Simple, you must set this option in each session. The Default Filter tab lets you establish default settings for all filtering operations (see Filtering Results [page 54]). View Menu The main window s View menu offers the following three options: Toolbar - Displays/hides a toolbar that provides button access to frequently used commands that are also available in menus (for description of individual toolbar buttons, see Toolbar [page 15]). Toolbar Labels - Displays/hides labels for toolbar buttons. Tool Tips - Activates/deactivates descriptive text displayed temporarily when you mouse over a toolbar button. Configurations Menu The main window s Configurations menu offers the following seven commands: Duplicate - Creates a duplicate of any configuration file selected from the Stored Configurations panel. The duplicate is named Copy of <configuration name> and can be opened and used as a starting point for creating a new configuration that you presumably would like to base on the original. Start - Executes the selected configuration (or adds it to the pending queue if another configuration is in progress). Note that this command is unavailable for modeling configurations, which can only be executed in conjunction with discovery configurations. Export Configuration - Displays the same Save dialog box used for exporting result sets (see Exporting Results [page 56]) and lets you save the currently displayed configuration to a file on disk. Import Configuration - Displays the Open dialog box, which allows you to retrieve a configuration file stored on disk and add it to the list of Stored Configurations. Page 13

14 Import IP List text file - Displays an Open dialog box, which lets you create a new IP List discovery configuration from a text file. The text file should consist of one or more lines, where each line contains one IP address expressed in the standard IP address format (xxx.xxx.xxx.xxx). New Discovery Configuration - Opens a submenu for accessing three types of discovery-only configuration creation dialog boxes (IP List, Range, or Router). For more information, see Creating a Configuration [page 17]. New Modeling Configuration - Currently there is only one option on the submenu accessed by this option: SPECTRUM. For more information, see Creating a Configuration [page 17]. New Discover and Model Configuration - Opens a submenu for accessing three types of discovery and modeling configuration creation dialog boxes (IP List, Range, or Router). For more information, see Creating a Configuration [page 17]. Result Sets Menu The main window s Result Sets menu offers the following three commands: Delete Rows - Prompts you for confirmation, then deletes a selected row of device information in an open Results dialog box. Export - Lets you save all or part of the currently selected or currently open result set to a file on disk. For more information, see Exporting Results [page 56]. Model to SPECTRUM - Displays the Modeling Configuration dialog box, which lets you specify how you want the currently selected or currently open result set to be modeled to SPECTRUM. For more information, see Modeling to SPECTRUM [page 33]. Tools Menu The main window s Tools menu offers a single command, Device Differencing, which displays a dialog box allowing you to compare any two result sets. For more information on using this panel, refer to Comparing Results [page 58]. Page 14

15 Window Menu The main window s Window menu offers the following three commands: Cascade - If dialog boxes/windows are overlaid directly on top of each other in the main window s work area, this command rearranges them so that the upper left corner of each one is visible. Cycle - Brings the bottom dialog box/window to the top of the stack. Close All Windows - Closes all dialog boxes/windows launched from the main window. Help Menu The main window s Help menu offers the following commands: About - Displays copyright information. Online Manuals - Accesses the SPECTRUM documentation set, providing you have inserted the documentation CD-ROM according to the instructions in the SPECTRUM Installation Guide. Toolbar The main window s toolbar includes four buttons that provide alternative access to some of the frequently used menu commands: Click the New button to display the same three new configuration commands available from the Configurations menu. Click the Open button to open any selected entry from the Stored Configurations panel or the Results list. Click the Delete button to delete any selected entry from the Stored Configurations panel or the Results list. Click the Scheduled Jobs button to display a dialog box showing all configurations currently scheduled for execution. Page 15

16 Creating Your Network Model This section provides detailed instructions for performing specific tasks with. In This Section What Are Configurations? [page 16] Creating a Configuration [page 17] Discovery by IP List [page 18] Discovery by Range [page 22] Discovery by Router [page 26] Modeling to SPECTRUM [page 33] What Are Configurations? Both discovery and modeling operations are executed according to sets of user-specified guidelines called configurations. You create these reusable configurations via dialog boxes accessed from the main window s Configurations menu. Once a configuration is saved, a corresponding entry is added to the appropriate folder in the main window s Stored Configurations panel, where the configuration can then be accessed for modification, deletion, duplication, or execution (see Stored Configurations [page 41]). There are three basic types of configurations: Discovery Configurations [page 16] Modeling Configurations [page 17] Discovery and Modeling Configurations [page 17] Discovery Configurations Discovery configurations determine the focus and scope of a discovery session. Depending on the discovery method selected (IP Address, Range, or Router), you specify individual addresses and/or ranges of addresses to be queried and set other parameters to further limit or expand the discovery operation. You can run the discovery session at the time you create the configuration or schedule it for execution at a later time. Each Page 16

17 time a discovery configuration is executed, a result set is generated and a corresponding entry is added to the Results list in the main window. Modeling Configurations Modeling configurations specify how and where models of discovered devices are represented in SpectroGRAPH Topology views. Modeling configurations are executable only in conjunction with a result set generated by the execution of a discovery configuration. Note: Modeling functions are not available to read-only users. Discovery and Modeling Configurations Discovery and modeling configurations combine a particular set of discovery guidelines with a particular set of modeling guidelines. As with discovery configurations, you can run a combined discovery and modeling session at the time the configuration is created or schedule it to run at a later time. Execution of a discovery and modeling session also adds an entry to the main window s Results list. Note that discovery and modeling configurations, like modeling-only configurations, are not available to readonly users. Why Use Different Types of Configurations? By allowing discovery configurations and modeling configurations to be created independently and stored for future use, offers mixand-match flexibility that lets you customize the discovery/modeling process to more efficiently meet the unique and dynamic requirements of your network. For example, if you wish to see the results of particular discovery session modeled in different ways, you can execute it multiple times, specifying a different modeling configuration each time. Or you can re-use the same modeling configuration with different discovery configurations. Creating a Configuration All configurations (see What Are Configurations? [page 16]) are created via tabbed dialog boxes within the main window. You can open a discovery creation dialog box in any of the following ways: Page 17

18 From the main window s Configurations Menu [page 13], select the desired type of configuration (and discovery method, if applicable). On the main window s toolbar, click the New button. This displays the relevant commands from the Configurations menu. In the main window s Stored Configurations panel, right-click one of the configuration types (i.e, the second-level folders: IP List, Range, etc.). The discovery creation dialog box opened by any of the above varies in appearance and function according to the type of configuration/discovery method selected. Currently there are seven different possible combinations of configuration type and discovery method: Discover by IP List Discover by Range Discover by Router Model to SPECTRUM Discover by IP List and Model to SPECTRUM Discover by Range and Model to SPECTRUM Discover by Router and Model to SPECTRUM Note that each of the three discover and model configurations simply combines a modeling configuration with one of the three types of discovery configurations. Thus there are only four basic procedures involved. For detailed instructions on creating a configuration, refer to the following four topics: Discovery by IP List [page 18] Discovery by Range [page 22] Discovery by Router [page 26] Modeling to SPECTRUM [page 33] Discovery by IP List When this method is used, attempts to contact and identify only those devices at the IP addresses you specify when you create the configuration. Page 18

19 To begin, select a discovery by IP List option (using any of the methods described under Creating a Configuration [page 17]) and a tabbed configuration creation dialog box appears in the right side of the main window with the IP List tab in the foreground and the Schedule tab in the background, as shown in Figure 2. If you are creating a discovery and modeling configuration, the foreground page is labeled Discovery instead of IP List, and Filtering and Modeling tabs are also visible. Figure 2: Discovery by IP List To create a discovery configuration using the IP List method of discovery, follow the steps explained in the following sections. Page 19

20 Step 1: The Custom and Existing Options If you are creating a discovery-only configuration, go directly to Step 2: The Community Strings Panel [page 20]. For a combined discovery and modeling configuration, however, you have the following two options: The Custom option (selected by default) lets you create a new discovery configuration from scratch by performing Step 2: The Community Strings Panel [page 20] through Step 7: Completing the Configuration [page 22]. The Existing option lets you select and import a previously created discovery configuration from the adjacent list, then skip to Step 7: Completing the Configuration [page 22]. Note: This option is unavailable if there are no configurations of the desired type available in the Stored Configurations panel (see Accessing a Stored Configuration [page 41]). Step 2: The Community Strings Panel In the Community Strings panel, specify the SNMP community strings (passwords) for the devices you want discovered. By default, attempts to discover devices at the IP addresses you specify (see Step 6: The IP Addresses Panel [page 21]) if they have a community string of public. You can enter additional strings one-at-a-time by typing in the text entry box and clicking Add. Use the Del (for Delete ) and Mod (for Modify ) buttons to remove or change any strings in the list. Note: You can delete the public community string, but at least one valid string must be entered. Community strings are used in the order they appear, and depending on the Timeout and Retries settings (Step 4: The Attempt Panel [page 21]), the time spent attempting to discover a device with a particular string can mount up quickly, especially in large subnets. Therefore it is advisable to keep your most commonly used community string at the top of the list. Step 3: The SNMP Ports Panel If you are autodiscovering a managed node environment in which proprietary SNMP protocols use ports other than the default SNMP port used by (161), add these ports in the SNMP Ports panel. The discovery process uses the ports in the order listed. Page 20

21 Note: If you wish to rediscover and model previously modeled devices that use SNMP ports other than the default 161, you must use a combined discovery and modeling operation. If you run the discovery, exit and restart, and then model the results set, SpectroSERVER is not able to contact these devices because SNMP port IDs do not persist in the database. Step 4: The Attempt Panel In the Attempt panel, adjust the Timeout and Retries settings. Timeout specifies the number of seconds spends per attempt at contacting an address. The Retries setting specifies the number of additional attempts makes if the first one times out before contact is established. Step 5: The Options Panel In the Options panel, the Discover Pingables check box is selected by default. This causes to discover all devices within the specified list that support ICMP. If Pingables is not selected, discovers only those devices from the IP address list (Step 6: The IP Addresses Panel [page 21]) that respond to SNMP. Step 6: The IP Addresses Panel In the IP Addresses panel, specify the IP addresses you want to attempt to contact. You can enter addresses in one of two ways: Build a list of IP addresses one address at a time by entering addresses in the IP Address box and clicking Add. Add an entire list of IP addresses at once by clicking the Browse button to access the Open dialog box. Select a file containing a list of IP addresses, then click Open to add those addresses to the list for this configuration. The text file should consist of one or more lines, where each line contains one IP address expressed in the standard IP address format (xxx.xxx.xxx.xxx). Page 21

22 Step 7: Completing the Configuration The rest of the procedure varies depending on whether the configuration you are creating is for discovery only or for discovery and modeling. For a discovery-only configuration, at this point you can do any of the following: If you want to set a time for execution of the configuration, click the Schedule tab (see Scheduling a Stored Configuration for Execution [page 42] for detailed instructions). If you want to execute the configuration immediately, click the Save & Start button. After you provide a name for the configuration, it is added to the IP List folder in the Stored Configurations panel, a corresponding entry is added to the Results list, and a Results dialog box replaces the configuration creation dialog box. If you want to save the configuration for later use, click Save. You are prompted to provide a name, and then the configuration is added to the IP List folder in the Stored Configurations panel. If you want to dismiss the creation dialog box without saving the configuration, click Cancel. If you are creating a combined discovery and modeling configuration, click the Modeling tab to see the default settings and adjust them as desired using the instructions under Modeling to SPECTRUM [page 33]. You can also click the Filtering tab, which lets you predetermine which of the discovered devices are displayed in the Results dialog box and modeled to SPECTRUM when the configuration is executed. For detailed instructions, see Filtering Results [page 54]. When you are satisfied with the settings on all four tabs, use the Save or Save & Start buttons as described above. Discovery by Range When this method is used, attempts to contact and identify devices at each IP address within the IP address range(s) specified. To begin, select a discovery by range option (using any of the methods described under Creating a Configuration [page 17]) and a tabbed configuration creation dialog box appears in the right side of the main window with the Range tab in the foreground and the Schedule tab in the background, as shown in Figure 3. If you are creating a combined discovery and modeling configuration, the foreground page is labeled Page 22

23 Discovery instead of Range, and the Filtering and Modeling tabs are also visible. Figure 3: Discovery by Range To create a discovery configuration using the Range method of discovery, follow the steps explained in the following sections. Page 23

24 Step 1: The Custom and Existing Options If you are creating a discovery-only configuration, go directly to Step 2: The IP Range Boundary List Panel [page 24]. For a combined discovery and modeling configuration, you have the following two options: The Custom option lets you create a new discovery configuration from scratch by performing Step 2: The IP Range Boundary List Panel [page 24] through Step 7: Completing the Configuration [page 25]. The Existing option lets you select and import a previously created discovery configuration from the adjacent list, then skip to Step 7: Completing the Configuration [page 25]. Note: This option is unavailable if there are no configurations of the desired type available in the Stored Configurations panel (see Accessing a Stored Configuration [page 41]). Step 2: The IP Range Boundary List Panel In the IP Range Boundary List panel, define a range(s) of IP addresses to be discovered by entering the lowest address in the range in the From field and the highest address in the To field. Then click the Add button to add the range to the list. Repeat these steps to add multiple ranges. Step 3: The Community Strings Panel In the Community Strings panel, specify the SNMP community strings (passwords) for the devices you want discovered. By default, attempts to discover devices at the IP addresses you specify if they have a community string of public. You can enter additional strings one-at-a-time by typing in the text entry box and clicking Add. Use the Del (for Delete ) and Mod (for Modify ) buttons to remove or change any strings in the list. Note: You can delete the public community string, but at least one valid string must be entered. Community strings are used in the order they appear, and depending on the Timeout and Retries settings (Step 5: The Attempt Panel [page 25]), the time spent attempting to discover a device with a particular string can mount up quickly, especially in large subnets. Therefore it is advisable to keep your most commonly used community string at the top of the list. Page 24

25 Step 4: The SNMP Ports Panel If you are autodiscovering a managed node environment in which proprietary SNMP protocols use ports other than the default SNMP port used by (161), add these ports in the SNMP Ports panel. The discovery process uses the ports in the order listed. Note: If you wish to rediscover and model previously modeled devices that use SNMP ports other than the default 161, you must use a combined discovery and modeling operation. If you run the discovery, exit and restart, and then model the results set, SpectroSERVER is not able to contact these devices because SNMP port IDs do not persist in the database. Step 5: The Attempt Panel In the Attempt panel, adjust the Timeout and Retries settings. Timeout specifies the number of seconds spends per attempt at contacting an address. The Retries setting specifies the number of additional attempts makes if the first one times out before contact is established. Step 6: The Options Panel In the Options panel, the Discover Pingables check box is selected by default. This causes to discover all devices within the specified list that support ICMP. If Pingables is not selected, discovers only those devices from the IP address list (Step 2: The IP Range Boundary List Panel [page 24]) that respond to SNMP. Step 7: Completing the Configuration The rest of the procedure varies depending on whether the configuration you are creating is for discovery only or for discovery and modeling. For a discovery-only configuration, at this point you can do any of the following: If you want to set a time for execution of the configuration, click the Schedule tab (see Scheduling a Stored Configuration for Execution [page 42] for detailed instructions). If you want to execute the configuration immediately, click the Save & Start button. After you provide a name for the configuration, it is added to the Range folder in the Stored Configurations panel, a Page 25

26 corresponding entry is added to the Results list, and a Results view replaces the configuration creation dialog box. If you want to save the configuration for later use, click Save. You are prompted to provide a name, and then the configuration is added to the Range folder in the Stored Configurations panel. If you want to dismiss the creation dialog box without saving the configuration, click Cancel. If you are creating a combined discovery and modeling configuration, click the Modeling tab to see the default settings and adjust them as desired using the instructions under Modeling to SPECTRUM [page 33]. You can also click the Filtering tab, which lets you predetermine which of the discovered devices is displayed in the Results dialog box and modeled to SPECTRUM when the configuration is executed. For detailed instructions, see Filtering Results [page 54]. When you are satisfied with the settings on all four tabs, use the Save or Save & Start buttons as described above. Discovery by Router Router discovery configurations require both a range of IP addresses (to establish the boundaries of the discovery) and one or more IP addresses for routers that uses as seed routers. The route information table and/or the routing neighbor tables of each seed router is queried to determine the addresses of neighboring routers. If these addresses are within the specified range, they too are queried, and the process is repeated until all known neighbors within the range(s) have been queried. There is also an option which enables the discovery of the devices that reside in subnets local to those routers that have been discovered. Note: Make sure the IP addresses for the seed routers listed are actually within the range specified. Otherwise there may be interface IPs listed in the Results Set that are out of the range specified. To begin, select a discovery by router option (using any of the methods described under Creating a Configuration [page 17]) and a tabbed configuration creation dialog box appears in the right side of the main window with the Router tab in the foreground and the Schedule tab in the background as shown in Figure 4. If you have selected an option to create a combined discovery and modeling configuration, the foreground Page 26

27 page is labeled Discovery instead of Router, and the Filtering and Modeling tabs are also visible. Figure 4: Discovery by Router To create a discovery configuration using the Router method of discovery, follow the steps explained in the following sections. Page 27

28 Step 1: The Custom and Existing Options If you are creating a discovery-only configuration, go directly to Step 2: The IP Boundary List Panel [page 28]. For a combined discovery and modeling configuration, you have the following two options: The Custom option (selected by default) lets you create a new discovery configuration from scratch by performing Step 2: The IP Boundary List Panel [page 28] through Step 9: Completing the Configuration [page 32]. The Existing option lets you select and import a previously created discovery configuration from the adjacent list, then skip to Step 9: Completing the Configuration [page 32]. Note: This option is unavailable if there are no configurations of the desired type available in the Stored Configurations panel (see Accessing a Stored Configuration [page 41]). Step 2: The IP Boundary List Panel In the IP Range Boundary List panel, define one or more ranges of IP addresses to establish the boundaries of the discovery by entering the lowest address in the range in the From field and the highest address in the To field. Then click the Add button to add the pair of addresses to the list. Use the Del (for Delete ) and Mod (for Modify ) buttons to remove or change any entries in the list. Step 3: The IP Addresses Panel In the IP Addresses panel, specify one or more routers for to use as seed routers, whose route and/or neighbor information tables are queried to determine addresses of neighboring routers. If the neighbors are within the boundaries specified in the previous step, they too are queried and the process repeated until all known neighbors within the boundaries have been queried. You can enter addresses for seed routers in one of two ways: Build a list of IP addresses one address at a time by entering addresses in the IP Address box and clicking Add. Add an entire list of IP addresses at once by clicking the Browse button to access the Open dialog box. Select a file containing a list of IP addresses, then click Open to add those addresses to the list for this configuration. The text file should consist of one or more lines, where Page 28

29 each line contains one IP address expressed in the standard IP address format (xxx.xxx.xxx.xxx). Step 4: The Community Strings Panel In the Community Strings panel, specify the SNMP community strings (passwords) for the devices you want discovered. By default, attempts to discover devices at the IP addresses you specify if they have a community string of public. You can enter additional strings one-at-a-time by typing in the text entry box and clicking Add. Use the Del (for Delete ) and Mod (for Modify ) buttons to remove or change any strings in the list. Note: You can delete the public community string, but at least one valid string must be entered. Community strings are used in the order they appear, and depending on the Timeout and Retries settings (Step 6: The Attempt Panel [page 29]), the time spent attempting to discover a device with a particular string can mount up quickly, especially in large subnets. Therefore it is advisable to keep your most commonly used community string at the top of the list. Step 5: The SNMP Ports Panel If you are autodiscovering a managed node environment in which proprietary SNMP protocols use ports other than the default SNMP port used by (161), add these ports in the SNMP Ports panel. The discovery process uses the ports in the order listed. Note: If you wish to rediscover and model previously modeled devices that use SNMP ports other than the default 161, you must use a combined discovery and modeling operation. If you run the discovery, exit and restart, and then model the results set, SpectroSERVER is not able to contact these devices because SNMP port IDs do not persist in the database. Step 6: The Attempt Panel In the Attempt panel, adjust the Timeout and Retries settings. Timeout specifies the number of seconds spends per attempt at contacting an address. The Retries setting specifies the number of additional attempts makes if the first one times out before contact is established. Page 29

30 Step 7: The Options Panel The default settings in the Options panel are recommended for most networks; however, you can adjust them as follows: Clear the Use Route Tables check box for discovery of networks of all server hardware using only the CDP (Cisco Discovery Protocol) routing table. The Use CDP Tables setting cannot be deselected. For discovery of networks with routing tables of more than 1,000 entries, select a Throttle value to stagger the processing workload by pausing for one second after reading every 50 entries (High), 100 entries (Medium), or 250 entries (Low). Step 8: The Subnet Discovery Panel The Subnet Discovery panel allows you to specify The Subnet Discovery Level [page 30] and The Maximum Subnet Size [page 32]. The Subnet Discovery Level You can select one of three levels of subnet discovery: Do not discover subnets, Discover bounded subnets, and Discover all routed subnets. If you choose Do not discover subnets, the router discovery behaves in its traditional manner (i.e. only routing devices are discovered). This is the default. If you choose Discover bounded subnets, then only those subnets that also fit within the range specified in the router discovery are discovered. The devices within these subnets are discovered by performing a range discovery on a range that corresponds to the range specified. Discover all routed subnets instructs to perform a range discovery on all subnets that are local to the routers discovered. Example Assume you have two routers, Router A and Router B (Figure 5). Router A has the following two interfaces: inta1 has the IP address and a mask of inta2 has the IP address and a mask of Page 30

31 Router B has the following interface: intb1 has the IP address and a mask of Two other devices exist within this network. Switch X sits between Router A (interface inta1) and Router B (interface intb1) and has an IP address of Host station Z sits off of Router A on interface inta2 and has an IP address of This is shown in Figure 5. Figure 5: Network Example Router A Router B inta inta intb Host Station Z Switch X A router discovery has been configured with the following parameters: Seed Router: IP Range Boundary: If a router discovery is performed with a Subnet Discovery Level of Do not discover subnets, the only devices that would be found are Router A and Router B. This is because these devices are routing devices and fit between the IP address range specified. If a router discovery is performed with a Subnet Discovery Level of Discover bounded subnets, then Router A, Switch X, and Router B would be found. Routers A and B would be found as a result of router discovery. Since a Limited Subnet Discovery was specified, performs a range discovery on /24 because this fits within the range specified. Thus Switch X is discovered. does not Page 31

32 perform a range discovery on /24 because it does not fit the specified boundary range. Thus Host Station Z is not discovered. If a router discovery was performed with a Subnet Discovery Level of Discover all routed subnets, then Host Station Z, Router A, Switch X, and Router B would all be discovered. This is because a range discovery would be performed on all the subnets of both Router A and Router B. The Maximum Subnet Size The Subnet Discovery panel s Max Subnet Size option (unavailable if Do not discover subnets is selected) allows you to specify the largest subnet size that can be discovered. You can choose a value from a list of valid sizes, each expressed as the maximum number of hosts for a given subnet mask. The default Max Subnet Size is 1024 hosts. For example, with a Max Subnet Size setting of 4096 (equivalent to a subnet mask of ), will not scan subnets off of router interfaces that have more hosts available (larger masks). If you specify 0 as the Max Subnet Size, does not scan the subnets. Instead, the Cisco Discovery Protocol is used to discover all Cisco Layer 2 switches. Step 9: Completing the Configuration The rest of the procedure varies depending on whether the configuration you are creating is for discovery only or for discovery and modeling. For a discovery-only configuration, at this point you can do any of the following: To set a time for execution of the configuration, click the Schedule tab (see Scheduling a Stored Configuration for Execution [page 42] for instructions). To execute the configuration immediately, click the Save & Start button. After you provide a name for the configuration, it is added to the Router folder in the Stored Configurations panel, a corresponding entry is added to the Results list, and a Results dialog box replaces the configuration creation dialog box. To save the configuration for later use, click Save. You are prompted to provide a name, and then the configuration is added to the Router folder in the Stored Configurations panel. To dismiss the creation dialog box without saving the configuration, click Cancel. Page 32

33 If you are creating a combined discovery and modeling configuration, click the Modeling tab to see the default settings and adjust them as desired using the instructions under Modeling to SPECTRUM [page 33]. You can also click the Filtering tab, which lets you predetermine which of the discovered devices are displayed in the Results dialog box and modeled to SPECTRUM when the configuration is executed. For detailed instructions, see Filtering Results [page 54]. When you are satisfied with the settings on all four tabs, use the Save or Save & Start buttons as described above. Modeling to SPECTRUM Once you have selected one of the commands for creating a new modeling configuration (using any of the methods described under Creating a Configuration [page 17]), a configuration creation dialog box appears in the right side of the main window, as shown in Figure 6. If you are creating a combined discovery and modeling configuration, a tabbed dialog box appears with the foreground page labeled Discovery and the Filtering and Modeling tabs in the background. Note: Previously modeled connections between devices may be locked. The process does not delete such connections, as they may be of value to the network administrator. See the How to Manage Your Network with SPECTRUM Guide (1909) for more information on locked connections. Page 33

34 Figure 6: The Modeling Tab Note: It is recommended that you perform an online database backup via the SPECTRUM Control Panel both before and after executing a modeling configuration. This is especially important to keep both primary and secondary SpectroSERVERs synchronized in a fault tolerant environment. To create a modeling configuration, follow the steps explained in the following sections. Page 34

35 Note: The parameter values that you select override the default parameter values set in the Model Information view available from the Landscape Configuration view of the VNM model. See the Distributed SpectroSERVER (2770) guide for further information about the Model Information view. Step 1: The Custom and Existing Options If you are creating a modeling-only configuration, go directly to Step 2: The Root Container Panel [page 35]. For a combined discovery and modeling configuration, click on the Modeling tab and note the following two options: The Custom option (selected by default) lets you create a new modeling configuration from scratch by performing Step 2: The Root Container Panel [page 35] through Step 7: Completing the Configuration [page 40]. The Existing option lets you select and import a previously created modeling configuration from the adjacent list, then skip to Step 5. Note: This option is unavailable if there are no modeling configurations available in the Stored Configurations panel (see Accessing a Stored Configuration [page 41]). Step 2: The Root Container Panel The Root Container panel includes the Select Container button, which allows you to select a container model to be used as the Root Container. The Root Container is the container where the network topology models will be modeled and displayed. See the Placement option in Step 4: The Modeling Options Panel [page 37] for information on how the network models are displayed in the Root Container. When you click on the Select Container button, SPECTRUM displays a list of available container models on the selected server as shown in Figure 7. The container models are displayed hierarchically corresponding to how they are modeled in SpectroGRAPH. The Refresh button allows you to update this view based on the latest container models available in SpectroGRAPH. Page 35

36 Figure 7: Select a Root Container Step 3: The Modeling Layout Panel In the Modeling Layout panel, you can choose how the resulting network model is placed: The Arrangement option allows you to choose whether the models are placed in a Grid, Radial, or Tree arrangement in the SpectroGRAPH. The default value is Grid. With this selection, the existing models are not replaced. The new device and container models are placed in grid form from the top left to the right and down. If the Radial or Tree option is selected, all models, including any existing models, are replaced in any container where a new model is placed. Note that models are only autoplaced in the chosen arrangement if new models are created when this configuration is executed. If you are rediscovering part of your network and did not select one of these options originally, selecting them for a subsequent modeling session does not have any effect unless new devices have been found and modeled in the interim. Page 36

37 You can, however, use SpectroGRAPH s Edit > Auto Place option at any time. The Placement option allows you to choose between a Hierarchical or Flat placement. If you choose Hierarchical, all layer 3 devices, LAN Containers, and Wide Area Links are placed in the Root Container. Layer 1 and layer 2 devices are placed in the proper LAN container under the Root Container. If an appropriate LAN container is not found for a layer 1 or layer 2 device, they are placed in the Root Container. If you choose Flat, all device models, including layer 1 and layer 2 devices, are placed in the Root Container. Step 4: The Modeling Options Panel The Modeling Options panel allows you to configure the following options, which play a role in how your network model is created: Create Wide Area Link Models: When this option is checked, a WA_Link model is created between the wide area linked interfaces of two routers. This occurs during layer 3 mapping. If this option is not selected, the two linked interfaces are directly connected without the WA_Link model. The How to Manage Your Network with SPECTRUM Guide (1909) defines Wide Area Link models and explains how they are used. Create LANs (IP Subnets): A LAN container model is used to represent an IP subnet. It will contain all the layer 1 and layer 2 devices within that IP subnet. If this option is checked, a LAN container model is created during the layer 3 mapping process for any router interface that routes to a local LAN. Remove Empty LANs: If this option is checked, empty LAN containers created by the Create LANs (IP Subnets) option are destroyed. Create Pingables: If this option is checked, models are created for Pingables. Create (Fanout): If the Create (Fanout) option is checked and if SPECTRUM cannot make an accurate connection among 3 or more interfaces, a Fanout model with name 802.3_Segment is created and these interfaces are connected to the Fanout model. If the Create (Fanout) option is not checked, a Fanout model is not created for the interfaces that have unclear connection information, and therefore these interfaces are not mapped. However, if there is a data Page 37

38 relay device s interface among these interfaces, and all other interfaces are for end node devices, a Fanout model with name Rpt_Segment is created. As noted above, if the Create (Fanout) option is selected and SPECTRUM is unable to resolve connections among three or more interfaces, a Fanout model is created to represent the ambiguous connections among these interfaces. If the Traffic Resolution Protocol option (see Step 5: The Protocol Options Panel [page 38]) is checked, SPECTRUM uses network traffic data (ifinoctet and ifoutoctet statistics) to determine connections between interfaces, and in many cases eliminate the need for a Fanout model. Create Physical Addresses: If this option is checked, models are created that represent devices with a MAC address that is known to one or more switches, but that is not modeled with an SNMP or pingable model. Step 5: The Protocol Options Panel The Protocol options panel allows you to configure options for mapping connectivity between models. It is recommended that you select all layer 2 protocol options, including Source Address Tables, Proprietary Discovery Tables, and Spanning Tree tables for layer 2 mapping. The advanced mapping algorithm used with these options automatically chooses which protocols should be used to obtain the most accurate mapping result. IP Address Tables: If this option is selected, layer 3 mapping is disabled and only layer 2 connections are mapped. In addition, the IP Route Tables Protocol option and the Create Wide Area Link Models, Create LANs (IP Subnets), and Remove Empty LANs Modeling options are disabled (see Step 4: The Modeling Options Panel [page 37]). IP Route Tables: The Read IP Route Tables option is deselected by default, since these tables can be very large and very time-consuming for to read. If you do not select this option, uses the IP Address Table to map routers, but is not able to map unnumbered IP interfaces ( ). If you want to have these interfaces mapped, you can either select the Read IP Route Tables Protocol option, or, after the configuration has been executed, use the Reconfigure Model option or the Discover LANs option, either of which are accessible through the router s Configuration view. The Discover LANs option always uses the IP Address Table, but allows you to specify that the IP Route Table be used as well. The same choice is available when you use the Model by IP option from the Edit menu in any Topology view. For more information on modeling Page 38

39 devices manually, see How To Manage Your Network with SPECTRUM (1909). Source Address Tables: If this option is selected, SPECTRUM uses the device s Source Address table when discovering connectivity information about this device. Proprietary Discovery Tables: If this option is selected, SPECTRUM uses the device s Proprietary Discovery tables when discovering connectivity information about this device. Currently this option enables the Cisco Discovery Protocol, the Cabletron Switch Discovery Protocol, and the Extreme Discovery Protocol. When a device supporting one of these is modeled manually by IP address and the Discover Connections feature is used, the protocol is used automatically. However, when you are autodiscovering a network with devices that support these protocols, you should select this option in order to ensure correct modeling of the connections between these devices. Spanning Tree: If this option is selected, SPECTRUM uses the device s Spanning Tree Address table when discovering connectivity information about this device. Traffic Resolution: If this option is selected, SPECTRUM uses network traffic data (ifinoctet and ifoutoctet statistics) to determine connections between interfaces. In many cases, this eliminates the need for a Fanout model. ATM Protocols: See the ATM Circuit Manager User s Guide (3578) for more information on ATM Discovery. If the ATM Discovery box is checked, the process runs whether or not any new models have been discovered during the process. Step 6: Activation Time Adjust the Activation Time as desired. This value determines the number of minutes waits for new models to activate before placing them and attempting to obtain connectivity information. The timer is reset to the specified value each time a new model activates within the allotted time. When the time expires without any new models activating, connectivity is established insofar as possible, regardless of whether all discovered models have activated. The minimum possible activation time is the default value of 5 minutes; the maximum is 15 minutes. Page 39

40 WARNING! Even though you can halt discovery or modeling sessions via the STOP button that displays at the lower right corner of the Results view while the session is in progress, you should NOT stop a modeling session during the model activation phase, as this can cause incomplete or inconsistent modeling of discovered devices and their connectivity. The modeling activation phase begins when the message Model creation finished... is displayed in the Modeling Status Information panel under the Results view s Modeling tab. When this phase is completed, either the All models are active or Finished processing inactive models message is displayed. Step 7: Completing the Configuration If you are creating a modeling-only configuration, click the Save button at the bottom of the page. This displays a message box asking you to enter a name for the configuration, which is then added to the Model Configurations/SPECTRUM folder in the Stored Configurations panel. If you are creating a combined discovery and modeling configuration, and the settings under all four tabs are to your satisfaction, you can save the configuration, as described above, or click Save & Start to execute the configuration immediately. In addition to adding the configuration to the appropriate Stored Configurations file, Save & Start adds an entry to the Results list and replaces the configuration creation dialog box with the Results view. Page 40

41 Stored Configurations This section discusses accessing and scheduling stored configurations. In This Section Accessing a Stored Configuration [page 41] Scheduling a Stored Configuration for Execution [page 42] Running a Stored Configuration From the Command Line [page 47] Accessing a Stored Configuration Whenever you create and save an configuration, a corresponding entry is added to the appropriate folder in the main window s Stored Configurations panel, shown in Figure 8. Figure 8: Stored Configurations Panel Configurations are displayed in a standard hierarchical arrangement with folders for the three basic configuration types. Click on folders to expand or collapse them. Single-click individual configurations to select them, double- Page 41

42 click to open them, or right-click to display a shortcut menu with the following commands: Open - displays the selected configuration s tabbed dialog box in the work area to the right of the Stored Configurations panel, allowing you to modify discovery, modeling, filtering, or scheduling settings as applicable. Delete - permanently removes the selected configuration from the system after prompting you for confirmation. Rename - displays a dialog box that lets you change the selected configuration s name. Duplicate - creates a copy of the selected configuration (named Copy of <configuration name> ), which you can then open and use as a starting point for creating a new configuration. Start - executes the selected configuration or adds it to the pending queue if another configuration is in progress. Note that this option is unavailable for modeling configurations, which can only be executed in conjunction with discovery configurations. Scheduling a Stored Configuration for Execution You can schedule single or periodic executions of discovery, modeling, or discovery and modeling configurations at the time you create them, or at a later time. In either case, use the configuration creation dialog box s Schedule tab, as shown in Figure 9. Page 42

43 Figure 9: The Schedule Tab To schedule a configuration for execution, follow these steps: Step 1: Enable the Scheduler Click the Scheduled option to activate the page, the rest of which is unavailable when the Not Scheduled option is selected. Step 2: Select the Date and Time In the Scheduling Info panel, click the Schedule configuration on button. This displays the Select Date & Time dialog box (Figure 10). Page 43

44 Figure 10: Select Date & Time dialog box In the Select Date & Time dialog box, adjust the following settings as necessary: a. Select a month from the list in the upper left corner. b. Select a year in the upper right corner. c. Select a day of the month by clicking a square in the calendar. d. Select a time of day in the digital clock display at the bottom of the dialog box. e. Click OK to dismiss the dialog box and transfer the selected date and time to the Schedule configuration on button. f. The scheduled date and time now appears on the Schedule configuration on button. Step 3: Select How Often the Configuration Runs Using the Run list, specify whether you want the configuration to run once or continuously at regular intervals. The default is to run the configuration once. If you select the continuous option, use the text box and the Hour(s)/ Day(s)/Week(s) menu to schedule how often the configuration is run. Page 44

45 For example, a configuration of 2 Day(s) runs the configuration at the selected time once every two days. Note: The first time a continuous discovery is run, a global result set is produced. Each subsequent execution of the configuration generates a result set that compares the latest results to the global result set. See Continuous Discovery Result Sets [page 60] for more information. WARNING! If you are scheduling continuous discoveries in hourly intervals, keep in mind that large discoveries could take several hours to complete. Make sure that the time interval between two discoveries is large enough for the initial discovery to finish before the next scheduled discovery is begun. Step 4: Review the Continuous Modeling Options Panel If you have scheduled the configuration to run at continuous intervals in Step 3: Select How Often the Configuration Runs [page 44], review the options in the Continuous Modeling Options panel. The Place new models in the New_Devices container option places all device models created when the scheduled configuration is executed in the New Devices container model located in the Universe view. This option is enabled by default. When one or more new device models are added to the New Devices container, SPECTRUM asserts a yellow alarm on the container model. This alerts you that new devices have been discovered and modeled. Figure 11: New Devices Container Model SPECTRUM automatically creates the New_Devices container the first time it is needed. If the container is empty, it is hidden by default. To allow the Page 45

46 container to be displayed even if it is empty, change the container model s ismoveable attribute to False. The Place new models in the New_Devices container option modifies the options chosen in the configuration s Modeling tab (see Modeling to SPECTRUM [page 33]). The selected root container is not used. The New_Devices container is used instead of the specified root container and all Protocol options (see Step 5: The Protocol Options Panel [page 38]) are cleared. The Put new models into maintenance mode option puts all new device models created when the scheduled configuration is executed in maintenance mode. For more information on maintenance mode, see How To Manage Your Network with SPECTRUM (1909). Step 5: Configure the Automatic Results Panel You can have the result set of the configuration exported to a text file using the Automatic Results Export panel. This mechanism is similar to the Export option available in the Result Sets menu (see Exporting Results [page 56]). To enable Automatic Export, check the Enable Automatic Export option. The Configure button allows you to specify the data that should be exported. See Exporting Results [page 56] for instructions. If you are exporting the results of a single discovery, exports the full result set. If you are exporting the results of a continuous discovery, you can use the setting to choose whether should Export full results or Export diffed results. If you choose to Export diffed results, only the changes since the last discovery are exported. These changes include any new device that has been discovered, all existing device firmware information, any changes to IP or MAC addresses, and any devices discovered previously that have stopped responding. You can provide an optional File name prefix, which is prepended to the date of the discovery to create the file name. If no File name prefix is specified, uses the configuration name with the discovery date appended. The Directory box allows you to specify a target directory where the export files are saved. <$SPECROOT>/AutoDiscover is the default. Use the Browse button to choose a different directory. Page 46

47 Step 6: Save the Schedule Options Click Save & Schedule to close the configuration and schedule it for execution at the time(s) you have specified. Once scheduled, the configuration is added to the Scheduled Jobs dialog box (Figure 12), which can be accessed either from the File menu or the toolbar. You can remove any job from the schedule by selecting it and clicking Delete. You can also override the schedule by re-opening the configuration s Schedule tab and selecting the Not Scheduled option. Clicking Save on the Schedule tab closes the configuration and saves the scheduling information without actually scheduling the job. Figure 12: Scheduled Jobs Dialog Box Running a Stored Configuration From the Command Line Once you have created and saved a configuration, you can run that configuration from the command line. When you run the configuration from the command line, the application must be closed, other SPECTRUM applications can be open or closed, and the SpectroSERVER must be running. You can also use this command as a Windows Scheduled Task or in a Solaris CRON job to run a stored configuration while you are logged off of the server (with the SpectroSERVER running). Procedure 1. Create a configuration as described in Creating a Configuration [page 17]. Page 47

48 2. Once you have completed the discovery and modeling portion of the configuration, click on the Schedule tab. The dialog box shown in Figure 9: The Schedule Tab appears. 3. Choose the Background Discovery option at the top of this dialog box. 4. Save the configuration and note the configuration name you have chosen. 5. Close. 6. From the <$SPECROOT>/AutoDiscover directory, type the following command: AutoDiscover bg <ConfigName> Where <ConfigName> is the name of the configuration you created in steps 1-4. Page 48

49 Result Sets This section discusses result sets and how they can be used. In This Section What Are Result Sets? Accessing and Using Result Sets [page 53] Sorting Results [page 54] Filtering Results [page 54] Exporting Results [page 56] Comparing Results [page 58] Continuous Discovery Result Sets [page 60] What Are Result Sets? Each time you start a discovery session (by executing a particular configuration), a result set is automatically created to store: the configuration that was used status and error messages generated during the session a list of all discovered devices called the discovered data set The discovered data set is the exportable part of the result set and the main input for subsequent modeling in SPECTRUM. It catalogs all the devices that were discovered and provides location, contact, port, and other information (see Device Information [page 51]) as applicable. Creation of a new result set has two effects on the main window, as shown in Figure 13. First, a new entry is added to the scrollable Results list at the lower left of the window. Each entry in this list uniquely identifies a particular result set using the name of the configuration that was used and the date and time the session was started. The entry also shows the current status of the session. Individual result sets can be selected from this list for opening, deleting, renaming, exporting, or modeling to SPECTRUM. For more information, see Accessing and Using Result Sets [page 53]. Page 49

50 Second, a Results view with tabs displays in the large panel at the right of the window. Figure 13: Result Sets in s Main Window Result sets list Results panel with tabs for accessing associated discovery and modeling configurations As devices are discovered, they are listed by IP address in the Results tab. Status or error messages generated during the discovery appear at the bottom of this tab. The Model Devices button lets you execute an associated modeling configuration if one exists, or displays the modeling configuration creation dialog box so that you can create one. (Note that this button does not display for read-only users.) The Discovery tab accesses the associated discovery configuration. For combined discovery and modeling configurations, the Results view also includes a Modeling tab, which accesses the associated modeling configuration. Page 50

51 Device Information When a discovery configuration is executed, the Results panel displays a table listing each of the discovered devices. The table provides the following information: IP Address, Name, Vendor, Description, Location, and SysOID. You can rearrange the column order by grabbing and moving column headers with your mouse. To see additional results information for a particular device, double-click in any cell in that device s row. This displays the Device Information dialog box (Figure 14). Figure 14: Device Information Dialog Box The Device Information dialog box lists agent information in the top panel and presents port information in table format in the bottom panel. Individual data elements are described below: Agent Information Name - The name of the device. Password - For SNMP devices, the community name assigned to control access. Description - Narrative description of the device. May include vendor and model name or other designation. Page 51

52 Contact - Authorized contact person for the device (e.g., System Administrator). Location - Physical location of the device (e.g., Quality Assurance Lab). # Ports - The number of ports on the device. Protocol - The networking protocol that was used to discover the device. OID - The Object Identifier for the device. Services - A number whose binary bits represent the services supported by the device. Ports Information IF# - Sequential number identifying the interface on the device. Type & Description - The type of interface and the interface s type description. MAC Address - The Media Access Control or physical address of the port. IP Address - The primary IP address of the interface. Netmask - The netmask associated with the primary IP address of the interface. Note: SPECTRUM can model different devices that share IPs (duplicate IPs), provided that each device has at least one IP that is unique to that device. This functionality accommodates networking technologies, such as load balancing, that create identical IP addresses across a range of devices. Devices that share some interface IP addresses can now be modeled manually or by using. Devices that share all of their interface IP addresses in common cannot be modeled manually or by using in SPECTRUM. Page 52

53 Accessing and Using Result Sets Whenever an configuration is executed, a corresponding entry is added to the Results list at the lower left corner of the main window. Each entry shows the name of the configuration, the date and time it was executed, and its current status. Once an entry has a status of Discovered or Modeled, you can select it by single-clicking, open it by double-clicking, or right-click it to display a shortcut menu with the following commands. Open - displays the selected result set in a tabbed view to the right of the Results list. The Results tab includes buttons that access dialog boxes that let you filter the results (see Filtering Results [page 54]), export them to a file (see Exporting Results [page 56]), or model them to SPECTRUM (see Modeling to SPECTRUM [page 33]). Depending on the type of configuration that was executed, there are also tabs allowing you to view the associated configuration, filtering, or scheduling information. Delete - permanently removes the selected result set from the system after prompting you for confirmation. Rename - displays a dialog box that lets you change the selected configuration s name. Export - displays the Export Data Selection dialog box that lets you export the selected result set to a file in the format and location of your choice (see Exporting Results [page 56]). This dialog box is also accessible from the Export button in the Results tab. Model to SPECTRUM - displays the Modeling Configuration dialog box that lets you create or modify and then execute the modeling configuration for the selected result set. This dialog box is also accessible from the Model Devices button in the Results tab. For detailed instructions, see Modeling to SPECTRUM [page 33]. Page 53

54 Sorting Results When a result set is created, the Results panel lists devices under the Results tab in the order that they were discovered. You can sort the list in ascending or descending order by the attributes identified by the column headings. Clicking once on a column heading displays an up-arrow next to the column name and sorts the list in ascending order for that attribute. Clicking the column heading again displays a down arrow next to the column name and sorts the list in descending order. Sorts are not saved when you close the view. Filtering Results In addition to the boundaries you set for any discovery configuration (such as specifying IP address ranges, community strings, whether or not to discover pingables, etc.) also provides a filtering mechanism that lets you set further limitations on which of the discovered devices are displayed in the result set created when the configuration is executed. Any filters applied to a configuration or a result set also apply to any subsequent exporting or modeling to SPECTRUM. For discovery-only configurations, filtering is applied after the configuration has been executed. You access the Filtering dialog box (Figure 15) by clicking the Filter button in the Results tab. Figure 15: Filtering Dialog Box For combined discovery and modeling configurations, you can set up filtering anytime before executing the configuration, either at the time you Page 54

55 create it, or by reopening the saved configuration and adding/modifying filtering information. In this case, you use the configuration creation dialog box s Filtering tab, which looks and functions just like the Filtering dialog box in Figure 15 [page 54]. To filter existing discovery results or set up filtering for subsequent execution of a combined discovery and modeling configuration, follow these steps: 1. Establish filtering criteria by creating expressions one-at-a-time, as follows: a. Make a selection from the Fields list e.g., vendor. b. Make a selection from the Condition list e.g., equals. c. Make an entry in the Value field e.g., cisco. d. Click Add to add the expression to the list in the middle of the dialog box. If the expression vendor equals cisco is the only filter applied, then the result set for this configuration will include only the Cisco devices that are discovered. 2. If you are using more than one criteria expression, select one of the following options: - Match all of the following (AND) - to display/model only those devices for which EACH of the listed expressions is true. - Match any of the following (OR) - to display/model only those devices for which ANY of the listed expressions are true. Clicking Mod allows you to modify any expression already in the list. Remove a selected expression by clicking the Delete button. 3. Click Show Pingables if you want pingable devices included in the filtered results. 4. If you are setting up filtering ahead of time for a combined discovery and modeling configuration, you can click OK to save your filtering criteria and dismiss the dialog box, or Cancel to dismiss the dialog box without saving. If you are filtering an existing result set, you can also click Apply to apply your filtering criteria temporarily while leaving the dialog box open. Page 55

56 Exporting Results The Export Data Selection dialog box (Figure 16) lets you export selected device information from a discovery result set to a file in the format and location of your choice. You can access this dialog box via the Export option in the shortcut menu for a result set selected from the Results list, or via the Export button in the Results tab. Figure 16: Export Data Selection Dialog Box To export device information, follow these steps: 1. Select a format from the Choose Export Format menu at the top of the dialog box. 2. All device information attributes ( exportable items ) are selected by default. Clear the adjacent check box for any option you do not want to include in the export file. 3. Click OK to display the Save dialog box (Figure 17). Page 56

57 Figure 17: The Save Dialog Box 4. Navigate to the directory where you want to store the exported file, type in a file name, and click Save. Page 57

58 Comparing Results lets you compare any two result sets generated by discovery configurations and export the differences to a text or html file. It is recommended that this feature not be used while discovery or modeling sessions are in progress. To perform a comparison, follow these steps: 1. From the main window s Tools menu, choose Device Differencing. 2. In the Differencing Tool dialog box (Figure 18), select one entry from each of the two lists labeled Select First ResultSet and Select Second ResultSet. 3. Click the Compare button. As shown in Figure 18, devices that are in the first result set but not the second are listed by IP address and MAC address in the leftmost two columns against a green background. Devices that are in the second result set but not the first are listed in the rightmost two columns against a red background. If devices appear in both result sets but associated information has changed for one of them (e.g., firmware may have been upgraded between discoveries), the background is yellow. Figure 18: Differencing Tool Dialog Box Page 58

59 4. If you wish to create a file detailing the differences, click the Export button at the bottom of the dialog box. a. In the Export Format dialog box, select a format (HTML or Ascii) from the list, then click OK. b. In the Save dialog box (the same one used for Exporting Results [page 56]), select the directory you wish to save the file in, then enter a file name and click Save. As shown in Figure 19, the Differencing Report file lists the devices unique to each result set, providing descriptive information in addition to the IP and MAC addresses. 5. Click Done. Figure 19: Differencing Report File Page 59

60 Continuous Discovery Result Sets Result sets that are based on discoveries that are scheduled to run continuously are different from the result sets from discoveries that are run once. Continuous discovery result sets show you an up-to-date composite of the history of the continuous discovery. There are two types of result sets linked to a continuous discovery: A global result set showing the cumulative results of all discoveries that have been run so far. Individual result sets showing the results of each discovery operation. Accessing a Global Result Set The first time a continuous discovery is executed, a corresponding entry is added to the Results list at the lower left corner of the main window. This entry is the global result set that tracks the cumulative results of the continuous discovery. You can select it by single-clicking on it and open it by double-clicking on it. When you open a global result set, displays a window like the one in Figure 20. The cumulative results of continuous discovery are shown in the table at the top of the window. Each individual result set generated by the continuous discovery is listed in the Result Set History section at the bottom of the window. Page 60

61 Figure 20: Initial Global Result Set Global Result Set Standard Result Set Accessing an Individual Result Set You can open an individual result set by double-clicking on it. When you open an individual result set, by default you only see the changes that occurred during that discovery (Figure 21). To see the full results of the discovery session, click the Show full results button. Page 61

62 Figure 21: Viewing an Individual Result Set Analyzing the Result Sets After each subsequent instance of a continuous discovery is run, an individual result set is created and its contents are compared to the current global result set. Any newly discovered devices are added to the global result set. Devices that have not changed since the previous discovery are removed from the standard result set, but are maintained in the global result set. Devices that have changed remain in both the global result set and the standard result set. Devices that are no longer responding also remain in both result sets. An entry for each standard result set is placed in the Result Set History section. Page 62