StorageTek Tape Analytics Configuration Guide, Version 1.0.2 |
E28378-04 |
Use the procedures below to troubleshoot an unsuccessful library SNMP connection test or data collection. The order you choose to perform these procedures is at your discretion. You can use the “STA / Library Configuration Parameters Worksheet” to help verify the correct configuration settings.
2.
|
Use the traceroute command to check communication from the server to the library.
|
# traceroute -I library_IP_address_or_name
3.
|
Use the traceroute command to check communication from the library to the server.
|
traceRoute sta_server_IP_address
•
|
traceroute sta_server_IP_address
Note – On SL500 libraries, the traceroute command is available with FRS 1468 and above.
4.
|
Use the snmp enable command to ensure that SNMP has been enabled on the public port. See “Enable SNMP on the Library”.
|
Note – This is not applicable to SL150 libraries. On SL150 libraries, SNMP is enabled by default.
5.
|
Verify that there is one and only one SNMP v2c user, if applicable. (See “Ensure an SNMP v2c User” to see if a v2c user is required in your case.)
|
•
|
On SL500, SL3000, and SL8500 libraries, use the snmp listUsers command to view a list of SNMP users.
|
•
|
On SL500, SL3000, and SL8500 libraries, use the snmp listUsers command to view a list of SNMP users.
|
Note – If you’re using SNMP v2c, see appendix “Configuring SNMP v2c Mode”.
Note – For SL500 libraries, verify the username or passwords do not contain single quotes as text.
Note – To verify SNMP communications, see “Verify SNMP Communications With the Library”.
Name – Must match the SNMP User Name on the STA SNMP Client Attributes screen, as well as the SNMP user specified when creating an SNMP trap recipient on the library.
Version – Must be v3.
Auth – Must be SHA.
Priv – Must be DES.
Auth Pass and Priv Pass – Must match the passwords on the STA SNMP Client Attributes screen, as well as the passwords specified when creating a trap recipient on the library.
7.
|
Use the snmp engineId (for SL500 libraries) or snmp engineId print (for SL3000 and SL8500 libraries) command to display the library engine ID.
|
Note – These commands are not applicable to SL150 libraries.
The entry must not contain any upper-case characters. For the SL8500 and SL3000 libraries, the entry must include the 0x prefix (the SL500 may also show this prefix). See “Create an SNMP v3 User”.
8.
|
•
|
On SL500, SL3000, and SL8500 libraries, use the snmp listTrapRecipients command to display a list of trap recipients on the library.
|
Note – If you’re using SNMP v2c, see appendix “Configuring SNMP v2c Mode”.
Note – For SL500 libraries, verify the passwords do not contain single quotes as text.
Engine Id – Must match the library engine ID displayed in Step 7. The entry must not contain any upper-case characters. For the SL8500 and SL3000 libraries, the entry must include the 0x prefix (the SL500 may also show this prefix). See “Create an SNMP v3 User”.
Host – IP address of the STA server.
Version – Must be v3.
Auth – Must be SHA.
Priv – Must be DES.
Auth Pass and Priv Pass – Must match the passwords on the STA SNMP Client Attributes screen, as well as the passwords specified when creating an SNMP user.
9.
|
For SL500 libraries, use the staConfig command to verify that “STA mode” has been enabled. See “Set the SL500 Volume Label Format”.
|
10.
|
The server cannot use a dynamically-assigned (DHCP) address.
3.
|
•
|
SNMP Connection User Name – User name you created for the SNMP v3 user and trap recipient on the library.
|
•
|
SNMP Connection Password – Connection authorization password for the SNMP v3 user and trap recipient on the library.
|
•
|
Privacy Encryption Password – Privacy encryption password for the SNMP v3 user and trap recipient on the library.
|
4.
|
•
|
Library Primary IP Address – IP address of the primary public port on the library. See “Retrieve the Library IP Address” for the correct entry.
|
•
|
Library Secondary IP Address – IP address of the secondary public port on the library, if applicable. For SL500 and SL150 libraries, this field is always blank. For SL3000 and SL8500 libraries, see “Retrieve SL3000 or SL8500 IP Addresses” for the correct entry.
|
•
|
STA IP Address – IP address of the STA server.
|
•
|
Library Engine ID – SNMP engine ID of the library. The entry must not contain any upper-case characters. For the SL8500 and SL3000 libraries, the entry must include the 0x prefix (the SL500 library may also show this prefix).
|
The server cannot use a dynamically-assigned (DHCP) address.
# tcpdump -v host library-public-port
•
|
library-public-port is the IP address of the primary public port on the library. See “Retrieve the Library IP Address” for the correct entry.
|
•
|
a.
|
Check the /Oracle/Middleware/user_projects/domains/TBI/servers/staServer/logs/staServer.log file for a “SEVERE” error, such as:
|
# netstat -ap |grep -I snmp
# netstat -anp |grep ":162"
# chkconfig --list
# chkconfig snmpd off
# chkconfig snmptrapd off
# service snmptrapd stop
# service snmpd stop
# STA stop
# STA start
5.
|
6.
|
For the SL500, ensure you configured the library with a supported version of SL Console. Earlier versions of SL Console restricted the number of trap level characters that could be entered. See “Library Software Requirements” in the STA Planning and Installation Guide for the minimum supported SL Console version.
|
Copyright © 2012, 2013 Oracle and/or its affiliates. All rights reserved. | Legal Notices |