Disk Enclosures
cancel
Showing results for 
Search instead for 
Did you mean: 

P2000 G3 Event log message 401

CLEB
Valued Contributor

P2000 G3 Event log message 401

The internal event Id. Incremented for each event, ranging between 1 and connUnitMaxEvents. Not used as table index to simplify the agent implementation. When this reaches the end of the range specified by connUnitMaxEvents, the Id will roll over to start at one. This value will be set back to one at reset. The relationship of this value to the index is that internal event id may represent a smaller number than a 32 bit integer (eg max 100 entries) and would only have a value range up to connUnitMaxEvents. 22 The type of this event. status The description of the event. Event type: 401, Managed logs warning: A log region has reached its warning level and should be archived before log data is lost. (region: EC debug, region code: 8)

 

 

"401

Warning

The indicated log has filled to a level at which diagnostic data will be lost if not transferred to a

log-collection system.

Recommended actions

Transfer the log file to the log-collection system."

 

This is an error I am seeing in HP SIM and the description of the error from the HP P2000 G3 MSA System Event Descriptions Reference Guide.  As far as I know I don't have a log-collection system. How can this be cleared or resolved?

3 REPLIES
Jan Soska
Honored Contributor

Re: P2000 G3 Event log message 401

Hello,

maybe it is firmware issue - do you have latest installed?

 

jan

Godfred
Visitor

Re: P2000 G3 Event log message 401

Transferring log data to a log-collection system
If the log-management feature is configured in pull mode, a log-collection system can access the storage system’s FTP
interface and use the get managed-logs command to retrieve untransferred data from a system log file. This
command retrieves the untransferred data from the specified log to a compressed zip file on the log-collection system.
Following the transfer of a log’s data, the log’s capacity status is reset to zero indicate that there is no untransferred
data. Log data is controller specific.
For an overview of the log-management feature, see "About managed logs" (page 31).
Use a command-line-based FTP client; a GUI-based FTP client might not work.
To transfer log data to a log-collection system
1. In SMU, prepare to use FTP:
a. Determine the network-port IP addresses of the system’s controllers; see Changing network interface settings
on page 47.
b. Verify that the system’s FTP service is enabled; see Changing management interface settings on page 40.
c. Verify that the user you will log in as has permission to use the FTP interface; see Modifying users on page 43.
2. On the log-collection system, open a Command Prompt (Windows) or a terminal window (UNIX) and navigate to
the destination directory for the log file.
3. Enter:
ftp controller-network-address
For example:
ftp 10.1.0.9
4. Log in as a user that has permission to use the FTP interface.
5. Enter:
get managed-logs:log-type filename.zip
where:
• log-type specifies the type of log data to transfer:
• crash1, crash2, crash3, or crash4: One of the Storage Controller’s four crash logs.
• ecdebug: Expander Controller log.
• mc: Management Controller log.
• scdebug: Storage Controller log.
• filename is the file that will contain the transferred data. It is recommended to choose a filename that
identifies the system, controller, log type, and date.
For example:
get managed-logs:scdebug Storage2-A_scdebug_2011_08_22.zip
Wait for the message Operation Complete to appear.
6. Quit the FTP session.

 

Regards,

 

Sheron Godfred

AnkitM
Trusted Contributor

Re: P2000 G3 Event log message 401

Since, HP P2000 G3 doesn't have any component nor there is any private area on the storage unit where the logs collected over the period of times are saved. IMHO, it simply refers to that the events have reached a threshold where it will be overwritten and it won't be recovered again. 

 

Play with For Eg. If you type show events from [timestamp] you would know since, when the events are logged. If its since, the day P2000 was installed or if its notr required any more you can "clear event" or just let it be, it should over write the events.

 

Refer to: http://www.hp.com/go/p2000/manuals > General Reference > P2000 CLI Guide > Page Number 227 for more switches on show events command.

 

To be honest, its nothing to worry about! If you want to get rid of it.

1. Gather a fresh store.log [save/archieve it]

2. Type clear events both from CLI. :)

 

 

Was your question answered correctly? If so, please remember to mark your question Answered when you get the correct answer and award KUDOS! to the person providing the answer. This helps others searching for a similar issue.