Document fins/I0534-1
FIN #: I0534-1
SYNOPSIS: E10000 using FDDI 6.0 software may encounter Broken Pipe errors and
Dynamic Reconfiguration problems.
DATE: Nov/08/99
KEYWORDS: E10000 using FDDI 6.0 software may encounter Broken Pipe errors and
Dynamic Reconfiguration problems.
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)
SYNOPSIS: E10000 using FDDI 6.0 software may encounter Broken Pipe
errors and Dynamic Reconfiguration problems.
TOP FIN/FCO REPORT: Yes
PRODUCT_REFERENCE: FDDI 6.0 on E10K performance
PRODUCT CATEGORY: Server / SW Admin; Networking / FDDI;
PRODUCTS AFFECTED:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
E10000 E10000 - Ultra Enterprise 10000 -
X-Options Affected
------------------
X1142A - - OPT SBUS SAS FDDI 6.0 W/SW -
X1143A - - OPT SBUS DAS FDDI 6.0 W/SW -
PART NUMBERS AFFECTED:
Part Number Description Model
----------- ----------- -----
370-3142-0X ASSY,HDW,FDDI SAS
370-3143-0X ASSY,HDW,FDDI DAS
REFERENCES:
BugId: 4228707, 4239753
URL:
http://www.sun.com/products-n-solutions/hw/networking/upgrades/index.html#fddi
DOC: 806-3610-10 Starfire SunFDDI
PROBLEM DESCRIPTION:
FDDI 6.0 is supported on E10000 servers running Solaris 7 11/99 and
earlier. Two documentation issues were discovered when testing FDDI 6.0
on the Enterprise 10000. The Bug Reports 4228707 and 4239753 describe
the issues.
Problem# 1 from: BugId# 4228707, Solaris 2.6 ONLY
----------
When running a heavy I/O load between domains using FDDI 6.0 with
Solaris 2.6 software, Broken Pipes may be experienced.
Problem# 2 From BugId# 4239753, Solaris 2.5.1 and 2.6 ONLY
----------
Unable to complete the detachment of a system board populated with FDDI
6.0 adapters if the SNMP daemons are active and SMT driver is loaded in
the kernel. This problem exists when running with Solaris 2.5.1 and 2.6.
In response to the bugIds mentioned above, a new Enterprise 10000 Sun
FDDI 6.0 Customer Document has been compiled with the intent of
providing workarounds and recommendations on FDDI 6.0 not given in the
FDDI 6.0 User's Guide.
A White Paper describing FDDI 6.0 on E10000 systems is included on
the Solaris 7 11/99 Supplements CD, in the following location:
Docs/E10K_SunFDDI/SunFDDI6e10k.ps
IMPLEMENTATION:
---
| | MANDATORY (Fully Pro-Active)
---
---
| X | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| | REACTIVE (As Required)
---
CORRECTIVE ACTION:
Problem #1: Broken Pipes
----------
When running heavy I/O load between domains using Solaris 2.6 software,
you may experience "broken pipes". To avoid or correct this problem:
Check the value of tcp_rexmit_interval_max by using the following:
# ndd -get /dev/tcp tcp_rexmit_interval_max
If the return value is not 60000, use the following command to re-
set the parameter.
# ndd -set /dev/tcp tcp_rexmit_interval_max 60000
To avoid losing this change between system reboots, you can create
a script and put in in /etc/rc2.d directory.
Problem #2 Dynamic Reconfiguration (DR) Issues.
----------
When detaching a system board, the SNMP daemons must be killed and the
SMT driver must be unloaded from the kernel when using Solaris 2.5.1
and 2.6 prior to detaching the system board.
This can be done by executing the following commend from the host
window command line:
# /etc/opt/SUNWconn/nf/bin/nf_snmd_kill
The Station Management (SMT) daemon starts two agents tat collect and
return FDDI statistics to a SunNet Manager (SNM) Console. Without the SNMP
daemons network data will not be available for monitoring.
To restart the SNMP daemons and reload the SMT driver to the kernel, after
the system board has been detached, execute the following command from
the host window command line: (Must have at least one FDDI adapter plumbed
and up).
# /etc/opt/SUNWconn/bin/nf_fddidaemon start
When removing a system board that is part of a FDDI configuration, no
data will travel through the FDDI adapters once the detach is completed.
To restore the configuration, attach the system board and plumb (ifconfig)
the FDDI adapters. This will allow the data to travel through the FDDI
adapters.
The FDDI adapter must have the inet (IP address), netmask and broadcast
values set to be in an active state. The implications of having a FDDI
adapter which does not pass data will vary with your specific topology.
*A White Paper describing FDDI 6.0 on E10000 systems is included on
the Solaris 7 11/99 Supplements CD, in the following location:
Docs/E10K_SunFDDI/SunFDDI6e10k.ps
NOTE: Please check the SunSolve database for any patches which may have
been issued against DR and FDDI 6.0.
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@Sun.COM
---------------------------------------------------------------------------
Copyright (c) 1997-2003 Sun Microsystems, Inc.