Sun Update Connection issues 01/06 vs 06/06

I am attempting to register my Solaris 10 Sparc Servers with the SUN Update Connection Portal. I have installed the Connection App (121118-08) on 4 machines. 1 of these is running Sol10 06/06 and the other 3 are running Sol10 01/06.

I can see all 4 servers on the Update Connection portal but I am only able to work with the 06/06 machine. When I installed Patch 121453-02 I get the follow messages on the 06/06 machine.

The following requested patches have packages not installed on the system.

Package SUNWbreg from directory SUNWbreg in patch 121453-02 is not installed on the system.

Changes for package SUNWbreg will not be applied to the system.

Package SUNWdc from directory SUNWdc in patch 121453-02 is not installed on the system.

Changes for package SUNWdc will not be applied to the system.

However, I did not receive these messages on the 01/06 machines. Come to find out SUNWberg and SUNWdc no longer exist on 06/06. SUNWberg has been renamed to SUNWbrg.

Also when I run the following command.

/usr/sbin/sconadm register -a -r /usr/lib/breg/data/RegistrationProfile.properties

I get the following messages on the 01/06 servers.

# /: /usr/sbin/sconadm register -a -r

/usr/lib/breg/data/RegistrationProfile.properties

sconadm is running

Authenticating user ...

Collecting asset ...

Registering asset ...

sconadm has been completed successfully

But when I run it on the 06/06 Server I get the following messages

# /: /usr/sbin/sconadm register -a - r

/usr/lib/breg/data/RegistrationProfile.properties

sconadm is running

Authenticating user ...

finish registration!

How do I fix this so that I will be able to manage both 01/06 servers like the 06/06 servers?

DP

[1873 byte] By [dpatterson21a] at [2007-11-26 13:12:00]
# 1

The changes between the 2 Solaris 10 releases should only relate to the registration process.

Both the examples of the sconadm command you providied show successful registration attempts and as such all of the hosts should be able to use the SunUC features without difficulty.

Can you clarify what the issue is? Do you mean that the 01/06 hosts are listed as "not checked in" when viewing them on the SunUC web portal?

ForumModeratora at 2007-7-7 17:28:22 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2
Yes, now the (3) 01/06 Systems are not checked in. Also you are unable to select them in the Systems Tab of the Update Connection App.However, the 06/06 machine is not having any issues at all. Daniel
dpatterson21a at 2007-7-7 17:28:22 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 3
Here is what I am seeing on the Sun Connection Portal. http://i26.photobucket.com/albums/c106/pojay21/SunUpdateConnectionSC.jpgDaniel
dpatterson21a at 2007-7-7 17:28:22 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 4
Hi.Could you run the following command on the non-reporting hosts:# /usr/lib/cc-cfw/platform/transport/bin/cctrunner -pThe command should output 'SUCCESSFUL PING' if the transport is OK.Mod.
ForumModeratora at 2007-7-7 17:28:22 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 5

Here are the results....

lfknpaps01 /: /usr/lib/cc-cfw/platform/transport/bin/cctrunner -p

* About to connect() to cns-transport.sun.com port 443

*Trying 198.232.168.137... * connected

* Connected to cns-transport.sun.com (198.232.168.137) port 443

* successfully set certificate verify locations:

*CAfile: /usr/lib/cc-cfw/platform/transport/etc/CACert.pem

CApath: none

* SSL certificate problem, verify that the CA cert is OK. Details:

error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

* Closing connection #0

* About to connect() to cns-transport.sun.com port 443

*Trying 198.232.168.137... * connected

* Connected to cns-transport.sun.com (198.232.168.137) port 443

* successfully set certificate verify locations:

*CAfile: /usr/lib/cc-cfw/platform/transport/etc/CACert.pem

CApath: none

* SSL certificate problem, verify that the CA cert is OK. Details:

error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

* Closing connection #0

curl error code: 60

curl message: SSL certificate problem, verify that the CA cert is OK. Details:

error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed

dpatterson21a at 2007-7-7 17:28:22 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 6
Hi again.It looks like the certificates are out-of-date.Could you apply patches 122231-01and 121118-08 manually, and try:/usr/lib/cc-cfw/platform/transport/bin/cctrunner -pagain. You should get a successful ping.If so, try smpatch again.mod.
ForumModeratora at 2007-7-7 17:28:22 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 7

I applied patch 122231-01and was able to PING successfully. But Patch 121118-08 was already installed as I did this during the initial install.

The patched system checked in but I am still unable to see any updates for that system. Screen looks the same as in the photobucket link above....

DP

dpatterson21a at 2007-7-7 17:28:22 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 8

The checkin and the inventory upload are 2 seperate jobs.

The "check-in" should happen hourly and operates as a heartbeat feature to the portal. It's primary role though is to check whether you have scheduled any jobs to be run using the web portal interface, and if you have it will action them appropriately.

The inventory upload only happens once daily and it is this which populates the list of available patches for a particular system. Think of it as a daily check of the current state of the system that gets uploaded to the portal so a list of available patches is produced allowing you to select and schedule jobs appropriately.

With that in mind I'd imagine that now that the host is checking in the inventory should be uploaded withing 24 hours. If it's still a problem after that let us know.

ForumModeratora at 2007-7-7 17:28:22 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 9
You could not have been more right!! Both systems that I made the update to have continued to check in and have updated. Thanks for all of the help! I can now close my case that I called into SUN.Daniel
dpatterson21a at 2007-7-7 17:28:22 > top of Java-index,Administration Tools,Sun Update Connection-System...