Modeling Your IT Infrastructure

Transcription

1 Modeling Your IT Infrastructure Administrator Guide Document 5167

2 Notice 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 , , and (c)(1) - (2) and DFARS Section (c)(1)(ii), as applicable, or their successors. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2007 CA. All rights reserved.

3 Contents Preface Chapter 1: Welcome to Modeling Your IT Infrastructure Network Modeling in OneClick SPECTRUM OneClick Terms Next Steps Chapter 2: Getting Started SPECTRUM OneClick Topologies Universe Topology Top View of Universe Topology Drill Down View of Universe Topology Component Detail View Define Models in the Universe Topology Global Collections Topology How to Use Global Collections Populate Global Collections View or Modify Modeled Devices World Topology TopOrg Topology Icons in Topology Views Icon Themes Icon Shape, Symbol, and Theme Icon Color and Condition Provision Access to Modeled Elements Methods for Modeling Network Entities Recommended Modeling Tips How to Get Started Chapter 3: Discover and Model Your Network What Is Discovery? Ways to Use Discovery Discovery Terms Discovery Overview Discovery Session Discovery Status Discovery Results Model Discovery Results Modeling Status

4 Contents Modeling Results Why Use Different Configurations? Launch Discovery Launching Discovery without Context Launching Discovery with Context Use Existing Discovery Configurations Discovery Console Layout Discovery Navigation Panel Create or Open Configurations Create Folders Contents Panel Configuration Tab Discovery Tab Modeling Tab History Tab Discovery Connection Status Define and Activate Configurations Define a Configuration Define Modeling Options Activate a Discovery Session Activate a Modeling Session View, Filter, and Export Results Lists Exporting a Results List Filter Results Using Advanced Filter After Discovering and Modeling VNM AutoDiscovery Control Settings Access VNM AutoDiscovery Control Loopback Interfaces and Discovery Chapter 4: Manual Modeling When to Model Manually in OneClick SPECTRUM OneClick Modeling Terminology Manual Modeling in the Universe Topology Create or Use an Existing Container Add Devices to Container Create Connections Enhance Topology View Add Containers to Universe Topology Views Add Existing Devices to Container Add Network Devices to Universe Topology Views Delete Modeled Elements from the Universe Topology View Modeling Your IT Infrastructure Administrator Guide

5 Contents Cut Modeled Element from Universe Topology View Export a Universe Topology View Create Connections (Pipes) Between Modeled Devices Removing Connections from a Universe Topology View Create an Unresolved Connection Between Modeled Elements Create a Resolved Connection (both device ports known) Create a Partially-resolved Connection (one device port known) Lock and Unlock Resolved Connections Enable or Disable a Live Link (applies to full or partial resolved connections) Model Manually in Global Collections Topology Dynamic Membership - Use Search Criteria Recommended Process for Defining Collections Global Collections Modeling Tasks Define a New Collection Edit an Existing Collection Create a Global Collection Hierarchy Manually Modeling in the World Topology View Recommended Process for Modeling Locations Manually Modeling the TopOrg Topology Model Services in the TopOrg Topology Chapter 5: Modeled Device and Interface Configurations Device and Interface Threshold Settings Device Threshold Settings Example: % CPU Utilization Default Settings Interface Threshold Settings Update Device Interface and Connection Information Automatically Updating Device Interface and Connection Information Manually Updating Device Interface and Connection Information Access Interface and Connection Update Controls Tools, Reconfiguration Menu Reconfiguration Subview and Advanced Subview Attribute Editor Change Management Group Redundant Connections between SPECTRUM and Modeled Devices Redundancy Preferred Addresses List Device Primary Address IP Redundancy Subview Redundancy Excluded Addresses List Chapter 6: Edit and Enhance Topology Views Commonly Used Terms Topology View Edit Mode Preferences Modeling Your IT Infrastructure Administrator Guide 5

6 Contents Use Edit Mode to Enhance Topology Views Accessing the Edit Mode Feature Edit Mode Tool Bar How to Enhance a Topology View Proportionally Resize Model Icons Add Shapes, Lines, or Text to a View Change Shapes, Lines, and Text Characteristics Enhancing Topology Background Group and Ungroup Items in a View Bringing Items to Front or Sending Items to Back Chapter 7: Device Type Identification Device Type Identification in OneClick Launch Device Type Identification Device Type Identification Table Search DTI Mappings Using Filters Apply DTI Changes to SPECTRUM Model Catalog Manage Device Type Mappings Custom Device Type Mappings Custom Mappings with Modified Device Type Name Custom Mappings with Modified SysObjectID Delete Custom DTI Mappings Map Unregistered Devices Distributed SpectroSERVER Support Servers Unavailable Warning DTI Mapping Conflicts Missing DTI Entries DTI and Fault Tolerant Environments Customization Considerations Prevent Changes to All Device Model Types Using DeviceTypeDiscEnable Attribute Preserve Device Type Customizations for Specific Devices Prevent Device Type Name Changes on Model Types Chapter 8: Modify Model Attributes Why Modify Attributes? Access Attributes From the Information Tab VNM Attributes in the Information Tab General Information Online Database Backup SpectroSERVER Control AutoDiscovery Control Modeling and Protocol Options Modeling Your IT Infrastructure Administrator Guide

7 Contents Trap Based Continuous Discovery Debug Options Fault Isolation Live Pipes Live Pipes and Global Collections in DSS Environments Alarm Management OneClick Attribute Editor Launch Attribute Editor Open Attribute Editor with Device Context Attribute Editor Dialog Box Task Oriented Attribute Groupings Filter Attribute Categories Attribute Edit Panel Attribute Editor Results Dialog User Defined Attributes Attribute Selector Dialog Box Change Attributes in Conjunction with Search Define a Search to Create a User Defined Attribute for Editing Edit Attributes for Specific Devices or for Model Types Example: Edit Interface_Polling_Interval for Cisco Devices Supporting IPsec Example: Edit the DeviceTypeDiscEnable Attribute for Specific Devices Example: Edit DeviceTypeDiscEnable for a Model Type Attribute Groupings Change Management Interface Configuration Stale Interfaces Maintenance Mode Attributes Roll-up Alarm Attributes Model Status and Alarm Conditions Roll-up Condition Thresholds SNMP Communications Attributes Tuning SPECTRUM s SNMP Communications More Efficient SNMP Communications Increase Reliability Thresholds Device Thresholds Interface Thresholds Chapter 9: MIB and Trap Management SNMP, MIBs, and SPECTRUM How a MIB Is Organized Object Identifiers Modeling Your IT Infrastructure Administrator Guide 7

8 Contents OneClick MIB Tools MIB Browser MIB Tools Database MIB Import Query Device MIBs Export MIB Tools Data Attribute and Trap Mapping in SPECTRUM MIB Tools User Interface Launch MIB Tools Launch MIB Tools In Context Navigation Panel MIB Management Import Individual MIBs Compile MIB Files MIB Editor Import Multiple MIBs Contents Panel Browse MIBs Browse Tab Contact Criteria MIB Tree Hierarchy Table Hierarchy Tool Bar Access MIB Objects on Network Devices View MIB Object Values Set MIB Object Values on a Device Device Query and SET Results Export Query Results To Support Troubleshooting Contents Panel Attribute and Trap Management Map Tab Attribute Support Table Create Attributes Trap Support Table Map Traps Create Trap Support Custom Trap Support File Details Identify and Resolve Partial Trap Support Multiple SpectroSERVERs Best Practice for Maintaining MIB Tools in a DSS Environment Attribute Support Conflicts Resolve Attribute Support Conflicts Incomplete Trap and Attribute Support Create Consistent Support Across a DSS Environment Trap Disposition Conflicts Resolve Trap Disposition Conflicts Modeling Your IT Infrastructure Administrator Guide

9 Contents Multiple OneClick Servers Best Practices to Maintain Synchronization Index Modeling Your IT Infrastructure Administrator Guide 9

10 Contents 10 Modeling Your IT Infrastructure Administrator Guide

11 Preface 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 8: Modify Model Attributes on page 125 discusses how to modify SPECTRUM OneClick model attributes using the OneClick Information view and the OneClick Attribute Editor. 11

12 Preface 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: 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 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 hypertextblue See Document Feedback on page 12. References to SPECTRUM documents (title and number) Italic SPECTRUM Installation Guide (5136) Document Feedback Please send feedback regarding SPECTRUM documents to the following address: [email protected] 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. 12 Modeling Your IT Infrastructure Guide Administrator Guide

13 Chapter 1: Welcome to Modeling Your IT 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. Modify device model attributes. After you have modeled your network using Discovery, you can modify specific attributes for all models of the same model type using the Attribute Editor. See Chapter 8, Modify Model Attributes, on page

14 Chapter 1: Welcome to Modeling Your IT Infrastructure 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 SpectroSERVER Distributed SpectroSERVER (DSS) Environment Topologies Manual modeling Discovery The Landscape is the network domain managed by a single 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). 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 are iconic views in OneClick of a modeled network. Manual modeling is the act of manually representing individual devices and their connections within a SPECTRUM OneClick topology view. Discovery is a OneClick feature used to automate the process of discovering and modeling entities in your IT infrastructure. 14 Modeling Your IT Infrastructure Administrator Guide

15 Next Steps Table 1-2: Commonly Used Modeling Terms Landscape Methods of modeling Network entity Modeling entity Security strings The Landscape is the local or remote SpectroSERVER. 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 most often refers to a device, an interface, a container, or a physical connection that makes up your IT infrastructure. A Modeling entity most often refers to an icon representing an individual modeled device, container, or physical connection. Security strings establish permission to various elements in OneClick models such as modeled devices. As an administrator you can secure access to models using a security string. See Provision Access to Modeled Elements on page 31 for more information. 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. Modeling Your IT Infrastructure Administrator Guide 15

16 Chapter 1: Welcome to Modeling Your IT Infrastructure 16 Modeling Your IT Infrastructure Administrator Guide

17 Chapter 2: Getting Started 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. In SPECTRUM OneClick, we recommend that you begin modeling with the Universe topology. After you have established one or more modeled elements in the Universe topology, you can reuse these modeled elements to define the other topologies, as shown in Figure

18 Chapter 2: Getting Started 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 The Universe topology helps you organize an enterprise network view of your infrastructure. Most often it provides a top level topology view of OSI Layer 3 devices and their connections, a drill- 18 Modeling Your IT Infrastructure Administrator Guide

19 SPECTRUM OneClick Topologies 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 SPECTRUM Virtual Network Machine OSI Layer 3 devices, such as a router and its connection Icon representing a WAN Segment 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 2 devices such as a switch. Off page reference to an OSI Layer 3 device (router) Modeling Your IT Infrastructure Administrator Guide 19

20 Chapter 2: Getting Started 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 You can define models in the Universe topology using OneClick s Discovery feature that automates the modeling process for you. You can also manually define new models or edit existing models in the Universe topology by using the modeling tools provided with OneClick. Finally, since the Universe topology view represents a true connectivity view of your infrastructure, we strongly 20 Modeling Your IT Infrastructure Administrator Guide

21 SPECTRUM OneClick Topologies 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. Figure 2-5: Cisco Router Collection Modeling Your IT Infrastructure Administrator Guide 21

22 Chapter 2: Getting Started 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 Create and name the new collection Specify the search criteria to locate the modeled devices to populate the new collection 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. 22 Modeling Your IT Infrastructure Administrator Guide

23 SPECTRUM OneClick Topologies Figure 2-7: Component Detail Panel - Global Collections Tabs for viewing and changing device attributes and settings The information tab provides general information about the selected modeled device 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 Contents of equipment container. 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 OneClick environment. Modeling Your IT Infrastructure Administrator Guide 23

24 Chapter 2: Getting Started 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 Finance Department: comprised of individuals and work groups 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. Finally, when populating the TopOrg 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 OneClick environment. 24 Modeling Your IT Infrastructure Administrator Guide

25 SPECTRUM OneClick Topologies 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 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 Individual icons are typically associated with an IP address or a physical address. SPECTRUM can communicate directly with the devices the individual icons represent, so long as the entities they represent are SNMP and ICMP entities. Individual icons often represent network devices. Some examples of individual icons are those that represent a router, switch, or host. 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. Modeling Your IT Infrastructure Administrator Guide 25

26 Chapter 2: Getting Started 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: 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. VNM icon example OneClick The OneClick icon theme offers a modern looking appearance for modeled icons. VNM icon example Utility The Utility icon theme presents a simplified two-dimensional display of the modeled icons. VNM icon example 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 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. 26 Modeling Your IT Infrastructure Administrator Guide

27 SPECTRUM OneClick Topologies Table 2-3: Icon Types by Theme (Continued) Icon Type Icon Appearance by Theme 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 red whenever 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. Modeling Your IT Infrastructure Administrator Guide 27

28 Chapter 2: Getting Started Figure 2-10: OneClick Theme Icons and Symbols Host Switch Ping SNMP Hub Bridge Fan out Offpage Reference Dialback WAN Router VPN Event Event Admin VNM Network LAN Chassis ATM Network MCAST OneClick Org Own Org Service VPN Cable Modem Power Test Universal Transport Device Wireless Access Point Printer IP Phone Firewall Flag 28 Modeling Your IT Infrastructure Administrator Guide

29 SPECTRUM OneClick Topologies Figure 2-11: Classic Theme Icons and Symbols Landscape Hub LAN Cable Event Admin Network VNM Router Switch Chassis VPN Landscape Hub LAN Event Model VNM Router Switch Chassis Network VPN SNMP Pingable Bridge Event Admin Dial Backup WAN Workstation Figure 2-12: Utility Theme Icons and Symbols Host Host Workstation Workstation Switch Ping SNMP Hub Bridge Fan out Dialback WAN Router VPN Event EventAdmin Off Page Reference VNM Network LAN Chassis Landscape ATM Network Org Services Org Owns VPN MCAST Printer Wireless Access Point IP Phone Universal Transport Cable Power Firewall Device Modem Modeling Your IT Infrastructure Administrator Guide 29

30 Chapter 2: Getting Started 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 Roll-up conditions: 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. 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: Normal Minor Major Critical Initial Maintenance Suppressed/ Unknown Green Yellow Orange Red Blue Brown Silver 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. 30 Modeling Your IT Infrastructure Administrator Guide

31 Provision Access to Modeled Elements 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 Information tab on Component Details panel Boston In this example, the security string Boston prevents any user that does not have an Access Group of Boston from accessing this modeled element. Note that a Super User or any user with an Access Group of Admin overrides model security (meaning these users can access all model elements regardless of the security string implemented). For further information about creating or renaming Access Groups associated with individual users or user groups, see the OneClick Administration Guide (5166). Modeling Your IT Infrastructure Administrator Guide 31

32 Chapter 2: Getting Started 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: Table 2-4: SPECTRUM OneClick Modeling Methods SPECTRUM OneClick Discovery feature Manual modeling 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. 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. To learn more about manual modeling, see Manual Modeling on page 67. Recommended Modeling Tips When creating models in OneClick, consider following these recommended steps and tips outlined in the following table: 32 Modeling Your IT Infrastructure Administrator Guide

33 Methods for Modeling Network Entities 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. 3. As needed, use OneClick s manual modeling features to define or edit models. 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. 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. For more information about OneClick s manual modeling features, see Manual Modeling on page 67 and Edit and Enhance Topology Views on page 105. Modeling Your IT Infrastructure Administrator Guide 33

34 Chapter 2: Getting Started 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 Learn about the manual modeling features available in the World topology. page 89 Learn about the manual modeling features available in the TopOrg topology. page Modeling Your IT Infrastructure Administrator Guide

35 How to Get Started 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 Learn about changing attributes at the device level using search page 139 Modeling Your IT Infrastructure Administrator Guide 35

36 Chapter 2: Getting Started 36 Modeling Your IT Infrastructure Administrator Guide

37 Chapter 3: Discover and Model Your 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 Administration Guide (5160). 37

38 Chapter 3: Discover and Model Your Network 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 Configuration Discovery session Modeling session Results (list) 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. 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. 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. 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. Provide a detailed list of the network entities discovered from a discovery session, or network entities modeled from a modeling session. 38 Modeling Your IT Infrastructure Administrator Guide

39 Discovery Overview 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 Click Model on the Discovery tab, after a discovery session has run for that configuration. Modeling Your IT Infrastructure Administrator Guide 39

40 Chapter 3: Discover and Model Your Network 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. When you launch Discovery in the context of a selected container in the Topology view, the Use Existing dialog box appears if any existing configurations include the IP address range of the 40 Modeling Your IT Infrastructure Administrator Guide

41 Discovery Console Layout 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 The Discovery Console has two main panels, the Navigation panel on the left, and the Contents panel on the right (Figure 3-1). The main features of the Discovery console are: Modeling Your IT Infrastructure Administrator Guide 41

42 Chapter 3: Discover and Model Your Network Figure 3-1: Discovery Console Layout Discovery Navigation Panel The Navigation panel (Figure 3-2) consists of a landscape selection box, a tool bar, and a list of configurations and folders available on the selected landscape. 42 Modeling Your IT Infrastructure Administrator Guide

43 Discovery Console Layout Figure 3-2: Discovery Navigation Panel Landscape selector Tool bar List of configurations and folders 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. Modeling Your IT Infrastructure Administrator Guide 43

44 Chapter 3: Discover and Model Your Network Figure 3-3: Configuration Tab Seed router parameters IP Boundary List SNMP parameters Import IP Addresses Import community strings and profiles Modeling options Advanced options Scheduling options Save options as default 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. 44 Modeling Your IT Infrastructure Administrator Guide

45 Discovery Console Layout 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. Discovery Options. Choose if the Discovery process uses ICMP, Route Tables; if you select Route Tables, you can set a Throttle level that controls the rate at which the server sends SNMP requests. See Define a Configuration on page 54, Table 3-2 on page 55 for more information. Modeling Your IT Infrastructure Administrator Guide 45

46 Chapter 3: Discover and Model Your Network 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 Existing profiles Profile parameters The selected authentication level determines passwords required for each profile 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 46 Modeling Your IT Infrastructure Administrator Guide

47 Discovery Console Layout 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 The Discovery tab (Figure 3-5) displays the results and status of the most recent discovery session for the configuration selected in the Navigation panel. The results show the devices discovered in the top portion of the Discovery tab, and the status and error messages generated display in the Discovery Status panel in the lower section of the tab. This tab is available to all users with Modeling Your IT Infrastructure Administrator Guide 47

48 Chapter 3: Discover and Model Your Network 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 Advanced Filter Export Filter text box Results list Discovery Status 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: 48 Modeling Your IT Infrastructure Administrator Guide

49 Discovery Console Layout 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 The Modeling tab (Figure 3-6) displays the results and status of the last modeling session. It shows the devices that were modeled in the table in the top portion of the Modeling tab, and the status and error messages generated during the last modeling session in the Modeling Status section in the lower section. Modeling Your IT Infrastructure Administrator Guide 49

50 Chapter 3: Discover and Model Your Network Figure 3-6: Modeling Tab Results set Modeling status 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 Modeling Your IT Infrastructure Administrator Guide

51 Discovery Console Layout Modeling Session Status Bar Figure 3-7: Modeling Session Status Bar The Modeling status bar (Figure 3-7) activates immediately after clicking the Model button on the Discovery tab. This status bar divides the modeling process into four operation phases: Model Creation - Phase 1. The label for this phase turns green while SpectroSERVER processes the data to model. Activation/Layer 3 - Phase 2. The label for this phase turns green while SpectroSERVER maps Layer 3 devices. Layer 2 Mapping - Phase 3. The label for this phase turns green while SpectroSERVER wait for model activation and maps Layer 2 devices. Autoplacement - Phase 4. The label for this phase turns green while SpectroSERVER places the models appearing in the modeling result list. The status and error messages related to each of the four phases appear in the Status box. History Tab The History tab (Figure 3-8) displays the Discovery Time, number of New Devices, number of Lost Devices, and Last Time of Discovery Without Changes for each activation of a configuration selected in the Discovery Navigation tab. Modeling Your IT Infrastructure Administrator Guide 51

52 Chapter 3: Discover and Model Your Network Figure 3-8: The History Tab Discovery Session Results Discovery Status, Discovery Results, Modeling Status tabs Discovery Time. Displays the time and date that a discovery session occurred. View Changes. Click View Changes to display Discovery Results Differences dialog box (Figure 3-9), listing all the devices that were either found or lost during the selected discovery session when compared to the previous discovery session. You can filter on the displayed information, and export it to a file. Figure 3-9: Discovery Results Differences 52 Modeling Your IT Infrastructure Administrator Guide

53 Discovery Console Layout New Devices. Displays the number of devices that did not exist during a previous discovery session, and then were found during the next discovery session for the selected configuration. Lost Devices. Displays the number of devices that existed during a previous discovery session, and then were not found during the next discovery session for the selected configuration. Last Time of Discovery Without Changes. The time and date information for when the selected configuration last ran without any changes is displayed in this column. No time and date information is displayed if changes have occurred each time the configuration has run. The History tab also displays the Discovery Results, Discovery Status, and the Modeling Status tabs in the lower section. Discovery Connection Status Click on the Connection status icon ( Status window (Figure 3-10). ) in the Status bar to display the Discovery Connection When displayed in the context of the Discovery Console, the Connection Status window displays: the SNMP service status - this is required for any discovery and modeling to occur the Web server connection status the Landscape (SpectroSERVER) connection status See the OneClick Console User Guide (5130) for more information on the Connection Status window and the Status bar. Figure 3-10: Discovery Connection Status Window Services and status Connection log for selected service Modeling Your IT Infrastructure Administrator Guide 53

54 Chapter 3: Discover and Model Your Network Define and Activate Configurations You create and modify configurations using the Configuration tab in Contents panel. The following sections provide step-by-step procedures for defining and activating these configurations. For more information, see: Define a Configuration on page 54. Define Modeling Options on page 57 Activate a Discovery Session on page 61 Activate a Modeling Session on page 62 Define a Configuration For SPECTRUM OneClick to determine which of the devices in your network to discover, you must define a configuration. You can define a configuration with or without the context of an element or container in your network (see Launch Discovery on page 40 for information about Discovery context). To Define a Configuration with Context of a Seed Router 1. Select a device from the Universe container in the OneClick Navigation panel you want to use as a seed router in a discovery session. a. Right-click and select Utilities, Discovery. If there are existing configurations that include the IP address of the selected device, the Existing Configuration dialog appears. Select the existing configuration you want to use, or select New. If there are no existing configurations that include the IP address of the selected device, the New Configuration dialog box appears. Use the name provided for the new configuration based on the device name, or enter another name. b. Click OK. The Discovery Console appears. Notice that the Seed Router section of the Configuration tab contains an entry that is the IP address of the selected device. 2. In the Configuration tab of the Discovery Console, specify the discovery configuration fields outlined in Table 3-2. Note that because you launched Discovery in the context of a selected network element, the IP address of the selected device is entered in the Seed Router field for you. 54 Modeling Your IT Infrastructure Administrator Guide

55 Define and Activate Configurations To Define a Configuration Without Context: 1. In the OneClick window, select Tools, Utilities, Discovery. The Discovery Console appears. Continue to step In the Configuration tab of the Discovery Console, specify the discovery configuration fields outlined in Table 3-2. Note that there are two mandatory sections (IP Range and SNMP Information) that you must specify to successfully create a discovery configuration. Table 3-2: Configuration Parameters Field Seed Routers (optional, but recommended for large discovery operations.) IP Boundary List (mandatory) Description Seed routers are a core list of routers that serves as a starting point for Discovery to determine the routed subnets. All routers discovered within the IP boundary list will be treated as seed routers. Note: If you launched Discovery in the context of a selected device, the Seed Router IP field is populated with the IP address of the device. To populate the seed router list, do the following: 1. Build a list of one or more seed router addresses, by entering the addresses in the Seed Router IP address box and clicking Add. 2. In the Discovery Type box, select one of the following: Routers and only local LANs in IP Boundary List. Discovers only the routed subnets within the IP range. Routers only. Discovers only the routing devices within the IP range. Routers and all local LANs. Discovers all subnets routed by the routers discovered in the IP range. 3. In the Max. subnet size box, select the max subnet size that you want to discover. If you launch Discovery in the context of a selected container in the Topology view, the IP Boundary List field is populated with an IP range determined using the network address and network address mask for the container. You can specify additional IP ranges or individual IPs as follows: In the IP list box, specify the IP address(es) you want Discovery to attempt to contact. To specify one address or a range of IP addresses you want to contact, do the following: 1. In the first IP address box, enter a single address or enter the lowest address in the IP range you want discovered then press the TAB key. You can use a wildcard character to input individual IP addresses. For example, entering *.1 could discover: ; ; ; etc. Alternatively, you can click the Import button to import a text file containing IP addresses and/or IP ranges. See Specify IP Addresses on page 44 for information about Static and Dynamic import of IP addresses. The text file must list each IP address (or range) on a single line. IP ranges should be separated by a dash ( - ). For example: In the second IP address box, specify the same single address or specify the highest address in the IP range you want discovered and click Add. Repeat steps 1 through 2 for each IP address or IP range of addresses that you want Discovery to contact. Modeling Your IT Infrastructure Administrator Guide 55

56 Chapter 3: Discover and Model Your Network Table 3-2: Configuration Parameters (Continued) Field SNMP Information (mandatory) Modeling Options (optional) (Admin modeling level privileges required.) Advanced Options Description Specify an ordered list of community strings and profiles for SNMP v1, v2c, and v3. For SNMP v1 and v2, specify the SNMP community strings (passwords) for the devices you want discovered. Discovery, by default, uses public if no other community strings are specified. Alternatively, you can click the Import button to import a text file containing a list of community strings and profiles. The text file must list each community string and profile on a separate line. See Syntax for Imported Community Strings and Profiles on page 47. Note: The following functionality is available only if either Secure Domain Manager or SNMP v3 Proxy are installed: For SNMP v3, specify profiles. Click Profiles to create, edit, delete profiles. See SNMP Information on page 46 for more information on creating profiles. Within the Modeling Options section, you can choose at this time to perform a Discover only operation or a combined discovery and modeling operation. When you choose to discover and model, click Modeling Options to review or modify the modeling configuration. For more information about parameters that define the modeling configuration, see Define Modeling Options on page 57. Click the Advanced Options button if you want to: Define other SNMP Ports in addition to the default port (161) that Discovery uses. This feature is most often used for managed node environments in which proprietary implementations of the SNMP protocols use ports other than the default port of 161. Define IP Exclusion Lists by entering them manually, or Import them from a text file. Modify Discovery Options default settings for ICMP, route tables, throttle, timeout, and retries. A quick description of these options follows: ICMP. This option is enabled by default. When this option is enabled Discovery will use ICMP when discovering devices. If ICMP is enabled, Discovery pings the devices in the ranges/subnets first. The devices that responded to ICMP will then be queried using SNMP. This can greatly reduce the number of SNMP requests, especially when multiple community strings are being used. Route Table. This option is enabled by default. You should use this option only if seed routers are specified in the discovery configuration. When this option is enabled, Discovery finds neighbor routers and routed subnets from the IP route tables. Throttle. This option is set to None by default. Most often this option applies to networks with routing tables containing more than 1,000 entries. If you have networks with routing tables containing over 1,000 entries, you can specify a throttle value (low, medium, or high) to stagger the processing workload by having SPECTRUM pause for one second after reading every 50 entries (high), 100 entries (Medium), or 250 entries (Low). Time-outs. This option is set to 3 by default. Use this option to specify the number of seconds Discovery spends per attempt at contacting an address. Retries. This option is set to 3 by default. Use this option to specify the number of additional attempts Discovery makes after the first attempt times out before establishing contact. Auto Export. Select to not export results, or select export file format sent to location identified on the dialog box. 56 Modeling Your IT Infrastructure Administrator Guide

57 Define and Activate Configurations Table 3-2: Configuration Parameters (Continued) Field Schedule Options Description Click Schedule to select an existing schedule to run the configuration, or create a new schedule. If the configuration is scheduled, the schedule name displays next in the Schedule Options section. 3. In the Configuration tab, do one of the following: Click Discover to activate a discovery session for the discovery configuration specified. Note that the results of the discovery session appear on the Discovery tab of the Discovery Console. Click Save Changes to save changes in the configuration. Note: The Save options as default checkbox, when selected, enables you to apply the most recent changes made to any named Discovery configuration. Close the Discovery. Define Modeling Options The modeling configuration dictates how Discovery models the devices it previously discovered. SPECTRUM OneClick, by default, provides modeling configuration parameters that you can choose to use or modify. At any time, you can review or change the modeling configuration by clicking the Modeling Options button on the Discovery Configuration tab or by clicking the Model button on the Discovery tab. The following procedure provides step-by-step instructions for defining a modeling configuration. Prior to using the following procedure to define a modeling configuration, you must create a discovery configuration, see Define a Configuration on page 54 for more information. You must have privileges to modeling operations. To Define Modeling Options Follow these steps to define a modeling configuration. 1. In the OneClick window, click Utilities, Discovery. The Discovery dialog box appears. 2. In the Open Discovery Configuration dialog box, double-click the name of the discovery configuration for which you want to define a modeling configuration. The Configuration tab appears. 3. Do one of the following: Define a combined discovery and modeling session by selecting Discover and automatically model to SPECTRUM. Click the Modeling Options button to review and/or modify the modeling configuration. The Modeling Configuration dialog box appears. Proceed to Step 4. Define a Modeling session after activating a discovery session by selecting Model. The Modeling Configuration dialog box appears. Proceed to Step 4. Modeling Your IT Infrastructure Administrator Guide 57

58 Chapter 3: Discover and Model Your Network 4. In the Modeling Configuration dialog box, review or modify any of the following fields described in Table 3-3. Table 3-3: Modeling Configuration Fields Field Destination Container Modeling Layout Filter Description The Destination Container is the container that Discovery uses to place new icons in the topology view. Discovery, by default, uses the Universe container as its destination container. If you want to select another container such as a LAN container, do the following: 1. Click Select a Container. A list of containers appears. 2. Select a destination container. In the Modeling Layout section you can dictate how Discovery places and arranges a model in the Universe topology view. Discovery, by default, uses a hierarchical placement and a radial arrangement. To modify the modeling layout that Discovery uses, do the following: 1. In the Placement box, select Flat or Hierarchical. If you select Hierarchical, all Layer 3 devices, LAN containers, and Wide Area Links are placed in the Destination Container. Layer 1 and Layer 2 devices are placed in the proper LAN container (based on IP) under the Destination Container. Note that if Discovery is unable to find the appropriate LAN container for a Layer 1 or 2 devices, these devices are placed in the Destination Container. If you select Flat, Discovery places all devices, including Layer 1 and Layer 2 in the Destination Container (no LAN containers are created). 2. In the Arrangement box, select Grid, Tree, or Radial. Create a filter that excludes the discovery results of specified devices from the modeling process. 58 Modeling Your IT Infrastructure Administrator Guide

59 Define and Activate Configurations Table 3-3: Modeling Configuration Fields (Continued) Field Modeling Options Description In the Modeling Options section, you can choose to enable or disable options that dictate how Discovery models discovered devices. A brief description follows about each of these modeling options: Create Wide Area Link Models. This option is by default enabled. When this option is enabled, Discovery creates a WA_Link model between the wide area linked interfaces of two routers. When this option is disabled, Discovery directly connects the linked interfaces. Create LANs (IP Subnets). This option is by default enabled. When this option is enabled, Discovery uses a LAN container to represent an IP Subnet. Discovery creates the LAN container during the Layer 3 mapping process for any router interface that routes to a local LAN. Remove Empty LANs. This option is by default disabled. When this option is enabled, Discovery destroys any empty LAN containers that were created by the Create LANs (IP Subnets) option. Create (Fanout). This option is by default disabled. When this option is enabled, and when SPECTRUM is unable to make an accurate connection among 3 or more interfaces, Discovery models an Fanout segment to represent the ambiguous connections among these interfaces. However, if the Traffic Resolution protocol option is enabled, SPECTRUM uses network traffic data (IfInOctet and ifoutoctect statistics) to determine connections between interfaces and, in many cases, eliminates the need to model a Fanout. Create Physical Address. This option is by default disabled. When this option is enabled, a physical address model is created for any MAC address that is not associated with any modeled device but was heard by a switch. This option is not recommended. Activation Time. This option, by default, is set to 5 minutes. You can adjust the activation time as desired using the up/down arrows. The activation time value determines the number of minutes Discovery waits for new models to activate before mapping connectivity. When the wait time expires without any new devices activating, connectivity is established insofar as possible, regardless of whether all connections to discovered devices have activated. The minimum activation time is 5 minutes and the maximum time is 15 minutes. Modeling Your IT Infrastructure Administrator Guide 59

60 Chapter 3: Discover and Model Your Network Table 3-3: Modeling Configuration Fields (Continued) Field Protocol Options Filter Options Description The Protocol options enable you to configure options for mapping connectivity between models. Discovery, by default, enables several of these protocol options based on best practices. To disable the default settings or enable additional protocol settings, click Protocol Options. A brief description follows about each of the protocol options: IP Address Table. This option is enabled by default. When this option is disabled, Discovery disables Layer 3 mapping and maps only the Layer 2 connections. In addition, when this option is disabled, Discovery automatically disables the IP Route Tables Protocol option, the Create Wide Area Link Model option, the Create LANs(IPSubnets) option, and the Remove Empty LANs options. IP Route Tables. This option is disabled by default since these tables can be very large and very time-consuming for Discovery to read. When this option is disabled, Discovery 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 should enable the IP Route Tables Protocol option. Source Address Tables. This option is enabled by default. When enabled, Discovery uses the device Source Address table to map layer 2 connectivity. Proprietary Discovery Tables. This option is enabled by default. When this option is enabled, Discovery uses the device Discovery tables when mapping layer 2 connectivity information about the device. Currently this option supports Cisco, Nortel, Cabletron Switch, and Extreme Discovery Protocols. ARP Tables for pingables. This option is enabled by default. When enabled, Discovery uses the ARP table to determine pingable MAC addresses for the connectivity mapping. Spanning Tree. This option is enabled by default. When enabled, Discovery uses the device Spanning Tree Address table (SAT) when mapping layer 2 connectivity information about the device. Traffic Resolution. This option is enabled by default. When enabled, Discovery uses network traffic data to determine connections between interfaces. In many cases, by having Discovery use the traffic data eliminates the need to model Fanout segments. ATM Protocols. This option is disabled by default. When enabled, the ATM discovery runs against all ATM switches in the SpectroSERVER database. See the ATM Circuit Manger User s Guide (3578) for more information. Click Filter Options to access the Advanced Filter dialog box. You can use the Advanced Filter dialog box any time you have a need to exclude certain discovered devices from being modeled. For instance, if you wanted to exclude Discovery from modeling all discovered devices with IP addresses greater than you would: 1. In the Attribute box, select IP address. 2. In the Comparison Type box, select GREATER THAN. 3. In the Attribute Value box, specify the Click Ok. You can also click Show Advanced to create a complex filter criteria that includes a combination of AND/OR clauses. To learn more about how to use these clauses, click the Hints link on the Advanced Filter dialog box or see Filter Results Using Advanced Filter on page 63. Reset Defaults Click Reset Defaults anytime you want Discovery to use the default modeling settings provided with SPECTRUM OneClick. 5. How you accessed the Modeling Configuration dialog box in Step 3 determines whether you can instruct Discovery to: save the modeling parameters you ve specified and activate a modeling 60 Modeling Your IT Infrastructure Administrator Guide

61 Define and Activate Configurations session immediately; or, save the modeling parameters specified and dismiss the dialog box without activating a modeling session. If you clicked Modeling Options on the Discovery Configuration tab to access the Modeling Configuration dialog box, you can do one of the following: Click OK to save all changes made and dismiss the Modeling Configuration dialog box. Discovery will use the last saved modeling parameters upon activating the next modeling session. Click Cancel to dismiss the Modeling Configuration dialog box without saving any recent modeling changes made. Alternatively, if you prefer not to save the changes made, deselect Save options as default. If you clicked Model on the Modeling tab to access the Modeling Configuration dialog box you can do one of the following: Click OK to dismiss the Modeling Configuration dialog box, save the modeling configuration parameters currently specified, and activate a modeling session. Click Cancel to dismiss the Modeling Configuration dialog box without saving any recent modeling changes made. Activate a Discovery Session All users with privileges to discovery operations can activate a discovery session by clicking Discover on either the Configuration tab or Discover tab. In addition, if you have privileges to modeling operations, you can activate a discovery session from the Modeling tab by clicking Discover. The following procedure provides step-by-step instructions about how to activate a discovery session for an existing discovery configuration using the Discovery Console. Prerequisites If you do not have at least one existing discovery configuration created and ready to activate, follow the instructions in Define a Configuration on page 54 prior to using the procedure for activating a discovery session. You should review and make any necessary changes to the discovery configuration prior to using this procedure to activate a discovery session. For more information about reviewing or modifying the discovery configuration, see Define a Configuration on page 54. You must have read/write privileges to discovery operations to activate a discovery session. Procedure Follow these steps to activate a discovery session for an existing discovery configuration: 1. In the SPECTRUM OneClick window, click Tools, Utilities, Discovery. The Open Discovery Configuration dialog box appears. 2. In the Open Discovery Configuration dialog box, double-click the name of the discovery configuration for which you want to activate a discovery session. The Discovery Console appears. Modeling Your IT Infrastructure Administrator Guide 61

62 Chapter 3: Discover and Model Your Network 3. In the Discovery Console, do one of the following: To activate a discovery session and/or combined discovery and modeling session, click the Discovery Configuration tab then click Discover. Discovery activates a discovery session or a combined discovery and modeling session based on the parameters specified on Discovery Configuration tab. The results of the discovery session appear in the Discover tab. The results of the modeling session appear in the Modeling tab. To rediscover an existing discovered or modeled configuration, click the Configuration tab then click Discover to activate a discovery session. All newly discovered results appear in the result list on the Discovery tab. Note that results from this new Discovery session overwrite the results of the previous Discovery session. Activate a Modeling Session If you have privileges to modeling operations, you can activate a modeling session any time after you activate a discovery session by: clicking Model on the Discovery tab; or clicking Discover and automatically model to SPECTRUM on the Configuration tab. The following procedure provides step-by-step instructions to activate a modeling session. Prerequisites You must have activated at least one discovery session of an existing discovery configuration prior to activating a modeling session. For instructions to activate a discovery session, see Activate a Discovery Session on page 61. You should review and make any necessary changes to the modeling configuration prior to using this procedure to activate a modeling session. For more information about reviewing or modifying the modeling configuration, see Define Modeling Options on page 57. If you want to exclude certain devices from being modeled, you should exclude these devices prior to using this procedure to activate a modeling session. For more information, see Exporting a Results List on page 63. You must have sufficient privileges to perform modeling operations. To Activate a Modeling Session Follow these steps to activate a modeling session for an existing discovery configuration: 1. In the SPECTRUM OneClick window, click Tools, Utilities, Open Discovery. The Open Discovery Configuration dialog box appears. 2. In the Open Discovery Configuration dialog box, double-click the name of the discovery configuration for which you want to activate a modeling session. The Discovery Console appears. 3. In the Discovery Console, do one of the following: In the Discovery Configuration tab click the option for Discover and automatically model to Spectrum then click the Discover button. Discovery activates a discovery session then automatically models the discovered devices appearing in the results tab of the Discovery tab. In the Discovery tab click the Model button to activate a modeling session and model the last set of discovered devices appearing in the results list of the Discovery tab. 62 Modeling Your IT Infrastructure Administrator Guide

63 View, Filter, and Export Results Lists View, Filter, and Export Results Lists Each time you activate a discovery or modeling session, Discovery automatically places the results of those sessions in the Discovery tab or the Modeling tab. You can use these results list to select the devices you want to model or export. For more information see these sections: Filter, Sort, Export, Search, and Model Discovery Results on page 48 Filter, Sort, Export, and Search Modeling Results on page 50 Exporting a Results List on page 63 Filter Results Using Advanced Filter on page 63 Activate a Modeling Session on page 62 Exporting a Results List You can easily export a results list by clicking the Export button appearing on the Discovery or Modeling tab. The Export feature accesses the Export table data to file dialog box where you can identify the: Location to save the exported data file. Name for the exported data file. Type of file to use to export the data. Type of file format to save the file. To Export Discovery or Modeling Results Table To export Discovery or Modeling results tables, follow these steps: 1. In Discovery, click the Discovery or Modeling tab. 2. Click Export. The Export table data to file dialog box appears. 3. In the Export table data to file dialog box, specify the following: Save in: specify the location to save the exported data file. File name: specify the name for the exported data file. Files of type: specify the type of file format to use. Save as type: specify the file type you want to use when saving the exported data. 4. Click Save to export the data to specified location, file name, and file format. Filter Results Using Advanced Filter Using the Advanced Filter dialog box, you can create filters with compound clauses to exclude certain entries appearing in the discovery or modeling results list. If you have privileges to both discovery and modeling operations, you can access the Advanced Filter dialog prior to activating a combined discovery and modeling session. If you have privileges to discovery operations only, you can access the Advanced Filter dialog box after initiating a discovery session. Note: Discovery uses the results list on the Discovery tab to determine which devices to model or export. Modeling Your IT Infrastructure Administrator Guide 63

64 Chapter 3: Discover and Model Your Network Prerequisite To filter certain devices from being modeled prior to a discovery session, you must have modeling privileges. To filter devices from being modeled after a discovery session, you must have at least one discovery results list available from an existing Discovery Configuration. To Exclude Devices from Modeling Using the Advance Filter Follow these steps to use the Advanced Filter dialog box to exclude certain devices from modeling (or exporting): Prior to performing a discovery, do the following: 1. In the Discovery Console, select Automatically model to SPECTRUM in the Configuration tab then click the Modeling Options button. The Modeling Configuration dialog box appears. 2. In the Modeling Configuration dialog box, click the Filter Options button. The Advanced Filter dialog box appears. Proceed to step 3 of this procedure. After a discovery session, do the following: 1. In the Discovery Console, click the Discovery tab. 2. In the Discovery tab click the Advanced Filter icon button. The Advanced Filter dialog box appears. Proceed to step 3 of this procedure. Continue: 3. In the Advanced Filter dialog box, specify the following fields to create a single expression filter. Field Attribute Case sensitive box Comparison Type Attribute value Description In the Attribute box, select an attribute of a device to filter. Note: If you choose an alphabetic attribute value, you can choose to either clear (ignore) or check (include) the case sensitivity option. In the Comparison Type box, select the type of comparison to be made against the value specified in the Attribute box. In the Attribute Value box, type or select the desired attribute value to filter. 4. To filter a single expression, click OK. The Advanced Filter option excludes entities in the results list based on the filter parameters specified in step 2. Build a compound clause: 5. To build a compound clause, click Show Advanced. The compound expression box and logical operator buttons appear. 6. Click Add to move the single expression (created in Step 2) to the compound expression box. 7. Click one of the following logical operator buttons to build a compound expression: New And; New Or; or And/Or. 64 Modeling Your IT Infrastructure Administrator Guide

65 After Discovering and Modeling The compound expression is represented in a tree structure grouped by logical operators (AND/OR). Each logical operator in the tree can include any number of attribute criteria nodes and logical operator nodes. For additional information, click Hints. Alternatively, you can create advanced search expressions using prefix notation. 8. Repeat step 5 and step 6 for each compound expression you want to build. 9. Click OK after building the expressions. The Advanced Filter mechanism excludes the entities in the results list based on the compound filter expressions applied. After Discovering and Modeling SPECTRUM does not support all possible network devices with model types and management modules. You will need to perform tasks to modify the Discovery and Modeling results to get the SPECTRUM environment you need to manage your network. After you have successfully used Discovery to discover and model your network, examine and enhance the results. This includes the following activities: Modify device names to accurately reflect the devices on your network. See Device Type Identification on page 115 for ways to do this. Modify attributes for device models and model types using the Attribute Editor. See Modify Model Attributes on page 125 for more information on editing attributes. Create model types for devices not directly supported by SPECTRUM model types and management modules. Refer to the Generic SNMP Device Management User Guide and Toolkit (1316). Import MIBs using the OneClick MIB Tools utility to get updated MIBs for devices, and for features not supported by the MIBs shipped with SPECTRUM. See MIB and Trap Management on page 149 for information on using OneClick MIB Tools. VNM AutoDiscovery Control Settings AutoDiscovery control settings available on the VNMs Information view impact some of the actions that occur during Discovery and Modeling sessions. If you have a Distributed SpectroSERVER (DSS) environment with multiple SpectroSERVERs, you will need to make any changes in these settings to all of your SpectroSERVERs. See AutoDiscovery Control on page 129 for more information on the attributes and settings available. Access VNM AutoDiscovery Control Select the VNM in the Explorer, or in a Universe Topology view. Select the Information tab in the Component Detail panel. Expand the AutoDiscovery Controls subview (Figure 3-11). Modeling Your IT Infrastructure Administrator Guide 65

66 Chapter 3: Discover and Model Your Network Figure 3-11: VNM AutoDiscovery Control Loopback Interfaces and Discovery You can set SPECTRUM to use a loopback interface as a primary agent address, and you can specify which loopback interface to use when modeling devices. See SpectroSERVER Control on page 128 for information on setting loopback interface options for Discovery. 66 Modeling Your IT Infrastructure Administrator Guide

67 Chapter 4: Manual Modeling This chapter walks you through the process of modeling your IT infrastructure manually in the OneClick core topologies: Universe, Global Collections, TopOrg, and World. It includes conceptual information as well as procedural information for performing manual modeling tasks within each topology. In This Chapter When to Model Manually in OneClick on page 67 Manual Modeling in the Universe Topology on page 68 Model Manually in Global Collections Topology on page 80 Manually Modeling in the World Topology View on page 89 Manually Modeling the TopOrg Topology on page 91 When to Model Manually in OneClick In the SPECTRUM OneClick environment, you will most often perform manual modeling tasks when you want to represent one or more previously modeled Universe topology devices in other OneClick topologies such as Global Collections, World, or TopOrg. You may also want to manually model a network device in OneClick after using Discovery in the Universe topology. For instance, the Discovery feature is unable to discover new devices in your network that are temporarily offline or blocking management communication. To resolve this situation, you could choose to rediscover these new devices at a later time using Discovery, or you could manually add them to the Universe topology. Additionally, you might decide to manually model one or more network connections between modeled devices appearing in a Universe or Global Collections view. Finally, you will want to manually model all container icons within a World or TopOrg topology view. 67

68 Chapter 4: Manual Modeling SPECTRUM OneClick Modeling Terminology Table identifies SPECTRUM OneClick modeling terms: Table 4-1: SPECTRUM OneClick Modeling Terms Container Connection Model by IP Address Model by Host Name A container is a graphical icon that you can use to depict a group of modeled devices by network technology such as LAN, Network, ATM, or to represent some other containment concept such as a Department. A connection is a link between two modeled elements in a view. Model by IP Address is a modeling feature that you can use in the Universe, World, or TopOrg topology. This feature enables you to manually model a new device by specifying the device IP address. See To Add a Device Using Create Model by IP Address or Create Model by Host Name on page 71. Model by Host Name is a modeling feature that you can use in the Universe, World, or TopOrg topology. This feature enables you to manually model a new device by specifying the host name for the device. See To Add a Device Using Create Model by IP Address or Create Model by Host Name on page 71 Model by Model Type Model by Model Type is a modeling feature you can use in the Universe, World, or TopOrg topology. This feature enables you to manually model container icons or devices by a model type. See To Add Device Using Create Model by Model Type on page 72. Network Address A network address is the IP address of a device. Manual Modeling in the Universe Topology When you perform manual modeling in the OneClick Universe topology, use the process described here. The following topics provide an overview of this process. Links to the procedures to use in performing the actions described here are listed after these topics. Create or Use an Existing Container Create or use an existing container (LAN, Network, FDDI, etc.) to represent the group of devices you want to model. You can create containers at any topology level to reduce the complexity of your topology views. Containers can effectively help you monitor and manage the health of the devices they represent. Add Devices to Container Add one or more devices to a container using the To Add a Device Using Create Model by IP Address or Create Model by Host Name on page 71, or To Add Device Using Create Model by Model Type on page 72 functions located in the Topology view tool bar (Figure 4-1). 68 Modeling Your IT Infrastructure Administrator Guide

69 Manual Modeling in the Universe Topology Figure 4-1: Create Model by Selections Model by model type Model by IP Address Model by Host Name Create Connections Depict the physical connections (pipes) between the modeled devices using the Start and End Connection options on the right-click menu. Enhance Topology View Place the topology view in edit mode and enhance the topology view by using the tools provided in the Edit mode tool bar. Using these tools you can create lines, shapes, annotations, as well as change the color of the topology view s background. If at any point during the modeling process you determine that you want to remove a modeled element from a view, you can do so by selecting the element and clicking Delete (X). You can also at any time export an image of any Universe topology view to a PNG file for further review and distribution. For additional information about how to perform these manual modeling tasks in the Universe topology, see: Add Containers to Universe Topology Views on page 69 Add Network Devices to Universe Topology Views on page 71 Create Connections (Pipes) Between Modeled Devices on page 76 Delete Modeled Elements from the Universe Topology View on page 75 Export a Universe Topology View on page 76 Add Containers to Universe Topology Views The following procedure describes how to manually add a container (LAN, FDDI, Fanout, etc.) to a Universe topology view by using the Select Model Type dialog box. To Add a Container to the Universe Topology Follow these steps to model a container (LAN, ATM, etc.) in a Universe topology view: 1. In the Explorer tab of the OneClick navigation panel, select the Universe topology view where you want to add a container. The selected topology view appears in the Topology tab of the Contents panel. Modeling Your IT Infrastructure Administrator Guide 69

70 Chapter 4: Manual Modeling 2. In the Topology tab of the Contents panel, click Create a new model by type ( ) in the Topology tab tool bar. The Select Model Type dialog box appears. 3. In the Select Model Type dialog box, click the Container tab. 4. Select the type of container you want to add then click OK. The Create Model of Type dialog box appears. Note: In the Container tab, you can use the Filter text box to filter the container list. For example, type LAN in the Filter text box to filter the container list by all LAN container types. See OneClick Console User Guide (5130) for more information on filtering in OneClick. 5. Depending on the type of container that you are creating, you can specify the parameters listed in the Create Model of Type dialog box shown in Table 4-2: Table 4-2: Create Model of Type Dialog Option Field Name (optional) Security String (optional) Network Address Note: This optional field appears only for Network and LAN containers Subnet Address Note: This optional field appears only for Network and LAN containers Description Specify a name for the new container you are adding. After the container is created, this name appears in the label area under the container icon. If you want to prevent certain users from viewing the contents of this container, you can do so by specifying a security string expression in the Security String text box. For more information, see Provision Access to Modeled Elements ; or, see the security chapter in the OneClick Administrator Guide (5166). If you want to specify one or more of the device IP addresses that this container represents, you can do so by typing the address(es) in the Network Address text box. If you want to identify the device subnet address that this container represents, you can do so by typing the subnet address in the Subnet Address text box. Note: When specified, the subnet address label appears whenever a user points to a container icon (using the mouse) in a topology view. 6. Click OK (in the Create Model of Type dialog box) to create the container and dismiss the Create Model of Type dialog box; or, click Cancel to dismiss the dialog box and cancel the create container operation. When you click OK, SPECTRUM OneClick places the newly created network container in the selected Universe topology view. You can move or enhance the appearance of the recently modeled container, using the Topology view edit mode. For instructions for editing, annotating, or enhancing a modeled element, see Chapter 6, Edit and Enhance Topology Views, on page 105. Add Existing Devices to Container To add modeled network devices to the container, you can double-click the container icon and copy and paste modeled devices from other Universe topology views into this container. Or, you can model new devices in this container by using these topology tool bar functions: Create model by 70 Modeling Your IT Infrastructure Administrator Guide

71 Manual Modeling in the Universe Topology model type, Create model by IP address, or Create model by Host Name. For more information, see Add Network Devices to Universe Topology Views on page 71. Add Network Devices to Universe Topology Views The following procedures describe how to manually add network devices to a Universe topology view using the Topology tool bar Create model by... functions. The best practice for manually adding a device to the OneClick environment is to use either the Create model by IP address or the Create model by Host Name function. The Create model by model type function is considered an advanced function that requires you to have an understanding of how network devices are categorized in the SpectroSERVER modeling catalog. To Add a Device Using Create Model by IP Address or Create Model by Host Name 1. In the Explorer tab of the OneClick navigational panel, navigate to the Universe topology view where you want the new device to appear. The selected Universe topology view appears in the Topology tab of the Contents panel. Tip: If you want to place the new device inside a network group container, double-click the container icon to display the topology view for that container. 2. In the Topology tab tool bar area, click either Create model by IP address or Create Model by Host Name. Either the Create Model by IP Address or the Create Model by Host Name dialog box appears. 3. In the Create Model by IP address or Create Model by Host Name dialog box, specify the device network address or the device host name, and any other optional fields described in Table 4-3: Table 4-3: Create Model by IP Address or Host Name Network Address (mandatory for Model by IP Address) Name (mandatory for Model by Host Name) Community Name (optional) DCM Time-out (optional) DCM Retry Count (optional) Agent port (optional) In the Network Address text box, specify the network address (IP address) for the device you are modeling. In the Name text box, specify the host name for the device you are modeling. If you want SPECTRUM OneClick to communicate with the device you are adding, you must provide the SNMP community string for the device (in the Community Name text box). The DCM (Device Communication Manager) time-out value, by default, is 3000 milliseconds (3 seconds). This option determines how long the SpectroSERVER will wait for a response from the device. The DCM (Device Communication Manager) count value, by default, is 2. This option determines how often the SPECTRUM Server tries to communicate with the device after the DCM time-out value expires. The agent port is the SNMP agent port. The SNMP agent port, by default, is 161. Modeling Your IT Infrastructure Administrator Guide 71

72 Chapter 4: Manual Modeling Table 4-3: Create Model by IP Address or Host Name (Continued) SNMP V2C Enabled (optional) Note: This SNMP option only appears when the SNMP V3 option is installed. SNMP V3 Enabled (optional) Note: This SNMP v3 option only appears when the SNMP V3 option is installed. Discover connections (optional) The SNMP V2C Enabled option lets you specify if the device you are modeling supports SNMPv2c protocols. When this option is selected, SPECTRUM uses SNMPv2c protocols to discover and map the specified device. The SNMP V3 Enabled option enables you to specify if the device you are modeling supports SNMPv3c protocols. When this option is selected, SPECTRUM uses SNMP V3 protocols to discover and model the specified device. For more information about configuring SNMP V3 devices, see the SPECTRUM SNMP V3 User Guide (5124). If you want SPECTRUM OneClick to discover the linked connections (pipes) between the device and other devices, select Discover Connections. 4. Click OK to dismiss the dialog box and create a device icon for the specified network device. Or, click Cancel to dismiss the dialog box and cancel the operation. Click OK to place the newly created device icon in the selected Universe topology view. Tips: To move or enhance the appearance of the recently modeled device icon, click the Edit mode button in the Topology tab tool bar. For instructions for editing, annotating, or enhancing a modeled element, see Chapter 6, Edit and Enhance Topology Views, on page 105. To cut and paste the modeled device icon to another Universe topology view, use the cut and paste functions in the Topology tab tool bar area. To copy or paste the modeled device icon to another topology view other than the Universe topology, use the copy and past functions in the Topology tab tool bar area. To change configuration parameters of a modeled device (for example, community name, polling interval, logging interval, security string, etc.) select the modeled device and change the appropriate setting(s) in the Component Detail panel. To Add Device Using Create Model by Model Type Follow these steps to depict network devices in a view by model type: 1. In the Explorer tab of the OneClick navigational panel, navigate to the Universe topology view where you want the new device to appear. The selected Universe topology view appears in the Topology tab of the Contents panel. Tip: If you want to place the new device inside a container, double-click the container icon to display the topology view for that container. 2. In the Topology tab tool bar area, click the Create a new model by type button. The Select Model Type dialog box appears. 3. In the Select Model Type dialog box, do the following: 72 Modeling Your IT Infrastructure Administrator Guide

73 Manual Modeling in the Universe Topology a. Click the All Model Types tab. b. In the All Model Types tab, select the SpectroSERVER model type of the device you are adding and click OK. The Create Model of Type dialog appears 4. In the Create Model of Type dialog box, specify the following fields that describe the device model type you are modeling. Note that the following table list descriptions for all fields of all model types. Table 4-4: Create Model by Model Type Landscape ID Name Network Address Community Name Security String Serial Number Each Landscape in a network is unique and must be identified by a Unique Landscape Handle (ID). This landscape ID is used to communicate between VNMs. Specify a unique name for the device you are modeling. If you want SPECTRUM OneClick to communicate with the device you are adding, you must provide the IP address for that device. If you want SPECTRUM OneClick to communicate with the device you are adding, you must provide the SNMP community string for the device you are modeling. If you want to prevent some users from viewing this device, you can do so by specifying a security string in Security String text box. For further information, see Provision Access to Modeled Elements on page 31; or the OneClick Administration Guide (5166). If you want to identify the serial number for the device you are modeling, you can do so in the Serial Number text box. Poll Interval By default, SPECTRUM OneClick polls modeled devices for status updates every 60 seconds (or for some model types every 3000 seconds). You can increase or decrease the polling interval by changing the value in the Port Interval text box. If you increase the time between polling intervals, you will use less bandwidth for management traffic, but you will receive device status updates less frequently. If you decrease the time between polling intervals, you will have more frequent updates of device status, but you will use more bandwidth. One way to achieve both goals is to use the default polling interval (60 seconds) for the router and edit the polling interval for all other devices to 600 seconds. Log Ratio (optional) Creation Author Manufacturer The log ratio defines how many times SPECTRUM polls devices for updates before logging the results. By default the log ratio is 10 (SPECTRUM logs the polling results after it polls the device every 10th time). In the Creation Author text box, you can specify the name of the author that is modeling this managed device. In the Manufacturer text box, you can specify the manufacturer name of the managed device you are modeling. Southbound Gateway-specific Note: For more information about Soouthbound Gateway settings, see the Southbound Gateway Toolkit Guide (2246). Unique ID The Unique Identifier is a composite of up to 6 variable data items (1-6). The final unique identified string is composed as follows: <1>_<2>_<3>_<4>_<5>_<6> If one of the unique identifier components is not provided, it is not included within the composite unique identifier. Modeling Your IT Infrastructure Administrator Guide 73

74 Chapter 4: Manual Modeling Table 4-4: Create Model by Model Type (Continued) Manager Name Event Model Prefix If the name of the third-party application does not apply in the list, choose Default. When this attribute is set on the EventAdmin, all EventModels contained with this EventAdmin will inherit this attribute. This field is prepended to the EventModel Name for all of the Event Models contained by this EventAdmin. It provides a way to ensure consistent naming prefixes for all EventModels associated with a particular EventAdmin. This is useful when sorting or filtering various SPECTRUM applications. Dialup_Link-specific Note: For more information about Dialup Link settings, see the Non-Persistent Connections Manager User Guide (2246). Dialup Link Type Dialup Protocol Type Activation Grace Period Deactivation Grace Period Active Time Until Yellow Active Time Until Orange Active Time Until Red The functional type of the Dialup Link. Possible types are Backup (DBL), Primary (PODL), and Bandwidth (BODL). The protocol type that will be used on the Dialup Link. Possible protocol types are Analog, Switch, ISDN, and FrameRelay. This field enables you to specify the time allowed, in minutes, for the secondary link to become active after a primary link failure. If this grace period expires before the secondary link is active, then a red alarm is generated. This field is only used by DBL-type link models. The default setting is 3 minutes. This field enables you to specify the time allowed, in minutes, for an active secondary link to deactivate after the failed primary link reactivates. If the secondary link is still active after this grace period expires, then a yellow alarm is generated. This field is only used by DBL-type Link models. The default setting is 3 minutes. This field enables you to specify the number of hours a backup link can be active before a yellow alarm is generated. This field enables you to specify the number of hours a backup link can be active before an orange alarm is generated. This field enables you to specify the number of hours a backup link can be active before an red alarm is generated. 5. Click OK (in the Create Model by Type dialog box) to dismiss the dialog box and to create a modeled device icon for the specified device. Or, click Cancel to dismiss the dialog box and cancel the model by type operation. Tips: When you click OK, SPECTRUM OneClick places the newly created device icon in the selected Universe topology view. To move or enhance the appearance of the recently modeled device icon, click the Edit mode button in the Topology tab tool bar. For instructions for editing, annotating, or enhancing a modeled element, see Chapter 6, Edit and Enhance Topology Views, on page 105. To cut and paste the modeled device icon to another Universe topology view, use the cut and paste functions in the Topology tab tool bar area. Or use the copy and paste functions to copy and paste modeled icon to another topology - World, TopOrg, or Global Collection. 74 Modeling Your IT Infrastructure Administrator Guide

75 Manual Modeling in the Universe Topology Delete Modeled Elements from the Universe Topology View You can delete modeled elements from the Universe topology view, in addition to cutting them and pasting them into another topology view. To Delete a Modeled Element from View Follow these steps to delete a modeled element from a Universe topology view. 1. In the Universe topology view, do one of the following: Right-click a modeled element, and select Remove. Select a modeled element and click Delete from view in the Topology tab tool bar area. 2. The Confirm Removal dialog box appears. Click Yes to finish deleting the element, or No to cancel. Figure 4-2: Topology Tool Bar - Delete From View Delete from view Cut Modeled Element from Universe Topology View When you cut a modeled element from a topology view, SPECTRUM OneClick removes the model from the view and places it into the Lost and Found view. You can at any time completely remove the modeled element from the Lost and Found view by deleting it from the List Tab of the Lost and Found Contents panel. To Cut a Modeled Element from a View Follow these steps to delete a modeled element from a Universe topology view: 1. In the Universe topology view, do one of the following: Right-click a modeled element, and select Cut. The deleted modeled element appears in the Lost and Found view. Select a modeled element and click Cut ( )in the Topology tab tool bar area. The cut modeled element and appears in the Lost and Found view. To Delete Modeled Element from Lost and Found Follow these steps to delete a modeled element from the Lost and Found view: 1. In the Explorer tab of the navigation panel, click Lost and Found. 2. In the Lost and Found Contents panel, click the List tab. 3. In the List tab, select the elements you want to remove then do one of the following: Modeling Your IT Infrastructure Administrator Guide 75

76 Chapter 4: Manual Modeling Select Delete from the right-click menu. Select Delete ( )from the tool bar. Export a Universe Topology View You can export any Universe topology view to a PNG file format. For more information, see the following procedure. See the OneClick Console User Guide (5130) for more information on exporting views and table data. To Create and Export a Topology View 1. In the Explorer tab of the navigation panel, navigate to the Universe topology view that you want to export. The selected topology view appears in the Topology tab of the Contents panel. 2. In the Topology tab, click the Export icon button in the Topology tool bar area. The Save As PNG dialog box appears. 3. In the Save As PNG dialog box, specify the name and location for the file then click OK. Create Connections (Pipes) Between Modeled Devices In SPECTRUM OneClick, you can manually create three types of connections between modeled devices: Resolved connection (for a fully-resolved connection). A resolved connection is when two devices are connected at the port level. For example, Port-A of device one is connected to Port- B of device two. To learn how to create a port-to-port connection, see Create a Resolved Connection (both device ports known) on page 78. Partially-resolved connection. A partially-resolved connection is when only one port is known between two devices. You typically create this type of connection when you know only the port of one modeled device. For example, device-one is connected to Port-A of device-two. When you manually model a partially-resolved connection, SPECTRUM attempts to resolve the port connection of the other device. If SPECTRUM succeeds, it will represent the connection as fully resolved connection. You can later determine if the connection is fully-resolved by clicking the link within that view and viewing the Link Information tab on the Component Detail panel. To learn how to create a partially-resolved connection, see Create a Partially-resolved Connection (one device port known) on page 79. Unresolved connection. An unresolved connection is when two modeled devices (or containers) are not connected in any way at the port level. For example, container-a is connected to container-b. If you have a DSS (Distributed SpectroSERVER) environment, and any of the connections or pipes you are creating span between two or more devices managed by different SpectroSERVERs, you need to make sure that the Live Pipes attribute for each VNM is set to Enable. See Live Pipes on page 132 for how to set this attribute and more information about using Live Pipes in a DSS. 76 Modeling Your IT Infrastructure Administrator Guide

77 Manual Modeling in the Universe Topology Static Connection Color Representation After Modeling Initially after modeling a connection the color of the connection is silver or gold. Note that gold appears for resolved or partially-resolved connections. Silver appears for all unresolved connections. Dynamic Link Status - Partial or Fully-Resolved Connections After you create a partial or fully-resolved connection between two modeled elements, you can monitor the status of that connection by enabling the connection (pipe) as a Live Pipe. The color of live pipes in the Universe topology views indicate status information about the connection. For example, good connection conditions are green; bad connection conditions are red, or disabled live-pipe connections are gold. A live pipe shows a combined status condition for fully-resolved connections (two ports). The connection having the most severe condition (lost, etc.) determines the pipe s color. A live pipe can generate an alarm when one or both the links it represents goes down. For more information about enabling a live pipe connection, see Enable or Disable a Live Link (applies to full or partial resolved connections) on page 80. Removing Connections from a Universe Topology View You can at any time delete a connection between two modeled elements in the Universe topology view by right-clicking the pipe and selecting Delete. When a pipe is deleted, SPECTRUM OneClick removes all of its associations. If the pipe represents more than one port connection, SPECTRUM OneClick prompts you to confirm the deletion. Automatic Recreation of Pipes Pipes are automatically recreated anytime you copy and paste a set of previously connected modeled icons to another Universe topology view. If you delete one of the connected modeled icons from the view, the pipe is erased. If you later copy that device from the Lost and Found view to the original topology view, SPECTRUM OneClick automatically recreates the connection between the two modeled devices. Lock Manually Resolved Connections You can preserve any manually configured resolved connection between two modeled devices by locking that connection. Note that OneClick Discovery process will not remove any resolved connection that is locked. You can lock or unlock a resolved connection by right-clicking the connection and selecting Lock Connection. For more information, Lock and Unlock Resolved Connections on page 79. For step-by-step instructions for manually creating connections between modeled elements in a Universe topology view, see the following the sections: Create an Unresolved Connection Between Modeled Elements on page 78 Create a Resolved Connection (both device ports known) on page 78 Create a Partially-resolved Connection (one device port known) on page 79 Lock and Unlock Resolved Connections on page 79 Enable or Disable a Live Link (applies to full or partial resolved connections) on page 80 Modeling Your IT Infrastructure Administrator Guide 77

78 Chapter 4: Manual Modeling Create an Unresolved Connection Between Modeled Elements When you do not know the port connections between two modeled elements that you want to connect, you can create an unresolved connection. When you create an unresolved connection between two modeled elements in the Universe topology view, the pipe representing the connection are silver and you are prevented from enabling that connection as a Live Pipe. However, after you create an unresolved connection between two modeled elements in a Universe topology view, SPECTRUM automatically attempts to resolve the connection between the two modeled elements. If SPECTRUM succeeds in resolving the connection, the pipe representing the connection are gold and behaves as a resolved connection. You can then proactively monitor the status of that resolved connection by right-clicking the pipe and selecting Live Pipe. Note: If SPECTRUM is unable to detect at least one port-level connection between two devices, the pipe in the topology view remains as an unresolved connection (silver). You cannot enable Live Pipe on an unresolved connection. To Create an Unresolved Connection Follow these steps to create an unresolved connection: 1. Designate the starting point of a connection. In a Universe topology view, right-click any modeled element (device or container) select Start Connection. 2. Designate the endpoint of the connection. In a Universe topology view, right-click the modeled element (device or element) and select Connect with <starting point address>. SPECTRUM OneClick models an unresolved silver colored pipe between the two modeled devices. Note that if the connection (between the modeled elements) spans two separate views, an off-page reference icon appears in the view. Create a Resolved Connection (both device ports known) When you know the ports of both modeled devices, you can create a port-to-port (resolved) connection. To Create a Resolved Connection Between Two Interfaces 1. Designate the starting point of a connection by following these steps: a. In a Universe topology view, select a modeled device (such as a switch or router) that contains port interfaces. b. In the Components Detail panel, click the Interfaces tab. c. In the Interfaces tab, right-click a port row and select Start Connection. 2. Designate the endpoint of the connection by following these steps: a. In a Universe topology view, select a modeled device (such as a switch or router) that contains port interfaces. b. In the Components Detail panel, click the Interfaces tab. c. In the Interfaces tab, right-click a port description and select Connect with <starting point port address>. 78 Modeling Your IT Infrastructure Administrator Guide

79 Manual Modeling in the Universe Topology SPECTRUM OneClick creates a resolved (gold-colored) pipe between the two modeled icons. Note that if the modeled devices are in separate views, an off-page reference icon appears in the view. Tip: To monitor the link status of this connection, right-click the connection and select Enable/ Disable Live Links. For more information, see Dynamic Link Status - Partial or Fully-Resolved Connections on page 77 or Enable or Disable a Live Link (applies to full or partial resolved connections) on page 80. Create a Partially-resolved Connection (one device port known) When you know only the device port of one of the two modeled devices that you want to connect, you can create a partially-resolved connection. To Create partially-resolved connection 1. Designate the starting point of a connection by following these steps: a. In a Universe topology view, select a modeled device (such as a switch or router) that contains port interfaces. b. In the Component Details panel, click the Interfaces tab. c. In the Interfaces tab, right-click a port row and select Start Connection. 2. Designate the endpoint of the connection. In a Universe topology view, right-click any modeled element (device or container) with unknown port address and select Connect with <starting point modeled port address>. SPECTRUM OneClick models a partially-resolved (gold) pipe between these two modeled devices. Note that if the connection between the modeled devices spans two separate views, an off-page reference icon appears in the view. Tips: SPECTRUM OneClick will automatically attempt to locate the unknown device port. You can verify whether SPECTRUM locates this device port by clicking the link and viewing the Link Information tab in the Component Details panel. To monitor the link status of this connection, right-click the connection and select Enable/ Disable Live Links. For more information, see Dynamic Link Status - Partial or Fully- Resolved Connections on page 77 or Enable or Disable a Live Link (applies to full or partial resolved connections) on page 80. Lock and Unlock Resolved Connections In SPECTRUM OneClick, you can preserve a resolved connection between two modeled devices by locking that connection. When you lock a connection, Discovery will not delete the connection. To Lock and Unlock Resolved Connections 1. In a Universe topology view, right-click the connection you want to lock and select Lock Connection. A Lock Connection dialog box appears. 2. In the Lock Connection dialog box, check the connections you want to Lock and click OK. Tip: To unlock a locked connection, right-click the locked connection, select Lock Connection, and deselect Locked Connection. Modeling Your IT Infrastructure Administrator Guide 79

80 Chapter 4: Manual Modeling Enable or Disable a Live Link (applies to full or partial resolved connections) You can monitor the link status of any resolved connection depicted in the Universe topology views by enabling Live Links. When you enable a live link on a partial or fully-resolved connection, you are able to monitor the port connections at either end of the modeled devices. The status condition of a live link displays through colors (red for critical, green for good, etc.). Additionally, if a port-connection within a live link goes down, you can view alarm information about that connection in the Alarm tab of the Contents panel. The following procedures describe how to enable and disable a live link for a partial or fullyresolved connection. For more information about creating a partial or fully-resolved link, see Create a Resolved Connection (both device ports known) on page 78 and Create a Partiallyresolved Connection (one device port known) on page 79. To Enable a Live Link Connection Follow these steps to enable or disable a live link on a partial or fully-resolved connection: 1. Right-click the connection you want to enable as a live link and select Live Link. The Enable/ Disable Live Link dialog box appears. 2. In the Enable/Disable Live Link dialog box, check the connections you want to make live then click OK. SPECTRUM indicates the link is live by changing the gold pipe to green (good condition) or red (bad condition). To Disable a Live Link Connection Follow these steps to enable or disable a live pipe: 1. Right-click the live link connection you want to disable. The Enable/Disable Live Link dialog box appears. 2. In the Enable/Disable Live Link dialog box, clear the checkboxes for the connections you want to disable then click OK. SPECTRUM indicates the live link is disabled by changing the color of the connection to gold. Model Manually in Global Collections Topology In the Global Collection topology, you can create a collection of any modeled elements previously modeled in one or more Universe topology views. When you create a collection within the Global Collections topology, you must provide a name for that collection and define its members. You can choose to define the members of a collection by either specifying a search criteria or using the copy/paste or add functionality offered in the topology view menus and tool bars. Dynamic Membership - Use Search Criteria When you use a search criteria to define the members of a collection, the members of that collection are considered dynamic. They remain in the collection only as long as they meet the specified search criteria. When a modeled element no longer meets the original search criteria specified, SPECTRUM automatically removes that modeled element from the collection the next time the collection is updated either manually or at the next scheduled interval. The default period 80 Modeling Your IT Infrastructure Administrator Guide

81 Model Manually in Global Collections Topology for automatic scheduled collection updates is 24 hours. At any time, you can choose to redefine the members in a dynamic collection by editing the specified search criteria. Static Membership - Use Copy/Cut/Paste When you use copy/paste or add functions to define members of a collection, the members of that collection are considered static. Static members always remain in a collection until you decide to manually remove them. Manage Connections Between Modeled Elements (Members) The connections between modeled elements in a Global Collection topology view exhibit the same behavior and functionality as the connections between modeled elements in a Universe topology view. In the Global Collections view, you can choose to create partial and fully-resolved connections, or unresolved connections (links, pipes). You can monitor the status of any resolved connection using Live Links. For more information about creating connections in the Universe or Global Collections views, see Create Connections (Pipes) Between Modeled Devices on page 76. Update Modeled Elements in Collections SPECTRUM OneClick updates all modeled elements in a Global Collection view as often as the Search Interval specifies. For instance, the search interval, by default, updates the dynamic members within a collection every twenty-four hours. Generate Reports on Collections You can generate reports on a global collection using the Report Manager module. By using the Report Manager module with the OneClick Global Collections topology, you can at any time generate a single report about any one collection. For more information about running reports, see the Report Manager User Guide (5158). Note: The Report Manager module is not included in the SPECTRUM core product line. This module must be purchased separately. Recommended Process for Defining Collections When defining a collection of modeled elements in the Global Collection topology, consider following these steps: Step 1: Create a new collection. A new collection remains empty until you define its members. Step 2: Define dynamic members or, when necessary, define static members. Step 3: Edit members in a collection as needed. For dynamic members in a collection, you can redefine the search criteria. For static members, you can delete, copy/paste, or add members in a collection. Step 4: Setup a Global Collection Hierarchy if you want to organize your collections into folders and sub-folders. Step 5: Delete collections as needed. Note that since the modeled elements within a global collection represent copies of modeled elements from the Universe topology, the Delete operation removes only the specified global collection and the copies of the modeled elements that collection represents. Modeling Your IT Infrastructure Administrator Guide 81

82 Chapter 4: Manual Modeling Global Collections Modeling Tasks The following sections define how to perform various modeling tasks when defining collections in the Global Collection topology. Additionally, the last section defines how you can setup a Global Collections Hierarchy. Define a New Collection on page 82 To Create an Empty Collection on page 85. To Create a New Dynamic Collection (Explorer tab) on page 85 To Create a New Static Collection on page 86 Edit an Existing Collection on page 87 To Add Static Members to an Existing Collection on page 87 To Edit Dynamic Members in Existing Collection on page 88 To Remove Static Members from an Existing Collection on page 88 Create a Global Collection Hierarchy on page 89 For more information about why you want to create global collections, see Global Collections Topology on page 21. Define a New Collection To create a new collection within the Global Collections topology, you use the Create Global Collections dialog box (Figure 4-3). If you are unsure of the type of collection you want to create, you can create an empty collection by providing only the name of the collection. After you create the collection, you can add static members, dynamic members, or both to the collection. Figure 4-3: Create Collection Dialog Box You must provide a name for the collection you want to create. A description and a security string are optional. The Advanced button (optional) enables you to immediately define dynamic members through a search criteria. If you know ahead of time you are creating a new collection of dynamic members, you can click the Advanced button in the Create Collections dialog box to immediately define the dynamic members using a search criteria. The Advanced button launches the Advanced Collection Options dialog box as shown in Figure Modeling Your IT Infrastructure Administrator Guide

83 Model Manually in Global Collections Topology Figure 4-4: Advanced Collections Options Alternatively you can create a dynamic collection by using the Search options offered in the Locater tab of the OneClick navigation panel (as shown in Figure ). Figure 4-5: Locater Tab - Search- Create Collection Create a collection from the Locater tab. If you want to create a collection of static members on the fly you can do so by right-clicking any modeled element in the Universe topology and selecting Add To, Collection. This feature launches the Select Collection dialog (Figure 4-6) where you can specify to which collection to add the modeled devices or create a new collection of the devices by clicking Create Collection as shown in figure Figure. Modeling Your IT Infrastructure Administrator Guide 83

84 Chapter 4: Manual Modeling Figure 4-6: Select Collections Dialog Box - Create Collection The Create button enables you to create a new collection based on the modeled elements selected. The following procedures describe how to create an empty collection, a new dynamic collection, and a new static collection. For more information about adding static or dynamic members to an existing collection, or about removing and redefining existing members in a collection, see Edit an Existing Collection on page Modeling Your IT Infrastructure Administrator Guide

85 Model Manually in Global Collections Topology To Create an Empty Collection 1. In the Explorer tab of the OneClick navigation panel, right-click Global Collections and select Create Collection. The Create Collection dialog box appears. 2. In the Create Collection dialog box, define the fields listed in Table 4-5: Table 4-5: Create New Collection Name (required) Description (optional) Security string (optional) Enter a unique name for the collection you are creating. Specify a description of the collection you are creating. If you want to prevent certain users from viewing the contents of this collection, you can specify a security string expression. For more information, see Provision Access to Modeled Elements on page 31 or see the security chapter in the OneClick Administrator User Guide (5166). 3. Click OK (in the Create Collection dialog box) to dismiss the dialog box and create the Global Collection The new collection appears in the navigation panel under the Global Collection node. Click Cancel to dismiss the dialog box and cancel the creation of the collection. Tip: You can edit an existing collection s description, security parameter, or search criteria by right-clicking the collection in the navigation panel and selecting Edit Collection. To Create a New Dynamic Collection (Explorer tab) 1. In the Explorer tab of OneClick navigation panel, right-click Global Collections and select Create Collection. The Create Collection dialog box appears. 2. In the Create Collection dialog box, define the fields described in Table Click Advanced (in the Create Collections dialog box) to launch the Advanced Collections Options dialog box. 4. In the Advanced Collections Options dialog box, specify any of the fields described in Table 4-6 to create a single search expression. Table 4-6: Advanced Collections Options Attribute Comparison Attribute Value Select the specific attribute you want to find from a predefined list of commonlyused attributes. If you cannot find the attribute you want to specify from the predefined list of attributes, click Attribute to specify the Model type (device, port, or other) and its associated attribute that you want to find. Select the type of comparison to be made against the value specified in the Attribute box. Type the desired attribute value to search. 5. Depending on whether you want to conduct a compound search clause or a single search clause do one of the following: To conduct a search based on a single expression, click OK and proceed to Step 6. Modeling Your IT Infrastructure Administrator Guide 85

86 Chapter 4: Manual Modeling To conduct a search based on a compound clause, do the following to build a compound search clause: a. Click Show Advanced. The compound expression box and logical operator buttons appear. b. Click Add to move the single expression (created in Step 4) to the compound expression box. c. Click one of the following logical operator buttons to build a compound expression: New And; New Or; or And/Or. Note: The compound expression is represented in a tree structure grouped by logical operators (AND/OR). Each logical operator in the tree can include any number of attribute criteria nodes and logical operator nodes. For additional information, click Hints in the Advanced Collections dialog box. d. Repeat Steps 4 through 5 for each compound search expression you want to build. 6. In the Update search field, specify how often you want SPECTRUM OneClick to conduct a search to update the members defined in the collection. 7. Click Landscapes to identify which Landscapes you want Search to include when searching models to populate a collection. 8. Click OK after building the search expressions. The Advanced Search mechanism locates and places a copy of all matching modeled elements (previously defined in the Universe topology) in the collection. To Create a New Static Collection To create a new collection of static members on the fly from the Universe topology, follow these steps: 1. In the Universe topology, do one of the following to designate the modeled elements you want to define in a collection: Single modeled element selection. In the Universe navigation panel, right-click a modeled element and select Add To, Collections. The Select Collections dialog box appears. Alternatively, you can right-click any single modeled element in any Universe topology view and select Add To, Collections. The Select Collections dialog box appears. Multiple modeled element selection. To multi-select modeled elements in a Universe topology view, do the following: a. Press and hold the SHIFT key and individually select the modeled elements. b. While the SHIFT key is pressed, right-click the last selected modeled element and select Add To, Collections. The Select Collections dialog box appears. Alternatively, you can select one or more modeled elements in the List tab and add them to a new collection. 2. In the Select Collections dialog box, click Create. The Create Collections dialog box appears. 86 Modeling Your IT Infrastructure Administrator Guide

87 Model Manually in Global Collections Topology 3. In the Create Collection dialog box, specify a name for the collection and any other optional fields defined in Table 4-7. Table 4-7: Create New Collection Name (required) Description (optional) Security string (optional) Advanced button (optional) Enter a unique name for the collection you are creating. Specify a description of the collection you are creating. If you want to prevent certain users from viewing the contents of this collection, you can specify a security string expression. For more information, see Provision Access to Modeled Elements on page 31 or see the security chapter in the OneClick Administrator User Guide (5166). Click Advanced only if you want to change the default Landscape setting where this collection will be created. 4. Click OK (in the Create Collection dialog box) to dismiss the dialog box and create the collection, it appears in the navigation panel under Global Collections. Click Cancel to dismiss the dialog box and cancel the creation of the collection. You can edit an existing collection s description, security parameter or search criteria by rightclicking the collection in the navigation panel and selecting Edit Collection. Edit an Existing Collection You can edit any existing collection in the Global Collections topology by adding static members, editing a search criteria to redefine dynamic members, or removing one or more static members. The following procedures provide instructions for adding static members, redefining dynamic members, and removing static members To Add Static Members to an Existing Collection Follow these steps to add static members to an existing collection: 1. In the Universe topology, do one of the following to designate the modeled elements you want to add to a collection: Single modeled element selection. In the Universe navigation panel, right-click a modeled element and select Add To, Collections. The Select Collections dialog box appears. Alternatively, you can right-click any single modeled element in any Universe topology view and select Add To, Collections. The Select Collections dialog box appears. Multiple modeled element selection. To multi-select modeled elements in a Universe topology view, do the following: a. Press and hold the SHIFT key and individually select the modeled elements. b. While the SHIFT key is pressed, right-click the last selected modeled element and select Add To, Collections. The Select Collections dialog box appears. Alternatively, you can multi-select one or more modeled elements in the List tab and add them to an existing collection. 2. In the Select Collections dialog box, select the name of the collection where you want to add the modeled elements then click OK. Modeling Your IT Infrastructure Administrator Guide 87

88 Chapter 4: Manual Modeling To Edit Dynamic Members in Existing Collection Follow these steps to edit dynamic members in an existing collection: 1. In the Explorer tab of the OneClick navigation panel, navigate to the Global Collections node. 2. Right-click on the collection to edit; select Edit Collection; the Edit Collection dialog box appears. 3. In the Edit Collection dialog box, edit any of the following fields:. Table 4-8: Edit Collection Description (optional) Security string (optional) Advanced button Specify a description of the collection you are creating. If you want to prevent certain users from viewing the contents of this collection, you can specify a security string expression. For more information, see Provision Access to Modeled Elements on page 31 or see the OneClick Administrator User Guide (5166). Click the Advanced button to edit the: Search criteria specified for this collection. For instructions for creating a search criteria, see Table 4-6. Update option that determines how often SPECTRUM updates the collection. 4. Click OK (in the Edit collection dialog box) to dismiss the dialog box and save the changes made to this collection. Click Cancel to dismiss the dialog box without saving the changes made. To Remove Static Members from an Existing Collection Follow these steps to remove static members in an existing collection: 1. Do one of the following: In the Global Collections navigation tree, right-click on the static member you want to remove from the collection, select Remove from the menu. Select the Global Collection you are modifying in the navigation tree. Go to the Topology or List view for that collection. Right-click on the device you want to remove and select Remove. Select the Global Collection you are modifying in the navigation tree. Go to the Topology view for that collection. Select the device you want to remove from the collection. Click Remove ( )in the Topology tool bar. 2. SPECTRUM OneClick displays a dialog box confirming that you want to proceed with the deletion. Click Yes to continue and remove the device from the collection, or click No to cancel the operation. When you click Yes, the Remove operation removes the element from the collection but does not destroy the modeled element. If the modeled element exists in other topologies, it will continue to exist in those topologies. If the modeled element does not exist in any other topology, it will be placed in the Lost and Found and later destroyed. Note: If you attempt to remove a dynamic member from a collection, an error message appears informing you that the selected member was added via a search criteria. To remove the dynamic member you must redefine the search criteria. 88 Modeling Your IT Infrastructure Administrator Guide

89 Manually Modeling in the World Topology View Create a Global Collection Hierarchy If you intend to organize your Global Collections into folders and sub-folders, you must set up the OneClick navigation panel with a Global Collection Hierarchy. In this Global Collection Hierarchy, you can create multiple levels of folders to represent previously defined global collections. To learn how to set up a Global Collection Hierarchy, see the following procedure. Procedure: Create a Collection Hierarchy 1. In the Explorer tab of the OneClick navigation panel, right-click Global Collections Hierarchy node and select New Folder. The New Folder dialog box appears. 2. In the New Folder dialog box, enter a descriptive folder name. The folder appears in the Global Collection Hierarchy tree. 3. In the Global Collection Hierarchy tree, perform any of the following tasks: Build additional top-level folders. Repeat Steps 1 and 2. Build one or more sub-folders. To create a sub-folder, right-click a top-level folder and select New Folder. Populate folder at any level. To populate a folder with one or more collections, follow these steps: a. Right-click the folder and select Add Collection. The Add Collections dialog box appears. b. In the Add Collection dialog box, select the name of the collection you want to add and click OK. Note: The Add Collection dialog box represents the list of collections previously created in the Global Collection topology. For more information about creating collections, see Define a New Collection on page 82. Manually Modeling in the World Topology View Anytime you want to represent your network geographically you can do so by creating a World topology view. In a World topology view, you can model several layers of container views depicting your network locations. For example, you may want to create container views of your network infrastructure from a national or regional level all the way down to an individual room containing network equipment. Modeling Your IT Infrastructure Administrator Guide 89

90 Chapter 4: Manual Modeling Recommended Process for Modeling Locations When modeling multiple containers representing locations within your network infrastructure, use this process: Step 1: Create top-level location views. From the World topology node, you can begin depicting the top-level view of any network location by modeling one of the following top-level containers: Building Site Region Country Step2: Create one or more sub-level location views. Depending on the top-level container modeled, you can then depict one or more sub-level containers (see Table ). Table 4-9: Top level and sub-level containers If the top-level container is a: Building Site Region Country You can model one any of these subcontainers: Floors, Rooms, Sections Building Building or site Region, building, or site. Step 3: Populate a room container view with modeled devices. After you have created a room container view, you can populate that view with modeled devices. The following procedures define how to create a top-level and sub-level location view, as well as how to populate a room container view with modeled devices. To Define Top-level or Sub-level Location View Follow these steps to create a top-level location view: 1. In the Explorer tab of the OneClick navigation panel, do one of the following: To define a top-level location view. Click the World topology node to display the World topology view in the Topology tab of the Contents panel. To define a sub-level location view. Click one of the top-level view folders appearing under the World topology node. The World topology view for that folder appears in the Topology tab of the Contents panel. 2. In the Topology tab tool bar area, click the Create a new Model by Type. The Select Model Type dialog appears. 3. In the Container tab of the Select Model Type dialog box, select a container type that best describes the network location you are depicting then click OK. The Create Model of Type dialog box appears. 90 Modeling Your IT Infrastructure Administrator Guide

91 Manually Modeling the TopOrg Topology 4. In the Name text box, specify a name that best describes the network location. 5. If you want to secure this view from certain users, specify a security string in the Security String text box. For more information about securing views, see Provision Access to Modeled Elements on page Click OK. The following occurs: The named icon container appears in the top-level (or sub-level) view of the World topology. The named folder representing the container appears in the navigation panel under the World topology node. Tip: To move the container icon or annotate this view further, click the Edit mode button in the tool bar area of the World topology view. For more information about using the Editor features, see Chapter 6, Edit and Enhance Topology Views, on page 105. To Populate a Room Container View with Modeled Devices Follow these steps to populate a room container view with modeled devices: 1. In a Universe topology view, copy the modeled devices that you want to appear in a World topology view. 2. In the World topology view, navigate to a room container type view. 3. In the room container-type view, paste the modeled devices. Tip: You should always model devices in the Universe topology view; then, copy and paste these devices to the World topology view. Alternatively, you can use the Create Model by IP or Create Model by Type option to manually model devices in a World topology view. Importantly, however, we do not recommend this alternative approach since the Universe topology views represent the connectivity views of your network. Tip: If you determine you want to model new devices directly in the World topology, you can choose to use either the Create Model by IP option or Create Model by Type option. For instructions on using these options, see To Add Device Using Create Model by Model Type on page 72 and To Add a Device Using Create Model by IP Address or Create Model by Host Name on page 71. To move the container icon or annotate the view, click the Edit mode button in the tool bar area of the World topology view. Manually Modeling the TopOrg Topology You can manually model your network in the TopOrg topology anytime you want to organize infrastructure models by organizational units or by services. For example, you can create a TopOrg topology view depicting devices that are essential for supporting a network service such as service. You could also depict services by department or individual responsibility. When populating a TopOrg topology view, you should copy the modeled elements from a Universe topology view and paste them in a TopOrg topology view. Alternatively, you can use the Create Model by IP or Create Model by Type option to manually model devices in a TopOrg topology view. However, we do not recommend this alternative approach since the Universe topology views represent the connectivity views of your network. Modeling Your IT Infrastructure Administrator Guide 91

92 Chapter 4: Manual Modeling Model Services in the TopOrg Topology Within the TopOrg topology it is possible to create multiple levels of containers representing organizations or individuals responsible for tracking the performance of mission critical services in your IT infrastructure. When modeling multiple organizational containers in the TopOrg topology, consider following this process: Step 1: Create one or more layers of ownership/responsibility. Using the Model by Type dialog box, depict one or more containers representing a department, individual, customer, or enterprise that is supported by a network service or that is responsible for tracking the performance of a network service. Step 2: Populate Service_Owns container with supporting devices. Populate the Service_Owns container with the modeled devices supporting the network service. You can populate these containers by copying/pasting modeled devices from the Universe topology to the TopOrg topology, or by defining new devices using the Create Model by IP Address dialog box. The following procedures describe how to create organizational and Service_Owns containers as well as how to populate a service_owns type container with modeled devices. To Define Organizational and Service_Owns Containers Follow these steps to define service related organizational views in the TopOrg topology: 1. In the Explorer tab of the OneClick navigation panel, click the TopOrg topology node to display the TopOrg topology view in the Topology tab of the Contents panel. 2. In the Topology tab tool bar area, click the Create Model by Type. The Select Model Type dialog box appears. 3. Within the Containers tab of the Select Model Type dialog box, select a container type that best describes the organization you are depicting then click OK. The Create Model of Type dialog box appears. 4. In the Name text box, specify a name that best describes the organization that is responsible for tracking the performance of the network services or is supported by these services. 5. If you want to secure this view from certain users, you can specify a security string in the Security String text box. For more information about securing views, see Provision Access to Modeled Elements on page Click OK. The following occurs: The named container icon appears in the top-level view of the TopOrg topology. The named folder representing the container appears in the navigation panel under the TopOrg topology node. 7. Repeat Steps 2 through 4 for each organizational or Service_Owns container you want to depict in the TopOrg topology. 92 Modeling Your IT Infrastructure Administrator Guide

93 Manually Modeling the TopOrg Topology To Populate Service_Owns Type Containers Follow these steps to populate Service_Owns containers with modeled devices in the TopOrg topology: 1. In a Universe topology view, copy the modeled devices that you want to appear in a TopOrg topology view. 2. In the TopOrg topology view, navigate to a Service_Owns container view. 3. In the Service_Owns container view, paste the modeled devices. Tip: The best practice is to always model devices in the Universe topology view; then, copy and paste these devices to the TopOrg topology view. Alternatively, you can use the Create Model by IP or Create Model by Type option to manually model devices in a TopOrg topology view. However, we do not recommend this alternative approach since the Universe topology views represent the connectivity views of your network. Tip: If you determine you want to model new devices in the TopOrg topology, you can choose to use either the Create Model by IP option or Create Model by Type option. For instructions on using these options, see To Add Device Using Create Model by Model Type on page 72 and To Add a Device Using Create Model by IP Address or Create Model by Host Name on page 71. To move the container icon or annotate the view, click the Edit mode button in the tool bar area of the World topology view. For more information about editing a topology view, see Edit and Enhance Topology Views on page 105. Modeling Your IT Infrastructure Administrator Guide 93

94 Chapter 4: Manual Modeling 94 Modeling Your IT Infrastructure Administrator Guide

95 Chapter 5: Modeled Device and Interface Configurations After you have discovered and modeled devices on your network, you can use SPECTRUM s reconfiguration functionality to keep the modeled devices up-to-date. SPECTRUM offers choices in how it can respond when it detects changes in a device s configuration. Also, to increase reliability in contacting devices on the network, SPECTRUM can use more than one IP address to contact a device as a form of redundant communication paths. In This Chapter Device and Interface Threshold Settings on page 95 Update Device Interface and Connection Information on page 98 Redundant Connections between SPECTRUM and Modeled Devices on page 102 Device and Interface Threshold Settings SPECTRUM ships with several device and interface alarms configured with three variables to define the alarm and reset conditions. These variables are: Threshold Setting a threshold setting above which an alarm condition can exist. Reset Level a reset level below which an existing threshold alarm condition is automatically cleared. SPECTRUM does not generate subsequent alarms for the parameter until the value falls below the reset level. Allowed Threshold Violation Duration setting that specifies how long the parameter can be greater than the threshold setting, in seconds, before SPECTRUM generates an alarm. You can configure device thresholds so that an alarm is generated if a given threshold is exceeded for a certain duration. Note: In order to configure device and interface threshold alarm settings, the Device Threshold attribute on the SpectroSERVER must be enabled. See SpectroSERVER Control on page 128 for more information. You can turn off individual device or interface thresholds by setting the threshold and reset level variables equal to zero. 95

96 Chapter 5: Modeled Device and Interface Configurations Device Threshold Settings You can configure device thresholds so that an alarm is generated if a given threshold is exceeded for a certain duration. No further alarms will be generated for a threshold violation until its monitored value falls below the reset threshold. To disable a threshold from generating alarms, set the threshold value to zero. The device threshold settings available are % CPU Utilization and % Memory Utilization. You can access these OneClick settings in the following ways: The Device Thresholds subview in the Information tab for the selected device. The Attribute Editor, Thresholds, Device Thresholds grouping. When using the Attribute Editor to set the Device Threshold attributes, the Allowed Threshold Violation Duration attribute is not available, and the default value of 300 seconds (five minutes) is used. See Thresholds on page 148 for information about accessing Device Threshold settings using the Attribute Editor. Example: % CPU Utilization Default Settings This example illustrates how the default % CPU Utilization Threshold settings work together to trigger an alarm. The example is illustrated in Figure 5-1. The default setting for this alarm setting are as follows: % CPU Utilization Threshold = 85% % CPU Utilization Reset = 70% Allow Threshold Violation Duration = 300 seconds Using the default settings, when the device s % CPU Utilization parameter exceeds the threshold setting of 85% at time Y, SPECTRUM begins the 300 second Allowed Threshold Duration timer. The % CPU Utilization does not fall below the reset value of 70% for the duration of the timer. At time= Y+5 minutes SPECTRUM triggers a % CPU Utilization alarm for the device. SPECTRUM will not generate another % CPU Utilization alarm until this alarm is cleared manually or automatically. At time=y+12 minutes the device s % CPU Utilization falls below the reset value of 70%. SPECTRUM clears the % CPU Utilization alarm for the device. 96 Modeling Your IT Infrastructure Administrator Guide

97 Device and Interface Threshold Settings Figure 5-1: Threshold Setting Examples % CPU Utilization 85% % CPU Utilization Threshold violated Allowed Threshold Violation Duration timer starts. Allowed Threshold Violation Duration (300 sec) % CPU Utilization Alarm generated % CPU Utilization falls below reset level, alarm cleared. 70% Y Y+5 Y+12 Time (min) % CPU Utilization 85% % CPU Utilization Threshold violated Allowed Threshold Violation Duration timer starts. Allowed Threshold Violation Duration (300 sec) % CPU Utilization Alarm generated % CPU Utilization falls below reset level, alarm cleared. 70% Y Y+5 Y+12 Time (min) % CPU Utilization 85% % CPU Utilization Threshold violated Allowed Threshold Violation Duration timer starts. Allowed Threshold Violation Duration (300 sec) % CPU Utilization falls below reset level prior to Allowed Threshold Violation Duration ends; No alarm issued 70% Y Time (min) % CPU Utilization Threshold = 85% % CPU Utilization Reset = 70% % CPU Utilization (Actual) Modeling Your IT Infrastructure Administrator Guide 97

98 Chapter 5: Modeled Device and Interface Configurations Interface Threshold Settings The following interface thresholds parameters are available: % Utilization Threshold Defines the level of port capacity used that triggers an alarm condition for a port. Packet Rate Threshold (packets/sec) Defines the number of packets per second that triggers an alarm condition for a port. % Error Rate Threshold Defines the error rate on a port that triggers an alarm condition. % Discarded Threshold Defines the percentage of discarded packets on a port that triggers an alarm condition. Each of these attributes has a reset value and Allowed Threshold Violation Duration timer attribute setting. You can access these OneClick settings in the following ways: The Interface Thresholds subview in the Information tab for the selected device interface. The Attribute Editor, Thresholds, Interface Thresholds grouping. See the OneClick Console User Guide (5130) for information on accessing the Interface Thresholds subview for a selected device interface. See Thresholds on page 148 for information about accessing Device Threshold settings using the Attribute Editor. Update Device Interface and Connection Information SPECTRUM can perform automatic discovery and mapping of a device s interfaces and connections based on the following events and conditions: A change in the number of configured interfaces on a device. When a device sends a LINK up trap. When SPECTRUM reconfigures a modeled device. OneClick administrators can also manually update this information on a modeled device. See the OneClick Console Guide (5130) for information on viewing a device s interface, sub-interface, and connection information. Automatically Updating Device Interface and Connection Information You can use the following attributes to configure SPECTRUM to automatically update a device s interface and connection information. Automatically Reconfigure Interfaces SPECTRUM will automatically discover and model a device s interfaces after the number of configured interfaces for a device changes when the Automatically Reconfigure Interfaces attribute is set to Yes. The updated interface information appears in the device s Interfaces view. Discover Connections After Link-Up Events SPECTRUM will automatically discover and map a model s connections one poll interval after it receives a LINK up trap from a device when the Discover Connections After Link-Up Events attribute is set to Yes. This delay allows the device to fully reconfigure its related SNMP tables 98 Modeling Your IT Infrastructure Administrator Guide

99 Update Device Interface and Connection Information before SPECTRUM reads them. The Poll Interval setting for the device appears in the Information view, SPECTRUM Modeling Information subview. See SNMP Communications Attributes on page 147 for information about the Poll Interval setting. Special Considerations for Flapping Interfaces A flapping interface is one that is constantly going up and down, most likely due to a problem on the device. The SPECTRUM intelligence associated with setting Device Discovery After Link-Up Events to Yes excludes LinkUp traps from flapping interfaces, so the stream of LinkUp traps from a flapping interface does not interfere with a LinkUp trap for another interface on the same device. This allows the connection discovery action to run as expected. When this intelligence detects a flapping interface, a minor alarm is generated on the related device. After a default interval of 10 minutes without receiving a trap from the flapping interface, the alarm is cleared. The default settings used to identify and track flapping interfaces are configured using Event Rules associated with Events 0x220002, 0x The default settings are as follows: An Event Sequence Rule on Event 0x220002, which generates Event 0x if a LinkUp trap is received and is followed by a LinkDown trap from the same interface within 60 seconds. An Event Rate Window Rule on Event 0x220006, which generates Event 0x if 15 0x events are generated within 5 minutes (300 seconds). Event 0x generates a Minor alarm on the device. An Event Pair Rule on Event 0x which generates Event 0x if Event 0x is not followed by Event 0x within 10 minutes (600 seconds). Event 0x clears the Minor alarm generated by Event 0x The default values will generate an alarm after 15 LinkUp/Down trap pairs are received and clear the alarm 10 minutes after the last LinkUp/Down Trap pair is received. These settings are user configurable, enabling you to define flapping interface Event thresholds to meet your needs. The rules listed above are specified in the <$SPECROOT>/SS/CsVendor/IETF/EventDisp file. To manually edit the files, see the Event Configuration Files Guide (5070) for information about SPECTRUM events and event rules. See the Event Configuration Editor User Guide (2260) for using the ECEditor to change the event rules associated with events 0x and 0x Automatically Reconfigure Interfaces When this attribute is set to Yes, SPECTRUM monitors the device for a change in the number of configured interfaces. If it detects a change, SPECTRUM automatically updates the device model to reflect the interface changes. Create Sub-Interfaces When this attribute is set to Yes, and the modeled device supports RFC 1573, SPECTRUM models the device s sub-interfaces. SPECTRUM differentiates physical and logical interfaces, creating subinterfaces using the logical interface information gathered from the device. A sub-interface appears in the device s Interfaces tab, nested beneath the logical interface it is configured on. Discovery After Reconfigure When this attribute is set to Yes, SPECTRUM rediscovers a device s connections whenever the device model is reconfigured. This includes when an interface reconfiguration or a manual device reconfiguration occurs. Modeling Your IT Infrastructure Administrator Guide 99

100 Chapter 5: Modeled Device and Interface Configurations Topologically Relocate Model When this attribute is set to Yes, SPECTRUM determines whether or not a device model needs to be moved to a different topology during a discovery, and moves the device if necessary, based on updated connection mapping. Manually Updating Device Interface and Connection Information You can manually initiate an interface reconfiguration and connection discovery using the functionality located in the Tools, Reconfigure menu and in the device Information view, Reconfiguration subview. Reconfigure Model When you activate a Reconfigure Model action SPECTRUM determines which interfaces on the device exist, and updates the device s interface modeling. The Reconfigure Model action is composed of the activities listed in Table 5-1. Table 5-1: What Happens During a Reconfigure Model Action Activity Device Discovery Verify the Device Type Verify proper MIB support Interface reconfiguration Reevaluate Model name Verifying CPU and Memory Normalize Source Verifying Serial Number Verifying Trunk membership Verifying Device Family What It Does Perform a discovery of the device to gather modeling information. Checks the current Device Type attribute value. Performs a Reconfigure SNMP MIBs action. Determines which interfaces exist on a device, and updates the device modeling as needed. Check the Model Naming Order setting on the VNM, and determine if the device model needs to be changed. Verifies which attribute to use for gathering device CPU and memory usage information Verifies the device serial number if available, and updates the device model if necessary. Checks to see if the device s interfaces are members of a 802.3ad trunk. Checks the Device Family value that Network Configuration Manager uses to groups devices by vendor. Discover Connections When you activate a Discover Connections action SPECTRUM performs a discovery on the device to update and remap the device model connection information. Rediscover SNMP MIBs When a device model is created, SPECTRUM automatically creates models for each of the major and minor applications the device supports. Click Reconfigure SNMP MIBs to retrieve application support information from the device. The application models for the device are updated with any changes. 100 Modeling Your IT Infrastructure Administrator Guide

101 Update Device Interface and Connection Information Rename Interface Models Use this function to update a device s interface model names after changing the device s Interface Model Name Suffix attribute. Using this command forces SPECTRUM to rename the interface models using the current value of the interface model name suffix (ifname, ifalias, ifdescr, or ifindex) Reevaluate Model Name Click Reevaluate Model Name and SPECTRUM determines whether or not to change the device s model name based on the VNM Model Naming Order setting for the VNM managing the device. See SpectroSERVER Control on page 128 for information about the VNM Model Naming Order setting. Access Interface and Connection Update Controls You can access to the interface and connection update controls described in this section in the following OneClick menus, views, or tools listed in Table 5-2: Table 5-2: OneClick Access to Interface and Connection Update Controls Attribute Tools, Reconfiguration Menu Reconfiguration Subview Attribute Editor, Change Management Group Automatically Reconfigure Interfaces X X Discover Connections After Link Up Events X X Discovery After Reconfigure X X Create Sub-Interfaces X Topologically Relocate Model X X Reconfigure Model X X Discover Connections X X Rediscover SNMP MIBs X X Rename Interface Models X X Reevaluate Model Name X X Tools, Reconfiguration Menu The Tools, Reconfiguration menu provides quick access to reconfiguration actions you can perform on a selected device model. Reconfiguration Subview and Advanced Subview The Reconfiguration subview provides access to attributes that control when SPECTRUM updates a device s interface, connection, topology information. You can also manually reconfigure a device and discover a device s connections from this subview. The Advanced section of the Reconfiguration subview provides access to individual model reconfiguration functions that occur as part of the Reconfigure Model function. In some cases, you Modeling Your IT Infrastructure Administrator Guide 101

102 Chapter 5: Modeled Device and Interface Configurations may want to perform these actions separately instead of performing an overall Reconfigure Model action. Attribute Editor Change Management Group Use the Change Management attribute grouping to access some of the interface and connection update parameters for a large number of models or modeled devices. See Change Management on page 142 for information on using the Attribute Editor to configure some of these settings on multiple models or model types at once. Redundant Connections between SPECTRUM and Modeled Devices If a modeled device is configured with a pool of IP addresses available to it for use in communicating on the network, SPECTRUM can use these IP addresses to create redundant connectivity with that device. If the redundancy feature is enabled on a device and SPECTRUM cannot reach the device using the designated primary address, SPECTRUM attempts to reestablish contact using the list of available IP addresses. Redundancy Preferred Addresses List A device that supports the SPECTRUM redundancy feature has a Redundancy Preferred Addresses list containing the device s interface IP addresses that is created when the router is originally modeled. SPECTRUM uses this list in determining redundant connectivity to the device. Devices have a primary address that is determined when the device is modeled. The SPECTRUM modeling process includes a loopback functionality. If the VNM is configured to use the loopback feature, the first valid loopback address detected for the device is used as device model s primary address. Device Primary Address The primary address for a device is by default the IP address assigned to the device for network communications. You can change the primary address in OneClick if the network address for the device changes. If SPECTRUM cannot contact the device using its primary address, it attempts to contact the device using the first IP address in the Redundancy Preferred Addresses List. See Loopback Interfaces and Discovery on page 66 and SpectroSERVER Control on page 128 for information about how a device s loopback interface is used to model its primary address, and how to activate this feature on the VNM managing your devices. You can change a device s primary address and the IP addresses listed in the Redundancy Preferred Addresses list using the IP Redundancy subview. Note: Do not include any shared addresses in the Redundancy Preferred Addresses list. If a shared address is included in the Redundancy Preferred Addresses list, it is possible that SPECTRUM may attempt connecting to Device_A when Device_A s primary address is down using the shared address, but Device_B is now using that address. IP Redundancy Subview The IP Redundancy subview displays attributes and settings SPECTRUM uses to create and monitor redundant communication paths to the device. Access the IP Redundancy subview by selecting a 102 Modeling Your IT Infrastructure Administrator Guide

103 Redundant Connections between SPECTRUM and Modeled Devices device that supports this feature in either the Navigation, List, or Topology view, then selecting the Information tab in the Component Detail panel. The IP Redundancy subview appears in the Information tab. Enable Redundancy When this attribute is set to Yes, SPECTRUM will use the addresses in a modeled device s Redundancy Preferred Addresses list, if it exists, to contact a device when the primary address is not available. Generate Redundancy Alarms When this attribute is set to Yes, SPECTRUM generates an alarm when a device cannot be contacted using its primary address. Primary Address This is the primary address SPECTRUM uses to communicate with the modeled device. You can change the primary address to another address in the device s preferred address list using the following procedures. To Change a Device s Primary Address 1. Click set located next to the Primary Address attribute in the IP Redundancy subview. The Preferred Address dialog appears. 2. The Primary Address field displays the current primary address for the device. 3. Select an IP address from the Redundancy Preferred Addresses list on the left side of the dialog. 4. Click Primary below the preferred address list. The IP address you selected now appears in the Primary Address field. The IP address that was the primary address now appears in the Preferred Address list. 5. Click OK to change the Primary address setting. The dialog closes. To Add an Address to a Device s Redundancy Preferred Addresses List 1. Click set located next to the Primary Address attribute in the IP Redundancy subview. The Preferred Address dialog appears. 2. Click Add below the Redundancy Preferred Address list. 3. Enter the IP address that you want to add to the list in the Add IP Address dialog, and click add. The IP address appears in the Redundancy Preferred Address List. Redundancy Excluded Addresses List The Redundancy Excluded Addresses list displays IP addresses that a device cannot use for communicating on the network. You can manually add or remove IP addresses to or from a device s Redundancy Excluded Addresses list. Modeling Your IT Infrastructure Administrator Guide 103

104 Chapter 5: Modeled Device and Interface Configurations To Add an Address to a Device s Redundancy Excluded Addresses List 1. Click set located next to the Primary Address attribute in the IP Redundancy subview. The Preferred Address dialog appears. 2. Click Add below the Redundancy Excluded Address list. 3. Enter the IP address that you want to add to the list in the Add IP Address dialog, and click add. The IP address appears in the Redundancy Excluded Address List. You can also select an address in the Preferred list and move it to the Excluded list by clicking the single right arrow located between the two lists. You can move an address from the Excluded list to the Preferred list by selecting the address in the Excluded list and then clicking the single left arrow located between the two lists. 104 Modeling Your IT Infrastructure Administrator Guide

105 Chapter 6: Edit and Enhance Topology Views This chapter describes how you can enhance OneClick topology views by using the tools provided in the Edit mode tool bar. It also describes how you can edit model device attributes using OneClick s Attribute Editor and Search features. In This Chapter After reading this chapter, you will understand how you can enhance OneClick topology views using the Edit mode features as well as how to modify device attributes using the Attribute Editor features. This chapter defines the Edit mode and Attribute Editor features in the following sections: Topology View Edit Mode Preferences on page 106 Use Edit Mode to Enhance Topology Views on page 106 How to Enhance a Topology View on page 110 Commonly Used Terms Table 6-1 identifies commonly used terms for performing the editing tasks described in this chapter. Table 6-1: Commonly Used Topology Editing Terms Edit mode Drawing tools Search Attribute Editor Device attributes Edit mode refers to the condition you place a view in when you want to edit its appearance. When you place a view into Edit mode, you automatically prevent other users from editing that view. Drawing tools refer to the Edit mode options you can use to draw lines, rectangles, ellipses, or text boxes. After you create these items in a view, you can later apply styles or colors to them. Search refers to the search features available in the Locater tab of the OneClick navigation panel. Attribute Editor enables you to change attributes configured at the device level. Device attributes refer to the configuration settings written to a device or interface. 105

106 Chapter 6: Edit and Enhance Topology Views Topology View Edit Mode Preferences You can set the following Topology view Edit Mode preferences using the Set Preferences dialog box: Show grid - displays a grid on the Topology view background when the Topology view is in Edit mode. Grid spacing - set the size of the grid squares using the value displayed using the Show grid option. Decreasing the value decreases the size of the grid squares, while increasing the value increases the size of the grid squares. Snap to grid - enables snap-to-grid while the topology view is in Edit mode, making it easier to align modeled device icons in the topology view. You can also set these preferences in the Background Editor dialog box (see Accessing the Edit Mode Feature on page 107). Use Edit Mode to Enhance Topology Views You can enhance any topology view using the Edit mode feature in the Topology view. You can make the following enhancements: Change the background characteristics of a view Add lines, rectangles, or ellipses to a view Edit the placement of modeled elements in a view Change font characteristics in a view Figure 6-1 illustrates the appearance of an enhanced topology view. 106 Modeling Your IT Infrastructure Administrator Guide

107 Use Edit Mode to Enhance Topology Views Figure 6-1: Enhanced Topology View Background image Shape Annotations Text Annotation Multi-User Considerations Note that OneClick topology view enhancements are shared across all users. Also, when you edit a view using the Edit mode button in a Topology tab tool bar area, SPECTRUM automatically prevents all other users from editing that view. The following sections describe how to access and use the Edit mode features : Accessing the Edit Mode Feature on page 107 Edit Mode Tool Bar on page 109 How to Enhance a Topology View on page 110 Accessing the Edit Mode Feature You can access the Edit mode tool bar by clicking the Edit mode option button in the Topology tab tool bar (Figure 6-2). Figure 6-2: Edit Mode Button Edit mode option - locks current topology view for edit. Modeling Your IT Infrastructure Administrator Guide 107

108 Chapter 6: Edit and Enhance Topology Views When you click the OneClick Edit mode option, the following changes occur: The current topology view automatically locks for edit, thereby preventing all other users from editing this view. The Edit mode tool bar appears providing you access to all the editing tools necessary to enhance the appearance of a topology view (Figure 6-3). Figure 6-3: Edit Mode Tool Bar The Save option unlocks all views for edit. Edit mode tool bar After you place a view into Edit mode, you can click Save to save changes that you make and exit the Edit mode. Any user that does not have privileges to edit a topology view will not have access the Edit mode tool bar options. 108 Modeling Your IT Infrastructure Administrator Guide

109 Use Edit Mode to Enhance Topology Views Edit Mode Tool Bar Table 6-2 describes the editing tools that you can access and use from the Edit mode tool bar. Table 6-2: OneClick s Annotation Tool bar Editing tool Name Description Front Properties Opens the Select Font dialog box for the selected text annotation. Choose a font family, style, and size from the respective columns in the Select Font dialog box. You can also choose the text foreground and background color and whether or not to show the text background (this is disabled by default). Shape Color Opens the Select Shape Color dialog box for the selected annotation. Select a shape color in the Select Color dialog box. Line Weight Sets the line weight for lines, ellipses, and rectangles. Line Style Sets the style for lines, ellipses, and rectangles. Group and Ungroup Selection Groups and ungroups selected modeled elements in a view. Rectangle Tool, Ellipse Tool, and Line Tool Text Box Draws rectangles, ellipses, and lines. Click and hold the rectangle or ellipse tool bar button for additional tools for each shape. Creates a text box used to enter text. Topology Background Changes topology background characteristics (edit mode grid, grid spacing and color, background color, image, and size). See Enhancing Topology Background on page 112 for more information. Modeling Your IT Infrastructure Administrator Guide 109

110 Chapter 6: Edit and Enhance Topology Views How to Enhance a Topology View The following sections describe various editing tasks to enhance OneClick topology views: Add Shapes, Lines, or Text to a View on page 110 Change Shapes, Lines, and Text Characteristics on page 111 Enhancing Topology Background on page 112 Group and Ungroup Items in a View on page 113 Bringing Items to Front or Sending Items to Back on page 114 Note: The following procedures assume the topology view has been placed in Edit mode. Proportionally Resize Model Icons You can resize model icons displayed in the Topology view as follows: To Resize a Model Icon 1. Select the model icon that you want to resize in the Topology view. A green box appears around the icon. 2. Click on one of the corners of the green box and drag the icon to make it either bigger or smaller. The icon device size changes proportionally automatically. 3. Deselect the icon when it is at the desired size. 4. Click Save to save your changes. Add Shapes, Lines, or Text to a View Use the following procedures to add a rectangle, ellipse, line, or text to a topology view. To Add a Rectangle or Ellipse Follow these steps to add a rectangle or an ellipse to a topology view. 1. Click and hold Rectangle or Ellipse ( ) in the Edit mode tool bar until a menu appears, then select the desired style for the shape. The pointer changes from an arrow to a crosshair when hovering over the background area of the topology view. 2. In the topology view, click and drag the pointer starting at the desired upper left corner of the shape and ending at the lower right-hand corner of the shape. 3. Release the mouse button and the shape appears in the view, behind any models or pipes. To Add a Line to a View 1. Click Line ( ) in the Edit mode tool bar,. The pointer changes from an arrow to a crosshair in the background area of the topology view (but on top of any other shapes or text that already exists). 2. In the topology view, click and drag the pointer from where you want the line to begin until where you would like the line to end. 110 Modeling Your IT Infrastructure Administrator Guide

111 Use Edit Mode to Enhance Topology Views 3. Release the mouse button and the line appears in the view, behind any models or pipes. To Add Text (text box) to a View 1. In the Edit mode tool bar, click the Text button. The pointer changes from an arrow to a crosshair pointer. 2. In the topology view, click where you want the text box to begin. A text box appears. 3. In the text box, type the desired text. 4. To exit the text box, click outside the text box. The text boundaries of the text box disappear and the text is placed in the background of the topology view. Change Shapes, Lines, and Text Characteristics The following procedures describe how you can apply different font properties to text, colors to shapes, or line weights to lines. Tip: The best practice for setting properties for shapes, lines or text, is to do so before adding (or drawing) these elements in a view. To Change Text Font Properties Follow these steps to change the font properties of user-specified text. 1. In the topology view, click the text you want to change then click the Font Properties button in the Edit mode tool bar. The Select Font dialog box appears. 2. In the Select Font dialog box, select the desired font family, style, size, foreground color, and background color. Tip: The preview pane at the bottom of the dialog box changes to reflect the font properties selected. 3. Click OK (in the Select Font dialog box) to set the font properties for the text you selected in Step 1. To Apply Color to Shapes or Lines Follow these steps to change the color of a selected shape or line. 1. In the topology view, click the shape or line that you want to edit then click the Shape Color button in the Edit mode tool bar. The Select Color dialog box appears. 2. In the Select Color dialog box, click the Swatches tab. Select a desired color from the color palette then click OK to apply the color to the shape selected in Step 1. Tip: In the Swatches tab, you can preview the colors chosen from the color palette in the Preview pane. If you selected and previewed multiple colors, the colors you have chosen appear in the Recent color grid for easy re-selection. Tip: Click the RGB tab to customize a standard color chosen on the Swatches tab. On the RGB tab you can customize a standard color by adding more or less red, green, blue colors. Tip: Click the HSB tab to customize the Hue, Saturation, and Brightness settings associated with standard color chosen on the Swatches tab. On the HSB tab, you can use the slider control to increase or decrease the settings associated with Red, Green, and Blue colors. Or, you can individually change the color settings associated with the Hue, Saturation, and Brightness. Note Modeling Your IT Infrastructure Administrator Guide 111

112 Chapter 6: Edit and Enhance Topology Views that when you change the color settings in the HSB tab, the color settings in the RGB tab are updated respectively. To Apply Line Weights Follow these steps to change the line style of a selected line. 1. In the topology view, click the line that you want to edit then click the Line Weight button in the Edit mode tool bar. A line weight menu appears. 2. In the line weight menu, click the line weight desired. The selected line weight is applied to the line. Enhancing Topology Background You can change a topology s background color, add a background image, or change the size of the background by using the Background Editor (Figure 6-4) feature. Figure 6-4: Background Editor SPECTRUM OneClick supports multiple type of images you can display in the background (buildings, equipment racks, countries, etc.) All images available in the Background Editor dialog box support a PNG image format. 112 Modeling Your IT Infrastructure Administrator Guide

113 Use Edit Mode to Enhance Topology Views To Change Background Characteristics Use these steps to change the background characteristics of a topology view: 1. Click Background Editor ( ) in the Edit mode tool bar. The Background Editor dialog box appears. 2. In the Background Editor dialog box, perform any of the tasks described in Table 6-3: Table 6-3: Background Editor Tasks Task Change the background type (color or image) Change background size Instructions 1. In the Background Type box specify whether you want to change the color or image. 2. Click the Browse button to preview the color or images. The Select Color dialog box appears for color background type edit. The Select Topology Background dialog box appears for Image background edit. 3. Select the desired image or color and click OK. A preview of the selected item appears within the background editor dialog box. The selected image or color appears at the lower left edge of the preview pane. You can change the background size of the topology view to create additional room for modeling network entities. To do this, in the Background Size text box, specify a pixel value for the Width and Height of the topology panel. 3. Click OK to apply the changes to the background or click Cancel to cancel the background edit operation. When you click OK, the background view immediately reflects the changes made. Group and Ungroup Items in a View You can group or ungroup items in any OneClick topology view. Grouping items within a view enables you to edit, move, copy/paste, or delete items as one group. Ungrouping a set of groupeditems within a view enables you to edit and move the items individually. One of the most common group-type operation you may perform within a topology view is to group text (annotations) with modeled devices. The following procedures provide step-by-step instructions for grouping and ungrouping items in a view. To Group Items in a View Follow these steps to group one or more selected items in a view: 1. In a topology view, hold down the shift key and select the items you want to represent as a group. 2. In the Edit mode tool bar, click the Group button to represent the selected items in the view as a single group. To Ungroup Grouped Items in a View Follow these steps to ungroup a set of grouped-items in a view: 1. In the topology view, click any one of the grouped-items to select the entire group. 2. In the Edit mode tool bar, click the Ungroup button to ungroup the items in the group. Modeling Your IT Infrastructure Administrator Guide 113

114 Chapter 6: Edit and Enhance Topology Views Bringing Items to Front or Sending Items to Back You can send items to the back of a view or bring items to the front of a view relative to other items within that view. In the topology view, right-click the item and select one of the following: Bring to Front moves the item to the front of the view relative to other items in the view. Send to Back moves the item to the back of the view relative to other items in the view. 114 Modeling Your IT Infrastructure Administrator Guide

115 Chapter 7: Device Type Identification In This Chapter This chapter describes how to use SPECTRUM OneClick Device Type Identification (DTI) to view, create, and edit the Device Type Identification entries. SPECTRUM uses the DTI entries to initialize the Device Type attribute on device models during the Discovery, Modeling, and Create Device processes. Information about using DTI is presented in the following sections: Device Type Identification in OneClick Launch Device Type Identification Distributed SpectroSERVER Support on page 121 To Modify an Existing DTI Entry on page 118 Customization Considerations on page 123 The Device Type attribute (0x23000e) is a text string used to identify a modeled device. SPECTRUM provides the ability to search, filter, and report on device models using the Device Type attribute, providing a fine level of granularity when managing your network infrastructure. Device Type Identification in OneClick Device Type Identification allows you to modify the Device Type attribute values for device model types. You can create DTI entries for devices not directly supported in OneClick by default. DTI supports a distributed SpectroSERVER environment, thus providing consistent device model identification across a distributed deployment. Launch Device Type Identification Launch Device Type Identification using the following methods: Launch DTI from the OneClick main menu: Tools>Utilities>Device Type Identification. Launch DTI with the context of a device selected in either the Explorer, List, or Topology view by right-clicking on the selected device and selecting Utilities>Device Type Identification. The Device Type Identification window (Figure 7-1) appears, and the entry for the selected device type is highlighted. 115

116 Chapter 7: Device Type Identification Device Type Identification Table DTI displays the Device Type Identification table that lists the SPECTRUM device type name-to- System Object Identifier (sysobjectid) mappings. This includes all standard mappings that SPECTRUM ships with, all user-defined mappings, and any unregistered mappings (see Figure 7-1). The table displays the following information about each mapping: Vendor Name. This column displays the name of the company identified as manufacturing the device, such as Cisco or Juniper. System Object ID. This column displays the MIB II sysobjectid entry retrieved from the device. Device Type Name. This column displays the Device Type value mapped to the associated sysobjectid. Type. This column identifies the source of the mapping. This column is hidden by default. Modified. This columns identifies mappings that have been modified in the current DTI session. This column is hidden by default. You can modify the table display using the standard OneClick table preferences and column sorting methods. You can export the data displayed in the DTI table to a file of your choice in either a comma delimited (.CSV), tab delimited (.txt), or Web page (.HTML) format. Click Export ( ) in the DTI tool bar to open the Export Table Data to File dialog box. See the OneClick Console User Guide (5130) for more information about setting table preferences, sorting table column values, and exporting table data. 116 Modeling Your IT Infrastructure Administrator Guide

117 Device Type Identification in OneClick Figure 7-1: Device Type Identification Window - Default View Search DTI Mappings Using Filters You can search for specific text or numeric strings in the DTI table by entering them in the filter field. As you enter characters in the filter field, only the mappings that contain the same string of characters that you entered in the filter field appear in the table. Use this feature to search for: Vendor Name. Enter the name of a specific vendor to display all supported sysobjectids for that vendor, such as Juniper or Cisco. This can help you determine if SPECTRUM supports a specific model. Note: You need to display the Type column before using the following filters. Custom mappings. Enter the text string custom in the Filter field to view only the mappings that you or someone else has modified using DTI. Unregistered devices. Enter the text string unregistered to view only mappings of unregistered devices in the table. See Map Unregistered Devices on page 120 for more information about unregistered devices and DTI. Apply DTI Changes to SPECTRUM Model Catalog Once you have created or modified a mapping and applied the changes, all device models in your distributed SPECTRUM environment for which the DTI mapping changed are updated. The updated device type names appear in the Topology, Navigation, Explorer and List views for all landscapes. Modeling Your IT Infrastructure Administrator Guide 117

118 Chapter 7: Device Type Identification The SPECTRUM modeling catalog is also updated so that all future device models with this sysobjectid are assigned the new Device Type value. Manage Device Type Mappings The DTI utility categorizes the Device Type mappings into the following types: CA mappings - these are the default mappings that ship with SPECTRUM. Custom mappings - these are mappings created or customized using the DTI utility. Unregistered mappings - these are entries that do not have a mapping. See Map Unregistered Devices on page 120 for more information about unregistered devices. The mapping type appears in the Type column. See Device Type Identification Table on page 116 for more information about viewing the Type column. Custom Device Type Mappings You can customize any mapping or create new mappings in order to: Modify device type names to be more descriptive. Add new mappings to accommodate devices. Assign device names to Unregistered devices that SPECTRUM identified on your network. See Map Unregistered Devices on page 120 for information on performing this task. Custom Mappings with Modified Device Type Name If you modify the Device Type Name of an existing DTI mapping, you create a custom mapping that overrides the original mapping. The original mapping remains intact on the system. If you delete a custom mapping with a modified device type name value, the original mapping appears in the table again. See Delete Custom DTI Mappings on page 119 for information about deleting mappings. To Modify an Existing DTI Entry 1. Select the entry to be modified from the DTI list. Notice the selection fills in the System Object ID and Device Type Name fields. 2. Modify the device type in the Device Type Name field to the desired value. 3. Click Modify to enter the modified Device Type Name. 4. Click Apply or OK to write the change to the SpectroSERVER. The Operation Results window displays (Figure 7-2). 5. Once the operation completes, the results, either successful or unsuccessful, are shown for each landscape in the DSS environment. Click Close. Custom Mappings with Modified SysObjectID If you modify the sysobjectid value of an existing DTI mapping, you create a new custom mapping entry in the table. If you delete a custom mapping that has a modified sysobjectid value, that entry is removed from the DTI table. 118 Modeling Your IT Infrastructure Administrator Guide

119 Manage Device Type Mappings To Create a New Entry 1. Enter the system object identifier for the device you want to map in the System Object ID text field, for example, Enter the device type name you would like to pair with this system object identifier in the Device Type Name text field, for example Catalyst The Vendor Name will be automatically populated by SPECTRUM based on the enterprise ID term in the system object identifier. 3. Click the Add button to add the entry to the Device Type Identification List. 4. Click Apply or OK to write the change to the SpectroSERVER. The Operation Results window displays (Figure 7-2). 5. Once the operation completes, the results, either successful or unsuccessful, are shown for each landscape in the DSS environment. Click Close. Note: If there are device models that you wish to prevent from being modified through this procedure, see the Customization Considerations on page 123 for information on how to do this. Delete Custom DTI Mappings You can delete custom mappings from the DTI table. Default CA mappings cannot be deleted from the DTI table. When you delete a custom mapping that overrides a default mapping, the default mapping displays after the delete operation completes. See Custom Mappings with Modified Device Type Name on page 118 for information about custom mappings and masking default entries. To Remove an Existing DTI Entry 1. Select the entry to be deleted from the DTI list. Notice the selection fills in the System Object ID and Device Type Name text fields. 2. Click Delete to remove the entry. If Delete is not available, then you cannot remove this entry from the table. 3. Click Apply or OK to write the change to the SpectroSERVER. The Operation Results window displays (Figure 7-2). 4. Once the operation completes, the results, either successful or unsuccessful, are shown for each landscape that the change was sent to. Click Close. Modeling Your IT Infrastructure Administrator Guide 119

120 Chapter 7: Device Type Identification Figure 7-2: Operation Results Window Map Unregistered Devices Unregistered devices are devices for which SPECTRUM could not find a matching device type entry during the discovery and modeling process. Any unregistered devices appear in bold (Figure 7-3). Figure 7-3: Unregistered Devices in DTI In order to assign device type names to unregistered devices you need to know the sysobjectid of the unregistered devices on your network. Note: Display the Type and Modified columns in order to see these values when performing the following procedure. To Map Unregistered Devices 1. In the DTI utility, select the unregistered mapping you want to modify. 2. Enter the Device Type Name you want to use for this mapping in the Device Type Name entry field. 120 Modeling Your IT Infrastructure Administrator Guide

121 Manage Device Type Mappings 3. Click Modify. The entry appears in the DTI table with the new Device Type Name, and the type changes to Custom from Unregistered, and a appears in the Modified column. 4. Click Apply or OK to write the change to the SpectroSERVER. The Operation Results window displays. Distributed SpectroSERVER Support The DTI utility supports a distributed SpectroSERVER (DSS) environment. DTI recognizes when there are multiple primary SpectroSERVERs in a SPECTRUM environment and alerts you when it is not able to communicate with a SpectroSERVER. DTI queries all SpectroSERVERs for DTI table entries, and identifies any conflicts that exist among SpectroSERVERs for user specified mappings. Servers Unavailable Warning When you launch the DTI utility in a distributed SpectroSERVER environment and any of the primary SpectroSERVERs are down, a warning message appears stating that the down SpectroSERVERs will not receive any DTI mapping changes you make (Figure 7-4). If you proceed under these conditions, there will be custom DTI mapping conflicts once all the SpectroSERVERs are back online. See DTI Mapping Conflicts on page 121 for more information on DTI conflicts. Figure 7-4: Servers Unavailable Warning DTI Mapping Conflicts Conflicts in DTI mappings can occur in a DSS SPECTRUM environment when a sysobjectid has more than one device type name defined. Conflicts usually happen when: One or more SpectroSERVERs are down prior to launching DTI. One or more SpectroSERVERs go down after launching DTI and prior to applying changes to custom mappings. A new SpectroSERVER is brought online. If conflicting DTI mappings are detected when you launch the DTI utility, a Conflicts Detected dialog box (Figure 7-5) appears. You are required to resolve the conflicts before DTI will launch. Use the following procedure to resolve conflicts. Modeling Your IT Infrastructure Administrator Guide 121

122 Chapter 7: Device Type Identification Figure 7-5: Conflicts Encountered Dialog Box To Resolve DTI Mapping Conflicts Use the following procedure to resolve conflict using the Resolve Conflicts window (Figure 7-6). 1. Click Resolve Conflicts in the Conflicts Encountered dialog box; the Resolve Conflicts window appears. 2. Select the Device Type Name from the drop-down list to use to use for each System Object ID. 3. Click OK. The Resolve Conflicts dialog box closes. Figure 7-6: Resolve Conflicts Dialog Box Missing DTI Entries If DTI identifies a DTI entry that is present on some but not all of the servers in the DSS environment, the entry is automatically applied to all servers that do not have the entry. This condition is different from a conflicting entry condition, described in DTI Mapping Conflicts on page 121. DTI and Fault Tolerant Environments If you are working in a fault tolerant environment, the DTI utility differentiates between a primary and a backup server. In order for the DTI utility to operate, it must be able to connect to the primary SpectroSERVER. The application will not connect to the backup server. The backup SpectroSERVER will obtain the Device Identifier List update and device model updates from the primary SpectroSERVER during the Online Backup procedure. See the Distributed SpectroSERVER Guide (2770) for more information on working in a fault tolerant environment. 122 Modeling Your IT Infrastructure Administrator Guide

123 Customization Considerations Customization Considerations When you customize the Device Type Identifier using the DTI utility, the changes can be overwritten. You can control if and how DTI customizations can be overwritten using the DeviceTypeDiscEnable attribute. Prevent Changes to All Device Model Types Using DeviceTypeDiscEnable Attribute The DeviceTypeDiscEnable attribute allows you to control whether or not customizations to the Device Type can be overwritten. Setting a model s DeviceTypeDiscEnable attribute value to FALSE prevents the model s Device Type from being changed later on by actions performed in the DTI utility. See To Edit DeviceTypeDiscEnable for Specific Device Models on page 141 for more instructions on setting this attribute. It is possible to set different Device Type values for device models with the same System Object Identifier using of the Attribute Editor. However, when making future modifications to Device Type values, it is possible for such device-specific customizations to be overwritten. To avoid this, you can use the DeviceTypeDiscEnable attribute (0x230bd4). Preserve Device Type Customizations for Specific Devices You can preserve the customizations of a few devices as outlined in this example. Example: Preserve Device Type Customizations on Specific Devices Using the DTI Utility, you have added the following new device type name: sysobjectid = , Device Type Name = PC After applying the changes there are 2 devices, Model1 and Model2, with the sysobjectid modeled with the GnSNMPDev model type that receive the new Device Type. At, you have decided to rename Model1 with a different device type name. In the Explorer, Topology, or List view, select Model1. Select the Information tab, expand the SPECTRUM Modeling Information subview, and change the device type name from PC to MailServerPC. Now you have two entries for the sysobjectid, Model1 MailServerPC and Model2 PC. Later you decide that the sysobjectid needs a more descriptive Device Type name. Use DTI to change it from PC to WindowsNT. See To Modify an Existing DTI Entry on page 118 for the procedure to change the device type name. Once you apply the device type name change to WindowsNT, all GnSNMPDev models with that system object identifier are changed, including Model2 MailServePC. You did not want the device type name for Model2 changed from MailServePC. To prevent the customization of Model2 s device type name of MailservePC from being overwritten, you can set the DeviceTypeDiscEnable attribute (0x230bd4) on the device model to FALSE using OneClick s Attribute Editor. See To Edit DeviceTypeDiscEnable for Specific Device Models on page 141 for details on using the Attribute Editor. Modeling Your IT Infrastructure Administrator Guide 123

124 Chapter 7: Device Type Identification Prevent Device Type Name Changes on Model Types If you need to create a new model type to effectively manage devices on your network not supported explicitly in SPECTRUM, use the following process to prevent the Device Type Name value from being unintentionally overwritten. To Prevent Device Type Name Changes on Model Types 1. Create the new custom model type. 2. Model some or all devices for that model type. 3. Use the Attribute Editor to place the DeviceTypeDiscEnable in the User Defined category, as described in To Create User Defined Attributes on page Create a search using the Locater tab in the Explorer panel to find some or all the device models that use the new custom model type. 5. Use the Attribute Editor to set the DeviceTypeDiscEnable attribute value to No, and apply the value change to all existing device models and the model type in the SPECTRUM catalog, as described in To Edit DeviceTypeDiscEnable for Specific Device Models on page 141 This sets the DeviceTypeDiscEnable attribute value for all the device models using the new custom model type, and the model type in the SPECTRUM catalog. All future device models created using this model type will have the DeviceTypeDiscEnable attribute set to No. These steps prevent the Device Type Attribute from being overwritten by a user using the DTI utility. 124 Modeling Your IT Infrastructure Administrator Guide

125 Chapter 8: Modify Model Attributes In This Chapter This chapter describes how you can edit model attributes using OneClick s Attribute Editor and Search features. After reading this chapter, you will understand how you can modify attributes using the OneClick interface and the Attribute Editor utility. This chapter defines how to modify model attributes in the following sections: Why Modify Attributes? on page 125 Access Attributes From the Information Tab on page 126 VNM Attributes in the Information Tab on page 127 OneClick Attribute Editor on page 133 Launch Attribute Editor on page 133 Attribute Editor Dialog Box on page 134 User Defined Attributes on page 137 Change Attributes in Conjunction with Search on page 139 Attribute Groupings on page 142 To use the Attribute Editor, you must have administrative read/write privileges for those models you want to configure. Why Modify Attributes? Attributes can be used to set values on models, set values directly on devices, turn SPECTRUM features on or off, configure SPECTRUM features, set default values in the SPECTRUM modeling catalog, and for many other purposes. You can modify an attribute which is associated with a device s MIB object, thus changing the device s value for that object without having to use the device s local management. For example, you can modify a device s contact details. You can modify the Maintenance or Hibernation mode attribute in order to control those features. 125

126 Chapter 8: Modify Model Attributes You can use the Information tab in the OneClick interface to view and modify many common attributes. You can use the Attribute Editor to modify non-list attributes for a model or subset of models as well as modify default attribute values in the SPECTRUM modeling catalog. If you change any attribute values and apply them to the SPECTRUM modeling catalog, each device model that is subsequently created based on that model type will use the new attribute value. See Access Attributes From the Information Tab on page 126 for more information about viewing and setting attribute values for a single model using the Information tab. See OneClick Attribute Editor on page 133 for information about using the Attribute Editor. Note: Use caution in changing default settings for models; this can affect SPECTRUM s overall performance. If you are operating in a DSS environment, SpectroSERVER performance can be affected by attribute changes. Additionally, attribute value changes you make to the selected models will affect the same values for similar models created in the future, and for any existing model if that model s type is using the default value. Access Attributes From the Information Tab You can view and set attribute values for individual models using the Information tab. The subviews that appear in the Information tab display grouped categories of information available for the model. The subviews available in the Information tab depend on the selected model (see Figure 8-1). Figure 8-1: Information Tab 126 Modeling Your IT Infrastructure Administrator Guide

127 VNM Attributes in the Information Tab The attribute values that appear in the Information tab for the selected model are a result of a combination of the following processes: Automated discovery and modeling Manual modeling Using the Attribute Editor Direct entry using OneClick Default SPECTRUM values You can set some attribute values that appear in the subviews of the Information tab. Specific attributes that you can set depend on the model selected, privileges applied to model or model types and other factors. You can change the values of attributes for which set appears next to the attribute value (see Figure 8-2). Figure 8-2: SPECTRUM Modeling Information Subview Click set to change attribute values VNM Attributes in the Information Tab In OneClick, you can view and set a variety of attributes for each Virtual Network Machine (VNM) in your SPECTRUM installation. The attributes available in the VNM Information view depend on the add-on applications installed as part of your SPECTRUM environment. The VNM attributes are grouped in subviews for specific applications and functionality. Most attributes have tool tips associated with them describing the attribute. VNM Information subviews are discussed in the following sections. General Information The General Information subview provides information about the VNM such as its Network or IP address, condition, contact status, and when it was last polled successfully. With administrator privileges, you can set the VNM roll-up alarm attributes. See Roll-up Alarm Attributes on page 144 for more information about using these attributes. Online Database Backup Use the settings available in this subview to configure online backups of the SPECTRUM database. Modeling Your IT Infrastructure Administrator Guide 127

128 Chapter 8: Modify Model Attributes Automatic Backups Set Automatic Backups to Enabled for the SPECTRUM database to be automatically backed up. The default setting is Disabled. Backup Interval Backup Interval set how often in hours and minutes the SPECTRUM database is automatically backed up. New Backup Date & Time Set the date and time of the next database backup. Backup Compression Set this to Enabled to compress the backup file using the default compression mode. The default setting is Enabled. Prefix for Backup File Name Set the prefix used in the database backup file name. File names are appended with the date the backup occurred. Backup Directory Specify the directory on the server where the backup files are written to. You need to know the full path to the directory, as this is not a browse function. Minimum Required Disk Space Specify the amount of free disk space that must exist on the server in order for a backup to start. You can initiate an online backup immediately by clicking Begin Backup Now. SpectroSERVER Control The SpectroSERVER Control attributes and setting allow you to configure various aspects of the SpectroSERVER. For more information on these settings, see the Configuring Landscapes section of the Distributed SpectroSERVER Guide (2770). Device Thresholds Set the Device Thresholds attribute to Enabled to activate the threshold functionality on devices supporting threshold. Each threshold values setting must also be set to a non-zero value for the threshold to be active. Unmanaged Trap Handling Set the Unmanaged Trap Handling to Enabled for SPECTRUM to process traps received from unmanaged devices. Auto Connects Set the Auto Connects attribute to Enabled and SPECTRUM attempts to resolve the port connections when a pipe is created between two device models. See Live Pipes on page 132 for information about Live Pipes. 128 Modeling Your IT Infrastructure Administrator Guide

129 VNM Attributes in the Information Tab Copy Users when Copying Groups If the Copy Users when Copying Groups attribute is set to Yes, whenever you copy a group or a user in a group from one landscape to another, the group and all users in the group are copied as well. Log When Device Cannot Be Contacted Set the Log When Device Cannot Be Contacted attribute to No so that SPECTRUM will not log attribute values for models that have lost primary management contact with the devices they represent. In most cases, this is the desirable behavior since it eliminates extra traffic on a part of the network where there is likely to be a problem. VLAN Configuration This attributes controls whether or not Virtual Local Area Networks (VLANs) are modeled for networks on this VNM. Server Polling This attribute controls whether or not the SpectroSERVER polls devices it is managing on the network. Minimum Disk Space (kbytes) This attribute sets the minimum amount of free disk space in kilobytes that must exist on the partition that the SpectroSERVER starts from in order for the SpectroSERVER to start. Use Fully Qualified Hostname If set to Yes, the domain name is included with the host name if the Name Service option is the primary method used to provide model names for new models. Model Naming Order Set the order of sources used by SPECTRUM to create model names for new models. If the first source is not available for a device, SPECTRUM attempts to use the next source. Use Loopback If Use Loopback is set to Yes, the SpectroSERVER will use the loopback interface as a primary agent address. Loopback if Description Enter a string in this field to identify a preferred loopback interface for SPECTRUM to use when modeling the device. SPECTRUM compares the string entered with the if_descr entries in the device IFTABLE for loopback interfaces only. If a match is found, SPECTRUM uses that loopback interface when it models the device. If there is no match, or no value is specified, SPECTRUM chooses the loopback interface on the device with the lowest if_index value. AutoDiscovery Control The attributes available in the AutoDiscovery Control subview affect actions that occur during Discovery and Modeling sessions. If you have a DSS environment, you will need to make any changes in these settings to all your SpectroSERVERs. Modeling Your IT Infrastructure Administrator Guide 129

130 Chapter 8: Modify Model Attributes Modeling and Protocol Options These attributes affect how SPECTRUM discovers and models elements on a network using the following functionality: Discovering and modeling LAN functionality available when reconfiguring a device model Discovering connections functionality for a container model (LAN, Network, and others) Auto Connects functionality used to resolve port connections when you manually create a connection between two models. Discover Connections functionality when creating a new model. Create WA Link Set the Create WA_Link Models attribute to Yes for SPECTRUM to create a WA_Link model between the interfaces of two routers linked by a wide area connection. If Create WA_Link is not selected, the two linked interfaces are directly connected without using the WA_Link model. See the How to Manage Your Network with SPECTRUM Guide (1909) for information about Wide Area Link models and how they are used. Proprietary Discovery Tables Set the Proprietary Discovery Tables attribute to Yes if you have devices on your network that use the following proprietary discovery protocols: Nortel Discovery Protocol Cisco Discovery Protocol Extreme Discovery Protocol Cabletron Discovery Protocol SPECTRUM will not be able to discover devices supporting these discovery protocols unless the Proprietary Discovery Tables attribute is set to Yes. Create LANs (IP subnets) Set the Create LANs (IP subnets) attribute to Yes so that SPECTRUM creates a LAN container model containing all the layer 1 and layer 2 devices within that IP subnet during the layer 3 mapping process for any router interface that routes to a LAN. Physical Addresses If this parameter is set to Yes, 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. Create (Fanout) Set the Create Fanout attribute to Yes to allow SPECTRUM to create a Fanout model for interfaces that cannot be accurately connected among three or more interfaces. If this attribute is set to No, interfaces that have unclear connection information will not be mapped. Trap Based Continuous Discovery Use the Trap Based Continuous Discovery subview to configure SPECTRUM to automatically create a device model when it receives an SNMP or syslog trap from a device not already modeled. When 130 Modeling Your IT Infrastructure Administrator Guide

131 VNM Attributes in the Information Tab the SpectroSERVER receives an unmanaged trap, it asserts an event on the VNM model indicating that an unmanaged trap was received. All models created using Trap Based Continuous Discovery are placed in the New Device Container. SPECTRUM places new models created by a scheduled continuous discovery or by an unmanaged trap in this container. Unmanaged Trap Discovery Set the Unmanaged Trap Discovery attribute to Yes to discover and model the source of an unmanaged trap using the IP address sent with the trap. This includes both SNMP and syslog traps from devices as well as Agent Log file matching traps. See SpectroSERVER Control on page 128 for information about how to enable unmanaged trap handling on the VNM. New Devices in Maintenance Set the New Devices in Maintenance attribute to Yes to have new device models created based on an unmanaged trap put into maintenance mode when they are discovered. Create Pingables Set the Create Pingables attribute to Yes and SPECTRUM will model devices that cannot be modeled using SNMP as type Pingable if the devices respond to a ping (ICMP) request. Discover Connections If the Discover Connections attribute is set to Yes, OneClick attempts to discover and model the connections for devices discovered by Trap-based Continuous Discovery. Community Names Create, order, and delete SNMP v1 and v2c community names used when SPECTRUM attempts to access and model devices that were discovered during Trap-based Continuous Discovery using SNMP. SPECTRUM first tries the community name included with the unsolicited trap. Then it proceeds through the list of community names in order. Note that SNMP v2c community names SNMP Ports Create, order, and delete the list of ports to use when accessing and modeling devices. Debug Options Set the Debug AutoDiscovery attribute to On to have SPECTRUM create a debug output file containing data on the status of the device modeling and mapping process for each Discovery session. These files are available at <$SPECROOT>/SS/ADiscDebug_<timestamp>. The Debug AutoDiscovery option is useful when the discovery modeling or mapping process is hanging. In this case, the output file indicates where and on which device the modeling or mapping process encountered difficulty. Debug Device at IP Use the Debug Device at IP attribute to debug a particular device s connectivity mapping process. To do this, set the Debug AutoDiscovery option to On. Use the Debug Device at IP option to specify the IP address of the device you want to debug. When Discovery is run, SPECTRUM prints out all connection information on the device model specified by the IP address to the ADiscDebug_<timestamp> debug log file. If you set the Debug Device at IP to , the debug log will contain debug data for all devices on your network. Modeling Your IT Infrastructure Administrator Guide 131

132 Chapter 8: Modify Model Attributes Fault Isolation The Fault Isolation Model Information view allows you to configure various aspects of SPECTRUM s fault isolation functionality. For complete details on this view, see How to Manage Your Network with SPECTRUM (1909). Live Pipes SPECTRUMs Live Pipes functionality lets you turn on port status monitoring for individual links and display the status of a link through the use of status color indicators. A link is a connection between two devices that SPECTRUM has resolved to the port level. See the How to Manage Your Network with SPECTRUM Guide (1909) for more information about Live Pipes functionality. The Live Pipes attribute must be set to Enabled on the VNM to turn on Live Pipes functionality on the VNM. Other attributes you can set in this view with administrator privileges are Alarm Linked Ports, Suppress Linked Port Alarms, and Port Always Down Alarm Suppression. Live Pipes and Global Collections in DSS Environments In a DSS environment, the Live Pipes attribute must be set to the same value on all VNMs so that the Live Pipes functionality provides accurate link connection information in Global Collections. If Live Pipes is set to different values on VNMs in a DSS setup, the Live Pipes information in Global Collections will be unpredictable. Alarm Management These settings control when SPECTRUM generates alarms. You can fine tune the types of alarms generated using the attribute settings in this subview. Generate Alarm Events Set the Generate Alarm Events attribute to Yes and SPECTRUM creates events (viewable in the Events tab) for alarms changes based on alarm creation, updating, and clearing events. The default setting for this attribute is Yes. Add Events to Alarms Set the Add Events to Alarms attribute to Yes and SPECTRUM adds alarm events to alarms. The default setting for this attribute is No. Age Out Residual Alarms Only Residual alarms are alarms that existed prior to a SpectroSERVER restart and have not been reverified. If the Age Out Residual Alarms Only attribute is set to Yes, SPECTRUM will clear only residual alarms based on the Alarm Age Out timer setting. The default setting for this attribute is Yes. Age Out Alarm Time (Hours) This attribute defines how long an alarm can exist in SPECTRUM. Once an alarm has existed for the number of hours specified by this attribute, it is a candidate for automatic removal. To disable this functionality, set this attribute to zero (0). 132 Modeling Your IT Infrastructure Administrator Guide

133 OneClick Attribute Editor NOTE: Displaying Initial and Suppressed alarms is not recommended in OneClick due to the volume of network traffic it can potentially add to your network. SPECTRUM will generate initial and suppressed alarms if the Disable Initial Alarms and Disable Suppressed Alarms settings for the Virtual Network Machine (VNM) managing your network are set to Yes. Disable Initial Alarms Set the Disable Initial Alarms to No and SPECTRUM will generate an alarm if a model s condition changes to Initial. The default setting for this attribute is Yes. Disable Suppressed Alarms Set the Disable Suppressed Alarms attribute to No and SPECTRUM will generate an alarm if a model s condition changes to Suppressed. The default setting for this attribute is Yes. Disable Maintenance Alarms Set Disable Maintenance Alarms to No and SPECTRUM will generate an alarm if a model s condition changes to Maintenance. See the OneClick Console User Guide (5130) for information about putting devices in Maintenance mode. The default setting for this attribute is No. OneClick Attribute Editor The Attribute Editor is an advanced SPECTRUM OneClick utility used to configure management policies that govern how SPECTRUM manages network devices and their components. It is best suited for performing bulk attribute changes on multiple devices models. You can change attribute values for one or more selected models in a view. The Attribute Editor dialog box groups attributes into categories. You can choose to edit the default settings provided within these categories, or you can define additional attributes to edit within the User Defined category. The following sections describe how to access the Attribute Editor, work in the Attribute Editor dialog box, and how to use Attribute Editor with the Search feature in the Locater tab. Launch Attribute Editor You can launch the Attribute Editor in OneClick by right-clicking on any model and selecting Tools, Utilities, Attribute Editor. You can also launch the Attribute Editor from anywhere in OneClick where a model is presented for you to select, including the List tab, the Explorer tab, Interface tab in Components Details panel, the Locator Results tab, or from the Tools menu. Open Attribute Editor with Device Context You can launch the Attribute Editor with context of selected models. If you select a model in the List, the Explorer, or the Interfaces view and then right-click and select Utilities, Attribute Editor, the Attribute Editor opens with the context of the selected model. Any changes you make apply to the selected models, and if you select Set as Default, the changes are applied to the SPECTRUM modeling catalog for the selected models. Modeling Your IT Infrastructure Administrator Guide 133

134 Chapter 8: Modify Model Attributes Attribute Editor Dialog Box The Attribute Editor (Figure 8-3) includes a right and left panel. The left panel groups attributes in a tree display. The right panel provides an editing area to view current attribute values and make changes. Figure 8-3: Attribute Editor Attribute groupings Palette for viewing and editing attribute values Task Oriented Attribute Groupings The left panel of the Attribute Editor provides attributes grouped by tasks you perform on devices and by categories of attribute types. The SNMP Communications folder groups attributes related to tuning SNMP communications between the SpectroSERVER and a device. See Attribute Groupings on page 142 for more information on the task-related attribute groupings. Filter Attribute Categories You can enter text in the Filter field to locate attributes in the attribute categories in the Attribute Editor left panel. When you enter text in the Filter field, attribute categories that do not contain an attribute that matches the filter appear as bullets, becoming inaccessible. All attribute categories that contain an attribute that matches the filter appear as folders that you can expand and then select the subcategories within to move into the right panel for editing. For example, if you wanted to find attributes related to alarms, type alarm in the Filter text box. Attribute Edit Panel To edit attribute values, you must select the attribute category from the left panel, then click the right facing arrow to place the attributes in the right side editing panel. When an attribute is placed in the edit panel, it appears in italics in the attribute list in the left panel. 134 Modeling Your IT Infrastructure Administrator Guide

135 OneClick Attribute Editor Tool tips describing an attribute are available for some attributes when they appear in the right panel for editing. Place the cursor over the attribute name and if a tool tip is available, it appears as shown in Figure 8-3. No Change. The No Change setting appears to the left of most attribute input fields. When No Change is selected, the input value, if any, is not written when you click Apply or OK. When you make changes to the attribute value by selecting a value or clicking in the input field, No Change is automatically deselected. In Figure 8-3, the Wide Area Link Fault attribute value is grayed out because No Change is selected. Either deselecting No Change or clicking in the input field makes the attribute value editable. Set as Default. This option appears to the right of most attribute input fields in the Editor panel. If you select Set as Default, the value is written to the model types in the SPECTRUM modeling catalog when you click Apply or OK. All future models that use these model types inherit the new value. Warning. Altering the default model-type value of an attribute changes the SPECTRUM modeling catalog. Any existing models that use that current default value and any models created in the future will use the new default value. This means changing the default value could affect models that are not explicitly selected. Changes to models not explicitly selected may not take effect until after the SpectroSERVER restarts. Load Attribute Values. You view the current value for a set of selected attributes when you have launched the Attribute Editor in the context of a specific model. After populating the edit panel, click Load Attribute Values to view the current values for the attributes. If the selected models do not use or have a value for an attribute, no value displays when you click Load Attribute Values. In Figure 8-3, the Flash Green attribute value of No and Wide Area Link Fault attribute value BothPortsandLink appear after clicking Load Values. The selected models do not use the Poll Port Status(Device) and Poll Port Status(Link) attributes, so a value did not load for them. If you have launched Attribute Editor in the context of multiple model types, they may have different values for the same attribute. If this occurs, the Select Model window appears when you click Load Attribute Values (Figure 8-4). Select the model you want to load attribute values for, and click OK. Modeling Your IT Infrastructure Administrator Guide 135

136 Chapter 8: Modify Model Attributes Figure 8-4: Select Model Window When you click Apply or OK in the Attribute Editor dialog, SPECTRUM OneClick attempts to write the new attribute values and displays the Attribute Edit Results dialog box. Attribute Editor Results Dialog The results of attribute value changes appear in the Attribute Edit Results dialog box (Figure 8-5). Each item in the table represents the result of a single attribute written to a model. Figure 8-5: Attribute Edit Results Dialog Box The Result column indicates whether the write operation succeeded or failed. The Old Value and New Value columns show the original value and the last written value. If the write operation failed or the previous value could not be obtained, the corresponding field will display N/A. If the write operation failed, for example, if the device did not respond, you can select the item in the table and click Retry. Use the Undo button to undo the selected successful attribute value change in results list if necessary. 136 Modeling Your IT Infrastructure Administrator Guide

137 OneClick Attribute Editor User Defined Attributes In the Attribute Editor dialog box, you can create a list of attributes that display when you expand the User Defined category. After you create this list, you can access the user defined attributes. You can at any time remove the user defined attributes. Attribute Selector Dialog Box You select user defined attributes using the Attribute Selector dialog box (see Figure 8-6). The following procedure describes how to create a user defined attribute in the User Defined category using the Attribute Selector dialog box. Figure 8-6: Attribute Selector Dialog Box To Create User Defined Attributes Follow these steps to create a user defined group of attributes in the Attribute Editor dialog box. 1. In the left panel of the Attribute Editor dialog box, next to the User Defined folder, click add. The Attribute Selector dialog box appears. 2. In the Attribute Selector dialog box, select a model type in the left panel. 3. Select the attribute that you want to edit from the list that appears in the right panel and click OK. The attribute you selected now appears in the User Defined category in the Attribute Editor dialogue box. You can only select one attribute at a time to add to the User Defined category. Repeat this process to select additional user defined attributes. Tips: Use the Filter text box to quickly locate an attribute or model type in the list. Modeling Your IT Infrastructure Administrator Guide 137

138 Chapter 8: Modify Model Attributes Remove user defined attributes within the User Defined category by clicking the remove link next to the attribute you want to remove. Each OneClick user can create their own unique set of user defined attributes. 138 Modeling Your IT Infrastructure Administrator Guide

139 OneClick Attribute Editor Change Attributes in Conjunction with Search You can use the Attribute Editor feature in conjunction with the Search feature in the Locater tab (Locater Search). By using the Locater Search feature with the Attribute Editor feature you can locate all models meeting certain criteria and then attempt to change the attribute values on those matching models. The following example combines creating and running a new search with changing attributes through the Attribute Editor. This example walks you through adding user defined attributes and writing changes to the component(s) (i.e., SpectroSERVER, device(s), interface(s)) meeting the search criteria. Note: For additional information about using the Search feature in the Locater tab of the OneClick window, see the OneClick Console User Guide (5130). Define a Search to Create a User Defined Attribute for Editing This example demonstrates how to create and run a search to locate the GlobalConfig model on the SpectroSERVER. It then shows how to use the Attribute Editor to add the HibernationCommSuccessTries attribute to the User Defined category so that you can update the value as needed. Note: The value for HibernationCommSuccessTries determines the number of successful attempts the SpectroSERVER must make to devices in hibernation mode before the devices can resume normal management communication. By default, the value of this attribute is 3. To Define a Search to Create a User Defined Attribute for Edit In OneClick window, do the following to create a new search: 1. In the OneClick Locater tab, click Create a new search. The Create Search dialog box appears. 2. In the Create Search dialog box select Modeltype Name (0x10000) from the Attribute dropdown menu. 3. Set Comparison Type to Equal To. 4. Type GlobalConfig in the Attribute Value field. 5. Click Save As and name the search (for example, hibernationattempts ) and click OK. 6. In the Create Search dialog box, click OK. 7. In the Locater tab, select the search you just created ( hibernation attempts ) then click Launch this Search. The Select Landscape to Search dialog appears. 8. Select the landscapes to search and click OK. The search results appear in the Results tab. 9. In the Results tab, right-click the GlobalConfig entry and select Utilities, Attribute Editor. The Attribute Editor dialog box appears. 10. In the left panel of the Attribute Editor dialog box, click the add link next to the User Defined folder. The Attribute Selector dialog box appears. 11. In the left panel of the Attribute Selector dialog box, click on the folder Other. Modeling Your IT Infrastructure Administrator Guide 139

140 Chapter 8: Modify Model Attributes 12. In the Filter text box (below the left panel) type GlobalConfig and then select the GlobalConfig entry appearing under the Other folder. 13. In the Filter box under the right panel of the Attribute Selector dialog box, type HibernationCommSuccessTries. The HibernationCommSuccessTries attribute appears in the Attribute for GlobalConfig list in right panel. 14. Double-click the HibernationCommSuccessTries entry in the list to add it to the User Defined category. 15. In the Attribute Editor dialog box, edit the user defined attribute value by selecting it in the left panel and clicking the Right Arrow button to move its associated attribute fields to the editing panel. 16. In the right panel, edit the attribute values as desired then click Apply to write the changes to the component. The Attribute Edit Results dialog appears listing the results of the changes made. Edit Attributes for Specific Devices or for Model Types This section provides examples for changing an attribute value for a specific model type, or for a specific set of devices. Example: Edit Interface_Polling_Interval for Cisco Devices Supporting IPsec Cisco IPSec tunnel interface management is available in SPECTRUM for Cisco devices that support the IPSec related MIBs. Once modeled, the tunnel models are updated every hour. If your environment requires less or more frequent updates to the tunnel models, you can use the Attribute Editor to do so. The attribute Interface_Polling_Interval defines how frequently SPECTRUM monitors the MIB associated with the tunnel interface models so that the modeling is up to date. To turn off this monitoring, you need to set the Interface_Polling_Interval attribute to 0. To change the frequency that SPECTRUM monitors these MIBs, change the value for attribute to the desired number of seconds between desired polling cycles seconds equals one hour. To Edit the Interface_Polling_Interval Attribute for Cisco Devices 1. Locate the Cisco routers on your network by creating a new Global Collection of Cisco routers that have the Interface_Polling_Interval set to 3600 seconds. See the OneClick Console User Guide (5130) for information about creating global collections. 2. Select the Cisco routers on which you want to edit the Interface_Polling_Interval value from the global collection. 3. Right-click and select Utilities, Attribute Editor. 4. Add the Interface_Polling_Interval to the User Defined attributes list. See To Create User Defined Attributes on page Move the Interface_Polling_Interval attribute into the right hand panel for editing. 6. Enter the value in seconds to which you want to change the polling interval. 140 Modeling Your IT Infrastructure Administrator Guide

141 OneClick Attribute Editor 7. Select OK. The Attribute Edit Results dialog box appears, displaying the results for each device you attempted to change the attribute value on. If the change failed on any of the selected devices, select them and click Retry. 8. Close the Attribute Edit Results dialog box, and click OK to close the Attribute Editor dialog box. Example: Edit the DeviceTypeDiscEnable Attribute for Specific Devices The DeviceTypeDiscEnable attribute is used to allow or prevent changes to the device type name value for device models and model types. Use the following procedures to modify the value for this attribute. See Device Type Identification on page 115 for information about device type names. To Edit DeviceTypeDiscEnable for Specific Device Models 1. Add the DeviceTypeDiscEnable attribute to the User Defined category using the procedure described in To Create User Defined Attributes on page 137. Select the devices on which you want to prevent device type name customizations; 2. Select the Locater tab in the Navigation panel. 3. Expand the Devices folder; double-click By Model Name; the Search dialog box appears. 4. Enter the name of the device type model on which you want to prevent device type name customizations. Select all applicable landscapes as necessary. Click OK. 5. The devices using the device type model specified appear the Lists tab. Select the specific devices on which you want to prevent customizations. 6. Right-click and select Utilities, Attribute Editor to launch the Attribute Editor. 7. Expand the User Defined folder and select DeviceTypeDiscEnable and click the right arrow to put the attribute in the right-side editing panel. 8. Set the attribute value to No and click Apply. 9. Make certain Set as Default is not selected. 10. The Attribute Edit Results window appears, and displays the results of the edit, either successful or unsuccessful. If successful, the DeviceTypeDiscEnable attribute is now set to false, or no, on the devices you selected in step 5. Modeling Your IT Infrastructure Administrator Guide 141

142 Chapter 8: Modify Model Attributes Example: Edit DeviceTypeDiscEnable for a Model Type You can set an attribute value and apply it to the model type in the SPECTRUM modeling catalog and to all device models. Also, all device models created in the future using the model type will use the attribute value that you set in this manner. To Edit DeviceTypeDiscEnable for a Model Type 1. Add the DeviceTypeDiscEnable attribute to the User Defined category using the procedure described in To Create User Defined Attributes on page Create a search using the Locater tab in the Explorer that finds some or all the device models that use the new custom model type. 3. Select one of the device models using the new custom model type in the search results list, right-click on it and select Utilities, Attribute Editor. The Attribute Editor opens with the context of the select device. 4. In the Attribute Editor, select the DeviceTypeDiscEnable attribute in the User Defined category and move it to the Attribute Editing panel by clicking the right arrow. 5. Set the attribute value to No. 6. Select Set as Default to apply this change to the SPECTRUM catalog for the model type used by the device model selected in step Click Apply. A warning message appears. Click Yes. This sets the attribute value for all the device models using the model type, and apply it to the model type in the SPECTRUM modeling catalog and to all device models. All future device models created using this model type will have the DeviceTypeDiscEnable attribute set to No, and the Device Type Attribute cannot be overwritten. Attribute Groupings This section describes some of the attribute grouping presented in the Attribute Editor window. Change Management on page 142 Interface Configuration on page 143 Maintenance Mode Attributes on page 144 Roll-up Alarm Attributes on page 144 SNMP Communications Attributes on page 147 Thresholds on page 148 Change Management This group of attributes allows SPECTRUM maintain up-to-date configuration information about modeled devices. The following attributes in this grouping enable SPECTRUM to interrogate a device and gather information about it s interfaces and connections after a specific event occurs: Automatically Reconfigure Interfaces 142 Modeling Your IT Infrastructure Administrator Guide

143 Attribute Groupings Discovery After Reconfigure Discover Connections after Link Up Event Topologically Relocate Model See Update Device Interface and Connection Information on page 98 for more information about these attributes, and about configuring SPECTRUM to maintain updated device configurations. The following attributes in this grouping configure SPECTRUM to have redundant ways of contacting devices. Enable Redundancy Generate Redundancy Alarms SPECTRUM will use multiple IP addresses in a cascading manner to contact devices if a device fails to respond to queries made on it s primary address. The devices must have multiple IP addresses configured in their IP tables. See Redundant Connections between SPECTRUM and Modeled Devices on page 102 for more information about Interface Configuration You set the value for a set of model type interface configuration attributes in the Interface Configuration grouping. Admin Status This attribute sets the administrative status for an interface. Create Sub-Interfaces Set this attribute to Yes, and if a device supports RFC1573, SPECTRUM will model the device s subinterfaces. Interface Model Name Suffix SPECTRUM uses the value of this attribute to name interfaces for the model or models. Choose from a set of available suffices in the drop down list when editing this attribute in the edit palette. Use If Entity Stacking When modeling interfaces, SPECTRUM uses the information contained within the MIB II ifstacktable to determine their logical stacking. For example, in the case of frame relay interface with DLCI sub-interfaces, SPECTRUM will attempt to stack them using information in the ifstacktable. Setting use_if_entity_stacking/0x12a83 to TRUE (on the device model) will cause SPECTRUM to attempt to use information from RFC2737 (Entity MIB) to determine interface stacking if the ifstacktable method fails. It is advised that this is done on a case-by-case basis as some vendors do not implement the RFC2737 indexing scheme correctly, which can cause interfaces to be incorrectly stacked. Modeling Your IT Infrastructure Administrator Guide 143

144 Chapter 8: Modify Model Attributes Stale Interfaces SPECTRUM handles interface definitions that are temporarily removed from their corresponding MIB tables using its Stale Interface functionality. These types of situations can include: a module is temporarily removed from a device a configured tunnel temporarily goes down on a device In these situations, it is advantageous for SPECTRUM to retain the interface modeling information rather than immediately destroying them. This prevents useful model-specific attributes and resolved connections from being lost. SPECTRUM determines that an interface model is stale when no corresponding entry exists in the MIB where the interface is defined. Once the stale interface ages out SPECTRUM removes it from the model. The age out period for an interface is defined by the Stale Interface Age Out attribute (in minutes) on the device model. An event is generated when SPECTRUM determines an interface is stale. If the stale interface has resolved connections, a MINOR alarm is generated on the interface model. If SPECTRUM determines that the interface is no longer stale before the age out period expires, and prior to a reconfiguration which causes the interface model to be destroyed, an event is generated and any stale interface alarm is cleared. Enable Stale Interface Alarms Set this attribute to Yes to enable SPECTRUM to generate a MINOR alarm on an interface model when the interface becomes stale and it has resolved connections. Set this attribute to No if you do not want this condition to generate an alarm. Stale Interface Age Out (min) This attribute specifies the amount of time in minutes that SPECTRUM waits for the stale interface to age out before removing the model. The default value is 120 minutes. To disable the stale interface functionality, set this attribute to 0. Maintenance Mode Attributes You can set values for the Maintenance and Hibernation mode attributes in the Attribute Editor s Maintenance Mode folder. You can also set these attribute values and create and apply maintenance mode schedules in the model s Information tab. See the OneClick Console User Guide (5130) for more information about Maintenance and Hibernation modes and managing maintenance mode schedules. Roll-up Alarm Attributes Access the SPECTRUM attributes used to manage roll-up alarm settings and threshold levels in the Attribute Editor s Roll Up Alarm Settings folder. You can also view and set these attributes in the Information tab under the General Information subview. You can adjust these attributes for containers modeled on your network and for the SPECTRUM container model library. 144 Modeling Your IT Infrastructure Administrator Guide

145 Attribute Groupings Table 8-1 lists the attributes and describes how they are used and their default values. Table 8-1: Roll-up Condition Threshold Level Attributes Roll-Up Alarm Setting Value When Yellow Value When Orange Value When Red Yellow Threshold Orange Threshold Red Threshold Description The point value of a Yellow alarm condition existing in a child towards the roll up alarm threshold value for the parent container. Default = 1. The point weight of an Orange alarm condition existing in a child towards the roll up alarm threshold value for the parent container. Default = 3. The point weight of a Red alarm condition existing in a child towards the roll up alarm threshold value for the parent container. Default = 7. The minimum points needed to trigger a Yellow roll up alarm for a container. Default = 3. The minimum points needed to trigger an Orange roll up alarm for a container. Default = 6. The minimum points needed to trigger a Red roll up alarm for a container. Default = 10. Note: Changing threshold levels should be done carefully. You may see an increase in generated alarms if threshold levels are set lower, or fewer alarms if levels are set higher. Model Status and Alarm Conditions SPECTRUM and OneClick use roll-up alarm thresholds and model alarm thresholds to determine the status for modeled entities. OneClick displays two types of status for modeled entities, Condition and Roll-up Condition. Table 8-2 lists the details about what these conditions describe, and what OneClick applies them to. Table 8-2: Model Status Categories in OneClick Model Status Applies to... Description Condition color Applies to all models Reflects the current contact or alarm status of the model itself. Roll-up Condition Color Applies to container models, such as networks, LANs, and WANs Reflects the composite status of all the other models in the container (sometime referred to as their children ). If a modeled device or interface exists in a container, its condition rolls up to the parent container and is reflected in the container s roll-up condition. The model status types listed in Table 8-2 rely on threshold values to determine when and how to use the associated color indicators. The Roll-up condition is displayed using an inverted triangle that appears adjacent to a container icon in the container s Information tab. Modeling Your IT Infrastructure Administrator Guide 145

146 Chapter 8: Modify Model Attributes Roll-up Condition Thresholds A container model has attributes that define values for alarm conditions that may exist on the children of the container. A container model also has attributes that define when it s roll-up alarm conditions are triggered. The combined value of all the alarm conditions for a container s children is used to determine the roll-up alarm condition for the container. Figure 8-7 shows a container that has a roll-up condition of orange, or major, based on the alarm conditions of it two children. The roll-up alarm setting for the container use the default values listed in Table 8-1. One child has a green or normal condition; this contributes zero points toward the container s roll-up condition. The other child has a red or critical condition that contributes seven points toward the container s roll-up condition (Value When Red = 7). The total value of the alarm conditions on the container s children is 7. The roll-up thresholds for the container use the default values for the Roll-up alarm settings listed in Table 8-1. The Orange Threshold value = 6, so the container s roll-up appears as Orange, indicating a major alarm condition. Figure 8-7: Container Model Roll-up Condition Parent container roll-up status = orange/major (roll-up icon appears orange). Child threshold points : = 7 Container major threshold = 6 Child threshold points : = 7 Roll-up status = Orange/Major Child1 condition = normal 0 points. Child2 condition = major. 7 points 146 Modeling Your IT Infrastructure Administrator Guide

147 Attribute Groupings SNMP Communications Attributes You can tune SPECTRUM s overall SNMP communications by changing the values of the attributes in the Attribute Editor s SNMP Communications folder. The attributes listed in Table 8-3 define how SPECTRUM communicates with a device. Table 8-3: Performance Attributes Attribute Attribute Location Description Community Name DCM Time Out DCM Try Count Polling Interval Polls to Log Ratio Information tab>spectrum Modeling Information Attribute Editor, SNMP Communications Information tab>spectrum Modeling Information Attribute Editor, SNMP Communications Information tab> SPECTRUM Modeling Information Attribute Editor> SNMP Communications Information tab> SPECTRUM Modeling Information Attribute Editor>SNMP Communications Attribute Editor>SNMP Communications Allows the SpectroSERVER to communicate with devices on your network. The number of milliseconds the polling agent will wait for a response from the device before timing out. The number of access attempts to make to a device before reporting a failure. The number of seconds between polls SPECTRUM makes to devices. The number of polls per log. If it is set to 3, then data is logged every third poll. Tuning SPECTRUM s SNMP Communications Using your knowledge of your network s infrastructure and of the services and connectivity provided by your network, you can manage the SNMP communications between SPECTRUM and the devices on your network. More Efficient SNMP Communications You can make adjustments such as reducing how often SPECTRUM requests updates from less critical devices. This results in less SNMP-related traffic on your network, and a smaller load on the SpectroSERVER. Do this by increasing the value of the Polling Interval attribute. Decreasing the value of the DCM Try Count will also reduce SNMP network traffic generated by SPECTRUM. Increase Reliability If you decrease the value of the Polling Interval attribute for mission critical devices and interfaces, network operators will see updated information about these devices in OneClick more often. This may improve their ability to see potential issues on the network before they impact network performance. A decreased Polling Interval will result in more SNMP network traffic generated by SPECTRUM. Modeling Your IT Infrastructure Administrator Guide 147

148 Chapter 8: Modify Model Attributes Thresholds The Thresholds grouping contains the SPECTRUM device and interface threshold settings. See Device and Interface Threshold Settings on page 95 for more information about using these settings to controls if and how SPECTRUM generates and clears alarms for these parameters. Device Thresholds The following device threshold parameters are available in this grouping: % CPU Utilization and % CPU Utilization Reset. % Memory Utilization and % Memory Utilization Reset. Interface Thresholds The following interface threshold parameters are available in this grouping: % Utilization Threshold and % Utilization Reset. Packet Rate Threshold (packets/sec) and Packet Rate Reset. % Error Rate Threshold and % Error Rate Reset. % Discarded Threshold and % Discarded Reset. See the OneClick Console User Guide (5130) for more information about interface threshold parameters. 148 Modeling Your IT Infrastructure Administrator Guide

149 Chapter 9: MIB and Trap Management MIB and trap management can be accomplished in SPECTRUM using OneClick integrated utilities. MIB Tools is a OneClick utility that lets you compile, import, and browse MIBs, issue Simple Network Management Protocol (SNMP) requests to network elements, and customize the way MIB objects and traps are mapped in SPECTRUM. This suite of functionality allows you to create, customize, and troubleshoot network element management in SPECTRUM. In This Chapter SNMP, MIBs, and SPECTRUM OneClick MIB Tools on page 151 Navigation Panel MIB Management on page 154 Contents Panel Browse MIBs on page 157 Contents Panel Attribute and Trap Management on page 162 Multiple OneClick Servers on page 170 Multiple SpectroSERVERs on page 167 SNMP, MIBs, and SPECTRUM SNMP and Management Information Bases (MIBs) form the basic structure of network element management in SPECTRUM. SPECTRUM provides network element management by communicating with SNMP-compliant network entities modeled in SPECTRUM using SNMP. These network entities are represented virtually by their MIBs. A MIB is a type of database which resides on a network device and represents that device as a hierarchical collection of objects. A MIB object represents an individual element of information in a MIB, such as the uptime of a device. MIBs themselves are text files with special syntax. SPECTRUM complies with the following RFCs regarding MIBs and SNMP: RFC 1155: Structure and Identification of Management Information for TCP/IP based internets RFC 1157: A Simple Network Management Protocol RFC 1213: Management Information Base for Network Management of TCP/IP-based internets 149

150 Chapter 9: MIB and Trap Management How a MIB Is Organized Because networking devices made by a variety of manufacturers must all be able to communicate with one another, the International Standards Organization requires that each network device organize its management information according to a pre-defined tree format. This tree structure branches out into several subtrees, with each subtree organized into branches (groups of related information) and leaves (the individual pieces of information, or objects). The Internet subtree is administered by the Internet Assigned Numbers Authority (IANA) and is designed to identify SNMP manageable agents. Object Identifiers Each layer of this tree is numerically encoded, so that each branch (group), leaf (object), and acorn (trap) is identified by a unique number known as an Object Identifier (OID). This identifier is a path to the information stored as the object s value, and provides the means by which the SNMP agent is able to locate the object in a device s MIB. An ASCII name is also assigned to each branch or OID, for convenience in identifying a management object. Figure 9-1 illustrates how MIB objects appear in the MIB Tools MIB Browser, showing the name and OID of the object. MIB Tools uses folders, acorns, and leaf icons to show branches, traps, and objects within a MIB. Each folder in the display indicates that more objects are contained in that level of the tree structure. Figure 9-1: Sample OID in the Internet Tree Displayed in MIB Tools 150 Modeling Your IT Infrastructure Administrator Guide

151 OneClick MIB Tools OneClick MIB Tools MIB Tools lets you browse MIBs, issue SNMP requests to network elements, import MIBs, and add MIB object and trap mapping support to SPECTRUM. You can use MIB Tools to accomplish many tasks, such as retrieving supported information directly from a given device to aid in troubleshooting and managing that device. You can customize your SPECTRUM network management environment by using MIB Tools to import into SPECTRUM the MIBs of network elements that are not yet supported in SPECTRUM. MIB Tools is a multifunctional MIB utility you can use to: Compile and import MIBs into the MIB Tools database. Browse MIBs for details of MIB objects and traps. Directly query and set values for MIB objects of network elements. Export MIB query result values for use in troubleshooting and creating simulations. Map new traps and MIB objects to create custom network element support in SPECTRUM. MIB Browser MIB Tools includes a MIB browser to browse and view MIB object details in the MIB Tools database, including object name, complete ObjectID, access, and description. For trap objects, you can view variable binding details. See MIB Tree Hierarchy Table on page 158 for more information on browsing MIBs. MIB Tools Database MIB Tools maintains a MIB database on the OneClick Web server. The default database consists of standard and proprietary MIBs. You can add MIBs to this database by importing them. The MIB Tools database is not used by SPECTRUM. MIB Import You can add MIBs to the MIB Tools database individually using the MIB Import feature. You can also import multiple MIB files using a script at the command line. There are several reasons that you may want to import MIBs into the MIB Tools database: If you wish to view new MIB objects in a MIB that is not imported. If you wish to retrieve MIB objects from a device whose MIB is not imported. If you wish to build OneClick views or create watches based on MIB objects not already supported in SPECTRUM, and the MIB is not already in the MIB database. Note that this is the first step. The second step involves mapping the MIB objects. See Import Individual MIBs on page 154 and Import Multiple MIBs on page 155 for information on importing MIBs into the database. Modeling Your IT Infrastructure Administrator Guide 151

152 Chapter 9: MIB and Trap Management Query Device MIBs You can perform SNMP GET, GET NEXT, and SET requests for MIB objects from network devices to retrieve and set information. See View MIB Object Values on page 159 for more information. Export MIB Tools Data You can export data displayed in MIB Tools for use outside of MIB Tools and OneClick. Data displayed in the Results, Attribute Support, and Trap Support tables can be exported in several file formats, including the.sim format for use in building device simulations using actual MIB data as part of troubleshooting device management issues with CA SPECTRUM support and development. See Export Query Results To Support Troubleshooting on page 162 Attribute and Trap Mapping in SPECTRUM You can add support for MIB objects that are not currently supported by SPECTRUM. You do this by creating attribute and trap support once you have imported the MIB into the MIB Tools database. Using these attributes, you can create OneClick views and Watches. Once you have mapped the traps and made the desired alarm assignments, SPECTRUM processes the trap accordingly. See Contents Panel Attribute and Trap Management on page 162 for more information on mapping object and trap support into SPECTRUM. MIB Tools User Interface The MIB Tools interface has two main panels that you use to find MIBs, and view MIB information: the Navigation panel and the Contents panel (Figure 9-2). 152 Modeling Your IT Infrastructure Administrator Guide

153 OneClick MIB Tools Figure 9-2: MIB Tools Interface Contact status indicator Contact criteria Hierarchy tree Results Navigation panel Launch MIB Tools You can launch MIB Tools from the main menu by selecting Tools, Utilities, MIB Tools. When you launch MIB Tools, it displays a status window showing the progress of retrieving and loading the MIB Tools database. Launch MIB Tools In Context You can also launch MIB Tools in the context of a specific network device. This allows you to communicate with the device and perform SNMP queries on it quickly in MIB Tools, as its contact criteria are automatically filled in. Modeling Your IT Infrastructure Administrator Guide 153

154 Chapter 9: MIB and Trap Management To Launch MIB Tools with Device Context To launch MIB Tools in the context of a specific network device, follow this procedure: 1. In the OneClick Console, locate the icon of the network element you want to investigate with MIB Tools. You can do this, for example, in either the Explorer tab of the Navigation Panel or the Topology tab of the Contents panel. 2. Right-click the element s icon and select Utilities, MIB Tools. MIB Tools opens, with the Contact Criteria pre-populated with the selected device s SNMP contact information. MIB Tools attempts to contact the device. If MIB Tools cannot contact the device an error message appears and the Contact Status indicator appears red. If the device is contacted, the Contact Status indicator appears green. A status window also appears showing the progress of retrieving and loading the MIB Tools database. See Contact Criteria on page 157 for more information about the MIB Tools Contact Criteria functionality. Navigation Panel MIB Management The Navigation panel lists the compiled MIBs in the MIB Tools database. The MIBs are organized by vendor and displayed alphabetically in ascending order by default. You can change the order to descending or back to ascending by clicking on the Name column heading. Use the Navigation panel to locate and select MIBs, setting the context for the Contents panel. When you select a MIB listed in the Navigation panel, its contents appear in the Hierarchy MIB tree view in the Browse tab of the Contents panel, or the Attribute and Trap Support views in the Map tab of the Contents panel. You can import individual MIBs into the MIB Tool database by clicking Add MIB located at the bottom of the Navigation panel. Import Individual MIBs To import a MIB into MIB Tools, the MIB file must be located on the file system accessible from the system you are running the OneClick Console on. You can only compile text formatted MIB files. Microsoft Word files or rich text format (containing control characters) cannot be compiled and are ignored. If you have a large number of MIBs to import, you can import multiple MIB files in bulk using the BulkMibImport command. See Import Multiple MIBs on page 155 for more information. Compile MIB Files MIB Tools compiles a MIB prior to importing it into the MIB Tools database. When you import a MIB file, MIB Tools recursively checks for any IMPORTS statements in the MIB file that reference other MIBs. The MIB files used to resolve IMPORTs statements are also compiled and placed in the <$SPECROOT>/MibDatabase/Dependent directory for subsequent import requests. Once you have located and compiled a referenced MIB, MIB Tools does not have to locate and compile it each time it is referenced by another MIB file. 154 Modeling Your IT Infrastructure Administrator Guide

155 Navigation Panel MIB Management To Import a MIB into MIB Tools Perform the following procedure to import a MIB file into the MIB Tools database. 1. Launch MIB Tools. 2. Click Add MIB in the Navigation panel. The Add MIB dialog box appears. 3. Click Browse to locate and select the file containing the MIB that you want to import. 4. Click Compile. If the MIB compiles successfully, a message stating the successful compile of the file appears in the Compiler section of the Add MIB dialog box. If the MIB does not compile successfully, errors and/or warnings generated during the compile appear in the Compiler section of the Add MIB dialog box. You will not be able to import a MIB that contains errors. Use the MIB Editor to edit the MIB and eliminate error conditions. 5. Click OK Once the MIB compiles successfully, click OK to close the Add MIB dialog and have the MIB added to the list in the Navigation panel. If the MIB references a new vendor, note that a new folder appears for that vendor. MIB Editor MIB Tools includes a MIB file editor that allows you to locate and correct errors identified during the compilation of a MIB file. To troubleshoot compiler errors, click Show Editor in the Add MIB dialog box to view the MIB file in the editor. Make any changes necessary to remove errors. You can search the file for alphanumeric strings, locate specific lines in the file, and save changes that you make to the file. Import Multiple MIBs Use the BulkMibCompile command included with MIB Tools to import large numbers of MIB files into MIB Tools database. This command allows you to migrate existing MIBs without using the MIB Tool utility GUI. BulkMibCompile is located in the default SPECTRUM installation directory on the OneClick server: <$SPECROOT>/MibDatabase/scripts/BulkMibCompile.sh This command uses the following format: BulkMibCompile [-u <MYSQL USER> ] [-p <MYSQL PASS> ] -d <MIB DIRECTORY> [-f <FILE MASK> ] [-skip_search ] -u <MYSQL USER> Specifies the MYSQL username. If you do not specify a username, BulkMibCompile uses the default MYSQL username root. You do not need to specify a username if the default username is correct. -p <MYSQL PASS> Specifies the MYSQL password. If you do not specify a password, BulkMibCompile uses the default MYSQL password root. You do not need to specify a password if the default password is correct. -d <MIB DIRECTORY> Specifies the directory containing the MIBs that you want to import. Modeling Your IT Infrastructure Administrator Guide 155

156 Chapter 9: MIB and Trap Management If you are running a Windows Cygwin bash shell, use the following format for specifying a directory: <$SPECROOT>/MibDatabase/scripts/BulkMibCompile.sh -d c:\\mibdirectory The double backslash (\\) is required because a single backslash (\) is defined as an escape character in this environment. Otherwise, use the following format: <$SPECROOT>/MibDatabase/scripts/BulkMibCompile.sh -d c:/mibdirectory-f <FILE_MASK> Use a file mask that includes all the MIB files in a directory that you want to import. Examples of file masks are: RFC* *RFC* *.mib -skip_search Use this option if all of the MIBs referenced by IMPORTS statements in the MIB files you are importing are in the MIB directory specified and are named using their MODULE-NAME. Using -skip_search speeds up the import process by having the compiler resolve IMPORTS statements. If you do not use -skip_search, the BulkMibCompile code searches each MIB for IMPORTS statements and attempt to resolve them. This process is repeated during the compiling of each MIB. -init Use this option to re initialize the MIB Tools database, clearing it of all MIBs. Example: Import All MIBs In a Directory <$SPECROOT>/MibDatabase/scripts/BulkMibCompile.sh -d /usr/mibstocompile -f RFC* Once a MIB is successfully compiled, it is immediately added to the database and will overwrite any existing MIBs with the same MIB MODULE-NAME. If there are any compilation errors, the errors are displayed to the screen and compilation will continue with the next MIB being imported. To Re Initialize the MIB Tools Database Use the following command to re initialize a MIB Tools database. <$SPECROOT>/MibDatabase/scripts/BulkMibCompile.sh [-u <MYSQL USER> ] [-p <MYSQL PASS> ] -init To Copy an Existing MIB Tools Database to Another OneClick Web Server Use the following procedure to populate the MIB Tools database of another OneClick server from the primary OneClick server. 1. Copy the contents of <$SPECROOT>/MibDatabase and <$SPECROOT>/MibDatabase/Dependent on the primary OneClick server to the same directories on the secondary OneClick server. 2. On the secondary OneClick server, run BulkMibCompile to import the MIBs you copied into the $<SPECROOT>/MibDatabase: <$SPECROOT>/MibDatabase/scripts/BulkMibCompile.sh -d <$SPECROOT>/MibDatabase -skip_search Once the script completes, the databases on the original and destination OneClick servers are identical. 156 Modeling Your IT Infrastructure Administrator Guide

157 Contents Panel Browse MIBs Contents Panel Browse MIBs The Contents panel has two functional tabs, the Browse tab and the Map tab. The Browse tab allows you to browse MIBs in the MIB Tools database, and to query devices on your network to obtain or set MIB object values. The Browse tab is described in the following sections. Browse Tab The Browse tab has three main sections: Contact Criteria, Hierarchy, and Results. Contact Criteria You can contact a device and see the contact status for a device using the Contact Criteria section. The device does not need to be modeled or represented in SPECTRUM to contact it using Contact Criteria. Table 9-1 lists and describes the Contact Criteria parameters. Table 9-1: Device Contact Criteria Parameter Device Version Community String V3 Profile Landscape Secure Domain Port Retry Count Timeout (ms) Description Enter the IP address or hostname for the device you want to contact. Select the version of SNMP to use. Note: SNMP v2c and v3 are available only if you have the Secure Domain Manager add-on application installed or the SNMP v3 Proxy software installed. Enter the community string required to access the device. If you are using SNMP v3, select the profile required to contact the device from the drop-down list. If you need to create a profile, click Profiles. Refer to SNMP Information on page 46 for information on creating SNMP v3 profiles. Advanced Option; if you have a Distributed SpectroSERVER environment, select the landscape from which the SNMP request should be initiated. Advanced Option; if you have the Secure Domain Manager add-on application installed with secure domains configured, select from the drop-down list the secure domain to which the SNMP request should be forwarded. Advanced Option; enter the value of the UDP port to contact the device on. The default value is 161. Advanced Option; enter the number of times to retry contacting the device before MIB Tools stops attempting to contact the device. The default value is 3. Advanced Option; enter the timeout value in milliseconds to wait before trying to contact the device again. The default value is 3,000. Other features of the Contact Criteria section are: List of Contacted Devices. A list of the last 10 devices successfully contacted using Contact Criteria is available in a drop-down list at the Device field. Modeling Your IT Infrastructure Administrator Guide 157

158 Chapter 9: MIB and Trap Management Contact Status Indicator. The color of the line surrounding the Contact Criteria section indicates the status of contact with the device. Table 9-2 describes the contact status indicator colors. Table 9-2: Contact Status Indicator Colors Contact Status Color Green Yellow Red Blue Description Contact with device was successful. Contact with device in progress Contact with device was unsuccessful. Contact with device has not been initiated. To Contact a Device Use the following procedure to contact a device using MIB Tools: 1. With MIB Tools running, select the Browse tab. 2. Enter the hostname or IP address for the device on your network you want to contact in the Device field. 3. Enter the version of SNMP to use in contacting the device in the Version field. 4. Enter the community string to use in contacting the device in the Community String field. 5. If you are using Secure Domain Connector, or if you want to change any of the default values for SNMP to use in contacting the device, click Advanced. See Table 9-1 for more information. 6. Click Contact to initiate contact with the device. 7. The Contact Status Indicator appears yellow while MIB Tools is attempting to contact the device. If contact is established, the indicator appears green. If MIB Tools cannot establish contact with the device, the MIB Tools Contact Failure message box appears, containing a message describing the cause of the failure, such as SNMP request timed out and the Contact Status Indicator then appears red. MIB Tree Hierarchy Table The default view of the Hierarchy table displays the entire MIB Tools database starting at the iso branch. Browse MIBs. You can browse the MIB Tools database and view detailed information for each group, object, and trap in the MIB database. To browse an individual MIB, select the MIB in the Navigation panel, and then using the MIB Hierarchy tree to navigate the MIB by expanding or collapsing the folders to view groups, objects, and traps. Search MIBs. You can search the MIB Hierarchy tree for a text string by entering it into the Search field. Press Enter after typing the string or click Next to see the first instance of the string in the Hierarchy tree. Continue clicking Next to see each successive instance of the search string. Click Previous to find the previous instance of the search string appearing in the Hierarchy tree. 158 Modeling Your IT Infrastructure Administrator Guide

159 Contents Panel Browse MIBs The Hierarchy tree table appears by default with the Name and Object ID columns visible. A third column, Access, is hidden by default. These are described in Table 9-3. Table 9-3: MIB Tree Hierarchy Table Fields Column Name Object ID Access Description The name of the MIB object. The Object ID of the MIB object. The Access type for the object can be read-only, read-write, readcreate, or not-accessible. To view or hide columns in the Hierarchy tree, right-click on one of the table headings. The Table Preferences dialog box for the Hierarchy tree appears. See the OneClick Console User Guide (5130) for more information on setting table preferences. Hierarchy Tool Bar The Hierarchy tool bar provides the following functions: View MIB object details. You can display MIB detail information for the group, object, or trap selected in the hierarchy tree by clicking in the tool bar. The detail information displayed for the selected object is taken directly from the MIB. SNMP GET and GET_NEXT. You can retrieve the value of a selected MIB object on a specific device on your network. See View MIB Object Values on page 159 for more information. SNMP SET. You can set the value of a selected MIB object on a specific device on your network. See Set MIB Object Values on a Device on page 160 for more information. Access MIB Objects on Network Devices The MIB for the device you are querying does not have to be imported into the MIB Tools database. If the MIB is not in the MIB Tools database, you will need to know the Object IDs of the objects you will query. Additionally, the network device you query does not have to be modeled in SPECTRUM. View MIB Object Values The SNMP GET and GET_NEXT functions in the Hierarchy tool bar become available after selecting a readable object in the Hierarchy tree. Use them to view MIB object values on network devices. Viewing objects from MIBs not in MIB Tools database. If the MIB objects you want to query are not in the MIB Tools database, you will need to input the OID in the SNMP GET dialog and select either GET or GET_NEXT from the drop down menu. To launch the SNMP GET dialog, choose an object in the Hierarchy tree that is a table object, then select. GET_NEXT only for group and table objects. If you select a group object (contains other groups and individual objects) or a table object (contains multiple instances of the same object) in the Hierarchy tree, and select GET from the tool bar or right-click menu, the SNMP GET dialog appears. You must change the request type to a GET_NEXT in the drop down menu before proceeding. Performing a GET request on a group object fails. Modeling Your IT Infrastructure Administrator Guide 159

160 Chapter 9: MIB and Trap Management To Perform an SNMP GET_NEXT Use the following procedure to query a MIB object in the MIB Database on a network device. 1. Establish contact with the device on which you want to query the MIB object. See To Contact a Device on page 158 for information about contacting a device. 2. Navigate to the MIB object you want to query. 3. Select Query/GET_NEXT ( ) in the hierarchy tool bar or right-click menu. 4. The Query/GET_NEXT results appear in the Results table. To Perform an SNMP GET 1. Establish contact with the device on which you want to query the MIB object. See To Contact a Device on page 158 for information about contacting a device. 2. Navigate to the group object or leaf that you want to query. 3. Click GET ( ) in the hierarchy tool bar or select it from the right-click menu. 4. If you selected a leaf object in the hierarchy, MIB Tools performs the GET request. If successful, the result appears in the Results table. If the GET request fails, an error message appears stating either the device was not reachable or the MIB object does not exist on the device. If either of these conditions occur, verify that the device is reachable, and that the MIB object is supported by the device. If you selected a group object or list object (contains multiple instances), the SNMP GET dialog appears. The Object ID field is filled in with the OID of the item selected in the Hierarchy tree. If this is the object that you want to query, leave the value; otherwise, enter the value of the Object ID that you want to query. If there is more than one instance of the MIB object on the device, enter the value of the instance to query in the Instance field. The default value for Instance = 0. You need to change the Request Type to GET_NEXT. 5. Click OK. 6. The results of the query appear in the Results table. If no results appear, either the object is not supported by the device, the object is not-accessible, or the device is unreachable. If you do not get any results from the query, verify that the device is reachable, and that the MIB object is supported by the device. Set MIB Object Values on a Device You can only set values for MIB objects that have write access, such as read-write. View the Access value for MIB objects in the Hierarchy tree Access column (see MIB Tree Hierarchy Table on page 158 for information displaying the Access column). To Perform an SNMP SET Perform the following procedure to set the value of a MIB object on a network device. 1. Establish contact with the device on which you want to set the value of the MIB object. See Contact Criteria on page 157 for information about contacting a device. 2. Navigate to the MIB object you want to set. 3. Click SNMP SET ( ) in the Hierarchy tool bar or select it from the right-click menu. 160 Modeling Your IT Infrastructure Administrator Guide

161 Contents Panel Browse MIBs The SNMP SET dialog box appears. 4. Verify that the correct MIB object is selected in the dialog box or enter the OID for the object you want to set (as in the case of a MIB that is not in the MIB Tools database), 5. Enter the Instance of the object you want to set. 6. Enter the Value you want to set the object to. Depending on the object type, you may be able to select a value from a drop-down list. Click OK. 7. A window appears, indicating whether or not the SET action was successful. If the action was unsuccessful, a reason is provided. Troubleshooting a Failed SET Action If the set action fails, use the following check list for troubleshooting: 1. Verify that the device is reachable by trying to contact it using the Contact Criteria section of the Browse tab. 2. If you can contact the device, verify that you can perform a GET action on the device for the MIB object you attempted to SET. 3. Verify that the MIB object has read-write access if the MIB is part of the MIB Tools database by looking at the value for the Access parameter in the Hierarchy tree. If the MIB is not part of the MIB Tools database, you will need to verify this from the MIB directly. 4. If all these conditions are met, verify the Community String entered in the Contact Criteria section is the correct one for the device. You can do so if the device is modeled in OneClick by looking at the Community Name value in the OneClick Information tab SPECTRUM Modeling Information sub view. Device Query and SET Results The Results section of the Browse tab displays the results of SNMP GET, GET_NEXT, and SET requests in a table. The Results table appears with the Object Name, Instance, Type, and Value columns visible by default. The Object ID and Access columns are hidden by default. Table 9-4 describes each of the Results table columns. Table 9-4: Results Table Columns Column Object Name Instance Type Value Object ID Access Description The name of the MIB object queried. The instance of the object queried. The object type, such as Integer, Counter, IP Address, Octet String, Gauge, Time Ticks. The value of the MIB object read from the device. The Object ID of the object. The Access type for the object can be read-only, read-write, readcreate, or not-accessible. Modeling Your IT Infrastructure Administrator Guide 161

162 Chapter 9: MIB and Trap Management To view or hide columns in the Results table, right-click on one of the table headings. The Results Table Preferences dialog box appears. See the OneClick Console User Guide (5130) for more information on setting table preferences. Auto Clear. If Auto Clear is selected, the contents of the Results table are cleared each time you query a device. If you want to view sequential SNMP queries, make sure Auto Clear is not selected. Results tool bar. Using the buttons in the Results tool bar, you can perform the following tasks: Clear the Results table. Export the Results table contents to a file. Perform an SNMP GET for a selected object in the Results table. Perform an SNMP SET on a selected object in the Results table (available only for objects that have read-write access). Filter Results. You can filter the Results table to display only results that contain specific strings by entering the string you are looking for in the Filter field. Only results containing the string appear as you enter the information. Export Query Results To Support Troubleshooting To aide in troubleshooting a problem, you may be asked by CA SPECTRUM technical support to provide a.sim file exported from MIB Tools containing information to use in building a simulation of your device. To Export Query Results Obtain a detailed SNMP snapshot of your device to provide CA SPECTRUM technical support and development using the following procedure. 1. Perform a query typically from the internet branch on the device that you require support for. See View MIB Object Values on page 159 for the procedure to query a device. 2. Once the query is complete, click in the Results table tool bar. The Export table data to file dialog box appears. 3. Select Simulation (*.sim) from the Save as type list of options on the right side of the dialog box. Give the file a name similar to the device the you queried on your network for easy recognition. 4. Save the file to your local file system. Contents Panel Attribute and Trap Management You can use the Map tab in the Contents panel to: Create attributes in the SPECTRUM database from MIB objects. Map traps in SPECTRUM. Identify the MIB objects that have been previously mapped to attributes in the SPECTRUM database using MIB Tools. Identify all trap support in SPECTRUM. 162 Modeling Your IT Infrastructure Administrator Guide

163 Contents Panel Attribute and Trap Management Map Tab The Map tab is composed of the Attribute Support and Trap Support sections. The Map tab identifies the objects and traps for a selected MIB that are supported in SPECTRUM by displaying the SPECTRUM Attribute ID for an object, and the SPECTRUM Event ID for a trap. Objects without support do not have an Attribute ID or Event ID, and have the value None in the Landscapes column. Attribute Support Table The Attribute Support table displays the information for MIB Objects and SPECTRUM attribute support described in Table 9-5. The Attribute Support table does not reflect SPECTRUM attribute support that exists in the SPECTRUM model type catalog; it only reflects SPECTRUM attribute support created using MIB Tools. Table 9-5: Attribute Support Table Information Column Name Identifier Attribute ID Landscapes Description Name of the object in the MIB Object ID in the MIB The SPECTRUM Attribute ID value; if the object is not supported in SPECTRUM, the field is blank. If there is a conflict regarding the assigned Attribute ID for the object in a DSS environment, Conflict appears in the field. See Attribute Support Conflicts on page 168. Indicates if the attribute is supported on Some, All, or None of your Landscapes. See Incomplete Trap and Attribute Support on page 168 for more information about a value of Some. Export Attribute Support table. Click Export ( ) to export the contents of the Attribute Support table to a file for use outside of OneClick. Filter Table Contents. Enter a string to filter the Attribute Support table contents on in the Filter field. Only entries containing the string appear in the table. Create Attributes To support a MIB object in SPECTRUM, a SPECTRUM attribute must be mapped to the MIB object. Attribute identifiers (IDs) are used to create these mappings. To create support for the MIB objects in the MIB Tools database, you need to create an attribute ID for the MIB objects. Click Create Attributes to create SPECTRUM Attribute IDs for the objects that appear in the Attribute Support table that are not already supported in SPECTRUM. After you create attributes, you must stop and then start the OneClick server in order for the new attributes to be visible in OneClick. See the OneClick Administration Guide (5166) for information on how to stop and start the OneClick server. To Create New Attribute Support To create new attribute support in SPECTRUM, perform the following procedure: 1. In MIB Tools, select the MIB in the Navigation panel for which you want to create attribute support. The list of MIB objects appears in the Attribute Support table. Modeling Your IT Infrastructure Administrator Guide 163

164 Chapter 9: MIB and Trap Management 2. If there are MIB objects which do not have corresponding Attribute IDs, then click Create Attributes. 3. Click OK in the confirmation window to continue creating the attributes on all SpectroSERVERs. 4. The MIB Tools Creation Results window appears, showing the status of the Create Attribute action including the number of attributes created for each Landscape. 5. Click Close to return to MIB Tools. 6. The Attribute Support table now shows the Attribute ID created for each object. The new attributes are now available for use by all model types in the SPECTRUM modeling catalog. Use this information to develop custom views or watches or other features to manage your network devices. Note: You must restart the OneClick server in order for the new attributes to be visible in OneClick. See the OneClick Administration Guide (5166) for information on how to stop and start the OneClick server. Trap Support Table The Trap Support table allows you to view the traps defined in the MIB selected in the Navigation panel and all default and custom SPECTRUM Event IDs mapped to them. The Trap Support table displays the trap and SPECTRUM Event information described in Table 9-6. Table 9-6: Trap Support Table Information Column Name Identifier Event ID Landscapes Description Name of the trap in the MIB Trap Object ID in the MIB SPECTRUM Event ID; If the trap is available for only select SPECTRUM models, the Event ID appears as Partial. See Identify and Resolve Partial Trap Support on page 166 for information on resolving partial trap mappings. If the trap has different Event IDs mapped on different SpectroSERVERs in a DSS environment, the Event ID appears as Conflict. See Trap Disposition Conflicts on page 169. Indicates if the trap is supported on Some, All, or None of your Landscapes. See Incomplete Trap and Attribute Support on page 168 for more information about a value of Some. The Trap Support section includes the following functionality: Remap All Conflicts. Allows you to remap traps that either are only partially supported in SPECTRUM, or that have inconsistent, conflicting support across SpectroSERVERs in a DSS environment. Remapping traps makes the trap available to all model types, and on all SpectroSERVERs. See Contents Panel Attribute and Trap Management on page 162 for more information. Export Trap Support table. Click Export ( ) to export the contents of the Trap Support table to a file for use outside of OneClick. Filter Table Contents. Enter a string to filter the Trap Support table contents on in the Filter field. Only entries containing the string appear in the table. 164 Modeling Your IT Infrastructure Administrator Guide

165 Contents Panel Attribute and Trap Management Map Traps Create Trap Support You can create new support in SPECTRUM for traps defined in MIBs imported in the MIB Tools database. This allows you to add custom trap support for new devices not yet supported in SPECTRUM, or to change the way a trap is currently supported in SPECTRUM. Note: If you have a fault tolerant SpectroSERVER environment, MIB Tools will not allow you to map traps on a secondary SpectroSERVER if your primary SpectroSERVER is down. If you have multiple primary SpectroSERVERs and none of them are available, you will not be able to create trap support until one of your primary SpectroSERVERs are available. Custom Trap Support File Details When you map traps using MIB Tools, entries are generated in the following files on all SpectroSERVERs in your DSS environment: <$SPECROOT>/custom/Events/EventDisp <$SPECROOT>/custom/Events/AlertMap The mapping information for a trap in these files overrides any mapping information that previously existed for that same trap in other files or directories on the SpectroSERVER. Additionally, when you map traps, the following files are generated and placed in the following directories on only the OneClick server that you are connected to: <$SPECROOT>/custom/Events/CsEvFormat There is a specific Event Format file for each event generated by SPECTRUM. These files define the event text that appears in the OneClick Alarm and Event lists. <$SPECROOT>/custom/Events/CsPCause This is a specific Probable Cause file for each alarm generated by SPECTRUM that appears in the OneClick Alarm Details view. These files define the alarm text. This happens only if you select an Alarm Severity Level when you map a trap. <$SPECROOT>/custom/Events/CsEvFormat/EventTable This file maps any varbind sent with a trap to enumerated values displayed in the event message directories. You must manually copy these three directories from your primary OneClick server to other OneClick servers in a multiple OneClick server environment. If you use the command line interface (CLI) commands show alarms or show events, or SPECTRUM Alarm Notification Manager (SANM), then you will want to copy the contents of these three directories to all SpectroSERVERs in <$SPECROOT>/SG-Support. See the SPECTRUM Concepts Guide (0647), the Event Configuration User Guide (2260), and the Event Configuration Files Guide (5070) for more information about SPECTRUM alarm and event support files. To Create Trap Support To create new trap support in SPECTRUM, use the following procedure: 1. In MIB Tools, select the MIB in the Navigation panel for which you want to create trap support. The list of traps for the MIB appears in the Trap Support table. If there are traps not already supported by SPECTRUM, the Map Traps button is available. Modeling Your IT Infrastructure Administrator Guide 165

166 Chapter 9: MIB and Trap Management Any traps with partial support appear in the Trap Support table with Partial in the Event ID column. If you want to create global trap support in SPECTRUM for these traps, you must remap them before continuing. Follow the procedures in Identify and Resolve Partial Trap Support on page 166 then continue with the next step. 2. Click Map Traps. The Assign Trap Alarms window appears. 3. Select the Alarm Severity for the alarm that SPECTRUM will generate when it receives each trap listed by clicking set in the Alarm Severity column. You may decide a trap will not generate an alarm, in that case, select None. 4. Click OK to map the traps on all SpectroSERVERs. 5. The Trap Support Results window appears, showing the status of the Map Traps action. When the action completes, the results appear, listing the number of traps created for each Landscape. 6. Click Close to return to MIB Tools. 7. The Trap Support table now shows the Event ID created for each trap. The new Events are now available for use by all model types in the SPECTRUM modeling catalog. Identify and Resolve Partial Trap Support This section discusses how to identify when a trap is supported on only select model types in the SPECTRUM modeling catalog, and how to change the support to all model types. Global Trap Support. When a trap is globally supported in SPECTRUM it is available for use by all model types. The Event ID value for a globally supported trap appears in the Event ID column in the Trap Support table. Partial Trap Support. When a trap is partially supported in SPECTRUM it is available to only select model types. The Event ID value for a partially supported trap reads Partial. You can choose to leave the trap partially supported, which is recommended, or you can remap the trap to make it globally supported in SPECTRUM. Note: If you remap the trap, you could be masking useful functionality provided by SPECTRUM, in essence turning it off. To change partial trap support to global, you must first remove the partial mapping, and then remap the trap. To Remove Partial Mapping for a Single Trap To remap a single trap with partial support, perform the following procedure. 1. With the trap you want to remap displayed in the Trap Support table, click Partial in the Event ID column for that trap. The Partial Trap Support window appears, displaying the trap Event ID, the landscapes it is available on, the MIB object name, and Object ID. 2. Click Remap. The Confirm Remap window appears. 3. Click Yes to continue remapping the trap. The remapped trap appears in the Trap Support table without an event ID value and Partial no longer appears the Landscape column. The previous partial mapping is now removed. 166 Modeling Your IT Infrastructure Administrator Guide

167 Multiple SpectroSERVERs 4. You can remap these traps globally by following the procedure listed in To Create Trap Support on page 165. To Remove Partial Mapping from All Traps in a MIB To remove the partial mapping from all traps for a selected MIB, perform the following procedure. 1. Select the MIB containing the traps you want to remove partial support for in the Navigation panel. The traps with partial support appear in the Trap Support table. 2. Select Remap All Conflicts All partial trap support is removed for the traps. Verify that the traps do not have an event ID and that Partial does not appear the Landscape column. The previous partial mapping is now removed. 3. You can remap these traps globally by following the procedure listed in To Create Trap Support on page 165. Multiple SpectroSERVERs MIB Tools supports a Distributed SpectroSERVER (DSS) environment in the following ways: Offline SpectroSERVERs. MIB Tools recognizes when any SpectroSERVERs in a DSS environment are offline while attempting to create Event and Attribute IDs for MIB objects and notifies the user. Incomplete Trap and Attribute Support. MIB Tools identifies when MIB objects are supported on some but not all SpectroSERVERs in a DSS environment. Resolve Incomplete Support. MIB Tools provides functionality to resolve incomplete trap support. See Create Consistent Support Across a DSS Environment on page 168 for more information. Conflicting Support. MIB Tools identifies MIB objects that have conflicting Event ID or Attribute ID mappings on multiple SpectroSERVERs in a DSS environment. See Incomplete Trap and Attribute Support on page 168 for more information. Resolve Trap Conflicts. MIB Tools provides functionality to resolve trap disposition conflicts. See Resolve Trap Disposition Conflicts on page 169 for more information. Conflicting support conditions are identified in the Attribute Support and Trap Support tables as described in Map Tab on page 163. Best Practice for Maintaining MIB Tools in a DSS Environment Use the following guidelines to maintain synchronization among SpectroSERVERs in a DSS setup: Do not create attribute and trap support if any of the SpectroSERVERs are down. A warning dialog appears when you attempt to create attributes or map traps. Always create consistent support for attributes and traps on all SpectroSERVERs (as indicated in the Attribute and Trap Support tables). See Incomplete Trap and Attribute Support on page 168 for information on how to resolve this condition. Always resolve trap disposition conflicts when they appear. See Trap Disposition Conflicts on page 169 for more information. Modeling Your IT Infrastructure Administrator Guide 167

168 Chapter 9: MIB and Trap Management Attribute Support Conflicts When inconsistent support for an attribute occurs in a DSS environment, an attribute conflict condition exists. Usually this results when an attribute is mapped to different Attribute IDs on one or more SpectroSERVERs. When an attribute conflict exists, the Attribute ID value for that attribute in the Attribute Support table reads Conflict. Click Conflict and the Attribute Disposition Conflict window appears, listing each Landscape and the Attribute ID for the attribute. When a conflict occurs, at least one SpectroSERVER will have a different Attribute ID or no Attribute ID for the attribute. Resolve Attribute Support Conflicts To resolve attribute support conflicts, you will need to synchronize the modeling catalogs on your SpectroSERVERs. See the Distributed SpectroSERVER Guide (2770) for information on how to resynchronize SpectroSERVER modeling catalogs and other database information. Incomplete Trap and Attribute Support When a trap or attribute is supported on some but not all SpectroSERVERs in a DSS environment, it is identified by the value Some appearing in the Landscapes column in their respective table. Click Some and the Landscape Details window appears. Each Attribute ID or Event ID to Landscape mapping for the selected MIB object appears in this window. Landscapes that the selected MIB object is not mapped on do not have a value. Create Consistent Support Across a DSS Environment If you want to create consistent support across your DSS environment for traps and attributes that are supported on only some of your SpectroSERVERs, you must remap the traps and recreate the attributes once all of your SpectroSERVERs are running. To Create Consistent Attribute Support Across a DSS Environment 1. In MIB Tools Navigation panel, Select the MIB containing the attributes for which you want to create consistent support. 2. In the Map tab, verify that there are attributes in the Attribute Support table with the value Some appearing in the Landscapes column. 3. Click Create Attributes. Click OK in the confirmation window. The Attribute Creation Results window displays the status and results of the Create Attribute action. 4. Click OK to close the Attribute Creation Results window. 5. The value All appears in the Landscapes column for the all the attributes. To Create Consistent Trap Support Across a DSS Environment 1. In MIB Tools Navigation panel, Select the MIB containing the traps for which you want to create consistent support. 2. In the Map tab, verify that there are traps in the Attribute Support table with the value Some appearing in the Landscapes column. 3. Click Map Traps. The Assign Trap Alarms window appears. 168 Modeling Your IT Infrastructure Administrator Guide

169 Multiple SpectroSERVERs 4. If desired, select the Alarm Severity for the alarm that SPECTRUM will generate when it receives each trap listed by clicking set in the Alarm Severity column. You may decide a trap will not generate an alarm; in that case, select None. 5. Click OK to map the traps on all SpectroSERVERs. 6. The Trap Support Results window appears, showing the status of the Map Traps action. When the action completes, the results appear, listing the number of traps created for each Landscape. 7. Click Close to return to MIB Tools. 8. The Trap Support table now shows the Event ID created for each trap. Trap Disposition Conflicts When inconsistent support for a trap occurs in a DSS environment, a trap disposition conflict condition exists. Examples include: A trap is mapped to different Event IDs on one or more SpectroSERVERs. A trap is disposed differently on one or more SpectroSERVERs. For example, a trap could be disposed to a minor alarm on one SpectroSERVER, and a major alarm on another. A trap can be utilizing an Event Rule for complex processing, and the other instance of the trap is not. When a trap disposition conflict exists, the Event ID value for that trap in the Trap Support table reads Conflict. Click Conflict and the Trap Disposition Conflict window appears, listing each Landscape and the Event details for the trap. Resolve Trap Disposition Conflicts There are two approaches to resolving a trap disposition conflict: Determine which mapping is the desired one by reviewing the Event details in the Trap Disposition Conflict window. Next, synchronize the conflicting Events on the other Landscape (SpectroSERVER) by editing the appropriate EventDisp file Remap the trap on all SpectroSERVERs in your DSS environment. This creates consistent support for the trap on all SpectroSERVERs. To Resolve Trap Disposition Conflicts Using Remap All of the SpectroSERVERs in your DSS environment should be up and running to resolve a trap support conflict. 1. Locate the trap in conflict in the Trap Support table. 2. Do one of the following: For multiple trap disposition conflicts, select Remap All Conflicts. Continue to step 5. For a single trap, click Conflict in the Event ID column. The Trap Disposition Conflict window appears, listing each Landscape and the Event ID for the trap. Modeling Your IT Infrastructure Administrator Guide 169

170 Chapter 9: MIB and Trap Management 3. Click Remap. The Confirm Remap window appears. 4. Click Yes to continue remapping the trap. The Confirm Remap window closes, returning you to the Trap Support table. The trap will have a value of Some or None in the Landscape column. 5. Click Map Traps to create a new Event ID for the trap on all the SpectroSERVERs in the DSS environment. Multiple OneClick Servers Using MIB Tools in an environment with multiple OneClick servers requires several manual steps to maintain MIB Tools synchronization across all OneClick servers. This section outlines the best practices to maintain synchronization, and the procedures to accomplish them. Best Practices to Maintain Synchronization When you import MIBs into the MIB Tools database and create trap and attribute support, information is written to all SpectroSERVERs in your DSS environment. However, information required by OneClick to support the traps and attributes is written only on the OneClick server that you are connected to using the OneClick Console. If you have multiple OneClick servers in your environment, you need to maintain synchronicity among the MIB Tools databases and support files for new attribute and trap support. Synchronize MIB Tools Databases and Support Files Across OneClick Servers Use the following process to synchronize and update MIB databases and support files on your OneClick servers: 1. Designate one of your OneClick servers as the primary server that contains the primary MIB Tools database. Import all MIBs and create attribute and trap support first on this primary OneClick server. 2. Distribute the MIB Tools database to other OneClick servers from the primary server. See To Copy an Existing MIB Tools Database to Another OneClick Web Server on page 156 for the details on this procedure. 3. Distribute OneClick support files created for events and alarms from the primary OneClick server to the other OneClick servers. See Custom Trap Support File Details on page 165 for information about these support files. 170 Modeling Your IT Infrastructure Administrator Guide

171 Index A Access 159, 161 Add Events to Alarms 132 Advanced Options 45 Age Out Alarm Time (Hours) 132 Age Out Residual Alarms Only 132 Attribute Maintenance Mode Attributes 144 Roll-up Alarm 144 Orange Threshold Level 145 Red Threshold Level 145 Value When Orange 145 Value When Red 145 Value When Yellow 145 Yellow Threshold Level 145 SpectroSERVER Control 128 VNM Alarm Management Disable Initial Alarms 133 Disable Maintenance Alarms 133 Disable Suppressed Alarms 133 Initial and Suppressed alarms 133 Autodiscovery Community Names 131 Create (Fanout) 130 Create LANs (IP subnets) 130 Create Pingables 131 Create WA_Link Models 130 Debug AutoDiscovery 131 Debug Device at IP 131 Discover Connections 131 New Devices in Maintenance 131 Physical Addresses 130 Proprietary Discovery Tables 130 SNMP Ports 131 Trap-Based Continuous Discovery 130 Unmanaged Trap Discovery 131 Live Pipes 132 Alarm Linked Ports 132 Port Always Down Alarm Suppression 132 Suppress Linked Port Alarms 132 Online Database Backup Automatic Backups 128 Backup Compression 128 Backup Directory 128 Backup Interval 128 Begin Backup Now 128 Minimum Required Disk Space 128 New Backup Date & Time 128 Prefix for Backup File Name 128 SpectroSERVER Auto Connects 128 Copy Users when Copying Groups 129 Device Thresholds 128 Minimum Disk Space (kbytes) 129 Model Naming Order 129 Server Polling 129 Unmanaged Trap Handling 128 Use Fully Qualified Hostname 129 VLAN Configuration 129 Attribute Editor 133 accessing 133 Attribute Edit Results 136 defining user-specified attributes 137 Interface Configuration 143 results 136 Stale Interfaces 144 Undo button 136 User Defined Attributes 137 using Search 139 working in dialog box 134 Attribute Support

172 Index Attribute Support Conflicts 168 Attributes, user-specified 137 Auto Clear 162 Auto Export 46 Automatically Reconfigure Interfaces 98 B background characteristics 112 branch (MIB) 150 bring to front 114 Browse Tab 157 BulkMibCompile 155 C Clear the Results table 162 color for lines and shapes 111 community string import 56 Compile MIB Files 154 Connections (pipes) defined 76 dynamic connection 77 removing 77 static connection 77 Contact Criteria 157 Containers adding to views 69 Create Attributes. 163 Create Folders 43 Create Model by Host Name 71 Create Model by IP Address 71 D Debug Options 131 delete modeled elements 75 Device icons 27 Device Identification Manager 115 Device Reconfiguration Automatically Reconfigure Interfaces 98, 99 Create Sub-Interfaces 99 Discover Connections 100 Discover Connections After Link-Up Events 98 Discovery After Reconfigure 99 Reconfiguration Advanced Subview 101 Reconfigure Model 100 Reconfigure SNMP MIBs 100 Reevaluate Model Name 101 Rename Interface Models 101 Topologically Relocate Model 100 Device Type 115 Device Type Identification table 116 Device Type Name 116 devices, adding to views 71 DeviceTypeDiscEnable 123 disable stale interface functionality 144 Discovery configuration, defined 39 defined 38 defining configurations 54 modeling configuration 57 results list 63 session 61 ways to use 38 Discovery dialog box features defined 41 how to access 40 Discovery Options 45 Discovery results table 48 discovery session 47 Discovery Status 47 Discovery tab 47 Discovery terms 38, 105 Distributed SpectroSERVER (DSS) 167 Dynamically Import IP Addresses 45 E Edit mode 106 accessing, procedure 107 tool bar, defined 108 Editing view characteristics 110 Enable Stale Interface Alarms 144 Entity Stacking 143 Export.sim files 162 Export Attribute Support table. 163 Export Table Data 116 Export the Results table 162 Export Trap Support table 164 export Universe view 76 F Filter advanced, discovery 63 Filter Table Contents. 163 font properties for text 111 G Generate Alarm Events 132 GET_NEXT 159 Global Collections 172 Modeling Your IT Infrastructure Administrator Guide

173 Index dynamic members defined 80 generating reports 81 managing connections (pipes) 81 modeling defined 80 procedures defined 82 static members defined 81 tips for creating 81 Global Trap Support 166 group and ungroup items 113 Hierarchy 158 H ICMP 131 Icons aggregate icon, defined 25 defined 25 individual, defined 25 shape and symbol, defined 26 themes, defined 26 types, defined 26 ifstacktable 143 import community string 56 Import IP Addresses 44 Import IP addresses or range 55 Import MIBs 155 Instance 161 Interface Configuration 143 Admin Status 143 Create Sub-Interfaces 143 Interface Model Name Suffix 143 Stale Interface Age Out (min) 144 Use If Entity Stacking 143 Interface Thresholds % Utilization Threshold, % Utilization Reset 98, 148 Discarded Threshold 98, 148 Error Rate Threshold 98, 148 Packet Rate Threshold (packets/sec) 98, 148 IP Boundary List 44 IP Exclusion List 45 IP Redundancy Device Primary Address 102 IP wildcard use 55 Launch MIB Tools 153 Launch MIB Tools with device context 153 I L line weights 112 lines, adding to views 110 Live pipes icon representation 27 Log When Device Cannot Be Contacted 129 Loopback if Description 129 Loopback Interfaces 66, 129 M Map Tab 163 Methods of modeling 32 MIB Editor 155 MIB object 149 MIB Tools summary 151 model security 31 Model State 48 Modeled elements grant or deny access 31 Modeling configuration, procedure 57 enhancing views 106 get started references 34 Getting Started 17 manual 67 manual, Global Collections 80 manual, TopOrg 91 manual, Universe 68 manual, World 89 methods, defined 32 tips 32 modeling features 13 modeling tips 32 Modified 116 Network group icons 27 N O Object Identifier (OID) 150 Off page icons 27 Online 127 Online Database Backup 127 P Partial Trap Support 166 ping 131 Modeling Your IT Infrastructure Administrator Guide 173

174 Index Polling Interval 147 Polls to Log Ratio 147 Proprietary Discovery Protocols Cabletron Discovery Protocol 130 Cisco Discovery Protocol 130 Extreme Discovery Protocol 130 Nortel Discovery Protocol 130 Query MIB Objects 159 Q R Reconfiguration Subview 101 Redundant Device Connections Enable Redundancy 103 Generate Redundancy Alarms 103 IP Redundancy Subview 102 Primary Address 103 Redundancy Excluded Addresses List 103 Redundancy Preferred Addresses List 102 Remap All Conflicts. 164 Resolve Trap Disposition Conflicts 169 Results list exporting 63 Results tool bar 162 Retry Count 157 Search DTI Mappings 117 Secure Domain 157 Secure view 31 securing models 31 Seed Routers 44 segment icons 27 send item to back 114 Shape, adding to views 110 SNMP Attributes 147 SNMP GET 159 SNMP GET and GET_NEXT 159 SNMP Ports 45 SNMP SET 159 Stale Interface Age Out (min) 144 Stale Interfaces 144 Enable Stale Interface Alarms 144 Static or One Time IP Addresses Import 45 syslog trap 130 System Object ID 116 S Table Preferences 48 Terms Discovery common terms 38 modeling common terms 68 SPECTRUM common terms 14 text, adding to views 111 Themes, icons 26 Thresholds 148 % CPU Utilization 96 % Memory Utilization 96 Allowed Threshold Violation Duration 95 Device and Interface Threshold Settings 95 Device Thresholds 148 Interface Threshold Settings 98 Interface Thresholds 148 reset level 95 Time Out 147 Tools, Reconfiguration Menu 101 Topologies core defined 17 edit background 112 Global Collections, introduction 21 icon representation 25 TopOrg, introduction 24 Universe, introduction 18 World, introduction 23 topologies 17 TopOrg topology define procedure 92 manual modeling defined 91 Trap Disposition Conflicts 169 Trap Support 164 fault tolerant SpectroSERVER 165 Try Count 147 Type 116 Universe topology manual model 68 Use Loopback 129 V3 Profile 157 Vendor Name 116 VNM Attributes 127 VNM icons 26 T U V 174 Modeling Your IT Infrastructure Administrator Guide

175 Index World topology define procedure 90 manual modeling 89 W Modeling Your IT Infrastructure Administrator Guide 175

176 Index 176 Modeling Your IT Infrastructure Administrator Guide