ZHONE Firmware/Software/Hardware Release Notes
ZHONE- PROPRIETARY
THIS DOCUMENT CONTAINS PROPRIETARY INFORMATION OF ZHONE CORPORATION AND IS NOT TO BE DISCLOSED OR USED EXCEPT IN ACCORDANCE WITH APPLICABLE AGREEMENTS.
Unpublished and Not for Publication
|
Release Number: 02.05.01 |
Date: |
|||
|
Release Type: Major |
Country Type: N/A |
|||
|
Release History |
Affected Product Models: See Below |
|||
|
Release |
Type |
Date |
Model |
Description |
|
02.05.01 |
Major |
2/12/2007 |
ALL |
Major |
|
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-423, ADSL2+ Annex B SHDSL 2671-A2-424, 2671-A2-425, 4279-A2-520 MLPPP-ADSL2+
2624-A1-422, 4224-A1-520, 4224-A1-522, 4224-A1-530, 4224-A1-532, 4234-A1-522, 4234-A1-532 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 |
9/14/2005 5/25/2005 4/8/2005 |
Revision-A Processors ADSL2+ Annex A 2621-A2-423, 2621-A1-424, 2621-A1-434, 2671-A1-424, 2671-A1-425, 4279-A1-520 REACH DSL 2611-A1-4XX 4219-A1-5XX MLPPP-ADSL2+
2624-A1-430, 4224-A1-522, 4234-A1-522, 4234-A1-532 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 |
|
02.00.15 |
Minor |
4/8/2005 |
ADSL2+ Annex A 2621-A2-423, 2621-A1-424, 2621-A1-434, 4279-A1-520 |
Minor Release |
|
02.00.08 |
Major |
8/23/2004 |
2621-A2-420, |
Major Release |
|
02.00.03 |
Initial |
6/30/2004 |
2671-A1-420, |
Initial Release |
1. Feature Enhancements / Functional Changes
Ø Added
IP Filters
Notes: DSLAMs running
firmware versions prior to 02.01.00 have to be upgraded with the
BS2600_REVA_020501.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_020501.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
|
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. |
|
MAUI (Management Uplinks and |
868-7451-8000 |
MAUI GigE with Wintegra Rev B chipset. |
|
2621-A1-420, |
868-6516-8001 |
BS2600 ADSL2 Annex A Main
Card Broadcom Release 06.03.08 |
|
4229-A1-520, |
868-6303-8001 |
4200IP ADSL2 Annex A Main
Card Broadcom Release 06.03.08 |
|
2621-A2-420, 2621-A3-420 |
868-6781-8000 |
BS2600 ADSL2+ Annex A Main Card Broadcom Release 06.03.08 |
|
4229-A2-520, 4229-A3-520 |
868-6779-8000 |
4200IP ADSL2+ Annex A Main
Card Broadcom Release 06.03.08 |
|
2631-A2-425, |
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 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
version 02.00.03 or greater |
|
T1E1 |
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_020501.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_020501.bin
Upgrading 1.0 f/w and 2.0 f/w to 2.5 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_0205xx.bin and BS2600_ALL_0205xx.bin. Any DSLAM running either a 1.0 or 2.0 build, must download the BS2600_REVA_0205xx.bin file first. Once this version is loaded on the DSLAM, then any subsequent BS2600_ALL_0205xx.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.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
PDYN#!configure
filter ip
Use
the Filter IP command to create, modify, and delete filtering rules
that can be applied to each connection on every port. The rules define
criteria to be checked in order to either forward or drop a packet. The order
that the criteria are checked is determined by the filter priority matrix.
After
you create the rule, you must add the rule to a filter profile. The filter
profile must then be bound to a connection on a port. Finally, the priority
matrix must be adjusted to determine the order in which the rules are
applied.
1. All filter rules are
Ingress (into the DSLAM) rules only. The system does not filter traffic
leaving the DSLAM.
2. These rules do not
filter multicast traffic. Multicast traffic has an IP address between 224.0.0.0
and 239.255.255.255.
3.
Every condition specified in the rule must be met in order
for the rule to be considered a match. For example, if you enter a source IP
address and a destination IP address, then both of those addresses must match
in order for the rule to be considered a match.
PDYN#!configure
filter ip ?
profile Configure IP filter profiles.
rule Configure IP filter rules.
rule-igmp Configure IGMP filter rules.
PDYN#!configure filter ip rule ?
create
Create an IP filter rule.
delete
Delete an IP filter rule.
modify
Modify an IP filter rule.
show Show IP filter rule(s).
PDYN#!configure filter ip rule create <rule_name>
PDYN#!configure filter ip rule modify <rule_name>
bind-to-profile Add or Delete a
rule binding to/from a specific IP profile
dest-ip-address Configure the
destination IP address and subnet mask for the specified rule.
dest-port-compare-type Configure the destination port comparison type for the specified
rule.
dest-port-max
Configure the maximum port value for the destination IP address for the
specified rule.
dest-port-min Configure
the minimum port value for the destination IP address for the specified rule.
icmp Configure the ICMP filter for the specified rule.
rule-name
Specify a different name for the IP filter name.
src-ip-address Configure
the source IP address and subnet mask for the specified rule.
src-port-compare-type Configure the source port comparison type for the specified
rule.
src-port-max
Configure the maximum port value for the source IP address for the
specified rule.
src-port-min
Configure the minimum port value for the source IP address for the
specified rule.
tcp
Configure the ICMP filter for the specified rule.
udp Configure the ICMP filter for the specified rule.
PDYN#!configure filter ip profile
create
Create a filter profile.
delete
Delete a filter profile.
modify
Modify a filter profile.
show Show Filter Profile(s). If no profile name is entered all filter profiles are displayed.
PDYN#!configure filter ip profile create <profile_name>
PDYN#!configure filter ip profile modify <profile_name>
bind-ingress-ports Bind the Filter profile to specified ingress ports.
dhcp
Configure the DHCP for the specified profile
icmp
Configure the ICMP rule for the specified profile.
igmp
Configure the IGMP rule for the specified profile.
profile-name Specify a different name
for the profile.
tcp
Configure the TCP rule for the specified profile.
udp
Configure the UDP rule for the specified profile
rule Add or delete rules from this profile.
PDYN#!configure filter ip rule-igmp
create
Create an IGMP filter rule.
delete
Delete an IGMP filter rule.
modify
Modify an IGMP filter rule.
show Show IGMP filter rule(s).
PDYN#!configure filter ip rule-igmp create <rule-name>
PDYN#!configure filter ip rule-igmp modify <rule-name>
bind-to-profile Add or Delete a rule binding
to/from a specific IP profile.
multicast-ip-address Configure the multicast IP address and subnet mask for the
specific rule.
igmp
Configure the IGMP filter for the specified rule.
rule-name Specify a different name for the IGMP filter rule.
PDYN#!configure filter ip rule-igmp modify <rule-name>
igmp
discard
Configure the IGMP filter to discard for the specified rule.
forward
Configure the IGMP filter to forward for the specified rule.
ignore Configure the IGMP filter to ignore for the specified filter.
PDYN#!configure filter ip rule-igmp modify <rule-name>
rule-name
<rule-new-name> Enter the new name for the rule.
PDYN#!configure filter ip rule-igmp modify <rule-name>
bind-to-profile
<ip-profile-name> Enter profile name to add or delete rule binding.
PDYN#!configure filter ip rule-igmp modify <rule-name>
bind-to-profile
test <ip-profile-name
add Add rule binding to specified profile
name.
delete Delete rule binding from specified profile name.
PDYN#!configure filter ip rule-igmp modify <rule-name>
multicast-ip-address <ip-address> <multicast-subnet>
<ip-address> Enter the multicast IP address for the specified ip filter rule
<multicast-subnet> Enter the multicast subnet mask for the specified IGMP filter rule.
PDYN#!sh filter ip
profile Show IP filter profiles
rule Show IP filter rules.
rule_igmp Show IGMP filter rules.
Here’s an example creating the filter and binding it to a port:
PDYN#!configure filter ip rule create dhcp1
PDYN#!configure filter ip rule modify dhcp1
src-port-min 67
PDYN#!configure filter ip rule modify dhcp1 udp
discard
PDYN#!configure filter ip rule modify dhcp1
src-port-compare-type eq
PDYN#!configure filter ip profile create dhcp1
PDYN#!configure filter ip profile modify dhcp1
bind-ingress-ports all-ports
PDYN#!sh filter ip profile
Profile Name
============
dhcp1
PDYN#!sh filter ip rule all
Rule Name
=========
dhcp1
PDYN#!sh filter ip rule rule-name dhcp1
***********************************************************
Rule Name
dhcp1
Rule Owner
management
Rule Type
EMC
Reference Count
0
ICMP Rule Action
ignore
TCP Rule Action
forward
UDP Rule Action
discard
Source Address
0.0.0.0
Source Address Mask
0.0.0.0
Source Port
Comparison Type equal
Source Port
Low
67
Source
Port High
0
Destination Address 0.0.0.0
Destination Address Mask
0.0.0.0
Destination Port Comparison Type
ignore
Destination
Port Low
0
Destination
Port High
0
Rule to
Profile Binding(s)
***********************************************************
sh filter ip profile dhcp1
*****************************************************************************************
Profile Name
dhcp1
DHCP Snooping
enabled
Default Action TCP
forward
Default Action UDP
forward
Default Action ICMP
forward
Default Action IGMP
forward
Discard Fragment
enabled
Owner
management
Reference Count
192
Number Of DHCP Rules 0
Number Of EMC Rules
0
Number Of MFC Rules
0
Rules Bound to Profile
Configured Ingress Connections All
Ingress Network and Subscriber Ports
Current Ingress Connections