(ASCEND) 7.2.4 for TNT

[Matt Holdrege <holdrege@lucent.com>]

MAX TNT TAOS 7.2.4 software has been given to support. It contains the
following:

Corrections in MAX TNT TAOS 7.2.4
*Nailed PPP connections failed after a cable was pulled out and plugged
back in.
*NVRAM default values were out of range.
*Ambiguity in interpretation of NAS port configuration format.
*Unchannelized T1 port LAN session failed to come back up after a T1 line
was reset.
*The SNMP ifOperStatus attribute was inaccurate when used on the T3 card.
*Calls failed to come up after IP pools were changed.
*MAX TNT stopped negotiating ATCP after a short period of time.
*Synchronous users failed to connect with 'Cant Open 1 HDLC Channel'
message.
*The MAX TNT intermittently failed to send expected E1 R2 signaling to the
central office (CO).
*The MAX TNT was not releasing Series56 digital modems from the inuse state.
*Connections with duplicate interface addresses failed.
*CSM3V modem cards failed the SAR external loopback test.
*Missing Framed-IP-Netmask attribute caused users to fail IPCP.
*Authentication and accounting packets were sent to destination port 0.
*V.42bis compression for PIAFS was disabled.
*Changing a PRI line from NT to TE caused an FE20.
*Noncompliance with RFC 2138 caused problems with MAX TNT authentication.
*CLID callback accepted a call unless Clid-Auth-Mode parameter was set to
Required.
*ATMP Foreign Agent discarded packets that were between 1441 and 1445 bytes.
*L2TP and AAC authentication failed when a single RADIUS server was used.
*ATMP Foreign Agent and Home Agent unable communicate with a tunnel number
greater than 65535.
*When NAT and callback with CLID were used, the IP route table was not
updated.
*The Ethernet interface had to be disabled and then reenabled for Route
filters to take effect.
*Large numbers of RADIUS filters sent to the MAX TNT caused authentication
failures.
*Users were able to ping a MAX TNT from the terminal server even after the
operation had been disallowed.
*SNMP queries returned corrupted community strings.
*The Series56 Digital modem card crashed with an FE36 when the terminal
server was enabled.
*Filters assigned through RADIUS did not work with DNIS authentication.
*Direct routes were not placed in the routing table.
*E1 R2 DNIS was truncated when CLID was requested.
*MP and MP+ channels were stuck in a connected state with DASS-2 switch
type.
*The MAX TNT used the input filter from first MP+ channel on subsequent
channels.
*A DSLTNT configured as a LAC reported inaccurately for L2TP accounting
packets.
*Upon reboot of the MAX TNT, dial-in subnets were not advertised via OSPF.
*Corrupt connection profiles did not save written parameters.
*NVRAM corruption during downgrading.
*Inclusion of an Ethernet MAC header resulted in ATMP packet size
miscalculation.
*The MAX TNT responded to RIP request even when RIP was disabled.
*Memory leaked when a firewall static element pool was defined.
*RADIUS accounting records trailed with 0x00 when accounting
Acct-Session-Id was set to vendor-specific.
*Ethernet 4/1 card reset under heavy load with FE8.
*After a modem failed CLID authentication using RADIUS, it was moved to the
suspect list.
The MAX TNT failed to recognize DPNSS CLI SIS ID 50.
*show dhcp address command looped when an static address preceded a group.
*Deleting a T1 profile sometimes caused an FE40.
*Poor performance with Windows 9.x over ISDN Terminal Adapters on HDLC2.
*The line quality fluctuated while using the 8Khz external clock.
*The MAX TNT sent a noncompliant state attribute length of 2 bytes.
*Problems occurred during installation of an E1 slot card in a DSLTNT.
*Multicast forwarding failed after a group member was removed.
*Problem occurred with the latest Series56III Digital Modem firmware
(5.8174) from Conexant.
*Hardware revision number can be a number as well as a letter.
*An incorrect message was displayed when the MAX TNT was reset.
*SNMP clarification for the sysConfigTftp parameter.
*Rlogin users were routed to the terminal server when Rlogin was disabled
on the MAX TNT.
*Chinese E1 R2 CLID category (KA) was not stripped from the response.
Conexant firmware versions:

The Conexant firmware versions for MAX TNT Digital Modem modules include
support for
V.90, K56flex, K56plus, and all slower, standard modem speeds.
This release includes the following Conexant firmware:
*V.34 Digital Modem modules support V1.610G24-V34_DP firmware.
*Series56(TM) Digital Modem modules (also called CSM/1, Model Number
TNT-SL-48MOD-S56) support V2.098-K56_2M_DLP_CSM firmware.
*Series56 II Digital Modem modules (also called CSM/3, Model Numbers
TNT-SL-48MOD-SGL and TNT-SL-48MOD-S-C) support V5.817 firmware.
*Series56 III Digital Modem modules (also called CSM/3V, Model Number
TNT-SL-48MODV3-S-C) support V5.817 firmware.

Known Issues:
*In TAOS releases earlier than 7.2, the format of call logging packets is
identical to the format of RADIUS Accounting packets. Starting with TAOS
7.2, however, call logging is no longer compatible with RADIUS, although
the NavisAccess? product fully supports call logging. The MAX TNTŪ
continues to support RADIUS accounting, Simple Network Management Protocol
(SNMP), and Syslog functionality.
*Because of the proprietary nature of and potential modification to call
logging packets, you do not use call logging packets with any application
other than Lucent?s NavisAccess.
*Before changing the virtual path identifier-virtual channel identifier
(VPI-VCI) range of an Asynchronous Transfer Mode (ATM) connection on an ATM
OC3/STM-1 card, you must disable the ATM connection.
*Use of this release is not recommended with Rev. B or lower of the
Ethernet-2 card (TNT-SL-E10-100, part number 0800-0433-001). If you have a
Rev. B or lower Ethernet-2 card, contact your Lucent representative to
obtain an upgrade to Rev. C or higher. The Rev. B or lower cards continue
to work with releases earlier than TAOS 7.0.0.
*Multilink Point-to-Point Protocol (MP) bonding of analog calls is
supported in this release, but some client modems and software might have
compatibility problems.
*Configurable receive and transmit data rate limits are not supported on
the DS3-ATM card. They are supported on the SDSL and unchannelized DS3 cards.
*If you replace an older Ethernet card with the new Ethernet-2 card, you
must write new Ethernet profiles for the new card. The old Ethernet
profiles do not carry forward. You must also write new profiles when you
replace an HA192 card with an HDLC2 card, or a Series56? I modem card with
either a Series56 II modem card or Series56 III card. For any card slot
where the card type is being changed, you must issue a slot -r command
after downing (slot -d) or removing the existing card and before inserting
a new card type.
*Connection profiles for Ascend Tunnel Management Protocol(ATMP) mobile
clients ignore the Shared-Profile setting. Shared-Profile is implicitly set
to Yes for all ATMP mobile client Connection profiles.
*LAN-Modem profiles contain entries for 96 devices. For 48-port modem
cards, only the first 48 entries are used.

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