I managed to install and get SMT installed.
Got the latest patches and installed on sles 11 sp2
now trying to connect the clients to use the local SMT server
after doing research, I couldn’t get it done, but finally it is working
I even get this message:
SMT Registration Report 2015-07-31 17:32 (localhost.site) – Registration successful
In the SMT management I can see the client with following messages:
[QUOTE]
There are some patches pending: ││
Optional patches: Status is unknown,
Package manager patches: Status is unknown,
Recommended patches: Status is unknown,
Security patches: Status is unknown[/QUOTE]
what do I need to do next ?
should I install the “smt client” software for client?
I managed to install and get SMT installed.
Got the latest patches and installed on sles 11 sp2
now trying to connect the clients to use the local SMT server
after doing research, I couldn’t get it done, but finally it is
working I even get this message:
SMT Registration Report 2015-07-31 17:32 (localhost.site) –
Registration successful
In the SMT management I can see the client with following messages:
There are some patches pending:
││
Optional patches: Status is unknown,
Package manager patches: Status is unknown,
Recommended patches: Status is unknown,
Security patches: Status is unknown
what do I need to do next ?
should I install the “smt client” software for client?[/color]
So my response to ecanmaster’s comment is…
I ended up having to install the smt client on the servers to monitor.
I also had to creat cron jobs (I scheduled for every hour) to run the
command ‘smt-agent’ from the clients as otherwise they would never
report back their status.
I was afraid of that.
SMT client has a lot of packages and this is a production server.
Not happy installing additional software on these servers.
[QUOTE=Stevo;28947]ecanmaster sounds like they ‘said’:
[color=blue]
I managed to install and get SMT installed.
Got the latest patches and installed on sles 11 sp2
now trying to connect the clients to use the local SMT server
after doing research, I couldn’t get it done, but finally it is
working I even get this message:
SMT Registration Report 2015-07-31 17:32 (localhost.site) –
Registration successful
In the SMT management I can see the client with following messages:
There are some patches pending:
││
Optional patches: Status is unknown,
Package manager patches: Status is unknown,
Recommended patches: Status is unknown,
Security patches: Status is unknown
what do I need to do next ?
should I install the “smt client” software for client?[/color]
So my response to ecanmaster’s comment is…
I ended up having to install the smt client on the servers to monitor.
I also had to creat cron jobs (I scheduled for every hour) to run the
command ‘smt-agent’ from the clients as otherwise they would never
report back their status.
I managed to install and get SMT installed.
Got the latest patches and installed on sles 11 sp2
Unless you have a very specific reason to stick to that version, I’d recommend to run at least the SMT server at a more recent, supported level (SLES11SP4 or SLES12)
[… client successfully registered via SMT server …]
what do I need to do next ?
should I install the “smt client” software for client?
that depends on how far you want to take things.
Running “zypper lr -u” on the client should list the required repositories as coming the from SMT server. That would be the most basic service you could have with SMT: download patches to a local server once, and redistribute to the local “SMT client” servers from there. You’d then run things as before - on the client, you can use the zypper commands just the same as if being registered to the SUSE servers directly.
If you would like to have centralized monitoring of the clients’ patch status, and would like to be able to use the SMT server for specific operations, you’d need the SMT client on the client machines. It will register a cron job during registration, that will run every three hours (via the file /etc/cron.d/novell.com-smt-client, part of the smt-client RPM) and ask the SMT server for activities to run. It will not automatically install updates.
For even more management support, up to automatic configuration of services etc., you might want to take a look at SUSE Manager, which could be looked at as the “adult” version of SMT
I don’t have specific reason to use sles 11 sp2 , but am afraid of the impact it will have on the production servers.
Of course, I do agree we need the latest sp, but we don’t know the impact.
I will try to upgrade the sp on one machine and see how that goes.
[QUOTE=jmozdzen;28956]Hi ecanmaster,
I managed to install and get SMT installed.
Got the latest patches and installed on sles 11 sp2
Unless you have a very specific reason to stick to that version, I’d recommend to run at least the SMT server at a more recent, supported level (SLES11SP4 or SLES12)
[… client successfully registered via SMT server …]
what do I need to do next ?
should I install the “smt client” software for client?
that depends on how far you want to take things.
Running “zypper lr -u” on the client should list the required repositories as coming the from SMT server. That would be the most basic service you could have with SMT: download patches to a local server once, and redistribute to the local “SMT client” servers from there. You’d then run things as before - on the client, you can use the zypper commands just the same as if being registered to the SUSE servers directly.
If you would like to have centralized monitoring of the clients’ patch status, and would like to be able to use the SMT server for specific operations, you’d need the SMT client on the client machines. It will register a cron job during registration, that will run every three hours (via the file /etc/cron.d/novell.com-smt-client, part of the smt-client RPM) and ask the SMT server for activities to run. It will not automatically install updates.
For even more management support, up to automatic configuration of services etc., you might want to take a look at SUSE Manager, which could be looked at as the “adult” version of SMT
Unless you have a very specific reason to stick to that version, I’d
recommend to run at least the SMT server at a more recent, supported
level (SLES11SP4 or SLES12)[/color]
There is no version of SMT available for SLES12 - it requires an update
version of SMT11 SP3 on SLES11 SP3. With SLES11 SP4 recently released
there is not yet an updated version of SMT for it (i.e. SMT11 SP4).
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.
Unless you have a very specific reason to stick to that version, I’d
recommend to run at least the SMT server at a more recent, supported
level (SLES11SP4 or SLES12)[/COLOR]
There is no version of SMT available for SLES12 - it requires an update
version of SMT11 SP3 on SLES11 SP3. With SLES11 SP4 recently released
there is not yet an updated version of SMT for it (i.e. SMT11 SP4).[/QUOTE]
[QUOTE]SMT 11 SP3 can run on top of SLES 11 SP4. In order to make it possible, it is necessary to install the latest maintenance updates of SMT 11 SP3. This needs to be done before SLES is updated from version 11 SP3 to version 11 SP4. After the update of SLES, SMT keeps running as-is.
In order to install SMT 11 SP3 on top of SLES 11 SP4, use the latest media available from download.suse.com . [/QUOTE]
I tried to update to sp3 first on one of the servers and it seems I don’t have permissions to download,
the credentials I used to connect to the servers to get the updates is working fine,
so that leaves only permissions problems
I have a trial license, probably I need a full license
Hi stevenhendry (a second account to “ecanmaster”?),
[QUOTE=stephenhendry;28969]thx for the information guys
I tried to update to sp3 first on one of the servers and it seems I don’t have permissions to download,
the credentials I used to connect to the servers to get the updates is working fine,
so that leaves only permissions problems
I have a trial license, probably I need a full license[/QUOTE]
It’s not fully clear to me what you tried to download / update.
I’d try to update SLES on the SMT server machine first, going from SLES11SP2 to SP3 (see https://www.suse.com/support/kb/doc.php?id=7012368), then update SMT to 11SP3. After that, update SLES to SP4. If not doing it per “zypper” or “wagon”, but directly from SLES11SP2 to SP4 using the SP4 installation media, you might need to re-install the SMT server from its installation media.
As updating via zypper or wagon actually is “downloading updates” and you’re currently able to download SP2 updates (“the credentials I used to connect to the servers to get the updates is working fine”), this should work.
SMT 11 SP3 can run on top of SLES 11 SP4. In order to make it possible,
it is necessary to install the latest maintenance updates of SMT 11 SP3.
This needs to be done before SLES is updated from version 11 SP3 to
version 11 SP4. After the update of SLES, SMT keeps running as-is.
In order to install SMT 11 SP3 on top of SLES 11 SP4, use the latest
media available from ‘download.suse.com’
(https://download.suse.com/index.jsp) .[/color][/color]
Hmm I missed that. Will have to ask SUSE if they plan on updating SMT to
match underlying SLES.
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.
It’s not fully clear to me what you tried to download / update.
I’d try to update SLES on the SMT server machine first, going from
SLES11SP2 to SP3 (see https://www.suse.com/support/kb/doc.php?id=7012368), then update SMT to
11SP3. After that, update SLES to SP4. If not doing it per “zypper” or
“wagon”, but directly from SLES11SP2 to SP4 using the SP4 installation
media, you might need to re-install the SMT server from its installation
media.[/color]
SUSE don’t support updating directly from SLES11 SP2 to SLES11 SP4 and
instead you have to first update to SLES11 SP3.
Given SMT11 SP2 on SLES11 SP2 I would:
Update SLES11 SP2 to SLES11 SP3
Update SMT11 SP2 to SMT11 SP3
Update SLES11 SP3 to SLES11 SP4
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.
yes, that is exactly what I have done
the problem is that after every upgrade, the yast online update doesnt work and
I get message with a denied to the url (sorry dont have the exact error message)
seems I can’t connect to repositories for the sp3 and sp4
after waiting for a while, I can just connect to the repositories online
this is a serious bug/fault, and because of this issue I got distracted
anyway I have upgrade to SLES 11 sp4 , thx guys
It’s not fully clear to me what you tried to download / update.
I’d try to update SLES on the SMT server machine first, going from
SLES11SP2 to SP3 (see https://www.suse.com/support/kb/doc.php?id=7012368), then update SMT to
11SP3. After that, update SLES to SP4. If not doing it per “zypper” or
“wagon”, but directly from SLES11SP2 to SP4 using the SP4 installation
media, you might need to re-install the SMT server from its installation
media.[/color]
SUSE don’t support updating directly from SLES11 SP2 to SLES11 SP4 and
instead you have to first update to SLES11 SP3.
Given SMT11 SP2 on SLES11 SP2 I would:
Update SLES11 SP2 to SLES11 SP3
Update SMT11 SP2 to SMT11 SP3
Update SLES11 SP3 to SLES11 SP4
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.
------------------------------------------------------------------------[/QUOTE]
