08-00032-01

Transcript

08-00032-01 StormTracker EMS User Guide Publication Date: October 2001 Document Number: 08-00032-01 Release Number: 2.1 Table of Contents 1 Chapter/Introduction 1-1 Overview Basic StormTracker EMS Functionality StormTracker EMS Installing Oware Solaris Installation Solaris Install Script Backwards Compatibility Installing as Root Installing as Non-Root Reinstalling the Database Solaris Client Installation Using Solaris’ inittab to Maintain Oware Processes Uninstall Solaris Windows 2000 Server Installation Windows 2000 Client Installation Windows 2000 Reinstallation Custom Installation Options Uninstall in Windows 2000 2 Chapter/Launching 2-1 Overview StormTracker EMS Applications Application Server Mediation Agent Agent Mapper Configuring Mediation Agents 2-1 2-1 2-2 2-2 2-4 2-4 3 Chapter/Logon 3-1 Overview Logging On Disabled Accounts Logging Off 3-1 3-1 3-2 3-2 4 Chapter/Launch Console 4-1 Overview Service Menu Assurance Menu Config Menu Device Menu Control Menu 08-000032-01, Rev. 2.1 1-1 1-1 1-1 1-2 1-2 1-2 1-2 1-8 1-12 1-12 1-13 1-14 1-17 1-18 1-19 1-19 1-19 4-1 4-2 4-2 4-3 4-4 4-4 StormTracker EMS User Guide i 5 Chapter/User Management 5-1 Overview User Passwords User Manager Filtering Users User Information Adding a New User Account Editing an Existing User Account Resetting a User’s Password Deleting a User Enabling or Disabling a User’s Account Importing and Exporting User Records User Group Manager Adding a New User Group Editing an Existing User Group Deleting a User Group Importing and Exporting User Groups User Predefined User Groups Permissions New Function Import Functions Export Functions Members Selecting User Group Members 5-1 5-1 5-2 5-3 5-3 5-4 5-4 5-4 5-5 5-5 5-5 5-5 5-6 5-7 5-7 5-7 5-7 5-8 5-9 5-10 5-10 5-10 5-10 6 Chapter/System Settings and Properties 6-1 Overview General User Options MIBs Alarm Severities Topology Adding or Modifying Topology Items General Tab Physical Tab Client Email Settings 7 Chapter/Discovery 7-1 Overview Discovery Wizard The Discovery Process Results Panel Options Discovery Options 08-000032-01, Rev. 2.1 6-1 6-2 6-3 6-4 6-5 6-6 6-7 6-7 6-8 6-9 7-1 7-2 7-3 7-4 7-5 StormTracker EMS User Guide ii The Discovery Scheduler Creating a Discovery Event Executing a Discovery Event Editing the Parameters of a Discovery Event Scheduling a Discovery Event Deleting a Discovery Event 8 Chapter/Managing Objects 7-5 7-6 7-7 7-7 7-8 7-8 8-1 Overview Managed Object Manager Filtering the List of Managed Objects Editing or Creating a Managed Object BitStorm Configure Multicast Configure Priority Queuing Configure VLAN Upgrade Firmware MIU Modem Cards Adding a Top-Level Managed Object Adding a New Component to an Existing Managed Object Moving Managed Objects Deleting a Managed Object Charting Managed Object Performance Copying Managed Objects Mapping Managed Objects Viewing the Data History of Managed Objects 9 Chapter/Network Traffic Management Overview Multicast Priority Queuing VLAN 8-1 8-2 8-3 8-3 8-3 8-4 8-6 8-8 8-9 8-18 8-22 8-33 8-34 8-34 8-34 8-34 8-35 8-35 8-35 9-1 9-1 9-2 9-4 9-6 10 Chapter/Network Security Management 10-1 Overview MAC Address Filtering Configuring MAC Filters 10-1 10-1 10-2 11 Chapter/Device Firmware 11-1 Overview Downloader Select Firmware Files Select Devices to Update 11-1 11-2 11-2 11-3 08-000032-01, Rev. 2.1 StormTracker EMS User Guide iii Download 11-4 12 Chapter/Class Manager 12-1 Overview sysObjectID Operations Adding or Editing a sysObjectID Deleting a sysObjectID Import and Export Operations 12-1 12-2 12-2 12-2 12-2 13 Chapter/Service Management 13-1 Overview Service Management Components Creating Services The Basics Service Manager Service Editor—General Panel Service Editor—SLA Panel Application Manager Creating and Editing Applications Application Editor—General Tab SLA Template Manager Using the SLA Template Manager Order Manager Creating or Editing an Order Group Manager Adding or Editing Groups Subscriber Manager Adding or Editing Subscribers Subscription Editor Contacts Manager Adding and Editing Contacts Deleting a Contact Importing and Exporting Contacts Vendor Manager Filtering Vendors Adding and Editing Vendors Deleting a Vendor Importing and Exporting Vendors 14 Chapter/Managing Locations 14-1 Overview Using the Location Manager Adding a Location Defining or modifying a Parent Location 08-000032-01, Rev. 2.1 13-1 13-1 13-2 13-3 13-3 13-4 13-5 13-6 13-6 13-7 13-7 13-8 13-8 13-8 13-8 13-9 13-9 13-9 13-10 13-10 13-11 13-12 13-12 13-13 13-13 13-14 13-15 13-15 StormTracker EMS User Guide 14-1 14-1 14-3 14-3 iv Editing a Location Location Coordinate Types Deleting a Location Importing and Exporting Locations 14-3 14-5 14-5 14-5 15 Chapter/Link Manager 15-1 Overview Using the Link Manager Importing and Exporting Links 15-1 15-2 15-2 16 Chapter/Data Collection Scheduler Overview Creating a Data Collection Query Adding Managed Objects Removing a Managed Object from a Query Editing the Parameters of a Data Collection Query Scheduling a Data Collection Query Executing a Data Collection Query 16-1 16-1 16-2 16-3 16-4 16-5 16-5 16-5 17 Chapter/Device Synchronization Scheduler 17-1 Overview Creating a Scheduled Device Resynchronization Adding Managed Objects Removing a Managed Object from the Schedule Device Resynchronization Schedule Parameters Scheduling Resynchronization Executing Device Resynchronization 17-1 17-2 17-3 17-4 17-4 17-5 17-5 18 Chapter/SNMP Diagnostic Utilities Overview The SNMP Trap Viewer SNMP Trap Viewer Columns Trap Viewer Controls The MIB Browser Using the MIB Browser 18-1 18-1 18-2 18-3 18-3 18-4 19 Chapter/Cut-thrus 19-1 Overview HTML Cut-thru Loading an HTML Document Telnet Cut-thru Opening a Telnet Session 08-000032-01, Rev. 2.1 18-1 19-1 19-1 19-1 19-2 19-2 StormTracker EMS User Guide v 20 Chapter/Topology 20-1 Overview Geographical Topology Geographic Topology Viewer Options Network Topology Viewers Editing a Managed Object Viewing Object Alarms Logical Topology Adding or Removing Filters Layouts Spring Layout Tree Layout Physical Topology 21 Chapter/Managing Events 20-1 20-1 20-2 20-4 20-4 20-4 20-5 20-6 20-6 20-7 20-9 20-12 21-1 Overview Event Template Organization Editing a Template Information Panel Behavior Panel Advisor Panel Email Panel Icon Panel Adding an Event Template Deleting an Event Template Importing and Exporting Event Templates 21-1 21-2 21-2 21-3 21-4 21-6 21-6 21-8 21-9 21-9 21-9 22 Chapter/Alarms 22-1 Overview Alarm Severities Alarm Window Views Alarm Window Columns Alarm Window Filters Creating or Editing a Filter Dates Event Props Owner Status Selecting a Filter Deleting a Filter Online Alarm Operations Disconnecting and Reconnecting the Alarm Window 08-000032-01, Rev. 2.1 StormTracker EMS User Guide 22-1 22-2 22-3 22-5 22-6 22-7 22-7 22-9 22-10 22-10 22-10 22-10 22-11 22-14 vi 23 Chapter/Alarm Rules 23-1 Overview Rules Manager Creating or Editing a Rule Rule Editor Controls Rule Objects The Begin and End Objects Logical Objects XRL Panel Deleting a Rule Object Connecting Rule Objects Deleting Rule Object Connections Object Properties Panel Object Variables Panel Rendering Your Alarm Rule Registration 23-1 23-1 23-2 23-3 23-3 23-3 23-4 23-5 23-5 23-6 23-6 23-7 23-9 23-10 23-10 24 Chapter/SNMP MIB Event Parser Overview Selecting a MIB File Elastic MIB File 24-1 24-2 24-2 25 Chapter/Performance Monitor Overview Selecting a Managed Object to Monitor Additional Information Performance Monitor Options General Tab SNMP MIB-II Tab Pausing the Performance Monitor Manually Refreshing the Performance Monitor 26 Chapter/StormTracker EMS Reports Overview Designing Reports Logical Operators Report Manager—Events Report Manager—Devices Report Manager—Customers Report Manager—Options Creating a New Report Running a Report Loading or Altering an Existing Report 08-000032-01, Rev. 2.1 24-1 StormTracker EMS User Guide 25-1 25-1 25-2 25-3 25-3 25-3 25-4 25-4 25-5 26-1 26-1 26-2 26-3 26-4 26-5 26-6 26-7 26-7 26-8 26-8 vii Deleting an Existing Report Exporting a Report Changing the Report Display Deleting a Column from a Report Adding a Deleted Column to a Report Moving Columns Resizing Columns Sorting by Column Value Printing Reports Printing a Report Page Setup Print Preview Creating Charts Creating a Pie Chart Creating a Simple Bar Chart Creating a Complex Bar Chart Report Preferences Export Tab Chart Tab Printing Tab 26-8 26-8 26-9 26-9 26-9 26-10 26-10 26-10 26-10 26-10 26-11 26-11 26-12 26-12 26-12 26-13 26-13 26-14 26-14 26-14 27 Chapter/StormTracker EMS Reports 27-1 Overview Preliminary Setup Using RMON The RMON Manager Alarms Events Adding an RMON Alarm Adding an RMON Event RMON Notification Event Templates Displaying Real-Time RMON Data 27-1 27-1 27-3 27-4 27-4 27-4 27-5 27-5 27-5 27-5 28 Chapter/Importing and Exporting 28-1 Overview Importing Files Exporting Files 28-1 28-2 28-3 Glossary 08-000032-01, Rev. 2.1 StormTracker EMS User Guide viii 1 Chapter/Introduction Overview StormTracker EMS provides the technology needed to deliver and manage network services and resources. Each component of the StormTracker EMS provides a specific area of functionality, and the various components can be combined to provide you with exactly the functions you require. Basic StormTracker EMS Functionality All StormTracker EMS components provide a set of common functions, including: • Network device discovery • Device management • Data Collection • Logical and physical topological data views StormTracker EMS StormTracker EMS is a complete, end-to-end solution that lets you quickly and easily manage all facets of a new-world network. Using StormTracker EMS, you can monitor every aspect of your next-generation network and ensure: • Reduction in time to resolve trouble tickets • Detection, monitoring, configuration, and alteration of your network • Rapid problem analysis, regardless of the origin • Reduction in operation costs 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-1 1 Chapter/Introduction Elastic Networks Installing Oware The following sections describe how to install Oware on Solaris and Windows 2000 operating systems. Here are some preliminary items of concern: • • • Installation now inserts the correct file name in the owappserver.properties and owdatabase.properties files. Although, in previous versions, *.properties files contained host name entries that default to localhost, your Oware server should NEVER be named localhost. While Oware can automate preserving your database information, it does NOT preserve *.properties files. Best practice is to back up these files, in addition to your database, before installing Oware. If you have just uninstalled Oware, you must reboot before reinstalling it. Solaris Installation You must install a portion of Oware as super-user (root) because the installation must modify or write files where Solaris requires root permissions. Once this portion is done, you can perform the balance of the installation or removal process as the database admin user. Solaris Install Script Backwards Compatibility The current version of install.sh not compatible with earlier versions. Remove earlier installations using the owclean.sh script before installing the new version. Installing as Root The first time you install Oware, you must install it as root. When you are logged in as root, the installation performs additional checks (for example, verifying the Solaris patch level). It also offers additional installation options, for example installing a server startup script. 1-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Oware requires installation as root only the first time you install the software or when you move the database components to a new location. Although you can install as root on other occasions, you must make the initial installation as root. The installation script tells you the action to be taken and lets you accept or bypass the change. If you accept the change, the installation saves a backup copy of the file and announces the saving location. If you bypass the change, you must change it manually before you can run the second phase of the install process—see Installing as Non-Root. NOTE: Before running the installer, establish the database admin user and group accounts if they do not already exist. You can use any valid user (other than root) and group names. Root installation may modify the following system files: /etc/system- Checks and upgrades key values, if needed. /etc/services- Adds the database daemon entry. /etc/inetd.conf- Adds the database daemon entry. /etc/.oscnnnnnn- Writers the database environment information to this file. /etc/rc2.d/S76oware- Installed. To run the root install: 1. Insert the CD into the computer. (Solaris typically mounts the CD as /cdrom/cdrom0.) 2. Type: cd/cdrom/cdrom0/solaris (The Solaris subdirectory on the CD). 3. Type ./install.sh [installation root directory]. If you do not specify one, the installation selects /opt/dorado. The installation root directory is the only command line option for install.sh. The installation obtains all other required information interactively. Usage: install.sh [installation root directory] Where: [installation root directory] is the starting point for this installation. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-3 4. Follow the instructions displayed by the install.sh. 5. If /etc/system is modified, the script asks you if you want to reboot after installation. If the installation modifies /etc/intetd.conf or /etc/services, the scripts asks you if you want to restart the inet daemon at the end of the root installation. Warning: To properly install Oware you must have administrator right to your database as well as being at root. The following is a transcript of a Solaris root installation: This part of the installer script (install.sh) performs the pre-installation functions requiring root user privileges install.sh will explain what changes will be made and give you a chance to bypass the changes before any modifications are made. If you allow the changes, your original files will be backed up first and the name of the backup file is displayed. A detailed history of actions is recorded in the install log The file name for the install log is announced when it is created... Begin recording system information End recording system information Checking patches for SunOS, release 5.7 Looking for required patch 106980, rev 05 Found installed patch 106980, rev 03 WARNING: Patch 106980 is installed but rev level 03 is not adequate Found installed patch 106980, rev 05 Found installed patch 106980, rev 05 Looking for required patch 107078, rev 18 Found installed patch 107078, rev 18 Looking for required patch 107607, rev 01 Found installed patch 107607, rev 01 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-4 Looking for required patch 107636, rev 03 Found installed patch 107636, rev 03 WARNING: One or more patch(es) must be installed or upgraded to ensure correct operation of oware Do not continue the installation without fixing the patch problems. Continue installation? y - yes n - no q - quit install.sh Selection?[n]: y Note that the following is a typical warning message if your patch level is inadequate. The Oware installation erroneously warns of patches later than the required patch level. You can ignore these messages in that case. WARNING: Oware may not work correctly due to patches discrepancies End patch check Install application server startup script /etc/rc2.d/ S76oware? y - yes n - no q - quit install.sh Selection?[y]: y Install mediation agent startup script /etc/rc2.d/ S77oware? y - yes n - no q - quit install.sh Selection?[y]: y 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-5 Will the db server be on this system? y - yes n - no q - quit install.sh Selection?[y]: y Pinging db host 'shadow' -- please wait shadow is responding Enter user name to be used Selection?[NotSpecified]: oware oware OK Backing up /dorado/.env as /dorado/backup/ .env.20000908131742 Enter group name to be used Selection?[NotSpecified]: oware oware OK Backing up /dorado/.env as /dorado/backup/ .env.20000908131742 No changes needed to /etc/system Modify /etc/services? y - yes n - no q - quit install.sh Selection?[y]: y Backing up /etc/services as /dorado/backup/ services.20000908131742 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-6 Modify /etc/inetd.conf? y - yes n - no q - quit install.sh Selection?[y]: y Backing up /etc/inetd.conf as /dorado/backup/ inetd.conf.20000908131742 Added oscssd entry to /etc/inetd.conf entry = 'oscssd stream tcp nowait root /dorado/oware3rd/ versant/5.2.2/sun4/bin/ss.d in.oscssd' Checking database properties file '/etc/.osc050202' /etc/.osc050202 not found Install /etc/.osc050202? y - yes n - no q - quit install.sh Selection?[y]: y /etc/.osc050202 installed OK Backing up /dorado/.env as /dorado/backup/ .env.20000908131742 Backing up /dorado/.env as /dorado/backup/ .env.20000908131742 Enable bootp? y - yes n - no q - quit install.sh Selection?[n]: y 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-7 Backing up /dorado/.env as /dorado/backup/ .env.20000908131742 The following line reminds you that you must reinstall as non root user (Oware) To finish the system installation, log in as oware and run install.sh again WARNING: inet daemon restart (kill -1) is needed for new /etc/inetd.conf values to take effect Restart now? y - yes n - no q - quit install.sh Selection?[y]: y Installing as Non-Root This phase installs program files, does setup functions and loads or upgrades the database load, as appropriate. To run this installation: 1. Log in as the database admin user (defined in the Installing as Root section). 2. Insert the CD and locate the following directory: cd/cdrom/cdrom0/ solaris. 3. Type: ./install.sh Following instructions displayed. The following a transcript of the installation as the (example) user Oware. :oware$ pwd /cdrom/oware/solaris :oware$ cd .. :oware$ ls 2000 solaris. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-8 4. Run the install.sh script. NOTE: This script installs all Solaris programs you select. For a typical client installation, you do not select the server applications. :oware$ install.sh == Welcome to oware installer for release XXX, build YYY Copyright (c) 2001 by Elastic Networks, Inc. Environment found The installation root directory appears to be /hd2/ti Use this directory? y - yes n - no q - quit install.sh Selection?[y]: n Enter installation root directory or 'q' to quit Selection?[q]: /elastic This part of the installer script (install.sh) performs all installation following the root setup functions install.sh - created installation log file /elastic/logs/ install_log.20000908084302 install.sh will explain what changes will be made and give you a chance to bypass the changes before any modifications are made. A detailed history of actions will be recorded in the install log The file name for the install log is /dorado/logs/ install_log.20000908084302 Select function 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-9 i - Install software r - Remove software or database Selection?[i]: i Install install support software? y - yes n - no q - quit install.sh Selection?[y]: y Unpacking files from /cdrom/oware/solaris/oware3rd.tar into /elastic This will take a while... ... files successfully unpacked Install application server and mediation agent? y - yes n - no q - quit install.sh Selection?[y]: y Unpacking files from /cdrom/oware/solaris/oware.tar into /elastic This will take a while... ... files successfully unpacked Backing up /elastic/oware/lib/owappserver.properties as / elastic/backup/owappserver.properties.20000908084302 Install database server program files? y - yes n - no q - quit install.sh Selection?[y]: y Unpacking files from /cdrom/oware/solaris/db.tar into / 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-10 dorado/oware3rd This will take a while... ... files successfully unpacked Backing up /dorado/oware/lib/owdatabase.properties as / dorado/backup/owdatabase.properties.20000908084302 Loading oware environment Running loaddb Please wait. This will take a few minutes Installation progress can be monitored by the following command: tail -f /dorado/logs/install_log.20000908084302 This is a fresh installation Creating databases Checking owenv ... No unresolved entries found while checking owenv Checking owenv ... done install complete Start the application? y - yes n - no q - quit install.sh Selection?[y]: y Starting application server Starting agent mapper When you are finished with the agent mapper, close it. Type 'y' to continue with startup Continue? y - yes n - no q - quit install.sh Selection?[y]: y 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-11 NOTE: The Mediation Agent, Management Center and Creation Center automatically start as part of the installation. Starting mediation agent Starting Management Center Starting Creation Center Check /dorado/logs for startup results Reinstalling the Database To reinstall the database without doing a full system installation, run install.sh and choose the option to remove software. Answer y when asked whether you want to remove the database. Answer n to all other questions about removing program files. You may then invoke install.sh again and answer n to all questions about installing files. The script will then begin to reinstall the database. Solaris Client Installation To perform a client-only installation on Solaris, following these steps: 1. Perform a normal installation on the client system. When the installer asks about start the application, answer ‘n’ to terminate the installer. NOTE: The user name you provide during installation on client machines should be a valid user login on the server too. The client account need not have a password on the server. 2. Edit the oware/lib/owappserver.properties and oware/lib/owdatabase.properties files on the client. 3. If the client user account is not the same name as the database administrator on the server, run ownewclientuser on the server to add the client username to the list of authorized database users. 4. Run ow start ems on the client machine. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-12 Using Solaris’ inittab to Maintain Oware Processes The UNIX process control initialization routine init spawns processes. Its primary role is to create processes from information stored in the / etc/inittab file. You can add an entry to /etc/inittab to start the Application Server or Mediation Agent at startup and restart it every time it terminates or is killed by a user. Caution Adding the Application Server and/or Mediation Agent to inittab prevents you from ever completely shutting down the processes, since they will always attempt to re-spawn. The /etc/inittab file consists of entries that are position-dependent and have the following format: id:rstate:action:process id: A one or two-character identifier. We suggest using ma for Mediation Agent, and as for Application Server. rstate: Represents the different init levels that this process should run (2 through 4 are suggested values). action: Should be respawn so init restarts the process when it terminates. process: The programs and the arguments it runs. The init process is a sysadmin process, therefore, you must log in as root to interact with it. To use init, add the following lines to the /etc/inittab file: ma:234:respawn:/dorado/oware/bin/startAppServer ma:234:respawn:/dorado/oware/bin/startMedAgent These examples assume that the startAppServer and startMedAgent scripts are installed in the /dorado/oware/bin directory. Replace this 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-13 with the correct path, if necessary, and replace hostname with the name of the Application Server host. Reread the inittab file by typing the following command: init Q Change init levels from 3 to 2 and back again (this makes it process the line in the new file): init2 init3 For more information about inittab, execute the following command from the terminal window: man inittab Uninstall Solaris You can install and remove Oware with install.sh. The uninstall procedure is the reverse of the installation. Remove the files (database, program files and data) as the database admin user with install.sh. If you are removing Oware to get a clean installation, you do not need to run the root user portion of the script unless you plan to install the software into a different set of directories than the initial installation. You must run install.sh as root to completely remove the installation in system files. The following is an edited transcript of an uninstallation in a Solaris Korn shell. You will start install.sh, but select the uninstall path. NOTE: When you uninstall as root, you also uninstall the Oware environment. = = = Welcome to oware installer = = = Environment found The installation root directory appears to be /hd2/ti Use this directory? 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-14 y - yes n- no q - quit install.sh Selection? [y]: n Enter the installation root directory or ‘q’ to quit Selection? [q]: /dorado This part of the installer script (install.sh) performs all installation following the root setup functions install.sh - created installation log file /dorado/logs/ install_log.20000908082325 install.sh will explain what changes will be made and give you a chance to bypass the changes before any modifications are made. A detailed history of action will be recorded in the install log The file name for the install log is /dorado/logs/ install_log.20000908082325 Select function i - install software r - remove software or database Selection?: [i]: r Remove the database files? y - yes n - no q - quit install.sh Selection? [n]: y 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-15 Removing classes db Removing metadata db Removing busdb db Removing lrep db Removing cntl db Removing db data files Removing dbid Removing dba user info Remove database server program files? y - yes n - no q - quit install.sh Selection? [n]: y Removing database server program files Run install.sh again when you are logged in as root if you wish to completely remove the databse installation Remove application server and mediation agent files/ y - yes n - no q - quit install.sh Selection?[n]: y Removing application server Application server and mediation agent successfully removed Remove support software? y - yes n - no 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-16 q - quit install.sh Selection? [n]: y Run install.sh again when logged in as root if you wish to completely remove the installation (When you run install as root, you also remove the environment) Windows 2000 Server Installation The following steps outline a server installation of Oware on Windows 2000: 1. Log in as an administrator, and insert the Oware installation CD (you must be an administrator to install Oware). 2. Click Start > Run, then type [X:]\nt\Setup.exe, where [X:] is your CD drive letter. The following screen appears: 3. Click Next to see the license acceptance screen. 4. Click Yes to accept the user license. 5. Choose the installation destination. The default is C:\Dorado. Click Next. 6. Choose the type of installation you want. In this case, we choose Server. 7. Click Next after confirming your selection. This screen informs you of changes, and warn you if you are going to overwrite data. 8. The illustrated status bar goes to 100% when the installation is done copying files. 9. You must reboot if you are prompted. You are prompted to reboot only for the initial database installation, or if you uninstalled and are re-installing Oware. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-17 10. Build the Oware databases. Click Next. 11. When the database seeding completes, you can click Finish. 12. To confirm the completion of your installation, and to start Oware, click Start. You can start Oware components from the menu items under this icon. Windows 2000 Client Installation The following section describes how to install Oware on Windows 2000 clients. Your installation may vary slightly, depending on whether you have previously installed Oware on the computer, either as a client or server. 1. Log in as an administrator, and insert the installation CD. Click Start > Run, then type [X:] \nt\Setup.exe, where [X:] is the CD drive letter. The following screen appears: 2. Click Yes to accept the user license. 3. Choose the installation destination. The default is C:\Dorado. Click Next. 4. Choose the type of installation you want. In this case, choose Client. 5. Enter a TCP/IP host name for the Appserver and for the DBServer. 6. Confirm the selection, and wait for the progress bar to reach 100%. 7. Click Finish. You have successfully installed Oware. Click Start to access the applications. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-18 Windows 2000 Reinstallation If you are re-installing or installing on the same machine as the server (Oware client is already installed), choose Modify or Repair (this reinstalls required components). NOTE: This screen also lets you remove installed components. The Custom Installation screen follows the Modify screen. Warning Selecting Modify allows you to delete the database. Select the application (Client), and deselect Application Server and Database Server. These last two components are part of the server installation. Custom Installation Options You can install portions of Oware to separate hosts by selecting desired options from the installation program dialog. The following are elements typically installed by themselves, using the Custom Installation option: • • • Application Server Database Server Client NOTE: To install the Mediation Agent, simply install the Client. Uninstall in Windows 2000 Use the Windows Add/Remove Programs dialog in Control Panel to uninstall Oware, then follow these steps: 1. Reboot the computer to remove locked files (the uninstall program prompts this). 2. Delete the Oware directory. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 1-19 2 Chapter/Launching Overview StormTracker EMS is an inherently distributed n-tier application; the primary user interface runs on the client side. After a normal installation, the server side processes must be manually started. The client processes can be started and stopped on demand. Server processes must be manually started if they are stopped or if the computer hosting them is restarted. StormTracker EMS Applications The following associated applications are required for full StormTracker EMS functionality, and are typically launched before StormTracker EMS. Application Server - The application server runs continuously in the background, and provides connectivity between all components. Mediation Agent - This application runs continuously. It handles all communications between StormTracker EMS and managed objects, receives and translates SNMP traps, and converts traps into events. Agent Mapper - This application is run whenever a Mediation 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 2-1 2 Chapter/Launching Elastic Networks Agent must be configured. It provides the Mediation Agent with location information for an agent, as well as the kinds of messages that the agent will be mediating. Application Server The StormTracker EMS Application Server runs in the background and enables the system to process incoming events and communicate with managed objects and network devices. Launch the Application Server by selecting the shortcut from the Oware Management Center launch bar. If you try to run StormTracker EMS without first starting the Application Server, a warning will appear and StormTracker EMS will not launch. Figure 2-1. Unable to Connect to Application Server NOTE: Note: If the server has been restarted, StormTracker EMS must be manually reconnected to the application server. Select Connect to Application Server from the Control menu. Mediation Agent The Mediation Agent is a translation service that provides an interface to external systems and devices. Default external protocols supported include: • General ASCII • TL1 • SNMP • CORBA • ICMP 2-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 2 Chapter/Launching The Mediation Agent contains Managed Beans (MBeans) that perform the physical connections to a mediation target system or device. Examples include communicating with a serial port device, a telnet session, a TCP socket, and external databases. The Agent executes dialogs with the mediation target (at the instruction of the client application) to retrieve and/or send data with the connection. Mediation can be accessed through a rule or from client code. The Mediation Agent is essential for normal use; if one is not running, administrative changes can still be made to the system, but no traps or other communication will be processed by StormTracker EMS. Launch the Mediation Agent from the Oware Management Center launch console. This must be executed on the host that was specified in the Agent Mapper application. If multiple Agents are specified, each agent must be started from its own workstation. Mediation Agents will automatically find the Application Server and can be started before or after the Application Server has been started. Figure 2-2. Mediation Agent Console The Mediation Agent only displays operational messages in the Mediation Agent console of Windows 2000 (this dialog box does not appear in Solaris). During normal operation, there is no need to view this output, as the Agent is intended to run in the background. The following figure illustrates an example of a Mediation Agent console. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 2-3 Agent Mapper The Agent Mapper enables the Mediation Agent to handle SNMP requests, SNMP traps, and ASCII grammars. When first installed, the Agent Mapper must be configured with each location of a Mediation Agent. It can be accessed any time a new Mediation Agent is required on a new computer, or the configuration of an existing agent is changed. The Agent Mapper must be run after installation to set up one Mediation Agent, as at least one Agent is required for StormTracker EMS to communicate with a network element. Figure 2-3. Agent Mapper Configuring Mediation Agents From the initial Agent Mapper screen, select Add Agent Mapping Object to display the Add Agent dialog box. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 2-4 Figure 2-4. Add Agent Dialog Make the requisite entries in this dialog and click OK to add the agent or Cancel to cancel the operation. The fields in the Add Agent dialog are as follows: Domain—This read-only field reflects Oware’s distributed domain. Remote Host—Type the hostname or IP address of the Server on which the Mediation Agent will run. Localhost is not a valid value. Launching StormTracker EMS. Subnet Mask—Type the appropriate Subnet Mask. Order—Type a number to specify the sequence of Mediation Agents. If there will only be one, this number should be 1. If there are to be multiple Agents that communicate with the same subnet, then this number will determine which is the primary and which are the backups. Select the check boxes corresponding to the kinds of communications you wish to process. The choices are: • ASCII Terminal Server • SNMP • SNMP Trap Listener • Custom Mediation MBean If StormTracker EMS will only be managing SNMP devices, then only the SNMP and SNMP Trap Listener options should be selected. Select OK to implement the agent and close the dialog box. If there is only one Mediation Agent required, then exit the application. Otherwise, perform the same steps for each Agent. Only one Agent is allowed on each host. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 2-5 3 Chapter/Logon Overview StormTracker EMS’s logon facility enforces security at the client level. You must have a valid user and password to log on to StormTracker EMS and make use of its features. Logging On To log on to StormTracker EMS, type a valid user name and password at the logon prompt. When StormTracker EMS is installed, there is a default user name/password of admin/stormtrackerems. This should be changed the first time StormTracker EMS is started. Figure 3-1. StormTracker EMS Logon Prompt 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 3-1 3 Chapter/Logon Elastic Networks Disabled Accounts If an incorrect password has been entered, the user will be prompted three times before the system disables the account, displays a warning dialog, and shuts down. The system will not allow a user with a disabled account to log on; a system administrator must re-enable the account before the user is allowed to re-access StormTracker EMS. Enabling user accounts is detailed in User Management. Figure 3-2. Login Access Denied Alert Logging Off Occasionally, it is necessary for a user to log off without closing the application. By doing so, the current user can log off and another user can log on using a separate account. To log off, select Log Off from the Control menu. This option displays the Logon dialog. To log off and exit the application, select Log Off and Exit from the Control menu. 3-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 08-00032-01, Rev. 2.1 3 Chapter/Logon StormTracker EMS User Guide 3-3 4 Chapter/Launch Console Overview StormTracker EMS functions are divided into logical groupings, represented by the various icons on the Launch Console. Those functions are mentioned briefly in this section and covered in detail later in this publication. All Launch Console menus are accessed by clicking on the appropriate icon or by entering the indicated command mnemonic— Alt-S for the Service menu, for example. Figure 4-1. StormTracker EMS Launch Console. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 4-1 4 Chapter/Launch Console Elastic Networks Service Menu The Service menu lets you create and manage services, orders, applications, service level templates, and contact information for individuals, groups, and subscribers. Assurance Menu The Assurance menu contains functions that monitor and report on network events, perform remote monitoring, manage alarms, monitor performance, and generate reports. 4-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 4 Chapter/Launch Console Config Menu The Config (Configuration) menu functions launch the various configuration managers, including the Managed Object Manager (MOM), Topology Viewer, Data Collection scheduler, Discovery Scheduler, Location Manager, Vendor Manager, and Multicast, VLAN, Priority Queue, and MAC Filter settings. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 4-3 Device Menu The Device menu lets you interact directly with system devices— either by HTTP or Telnet cut-thru to a device, by loading or browsing MIBs, or by viewing incoming traps. In addition, you may download the latest firmware available for system hardware. Control Menu The Control menu contains functions that let you change passwords, log off the system, manage Users and User Groups, modify system set- 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 4-4 tings, and connect to the Application Server. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 4-5 5 Chapter/User Management Overview StormTracker EMS users are organized into User Groups; each group is assigned a certain permission level. Every function within StormTracker EMS has a corresponding Permission. To access a function, a user must belong to a Group that has permission rights for that function. This lets the StormTracker EMS Administrator organize users on the basis of their access requirements, and to enforce security accordingly. If a user does not have permission to access an area, the section will not appear in the menu at all. User Passwords Users can change their passwords through the Change Password dialog. In addition, administrators may reset passwords. Passwords must not be “empty” (have no value) and cannot contain a portion of the user’s login name. For example, the user “afly” may not specify a password with that string embedded in it (19tenafly70, for example). To access the Change Password function, select Change Password from the Control menu. The Change Password dialog, shown below, appears. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 5-1 5 Chapter/User Management Elastic Networks Figure 5-1. Change Password dialog The user must type their original password, then the new password. User Manager Administrators can create, edit, and delete user accounts through the User Manager. To access the User Manager, select Manage Users from the Control menu. When activated, all users within the system are displayed. Once a user has been created, the User Group can be set and detailed information can be entered, including phone numbers and email addresses. In addition, user passwords may be reset, if necessary. Figure 5-2. User Manager 5-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 5 Chapter/User Management Filtering Users The User Manager dialog initially displays all defined users. You can filter the display by selecting one of the predefined filters from the drop-down menu at the top of the dialog, or you can search for a user by typing text directly into the filter field. Searches are performed on the User Name and Description, and are case-sensitive. If “Admin” is entered into the filter field, for example, the user “admin” will not be returned. User Information The User Manager contains the following fields: Login Name—Name used to log in to the system. Description—Short description of user. User Enabled—Check box; must be selected in order for user to access system. Automatically deselected if the user logs in incorrectly three times. First Name—First name of user. Last Name—Last name of user. Address—Three-line address. Phone Number—Can contain up to three phone numbers: Work, Home, Other. Pager Number—Can contain up to three pager numbers: Work, Home, Other. Mobile Number—Can contain up to three mobile phone numbers: Work, Home, Other. Fax Number—Can contain up to three fax numbers: Work, Home, Other. Email—Can contain up to four e-mail addresses: Work, Home, Pager, Other. Group—User group to which the user belongs; displayed as a dropdown box. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 5-3 Adding a New User Account To add a new user, select New or press Alt-N to open the Add New User dialog. Type the user’s login name and password, retype the password, and select a Group for the user. User names must be unique. Figure 5-3. Add New User dialog box Editing an Existing User Account To modify a current user’s data, highlight the user’s name and click Edit or press Alt-E. All information for a user can be altered, and additional detailed information—including name, address, e-mail, and phone numbers—can be added by editing a user. In addition, the user account can be activated or deactivated by checking the User Enabled box. Resetting a User’s Password To reset a user’s password, select the user in question and click on Reset Password or press Alt-R to display the Enter Password dialog box. Type the new password, re-type it to confirm, and click OK. Figure 5-4. Enter Password dialog 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 5-4 Deleting a User To remove a user record, highlight the user’s name, and click Delete or press Alt-D. This will remove the record of a user from the system; StormTracker EMS will prompt before deleting. Note that it is possible to deactivate a user instead of deleting the record. Enabling or Disabling a User’s Account To enable or disable a user’s account, double-click the user’s account, or highlight the account and select Edit or press Alt-E, then select or deselect the User Enabled check box. Once an account has been disabled, an administrator must enable the account again before the user can logon again. Normally, StormTracker EMS disables accounts automatically if the user logs in incorrectly three times; however, accounts may be disabled manually by an administrator. Importing and Exporting User Records User Records can be imported and exported through StormTracker EMS’s Import and Export utilities. Exported files can serve as backups, as seed files, and can be imported by clients running on other servers. For more information, please see Importing and Exporting. User Group Manager The User Group Manager provides the system administrator with the means for creating, deleting, modifying, and managing user groups. Run the User Group Manager by selecting Manage User Groups from the Control menu. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 5-5 Figure 5-5. User Group Manager Adding a New User Group Whenever you need to add a user group on the network, select New or press Alt-N to display the Add New Group dialog. Type the group name and description. Note that group names must be unique. Additional user group information—such as group members and permission levels—may be added later, by editing the existing group. Figure 5-6. Add New Group Dialog 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 5-6 Editing an Existing User Group All information for the specified group can be altered, and additional information—such as group members and permission levels—can be added by editing a user group. Double-click on the user group to be edited, or highlight the group and click Edit or press Alt-E. For more information on editing permission levels and memberships, see Permissions and Members. Deleting a User Group This function is used to remove a group from the system; StormTracker EMS will prompt before final deletion. Highlight the User Group to be deleted and click Delete or press Alt-D. Importing and Exporting User Groups User Groups can be imported and exported using the StormTracker EMS Import and Export utilities. Exported files can serve as backups, as seed files for downstream deployment, or as source files for clients running on other servers. The procedure for importing and exporting files is outlined in Importing and Exporting. Predefined User Groups StormTracker EMS provides the following default User Groups and preset permissions: Administrators—All functions of the system are available. Data Entry Clerks—Access is restricted to functions relating to customers and services. Operators—Access is restricted to Alarm management and report functions. Trainees—Allows Alarm Window viewing access only. Group Information 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 5-7 The Group Information tab of the User Group Manager provides a basic description of each group and associates a default filter, if desired, with each group. Figure 5-7. User Group Manager: Group Information tab The settings in the Group Information tab are as follows: Group Name—The name of the user group; note that group names must be unique. Description—Description of the group. Default Filter—The default filter used within the StormTracker EMS Alarm Window; displayed as a drop-down box. For more information on Filters, refer to Customizing the Alarm Window: Filters. Permissions The Permission Tab gives the administrator the ability to define and modify the permission levels for each group. In StormTracker EMS, a Permission is a function that has been enabled for a particular group or member. Each available function is listed, along with an Enabled box. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 5-8 Functions that are enabled are indicated by a check mark within the Enabled box. To enable or disable a specific function, click on the Edit button at the bottom of the User Group Manager dialog, and doubleclick the associated Enabled box. Click Save to accept the changes. Figure 5-8. User Group Manager: Permissions tab New Function An administrator (or any one with Add New Function permission) can add a new function to the system. Select New Function or press Alt-W to display the Add New Function dialog. Type the name of the new function and click OK to save it. Figure 5-9. Add New Function dialog 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 5-9 Import Functions This function lets you import multiple Functions from a preexisting text file. Click Import Functions, browse to the location of the file, select it, and click Import. Export Functions This function is used to export all existing StormTracker EMS Functions to a text file. Click Export Functions, browse to select the required file location, type the filename, and click Open. Members The Members tab lets you define the members of each User Group. Figure 5-10. User Group Manager: Members tab Selecting User Group Members This function is used to define and alter members of the group. To access, select the required members of the group from the provided list of defined users and add them to the specified group. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 5-10 6 Chapter/System Settings and Properties Overview The System Settings dialog lets you modify certain global settings for StormTracker EMS. This dialog is available from the System Settings option in the Control menu. System Settings includes log file options, user login options, alarm severity colors and associated sounds, and topology options. The System Settings dialog is divided into the following tabs: General, User Options, MIBs, Alarm Severities, Topology, and Client Email Settings. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-1 6 Chapter/System Settings and Properties Elastic Networks General The General tab, shown below, specifies settings for the log file, alarms, and system sounds. Figure 6-1. System Settings: General The settings in the General tab are as follows: Log Output Path:—This entry specifies the full path to the log file. New log file per day?—This option specifies that a new log file be generated every day. The date of generation is embedded within the filename. The default is for StormTracker EMS to maintain the same log file. Separate log file per device?—This option creates a separate log file for each device. The name of the device is embedded within the file name. Field Delimiter:—The entry in this field is used to specify the character that is used to separate fields in the log file. The available delimiters are displayed in a drop-down menu. String Delimiter:—The entry in this field is used to specify the character that is used to separate strings in the log file. The available delimiters are displayed in a drop-down menu. 6-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 6 Chapter/System Settings and Properties Restrict viewed alarms?—When this option is selected, the number of alarms that can be displayed is limited to the number specified in Maximum Viewed Alarms. Maximum Viewed Alarms—This field specifies the maximum number of viewed alarms that can be displayed when the Restrict viewed alarms? option is selected. Enable system sounds?—Select this option to enable the sounds associated with each alarm. If this option is not selected, sounds are not played when an alarm goes off. User Options The User Options tab allows you to configure password settings. The settings in this tab are detailed following the illustration. Figure 6-2. System Settings: User Options Minimum Password Length—Specifies the fewest number of characters allowed for a password. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-3 Require a Special Character in Password?—Check box; when selected, specifies that a password must contain a special character, as defined by the next entry. Special Characters—Specifies the characters that can be used when the “Require a Special Character in Password” option has been set. Expire Inactive Accounts—Specifies, when selected, that accounts that have been active for the period of time specified by “Maximum Inactive Days” are to be expired. Maximum Inactive Days—Specifies the maximum number of days an account may remain inactive before becoming eligible for expiration. Allow Login Name in Password?—Enable or disable user’s access to use all or part of login name in password. MIBs The MIBs tab lets you specify which MIBs—if any—are preloaded when StormTracker EMS is launched, and it provides other related options. Figure 6-3. System Settings: MIBs 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-4 Add—Click on this button (or press Alt-A) to display the Add MIB dialog box, shown below. Type the new MIB name and click on OK to add it to the list of MIBs to be preloaded. Remove—Click on this button (or press Alt-R) to remove the selected MIB from the list. Edit—Click on this button to edit the name of the selected MIB. Copy—Click on this button to copy the selected MIB filename; you will be prompted for a new name. Move Up—Click on this button to move the selected MIB up one position in the list. Move Down—Click on this button to move the selected MIB one position down in the list. Load MIB—Click on this button to load the selected MIB. Load All MIBs—Click on this button to load all the MIBs in the list. Default Discovery sysObjectID—The sysObjectID entered in this field, if any, becomes the default for Device Discovery. Alarm Severities The Alarm Severities customizes the alarm colors and associates a sound file (.wav or .au format) with a specific alarm severity level. Figure 6-4. System Settings: Alarm Severities 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-5 The available severity levels are displayed in tabs on the left side of the dialog. The display name associated with a severity level is shown in the Displayed Name field at the bottom of the dialog. Change this value as appropriate for your installation.Selecting a tab also highlights the associated sound, if any, and displays the associated color. Select a severity level by clicking on the associated tab, and then associate it with a sound (audible alarm) and a color by clicking on each in turn. Topology The Topology tab in System Settings allows you to add, remove, and edit object names, or copy a graphic image associated with the selected type of topology object. The objects and images are used in the Geographic Topology Viewer to provide the StormTracker EMS user with a GUI environment for managing network devices. For more details about topology settings and use refer to Chapter 17, Topology. The Add, Remove, Edit, and Copy buttons are documented in Adding or Modifying Topology Items. Figure 6-5. System Settings: Topology Panel 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-6 Top Level Background Map:—The entry in this field specifies a graphic to be used as a background map for the top level topology view. Adding or Modifying Topology Items The buttons to the right of the Topology tab let you add, edit, or remove topology items. Edit an existing item by selecting it and clicking the Edit button. Remove an existing item by selecting it and clicking on the Remove button. Copy an existing item (enabling you to save it under a different name) by selecting it and clicking on the Copy button. Add a new item by clicking on the Add button. The resulting dialog, shown below, is the same as the Edit Topology Item dialog, but all the fields are blank. The New Topology Item and Edit Topology Item dialogs are divided into the General Tab and the Physical Tab. The options on those tabs are as follows: General Tab The General Tab lets you specify a class and associate an image with a Topology item. Class Name:—Select from the available classes by picking one from the drop-down menu. Graphic File:—Specify a graphic file, including the full path, to be associated with this item if a graphic is needed. (The graphic forms the frame for the icon, and allows certain state information to be presented.) Icon File:—The name, including the full path, of the StormTracker EMS icon graphic. Icon Attribute:—Specifies the attribute to be used to obtain the graphic name from the appropriate class. Icon X Coordinate:—Specifies the horizontal location of the icon, in pixels, with respect to the left side of the graphic. Icon Y Coordinate:—Specifies the vertical location of the icon, in pixels, with respect to the top of the graphic. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-7 Physical Tab The Physical tab lets you specify a background for the image, an Image Graphic, and lets you define subcomponents (slots, ports) of the device. The entries in the Physical tab are as follows: Image Background—Specifies the image, if any, to be used as a background for the image representing this entity. Image Graphic—Drop-down list containing the names of the available graphics. The large text panel in this dialog contains “registry entries,” entries that identify subcomponents of this entity by name and by location. Click on the Add button to display this dialog, and type the appropriate information. The fields in this dialog are as follows: Location Name—An attribute of the class RedCell.Config. PhysicalLocation that identifies this subcomponent. Icon X Coordinate—Specifies the horizontal location of the icon, in pixels, with respect to the left side of the parent graphic. Icon Y Coordinate:—Specifies the vertical location of the icon, in pixels, with respect to the top of the parent graphic. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-8 Client Email Settings The Client Email Settings tab lets you specify a SMTP host to which email is sent, as well as a return address for outgoing mail. Figure 6-6. System Settings: Client Email Settings The fields in this tab are as follows: SMTP Host:—Specifies the SMTP host to use when StormTracker EMS sends e-mail. Return Address:—Specifies an e-mail return address for alarms emailed from the Alarm window. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-9 Sound:—The Sound panel lists the sound files that can be associated with a severity level. Select a sound file from this list by clicking on it, or click on (none) to associate no sound with the selected severity level. Color:—The Color panel lets you select the color to associate with a severity level. The colors can be viewed as swatches, or can be specified through a Hue, Saturation, and Brightness (HSB) model or a Red, Green Blue (RGB) model. Swatches—This color model presents the available colors as a grid of 310 boxes. Click on any box to select that color. The Recent portion of this panel displays the 35 most recently selected swatch colors; you can select any of these colors by clicking on the appropriate box. HSB—This color model lets you specify a color by its Hue, Saturation, and Brightness values. One component (H, S, or B) is selected and adjusted at a time. The large square in this panel displays a range for the selected component with respect to the other two components. For example, if a Hue value of 200 is selected, the square displays that hue with the saturation ranging from 100 (right) to 0 (left), and the brightness ranging from 0(bottom) to 100 (top). The slider in the middle displays the range of values for the selected component. The H, S, and B radio buttons to the right of the panel let you select the color component to adjust, and let you directly specify the value for each component. Acceptable values are as follows: H—Hue is measured on a color wheel, and is specified in degrees. Acceptable values range from 0 to 360. S—Saturation (the amount of the specified hue present) is specified as a percentage. Acceptable values range from 0 to100. B—Brightness is specified as a percentage. Acceptable values range from 0 to 100. The R, G, and B values on the lower right side of this panel indicate the equivalent Red, Green, and Blue values for the selected color. RGB—This color model lets you specify a color by its Red, Green, and Blue components. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-10 Each color component (Red, Green, and Blue) has an associated slider. Move the slider to the right or left to change the value, or type a component value ranging from 0 to 255 in the text box to the right of the appropriate slider. For all three color models, the Preview portion of this dialog shows you what your current color looks like as the text color against a grey background, as the background for white text, and as the text color against a white background. When you are satisfied with the color, click OK to implement it. Click Cancel to cancel the operation. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 6-11 7 Chapter/Discovery Overview Discovery is the process by which StormTracker EMS identifies network elements. Once a network element has been identified, a Managed Object can be created, enabling StormTracker EMS to communicate with the element. Discovery can be performed interactively, through the Discovery Wizard, or can be set up in advance and scheduled for automatic execution, through the Discovery Scheduler. Both methods are detailed in this section. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 7-1 7 Chapter/Discovery Elastic Networks Discovery Wizard The Discovery Wizard simplifies the process of network element discovery by providing a high degree of interactivity. When the Discovery Wizard is initially launched, the Discovery Options panel appears. Figure 7-1. StormTracker EMS Network Discovery Wizard Options Panel The Options panel lets you specify IP address ranges to include or exclude. Fill out the fields in this panel as follows: 1. Specify a starting and ending IP address to establish a range. Each address in this range is sent an ICMP Echo command. If a response is received, the address is listed as valid. 2. Specify an SNMP Read Community (Public or Private) to enable SNMP checking. When SNMP checking is enabled, any address that responds to an ICMP Echo is sent an SNMP get command. Discovery does not process the next address until either a valid SNMP response or an SNMP time-out is returned. Because the wait for a time-out adds considerably to the processing time, this option 7-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 7 Chapter/Discovery should be restricted to ranges of addresses likely to host SNMP devices. 3. Click Add to add the address range and specifications to the processing queue. 4. Enter any additional range specifications you may require. When you are done, click Next to initiate Discovery. The Discovery Process The Discovery Wizard provides a status message to indicate which address is currently being checked, which addresses have been processed and what network elements have been discovered, and when discovery is complete. The discovered network elements are listed in a tabular display, and some columns feature check boxes that let you select certain options. Select any appropriate options and click Next to move to the next dialog. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 7-3 The options you have selected are put into effect, and those elements slated for a Save are converted into Managed Objects. Click Finish to close this dialog. Results Panel Options During the Results phase of discovery, various options are available. Every column in the Discovery display is active; some are editable, some contain check boxes that activate options, and some contain dropdown menus. The columns in the Discovery display are as follows: Save—Click the check box to create a managed object for this network element. IP Address—Editable; the IP address for this network element. Host Name—Editable; the Host Name for this network element. Class—Menu; the class into which this network element has been placed. Select a class from the drop-down menu. If no Discovery specification is made, the element is placed in RedCell.Config.DiscoveredEntities. Location—Editable; the location of the device. Click on the field to activate it. Type the name of a location or use the Command button to open a browser through which you can specify the location. Schedule Heartbeat—Check box; select this option to automatically schedule a heartbeat for this network element. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 7-4 Schedule Data Collection—Check box; select this option to automatically schedule this network element for data collection. Schedule Resynchronization—Check box; select this option to automatically schedule this network element for resynchronization. Protocol—The protocol (typically IP) associated with this network element. Community—Editable; the SNMP read community for this network element. If no community is specified, only an ICMP “ping” is performed; the SNMP get operation is omitted. SysName—Editable; the SysName of this network element. SysObjectID—Editable; the SysObjectID for this network element. Discovery Options While the Results panel is displayed, the Options buttons on the right side of the dialog are active. These buttons are as follows: Telnet—Opens a Telnet session with the selected network element, if it supports Telnet. HTTP—Opens the default Web page of the HTTP server, if one exists, running on the specified network element. Browse—Reserved for future expansion. Check SNMP—Reserved for future expansion. Select All—Selects all check boxes in the active column. (This option has no effect unless a check box column is active.) Deselect All—Deselects all check boxes in the active column. The Discovery Scheduler The Discovery Scheduler is designed to schedule and launch SNMP Discovery sessions for a specified IP address range. The Discovery Scheduler is accessed by selecting Device Discovery Scheduler from the Device menu. Devices discovered through the Discovery Scheduler are added automatically to StormTracker EMS and appear in the Man- 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 7-5 aged Object Manager as Discovered Entities. Figure 7-2. Discovery Scheduler window To launch a discovery event, you must provide a network address and mask, as well as the sysObjectID of the required device. For convenience, a default sysObjectID can be designated within the StormTracker EMS Properties file. If set, this value will be used for all scheduled discovery events. For more information on the default sysObjectID, refer to the System Management section. In addition, you can choose from several predefined sysObjectIDs. These sysObjectIDs are defined within the classidentifiers.txt file. Creating a Discovery Event Click New or press Alt-N to display the Scheduled Discovery Parameters dialog. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 7-6 Figure 7-3. Scheduled Discovery Parameters dialog The entries in this dialog are as follows: Network Address—Starting IP address to query. Network Mask—Network mask of query. SysObjectID—SysObjectID of devices to query; specify this value directly or click on the Command (...) button to display a Browse dialog. Leave this field blank or type Any to query all sysObjectIDs. Read Community—Specifies a SNMP Read Community for this query. Only devices matching this value will be queried. Executing a Discovery Event Highlight the event and click Execute or press Alt-X to run the scheduled event immediately. Editing the Parameters of a Discovery Event Double-click on the discovery event to be edited, or highlight the event and click Parameters or press Alt-P to display the Scheduled Discovery Parameters dialog box. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 7-7 Scheduling a Discovery Event Highlight the event to be edited and click Schedule or press Alt-S to display the Schedule Discovery Event dialog. Figure 7-4. Schedule Discovery Event dialog The fields in the Schedule Discovery Event dialog are as follows: Time—The time that the discovery event should run. Click on the arrow to display a combo box from which the time can be selected. Interval—The interval at which discovery events should run; displayed as a drop-down list. Available entries are: Once Only, Hourly, Daily, Weekdays, Weekends, Weekly, Monthly, Yearly, User Defined. Deleting a Discovery Event This function is used to remove a discovery event from the system; StormTracker EMS will prompt before deleting. Highlight the discovery event to be deleted and click Delete or press Alt-D. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 7-8 8 Chapter/Managing Objects Overview The Managed Object Manager (MOM) provides StormTracker EMS’s object management functions. The Managed Object Manager lets you view device-specific information, both general (name, description, location) and technical (IP address, vendor, model). In addition, the MOM provides the facilities to define alternate behavior for an object, thereby overriding that object’s Event Template settings. This ensures that events for an object automatically generate a log entry, trigger an alarm, or send an e-mail. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-1 8 Chapter/Managing Objects Elastic Networks Managed Object Manager To access the Managed Object Manager, select Managed Objects from the Config menu. Figure 8-1. Managed Object Manager The Manager uses a tree view. Note that managed objects are categorized by the top-level component; a port on a slot, for example, is displayed under the Slot type and not the Port type. To access a subcomponent of an object, select the node or double-click the object. 8-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 8 Chapter/Managing Objects Filtering the List of Managed Objects Managed Objects are sorted by Object Type; select an object type from the drop-down menu at the top of the dialog to view all objects in that class. Editing or Creating a Managed Object To edit an existing object, select the object and click Edit. To create a new managed object, click New or press Alt-N. Either action displays the Managed Object Editor, which is detailed in the pages that follow. BitStorm The BitStorm panel displays information related to the selected device, i.e., multiplexer, MIU, modem. Select the BitStorm device from the Managed Object Manager, then click Edit to access settings. Figure 8-2. BitStorm Panel 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-3 The fields in the BitStorm tab are as follows: Video Protect Mode Enable- Prioritizes downstream packets for video. When disabled, upstream and downstream speed is equal. CO Modem Trap Enable- Sets the trap for CO modems associated with selected device. CPE Modem Trap Enable- Sets the trap for CPE modems associated with selected device. Reset Shelf- Resets Shelf settings. Configure Multicast Enables multicast for shelf and port settings for 6306 and 10306 modem cards. The shelf tab enables the multicast functionality and allows you to set time parameters. Edit as necessary, then click Apply to save settings. Click Reload to return to original settings. Figure 8-3. Multicast Configuration - Shelf 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-4 The port tab allows you to enable ports in groups of three, i.e., ports 13 are enabled/disabled as a group, as are ports 4-6, 7-9, etc. Select Enable where appropriate, then click Apply to save settings. Figure 8-4. Multicast Configuration - Ports 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-5 Configure Priority Queuing The priority queuing function lets you assign low and high priority queues to packets. High-priority queue packets are given priority over low-priority queue packets. When traffic levels exceed queue capacity, new packets are dropped. Figure 8-5. Priority Queues To configure priority queuing: 1. Select Priority Queuing from the Config menu. 2. Select a BitStorm multiplexer shelf from the Managed Object Manager. 3. Click Edit. This displays the BitStorm panel. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-6 4. Click the Configure Priority Queuing Go button. This displays the Priority Queues screen. 5. Select the Queue Enabled checkbox. 6. Place cursor in each port field, then select Low or High from the drop-down menu. 7. Select a default priority setting from the drop-down menu (Tags 0-3 are low-priority, tags 4-7 are high-priority). 8. Click Apply when finished. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-7 Configure VLAN Enables you to create and edit a VLAN, setting membership access on a port-by-port basis. Figure 8-6. VLAN Configuration To create a new VLAN: 1. Click New. 2. Enter a name in the VLAN field (the name can be changed by highlighting the field and re-entering a new name). To set VLAN Membership: 1. Place cursor in each port field that requires a membership setting. 2. Select a membership option from the drop-down menu. 3. Click Apply to save settings. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-8 Upgrade Firmware Enables you to download firmware for a select device. This feature can also be accessed from the Downloader option under the Device menu. To upgrade firmware, click the corresponding Go button from the BitStorm panel and perform the following steps: 1. Select the Select Firmware Files tab. 2. Click Add to add a new file local to the machine running Downloader. 3. Check the corresponding checkboxes, then click Download. 4. Select the Select Devices to Update tab. The following screen appears: 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-9 5. Select the corresponding checkboxes for the devices you wish to update. 6. Select the Download tab. The following screen appears: 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-10 7. Click Start to begin downloading firmware. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-11 Device The Device panel displays information unique to the device and its deployment within the network. Figure 8-7. Managed Object Editor: Device Panel The fields within the Device tab are as follows: Host Name—Usually defined as the node name, but can be set to any value. IP Address—IP address of the object. Administration Port—The port to query the device; the default is 23 (Telnet). SNMP Read Community—SNMP Read Community of the object. Valid entries are: public, private. SNMP Write Community—SNMP Write Community of the object. Valid entries are: public, private. SNMP sysUp Time—Length of time since the device was restarted. Vendor—Vendor contact of device. Model—Model of device. Serial Number—Serial number of device. Software Version—Software version number of device. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-12 General The General panel displays descriptive information for managed objects and associates them with a location and a contact. Figure 8-8. Managed Object Editor: General Panel Name—The name of the managed object; this name must be unique. Description—A description of the managed object. Administrative State—One of three values, selected from a dropdown menu, defining how the object can be used. The options are: Locked—Device is currently prohibited from use. Shutting Down—Device use is permitted only to existing users. Unlocked—Normal use of device is permitted. Operational State—One of four possible values, selected from a dropdown menu, describing the availability of the managed object. The options are: Disabled—Device is inoperable because of a fault, or resources are unavailable. Enabled—Device is operable and available for use. Active—Device is operable and currently in use with operating capacity available to support further services. Busy—Device is operable and currently in use with no operating 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-13 capacity to spare. Location—Location of object, used for Geographic Topology. Contact—Primary contact for object. Installed Date—Date object was installed. Created—Read-only field indicating the Date/Time the managed object was created. Creator—Read-only field indicating the user who created the managed object. Behavior In certain circumstances, you need to assign unique behaviors to specific objects. The Behavior tab, shown below, lets you accomplish this by letting you specify an override for the object’s Event Template behavior. Figure 8-9. Managed Object Editor: Behavior Panel The fields in the Behavior tab are as follows: Override Event Template Behavior—Utilizes the behaviors specified on this tab for this particular object, instead of the behaviors specified in the Event Template. You can use this check box to turn a set of 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-14 behaviors on and off as needed. Log Events—Select this option to write all incoming events for this object to the log file specified in System Settings. Generate Alarm—This option causes an alarm to be generated for all incoming events for this object. Automatically Send Email—This option sends an e-mail message for every incoming event for this object. The e-mail is sent to the Address of those recipients defined through the Email Recipients dialog. Email Recipients—Click on this button to display the Email Recipients dialog. This dialog lets you define the people to whom e-mail is sent whenever an event is generated by this object, if the Generate Alarm option has been selected. Select recipients from the Available panel and click on the right bracket (>) to move them into the Selected panel. You can click on the doubleright bracket (>>) to move all the names from the Available panel to the Selected panel. Move names out of the Selected panel in the same manner, using the left (<) or double-left (<<) brackets. Forward Event—This option forwards all events received for this object, using the specified settings. These settings are: Forward Host—The IP address/hostname where this event is forwarded. Community—Public or Private; the default is Public. Port—The port where this event is forwarded; the default is 161. CAUTION: CONTACT YOUR ADMINISTRATOR PRIOR TO CHANGING THIS SETTING. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-15 Icon The Icon tab lets you associate each Managed Object with an icon. Select an icon from the list displayed in this tab and click OK. Figure 8-10. Managed Object Editor: Icon Panel 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-16 History The History tab displays information collected by the Data Collection Scheduler. All data collected from the Scheduler can be displayed; for more information see the section on Data Collection. Physical The Physical tab displays the physical location within a multiplexer (this tab does not apply to the multiplexer itself) such as a slot within a BitStorm 1900. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-17 MIU The MIU panel displays information related to the MIU devices within each BitStorm multiplexer in your network. General The General panel displays settings for the MIU. Figure 8-11. MIU General Tab The settings in the General tab are as follows: Name—The name of the managed object; this name must be unique. Description—A description of the managed object. Administrative State—One of three values, selected from a dropdown menu, defining how the object can be used. The options are: Locked—Device is currently prohibited from use. Shutting Down—Device use is permitted only to existing users. Unlocked—Normal use of device is permitted. Operational State—One of four possible values, selected from a dropdown menu, describing the availability of the managed object. The options are: Disabled—Device is inoperable because of a fault, or resources 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-18 are unavailable. Enabled—Device is operable and available for use. Active—Device is operable and currently in use with operating capacity available to support further services. Busy—Device is operable and currently in use with no operating capacity to spare. Location—Location of object, used for Geographic Topology. Contact—Primary contact for object. Installed Date—Date object was installed. Created—Read-only field indicating the Date/Time the managed object was created. Creator—Read-only field indicating the user who created the managed object. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-19 Behavior The Behavior panel includes options for overriding the system event template. Figure 8-12. MIU Behavior Tab Override Event Template Behavior- Check this box to enable alarm notification features. Log Events- Specifies that MIU events be written to a log file. Generate Alarm- Generates an alarm when an MIU event is received. Alarm Severity- Specifies severity of event (Information, Indeterminate, Warning, Minor, Major, or Critical). Automatically Send Email- Sends email to recipients from the selection dialog. Forward Event- Specifies that the event be forwarded to the specified host, using the default or specified community and port settings. Forward Host- Specifies the IP address of the host to which the event is forwarded. Port- Specifies the port to which the event is forwarded. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-20 Icon The Icon panel lets you associate each MIU with an icon. Select an icon from the list displayed in this tab and click OK. Figure 8-13. MIU Icon Panel History The History tab displays MIU information collected by the Data Collection Scheduler. Physical The Physical tab displays the physical location (slot number) of the MIU in the BitStorm multiplexer shelf. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-21 Modem Cards The BitStorm modem card panel displays the model number in the tab title and modem parameter throughout the panel selections. CO Config The CO Config panel displays settings for the selected CO modem port. Figure 8-14. CO: Config Interface Index- SNMP value defined by MIB Slot/CPU/Port- Location of device Firmware Rev.- Version of firmware loaded for the modem Current Modulation- Measured using QAM/QPSK speed values. Speed Count- Automatically calculated based on speed and modulation. Block Broadcast- Blocks broadcast over network to enable unicast communication 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-22 Training Delay- Delay incurred by training sequence when data connection is established Modem Rev.- Revision number of modem board Modem BTEQ- BTEQ version of modem board Clear Stats- Select Normal to log modem statistics, or Clear to delete Traps Status- Select On to enable traps sets for modem events, or Off to disable traps 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-23 CO Statistics Tab The CO Statistics tab displays transmission metrics for the selected CO modem port. Figure 8-15. CO Statistics Interface Index- SNMP value defined by MIB Current TX Speed- Modem transmit speed Current RX Speed- Modem receive speed Up Time- Duration of modem connection Theoretical TX Speed- Theoretical transmit speed Theoretical RX Speed- Theoretical receive speed Max TX Training Speed- Maximum transmit training speed Max RX Training Speed- Maximum receive training speed Local LQF- Local line quality factor on a scale of 100 Remote LQF- Remote line quality factor on a scale of 100 Free Buffer Count- Available storage for data to compensate for differences in transmission speeds or timing Apparent Distance- Estimate of distance between CO and CPE 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-24 modem to the nearest 1000 feet (displayed in Kft) Physical Address- CO MAC address Admin Status- Displays administrative status - Up or Down Operational Status- Displays operational status - Up or Down In Octets- Received octets In Discards- Received discards In Errors- Received errors Out Octets- Transmitted octets Out Errors- Transmitted errors 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-25 CO Spectrum Manager The CO Spectrum Manager panel displays information related to detected other services coexisting with EtherLoop™ in the same binder. Figure 8-16. CO Spectrum Manager Interface Index- This is an SNMP unit of measure for the use of specific extents. Internal Logging- Logs internal information directly to the modem. Mode- Sets one of the selected protection modes: Monitor: Monitors for interference, but does not protect against it Auto-Protect: Protects EtherLoop when asymmetrical services are detected and reports these interferences Force-Protect: Continuously protects EtherLoop from asymmetrical services (even when not detected) Native: Minimum protection/monitoring provided Recent Action: Action taken based on what other services were detected 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-26 Interval- Schedule (in seconds) for monitoring or detecting services in the binder Detected Service- Service detected that may cause potential interference CO Speed Table The CO Speed Table displays transmit/receive speeds for the modem port selected. Figure 8-17. CO Speed Table 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-27 CPE Config The CPE Config panel displays modem details settings for the selected CPE modem port. Figure 8-18. CPE Config Interface Index- SNMP value defined by MIB Description- Displays modem model Interface StatusMAC Address- Modem MAC Address Firmware Rev.- Version of firmware loaded for the modem Current Modulation- Measured using QAM/QPSK speed values. Speed Count- Automatically calculated based on speed and modulation. Modem Rev.- Revision number of modem board Modem BTEQ- BTEQ version of modem board Reset- Resets modem Clear Stats- Select Normal to log modem statistics, or Clear to delete 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-28 Traps Status- Select On to enable traps sets for modem events, or Off to disable traps CPE Statistics The CPE Statistics panel displays transmission metrics for the selected CPE modem. Figure 8-19. CPE Statistics Interface Index- SNMP value defined by MIB Current TX Speed- Modem transmit speed Current RX Speed- Modem receive speed Up Time- Duration of modem connection Theoretical TX SpeedTheoretical RX SpeedEthernet TX Bytes- Amount of Ethernet data transmitted in bytes Ethernet RX Bytes- Amount of Ethernet data received in bytes Ethernet TX Frames- Number of Ethernet frames transmitted 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-29 Ethernet RX Frames- Number of Ethernet frames received Ethernet TX Errors- Number of Ethernet transmit errors Ethernet RX Errors- Number of Ethernet receive errors EtherLoop TX Bytes- Amount of EtherLoop data transmitted in bytes EtherLoop RX Bytes- Amount of EtherLoop data received in bytes EtherLoop TX Blocks- Number of EtherLoop blocks transmitted EtherLoop RX Frames- Number of EtherLoop frames received EtherLoop RX Blocks- Number of EtherLoop blocks received EtherLoop TX Errors- Number of EtherLoop transmit errors EtherLoop RX Errors- Number of EtherLoop receive errors EtherLoop Retries- Number of EtherLoop re-transmission attempts Max TX Training SpeedMax RX Training SpeedLocal LQF- Local line quality factor on a scale of 100 Remote LQF- Remote line quality factor on a scale of 100 Free Buffer Count- Available storage for data to compensate for differences in transmission speeds or timing Apparent Distance- Estimate of distance between CO and CPE modem to the nearest 1000 feet (displayed in Kft) 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-30 CPE Spectrum Manager The CPE Spectrum Manager panel displays information related to detected other services coexisting with EtherLoop™ in the same binder. Figure 8-20. CPE Spectrum Manager Interface Index- This is an SNMP unit of measure for the use of specific extents Internal Logging- Logs internal information directly to the modem Mode- Sets one of the selected protection modes: Monitor: Monitors for interference, but does not protect against it Auto-Protect: Protects EtherLoop when asymmetrical services are detected and reports these interferences Force-Protect: Continuously protects EtherLoop from asymmetrical services (even when not detected) Native: Minimum protection/monitoring provided Recent Action: Action taken based on what other services were detected 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-31 Interval- Schedule (in seconds) for monitoring or detecting services in the binder Detected Service- Service detected that may cause potential interference 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-32 CPE Speed Table The CPE Speed Table displays transmit/receive speeds for the modem port selected. Figure 8-21. CPE Speed Table Adding a Top-Level Managed Object Click New or Alt-N to display the Adding New Managed Object dialog box. Within the Adding New Managed Object dialog box, you can set device-specific general (name, description, location) and technical (IP address, vendor, model) information; object behavior; and the object icon. Note that the object name must be unique. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-33 Adding a New Component to an Existing Managed Object Highlight the Managed Object you want to add to and select New or Alt-N, or right-click on the object and select New Component. This will display a modified version of the Adding New Managed Object dialog box. Since new components often share information with the immediately higher level component, the Adding New Managed Object dialog box will appear with several fields already populated. By default, new components have the same Managed Object Type, Administrative State, Operational State, Location, Contact, Software Version, and Icon as the next higher level. NOTE: All defaulted values can be modified. Other values that can be set include device-specific general (name, description, location) and technical (IP address, vendor, model) information; object behavior; and the object icon. Note that the object name must be unique. Moving Managed Objects There may be occasions when devices are not correctly categorized (such as newly discovered objects being placed under Discovered Entities) and need to be moved from one category to another. To move an object, select it and click Move. The Select Destination window appears, enabling you to select a new destination. Click OK to complete the operation. Deleting a Managed Object This function is used to remove a Managed Object from the system. Highlight the Managed Object to be deleted and select Delete or press Alt-D, or right-click on the object and select Delete. Charting Managed Object Performance Highlight the Managed Object whose performance you wish to monitor, and select Performance or Alt-P, or right-click on the object and select Monitor Performance. The system will display the StormTracker EMS Performance Monitor for the specified object. If the device you have chosen has not had its performance information defined, an error message —There is no perfor- 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-34 mance data defined for this class of equipment —will appear. For more information, please see Performance Monitor. Copying Managed Objects Highlight the Managed Object you wish to copy and click Copy or press Alt-C, or right-click on the object and select Copy from the resulting pop-up menu. This function lets you copy the configuration of a managed object to a new object. Note that the new object must be given a unique name. Mapping Managed Objects This function displays the Logical Topology map, centered on the selected object. Viewing the Data History of Managed Objects This function lets you view object data value changes within a networked environment. Highlight the Managed Object whose history you need to review and select View Data History or press Alt-V, or rightclick on the object and select View Data History from the resulting popup menu. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 8-35 9 Chapter/Network Traffic Management Overview StormTracker EMS™ provides three traffic management configuration options to maximize the efficiency of your network. Multicast- Upstream traffic is prioritized over downstream traffic for optimum video streaming. Priority Queues- High queue packets are prioritized over low queue packets. VLAN- Packets are tagged or untagged for each member for access to designated areas in the network. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 9-1 9 Chapter/Network Traffic Management Elastic Networks Multicast From the shelf tab, multicast functionality is enabled for all ports belonging to the selected shelf. Multicast settings can be configured for shelves housing the 6306 and 10306 modem cards. Figure 9-1. Multicast Configuration - Shelf From the port tab of the Multicast Configuration screen, you can selectively enable/disable ports in groups of three, i.e., ports 1-3, 4-6, 7-9, etc. 9-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 9 Chapter/Network Traffic Management Figure 9-2. Multicast Configuration - Ports To configure multicast: 1. Select a BitStorm multiplexer shelf from the Managed Object Manager. 2. Click Edit. This displays the BitStorm panel. 3. Click the Configure Multicast Go button. This displays the Multicast Configuration screen. 4. From the Shelf panel, select Enable Multicast. 5. Set time parameters as appropriate. 6. Click Apply to save settings (click Reload to return to original settings). Optional: To selectively enable/disable ports in groups of three, select the Ports panel, then select or deselect Enable for respective ports. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 9-3 Priority Queuing Packets can be set to high-priority or low-priority. This feature drops new packets when queues have reached full capacity from high traffic levels. Figure 9-3. Priority Queues To configure priority queuing: 1. Select Priority Queuing from the Config menu. 2. Select a BitStorm multiplexer shelf from the Managed Object Manager. 3. Click Edit. This displays the BitStorm panel. 4. Click the Configure Priority Queuing Go button. This displays the Priority Queues screen. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 9-4 5. Select the Queue Enabled checkbox. 6. Place cursor in each port field, then select Low or High from the drop-down menu. 7. Select a default priority setting from the drop-down menu (Tags 0-3 are low-priority, tags 4-7 are high-priority). 8. Click Apply when finished. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 9-5 VLAN From the VLAN Configuration screen, you can create and edit VLAN’s for each shelf in your network. The VLAN feature allows you to tag packets with the appropriate VLAN membership settings for each port. Figure 9-4. VLAN Configuration To configure a VLAN: 1. Click New to create a VLAN, then enter a name in the designated field. Highlight the name to change it, if necessary. 2. Place cursor in each port field that requires a membership designation, then select an access option from the drop-down menu. 3. Click Apply when finished. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 9-6 10 Chapter/Network Security Management Overview StormTracker EMS™ provides network security with MAC Filtering functionality. This function is accessible from the BitStorm panel of the Managed Object Manager, or the Config menu. MAC Address Filtering The MAC Address filtering function adds or removes MAC address filters from the modem cards within the BitStorm multiplexer. MAC addresses from the shelf selected automatically display in the MAC Filtering Configuration screen list. MAC address filtering operates on a per-CPU basis, therefore, selecting a particular port also selects other ports associated with it. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 10-1 10 Chapter/Network Security Management Elastic Networks Configuring MAC Filters To configure MAC filters: 1. Enter a new MAC address (if necessary) to include any additional MAC addresses not listed, then click Add. 2. Select ports as necessary, then click Apply. 10-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 08-00032-01, Rev. 2.1 10 Chapter/Network Security Management StormTracker EMS User Guide 10-3 11 Chapter/Device Firmware Overview The Downloader feature is used to download device firmware for network hardware upgrades. This feature is accessible from the BitStorm panel of the Managed Object Manager or the Device menu. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 11-1 11 Chapter/Device Firmware Elastic Networks Downloader Upgrading device firmware is a three-part process: selecting firmware files, selecting devices to update with respective firmware files, and downloading firmware files. Select Firmware Files To select firmware files: 1. Select the Select Firmware Files tab. The screen following displays: 2. Click Add to add a new file local to the machine running Downloader. 3. Check the corresponding checkboxes, then click Download to complete to this task. 11-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 11 Chapter/Device Firmware Select Devices to Update To select devices: 1. Select the Select Devices to Update tab. The following screen displays: 2. Select the corresponding checkboxes for the devices you wish to update. OPTIONAL: Click All to select all modems or MIU devices. Click Discover Modems from All MIU’s to display network modems in the modem lists, or click Discover Modems From Selected MIU’s to display network modems associated with selected MIU devices. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 11-3 Download To download firmware files previously selected: 1. Select the Download tab. The following screen displays: 2. Select a maximum number of concurrent downloads from the dropdown menu. This number should be set based on processor speed, free memory, connection speed, etc. 3. Click Start to begin downloading firmware. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 11-4 12 Chapter/Class Manager Overview The Device Class stores object identifiers, or sysObjectIDs, for convenient retrieval. Both the Discovery Scheduler and the MIB Loader utilize this mechanism to let you browse through defined sysObjectIDs. The Device Class Manager, shown below, provides the interface through which sysObjectIDs are managed. Figure 12-1. Select Device Class window 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 12-1 12 Chapter/Class Manager Elastic Networks sysObjectID Operations StormTracker EMS ships with a small number of sample sysObjectIDs; these are provided as examples of the format. As part of your ongoing operations, you will need to edit and/or delete these sysObjectIDs, as well as add the new ones that your installation requires. The Device Class manager lets you add, delete, import, and export sysObjectIDs. Adding or Editing a sysObjectID Adding a sysObjectID and editing an existing sysObjectID are similar operations. Both procedures are as follows: 1. To add a sysObjectID, click New or press Alt-N. To edit an existing sysObjectID, select it and click Edit or press Alt-E.In either case, an Edit dialog appears. The title bar provides either the name of the operation or the sysObjectID. 2. 2. If you are adding an object, type the sysObjectID in the sysObjectID field. If you do not know this value but do know the IP address of the device in question, you can use the Command button (...) to open a Query dialog. Simply type the IP address or the Host name in the Host field and click on Query. 3. Once you have obtained or edited the sysObjectID, edit the Vendor field as appropriate or use the Command button to display a browser, through which you can locate the appropriate vendor. 4. Type or edit the Model name, as appropriate. 5. Associate the device with an equipment class by selecting a class from the drop-down menu. 6. Click OK to store the results. Deleting a sysObjectID To delete a sysObjectID, select it and click on Delete or press Alt-D. Import and Export Operations SysObjectIDs can be imported and exported through the standard 12-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 12 Chapter/Class Manager StormTracker EMS Import/Export dialogs. This allows you to back up your sysObjectID records and/or store them for deployment to other installations. An exported sysObjectID file is similar in structure to this example: # RedCell sysObjectID Export File # Created 09/06/2000 10:30 by admin sysObjectID = 1.3.6.1.4.1.42.2.1.1 equipmentClass = RedCell.Config.Server model = Solaris vendor = Sun sysObjectID = 1.3.6.1.4.1.311.1.1.3.1.1 equipmentClass = RedCell.Config.Workstation model = Windows NT vendor = Microsoft sysObjectID = 1.3.6.1.4.1.2021.250.10 equipmentClass = RedCell.Config.Server model = vendor = Linux sysObjectID = 1.3.6.1.4.1.9.1.110 equipmentClass = RedCell.Config.Router model = 2500 vendor = Cisco # End of File For more information about Import and Export operations, please see Importing and Exporting. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 12-3 13 Chapter/Service Management Overview StormTracker EMS’s Service Management framework gives you the tools to define and create services and their components, including orders, subscriptions, and service level agreements. Service agreements have any number of components, including: • Customers • Groups • Subscribers • Subscriptions • Services • Service Level Agreements • Orders Service Management Components The Service Management Framework consists of a number of discrete managers, each of which performs a specific function. Most managers have a similar interface; features common to all Managers are detailed below. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-1 13 Chapter/Service Management Elastic Networks Figure 13-1. A Typical Manager Dialog Box List Filter—The drop-down menu at the top of the Manager dialog contains the filters for the manager. Select a filter from the list to restrict the display to a certain range. For example, a filter of “A to C” in the Subscriber Manager would restrict the display of subscribers to those having names beginning with A, B, or C. Shortcut: None New—Creates a new record, the type of which is governed by the Manager. In Figure 12-1, a new Subscriber would be created. Shortcut: AltN Delete—Deletes the selected object(s). Shortcut: Alt-D Close—Closes the Manager. Help—Displays the help file for this Manager. Creating Services StormTracker EMS’s Service Management Framework is a dynamic, highly customizable environment designed to let you create the tool 13-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 13 Chapter/Service Management you require. The exact nature of this tool will differ from one installation to the next, as will its appearance and functionality. Because of this, we will present a generalized outline of the Service Management framework. The Basics Once the basic framework is in place, services can be created and managed. A typical service creation scenario will run along these lines: • A subscriber must exist. Subscribers are created and modified through the • • • • Subscriber Manager. Typically, the subscriber is a member of a group. Groups are created and modified through the Group Manager. The subscriber can request a subscription to a specific service. Services are created and modified through the Service Manager. A service can require an Application; applications are created through the Application Manager. Certain equipment may be associated with a service; this is done through the Service Equipment Manager. • An order is created to fulfill the subscription, and a service is implemented according to the terms of a Service Level Agreement (SLA). Orders are orchestrated through the Order Manager. An individual Service Level Agreement can be created at any time, through any of the managers; Service Level Agreement Templates are created and modified through the SLA Template Manager. Service Manager Services can be created “from scratch” or from predefined templates. The following example illustrates the creation of a service from scratch. Note that the only required field is the Service Name. 1. Select Services from the Service menu. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-3 2. Select a service type from the Service Manager’s drop-down menu and click New (or press Alt-N) to create a new service. The types of service are configurable; StormTracker EMS ships with Connection-Service, Application Service, and Service. Figure 13-2. Service Manager Dialog Box—Connection Service The Service Editor, which displays when you elect to edit an existing service or create a new one, is also configurable. Its display is dependent upon the type of service selected. The example presented next represents a new Connection Service, selected from the default Service Manager options. Service Editor—General Panel The fields in the General panel let you name and describe the service. The fields in this panel are as follows: 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-4 Service Name—This service has been named Sample. Note that the service name must be unique. Description—An informative description of this service. Service Editor—SLA Panel The fields in the SLA panel let you define a Service Level Agreement Class for this service, as well as invoke a Service Level Agreement template. Figure 13-3. Service Editor Dialog Box—SLA Panel The fields in the SLA panel are as follows: SLA Class—The class of this service. By default, either SLA or SLAConnectionService. SLA Template—The SLA Template, if any, associated with this service. SLA Name—The name of this service. This name is contained within the service and does not have to be unique. SLA Templates, however, exist outside of a service and must be given a unique name. Once all the entries are made, click OK to save the service. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-5 Application Manager The Application Manager lets you create, modify, and delete applications such as E-mail, HTTP, TCP, or UDP. Figure 13-4. Application Manager Creating and Editing Applications Click on the New button in the Application Manager to create a new application; select an application from the list and click Edit to open it for modification. Either action displays the Application Editor. Figure 13-5. Application Editor 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-6 Application Editor—General Tab Application Name—The name you wish to give this application. Protocol—The protocol this application will be using. The default choices are TCP, UDP, and All. Application Editor—Default Ports Click on Add New Default Port to display the Port Editor. Type the number of the default port and click OK. If more than one port is needed, repeat this operation for each port. SLA Template Manager The Template Manager lets you create and edit service level agreement templates. Figure 13-6. Service Template Manager 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-7 Using the SLA Template Manager To create a new service: 1. Identify the class of service required. StormTracker EMS provides three default services: Connection Service, Application Service, and a generic Service. Select the appropriate service from the dropdown menu. 2. Click New to display the template editor for the selected class of service. 3. Give the new service a name and description, and associate it with a contact, if necessary. 4. Add any required orders to the service. 5. Create a Service Level Agreement (SLA) for the service. Order Manager The Order Manager provides a convenient mechanism for specifying and tracking services delivered to customers. Typically, an order is created after all the other pieces of the system are in place. All orders are created in the Order Manager. Creating or Editing an Order Click New (or press Alt-N) to create a new order; select an existing order and click on Edit (or press Alt-E) to edit an order. Give the order a unique ID and, if needed, an indication of its status. Click on the Services and Subscription tabs, as needed, to add services and/or subscriptions to this order or to view any existing associations. Click OK to save the order and close the dialog, or Apply to save the order and leave the dialog open. Click Cancel to discard any changes. Group Manager The Group Manager provides a mechanism for the creation of logical groups. The default Group Manager provides for two kinds of groups— generic groups and Customers. As with most StormTracker EMS dialogs, more choices can be added through customization. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-8 Adding or Editing Groups To add a new group, select the group type from the drop-down menu and click New or press Alt-N. To edit an existing group, select the group type from the drop-down menu and click Edit, or press Alt-E. In both cases, the Group Editor appears. If you are editing an existing group, some or all fields will have information. Subscriber Manager Subscribers are created and modified through the Subscriber Manager. Adding or Editing Subscribers Add a new subscriber by clicking New or entering Alt-N. Select a subscriber and click Edit (or press Alt-E) to edit that subscriber. The General panel of the Subscriber Editor is identical to the Contact Editor, with the exception of the name of the first field (Subscriber ID). The other panels in the Subscriber Editor are as follows: IP Address—This panel, displayed when an IP Subscriber is being created or edited, lets you associate an IP address, subnet mask, and hardware (MAC) address with a subscriber. Make any required entries or changes, and click on OK to implement them, Cancel to discard them, or click on one of the panel’s other tabs to enter additional information. Subscriptions—This panel displays a list of subscriptions, and lets you add, remove, or edit subscriptions. The controls in this panel are as follows: Add Subscription—Displays the Subscription Editor. Remove Subscription—Deletes the selected subscription. Edit Subscription—Displays the Subscription Editor, prefilled with the information for the selected subscription. When you have finished working with this panel, click OK to implement your changes, Cancel to discard them, or click on one of the panel’s tabs to move to a different area. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-9 Subscription Editor The Subscription Editor, displayed whenever a new subscription is created or an existing one is edited, lets you associate services and orders with a subscription. The Subscription Editor has the following panels: Services—This panel lets you add, remove, and edit services. Orders—This panel lets you add, remove, and edit orders. Contacts Manager The Contact Manager lets you organize and manage your contact. By default, the Contacts list includes all defined groups, subscribers, vendors, and system users. To access the Contact Manager, select Contacts from the Service menu. Note that if a contact is deleted through another Manager—for example, a vendor through the Vendor Manager—the relevant contacts must be deleted separately from the Contact Manager. The Contact Manager dialog initially displays all defined contacts. You can filter the display by selecting one of the predefined filters from the drop-down menu at the top of the dialog, or you can search for a customer by typing text directly into the filter field. Searches are performed on Contact ID and Last Name, and are case-sensitive; if “one” is entered into the combo box, for example, “Customer One” will not be returned. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-10 Figure 13-7. Contact Manager Adding and Editing Contacts Select New or press Alt-N to display the Contact Editor, shown below. Figure 13-8. Contact Editor 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-11 The fields in this dialog are as follows: Contact ID—A unique identifier for this contact. First Name—The first name of this contact. Last Name—The last name of this contact. Address—The address of this contact. Three lines are provided. Phone Number—The drop-down menu associated with this field lets you define three phone numbers for this contact: Work, Home, Other. Pager Number—The drop-down menu associated with this field lets you define three pager numbers for this contact: Work, Home, Other. Mobile Number—The drop-down menu associated with this field lets you define three mobile numbers for this contact: Work, Home, Other. Fax Number—The drop-down menu associated with this field lets you define three fax numbers for this contact: Work, Home, Other. Email—The drop-down menu associated with this field lets you define four e-mail addresses for this contact: Work, Home, Pager, Other. Deleting a Contact This function is used to remove a Contact from the system; StormTracker EMS will prompt before deleting. Highlight the Contact to be deleted, and select Delete or Alt-D. Importing and Exporting Contacts The Contacts file can be exported and imported through StormTracker EMS’s Import and Export utilities. Exported files can be used as backup files or seed files or they can be imported by clients running on other servers. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-12 Vendor Manager Contact information for vendors who supply Managed Objects is created and modified through the Vendor Manager. To access the Vendor Manager, select Vendors from the Config menu. Figure 13-9. Vendor Manager Window. Filtering Vendors The Vendor Manager provides predefined filters to let you restrict the display, and also incorporates a search feature. To use this feature, select a filter from the drop-down menu or type a search value in the filter field. Searches are performed based on the Vendor Name, and are case-sensitive; if “one” is entered into the search field, for example, “Vendor One” will not be returned. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-13 Adding and Editing Vendors Select New or press Alt-N to display the Vendor Editor dialog, shown below. (The title bar of this dialog reflects the current operation.) Figure 13-10. Vendor Editor Dialog Fill out the dialog as appropriate, and click on OK to save the data or Cancel to cancel the operation. The fields in this dialog are as follows: Vendor Name — Short description of vendor. First Name — First name of contact. Last Name—Last name of contact. Address—Three-line address. Phone Number—Can contain up to three phone numbers: Work, Home, Other. Pager Number—Can contain up to three pager numbers: Work, Home, Other. Mobile Number—Can contain up to three mobile phone numbers: Work, Home, Other. Fax Number—Can contain up to three fax numbers: Work, Home, Other. Email—Can contain up to four e-mail addresses: Work, Home, Pager, Other. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-14 Deleting a Vendor To remove a vendor from the system, highlight the required vendor to be deleted, and select Delete or press Alt-D. StormTracker EMS Assure will display a prompt before deleting. Importing and Exporting Vendors The Vendor file can be exported and imported through StormTracker EMS’s Import and Export utilities. Exported files can be used as backup files and seed files or they can be imported by clients running on other servers. For more information regarding the Import and Export functions, please see Importing and Exporting. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 13-15 14 Chapter/Managing Locations Overview The locations of Managed Objects—used when designing Services —are specified within the Location Manager. Note that StormTracker EMS utilizes the concept of “Parent” Locations, where one location can be defined as a subset of another. For example, if network objects are located on the third floor of a facility, both the building and the specific floor can be designated as locations; the building would be defined as the parent of the floor. Using the Location Manager To access the Location Manager, select Locations from the Config menu. The Location Manager Window, shown below, appears. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 14-1 14 Chapter/Managing Locations Elastic Networks Figure 14-1. Location Manager The drop-down menu at the top of the window lets you apply a toplevel location filter to restrict the display. By default, all locations are displayed when the Location Manager first opens. You can select a predefined filter, or you can type in your own specification. The filter lets you specify the full name of a location (California, for example) or part of a name (Ca). Only locations matching that specification are displayed. Note that the filter is case-sensitive. The Location Manager contains the following fields: New—Opens the Location Editor, through which you can define a new location. Delete—Deletes the selected location. Import—Opens the Import utility. Export—Opens the Export utility. Edit—Opens a Location Editor for the selected location. Map—Opens the Topology Viewer, displaying the selected location. Close—Closes the Location Editor. 14-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 14 Chapter/Managing Locations Help—Displays Online Help for the Location Editor. Adding a Location Select New or press Alt-N to display the Location Editor. Enter information regarding the new Location; you can specify name, parent name, address, description, coordinates, and coordinate type. Note that location names must be unique. Defining or modifying a Parent Location From the appropriate location dialog box, click on the Command button (...) to open a Browser dialog from which you can specify the Parent Location. The Parent Location dialog box functions exactly as the primary Location dialog box and lets you add, delete, and edit locations. Editing a Location Highlight the Location and select Edit or press Alt-E; the Location Editor appears. All Location information can be modified, including the name, parent name, address, and description, as well as coordinate type 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 14-3 and specific coordinates. Figure 14-2. Location Editor The Location Editor has the following fields: Location Name—A unique name for the Location. Parent Location—The “parent” (the location to which this location is subordinate) of this location. Click on the Command button (...) to open a Browser through which you can select a Parent Location. Click on the Eraser icon to clear the Parent Location field. Location Type—Type of location, as selected from the drop-down menu. Available types are: Customer, Provider, Other, Area Hub, Regional Hub, National Hub. Coordinate Type—Specifies the way coordinates are designated; see Location Coordinate Types for more information. Valid types are: v-h coordinates, lat-long, NPA-NXX, country-city, ST-Country, CITY-ST. Coordinates—Coordinates of location, using the Coordinate Type specified above. Address—Three-line address of location. Location Details—Detailed description of location. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 14-4 Location Coordinate Types StormTracker EMS lets you define locations using a variety of coordinate types, enabling accurate definition of locations. The default coordinate types are as follows: v-h coordinates—Vertical / horizontal coordinates, developed by Bell Systems. lat-long—Latitude and longitude. Example: 38.57N, 121.47W NPA-NXX—Area code and prefix. Example: 916-939 country-city—Country and city access codes. Example: 049-071 CITY-ST—City and state. Example: Sacramento, CA Deleting a Location Highlight the location to be deleted, and select Delete or press Alt-D to remove a Location from the system. StormTracker EMS will prompt you before deletion. Importing and Exporting Locations Locations can be imported and exported through StormTracker EMS’s Import and Export utilities. Exported files can serve as backups or as seed files, and can be imported by clients running on other servers. For more information, please see Importing and Exporting. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 14-5 15 Chapter/Link Manager Overview The Link Manager lets you create and edit both logical and physical links. Figure 15-1. Link Manager 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 15-1 15 Chapter/Link Manager Elastic Networks The Link Manager displays a tree listing of all defined links. The listing can be filtered by any combination of three fields: Link type—Select Link (displays all links), or select Physical or Logical from the drop-down menu to restrict the display to the specified link type. A End Point, Z End Point—These entries specify the head and the tail of the list. Click on the Command button (...) to display a list of links. Select the appropriate link from this list and click OK to set it as the A or Z end point. The list is then filtered to display only links between these points. Using the Link Manager To create a new link or edit an existing link: 1. Select a link from the list and click Edit, or click New. These actions display the Link Editor in a blank state (for a new link) or prefilled with the values of the link being edited. 2. The Link Editor appears with the General tab active. Give the link a name and set the A and Z End Points. Both end point fields feature a command button, which can be used to select the appropriate end point from a list of links. 3. Click OK to create the link. Importing and Exporting Links Links can be imported and exported through StormTracker EMS’s Import and Export utilities. Exported files can serve as backups, as seed files, and can be imported by clients running on other servers. For more information, please see Importing and Exporting. 15-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 08-00032-01, Rev. 2.1 15 Chapter/Link Manager StormTracker EMS User Guide 15-3 16 Chapter/Data Collection Scheduler Overview The Data Collection Scheduler is used to schedule and perform status queries on predefined Managed Objects. To access the Data Collection Scheduler, select Data Collection Schedule from the Config menu. Currently, the Data Collection Scheduler collects the SNMP SysUpTime of the queried device and populates the retrieved value into the Device panel of the Managed Object Manager. In addition, if the initial SysUpTime is greater than the newly received value, an alarm is generated. Note that one status query may contain several devices; in this case, the information is retrieved in the order in which the devices are specified. To change the order in which data is retrieved, simply rearrange the devices within a query. By default, the query will be executed daily, at 1:00 AM local time. Both the time and frequency of execution can be changed through the Data Collection Scheduler. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 16-1 16 Chapter/Data Collection Scheduler Elastic Networks Figure 16-1. Data Collection Scheduler Creating a Data Collection Query A data collection query is created by specifying one or more Managed Objects to process, setting the parameters of the query, and setting up 16-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 16 Chapter/Data Collection Scheduler the schedule. Click New to display the Scheduled Event dialog. Figure 16-2. Scheduled Event Dialog The managed objects listed in this dialog will be processed in the order in which they appear. To change their respective order, select one and click Move Up or Move Down until it is in the desired position. Click Remove to remove the selected object from the list. Adding Managed Objects If you need to add objects to the list, click Add or press Alt-A. The Select Managed Object dialog, shown below, appears. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 16-3 Figure 16-3. Select Managed Object Dialog Select a category of objects for display from the drop-down menu at the top of the dialog. Then, select one or more objects from the resulting list and click OK. If the object you need does not appear on the list, you can import it by clicking Import; once imported, it appears under the appropriate category. Removing a Managed Object from a Query Highlight the object in the list and click Delete or press Alt-R to 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 16-4 remove it from the query. The selected Managed Object will be removed from the query. Editing the Parameters of a Data Collection Query You can modify the parameters of an existing Data Collection query by double-clicking on query to be edited, or by highlighting the query and selecting Parameters (or entering Alt-P) to display the Scheduled Event dialog box. Scheduling a Data Collection Query Highlight the query to be edited, and click Schedule or press Alt-S. Modify the schedule information for Data Collection queries, including the time to start and the interval between queries. Figure 16-4. Scheduling Data Collection Query dialog The fields in the Scheduling Data Collection Query dialog are as follows: Active—Select this option to activate this query. Start Time—Specify a start time for this query by selecting one of the twenty-four hourly options from the drop-down menu. Interval—Specifies the interval between executions of this process. Executing a Data Collection Query Highlight the query and click Execute or press Alt-X to run the scheduled query immediately. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 16-5 17 Chapter/Device Synchronization Scheduler Overview The Device Resynchronization Scheduler is used to automate the resynchronization of managed devices according to a preset schedule. During resynchronization, all managed objects are queried to determine whether their values matched the stored values. Any values that have changed since the last resynchronization (or, if this isn’t applicable, since discovery) are updated. By default, resynchronization is executed daily, at 2:00 AM local time. Both the time and frequency of execution can be changed through the Device Resynchronization Scheduler. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 17-1 17 Chapter/Device Synchronization Scheduler Elastic Networks Figure 17-1. Device Resynchronization Scheduler Creating a Scheduled Device Resynchronization A device resynchronization schedule is created by specifying one or more Managed Objects to process, setting the parameters of the resynchronization, and setting up the schedule. First, click New or press AltN to display the Scheduled Event dialog. 17-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 17 Chapter/Device Synchronization Scheduler Figure 17-2. Scheduled Event Dialog The managed objects (or groups of objects) listed in this dialog will be processed in the order in which they appear. To change their respective order, select one and click on Move Up or Move Down until it is in the desired position. Click Remove to remove the selected object from the list. Adding Managed Objects If you need to add objects to the list, click on Add or press Alt-A. The Select Managed Object dialog, shown below, appears. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 17-3 Figure 17-3. Select Managed Object Dialog Select a category of objects for display from the drop-down menu at the top of the dialog. Then, select one or more objects from the resulting list and click OK. If the object you need does not appear on the list, you can import it by clicking Import; once imported, it appears under the appropriate category. Removing a Managed Object from the Schedule Highlight the object in the list and click Remove or press Alt-R to remove it from the resynchronization schedule. Device Resynchronization Schedule Parameters You can modify the parameters of an existing Device Resynchroniza- 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 17-4 tion schedule by double-clicking on the schedule to be edited, or by highlighting the schedule and selecting Parameters (or entering Alt-P) to display the Scheduled Event dialog box. Scheduling Resynchronization Highlight the resynchronization schedule to be edited and click on Schedule or press Alt-S. Modify the schedule information, including the time to start and the interval between resynchronizations. Figure 17-4. Scheduling Device Resynchronization dialog The fields in the Scheduling Device Resynchronization dialog are as follows: Active—Select this option to activate this resynchronization schedule. Start Time—Specify a start time for this resynchronization schedule by selecting one of the twenty-four hourly options from the drop-down menu. Interval—Specifies the interval between executions of this process. Executing Device Resynchronization Highlight the resynchronization schedule and click Execute or press Alt-X to run the scheduled resynchronization immediately. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 17-5 18 Chapter/SNMP Diagnostic Utilities Overview The Launch Console Device menu provides access to several diagnostic utilities, including an SNMP Trap Viewer and a MIB Browser. The SNMP Trap Viewer Select Trap Viewer from the Device menu to launch the Trap Viewer. The SNMP Trap Viewer is a simplified version of the Alarm Window and can be useful as a diagnostic tool. It displays information regarding incoming SNMP traps, including the sending agent, the trap type, time received, system uptime, OID, and trap value. In addition, the Examined column lets you double-click on a trap to indicate that it has been investigated. Note that the Trap Viewer does not total similar incoming traps; every trap receives an entry. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 18-1 18 Chapter/SNMP Diagnostic Utilities Elastic Networks Figure 18-1. SNMP Trap Viewer To clear all events in the viewer, use the Clear button at the bottom of the display. If necessary, the display can be paused and resumed, using the Pause and Continue buttons. SNMP Trap Viewer Columns The SNMP Trap Viewer has the following columns: Examined—This column is used to mark investigated traps; defaults to False. Agent—This column displays the IP address of the agent sending the trap. Type—This column displays the SysObjectID of the sending agent; the trap viewer will resolve to system (1.3.6.1.2.1.1) or enterprise (1.3.6.1.4.1). Received at—This column displays the date and time that the trap was received. Running since—This column displays the system uptime of the trap 18-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 18 Chapter/SNMP Diagnostic Utilities emitter; displayed in hh:mm:ss format. OID—This column displays the ObjectID of trap. Value—This column displays the trap value. Trap Viewer Controls The buttons at the bottom of the SNMP Trap Viewer have the following functions: Clear—Clears all traps within the viewer. Pause—Pauses the display of incoming traps without affecting the flow of incoming traps. Continue—Resumes the display of incoming traps, and displays any traps received while viewing was paused. The MIB Browser The SNMP MIB Browser allows you to quickly browse through a device’s MIB, get and set values for given OIDs, or walk a node. To access the MIB Browser, select MIB Browser from the Device menu. Figure 18-2. SNMP MIB Browser 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 18-3 Using the MIB Browser The MIB is displayed on the left side of the browser window; the highlighted OID and Value are displayed on the right. If desired, additional MIBs can be added from a text file and browsed through the console as well. Note that the MIB Browser uses mediation; therefore, the Mediation Agent must be running to access MIBs. The fields in the MIB Browser are as follows: Host—The IP address of host to browse. Port—The port to access; the default for SNMP traffic is 161. Read—The SNMP Read Community; allowable values are Public or Private. Write—The SNMP Write Community; allowable values are Public or Private. Retries—The number of times to attempt a retry; default is 2. Timeout—The number of seconds to wait before timeout; default is 10. OID—Displays the selected OID. Value—Displays the value of the selected OID. Add MIB—Imports a MIB for viewing. To add a MIB, browse to the file location, select the file, and click on Open. The MIB is then added into the browser and may be opened. Note that the MIB is added only for the duration of the session. Get—Performs a get on the selected OID. To get an OID, type a host IP address in the Host field, browse to the desired OID, and click on Get. Next—Performs a get on the next OID. Cancel—Cancels the current operation. Walk—Walks the node; performs a multiple get on all OIDs. To walk a node, type a host IP address in the Host field, browse to the desired node, and click on Walk. Set—Perform a set on the selected OID. To set an OID, type a host IP address in the Host field, browse to the desired OID, type the new value in the Value box, and select Set. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 18-4 19 Chapter/Cut-thrus Overview StormTracker EMS’s “Cut-thrus” provide a convenient way to open a Telnet session with a managed object or view a Web page hosted by a managed object. In both cases, StormTracker EMS automatically supplies the IP address of the current managed object. HTML Cut-thru The StormTracker EMS HTTP Cut-thru lets you establish an HTML session with a managed object without requiring you to know its IP address. Launch the HTTP cut-thru by selecting HTTP Cut-thru from the Device menu. Loading an HTML Document Type the IP address of a device hosting an HTTP server or type its URL. You can also select from the list of Managed Objects by clicking on the Command button. This action displays a dialog listing the managed objects; select one from the list and click OK to populate the IP address field with the IP address of that device. If a functioning HTTP Server exists at the specified address, and if a default HTML document can be found, it is displayed in the workstation’s default browser. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 19-1 19 Chapter/Cut-thrus Elastic Networks Figure 19-1. HTML Session with Router The HTTP Cut-thru is typically used to interact with Web-based utilities, such as the Router Management utility displayed in the previous illustration. Telnet Cut-thru The StormTracker EMS Telnet Cut-thru lets you establish a Telnet session with a specified device, typically a Managed Object. To launch the Telnet Cut-thru, select Telnet Cut-thru from the Device menu. Opening a Telnet Session Type the IP address of the device with which you want to establish the Telnet session or click on the Command button to display a list of managed objects. Select a device from the list and click OK to populate the IP address field with that of the specified device. Select Connect to begin the session. Click on Local Echo if you want the text you are typing to be displayed in the Telnet window. 19-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 19 Chapter/Cut-thrus Figure 19-2. Telnet Cut-thru frame. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 19-3 20 Chapter/Topology Overview The Geographic and Logical Topology functions provide a visual representation of the geographical and logical placement of managed objects, as well as their hierarchical relationships. Physical Topology provides you with a representation of the actual device and any components that may reside within. The Topology viewers let you view and monitor network devices, as well as respond to network alarms. Geographical Topology Select Geographic Topology from the Config menu to display the Geographical Topology Viewer, shown below. This viewer initially displays the Top Level geographic map of the organizational hub. The locations and associated devices within the hub are mapped based on all or part of the organization’s network configuration. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-1 20 Chapter/Topology Elastic Networks Figure 20-1. Geographic Topology Viewer The Top Level of the Geographic Topology viewer provides access to specific geographic locations. To access any of these locations, doubleclick the associated icon or right-click within the icon and select Open from the resulting pop-up menu. Geographic Topology Viewer Options Right-click on any object displayed within the Geographic Topology Viewer to access the pop-up menu shown here. The functions within this menu are as follows: Drill—Opens the next lower level of the topology map in the same window. Alarms—Opens the Alarm Window and displays the alarms (if any) associated with the current device. 20-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 20 Chapter/Topology Logical Topology—Opens the Logical Topology Viewer and displays the associated Managed Objects, Contacts, Vendors, Locations, and Physical Links between managed objects and network devices. (See Logical Topology on page 127.) Open—Opens the next lower level of the topology map in a new window; the lowest level is the device level. Figure 20-2. Geographic Topology at the Device Level Edit—Displays the Location Editor for the selected object. See Editing a Location for more information. Zoom In—Increases the current viewing scale. Zoom Out—Decreases the current viewing scale. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-3 Network Topology Viewers Both the Geographical and Logical Topology Viewer feature the following options, available through buttons at the bottom of the viewer: Refresh—Reinitializes the view of the current window. Reorder—Recalculates the layout of the entities within the window using available data. Add—Allows the user to add additional Locations, Managed Objects, Vendors, and Contacts. To add an entity, click on this button and select an entity from the resulting pop-up menu. Add Link—Activates Link mode. The cursor turns into a cross-hair to indicate that Link mode is active. Click and drag from one object to another to create a link between them. Options—Displays the Spring Layout settings panel for adjusting the viewer linked objects visual expansion. Filters—Allows user to modify what filtered network entities will be displayed. Close—Closes the current window. Editing a Managed Object This function is used to display the Edit Device panel for managing a specific device or set of devices within the network configuration of a site. To access, right click and select Edit on the local device you want to review or change. Device settings are detailed in Chapter 7, Managing Objects. Viewing Object Alarms Right-click on any managed object icon to display the Alarm Window and any outstanding alarms associated with the device. From the Alarm window, you can acknowledge and/or clear the alarms as well as attend to any other alarm management tasks. Please see Chapter 19, Alarms for more information about the Alarm Window and alarm management. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-4 Logical Topology The Logical Topology Viewer lets you display, organize, and manage devices and objects within the network configuration. Additionally it is used to maintain all Managed Objects, Contacts, Vendors, Locations, and Physical Links information between devices. To display the Logical Topology Viewer, right-click on an object and select Logical Topology from the pop-up menu. Figure 20-3. Logical Topology Viewer window 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-5 Adding or Removing Filters From the Logical Topology Viewer window, click Filters to display the Filters dialog. Select or deselect filters as needed and click OK to store your changes. Figure 20-4. Filters Dialog Layouts Logical Topology can be viewed in either of two layouts— Spring or Tree. Select the type of view by right-clicking on a blank area within the Logical Topology viewer. The resulting pop-up menu lets you select Spring or Tree layout, and lets you expand (Zoom In) or contract (Zoom Out) the current scale. Figure 20-5. Logical Topology Viewer Layout Pop-up Menu 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-6 Spring Layout Spring Layout connects entities by their centers, as if they were connected by springs. The arrangement of the entities is adjusted until equilibrium is reached. Figure 20-6. Logical Topology Viewer: Spring Layout 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-7 To display the settings dialog for Spring Layout, click Options at the bottom of the Logical Topology viewer. Figure 20-7. Spring Layout Settings The fields in the Spring Layout Settings dialog are as follows: Propagate—When selected, changes to any individual entity cause the positions of connected entities to be recalculated. Use objects’ sizes—Utilizes the relative size of each object to determine its weighting, and hence its relative placement. Fix selected objects—Specifies that the selected objects remain in their current position. Automatic edge length—Calculates the length of the links and the relative spacing of the entities with respect to the containing window. Edge length constant—If Automatic edge length is not selected, specifies the length of links and the relative spacing of entities. Repaint period—Determines the interval between repaints. Epsilon—The epsilon constant determines when the iterative process for the spring embedder should stop. The greater this constant, the faster the layout, but the more distant the final position from the optimal layout. Apply—Applies the current settings. Reorder—Recalculates the positioning of entities without refreshing the data from the database. Close—Closes the Settings dialog. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-8 Tree Layout Tree layout displays objects as a hierarchy, beginning with the root node. The tree can be oriented vertically or horizontally. Figure 20-8. Logical Topology Viewer: Tree Layout To display the Tree layout settings dialog, click on Options at the bottom of the Logical Topology viewer. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-9 Figure 20-9. Tree Layout Settings The settings in this dialog are as follows: Propagate—When selected, changes to any individual entity cause the positions of connected entities to be recalculated. Root—This read-only field displays the name of the root entity. Grab root...—Click this button to display the Grab root dialog, which enables you to specify the root entity. Tree orientation—Select the radio button corresponding to the desired 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-10 direction of orientation. The label on each button (Left, Top, Right, Bottom) indicates where the tree will start. A tree orientation of Top, for example, will place the root node of the tree at the top, with each successive level proceeding toward the bottom of the graphic. Layout order—Specifies whether the entities should be placed according to their order in the database listing (List Order) or according to their current position (Closest position). Layout Method—Determines the methodology used to place the graphics. The options are: Compact—Places the objects as close together as possible. Fixed Spacing—Places the objects a specified distance from each other. Use objects’ sizes—Utilizes the size of the object to determine its placement with respect to the other objects. Horizontal Fixed Spacing—Specifies the horizontal distance between objects, in pixels, when Fixed Spacing is turned on. Vertical Fixed Spacing—Specifies the vertical distance between objects, in pixels, when Fixed Spacing is turned on. Apply—Applies the current settings. Reorder—Recalculates the layout of the entities within the window using available data. Close—Closes the dialog. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-11 Physical Topology Physical Topology provides you with a graphical representation of the equipment being monitored. It provides for “nesting,” giving you the ability to monitor, for example, a card in a slot within a switch. Figure 20-10. Physical Topology View of a Device with Ten Slots 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 20-12 21 Chapter/Managing Events Overview StormTracker EMS’s Event Templates determine whether, when, and how events are turned into alarms. A default set of Event Templates is provided with StormTracker EMS; these can be modified to better suit your own requirements or can be augmented with new ones. Event Templates are created, modified, and deleted through the Event Template Manager, shown below. To display the Event Template Manager, select Event Templates from the Assurance menu. Figure 21-1. Event Template Manager 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 21-1 21 Chapter/Managing Events Elastic Networks Event Template Organization Event Templates are organized according to the general source of the event: ASCII, RMON Notification, SNMP Enterprise Trap, SNMP MIB-II Trap, SNMP Notification, TL1, and Other. You can view all event templates (the default), or you can select a category from the drop-down menu and view, for example, only TL1 event templates. Editing a Template To edit an existing template, select it from the list of templates and click Edit. The Event Template Editor displays with the selected template loaded. The Event Template Editor is divided into five tabbed sections: Information, Behavior, Advisor, Email, and Icon. Each section is explained, in turn, in the pages that follow. 21-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 21 Chapter/Managing Events Information Panel The Information panel contains entries that let you name and describe the event associated with the template, and the event category covered by the template. Figure 21-2. Edit Event Window: Information Panel The fields in the Information panel are as follows: Event Name—Name of the Event. Description—Short description of the Event. Event Type—Classification of event; displayed as a drop-down box. Possible values are: Other, ASCII, RMON Notification, SNMP Enterprise Trap, SNMP MIB-II Trap, SNMP Notification, and TL1. SysObjectID—(SNMP Enterprise Traps only) The SysObjectID associated with the event. Event Identifier—For SNMP, the trap value; for ASCII or TL1, a specified Identifier. Service Affecting—Select this checkbox if the associated event affects service to this managed object. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 21-3 Behavior Panel The Behavior panel lets you specify how an event is handled and categorized, and what action is taken. Figure 21-3. Edit Event window: Behavior Panel The settings in the Behavior panel are as follows: Log Event—Select this option to specify that all incoming events be written to a log file. Log file settings are specified in System Settings. Generate Alarm—Select this option to generate an alarm (the default) when an event of this type is received. If this option is not selected, the event is still available for logging. Alert Severity—This drop-down menu lets you specify a severity (Information, Indeterminate, Warning, Minor, Major, or Critical) to the event. Apply Correlation—Select this option to enable simple correlation. When correlation is applied, StormTracker EMS will clear an initial event when a correlated event subsequently occurs. For example, if a linkDown event is subsequently followed by a linkUp event, the link- 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 21-4 Down event is automatically cleared. Event...—Click on the Event command button to display the Select Event dialog. This event is the correlated event to be used when Apply Correlation is selected. Apply Threshold—Select this option to put thresholding into effect. The threshold is the number of events that must be received before an alarm is raised. Threshold Count—If Apply Threshold has been selected, this field lets you specify the number of events that must be received before an alarm is raised. Threshold Window Minutes—This field is used in conjunction with the Threshold Count field when Apply Threshold has been selected. It specifies, in minutes, the period of time within which the specified number of events must be received. Seconds—The value specified here is added to Threshold Window Minutes to precisely define the period of time within which the specified number of events must be received. Automatically Send Email—Select this option to send e-mail to the user(s) defined in the Email panel whenever this event is received. Forward Event—Select this option to specify that the event be forwarded to the specified host, using the default or specified community and port settings. Community—If Forward Event has been selected, this entry defines the Community: Public, Group, or Private. This entry defaults to Public. Forward Host—If Forward Event has been selected, this entry specifies the IP address of the host to which the event is forwarded. Port—If Forward Event has been selected, this entry specifies the port to which the event will be forwarded. The default is port 162, the SNMP port. CAUTION: CONTACT ADMINISTRATOR PRIOR TO CHANGING THIS SETTING. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 21-5 Advisor Panel The Advisor panel provides an explanation for the event and may propose a remedy. This message originates with the trap’s MIB. Figure 21-4. Edit Event Window: Advisor Panel The text in this panel can be edited. Make any appropriate changes and click OK to save them or Cancel to cancel the operation. Advisor text appears within the detailed alarm view in the Alarm window, and is the default text for any e-mails sent. Email Panel The Email panel lets you define a subject and message for an email message to be associated with an event. If the Automatically Send Email option in the Behavior panel is selected, this email is sent automatically any time the associated event is received. Note that although additional e-mail addresses can be defined, the Work address is used. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 21-6 Figure 21-5. Edit Event window: Email Panel The fields in the Email panel are as follows: Email Subject—This field is initially set to the Event Description, as defined in the Information panel. Edit it as appropriate. Email Message—This field is initially set to the text defined in the Advisor panel. Edit it as appropriate. Recipients—Click on this button to display the Automatic Email Recipients dialog, shown in the next illustration. This dialog displays all defined StormTracker EMS users; select one or more users from the Available list and click on the right (>) bracket to move them into the Selected list or click on the double-right (>>) bracket to move all the users into the Selected list. Remove users from the Selected list by selecting them and clicking on the left (<) bracket. Once you have selected the desired recipients, click OK to implement your choices or click Cancel to cancel the operation. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 21-7 Figure 21-6. Automatic Email Recipients Selection dialog Icon Panel The Icon panel lets you associate an icon with the event. Select an icon from the list, based on the severity you want to associate with the selected event, and click OK. Select (None) to display no icon. Figure 21-7. Edit Event Window: Icon Panel 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 21-8 Adding an Event Template Click New or press Alt-N to display the Adding New Event Template dialog. This dialog is identical to the Event Template Editor. Fill out the panels in this dialog as appropriate, and click OK to store the new template or Cancel to cancel the operation. Deleting an Event Template This function is used to remove an Event Template from the system. Highlight the Event Template to be deleted and select Delete or press Alt-D. StormTracker EMS prompts you to confirm the deletion. Importing and Exporting Event Templates Event Templates can be imported and exported through StormTracker EMS’s Import and Export utilities. Exported files can serve as backups or as seed files, and can be imported by clients running on other servers. For more information, please see Importing and Exporting. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 21-9 22 Chapter/Alarms Overview The Alarm Window is used to display information about and allow acknowledgement of received alarm-level events. To access, select Alarm Window from the Assurance menu. Alarms displayed within the Window are color-coded based upon their severity, and are displayed until cleared. To aid in troubleshooting, alarms may be e-mailed from inside the Alarm Window. To see more detailed information on a given alarm, double-click on the alarm, or right-click and select Show detail from the pop-up menu. Although the window is listening for alarms by default, the user can quickly disconnect and reconnect by clicking on the Network Connection button. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-1 22 Chapter/Alarms Elastic Networks Figure 22-1. Alarm Window Alarm Severities StormTracker EMS ships with the following alarm severity definitions: Critical—A service-halting condition has occurred and immediate corrective action is required. Example: The managed object is totally out of service and its capability must be restored. Major—A service-affecting condition has developed and corrective action is required. Example: There is a severe degradation in the capability of the managed object and its full capability must be restored. Minor—A non-service-affecting fault condition exists and corrective action should be taken in order to prevent a more serious (for example, service affecting) fault. 22-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 22 Chapter/Alarms Example: The detected alarm condition is not currently degrading the capacity of the managed object. Warning—The detection of a potential or impending service affecting fault, before any significant effects have been felt. Action should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a more serious service-affecting fault. Example: The detected alarm condition does not currently pose a problem, but may degrade the capacity of the managed object if corrective action is not taken. Indeterminate—The severity level cannot be determined. Information—General information about the condition of the overall system. Alarm Window Views The Alarm Window contains fields that enable the operator to quickly determine the location, severity, and nature of an alarm. The Alarm Window display is fully customizable; columns can be added, deleted, sorted, or reorganized as the user sees fit. Once modifications have been made to an Alarm Window view, it can be saved and accessed later. Previously created views can be accessed from the View menu. StormTracker EMS will remember the view used last, regardless of whether it was saved. Inserting Columns—To insert a column, right-click on a column header, select Insert Column from the resulting drop-down menu, and select the desired column from the submenu. Removing Columns—To remove a column, right-click on the header of the column to be removed and select Remove Column from the 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-3 resulting pop-up menu. Moving Columns—Click on the heading of the column you wish to move and drag it to its new position. Resizing Columns—Select the column margin and resize by dragging. The column will be resized accordingly. Column Sort Direction—Right-click on the heading of the column you wish to sort and select Sort Ascending or Sort Descending from the resulting pop-up menu. The selected column is then resorted according to your selection. Creating a View—A new view is created whenever you make changes to an existing view. Once a view is arranged to your liking, you can preserve it by saving the view. Selecting a View—Select the desired view from the View drop-down box at the top of the alarm window. The alarm window’s display will change to the selected view. Saving a View—To preserve the current arrangement of columns, click on Save View. The Create New View dialog, shown below, appears. Figure 22-2. Create New View dialog The fields in the Create New View dialog are as follows: View Name—Type a unique name for the view. If a view already exists with this name, a warning dialog appears. If you save a view with the same name as an existing view, the existing view will be overwritten. Public?—Specifies that the view can be used by anyone. Group Owned?—Specifies that the view can be used by anyone in the same group as the view’s creator. Owned?—Specifies that the view can only be used by its creator. Click on Save to save the view, or Cancel to cancel the operation. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-4 Deleting a View—To delete a view, click on the Views button to display the Manage Views dialog. All defined views are displayed in this dialog. To delete one, select it from the list and click on Delete. Figure 22-3. Manage Views dialog Alarm Window Columns Any or all of the following columns can be inserted into a view: Icon—The icon column displays a graphic appropriate to the severity level. While the alarm is unacknowledged, the icon blinks. Managed Object—The name of the Managed Object sending the alarm. Description—A description of the alarm. Date/Time—The date and time an alarm was received. If more than one alarm has been received, the time displayed reflects the most recent alarm. Source—The IP address of the object sending the alarm. Severity—Severity of alarm. Acceptable values are Critical, Major, Minor, Warning, Indeterminate, and Information. Ack By—Displays the logon name of the User, if any, who acknowl- 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-5 edged the alarm. If new alarms have come in since the alarm was acknowledged, an asterisk (*) is displayed after the user name. Ack Time—The date and time, if any, that the alarm was acknowledged. Event count—Number of received alarms of the same type— both acknowledged and unacknowledged. Event name—The name of the event generating the alarm (linkDown, for example). Type—The type of alarm (SNMP, for example). Alarm Window Filters The Filter Manager lets you design a filter to limit the display of alarms in the Alarm Window to those meeting certain criteria. Click on the Filters button to display this dialog. Once filters have been created, they may be accessed from the Filter drop-down box at the top of the Alarm Window. Figure 22-4. Filter Manager 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-6 The Filter Manager displays, by default, a list of all defined filters. You can also select a group from the drop-down menu and restrict the display to Public filters, Group filters, or Private filters. Creating or Editing a Filter To create a filter, click New in the Filter Manager. Type the name of your new filter in the Filter Name field. To edit an existing filter, simply select it from the list and change values as necessary. Once you have made any changes, the Save button becomes active. The Filter Manager dialog is divided into three tabbed panels: Dates, Event Props, and Owner. Enter the appropriate information in each of these panels. Once you have defined all the criteria for your filter, click Save to save it or Cancel to cancel the operation. Click Close to close the Filter Manager. Dates This panel of the Filter Manager lets you define the start and end dates and/or times for this filter. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-7 Start Date—Type, in month/day/year format, the starting date for this filter. Only events occurring on or after this date will be displayed. You can also click on the command button to display an interactive calendar. Select the appropriate year and month from the drop-down menus, then click on the appropriate day. The selected date is entered into the Start Date field. Start Time—Type the start time for this filter, or select it from the drop-down menu. End Date—Type the ending date for this filter, or select it from the interactive calendar in the same manner as for the Start Date. End Time—Type the ending time for this filter or select it from the drop-down menu. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-8 Event Props The Event Props panel lets you define the Event Properties that this particular filter will monitor. You may choose any combination of Managed Objects, Events, Severities, and Locations. Build this portion of the filter by selecting the appropriate tab. The properties associated with that tab appear in the Available column, on the left. To include any of the available properties, click on it and click the single right bracket (>). The selected property moves into the Selected panel. You can move all the properties into the Selected panel by clicking on the double right bracket (>>). Conversely, you can remove selected properties singly (<) or all at once (<<). 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-9 Owner The Owner panel of the Filter Manager lets you set the availability of the filter. Select the radio button appropriate to the availability you desire. Public filters may be used by any user; Group filters may be used by any user belonging to the same group as the filter creator; and Private filters (the default) may only be used by the filter creator. Status The Status area of the Filter Manager, on the lower right, shows you the current definition of the filter.The Status area above indicates that the filter being constructed will display alarms of any severity, from any location, generated by any managed object, and is available to anyone. (This is the filter.) Selecting a Filter Click the Filter drop-down box at the top of the alarm window and select the desired filter. The alarms are then displayed again according to the criteria of the selected filter. Deleting a Filter To delete a filter, select the Filters button at the bottom of the alarm window, highlight the filter you wish to delete, and click Delete. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-10 Online Alarm Operations Once an alarm is received and displayed in StormTracker EMS, several options are accessible. To display this menu, select an alarm and rightclick within that alarm. The options in the Alarm pop-up menu are as follows: Show Detail...—Select this option to display detailed information about the selected alarm. The Event Detail is divided into four panels. Figure 22-5. Event Detail Window 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-11 The panels in the Event Detail window display the following: Event Detail—Breaks the event down into its component parts and displays the attribute along with the value for that attribute. Event attributes include: Managed Object—The associated Managed Object; if the object is unknown, ‘NotFound’ will be displayed. Description—Text description of alarm; defined in the relevant Event Template. Date/Time—Date and time alarm was received. Status—Current status of alarm; can be either Open or Closed. Severity—Severity of alarm. The degrees of severity are: Critical, Major, Minor, Warning, Indeterminate, and Information. Ack By—User acknowledging alarm. If new alarms have come in since the alarm was acknowledged, an asterisk (*) will be displayed after the user name. Ack Time—Date and time alarm was acknowledged. Event Count—Number of identical events that have occurred. Events are considered identical if they have the same Event ID / Type, Managed Object, and Severity. EventInfo ID—Unique key describing the event; consists of the Managed Object and a time field. Event Name—Name of the event; defined in the relevant Event Template. SNMP OID—SNMP Object ID Type—Event type, or protocol; defined in the relevant Event Template. The choices are: SNMP, Other, ASCII, and TL1. SNMP SysUpTime—Amount of time, in seconds, elapsed since the object was last rebooted. SNMP Version—Version number, either SNMP v1 or v2c. Source—IP of object sending the alarm. Clear By—User clearing alarm. Clear Time—Date and time alarm was cleared. SNMP SysObjID—Identifier used for SNMP v1 traps. Event—Trap value. Icon—Graphic image Variable Binding List—Displays a list of the variable bindings for the selected alarm. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-12 Advisor—Provides a description of the alarm, such as “This device has received a protocol message that was not properly authorized. The message has been discarded.” These messages derive from the relevant trap MIB. When an alarm level vent occurs, these messages are displayed in the Advisor panel of the Event Detail. In addition, the message is set as the default for any emails sent. Notes—Provides an area for the operator to provide information concerning the selected alarm. The note is stored with the alarm. Show Managed Object...—Displays the Managed Object Manager’s General panel, with the managed object associated with the selected alarm preloaded. Geographic Topology Map...—Displays the Geographic Topology Map, centered on the managed object associated with the selected alarm. Logical Topology Map...—Opens the Logical Topology Map, which displays all icons logically representing and defining the managed object, the number of associated alarms, the physical location of the device, and the administrator. Monitor Performance...—Opens the Performance Monitor window to display the performance data, if any, for the managed object associated with the selected alarm. Telnet Cut thru—Opens a Telnet session to the device specified in the alarm. HTTP Cut thru—Opens a browser window to the URL of the device specified in the alarm. Email—Sends the selected alarm, via e-mail, to the specified recipient. The Properties file contains the name of the SMTP host through which e-mail is routed, as well as the return address included with the e-mail. Acknowledge—Acknowledges the selected alarm. The current date and time are displayed in the Ack Time field, and the name of the current signed-on user is displayed in the Ack By field. Unacknowledge—Once an alarm has been acknowledged, the Unac- 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-13 knowledge menu option is displayed in place of the Acknowledge option. Selecting this option removes the acknowledgement from the alarm, clearing the entries in the Ack By and Ack Time fields. Clear—Clears the selected alarm only. The name of the currently signed on user is recorded, as well as the date and time. If the alarm has not been acknowledged, it is automatically acknowledged before being cleared. Clear All Alarms—Clears all alarms. The name of the currently signed on user is recorded, as well as the date and time. If any alarms have not been acknowledged, they are automatically acknowledged before being cleared. Disconnecting and Reconnecting the Alarm Window The Network Connection button at the top right-hand side of the Alarm window lets you disconnect and reconnect StormTracker EMS from the mediation agent. As the graphic to the left shows, the Network Connection button indicates the current state of connection. StormTracker EMS continues to process alarms while it is disconnected from the mediation agent, but they are no longer displayed. Once StormTracker EMS is reconnected, all alarms that occurred during disconnection are displayed. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 22-14 23 Chapter/Alarm Rules Overview The Rules Manager provides a graphic interface to simplify the creation of complex rules. Select Rules Manager from the Control menu to display the initial dialog. Figure 23-1. StormTracker EMS Rule Manager Rules Manager The initial Rule Manager dialog lists all the rules the current user has created. The list can be filtered by the selections in the drop-down menu above the display. The buttons on the right allow you to create, edit, delete, and register graphical rules as well as schedule their execution. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-1 23 Chapter/Alarm Rules Elastic Networks Creating or Editing a Rule The New or Edit button invokes the graphical rule editor. All rules that are created with the StormTracker EMS graphical rule editor reside in the RedCell.UserRules package, and receive a parameter of RedCell.Assurance.Generic-FaultRuleParamSet. All XRLs are taken from the RedCell.XRL package. Figure 23-2. StormTracker EMS Rule Editor 23-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 23 Chapter/Alarm Rules Rule Editor Controls The Rule Information area, at the top of the Rule Editor, displays the name of your rule. If you are creating a new rule, type a unique name for it in this field. Three buttons and a check box appear at the top right side of the Rule Editor; these action buttons and check box let you perform actions in the work area. Selection—lets you select rule objects in the work area. Delete—lets you delete a rule object or connection. When you delete a rule object or connection an alert box appears asking you to confirm deletion. Delete Rule—deletes all rule objects and connections in the work panel except for the begin and end rule objects. Compile—compiles the rule when you render it. If you deselect this check box, Oware will save the rule but not compile the code. Rule Objects Rule objects reside in two tabbed panels: Logical and XRL. You can place objects in the work area by selecting them from the appropriate objects panel. Once objects have been placed in the work area, they can be dragged to any location within the work area. The Begin and End Objects When you open the Rule Editor, two rule objects appear by default in the work area: The begin object (a green traffic light) and the end object (a red traffic light). These rule objects signify the beginning and end of the rule. The begin rule object contains an output connector at the bottom that signifies that rule object’s ability to plug into another rule object. The end rule object contains an input connector (with a down arrow on it) at the top of the rule object that signifies that object’s ability to receive a connecting rule object. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-3 Logical Objects The Logical panel, which appears by default, contains the different rule objects you can add. Figure 23-3. Logical panel Select a rule object by clicking on the corresponding button. A blue selection box representing the object appears in the work area. Place the rule object by clicking the mouse button. Assignment Object—Assigns the value of one variable to another. Decision Object—Creates an if/then statement for selecting one of two branch destinations depending on the value of an expression. Loop Object—Creates a loop that repeats . End Object—Signifies the end of the rule. Switch Object—Creates a case statement for selecting a branch destination depending on the value of an expression. Variable Increment Object—Increments the value of a variable by a specified number. Variable Decrement Object—Decrements the value of a variable by a specified number. Method Call Object—Calls a method. Method Call Assignment Object—Assigns the value returned by a method call to a variable. Boolean Expression Object—Assigns a true or false value to a variable. Mathematical Expression Object—Assigns value returned by a mathematical expression to a variable. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-4 XRL Panel The XRL panel lets you add Extensible Rule Language (XRL) code into your graphical rule. Figure 23-4. XRL panel Select the package in which the XRL resides from the drop-down list and a category from the bottom. All XRLs in the specified package and category are displayed. Deleting a Rule Object You can delete one or more rule objects by selecting them and using one of three delete methods: • Press the Delete key. • Click the Delete button. • Right-click on the rule object and select Delete selected item(s) from the popup menu. When you delete a rule object an alert box appears confirming that you want to delete the rule object. Delete the rule object by clicking on Yes, or click the No or Cancel buttons to abandon the deletion. If you click Yes, Oware deletes the rule object and all connections to and from it. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-5 Caution: You cannot undo the delete action once you click Yes. Connecting Rule Objects Once you place your rule objects you can connect them using the object connectors. NOTE: In most cases, you can only have one object connected to each output connector. If you try to connect a second object to a connector that does not allow it, an alert box will appear stating that the Graphics Composer could not complete the connection. In some cases, an input connector can have more than one connection, for example, different branches from an if/or switch. You can connect objects by moving the mouse pointer to an object’s output connector, holding the mouse button, and dragging the mouse across the work area. A blue line appears that connects to the output connector. When you move the line to an input connector, the line turns red when the line connects. Complete the connection by releasing the mouse button; the connected components have thick gray lines between their connectors. NOTE: If the line does not turn red and you release the mouse button, the line closes and the connection is not created. If you move one of the objects, the connectors move with the object. You can select the connector by clicking on it. Deleting Rule Object Connections You can delete a selected connector line with any of the following delete methods: • Press the Delete key. • Click the Delete button. • Right-click the connector line and select Delete selected item(s) from the popup menu. After you select the deletion method the connector line disappears. This action cannot be reversed. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-6 Object Properties Panel You can view rule object properties in the Properties panel, which appears by default. Figure 23-5. Object Properties panel You can view a specific rule object’s properties by selecting the rule object in the work panel or selecting it from the Object Properties dropdown list. Name—The rule object name. Comment—Text that describes what the rule object does. Oware writes this text into the text version of the rule. When you click on the command button to the right of the Comment text field, the Comment window opens. Type any comments and click on OK to save the text and close the window. Click on Cancel to close without saving. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-7 Figure 23-6. Comment window Apply—Applies the properties to the selected rule object. For example, if you add the name End to a rule object, the rule refers to that object as End. NOTE: If you render your graphical rule before applying property changes, an alert box appears that asks if you want to apply the property changes before rendering. Cancel—Returns the edited property to its previous state without saving the edits. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-8 Object Variables Panel The Variables panel contains a table of object attributes. Figure 23-7. Object Variables panel The Variables table contains the object attribute name, type, and value. The most recently entered attribute appears at the top of the table. You cannot make any changes to this table. Two buttons appear at the bottom of the Variables panel. New—Adds a new variable. When you click this button the New Variable dialog box appears. Figure 23-8. New Variable dialog 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-9 Create a new variable by entering a variable name in the Name text box and selecting the variable type in the Type drop-down list. Save the variable in the attributes table by clicking OK. If you decide against creating a new variable, click Cancel. Delete—Deletes the selected variable from the table. NOTE: When you delete a variable, Oware does not confirm the | deletion. Rendering Your Alarm Rule Render your rule by clicking on Render. After a few seconds, the Rule Saved alert box appears. Registration Rules must be registered before they can be attached to events. Click on Registration to display the Rule Registration dialog. The rule can be run for all events or one or more specific events, and can be run either before or after the event is processed. The registration process is as follows: 1. Specify the scope of processing by selecting either of two options: For All Events or For Specific Events. 2. If you specify For All Events, the rule will be run whenever an Event occurs. You must then select one of two options: Prior to processing—runs the rule before the event is processed. After processing—runs the rule after the event is processed. 3. If you specify For Specific Events, you must specify the events for which this rule will be run as well as the processing options. To add an event, click on the Add button. The following dialog—labeled Editing Event Rule or New Event Rule—appears. Specify the event to be associated with this rule by clicking on the Command (...) button and selecting an event from the resulting list. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-10 Select an event from the list and click on OK to implement your choice. Each event associated with a rule can have its own processing criteria with respect to that rule. Select one of the following Run Rule options: Prior to processing—The rule is run before the event is processed. After processing—The rule is run after the event is processed. When you have made all of your specifications, click on OK to implement your choices and return to the Registration dialog.Repeat this sequence for each event you want to associate with this rule. When you are finished, click OK. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 23-11 24 Chapter/SNMP MIB Event Parser Overview The SNMP MIB Event Parser is designed to parse SNMP v1 and v2 MIBs. All traps and notifications listed within the loaded Elastic MIB are automatically converted into Event Templates. To launch the SNMP MIB Event Parser, select MIB Event Parser from the Device menu. Figure 24-1. SNMP MIB Event Parser 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 24-1 24 Chapter/SNMP MIB Event Parser Elastic Networks Selecting a MIB File Navigate to the location of the MIB file you want to parse and select it (or type the path and filename directly in the File name field) and click Import. After the MIB Loader has successfully parsed the trap data from the text, the system displays a message confirming the transfer. NOTE: Note: If you type the name of the MIB file and the file name contains spaces, you must surround the entire specification (path information and file name) with quotes. Figure 24-2. MIB Event Parser Confirmation Dialog Elastic MIB File The Elastic MIB supports the following traps: _enEloopCOModemIfClearStatsEvent _enEloopCOModemIfDownEvent _enEloopCOModemIfUpEvent _enEloopCPEModemClearStatsEvent _enEloopCPEModemEnetDownEvent _enEloopCPEModemEnetUpEvent _enEloopCPEModemResetEvent _enEloopShelfStatusChange 24-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 08-00032-01, Rev. 2.1 24 Chapter/SNMP MIB Event Parser StormTracker EMS User Guide 24-3 25 Chapter/Performance Monitor Overview The StormTracker EMS Performance Monitor, shown below, provides real-time monitoring of selected Managed Objects via SNMP MIB-II. Figure 25-1. Performance Monitor 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 25-1 25 Chapter/Performance Monitor Elastic Networks You can access the monitor by selecting Performance Monitor from the Assurance menu; through the Managed Object Manager, by selecting Performance; and from the Alarm Window, by selecting Monitor Performance from a highlighted event. The polling rate for the device can also be changed; the default is 15 seconds. Selecting a Managed Object to Monitor Type the name of the device to be monitored in the Managed Object field at the top of the Performance Monitor or click on the command button (...) to display a Browser from which one can be located. If the device you have chosen has not had its performance information defined, an error message—There is no performance data defined for this class of equipment—will appear. The following data is monitored: System Up Time—Displayed in days, hours, minutes, seconds. System Name—User defined. IP Packets Received—In packets. IP Reception Errors—Displayed as a bar graph. IP Packets Transmitted—In packets. IP Transmission Errors—Displayed as a bar graph. IP Forwarding Rate—Displayed as a bar graph. ICMP Packets Received—In messages. ICMP Reception Errors—Displayed as a bar graph. ICMP Packets Transmitted—In messages. ICMP Transmission Errors—Displayed as a bar graph. UDP Packets Received—In datagrams. UDP Reception Errors—Displayed as a bar graph. Interface Name—Must be specified through the Options dialog box. Bytes Received—Interface must be selected; displays in packets. Reception Errors—Interface must be selected; displayed as a bar graph. Bytes Transmitted—Interface must be selected. 25-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 25 Chapter/Performance Monitor Transmission Errors—Interface must be selected; displayed as a bar graph. Bandwidth Utilization—Interface must be selected; displayed as a bar graph. Additional Information In some cases, more information is available than is displayed. Those fields for which this is true contain an information button. Click on this button to display a dialog with the additional information. Performance Monitor Options The Performance Monitor Options dialog has two modes of display. If a Monitored Object has been specified and is being monitored, the Performance Monitor appears with two tabs: General and SNMP MIB-II. If no device is being monitored, only the General settings are available. General Tab The settings on the General tab control general monitor functions. Figure 25-2. Performance Monitor Options: General Tab 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 25-3 The fields in the General tab are as follows: Refresh Rate— This is the rate at which the monitor refreshes. Number of Columns—This setting specifies the number of data columns in the monitor; the default is 1. Remember Last Managed Object?—Select this option to specify that the Performance Monitor loads the last Managed Object, if any, when it is launched. SNMP MIB-II Tab The fields in the SNMP MIB-II tab control functions specific to the SNMP MIB-II interface. Interface to Monitor—This option, selected from a drop-down menu, determines which available SNMP MIB-II interface on the selected Managed Object is monitored. Monitor relative change only?—This option, when selected, specifies that changes in monitored values are tracked between readings. Otherwise, changes are tracked from the initial reading. Pausing the Performance Monitor From the Performance Monitor screen, select Pause to pause the Performance Monitor. The monitor will temporarily stop polling for information. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 25-4 Manually Refreshing the Performance Monitor From the Performance Monitor screen, select Refresh to manually refresh the Performance Monitor. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 25-5 26 Chapter/StormTracker EMS Reports Overview The Report Manager can generate reports regarding all data managed by StormTracker EMS, including incoming events, existing customers, contacts, and managed objects. Once reports have been created, they can be saved for later reference and shared among all users or members of a particular group. In addition, the Report Manager allows you to export reports to a text file, create colorful graphs and charts, and print the results. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-1 26 Chapter/StormTracker EMS Reports Elastic Networks To create a report, select Reports from the Assurance menu; the Report Manager appears. Figure 26-1. Report Manager window Designing Reports The Report Manager is split into several tabs, each allowing specialization of one aspect of the report. To use an item on a given tab, check the box next to the item (Severity, Event Type, Ack By, and so on), type the desired value in the box, and check the Use This Page box at the bottom of the tab. To design a report with multiple items, check the box next to the first item, select a logical operator, and check the box next to the next item desired. Items on multiple tabs can be utilized in a single report; merely check the Use This Page box at the bottom of each tab containing an item being used. 26-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 26 Chapter/StormTracker EMS Reports Logical Operators Selectable items have two radio buttons associated with them: AND and OR. These logical operators determine which items appear in a report. AND—Select this radio button to specify that this item must be present in order to generate a report entry. For example, if you specify AND for both the Event Type and Cleared By items, a report entry will be generated only if an event of the type specified has occurred and has been cleared by the specified user. OR—Select this radio button to specify that only one of the specified items must be present in order to generate an entry. For example, if you specify OR for the Event Type, Cleared By, and Ack By items, a report entry will be generated for an event of the specified type, or an event cleared by the indicated user, or an event acknowledged by the indicated user. Wildcard characters are also supported in Report Manager; if you would like to select all elements of a designated item, type an asterisk (*). Using the wildcard, a report can return multiple responses from a single command—for example, if the user enters a* in the Ack By field of the Events tab, all events with acknowledging users beginning with ‘a’ would be selected. Note, however, that the searches are case sensitive; users beginning with ‘A’ would not be selected with the query. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-3 Report Manager—Events The Events tab lets you use field values and boolean logic to specify the information that appears in a report. Figure 26-2. Report Manager Events tab The fields in the Report Manager Event Tab are as follows: Severity—The severity of event. Event Type—Event type, or protocol; defined in the Event Template Manager. Ack By—User who acknowledged the alarm in the Alarm Window. Cleared By—User who cleared the alarm in the Alarm Window. Occurrence Date—Date the event occurred; selected with the Date Range button. Use This Page—Design a report using data on this page. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-4 Report Manager—Devices Using the Devices tab, the user can design a report on defined Managed Objects, and, in conjunction with the Events tab, on correlated devices and events. Figure 26-3. Report Manager Devices panel. Device ID—The unique name of the managed object, as defined in the Managed Object Manager. IP Address—The IP address of the device, as defined in the Managed Object Manager. Device Type—Type of managed object, as defined in the Managed Object Manager. Possible entries include ATM, Bridge, Cable Modem, Card, DCS, Discovered Entities, Frame Relay, Interface, Mux, Port, Router, Server, SONETMux, Switch, and Workstation. Device Location—Location of device, as defined in the Managed Object Manager. Locations must be defined in order to be valid entries. Use This Page—Use the data on this page when generating a report. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-5 Report Manager—Customers The Customers tab allows reporting on various aspects of customers, including name, account number, and customer contact phone numbers. Figure 26-4. Report Manager Customer panel. Customer Name—ID of the Customer firm; defined in the Customer Manager. Acct Number—Internal account number of the customer; defined in the Customer Manager. Phone Number—Phone numbers for the Customer Contact; defined in the Contact Manager. Use This Page—Design a report using data on this page. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-6 Report Manager—Options The Options tab allows reports to be assigned to a particular set of users. Figure 26-5. Options Tab The radio buttons in this tab let you specify who can view the report: Public—Makes reports available to all network users based on defined customers. Group Owned—Makes reports available to users in a specific group. Owned—Makes report available only to the owner, typically the report’s creator. Creating a New Report Click New and type in the name of the new report, then design the report and click Save when finished. The newly designed report will be saved to the database. Once saved, the report can be retrieved from the Report drop-down list at the top of the Report Manager. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-7 Running a Report Design a new report, or select an existing report from the Report dropdown list at the top of the Report Manager, and click Run to generate the report. For more information on report design, refer to the Designing Reports section. Loading or Altering an Existing Report Select the previously saved report from the Report drop-down list at the top of the Report Manager. Make changes as desired and click Save, if necessary. Once loaded, the report values will automatically be populated in the various tabs. The loaded report can be modified and saved if any changes have been made. Deleting an Existing Report Select an existing report from the Report drop-down list at the top of the Report Manager, and click Delete. The specified report will be deleted; a dialog will prompt you before deletion. Exporting a Report Design a new report, or select an existing report from the Report dropdown list at the top of the Report Manager, and click Export. At the Export Report prompt, type the report filename and browse to the desired export location. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-8 Figure 26-6. Export File Window. The report is exported to the specified location using the supplied filename. Reports are exported using the settings entered in the Preferences dialog box, including field and string delimiters. Changing the Report Display Once a report has been run, the display of the results can be altered by moving, sorting, re-sizing, or deleting selected columns. After modifying the display, the report can then be saved. When the report is reloaded and executed, the altered display will be loaded. Deleting a Column from a Report From an existing report, highlight a cell in the column you wish deleted. Right click and select Delete Column. The column will be deleted from the report. In case of an error, StormTracker EMS will remember the column that has been deleted, and it can be re-added to the display. Adding a Deleted Column to a Report From an existing report with a deleted column(s), highlight a cell in the report, right click, and select Add Column. Select the columns to restore from the displayed list. The column will be added before the column of the highlighted cell. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-9 Moving Columns Click on the column heading of the column you need to move and drag it to its new position. Resizing Columns Drag the border of a column to the right or left to resize it. Note, however, that resizing a column is not permanent. The columns will revert to their default sizes when the report is reloaded. Sorting by Column Value Double-click on the column heading of the column you want to sort. The report will be sorted according to the contents of that column. Printing Reports After designing and running your report, StormTracker EMS lets you print the information. In addition, the printout may be fully customized—from page orientation and size, to report specific headers and footers. Headers and footers are modified within the Preferences dialog box; all other aspects of page formatting are handled in the Page Setup section of the Print menu. For more information on the Preferences dialog box, refer to the Report Preferences section. Printing a Report From a report, click on Print... and select Print from the resulting menu. The report is printed, using the settings set in Page Setup and Report. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-10 Page Setup From a report, click on Print... and select Page Setup from the resulting menu. This displays an operating system-specific Page Setup dialog through which you can set margins and specify a printer, as well as set paper size, source, and orientation. Figure 26-7. Microsoft Windows 2000 Page Setup. Print Preview From a report, click on Print... and select Print Preview from the resulting menu. StormTracker EMS’s Print Preview lets the user see precisely how a report will look before printing, including margins and headers and footers. From the Print Preview window, the user can zoom in to examine the report in greater detail. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-11 Creating Charts After a report has been designed and run, you can create bar and pie charts from the results. Pie and simple bar charts can be created on a specified column within the report, and once created can be printed. In addition to these options, a complex bar chart can be created that plots the specified column against another column within the report. Additional chart preferences, including 3-D effects and data labeling, can be found in the Report Preferences dialog. Creating a Pie Chart From an existing report, highlight a cell in the report, right click, and select Create Pie Chart. A chart is automatically generated from the values in the given column. If you wish to print the chart, click on Print from the chart dialog box. To display additional information about the chart, including the percentage and title of each piece (data labels), move the mouse pointer over the specific chart area. Creating a Simple Bar Chart From an existing report, highlight a cell in the report, right click, and select Create Bar Chart. A chart will be automatically generated from the values in the given column. If you wish to print the chart, click on Print from the chart dialog box. To display additional information about the chart, including the percentage and title of each bar (data labels), move the mouse pointer over the specific chart area. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-12 Creating a Complex Bar Chart From an existing report, right-click on a cell and select Create Complex Bar Chart from the resulting menu. This will display a dialog box that lets you select the column to be used for the Y-axis (the highlighted column is used for the X-axis). Select the desired column and click OK. A chart is automatically generated from the values in the given columns. If you wish to print the chart, click on Print from thechart dialog box. By default, data labels (the values of given bars) are displayed; this can be changed in the Preferences dialog box. Report Preferences The Report Preferences dialog lets you specify preferences for different actions available within the Report Manager. Changes to the way StormTracker EMS formats text for export, creates charts, and prints reports can be made through this dialog box. Figure 26-8. Report Preferences Window. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-13 Export Tab This tab lets you set the delimiters used by Report text files. Delimiters separate values from one another; the default values are tab (field) and double quotes (string). The options are as follows: Field Delimiter—Used to delimit fields within exported files; select from the following radio buttons: Tab (default) Comma Semicolon Space Other (user defined) StormTracker EMS Reports String Delimiter—Used to delimit strings within exported files; select one delimiter from the following radio buttons: Double Quotes (default) Single Quotes No string delimiter Chart Tab This tab lets you specify the effects used to create charts. The options are as follows: 3D Effect—Selected by default; if unselected, the chart is 2-D. Data Labels—Data labels appear in pie and simple bar charts upon moving the mouse pointer over the chart, and consist of the name and percentage of the graph. In complex bar charts, the data labels are always visible and are the values of each bar. By default, this option is selected. Printing Tab The Printing tab lets you set headers and footers for printed reports. Note that the footer of a printed report always displays Page x of y in the left margin and the time and date in the right margin; any additional footer added here is displayed above the default footer. Both headers 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-14 and footers may be located in the left margin, right margin, or center of the page. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 26-15 27 Chapter/StormTracker EMS Reports Overview RMON (Remote Monitor) is a system of SNMP-based MIBs used to manage networks remotely. Two RMON groups are supported by StormTracker EMS: Events and Alarms. RMON is used to monitor data points on devices by detecting whether the values have risen or fallen below a specified value. The values are measured as either a delta, signifying a change since the last reading, or as an absolute, signifying a change since the initial reading. The set of values required to generate an alarm for a specified data point is defined as an RMON Alarm; the action(s) to take once the alarm has been generated is the associated Event, which is similar to a standard StormTracker EMS Event. The actions available are: generate a log, emit an SNMP trap, create both a log and a trap, and do nothing. Using the StormTracker EMS RMON interface, you can monitor a device, as well as create, alter, and delete entries in both the Event and Alarm tables. These modifications can then be propagated to the network devices and the configurations written to the database. Preliminary Setup Before you can utilize RMON, you must do the following: 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 27-1 27 Chapter/StormTracker EMS Reports Elastic Networks 1. Add the following line to the settings.txt file: equipmentClass = RedCell.rmon.device 2. Implement the change by running init to reseed StormTracker EMS’s database: init busdb 3. Move the device or devices to be monitored from the Discovered Entities class to the RMON device class. (After the database is reinitialized, the RMON device class is displayed as “device” in the drop-down list of classes.) 27-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 27 Chapter/StormTracker EMS Reports Using RMON To access the RMON system, select RMON from the Assurance menu. The RMON Manager, shown in the next illustration, appears. Next, select a Managed Object (RMON Agent) to monitor. You may either type the name of the device directly in the RMON Agent field, or click on the command button to locate the associated Managed Objects. Figure 27-1. RMON Manager 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 27-3 The RMON Manager The RMON Manager is context sensitive; the display changes to fit the function of the selected RMON Group. There are also certain global controls which affect overall operations. Alarms Select Alarm from the RMON Groups panel to display the controls associated with RMON Alarms. These controls are as follows: Index—The alarm index; automatically set by the system. Interval—Number of seconds between polling. Variable—The OID to monitor. Sample Type—Monitor based on delta or total change; displayed as a drop-down box. Available types are: Absolute value, Delta value. Startup Alarm—The type of behavior to monitor; displayed as a dropdown box. Available options are: Rising alarm, Falling alarm, Rising or falling alarm. Rising Threshold—The threshold level at which to generate a rising alarm. Falling Threshold—The threshold level at which to generate a falling alarm. Rising Event Index—The associated event for a rising alarm. Falling Event Index—The associated event for a falling alarm. Owner—The RMON Owner; set automatically. Can be changed within StormTracker EMS’s System Settings. Events Select Event from the RMON Groups panel to display the controls associated with RMON Events. These controls are as follows: Managed Object—The device to monitor; set automatically. Index—The event index; automatically set by the system. Description—The event description. Type—The action to take upon alarm: generate a log, emit an SNMP trap, create both a log and a trap, or do nothing. Displayed as a dropdown box. Available action types are: none, log, SNMP trap, log and trap. Community—SNMP community. Valid entries are: public, private. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 27-4 Owner—The RMON Owner; set automatically. Can be changed within StormTracker EMS System Settings. Adding an RMON Alarm Select Alarm from the New... drop-down menu to display the Add RMON Alarm dialog. Set the values as desired in the primary dialog box, then select Event Template to create the settings for the associated StormTracker EMS Event. The specified variable will already be populated into the Event Identifier field of the new event. Once created, the event will be added to the Event Template Manager as an RMON Notification event. Adding an RMON Event Select Event from the New... drop-down menu to display the Add RMON Event dialog. Set the values as desired in the primary dialog box. RMON Notification Event Templates Select Event Templates from the Show... drop-down menu to display all defined RMON Notification Events. The resulting dialog lets you add additional events, or modify or delete existing events. Displaying Real-Time RMON Data Select Live Data from the Show... drop-down menu to display all RMON data—Events, Alarms, or Logs—for the specified device. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 27-5 28 Chapter/Importing and Exporting Overview StormTracker EMS gives you the ability to export certain kinds of data as text files, and to import them. The Export facility gives you the means to create new “seed” files for downstream installations, to back up your data, or to create data files for use by StormTracker EMS clients running on other servers. (All clients running on the same server share seed files.) The process of importing is the same, regardless of the entity being imported, and the process of exporting is the same, regardless of the entity being exported. Therefore, this section discusses importing and exporting in a generic sense. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 28-1 28 Chapter/Importing and Exporting Elastic Networks Importing Files The Import utility is available from all StormTracker EMS Manager utilities, and the procedure for importing text files is the same throughout. From the appropriate manager, select Import (or press Alt-I), browse to the location of the file, select the file, and click Import. Figure 28-1. Import File dialog 28-2 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks 28 Chapter/Importing and Exporting Exporting Files The Export utility is available from all StormTracker EMS Manager utilities. To export a file, select that file (from within the appropriate manager) and click on the Export button (or press Alt-X). An Export File dialog, similar to the one in the next illustration, appears. Browse to the desired destination directory and click on the Open button; a new export file is created. Figure 28-2. Export File dialog Exported files can be used as seed files, letting you modify StormTracker EMS for further “downstream” installations, and can also be imported by client applications running on other servers. The export function also provides you with a convenient backup mechanism. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide 28-3 Glossary Agent Mapper: The Mediation Agent handles SNMP requests, SNMP traps, and ASCII grammars through the Agent Mapper. You must configure the Agent Mapper with each location of a Mediation Agent. Alarm; A signal alerting the user to an error or fault. Alarms are produced by events. Alarms produce a message within the Alarm Window. API: Application Programing Interface—A set of routines used by the application to direct the performance of procedures by the computer’s operating system. Applet: A small Java program that runs on a client. Often downloaded onto the client to customize the or add interactivity to the client. Application Server: A container for component frameworks—for example, Enterprise JavaBeans—that includes fundamental services for access and intra-system communication. Both StormTracker and Oware run in the Application Server. ASCII: American Standard Code for Information Interchange protocol. ATM: Asynchronous Transfer Mode. ATM is a high bandwidth, lowdelay, connection-oriented, packet-like switching and multiplexing technique. Blade: See Solution Blade. BOM: Business Object Manager; responsible for managing all defined objects. Includes object database. Handles all scheduling, notification, caching and modification services for objects. Business Class: A category of objects. A business class contains a name that defines the class, properties, and attributes that define the individual data within the business class. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide G-A Glossary Elastic Networks For example, you can have a business class named Employee that has a persisted property and a Name attribute. Note: A business class is not the same as a Java class. Business class is concept that is unique to Oware. Business Object: One specific instance in a class. For example, the Employee business class would include the John Smith object. Center: One of three integrated Oware parts; each part has its own function within Oware. The three centers are: • Oware Creation Center (OCC)—for creating and rendering solution blades • Oware Execution Center(OEC)—for powering solution blades • Oware Management Center (OMC)—for deploying and managing solution blades Class: See Business Class. CORBA: Common Object Request Broker Architecture—An architecture that enables pieces of programs, called objects, to communicate with one another regardless of what programming language they were written in or what operating system they're running on. CoS: Class of Service—Describes the level of service provided to a user. Also provides a way of managing traffic in a network by grouping similar types of traffic. Creation Center, (OCC) This is the center where you create and render solution blades. Database: An organized collection of Oware objects. Deployment: The distribution of solution blades throughout the domain. Domain: A goal-oriented environment that can include an industry, company, or department. You can use Oware to create solutions within your particular domain. EJB: Enterprise JavaBean—An application designed to extend the JavaBean component model to a cross-platform, server-side application. G-B StormTracker EMS User Guide 08-00032-01, Rev. 2.1 Elastic Networks Glossary Element: A type of data that defines and organizes Oware data for easy references. There are six types of elements: business class, event, form, grammar, graphic, and rule. Event: Notification received from the NMS (Network Management System). Notifications may originate from the traps of network devices or may indicate an occurrence such as the closing of a form. Events have the potential of becoming alarms. Event Definition: Parameters that define what an event does. For example, you can tell Oware that the event should be to wait for incoming data from a remote database, then have the Oware application perform a certain action after it receives the data. Event Instance: A notification sent between two Oware components. An event instance is the action the event performs per the event definition. Event Template: Defines how an event is going to be handled. Event Threshold: Number of events within a given time frame that must occur before an alarm is raised. Execution Center (OEC): This center that renders solutions by executing solution blades. It does this by completing the application. It loads classes into the classes database, it and reads and creates objects in the database. Exporting: Saving business objects, packages, or solution blades to a file for others to import. FCAPS: Fault Configuration Accounting Performance Security Form: An interface that lets users interact with a solution blade. Users can use forms to enter data, view data and/or events, and trigger rules and/or events in a solution blade. Grammar: Translates ASCII text communications between the solution blade and the external systems via patterns built into the OCC 08-00032-01, Rev. 2.1 StormTracker EMS User Guide G-C Grammar Composer. GUI: Graphical User Interface IDE: Integrated Development Environment. A programing environment integrated into an application. IIOP: Internet Inter-ORB Protocol. A protocol used to implement CORBA solutions over the World Wide Web Importing: Loading business objects, packages, or solution blades into the OCC for you to edit. Managed Object: A network device managed by the system. Management Center, Oware (OMC): This Oware center deploys and manages solution blades. Mbeans: Management Beans. The objects specify the protocol of the device with which they are communicating. Mediation: Communication between Oware and external systems or devices, for example, telephone switches, security systems, or remote database. Mediation services let Oware treat external systems and/or devices as objects. Mediation Agent: Any communication to and from managed objects is handled by the Mediation Agent. This communication includes SNMP requests, ASCII requests, and unsolicited ASCII messages. In addition, the Mediation Agent receives and translates emitted SNMP traps and converts them into events. Metadata: Attributes that describe Oware database objects; data about data (for example, title, size, author, or subject). Metadatabase: An organized collection of Oware attributes (also called meta-data). For example, the attribute ZIP Code in the metadatabase can describe all database business objects with five digits (for 08-00032-01, Rev. 2.1 StormTracker EMS User Guide G-D example, 94101). MIB: Management Information Base. A database (repository) of managed objects containing object characteristics and parameters that can be monitored by the network management system. Multi-Threading: Concurrent processing of more than one message by the application. OCC: Oware Creation Center (see Creation Center) OEC: Oware Execution Center (see Execution Center). OID: Object ID. OMC: Oware Management Center (see Management Center). Oware: Oware is an Internet infrastructure software product that delivers advanced user, content and network aware Internet Commerce Systems. Oware allows users to quickly render Internet Commerce Systems that have inherent knowledge of user profiles, content, and network resources, enabling a class-of-service based Internet. Package: The container for Oware elements. Persistent Data: Data stored in the database for future use. (As opposed to transient data). Policy: Establishing priorities for the network based on parameters such as traffic type, applications, or users. Policy routing: Routing scheme that forwards packets to specific interfaces based on user-configured policies. Such policies might specify that traffic sent from a particular network should be routed through interface, while all other traffic should be routed through another interface. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide G-E QoS: Quality of Service. In digital circuits, it is a measure of specific error conditions as compared with a standard. The establishment of QoS levels means that transmission rates, error rates, and other characteristics can be measured, improved, and, to some extent, guaranteed in advance. Often related to Class of Service (CoS). Rendering/Render: The process of generating OMG metadata, compiling and saving application components within the context of Oware. Also called solution rendering. RMI: Remote Method Invocation—A set of protocols (Sun’s JavaSoft) that enables Java objects to communicate remotely with other Java objects. It works only with Java objects. RMON: Remote MONitoring; a monitoring set of SNMP-based MIBS used to manage networks remotely. Nine diagnostic groups are defined. Of these, StormTracker EMS supports Events and Alarms. Rule: Defines what a solution blade does in a particular situation, for example, how the solution blade responds to an event. An event, another rule, or program code can trigger a rule. Servlet: A small Java program that runs on a server, noted for quickness. (also see applet). SMTP: Simple Mail Transfer Protocol. SNMP: Simple Network Management Protocol. Network management protocol used almost exclusively in TCP/IP networks. SNMP provides the means to monitor and control network devices, and to manage configurations, statistics collection, performance, and security. Solution Blade: The properties specified in the OCC that describe the application to be rendered. Also called a meta application or a blade. Solution Rendering: The integration of all Oware elements and components into an executable application and a set of instructions (metadata) for creating the application. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide G-F Transient Data: Temporary data that exists only while being used by a solution blade. Trap (SNMP Trap): A notification from a network element or device of its status, such as a server startup. This notification is sent by an SNMP agent to a Network Management System (NMS) where it is translated into an event by the Mediation Agent. Trap Forwarding: The process of re-emitting trap events as traps to another management system such as the NMS (Network Management System). Virtual Rule Machine (VRM): A rule engine encapsulated by a ubiquitous meta schema that manages logic, processes requests, and associates behaviors required by a solution blade. Also called VRM. Virtual Solution Machine (VSM): A complete, integrated set of technologies that let you create, execute, and manage Internet commerce business systems. All of the components, services and technology in a single product, already integrated and ready to use. Also called VSM. XRL: Extensible Rule Language. A high-level language that contains the building blocks of rule types and commands. 08-00032-01, Rev. 2.1 StormTracker EMS User Guide G-G i A Agent Mapper 2-1, 2-4 Alarm Rules 23-1 Registration 23-10 Alarm Severities 6-9, 22-2 Alarm Window Columns 22-5 Alarm Window Filters 22-6 Alarm Window Views 22-3 Alarms 22-1 Filter Creating or Editing 22-7 Dates 22-7 Event Props 22-9 Rules Creating or Editing 23-2 Objects 23-3 Rules Manager 23-1 Severities 22-2 Application Manager 13-6 Application Server 2-1, 2-2 Applications Creating and Editing 13-6 Assurance Menu 4-2 C Charts Creating 26-12 Client Email Settings 6-9 Client Installation 1-12 Config Menu 4-3 Contact Manager 13-10 Contacts Importing and Exporting 13-12 Control Menu 4-4 Cut-thru HTML 19-1 Loading an HTML Document 19-1 Telnet 19-2 Cut-thrus 19-1 D Creating 16-2 Editing Parameters 16-5 Executing 16-5 Data Collection Scheduler 16-1 Device Firmware 11-1 Device Menu 4-4 Device Resynchronization Creating a Schedule 17-2 Device Resynchronization Scheduler 17-1 Discovery 7-1 Discovery Event Creating 7-6 Editing Parameters 7-7 Schedule 7-8 Discovery Process 7-3 Discovery Wizard 7-2 Downloader 11-2 E Event Template Adding 21-9 Delete 21-9 Editing 21-2 Importing and Exporting 21-9 Organization 21-2 Export Functions 5-10 Exporting Files 28-3 F Firmware 11-1 I Import Functions 5-10 Importing and Exporting 28-1 Importing Files 28-2 Installation Windows 2000 1-17 Windows 2000 Client 1-18 Windows 2000 Server 1-17 Installing Oware 1-2 Data Collection Query StormTracker EMS User Guide 08-00032-01, Rev. 2.1 ii L Launch Console 4-1 Layouts 20-6 Link Manager 15-1 Link type 15-2 Logging Off 3-2 Logging On 3-1 M Managed Beans 2-3 Managed Object Manager 8-1 Managing Events 21-1 MBeans 2-3 Mediation Agent 2-1, 2-2 Mediation Agents Configure 2-4 MIB 24-1 Elastic MIB 24-2 MIB Browser 18-3 MIBs 6-3 MOM 8-1 O Order Creating or Editing 13-8 Order Manager 13-8 Oware Installation 1-2 P Passwords 5-1 Performance Monitor 25-1 Select Managed Object 25-2 Permissions 5-8 R Remote Monitor 27-1 Report Manager 26-1 Reports 26-1 Deleting 26-8 Designing 26-2 Exporting 26-8 Loading or Altering 26-8 Preferences 26-13 Printing 26-10 Running 26-8 RMON 27-1 Alarms 27-4 S Service Management 13-1 Service Menu 4-2 SLA Template Manager 13-7 SNMP MIB Browser 18-3 SNMP MIB Event Parser 24-1 SNMP Trap Viewer 18-1 Columns 18-2 Controls 18-3 Solaris Installing as Non-Root 1-8 Installing as Root 1-2 Solaris Installation 1-2 StormTracker EMS Applications 2-1 Subscriber Manager 13-9 Subscription Editor 13-10 sysObjectID 12-2 System Settings 6-1 T Telnet Open a Session 19-2 Telnet Cut-thru 19-2 Topology 6-11, 20-1 Geographical 20-1 Layouts Spring 20-7 Tree 20-9 Logical 20-5 Physical 20-12 Topology Items Adding or Modifying 6-7 Trap 18-3 U User Group Adding 5-6 StormTracker EMS User Guide 08-00032-01, Rev. 2.1 iii Deleting 5-7 Importing and Exporting 5-7 User Management 5-1 User Manager 5-2 User Options 6-11 Users Filter 5-3 V Vendor Manager 13-13 Vendors Adding or Editing 13-14 Importing and Exporting 13-15 W Windows 2000 Client Installation 1-18 Windows 2000 Installation 1-17 StormTracker EMS User Guide 08-00032-01, Rev. 2.1