Troubleshooting

Dell™ Embedded Remote Access/MC User's Guide

The section helps you diagnose and possibly solve problems that may occur with your ERA/MC controller.

Using the Controller Trace Log

The internal controller Trace Log can be used by administrators needing to debug alerting or networking from the controller. The Trace Log can be accessed from the RAC home page by clicking the Debug tab, and then clicking Network Debug. From the Network Debug window, select Dump Trace Log, and then click Submit. The Trace Log tracks the following information:

DHCP – Traces packets sent to and received from a DHCP server.

NOTE: Settings for DHCP, can be accessed from the Web-based interface by clicking the Debug tab, and then clicking Trace Log.

NOTE: In the controller Trace Log, nonprintable ASCII characters are translated to printable ASCII characters. If the character code is less than 0x20, or between 0x7f and 0xa0 (inclusive), the value 0x40 is exclusive, ordered with the character before printing, after a "^" is added to the beginning. Thus, the ASCII carriage return character, 0xd, is printed as "^M" in the Trace Log. Nonprintable ASCII characters may occur during tracing of the CHAT and TAP protocols, and occasionally during PPP negotiations.

Troubleshooting Network Problems

The controller provides a standard set of network diagnostic tools, similar to those found on systems running the Microsoft® Windows® or Red Hat Linux-based operating systems. Using the RAC home page, you can access the following network debugging tools by clicking the Debug tab and then clicking Network Debug. For more information about the Network Debug feature, see the Web-based remote access interface help.

The trace log may also contain controller operating-system specific error codes (relating to the internal controller operating system, not the managed system's operating system). Table C-1 can help you diagnose network problems reported by the internal RAC operating system.

Table C-1. Controller Network Error Codes

Error Code	Description
0x5006	ENXIO: No such address.
0x5009	EBADS: The socket descriptor is invalid.
0x500D	EACCESS: Permission denied.
0x5011	EEXIST: Duplicate entry exists.
0x5016	EINVALID: An argument is invalid.
0x5017	ENFILE: An internal table has run out of space.
0x5020	EPIPE: The connection is broken.
0x5023	EWOULDBLOCK: The operation would block; socket is nonblocking.
0x5024	EINPROGRESS: Socket is nonblocking; connection not completed immediately.
0x5025	EALREADY: Socket is nonblocking; previous connection attempt not complete.
0x5027	EDESTADDRREQ: The destination address is invalid.
0x5028	EMSGSIZE: Message too long.
0x5029	EPROTOTYPE: Wrong protocol type for socket.
0x502A	ENOPROTOOPT: Protocol not available.
0x502B	EPROTONO SUPPORT: Protocol not supported.
0x502D	EOPNOTSUPP: Requested operation not valid for this type of socket.
0x502F	EAFNOSUPPORT: Address family not support.
0x5030	EADDRINUSE: Address is already in use.
0x5031	EADDRNOTAVAIL: Address not available.
0x5033	ENETUNREACH: Network is unreachable.
0x5035	ECONNABORTED: The connection has been aborted by the peer.
0x5036	ECONNRESET: The connection has been reset by the peer.
0x5037	ENOBUFS: An internal buffer is required but cannot be allocated.
0x5038	EISCONN: The socket is already connected.
0x5039	ENOTCONN: The socket is not connected.
0x503B	ETOOMANYREFS: Too many references, cannot splice.
0x503C	ETIMEDOUT: Connection timed out.
0x503D	ECONNREFUSED: The connection attempt was refused.
0x5041	EHOSTUNREACH: The destination host could not be reached.
0x5046	ENIDOWN: NI_INIT returned -1.
0x5047	ENMTU: The MTU is invalid.
0x5048	ENHWL: The hardware length is invalid.
0x5049	ENNOFIND: The route specified cannot be found.
0x504A	ECOLL: Collision in select call; these conditions already selected by another task.
0x504B	ETID: The task ID is invalid.

Troubleshooting Alerting Problems

Use the following information to troubleshoot a particular type of controller alert:

E-mail paging – E-mail paging uses SMTP. To troubleshoot e-mail paging problems, check SMTP entries in the trace log. All interactions with the SMTP server are logged in the Trace Log by default.
SNMP traps – SNMP trap deliveries are logged in the Trace Log by default. However, since SNMP does not confirm delivery of traps, it is best to trace the packets on the managed system using a network analyzer or a tool such as Microsoft's snmputil.

Controller Log Messages

RAC Log messages can be used by administrators to debug alerting from the controller. Table C-2 provides a list of controller log message IDs, message and description, as well as corrective actions to take for a particular message.

NOTE: In Table C-2, the character "L" is sometimes used in the Message ID column. "L" represents the severity level or type of the message, which can be one of the following: W (warning), E (error), S (severe), F (fatal), or A (always).

Table C-2. RAC Log Messages

Message ID	Description	Corrective Action
RAC186L	dhcp: no response from server, need LAN address. The management Ethernet port cannot be enabled until a response is received from the DHCP server.	Informational only. No specific corrective action is indicated. Ensure that the DHCP server is operational.
RAC187L	dhcp: no response from server, using default PPP addresses.	Provides information only. No specific corrective action is indicated. Ensure that the DCHP server is operational.
RAC188L	dhcp: no response from server, warm starting with <IP address>.	Provides information only. No specific corrective action is indicated. Ensure that the DHCP server is operational.
RAC189L	snmp: trap sent to <IP address>.	Provides information only. No corrective action is necessary.
RAC191L	snmp: internal failure during trap generation.	Reset the controller and retry the operation.
RAC199L	E-mail paging attempts failed, SMTP protocol failure.	A trace of the SMTP connection may be found in the trace log. Examine the trace log to identify the source of the protocol failure, such as the connection could not be established (SMTP server is down or an invalid IP address), an invalid e-mail destination address, an invalid domain in the e-mail address, or the SMTP server does not support forwarding e-mail. Correct the problem and try again.
RAC200L	E-mail paging encountered an internal error.	Reset the controller and retry the operation.
RAC253L	PAP peer authentication succeeded for <user>. CHAP peer authentication succeeded for <user>.	Provides information only. No corrective action is necessary.
RAC254L	PAP peer authentication failed for <user>. CHAP peer authentication failed for <user>.	Verify that the dial-in or demand dial-out entry remote user name and password are correct. This user name and password are used for the PPP connection only, and are not an administrator log in user name and password.
RAC256L	RAC hardware log event: <formatted hardware log event>.	Provides information only. No corrective action is necessary, unless the contents of the hardware log indicate a problem. In this case, the corrective action is based on the problem reported; for example, battery voltage low indicates that the battery may need replacing.
RAC016A	RAC log cleared.	Provides information only.
RAC030A	RAC time was set.	Provides information only.
RAC048A	RAC firmware update was initiated.	Provides information only.
RAC049A	RAC firmware update was initiated with config to defaults option.	Provides information only.
RAC065A	RAC hard reset, delay <seconds> was initiated.	Provides information only.
RAC066A	RAC soft reset, delay <seconds> was initiated.	Provides information only.
RAC067A	RAC reset, delay <seconds> was initiated.	Provides information only.
RAC068A	RAC cfg2default reset, delay <seconds> was initiated.	Provides information only.
RAC069A	RAC shutdown was initiated.	Provides information only.
RAC114A	Requested server module {powerdown\|powerup\| powercycle\|hardreset\|.	Provides information only.
RAC122A	RAC booted.	Provides information only.
RAC138A	Console redirect session enabled.	Provides information only.
RAC139A	Console redirect session disabled.	Provides information only.
RAC154A	Logout from <IP address>.	Provides information only.
RAC155A	Login from <IP address>.	Provides information only.
RAC156A	Session cancelled from <IP address>, maximum log in attempts exceeded.	Provides information only.
RAC157A	Session cancelled from <IP address>, due to inactivity.	Provides information only.
RAC158A	Unvalidated session from <IP address> cancelled.	Provides information only.
RAC175A	vt-100: log in {successful\|authentication failed}.	Provides information only.
RAC240A	RAC shut down through hwmon.	Provides information only.
RAC242A	RAC shut down due to voltage below threshold.	Provides information only.

Back to Contents Page