Document fins/I0593-1


FIN #: I0593-1

SYNOPSIS: Netcon logging should be enabled for all E10000 Servers.

DATE: Jul/05/00

KEYWORDS: Netcon logging should be enabled for all E10000 Servers.


---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------  
                            FIELD INFORMATION NOTICE
                  (For Authorized Distribution by SunService)



SYNOPSIS: Netcon logging should be enabled for all E10000 Servers.
                                 

TOP FIN/FCO REPORT: Yes 
 
PRODUCT_REFERENCE:  E10000 Server Configuration  
 
PRODUCT CATEGORY:   Server / SW Admin; Server / Documentation 

PRODUCTS AFFECTED:  
  
Mkt_ID   Platform   Model   Description   Serial Number
------   --------   -----   -----------   -------------
Systems Affected
----------------

  -       E10000     All         -              -

X-Options Affected
------------------
  -          -        -          -              -

PART NUMBERS AFFECTED: 

Part Number   Description   Model
-----------   -----------   -----
     -             -          - 

REFERENCES:

BugId:   4308756
PatchId: 108638 - SSP3.1.1    
         108676 - SSP3.2.0   
MANUAL:  805-7519-10: Sun Enterprise(tm) 10000 SSP3.3 User's Guide 
         806-1500-10: Sun Enterprise(tm) 10000 SSP3.2 User's Guide
         806-2887-10: Sun Enterprise(tm) 10000 SSP3.1.1 User's Guide
URL: http://sunsolve-int.central.sun.com/cgi/retrieve.pl?doc=infodoc%2F15786

      
PROBLEM DESCRIPTION:

The review and improvement of Solaris diagnostic messages have uncovered
a hole in message retention for the E10000 platform.  After a panic
reboot, hpost performs a destructive scrub of memory effectively
destroying the message buffer and any information it may have contained
for problem diagnosis.  Since we cannot change the destructive nature
of hpost, the only reliable solution is to capture what is output on
the console.

All E10000 servers using SSP release 3.1.1 and higher have the ability
to log console output via the netcon logging feature.  This is handled
by the syslog local1 facility and is disabled by default.  Beginning
with release 3.4, this feature will be enabled by default but prior
releases will need to be changed manually.

Enabling the feature has negligible effects on performance but disk
space may be of concern depending on current disk and console usage.
Although we don't anticipate anyone having issues with disk space, disk
cleanup may be necessary to avoid full filesystem scenarios.
Currently, nine netcon logs are retained per configured domain and
expire once a week.  File sizes can vary greatly depending on console
usage so tuning may be required to reduce the amount of disk space
needed to accommodate these new logs.


IMPLEMENTATION:  
 
         ---
        |   |   MANDATORY (Fully Pro-Active)
         ---    
         
  
         ---
        | X |   CONTROLLED PRO-ACTIVE (per Sun Geo Plan) 
         --- 
         
                                
         ---
        |   |   REACTIVE (As Required)
         ---
         

CORRECTIVE ACTION:

Enterprise Customers and authorized Field Service Representatives may
avoid the above mentioned problem by following the recommendations
as shown below: 

To enable netcon logging for SSP release 3.1.1, 3.2 and 3.3:

1. Login as root.

2. Uncomment local1.debug in /etc/syslog.conf.

3. Restart syslogd.

     # /etc/init.d/syslog stop
     # /etc/init.d/syslog start

To enable netcon logging for SSP releases prior to 3.1.1, see Infodoc
#15786.

To reduce the number of aged log files to retain:

1. Login as root.

2. Edit /opt/SUNWssp/bin/newssplog.

3. Change variable MAX=8 to MAX=3.

   - This will reduce the number of aged files from 9 weeks to 4
     weeks.


COMMENTS:  

--------------------------------------------------------------------------
Implementation Footnote:

i)   In case of MANDATORY FINs, Enterprise Services will attempt to    
     contact all affected customers to recommend implementation of 
     the FIN. 
   
ii)  For CONTROLLED PROACTIVE FINs, Enterprise Services mission critical    
     support teams will recommend implementation of the FIN  (to their  
     respective accounts), at the convenience of the customer. 

iii) For REACTIVE FINs, Enterprise Services will implement the FIN as the   
     need arises.
----------------------------------------------------------------------------
All released FINs and FCOs can be accessed using your favorite network 
browser as follows:
 
SunWeb Access:
-------------- 
* Access the top level URL of http://sdpsweb.ebay/FIN_FCO/

* From there, select the appropriate link to query or browse the FIN and
  FCO Homepage collections.
 
SunSolve Online Access:
-----------------------
* Access the SunSolve Online URL at http://sunsolve.Corp/

* From there, select the appropriate link to browse the FIN or FCO index.

Supporting Documents:
---------------------
* Supporting documents for FIN/FCOs can be found on Edist.  Edist can be 
  accessed internally at the following URL: http://edist.corp/.
  
* From there, follow the hyperlink path of "Enterprise Services Documenta- 
  tion" and click on "FIN & FCO attachments", then choose the
appropriate   
  folder, FIN or FCO.  This will display supporting directories/files for 
  FINs or FCOs.
   
Internet Access:
----------------
* Access the top level URL of https://infoserver.Sun.COM
--------------------------------------------------------------------------
General:
--------
* Send questions or comments to finfco-manager@sdpsweb.EBay
---------------------------------------------------------------------------
                                                        





Copyright (c) 1997-2003 Sun Microsystems, Inc.