SCA Appliance
Ever wonder what happens when you run a supportconfig -ur SR#? The support config gets uploaded and analyzed by a Support Config Analysis server that runs potentially over 900 support patterns to analyze the support configs contents. The report is then posted to the SR listing critical issues than when fixed have been found to fix roughly 50% of the issues an SR was created for.
The Support Config Analysis server is available for download as an appliance than can be ran on premises. The appliance stores analysis results in a MariaDB database and uses PHP to read the database and generate the report. It has a FTP server allowing for support configs to be uploaded, archived, processed, and analyzed. With this it is possible to modify the supportconfig script to gather more information for other applications running on the server and… Continue reading
How To Register OES and SLES Servers Using Command Line and a Script
It is important to keep your servers at the current patch level. Usually there are many bugs fixed and if you come across a new issue it helps Novell Support the the Developers.
I like to use the command line to register my servers. It is easy and relatively fast compared to the GUI. Even easier is to use a script. Just copy the script to the server, modify the e-mail account and registration codes and run the script. If something happens to the update services and repositories just run the script to clean up the old and re-register.
Below is a video demonstrating the register.sh script
TID 3030847 goes over the command line process.
Note: do not include < > for email or regcodes in the examples below
The command to register a OES server is
suse_register -a email=<user@email.com> -a regcode-sles=<your sles code>… Continue reading
VMWare and best practices for Timekeeping
Lately I’ve been getting a lot of requests for timekeeping best practices for VMWare
VMWare has a great support article on this. Below are the SLES recommendations. The article can be found here
| SLES 11 (All updates) | No additional kernel parameters required. | |
| SLES 10 SP4 on ESX 5.0 and later | clock=pmtmr hpet=disable |
|
| SLES 10 SP4 on ESX 4.x | Use a VMI enabled kernel. | |
| SLES 10 SP3 on ESXi 5.0 | clock=pmtmr hpet=disable |
|
| SLES 10 SP3 on ESX 3.5 and 4.x | Use a VMI enabled kernel. | |
| SLES 10 SP3 on ESX 3.0.x and earlier | clock=pmtmr hpet=disable |
|
| SLES 10 SP2 on ESXi 5.0 | clock=pmtmr hpet=disable |
|
| SLES 10 SP2 on ESX 3.5 and 4.x | Use a VMI enabled kernel. | |
| SLES 10 SP2 on ESX 3.0.x and earlier | clock=pmtmr hpet=disable |
|
| SLES 10 SP1 | clock=pmtmr hpet=disable |
|
| SLES 10 | clock=pmtmr hpet=disable |
|
| SLES 9 (All updates) | clock=pmtmr hpet=disable |
|
| SLES 8 | No additional kernel parameters required.… Continue reading |
Creating a SLES11 Install source
Creating an install source is extremely easy to do with YaST. Just follow the installation server wizard.
To create a single SLES+OES DVD follow Simon’s Coolsolution Article