Paradyne Firmware/Software/Hardware Release Notes

PARADYNE - PROPRIETARY

THIS DOCUMENT CONTAINS PROPRIETARY INFORMATION OF PARADYNE CORPORATION AND IS NOT TO BE DISCLOSED OR USED EXCEPT IN ACCORDANCE WITH APPLICABLE AGREEMENTS.

Unpublished and Not for Publication

Release Number: 02.04.25			Date: 9/22/2006
Release Type: Major			Country Type: N/A
Release History			Affected Product Models: See Below
Release	Type	Date	Model	Description
02.04.25	Major	9/22/2006	ALL	Major
02.04.23	Major	7/03/2006	ALL	Major
02.04.11	Major	4/22/2006	ALL	Major
02.03.11	Major	03/22/2006	ALL	Major
02.03.06 02.02.08 02.02.06	Major Major Initial	12/16/05 10/03/2005 9/14/2005	Revision-B Processors ADSL2+ Annex A 2621-A3-420, 2621-A3-423, 2621-A3-424, 2621-A3-425, 2621-A3-430, 2621-A3-431, 2621-A3-433, 2621-A3-434, 2621-A3-435, 2621-A3-436, 4229-A3-520, 4229-A3-530, 4229-A3-531 ADSL2+ Annex B 2631-A3-425, 2631-A3-435, 4239-A3-520, 4239-A3-532 SHDSL 2671-A2-420, 2671-A2-424, 2671-A2-425, 4279-A2-520 MLPPP-ADSL2+ 2624-A1-420, 2624-A1-422, 4224-A1-520, 4224-A1-522, 4224-A1-530, 4224-A1-531, 4224-A1-532, 4234-A1-522, 4234-A1-532 MLPPP-SHDSL 2674-A1-420, 2674-A1-422, 4274-A1-520, 4274-A1-522 REACH DSL 2611-A2-4XX 4219-A2-5XX MLPPP-REACH 2614-A1-420, 2614-A1-422, 4214-A1-520, 4214-A1-530, 4214-A1-522, 4214-A1-531, 4214-A1-532	Major Major Initial Release
02.02.08 02.02.06 02.01.16	Major Minor Minor	10/03/2005 9/14/2005 5/25/2005 4/29/2005 4/8/2005 2/14/2005 1/29/2005	Revision-A Processors ADSL2+ Annex A 2621-A2-420, 2621-A2-423, 2621-A2-424, 2621-A2-425, 2621-A2-430, 2621-A2-431, 2621-A2-433, 2621-A2-434, 2621-A2-435, 2621-A2-436, 4229-A2-520, 4229-A2-530, 4229-A2-531 ADSL2+ Annex  B 2631-A2-425, 2631-A2-435, 4239-A2-520, 4239-A2-532 ADSL 2 Annex A 2621-A1-420, 2621-A1-424, 2621-A1-425, 2621-A1-430, 2621-A1-434, 2621-A1-435, 2621-A1-436, 4229-A1-520, 4229-A1-530, 4229-A1-531 SHDSL 2671-A1-420, 2671-A1-424, 2671-A1-425, 4279-A1-520 REACH DSL 2611-A1-4XX 4219-A1-5XX MLPPP-ADSL2+ 2624-A1-420, 2624-A1-430, 4224-A1-522, 4224-A1-531, 4234-A1-522, 4234-A1-532 MLPPP-SHDSL 2674-A1-420, 2674-A1-422, 4274-A1-520, 4274-A1-522 MLPPP-REACH 4214-A1-520, 4214-A1-530, 4214-A1-522, 4214-A1-531, 4214-A1-532, 2614-A1-420, 2614-A1-430, 2614-A1-422, 2614-A1-435	Major Release Minor Release Minor Release
02.00.15 02.00.14 02.00.13	Minor Minor	4/8/2005 2/14/2005 1/29/2005	ADSL2+ Annex A 2621-A2-420,  2621-A2-423, 2621-A2-424, 2621-A2-425, 2621-A2-430, 2621-A2-431, 2621-A2-433, 2621-A2-434, 2621-A2-435, 2621-A2-436, 4229-A2-520, 4229-A2-530, 4229-A2-531, ADSL2+ Annex  B 2631-A2-425, 2631-A2-435, 4239-A2-520, 4239-A2-531, ADSL 2 Annex A 2621-A1-420, 2621-A1-424, 2621-A1-425, 2621-A1-430, 2621-A1-434, 2621-A1-435, 2621-A1-436, 4229-A1-520, 4229-A1-530, 4229-A1-531, SHDSL 2671-A1-420, 4279-A1-520	Minor Release Minor Release
02.00.08	Major	8/23/2004	2621-A2-420, 2621-A2-423, 2621-A2-424, 2621-A2-425, 2621-A2-430, 2621-A2-431, 2621-A2-433, 2621-A2-434, 2621-A2-435, 2621-A2-436, 2631-A2-425, 2631-A2-435, 2671-A1-420, 4229-A2-520, 4229-A2-530, 4229-A2-531, 4239-A2-520, 4239-A2-531, 4279-A1-520	Major Release
02.00.03	Initial	6/30/2004	2671-A1-420, 4279-A1-520	Initial Release

1. Feature Enhancements / Functional Changes

Ø Added Radius Authentication for web interface

Ø Added New Command Show Running Config

Ø Added support for 32 Host Address on the Sec IP table

Ø Added clear statistics button to status pages

Ø Web Timestamp for SELT/DELT

Ø Multicast Whitelisting

Notes: DSLAMs running firmware versions prior to 02.01.00 have to be upgraded with the BS2600_REVA_020425.bin file, before upgrading to a later build. Otherwise the Download will fail.

DSLAMs with firmware 02.01.00 or later use file BS2600_ALL_020425.bin

This build may upgrade the unit's bootrom. Customers should not power cycle the unit while a firmware switch is in progress. The bootrom update may take 5-10 minutes.


2. Resolved Customer Issues

Problem	Description
	Resolved Customer Issues in 02.04.25
PDNaa19652 PDNaa19715	4229 DSLAM Ports 1-12 not passing data The DSLAM show the ports as up but the speed is 0. Customers are not getting any service so we rebooted the chassis. The syslog show the Broadcom chip is not responding. Priority Date and Time Message Debug JUN 22 11:10:21 ifmPhysTable.c: 166: _doGetIoctl(): ioctl()failed for IOADSL_GET_adslAtuXPhysEntryInv.
PDNaa19741	ARP request being dropped on subscriber port Customer upgraded from 02.04.11 to 02.04.23 and now ARP request on the subscriber port are being dropped. No traffic flows upstream. However, DHCP request pass as the PC is able to obtain an IP address.
PDNaa19790 PDNaa19791	White Listing Feature does not work properly Help text was modified to clarify the operation of this feature.
PDNaa15939	Reporting large number of receive errors on GigE interface
PDNaa16023	DSL port stat counters reporting higher value than current timer value The DSL Port Statistics are inaccurate the DSLAM was reporting a higher count for ES,SES,UAS than the current timer count.
PDNaa16899 PDNaa18074	DSL stat screen reports 900 errored secs in all fields with port trained The link is up at 7.6M/896K, yet the Status->DSL Statistics Screen is reporting 900 LOSS, ES, SES, UAS , etc.
PDNaa18725	Alarm Connector does not report correctly
PDNaa18833	DSLAM Losing Mgt Access
PDNaa19670	Unable to set Querier Interval (sec.) to disable Customer is reporting that they are unable to disable the Querier Interval (sec.). The help: The valid range is 0–65535. Enter 0 to disable.
PDNaa19347	4219: Add the circuit name to the DSL Port Rate Screen The customer request we add the circuit name to the DSL Port Rate Screen similar to the 4200 ATM DSLAMs.
	Resolved Customer Issues in 02.04.23
PDNaa19329	Traffic should never leak between VLANs. Symptoms: Our multicast implementation causes multicast traffic to "leak" between VLANs. Fix: We changed the igmp code to be vlan-aware. What does this means? The multicast group will now be associated w/ a vlan. So when a subscriber joins a multicast group, a multicast group will be associated w/ the vlan the subscriber come on in.
PDNaa19649	DSLAM Losing Mgt Access Symptoms: The customer reported that they have 200 of 400 DSLAM that were upgraded to firmware 02.04.11 from 02.03.11 now have locked up. No ping, no telnet, no web and no console.
PDNaa19408	MLPPP bundle recovery time takes too long after loss of a link Symptoms: 4224 DSLAM connected to another 4224 DSLAM with 4 T1's in a Bundle, drop one link and lost pings response for 40 seconds
PDNaa19465	ETH3 Stops passing data Symptoms: Stacking fails when stack unit #1 is running 02.03.xx. All units below #1 become unreachable until #1 is rebooted. Multicast suddenly fails on isolated DSL ports. After a reboot it works again for a few hours. This problem has not been seen when ETH2 is the uplink. ETH3 interface counters are reporting huge amounts of receive errors.
PDNaa19513	MLPPP: DHCP Option 82 Issue Symptoms: The customer is reporting that when they enable Option 82 on the MLPPP DSLAMs the DHCP offer is not passed down to the subscriber. Also, the DSLAM resets when they disable the Option 82 feature.
PDNaa19547	TX Queue Dropping packets Symptoms: The customer is report no TX traffic downstream on port 20. Cells and Packets upstream incremented, but downstream counters remain unchanged. Bridge table is learning the modems MAC address. Checked the walvbTestMenu for port 153 indicates packets are being dropped.
PDNaa19646 PDNaa19700	Security IP Table Reporting Incorrect VLAN and Time Values Symptoms: Several customers are having problems getting an IP by DHCP through the DSLAM. The show security ip command (CLI), reports VLAN 0 and a large timeout value.
PDNaa19667	Web Intf: Status - DSL PVC Perf issue Symptoms: The WEB browser locks-up when trying to look at: Status / DSL PVC Performance for port 24. It works ok for ports 1 through 23 but locks up the web browser for port 24.
PDNaa19669	CLI: Problem writing configuration Symptoms: The following CLI procedure failed to apply the changes configure factory save configure management out-of-band address xxxxxxxxxx configure management inband address xxxxxxxxx configure management default-gateway xxxxxxxxxxx save restart Prior to the restart, sh man out, sh man in and sh amn def report the changes were save. When the DSLAM restarts the unit is at the default configuration.
PDNaa17264	SNMP: Unable to create or delete ATM vpi/vci by pdnAtmBridgeIwfEntry objects. Symptoms: When deleting ATM VC 0/35 from dsl port 1 by setting of value "destroy(6)" to pdnAtmBridgeIwfRowStatus.1002001.0.35 returns error. Result of snmpset to MLPPP device. snmpset -Os 192.168.5.15 private pdnAtmBridgeIwfRowStatus.1002001.0.35 i 6 genError: pdnAtmBridgeIwfRowStatus.1002001.0.35 Deletion or creation of ATM VC works from web and cli but not snmp
PDNaa18896	4219 ReachDSL : Attainable rate = Current Rate Symptoms: The attainable rate field is showing the configured rate and not the rate achievable.
PDNaa19015	Add the Circuit ID to the DSL Port Rates screen
PDNaa19282	SNMP: Erratic ifInOctets and ifOutOctets on 4219 DSLAMs Symptoms: In some instances the ifInOctets and ifOutOctest counters appear to have rolled over in a very short (60 min) period. For example), the previous hours reading of ifInOctets is 1.04GBytes, 60 min later the reading is 3.3Mbytes. It is impossible that the customer downloaded over 3Gbytes in 60 min.
PDNaa19589	4279 SHDSL DSLAM will not link to 8985 SHDSL Line card when configured for 4 wire mode.
PDNaa18054	Added daylight savings time offset
PDNaa19076	Added clear statistics button to status pages
PDNaa19402	CLI: Modify the Configure VLAN Command Symptoms: The CLI does not allow a single port to be deleted. The command was change to allow deletion and addition of single port to the VLAN. For example: PDYN#configure vlan modify 221 ports delete 18 Vlan 221 Vlan 221, 'delete' ports '18', modified successfully. PDYN#!configure vlan modify 221 ports untagged 18 Vlan 221 Vlan 221, 'untagged' ports '18', modified successfully.
PDNaa19381	MLPPP: SNMP Walk fails in the pdnPppMlBundleStatusTable Symptoms: The WAN interface was not connected, issue an SNMP walk and it failed. Returns the following error message. pdnPppMlBundleStatusRemoteToLocalEDClass.1004401 (integer) nullClass (0) Error: Too big Error index: 0
	Resolved Customer Issues in 02.04.11
PDNaa19434	Data not passing with SHDSL Extended Rate enabled.
PDNaa19190	CLI command: "Configure Interface SHDSL" does not work Symptoms: The CLI command “conf int shdsl all state disable” which should disable all SHDSL ports generates a error message (“Error Writing ifEntry to database. ifIndex=1001009,iLevel=1,Port=9”). This happens in extended mode and it seems that this error message is only generated when SHDSL ports are grouped.
PDNaa19488	CLI: Configure Access List Crashes DSLAM Symptoms: The DSLAM crashes after issuing the following command, configure management access-list create-entry 217.168.32.0 255.255.128.0 snmp telnet and then save.
PDNaa19489	MLPPP DHCP Packets not forward downstream Symptoms: When two MLPPP DSLAMs are interconnected DHCP request are not forwarded downstream to subscribers on the second DSLAM
PDNaa15939	Reporting large number of receive errors on GigE interface Symptoms: The 4200IP is reporting a large number of receive errors on the GigE stats screen. The errors are reported to occur whenever the set top box gets a firmware download, or an update to the programming guide. The development screen shows these as being rx_oversize.
PDNaa19333	CLI: VLAN ports display is confusing Symptoms: Customer reported that the Ports/PIWGS display portion of the VLAN configuration is confusing when displaying a range of ports. For example, if the following ports are configured 10:2,11:2,12:2,13:1 it is displayed as 10:2-13.
PDNaa19082	CLI: Invalid CLI access list commands can reset the DSLAM Symptoms: If you enter: configure management access-list create-entry 0.0.0.0 0.0.0.0 then you enter: the DSLAM stops responding.
PDNaa19383	CLI: Show int dsl 1 confg crashes the DSLAM Symptoms: When the DSLAM is configured for Annex-M, issuing the following command from the CLI crashes the DSLAM. Show int dsl 1 confg
PDNaa19163	With Access List enabled you can delete the only entry Symptoms: With the Access control list enabled you can delete the only entry that has access to the box. Which causes lose of mgmt. only way to recover is Console or reboot unit.
PDNaa19077	Special characters not supported in username/password The currently supported special non-alpha numeric characters are: !, @, #, $, %, ^, &, *, (, ), _, -, +, =, |, _, {, }, [, ], >, <, / ,, ;, . The '?' is excluded, because the emweb CLI engine uses the ? as a special character to display help.
PDNaa19260		Cannot pass OSPF or RIP multicast protocols
PDNaa19317		Reset needed after deleting a user ID Symptoms: The feature to delete a user ID does not really delete the user until the DSLAM is reset. The UI gives the impression that the User ID has been deleted, but you can still access the device with the deleted user ID. The only way for the user ID to be truly deleted, is to reset the DSLAM.
PDNaa12730		Add New Command Show Running Config show running-config
PDNaa14553		Make Security IP Permanent Entry in the Config File Symptoms: The current arp table entries in the 4200IP are all temporaries including the ones learned thru DHCP snooping. In the event of a reset, power failure, or firmware upgrade, all entries in this table are cleared requiring the end customer to perform a DHCP renew on their PC or Internet gateway router. This is fixed as part of the 2.4 Enhance Proxy ARP feature. The lease time saved in the database but it is not updated in realtime due to the number of writes to Flash. So if the unit resets, the DHCP entry will be created with the full lease time
PDNaa17840		Add support for 32 Host Address on the Sec IP table
PDNaa19076		Add clear statistics button to status pages
PDNaa17640		Add capability to enable/disable radius without having to delete all entries
PDNaa18267 PDNaa18684 PDNaa18685		Request to add Radius Authentication for web interface
PDNaa19050		CLI: When adding an untagged port, append it to the existing configuration
PDNaa19201		CLI - be able to delete a specific port from a vlan without having to delete all ports
PDNaa19582		CLI locks up creating DSL line profile
PDNaa18993		IGMP snooping not working properly when Unknown MCast set to drop Scenario: Two PCs running video on ports 4 and 12 and the multicast stream being supplied on eth2. With igmp snooping enabled, and all ports set to Unknown MCast flood, the join and leave from the video work normally and the intended streams are received at the PCs. When the dsl ports is set to drop and leave eth2 to flood, the joins and leaves from video do not make it to the igmp circuitry. When I have the dsl ports set to flood, and eth2 set to drop, the video joins and leaves are being processed normally but the multicast stream is being blocked from getting downstream. Added Multicast Whitelist Feature

Unresolved Issues

Problem	Description
PDNaa17793	MLPPP: Unable to transfer user data when short sequence number is not equal between the devices Unable to transfer user data over the mlppp bundle when the setting of the short sequence number is not equal between local and remote mlppp devices. This option is configured from the Configuration->MLPPPBundles screen.
PDNaa17879	MLPPP: LCP negotiation will not complete after stopped LLB. Two DSLAMs in back-to-back configuration, some PPP ports will not accept their LCP negotiation after terminated LLB on a T1E1 port.
PDNaa18767	Reach dsl ports retrain again after being administratively disabled
PDNaa18982	ADSL ports trying to train with no CPE attached on firmware 02.03.01.
PDNaa19332	ADSL: MIB Walks on SELT and/or DELT timeout sometimes A MIB walk on the pdnAdslSeltTable and/or pdnAdslLineExtTable intermittently stall and timeout.
PDNaa19397	SHDSL: Attainable Rate always reporting "0".

3. Hardware Co-Requirements

Model Number	CCA Part Number	Description
MAUI (Management Uplinks and Aggregation Interface Cards)	868-6421-5170	Hardware with new Memory Configuration. These units have 128 Meg of Packet RAM and 16 Meg of Parameter RAM.
MAUI (Management Uplinks and Aggregation Interface Cards)	868-7451-8000	MAUI GigE with Wintegra Rev B chipset. Supports only the GigE Rev B units.
2621-A1-420, 2621-A1-424, 2621-A1-425, 2621-A1-430, 2621-A1-434, 2621-A1-435, 2621-A1-436	868-6516-8001	BS2600 ADSL2 Annex A Main Card Broadcom Release 06.03.08
4229-A1-520, 4229-A1-530, 4229-A1-531	868-6303-8001	4200IP ADSL2 Annex A Main Card Broadcom Release 06.03.08
2621-A2-420, 2621-A3-420 2621-A2-423, 2621-A3-423 2621-A2-424, 2621-A3-424 2621-A2-425, 2621-A3-425 2621-A2-430, 2621-A3-430 2621-A2-431, 2621-A3-431 2621-A2-433, 2621-A3-433 2621-A2-434, 2621-A3-434 2621-A2-435, 2621-A3-435 2621-A2-436, 2621-A3-436	868-6781-8000	BS2600 ADSL2+ Annex A Main Card Broadcom Release 06.03.08
4229-A2-520, 4229-A3-520 4229-A2-530, 4229-A3-530 4229-A2-531, 4229-A3-531	868-6779-8000	4200IP ADSL2+ Annex A Main Card Broadcom Release 06.03.08
2631-A2-425, 2631-A2-435	868-7121-8000	BS2600 ADSL2+ Annex B Main Card Broadcom Release 06.03.08
4239-A2-520, 4239-A2-520	868-7119-8000	4200IP ADSL2+ Annex B Main Card Broadcom Release 06.03.08
2671-A1-420	868-6782-8000	BS2600 SHDSL Main Card Infineon DSP Release 0.9.3
4279-A1-520	868-6780-8000	4200IP SHDSL Main Card Infineon DSP Release 0.9.3
2614-A1-420, 2614-A1-422, 2624-A1-420, 2624-A1-422, 2674-A1-420, 2674-A1-422, 4214-A1-520, 4214-A1-522, 4214-A1-530, 4214-A1-531, 4214-A1-532, 4224-A1-520, 4224-A1-522, 4224-A1-530, 4224-A1-531, 4224-A1-532, 4234-A1-522, 4234-A1-532, 4274-A1-520, 4274-A1-522	868-7122-8000	T1/E1 MLPPP Uplink MAUI Hardware. Supports only the T1/E1 MLPPP units. Infineon DSP Release 0.9.3 (SHDSL) Reach DSP Release 02040 Broadcom Release 06.03.08 (ADSL2+)
2611-A1-420, 2611-A1-424, 2611-A1-425, 2611-A1-430, 2611-A1-431, 2611-A1-434, 2611-A1-435, 2611-A1-436, 2611-A2-420, 2611-A2-424, 2611-A2-425, 2611-A2-430, 2611-A2-431, 2611-A2-434, 2611-A2-435, 2611-A2-436, 2614-A1-420, 2614-A1-422	868-6515-8000	BS2600 ReachDSL Main Card Reach DSP Release 02040
4214-A1-520, 4214-A1-522, 4214-A1-530, 4214-A1-531, 4214-A1-532, 4219-A1-520, 4219-A1-530, 4219-A1-531, 4219-A2-520, 4219-A2-530, 4219-A2-531	868-6302-8000	4200IP ReachDSL Main Card Reach DSP Release 02040

4. Software Co-Requirements

Request Number	Description
MAUI Boot Code	MAUI Boot Code version 02.00.03 or greater
T1E1 MAUI Boot Code	T1/E1 MAUI Boot Code version 02.01.01 or greater
Initialization Configuration Files	Initialization configuration files
T1/E1 MLPPP Initialization Configuration Files	TIE1 MLPPP Unit Initialization configuration files

5. Compatibility with other Released Models

Notes: DSLAMs running firmware versions prior to 02.01.00 have to be upgraded with the BS2600_REVA_020425.bin file, before upgrading to a later build. Otherwise the Download will fail.

DSLAMs with firmware 02.01.00 or later use file BS2600_ALL_020425.bin

Upgrading 1.0 f/w and 2.0 f/w to 2.4 The 2600/4200 DSLAMs have been using a Rev A Wintegra part through the 1.0 and 2.0 firmware life cycles. The firmware builds for 1.0 and 2.0 have been anywhere from 3.6MB to 4.6MB in size. Because Wintegra is discontinuing the Rev A part, a Rev B part started being used on the MLPPP MAUI cards and are used on the GigE MAUI cards. The Rev A and Rev B parts cannot run the same driver code so a dual firmware image had to be created to support both versions of the Wintegra part in the 2.1 f/w baseline. These dual image files are greater than 10MB in size. The 1.0 and 2.0 f/w builds do not know how to handle the dual image file so two versions of the 2.1 f/w builds are produced. They are in the form of BS2600_REVA_0204xx.bin and BS2600_ALL_0204xx.bin. Any DSLAM running either a 1.0 or 2.0 build, must download the BS2600_REVA_0203xx.bin file first. Once this version is loaded on the DSLAM, then any subsequent BS2600_ALL_0203xx.bin files may be loaded.

CAUTION: A change was made to the 4200/2600 boot code that is incorporated into build 2.00.13 and later. When new boot code is involved in the f/w upgrade process, the upgrade takes considerably longer than it normally does. From the time the switch to the new f/w is performed, customers should expect at least a 5-10 minute period before the unit is finished with the upgrade. While the upgrade is taking place, it appears from the front panel of the unit that nothing is happening. Due to the longer upgrade period, it may cause confusion and the unit is power cycled during the upgrade of the bootrom. If this occurs, the unit will not boot again and would need to be returned to the factory. There is no way to recover from this in the field.

This code contains protection to prevent downloading incorrect firmware to the unit. The SHDSL platform will not allow downloading of any f/w file older than 2.0.0. The ADSL2+ annex A platform will not allow downloading of any f/w file older than 1.1.0. The ADSL2+ annex B platform will not allow downloading of any f/w file older than 2.0.0. New build units with the rev B GigE MAUI card will not allow code older than 2.01.19 to be loaded.

This code will migrate the configuration from the 1.0.X and 1.1.X code sets and will create a DSL line profile table that may look somewhat different. The older code platforms did not support line profiles so the migration from individual DSL port settings to a profile table was accomplished as follows. After upgrading, the line profile table will contain 24 profiles which will have the ifIndex numbers (ie 1001001) as the profile names but the config settings in the profile for each port will be left intact as they were before the upgrade. Each one of the line profiles will be assigned to the respective port#. The first time the unit is set to factory defaults, the line profile table will then have only the one DEFVAL profile, which will be assigned to all ports.

SHDSL DSLAMs and Globespan 1.5 CPE There has been an issue with the 2600/4200 SHDSL DSLAMs training in adaptive mode to cpe that have Globespan 1.5 or earlier code. This code release allows training in adaptive mode but the max rate for the line profile must not exceed 2312.

SHDSL.bis Configuration Notes: All configurations done using 4 port boundaries and the boundaries start on ports 1,5,9,13,17, and 21. In other words, all multiple pair connections must fall within any group of 4. For instance, you should not assign an 8-wire profile to port 3 and have it extend across a boundary into the next group of 4. The rate referred to in this explanation also assumes you are using modems that support extended rates (.bis). Standard rate 2-wire and 4-wire modems may also be used in the mix but be careful of the max rate for Globespan based cpe as stated in the preceding note.

In 4104 Mode: On the first group of four, ports 1-4, you could have; (four-2 wire modems each supporting a rate up to 4104), (two-4 wire modems each supporting a rate up to 8208), (one-6 wire modem supporting a rate up to 12312 and one-2 wire modem on port 4), (one-8 wire modem that supports a rate up to 16416). These rules hold true for the remaining groups of 4. In 5704 Mode: Ports 9-12 and 21-24 are not available and 5704 supports only 2-wire and 4-wire. You could have modems in 2-wire mode on all 16 available ports each getting a rate up to 5704 or you could have eight-4 wire modems on ports 1,3,5,7,13,15, and 17 supporting a rate up to 11408.

IGMP Change In code sets 1.0 and 2.0, igmp snooping enable/disable was configurable on a port by port basis. In the 2.1 code, igmp snooping is a global setting (all ports enabled or disabled). During migration from 1.0 or 2.0 to 2.1, if any port is set for igmp snooping enabled, then the global setting will be enabled.

6. Supporting Customer Documentation / Significant Changes

The following manuals support the 2600-A2 and 4200IP A2 models:

2600-A2-GN20-30   installation guide (2600)
2600-A2-GB21-20 command line reference guide (2600/4200)
2600-A2-GB22-20 SNMP reference guide (2600/4200)
4200-A2-GN21-40 installation guide (4200)

7. SNMP MIBs SUPPORTED BY THIS RELEASE

Please refer to 2600-A2 and 4200IP A2 MIBS for MIBS and associated OIDs supported by this release on the Service & Support web site.

8. New CLI Commands

Single Apply Configuration Save

configure system options persistence-mode

-apply-and-save-combined (When applying configuration automatically store to database).

-apply-and-save-separate (When applying configuration do NOT automatically store to database).

Show running-config

Clear Statistics

PDYN#!show interface shdsl shdsl

clear-statistics-atm Clear the ATM statistics for the given SHDSL port.

clear-statistics-line Clear running statistics for the specified unit, unit side, and wire pair for a SHDSL span.All intervals are

displayed if no bucket-number is specified.

PDYN#!show int shdsl shdsl clear-statistics-line stu-c

stu-c SHDSL central site terminal unit.

stu-r SHDSL remote site terminal unit.

rep-1 SHDSL renenerator/repeater unit 1.

rep-2 SHDSL renenerator/repeater unit 2.

rep-3 SHDSL renenerator/repeater unit 3.

rep-4 SHDSL renenerator/repeater unit 4.

rep-5 SHDSL renenerator/repeater unit 5.

rep-6 SHDSL renenerator/repeater unit 6.

rep-7 SHDSL renenerator/repeater unit 7.

rep-8 SHDSL renenerator/repeater unit 8.

PDYN#!show int shdsl shdsl clear-statistics-line stu-c

cust The side of the unit facing the customer teminal equipment.

PDYN#!show int shdsl shdsl clear-statistics-line stu-c cust

pair-1 First wire pair.

pair-2 Second wire pair.

pair-3 Third wire pair.

pair-4 Fourth wire pair.

PDYN#!show int shdsl shdsl clear-statistics-line stu-c cust pair-1

PDYN#configure multicast-whitelist

state Enable or disable multicast whitelisting.

add Add an IP address to the multicast whitelist table.

delete Delete an IP address from the multicast whitelist table.

show Display multicast whitelist configuration.

Note: Multicast whitelisting reduces the chances of accidental or intentional denial of service attacks.

The most common use of filtering in networks involves blacklisting. Blacklisting simply contains a list a hosts or services that need to be denied, while all other hosts or services are permitted. White lists, on the other hand, contain a list of hosts or services that are permitted, while all other hosts and services are denied.

If multicast white list filtering is enabled, the system will accept multicast traffic only from sources that are configured in the multicast white list table. If the multicast whitelist table is empty, and white list filtering is enabled, then the system will accept multicast traffic from the following IP multicast addresses only (as per RFC 3171): 224.0.0.0/8, 232.0.0.0/8, 233.0.0.0/8. All other multicast traffic shall be discarded.

If multicast white list filtering is disabled, the system will forward all multicast traffic.