Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Troubleshooting RLM problems

Communication problems  Top

If there is a communication failure between the storage system and the RLM, search for EMS events titled:

[rlm.orftp.failed:warning]: RLM communication error, (reason)

Configuration problems  Top

If you are having difficulty configuring the RLM, view detailed configuration information and assign a new IP address by completing the following steps.

Step

Action

1

Verify the RLM is online and the IP configuration is correct by entering the following command:

toaster*> rlm status

2

If the RLM is configured using DHCP, reconfigure the RLM using a static IP address by entering the following command:

toaster*> rlm setup

Connection problems  Top

If you are having difficulty connecting to the RLM, check the connection by completing the following steps.

Step

Action

1

Verify you are using a secure shell client to connect to the RLM. For information on secure shell client applications, see Prerequisite for logging in to the RLM.

2

From the storage system, verify the RLM is online and the IP configuration is correct by entering the following command:

toaster> rlm status

3

From the administration host, test the network connection for the RLM by entering the following command:

ra_host> ping rlm_IP_address

If the ping fails:

  • Verify the RLM network port on the back of the storage system is cabled and active. For more information, see the Installation and Setup Instructions for your storage system.
  • Verify the RLM has a valid IP address. (At the storage system, enter the rlm setup command to use the DHCP server or assign a valid IP address.).
  • Verify the administration host has a route to the RLM.
4

From the storage system, reboot the RLM by entering the following command:

toaster> rlm reboot

Note
It takes approximately one minute for the RLM to reboot.

5

If the RLM does not reboot, repeat Steps 2 through 4. If the RLM still does not reboot, contact technical support for assistance.

RLM failures  Top

An RLM failure can occur for one of the following reasons:

If the RLM fails, search for EMS events titled:

[rlm.heartbeat.stopped:warning]: Have not received a Heartbeat from 
the Remote LAN Module in the last n seconds, (reason)

To troubleshoot an RLM failure, complete the following steps.

Step

Action

1

Run diagnostics by entering the following command from the CFE prompt:

CFE> boot_diags

Result

The diagnostics main menu appears.

Copyright (c) 1992-2005 Network Appliance, Inc.
Diagnostic Monitor v-4. 4x67
------------------------------------------------
all         Run all system diagnostics
mb          FAS3020 motherboard diagnostic
mem         main memory diagnostic
agent       agent & rlm diagnostic
cf-card     CompactFlash controller diagnostic
fcal        FCAL controller diagnostic
stress      System wide stress diagnostic

Commands:
Config      (print a list of configured PCI devices)
Default     (restore all options to default settings)
Exit        (exit diagnostics and return to firmware OK
              prompt)
2

From the main menu, enter the following option:

Enter Diag, Command or Option: agent

Result

The following RLM diagnostic menu appears.

Agent Diagnostic
--------------------------
 1: Comprehensive test       
 2: Appl-Agent interface test
 3: Appl PS On-Off test      70: Show Agent ring
                                 buffer info
 4: RLM Memory test          71: Show RLM info
 5: RLM Sensor test          72: Show Restart reason
 6: RLM-Agent interface test 
 7: RLM IRQ test
 8: RLM NMI test              91: Enable/disable looping
                              92: Stop/continue on
                                  error
11: RLM PS On-OFf test        93: Extended/Normal test
                              99: Exit

Select test or feature by number [0]:
3

From the RLM diagnostic prompt, enter test number 1 as shown:

Select test or feature by number [0]: 1

Note
It takes approximately ten minutes to complete this test.

Result

This initiates a comprehensive test that includes running tests 2 through 8, and 11. The results of each test are displayed.

4

Based on the results of Step 3, diagnose the problem. If the problem persists, reseat the RLM and repeat Steps 1 to 4.

If the problem still persists, replace the RLM.

RLM firmware update problems  Top

A firmware update failure can occur for one of the following reasons:

To troubleshoot a firmware failure, search for EMS events titled:

[rlm.orftp.failed:warning]: RLM firmware update failed, (reason)

Example

[rlm.orftp.failed:warning]: RLM firmware update failed: 
ORFTP couldn't send info.symlinks to RLM.

This error message indicates that the firmware update failure is due to a communication error.

Troubleshooting with the Data ONTAP CLI.

To troubleshoot updating the firmware using the Data ONTAP CLI, complete the following steps.

Step

Action

1

Verify the RLM is online by entering the following command:

toaster> rlm status

2

Update the firmware by entering the commands described at Using the Data ONTAP CLI.

Note
Verify you are using the correct filename (filename.zip) of the RLM firmware.

3

Reboot RLM by entering the following command:

toaster> rlm reboot

Note
It takes approximately one minute for the RLM to reboot.

4

If the RLM does not reboot, repeat Steps 1 through 3. If the RLM still does not reboot, contact technical support for assistance.

Troubleshooting with the RLM CLI

To troubleshoot updating the firmware using the RLM CLI, complete the following steps.

Step

Action

1

Verify the RLM is online by entering the following command:

toaster> rlm status

2

From a browser, access the RLM firmware file on your Web server.

Note
Verify you are using the correct filename (filename.tar.gz) of the RLM firmware.

3

Update the firmware by entering the following command.

RLM toaster> rlm update http://path_hostname/RLM.FW.tar.gz

If this command fails, replace the path_hostname with the correct IP address.

4

Reboot the RLM by entering the following command:

toaster> rlm reboot

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments