Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(ASCEND) MaxTNT 2.1

2.1.0 for the MaxTNT has been given to Customer Support.  This release
contains the following:

Features:
Inband T1 support for ANI (Caller ID) and called number
RADIUS dial-out billing code based on source IP address
Overlap Receiving on PRI lines
Non-intrusive Refresh -n command
Setting individual SNMP traps
LMI link management on DLCI 1023
Configurable status and command window sizes
ATMP resiliency in Primary and Secondary Home Agents
Private static routes in RADIUS
T1 R1 and R1-Modified (Taiwan) with ANI and called number
Class attribute in RADIUS Stop records when slot card goes down
R2 CLID processing (Brazil)
R2 CLID processing (Argentina)
IPX over ATMP
Multichannel ATMP support
R2 CLID processing (Philippines)
New modulation setting for Rockwell V.90
Configurable AT answer string for incoming modem 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
RADIPAD support for centralized pool management
Configurable retry time for RADIUS ID authentication
Configurable login behavior with RADIUS Attributes 6 and 7
Profile pathname and status indicators
Messages about writing profile changes
New flash card error messages
New command for testing ATM operation and maintenance
Parameter for displaying boot-loader version
Frame Relay Permanent Virtual Circuit (PVC) Backup
Answer-Defaults IPX Peer-Mode setting
AppleTalk routing and remote access
Virtual Routers (static)
Store-and-forward IP-Fax

Corrections:
TR 1414    RADIUS IPX static routes were not working properly.
TR 1818    Terminal-server 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 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 line utilization went below
threshold.
TR 2798    Dropping a channel stopped routing to the far end.
TR 2835    CLID-authenticated sessions could ignore profile information.
TR 2860    FE-18 was observed on E1 cards with R2 signaling.
TR 2994    Backup parameter now works properly.
TR 3015    Second channel of an MP+ call could dial the wrong number.
TR 3016    TCP headers were corrupted when VJ compression was enabled.
TR 3088    Filters did not work for some RADIUS-authenticated
terminal-server logins.
TR 3103    Data filter caused modem or IDSL card to reset.
TR 3136    Consecutive Framed-Route attributes were not parsed
correctly.
TR 3151    FE-2 on shelf controller.
TR 3191    Frame Relay PVC could become inactive under heavy load.
TR 3237    S7 could not be configured for incoming modem calls.
TR 3239    Specific malformed UDP packet caused Ascend units to reset.
TR 250062  FR Direct connections could Ping or Telnet to the MAX TNT.
TR 250117  Outgoing call filter did not prevent call from being
generated.
TR 250184  External-Auth profile did not allow null Acct-Key and
Auth-Key.
TR 250269  Wrong ifOperStatus from the SNMP agent for a SWAN port.
TR 250279  IP routing table was sometimes not updated correctly.
*  Cellular modem support did not work properly.
*  Modem card FE-2.
*  Modem card reset after failure to authenticate a caller via RADIUS.
*  Immediate modem server did not detect dead client sessions quickly
enough.
*  V.34 modem card could FE-2 when loaded with TCP-clear calls.
*  When disabling a single modem and B channel, the B channel came back
up.
*  Modem cards timed out when used for ATMP calls.
*  Modem card could fail without fatal-log with pool calls.
*  HDLC card reset if Ping arrived during call setup.
*  HDLC card could FE-29 when used in a Frame Relay NNI setup.
*  HDLC card Warning 106.
*  10 to 14 second lag between call disconnect and No Carrier.
*  Number of DS0 channels could only set from 1 and up.
*  T1 card toggle could reset HDLC card.
*  xDSL cards could sometimes FE-1 under heavy traffic.
*  ADSL-CAP CPE disconnected too soon.
*  Intermittent ADSL-CAP and SDSL system startup problem.
*  Occasional Transmit Lock-up for ADSL-CAP card during high traffic.
*  Frameline card could FE-8 with no fatal log.
*  SWAN card began dropping packets under heavy load conditions.
*  Ethernet slot card reset if Proxy ARP was on.
*  FE-1 under light traffic.
*  MAX TNT could fail to dial out for certain Connection profiles.
*  System stopped accepting calls.
*  Host-to-host FTP sessions could fail under certain conditions.
*  Warning 191 & 192 and other fixes for TCP-Clear.
*  Host card could FE-29 while attempting to make a TCP connection.
*  Telnet provoked unwarranted Warning 179.
*  Warning 179 in TCP sessions.
*  ICMP redirects were not sent in some instances.
*  IP pool leakage with MP/MP+ calls.
*  Connection profile routes were assigned an incorrect preference
value.
*  Hidden OSPF entries were created in the routing table for local
Ethernet routes.
*  FE-29 on the shelf-controller in an OSPF environment.
*  Fatal-40 in OSPF database display.
*  Changing logical IP addresses deleted local Ethernet.
*  Parameters for handling directed broadcasts did not default to Yes.
*  FE-179 with UDP event queues.
*  DNS lookups could sometimes fail due to UDP port number leak.
*  OSPF Database displayed only a partial link-state database.
*  FE-1 following OSPF Database command.
*  Local directed broadcast packets (including RIP packets) were
dropped.
*  The MAX TNT was not processing next-hop routes in RIP-v2 input
packets.
*  FE-1 while adding a static ARP entry while a matching ARP entry is
pending.
*  DNS Local Table memory usage was reduced to prevent possible FE-36.
*  Routes learned from RADIUS sometimes showed up twice.
*  RADIUS packet type 51 was not delivered from Ethernet slot.
*  RADIUS ID authentication retry caused timeouts related to the T310
timer.
*  Filters specified in the Answer-Defaults profile were not applied.
*  T-Online: All external configuration was not obtained from
Auth-Boot-Host.
*  101/67 disconnects were sometimes not related to LAN security.
*  Memory leak could occur when running RADIUS proxy accounting.
*  RADIUS Attribute 7 was not interpreted if Attribute 6 was not
defined.
*  RADIUS Accounting did not work for Immediate modem dialout sessions.
*  System did not issue Accounting Stop packets if a card reset.
*  Memory leak could occur following terminal-server login.
*  Terminal-server idle timer did not work for immediate service logins.
*  Occasional FE- 40 in Terminal-server interface from a Telnet session
on Ethernet.
*  SLIP/CSLIP sessions could hang on data transfer to dial-up client.
*  Warning 176 could occur upon close of immediate Telnet session.
*  CL Syslog record did not always appear.
*  Progress codes were incorrect for TCP-Clear sessions.
*  Slot command could bounce shelf controller.
*  Fatal error log entries were not always written to error log.
*  TCP-clear sessions could generate extra SNMP name or service change
events.
*  Sessions window reported answered calls as unknown.
*  System went down with FE-8 while trying to save configuration.
*  Error in displaying help text for Area-Type parameter.
*  Userstat command could eventually cause Warning 111 (buffer too big).
*  SNMP: Advanced MIB scalars should only count switched channels.
*  SNMP: Ascend devices sent non-standard Frame Relay traps.
*  SNMP: Frame Relay circuit table (RFC 1315) did not display all DLCIs.
*  SMNP: Disconnect codes did not match RADIUS accounting and Syslog
codes.
*  SNMP: Ethernet interfaces were not listed in the slot iftable.
*  FE-40 when booting shelf with shelf number thumb wheel set to 0.
*  Cards on slave shelves could sometimes hang during a Load command.
*  HDLC card crashed when receiving an LCP frame from a slave MP(P)
channel.
*  When local FR T1 CPE went down, DLCIs were not activated when up
again.
*  During a Frame Relay circuit state change, slot cards could hang with
no fatal log.
*  Frame Relay circuits didn't come up if nailed-group 0 was used.
*  FE-29 reading RADIUS Frame Relay profiles.
*  IPX RIP and SAP going across modem had wrong source node address.
*  System dropped IPX burst-mode packets and caused session timeout.
*  IPX throughput was slow.
*  Local IPX server information was lost if authentication failed.
*  IPX with MPP encapsulation failed.
*  IPX routing table could become corrupted.
*  Could not open IPXCP as stand alone WAN protocol.
*  MAX TNT did not forward NetWare information learned on a LAN
interface.
*  ATMP Foreign Agents did not allow two Mobile Clients with the same IP
address.
*  ATMP performance enhancement.
*  FE-8 when system was running as ATMP Router Home Agent.
*  Could not open more than one ATMP session.
*  NavisAccess could not read the interface description for UT1
(Frameline) cards.

Known issues in 2.1.0:
*  A data filter applied in a local profile doesn't take effect for
terminal-server calls.
*  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.
*  This software is not recommended for DM48 modem cards under heavy
load.
*  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 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.


Release 2.1.0 contains the following Rockwell modem code versions:
*  V.34: V1.610G19-V34_DP
*  V.90: V2.084-K56_DLP_CSM

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>
Follow-Ups: