EMS informational message

[Philip J. Priest_1]

Should i be concerned about messages from EMS like this one:

Event data from monitor:

Event Time..........: Sun Mar 27 03:03:55 2005
Severity............: INFORMATION
Monitor.............: dm_TL_adapter
Event #.............: 24
System..............: sgoraone.itsinc.com

Summary:
Adapter at hardware path 1/4/0/0 : Received a FCP Assists Frozen
completion message


Description of Error:


lbolt value: -1635956725

The Fibre Channel Driver received a FCP assists frozen completion
message


Probable Cause / Recommended Action:

The Tachyon TL adapter generated an interrupt indicating that
the FCP Assists have been frozen. This is caused by the driver
requesting the Tachyon TL chip to freeze the FCP Assists.
No action required. Informative message. The driver will recover
from this condition

Phil

[RAC_1]

lbolt message makes me think that it should be checked. Does fcmsutil /dev/tdx stat show everything OK??
Anything in syslog/dmesg??

Anil

[Philip J. Priest_1]

Nothing in dmesg or syslog im afraid.....

Phil

[Denver Osborn]

I wouldn't worry about it. The "recommended" action even says no action required. The message is logged with the severity at "INFORMATION". The default for the monitor request should be to log events with severity of INFORMATION to /var/opt/resmon/log/event.log. Is that where you found the message? If you saw it in your syslog or emailed to root, I would either choose to ignore them if "no action required" or setup the monitor request to just log INFORMATION -vs- email to root or logging to the syslog.

Hope this helps,
-denver

[Steven E. Protter]

I'd keep an eye on it, maybe once run xstm on it and make sure the hardware is feeling warm and fuzzy.

If its something serious you will see words like SEVERE and SERIOUS in the EMS notation.

SEP

[Denver Osborn]

the lbolt part of the message just says how long the system was up when it logged the event. the lbolt itself isn't a concern either.

forgot to mention... use monconfig to view/change the monitor request if you need to.

/etc/opt/resmon/lbin/monconfig


-denver

[Philip J. Priest_1]

Yes /var/opt/resmon/log/event.log is where i see this message. Trying to track this down if it is something to be concerned about.

I agree the "no action requried" but just wanna be sure.

Phil

[Anthony Lennan · Accepted solution]

Hi Philip,

I see these errors almost every day on our Dataprotector cell server. They seem to occur when we're absolutely hammering the system with backups and too much data is trying to go through the fibre cards.

Generally they're not an issue but I have noticed that on occasions when we get these errors we also get I/O errors on our backups at the same time (within about 5 seconds after the EMS error) and then the backup fails.

These EMS errors and I/O errors in Omniback are the only link I've found so far. There are no errors in our syslog or any other logs I've found either.

I would have a look at what kind of data you're trying to push through your cards at the times your getting the errors and then evaluate if they are really causing an issue. If they are then you may need to look at load balancing across other cards. Otherwise I wouldn't worry about them.

Cheers,
Anthony

[Philip J. Priest_1]

thread closed