Configuration Troubleshooting

Use this section to troubleshoot connections between the server on which STA is installed and the library.

•	“Troubleshoot an Unsuccessful SNMP Connection”

•	“Troubleshoot Unsuccessful Trap Processing”

▼	Troubleshoot an Unsuccessful SNMP Connection

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.

•	What to Check on the Library

•	What to Check on the Server

▼	What to Check on the Library

1.	Verify that the library is fully initialized. See “Verify the Library is Operational”.

2.	Use the `traceroute` command to check communication from the server to the library.

a.	Log in to the server on which STA is installed.

b.	Issue the following command:

# traceroute -I library_IP_address_or_name

Output will show the number of hops to the library, as well as the round-trip time to reach each hop. The round-trip time to the library (the last line in the command output) should be less than one second. If it is greater than one second, confirm the network’s performance with your network administrator.

3.	Use the `traceroute` command to check communication from the library to the server.

a.	Log in to the library, as described in “Log In to the Library”.

b.	Issue the following command, depending on the library type:

•	SL8500 and SL3000:

traceRoute sta_server_IP_address

•

SL500:

traceroute sta_server_IP_address

Note – On SL500 libraries, the traceroute command is available with FRS 1468 and above.

Output will show the number of hops to the server, as well as the round-trip time to reach each hop. The round-trip time to the server (the last line in the command output) should be less than one second. If it is greater than one second, confirm the network’s performance with your network administrator.

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 SL150 libraries, go to Settings > SNMP > SNMP Users.

6.	Verify that the SNMP v3 user was added correctly. (See “Create an SNMP v3 User” for details.)

•	On SL500, SL3000, and SL8500 libraries, use the `snmp listUsers` command to view a list of SNMP users.

•	On SL150 libraries, go to Settings > SNMP > 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.	Verify that STA has been correctly configured as a trap recipient. (See “Create an SNMP v3 Trap Recipient” for details).

•	On SL500, SL3000, and SL8500 libraries, use the `snmp listTrapRecipients` command to display a list of trap recipients on the library.

•	On SL150 libraries, go to Settings > SNMP > SNMP Trap Recipients.

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

Note – Checking the engine ID is not applicable to SL150 libraries, as the engine ID is automatically obtained.

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.

For SL150 libraries, go to Settings > Library to ensure Volume Label Format is set to “Trim last two characters”. See “Set the SL150 Volume Label Format”.

11.

If you find any data entry errors, use the appropriate commands to fix them, and then try the SNMP connection procedure again.

12.

As a last resort, after checking all other options on both the library and STA, consider deleting and re-adding the SNMP v3 user.

▼	What to Check on the Server

1.	Ensure the server on which STA is installed is using a static IP address.

The server cannot use a dynamically-assigned (DHCP) address.

2.	Verify that the library public port is reachable from the STA server by pinging the primary IP address and, if applicable, the secondary IP address.

3.	Display the STA SNMP Client Attributes screen, and verify that the settings exactly match the corresponding settings for the SNMP v3 user and SNMP v3 trap recipient on the library. See “Configure SNMP Client Settings for STA”.

•	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.	Display the STA Monitored Libraries screen, and verify that the settings exactly match the corresponding settings for the SNMP v3 user on the library. See “Configure SNMP Connections With the Library”.

•	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).

Note – Checking the engine ID is not applicable to SL150 libraries, as the engine ID is automatically obtained.

Note – When initially entering library details in the STA GUI, leave the Library Engine ID blank. It will be filled in by STA after you select the library and perform a "Test Connection".

5.	If you find any data entry errors, fix them on the appropriate screen, and then try the SNMP connection procedure again.

▼	Troubleshoot Unsuccessful Trap Processing

If traps are not being received by the STA host, or traps are not being processed by STA, perform the following.

1.	Ensure the server on which STA is installed is using a static IP address.

The server cannot use a dynamically-assigned (DHCP) address.

2.	Within a separate terminal window, enter the following command:

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

•	In the output, look for “.snmptrap” and “SNMPv3”. Network traffic that meets “Get Latest Data” requests will be “.snmp”.

•	If there is activity on the library, but no traps are being received, then check the library trap recipient entry for accuracy. See “Troubleshoot an Unsuccessful SNMP Connection”.

3.	Ensure SNMP port 162 is available for STA.

The STA trap listener processes traps through port 162. To troubleshoot communications over this port, do the following.

a.	Check the `/Oracle/Middleware/user_projects/domains/TBI/servers/staServer/logs/staServer.log` file for a “SEVERE” error, such as:

“SEVERE: SNMP Trap/Inform Listener Port 162 is NOT bindable. Stop the application currently bound to that port.”

b.	If port 162 is already in use, determine what process is using it:

# netstat -ap |grep -I snmp
# netstat -anp |grep ":162"

c.	Follow the process associated with the port or check what services may have started during system boot.

# chkconfig --list

4.	If snmpd or snmtrapd are running, then ensure that they are turned off permanently.

a.	Deconfigure SNMP services:

# chkconfig snmpd off
# chkconfig snmptrapd off

b.	Stop SNMP services:

# service snmptrapd stop
# service snmpd stop

c.	Stop and restart STA services:

# STA stop
# STA start

5.	If some traps are being reported in the Notifications screen, ensure that ALL trap levels were specified when creating a trap recipient on the library. See “Create an SNMP v3 Trap Recipient” for the list of supported trap levels.

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.

Configuration Troubleshooting

▼

Troubleshoot an Unsuccessful SNMP Connection

▼

What to Check on the Library

▼

What to Check on the Server

▼

Troubleshoot Unsuccessful Trap Processing