************************************************* ECO SUMMARY INFORMATION ************************************************* Release Date: Oct 17, 2005 Kit Name: AXP_X25ECO03-V73X Kit Applies To: OpenVMS Alpha 7.3-1, OpenVMS Alpha 7.3-2 Approximate Uncompressed Kit Size: 13552 INSTALL_2 Kits Superseded By This Kit: None System Reboot Necessary: Yes Checksum of Compressed Kit: 2805449754 HP_X.25_for_OpenVMS_Alpha___________________________ Release Notes September 2005 These Release Notes apply to the HP X.25 for OpenVMS Alpha, Version 1.6 ECO3 product. Please read these Release Notes before attempting to install this product. Operating System: OpenVMS Alpha Version 7.3-1 with DECnet-Plus 7.3-1 Operating System: OpenVMS Alpha Version 7.3-2 with DECnet-Plus 7.3-2 Software Version: HP X.25 for OpenVMS Alpha, Version 1.6 ECO3 Hewlett-Packard Company Palo Alto, California © 2005 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Intel and Itanium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group. Printed in the US _________________________________________________________________ Contents Preface................................................... vii 1 Installation Information 1.1 Installation Instructions..................... 1-1 2 New Features 2.1 Maintenance Release Only...................... 2-1 3 Resolved Problems 3.1 Problems Resolved in Version 1.6 ECO3......... 3-1 3.1.1 Deleting a DTE using the configurator does not remove all the DTE attributes......... 3-1 3.1.2 Reconfigured LLC2 DTE resets the values to default when the user steps through the current values............................ 3-1 3.1.3 Creation of more than 100 DTE results in a error..................................... 3-1 3.1.4 X.25 applications do not work using PVC and GAP................................... 3-2 3.1.5 PBXDD does not assert DTR when cable is removed/reinserted........................ 3-2 3.1.6 Diagnostic code not relayed back properly.................................. 3-2 3.1.7 System Crash with RSVD_LP in GAP_DELETE_GSB............................ 3-2 3.1.8 System Crash at X25$L1+11F70.............. 3-2 3.1.9 PBXDD Buffer too small for SNA............ 3-3 3.1.10 M-bit Incorrectly Handled for GAP Connections............................... 3-3 3.1.11 Pool Corruption when using CUG with GAP... 3-3 iii 3.1.12 X.25 Relay Hangs with Depleted Credits.... 3-3 3.1.13 Rights Identifiers Corrupted by X25$CONFIGURE............................. 3-3 3.1.14 X25$CONFIGURE doesn't Allow PVC Configuration with XOT.................... 3-3 3.1.15 X25$SHUTDOWN.COM doesn't Delete some X.25 Entities.................................. 3-4 3.1.16 Multiple Issues with XOT.................. 3-4 3.1.17 System Crash at X25$L1+11F70.............. 3-4 3.1.18 Invalid Security State Bugcheck........... 3-4 3.1.19 Machine Check Crash During Load of X25$ZZDRIVER.............................. 3-4 3.1.20 Double Deallocation Bugcheck in X25$ACCESS.EXE............................ 3-5 3.1.21 VCRP Leak in Nonpaged Pool................ 3-5 3.1.22 ZZ Device Shows Offline................... 3-5 3.1.23 Inverted Clock Required with PBXDD........ 3-5 4 Known X.25 Problems 4.1 X.29 logins hang and incorrect terminal naming on OpenVMS 7.3-2.............................. 4-1 4.2 X25$APPLD Unexpectedly Exhausts BYTLM Quota... 4-2 4.3 Facility Code "Called Address Extension" Is Modified by the X.25 Software for CALLC Packet........................................ 4-2 4.4 Error Messages During Reinstall/Upgrade of X.25.......................................... 4-3 5 Documentation Updates for X.25 and WANDD on Alpha 5.1 Alpha Restrictions............................ 5-1 5.1.1 Supported Devices......................... 5-1 5.1.2 Framing................................... 5-2 5.1.3 Half-Duplex and Multipoint Operations..... 5-2 5.1.4 Obsolete Interface........................ 5-2 5.1.5 LLC2 Datalink............................. 5-2 5.2 Documentation Corrections for X.25 on OpenVMS Alpha......................................... 5-3 5.2.1 Manual References......................... 5-3 5.2.2 X.25 new Features Corrections............. 5-3 5.2.2.1 X.25 over TCP/IP - XOT.................. 5-3 5.2.2.2 X.25 Relay.............................. 5-3 iv 5.2.3 Programming Reference Corrections......... 5-3 5.2.3.1 Section 4.2.1 Open a Port............... 5-4 5.2.3.2 Section 4.2.2 Enable Attention AST...... 5-4 5.2.3.3 Section 4.2.5 Getting Port Information............................. 5-4 5.2.4 Appendix B: User-Written Datalink Protocols................................. 5-4 5.2.5 Appendix C: Example Programs.............. 5-4 5.2.6 Appendix D Obsolete Features of the $QIO Interface................................. 5-4 5.2.7 Section E.2 NCL Commands.................. 5-5 6 Additional Problem Solving Information 6.1 Poor Datalink Performance and Low X.25 Throughput on PBXDP-Ax Cards.................. 6-1 7 Installation of PBXDP and PBXDI Cards 7.1 Installation of PBXDP Cards................... 7-1 7.2 Installation of PBXDI-Ax Cards................ 7-1 v _________________________________________________________________ Preface These Release Notes apply to Version 1.6 ECO3 of HP X.25 for OpenVMS Alpha. This document is divided into seven chapters: o Chapter 1, Installation Information o Chapter 2, New Features o Chapter 3, Resolved Problems o Chapter 4, Known X.25 Problems o Chapter 5, Documentation Updates for X.25 and WANDD on Alpha o Chapter 6, Additional Problem Solving Information o Chapter 7, Installation of PBXDP and PBXDI Cards vii 1 _________________________________________________________________ Installation Information 1.1 Installation Instructions If you are installing HP X.25 for OpenVMS Alpha from the CD-ROM distribution, follow the instructions contained in the CD-ROM booklet. Otherwise, install the product with the PRODUCT command by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL X25/SOURCE=[location of the kit] The kit location may be a tape drive or a disk directory that contains the PCSI kit. The system must be rebooted for the new images to be loaded. __________ PRE-INSTALLATION WARNING ADVISORY __________ If you are upgrading to OpenVMS Alpha 7.3-1, you must first upgrade to X.25 Version 1.6 ECO3 or 1.6. Failure to upgrade to X.25 Version 1.6 ECO3 or 1.6 before upgrading to OpenVMS Alpha 7.3-1 will result in a SPLINVIPL bugcheck when starting X.25 at boot time. ______________________________________________________ Installation Information 1-1 2 _________________________________________________________________ New Features The version references in the left margin indicate in what version of the product the feature was first introduced. 2.1 Maintenance Release Only V1.6 This release is strictly a maintenance release for ECO3 supported OpenVMS Alpha platforms. No new features are provided. New Features 2-1 3 _________________________________________________________________ Resolved Problems This chapter discusses problems that were resolved between the 1.6 and 1.6 ECO3 Release. ECO3 is a cumulative release, it is not necessary to apply ECO2 prior to applying ECO3. 3.1 Problems Resolved in Version 1.6 ECO3 3.1.1 Deleting a DTE using the configurator does not remove all the DTE attributes When a DTE is deleted, all the attributes of a DTE are deleted from the NCL script except the Local DTE Class. This causes display of error messages during startup. The problem has been fixed in this release. Source: QXCM1000207698 / WFM 1205802843-121 3.1.2 Reconfigured LLC2 DTE resets the values to default when the user steps through the current values When modifying a LLC2 DTE with the X25$CONFIGURE utility, the values of the characteristics will be reset to defaults, even when the user only steps through the current values. The problem has been fixed in this release. Source: QXCM1000212246 / WFM 1205899041-121 3.1.3 Creation of more than 100 DTE results in a error When X25 is configured with more than 100 DTEs, the following error is displayed during startup. Node 0 X25 Protocol DTE DTE-103 at 2005-03-16-12:30:29.878+02:00Iinf command failed due to: no resources available Resolved Problems 3-1 The problem has been fixed in this release. The maximum number of DTEs that can be created now is 250. Source: QXCM1000226451 / WFM 1206952889-122 3.1.4 X.25 applications do not work using PVC and GAP The GAP server on Alpha does not handle the RESET IND packet from the GAP client properly, causing the application to abort. The GAP server code has been modified to fix this problem. Source: QXCM1000221538 / WFM 3209476275-323 3.1.5 PBXDD does not assert DTR when cable is removed/reinserted When the cable is removed/reinserted from the PBXDD, the NCL "show modem connect line" command indicates that DTR is asserted but the same is not indicated by the breakout box. The problem has been fixed in this release. Source: QXCM1000195198 and QXCM1000201831 / WFM 1205193387- 121 and WFM 1205426383-121 3.1.6 Diagnostic code not relayed back properly Diagnostic code not relayed back properly. The problem has been fixed in this release. Source: QXCM1000201084 / WFM 1205426376-121 V1.6 3.1.7 System Crash with RSVD_LP in GAP_DELETE_GSB ECO2 If a network error caused DECnet to terminate a Session Connection being established by GAP, in some situations this would result in a corrupt X.25 data structure which would lead to a system crash. The GAP code has been modified to prevent this situation. Source: CFS.97089 3.1.8 System Crash at X25$L1+11F70 Additional coding modifications, beyond the ones provided in ECO1 were needed to fully resolve this crash. Source: CFS.100759 3-2 Resolved Problems 3.1.9 PBXDD Buffer too small for SNA The buffer used by the PBXDD to receive inbound data did not correctly account for the size of the CRC in the HDLC header. The ZZDRIVER has been modified to correctly account for the CRC. Source: CFS.101193 3.1.10 M-bit Incorrectly Handled for GAP Connections The M-Bit was not correctly forwarded for GAP Server connections. The GAP Server code has been modified to correctly foward the M-Bit. Source: CFS.101769 3.1.11 Pool Corruption when using CUG with GAP Non-Paged pool was inadvertantly being corrupted when Closed User Groups were implemented over GAP connections. The GAP code has been modified to correct this issue. Source: CFS.102768 3.1.12 X.25 Relay Hangs with Depleted Credits In situations where large application packets were sent via X.25 Relay, which resulted in multiple packets with the M-Bit being set, relay would deplete the available credits for reception and the connection would hang. Relay has been modified to provide more credits for data reception. Source: CFS.103086 3.1.13 Rights Identifiers Corrupted by X25$CONFIGURE When configuring X25 Security, if long names were used for Rights Identifiers, the Identifier name could be corrupted, resulting in a failure to add the identifier. The code has been modified to correct the corruption issue. Source: CFS.103637 3.1.14 X25$CONFIGURE doesn't Allow PVC Configuration with XOT X25$CONFIGURE would not allow a PVC circtui to be configured over a XOT DTE. The configurator has been corrected so that PVC's can be created on XOT DTE's Source: CFS.103758 Resolved Problems 3-3 3.1.15 X25$SHUTDOWN.COM doesn't Delete some X.25 Entities X25$SHUTDOWN.COM was not correctly deleting X.25 Relay or XOT entities. The command procedure has been modified to correctly delete these entities. Source: CFS.104808 3.1.16 Multiple Issues with XOT In performing interoperability testing with other vendors, multiple issues with XOT were encountered. These issues have been corrected. Source: Engineering and Customer Testing V1.6 3.1.17 System Crash at X25$L1+11F70 ECO1 In certain situations, the ZZDRIVER can receive a message from the PBXDD card after the port associated with the card has been deleted. The driver has been modified to correctly discard any messages received for a non-existant port. Source: CFS.93541 3.1.18 Invalid Security State Bugcheck If a program makes multiple QIO/IO$_ACPCONTROL calls to an NW device and the SYSGEN parameter SYSTEM_CHECK is set to a non-zero value, the system will crash when the I/O channel to the NW device is deassigned. The NWDRIVER has been modified to properly account for I/O operations. Source: Engineering testing 3.1.19 Machine Check Crash During Load of X25$ZZDRIVER On ES47, ES80 or GS1280 hardware platforms, the system may crash during boot if a PBXDD card is installed on the system. The driver has been modified to increase the time between loading the PBXDD firmware and checking to see if the firmware is running, thus preventing PCI bus read timeouts. Source: Hardware qualification testing 3-4 Resolved Problems 3.1.20 Double Deallocation Bugcheck in X25$ACCESS.EXE A change implemented in 1.6 to prevent a memory leak resulted in a double deallocation of memory under certain circumstances. The code has been modified to prevent the double deallocation. Source: CFS.98308 3.1.21 VCRP Leak in Nonpaged Pool A number of memory leaks associated with X.25 Server functionality were fixed. Source: CFS.98567 3.1.22 ZZ Device Shows Offline On some hardware platforms, the PBXDD controller was not initializing correctly resulting in the ZZ device showing as offline. The PBXDD driver has been modified to assert the board reset signal for a longer period of time to ensure that the PBXDD correctly resets at boot. Source: CFS.98335 3.1.23 Inverted Clock Required with PBXDD The PBXDD card required that the clock signal on V.11 cables be inverted with repect to the requirements that the PBXDP card has. The firmware for the PBXDD card was modified so that the clock does not need to be inverted. Source: CFS.96901 Resolved Problems 3-5 4 _________________________________________________________________ Known X.25 Problems The version references in the left margin indicate in what version of these release notes the problem was first reported. 4.1 X.29 logins hang and incorrect terminal naming on OpenVMS 7.3-2 V7.3- A new feature was introduced in OpenVMS 7.3-2 that allows 2 device numbers to exceed 9999. When the NV device number increments past 9999, loginout.exe will fail and X.29 login attempts will appear to hang. OpenVMS Engineering is aware of the issue in loginout.exe and is working on a solution for 7.3-2 and later. In addition, SHOW USER, SHOW PROCESS and $GETJPI with JPI$_ TERMINAL will return truncated information about the NV terminal name which may result in display anomolies or unexpected behavior for programs that use this information. This issue will be addressed in a release of OpenVMS after 7.3-2. Either problem can be eliminated by setting bit 2 in SYSGEN's DEVICE_NAMING parameter, on most systems this will result in DEVICE_NAMING having a value of 4. Setting bit 2 will cause OpenVMS to use the previous behavior of wrapping device numbers back to zero once they exceed 9999. Source: Engineering Testing Known X.25 Problems 4-1 4.2 X25$APPLD Unexpectedly Exhausts BYTLM Quota V1.2 This problem was seen when a customer migrated an X.29 application from VAX to Alpha. The VAX systems were used to accommodate hundreds of simultaneous server-client connections for a real-time stock exchange application provided to remote interactive X.29 users. When this application was installed on Alpha production systems, remote users began to experience a lack of connectivity to their application. Investigation determined that this problem was the result of the X25$APPLD process on the Alpha systems quickly exhausting its BYTLM quota. Workaround: Dramatically increase the process quota and reboot those systems in order to retrieve the expected functionality for this application. Source: QAR.00085 4.3 Facility Code "Called Address Extension" Is Modified by the X.25 Software for CALLC Packet V1.2 A valid received X.25 call including the called and calling address extension will result in a modified called address extension in CALLC packet. If you using the standard X.25 examples to run a send/receive via X.25 you can reproduce the problem. The application which receives the call and an NCB with called/calling address extension does an IO$_ACCESS without modifying the content of the NCB, but the X.25 software does modify the contents. The expected facility called address extension is modified as in this example: received data value: C9 09 10 36 26 24 58 90 09 31 03 incorrectly modified value: C9 0A 12 36 26 24 58 90 09 31 03 0E Workaround: None, at this time. Source: QAR.00089 4-2 Known X.25 Problems 4.4 Error Messages During Reinstall/Upgrade of X.25 V1.2 If X.25 is installed on a system which already has an earlier version of the product installed, the following error messages are seen: %SYSTEM-W-NOSUCHFILE, no such file . . . (SYSTEM-W-NOSUCHFILE repeated a number of times) . . . %PCSIEERRCREACCT, error creating account X25$MAIL -SYSTEM-F-DUPIDENT, duplicate identifier %PCSIE-OPFAILED, operation failed These error messages can be ignored. In order for the installation to succeed you must answer "NO" to the question: Terminating is strongly recommended. Do you want to terminate? [YES] [NO] Known X.25 Problems 4-3 5 _________________________________________________________________ Documentation Updates for X.25 and WANDD on Alpha The version references in the left margin indicate in what version of these release notes the documentation update was first reported. HP X.25 for OpenVMS Alpha now supports a WANDD programming interface previously available only on the OpenVMS VAX platform. This product requires Version 7.2-2 of OpenVMS Alpha with Version 7.2-1 ECO4 of DECnet-Plus for OpenVMS Alpha or Version or 7.3 of OpenVMS Alpha and Version 7.3 of DECnet-Plus for OpenVMS Alpha. Information on WANDD programming is contained in the DECnet/OSI for VMS VAX WANDD Programming manual. Exceptions for OpenVMS Alpha are documented in this chapter. 5.1 Alpha Restrictions The following restrictions exist for the WANDD programming interface on OpenVMS Alpha. 5.1.1 Supported Devices The only devices supported are those currently supported by the HP X.25 for OpenVMS Alpha product. These include the following: V1.5 o PBXDD V1.2 o PBXDP o PBXDI o DNSES o DSYT1 o SCC Documentation Updates for X.25 and WANDD on Alpha 5-1 Ignore all devices listed in Section 1.2 and elsewhere in the DECnet/OSI for VMS VAX WANDD Programming manual because these are VAX-only devices. 5.1.2 Framing V1.3 BISYNC framing is now supported when using the PBXDP card. ECO- 01 V1.2 Except as noted in the preceding paragraph, only HDLC framing is supported on the HP X.25 for OpenVMS Alpha product. In particular, the BISYNC framing, DDCMP framing, and GENBYTE framing described in the manual are VAX-only. 5.1.3 Half-Duplex and Multipoint Operations V1.3 Half-duplex is now supported when using the PBXDP card. ECO- 01 V1.2 Except as noted in the preceding paragraph, half-duplex operations and multipoint operations are not supported. 5.1.4 Obsolete Interface V1.2 The obsolete interface described in Appendix D of the manual is not supported on OpenVMS Alpha. 5.1.5 LLC2 Datalink V1.2 In addition to support for the HDLC and LAPB datalink protocols discussed in the DECnet/OSI for VMS VAX WANDD Programming manual, there is support for the LLC2 datalink. To open a datalink port to an LLC2 datalink, the name of the datalink specified through the P1 parameter of the IO$_ CREATE call (see section 4.2.1 of the manual) must be of the form LLC2.sap-name.link-name. For example, to use an LLC2 link called my-link which is a subentity of my-sap, specify a datalink name of LLC2.MY-SAP.MY-LINK. The datalink name specified in an IO$_CREATE call (see section 4.2.1 of the manual) can be a system logical name which translates to a string of the required form. 5-2 Documentation Updates for X.25 and WANDD on Alpha 5.2 Documentation Corrections for X.25 on OpenVMS Alpha 5.2.1 Manual References For any references to OpenVMS operating system manuals or DECnet-Plus manuals, please refer to the Version 7.1 documents. In some cases, the names of the manuals have changed. 5.2.2 X.25 new Features Corrections 5.2.2.1 X.25 over TCP/IP - XOT V1.4 For PVC circuits to interoperate correctly over a XOT DTE, it is necessary to specify additional information in the NCL configuration for the PVC. Each XOT PVC must have a REMOTE PVC NAME specified via NCL, via the command: SET X25 PROTOCOL DTE dte-name PVC pvc-name REMOTE PVC NAME "name" The name should match the name configured on the remote system. The X25$CONFIGURATOR does not support this attribute when creating a PVC, so the appropriate NCL command should be placed in the file SYS$STARTUP:X25$EXTRA_ SET.NCL 5.2.2.2 X.25 Relay V1.4 In order for the calling DTE to be forwarded on a Relay connection, the DTE that received the inbound call must be configured to be in DCE mode. 5.2.3 Programming Reference Corrections The following sections provide Alpha-specific information that differs from the VAX-only information in Chapter 4 of the DECnet/OSI for VMS VAX WANDD Programming manual. Documentation Updates for X.25 and WANDD on Alpha 5-3 5.2.3.1 Section 4.2.1 Open a Port V1.2 The P1 argument to the IO$CREATE call can also be LLC2, as described in Section 5.1.5 of these release notes. The following items codes listed in Table 4-4 are ignored in the HP X.25 for OpenVMS Alpha product: o dll$k_auto_start o dll$k_auto_restart o dll$k_buffer_limit The item code dll$k_profile listed in Table 4-4 fails on Alpha, if the profile does not match. 5.2.3.2 Section 4.2.2 Enable Attention AST V1.2 The following two status codes listed in Table 4-5 are never generated on Alpha: o dll$m_sts_physical_loopback o dll$m_err_threshold_exceeded 5.2.3.3 Section 4.2.5 Getting Port Information V1.2 In Table 4-7, the dll$k_buffer_limit item code always returns TRUE on Alpha. 5.2.4 Appendix B: User-Written Datalink Protocols V1.2 Only Section B.2 on HDLC Framing is applicable to the HP X.25 for OpenVMS Alpha. Remaining sections of Appendix B are VAX only. 5.2.5 Appendix C: Example Programs V1.2 To compile the example programs in Section C.1, use the following: $ cc WANDRIVER_READ_EXAMPLE.C+sys$library:sys$lib_c/lib The programs in Section C.2 are VAX-only. 5.2.6 Appendix D Obsolete Features of the $QIO Interface V1.2 The interface is VAX-only and is not supported by the HP X.25 for OpenVMS Alpha product. 5-4 Documentation Updates for X.25 and WANDD on Alpha 5.2.7 Section E.2 NCL Commands V1.2 The section on Issuing NCL Commands for DDCMP is VAX-only and is not supported by the HP X.25 for OpenVMS Alpha product. Following is new information on issuing NCL commands for LLC2: Issuing NCL Commands for LLC2 If you are going to use the LLC2 module you must CREATE, SET and ENABLE an LLC2 sap and link. NCL> CREATE LLC2 SAP sap-name NCL> SET LLC2 SAP sap-name LAN STATION lan-name, - _NCL> LOCAL LSAP ADDRESS sap-addr NCL> CREATE LLC2 SAP sap-name LINK link-name NCL> SET LLC2 SAP sap-name LINK link-name - _NCL> REMOTE MAC ADDRESS mac-addr NCL> SET LLC2 SAP sap-name LINK link-name - _NCL> REMOTE LSAP ADDRESS rsap-addr NCL> ENABLE LLC2 SAP sap-name NCL> ENABLE LLC2 SAP sap-name LINK link-name Replace the variables like this: sap-name is the name you want to give to the LLC2 sap lan-name is the name of the LAN device over which LLC2 is to run, for example, CSMACD STATION csmacd-0 lsap-addr is the value of the LOCAL Service Access Point address, which should normally be 7E but if another value MUST be used an even value must be specified, for example, 7C (but not 7D or 7F) link-name is the name you want to give to the LLC2 link (note there can be multiple LLC2 links to an individual LLC2 sap) mac-addr is the 6-byte LAN MAC address of the interface to be used on the remote system, for example, AA-00-04-00-16-10 Documentation Updates for X.25 and WANDD on Alpha 5-5 rsap-addr is the value of the REMOTE Service Access Point address, which should normally be 7E but if another value MUST be used an even value must be specified, for example, 7C (but not 7D or 7F) Other LLC2 attribute values are described in the DECnet- Plus Network Control Language Reference manual. See the X.25 for OpenVMS Alpha Systems-Configuration Guide for more information on LLC2 configuration. 5-6 Documentation Updates for X.25 and WANDD on Alpha 6 _________________________________________________________________ Additional Problem Solving Information This chapter supplements information contained in the X.25 for OpenVMS Alpha Systems-Problem Solving Guide. The version references in the left margin indicate in what version of these release notes the information was first reported. 6.1 Poor Datalink Performance and Low X.25 Throughput on PBXDP-Ax Cards V1.2 The X.25 software takes no notice of the Ring Indicator (RI) signal; however, the RI signal can affect X.25 (and WANDD) operation with PBXDP-Ax boards. The PBXDP- Ax series of boards are wired so that RI transitions also cause a transition on Data Carrier Detect (DCD). If the corresponding modem connect line uses "full" modem control, this DCD transition may cause the loss of one or more incoming frames. The normal datalink protocol error recovery mechanisms will recover from the frame loss by retransmitting the lost frames; however, the result will be suboptimal performance due to the retransmissions. The frame is discarded by the modem connect module, because the DCD transition is seen as a loss of communication between the local and remote modems. A DCD transition due to an RI transition shows itself through software in a number of ways: 1. A datalink trace will show a Line Up event without a preceding Line Down event. If the trace indicates lost frames before the Line Up event, then it is possible (but not certain) that the lost frames were discarded due to a DCD state transition. Additional Problem Solving Information 6-1 2. A modem connect trace will show a modem connect line state transition from FDPX_BOTH (Full Duplex line, both receive and transmit enabled) to FDPX_TRANSMIT (transmit only enabled) on the "asserted to unasserted" transition of DCD, and a modem connect line state transition from FDPX_TRANSMIT to FDPX_BOTH on the "unasserted to asserted" transition of DCD. Any frames received while the modem connect line is in the FDPX_TRANSMIT state will be quietly discarded (they will not appear in the trace). Customers should ensure that the Ring Indicator signal on all PBXDP interfaces remains stable. Wiring RI to Signal Ground is one way of accomplishing this. 6-2 Additional Problem Solving Information 7 _________________________________________________________________ Installation of PBXDP and PBXDI Cards The version references in the left margin indicate in what version of these release notes the information was first reported. 7.1 Installation of PBXDP Cards V1.2 PBXDP (PCI synchronous communications) cards may be simply plugged into an unoccupied PCI slot in the system. Any PBXDP cards will be automatically recognized when the X.25 or WAN software is configured. 7.2 Installation of PBXDI-Ax Cards V1.2 Installing the PBXDI-Ax card requires the following steps: 1. Invoke the console utility ICONFIG to specify the adapter configuration parameters: I/O register base, IRQ and memory base. 2. Set the adapter I/O register base through the adapter switches. The other adapter configuration parameters are set by operating system software from the values specified to the ICONFIG utility. 3. Set the jumpers for the electrical interface to be used (necessary only on boards supporting the EIA-232 and V.35 electrical interface). 4. Physically install the adapter into the system. It is recommended that the console configuration commands (step 2) be issued before setting the adapter IO register base so that any console detected resource conflict can be rectified BEFORE physically configuring the adapter IO register base. Installation of PBXDP and PBXDI Cards 7-1 These steps will now be described in more detail. 1. Invoke the console utility ICONFIG, for example: >>> iconfig ISA CONFIGURATION UTILITY Name I/O IRQ DMA Mem Length Enabled MOUSE 60 12 Y KBD 60 1 Y COM1 3f8 4 Y COM2 2f8 3 Y LPT1 3bc 7 Y FLOPPY 3f0 6 2 Y On an OpenVMS Alpha system, enter PBXDI-A2 (2-port PBXDI-Ax card) or PBXDI-A4 (4-port PBXDI-Ax card) or PBXDI-A (generic PBXDI-Ax card, number of ports unspecified) or PBXDI (generic PBXDI-Ax card, number of ports unspecified). The I/O base address must be a multiple of 0x10. The factory configured address is 0x300 which is not in use by any other device on this particular system so that may be selected. The IRQ must be one of 3, 5, 7, 10, 11, 12 or 15. The selected IRQ must not be in use by any other device. On this particular system IRQ 5 is the lowest PBXDI IRQ not in use by any other device so specify that. The PBXDI does not use a DMA channel so TAB over that field. The Mem value must be a multiple of 0x4000 (16K). On this particular system no other device uses any ISA memory so 0 may be selected. The Length field must be specified as 4000. The Enabled field must contain Y otherwise the console will not tell the operating system about the device. After configuration: 7-2 Installation of PBXDP and PBXDI Cards ISA CONFIGURATION UTILITY Name I/O IRQ DMA Mem Length Enabled MOUSE 60 12 Y KBD 60 1 Y COM1 3f8 4 Y COM2 2f8 3 Y LPT1 3bc 7 Y FLOPPY 3f0 6 2 Y PBXDI-A 300 5 0 4000 Y Subsequent PBXDI-Ax cards could be configured with I/O 310, 320 (etc), IRQ 10, 11 (etc.) and memory 4000, 8000 (etc). 2. Set the Adapter I/O register base address. See Section 5.11 of the accompanying manual. 3. Set the appropriate electrical interface. This is required only if a board supporting V.35 or RS-232 is to be installed. See Appendix B of the accompanying manual. 4. Physically install the adapter into the system. See the appropriate system manual for details on installing expansion adapters. Installation of PBXDP and PBXDI Cards 7-3