1. Manuals
  2. Brands
  3. Bay Networks Manuals
  4. Software
  5. 5399
  6. Release note

Bay Networks 5399 Release Note

Remote access software
Hide thumbs Also See for 5399:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Manual
Remote Access
Software Version 5.3

Release Notes

Marketing Release 5.3
Part No. 300115-B Rev. A
January 1998

Advertisement

Table of Contents
loading

Related Manuals for Bay Networks 5399

Summary of Contents for Bay Networks 5399

  • Page 1: Release Notes

    Remote Access Software Version 5.3 Release Notes Marketing Release 5.3 Part No. 300115-B Rev. A January 1998...

  • Page 2: Restricted Rights Legend

    Software License is included in this document. Bay Networks is a registered trademark and Remote Annex, Quick2Config, RouterMan, SN, SPEX, Switch Node, System 5000, Bay Networks Press, and the Bay Networks logo are trademarks of Bay Networks, Inc. Microsoft, MS, MS-DOS, Win32, Windows, and Windows NT are registered trademarks of Microsoft Corporation.
  • Page 3 SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. In addition, the program and information contained herein are licensed only pursuant to a license agreement that contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed by third parties).
  • Page 4 300115-B Rev. A...

  • Page 5: Bay Networks Customer Service

    Ordering Bay Networks Publications To purchase additional copies of this document or other Bay Networks publications, order by part number from Bay Networks Press following numbers: The Bay Networks Press catalog is available on the World Wide Web at support.baynetworks.com/Library/GenMisc. Bay Networks publications are available on the World Wide Web at support.baynetworks.com/Library/tpubs.
  • Page 6 Contacting Bay Networks How to Get Help If you purchased a service contract for your Bay Networks product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. If you purchased a Bay Networks service program, call one of the following Bay Networks Technical Solutions Centers: Technical Solutions Center Billerica, MA...

  • Page 7: Table Of Contents

    Supported Software and Switch Types........
  • Page 8 Contents SPR 11019 ................37 SPR 11241 .
  • Page 9 SPR 10137 ............... 73 SPR 10255 .
  • Page 10 Contents Placing the File onto the RAC ............94 Using monitor Mode to Provide an IP Address for a New Unit .
  • Page 11 Library/tpubs. Check this site for late information that is not included in this version of the release notes. These Release Notes address the following topics: • Supported RAC Hardware For Release 5.3 • Supported Software and Switch Types • 56K Modem Support • New CLI Commands in R14.1.9 •...

  • Page 12: Supported Remote Annex/Rac Hardware For Release 5.3

    • Changes to Remote Annex Server Tools for Windows NT R3.1 • 24-Hour Unit Replacement Service • 5399 RAC • 8000 RAC Although your distribution media contain Release 5.3 for Remote Annexes, do not install Release 5.3 on any Remote Annex (that is, on any of the following platforms: RA2000, RA4000, RA6100, RA6300, RA5390, RA5391, or RA5393).

  • Page 13: Supported Software And Switch Types

    Supported Software and Switch Types Release 5.3 supports or is compatible with a number of operating systems, compilers, switch types, and security servers. Supported Operating Systems The distribution media contain binary files for the supported operating systems. When the installation script detects that there are binary files for the host operating system, it gives you the option of installing the binary files or loading the source code and compiling the software at a later time.

  • Page 14: Supported Compiler Versions

    Remote Access Software Version 5.3 Release Notes Supported Compiler Versions Release 14.1.9 supports the following compiler versions: RADIUS Server Information The embedded RADIUS client in Remote Access Software Release 5.3 is known to be compatible with the following RADIUS servers: SecurID/ACE Compatibility Information Remote Access Software Release 5.3 is compatible with SecurID/ACE Server Version 2.2.

  • Page 15: Safeword Compatibility Information

    SafeWord server, and is compatible with Version 4.1 of the SafeWord UNIX client. There is no support for Windows NT. Supported Switch Types Table 1 lists the PRI switch types supported in Release 14.1.9. Table 1 Valid PRI switch_type Values Protocol switch_type Description...
  • Page 16 Table 2 Valid CAS switch_type Values Protocol Channelized T1 Channelized T1 - R1 Channelized E1 - P7 Channelized E1 - R2 300115-B Rev. A lists the CAS switch types supported in Release 14.1.9. switch_type UST1 HKT1 UST1FD TWT1R1 SWE1P7 BBE1R2...

  • Page 17: 56K Modem Support

    56K Modem Support Release 5.3 introduces support on the 5399 RAC and the 8000 RAC for 56K modems using the Rockwell Semiconductor/Lucent Technologies K56flex protocol. Support for 56K modems using the U.S. Robotics x2 protocol (also on the 5399 RAC and the 8000 RAC) was introduced in Release 5.2.

  • Page 18: Notes On K56Flex 56K Modem Support

    Remote Access Software Version 5.3 Release Notes Notes on K56flex 56K Modem Support Rockwell has acknowledged several problems with K56flex in an A law environment. These problems are in the K56flex protocol, and are common to all K56flex platforms. It is expected that Rockwell will release modem software that will correct this problem.

  • Page 19: Notes On X2 56K Modem Support

    Robotics test line may be routed differently than a call to your own facility. The only way to find out for certain if your line is compatible with x2 is to borrow a 56K modem and dial in to your 5399 RAC or 8000 RAC from your home or office.

  • Page 20: Using The Set56K Command

    Remote Access Software Version 5.3 Release Notes Using the set56k Command The superuser CLI command set56k allows you to configure your RAC for 56K modem support if it does not have 56K modems enabled already. The set56k command uses a password as its argument; the key value indicates to the RAC which 56K modem protocol to enable.

  • Page 21: Exchanging Your Rac

    Remote Access Software Version 5.3 Release Notes An example configuration session follows. In this example, the specific key value that is used sets x2 as the 56K protocol; however, the procedure is identical for setting K56flex as the 56K protocol. command: set56k none command: set56k <key value>...

  • Page 22: Digital Modem Configuration Parameter Changes

    Remote Access Software Version 5.3 Release Notes Digital Modem Configuration Parameter Changes Bit settings for 17 of the digital modem configuration parameters have changed; many of the new bit settings support 56K modems. Refer to Appendix A of the manual Managing Remote Access Concentrators Using Command Line Interfaces for complete instructions on configuring and using these parameters.

  • Page 23: Parameter 5

    Remote Access Software Version 5.3 Release Notes L: Host Link Passthrough 00: Inbound remove 01: Inbound passthrough 10: Inbound translate to outbound 11: Inbound translate and pass Parameter 5 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Value 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 Descr.

  • Page 24: Parameter 6

    Remote Access Software Version 5.3 Release Notes Parameter 6 Value Descr. Default config_bytes Setting: Decimal base: 1 Octal base: 01 Hexadecimal base: 0x1 D: DCE Databits 0: Databits 7 1: Databits8 P: DCE Parity 000: Parity None 001: Parity Even 010: Parity Odd 011: Parity Mark 100: Parity Space...

  • Page 25: Parameter 7

    Remote Access Software Version 5.3 Release Notes Parameter 7 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Value 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 Descr.

  • Page 26: Parameter 14

    Remote Access Software Version 5.3 Release Notes Lost CD Time: The modem waits the specified multiple of 100 milliseconds (the default value is 14, i.e., 1.4 seconds) after loss of carrier to report a failure and drop the connection. Message: No carrier Disconnect reason: Carrier lost Parameter 14 Value...

  • Page 27: Parameter 16

    Remote Access Software Version 5.3 Release Notes Parameter 16 15 14 13 12 11 10 9 8 Value 0 0 0 0 0 0 0 0 0 Descr. Unused Default config_bytes Setting (for V.34 and V.32): Decimal base: 17 Octal base: 021 Hexadecimal base: 0x11 Default config_bytes Setting (for x2): Decimal base: 52...
  • Page 28 Remote Access Software Version 5.3 Release Notes 1110: Speed 26400 1111: Speed 28800 10000: Speed 31200 10001: Speed 33600 (default for V.34 and V.32) 10010: Reserved 10011: Reserved 10100: Reserved 10101: Reserved 10110: Speed 25333 (x2) 10111: Speed 26666 (x2) 11000: Speed 28000 (x2) 11001: Speed 29333 (x2) 11010: Speed 30666 (x2)

  • Page 29: Parameter 18

    Remote Access Software Version 5.3 Release Notes 110001: Speed 54000 (K56flex) 110010: Speed 54666 (x2) 110011: Speed 56000 (K56flex)/(x2) 110100: Speed 57333 (x2) (default for x2) 110101: Speed 58000 (K56flex) 110110: Speed 60000 (K56flex) (default for K56flex) Parameter 18 15 14 13 12 11 10 9 8 Value 0 0 0 0 0 0 0 0 0 Descr.
  • Page 30 Remote Access Software Version 5.3 Release Notes 1111: Speed 28800 10000: Speed 31200 10001: Speed 33600 10010: Reserved 10011: Reserved 10100: Reserved 10101: Reserved 10110: Speed 25333 (x2) 10111: Speed 26666 (x2) 11000: Speed 28000 (x2) 11001: Speed 29333 (x2) 11010: Speed 30666 (x2) 11011: Speed 32000 (K56flex)/(x2) 11100: Speed 33333 (x2)

  • Page 31: Parameter 21

    Remote Access Software Version 5.3 Release Notes 110010: Speed 54666 (x2) 110011: Speed 56000 (K56flex)/(x2) 110100: Speed 57333 (x2) 110101: Speed 58000 (K56flex) 110110: Speed 60000 (K56flex) Parameter 21 15 14 13 12 11 10 9 8 7 6 5 4 3 Value 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Descr.

  • Page 32: Parameter 26

    Remote Access Software Version 5.3 Release Notes Parameter 26 Value Descr. Default config_bytes Setting: Decimal base: 31 Octal base: 037 Hexadecimal base: 0x1F Pre-emphasis Filter - Pre-emphasis is an equalization method in which the transmission signal spectrum compensates for amplitude distortion.

  • Page 33: Parameter 30

    Remote Access Software Version 5.3 Release Notes MC: Mandatory Carrier Frequency - This option, effective only if Channel Probing is disabled, allows you to manually specify which carrier frequency (high or low) to use in V.34 modulation. Six baud rates are specified in V.34 modulation: 2400, 2743, 2800, 3000, 3200, and 3429.

  • Page 34: Parameter 32

    Remote Access Software Version 5.3 Release Notes T: Trunk Type 00: PRI 01: T1/E1 10: Reserved 11: Reserved RB: Robbed Bit Signaling 0: Disable 1: Enable P: Higher Level Protocol Optimization 000: None 001: PPP Framing 010: PPP AHDSL 011: Reserved 100: Reserved 101: Reserved 110: Reserved...

  • Page 35: Parameter 34

    Remote Access Software Version 5.3 Release Notes Parameter 34 15 14 13 12 11 10 9 8 Value 0 0 0 0 0 0 0 0 0 Descr. Unused Default config_bytes Setting: Decimal base: 99 Octal base: 0143 Hexadecimal base: 0x63 Eq: Equalizer Type - This is for V.32 operation only and is provided to support certain international line conditions.

  • Page 36: Parameter 35

    Remote Access Software Version 5.3 Release Notes Parameter 35 Value Descr. Default config_bytes Setting: Decimal base: 0 Octal base: 00 Hexadecimal base: 0x0 EP: Echo Protection Tone - When this option is enabled, the modem sends an unmodulated carrier signal prior to the training and data signals to disable the telephone network echo suppressor.

  • Page 37: Parameter 38

    Remote Access Software Version 5.3 Release Notes CT: V25 Calling Tone - V25 calling tone. This tone is used in some international modems to identify a data call from a voice call. 0: Disable 1: Enable Parameter 38 15 14 13 12 11 10 9 8 7 6 5 4 3 Value 0 0 0 0 0 0 0 0 0 0 0 0 0 Descr.

  • Page 38: Parameter 39

    Remote Access Software Version 5.3 Release Notes This should be done only when normal operation is not possible and the telco indicates that such a conversion is taking place. Enabling this feature may result in an inability to achieve connect speeds in excess of 31.2 Kb/s.

  • Page 39: Known Modem Compatibility

    Known Modem Compatibility Table 3 5.3. This list is not comprehensive; a modem’s absence from this list does not mean that that modem is not compatible with Release 5.3. Table 3 Modems Known To Be Compatible With Release 5.3 Type Manufacturer V.32t AT&T Paradyne...
  • Page 40 Remote Access Software Version 5.3 Release Notes Table 3 Modems Known To Be Compatible With Release 5.3 (Continued) Type Manufacturer V.34b Hayes V.34 Hayes V.32b Hayes Maxtech Internal V.34b Maxtech V.34b Microcom V.34 Microcom V.32b Motorola Motorola V.34b Motorola V.34 Motorola V.34 Motorola UDS...
  • Page 41 Table 3 Modems Known To Be Compatible With Release 5.3 (Continued) Type Manufacturer V.34b US Robotics V.34 US Robotics V.34 US Robotics V.32b US Robotics V.32b US Robotics V.34b US Robotics V.34b US Robotics US Robotics V.22b Zenith V.32b ZOOM V.34 ZOOM V.32b ZOOM...

  • Page 42: New Cli Commands In R14.1.9

    Remote Access Software Version 5.3 Release Notes Table 3 Modems Known To Be Compatible With Release 5.3 (Continued) Type Manufacturer V.34 Psion Dacom V.34b Zoom Telephonic Xircom V.34b Xircom ZOOM Global Village Diamond Multimedia New CLI Commands in R14.1.9 Four commands have been added to the command line interface, history, ppp -i, reset annex filter, and list -r.

  • Page 43: Ppp -I

    Ctrl-p and Ctrl-n work without a <CR>; use them to scroll backward and forward through the command history. ppp -i The -i argument now may be used with the ppp command. This argument displays the locally configured local and remote addresses. New admin/na Parameters in R14.1.9 Four configuration parameters have been added.

  • Page 44: Radius Filters

    Remote Access Software Version 5.3 Release Notes RADIUS Filters RADIUS filters now reside on the unit, rather than on the RADIUS server. The unit reads these filters when it boots, and stores the filters in memory, applying them only to Framed PPP or SLIP users. This is achieved through the use of a %filters section in the unit’s configuration file.
  • Page 45 Remote Access Software Version 5.3 Release Notes A filter definition consists of these arguments, which are explained in Table <direction> <scope> <family> <criteria> <actions> Table 4 Filter Definition Arguments Argument Valid Values direction input, output scope include, exclude family criteria dst_addr, dst_port, src_port, src_address, address_pair,...

  • Page 46: Tmux And Tstty

    Remote Access Software Version 5.3 Release Notes TMUX and TSTTY As of Release 5.3, support for TMUX and TSTTY is discontinued. This is an issue only for customers who are using Remote Annexes. Known Problems/Limitations in R14.1.9 Problems Resolved Since R14.1 SPR 11117 Tunnel key decryption of the RADIUS received encrypted attribute is now supported on the unit.

  • Page 47: Spr 11019

    RADIUS filters now reside on the unit, reducing additional network traffic and making them easier to manage. SPR 10851 Switch type INE1R2_2 now is recognized by the WAN Manager. SPR 11128 The unit no longer responds to ICMP router solicitations when routed is set to no.

  • Page 48: Spr 11247

    Remote Access Software Version 5.3 Release Notes SPR 11247 The parameters pref_nbns1_addr and pref_nbns2_addr have been added for primary and secondary NBNS (WINS) addresses per RFC 1877. SPR 11368 PRI E1 SNG no longer is detected incorrectly as T1. SPR 10954 You can change the unit’s username and password prompts via embedded RADIUS using the parameters radius_user_prompt and radius_pass_prompt.

  • Page 49: Features In Release 5.1

    Features in Release 5.1 The following sections describe the features supported in Release 5.1: Remote Access Software Version 5.3 Release Notes • Bay Networks Remote Access Concentrators (RACs) • BayDSP (Digital Signal Processing) Modem Technology • AFD (Automatic Firmware Download) Changes •...
  • Page 50 Remote Access Software Version 5.3 Release Notes Table 5 Table 5 New Feature Support 300115-B Rev. A summarizes new feature support by platform. DSP modems Automatic Firmware Download Single number dial-up Channel and modem error detection Obsolete option_key Embedded RADIUS client Multi-System Multilink PPP Long user names V.110 support...

  • Page 51: Bay Networks Remote Access Concentrators (Racs)

    (RACs) The 5399 RAC and the 8000 RAC introduce a number of new features. The 5399 RAC is a member of the existing 539x family of Remote Access products built for the Bay Networks 5000 hub. The new high-performance Remote Access Concentrator features industry-leading dial access density, security, call management, and BayDSP integrated Digital Signal Processing (DSP) modem technology.

  • Page 52: Afd (Automatic Firmware Download) Changes

    Remote Access Software Version 5.3 Release Notes AFD (Automatic Firmware Download) Changes This section describes a new superuser CLI command, afd, and other changes to AFD not reflected in the Release 5.1 UNIX documentation. The afd Command The new superuser afd command allows manual downloading of firmware for a designated WAN module.

  • Page 53: How Afd Works

    file name and version information, separated by white space. The version information is divided into three fields, separated by semicolons (;). The first field is the hardware type; the second field is the switch type (as set by the WAN switch_type parameter); and the third field is the version string.
  • Page 54 • If the hardware type is “CAS T1.*” or “CAS E1.*” and there is no firmware in the module, the switch type is ignored, and the firmware image downloaded is the one appropriate for the first hardware type (CAS T1 or CAS E1) in afd_list that matches the hardware type of the module.

  • Page 55: Single Number Isdn Dial-Up

    Remote Access Software Version 5.3 Release Notes Single Number ISDN Dial-Up The single number ISDN dial-up feature allows you to configure the unit to discriminate automatically between the various protocols that may be used for dial-up over ISDN. This allows you to lower operating costs by purchasing a single dial-in number to cover all remote access needs, rather than having separate numbers for TA (V.120 and V.110), synchronous PPP, and modem users.

  • Page 56: Counting The Call Events

    This message from a WAN module to a WAN manager process on the main processor indicates that the central office switch has sent a channelized T1/E1 seize event. This message from a WAN module to a WAN manager process on the main processor indicates that a call has arrived.
  • Page 57 Table 8 Event Count Discrepancy Causes Missing Event Description RING Call aborted, “short seize”. Modem No modem available. assignment CONNECT Call aborted, “short seize”. Chat process Modem error or hang-up. finished Modem did not establish a assertion connection with its peer. Remote Access Software Version 5.3 Release Notes Cause The T1/E1 is misconfigured, or the caller...

  • Page 58: Specifying The Consecutive Failure Threshold

    Remote Access Software Version 5.3 Release Notes Specifying the Consecutive Failure Threshold Error reporting is configurable through the use of two SNMP annex parameters, ds0_error_threshold for channel event counts, and modem_error_threshold for modem event counts. Each parameter specifies the number of consecutive failures to reach DCD assertion that is allowed before busying out the channel or modem and sending a syslog message and SNMP trap.

  • Page 59: Resetting The Consecutive Failure Counts To Zero

    Remote Access Software Version 5.3 Release Notes Issuing either command without arguments displays the event counts for all channels or all modems, respectively. Issuing either command with the flag -f displays only those channels or modems that have consecutive failure counts greater than 0. Resetting the Consecutive Failure Counts to Zero The consecutive failure counts for a range of channels or modems can be reset by issuing the inchanerr command or the inmoderr command with...

  • Page 60: Embedded Radius Client

    Remote Access Software Version 5.3 Release Notes Since the features now enabled by default consume a significant amount of memory, you may want to disable those that you do not use. To do so, use the Annex parameter disabled_modules. Embedded RADIUS Client Release 5.1 includes an embedded RADIUS client.

  • Page 61: Multi-System Multilink Ppp

    RADIUS. Multi-System Multilink PPP Release 5.1 supports multi-system Multilink PPP (MMP) on platforms that support PRI connections: RA 6300, RA 5393, 5399 RAC, and 8000 RAC. MMP is a superset of Multilink PPP, allowing MP links belonging to the same MP bundle to terminate on multiple RACs.

  • Page 62: Long User Names

    Remote Access Software Version 5.3 Release Notes MMP is disabled by default, through the annex parameter mmp_enabled set to n. To enable MMP, you must set mmp_enabled to y and configure the global port or inbound channels for MP, if you have not done so already.

  • Page 63: Data Compression Card

    The status of the GSY port is displayed along with that of the other port classes when you issue the stats command. Data Compression Card The Model 5399 and Model 8000 RACs support an optional data compression card which provides a hardware implementation of Stac LZS compression and Microsoft’s Point-to-Point Compression Protocol (MPPC).

  • Page 64: Radius Attributes - Additional Information

    Remote Access Software Version 5.3 Release Notes The RADIUS attributes Unassigned(17), Unassigned(21), Termination-Action(29), Proxy-State(33), Login-LAT-Group(36), Framed-AppleTalk-Link(37), Framed-AppleTalk-Network(38), and Framed-AppleTalk-Zone(39) are not supported in this release. RADIUS Attributes - Additional Information After changing the setting of the auth_protocol parameter, you must reboot the unit in order for the change to take effect.
  • Page 65 Remote Access Software Version 5.3 Release Notes Table 9 RADIUS Attributes Value Description Unknown Telephone disconnect: caller hung up Dial failed WAN manager error Disconnect reset Error from adm_notify() Modem down from adm_notify() PPP protocol disconnect Inactivity timer (port data) CLI “hangup”...
  • Page 66 Remote Access Software Version 5.3 Release Notes Table 9 RADIUS Attributes (Continued) Value Description 300115-B Rev. A Modem dead PPP LCP negotiation failure PPP last NCP failure (IPCP) PPP last NCP failure (IPXCP) PPP last NCP failure (ATCP) PPP last NCP failure (CCP) PPP last NCP failure (MP) PPP last NCP timeout (IPCP) PPP last NCP timeout (IPXCP)
  • Page 67 Remote Access Software Version 5.3 Release Notes Table 9 RADIUS Attributes (Continued) Value Description PPP VPN LCP phase failure PPP VPN AUTH phase failure PPP MP invalid port configuration PPP invalid operation for device type PPP MMP bundle discovery failure DVS registration failure DVS home agent deregistration DVS tunnel no renew...

  • Page 68: Cli Ip Host Filtering - Corrected Information

    Remote Access Software Version 5.3 Release Notes Annex-Disconnect-Reason (Bay Networks VSA 46): This integer attribute describes the composite disconnect reason reported by the unit. Essentially, this attribute is the more important of the Annex-System- Disconnect and Annex-Modem-Disconnect reasons. Its values are the same as those from Annex-System-Disconnect with the addition of those listed in Table 11 Unit Disconnect Reasons...

  • Page 69: Call Disconnect Reasons

    Remote Access Software Version 5.3 Release Notes Call Disconnect Reasons The 5399 RAC and 8000 RAC provide call and modem disconnect reasons through the CLI histcall command, through the SNMP MIB objects callHistDisconnectReason, callHistAsyModemDisconnectReason, and callHistCompositeDisconnectReason, and through RADIUS accounting attributes.
  • Page 70 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason Success Indication Explanation CD Timer Expired No Carrier 300115-B Rev. A Unsuccessful The local (RAC) modem did not detect carrier within the designated amount of time.
  • Page 71 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason Success Indication Explanation Carrier Lost Indeterminate Modem Reset Forced WAN/Channel Reset Forced Dead Modem Reset Unsuccessful This indicates that the received signal was lost for a consecutive time longer than the debounce timer (1.4 seconds) without...
  • Page 72 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason Success Indication Explanation Modem Protocol - Remote Modem Cleardown 300115-B Rev. A Graceful This indicates a modem protocol teardown by the modem at the remote end. The client software initiated a modem hangup request via the modem's AT...
  • Page 73 The modem hung up because it failed to negotiate a retrain (within 20 seconds), probably due to poor line conditions. The caller/switch hung Busy or disconnect was received from the switch when attempting to place an outgoing call. 300115-B Rev. A...
  • Page 74 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason Success Indication Explanation pppTerm InactivityTimer HangupCmd Last Job MaxLogon SlaveNormal 300115-B Rev. A Graceful The remote side initiated an LCP terminate. This would likely be due to the user requesting a termination of the session.
  • Page 75 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason Success Indication Explanation Slave Error Unsuccessful CLI Inactivity Forced Timer Port Reset Forced CLI Auth Fail Authentication/ authorization slave Auth Fail Authentication/ authorization pppPapFail Authentication/ authorization pppChapFail Authentication/...
  • Page 76 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason pppLastNCPFailIpcp pppLastNCPFailIpxcp pppLastNCPFailAtcp pppLastNCPFailCcp PppLastNCPFailMp 300115-B Rev. A Success Indication Explanation Unsuccessful The NCP protocol (IPCP) failed negotiations, and all other NCP protocols failed before IPCP or were not negotiated at all.
  • Page 77 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason Success Indication Explanation PppLastNCPToIpcp Unsuccessful pppLastNCPToIpxcp Unsuccessful pppLastNCPToAtcp Unsuccessful pppLastNCPToCcp Unsuccessful PppLastNCPToMp Unsuccessful The NCP protocol (IPCP) failed due to protocol timeout, and all other NCP protocols failed before IPCP or were not negotiated at all.
  • Page 78 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason Success Indication Explanation pppInitFailed pppUnknownCode pppDialback pppAddrInuse pppNoDevice pppModSigHangup pppSigHangup pppSigTerm 300115-B Rev. A Indeterminate PPP not configured properly. Indeterminate Code not defined for call management. Graceful Call Disconnect for purpose of dialback.
  • Page 79 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason Success Indication Explanation pppSigKill Indeterminate pppSigTime Forced pppNoMem Unsuccessful pppConnAbort Indeterminate pppVpnLcpFail Unsuccessful pppVpnAuthFail Unsuccessful Caused by an emergency abort within the system. Caused by an inactivity timer (ppp inactivity, or port inactivity) which caused the link...
  • Page 80 Remote Access Software Version 5.3 Release Notes Table 12 Disconnect Reason Descriptions (Continued) Disconnect Reason pppMpBadPortCfg pppInvOpDevType mmpBunDiscFail dvsRegFail dvsHaDereg dvsTnlNoRenew dvsTnlExpire l2tpCallFail l2tpCallDiscNotify 300115-B Rev. A Success Indication Explanation Unsuccessful A port or channel was incorrectly configured for MP link processing. Unsuccessful Operation attempted for PPP link was invalid...

  • Page 81: Remote Access Software Release 5.1 Corrections

    Remote Access Software Version 5.3 Release Notes Remote Access Software Release 5.1 Corrections SPR 10952 The calling number is included now in erpcd proxy RADIUS accounting messages. SPR 10229 erpcd RADIUS class attributes now work with the Bay Networks Secure Access Control (BSAC) address pool.

  • Page 82: Spr 9950

    Remote Access Software Version 5.3 Release Notes SPR 9950 CCP BSD Compress now complies with RFC 1977. SPR 9955 Handling of V.120 for dialback has been added. SPR 8739 Port server connections show the username instead of “---” when the who command is executed.

  • Page 83: Spr 10137

    Remote Access Software Version 5.3 Release Notes SPR 10137 The default port mode on all PRI products has changed from cli to auto_adapt. SPR 10255 RIP updates should no longer stop on PPP interfaces. SPR 9540 Annex printing no longer causes the Annex to panic. SPR 10434 The reset annex all command now correctly updates modem type definitions in Annex memory, depending on the new list of session...

  • Page 84: Spr 10483

    Remote Access Software Version 5.3 Release Notes SPR 10483 The answer_delay keyword is available for SPBs. This keyword takes a single decimal argument in seconds. The keyword specifies the delay for answering the call to putting the modem or other resource (sync, TA) on the channel.

  • Page 85: Changes To Unix Clis Release 14.1

    Changes to UNIX CLIs Release 14.1 This section describes changes to the UNIX command line interfaces for Release 14.1 of the Remote Annex/RAC operational code. Known Problems/Limitations Remote Access Software Version 5.3 Release Notes • If you are using acp logging, you need to be certain that you have sufficient disk space available for log messages.
  • Page 86 • The ISDN TAs listed below are known to have compatibility problems running Mulitlink PPP with the RA 6300, RA5393, 5399 RAC, and 8000 RAC models. However, running single- link PPP with these TAs on those models is supported: •...
  • Page 87 CLI session, always close the session (hang-up) and return to the Console monitor before rebooting or resetting the 5399 RAC. Otherwise, it is possible to get the RAC Console monitor into an inaccessible state, which will then require the unit to be physically removed/reinserted in the 5000 hub.
  • Page 88 Remote Access Software Version 5.3 Release Notes remote_address: ipx_network:* ipx_node:* 300115-B Rev. A • IPX dialup addressing is completely rearranged when address_origin is set to local and the addresses are to be selected from the WAN; the remote addresses are set to 0.0.0.0.

  • Page 89: Spr 10025

    Remote Access Software Version 5.3 Release Notes SPR 10025 The UNIX installation can install the host tool sources on nonsupported UNIX platforms. SPR 10269, 10270, 10271 Deficiencies in the help for the admin CLI. SPR 10610 You must specify wan=1 for the CLI admin command you are using, even if the RAC contains only a single WAN interface.

  • Page 90: Spr 10653

    Remote Access Software Version 5.3 Release Notes SPR 10653 You cannot expire old passwords and enter new passwords using the Windows NT erpcd server. SPR 10585 The Windows NT install shield appears to hang during server tool installation. Please be patient; it will complete the installation. SPR 10037 The RA 6300 and RA 5393 support the actcall/histcall CLI commands, but not all modem information is available with those commands.

  • Page 91: Changes To Annex Manager Release 3.1

    Changes to Annex Manager Release 3.1 System Requirements Annex Manager Release 3.1 runs on several popular UNIX systems. The following sections list the hardware and software requirements for installing and running Annex Manager. For all systems, a minimum of 10MB of free disk space must be available prior to installation.

  • Page 92: Ibm Requirements

    New Features and Commands Annex Manager Release 3.1 supports the model 5399 and model 8000 RACs. For more information on the new RAC product features and commands, please see other sections of these release notes and the revised Annex Manager User’s Guide included with your documentation.

  • Page 93: Changes To Quick2Config Annex Release 3.1

    TCP/IP stacks included with Windows NT and Windows 95 • If you select a T1-supporting unit (RA 6100, RA 5391, 5399 RAC, or 8000 RAC) in the tree, then select the WAN Interface tab, you should ignore the resulting error message: <annex name>...

  • Page 94: Corrections To Quick2Config Annex Release 3.1

    This happens rarely and randomly, and only if the device is unreachable and is in an unknown state. • In the WAN interface tab, switch types are not dimmed by module type. For example, even though the WAN is running a channelized T1 protocol, the E1 switch types (Korea, China, Brazil, etc.) are still available.

  • Page 95: Spr 9155

    SPR 9155 You can use Quick2Config Annex to set all valid combinations of PPP interface protocols. Changes to the Network Administrator Utility (na) for Windows NT and Windows 95 Hardware/Software Requirements You must use the following hardware and operating system version to use the na utility on Windows NT or Windows 95: Special Considerations The na utility no longer requires that you have administrator privileges...

  • Page 96: Changes To Remote Annex Server Tools For Windows Nt R3.1

    Remote Access Software Version 5.3 Release Notes Changes to Remote Annex Server Tools for Windows NT R3.1 System Requirements You will need the following to install and run Remote Annex Server Tools for Windows NT Release 3.1: Installing Windows NT Server Tools The installation instructions for Windows NT Server Tools state that you must run the setup.exe file for both Windows NT 3.51 and 4.0.
  • Page 97 Remote Access Software Version 5.3 Release Notes Go to the Control Panel > Services and stop Annex erpcd, Annex syslogd, and Annex timed. Start the registry editor: a) For Windows NT 3.51, you can find the registry in \windows_install_dir\system32\regedt32.exe. Remove the following keys: HKEY_LOCAL_MACHINE (on the local machine) SOFTWARE...
  • Page 98 Remote Access Software Version 5.3 Release Notes 300115-B Rev. A HKEY_LOCAL_MACHINE (on the local machine) SOFTWARE PROGRAM GROUPS Bay Networks (To avoid removing Q2CAnnex or NA icons, go to the group and delete the icons for the Remote Annex Server Tools for Windows NT) b) For WIndows NT 4.0, you can find the registry file in \windows_install_dir\regedt.exe.

  • Page 99: Known Problems/Limitations

    Remote Access Software Version 5.3 Release Notes Go to Settings > Taskbar > Start Menu Programs > Advanced and delete the Bay Networks Remote Annex programs. Go to the File Manager or Explorer and delete the following files/ directories: Delete the installation directory c:WIN32APP\BayNet\RAnnex and its files.
  • Page 100 Remote Access Software Version 5.3 Release Notes 300115-B Rev. A • Remote Annex Server Tools for Windows NT do not support the following UNIX utilities: • aprint - the Remote Annex printer utility • ch_passwd - the Remote Annex user password change utility •...

  • Page 101: 24-Hour Unit Replacement Service

    24-Hour Unit Replacement Service This service is named “Next Day With Labor - BJ 2300.” You must follow the procedures in this section in order for the Next Day With Labor Service Agreement to be honored. Saving the RAC Configuration When you have finished configuring your RAC, Bay Networks recommends that you save your configuration to a host file.
  • Page 102 Remote Access Software Version 5.3 Release Notes To save a RAC’s configuration: The following is a typical login procedure prompting you for a password (on Windows NT, only the first line is different): # /usr/annex/na command: Annex 192.32.30.49 Password for 192.32.30.49 <unknown>: abc 192.32.30.49: Micro-Annex-UX R11.1, 8 async ports command: write 192.32.30.49 annex.param command: quit...
  • Page 103 Remote Access Software Version 5.3 Release Notes # Annex 192.32.30.49 echo setting Annex parameters set annex subnet_mask 255.255.255.0 set annex pref_load_addr 192.32.30.30 set annex pref_dump_addr 192.32.30.30 set annex load_broadcast N set annex broadcast_addr 192.32.30.255 set annex load_dump_gateway 0.0.0.0 set annex load_dump_sequence net,self set annex image_name "oper.56.enet "...

  • Page 104: Restoring The Rac Configuration

    Remote Access Software Version 5.3 Release Notes You may want to create a backup directory elsewhere and copy this file into that directory. This ensures that there is no chance of the file being corrupted or otherwise changed when you upgrade the unit. Restoring the RAC Configuration This process is necessary for restoring a configuration to a RAC.
  • Page 105 Remote Access Software Version 5.3 Release Notes To restore a RAC’s configuration: At the command prompt, enter the following: command: annex <IP address*> This identifies which RAC you want for subsequent commands. (For UNIX) command: read (For Windows NT) command: read This copies the filename.param file to the RAC that you specified and changes the parameters to ones specified in the file.
  • Page 106 Remote Access Software Version 5.3 Release Notes command: read annex.param setting annex parameters setting parameters for async port 1 setting parameters for async port 2 setting parameters for async port 3 setting parameters for async port 4 setting parameters for async port 5 setting parameters for async port 6 setting parameters for async port 7 setting parameters for async port 8...
  • Page 107 Remote Access Software Version 5.3 Release Notes To assign an IP address to a RAC: Insert the RJ45 connector in the console port of the RAC. Set your terminal to the following settings: 9600 baud, 8 data, 1 stop, no parity, and XON/XOFF. Insert the other end of the RJ45 connector into the console adapter and connect the console adapter to your laptop.
  • Page 108 Remote Access Software Version 5.3 Release Notes 300115-B Rev. A...

This manual is also suitable for:

200053905391539361006300 ... Show all

Table of Contents