(ASCEND) MAX TNT TAOS 8.0.0 Release

[Matt Holdrege <matt@ascend.com>]

TAOS 8.0.0 software for the MAX TNT has been given to Customer Support and 
Manufacturing. This release contains data and voice support and the following:

New Features

* Series56 III modem card support
* Expanded MultiDSP card support
* Stac compression for asynchronous calls
* Ethernet-3 slot card support
* OC3-ATM slot card support
* HDLC2-EC-C slot card support
* STM-0 slot card support
* Bandwidth Allocation Control Protocol (BACP)
* X.75 frame size increase to 2048 bytes
* Support for multidigit trunk groups
* MAX TNT stacking
* Sharing profiles on a per-user basis
* New settings for CLID-Auth-Mode
* Extensions to DNIS management
* Bidirectional CHAP
* Username available for first-tier DNIS authentication
* NAS-Port-Type specification for local profiles
* RADIUS: Enhanced IETF compliance in VSA compatibility mode
* RADIUS: Tunnel attribute sets with tags and preferences
* RADIUS: Support for MS-CHAP authentication
* RADIUS: Authentication of Telnet sessions
* RADIUS: Inclusion of data and transmit rates in access request
* RADIUS: TCP-Clear-Quiet value added to Login-Service attribute
* RADIUS: Toggle boot requests
* RADIUS: Overriding the Answer-Defaults authentication method
* ISDN callback
* DOS-compatible FAT-16 flash memory format
* Additional onboard memory for extended profiling
* Pattern detection and reporting in the TCP-Clear data stream
* Telnet access control list
* Periodic log message for reporting the software version
* Remote management of other units
* Command for displaying filter information
* Customizable screen width up to 255 characters
* TCP-Clear login host IP address reported
* Coredump generated by specific Warning messages
* Event logging when an operator downs or resets a slot card
* Support for multiple Syslog servers
* Full backup queue type now identified in Syslog
* Grep-like capability added to certain commands
* CLID display option for Userstat command
* Options for displaying the system log
* Option for displaying line status
* Dynamic remote filters
* MaxTap support
* Userstat options to display address and username
* Selectable call-logging server
* Enhanced reporting of HDLC errors
* SNMP: Partial support for ATM MIB RFC 2515
* SNMP: Trap for dropped call-logging packets
* SNMP: Configuration of TFTP port for network management
* SNMP: New Config-Change trap
* SNMP: Trap for console state change now displays IP address
* SNMP: Support for loopback modes in DS1 MIB
* SNMP: Fatal log table
* SNMP: Idle Time variable in the active session table
* SNMP: Variables added from event.mib to call.mib
* SNMP: New MIB variables for summarizing B channel states
* SNMP: Modified method for adding SNMP object IDs
* SNMP: Details on terminating access resources
* SNMP: Limited support for RFC 2574 user-based security model
* OSPF nonbroadcast multiaccess (NBMA) support
* OSPF area border router (ABR) support
* OSPF MD5 16-byte authentication key
* RFC 1850 OSPF traps
* OSPF reconfiguration restart no longer required
* Per-connection Microsoft WINS assignment
* Private routing tables
* Port redirection
* IP pool chaining
* Don't Fragment option added to Ping command
* Commands for monitoring multipath route caching
* Store-and-forward IP fax
* IP fax call accounting
* Redialer support on MultiDSP card for store-and-forward fax
* PHS Internet Access Forum Standard (PIAFS) 2.1 on MultiDSP
* Asynchronous V.110 on MultiDSP
* R2 CLID processing for New Zealand
* R2 CLID processing for Thailand
* R2 CLID processing for Israel
* R2 CLID processing for Mexico
* R2 signaling for Kuwait
* Support for ISDN network-side emulation (T1 and E1)
* ISDN NFAS support for Japanese switch types
* Frame Relay PVCs over switched ISDN connections
* Frame Relay switched virtual circuits (SVCs)
* Multilink Frame Relay (MFR)
* DLCI bundling in MFR
* MFR circuit switching
* Configurable VPI-VCI ranges
* OAM loopback for DS3 ATM PVC fault management
* ATM-direct
* ATM switched virtual circuits (SVCs)
* ATM traffic shaping
* ATM-Frame Relay transparent-mode circuits (FRF.8)
* ATM-Frame Relay virtual channel trunking
* Signaling System 7 (SS7)
* SS7 IPDC support for call ID and disconnect cause codes
* MultiVoice support
* IPDC enhancements for reporting VoIP call statistics
* IPDC message support for T.38 fax and transparent modem
* IPSec for L2TP tunnels and TCP-Clear
* L2TP timer options
* L2TP list attempts
* Multiple endpoints for tunnel sessions (RADIUS only)
* Secondary tunnel server for L2TP and L2F tunnels
* Optional L2TP system name
* Limited support for Layer 2 Forwarding (L2F)
* Virtual router (VRouter) DNS
* VRouter support for L2TP connections
* Short-duration transaction network (SDTN)

NOTE: The MultiDSP Card Product Guide is located in the same FTP site 
directory as the TAOS 8.0.0 MAX TNT Release Notes.

Notice of deprecated management features:
Use of the if-admin diagnostic command is deprecated. The functionality 
that was provided by the -d (down) and -u (up) options of the command is 
now provided by read, set, and write operations on one of the following 
profiles:
* The Admin-State-Perm-If profile for permanent interfaces such as a nailed 
interface
* The Admin-State-Phys-If profile for physical interfaces such as a T1 line

The other options of the if-admin command are not supported.
Use of the call-log-radius-compat parameter in the Call-Logging profile is 
deprecated in this software version.

The callActiveIfIndex and callStatusIfIndex objects in the call MIB are not 
supported in this software version. The following objects are supported in 
this software version, but will not be supported in future software versions:
* The lmodem.mib
* The resetStat group in ascend.mib
* The consoleTable, doTable, and hostStatusTable in ascend.mib


Corrections:

* TR 1612 Log window displayed extra lines for Windows95 Telnet sessions 
when the user pressed the up-arrow key to scroll through the log status.
* TR 2180 Cutting and pasting the argument to the Open command resulted in 
a double carriage return, which caused the system to generate an "Error 
from far end" message.
* TR 2490 The Quit command was included as the last entry in a 
configuration file saved either by using the Save command in the CLI or 
from an SNMP management station.
* TR 2255 In releases prior to 7.0.3, multishelf systems maintained 
multiple dates and times. Now, the slave systems are synchronized with the 
master shelf clock whenever a slave comes up, a user changes the Timedate 
profile on the master shelf, or the master receives SNTP updates.
* TR 3003 In previous releases, administrators could not log into a user's 
unit for configuration purposes. This has been fixed.
* TR 3045 SNMP: ifAdminStatus returned Up for a disabled T1 interface.
* TR 3207 When Pool-Summary is enabled and the IP address pools are defined 
in the IP-Global profile, the MAX TNT did not add summary routes to the 
routing table, so the routes were not advertised in RIP updates.
* TR 3553 The MAX TNT incorrectly forwarded broadcast packets received from 
a WAN link to the shelf's Ethernet network.
* TR 3626 When using TFTP to load or save a large number of profiles, the 
TFTP operation could sometimes time out and abort.
* TR 3739 When using TFTP to load or save a large number of profiles, the 
TFTP operation could sometimes time out and abort.
* TR 3746 System did not use multipath routing to load balance between 
interfaces.
* TR 3976 When a power supply failed or was unplugged, the MAX TNT 
generated a power supply state change trap (Ascend enterprise trap 24 ), 
but did not generate the trap when power was restored.
* TR 4003 MAX TNT units did not reestablish a nailed connection correctly 
after it had been dropped.
* TR 4043 The MAX TNT unit stopped taking fax calls after 16 hours, 
generating Warning messages 179 and 154 in Diagnostic mode.
* TR 4148 MAX TNT unit sent RIP packets with a Time To Live (TTL) value of 
64 instead of a value of 1.
* TR 4179 MAX TNT unit did not propagate changes to a filter applied to an 
Ethernet interface to the interface when the Filter profile was written.
* TR 4189 The NAS-Port attribute-value pair was missing in Accounting 
records for calls received on shelf 1, slot 1, port 5, channel 1.
* TR 4268 MAX TNT RADIUS Statistics were not aggregated for all host slot 
cards
* TR 4270 Occasionally, the MAX TNT reported progress code 65 (LCP_OPENED) 
instead of progress code 60 (LAN_SESS_UP) when an NCP connection was 
established during a PPP dial-in.
* TR 4284 MAX TNT unit stopped accepting new calls and sent busy signals.
* TR 4294 MAX TNT units supporting LAN modems did not send ASCEND_CD ON/OFF 
notifications to notify remote clients of carrier detect changes.
* TR 4341 Occasionally, a MAX TNT supporting Series56 II modem cards could 
reset, generating a Fatal Error 1 in Diagnostic mode.
* TR 4357 MAX TNT units supporting LAN modems did not send ASCEND_CD ON/OFF 
notifications to notify remote clients of carrier detect changes.
* TR 4358 The MAX TNT did not generate power supply traps following a 
system reset unless you set the powerSupplyStateTrapState and 
powerSupplyOperationalStateTrapState variables in the power supply MIB 
(ps.mib) to Enabled(1).
* TR 4464 Occasionally, data reported by the frdump and frMgrdump 
debug-level commands was lost.
* TR 4558 During OSPF initialization, link-state database exchange with 
Wellfleet routers would fail, because the unicast packets transmitted by 
the MAX TNT had IP TTL set to 0. Could not bring up OSPF between MAX TNT 
and Wellfleet router.
* TR 4595 CLID was not passed across the PRI trunk for net-to-net calls.
* TR 4639 When IPDC protocol was used for SS7 signaling between the MAX TNT 
and a Softswitch and the Softswitch sent RCR message on a channel that was 
idle, the MAX TNT responded with MRJ (message reject) instead of the 
expected ACR.
* TR 4668 Frame Relay profile values were not case-sensitive.
* TR 4670 Outbound modem sessions were not sending the username in the 
RADIUS Accounting Start record.
* TR 4708 Invalid names appeared when xDSL profiles were deleted and 
recreated.
* TR 4770 When using TFTP to load or save a large number of profiles, the 
TFTP operation could sometimes time out and abort.
* TR 4792 After upgrading IPDC server software, the Control Server 
repeatedly sent a specific sequence of IPDC messages which caused DDL to 
corrupt its layer 2 transmission window.
* TR 4858 When the MAX TNT was set to MAX-compatible Syslog mode, the 
Incoming Call, Call Connected, and Call Disconnected Syslog records 
referenced the incoming line's shelf, slot and port values rather than the 
modem or controller shelf, slot and port as it should for MAX compatibility.
* TR 4896 PPP call failed on MAX TNT units, generating Warning 179 messages 
in Diagnostic mode, when configured with Auth-Frm-Addr-Start set to yes.
* TR 4922 The MAX TNT EchoSuppressToneDisable parameter disabled the tone 
for all calls.
* TR 4946 Analog calls connected to terminal server with digital NAS Port 
Type.
* TR 4966 The MAX TNT did not report the RADIUS Accounting NAS-Port 
attribute as documented.
* TR 4967 Variables were missing for L2TP/ATMP/PPTP in the Ascend MIB.
* TR 5113 TDM path was not established correctly for Net-to-Net calls.
* TR 5221 The MAX TNT unit incorrectly detected CLID authentication 
failures because it sent Calling-Station-Id with the incorrect size in 
RADIUS Access-Request packets
* TR 5308 The MAX TNT unit terminated a call during logon sequence after 
receiving a Control-C command.
* TR 5482 After a few weeks, synchronous users could not connect 
successfully into the MAX TNT unit. Diagnostic mode displayed the message 
CANT OPEN 1 HDLC CHANNEL.
* TR 5539 MAX TNT unit sent RADIUS authentication and accounting packets 
from source port 0 to destination port 0.
* TR 5626 The SNMP object ssnActiveIdleTime was not supported.
* TR 5674 Occasionally, when a Lucent Winmodem connected to a CSM3V modem, 
it failed to train at speeds lower than V.90, causing the modems to 
continue to train until timeout.
* TR 1000033 MAX TNT units sent RADIUS authentication and accounting 
packets from source port 0 to destination port 0
* TR 1000235 MAX TNT units supporting E1/R2 did not send blocking towards 
switch when DSP resources were unavailable.
* TR 1000236 MAX TNT units did not support R2 blocking for all R2 types.
* TR 1000268 The Series56 III slot card reset, generating a Warning 106 in 
Diagnostic mode.
* TR 250094 Some RADIUS accounting records showed zero packet and byte counts.
* TR 250283 Using different trunk numbers for each BRI channel does not work
* TR 258625 The MAX TNT unit did not send SNMP Accounting Event messages 
correctly.
* TR 258669 If you set the Shared-Profile parameter in the IP-Global 
profile to No, the system always rejected an attempt to share a user 
profile, even if the RADIUS user profile specified 
Ascend-Shared-Profile-Enable=Yes.
* TR 258671 If you set the Shared-Profile parameter in the IP-Global 
profile to No, the system always rejected an attempt to share a user 
profile, even if the RADIUS user profile specified 
Ascend-Shared-Profile-Enable=Yes.
* TR 258749 Inverse ARP was not recognized as a valid protocol on the 
DS3-ATM card.
* TR 258791 When the MAX TNT was configured as both ATMP Home Agent and 
Foreign Agent, and the home network was unreachable, the Foreign Agent did 
not build a tunnel to the secondary Home Agent.
* TR 258800 If an incoming call was received while a modem was dropping a 
previous call, some of the modems occasionally stopped answering calls.
* TR 258821 After several days, ATMP Gateway Home Agents stopped accepting 
tunnel requests from Foreign Agents.
* TR 258826 Although several tunnels might be active, the Home Agent (in 
router mode) displayed only the latest tunnel when browsing the ATMP MIB 
Tunnel Table
* TR 258864 With the MAX TNT configured for Net5 ISDN signalling (framing 
2DS) and configured for SNMP, when the MAX TNT unit's D channel failed and 
recovered from the failure (the line goes to TE) the unit did not send a 
link up TRAP
* TR 258929 When supporting MultiVoice, an ingress MAX TNT unit sent the 
ALERTING message before the egress unit received it
* TR 1000079 When an E1 line was incorrectly configured to support 
Australia PRI (when a Net5 PRI should have been configured), the MAX TNT 
unit reset, generating a Fatal Error 8 in Diagnostic mode.
* TR 1000103 When a client used the Finger command to query a MAX TNT, the 
connection was refused.
* TR 1000135 Blocking needed for NZ IHUG when channels are disabled.
* TR 1000192 Systems configured for E1 R2 signaling in China did not pass 
the correct CLID number or remove the group-II tone.
* TR 1000235 MAX TNT did not send blocking messages to the switch when DSP 
resources became unavailable
* TR 1000236 MAX TNT did not send blocking messages to the switch when DSP 
resources became unavailable
Conexant (formerly Rockwell) firmware versions:
* Series56 Digital Modem cards (also called CSM/1, TNT-SL-48MOD-S56) 
support V2.0982-K56_2M_DLP_CSM firmware.
* Series56 II Digital Modem cards (also called CSM/3, TNT-SL-48MOD-SGL and 
TNT-SL-48MOD-S-C) support V5.817 firmware.
* Series56 III Digital Modem cards (also called CSM/3V, TNT-SL-48MODV3-S-C) 
support V5.8173 firmware.
The V5.817 and V5.8173 firmware include a fix for synchronization rate 
failures with some PCtel chipset modems. The V5.8173 firmware also provides 
a fix for synchronization failures observed with some Lucent winmodems.
Firmware versions for MultiDSP cards:
* 48-port MultiDSP cards (TNTP-SL-ADI-C or TNTV-SL-ADI-C) support Lucent 
V1.16.14 firmware.
* 96-port MultiDSP cards (APX8-SL-96DSP) support Lucent V1.16.14 firmware.

Known Issues:

* Notice of modified RADIUS port and ID space defaults. The default 
settings for User Datagram Protocol (UDP) source ports and ID spaces for 
communication with a RADIUS server have been changed from single to 
multiple. This modification could cause authentication failures with RADIUS 
servers that do not support distinct UDP source ports. If your RADIUS 
server does not support authentication requests from multiple source ports, 
you must reset the modified parameters to their previous values.

* Notice of modified behavior during IPCP negotiation. In previous 
releases, the MAX TNT unit's system address was used during IP Control 
Protocol (IPCP) negotiation. In previous releases, if the System-IP-Addr 
parameter was null, the shelf controller IP address was used. With MAX TNT 
TAOS 8.0.0, the MAX TNT unit requires a valid System-IP-Addr setting to 
complete IPCP negotiation.

* Before changing an ATM connection's VPI-VCI assignment, you must disable 
the connection on a MAX TNT OC3 (Copper) ATM slot card (TNT-SL-OC3-C) or 
MAX TNT OC3 (Fibre) ATM slot card (TNT-SL-OC3-F).

* Multilink Protocol (MP) bonding of analog calls is supported, but some 
client modems and software may have compatibility problems.

* Configurable receive and transmit data rate limits are not supported on 
the MAX TNT unchannelized DS3-ATM slot card (TNT-SL-UDS3A). Configurable 
receive and transmit data rate limits are supported on the DS3 Frame slot 
card (TNT-SL-UDS3).

* LAN-Modem profiles contain entries for 96 devices. For the 96-port 
MultiDSP card, all 96 entries in the profile are used. For 48-port modem 
cards (Series56 modem card (TNT-SL-48MOD-S56), Series56 II 
(TNT-SL-48MOD-S-C), and Series56 III (TNT-SL-48MODV3-S-C) cards), only the 
first 48 entries are used. For the 48-port MultiDSP card (TNTP-SL-ADI-C or 
TNTV-SL-ADI-C), every other entry in a LAN-Modem profile is used (odd ports 
only, from 1 to 95).
Notice of discontinuance:

* Software support has been discontinued for the MAX TNT Ethernet-0 slot 
card (TNT-SL-E10), the Fast (100 MB) Ethernet-1 slot card (TNT-SL-E100), 
and the older MAX TNT Hybrid Access slot cards (TNT-SL-HA128 and 
TNT-SL-HA192).

* Support for digital subscriber loop (DSL) functionality is discontinued 
in MAX TNT units as of MAX TNT TAOS 8.0.0. The DSLTNT platform continues 
support for existing DSL products and will introduce additional DSL 
functionality in future releases.

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>