When working with Exadata, you will eventually have to provide an ILOM snapshot to support.
The procedure is described in this documentation but honestly it was not really clear to me before I did it as the procedure does not show real examples.
Before describing a real example from an ILOM snapshot taken from a production cell, one point is worth to be mentioned here :
- A full ILOM snapshot (which is the one Oracle support will most likely ask you) may (yes, "may") reset the host as per the documentation :
Note - Using this option might reset the host operating system.
"Reset the host" meaning rebooting the host.
I did it few times on production cells and they have never been rebooted but this is something to keep in mind if you are asked to take a full ILOM snapshot of a database server. Indeed, a cell reboot would be transparent but this is a different story with a database server.
Unless a full snapshot is specifically required by Oracle Support, I recommend to take a normal ILOM snapshot instead of a full which is 99% of the time enough to troubleshoot an issue (and no resest host risk).
Having said that, one more thing before describing the procedure itself is to check what is needed to proceed :
- The name of the target you want to take the snapshot on; in my example I'll take it on "myclustercel07"
- An access to the target's ILOM: here "myclustercel07-ilom"
- The ILOM root password (default is welcome1)
- The IP address of the host you want to store the ILOM on (it will be 10.11.12.13 in the below example); I personally use the database server 1 for this purpose : "myclusterdb01"; just ping it to get its IP as the ILOM won't resolve the hostname
First of all, let's connect and set the snapshot type to full :
[root@myclusterdb01 ~]# ssh myclustercel07-ilom
Password:
Oracle(R) Integrated Lights Out Manager
Version 3.2.7.30.a r112904
Copyright (c) 2016, Oracle and/or its affiliates. All rights reserved.
Warning: HTTPS certificate is set to factory default.
Hostname: myclustercel07-ilom
-> set /SP/diag/snapshot dataset=full # or "normal" for a non full ILOM snapshot
Set 'dataset' to 'full'
->
Then start the ILOM snapshot using the IP of the target system we will put the ILOM on and its root password (it'll copy the ILOM snapshot in /tmp in the below example) :
-> set /SP/diag/snapshot dump_uri=sftp://root@10.11.12.13/tmp Collecting a "full" dataset may reset the host. Are you sure (y/n)? y Enter remote user password: ************ Set 'dump_uri' to 'sftp://root@10.11.12.13/tmp' ->
An alternative syntax with the password in the command line is also an option :
-> set /SP/diag/snapshot dump_uri=sftp://root:root_password@10.11.12.13/tmp Collecting a "full" dataset may reset the host. Are you sure (y/n)? y Set 'dump_uri' to 'sftp://root@10.11.12.13/tmp' ->
Now that the ILOM snapshot has been started, you can monitor it using the below command :
-> show /SP/diag/snapshot /SP/diag/snapshot Targets: Properties: dataset = full dump_uri = (Cannot show property) encrypt_output = false result = Running Commands: cd set show ->
After few minutes you should see the ILOM snapshot as completed :
-> show /SP/diag/snapshot
/SP/diag/snapshot
Targets:
Properties:
dataset = full
dump_uri = (Cannot show property)
encrypt_output = false
result = Collecting data into sftp://root@10.11.12.13/tmp/myclustercel07-ilom_1133FMM02D_2018-02-04T23-18-06.zip
Snapshot Complete.
Done.
Commands:
cd
set
show
->
This is actually quite a small file easy to transfer to MOS :
[root@myclusterdb01 ~]# du -sh /tmp/myclustercel07-ilom_1133FMM02D_2018-02-04T23-18-06.zip 2.5M /tmp/myclustercel07-ilom_1133FMM02D_2018-02-04T23-18-06.zip [root@myclusterdb01 ~]#[root@myclusterdb01 ~]#
Et voila !
No comments:
Post a Comment