Reset Discovery Data
When Discovery processes execute, they collect information on discovered devices and store this information in the Reporting Database. When you reset the Discovery data, you purge all this information from the Reporting Database and reset the Client Protection Summary report. The data re-populates the next time the Discovery processes run.
Consider resetting your Discovery data if any of the following conditions are true:
• If your initial Discovery policy was too broad, and included devices that were in a DHCP range. This policy configuration could result in potentially large numbers of IP addresses showing up in the Client Protection Summary report thereby diminishing the effectiveness of the report.
• If previously discovered clients no longer exist in your environment, but are still showing in the Client Protection Summary report.
• If a file system on a previously discovered client had subsequently been removed, and is still showing up in the Client Protection Summary report.
By resetting the Discovery data, you can start over and rebuild a fresh list of discovered devices and file systems. A reset only impacts the Client Protection Summary report. A reset does not affect any of the other collected backup data that is used in all other reports.
Note: The information contained in this section is intended for the administration of Discovery functionality. APTARE provides this SNMP configuration guidance for informational purposes only. APTARE Global Support Services will not provide assistance with the installation, configuration, and troubleshooting of SNMP subsystems on your Master Servers.
Why Enable SNMP?
The Simple Network Management Protocol (SNMP) is an Internet standard that provides a common way to query, monitor, and manage devices connected to IP networks. The protocol is defined in RFC 2571. For additional information, see
http://www.ietf.org/rfc/rfc2571.txt.
To capture filesystem level information on your media servers and any other servers in your environment, you must enable SNMP.
Using SNMP v2c messaging, Discovery queries all media servers and other servers or devices and retrieves information about the physical attributes of their configured storage units and file systems. The SNMP probe uses UDP and the standard SNMP Port 161 by default.
There are different SNMP probes for different operating systems. The way that you enable and configure SNMP services on your servers to take advantage of these probes depends on your operating system.
• Windows
• Red Hat Linux
• HP-UX
• Solaris 8/9
• Solaris 10
About SNMP Probes
To take full advantage of the Discovery functionality, the SNMP subsystem must be configured to respond to the following probes:
First Probe (sysObjectOID)
This probe is sysObjectOID (.1.3.6.1.2.1.1.2). This probe returns an OID that conforms to the enterprise OIDs allocated by the Internet Assigned Numbers Authority. Be aware that the SNMP agent resident on the device returns this number, and this number might not be the same number as the hardware manufacturer. For example an HP N-class server may return the enterprise OID of 1.3.6.1.4.1.11 or 1.3.6.1.4.1.2021.250.14 depending on whether the SNMP agent is provided by HP or is the open source NET-SNMP package. The number returned is matched against a lookup table to try and determine the company value of the OID. (For example, IBM or Sun).
Second Probe (sysDescr OID)
This probe is made for the sysDescr OID (.1.3.6.1.2.1.1.1). This probe returns a description of the device or agent. This string is matched against a lookup table to try and determine the system description value. (For example, Windows 2000 or Solaris).
Lastly, if configured, a query is made against the Device and Storage section of the Host Resources Management Information Block (MIB). Specific information retrieved is the file system mount point, storage type, storage description, allocation units, size in storage units, and storage units used. Before this information is returned, calculations are made to convert the values into kilobytes. Only fixed disk storage units are returned.
Enabling SNMP for Windows (NT/2000/XP)
This procedure assumes that you have Windows 2000/XP. However, the process is very similar on Windows NT. For more information about setting up SNMP on Windows, go to the following Microsoft articles:
To install the SNMP on Windows 2000/XP:
You might need to install the CD for your operating system, so have the recovery CD available.
1. Click Start > Settings > Control Panel.
2. Double-click Add/Remove Programs.
3. Click Add/Remove Windows Components.
4. Click Management and Monitoring Tools and click Details.
The Management and Monitoring Tools window appears.
5. Select Simple Network Management Protocol check box and click OK.
6. Click Next to initiate the installation.
7. After the installation completes and from the Control Panel, double-click on Administrative Tools.
8. Double-click on Computer Management.
9. In the navigation tree on the left, expand Services and Applications, then click on Services.
10. In the Services contextual frame, scroll down to SNMP Service, then double-click SNMP Service.
11. In the General tab, select Automatic for Startup Type.
12. In the Security tab, do one of the following:
• Leave the default community name public.
• To improve security, choose your own name. Click on Add... for accepted community names, leave Community Rights as Read-Only, pick a secure Community Name, and click on OK. Remove the public entry. Modify the default Discovery properties configuration file to match this value.
13. In the Security tab, choose which IP addresses can access the SNMP service. You must choose at least the IP address of the Master Server that runs APTARE StorageConsole.
14. In the Agent tab, specify the values for all fields, and select the Internet check box to make all SNMP values available.
Enabling SNMP for Red Hat Linux
Red Hat Linux has an SNMP agent, ucd-snmp, preinstalled. Ucd-snmp is the pre-cursor to net-snmp. You need to configure the ucd-snmp agent to return the host resource information and to ensure that it executes at system startup. This procedure provides the steps for enabling SNMP in a Red Hat Linux environment.
To enable SNMP for Red Hat Linux:
1. Locate the SNMPD configuration file in /etc/snmp/snmpd.conf and the executable at /usr/sbin/snmpd.
2. Configure the SNMP agent as shown in the following example, which shows read-only access to the system and host resource storage portions of the MIB.
####
# First, map the community name "public" into a "security name"
# sec.name source community
com2sec notConfigUser default public
####
# Second, map the security name into a group name:
# groupName securityModel securityName
group notConfigGroup v1 notConfigUser
group notConfigGroup v2c notConfigUser
####
# Third, create a view for us to let the group have rights to:
# name incl/excl subtree mask(optional)
#view systemview included .1
view APTARE StorageConsole included
.iso.org.dod.internet.mgmt.mib-2.system fe
view APTARE StorageConsole included
.iso.org.dod.internet.mgmt.mib-2.host.hrStorage ff
view APTARE StorageConsole included
.iso.org.dod.internet.mgmt.mib-2.host.hrDevice ff
# .iso.org.dod.internet.mgmt.mib-2.system = .1.3.6.1.2.1.1
# .iso.org.dod.internet.mgmt.mib-2.host.hrStorage = .1.3.6.1.2.1.25.2
####
# Finally, grant read-only access to the system and storage portions of
the MIB2 tree
# group context sec.model sec.level prefix read write
notif
#access notConfigGroup "" any noauth exact systemview none
none
access notConfigGroup "" any noauth exact APTARE StorageConsole
none none
Enabling SNMP for HP-UX
Although HP-UX 11.00 has an SNMP agent installed, it does not provide access to the Host Resource MIB, so Discovery cannot use this agent to find storage units. However, net-snmp is supported on HP-UX 10.20, 11.00 and 11.11.
To install and configure SNMP for HP-UX 11.00:
1. Read the Net-SNMP HP-UX README.
2. Download and the net-snmp binaries
Enabling SNMP for Solaris 8/9
The Solstice Enterprise Agent does not support the Host Resource MIB, so Discovery cannot use this agent to find storage units. However, net-snmp is supported on Solaris 5.6, 5.7, 5.8, and 5.9.
To install and configure SNMP for Solaris:
1. Read the Net-SNMP Solaris README.
Enabling SNMP for Solaris 10
The Solaris System Management Agent (SMA) is an SNMP agent that Sun Microsystems offers, and it is based on the Net-SNMP open source implementation version 5.0.9.
To install and configure SNMP for Solaris 10:
1. Install the SMA packages just as you would install bundled products as outlined in the Solaris 10 Installation Guide: Basic Installations and in the Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
2. Configure the SMA agent as outlined in the Solaris System Management Agent Administration Guide.
Troubleshooting
If you have problems installing and configuring SMA, go to SunSolve.
Example—Installing Net-SNMP
Net-SNMP is an open source implementation of the Simple Network Management Protocol.
Net-SNMP provides an extensible agent for responding to SNMP queries for management information, and this functionality is important to the Media Discovery module Net-SNMP includes built-in support for a wide range of MIB information modules, specifically the Host Resource MIB. Net-SNMP is available for many Linux and Linux-like operating systems and also for Microsoft Windows, though functionality can vary depending on the operating system.
To install net-snmp:
1. Download and install Perl 5.6 or above, if you the package is not already installed.
2. Install net-snmp as outlined in the following example:
# /usr/local/bin/snmpconf -g basic_setup
*** Beginning basic system information setup ***
Do you want to configure the information returned in the system MIB group
(contact info, etc)? (default = y): no
Do you want to properly set the value of the sysServices.0 OID (if you don't know, just say no)? (default = y): no
*** BEGINNING ACCESS CONTROL SETUP ***
Do you want to configure the agent's access control? (default = y):
Do you want to allow SNMPv3 read-write user based access (default = y): no
Do you want to allow SNMPv3 read-only user based access (default = y): no
Do you want to allow SNMPv1/v2c read-write community access (default = y): no
Do you want to allow SNMPv1/v2c read-only community access (default = y): yes
Configuring: rocommunity
Description:
a SNMPv1/SNMPv2c read-only access community name arguments: community [default|hostname|network/bits] [oid]
The community name to add read-only access for: public
The hostname or network address to accept this community name from [RETURN for all]:
The OID that this community should be restricted to [RETURN for norestriction]:
Finished Output: rocommunity public
Do another rocommunity line? (default = y): no
*** Beginning trap destination setup ***
Do you want to configure where and if the agent will send traps? (default= y): no
*** Beginning monitoring setup ***
Do you want to configure the agent's ability to monitor various aspects of your system? (default = y): no
The following files were created:
snmpd.conf
3. Move the snpd.conf file to one of the following locations:
• If you want this file used by everyone on the system, moved the file to /usr/local/share/snmp. Next time, use the -i option if you want the command to copy the files to that location automatically.
• If you want the file for your personal use only, copy the file to your HOME directory. Next time, use the -p option if you want the command to copy the file to that location automatically.
4. Ensure that user root starts the snmpd executable that is located in /usr/local/sbin/snmpd.
Troubleshooting Net-SNMP Installations
The /usr/local/bin/snmpconf file requires Perl v5.6 and above.
Replace the line:
#!/usr/local/bin/perl
in /usr/local/bin/snmpconf to reference your Perl installation:
If your version of Perl is 5.0 or before then you might receive a runtime error when the snmpconf file executes. To correct this problem, edit the snmpconf file and make the following changes:
#!/usr/local/bin/perl
- if (! (-d "$opts{'I'}") && ! (mkdir ("$opts{'I'}"))) {
+ if (! (-d "$opts{'I'}") && ! (mkdir ("$opts{'I'}", 0755))) {
print "\nCould not create $opts{'I'} directory: $!\n";
print ("File $didfile{$i} left in current directory\n");
}
@@ -198,7 +198,7 @@
}
}
} elsif ($opts{'p'}) {
- if (! (-d "$home") && ! (mkdir ("$home"))) {
+ if (! (-d "$home") && ! (mkdir ("$home", 0755))) {
print "\nCould not create $home directory: $!\n";
print ("File $didfile{$i} left in current directory\n");
Note: