Sun Management Center
 
Sun Blade 150 Workstation
 

GCS>Sun Microsystems>Desktops>Workstations
 

During the Sun[TM] Management Center 3.0 (SunMC 3.0) agent installation on a
Sun Blade[TM] 150, the following script error
can occur when attempting the config reader package:

 "Configurator package is not available do you want to continue with the
setup ?"

If you choose "yes", the agent installation will successfully complete. But
after logging into the console, no information is displayed in the Hardware
Diagnostic Suite tab.

Another symptom of the same problem is that after adding the SunBlade 150
agent to your Sun Management Center Console, the console shows a blue
folder instead of a Blade icon for the system.

It is not necessary to change the OBP banner information. The workaround is
to install the config reader package (SUNWeswsa) using the Sun Management
Center Product Update 4 media cd 2 of 3:

This example applies to Solaris 8 and later:

 # cd /cdrom/cdrom0/image/Addons/Desktop/Solaris_8/Basic
# pkgadd -d . SUNWeswsa

 Processing package instance <SUNWeswsa> from
</cdrom/cdrom0/sun_management_center_3_0/image/Addons/Desktop/Solaris_8/Basic>

 Sun Management Center Configd Agent For Ultra Workstations
(sparc) 3.0_Build73,REV=2.8.2001.12.07
Copyright 1999 Sun Microsystems, Inc. All rights reserved.
Using </opt> as the package base directory.
## Processing package information.
## Processing system information.
8 package pathnames are already properly installed.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
The following files are already installed on the system and are being
used by another package:
/opt/SUNWsymon <attribute change only>
* /opt/SUNWsymon/base <attribute change only>
* /opt/SUNWsymon/base/lib <attribute change only>

 * - conflict with a file which does not belong to any package.

 Do you want to install these conflicting files [y,n,?,q] n

 Do you want to continue with the installation of <SUNWeswsa> [y,n,?] y
## Checking for setuid/setgid programs.

 This package contains scripts which will be executed with super-user
permission during the process of installing this package.

 Do you want to continue with the installation of <SUNWeswsa> [y,n,?] y
## Processing package information.
## Processing system information.

 Installing Sun Management Center Configd Agent For Ultra Workstations as
<SUNWeswsa>

 ## Installing part 1 of 1.
/opt/SUNWsymon <conflicting pathname not installed>
/opt/SUNWsymon/base <conflicting pathname not installed>
/opt/SUNWsymon/base/lib <conflicting pathname not installed>
2006 blocks

 Installation of <SUNWeswsa> was successful.

Now run es-setup to setup the new config reader:

 # /opt/SUNWsymon/sbin/es-setup

As the root user restart the agent:

 # /opt/SUNWsymon/sbin/es-start -a

Note: Sun Management Center 3.5 and 3.5 Update1 are not affected by this issue.
During the installation:

 # /cdrom/cdrom0/SunMC3.5.1/disk1/sbin/es-inst 

Choose "Yes" to Desktop and the appropriate packages will be added.

This is due to the lack of information in the /usr/platform/ directory for
the Sun Blade 150.

One of the areas the config reader installation for Sun Management Center
(HardwareDiagnostic Suite) looks at is the uname information to determine
the hardware platform.

For example, type the command uname -a on SunBlade 150 and the following is
displayed :

 SunOS sb150-hw 5.9 Generic_112233-05 sun4u sparc SUNW,Sun-Blade-100

Yet, type the command prtdiag and the following is displayed:

 System Configuration: Sun Microsystems sun4u Sun Blade 150 (UltraSPARC-IIe
650 Mhz)

This solution has no attachment