PulseNET Devices Guide€¦ · solve complex IT challenges ranging from database management, data...

Version 2.4

An Enterprise Management Tool for GE MDS Productsand other IP-Connected Devices

MDS 05-6571A01FEBRUARY 2013

Dev

ices

Gui

de

Quest Copyright Notice

© 2013 Quest Software, Inc. ALL RIGHTS RESERVED.

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.

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.

If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA 92656 www.quest.com email: [email protected]

Refer to our Web site for regional and international office information.

Patents

This product is protected by U.S. Patents # 7,979,245 and 8,175,862. Additional patents pending.

Trademarks

Quest, Quest Software, the Quest Software logo, Foglight, IntelliProfile, PerformaSure, Spotlight, StealthCollect, TOAD, Tag and Follow, Vintela Single Sign-on for Java, 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.

Third Party Contributions

MDS PulseNET contains some third party components. For a complete list, see the License Credits page in <INSTALLDIR>\docs\core\pdf.

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, user workspace management to Windows management. For more information, visit www.quest.com.

http://www.quest.com

mailto:[email protected]

http://www.quest.com

http://www.quest.com/legal/trademark-information.aspx

http://www.quest.com/legal/trademark-information.aspx

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.

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.

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.

Related Materials on the Internet—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.

Devices Guide February 2013 Version 2.4

Table of Contents

PulseNET Devices Guide 4

Introduction.........................................................................................................................................................................5

Working with Dlink Devices...............................................................................................................................................6

Adding Dlink Master Seeds ..................................................................................................................................................... 6

Changing Global Advanced Dlink Settings.............................................................................................................................. 7

Discovering Dlink Devices............................................................................................................................................................. 10

Running Dlink Discovery ....................................................................................................................................................... 11

Dlink Auto-discovery.............................................................................................................................................................. 13

Defining Data Collection on Dlink Networks.................................................................................................................................. 13

Collecting Data on Dlink Master Devices ...................................................................................................................................... 15

Working with SNMP Devices ...........................................................................................................................................21

Adding SNMP v1 or v2c Community Strings......................................................................................................................... 21

Adding SNMP v3 Credentials................................................................................................................................................ 22

Defining Advanced SNMP Settings....................................................................................................................................... 24

Migrating Devices from One Community String or Set of Credentials to Another ................................................................. 25

Discovering SNMP Devices .......................................................................................................................................................... 26

Ineligible Devices .................................................................................................................................................................. 29

Index ..................................................................................................................................................................................31

1

Introduction

This guide introduces you to the various types of devices that the system can monitor and provides the instructions necessary to set up the system to monitor those devices.

For information about:

• Dlink devices—see “Working with Dlink Devices” on page 6.

• SNMP devices—see “Working with SNMP Devices” on page 21.

For general navigation instructions, see the Quick Start Guide. For monitoring task workflow instructions, see the Monitoring Guide. For general administration task workflow instructions, see the Administration Guide.

2

Working with Dlink Devices

To monitor Dlink devices, master seeds must be added and settings must be defined so that the devices can be discovered and authorized. Use the information in this chapter to configure your environment for Dlink monitoring.

Adding Dlink Master SeedsIdentify the Dlink devices that 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 a master seeds, you can discover the device and authorize it for monitoring.

To add a Dlink Master Seed:

1 On the navigation panel, click Administration > Global Device Settings > Dlink Configuration.

2 In the Seeded Master Settings table, click Add.

3 In the dialog box, enter the IP address and port for the terminal server associated with the master seed.

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.

Warning: 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 “Discovery Methods” on page 10.


Chapter 2—Working with 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 5000, a passive request is sent every 5 seconds 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 is set in the Global Advanced Dlink Settings. For more information, see Changing Global Advanced Dlink Settings.

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 is selected, a warning dialog box appears. Click Continue.

The master seed is added.

Now you can use these settings to discover the Dlink devices. For more information, see “Discovering Dlink Devices” on page 10.

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 check box that corresponds to the master seed that you want to delete.

The Delete button becomes enabled.

2 Click Delete.

Changing Global Advanced Dlink SettingsDlink 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 authorized, 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” on page 13.



To change the advanced Dlink setting values:

1 Click the advanced Dlink settings link at the bottom-left 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 to make global changes to Dlink devices are described in the following table.

Parameter Definition Default

Dlink Active Collection Request Timeout (ms)

The length of time the system waits for a device to respond to a Dlink collection request.

2000

Dlink Active Discovery Request Timeout (ms)

The length of time the system waits for a device to respond to a Dlink active discovery request.

2000

Dlink Passive Discovery Request Timeout (ms)

The length of time the system waits for a device to respond to a Dlink passive discovery request.

30000

Dlink Active Collection Request Max Attempts (count)

The number of times the system attempts a collection request.

3

Dlink Active Discovery Request Max Attempts (count)

The number of times the system attempts a discovery request.

3

Dlink Worker Threads (count)

The number of threads the system uses for Dlink. This value needs to be increased as the number of devices the system is monitoring increases. Additional threads consume CPU and memory, so use caution when you increase this value.

10

Dlink Use Passive Discovery

The type of discovery that the system uses when communicating with a Dlink device directly, rather than through a master seed. The system uses either passive or active discovery.

Note For passive discovery of devices to run properly, the firmware revision on the devices must support passive discovery.

Not selected

Dlink Active Discovery Min Unit Address (count)

The lowest unit address in the range of unit addresses that you want the system to search through when performing discovery.

0



Dlink Active Discovery Max Unit Address (count)

The highest unit address in the range of unit addresses that you want the system to search through when performing discovery.

9999

Dlink Passive Discovery Repeats (count)

The number of additional times, in succession, that you want the system to repeat the discovery.

2

Dlink Passive Discovery Repeat Interval (ms)

The time gap between making passive requests. For example, if the value is 5000, a passive request is sent every 5 seconds 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.

5000

Dlink Active Request Gap (ms)

The length of time the system waits between making active requests for data to a Dlink device.

2000

DLink Sleep Mode Discovery Wakeup Gap (ms)

The length of time the system waits between sending wakeup messages to a Dlink device in sleep mode when doing discovery.

500

DLink Sleep Mode Discovery Wakeup Iterations (count)

The number of wakeup messages the system sends to a Dlink device in sleep mode when doing discovery.

20

DLink Sleep Mode Discovery Timeout (ms)

The length of time the system waits for a Dlink device to respond after sending a discovery request.

100

DLink Sleep Mode Discovery Sleep Inhibit Timeout (ms)

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

DLink Sleep Mode Collection Wakeup Gap (ms)

The length of time the system waits between sending wakeup messages to a Dlink device in sleep mode when doing discovery.

500

DLink Sleep Mode Collection Wakeup Iterations (count)

The number of wakeup messages the system sends to a Dlink device in sleep mode when doing discovery.

20

DLink Sleep Mode Collection Timeout (ms)

The length of time the system waits for a Dlink device to respond after sending a collection request.

100




Discovering Dlink DevicesUse discovery to find unauthorized devices in a monitored network.

Discovery Methods

There are two on-demand methods for finding unauthorized Dlink devices: active discovery and passive discovery. The difference in the methods is the way the network data is retrieved. The discovery method can be defined for each master device or defined globally for all master devices.

Review the methods to decide which method is most appropriate for discovering unauthorized devices on the network.

Active Discovery

Active discovery immediately requests the master device to return information from the remote devices in the network. This discovery is intrusive because it is prioritized over other application requests, so it disrupts normal operations on the network.

If you have devices that are kept in sleep mode, use active discovery to ensure that the devices require the least amount of wake time. When a device is discovered, it wakes up and sends information and then quickly returns to sleep mode.

Active discovery is the default discovery method.

DLink Sleep Mode Collection Sleep Inhibit Timeout (ms)

The maximum length of time the system keeps a sleep-mode Dlink device awake to collect data. The system wakes the device again if the collection has not finished in this amount of time.

655350

Dlink Connection Type The type of connection PulseNET uses to communicate with Dlink devices: either Raw TCP or Telnet.1

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 (ms) The length of time the system waits for an IP device to respond to an ICMP request.

5000

HTTP Timeout (ms) The length of time the system waits for an IP device to respond to an HTTP request.

5000

1 When PulseNET is configured to use a raw TCP connection, some terminal servers may not allow access through a Telnet connection to downstream Dlink devices for debugging purposes.




Passive Discovery

Passive discovery sends a broadcast message to the remote devices asking them to return data the next time your regular application polls them for information. Because of this, discovery information can take longer to receive, but the data retrieval is less intrusive to the network.

Note After a master is discovered and authorized, a persistent discovery is available for networks that are configured for passive collection. For more information, see “Dlink Auto-discovery” on page 13.

Defining the Discovery Method for a Master Device

Active discovery is the default discovery method. To change the default discovery method to passive discovery, update the Dlink Advanced Configuration settings. For more information, see “Changing Global Advanced Dlink Settings” on page 7.

To define passive discovery as the method for an individual master, select Passive Discovery when you add the master. For more information, see “Adding Dlink Master Seeds” on page 6. The discovery method can also be changed in the discovery wizard.

Decide which discovery method should be used for the master and then run the discovery.

Running Dlink Discovery

Caution When the Dlink discovery process starts, scheduled collections for previously authorized Dlink devices are suspended. The collections resume automatically when Dlink discovery completes.

Note The DType of the master device must be configured as Root.

To discover Dlink devices:

1 On the navigation panel, click Administration > Device Selection > Dlink Device Selection.

2 On the Dlink Discovery view, click Discover Dlink Devices.

3 On the Discovery Wizard, select the search type for discovering devices.

• Dlink Terminal Server via Seed File. Discover devices using references (seeds) to specific master devices. For each master, you can define whether active or passive discovery is used.

If you have a sleep mode network, this discovery method should be used.

• SD Radio via IP. Discover master devices (SD only), within a specified IP range. The global advanced Dlink setting defines whether active or passive discovery is used on the specified masters, and it can be changed in the discovery wizard.

4 Click Next.

5 If you select Dlink Terminal Server via Seed File, specify the Dlink master seeds to be used to discover devices. Otherwise, proceed to the next step.



The more master seeds you specify, the longer discovery typically takes to run.

Note If you do not see any Dlink master seeds, click the link at the bottom-left of the Discovery Wizard to add more. For information, see “Adding Dlink Master Seeds” on page 6.

6 If you select SD Radio via IP, specify the IP addresses to use for discovery. Otherwise, proceed to the next step.

a To specify an IP address, click Add IP and type the IP address.

b Optional—to change the discovery method, click the link to edit the global Dlink advanced configuration settings. Select or clear the Dlink Use Passive Discovery check box. Save your changes.

c To add the IP address, click Add.

d To specify an IP address range, click Add IP Range and type the IP range.

e Optional—to change the discovery method, click the link to edit the global Dlink advanced configuration settings. Select or clear the Dlink Use Passive Discovery check box. Save your changes.

f To add the IP address range, click Add. For example, an IP range of 10.10.120.1 - 10.10.121.2 adds the following IP addresses to the discovery: 10.10.120.1, 10.10.120.2, 10.10.121.1, and 10.10.121.2.

Add several IP addresses and IP address ranges, if necessary.

On the same screen of the Discovery Wizard, you are prompted to specify IP address exclude criteria.

g To specify an IP address in the Exclude Criteria table, click Add IP and type the IP address. Click Add. The IP address is added to the exclude criteria.

Note There is no need to exclude the IP addresses of devices that are already authorized; They are excluded by default. Click the Exclude Criteria Information icon to see a list of other IP addresses that are excluded by default.

h To specify an IP address range in the Exclude Criteria table, click Add IP Range and type an IP address range. Click Add. The IP address range is added to the exclude criteria.


Note The Discovery Wizard provides an estimate of the time it takes to perform discovery. This is a worst-case estimate based on the configuration of the advanced Dlink settings. For information about configuring advanced Dlink settings, see “Dlink Auto-discovery” on page 13.



7 Click Finish.

Your discovery request is processed.

Discovery Progress

Discovered devices that can be authorized appear in the list in the Discovery Progress pane. For instructions on how to authorize devices, see the Administration Guide.

During discovery, in the Discovery Progress pane at the top-right, you are notified about any decommissioned devices (that you might want to re-authorize) and about any monitored devices that have significant configuration changes.

If there are decommissioned devices that you want re-authorized, run a discovery to re-authorize them. Also, if you become aware that the configuration for a device has changed and you do not have the information you require to manually edit the configuration, you can run a discovery to acquire the new configuration information.

Dlink Auto-discovery

When PulseNET broadcasts a passive data collection request, all of the remote devices in the network receive the request, even unauthorized remote devices. If auto-discovery is enabled and an unauthorized remote device returns data, information about the device is collected and stored. Administrators can view and authorize these discovered remote devices at any time. To view the discovery results, navigate to Administration > Device Selection > Dlink Auto-discovery Selection.

If Auto-discovery is not enabled, the information about the unauthorized remote devices is discarded.

For information about enabling auto-discovery on Dlink masters see, “Collecting Data on Dlink Master Devices” on page 15. For more information about authorizing discovered devices, see the Administration Guide.

Defining Data Collection on Dlink NetworksThere are a numbers of factors that you should consider when planning data collections for monitored Dlink networks. You must identify the physical arrangement of the devices in your environment and their relationships to each other. Identify the way in which the applications are operating and polling over the network, and identify the type of network you have to determine how the data is collected. The following network types are defined below:

• Rarely Polled Networks

• Frequently Polled Networks

• Sleep Mode Networks



Rarely Polled Networks

Rarely polled networks typically have very little traffic most of the day with the exception of increased traffic at specific times. These networks are good candidates for active data collection. To collect actively, PulseNET requests data from each device directly and intrusively. Active data collection is fast and reliable, but it can impact other traffic that may be flowing through the device at the same time

However, if the network devices have limited battery power (for example, solar devices), use passive collection so that collection and polling occurs at the same time.

Key Considerations:

• Schedule

Use careful scheduling to control collection times and avoid impacting critical network operations.

You can independently schedule performance and configuration data collection to occur either on a frequency (for example, every 20 minutes), or on a pre-defined schedule.

• Request Timeout

The length of time that PulseNET waits for a response from the device. Remember to consider latency within your network because of the distances between devices, and also the number of gateways or repeaters that may be deployed.

• Request Gap

The length of time that PulseNET waits between data requests. A larger request gap means that it takes longer to retrieve all the data for that device, reducing the coherency of the data. However, a larger gap also reduces the intrusiveness of the data collection, relieving network performance. If you need to configure data collection using the frequency technique, select a larger request gap (1-2 seconds).

Frequently Polled Networks

Frequently polled networks typically have significant and frequent traffic on the network. Finding opportunities to schedule active collection may be difficult because active collection can be intrusive regardless of when it occurs. In these networks, passive data collection is recommended. When you use passive data collection, the performance data requests are sent with your application polling. As a result, PulseNET only receives responses when there is other traffic on the monitored network.

Key Considerations

• Data Freshness

PulseNET requests information from Dlink devices one item at a time. Responses are received only when application data is flowing on the network. If PulseNET needs to collect four data points at a time, and your application polls twice a day, it may take two days before a specific data value is refreshed.

• Timeouts



PulseNET assumes a Round-robin style of data collection. Timeouts should be configured to reasonably reflect the amount of delay expected between responses from different devices on your network. Timeouts that are too short results in incomplete data collection and the devices are incorrectly marked as unavailable.

If you have a layered gateway or repeater devices, multiple data collection cycles may be required before all the devices send back the requested performance data. With these configurations, the timeout value may need to be set as a multiple of your application polling frequency.

• Forgive Missed Polls

The value of this parameter determines how quickly a device is marked as unavailable. If a device misses the specified number of consecutive data collection requests, it is considered unavailable.

Sleep Mode Networks

Sleep mode networks typically have limited access to power. These networks are often configured to operate in a low-power mode most of the time, and are woken up periodically for scheduled activities. These networks require special handling in PulseNET and should be monitored with care. Active data collection is recommended for these networks.

Passive collection can be used if the sleep mode network is awake for regular intervals. For example, if devices are scheduled to be awake for 10 seconds and then sleep for 20 seconds. If you use passive collection, the Passive Collection Repeat Interval parameter value should be low enough that the request frequency catches the devices when they are awake.

Key Considerations

• Scheduling

Allow sufficient time between your application polling and the schedule for PulseNET data collection. Also, consider how the power is consumed for monitoring your devices. Ensure that you leave enough power available for normal application polling.

• Sleep Inhibit Timeout

This parameter determines how long the devices stay awake when PulseNET attempts to collect monitoring data. If this parameter is too short, some devices will go back to sleep before they have an opportunity to respond; these devices are then reported as unavailable. If the parameter value is too long, you may be consuming more power than necessary when monitoring data.

Collecting Data on Dlink Master DevicesUse the Configure Collection Wizard to define the collection type, the scope of data, and the collection schedule for performance and configuration data collection on individual Dlink master devices. You can also change the IP address and the port number of the master.



Configuration data collection can be requested at any time. For information about starting an immediate configuration data collection, see “Triggering a Configuration Data Collection” on page 21.

Default settings are predefined globally for master devices in the Dlink Advanced Configuration dialog. For more information see “Changing Global Advanced Dlink Settings” on page 7.

To define the settings for an individual master device:

1 On the Summary dashboard, click the Summary tab.

2 Click the Access Points tile and click the Dlink device name in the table.

3 On the Detail view for the master, click the Administrative Menu and select Configure Collection from the list.

4 In the Configure Collection Wizard, select the appropriate collection type for the master. Use the information in “Defining Data Collection on Dlink Networks” on page 13 to decide which collection type is appropriate for the Dlink network.

• Collect Passively

If you choose passive collection, you can also select to enable Auto-discovery.

When PulseNET broadcasts a passive data collection request, all of the remote devices in the network receive the request, even unauthorized remote devices. If auto-discovery is enabled and an unauthorized remote device returns data, information about the device is collected and stored. Administrators can view and authorize these discovered remote devices at any time. To view the discovery results, navigate to Administration > Device Selection > Dlink Auto-discovery Selection.

If Auto-discovery is not enabled, the information about the unauthorized remote devices is discarded.

• Collect Actively

If some of the remote devices on the network are in sleep mode, also select Sleep mode network.



5 Choose the collection size. To minimize the impact of data collection, which can be intrusive or slow, you can limit the amount of data collected.

Limited—a smaller selection of data is requested and returned for masters and remote devices. This is the default value.

Note The following data is not collected:

• Active Freq TX

• Active Freq RX

• Continuous Key

• Data Key Mode

• EMP

• RTU Simulator ID

• Seamless Setting

• Seamless Timer

Extended—all available data is requested and returned for masters and remote devices.

If you are deciding whether to choose limited or extended collection, the tables below provide examples of estimated passive collection times for each device.

Consider the polling interval for both performance and configuration data and the collection time. The polling interval for passive collection is determined by your enterprise application polling.

Performance Collection

Configuration Collection

Device type Polling interval (min) Limited collection (hr) Extended collection (hr)

x71x0x8x0TransNET

5 0.5 0.5

60 6 6

SD 5 0.3 0.3

60 3 3

Device type Polling interval (min) Limited collection (hr) Extended collection (hr)

x71x0x8x0TransNET

5 1.8 2.5

60 21.1 29.1

SD 5 1.7 2.4

60 19.1 27.1



6 To update the IP address or port number of the master device, beside Current Address, click Edit. Make the required changes and click OK.

7 Click Next.

8 If you chose Collect Passively, complete the following steps. Otherwise, continue to step 9.

a In the Response Gap field, type the value for the length of time, in milliseconds, that the system waits for the device to respond to the request. If the request timeout is reached, another request is sent.

b In the Forgive missed polls field, type the number of times a device can be unresponsive to consecutive requests before it is marked as unavailable.

c In the Passive Collection Repeat Interval box, type the delay time, in milliseconds, between passive requests.

For example, if the value is 5000, a passive request is sent every 5 seconds 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.

d In the Passive Poll Timeout box, type the length of time, in milliseconds, that the system waits for a poll to happen. The value is typically high because it is based on how often the network is polled.

e In the Auto-discovery Timeout box, type the length of time, in milliseconds, required for the poll to visit all of the devices on the network.

The box appears disabled if Auto-discovery was not selected on the previous wizard page.

f Click Next.

g Schedule the configuration data collection.



Select one of the following options:

• Disable configuration collection. Configuration collection may interrupt your application polling. Disable this option if you expect the configuration data to be static.

Note Configuration data collection retrieves and updates information about TransNET device relationships. Ensure that you schedule configuration collections occasionally if you want updates on TransNET device relationships.

• On a Schedule. Schedule configuration date to be collected on specific days of the week or dates during the month. Click Edit to change the schedule settings.

For more information about scheduling configuration data collection, see the Administration Guide.

h Click Finish.

9 If you chose Collect Actively in step 4, complete the following steps:



a Type the values for the active collection settings. If the values are not changed, the global values in the Dlink Advanced Configuration are used. For more information about the settings and default values, see “Changing Global Advanced Dlink Settings” on page 7.

b Type the values for the sleep mode settings. If the values are not changed, the global values in the Dlink Advanced Configuration are used.

c Click Next.

d Select the type of schedule for performance data collection. Click Edit to change the schedule settings.

e Click Next.

f Schedule the configuration data collection by selecting one of the following options:

• Disable configuration collection. Configuration collection can interrupt your application polling. Disable this option if you expect the configuration data to be static.

Note Configuration data collection retrieves and updates information about TransNET device relationships. Ensure that you schedule configuration collections occasionally if you want updates on TransNET device relationships.

• On a Schedule. Schedule configuration data to be collected on specific days of the week or dates during the month. Click Edit to change the schedule settings.

For more information about scheduling configuration data collection, see the Administration Guide.

g Click Finish.

The Dlink master device is updated with the collection type and scope of data. When the scheduled collection returns data, you can view the information by navigating to the Summary dashboard and clicking on a device to see more details. For more information about the Summary dashboard, see the Monitoring Guide.

Note If you start a discovery on an authorized master, any ongoing active and passive data collections on the master are interrupted so that the discovery can start immediately.

3

Working with 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.

Adding SNMP v1 or v2c Community StringsThere are two default community strings: public (read-only) and private (write). More community strings can be added.

To add an SNMP v1 or v2c community string:

1 On the navigation panel, click Administration > Global Settings > SNMP Configuration.

2 In the SNMP v1 and v2c Community Strings table, click Add.

Note The Add button is dimmed if neither SNMP v1 nor SNMP v2c are selected for use in the advanced SNMP settings. For information about configuring advanced SNMP settings, see “Defining Advanced SNMP Settings” on page 24.

3 In the dialog box, type a community string name.


Chapter 3—Working with SNMP Devices

4 Select Read Permission or 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.

Tip 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.

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 “Discovering SNMP Devices” on page 26.

Deleting SNMP v1 or v2c Community Strings

Community strings cannot be deleted if they are being used to manage devices.

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.

2 Click Delete.

Alternatively, click Delete in the row for the community string you want to delete.

Adding SNMP v3 CredentialsSNMP v3 credentials can be added, edited, and removed.

To add SNMP v3 credentials:


2 In the SNMP v3 Credentials table, click Add.

Note The Add button is disabled if SNMP v3 is not selected for use in the advanced SNMP settings. For information about configuring advanced SNMP settings, see “Defining Advanced SNMP Settings” on page 24.



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 or 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.

Tip 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:

a No authentication and no privacy - the identity of the sender is not verified.

b Authentication and no privacy - the identity of the sender is verified, but the information is not encrypted.

c Authentication and privacy - the identity of the sender is verified and the information is encrypted.

6 If the Security Level that you selected requires authentication, specify an authentication protocol and passphrase. The passphrase is 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.

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 “Discovering SNMP Devices” on page 26.

Editing SNMP v3 Credentials

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.

For information about the credentials, see “Adding SNMP v3 Credentials” on page 22.

3 Click Save.

Deleting SNMP v3 Credentials

Credentials cannot be deleted if they are being used to manage devices.

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 icon becomes enabled.

2 Click Delete.

Alternatively, click Delete in the row for the set of credentials that you want to delete.



Defining Advanced SNMP SettingsTo configure advanced SNMP settings:


2 In the bottom-left of the SNMP Configuration view, click advanced SNMP settings .

The Advanced SNMP Settings dialog appears.

In the Advanced SNMP Settings dialog box, you can configure the following parameters:


SNMP Usage The version of SNMP that the system uses for communication. Select all versions that you want the system to use.

All

SNMP Target Port The port used for SNMP communication. 161

SNMP Timeout (ms)

The length of time the system waits for a device to respond to an SNMP request.

7000

ICMP Timeout (ms)

The length of time the system waits for a device to respond to an ICMP request.

5000



3 Make changes to one or more of the settings.

4 Click Save.

Migrating Devices from One Community String or Set of Credentials to AnotherTo migrate devices:


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 the check boxes beside the devices that you want to migrate.

To select all of the devices, click the check box at the top of the column.

4 Click Next.

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.

10

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




5 Select a destination community string, a set of credentials, or a new SNMP version.

6 Click Finish.

Discovering SNMP DevicesAfter SNMP credentials have been defined, you can run a discovery to find the devices that you want to monitor.

To discover devices:

1 On the navigation panel, click Administration > Device Selection > SNMP Device Selection.

2 In the SNMP Discovery view, click Discover Devices.



3 In the Discovery Wizard, specify the SNMP community strings and/or credentials required to discover devices.

The more strings or credentials that you specify, the longer the discovery typically takes to run.

Note If you do not see the SNMP community strings or credentials, click the link at the bottom left of the Discovery Wizard to configure them. For information about configuring SNMP, see “Adding SNMP v1 or v2c Community Strings” on page 21. To enable community strings, you must select v1 or v2c for SNMP Usage in the Advanced SNMP Settings. To enable credentials, you must select v3 for SNMP Usage. For information about configuring advanced SNMP settings, see “Defining Advanced SNMP Settings” on page 24.

4 Click Next.

5 Specify IP addresses for the discovery.



a To specify an IP address in the IP Search Space table, click Add IP.

In the Edit IP dialog box that appears, enter the IP address and click Add.

The IP address is added to the discovery.

b To specify an IP address range in the IP Search Space table, click Add IP Range and type the IP address range. Click Add.

For example, an IP address range of 10.10.120.1 - 10.10.121.2 adds the following IP addresses to the discovery: 10.10.120.1, 10.10.120.2, 10.10.121.1, and 10.10.121.2.


On the same screen of the Discovery Wizard, specify the IP addresses to be excluded from the discovery.

c To specify an IP address in the Exclude Criteria table, click Add IP. Type the IP address and click Add.

The IP address is added to the exclude criteria.

Note There is no need to exclude the IP addresses of devices that are already authorized; They are excluded by default. Click Exclude Criteria to see a list of other IP addresses that are excluded by default.



d To specify an IP address range in the Exclude Criteria table, click Add IP Range. Type an IP address range and click Add.

The IP address range is added to the exclude criteria.


Note The Discovery Wizard provides an estimate of the time it takes to perform discovery. This is a worst-case estimate based on the configuration of the advanced SNMP and ICMP settings. For information about configuring advanced SNMP and ICMP settings, see “Defining Advanced SNMP Settings” on page 24.

6 Click Finish.

Your discovery request is processed. Watch the Discovery Progress pane to see which devices are discovered and can be authorized for monitoring.

Discovery Progress

Discovered devices that can be authorized appear in the list in the left pane of the SNMP Device Selection view. Discovered devices that are ineligible appear in the Ineligible Devices pane at the right. For information on how to authorize devices, see the Administration Guide. For information about discovered ineligible devices, see the “Ineligible Devices” section.

During discovery, you are notified about any decommissioned devices (that you may want to re-authorize) and about any monitored devices that have significant configuration changes.

Therefore, if there are decommissioned devices you want re-authorized, you can perform discovery to re-authorize them. Also, if you become aware that the configuration for a device has changed and you do not have the information required to manually edit the configuration, you can perform discovery to acquire the new configuration information.

Ineligible Devices

Note PulseNET cannot discover ineligible Dlink devices.

SNMP devices can be deemed ineligible for one of the following reasons:

• The device is one that PulseNET does not monitor.

• MDS entraNET remote devices are discovered without an SNMP Write credential (private) defined, so there is not enough information to authorize the devices. Run an SNMP discovery again with a Write credential so that the entraNET remote devices can be discovered.

• PulseNET successfully made contact with the device, but could not connect to it.

Note This could be a configuration problem and should be investigated. To assist you in this investigation, export the ineligible devices list.

Exporting the Ineligible Devices List

If ineligible devices are discovered and you want to investigate, you can export the ineligible devices list to assist you in the investigation.



To export the ineligible devices list:

1 On the navigation panel, click Administration > Device Selection > SNMP Device Selection.

The SNMP Discovery view appears.

2 In the Ineligible Devices pane, click the Customizer icon at the top-right of the list.

3 In the popup, click Export.

4 In the next popup, select an export format.

The list is exported in the format that you selected.


Index

Aactive

data collection 16suspended for discovery 20

discovery 10sleep mode network 15

Active Freq RX and TX 17adding

SNMP community strings 21SNMP v3 credentials 22

authenticationSNMP configuration 23

auto-discovery 13

Ccommunity strings

adding and removing 21migrating devices to 25

configuration dataTransNET device relationships 20updating by discovery 29

Configure Collection Wizard 15Continuous Key 17credentials

adding SNMP v3 22deleting 23

Ddata collection

configuration data 18Dlink

collection size 17per master 15

scope 17suspended for discovery 20timeouts 14

Data Key Mode 17devices

discovering

Dlink 11SNMP 26

ineligible 29unavailable 14updating information 13

discoveryDlink

active 10auto-discovery 13global change 12passive 11progress 13running 11sleep mode 10suspends data collection 20

for updating configuration data 29SNMP

progress 29running 26

Dlinkadding master seeds 6advanced settings 7auto-discovery 13change IP and port 15data collection

per master 15scope 17suspended for discovery 20type 13

discovering devices 11networks 13parameters 8

Eediting

Dlink master seed 7SNMP credentials 23

EMP 17encryption


Index

SNMP v3 credentials 23entraNET devices

ineligible 29SNMP v3 credentials 23

extended data collection 17

FForgive Missed Polls 15frequently polled network 13

IIP addresses

Dlinkadding devices 6changing IP 15device discovery 11

SNMPdiscovery 27

Llimited data collection 17

Mmaster seeds

adding 6defining data collection 15

migrating devicesSNMP credentials 25

Nnetwork types for Dlink 13

Pparameters

SNMP settings 24parameters for Dlink settings 8passive

data collection 16suspended for discovery 20

discovery 11passwords

SNMP v3 credentials 23port

changing on dlink master 15

Dlink terminal server 6SNMP target 24

portschanging on Dlink device 15

Rrarely polled network 13removing

SNMP credentials 23Request Gap 14Request Timeout 14RTU Simulator ID 17

Sschedules

active Dlink collection consideration 14for Dlink sleep mode networks 15

Seamless Setting and Timer 17Sleep Inhibit Timeout 15sleep mode

data collection 16discovery 10network considerations 15

sleep mode network 13SNMP

advanced settings 24community strings

adding and removing 21migrating devices 25

credentialsediting 23migrating devices 25

devicesdiscovering 26ineligible 29migrating 25

encryption for v3 23entraNET devices 23parameters 24v3 credentials

adding 22

Ttimeout

Dlink ICMP and HTTP 10Dlink monitoring request 8


Index

for passive discovery 11SNMP request 24

topologyupdated for Dlink 20

TransNETdevice relationship updates 20

troubleshootingineligible devices 29

Uunavailable devices 14

Wwrite permissions

ineligible entranet devices 29

IN CASE OF DIFFICULTY...

If you have problems, comments or questions pertaining to the MDS PulseNET application, please contact GE MDS using one of the methods listed below:

Phone: 585 241-5510 E-mail: [email protected] FAX: 585 242-8369 Web: www.gemds.com

PulseNET Devices Guide€¦ · solve complex IT challenges ranging from database management, data...

Documents

Transcript of PulseNET Devices Guide€¦ · solve complex IT challenges ranging from database management, data...