0% found this document useful (0 votes)
25 views13 pages

R13 7 0 Release Notes EX

The ADTRAN Operating System R13.7.0 Release Notes provide an overview of the new features, enhancements, and bug fixes included in this major system release. It supports various platforms and addresses customer issues from previous versions, with specific improvements in Carrier Ethernet functionalities. The document also includes warranty and contact information for technical support.

Uploaded by

Ashley Gibbon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
25 views13 pages

R13 7 0 Release Notes EX

The ADTRAN Operating System R13.7.0 Release Notes provide an overview of the new features, enhancements, and bug fixes included in this major system release. It supports various platforms and addresses customer issues from previous versions, with specific improvements in Carrier Ethernet functionalities. The document also includes warranty and contact information for technical support.

Uploaded by

Ashley Gibbon
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

ADTRAN Operating System

R13.7.0 Release Notes


Release Notes
6AOS1370-40A
April 2020
To the Holder of this Document

To the Holder of this Document


This document is intended for the use of ADTRAN customers only for the purposes of the agreement under
which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any
form or means without the prior written permission of ADTRAN.

The contents of this document are current as of the date of publication and are subject to change without
notice.

Trademark Information
“ADTRAN” and the ADTRAN logo are registered trademarks of ADTRAN, Inc. Brand names and product
names included in this document are trademarks, registered trademarks, or trade names of their respective
holders.

Disclaimer of Liability
The information or statements given in this document concerning the suitability, capacity, or performance of the
mentioned hardware or software products are given “as is”, and any liability arising in connection with such
hardware or software products shall be governed by ADTRAN’s standard terms and conditions of sale unless
otherwise set forth in a separately negotiated written agreement with ADTRAN that specifically applies to such
hardware or software products.

To the fullest extent allowed by applicable law, in no event shall ADTRAN be liable for errors in this document
for any damages, including but not limited to special, indirect, incidental or consequential, or any losses, such
as but not limited to loss of profit, revenue, business interruption, business opportunity or data, that may arise
from the use of this document or the information in it.

Copyright © 2020 ADTRAN, Inc.


All Rights Reserved.

2 6AOS1370-40A
Table of Contents

Table of Contents

1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2. Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3. Features and Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6


General Features in R13.7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Carrier Ethernet Features in R13.7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4. Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
General Bug Fixes in R13.7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Carrier Ethernet Specific Bug Fixes in R13.7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Voice Specific Bug Fixes in R13.7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Switch Specific Bug Fixes in R13.7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5. Errata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
General Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Carrier Ethernet Specific Errata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Voice Specific Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Switch Specific Errata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6. System Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

7. Upgrade Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

8. Warranty and Contact Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13


Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Contact Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

6AOS1370-40A 3
Introduction

1. Introduction
AOS version R13.7.0 is a major system release that adds new features and addresses customer issues that
were uncovered in previous code releases.
This release is generally available code. Results obtained during internal testing have been evaluated and the
code has been determined to be ready for general availability. Caveats discovered during testing but not
addressed in this build are listed in “Errata” on page 8.
Configuration guides, white papers, data sheets, and other documentation can be found on ADTRAN's Support
Forum, https://supportforums.adtran.com. The contents of these release notes will focus on the platforms listed
in “System Notes” on page 13. Additional information specific to AOS is outlined in “System Notes” on page 13.

2. Supported Platforms
Table 1 lists the platforms that are supported in AOS version R13.7.0. To confirm the Boot ROM version of the
ADTRAN unit, Telnet or console to the unit and issue the show version command. In the command output, the
Boot ROM version will be listed as Boot ROM version XX.XX.XX. If you require a Boot ROM upgrade, please
contact ADTRAN Technical Support support@adtran.com or 888-423-8726) for assistance.
Table 1. Supported Platforms

Platform Standard Enhanced SBC Minimum


Feature Feature Feature Boot ROM
Pack Pack Pack

NetVanta 1234/1234P/1238/1238P (2nd and 3rd  XB.01.02


Gen.)

NetVanta 1531/1531P  R11.1.0

NetVanta 1544/1544F  17.06.04.00

NetVanta 1544 (2nd Gen.)  17.08.01.00

NetVanta 1544P (2nd Gen.)  17.09.01.00

NetVanta 1550  BVS1.0

NetVanta 1638/1638P  18.02.01.SC

NetVanta 3140    R11.5.0

NetVanta 3148   R11.3.0.B3

NetVanta 3200/3205 (3rd Gen.)   17.02.01.00

NetVanta 3305 (2nd Gen.)   04.02.00

NetVanta 3430   13.03.SB

NetVanta 3430 (2nd Gen.)    17.05.01.00

NetVanta 3448    13.03.SB

NetVanta 3450   17.06.01.00

NetVanta 3458   17.06.01.00

NetVanta 4148   R11.3.0.B3

4 6AOS1370-40A
Supported Platforms

Table 1. Supported Platforms (Continued)

Platform Standard Enhanced SBC Minimum


Feature Feature Feature Boot ROM
Pack Pack Pack

NetVanta 4305 (2nd Gen.)   08.01.00

NetVanta 4430    17.04.01.00

NetVanta 4660   R10.10.0.B5

NetVanta 5660   R11.4.1.B2

NetVanta 6250   R10.9.0

NetVanta 6310/6330   A3.01.B2

NetVanta 6360   R11.2.0

Total Access 900 Series (2nd Gen.)  14.04.00

Total Access 900e Series (2nd Gen.)   14.05.00.SA

Total Access 900e Series (3rd Gen.)   R10.9.0

6AOS1370-40A 5
Features and Enhancements

3. Features and Enhancements


General Features in R13.7.0
This section highlights the major features, commands, and behavioral changes for all products running AOS
version R13.7.0.
■ Added support for the NetVanta 3148 and 4148 in SBC-only applications.

Carrier Ethernet Features in R13.7.0


This section highlights the major Carrier Ethernet related features, commands, and behavioral changes for all
products running AOS version R13.7.0.
■ Added Layer 2 forwarding discard and Layer 2 forwarding action discard counters on Gigabit
Ethernet interfaces.
■ Added support for terminal MAC swap loopbacks.

4. Fixes
General Bug Fixes in R13.7.0
This section highlights major bug fixes for all products running AOS version R13.7.0.
■ Fixed an issue in which the gigabit-ethernet 0/2 through 0/5 interfaces would not come up in
some cases when speed 1000 nonegotiate was configured on the NetVanta 4660 and 5660
with a fiber SFP.
■ Fixed an issue in which the xdsl2ChStatusActDataRate object in the VDSL2-LINE-MIB was
reported in kbits/second instead of bits/second.
■ Fixed an issue in which the SSH key did not persist to flash if power was removed immediately
after the ssh key regenerate command completed execution.
■ Fixed an issue in which show running-config took a long time to execute when up to 200
policers were present in the configuration.
■ Fixed an issue in which the use of debug ip udp may have resulted in a lockup and reboot.
■ Fixed an issue in which a reboot may have occurred when using PIM-SM.
■ Fixed an issue in which a unit that did not have any licenses installed displayed an event
message that stated License has been deactivated during bootup.
■ Fixed an issue in which show running-config took a long time to execute when up to 75 tracks
were present in the configuration.
■ Fixed an issue in which a Host already exists error was displayed if the snmp-server host auto-
link traps command was issued after the snmp-server host auto-link traps and then no
snmp-server host auto-link traps commands had been issued.
■ Fixed an issue in which the Priority was displayed as - instead of 0 in the output of show host
verbose the if the SRV priority of a host was 0.
■ Disabled the DES, 3DES, and RC4 ciphers by default in the HTTPS server.
■ Fixed an issue in which a reboot occurred if an ICMPv6 packet with an invalid prefix length was
received by the local IP stack.

6 6AOS1370-40A
Fixes

■ Fixed an issue in which a reboot could occur if the FTP server was accessed by an authenticated
user and ip ftp server default-filesystem cflash was configured.
■ Fixed an issue in which license activation did not work due to improper parsing of the response
from the license server.
■ Fixed an issue in which a default route advertised by OSPF would flap when default-
information originate was configured and the default route was redistributed from BGP.
■ Fixed an issue in which the terminal length was set to 0 when the certificate ca <serial number>
command was issued.
■ Fixed an issue on the NetVanta 3140, 4660, 5660, 6250, 6360, and Total Access 900e (Third
Generation) in which the CPU utilization incorrectly displayed as 100% in the output of show
processes cpu on units with a long uptime.
■ Fixed an issue in which the message displayed upon changing the auto-cost reference
bandwidth on an OSPFv2 process stated to use the clear ospf process command instead of
clear ip ospf process.
■ Fixed an issue in which the clock was not properly adjusted for daylight savings (DST) when DST
started in current year and ended in the following year. Additionally, the timezone database was
updated.

Carrier Ethernet Specific Bug Fixes in R13.7.0


This section highlights Carrier Ethernet specific bug fixes in AOS version R13.7.0.
■ Fixed an issue in which the no men-pri command on EVC maps did not apply properly.
■ Fixed an issue in which the ethernet y1731 enable down-mep md-level-check-filter
configuration command did not persist in the configuration.
■ Fixed an issue in which a Resource conflict error was presented when an EVPL service was
configured with Y.1731 CCMs enabled.
■ Fixed an issue in which the Avg Rate (kbps) in the output of show dynamic-counter didn't
match the values in the output of show dynamic-counter average-rates.
■ Fixed an issue in which one too many Y.1731 single-ended loss measurement PDUs were sent
during each 15 minute measurement interval.

Voice Specific Bug Fixes in R13.7.0


This section highlights voice specific bug fixes in AOS version R13.7.0.
■ Fixed an issue in which 64 bytes of memory was leaked each time a number was dialed from an
analog phone, which would eventually result in a reboot.
■ Fixed an issue in which new registrations would not be triggered if the sip-server on the SIP trunk
was changed and no registrar was configured.
■ Fixed an issue in which Two B-Channel Transfer (TBCT) did not function properly in some
scenarios.
■ Fixed an issue in which a reboot occurred during a call transfer or forward in SBC applications if
the configuration or SIP trunk statistics were being accessed at the same time.
■ Fixed an issue in which inbound calls from an analog trunk to a ring group containing SIP proxy
users failed when the WAN interface was down.

6AOS1370-40A 7
Errata

■ Fixed an issue in which inbound audio was lost and Inbound SRTP decapsulation failure
0x00000004 was displayed repeatedly on the console if a reINVITE with no-op SDP was received
and srtp reduced-rekeying was configured. AOS will now handle the scenario in which the ROC
is improperly reset to 0 in the inbound SRTP stream. Additionally, the optional roc-reset-on-
reinvite parameter was added to the srtp reduced-rekeying command on SIP voice trunks.
■ Fixed an issue in which multipart SIP messages bodies containing SDP were not processed
properly.

Switch Specific Bug Fixes in R13.7.0


This section highlights switch specific bug fixes in AOS version R13.7.0.
■ Fixed an issue on the NetVanta 1531, 1550, and 1638 in which enabling IGMP snooping on a
VLAN prevented IPv6 multicast from passing on that VLAN.
■ Fixed an issue in which it was not possible to remove track <name> from the no shutdown
command on giga-swx and xgiga-swx interfaces.

5. Errata
General Errata
The following is a list of errata that exists in all products running AOS version R13.7.0.
■ The switch ports on the NetVanta 4148 are not supported in R13.7.0.
■ If two TACACS+ hosts are configured, a reboot will occur if a timeout occurs when attempting to
contact the first listed server.
■ The sequence number in the TCP RST generated by the firewall when clearing a policy-session
entry does not comply with RFC 793. This issue occurs when clearing a policy-session entry
manually via the CLI and during failover if ip firewall fast-nat-failover and/or ip firewall fast-
allow-failover are configured.
■ Router advertisements for delegated prefixes assigned to a interface do not use the valid lifetime
specified in the received IA_PD Prefix option. Workaround: Configure ipv6 nd prefix named-
prefix <prefix name> <prefix sub-bits> for each delegated prefix assigned to the interface.
■ Making any changes in the GUI for an Ethernet interface configured for DHCP causes the DHCP
client to perform a DHCP release/renew on that interface when the changes are applied.
■ A few legacy cellular interface commands were incorrectly removed when USB LTE support was
added. The removed commands include:
♦ snmp trap cellular
♦ snmp trap link-status
♦ snmp trap threshold-ecio
♦ snmp trap threshold-rssi
■ The Netvanta 3140 with Novatel USB 551L will dribble a small amount of lost frames with
packets smaller than 512 bytes. The loss occurs in the modem. This issue is to document that
the Novatel USB 551L modem will drop a small percentage (<1%) of packets. We also found
these same drops occur when the 551L is connected to a laptop.
■ Assigning the IP address 192.168.190.1 to a NetVanta 160 from an AOS controller prevents it
from pulling a full configuration from the AOS controller.

8 6AOS1370-40A
Errata

■ If a track is configured to monitor the line protocol of an interface configured for 802.1q, the track
will never go into a passing state even the interface is up. This issue does not affect the
NetVanta 4660, 5660, or 6360. Workaround: Track the line protocol of the subinterface.
■ In some command sets, the exit command is not visible even though it still functions properly.
■ Speed and duplex settings are displayed with on MEF Ethernet interfaces in show running-
config verbose command output, even though those options are not valid and cannot be
configured for that type of interface.
■ In the VQM RTP Monitoring menu, the refresh button refreshes the displayed graphic, but it also
duplicates information in the lower part of the menu. In addition, when the cursor hovers over a
data point, multiple instances of the same data display.
■ In the VQM RTP Monitoring menu, the Source IPs and Interfaces menus have invisible data
points that appear and display data when the cursor hovers over them. The invisible data point
information duplicates a visible data point and can usually be found hidden above the visible
data point.
■ On the NetVanta 3430, the setup wizard in the GUI can freeze with a Please Wait message.
■ The output of show qos map interface <interface> shows ce-vlan-id instead of vlan-id and ce-
vlan-pri instead of cos on products other than the NetVanta 4660.
■ On a NetVanta 4430, information for an inserted SFP does not display correctly.
■ Ethernet interfaces in third generation Total Access 900e units are not visible in the Data > IP
Interfaces GUI menu. These interfaces are visible and can be configured from the System >
Physical Interfaces menu instead.
■ The Total Access 900e (third generation) and NetVanta 6250 send a cold start SNMP trap on
reload instead of a warm start trap.
■ On very rare occasions, port T1 3/3 on an Octal T1 NIM can stop negotiating LCP when it is part
of an MLPPP bundle. Rebooting the device will restore the interface.
■ On the NetVanta 6310 or 6330, if a SHDSL circuit with a detected bad splice retrains to a
different line rate, the distance of the bad splice will display incorrectly.
■ On the NetVanta 6310 or 6330, if the top level ATM interface on a SHDSL ATM NIM2 module is
disabled and re-enabled, the ATM circuit will no longer be able to pass traffic. The ADTRAN unit
must be rebooted to correct the problem.
■ When using a T1/E1 EFM NIM2 in the NetVanta 6310 or 6330, the EFM counters do not
increment as traffic passes through the device.
■ Removing a USB modem from the USB NIM while active could cause the AOS device to reboot.
Shutting down the demand interface being used by the modem prior to removing the modem will
prevent this reboot.
■ Event messages indicating a firmware upgrade was attempted may appear in the AOS event log
for NetVanta 160 APs that are not being upgraded.
■ Having more than two entries in a Network Monitor ICMP probe test list will display Tracked by:
Nothing in the show probe command output. This is merely a display error; the probes still
function correctly.
■ VQM may show a loopback interface in the GUI when a loopback interface is not configured.
■ The called-number command on a demand interface does not function properly.
■ When using XAUTH with a VPN client, an AOS device requests CHAP authentication from the
client but does not send a CHAP challenge payload. This can cause issues with VPN clients that
expect to receive this payload.

6AOS1370-40A 9
Errata

■ If a USB modem is physically disconnected from a USB WWAN NIM while active NIM is active,
the demand interface being used by the modem will not automatically shut down. The demand
interface should be disabled before removing the modem to prevent this issue.
■ On the NetVanta 6310/6330, with FFE enabled, passing traffic from the Ethernet 0/1 interface
out an Ethernet NIM2 can cause the Ethernet 0/1 interface to fail. The interface is recovered with
a reboot. Disabling FFE on the Ethernet 0/1 interface prevents the issue.
■ The vap-reference command will not replicate VLAN IDs for an AP unless 802.1q encapsulation
has been manually enabled on the AP expecting to receive the replicated configuration.
■ Updating PRL values on a Sprint NetVanta 3G NIM may not function properly.
■ EAP Identity Responses from a wireless client that do not contain an Identity field can result in
the NetVanta 150 creating a malformed RADIUS packet.
■ NetVanta 150s may not properly handle immediate Access-Accept responses to Access-
Request messages.
■ The name of a deleted IPv4 ACL cannot be used to name a new IPv6 ACL.
■ When a switchport on a NetVanta 3458 is configured for port-security, it does not receive
BPDUs. If multiple connections between the NetVanta 3458 and another switch are made, a
switching loop could occur because both ports will automatically enter a forwarding state even
though the Spanning Tree protocol should cause one port to enter a blocking state.
■ The output of the command show ethernet cfm mep local may display an incorrect
maintenance association for a MEP ID if multiple maintenance associations are configured on
the unit.

Carrier Ethernet Specific Errata


The following is a list of Carrier Ethernet specific errata that exist in products running AOS version R13.7.0.
■ The Invalid CE VLAN ID counter does not function on the GigabitEthernet 0/1 interface on the
NetVanta 4660, 5660, and 6360 because GigabitEthernet 0/1 is not intended for use as a UNI
interface on these platforms.
■ The efm-group interface type option is missing from the tunnel source command on Tunnel
interfaces.

Voice Specific Errata


The following is a list of voice specific errata that exist in products running AOS version R13.7.0.
■ In some cases it may not be possible to break dial tone after going offhook on a FXS port on the
Total Access 900e (Third Generation) and NetVanta 6250 when the following sequence of
events occurs on that port:
1. A SIP call is established on the FXS port.
2. The user on the FXS port performs a hook flash.
3. A BYE is received from the SIP network before AOS can send the ACK on the reINVITE transaction
resulting from the hook flash.
■ If a voice trunk is removed while calls are active, a reboot may occur.
■ Enabling the SIP stack on a device allocates numerous resources. If this resource allocation
fails, the device will reboot. Multiple sockets must be available and local SIP ports, typically UDP
and TCP 5060, must be available as well, otherwise the resource allocation will fail and the
device will reboot.

10 6AOS1370-40A
Errata

■ When using the SIP proxy with media anchoring, VQM reports incorrect information for
LocalURI, RemoteURI, and LocalCaller if a reINVITE that modifies the SDP is received from the
called party during a call.
■ Issuing the command clear voice call active with active MGCP calls may result in a reboot.
■ If sip tls is configured while sip is disabled, no sip tls must be issued before sip can be
enabled, otherwise the following error will be displayed: %Error: Failed to modify SIP Access-
class with new VRF.
■ If a CA profile is removed while SIP TLS calls using that profile are active, BYE messages will not
be sent for any of the active calls.
■ The ERL tool is not functional on the NetVanta 6360.
■ On the NetVanta 6360, if the onboard FXO port is configured to receive digits, a 500 ms delay is
required after answering before receiving the first DTMF digit.
■ Receiving an initial INVITE with both audio and T.38 SDP will result in the call being placed on
hold.
■ In AOS R10.4.0 and higher, modem-passthrough will fail to send a reINVITE to G.711 if the
endpoint is configured with a codec-list that does not contain G.711.
■ The command ip mgcp qos dscp <value> will not take effect until either ip mgcp is disabled
and then re-enabled or the AOS device is reset.
■ When the SIP server monitor clears the primary SIP server from a delayed state due to a failure
of the secondary SIP server, there will be a 60-second delay until a SIP registration is attempted
to the primary SIP server. This delay will not occur if the SIP server monitor is clearing the
secondary SIP server from a delayed state due to a failure of the primary SIP server.
■ On the Total Access 900e (third generation) and NetVanta 6250, SIP must be enabled in the
running configuration whenever MGCP is used for voice.
■ If an ADTRAN unit is configured with single call appearance mode, forwarded calls on a PRI
trunk will fail.
■ When using media anchoring, receiving a 183 Session Progress after a previous 183 on
hairpinned calls can result in no early media if the SDP in the second 183 differs from the first.
■ Echo cancellation is not enabled on three-way calls when using the local conferencing feature.
■ With the ADTRAN unit set for voice flashhook mode transparent, the conference originator
must wait for the third-party to answer before executing the flashhook to initiate the conference.
■ The Total Access 900e Series (second generation) cannot properly handle more than 40
simultaneous E&M RBS calls. More than 40 simultaneously active calls could result in no dial
tone or no audio on the last 8 channels.
■ On the NetVanta 6310/6330 Series, if a SIP trunk is trying to register a large number of users
and the registration fails, activating debug sip trunk-registration will cause the Telnet and
console connection to become unresponsive. A reboot clears the condition.

Switch Specific Errata


The following is a list of switch specific errata that exist in products running AOS version R13.7.0.
■ On a NetVanta 1544F, a switchport interface with a connected SFP interconnect cable cannot be
shut down properly.
■ The idle process on a NetVanta 1638, visible with the command show processes cpu, is
named procnto-600-, rather than Idle, like other AOS platforms.

6AOS1370-40A 11
Errata

■ Certain NetVanta PoE switches require the command power inline 2-point be configured on
applicable switchports in order to power Polycom VVX phones with three attached color
expansion modules.
■ In an ActivChassis configuration utilizing port channels that are distributed among individual line
cards, if more than 1 Gbps is sent across the port channel the ActivChassis will sometimes
discard some traffic.
■ Traffic destined for devices that match static ARP entries in a Layer 3 switch will experience
extra latency if a static MAC entry is not present for the same device.
■ ICMP responses from a VLAN interface on the NetVanta 1531 may be periodically latent. ICMP
routed or switched through the unit is not affected.
■ Creating a hardware ACL with the same name as a previously created and deleted IP ACL will
result in the creation of an IP ACL with an implicit permit.
■ Removing port channels from the configuration while an ActivChassis is under a heavy load
could cause the ActivChassis to reboot.
■ On NetVanta 1638 units in ActivChassis mode, spanning tree will reconverge at non-rapid
spanning tree rates (about 30 seconds) if there are spanning tree topology changes in the
network.
■ If an ActivChassis line card has NetVanta APs physically attached, and the line card is removed
and added back to the ActivChassis stack, the NetVanta APs will not properly indicate the AC
that controls them. Bouncing the switchport on the line card or rebooting the ActivChassis master
will resolve this issue.
■ Certain OIDs in the Bridge-MIB may not return a value on AOS switches.
■ Port mirroring on a NetVanta 123x (second and third generation) 1534, and 1544 cannot send
transmit mirrored frames without a VLAN tag.

12 6AOS1370-40A
System Notes

6. System Notes
■ Beginning with AOS version 17.09.01, the syntax of certain commands was modified from previous AOS
versions by either removing or adding the ip keyword. In general, when the ip keyword appears in a
command, it signifies that the command is only applicable to IPv4 functionality. As more features introduce
IPv6 support, the ipv6 keyword is added to signify the command is only applicable to IPv6 functionality. The
ip keyword has been removed from several commands to signify that the command has both IPv4 and IPv6
functionality.
Due to this syntax change, downgrading a unit configured in AOS version R13.7.0 to a previous AOS
version, could cause service disruption because the new syntax might not be recognized by the previous
version. Upgrading a unit from an older AOS version to AOS version R13.7.0 will cause no service
disruption because both the old and the new syntaxes are accepted. For more information on specific
commands, refer to the AOS Command Reference Guide available at https://supportforums.adtran.com.
■ It is recommended that your browser’s cache be cleared before viewing the GUI after an upgrade.
■ MGCP is not supported on the NetVanta 6360.
■ As of R11.8.0, a valid SBC call capacity license is required for SIP B2BUA functionality on the following
products:
♦ NetVanta 6250
♦ NetVanta 6360
♦ Total Access 900e (third generation)

7. Upgrade Instructions
Upgrading ADTRAN products to the latest version of AOS firmware is explained in detail in the configuration
guide Upgrading Firmware in AOS, available at https://supportforums.adtran.com.

8. Warranty and Contact Information


Warranty
Warranty information can be found online at: www.adtran.com/warranty.

Contact Information
For all customer support inquiries, please contact ADTRAN Customer Care:

Contact Support Contact Information

Customer Care From within the U.S. 1.888.4ADTRAN (1.888.423.8726)


From outside the U.S. + 1.256.963.8716
Technical Support: www.adtran.com/support
■ Web:
Training: training@adtran.com
■ Email: www.adtran.com/training
■ Web: www.adtranuniversity.com
Sales Pricing and Availability 1.800.827.0807

6AOS1370-40A 13

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy