CA Nimsoft Monitor
snmpcollector Release Notes
All versions
Legal Notices
This online help system (the "System") is for your informational purposes only and is
subject to change or withdrawal by CA at any time.
This System may not be copied, transferred, reproduced, disclosed, modified or
duplicated, in whole or in part, without the prior written consent of CA. This System is
confidential and proprietary information of CA and protected by the copyright laws of
the United States and international treaties. This System may not be disclosed by you or
used for any purpose other than as may be permitted in a separate agreement between
you and CA governing your use of the CA software to which the System relates (the “CA
Software”). Such agreement is not modified in any way by the terms of this notice.
Notwithstanding the foregoing, if you are a licensed user of the CA Software you may
make one copy of the System for internal use by you and your employees, provided that
all CA copyright notices and legends are affixed to the reproduced copy.
The right to make a copy of the System is limited to the period during which the license
for the CA Software remains in full force and effect. Should the license terminate for any
reason, it shall be your responsibility to certify in writing to CA that all copies and partial
copies of the System have been destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM “AS IS”
WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY
FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM,
INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS
INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN
ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.
The manufacturer of this System is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States
Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14,
and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their
successors.
Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks,
and logos referenced herein belong to their respective companies.
Legal information on third-party and public domain software used in the Nimsoft
Monitor solution is documented in Nimsoft Monitor Third-Party Licenses and Terms of
Use (http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html).
Contact CA
Contact CA Support
For your convenience, CA Technologies provides one site where you can access the
information that you need for your Home Office, Small Business, and Enterprise CA
Technologies products. At http://ca.com/support, you can access the following
resources:
■
Online and telephone contact information for technical assistance and customer
services
■
Information about user communities and forums
■
Product and documentation downloads
■
CA Support policies and guidelines
■
Other helpful resources appropriate for your product
Providing Feedback About Product Documentation
Send comments or questions about CA Technologies Nimsoft product documentation to
[email protected].
To provide feedback about general CA Technologies product documentation, complete
our short customer survey which is available on the CA Support website at
http://ca.com/docs.
Contents
Chapter 1: snmpcollector General Overview
7
Related Documents ...................................................................................................................................................... 7
Chapter 2: Requirements
9
Hardware Requirements .............................................................................................................................................. 9
Software Requirements ............................................................................................................................................. 10
Memory and Disk Requirements ................................................................................................................................ 10
Probe v1.4 and Later ........................................................................................................................................... 11
Probe v1.3 and Earlier ......................................................................................................................................... 11
Adjust Xmx Memory ............................................................................................................................................ 12
Supported Platforms .................................................................................................................................................. 12
Chapter 3: Considerations
13
Installation Considerations ......................................................................................................................................... 13
General Considerations .............................................................................................................................................. 13
Versions for CA Nimsoft Monitor Snap ............................................................................................................... 13
Do Not Duplicate Priority for Rules ..................................................................................................................... 14
Some Metrics May Not Be Reported on Some Devices ...................................................................................... 14
Limitations for Juniper Devices ........................................................................................................................... 15
Changes to Profile Credentials Not Saved ........................................................................................................... 15
Configuration File Can Become Corrupted ......................................................................................................... 15
Chapter 4: Vendor Support
17
Chapter 5: Revision History and Issues
19
Revision History .......................................................................................................................................................... 19
Additional Metric Families ......................................................................................................................................... 21
Known Issues and Workarounds ................................................................................................................................ 25
Contents 5
Chapter 1: snmpcollector General Overview
Simple Network Management Protocol (SNMP) is an internet-standard protocol for
managing devices on IP networks and consists of a set of standard for network
management, including application layer protocol, database schema and a set of data
objects. Typical devices that support SNMP are routers, switches, servers, workstations,
and printers.
The SNMP data monitoring probe allows you to monitor network-attached devices for
conditions that require administrative attention.
This section contains the following topics:
Related Documents (see page 7)
Related Documents
Related Documentation
Documentation for snmpcollector probe in Admin Console
Monitor Metrics Reference Information for CA Nimsoft Probes
(http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm)
Chapter 1: snmpcollector General Overview 7
Chapter 2: Requirements
This section contains the requirements for the SNMP data monitoring probe.
This section contains the following topics:
Hardware Requirements (see page 9)
Software Requirements (see page 10)
Memory and Disk Requirements (see page 10)
Supported Platforms (see page 12)
Hardware Requirements
The SNMP data monitoring probe should be installed on systems with the following
minimum resources:
■
Memory: 4 GB (minimum) of RAM. This probe’s out of the box configuration
requires 2.5GB of RAM.
■
CPU: 3 GHz dual-core processor, 64-bit.
Chapter 2: Requirements 9
Software Requirements
Software Requirements
The SNMP data monitoring probe can be used to monitor devices that support SNMP
v1, v2c and v3.
Note: It is recommended that the CA Nimsoft Monitor server and CA Unified
Management Portal (UMP) are the same version but not required.
SNMP data monitoring probe v1.4 and later requires:
■
CA Nimsoft Monitor server version 7.5 or later
■
CA Nimsoft Monitor discovery_server probe version 7.5 or later on the primary
hub
■
CA Nimsoft Monitor ppm probe version 2.23 or later on each hub with a robot
running the SNMP data monitoring probe
■
CA Unified Management Portal (UMP) version 7.5 or later
SNMP data monitoring probe v1.2 and v1.3 requires:
■
CA Nimsoft Monitor server version 7.1
■
CA Nimsoft Monitor discovery_server probe version 7.10 or later on the
primary hub
■
CA Nimsoft Monitor ppm probe version 2.20 or later on each hub with a robot
running the SNMP data monitoring probe
■
CA Unified Management Portal (UMP) version 7.0 or later
SNMP data monitoring probe v1.1 requires:
■
CA Nimsoft Monitor server version 7.0
■
CA Nimsoft Monitor discovery_server probe version 7.10 or later on the
primary hub
■
CA Nimsoft Monitor ppm probe version 2.10 or later on each hub with a robot
running the SNMP data monitoring probe
■
CA Unified Management Portal (UMP) version 7.0 or later
Memory and Disk Requirements
This section includes the memory and disk requirements for specific releases of the
snmpcollector and pollagent probes and instructions for adjusting Xmx memory.
10 snmpcollector Release Notes
Memory and Disk Requirements
Probe v1.4 and Later
The following table shows the memory and disk requirements for the snmpcollector and
pollagent probes.
Number of
Components
Value
snmpcollector
pollagent
1000
Xmx Memory
1,024 MB
2,048 MB
Disk
2 GB
3 GB
Xmx Memory
2,048 MB
4,096 MB
Disk
4 GB
6 GB
Xmx Memory
3,072 MB
6,144 MB
Disk
6 GB
12 GB
Xmx Memory
4,096 MB
8,192 MB
Disk
9 GB
20 GB
Xmx Memory
6 GB
13 GB
Disk
13 GB
28 GB
5,000
10,000
20,000
50,000
Probe v1.3 and Earlier
The following table shows the memory and disk requirements for the snmpcollector and
pollagent probes.
Number of
Components
Value
snmpcollector
pollagent
1000
Xmx Memory
1,024 MB
2,048 MB
Disk
2 GB
3 GB
Xmx Memory
2,048 MB
4,096 MB
Disk
8 GB
12 GB
5,000
Chapter 2: Requirements 11
Supported Platforms
10,000
20,000
Xmx Memory
3,072 MB
6,144 MB
Disk
12 GB
24 GB
Xmx Memory
4,096 MB
8,192 MB
Disk
20 GB
40 GB
Adjust Xmx Memory
The memory and disk requirements for the snmpcollector and pollagent probes can vary
according to the number of processors, devices, device components, and metrics. You
might need to adjust the Xmx memory to improve performance.
Follow these steps:
1.
In Infrastructure Manager, select and right-click on pollagent or snmpcollector.
2.
Select Edit from the menu.
3.
In the Arguments box, change the text -Xmx1536m so that the number following
Xmx is the desired number of megabytes for Xmx memory.
4.
Click OK.
The probe restarts with the new setting.
Supported Platforms
The snmpcollector probe is supported on the same set of operating systems and
databases as the Nimsoft Monitor Server solution. Please refer to the:
■
Nimsoft Compatibility Support Matrix for the latest information on supported
platforms.
■
Support Matrix for Nimsoft Probes for additional information on the snmpcollector
probe.
12 snmpcollector Release Notes
Chapter 3: Considerations
This section contains the considerations for the SNMP data monitoring probe.
This section contains the following topics:
Installation Considerations (see page 13)
General Considerations (see page 13)
Installation Considerations
The SNMP data monitoring probe actually is two distinct probes:
■
snmpcollector
■
pollagent
The probes are downloaded and installed just like other CA Nimsoft Monitor probes.
Download both these probes from the Internet Archive into your local Archive.
After you download the probes to your local Archive, you only need to install (drag from
the Archive to the Robot), the snmpcollector probe. The snmpcollector probe has a
dependency on the pollagent probe, so the pollagent probe is automatically installed.
Important! Install the snmpcollector probe and the pollagent probe on a secondary hub
where no other monitoring probes are installed.
Note: On Linux/Unix systems the /etc/hosts file should contain an entry with the FQDN
for the installation system.
General Considerations
This section lists general considerations for the SNMP data monitoring probe.
Versions for CA Nimsoft Monitor Snap
The 1.2 and 1.4 versions of the SNMP data monitoring probe were not released for use
with the CA Nimsoft Monitor Snap GUI. CA Nimsoft Monitor Snap users should refer to
the document version appropriate for the version of the SNMP data monitoring probe
included with their installation of CA Nimsoft Monitor Snap.
Chapter 3: Considerations 13
General Considerations
Do Not Duplicate Priority for Rules
Do not assign the same priority to more than one rule. If you do so, the existing rule
with that priority is overwritten (deleted).
Some Metrics May Not Be Reported on Some Devices
Not all metrics defined in a metric family are delivered for all devices. Some devices do
not support some OID metrics. For example, PctDiscards of packets on a virtual router
may not be able to be calculated if certain OID data is not available from the router.
To determine whether metrics are not being reported, view the pollagent log file. When
the pollagent is given a new set of metrics to poll, it attempts to collect all OID data. Any
OIDs not supported by a device are logged in the following format only once when the
metric is first added, and when it is re-added through a probe restart.
In the following pollagent log message examples you see the device IPaddress, the
metric family name, and the OID name and value that is not supported.
Dec 20 10:41:42 DASCH03-780.ca.com AGM: [Info.]
(Tests:SnmpGetExpression:p_172.19.255.12|NormalizedPortInfo|s86)
[SnmpGetExpressionTest: 172.19.255.12_V2] UNSUPPORTED_OID=1.3.6.1.2.1.31.1.1.1.6.86 ifHCInOctets
Dec 20 10:41:42 DASCH03-780.ca.com AGM: [Info.]
(Tests:SnmpGetExpression:p_172.19.255.12|NormalizedPortInfo|s86)
[SnmpGetExpressionTest: 172.19.255.12_V2] UNSUPPORTED_OID=1.3.6.1.2.1.31.1.1.1.8.86 ifHCInMulticastPkts
Dec 20 10:41:42 DASCH03-780.ca.com AGM: [Info.]
(Tests:SnmpGetExpression:p_172.19.255.12|NormalizedPortInfo|s18)
[SnmpGetExpressionTest: 172.19.255.12_V2] UNSUPPORTED_OID=1.3.6.1.2.1.31.1.1.1.10.18 ifHCOutOctets
Dec 20 10:41:42 DASCH03-780.ca.com AGM: [Info.]
(Tests:SnmpGetExpression:p_172.19.255.12|NormalizedPortInfo|s18)
[SnmpGetExpressionTest: 172.19.255.12_V2] UNSUPPORTED_OID=1.3.6.1.2.1.31.1.1.1.12.18 ifHCOutMulticastPkts
Dec 20 10:41:42 DASCH03-780.ca.com AGM: [Info.]
(Tests:SnmpGetExpression:p_172.19.255.12|NormalizedPortInfo|s18)
[SnmpGetExpressionTest: 172.19.255.12_V2] UNSUPPORTED_OID=1.3.6.1.2.1.31.1.1.1.6.18 ifHCInOctets
Dec 20 10:41:42 DASCH03-780.ca.com AGM: [Info.]
(Tests:SnmpGetExpression:p_172.19.255.12|NormalizedPortInfo|s18)
[SnmpGetExpressionTest: 172.19.255.12_V2] UNSUPPORTED_OID=1.3.6.1.2.1.31.1.1.1.8.18 ifHCInMulticastPkts
14 snmpcollector Release Notes
General Considerations
Limitations for Juniper Devices
Metrics for memory and CPU are not supported for Juniper devices for the 1.2 release.
Changes to Profile Credentials Not Saved
If you add a profile and then edit an authentication credential the change is not saved. If
you need to change the credentials for a profile, delete the profile and add it again with
the correct credentials.
Configuration File Can Become Corrupted
The configuration file can become corrupted if the probe is disconnected from the
controller while executing a discovery or configuration operation. The SNMP data
monitoring probe creates a configuration backup file every time the probe starts
successfully. You can use the snmpcollector.cfg.BAK file located in
Nimsoft/probes/networking/snmpcollector/ to assist with the recovery process.
Note: We recommend frequent backups while making configuration changes.
Chapter 3: Considerations 15
Chapter 4: Vendor Support
For information on supported SNMP vendors, see the Supported Device Inventory
document.
Chapter 4: Vendor Support 17
Chapter 5: Revision History and Issues
This section contains the revision history and known issues for the SNMP data
monitoring probe.
This section contains the following topics:
Revision History (see page 19)
Additional Metric Families (see page 21)
Known Issues and Workarounds (see page 25)
Revision History
This section describes the history of the revisions for the SNMP data monitoring probe.
Date
Description
State
Version
May
2014
Added the ability to override the default speed in
and out settings for interface devices. For more
information, see the updated Known Issues and
Workarounds (see page 25) section.
GA
1.42
GA
1.41
Fixed an issue with the calculation of metric counter
values.
April
2014
Fixed an issue where large values for QoS metrics
were being calculated incorrectly.
Fixed an issue with inventory corruption when
loading USM devices.
Removed the obsolete metric family Generic System
CA. Metrics were moved into specific device metric
families.
Chapter 5: Revision History and Issues 19
Revision History
Date
Description
State
Version
March
2014
Support for SNMP AES-192 and AES-256 privacy
protocols.
GA
1.40
GA
1.33
February Minor bug fixes and performance enhancements.
2014
Name changes for System Management
Info-Router\Director and Anti-Virus Info metric
families.
GA
1.32
January
2014
GA
1.30
GA
1.20
Support for polling 50,000 interfaces every 5
minutes.
Added full support for Juniper devices.
Improved handling of index shift for router
interfaces.
Improvements in performance for Discovery Server
and detection of device components.
Corrected issues with invalid or duplicate device
names appearing after rediscovery.
Updated memory and disk requirements, software
requirements, and supported platforms.
Unsupported metrics no longer appear for device
components. Previously, unsupported metrics would
appear as configurable but never collect data.
March
2014
Updated for use with CA Nimsoft Monitor Snap 7.5.
Fixed an issue with QOS_pctDiscardsOut not
appearing in USM.
Fixed an issue where SNMP V3 devices with AES
encryption would appear in USM without default
monitors.
Support for SNMP V3 3-DES, and AES-128 privacy
protocols.
Support for CPU and physical memory metric
families on Juniper devices.
Added the NMS RULE AdminStatus Down rule to
filter interfaces that are administratively down.
Updated memory and disk requirements, software
requirements, and supported platforms.
Decembe Support for additional metric families.
r 2013
Support for F5, Juniper devices, and system agents
(Host Resources and CA SystemEDGE)
20 snmpcollector Release Notes
Additional Metric Families
Date
Description
Septemb Improvements in performance, especially discovery.
er 2013
Usability improvements to UI.
State
Version
GA
1.10
Added the ability to monitor Cisco devices, similar to
the functionality of the cisco_monitor probe.
Added the ability to set rules for monitoring
configurations so that you can set different
thresholds based on non-polled configuration
information (for example, based on ifType).
July 2013 Improvements to memory management and
discovery performance.
Controlled 1.01
Release
June
2013
Controlled 1.00
Release
Initial version of the SNMP data monitoring probe
Additional Metric Families
The following metric families were added or updated in version 1.4 of the probe.
Battery
Defines metrics for battery modules.
Battery Controller
Defines metrics for battery controller modules.
CBQos ClassMap
Defines the identification information, configuration
information, and polled metrics for CBQos Class Map.
CBQos Match Statement
Defines the identification information, configuration
information, and polled metrics for CBQoS CBQos
Match Statement.
CBQoS Policer
Defines the identification information, configuration
information, and polled metrics for CBQos Policer.
CBQoS Queuing
Defines the identification information, configuration
information, and polled metrics for CBQos Queueing
CBQos RED
Defines the identification information, configuration
information, and polled metrics for CBQos RED.
CBQos Traffic Shaping
Defines the identification information, configuration
information, and polled metrics for CBQoS Traffic
Shaping.
Controller Enclosure
Defines metrics for controller enclosure modules.
Disk Enclosure
Defines metrics for disk enclosure modules.
Disk Raid
Defines metrics for disk raid modules.
Chapter 5: Revision History and Issues 21
Additional Metric Families
Disk Volume
Defines metrics for disk volume modules.
Expander
Defines metrics for expander modules.
LUN
Defines metrics for LUN (logical unit number) modules.
Response Path Test DHCP
Defines the identification information, configuration
information, and polled metrics for response paths.
Response Path Test DLSW
Defines the identification information, configuration
information, and polled metrics for response paths.
Response Path Test
EthernetPing
Defines the identification information, configuration
information, and polled metrics for response paths.
Response Path Test HTTP
Defines the RTTMon HTTP response path.
Response Path Test ICMP
Defines the identification information, configuration
information, and polled metrics for response paths.
Response Path Test Jitter
Defines the response path with Jitter.
Response Path Test PathEcho
Defines the identification information, configuration
information, and polled metrics for response paths.
Response Path Test TCP
Defines the identification information, configuration
information, and polled metrics for response paths.
Response Path Test UDP
Defines the identification information, configuration
information, and polled metrics for response paths.
Storage Array
Defines metrics for storage array modules.
Storage Array Controller
Defines metrics for storage array controller modules.
Storage Array Disk
Defines metrics for storage array disk modules.
Storage Interface
Defines metrics for storage interface modules.
Storage Mirror
Defines metrics for storage mirror modules.
The following metric families were added or updated in version 1.3 of the probe.
Metric Family
Description
Anti-Virus Info
Defines the configuration and polled metrics for
Anti-Virus file scanned and detected.
CPU
Defines the identification information, configuration
information, and polled metrics for CPUs.
Disk
Defines generic disk-related stats such as disk name,
capacity, total used and free disk, disk bytes reads\
writes in value and percentage.
22 snmpcollector Release Notes
Additional Metric Families
Generic System CA
Defines general system configuration information and
polled metrics for a device.
IPSEC Tunnel CA Information
Defines the configuration information and polled
metrics for IPSEC tunnel.
Interface
Defines general interface information and polled
metrics for a device.
Physical Memory
Defines the configuration information and polled
metrics for physical memory on a device.
Pool Connections - Pool
Members
Defines the configuration information and polled
metrics for pool connections frames in/out, I/O bytes,
current, maximum and total connections present on
the device.
System Management
Info-Router\Director
Defines system management information generated
by Acme Packet Session Router and Session Director.
System Information
Defines identification and configuration information
for system related metrics like location, description,
vendor etc.
System Session Information
Defines general session information and polled metrics
for a device.
System Utilization
Information
Defines general CPU use information and polled
metrics for device management.
Support for the following metric families was added in version 1.2 of the probe.
Metric Family
Description
Disk Partition
Supports disk-related stats such as disk name,
capacity, total used and free disk in value and
percentage.
Disk
Defines generic disk-related statistics such as disk
name, capacity, total used and free disk, disk bytes
reads/writes in value and percentage.
IDS Protection
Defines statistics for intrusion detection systems (IDS)
protection such as different kinds of attacks.
IPv6 Stats
Defines information on IPv6 Statistics such as IP
datagrams received and discarded, forward attempts,
and so on.
Virtual Server
Defines the configuration information and polled
metrics for virtual server, which includes frames
in/out, I/O bytes, current, maximum and total
connections present on the device.
Chapter 5: Revision History and Issues 23
Additional Metric Families
System Environmental Sensor Defines configuration information and polled metrics
- CPU
for system environmental sensor for CPU, which
includes fan speed and temperature in Celsius and
Fahrenheit.
System Utilization
Information
24 snmpcollector Release Notes
Defines configuration information and polled metrics
for system utilization, which includes CPU and memory
utilization.
Known Issues and Workarounds
Known Issues and Workarounds
Issue:
The interface speed for some virtual interfaces is not reported correctly because the
device is not able to detect the true speed of connection. This issue is usually seen with
WAN related interfaces.
Workaround:
To properly calculate utilization on these interfaces, you must contact your system
administrator to determine the maximum speed of the interface. You must then set the
interface speed in the probe.
The interface speed settings are available with probe v1.42 or later.
Follow these steps:
1.
Open the probe UI and view the device profile with the incorrect interface metrics.
Select snmpcollector > Profiles > profile name > device name > Interface.
A table of interface devices appears in the pane to the right.
2.
Click the name of an interface device to modify the device settings in the fields
below the table.
3.
Set an override value in the Speed out Override and Speed in Override fields in bits
per second.
For example, to set an interface to a speed of 100GB you would enter
100000000000.
4.
Save your changes.
The probe uses the override values to calculate the utilization for the interface.
Issue:
Some polled metric values larger than 8 million might be rounded. This limits the
precision available in polled metrics.
Workaround:
No workaround exists at this time.
Issue:
I see an I/O communication error in the snmpcollector.log file with the following
message:
Exception in ThreadClient: (2) communication error, I/O error on nim session (S)
com.nimsoft.nimbus.NimServerSession(/123.45.678.191:54827-/123.45.6.7:59412): End
of stream while trying to read header
This message only appears when loglevel is 1 or greater when loading or reloading the
configuration page.
Chapter 5: Revision History and Issues 25
Known Issues and Workarounds
Workaround:
No action is required. You can ignore this alarm.
Issue:
SNMP devices with non-standard port numbers are not detected. The standard port
number for an SNMP device is 161.
Workaround:
View the device in NMS and verify that a non standard device port is in use. You must
reconfigure the device to use port 161.
Issue:
I see an alarm with the following message:
An attach queue for the subject probe_discovery on the hub
/SNMPdom/SNMPhub/SNMProbot/hub has been successfully detected. Though not
determined here, either a get or post queue may also be needed to forward discovery
results if this is not the primary hub.
Workaround:
No action is required. You can ignore this alarm.
Issue:
It may take 30 minutes or more to complete initial discovery of device subcomponents
(after querying the Discovery Server for the first time). This may cause screen (GUI)
timeouts during that period.
Workaround:
Wait for subcomponent discovery to complete.
Issue:
When thresholds are changed in a monitoring template, all devices may not receive the
updated thresholds. This is an issue in probe versions earlier than 1.2.
Workaround:
Avoid changing an existing monitoring template. Create a new template (uses the values
in the default) and apply the new template to the devices.
Issue:
Admin Console based Restart command does not work for snmpcollector or pollagent.
Workaround:
First Deactivate the probe and then Activate it.
26 snmpcollector Release Notes
Known Issues and Workarounds
Issue:
The SNMP data monitoring probe may be unresponsive under heavy load, during
scheduled re-discovery, or immediately after applying a monitoring template to multiple
large devices.
Workaround:
If the probe is unresponsive, wait several minutes and try again.
Issue:
Discovery can take longer than expected. This issue is most likely to occur in version 1.0
of the probe. The snmpcollector 1.1 probe greatly improves performance of discovery.
Workaround:
To check discovery progress:
Version 1.0
In the probe GUI click the SNMP Collector Probe node in the tree and view the
Discovery Status field.
Version 1.1
In the probe GUI click a device name in the tree (SNMP Collector Probe >
Profiles > profile name > device name) and view the Component Discovery
field.
Chapter 5: Revision History and Issues 27