10-29-2015
Hp-dl580 g7 offline logs collection
Offline Log Collection Steps:-
A. Offline Test Report (3 Loop) .
1. Boot the server with Smart Start CD.
2. Select language - English.
3. Select Maintain server.
4. Select Diagnose Server.
5. In Test Tab
Test mode - Unattended.
Number of loops - 3.
Devices - All.
Select Complete test and click the begin test option and save the report after completing the test.
B. Survey Report.
1. Boot the server with Smart Start CD.
2. Select language - English.
3. Select Maintain server.
4. Select Diagnose Server.
5. In survey Tab
Select Category >> ALL.
Select View Level >> Advanced.
And save the report.
C. Offline IML logs.
1. Boot the server with Smart Start CD.
2. Select language - English.
3. Select Maintain server.
4. Select Diagnose Server.
5. In Log tab
Select Integrated Management Log and save the report.
D. Offline ADU report:
1. Boot the server with Smart Start CD.
2. Select language - English.
3. Select Maintain server.
4. Diagnose array Option.
5. Save the report.
Note: - To save the generated reports USB pen drive is needed.
5 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
I am trying to write a script which would go search and get the info from the logs based on yesterday timestamp and write yesterday logs in new file. The log file format is as follows:
""""""""""""""""""""""""""... (3 Replies)
Discussion started by: harish.parker
3 Replies
2. AIX
Hello,
I have about 200 different files that I need to get data from. Can someone help with a script that will:
1. Find the files
2. Parse the file for a specific number
3. collect a number to a file (probably)
4. add up the numbers
5. spit out the total.
Think it's possible?
BTW -... (3 Replies)
Discussion started by: bbbngowc
3 Replies
3. Solaris
Hi,
I have a HBA that is currently offline for some unknown reason. The device shows up in the prtdiag -v stating it is okay. How can I bring this back online? It was working okay until recently. It is currently connected to the SAN. Details below.
# fcinfo hba-port
HBA Port WWN:... (7 Replies)
Discussion started by: sparcman
7 Replies
4. Shell Programming and Scripting
Appreciate help for the below issue.
Im using below code.....I dont want to attach the logs when I ran the perl twice...I just want to take backup with today date and generate new logs...What I need to do for the below scirpt..............
1)if logs exist it should move the logs with extention... (1 Reply)
Discussion started by: Sanjeev G
1 Replies
5. UNIX for Beginners Questions & Answers
I need to write a python script that will
look at the local gc logs.
6 sys=0.00, real=0.06 secs]
2019-06-05T07:43:12.029-0500: 1072696.494: 2791209K->1995953K(2796544K)] 2803355K->1995953K(4164608K), , 3.0299555 secs]
2019-06-05T07:43:17.149-0500: 1072701.614: 3334321K->2008193K(4167680K),... (1 Reply)
Discussion started by: xgringo
1 Replies
LEARN ABOUT DEBIAN
log::any::test
Log::Any::Test(3pm) User Contributed Perl Documentation Log::Any::Test(3pm)
NAME
Log::Any::Test -- Test what you're logging with Log::Any
SYNOPSIS
use Test::More;
use Log::Any::Test; # should appear before 'use Log::Any'!
use Log::Any qw($log);
# ...
# call something that logs using Log::Any
# ...
# now test to make sure you logged the right things
$log->contains_ok(qr/good log message/, "good message was logged");
$log->does_not_contain_ok(qr/unexpected log message/, "unexpected message was not logged");
$log->empty_ok("no more logs");
# or
my $msgs = $log->msgs;
cmp_deeply($msgs, [{message => 'msg1', level => 'debug'}, ...]);
DESCRIPTION
"Log::Any::Test" is a simple module that allows you to test what has been logged with Log::Any. Most of its API and implementation have
been taken from Log::Any::Dispatch.
Using "Log::Any::Test" sends all subsequent Log::Any log messages to a single global in-memory buffer. It should be used before Log::Any.
METHODS
The test_name is optional in the *_ok methods; a reasonable default will be provided.
msgs ()
Returns the current contents of the global log buffer as an array reference, where each element is a hash containing a category, level,
and message key. e.g.
{
category => 'Foo',
level => 'error',
message => 'this is an error'
},
{
category => 'Bar::Baz',
level => 'debug',
message => 'this is a debug'
}
contains_ok ($regex[, $test_name])
Tests that a message in the log buffer matches $regex. On success, the message is removed from the log buffer (but any other matches
are left untouched).
does_not_contain_ok ($regex[, $test_name])
Tests that no message in the log buffer matches $regex.
empty_ok ([$test_name])
Tests that there is no log buffer left. On failure, the log buffer is cleared to limit further cascading failures.
contains_only_ok ($regex[, $test_name])
Tests that there is a single message in the log buffer and it matches $regex. On success, the message is removed.
clear ()
Clears the log buffer.
SEE ALSO
Log::Any, Test::Log::Dispatch
AUTHOR
Jonathan Swartz
COPYRIGHT & LICENSE
Copyright (C) 2009 Jonathan Swartz, all rights reserved.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.10.1 2009-12-08 Log::Any::Test(3pm)