(ASCEND) 7.11.2 for Stinger

[Matt Holdrege <holdrege@lucent.com>]

The TAOS 7.11.2 software is now available from Customer Support and will be
released to Manufacturing. This release contains the following:

New features
------------
Modem firmware for DSL modems
SDSL auto rate support
New parameters for al-dmt-stat profile
Vendor ID added to G.DMt and G.Lite code
WAN access server
Copper Loop Test (CLT) Module
Stinger ADSL 24 Port LIM
STM-1/STS-3 support on Stinger
LIM redundancy
Add support to Stinger CM for 32M SIMMs
Management agent
Switching fabric detection and correction mechanisms
Cell payload scrambling
SNMP interface statistics for TMs and LIMs
SNMP management for LIM and trunk sparing
SNMP management for DS3 trunk module
Stinger alarm enhancements
New LED Alarm States
Log message for power supply failure
Atmvcc debug command change
Controller-redundancy debug command updated
Gabarit test command
Reset and Nvram command changes
Change to atm-options
Loadmate command
Update to load command
Change to atm-qos profile

Corrections
-----------
CLI command displayed wrong version of boot loader
Second group of 24 SDSL ports did not train
Control port auto logout caused fatal errors
The Alarm Led on the DS3 TM was never lit during boot up
The DS3ATMStat profiles displayed "bad value" for the VPI-VCI-Range parameter
DS3 port bypass did not switch back to main trunk
OC3 TMs would not come back up after being hot swapped.
No alarm log generated when the redundant CM goes out of service.
Stinger did not send out yellow alarm signal to remote device when it had a 
red
alarm and loss of frame conditions.
The Ls command indicated flash cards 3 and 4 were not inserted, even though 
the
Stinger only supports two cards.
CM crashed with a Fatal Error 40 if the OAM -l command, or the OAMLoop command
were run on a non-existent VC.
Save -m option incorrectly reported VPI-VCI-Range parameter in saved
configuration file.
Desired-State parameter setting did not match setting configured in the
AL-DMT-Stat profile
Erroneous fan failure alarm messages
ifOperStatus in RFC2233 Interface table was not set correctly for OC3 trunk
SNMP reported two control modules in chassis even though only one was present
SNMP erroneously reported Ethernet interface down
Clocking from the trunk module did not work
The Stinger would reset with a fatal error 40 whenever an active OC3 trunk
connected to a
Lucent DSL Terminator was disconnected
ifOperStatus in RFC2233 Interface table was not set correctly for DS3 trunk
The Show command displayed a DS3 TM in slot 18 even though an OC3 Tm was
installed
The Show command displayed the DS3 and OC3 trunk modules as Down after they 
were removed from the Stinger unit, instead of not displaying them at all
ADSL ports 13-24 did not pass traffic
OC3-ATM-Stat not deleted when OC3 TM is removed
The routing table on the secondary CM was not updated until a reboot
DS3 TM did not generate a yellow alarm when it received a blue alarm (AIS)
After a reset, a VCC using VPI 0 could not be established
Major and minor alarm relays not turned off after specified duration
Alarm relay duration of 0 (zero) not operating properly
SNMP did not report the TM slots in the Slot Table in the Chassis MIB
The Slot Table would lose information after a switchover to a secondary
controller
OC3 ATM trunk loopback did not work
The flashDeviceDescription object was misread
An ATM trunk-to-trunk connection failed to come up if both DS3-ATM profiles 
and
OC3-ATM profiles existed in a Stinger that only had OC3-ATM trunk cards
installed
ATM-Config profile displayed bad value for slots 8 and 9
SNMP ifTable not supported for non-physical ATM connections
SNMP reported SDSL LIM ifEntry as 0 (zero) even when the interface was up and
passing data
Show command from secondary controller did not show slot status
The sysDescription object changed from Ascend Stinger-10 to Lucent 
Stinger-10 50
The Uptime command online help changed from TNT to Stinger
Cannot load tar file to PCMIA card over serial link
Defective Stinger Ripper OAM feature
Stinger Ripper nrtVBR and UBR QoS problem
Line alarm on trunk module not cleared when line is up and module is 
re-inserted
LIM-to-LIM and LIM-to-trunk ATM circuits do not come up after setting NVRAM
configuration to factory default
Resetting all 12 ports or disconnecting telco cable causes ADSL 12 port LIM to
reset
HDSL2 modem trains intermittently
Downgrade can cause memory or nvram corruption
ETHER-INFO profile not reporting information correctly
The atm-qos statistic in the atmvcc command does not always display correctly
BANDWIDTH-CONFIG parameter in ATM-CONFIG profile does not show the proper range
Fix QoS problem on ADSL 24 port LIMs
Downstream performance problem for Stinger 24 port ADSL LIM
Warning message for ATMVCC command not issued if debug is turned off
Cannot load TAR files over serial link
Line state change alarms were not detected if alarm profile configuration 
had an entry for a specific slot
Alarm profile does not support physical address where shelf = "any"

OC3/DS3 line down alarms not being generated for trunk lines disabled
administratively
Under a heavy load of polling by SNMP manager, Stinger reboots
Active non-physical ATM sessions are shown with IFDescr = Unknown in ifTable
Circuit manager cannot bring up the second leg of an HDSL2 LIM to LIM 
connection
New counters in al-dmt-stat do not increment correctly and are mislabeled
Bert test on several ports of SDSL LIM fails
Resetting port on 12 port ADSL LIM sometimes causes ports on long loops to go
down
A memory leak that occured when SNMP was polling has been corrected
Problem with decompressing a tar file loaded over the serial link was corrected
Port sparing when activated on a specific port and then disabled would cause
mid-plane bus to be always locked
Unable to open a session on the redundant controller slot
Loop timing parameter on oc3-atm trunk module profile does not work
A 24 port ADSL LIM takes 2 loading cycles to boot up
System-8k-clock = trunk setting causes synchronization failure on SDSL LIMs
IP address in route entry for SDSL LIM is reported in reverse order
Copper Loop Test (CLT) module calibration and send tone commands fail.
LIM port fails to retrain the presence of excessive CRC errors

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