Specifications

Features in 291-17 8
Version 291-18
C613-10488-00 REV Q
CR00022946 DHCP 2 Previously, when you created a DHCP user-defined option, a null byte was
attached to the end of any defined string. For example, if this option was
specified:
add dhcp option=99 policy=name type=string value=acme
then when this option was included in a DHCP message, a null byte was
added to “acme”, making the string 5 bytes long.
This behaviour has changed based on the option number. For options
numbered between 0 and 86, the null byte is still added to the end of the
string. For options numbered 87 and higher, the null byte is not added. If
you override a predefined option in the range of 0 to 86 with a user-defined
option, it will continue to append the string with a null byte for backwards
compatibility.
This is to meet the requirements of both RFC 2131 and 2132. RFC 2131,
which defines the DHCP protocol, explicitly states that certain string fields
should be null terminated (specifically options 12 and 67). This RFC and
others before it have led Allied Telesis routers and switches to null terminate
string-based options from 0 to 86. However, RFC 2132, which defines
further DHCP and BOOTP vender extensions, clarifies that string fields
should not be null terminated.
Note that you can use the hexstring parameter if you want to have a value
that does not have the null byte appended for DHCP options between 0
and 86.
YYYYYYYYYYY
CR00023047 IPsec 2 Under certain IPSec policy configurations with multiple policies numbering
above 24, the throughput performance of IPSec was not linear across the
increasing number of policies. This issue has been resolved.
YYYYYY––– ––
CR00023261 STP,
EPSR
2 Sometimes, under sustained broadcast storm conditions and following an
STP topology change or an EPSR ring state change, the switch would
restart.
This issue has been resolved.
––––––––YY–
CR Module Level Description
AR44x / AR450 AR7x5 AR750S / AR770S Rapier i Rapier w AT-8800 AT-8600 AT-8700XL AT-8948 / x900-48 AT-9900 AT-9800