FS System: How to Manually Extract Some ILOM Log Files from a Pilot or Controller

Asset ID:	1-71-2389447.1
Update Date:	2018-05-07
Keywords:

Solution Type Technical Instruction Sure

Solution 2389447.1 : FS System: How to Manually Extract Some ILOM Log Files from a Pilot or Controller

Applies to:

Oracle FS1-2 Flash Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

To provide details on how to manually extract various log files from an ILOM.

Solution

Typically this information can be obtained via an ILOM snapshot. See KM Document 1963071.1 FS System: How to Collect an ILOM Snapshot from the Pilot or Controller for details. However there are times when it may not be possible to extract ILOM log information from an FS1-2 component. The steps below are equally applicable to Pilots, Controllers and even the MaxRep3 Engines. By entering the SESSION mode of restricted, some of the files from an ILOM snapshot can be accessed.

Enable ssh to Pilots:

# fscli login -u administrator -oracleFs <FQDN or IP address of FS1-2>
Password:

Login Successful

*****************************************************
**                                                 **
** This is a company computer system with access **
** restricted to those with proper authorization. **
** Authorized parties are restricted to those     **
** functions which have been assigned to perform **
** work related duties. Any unauthorized access **
** will be investigated and prosecuted to the     **
** full extent of the law. If you are not an     **
** authorized user, disconnect now.               **
**                                                 **
*****************************************************
# fscli system -modify -enableSsh <duration in minutes>

Command Succeeded

#

See KM Document 2029847.1 FS System: How to Enable SSH Access to the Pilot for more details.
Using PuTTY (or similar software), enable logging to capture screen output and ssh to active Pilot using the shared or public IP address of the FS1-2.
If collecting logs from a Controller, ssh to a Controller (172.30.80.128/172.30.80.129 for Controller 1 or Controller 2 respectively).
ssh to the appropriate ILOM where needed logs are:
- ssh to 169.254.2.5 (to access that node's ILOM)
- ssh to 169.254.2.9 (to access that node's ILOM buddy).
Enter restricted mode:

-> set SESSION mode=restricted

WARNING: The "Restricted Shell" account is provided solely
to allow Services to perform diagnostic tasks.

[(restricted_shell) ORACLESP-1315FM####:~]#
There are two directories from which logs can be read, log and persist:

[(restricted_shell) ORACLESP-1315FM####:~]# ls
bin/ log/ misc/ persist/
The following files (or files in directories) marked with two asterisks are readable:

[(restricted_shell) ORACLESP-1315FM####:~]# ls log
dmesg**         lumain.log      networking**      usrmgt.log**
ealertd.log**   lumain.log.1    snmpd.err.log**
htsignon**      messages**      snmpd.log**
ipv6_proxy.log messages.1**    ssl_proxy.log**
[(restricted_shell) ORACLESP-1315FM2008:~]# ls persist
available_power**        ilom.rnd               psn-cache**
conf.v3.1.tgz            local/                 psnc_backup1
faultdiags/**            logmgr.log             psnc_backup2
fips.conf**              logmgr.log.1           psnc_primary
frutemp/                 logmgr_audit.log       replicated/**
fruwrites/               logmgr_audit.log.1     sensorhistory/**
host-boot-device-list** logmgr_sdm.log         servicetag.xml**
host_debug_err.log**     logmgr_sdm.log.1       spd_cache/**
host_debug_err.log.1** memstore               tmp/
host_logs/               minimum_power**        uefi-expert-mode.xml**
hostconsole.log**        permitted_power        uefi-normal-mode.xml**
hostconsole.log.1**      pod_db/**              ueficfg_state**
hwconfig_power**         pseudofru/**           urandom/
[(restricted_shell) ORACLESP-1315FM####:~]#
Use cat, more or less to dump the contents of logs:

[(restricted_shell) ORACLESP-1315FM####:~]# cat persist/hostconsole.log
TDS: logextract get filename for backup log
tds_directory_find() returned error
tds_get_filename(): filename: 000000.000000-000000.000000.GMT.xx-xx use_backup flag: 1
TDS: tds_dump_logs get backup log with name 000000.000000-000000.000000.GMT.xx-xx
++++ Dump backup TDS memory
Backup memory is empty. No logfile generated.
++++ Dump backup TDS memory -- DONE

USER TDS flag written

sending incremental file list
slammer/
slammer/508002000######0/
slammer/508002000######0/var_log/
...
num_drives = 0
Controller PN:7051791
Controller SN:489089M+130329004Y
Chassis SN:1315FM####
Sending event 66(0x40042) to mcc...
num_drives = 0
Controller PN:7051791
Controller SN:489089M+130329004Y
Chassis SN:1315FM####
[(restricted_shell) ORACLESP-1315FM####:~]#
Exit out of the FS1-2

[(restricted_shell) ORACLESP-1315FM####:~]# exit
exit

-> exit
WN508002000#######0 # exit
[root@pilot1 ~]#

Attachments

This solution has no attachment