31 March 2021

Online Events about Oracle Solaris 04/2021

April 13th, 2021   9:00 am -  11:00 am PT
 

Oracle Webinar: Systems Engineering Forum Oracle Solaris and SPARC

Modernizing Enterprise Infrastructure with Oracle Solaris and SPARC
Simplifying Security and Compliance with Oracle Solaris (Incl. Demo)
Continuous Observability of Systems and Applications on Oracle Solaris (Incl. Demo)


April 27th, 2021    9:00 AM IST | 11:30 AM SGT | 1:30 PM AEST


Oracle Webinar: Infrastructure Modernization Forum: Oracle SPARC & Solaris

Oracle Compute Platforms for On-Prem Deployments

During this virtual event you will learn the vision and strategy of
Oracle Solaris and SPARC servers and more.


05 March 2021

Do you have the overview of your Solaris server patch levels?

To have updated systems is very important for security and stability reasons.

Oracle releases patch updates each quarter for Solaris 10 and Solaris 11.3 till 01/2024.
This patches only fix the most important issues, but not all.
To receive this patches for the older Solaris releases you need Extended Support.

It is highly recommended to update to the current Solaris 11.4 release.
For Solaris 11.4 there is a SRU (Support Repository Update) each month.

Make sure you know which Solaris server are not yet on the recommended level.

With our JomaSoft VDCF management tool for Solaris you have a good realtime overview of the Levels.


Learn more about VDCF
bitly.com/jomasoft



 


04 March 2021

Online Events about Oracle Solaris 03/2021

Mar 10, 2021 09:00 - 10:00 CET

Oracle Webinar: Oracle Solaris Update

This webinar will give an update on the Oracle Solaris operating system recent advancements. There is a specific focus on the observability in Solaris and compliance in Solaris. These will help you to improve the performance and secure compliance to regulatory requirements like PCI DSS for example. The webinar consists of a presentation and demonstrations of these features. 

 

 

Mar 16, 2021 19:00 - 20:30 CET

FRAOSUG - Frankfurt Area OpenSolaris User Group: Virtual Datacenter Cloud Framework

German/Deutsch

Das “Virtual Datacenter Cloud Framework” (VDCF ) ist seit 2006 verfügbar, inzwischen in der Version 8.1. Es deckt den ganzen Life Cycle von Solaris Systemen ab und unterstützt die SPARC und x86 Platform. Mittels einer Handvoll intuitiver Befehle können virtuelle Solaris Umgebungen auch von unerfahrenen Solaris Administratoren erstellt und betrieben werden.


15 February 2021

Oracle LGWR is not running at highest priority

The Oracle database does automatically increase the priority on Solaris if you run
the database version 11.2.0.4 or later. On older versions this does not happen.


If you are on Oracle 12.1.0.2 it could be because of Bug
27092821 - IN 12C CRITICAL DATABASE PROCESSES ARE NOT RUNNING WITH HIGHER PRIORITIES IN FSS
It is fixed in 12.1.0.2.99


If you run the Oracle database in a Solaris Zone, make sure you have 'proc_priocntl' set in limitpriv in your zonecfg. This is required to allow the change of the priority inside the zone.


Ideally the ora_lwgr_x process should run in the FX class with prio 60.
This can be verified using

ps -efcZ | grep lgwr




19 December 2020

Does your system contain the fixes for CVEs or are you vulnerable?

On Solaris 11 the software packages are stored in a IPS repository.
One of the packages is 'solaris-11-cpu'.

If a CVE is fixed Oracle adds the CVE info into this package as metadata.

That's great. You can easly search for a CVE to find out which
package and Solaris Update contains the fix.

Current sample for CVS-2020-14871 "component: Pluggable authentication module"

-bash-5.0$ pkg search :CVE-2020-14871:
INDEX          ACTION VALUE              PACKAGE
CVE-2020-14871 set    pkg://solaris/consolidation/osnet/osnet-incorporation@11.4,5.11-11.4.25.0.1.75.3 pkg:/support/critical-patch-update/solaris-11-cpu@2020.12-1
CVE-2020-14871 set    pkg://solaris/consolidation/osnet/osnet-incorporation@11.4,5.11-11.4.25.0.1.75.3 pkg:/support/critical-patch-update/solaris-11-cpu@2020.9-2
CVE-2020-14871 set    pkg://solaris/consolidation/osnet/osnet-incorporation@11.4,5.11-11.4.25.0.1.75.3 pkg:/support/critical-patch-update/solaris-11-cpu@2020.11-1
CVE-2020-14871 set    pkg://solaris/consolidation/osnet/osnet-incorporation@11.4,5.11-11.4.25.0.1.75.3 pkg:/support/critical-patch-update/solaris-11-cpu@2020.10-2
CVE-2020-14871 set    pkg://solaris/consolidation/osnet/osnet-incorporation@11.4,5.11-11.4.27.0.1.82.2 pkg:/support/critical-patch-update/solaris-11-cpu@2020.12-1
CVE-2020-14871 set    pkg://solaris/consolidation/osnet/osnet-incorporation@11.4,5.11-11.4.27.0.1.82.2 pkg:/support/critical-patch-update/solaris-11-cpu@2020.11-1
CVE-2020-14871 set    pkg://solaris/system/library@0.5.11,5.11-0.175.3.36.0.22.0    pkg:/support/critical-patch-update/solaris-11-cpu@2020.6-2
CVE-2020-14871 set    pkg://solaris/system/library@0.5.11,5.11-0.175.3.36.0.22.0    pkg:/support/critical-patch-update/solaris-11-cpu@2020.12-1
CVE-2020-14871 set    pkg://solaris/system/library@0.5.11,5.11-0.175.3.36.0.22.0   pkg:/support/critical-patch-update/solaris-11-cpu@2020.8-2
CVE-2020-14871 set    pkg://solaris/system/library@0.5.11,5.11-0.175.3.36.0.22.0   pkg:/support/critical-patch-update/solaris-11-cpu@2020.9-2
CVE-2020-14871 set    pkg://solaris/system/library@0.5.11,5.11-0.175.3.36.0.22.0    pkg:/support/critical-patch-update/solaris-11-cpu@2020.11-1
CVE-2020-14871 set    pkg://solaris/system/library@0.5.11,5.11-0.175.3.36.0.22.0   pkg:/support/critical-patch-update/solaris-11-cpu@2020.10-2
CVE-2020-14871 set    pkg://solaris/system/library@0.5.11,5.11-0.175.3.36.0.22.0   pkg:/support/critical-patch-update/solaris-11-cpu@2020.7-2


This means you have the fix installed if you are on
Solaris 11.4  CPU 2020-09 or later which is S11.4 SRU 25

Users of our JomaSoft VDCF tool can list the systems centrally
where the required package is already installed

-bash-5.0$ vpkgadm -c show_server id=solaris/system/library@0.5.11-0.175.3.36.0.22.0

Package: system/library - Core system libraries
PKG-ID : solaris/system/library@0.5.11-0.175.3.36.0.22.0
Version: 0.5.11-0.175.3.36.0.22.0 is installed on:
   Name  Type     PatchLevel                GroupPkg       Comment
  g0062  Node     3.36.0.23.0 (U3.SRU36)    large-server   ZFS Cloning / Shared DS
  v0123  vServer  3.36.0.23.0 (U3.SRU36)    mini-server    ZFS Clones
  v0143  vServer  3.36.0.23.0 (U3.SRU36)    mini-server    Shared dataset

If the fix is not installed, it does not mean you are vulnerable in this special case,
because the bug has no impact on Solaris 11.1 or later.

This is documented here:
https://www.oracle.com/security-alerts/cpuoct2020.html#AppendixSUNS

Anyway ... make sure you are up-to-date ...


20 November 2020

Solaris 11.4 SRU27 with Zones Sheet on the Dashboard

Solaris 11.4 GA was released in 08/2018. Since then Oracle published an update (SRU) each month.


We are now at SRU27 (November 2020). This new SRU contains a bunch of new features.

My favorite is the Zones Sheet where you can see how the Resource Usage of your zones is. 

 



Check out all the other changes on the Oracle Solaris Blog

https://blogs.oracle.com/solaris/announcing-oracle-solaris-114-sru27


Many details on Twitter by Alan Coopersmith
https://twitter.com/alanc/status/1329196081041735682


02 November 2020

Solaris 11 Upgrade on Veritas Cluster with Failover Zones

For efficient Solaris 11 upgrades on Veritas Cluster do the following

1. Disable Evacuation of the Solaris Zones

/opt/VRTSvcs/bin/hagrp -modify myzone_sg Evacuate 0

After the Solaris 11 Upgrade and reboot the Zones are not evacuated to the other Cluster Node.

2. Double check AutoStartList

Check and set the AutoStartList of your Solaris Zones Service Group to make sure
the Zones are attached to the same Node they are currently running on.

/opt/VRTSvcs/bin/hagrp -modify myzone_sg AutoStartList node1 node2


With this setup you can upgrade your first node, reboot and verify all Zones are running fine.

pkg update --be-name s11.3.36 entire@0.5.11,5.11-0.175.3.36
init 6

If all is well with your Solaris Zones and Apps you can do the same with your second node.
 

And after all your nodes are upgraded you can enable Evacuation again.

/opt/VRTSvcs/bin/hagrp -modify myzone_sg Evacuate 1


Happy Upgrading ..