C Configuration Troubleshooting

Use this appendix to troubleshoot connections between the STA server and the library.

• "Troubleshooting Connection Tests and Data Collections"

• "Unsuccessful Trap Processing"

Note: This appendix assumes you are using the recommended SNMP v3 protocol for STA communications.

C.1 Troubleshooting Connection Tests and Data Collections

Use the following sections to troubleshoot library connection tests (as described in "Test the SNMP Connection to the Library") and "Get latest data" requests (as described in "Get the Latest Configuration Data From the Library").

• "MIB Walk Channel Test"

• "Trap Channel Test"

• "Media Validation Support Test"

C.1.1 MIB Walk Channel Test

The MIB Walk Channel test checks for library initialization, network connectivity, proper SNMP client settings, and correct library firmware. If this test fails, one or more of the following could be true:

• STA is not configured

• The library is not initialized

• The library firmware does not meet the minimum for STA

• There are network problems between the STA server and library

• A static IP address is not assigned to the STA server or library

• SNMP is not enabled on the library

• SNMP client settings do not match between STA server and library

To resolve the failure, perform troubleshooting steps on both the library and STA server, as follows.

C.1.1.1 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 between the library and server. (This command is not available on the SL150.)

   1. Log in to the library.

   2. Issue one of the following commands:

      • SL8500 and SL3000:

        traceRoute sta_server_IP_address
        

      • SL500:

        traceroute sta_server_IP_address
        

      The output shows the number of hops and the round-trip time to reach each hop. The round-trip time (the last line in the command output) should be less than one second. If it is not, confirm the network's performance with your network administrator.

3. Ensure that SNMP has been enabled on the public port (see "Enable SNMP on the Library").

4. Verify that there is one and only one SNMP v2c user (see "Ensure an SNMP v2c User").

5. Verify that the SNMP v3 user was added correctly:

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

   • To create a v3 user, see "Create an SNMP v3 User".

6. Ensure that a static IP address has been assigned to the library (see "Retrieve the Library IP Address").

7. After performing all other steps on both the library and STA server, consider deleting and re-adding the SNMP v3 user.

C.1.1.2 What to Check on the Server

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

2. Use the traceroute command to check communication between the server and library.

   1. Log in to the STA server.

   2. Issue the following command:

      traceroute -I library_IP_address_or_name
      

      The output shows the number of hops and the round-trip time to reach each hop. The round-trip time (the last line in the command output) should be less than one second. If it is not, confirm the network's performance with your network administrator.

3. Verify that the STA server can reach the library public port by pinging the primary IP address and, if applicable, the secondary IP address.

4. Verify that UDP ports 161 and 162 are enabled on all network nodes between the STA server and the library (see "Verify SNMP Communications With the Library").

5. 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").

6. Display the STA Monitored Libraries screen, and verify that the settings are correct for the library (see "Configure SNMP Connections With the Library").

C.1.2 Trap Channel Test

The Trap Channel test requests that the library send a test trap (13) to the STA server. If the test fails, STA will indicate the date and time when the last trap/inform was received. If the test fails or indicates "Unknown", one or more of the following could be true:

• The library firmware may not support the test trap

• The STA server may not be properly configured as a trap recipient on the library

• If you recently upgraded to STA 2.0.x, the STA server's IP address may not be specified in the connection details for the library.

To resolve:

1. Ensure the library is running the recommended (or higher) firmware shown in the STA Requirements Guide. Lower firmware versions may not support the test trap (13).

2. After upgrading to STA 2.0.x, ensure you have selected the STA server's IP address in the library's connection details. See Task 10, "Configure STA 2.0.x."

3. Use the snmp engineId (for SL500 libraries) or snmp engineId print (for SL3000 and SL8500 libraries) command to display the library engine ID. (Not applicable to SL150 libraries.)

4. Verify that STA is correctly configured as a trap recipient (see "Create an SNMP v3 Trap Recipient").

   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 SNMP > SNMP Trap Recipients.

   • Engine Id: Must match the library engine ID displayed in Step 3. 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).

   • 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. For SL500 libraries, verify the passwords do not contain single quotes as text.

   • Trap Level: Must include trap 13.

5. Verify that the library engine ID from Step 3 matches the value in the STA UI (Setup & Administration > Configuration > SNMP Connections > Monitored Libraries). If it does not match:

   1. Select the library in the Monitored Libraries list.

   2. Click the Edit button.

   3. Clear the Library Engine ID field, and then click Save.

   4. Perform a connection test to retrieve the library's engine ID (see "Test the SNMP Connection to the Library").

C.1.3 Media Validation Support Test

The Media Validation Support test checks for the correct firmware and configuration to enable media validation in STA. If the library model does not support media validation, the test will report Not Applicable. If the test is unsuccessful for a library that can support media validation, one or more of the following could be true:

• The library firmware does not support media validation

• SNMP v3 is not configured

• There are no drives in the media validation pool

• There are no empty or reservable drives in the media validation pool

To resolve:

1. See the STA Requirements Guide for the minimum library and drive firmware required for media validation.

2. Ensure you have an SNMP v3 user configured on both the library and STA server, and have configured the STA server to be a trap recipient on the library. Review the SNMP configuration steps in Chapter 4 and Chapter 5.

See the STA User's Guide for more information about configuring media validation.

C.2 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 STA server is using a static IP address.

2. Within a separate terminal window on the STA server, enter the following command as root:

   # 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 for ”Get Latest Data” requests will contain .snmp.

   • If there is activity on the library, but no traps are being received, then check the library trap recipient entry for accuracy (see "Trap Channel Test").

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.

   1. Check the /Oracle/Middleware/user_projects/domains/tbi/servers/staAdapter/logs/staAdapter.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.”

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

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

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

   1. Deconfigure SNMP services:

      # chkconfig snmpd off
      # chkconfig snmptrapd off
      

   2. Stop SNMP services:

      # service snmptrapd stop
      # service snmpd stop
      

   3. Stop and restart STA services:

      # STA stop all
      # STA start all
      

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.

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.

7. For SL500 and SL150 libraries, ensure the Volume Label Format is set properly:

   • "Set the SL500 Volume Label Format"

   • "Set the SL150 Volume Label Format and Drive Element Addressing Mode"