Re: (ASCEND) Max TNT 7.0.3

[Matt Holdrege <matt@ascend.com>]

All I've heard about the problem is here on the users list. Is in any
ethernet card, or only the V2 card? I'm on the road now so I don't know if
they are working on your problem or not. Have you contacted support and
received a ticket on the problem?


At 02:44 AM 3/1/99 -0600, William R. Charnock wrote:
>Is there any word on when there might be a fix for the Ethernet card
>problems with the 7.0.3 release?
>
>--
>William Charnock
>CTO, FastLane Internet Services
>(817)-429-5263
>netadmin@fastlane.net
>
>On Tue, 23 Feb 1999, Matt Holdrege wrote:
>
>> MAX TNT TAOS 7.0.3 software has been given to support.  This release
>> contains the following:
>> 
>> 
>> New features in MAX TNT TAOS 7.0.3: 
>> * Configurable VPI/VCI ranges 
>> * Updated ADSL-DMT firmware 
>> * Pattern detection and reporting in TCP-Clear data stream 
>> * Periodic log message for reporting software version 
>> * Don't Fragment option added to Ping command 
>> * New MIB variables for summarizing B channel states 
>> * 64Kbps Personal Handy Phone Service support (Japan only) 
>> * Additional flash segment available for extended profiling 
>> * Remote management of other Ascend units 
>> * Extensions to DNIS management 
>> * Changes in method of adding SNMP object IDs 
>>  
>>  
>> Corrections in MAX TNT TAOS 7.0.3 
>> * TR 3003 Remote command was not available on the MAX TNT. 
>> * TR 3045 SNMP: ifAdminStatus returned Up for a disabled T1 interface. 
>> * TR 3637 Immediate dialout did not work if dialout was defined in a RADIUS
>> profile. 
>> * TR 4048 System not restoring all Connection profiles. 
>> * TR 4179 Ethernet filters were not working properly. 
>> * TR 4256 System did not release IP address back to RADIPAD global IP
pool. 
>> * TR 4270 MAX TNT reported incorrect progress code. 
>> * TR 4284 System not accepting any more calls, getting busy signals. 
>> * TR 4341 Series56-II modem cards could run out of buffers under heavy
load. 
>> * TR 4344 OSPF could stop running after approximately 10 days, with Warning
>> 200. 
>> * TR 4388 T1-Stat profile memory leak. 
>> * TR 258605 Sporadic disconnects with Cause Code 101/Progress 67. 
>> * TR 258651 T-Online: DTPT sessions were no longer load balanced after a
>> Slot-b. 
>> * TR 258678 Problems observed with HDLC-2 card and async PPP calls. 
>> * TR 258701 T-Online: ISDN Overlap-Receiving caused DNIS authentication to
>> fail. 
>> * TR 258714 FE-36 after disconnecting net-to-net (transparent) sessions. 
>> * TR 258720 Digital calls that did not send frames properly could hang
>> indefinitely. 
>> * TR 258748 Multipath external OSPF routes were not deleted when the route
>> went down. 
>> * TR 1000020 RADIUS checkpoint packets did not send valid packet and byte
>> counts. 
>> * TR 1000032 System could drop MP/MP+ packets sent through ATMP tunnels. 
>> * TR 1000085 Modem calls could sometimes fail to connect, requiring a card
>> reset. 
>> * TR 1000096 R2 signaling did not always handle the B-5 tone correctly. 
>> * TR 1000103 Finger did not work in E1 loads. 
>> * TR 1000166 UE1 (Frameline) card could not set 2DS framing. 
>> * Warning 179s observed on shelf controller. 
>> * Changes in system response to TCP keep-alives. 
>> * Userstat command did not identify ATM connections properly. 
>> * Timedate profile and Date command were inconsistent, could cause Y2K
>> issues. 
>> * OSPF is now more efficient in allocating memory for packet transmission. 
>> * Non-OSPF routes were ordered by metric rather than cost. 
>> * OSPF Router Dead Interval was too prolonged. 
>> * OSPF MD5 authentication was inoperative with Cisco routers. 
>> * OSPF could create an incorrect hidden route. 
>> * L2TP tunnels sometimes did not disconnect correctly. 
>> * SNMP: System did not report changing WAN speeds on ADSL ports. 
>> * SNMP: Calls to disabled DNIS did not generate call logging packets. 
>> * Incorrect slotItem count was returned to MIB Browsers. 
>> * MAX TNT did not return revision numbers to NavisAccess. 
>> * Long delays could occur when SNMP Managers queried modem status. 
>> * Series56 and Series56-II modems could stop accepting calls under heavy
load.
>> * Series56-II modems did not reset when placed on reserved list. 
>> * Graceful reboot of Series56-II digital modems under abnormal conditions. 
>> * V.120 and X.75 features did not work on Series56-II digital modems. 
>> * Modem card could fatal nolog under specific conditions. 
>> * Series56-II modems could stall during an FTP get. 
>> * Series56-II modem could cause FE-1 while processing TCP-Clear calls. 
>> * Framed routes defined in RADIUS dialout profiles were ignored. 
>> * RADIUS Accounting-On packet was not generated. 
>> * Reference count in the IPX server table was updated incorrectly. 
>> * IPX dialin pool was not updated in the IPX routing table. 
>> * IPX route pool leak was observed. 
>> * With DNIS-authenticated RADIUS profiles, encapsulation was not always
>> enforced. 
>> * Memory corruption could occur when RADIUS accounting was enabled.
>> * Compression settings could cause poor performance on HDLC-2 card.
>> * New X.75 connections could be refused due to hung sessions on the HDLC
>> card. 
>> * Calls on E1/T1 (including T3) channels were not always cleared properly. 
>> * Ethernet-2 100Base-T port could stop responding to ARP requests. 
>> * Intermittent resets on Ethernet-2 100Base-T port. 
>> * FE-2 on Ethernet card. 
>> * OC3-ATM card could occasionally stop sending data to the shelf
controller. 
>> * Harris switch in China dropped R2 calls with CLID. 
>> * Outbound R2 calls failed in Brazil. 
>> * Memory corruption in address pools on host cards. 
>> * FE-8 and FE-40 were observed on host cards. 
>> * Filter names were not handled properly. 
>> * Filters were not working properly on Ethernet interfaces. 
>> * System listened on port 1723 even when PPTP was not licensed. 
>> * Restoring configuration caused errors due to unlicensed features.
>> * FE-40 while saving Route or Connection profiles. 
>> * MP-encapsulated LCP packets were not handled as specified in RFC 1990. 
>> * FR PVC did not come up on SWAN/HDLC after remote device reset. 
>> * Code downgrades could cause memory and profile problems. 
>> * RIP-v1 summary failed when RIP triggering was enabled. 
>> * Simultaneous dial of MP calls spanning host cards 
>>  
>>  
>> Conexant (formerly Rockwell) firmware versions: 
>> * Series56 II Digital Modem Modules support Conexant V5.328 firmware, which
>> includes support for V.90, K56flex, K56plus, and all slower, standard modem
>> speeds. 
>> * Series56 Digital Modem Modules support Conexant
>> V2.098-K56_2M_DLP_CSM firmware, which includes support for V.90, K56flex,
>> K56plus, and all slower, standard modem speeds. 
>> * V.34 Digital Modem Modules support Conexant V1.610G24-V34_DP. 
>>  
>>  
>> Known issues: 
>> * 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 Ascend representative to
>> obtain an upgrade to Rev. C or higher. The Rev. B or lower cards continue
>> to work with releases earlier than 7.0.0. 
>> * MP bonding of analog calls is supported, but some client modems and
>> software may have compatibility problems. 
>> * The DS3-ATM card can sometimes generate a fatal error when operating
>> under heavy load with multiple configured VPI/VCIs. 
>> * Configurable receive and transmit data rate limits are not supported on
>> the DS3 ATM card. They are supported on the CAP-RADSL, 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. 
>> * Connection profiles for 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. 
>> * This release is not recommended for use with DM48-v.34 cards under heavy
>> load. 
>> * The 24-port SDSL data card sometimes stops transmitting and receiving
>> data when handling continuous heavy bidirectional traffic (>15 Mbps) on all
>> 24 ports. In addition, when one of the SDSL ports is connected or
>> disconnected at maximum line performance reach (AWG = 24; loop length =
>> 13750 ft.), the rest of the ports can stop transmitting and receiving
data. 
>> 
>> ++ Ascend Users Mailing List ++
>> To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
>> To get FAQ'd:	<http://www.nealis.net/ascend/faq>
>> 
>
>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>