This documentation (the "Documentation") and related computer software program (the "Software") (hereinafter collectively referred to as the "Product") is for the end user's informational purposes only and is subject to change or withdrawal by CA at any time.
This Product may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Product is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties.
Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the Documentation for their own internal use, and may make one copy of the Software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the Software are permitted to have access to such copies.
The right to print copies of the Documentation and to make a copy of the Software is limited to the period during which the license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user's responsibility to certify in writing to CA that all copies and partial copies of the Product have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS PRODUCT "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS PRODUCT, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.
The use of this Product and any product referenced in the Documentation is governed by the end user's applicable license agreement.
The manufacturer of this Product is CA.
This Product is provided with "Restricted Rights." Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7013(c)(1)(ii), as applicable, or their successors.
Preface . . . 11
Chapter 1: Welcome to Modeling Your IT Infrastructure . . . 13
Network Modeling in OneClick . . . 14
SPECTRUM OneClick Terms . . . 14
Next Steps . . . 15
Chapter 2: Getting Started . . . 17
SPECTRUM OneClick Topologies . . . 17
Universe Topology . . . 18
Top View of Universe Topology . . . 19
Drill Down View of Universe Topology . . . 19
Component Detail View . . . 20
Define Models in the Universe Topology . . . 20
Global Collections Topology . . . 21
How to Use Global Collections . . . 21
Populate Global Collections . . . 22
View or Modify Modeled Devices . . . 22
World Topology . . . 23
TopOrg Topology . . . 24
Icons in Topology Views . . . 25
Icon Themes . . . 26
Icon Shape, Symbol, and Theme . . . 26
Icon Color and Condition . . . 30
Provision Access to Modeled Elements . . . 31
Methods for Modeling Network Entities . . . 32
Recommended Modeling Tips . . . 32
How to Get Started . . . 34
Chapter 3: Discover and Model Your Network . . . 37
What Is Discovery? . . . 38
Ways to Use Discovery . . . 38
Discovery Terms . . . 38
Discovery Overview . . . 39
Discovery Session . . . 39
Discovery Status . . . 39
Discovery Results . . . 39
Model Discovery Results . . . 39
Modeling Results . . . 40
Why Use Different Configurations? . . . 40
Launch Discovery . . . 40
Launching Discovery without Context . . . 40
Launching Discovery with Context . . . 40
Use Existing Discovery Configurations . . . 40
Discovery Console Layout . . . 41
Discovery Navigation Panel . . . 42
Create or Open Configurations . . . 43
Create Folders . . . 43 Contents Panel . . . 43 Configuration Tab . . . 43 Discovery Tab . . . 47 Modeling Tab . . . 49 History Tab . . . 51
Discovery Connection Status . . . 53
Define and Activate Configurations . . . 54
Define a Configuration . . . 54
Define Modeling Options . . . 57
Activate a Discovery Session . . . 61
Activate a Modeling Session . . . 62
View, Filter, and Export Results Lists . . . 63
Exporting a Results List . . . 63
Filter Results Using Advanced Filter . . . 63
After Discovering and Modeling . . . 65
VNM AutoDiscovery Control Settings . . . 65
Access VNM AutoDiscovery Control . . . 65
Loopback Interfaces and Discovery . . . 66
Chapter 4: Manual Modeling . . . 67
When to Model Manually in OneClick . . . 67
SPECTRUM OneClick Modeling Terminology . . . 68
Manual Modeling in the Universe Topology . . . 68
Create or Use an Existing Container . . . 68
Add Devices to Container . . . 68
Create Connections . . . 69
Enhance Topology View . . . 69
Add Containers to Universe Topology Views . . . 69
Add Existing Devices to Container . . . 70
Add Network Devices to Universe Topology Views . . . 71
Cut Modeled Element from Universe Topology View . . . 75
Export a Universe Topology View . . . 76
Create Connections (Pipes) Between Modeled Devices . . . 76
Removing Connections from a Universe Topology View . . . 77
Create an Unresolved Connection Between Modeled Elements . . . 78
Create a Resolved Connection (both device ports known) . . . 78
Create a Partially-resolved Connection (one device port known) . . . 79
Lock and Unlock Resolved Connections . . . 79
Enable or Disable a Live Link (applies to full or partial resolved connections) . . . 80
Model Manually in Global Collections Topology . . . 80
Dynamic Membership - Use Search Criteria . . . 80
Recommended Process for Defining Collections . . . 81
Global Collections Modeling Tasks . . . 82
Define a New Collection . . . 82
Edit an Existing Collection . . . 87
Create a Global Collection Hierarchy . . . 89
Manually Modeling in the World Topology View . . . 89
Recommended Process for Modeling Locations . . . 90
Manually Modeling the TopOrg Topology . . . 91
Model Services in the TopOrg Topology . . . 92
Chapter 5: Modeled Device and Interface Configurations . . . 95
Device and Interface Threshold Settings . . . 95
Device Threshold Settings . . . 96
Example: % CPU Utilization Default Settings . . . 96
Interface Threshold Settings . . . 98
Update Device Interface and Connection Information . . . 98
Automatically Updating Device Interface and Connection Information . . . 98
Manually Updating Device Interface and Connection Information . . . 100
Access Interface and Connection Update Controls . . . 101
Tools, Reconfiguration Menu . . . 101
Reconfiguration Subview and Advanced Subview . . . 101
Attribute Editor Change Management Group . . . 102
Redundant Connections between SPECTRUM and Modeled Devices . . . 102
Redundancy Preferred Addresses List . . . 102
Device Primary Address . . . 102
IP Redundancy Subview . . . 102
Redundancy Excluded Addresses List . . . 103
Chapter 6: Edit and Enhance Topology Views . . . 105
Commonly Used Terms . . . 105
Use Edit Mode to Enhance Topology Views . . . 106
Accessing the Edit Mode Feature . . . 107
Edit Mode Tool Bar . . . 109
How to Enhance a Topology View . . . 110
Proportionally Resize Model Icons . . . 110
Add Shapes, Lines, or Text to a View . . . 110
Change Shapes, Lines, and Text Characteristics . . . 111
Enhancing Topology Background . . . 112
Group and Ungroup Items in a View . . . 113
Bringing Items to Front or Sending Items to Back . . . 114
Chapter 7: Device Type Identification . . . 115
Device Type Identification in OneClick . . . 115
Launch Device Type Identification . . . 115
Device Type Identification Table . . . 116
Search DTI Mappings Using Filters . . . 117
Apply DTI Changes to SPECTRUM Model Catalog . . . 117
Manage Device Type Mappings . . . 118
Custom Device Type Mappings . . . 118
Custom Mappings with Modified Device Type Name . . . 118
Custom Mappings with Modified SysObjectID . . . 118
Delete Custom DTI Mappings . . . 119
Map Unregistered Devices . . . 120
Distributed SpectroSERVER Support . . . 121
Servers Unavailable Warning . . . 121
DTI Mapping Conflicts . . . 121
Missing DTI Entries . . . 122
DTI and Fault Tolerant Environments . . . 122
Customization Considerations . . . 123
Prevent Changes to All Device Model Types Using DeviceTypeDiscEnable Attribute . . 123
Preserve Device Type Customizations for Specific Devices . . . 123
Prevent Device Type Name Changes on Model Types . . . 124
Chapter 8: Modify Model Attributes . . . 125
Why Modify Attributes? . . . 125
Access Attributes From the Information Tab . . . 126
VNM Attributes in the Information Tab . . . 127
General Information . . . 127
Online Database Backup . . . 127
SpectroSERVER Control . . . 128
AutoDiscovery Control . . . 129
Trap Based Continuous Discovery . . . 130
Debug Options . . . 131
Fault Isolation . . . 132
Live Pipes . . . 132
Live Pipes and Global Collections in DSS Environments . . . 132
Alarm Management . . . 132
OneClick Attribute Editor . . . 133
Launch Attribute Editor . . . 133
Open Attribute Editor with Device Context . . . 133
Attribute Editor Dialog Box . . . 134
Task Oriented Attribute Groupings . . . 134
Filter Attribute Categories . . . 134
Attribute Edit Panel . . . 134
Attribute Editor Results Dialog . . . 136
User Defined Attributes . . . 137
Attribute Selector Dialog Box . . . 137
Change Attributes in Conjunction with Search . . . 139
Define a Search to Create a User Defined Attribute for Editing . . . 139
Edit Attributes for Specific Devices or for Model Types . . . 140
Example: Edit Interface_Polling_Interval for Cisco Devices Supporting IPsec . . . 140
Example: Edit the DeviceTypeDiscEnable Attribute for Specific Devices . . . 141
Example: Edit DeviceTypeDiscEnable for a Model Type . . . 142
Attribute Groupings . . . 142
Change Management . . . 142
Interface Configuration . . . 143
Stale Interfaces . . . 144
Maintenance Mode Attributes . . . 144
Roll-up Alarm Attributes . . . 144
Model Status and Alarm Conditions . . . 145
Roll-up Condition Thresholds . . . 146
SNMP Communications Attributes . . . 147
Tuning SPECTRUM’s SNMP Communications . . . 147
More Efficient SNMP Communications . . . 147
Increase Reliability . . . 147
Thresholds . . . 148
Device Thresholds . . . 148
Interface Thresholds . . . 148
Chapter 9: MIB and Trap Management . . . 149
SNMP, MIBs, and SPECTRUM . . . 149
How a MIB Is Organized . . . 150
OneClick MIB Tools . . . 151
MIB Browser . . . 151
MIB Tools Database . . . 151
MIB Import . . . 151
Query Device MIBs . . . 152
Export MIB Tools Data . . . 152
Attribute and Trap Mapping in SPECTRUM . . . 152
MIB Tools User Interface . . . 152
Launch MIB Tools . . . 153
Launch MIB Tools In Context . . . 153
Navigation Panel—MIB Management . . . 154
Import Individual MIBs . . . 154
Compile MIB Files . . . 154
MIB Editor . . . 155
Import Multiple MIBs . . . 155
Contents Panel—Browse MIBs . . . 157
Browse Tab . . . 157
Contact Criteria . . . 157
MIB Tree Hierarchy Table . . . 158
Hierarchy Tool Bar . . . 159
Access MIB Objects on Network Devices . . . 159
View MIB Object Values . . . 159
Set MIB Object Values on a Device . . . 160
Device Query and SET Results . . . 161
Export Query Results To Support Troubleshooting . . . 162
Contents Panel—Attribute and Trap Management . . . 162
Map Tab . . . 163
Attribute Support Table . . . 163
Create Attributes . . . 163
Trap Support Table . . . 164
Map Traps—Create Trap Support . . . 165
Custom Trap Support File Details . . . 165
Identify and Resolve Partial Trap Support . . . 166
Multiple SpectroSERVERs . . . 167
Best Practice for Maintaining MIB Tools in a DSS Environment . . . 167
Attribute Support Conflicts . . . 168
Resolve Attribute Support Conflicts . . . 168
Incomplete Trap and Attribute Support . . . 168
Create Consistent Support Across a DSS Environment . . . 168
Trap Disposition Conflicts . . . 169
Multiple OneClick Servers . . . 170 Best Practices to Maintain Synchronization . . . 170
This guide introduces SPECTRUM OneClick modeling concepts and functionality. This document is intended for users responsible for modeling their IT infrastructure within the OneClick
environment. This guide assumes that you are familiar with the SPECTRUM OneClick web-based, client-server architecture and are thoroughly familiar with how to launch the OneClick client using a web browser.
What Is In This Book
This guide contains the following chapters:
• Chapter 1: “Welcome to Modeling Your IT Infrastructure”—introduces OneClick’s prominent modeling features.
• Chapter 2: “Getting Started”—defines OneClick’s network topologies, icons for modeling, model-based security, and methods for defining new models. It also includes references on how to get started.
• Chapter 3: “Discover and Model Your Network”—steps you through the tasks associated with defining and maintaining discovery configurations. It provides concepts and detailed
procedures for defining configurations, activating configurations, modeling, filtering, and exporting discovery results.
• Chapter 4: “Manual Modeling”—describes how to perform manual modeling tasks within each of the OneClick core topology views: Universe, Global Collections, World, and TopOrg.
• Chapter 5: “Modeled Device and Interface Configurations”—describes how to use OneClick features to further configure device and interface parameters so that they are either
automatically or manually update the configuration information for devices modeled on your network.
• Chapter 6: “Edit and Enhance Topology Views”—instructs you how to enhance a topology view using the Edit mode feature. It also discusses how you can edit attributes at the device level using the Attribute Editor feature.
• Chapter 7: “Device Type Identification” on page 115—describes how to use OneClick Device Type Identification to manage device type naming in OneClick.
• Chapter 9: “MIB and Trap Management” on page 149—describes the OneClick MIB Tools utility and how to use to add SPECTRUM attribute and trap support for devices not supported by default in SPECTRUM, as well as how to view MIBs to understand what’s in a device MIB that you can leverage to manage the device.
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:
Thank you for helping us improve our documentation.
Online Documents
SPECTRUM documents are available online at:
http://support.concord.com/support/secure/products/Spectrum_Doc/
Check this site for the latest updates and additions.
Element Convention Used Example
Variables
(The user supplies a value for the variable.)
Courier and Italic in angle brackets (<>)
Type the following:
DISPLAY=<workstation name>:0.0 export display
The directory where you installed SPECTRUM (The user supplies a value for the variable.)
<$SPECROOT> Navigate to:
<$SPECROOT>/app-defaults
Linux, Solaris, and Windows directory paths
Unless otherwise noted, directory paths are common to all operating systems, with the exception that slashes (/) should be used in Linux and Solaris paths, and backslashes (\) should be used in Windows paths.
<$SPECROOT>/app-defaults on
Linux and Solaris is equivalent to
<$SPECROOT>\app-defaults on Windows.
On-screen text Courier The following line displays:
path=”/audit”
User-typed text Courier Type the following path name:
C:\ABC\lib\db Cross-references Underlined and
hypertext-blue
See “Document Feedback” on page 12.
References to SPECTRUM documents (title and number)
Infrastructure
SPECTRUM OneClick product suite is a framework that integrates all network management
features (core and add-on management). Prominent among these network management features are the following core modeling features that OneClick provides:
• Two methods for modeling. You can model your IT infrastructure manually or you can have SPECTRUM OneClick automate the process for you by using its Discovery feature. Specific information about these modeling methods are discussed in Chapter 3, “Discover and Model Your Network,” on page 37 and Chapter 4, “Manual Modeling,” on page 67.
• Multiple topologies for representing network models. You can create models of your IT infrastructure and represent them within four different topologies. For example, you can use the Universe topology to represent an enterprise network view of your infrastructure; you can use the World topology to represent a geographic view of your infrastructure; you can use the TopOrg topology to represent an organizational view of your infrastructure; or, you can use the Global Collections topology to represent an entity-based (free-form) view of network objects, services, or organizations. Detailed information about these topologies and their use are described in Chapter 2, “Getting Started,” on page 17.
• Automated discovery and modeling process. You can use the Discovery feature to automate the process of identifying assets within your IT infrastructure. After identifying network assets, you can use Discovery’s modeling functionality to automate the modeling process. Complete details about using Discovery to help you automate the modeling process are provided in Chapter 3, “Discover and Model Your Network,” on page 37.
• Modify device type identification. If you have devices on your network that are not supported by the extensive default SPECTRUM device type library, you can modify the device type identifier for the devices to better match the device name, model, or other parameter that meets your needs. See Chapter 7, “Device Type Identification,” on page 115.
• Automatic assignment of intuitively designed icons. SPECTRUM OneClick uses a wide range of icons to represent the network entities in your infrastructure. These icons are automatically assigned to each entity as you add them to your models. Details about the different types of icons that OneClick uses to represent entities in your network models are described in Chapter 2, “Getting Started,” on page 17.
• Editing tools for enhancing the read-ability of a topology view. You can enhance the readability of any topology by adding annotations, changing background color, or arranging the modeled icons in a tree or radial display. Details about these editing tools are described in
Chapter 6, “Edit and Enhance Topology Views,” on page 105.
• MIB and Trap Management. OneClick comes with a powerful MIB management tool, MIB Tools, that provides you with functionality to view MIBs, create SPECTRUM attribute and trap support, compile, and import additional MIBs into the database. See Chapter 9, “MIB and Trap Management,” on page 149 for details about using MIB Tools.
Network Modeling in OneClick
Network modeling in SPECTRUM OneClick is the act of graphically representing network entities and their connections. Icons created, placed, and connected within the OneClick topology views represent various aspects of a modeled network.
Using the modeling features offered in the OneClick client you can easily create and maintain accurate software models of your network. These intelligent network models enable SPECTRUM to determine actual points of failure and suppress superfluous alarms.
SPECTRUM OneClick Terms
Table 1-1 and Table 1-2 list commonly-used SPECTRUM OneClick terms that you should be familiar with prior to reading the chapters in this guide.
Table 1-1: SPECTRUM OneClick Terms
Landscape The Landscape is the network domain managed by a single SpectroSERVER. SpectroSERVER The SpectroSERVER is the server process responsible for providing network
management services such as polling, trap management, notification, data collection, fault management, etc.
Also referred to as the Virtual Network Machine (VNM). Distributed SpectroSERVER
(DSS) Environment
A Distributed SpectroSERVER (DSS) environment consists of more than one SpectroSERVER. This environment enables management of a large-scale infrastructure. The SpectroSERVERs in this environment may be located within a single physical location or multiple physical locations.
For additional information about a Distributed SpectroSERVER Environment, see the SPECTRUM Concepts Guide.
Topologies Topologies are iconic views in OneClick of a modeled network.
Manual modeling Manual modeling is the act of manually representing individual devices and their connections within a SPECTRUM OneClick topology view.
Next Steps
This guide describes SPECTRUM OneClick’s modeling concepts and functionality so that you can quickly get started producing topologies that describe your IT infrastructure.
Next
• Learn more about OneClick’s topology views, icon representation of models, model security, methods for defining new models, and tips for modeling in “Getting Started” on page 17.
Later
After you’re familiar with OneClick’s modeling features and concepts presented in Chapter 2, you can continue to learn how to define and enhance models of your IT infrastructure by reading the following chapters:
• “Discover and Model Your Network” on page 37. This chapter discusses ways you can use the Discovery feature to auto discover and model entities in your IT infrastructure.
• “Manual Modeling” on page 67. This chapter walks you through the manual modeling tasks associated with the Universe, Global Collections, TopOrg, and World topologies.
• “Edit and Enhance Topology Views” on page 105. This chapter describes how to enhance topology views using Edit mode and how to reconfigure attribute settings at the device level.
Table 1-2: Commonly Used Modeling Terms Landscape The Landscape is the local or remote SpectroSERVER.
Methods of modeling
Methods of modeling -You can choose to automate the process using Discovery, or you can choose to manually model the individual entities and then enhance the model presentation using the Editing tools. See “Methods for Modeling Network Entities” on page 32 for more information.
Network entity Network entity most often refers to a device, an interface, a container, or a physical connection that makes up your IT infrastructure.
Modeling entity A Modeling entity most often refers to an icon representing an individual modeled device, container, or physical connection.
In This Chapter
This chapter provides important information about SPECTRUM OneClick’s modeling features and concepts. Specifically, it explores the four modeling topologies offered, icon representation of models, model security, and methods for defining new models. Finally, it provides modeling suggestions and tips, and references for getting started. This information is presented in the following sections:
• “SPECTRUM OneClick Topologies” on page 17
• “Icons in Topology Views” on page 25
• “Provision Access to Modeled Elements” on page 31
• “Methods for Modeling Network Entities” on page 32
• “Recommended Modeling Tips” on page 32
• “How to Get Started” on page 34
SPECTRUM OneClick Topologies
In SPECTRUM OneClick there are four core topologies that you can use to model your IT infrastructure:
• Global Collections • Universe
• World • TopOrg
All four of these topologies are available from the OneClick Navigation panel.
Figure 2-1: OneClick Topologies Navigation
To navigate through the model views of any topology, click the view control icons in the tool bar area, or in some cases, you can click an aggregate icon container to view its content. See “Icons in Topology Views” on page 25 for more information on Aggregate icons.
A brief summary of these topologies follows: • “Universe Topology” on page 18
• “Global Collections Topology” on page 21
• “World Topology” on page 23
• “TopOrg Topology” on page 24
Universe Topology
drill-down topology view of OSI Layer 2 devices and their connections, and a component detail view of attributes associated with a modeled entity.
Top View of Universe Topology
The top view in the Universe topology most often includes the SPECTRUM Virtual Network Machine (VNM), network groupings, network segments, and OSI Layer 3 devices and their connections, as shown in Figure 2-2 .
Figure 2-2: Top View of Universe Topology
Drill Down View of Universe Topology
Figure 2-3 shows a drill down view of a LAN container selected from the top view. A drill down view in the Universe topology most often includes all OSI Layer 2 devices and their connections, and off page references to devices modeled in other views.
Figure 2-3: Drill Down View of Universe Topology OSI Layer 3 devices, such as a
router and its connection SPECTRUM Virtual
Network Machine
Icon representing a WAN Segment
such as a switch.
Component Detail View
The component detail view within the Universe topology appears in the Component Detail panel (Figure 2-4 ). This view identifies the attributes associated with a modeled network entity such as its interfaces, alarms and events, and other pertinent device information.
You can view the device attributes and possibly change their settings by clicking the Component Detail panel tabs. For instance, you can:
• View and modify general device settings in the Information tab, such as granting or denying access to a modeled device by providing (or possibly removing) a security string.
• View root cause analysis data in the Root Cause tab.
• View CPU and memory utilization information in the Performance tab. • View device interface information in the Interfaces tab.
• View neighboring routers in the Neighbors tab. • View current alarms in the Alarm tab.
• View historical events in the Events tab.
Figure 2-4: Component Detail View of Universe Topology
Define Models in the Universe Topology
recommend that you reuse modeled elements from this view when creating other views.
Therefore, as a best practice, you should copy model elements from the Universe topology view to create Global Collections, World, or TopOrg views. This modeling approach helps to ensure
accurate fault isolation of your network within the SPECTRUM OneClick environment.
Global Collections Topology
Global Collections help organize entity-based network views that may span one or more landscapes. Global collections enable operators to monitor all aspects of your IT infrastructure from any perspective.
How to Use Global Collections
Administrators can use Global Collections to create and track collections of network entities, organizations, or services that make up your infrastructure. For example, you could create and maintain collections that identify and track:
• Response teams within an organization responsible for maintaining equipment • Devices supporting various services in your organization
• Customers receiving services from your organization The Figure 2-5 illustrates a collection of routers.
Populate Global Collections
This section describes how to create and populate a OneClick Global collection.
To Populate Global Collections Using Search Criteria
The most common method to create and populate a Global Collections view is: 1. Create and name a new collection.
2. Specify search criteria to locate modeled elements (previously modeled within the Universe topology) to populate the new collection.
Figure 2-6: Create Collection Using Search Criteria
To Populate Global Collections Using Add To
You can also populate a new or an existing Global Collections view by right-clicking the modeled elements you want to copy from the Universe topology and selecting Add To - Collections.
See Chapter 4, “Manual Modeling,” on page 67 for more information on using these methods to create and populate a Global Collection view.
View or Modify Modeled Devices
You can view and change modeled device attributes or settings in the Component Detail Panel within the Global Collections topology. Click the tabs in this panel to access general information about a device, its interfaces, alarms, events, and other pertinent information.
Create and name the new collection
Figure 2-7: Component Detail Panel - Global Collections
World Topology
The World topology helps organize geographic area views of your network. In this topology, you can represent device models of network locations from a national or regional level all the way down to a wiring closet.
The following example illustrates a drill down view of an equipment room located at a fictitious North Dallas location.
Figure 2-8: World Topology Drill Down View
In the World topology, you can create several layers of views that represent locations of your networked devices (i.e., Texas regional offices, Dallas office, North Dallas equipment room, etc.). Additionally, you can use the Component Detail panel to view and possibly change the attributes associated with a modeled device in any World topology view. For instance, by clicking the Component Detail tabs (associated with a modeled device) you can view device information, interfaces, alarms, events, and other pertinent device information.
Finally, when populating the World topology views with modeled devices, we highly recommend that you copy and paste modeled elements from Universe topology views. This recommendation stems from the fact that Universe topology views represent the true connectivity views of your infrastructure, thereby, ensuring accurate fault isolation of your network within the SPECTRUM
Tabs for viewing and changing device attributes and settings
The information tab provides general information about the selected modeled device
For further information about creating views within the World topology, see Chapter 4, “Manual Modeling,” on page 67.
TopOrg Topology
The TopOrg topology helps depict organizational views of your network. In this topology, you can group subnets and device models by services, responsibilities, departments, or other
organizational considerations.
The following example shown in Figure 2-9 illustrates an organizational view that identifies individuals and groups that comprise a fictitious Finance Department. This type of view is useful when identifying how a network failure or a re configuration impacts an organizational unit. Note: If you purchased the Service Manager module, you can use this module in conjunction with the TopOrg topology to model business services and applications. Further, the Service Manager module also tracks the performance of the service against a contract or Service Level Agreement (SLA). For additional information about using the Service Manager module, see the Service
Manager User Guide (5155).
Figure 2-9: TopOrg Topology - Finance Department View
In the TopOrg topology, you can create several layers of views that represent various levels of your networked devices (Enterprise ownership, Department ownership, supporting devices, supporting services, etc.). Additionally, you can use the Component Detail panel to view and possibly change the attributes associated with a modeled device in any TopOrg topology view. For instance, by clicking the Component Detail tabs (associated with a modeled device) you can view device information, interfaces, alarms, events, and other pertinent device information.
For further information about creating views within the TopOrg topology, see Chapter 4, “Manual Modeling,” on page 67.
Icons in Topology Views
Icons appearing in SPECTRUM OneClick topology views are graphical representations of network entities such as individual devices, groups of devices, geographic locations, physical connections, and others.
When creating or editing a model, an icon is merely an image with which you interact to
manipulate and configure a modeled element. When monitoring the condition of a network through the SPECTRUM OneClick topology views, an icon represents the current status of a device, network group, device location, or a physical link in your infrastructure.
SPECTRUM OneClick offers both aggregate and individual icons for representing entities in your infrastructure. Table 2-1 describes the differences between these icons.I
SPECTRUM OneClick offers many types of individual and aggregate icons. The appearance of each icon is always based on the entity it represents in your network. The following sections further describe icons by themes, shape, symbol, and color.
Table 2-1: Individual and aggregate icons Aggregate icons
Aggregate icons are not managed by an IP or physical address. However, you can configure these icons to display the device IP address that container represents (or the subnet address of the devices that the container represents). These type of icons primarily act as containers, or placeholders in a topology view.
An aggregate icon often represents a network group icon. Some examples of network groups are LAN, LAN_802.x, FDDI, ATM_Network, WA_Link and Dialup_Link.
Individual icons
Icon Themes
Icon themes present a unified look and feel for all the icons that make up your models. You can apply one of the icon themes to your models from the OneClick View menu shown in Table 2-2:
Icon Shape, Symbol, and Theme
As you model devices in your network (through Discovery or manual modeling) SPECTRUM automatically determines the functionality of each device and selects the appropriate icon shape and symbol for that device.
Icons come in various shapes and sizes. Icon symbols vary by the model class represented and by the topology in which the icon is located.
The most frequently used icons in OneClick topology views are described in Table 2-3 and
Figure 2-10 , Figure 2-11 , Figure 2-12 . Table 2-2: OneClick Icon Themes Classic
The classic icon theme has been especially designed for former SpectroGRAPH users. This theme offers a similar appearance to the icons presented in SpectroGRAPH.
OneClick
The OneClick icon theme offers a modern looking appearance for modeled icons.
Utility
The Utility icon theme presents a simplified two-dimensional display of the modeled icons.
Table 2-3: Icon Types by Theme
Icon Type Icon Appearance by Theme
VNM icons
The Virtual Network Machine (VNM) icon normally appears in the top level view above the network group icons.
The background color of the VNM icon changes to indicate the current condition of the SpectroSERVER. For example, the VNM icon turns red when the
SpectroSERVER disk space reaches 90% capacity.
Network group icons
The network group icons represent network groupings such as cable groups, LANs, IP Class A, B, C networks, etc.
Device icons
A device icon represents an individual device. The device icon color changes to indicate the current condition of the modeled device. For example, the device icon changes redwhenever SPECTRUM detects a serious condition requiring attention.
Off-Page Reference icons
The off-page reference icon is a special-purpose topology icon. It represents a device that is directly connected to a device in the current view but is modeled in another layer.
Segment icons
Segment icons represent conceptual elements of a network.
Examples of segment icons can include (but not limited to): coax segment, wa_segment, fanout, unplaced icon, and pingable icons.
Live pipes (or links)
Live pipes represent the connection status between network devices. The links change color to indicate the current condition. A gold pipe represents a resolved connection. A silver pipe represents an unresolved connection.
Note that live pipes are not enabled by default. To monitor the connection status between devices, you must enable a live pipe.
Table 2-3: Icon Types by Theme (Continued)
Figure 2-10: OneClick Theme Icons and Symbols
Host Switch
Dialback
Ping SNMP Hub Bridge Fan out ReferenceOffpage
Network
Org Own
WAN Router VPN Event Event Admin VNM
LAN ATM Network MCAST OneClick
Org Service VPN Wireless Access Point Universal Transport Device Power Cable Modem
Printer IP Phone Firewall Flag Test
Figure 2-11: Classic Theme Icons and Symbols
Figure 2-12: Utility Theme Icons and Symbols Landscape
Hub LAN Cable
Event
Network VNM Router Switch Chassis VPN
Admin Landscape WAN Router Switch Pingable Workstation SNMP
Hub EventModel
Event
Admin BackupDial
VNM Chassis
LAN
802.3 Network VPN
Bridge
Host
WorkstationWorkstationHost Switch Ping SNMP Hub Bridge Fan out Dialback
WAN Router VPN Event EventAdmin Off Page
Reference VNM Network
LAN Chassis Landscape NetworkATM ServicesOrg OwnsOrg VPN
MCAST Printer
Wireless Access
IP Phone
Universal
Transport Power Firewall
Device Point
Icon Color and Condition
All icons change color to indicate the condition of the device(s) they represent. For instance, a device icon will change color when an alarm condition for that device occurs. A roll-up triangle on a device icon or container icon will change color when an alarm condition occurs on one or more of its components (devices or interfaces).
Figure 2-13: Roll-up and Color Conditions
Logical links (or pipes) change color to indicate the condition of the connection, for instance: disabled or maintenance conditions are brown, good conditions are green, initial conditions are blue, suppressed or unknown conditions are silver, and poor conditions are red.
The roll-up triangle associated with the Network container icon represents that one or more components of the container has a critical alarm. In this example, a device within the Network container has a critical alarm.
Normal Minor Major Critical Initial Maintenance
Green Yellow Orange Red Blue Brown Silver
Suppressed/ The roll-up triangle associated with the device icon represents that a component of that device has an alarm condition. In this example, an interface on a Cisco router has a minor alarm.
Icon condition colors: Roll-up conditions:
Provision Access to Modeled Elements
As an administrator you can secure access to SPECTRUM OneClick models by applying a security
string. A security string establishes permission to various modeled elements in a OneClick topology
view such as a modeled device.
After a security string is applied to a modeled device all subcomponent models (or views) of that device inherit the security string. The security string field for implementing modeled security appears in the Component Details panel.
Figure 2-14: Security String Setting on Component Detail Panel
For further information about creating or renaming Access Groups associated with individual users or user groups, see the OneClick Administration Guide (5166).
Information tab on Component Details panel
Boston
Methods for Modeling Network Entities
As an administrator you can define models representing entities in your IT infrastructure by manually modeling them or having the SPECTRUM OneClick Discovery feature create them for you:
Recommended Modeling Tips
When creating models in OneClick, consider following these recommended steps and tips outlined in the following table:
Table 2-4: SPECTRUM OneClick Modeling Methods SPECTRUM OneClick
Discovery feature By using OneClick’s Discovery feature, you can model your network infrastructure in less time and effort than by using the manual modeling process.
When using Discovery to automate the modeling process you are required to know:
• Device IP address ranges • Device SNMP community names
Note that all discovery results are modeled to the Universe topology. To learn more about automated modeling using Discovery, see “Discover and Model Your Network” on page 37.
Manual modeling When you manually model your network you are required to have knowledge of all the network devices you plan to model, including their:
• IP addresses
• Device SNMP Community names
All four core topologies (Universe, Global Collections, World, and TopOrg) in OneClick support manual modeling operations. However, we recommend that you always model new devices in the Universe topology and then reuse these modeled devices to create other topologies views.
Table 2-5: Recommend Modeling Steps
Recommended steps: Tips
1. Plan Create a plan about the network entities you want to model by gathering all required network device information. For instance: • Typical information needed for Discovery operations include:
• Range of IP addresses of all addressable devices. • SNMP Community names for devices
• Router address (optional).
• Typical information needed for manual modeling operations include:
• Type of network (switched, routed, flat) • Network masks
• Network technology (FDDI, Ethernet, WAN, etc.) • List of all devices
• IP addresses for all addressable devices • SNMP Community names for all devices • Physical and logical network diagrams 2. Use OneClick’s Discovery feature
to model.
In the Universe topology, create one or multiple discovery
configurations to locate and identify the devices you want to model. Use the filter mechanism to exclude any devices from the result list you don’t want to model. After you are satisfied with the device list (or results list), use Discovery’s modeling option to model these devices in the Universe topology.
For more information about Discovery, see “Discover and Model Your Network” on page 37.
3. As needed, use OneClick’s manual modeling features to define or edit models.
There are a number of ways you can manually create or edit models in OneClick:
• In the Global Collections topology, you can create and name collections of devices previously modeled in the Universe topology. • In the Universe topology, you could add devices and annotations to
existing models, change device configuration information, or improve the readability of models by possibly keeping the layers within the Universe topology simple. You may want to consider placing routers near the top and grouping devices logically by IP domains.
How to Get Started
If you are not sure which modeling feature to use to accomplish your task, here are some references to help you get started:
Table 2-6: Using Discovery to Discover and Model, Chapter 3
To Do the Following: Refer to:
Learn what Discovery provides and how you can use it page 38
Launch the Discovery Console page 40
Get acquainted with Discovery commonly-used terms page 38
Learn about the two configurations you create in Discovery page 39
Learn about the Discovery Console tabs and settings page 41
Define a configuration using the Discovery Configuration tab page 54
Define a configuration using the Modeling Configuration dialog box page 57 Activate a Discovery session per the Discovery Configuration settings page 61 Activate a Modeling session per the Discovery tab results list page 62 Learn what the discovery results list provides and how you can use it page 63 Learn what the modeling results list provides and how you can use it page 63
Use the Advanced Filter to filter results page 63
Use Export to export the results list to a supported file format page 63
Table 2-7: Manually modeling, Chapter 4
To Do the Following: Refer to:
When to model manually in OneClick page 67
Get acquainted with manual modeling terminology page 68
Learn about the manual modeling features available in the Universe topology page 68
Learn how to create containers in the Universe topology page 69
Learn how to add network devices to a Universe topology page 71
Learn how to depict connections (pipes) between modeled devices page 76 Learn about the manual modeling features available in the Global Collections topology page 80
Learn how to perform global collection modeling tasks page 82
Learn how to create a Global Collection Hierarchy page 89
Table 2-8: Enhancing Topology Views, Chapter 5
To Do the Following: Refer to:
Learn how to enhance topology views using the Edit mode page 106
Learn how to perform editing tasks to enhance a topology view page 110
Table 2-9: Editing Model Device Attributes, Chapter 6
To Do the Following: Refer to:
Learn about changing attributes at the device level page 125
Network
In This Chapter
This chapter steps you through the tasks associated with defining and maintaining SPECTRUM OneClick Discovery configurations. Specifically, this chapter defines Discovery’s capabilities, its user-interface, and the ways you can use Discovery to discover and model devices. Finally, it provides detailed procedures for defining and activating Discovery configurations, modeling Discovery results, and filtering and exporting the Discovery results.
After reading this chapter, you will understand Discovery capabilities and how to use the Discovery Console to define, maintain, and activate discovery and modeling configurations.
The information in this chapter is presented in the following sections: • “What Is Discovery?” on page 38
• “Discovery Overview” on page 39
• “Discovery Console Layout” on page 41
• “Define and Activate Configurations” on page 54
• “View, Filter, and Export Results Lists” on page 63
• “After Discovering and Modeling” on page 65
• “VNM AutoDiscovery Control Settings” on page 65
You must have the appropriate user level privilege to use the discovery or modeling options described in this chapter. For more information about setting user privileges, see the OneClick
What Is Discovery?
Discovery finds devices in your network and automates the process of modeling them within the Universe topology. It uses a set of configuration parameters to determine which network entities to discover and model. You specify these configuration parameters using Discovery accessed from the OneClick window. You can reuse any set of previously saved configuration parameters. You can also rename, duplicate, or delete configurations.
Ways to Use Discovery
Depending on the user privileges assigned, you can use the automated discovery and modeling features in conjunction with one another or you can use them separately. For example, here are some ways in which you can use Discovery:
• To perform network inventories. If you have read/write privileges to the discovery parameters, you can use Discovery to identify assets within your network and, as needed, export the results describing those assets to a desired file format for further review and distribution.
• To model network entities you want to manage. If you have read/write privileges to both discovery and modeling parameters, you can use Discovery to (1) determine which elements in your network you want to model and (2) identify how you would like SPECTRUM to
automatically model these elements for you.
By specifying modeling parameters in conjunction with the discovery parameters, you can easily create accurate software models of your infrastructure in less time and effort than if you had to manually model them yourself. After using Discovery to create models in the Universe topology, you can at any time enhance your models further by using the manual modeling features later described in Chapter 4.
Discovery Terms
Table 3-1 identifies terms used in SPECTRUM OneClick for performing the Discovery tasks described in this chapter.
Table 3-1: SPECTRUM OneClick Discovery Terms
Discovery Provides all the functionality for creating, editing, and activating discovery and modeling configurations; as well as, filtering and exporting the results of discovery or modeling session.
Configuration Contains the parameters you specify to determine which network entities in your infrastructure you want Discovery to locate and identify for review, export, or modeling. Discovery session Occurs upon activating a configuration to discover network entities per the parameters
specified in the configuration. It uses SNMP and other network technologies to discover and identify network entities specified in the configuration.
Modeling session Occurs upon instructing Discovery to model the results of a discovery session. It uses the Modeling options specified to model the network entities discovered in that configuration. Results (list) Provide a detailed list of the network entities discovered from a discovery session, or
Discovery Overview
Use Discovery to create configurations to discover devices in your network, and if you choose to do so, automate the process of modeling the devices within the Universe topology. Each configuration uses a set of parameters to determine which network entities to discover and model. You specify these configuration parameters using the Configuration tab.
A configuration determines the focus and scope of a discovery or modelling session. You define the configuration by selecting parameters on the Discovery Console Configuration tab. After creating a configuration, you have the choice of when to active it:
• You can activate the configuration immediately by clicking Discover.
• You can schedule when to activate the configuration, including scheduling it to recur. • You can save the configuration and activate it at a later time.
Discovery Session
Whether you choose to run Discovery only, or Discover and automatically model to SPECTRUM, a Discovery session runs when you click Discover or at the scheduled time.
Discovery Status
Once you activate a configuration, you can access the status of the discovery session in two locations:
• The Discovery Status panel of the Discovery tab shows current or most recent status information.
• The Discover Status Tab in the History tab view shows historical status information for a selected discovery session.
Discovery Results
The Discovery results table appears in two locations: • The upper panel of the Discovery tab
• The Discovery Results tab in the History tab view
Model Discovery Results
You can model Discovery results either as part of the Discovery session, or any time after the Discovery session has completed, provided you save the configuration. You can specify how SPECTRUM models discovered devices appearing in the results list of the Discovery tab. On the Modeling Configuration dialog box, you can choose to accept the default modeling options or change them to meet your needs. You can activate a modeling session two ways:
• Select Discover and automatically model to SPECTRUM in the configuration
Modeling Status
You can view the status of a modeling session while it is occurring in the Modeling Status panel of the Model tab. The status is also available after the modeling session is complete in the Modeling Status tab of the History tab view. See “Filter, Sort, Export, and Search Modeling Results” on page 50.
Modeling Results
You can view the modeling results in the upper section of the Modeling tab view.
Why Use Different Configurations?
Separate configurations offer more flexibility for customizing the discovery and modeling process. By providing separate configurations, you can :
• Discover limited portions of your network by performing several smaller discovery operations instead of performing one large discovery operation.
• Model the results of a discovery operation using different modeling options. • Filter and export the results of a discovery session in different ways. • Filter and export the results of a modeling session in different ways.
Launch Discovery
You can launch Discovery with and without context of a selected device.
Launching Discovery without Context
• Tools menu. Select Tools, Utilities, Discovery.
• Discovery icon. Click Discovery ( ) in the Topology view tool bar without selecting a device in the Navigation panel or topology view.
Launching Discovery with Context
You can launch Discovery with the context of a selected element using the following methods: • Right-click on a selected element in the Universe navigation node and select Utilities,
Discovery.
• Right-click on a selected element in the Topology tab in the Contents panel and select Utilities, Discovery.
• Select an element in the Topology tab, and click the Create Discovery icon in the tool bar.
Use Existing Discovery Configurations
When you launch Discovery in the context of a selected element, the Use Existing dialog box appears if any existing configurations include the IP address of the selected device. You can either select one of the existing configurations or create a new configuration. If you create a new
configuration, the Seed Router IP field is populated with the IP address of the device.
selected container. You can either select one of the existing configurations or create a new
configuration. If you create a new configuration, the IP Boundary List field is populated with an IP range. The IP range is determined by using the network address and network address mask for the selected container.
See “To Define a Configuration with Context of a Seed Router” on page 54 for more information.
Discovery Console Layout
Figure 3-1: Discovery Console Layout
Discovery Navigation Panel
Figure 3-2: Discovery Navigation Panel
Create or Open Configurations
Using the tool bar functions in the Navigation panel, you can create, open, copy or delete configurations.
Create Folders
Use the Navigation panel tool bar to create a new folder in which you can create a new
configuration or copy an existing configuration. You can move existing configurations to different folders using the drag and drop method.
Contents Panel
The Discovery Console groups the parameters you use to define discovery and modeling
configurations into four tabs: the Configuration tab; the Discovery tab; the Modeling tab, and the History tab.
Configuration Tab
The Configuration tab lists all the required and optional parameters you can set to create a configuration. This tab is available to all users with privileges to discovery operations. Figure 3-3
shows the Discovery Configuration tab.
Landscape selector Tool bar
Figure 3-3: Configuration Tab
Specify IP Addresses
Specify the configuration IP parameters using one IP address, a range of IP addresses, or by building a list of IP addresses in the Seed Routers and IP Boundary List sections. See Table 3-2 on page 55 for more information about using these parameters to define a configuration.
• Seed Routers. Enter the IP addresses for any seed routers on your network that will act as an initial communication point to discover the network topology. If you launch Discovery in the context of a network element, the Seed Router field is populated with the IP address of that device. You can add additional seed router IP addresses (see “Launch Discovery” on page 40
for information about device context).
• IP Boundary List. Enter a range of IP addresses, one or more single IP addresses, and any combination of the two to define the boundaries for the configuration. If you launch Discovery in the context of a container in the Topology view or Explorer view, the IP Boundary List is populated with an address range determined using the IP address and network mask of the select device. You can specify additional IP addresses and address ranges.
• Import IP Addresses. You can import IP addresses into a configuration from a text file. You can import IP addresses in a one-time or static manner, or you can import the addresses each time the configuration is activated, or dynamically.
Seed router parameters
IP Boundary List SNMP parameters
Import IP Addresses Import community strings and profiles Modeling options
Advanced options
Scheduling options
To Import IP Addresses Statically or One Time
1. Click Import. The Import File dialog box appears.
2. To import a text file containing IP addresses while you are creating the configuration only, select Local Host from the drop-down menu. Then select the text file containing the IP addresses to import.
3. Click OK. OneClick Discovery reads in this information at this time only.
To Dynamically Import IP Addresses
1. Click Import. The Import File dialog box appears.
2. Select OneClick web server host from the Import file location drop-down list.
3. Enter the path to the file on the OneClick Web server host that contains the IP addresses to import. This option instructs OneClick to read this file and import the IP addresses during each configuration activation.
4. Click OK.
The IP addresses in the text file can be updated on a regular basis, and the updates are reflected in each activation. This feature provides an automated way of maintaining current IP addresses when activating a configuration on a scheduled basis.
Syntax for Dynamic Import: The path to text file on the OneClick Web server must be in the native format of the OneClick Web server operating system (OS).
• If the Web server is running a Microsoft Windows OS, the format of the path must be C:\Program Files\Spectrum\IP_Files\core_network_ips
• If the Web server is running a Solaris or Linux OS, the format of the path must be /usr/Spectrum/IP_Files/core_network_ips
Specify Modeling Options
If you have read/write privileges to Discovery’s modeling operations, you can specify if you want to perform a discover only operation or a combined discover and model operation. By clicking the Modeling Options button you can review and accept the modeling defaults provided or edit them as needed. For more information about modeling options, see “Define Modeling Options” on page 57.
Specify Advanced Options
The Advanced Options button on the Configuration tab launches the Advanced Options dialog box. In Advanced Options dialog box you can review, accept, or redefine the following options:
• SNMP Ports. Discovery, by default, uses port 161, however, you can specify additional ports. This feature is most often used for managed node environments that use port numbers other than the default port number of 161.
• IP Exclusion List. Create, delete, modify, or import an IP exclusion list so that the discovery session will not look for devices in a defined range of IP addresses.
• Auto Export. Choose whether or not to automatically export the complete discovery session results or just any differences from the previous discovery session; select the format to export them in (comma delimited, tab delimited, or web page).
SNMP Information
• Community Strings and Profiles. The Community String/Profile Name table displays an ordered list of SNMP v1 and v2c community strings and v3 security parameters currently applied to the configuration.
Note: If you have either Secure Domain Manager or SNMP v3 Proxy OneClick add-on applications installed, you will be able to use the SNMP v2c SNMP v3 parameter options described here.
Add community strings by selecting SNMP v1 or SNMP v2c, entering the community string in the Community String text box, and clicking Add.
Add SNMP v3 profiles by selecting SNMP v3, clicking the V3 Profile drop-down menu and selecting from the profiles listed.
• Edit and Create Profiles. Edit or create SNMP v3 profiles by selecting SNMP v3 and clicking Profiles. Create, modify or remove profiles in the Edit SNMP v3 Profiles dialog (see Figure 3-4). Figure 3-4: Edit SNMP v3 Profiles Dialog Box
• Import Community Strings and Profiles. You can import community strings and profiles from a text file. Click Import to import SNMP v1 and V2c community strings and SNMP v3 profile names. Valid community strings and profile names imported from a text file are added to the lists of available community strings and profile names. You cannot create profile names using Import. Use the SNMP v3 profile editor.
Note: You must first create any desired profile names using the Edit SNMP v3 Profiles dialog before importing the text file. During import, SPECTRUM OneClick verifies the list of SNMP v3 profile names in the text file against the existing profiles that have been manually created using the Edit SNMP v3 Profiles dialog (see Figure 3-4). If a profile name included in the text
Profile parameters The selected authentication level determines passwords required for each profile
file being imported does not already exist in SPECTRUM, an error message displays and the import action fails.
Syntax for Imported Community Strings and Profiles
Use the following syntax when creating a text file containing community strings and profiles: <name>,v<SNMP_version>
where <name> is the actual community string or profile, and <SNMP_version> is either 1, 2, or 3. Use of the version number for SNMP v1 community strings is optional.
For SNMP v1 community strings use either of the following: public
public,v1
For SNMP v2 community strings use: public,v2
For SNMP v3 profiles use: public,v3
Configuration Scheduling Options
To keep your network model current, you can activate a configuration on a regular schedule. Note: In a DSS environment that spans multiple time zones, schedules are executed according to each SpectroSERVERs local time. Please refer to the OneClick Console User Guide (5130) for more information regarding OneClick schedules in a DSS environment.
• Current Schedule Setting. The configuration schedule setting appears next to Select in the Scheduling Options section.
• Set a Schedule. To set a schedule for activating the configuration, click Select. The Select Schedule window appears.
Select one of the existing schedules displayed in the Select Schedule window and click OK, or click Create to create a new schedule. The Create Schedule window appears. See
Change Default Configuration Options
Select Save options as default to save all specified configuration settings and apply them to future configurations (regardless of whether or not the configuration is named).
For example, the Discover only option is by default enabled on the Configuration tab. If you prefer to select Discover and automatically model to SPECTRUM as the default setting, do the following: 1. Select Discover and automatically model to SPECTRUM.
2. Select Save options as default and click Save Changes. The option Discover and automatically model to SPECTRUM is now enabled by default on the Discovery Console (until it is changed using the steps previously described).
Discovery Tab
discovery privileges. The Discovery tab initially appears disabled for new discovery configurations and becomes enabled after an initial discovery session is generated from the Configuration tab. The Discovery Results table. The Discovery results table includes the following columns by default: IP Address, sysName, Device Type, and sysDescr. Right-click on one of the column headings to display the Table Preferences dialog box. You can select additional columns to display in this dialog box. The Model State column tells you whether the device is currently modeled in OneClick or not. This is useful in identifying devices discovered on your network that require modeling in OneClick.
Figure 3-5: Discovery Tab
Filter, Sort, Export, Search, and Model Discovery Results
The Discovery tab provides the following options to help you review, filter, export, and model the discovery results:
Export Filter text box AdvancedFilter
Results list
• Filter text box. The filter text box enables you to quickly filter the devices in the Discovery Results list. For example: if you wanted to develop, model, and export a list of Cisco devices from your results list, you would:
a. Type Cisco in the Filtering text box to filter the results list by Cisco devices. b. Click Model to model only the Cisco devices.
c. Click Export to export the Cisco device results list.
• Advanced Filter button. Click Advanced Filter to establish additional filter criteria by creating one or more expressions. These expressions enable you to set additional filters on the
discovery results list. For more information about using the Advanced Filter mechanism, see
“Filter Results Using Advanced Filter” on page 63.
• Right-click menu command - Exclude. You can exclude one or multiple entries in the discovery result list by right-clicking the entries (rows) that you want to exclude and selecting Exclude. If you have selected Save options as default in the Configuration tab, and you save the configuration after excluding one or more devices, those devices are also excluded from the discovery configuration whenever it is run again.
• Export button. Clicking Export launches the Export table data to file dialog box. In this dialog box, you can specify a file format and location to export the discovery results. For more information, see “Exporting a Results List” on page 63.
• Status search. Enter character strings that you want to search for in Discovery or Model Status into the Search text field. Select Highlight All to see all search matches in the Status panel. Use Next and Previous to navigate through all of the search matches in the Status panel. • Model. Click Model to launch the Modeling Configuration dialog box. In this dialog box, you can
review or modify the default modeling options provided. When you click OK, SPECTRUM OneClick models only the devices appearing in the discovery results list. Note that this function is only enabled for users with privileges to modeling operations. For more information, see
“Define Modeling Options” on page 57.
Modeling Tab
Figure 3-6: Modeling Tab
The Modeling tab is available to all users with modeling privileges. This tab initially appears disabled for new discovery configurations and only becomes enabled after an initial modeling session is activated from the Discovery tab.
Filter, Sort, Export, and Search Modeling Results
The Modeling tab provides the following options to help you review, filter, export, and search modeling results:
• Filter text box - see “Filter, Sort, Export, Search, and Model Discovery Results” on page 48
• Sort controls - see “Filter, Sort, Export, Search, and Model Discovery Results” on page 48
• Export button - see “Filter, Sort, Export, Search, and Model Discovery Results” on page 48
• Status search - see “Filter, Sort, Export, Search, and Model Discovery Results” on page 48 Results set
