Chapter 5

Understanding Remote LAN Module messages

What the RLM does

The Remote LAN Module (RLM) is installed in FAS3000 series and C2300/C3000 NetCache appliance systems to provide remote platform management capabilities, including remote access, monitoring, troubleshooting, logging and alerting features. The RLM extends AutoSupport capabilities by sending alerts or "down system" notification through an AutoSupport Message when the system goes down, regardless of whether the system can send AutoSupport messages.

RLM-generated AutoSupport messages

These messages include the following information:

Subject line--A system notification from the RLM of the system, listing the system condition or event that caused the AutoSupport message and the log level.
In the message body--The RLM configuration and version information, the system ID, serial number, model number, and host name
In the zipped attachments--The System Event Logs, the system sensor state as determined by the RLM, and console logs. (Console logs can be committed by setting the autosupport.content option to minimal.)

Typical RLM-generated AutoSupport messages occur in the following conditions:

The system reboots unexpectedly
The System stops communicating with the RLM
A watchdog reset occurs
The system is power-cycled
Firmware POST errors occur
A user-initiated AutoSupport message occurs

RLM e-mail Notifications

RLM e-mail notifications are sent to configured recipients designated by the AutoSupport feature. The e-mail notifications have the title "System Notification from the RLM of <hostname>", followed by the message type.

RLM generated messages

Use the following table to look up messages sent by the RLM and the appropriate corrective actions.

RLM message	Explanation	Action
RLM heartbeat stopped	The system software cannot see the RLM.	Connect to the RLM CLI to check whether the RLM is operational. Contact technical support if the problem persists.
Reboot warning	The RLM detects an abnormal system reboot.	If this was a manually triggered or expected reboot, no action is necessary. Check the status of the appliance and determine the cause of the reboot. Contact technical support if the appliance fails to reboot.
Heartbeat loss warning	The RLM detects the system is offline, possibly because the system has stopped serving data.	If this system shutdown was manually triggered, no action is necessary. Check the status of your system and verify that the appliance and disk shelves are operational. Contact technical support if the problem persists.
Reboot (power loss) critical	The RLM detects that the appliance has lost AC power.	If you switched off the appliance before you received the notification, no action is necessary. Restore power to the appliance.
Reboot (watchdog reset) warning	The RLM detects a watchdog reset error.	Check the system to verify that it is operational. If your system is operational, run diagnostics on your entire system. Contact technical support if the appliance is not serving data.
System boot failed (POST failed)	The RLM detects that during POST a system error occurred and the system software cannot be booted.	Run diagnostics on your system. Contact technical support if running diagnostics does not detect any faulty components.
User_triggered (system power cycle)	A user is initiating a system power-cycle the through the RLM.	No action is necessary.
User_triggered (system power on)	A user is powering on the appliance through the RLM.	No action is necessary.
User_triggered (system power off)	A user is powering off the appliance through the RLM	No action is necessary.
User_triggered (system nmi)	A user is initiating a system core dump (nmi) through the RLM.	No action is necessary.
User_triggered (system reset)	A user is resetting the system through the RLM.	No action is necessary.
User triggered (RLM test)	The RLM received the RLM test command, which tests the RLM configuration.	No action is necessary.

EMS messages about the RLM

The following messages are EMS events sent to your console regarding the status of your RLM.

Name	Description	Corrective action
rlm.driver.hourly.stats	An error occurred while the system was trying to get hourly statistics from the RLM	Issue the `rlm status` command at the Data ONTAP prompt to check whether the RLM is online. If the RLM is operational and this message persists, issue the`rlm reboot`command at the data ONTAP prompts to reboot the RLM.
rlm.driver.mailhost	RLM setup verifies that a mailhost specified in options autosupport. mailhost can be reached. In this case, the RLM setup could not connect to the specified mailhost.	Verify the current value of the autosupport.mailhost using the `options autosupport.mailhost`command.If the autosupport.mailhost is not correct, set it to the correct value using the command `options autosupport.mailhost`mailhost- name. If mailhost name in the autosupport.mailhost is correct, there might be an incorrect entry corresponding to this mailhost in the /etc/hosts file. Verify and correct the associated IP address for this mailhost stored in /etc/hosts file. You can do this by mounting the root volume of your appliance on an administrative host and editing the /etc/hosts file under the root volume. You can also run the `setup` command again with correct IP address for mailhost.
rlm.driver.network.failure	There was a failure during the network configuration of the RLM. The RLM could not be assigned a DHCP or fixed IP address.	Check whether a network cable is correctly plugged into the RLM network port. Check the link status LED on the RLM. The RLM supports a 10/100 Ethernet network in auto negotiation mode. The network that the RLM is connected to needs to support auto negotiation to 10/100 speed or be running at one of those speeds for the RLM network connectivity to work.
rlm.firmware.update.failed	There was an error updating the RLM's firmware.	The `software install` command needs to be run with correct parameters before running the `rlm update` command. Run the following command to download the RLM firmware image before running the `rlm update` command: `software install http://pathto/RLM_FW.zip -f'` c Issue the `rlm status` command at the Data ONTAP prompt to check whether the RLM is still operational. Retry the RLM firmware update. If the failure persists, then contact technical support.
rlm.heartbeat.bootFromBackup	This event occurs when the RLM has been rebooted from its backup firmware by the appliance to restore RLM availability. When the appliance stops receiving heartbeat notifications from the RLM, the RLM is considered unavailable. To restore availability, the appliance first attempts to reboot the RLM from the RLM's primary firmware. If that fails, the appliance attempts to reboot the RLM from its backup firmware. If the reboot from backup firmware restores availability, (heartbeat notifications are received) this message is generated.	Update RLM firmware.
rlm.heartbeat.resumed	This event occurs when the appliance detects resumption of RLM heartbeat notifications indicating that the RLM is now available. The earlier issue indicated by the rlm.heartbeat.stopped event has been resolved.	No action is needed; this message is user-generated.
rlm.heartbeat.stopped	This event occurs when the appliance has not received an expected heartbeat message from the RLM. The RLM and the appliance exchange heartbeat messages so that they can detect when one or the other is unavailable.	Run diagnostics on the RLM. Run diagnostics on your system. If the problem persists, contact technical support.
rlm.orftp.failed	A communication error occurred while sending or receiving information from the RLM.	Issue the `rlm status` command at the Data ONTAP prompt to check whether the RLM is operational. If the RLM is operational and this message persists, issue the `rlm reboot` command at the Data ONTAP prompt to reboot the RLM. If this message persists after the RLM has been rebooted, contact technical support.
rlm.userlist.update.failed	There was an error while updating user information for the RLM. When user information is updated on Data ONTAP, the RLM is also updated with the new changes. This enables users to login to the RLM.	Issue the `rlm status` command at the Data ONTAP prompt to check whether the RLM is operational. If the RLM is operational and this message persists, issue the`rlm reboot`command at the Data ONTAP prompt to reboot the RLM. Retry the operation that caused the error message. If this message persists after the RLM is rebooted, contact technical support.