05-6566a01

Transcript

PulseNET Enterprise Administration Guide Version 3.0.0 MDS 05-6566A01 Table of Contents 1 Introduction 5 What is PulseNET? Understanding PulseNET Roles PulseNET Documentation Release Notes Installation Guide User Guide Administration Guide 2 Getting Started 5 5 7 7 7 7 8 9 Starting PulseNET Stopping PulseNET Starting the High Availability Service Stopping the High Availability Service Logging in to PulseNET Manually Installing PulseNET as a Windows Service 9 10 11 11 12 12 Using the Administration Dashboard 13 Using the Start Menu Options Using the Command Line 3 Working with Licenses Requesting Licenses Configuring Email Settings Installing Licenses Managing Licenses Deleting Licenses Migrating Authorized Devices from an Expiring License to a New License Requesting Replacement Licenses License Order when Authorizing Devices Example 1 Example 2 4 Working with Users Creating Users Managing Users Reconfiguring Existing Users Copying Existing Users to Create New Users Changing the Passwords of Existing Users Expiring the Passwords of Existing Users Updating Roles for Existing Users Removing Users Viewing Audit Information for Users 13 13 15 15 16 17 18 18 18 19 19 19 19 21 21 22 22 23 23 24 24 24 25 Configuring Password Settings Setting User Session Timeout Configuring LDAP 25 26 26 Enabling RADIUS Authentication 31 Importing LDAP Groups Adding External RADIUS Users 30 31 5 Managing Device Groups Adding and Removing Subgroups Configuring Subgroups Assigning User Permissions Managing Monitored Devices Viewing the Audit Log 6 Rules and Notifications Applying Rules to Monitored Devices Enabling and Disabling Rules Configuring Rule Thresholds Trigger Delay Values Enabling Email and SNMP Trap Notifications for Rules 7 Managing Reports Building Custom Report Templates Managing Your Custom Template Running and Scheduling Reports Using a Custom Template 32 33 34 35 37 38 40 40 43 44 44 45 46 46 49 50 Viewing Audit Information 50 8 Global Device Settings 51 Scheduling Device Data Collection Managing Firmware Images Adding and Removing Images Changing the Image State Deploying Images to Devices Viewing Audit Information for Firmware Images Using Free-form Data Fields 9 Managing Dlink Devices Adding Dlink Master Seeds Editing Dlink Master Seed Settings Deleting Dlink Master Seeds Changing Global Advanced Dlink Settings 51 53 53 54 55 57 57 60 60 61 61 61 10 Managing SNMP Devices 64 11 Managing 4G Devices 68 Managing SNMP v1 or v2c Community Strings Managing SNMP v3 Credentials Defining Advanced SNMP Settings Migrating Devices between Strings or Credentials Configuring 4G Interfaces Defining Global Device Settings on the Element Manager Discovering Air4G Base Stations Adding Credentials Defining Air4G Base Station Settings 12 System Configuration Email Settings Enabling SNMP Trap Actions Managing Schedules Enabling Google Maps API Functionality Configuring Web Server Ports 64 65 66 67 68 69 69 70 70 71 71 71 73 74 74 13 Getting Support Generating a Support Bundle Requesting Support Managing Support Bundles Downloading Generated Support Bundles Deleting Generated Support Bundles Cartridge Information 76 76 76 77 77 77 78 14 Appendix 79 Metric View Chart Options Metric View Gauge Options Metric View List Options 79 80 80 Introduction 1 The Administration Guide is intended to help you configure and manage PulseNET and contains information related to configuring the system settings and monitoring devices. This section describes the Operator and Administrator roles, provides instructions for starting, stopping, and logging in to PulseNET, and describes the Administration Home dashboard that you see when you log in with the PulseNET Administrator role. What is PulseNET? PulseNET is a software application used for monitoring devices in Industrial Communications networks. Each device that PulseNET monitors serves a specific function in the network. These functions may include acting as a bridge, router, access point/base station, or remote/subscriber. The devices can be widely dispersed geographically and are able to operate with different bandwidths, depending on radio type and frequency. For additional information on specific Industrial Communications products, refer to the GE MDS website: http://www.gedigitalenergy.com/Communications/. PulseNET Base is intended for small-scale operations with a need to monitor less than 500 devices. PulseNET Enterprise is intended for large-scale operations with a need to monitor up to 25,000 devices. Understanding PulseNET Roles There are two PulseNET roles to which permissions can be assigned: Operator — An operator is primarily responsible for tracking the status of the devices that the system is monitoring. Operators have access to a restricted set of dashboards. An administrator, or an operator who has been assigned Device Group Owner permissions by an administrator, may also assign an operator additional device-group-specific permissions (such as performing discovery or decommissioning devices). The User Guide primarily explains the tasks that operators can accomplish. PulseNET Administration Guide Introduction Administrator — An administrator installs, configures, and controls the overall functionality of the PulseNET system, and provides support for all of the operators. An administrator has a number of responsibilities including creating users, creating device groups, requesting and installing licenses, assigning device-group-specific permissions to operators, as well as configuring email settings and the frequency of data collection and retention. This Administration Guide outlines the advanced responsibilities granted to administrators. Since the User Guide contains basic information for operations that will be employed by all users, it is recommended that administrators read through that guide as well. The following table lists each PulseNET administrative task along with the corresponding permission name, if applicable, and the role of the person who performs the task. Task Permission Name Role Installing and setting up PulseNET Configuring system settings Requesting, installing, and managing licenses Configuring global device settings Creating and managing users Creating and managing device groups and assigning permissions Performing discovery Triggering collections Configuring failover Creating and managing maintenance windows Generating, scheduling, and managing reports Upgrading firmware Decommissioning devices Adding an alias for a device or network interface Generating and managing support bundles and requesting support — — Administrator Administrator — Administrator — — Administrator Administrator Device Group Owner Administrator or Operator Perform Discovery Collection Management Failover Configuration Administrator or Operator Administrator or Operator Administrator or Operator Maintenance Windows Administrator or Operator Reporting Administrator or Operator Firmware Push Decommission Device Administrator or Operator Administrator or Operator Update Alias Administrator or Operator — Administrator 6 PulseNET Administration Guide Introduction PulseNET Documentation Release Notes The Release Notes provide: • A list of new and updated features • Workarounds for any known issues • Late-breaking news about the software Consult this document first, because it may contain updates to information and procedures described in the other PulseNET documents. Installation Guide The Installation Guide includes: • Installation prerequisites, system recommendations, and planning guidelines • Instructions for installing and configuring PulseNET on all supported platforms • Information about installing and configuring the Agent Manager • Detailed instructions on setting up and running PulseNET as a High Availability service User Guide The User Guide provides basic navigation and operation information that all users, especially those with the Operator role, will need in order to effectively use PulseNET. • An overview of PulseNET, describing its purpose, explaining key concepts, and providing instructions for basic navigation • Basic navigation and dashboard overview • Working with time ranges, charts, and tables • Managing and monitoring devices, including information on device detail views • Creating and scheduling reports and dealing with alerts • Discovering and authorizing devices and managing device groups Because the information contained in this guide is vital for the normal operation of PulseNET, we recommend that both Operators and Administrators read this guide. 7 PulseNET Administration Guide Introduction Administration Guide The Administration Guide is intended to help those with the administrator role configure and manage the PulseNET system. This guide provides instructions on how to perform administrative tasks such as: • Creating users and device groups • Requesting and installing licenses • Managing device groups and permissions • Configuring email settings and user access methods • Creating report schedules and setting rule thresholds • Setting the polling frequency for data collection • Requesting GE support 8 2 Getting Started Starting PulseNET Windows—Choose one of the methods listed below. • If PulseNET is installed to run as a service, go to the Services application, select PulseNET from the list, and click Start Service. • If you installed the startup icon in the default location, navigate to Start > Programs > GE MDS > PulseNET 3.0 > Start PulseNET. • Double-click the Start PulseNET shortcut on the desktop. • Open a command window and navigate to the directory \bin and execute the following command: fms.exe -s When PulseNET starts successfully, the following message appears in the command window: PulseNET startup completed. Additional fms commands: Command Represents -s start -n name -j jvm-argument -v version -h -b -r help start-service remove-service Description Starts PulseNET (this is assumed if no command is specified). Provides a unique name for this instance of PulseNET. Sets an option to be passed directly to the Java VM. Can be used to set more than one VM option. Displays the version number for this program and exits. Shows help information and exits. Starts the service. Stops and removes the service. IMPORTANT — During the initial startup, an Agent Manager command prompt window may open. Do not close the command window. The window closes when the server is shut down. This is most likely to occur on Windows 7 or 2008 R2. PulseNET Administration Guide Getting Started Be aware that the embedded Agent Manager starts automatically with the PulseNET service. When that happens, WARN messages like the following may appear in the log file for the PulseNET Agent Manager. These messages can safely be ignored. • Could not find an acceptable JRE in \fglam\jre • The path \fglam\jre does not exist or is not a directory Linux—Choose one of the methods listed below. • If PulseNET has been configured to run at boot time, use the method appropriate to your version of Linux to start the running service. For example: service pulsenet start (on RedHat) • If PulseNET shortcuts were created at install time, double-click the shortcut to start PulseNET. • Open a terminal window and navigate to /bin and execute the following command: fms -s The additional fms command options in the Windows list above can be used on Linux. Stopping PulseNET Windows—Choose one of the methods listed below. • If PulseNET is running as a service, go to the Services application, select PulseNET from the list, and click Stop Service. • If you installed the startup icon in the default location, navigate to Start > Programs > GE MDS > PulseNET 3.0 > Stop PulseNET. • Double-click the Stop PulseNET icon on the desktop. • Type Ctrl-C on the command window in which PulseNET started. • Navigate to the directory \bin and execute the following command: fms -q Linux—Choose one of the methods listed below. • If PulseNET has been configured to run at boot time, use the method appropriate to your version of Linux to stop the running service. For example: service pulsenet stop (on RedHat) • If PulseNET is running in a terminal window, type Ctrl-C to stop PulseNET. • If PulseNET shortcuts were created at install time, double-click the shortcut to stop PulseNET. 10 PulseNET Administration Guide Getting Started Starting the High Availability Service When running PulseNET in High Availability (HA) mode, there are multiple servers in the HA cluster. Windows—Choose one of the methods listed below. • Navigate to Start > Programs > GE MDS > PulseNET 3.0 > High Availability > Start PulseNET in HA Mode. • If PulseNET is installed to run as a service, go to the Services application, select PulseNET High Availability from the list, and click Start Service. • Open a command window and execute the following command: \bin\fmsha When the server has started successfully, the following message appears in the window: High Availability Server startup completed. IMPORTANT — During the initial startup, an Agent Manager command prompt window may open. Do not close the command window. The window closes when the server is shut down. This is most likely to occur on Windows 7 or 2008 R2. Linux—Choose one of the methods listed below. • If PulseNET has been configured to run at boot time, use the method appropriate to your version of Linux to start the running service. For example: service fmsha start (on RedHat) • If PulseNET shortcuts were created at install time, double-click the shortcut to start PulseNET in High Availability. • Open a terminal window and navigate to /bin and execute the following command: fmsha Stopping the High Availability Service Windows—Choose one of the methods listed below. • Navigate to Start > Programs > GE MDS > PulseNET 3.0 > High Availability > Stop PulseNET in HA Mode. • If PulseNET is installed to run as a service, go to the Services application, select PulseNET High Availability from the list, and click Stop Service. • Type Ctrl-C on the command window in which PulseNET started in HA mode. • Open a command window and execute the following command: \bin\fmsha.exe -q 11 PulseNET Administration Guide Getting Started Linux—Choose one of the methods listed below. • If PulseNET has been configured to run at boot time, use the method appropriate to your version of Linux to stop the running service. For example: service fmsha stop (on RedHat) • If PulseNET HA is running in a terminal window, type Ctrl-C to stop PulseNET. • If PulseNET shortcuts were created at install time, double-click the shortcut to stop PulseNET. • Open a terminal window and navigate to /bin and execute the following command: fmsha -q Logging in to PulseNET NOTE — PulseNET must be running before you can log in with the web interface. To log in from the Windows Start Menu: 1  If the program was installed in the default location, navigate to Start > Programs > GE MDS > PulseNET 3.0 > PulseNET Enterprise Console. 2  In the web browser that appears, type a valid User name and Password in the appropriate fields, then click the Login button. To log in directly with a Web browser: 1  Open a Web browser and type the following URL: http://: where is the name of the machine where PulseNET is installed and is the HTTP or HTTPS port specified during installation (the defaults are 8080 and 8443). 2  Enter a valid User name and Password and click Login. Manually Installing PulseNET as a Windows Service After the installation has completed, you can install PulseNET as a Windows service either from the Start menu or the command line. The procedures below assume you have installed the program shortcuts in the default location. 12 PulseNET Administration Guide Getting Started Using the Start Menu Options • To install or remove the PulseNET service from the Start menu, navigate to Start > Programs > GE MDS > PulseNET 3.0 > Windows Service > Install Service For PulseNET (or Remove Service For PulseNET). • To start or stop the PulseNET service from the Start menu, navigate to Start > Programs > GE MDS > PulseNET 3.0 > Windows Service > Start Service For PulseNET (or Stop Service For PulseNET). Using the Command Line • Open a command window by right-clicking on the Command Prompt icon and selecting Run as administrator. • Type \bin\fms -i Using the Administration Dashboard The Administration dashboard is the default home page for an administrator. It provides links to other dashboards where you can complete administrative tasks. The dashboard provides the following links: Licensing — for requesting, installing, and managing licenses 13 PulseNET Administration Guide Getting Started Manage Device Groups — for setting up and maintaining device groups and managing threshold and notification rules Global Device Settings — for setting the frequency of data collection and managing device settings Reports — for generating, scheduling, and managing reports and viewing audit logs System Configuration — for managing email settings and schedules Users — for creating, configuring, and maintaining PulseNET users Support — for generating and downloading support bundles and requesting support 14 3 Working with Licenses A license provides PulseNET with the capacity to authorize and monitor devices. Each device connected with PulseNET requires a license. Requesting Licenses To request a license: 1  Navigate to Administration > box will appear. Licensing > Request a License. A dialog 2  In the Contact Name field, type your name. 3  In the Access Code field, type your access code. This code is saved; you do not have to re-type it for subsequent license requests. 4  In the Desired Capacity field, type the number of licenses required. For example, if you want to be able to monitor 100 access points and 300 remote devices, enter 400. 5  In the Comment field, enter any comments that you have. 6  Click Request License Now. An email requesting the license is sent automatically to GE. If you have not configured PulseNET email settings, PulseNET opens the license request for you to send through an external email client. (For more information, see Configuring Email Settings below. In some cases, this step may need to be completed before you can request the license.) If the request is approved, the new license is sent to you within one business day. If you cannot request a license using the browser interface because your PulseNET server is not connected to the Internet, populate the Request License dialog box above, take a screen capture of the populated dialog box, and then email the screen capture to [email protected]. After you have taken the screen capture, cancel the dialog box. PulseNET Administration Guide Working with Licenses 16 Configuring Email Settings After you log in to PulseNET for the first time, configure the email settings so that you can request licenses from GE and allow PulseNET to notify users about system issues. To define email settings: 1  Navigate to Email Settings. Administration > System Configuration > Configure 2  In the Configure Email Settings dialog box, click Edit for each property and define the required values so that you can be notified about system issues (see the table below for information about these values). 3  When you are finished editing the properties, click Test Configuration to ensure that emails can be sent. 4  In the Recipient Addresses box, type your email address. 5  Click Send Test Email. PulseNET accesses the mail server using the email configuration parameters and sends a test email to your email address. Check your mailbox to ensure that it contains a new email message. To clear a property value, click the Clear icon for the property. Below are explanations of the values you must define in order to receive email notifications about system issues: Mail Server (required) Sender Address (required) The host name or IP address of the mail server that is used for sending email. The email address of the user that PulseNET uses to send email. The email distribution list that receives all system event email notifications. Users will be notified Recipient Address about system events like CPU failures or expiring (required) licenses. Separate multiple email addresses with a comma. The user name of the account PulseNET uses to send emails. If your mail server requires user User Name to Log in to authentication, you must supply the user name Server and password. For more information, contact your mail server administrator. PulseNET Administration Guide Working with Licenses User Password Mail Server Port Mail Protocol Enable Debug Mode? Enable STARTTLS? Enable SSL? The password of the user account PulseNET uses to send emails. The port number that PulseNET uses to communicate with the mail server. The transport protocol used for sending emails. The supported protocols are SMTP and SMTPS. This is for enabling or disabling debug mode so that email-related debugging information is stored in the log. Indicates whether you want to enable the STARTTLS protocol and use encryption when sending emails from PulseNET. Indicated whether you want to enable the SSL protocol and use encryption when sending emails from PulseNET. Now that your email settings are defined, you can request licenses from GE. For more information, see Requesting Licenses above. Installing Licenses After you receive new licenses, you must install them so that you can authorize and monitor the devices in your network. To install a license: 1  Navigate to Administration > Licensing > Install a License. 2  In the dialog box that appears, click Choose File to locate the license file on your computer (the file must be on the machine where the browser is running). 3  Click Install. If the license is valid, it is installed on the system. Otherwise, you will receive a message stating that the license file is invalid. You must try installing a different license. If you have a previous license installed that is about to expire, you are asked if you want to migrate any existing authorized devices to the new license. If you want to migrate authorized devices to the new license, click Migrate. (See Migrating Authorized Devices from an Expiring License to a New License.) 17 PulseNET Administration Guide Working with Licenses Managing Licenses Installed licenses appear under Administration > Licensing > Manage Licenses. After licenses are installed, you can delete expiring licenses, migrate devices to new licenses, or request a replacement license. Deleting Licenses Only expiring licenses can be deleted. The license must be 14 days or less from its expiration date. To delete a license: 1  Navigate to Administration > 2  Find the license and click the button. 3  Click the Licensing > Manage Licenses. check box next to the License icon to enable the Delete Delete button. 4  In the confirmation dialog box, click Delete. Migrating Authorized Devices from an Expiring License to a New License To migrate authorized devices from an expiring license to a new license, you must have a new license installed. See Installing Licenses above. Migrating existing devices to a new license will not require a new discovery process, will not impact system configuration, or affect any stored data. To migrate authorized devices to a new license: 1  Navigate to Administration > Licensing > Manage Licenses. 2  In the table, find the expiring license. Click the value in the Used column (under the Monitoring Capacity heading). The Migration dialog box appears. NOTE — This functionality is only available if the license is expiring (that is, if the license is 14 days or less from its expiration date). 3  In the column at the left, click the check boxes for the devices you want to migrate. To select all of the devices, click the check box at the top of the column. 4  Click Migrate Now. 5  In the confirmation dialog box, click Proceed. The authorized devices you selected migrate to the new license. 18 PulseNET Administration Guide Working with Licenses Requesting Replacement Licenses If a GE device is removed from service and replaced with a new device, you will need to request that GE send a replacement PulseNET license for the new device. Existing licenses are bound to the serial numbers of GE devices, so they cannot be reused once they have been assigned to a specific device during the authorization process. License Order when Authorizing Devices If your environment has a mix of active licenses (where the expiration date is more than 14 days away) and expiring licenses (where the expiration date is in 14 days or less), PulseNET uses the following order in the authorization process: 1  The active license pool with remaining capacity that is expiring earliest 2  The active license pool with remaining capacity that is expiring next (until all active licenses are exhausted) 3  The expiring license pool with remaining capacity that is expiring earliest 4  The expiring license pool with remaining capacity that is expiring next (until all expiring licenses are exhausted) Example 1 There are 2 active licenses: one license has an expiration date of July 1 and remaining capacity for 10 devices, the other license has an expiration date of August 1 and remaining capacity for 20 devices. Today is May 20 and you want to authorize 15 devices. License capacity is consumed in the following order: 1  10 available on the July 1 license 2  5 of the 20 available on the August 1 license The July 1 license has no remaining capacity, and the August 1 license has remaining capacity for 15 devices. Example 2 Like in Example 1, there are 2 active licenses: one license has an expiration date of July 1 and remaining capacity for 10 devices, the other license has an expiration date of August 1 and remaining capacity for 20 devices. 19 PulseNET Administration Guide Working with Licenses There are also 2 expiring licenses: the first license has an expiration date of May 21 and remaining capacity for 10 devices, the second license has an expiration date of May 22 and remaining capacity for 10 devices. Today is May 20 and you want to authorize 40 devices. License capacity is consumed in the following order: 1  10 available on the July 1 license 2  20 available on the August 1 license 3  10 available on the May 21 license The July 1, August 1, and May 21 licenses have no remaining capacity. The May 22 license still has remaining capacity for 10 devices. 20 4 Working with Users PulseNET controls user access using the concept of users and roles. When administrators create new users, a role is assigned to the user. The assigned role determines the dashboards and views that users can access when they log in to PulseNET. Users assigned to the PulseNET Administrator role have access to all available dashboards. Users assigned to the PulseNET Operator role have access to a restricted set of dashboards. Creating Users As a PulseNET Administrator, you can create new PulseNET users. To create a new user from the Users view: 1  Navigate to 2  Click Administration > Users. Create New User. 3  In the New User wizard, type a name for the new user. Click Next. 4  Assign the new user a role. A user can be an administrator or an operator, but not both. Administrators have access to all operator functionality. See Understanding PulseNET Roles. 5  Click Next. 6  In the Password and Confirm Password fields, type the same password. If you want the new user to change the password the first time that they log in, leave the check box selected. If not, clear the check box. (The password requirements depend on configurable password settings; see Configuring Password Settings.) 7  Click Finish. The new user appears in the User Management list: Manage Users. Administration > Users > PulseNET Administration Guide Working with Users Managing Users All users are listed in the User Management view. For each user, you can edit or delete the profile, make password updates, and change the assigned role. To make changes to existing users: 1  Navigate to Administration > Users > Manage Users. 2  In the User Management list, click on the name of a user. 3  In the dialog box that opens, the following options are available: • Editing Existing Users • Copying Existing Users to Create New Users • Changing the Passwords of Existing Users • Expiring the Passwords of Existing Users Reconfiguring Existing Users To edit the configuration of an existing user: 1  Navigate to Administration > Users > Manage Users. 2  In the User Management view, click the name of the user. 3  In the popup that appears, click Edit. 4  On the first page of the wizard, you are able to edit the user’s email address (however, user names cannot be edited). Click Next. 5  On the second page, you are able to assign the user to a different role. Select either PulseNET Administrators or PulseNET Operators. A user can be an administrator or an operator, but not both. Administrators have access to all operator functionality. (For more information, see Understanding PulseNET Roles.) Click Next. 6  On the third page, you are able to change the password of the user. (The password requirements depend on configurable password settings. For more information, see Configuring Password Settings.) Type the new password and confirm. 7  Click Finish. The new user appears in the User Management list: Manage Users. Administration > Users > 22 PulseNET Administration Guide Working with Users Copying Existing Users to Create New Users To create a new user by copying an existing user: 1  Navigate to Administration > Users > Manage Users. 2  In the User Management view, click the name of the user. 3  In the popup, click Copy. 4  In the wizard that appears, type a name for the new user. 5  Click Next. 6  Assign the user a role. Select either PulseNET Administrators or PulseNET Operators. NOTE — A user can be an administrator or an operator, but not both. Administrators have access to all Operator functionality. For more information, see Understanding PulseNET Roles. 7  Click Next. 8  Type the new password in each of the fields (Password and Confirm Password) provided. If you want the user to change the password the first time that he or she logs in, leave the check box selected. If not, clear the check box. (The password requirements depend on configurable password settings. For more information, see Configuring Password Settings.) 9  Click Finish. The new user appears in the User Management list: Manage Users. Administration > Users > Changing the Passwords of Existing Users To change the password of an existing user: 1  Navigate to Administration > Users > Manage Users. 2  In the User Management view, click the name of the user. 3  In the popup menu, click Change Password. 4  Type the new password in the each of the boxes (Password and Confirm Password). 5  Click Change. The password is updated. For more information about password administration for PulseNET, see Configuring Password Settings. 23 PulseNET Administration Guide Working with Users Expiring the Passwords of Existing Users To expire the password of an existing user: Administration > 1  Navigate to Users > Manage Users. 2  In the User Management view, click the name of the user. 3  In the popup menu, click Expire Password. 4  In the confirmation dialog box, click Change Password Next Logon to force the user to change their password. A notification icon appears in the Force Change Password column for the user. For more information about password administration for PulseNET, see Configuring Password Settings. Updating Roles for Existing Users For more information about roles and the types of responsibilities users can have, see Understanding PulseNET Roles. To change the role of an existing user: Administration > 1  Navigate to Users > Manage Users. 2  In the User Management view, find the name of the user. 3  In the Roles column, click the existing role of the user (administrator or operator). 4  In the Assign Roles dialog box, select the new role. 5  Click Save. The next time the user logs in to PulseNET, they will have access to the features and functions that are permitted by the newly assigned role. Removing Users To remove users from PulseNET: 1  Navigate to Administration > Users > 2  In the User Management view, select the enable the Remove button. 3  Click the Remove button. 4  In the confirmation dialog box, click Delete. The user is removed from PulseNET. Manage Users. check box next to the name of the user to 24 PulseNET Administration Guide Working with Users Viewing Audit Information for Users PulseNET records changes to users in the audit log. Each audit log entry shows the date and time at which the operation was performed, the name of the user who initiated the operation, and the operation name. To view the changes made to a user: 1  Navigate to Administration > Users > Manage Users. 2  In the row for the user, click View Audit in the Audit column. All changes that have been made to the user account are shown in the audit log. Configuring Password Settings As an administrator, you can configure a number of password settings. To change one of the password settings: 1  Navigate to Administration > Users > Password Policy Settings. Password Setting Days before user password expires Days before administrator password expires Bad logins before user account is locked Seconds after which lockout expires (0 for no expiration) Minimum password length Number of old passwords that will be remembered Maximum user name length Number of days before password expiration to warn user User password complexity level: 1 = Passwords must be seven or more characters in length and contain at least one alpha and one numeric character 2 = Passwords must be seven or more characters in length and contain at least one alpha, one numeric, and one upper case character 3 = Passwords must be seven or more characters in length and contain at least one alpha, one numeric, one upper case, and one special character Default 90 45 5 900 7 12 15 15 1 25 PulseNET Administration Guide Working with Users Admin password complexity level: 26 2 1 = Password must be seven or more characters in length and contain at least one alpha and one numeric character 2 = Password must be seven or more characters in length and contain at least one alpha, one numeric, and one upper case character 3 = Password must be seven or more characters in length and contain at least one alpha, one numeric, one upper case, and one special character User cache expiration in minutes (login is fast until cache expires) 600 2  Click on the password setting value and make your change. 3  Click Save. To configure a number of password settings: 1  Navigate to 2  Click Administration > Users > Password Policy Settings. Edit and make your changes. 3  Click Save. Setting User Session Timeout As an administrator, you can set the user session timeout. To set the user session timeout: 1  Navigate to Administration > Users > User Session Settings. 2  In the Change User Session Timeout dialog box, type the number of minutes after which a user is logged out. If you do not want users to ever be logged out automatically, select Session Never Times Out. 3  Click OK. Configuring LDAP Instead of duplicating your existing LDAP or Active Directory users in PulseNET, you can configure PulseNET to send authentication requests directly to your LDAP or Active Directory server. PulseNET supports Lightweight Directory Access Protocol (LDAP version 3) compatible directory services, including Active Directory, Sun Java Systems Directory Server, OpenLDAP, and Novell eDirectory. PulseNET Administration Guide Working with Users 27 You need to be familiar with the details of your LDAP directory service to set the appropriate configuration parameters in PulseNET. The following considerations are important when planning to integrate an external directory service with the PulseNET: • Secure LDAP is supported, but not required • LDAP with Transport Layer Security is not supported • A persistent connection to the LDAP server is not required LDAP groups can be imported into PulseNET and assigned PulseNET roles. This allows for users who have been granted special permissions within an organization to have associated permissions in PulseNET. User credentials continue to be managed on the LDAP server. Any password changes in the LDAP directory service are transparent to PulseNET. After a password change in the directory service, that user can log into PulseNET with the new password, while any attempts to use the old password will fail. If a user account is removed from the directory service, any login requests with those credentials result in a login failure in PulseNET. Similarly, if the LDAP authentication service is down, PulseNET cannot authenticate users whose accounts are defined there. At the same time, any internal PulseNET users, such as the built-in admin user or any accounts that you create manually using the Manage Users dashboard, are unaffected during LDAP authentication service interruptions. To configure PulseNET with your LDAP server information: 1  Navigate to Administration > Users > Configure LDAP Settings. 2  On the Configure LDAP Settings view, in the LDAP Locations section at top, click Edit and type in the Nearest LDAP server URL. This is the URL to the primary LDAP server. For basic LDAP, use the following syntax: ldap://host:port, where host is the fully qualified domain name or IP address of the LDAP server and port is the number of the network port for the LDAP server. For secure LDAPS, use the following syntax: ldaps://host:port If you are using Active Directory, PulseNET searches child domains of the primary LDAP server. If the primary LDAP server fails, it searches child domains of the secondary LDAP server (specified by the Secondary LDAP server URL setting). 3  If desired, specify the Secondary LDAP server URL (use the same syntax as the primary). 4  Click Test to verify the status of the LDAP server. Ensure that the LDAP server is up. 5  Close the validation dialog box and then click Save. 6  In the Settings section, click Edit and provide the required information. Descriptions of typical parameters are shown in the chart below. PulseNET Administration Guide Working with Users Each LDAP server has different settings. Use the following information merely as a guideline and refer to your LDAP server documentation for the applicable values for your system Account is anonymous Distinguished name of the service account Password If enabled, PulseNET uses an anonymous service account to search for users in the extended directory. The default user name for anonymous service accounts is _anonymous_ and enabling this option sets the Distinguished Name of the service account to _anonymous_ The distinguished name (DN) of the service account to fetch users and groups. In Active Directory, typically a common name (CN) is used instead of DN. For example: CN= John Smith, OU=Employees, DC=company, DC=com. The password of the service account used for user searching in the external directory. The query for finding employees in the external directory. The external directory tree typically contains multiple levels. You can narrow the search to the specific groups that you want the LDAP queries to use by setting the prefix and suffix of the query. LDAP query prefix and suffix If you are using Active Directory, point the LDAP query suffix to the root of the domain to search the entire domain. For example, in Active Directory, if the CN user accounts are defined in the sAMAccount=Users group, and the Active Directory domain is 2K3.DOM, apply the following settings: a) LDAP query prefix: CN= b) LDAP query suffix: ,CN=Users,DC=2k3,DC=dom NOTE — LDAP authentication can also be configured if the LDAP query prefix is set to “sAMAccountName=”. When the prefix and suffix are specified, they are appended to the LDAP queries. The scope(s) to search for groups, the second group namespace, and the third group namespace The query to search for groups identified in your LDAP server. For example: OU=Groups,DC=2k3,DC=dom. The order in which the groups are searched is determined by the order of the groups listed in these settings. The LDAP context for user searching Similar to specifying the groups in the directory tree, this setting provides a way for selecting a portion of the directory tree, giving a context to the query. If you are using Active Directory, this value should match the LDAP query suffix setting without the leading comma. For example, if the LDAP query suffix is ,CN=Users,DC=2k3,DC= dom the LDAP context for user searching would be CN=Users,DC=2k3,DC=dom Role attribute ID and Is Role attribute a DN User alias attribute ID User attribute ID to search for groups Match on User DN JAAS LoginModule name Groups in the external directory are objects with attributes. Each attribute has an ID and a value. The setting Role attribute ID specifies the name of the attribute that uniquely identifies the name of the role in the external directory. LDAP queries use the role attributes to authenticate users. Is Role attribute a DN specifies whether the role attribute is a distinguished name. For Active Directory, this setting should always be set to “false”. User accounts in an external directory can have aliases. This setting specifies the name of the attribute associated with the user alias. Specifies the name of the attribute of groups (for example, member) that contains users’ distinguished names. Indicates if user distinguished names are matched. This setting is internal and it should never be modified. 28 PulseNET Administration Guide Working with Users Name of JAAS security domain Parent group attribute ID Group attribute for nested group searching Maximum level of group nesting LDAP search timeout (milliseconds) Mode of group searching This setting is internal and it should never be modified. Specifies the name of the attribute of users and groups (for example, memberOf) that holds the containing groups’ distinguished names. Specifies the name of the attribute of groups (for example, member) that contains nested groups’ distinguished names. Specifies the maximum number of nested groups that can be queried. Specifies the maximal duration of an LDAP search, in milliseconds. LDAP searches that take longer than this will result in timeouts. Indicates the direction in which groups are searched: a) disabled = Do not search for groups, b) direct = Search for groups using the Parent group attribute ID (for example, memberOf), c) indirect = Search for groups in the scope to using the User attribute ID to search for groups and Group attribute for nested group searching. 7  When you have finished entering the appropriate LDAP settings, click Save. 8  To validate your settings, click Test Configuration. 9  In the Test Configuration dialog box, type a user name that exists in the newly integrated external directory. Click Test. PulseNET queries your LDAP server for that user. 10  When you receive the configuration validation, click OK and then close the Test Configuration dialog box. If you are configuring PulseNET to use secure LDAP, an additional step is required. PulseNET makes use of the standard Java LDAP service provider using Java Secure Socket Extension (JSSE) software for SSL support. To configure secure communication between PulseNET and your LDAP server, you need to ensure that the PulseNET LDAP client trusts your LDAP server. To do this, install the LDAP server’s root certificate (CA) in PulseNET’s database of trusted certificates. 1  Navigate to \jre\lib\security 2  Obtain the CA certificate for your secure LDAP server and make sure it is accessible under 3  Use the Java keytool program to import your LDAP server’s root CA certificate into the keystore. Refer to the documentation for the Java keytool command if you need additional information (docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool. html). If the jssecacerts keystore does not exist, the following commands will create it. If it already exists, be sure you have the existing keystore password to access it. • \jre\bin\keytool -import -file \.crt -keystore jssecacerts • Enter the jssecacerts keystore password, or enter a new password if none previously existed. 29 PulseNET Administration Guide Working with Users • Look at the files in the security folder to verify that the jssecacerts keystore exists. 4  Restart the PulseNET service and log in as an admin user to retest LDAPS connectivity. PulseNET can now send requests to your secure LDAP server. Importing LDAP Groups LDAP groups can be imported and assigned PulseNET roles (Operator or Administrator) so that LDAP users can access PulseNET with the appropriate permissions for their roles. External LDAP servers typically contain many organizational groups, but only a few need to be imported into PulseNET. You may need to have your LDAP administrator create new groups or modify existing ones on the LDAP server in order to consolidate LDAP users into the appropriate PulseNET role categories, which will help avoid issues later on. Select the groups that you need to see in PulseNET’s User Management view so that each group can be assigned a PulseNET role. To select LDAP groups: 1  Navigate to Administration > Users > Manage Users. 2  On the User Management view, click the Group Mapping tab and then click LDAP Groups. 3  In the LDAP Group Visibility Settings dialog box, find the groups that you want to add to PulseNET. The group list shown here is limited by the Scope(s) to search for groups value on the Configure LDAP Settings display that was discussed above. 4  If the group is not listed, click Import Groups to search for the group name. • If desired, limit the number of search results. In the Import External Groups dialog box, click Results Limit and select an appropriate value. • Type a text string for the search filter. For example, to find groups whose names start with Office.Services, in the Group Name box type Office.Services, and click Update Group List. An asterisk (*) can be used as a wildcard. • Select the groups that you want to import and click Import Groups. 5  When the import is confirmed, the LDAP Group Visibility Settings dialog is updated with the groups that you imported. They are now available to be added to PulseNET. 6  Select the LDAP groups that you want to add to PulseNET. 7  Click Save. The LDAP groups that you selected are displayed on the Group Mapping tab. By default, new groups are assigned the PulseNET Operator role. Any external user contained in that group can now log in to PulseNET and see the dashboards and views that Operators are allowed to access. 30 PulseNET Administration Guide Working with Users Repeat these steps whenever you want to update PulseNET with an external LDAP group. Any groups that you have already imported will remain selected. To change the role for a group, select the PulseNET Operators value in the Roles column. In the dialog box, select the PulseNET Administrators role. If only some of the users in the LDAP group require access to administrative dashboards and views, change the role for those users only, rather than the entire group. For more information, see Updating Roles for Existing Users. Enabling RADIUS Authentication If you use Remote Authentication Dial In User Service (RADIUS) to manage user access to your network, you can enable RADIUS server authentication in PulseNET. When the PulseNET server is configured to access the RADIUS server, it is able to authenticate PulseNET users there, which enables you to manage user credentials using RADIUS. To enable RADIUS authentication: 1  Navigate to Administration > Users > 2  In the dialog box that appears, select the Configure RADIUS Settings. Enable check box. 3  In the Server Host Name box, type the host name or IP address of the RADIUS server. 4  In the Authentication Port and Accounting Port boxes, type each port number. 5  In the Shared Secret box, type the authentication key for the RADIUS server. 6  Select the Authentication Mode — PAP (Password Authentication Protocol) and CHAP (Challenge-Handshake Authentication Protocol) are both supported. 7  To ensure that all values are correct, click Test Connection to try connecting to the RADIUS server. 8  After the test connection is successful, click Save. PulseNET and the RADIUS server are now connected. PulseNET only supports RADIUS user names that have more than four characters. Adding External RADIUS Users After you enable RADIUS authentication, existing RADIUS users can log in to PulseNET. Matching PulseNET user accounts are created and assigned the Operator role. If certain users require administrative permissions, a PulseNET administrator can upgrade those permissions. See Updating Roles for Existing Users. 31 Managing Device Groups 5 This section describes how to create and manage device groups for organizing your monitored devices. Devices are added to device groups when they are authorized, after the initial discovery process is complete. For more information about authorization, see “Authorizing Devices” in the User Guide. PulseNET provides two default device groups: • Production: For devices that are in your production environment and that are actively being monitored. • Staging: For devices that you want to monitor separately so that they do not affect the device availability (KPIs) in your production environment. For example, you can authorize new devices into this root group and monitor them to ensure that they are working as expected before you move them to production device groups. Also, if a device that is currently in your production environment is performing poorly, move it into this group so that you can monitor its performance separately. Administrators are owners of these default device groups and therefore have global administrative control over all device groups underneath them. However, Administrators who are external users (imported from LDAP) must be manually added to the Production and Staging groups so that they have the same administrative control as internally-created Administrators. To organize your monitored devices, create a logical structure of subgroups under the Production or Staging root groups. When you create a new subgroup, you must assign an owner, who will be responsible for administering the devices in that group. Both Administrators and Operators can be group owners. Owners receive alerts if predefined rule thresholds are met for devices in their device groups. In addition, device group owners can give other users ad- PulseNET Administration Guide Managing Device Groups 33 ministrative responsibilities for devices in the group. For more information, see Assigning User Permissions. For each group or subgroup, PulseNET supports the following activities: • Adding and Removing Subgroups • Configuring Subgroups • Managing Monitored Devices • Viewing the Audit Log for Device Groups Adding and Removing Subgroups Before you create device groups, consider which users you want to be the owners of the device groups. If the users have not yet been created, create the users first so that you can assign them to be device group owners. For more information, see Creating Users. Device group owners and inherited users of the parent group have permission to add subgroups underneath their parent group. To add a new subgroup: 1  Navigate to 2  Click Administration > Manage Device Groups. New Subgroup. 3  In the New Subgroup wizard, select the group that will be the parent of the new subgroup. A maximum of five subgroup levels can be created. Click Next. 4  Type the new group name in the required field. 5  Specify a group owner by clicking the Not specified link. In the popup that appears, select one or more users to become the owner(s). Each group must have at least one owner, which can be either an administrator or operator. Device group owners have full administrative access over the group and the devices linked to it. Click OK. 6  Type a description for the group, if desired. Click Finish. PulseNET Administration Guide Managing Device Groups The subgroup is added to the parent group. Now you can configure the group by adding users and subgroups, or manage the rules and notifications for the group. To remove a subgroup: 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the parent group in the list. 3  In the same row as the parent group, in the Configuration column, click Edit. 4  On the Configure Group dashboard, click the Subgroups tab. 5  Select the group you wish to remove by clicking the will become active. 6  Click check box. The Delete button Delete. If the subgroup you are trying to remove still contains devices, a dialog box will appear asking you to move those devices to another group. You must move all devices out of a device group before you can delete it. Configuring Subgroups Assigning Existing Users to Device Groups Administrators and device group owners can configure groups by assigning users and adding subgroups. When subgroups are created, device group owners of the parent group become associated users of the subgroup. Their association is inherited, which means that the permissions that these users have on the parent group also apply to the subgroup now. To add existing users to a group: 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the group in the list. 3  In the same row as the desired group, in the Configuration column, click 4  On the Configure Group dashboard, click the Associated Users tab. 5  Click Add User. Edit. 34 PulseNET Administration Guide Managing Device Groups 6  In the dialog box, select the users that you want to associate to the device group. Click OK. The users are now associated with the group. They can view the devices in the group, but they cannot manage the group or its devices. If you want the new users to perform administrative tasks on the group and its devices, you must assign permissions to them. Assigning User Permissions Administrators have global permissions for all device groups. New users must be assigned permissions for each group before they can exercise administrative responsibilities for the devices in the group. To assign permissions to users: 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the group in the list. 3  In the same row as the desired group, in the Configuration column, click Edit. 4  On the Configure Group dashboard, click the Associated Users tab. 5  In the same row as the desired user, in the Manage Permissions column, click Edit. 6  In the Assign Permissions dialog box, select the permissions you wish to assign to the user for the devices in this group. Click OK. 35 PulseNET Administration Guide Managing Device Groups The permissions that you assign to the user only apply to the selected device group and any subgroups under it. If devices in this group are later moved to another group, the assigned permissions do not follow the devices. NOTE — Device group owners have full authority over the devices in the group. If you select the Device Group Owner permission, all of the other permissions will be automatically applied. The following table provides a description of the available permissions. Permission Description Discover and authorize SNMP and Dlink devices. Users can also authorize devices that are discovered by Dlink Passive Auto-discovery. Collection Management Trigger a configuration or performance collection for a device. Decommission Device Decommission devices so that data is not collected from devices. Firmware Push Upgrade devices with new firmware versions. Create scheduled and temporary maintenance windows so that data Maintenance Windows is not collected from devices when they are unavailable, for example, when maintenance tasks are being done on the device. Assign failover devices to Mercury access points and create and manFailover Configuration age redundant clusters. If failover occurs, PulseNET polls failover or redundant backup devices for configuration and performance data. Reporting Create and run reports on devices in device groups. Rename devices and network interfaces so that they are more meanUpdate Alias ingful within your monitoring environment. Configuration Edit configuration information in PulseNET and write those changes to Management remote devices in the field. Acquire Device This is the default permission for all associated users to view informaInformation tion about devices in the device group. Perform Discovery Users can now access specific dashboards related to their permissions. Operators with wider permissions can access these dashboards through the Administration menu on the Summary dashboard while viewing this group. Managing Monitored Devices To view the devices assigned to a particular group: 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the device group. In the same row as the desired group, in the Configuration column, click Edit. 36 PulseNET Administration Guide Managing Device Groups 37 3  On the Configure Group dashboard, click the Monitored Devices tab. All of the monitored devices that are assigned to this group are listed in the table. 4  To see devices assigned to subgroups of this group, toggle the Show Devices From Subgroups button. All of the devices assigned to the parent and its subgroups are listed in the table. To see only the devices assigned to the parent group again, toggle the Hide Devices From Subgroups button. To identify the devices that belong to the parent group, look at the Primary column. Devices that are marked Yes belong to the parent group. To drill down to the device detail view, click the device name. To learn more about the device detail view, see “Detail Views” in the User Guide. To decommission a device: If you know that a monitored device is not available and you do not want to attempt data collection from that device (because, for example, that would incorrectly impact PulseNET summary statistics), you can decommission the device. 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the device group. In the same row as the desired group, in the Configuration column, click Edit. 3  On the Configure Group dashboard, click the Monitored Devices tab. All of the monitored devices that are assigned to this group are listed. 4  In the row of the desired device, click the Decommission Device icon. Follow the instructions in the Decommission Devices dialog box. Decommissioned devices are removed. If needed, they can be recommissioned by performing a new discovery. For more information about decommissioning and recommissioning devices, see “Decommissioning a Monitored Device” in the User Guide. To move devices from one group to another: Devices can be moved to different groups. The workflow for moving devices depends on the type of device that you are moving. SNMP access points and remotes can be moved independently of their device groups. Dlink remotes and masters must be located in the same device group, so moving one device in the relationship moves them all. You cannot move devices to groups that you are not associated with. PulseNET Administration Guide Managing Device Groups 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the device group. In the same row as the desired group, in the Configuration column, click Edit. 3  On the Configure Group dashboard, click the Monitored Devices tab. 4  To select the devices that you want to move, select the check box next to the device name or click Select All. The Move Devices button will become active. 5  Click Move Devices. 6  On the first page of the Move Devices Wizard, review the list of devices. If you are moving SNMP devices, select the remote devices that you also want to move. If you are moving Dlink devices, the devices that will automatically be moved are listed. (All Dlink remotes move with the parent device.) Click Next. 7  Select the destination device group for the device you are moving. Click Next. 8  Verify your selections and click Finish to complete the move. Otherwise, click Previous to change settings or Cancel to abort the move. The devices are moved to the specified group. If email notifications for device moves have been enabled for the target device group, all users associated with the group will be notified about the new devices added. Viewing the Audit Log The Audit Log for a device group contains information about user and device changes for the group. Each log entry shows the date and time at which the operation was performed, the name of the user who initiated it, and the operation name. To view the audit log for a device group: 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the group in the list. In the same row as the desired group, in the Configuration column, click Edit. 3  On the Configure Group dashboard, click the Audit Log tab. The audit log lists all the operations that have been completed on the device group (like adding/removing subgroups, adding/removing users, decommissioning devices, moving devices between 38 PulseNET Administration Guide Managing Device Groups groups, and changing user permissions for the group). 4  To see all of the operations that have been completed on any subgroups associated with the device group, toggle the Show Audit Log From Subgroups button. To see only the operations for the parent group again, toggle the Hide Audit Log From Subgroups button. The Audit Log tab shows the list of administrative tasks during the selected time range. To change the time range, click the arrow and adjust the time settings as shown below. 39 Rules and Notifications 6 PulseNET employs several types of notifications so that you can efficiently monitor your system and devices. System event emails — System events (such as expiring licenses or CPU issues) that occur on the PulseNET machine will trigger automatic email notifications (which cannot be disabled). To direct such emails to the proper recipients, add the user email addresses to the Email Recipient Address property in the system settings. For more information, see Configuring Email Settings. Alerts based on PulseNET rules — Alerts are triggered when problems arise in your monitored environment. Once a performance rule has been enabled, PulseNET will send an alert ( fatal, critical, or warning) when it determines that one or more devices have met that rule’s predefined conditions. This alert appears as an icon beside the device name in the browser interface and a generic icon on the device type. See Enabling and Disabling Rules. Email notifications based on PulseNET rules — You can also receive email notifications if problems arise in your monitored environment. These notifications can be enabled instead of (or in addition to) the alerts sent when rule thresholds are met. Rules do not have to be enabled for these notifications to work. See Enabling Email and SNMP Trap Notifications for Rules. Applying Rules to Monitored Devices PulseNET contains a number of predefined rules for device monitoring or you can set your own custom rules. You can enable any of these rules and configure the thresholds you require so that you are notified if your system encounters problems. Rules and notifications can be configured separately for each device group and subgroup. Users are notified when rule thresholds are met if their email addresses are correctly configured in the system email settings. See Configuring Email Settings. PulseNET Administration Guide Rules and Notifications The following table provides a description of each of PulseNET’s predefined rules. Rule Description AP Change for Remote Monitors remote devices for migration to different access points. This is a PulseNET Simple Rule. If a change in access point is detected, an email notification is sent. N/A Bad Access Point Health Monitors the percentage of remote devices for an access point that are in a particular alert state or worse. Beyond that percentage, the access point may be the root cause of the problem. Warning, Critical, Fatal Bad Remote Health Monitors the percentage of remote devices that are in a particular alert state or worse. Warning, Critical, Fatal Bad Repeater Health Monitors TransNET devices that are acting as Store and Forward (SAF) or master devices. This rule fires if a defined number of downstream devices (direct children) are unavailable. Warning, Critical, Fatal Device Unavailable Monitors the availability of the device. Fatal Dlink Alert Notification This is a PulseNET Simple Rule. If a Dlink alarm is created or changed, an email notification is sent. N/A MAC Address not found Generates a warning when the MAC address of a device is not found. Warning PA Temperature Generates an alert for Dlink devices when Power Amplifier temperatures reach certain limits. Warning, Critical, Fatal Poor Response Time Monitors the ICMP round trip time for a device. Warning, Critical, Fatal Repeater Change for TransNET Remotes Monitors TransNET remote devices for a changed parent device. Warning RSSI Change Monitors for RSSI values (for devices) that are outside a two-day moving average. Warning, Critical, Fatal Monitors the RSSI levels for devices. Warning, Critical, Fatal Serial Number Unrecognizable Generates an alert when the serial number of a Dlink master is unrecognizable. Fatal SNR Change Monitors for SNR values (for devices) that are outside a two-day moving average. Warning, Critical, Fatal Monitors the levels of SNR for devices. Warning, Critical, Fatal RSSI Level SNR Level Severity NOTE — Some of the predefined rules are disabled by default, allowing you to enable the ones you need for your environment. 41 PulseNET Administration Guide Rules and Notifications There are two ways to navigate to the Rules and Notifications dashboard. The first way, open to Administrators only, is through the Manage Device Groups dashboard. In the row corresponding to your selected device group or subgroup, click the Edit icon in the Rules/Notifications column. This takes you to the Rules and Notifications page. The second way, open to both Administrators and Operators, is through the Administration menu on the Summary dashboard. Click the Administration menu icon in the upper right corner and select Configure Rules from the dropdown menu. This takes you to the identical Rules and Notifications page. Rules are configured based on the device group or subgroup you choose, so having a well-thought-out organization structure working in tandem with carefully applied rules is an important part of efficiently monitoring your industrial communications environment. 42 PulseNET Administration Guide Rules and Notifications Enabling and Disabling Rules Enable rules so that alerts are triggered when problems arise in your monitoring environment. The alert appears as an icon beside the device name in the browser interface and, if configured, an email is sent to the user addresses associated with that rule. To enable a rule: 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the group in the list. In the same row as the desired group, in the Rules/Notifications column, click Edit. 3  On any of the tabs for specific types of rules, find the rule that you want to enable. 4  In the Enabled column for the desired rule, click the Disabled icon to toggle the rule on. 5  In the confirmation dialog box, click Yes. The rule is enabled. Multiple severity rules can have different thresholds so that you are notified when certain conditions are met. Once a rule is enabled, define the required thresholds (see Configuring Rule Thresholds below) and enable email notifications if desired. To disable a rule: 1  In the Enabled column for a rule, click the Enabled icon to toggle the rule off. 2  In the confirmation dialog box, click Yes. The rule is disabled. 43 PulseNET Administration Guide Rules and Notifications Configuring Rule Thresholds Most PulseNET Multiple Severity Rules have four thresholds: fatal, critical, warning, and normal. You can define the thresholds for an enabled rule so that PulseNET sends alerts when your required thresholds are met on the devices you are monitoring. To configure the thresholds for a rule: 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the group in the list. In the same row as the desired group, in the Rules/Notifications column, click Edit. 3  On the PulseNET Multiple Severity Rules tab, find the rule you want to define. 4  In the Edit column for the desired rule, click Edit. 5  In the table provided, click the value that you want to edit. The value becomes highlighted. NOTE — Some rules have trigger delay values. Altering these values may affect how alerts are raised. For detailed information about this interdependency, see Trigger Delay Values below. 6  Type the new value. 7  When you are finished configuring threshold values, click OK. Trigger Delay Values A trigger delay value is the number of consecutive times a certain threshold must be met to cause a rule to raise the corresponding alert ( fatal, critical, warning). Example For a Mercury 3650 remote, the signalto-noise ratio (SNR) change for the warning alert is set to 2 dB with a trigger delay value of 4. This means that if the 2 dB threshold is met four collections in a row for that device, a warning alert is raised. The collection frequency for the performance information of the device is set to every 5 minutes. 44 PulseNET Administration Guide Rules and Notifications With this configuration, an SNR change warning alert, if required, will be raised 15 minutes after the first time the 2 dB threshold is observed by PulseNET. If you change the collection frequency to 1 hour, an SNR change warning alert, if required, will be raised 3 hours after the first time the 2 dB threshold is observed. If the collection frequency remains set to every 5 minutes, and you change the trigger delay value to 6, an SNR change warning alert, if required, will be raised 25 minutes after the first time the 2 dB threshold is observed. Enabling Email and SNMP Trap Notifications for Rules Predefined PulseNET rules are configured by default not to send notifications when a certain threshold is met. Notifications can be enabled, however, even if the rule is not enabled. Email and SNMP Trap notifications can be enabled for any desired severity level while you are editing a specific rule, as shown in the image above. Simply check the box to Enable Email or to Enable SNMP Trap. If you would like a summary view of the thresholds that will send email or SNMP notifications for all of the available rules, you can display them by following the steps below. To show the Email and SNMP columns in the Rules and Notifications table: 1  Navigate to Administration > Manage Device Groups. 2  On the Manage Device Groups dashboard, find the group in the list. In the same row as the desired group, in the Rules/Notifications column, click Edit. 3  On the Rules and Notifications view, click the Customizer icon. 4  In the dialog box, select Email and SNMP, then select the severity thresholds ( fatal, critical, warning, and normal) that you want to appear in the Rules and Notifications table. At least one threshold must be selected. 5  Click Apply. The column showing the selected thresholds is added to the table. The icons then show you which thresholds have email or SNMP notifications enabled. 45 Managing Reports 7 Reports are a convenient way to share data about your monitored environment with others in your organization. A report can also provide a quick, high-level perspective on your data. If you have the appropriate permissions, you can generate a report using one of the predefined report templates provided by PulseNET or create custom report templates to tailor the content and presentation of each report to suit your needs. The Reports dashboard is your starting point for working with reports. Use it to create and schedule reports and to access the Manage Reports dashboard and Audit Log dashboard. This dashboard provides links for you to accomplish the following tasks: • Generate a report — this allows you to run a report immediately • Schedule a report — this allows you to run a report at a scheduled time • Manage reports — this allows you to disable or re-enable a report and edit, download, and delete reports • Build custom report templates — this allows you to create new report templates that can be selected by other users • View Audit Information — this allows you to view all of the separate audit logs generated by PulseNET in one consolidated report Reports can be generated so that they run immediately, or they can be scheduled so that they run regularly in the future. Both Administrators and Operators can perform basic reporting actions, but only Administrators can create custom templates and view the consolidated audit log. For detailed information about generating, scheduling, and managing reports, see the “Working with Reports” section in the User Guide. Building Custom Report Templates Administrators, as well as Operators who are device group owners of the Production and Staging root groups, can create custom report templates. PulseNET Administration Guide Managing Reports To build a custom report template: 1  Navigate to Administration > Reports > Build a Custom Report. A new report (for example, My Report 1) automatically opens. 2  Click Add view. In the dialog box that appears, select the input data to include from the list in the left-hand pane (for example, PN Operation > All Remotes). Once you have chosen the input data you want to include from the left-hand panel, the View Styles available for that type of input data are enabled at the right. Not every view is available for every type of input data. • Choose Metric View to arrange the data in a chart, gauge, or list. • Choose Table View to arrange the data in a table. This style is only available when you choose multiple objects to gather data from, such as All Remotes. • Choose Property View to arrange the data as a label or name-value list. This style is only available when you choose an individual object to gather data from, such as a specific remote. • Choose View Template to arrange the data in a pre-defined template. Select the view style best suited to displaying your data. The Table View style is recommended because it tends to present the data most efficiently in report form. Click Next, and follow the instructions contained in the chart below for your selected style. 47 PulseNET Administration Guide Managing Reports Metric View Show metrics associated with the selected data as a chart, gauge, list, or other graphic a From the Select Metric(s) list, select one or more metrics to be represented. b At the bottom left, select the type of chart, gauge, or list you wish to use. A preview of how the data will be displayed is shown at the right. c Click the Common tab. If desired, add a title for the view or adjust the height of the title. d Click the Metric Labels tab. If desired, select a metric label or parent label from the lists provided. Depending on your selections, there may be only one metric in the list. e Click the Options tab. If desired, set the available metric view parameters. For descriptions of the available parameters, see the Appendix. Click Finish. Table View Choose metrics to show as columns in a table where each row is an element in the list. a From the list, select the properties that you want to appear in the view. Click Next. b Configure the order of the columns and the label and alignment for each column, and select a renderer for the data for each metric. Click Next. c Preview the data table. To make changes, click Previous. Otherwise, click Next. d Specify rules to filter the selected data. Click Finish. Property View Display properties of the selected data as a label or name-value list a From the list at the left, select the properties you want listed in the view. b Select the view style (Name-Value vs. Property Renderer) for displaying the properties in the view. Click Next. c Configure the display order and renderer and add a title for the view, if desired. Click Finish. View Template Choose an existing view template that uses the selected data as the input. a From the list, select a pre-defined report view template. A preview of how the data will appear is shown at the right. b Click the Common tab and add a title for this view, if desired. Click Finish. Your custom view is added to the report. To add another view to your report, repeat the process described above. You can also use drag-and-drop functionality to add more views. 1  On the Action Panel, click the Data tab. 2  From the list, select a data item for the input data and drag it into the custom report workspace. A popup appears with three of the following four view style choices—Select metrics, Create a table, Select properties, and Select a view—that correspond to the view styles described above. 3  Select the view style for displaying the properties in the view. 48 PulseNET Administration Guide Managing Reports 4  In the Create view dialog box that appears, follow the steps given above for your selected view style. Managing Your Custom Template To change the name of your custom template: 1  Click the name of the report at the top of the custom report workspace. 2  Type a new name and hit Enter on the keyboard. To add text to the first page of your custom template: 1  Click Add text. 2  In the dialog box that appears, select a style for the text from the dropdown list. 3  Type your text in the field provided. 4  To save your changes, click OK. To add a header or footer: 1  Click the Header placeholder bar near the top of the custom report workspace or the Footer placeholder bar near the bottom of the workspace. 2  In the dialog box that appears, define your header or footer using the controls provided. • Click the left, center, and/or right fields provided and add your text • Add variables using the controls provided at the top of the dialog box 3  Click OK. To configure optional report properties: 1  Click Properties near the top of the custom report workspace. 2  In the Edit Properties dialog box that appears, you can: • Edit the name of the report • Define the relevant roles for the report • Define the roles allowed to see the report • Provide a descriptive tool tip message for the report • Provide a background image by linking to a valid URL, selecting an image from the tree provided, or uploading an image 3  Select the check box at the bottom if you want this report to be available for inclusion in other reports. 4  Change the page orientation of the report using the dropdown menu, if desired. 5  Click OK. 49 PulseNET Administration Guide Managing Reports Running and Scheduling Reports Using a Custom Template After a custom template is created, it is added to the list of templates available to all PulseNET users and can be used to run both immediate reports and scheduled reports. For information about generating, scheduling, and managing reports, see the “Working with Reports” section in the User Guide. Viewing Audit Information PulseNET automatically generates logs that contain information about the changes and system actions that are performed by PulseNET users to the monitored devices. Audit logs for specific tasks (such as adding and removing users or devices) are available for the following PulseNET components: • Users — this tracks the changes a specific user has made to the system and his or her login and logout times (see Managing Users) • Firmware — this tracks the dates and times firmware pushes were made and who initiated them (see Managing Firmware Images) • Device Groups — this tracks changes made within a specific device group (see Viewing the Audit Log) • Monitored Devices — this tracks changes to specific devices (see the Audit Log tab information in “Detail Views“ in the User Guide) These separate audit logs are gathered together into a single report on the View Audit Information dashboard. Each entry shows the date and time at which the operation was performed, the name of the user who initiated the operation, and the type of operation. To navigate to this dashboard, choose Administration > Reports > Audit Log. Clicking on the text in a particular row will generate a popup containing further information about that audit log. 50 8 Global Device Settings The Global Device Settings section of the Administration Menu describes how to configure PulseNET settings for SNMP, Dlink, and 4G data collection, manage data collection schedules, manage firmware images, and create free-form data fields. Some of these topics will be explained in chapters of their own here in this guide. Scheduling Device Data Collection After devices are authorized, they can be monitored by PulseNET. Administrators can schedule the frequency of data collection by device type. The Collection Management view lists the devices that PulseNET can monitor. To configure the data collection schedule for monitored devices: 1  Navigate to Management. Administration > Global Device Settings > Collection PulseNET Administration Guide Global Device Settings 2  On the Collection Management view, there are panels for each type of device. In the Schedule Configuration column of any panel, click Edit. 3  On the first page of the Schedule Data Collection wizard, specify the schedule type. • Day of Week: Schedule data collection by the day—for example, on Monday, Wednesday, and Friday of each week. • Day of Month: Schedule data collection by the date—for example, on the 5th, 17th, and 26th of every month. 4  Click Next. 5  If you chose Day of Week, select all of the days that you want configuration data to be collected for the devices, then click Next. 6  If you chose Day of Month, select all of the dates on which you want to collect configuration data for devices, then click Next. 7  Specify the time of day you want data collection to run. • Minutes: Select the minute of the hour for data collection. For example, select 15 to schedule collection to run 15 minutes after the hour. • Hours: Specify the hours for collection by selecting the check box beside the hours. For example, 7 means 07:00. • For example, if you select 15 for Minutes, and 2 for Hours, data is collected at 02:15 on the day of the week or the date of the month that you specified previously. 8  Click Finish. To specify the collection interval for Performance and Availability: 1  In the related column of the panel, click the existing interval value. 2  In the dialog box, type the interval. 3  Click Save. To disable the collection schedule for Dlink devices: NOTE — If you disable the collection schedule for Dlink devices, up-time is not collected. Therefore, soon after the device is authorized, the initial up-time value reported for the device no longer applies. 1  In the Collection Scheduler for Dlink Devices panel at the bottom right, in the Schedule Configuration column, click the Enable icon to toggle collection off. 2  In the confirmation dialog box, click Yes. The schedule for Dlink devices is disabled. The Schedule Configuration Enable icon changes to reflect the disabled status. 52 PulseNET Administration Guide Global Device Settings To re-enable schedule configuration for Dlink devices: 1  In the Collection Scheduler for Dlink Devices panel at the bottom right, in the Schedule Configuration column, click the Disable icon to toggle collection back on. 2  In the confirmation dialog box, click Yes. NOTE — If you disable the schedule for Dlink devices and then later enable it, the collection schedule returns to the default collection schedule. That is, any previous collection schedule you configured is not retained. Managing Firmware Images This section describes how to add firmware image versions to PulseNET and deploy images to monitored devices. Administrators, as well as Operators with the Firmware Push permission for a specific device group, can manage firmware images. Currently, firmware management is supported for Mercury and iNET devices only. Adding and Removing Images You must add new firmware images in order to upgrade the devices in your monitored environment. Only Administrators can add new firmware image versions. To add a firmware image: 1  Navigate to ware Images. Administration > Global Device Settings > 2  On the Manage Firmware dashboard, click Manage Firm- Add. 3  In the Add Firmware Image dialog box, click Choose File to select the image. Do not change the name of the image file that you download from GE. 4  Click OK. 53 PulseNET Administration Guide Global Device Settings To remove a firmware image: Administrators can remove all firmware images. Operators assigned the Firmware Push permission can remove images associated to devices within their assigned device groups only. 1  In the Manage Firmware table, select the 2  Click check box next to the Device Type name. Remove. Changing the Image State Images have an assigned state. When an image is added to PulseNET, the default state is New. Because images cannot be deployed in this state, you must change the image to a different state, according to the situation. Administrators, and Operators who have the Firmware Push permission, can view and change the firmware image state. To change the image state: 1  On the Navigation Panel, select Summary. 2  On the Summary dashboard, select the device group, click the icon, and select Firmware Push. Administration menu Additionally, Administrators can navigate to the Manage Firmware dashboard by clicking ages. Administration > Global Device Settings > Manage Firmware Im- 3  In the Manage Firmware table, find the device and click the value in the State column. 4  In the popup, select one of the options: • Accepted — The image is tested and ready to be deployed to multiple devices at the same time • Obsolete — The image is outdated because a newer image version is available • Staging — The image can be individually deployed and tested on devices (after testing is complete, change the image state to Accepted) 5  Click OK. When you change the image state to Staging or Accepted, the Candidate Devices column is populated with the number of devices that are eligible for upgrade to the new firmware version. Operators with the Firmware 54 PulseNET Administration Guide Global Device Settings Push permission see candidate devices that are contained in their associated device groups only. Deploying Images to Devices Firmware images can be deployed if candidate devices are detected for the image. Administrators can deploy all firmware images. Operators who have the Firmware Push permission can deploy images to devices within their assigned device groups only. To deploy an image to a device: 1  On the Navigation Panel, select Summary. On the Summary dashboard, select the device group and then click the Administration menu icon and select Firmware Push. Administrators can deploy firmware images to all candidate devices, not just devices associated to a specific device group, through the Manage Firmware dashboard. Click Administration > Global Device Settings > Manage Firmware Images. 2  In the Manage Firmware table, click the value in the Candidate Devices column of the image that you want to deploy. NOTE — If there are no candidate devices, check the value in the State column. The image state must be set to Staging or Accepted to see candidate devices. For more information about image state, see Changing the Image State. If the image version is lower than the firmware version on either image slot on the device, the device is not displayed as a candidate for upgrade. 3  On the first page of the Deploy Firmware wizard, complete the following steps: • Select the check boxes beside the devices that you want to deploy the new firmware version to. To select all of the devices, click Select All. • In the Current Image columns of the table, you can see the active image that the device is booting from and the current firmware version on the device. The new firmware version deployment defaults to the inactive image. When firmware deployment completes, the device boots automatically from that image. If you want to change the image side that the firmware is deployed to, or change the 55 PulseNET Administration Guide Global Device Settings current active image, click Edit and select the alternate image. Be aware that the device reboots after firmware image deployment or when the active image is changed, and a configuration data collection automatically begins. • To receive an email notification when the firmware upgrade completes, select Notify me on completion. If the check box is dimmed, your email address is not configured. Operators must have an administrator add the correct email address to their user profile, which can be done by navigating to Administration > System Configuration > Configure Email Settings. If the Notify me on completion check box is still disabled, return to Configure Email Settings and re-configure the email server settings. For more information, see Configuring Email Settings. 4  Click Next. 5  On the second page of the Deploy Firmware wizard, select the SNMP community string or credential to be used to deploy the image. If a community string is used, ensure that the correct version—V1 or V2—is selected. Only Write credentials are used so that device configuration changes can be made. The SNMP community string or credential is device-specific. Only one SNMP community string or credential is required. 6  Click Finish. 7  In the Firmware Upgrade Progress table, view the status of the upgrade. Select Auto Remove Completed Items to remove the upgraded instances from the table when their cycle is complete. Be aware that Auto Remove Completed Items is a global setting. If selected, all completed firmware upgrade instances are removed in all device groups. Items that cannot complete because of errors remain in the table until the next PulseNET service restart. During the firmware upgrade, devices automatically reboot with the new version. If you selected Notify me on completion, an email is sent to you and the device group owners when the upgrade completes. 56 PulseNET Administration Guide Global Device Settings To verify the upgrade, you can navigate to the Configuration tab on the Device Detail View and validate the firmware version. Viewing Audit Information for Firmware Images To see changes to a firmware image, check the image audit log. To view the audit log: 1  On the Navigation Panel, select Summary. On the Summary dashboard, select the device group. Click the Administration menu icon and select Firmware Push. Administrators can also navigate to the Manage Firmware dashboard by clicking Administration > Global Device Settings > Manage Firmware Images. 2  In the Manage Firmware table, find the image and click View Audit in the Audit column. Each log entry shows you the date and time at which an operation was performed, the name of the user who initiated the operation, and the operation type. A log entry is created when an image is added, removed, or deployed to a device, when the image state is changed, or when the device image is switched. Using Free-form Data Fields You may want to store device information that PulseNET does not collect. For that purpose, you can create up to ten custom free-form data fields. To create a free-form data field: 1  Navigate to Settings > 2  Click Administration > Global Device Free-form Data Field Configuration. Add. 3  In the New Free-form Data Field dialog box that opens, type a label for the field. 4  If you want the label and information to be searchable by PulseNET global search, select the Searchable check box. For information on global search, see “Using Global Search” in the User Guide. 57 PulseNET Administration Guide Global Device Settings 5  If you want the field to be visible as a column in the Summary view for applicable devices, select the Visible in Summary View check box. For information on the Summary view, see the “Working with PulseNET“ section of the User Guide. 6  Click Add. The new field is added to the Free-form Data Field tab on the Device Detail View for every monitored device and, if you selected the Visible in Summary View check box, as a column in the Summary view for applicable devices. To edit a free-form data field: 1  Navigate to Administration > Field Configuration. 2  Select the 3  Click Global Device Settings > Free-form Data check box for the free-form data field(s) you want to edit. Edit. 4  In the Edit Free-form Data Fields dialog box that opens, edit the label for a field by clicking the present label and typing over it. 5  If you want the label and information to be searchable by PulseNET global search, select the Searchable check box. If not, clear that check box. For more information, see “Using Global Search” in the User Guide. 6  If you want the field to be visible as a column in the Summary view for applicable devices, select the Visible in Summary View check box. If not, clear that check box. For information on the Summary view, see the “Working with PulseNET” section in the User Guide. 7  Click Save. Fields that were created by the Administrator will become available for Operators to edit on the Free-form Fields tab in the Device Detail view for every device in the network. If the Administrator selected Visible in Summary View, then that column will be available in the Summary table as well. 58 PulseNET Administration Guide Global Device Settings To delete a free-form custom field: 1  Navigate to Administration > Field Configuration. 2  Select the 3  Click Global Device Settings > Free-form Data check box for the free-form data field(s) you want to delete. Delete. 4  Confirm that you want to delete the free-form data field(s). The fields are deleted from the PulseNET browser interface. 59 9 Managing Dlink Devices Use the information in this chapter to configure your environment for Dlink monitoring. To monitor Dlink devices, master seeds must be added and settings must be defined so that the devices can be discovered and authorized. Information on discovering and authorizing Dlink devices is included in the User Guide, since these are tasks both Administrators and Operators with the appropriate permissions can handle. For information on these basic tasks, see the “Device Administration” section in the User Guide. Adding Dlink Master Seeds Identify the Dlink devices you want to monitor with PulseNET. When you add the device information, you also define some of the discovery and data collection settings for that device. After you add master seeds, you can discover the device and authorize it for monitoring. To add a Dlink Master Seed: 1  Navigate to uration. Administration > 2  In the Seeded Master Settings table, click Global Device Settings > Dlink Config- Add. 3  In the dialog box, enter the IP address and port for the terminal server associated with the master. 4  If you want passive discovery to be the default discovery method for this master, leave the Passive Discovery check box selected. Clear the check box if you want active discovery to be the default. Be aware that the choice between active and passive discovery can significantly affect the length of time that the discovery process takes and the impact that the discovery process has on your network. For more information about passive and active discovery, see “Discovering Dlink Devices” in the User Guide. PulseNET Administration Guide Managing Dlink Devices 5  In the Passive Collection Repeat Interval box, type the value for the time gap between making passive requests for data collection. For example, if the value is 700, a passive request is sent every 700 milliseconds until the request times out. The system resets the timeout value if it receives a response from any new devices before timing out. Values greater than 250 milliseconds are supported. The request timeout length is set in the Global Advanced Dlink Settings. See Changing Global Advanced Dlink Settings below. 6  Leave the Sleep Mode Network check box selected if the radio network is in sleep mode. Clear the check box if the radio network is not in sleep mode. 7  Click Save. If the Sleep Mode Network check box was selected, a warning dialog box appears. Click Continue. 8  The master seed is added. Now you can discover devices. See “Discovering Dlink Devices” in the User Guide. Editing Dlink Master Seed Settings To edit Dlink master seed settings: 1  In the Master Seed Settings table, click the IP address of the terminal server associated with the master seed for which you want to edit settings. 2  In the dialog box, edit the master seed settings. 3  Click Save. Deleting Dlink Master Seeds Master seeds cannot be deleted if they are parents of devices being monitored by PulseNET. To delete a Dlink master seed: 1  In the Master Seed Settings table, select the ter seed that you want to delete. check box that corresponds to the mas- The Delete button becomes enabled. 2  Click Delete. Changing Global Advanced Dlink Settings Dlink settings can be applied on a global level or to individual authorized masters. The global settings contain the default values that are used when masters are first autho- 61 PulseNET Administration Guide Managing Dlink Devices rized, or until the settings are changed for the individual master. For more information about changing the settings for individual masters, see “Defining Data Collection on Dlink Networks” in the User Guide. To change the advanced Dlink settings values: 1  Click the advanced Dlink settings link at the bottom of the Dlink Configuration view. 2  In the Dlink Advanced Configuration dialog box, make changes to one or more of the parameter settings. 3  Click Save. The parameters available in the advanced Dlink settings view are described in the following table. These make global changes to all Dlink devices in your network. Parameter Dlink Active Monitoring Request Timeout Dlink Active Discovery Request Timeout Dlink Passive Discovery Request Timeout Dlink Active Monitoring Request Max Attempts Dlink Active Discovery Request Max Attempts Definition Default The length of time the system waits for a device to respond to a Dlink monitoring request. 2000 ms The length of time the system waits for a device to respond to a Dlink active discovery request. 2000 ms The length of time the system waits for a device to respond to a Dlink passive discovery request. 30000 ms The number of times the system attempts a monitoring request. 3 The number of times the system attempts a discovery request. 3 62 PulseNET Administration Guide Managing Dlink Devices Dlink Worker Threads The number of threads the system uses for Dlink. This value needs to be increased as the number of monitored devices increases. Additional threads consume CPU and memory, so use caution when you increase this value. 10 Dlink Use Passive Discovery The type of discovery (passive or active) that the system uses when communicating with a Dlink device directly, rather than through a master seed. (Note: device firmware must support passive discovery.) Not selected The lowest unit address in the range of unit addresses the system will search when performing discovery. 0 The highest unit address in the range of unit addresses the system will search when performing discovery. 9999 The number of additional times, in succession, that you want the system to repeat the discovery. 2 Dlink Passive Discovery Repeat Intervals The time gap between making passive requests. (For example, if the value is 700, a passive request is sent every .7 seconds until the request times out.) Values greater than 250 milliseconds are supported. 700 ms Dlink Active Request Gap The length of time the system waits between making active requests for data. 2000 ms DLink Sleep Mode Discovery Wakeup Gap DLink Sleep Mode Discovery Wakeup Iterations DLink Sleep Mode Discovery Timeout The length of time the system waits between sending wakeup messages to a device in sleep mode during discovery. 500 ms The number of wakeup messages the system sends to a device in sleep mode during discovery. 20 The length of time the system waits for a device to respond after sending a discovery request. 100 ms DLink Sleep Mode Discovery Sleep Inhibit Timeout The maximum length of time the system keeps a sleep-mode Dlink network awake for discovery. The system wakes the network again if discovery has not finished in this amount of time. 655350 ms DLink Sleep Mode Monitoring Wakeup Gap DLink Sleep Mode Monitoring Wakeup Iterations DLink Sleep Mode Monitoring Timeout The length of time the system waits between sending wakeup messages to a device in sleep mode during discovery. 500 ms The number of wakeup messages the system sends to a Dlink device in sleep mode when doing discovery. 20 The length of time the system waits for a Dlink device to respond after sending a collection request. 100 ms DLink Sleep Mode Monitoring Sleep Inhibit Timeout The maximum length of time the system keeps a sleep-mode device awake to collect data. The system wakes the device again if the collection has not finished in this amount of time. 655350 ms Dlink Connection Type The type of connection PulseNET uses to communicate with Dlink devices: either Raw TCP or Telnet. Raw TCP Dlink TCP Port The port the system uses when communicating with a Dlink IP device directly, rather than through a master seed. 9999 ICMP Timeout The length of time the system waits for an IP device to respond to an ICMP request. 5000 ms HTTP Timeout The length of time the system waits for an IP device to respond to an HTTP request. 5000 ms Dlink Active Discovery Min Unit Address Dlink Active Discovery Max Unit Address Dlink Passive Discovery Repeats 63 10 Managing SNMP Devices To monitor SNMP devices, credentials and settings must be defined and the devices must be discovered and authorized. Use the information in this chapter to configure your environment for SNMP monitoring. Information on discovering and authorizing SNMP devices is included in the “Device Administration” section of the User Guide. Managing SNMP v1 or v2c Community Strings There are two default community strings: public (read-only) and private (write). Custom community strings can also be added. To add an SNMP v1 or v2c community string: 1  Navigate to uration. Administration > Global Device Settings > 2  In the SNMP v1 and v2c Community Strings table, click SNMP Config- Add. NOTE — The Add button is dimmed if neither SNMP v1 nor SNMP v2c are selected for use in the advanced SNMP settings. See Defining Advanced SNMP Settings. 3  In the dialog box, type a community string name. 4  Select Read Permission, Write Permission, or both. To discover MDS entraNET devices, you must have at least one Write credential defined so that remote devices can be discovered from the access point. To change the permission on an existing community string, click the value in the Permission column. In the dialog box, select the permission. 5  Click Save. To delete an SNMP v1 or v2c community string: 1  In the SNMP v1 and v2c Community Strings table, click the check box next to the community string that you want to delete. The Delete button becomes enabled. PulseNET Administration Guide Managing SNMP Devices 2  Click Delete. Alternatively, click Delete in the row for the community string you want to delete. NOTE — Community strings cannot be deleted if they are actively being used to manage devices. Managing SNMP v3 Credentials To add SNMP v3 credentials: 1  Navigate to uration. Administration > 2  In the SNMP v3 Credentials table, click Global Device Settings > SNMP Config- Add. The Add button is disabled if SNMP v3 is not selected for use in the advanced SNMP settings (see Defining Advanced SNMP Settings). 3  Type the user name that will be used for authentication. NOTE — It is not supported to have multiple SNMP v3 credentials with the same user name but different passwords. 4  Select Read Permission, Write Permission, or both. To discover MDS entraNET devices, you must have at least one Write credential defined so that remote devices can be discovered from the access point. To change the permission on an existing credential, click the value in the Permission column. In the dialog box, select the permission. 5  Select a Security Level: • No authentication and no privacy — the identity of the sender is not verified • Authentication and no privacy — the identity of the sender is verified, but the information is not encrypted • Authentication and privacy — the identity of the sender is verified and the information is encrypted 65 PulseNET Administration Guide Managing SNMP Devices 6  If the Security Level that you selected requires authentication, specify an authentication protocol and passphrase (i.e., the password of the specified user name). 7  If the Security Level that you selected requires privacy, specify a privacy protocol and passphrase. The passphrase is the encryption key. 8  Click Save. To edit SNMP v3 credentials: 1  In the SNMP v3 Credentials table, click the user name that corresponds with the SNMP v3 credentials that you want to edit. 2  In the dialog box, edit the credentials. 3  Click Save. To delete SNMP v3 credentials: 1  In the SNMP v3 Credentials table, click the check box next to the set of credentials that you want to delete. The Delete button becomes enabled. 2  Click Delete. Alternatively, click Delete in the row for the set of credentials that you want to delete. NOTE — Community strings cannot be deleted if they are actively being used to manage devices. After SNMP credentials are defined, you can use the credentials to run an SNMP discovery to discover and authorize devices for monitoring. For more information, see the “Device Administration” section of the User Guide. Defining Advanced SNMP Settings To configure advanced SNMP settings: 1  Navigate to uration. Administration > Global Device Settings > SNMP Config- 2  At the bottom of the SNMP Configuration view, click Advanced SNMP settings. The Advanced SNMP Settings dialog appears, allowing you to configure the following parameters: Parameter Definition Default SNMP Usage The version of SNMP that the system uses for communication. Select all the versions that you want the system to use. All SNMP Target Port The port used for SNMP communication. 161 66 PulseNET Administration Guide Managing SNMP Devices SNMP Timeout The length of time the system waits for a device to respond to an SNMP request. 7000 ms ICMP Timeout The length of time the system waits for a device to respond to an ICMP request. 5000 ms SNMP Worker Threads The number of threads that the system uses for SNMP. You must increase this value as the number of devices that the system is monitoring increases. Additional threads consume CPU and memory, so use caution when you increase this value. 50 ICMP Worker Threads The number of threads that the system uses for ICMP. You must increase this value as the number of devices that the system is monitoring increases. Additional threads consume CPU and memory, so use caution when you increase this value. 50 Disable Auto Firmware Upgrade Select if you do not want the access point to automatically push firmware upgrades to its connected remotes. If this parameter is selected, you must explicitly upgrade the firmware version on remote devices. Selected Migrating Devices between Strings or Credentials To migrate devices from one community string or set of credentials to another: 1  Navigate to uration. Administration > Global Device Settings > 2  Find the community string or credential from which you want to migrate devices, and click the value in the Managed Devices column. 3  In the Migrate Credential Wizard, select those check boxes beside the devices that you want to migrate. To select all of the devices, click the box at the top of the column. check 4  Click Next. 5  Select a destination community string, a set of credentials, or a new SNMP version. 6  Click Finish. PulseNET will begin using the new SNMP credentials to talk to the devices. SNMP Config- 67 Managing 4G Devices 11 Use the information in this chapter to configure your environment for Airspan Air4G base station monitoring. The following topics will help you configure communication parameters for the element manager and discover and authorize devices for monitoring. PulseNET communicates with the element manager for monitoring Air4G base stations. Air4G base stations that have Mercury 1800 subscribers can be monitored in PulseNET. Air4G remotes are currently not supported. Configuring 4G Interfaces Configure communications parameters for the element manager. Provide the settings for the web services and web portal interfaces. To define the settings for the element manager: 1  Navigate to tion. Administration > Global Device Settings > 2  On the 4G Configuration dashboard, click Configure 4G Interfaces. 3  In the Web Services Interface section of the dialog box that appears, provide the required information for the SOAP interface of the element manager. This tells PulseNET how to communicate with the element manager. • Type the URL for the element manager • Type the Username to connect to the SOAP interface (typically the user name is wsadmin) • Type the Password for the user • If desired, change the SOAP call Timeout (the default is 10 seconds) 4G Configura- PulseNET Administration Guide Managing 4G Devices 4  In the Web Portal Interface section, provide the information for the element manager Web portal. • Type the URL for the element manager • Type the Username of the admin account for the element manager • Type the Password for the administrator account 5  Click Save. PulseNET is now configured to communicate with the element manager. Next, review the profiles and settings for the element manager. Defining Global Device Settings on the Element Manager The element manager can be administered directly through PulseNET after the web services and web portal interfaces are configured. On the 4G Device Configuration dashboard, click any of the settings in the three sections—Service Profiles, Software Management, and 16e BaseStation Profiles—to make changes to the element manager. Discovering Air4G Base Stations To monitor Air4G base station devices, the devices must be discovered and authorized. The SNMP discovery process is used to find Air4G devices. Ensure that SNMP credentials are defined before you run a discovery. 69 PulseNET Administration Guide Managing 4G Devices Adding Credentials To discover Air4G devices, both READ and WRITE credentials are required. There are two default community strings: public (read-only) and private (write). Custom community strings and v3 credentials can be added. For detailed instructions, see Managing SNMP Devices. After READ and WRITE credentials are defined, you can run an SNMP discovery for Air4G devices. For discovery details, see the “Device Administration” section of the User Guide. Defining Air4G Base Station Settings After devices are discovered, you can configure the settings for each Air4G base station device on the element manager. When you define a setting for a specific base station, it overwrites the global Air4G settings on that device only. For more information about defining global settings, see Defining Global Device Settings on the Element Manager. To configure settings for an Air4G base station device: 1  On the Summary dashboard, click the Summary tab. 2  Click the Access Points tile and click the Air4G device name in the table. 3  On the Detail View for the device, click the of these options from the list: Administration menu icon and select one • Edit Profiles — Manage the profiles on the Air4G base station • Manage State and Control — Manage the state of the device (for example, change the running state of the device or enable and disable some of the features of the device) • Software Upgrade — Manage the software images on the device The settings for that Air4G base station are updated. For information about scheduling data collection on Air4G devices and putting devices in maintenance windows, see Scheduling Device Data Collection. 70 System Configuration 12 PulseNET Administrators are responsible for configuring system settings. Some of these settings should be defined immediately after you log in to PulseNET for the first time. Others may need to be altered periodically as your monitoring system changes and grows. In this section, you can also find detailed steps for managing system schedules and enabling enhanced Google Maps functionality so that you can view device locations geographically. Email Settings When you log in to PulseNET for the first time, configure the email settings. Once the email properties are defined, you can request licenses from GE so that you can start monitoring devices. PulseNET also uses email messages to notify administrators and device group owners about system issues. See Configuring Email Settings. Enabling SNMP Trap Actions Enable SNMP trap actions if you want PulseNET to send alerts to external systems that can receive and display them. See Enabling Email and SNMP Trap Notifications for Rules. PulseNET must be told where to forward SNMP alerts. Once these settings are configured, you can clear and re-enter them at any time by using the Click here to clear your SNMP Trap settings link found on the System Configuration dashboard under the Configure SNMP Trap Settings option. PulseNET Administration Guide System Configuration To configure SNMP trap actions to forward alerts: 1  Navigate to Administration > SNMP Trap Settings. System Configuration > Configure 2  Select the appropriate SNMP Version: SNMP v1, v2c, or v3. 3  In the Target Addresses box, type the IP address(es) for the receivers that you want SNMP trap alerts to be forwarded to. Separate each IP address with a comma. 4  In the Target Port box, type the port number. Click Next. 5  If you selected SNMP v1 or SNMP v2c, type a community string that is valid on the receiving system and click Finish. 6  If you selected SNMP v3, supply the following information: • Type the User Name that will be used for authentication. PulseNET does not support multiple SNMP v3 credentials for the same user name. • Select the appropriate Security Level for your needs: No authentication and no privacy means that the identity of the sender is not verified. Authentication and no privacy means that the identity of the sender is verified, but the information is not encrypted. Authentication and privacy means that the identity of the sender is verified and the information is encrypted. 72 PulseNET Administration Guide System Configuration • If the Security Level that you selected requires authentication, specify an Authentication protocol and passphrase (which is the password of the specified user name). • If the Security Level that you selected requires privacy, specify a Privacy protocol (encryption key) and passphrase (which is the encryption key). • Click Finish. For information about setting SNMP trap actions for pre-defined rules, see Enabling Email and SNMP Trap Notifications for Rules. Managing Schedules This section describes how to manage schedules so that they can be used for scheduling reports and maintenance windows. PulseNET provides many predefined schedules. A schedule can contain one or more schedule items, each describing a recurrence pattern. For example, if you want a schedule to run indefinitely from 10:00 AM to 11:00 AM daily, and on the first day of the month from 8:00 AM to 6:00 PM, and also every Saturday from 11:00 AM to 4:00 PM in May, you can add a schedule item for each of these time spans to the schedule. If these predefined schedules do not meet your business needs, you can create custom schedules when you are working with reports or maintenance windows. An easy way to create a custom schedule is to copy an existing schedule that is close to what you want and make your customizations. When you create a new schedule, it becomes immediately available to all users for reports and maintenance windows. However, only PulseNET Administrators can create new schedules. For more information about creating custom schedules from scratch, see “Managing Custom Schedules” or “Creating Maintenance Windows” in the User Guide. To copy an existing schedule to create a new schedule: 1  Navigate to Schedules. Administration > System Configuration > Manage Default 2  In the list, find the schedule that you want to copy. In the same row as the schedule, click Copy Schedule. 3  In the confirmation dialog box, click OK. 4  In the Edit Schedule view, change the Schedule Name and Description/Comments. 5  Click Save. 6  To edit the details of the schedule, click Add Schedule Item. 7  Use the fields provided to specify new details for the schedule you are creating. 73 PulseNET Administration Guide System Configuration 8  When you are finished specifying the new details, click Save. The new details are added to the schedule. 9  To return to the Manage Default Schedules view, click Go to Schedule List. You can use these new schedules when you are scheduling reports and maintenance windows. See the “Working with Reports” section in the User Guide. Enabling Google Maps API Functionality To enable enhanced Google Maps API functionality and acquire access to additional support, you must obtain and add a Premier Client ID. For more information about Google Maps API options, see https://developers.google.com/maps/documentation/ javascript/usage#usage_limits. To add the Premier Client ID: 1  Navigate to Administration > gle Maps API Premier Client ID. System Configuration > Configure Goo- 2  In the dialog box, type the Client ID number. 3  Click Save. The Premier Client ID is now added to the configuration and enhanced Google Maps functionality is automatically enabled. Configuring Web Server Ports If during installation you chose not to run PulseNET in secure HTTPS-only mode but find you need to change this at a later date, follow the steps below. Be aware that you must have the administrator role to perform the following steps. When in HTTPS-only mode, the user must access the server using port 8443. When not in HTTPS mode, the user can access the server using either port 8080 (HTTP) or port 8443 (HTTPS). To set HTTPS-only mode: 1  Navigate to \config and edit the server.config file. 2  Find the server.console.httpsonly line and change the value from “false” to “true”. 3  Save the file and restart the PulseNET service. 74 PulseNET Administration Guide System Configuration To change the Web Server port number(s): 1  Navigate to \config and edit the server.config file. 2  Find the server.http.port line and change the value to your desired port number. Find the server.https.port line and change the value to your desired port number. 3  Navigate to \fglam\state\default\config and edit the fglam.config.xml file. 4  Find the tag and change the port value to the same value you used for the server.http.port above. 5  Save these files and restart the PulseNET service. 75 13 Getting Support If problems arise, diagnostic data can be gathered and saved as a collection of files called a support bundle. These support bundles can then be forwarded to the GE MDS Technical Support Department to aid in determining and correcting the problem. Each support bundle contains a diagnostic snapshot of the PulseNET Management Server and log files. PulseNET saves each support bundle as a ZIP file in the /support/ directory on the machine hosting the PulseNET Management Server. Generating a Support Bundle It is not difficult to generate a support bundle, but it may take some time, depending on the number of monitored devices in your network and the length of time the system has been monitoring those devices. To generate a support bundle: 1  Navigate to Administration > Support. 2  On the Support view, click Generate Support Bundle. The ZIP file is created in the /support/ directory on the PulseNET machine. 3  To download the new support bundle, click Download Now. The support bundles you generate are listed under Administration > Support > Manage Support Bundles. For information about managing support bundles, see Managing Support Bundles. Requesting Support You can request support through email. (If you require support and do not have Internet access, see the In Case of Difficulty section at the end of this guide.) To request support through email, first make sure you have configured your PulseNET email settings (see Configuring Email Settings). If you have not configured email set- PulseNET Administration Guide Getting Support tings, PulseNET opens the support request for you to send through an external email client. NOTE — If you are requesting support through an external email client and you want to attach a support bundle to the request, you must generate and attach the support bundle manually. To request support: 1  Navigate to Administration > Support dialog box appears. Support > Request Support. The Request 2  Type your customer number in the Access Code field. 3  Leave the Include Support Bundle check box selected if you want to include a support bundle. A support bundle is generated and included in the support request. 4  Leave the Create Support User check box cleared, unless the Support team requests that you select it. 5  Type an appropriate subject in the Subject field. 6  Type a description of the problem in the Body field. 7  Click Request Support Now. Your request for support is sent to the GE MDS Technical Support Department. Managing Support Bundles Generated support bundles are listed in the Manage Support Bundles view. From this view you can also generate new support bundles, download previously generated support bundles, and delete outdated support bundles. Downloading Generated Support Bundles To download a generated support bundle: 1  Navigate to Administration > Support > 2  In the table, find the generated support bundle and click or save the support bundle. Manage Support Bundles. Download. You can open Deleting Generated Support Bundles To delete a generated support bundle: 1  Navigate to Administration > Support > Manage Support Bundles. 77 PulseNET Administration Guide Getting Support 2  In the table, click the check box beside the name of the support bundle to enable the Delete button. 3  Click Delete. 4  In the confirmation dialog box, click Delete. The support bundle is removed from the table. Cartridge Information Clicking this link brings up a popup that lists all of the installed cartridge components of the PulseNET server. 78 Appendix 14 The following tables list and describe the Metric View parameters available to PulseNET Administrators when creating custom reports. Metric View Chart Options The options available depend on the type of chart you select. Parameter Use these settings as default Metric value Show one chart per metric Only show axis of selected metric (different charts will line up) Show thresholds for selected metric Description Options The configured settings are used as the default settings. Specifies the type of value to be displayed for one metric, or all metrics, in a chart. A separate chart is displayed for each metric. None, Average, Minimum, Maximum Only the axes for the selected metric are displayed. Check box If a metric has a threshold, it is displayed. Data is shown at both the start and Show data at both start and end of intervals. This applies only to end of intervals plot and area charts. Honor bounds (calibrated Sets the chart axes so that they do max, unit bounds) not go out of the chart boundaries. Specifies what you want a select On Select action to invoke. Displays the overall value for the set Show overall time range as a dashed line. Displays the minimum and maximum Show min/max as per interval. Displays the baseline minimum and Show baseline min/max as maximum. Check box Check box Check box Check box Check box Drilldown, Highlight Average, Min, Max Envelope, Marks, Lines Envelope, Marks, Lines PulseNET Administration Guide Device Groups Appendix Show standard deviation as Standard deviation multiplier Show Average Line Highlights a range per interval. Displays the high and low (that is, deviation from the average) values. Emphasizes the highest and lowest values. Envelope, Marks, Lines 1, 2, 3 Check box Metric View Gauge Options The options available depend on the type of gauge you select. Parameter Use these settings as default Indicator Size Bar Thickness Metric Value Source Description The configured settings are used as the default settings. Highlights a fluctuating value in your real-time application in a visually meaningful way. Determines the thickness of the bar. Specifies the metric value to be displayed, the current value or the average over the configured period. Options Check box Normal, Wider Thinner, Normal, Thicker Metric Current, Metric Period Metric View List Options The options available depend on the type of list you select. Parameter Description Show Sparkline The configured settings are used as the default settings. Displays a sparkline for each metric. Show Column For Displays the columns you select. Use these settings as default Options Check box Check box Check boxes for: Min, Average, Max, Sum, Baseline Min, Baseline Max, Standard Deviation 80 Index A Air4G Devices G Global Device Settings Adding credentials 70 Disabling collection schedule 52 Defining base station settings 70 Re-enabling collection schedule 53 Defining settings 68 Scheduling data collection 51 Global device settings 69 Specifying collection interval 52 C H Configuring Email Settings 16 Configuring Password Settings 25 D Device Groups Adding subgroups 33 Assigning existing users 34 Assigning user permissions 35 Decommissioning devices 37 Moving devices 37 Removing subgroups 34 Viewing assigned devices 36 Viewing audit log 38 Dlink Devices Adding master seeds 60 Changing global advanced settings 61 Deleting master seeds 61 Editing master seeds 61 F Firmware Adding images 53 Changing image state 54 High Availability Starting Linux 11 Starting Windows 11 Stopping Linux 12 Stopping Windows 11 L LDAP Configuring 27 Explanation of settings 28 Importing groups 30 JSSE 29 Licenses Deleting 18 Installing 17 Migrating devices 18 Order when authorizing 19 Replacement 19 Requesting 15 Logging in 12 R RADIUS Deploying image to device 55 Adding external users 31 Removing images 54 Enabling authentication 31 Viewing audit information 57 Free-form Data Reports Audit information 50 Creating fields 57 Building custom templates 46 Deleting fields 59 Managing custom templates 49 Editing fields 58 Running and scheduling 50 Rules and Notifications Configuring thresholds 44 Disabling rules 43 Email notifications 45 Enabling rules 43 Navigating to dashboard 42 Predefined rules 41 SNMP Trap notifications 45 U Users Changing passwords for 23 Copying 23 Creating 21 Expiring passwords for 24 Reconfiguring 22 Trigger delay values 44 Removing 24 S Updating roles 24 SNMP Devices Adding community strings 64 Adding v3 credentials 65 Defining advanced settings 66 Deleting community strings 64 Deleting v3 credentials 66 Editing v3 credentials 66 Migrating devices 67 Starting PulseNET Linux 10 Windows 9 Stopping PulseNET Linux 10 Windows 10 Support Cartridge information 78 Deleting support bundles 77 Downloading support bundles 77 Generating a support bundle 76 Requesting support 76 System Configuration Configuring SNMP Trap actions 72 Configuring web server ports 74 Enabling Google Maps API 74 Managing schedules 73 Setting session timeout for 26 Viewing audit information for 25 W Windows Service 12 Quest Copyright Notice © 2014 Quest Software, Inc. ALL RIGHTS RESERVED. Patents This product is protected by U.S. Patents #7,979,245 and #8,175,862. Additional patents pending. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc. Trademarks Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag and Follow, Vintela Single Sign-on for Java, vOPS, and vFoglight are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. For a complete list of Quest Software’s trademarks, please see http://www.quest.com/legal/ trademark-information.aspx. Other trademarks and registered trademarks are property of their respective owners. The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED, OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL, OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION, OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. Third Party Contributions MDS PulseNET contains some third party components. For a complete list, see License Credits below. If you have any questions regarding your potential use of this material, contact: About Quest Software, Inc. Established in 1987, Quest Software (Nasdaq: QSFT) provides simple and innovative IT management solutions that enable more than 100,000 global customers to save time and money across physical and virtual environments. Quest products solve complex IT challenges ranging from database management, data protection, identity and access management, monitoring, and user workspace management to Windows management. For more information, visit www.quest.com. About GE MDS Over two decades ago, GE MDS began building radios for business-critical applications. Since then, we have installed thousands of radios in over 110 countries. To succeed, we overcame impassable terrain, brutal operating conditions, and disparate, complex network configurations. We also became experts in wireless communication standards and system applications worldwide. The result of our efforts is that today, thousands of utilities around the world rely on GE MDS-based wireless networks to manage their most critical assets. Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com email: [email protected] The majority of GE MDS radios deployed since 1985 are still installed and performing within our customers' wireless networks. That’s because we design and manufacture our products in-house, according to ISO 9001, which allows us to control and meet stringent global quality standards. Refer to our web site for regional and international office information. Thanks to our durable products and comprehensive solutions, GE MDS is the wireless leader in industrial automation—including oil and gas production and transportation, water/wastewater treatment, supply, and transportation, electric transmission and distribution, and many other utility applications. GE MDS is also at the forefront of wireless communications for private and public infrastructure and online transaction processing. Now is an exciting time for GE MDS and our customers as we look forward to further demonstrating our abilities in new and emerging markets. As your wireless needs change, you can continue to expect more from GE MDS. We'll always put the performance of your network above all. Visit us at www.gemds.com for more information. GE MDS ISO 9001 Registration GE MDS adheres to the internationally-accepted ISO 9001 quality system standard. To GE Customers We appreciate your patronage. You are our business. We promise to serve and anticipate your needs. We will strive to give you solutions that are cost effective, innovative, reliable and of the highest quality possible. We promise to build a relationship that is forthright and ethical, one that builds confidence and trust. Data sheets, frequently asked questions, application notes, firmware upgrades and other updated information is available on the GE MDS Web site at www.gemds.com. Manual Revision and Accuracy This manual was prepared to cover a specific version of our product. Accordingly, some screens and features may differ from the actual version you are working with. While every reasonable effort has been made to ensure the accuracy of this guide, product improvements may also result in minor differences between the manual and the product shipped to you. If you have additional questions or need an exact specification for a product, please contact our Customer Service Team using the information at the back of this guide. In addition, manual updates can often be found on the GE MDS Web site at www.gemds.com. About End 2 End Technologies End 2 End (E2E) Technologies offers a unique combination of wireless communications and information technology expertise. We improve efficiency, reduce risk and lower the cost of industrial field operations via modernization and management of our customer’s wireless communications networks. From initial planning through lifecycle support we assist your team in adopting a wireless solution that keeps communication costs low while maximizing network reliability and performance. Visit us at www.e2etechinc. com for more information. In case of difficulty... If you have problems, comments, or questions pertaining to the MDS PulseNET application, please contact GE MDS via one of the methods below: Phone: 585-241-5510 Email: [email protected] Fax: 585-242-8369 Website: www.gemds.com License Credits MDS PulseNET contains several third party components using open source licenses (copies of which can be found at: http://www.quest.com/legal/third-party-licenses.aspx). Proprietary: • Dlink — Copyright GE MDS, LLC. • InstallAnywhere 8.0 — Common Public License 1.0 • MILLER-394729 Map 1.0 — Map Resources Extended Use License Agreement 1.0 Open Source: • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • [ini4j] 0.5 — Apache License 2.0 Annotations 9.0.1 — Apache License 2.0 ANTLR 2.2.7 — ANTLR License 2 ANTLR 2.2.7.6 — BSD License 4.4 ANTLR 3.1.3 — ANTLR License 3 Apache 2.0.5.4 — Apache License 1.1 Apache Commons 1.0 — Apache License 1.1 Apache Commons 1.1 — Apache License 1.1 Apache Commons 1.2 — Apache License 1.1 Apache Commons 2.4 — Apache License 2.0 Apache Commons Codec 1.4 — Apache License 2.0 Apache Commons IO 1.4 — Apache License 2.0 Apache Commons IO 2.0.1 — Apache License 2.0 Apache Commons Validator 1.4.0 — Apache License 2.0 Apache log4net 1.2.10 — Apache License 1.1 Apache POI 3.7 — Apache License 1.1 Apache Taglibs 1.1.0 — Apache License 2.0 Apache Velocity 1.5 — Apache License 1.1 args4j 2.0.16 — MIT License arsys-api 7.5 — Apache License 2.0 Axiom 1.2.12 — Apache License 2.0 Axis 1.4 — Apache License 2.0 Axis2 1.6.1 — Apache License 2.0 BCEL 5.0 — Apache License 1.1 BCEL 5.1 — Apache License 2.0 BeanShell 1.3.0 — GNU Lesser General Public License 2.1 Boost 1.33.1 — Boost Software License 1.0 Bouncy Castle 145 — Bouncy Castle 1.5 Codemodel 2.4 2 — Common Developer & Distribution License (CDDL) 1.0 com.oreilly.servlet 2008 — Artistic License 1.0 Commons Logging 1.1 — Apache License 1.1 commons-cli 1.2 — Apache License 2.0 commons-codec 1.7 — Apache License 2.0 commons-compress 1.2 — Apache License 2.0 commons-digester 2.1 — Apache License 2.0 commons-discovery 0.2 — Apache License 2.0 commons-httpclient 4.0 — Apache License 2.0 commons-httpclient 4.1.1 — Apache License 2.0 commons-io 3.1 — Apache License 2.0 commons-modeler 2.0.1 — Apache License 2.0 commons-net 3.2 — Apache License 2.0 commons-pool 1.2 — Apache License 1.1 DWR 2.0 rc2 — Apache License 1.1 • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • ehcache 1.3.0 — Apache License 2.0 ehcache 2.3.0 — Apache License 2.0 Ext JS 2.2 — Common Developer & License (CDDL) 1.0 FasterXML ClassMate 0.8.0 — Apache License 2.0 Findbugs 1.3.9 — GNU Lesser General Public License 2.1 FreeMarker 2.3.10 — BSD License 4.4 Ganymed SSH-2 for Java build 250 — Ganymed SSH-2 for Java License Geronimo 1.1 — Apache License 2.0 Geronimo 1.4 — Apache License 2.0 Gif89Encoder 1.0 — ACME Labs Freeware License 1.0 GlassFish javax.el — CDDL + GPLv2 with classpath exception Google Diff, Match and Patch 20110725— Apache License 2.0 google-collections 1.0 — Apache License 2.0 Granados 2.0.0 — Apache License 1.1 Groovy 1.5.7 — Apache License 1.1 Groovy 1.7.6 — Apache License 2.0 groovy-wslite 1.0.0 — Apache License 2.0 Gson 1.5 — Apache License 2.0 Guava 13.0.1 — Apache License 2.0 HBA API 2.2.1 — Storage Networking Industry Assoc (SNIA) License 1.1 Hibernate 3.2.4 sp1 — GNU Lesser General Public License 2.1 Hibernate Validator — Apache License 2.0 hybrid labs beautifier 1.1.7 — Apache License 1.1 Java SMI Parser — Apache License 2.0 javax.el-api — CDDL + GPLv2 with classpath exception javax.validation — Apache License 2.0 j-interop 2.03 — GNU Lesser General Public License 2.1 j-interop 2.08 — GNU Lesser General Public License 2.1 JACOB (Java Com-Bridge) 1.13 — GNU Lesser General Public License 2.1 JACOB (Java Com-Bridge) 1.15 M2 — GNU Lesser General Public License 2.1 JAX-WS 2.1.3 — Common Developer & Distribution License (CDDL) 1.0 JAXB 2.1.5 — Common Developer & Distribution License (CDDL) 1.0 JAXB 2.2.3u1 — Common Developer & Distribution License (CDDL) 1.1 jaxb-api 2.1 — Common Developer & Distribution License (CDDL) 1.0 jaxb-impl 2.1.3 — Common Developer & Distribution License (CDDL) 1.0 jaxen 1.1 — Apache License 1.1 JBoss 4.2.3_GA 2 — GNU Lesser General Public License 2.1 JBoss Logging — GNU Lesser General Public License 2.1 JCIFS 1.3.0 — GNU Lesser General Public License 2.1 JCIFS 1.3.12 — GNU Lesser General Public License 2.1 JCIFS 1.3.14 — GNU Lesser General Public License 2.1 JDOM 1.0 — JDOM License 1.11 jettison 1.2 — Apache License 2.0 Jetty 6.1.26 — Apache License 2.0 Jetty 7 — Eclipse Public License 1.0 Jibx 1.1 — BSD License 4.4 Jibx 1.2.2 — BSD License 4.4 Jibx 1.6a — BSD License 4.4 JRadiusClient 2.0.0 — GNU Lesser General Public License 2.1 Json-lib 2.2.1 — Apache License 2.0 Json.NET 3.5 release 8 — MIT License JSR-305 — BSD-style license jTDS SQL Server Driver 1.2 — GNU Lesser General Public License 2.1 JUnit 4.8.1 — Common Public License 1.0 JUnit 4.8.2 — Common Public License 1.0 Log4J 1.2.13 — Apache License 2.0 Log4J 1.2.14 — Apache License 1.1 Log4Net.dll 1.2.9.0 — Apache License 2.0 NpgSql 2.0.10 — NpgSql License 2.0.8 oAW 4.2 — GNU Lesser General Public License 2.1 OpenSymphony OSCore 2.2.7 — Apache License 1.1 OpenSymphony Quartz Scheduler 1.6.1— Apache License 1.1 OpenSymphony SiteMesh 2.2.1 — Apache License 1.1 OpenSymphony XWork 2.0.4 — Apache License 1.1 Perf4j 0.9.13 — Apache License 2.0 PostGreSQL 9.1 — PostgreSQL License Quartz Scheduler 1.6.5 — Apache License 2.0 RemCom 1.2 — BSD Simple License Rome 0.8 — Apache License 1.1 SAAJ 1.3 — Common Developer & Distribution License (CDDL) 1.0 Saxon-B 8 — Mozilla Public License (MPL) 1.1 Saxon-B 9.1 — Mozilla Public License (MPL) 1.0 saxpath 1.0 — Jaxen license SLF4j — MIT License slf4j - Simple Logging Facade for Java 1.6.1 — slf4j license • • • • • • • • • • • • • • • • SNMP4j 2.1.0 — Apache License 2.0 Spring Security 2.0.4 — Apache License 2.0 spring-framework 1.2.7 — Apache License 1.1 StAX 1.0 — Apache License 1.1 StringTemplate 4.0.2 — BSD-style license Struts Framework 2.0.14 — Apache License 2.0 Trilead SSH for Java Build 213 — Trilead SSH for Java Trilead SSH for Java build213-svnkit-1.3 — Trilead SSH for Java VI Java API 5.1 — BSD - VI Java VServ TCP/IP — Apache License 2.0 Wiseman 1.0 — Apache License 1.1 Woden 1.0 — Apache License 2.0 Woodstox 4.0.8 — Apache License 2.0 Xalan Java 2.7.1 — Apache License 1.1 XMLUnit 1.0 — BSD License 4.4 zlib 1.2.3 — zlib License 1.2.3