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

(ASCEND) 2.0.0 for the MAX TNT

2.0.0 for the MAX TNT has been given to support and manufacturing. This
release contains the following:

New features:

* Flash format change
* New dual-stage boot procedure
* Loadslave command for updating slave shelf code
* Reset -a to reset the mutishelf system
* MP and MP+ bundled channels span HDLC cards and shelves
* Multishelf Show and Open commands
* R2 signaling support for E1
* PRIdisplay command enhancements
* DS3 -i for internal loopback
* Clock-Source command enhancements
* Support for 64K and 56K calls over channels using R2 signaling
* Multiple NFAS groups on T1 and T3 cards
* E1_R2 Israeli signaling
* V.34 setting for 56k modem cards
* Command for displaying WAN session data
* Terminal server login timeout
* New call-routing sort method for digital calls
* Direct-access modem dialout over 56K modems
* Performance enhancements for TCP-Clear calls
* POST and loopback test for xDSL cards
* IDSL command for loopback and error tests
* BRIdisplay command for displaying D-channel traffic
* New SDSL statistics reported
* New maximum down-stream rate for ADSL-CAP
* Nailed connections supported via IDSL
* Frame-Relay circuit switching on xDSL cards
* OSPF does not support virtual IP interfaces
* IP port caching
* TCP-timeout parameter enabled
* OSPF global option for disabling ASBR calculations
* Change in ASE route handling for NSSA configurations
* Local DNS table
* Parameters for handling directed broadcasts
* IPX routing for the MAX TNT
* Frame Relay Switching
* Ascend Tunnel Management Protocol (ATMP)
* ATMP support for connecting to a GRF switch
* Home agent inactivity timers for ATMP tunnels
* Changes to Syslog output
* Fatal crash information on console
* Finger (RFC 1288) support and Userstat enhancements
* Userstat -k to terminate user sessions
* Slot card and system uptime information
* New disconnect code (210-slot card down)
* Separate transmit and receive data rates reported
* IP-Pools command
* Netstat command displays active sockets on slot cards
* Netstat reports TCP statistics collected from slot cards
* Add DNIS and CLID to Syslog messages
* Call logging using the RADIUS accounting protocol
* Configurable session listing output
* Setting the number of RADIUS accounting retries
* NAS-port type added to RADIUS accounting
* RADIUS accounting for failed authentication
* Preventing accounting Stop packets with no user name
* Distinct ID sequences for RADIUS authentication and accounting
* Unique RADIUS accounting IDs based on source port number
* RADIUS accounting Start packet includes user's IP address
* ATMP attributes in RADIUS accounting Stop records
* New Local-Profiles-First setting
* Configurable cause element in ISDN Disconnect packets
* Nailed connections retrieved from RADIUS
* Shelf-controller proxy RADIUS accounting
* NAS port identifier optionally reported in new format
* SNMP agent on multishelf system now reports on slave cards
* Ability to disconnect user via SNMP request
* Ability to enable and disable modems via SNMP
* SNMP support for TNT IDSL slot card
* SNMP advanced.mib now supported
* DTPT sessions to the ZGR identified in Session MIB
* Multishelf traps enabled by default
* Slave shelves generate trap when multishelf link is down
* T-Online: PRI-PRI switching for E1
* Pseudo-tunneling PPP for T-Online

Corrections:

* TR 1510: Closing Immediate Telnet session cleared call before Telnet closed.
* TR 1754: Old IP route entries were not cleared under some conditions.
* TR 2087: SNMP ifOutOctets and ifInOctets did not work for Ethernet cards.
* TR 2110: Connections/Session count was not accurate.
* TR 2157: The Max-Call-Duration parameter did not work correctly.
* TR 2257: Digital call routing could sometimes stop on MP+ calls.
* TR 2285: MAC addresses and link-states were inaccurate for Ethernet ports.
* TR 2305: OSPF advertised private routes.
* TR 2309: Host and time information was not generated for TCP-Clear sessions.
* TR 2324: Shelf-controller reset with Warning 191 but no FE.
* TR 2362: SNMP MIB variable did not report slave shelf serial number.
* TR 2373: NVRAM corruption following reset has been fixed.
* TR 2383: Formatting both flash cards could sometimes cause a reset with
FE 104.
* TR 2398: Warning messages 175,106, or145, and FE2 with IPX MP+ calls.
* TR 2438: FTP over ATMP from client to server sometimes failed.
* TR 2443: MAX TNT now supports up to 15 FrameLine cards.
* TR 2456: RADIUS authentication for dialins failed after sustained
dialin/dialout traffic.
* TR 2459: Idle code was not transmitted in unused DS0s on T3 card.
* TR 2466: Connection IP address not included in RADIUS accounting Start
packets.
* TR 2473: MAX TNT did not grab all outgoing routes and profiles from RADIUS.
* TR 2483: Modems reset with FE 2.
* TR 2502: ISDN users could not connect and Ifmgr output displayed
incorrect user names.
* TR 2504: Second flash card could be unavailable.
* TR 2506: SNMP traps now report loss of communication to slave shelf.
* TR 2521: A write error occurred when loading code to flash.
* TR 2522: FE 3001 on Ethernet cards is now reported correctly as a warning.
* TR 2531: The Netstat command showed T-Online DTPT interfaces in domestic
loads.
* TR 2537: MAX TNT sometimes sent packets to the wrong WAN interface.
* TR 2552: 56K- modem cards showed high CRC errors during JPEG file down load.
* TR 2574: Multicast address exported via SNMP caused a problem with HP
OpenView.
* TR 2578: IP-Direct connections did not work properly.
* TR 2582: Calls nacked via DNIS did not return User Busy.
* TR 2619: Ethernet, HDLC, and modem cards could generate FE 2 under heavy
load.
* TR 2625: System sometimes reset with FE 2 after several days of heavy load.
* TR 2628: RADIUS accounting records could replace user name with modem
number.
* TR 2629: MAX TNT could lose its configuration following a system crash or
reset.
* TR 2630: V.32 modems had difficulty connecting to 56K modems due to
V.8bis tone.
* TR 2647: V34 modems reset with FE2.
* TR 2648: RADIUS accounting could report incorrect information for async
PPP calls.
* TR 2662: Abnormal tone before V.8 56K tone blocked some modem callers.
* TR 2666: After 7 to 24 hours, E1 channels using R2 signaling became
inoperative.
* TR 2685: 56K modem cards showed low sync rate ("dead air") on heavily
loaded system.
* TR 2688: Shelf-controller could crash following Warning 108 when
receiving a small bus packet from a slot card.
* TR 2690: Memory leak could occur when filters were obtained from RADIUS.
* TR 2696: Network Management option was not enabled by the update hash code.
* TR 2711: OSPF could cause FE 29 on the shelf-controller.
* TR 2714: HDLC card sometimes wouldn't load when unit is busy.
* TR 2715: HDLC cards appeared to fail with Timeout Failure error messages.
* TR 2718: Ethernet slot card crashed when Proxy ARP was enabled.
* TR 2720: ISDN users sometimes failed to connect due to erroneous RADIUS
timeouts.
* TR 2723: Second channel dropped on 2-channel permanent switched connection.
* TR 2732: FE 1s were sometimes observed on the shelf-controller.
* TR 2733: Ethernet card could sometimes generate a FE 8.
* TR 2735: Multishelf system couldn't load more than 16 slot card
simultaneously.
* TR 2736: Modem card reported WANSESS: newSession: Out of Sessions.
* TR 2738: FE 1 could occur when modem cards went down and then came up.
* TR 2739: FE 8 or FE 104 could occur during external authentication of PPP
sessions.
* TR 2744: IP port caching enabled.
* TR 2745: Coredump fixes.
* TR 2757: Date/time could become corrupted, jumping to January 1, 2000.
* TR 2758: FE 29 errors reported on modem cards.
* TR 2768: TCP ISN generation is now more secure.
* TR 2794: Additional information provided about SNMP-initiated transfers.
* TR 2798: When MP dropped a channel, MAX TNT stopped routing to the far end.
* TR 2808: Userstat command output could show incorrect number of users.
* TR 2834: Slot cards reset when trying to log Warning 104.
* TR 2835: CLID-authenticated sessions could ignore profile information.
* TR 2841: Modem transmits level are now correct for K56 modems.
* TR 2843: End-of-packet character did not work properly for TCP-Clear calls.
* TR 2897: Invalid emergency log message seen on console.
* TR 2943: MAX TNT not returning Port Address/NetMask via SNMP
* TR 2952: Reduced incidences of transmission errors.
* TR 2969: Call connect rate could degrade under heavy call volume.
* TR 2972: Encapsulation method was not enforced in local Connection profile.
* TR 2983: Ethernet card could reset without generating a fatal log message.
* TR 2993: Framed IP route pointed to ie0, should point to a WAN port
interface.
* TR 3013: Syslog output optionally reported in new format.
* TR 3015: Second channel of an MP+ call could dial the wrong number.
* TR 3023: FE 36 was observed when MP calls spanned multiple HDLC cards.
* TR 3103: Data filter could crash the IDSL card.
* TR 130737: Pool address was not freed reliably when multi-channel call
terminated.
* TR 250022: SNMP sysConfigTftp object was not supported by the MAX TNT.
* TR 250036: Security problem with CLID authentication.
* TR 250050: System Up diagnostic was not logged after a reset.
* TR 250062: FR Direct connections could Ping or Telnet to the MAX TNT.
* TR 250071: RADIUS accounting packet octet counts were inaccurate.
* TR 250075: The system did not refresh RADIUS routes if dialout-poison was
enabled.
* TR 250078: RADIUS address pools were not deallocated properly.
* TR 250080: The Expect Callback feature did not work.
* TR 250081: Immediate service did not work for CLID or DNIS authenticated
calls.
* TR 250096: The Acct-Sess-Interval parameter did not work properly.
* TR 250102: HDLC cards ran out of memory intermittently.
* TR 250108: Call rejected with more modems in use than callers.
* TR 250117: Call-Filters in Connection profiles did not prevent dialout.
* TR 250127: CIDR routing caused low memory conditions.
* TR 250217: UDP checksums were generated intermittently.
* A MAX TNT can now bring up 720 calls.
* Ascend MIB slots group did not report multishelf slots.
* Slot -d command did not check shelf numbers correctly on multishelf systems.
* Data corruption could occur if a host card when down in a multishelf system.
* Slot cards could take several minutes to come up in a loaded multishelf
system.
* Excessive CRC errors on some multishelf systems.
* Multishelf system with three shelves could not boot slave slot cards.
* The Fatal-History command did not report shelf numbers.
* Slave shelves did not log RESET to master's fatal log.
* HDLC cards did not load properly in slave shelves of a multishelf system.
* Slave shelves did not work properly with ATMP.
* Shelf-controller FE 8 problem has been fixed.
* Out-of-memory error on the shelf-controller has been fixed.
* Shelf-controller could crash on early Ethernet receive.
* Potential memory leaks were fixed.
* FE 2  could occur on shelf-controller  following a coredump.
* Ethernet card failed to come up under certain conditions.
* Coredump was not supported on local Ethernet interfaces.
* Slot cards in DIAG state remained UP if coredump failed.
* Ethernet controller could overwrite current packet.
* 100Base-T interface was displayed in UP state when card is downed or
removed.
* Shelf-controller's MAC address could be overwritten.
* Memory corruption in L2/L3 control blocks occurred when an ISDN line was
disconnected.
* NFAS fixes.
* Trunk-Group parameter accepted illegal values.
* D4 framing and 56K data service did not work on Frameline cards.
* T1, E1, and Ethernet slot cards were not notified of System profile updates.
* Intermittent D-channel failure on T3 cards could sometimes occur.
* DS0 idle code generation was not generated correctly on PRI lines on the
DS3 card.
* Writing a T1 or E1 profile with an invalid index could generate a FE 1.
* Problems with E1 outgoing calls when T-Online was disabled in the System
profile.
* Force-56 didn't work properly for E1 configurations.
* A T3 card provisioned with PRI DS1s could crash.
* T1 interfaces could come up as unavailable.
* Shelf-controller could crash when a T3 card went down with a fatal error.
* Nailed-Group parameter accepted illegal values.
* MAX TNT could stop accepting calls.
* T3 card could crash a shelf when it dumped core.
* Host port mapping wrong for FrameLine cards.
* Frameline memory was depleted under heavy packet traffic.
* Outbound calls used first DSL regardless of line's state.
* xDSL and unchannelized E1 cards now support RADIUS proxy accounting.
* System did not respond with message when second Setup message was received.
* SNMP SET operation on wanLineUsage object failed.
* xDSL and unchannelized E1 cards now support RADIUS proxy accounting.
* TCP-clear connections could cause modem cards to fail with FE 8.
* Frame Relay connections could cause HDLC cards to fail with FE 8.
* RADIUS initialization on slave-shelf 56K modem cards failed intermittently.
* VJ compression modem sessions now function with a smaller number of slots.
* Fatal Error 102 sometimes occurred on 56K-modem cards.
* Host cards could generate a FE 8 under heavy MP+ load.
* FE102 on 56k modem cards.
* V.34 modem card could crash when loaded with TCP-clear connections.
* Fatal 29 when modem sessions hang up.
* Modem slot card FE2 with RADIUS authentication.
* RADIUS external routes could cause host card memory leak.
* Modem-connected terminal-server session could hang on Telnet to an
unknown host.
* Dialout for 56K modems sometimes failed.
* Host cards could periodically reset.
* Memory leak could occur for incoming modem calls.
* Replace Warning 390 with a Syslog message.
* Modem calls that failed DNIS authentication were considered modem failures.
* Modem cards reset if call disconnected as ATMP tunnel request timed out.
* If a slot card went down, all ATMP tunnels on the card were not removed.
* HDLC card could fail if an ATMP mobile client dialed in using Stac
compression.
* HDLC cards sometimes operated slowly under light load.
* HDLC cards could occasionally crash under heavy traffic.
* HDLC card failed to come up about 15% of the time.
* HDLC card failed with FE8 under heavy MP+ and MP call traffic and dynamic
address assignment.
* HDLC card could crash if a Ping packet arrived during call setup.
* HDLC cards could crash receiving LCP frame from a slave MP or MP+ channel.
* HDLC cards in slave shelves could sometimes fail to load.
* All channels of MP and MP+ connections were sometimes not cleared.
* The MP Maximum-Channel parameter in the Answer-Defaults profile was not
used.
* MAX TNT could open MP+ when a connection was configured for MP.
* HDLC card could report low memory on 128 calls.
* xDSL card could sometimes crash under heavy traffic.
* After POST on SDSL and ADSL-CAP, a DSLPipe could not Ping the MAX TNT.
* PPP clients could fail to reconnect after an ADSL or SDSL line came back up.
* Problems with more than nine SDSL cards.
* PPP calls failed to authenticate on SDSL-nailed connections (COE and CPE) .
* Performance improvement for xDSL cards.
* ADSL or SDSL line down caused fatal error.
* Occasional transmit Lock-up for ADSL-CAP Line card during high traffic.
* SuperDigital 128 over nailed IDSL connections did not work properly.
* Added virtual devices to the IDSL module to support Frame Relay.
* Performance enhancement for IDSL connections.
* IDSL card was unusable above 14 connections.
* FE conditions fixed for xDSL cards.
* Duplicate SLIP sessions could sometimes occur.
* IP broadcast addresses were cached.
* IP pool addresses became unavailable when used for MP or MP+ calls.
* IP pool addresses sometimes leaked .
* Duplicate routing sessions could occur for SLIP sessions.
* Connection profile routes were assigned an incorrect preference value.
* The IPcache cache command did not display one page of output at a time.
* Remote-Address and Local-Address accepted illegal values.
* Client-Default-Gateway should not allow a netmask specification.
* IP packets originating on a slot card did not use the IP route cache.
* Could not establish SLIP connection using IP Pools.
* Phantom interfaces prevented subsequent calls.
* Very heavy traffic to the system address could cause FE2 on the
shelf-controller.
* A problem with external routes from RADIUS sometimes caused dialouts to
fail.
* Shared-Prof set to No did not prevent MP+ calls from sharing a profile.
* Multiple IP interfaces did not work on the shelf-controller.
* Routes were non-private for some assigned addresses from a summarized pool.
* Deleting virtual IP-Interface profiles could eventually cause an FE2.
* FE 179 was observed related to UDP event queues.
* The local route interface could change when a call came in.
* Netstat command output did not report Finger service (port 79).
* ICMP redirects were not sent in some instances.
* VJ compression could cause reduced throughput.
* Telnet port (23) could stop listening.
* Memory leak in route filters.
* RIP could send duplicate packets to the multicast/broadcast address on
Ethernet.
* IGMP query packets could keep an idle connection alive.
* RADIUS authentication failed when System-IP-Addr  was not set.
* The MAX TNT did not work as an ATMP home agent in router mode.
* ATMP tunnel routes were not removed from the routing table.
* Data transfer to client over SLIP/CSLIP sessions could hang.
* Large packet sizes could cause Ping to fail on MAX TNT Ethernet interfaces.
* OSPF Fatal Error 29 conditions have been fixed.
* RADIUS dialout routes were not exported properly into OSPF.
* MAX TNT didn't handle some loop situations properly in OSPF environment.
* OSPF MIB was not enabled in earlier releases.
* OSPF Database command output did not show ASE Type-5 entries.
* OSPF Database command caused FE 1 or FE 29 when NSSA was enabled.
* Static routes were entered in the OSPF database as ASE-5 Links even in
stub areas.
* Framed Address information omitted from RADIUS start accounting records.
* RADIUS messages did not identify retry attempts.
* RADIUS accounting START and STOP packets did not have guaranteed delivery.
* RADIUS reply messages could be truncated.
* RADIUS accounting ON and OFF packets sometimes timed out.
* Routes learned from RADIUS showed up twice in the routing table.
* RADIUS packet type 51 was not delivered from Ethernet cards.
* Check-point RADIUS accounting memory leak fixed.
* Some values were not recorded in RADIUS Accounting Stop packets.
* RADIUS CHAP authentication denial could cause memory error with Warning 104.
* RADIUS authentication could fail under certain conditions.
* RADIUS accounting reported DTPT sessions.
* Conflicts between RADIUS and local configurations resolved.
* NasPortID (5) and NasPortType (61) were reported in Accounting On/Off
packets.
* Memory leak could occur during CLID authentication to RADIUS.
* RADIUS permconn profiles for FR-CIR management type did not load properly.
* RADIUS-authenticated Immediate Telnet sessions did not release
terminal-server resources.
* SNMP accounting progress codes and disconnect reasons were incorrect for
immediate TCP sessions.
* System reset via SNMP MIB failed on the MAX TNT.
* SNMP applications could not read information from an Ethernet slot card.
* The timestamp on SNMP call-clear events did not show when the call
terminated.
* Disconnection code 185 is now reported to SNMP accounting as expected.
* User names could be reported inaccurately in SNMP accounting events.
* TCP-clear sessions could generate extra SNMP name or service change events.
* Users were not disconnected via SNMP request.
* Some SNMP event billing information was missing.
* SNMP accounting information was incorrect for immediate TCP-clear sessions.
* Advanced-Agent Wan MIB restored to its previous OID.
* SNMP slotName object did not report the 100Base-T interface.
* SNMP reported nailed channels as switched channels when there was no
physical interface.
* Unable to Set the slotmdmItemConfig variable in Slot Modem table.
* Advanced MIB scalars should only count switched channels.
* Called-Number-Type did not allow Network-Specific setting in Connection
profiles.
* CLID authentication sometimes did not work properly.
* DNIS authentication sometimes did not work properly.
* CLID and DNIS were not contained in some Syslog messages.
* CLID security did not work with a null callID.
* Failed CLID/DNIS authentication could cause FE1 on slot cards.
* Send-Auth-Mode parameter accepted illegal values.
* Active terminal-server sessions sometimes disconnected based on the idle
timer.
* Terminal-server error handling has been improved.
* PPP and immediate TCP clear sessions invoked from the terminal server now
use memory more efficiently.
* Dial-up terminal-server session cannot return to the terminal-server prompt.
* Warning 191 could be reported for TCP-Clear connections.
* TCP-Clear connections could sometimes cause FE8.
* Spurious report of FE8 could sometimes appear on serial console.
* Excessive fatal error log messages on the serial port could cause a reset.
* Flash card write error when loading code
* Saving configuration to a server caused a system reset.
* Slot cards could reset when trying to log Warning 104.
* Shelf-controller Ethernet driver reported Warnings as Fatal Errors.
* Secure Access firewall packet traces did not display as expected.
* Firewall error messages have been fixed.
* Listing Firewall profile contents could cause an FE1 or FE40.
* Firewalls could fail to match on some packets.
* Ascend Enterprise MIB did not report Frame Relay information on SWAN cards.
* The Nailed-Up-Group parameter now allows a maximum value of 1024.
* FR-Link-Up parameter deleted and corresponding RADIUS attribute deprecated.
* IGMP command output was incorrect.
* Command-line text field length limit was not enforced accurately.
* Spinning cursor now indicates progress of Load and Save commands.
* WANDisplay debug command displayed transmitted frames with incorrect length.
* Clearing a T-Online call could cause an FE 1.
* T-Online: The MAX TNT can now dialout MP+ calls when T-Online is enabled.
* T-Online: Calling DTPT Connection profile made LAN inaccessible.
* T-Online: Problem 503 has been fixed.
* T-Online: Problem 30965 has been fixed.
* T-Online problem # IM 30704 has been fixed.
* T-Online: Dialing the ZGR/T-Online profile using tntcall -c could crash
the router.

Known issues:

* FE29 in some OSPF environments.
* 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.
* 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
subprofiles 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.

Rockwell code version:

* Release 2.0.0 supports Rockwell K56flex code version 1.160T.






Kevin


++ 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: