Patch Name: PHNE_8830 Patch Description: s700 10.20 OTS C.07.00 cumulative mega patch Creation Date: 97/06/30 Post Date: 97/07/17 Hardware Platforms - OS Releases: s700: 10.20 Products: OTS/9000 C.07.00 Filesets: OTS9000.OTS-KRN,C.07.00 OTS9000.OTS-MAN,C.07.00 OTS9000.OTS-RUN,C.07.00 OTS9000.OTS-SES-PRG,C.07.00 OTS9000.XAP-PRG,C.07.00 OTS9000.APLI-PRG,C.07.00 OTS9000.ROSE-PRG,C.07.00 Automatic Reboot?: Yes Status: General Superseded Critical: Yes PHNE_8830: PANIC PHNE_8225: PANIC Path Name: /hp-ux_patches/s700/10.X/PHNE_8830 Symptoms: PHNE_8830: 1. osiconf will not allow preferred multiplexing class to be set to 3. 2. Shell scripts rely on transition links in 10.X releases of OTS. 3. osiadmin coredumps (not a panic) when you exit to a shell and return. 4. OTS - osiconf does not allow rfc1006 to be configured on some interfaces. 5. osidiag allows for the testing of the status of 2 of the 5 supported LAN cards. 6. osipdufmt -r does not put any timestamps into the formatted output, and it only formats RFC1006 PDUs. It is desirable to have other PDUs formatted as well. 7. OTS ESH packets are not sent out according to snet_esh_ctimer. If snet_esh_ctimer < 10, then ESHs are sent every 10 seconds, and it seems to round it off to a suitable multiple of 10. 8. OTS APLI problem with encoding of CPR-PPDU - invalid PCDRL. 9. OTS could not make connection to a remote node through X.25 when the X.25 subnet was configured to use 1980 standards with a NULL subaddress and snet_bind_by_pid set to one. 10. When OTS is configured over RK6, the IP address supplied by the application in osi_rgr_rq() is not transmitted to the peer. 11. An invalid TPDU sequence number is generated when the tpcons_propose_ext_fmt parameter is set to 1. 12. OTS does not conform to INTAP standards - ASN.1 TLV NULL values. 13. OTS returns OPI_ERR(0x8422) instead of ESPABID(0x1407) when an invalid NSAP address is used. 14. SESSION API, osi_rgr_rq() with no_of_connections parameter set to a value greater than 1024 returns osierrno : OSIEBADRNG. 15. OTS sends ESH out on the wrong lan card. 16. A TP3 CR could be interpreted as TP2 with flow control. 17. Memory leak occurs when an application registers and deregisters using Session API's by calling osi_rgr_rq() and osi_drg_rq() in a loop continuously. 18. ap_rcv() causes APRI application to core dump when APRI tracing is enabled. 19. System panics if the following are true: 1. Running TP3 2. OTS is rejecting a connection confirmation 3. The flag tpcons_propose_ext_fmt in ots_parms is set to 0(default). 20. The date field in osidiag when the tracing is enabled depends on the assumption of the date field being less than the year 2000. This assumption is no longer valid as one hits the century mark. 21. Applications written on 10.20, when moved to 10.30 and beyond, will not link with the proper version of the shared library, and may crash. 22. On receiving NULL data packets, the system panics. 23. If 'otsamd' dies, then at the first attempt to send out an RFC 1006 PDU, the system crashes. 24. 'otsdeles' does not handle alternate physical addresses properly. 25. PHNE_8828 prevents incoming Streams X.25 OTS calls. 26. Invoking 'man' on otsaddes, otsdeles and otsshowes results in the following error message - stdin: not in compressed format PHNE_8225: 1. The retransmission timer doesn't work as expected. 2. System panicked when it was idling. Panic message: Data page fault 3. MSDSG doesn't work. 4. ots_get_layer_stats does not return 0 when successful. 5. OTS does not support TP3. 6. TP3 over CONS is added to OTS. 7. System panicked when a FTAM connection is being established. Panic message: INTERNAL ERROR: Illegal RCI operation 8. a) osipdufmt doesn't handle -l option correctly. b) osipdufmt doesn't handle pdus across multiple X.25 packets c) odipdufmt doesn't format RFC1006 traces. 9. a) With multiple X.25 cards configured, no LAN; all cards in both CLNS and CONS subnets and any card's, other than the first's, X.121 address in the ots_dests file, a loopback(transport) test after doing an x25init of all cards will cause a system panic. b) With a single X.25 card configured in a CLNS subnet and no LAN subnet configured, the CLNS X.25 subnet will not work. One will not be able to make connections or transfer data. A simple loopback(transport) test will fail. Defect Description: PHNE_8830: 1. The JAM screen regular expression was not updated to reflect the multiplexing class when it was set to 3. 2. The OTS product for ALL 10.X versions shipped shell scripts with either "/bin/sh" or "/bin/ksh". These will only work for systems with transition links. It is an option when installing a system to NOT have transition links. To be fully compatible with all the systems these references must be changed to "/usr/bin/sh". 3. The JAM osiadmin main menu return pointer (ui_init_ptr) was not initialized as a result of which Osiadmin coredumps. 4. The method used by osiconf to check the IP address was not sufficient to locate all IP addresses on all lan cards. 5. The code had a wrong interpretation of the 'dl_next_offset' field, and the AREA_SIZE definition was too small to hold data with many structures sent back by PPA_INFO_ACK as a result of which it was not possible to test the status of more than 2 lan cards. 6. The AWK script which preprocesses the output from 'nettl' was not including timestamp information. The -r option was designed to ignore all but RFC1006 trace entries. 7. The current timer value in e2ittim() was decremented by 10 at each call and then the timer value was checked for expiration. The timer granularity was 10 sec, and the same timer was used for ESH and RIB. 8. On receiving a Connect Presentation(CP) PPDU with invalid Calling-Presentation-selector from connection initiator, OTS responder encodes the Connect Presentation Reject(CPR) PPDU with a wrongly encoded PCDRL and provider-reason. 9. OTS did not bind correctly to the 1980 X.25 PID even though the configuration was set to the 1980 standard. 10. The default IP address of the card (which is configured with ifconfig) was being sent to the remote application. RK6 was not doing an explicit bind of the local address. So the default was being picked up. 11. When the tpcons_propose_ext_fmt parameter is set to 1, the sequence numbering in the Transport PDU is incorrect, that is, it is 0, 2, 4 etc. instead of 0, 1, 2.. and the receiver closes the connection. 12. When P-selectors are configured as NULL for ftam initiator and responder (ae_local_paddr in local_app), the P-selectors sent in CP, CPA and CPR PPDUs are ASN.1 encoded as NULL with length as zero and no value. INTAP standard requires such P-selectors to be absent from the PDUs, these being optional fields of the PDUs. 13. When OTS is configured with only an RFC1006 subnet and an attempt is made to access a non-RFC1006 NSAP, OTS returns OPI_ERR(0x8422) instead of ESPABID(0x1407). OPI_ERR is not a known event as far as X.400 is concerned and so its state machine gets into an indeterminate state from which it is unable to recover. 14. The maximum number of connections supported at the session level is supposed to be 4096 for OTS from C.05.02 through C.07.00. But the maximum number of connections in transport over CLNS is 1024. The no_of_connections parameter was being checked against 1024 instead of 4096. 15. The parameter 'snet_esis' set to 0 prevents a subnet's ESH from being sent. Despite this, a non-HP machine sending out a DC (Disconnect Confirm) to an ALLES address, triggers the sending of an ESH for all LAN subnets. 16. Combining TRS_FLW (defined as 0x10) with TRS_CLASS2 (defined as 0x20), will conflict with newly added TRS_CLASS3 (0x30). 17. An application wishing to register itself calls osi_rgr_rq() which allocates memory. When deregistering, osi_drg_rq() is called which should deallocate the resources, but doesn't do it. This was causing a memory leak. 18. This happens in the ap_rcv() call, due to missing fprintf() format string. 19. With the misplaced/additional "#else and #endif", in t3sedrj() function, 'copy' buffer was a NULL pointer when tenqpfs was called and this resulted in a panic. 20. The onset of the year 2000 would result in major problems with the date field and other date related impacts. When the tracing is turned on in osidiag, the year field of the FORMATTER FILTER i.e., time_from