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.03.11			Date: 3/22/2006
Release Type: Major			Country Type: N/A
Release History			Affected Product Models: See Below
Release	Type	Date	Model	Description
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

Ø ADSL2+ Bonding (2-Pair)

Ø SHDSL.Bis Extended Rates Enhancements (New SHDSL DSP code)

Ø Rate Limiting Traffic Profile per Priority Group

Ø Mulitcast Filtering (When upgrading Multicast Filtering is disabled by defaults)

Ø Single Apply Configuration Save

Ø Web Interface updated with Zhone Logo and color scheme

Ø Web Logout feature added

Ø Resolves customer issues with telnet sessions hanging

Ø Access list enhancements

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

DSLAMs with Revision –A processors with firmware 2.1.0 or later use file BS2600_ALL_020311.bin

DSLAMs with Revision –B processors with firmware 2.1.0 or later require a two step upgrade first load file BS2600_ALL_020300.bin. Then load BS2600_ALL_020311.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
PDNaa19129	Get login prompt even though not in access list
PDNaa19124	Firmware upgrade failed – BOOTROM corrupted The firmware upgrade from 02.02.08 or 02.02.10 to 02.03.06 on DSLAMs with Revision-B processors.
PDNaa19130	Heater Self Test Fail after upgrading to f/w 2.03.06.
PDNaa19122	20 Telnet sessions hangs mgt intf Upon opening 20 telnet, connection that never completely logged into the unit will cause what appears to be management of the unit locked up. You can ping the unit but it does not respond to SNMP, Web or Telnet.
PDNaa19137	Uplink Tag Base Vlan and Index value is not saved across restart
PDNaa18797	4279: After Upgrade Pairs are showing swapped Symptoms: After the customer upgraded the DSLAM from 02.00.03 to the 02.01.16 firmware they noticed that they have to go and swap pairs in order for the SHDSL lines to come up in 4-wire mode.
PDNaa18088	4279: Intermitent SHDSL Line Errors cause data errors Symptoms: The syslog is full of threshold traps for LOSW. The SHDSL DSL Statistics screen contains NE errors for LOSW and UAS in each interval, even though the line is up.
PDNaa19066	Losing management access via telnet
PDNaa12808	Incorrect Loss of Signal Counters Symptoms: Port 3 on the BS2600 was reporting 64787 seconds of loss of signal which translates to 17 hours.
PDNaa19136 PDNaa19139	Web Interface: Rate adaptive mode set incorrectly Symptoms: In the web intf under -> Configuration -> Line Profile -> <profile name> there is a setting for "Rate Adaptive Mode", with values "Manual", "Init" and "Dynamic". There was a mismatch between the web and the SNMP values for the corresponding setting.
PDNaa16815		Unable to populate entry in Security IP table Symptoms: Configuring three IP address' (X.X.X.107, .10, .109) on the Security IP screen for port 8. IP address X.X.X.107 would take but not be displayed. Added other address' no problem. Tried adding the entry via CLI, same result. Reboot the the DSLAM, the .107 address was populated in the IP table. Reported in F/W 02.00.08
PDNaa16899		4229: DSL stat screen reports 900 errored secs in all fields with port trained. Symptoms: The link is up at 7.6M/896K, yet the Status->DSL Statistics Screen is reporting 900 LOSS, ES, SES, UAS , etc.
PDNaa18391		4229: Current snr margin for far end and near end are reversed on CLI Symptoms: Enter the command "show int dsl 25 status". The near end snr reads 13.5 and the far end reads 6.4 while the mib shows them as being the reversed.
PDNaa18881		CLI does not except "-" character Symptoms: The customer entered the following port name from the web intf, but received an error when they attempted to enter it on the CLI. Example: T123-456-7890
PDNaa19190		SHDSL: 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.
PDNaa19078		CLI: get error message when changing the linkupdown trap parameter Symptoms: Customer reported that you get an error message when trying to change the linkupdown trap parameter. The command was: configure interface dsl all linkupdown-trap disable
PDNaa18390		Radius modification. The NAS-IP-Address is missing for huntgroups Add NAS-IP-Address in RADIUS Request packets to support Hunt Groups.
PDNaa18978		Exception Dump-emWeb suspends displaying Bits per Tone Symptoms: Selecting the Display Bits per Tone button from the DSL performance screen caused the DSLAM to reset.
PDNaa18076		4279: SHDSL stats not starting at zero for each new bucket Symptoms: Every 15 minute interval reports the same number of SHDSL-layer errors, but there have actually been no errors. "inf stats" on the console shows the total number of errors is the same as the contents of each interval (i.e. each bucket shows 3 ES but inf stats shows 3 ES total since reset).
PDNaa18824		CLI - Add Rate Limiting Traffic Profile CLI Commands
PDNaa18809		False Fan Low RPM Alarm
PDNaa18886		Added SHDSL Extended Rate CLI and Web Support
PDNaa18987		CLI & Web Save & Apply Persistance support Add CLI & Web Save & Apply Persistance support under system options.
PDNaa19010		Web – Added Zhone Web Pages and add logout screen Change Web Pages color scheme to that of Zhone and add logout screen.
PDNaa19085		Added ADSL2+ Bonding CLI and Web Support

Unresolved Issues

Problem	Description
PDNaa19239	Traffic should never leak between VLANs. The multicast implementation causes multicast traffic to "leak" between VLANs..
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.
PDNaa18400	Lost Margin Issue After some time line margin starts decreasing rapidly all of a sudden. At first glance it looks like impulse noice. Sometimes all margin is lost and the line retrains. Sometimes the "normal" margin recovers, until the cycle begins over.
PDNaa18767	Reach dsl ports retrain again after being administratively disabled
PDNaa18982	ADSL ports trying to train with no CPE attached
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.
PDNaa19163	With Access List enabled you can delete the only entry With the Access control list enabled you can delete the only entry that has access to the box. Which causes you to lose mgmt access. The only way to recover is via the console or to reboot unit.
PDNaa19260	Cannot pass OSPF or RIP multicast protocols
PDNaa19332	ADSL: MIB Walks on SELT and/or DELT timeout sometimes A MIB walk on the pdnAdslSeltTable and/or pdnAdslLineExtTable intermittently stall and timeout.
PDNaa19381	MLPPP: SNMP Walk fails in the pdnPppMlBundleStatusTable
PDNaa19397	SHDSL: Attainable Rate always reporting "0".
PDNaa19408	MLPPP bundle recovery time takes too long after loss of a link
PDNaa19404	ADSL Bonding - data does pass when primary line is pulled

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-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	868-6781-8000	BS2600 ADSL2+ Annex A Main Card Broadcom Release 06.03.08
4229-A2-520, 4229-A2-530, 4229-A2-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	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 2.1.0 have to be upgraded with the BS2600_REVA_020311.bin file, before upgrading to a later build. Otherwise the Download will fail.

DSLAMs with Revision –A processors with firmware 2.1.0 or later use file BS2600_ALL_020311.bin

DSLAMs with Revision –B processors with firmware 2.1.0 or later require a two-step upgrade first load file BS2600_ALL_020300.bin. Then load BS2600_ALL_020311.bin

Upgrading 1.0 f/w and 2.0 f/w to 2.3 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_0203xx.bin and BS2600_ALL_0203xx.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 located at the following URL:
http://www.paradyne.com/tech_support/mibs.html

8. New CLI Commands

Rate Limiting Traffic Profile CLI Commands

configure interface shdsl-profile-traffic create <name> (Create a SHDSL traffic profile)

configure interface shdsl-profile-traffic max-rate <rate> <name> (Configures the maximum rate allowed for the specified traffic profile)

configure interface shdsl-profile-traffic port-activate <name> <port #> (Activates a specified SHDSL traffic rofile onto the specified port(s).)

configure interface shdsl-profile-traffic port-deactivate <name> <port #> (Deactivates a specified SHDSL traffic profile from the specified port(s).)

configure interface shdsl-profile-traffic delete <name> (Deletes a SHDSL traffic profile)

configure interface shdsl-profile-traffic traffic-class <select class from options below>

-data Set the traffic class to 'data' for the specified traffic profile.

-video Set the traffic class to 'video' for the specified traffic profile.

-voice Set the traffic class to 'voice' for the specified traffic profile.

configure interface shdsl-profile-traffic show (Display the SHDSL traffic profile parameters. If no profile name is specified, all traffic profiles are displayed)

*********************************

* Traffic Profile Configuration *

*********************************

Traffic Profile Name test

Traffic Class data

Maximum Rate 768 kbps

Number of References 1

Ports Bound To Profile 1:1

SHDSL.Bis Extended Rates

configure interface shdsl-extended-rate-mode

-selection Configures the extended rate mode.

-show Displays the configuration of extended rate mode

configure interface shdsl-extended-rate-mode selection

-payload5696 Enables extended rate mode for a payload of 5696 kbps specified in G.991.2, Annex F.

-diisable Disables extended rate mode.

Single Apply Configuration Save

configure system options persistance-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).

ADSL2+ Bonding Commands

configure interface dsl-bonding

-create Create an DSL Bonding group with a maximum of 6 ADSL Ports.

-delete Delete the specified DSL Bonding group.

-group-status-trap Enable or disable group status trap for the soecified DSL Bonding Group.

-name Configure an alias for a DSL Bonding Group.

-show Show the configuration for the specified DSL Bonding Group Id.

-state Disable or enable DSL Bonding Group interface for operation.

configure interface dsl-bonding 1 create <port-id> <alarm profile>

-<port-id> This is a DSL port range to be included in the DSL Bonding group. (et 1-6, or 7-12, 13-18, or 19-24). Due to hardware architecture

a maximum of 6 DSL ports can be in one DSL Bonding Group. To have 6 DSL ports in one DSL Bonding Group the lowest number port must be

1, 7, 13, or 19. Also, the port range can not span across ports 6-7, 12-13, or 18-19. Hence, a port range of 5-8 is invalid since it crosses ports

6-7.

Example:

configure interface dsl-bonding 1 create 1-6 DEFVAL

port 1 added to DSL Bonding Group, GroupId=1, GroupIndex=1

port 2 added to DSL Bonding Group, GroupId=1, GroupIndex=1

port 3 added to DSL Bonding Group, GroupId=1, GroupIndex=1

port 4 added to DSL Bonding Group, GroupId=1, GroupIndex=1

port 5 added to DSL Bonding Group, GroupId=1, GroupIndex=1

port 6 added to DSL Bonding Group, GroupId=1, GroupIndex=1

DSL Bonding Group Created. Main Port=1, Number Ports=6, GroupIndex=1

configure interface dsl-bonding 1 state

-enable Enable a DSL Bonding Group.

-disable Disable a DSL Bonding Group.

-restart Restart a DSL Bonding Group.

Other commands

configure management periodic-arp

-add Configure management IP address to periodically send ARP request.

-delete Delete IP address from ARP periodic request table

-show Display Management ARP Periodic Table.