This is a heads up on the issues I come across installing and testing 
SSP 3.1.1 in the lab.

There is only one serious gotcha, otherwise there are no big issues, as 
long as the manual is followed.

The Installation Guide and the User guide are well written, but you do
need to read them fully before you start.


GOTCHA ALERT: 
------------
Domain may be UNBOOTABLE after the upgrade due to new diagnostic test
which checks for unsafe Sbus card config. (Certain cards cause problems  
in slot 1)  Read FIN I0405 carefully before attempting the upgrade. It is 
possible to render SAFE configurations unbootable.  

BEWARE..............


Tips:
----
Straight upgrade 3.1 to 3.1.1 without upgrading the OS:-
-------------------------------------------------------
On dual SSP configs that are configured the standard way as "main" and
"spare" being distinct hosts, you can upgrade the spare SSP. On single
configs or dual cloned configs you can upgrade the main SSP.

Upgrading Solaris
-----------------
Upgrade to 3.1.1 first.

The SSP must be configured as SPARE using ssp_config, even if there is is only
one SSP.

If doing an upgrade, remember to go into custom upgrade and add the CDE
packages.  I would tend to advise a clean install though.  

There are scripts (ssp_backup and ssp_restore) in the Tools directory to save 
and restore /var/opt/SUNWssp after a fresh OS install.

Features:
---------
Netcon logging works well, but is not enabled by default after an upgrade to
SSP3.1.1.  Page 40 of the user guide tells you how to enable it.

The S/W works well under CDE.  The netcon tool from the SSP menu, asks you
for the domain_name as it starts up.

There is a new method of syncing the main and spare SSP and failing over.
See page 71 of the user guide.