Hi, I’m newbie to SUSE Linux.
Currently, my working environment is require 2 new Linux 11 SAP SP3
This particular 2 server is isolate from internet network and my working environment is using Symantec Altiris to maintenance Windows Server patches.
Thus, i have install Symantec Altiris Agent on SUSE Linux and apply patches manually.
During applying software update, there’s a lot of software dependencies error encounter.
Any idea what’s best practice for me to perform patches in this environments?
I cant use ‘zypper update’ at all :mad: (no internet network allow)
I cant setup new and latest version of Linux SPx :mad: (there’s software requirement must maintenance to Linux 11 SAP SP3, cannot upgrade)
Hi, I’m newbie to SUSE Linux.
Currently, my working environment is require 2 new Linux 11 SAP SP3
This particular 2 server is isolate from internet network and my working
environment is using Symantec Altiris to maintenance Windows Server
patches.
Thus, i have install Symantec Altiris Agent on SUSE Linux and apply
patches manually.
During applying software update, there’s a lot of software dependencies
error encounter.
Any idea what’s best practice for me to perform patches in this environments?
I cant use ‘zypper update’ at all :mad: (no internet network
allow)
I cant setup new and latest version of Linux SPx :mad: (there’s
software requirement must maintenance to Linux 11 SAP SP3, cannot
upgrade)[/color]
If new to SUSE Linux and new servers can I ask why SLES11 SP3 for
SAP Applications and not “regular” SLES? Is SAP software in
play?
I’ll also note SLES11 SP3, with or without SAP, is out of General
Support so you should be installing SLES11 SP4 or SLES12
SP1.
Thanks you Simon for reply. Yes, there’s SAP module has been setup on SUSE 11 SAP SP3. Probably i will open a new post in SAP sub-forum for SAP advice.
I have one general question.
If we are attempting to patch SUSE Linux manually in my environment, what’s best practice to manage or resolve dependencies problem?
So far, i can think of is manually patch from early release date of Erratum like start from year 2013.
But, it will be total of 1788 rows of erratum update need to be apply… OMG
Thanks you Simon for reply. Yes, there’s SAP module has been setup on
SUSE 11 SAP SP3. Probably i will open a new post in SAP sub-forum for
SAP advice.
I have one general question.
If we are attempting to patch SUSE Linux manually in my environment,
what’s best practice to manage or resolve dependencies problem?
So far, i can think of is manually patch from early release date of
Erratum like start from year 2013.
[image: https://s21.postimg.org/hlkkhlq7b/suse_linux_patchine_ns.jpg]
But, it will be total of 1788 rows of erratum update need to be apply…
OMG[/color]
Are we still talking about the same new SLES11 SP3 for SAP Applications
server? I notice several of those patches in your screenshot reference
SLES11 SP2 … was your server upgraded from SP1 and/or SP2?
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
Yup, this’s kind like scan of missing software update for SLES11 SP3 for SAP(endpoint server hostname is linux-SUSE07).
This SUSE endpoint has been setup out of the box with SLES11 SP3 for SAP, never been upgraded from SP1 and/or SP2.
I have google ‘suse-7757’ only state
Affected Products:
SUSE Linux Enterprise Software Development Kit 11 SP2
SUSE Linux Enterprise Server 11 SP2 for VMware
SUSE Linux Enterprise Server 11 SP2
SUSE Linux Enterprise Desktop 11 SP2
So, in this case, i shall skip software update for slessp1 and slessp2?
Am 03.11.2016 um 19:34 schrieb fookyw87:[color=blue]
So, in this case, i shall skip software update for slessp1 and slessp2?
[/color]
To be frank, I would strongly suggest to rather skip that software you
use (did you say Symantec?) to patch those servers, as apparently it has
no clue what it’s doing.
Setup a SMT server instead.
CU,
Massimo Rosen
Micro Focus Knowledge Partner
No emails please! http://www.cfc-it.de
On 03/11/16 22:10, Massimo Rosen wrote:
[color=blue]
To be frank, I would strongly suggest to rather skip that software you
use (did you say Symantec?) to patch those servers, as apparently it has
no clue what it’s doing.[/color]
Yes it’s obvious the software is offering all available patches and not
just those that are applicable - you certainly don’t want to install
non-SP3 patches on a SP3 server plus you only want to install the SP3
patches that patch already installed packages (i.e. you don’t want to
install additional packages which themselves may need patching in the
future!).
[color=blue]
Setup a SMT server instead.[/color]
Seconded!
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
Hey Guys, really appreciate for the feedback and tips! Cheers!!!
Basically i’m regularity maintain more on Windows Server with Symantec NS. Probably, i will found a way to filter out patches just for ‘SLESSP3’.
And checking for SMT option as well.
Hey Guys, really appreciate for the feedback and tips! Cheers!!!
Basically i’m regularity maintain more on Windows Server with Symantec
NS. Probably, i will found a way to filter out patches just for
‘SLESSP3’.[/color]
If Symantec NS is just listing all SP3 patches without actually
checking they’re applicable to a particular server please don’t
use it.
[color=blue]
And checking for SMT option as well.[/color]
SMT is free so just requires a server, which can be virtual, with
storage. It’s by SUSE so understands your SLES servers.
If you don’t have any Micro Focus Open Enterprise Server (OES)
boxes I would either setup SMT11 SP3 on SLES11 SP4 pointing at
SUSE Customer Center (SCC) or use SLES12 SP1 which includes newer
SMT. If you do have OES you’ll need to setup SMT11 SP3 pointing
at Novell (Micro Focus) Customer Center (NCC).
environments?
environments?
