Release Notes PN 93000352 (SPARC) / 93000353 (Intel) Digi International RAS Driver for Solaris Version C Solaris 2.7 and 2.8 Software Package PN 40002060 (SPARC) / PN 40002061 (Intel) Software Manual PN 92000363 November 10, 2000 CONTENTS 1. Introduction 2. Supported Products 3. Enhancements 4. Bug Fixes 5. Known Limitations 6. Notes: Device Nodes 7. Notes: Utilities 8. Notes: Features for DataFire RAS PT Adapters 9. Notes: Setting Lesser-Used and Arbitrary Baudrates 10. Notes: Features for AccelePort Xp Adapters 11. History 1. INTRODUCTION This device driver software provides support for up to 32 Digi RAS PCI adapters on the Solaris operating system. 2. SUPPORTED PRODUCTS AccelePort 2p, 4p, 8p, 16p DataFire RAS 24 PT1 DataFire RAS 48 PT2 AccelePort RAS A4 AccelePort RAS A8 3. ENHANCEMENTS Changes since B: -- Upgraded the AccelePort RAS and DataFire RAS firmware from version K2 to version K3 Changed since A: -- Upgraded the AccelePort RAS and DataFire RAS firmware from version J3 to version K2 -- Added new device names. The device names have the form "/dev/dgrasXXXs" and are meant to be used in place of the devices with the form /dev/DIGIras/bXXpXXs. The "/dev/DIGIras/bXXpXXs" device names will continue to exist. This is described in more detail below. -- Modified the /dev/term and /dev/cua device links to be in the form "/dev/term/dgrasXXX" and "/dev/cua/dgrasXXX". This change was made so the /dev/term and /dev/cua links could be based on a unique name rather than a cryptic sequential number. -- Added the dm_gui utility to the package. dm_gui is a X windows graphical application that can be used to monitor and configure adapters. -- Added simple utility called digiras_info. This utility gives information on device names. -- Added support for clone management devices. This allows a utility such as dm_gui to be opened multiple times. Changed since 3P: -- The behavior of the "cspeed" flag to ditty has been made friendly. Its use is described below. -- Upgraded the AccelePort Xp firmware from version 4P to version A1. -- Upgraded the AccelePort RAS and DataFire RAS firmware from version K2P to version J3. Changed since 2P: -- Upgraded the AccelePort Xp firmware from version 3P to version 4P. -- Upgraded the AccelePort RAS and DataFire RAS firmware from version K1P to version K2P. Changed since 1P: -- Improved the reporting of OS and driver versions via PortAssist Manager (PAM). -- Upgraded the AccelePort Xp firmware from version 1P to version 3P. -- Upgraded the AccelePort RAS and DataFire RAS firmware from version J1 to version K1P. -- Added a line to /etc/rc2.d/S90DIGIras which can be uncommented to enable the launching of the PAM Communications Agent upon boot. 4. BUG FIXES Changed since B: -- Upgraded the AccelePort RAS and DataFire RAS firmware from version K2 to version K3. This has fixed the following bugs: -With the AccelePort RAS adapter, RING would go away after opening a port for a second time. This bug is fixed with the K3 firmware. -With the DataFire RAS adapter, an unusual frame caused a panic in the firmware. This bug is fixed with the K3 firmware. -With the DataFire RAS adapter, some linecode violations were occuring. This bug is fixed with the K3 firmware. Changed since A: -- Modified the CLOCAL behavior. CLOCAL no longer can be used to ignore carrier on an open. If you want this behavior use the cu type devices (e.g. /dev/cua/dgrasa01) or use ditty to make a port assert carrier on open (e.g. ditty forcedcd /dev/term/dgrasa01). Note CLOCAL still ignores carrier, it just can not be used to ignore carrier on open. -- Fixed a very unlikely race condition that might have occured during a hangup and close. -- Fixed a bug in dpa where the "SET_SERIAL_STATUS FAILED" messge would get displayed when scrolling through the ports. Changed since 1P: -- Fixed the bug that would cause a kernel panic if DPA were used to inspect the ports on an adapter on which no ports had yet been opened. 5. KNOWN LIMITATIONS Only analog calls are supported. 6. NOTES: DEVICE NODES Device nodes can be found in "/dev", "/dev/DIGIras", "/dev/term", and "/dev/cua". The device nodes found in "/dev" have the form dgrasLNNs and dgrasLNNm. L is a letter and is used to identify the board. Each board is assigned a letter based on the board's instance number. So instance 0 gets 'a', instance 1 gets 'b', and so on. NN is a two digit base-10 number identifying the port. Devices ending with the letter "m" ("modem-control") block on DCD on open; those ending in "s" do not. The former are sometimes called dial-in nodes; the latter dial-out nodes. Links to these device nodes can be found in /dev/term ("m" nodes) and /dev/cua ("s") nodes. Additionally, transparent-print device nodes are provided for ports on AccelePort Xp adapters. These are of the form /dev/dgrasLNNlp. The utilitiy "digiras_info" can be used to quickly determine what device name is used for a particular board. You must be super-user to run this utility. The device nodes found in "/dev/DIGIras" have the form bMMpNNm and bMMpNNs. These devices are provided to maintain compatibility with the way devices were originally named in this driver. MM is a two digit base-10 number and is used to identify the board. Each board is assigned a number based on the board's instance number. So instance 0 gets '00', instance 1 gets '01', and so on. NN is a two digit base-10 number identifying the port. Devices ending with the letter "m" ("modem-control") block on DCD during open; those ending in "s" do not. The former are sometimes called dial-in nodes; the latter dial-out nodes. Additionally, transparent-print device nodes are provided for ports on AccelePort Xp adapters. These are of the form /dev/DIGIras/bMMpNNlp. The names and locations of these devices can be customized to some extent. See the DIGIras.1 man page for details. 7. NOTES: UTILITIES The following utilities can be found in /opt/DIGIras/bin. There are links to most of these utilities in the /usr/sbin directory. Many of these utilities support man pages. ditty - a stty(1)-like program which gives easy command-line access to a number of the extended-functionality features of your Digi DataFire and AccelePort adapters. dm_gui - a graphical application that can be used to monitor and configure your adapter. dm_admin - a command-line utility which can be used to configure and gather info about your adapter. ras_config - this utility has been replaced by dm_admin. It is included for users who are familiar with this utility. Note this utility does not work for the AccelePort Xp line of adapters. dpa - this utility is a curses based application that can be used to view and monitor port information. dm_trace - this utility can be used to do data traces for the DataFire and AccelePort RAS adapters. Note this utility does not work for the AccelePort Xp line of adapters. digiras_info - a command-line utility that prints the device name that is used with each adapter. pamagent - this is an internet based monitoring utility that can be used in conjunction with Digi's PortAssist Manager. The PortAssist Manager application is supported on various Microsoft Windows and Unix platforms. PortAssist Manager is not included with this package. PortAssist Manager can be found on the installation disk that came with the adapter or it can be found at Digi's internet site located at support.digi.com/support/utilities. ras_reset - this is a utility that is used to hangup and/or reset modems. This utility works with the DataFire and AccelePort RAS adapters. Type "./ras_reset -h" to display the list of options. 8. NOTES: FEATURES FOR DataFire RAS PT ADAPTERS Support for DataFire RAS PT1 and PT2 adapters. Support for ANI/DNIS information via AT command #CID=10 Support for NFAS protocol via ras_config. Partial Support for Solaris Sync API protocol via framing AT command set and S_IOCSETMODE ioctl. Port configuration utility /opt/DIGIras/bin/ras_config: ras_config -? for usage statement /dev/DIGIras/mgmtX opens a control path to adapter instance X Can see the current switch settings in NVRAM with ras_config -b 0 -k 0x21 -p 1 ras_config -b 0 -k 0x21 -p 2 Can see the current D Channel settings in NVRAM with ras_config -b 0 -k 0xa1 -p 1 ras_config -b 0 -k 0xa1 -p 2 Can set current switch settings in NVRAM in AT&T 5ess mode (ESF, B8ZS, PRI (5E), Loop Clock, LeasedMask = 0, Long Haul, 0db) with ras_config -b 0 \ -k0x9021 -p1 -f0x1 -l0x1 -s34 -t0x1 -M0 -i0x1 -Q1 -P0 -I0 Note that the -P and -I options deal with NFAS master port and interface ID values. Setting them to zero indicates non-NFAS mode. Can set the current D Channel settings in NVRAM with ras_config -b 0 -k 0x90a1 -g 1 -h 1 -H 1 -p 1 ras_config -b 0 -k 0x90a1 -g 1 -h 1 -H 1 -p 2 Can set adapter in port-to-port loopback mode with ras_config -b 0 -k 0x9021 -R 4 -t 2 -i 3 -p 1 ras_config -b 0 -k 0x9021 -R 4 -t 2 -i 3 -p 2 port 0 dials port 1, etc... 9. NOTES: SETTING LESSER-USED AND ARBITRARY BAUDRATES Baudrates may be set in the Solaris-standard way, stty (or from an application via struct termios, tcgetattr(), cfsetospeed() and tcsetattr().) This provides ready access to the following baudrates: 50, 75, 110, 134, 150, 200, 300, 600, 1200, 1800, 2400, 4800, 9600, 19200, 38400, 57600, 76800, 115200, 153600, 230400, 307200 and 460800. Additional baudrates may be attained using the "fastbaud" feature provided by the ditty utility. Fastbaud can be turned on with the command ditty fastbaud and turned off with the command ditty -fastbaud When fastbaud is on, the following mappings are put into effect: baudrate setting -> + fastbaud -> actual baudrate ---------------- --------------- 50 57,600 75 76,800 110 115,200 134 131,657 or arbitrary 150 153,600 200 230,400 300 460,800 600 921,600 All other baudrate settings are unaffected by the setting of fastbaud. The arbitrary baudrate alluded to above may be set using the command ditty cspeed [baudrate] The "cspeed" feature automatically sets fastbaud on *and* sets the baudrate setting to 134. Fastbaud is "sticky," meaning it retains its setting across opens and closes. 10. NOTES: FEATURES FOR AccelePort Xp ADAPTERS Via the /kernel/drv/dgdxb.conf file: -- To turn on reduced-latency (i.e., interrupt-driven) mode, add one or more lines of the form instanceN_use_interrupts=1; where N is replaced by the instance number of the adapter (which is printed at driver-load/boot time). In reduced-latency mode, data received at the port will be delivered to the device node, and hence the application, faster than would otherwise be the case. A side effect of this mode of behavior is elevated CPU usage. The latency/CPU usage tradeoff can be fine-tuned by adding lines of the form instanceN_interrupt_period=X; where N is replaced by the instance number of the adapter, and X is the desired interrupt period in milliseconds. The default interrupt period is 10 milliseconds (1/100 second). -- To turn on ALTPIN behavior (swapping the DCD and DSR modem-control inputs) for all ports on an adapter, add one or more lines of the form instanceN_altpin=1; where N is replaced by the instance number of the adapter. ALTPIN makes DCD available when using an 8-pin RJ-45 connector. ALTPIN on any single port can be set using the ditty utility. 11. HISTORY Version 1P of this driver package was released to Systems Assurance in February 2000 (i386) and March 2000 (SPARC). Version 2P of this driver package was released to Systems Assurance on April 20, 2000. Version 3P of this driver package was released to beta testers on April 27, 2000. Version A of this driver package was released for general availability on July 10, 2000. Version B of this driver package was released for general availability on October 24, 2000. Version C of this driver package was released for general availability on November 10, 2000. Copyright 1999-2000 Digi International