Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) MaxTNT 7.0b0 release
The 7.0b0 beta release for the MAX TNT is now available to registered users
on www.ascend.com. The user will see a link to the Beta Agreement Form
from their logon confirmation screen. The agreement starts at:
http://www.ascend.com/private/beta
If the user accepts the agreement they are taken to an index page with
links to all of the available images.
The 7.0b0 beta release for the MAX TNT contains the following:
FEATURES:
* FID 384 Support for E1 Frameline card
* FID 427 Inband T1 support for ANI and called number
* FID 428 RADIUS dial-out billing code by source IP address
* FID 433 Overlap Receiving on PRI lines
* FID 504 Non-intrusive reload of nailed profiles from RADIUS
* FID 575 Setting individual SNMP traps
* FID 575 LMI link management on DLCI 1023
* FID 59446 Private static routes in RADIUS
* FID 259162 Configurable status and command window sizes
* FID 259163 ATMP resiliency in Primary and Secondary Home Agents
* FID 259718 RADIPAD support for centralized pool management
* FID 259758 Suppress host-route advertisements
* FID 509046 T1 R1 and R1-Modified (Taiwan) with CLID/DNIS
* FID 509444 Point-to-Point Tunneling Protocol (PPTP)
* FID 509578 Class attribute in RADIUS proxy Stop records
* FID 509586 R2 CLID processing (Brazil)
* FID 509590 R2 CLID processing (Argentina)
* FID 509610 Multichannel ATMP support
* FID 509610 IPX over ATMP
* FID 509614 Cause of No CLID (Japan switch type only)
* FID 509642 KR2 processing on E1 lines for Czech Republic
* FID 509650 R2 CLID processing (India)
* FID 509654 R2 CLID processing (Philippines)
* New modulation setting for Rockwell V.90
* Configurable AT answer string for modem calls
* Immediate modem dialout for E1 loads
* Multiple destination support for TCP-Clear
* Support for IDSL voice calls
* Support for ATM DS3 slot card
* Support for unchannelized DS3 slot card
* Support for unchannelized E1 slot card
* Support for full-duplex 100BaseT Ethernet-2 slot card
* Switched mode for xDSL lines
* Configurable transmit and receive data rate limits
* LQM magic number support
* X.75 support
* Configurable dialout timer
* Include terminating port in RADIUS Accounting
* Configurable retry time for RADIUS ID authentication
* Configurable behavior with Attributes 6 and 7
* ATM support in RADIUS
* Profile pathname and status indicators
* Messages about writing profile changes
* New flash card error messages
* Testing ATM operation and maintenance
* Parameter for displaying boot-loader version
* MAX TNT support for DSLPipe Plug & Play
* Configurable Rlogin source port range
* Routing Information Protocol (RIP) triggering
* Netstat -z to display zombie routes
* Changes in setting an interface-independent IP address
* MD5 authentication for OSPF (RFC 2178)
* Frame Relay PVC backup
* Answer-Defaults IPX Peer-Mode setting
* AppleTalk routing and remote access
* Modified tunneling parameter and attribute names
* Layer 2 Tunneling Protocol (L2TP)
* Virtual Routers (dynamic)
* Support for TCP-Clear connections in VRouters
* Store-and-forward IP-Fax
CORRECTIONS:
* TR 1414 RADIUS IPX static routes were not working.
* TR 1818 Show Calls did not display phone numbers.
* TR 2288 LQM negotiations sometimes failed.
* TR 2398 Warning 175,106, or 145, and FE-2 with IPX MP+ calls.
* TR 2449 Refresh -t did not update initial-banner from RADIUS.
* TR 2525 Netstat command showed zero packet counts for MP+ calls.
* TR 2571 MIB did not report modem card's second slot as Occupied.
* TR 2681 LEDs 5,6,7 or 8 did not work as documented.
* TR 2758 FE from slot could be ignored by the shelf-controller.
* TR 2768 TCP ISN generation is now more secure.
* TR 2781 First channel dropped if LU went below threshold.
* TR 2798 Dropping a channel stopped routing to the far end.
* TR 2835 CLID-authenticated sessions could ignore profile info.
* TR 2843 End-of-Packet pattern did not work properly for TCP-Clear.
* TR 2860 FE-18 was observed on E1 cards with R2 signaling.
* TR 2985 TCP Netstat counters were not always correct.
* TR 2994 Backup parameter now works properly.
* TR 3015 Second channel of MP+ call could dial the wrong number.
* TR 3016 TCP headers were corrupted with VJ compression.
* TR 3088 Filters did not work for some RADIUS-authenticated logins.
* TR 3103 Data filter caused modem or IDSL card to reset.
* TR 3136 Consecutive Framed-Route attributes were not parsed.
* TR 3151 FE-2 on shelf controller.
* TR 3191 Frame Relay PVC could become inactive under heavy load.
* TR 3207 RIP updates did not include routes for summarized pools.
* TR 3222 D-channel flapping on T3 card configured for NFAS ISDN.
* TR 3237 S7 could not be configured for incoming modem calls.
* TR 3239 Specific malformed UDP packet caused Ascend units to reset.
* TR 3303 Data corrupted when multiple Telnet sessions were active.
* TR 3383 MAX TNT returned incorrect Password Updated message.
* TR 250062 FR Direct connections could Ping or Telnet to the MAX TNT.
* TR 250117 Call filter did not prevent call from being generated.
* TR 250184 Did not allow null Acct-Key and Auth-Key.
* TR 250207 Only timeouts initiated cx to a Secondary Home Agent.
* TR 250269 Wrong ifOperStatus from the SNMP agent for a SWAN port.
* TR 250279 IP routing table was sometimes not updated correctly.
* TR 258579 Ascend-Authen-Alias not recognized for added channels.
* Immediate modem dialout could log Warning 179.
* Warning 106, 104, and sometimes FE8 on modem cards.
* Modems sometimes failed to handshake under heavy load.
* Cellular modem support did not work properly.
* Modem card FE-2.
* Modem card reset after failure to authenticate via RADIUS.
* Immediate modem server did not detect dead client sessions.
* V.34 modem card could FE-2 when loaded with TCP-clear calls.
* Disabling a modem and B channel, B channel came back up.
* Modem cards timed out when used for ATMP calls.
* Modem card could fail without fatal-log with pool calls.
* Nailed call caused FE 40.
* T3 card could FE-8 in some geographic locations.
* Intermittent ADSL-CAP and SDSL system startup problem.
* Increase maximum number of calls to 512 for DS3 ATM card.
* FE 8 and FE 2 with immediate service.
* DS3 ATM card now supports the DS3 MIB (RFC 1407).
* Occasionally MAX TNT did not dial out via Ping or TNTcall.
* Memory leak when running RADIUS proxy accounting.
* FE 111 when using RADIUS authentication.
* PPP sessions mistaken for MP+, causing disconnect code 35.
* Memory leak when filters were applied to out-dial calls.
* T-Online: Obtain external config from Auth-Boot-Host.
* Filters in the Answer-Defaults profile were not applied.
* Data filters did not take effect in slot-card IP-Interface.
* RADIUS Accounting did not work for Immediate modem dialout.
* SNMP frcircuitifindex reported zero for some FR links.
* FE 40 on shelf controller during startup.
* Resetting Ethernet-2 card could sometimes cause an FE1.
* Progress codes were incorrect for TCP-Clear sessions.
* SNMP: FR circuit table (RFC 1315) did not display all DLCIs.
* Slot command could bounce shelf controller.
* SMNP disconnect codes did not match RADIUS and Syslog codes.
* FE-1 following OSPF Database command.
* Userstat command could cause Warning 111 (buffer too big).
* DNS lookups could fail due to UDP port number leak.
* Routes are aged at 10-second rather than 1-second intervals.
* IP Probe Response was followed by ICMP Unreachable.
* System did not process next-hop routes in RIP-v2 input.
* FE-179 with UDP event queues.
* Local directed bcast packets (including RIP) were dropped.
* Did not forward directed bcast traffic from dial-in.
* FE-1 while adding a static ARP entry.
* On numbered interfaces, Ping returned the system address.
* RADIUS-based FR connection using a SWAN card failed.
* HDLC card could reset without fatal error under heavy load.
* HDLC card FE2 prevention.
* HDLC card Warning 106.
* During a FR circuit state change, slot cards could hang.
* DLCIs were not brought up or reported immediately.
* HDLC card reset after deletion of a Frame Relay PVC segment.
* ARA did not work on a slave shelf.
* FE-8 when system was running as ATMP Router Home Agent.
* ATMP FAs did not allow duplicate Mobile Client IP addresses.
* ATMP performance enhancement.
* Could not open more than one ATMP session.
* HA sometimes did not send error condition result code.
* Telnet to MAX TNT in a VRouter network did not always work.
* Could not ping through VRouter.
* VRouter could stop routing after approximately 5 minutes.
ROCKWELL CODE:
Rockwell modem code versions 2.084 (V.90) and 1.610g19 (V.34)
KNOWN ISSUES:
* In this release, WAN calls have to be started manually to form OSPF
adjacencies.
* L2TP is not yet ready for evaluation in release 7.0b0.
* The Primary-Home-Agent, Secondary-Home-Agent, and Home-Agent-Password
parameters in the Connection Tunnel-Options subprofile have not yet been
renamed to Primary-Tunnel-Server, Secondary-Tunnel-Server, and Password,
respectively. These changes will appear in the next beta release.
* 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.
* When booting, after the slot cards complete their power-on self tests,
the MAX TNT may continue to not accept calls for a few seconds. Immediately
thereafter, full operation resumes.
* Release 7.0b0 is not recommended for use with DM48-v.34 cards under heavy
load.
* Data filters applied in local Connection profiles do not take effect for
callers that start PPP after authenticating through the terminal server.
* Frame Relay NNI is not supported on Frameline and SWAN cards.
* 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.
* NetWare and STAC link compression.
NetWare, by default, relies on the Data Link layer (also called Layer 2) to
validate and guarantee data integrity. When you configure STAC link
compression, it performs an eight-bit checksum, which is inadequate for
NetWare data. This issue has existed in all previous releases of Ascend
software.
For MAX TNT connections, you configure STAC link compression in the PPP
subprofile of the Answer-Defaults profile and individual Connection
profiles. For NetWare connections, you can configure one of the following
link compression options:
- Configure either STAC-9 or MS-STAC compression, which use a more robust
error-checking method.
- Disable Link Compression by setting Link-Compression to None. When link
compression is disabled, the MAX TNT validates and guarantees data
integrity via PPP.
- Leave the default STAC compression setting and enable IPX-checksums on
your NetWare servers and clients. Both server and client must support
IPX-checksums. If you enable checksums on your servers but your clients do
not support checksums, their logins will fail.
Matt Holdrege http://www.ascend.com matt@ascend.com
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>