Professional Documents
Culture Documents
Code
Huawei AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600
V200R007C00
Feature Delta Information
Issue 08
Date 2017/04/11
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of
products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherw
specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties
guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the preparation of this documen
ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty
any kind, express or implied.
Website: http://e.huawei.com
rights reserved.
any form or by any means without prior written consent of Huawei
by the contract made between Huawei and the customer. All or part of the
ay not be within the purchase scope or the usage scope. Unless otherwise
mmendations in this document are provided "AS IS" without warranties,
mplied.
notice. Every effort has been made in the preparation of this document to
on, and recommendations in this document do not constitute a warranty of
Purpose
This document describes changes in features and specifications of
AR120&AR150&AR160&AR200&AR1200&AR2200&AR3200&AR3600 series enterprise routers from
V200R006C10SPC300 to V200R007C00SPCc00.
Structure
Some fields are described as follows.
Field
Change Description
Affect Upgrade
Change History
Issue Date
08 2017/4/11
07 2016/10/26
06 2016/9/21
05 2016/5/13
04 2016/2/5
03 2015/11/9
02 2015/9/28
01 2015/8/15
t describes changes in features and specifications of
AR160&AR200&AR1200&AR2200&AR3200&AR3600 series enterprise routers from
PC300 to V200R007C00SPCc00.
e described as follows.
Description
Indicates the first version that these changes. (Unless otherwise stated, the
changes in earlier versions are applicable to the later versions based on the
version release sequence.)
Description
V200R007C00SPCc00
V200R007C00SPCb00
The AR configures the timestamp sent to the log server as the local time.
The system checks for port number conflicts when a VPN is conf
The TCP MSS backoff is supported.
Bandwidth management technology manages and controls traffic based
on the flow direction (inbound or outbound) of an interface, source or
destination IP address, user group, time range, and description.
Auto-Start enables the device to load version files automatically after
startup.
The device can reselect routes when transmitting IPv6 packets.
A command can be run to allow non-labeled public
Aroutes
route-policy can be used
to be iterated only toto set
LSPs.a priority for
the routes that meet the matching rules of the
route-policy. The routes that fail to meet the
Devices access the Internet through static routes. Because the cable
matching rules of the route-policy use the global
modem is deployed in the middle, static routes can be used for traffic
priority.
forwarding
If only when
a device receives the IPLSP
a purge address
with of the remote
fragment interface
number 0, theconnected
device to
the local
delays outbound
IS-IS interface istriggered
route calculation obtained byusing DHCP.
other purge LSPs sent by the
advertiser of the purge LSP, which prevents routes from being deleted
incorrectly
If a remote due to aID
system network
conflictfault.
is detected, IS-IS changes the conflicting
system ID automatically.
If a router receives a MaxAge Router LSA, the router delays OSPF route
calculation triggered by other MaxAge LSAs sent by the advertiser of the
MaxAge Router LSA, which prevents routes from being deleted
incorrectly
If an IS-ISdue toLSP
a network fault.
frequently flaps, its generation,
calculation, and forwarding will be suppressed.
If an OSPF LSA flaps frequently, its generation and reception will be
suppressed.
If the age of an LSA in the local OSPF LSDB reaches 2700s, the LSA
will be flooded so that the generator of this LSA can update it
immediately. This feature prevents LSAs from being aged incorrectly
due to a local clock fault.
N/A
N/A
N/A
N/A
The device supports MPLS MTU fragmentation in the inbound direction
of a PW.
Application names or application groups are matched.
N/A
N/A
N/A
N/A
In the trunk tandem scenario, the bearer capability can be set
to speech or 3.1 kHz audio based on a software parameter.
In the Q931 SETUP message, the call reference value is
displayed.
The reason value on the Q931 side maps the status code on
the SIP side in the AR disconnection message.
The AR supports attack prevention at the voice application
layer, that is, prevents SIP Flood DDoS attacks using the
source authentication method.
The SIP AT0 registration message is obtained from the proxy.
The AR transparently transmits fax rollback failure messages
such as 488 and 606 to downlink PBXs in IP-to-IP calls.
The AR transparently transmits the Prack message sent by the
PBX to the uplink IMS in the 183 scenario when the 181
message
The carrying media
AR performs information
processing is received
after receiving first.
the UPDATE
message
When the peer end of the SIP IP trunk is configured 181
in the SIP trunk tandem scenario when the to work
message
in carryingmode,
the DNS-SRV mediapeerinformation is received
end IP addresses arefirst.
selected
based on the configured weight ratio to initiate calls if the
configuration of theasDNS
When functioning serverthe
the eSBC, meets
AR the loading
accepts balancing
registration
condition.
requests from the IP PBX through the SIP PRA, and registers
with maximum
The the IMS through
numbertheof SIP PRA trunk.
concurrent online users is
increased from 30 to 120 on the AR161FV-1P, and increased
to 600 on the AR1220EV and AR1220EVW.
The AR newly supports the line hunting function.
The AR newly supports mappings between ISDN cause
The ARand
values newly
SIP supports the which
error codes, following function:
are also The AR can
configurable.
correctly handle the call forwarding process when receiving
the 300 message returned by the SIP trunk group, and it can
The
also AR supports
handle twomedia
the early call forwarding
negotiationmodes in Fastweb:
process after this type
single-dialog and
of call forwarding. multi-dialog, both of which support call
forwarding unconditional, call forwarding on busy, and call
forwarding
The AR newly on no reply. configurable no-response waiting
supports
time for incoming
The AR newly supports and outgoing calls in
the following Fastweb.Sending the
function:
The AR supports message conversion between
subsequent message, if it is a request message, to ISDN and SIP
the address
trunks. It also can converse the 18X message to the
specified in the contact field of the message received from
corresponding
the peer. ALERT or PROGRESS message when calls
reach the ISDN trunk and go out through the SIP trunk. It
also can converse the ALERT or PROGRESS message to the
The
18XAR supports
message whenthecalls
NOTreach
operation ontrunk
the SIP the matching
and go out result
when
throughthe caller number changes.
The AR thecan ISDN trunk.
determine whether to use a software parameter
to set the flow mode to active in the SDP when the AR
receives the message in which the flow mode is sendonly.
The AR can encapsulate require100rel in the 18X message
based on software parameters.
The AR determines whether to play the call hold tone when
the media stream is inactive based on the software
parameters.
N/A
N/A
In the source version, the system allows a non-existing IP
prefix
N/A or route policy to be specified in an IS-IS IPv4
command.
In the source version, OSPF-related commands
In the target
support version, theIP
non-existent system
prefixdoes notorallow
lists a non-
route-policies.
existing IP prefix or route policy to be specified in an IS-IS
In the target version, if OSPF-related commands with
IPv4 command. In addition, the system does not check
non-existent IP prefixIPlists
whether a non-existing ororroute-policies
prefix route policy hasspecified
been
are run, the
specified configurations
in the of the commands
configuration restoration process. fail to be
N/A
delivered, and no relevant check is performed during
configuration restoration.
N/A
N/A
A HAAP device connects to a terminal through HAAP.
In the source version, a terminal must carry the correct CIN
N/A
in the Setup-Request packet when going online over the
Overflow tunnel the first time.
In
In the
the source
target version,aifterminal
version, a nonexistent IP prefix is referenced
In
in athe source
command, version,
the when must
configuration the
is
carry
VPN the correct
configured
successful.
CIN
for in
the Auth-Request packet when going online over the
an NQA server is valid, the system checks whether
Overflow tunnel the first time.
the
In
Afterconfigured
the target
the port
version,
upgrade, ifnumber conflicts
a nonexistent
a terminal will failIP gowith
to prefix isexisting
referenced
online.
port numbers the
in a command, on configuration
the public network.
fails, and no check is
performed
In the targetduring configuration
version, restoration.
when the VPN configured for an
NQA server is valid, the system checks whether the
configured port number conflicts with existing port
numbers in the VPN.
In the source version, the backoff function takes effect
only after PMTU is enabled for the TCP connection.
In the target version, the backoff function takes effect,
regardless of whether PMTU is enabled for the TCP
N/A
connection.
N/A
N/A
In the source version, the global route priority configured
using the preference command and the priority set using a
N/A
route-policy are mutually exclusive.
In the target version, the global route priority configured
using the preference command and the priority set using a
route-policy are not exclusive. The routes that meet the
matching
N/A rules of the route-policy use the priority set using
the route-policy, and the routes that fail to meet the matching
rules
N/A of the route-policy use the global priority.
N/A
N/A
N/A
In
N/Athe source version, when an ABR in the
backbone area receives inter-area routes if
the
N/A ABR's neighbor relationship is not in
the Full state, the ABR generates Type 3
LSAs and sends the LSAs to other areas.
In the target version, when an ABR in the
backbone area receives inter-area routes if
N/A
the ABR's neighbor relationship is not in
the Full state, the ABR does not generate
N/A
Type 3 LSAs to be sent to other areas.
In the source version:
When
N/A this TCP
In the source function is enabled, the maximum TCP
version:
packet size is increased
The system does not check to the less one
whether thebetween
length ofthe outbound
a UDP
interface MTU minus 40 and the configured
N/A header is shorter than the standard UDP packet header
packet maximum TCP
MSS.
length (8 bytes).
When this TCP
In the target function is disabled, the maximum TCP
version:
packet
The size is increased to thetheleast oneofamong
a UDPthe outbound
In thesystem
interfacesource
MTU
checks whether
version:
minus 40, MSS
length
of the VP channel,
packet
the
header
The
In theMSS is shorter
value
source thanfor
used
version, the standard
thenegotiation
maximum UDP packet
during
length TCP
of anheader length
connection
assembled
negotiated
(8 bytes). IfMSS
the received
packet from
header the
is remote
shorter device,
than 8 andthe
bytes, the
setup
PIM
maximum is noTCP
less than
Join/Prune the
In value
message
MSS. is theofsmallest
addition, tcp-min mss.among
value
the maximum the
TCPsecond.
packet
device
In the
following discards
target the packet
version: and generates a log every
size cannot be less than the minimum TCP MSS. The set in
three values: join-prune max-packet-length
The
the MSSview,
PIM
maximum value used for
TCPinterface
packet negotiation
MTU,
size for and
TCPvalue during TCP used
defined
connections connection
in theforPAF
setup
file. cannot exceed
gateway routes is 512. the MTU of the outbound interface
minus
In
In the 40, which
the target
target maythe
version,
version: be maximum
less than the valueofofantcp-min
length assembled mss.
PIM
N/A Join/Prune message is the smallest value
When this TCP function is enabled or disabled, the maximum between the
following
TCP packet two values:
size remainsjoin-prune
unchanged. max-packet-length set in
the
N/APIM view and interface MTU.
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Affect
Reason for Change
Upgrade
N/A N
N/A N
N/A N
N/A N
This feature enables the AR to be compatible with
different peer devices. N
N/A N
N/A N
N/A N
N/A Y
N/A Y
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
Bandwidth management based on IP addresses or user
N
groups can be configured in the web view.
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A Y
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A Y
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
The default APN of the LTE network is configured.
N
N/A N
N/A N
N/A N
N/A N
N/A N
N/A N
Impact AR120&A AR1200AR2200 AR3200 AR3600
Y Y Y Y Y
Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y N
N/A Y Y Y Y Y
N/A Y Y Y Y Y
No
N/Arelevant check is performed during configuration Y Y Y Y Y
restoration,
N/A and the upgrade is not affected. However, route- Y Y Y Y Y
policy
N/A implementation changes. Y Y Y Y Y
In the source version:
1. Route-policies that are being used can be deleted. Y Y Y Y Y
2. Non-existent route-policies can be referenced.
In
N/Athe target version: Y Y Y Y Y
1. Route-policies that are being used cannot be deleted.
2.
N/ANon-existent route-policies cannot be referenced. N Y Y Y Y
N/A
In theansource version, OSPF-related N Y Y Y Y
After upgrade, the system does notcommands
allow a
support
non-existing IP prefix or routelists
non-existent IP prefix policyorto be
route-policies. Y Y Y Y Y
specified in an IS-IS IPv4 command, but
In the target version,
configuration if OSPF-related
restoration is not affected.
commands with non-existent IP prefix lists or Y Y Y Y Y
route-policies specified are run, the
configurations
N/A of the commands fail to be Y Y Y Y Y
delivered, and no relevant check is performed
during
N/A configuration restoration. Y Y Y Y Y
In the target version, the GRE key configuration is generated
before the source and destination address configurations in the Y Y Y Y Y
buildrun.
After
N/A a HAAP device is upgraded, the terminal cannot go Y Y Y Y Y
online. According to the conclusion provided by the solution
Impact:
department, a terminal seldom connects to a HAAP device
In
1. the
If asource
running port version, on
number
V600R009C10 if (VRP
a the
nonexistent
public IP prefix is
version:network is referenced
V500R016C70) boundandto in a N Y Y Y Y
command,
services, the configuration
any attempt
generally connects is
to bind
to a HAAP successful.
the same
device runningport number in
In
thethe target version, if
VPN for the NQA
V600R009C00(VRP a nonexistent
server
version: failsIPinprefix
V500R016C60). is referenced in a
the source version N Y Y Y Y
command, the configuration fails, and no check is performed
and succeeds in the target
during configuration restoration.version.
Y Y Y Y Y
2. If a port number in a VPN is bound to services, any
attempt to bind the same port number in the VPN for the
NQA server succeeds (invalid configuration) in the
source version and fails in the target version.
1. If PMTU is not enabled and intermediate devices do
not support packet fragmentation, TCP connections may
be interrupted.
2. If PMTU is not enabled, the packet size will not be
reduced even though packets are discarded multiple
times. Y Y Y Y Y
In the target version:
N/A
1. If PMTU is not enabled and intermediate devices do Y (Only N N N N
not support packet fragmentation, TCP connections will
N/A
not be interrupted. Y Y Y Y Y
2. If PMTU is not enabled and packets are discarded
N/A
multiple times, the packet size will be reduced. Y Y Y Y Y
N/A N Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
Route calculation on other devices may be affected, and the path
along which services are forwarded may change. Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
Y
N/A AR120
Y Y Y Y Y
series
N/A
If the length of assembled PIM Join/Prune messages defined in , Y Y Y Y Y
the PAF file is less than the interface MTU or the value AR161,
specified in the related PIM command, the maximum length of AR161WY Y Y Y Y
assembled PIM Join/Prune messages to be sent will be increased ,
after
Whenanthe AR supports fragmentation for large-sized packets, che AR161G
upgrade. N Y Y Y Y
-L,
Y
AR169,
AR120
N/A N Y Y Y
AR169G
series
-L,
,Y
N/A
and Y Y Y Y
AR161,
AR169-
AR161W
N/A YP-M9 Y Y Y Y
,
do
AR161G not
N/A Ysuppor Y Y Y Y
-L,
tAR169,
the
N/A functi N Y Y Y
AR169G
on.
-L,
N/A Yand Y Y Y Y
AR169-
P-M9
do not
suppor
t the
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A Y Y Y Y Y
N/A N Y Y Y Y
N/A Y Y Y Y Y
N/A N Y Y Y Y
N/A N Y Y Y Y
N/A Y Y Y Y Y
First Updated Version Change Type Hardware Name Hardware Description
NA NA
NA NA
NA NA
The LTE module is changed to the ME909S-120. ME906E modules will be discontinued.
The LTE module is changed to the ME909S-120. ME906E modules will be discontinued.
The LTE module is changed to the ME909S-120. ME906E modules will be discontinued.
The LTE module is changed to the ME909S-120. ME906E modules will be discontinued.
The LTE module is changed to the ME909S-120. ME906E modules will be discontinued.
The LTE module is changed to the ME909S-120. ME906E modules will be discontinued.
The LTE module is changed to the ME909S-120. ME906E modules will be discontinued.
The LTE module is changed to the ME909S-120. ME906E modules will be discontinued.
Y Y Y Y Y
NA NA N Y N N N
NA NA N N Y N N
NA NA N N Y N N
N/A N/A Y N N N N
N/A N/A Y N N N N
N/A N/A Y N N N N
N/A N/A Y N N N N
N/A N/A Y N N N N
N/A N/A Y N N N N
N/A N/A N N N N N
N/A N/A N Y Y Y Y
Y Y Y Y Y
N/A N/A N N N N N
N/A N/A N N N N N
Change
First Updated Version Feature License Change Description
Type