Patch-ID# 102146-03 Keywords: SNA p2p jumbo appc CPIC INET_READ_FAIL p2pconv appc_test test_p2p Synopsis: Sunlink SNA P2P 8.0: Jumbo patch Date: Jan/03/95 Solaris Release: 2.1, 2.2, 2.3, 2.4 SunOS Release: 5.1, 5.2, 5.3, 5.4 Unbundled Product: Sunlink SNA P2P Unbundled Release: 8.0 Relevant Architectures: sparc BugId's fixed with this patch: 1087789 1153228 1170740 1174034 1100104 1164044 1175264 1174360 1177234 1175264 1176031 1177088 1183019 Changes incorporated in this version: 1183019 Patches accumulated and obsoleted by this patch: 101391-04 Patches which conflict with this patch: Patches required with this patch: 101306 : Ethernet driver patch (Needed only if using LLC2 over ethernet or FDDI.) 101524 : The SUNWllc2a patches must be extracted from this X.25 Jumbo patch. (Needed only if using LLC2.) 102147 : SDLC and snacommd patch. Obsoleted by: Files included with this patch: SUNWconn/snap2p/p2p_etc/bin/appc SUNWconn/snap2p/p2p_etc/bin/appconf SUNWconn/snap2p/p2p_etc/bin/db_msg SUNWconn/snap2p/p2p_etc/bin/ftp62 SUNWconn/snap2p/p2p_etc/bin/ftp62_paral SUNWconn/snap2p/p2p_etc/bin/ftp_server SUNWconn/snap2p/p2p_etc/bin/ftp_server_paral SUNWconn/snap2p/p2p_etc/bin/p2pconf SUNWconn/snap2p/p2p_etc/bin/p2pconv SUNWconn/snap2p/p2p_etc/bin/p2pstat SUNWconn/snap2p/p2p_etc/bin/startp2p SUNWconn/snap2p/p2p_etc/bin/test_drive SUNWconn/snap2p/p2p_etc/bin/test_p2p SUNWconn/snap2p/p2p_lib/lib/libappc_api.a SUNWconn/snap2p/p2p_lib/lib/libcpic.a SUNWconn/snap2p/p2p_lib/lib/libcpic_db.a SUNWconn/snap2p/p2p_etc/bin/APING/aping SUNWconn/snap2p/p2p_etc/bin/APING/apingd SUNWconn/snap2p/p2p_etc/bin/AREXEC/arexec SUNWconn/snap2p/p2p_etc/bin/AREXEC/arexecd SUNWconn/snap2p/p2p_etc/bin/ATELL/atell SUNWconn/snap2p/p2p_etc/bin/ATELL/atelld SUNWconn/snap2p/p2p_etc/src/cnos.c SUNWconn/snap2p/p2p_etc/src/p2pconv.c SUNWconn/snap2p/p2p_etc/src/test_p2p.c SUNWconn/snap2p/p2p_etc/src/tp_echo.c SUNWconn/snap2p/p2p_etc/src/tp_parent.c SUNWconn/snap2p/p2p_lib/include/cpic.h SUNWconn/snap2p/p2p_lib/include/cpic_proto.h Problem Description: (Rev 03) 1183019: host sends unbind after positive response to prepare_to_receive_long. other changes: fixed copying the mode name from cnos command. fixed receiving cnos request in chaining. Fixed scan lulucb problem that may cause core dump or other problem when link reconnects. Do not set rcb to NULL in scb if it does not match rcb in DEALLOCATE verb. This problem may cause tp to hang or loop in receive verb and no one can use this session anymore. CMSEND should not check first two bytes of data as length, it can be part of logical record. security_same and security_pgm should be downgraded to security_none if remote lu does not accept any security info. security_same should be downgraded security_none if remote lu does not accept alraedy_verified. (Rev 02) 1087789: appc_test verb does not check invalid SUB_TYPE. 1153228: appc accepts a session without security user id. 1170740: XID failed to request ACTPU when gateway defines a dependent LU. 1174034: appc generates an invalid XID if gateway does not define id_number or block_number after role_type. 1100104: test_p2p bug: mc_receive_and_wait_proc is not handled properly. 1164044: p2pconv fails to correctly convert config file for remote_mac_address. 1175264: execlp() returns EFAULT when license manager is running. 1180403: Two-way simultaneous mode of SDLC is not supported. Therefore, the tx_rx_capability parameter of the p2pconf file must always be set to alternating. A change was made to always set this option to alternating in the XID. other changes: INET_READ_FAIL return code from SEND_DATA and DEALLOCATE. Return an ALLOCTION_FAILURE_NO_RETRY error code to tp when fmh5 is rejected. Set default value for window size and rcv_iframe_size. Using data area for env gateway and tp_name for fork_tp. Incorrect node_id in nonactivation xid. xtwait paramter does not work properly. Added #define cmspln CMSPLN. Support blank sym_dest_name for CMINIT. Fixed cminit-cmallc-cmsend-...-cmsend-cmdeal loop problem. Added ebcdic tp_name in side_info file. The format is x'hhhhhh'. Fixed getting an invalid tp_name in CMINIT. Do not print trace headline if it is set to DB_DISABLE. Fixed send negative LUSTAT response problem. Free rcb when tp name not found from an attach. Added new FDDI driver nf support. (Rev 01) 102146-01 was not released. Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- You must recompile all your applications in order to pick up the new versions of the header files and libraries, if you did not have patch 102146-02 installed. You need to recompile your cpic applications in order to pick up the new cpic library. See also the following patches: 101306 : Ethernet driver patch (Needed only if using LLC2 over ethernet or FDDI.) 101524 : The SUNWllc2a patches must be extracted from this X.25 Jumbo patch. (Needed only if using LLC2.) 102147 : SDLC and snacommd patch. Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Patch Backout Errors:
---------------------
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message:
This patch was obsoleted by patch $1.
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: The obsoleted contents of an
older patch rev that apparently still exists under /var/sadm/patch
should never be restored out of sequence. This could undermine
the integrity of the more current patch rev installed and the
restoration of the files it has saved.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used. The
original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev