| Document Audience: | INTERNAL
Archive
| WARNING:Articles moved into the Archived collection were accurate at the "Last Update" date, but are not maintained from that date forward.
As such, Sun disclaims all implied or express warranties with respect to the information contained in such articles.
| Document ID: | I0412-1 |
| Title: | SunATM-155 Sbus Board Replacement May Render Interface Unrecognizable. |
| Copyright Notice: | Copyright © 2005 Sun Microsystems, Inc. All Rights Reserved |
| Last Updated Date: | 1998-08-05 |
---------------------------------------------------------------------
- Sun Proprietary/Confidential: Internal Use Only -
---------------------------------------------------------------------
FIELD INFORMATION NOTICE
(For Authorized Distribution by SunService)FIN #: I0412-1
Synopsis: SunATM-155 Sbus Board Replacement May Render Interface Unrecognizable.Create Date: Aug/04/98
Keywords:
SunATM-155 Sbus Board Replacement May Render Interface Unrecognizable.
Top FIN/FCO Report: No
Products Reference: SunATM-155 SBus Board
Product Category: Networking / ATM
Product Affected:
Mkt_ID Platform Model Description Serial Number
------ -------- ----- ----------- -------------
Systems Affected
----------------
- 4/15 All SPARCclassic -
- 4/30 All SPARCstation LX -
- 4/50 All SPARCstation IPX -
- 4/75 All SPARCstation 2 -
- SS4 All SPARCstation 4 -
- SS5 All SPARCstation 5 -
- SS10 All SPARCstation 10 -
- SS20 All SPARCstation 20 -
- 4/600 All SPARCserver 600 -
- SS1000 All SPARCcenter 1000 -
- SS1000E All SPARCcenter 1000E -
- SC2000 All SPARCcenter 2000 -
- SC2000E All SPARCcenter 2000E -
- A11 All Ultra 1 -
- A12 All Ultra Enterprise 1 -
- A14 All Ultra 2 -
- E150 All Ultra Enterprise 150 -
- E3000 All Ultra Enterprise 3000 -
- E3500 All Ultra Enterprise 3500 -
- E4000 All Ultra Enterprise 4000 -
- E4500 All Ultra Enterprise 4500 -
- E5000 All Ultra Enterprise 5000 -
- E5500 All Ultra Enterprise 5500 -
- E6000 All Ultra Enterprise 6000 -
- E6500 All Ultra Enterprise 6500 -
- E10000 All Ultra Enterprise 10000 -
X-Options Affected
------------------
X1060A - - SunATM-155/MFiber SBus Adapter -
X1061A - - SunATM-155/UTP5 SBus Adapter -
Parts Affected:
Part Number Description Model
----------- ----------- -----
501-2794-08 SunATM-155/MFiber SBus Adapter -
501-2795-06 SunATM-155/UTP5 SBus Adapter -
References:
ECO: WO_11347
DOC: path_to_inst(4)
Issue Description:
Since the introduction of ECO WO_11347 which added a new ASIC,
PROM and a binary code license agreement, SunATM-155 SBus card(s)
(shown above), may encounter a configuration problem as described
under the following conditions:
When an older SunATM-155 SBus board (501-2794-07 and 501-2795-05
and prior versions) is replaced by a new SunATM-155 SBus board
(501-2794-08 and 501-2795-06 and compatible versions), the
replacement board will be given a different instance number even
though both resided in the same SBus slot. For example, if a
system is configured with an older SunATM-155 interface
identified as ba0 and a new SunATM-155 board is placed in the
same SBus slot as the older one, the new interface will
nonetheless be identified as ba1 after the system is rebooted.
The SunATM-155 SBus board originally shipped with an FCode name
property of "ba". A more recent Sun practice is to prepend the
stock symbol to the name to avoid conflicts with third-party
devices which happen to choose the same name. When a third-party
board was found which had also chosen the name property "ba",
the SunATM-155 SBus board was updated to use the "SUNW,ba" name
property instead.
As a result, if a SunATM-155 SBus board with the "ba" name
property is replaced by a newer SunATM-155 SBus board with the
"SUNW,ba" name property, the system will not recognize the new
board as a replacement but as a new interface and will assign
to it a new instance number.
Implementation:
---
| | MANDATORY (Fully Pro-Active)
---
---
| | CONTROLLED PRO-ACTIVE (per Sun Geo Plan)
---
---
| X | REACTIVE (As Required)
---Corrective Action:
The file /etc/path_to_inst is created by the Solaris system to
identify installed devices and their instance numbers. If a
SunATM-155 SBus board with the "ba" name property is installed
in a system, /etc/path_to_inst will have an entry similar to
the following to identify it as ba0:
"/sbus@1f,0/ba@0,0" 0 "ba"
where
"/sbus@1f,0/ba@0,0" is the physical name
0 is the instance number
"ba" is the driver binding name
When a replacement board with the "SUNW,ba" name property is
installed into the same location and the system is rebooted, it
will be treated as a new device and a new entry in
/etc/path_to_inst will be created for ba1:
"/sbus@1f,0/SUNW,ba@0,0" 1 "ba"
To correct this, delete the original entry that contains the "ba"
name. The second field of the new entry which contains the
name "SUNW,ba" must be modified to reflect the proper instance
number. In this example, the new entry is being designated
as instance 0:
"/sbus@1f,0/SUNW,ba@0,0" 0 "ba"
After /etc/path_to_inst has been properly modified and saved, reboot
the system for the changes to take effect.
The physical name listed in /etc/path_to_inst will vary from one
architecture to another and may not match the examples above exactly.
Regardless, the instance number is the only field which should be
modified, leaving all other fields as is.
Comments:
NOTE: The /etc/path_to_inst file contains the following WARNING:
WARNINGS
If the file is removed the system may not be bootable (as it
may rely on information found in this file to find the root,
usr or swap device). If it does successfully boot, it will
regenerate the file, but after rebooting devices may end up
having different minor numbers than they did before, and
special files created via mknod(1M) may refer to different
devices than expected.
For the same reasons, changes should not be made to this file
without careful consideration.
*Thus, it is STRONGLY RECOMMENDED that a copy of this file is
created PRIOR to the implementation of this workaround.
The SunATM-622 SBus board has always used the "SUNW,ba" name and
is unaffected by this problem. Likewise, the SunATM-155 PCI and
SunATM-622 PCI boards use the name "SUNW,ma" and are unaffected
by this problem.
--------------------------------------------------------------------------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 sup-
port 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://cte.corp/FIN_FCO/
* From there, select the appropriate link to query or browse the FIN and
FCO Homepage collections.
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 "SunService Documentation" 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@cte.Corp
---------------------------------------------------------------------------