Monday Nov 05, 2007

First try with Sun Service Tags and SXDE 09/07

I just installed SXDE 09/07 and decided to give Service Tags another shot. The installation of the Service Tags packages doesn't take a special effort.

Unfortunately I can't get the product registration agent to find anything. I checked with one of my co-workers to make sure that he had success before spending any time on the issue.

He confirmed that he was getting discovery for OS installs on systems without servicetag supported products.

Service Tag Discovery: No Products Found

So clearly I have just installed the packages. This is obnoxious.

So under preferences I enabled FINEST logging and tried again.

FINE: Checking ip addresses:
Nov 5, 2007 11:57:17 AM com.sun.scn.client.ui.RegClient getSystems
FINE: Getting ip addresses:
Nov 5, 2007 11:57:17 AM com.sun.scn.client.ui.RegClient getSystems
FINE: Checking:
Nov 5, 2007 11:57:17 AM com.sun.scn.client.ui.RegClient checkIPAddress
FINE: Checking if valid ip address:
Nov 5, 2007 11:57:17 AM com.sun.scn.client.comm.TCPProbe run
FINER: sending message to:
Nov 5, 2007 11:57:17 AM com.sun.scn.client.comm.Communicator$1 run
FINER: communicating with: /
Nov 5, 2007 11:57:17 AM com.sun.scn.client.comm.Communicator getFromAgent
FINE: Getting agent:

That look like communication to me, but wait a URI...trying in a browser returns: in.stlisten: fatal: open failed: No such file or directory

When I look on my system I see I know an easy first try to "fix" that.
ln -s /usr/sfw/lib/ /usr/sfw/lib/
It seems to me that we could do with some sort of error detection or a host level smf service failure.
e.g. We got a response from the polled host but it wasn't anything that we were expecting.

Trying again in a browser returns a result that looks a lot like I would expect given my understanding of Service Tags.
<?xml version="1.0" encoding="UTF-8"?>
<st1:response xmlns:st1="">
    <manufacturer>Parallels Software International Inc.</manufacturer>
    <serial_number>Parallels-18 F2 11 FF 3E 85 43 C5 B4 CC D7 85 04 84 A9 AD</serial_number>

Now everything is working as expected. That is what I am expecting to see!

Taking a look at the Sun Connection Inventory Channel I can see the host I just registered!
Sun Connection: Viewing Registered Hosts

Now everyone should go and install the Service Tags agent and register their devices (It's tied to an extra bonus for us next year :) ).

References: Sun Connection on BigAdmin

Thursday Nov 01, 2007

Indiana IPS (Image Packaging System)

Boldly forward with minimal reading of the docs.

I can't obviously find where I would be downloading additional packages from. I feel like I am running in circles. It would seem that nearly the first thing I should be able to find would be download the rest from HERE. The single CD installer rocks, but we are up to 1 DVD for the normal full install.

I want the Firefox default home to prominently show me:
"Now that you have completed the Slim install get the rest of the packages. Use pkg list/status/something someargs"

The Preview includes the Image Packaging System. With IPS, you can select versioned builds of components to manage or create your own custom OpenSolaris distribution.

IPS packages that are not included in the Slim Install installation image, such as developer tools, can be downloaded after the installation. This prototype uses new IPS commands to access packages from the network repositories. Both IPS packages and SVR4 packages are supported.

The OpenSolaris Project: Image Packaging System project page contains man pages for the new IPS commands and a link to the IPS download site.

OK, pkg(5) has some indications of a repository (or authority) pkg:// No examples, is pkg:// actually a valid and running authority? OK says Looking at the list of available packages I now see that they are basically ALL installed. (maybe pkg(5) should reference

I can also see that when I pkg uninstall SUNWbind and pkg install SUNWbind the counters on the site increment. When I drop ni0 the install fails and with it enabled and snoop running there is http traffic downloading the package. Clearly I am hitting the remote authority. Somewhere I think I should be able to see what the default authority is or where to find it (without digging in /var/pkg and guessing that cfg_cache should be the source, or looking at snoop to see where my traffic is going)

pkg install/uninstall is fast and also easy (somewhat dependent on network bandwidth I would guess). It wouldn't suffer from the some sort of optional feedback that work is progressing.

Errors from pkg are quite ugly and straight out of python.

At this point I call the install a success simple, easy, fast. The post install experience is still missing something. The packages that are not included on the live CD, how did they get installed on my instance when I had no net during the install.

So we are down to
  1. Is the only authority?
  2. are all the packages that are available installed by default?
  3. If pkgadd can't add packages (or is this a bug) how do I add standard SYSV packages now

In the end this was fun and interesting, I have a much better understanding of where we are going but it doesn't look like Indiana is going to be my everyday system for a while yet,

OpenSolaris/Indiana first thoughts

(See Update 1 for how to get functional networking in Indiana under Parallels)

As ThinGuy just mentioned on twitter, no registration or login to download the image. Woot!

I am running the installer iso on top of Parallels on Mac OS X 10.5 (leopard)

  • Boot speed is fabulous
  • Installer is straight forward
    • so few steps it seems like I must be forgetting something
  • Base install is FAST

On the down side:

  • I can't seem to get an external network interface to plumb, but Parallels seems a bit flaky on Leopard
  • single disk contention is the long pole install is not as fast as it could be, should have burned a CD

So now as long as I can get a network interface working one way or another I am set. Fingers crossed. I have already nuked my other local install so I had space to play. I would rather not have to recover it.

Update 1:

Networking: It helps if you remember to install the Parallels provided network interface driver.

See the comment about so few steps I must be forgetting something (like installing the driver)

Parallels: Installing the Beta got rid of some VM related network error messages and appears to have fixed shared networking (my default for my simple test instance).

I guess I could have provided a link:

Issues with the base slim install No /usr/ccs/bin/make (or any make as far as I can tell in the default install). To install the required driver the following manual steps are required.

  • untar the ni\*.tgz into /tmp
  • in the /tmp/ni\*/i386 directory
    • cp ni dp8390 to /kernel/drv
    • cd ..
      (or you can change /etc/path_to_inst yourself)
    • modload /kernel/drv/ni
  • Assuming you are using dhcp wait a moment and get the popup telling you that you have an address.

Appendix C: is way out of date although it would have reminded me to install the network driver.




« July 2016
Sun Managed Operations