This appendix briefly discusses the implications of using the SNC simultaneously with other optional hardware/software systems.
The SNC is fully compatible with Sun's Network Software Environment
product. However, the NSE-supplied installation verification script
The Sun Network CoProcessor is fully compatible with the Sbus or VME PrestoServe board. Using both in one server can result in excellent NFS performance.
It is possible for conflicts to occur with the VME address space. The address 0x0800000, in particular, is used by the VME Prestoserve board. The standard VME address space configuration for SNC avoids this conflict, but if you have chosen 0x0800000 as an alternate address, the problem will occur, and you will have to choose an alternate address for that SNC.
See Appendix C , "Address Space Conflicts with Other Hardware" for more SNC switch settings and their corresponding 32/24-bit VME addresses.
The SNC is fully compatible with TOPS AppleTalk. If you are discontinuing
your use of the standard ie or
The example below assumes that you are using vi to edit the file.
Note - If you cannot find these lines, you may have an early version of TOPS AppleTalk. If that is the case, go to "Early AppleTalk Versions.
You cannot run NC400 and NC600 software on the system at the same time as the SNC software.
You can install SunLink DNI 7.0 before or after installing the SNC.
In this case, when you run the SunLink installation script, it will not list the neX devices when it asks you which interface you want to use to run DECnet. You may, however, specify an neX device and the installation will proceed correctly.
If you replace an interface that was used to run DECnet with an SNC interface, you must change the name of the interface in both /etc/sunlink/dni/etc /etc/rc.boot.
For example, assume that you want to replace the le0 interface with ne0.