I have to find the registration status of SLES and SLED machines offline.
I’ve tried SUSEConnect --status But it requires internet connectivity to check the registration status.
Older forum posts point to a file in /var/cache/SuseRegister/. But my SLES12 SP1 machine doesn’t have that file even while being registered.
DesktopCentral Suse wrote:
[color=blue]
I have to find the registration status of SLES and SLED machines
offline.
I’ve tried
Code:SUSEConnect --status
But it requires internet connectivity to check the registration
status.
Older forum posts point to a file in -/var/cache/SuseRegister/-. But
my SLES12 SP1 machine doesn’t have that file even while being
registered.[/color]
Log into the SUSE Customer Center:
https://scc.suse.com
The “Subscriptions” tab will show what subscriptions you have along
with the Registration Code(s).
The “Systems” tab will show what systems have been registered.
–
Kevin Boyle - 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 this post.
Thank you.
DesktopCentral Suse Wrote in message:
[color=blue]
I have to find the registration status of SLES and SLED machines
offline.
I’ve tried
Code:SUSEConnect --status
But it requires internet connectivity to check the registration
status.
Older forum posts point to a file in -/var/cache/SuseRegister/-. But my
SLES12 SP1 machine doesn’t have that file even while being registered.[/color]
Just so I understand your problem you would like to be able to
find whether an off-line SLE machine is registered (to SUSE
Customer Center, local SUSE Manager, or local SMT)?
HTH.
Simon Flood
SUSE Knowledge Partner
----Android NewsGroup Reader----
http://usenet.sinaapp.com/
Thanks for your reply.
But my query is to do it programmatically and not manually.
Thanks for your reply.
I would like to verify that the offline SLE machine’s OS license hasn’t expired. Sorry for not being clear.
DesktopCentral wrote:
[color=blue]
Thanks for your reply.
But my query is to do it programmatically and not manually.[/color]
I’m sorry but that was not apparent on your previous pose.
One advantage of using the SUSE Customer Center is that the status of
all registered devices can be seen from one screen.
Perhaps Simon can provide some additional ideas…
–
Kevin Boyle - 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 this post.
Thank you.
On 12/07/18 10:24, DesktopCentral wrote:
[color=blue]
Thanks for your reply.
I would like to verify that the offline SLE machine’s OS license hasn’t
expired. Sorry for not being clear.[/color]
By “license” do you mean subscription? With SLE there is no OS license
(as such) but instead you can purchase a subscription which gives you
patches, upgrades, and support.
By registering your server you then get access to the patches & upgrades
but your server would need to be online to register, whether to SUSE
Customer Center (SCC) or a local SUSE Manager/SMT server. If your server
is offline then it’s unlikely to be registered (though it could be if
you installed, registered, updated, and then pulled the network cable or
otherwise restricted it’s ability to talk to the outside world).
What does “SUSEConnect --status” report/do on your offline machines?
On one of my unregistered test servers it reports “Not Registered”
(though it does have have internet access via NAT).
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.
Hi Simon,
Yeah, I mean the SCC subscription.
If my machine is not registered, it gives “Not registered”. But if the machine is registered, it gives an error as the request could not reach scc.suse.com.
But my problem is, the machine won’t be in unregistered state to start with. It will be registered. I’m not sure of what the output will be when the subscription expires and the machine is offline.
DesktopCentral wrote:
[color=blue]
But my problem is, the machine won’t be in unregistered state to start
with. It will be registered.[/color]
When you first install the system, it us unregistered. When you run
“suse_register” it contacts the SCC. When it completes successfully,
your system is registered with the SCC.
[color=blue]
I’m not sure of what the output will be
when the subscription expires and the machine is offline.[/color]
If the machine is offline, it cannot contact the SCC so the status
cannot be updated. The system is still registered but there may no
longer be an active maintenance subscription.
This is the sequence of events:
- You install the system, It is unregistered.
- You run “suse_register” with valid “regcode-sles=” while online.
- The SCC is contacted and “regcode-sles=” is validated.
- The system is then registered with the SCC.
- The system also gains access to repositories for updates.
- When the maintenance expires, the system still remains registered.
- When the maintenance expires, you lose access to the repositories.
- To regain access to the repositories you must re-register with a new
“regcode-sles=” which will be provided when maintenance is renewed.
If your system is always offline after the initial registration, you
cannot properly determine its status without consulting the SCC.
–
Kevin Boyle - 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 this post.
Thank you.
“Kevin Boyle” Wrote in message:
[color=blue]
When you first install the system, it us unregistered. When you run
“suse_register” it contacts the SCC. When it completes successfully,
your system is registered with the SCC.[/color]
[color=blue]
If the machine is offline, it cannot contact the SCC so the status
cannot be updated. The system is still registered but there may no
longer be an active maintenance subscription.This is the sequence of events:
- You install the system, It is unregistered.
- You run “suse_register” with valid “regcode-sles=” while online.
- The SCC is contacted and “regcode-sles=” is validated.
- The system is then registered with the SCC.
- The system also gains access to repositories for updates.
- When the maintenance expires, the system still remains registered.
- When the maintenance expires, you lose access to the repositories.
- To regain access to the repositories you must re-register with a new
“regcode-sles=” which will be provided when maintenance is renewed.If your system is always offline after the initial registration, you
cannot properly determine its status without consulting the SCC.[/color]
With SLES12 you use the SUSEConnect command to register the server
from the command-line.
HTH.
Simon Flood
SUSE Knowledge Partner
----Android NewsGroup Reader----
http://usenet.sinaapp.com/
DesktopCentral Wrote in message:
[color=blue]
Yeah, I mean the SCC subscription.
If my machine is not registered, it gives “Not registered”. But if the
machine is registered, it gives an error as the request could not reach
scc.suse.com.
But my problem is, the machine won’t be in unregistered state to start
with. It will be registered. I’m not sure of what the output will be
when the subscription expires and the machine is offline.[/color]
I don’t currently have access to my test servers but I don’t think
the SUSEConnect status is cached … though that doesn’t mean you
couldn’t cache it yourself after registering the server for
querying offline. Ultimately the SUSE Customer Center is the
definitive source of registration info.
HTH.
Simon Flood
SUSE Knowledge Partner
----Android NewsGroup Reader----
http://usenet.sinaapp.com/
Simon Flood wrote:
[color=blue]
With SLES12 you use the SUSEConnect command to register the server
from the command-line.[/color]
Thanks, Simon. That was mentioned in the OP…
I’m still working with SLE 11 and still thinking “suse_register”. 
While the command and syntax have changed, the process should remain
essentially the same.
–
Kevin Boyle - 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 this post.
Thank you.
Ah, this was what I was looking for! Thanks a lot Kevin!
Yes, Simon. I’m aware of the command. Thank you!
Thanks for the suggestion, Simon!
I’ll think about it.
I came across an API on GitHub.
https://github.com/SUSE/connect/blob/master/doc/SCC-API-(Implemented).md
Thought it might help someone in the future.