Stinger True Access® Operating System (TAOS) 9.9.1 Release Note
Part number: 363-217-006R9.9.1 Revision 1 For software version 9.9.1 Release date: August 09, 2006 Copyright © 2006 Lucent Technologies Inc. All rights reserved.
This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or licensing, without the express written consent of Lucent Technologies. For permission to reproduce or distribute, please email your request to [email protected].
Notice
Every effort was made to ensure that the information in this document was complete and accurate at the time of printing, but information is subject to change. For latest information, refer to online product documentation at www.lucent.com/support.
European Community (EC) RTTE compliance
Hereby, Lucent Technologies, declares that the equipment documented in this publication is in compliance with the essential require- ments and other relevant provisions of the Radio and Telecommunications Technical Equipment (RTTE) Directive 1999/5/EC. To view the official Declaration of Conformity certificate for this equipment, according to EN 45014, access the Lucent INS online documentation library at http://www.lucentdocs.com/ins.
Safety, compliance, and warranty information
Before handling any Lucent Access Networks hardware product, read the Edge Access and Broadband Access Safety and Compliance Guide included in your product package. See that guide also to determine how products comply with the electromagnetic interference (EMI) and network compatibility requirements of your country. See the warranty card included in your product package for the limited warranty that Lucent Technologies provides for its products.
Security statement
In rare instances, unauthorized individuals make connections to the telecommunications network through the use of access features.
Trademarks
Lucent, the Lucent logo, and all Lucent brand and product names are trademarks or registered trademarks of Lucent Technologies Inc. Other brand and product names are trademarks of their respective holders.
Ordering information
You can order the most up-to-date product information and computer-based training online at http://www.lucentdocs.com/bookstore.
Feedback
Lucent Technologies appreciates customer comments about this manual. Please send them to [email protected].
Lucent Technologies Customer Service Product and service information, and software upgrades, are available 24 hours a day. Technical assistance options accommodate varying levels of urgency.
Finding information and software To obtain software upgrades, release notes, and addenda for this product, log in to Lucent OnLine Customer Support at http://www.lucent.com/support.
Lucent OnLine Customer Support also provides technical information, product information, and descriptions of available services. The center is open 24 hours a day, seven days a week. Log in and select a service.
Obtaining technical assistance Lucent OnLine Customer Support at http://www.lucent.com/support provides easy access to technical support. You can obtain technical assistance through email or the Internet, or by telephone. If you need assistance, make sure that you have the following information available: ■ Active service or maintenance contract number, entitlement ID, or site ID ■ Product name, model, and serial number ■ Software version or release number ■ Software and hardware options ■ If supplied by your carrier, service profile identifiers (SPIDs) associated with your line ■ Whether you are routing or bridging with your Lucent product ■ Type of computer you are using ■ Description of the problem
Obtaining assistance through email or the Internet
If your services agreement allows, you can communicate directly with a technical engineer through Email Technical Support or a Live Chat. Select one of these sites when you log in to http://www.lucent.com/support.
Calling the technical assistance center (TAC)
If you cannot find an answer through the tools and information of Lucent OnLine Customer Support or if you have a very urgent need, contact TAC. Access Lucent OnLine Customer Support at http://www.lucent.com/support and click Contact Us for a list of telephone numbers inside and outside the United States.
From any location in North America, call 1-866-LUCENT8 (1-866-582-3688) for a menu of Lucent services or call +1 510-747-2000 for an operator. For the EMEA region, you can reach the call center at +353 16924579. If you do not have an active services agreement or contract, you will be charged for time and materials.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note iii
Contents
Section 1 Upgrading to this release...... 1-11-1
Before you begin ...... 1-1 TFTP server requirement ...... 1-1 Upgrade paths to this software release ...... 1-1 Saving system configuration...... 1-2 Upgrading a Compact Remote IP DSLAM system (hosted) ...... 1-3 Boot loader files, tar files and binaries...... 1-3 Preparing the host and remote shelves for the upgrade...... 1-3 Loading TAOS software onto the host Stinger FS+ unit...... 1-4 Adding a Compact Remote unit to the Stinger host...... 1-4 Storing hosted system configuration ...... 1-6 Diagnostics ...... 1-7 Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units ...... 1-9 Boot loader files, tar files and binaries...... 1-9 Upgrading software for Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, or Stinger RT units (hosted Stinger systems) ...... 1-11 Downgrading to an earlier software version ...... 1-13 Upgrading software for Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units (standalone units)...... 1-14 Upgrading and downgrading standalone Compact Remote units...... 1-15 Compact remote boot loader file, tar file, and related binaries ...... 1-15 Upgrading a standalone Compact Remote unit ...... 1-15
Section 2 TAOS 9.9.1 ...... 2-12-1
About this release ...... 2-1 ATM G.Bond Support for ADSLx LIM ...... 2-1 Advantages ...... 2-2 Overview ...... 2-22-2 GbondLines command...... 2-9 GbondGroups command...... 2-9 Configuring groups, lines and connections ...... 2-10 VDSL2 Features and SELT DELT BIST Support for Ikanos LIMs ...... 2-11 SELT DELT BIST support for Ikanos LIMs ...... 2-16 Upgrade of Ikanos DSP+API code...... 2-17 Support for PPPoA over LLC ...... 2-17 Verifying the encapsulation type ...... 2-17 New Version of Stinger Compact Remote...... 2-18 MS+IP, new version of MS+ ...... 2-19 Support for G24V and Enhanced Impulse Noise Protection ...... 2-19
v Overview ...... 2-192-19 Prerequisite for enhanced INP ...... 2-20 Supported LIMs ...... 2-20 User interface changes ...... 2-20 Provisioning the LIM ...... 2-21 Support for SELT on VDSL LIM ...... 2-21 Minor changes related to SELT on Ikanos board...... 2-21 VDSL-Config subprofile in this release...... 2-22 VDSL2 support...... 2-22 Support for ECMP on IP2100...... 2-22 Selectable Line Code for G24 Based Conexant LIMs ...... 2-22 Background...... 2-22 bit-map parameter ...... 2-23 line-code-config subprofile ...... 2-23 Example ...... 2-25 Support for SNRM per bin in A2P card...... 2-26 Overview...... 2-26 Firmware in this release ...... 2-27
Section 3 Change requests fulfilled in this release...... 3-13-1
Section 4 System capacity in TAOS 9.9.1 ...... 4-14-1
Stinger Compact Remote IP DSLAM throughput ...... 4-1 Stinger IP2100 throughput ...... 4-1 Stinger IP2100 capacity...... 4-2 Stinger IP2000 capacity...... 4-2 Maximum number of PVCs per device ...... 4-3 VCC Capacity...... 4-3
Section 5 Notices, known issues and limitations ...... 5-15-1
Notices in TAOS 9.9.1 ...... 5-1 Compact Remote IP DSLAM boot ROM requirements ...... 5-1 IP2100 boot ROM and PSB requirements...... 5-2 High-bandwidth LIM requirements ...... 5-3 Control module support in Stinger TAOS releases...... 5-3 Clarification about support for STGRRT-CM-A control modules with 64MB ...... 5-45-4 Control module compatibility in redundant systems...... 5-5 NavisAccess™ support for Stinger software releases...... 5-5 Known issues and limitations...... 5-6 Known Compact Remote IP DSLAM issues and limitations ...... 5-6 Known issues with Stinger Compact Remote ATM units ...... 5-8 IP control modules ...... 5-8 IP2100 system known issues and limitations ...... 5-9 IP2000 system known issues and limitations ...... 5-12 ATM limitations ...... 5-13 Stinger MRT units ...... 5-13 Known issues and limitations with LIMs and trunk modules ...... 5-13 Known VDSL LIM issues ...... 5-13 ADSL LIM limitations ...... 5-14 vi 48-port and 72-port SHDSL LIM limitations ...... 5-15 T1 IMA LIM limitation...... 5-15 Command-line interface limitations ...... 5-15 Copper loop testing limitation...... 5-16 Known issues and limitations with SNMP ...... 5-16 Known issues and limitations with PPPoA over LLC...... 5-16 Known issues and limitations with G.Bonding...... 5-17 Known issues and limitations with PPPoE calls ...... 5-17 Known issues and limitations with traffic flow on ports ...... 5-18 Known issues related to RADIUS support...... 5-18 Known issues related to SELT on VDSL LIM ...... 5-19 Known issues related to ADSL/ADSL2+ ...... 5-19 Known issues related to VDSL2 ...... 5-19 End of sale for Stinger products ...... 5-19
vii viii Upgrading to this release 1
Before you begin ...... 1-1 1-1
Upgrading a Compact Remote IP DSLAM system (hosted) ...... 1-3 1-3
Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units ...... 1-9 1-9
Upgrading a standalone Compact Remote unit ...... 1-15 1-15
Before you begin Note Be aware that upgrading or downgrading software is a service affecting activity.
Read the notices and known issues described in “Notices, known issues and limitations” on page 5-1 before upgrading to this release.
TFTP server requirement
Caution In this release the size of stgiprel.tar exceeds 32MB. Before upgrading to this release, verify that your TFTP server supports file sizes greater than 32MB.
The following TFTF servers support file sizes greater than 32MB: ■ For Windows:Tftpd32 version 2.0 upwards, available at http://tftpd32.jounin.net/ ■ For UNIX: Tftp-hpa series, available at http://www.kernel.org/pub/software/network/tftp/ NavisAccess® DSL management software version 9.2 and later releases support TFTP of files greater than 32MB.
Upgrade paths to this software release If your unit is running one of the following software versions, you can upgrade directly to TAOS 9.9.1: ■ 9.9.0 ■ 9.8.2, 9.8.1, 9.8.0 ■ 9.7.4, 9.7.3, 9.7.2, 9.7.1, 9.7.0 ■ 9.6.1, 9.6.0
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 1-1 Upgrading to this release Before you begin
■ 9.5-206.2, 9.5-206.1 ■ 9.4-185.5 ■ 9.3-170.4, 9.3-170.3 If you are upgrading from a software version that is not in the preceding list, the upgrade to TAOS 9.9.1 might be a two-stage process. First, upgrade to a software version listed above. Then, upgrade from the intermediate software version to TAOS 9.9.1 software.
Saving system configuration As a general practice, Lucent Technologies recommends that you always save the system configuration before upgrading, downgrading, or reloading system software. You can then restore the configuration along with the system software if anything unexpected occurs. Note You can optionally load only specific module images during the upgrade process. TAOS includes a load-select profile that prevents the system from loading the entire set of module images. You can also use the load command to load only specific images. For more information about loading only specific images, see the Stinger Administration Guide.
Saving the system configuration using a TFTP server Before you save the system configuration, enable the allow-password permission in your Stinger user profile. The system requires this permission to save the configured passwords. If you do not have allow-password permission enabled, you are prompted to confirm that you wish to save the configuration without passwords. If you do so and then restore the saved configuration, all passwords in the configuration are deleted. The following command entered on the Stinger unit saves the system’s configuration to the target file testcfg.1 on the TFTP server. Replace IPaddress with the IP address of your TFTP server: admin> save -a network IPaddress testcfg.1
Saving configuration information to the default.cfg file The upgrade and downgrade procedures require that you clear your system’s nonvolatile RAM (NVRAM) of its configured settings (including its IP address) using the nvram command. On systems running TAOS 9.2-167 or later releases, you can save basic system settings to a default.cfg file, which will allow the system to start up with its IP address and other basic configuration that you would like to be restored for your system after an nvram command. For information about how to save to the default.cfg file, see the Stinger Administration Guide. If after the nvram command your system's IP address is not restored, log into the primary control module via the serial connection. Open the ip-interface profile for the shelf controller and set the address. For example: admin> read ip-int {{ 1 8 1 }0} admin> set ip-address = IPaddress admin> write
1-2 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Upgrading to this release Upgrading a Compact Remote IP DSLAM system (hosted)
Upgrading a Compact Remote IP DSLAM system (hosted) The following instructions describe how to load the TAOS 9.9.1 software to support a hosted Compact Remote IP DLAM system. You will perform the following tasks: ■ Load TAOS software onto the host Stinger FS+ unit. ■ Add Compact Remote units to the host Stinger FS+ unit. Note Be aware that upgrading or downgrading software is a service affecting activity.
Read the notices and known issues described in “Notices, known issues and limitations” on page 5-1 before upgrading to this release.
Boot loader files, tar files and binaries Table 1-1 lists the boot-loader files and tar files that you will need to load TAOS 9.9.1 software.
Table 1-1. Boot-loader and tar files for Stinger FS+ units
File name Description
stgcmb21.bin Boot-loader file for IP2100 Stinger system (the Stinger FS+ host).
gecrtcmb.bin Boot-loader file for the GE-COP (Compact Remote shelves).
stgiprel.tar Tar file for Stinger FS+ host containing images for the IP2100, GE-COP, ADSL2+ RLIM, and GE-GOLIM.
Table 1-2 lists the relevant binaries for loading TAOS 9.9.1 software contained in stgiprel.tar and their approximate file sizes.
Table 1-2. Binaries in stgiprel.tar
Binary filename Device Approximate size (bytes)
stngrcm21.ffs IP2100 control module and all trunk 6159177 modules
stngrgolim.ffs GE-OLIM 2835594
gecrtcm.ffs GE-COP 3296911
stngrgebgsdmt.ffs GE ADSL2+ RLIM 2602548
Preparing the host and remote shelves for the upgrade 1 Configure the Stinger FS+ as the host. For example: admin> read system
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 1-3 Upgrading to this release Upgrading a Compact Remote IP DSLAM system (hosted)
admin> set shelf-controller-type = master admin> write 2 By default, the remote shelves are configured to operate in slave mode. To ensure that GE-COPs on the remote shelves are in slave mode, clear the NVRAM on the remote shelves. 3 Reset the host Stinger FS+ unit. This step is required. For example: admin> reset
Loading TAOS software onto the host Stinger FS+ unit 1 Load the boot loader for the IP2100 control module. For example: admin> load boot-cm network IPaddress stgcmb21.bin 2 Load the new tar file onto the primary control module. For example: admin> load tar network IPaddress stgiprel.tar 3 Load the boot-loader file for the GE-COP (Compact Remote shelves). For example: admin> load file network IPaddress gecrtcmb.bin 4 Save your unit’s IP address to the default.cfg file. See “Saving configuration information to the default.cfg file” on page 1-2. 5 Clear all profiles by entering the nvram command. admin> nvram After the nvram command, your system's IP address should have been restored. If an unexpected error occurs and you must restore your system IP address, see “Saving configuration information to the default.cfg file” on page 1-2. 6 Configure the Stinger FS+ as the host. For example: admin> read system admin> set shelf-controller-type = master admin> write 7 Load the saved backup configuration. admin> load config network IPaddress config/backup-config 8 Reset the system. This step is required. For example: admin> reset
Adding a Compact Remote unit to the Stinger host The following procedure shows how to add Compact Remote units to the host Stinger FS+ unit. You must have already completed the steps described in “Preparing the host and remote shelves for the upgrade” on page 1-3 and installed software on
1-4 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Upgrading to this release Upgrading a Compact Remote IP DSLAM system (hosted)
the Stinger host as described in the section “Loading TAOS software onto the host Stinger FS+ unit” on page 1-4. Enter the following commands on the host Stinger unit. 1 Use the ls command to verify that the necessary GE-OLIM, GE-COP, and GE ADSL2+ RLIM images (.ffs files) and Compact Remote bin loader file and are present on the Stinger host flash card. The following files must be present: – stngrgolim.ffs – gecrtcm.ffs – stngrgebgsdmt.ffs – gecrtcmb.bin – stngrcm21.ffs 2 Wait for the host Stinger unit to initialize, and then verify that the host Stinger unit recognizes the OLIM and that the GE-OLIM is active. For example: admin> show Shelf 1 ( master ): Controller { first-control-module } ( PRIMARY ): Reqd Oper Slot Type { shelf-1 slot-5 0 } UP UP stngr-golim-card { shelf-1 trunk-module-2 0 } UP UP oc3-atm-trunk-daughter-card The status of GE-OLIM should be UP (that is, the Oper field must show UP). If this is not the case, reset the GE-OLIM by entering the slot -b slot-number command (replace slot-number with the slot number of the GE-OLIM).
Note For information about Stinger Compact IP DSLAM physical connectivity, see the Stinger Compact Remote IP DSLAM Getting Started Guide.
3 Enable the ethernet profile of the GE-OLIM for the port to which the GE-COP is connected. In the following example, it is port {1 5 1}: admin> read ethernet {1 5 1} admin> set enabled = yes admin> write 4 Create the remote-shelf-config profile for the Compact Remote unit on the host Stinger unit. In this example, the Compact Remote is designated as shelf 10. Assign a GE-OLIM port on host Stinger for the Compact Remote—shelf 1, slot 5, port 1, in the following example. admin> new remote-shelf-config 10 admin> set host-port = {{1 5 1}} admin> set enabled = yes admin> write Wait approximately 5 minutes for the GE-COP to initialize. The GE-COP will boot up first, followed by RLIM. 5 Repeat step 4 for each remote shelf. 6 Save the ethernet profile and the remote-shelf-config profiles to the default.cfg file.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 1-5 Upgrading to this release Upgrading a Compact Remote IP DSLAM system (hosted)
7 Enter the itp -s debug command to show the files being downloaded by the remote from host. For example: admin> itp -s Time: 435382 ticks. SH/SL fd State VS VR VA Frag Total LastEvnt Cond Cmd Ctrl Tload TFdata TDcmp Loading 1/ 5 0 idle 0 0 0 9459 9459 ExecR (none) 1 3300 9725 2020 7461 0 0 10/ 2 0 idle 0 0 0 8464 8464 ExecR (none) 1 3300 11137 5175 5771 0 0 10/ 8 0 idle 0 0 0 1 1 ExecR (none) 1 3300 2 0 0 0 0 In the preceding output, 10/2 is the RLIM and 10/8 is GE-COP (remote shelf). 8 Verify that the Stinger host recognizes the Compact Remote components, as shown in the following sample output: admin> show Shelf 1 ( master ): Controller { first-control-module } ( PRIMARY ): Reqd Oper Slot Type { shelf-1 slot-5 0 } UP UP stngr-golim-card { shelf-10 slot-2 0 } UP UP geb-gs-adsl2plus-card { shelf-10 first-control-mo+ UP UP gecrt-cm 9 Reset the remote shelf by entering the reset -s shelf-id command on the host. Replace shelf-id with the shelf ID number of the remote shelf. For example: admin> reset -s 10 Reset remote slave controller 10 ? [y/n] y Note During the upgrade procedure, the system will generate the following sample log error message as each remote shelf is installed with TAOS 9.9.1.
LOG error, Shelf 1, Controller-1, Time: 10:09:25-- ../ms.c:2373 - slot type missing from shelf-16! LOG error, Shelf 1, Controller-1, Time: 10:09:26-- ../ms.c:2373 - slot type missing from shelf-16! ... The system generates these harmless messages when the controller and the GE-COPs have temporarily mismatched software versions.
Storing hosted system configuration After loading TAOS 9.9.1 software and configuring the Compact Remote IP DSLAM for hosted operations, to ensure that the system can recover and operate in a hosted environment in case of an unexpected event, consider storing certain profiles to the default.cfg file. To enable the system to recover and operate in a hosted environment, use the save command to store the following files the default.cfg file: ■ ethernet profiles ■ remote-shelf-config profiles For more information about using the default.cfg file, see the Stinger Administration Guide.
1-6 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Upgrading to this release Upgrading a Compact Remote IP DSLAM system (hosted)
Diagnostics The following are useful tools for diagnosing operations after the upgrade procedure.
Verifying the status of the MS link between the GE-OLIM and the GE-COPs To verify the MS link status between the GE-OLIM and the GE-COPs, enter the msstat command from the host. For example: admin> msstat SH/SL State TxQs TxSeq# RxSeq# ReXmit ReAck TxNak RxNak Timer LinkUp 1/ 9 2 0 0 0 0 0 0 0 2 0 2/ 8 4 0 19112 25281 0 0 0 0 0 1 7/ 8 4 0 59808 1260 0 0 0 0 0 2 If the State column shows 4, the MS link is active.
Displaying statistics on the GE-OLIM To display statistics on the GE-OLIM, use the stats traffic ether command to display traffic on the backplane. For example: slot-1/1> stats traffic ether Port Rx Pkts Tx Pkts Rx Mcs Tx Mcs Rx Bytes Tx Bytes 1 85769 85823 0 0 6297410 8210459
Verifying physical connectivity on the GE-COP If the MS link is up (see “Verifying the status of the MS link between the GE-OLIM and the GE-COPs” on page 1-7), you should be able to access the GE-COP from the host Stinger FS+ unit. Open a session with the GE-COP. In the following example, the GE-COP is in shelf 2, slot 8: admin> open 2 8 shelf-router-2/8>
Verifying traffic on the RLIM To verify data traffic through a particular connection, proceed as follows: admin> open 2 2 geb-gs-dmt-48-2/2> ifmgr -d sif slot bif u m p ifname host-name remote-addr local-addr ------000 0:00 000 * pb0 - 0.0.0.0/32 0.0.0.0/32 001 1:08 029 * wan1 ppp-ckt 0.0.0.0/32 0.0.0.0/32
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 1-7 Upgrading to this release Upgrading a Compact Remote IP DSLAM system (hosted)
MTU : 1610 WINPATH ATM INFO : rx Utopia Port : 0 rx Utopia Address : 0 rx Utopia VPI : 8 rx Utopia VCI : 35 tx Utopia Port : 0 tx Utopia Address : 0 tx Utopia VPI : 8 tx Utopia VCI : 35 ATM Encap Type : LLC PPPoE IW Mode : IW MODE ROUTING qosType : 3 pcr : 0 scr : 0 mbs : 8 cdvt : 1 VLAN INFO vlan id : 0 VLAN INFO acceptTagged : 0 VLAN INFO acceptUnTagged: 1 atmChannel : 21 etherInfo IWMode : IW MODE BRIDGING VLAN INFO vlan id : 0 VLAN INFO acceptTagged : FALSE VLAN INFO acceptUnTagged: FALSE Ether-QosInfo packetrate: 0
The ATM channel for this connection is 21. Note that the ATM channel for PPP calls is 21 and will have to be verified on the ATM-circuit.
Use the following commands to display traffic information on this connection (29). First, enable the system to monitoring statistics. For example: geb-gs-dmt-48-2/2> stats enable aal5 all Statistics collection enabled : connection 3 Statistics collection enabled : connection 21
Then, display traffic statistics for ATM channel 21. For example: geb-gs-dmt-48-2/2> stats traffic aal5 21 Rx frames : 0 Tx frames : 0 Aborted frames : 0 CLP frames : 0 L3 Iw Frames : 0 Rx CLP0 Cells : 0 Rx CLP1 Cells : 0
Note The LEDs on the GE-OLIM, GE-COP, and RLIMs are not working as required.
1-8 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Upgrading to this release Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units
Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units This section describes procedures for upgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ to TAOS 9.9.1 software and downgrading from TAOS 9.9.1 to a previous software release.
Boot loader files, tar files and binaries Table 1-3 lists the boot-loader files and tar files that you use to upgrade your Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ unit to this release. You must always install the proper new boot loader when upgrading or downgrading.
Table 1-3. Boot-loader and tar files for Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units
File name Description
stgcmb.bin Boot-loader file for Stinger LS and Stinger FS units with revision 1 control modules.
stg1rel.tar Tar file for Stinger units with CM-v1 control modules. Includes LIM binaries.
Note Not supported beyond 9.7.x releases
stgcmb2.bin Boot-loader file for Stinger LS, Stinger FS, Stinger FS+, Stinger RT, and Stinger MS+ units with revision 2-or-higher control modules.
stgrel.tar Tar file for Stinger units installed with CM-v2, CM-v2.1, and IP2000 control modules and LIM images.
stgcmb21.bin Boot-loader file for systems with an IP2100 control module.
stgiprel.tar Tar file for systems with an IP2100 control module. Includes binaries for control modules and LIMs.
Note You can verify the type of control module installed in a Stinger system by using the revision command.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 1-9 Upgrading to this release Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units
Table 1-4 lists the software images (binaries) contained in stgrel.tar and stg1rel.tar their approximate file sizes. The binaries for the trunk modules are loaded with the control modules.
Table 1-4. Binaries in stgrel.tar and stg1rel.tar in this TAOS 9.9.1
Device Filename Approximate size (bytes)
Stinger Compact Remote control and optics pack (COP) crtcm.ffs 3816804
Revision 1 control module and all trunk modules stngrcm.ffs 5027998 (Not present in Note Not supported beyond 9.7.x releases stgrel.tar)
Revision 2-or-higher control module, IP2000 control module stngrcm2.ffs 5782551 and all trunk modules (Not present in stg1rel.tar)
24-port ADSL LIM stngrral24dsl.ffs 1213738
32-port single-pair high-speed digital subscriber line stngrhdsl2.ffs 1,186 KB (SHDSL)/HDSL version 2 (HDSL2) LIM
72-port ADSL Centillium LIM stngrctdmt72.ffs 1343883
48-port ADSL Annex A and Annex C LIMs stngrdmt48.ffs 1150758
48-port ADSL Annex B LIM. stngrdmt48b.ffs 1152217
72-port ADSL Globespan LIM stngrgsdmt.ffs 1636362 48-port low-power ADSL LIM 72-port ADSL2/ADSL+/ADSL2+
Enhanced 72-port ADSL/ADSL2+ LIM stngrwgsdmt.ffs 2523774
48-port and 72-port Annex A LIMs with ADSL2+ capability stngrhsdmt.ffs 2759825 (high-bandwidth LIM)
48-port ADSL G.lite LIM stngrgltdsl.ffs 1146082
T1 and E1 modules stngrima.ffs 931544
Optical line interface module (OLIM) stngolim.ffs 826294
48-port SDSL-v2 LIM stngrrsdsl.ffs 1164891
48-port SHDSL LIM and 72-port SHDSL LIM stngrshdsl.ffs 1320998
48-port SHDSL LIM with IMA stngrishdsl.ffs 2421919
T1000 module stngrt1000.ffs 1367416
1-10 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Upgrading to this release Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units
Table 1-4. Binaries in stgrel.tar and stg1rel.tar in this TAOS 9.9.1 (Continued)
Device Filename Approximate size (bytes)
Fast Ethernet trunk module stngrfet.ffs 1145520
24-port VDSL LIM stngrwikvdsl24.ffs 2677064
Upgrading software for Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, or Stinger RT units (hosted Stinger systems) The following upgrade instructions are for upgrading a Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, or Stinger RT unit to support a hosted Compact Remote unit (a hosted system). You will perform the following tasks: ■ Upgrade the host Stinger unit to this release. ■ Add Compact Remote units to the host Stinger unit.
Upgrading the host Stinger unit
1 Save the Stinger unit system configuration. See “Before you begin” on page 1-1. 2 Modify the load-select profile to force the system to load the following required images from the tar file. admin> read load-select admin> set olim = load admin> set crtcm = load admin> set 72-gs-dmt-adsl = load admin> write 3 Load the appropriate boot loader for your control module. – If your Stinger unit has a revision 1 control module, use the stgcmb.bin boot loader. admin> load boot-cm network IPaddress stgcmb.bin – If your Stinger unit has a revision 2-or-higher control module, use the stgcmb2.bin boot loader. admin> load boot-cm network IPaddress stgcmb2.bin 4 Load the new tar file onto the primary control module. admin> load tar network IPaddress stgrel.tar If you must clear your system’s NVRAM, perform step 5 through step 7. Otherwise, proceed to step 8. 5 Save your unit’s IP address to the default.cfg file. See “Saving configuration information to the default.cfg file” on page 1-2. 6 Clear all profiles by entering the nvram command. admin> nvram
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 1-11 Upgrading to this release Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units
After the nvram command, your system's IP address should have been restored. If an unexpected error occurs and you must restore your system IP address, see “Saving configuration information to the default.cfg file” on page 1-2. 7 Load the backup configuration that you saved in step 1. admin> load config network IPaddress config/backup-config 8 Reset the system. This step is required. admin> reset
Adding a Compact Remote unit to the Stinger host
The following procedure adds a Compact Remote unit to the Stinger host unit. You must have already installed software on the Stinger host. (See “Upgrading the host Stinger unit” on page 1-11.) Enter the following commands on the host Stinger unit. 1 Use the ls command to verify that the OLIM, COP, and LIM images (.ffs files) are present on the Stinger host flash card. For a listing of binary files, see Table 1-4. 2 Configure the host Stinger system as the host. (Note that on the Compact Remote unit, the system:shelf-controller-type parameter is set to slave by default). For example: admin> read system admin> set shelf-controller-type = master admin> write 3 Reset the host Stinger unit. This step is required. admin> reset Reboot the entire system, dropping all connections? [y/n] y Rebooting only the primary controller, Secondary is not available Please stand by. System reset in progress... 4 Wait for the host Stinger unit to initialize, then install the OLIM onto the Stinger host. Wait for the host Stinger unit to complete initialization, and then verify that the host Stinger unit recognizes the OLIM. For example: admin> show Shelf 1 ( master ): Controller { first-control-module } ( PRIMARY ): Reqd Oper Slot Type { shelf-1 slot-4 0 } UP UP stngr-olim-card { shelf-1 trunk-module-1 0 } UP UP oc3-atm-trunk-daughter-card 5 Connect the OLIM on the Stinger host to the COP on the Compact Remote using an OC3 cable. (See the Stinger Compact Remote Installation and Configuration Guide for instructions.) 6 Create the remote-shelf-config profile for the Compact Remote unit on the host Stinger unit (the Compact Remote is designated as shelf 8). Valid shelf numbers are 2 through 56. Assign an OLIM port on host Stinger for the Compact Remote—shelf 1, slot 4, port 6, in this example. admin> new remote-shelf-config 8 admin> set host-port = {{ 1 4 6 } 0} admin> set enabled = yes admin> write
1-12 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Upgrading to this release Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units
7 Wait approximately 5 minutes for the COP to initialize. Verify that the Stinger host recognizes the Compact Remote components, shown in bold in the following sample output: admin> show Shelf 1 ( master ): Controller { first-control-module } ( PRIMARY ): Reqd Oper Slot Type { shelf-1 slot-4 0 } UP UP stngr-olim-card { shelf-1 trunk-module-1 0 } UP UP oc3-atm-trunk-daughter-card { shelf-8 slot-3 0 } UP UP stngr-48-gs-adsl-card { shelf-8 first-control-mod+ UP UP cm-v2
Downgrading to an earlier software version Because releases are not necessarily backward compatible, Lucent recommends that you always restore a backup configuration made under the previous version. If you are running TAOS 9.9.1, to restore a previous software version, proceed as follows: 1 Load the previous version of the boot loader. For example: admin> load boot-cm network IPaddress stgcmb.bin 2 Format the flash card(s) on the control module(s). For example, from the primary control module, enter the following commands: admin> format flash-card-1 admin> format flash-card-2 On a redundant system, telnet to the secondary control module and format the flash card(s) on the secondary control module. 3 Load the previous version of the tar file. admin> load tar network IPaddress stgrel.tar 4 Save your unit’s IP address to the default.cfg file. See “Saving configuration information to the default.cfg file” on page 1-2. 5 Clear all profiles by entering the nvram command. admin> nvram After the nvram command, your system's IP address should have been restored. If an unexpected error occurs and you must restore your system IP address, see “Saving configuration information to the default.cfg file” on page 1-2. 6 Load a backup configuration made under the restored software version or one of its predecessors. For example: admin> load config network IPaddress config/backup-config 7 Reset the system. This step is required. For example: admin> reset
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 1-13 Upgrading to this release Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units
Upgrading software for Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units (standalone units) This section describes upgrade procedures for standalone Stinger units. If your have a redundant system with revision 2-or-higher control modules installed, follow the upgrade procedure described in “Upgrading and Downgrading Stinger FS, Stinger FS+, Stinger LS, Stinger LS+, Stinger RT, or Stinger MS+ units” on page 1-9.
Upgrading a unit with a single control module or a redundant system with the same revision control modules
Note If your unit has redundant control modules, you must upgrade both control modules to the same software version.
To upgrade a unit with a single control module or a redundant system with the same revision control modules, proceed as follows: 1 Save the system configuration. For instructions, see “Saving the system configuration using a TFTP server” on page 1-2. 2 Load the appropriate boot loader for your control module. – If your Stinger unit has a revision 1 control module, use the stgcmb.bin boot loader. For example: admin> load boot-cm network IPaddress stgcmb.bin – If your Stinger unit has a revision 2-or-higher control module, use the stgcmb2.bin boot loader. For example: admin> load boot-cm network IPaddress stgcmb2.bin 3 Load the new tar file onto the primary control module. For example: admin> load tar network IPaddress stgrel.tar 4 If your system has a single control module, proceed to step 5. On a redundant system, depending on the software version that your unit is running, the system automatically copies software images from the primary to the secondary control module.
Verify that the appropriate images (.ffs files) are on the flash card of your secondary control module. If an unexpected error occurs and you must load the boot-loader and tar files for the secondary control module, telnet to the secondary control module and repeat step 2 and step 3 for the secondary control module. 5 Save your unit’s IP address to the default.cfg file. See “Saving configuration information to the default.cfg file” on page 1-2. 6 Clear all profiles by entering the nvram command. admin> nvram After the nvram command, your system's IP address should have been restored. If an unexpected error occurs and you must restore your system IP address, see “Saving configuration information to the default.cfg file” on page 1-2. 7 Load the backup configuration that you saved in step 1. For example: admin> load config network IPaddress config/backup-config
1-14 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Upgrading to this release Upgrading and downgrading standalone Compact Remote units
8 Reset the system. This step is required. For example: admin> reset
Upgrading and downgrading standalone Compact Remote units
Note You must upgrade both control modules to the same software version.
Compact remote boot loader file, tar file, and related binaries Table 1-5 lists the boot-loader and tar files for upgrading software for a standalone Compact Remote Stinger system.
Table 1-5. Boot loader and tar file for standalone Compact Remote systems
File name Description
crtcmb.bin Boot-loader file for standalone Compact Remote systems.
stg1rel.tar Tar file for Stinger units with CM-v1 control modules, includes LIM and trunk binaries.
Note Not supported beyond 9.7.x releases
stgrel.tar Tar file for Stinger units installed with CM-v2, CM-v2.1, and IP2000 control modules. Includes LIM binaries. For a listing of the binaries in the stg1rel.tar and stgrel.tar files, see “Binaries in stgrel.tar and stg1rel.tar in this TAOS 9.9.1” on page 1-10.
Upgrading a standalone Compact Remote unit To upgrade a standalone Compact Remote unit, proceed as follows: 1 Save the system configuration. For instructions, see “Saving the system configuration using a TFTP server” on page 1-2. 2 Load the appropriate boot loader for the primary control module. admin> load boot-cm network IPaddress crtcmb.bin 3 Load the new tar file onto the control modules. On the primary control module, enter the following sample command: admin> load tar network IPaddress crtrel.tar On a redundant system, the system automatically copies software images from the primary to the secondary control module. Check to see if the appropriate images (.ffs files) are on the flash card of your secondary control module.
If you must load the boot-loader and tar files for the secondary control module, telnet to the secondary control module, then repeat this step.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 1-15 Upgrading to this release Upgrading and downgrading standalone Compact Remote units
4 Save your unit’s IP address to the default.cfg file. See “Saving configuration information to the default.cfg file” on page 1-2. 5 Clear all profiles by entering the nvram command. admin> nvram After the nvram command, your system's IP address should have been restored. If an unexpected error occurs and you must restore your system IP address, see “Saving configuration information to the default.cfg file” on page 1-2. 6 Load a backup configuration made under the restored software version or one of its predecessors. admin> load config network IPaddress config/backup-config 7 Reset the system. This step is required. admin> reset
1-16 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS ‘9.9.1 2
About this release...... 2-1 2-1
ATM G.Bond Support for ADSLx LIM ...... 2-1 2-1
VDSL2 Features and SELT DELT BIST Support for Ikanos LIMs ...... 2-11 2-11
Support for PPPoA over LLC ...... 2-17 2-17
New Version of Stinger Compact Remote ...... 2-18 2-18
Support for G24V and Enhanced Impulse Noise Protection ...... 2-19 2-19
MS+IP, new version of MS+...... 2-19 2-19
Support for SELT on VDSL LIM ...... 2-21 2-21
Support for ECMP on IP2100...... 2-22 2-22
Selectable Line Code for G24 Based Conexant LIMs ...... 2-22 2-22
Support for SNRM per bin in A2P card ...... 2-26 2-26
Firmware in this release...... 2-27 2-27
About this release The TAOS 9.9.1 release introduces new hardware devices and new software features for Compact Remote IP DSLAM systems and IP control modules. It also includes a few administrative enhancements. This release note describes the new software features introduced in TAOS 9.9.1, and provides an overview of the new hardware devices introduced this release. This release note also describes other changes to the command-line interface and change requests fulfilled in this release.
ATM G.Bond Support for ADSLx LIM The ATM G.Bond feature, based on ITU-T G.998.1, is supported on the high bandwidth ADSLx LIM. This feature enables ADSL equipment to aggregate multiple digital subscriber lines (DSL) into a single ATM data stream.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-1 TAOS 9.9.1 ATM G.Bond Support for ADSLx LIM
The ATM G.Bond feature supports bonding of up to four physical lines within a single bonded group. This feature is available on the following ADSLx LIMs: ■ ADSL2/2+ STGR-LIM-A2P-48-HB ■ ADSL2/2+ STGR-LIM-A2P-72-HB
Advantages The ATM G.Bond feature provides the following advantages: ■ Higher bandwidth. ■ Redundancy: In case of link failure, the data transfer over the failed physical link in a group can still reach the destination over other lines in that group. ■ Cost effective solution for both service providers and users when compared to using multiple separate DSL lines for more bandwidth.
Overview
What is bonding The purpose of the ATM G.bond feature is to group together multiple DSL lines to transport a single ATM data stream. The ATM G.Bond supports the following: ■ Dynamic removal and restoration of bonded DSL lines without manual intervention. ■ Disparate data rates among the bonded DSL lines.
Bonded groups DSL lines on a particular ADSLx LIM can be grouped together. The group cannot be formed using DSL lines across multiple LIMs. On a LIM, any line can be bonded in any order. Each line can only belong to a single bonded group.
How bonded lines function The bonded lines function in the following sequence of actions: 1 Each DSL line acts as the bonding link within the specific bonding group. 2 The ATM bonding links can carry traffic with different cell rate. 3 The cell is modified to hold a specific Sequence ID (SID). 4 Bonding layer introduces the SID in each outgoing ATM cell and sends them on the different bonding links. 5 The SID then enables reassembling of the original sequence on the receiving side. Support is available for both 8 and 12 bit formats of SID. 6 The asynchronous status messages (ASM) protocol synchronizes and maintains the status of the bonding line between the CO and CPE. 7 After the lines are grouped, a connection or permanent virtual circuit (PVC) is created on the group. The connection is not created on the individual lines. 8 The nailed group associate lines within the group.
2-2 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 ATM G.Bond Support for ADSLx LIM
Removing bonded lines
To remove bonded lines, the administrator must bring down the group, and change the nail group of the line. When removing a link from a gbond group, you should also adjust the num-links number in the gbondgroup profile.
Link behavior
The bonded group remains up even in the following situations: ■ When the al-dmt profile is disabled, it is treated as a regular link failure and the bonded group is retained. When a link goes down when disabled, the bonded group is up with another link. However, the value of the num-links parameter in the gbondgroup profile does not change. By saying that the bonded group remains up, it implies that the bonded group is not removed although the line is down because the al-dmt enable=no. The gbond-group- status profile is not deleted. The dev up state of the group remains Idle as displayed in the following example.
admin> gbondg -a All GBOND groups: (dvOp dvUpSt dvRq sAdm nailg) 53 { 1 2 75 } (Down Idle UP UP 53)
The group does exist but its status is idle when all its links are down. This behavior is identical to link failure due to other reasons. The bonded group goes down in the following situations: ■ When the value of nailed group of any of the links changes. ■ When you disable a link first, and then change the nailed group, the group that was operating with the first link goes down. To get the bonded group up again, modify the value of num-links to equal the number of links that are present. The bonded group link can be disabled in the following ways: ■ In the al-dmt profile of the link, set enable = no ■ Modify the nailed group of the bonded link.
GBONDGROUP profile
A new profile, GBONDGROUP, is introduced to configure the bonded group.
[in GBONDGROUP/gbond_1] name* = gbond_1 active = yes nailed-group = 53 asm-version = 1 ignore-lineup = system-defined num-links = 2 group-id = 3 sid-format = 8bit
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-3 TAOS 9.9.1 ATM G.Bond Support for ADSLx LIM
diff-delay-max-up = 10000 diff-delay-max-dn = 0 max-aggr-rate-up = 4200000 max-aggr-rate-dn = 42000000 min-aggr-rate-up = 1100000 min-aggr-rate-dn = 11000000 vp-switching-vpi = 15 tx-shaping-mode = vc phys-addr = {shelf-1 slot-2 74}
Parameter Setting name A text name for the profile, up to 15 characters. active Sets the profile status either to active or inactive. The field type is boolean. Valid values are yes or no. nailed-group Identifies the nailed group of the bonded links. The nailed group of a bonded group created on a particular slot card must be within the range of valid nailed groups available on that slot card. asm-version Version of the Autonomous Synchronous Message control protocol. Currently supported version is 1 as per ITU-T G.998.1[pre-published]. This is a read-only parameter. ignore-lineup Specifies whether the Stinger system ignores line status when determining whether calls are established. Valid values are: no Do not ignore lineup yes Ignore lineup. num-links Number of links that are participating in the bond group. Valid range = 1 to 4 group-id Identifies the group uniquely. Group-id is automatically assigned if not configured by user. The group id can range from 1 to 65536. sid-format The format of the SID messages to be used for cell segmentation and reassembly. Enumerated field values are: 8bit First 8 bits of VCI are used by SID. 12bit 4 bits of GFC and first 8 bits of VCI are used by SID.
2-4 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 ATM G.Bond Support for ADSLx LIM
Parameter Setting diff-delay-max-up Maximum upstream differential delay tolerance value specified in milliseconds between the fastest and the slowest link in the bonded group. Default value = 20000 Numeric field. Range = 0 to 4294967295 For example, for 2 links with 1 mbps bit rate each, a good value would be 300 msec. If the number of links participating in the bonded group are more than two then the value can be adapted as follows. us-max-delay = 300 * ( no of links - 1 ) diff-delay-max-dn Maximum downstream differential delay tolerance value specified in milliseconds between the fastest and the slowest link in the bonded group. Numeric field, range = 0 to 4294967295
Note This parameter is not supported in this release and the value set here has no effect on the system operation. max-aggr-rate-up Maximum upstream data rate allowed on the bonded group.
Note This parameter is currently ignored by the system. The bond bit rate depends on the line rate configurations as defined in the al-dmt profile. max-aggr-rate-dn Maximum downstream data rate allowed on the bonded group.
Note This parameter is currently ignored by the system. The bond bit rate depends on the line rate configurations as defined in the al-dmt profile. min-aggr-rate-up Minimum upstream data rate allowed on the bonded group.
Note This parameter is currently ignored by the system. The bond bit rate depends on the line rate configurations as defined in the al-dmt profile. min-aggr-rate-dn Minimum downstream data rate allowed on the bonded group.
Note This parameter is currently ignored by the system. The bond bit rate depends on the line rate configurations as defined in the al-dmt profile.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-5 TAOS 9.9.1 ATM G.Bond Support for ADSLx LIM
Parameter Setting vp-switching-vpi The base VPI used for VP switching. All VPIs including and above this are used in VP switching.
Caution Changing this value will drop all connections on the port immediately. tx-shaping-mode The shaping that is applied on the group. Enumerated values are vc and vpvc. phys-addr Preferred physical address for the G.bond group defined as a shelf slot and item-number. This parameter can be optionally specified by the user. When the parameter is not specified by the user, the system allocates a physical address during bond group creation. User is required to allocate a unique port number on the slot for which the group is created. shelf The shelf number slot The slot index item-number The physical index of the bonded links on the LIM.
GBOND-GROUP-STAT profile The GBOND-GROUP-STAT profile provides the group statistics of the bonded group. All parameters in this profile are read-only.
Parameter Setting name A text name for the profile, up to 15 characters. nailed-group Nailed group identifier of the bonded links. active Yes if the group is active, otherwise No. Valid values are Yes or No. phys-addr Preferred physical address for the ATM G.bond group. shelf The shelf number slot The slot index item-number The physical index of the bonded links on the LIM. group-id The current group index. num-links The number of links that are currently part of the bonded group ne-group-status The current status of the bonded group. Enumerated fields are: operational The bond group is operational. unavailable The bond group is unavailable.
2-6 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 ATM G.Bond Support for ADSLx LIM
Parameter Setting grp-fail-code Displays the reason for bond group unavailability. This parameter is currently not supported and any dependence on this parameter can lead to erroneous results. group-statistic Sub-profile containing statistics of the bond group. group-statistic: Current (actual) aggregate data rate in upstream aggr-data-rate-up direction in bits/second. group-statistic: Current (actual) aggregate data rate in downstream aggr-data-rate-dn direction in bits/second. group-statistic: Time elapsed since the Bond group is up in seconds. running-time group-statistic: Cell loss count in the upstream direction. rx-loss-count-up group-statistic: Cell loss count in the downstream direction. rx-loss-count-dn group-statistic: Number of times group becomes unavailable in the grp-fail-count measurement interval. vp-switching-vpi The base VP value used in VP switching. gbond-link-status subprofile This subprofile is added in AL-DMT-STAT profile together with a parameter to identify the current line operational mode. The subprofile lists the parameters that display current link status and the bonded machine states.
Parameter Setting tx-link-number Indicates the link number associated with the DSL line. The link identifier is assigned by the Gbond protocol for the bonded Group. The links are numbered from 0, and a maximum of 4 links are supported in a group. rx-link-status Receive status of this bonded link. This parameter is updated by the ASM protocol. The link is available for data transfer only when its receive and transmit status is SELECTED-TO-CARRY-BONDED-TRAFFIC. The status field is enumerated with the following values: ■ Not Provisioned ■ Not used ■ Acceptable to carry bonded traffic ■ Selected to carry bonded traffic
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-7 TAOS 9.9.1 ATM G.Bond Support for ADSLx LIM
Parameter Setting tx-link-status Transmit status of this bonded link. This parameter is updated by the ASM protocol.The link is available for data-transfer only when its receive and transmit status is SELECTED-TO-CARRY-BONDED-TRAFFIC. The status field is enumerated with the following values:. ■ Not Provisioned ■ Not used ■ Acceptable to carry bonded traffic ■ Selected to carry bonded traffic group-id Identifies the group and also associates the group with the links to be contained within using Nailed group number. rx-asm-status Enumerated field with values 'Yes' and 'No' to indicate that a ASM message has been received in the last one second. req-tx-delay Requested delay in 0.1 ms unit to be implemented by the transmitter entity on the link carrying the ASM cell. This value shall be set to 0 on ASMs transmitted from the CPE. This field is not supported in the current release. See diff- delay-max-up parameter in the GBONDGROUP profile for delay restrictions. act-tx-delay Actual delay in 0.1 ms unit implemented by the transmitter entity on the link carrying the ASM cell. This value shall be set to 0 on ASMs transmitted from the CO. This field is not supported in the current release. gbond-link-statistic subprofile This subprofile is added in AL-DMT-STAT profile together with a parameter to identify the current line operational mode. The subprofile displays the bonded group statistic counters.
Parameter Setting incoming-cells Total cells received on the bonded link within the group. outgoing-cells Total cells transmittedon the bonded link within the group. incoming-asm-cells Total ASM cells received on the bonded link within the group. outgoing-asm-cells Total ASM cells transmitted on the bonded link within the group. incoming-err-slc Total cells received with SLC error on the bonded link within the group.
2-8 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 ATM G.Bond Support for ADSLx LIM
Parameter Setting incoming-err-parity Total cells received with Parity error on the bonded link within the group. elapsed-seconds Number of seconds that have elapsed in the current measurement interval of 15 minutes. line-mode This parameter indicates the current operational mode of the line. The enumerated values are: uni Link operates in UNI mode. gbond Link operates in ATM gbond mode
GbondLines command This command displays the bonded lines. On LIM, gbondlines lists all the lines and marks the bonded lines as GBOND.
Usage gbondLines -[ a | f | u ]
Command Element Description
G a List all Gbond lines f List all free lines u List in-use lines
Example To display all the Gbond lines: admin> gbondlines -a Note Use the which -p
GbondGroups command This command displays the bonded groups.
Usage gbondGroups -[ a | d | u ]
Command Element Description
a List all Gbond groups d List all disabled groups u List in-use groups
Example To display all the Gbond groups: admin> gbondgroups -a
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-9 TAOS 9.9.1 ATM G.Bond Support for ADSLx LIM
Configuring groups, lines and connections Complete the following procedure to configure groups, lines and connections: 1 Create a new gbondgroup profile. For example, new gbondgroup g23 set active=yes set nail=73 set num-links=2 set asm=1 set sid = 8 set group-id=23 set diff-delay-max-up = 1000 write -f 2 Add links to the gbondgroup profile. To do this, equate the nailed groups of the individual ports to the nail group of the gbondgroup profile and set the value for line enable to true. For example, read al-dmt {1 2 23} set enabled=yes set line nail=73 write -f
read al-dmt {1 2 24} set enabled=yes set line nail=73 write -f For complete details of the al-dmt profile, refer to the Stinger ADSL and ADSL2+ Line Interface Modules (LIMs) Module Guide. After both links are added, the ASM protocol starts automatically and transmits ASM cells to the CPE, once the lines are trained up. The response ASM of CPE is processed and state transitions occur on both far and near sides. When the status of both sides is functional, they are ready for user data transfer. When the value of ne-group-status parameter in the gbond-group-stat profile changes to OPERATIONAL, it indicates that the links are ready for user data transfer. 3 Create connections on the bonded group. To do this, proceed just as you would when creating connections on a regular ATM line. For example, A 1-to-1 PVC vlan connection new VLAN-ETHERNET set interface-address physical-address shelf = shelf-1 set interface-address physical-address slot = first-control-module set interface-address physical-address item-number = 2 set interface-address logical-item = 73 set enabled = yes set bridging-options bridging-group=73
2-10 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 VDSL2 Features and SELT DELT BIST Support for Ikanos LIMs
set bridging-options bridge = yes write -f
new CONNECTION set station = c73 set encapsulation-protocol = atm set ip-options ip-routing-enabled = no set bridging-op bridge=yes set bridging-options bridging-group =73 set bridging-options bridge = yes set atm-options nailed-group =73 set atm-o vpi=0 set atm-o vci=35 set active=yes write -f
VDSL2 Features and SELT DELT BIST Support for Ikanos LIMs This section describes the following topics: ■ The new vdsl2-config subprofile that provides the VDSL2 features for the Stinger R9.9.1 release. ■ The new variable, notch-enable in the AL-DMT:vdsl-config:spectrum- config:notch-config that allows you to enable or disable the various RFI notches. ■ SELT DELT BIST support for Ikanos LIMs. ■ Upgrade of Ikanos DSP+API code. vdsl2-config
Description vdsl2-config enables you to configure VDSL2 settings. This subprofile can be set when vdsl2 is set as the line-code in the al-dmt vdsl-config:line- config subprofile.
Usage The vdsl2-config subprofile simplifies the task of configuring vdsl2 train- ups. It achieves this by approximating as closely as possible, the 993.2 standard description for region, profile type and PSD mask.
Following is a listing of the vdsl2-config subprofile with its default settings.
[in AL-DMT/{ shelf-1 slot-4 1 }:vdsl-config:vdsl2-config] region = europe profile = p12a mask-europe = b8-4-998-m2x-a mask-up-north-america = eu-32 mask-dn-north-america = d-32
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-11 TAOS 9.9.1 vdsl2-config
The following table describes the profile parameters.
Parameter Description region Specifies the region. The settings for this parameter map to the annex A and annex B of G993.2. The annex B denotes Europe and annex A denotes North America. Valid values include europe and north-america. europe:When this value is selected, note the following rules in parameter settings: ■ This value uses the mask-europe settings. The mask-up/down-north- america are ignored. ■ With the region selected as Europe, the valid profile selections are 8a, 8b, 8c, 8d and 12a, 12b. The 8X profiles are restricted from using the b7-X settings. Wehn you select either p8a or p8b as the profile setting, then b8-X is the valid mask-europe setting.Setting mask-europe to one of the b7-X settings, rejects the profile for this combination of region and profile. north-america:When this value is selected, note the following rules in parameter settings: ■ This value uses the mask-up-north-america, mask-dn-north- america settings. The mask-europe setting is ignored. ■ With the region selected as North America, the valid profile selections are p8c, p8d, p12a, and p12b. Setting profile to p8a or p8b, rejects the profile. If the mask-up-north-america and mask- down-north-america do not match, such as eu-32 and d-64, then the profile is rejected. profile Specifies the VDSL2 profile. Valid values: p8a p8b p8c p8d p12a p12b The settings for these parameter directly map to settings in the G993.2 standard.
2-12 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 vdsl2-config
Parameter Description mask-europe: Specifies the VDSL2 mask for the value europe. Valid values: b8-1-998-m1x-a b8-2-998-m1x-b b8-3-998-m1x-nus0 b8-4-998-m2x-a b8-5-998-m2x-m b8-6-998-m2x-b b8-7-998-m2x-nus0 b7-1-997-m1c-a-7 b7-2-997-m1x-m-8 b7-3-997-m1x-m b7-4-997-m2x-m-8 b7-5-997-m2x-a b7-6-997-m2x-m The settings for these parameter directly map to settings in the G993.2 standard. mask-up-north-america Specifies theVDSL2 upstream mask for the value north-america. Valid values: eu-32 eu-64 The settings for these parameter directly map to settings in the G993.2 standard. mask-dn-north-america Specifies the VDSL2 downstream mask for the value north-america. Valid values: d-32 d-64 The settings for these parameter directly map to settings in the G993.2 standard.
Dependencies The vdsl2-config subprofile is active only when the line-code parameter in the vdsl-config is set to vdsl2. When the vdsl2-config subprofile is active, then the certain settings are ignored in the following subprofiles: ■ In the vdsl-config: line-config subprofile, the standard setting is ignored. ■ In the vdsl-config: spectrum-config subprofile, the following settings are ignored – band-plan
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-13 TAOS 9.9.1 notch-enable
– u0-band – scenario – etsi-variant – up-psd-template – down-psd-template – adsl-presence – adsl-friendly
Location al-dmt:vdsl-config notch-enable
Description The notch-enable variable lets you select which RFI notches to enable or disable.
Usage Valid values are yes and no. The yes value enables an RFI notch and a no value disables an RFI notch. The frequency range addressed by these notches is covered by settings in notch- enable. Guidelines for usage: ■ For vdsl2 train-ups, set the nc-XXXXk notches to no. Use the notch-enable variable to enable or disable notches. ■ A maximum of 16 notches can be set at any given time. Notches that overlap in frequency range still count one each to the total number of notches. ■ For VDSL1, you can use any combination of nc-XXXXk and notch-enable values up to 16 total notches.
Example super> read al-dmt {1 4 1} AL-DMT/{ shelf-1 slot-4 1 } read super> list vdsl spec notch [in AL-DMT/{ shelf-1 slot-4 1 }:vdsl-config:spectrum-config:notch-config] nc-1810k = no nc-3500k = no nc-7000k = no nc-10100k = no notch-enable = [ no no no no no no no no no no no no no no no no no no no no no+
Dependencies This subprofile is rejected in the following situations: ■ If the value nc-XXXXk notches is set to yes when the line-code parameter in the vdsl-config: line-config subprofile equals vdsl2. The nc-XXXXk notches are legacy VDSL1 RFI notch enables. Their use is mutually exclusive with the new notch-enable variable. ■ If more than 16 values in notch-enable are set to yes.
2-14 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 notch-enable
The following table provides a mapping of notch-enable values to RFI notch ranges:
Index RFI notch
0 1800-2000
1 1810-2000
2 2173-2191
3 2850-3155
4 3400-3500
5 3500-3800
6 3500-4000
7 3800-4000
8 4200-4215
9 4650-4850
10 5450-5730
11 5900-6200
12 6300-6320
13 6525-6765
14 7000-7100
15 7000-7200
16 7000-7300
17 7200-7450
18 8405-8420
19 8815-9040
20 9400-9900
21 10005-10100
22 10100-10150
23 11175-11400
24 11600-12100
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-15 TAOS 9.9.1 notch-enable
Location AL-DMT/{shelf-1 slot-4 1}:vdsl-config:spectrum-config:notch-config
SELT DELT BIST support for Ikanos LIMs Support for SELT, DELT and BIST is now available for the Ikanos 24 port VDSL and VDSL2 LIMs.
Similarities when compared to SELT DELT in Conexant LIMs ■ The test launch and retrieval of data use the same interface that exists for Conexant LIMs. ■ All tests follow the paradigm and SNMP/profile used by the Conexant ADSL/ ADSL2/ADSL2+ packs.
Differences when compared to SELT DELT in Conexant LIMs ■ Port control limitations ■ Time required to complete SELT DELT ■ Data format and analysis
Port control limitation The port control limitation is because of the SELT DELT processing on the Ikanos DSP. When the SELT DELT is running, other not-under-test ports on that DSP (DSP groupings 1-8, 9-16, 17-24) have port enables, disables and provisionings queued for processing after SELT DELT completes.
Time required to complete SELT DELT The time required to complete SELT DELT for the Ikanos LIMs could be significantly longer than for the Conexant LIMs. The Conexant LIMs typically complete SELT DELT in under a minute. The Ikanos LIMs can take up to two minutes. The time required to transfer the results data using tftp is equivalent.
Data format and analysis The Ikanos test result data varies in format from Conexant. It uses different analysis tools. The SELT result data format is in non-readable binary. You need to use an Ikanos provided tool to process the data and then generate readable graphs and values. The DELT result data format is in readable ASCII. Ikanos will provide details of how to process this data under separate cover.
BIST BIST control on Ikanos LIM is the same as Conexant LIMs. However, the functionality covered in the test is different. BIST on the Ikanos LIM does not test the data path. This functionality was left out because Ikanos requires the DSP to be reset on a data path test. Doing this would have impacted the service on ports not under test in the same DSP grouping as the port under test.
2-16 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 Support for PPPoA over LLC
Upgrade of Ikanos DSP+API code Ikanos DSP+API code is now upgraded to version 2.0.4r19F.
Support for PPPoA over LLC This feature adds support for PPPoA over LLC encapsulation. Until now PPPoA worked only with VC encapsulation.
To bring up a PPPoA call, Stinger requires two profiles, atm-ckt and PPPoA. The atm- ckt profile runs between the dsl port and the sar port. Both VC-mux and LLC type of encapsulations use this approach. The first packet that the circuit receives decides the type of encapsulation to be used. For example, ■ If the first packet arrives with a VC encapsulation, then Stinger brings up the PPPoA call with VC-mux encapsulation. ■ If the first packet arrives with the LLC encapsulation, then Stinger brings up the PPPoA call with LLC encapsulation.
Verifying the encapsulation type A standard PPPoA configuration caters to both the types of encapsulation. To verify the encapsulation type in use, check the ifmgr dump of the circuit connection.
The following information displays for a VC encapsulation on executing the ifmgr dump: admin >ifmgr -n ckt Profile[ckt] slot/if=[1/27] rdh>ifmgr -d 27 iff 0x85077e98 inUse: Yes hostName: ckt . . .atm1483-encaps : aal5-vc . . admin >info np connection 1 1 27 Connection Handles if sh/sl act cPort dPort type uctl udata dctl ddata Encaps: PPPoA over VC - MTU=1524 (50) Control & Data Service Queues: ------ControlQID 324 Lport 0x0000 Scheduler CBR CosQueue 1
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-17 TAOS 9.9.1 New Version of Stinger Compact Remote
DataQID 332 Lport 0x0000 Scheduler UBR CosQueue . .
The following information displays for the LLC encapsulation on executing the ifmgr dump: admin>ifmgr -n ckt Profile[ckt] slot/if=[1/27] rdh>ifmgr -d 27 iff 0x85077e98 inUse: Yes hostName: ckt . . atm1483-encaps : aal5-llc . . admin>info np connection 1 1 27 Connection Handles if sh/sl act cPort dPort type uctl udata dctl ddata 27 1/1 Y 000000 000000 LIM 0/149 0/148 0/149 0/148 Encaps: PPPoA over LLC - MTU=1524 (50) Control & Data Service Queues: ------ControlQID 340 Lport 0x0000 Scheduler CBR CosQueue 1 DataQID 344 Lport 0x0000 Scheduler UBR CosQueue 3 . .
New Version of Stinger Compact Remote
This release introduces a new version of the Stinger Compact Remote. The new version enables Stinger Compact Remote to use the VDSL2 functionality. The following changes have been made to enable VDSL2 functionality on the Stinger Compat Remote: ■ Heat sinks have been attached to the inside and outside of the left enclosure wall. ■ Additional ductwork to manage the internal and external airflow. ■ Improved solar insulation. ■ Revised louvering. ■ A new protection block assembly has been developed. ■ Retrofit Kit lets you upgrade the Phase 1 version of Stinger Compact Remote (CR) system to support VDSL-2 Circuit Pack functionality.
2-18 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 MS+IP, new version of MS+
For complete details, see the Stinger Compact Remote ATM DSLAM Getting Started Guide, or the Stinger Compact Remote IP DSLAM Getting Started Guide.
MS+IP, new version of MS+ MS+IP is a new version of MS+ introduced in this release. MS+IP is similar to MS+ except that MS+IP has a back-plane design, whereas MS+ has a mid-plane design. MS+IP has the following additional features: ■ Four LIPM slots ■ One CM slot ■ No TM slots ■ No LPM slots ■ Disable LIM sparing and per port LIM sparing ■ Up to 288 xDSL ports (4 X 72) ■ Two DC filter tray slots (works with one or two filter modules) ■ One alarm relay slot ■ Fan is inserted from front ■ Uses existing Stinger modules (except fan design is new) ■ Software allows initialization of LIMs in LIPM slots TAOS features for MS+IP include the following hardware changes: – Recognize chassis as specified earlier – Denies TM provisioning – Denies redundant CM provisioning – MIB models MS+IP with 4 LIMs, and 1 CM
Note Trunk module provisioning on slot 17 and 18 (non-existent trunk slots), TM and CM redundancy is denied and an error message is displayed.
For more details on MS+IP, refer Stinger MS+, MS+IP Getting Started Guide.
Support for G24V and Enhanced Impulse Noise Protection
Overview Impulse Noise Protection (INP) is a mechanism that reduces the number of errors that occur due to impulse noise. The noise can be caused by interferences from fans, engines, and similar disturbers. It is a part of the ADSL2+ standard (ITU 992.5). For services requiring low bit-error rate (such as IPTV), this feature helps DSL to be more robust. ITU 992.5 specifies the following mandatory parameter values: INP = 2 1/S = up to 3 D = up to 64
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-19 TAOS 9.9.1 Support for G24V and Enhanced Impulse Noise Protection
In this release, a new device G24V is introduced that has extra memory to allow for the enhanced INP features as per the 992.5 amendments. The G24V is a modified Conexant G24 device. The amendment calls for support of D up to 511 and higher 1/ S so that higher rates (up to 20Mbps) can be achieved with an INP=2. G24V based LIMs look and behave the same way as G24 LIMs. The only difference is that the revision bit is used internally to flag the board as a G24V device. Once Stinger detects a LIM with G24V devices, it automatically turns on the enhanced INP features. The debug option allows a user to verify whether a LIM is a G24V or a G24. There is also a log message that is printed as part of the POST to let the user know that the LIM is a G24V based LIM.
Prerequisite for enhanced INP A G24V based LIM is required for implementing the enhanced INP. You need to have a modem (CPE) to support this feature.
Supported LIMs The following LIMs support this feature: ■ STGR-LIM-A2P-72-HB1 ■ STGR-LIPM-A2P-72-HB ■ STGR-LIM-A2P-48-HB1
User interface changes There is no change to the user interface. However, there are extra values added for setting the INP parameter.
Overview of the min-inp-down parameter This parameter specifies the minimum number of downstream DMT symbols with impulse noise errors that can be corrected. Settings for greater correction also result in greater delay and lower data rates. The setting is only valid on lines using ADSL2 or ADSL2+ protocols. The valid settings are: auto half-symbol one-symbol two-symbols four-symbols eight-symbols sixteen-symbols
Note INP works only in interleave mode. You need to set latency to interleave for this feature to work.
Example: [in AL-DMT/{ shelf-1 slot-1 2 }:interleave-path-config] min-bitrate-up = 128 min-bitrate-down = 128
2-20 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 Support for SELT on VDSL LIM
max-bitrate-up = 1000 max-bitrate-down = 24544 planned-bitrate-up = 512 planned-bitrate-down = 1000 max-delay-up = 16 max-delay-down = 16 min-inp-down = two-symbols min-inp-up = auto
Provisioning the LIM The provisioning is straightforward. A user can set the minimum required INP value, and the LIM will try to train at the highest rate possible while achieving the minimum INP value specified in the profile. If CPE supports enhanced INP feature, then the rate achieved at specific INP settings will be much higher compared to the DS rate achieved against a CPE that does not. CPE 1 supports enhanced INP features. CPE 2 does not. An example for achieved data rate is shown below:
Table 2-1. Achieved data rate for CPE
CPE Mode US/DS rate
1 ADSL2plus 1130/19370
2 ADSL2plus 1130/7495
Support for SELT on VDSL LIM In this release, SELT is enabled on VDSL2 LIM. SELT is primarily used to estimate the length of the subscriber loop. This is done by sending an electrical impulse down the line, then measuring the echo delay, which is directly proportional to loop length. SELT can also be used to perform the following tests. ■ Detection of cable breaks ■ Detection of electrical shorts ■ Estimation of inband noise vs. frequency ■ Estimation of margin vs. rate ■ Estimation of loop length ■ Estimation of attainable rate
Minor changes related to SELT on Ikanos board SELT will run the same way it is run on the Conexant LIM. Follow the same guidelines provided before with the following changes: ■ selt-delt-params results-filename must have a .bin suffix for PC version of SELT tool to process. ■ selt-delt-params timeout-tftp should be set to 180 seconds or greater.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-21 TAOS 9.9.1 VDSL-Config subprofile in this release
VDSL-Config subprofile in this release In this release, support is added for the following parameter settings of the AL-DMT: vdsl-config:line-config subprofile.
Parameter Setting ptm-encapsulation Supports the following values: ptm-64-65 ptm-hdlc Because the Ikanos VDSL CPEs do not support ptm-64- 65, set the ptm-encapsulation value to ptm-hdlc for the VDSL lines. line-code Supports the following values: vdsl vdsl2 bit-swapping Setting is ignored. The bit-swapping setting for vdsl line-code and vdsl2 line-code is always enabled.
VDSL2 support The following parameters of vdsl-config subprofile are now supported by the VDSL2: ■ line-config: upbo ■ spectrum-config: notch-config ■ interleave-path-config: max-delay-up ■ interleave-path-config: max-delay-down ■ interleave-path-config: max-inp-up ■ interleave-path-config: max-inp-down
Support for ECMP on IP2100 With this software version, Stinger IP2100 systems support load balancing of equal cost multipath (ECMP) routes. Up to four multipath routes can be load balanced to a given destination with the current software. This feature is already available on IP2000 control module in the 9.7.2 release. For examples of how to configure upstream and downstream ECMP routing, see the Stinger IP Control Module Configuration Guide.
Selectable Line Code for G24 Based Conexant LIMs
Background Selectable line code feature is available only for the G24 based Conexant LIMs. This feature allows the flexibility of defining what line-code are allowed on the line.
2-22 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 Selectable Line Code for G24 Based Conexant LIMs
Previously, when provisioning the line-config: line-code subprofile, a fixed set of values could be set. For example, the line-config: line-code subprofile includes the parameters auto- select, ansi-dmt, g-dmt, legacy-mode, etsi-annex-b, adsl2, adsl2plus, adsl2re, adsl2plus-only,annex-m, and annex-mplus. Some of these values are mapped in a specific way in the low-level driver. For instance, a line-code set to adsl2plus allows the g-dmt, adsl2, adsl2re and adsl2plus modes to train. bit-map parameter The selectable line code feature introduces bit-map, an additional value for the line-config :line code subprofile. If the line-code is set to bit-map, then it enables you to set the new subprofile, line- code-config subprofile. admin> set line-code ? line-code: The DMT line code to be used for the training. Enumerated field, values: auto-select: g-lite: ansi-dmt: g-dmt: legacy-mode: etsi-annex-b: adslplus: adsl2: adsl2plus: adsl2re: adsl2plus-only: annex-m: annex-mplus: bit-map: line-code-config subprofile The line-code-config subprofile lets you define what operational modes are allowed. It provides you more control on what modes are allowed to train under the new configuration. For example, you can either enable ansi-dmt and adsl2plus only, or g-dmt and adsl2plus only.
Note Select the line-code values cautiously because certain line-codes might interact with each other and the rate-reach result might not be as desired.
This subprofile is located at AL-DMT: line-config. super> list line [in AL-DMT/{ shelf-1 slot-1 1 }:line-config] trunk-group = 0 nailed-group = 1 vp-switching-vpi = 15 activation = static
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-23 TAOS 9.9.1 Selectable Line Code for G24 Based Conexant LIMs
call-route-info = { any-shelf any-slot 0 } rate-adapt-mode-up = automatic-at-startup rate-adapt-mode-down = automatic-at-startup rate-adapt-ratio-up = 100 rate-adapt-ratio-down = 100 max-aggr-power-level-up = 13 max-aggr-power-level-down = 20 max-power-spectral-density = 40 line-code = adsl2plus line-latency-down = interleave line-latency-up = interleave trellis-encoding = yes gain-default = 20 db upstream-start-bin = 6 upstream-end-bin = 31 downstream-start-bin = 32 downstream-end-bin = 511 loop-back = none bit-swapping = yes fbm-dbm-mode = fbm alcatel-us-413-boost = unknown psd-mask-down = co psd-mask-up = annexm-all line-code-config = { yes yes yes no no no no no }
Default settings list line-code-config [in AL-DMT/{ shelf-1 slot-1 1 }:line-config:line-code-config] g-lite = yes ansi-dmt = yes g-dmt = yes adsl2 = no adsl2plus = no adsl2re = no annex-m = no annex-mplus = no
2-24 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 Selectable Line Code for G24 Based Conexant LIMs
Parameter descriptions
Parameter Description g-lite The LIM attempts to train using ITU-T G.992.2 protocol. (Not supported for Annex B LIMs). ansi-dmt The LIM attempts to train using ANSI T1.413-1998 protocol g-dmt The LIM attempts to train using ITU-T G.992.1 protocol. adsl2 Supported only for ADSL2+ LIMs. The LIM attempts to train using the ADSL2 (ITU-T G.992.3) or ADSL (ITU-T G.992.1) protocol. adsl2plus Supported only for ADSL2+ LIMs. The LIM attempts to train using ADSL2+ protocol (ITU-T G.992.5). If this protocol is not supported, then the LIM attempts to train using READSL2 (ITU-T G.992.3 Annex-L), or ADSL2 (ITU-T G.992.3). adsl2re Supported only for Annex A ADSL2+ LIMs. The LIM attempts to train using the extended reach READSL2 protocol (ITU-T G.992.3 Annex L). Avoid enabling only adsl2re. On enabling it, the code internally enables adsl2 as well. The adsl2re is a desired mode at long loops and at specific noisy scenarios. It is not suitable for short loop scenarios. The TAOS protects against this selection. annex-m Supported only for ADSL2+ LIMs. The LIM attempts to train using the Annex M (ITU-T G.992.5). annex-mplus Supported only for ADSL2+ LIMs. The LIM attempts to train using the Annex M+ (ITU-T G.992.5).
Example super> read al-dmt { 1 1 2} AL-DMT/{ shelf-1 slot-1 2} read super> list line super > set line-code = bit-map super> list line-code-config [in AL-DMT/{ shelf-1 slot-1 2 }:line-config:line-code-config (changed)] g-lite = yes ansi-dmt = yes g-dmt = yes adsl2 = no adsl2plus = no adsl2re = no annex-m = no
super> set g-lite = no
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-25 TAOS 9.9.1 Support for SNRM per bin in A2P card
super> set ansi-dmt = yes super> set g-dmt = yes super> set adsl2plus = yes super> write AL-DMT/{ shelf-1 slot-1 2 } written super> list [in AL-DMT/{ shelf-1 slot-1 2 }:line-config:line-code-config] g-lite = no ansi-dmt = yes g-dmt = yes adsl2 = no adsl2plus = yes adsl2re = no annex-m = no annex-mplus = no
Support for SNRM per bin in A2P card
Overview In this release, A2P cards support Signal-to-Noise Ratio Margin(SNRM) per bin. This allows the CO and CPE to exchange information about the downstream and upstream SNRM per bin using the overhead channel PMD test parameter update messaging. Note that the SNRM per bin values can be 256 or 512 depending on the mode. System update occurs every four minutes. Also, it may take up to two minutes to get the SNRM per bin values the first time after the link enters showtime. Note This feature works properly only if CPE supports it.
A user can access this feature using the command adslcommand. No debug privileges are required.
Usage adslcommand -s| -m| [port]
Command element Description -s Status -m Margin port ADSL port number. You must always specify a port number.
2-26 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note TAOS 9.9.1 Firmware in this release
Firmware in this release Table 2-2 lists the firmware versions for Stinger devices in this release. New hardware devices in TAOS 9.9.1 are shown in bold font.
Table 2-2. Firmware versions in TAOS 9.9.1
Device Product Code Chipset Firmware version 24-port ADSL line interface module STGR-LIM-AD-24 a O69.10 (LIM) STGRRT-LIM-AD-24 Conexant 48-port ADSL Annex A and STGR-LIM-AD-48 Conexant U24.15.04 Annex C LIMs STGRRT-LIM-AD-48 48-port ADSL Annex B LIM STGR-LIM-AB-48 Conexant W49.11.05 72-port ADSL2/ADSL+/ADSL2+ LIM STGR-LIM-AP-72 Conexant E67.1.36 STGRRT-LIM-AP-72 48-port ADSL2/ADSL+/ADSL2+ LIM STGR-LIM-AP-48 STGRRT-LIM-AP-48 48-port low-power ADSL LIM STGRCR-LIM-AP-48 48-port ADSL2+ IP LIM STGRCR-ELIM-AP-48 72-Port ADSL2+ Annex A Line Interface STGR-LIPM-A2P-72 and Protection Module (LIPM), network Conexant E67.1.36 processor based 72-Port ADSL2+ Annex A LIM, STGR-LIM-A2P-72 network-processor based High-bandwidth Annex A ADSL2+ LIMs STGR-LIM-AP-72-HB Conexant E67.1.36 48-port and 72-port STGR-LIM-AP-48-HB 72-port ADSL2+ Annex A LIPM STGR-LIPM-A2P-72-HB E67.1.36 Conexant 72-port ADSL2+ Annex B LIPM STGR-LIPM-A2B-72-HB E11.1.23 24-port VDSL LIM STGR-LIM-VD-24 Ikanos 2.0.4r19F 32-port SHDSL/HDSL2 LIM STGR-LIM-H2-32 Conexant 1.7 STGRRT-LIM-H2-32
48-port SHDSL and 72-port SHDSL STGR-LIM-SL-48, LIMs STGR-LIM-SL-72 Conexant R3.0.2 STGRRT-LIM-SL-48 STGRRT-LIM-SL-72 36-port SHDSL MRT 19 MRT19-SL-36
72-port ADSL Centillium Annex A LIM STGR-LIM-AD-72 Centillium 280 STGRRT-LIM-AD-72
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 2-27 TAOS 9.9.1 Firmware in this release
Table 2-2. Firmware versions in TAOS 9.9.1 (Continued)
Device Product Code Chipset Firmware version
Stinger MRT 23, Stinger MRT 19, and MRT-AD-36S Stinger MRT-2 ADSL ports MRT-AD-36S-xxx MRT19-AD-48 MRT2U-AD-72S-56K- MODEL 72-port ADSL2+ MRT2+ Centillium 3234 a. Conexant was formerly known as Globespan.
2-28 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Change requests fulfilled in this 3 release
The following change requests (CRs) have been fulfilled in the TAOS 9.9.1 release.
Change request Description of issue number
7018348 Eight consecutive ports were blocked on the ADSL2+ LIM card.
7018560 OAMLOOP does not work on IPoA and BIR connections.
7014515 Stinger sends incorrect values for the attributes Acct-Input- Octets, Acct-Output-Octets, Acct-Input-Packets, and Acct- Output-Packets in accounting stop records for traffic through GigE.
7017358 In a Stinger FS+ equipped with a CM IP2100, the CLI command info wrongly reports the Platform type as Lucent Stinger FS.
7018934 A2P-HB LIMs reset with fatal error 40.
7018002 PPPoE connection does not work when Relay-Session-Id is present in the PADI.
7019127 System displays addDid error while adding 254th client to the bridge group.
7019503 DELT test times out if a line on the same slot is enabled.
VDSL LIM goes into DIAG state resulting in loss of service.
On VDSL LIM, Wintegra is not able to allocate channel to a call.
Call on ADSL port fails to come up after multiple bounces.
7018975 The last-state-change parameter in the physical-status-sub- profile should not be updated continuously.
7019006 The log message Ethernet link 2 is on/off makes troubleshooting difficult for other issues.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 3-1 Change requests fulfilled in this release
Change request Description of issue number
7018721 Interleave line latency behaves abnormally when line-code is equal to auto-select.
7019007 Enabling the link-state traps for the GE-OLIM trunk ports fails.
7019140 When multiple GEs are enabled, GE-OLIM reports problems.
7015901 Acct-checkpoint parameter is not working as expected.
7017217 When config is reloaded into IP2100, the np-port-stat entry reports error.
7019126 The rxOctectsHigh and txOctectsHigh counters never count or are always set to 0 even when the low counters reach their maximum value.
7018868 Automatic port sparing reports problems in TAOS 9.7.2e71.
7019299 The exclude-listed-commands in a user-group profile does not allow to enable/disable permission for the users in the group for CLI commands that have uppercase characters in their name.
7018866 SAR channels are sometimes getting stuck on the LIM, resulting in all cells received from the CPE end being discarded on the Stinger.
7019726 No sync in presence of ETSI ABDC noise in 4W mode on STGR-LIM.
7019036 Stinger MRT2+ based on Centillium chipset (ver. 3230) doesn't synchronize correctly with modem Siemens SpeedStream 4100 based on Texas Instrument chipset.
7018560 oamloop -s does not work on IPoA or BIR connections.
7019213 There are various derived clock source issues (including holdover).
7019300 No traffic flow to certain LIMs on loaded systems running 9.8.1.
7020114 There are issues related to handling of PACKET-FLOWS profiles.
7019301 On MRT and MRT-2, idle-cell-counter and valid-cell-counter from oc3-atm-stat will NOT increment or always show "0".
3-2 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Change requests fulfilled in this release
Change request Description of issue number
7018635 Warning 179 is observed whenever a DHCP_ACK is received for a connection and if the WAN Session is not found for the main interface.
7011921 Upstream Noise margin calculated and reported on Stinger for 48 ports Globespan ADSL LIM is not accurate. A noise margin of 0 dB should correspond to a BER of 10E-7, but the BER is already higher than 10e-7 when reported noise margin is 1 dB.
7018979 On an IP2100, when downstream traffic reaches about 3200kbit/sec, few cell losses occur and this cell loss increases when the downstream traffic increases.
7019822 Certain flash cards (64 MB) fail to operate properly and are not detected with the IP2100 (rev. 12) board.
7018809 In a Stinger with T1 IMA LIM to LIM connections, PVCs will not activate in the IMA LIM after CM redundancy.
7017360 Proper clean up after addDidToMulticastGroupId fails.
7019172 Choppy management traffic after SNMP poll of OID 1.3.6.1.4.
7018175 Traffic rate significantly degrades (to almost zero) when exceeding TM OC3 port capacity with IP2100 in slot 9.
7020141 With atmvccmgr, the number of discarded cells as shown in the discarded cells counter is stuck at 28348500.
7019536 The ‘auto-logout’ feature on serial port is not working on IP2100.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 3-3
System capacity in TAOS 9.9.1 4
Stinger Compact Remote IP DSLAM throughput
Table 4-1. Stinger Compact Remote IP DSLAM throughput
Stinger Compact Remote IP DSLAM (hosted)
Per ELIM ■ 540Mbps, Data via IP2100 - GE-OLIM backplane ■ 900Mbps, Video via GE-OLIM trunk ports
Per Gigabit Ethernet ■ 2Gbps from the GE-OLIM over two GigE Compact Remote ports with link aggregation
Per GE-OLIM ■ 2Gbps, Video on two trunk ports (1Gbps each). ■ 540Mbps, Data from IP2100 backplane ■ 1 to 3 Gigabit Ethernet Compact Remote units with link aggregation
Stinger IP2100 throughput
Table 4-2. Stinger IP2100 system throughput
Stinger IP2100 system throughput
Total throughput on an IP2100 system 3.65Gbps
Per high-bandwidth LIM 550Mbps
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 4-1 System capacity in TAOS 9.9.1 Stinger IP2100 capacity
Stinger IP2100 capacity
Table 4-3. Stinger IP2100 system capacity
IP2100 capacity
Maximum number of RFC 2684 LIM-terminated PVC connections per IP2100 system:
IP2100 with MODEL-A2P-LIMs 5,000
IP2100 with MODEL-AP-LIMs 3,000
Maximum connections based on np-fpp-class-mem-mode parameter settings and number of OAM connections supported.
high-performance mode
■ Trunk-to-LIM ATM PVCs (OAM support is left at the default 4,000 limit of 5000 connections)
■ Trunk-terminated connections (No OAM connections 3,000 supported)
■ 2000 trunk-terminated connections and 2000 trunk-to-LIM ATM PVCs (OAM support is limited to 1000 connections)
medium-capacity mode
■ Trunk-to-LIM ATM PVCs (OAM support is left at the default 4,032 limit of 5000 connections)
■ Trunk-terminated connections (No OAM connections 4,000 supported)
■ 2,000 trunk-terminated and 4,000 trunk-to-LIM ATM PVCs (OAM support is left at the default limit of 5,000 connections)
■ 4,000 trunk-terminated and 4,000 trunk-to-LIM ATM PVCs (No OAM connections supported)
Note Beyond these limits, fatal error FE-29 messages can occur.
Stinger IP2000 capacity
Table 4-4. Stinger IP2000 system capacity
IP2000 capacity
Maximum number of RFC 2684 LIM-terminated PVC 3,000 connections per IP2000 Stinger system
4-2 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note System capacity in TAOS 9.9.1 Maximum number of PVCs per device
Table 4-4. Stinger IP2000 system capacity (Continued)
IP2000 capacity
Maximum number of trunk-terminated connections 1,200
Maximum number of RFC 2684 virtual connections per customer 3 premises equipment (CPE) device.
Maximum number of stacked VLAN calls that can terminate on 3,018 an IP2000 control module
Maximum number of PVCs per device The maximum number of trunk-to-LIM PVCs per port supported is 5 PVCs per port. The maximum number of trunk-to-LIM PVCs per LIM is equal to 4 * the number of ports on the LIM. ■ 48-port LIMs—No more than 192 PVCs/LIM ■ 72-port LIMs—No more than 288 PVCs/LIM
VCC Capacity The type of control module installed in a chassis determines the maximum number of virtual circuit connections per chassis. The total number can be divided across all of the LIM slots depending on the port count for the installed LIM. Any trunk-to-trunk switching VCC must be taken into account in the maximum VCC count. If virtual path (VP) switching is configured for the system, all virtual circuits within the VPC are transparently switched and do not affect the overall virtual circuit capacity.
N
Table 4-5. Virtual circuit connection capacity
Stinger device Maximum number of VCCs
Control module capacity
CM v2 STGRa-CM-A With 64MB memory: 900 VCCs per chassis With 128MB memory: 3200 VCCs per chassis
LIM capacity per port
Enhanced-processor STGR-LIPM-A2P-72 Terminated connections: 72-port ADSL2+ STGR-LIM-A2P-72 4 VCCs per port LIM ATM switched connections: 4 VCCs per port
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 4-3 System capacity in TAOS 9.9.1 VCC Capacity
Table 4-5. Virtual circuit connection capacity (Continued)
Stinger device Maximum number of VCCs
72-port ADSL LIMs STGR-LIM-AP-72 Terminated connections: with ADSL2+ STGRRT-LIM-AP-72 4 VCCs per port capability ATM switched connections: 4 VCCs per port
xDSL LIMs MODEL-LIM-AD-xx Terminated connections: 3 VCCs per port ATM switched connections: 4 VCCs per port
LIM capacity per slot
24 port 96 VCCs per slot
48 port 192 VCCs per slot
72 port LIMs 288 VCCs per slot
a. See “Clarification about support for STGRRT-CM-A control modules with 64MB” on page -4 for additional information.
4-4 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and 5 limitations
Notices in TAOS 9.9.1...... 5-1
Known issues and limitations ...... 5-6
End of sale for Stinger products ...... 5-19 5-19
Notices in TAOS 9.9.1 Following are important notices about TAOS software and hardware support in this release.
Compact Remote IP DSLAM boot ROM requirements For proper operation with this release, Compact Remote IP DSLAM hardware devices must be running the latest version of boot ROM code. The boot ROM code requirements for this release are listed in Table 5-1.
Table 5-1. Required versions of boot ROM code
Device Required version of boot ROM
Gigabit Ethernet (GigE) optical line interface module (GE- ROM version 1.1 OLIM) Checksum 443D
GE-COP—The GE-COP can be version P3 or P3-64M. Use the version command to display the version of the GE-COP.
For GE-COP version P3 ROM version 1.2
For GE-COP version P3-64M ROM version 2.0
Compact Remote IP DSLAM LIM or RLIM ROM version 2.1
To display version of boot ROM code running on a device, open a session with the device and enter the romupdate -c command, as shown in the following examples: ■ For a GE-OLIM in shelf 1, slot 1, enter the commands
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-1 Notices, known issues and limitations IP2100 boot ROM and PSB requirements
admin> open 1 1 golim-1/1> romupdate -c ■ For a GE-COP in shelf 9, slot 8, enter the commands admin> open 9 8 shelf-router-9/8> romupdate -c ■ For an RLIM in shelf 9, slot 2, enter the commands admin> open 9 2 geb-gs-48-9/2> romupdate -c If the version of boot ROM is earlier than the required versions shown in Table 5-1, an upgrade is required. Contact Lucent TAC—see “Calling the technical assistance center (TAC)” on page iii—for information about how to upgrade boot ROM code.
IP2100 boot ROM and PSB requirements For proper software operation with this release, IP2100 control modules must be running the latest versions of PSB and boot ROM code. The required versions of IP2100 boot ROM and PSB for this release are listed in Table 5-2.
Table 5-2. Required versions of IP2100 boot ROM and PSB
Device Required version
PSB Version 0x20
Boot ROM Version 1.46
■ To display the version of PSB running on an IP2100 control module, enter the following command: admin> agerefpga -s ... PSB Version 0x19 ... If the output shows a PSB version that is earlier than the version shown in Table 5-2, an upgrade is required. ■ To view the boot PROM version of the IP2100 control module, enter the ver command from the Boot Mon> prompt. Access the Boot Mon> prompt as in the following example. Reset the system. For example: admin> reset -f Immediately after the reset, the controller displays the character > on the serial terminal. Enter the string lucent within 5-seconds. > lucent You will not see the characters lucent echoed following the prompt sign >. If you do not see the Boot Mon> prompt, repeat this step. From the Boot Mon> prompt enter the ve command.
5-2 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations High-bandwidth LIM requirements
Boot Mon> ve --Versions/Revisions--Test version 1.46 Dec 7 2004 11:32:20 ... If the Test version string differs from the string shown above in bold type font, an update is required. For information about how to upgrade IP2100 PSB and boot ROM code, contact Lucent TAC (see “Calling the technical assistance center (TAC)” on page iii).
High-bandwidth LIM requirements For proper software operation with this release, high-bandwidth (HB) LIMs (model numbers STGR-LIM-AP-72-HB and STGR-LIM-AP-48-HB) must be running the latest version boot ROM code. To display the version of boot ROM code running on the high-bandwidth LIM, open a session with the LIM and enter the following command: ep-hs-72-1/1> rom -c ROM Checksum 5C67 If the output returns a checksum value other than that shown above, a boot ROM update is required. For information about how to upgrade high-bandwidth LIM boot ROM code, contact Lucent TAC (see “Calling the technical assistance center (TAC)” on page iii).
Control module support in Stinger TAOS releases Table 5-3 lists the control modules supported by each Stinger TAOS release. Acheck(√) indicates that a control module is supported by that release.
Table 5-3. Control modules supported by Stinger TAOS releases
Control module product codes
v2 v2.1 IP2000 IP2100
STGR-CM-B STGR-CM-A2 STGR-CM-IP2000-F STGR-CM-IP2100- STGR-CM-C STGRRT-CM-A2 STGRRT-CM-IP2000-F F-MODEL STGRRT-CM-A1 TAOS STGRRT-CM-B version STGRRT-CM-C
7.11.x 9.0-xxx
9.1-xxx √ 1
9.3-xxx √
9.4-185.0 √ √2
9.4-185.1 √√
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-3 Notices, known issues and limitations Control module support in Stinger TAOS releases
Table 5-3. Control modules supported by Stinger TAOS releases (Continued)
Control module product codes
v2 v2.1 IP2000 IP2100
STGR-CM-B STGR-CM-A2 STGR-CM-IP2000-F STGR-CM-IP2100- STGR-CM-C STGRRT-CM-A2 STGRRT-CM-IP2000-F F-MODEL STGRRT-CM-A1 TAOS STGRRT-CM-B version STGRRT-CM-C
9.4-185.2 9.4-185.3 9.4-185.4 9.4-185.5 9.5-206.0 √√ √3 9.5-206.1 9.6.0 9.6.1 9.7.0 9.7.1
9.7.2 9.7.3 9.7.4 9.8.0 √√ √ √ 9.8.1 9.9.0 9.9.1
1. Support for control module v2 was introduced in TAOS 9.1-142.1. 2. TAOS 9.4-185.x releases support a limited feature set of the IP2000 control modules. 3. IP2000B modules (STGR-CM-IP2000-F and STGRRT-CM-IP2000-F) were introduced in TAOS 9.4.185.2. The version command identifies IP2000B modules as follows: Hardware revision: 2.2 Model E - IP (Version B) with gigE fiber interface. On the an IP2000A module, Version B is not displayed.
Clarification about support for STGRRT-CM-A control modules with 64MB Support for Stinger control modules STGGRT-CM-A with 64MB running TAOS 9.7.3 and later releases is available only in Stinger RT units. Control modules with 64MB are not supported in any other Stinger chassis. For Stinger RT units installed with STGRRT-CM-A control modules, no additional software enhancements will be provided beyond the working limitations of the features supported in TAOS 9.7.3. Software releases after TAOS 9.7.3 will most likely allocate additional memory on the STGRRT-CM-A, which can reduce the number of concurrent connections supported in TAOS 9.7.3 or earlier releases. In addition, STGRRT-CM-A control modules with 64MB will be supported only up to the Stinger 9.10 release. Customers who intend to use features introduced after TAOS 9.7.3 will require new control modules with at least 128MB.
5-4 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations Control module compatibility in redundant systems
Control module compatibility in redundant systems Note Be aware that there might be release-specific limitations with redundancy support for Stinger control module. See “Known issues and limitations” on page 5-6 for more information.
If you must use control modules with different hardware revision numbers, be aware that there might be some differences in functionality in a Stinger unit installed with different revision number control modules. Use Table 5-4 to determine if your control modules are compatible. A check (√) indicates that the control modules are compatible in a redundant system.
Table 5-4. Control module compatibility in redundant Stinger systems
Control module v2 v2.1 IP2000x IP2100 hardware version
v2 √√
v2.1 √√
IP2000x √
IP2100 √
NavisAccess™ support for Stinger software releases Table 5-5 lists the NavisAccess™ DSL version support for Stinger TAOS releases.
Table 5-5. NavisAccess™ DSL version support for Stinger TAOS releases.
Stinger TAOS software version NavisAccess™ DSL version
9.9.1 11.0 (To be released)
9.9.0 11.0 (To be released)
9.8.1 10.2
9.8.0 10.0
9.7.3 10.1
9.7.2 9.2
9.7.1, 9.7.0 9.6.1, 9.6.0 9.0 9.5-206.2
9.4-185.5 8.0
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-5 Notices, known issues and limitations Known issues and limitations
Table 5-5. NavisAccess™ DSL version support for Stinger TAOS releases.
Stinger TAOS software version NavisAccess™ DSL version
9.6.0 9.5-206.1 7.4 9.4-185.4, 9.4-185.3 9.4-185.2, 9.4-185.1, 9.4-185.0 7.3 9.3-170.4, 9.3-170.3
9.4-185.0 7.2 9.3-170.2
9.3-170.0 5.1.4 9.2-167 5.1.2 Hotfix 1
9.1-163 5.1.2
9.1-142 5.1.1 9.0-139
9.0 5.1
Known issues and limitations The following issues and limitations are known to exist in TAOS 9.9.1.
Known Compact Remote IP DSLAM issues and limitations The following issues that are known to exist with Stinger Compact Remote IP DSLAM systems.
■ When one of the two fiber stands between the GE-COP and GE-OLIM is cut, the LIMs associated with that fiber pair might reset. This situation does not occur when the full fiber is cut (that is, when both pairs are cut). ■ Unplugging the GigE cable from the Stinger chassis causes the port to be removed from the RSTP-enabled bridge group. This means that the RSTP will fail to provide redundant link. Plugging the cable back in does not resolve the situation. To recover, reset the GigE port using the ifmgr down/ifmgr up commands or disable and then reenable the Ethernet profile. ■ Multicast – The system does not prevent nontrunk ports from being configured as the MBONE. This situation allows for the misconfiguration of the video source ports on the GE-OLIM, however, there is no adverse impact on service or operations. – Bridged IP routing (BIR) over the GE-OLIM is supported only with multicast forwarding; it is not supported with unicast forwarding.
5-6 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations Known Compact Remote IP DSLAM issues and limitations
– On a setup with 3 RLIM, each with 144 groups, when LEAVE messages are sent from the RLIMs, stale groups remain on the GE-COP. This condition resolves itself when timers expire, and has no impact on service. – In hosted applications, when MSTV2 video is used over the Compact Remote IP DSLAM architecture, video flows in the initial unicast stage, but video stops when the application shifts to the multicast stage. ■ Cyclic redundancy check (CRC) errors occur when traffic is passed over two trunk ports on two remote shelves on the same GE-OLIM. ■ On the GE-OLIM, the SNMP command getEthernetInterfaceProfile() reports inaccurate values for the ethenet profile. ■ Virtual LANs (VLANs): After an SNMP walk on the table gigEVlanStatTable, not all VLANs are reported with values. ■ Filters: This release does not support input filters for exception traffic over VLAN interfaces, for example, ARP packets. ■ For traffic in the downstream direction from the GE-OLIM to the RLIM, no IP fragmentation occurs for packet size between 1492 and 1500. This situation does not affect residential gateway modem-initiated calls. ■ When modifying an atm-qos profile that is applied to an active PPPoE call, the RLIM fails with W4301 and W179 messages. To prevent service interruptions, modify the atm-qos when traffic is not being passed. ■ The system sometimes generates Warning 4301 messages on RLIMs (revision 10) with traffic running on PPPoE calls. ■ When about 16MB of downstream unicast data is flowing over a PPPoE call, and call goes down, the system sometimes resets with an FE29 (_etherSendFrame) message. ■ The system generates harmless warning W179 messages as the GE-OLIM is activating. ■ The GE-COP stops operating when the quit command is executed on the serial port. A reset is required to restore the GE-COP to normal operation. ■ When upgrading system software, the system sometimes generates harmless warning W179 (abcmRmInitIpmcSupport) messages on the GE-OLIM. ■ The network processor fixed rate (NPFR) bandwidth cannot exceed 554Mbps on HB LIMs and 140Mbps for low-bandwidth LIMs. ■ For PPPox calls, if the system IP address in the system profile and the local-ip- address and source-if parameters in the connection profile are not set, IGMP queries are sent with source IP address of 0.0.0.0. As a result, video would stop after about 4 minutes. To avoid this situation, set any of the preceding parameters with an IP address. ■ Occasionally, an FE40 message is reported on the RLIM after a trunk-to-LIM traffic soak test. ■ After modifying the VC-switching VPI setting in the oc3-atm profile, the system generates a fatal warning message W4301 on the GE-OLIM. ■ After resetting a remote shelf, the system sometimes generates the log warning, error retrieving ether-info profile. ■ After clearing NVRAM on a CR IP DSLAM system, as saved configuration is reloaded, misleading error messages related to trunk modules are reported.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-7 Notices, known issues and limitations Known issues with Stinger Compact Remote ATM units
Known issues with Stinger Compact Remote ATM units The following issues are known to exist with Stinger Compact Remote (ATM) systems.
■ On hosted systems, if a remote shelf is disabled while configuration is being loaded, some connections do not recover. To restore connections, reload the configuration onto the remote shelf. ■ On hosted systems, after a software upgrade, the system displays the error message fl_close error -1. If the upgrade fails with this error message, remove the crtcmb.bin file from flash before upgrading to the current release. ■ A few Compact Remote systems have been reported to reset (CR 7016927).
IP control modules The following issues and limitations that are known to exist in both IP2100 and IP2000 systems.
■ The lqm parameter specifies whether the Stinger unit requests link-quality monitoring (LQM) when answering a PPP session request. If LQM is enabled on the system, but is not negotiated by the peer, the Stinger unit sends LCP echo request every three seconds to gauge the quality of the link. After nine consecutive unanswered echo requests, the call is disconnected. ■ Rapid Spanning Tree Protocol (RSTP) – Currently, only a single instance of RSTP is supported on a system. If multiple STP ether-group profiles are configured in NVRAM, STP will not work. – During testing, the system reset with a FE50 {_agRmMacPortMapAdd}. – When you change ether-group profile from LACP to RSTP, the system sometimes generates a warning W179 {createLocalVirtualIf} message. To prevent this situation, disable the ether-group profile before changing the settings. ■ PPPoA bridging: The system does not remove padding (packets less than 64 bytes are padded with zeros) in the Ethernet frame coming from the PPPoE server/BRAS, and sends the padding as valid AAL5 data to the CPE modem. The CPE modem must be capable of recognizing that the zeros are not a part of the PPP frame and that they should be ignored. ■ Input Ethernet filters (ether-type comparisons) do not work on pretagged frames in the upstream direction. ■ At lower NPFR settings, ATM QoS inaccuracies can lead to packet loss. ■ When a PPPoE call configured with packet-flows profile is disconnected, the system generates harmless W179(_ipQosFreeResource) messages. ■ Multicast: Changes to a BIR connection profile (such as changes to the atm-qos profile) that result in calls being reset can cause a fatal error FE40 message. To prevent this situation, disable the BIR call before applying any changes.
5-8 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations IP control modules
■ When multicast/unicast data traffic with TTL=1 is received by the system on GigE side, all the traffic comes to control plane, instead of being discarded by the NP. ■ The system generates warning W4302 messages on HB LIMS with continuous channel zapping over PPPoE calls for over one hour. The LIM fails, affecting services. ■ RADIUS filter rules applied directly to RADIUS PPP configuration profiles do not work for calls on LIMs. Use the Filter-ID RADIUS attribute in the RADIUS PPP configuration, assign a filter name to it, and then create that filter separately either in RADIUS or as local profile. (Note that RADIUS filter rules applied directly to RADIUS PPP configuration profiles are supported on calls terminated on RLIMs in a hosted IP DSLAM environment.) ■ The maximum number of supported flow-service profiles is 750. IP2100 system known issues and limitations The following issues and limitations that are known to exist in IP2100 systems: ■ Bandwidth limitation on the GigE port is inaccurate (the setting of the bandwidth parameter in the IP-INTERFACE:scheduling profile yields inaccurate results). ■ If the control module installed in slot 9 is primary, and the rate of traffic exceeds the trunk module line rate, Route Switch Processor (RSP) lockups can occur. ■ While heavy downstream traffic is flowing, Pbus packet loss can occur. The observed packet loss is greatest when traffic is flowing at 1Gbps; no loss occurs at 500Mbps. ■ The MIB ip2kstats.mib (LUCENT-IP2K-STATS-MIB) is not supported in this release. GigE port GMAC statistics and VLAN statistics are reported in the ip2kstats.mib. ■ LACP – OSPF is not supported on systems configured for LACP. – When the type parameter in the ether-group profile is changed from stp to LACP, the system generates an FE40 message. Disable the ether-group profile, set the type parameter to lacp, and then reenable the profile. – On a system enabled for LACP, disabling LACP (setting the ether-group parameter in the Ethernet profiles to 0 for both GigE ports) causes multicast traffic to stop flowing. To recover from the situation, disable and then reenable the GigE ports. – Changing the setting of the ether-group parameter in the ethernet profile sometimes causes the system to generate a W179 message on the LACP aggregated link. ■ IP2100 control module redundancy is not supported in hosted Compact Remote configurations. ■ The status of LIM port redundancy is incorrectly reflected on the redundant control module. ■ Automatic LIM port sparing is not supported in this release. Connections do not come up on the spare port. ■ Upstream VLAN shaping is not supported on IP2100 systems.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-9 Notices, known issues and limitations IP control modules
■ Stacked VLANs – This release does not support IP QoS statistics on stacked VLAN interfaces. – This release does not support upstream traffic over pretagged trunk- terminated stacked VLAN connections. – For stacked VLAN calls, downstream traffic shaping does not work according to the applied QoS. Set the NP port settings (requested-fixed- bandwidth parameter) to a higher value. – After resetting a system with a large number of trunk-terminated stacked VLAN connections (~2000), some connections are not established on the network processor. To restore the connections, disable and then reenable those connections that failed to reestablish. –If a flow-services profile is applied to a stacked VLAN connection, the call comes up. Deleting the flow-services profile causes the call to drop as expected. However, if you reconfigure the flow-services profile, the call will not come up unless you delete the connection profile and reconfigure it or until you reset the system. ■ A GigE reset is required for MAC learning limit to work on transparent VLANs. ■ Misconfiguring a flow-service profile configured with pretagged VLANs causes the system to generate warning W179 messages (_deleteStackVlanEntries). ■ If the connection profile for an MPoA call is not configured with a remote address, after a system reset, the system generates an FE40 message as the call is being established. ■ On IP2100 systems, F4 OAM segment testing is not supported on virtual path connections (VPCs) over Centillium-based ADSL 72-port LIMs (stngr-72-ct- adsl-card), MODEL-LIM-AD-48 LIMs, and MODEL-LIM-AP-72 LIMs. ■ Filters in transparent bridging: If an existing filter that is applied to a vlan- ethernet profile is deleted and then recreated, a GigE reset is required for that filter entry to be updated on the network processor for that VLAN. ■ On connections configured with UBR QoS, downstream traffic exceeding the train rate (about 5%) might pass through the LIM. This condition has no impact on service. ■ IP2100, GigE and GE-OLIM or GE-COP Ethernet ports sometimes generate harmless linkUP and linkDOWN messages. ■ On IP2100 systems, DpRamFailure logs are generated, even when no killer LIMs are present. ■ The system generates errorType=999 on the secondary control module when using the slot -r command. ■ Setting the term-rate parameter to 0 or null causes the serial port to freeze. ■ Multicast forwarding: Instead of being discarded, broadcast traffic that is sent on a nonexistent VLAN is sent to the GE-OLIM. To avoid this situation, configure the network to prevent broadcast traffic from nonexistent VLANs from entering the Stinger GE-OLIM.
5-10 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations IP control modules
■ Multicast packets exceeding PPPoE MTU: If the configured MTU is 1492, packets greater than 1492 bytes are be dropped by the CPE, and fragmentation will not work for PPPoE calls with multicast traffic. If the configured PPP MTU is 500, packets greater than 543 bytes are dropped. ■ The system generates W179 (oamFlexClose) warning messages when a VPI used by a VPC is reserved for VC switching. ■ For trunk-terminated connections, ATM QoS configuration for downstream shaping on the network processor works only if the atm-qos upstream parameter is configured. ■ Filters: RADIUS virtual LAN (VLAN) profiles and ecmp-type comparisons for IP filter configuration on RADIUS is not supported. ■ When provisioning NPFR bandwidth, be aware that oversubscription can result in loss of data on the ports that have been improperly provisioned and might require a system reset to recover. ■ During GigE interface performance testing, packet discards were reported in the RSP global counters for 64 byte and 70 byte packets transmitted at 62% and 77% of the GigE interface rate, respectively. This condition could lead to degraded service for small packet sizes. ■ When there are multiple PPPoE calls per port on a high-bandwidth LIM, CRC errors can occur for traffic in downstream direction. ■ With a 72-port SHDSL LIM, supported number of PPPoE calls should be 216 calls (3 calls/port * 72 ports). Only 215 calls come up properly; the 216th PPPoE call fails. ■ Network processor traffic shaping is inaccurate when multiple PPPoE calls are configured on the same port. This configuration is not typical in customer setups. ■ When saving the configuration of two IP2100 control modules to the default.cfg file, after clearing NVRAM, the system generates SNMP-related error messages describing mismatched states. ■ Standalone IP2100 systems – On a standalone system with 14 72-port ADSL LIMs all in digital loopback, if the system is configured with approximately 4000 trunk-to-LIM connections, the system generates warning W179 and log error messages (learnFppRule: ag_fpp_learn failed st=29). – After saving the IP2100 configuration files and reloading the saved file, the system generates the following error message: SYSTEM-INTEGRITY written error: new profiles of this type may not be created This condition has no impact on service. – On standalone (nonhosted) systems, the distributed multicast feature is supported only on routed calls. It is not supported on bridged calls, such as VLANs with IGMP snooping. The number of multicast clients supported per system is higher with the distributed multicast feature, because multicast replication occurs at distributed points. ■ When PPPoE calls use default scheduler queue size, the downstream shaping is not coming proper. Make sure that you increase the scheduler queue size to 2000 from the default size.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-11 Notices, known issues and limitations IP control modules
■ Maximum multicast groups supported are 512 groups. ■ Downstream shaping not proper for multicast traffic on HBLIM. Make sure that you send the multicast traffic below the configured shaping rate. ■ Confusing log messages, iff-26 dhcpRemoteID already used by iff-25. These messages fill up the syslog. Change the log-display level to error or higher. ■ FE50 (gtGetRxDescOwnership) observed after reset. There will be longer recovery after Stinger reset due to this FE after NVRAM. ■ Redundancy - Multiple issues with bandwidth allocation in dual IP2100. Make minor change in the NP-PORT profile and do a write. ■ Downstream discards for VBR when PCR < 1.1 SCR. Configure PCR at least 10% higher than SCR. ■ With four OC3-TMs, lots of Warning 179s (_sendMail) observed when system comes up after reset. Under a stress condition when more than three OC3 trunks are carrying data over 3000 or more IPoA calls, the system does a reboot. For IPoA configurations, limit the number of Trunk Term calls to 3000 and set log-display to Warning or higher. IP2000 system known issues and limitations The following issues and limitations that are known to exist in IP2000 systems: ■ As traffic to the legacy LIM (48-port SDSL-v2 LIM) control plane approaches 1 Mbps, the Pbus fails and does not recover when traffic is stopped. A slot reset is required to restore normal operations. ■ If more than 2184 calls are established with a packet flow of 7 rules attached to each of them, the system resets with an FE2 message. To prevent the system reset, reduce the number of calls. ■ On a setup with a filter attached to a DHCP over BIR call which blocks all packets destined to a particular address, when DHCP RENEW packets are sent with a destination IP address matching the filter rule, instead of being discarded at the network processor, the packets are sent to the control plane. A blocked client address can continue to generate DHCP requests. Although such requests will fail, the situation can be an unnecessary load on control plane traffic and can be a security concern. ■ An inaccuracy in the range of +/- 0.5 to 0.7% exists when configuring ATM QoS. In the atm-qos profile, specify PCR and SCR values that are approximately 0.5 to 0.7% greater than actual requirement for the connection. ■ On a hosted system with redundant control modules, after a redundancy event, the system sometimes generates the following log message: LOG warning, Shelf 1, Controller-1, Time: 14:34:11-- This profile can not be deleted ■ Counters not incrementing for default queue for VLAN aggregated call. With this problem, statistics cannot be obtained for the packets that took default queue.
5-12 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations ATM limitations
ATM limitations The following issues related to ATM operations exist in this release:
■ In the upstream direction, unspecified bit rate plus (UBR+) data traffic is lost or policed below the specified peak cell rate (PCR). ■ Performance monitoring traffic statistics are not reported on trunk-to-trunk VPCs. ■ After a trunk reset using the atmtrunkreset command, a few connections sometimes fail to recover with data. ■ When modifying the atm-qos profile for an active PPPoE call, the RLIM is disabled with warning and fatal error messages. To avoid the situation, stop traffic or disable the call before modifying the atm-qos profile. ■ OAM support –In the CONNECTION:atm-connect-options and CONNECTION:atm-options subprofiles, setting the oam-support parameter to no to disable F5 OAM support also disables F4 OAM support. – F5 OAM is not supported on LIM-terminating connections on 72-port high- bandwidth LIMs. – This release does not support OAM on LIM-to-LIM VCCs.
Stinger MRT units
The atmvccmgr -r and atmvccmgr -t commands do not update statistics for trunk interfaces on Stinger MRT units.
Known issues and limitations with LIMs and trunk modules The following issues and limitations are known to exist in TAOS 9.9.1.
Known VDSL LIM issues
■ The system sometimes generates FE29 messages (openConnection)and (atmCktMgrOpenVcc) and enters the DIAG state, resulting in loss of service. To recover from the situation, disable and then reenable the slot. ■ With ADSL2+ traffic flowing, if the ADSL line is retrained to ADSL2 rates, traffic stops. The line recovers when the traffic rate is reduced to ADSL2 rates. ■ The system generates harmless log messages as calls are established or dropped on the VDSL LIM (atmif_GetCTECounters) and when the LIM is reset (CB_CARDINFO). ■ Ethernet QoS shaping is inaccurate at high rates. ■ The VDSL LIM supports ADSL and ADSL2+ modes on the ADSL ports of the LIM. When the VDSL line is set to ADSL2 mode, the operational mode is G.DMT.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-13 Notices, known issues and limitations Known issues and limitations with LIMs and trunk modules
■ VDSL2 support: Training the line from VDSL to VDSL2 rate can take up to 10 minutes. ■ Supported settings: – Bit swapping is enabled by default; it cannot be disabled for ADSL, ADSL2+, VDSL, or VDSL2 services. – Impulse noise protection settings are currently supported only for ADSL2+, VDSL1, and VDSL2. – The upstream power backoff setting, upbo parameter, is supported only for VDSL1; it is currently not supported for VDSL2, and is not applicable to ADSL/ADSL2+. – Interleave delay settings are currently supported only for ADSL1, ADSL2+, VDSL1, and VDSL2. For related parameters, see the VDSL Line Interface Modules (LIMs) Module Guide. ■ The system generates timeout failure code=0 message after a VDSL LIM resets. This message is not service affecting. ■ Modem interoperability – Thompson SpeedTouch modems running firmware version 5.3.3.4: Lines operating in ADSL mode reset randomly, which adversely impacts LIM stability. To avoid this condition, set the ignore-lineup parameter to yes. – Millinet MVL100D4LR modems running firmware 1.0.7r13IK104012: At distances greater than 2000 feet, upstream rates decrease to approximately 8Mbps. – ECI B-Focus USB modems fail TR67 due to low upstream rates and for failure to train at 3000 feet. – For all modems tested, Upstream Attenuation is reported as zero; Downstream Attenuation values are inconsistent. ■ Set-Top Boxes (STB) for IPTV video applications – i3Micro Set-Top Boxes have been verified to work with the VDSL LIM in this release. – Amino 110 Set-Top Boxes will require an Ethernet hub to connect Millinet VDSL modems. The Millinet modems run on firmware version 2.0.2r3. – Based on the STB type, an Ethernet hub might be required to connect to Millinet VDSL modems.
ADSL LIM limitations
■ High bandwidth (HB) LIMs (STGR-LIM-AP-72-HB and STGR-LIM-AP-48-HB) – The HB LIMs reset with FE1 and Index 95 during channel zapping tests. Channel zapping tests are not typical customer scenarios. – The HB LIM resets with FE40 and FE50 (commonExceptHandler) messages when modems are power-cycled while traffic is passing.
5-14 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations Command-line interface limitations
– On the 72-port HB LIM, using SNMP to run a self test causes the system to generate fatal error FE74 messages, resulting in loss of service on all ports. ■ Annex-M modem interoperability – ENI 4200 / ENI 6520 modems Reach is at least 12000 feet for all masks. While operating in FAST (low latency) mode, high CRC bursts occur on some loops between the range of 1000 to 5000 feet. – TECOM AH4021 and AH4222 modems: Annex-M interopabilty is not supported with the TAOS 9.9.1 release. ■ With ADSL2+ traffic flowing, if an ADSL line is retrained to ADSL2 rates, traffic stops flowing. The line recovers when the traffic rate is reduced to ADSL2 rates. ■ On ADSL 48-port G.lite LIMs (STGR-LIM-AD-48), a few enabled ports remain in a NOT-UP state and modems are unable to train. A LIM reset is required to resolve the situation. ■ Annex-B LIPMs (STGR-LIPM-AB2-72-HB): Port flapping occurs when the LIM operates at temperatures approaching the hot and cold ends of the supported range. ■ 48-port ADSL LIMs (Conexant-based): After several days of uptime, performance monitoring counters report invalid values.
48-port and 72-port SHDSL LIM limitations
■ A line on a 48-port or 72-port SHDSL LIM that is configured for analog loopback cannot be configured for digital loopback without a LIM reset. ■ TAOS 9.7.0 and later releases support 72-port SHDSL LIMs revision 18 or higher and 48-port SHDSL LIMs revision 8 or higher. Earlier LIM versions might require hardware upgrades.
T1 IMA LIM limitation
When deleting connections on a legacy 24-port T1 IMA LIM, the system generates fatal error FE1 messages. This scenario does not typically occur in customer setups.
Command-line interface limitations
■ The system does not verify if invalid values are being used with the cltactivate command. ■ When telneting to a system, the setting for the name parameter in the system profile must not exceed 27 characters. ■ The chassidesc command incorrectly identifies the Stinger FS+ unit as Stinger FS.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-15 Notices, known issues and limitations Copper loop testing limitation
Copper loop testing limitation
Stale relay settings can cause erroneous cooper loop test (CLT) results. A stale relay on a line protection module (LPM-RP) or CLT module is an active relay that is connected to the sparing bus or test head, which cannot be cleared except by reseating the module.
Known issues and limitations with SNMP
■ No option is available for resetting a remote shelf using SNMP. To reset a remote shelf, use the command-line interface command reset -s shelf_ID. ■ When an SNMP query is sent to a Stinger system on which SNMP access is disabled, no snmpIllegalAccessAttempt trap is generated and no traps for SNMP authentication failures are sent to Navis® management software. However, system data and configuration safety remain uncompromised.
Known issues and limitations with PPPoA over LLC
■ An L2TP call fails to come up if you bring down an L2TP call over PPPoA with LLC encapsulation and then try to bring it up with PPPoA over VC-mux. ■ Problem with multicast on PPPoA with LLC encapsulation does not enable the use of multicast on PPPoA with LLC encapsulation. For multicast on PPPoA, use PPPoA over VC-Mux encapsulation.
5-16 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations Known issues and limitations with G.Bonding
Known issues and limitations with G.Bonding
■ This feature does not support LIM module and port sparing. ■ When G.Bonding is enabled on the system, the atmvccmgr command is not available for troubleshooting. To make the atmvccmgr command available for troubleshooting, do not apply QOS profile to the connection profile. On non-G.Bonded systems, the atmvccmgr command is available. ■ No connection profile can be saved to non-operational gbond group. The workaround is to save the connection profile with "active = no", otherwise you get the atm-if-config error. ■ For LIM, that is used exclusively for GBOND, packet discards occur for this release when overall throughput on the HBLIM in the downstream direction exceeds 400 Mbps. Ensure that the engineer traffic on LIM does not exceed 400Mpbs. ■ GBOND groups do not come up when ports greater than 62 are configured as part of the GBOND group for 72 port HBLIMs. Do not configure ports greater than 62 (63-72) as part of a GBOND group. ■ Connections associated with a GBOND group do not come up when ignore- lineup is used for that group. Do not use ignore-lineup with GBOND groups. ■ When a GBOND line goes down or is disabled (al-dmt enable=no), all connections on the GBOND group bounce (go down and come back up). There is no workaround and connections will recover automatically. ■ Sometimes after a LIM is inserted or bounced, the group comes up but does not include all of the links. After LIM insertion or bounce, check the num-links in gbond-group-stat profile to verify that the proper number of links are active. If not, toggle the GBOND group to recover. ■ GBOND connections are not restored after IP2100 switchover. To restore GBOND connections, toggle GBOND groups after switch over. ■ After pulling and reinserting a LIM into the chassis, some gbond groups do not become active when the LIM recovers. Toggle the al-dmt profile for each link shown to be uni-mode for Gbond groups that do not recover after LIM reinsertion. ■ Errors for GBOND Groups are not getting reported by the gbond-group-stat command. Open the lim console and issue the gbond -cg
Known issues and limitations with PPPoE calls
■ PPPoE calls do not come up after resetting Stinger in the presence of downstream traffic. This issue impacts LCLIM (Wintegra based LIMs) only.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-17 Notices, known issues and limitations Known issues and limitations with traffic flow on ports
Known issues and limitations with traffic flow on ports
■ The traffic does not flow on the affected ports in the following conditions: – When the ep-72-gs-adsl2plus or stngr-72-gs-adsl-card LIMs are deployed. – When the Firmware Conexant release D57.3.23 is running on the LIMs. – When the ADSL port is disabled using set enable = no. – When the modem remains online and line-state = active. – When rx-signal-present = yes – When dev-line-state = port-up Bounce slot (Bring down and then bring up the slot) to get the traffic flow working.
Known issues related to RADIUS support
■ For RADIUS authenticated MPoA (RFC 1483) calls, static routes are not automatically added to the network processor or main Stinger routing table. To add the static routes to the routing tables, use local profiles. ■ When an ADSL line resets frequently (for example, every two seconds) leaks can occur on the RadAcctCallLogInfo for the LIM. This condition is not a typical scenario. ■ When RADIUS accounting is disabled, account failsafe error messages are displayed for slots for a large number of nonexistent shelves. Also, the debug command acct-failsafe -d displays information for nonexistent shelves.
5-18 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations Known issues related to SELT on VDSL LIM
Known issues related to SELT on VDSL LIM
■ Recommend not to do any administrative work on the LIM while running the test. Do not attempt to provision ports or change line profiles at the same time SELT is running. Current SELT performance is: – loop estimation from 300 to 9000 feet with +-10 percent accuracy; accurate (less than 10 percent chance of error) – termination detection, open or short, for loops between and including 1000 feet and 9000 feet ■ Loop estimation below 300 feet and greater than 9000 feet will result in display of erroneous results and setting of an error flag in PC version of SELT analysis GUI. For more details, see Ikanos SELT GUI documentation. ■ Loop termination detection for loops below 1000 feet is not guaranteed with any degree of accuracy.
Known issues related to ADSL/ADSL2+
These issues are specific to ADSL/ADSL2+ operation on the VDSL Ikanos LIM, and do not apply to the Conexant LIM. ■ Low US rates against some modems. Cannot meet TR-067 required US rates. ■ Occasional NE FEC/HEC bursts. Typically seen at show time but not in steady state.
Known issues related to VDSL2
■ FE reporting of SNR and attenuation is not reliable against most modems. ■ US power reporting is invalid at times.
End of sale for Stinger products Table 5-6 lists Stinger HW/SW products that have been discontinued and their recommended replacement products. Orders for discontinued products are no longer accepted. Product warranty, repair, and technical support programs will continue for the duration of existing contracts. The recommended replacement products (if any) provide equivalent functionality and will be manufactured and supported until further notice. Replacement products might be priced higher than the products they
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-19 Notices, known issues and limitations End of sale for Stinger products
replace. No additional software enhancements or bug fixes will be provided for discontinued products.
Table 5-6. Discontinued Stinger hardware and software products
Product Stinger unit Discontinued product Replacement product code code
TAOS operating Stinger FS STGR-SR-STD STGR-SR-STD-9X system Stinger LS STGR-SR-STD STGRLR-SR-STD-9X Stinger RT
Base unit Stinger FS STGR STGRFSP Stinger FS+ STGR-R STGRFS
Control module ver- Stinger FS STGR-CM-A MODEL-CM-A2 sion 1 Stinger FS+ Stinger LS STGR-CM-B STGR-CM-C STGR-CM-A-J
Stinger RT STGRRT-CM STGRRT-CM-A-MODEL1 STGRRT-CM-A2-MODEL
STGRRT-CM-B STGRRT-CM-C
Line Protection Stinger FS STGR-LPM-24 STGR-LPM-48 Module (LPM) Stinger FS+ STGR-LPM2-48-S STGR-LPM2-48-S-NPS STGR-LPM2-72
Stinger LS STGRLS-LPM-24 STGRLS-LPM-48 STGRLS-LPM2-72
Stinger RT STGRRT-LPM-24 STGRRT-LPM-48 STGRRT-LPM2-72 STGRLR-LPM2-48-S
LPM with Stinger FS STGR-LPM-24-RP STGR-LPM-48-RP redundancy Stinger FS+ STGR-LPM2-72-RP
Stinger LS STGRLS-LPM-24-RP STGRLS-LPM-48-RP STGRLS-LPM2-72-RP
Stinger RT STGRRT-LPM-24-RP STGRRT-LPM-48-RP STGRRT-LPM2-72-RP
PCMCIA flash mem- Stinger FS STGR-SP-FLASH STGR-SP-FLASH-64 ory card Stinger FS+ Stinger LS
5-20 Stinger True Access® Operating System (TAOS) 9.9.1 Release Note Notices, known issues and limitations End of sale for Stinger products
Table 5-6. Discontinued Stinger hardware and software products (Continued)
Product Stinger unit Discontinued product Replacement product code code
ADSL line interface Stinger FS STGR-LIM-AD-24 STGR-LIM-AD-48 module (LIM) Stinger FS+ STGR-LIM-AL-48 STGR-LIM-AD-72 Stinger LS STGR-LIM-AP-48 STGR-LIM-A2P-48-HB STGR-LIM-AP-72 STGR-LIM-A2P-72-HB
Stinger RT STGRRT-LIM-AD-24 STGRRT-LIM-AD-48 STGRRT-LIM-AD-72 STGR-LIM-A2P-48-HB STGR-LIM-A2P-72 STGRRT-LIM-AP-48 STGRRT-LIM-AP-72
SHDSL/HDSL2 LIM Stinger FS STGR-LIM-H2-32 STGR-LIM-SL-48 Stinger LS STGR-LIM-SL-72
Stinger RT STGRRT-LIM-H2-32 STGRRT-LIM-SL-48 STGRRT-LIM-SL-72
Copper Loop Test Stinger FS STGR-CLT STGR-CLTE (CLT) module Stinger LS STGRLS-CLT-24 STGRLS-CLTE-72 STGRLS-CLT-48
Stinger RT STGRRT-CLT-24 STGRRT-CLTE-72 STGRRT-CLT-48
Stinger T1000 STGR-T1000-LIM2 IP2000 module
PNNI Stinger FS STGR-SO-PNNI
Stinger LS STGRLR-SO-PNN Stinger RT MRT-SO-PNNI
1. TAOS 9.9.1 includes software support for control module STGRRTCM-A with 128MB. See “Clarification about support for STGRRT-CM-A control modules with 64MB” on page -4. 2. Availability has been discontinued with the TAOS 9.8.0 release. The IP2000 control module is functional replacement as an IP module, but not a feature-by-feature replacement.
Stinger True Access® Operating System (TAOS) 9.9.1 Release Note 5-21