(ASCEND) 7.2.4 for MAX

[Matt Holdrege <holdrege@lucent.com>]

TAOS Release 7.2.4 for MAX family has been given to customer support.
This release contains the following:

CORRECTIONS
3374
When the Ascend-Menu-Item RADIUS attribute was set, terminal-server menu
commands other than ping, ppp, or telnet failed to work. This problem has
been corrected.
3673
Occasionally, the MAX unit gave users, when sharing a Connection profile,
the same Security profile.
4003
A nailed PPP connection failed after a cable was pulled out and plugged
back in. The problem that caused the failure has been corrected.
4569
A problem that resulted in occasional false RADIUS accounting records with
session IDs of 0 has been corrected.
4616
MAX units were resetting with FE29 errors when running X.25
PAD-data-intensive applications.
4918
MAX units were sending ReleaseComplete with ISDN Cause code #96 for
Japanese switch types. This has been corrected.
4966
Ambiguity in interpretation of NAS port format configuration has caused
confusion. The problem has been resolved by defining a new,
Ascend-specific, RADIUS attribute to report the format and eliminate
confusion.
The new attribute, Ascend-NAS-Port-Format, specifies how to interpret the
format used in the RADIUS accounting request packet NAS port specification
(as indicated by the NAS-Port attribute). The attribute values are
described in the TAOS 7.2.4 Release Notes.
5094
A problem on a MAX unit that resulted in PRI channels being unavailable for
outgoing calls has been corrected.
5306
When Auth Reset Timeout was left at the default value, a MAX unit that is
configured for authentication by more than one RADIUS server booted
incorrectly from the secondary server instead of the primary server after
a reset. This problem has been corrected.
5307
MAX 2000 units with PIAFS cards installed were resetting with an FE8 error.
The problem has been corrected.
5386
A problem that resulted in intermittent AO/DI failures has been corrected.
5482
Sync users were unable to connect to the MAX and were receiving the
message: CANT OPEN 1 HDLC CHANNEL. The problem has been corrected.
5483
Intermittent failures of E1/R2 lines to send expected signaling to the
Central Office have been corrected.
5504
When a MAX unit?s DNIS capacity management feature denied a call, the
syslog message for the call reported disconnect code 2 and call progress
code 2, both indicating ?unknown.? The correct disconnect and progress
codes were not reported. The problem has been corrected.
5505
Switched modem users using the RADIUS authentication attribute
Ascend-PPP-Address in their profiles were unable to ping the MAX unit, and
the MAX unit could not ping the client. This problem has been corrected.
5518
When upgrading to release 7.2.3, configuration files were corrupted on a
MAX unit without the L2TP hash bit set. The problem has been corrected.
5521
A MAX 6000 using R2 signaling with heavy inbound calling experienced an
FE17. The problem has been corrected.
5532
A problem was resulting in calls failing because of failed RADIUS
authentication when the Auth Pool parameter was set to Yes, but no
addresses were available in the first pool. The problem has been corrected.
5539
When RADIUS authentication or accounting ports were configured to be a
ports already in use, the MAX unit sent the packets to port 0 and
consequently they never reached their destinations. This has been
corrected. Now the MAX assigns a port from the set of non-privileged ports
and continues with operations, sending a warning message to the syslog
server.
5677
A problem that resulted in a MAX unit experiencing FE8/FE29 with SecurID
authentication has been resolved.
5682
V.42 BIS compression for PIAFS was always disabled. This has been
corrected. To enable V.42BIS correction, use the DO menu to enter the
Diagnostics CLI. Use the phsv42bis command to toggle the compression
V.42BIS compression on and off. For example:
 > phsv42bis
PHS V42bis compression is OFF
 > phsv42bis
PHS V42bis compression is ON
 >
5697 EOI 42013 Incoming calls from a MAX 6000 to the latest NEC TA in
Japan were resulting in CRC errors on the NEC TA. The errors were caused by
the MAX unit's echo cancellation, which is not necessary in Japanese
digital networks. The software no longer sends echo cancellation tones for
Japanese switch types.
20251
A problem that resulted in an FE20 when changing a PRI line from NT to TE
has been corrected.
250255
When two clients were using ATMP, they were able to share Connection
profiles, regardless of the value specified in the Ascend-Shared-Profile
attribute. The problem has been corrected.
258778
Channel signalling on DASS2/DPNSS E1 lines stopped after several hours of
operation. The problem has been corrected.
258804
When a remote peer dialed into a MAX using NAT with the Reuse Last IP
Address option set, the option caused the peer to request the same IP
address it was allocated the last time it called the local unit. Using the
callback feature, the connection was established, but while the remote
peer?s IP address was acknowledged, the address was not entered into the
routing table and data transfer was not possible. This problem has been
corrected
258821
A problem that resulted in communication failure between ATMP Foreign
Agents and Home Agents when tunnel numbers were greater than 65535 has been
corrected.
258839
NAT functionality was not supported on E1 MAX units. The software load
including NAT/DHCP is now available.
258875
The TAOS DPNSS implementation did not recognise the CLI Supplementary code
*50*. This problem has been corrected.
258881
When using an incoming AO/DI connection profile, non-AO/DI MP calls on the
first B-Channel were idled after adding the second B-Channel. The problem
has been corrected.
258883
When trying to store and select a profile using X.25 commands, the MAX unit
reset without a fatal error message. The problem has been corrected.
258937
Users were able to ping a MAX from the terminal server when the operation
had been disallowed. The problem has been corrected.

1000107
A problem that resulted in SNMP queries returning corrupted community
strings has been corrected.
1000207
A MAX 4000 unit was reporting the incorrect Security profile in use in the
fatal-error log messages. The problem has been corrected.
1000256
MAX units configured as Foreign Agents in an ATMP environment were
resetting with message FE38. The problem has been corrected.
1000261
When direct routes (over serial/frame relay links) came up, the static
routes using that interface were not placed in the routing table. This
problem has been corrected.
1000277
E1 loopback was not operating correctly on a MAX 6000. The problem has been
corrected.
1000281
On MAX 6000 units in a stacked configuration, the Finger and Show Users
commands were showing entries for users even after channels were
disconnected. The problem has been corrected.
6000082
A problem resulting in occasional FE38 resets on a MAX 6000 has been
corrected.
6000088
MAX 6000 users were unable to access the network after a firewall
activation. The problem has been corrected.
6000125
A problem that resulted in a trailing zero being appended to the RADIUS
Acct-Session-ID record has been corrected. Now, if RADIUS accounting is
set to Ascend, the trailing zero appears; if set to vendor-specific, the
trailing zero does not appear.
6000134
When a B-channel was added to an AO/DI session and all traffic is switched
from the X.25 SVC (9600bps) to the B-channel (64kbps), the FTP transfer
involved in this process was taking too long. This problem has been corrected
6000152
A problem that resulted in L2TP accounting packets reporting inaccurate I/O
octets has been corrected.
6000160
A problem in a trial of AO/DI that resulted in a MAX unit rejecting all
X.25 SVC and B-channel connection attempts has been corrected.
6000169
On a MAX TNT, the first time a remote user connected, the subnet route was
not propagated to the peer OSPF neighbors. Only the host route was
propagated. Upon disconnection and reconnection, both routes were
propagated. The problem has been corrected.
6000248
A problem that resulted in connections over X.25 SVC to MAX units being
dropped during PPP negotiation, with subsequent connections being dropped
with RADIUS disconnect cause codes 45 and 49, has been corrected.
6000255
A problem with data transfer between two MAX units connected over IP with
X.25 has been corrected.
6000256
A problem that resulted in the help ascend command working inconsistently
has been corrected.
6000301
A problem occurred on Foreign Agent when a frame with a size near WAN mtu
is sent to the Mobile Client. The Foreign Agent starts to fragment IP
frames 14 bytes before WAN mtu limit. This problem has been corrected.
6000489
When Pool Summary is set to No and a WAN connection goes down, packets
being sent to the no-longer-existent pool address might result in local ARP
requests. To prevent this, private routing entries to the blackhole
interface bh0 are added for all local pool addresses. The entries have the
lowest preference (254) and the highest metric (15). This change results in
packets that are sent after the corresponding connection has gone down
being discarded until that IP address is used again.

NOTICE OF DISCONTINUANCE
Software support for v.34 slot cards--
Software support for V.34 modem slot cards will be phased out of new TAOS
code releases beginning with TAOS 7.1. The last TAOS release to contain
software support for V.34 slot cards for the MAX family is TAOS 7.0.

CONEXANT MODEM CODE
TAOS release 7.2.4 supports the following Conexant code versions:
Digital Modem Modules Conexant code version
K56 2.098
V.34 Modem-8 1.610G19
V.34 Modem-12 1.610G24
Conexant 2.084 firmware supports v.90, K56flex, K56plus, and all slower,
standard modem speeds.

KNOWN ISSUES
Issues you should be aware of before loading release 7.2.4 include the
following:
1. Change in Call-logging packet format
In releases prior to 7.2.0, the format of Call-logging packets are
identical to RADIUS Accounting packets. With the introduction of 7.2.0,
Call-logging will no longer be compatible with RADIUS, although Ascend's
NavisAccess product fully supports Call-logging. The MAX continues to
support RADIUS accounting, SNMP and SYSLOG functionality.
Because of the proprietary nature of and potential modification to
call-logging packets, you should not use call-logging packets with any
application other than Ascend's NavisAccess.
2. Some multimedia features are not supported in this release. Customers
using the following features should not upgrade to 7.2.4:
--AIM/BONDING
--Time-of-day calling
--Backup and overflow
3. The default value for the parameter CBCP Trunk group was out of the
valid range. The default value has been changed from 0 to 4. This
correction might cause a previously saved profile to yield a different
value when this release is loaded.
4. In MAX systems, data flows between T1/E1 WAN ports and host devices such
as modems and HDLC ports using a limited group of internal data pathways.
The capacity of these pathways is sufficient to accommodate the built-in
WAN ports of the MAX. When BRI cards are installed in the system, pathways
normally allocated for built-in T1/E1 ports are used to support the BRI WAN
ports, and are not available for T1/E1 usage.
TAOS 7.2.4 Release Notes has a table summarizing how the addition of BRI
cards affects the availability of built-in WAN ports in various MAX models.
These limits apply regardless of the type of BRI card used (Net, Host,
IDSL, etc.)



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